gsd-xsettings crashed with SIGSEGV in g_type_check_value()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-settings-daemon (Ubuntu) |
Expired
|
Low
|
Unassigned |
Bug Description
gsd-xsettings crashed with SIGSEGV in g_type_
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-settings-
ProcVersionSign
Uname: Linux 4.15.0-17-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 20 18:28:22 2018
ExecutablePath: /usr/lib/
InstallationDate: Installed on 2018-04-06 (13 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403)
ProcCmdline: /usr/lib/
SegvAnalysis:
Segfault happened at: 0x7f248dc12463 <g_type_
PC (0x7f248dc12463) ok
source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%rbx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-settings-
StacktraceTop:
g_type_check_value () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
gtk_css_
Title: gsd-xsettings crashed with SIGSEGV in g_type_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
tags: | removed: need-amd64-retrace |
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.