Package: gir1.2-gdkpixbuf-2.0 Version: 2.30.5-1 Severity: important I have seen this behavior since my last update to 2.30.5 version on my two machines. It is totally reproducible and occurs at each attempt.
Yet, the crash occurs in /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 but, the failure may comes from other places (e.g. the gnome-control center). In the Gnome environment, the background is replaced by a solid color (gray) with no image displayed at all. When attempting to set the background image through the gnome-control-center, the software crash. Here are more details: root@beagle:~# tail -f /var/log/messages Mar 5 19:18:28 beagle kernel: [ 92.918008] gnome-control-c[5064]: segfault at 26bc000 ip 00007f4fc4656894 sp 00007fff5cb8c900 error 4 in libgdk-3.so.0.1000.7[7f4fc4629000+ab000] Mar 5 19:23:49 beagle kernel: [ 414.266984] gnome-control-c[5233]: segfault at 2183000 ip 00007f680d2df894 sp 00007fff82d41710 error 4 in libgdk-3.so.0.1000.7[7f680d2b2000+ab000] Mar 5 19:24:02 beagle kernel: [ 427.049226] gnome-control-c[5245]: segfault at 2f81000 ip 00007f93b7782894 sp 00007fff44047c20 error 4 in libgdk-3.so.0.1000.7[7f93b7755000+ab000] Mar 5 19:24:43 beagle kernel: [ 468.088191] gnome-control-c[5316]: segfault at 2e39000 ip 00007f7ac4ce8894 sp 00007fff3d773cc0 error 4 in libgdk-3.so.0.1000.7[7f7ac4cbb000+ab000] Mar 5 19:26:10 beagle kernel: [ 555.609458] gnome-control-c[5337]: segfault at 2445000 ip 00007fecb59f5894 sp 00007fffec8ad0f0 error 4 in libgdk-3.so.0.1000.7[7fecb59c8000+ab000] Mar 5 19:28:48 beagle kernel: [ 713.044324] gnome-control-c[5412]: segfault at 2a83000 ip 00007f72ecc0b894 sp 00007fff912ad9c0 error 4 in libgdk-3.so.0.1000.7[7f72ecbde000+ab000] When run under gdb and triggered to go to the background settings: (gdb) r Starting program: /usr/bin/gnome-control-center [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffd23ce700 (LWP 5443)] [New Thread 0x7fffc1c32700 (LWP 5444)] [New Thread 0x7fffc1431700 (LWP 5445)] Program received signal SIGSEGV, Segmentation fault. 0x00007ffff219e894 in gdk_pixbuf_get_from_surface () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 (gdb) bt #0 0x00007ffff219e894 in gdk_pixbuf_get_from_surface () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #1 0x000000000045a4bc in ?? () #2 0x00007ffff1c58a57 in g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #3 0x00007ffff1ca913a in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x00007ffff1c58a57 in g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #5 0x00007ffff1c58ab9 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #6 0x00007ffff0d48526 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x00007ffff0d48878 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x00007ffff0d4891c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x00007ffff1c84a1c in g_application_run () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #10 0x00000000004498c8 in main () (gdb) i f Stack level 0, frame at 0x7fffffffdf80: rip = 0x7ffff219e894 in gdk_pixbuf_get_from_surface; saved rip 0x45a4bc called by frame at 0x7fffffffdfd0 Arglist at 0x7fffffffdf18, args: Locals at 0x7fffffffdf18, Previous frame's sp is 0x7fffffffdf80 Saved registers: rbx at 0x7fffffffdf48, rbp at 0x7fffffffdf50, r12 at 0x7fffffffdf58, r13 at 0x7fffffffdf60, r14 at 0x7fffffffdf68, r15 at 0x7fffffffdf70, rip at 0x7fffffffdf78 (gdb) I can provide more information, but you need to tell me where to look because the bug seems to be between the gnome-control-center and the library... Don't know exactly where... -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13.5 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
