Arch Linux

babbleshack

Member

Registered: 2015-02-10

Posts: 4

Gnome-control-center(re) crash

Gnome-control-center wont start, when I try to start from the terminal I am presented with

 Failed to register: Timeout was reached 

I have tried reinstalling gnome-control-center via pacman. This has made no changes.

I enabled the  scale-monitor-framebuffer experimental-feature from dconf, dissabling this has made no differance.

I run gnome 3.28 on wayland from the arch repository.

My journalctl -b | grep gnome-control-center is:

 
Mar 27 12:59:06 babblebook gnome-control-center.desktop[2325]: Failed to register: Timeout was reached
Mar 27 13:02:18 babblebook gnome-software[1377]: failed to rescan: Failed to parse /usr/share/applications/gnome-control-center.desktop file: cannot process file of type application/x-desktop
Mar 27 13:03:59 babblebook gnome-control-center.desktop[3607]: Failed to register: Timeout was reached
Mar 27 13:04:48 babblebook gnome-control-center.desktop[3743]: Failed to register: Timeout was reached
Mar 27 13:08:54 babblebook gnome-control-c[5545]: gnome-control-center: Fatal IO error 2 (No such file or directory) on X server :0.
Mar 27 13:13:58 babblebook gnome-control-center.desktop[7748]: Failed to register: Timeout was reached
Mar 27 13:15:16 babblebook gnome-control-center.desktop[7949]: Failed to register: Timeout was reached

Last edited by babbleshack (2018-03-27 12:29:10)

ewaller

Administrator

From: Pasadena, CA

Registered: 2009-07-13

Posts: 20,721

Re: Gnome-control-center(re) crash

https://bbs.archlinux.org/viewtopic.php?id=235651  ?

---

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way

babbleshack

Member

Registered: 2015-02-10

Posts: 4

Re: Gnome-control-center(re) crash

https://bbs.archlinux.org/viewtopic.php?id=235651  ?

Thanks buddy!
Ill follow the info at the link. There is a workaround there for now.