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 428941 - crash in Sound: gnome-sound-properties c...
crash in Sound: gnome-sound-properties c...
Status: RESOLVED DUPLICATE of bug 363005
Product: gnome-control-center
Classification: Core
Component: Sound
2.16.x
Other All
: High critical
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-04-12 09:01 UTC by Iain Buchanan
Modified: 2007-04-13 18:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Iain Buchanan 2007-04-12 09:01:13 UTC 
Version: 2.16.2

What were you doing when the application crashed?
gnome-sound-properties crashes when starting from terminal, or menu.  New install on AM2, recompiled with debugging info. compile flags were "-O2 -march=i686 -pipe", nothing AM2 special.

alsa-utils-1.0.14
nvidia MCP61 sound card, using snd_hda_intel from 2.6.19. 


Distribution: Gentoo Base System release 1.12.9
Gnome Release: 2.16.2 2007-04-05 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 21266432 vsize: 0 resident: 21266432 share: 0 rss: 11079680 rss_rlim: 0
CPU usage: start_time: 1176368175 rtime: 0 utime: 17 stime: 0 cutime:15 cstime: 0 timeout: 2 it_real_value: 0 frequency: 2

Backtrace was generated from '/usr/bin/gnome-sound-properties'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1227315536 (LWP 31465)]
0xb7fb1410 in __kernel_vsyscall ()

+ Trace 127124

Thread 1 (Thread -1227315536 (LWP 31465))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 libgnomeui_segv_handle
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 main
  • #5 __libc_start_main
    from /lib/libc.so.6
  • #6 _start
  • #0 __kernel_vsyscall 






Comment 1


Jens Granseuer





          2007-04-13 18:10:30 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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