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 399915 - crash in Rhythmbox Music Player: eigentlich gar nichts, h...
crash in Rhythmbox Music Player: eigentlich gar nichts, h...
Status: RESOLVED DUPLICATE of bug 373226
Product: rhythmbox
Classification: Other
Component: general
0.9.6
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-01-23 19:52 UTC by martinvogel
Modified: 2007-01-25 02:57 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description martinvogel 2007-01-23 19:52:27 UTC 
What were you doing when the application crashed?
eigentlich gar nichts, habe eine verbindung zu radiosendeer aufgebaut und laufen lassen. boote von live cd ( ubuntu ), habe von linux keine große ahnung, geschweige denn von der entwicklung!							


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 117866496 vsize: 0 resident: 117866496 share: 0 rss: 25825280 rss_rlim: 0
CPU usage: start_time: 1169581437 rtime: 0 utime: 774 stime: 0 cutime:722 cstime: 0 timeout: 52 it_real_value: 0 frequency: 8

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1228675408 (LWP 7078)]
[New Thread -1300034656 (LWP 7213)]
[New Thread -1291641952 (LWP 7209)]
[New Thread -1282856032 (LWP 7206)]
[New Thread -1252176992 (LWP 7205)]
[New Thread -1270551648 (LWP 7204)]
[New Thread -1279198304 (LWP 7203)]
[New Thread -1262113888 (LWP 7091)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 104663

Thread 1 (Thread -1228675408 (LWP 7078))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #10 fs_module_create
    from /usr/lib/gtk-2.0/2.10.0/filesystems/libgnome-vfs.so
  • #11 g_object_unref
    from /usr/lib/libgobject-2.0.so.0
  • #12 fs_module_init
    from /usr/lib/gtk-2.0/2.10.0/filesystems/libgnome-vfs.so
  • #13 gnome_vfs_connect_to_server
    from /usr/lib/libgnomevfs-2.so.0
  • #14 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #15 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #16 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #17 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #18 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 main
  • #0 __kernel_vsyscall 






Comment 1


André Klapper





          2007-01-25 02:57:21 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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