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 355319 - crash in Sound: I was running updatedb a...
crash in Sound: I was running updatedb a...
Status: RESOLVED DUPLICATE of bug 351002
Product: gnome-control-center
Classification: Core
Component: Sound
2.16.x
Other All
: High critical
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
: 355754 356098 361219 361245 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-09-10 17:39 UTC by head
Modified: 2006-10-10 19:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description head 2006-09-10 17:39:11 UTC
Version: 2.16.0

What were you doing when the application crashed?
I was running updatedb at the time.  Also had azureus, nautilus and some terminals running.


Distribution: Gentoo Base System version 1.12.4
Gnome Release: 2.16.0 2006-09-07 (Gentoo)
BugBuddy Version: 2.16.0

Memory status: size: 109985792 vsize: 109985792 resident: 14217216 share: 10031104 rss: 14217216 rss_rlim: -1
CPU usage: start_time: 1157909918 rtime: 22 utime: 20 stime: 2 cutime:2 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 47688117026992 (LWP 25183)]
0x00002b5f401188f5 in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 47688117026992 (LWP 25183))

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

Comment 1 Karsten Bräckelmann 2006-09-13 11:10:33 UTC
*** Bug 355754 has been marked as a duplicate of this bug. ***
Comment 2 Jens Granseuer 2006-10-06 12:57:26 UTC
Possibly a duplicate of bug 351002?
Comment 3 Karsten Bräckelmann 2006-10-10 19:52:44 UTC
*** Bug 356098 has been marked as a duplicate of this bug. ***
Comment 4 Karsten Bräckelmann 2006-10-10 19:52:53 UTC
*** Bug 361219 has been marked as a duplicate of this bug. ***
Comment 5 Karsten Bräckelmann 2006-10-10 19:53:01 UTC
*** Bug 361245 has been marked as a duplicate of this bug. ***
Comment 6 Karsten Bräckelmann 2006-10-10 19:58:42 UTC
Thanks, Jens. :)  Yes, looks like a duplicate.

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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