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 460742 - crash in Sound Juicer CD Extractor: cdから曲の取り込み
crash in Sound Juicer CD Extractor: cdから曲の取り込み
Status: RESOLVED DUPLICATE of bug 403870
Product: sound-juicer
Classification: Applications
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: Sound Juicer Maintainers
Sound Juicer Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-07-26 20:30 UTC by setaka_06
Modified: 2007-09-30 15:00 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description setaka_06 2007-07-26 20:30:04 UTC
Version: 2.16.4

What were you doing when the application crashed?
cdから曲の取り込み


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-27.fc7 #1 SMP Tue Jul 17 17:13:26 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: 86077440 vsize: 86077440 resident: 28217344 share: 21200896 rss: 28217344 rss_rlim: 4294967295
CPU usage: start_time: 1185481556 rtime: 316 utime: 281 stime: 35 cutime:14 cstime: 5 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/sound-juicer'

(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 -1208169600 (LWP 2864)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208169600 (LWP 2864))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ??
  • #5 filepath_parse_pattern
  • #6 ??
  • #7 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #8 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #9 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #10 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #11 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #12 gtk_button_clicked
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #15 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #16 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #17 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #18 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #19 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #20 gtk_button_released
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #24 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #25 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #26 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #27 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #28 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgtk-x11-2.0.so.0
  • #29 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #31 g_cclosure_marshal_VOID__VOID
    from /usr/lib/libgdk-x11-2.0.so.0
  • #32 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #33 g_cclosure_marshal_VOID__VOID
    from /lib/libglib-2.0.so.0
  • #34 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #35 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #36 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (117 sec old) ---------------------
Starting SCIM as daemon ...
Launching a SCIM process with x11...
Loading socket Config module ...
Creating backend ...
Loading x11 FrontEnd module ...
GTK Panel of SCIM 1.4.5
Starting SCIM as daemon ...
SCIM has been successfully launched.
Smart Common Input Method 1.4.5
SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2624
could not attach to desktop process
** (sound-juicer:2864): WARNING **: Could not lock drive: CD から楽曲の取り込み中
--------------------------------------------------
Comment 1 Ross Burton 2007-09-30 15:00:01 UTC

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