Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#23972 - [glibc] 2.13-5 causes calibre and VirtualBox to segfault

Attached to Project: Arch Linux
Opened by x (onexused) - Thursday, 28 April 2011, 12:43 GMT
Last edited by Allan McRae (Allan) - Sunday, 01 May 2011, 21:02 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Allan McRae (Allan)
Architecture i686
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
After doing a recent system update, I found that I could no longer run calibre or VirtualBox. Both reported "Segfault" when run from a terminal, before showing anything else. Downgrading either didn't help. Downgrading glibc from 2.13-5 to 2.13-4 fixed the problem.
This task depends upon

Closed by  Allan McRae (Allan)
Sunday, 01 May 2011, 21:02 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Issue with old Nvidia drivers
Comment by Gerardo Exequiel Pozzi (djgera) - Friday, 29 April 2011, 03:47 GMT
  • Field changed: Summary (glibc-2.13-5 causes calibre and VirtualBox to segfault → [glibc] 2.13-5 causes calibre and VirtualBox to segfault)
  • Field changed: Status (Unconfirmed → Assigned)
  • Task assigned to Allan McRae (Allan)

Comment by Gerardo Exequiel Pozzi (djgera) - Friday, 29 April 2011, 03:48 GMT
In my case, I can't start KDE:

kdeinit4[10060]: segfault at c ip b7897e02 sp bf889780 error 4 in ld-2.13.so[b7895000+f000]
ksmserver[10061]: segfault at c ip b78e019e sp bfc0cbd8 error 4 in ld-2.13.so[b78dd000+f000]

EDIT: On x86_64 works OK.
Comment by Allan McRae (Allan) - Friday, 29 April 2011, 06:47 GMT
I think I know this bug....

What processor do you have? Does running under gdb cause the application to work?
Comment by Gerardo Exequiel Pozzi (djgera) - Friday, 29 April 2011, 11:28 GMT
AMD Athlon(tm) 64 X2 Dual Core Processor 5200+

Yes under gdb/strace runs OK.
Comment by x (onexused) - Friday, 29 April 2011, 13:23 GMT
I have an Intel Core 2 Duo 6600.
I upgraded to glibc-2.13-5 again and tried running calibre and virtualbox with both gdb and strace.
Running the programs with gdb do -not- work for me (I did run gedit successfully, to make sure I wasn't doing something wrong):

[code]$ gdb
GNU gdb (GDB) 7.2
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
(gdb) file calibre
"/usr/bin/calibre": not in executable format: File format not recognized
(gdb) file virtualbox
"/usr/bin/virtualbox": not in executable format: File format not recognized
(gdb) file gedit
Reading symbols from /usr/bin/gedit...(no debugging symbols found)...done.
(gdb) start
Temporary breakpoint 1 at 0x8067163
Starting program: /usr/bin/gedit
[Thread debugging using libthread_db enabled]

Temporary breakpoint 1, 0x08067163 in main ()
(gdb) continue
Continuing.
/home/user/.themes/ClearMurrine/gtk-2.0/gtkrc:111: Murrine configuration option "hilight_ratio" will be deprecated in future releases. Please use "highlight_shade" instead.
/home/user/.themes/ClearMurrine/gtk-2.0/gtkrc:116: Murrine configuration option "gradients" is no longer supported and will be ignored.
/home/user/.themes/ClearMurrine/gtk-2.0/gtkrc:119: Murrine configuration option "style" is no longer supported and will be ignored.
[New Thread 0xb6e4ab70 (LWP 15076)]
[Thread 0xb6e4ab70 (LWP 15076) exited]

Program exited normally.
(gdb) quit
$ [/code]

Running calibre with strace worked, but running virtualbox with strace did not.
Attached is the output from "strace virtualbox". Would the strace output for calibre be useful?
   vbox.strace.bz2 (3.8 KiB)
Comment by Gerardo Exequiel Pozzi (djgera) - Friday, 29 April 2011, 14:03 GMT
Because are scripts, for example to run virtualbox you need to go directly to executable /usr/lib/virtualbox/VirtualBox, and run as root, because setuid bit will not work.

Something is wrong with gcc 4.6.0 and glibc loader in x86_32.
Comment by Allan McRae (Allan) - Friday, 29 April 2011, 21:10 GMT
This is the gentoo bug report: http://bugs.gentoo.org/show_bug.cgi?id=362391 . Also seen by the Chakra devs.

Unfortunately, I can not replicate and the bug seems to disappear randomly...
Comment by Gerardo Exequiel Pozzi (djgera) - Friday, 29 April 2011, 22:17 GMT
aja!, I catched, is related with libGL (provided by nvidia). Using LD_LIBRARY_PATH=/tmp/libgl/usr/lib/ (where here is libGL from libgl pkg) works fine.

@x: are you using nvidia propietary drvs?
Comment by Gerardo Exequiel Pozzi (djgera) - Friday, 29 April 2011, 22:30 GMT
aja! and this is fixed with latest nvidia libgl (270.41.03), but I am still with old driver (260.19.29) and Xorg because other unrelated problems of this topic.

If @onexused can confirm this, I think we can close this ticket.
Comment by Allan McRae (Allan) - Saturday, 30 April 2011, 07:14 GMT
The Chakra dev seeing the issue confirms he was using that version of the nvidia driver.
Comment by x (onexused) - Sunday, 01 May 2011, 20:00 GMT
I was using the nvidia proprietary drivers (260.19.44). After updating to 270.41.06, the bug disappears for me.

Loading...