gnome-control-center crashed with SIGSEGV in __GI_____strtoul_l_internal()

Bug #1732478 reported by Edson T. Marques
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I installed nvidia proprietary driver on my notebook:

etm@etm:~$ sudo ubuntu-drivers devices
== /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0 ==
modalias : pci:v000010DEd00001C8Csv00001028sd00000798bc03sc00i00
vendor : NVIDIA Corporation
model : GP107M [GeForce GTX 1050 Ti Mobile]
driver : nvidia-384 - distro non-free recommended
driver : xserver-xorg-video-nouveau - distro free builtin

== cpu-microcode.py ==
driver : intel-microcode - distro non-free

After this I try to run gnome-control-center to see what graphic card are in use...

The gnome-control-center not ran and I receive this crash message.

etm @ etm: ~ $ gnome-control-center
i965_dri.so does not support PCI ID 0xffffffff.

(gnome-control-center: 24160): GLib-CRITICAL **: g_strsplit: assertion 'string! = NULL 'failed
Segmentation fault (core image recorded)

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.26.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 15 13:08:21 2017
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2017-09-29 (47 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170929)
ProcCmdline: gnome-control-center --overview
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f5b4ec670f5 <__GI_____strtoul_l_internal+53>: movsbq (%r14),%rax
 PC (0x7f5b4ec670f5) ok
 source "(%r14)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 __GI_____strtoul_l_internal (nptr=0x0, endptr=0x7fff5bda8298, base=10, group=<optimized out>, loc=0x7f5b4f002800 <_nl_C_locobj>) at ../stdlib/strtol_l.c:292
 () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
 () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
 () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
 () at /usr/lib/x86_64-linux-gnu/libcogl.so.20
Title: gnome-control-center crashed with SIGSEGV in __GI_____strtoul_l_internal()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm bluetooth cdrom clamav dip firebird input lpadmin plugdev pulse sambashare sudo utmp uucp uuidd video voice

Revision history for this message
Edson T. Marques (edsontmarques) wrote :
Revision history for this message
Edson T. Marques (edsontmarques) wrote :

Well, I should add that after rebooting Ubuntu, I ran the gnome-control-center again and it ran normally.

Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #1712961, 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.

information type: Private → Public
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-control-center (Ubuntu):
status: New → Confirmed
Revision history for this message
SwaJime (john-swajime) wrote :

Bug 1712961 cannot be found ???

Revision history for this message
Gunnar Hjalmarsson (gunnarhj) wrote :

On 2020-05-27 13:15, SwaJime wrote:
> Bug 1712961 cannot be found ???

It can now.

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.