Bug 327543 - No longer can restart, reboot or log off via applications kickoff launcher
Summary: No longer can restart, reboot or log off via applications kickoff launcher
Status: RESOLVED DUPLICATE of bug 328571
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: 4.11.2
Platform: Kubuntu Linux
: HI major
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-13 03:20 UTC by Gérard Talbot (no longer involved)
Modified: 2014-07-12 20:37 UTC (History)
6 users (show)

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 Gérard Talbot (no longer involved) 2013-11-13 03:20:21 UTC
Since today, I no longer can restart, reboot or session logoff. This is a serious issue.

Reproducible: Always

Steps to Reproduce:
1. Click the big white K on blue background button (lower-left corner of plasma panel)
2. Hover the mouse cursor over the rightmost red-on-white "Quit" button
3. Several choices appear including Disconnect (end session: downward white arrow on light blue background), Restart (white curvy arrow on orange background) and Turn off computer (white symbol on red background) appear
4. Click one of those 3 choices
Actual Results:  
Nothing happens !

Expected Results:  
Session should end (disconnect) or system should reboot or computer should turn off.

I updated my system today with the following:

libnetworkmanagerqt0 (0.9.0-0ubuntu1, 0.9.0.1-0ubuntu1~saucy1) updated at 18:36 today

plasma-nm (0.9.0.3-0ubuntu5.1, 0.9.3.1-0-ubuntu1~saucy1) updated at 18:36 today

Additional information on my system
--------------------------------------------------
uname --kernel-name --kernel-release --processor && kde4-config --version && lsb_release --description --codename
will return:

Linux 3.11.0-13-generic x86_64
Qt: 4.8.4
KDE Development platform: 4.11.2
kde4-config: 1.0
Description:    Ubuntu 13.10
Codename:       saucy

If product and/or component are wrong, please make appropriate corrections if you know these.

I can provide more information on recent packages installed on my system if requested.
Comment 1 Gérard Talbot (no longer involved) 2013-11-13 23:08:20 UTC
Product is now plasma-nm
Comment 2 Gérard Talbot (no longer involved) 2013-11-13 23:26:17 UTC
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
Comment 3 Cade 2013-11-15 12:09:14 UTC
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?
Comment 4 Gérard Talbot (no longer involved) 2013-11-15 18:00:36 UTC
> 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
Comment 5 Joakim Hernberg 2014-04-04 13:14:05 UTC
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
Comment 6 altosch 2014-05-27 10:34:40 UTC
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.
Comment 7 Gérard Talbot (no longer involved) 2014-05-30 01:01:54 UTC
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
Comment 8 Felipe Sateler 2014-07-12 19:56:43 UTC
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.
Comment 9 Rex Dieter 2014-07-12 20:37:47 UTC
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 ***