gnome-control-center crashed with SIGSEGV after reducing items retrieved via google account
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gnome-control-center (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
I had added a google account which then adds all subfunctions. Through the calendar app I adjusted the account settings to a subset. This completed but then resulted in a crash.
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-control-
ProcVersionSign
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 17 20:20:51 2017
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2017-10-17 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171015)
ProcCmdline: /usr/bin/
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_
PATH=(custom, no user)
LANGUAGE=en_CA:en
LANG=en_CA.UTF-8
SegvAnalysis:
Segfault happened at: 0x7ff33d18ab3b: mov 0x8(%rax),%rax
PC (0x7ff33d18ab3b) ok
source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: gnome-control-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
| Willem (withaar) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| information type: | Private → Public |
| tags: | removed: need-amd64-retrace |
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1724011, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.