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 169021 - gnome-volume-control segmentation fault
gnome-volume-control segmentation fault
Status: RESOLVED FIXED
Product: gnome-media
Classification: Deprecated
Component: gnome-volume-control
2.9.x
Other All
: High critical
: 2.9.93
Assigned To: gnome media maintainers
gnome media maintainers
: 169106 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-03-02 20:44 UTC by Joaquim Fellmann
Modified: 2005-03-04 19:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10

Attachments
Partial solution (348 bytes, patch)
2005-03-04 12:50 UTC, Andrei Yurkevich 		none Details | Review
proposed patch (653 bytes, patch)
2005-03-04 13:31 UTC, Ronald Bultje 		none Details | Review

Description Joaquim Fellmann 2005-03-02 20:44:29 UTC 
Steps to reproduce:

I'm unable to launch gnome-volume-control 2.9.92 (same behaviour with 2.9.91 and
2.9.90 AFAIR). Running it from a terminal simply gives a segmentation fault
(small backtrace attached but no symbols).



Stack trace:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1222739808 (LWP 9502)]
0xb7c65666 in gtk_widget_show () from /usr/lib/libgtk-x11-2.0.so.0
(gdb) thread apply all bt

+ Trace 56356

Thread 1 (Thread -1222739808 (LWP 9502))

  • #0 gtk_widget_show
    from /usr/lib/libgtk-x11-2.0.so.0
  • #1 gnome_volume_control_element_change
  • #2 gnome_volume_control_element_new
  • #3 gnome_volume_control_window_new
  • #4 ??
  • #5 ??
  • #6 ??
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 gst_element_factory_get_type
    from /usr/lib/libgstreamer-0.8.so.1 

Other information:
I'm running an uptodate Ubuntu Hoary on a x86 platform.
Comment 1 Ronald Bultje 2005-03-03 13:02:17 UTC 
Can you get me a backtrace with debug symbols? If I know on which line number
(and possibly in which statement) it crashes, it'll be a lot easier to fix...
Comment 2 Joaquim Fellmann 2005-03-03 13:28:06 UTC 
I'll try to rebuild the Ubuntu package with the debugging symbols enabled but
I'm not sure how to do this. I know it's possible with deb packages but can't
remember how (if you have any hint).
Comment 3 Joaquim Fellmann 2005-03-03 14:07:30 UTC 
I did a:
DEB_BUILD_OPTIONS=nostrip fakeroot apt-get source --build gnome-media

and here's the trace:

joaquim@ubuntu:/usr/src$ gdb /usr/bin/gnome-volume-control
GNU gdb 6.3-debian
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-linux"...Using host libthread_db library
"/lib/tls/i686/cmov/libthread_db.so.1".

(gdb) run
Starting program: /usr/bin/gnome-volume-control
[Thread debugging using libthread_db enabled]
[New Thread -1222743904 (LWP 25101)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1222743904 (LWP 25101)]
0xb7c64666 in gtk_widget_show () from /usr/lib/libgtk-x11-2.0.so.0
(gdb) thread apply all bt

+ Trace 56384

Thread 1 (Thread -1222743904 (LWP 25101))

  • #0 gtk_widget_show
    from /usr/lib/libgtk-x11-2.0.so.0
  • #1 gnome_volume_control_element_change
  • #2 gnome_volume_control_element_new
  • #3 gnome_volume_control_window_new
  • #4 main
Comment 4 Ronald Bultje 2005-03-03 17:07:56 UTC 
*** Bug 169106 has been marked as a duplicate of this bug. ***
Comment 5 Ronald Bultje 2005-03-03 17:08:42 UTC 
Hi, this backtrace isn't good enough, it's still stripped for some reason. Try
installing from source or so, or ask for help online on some IRC channel or so.
Comment 6 Joaquim Fellmann 2005-03-03 17:19:21 UTC 
I really don't have any time for this right now.
If anyone on the list has any idea how to get those debugging symbols show up
with a debian packaging system, let me now. Otherwise that's pretty much all I
can do right now.
Sorry
Comment 7 Andrei Yurkevich 2005-03-04 12:50:25 UTC 
Created attachment 38241 [details] [review]
Partial solution

This patch pretty much explains where the problem is and even makes g-v-c not
crash. However, this is definitely not the solution - just a pointer to the
problem.
Comment 8 Ronald Bultje 2005-03-04 13:31:01 UTC 
Created attachment 38243 [details] [review]
proposed patch

This may be the actual fix...
Comment 9 Joaquim Fellmann 2005-03-04 15:44:25 UTC 
Yes, this fixes the problem, thanks!
Comment 10 Ronald Bultje 2005-03-04 19:02:54 UTC 
Thanks, applied (with permission from the release team).