Bug#785782: Issue re-sighted: gdm3 starts but no login prompt after fresh installs
I have a sighting of this. Interested in helping to diagnose it... but someone more expert than I about PAM and systemd etc will have to tell me what to type to generate any useful logging! In fact I realise I've seen it twice now: a few weeks ago I was using the 32bit Debian9 installer to nuke the HD on an old long unused Thinkpad T22 I was giving away. Out of interest I thought I'd do a whole install. When gdm3 didn't come up with anything but the dark-grey textured "wallpaper" (but no dialog prompting for who's logging in) I thought the ageing Thinkpad's graphics HW just couldn't cope and switched to lightdm, which worked fine. With hindsight I realize it was probably this issue. And now just this morning I'm doing a 64bit Debian9 install on a shiny new 7700K system. And see the same problem. A bit of googling led to this issue. FWIW, a few things: Output of systemctl status gdm3: gdm.service - GNOME Display Manager Loaded: loaded (/lib/systemd/system/gdm.service; static; vendor preset: enabled) Active: active (running) since Tue 2017-09-26 15:18:54 BST; 11min ago Process: 916 ExecStartPre=/usr/share/gdm/generate-config (code=exited, status=0/SUCCESS) Process: 912 ExecStartPre=/bin/sh -c [ "$(cat /etc/X11/default-display-manager 2>/dev/null)" = "/usr/sbin/gdm3" ] (code=exited, status=0/SUCCESS) Main PID: 925 (gdm3) Tasks: 3 (limit: 4915) CGroup: /system.slice/gdm.service └─925 /usr/sbin/gdm3 Sep 26 15:18:54 everest systemd[1]: Starting GNOME Display Manager... Sep 26 15:18:54 everest systemd[1]: Started GNOME Display Manager. Sep 26 15:18:54 everest gdm-launch-environment][932]: pam_unix(gdm-launch-environment:session): session opened for user Debian-gdm by (uid=0) Tail end of /var/log/syslog after boot: Sep 26 15:34:25 everest systemd[1]: Started Network Manager Wait Online. Sep 26 15:34:25 everest systemd[1]: Reached target Network is Online. Sep 26 15:34:25 everest systemd[1]: apt-daily.timer: Adding 1h 17min 31.447421s random time. Sep 26 15:34:25 everest systemd[1]: Started Daily apt download activities. Sep 26 15:34:25 everest systemd[1]: apt-daily-upgrade.timer: Adding 29min 15.620376s random time. Sep 26 15:34:25 everest systemd[1]: Started Daily apt upgrade and clean activities. Sep 26 15:34:25 everest systemd[1]: Reached target Timers. Sep 26 15:34:25 everest systemd[1]: Starting keep memory of all UPnP devices that announced themselves... Sep 26 15:34:25 everest systemd[1]: Started keep memory of all UPnP devices that announced themselves. Sep 26 15:34:25 everest systemd[1]: Reached target Multi-User System. Sep 26 15:34:25 everest systemd[1]: Reached target Graphical Interface. Sep 26 15:34:25 everest systemd[1]: Starting Update UTMP about System Runlevel Changes... Sep 26 15:34:25 everest systemd[1]: Started Update UTMP about System Runlevel Changes. Sep 26 15:34:25 everest systemd[1]: Startup finished in 2.818s (kernel) + 9.195s (userspace) = 12.014s. Sep 26 15:34:47 everest systemd-timesyncd[529]: Synchronized to time server 176.58.109.199:123 (2.debian.pool.ntp.org). Sep 26 15:35:33 everest systemd[1]: Created slice User Slice of local. Sep 26 15:35:33 everest systemd[1]: Starting User Manager for UID 1000... Sep 26 15:35:33 everest systemd[1]: Started Session 2 of user local. Sep 26 15:35:33 everest systemd[856]: Reached target Paths. Sep 26 15:35:33 everest systemd[856]: Listening on GnuPG cryptographic agent (access for web browsers). Sep 26 15:35:33 everest systemd[856]: Listening on GnuPG cryptographic agent (ssh-agent emulation). Sep 26 15:35:33 everest systemd[856]: Listening on GnuPG cryptographic agent and passphrase cache. Sep 26 15:35:33 everest systemd[856]: Reached target Timers. Sep 26 15:35:33 everest systemd[856]: Starting D-Bus User Message Bus Socket. Sep 26 15:35:33 everest systemd[856]: Listening on GnuPG cryptographic agent and passphrase cache (restricted). Sep 26 15:35:33 everest systemd[856]: Listening on D-Bus User Message Bus Socket. Sep 26 15:35:33 everest systemd[856]: Reached target Sockets. Sep 26 15:35:33 everest systemd[856]: Reached target Basic System. Sep 26 15:35:33 everest systemd[856]: Reached target Default. Sep 26 15:35:33 everest systemd[856]: Startup finished in 10ms. Sep 26 15:35:33 everest systemd[1]: Started User Manager for UID 1000. And then after a systemctl restart gdm3: Sep 26 15:37:49 everest systemd[1]: Stopping GNOME Display Manager... Sep 26 15:37:49 everest gnome-shell[671]: Connection to xwayland lost Sep 26 15:37:49 everest org.a11y.atspi.Registry[707]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":1024" Sep 26 15:37:49 everest org.a11y.atspi.Registry[707]: after 21 requests (21 known processed) with 0 events remaining. Sep 26 15:37:49 everest kernel: [ 216.033849] traps: gnome-shell[671] trap int3 ip:7f8f62c41261 sp:7ffd06d36bb0 error:0 Sep 26 15:37:49 everest kernel: [ 216.033861] in libglib-2.0.so.0.5000.3[7f8f62bf1000+112000] Sep 26 15:37:49 everes
Bug#785782: False sighting (will re-close) - problem was actually an invisible primary display
OK it turned out the gmd3 login prompt dialog wasn't actually absent... the issue was due to my install actually thinking the machine had two heads, when it didn't (7700K i7; CPU's integrated graphics on an Asrock H270 Pro4 mobo, one monitor attached to VGA port... but the freshly installed system seemed to think there was a monitor on one on the other ports too). The dialog was presumably on the invisible-to-me display. On closer inspection I could slide the mouse off the left hand side of the screen I could see. I think lightdm appeared to work better as it has he login dialog follow the mouse from screen to screen (maybe gdm3 would be improved by such behaviour; couldn't see anything in its config to select anything like that though). Anyway, the two screens issue became apparent when I looked closer at the desktop lightdm was logging me into and I was obviously looking at the secondary screen of a primary+secondary pair. Reconfiguring displays (usual right click on desktop) to be just a single primary on the desktop I do have worked good. The trick was then to copy the logged in user's .config/monitors.xml over to where gdm3 could use it: sudo cp .config/monitors.xml /var/lib/gdm3/.config/ sudo chown Debian-gdm:Debian-gdm /var/lib/gdm3/.config/monitors.xml And after a dpkg-reconfigure gdm3 and selecting it as the login manager, and a system restart, I'm seeing the expected gdm3 login prompt. Phew! (Makes me wonder if the Thinkpad I also ran into this on had the same problem.) Will send a separate control email to re-close this issue.
Bug#527165: xserver-xorg-video-sunffb: X fails to start on Creator3D graphics
Just a note confirming reverting to xserver-xorg-core_2%3a1.4.2-10_sparc.deb restored X11 via sunffb. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#386773: Is this bug blocking migration of 2.6.17 prebuilt modules into testing ?
There seem to be prebuilt modules for 2.6.17 in sid ready to migrate into testing, at least according to the "Why is package X not in testing yet?" page, but the way I read it they're being blocked by a release critical bug on nvidia-graphics-legacy-modules-i386, which is presumably this grave severity one (but there's a bunch of other reasons there too and I still don't entirely understand the rules; maybe there's the remainder of the wait period still to run too). Anyway, since the availability of the 2.6.17 prebuilts presumably fixes this, can someone mark it fixed or downgrade it or whatever it takes to unblock things ? [Nvidia legacy for 2.6.16 was a dud by the way... see discussions on the testing mail list around 18th-20th August 2006]. Tim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#386773: Is this bug blocking migration of 2.6.17 prebuilt modules into testing ?
On Sun, 2006-09-24 at 05:43 -0700, Steve Langasek wrote: > On Sun, Sep 24, 2006 at 12:38:46PM +0100, Tim Day wrote: > > [A load of nonsense about > > nvidia-kernel-legacy-2.6.17 packages > > deleted] > > nvidia-graphics-drivers-legacy (1.0.7174-4 to 1.0.7184-2) > Maintainer: Randall Donald > Section: non-free/x11 > Too young, only 2 of 10 days old > nvidia-glx-legacy/i386 unsatisfiable Depends: > nvidia-kernel-legacy-1.0.7184 > nvidia-glx-legacy/amd64 unsatisfiable Depends: > nvidia-kernel-legacy-1.0.7184 > nvidia-glx-legacy-ia32/amd64 unsatisfiable Depends: > nvidia-kernel-legacy-1.0.7184 > nvidia-glx-legacy-dev (i386, amd64) is buggy! (1 > 0) > nvidia-graphics-drivers-legacy (source) is buggy! (1 > 0) > Not considered > > There are two missing bugs, and three unsatisfiable dependencies. Where are > you seeing prebuilt modules that are compatible with this version? Oooops sorry didn't notice that the nvidia-kernel-legacy-2.6.17* packages in unstable are only built off the 1.0.7182 Nvidia release, but the nvidia-glx-legacy already in testing is 1.0.7184. Doh. Tim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
