Someone in the github discussion of the issue recommended `killall ibus-daemon` after booting.
Someone in the github discussion of the issue recommended
killall ibus-daemon after booting.
RInstalling Bazzite on new hardware
RTesting things out
Ayou could try that, im recommending the env variable cause less intrusive
WYeah, I like that.
Athat bar is tiny lol
KIf that has no downsides it could be added to bazzite-steam
KAs a workaround
WIt took me a few days or weeks of "I think something is wrong but I'm not sure what." So some others -might- be affected but haven't identified what the deal is yet?
KI think Japanese and Chinese input make heavy use of ibus though
KYeah I'd love to know what sets it off, clearly not consistent
RI am running a 4K screen after all lol
WI don't know the first thing about ibus, but someone else in that thread mentioned that
IBUS_ENABLE_SYNC_MODE=2
JYeah p. much reliant on it for IME features
Jit's possible to use fcitix with gnome I think but ibus is pretty well integrated standard
RWhat're you folks working on right now?
KLet me know if that works for you
WIBUS_ENABLE_SYNC_MODE=2If it does I can see about automating it
KRip
JLinux be like we finally got good GPU support lets break keyboards now
WI am also including my vcapture thing, so will test the other recommended one with it to troubleshoot.
Aits all gui anyway you can just click it who need keyboard
WIncluding the obs_vkcapture=1,
OBS_VKCAPTURE=1 XMODIFIERS="@im=null" %command%OBS_VKCAPTURE=1 IBUS_ENABLE_SYNC_MODE=2 %command%try =0 maybe?
WOn it.
WTho the github commenter said "It only happens with IBUS_ENABLE_SYNC_MODE=1 not in mode 0 or 2, seemingly because it never hits that codepath in mode 0 or 2."
WConfirmed with mode=0, the problem is still present.
WYour original suggestion still seems like the winner.
Amaybe different problem or something more specific then
WThanks again for the find. This prevents me from playing m/kb games with a controller, and from otherwise pulling my hair out.
Anp
WDo you think added context of x11 not affecting the issue and that native non-proton games don't affect it? Is that useful to add to the github comments, or do you think they're well on the scent already?
Ai think most are already talking about proton
Aand proton does not run natively in wayland anyway
WThe things that don't run natively in wayland will continue to run per normal in xwayland after we discontinue including x11 in the distro? That is, xwayland is not dependent on x11?
Aif you use amd, x11 already gone for few months lol
Aor longer
Axwayland is a way for running x11 apps under wayland
Jwhen touch keyborad in instaler
Aim pretty sure upstream need to implement it
WI am on nvidia and had to use x11 until 555 driver came to :testing, otherwise it was unusable. I'm back on :latest with 555 and everything runs great. Firefox is working for me too, so that must have gotten fixed.
Zhello guys, whats up?
Zi have a second screen and its kinda empty, i mean when i was on kde i use it as system monitor using widgets, on windows i use hwinfo or something like that, is there any way i can utilize my second monitor that way, btw the monitor is small, like 8 inch, 1280x800 from Jonsbo D31 case
Anow on gnome? or still on kde
Gis there an official way to run EXEs on a specific proton prefix?
Gfor things like mod installers, etc
OSteam Tinker Launch
Oinstall with ProtonUp-Qt or the Gnome equivalent (edit: ProtonPlus), once it runs hit the menu and somewhere in the options you can set it to run a custom executable
Oit's a lot of tinkering but if you run a lot of mods you're probably used to that
Aprobably protontricks?
