nm-connection-editor crashed with SIGSEGV in g_object_newv()

Bug #423257 reported by James Deibele
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
network-manager-applet (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Right clicked on the network manager icon and it crashed.

ProblemType: Crash
Architecture: amd64
CRDA: Error: [Errno 2] No such file or directory
Date: Mon Aug 31 09:56:43 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nm-connection-editor
Gconf:

IfupdownConfig:
 auto lo
 iface lo inet loopback
IpRoute:
 192.168.10.0/24 dev eth0 proto kernel scope link src 192.168.10.101 metric 1
 169.254.0.0/16 dev eth0 scope link metric 1000
 default via 192.168.10.1 dev eth0 proto static
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.

 vboxnet0 no wireless extensions.
NonfreeKernelModules: nvidia
Package: network-manager-gnome 0.8~a~git.20090818t151413.a8b7eed-0ubuntu2
ProcCmdline: nm-connection-editor
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-9.29-generic
RfKill:

SegvAnalysis:
 Segfault happened at: 0x7f6052934550: mov 0x20(%rax),%rdi
 PC (0x7f6052934550) ok
 source "0x20(%rax)" (0x00000020) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: network-manager-applet
StacktraceTop:
 ?? () from /usr/lib/libpolkit-gnome.so.0
 ?? () from /usr/lib/libpolkit-gnome.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libpolkit-gnome.so.0
 g_object_newv () from /usr/lib/libgobject-2.0.so.0
Title: nm-connection-editor crashed with SIGSEGV in g_object_newv()
Uname: Linux 2.6.31-9-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev pulse pulse-access sambashare vboxusers

Revision history for this message
James Deibele (jdeibele) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:_update_action (action=0x1ee8060) at polkit-gnome-action.c:869
set_property (object=<value optimized out>,
g_object_constructor (type=<value optimized out>,
polkit_gnome_action_constructor (type=30975344,
IA__g_object_newv (

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in network-manager-applet (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Alexander Sack (asac)
visibility: private → public
Revision history for this message
Victor Vargas (kamus) wrote :

Can you try to reproduce this crash using latest version of NetworkManager included in Karmic (at least here I have 0.8~a~git.20091013t193206.679d548-0ubuntu1), because I tried to follow these steps and works fine here. Additionally if this issue is still occurring could you attach a backtrace to your report? Thanks in advance

Changed in network-manager-applet (Ubuntu):
status: New → Incomplete
Revision history for this message
Victor Vargas (kamus) wrote :

ouch, something wrong has happened and cut part of my answer.. Well, I said that please if you can try to reproduce this issue using latest version of NM included in karmic and if this problem is still occuring please attach a backtrace to your report. Thanks in advance

Revision history for this message
James Deibele (jdeibele) wrote : Re: [Bug 423257] Re: nm-connection-editor crashed with SIGSEGV in g_object_newv()

Thanks for the response.

I'm not using Karmic. I'm running Lucid, 10.04.

I didn't invoke the command myself - it crashed and I was just reporting it.
 I'd repeat it if I could but I don't know how.

On Thu, Jan 21, 2010 at 9:21 AM, Kamus <email address hidden> wrote:

> ouch, something wrong has happened and cut part of my answer.. Well, I
> said that please if you can try to reproduce this issue using latest
> version of NM included in karmic and if this problem is still occuring
> please attach a backtrace to your report. Thanks in advance
>
> --
> nm-connection-editor crashed with SIGSEGV in g_object_newv()
> https://bugs.launchpad.net/bugs/423257
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Tony Espy (awe) wrote :

@ James

Your original bug report was in Sep 2009 while running a pre-release version of Karmic ( 9.10 ).

Are you saying now that you get the same crash while running Lucid ( 10.04 ) Alpha2? If so, can you please use the command:

% apport-bug -p network-manager 423257

...to add current debug information from your system?

Revision history for this message
James Deibele (jdeibele) wrote :

Hello, Tony.

No, I'm not saying that it's still happening. As far as I know, it's not.
Yes, I was running Karmic then but I'm not now.

If there's anything I can do to help, I will.

On Thu, Jan 21, 2010 at 3:51 PM, Tony Espy <email address hidden> wrote:

> @ James
>
> Your original bug report was in Sep 2009 while running a pre-release
> version of Karmic ( 9.10 ).
>
> Are you saying now that you get the same crash while running Lucid (
> 10.04 ) Alpha2? If so, can you please use the command:
>
> % apport-bug -p network-manager 423257
>
> ...to add current debug information from your system?
>
> --
> nm-connection-editor crashed with SIGSEGV in g_object_newv()
> https://bugs.launchpad.net/bugs/423257
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for network-manager-applet (Ubuntu) because there has been no activity for 60 days.]

Changed in network-manager-applet (Ubuntu):
status: Incomplete → 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.