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 507622 - crash in Rhythmbox Music Player:
crash in Rhythmbox Music Player:
Status: RESOLVED DUPLICATE of bug 465946
Product: rhythmbox
Classification: Other
Component: general
0.10.x
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-06 07:52 UTC by kkisical
Modified: 2008-01-06 08:15 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description kkisical 2008-01-06 07:52:08 UTC
Version: 0.10.1

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: 113881088 vsize: 113881088 resident: 29564928 share: 16928768 rss: 29564928 rss_rlim: 4294967295
CPU usage: start_time: 1199605290 rtime: 602 utime: 544 stime: 58 cutime:3 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 -1208251856 (LWP 5830)]
[New Thread -1271403632 (LWP 5903)]
[New Thread -1260913776 (LWP 5902)]
[New Thread -1223631984 (LWP 5901)]
[New Thread -1260643440 (LWP 5874)]
[New Thread -1234121840 (LWP 5853)]
[New Thread -1247143024 (LWP 5835)]
(no debugging symbols found)
0x00493402 in __kernel_vsyscall ()

Thread 4 (Thread -1223631984 (LWP 5901))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 xmlEncodeEntitiesReentrant
    from /usr/lib/libxml2.so.2
  • #5 ??
  • #6 ??
  • #7 ??
  • #8 g_hash_table_foreach
    from /lib/libglib-2.0.so.0
  • #9 ??
  • #10 g_hash_table_foreach
    from /lib/libglib-2.0.so.0
  • #11 ??
  • #12 g_hash_table_foreach
    from /lib/libglib-2.0.so.0
  • #13 ??
  • #14 g_hash_table_foreach
    from /lib/libglib-2.0.so.0
  • #15 ??
  • #16 ??
  • #17 ??
  • #18 g_hash_table_foreach
    from /lib/libglib-2.0.so.0
  • #19 rhythmdb_entry_type_foreach
  • #20 ??
  • #21 ??
  • #22 ??
    from /lib/libglib-2.0.so.0
  • #23 start_thread
    from /lib/libpthread.so.0
  • #24 clone
    from /lib/libc.so.6


----------- .xsession-errors (9 sec old) ---------------------
JACK tmpdir identified as [/dev/shm]
** Message: don't know how to handle video/x-xvid, framerate=(fraction)25/1, width=(int)656, height=(int)288
JACK tmpdir identified as [/dev/shm]
** Message: Missing plugin: gstreamer.net|0.10|totem|XVID MPEG-4 decoder|decoder-video/x-xvid (XVID MPEG-4 decoder)
** Message: Automatic missing codec installation not supported (helper script missing)
JACK tmpdir identified as [/dev/shm]
error : xmlEncodeEntitiesReentrant : input not UTF-8
error : xmlEncodeEntitiesReentrant : char out of range
Xlib: unexpected async reply (sequence 0x3278b)!
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
(totem:5918): GStreamer-WARNING **: Failed to load plugin '/usr/lib/gstreamer-0.10/libgsticydemux.so': /usr/lib/gstreamer-0.10/libgsticydemux.so: undefined symbol: gst_tag_freeform_string_to_utf8
(totem:5918): GStreamer-WARNING **: Failed to load plugin '/usr/lib/gstreamer-0.10/libgstrtpmanager.so': /usr/lib/gstreamer-0.10/libgstrtpmanager.so: undefined symbol: gst_rtcp_packet_bye_set_reason
--------------------------------------------------
Comment 1 Jonathan Matthew 2008-01-06 08:15:24 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 465946 ***