Summary: | gnome-extra/gnome-screensaver-3.2.0: gnome-screensaver-dialog segfaults and keeps screen locked | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Fabian Hahn <esmf68> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | gentoo, jlec, nexus |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Build log for gtk+:2 (gzip)
Build log for gtk+:3 (gzip) Build log for gnome-screensaver (gzip) |
Description
Fabian Hahn
2012-01-31 19:49:22 UTC
(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. |