segmentation fault (core dumped)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-control-center (Ubuntu) |
Expired
|
Low
|
Unassigned |
Bug Description
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 19.04
Release: 19.04
Codename: disco
$ gnome-control-
22:48:42.0979 cc-object-storage: DEBUG: Finished creating D-Bus proxy for CcObjectStorage
22:48:42.0979 cc-object-storage: DEBUG: Adding object GDBusProxy (CcObjectStorag
22:48:42.0979 cc-object-storage: DEBUG: Finished creating D-Bus proxy for CcObjectStorage
22:48:42.0979 cc-object-storage: DEBUG: Adding object GDBusProxy (CcObjectStorag
22:48:42.0979 display-cc-panel: WARNING: no sunset data, using 16.00
22:48:42.0979 display-cc-panel: DEBUG: setting adjustment 16.000 to 16:00
22:48:42.0980 display-cc-panel: WARNING: no sunrise data, using 8.00
22:48:42.0980 display-cc-panel: DEBUG: setting adjustment 8.000 to 8:00
22:48:42.0982 cc-object-storage: DEBUG: Finished creating D-Bus proxy for CcObjectStorage
22:48:42.0982 cc-object-storage: DEBUG: Adding object GDBusProxy (CcObjectStorag
22:48:42.0990 display-cc-panel: DEBUG: SensorProxy vanished
22:48:42.0990 display-cc-panel: DEBUG: Has no accelerometer
22:48:42.0991 display-cc-panel: DEBUG: Resetting current config!
22:48:42.0991 GLib-GObject: CRITICAL: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
[1] 12354 segmentation fault (core dumped) gnome-control-
$ dmesg
[ 1811.497720] gnome-control-
[ 1811.497728] Code: 40 00 48 8b 2b 4c 89 e6 48 89 ef e8 ca f9 ff ff 31 d2 31 f6 48 89 ef e8 ce f9 ff ff 48 8b 5b 08 48 85 db 75 dd 5b 5d 41 5c c3 <48> 8b 07 ff a0 98 00 00 00 0f 1f 80 00 00 00 00 48 8b 07 ff a0 a0
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions: wiki.ubuntu. com/DebuggingPr ogramCrash and upload the backtrace (as an attachment) to the bug report
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
* Could you try to obtain a backtrace following the instructions at http://
This will help us to find and resolve the problem.