Bug 309874 - restarting dbus causes keyboard layout disappear and Klipper appear in tray
Summary: restarting dbus causes keyboard layout disappear and Klipper appear in tray
Status: RESOLVED WORKSFORME
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 4.8.4
Platform: FreeBSD Ports FreeBSD
: NOR normal
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-10 20:09 UTC by Yuri
Modified: 2023-01-30 05:07 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yuri 2012-11-10 20:09:40 UTC
When I restart dbus '/usr/local/etc/rc.d/dbus restart', keyboard layout switcher disappear, and KOrganizer and Klipper appear in tray.

Maybe it is debatable if DBus restart by user is a legitimate operation. But why Korganizer and Klipper were not shown before such restart? This is definitely a problem. Another apparent problem is why different tray icons behave differently when DBus is restarted? Why does keyboard layout indicator disappear?

Another side effect is that global user defined keyboard shortcuts stopped working.

So the main point of this PR is to ensure that kde4 behaves consistently when DBus is restarted. kde4 should probably try to be as unaffected as possible, always reconnecting it DBus in case connection is lost.

Another side issue is that KOrganizer and Klipper aren't started by the system.

Reproducible: Always
Comment 1 Yuri 2012-11-10 20:12:48 UTC
Also printer applet crashes when dbus is restarted.
Comment 2 Andrew Crouthamel 2018-11-09 01:03:59 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 3 Andrew Crouthamel 2018-11-20 03:58:14 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? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Justin Zobel 2022-12-31 00:24:30 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 5 Bug Janitor Service 2023-01-15 05:10:52 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 6 Bug Janitor Service 2023-01-30 05:07:33 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!