Activity log for bug #1759604

Date Who What changed Old value New value Message
2018-03-28 15:18:08 Jeremy Bícha bug added bug
2018-03-28 15:24:07 Jeremy Bícha description Test Case ========= From Ubuntu 18.04, click the top right of the screen to open the system status menu. Click the gear button at the bottom to open the Settings app. In the Settings app, click Devices > Printers. Close the Settings app and then use the system status menu to re-open Settings. Navigate to the Printers panel. gnome-control-center crashes Other Info ========== This is also reproducible by opening the Settings app from the Activities Overview. This is not reproducible by running gnome-control-center from the command line. It's also odd that running gnome-control-center will always open the last opened panel (this is a GNOME 3.28 feature), but running it from either the Activities Overview or from the system status menu will only open the last opened panel if it is not in the Details or Devices submenus. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.0-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 28 11:09:04 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-10-13 (166 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012) ProcCmdline: gnome-control-center --overview SegvAnalysis: Segfault happened at: 0x563e01746371: mov 0x90(%rbp),%rsi PC (0x563e01746371) ok source "0x90(%rbp)" (0x00000090) not located in a known VMA region (needed readable region)! destination "%rsi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: () () () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV UpgradeStatus: Upgraded to bionic on 2017-11-24 (123 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo Test Case ========= From Ubuntu 18.04, click the top right of the screen to open the system status menu. Click the gear button at the bottom to open the Settings app. In the Settings app, click Devices > Printers. Close the Settings app and then use the system status menu to re-open Settings. Navigate to the Printers panel. gnome-control-center crashes Other Info ========== I can reproduce the crash in Debian Buster also. This is also reproducible by opening the Settings app from the Activities Overview. This is not reproducible by running gnome-control-center from the command line. It's also odd that running gnome-control-center will always open the last opened panel (this is a GNOME 3.28 feature), but running it from either the Activities Overview or from the system status menu will only open the last opened panel if it is not in the Details or Devices submenus. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.0-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 28 11:09:04 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-10-13 (166 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012) ProcCmdline: gnome-control-center --overview SegvAnalysis:  Segfault happened at: 0x563e01746371: mov 0x90(%rbp),%rsi  PC (0x563e01746371) ok  source "0x90(%rbp)" (0x00000090) not located in a known VMA region (needed readable region)!  destination "%rsi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop:  ()  ()  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0  g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV UpgradeStatus: Upgraded to bionic on 2017-11-24 (123 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sbuild sudo
2018-03-28 15:33:06 Apport retracing service bug added subscriber Crash bug triagers for Ubuntu packages
2018-03-28 15:33:08 Apport retracing service attachment removed CoreDump.gz https://bugs.launchpad.net/bugs/1759604/+attachment/5093624/+files/CoreDump.gz
2018-03-28 15:33:08 Apport retracing service attachment removed Disassembly.txt https://bugs.launchpad.net/bugs/1759604/+attachment/5093626/+files/Disassembly.txt
2018-03-28 15:33:09 Apport retracing service attachment removed ProcMaps.txt https://bugs.launchpad.net/bugs/1759604/+attachment/5093630/+files/ProcMaps.txt
2018-03-28 15:33:09 Apport retracing service attachment removed ProcStatus.txt https://bugs.launchpad.net/bugs/1759604/+attachment/5093631/+files/ProcStatus.txt
2018-03-28 15:33:10 Apport retracing service attachment removed Registers.txt https://bugs.launchpad.net/bugs/1759604/+attachment/5093632/+files/Registers.txt
2018-03-28 15:33:10 Apport retracing service attachment removed Stacktrace.txt https://bugs.launchpad.net/bugs/1759604/+attachment/5093633/+files/Stacktrace.txt
2018-03-28 15:33:10 Apport retracing service attachment removed ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1759604/+attachment/5093634/+files/ThreadStacktrace.txt
2018-03-28 15:33:16 Apport retracing service marked as duplicate 1754924
2018-03-28 15:33:16 Apport retracing service information type Private Public
2018-03-28 15:33:18 Apport retracing service tags amd64 apport-crash bionic need-amd64-retrace wayland-session amd64 apport-crash bionic wayland-session