crashs after suspend
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
emifreq-applet (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: emifreq-applet
Emifreq crashed after suspend. I can reproduce this bug. I have tried to make a backtrace,
Memory status: size: 21188608 vsize: 0 resident: 21188608 share: 0 rss: 10747904 rss_rlim: 0
CPU usage: start_time: 1161200895 rtime: 0 utime: 124 stime: 0 cutime:120 cstime: 0 timeout: 4 it_real_value: 0 frequency: 0
Backtrace was generated from '/usr/libexec/
(no debugging symbols found)
Using host libthread_db library "/lib/tls/
[Thread debugging using libthread_db enabled]
[New Thread -1208682832 (LWP 5221)]
0xffffe410 in __kernel_vsyscall ()
#0 0xffffe410 in __kernel_vsyscall ()
#1 0x45878323 in __waitpid_nocancel ()
from /lib/tls/
#2 0x496951b6 in libgnomeui_
#3 <signal handler called>
#4 0x0804c479 in ?? ()
#5 0x081f6c40 in ?? ()
#6 0xbfbfc434 in ?? ()
#7 0xbfbfc430 in ?? ()
#8 0x00000000 in ?? ()
Thread 1 (Thread -1208682832 (LWP 5221)):
#0 0xffffe410 in __kernel_vsyscall ()
No symbol table info available.
#1 0x45878323 in __waitpid_nocancel ()
from /lib/tls/
No symbol table info available.
#2 0x496951b6 in libgnomeui_
estatus = 0
sa = {__sigaction_
sa_mask = {__val = {1168404780, 3217015084, 134930480, 1168331771,
1168463568, 1168463568, 3217015124, 3217015592, 1168339180, 3217015084,
3217015084, 3217015468, 134217728, 3217015012, 3217015012, 0,
1094116192, 20, 0, 3217015020, 1165203147, 3217015612, 20, 0,
1092767616, 19, 0, 3217015052, 1165203147, 3217015644, 19, 0}},
sa_flags = -1077951804, sa_restorer = 0}
pid = 0
in_segv = 1
#3 <signal handler called>
No symbol table info available.
#4 0x0804c479 in ?? ()
No symbol table info available.
#5 0x081f6c40 in ?? ()
No symbol table info available.
#6 0xbfbfc434 in ?? ()
No symbol table info available.
#7 0xbfbfc430 in ?? ()
No symbol table info available.
#8 0x00000000 in ?? ()
No symbol table info available.
#0 0xffffe410 in __kernel_vsyscall ()
Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Thanks in advance.