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 383217 - crash in Sound: loaded system->preferenc...
crash in Sound: loaded system->preferenc...
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: 2006-12-07 00:57 UTC by fenixrf
Modified: 2006-12-10 17:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Attachments
Check for errors before using return value (593 bytes, patch)
2006-12-08 12:45 UTC, palfrey
none Details | Review

Description fenixrf 2006-12-07 00:57:15 UTC
Version: 2.16.2

What were you doing when the application crashed?
loaded system->preferences->sound


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

Memory status: size: 101502976 vsize: 101502976 resident: 13377536 share: 10166272 rss: 13377536 rss_rlim: -1
CPU usage: start_time: 1165452918 rtime: 13 utime: 12 stime: 1 cutime:1 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(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 47454523437344 (LWP 9403)]
0x00002b28dcdd0a95 in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 47454523437344 (LWP 9403))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #5 <signal handler called>
  • #6 main
  • #0 waitpid
    from /lib/libpthread.so.0

Comment 1 palfrey 2006-12-07 11:39:56 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 fenixrf 2006-12-08 01:38:01 UTC
Hopefully this will be more helpful.


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

Memory status: size: 101507072 vsize: 101507072 resident: 13377536 share: 10170368 rss: 13377536 rss_rlim: -1
CPU usage: start_time: 1165540740 rtime: 16 utime: 14 stime: 2 cutime:1 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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 46967582626080 (LWP 3149)]
0x00002ab77cedea95 in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 46967582626080 (LWP 3149))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #5 <signal handler called>
  • #6 main
    at sound-properties-capplet.c line 478
  • #0 waitpid
    from /lib/libpthread.so.0

Rich
Comment 3 palfrey 2006-12-08 12:44:53 UTC
Several things to try:
1) Run /usr/bin/gnome-sound-properties from the command line, and see if you get any errors from HAL or DBus before the crash. Things like "wrong reply from hald.  Expecting an array" might turn up.
2) Try applying the patch I'm about to attach, and see if it fixes things.
3) Even if the patch fixes things, restart HAL, and re-run /usr/bin/gnome-sound-properties. Interesting to know whether you still get the same errors as you probably would have seen in step 1.
Comment 4 palfrey 2006-12-08 12:45:43 UTC
Created attachment 77956 [details] [review]
Check for errors before using return value
Comment 5 André Klapper 2006-12-10 17:06:33 UTC
hi tom, thanks a lot for coming up with a patch.
this bug has been already reported, and i have added a comment about your patch to bug 363005.

thanks again! :-)

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