It seems that the new discover is not capable of switching into admin mode? Trying to update I only get a message that “This operation cannot continue since proper authorization was not provided”. Did it ask for? No.
Of course I can update via apt in a terminal - but the system is for someone who is not willing to deal with a terminal…
So how can this be solved?
Seems to be related to the other problem with the password prompt.
Somehow either dbus or the policykit session are not up and running for you.
Do you have a second user logged in which maybe does not have the sufficent rights ?
I have the same issue and I have only one user on the system
Please make sure that the package polkit-kde-1 is installed. It might have been removed during the upgrade to Plasma 5.5.4 in Kubuntu Backports ppa.
The installation of polkit-kde-1 solved the issue, thank you :).
Not solved. After a system restart the same problem occurs though polkit-kde-1 and polkit-kde-agent-1 are installed…
Had the same problem. As posted in the http://forums.netrunner.com/showthread.php?tid=23499 thread a downgrade of sddm did the job for me.
sudo apt-get install sddm=0.11.0-0ubuntu11I’m curious about the result.
Greetings
Solved :).
These 4 issues were solved by downgrading sddm:
As loginctl show-session revealed the session was marked as “online” and therefore the user was not allowed to play local sound, shutdown the system, update the system and use removable media without authorizsation. I just wonder why the session gets marked as online session with sddm 13…
Can you give the full output of the loginctl show-session command of the session that isn’t working.
Btw. how many sessions do you have ? Maybe SDDM started twice.
There were 2 sessions listed in both cases: 1 sddm seat0 & 2 the user seat0
The output of the working and not working sddm for session 2 (user) differed in two points:
working: Active=yes + State=active
not working: Active=no + State=online
The bug seems to be lot more complicated then we thought. It is a tripple bug combination. First of all a bug in Plasma 5.5.4 not closing the session properly.
2. A bug in systemd
3. A bug in sddm.
For now we decided to switch back to SDDM 0.11 which comes automatically as update and does not suffer from all these bugs. (actually called 0.13.1+really0.11)
Thanks for helping us analyzing the problem which allowed us to provide a fix
I’ve “upgraded” from 0.11 to 0.13.1+really0.11 and now have two “Kodi” entries in sddm (accidently started kodi after reboot because it was default) and loginctl now shows me two user sessions, one with state “closing”? And sddm as a session between the two user sessions?
susan@panther:~$ loginctl
SESSION UID USER SEAT
3 117 sddm seat0
2 1000 susan seat0
4 1000 susan seat0
3 sessions listed.
susan@panther:~$ loginctl show-session 2
Id=2
Name=susan
Timestamp=Fr 2016-04-08 17:32:19 CEST
TimestampMonotonic=28433463
VTNr=7
Display=:0
Remote=no
Service=sddm
Scope=session-2.scope
Leader=1304
Audit=2
Type=x11
Class=user
Active=no
State=closing
IdleHint=no
IdleSinceHint=0
IdleSinceHintMonotonic=0
susan@panther:~$ loginctl show-session 4
Id=4
Name=susan
Timestamp=Fr 2016-04-08 17:34:00 CEST
TimestampMonotonic=128237816
VTNr=7
Display=:0
Remote=no
Service=sddm
Desktop=KDE
Scope=session-4.scope
Leader=1677
Audit=4
Type=x11
Class=user
Active=yes
State=active
IdleHint=no
IdleSinceHint=0
IdleSinceHintMonotonic=0Apart from that everything seems to work…
That seems to be the bug in plasma that does not close this sessions.
But just to be sure you can figure out the culprit maybe with
loginctl session-status 2 for session 2 and
loginctl session-status 4 for session 4.
It should give you an status message which should provide the error which leads to those sessions to be left opened.
Session 2, the “closing” one:
[code]susan@panther:~$ loginctl session-status 2
2 - susan (1000)
Since: Fr 2016-04-08 17:32:19 CEST; 19min ago
Leader: 1304
Seat: seat0; vc7
Display: :0
Service: sddm; type x11; class user
State: closing
Unit: session-2.scope
├─1314 /usr/bin/kwalletd --pam-login 15 18 --nofork
└─1316 /usr/bin/kwalletd5 --pam-login 15 19
Apr 08 17:32:19 panther systemd[1]: Started Session 2 of user susan.
Apr 08 17:32:19 panther sddm-helper[1304]: pam_ck_connector(sddm:session): nox11 mode, ignoring PAM_TTY :0
Apr 08 17:32:19 panther sddm-helper[1304]: pam_kwallet(sddm:session): pam_kwallet: pam_sm_open_session
Apr 08 17:32:19 panther sddm-helper[1304]: pam_kwallet(sddm:session): pam_kwallet: final socket path: /tmp/kwall
Apr 08 17:32:19 panther sddm-helper[1304]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session
Apr 08 17:32:19 panther sddm-helper[1304]: pam_kwallet5(sddm:session): pam_kwallet5: final socket path: /tmp/kwa
Apr 08 17:32:47 panther pulseaudio[1469]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedeskto
…skipping…
2 - susan (1000)
Since: Fr 2016-04-08 17:32:19 CEST; 19min ago
Leader: 1304
Seat: seat0; vc7
Display: :0
Service: sddm; type x11; class user
State: closing
Unit: session-2.scope
├─1314 /usr/bin/kwalletd --pam-login 15 18 --nofork
└─1316 /usr/bin/kwalletd5 --pam-login 15 19
Apr 08 17:32:19 panther systemd[1]: Started Session 2 of user susan.
Apr 08 17:32:19 panther sddm-helper[1304]: pam_ck_connector(sddm:session): nox11 mode, ignoring PAM_TTY :0
Apr 08 17:32:19 panther sddm-helper[1304]: pam_kwallet(sddm:session): pam_kwallet: pam_sm_open_session
Apr 08 17:32:19 panther sddm-helper[1304]: pam_kwallet(sddm:session): pam_kwallet: final socket path: /tmp/kwall
Apr 08 17:32:19 panther sddm-helper[1304]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session
Apr 08 17:32:19 panther sddm-helper[1304]: pam_kwallet5(sddm:session): pam_kwallet5: final socket path: /tmp/kwa
Apr 08 17:32:47 panther pulseaudio[1469]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedeskto
~
[/code]
And session 4:
[code]susan@panther:~$ loginctl session-status 4
4 - susan (1000)
Since: Fr 2016-04-08 17:34:00 CEST; 19min ago
Leader: 1677 (sddm-helper)
Seat: seat0; vc7
Display: :0
Service: sddm; type x11; class user
Desktop: KDE
State: active
Unit: session-4.scope
├─1677 /usr/lib/x86_64-linux-gnu/sddm/sddm-helper --socket /tmp/sddm-auth1eb49268-6651-4b54-88
├─1683 /usr/bin/kwalletd --pam-login 15 18 --nofork
├─1685 /usr/bin/kwalletd5 --pam-login 15 19
├─1686 /usr/bin/ck-launch-session /usr/bin/dbus-launch --exit-with-session /usr/bin/im-launch
├─1741 dbus-launch --autolaunch=467a8ecd66e8bd1e057920fd5650b342 --binary-syntax --close-stder
├─1742 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
├─1747 /usr/bin/ssh-agent /usr/bin/gpg-agent --daemon --sh --write-env-file=/home/susan/.gnupg
├─1748 /usr/bin/gpg-agent --daemon --sh --write-env-file=/home/susan/.gnupg/gpg-agent-info-pan
├─1753 /bin/sh /usr/bin/startkde
├─1756 /usr/bin/dbus-launch --exit-with-session /usr/bin/im-launch /usr/bin/startkde
├─1757 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 15 --session
├─1803 /usr/lib/x86_64-linux-gnu/libexec/kf5/start_kdeinit --kded +kcminit_startup
├─1804 kdeinit5: Running…
├─1805 klauncher [kdeinit5] --fd=9
├─1807 kded5 [kdeinit5]
├─1817 kwrapper5 /usr/bin/ksmserver
├─1818 /usr/bin/ksmserver
├─1819 /usr/bin/kaccess
├─1823 /usr/bin/kglobalaccel5
├─1835 /usr/lib/telepathy/mission-control-5
├─1838 kwin_x11
├─1840 /usr/lib/dconf/dconf-service
├─1845 /usr/bin/baloo_file
├─1847 /usr/lib/x86_64-linux-gnu/libexec/kdeconnectd
├─1849 /usr/bin/krunner
├─1882 /usr/bin/kactivitymanagerd start-daemon
├─1883 /usr/lib/x86_64-linux-gnu/libexec/kf5/kscreen_backend_launcher
├─1887 /usr/bin/plasmashell --shut-up
├─1900 /usr/lib/x86_64-linux-gnu/libexec/polkit-kde-authentication-agent-1
├─1906 /usr/bin/xembedsniproxy
├─1909 /usr/bin/python3 /usr/share/gis-weather/gis-weather.py
├─1910 /usr/bin/quiterss
├─1913 /usr/bin/xscreensaver -no-splash
├─1914 /usr/bin/python3 /usr/bin/hp-systray -x
├─1921 /usr/bin/ksuperkey
├─1927 /usr/bin/pulseaudio --start --log-target=syslog
├─1932 /usr/bin/yakuake
├─1935 /usr/lib/at-spi2-core/at-spi-bus-launcher
├─1942 /usr/bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.conf --nofork --print-add
├─1944 /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session
├─1959 kdeinit4: kdeinit4 Running…
├─1960 /usr/bin/python3 /usr/bin/hp-systray -x
├─1961 /usr/bin/python3 /usr/bin/hp-systray -x
├─1964 kdeinit4: klauncher [kdeinit] --fd=
├─1967 kdeinit4: kded4 [kdeinit]
├─2000 /usr/lib/gvfs/gvfsd
├─2008 /bin/bash
├─2023 /usr/bin/knotify4
├─2026 ksysguardd
├─2043 /usr/bin/kuiserver5
├─2092 /bin/bash
├─2173 /usr/lib/thunderbird/thunderbird
├─2177 /usr/lib/x86_64-linux-gnu/gconf/gconfd-2
├─2197 /usr/lib/mozilla/kmozillahelper
├─2277 chromium-browser --ppapi-flash-path=/usr/lib/pepperflashplugin-nonfree/libpepflashplaye
├─2299 chromium-browser --type=zygote --ppapi-flash-path=/usr/lib/pepperflashplugin-nonfree/li
├─2301 chromium-browser --type=zygote --ppapi-flash-path=/usr/lib/pepperflashplugin-nonfree/li
├─2354 chromium-browser --type=gpu-process --channel=2277.0.1373315111 --window-depth=24 --sup
├─2365 chromium-browser --type=gpu-broker
├─2371 /usr/lib/chromium-browser/chromium-browser --type=renderer --enable-pinch --touch-event
├─2389 /usr/lib/chromium-browser/chromium-browser --type=renderer --enable-pinch --touch-event
├─2415 /usr/lib/chromium-browser/chromium-browser --type=renderer --enable-pinch --touch-event
├─2416 /usr/lib/chromium-browser/chromium-browser --type=renderer --enable-pinch --touch-event
├─2420 /usr/lib/chromium-browser/chromium-browser --type=renderer --enable-pinch --touch-event
├─2425 /usr/lib/chromium-browser/chromium-browser --type=renderer --enable-pinch --touch-event
├─2431 /usr/lib/chromium-browser/chromium-browser --type=renderer --enable-pinch --touch-event
├─2435 /usr/lib/chromium-browser/chromium-browser --type=renderer --enable-pinch --touch-event
├─2441 /usr/lib/chromium-browser/chromium-browser --type=renderer --enable-pinch --touch-event
├─2448 /usr/lib/chromium-browser/chromium-browser --type=renderer --enable-pinch --touch-event
├─2455 /usr/lib/chromium-browser/chromium-browser --type=renderer --enable-pinch --touch-event
├─2459 /usr/lib/chromium-browser/chromium-browser --type=renderer --enable-pinch --touch-event
├─2470 /usr/lib/chromium-browser/chromium-browser --type=renderer --enable-pinch --touch-event
├─2474 /usr/lib/chromium-browser/chromium-browser --type=renderer --enable-pinch --touch-event
├─2476 /usr/lib/chromium-browser/chromium-browser --type=renderer --enable-pinch --touch-event
├─2484 /usr/lib/chromium-browser/chromium-browser --type=renderer --enable-pinch --touch-event
├─2491 /usr/lib/chromium-browser/chromium-browser --type=renderer --enable-pinch --touch-event
├─2811 /usr/lib/chromium-browser/chromium-browser --type=renderer --enable-pinch --touch-event
├─3013 /usr/lib/chromium-browser/chromium-browser --type=renderer --enable-pinch --touch-event
├─3176 loginctl session-status 4
└─3177 pager
Apr 08 17:53:35 panther org.kde.KScreen[1757]: kscreen: Primary output changed from KScreen::Output(Id: 638 , Na
Apr 08 17:53:35 panther org.kde.KScreen[1757]: kscreen: Primary output changed from KScreen::Output(Id: 638 , Na
Apr 08 17:53:35 panther org.kde.KScreen[1757]: kscreen: Primary output changed from KScreen::Output(Id: 638 , Na
Apr 08 17:53:35 panther org.kde.KScreen[1757]: kscreen: Primary output changed from KScreen::Output(Id: 638 , Na
Apr 08 17:53:35 panther org.kde.KScreen[1757]: kscreen: Primary output changed from KScreen::Output(Id: 638 , Na
Apr 08 17:53:35 panther org.kde.KScreen[1757]: kscreen: Primary output changed from KScreen::Output(Id: 638 , Na
Apr 08 17:53:35 panther org.kde.KScreen[1757]: kscreen: Primary output changed from KScreen::Output(Id: 638 , Na
Apr 08 17:53:35 panther org.kde.KScreen[1757]: kscreen: Primary output changed from KScreen::Output(Id: 638 , Na
Apr 08 17:53:35 panther org.kde.KScreen[1757]: kscreen: Primary output changed from KScreen::Output(Id: 638 , Na
Apr 08 17:53:35 panther org.kde.KScreen[1757]: kscreen: Primary output changed from KScreen::Output(Id: 638 , Na
lines 71-100/100 (END)
[/code]
[/code]
And thats journal in case it matters
susan@panther:~$ journalctl -b -u sddm
-- Logs begin at Fr 2016-04-08 17:31:57 CEST, end at Fr 2016-04-08 17:57:59 CEST. --
Apr 08 17:32:06 panther systemd[1]: Started Simple Desktop Display Manager.
Apr 08 17:32:08 panther sddm-helper[1244]: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=
Apr 08 17:32:19 panther sddm-helper[1304]: pam_kwallet(sddm:auth): (null): pam_sm_authenticate
Apr 08 17:32:19 panther sddm-helper[1304]: pam_kwallet5(sddm:auth): (null): pam_sm_authenticate
Apr 08 17:32:19 panther sddm[1191]: Oops, secure memory pool already initialized
Apr 08 17:32:19 panther sddm-helper[1304]: pam_kwallet(sddm:setcred): pam_kwallet: pam_sm_setcred
Apr 08 17:32:19 panther sddm-helper[1304]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Apr 08 17:32:19 panther sddm-helper[1304]: pam_unix(sddm:session): session opened for user susan by (uid=0)
Apr 08 17:33:41 panther sddm-helper[1660]: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=
Apr 08 17:33:59 panther sddm-helper[1677]: pam_kwallet(sddm:auth): (null): pam_sm_authenticate
Apr 08 17:33:59 panther sddm-helper[1677]: pam_kwallet5(sddm:auth): (null): pam_sm_authenticate
Apr 08 17:33:59 panther sddm[1191]: Oops, secure memory pool already initialized
Apr 08 17:34:00 panther sddm-helper[1677]: pam_kwallet(sddm:setcred): pam_kwallet: pam_sm_setcred
Apr 08 17:34:00 panther sddm-helper[1677]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Apr 08 17:34:00 panther sddm-helper[1677]: pam_unix(sddm:session): session opened for user susan by (uid=0)Yeah like expected. Plasma unable to kill pulseaudio which leaves the session open.
If it does not provide any big problems. Leave it there as is.
Plasma 5.5.5 onwards fixes this issue.
Ok, so I’ll wait until the new Plasma version comes in…