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 453053 - crash in Rhythmbox Music Player: Closing it from the x bu...
crash in Rhythmbox Music Player: Closing it from the x bu...
Status: RESOLVED DUPLICATE of bug 452703
Product: rhythmbox
Classification: Other
Component: general
0.10.0
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-07-02 10:09 UTC by joel.granados
Modified: 2007-07-02 11:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description joel.granados 2007-07-02 10:09:58 UTC
What were you doing when the application crashed?
Closing it from the x button in the window


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-2925.11.fc7xen #1 SMP Mon Jun 11 16:18:59 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 876924928 vsize: 876924928 resident: 285384704 share: 25145344 rss: 285384704 rss_rlim: 18446744073709551615
CPU usage: start_time: 1183363712 rtime: 9032 utime: 8582 stime: 450 cutime:1 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496355904 (LWP 3791)]
[New Thread 1105209680 (LWP 3805)]
[New Thread 1126455632 (LWP 3802)]
[New Thread 1115699536 (LWP 3799)]
(no debugging symbols found)
0x00000030c0c0d89f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496355904 (LWP 3791))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 ??
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib64/libc.so.6
  • #4 abort
    from /lib64/libc.so.6
  • #5 g_logv
    from /lib64/libglib-2.0.so.0
  • #6 g_log
    from /lib64/libglib-2.0.so.0
  • #7 g_assert_warning
    from /lib64/libglib-2.0.so.0
  • #8 ??
  • #9 ??
  • #10 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #11 ??
    from /lib64/libgobject-2.0.so.0
  • #12 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #13 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #14 ??
  • #15 ??
  • #16 rhythmdb_query_model_remove_entry
  • #17 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #18 ??
    from /lib64/libgobject-2.0.so.0
  • #19 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #20 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #21 ??
  • #22 ??
    from /lib64/libglib-2.0.so.0
  • #23 ??
  • #24 ??
  • #25 PyEval_EvalFrameEx
    from /usr/lib64/libpython2.5.so.1.0
  • #26 PyEval_EvalCodeEx
    from /usr/lib64/libpython2.5.so.1.0
  • #27 ??
    from /usr/lib64/libpython2.5.so.1.0
  • #28 PyObject_Call
    from /usr/lib64/libpython2.5.so.1.0
  • #29 ??
    from /usr/lib64/libpython2.5.so.1.0
  • #30 PyObject_Call
    from /usr/lib64/libpython2.5.so.1.0
  • #31 ??
    from /usr/lib64/libpython2.5.so.1.0
  • #32 PyObject_CallMethod
    from /usr/lib64/libpython2.5.so.1.0
  • #33 ??
  • #34 ??
  • #35 ??
  • #36 ??
    from /lib64/libglib-2.0.so.0
  • #37 g_hash_table_remove_all
    from /lib64/libglib-2.0.so.0
  • #38 g_hash_table_destroy
    from /lib64/libglib-2.0.so.0
  • #39 rb_plugins_engine_shutdown
  • #40 rb_shell_quit
  • #41 ??
  • #42 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #43 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #44 ??
    from /lib64/libgobject-2.0.so.0
  • #45 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #46 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #47 ??
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #48 gtk_main_do_event
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #49 ??
    from /usr/lib64/libgdk-x11-2.0.so.0
  • #50 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #51 ??
    from /lib64/libglib-2.0.so.0
  • #52 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #53 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #54 main
  • #0 waitpid
    from /lib64/libpthread.so.0


----------- .xsession-errors ---------------------
(gnome-terminal:3819): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x440005a (OpenOffice)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x440005a (OpenOffice)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x440005a (OpenOffice)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x440005a (OpenOffice)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Playing WAVE '/usr/share/sounds/pidgin/alert.wav' : Signed 16 bit Little Endian, Rate 22050 Hz, Mono
Playing WAVE '/usr/share/sounds/pidgin/alert.wav' : Signed 16 bit Little Endian, Rate 22050 Hz, Mono
Playing WAVE '/usr/share/sounds/pidgin/alert.wav' : Signed 16 bit Little Endian, Rate 22050 Hz, Mono
RhythmDB-ERROR **: file rhythmdb-property-model.c: line 653 (rhythmdb_property_model_delete_prop): assertion failed: ((ptr = g_hash_table_lookup (model->priv->reverse_map, propstr)))
aborting...
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-07-02 11:30:05 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 452703 ***