| Summary: | No longer can restart, reboot or log off via applications kickoff launcher | ||
|---|---|---|---|
| Product: | [Unmaintained] plasma4 | Reporter: | Gérard Talbot (no longer involved) <browserbugs2> |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | major | CC: | ahx2323, ales, dvdmerwe, fsateler, jbh, rdieter |
| Priority: | HI | ||
| Version: | 4.11.2 | ||
| Target Milestone: | --- | ||
| Platform: | Kubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Gérard Talbot (no longer involved)
2013-11-13 03:20:21 UTC
Product is now plasma-nm Other similar or related or dependent bug reports: Bug 325324 - Crash on upgrade from networkmanagement to plasma-nm https://bugs.kde.org/show_bug.cgi?id=325324 and Bug _1231360_ crash on upgrade from networkmanagement to plasma-nm https://bugs.launchpad.net/ubuntu/+source/plasma-nm/+bug/1231360 I too can't reboot|logout|shutdown through kickoff menu, but kshutdown work fine. Linux Mint 15 KDE platform version 4.10.5. What action taken when user click kickoff reboot|logout|shutdown menu item? Where is config file for these actions? > I too can't reboot|logout|shutdown through kickoff menu, but > kshutdown work fine. Cade, I do not know what kshutdown is but I was able to restart via Konsole (terminal) with sudo reboot In order to shutdown via Konsole (terminal), I believe that sudo shutdown should also work. > > Linux Mint 15 > KDE platform version 4.10.5. > > What action taken when user click kickoff reboot|logout|shutdown menu item? I believe you meant to say "What action *_is supposed to be_* taken when user click kickoff reboot|logout|shutdown menu item?" > Where is config file for these actions? Cade, I was able to "fix" (definitely not the correct verb here) the problem I was experiencing by reading "NetworkManager broken after upgrade to Kubuntu Saucy" coming from http://askubuntu.com/questions/363945/networkmanager-broken-after-upgrade-to-kubuntu-saucy#answer-368532 and by trying in Konsole (terminal) sudo service network-manager restart Don't ask me why or how this happens... I have no idea. Gérard Don't know if this is related or merits it's own bug report. I've had a similar problem for ages. Sometimes I can't logout/restart/shutdown from the Kickoff menu, invoking ksmserver directly also has no effect. I read some bugreport elsewhere stating that disabling the logout sound fixes it, and indeed that appears to be true on my system. Interesting as I've have the player settings configured for no audio output. 64b Archlinux + KDE 4.12.4 I have the same problem. Kubuntu 14.04, KDE 4.13.0, all updates. I don't have any logout sound enabled. Maybe it has something to do with the policy: https://wiki.debian.org/PolicyKit I tried this: sudo apt-get install --reinstall policykit-1 policykit-desktop-privileges consolekit polkit-kde-1 Then I had to force shut down KDE with killall ksmserver. After new login everything works again. Unfortunately I'm not sure if it's a real solution or just a coincidence. You can try it. At least it shouldn't break up anything. I have been re-experiencing on and off (intermittently) this annoying phenomenon. And now, what I do is, from the keyboard (and not in a terminal): Alt+System+E (halts all programs) and then Alt+System+U (puts hard disk in read-only mode) and then Alt+System+B (restarts, reboots system) and this restarts my system. I am now using Linux 3.13.0-27-generic x86_64 Qt: 4.8.6 KDE Development platform: 4.13.1 Description: Kubuntu 14.04 LTS Codename: trusty Gérard I have been experiencing similar symptoms: I cannot logout, reboot or shut down the computer from the "Leave" menu. The confirmation pop-up never appears. I have discovered that ksmserver does not respond to the org.kde.KSMServerInterface.logout dbus method. Also, KDE does not appear to be starting the programs configured to autostart on login (not sure if related, but since both are session related...). I have been unable to find any logs that might be related. xsession-errors does not say anything, nor does the X log or the systemd journal. I'm using systemd 208. PolicyKit issues are not likely, because I can issue systemctl poweroff as my own user just fine. I did test with a test user, and I can logout with that user. This suggests that I have some sort of misconfiguration that confuses kde. I can provide any extra information required, just instruct me what to do and where to look. see bug #328571 for a bit more analysis, and one possible workaround (setting QT_NO_GLIB=1) *** This bug has been marked as a duplicate of bug 328571 *** |