3 posts were split to a new topic: Systemtray bluetooth menu is empty after latest updates
It does not, no. On cold boot the built-in keyboard stops working from the initramfs stage & will not work even after I reach the GUI. However, it does work in GRUB.
This was not the case before the most recent update. Keyboard didn’t work in initramfs but was fine once I got to the GUI. So something has changed.
I have the UM325SA, btw. Maybe it’s a model specific thing? I haven’t been able to find any other solutions - I’m sorry 
No worries! It was fixed for me as mentioned in one of the earlier posts- had to set some new kernel option. It most likely is some model specific thing, since I didn’t have your issue earlier, and your solution didn’t work either. Just gotta try everything 
Did you generate an image with that custom mkinitpcio.conf file ?
Creating a /etc/mkinitcpio-custom.conf from the original file but using the arch solution worked for me.
I also overwrote the original 5.16 kernel initramfs file with the new mkinitcpio-custom.conf, and it worked : mkinitcpio --config /etc/mkinitcpio_custom.conf --generate /boot/initramfs-5.16-x86_64.img --kernel 5.16.2-1-MANJARO
I love your username!
I was able to chroot into my borked system and update zfs-utils without a glitch. I was back into my system in minutes.
updating the Python packages took a while but I am now up and running.
thank you for the support, particularly @philm for reverting the changes in zfs-utils.
Just wondering: what environment variables do you have for applying the theme to both Qt5 and Qt6 applications?
AFAIK qt5ct and qt6ct both require to be set to QT_QPA_PLATFORMTHEME, which takes a single value…
I saw those &, just for kicks, I tried it out on mine. Seems to work!
As an aside, I believe that on Manjaro the settings go into a file in the /etc/modprobe.d/ directory - rather than the file /etc/modprobe.conf.
I’m sure someone will correct me if I’m wrong or the distinction is irrelevant.
After this update, fish shell overrides the default cursor shape (block) for kitty terminal and sets cursor to beam!?
How do I get the old behavior/cursor back?
EDIT:
Solution: add shell_integration no-cursor to your kitty.conf
(Why is this suddenly needed, and it wasn’t before - no idea)
Hello,
Since You and @kI3RO are on xfce, I’d like to add my two cents on the metter 
…
I did not change anything in Kvantum Manager.
I just installed qt6tc and set the background to kvantum, changed font, etc… just like @Strit said in his post above ( waaayy above ).
From terminal
$ echo $QT_QPA_PLATFORMTHEME
qt5ct
So nothing is changed.
Hope this clears it for you…
Cheers…
1 Like
update also wiped my qbittorrent settings including my using a proxy which I dont appreciate as I’ve just accidentally exposed my ip.
qt6ct crashes with Segmentation fault when i select qt6gtk2. 
I could try setting directly through the config file, but i don’t want to risk it. I’ll do with qbittorrent-qt5 for the time being, until the paint dries.
To be continued…
Thank you very much! Can now unlock my system again.
/cheers
Maybe I wasn’t clear enough. Don’t change anything in Kvantum Manager.
In Kvantum Manager I have set only the theme to match my system theme and nothing else.
Current theme KVAdaptaMaiaDark it matches my system theme.
Open qt6tc and in Appearance first tab Style should be kvantum, Standard dialogs should be default or GTK3 your preference! For me both work.
Also set Icon Theme and the others to match your system. Apply and OK.
It works just fine for me for qBittorrent.
Edit qt6gtk2 → I don’t have that package installed.
Edit 2 However qBittorrent matches my system theme ( dark theme ) and works fine for now.
Where is it? I can’t find it. Can you provide a full path to that option or a screenshot? There is no “Config->Apearence” anywhere, only “Configure active theme”. No menus or anything alike.
Edit, latest: Has since been updated and fixed.
Having issues with Brave browser (package brave-browser, v 1.34.80-1) …
After latest update it seems I can’t rearrange tabs without issue (opens new window instead of moving)
Anyone else seeing the same behaviour?
Edit: Clearing cache and reinstalling does not fix this
part of the issue on browser derived of chromium v97.0.4692.71, was fixed in v97.0.4692.99
2 Likes
Can confirm: 1279532 - chromium - An open-source project to help move the web forward. - Monorail
Time to return to Chrome stable
1 Like