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 542936 - crash in Rhythmbox Music Player: Connected a Nokia 770 wi...
crash in Rhythmbox Music Player: Connected a Nokia 770 wi...
Status: RESOLVED DUPLICATE of bug 510236
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-14 15:13 UTC by gt
Modified: 2008-07-21 23:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description gt 2008-07-14 15:13:28 UTC
Version: 0.11.5

What were you doing when the application crashed?
Connected a Nokia 770 with media on it.	


Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 114880512 vsize: 114880512 resident: 35565568 share: 18300928 rss: 35565568 rss_rlim: 4294967295
CPU usage: start_time: 1216048380 rtime: 121 utime: 105 stime: 16 cutime:1 cstime: 2 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/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb65bc9c0 (LWP 25943)]
[New Thread 0xb3339b90 (LWP 25974)]
[New Thread 0xb5fe0b90 (LWP 25970)]
[New Thread 0xb2b38b90 (LWP 25968)]
[New Thread 0xb433bb90 (LWP 25956)]
[New Thread 0xb4ce8b90 (LWP 25955)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb65bc9c0 (LWP 25943))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/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 rhythmdb_entry_allocate
    from /usr/lib/librhythmbox-core.so.0
  • #7 rhythmdb_entry_new
    from /usr/lib/librhythmbox-core.so.0
  • #8 ??
    from /usr/lib/librhythmbox-core.so.0
  • #9 ??
  • #10 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
(firefox-bin:17396): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
** (gnome-panel:4680): WARNING **: Failed to establish a connection with GDM: No such file or directory
** (gnome-panel:4680): WARNING **: Failed to establish a connection with GDM: No such file or directory
kbuildsycoca running...
Reusing existing ksycoca
** (gnome-panel:4680): WARNING **: Failed to establish a connection with GDM: No such file or directory
kbuildsycoca running...
Reusing existing ksycoca
Avviso del window manager: Received a _NET_WM_MOVERESIZE message for 0x12006fd (N95); these messages lack timestamps and therefore suck.
closing
Avviso del window manager: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3600022 (Riprodutto)
Avviso del window manager: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------
Comment 1 Susana 2008-07-21 06:27:59 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Comment 2 Susana 2008-07-21 06:28:17 UTC
*** Bug 543343 has been marked as a duplicate of this bug. ***
Comment 3 André Klapper 2008-07-21 21:52:43 UTC
*** Bug 543343 has been marked as a duplicate of this bug. ***
Comment 4 Susana 2008-07-21 23:12:34 UTC
Matches trace in bug 543343 which is a dupe of bug 510236.

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 510236 ***