Bug 210973

Summary: Icons using the new system tray protocol do not appear on KDE3 (kded4 registers the interface and disables the legacy FDO protocol)
Product: [Unmaintained] kdelibs Reporter: Vito De Tullio <vito.detullio>
Component: generalAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: normal CC: alex.danila.web, andresbajotierra, asraniel, espinosa_cz, notmart, plasma-bugs-null
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Vito De Tullio 2009-10-18 15:10:24 UTC
Version:           KDE 4.3.72 (KDE 4.4 >= 20091015 (using Devel)
OS:                Linux
Installed from:    Compiled sources

I know, kde3 is no longer supported.
but.
I primaly use kde3 as my DE, plus some (kmail, ktorrent, kopete...) kde4 single apps.
Some of them use the systray to let me hide in background.

today, using kmess 2.0 + kde 4.3.72 I sadly found it no longer shows the icon into the kde3 systray (no problems in kde4 version).

Is this intentional? Can be resolved with little pain? One thing is no longer active support, another is intentionally break good'ol kde :\
Comment 1 Dario Andres 2009-11-01 16:39:31 UTC
AFAIK the applications using the new systray icon class (KStatusNotifierItem) will fallback to the old FDO protocol (Q/KSystemTrayIcon) if a Plasma SystemTray (which is capable of rendering the new items) is not found. So, icons should appear in any other systemtray implementation (including KDE3, GNOME, XFCE, other panels..). Support was not dropped, so this should be a bug somewhere.

- Have you tried this with an updated KDE4 and several other KDE4 apps ? (KMix, KWalletManager and some others are also using the new protocol/system too)

Thanks
Comment 2 Vito De Tullio 2009-11-03 20:45:54 UTC
$ /usr/bin/kmix --version
Qt: 4.6.0                                   
KDE: 4.3.73 (KDE 4.3.73 (KDE 4.4 >= 20091026)) "release 2"
KMix: 3.6-alpha2                                          
$ /usr/bin/kmix
kmix(3410) Mixer::setGlobalMaster: Mixer::setGlobalMaster() card= "ALSA::HDA_ATI_SB:1"  control= "Master:0"
kmix(3410) Mixer_ALSA::openAlsaDevice: "Trying ALSA Device 'hw:0': " found                                 
kmix(3410) Mixer_ALSA::identify: "Master"                                                                  
kmix(3410) Mixer_ALSA::open: Setting m_recommendedMaster to  "Master:0"                                    
kmix(3410) Mixer_ALSA::identify: "Headphone"                                                               
kmix(3410) Mixer_ALSA::identify: "PCM"                                                                     
kmix(3410) Mixer_ALSA::identify: "Front Mic Boost"                                                         
kmix(3410) Mixer_ALSA::identify: "Mic Boost"                                                               
kmix(3410) Mixer_ALSA::identify: "Capture"                                                                 
kmix(3410) Mixer_ALSA::identify: "Capture"                                                                 
kmix(3410) Mixer_ALSA::identify: "Beep"                                                                    
kmix(3410) Mixer_ALSA::identify: "Digital"                                                                 
kmix(3410) Mixer_ALSA::identify: "Input Source"                                                            
kmix(3410) Mixer_ALSA::identify: "Input Source"                                                            
kmix(3410) Mixer_ALSA::identify: "Speaker"                                                                 
kmix(3410) Mixer::openIfValid: Mixer::open() detected master:  "Master:0"                                  
kmix(3410) MixerToolBox::possiblyAddMixer: mixerNums entry of added mixer is now:  1                       
kmix(3410) Mixer_ALSA::openAlsaDevice: "Trying ALSA Device 'hw:1': " not found: snd_ctl_open err= No such file or directory
kmix(3410) Mixer_ALSA::openAlsaDevice: "Trying ALSA Device 'hw:2': " not found: snd_ctl_open err= No such file or directory
kmix(3410) Mixer_ALSA::openAlsaDevice: "Trying ALSA Device 'hw:3': " not found: snd_ctl_open err= No such file or directory
kmix(3410) Mixer_ALSA::openAlsaDevice: "Trying ALSA Device 'hw:4': " not found: snd_ctl_open err= No such file or directory
kmix(3410) Mixer_ALSA::openAlsaDevice: "Trying ALSA Device 'hw:5': " not found: snd_ctl_open err= No such file or directory
kmix(3410) Mixer_ALSA::openAlsaDevice: "Trying ALSA Device 'hw:6': " not found: snd_ctl_open err= No such file or directory
kmix(3410) Mixer_ALSA::openAlsaDevice: "Trying ALSA Device 'hw:7': " not found: snd_ctl_open err= No such file or directory
kmix(3410) Mixer_ALSA::openAlsaDevice: "Trying ALSA Device 'hw:8': " not found: snd_ctl_open err= No such file or directory
kmix(3410) Mixer_ALSA::openAlsaDevice: "Trying ALSA Device 'hw:9': " not found: snd_ctl_open err= No such file or directory
kmix(3410) Mixer_ALSA::openAlsaDevice: "Trying ALSA Device 'hw:10': " not found: snd_ctl_open err= No such file or directory
kmix(3410) Mixer_ALSA::openAlsaDevice: "Trying ALSA Device 'hw:11': " not found: snd_ctl_open err= No such file or directory
kmix(3410) Mixer_ALSA::openAlsaDevice: "Trying ALSA Device 'hw:12': " not found: snd_ctl_open err= No such file or directory
kmix(3410) Mixer_ALSA::openAlsaDevice: "Trying ALSA Device 'hw:13': " not found: snd_ctl_open err= No such file or directory
kmix(3410) Mixer_ALSA::openAlsaDevice: "Trying ALSA Device 'hw:14': " not found: snd_ctl_open err= No such file or directory
kmix(3410) Mixer_ALSA::openAlsaDevice: "Trying ALSA Device 'hw:15': " not found: snd_ctl_open err= No such file or directory
kmix(3410) Mixer_ALSA::openAlsaDevice: "Trying ALSA Device 'hw:16': " not found: snd_ctl_open err= No such file or directory
kmix(3410) Mixer_ALSA::openAlsaDevice: "Trying ALSA Device 'hw:17': " not found: snd_ctl_open err= No such file or directory
kmix(3410) Mixer_ALSA::openAlsaDevice: "Trying ALSA Device 'hw:18': " not found: snd_ctl_open err= No such file or directory
kmix(3410) Mixer_ALSA::openAlsaDevice: "Trying ALSA Device 'hw:19': " not found: snd_ctl_open err= No such file or directory
kmix(3410) MixerToolBox::initMixer: "Driver audio supportati: ALSA + OSS
Driver audio usati: ALSA"
Total number of detected Mixers:  1
kmix(3410) MixerToolBox::selectProfile: "profiles/ALSA.default.xml" ; fnfq1= "/usr/share/kde4/apps/kmix/profiles/ALSA.default.xml"
kmix(3410) MixerToolBox::selectProfile: "profiles/ALSA.HDA_ATI_SB.xml" ; fnfq2= ""
kmix(3410) MixerToolBox::selectProfile: 0 : Check user profile  ""
kmix(3410) MixerToolBox::selectProfile: 1 : Check user profile  "ALSA.default.xml"
kmix(3410) MixerToolBox::selectProfile: 1 : Try user profile  "/usr/share/kde4/apps/kmix/profiles/ALSA.default.xml"
kmix(3410) GUIProfile::readProfile: Read profile: "profiles/ALSA.default.xml"  =>  "/usr/share/kde4/apps/kmix/profiles/ALSA.default.xml"
kmix(3410) KMixerWidget::loadConfig: KMixerWidget::loadConfig()
kmix(3410) KMixerWidget::loadConfig: KMixerWidget::loadConfig() "Base"
kmix(3410) KMixToolBox::loadView: KMixToolBox::loadView() grp= "View.Base"
kmix(3410)/kdeui (KNotification) KNotificationItemDBus::KNotificationItemDBus: service is "org.kde.NotificationItem-3410-1"
kmix(3410)/kdeui (KNotification) KNotificationItemPrivate::registerToDaemon: Registering a client interface to the system tray daemon
kmix(3410) Mixer_ALSA::readVolumeFromHW: volumePlayback control= "Master:0" , chid= 0 , vol= 34
kmix(3410) Mixer_ALSA::readVolumeFromHW: volumePlayback control= "PCM:0" , chid= 0 , vol= 255
kmix(3410) Mixer_ALSA::readVolumeFromHW: volumePlayback control= "PCM:0" , chid= 1 , vol= 255


and

$ /usr/bin/kwalletd --version
Qt: 4.6.0
KDE: 4.3.73 (KDE 4.3.73 (KDE 4.4 >= 20091026)) "release 2"
Servizio portafogli di KDE: 0.2
$ /usr/bin/kwalletd
[no stdout]

and (just in case)

$ /opt/kde3/bin/kicker --version
Qt: 3.3.8b
KDE: 3.5.10 "release 61"
KDE Panel: 3.5.10

and no icon on the panel
Comment 3 Dario Andres 2009-11-03 22:01:53 UTC
May be the a kded4 daemon is enabling the new protocol interface, and therefore the icons is registered on it, so the fallback protocol is not enabled at all. (just a wild guess, I don't really know how this work)
I wonder if Marco can take a look at this. 
Regards
Comment 4 Vito De Tullio 2009-11-07 11:28:24 UTC
Well, I made some stupid test...
I have kde4 kmix and knetworkmanager launched, but I can't see the icons on the kde3 panel.
killing the process called "kdeinit4: kded4 [kdeinit]" they "magically" appears.
but if I interact with them (for example: i select a connection from the knetworkmanager popup) a new kdeinit4 process is launched and they "magically" disappears.
Comment 5 Dario Andres 2009-11-09 22:37:18 UTC
It seems likely as a bug of the new implementation... probably as I suggested in comment 3.
Thanks for testing
Comment 6 Dario Andres 2009-11-16 16:44:40 UTC
*** Bug 214795 has been marked as a duplicate of this bug. ***
Comment 7 Alex Dănilă 2009-11-18 14:12:48 UTC
Hi, one further note from the duplicate 214795.

The gnome-panel is only affected by this bug if it is running in a KDE session. gnome-panel running in a GNOME session will function correctly. I believe this confirms Dario's guess at comment #3.
Comment 8 Dario Andres 2010-02-03 02:00:05 UTC
*** Bug 225137 has been marked as a duplicate of this bug. ***
Comment 9 Andrew Crouthamel 2018-11-02 23:06:29 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 10 Andrew Crouthamel 2018-11-16 05:29:29 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version?

Thank you for helping us make KDE software even better for everyone!
Comment 11 Justin Zobel 2022-12-09 22:13:22 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 12 Vito De Tullio 2022-12-10 02:53:58 UTC
Well, I don't use KDE 3, nor KDE 4, anymore, so I don't really think Is really possible to help on this ticket.
Comment 13 Bug Janitor Service 2022-12-25 05:20:33 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 14 Bug Janitor Service 2023-01-09 05:15:07 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!