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 505234 - crash in Rhythmbox Music Player: opening rhythmbox from a...
crash in Rhythmbox Music Player: opening rhythmbox from a...
Status: RESOLVED DUPLICATE of bug 499208
Product: rhythmbox
Classification: Other
Component: general
0.11.x
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-12-23 14:58 UTC by Basilio Kublik
Modified: 2007-12-27 08:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Basilio Kublik 2007-12-23 14:58:09 UTC 
Version: 0.11.4

What were you doing when the application crashed?
opening rhythmbox from a jhbuild environment


Distribution: Ubuntu 8.04 (hardy)
Gnome Release: 2.21.4 2007-12-22 (JHBuild)
BugBuddy Version: 2.20.1

System: Linux 2.6.24-2-generic #1 SMP Thu Dec 20 17:36:12 GMT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 78450688 vsize: 78450688 resident: 20844544 share: 15724544 rss: 20844544 rss_rlim: 4294967295
CPU usage: start_time: 1198421860 rtime: 85 utime: 78 stime: 7 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/gnome2/bin/rhythmbox'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb63dbae0 (LWP 20233)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 182782

Thread 1 (Thread 0xb63dbae0 (LWP 20233))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at gspawn.c line 682
  • #4 run_bug_buddy
    at gnome-breakpad.cc line 213
  • #5 check_if_gdb
    at gnome-breakpad.cc line 283
  • #6 google_breakpad::ExceptionHandler::InternalWriteMinidump
    at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 225
  • #7 google_breakpad::ExceptionHandler::HandleException
    at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 196
  • #8 <signal handler called>
  • #9 main
    at main.c line 325
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
** (empathy:6143): DEBUG: dbus_async_cb: Error: Message did not receive a reply (timeout by message bus) (4)
(xchat-gnome:20186): Gdk-CRITICAL **: gdk_pixmap_new: assertion `(width != 0) && (height != 0)' failed
(xchat-gnome:20186): Gdk-CRITICAL **: gdk_pixmap_new: assertion `(width != 0) && (height != 0)' failed
(xchat-gnome:20186): Gdk-CRITICAL **: gdk_pixmap_new: assertion `(width != 0) && (height != 0)' failed
Window manager warning: Log level 16: Could not get attrs
Window manager warning: Log level 16: Could not get attrs
Window manager warning: Log level 16: Could not get attrs
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3800021 (Music Play)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Log level 16: Could not get attrs
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3800021 (Music Play)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-12-27 08:32:46 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 499208 ***