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 464591 - crash in Rhythmbox Music Player: 特に何もしていない
crash in Rhythmbox Music Player: 特に何もしていない
Status: RESOLVED DUPLICATE of bug 409540
Product: rhythmbox
Classification: Other
Component: general
0.10.0
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-08-08 06:40 UTC by katsuma
Modified: 2007-08-21 13:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description katsuma 2007-08-08 06:40:29 UTC 
What were you doing when the application crashed?
特に何もしていない


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.20-2925.13.fc7xen #1 SMP Tue Jul 17 10:38:27 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: 217624576 vsize: 217624576 resident: 47562752 share: 29188096 rss: 47562752 rss_rlim: 4294967295
CPU usage: start_time: 1186546648 rtime: 18185 utime: 16033 stime: 2152 cutime:2 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/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208494368 (LWP 2266)]
[New Thread -1278923888 (LWP 3791)]
[New Thread -1268434032 (LWP 3789)]
[New Thread -1354441840 (LWP 3788)]
[New Thread -1332663408 (LWP 3725)]
[New Thread -1300718704 (LWP 3724)]
[New Thread -1289835632 (LWP 3723)]
[New Thread -1311683696 (LWP 3720)]
[New Thread -1343951984 (LWP 3718)]
[New Thread -1311417456 (LWP 2290)]
[New Thread -1257944176 (LWP 2273)]
(no debugging symbols found)
0x00bf1402 in __kernel_vsyscall ()

+ Trace 153641

Thread 1 (Thread -1208494368 (LWP 2266))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/nosegneg/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/i686/nosegneg/libc.so.6
  • #6 abort
    from /lib/i686/nosegneg/libc.so.6
  • #7 g_logv
    from /lib/libglib-2.0.so.0
  • #8 g_log
    from /lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /lib/libglib-2.0.so.0
  • #10 rb_shell_preferences_new
  • #11 ??
  • #12 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #13 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #14 ??
    from /lib/libgobject-2.0.so.0
  • #15 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #16 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #17 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 gtk_action_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #20 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #21 ??
    from /lib/libgobject-2.0.so.0
  • #22 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #23 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #24 gtk_widget_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 gtk_menu_shell_activate_item
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #29 ??
    from /lib/libgobject-2.0.so.0
  • #30 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #31 ??
    from /lib/libgobject-2.0.so.0
  • #32 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #33 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #34 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #35 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #36 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #37 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #38 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #39 ??
    from /lib/libglib-2.0.so.0
  • #40 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #41 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #42 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (104556 sec old) ---------------------
scsi_read error: sector=206199 length=1 retry=5
                 Sense key: 2 ASC: 3a ASCQ: 2
                 Transport error: Device busy
                 System error: デバイスもしくはリソースがビジー状態です
scsi_read error: sector=206199 length=1 retry=6
                 Sense key: 2 ASC: 3a ASCQ: 2
                 Transport error: Device busy
                 System error: デバイスもしくはリソースがビジー状態です
scsi_read error: sector=206199 length=1 retry=7
                 Sense key: 2 ASC: 3a ASCQ: 2
                 Transport error: Device busy
                 System error: デバイスもしくはリソースがビジー状態です
scsi_read error: sector=206199 length=1 retry=8
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-08-21 13:08:01 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 409540 ***