[network]: gnome-control-center crashed with SIGSEGV in g_main_dispatch()

Bug #938038 reported by Saurabh Rawat
48
This bug affects 9 people
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Incomplete
Low
Unassigned

Bug Description

I was trying to use my laptop as a WiFi hotspot, which worked really easily and fine (thank you so much developers). However my android phone doesn't work with ad-hoc wifi networks so I tried to change the connection type to Infrastructure, the network icon was showing activity for a long time. I started stopping the hotspot thats when it crashed.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-control-center 1:3.3.5-0ubuntu5
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.92-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Tue Feb 21 23:45:12 2012
ExecutablePath: /usr/bin/gnome-control-center
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120217)
ProcCmdline: gnome-control-center
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANGUAGE=en_IN:en
 LANG=en_IN
SegvAnalysis:
 Segfault happened at: 0x7fa0bdccb105: mov 0x8(%r13),%esi
 PC (0x7fa0bdccb105) ok
 source "0x8(%r13)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 ?? () from /usr/lib/control-center-1/panels/libnetwork.so
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_application_run () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: [network]: gnome-control-center crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
usr_lib_gnome-control-center:
 activity-log-manager-control-center 0.9.1-0ubuntu2
 deja-dup 21.2-0ubuntu4
 gnome-bluetooth 3.2.2-0ubuntu1
 indicator-datetime 0.3.90-0ubuntu1

Revision history for this message
Saurabh Rawat (eklavya) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? () from /tmp/tmpBaNTJf/usr/lib/control-center-1/panels/libnetwork.so
 g_main_dispatch (context=0x7fa0dd94d480) at /build/buildd/glib2.0-2.31.18/./glib/gmain.c:2510
 g_main_context_dispatch (context=0x7fa0dd94d480) at /build/buildd/glib2.0-2.31.18/./glib/gmain.c:3047
 g_main_context_iterate (dispatch=1, block=<optimized out>, context=0x7fa0dd94d480, self=<optimized out>) at /build/buildd/glib2.0-2.31.18/./glib/gmain.c:3118
 g_main_context_iterate (context=0x7fa0dd94d480, block=<optimized out>, dispatch=1, self=<optimized out>) at /build/buildd/glib2.0-2.31.18/./glib/gmain.c:3055

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-control-center (Ubuntu):
importance: Undecided → Medium
summary: [network]: gnome-control-center crashed with SIGSEGV in
- g_main_context_dispatch()
+ g_main_dispatch()
tags: removed: need-amd64-retrace
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

visibility: private → public
Changed in gnome-control-center (Ubuntu):
importance: Medium → Low
status: New → Incomplete
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.