Your message dated Mon, 01 Apr 2013 00:35:18 +0200
with message-id <5158ba26.9020...@debian.org>
and subject line Re: Bug#704423: systemd: gdm does not start, user sessions
have multiple issues, root session works normally
has caused the Debian Bug report #704423,
regarding systemd: gdm does not start, user sessions have multiple issues, root
session works normally
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
704423: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704423
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 44-11
Severity: grave
Justification: renders package unusable
Dear Maintainer,
***I'm marking this as grave because it causes some fairly serious usability
issues for me, if you feel this status is incorrect please feel free to change
it.***
As you might know, much of GNOME 3.8 has landed in Experimental recently,
certainly enough to run a GNOME 3.8 environment at least.
GNOME 3.8, or, more specifically, gnome-settings-daemon 3.8, depends on systemd
for a number of things, most notably the power manager plugin (requires
systemd-logind to be running), leaving me without a power status indicator in
GNOME Shell when using sysvinit.
As I am operating on a laptop, having this indicator is most definitely
desired, so I decided to switch my init system to systemd.
This is where things go wrong.
Firstly, after the initial boot phase is complete, when the desktop manager
(GDM) is supposed to start, it doesn't. Xorg appears to start fine, and I get
the busy cursor for a short while as the system seems to be loading, then the
cursor changes to the normal pointer and nothing further happens.
So I drop to a tty, and log in to my personal account. That's when I get these
two messages:
-su: /dev/cgroup/cpu/user/2866/tasks: No such file or directory
-su: /dev/cgroup/cpu/user/2866/notify_on_release: No such file or directory
Already this does not bode well for me.
Next, I stop GDM, kill Xorg (for some reason it doesn't quit when GDM is
stopped), and start an X session. It takes a few moments, but eventually
everything loads and I'm in GNOME Shell. This is when I discover that things
aren't working as I would expect them to. The entire environment is very laggy,
cursor movements stutter, my audio doesn't work (PulseAudio shows my audio as
Dummy Output), the network status indicator doesn't show my network connection
status or show a list of nearby networks (or even the Network Settings menu
option, nothing at all pops up) when clicked on, and when checking the Graphics
information in the Details applet of GNOME Control Center, I see that it's
using Gallium 0.4 on llvmpipe (LLVM 0x209) when it should be using my Intel
integrated graphics (this probably accounts for the lag and stutters).
I do get my power status indicator back, however, my graphical user session
basically just doesn't work properly.
So I close the session and logout, log in as root, and start an X session.
Everything works as I would expect. The environment operates smoothly, I have
sound, my graphics adapter is detected properly (Mobile Intel® GM45 Express
Chipset), I have my power status indicator, the network status icon reflects my
connected status and shows the nearby networks. It all works!
So now I'm wondering... Maybe it's a problem with my personal user account?
I create a brand new user account, log in as that user (and get two similar
messages as when I logged into my personal account), and start an X session. It
suffers the same problems as my personal user account.
Now I have no idea what's going on, so I decide to file this bug report and
hopefully get some ideas of what to do to determine what's going wrong and why,
and possibly how to fix it all.
All this, because I wanted my power status indicator back, because it doesn't
show up when using sysvinit. Everything else seems to work just fine, but that
indicator is missing and it bothered me that much.
(I will note that I discovered that starting systemd-logind manually when using
sysvinit, then killing and restarting gnome-settings-daemon does give me back
the power status indicator without any other complications, however, this is
not an ideal solution.)
You'll have to forgive me for this lengthy report. I really wasn't sure how
else to get everything across accurately.
-- System Information:
Debian Release: 7.0
APT prefers experimental
APT policy: (650, 'experimental'), (650, 'unstable'), (600, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.8-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages systemd depends on:
ii dpkg 1.16.10
ii initscripts 2.88dsf-41
ii libacl1 2.2.51-8
ii libaudit0 1:1.7.18-1.1
ii libc6 2.17-0experimental2
ii libcap2 1:2.22-1.2
ii libcryptsetup4 2:1.4.3-4
ii libdbus-1-3 1.6.8-1
ii libkmod2 9-2
ii liblzma5 5.1.1alpha+20120614-2
ii libpam0g 1.1.3-9
ii libselinux1 2.1.12-1
ii libsystemd-daemon0 44-11
ii libsystemd-id128-0 44-11
ii libsystemd-journal0 44-11
ii libsystemd-login0 44-11
ii libudev0 175-7.1
ii libwrap0 7.6.q-24
ii udev 175-7.1
ii util-linux 2.20.1-5.3
Versions of packages systemd recommends:
pn libpam-systemd <none>
Versions of packages systemd suggests:
ii python 2.7.3-13
ii python-cairo 1.8.8-1+b2
ii python-dbus 1.1.1-1
ii systemd-gui 44-11
-- no debconf information
--- End Message ---
--- Begin Message ---
Am 01.04.2013 00:26, schrieb Alex Vanderpol:
> ...Wow, I feel really dumb right now. That was all it took to get things
> working.
>
> Thank you so much!
>
> (I have to wonder now, though... if that package is necessary to make
> things work properly, why isn't a dependency of the package?)
We've been considering that, actually.
Thing is, you can run systemd without libpam-systemd.
libpam-systemd is only relevant if you are using logind, which is mostly
interesting for multi-user or graphical setups.
Michael
(Closing the bug report)
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
