inxi
hat@hatpc:~$ inxi -F --filter
System:
Kernel: 5.19.0-1-amd64 arch: x86_64 bits: 64 Desktop: i3 v: 4.20.1
Distro: Debian GNU/Linux bookworm/sid
Machine:
Type: Desktop System: ASUS product: All Series v: N/A
serial: <superuser required>
Mobo: ASUSTeK model: Z87-DELUXE v: Rev 1.xx serial: <superuser required>
BIOS: American Megatrends v: 1504 date: 10/03/2013
CPU:
Info: quad core model: Intel Core i5-4670 bits: 64 type: MCP cache:
L2: 1024 KiB
Speed (MHz): avg: 1175 min/max: 800/3800 cores: 1: 800 2: 2300 3: 800
4: 800
Graphics:
Device-1: NVIDIA TU106 [GeForce GTX 1650] driver: nvidia v: 470.141.03
Device-2: Microdia Integrated Camera type: USB driver: uvcvideo
Display: x11 server: X.Org v: 1.21.1.4 with: Xwayland v: 22.1.3 driver:
X: loaded: nvidia unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia
resolution: 1920x1080~60Hz
OpenGL: renderer: NVIDIA GeForce GTX 1650/PCIe/SSE2 v: 4.6.0 NVIDIA
470.141.03
Audio:
Device-1: Intel 8 Series/C220 Series High Definition Audio
driver: snd_hda_intel
Device-2: NVIDIA TU106 High Definition Audio driver: snd_hda_intel
Device-3: C-Media Redragon Gaming Headset type: USB
driver: hid-generic,snd-usb-audio,usbhid
Sound Server-1: ALSA v: k5.19.0-1-amd64 running: yes
Sound Server-2: PulseAudio v: 15.0 running: yes
Sound Server-3: PipeWire v: 0.3.58 running: yes
Network:
Device-1: Intel Ethernet I217-V driver: e1000e
IF: eno1 state: down mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
driver: r8169
IF: enp9s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-3: Broadcom BCM4352 802.11ac Wireless Network Adapter
driver: bcma-pci-bridge
Bluetooth:
Device-1: ASUSTek BCM20702A0 type: USB driver: btusb
Report: hciconfig ID: hci0 state: up address: <filter> bt-v: 2.1
Drives:
Local Storage: total: 2.1 TiB used: 27.97 GiB (1.3%)
ID-1: /dev/sda vendor: SanDisk model: SSD PLUS 240GB size: 223.58 GiB
ID-2: /dev/sdb vendor: Seagate model: ST2000DM006-2DM164 size: 1.82 TiB
ID-3: /dev/sdc vendor: SanDisk model: SDSSDHP064G size: 59.63 GiB
Partition:
ID-1: / size: 218.07 GiB used: 27.97 GiB (12.8%) fs: ext4 dev: /dev/sda1
Swap:
ID-1: swap-1 type: partition size: 975 MiB used: 0 KiB (0.0%)
dev: /dev/sda5
Sensors:
System Temperatures: cpu: 35.0 C mobo: N/A gpu: nvidia temp: 32 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 40%
Info:
Processes: 210 Uptime: 15m Memory: 15.57 GiB used: 1.98 GiB (12.7%)
Shell: Bash inxi: 3.3.21
workaround
dconf reset -f /org/gnome/control-center/
Provavelmente funciona por evitar o aplicativo de tentar carregar as configurações de cor ao iniciar.
GDB
hat@hatpc:~$ gdb gnome-control-center
GNU gdb (Debian 12.1-3) 12.1
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
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:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
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) run
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 0x7ffff07ff640 (LWP 5397)]
[New Thread 0x7fffefffe640 (LWP 5398)]
[New Thread 0x7fffef7da640 (LWP 5399)]
[Thread 0x7fffef7da640 (LWP 5399) exited]
[New Thread 0x7fffef7da640 (LWP 5400)]
[New Thread 0x7fffdffff640 (LWP 5401)]
[New Thread 0x7fffdf7fe640 (LWP 5402)]
[New Thread 0x7fffdeffd640 (LWP 5403)]
[New Thread 0x7fffde7fc640 (LWP 5404)]
[New Thread 0x7fffddffb640 (LWP 5405)]
[New Thread 0x7fffdcbff640 (LWP 5406)]
[New Thread 0x7fffc7fff640 (LWP 5407)]
[New Thread 0x7fffc77fe640 (LWP 5408)]
[New Thread 0x7fffc6ffd640 (LWP 5409)]
[New Thread 0x7fffc67fc640 (LWP 5410)]
[New Thread 0x7fffc5ffb640 (LWP 5411)]
[New Thread 0x7fffc57fa640 (LWP 5412)]
[Thread 0x7fffc5ffb640 (LWP 5411) exited]
[Thread 0x7fffc57fa640 (LWP 5412) exited]
[New Thread 0x7fffc57fa640 (LWP 5413)]
[New Thread 0x7fffc5ffb640 (LWP 5414)]
[Thread 0x7fffc57fa640 (LWP 5413) exited]
[Thread 0x7fffc5ffb640 (LWP 5414) exited]
[New Thread 0x7fffc5ffb640 (LWP 5415)]
[Thread 0x7fffc5ffb640 (LWP 5415) exited]
[New Thread 0x7fffc5ffb640 (LWP 5416)]
[New Thread 0x7fffc57fa640 (LWP 5417)]
[Thread 0x7fffc5ffb640 (LWP 5416) exited]
[Thread 0x7fffc57fa640 (LWP 5417) exited]
[New Thread 0x7fffc57fa640 (LWP 5418)]
[Thread 0x7fffc57fa640 (LWP 5418) exited]
Thread 1 "gnome-control-c" received signal SIGSEGV, Segmentation fault.
0x00005555555d1390 in cc_color_device_set_expanded ()
(gdb) exit
A debugging session is active.
Inferior 1 [process 5394] will be killed.
Quit anyway? (y or n) y
hat@hatpc:~$
O aplicativo fecha quando abro as configurações de cor e não tenho muita noção do porque.
Ao tentar abrir denovo ele apenas aparece por alguns segundos e logo em seguida se vai. A unica maneira que achei de fazer ele abrir sem imediatamente fechar foi abrindo pelo GDB ( GNU Debugger ), e mesmo assim a aplicação não fuciona.
Alguem para o resgate?