Since I upgraded to Plasma6KDE 5.6.0, Dropbox is missing its system tray icon again. This has been an issue in the past, and has been fixed for quite a while, so not sure if this issue is related to the old one. Reproducible: Always Steps to Reproduce: 1. Start Dropbox Actual Results: No icon in system tray even though Dropbox is running Expected Results: Dropbox icon should appear in system tray Possibly related: https://bugs.kde.org/show_bug.cgi?id=344620
is a process called xembedsniproxy running?
Hello, I have just upgraded to Kubuntu 16.04 from 15.04 and it went very well, I am now running plasma version 5.6.90 and initially the dropbox icon was showing ok, then I upgraded some packages including a new set of icons and it disappeared although dropbox is still running in the background, its annoying since I can't even uninstall dropbox from the system as it says it isn't installed....however I just wanted to know if there was any fix for the dropbox icon missing? thanks
confirmed here, chakra testing, plasma 5.6.4 Old workaround using dbus-launch not working anymore.
xembedsniproxy is working: $pgrep -a xembedsniproxy 978 /usr/bin/xembedsniproxy
with simplesystray works: https://quickgit.kde.org/?p=scratch%2Fmart%2Fsimplesystray.git (old compiled version 5.6.0)
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 set the bug status 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!
*** This bug has been marked as a duplicate of bug 361613 ***