Actually it looks like a common issue:

https://errors.ubuntu.com/problem/52cceae54b9e2fbd142648250df0027efdebcb2e

** Description changed:

+ https://errors.ubuntu.com/problem/52cceae54b9e2fbd142648250df0027efdebcb2e
+ 
+ ---
+ 
  i need help
  
  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Tue Apr  7 14:53:42 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2020-04-07 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Beta amd64 
(20200405)
  ProcCmdline: gnome-control-center sound
  ProcEnviron:
-  LANGUAGE=fr_FR
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=<set>
-  LANG=fr_FR.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=fr_FR
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=<set>
+  LANG=fr_FR.UTF-8
+  SHELL=/bin/bash
  SegvAnalysis:
-  Segfault happened at: 0x7f57bb0eb1ea <__GI_____strtoul_l_internal+58>:       
movsbq 0x0(%r13),%rax
-  PC (0x7f57bb0eb1ea) ok
-  source "0x0(%r13)" (0x00000000) not located in a known VMA region (needed 
readable region)!
-  destination "%rax" ok
+  Segfault happened at: 0x7f57bb0eb1ea <__GI_____strtoul_l_internal+58>:       
movsbq 0x0(%r13),%rax
+  PC (0x7f57bb0eb1ea) ok
+  source "0x0(%r13)" (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=0x7fff3a4881c8, base=10, 
group=<optimized out>, loc=0x7f57bb289960 <_nl_C_locobj>) at 
../stdlib/strtol_l.c:292
-  ?? () from /lib/x86_64-linux-gnu/libcogl.so.20
-  ?? () from /lib/x86_64-linux-gnu/libcogl.so.20
-  ?? () from /lib/x86_64-linux-gnu/libcogl.so.20
-  ?? () from /lib/x86_64-linux-gnu/libcogl.so.20
+  __GI_____strtoul_l_internal (nptr=0x0, endptr=0x7fff3a4881c8, base=10, 
group=<optimized out>, loc=0x7f57bb289960 <_nl_C_locobj>) at 
../stdlib/strtol_l.c:292
+  ?? () from /lib/x86_64-linux-gnu/libcogl.so.20
+  ?? () from /lib/x86_64-linux-gnu/libcogl.so.20
+  ?? () from /lib/x86_64-linux-gnu/libcogl.so.20
+  ?? () from /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 cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

** Changed in: gnome-control-center (Ubuntu)
       Status: Expired => Confirmed

** Summary changed:

- gnome-control-center crashed with SIGSEGV in 
_cogl_gpu_info_parse_version_string()
+ gnome-control-center crashed with SIGSEGV in strtoul() from 
_cogl_gpu_info_parse_version_string()

** Summary changed:

- gnome-control-center crashed with SIGSEGV in strtoul() from 
_cogl_gpu_info_parse_version_string()
+ gnome-control-center crashed with SIGSEGV in __GI_____strtoul_l_internal() 
from _cogl_gpu_info_parse_version_string()

** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #1019
   https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1019

** Also affects: gnome-control-center via
   https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1019
   Importance: Unknown
       Status: Unknown

** Changed in: gnome-control-center (Ubuntu)
   Importance: Low => Medium

** Tags added: bionic groovy xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871385

Title:
  gnome-control-center crashed with SIGSEGV in
  __GI_____strtoul_l_internal() from
  _cogl_gpu_info_parse_version_string()

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1871385/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to