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 552795 - crash in Rhythmbox: Connecting my N800 to th...
crash in Rhythmbox: Connecting my N800 to th...
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-09-18 16:22 UTC by Hubert Figuiere (:hub)
Modified: 2008-09-23 10:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Hubert Figuiere (:hub) 2008-09-18 16:22:05 UTC 
Version: 0.11.5

What were you doing when the application crashed?
Connecting my N800 to the PC. This is a different stack trace.


Distribution: openSUSE 11.0 (X86-64)
Gnome Release: 2.22.1 2008-06-07 (SUSE)
BugBuddy Version: 2.22.0

System: Linux 2.6.25.5-1.1-default #1 SMP 2008-06-07 01:55:22 +0200 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 601796608 vsize: 601796608 resident: 55926784 share: 20770816 rss: 55926784 rss_rlim: 18446744073709551615
CPU usage: start_time: 1221754757 rtime: 95 utime: 82 stime: 13 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

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

[?1034h[Thread debugging using libthread_db enabled]
[New Thread 0x7fa3494de770 (LWP 17976)]
[New Thread 0x435c5950 (LWP 17985)]
[New Thread 0x42dc4950 (LWP 17982)]
[New Thread 0x425c3950 (LWP 17981)]
0x00007fa33ef7664f in waitpid () from /lib64/libpthread.so.0

+ Trace 206945

Thread 1 (Thread 0x7fa3494de770 (LWP 17976))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib64/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib64/libglib-2.0.so.0
  • #3 ??
    from /usr/lib64/gtk-2.0/modules/libgnomebreakpad.so
  • #4 ??
    from /usr/lib64/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 rhythmdb_entry_allocate
    at rhythmdb.c line 1210
  • #7 rhythmdb_entry_new
    at rhythmdb.c line 1319
  • #8 rhythmdb_add_import_error_entry
    at rhythmdb.c line 1858
  • #9 rhythmdb_process_metadata_load_real
    at rhythmdb.c line 1898
  • #10 rhythmdb_process_one_event
    at rhythmdb.c line 2072
  • #11 rb_async_queue_watch_dispatch
    at rb-async-queue-watch.c line 61
  • #12 g_main_context_dispatch
    from /usr/lib64/libglib-2.0.so.0
  • #13 ??
    from /usr/lib64/libglib-2.0.so.0
  • #14 g_main_loop_run
    from /usr/lib64/libglib-2.0.so.0
  • #15 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #16 main
    at main.c line 327
  • #0 waitpid
    from /lib64/libpthread.so.0 


----------- .xsession-errors ---------------------
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
Xlib:  extension "Generic Event Extension" missing on display ":0.0".
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Jonathan Matthew 2008-09-23 10:47:43 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 510236 ***