[opensuse-factory] snapshot 20151012 problems
Since todays snapshot zypper dup KDE hangs showing only the wallpaper. Systemctl shows that polkit and udisks2.service did not load. They failed because the control process exited with error code=exited, status= 127 One time i waited 15 min or so and then KDE Started fully. But i could not reproduce this success... Killing the wallpaper-only Session results in a black screen instead of reloading KDE... extra-repos enabled are only packman and one for font rendering. Anybody else seeing this? Sugesstions? I do not know how to post a full log without a desktop ... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Thursday, October 15, 2015 08:49:11 PM Thomas Langkamp wrote:
Since todays snapshot zypper dup KDE hangs showing only the wallpaper. Systemctl shows that polkit and udisks2.service did not load. They failed because the control process exited with error code=exited, status= 127
One time i waited 15 min or so and then KDE Started fully. But i could not reproduce this success... Killing the wallpaper-only Session results in a black screen instead of reloading KDE... extra-repos enabled are only packman and one for font rendering.
Anybody else seeing this? Sugesstions?
I do not know how to post a full log without a desktop ...
I filed a bug where the desktop would inevitably crash either after a period of time, or soon after opening Flash-based videos. https://bugzilla.opensuse.org/show_bug.cgi?id=947028 Could they be related?
On Thu, Oct 15, 2015 at 08:49:11PM +0200, Thomas Langkamp wrote:
Since todays snapshot zypper dup KDE hangs showing only the wallpaper. Systemctl shows that polkit and udisks2.service did not load. They failed because the control process exited with error code=exited, status= 127
Something like this keeps happening to me for about a week. Apparently the problem is something crashing on KDE session start and KDE trying to show dr_konqui which has no chance to show at the moment. Killing the dr_konqui process unblocks the session. I'll need to check if the KDE_DEBUG variable still works so that I can see what crashes and why. Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hello, Am Donnerstag, 15. Oktober 2015 schrieb Thomas Langkamp:
Since todays snapshot zypper dup KDE hangs showing only the wallpaper. Systemctl shows that polkit and udisks2.service did not load. They failed because the control process exited with error code=exited, status= 127
127 is the typical exitcode for "command not found". Does the log show any indication if/what could be missing? Regards, Christian Boltz -- <dragotin> yes, so whenever you have the feeling a booster is disturbing your work, beat him up and than tell me and I do it even harder <dragotin> ...except if its me ;_) <suseROCKs> dragotin, you hae to promise to videotape that! [from #opensuse-project] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 16.10.2015 um 13:38 schrieb Christian Boltz:
Hello,
Am Donnerstag, 15. Oktober 2015 schrieb Thomas Langkamp:
Since todays snapshot zypper dup KDE hangs showing only the wallpaper. Systemctl shows that polkit and udisks2.service did not load. They failed because the control process exited with error code=exited, status= 127
127 is the typical exitcode for "command not found". Does the log show any indication if/what could be missing?
Regards,
Christian Boltz
thanks for the hint so far I tried disabling all non-standard repo and also with a new user, to no avail. I also tried IceWM, which does come up, but then is not able to start e.g. firefox systemctl status polkit.service says something about "polkit.service failed because controll process excited with error code" for udisks2 it says that polkit is missing, so the first problem seems to be with polkit if I try systemctl start polkit.service it says something about a "qdbus-error-quark 20" during boot I also saw "systemd-udevd[251]:invalid key/value pair in file /usr/lib/udev maybe you can make sense about something of this. Otherwise I will have to try a fresh installation. thx, tomme -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (4)
-
Chan Ju Ping -
Christian Boltz -
Michal Kubecek -
Thomas Langkamp