This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

FEDORA-2020-fa16bcad0c has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-fa16bcad0c

The directory ownership should be fixed now. Can you test the package in the update request?
https://bodhi.fedoraproject.org/updates/FEDORA-2020-fa16bcad0c

When I install gmediarender there is an error in POSTIN scriptlet:

[root@localhost andrea]# export LANG=en_US.UTF-8
[root@localhost andrea]# dnf install https://kojipkgs.fedoraproject.org//packages/gmediarender/0.0.8/6.fc33/x86_64/gmediarender-0.0.8-6.fc33.x86_64.rpm
Last metadata expiration check: 2:15:06 ago on Sun 13 Dec 2020 10:59:36 AM CET.
gmediarender-0.0.8-6.fc33.x86_64.rpm            103 kB/s |  88 kB     00:00    
Dependencies resolved.
================================================================================
 Package            Architecture Version               Repository          Size
================================================================================
Installing:
 gmediarender       x86_64       0.0.8-6.fc33          @commandline        88 k

Transaction Summary
================================================================================
Install  1 Package

Total size: 88 k
Installed size: 156 k
Is this ok [y/N]: y
Downloading Packages:
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                        1/1 
  Running scriptlet: gmediarender-0.0.8-6.fc33.x86_64                       1/1 
  Installing       : gmediarender-0.0.8-6.fc33.x86_64                       1/1 
  Running scriptlet: gmediarender-0.0.8-6.fc33.x86_64                       1/1 
/var/tmp/rpm-tmp.K43pnF: line 8: fg: no job control
warning: %post(gmediarender-0.0.8-6.fc33.x86_64) scriptlet failed, exit status 1

Error in POSTIN scriptlet in rpm package gmediarender
  Verifying        : gmediarender-0.0.8-6.fc33.x86_64                       1/1 

Installed:
  gmediarender-0.0.8-6.fc33.x86_64                                              

Complete!


If I start gmediareder as a service I still cannot play an audio file.

[root@localhost andrea]# systemctl start gmediarender

This is the journald log (no error is shown):

[root@localhost andrea]# journalctl -u gmediarender
-- Logs begin at Thu 2020-11-26 15:56:17 CET, end at Sun 2020-12-13 13:58:24 CET. --
Dec 13 13:53:53 localhost.localdomain systemd[1]: Started GMediaRender UPnP/DLNA renderer.
Dec 13 13:54:05 localhost.localdomain gmediarender[8625]: gmediarender 0.0.8 started [ gmediarender 0.0.8 (libupnp-1.12.1; glib-2.66.3; gstreamer-1.18.1) ].
Dec 13 13:54:05 localhost.localdomain gmediarender[8625]: Logging switched off. Enable with --logfile=<filename> (or --logfile=stdout for console)
Dec 13 13:54:08 localhost.localdomain gmediarender[8625]: Ready for rendering.
Dec 13 13:58:24 localhost.localdomain systemd[1]: Stopping GMediaRender UPnP/DLNA renderer...
Dec 13 13:58:24 localhost.localdomain systemd[1]: gmediarender.service: Succeeded.
Dec 13 13:58:24 localhost.localdomain systemd[1]: Stopped GMediaRender UPnP/DLNA renderer.
Dec 13 13:58:24 localhost.localdomain systemd[1]: gmediarender.service: Consumed 4.269s CPU time.

If I start gmediarender from root, I cannot also the audio file and that's what I get (probably that's the correct behaviour):

[root@localhost andrea]# gmediarender 
gmediarender 0.0.8 started [ gmediarender 0.0.8 (libupnp-1.12.1; glib-2.66.3; gstreamer-1.18.1) ].
Logging switched off. Enable with --logfile=<filename> (or --logfile=stdout for console)
Ready for rendering.
XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e.g. happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)

If I start gmediarender from a non-root user, I can play the audio file but I also get some error:

[andrea@localhost ~]$ gmediarender
gmediarender 0.0.8 started [ gmediarender 0.0.8 (libupnp-1.12.1; glib-2.66.3; gstreamer-1.18.1) ].
Logging switched off. Enable with --logfile=<filename> (or --logfile=stdout for console)
ERROR [2020-12-13 14:03:58.543235 | webserver] Could not stat '/usr/share/gmediarender/grender-64x64.png': Permission denied
ERROR [2020-12-13 14:03:58.543262 | webserver] Could not stat '/usr/share/gmediarender/grender-128x128.png': Permission denied
Ready for rendering.

Permissions in that directory:

[andrea@localhost ~]$ ll -d /usr/share/gmediarender/
drwx------. 4 gmediarender gmediarender 4096 13 dic 13.56 /usr/share/gmediarender/

FEDORA-2020-fa16bcad0c has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-fa16bcad0c`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-fa16bcad0c

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

(In reply to Andrea Musuruane from comment #4)
> If I start gmediarender from root, I cannot also the audio file and that's
> what I get (probably that's the correct behaviour):
> 
> [root@localhost andrea]# gmediarender 
> gmediarender 0.0.8 started [ gmediarender 0.0.8 (libupnp-1.12.1;
> glib-2.66.3; gstreamer-1.18.1) ].
> Logging switched off. Enable with --logfile=<filename> (or --logfile=stdout
> for console)
> Ready for rendering.
> XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid
> 1000! (This could e.g. happen if you try to connect to a non-root PulseAudio
> as a root user, over the native protocol. Don't do that.)
> XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid
> 1000! (This could e.g. happen if you try to connect to a non-root PulseAudio
> as a root user, over the native protocol. Don't do that.)
> XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid
> 1000! (This could e.g. happen if you try to connect to a non-root PulseAudio
> as a root user, over the native protocol. Don't do that.)
> XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid
> 1000! (This could e.g. happen if you try to connect to a non-root PulseAudio
> as a root user, over the native protocol. Don't do that.)
> XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid
> 1000! (This could e.g. happen if you try to connect to a non-root PulseAudio
> as a root user, over the native protocol. Don't do that.)
> XDG_RUNTIME_DIR (/run/user/1000) is not owned by us (uid 0), but by uid
> 1000! (This could e.g. happen if you try to connect to a non-root PulseAudio
> as a root user, over the native protocol. Don't do that.)
> 

Not allowing to run as root is actually the expected behavior.

> If I start gmediarender from a non-root user, I can play the audio file but
> I also get some error:
> 
> [andrea@localhost ~]$ gmediarender
> gmediarender 0.0.8 started [ gmediarender 0.0.8 (libupnp-1.12.1;
> glib-2.66.3; gstreamer-1.18.1) ].
> Logging switched off. Enable with --logfile=<filename> (or --logfile=stdout
> for console)
> ERROR [2020-12-13 14:03:58.543235 | webserver] Could not stat
> '/usr/share/gmediarender/grender-64x64.png': Permission denied
> ERROR [2020-12-13 14:03:58.543262 | webserver] Could not stat
> '/usr/share/gmediarender/grender-128x128.png': Permission denied
> Ready for rendering.
> 
> Permissions in that directory:
> 
> [andrea@localhost ~]$ ll -d /usr/share/gmediarender/
> drwx------. 4 gmediarender gmediarender 4096 13 dic 13.56
> /usr/share/gmediarender/

Ok this can be fixed easily.
BTW, can I know which application you are rendering from? I package this several years ago to enjoy music on my mobile in the beginning. However I haven't use this again after changed my mobile long time ago, and I cannot even find any working app to actually render from now. If you could give me some information on the app you are rendering from it'll be really useful for me to debug the rendering issue when running as a service.

(In reply to Zamir SUN from comment #6)

> BTW, can I know which application you are rendering from? I package this
> several years ago to enjoy music on my mobile in the beginning. However I
> haven't use this again after changed my mobile long time ago, and I cannot
> even find any working app to actually render from now. If you could give me
> some information on the app you are rendering from it'll be really useful
> for me to debug the rendering issue when running as a service.

I'm using BubbleUPnP
https://play.google.com/store/apps/details?id=com.bubblesoft.android.bubbleupnp

Thanks for the info.

Can you try this scratch build? When running as service, rendering from my mobile (using BubbleUPnP free version) works just fine for me with this.
https://koji.fedoraproject.org/koji/taskinfo?taskID=57436773

In case you did not check it, you need to enable ssdp and gmediarender service on firewall.

The situation in unchanged. If I start gmediareder as a service I still cannot play an audio file, even with firewalld stopped.

If I start gmediarender from a non-root user, I no longer have permission errors:

[andrea@localhost ~]$ gmediarender 
gmediarender 0.0.8 started [ gmediarender 0.0.8 (libupnp-1.12.1; glib-2.66.3; gstreamer-1.18.2) ].
Logging switched off. Enable with --logfile=<filename> (or --logfile=stdout for console)
Ready for rendering.

This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle.
Changing version to 34.

This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '35'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.

This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.

Fedora Linux 36 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.