Bug 448664 – crash in Rhythmbox Music Player: Trying to open my MTP de...

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 448664 - crash in Rhythmbox Music Player: Trying to open my MTP de...


Summary:	crash in Rhythmbox Music Player: Trying to open my MTP de...


Status:	RESOLVED DUPLICATE of bug 569074

Product:	rhythmbox
Classification:	Other
Component:	general
Version:	0.9.6
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	RhythmBox Maintainers
QA Contact:	RhythmBox Maintainers

URL:
Whiteboard:

Duplicates:	463949 523104 (view as bug list)
Depends on:
Blocks:

Reported:	2007-06-18 03:41 UTC by cbeacham
Modified:	2009-01-28 09:12 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description cbeacham 2007-06-18 03:41:10 UTC

What were you doing when the application crashed?
Trying to open my MTP device for the first time, and downloading podcasts


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 121499648 vsize: 0 resident: 121499648 share: 0 rss: 28958720 rss_rlim: 0
CPU usage: start_time: 1182137817 rtime: 0 utime: 2376 stime: 0 cutime:2233 cstime: 0 timeout: 143 it_real_value: 0 frequency: 2

Backtrace was generated from '/usr/local/bin/rhythmbox'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1227344208 (LWP 6473)]
[New Thread -1288586336 (LWP 6710)]
[New Thread -1305371744 (LWP 6484)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 141786

Thread 1 (Thread -1227344208 (LWP 6473))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/tls/i686/cmov/libc.so.6
#6 abort
from /lib/tls/i686/cmov/libc.so.6
#7 g_logv
from /usr/lib/libglib-2.0.so.0
#8 g_log
from /usr/lib/libglib-2.0.so.0
#9 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#10 load_mtp_db_idle_cb
at rb-mtp-source.c line 324
#11 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#12 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#13 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#14 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#15 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#16 main
at main.c line 306
#0 __kernel_vsyscall

Comment 1 Jonathan Matthew 2007-07-21 02:04:44 UTC

Looking at the code, I can't see how this can possibly occur.  Did this ever happen again?

Comment 2 cbeacham 2007-07-21 15:18:58 UTC

No, it never repeated, maybe it was a freak incident.

Comment 3 Jonathan Matthew 2007-11-28 13:18:58 UTC

*** Bug 463949 has been marked as a duplicate of this bug. ***

Comment 4 Jonathan Matthew 2008-03-18 08:34:39 UTC

*** Bug 523104 has been marked as a duplicate of this bug. ***

Comment 5 Jonathan Matthew 2008-11-11 05:14:32 UTC

I don't think we're ever going to figure out what happened.

Comment 6 Jonathan Matthew 2009-01-28 09:11:51 UTC

Actually, no, I just fixed this.

Comment 7 Jonathan Matthew 2009-01-28 09:12:27 UTC


*** This bug has been marked as a duplicate of 569074 ***