After locking the screen and attempting to move the mouse or pressing a key, the screen just flickers and returns back to black. Further investigation showed that gnome-screensaver is trying to execute /usr/libexec/gnome-screensaver-dialog which then immediately segfaults. The desktop locked down from that point and can only be recovered by killing gnome-screensaver from another terminal. Reproducible: Always Steps to Reproduce: 1. Lock the gnome shell screen 2. Move the mouse Actual Results: Screen flickers and returns to black Expected Results: Unlock dialog appears Here's a gdb trace if I just run /usr/libexec/gnome-screensaver-dialog from a terminal: $ gdb -q /usr/libexec/gnome-screensaver-dialog Reading symbols from /usr/libexec/gnome-screensaver-dialog...Reading symbols from /usr/lib64/debug/usr/libexec/gnome-screensaver-dialog.debug...done. done. (gdb) run Starting program: /usr/libexec/gnome-screensaver-dialog [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". (gnome-screensaver-dialog:5917): GLib-GObject-WARNING **: cannot register existing type `GdkWindow' (gnome-screensaver-dialog:5917): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed Program received signal SIGSEGV, Segmentation fault. 0x00007ffff7147822 in _gdk_windowing_window_init () from /usr/lib64/libgdk-x11-2.0.so.0 (gdb) where #0 0x00007ffff7147822 in _gdk_windowing_window_init () from /usr/lib64/libgdk-x11-2.0.so.0 #1 0x00007ffff713f062 in _gdk_x11_screen_new () from /usr/lib64/libgdk-x11-2.0.so.0 #2 0x00007ffff712776a in gdk_display_open () from /usr/lib64/libgdk-x11-2.0.so.0 #3 0x00007ffff70f4c2d in gdk_display_open_default_libgtk_only () from /usr/lib64/libgdk-x11-2.0.so.0 #4 0x00007ffff79051c6 in post_parse_hook () from /usr/lib64/libgtk-3.so.0 #5 0x00007ffff5af5b1c in g_option_context_parse () from /usr/lib64/libglib-2.0.so.0 #6 0x00007ffff7904ef6 in gtk_init_with_args () from /usr/lib64/libgtk-3.so.0 #7 0x00000000004082ba in main (argc=1, argv=0x7fffffffda08) at gnome-screensaver-dialog.c:577 Here's my emerge --info: Portage 2.1.10.22 (default/linux/amd64/10.0, gcc-4.5.3, glibc-2.13-r4, 2.6.36-tuxonice x86_64) ================================================================= System uname: Linux-2.6.36-tuxonice-x86_64-Intel-R-_Core-TM-_i7_CPU_M_620_@_2.67GHz-with-gentoo-2.1 Timestamp of tree: Tue, 31 Jan 2012 19:00:01 +0000 app-shells/bash: 4.2_p20::<unknown repository> dev-java/java-config: 2.1.11-r3::<unknown repository> dev-lang/python: 2.6.7-r2::<unknown repository>, 2.7.2-r3::<unknown repository>, 3.1.4-r3::<unknown repository>, 3.2.2::<unknown repository> dev-util/cmake: 2.8.5-r2::<unknown repository> dev-util/pkgconfig: 0.26::<unknown repository> sys-apps/baselayout: 2.1::<unknown repository> sys-apps/openrc: 0.9.8.4::<unknown repository> sys-apps/sandbox: 2.5::<unknown repository> sys-devel/autoconf: 2.13::<unknown repository>, 2.68 sys-devel/automake: 1.9.6-r3, 1.10.3::<unknown repository>, 1.11.1-r1::<unknown repository> sys-devel/binutils: 2.22-r1::<unknown repository> sys-devel/gcc: 4.4.5, 4.5.3-r2::<unknown repository> sys-devel/gcc-config: 1.4.1-r1::<unknown repository> sys-devel/libtool: 2.4.2::<unknown repository> sys-devel/make: 3.82-r3::<unknown repository> sys-kernel/linux-headers: 2.6.39::<unknown repository> (virtual/os-headers) sys-libs/glibc: 2.13-r4::<unknown repository> Repositories: gentoo ACCEPT_KEYWORDS="amd64 ~amd64" ACCEPT_LICENSE="* -@EULA" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-Os -pipe -march=native" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/share/config /usr/share/gnupg/qualified.txt" CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/php/apache2-php5.3/ext-active/ /etc/php/apache2-php5.4/ext-active/ /etc/php/cgi-php5.3/ext-active/ /etc/php/cgi-php5.4/ext-active/ /etc/php/cli-php5.3/ext-active/ /etc/php/cli-php5.4/ext-active/ /etc/revdep-rebuild /etc/sandbox.d /etc/splash /etc/terminfo /etc/texmf/language.dat.d /etc/texmf/language.def.d /etc/texmf/updmap.d /etc/texmf/web2c" CXXFLAGS="-Os -pipe -march=native" DISTDIR="/usr/portage/distfiles" FEATURES="assume-digests binpkg-logs distlocks ebuild-locks fixlafiles fixpackages news parallel-fetch protect-owned sandbox sfperms splitdebug strict unknown-features-warn unmerge-logs unmerge-orphans userfetch" FFLAGS="" GENTOO_MIRRORS="http://mirror.switch.ch/ftp/mirror/gentoo/ " LANG="en_US.UTF-8" LDFLAGS="-Wl,-O1 -Wl,--as-needed" MAKEOPTS="-j4" PKGDIR="/usr/portage/packages" PORTAGE_CONFIGROOT="/" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="acl amd64 bash-completion berkdb bzip2 cli cracklib crypt cups cxx dri fortran gdbm gpm iconv ipv6 mmx modules mudflap multilib ncurses nls nptl nptlonly openmp pam pcre pppd readline session sse sse2 ssl sysfs tcpd unicode vim-syntax visibility xorg zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mmap_emul mulaw multi null plug rate route share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon authn_dbm authn_default authn_file authz_dbm authz_default authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache filter headers include info log_config logio mem_cache mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="kexi words flow plan stage tables krita karbon braindump" CAMERAS="ptp2" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock itrax mtk3301 nmea ntrip navcom oceanserver oldstyle oncore rtcm104v2 rtcm104v3 sirf superstar2 timing tsip tripmate tnt ubx" INPUT_DEVICES="keyboard mouse evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" PHP_TARGETS="php5-3" RUBY_TARGETS="ruby18" USERLAND="GNU" VIDEO_CARDS="fbdev glint intel mach64 mga neomagic nouveau nv r128 radeon savage sis tdfx trident vesa via vmware dummy v4l" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipset ipp2p iface geoip fuzzy condition tee tarpit sysrq steal rawnat logmark ipmark dhcpmac delude chaos account" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL, LINGUAS, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
(In reply to comment #0) > #3 0x00007ffff70f4c2d in gdk_display_open_default_libgtk_only () from > /usr/lib64/libgdk-x11-2.0.so.0 > #4 0x00007ffff79051c6 in post_parse_hook () from /usr/lib64/libgtk-3.so.0 libgtk-3.so.0 belongs to gtk3, but libgdk-x11-2.0.so belongs to gtk2. Linking to gtk2 and gtk3 simultaneously is something that theoretically should be impossible, but if it happens, it inevitably leads to crashes. What versions of gtk+:2 and gtk+:3 are you using, and with what USE flags? Please rebuild the latest ~arch versions of gtk+:2, gtk+:3, and gnome-screensaver. If the problem persists after the rebuild, please attach the complete build logs for these 3 packages when building with MAKEOPTS="V=1" (to ensure that the log is more verbose).
Created attachment 300999 [details] Build log for gtk+:2 (gzip)
Created attachment 301001 [details] Build log for gtk+:3 (gzip)
Created attachment 301003 [details] Build log for gnome-screensaver (gzip)
I rebuilt all three packages and the problem persists. I've attached the build logs for all three packages above. By the way, here's the ldd output which seems to confirm that the binary links to both gtk versions 2 and 3: $ ldd /usr/libexec/gnome-screensaver-dialog linux-vdso.so.1 => (0x00007fff43d88000) libgtk-3.so.0 => /usr/lib64/libgtk-3.so.0 (0x00007feaa7013000) libpam.so.0 => /lib64/libpam.so.0 (0x00007feaa6e07000) libgnomekbdui.so.7 => /usr/lib64/libgnomekbdui.so.7 (0x00007feaa6bef000) libgdk-x11-2.0.so.0 => /usr/lib64/libgdk-x11-2.0.so.0 (0x00007feaa694a000) libgio-2.0.so.0 => /usr/lib64/libgio-2.0.so.0 (0x00007feaa6629000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007feaa640c000) libgdk-3.so.0 => /usr/lib64/libgdk-3.so.0 (0x00007feaa6199000) libgdk_pixbuf-2.0.so.0 => /usr/lib64/libgdk_pixbuf-2.0.so.0 (0x00007feaa5f7e000) libcairo.so.2 => /usr/lib64/libcairo.so.2 (0x00007feaa5c8e000) libxklavier.so.16 => /usr/lib64/libxklavier.so.16 (0x00007feaa5a71000) libgobject-2.0.so.0 => /usr/lib64/libgobject-2.0.so.0 (0x00007feaa5831000) libgthread-2.0.so.0 => /usr/lib64/libgthread-2.0.so.0 (0x00007feaa562c000) libglib-2.0.so.0 => /usr/lib64/libglib-2.0.so.0 (0x00007feaa532e000) libc.so.6 => /lib64/libc.so.6 (0x00007feaa4fa8000) libXext.so.6 => /usr/lib64/libXext.so.6 (0x00007feaa4d97000) libXi.so.6 => /usr/lib64/libXi.so.6 (0x00007feaa4b89000) libXrandr.so.2 => /usr/lib64/libXrandr.so.2 (0x00007feaa4981000) libXcursor.so.1 => /usr/lib64/libXcursor.so.1 (0x00007feaa4777000) libpangocairo-1.0.so.0 => /usr/lib64/libpangocairo-1.0.so.0 (0x00007feaa456b000) libX11.so.6 => /usr/lib64/libX11.so.6 (0x00007feaa424a000) libXcomposite.so.1 => /usr/lib64/libXcomposite.so.1 (0x00007feaa4047000) libXdamage.so.1 => /usr/lib64/libXdamage.so.1 (0x00007feaa3e44000) libXfixes.so.3 => /usr/lib64/libXfixes.so.3 (0x00007feaa3c3e000) libatk-1.0.so.0 => /usr/lib64/libatk-1.0.so.0 (0x00007feaa3a1e000) libcairo-gobject.so.2 => /usr/lib64/libcairo-gobject.so.2 (0x00007feaa3815000) libpangoft2-1.0.so.0 => /usr/lib64/libpangoft2-1.0.so.0 (0x00007feaa35f2000) libpango-1.0.so.0 => /usr/lib64/libpango-1.0.so.0 (0x00007feaa33ad000) libfreetype.so.6 => /usr/lib64/libfreetype.so.6 (0x00007feaa3125000) libz.so.1 => /lib64/libz.so.1 (0x00007feaa2f12000) libbz2.so.1 => /lib64/libbz2.so.1 (0x00007feaa2d05000) libfontconfig.so.1 => /usr/lib64/libfontconfig.so.1 (0x00007feaa2ad5000) libgmodule-2.0.so.0 => /usr/lib64/libgmodule-2.0.so.0 (0x00007feaa28d1000) librt.so.1 => /lib64/librt.so.1 (0x00007feaa26c8000) libm.so.6 => /lib64/libm.so.6 (0x00007feaa2446000) libdl.so.2 => /lib64/libdl.so.2 (0x00007feaa2242000) libgnomekbd.so.7 => /usr/lib64/libgnomekbd.so.7 (0x00007feaa203b000) libXrender.so.1 => /usr/lib64/libXrender.so.1 (0x00007feaa1e32000) libffi.so.5 => /usr/lib64/libffi.so.5 (0x00007feaa1c2a000) libresolv.so.2 => /lib64/libresolv.so.2 (0x00007feaa1a14000) /lib64/ld-linux-x86-64.so.2 (0x00007feaa75f9000) libpng15.so.15 => /usr/lib64/libpng15.so.15 (0x00007feaa17ec000) libpixman-1.so.0 => /usr/lib64/libpixman-1.so.0 (0x00007feaa158b000) libEGL.so.1 => /usr/lib64/libEGL.so.1 (0x00007feaa1375000) libGL.so.1 => /usr/lib64/libGL.so.1 (0x00007feaa105f000) libxml2.so.2 => /usr/lib64/libxml2.so.2 (0x00007feaa0d41000) libxkbfile.so.1 => /usr/lib64/libxkbfile.so.1 (0x00007feaa0b21000) libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x00007feaa0904000) libexpat.so.1 => /usr/lib64/libexpat.so.1 (0x00007feaa06e3000) libX11-xcb.so.1 => /usr/lib64/libX11-xcb.so.1 (0x00007feaa04e1000) libxcb-dri2.so.0 => /usr/lib64/libxcb-dri2.so.0 (0x00007feaa02dd000) libxcb-xfixes.so.0 => /usr/lib64/libxcb-xfixes.so.0 (0x00007feaa00d6000) libdrm.so.2 => /usr/lib64/libdrm.so.2 (0x00007fea9fecc000) libnvidia-tls.so.290.10 => /usr/lib64/opengl/nvidia/lib/libnvidia-tls.so.290.10 (0x00007fea9fcc9000) libnvidia-glcore.so.290.10 => /usr/lib64/libnvidia-glcore.so.290.10 (0x00007fea9d9c2000) libicuuc.so.48 => /usr/lib64/libicuuc.so.48 (0x00007fea9d67e000) libXau.so.6 => /usr/lib64/libXau.so.6 (0x00007fea9d47b000) libXdmcp.so.6 => /usr/lib64/libXdmcp.so.6 (0x00007fea9d275000) libicudata.so.48 => /usr/lib64/libicudata.so.48 (0x00007fea9bf07000) libstdc++.so.6 => /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.3/libstdc++.so.6 (0x00007fea9bc07000) libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007fea9b9f1000)
Package versions and USE flags are as follows: x11-libs/gtk+-2.24.9-r1: (-aqua) cups -debug -doc -examples introspection vim-syntax -xinerama (-test) x11-libs/gtk+-3.2.3: (-aqua) -colord cups -debug -doc -examples introspection -packagekit vim-syntax -xinerama (-test) gnome-extra/gnome-screensaver-3.2.0: debug -doc pam
(In reply to comment #4) (In reply to comment #5) Thanks, this helps. What version of gnome-base/libgnomekbd do you have installed? If its 2.something, please try updating to 3.2.x, and then rebuild gnome-screensaver.
Just checked and it turns out I'm already running gnome-base/libgnomekbd-3.2.0-r1. I quickly rebuilt it as well as gnome-screensaver, but the problem remains even after completely restarting X. By the way, all other parts of the new GNOME 3 desktop seem to work just fine, including gnome-shell with all its fancy hardware accelerated stuff. Even the options in the screen section of the system settings applet work as expected (such as screen turn off timeout) and the gnome-screenserver daemon is running all the time in the background when I look at the processes. It just fails to actually run that dialog whenever I attempt to unlock.
Any fix around? Otherwise we should mask it until this is fixed.
(In reply to comment #9) > Any fix around? No. As far as I know, no dev has been able to reproduce the segfault, and I cannot think of a mechanism that could cause the linking problem that causes it. > Otherwise we should mask it until this is fixed. No. I have not seen any indication that the segfault is caused by a bug in gnome-screensaver.
(In reply to comment #10) > (In reply to comment #9) > > Any fix around? > > No. As far as I know, no dev has been able to reproduce the segfault, and I > cannot think of a mechanism that could cause the linking problem that causes > it. I can reproduce it and Diego said something similar about g-screensaver acting weird. > > > Otherwise we should mask it until this is fixed. > > No. I have not seen any indication that the segfault is caused by a bug in > gnome-screensaver. Might be right, but I would be careful, because it causes some serious trouble to people if it happens.
I read through the bug and I have a slightly different behavior. If I log into gdm, my screen gets directly locked without any possibility to unlock it again. Only possibility is to remove gnome-screensaver to be able to log in.
(In reply to comment #12) > I read through the bug and I have a slightly different behavior. > If I log into gdm, my screen gets directly locked without any possibility to > unlock it again. Only possibility is to remove gnome-screensaver to be able > to log in. This bug report is about segfaults in /usr/libexec/gnome-screensaver-dialog If gnome-screensaver-dialog is not segfaulting but you are experiencing a black screen in gnome-screensaver-3.4.2 on multi-monitor setups, that's bug #425070 (which I suspect has something to do with nvidia's idiosyncrasies).
oh, thought it was the same. sorry.
I have a similar problem, the screensaver prevents my normal access to the computer. I still see the mouse pointer and head pannel with the clock and I can switcht to the alpha-numerical console (ALT-CTL-F1), but if I press other keys or klick with the mouse the screen remains black. If I try switch back to the graphical console (ALT-F7) all stays black, there is any head pannel clock etc, but if I press (ALT-F8) I get a head panel, but I can't elsewise interact this console. rose@moose:/home/rose(2)$ genlop -t gtk+ | tail Fri Jul 6 09:26:28 2012 >>> x11-libs/gtk+-3.4.3-r1 merge time: 5 minutes and 38 seconds. Mon Jul 16 11:17:59 2012 >>> x11-libs/gtk+-2.24.11 merge time: 5 minutes and 43 seconds. Mon Jul 16 11:23:11 2012 >>> x11-libs/gtk+-3.4.4 merge time: 5 minutes and 12 seconds. rose@moose:/home/rose(3)$ genlop -t gnome-screensaver | tail Tue Jul 10 18:44:31 2012 >>> gnome-extra/gnome-screensaver-3.4.1 merge time: 20 seconds. Mon Jul 16 11:31:40 2012 >>> gnome-extra/gnome-screensaver-3.4.2-r1 merge time: 20 seconds. Thu Jul 19 17:51:14 2012 >>> gnome-extra/gnome-screensaver-3.4.4 merge time: 26 seconds. Maybe ten minutes later the screen appears again, but the system is very slow. After selecting an other window or an other page I have to wait several seconds until the window comes up or until the screen switches to the other page.
Top show something like this via ssh: top - 14:57:55 up 16 days, 1:46, 19 users, load average: 4.04, 4.12, 4.13 Tasks: 286 total, 7 running, 278 sleeping, 0 stopped, 1 zombie %Cpu(s): 27.1 us, 9.1 sy, 0.0 ni, 47.7 id, 16.0 wa, 0.0 hi, 0.1 si, 0.0 st KiB Mem: 8167768 total, 8008864 used, 158904 free, 64836 buffers KiB Swap: 33575840 total, 2233220 used, 31342620 free, 486652 cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 12051 root 20 0 212m 138m 3756 R 19.6 1.7 0:00.59 genlop 8328 rose 20 0 580m 9892 3172 S 15.6 0.1 119:57.33 gnome-system-mo 30518 root 20 0 426m 106m 11m S 11.6 1.3 609:03.20 Xorg 30857 rose 20 0 4455m 1.8g 7564 D 7.3 22.8 507:44.49 gnome-shell 14616 rose 20 0 2150m 430m 8216 R 4.3 5.4 717:12.19 firefox 15162 rose 20 0 4828m 3.1g 3.1g S 4.0 39.5 67:00.46 VirtualBox 12091 root 20 0 131m 8636 5456 R 3.3 0.1 0:00.10 mono 9733 root 20 0 31140 3812 1300 S 2.7 0.0 0:46.54 htop 7204 root 20 0 25808 2232 784 S 1.7 0.0 30:13.63 htop 16093 root 20 0 76012 20m 1076 S 1.0 0.3 0:27.97 multitail 17610 rose 20 0 255m 5400 2868 S 1.0 0.1 113:07.60 gkrellm 15857 rose 20 0 417m 2828 2032 S 0.7 0.0 2:42.28 plugin-containe 31073 rose 20 0 76156 2488 872 S 0.7 0.0 1:02.16 xterm 200 root 20 0 0 0 0 S 0.3 0.0 0:32.06 sync_supers 4042 root 20 0 0 0 0 S 0.3 0.0 1:06.30 md127_raid1 9143 root 20 0 8452 628 512 R 0.3 0.0 0:01.51 tee 9152 root 20 0 657m 500m 1764 R 0.3 6.3 4:05.27 emerge 10281 root 20 0 0 0 0 S 0.3 0.0 0:00.02 kworker/3:0 ... At the direct graphical console the is practically unsusable.
What about gnome-screensaver-3.4.4 ? I also had various problems with screenlocking all fixed now with this version.
(In reply to comment #17) > What about gnome-screensaver-3.4.4 ? I also had various problems with > screenlocking all fixed now with this version. All issues are fixed here on ~arch system
The problem is also fixed for me with >=gnome-screensaver-3.4.4, closing.
