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 463642 - crash in Rhythmbox Music Player: listening to a song from...
crash in Rhythmbox Music Player: listening to a song from...
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-08-05 12:33 UTC by Terry Wallwork
Modified: 2007-08-07 13:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Terry Wallwork 2007-08-05 12:33:24 UTC 
What were you doing when the application crashed?
listening to a song from the music player and went to close the application down, which then 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.22.1-33.fc7 #1 SMP Mon Jul 23 17:33:07 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: Fedora

Memory status: size: 279105536 vsize: 279105536 resident: 171655168 share: 25530368 rss: 171655168 rss_rlim: 4294967295
CPU usage: start_time: 1186316931 rtime: 2650 utime: 2518 stime: 132 cutime:2 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 "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208473040 (LWP 14264)]
[New Thread -1279255664 (LWP 14296)]
[New Thread -1325945968 (LWP 14282)]
[New Thread -1242895472 (LWP 14273)]
[New Thread -1257538672 (LWP 14270)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 152949

Thread 2 (Thread -1279255664 (LWP 14296))

  • #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 (28925 sec old) ---------------------
(gwget:5094): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()
(gwget:5094): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()
Window manager warning: Property _NET_WM_NAME on window 0x3c00003 contained invalid UTF-8
Window manager warning: Property _NET_WM_ICON_NAME on window 0x3c00003 contained invalid UTF-8
(gwget:5094): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()
(gwget:5094): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()
Window manager warning: Property _NET_WM_NAME on window 0x3c00003 contained invalid UTF-8
Window manager warning: Property _NET_WM_ICON_NAME on window 0x3c00003 contained invalid UTF-8
(gwget:5094): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-08-07 13:27:20 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 434003 ***