Your message dated Mon, 08 Jun 2015 11:51:28 +0100 with message-id <[email protected]> and subject line Re: Bug#767388: bug seems fixed with gdm3 3.14.1-7 has caused the Debian Bug report #767388, regarding gdm3: (with default=kdm) gdm.service gives failed status 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 [email protected] immediately.) -- 767388: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767388 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: gdm3 Version: 3.14.0-1 Severity: minor Dear Maintainer, I have kdm as default display manager. Systemd starts gdm.service, which contains an ExecStartPre assertion default=gdm that fails giving a failure log and a failure status. I do not know if this is a bug or a feature, nor if I should report this to kdm, but in my mind having a programmatic failure in a normal situation should not be normal... Thanks for your time ric # cat /etc/X11/default-display-manager /usr/bin/kdm # systemctl status gdm.service ● gdm.service - GNOME Display Manager Loaded: loaded (/lib/systemd/system/gdm.service; static) Active: failed (Result: start-limit) since Thu 2014-10-30 09:19:36 CET; 10h ago Process: 1145 ExecStartPre=/bin/sh -c [ "$(cat /etc/X11/default-display-manager 2>/dev/null)" = "/usr/sbin/gdm3" ] (code=exited, status=1/FAILURE) Oct 30 09:19:35 IPhT-IA-004976 systemd[1]: Failed to start GNOME Display Manager. Oct 30 09:19:35 IPhT-IA-004976 systemd[1]: Unit gdm.service entered failed state. Oct 30 09:19:36 IPhT-IA-004976 systemd[1]: gdm.service start request repeated too quickly, refusing to start. Oct 30 09:19:36 IPhT-IA-004976 systemd[1]: Failed to start GNOME Display Manager. Oct 30 09:19:36 IPhT-IA-004976 systemd[1]: Unit gdm.service entered failed state. Warning: Unit file changed on disk, 'systemctl daemon-reload' recommended. # systemctl status kdm.service ● kdm.service - LSB: X display manager for KDE Loaded: loaded (/etc/init.d/kdm) Drop-In: /run/systemd/generator/kdm.service.d └─50-kdm-$x-display-manager.conf Active: active (running) since Thu 2014-10-30 09:19:31 CET; 10h ago Process: 1039 ExecStart=/etc/init.d/kdm start (code=exited, status=0/SUCCESS) CGroup: /system.slice/kdm.service ├─1057 /usr/bin/kdm -config /var/run/kdm/kdmrc └─1062 /usr/bin/X :0 vt7 -br -nolisten tcp -auth /var/run/xauth/A:0-mwU3Gb Oct 30 09:19:31 IPhT-IA-004976 kdm[1039]: Starting K Display Manager: kdm. Oct 30 09:19:36 IPhT-IA-004976 kdm_greet[1072]: Cannot load /usr/share/kde4/apps/kdm/faces/.default.face: No ...tory Oct 30 09:19:49 IPhT-IA-004976 kdm[1070]: :0[1070]: pam_unix(kdm:session): session opened for user guida by (uid=0) Hint: Some lines were ellipsized, use -l to show in full. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gdm3 depends on: ii accountsservice 0.6.37-3+b1 ii adduser 3.113+nmu3 ii dconf-cli 0.22.0-1 ii dconf-gsettings-backend 0.22.0-1 ii debconf [debconf-2.0] 1.5.53 ii gir1.2-gdm3 3.14.0-1 ii gnome-session [x-session-manager] 3.14.0-2 ii gnome-session-bin 3.14.0-2 ii gnome-session-flashback [x-session-manager] 3.8.1-4 ii gnome-settings-daemon 3.14.0-2 ii gnome-shell 3.14.0-1 ii gnome-terminal [x-terminal-emulator] 3.14.0-1 ii gsettings-desktop-schemas 3.14.0-1 ii kde-window-manager [x-window-manager] 4:4.11.12-2+b1 ii konsole [x-terminal-emulator] 4:4.14.1-1 ii libaccountsservice0 0.6.37-3+b1 ii libaudit1 1:2.4-1 ii libc6 2.19-11 ii libcanberra-gtk3-0 0.30-2.1 ii libcanberra0 0.30-2.1 ii libgdk-pixbuf2.0-0 2.31.1-2+b1 ii libgdm1 3.14.0-1 ii libglib2.0-0 2.42.0-2 ii libglib2.0-bin 2.42.0-2 ii libgtk-3-0 3.14.3-1 ii libpam-modules 1.1.8-3.1 ii libpam-runtime 1.1.8-3.1 ii libpam-systemd 215-5+b1 ii libpam0g 1.1.8-3.1 ii librsvg2-common 2.40.5-1 ii libselinux1 2.3-2 ii libsystemd0 215-5+b1 ii libwrap0 7.6.q-25 ii libx11-6 2:1.6.2-3 ii libxau6 1:1.0.8-1 ii libxdmcp6 1:1.1.1-1 ii libxrandr2 2:1.4.2-1 ii lsb-base 4.1+Debian13 ii metacity [x-window-manager] 1:3.12.0-2 ii policykit-1 0.105-7 ii ucf 3.0030 ii x11-common 1:7.7+7 ii x11-xserver-utils 7.7+3 ii xterm [x-terminal-emulator] 312-1 Versions of packages gdm3 recommends: ii at-spi2-core 2.14.0-1 ii desktop-base 7.0.3 ii gnome-icon-theme 3.12.0-1 ii gnome-icon-theme-symbolic 3.12.0-1 ii x11-xkb-utils 7.7+1 ii xserver-xephyr 2:1.16.1-1 ii xserver-xorg 1:7.7+7 ii zenity 3.14.0-1 Versions of packages gdm3 suggests: ii gnome-orca 3.14.0-1 ii libpam-gnome-keyring 3.14.0-1+b1 -- debconf information: gdm3/daemon_name: /usr/sbin/gdm3 * shared/default-x-display-manager: kdm
--- End Message ---
--- Begin Message ---Version: 3.14.1-7 On 08/06/15 09:50, [email protected] wrote: > the bug seems fixed at least after my last full-upgrade from testing: gdm3 > 3.14.1-7 (and kdm 4:4.11.13-2): Closing it as fixed in that version.
--- End Message ---
