[Bug 16926] Rhythmbox crashes on startup

[bugzilla-daemon at bugzilla.ubuntu.com]

Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=16926
Ubuntu | rhythmbox





------- Additional Comments From mail at dfile.nl  2005-10-04 23:21 UTC -------
I am pretty sure I installed the debug package before putting the backtrace info
here.

But to be sure I installed the package again and ran it with gdb...

Here is the output:

dennis at dennis:~$ sudo dpkg -i rhythmbox_0.9.0-0ubuntu5_i386.deb
dpkg - warning: downgrading rhythmbox from 0.9.0-0ubuntu6 to 0.9.0-0ubuntu5.
(Reading database ... 69903 files and directories currently installed.)
Preparing to replace rhythmbox 0.9.0-0ubuntu6 (using
rhythmbox_0.9.0-0ubuntu5_i386.deb) ...
Unpacking replacement rhythmbox ...
Setting up rhythmbox (0.9.0-0ubuntu5) ...

dennis at dennis:~$ gdb rhythmbox
GNU gdb 6.3-debian
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i486-linux-gnu"...Using host libthread_db library
"/lib/tls/i686/cmov/libthread_db.so.1".

(gdb) run
Starting program: /usr/bin/rhythmbox
[Thread debugging using libthread_db enabled]
[New Thread -1224874304 (LWP 18653)]
[New Thread -1226765392 (LWP 18674)]
[New Thread -1235158096 (LWP 18675)]
[New Thread -1235670096 (LWP 18676)]
[Thread -1235670096 (LWP 18676) exited]
[New Thread -1244079184 (LWP 18677)]
[Thread -1244079184 (LWP 18677) exited]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1224874304 (LWP 18653)]
0xb7137b7a in strcmp () from /lib/tls/i686/cmov/libc.so.6



-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.