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 151552 - GNOME CD crashes
GNOME CD crashes
Status: RESOLVED FIXED
Product: gnome-media
Classification: Deprecated
Component: Gnome-CD
unspecified
Other Linux
: Normal critical
: 2.8.0
Assigned To: gnome media maintainers
gnome media maintainers
Depends on:
Blocks:
 
 
Reported: 2004-08-31 21:29 UTC by Kjartan Maraas
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: 2.8.x
GNOME version: ---

Attachments
patch to fix crash and reading of gconf key (4.26 KB, patch)
2004-08-31 22:45 UTC, Kjartan Maraas 		none Details | Review

Description Kjartan Maraas 2004-08-31 21:29:11 UTC 
While trying out a patch for a crash on startup with the latest release (2.7.92)
I still see crashing, this time the window comes up before it explodes though:

(lt-gnome-cd:30012): GLib-CRITICAL **: file gstrfuncs.c: line 1743
(g_ascii_strcasecmp): assertion `s1 != NULL' failed

** (lt-gnome-cd:30012): WARNING **: Could not contact CDDB server
Segmentation fault

+ Trace 49790

  • #0 gdk_draw_pixbuf
    at gdkdraw.c line 771
  • #1 gdk_pixbuf_render_to_drawable_alpha
    at gdkpixbuf-render.c line 221
  • #2 draw_pixbuf
    at display.c line 215
  • #3 expose_event
    at display.c line 271
  • #4 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 82
  • #5 g_type_class_meta_marshal
    at gclosure.c line 514
  • #6 g_closure_invoke
    at gclosure.c line 437
  • #7 signal_emit_unlocked_R
    at gsignal.c line 2473
  • #8 g_signal_emit_valist
    at gsignal.c line 2204
  • #9 g_signal_emit
    at gsignal.c line 2238
  • #10 gtk_widget_event_internal
    at gtkwidget.c line 3563
  • #11 gtk_main_do_event
    at gtkmain.c line 1542
  • #12 gdk_window_process_updates_internal
    at gdkwindow.c line 2052
  • #13 gdk_window_process_all_updates
    at gdkwindow.c line 2099
  • #14 gdk_window_update_idle
    at gdkwindow.c line 2113
  • #15 g_idle_dispatch
    at gmain.c line 3802
  • #16 g_main_context_dispatch
    at gmain.c line 1942
  • #17 g_main_context_iterate
    at gmain.c line 2573
  • #18 g_main_loop_run
    at gmain.c line 2777
  • #19 bonobo_main
    at bonobo-main.c line 297
  • #20 main
    at gnome-cd.c line 865 






Comment 1


Kjartan Maraas





          2004-08-31 21:44:26 UTC
        



==30107== Use of uninitialised value of size 4
==30107==    at 0x853C57: _itoa_word (in /lib/tls/libc-2.3.3.so)
==30107==    by 0x856FB9: _IO_vfprintf_internal (in /lib/tls/libc-2.3.3.so)
==30107==    by 0x86F3CA: _IO_vsprintf_internal (in /lib/tls/libc-2.3.3.so)
==30107==    by 0x85D1EA: __GI_sprintf (in /lib/tls/libc-2.3.3.so)
==30107==    by 0x805436C: cddb_sum (cddb.c:260)
==30107==    by 0x80571D1: gst_cdparanoia_cdrom_get_cddb_data
(gst-cdparanoia-cdrom.c:1233)
==30107==    by 0x80508B3: gnome_cd_build_track_list_menu (gnome-cd.c:210)
==30107==    by 0x8051865: main (gnome-cd.c:632)







Comment 2


Kjartan Maraas





          2004-08-31 22:41:23 UTC
        



And here's a backtrace from the GLib-CRITICAL:

GLib-CRITICAL **: file gstrfuncs.c: line 1743 (g_ascii_strcasecmp): assertion
`s1 != NULL' failed
aborting...

Program received signal SIGABRT, Aborted.




+
Trace
    49791






Thread NaN
          (LWP 30131)


    

  • 
#0
??

    
                at rtld.c
                  line
                  576

    

    • 

  • 
#1
*__GI_raise

    
                at ../nptl/sysdeps/unix/sysv/linux/raise.c
                  line
                  67

    

    • 

  • 
#2
*__GI_abort

    
                at ../sysdeps/generic/abort.c
                  line
                  88

    

    • 

  • 
#3
g_logv

    • 

  • 
#4
g_log

    
                at gmessages.c
                  line
                  541

    

    • 

  • 
#5
g_ascii_strcasecmp

    
                at gstrfuncs.c
                  line
                  1744

    

    • 

  • 
#6
cdparanoia_get_type

    
                from
                /usr/lib/gstreamer-0.8/libgstcdparanoia.so

    

    • 

  • 
#7
g_object_set_valist

    
                at gobject.c
                  line
                  724

    

    • 

  • 
#8
g_object_set

    
                at gobject.c
                  line
                  1210

    

    • 

  • 
#9
build_pipeline

    
                at gst-cdparanoia-cdrom.c
                  line
                  212

    

    • 

  • 
#10
gst_cdparanoia_cdrom_get_status

    
                at gst-cdparanoia-cdrom.c
                  line
                  1030

    

    • 

  • 
#11
gnome_cd_build_track_list_menu

    
                at gnome-cd.c
                  line
                  207

    

    • 

  • 
#12
main

    
                at gnome-cd.c
                  line
                  632

    

    • 













Comment 3


Kjartan Maraas





          2004-08-31 22:45:18 UTC
        



Attaching the patch that was supposed to fix the crash and reading the gconf key
for the audiosink after changing it to:

audioscale ! audio/x-raw-int,rate=48000 ! alsasink device=hw:0

to fix my broken Audigy NX 2






Comment 4


Kjartan Maraas





          2004-08-31 22:45:58 UTC
        



Created attachment 31159 [details] [review]
patch to fix crash and reading of gconf key






Comment 5


Kjartan Maraas





          2004-09-01 07:30:29 UTC
        



The above patch is the one I'm running with when I get the crash, not a fix for
the problem. The patch was needed to get working sound on my card because the
driver lies and says it supports 44.1 khZ but in reality it has to run at 48 khZ
to get good sound.






Comment 6


Vincent Noel





          2004-09-01 14:02:23 UTC
        



I cannot find a bug with gst_cdparanoia_cdrom_get_cddb_data in the stack trace,
so I'm marking this as new...






Comment 7


Ronald Bultje





          2004-09-13 13:01:34 UTC
        



I've reverted several of the changes in 2.7.92, so this should no longer be
there (code is back to previous state, basically).