[Bug]: Bismuth broken with update

[cas829]

Summary

I use fedora kde spin After updating my system I restarted my system. I could not view any windows while in wayland regardless of what I did, the applications were opening but their windows would not show. Starting in x11 i was able to put the window into floating mode and quick tile the window to act on it. clicking on the window though would make it go away and I have to redo what i did.

Steps to Reproduce

I assume installing the latest kde spin would get this to happen with bismuth

Expected behavior

windows viewable

Screenshots

i can't give you screen shots of the issue in affect b/c I can interact with the application please tell me what other info I can provide to help until then I am probably going to downgrade back

Bismuth version

4.14.0 package 3.13

KDE Plasma version

5.26.3

The platform KWin is running on

Wayland

Additional context

this issue apire on both but is much worse on wayland

[stewy91]

I am having the exact same issue. I use x11 primarily but it's also an issue in Wayland. Let me know if there is any info I can provide.

[ekinmeroglu]

Same issue here. The new app windows seem to be created outside the visible screen, sometimes I can move them into the visible area using the Move action on context menu. Even the widget menus of the system tray are effected - seems to be created, but totally invisible

Using Plasma 5.26.3 on X11, bismuth package is 3.1.3-1.fc36 from the Fedora 36 - x86_64 - Updates repo

[stewy91]

thank you @ekinmeroglu after seeing your comment I tried opening windows and turning off Window Tiling and you are correct. I am going to share my step to recreate what I did.

1. open a few windows with tiling on. (firefox, settings, dolphin)
2. open settings
3. right mouse click on the settings icon on the taskbar and select "More" -> "fullscreen"
4. Turn off window tiling
5. Close Settings
6. select an open application from the taskbar.

This showed a very small, near resized to only show title bar buttons, windows that could be moved and resized now that windows were not tiling. i have included the details of the current package I have installed.

[prawilny]

There's a sensible workaround: https://github.com/Bismuth-Forge/bismuth/issues/451#issuecomment-1317934416

[ekinmeroglu]

Thanks @prawilny - I installed the fc37 package from https://koji.fedoraproject.org/koji/buildinfo?buildID=2090689 and it seems everything's back in order.

[Vistaus]

There's a sensible workaround: #451 (comment)

Not really as I have the issue with 3.1.4 on openSUSE Tumbleweed too, so the issue is NOT fixed in 3.1.4

[aitorpazos]

It is working fine for me in OpenSUSE Tumbleweed (I hit this bug before and the upgrade fixed it for me):

Information for package bismuth:
--------------------------------
Repository     : KDE:Extra
Name           : bismuth
Version        : 3.1.4-4.6
Arch           : x86_64
Vendor         : obs://build.opensuse.org/KDE:Extra
Installed Size : 412.1 KiB
Installed      : Yes
Status         : up-to-date
Source package : bismuth-3.1.4-4.6.src
[...]

System info:

Operating System: openSUSE Tumbleweed 20221214
KDE Plasma Version: 5.26.4
KDE Frameworks Version: 5.101.0
Qt Version: 5.15.7
Kernel Version: 6.0.12-1-default (64-bit)
Graphics Platform: Wayland

[Vistaus]

@aitorpazos That's odd. I'm using the exact same package, yet I do hit this bug (only on Wayland, though - on X11 it's fine - but I primarily use Wayland, so I'd like to find a fix that works for me).

[Vistaus]

It seems like the bug is present with fadora 36 repository not having the latest version

Did you read my post about openSUSE Tumbleweed, where I experience the issue with the latest version? So it's definitely NOT just an issue with the Fedora 36 repo.

[Vistaus]

Is there any way to debug this, to see why I'm having this issue even with 3.1.4?

[cas829]

Thanks @prawilny - I installed the fc37 package from https://koji.fedoraproject.org/koji/buildinfo?buildID=2090689 and it seems everything's back in order.

this worked thank you

[Vistaus]

Is there any way to debug this, to see why I'm having this issue even with 3.1.4?

bump