nm-applet crashed with SIGSEGV in gtk_container_forall()

Bug #272982 reported by Jayotis Diggory
6
Affects Status Importance Assigned to Milestone
network-manager-applet (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

dmesg | grep error

[ 9.635725] uvesafb: probe of uvesafb.0 failed with error -22
[ 29.968262] VIA 82xx Modem: probe of 0000:00:11.6 failed with error -13
[ 34.293228] powernow-k8: BIOS error - no PSB or ACPI _PSS objects
[ 55.366023] gvfsd-trash[6025]: segfault at 7f0f1e87f673 ip 00007f0f1e87f673 sp 00007fff29f81620 error 14 in libgvfsdbus.so[7f0f1f132000+26000]
[14214.303517] nm-applet[5936] general protection ip:7f6df730229f sp:7fff01ea74c8 error:0 in libgtk-x11-2.0.so.0.1400.2[7f6df724e000+3da000]

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/nm-applet
Gconf:

IfupdownConfig:
 auto lo
 iface lo inet loopback
NonfreeKernelModules: nvidia
Package: network-manager-gnome 0.7~~svn20080907t033843-0ubuntu2
ProcAttrCurrent: unconfined
ProcCmdline: nm-applet --sm-disable
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: network-manager-applet
Stacktrace:
 #0 0x00007f6df730229f in gtk_container_forall ()
    from /usr/lib/libgtk-x11-2.0.so.0
 #1 0x0000000000000000 in ?? ()
StacktraceTop:
 gtk_container_forall ()
 ?? ()
ThreadStacktrace:
 .
 Thread 1 (process 5936):
 #0 0x00007f6df730229f in gtk_container_forall ()
    from /usr/lib/libgtk-x11-2.0.so.0
 #1 0x0000000000000000 in ?? ()
Title: nm-applet crashed with SIGSEGV in gtk_container_forall()
Uname: Linux 2.6.27-3-generic x86_64
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare
WpaSupplicantLog:

Revision history for this message
Jayotis Diggory (jayotis-d) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Pedro Villavicencio (pedro) wrote : Missing Backtrace

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in network-manager-applet:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Jayotis Diggory (jayotis-d) wrote : Re: [Bug 272982] Re: nm-applet crashed with SIGSEGV in gtk_container_forall()

Probably a security breach, I suspect a contaminated package either in
the repos or an internet interception. I have stopped using Ubuntu
due to this and various arp flood attacks after posting to the forums.
 Excellent job looking into this.

On Wed, Nov 26, 2008 at 11:44 AM, Pedro Villavicencio <email address hidden> wrote:
> Thanks for your bug report. Please try to obtain a backtrace
> http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the
> bug report. This will greatly help us in tracking down your problem.
>
> ** Attachment removed: "CoreDump.gz"
>
> http://launchpadlibrarian.net/17802543/CoreDump.gz
>
> ** Changed in: network-manager-applet (Ubuntu)
> Importance: Undecided => Medium
> Status: New => Incomplete
>
> ** Visibility changed to: Public
>
> --
> nm-applet crashed with SIGSEGV in gtk_container_forall()
> https://bugs.launchpad.net/bugs/272982
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Michele Mangili (mangilimic) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in network-manager-applet:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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