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 575774 - crash in Rhythmbox Music Player: Resuming from hibernate
crash in Rhythmbox Music Player: Resuming from hibernate
Status: RESOLVED DUPLICATE of bug 527898
Product: rhythmbox
Classification: Other
Component: general
0.11.x
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-03-18 00:13 UTC by Tobias Mueller
Modified: 2009-03-18 00:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description Tobias Mueller 2009-03-18 00:13:11 UTC 
Version: 0.11.6

What were you doing when the application crashed?
Resuming from hibernate


Distribution: Fedora release 10 (Cambridge)
Gnome Release: 2.24.3 2009-01-16 (Red Hat, Inc)
BugBuddy Version: 2.24.2

System: Linux 2.6.27.19-170.2.35.fc10.x86_64 #1 SMP Mon Feb 23 13:00:23 EST 2009 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10503000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Nodoka
Icon Theme: Fedora

Memory status: size: 1414115328 vsize: 1414115328 resident: 562667520 share: 5996544 rss: 562667520 rss_rlim: 18446744073709551615
CPU usage: start_time: 1237229354 rtime: 57235 utime: 46717 stime: 10518 cutime:1 cstime: 13 timeout: 0 it_real_value: 0 frequency: 100

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

[?1034h[Thread debugging using libthread_db enabled]
[New Thread 0x7f5cc3e58800 (LWP 8064)]
[New Thread 0x7f5c97dcc950 (LWP 8876)]
[New Thread 0x7f5cbd3de950 (LWP 8512)]
[New Thread 0x7f5caeaac950 (LWP 8412)]
0x0000003fb500ec2f in __libc_waitpid (pid=9656, stat_loc=0x7fffcbea9ad0, 
    options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41
41	  int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);

+ Trace 213577

Thread 1 (Thread 0x7f5cc3e58800 (LWP 8064))

  • #0 __libc_waitpid
    at ../sysdeps/unix/sysv/linux/waitpid.c line 41
  • #1 IA__g_spawn_sync
    at gspawn.c line 382
  • #2 IA__g_spawn_command_line_sync
    at gspawn.c line 694
  • #3 run_bug_buddy
    at gnome-breakpad.cc line 223
  • #4 check_if_gdb
    at gnome-breakpad.cc line 292
  • #5 bugbuddy_segv_handle
    at gnome-breakpad.cc line 84
  • #6 <signal handler called>
  • #7 raise
    at ../nptl/sysdeps/unix/sysv/linux/raise.c line 64
  • #8 abort
    at abort.c line 88
  • #9 IA__g_assertion_message
    at gtestutils.c line 1301
  • #10 IA__g_assertion_message_expr
    at gtestutils.c line 1312
  • #11 rhythmdb_property_model_prop_changed_cb
    at rhythmdb-property-model.c line 584
  • #12 IA__g_closure_invoke
    at gclosure.c line 767
  • #13 signal_emit_unlocked_R
    at gsignal.c line 3244
  • #14 IA__g_signal_emit_valist
    at gsignal.c line 2977
  • #15 IA__g_signal_emit
    at gsignal.c line 3034
  • #16 rhythmdb_query_model_entry_changed_cb
    at rhythmdb-query-model.c line 975
  • #17 IA__g_closure_invoke
    at gclosure.c line 767
  • #18 signal_emit_unlocked_R
    at gsignal.c line 3244
  • #19 IA__g_signal_emit_valist
    at gsignal.c line 2977
  • #20 IA__g_signal_emit
    at gsignal.c line 3034
  • #21 rhythmdb_emit_entry_signals_idle
    at rhythmdb.c line 1130
  • #22 g_main_dispatch
    at gmain.c line 2144
  • #23 IA__g_main_context_dispatch
    at gmain.c line 2697
  • #24 g_main_context_iterate
    at gmain.c line 2778
  • #25 IA__g_main_loop_run
    at gmain.c line 2986
  • #26 IA__gtk_main
    at gtkmain.c line 1200
  • #27 main
    at main.c line 330 






Comment 1


Jonathan Matthew





          2009-03-18 00:20:43 UTC
        



Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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