Re: Which package to file plasma startup bugreport against?
Hi Scott,
thanks for your prompt response.
On Sunday, January 10, 2016, 16:01:56 Scott Kitterman wrote:
> On Saturday, January 09, 2016 01:44:09 PM Peter Pöschl wrote:
> > what is the proper package to file a burgreport regarding the plasma
> > desktop startup?
> >
> > On an amd64 system running Testing, when I hit Enter on the password entry
> >
> > of the sddm login screen (Elarun theme) one of 3 things happen:
> > 1) probability about 50 %:
> > * login screen stays, progress bar goes to 100 %.
> > * login screen fades into a black screen, i.e. *no working desktop*.
> >
> > On this screen, a krusader window is running, started via Autostart.
> > I can start a separate konsole window from krusader and
> > other GUI-programs, e.g. iceweasel, from the shell.
> >
> > * Alt-Ctrl-Del gives me a popup to logout.
> > * re-login then usually works, but I had one case where I had to
> >
> > repeat the logout/login again.
> >
> > 2) probability about 50 %:
> > * screen turns completely black.
> > * login screen re-appears, progress bar now at 100 %.
> > * login screen fades into desktop screen, everything works fine.
> >
> > 3) probability small:
> > * login screen stays, progress bar goes to 100 %.
> > * login screen fades into desktop screen, everything works fine.
> >
> > What additional data should I add to provide a meaningful bugreport?
> > P.S.: Please keep me on CC, as I am not subscribed on the list.
>
> Make sure you have sddm 0.13 which recently transitioned to testing
> installed. It also brings a Recommends on libpam-systemd (for systemd users
> - that being the default) which you also want. Those two together are
> expected to resolve some issue that had symptoms similar to yours.
I have now updated to
ii cgmanager 0.39-2 amd64
ii libpam-systemd:amd64 228-4 amd64
ii sddm 0.13.0-1 amd64
ii sddm-theme-elarun 0.13.0-1 all
ii systemd 228-4 amd64
The probability of 3) may have risen, but today I have seen 1) again.
----- 'journalctl -xe' has this
Jan 20 20:04:01 Gehenna kernel: [ 15.206227] Adjusting tsc more than 11%
(5285504 vs 5285151)
Jan 20 20:04:14 Gehenna org.freedesktop.systemd1[1745]: ** (process:1778):
WARNING **: Could not connect to cgmanager: Could not connect: No such file or
directory
Jan 20 20:04:14 Gehenna org.freedesktop.systemd1[1745]: ** (process:1778):
CRITICAL **: Unable to acquire bus name 'org.freedesktop.systemd1'. Quitting.
Jan 20 20:05:06 Gehenna org.kde.kglobalaccel[1745]: The X11 connection broke
(error 1). Did the X11 server die?
Jan 20 20:05:13 Gehenna org.freedesktop.systemd1[2155]: ** (process:2188):
WARNING **: Could not connect to cgmanager: Could not connect: No such file or
directory
Jan 20 20:05:13 Gehenna org.freedesktop.systemd1[2155]: ** (process:2188):
CRITICAL **: Unable to acquire bus name 'org.freedesktop.systemd1'. Quitting.
-----
The lines starting at 20:05:06 are IMO related to the logout/re-login after a
bad desktop following login. In prior logs I only see the two lines after
20:04:14.
What can I do to get you better data to diagnose the problem?
Regards,
Peter Pöschl
Reply to: