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 353616 - crash in Rhythmbox Music Player: I open and close Rhythmb...
crash in Rhythmbox Music Player: I open and close Rhythmb...
Status: RESOLVED NOTABUG
Product: rhythmbox
Classification: Other
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-08-30 23:26 UTC by Cristian Aravena Romero
Modified: 2007-01-27 15:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Cristian Aravena Romero 2006-08-30 23:26:59 UTC 
What were you doing when the application crashed?
I open and close Rhythmbox.


Distribution: Ubuntu 6.06 (dapper)
Gnome Release: 2.15.92 2006-08-29 (GARNOME)
BugBuddy Version: 2.15.92

Memory status: size: 79663104 vsize: 0 resident: 79663104 share: 0 rss: 32153600 rss_rlim: 0
CPU usage: start_time: 1156980296 rtime: 0 utime: 419 stime: 0 cutime:315 cstime: 0 timeout: 104 it_real_value: 0 frequency: 4

Backtrace was generated from '/home/gnome/garnome/bin/rhythmbox'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1230247200 (LWP 6071)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 71285

Thread 1 (Thread -1230247200 (LWP 6071))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 867
  • #3 <signal handler called>
  • #4 IA__g_logv
    at gmessages.c line 503
  • #5 IA__g_log
    at gmessages.c line 517
  • #6 IA__g_return_if_fail_warning
    at gmessages.c line 532
  • #7 IA__gtk_container_foreach
    at gtkcontainer.c line 1283
  • #8 IA__gtk_container_get_children
    at gtkcontainer.c line 1373
  • #9 update_node
    at gtkuimanager.c line 2154
  • #10 update_node
    at gtkuimanager.c line 2567
  • #11 update_node
    at gtkuimanager.c line 2567
  • #12 do_updates
    at gtkuimanager.c line 2609
  • #13 do_updates_idle
    at gtkuimanager.c line 2620
  • #14 g_idle_dispatch
    at gmain.c line 3924
  • #15 IA__g_main_context_dispatch
    at gmain.c line 2043
  • #16 g_main_context_iterate
    at gmain.c line 2675
  • #17 IA__g_main_loop_run
    at gmain.c line 2879
  • #18 IA__gtk_clipboard_store
    at gtkclipboard.c line 1883
  • #19 _gtk_clipboard_store_all
    at gtkclipboard.c line 1917
  • #20 IA__gtk_main
    at gtkmain.c line 1050
  • #21 main
    at main.c line 375
  • #0 __kernel_vsyscall 






Comment 1


Jonathan Matthew





          2006-08-31 09:48:28 UTC
        



Does this happen every time you run rhythmbox?  How did you close it?  Did you close it before it had fully started up?






Comment 2


Karsten Bräckelmann





          2006-09-17 23:56:54 UTC
        



Jonathan, please see bug 350776, which got a similar issue. There is quite a lot of interesting discussion over there.

Actually, the stacktrace is identical. However, the fix is gedit specific -- unless this issue happens to be a Python issue as well. Thus not marking as duplicate, since Rhythmbox likely needs a similar fix.