Icon for volume control, it's a ghost

Desktop Environments XFCE
1

Hello everyone !

As the title of the post says, the volume control icon appears and disappears in the upper right corner of the screen every so often, that in itself is not the problem.

Also when “icon ghost” appears, it produces a very unpleasant sound (thick beep) from the speakers, as if you were connecting or disconnecting something in the computer.

Long ago, I can’t remember well anymore, I think @pudge had written something about it.

It only appears on the Xfce desktop, not on others.

I leave a screenshot so that you can see the exposed better:

2021-05-16-153936_1920x1080_scrot

Thanks, as always !

2

I see it only when i boot up. It also comes up if i scroll the volume up or down on the icon in the tray.

3

interesting. are you guys using Status Tray Plugin or Status Notifier Plugin to display the tray? Might be worth switching from the one to the other.
I am writing this because I don’t experience any of this, but then again, nothing happens if I scroll over the sound icon, so I think I am using another tray plugin than you (I’m using Status Tray Plugin).

4

It’s what ever was installed from default. I haven’t changed a thing on this Xfce install. I don’t usually change things like that only icons, background. I’m using the vanilla set up.

5

That’s the difference, in my case it appears every now and then without touching the volume at any time. This annoyance has been happening for a long time in Xfce, in several versions of EOS.

6

sound it a plugin that no working as should .

7

what shows up is the osd (xfce4-notifyd) should be the default, indicates volume changes :wink:
~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-notifyd.xml

This looks like something is reinitializing or crashing and restarting… so not the osd itself and more like something with Soundsystem is causing osd to show up.

Alsa or Pulseaudio… journal do not show related errors?

journalctl --since "60 minutes ago" | grep pulseaudio

8

First of all, thank you all for the responses!
I have not had an inet signal for more than twenty days and I am only getting by with my smartphone, and data is not cheap on this side of the world.
For this reason I have not published dmesg or journalctl, since I have no upload in the data and only download them. Having to borrow a place with internet … is what you see next in my house:

[judd@judd-b365mds3h ~]$ speedtest simple

   Speedtest by Ookla

     Server: EdgeUno - Buenos Aires (id = 29672)
        ISP: Telecom Personal
    Latency:    39.24 ms   (1.82 ms jitter)
   Download:     9.06 Mbps (data used: 11.3 MB)                               
   Download: FAILED                                            
[error] Cannot open socket: Timeout occurred in connect.
[judd@judd-b365mds3h ~]$

@joekamprad !

Resumen

[judd@judd-b365mds3h ~]$ journalctl --since “60 minutes ago” | grep pulseaudio

may 18 10:29:51 judd-b365mds3h dbus-daemon[442]: [system] Activating via systemd: service name=‘org.freedesktop.RealtimeKit1’ unit=‘rtkit-daemon.service’ requested by ‘:1.33’ (uid=1000 pid=2707 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo")

may 18 10:29:52 judd-b365mds3h dbus-daemon[442]: [system] Activating via systemd: service name=‘org.bluez’ unit=‘dbus-org.bluez.service’ requested by ‘:1.39’ (uid=1000 pid=2707 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo")

may 18 10:30:00 judd-b365mds3h systemd[1115]: pulseaudio.socket: Deactivated successfully.

may 18 10:30:17 judd-b365mds3h pulseaudio[2707]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

may 18 10:34:29 judd-b365mds3h pulseaudio[2707]: ICE default IO error handler doing an exit(), pid = 2707, errno = 11

may 18 10:34:30 judd-b365mds3h systemd[2063]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE

may 18 10:34:30 judd-b365mds3h systemd[2063]: pulseaudio.service: Failed with result ‘exit-code’.

may 18 10:34:30 judd-b365mds3h systemd[2063]: pulseaudio.socket: Deactivated successfully.

may 18 10:35:05 judd-b365mds3h dbus-daemon[465]: [system] Activating via systemd: service name=‘org.freedesktop.RealtimeKit1’ unit=‘rtkit-daemon.service’ requested by ‘:1.31’ (uid=1000 pid=932 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo")

may 18 10:35:06 judd-b365mds3h dbus-daemon[465]: [system] Activating via systemd: service name=‘org.bluez’ unit=‘dbus-org.bluez.service’ requested by ‘:1.37’ (uid=1000 pid=932 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo")

may 18 10:35:13 judd-b365mds3h systemd[718]: pulseaudio.socket: Deactivated successfully.

may 18 10:35:31 judd-b365mds3h pulseaudio[932]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

[judd@judd-b365mds3h ~]$

(Sent from Win10 …) :shushing_face: :grinning_face_with_smiling_eyes:

Thanks !

9

shows exactly what you are experiencing, but only a little hint on what is causing it :wink: