GNOME Bugzilla – Bug 410590
gnome-panel crashed with SIGSEGV in panel_applet_lockable()
Last modified: 2007-05-15 13:08:11 UTC
That bug has been opened on https://beta.launchpad.net/ubuntu/+source/gnome-panel/+bug/86709 "Binary package hint: gnome-panel I add "GNOME Sensors Applet 1.7.10" and freezy gnome-panel. Restart session and open apport. ... Package: gnome-panel 2.17.91-0ubuntu1 ..." Debug backtrace for the crash:
+ Trace 112730
...
(In reply to comment #0) > I add "GNOME Sensors Applet 1.7.10" and freezy gnome-panel. Restart session and > open apport. Can't reproduce the bug on my machine. Then again, my machine has no sensors (according to the applet). We probably need more info on the machine's config to track down the cause here.
What commandos need? What information needs? Config Ubuntu: Defaul caravena@zeus:/$ uname -a Linux zeus 2.6.20-8-lowlatency #2 SMP PREEMPT Tue Feb 13 05:21:37 UTC 2007 i686 GNU/Linux
Created attachment 83205 [details] $sudo dmidecode
Created attachment 83207 [details] $dmesg
Created attachment 83209 [details] $lspci -vvnn
caravena@zeus:/proc$ cat interrupts CPU0 0: 40775991 IO-APIC-edge timer 1: 108854 IO-APIC-edge i8042 8: 3 IO-APIC-edge rtc 12: 5333440 IO-APIC-edge i8042 14: 1122850 IO-APIC-edge ide0 15: 38481 IO-APIC-edge ide1 16: 4239896 IO-APIC-fasteoi yenta, ATI IXP Modem, ATI IXP, fglrx 17: 2 IO-APIC-fasteoi ohci_hcd:usb1, ohci_hcd:usb2, ehci_hcd:usb3 19: 0 IO-APIC-fasteoi eth0 20: 1514247 IO-APIC-fasteoi eth1 21: 151903 IO-APIC-fasteoi acpi NMI: 0 LOC: 40775903 ERR: 0 MIS: 0
I meant more like: What sensors did you see before in this panel applet? (if you did run it before) If we can find that out, someone might be able to get a similar machine to yours and see if the bug is reproducible there.
Created attachment 83241 [details] Sensor: ACPI THRM
Created attachment 83242 [details] Config of sensor
/proc/acpi$ ls -lisha total 0 4026532121 0 dr-xr-xr-x 11 root root 0 2007-02-24 10:57 . 1 0 dr-xr-xr-x 121 root root 0 2007-02-24 07:57 .. 4026532640 0 dr-xr-xr-x 3 root root 0 2007-02-24 11:59 ac_adapter 4026532330 0 -rw-r--r-- 1 root root 0 2007-02-24 11:59 alarm 4026532643 0 dr-xr-xr-x 3 root root 0 2007-02-24 11:59 battery 4026532648 0 dr-xr-xr-x 5 root root 0 2007-02-24 11:59 button 4026532125 0 -r-------- 1 root root 0 2007-02-24 11:59 dsdt 4026532122 0 dr-xr-xr-x 3 root root 0 2007-02-24 11:59 embedded_controller 4026532127 0 -r-------- 1 root root 0 2007-02-24 10:57 event 4026532126 0 -r-------- 1 root root 0 2007-02-24 11:59 fadt 4026532332 0 dr-xr-xr-x 2 root root 0 2007-02-24 11:59 fan 4026532124 0 -r--r--r-- 1 root root 0 2007-02-24 11:59 info 4026532123 0 dr-xr-xr-x 2 root root 0 2007-02-24 11:59 power_resource 4026532333 0 dr-xr-xr-x 3 root root 0 2007-02-24 11:59 processor 4026532329 0 -rw-r--r-- 1 root root 0 2007-02-24 11:59 sleep 4026532339 0 dr-xr-xr-x 3 root root 0 2007-02-24 11:59 thermal_zone 4026532661 0 dr-xr-xr-x 3 root root 0 2007-02-24 11:59 video 4026532331 0 -rw-r--r-- 1 root root 0 2007-02-24 11:59 wakeup
Created attachment 83244 [details] $hwinfo
Unfortunately, the stack trace doesn't make sense. Is the crash still happening? If yes, a new stack trace would be really useful.
closing for now, I'll reopen if the submitter get a new backtrace