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 513396 - crash in Volume Control: at start, it crashed!
crash in Volume Control: at start, it crashed!
Status: RESOLVED DUPLICATE of bug 513018
Product: gnome-applets
Classification: Other
Component: mixer
unspecified
Other All
: High critical
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-31 10:06 UTC by giovanni.marzulli
Modified: 2008-01-31 11:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description giovanni.marzulli 2008-01-31 10:06:55 UTC
What were you doing when the application crashed?
at start, it crashed!


Distribution: Debian lenny/sid
Gnome Release: 2.20.3 2008-01-12 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy P
Icon Theme: Noia

Memory status: size: 46448640 vsize: 46448640 resident: 13443072 share: 9740288 rss: 13443072 rss_rlim: 4294967295
CPU usage: start_time: 1201773966 rtime: 14 utime: 11 stime: 3 cutime:1 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/lib/bug-buddy/mixer_applet2'

(no debugging symbols found)
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6e466b0 (LWP 4090)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6e466b0 (LWP 4090))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 ??
    from /usr/lib/gstreamer-0.10/libgstossaudio.so
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 ??
    from /usr/lib/libgthread-2.0.so.0
  • #12 ??
  • #13 ??
    from /usr/lib/gstreamer-0.10/libgstossaudio.so
  • #14 ??
    from /usr/lib/gstreamer-0.10/libgstossaudio.so
  • #15 ??
    from /usr/lib/gstreamer-0.10/libgstossaudio.so
  • #16 ??
  • #17 ??
  • #18 ??
  • #19 ??
  • #20 ??
  • #21 ??
  • #22 ??
  • #23 ??
  • #24 ??
  • #25 ??
  • #26 ??
  • #27 ??
  • #28 ??
  • #29 ??
  • #30 ??
  • #31 ??
  • #32 ??
  • #33 ??
  • #34 ??
  • #35 ??
  • #36 ??
  • #37 ??
  • #38 ??
  • #39 ??
  • #40 ??
  • #41 ??
    from /usr/lib/gstreamer-0.10/libgstossaudio.so
  • #42 gst_structure_set_parent_refcount
    from /usr/lib/libgstreamer-0.10.so.0
  • #43 ??
    from /usr/lib/gstreamer-0.10/libgstossaudio.so
  • #44 ??
  • #45 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors (6 sec old) ---------------------
/etc/gdm/Xsession: Beginning session setup...
can't lock memory: Cannot allocate memoryWARNING: not using secure memory for passwords
SESSION_MANAGER=local/DebianLaptop:/tmp/.ICE-unix/3863
** (gsynaptics-init:3949): WARNING **: Using synclient
Unknown parameter CoastingSpeedThreshold
seahorse nautilus module initialized
Initializing gnome-mount extension
xrdb:  "*Label.background" on line 220 overrides entry on line 150
xrdb:  "*Text.background" on line 226 overrides entry on line 191
xrdb:  "*Label.foreground" on line 232 overrides entry on line 151
xrdb:  "*Text.foreground" on line 238 overrides entry on line 192
Impossibile aprire il file .desktop «/usr/share/applications/gimp-2.2.desktop» per il lanciatore da pannello: No such file or directory
Impossibile aprire il file .desktop «/usr/share/applications/k3b.desktop» per il lanciatore da pannello: No such file or directory
--------------------------------------------------
Comment 1 Gianluca Borello 2008-01-31 11:32:37 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 513018 ***