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 491656 - crash in Rhythmbox Music Player: This bug appears always ...
crash in Rhythmbox Music Player: This bug appears always ...
Status: RESOLVED DUPLICATE of bug 484988
Product: rhythmbox
Classification: Other
Component: general
0.11.x
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-30 10:11 UTC by luca.cerrone
Modified: 2007-10-30 11:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description luca.cerrone 2007-10-30 10:11:14 UTC
Version: 0.11.2

What were you doing when the application crashed?
This bug appears always when i close rhythmbox.


Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-2-amd64 #1 SMP Thu Aug 30 23:43:59 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 527241216 vsize: 527241216 resident: 45019136 share: 23134208 rss: 45019136 rss_rlim: 18446744073709551615
CPU usage: start_time: 1193737485 rtime: 18824 utime: 17755 stime: 1069 cutime:0 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 0x2b3f52a99890 (LWP 6123)]
[New Thread 0x41843950 (LWP 6384)]
[New Thread 0x41001950 (LWP 6141)]
(no debugging symbols found)
0x00002b3f499d9c7f in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0x2b3f52a99890 (LWP 6123))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 ??
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 ??
  • #4 ??
    from /lib/libpthread.so.0
  • #5 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #6 ??
    from /usr/lib/libglib-2.0.so.0
  • #7 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #8 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #9 main
  • #0 waitpid
    from /lib/libpthread.so.0


----------- .xsession-errors (1353 sec old) ---------------------
LoadPlugin: failed to initialize shared library /home/luca/.mozilla/plugins/libflashplayer.so [/home/luca/.mozilla/plugins/libflashplayer.so: wrong ELF class: ELFCLASS32]
FG: canHandleContent application/vnd.mozilla.maybe.feed)
FG: _shouldIntercept(application/vnd.mozilla.maybe.feed)
LoadPlugin: failed to initialize shared library /home/luca/.mozilla/plugins/libflashplayer.so [/home/luca/.mozilla/plugins/libflashplayer.so: wrong ELF class: ELFCLASS32]
FG: canHandleContent application/vnd.mozilla.maybe.feed)
FG: _shouldIntercept(application/vnd.mozilla.maybe.feed)
LoadPlugin: failed to initialize shared library /home/luca/.mozilla/plugins/libflashplayer.so [/home/luca/.mozilla/plugins/libflashplayer.so: wrong ELF class: ELFCLASS32]
FG: canHandleContent application/vnd.mozilla.maybe.feed)
FG: _shouldIntercept(application/vnd.mozilla.maybe.feed)
LoadPlugin: failed to initialize shared library /home/luca/.mozilla/plugins/libflashplayer.so [/home/luca/.mozilla/plugins/libflashplayer.so: wrong ELF class: ELFCLASS32]
FG: canHandleContent application/vnd.mozilla.maybe.feed)
FG: _shouldIntercept(application/vnd.mozilla.maybe.feed)
LoadPlugin: failed to initialize shared library /home/luca/.mozilla/plugins/libflashplayer.so [/home/luca/.mozilla/plugins/libflashplayer.so: wrong ELF class: ELFCLASS32]
FG: canHandleContent application/vnd.mozilla.maybe.feed)
FG: _shouldIntercept(application/vnd.mozilla.maybe.feed)
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-10-30 11:58:45 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 484988 ***