Hello World,
Sorry for this thread, but I’m new to linux and with so many interconnected systems each with it’s own developers/mainteiners I have no idea what exactly is causing the problem let alone where to report it.
So is https[Still can’t include links, even your own…]bugs[DOT]kde[DOT]org/ the right place to report the following problem? Cause I tried googling “report a bug to wayland”, but couldn’t find anything except a place to report libinput bugs but I have no idea if thats the cause…
Gonna copy&paste the relevant parts from the last place I asked for help, let me know if you need anything else please.
Thank you.
[quote=“VIKINGS”]
Hello World,
So some genius thought it a good idea to rename tracker3 to tinysparql(at least that’s what my google search turned up, not that I understand any of this) and I tried to update without changing it but it wouldn’t let me so in the end I answered yes and now stuff doesn’t work.
When I say “stuff” it’s just easyeffects for the moment, but I expect to find more in time.
If I try to launch it from the console I get:
[vikings@VIKINGSKINGDOM ~]$ easyeffects
(easyeffects:5436): Gtk-WARNING **: 09:31:35.093: Unknown key gtk-modules in /home/vikings/.config/gtk-4.0/settings.ini
WARNING: radv is not a conformant Vulkan implementation, testing use only.
[2024-09-23 09:31:35.505] [MANGOHUD] [error] [overlay_params.cpp:647] Unknown option 'io_stats'
Gdk-Message: 09:31:35.752: Error 71 (Protocol error) dispatching to Wayland display.
[vikings@VIKINGSKINGDOM ~]$
Tried to reinstall it didn’t help, suggestions? 
LE: Yeap, add 2 more, pavucontrol and mission-center don’t work anymore eighter, basically I don’t think anything below/under gtk4 works anymore(but I’m not gonna try everything since I don’t know what some of those are/do)
[vikings@VIKINGSKINGDOM ~]$ pactree -r tinysparql
tinysparql
├─grilo-plugins
├─gtk3
│ ├─abiword
│ ├─appstream-glib
│ ├─brave-bin
│ ├─gnome-desktop
│ │ └─lutris-git
│ ├─goffice
│ │ └─abiword
│ ├─gspell
│ │ └─yad
│ │ ├─eos-apps-info
│ │ ├─eos-log-tool
│ │ ├─reflector-simple
│ │ └─welcome
│ ├─gtkmm3
│ ├─gtksourceview3
│ │ └─yad
│ ├─gtksourceview4
│ │ └─meld
│ ├─libappindicator-gtk3
│ ├─libdbusmenu-gtk3
│ │ └─libappindicator-gtk3
│ ├─libhandy
│ │ └─yelp
│ ├─libwnck3
│ ├─linux-steam-integration
│ ├─lutris-git
│ ├─meld
│ ├─webkit2gtk
│ ├─webkit2gtk-4.1
│ │ ├─lutris-git
│ │ ├─yad
│ │ └─yelp
│ ├─wxwidgets-gtk3
│ │ ├─aegisub
│ │ └─python-wxpython
│ └─yad
└─gtk4
├─easyeffects
├─gtkmm-4.0
│ └─pavucontrol
├─gtksourceview5
├─libadwaita
│ ├─easyeffects
│ ├─mission-center
│ └─zenity
│ └─steam
│ └─linux-steam-integration
├─libportal-gtk4
├─pavucontrol
└─zenity
[vikings@VIKINGSKINGDOM ~]$
If I try to open mission-center with the console I get:
[vikings@VIKINGSKINGDOM ~]$ missioncenter
MissionCenter::Application-Message: 10:17:00.625: Starting Mission Center v0.6.1
(missioncenter:5742): Gtk-WARNING **: 10:17:00.650: Unknown key gtk-modules in /home/vikings/.config/gtk-4.0/settings.ini
(missioncenter-gatherer:5750): Gatherer::Main-MESSAGE: 7:17:0.807: Starting v0.6.1...
(missioncenter-gatherer:5750): Gatherer::Main-MESSAGE: 7:17:0.808: Initializing system state...
(missioncenter:5742): MissionCenter::Gatherer-CRITICAL **: 10:17:00.952: Call to Gatherer Ping method failed on try 0: The name is not activatable
WARNING: radv is not a conformant Vulkan implementation, testing use only.
WARNING: radv is not a conformant Vulkan implementation, testing use only.
[2024-10-09 10:17:01.011] [MANGOHUD] [[2024-10-09 10:17:01.011] [MANGOHUD] [errorerror] [overlay_params.cpp:647] Unknown option 'io_stats'
] [overlay_params.cpp:647] Unknown option 'io_stats'
Gdk-Message: 10:17:01.088: Error 71 (Protocol error) dispatching to Wayland display.
[vikings@VIKINGSKINGDOM ~]$
Here are the contents of that ini file(I hashed out every line one by one to see if the programs would open until the entire document was hashed out and nothing…):
[Settings]
gtk-application-prefer-dark-theme=false
gtk-cursor-theme-name=XSKHSE
gtk-cursor-theme-size=48
gtk-decoration-layout=icon:minimize,maximize,close
gtk-enable-animations=true
gtk-font-name=Noto Sans, 11
gtk-icon-theme-name=darkine
gtk-modules=colorreload-gtk-module:window-decorations-gtk-module
gtk-primary-button-warps-slider=true
gtk-sound-theme-name=ocean
gtk-xft-dpi=127795
And here’s the output of that inxi -Fzxc0 command:
[vikings@VIKINGSKINGDOM ~]$ inxi -Fzxc0
System:
Kernel: 6.10.10-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
Desktop: KDE Plasma v: 6.1.5 Distro: EndeavourOS base: Arch Linux
Machine:
Type: Desktop Mobo: MSI model: B250M MORTAR (MS-7A69) v: 1.0
serial: <superuser required> UEFI: American Megatrends v: 2.60
date: 06/29/2018
CPU:
Info: quad core model: Intel Core i7-7700 bits: 64 type: MT MCP
arch: Kaby Lake rev: 9 cache: L1: 256 KiB L2: 1024 KiB L3: 8 MiB
Speed (MHz): avg: 4000 min/max: 800/4200 cores: 1: 4000 2: 4000 3: 4000
4: 4000 5: 4000 6: 4000 7: 4000 8: 4000 bogomips: 57616
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 31 [Radeon RX 7900 XT/7900
XTX/7900M] vendor: ASRock driver: amdgpu v: kernel arch: RDNA-3
bus-ID: 03:00.0
Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 24.1.2
compositor: kwin_wayland driver: X: loaded: amdgpu dri: radeonsi gpu: amdgpu
resolution: 1969x1108
API: EGL v: 1.5 drivers: kms_swrast,radeonsi,swrast platforms:
active: gbm,wayland,x11,surfaceless,device inactive: N/A
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.3.0-devel
glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 7900 XT (radeonsi
navi31 LLVM 18.1.8 DRM 3.57 6.10.10-arch1-1)
API: Vulkan v: 1.3.295 drivers: amd surfaces: xcb,xlib,wayland devices: 1
Audio:
Device-1: Intel 200 Series PCH HD Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel bus-ID: 00:1f.3
Device-2: Advanced Micro Devices [AMD/ATI] Navi 31 HDMI/DP Audio
driver: snd_hda_intel v: kernel bus-ID: 03:00.1
Device-3: Razer USA RC30-026902 Gaming Headset [Nari Essential Wireless
Receiver] driver: hid-generic,snd-usb-audio,usbhid type: USB bus-ID: 1-4:2
API: ALSA v: k6.10.10-arch1-1 status: kernel-api
Server-1: PipeWire v: 1.2.4 status: active
Network:
Device-1: Intel Ethernet I219-V vendor: Micro-Star MSI driver: e1000e
v: kernel port: N/A bus-ID: 00:1f.6
IF: enp0s31f6 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
Local Storage: total: 22.3 TiB used: 21.14 TiB (94.8%)
ID-1: /dev/nvme0n1 vendor: A-Data model: SX6000PNP size: 476.94 GiB
temp: 39.9 C
ID-2: /dev/sda vendor: Seagate model: ST8000DM004-2CX188 size: 7.28 TiB
ID-3: /dev/sdb vendor: Seagate model: ST8000DM004-2U9188 size: 7.28 TiB
ID-4: /dev/sdc vendor: Seagate model: ST8000DM004-2CX188 size: 7.28 TiB
Partition:
ID-1: / size: 43.99 GiB used: 28.65 GiB (65.1%) fs: ext4 dev: /dev/nvme0n1p7
ID-2: /home size: 35.61 GiB used: 21.56 GiB (60.6%) fs: ext4
dev: /dev/nvme0n1p8
Swap:
ID-1: swap-1 type: partition size: 2 GiB used: 1.99 GiB (99.7%)
dev: /dev/nvme0n1p6
Sensors:
System Temperatures: cpu: 59.0 C mobo: N/A gpu: amdgpu temp: 38.0 C
Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Info:
Memory: total: 8 GiB available: 7.72 GiB used: 3.58 GiB (46.3%)
Processes: 283 Uptime: 3h 8m Init: systemd
Packages: 1469 Compilers: clang: 18.1.8 gcc: 14.2.1 Shell: Bash v: 5.2.32
inxi: 3.3.36
[vikings@VIKINGSKINGDOM ~]$
Anyway, back to the matter at hand, based on what @ddnn said yesterday I figured out this morning how to switch between x11 and wayland and gave it a shot and indeed it seems things work just fine under x11. So I guess I’m gonna go report this to the wayland people…?
Wish me luck, I’ll be back to update this thread when/if a solution is found. Till then thank you for trying to help everyone.
[quote]
And maybe are there any other commands I can run to check if other stuff is going wrong under the hood now? Cause that crap just ain’t normal…
