| 2017-08-31 17:22:13 |
starkus |
bug |
|
|
added bug |
| 2017-08-31 17:34:59 |
Apport retracing service |
bug |
|
|
added subscriber Crash bug triagers for Ubuntu packages |
| 2017-08-31 17:35:02 |
Apport retracing service |
attachment removed |
CoreDump.gz https://bugs.launchpad.net/bugs/1714315/+attachment/4941942/+files/CoreDump.gz |
|
|
| 2017-08-31 17:35:02 |
Apport retracing service |
attachment removed |
Disassembly.txt https://bugs.launchpad.net/bugs/1714315/+attachment/4941944/+files/Disassembly.txt |
|
|
| 2017-08-31 17:35:03 |
Apport retracing service |
attachment removed |
ProcMaps.txt https://bugs.launchpad.net/bugs/1714315/+attachment/4941947/+files/ProcMaps.txt |
|
|
| 2017-08-31 17:35:04 |
Apport retracing service |
attachment removed |
ProcStatus.txt https://bugs.launchpad.net/bugs/1714315/+attachment/4941948/+files/ProcStatus.txt |
|
|
| 2017-08-31 17:35:05 |
Apport retracing service |
attachment removed |
Registers.txt https://bugs.launchpad.net/bugs/1714315/+attachment/4941949/+files/Registers.txt |
|
|
| 2017-08-31 17:35:07 |
Apport retracing service |
attachment removed |
Stacktrace.txt https://bugs.launchpad.net/bugs/1714315/+attachment/4941950/+files/Stacktrace.txt |
|
|
| 2017-08-31 17:35:09 |
Apport retracing service |
attachment removed |
ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1714315/+attachment/4941951/+files/ThreadStacktrace.txt |
|
|
| 2017-08-31 17:35:19 |
Apport retracing service |
marked as duplicate |
|
1704618 |
|
| 2017-08-31 17:35:19 |
Apport retracing service |
information type |
Private |
Public |
|
| 2017-08-31 17:35:33 |
Apport retracing service |
tags |
amd64 apport-crash artful need-amd64-retrace |
amd64 apport-crash artful |
|
| 2017-09-08 16:36:38 |
starkus |
description |
I installed all update and upgrades for ubuntu 17.10 with gnome-shell running, after I logged out and switched to tty2. After a reboot the system logged out, just by itself. I rebooted, installed 'Hide Dash X', because of a bug with 'Dash to Dock' which did not hide the standard dash. After that, what I first wanted to do, I switched to gnome-control-center to reenable automatic login for my account, because I thought somehow there's the reason why the system logged out by itself. After I unlocked the settings, the window was grayed out and crashed. The bug report appeared. On the second try I could reenable it. It was disabled. I reinstalled all x11, nvidia and noiveau packages via synaptic that where shown as installed due the search option. I think it is fixed now.
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.24.3-0ubuntu6
ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
Uname: Linux 4.12.0-12-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Aug 31 19:11:54 2017
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2017-07-18 (43 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: gnome-control-center --overview
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=de_DE.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7fe95ef49499: cmpq $0x0,0x58(%rax)
PC (0x7fe95ef49499) ok
source "$0x0" ok
destination "0x58(%rax)" (0x00000058) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libnm.so.0
ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in ffi_call_unix64()
UpgradeStatus: Upgraded to artful on 2017-08-13 (18 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
I switched to gnome-control-center to reenable automatic login for my account, because I thought somehow there's the reason why the system logged out by itself. After I unlocked the settings, the window was grayed out and crashed. The bug report appeared. On the second try I could reenable it. It was disabled.
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.24.3-0ubuntu6
ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
Uname: Linux 4.12.0-12-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Thu Aug 31 19:11:54 2017
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2017-07-18 (43 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
ProcCmdline: gnome-control-center --overview
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=de_DE.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7fe95ef49499: cmpq $0x0,0x58(%rax)
PC (0x7fe95ef49499) ok
source "$0x0" ok
destination "0x58(%rax)" (0x00000058) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libnm.so.0
ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-control-center crashed with SIGSEGV in ffi_call_unix64()
UpgradeStatus: Upgraded to artful on 2017-08-13 (18 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo |
|
