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 426923 - crash in Volume Control: the system was starting
crash in Volume Control: the system was starting
Status: RESOLVED DUPLICATE of bug 412524
Product: gnome-applets
Classification: Other
Component: mixer
unspecified
Other All
: High critical
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-04-06 13:49 UTC by lusenti.s
Modified: 2007-07-26 05:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description lusenti.s 2007-04-06 13:49:02 UTC 
What were you doing when the application crashed?
the system was starting


Distribution: Mandriva Linux release 2007.0 (Official) for x86_64
Gnome Release: 2.16.0 2006-09-05 (Mandriva)
BugBuddy Version: 2.16.0

Memory status: size: 115949568 vsize: 115949568 resident: 7221248 share: 3461120 rss: 7221248 rss_rlim: -1
CPU usage: start_time: 1175867315 rtime: 2 utime: 2 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/libexec/mixer_applet2'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47152316375264 (LWP 4389)]
(no debugging symbols found)
0x00002ae2803d2dd5 in waitpid () from /lib64/libpthread.so.0

+ Trace 125495

Thread 1 (Thread 47152316375264 (LWP 4389))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 do_lookup_x
    at do-lookup.h line 72 






Comment 1


Philip Withnall





          2007-07-26 05:17:41 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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