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 473472 - crash in Rhythmbox Music Player: I just clicked on magnat...
crash in Rhythmbox Music Player: I just clicked on magnat...
Status: RESOLVED DUPLICATE of bug 436456
Product: rhythmbox
Classification: Other
Component: general
0.10.0
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-09-04 07:37 UTC by Bjørn Erik Halvorsen
Modified: 2007-09-09 04:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Bjørn Erik Halvorsen 2007-09-04 07:37:38 UTC
What were you doing when the application crashed?
I just clicked on magnatune


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-41.fc7 #1 SMP Fri Jul 27 18:21:43 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Gion

Memory status: size: 1017462784 vsize: 1017462784 resident: 320249856 share: 33824768 rss: 320249856 rss_rlim: 18446744073709551615
CPU usage: start_time: 1188888816 rtime: 10556 utime: 8857 stime: 1699 cutime:6 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496449488 (LWP 4659)]
[New Thread 1126189392 (LWP 4785)]
[New Thread 1105209680 (LWP 4784)]
[New Thread 1084229968 (LWP 4783)]
[New Thread 1157658960 (LWP 4782)]
[New Thread 1094719824 (LWP 4781)]
[New Thread 1136679248 (LWP 4780)]
[New Thread 1147169104 (LWP 4779)]
[New Thread 1115699536 (LWP 4667)]
(no debugging symbols found)
0x0000003016e0d97f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912496449488 (LWP 4659))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 ??
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib64/libc.so.6
  • #4 abort
    from /lib64/libc.so.6
  • #5 __assert_fail
    from /lib64/libc.so.6
  • #6 PyEval_EvalCodeEx
    from /usr/lib64/libpython2.5.so.1.0
  • #7 ??
    from /usr/lib64/libpython2.5.so.1.0
  • #8 PyObject_Call
    from /usr/lib64/libpython2.5.so.1.0
  • #9 ??
    from /usr/lib64/libpython2.5.so.1.0
  • #10 PyObject_Call
    from /usr/lib64/libpython2.5.so.1.0
  • #11 PyEval_CallObjectWithKeywords
    from /usr/lib64/libpython2.5.so.1.0
  • #12 ??
  • #13 ??
  • #14 ??
  • #15 ??
    from /lib64/libglib-2.0.so.0
  • #16 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #17 ??
    from /lib64/libglib-2.0.so.0
  • #18 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #19 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #20 main
  • #0 waitpid
    from /lib64/libpthread.so.0


----------- .xsession-errors (3697 sec old) ---------------------
(evolution:4096): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid
(evolution:4096): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid
(evolution:4096): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid
(evolution:4096): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-09-09 04:27:10 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 ***