Reply to topic

System Policy error after update

Bladeforce
Registered Member
Posts
26
Karma
0

System Policy error after update

Sat Sep 02, 2017 10:45 am
Hello , After updating to latest dev build i am getting an error on boot:
System policy prevents control of network connections and have to enter a password. I cant automount any internal drives anymore without entering a password and also cdemu (a program that uses dbus to mount cd images) cant autostart in the system tray with an error :
"Daemon autostart failed. Error:
g-dbus-error-quark: Error calling StartServiceByName for net.sf.cdemu.CDEmuDaemon: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process net.sf.cdemu.CDEmuDaemon exited with status 255 (25)"
This was working fine until yesterday so some update has borked this. Ive got polkit i'ds appearing all over the place when i had a fully working desktop yesterday
User avatar subdiff
Registered Member
Posts
59
Karma
0
OS

Re: System Policy error after update

Sat Sep 02, 2017 10:54 am
Thanks for posting. Glad I'm not the only one. Already tried quite some stuff. For any chance, does your sound not work as well and do you have only a dummy output in your Audio devices? I think it's the same problem, the desktop not being able to query all resources in time because of missing permissions.
Bladeforce
Registered Member
Posts
26
Karma
0

Re: System Policy error after update

Sat Sep 02, 2017 11:33 am
Hello, Strangely enough my audio is working fine but auto mounting requires a password and i cant use cdemu anymore because it wont create a virtual device anymore.
User avatar subdiff
Registered Member
Posts
59
Karma
0
OS

Re: System Policy error after update

Sat Sep 02, 2017 11:54 am
The problem might be a recent change to sddm's seat management: https://build.neon.kde.org/job/xenial_u ... dm/changes

If you execute `loginctl list-sessions` it doesn't show you a seat number to the active session, correct?
Bladeforce
Registered Member
Posts
26
Karma
0

Re: System Policy error after update

Sat Sep 02, 2017 12:07 pm
Thats is correct yes there is no SEAT number in the active session
User avatar subdiff
Registered Member
Posts
59
Karma
0
OS
The error is somewhere in the changes recently pushed to seat handling in sddm:
https://github.com/sddm/sddm/commit/ae7 ... 60fb09b539
I hope David can soon fix it.

As a workaround for the time being you can install the stable branch sddm deb: http://archive.neon.kde.org/dev/stable/ ... in/s/sddm/

But when you do a system upgrade afterwards, it will again go back to the unstable sddm. You can somehow exclude a package from upgrading with apt. But not sure if it's worthwhile or just wait afterwards with future updates until the problem is fixed (you could also update after installing the deb and then install back the deb).
User avatar acheronuk
KDE Developer
Posts
94
Karma
2
sddm_0.15.0+p16.04+git20170902.1633-0 should hopefully fix some or all these issues when available.
User avatar subdiff
Registered Member
Posts
59
Karma
0
OS
Fixed it for me as well. Just do a normal update and you get the new version.
Bladeforce
Registered Member
Posts
26
Karma
0
Hi, I can confirm the latest git of sddm fixed all my issues. Thank you very much KDE developers

 
Reply to topic

Bookmarks



Who is online

Registered users: Baidu [Spider], Bing [Bot], BobF, Google [Bot], MSN [Bot], Sogou [Bot], Zeikcied