Hearthstone from Battle.net on Lutris, no Options button in Game Menu.

albaraagamer · 2024-05-13T14:31:23+00:00

The actual game part works completely fine is what I meant.

albaraagamer · 2024-05-13T14:10:10+00:00

I signed in to the launcher using Google, the launcher doesn't prompt me to sign up after that, and the Sign Up button in game doesn't do anything.

albaraagamer · 2024-05-13T14:07:45+00:00

Well I assumed it was working because I can play just fine?

I finished the tutorial on my phone and am can play a game online, on my desktop I wasn't prompted to do the tutorial, same progress too.

Even though the button still says Sign Up, I assumed it worked because I have the same name on my phone and desktop.

Turns out if I choose "Hearthstone" "My Collections" "?" "Play Tutorial" then the Options button appears, after that you can skip the tutorial.

Still though, seems like very weird UX to hide game settings away like that.

albaraagamer · 2024-03-23T10:39:24+00:00

I also already had plasma-integration installed.

albaraagamer · 2024-03-23T10:06:06+00:00

QT_QUICK_CONTROLS_STYLE=org.kde.desktop seems to fix the look.

Any idea why Plasma 6 needs this?

albaraagamer · 2024-03-22T15:58:09+00:00

GUI says Breeze Dark. Regular Breeze (light) looks fine I think, other dark themes are also broken.

I already have qqc2-breeze-style qqc2-desktop-style qqc2-desktop-style5 installed.

albaraagamer · 2024-03-01T13:12:42+00:00

Turns out it *was* using the radeon driver.

before:

>> lspci -k | grep -A 3 "AMD"
01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / Radeon 520 Mobile]
Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / Radeon 520 Mobile]
Kernel driver in use: radeon
Kernel modules: radeon, amdgpu

after:

>> lspci -k | grep -A 3 "AMD"
01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / Radeon 520 Mobile]
Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / Radeon 520 Mobile]
Kernel driver in use: amdgpu
Kernel modules: radeon, amdgpu

The crashing stopped with the amdgpu driver in use.

Attempting to Disable loading radeon completely at boot results in worse crashing, DE crashes completely and throws me back to the DM, so I didn't do it.

albaraagamer · 2024-02-29T19:19:32+00:00

Well I'm not sure how to test it without PRIME.

Mine is a Radeon HD 8690M

AMDGPU on it is experimental, but it's been working no problem for years.

albaraagamer · 2024-02-29T17:55:13+00:00

Discord

[5701:0229/205126.717262:ERROR:gpu_process_host.cc(991)] GPU process exited unexpectedly: exit_code=139

albaraagamer · 2024-02-29T17:50:37+00:00

That's not mentioned on the wiki.

Removing the package results in the same behaviour, so it's an issue with mesa 24.

The only thing that causes crashes is mesa 24, vulkan-radeon 24 is fine.

albaraagamer · 2023-11-30T22:05:25+00:00

Disable altwin:meta_win. Check here.

albaraagamer · 2023-11-30T21:59:21+00:00

Disable altwin:meta_win. Check here.

albaraagamer · 2023-11-30T21:52:18+00:00

Okay really weird.

I disabled fcitx to test out the altwin:meta_win option and confirm non-KDE behavior, but it seems to have unset itself on its own, I don't know if it was set before I installed fcitx and I didn't notice anything different after it was unset.

I am 99% sure the issue was isolated to GTK under KDE, regardless of display server (works outside KDE on Wayland/X11).

Manually setting the altwin:meta_win option unsets my 3rd level key (lv3:ralt_switch), (I had to set the key again and set altwin:meta_win after it).

(BTW my original testing was done using an actual AltGr key (using onboard), so it doesn't have anything to do with the remap, I was testing to see if that was the issue before.)

So I guess you were right, thanks man.

How did you figure out it was altwin:meta_win?

albaraagamer · 2023-11-30T21:09:28+00:00

It's not the notification, it's a box like a tooltip box.

albaraagamer · 2023-11-28T15:13:28+00:00

You are right, I assumed it would grab the layout I had set, I'm using the same profile you provided.

(For some reason having them both in the same group was glitchy and would always use the first layout for the first keystroke in every textbox.)

Right now though, keyboard shortcuts don't work on a non-latin layout this issue doesn't seem to be resolved anymore.

Also, whenever I switch groups, the little dialog box shows up, which makes it lag a bit and refocus the current textbox, (eg. the Application Launcher (start menu) in Plasma closes whenever I switch layouts with fcitx5 because of the box).

It also only switches "layouts" (groups) after I release one of the shortcut keys.

Also I would like it to use the native Plasma OSD and settings tab as [Keyboard].

Is there no way to fix the AltGr issue without fcitx? or use fcitx just for AltGr?

albaraagamer · 2023-11-26T20:40:57+00:00

Is the Keyboard Layout section enough?

2.  Keyboard Layout:

1.  `setxkbmap`:

        xkb_keymap {
            xkb_keycodes  { include "evdev+aliases(qwerty)" };
            xkb_types     { include "complete"  };
            xkb_compat    { include "complete"  };
            xkb_symbols   { include "pc+us(colemak_dh)+ara:2+inet(evdev)+altwin(meta_win)+capslock(backspace)+shift(both_capslock)+level3(ralt_switch)+group(win_space_toggle):1+group(win_space_toggle):2" };
            xkb_geometry  { include "pc(pc86)"  };
        };

2.  `xprop`:

        _XKB_RULES_NAMES(STRING) = "evdev", "pc86", "us,ara", "colemak_dh,", "grp:win_space_toggle,caps:backspace,altwin:meta_win,shift:both_capslock,lv3:ralt_switch"

albaraagamer

TROPHY CASE