[Bug 1924895] Re: Settings crashes as soon as it is opened

2021-04-18 Thread Daniel van Vugt 
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


** Changed in: gnome-control-center (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1924895

Title:
  Settings crashes as soon as it is opened

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

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

[Bug 1924859] Re: Virtual machine not grabbing alt+tab input

2021-04-18 Thread Daniel van Vugt 
** Tags added: wayland wayland-session

** Package changed: xorg (Ubuntu) => mutter (Ubuntu)

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1720
   https://gitlab.gnome.org/GNOME/mutter/-/issues/1720

** Also affects: mutter via
   https://gitlab.gnome.org/GNOME/mutter/-/issues/1720
   Importance: Unknown
   Status: Unknown

** Changed in: mutter (Ubuntu)
   Importance: Undecided => Low

** Changed in: mutter (Ubuntu)
   Status: New => Triaged

** Summary changed:

- Virtual machine not grabbing alt+tab input
+ VMware not grabbing Alt+Tab input in Wayland sessions

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

Title:
  VMware not grabbing Alt+Tab input in Wayland sessions

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1924859/+subscriptions

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

[Bug 1924859] [NEW] Virtual machine not grabbing alt+tab input

2021-04-18 Thread Launchpad Bug Tracker 
You have been subscribed to a public bug:

I am currently running VMware workstation pro 16.1. When pressing
alt+tab to toggle the windows in the guest OS, the input is instead
applied to the host OS and not the guest. When switching from Wayland to
Xorg the problem is resolved.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xorg 1:7.7+22ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12
Uname: Linux 5.11.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: 
Error executing command as another user: Request dismissed
Date: Sat Apr 17 15:48:45 2021
DistUpgraded: Fresh install
DistroCodename: hirsute
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Subsystem: ASRock Incorporation 2nd Generation Core Processor Family 
Integrated Graphics Controller [1849:0112]
 NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] GM206 [GeForce GTX 960] 
[1462:3202]
InstallationDate: Installed on 2021-04-16 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic 
root=UUID=739968f7-1aa4-47f1-8d68-55af0ffb428d ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] 
failed with exit code 126: Error executing command as another user: Request 
dismissed
dmi.bios.date: 07/11/2013
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.30
dmi.board.name: Z77 OC Formula
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.30:bd07/11/2013:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77OCFormula:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.104-1build1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

** Affects: mutter (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute ubuntu wayland wayland-session
-- 
Virtual machine not grabbing alt+tab input
https://bugs.launchpad.net/bugs/1924859
You received this bug notification because you are a member of Ubuntu Desktop 
Bugs, which is subscribed to mutter in Ubuntu.

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

[Bug 1924855] Re: Dock is sporadically blank when booting up or when waking from hibernation

2021-04-18 Thread Daniel van Vugt 
Thanks for the bug report. Please try this (from bug 1874578):

gsettings set org.gnome.shell.extensions.dash-to-dock show-mounts false

and then log in again.

** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension-
ubuntu-dock (Ubuntu)

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: New => Incomplete

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

Title:
  Dock is sporadically blank when booting up or when waking from
  hibernation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1924855/+subscriptions

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

[Bug 1924689] Re: Can see some garbage at the edge of the window after changing scale

2021-04-18 Thread Daniel van Vugt 
** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu)

** Changed in: mutter (Ubuntu)
   Importance: Undecided => Low

** Changed in: mutter (Ubuntu)
   Status: New => Triaged

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

Title:
  Can see some garbage at the edge of the window after changing scale

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1924689/+subscriptions

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

[Bug 1924852] Re: Selected output device in Sound settings is not persisted across restarts

2021-04-18 Thread Daniel van Vugt 
** Tags added: focal

** Also affects: pulseaudio (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1924852

Title:
  Selected output device in Sound settings is not persisted across
  restarts

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

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

[Bug 1886059] Re: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260]

2021-04-18 Thread Daniel van Vugt 
You don't need to remove 'ubuntu-appindicat...@ubuntu.com', 'ubuntu-
d...@ubuntu.com', and 'desktop-icons@csoriano' because those are the
core Ubuntu extensions.

Also the set of 'enabled-extensions' does not have to correlate at all
with the set of installed extensions. You can install an extension and
have it disabled, although disabled extensions can still break things in
some cases. That's probably not an issue here.

If you can identify a single extension (or extensions) that causes this
crash then we would appreciate it.

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

Title:
  gnome-shell crashed with assertion failure
  "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886059/+subscriptions

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

[Bug 1924753] Re: gnome-shell repeatedly crashing and core dumping

2021-04-18 Thread Daniel van Vugt 
*** This bug is a duplicate of bug 1886059 ***
https://bugs.launchpad.net/bugs/1886059

Thanks for the bug report. The log seems to confirm this is a duplicate
of bug 1886059, however what we really need is a stack trace from a
core/dump file. Please follow these instructions to get that:

https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

** This bug has been marked a duplicate of bug 1886059
   gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" 
[xcb_io.c:260]

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

Title:
  gnome-shell repeatedly crashing and core dumping

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1924753/+subscriptions

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

[Bug 1922353] Re: Overview sometimes fails to appear or disappear fully when Ubuntu Dock is loaded

2021-04-18 Thread Daniel van Vugt 
Can you rephrase that? Is this bug still occurring?

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

Title:
  Overview sometimes fails to appear or disappear fully when Ubuntu Dock
  is loaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922353/+subscriptions

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

[Bug 1924932] Re: Nautilus default behaviour for executable scripts is poor

2021-04-18 Thread Rick 
I agree

I think the default behavior in Nautilus Preferences should be "Ask what
to do" for "Executable Text Files"

gsettings set org.gnome.nautilus.preferences executable-text-activation
ask

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

Title:
  Nautilus default behaviour for executable scripts is poor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1924932/+subscriptions

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

[Bug 1924932] [NEW] Nautilus default behaviour for executable scripts is poor

2021-04-18 Thread liamdawe 
Public bug reported:

This is a papercut / quality of life issue that's really annoying me.

On other file managers, if you set an .sh file as executable, it will
offer to do something. With Ubuntu + Nautilus, it always by default just
opens it in a text editor. This is really annoying and frankly a bad
default to have.

I know there's the right click menu to run as program, but since Ubuntu
is trying to appeal to the masses here, good default behaviour is needed
IMO.

Example: you download a Linux game from GOG, you make it executable and
then you double click to run -> wait a while as text editor tries to
load a multiple GB installer .sh script, which is made with MojoSetup
(it's a graphical app).

Other file managers first ask what to do with a box like: "run? open as
file? run in terminal?". Ubuntu should ideally do this too.

I just don't think auto-opening big .sh executable files by default, in
a text editor, is very good for users.

** Affects: nautilus (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Description changed:

  This is a papercut / quality of life issue that's really annoying me.
  
  On other file managers, if you set an .sh file as executable, it will
  offer to do something. With Ubuntu + Nautilus, it always by default just
- opens it in a text editor. This is really annoying.
+ opens it in a text editor. This is really annoying and frankly a bad
+ default to have.
  
  I know there's the right click menu to run as program, but since Ubuntu
  is trying to appeal to the masses here, good default behaviour is needed
  IMO.
  
  Example: you download a Linux game from GOG, you make it executable and
  then you double click to run -> wait a while as text editor tries to
  load a multiple GB installer .sh script, which is made with MojoSetup
  (it's a graphical app).
  
  Other file managers first ask what to do with a box like: "run? open as
- file? run in terminal?"
+ file? run in terminal?". Ubuntu should ideally do this too.
  
  I just don't think auto-opening big .sh executable files by default, in
  a text editor, is very good for users.

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

Title:
  Nautilus default behaviour for executable scripts is poor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1924932/+subscriptions

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

[Bug 1924932] Re: Nautilus default behaviour for executable scripts is poor

2021-04-18 Thread Launchpad Bug Tracker 
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: nautilus (Ubuntu)
   Status: New => Confirmed

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

Title:
  Nautilus default behaviour for executable scripts is poor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1924932/+subscriptions

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

[Bug 1908429] Re: gnome-shell fills syslog: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal conn

2021-04-18 Thread Damien Lecan 
Disk full today! Same error messages

syslog.* files about 30-40GB

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

Title:
  gnome-shell fills syslog: Attempting to run a JS callback during
  garbage collection. This is most likely caused by destroying a Clutter
  actor or GTK widget with ::destroy signal connected, or using the
  destroy(), dispose(), or remove() vfuncs. Because it would crash the
  application, it has been blocked. The offending callback was
  SourceFunc().

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1908429/+subscriptions

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

[Bug 1924852] Re: Selected output device in Sound settings is not persisted across restarts

2021-04-18 Thread Filippo Ghibellini 
# Temporary Workaround for others who face this

Get the list of available sinks:

```
$ pactl list sinks

Sink #1
State: IDLE
Name: 
alsa_output.usb-Audio_Technica_Corp_ATR2100x-USB_Microphone-00.analog-stereo
Description: ATR2100x-USB Microphone Analog Stereo
Driver: module-alsa-card.c
Sample Specification: s16le 2ch 44100Hz
Channel Map: front-left,front-right
Owner Module: 26
Mute: no
Volume: front-left: 5282 /   8% / -65.62 dB,   front-right: 49145 /  
75% / -7.50 dB
balance 0.89
Base Volume: 65536 / 100% / 0.00 dB
Monitor Source: 
alsa_output.usb-Audio_Technica_Corp_ATR2100x-USB_Microphone-00.analog-stereo.monitor
Latency: 34631 usec, configured 4 usec
Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY 
Properties:
alsa.resolution_bits = "16"
device.api = "alsa"
device.class = "sound"
alsa.class = "generic"
alsa.subclass = "generic-mix"
alsa.name = "USB Audio"
alsa.id = "USB Audio"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.device = "0"
alsa.card = "3"
alsa.card_name = "ATR2100x-USB Microphone"
alsa.long_card_name = "Audio Technica Corp ATR2100x-USB 
Microphone at usb-:08:00.3-3.3, full speed"
alsa.driver_name = "snd_usb_audio"
device.bus_path = "pci-:08:00.3-usb-0:3.3:1.0"
sysfs.path = 
"/devices/pci:00/:00:08.1/:08:00.3/usb3/3-3/3-3.3/3-3.3:1.0/sound/card3"
udev.id = "usb-Audio_Technica_Corp_ATR2100x-USB_Microphone-00"
device.bus = "usb"
device.vendor.id = "0909"
device.vendor.name = "Audio-Technica Corp."
device.product.id = "004d"
device.product.name = "ATR2100x-USB Microphone"
device.serial = "Audio_Technica_Corp_ATR2100x-USB_Microphone"
device.form_factor = "microphone"
device.string = "front:3"
device.buffering.buffer_size = "352800"
device.buffering.fragment_size = "176400"
device.access_mode = "mmap+timer"
device.profile.name = "analog-stereo"
device.profile.description = "Analog Stereo"
device.description = "ATR2100x-USB Microphone Analog Stereo"
module-udev-detect.discovered = "1"
device.icon_name = "audio-input-microphone-usb"
Ports:
analog-output-headphones: Headphones (priority: 9900)
Active Port: analog-output-headphones
Formats:
pcm

Sink #2
State: SUSPENDED
Name: alsa_output.pci-_08_00.4.analog-stereo
Description: Starship/Matisse HD Audio Controller Analog Stereo
Driver: module-alsa-card.c
Sample Specification: s16le 2ch 44100Hz
Channel Map: front-left,front-right
Owner Module: 27
Mute: no
Volume: front-left: 19660 /  30% / -31.37 dB,   front-right: 19660 /  
30% / -31.37 dB
balance 0.00
Base Volume: 65536 / 100% / 0.00 dB
Monitor Source: alsa_output.pci-_08_00.4.analog-stereo.monitor
Latency: 0 usec, configured 0 usec
Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY 
Properties:
alsa.resolution_bits = "16"
device.api = "alsa"
device.class = "sound"
alsa.class = "generic"
alsa.subclass = "generic-mix"
alsa.name = "ALC1220 Analog"
alsa.id = "ALC1220 Analog"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.device = "0"
alsa.card = "2"
alsa.card_name = "HD-Audio Generic"
alsa.long_card_name = "HD-Audio Generic at 0xfc80 irq 73"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-:08:00.4"
sysfs.path = 
"/devices/pci:00/:00:08.1/:08:00.4/sound/card2"
device.bus = "pci"
device.vendor.id = "1022"
device.vendor.name = "Advanced Micro Devices, Inc. [AMD]"
device.product.id = "1487"
device.product.name = "Starship/Matisse HD Audio Controller"
device.string = "front:2"
device.buffering.buffer_size = "17664"
device.buffering.fragment_size = "2944"
device.access_mode = "mmap"
device.profile.name = "analog-stereo"
device.profile.description = "Analog Stereo"
device.description = "Starship/Matisse HD Audio

[Bug 1924895] [NEW] Settings crashes as soon as it is opened

2021-04-18 Thread Vadim Peretokin 
Public bug reported:

Just opening the settings causes it to almost immediately crash.


❯ gnome-control-center


(gnome-control-center:12969): dconf-WARNING **: 09:14:26.286: failed to commit 
changes to dconf: Could not connect: Connection refused
Error creating rfkill proxy: (null)
Segmentation fault (core dumped)
~ 
❯ 
~ 
❯ gnome-control-center user-accounts

(gnome-control-center:13142): dconf-WARNING **: 09:15:10.855: failed to
commit changes to dconf: Could not connect: Connection refused

(gnome-control-center:13142): dconf-WARNING **: 09:15:11.085: failed to commit 
changes to dconf: Could not connect: Connection refused
Segmentation fault (core dumped)
~ took 16s 
❯ gdb gnome-control-center
GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from gnome-control-center...
(No debugging symbols found in gnome-control-center)
(gdb) r
Starting program: /usr/bin/gnome-control-center 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffea9e0700 (LWP 13237)]
[New Thread 0x7fffdf05b700 (LWP 13238)]
[New Thread 0x7fffde85a700 (LWP 13239)]
[New Thread 0x7fffde059700 (LWP 13240)]
[New Thread 0x7fffdd858700 (LWP 13241)]
[New Thread 0x7fffdcc17700 (LWP 13242)]
[New Thread 0x7fffc7fff700 (LWP 13243)]
[New Thread 0x7fffc77fe700 (LWP 13244)]
[New Thread 0x7fffc6ffd700 (LWP 13245)]

(gnome-control-center:13233): dconf-WARNING **: 09:15:38.054: failed to commit 
changes to dconf: Could not connect: Connection refused
Error creating rfkill proxy: (null)

Thread 8 "pool-gnome-cont" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffc7fff700 (LWP 13243)]
0x77ca6ac3 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
(gdb) bt
#0  0x77ca6ac3 in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x77ca6e1c in  () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7637e5a1 in __nptl_deallocate_tsd () at pthread_create.c:301
#3  0x7637f62a in __nptl_deallocate_tsd () at pthread_create.c:256
#4  start_thread (arg=) at pthread_create.c:488
#5  0x762a6293 in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
(gdb) q
A debugging session is active.

Inferior 1 [process 13233] will be killed.

Quit anyway? (y or n) y
~ took 20s 
❯ gnome-control-center --version
gnome-control-center 3.36.5
~ 
❯ ubuntu-bug gnome-control-center

(gio open:15213): GLib-GIO-CRITICAL **: 09:17:11.048:
g_dbus_connection_flush: assertion 'G_IS_DBUS_CONNECTION (connection)'
failed

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-control-center 1:3.36.5-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101
Uname: Linux 5.4.0-71-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 18 09:16:22 2021
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-02-15 (1522 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1924895

Title:
  Settings crashes as soon as it is opened

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

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