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 481619 - crash in Rhythmbox Music Player:
crash in Rhythmbox Music Player:
Status: RESOLVED DUPLICATE of bug 436456
Product: rhythmbox
Classification: Other
Component: general
0.10.x
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
: 468828 481639 500720 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2007-09-29 15:29 UTC by Zimecki
Modified: 2008-05-27 15:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Zimecki 2007-09-29 15:29:23 UTC
Version: 0.10.1

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-2931.fc7xen #1 SMP Mon Aug 13 10:12:37 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 166735872 vsize: 166735872 resident: 46034944 share: 26406912 rss: 46034944 rss_rlim: 4294967295
CPU usage: start_time: 1191079404 rtime: 717 utime: 656 stime: 61 cutime:4 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208813856 (LWP 6394)]
[New Thread -1319130224 (LWP 6438)]
[New Thread -1287660656 (LWP 6436)]
[New Thread -1308640368 (LWP 6416)]
[New Thread -1298150512 (LWP 6415)]
[New Thread -1266680944 (LWP 6414)]
[New Thread -1238635632 (LWP 6413)]
[New Thread -1277170800 (LWP 6401)]
(no debugging symbols found)
0x00b85402 in __kernel_vsyscall ()

Thread 1 (Thread -1208813856 (LWP 6394))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/nosegneg/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/i686/nosegneg/libc.so.6
  • #6 abort
    from /lib/i686/nosegneg/libc.so.6
  • #7 __assert_fail
    from /lib/i686/nosegneg/libc.so.6
  • #8 ??
    from /usr/lib/libpython2.5.so.1.0
  • #9 PyGC_Collect
    from /usr/lib/libpython2.5.so.1.0
  • #10 ??
  • #11 ??
    from /lib/libglib-2.0.so.0
  • #12 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #13 ??
    from /lib/libglib-2.0.so.0
  • #14 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #15 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 main
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
(bug-buddy:6384): GLib-GObject-WARNING **: invalid uninstantiatable type `GParamChar' in cast to `GObject'
(bug-buddy:6384): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed
(bug-buddy:6384): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table->ref_count > 0' failed
(bug-buddy:6384): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
rhythmbox: Modules/gcmodule.c:241: update_refs: Assertion `gc->gc.gc_refs == (-3)' failed.
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-10-01 09:36:08 UTC
*** Bug 481639 has been marked as a duplicate of this bug. ***
Comment 2 Jonathan Matthew 2007-12-01 09:12:07 UTC
*** Bug 468828 has been marked as a duplicate of this bug. ***
Comment 3 Jonathan Matthew 2007-12-01 09:12:17 UTC
*** Bug 500720 has been marked as a duplicate of this bug. ***
Comment 4 Diego Escalante Urrelo (not reading bugmail) 2008-05-27 15:24:28 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 436456 ***