gnome-control-center crashed with SIGSEGV

Bug #1717626 reported by José Henrique de Almeida Gomes
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Expired
Medium
Unassigned

Bug Description

gnome-control-center crashed with SIGSEGV

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
Uname: Linux 4.12.0-13-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 15 22:08:33 2017
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2017-09-14 (1 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: gnome-control-center wifi
SegvAnalysis:
 Segfault happened at: 0x7fd2b0a4b1d4: mov 0x0(%rbp),%rdi
 PC (0x7fd2b0a4b1d4) ok
 source "0x0(%rbp)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/libnm.so.0
 ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
 g_cclosure_marshal_generic () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV
UpgradeStatus: Upgraded to artful on 2017-09-15 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
José Henrique de Almeida Gomes (jhgomes) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 updated_cb (proxy=<optimized out>, user_data=0x563239ee8320) at libnm/nm-remote-connection.c:612
 ffi_call_unix64 () at ../src/x86/unix64.S:76
 ffi_call (cif=cif@entry=0x7ffdeb998c30, fn=fn@entry=0x7fd2b0a4b1b0 <updated_cb>, rvalue=<optimized out>, avalue=avalue@entry=0x7ffdeb998b60) at ../src/x86/ffi64.c:525
 g_cclosure_marshal_generic (closure=0x563239cfa300, return_gvalue=0x0, n_param_values=<optimized out>, param_values=<optimized out>, invocation_hint=<optimized out>, marshal_data=<optimized out>) at ../../../../gobject/gclosure.c:1490
 g_closure_invoke (closure=0x563239cfa300, return_value=0x0, n_param_values=1, param_values=0x563239e48180, invocation_hint=0x7ffdeb998de0) at ../../../../gobject/gclosure.c:804

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-control-center (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
information type: Private Security → Public
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Thanks for your report. Could you tell us what you were doing when control-center crashed or give us steps to reproduce this defect.

Thanks.

Changed in gnome-control-center (Ubuntu):
status: New → Incomplete
Revision history for this message
BRUN (christian-brun2244) wrote :

Hello,
This problem not appears on my USB hard-disk...Just with my principal intern HD.

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

[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.]

Changed in gnome-control-center (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.