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 497829 - crash in Rhythmbox Music Player:
crash in Rhythmbox Music Player:
Status: RESOLVED DUPLICATE of bug 434003
Product: rhythmbox
Classification: Other
Component: general
0.10.0
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-11-18 09:30 UTC by veraneitor_pc
Modified: 2007-11-18 14:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description veraneitor_pc 2007-11-18 09:30:03 UTC
What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 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: 127897600 vsize: 127897600 resident: 31453184 share: 16449536 rss: 31453184 rss_rlim: 4294967295
CPU usage: start_time: 1195377790 rtime: 2854 utime: 2470 stime: 384 cutime:5 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208849872 (LWP 3289)]
[New Thread -1257247856 (LWP 3384)]
[New Thread -1322255472 (LWP 3380)]
[New Thread -1278227568 (LWP 3369)]
[New Thread -1245312112 (LWP 3306)]
[New Thread -1234429040 (LWP 3297)]
(no debugging symbols found)
0x002c9402 in __kernel_vsyscall ()

Thread 2 (Thread -1257247856 (LWP 3384))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 g_logv
    from /lib/libglib-2.0.so.0
  • #8 g_log
    from /lib/libglib-2.0.so.0
  • #9 ??
    from /lib/libgthread-2.0.so.0
  • #10 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #11 ??
  • #12 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #13 ??
  • #14 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #15 ??
  • #16 free
    from /lib/libc.so.6


----------- .xsession-errors (1373 sec old) ---------------------
(gnome-background-properties:3092): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed
(gnome-background-properties:3092): GdkPixbuf-CRITICAL **: gdk_pixbuf_composite: assertion `src != NULL' failed
(gnome-background-properties:3092): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed
(gnome-background-properties:3092): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed
(gnome-background-properties:3092): GdkPixbuf-CRITICAL **: gdk_pixbuf_composite: assertion `src != NULL' failed
(gnome-background-properties:3092): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed
(gnome-background-properties:3092): 
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 André Klapper 2007-11-18 14:51:43 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 434003 ***