Open Bug 2007778 Opened 5 months ago Updated 4 months ago

[KDE 5.x] All toolbar buttons become un-clickable /broken except Downloads on linux kde wayland & vertical tabs enabled

Categories

(Core :: Widget: Gtk, defect, P3)

Firefox 146
defect

Tracking

()

UNCONFIRMED

People

(Reporter: ragy.mahmoud, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:146.0) Gecko/20100101 Firefox/146.0

Steps to reproduce:

Randomly happens, Can't track the steps to reproduce, Yet happened more than 20 times with me, I suspect the following:
Vertical tabs functionality
Error related to Linux / KDE Plasma / Wayland Combo
Sleep / Hibernation
Picture in picture (Laptop screen only, No monitors attached)

Actual results:

Suddenly all the buttons become broken / unclickable / unhoverable, except for the downloads button

Can resize the window only using shortcuts (Win + arrows or page up/down)

Expected results:

All buttons should be permanently clickable

The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Widget: Gtk
Product: Firefox → Core

Which KDE version do you run?
Thanks.

Flags: needinfo?(ragy.mahmoud)
Priority: -- → P3
Summary: All toolbar buttons become un-clickable /broken except Downloads on linux kde wayland & vertical tabs enabled → [KDE] All toolbar buttons become un-clickable /broken except Downloads on linux kde wayland & vertical tabs enabled

(In reply to Martin Stránský [:stransky] (ni? me) from comment #2)

Which KDE version do you run?
Thanks.

KDE Plasma v: 5.27.5

Flags: needinfo?(ragy.mahmoud)

It's known KDE 5.x bug, please update to 6.x line.

Blocks: wayland-kde
Summary: [KDE] All toolbar buttons become un-clickable /broken except Downloads on linux kde wayland & vertical tabs enabled → [KDE 5.x] All toolbar buttons become un-clickable /broken except Downloads on linux kde wayland & vertical tabs enabled
You need to log in before you can comment on or make changes to this bug.