[apport] cpufreq-applet crashed with SIGSEGV in _start()

Bug #98727 reported by Christian González
14
Affects Status Importance Assigned to Milestone
GNOME Applets
Expired
High
gnome-applets (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-applets

crash after resuming from standby

ProblemType: Crash
Architecture: i386
Date: Thu Mar 29 21:03:52 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/lib/gnome-applets/cpufreq-applet
Package: gnome-applets 2.18.0-0ubuntu1
PackageArchitecture: i386
ProcCmdline: /usr/lib/gnome-applets/cpufreq-applet --oaf-activate-iid=OAFIID:GNOME_CPUFreqApplet_Factory --oaf-ior-fd=19
ProcCwd: /
ProcEnviron:
 LANG=de_AT.UTF-8
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANGUAGE=de_AT:de
Signal: 11
SourcePackage: gnome-applets
Stacktrace: #0 0x0804d59f in _start ()
StacktraceTop: _start ()
ThreadStacktrace:
 .
 Thread 1 (process 9738):
 #0 0x0804d59f in _start ()
Uname: Linux gimli 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video

Revision history for this message
Christian González (droetker) wrote :
Changed in gnome-applets:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:cpufreq_applet_update (applet=0x80ab060, monitor=0x80ce620) at cpufreq-applet.c:814
IA__g_cclosure_marshal_VOID__VOID (closure=0x80cd1c8, return_value=0x0, n_param_values=1, param_values=0xbf99a7ec, invocation_hint=0xbf99a6fc,
IA__g_closure_invoke (closure=0x80cd1c8, return_value=0x0, n_param_values=1, param_values=0xbf99a7ec, invocation_hint=0xbf99a6fc) at gclosure.c:490
signal_emit_unlocked_R (node=0x80ccfd8, detail=0, instance=0x80ce620, emission_return=0x0, instance_and_params=0xbf99a7ec) at gsignal.c:2440
IA__g_signal_emit_valist (instance=0x80ce620, signal_id=140, detail=0,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Daniel Holbach (dholbach) wrote :

I forwarded the bug to the upstream developers: http://bugzilla.gnome.org/show_bug.cgi?id=424383

Changed in gnome-applets:
status: Unconfirmed → Confirmed
Changed in gnome-applets:
status: Unknown → Unconfirmed
Revision history for this message
Daniel Holbach (dholbach) wrote :

Upstream asks:
"could you run cpufreq-applet from the command line to see if there is any
message sent to stdout, please? "

Changed in gnome-applets:
status: Confirmed → Needs Info
Revision history for this message
Sebastien Bacher (seb128) wrote :

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

Changed in gnome-applets:
status: Needs Info → Rejected
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Christian, may you please run the command that Daniel is asking for? It would help us a lot to get the problem fixed. thanks.

Revision history for this message
Christian González (droetker) wrote :

Hm - I am using Kubuntu ATM - but I'm playing around all the time, should be no problem - just give me a few days time to set up Ubuntu/Gnome again.

Revision history for this message
Christian González (droetker) wrote :

running /usr/lib/gnome-applets/cpufreq-applet from commandline - there is no output.
I don't have the problem atm, since I have another one with the suspend option. I will avoid suspending in future...

Changed in gnome-applets:
status: New → Invalid
Changed in gnome-applets:
importance: Unknown → High
status: Invalid → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.