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

Bug #1725347 reported by Stuardo -StR- Rodríguez
114
This bug affects 24 people
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Invalid
Low
Unassigned

Bug Description

When I run gnome-control-center I get the following error message:

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

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-control-center 1:3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 20 09:33:23 2017
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2017-10-20 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: gnome-control-center user-accounts
SegvAnalysis:
 Segfault happened at: 0x7fbb994a3b59: mov (%rsi),%rsi
 PC (0x7fbb994a3b59) ok
 source "(%rsi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-control-center
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
 ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
 ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
 cogl_renderer_connect () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
 ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
Title: gnome-control-center crashed with SIGSEGV in cogl_renderer_connect()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Stuardo -StR- Rodríguez (stuardo) wrote :
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 #1631434, 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
Stuardo -StR- Rodríguez (stuardo) wrote :

I was not able to find bug #1631434.

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
Sebastien Bacher (seb128) wrote :

Do you get the issue every time you try to start it? What video card/driver do you use? You should be able to access the other bug now

Revision history for this message
Stuardo -StR- Rodríguez (stuardo) wrote :

Hmm. I'm no longer able to replicate the problem

Revision history for this message
Andrew Moreland (derander) wrote :

I have this issue on Ubuntu 17.10, same exact segfault message. Happens every time I try to execute the program. Using an nvidia 1050 ti with the 387.12 NVIDIA binary drivers selected from "Additional Drivers" under "software and updates".

Revision history for this message
Andrew Moreland (derander) wrote :

If it is relevant, I am using an AMD ryzen processor.

Revision history for this message
Had (hadriman) wrote :

I got this bug running a live CD after I switched the video drivers from nouveau to nVidia's proprietary driver

Changed in gnome-control-center (Ubuntu):
status: Confirmed → Invalid
importance: Undecided → Low
Revision history for this message
Stuardo -StR- Rodríguez (stuardo) wrote :

I think this is fixed, I can't replicate it anymore.

Revision history for this message
Paul Williams (paul1764) wrote :

I agree, I can't replicate it either

Revision history for this message
Lee Colleton (lee-colleton) wrote :

This bug affects me when using the gnome shell on Xenial

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.