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 500988 - crash in Rhythmbox Music Player: Viewing the lyrics using...
crash in Rhythmbox Music Player: Viewing the lyrics using...
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: 2007-12-02 08:23 UTC by stephen84s
Modified: 2007-12-02 08:36 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description stephen84s 2007-12-02 08:23:53 UTC
Version: 0.10.1

What were you doing when the application crashed?
Viewing the lyrics using the Song lyrics plugin of Rhythmbox 


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.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Bluecurve
Icon Theme: Bluecurve

Memory status: size: 227901440 vsize: 227901440 resident: 58339328 share: 41803776 rss: 58339328 rss_rlim: 4294967295
CPU usage: start_time: 1196583323 rtime: 1130 utime: 1037 stime: 93 cutime:3 cstime: 1 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 -1208878544 (LWP 5450)]
[New Thread -1314104432 (LWP 5500)]
[New Thread -1368392816 (LWP 5499)]
[New Thread -1380975728 (LWP 5498)]
[New Thread -1356698736 (LWP 5485)]
[New Thread -1346208880 (LWP 5484)]
[New Thread -1335719024 (LWP 5483)]
[New Thread -1325229168 (LWP 5482)]
[New Thread -1303614576 (LWP 5480)]
[New Thread -1269347440 (LWP 5479)]
[New Thread -1281565808 (LWP 5456)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 4 (Thread -1380975728 (LWP 5498))

  • #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 g_hash_table_foreach
    from /lib/libglib-2.0.so.0
  • #8 ??
  • #9 g_hash_table_foreach
    from /lib/libglib-2.0.so.0
  • #10 ??
  • #11 g_hash_table_foreach
    from /lib/libglib-2.0.so.0
  • #12 ??
  • #13 g_hash_table_foreach
    from /lib/libglib-2.0.so.0
  • #14 ??
  • #15 ??
  • #16 ??
  • #17 g_hash_table_foreach
    from /lib/libglib-2.0.so.0
  • #18 rhythmdb_entry_type_foreach
  • #19 ??
  • #20 ??
  • #21 ??
    from /lib/libglib-2.0.so.0
  • #22 start_thread
    from /lib/libpthread.so.0
  • #23 clone
    from /lib/libc.so.6


----------- .xsession-errors (39 sec old) ---------------------
QLayout: Adding KToolBar/mainToolBar (child of QVBox/unnamed) to layout for PlaylistWindow/PlaylistWindow
QObject::connect: Incompatible sender/receiver arguments
	StarManager::ratingsColorsChanged() --> ContextBrowser::ratingOrScoreOrLabelsChanged(const QString&)
Amarok: [Loader] Starting amarokapp..
Amarok: [Loader] Don't run gdb, valgrind, etc. against this binary! Use amarokapp.
QObject::disconnect: Unexpected null parameter
QObject::connect: Cannot connect (null)::activePartChanged( KParts::Part * ) to KHTMLPart::slotActiveFrameChanged( KParts::Part * )
QLayout "unnamed" added to QVBox "unnamed", which already has a layout
QLayout: Adding KToolBar/mainToolBar (child of QVBox/unnamed) to layout for PlaylistWindow/PlaylistWindow
QObject::connect: Incompatible sender/receiver arguments
	StarManager::ratingsColorsChanged() --> ContextBrowser::ratingOrScoreOrLabelsChanged(const QString&)
Amarok: [Loader] Starting amarokapp..
Amarok: [Loader] Don't run gdb, valgrind, etc. against this binary! Use amarokapp.
ICE default IO error handler doing an exit(), pid = 5425, errno = 0
Xlib: unexpected async reply (sequence 0x1a4b0)!
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-12-02 08:36:40 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 ***