There is a way to firefox to integrate more with KDE
https://wiki.archlinux.org/index.php/Firefox#KDE_integration
Hi, since Iāve updated the day before yesterday, I am having some serious problem again. My Screen freezes and I am also unable to switch TTY. SysRQ + REI getās me back to lightdmās login screen, but mehhh this canāt be a viable solution. Does anybody have some intell for me?
Thanks a lot ![]()
kernel: amdgpu 0000:09:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1040 thread Xorg:cs0 pid 1114)
kernel: amdgpu 0000:09:00.0: amdgpu: in page starting at address 0x000080010d00a000 from client 27
kernel: amdgpu 0000:09:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00101031
kernel: amdgpu 0000:09:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8)
kernel: amdgpu 0000:09:00.0: amdgpu: MORE_FAULTS: 0x1
kernel: amdgpu 0000:09:00.0: amdgpu: WALKER_ERROR: 0x0
kernel: amdgpu 0000:09:00.0: amdgpu: PERMISSION_FAULTS: 0x3
kernel: amdgpu 0000:09:00.0: amdgpu: MAPPING_ERROR: 0x0
kernel: amdgpu 0000:09:00.0: amdgpu: RW: 0x0
kernel: gmc_v9_0_process_interrupt: 68560 callbacks suppressed
@XRaTiX that did the trick! Iāll share in here exactly what I did to make Firefox integrate better with KDE, and it was much simpler than I assumed! Thank you so much!
@PetervB try this out:
- Make sure the packages xdg-desktop-portal and xdg-desktop-portal-kde are installed. (They should be by default on a Manjaro KDE installationn.)
- Open up Firefox, and in the address bar type about:config, then hit Enter
- If you see a āwarningā just proceed. Itās not as dangerous as the warning portrays.
- Search for widget.use-xdg-desktop-portal
- For the option widget.use-xdg-desktop-portal, change it from false to true (by double-clicking it)
- Close Firefox and re-launch it. Try opening or saving files, images, downloads, etc. Enjoy your KDialog seamlessly integrated with your KDE desktop!

For me, testing branch with kernel511 works fine #Gnome
@_thomas I donāt have a fix for it yet, but I posted a similar issue I and a lot of people have been going through here. Hope you can find it useful, or drop any information you find worth mentioning.
Iāve just been over to the Mesa site looking at release notes for Mesa 21.01 & 21.02, and unless I donāt know what to look for (very possible) I canāt find mention of this bug. I wonder if this gets fixed? lot of Linux users use older intel hardware, so youād think this would get addressed.
Just found the Mesa developers working on this, discussion:
Thanks winnie
