Your message dated Thu, 11 Sep 2014 20:38:23 +0200
with message-id <20140911183823.gf13...@gnuservers.com.ar>
and subject line gdm3 blocks USR1
has caused the Debian Bug report #755761,
regarding gdm3: Unable to start KDE after last gdm3 upgrade
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.)
--
755761: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755761
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gdm3
Version: 3.12.2-2
Severity: critical
Justification: breaks unrelated software
After today's gdm3 upgrade on testing from 3.8 to 3.12, I'm unable to
sucessfully logon onto my KDE4 setup.
Here is what is happening here: after the gdm3 upgrade, if I try to start a KDE
session by logging in, KDE hangs at the startup screen. Only the "harddrive"
icon is shown. System remains responsive (can switch to VTs, can SSH in, mouse
pointer still moves...). If I launch a task manager (like htop), there are
about 3 "kdeinit4" process in a tree:
/usr/bin/kdeinit4 --oom-pipe 4 +kcminit_startup
CPU load during this hang remains at zero. There is no disk activity present.
For all effects the system sat there, idle.
After poking a bit those "hung" kdeinit4 processes with GDB, if I kill the one
with the following backtrace:
#0 0x00007f38346195c0 in __read_nocancel () at ../sysdeps/unix/syscall-
template.S:81
#1 0x00000000004070d5 in _start ()
....KDE resumes startup as usual (it's almost always the second-to-last kdeinit4
process in the tree). Another workaround is to switch to a different login
manager (be it kdm or LightDM), and in such case KDE starts up without
incident, but these aren't really good options to me as I like using GDM.
Yesterday's systemd-sysv update doesn't seem to be relevant to this case, as
the older version of gdm3 worked fine until today, when I received the faulty
upgrade.
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'testing-updates'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=es_VE.UTF-8, LC_CTYPE=es_VE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gdm3 depends on:
ii accountsservice 0.6.37-2
ii adduser 3.113+nmu3
ii dconf-cli 0.20.0-2
ii dconf-gsettings-backend 0.20.0-2
ii debconf [debconf-2.0] 1.5.53
ii gir1.2-gdm3 3.12.2-2
ii gnome-session [x-session-manager] 3.12.1-3
ii gnome-session-bin 3.12.1-3
ii gnome-session-flashback [x-session-manager] 3.8.0-3
ii gnome-settings-daemon 3.12.2-1
ii gnome-shell 3.12.2-3
ii gnome-terminal [x-terminal-emulator] 3.12.3-1
ii gsettings-desktop-schemas 3.12.2-1
ii kde-window-manager [x-window-manager] 4:4.11.9-1
ii konsole [x-terminal-emulator] 4:4.13.1-1
ii libaccountsservice0 0.6.37-2
ii libatk1.0-0 2.12.0-1
ii libaudit1 1:2.3.7-1
ii libc6 2.19-7
ii libcairo-gobject2 1.12.16-2
ii libcairo2 1.12.16-2
ii libcanberra-gtk3-0 0.30-2
ii libcanberra0 0.30-2
ii libgdk-pixbuf2.0-0 2.30.7-1
ii libgdm1 3.12.2-2
ii libglib2.0-0 2.40.0-3
ii libglib2.0-bin 2.40.0-3
ii libgtk-3-0 3.12.2-1+b1
ii libpam-modules 1.1.8-3
ii libpam-runtime 1.1.8-3
ii libpam-systemd 208-6
ii libpam0g 1.1.8-3
ii libpango-1.0-0 1.36.3-1
ii libpangocairo-1.0-0 1.36.3-1
ii librsvg2-common 2.40.2-1
ii libselinux1 2.3-1
ii libsystemd-daemon0 208-6
ii libsystemd-id128-0 208-6
ii libsystemd-journal0 208-6
ii libsystemd-login0 208-6
ii libwrap0 7.6.q-25
ii libx11-6 2:1.6.2-2
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 marco [x-window-manager] 1.8.1+dfsg1-1
ii mate-session-manager [x-session-manager] 1.8.1-4
ii mate-terminal [x-terminal-emulator] 1.8.0+dfsg1-3
ii metacity [x-window-manager] 1:2.34.13-1
ii policykit-1 0.105-6
ii ucf 3.0030
ii x11-common 1:7.7+7
ii x11-xserver-utils 7.7+3
ii xterm [x-terminal-emulator] 308-1
Versions of packages gdm3 recommends:
ii at-spi2-core 2.10.2-3
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.15.99.904-1
ii xserver-xorg 1:7.7+7
ii zenity 3.12.1-1
Versions of packages gdm3 suggests:
ii gnome-orca 3.12.1-1
ii libpam-gnome-keyring 3.8.2-2+b1
-- Configuration Files:
/etc/gdm3/greeter.gsettings [Errno 2] No existe el fichero o el directorio:
u'/etc/gdm3/greeter.gsettings'
-- debconf information:
* shared/default-x-display-manager: kdm
gdm3/daemon_name: /usr/sbin/gdm3
--- End Message ---
--- Begin Message ---
Version: 3.12.2-4
Hi,
kdeinit uses USR1 to comunicate with it's starting wrapper, the issue is fixed
in gdm3 with the patch d/p/04_really_dont_block_SIGUSR1.patch
Happy hacking,
--
"The most important thing in the programming language is the name. A language
will not succeed without a good name. I have recently invented a very good
name and now I am looking for a suitable language."
-- Donald Knuth
Saludos /\/\ /\ >< `/
signature.asc
Description: Digital signature
--- End Message ---
