this post was submitted on 08 Mar 2024
23 points (100.0% liked)

KDE

5412 readers
115 users here now

KDE is an international technology team creating user-friendly free and open source software for desktop and portable computing. KDE’s software runs on GNU/Linux, BSD and other operating systems, including Windows.

Plasma 6 Bugs

If you encounter a bug, proceed to https://bugs.kde.org/, check whether it has been reported.

If it hasn't, report it yourself.

PLEASE THINK CAREFULLY BEFORE POSTING HERE.

Developers do not look for reports on social media, so they will not see it and all it does is clutter up the feed.

founded 1 year ago
MODERATORS
carlschwan@lemmy.kde.social
Bro666@lemmy.kde.social
herzenschein@pawb.social
Aniqakhokhar@lemmy.kde.social
23
Firefox On Plasma 6 Wayland Dragging and Rearranging A Bookmark Auto Opens A Bookmark (lemmy.ml)
submitted 9 months ago by WadamT@lemmy.ml to c/kde@lemmy.kde.social
4 comments fedilink hide all child comments
 

cross-posted from: https://lemmy.ml/post/12930181

Does anyone experience this bug with Plasma 6 Wayland and Firefox Wayland? Basically you drag and rearrange a bookmark in 'other bookmark' or home page, FF auto opens a bookmark above the bookmark you rearranged.

Video demo

  • OS: Arch Linux with Plasma 6 from official repo
  • Firefox version: 123.0.1 (64-bit)

Already filed a bug at Firefox bugzilla

you are viewing a single comment's thread
view the rest of the comments
[–] WadamT@lemmy.ml 1 points 8 months ago (1 children)

I am on Plasma 6.0.2 (Arch Linux). The bug seems still there. Reported to KDE bugzilla after this post.

Follow here - https://bugs.kde.org/show_bug.cgi?id=483029

[–] PumpkinEscobar@lemmy.world 1 points 8 months ago (1 children)

Sorry to hear that, I may have overstated, I think I got distracted/focused mainly at the mouse cursor offset / interacting with something at a different position problem. That seemed to get fixed for me with 6.0.2, I don't see the dragging thing but I'm on X11 still, maybe that's a factor

[–] WadamT@lemmy.ml 2 points 8 months ago

This bug is no longer happening in 6.0.2 after a restart.