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 636922 - crash in Rhythmbox: I just came back from sl...
crash in Rhythmbox: I just came back from sl...
Status: RESOLVED DUPLICATE of bug 613526
Product: rhythmbox
Classification: Other
Component: general
0.12.x
Other All
: Normal critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-12-09 22:06 UTC by juanmi
Modified: 2010-12-10 02:13 UTC
See Also:
GNOME target: ---
GNOME version: 2.29/2.30


Description juanmi 2010-12-09 22:06:23 UTC 
Version: 0.12.8

What were you doing when the application crashed?
I just came back from sleeping mode (computer was in standby), nothing special.


Distribution: Debian squeeze/sid
Gnome Release: 2.30.2 2010-11-12 (Debian)
BugBuddy Version: 2.30.0

System: Linux 2.6.32-trunk-686 #1 SMP Sun Jan 10 06:32:16 UTC 2010 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10707000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome
GTK+ Modules: gnomebreakpad

Memory status: size: 216272896 vsize: 216272896 resident: 50700288 share: 23314432 rss: 50700288 rss_rlim: 18446744073709551615
CPU usage: start_time: 1291891637 rtime: 14538 utime: 12548 stime: 1990 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xa9d66b70 (LWP 23739)]
[New Thread 0xa60ffb70 (LWP 25105)]
[New Thread 0xa7afdb70 (LWP 12729)]
[New Thread 0xa82feb70 (LWP 30321)]
[New Thread 0xae58eb70 (LWP 30318)]
[New Thread 0xa8d64b70 (LWP 20829)]
[New Thread 0xb01ffb70 (LWP 20820)]
[New Thread 0xb213ab70 (LWP 16038)]
0xb786e424 in __kernel_vsyscall ()

+ Trace 225065

Thread 1 (Thread 0xb60b9970 (LWP 16034))

  • #0 __kernel_vsyscall
  • #1 waitpid
    at ../sysdeps/unix/syscall-template.S line 82
  • #2 g_spawn_sync
    from /lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 __kernel_vsyscall
  • #7 *__GI_raise
    at ../nptl/sysdeps/unix/sysv/linux/raise.c line 64
  • #8 *__GI_abort
    at abort.c line 92
  • #9 g_assertion_message
    from /lib/libglib-2.0.so.0
  • #10 g_assertion_message_expr
    from /lib/libglib-2.0.so.0
  • #11 rb_sourcelist_remove
    from /usr/lib/librhythmbox-core.so.0
  • #12 ??
    from /usr/lib/librhythmbox-core.so.0
  • #13 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #15 ??
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #18 rb_source_delete_thyself
    from /usr/lib/librhythmbox-core.so.0
  • #19 ??
    from /usr/lib/rhythmbox/plugins/mtpdevice/libmtpdevice.so
  • #20 ??
    from /lib/libglib-2.0.so.0
  • #21 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #22 ??
    from /lib/libglib-2.0.so.0
  • #23 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #24 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 main 
A debugging session is active.

	Inferior 1 [process 16034] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors (13 sec old) ---------------------
(evolution:3504): camel-CRITICAL **: camel_data_wrapper_set_mime_type_field: assertion `mime_type != NULL' failed
(evolution:3504): camel-CRITICAL **: camel_data_wrapper_set_mime_type_field: assertion `mime_type != NULL' failed
evolution-shell-Message: Network disconnected.  Forced offline.
** Message: RFKILL event: idx 0 type 1 op 2 soft 0 hard 0
** Message: RFKILL event: idx 1 type 2 op 2 soft 0 hard 0
** Message: killswitch 1 is 1
** Message: killswitches state 1
** Message: RFKILL event: idx 2 type 1 op 2 soft 0 hard 1
** Message: RFKILL event: idx 2 type 1 op 2 soft 0 hard 0
--------------------------------------------------
Comment 1 Fabio Durán Verdugo 2010-12-10 02:13:45 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

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