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 541639 - crash in Rhythmbox Music Player: die letzte Aktivierung e...
crash in Rhythmbox Music Player: die letzte Aktivierung e...
Status: RESOLVED DUPLICATE of bug 523463
Product: rhythmbox
Classification: Other
Component: general
0.11.x
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-07-05 08:47 UTC by walter
Modified: 2008-11-11 02:45 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description walter 2008-07-05 08:47:50 UTC 
Version: 0.11.5

What were you doing when the application crashed?
die letzte Aktivierung eingespielt und dann die Hardwaredatenbank geprüft.


Distribution: Ubuntu 8.04 (hardy)
Gnome Release: 2.22.2 2008-06-03 (Ubuntu)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-19-generic #1 SMP Wed Jun 18 14:43:41 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 95051776 vsize: 95051776 resident: 36171776 share: 18587648 rss: 36171776 rss_rlim: 4294967295
CPU usage: start_time: 1215247451 rtime: 171 utime: 158 stime: 13 cutime:1 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/rhythmbox'

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb65b2740 (LWP 11984)]
[New Thread 0xb3952b90 (LWP 11999)]
[New Thread 0xb4b52b90 (LWP 11997)]
(no debugging symbols found)
0xb7f9b410 in __kernel_vsyscall ()

+ Trace 202095

Thread 1 (Thread 0xb65b2740 (LWP 11984))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #7 ??
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #9 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #10 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (249 sec old) ---------------------
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
new doRestore
[1215246838336] (4): Skipping no location: chrome://browser/content/sanitize.xul
/usr/lib/bug-buddy/exaile.py: No such file or directory.
hwdb.ubuntu.com
Fenstermanager-Warnung: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x260005a (BMP)
Fenstermanager-Warnung: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------
Comment 1 Jonathan Matthew 2008-11-11 02:45:42 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 523463 ***