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 389044 - crash in Sound Juicer CD Extractor:
crash in Sound Juicer CD Extractor:
Status: RESOLVED FIXED
Product: sound-juicer
Classification: Applications
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: Sound Juicer Maintainers
Sound Juicer Maintainers
: 387585 391974 408891 418385 444013 456718 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-12-23 22:13 UTC by thelema
Modified: 2014-03-24 16:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Attachments
Don't crash if the device exists but nautilus-burn does not know about it (1.21 KB, patch)
2007-03-17 21:21 UTC, Pascal Terjan
committed Details | Review

Description thelema 2006-12-23 22:13:33 UTC
Version: 2.16.2

What were you doing when the application crashed?



Distribution: Mandriva Linux release 2007.1 (Cooker) for i586
Gnome Release: 2.17.2 2006-11-30 (Mandriva)
BugBuddy Version: 2.17.3

System: Linux 2.6.14-0.mm.s.5mdkcustom #1 Wed Jul 5 00:18:33 EAT 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Enabled

Memory status: size: 69775360 vsize: 0 resident: 69775360 share: 0 rss: 16199680 rss_rlim: 0
CPU usage: start_time: 1166911785 rtime: 0 utime: 74 stime: 0 cutime:69 cstime: 0 timeout: 5 it_real_value: 0 frequency: 6

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/libthread_db.so.1".
(no debugging symbols found)
`shared object read from target memory' has disappeared; keeping its symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1228880176 (LWP 5627)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()
  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/i686/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/i686/libc.so.6
  • #6 abort
    from /lib/i686/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 cd_drive_exists
  • #11 on_reread_activate
  • #12 main

Thread 1 (Thread -1228880176 (LWP 5627)):
#-1 0xffffe410 in __kernel_vsyscall ()
No symbol table info available.


----------- .xsession-errors (8 sec old) ---------------------
Window manager warning: Log level 8: gtk_widget_get_parent: assertion `GTK_IS_WIDGET (widget)' failed
Window manager warning: Log level 8: gtk_widget_get_parent: assertion `GTK_IS_WIDGET (widget)' failed
Window manager warning: Log level 8: gtk_widget_get_parent: assertion `GTK_IS_WIDGET (widget)' failed
Window manager warning: Log level 8: gtk_widget_get_parent: assertion `GTK_IS_WIDGET (widget)' failed
Window manager warning: Log level 8: gtk_widget_get_parent: assertion `GTK_IS_WIDGET (widget)' failed
Window manager warning: Log level 8: gtk_widget_get_parent: assertion `GTK_IS_WIDGET (widget)' failed
Window manager warning: Log level 8: gtk_widget_get_parent: assertion `GTK_IS_WIDGET (widget)' failed
Window manager warning: Log level 8: gtk_widget_get_parent: assertion `GTK_IS_WIDGET (widget)' failed
Window manager warning: Log level 8: gtk_widget_get_parent: assertion `GTK_IS_WIDGET (widget)' failed
Window manager warning: Log level 8: gtk_widget_get_parent: assertion `GTK_IS_WIDGET (widget)' failed
Window manager warning: Log level 8: gtk_widget_get_parent: assertion `GTK_IS_WIDGET (widget)' failed
Window manager warning: Log level 8: gtk_widget_get_parent: assertion `GTK_IS_WIDGET (widget)' failed
Window manager warning: Log level 8: gtk_widget_get_parent: assertion `GTK_IS_WIDGET (widget)' failed
Window manager warning: Log level 8: gtk_widget_get_parent: assertion `GTK_IS_WIDGET (widget)' failed
Window manager warning: Log level 8: gtk_widget_get_parent: assertion `GTK_IS_WIDGET (widget)' failed
--------------------------------------------------
Comment 1 thelema 2006-12-24 00:18:27 UTC
sound-juicer wouldn't see my CD drive (it told me so when it tried to start), so I tried -d /dev/cdrom, and it died this way.  Could be many library problems - I'm running mandriva cooker.
Comment 2 Pedro de Medeiros 2006-12-26 13:11:51 UTC
*** Bug 387585 has been marked as a duplicate of this bug. ***
Comment 3 Pedro de Medeiros 2006-12-26 13:12:32 UTC
Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 4 liox 2006-12-27 13:59:06 UTC
ok, I recompiled glib, gtk+, gnome-vfs and sound-juicer with the instruction the gnome page gave me and the debug use flag.
Now the output of bug-buddy:

Distribution: Gentoo Base System version 1.12.6
Gnome Release: 2.16.2 2006-12-12 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 69787648 vsize: 0 resident: 69787648 share: 0 rss: 13971456 rss_rlim: 0
CPU usage: start_time: 1167227154 rtime: 0 utime: 75 stime: 0 cutime:72 cstime: 0 timeout: 3 it_real_value: 0 frequency: 6

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

Using host libthread_db library "/lib/libthread_db.so.1".
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1230109008 (LWP 26992)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1230109008 (LWP 26992))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 IA__g_logv
  • #5 IA__g_log
  • #6 IA__g_assert_warning
    at gmessages.c line 552
  • #7 set_drive_from_device
    at sj-main.c line 808
  • #8 set_device
    at sj-main.c line 848
  • #9 main
    at sj-main.c line 1531
  • #0 __kernel_vsyscall

and now the output I see if I call the sound-juicer on a console:
sound-juicer --device=/dev/dvd

** (sound-juicer:27009): WARNING **: hal_initialize failed: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory

** ERROR **: file sj-main.c: line 808 (set_drive_from_device): assertion failed: (drive)
aborting...


if I call sound-juicer without the --device option it does not find any of my cd drives just like thelema@swbell.net reports
hope this helps 
By Liox

Comment 5 Pedro de Medeiros 2007-01-05 03:57:09 UTC
*** Bug 391974 has been marked as a duplicate of this bug. ***
Comment 6 Susana 2007-02-17 13:48:35 UTC
*** Bug 408891 has been marked as a duplicate of this bug. ***
Comment 7 Christian Kirbach 2007-03-15 20:07:58 UTC
*** Bug 418385 has been marked as a duplicate of this bug. ***
Comment 8 Christian Kirbach 2007-03-15 20:37:49 UTC
excellent trace from liox, confirming report.
Comment 9 Christian Kirbach 2007-03-15 20:39:07 UTC
sorry for the spam
Comment 10 Pascal Terjan 2007-03-17 21:21:37 UTC
Created attachment 84790 [details] [review]
Don't crash if the device exists but nautilus-burn does not know about it

Here is a patch avoiding the crash
Comment 11 Ross Burton 2007-03-20 09:42:35 UTC
That patch looks good but has string changes, so will have to wait for the branch.

I shall branch shortly, I promise.
Comment 12 Ross Burton 2007-03-26 09:37:25 UTC
Committed, thanks.
Comment 13 Pedro Villavicencio 2007-06-05 00:22:41 UTC
*** Bug 444013 has been marked as a duplicate of this bug. ***
Comment 14 Susana 2007-07-14 22:40:52 UTC
*** Bug 456718 has been marked as a duplicate of this bug. ***