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 461687 - crash in Rhythmbox Music Player: closing the program
crash in Rhythmbox Music Player: closing the program
Status: RESOLVED DUPLICATE of bug 434003
Product: rhythmbox
Classification: Other
Component: general
0.10.0
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-07-30 04:57 UTC by romopo
Modified: 2007-08-02 10:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description romopo 2007-07-30 04:57:22 UTC
What were you doing when the application crashed?
closing the program


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-33.fc7 #1 SMP Mon Jul 23 17:33:07 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 96071680 vsize: 96071680 resident: 33333248 share: 22228992 rss: 33333248 rss_rlim: 4294967295
CPU usage: start_time: 1185771367 rtime: 287 utime: 250 stime: 37 cutime:4 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 -1208894928 (LWP 4635)]
[New Thread -1220596848 (LWP 4648)]
[New Thread -1244918896 (LWP 4645)]
[New Thread -1234429040 (LWP 4642)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 2 (Thread -1220596848 (LWP 4648))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 g_logv
    from /lib/libglib-2.0.so.0
  • #8 g_log
    from /lib/libglib-2.0.so.0
  • #9 ??
    from /lib/libgthread-2.0.so.0
  • #10 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #11 ??
  • #12 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #13 ??
  • #14 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #15 ??
  • #16 free
    from /lib/libc.so.6


----------- .xsession-errors (34 sec old) ---------------------
localuser:Ryan being added to access control list
SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2653
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a0005b (OpenOffice)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name org.freedesktop.NetworkManager was not provided by any .service files
Window manager warning: Received a NET_CURRENT_DESKTOP message from a broken (outdated) client who sent a 0 timestamp
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3200021 (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-08-02 10:35: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 434003 ***