[kasts] [Bug 482153] Podcasts not playing

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=482153

Tammes Burghard  changed:

   What|Removed |Added

 CC||k...@kuchenmampfer.de

--- Comment #1 from Tammes Burghard  ---
Looks to me like it does not have proper network access from inside the snap. I
assume you are trying to stream. Can you download the podcast and then play
from there?

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 486543] [Wayland] Dolphin window doesn't open under certain conditions when minimized

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=486543

Tammes Burghard  changed:

   What|Removed |Added

 CC||k...@kuchenmampfer.de

--- Comment #2 from Tammes Burghard  ---
For me, that setting does nothing and it just opens another window,
interesting.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Alligator] [Bug 479190] content can be scrolled out of its page

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=479190

Tammes Burghard  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |UPSTREAM

--- Comment #6 from Tammes Burghard  ---
Now I am using 24.02.2 and can't reproduce it anymore. So I guess it was maybe
a qt6.7 beta bug or something that is now fixed.

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 482122] In split view the location bar of right side adds a drag-able separator in toolbar

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=482122

--- Comment #4 from Tammes Burghard  ---
I honestly don't really care about it. Its not really discoverable, so I never
noticed it exists until this bug report. Now that I know about it, it seems
useful in very specific situations, so not removing it for these makes sense I
guess. But it also does not really matter, so if it adds maintenance burden, it
can be removed in my opinion.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 484391] Digital clock causes applets in system tray jitter back and forth

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=484391

--- Comment #3 from Tammes Burghard  ---
Ah then its based in the font. Yeah makes sense. I am using Noto Sans (whatever
the default is).

Am 25. März 2024 15:50:47 MEZ schrieb DeKay :
>https://bugs.kde.org/show_bug.cgi?id=484391
>
>--- Comment #2 from DeKay  ---
>(In reply to Tammes Burghard from comment #1)
>> I can confirm that and it seems like only the 4 is one pixel wider than all
>> the other numbers.
>
>The bounce between 0 -> 1 -> 2 is especially noticable to me.  But it bounces
>between other numbers too, like 7 -> 8.  I'm using the Inter font BTW.
>
>-- 
>You are receiving this mail because:
>You are on the CC list for the bug.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kscreenlocker] [Bug 483919] Toggle keyboard light key doesn't work in lock screen

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=483919

Tammes Burghard  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 CC||k...@kuchenmampfer.de
 Ever confirmed|0   |1

--- Comment #5 from Tammes Burghard  ---
I can confirm the brightness controls and color switch buttons work, but toggle
does not. I am on a tuxedo aura 15 gen 1 in case that is relevant.

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 484386] Solarised theme inconsistent black/gray

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=484386

Tammes Burghard  changed:

   What|Removed |Added

 Resolution|NOT A BUG   |---
 Status|NEEDSINFO   |CONFIRMED
 Ever confirmed|0   |1

--- Comment #3 from Tammes Burghard  ---
Oh yes, looks like it is. Sorry

-- 
You are receiving this mail because:
You are watching all bug changes.

[konsole] [Bug 484386] Solarised theme inconsistent black/gray

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=484386

Tammes Burghard  changed:

   What|Removed |Added

 Resolution|--- |NOT A BUG
 Status|REPORTED|NEEDSINFO
 CC||k...@kuchenmampfer.de

--- Comment #1 from Tammes Burghard  ---
I can confirm that these colors are visible/invisible as you describe. But, as
far as I know, Solarized is a third party theme not provided by KDE, so we
can't do anything about it here and you will have to ask the theme's developer
instead. Where did you get the theme from?

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 484391] Digital clock causes applets in system tray jitter back and forth

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=484391

Tammes Burghard  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 CC||k...@kuchenmampfer.de
 Ever confirmed|0   |1

--- Comment #1 from Tammes Burghard  ---
I can confirm that and it seems like only the 4 is one pixel wider than all the
other numbers.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 483608] Discover Crash when searching

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=483608

--- Comment #1 from Tammes Burghard  ---
Created attachment 167206
  --> https://bugs.kde.org/attachment.cgi?id=167206=edit
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 483608] New: Discover Crash when searching

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=483608

Bug ID: 483608
   Summary: Discover Crash when searching
Classification: Applications
   Product: Discover
   Version: 6.0.2
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: plasma-b...@kde.org
  Reporter: k...@kuchenmampfer.de
CC: aleix...@kde.org
  Target Milestone: ---

Application: plasma-discover (6.0.2)

Qt Version: 6.6.2
Frameworks Version: 6.0.0
Operating System: Linux 6.7.9-arch1-1 x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 6.0.2 [CoredumpBackend]

-- Information about the crash:
Discover crashes whenever I search for something. I only really use it for
flatpaks. It might not be able to access the arch repo side of things and
crashes because of that. Just a guess, it could be anything and I can't make
sense of the backtrace.

The crash can be reproduced every time.

-- Backtrace (Reduced):
#5  0x79897ff7ed4a in KNSCore::ResultsStream::fetch (this=0x6418ad87fd10)
at /usr/src/debug/knewstuff/knewstuff-6.0.0/src/core/resultsstream.cpp:70
#6  0x7989b4590ca9 in QtPrivate::QSlotObjectBase::call (a=0x7ffc8884dd68,
r=0x6418ad87fd10, this=0x6418a88c7530, this=, r=,
a=) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qobjectdefs_impl.h:433
#7  doActivate (sender=0x6418a8d68130, signal_index=4,
argv=0x7ffc8884dd68) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qobject.cpp:4039
#8  0x7989b4590ca9 in QtPrivate::QSlotObjectBase::call (a=0x7ffc8884de48,
r=0x6418a8d68130, this=0x6418a914f6a0, this=, r=,
a=) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qobjectdefs_impl.h:433
#9  doActivate (sender=0x6418a9201d30, signal_index=4,
argv=0x7ffc8884de48) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qobject.cpp:4039


Reported using DrKonqi

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 482121] Plasma 6 panel has borders on sides

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=482121

Tammes Burghard  changed:

   What|Removed |Added

 Status|REPORTED|NEEDSINFO
 CC||k...@kuchenmampfer.de
 Resolution|--- |WAITINGFORINFO

--- Comment #1 from Tammes Burghard  ---
Sorry, I don't get what you are describing from the screenshot. Can you maybe
show more of your panel and all the way to the screen edge?

Also, I get some empty space on the sides when my panel defloats, but when it
is set to non floating, the widgets move further out.

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 482122] In split view the location bar of right side adds a drag-able separator in toolbar

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=482122

Tammes Burghard  changed:

   What|Removed |Added

 CC||k...@kuchenmampfer.de
 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Tammes Burghard  ---
I can reproduce this on arch with plasma 6 and also find it a bit weird

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 481743] New: confusing edit mode options with multiple panels

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=481743

Bug ID: 481743
   Summary: confusing edit mode options with multiple panels
Classification: Plasma
   Product: plasmashell
   Version: 5.93.0
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: k...@kuchenmampfer.de
CC: niccolo.venera...@gmail.com
  Target Milestone: 1.0

SUMMARY
***
Note that my system is in german and I only guess that the options in question
are named "enter edit mode" and "quit edit mode". But I assume that they are
unique enough so you get what I am referring to.

My observations (see below) let me assume that edit mode kind of works like a
stack where you can stack the edit modes of different panels on top of each
other. Instead, there should be only one edit mode and you should be able to
choose which panel to focus on.
***


STEPS TO REPRODUCE
1. have a panel -> right click it -> enter edit mode
2. add a second panel -> right click it
3. enter edit mode
4. right click the first panel
5. quit edit mode
6. right click it again
7. quit edit mode

OBSERVED RESULT
3. the option is named "enter edit mode" even though I already am in edit mode
(of the other panel)
5. this shows the configuration popup for the first panel
7. now it quits edit mode

EXPECTED RESULT
3. the option should be named something like "edit this panel"
5. this should actually quit edit mode and also there should have been an "edit
this panel" option
7. correct, but inconsistent with 5.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.93.0
KDE Frameworks Version: 5.249.0
Qt Version: 6.7.0
Kernel Version: 6.7.6-arch1-1 (64-bit)
Graphics Platform: Wayland

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 481742] New: Panel configuration popup hidden behind second panel

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=481742

Bug ID: 481742
   Summary: Panel configuration popup hidden behind second panel
Classification: Plasma
   Product: plasmashell
   Version: 5.93.0
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: k...@kuchenmampfer.de
CC: niccolo.venera...@gmail.com
  Target Milestone: 1.0

SUMMARY
***
I was about to report another bug, but now could not reproduce it. However,
while exploring, I found the following one:
***


STEPS TO REPRODUCE
1. Take a standard panel
2. Add a second standard panel
3. Move that to the bottom too
4. Right click the new panel that now sits on top of the first one
5. click start edit mode

OBSERVED RESULT
panel configuration popup appears behind the second panel (it seems to be
positioned relative to the first panel)

EXPECTED RESULT
panel configuration popup appears above the top most panel so nothing is hidden
behind that panel

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.93.0
KDE Frameworks Version: 5.249.0
Qt Version: 6.7.0
Kernel Version: 6.7.6-arch1-1 (64-bit)
Graphics Platform: Wayland

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 481740] Installed page entry not present in the drawer

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=481740

--- Comment #1 from Tammes Burghard  ---
The "Updates" entry also is missing

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 481740] New: Installed page entry not present in the drawer

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=481740

Bug ID: 481740
   Summary: Installed page entry not present in the drawer
Classification: Applications
   Product: Discover
   Version: 5.93.0
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: plasma-b...@kde.org
  Reporter: k...@kuchenmampfer.de
CC: aleix...@kde.org
  Target Milestone: ---

Created attachment 166047
  --> https://bugs.kde.org/attachment.cgi?id=166047=edit
Screenshot of the narrow window

SUMMARY
***
When I make the window so narrow, that the menu at the side hides in a drawer,
that drawer does not contain the "installed" entry anymore.
***


STEPS TO REPRODUCE
1. Make the window so narrow that the left navigation bar hides into a drawer
2. open the drawer by clicking the hamburger menu button

OBSERVED RESULT
Drawer opens, but without "installed" entry

EXPECTED RESULT
Drawer opens with the same entries as the side bar when the window is wider

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.93.0
KDE Frameworks Version: 5.249.0
Qt Version: 6.7.0
Kernel Version: 6.7.5-arch1-1 (64-bit)
Graphics Platform: Wayland

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 447603] Icons in icons only task manager reduce to unusable size when Panel is filled up with other widgets

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=447603

--- Comment #23 from Tammes Burghard  ---
Very nice, thanks for linking it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 481225] Some ideas to improve the interface to change the custom times

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=481225

Tammes Burghard  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1
 CC||k...@kuchenmampfer.de

--- Comment #1 from Tammes Burghard  ---
I can reproduce on Arch Plasma 6 RC2.

And I found slightly better time choosers in
a) The date and time KCM
b) Itinerary where you add a trip
Maybe Components can be copied from one of these places?

-- 
You are receiving this mail because:
You are watching all bug changes.

[NeoChat] [Bug 481088] Neochat Doesn't remember scroll position

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=481088

--- Comment #2 from Tammes Burghard  ---
I just tested this on plasma 6 and it always opens chats at the most recent
message. So I guess this might be fixed there?

-- 
You are receiving this mail because:
You are watching all bug changes.

[NeoChat] [Bug 481088] Neochat Doesn't remember scroll position

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=481088

Tammes Burghard  changed:

   What|Removed |Added

 CC||k...@kuchenmampfer.de

--- Comment #1 from Tammes Burghard  ---
This looks related to https://bugs.kde.org/show_bug.cgi?id=476291, but with a
bit more nuance to it, so I will not mark it as duplicate and leave that
decision to others.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 447603] Icons in icons only task manager reduce to unusable size when Panel is filled up with other widgets

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=447603

Tammes Burghard  changed:

   What|Removed |Added

Version|5.24.0  |5.93.0

--- Comment #20 from Tammes Burghard  ---
Ideas I have for this:

1. Make all the spacers actually width 0
2. collapse as many items as needed in the systemtray into that expandable
arrow widget that already holds hidden items
3. Let the clock fall back to a more compact formatting
4. squeeze everything equally
5. force multiple rows

Yes I know this is quite complicated and a lot of work...

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 480871] Windows can inappropriately be resized to below their minimum sizes

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=480871

--- Comment #18 from Tammes Burghard  ---
Perfect, thank you for pointing out :)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 480871] Windows can inappropriately be resized to below their minimum sizes

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=480871

Tammes Burghard  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---

--- Comment #16 from Tammes Burghard  ---
For both the settings and discover, it reports a min size of 150x150.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 480871] Windows can inappropriately be resized to below their minimum sizes

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=480871

Tammes Burghard  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---

--- Comment #14 from Tammes Burghard  ---
Yes, I can also make the settings window this narrow on a fresh user account.

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 480871] Weird component overlapping when making the window too narrow

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=480871

Tammes Burghard  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |---
 Status|NEEDSINFO   |REPORTED

--- Comment #12 from Tammes Burghard  ---
Both of these ultimately lead me to the same set of settings (as they probably
should).
And there I only have three rules. One each for KeepassXC, Simutrans and MPV.
Nothing that should affect Systemsettings or Discover.

Might this be an arch issue? I originally got my kde stuff from the arch repos
and only switched to the kde unstable repos a few months back.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 478259] Tasks become tiny in tablet mode when certain apps are opened in tablet mode and screen is rotated

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=478259

Tammes Burghard  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REOPENED
 Resolution|WAITINGFORINFO  |---

--- Comment #15 from Tammes Burghard  ---
(In reply to Nate Graham from comment #14)
> I don't. Does the issue still reproduce if you remove them from your panel
> setup?

Yes but only with 150% scaling and when the screen is rotated. Otherwise there
is enough breathing space for the task icons to not be squished together.
>From my understanding, these flexible spacers are actually not so flexible and
take up a lot of space. This makes this issue much more likely to appear
because it only happens when there is not enough space. The underlying issue
that only task icons get squished when there is not enough space fundamentally
is not an issue with the spacers, because the system tray also should not
spread out as much when there is not enough space. However, flexible spacers
should always shrink first and fixing that would make the rest much less
annoying.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 478259] Tasks become tiny in tablet mode when certain apps are opened in tablet mode and screen is rotated

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=478259

--- Comment #13 from Tammes Burghard  ---
(In reply to Nate Graham from comment #3)
> It's expected that the app icons shrink when squeezed by other applets that
> become bigger (*something* has to get squeezed; there's no way around it),
> but it's not expected that the squeezing happens when there's clearly more
> empty space on the panel, as shown in your screenshots. That said, I can't
> reproduce the issue with my 2-in-1 convertible at either 200% screen scale
> or 150% screen scale when I follow your instructions exactly.
> 
> Can you reproduce it with a 100% standard panel with no customizations?

Do you have flexible width spacers around your task icon area? Adding these to
center the task icons might be a relevant customization that I did.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 478259] Tasks become tiny in tablet mode when certain apps are opened in tablet mode and screen is rotated

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=478259

--- Comment #12 from Tammes Burghard  ---
Very correct. In addition to your proposal of the correct behavior, I think
first, the variable width spacers (which I have on both sides of the task
icons) should be squished to 0. And only after that, everything should go back
to desktop spacing and then be uniformly condensed. And potentially allow the
system tray icons to go into multiple rows when needed. This is already
possible for task icons, but I would prefer the system tray to enter that state
first.

For now, my workaround will be
1. Set the spacers surrounding the task icons to constant width 0
2. Remove some icons from the system tray
3. Allow task icons to form two rows when there is not enough space. Sadly, I
have to make my panel thicker for this to not be unusable.

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 480871] Weird component overlapping when making the window too narrow

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=480871

--- Comment #9 from Tammes Burghard  ---
On the system I recorded this on, I do indeed use a material-you-dark color
scheme and aritim-dark window decorations. But I can also reproduce this on my
tablet, where I just use normal breeze dark. I did customize things a little
bit there as well, but nothing that I can imagine affects this. Only things
like keyboard shortcuts, enabling workspace switching OSD, etc.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 467182] Cannot pan zoom area to certain locations when using KWin Zoom plugin with certain multi-monitor configurations

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=467182

Tammes Burghard  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1
 CC||k...@kuchenmampfer.de

--- Comment #2 from Tammes Burghard  ---
Acidic light made a video about this explaining it in great detail:
https://yewtu.be/watch?v=3wH0wDqfF5g

And also I can reproduce this on the following system (so it is neither a
problem with X11 nor Nvidia):
Operating System: Crystal Linux 
KDE Plasma Version: 5.93.0
KDE Frameworks Version: 5.249.0
Qt Version: 6.7.0
Kernel Version: 6.7.3-arch1-2 (64-bit)
Graphics Platform: Wayland
Processors: 8 × AMD Ryzen 7 4700U with Radeon Graphics
Memory: 30.7 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: TUXEDO
Product Name: TUXEDO Aura 15 Gen1

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 477825] White bar when floating/unfloating

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=477825

--- Comment #4 from Tammes Burghard  ---
Created attachment 165584
  --> https://bugs.kde.org/attachment.cgi?id=165584=edit
New recording of the bug

Its just a very short flash when I take off my fingers from my touchpad. So
look closely at the panel when it defloats/floats, I purposefully inserted a
little pause before that so there is less confusion.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 477825] White bar when floating/unfloating

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=477825

Tammes Burghard  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Ever confirmed|0   |1
 Resolution|DUPLICATE   |---

--- Comment #3 from Tammes Burghard  ---
(In reply to Nate Graham from comment #2)
> I cannot reproduce this issue with today's git master when I follow your
> steps. Can you still reproduce it?
> 
> *** This bug has been marked as a duplicate of bug 480548 ***

Yes I can still reproduce this. But only with my steps to recreate, not with
the steps of bug 480548. So I think it was not actually a duplicate maybe?

I admit that my previous video recording was bad, so I will make a new one.

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 480871] Weird component overlapping when making the window too narrow

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=480871

--- Comment #7 from Tammes Burghard  ---
And when made too narrow, Discovers UI becomes unresponsive, see
https://kuchenmampfer.de/kde_bug_480871.webm

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 480871] Weird component overlapping when making the window too narrow

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=480871

--- Comment #6 from Tammes Burghard  ---
Created attachment 165583
  --> https://bugs.kde.org/attachment.cgi?id=165583=edit
Discovers UI also can be made too narrow

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 480871] Weird component overlapping when making the window too narrow

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=480871

Tammes Burghard  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---

--- Comment #5 from Tammes Burghard  ---
Ummm, I just grabbed the right border and moved it.
I can reproduce this both on my laptop and on my tablet and on the latter both
with the mouse and with touch.

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 480871] Weird component overlapping when making the window too narrow

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=480871

--- Comment #4 from Tammes Burghard  ---
Created attachment 165582
  --> https://bugs.kde.org/attachment.cgi?id=165582=edit
Me making the window narrow

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 480875] Let tablet mode automatically switch to single tap/click

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=480875

--- Comment #2 from Tammes Burghard  ---
If I shall make individual Bugs for the different issues because autoswitching
that setting is unfeasable, I can of course do that as well.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 480875] Let tablet mode automatically switch to single tap/click

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=480875

--- Comment #1 from Tammes Burghard  ---
If this is better discussed somewhere else (like matrix/discourse/mailing
list), feel free to point me there and I will happily join

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 480875] New: Let tablet mode automatically switch to single tap/click

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=480875

Bug ID: 480875
   Summary: Let tablet mode automatically switch to single
tap/click
Classification: Plasma
   Product: plasmashell
   Version: 5.93.0
  Platform: unspecified
OS: Unspecified
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: Input Method
  Assignee: plasma-b...@kde.org
  Reporter: k...@kuchenmampfer.de
CC: aleix...@kde.org
  Target Milestone: 1.0

I know there has been a lot of discussion on single click versus double click
and double click was chosen because every distro defaults to it. I do agree
with this when using mouse input devices. But for touch, it does not make a lot
of sense for the following reasons:

- Opening recently used files in for example Okular or Kate is impossible with
touch (see https://bugs.kde.org/show_bug.cgi?id=480375 for details)
- You need many tries to open a folder (not from the side bar) in the file
picker because there is no consistently working way to do it via touch
- Dolphin handles this by already automatically switching to single tap when
the tap is not a mouse click but a touch tap. So switching to single click
entirely in tablet mode would only make this more consistent

An alternative to autoswitching to single click would of curse be adressing the
first two issues individually. But this would make it quite likely that many
more issues like these would pop up over time which would need to be adressed
one by one. That is why I chose to primarily propose autoswitching to single
click in tablet mode. Maybe there is also another even more elegant solution,
but I don't know how this works internally well enough to judge this properly.

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 480375] Recently opened files can not be opened via touch

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=480375

Tammes Burghard  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |MOVED

--- Comment #1 from Tammes Burghard  ---
This is fixed by using single click to open stuff.

As the file picker and Dolphin in general are also very touch unfriendly if
double click is used to open stuff because doing that with touch is very
unreliable, I will close this and open a proposal to let the tablet mode
automatically switch to single click.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 480873] Blur behind semi transparent konsole window is not applied in desktop grid and overview

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=480873

--- Comment #1 from Tammes Burghard  ---
The screen recording seems to not like the transition to the overview effect.
But you can see how the window is blurry before and not blurry in the effects.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 480873] New: Blur behind semi transparent konsole window is not applied in desktop grid and overview

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=480873

Bug ID: 480873
   Summary: Blur behind semi transparent konsole window is not
applied in desktop grid and overview
Classification: Plasma
   Product: kwin
   Version: 5.93.0
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: effects-desktop-grid
  Assignee: kwin-bugs-n...@kde.org
  Reporter: k...@kuchenmampfer.de
  Target Milestone: ---

Created attachment 165550
  --> https://bugs.kde.org/attachment.cgi?id=165550=edit
Screen recording of the effects

SUMMARY
***
I have configured konsole to be slightly transparent with blur. When I enter
the desktop grid or the overview effect, that blur disappears.
***


STEPS TO REPRODUCE
1. Open Konsole
2. Open Hamburger Menu
3. Create a new Profile
4. switch to that profile
5. Open the menu again and edit the profile
6. Go to appearance
7. Select the currently used Breeze theme
8. Edit it
9. Add some transparency
10. Enable background blur
11. Click OK twice
12. Multi-finger-swipe up or down to enter the desktop grid or the overview
effect

OBSERVED RESULT
The Konsole window is semi transparent but its background is not blurry

EXPECTED RESULT
The Konsole window is semi transparent and its background blurry

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.93.0
KDE Frameworks Version: 5.249.0
Qt Version: 6.7.0
Kernel Version: 6.7.3-arch1-1 (64-bit)
Graphics Platform: Wayland

-- 
You are receiving this mail because:
You are watching all bug changes.

[systemsettings] [Bug 480871] New: Weird component overlapping when making the window too narrow

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=480871

Bug ID: 480871
   Summary: Weird component overlapping when making the window too
narrow
Classification: Applications
   Product: systemsettings
   Version: 5.93.0
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: k...@kuchenmampfer.de
  Target Milestone: ---

Created attachment 165548
  --> https://bugs.kde.org/attachment.cgi?id=165548=edit
Screen showing the weird overlapping

SUMMARY
***
When making the window too narrow, its components overlap in a weird way
***


STEPS TO REPRODUCE
1. Open systemsettings
2. unmaximize the window
3. resize it to be as narrow as in my screenshot

OBSERVED RESULT
content page goes over the side bar, but buttons below the content page go
behind

EXPECTED RESULT
either the content page disappears or the sidebar closes itself below a minimum
width.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.93.0
KDE Frameworks Version: 5.249.0
Qt Version: 6.7.0
Kernel Version: 6.7.3-arch1-1 (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFRMATION
I tested this with both 100% and 150% scaling

-- 
You are receiving this mail because:
You are watching all bug changes.

[Alligator] [Bug 478077] Choosing an individual feed shows posts of all feeds until refreshing

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=478077

Tammes Burghard  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from Tammes Burghard  ---
This seems to be fixed

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 480604] Settings window is blank

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=480604

Tammes Burghard  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 Resolution|--- |FIXED

--- Comment #2 from Tammes Burghard  ---
It was installed when I just checked. But also the bug seems fixed on RC2 now.
So everything is fine :)

-- 
You are receiving this mail because:
You are watching all bug changes.

[Alligator] [Bug 480749] Crash when opening redstrate post and maximizing Alligator

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=480749

--- Comment #1 from Tammes Burghard  ---
Created attachment 165486
  --> https://bugs.kde.org/attachment.cgi?id=165486=edit
Incorrect images

-- 
You are receiving this mail because:
You are watching all bug changes.

[Alligator] [Bug 480749] New: Crash when opening redstrate post and maximizing Alligator

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=480749

Bug ID: 480749
   Summary: Crash when opening redstrate post and maximizing
Alligator
Classification: Applications
   Product: Alligator
   Version: 24.01.95
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: fe...@posteo.de
  Reporter: k...@kuchenmampfer.de
  Target Milestone: ---

Created attachment 165485
  --> https://bugs.kde.org/attachment.cgi?id=165485=edit
Crash backtrace

SUMMARY
***
Alligator crashes when I open
https://redstrate.com/blog/2024/01/my-work-in-kde-for-january-2024/ and then
maximize the window
***


STEPS TO REPRODUCE
1. Add Planet KDE feed
2. open https://redstrate.com/blog/2024/01/my-work-in-kde-for-january-2024/
3. maximize the window

OBSERVED RESULT
2. Images are not rendered correctly
3. Crash

EXPECTED RESULT
Correct images and no crash

SOFTWARE/OS VERSIONS
Operating System: Crystal Linux 
KDE Plasma Version: 5.93.0
KDE Frameworks Version: 5.249.0
Qt Version: 6.7.0
Kernel Version: 6.7.2-arch1-2 (64-bit)
Graphics Platform: Wayland
Processors: 8 × AMD Ryzen 7 4700U with Radeon Graphics
Memory: 30.7 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: TUXEDO
Product Name: TUXEDO Aura 15 Gen1

-- 
You are receiving this mail because:
You are watching all bug changes.

[Alligator] [Bug 479190] content can be scrolled out of its page

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=479190

--- Comment #4 from Tammes Burghard  ---
Created attachment 165481
  --> https://bugs.kde.org/attachment.cgi?id=165481=edit
Now the text goes behind other things

-- 
You are receiving this mail because:
You are watching all bug changes.

[Alligator] [Bug 479190] content can be scrolled out of its page

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=479190

Tammes Burghard  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|UPSTREAM|---

--- Comment #3 from Tammes Burghard  ---
This is an issue again in RC2, but now the text disappears behind the other
parts of the window instead of going above it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 480630] New: Workspace switching OCD misses switching via overview effect or desktop grid

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=480630

Bug ID: 480630
   Summary: Workspace switching OCD misses switching via overview
effect or desktop grid
Classification: Plasma
   Product: plasmashell
   Version: 5.93.0
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: k...@kuchenmampfer.de
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

SUMMARY
***
The Workspace switching OCD displays arrows for the current motion. But these
arrows seem to get their previous workspace from the last time the OCD was
opened. This allows me to confuse them by switching workspace via the overview
effect or desktop grid which does not trigger the OCD. When I then switch via
gesture, the arrows report an incorrect motion.
***


STEPS TO REPRODUCE
1. Create four workspaces in a row and enter the first one
2. Open either the overview effect or the desktop grid via gesture
3. In one of these effects, navigate to the fourth workspace and enter it
4. switch back to the third workspace via three finger gesture

OBSERVED RESULT
4. The OCD shows arrows to the right on the first and second workspace
indicating I moved from the first to the third workspace

EXPECTED RESULT
4. The OCD shows one arrow to the left on the fourth workspace

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.93.0
KDE Frameworks Version: 5.249.0
Qt Version: 6.7.0
Kernel Version: 6.7.2-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Pentium® CPU 4425Y @ 1.70GHz
Memory: 7.6 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 615
Manufacturer: Microsoft Corporation
Product Name: Surface Go 2
System Version: 1

-- 
You are receiving this mail because:
You are watching all bug changes.

[Spectacle] [Bug 480628] New: Spectacle refuses to do vertical screen recording

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=480628

Bug ID: 480628
   Summary: Spectacle refuses to do vertical screen recording
Classification: Applications
   Product: Spectacle
   Version: 24.01.90
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: noaha...@gmail.com
  Reporter: k...@kuchenmampfer.de
CC: k...@david-redondo.de
  Target Milestone: ---

SUMMARY
***
When I try to do a vertical full screen screen recording, spectacle sometimes
freezes. Sometimes means most of the time if started via keyboard shortcut or
krunner, but only seldomly if started from the terminal.
***


STEPS TO REPRODUCE
1. Rotate device to be vertical
2. Open Spectacle
2. Choose the Recording tab and click the "Full Screen"-button
3. Click somewhere to start the recording
4. If red circle appears in the system try, terminate the recording and try
again
5. Otherwise open the spectacle window from the panel (I had to rotate the
screen back for this due to https://bugs.kde.org/show_bug.cgi?id=478259)
6. Click finish recording

OBSERVED RESULT
1. I get the following output in the terminal:

kpipewire_record_logging: VAAPI: Failed to initialize display
kpipewire_record_logging: DRM device not found
kpipewire_record_logging: VAAPI: Failed to initialize display
kpipewire_record_logging: DRM device not found

3. Spectacle minimizes and I get the following terminal output:

kpipewire_record_logging: VAAPI: Failed to initialize display
kpipewire_record_logging: DRM device not found
kpipewire_record_logging: VAAPI: Failed to initialize display
kpipewire_record_logging: DRM device not found
[libvpx @ 0x768bd01c8080] v1.14.0
[AVFormatContext @ 0x768bd051e340] Unable to choose an output format for '';
use a standard extension for the filename or specify the format manually.
kpipewire_record_logging: Could not deduce output format from file: using WebM.
""
kpipewire_record_logging: Could not open "" Datei oder Verzeichnis nicht
gefunden
kpipewire_record_logging: Could not set up the producing thread

6. Nothing happens, Spectacle is entirely frozen

EXPECTED RESULT
1. No error
3. No error, Spectacle minimizes, starts recording and spawns a red circle in
the system tray that allows me to finish the recording
6. The recording gets finished and saved and Spectacle is overall responsive

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.93.0
KDE Frameworks Version: 5.249.0
Qt Version: 6.7.0
Kernel Version: 6.7.2-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Pentium® CPU 4425Y @ 1.70GHz
Memory: 7.6 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 615
Manufacturer: Microsoft Corporation
Product Name: Surface Go 2
System Version: 1

-- 
You are receiving this mail because:
You are watching all bug changes.

[Spectacle] [Bug 480378] Vertical screen recording is upside down

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=480378

Tammes Burghard  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #6 from Tammes Burghard  ---
Somehow I managed to not get the bug (two times) that was preventing me from
testing this and this one seems to indeed be fixed. Very nice.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Spectacle] [Bug 480627] New: Sometimes, Spectacle freezes when supposed to record its own window

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=480627

Bug ID: 480627
   Summary: Sometimes, Spectacle freezes when supposed to record
its own window
Classification: Applications
   Product: Spectacle
   Version: 24.01.90
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: noaha...@gmail.com
  Reporter: k...@kuchenmampfer.de
CC: k...@david-redondo.de
  Target Milestone: ---

SUMMARY
***
It does not happen every time, but more than half of the time for me. Note that
I might confuse some button or tab namings because I am translating them from
German.
***


STEPS TO REPRODUCE
1. Open Spectacle (in the terminal to get output there)
2. Choose the Recording tab and click the "Window"-button
3. Choose the "Spectacle"-window to record by clicking it
4. Click finish recording

OBSERVED RESULT
1. I get the following output in the terminal:

kpipewire_record_logging: VAAPI: Failed to initialize display
kpipewire_record_logging: DRM device not found
kpipewire_record_logging: VAAPI: Failed to initialize display
kpipewire_record_logging: DRM device not found

3. I get the output above again and the second counter hangs at 0
4. Nothing happens, Spectacle is entirely frozen

EXPECTED RESULT
1. No error
3. No error, the second counter starts counting and Spectacle starts recording
itself
4. The recording gets finished and saved and Spectacle is overall responsive

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.93.0
KDE Frameworks Version: 5.249.0
Qt Version: 6.7.0
Kernel Version: 6.7.2-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Pentium® CPU 4425Y @ 1.70GHz
Memory: 7.6 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 615
Manufacturer: Microsoft Corporation
Product Name: Surface Go 2
System Version: 1

-- 
You are receiving this mail because:
You are watching all bug changes.

[Spectacle] [Bug 480378] Vertical screen recording is upside down

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=480378

--- Comment #5 from Tammes Burghard  ---
Alright, I just upgraded, but now can't even test it due to new bugs. I will
have to file more reports and get them fixed before I can come back to this
one.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 480261] plasmashell sometimes crashes in Plasma::Corona::editModeChanged() when tapping on the desktop with two fingers at the same time

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=480261

Tammes Burghard  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #10 from Tammes Burghard  ---
I just upgraded to the RC2 and this seems to be fixed

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 480605] New: Deleting a clipboard entry does not sync properly

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=480605

Bug ID: 480605
   Summary: Deleting a clipboard entry does not sync properly
Classification: Applications
   Product: kdeconnect
   Version: 24.01.90
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: k...@kuchenmampfer.de
CC: andrew.g.r.hol...@gmail.com
  Target Milestone: ---

SUMMARY
***
This might be an intended feature for normal use, but for the following use
case, it is a security risk in my eyes:

I use the KeepassXC password manager which copies passwords to the clipboard
and automatically deletes them from the clipboard after ten seconds. If my
device is connected to another device, the password remains in the clipboard
history of that other device.
***


STEPS TO REPRODUCE
1. Have two devices (running Plasma 6.0 RC1) connected to each other with
clipboard sharing enabled
2. Copy two pieces of text to the clipboard (we need at least two entries in
the clipboard history)
3. Delete the most recent entry from device A using the clipboard history
plasmoid

OBSERVED RESULT
The entry is deleted on device A, but on device B, it is swapped with the
second most recent entry

EXPECTED RESULT
The entry gets deleted on both devices. At least if it was added to the
clipboard by device A

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.92.0
KDE Frameworks Version: 5.249.0
Qt Version: 6.7.0
Kernel Version: 6.7.1-arch1-1 (64-bit)
Graphics Platform: Wayland

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 480604] New: Settings window is blank

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=480604

Bug ID: 480604
   Summary: Settings window is blank
Classification: Applications
   Product: kdeconnect
   Version: 24.01.90
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: k...@kuchenmampfer.de
CC: andrew.g.r.hol...@gmail.com
  Target Milestone: ---

Created attachment 165398
  --> https://bugs.kde.org/attachment.cgi?id=165398=edit
KDE Connect with blank settings page

STEPS TO REPRODUCE
1. Open the KDE Connect application on Arch Linux Plasma 6.0 RC1
2. Click on the settings button in the bottom left corner of the window

OBSERVED RESULT
A blank window without Content opens

EXPECTED RESULT
A Window containing settings and about information opens

SOFTWARE/OS VERSIONS
Operating System: Crystal Linux 
KDE Plasma Version: 5.92.0
KDE Frameworks Version: 5.248.0
Qt Version: 6.7.0
Kernel Version: 6.7.2-arch1-1 (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION
I can reproduce this on the device above as well as on my tablet (The tablet
uses the breeze dark global theme, my laptop is a bit more customized, both are
connected to each other, but I don't think that is relevant):

Operating System: Arch Linux 
KDE Plasma Version: 5.92.0
KDE Frameworks Version: 5.249.0
Qt Version: 6.7.0
Kernel Version: 6.7.1-arch1-1 (64-bit)
Graphics Platform: Wayland

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 478259] app icons become tiny in tablet mode with unmaximized info center or okular window

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=478259

--- Comment #9 from Tammes Burghard  ---
(In reply to Tammes Burghard from comment #6)
> Alright, with 100% scaling, I can not reproduce 5. anymore, but 6. is still
> an issue.

I can reproduce 5. again, this time with Kasts:
1. Plasma6 RC1 on a tablet
2. Open Kasts in a floating window
3. Detach keyboard to enter tablet mode
4. Icons become tiny

The settings should be the same as above

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 480602] Plasmashell crash when switching workspace via touch and the desktop grid

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=480602

--- Comment #1 from Tammes Burghard  ---
Nicolas Fella already marked this (https://bugs.kde.org/show_bug.cgi?id=480364)
as duplicate of https://bugs.kde.org/show_bug.cgi?id=480261, but Nate Graham
wanted me to make another bug report. Here it is, but I still think it is a
duplicate

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 480261] plasmashell sometimes crashes in Plasma::Corona::editModeChanged() when tapping on the desktop with two fingers at the same time

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=480261

--- Comment #7 from Tammes Burghard  ---
(In reply to Tammes Burghard from comment #6)
> The backtrace looked identical to me, so I figured it is the same bug. But
> sure, I can make a separate one if that helps.

https://bugs.kde.org/show_bug.cgi?id=480602

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 480602] New: Plasmashell crash when switching workspace via touch and the desktop grid

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=480602

Bug ID: 480602
   Summary: Plasmashell crash when switching workspace via touch
and the desktop grid
Classification: Plasma
   Product: plasmashell
   Version: 5.92.0
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: k...@kuchenmampfer.de
  Target Milestone: 1.0

Application: plasmashell (5.92.0)

Qt Version: 6.7.0
Frameworks Version: 5.249.0
Operating System: Linux 6.7.1-arch1-1 x86_64
Windowing System: Wayland
Distribution: Arch Linux
DrKonqi: 5.92.0 [CoredumpBackend]

-- Information about the crash:
Steps to reproduce:

1. Have Plasma 6.0 RC1 under arch linux on a tablet (Mine is the MS Surface Go
2)
2. Have multiple Workspaces (I have 1x4) and be in the first
3. Detach keyboard to enter touch mode
4. Three-finger-swipe down once or three-finger-swipe up twice to enter the
desktop grid view
5. Tap on the second workspace to enter it
6. Wait a bit

What happens:
5. The workspace indicator in the panel says that I am still in workspace 1
even though I am in WS2 (proven by the ability to three-finger-swipe to the
right and switch to WS1)
6. Plasmashell crashes

What should have happened:
5. The workspace indicator correctly reports being in WS2
6. No crash

The crash can be reproduced sometimes.

-- Backtrace:
Application: plasmashell (plasmashell), signal: Segmentation fault


This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[New LWP 16342]
[New LWP 16349]
[New LWP 16353]
[New LWP 16351]
[New LWP 16402]
[New LWP 16431]
[New LWP 16384]
[New LWP 16411]
[New LWP 16385]
[New LWP 16432]
[New LWP 16413]
[New LWP 16409]
[New LWP 16454]
[New LWP 16457]
[New LWP 16416]
[New LWP 16456]
[New LWP 16436]
[New LWP 16410]
[New LWP 16453]
[New LWP 16350]
[New LWP 16412]
[New LWP 16455]
[New LWP 16439]
[New LWP 16414]
[New LWP 16458]
[New LWP 16352]
[New LWP 16359]
[New LWP 16361]
[New LWP 16362]
[New LWP 16374]
[New LWP 16447]
[New LWP 16452]
[New LWP 16360]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `/usr/bin/plasmashell --no-respawn'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7e11f1aac83c in ?? () from /usr/lib/libc.so.6
[Current thread is 1 (Thread 0x7e11ec5609c0 (LWP 16342))]
Cannot QML trace cores :(
[Current thread is 1 (Thread 0x7e11ec5609c0 (LWP 16342))]

Thread 33 (Thread 0x7e11e10006c0 (LWP 16360)):
#0  0x7e11f1aa74ae in ??? () at /usr/lib/libc.so.6
#1  0x7e11f1aa9d40 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x7e11e1d139bc in ??? () at /usr/lib/dri/iris_dri.so
#3  0x7e11e1d0acfc in ??? () at /usr/lib/dri/iris_dri.so
#4  0x7e11f1aaa9eb in ??? () at /usr/lib/libc.so.6
#5  0x7e11f1b2e7cc in ??? () at /usr/lib/libc.so.6

Thread 32 (Thread 0x7e1181c006c0 (LWP 16452)):
#0  0x7e11f1aa74ae in ??? () at /usr/lib/libc.so.6
#1  0x7e11f1aa9d40 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x7e11f16e1f40 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt6Core.so.6
#3  0x7e11f303794b in ??? () at /usr/lib/libQt6Quick.so.6
#4  0x7e11f16d59e3 in ??? () at /usr/lib/libQt6Core.so.6
#5  0x7e11f1aaa9eb in ??? () at /usr/lib/libc.so.6
#6  0x7e11f1b2e7cc in ??? () at /usr/lib/libc.so.6

Thread 31 (Thread 0x7e11826006c0 (LWP 16447)):
#0  0x7e11f1b214c6 in ppoll () at /usr/lib/libc.so.6
#1  0x7e11f16cde33 in qt_safe_poll(pollfd*, unsigned long, QDeadlineTimer)
() at /usr/lib/libQt6Core.so.6
#2  0x7e11f0b52ea2 in ??? () at /usr/lib/libQt6Network.so.6
#3  0x7e11f0ae19a3 in ??? () at /usr/lib/libQt6Network.so.6
#4  0x7e11f0ad9939 in QAbstractSocket::waitForReadyRead(int) () at
/usr/lib/libQt6Network.so.6
#5  0x7e11f0ec2aca in ??? () at /usr/lib/libKF6KIOCore.so.6
#6  0x7e11f0fa6b1d in ??? () at /usr/lib/libKF6KIOCore.so.6
#7  0x7e11f0f81912 in ??? () at /usr/lib/libKF6KIOCore.so.6
#8  0x7e11f16d59e3 in ??? () at /usr/lib/libQt6Core.so.6
#9  0x7e11f1aaa9eb in ??? () at /usr/lib/libc.so.6
#10 0x7e11f1b2e7cc in ??? () at /usr/lib/libc.so.6

Thread 30 (Thread 0x7e11daa006c0 (LWP 16374)):
#0  0x7e11f1b20f6f in poll () at /usr/lib/libc.so.6
#1  0x7e11f01a22f6 in ??? () at /usr/lib/libglib-2.0.so.0
#2  0x7e11f0142162 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7e11f17aba54 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt6Core.so.6
#4  0x7e11f156e39e in
QEventLoop::exec(QFlags) () at

[plasmashell] [Bug 480261] plasmashell sometimes crashes in Plasma::Corona::editModeChanged() when tapping on the desktop with two fingers at the same time

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=480261

--- Comment #6 from Tammes Burghard  ---
The backtrace looked identical to me, so I figured it is the same bug. But
sure, I can make a separate one if that helps.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Spectacle] [Bug 480378] Vertical screen recording is upside down

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=480378

--- Comment #3 from Tammes Burghard  ---
The issue still persists, but that commit is probably not yet included in the
arch kde unstable repo. I will test again when I have the RC2 on my tablet.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kirigami] [Bug 476484] Touch swipe scrolling in ScrollablePage does not work over SelectableLabel text

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=476484

--- Comment #5 from Tammes Burghard  ---
Yes, It is fixed for me as well. Nice :)

-- 
You are receiving this mail because:
You are watching all bug changes.

[Spectacle] [Bug 480378] New: Vertical screen recording is upside down

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=480378

Bug ID: 480378
   Summary: Vertical screen recording is upside down
Classification: Applications
   Product: Spectacle
   Version: 24.01.90
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: noaha...@gmail.com
  Reporter: k...@kuchenmampfer.de
CC: k...@david-redondo.de
  Target Milestone: ---

SUMMARY
***
I made a screen recording of my tablet in vertical orientation and it came out
upside down, see my attachment at
https://bugsfiles.kde.org/attachment.cgi?id=165262
***


STEPS TO REPRODUCE
1. rotate the screen to be vertical
2. record it

OBSERVED RESULT
video is upside down

EXPECTED RESULT
video is correctly oriented

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.92.0
KDE Frameworks Version: 5.248.0
Qt Version: 6.7.0
Kernel Version: 6.7.1-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Pentium® CPU 4425Y @ 1.70GHz
Memory: 7.6 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 615
Manufacturer: Microsoft Corporation
Product Name: Surface Go 2
System Version: 1

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 480377] Weird transparent visual glitch

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=480377

--- Comment #2 from Tammes Burghard  ---
(In reply to Tammes Burghard from comment #1)
> Created attachment 165262 [details]
> Screen recording of the glitchy okular window

It also happened without plasmashell crashing, but the shell crashed a lot
while I tried to consistently reproduce this, so I did not bother to retry
until I get it without crash.

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 480377] Weird transparent visual glitch

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=480377

--- Comment #1 from Tammes Burghard  ---
Created attachment 165262
  --> https://bugs.kde.org/attachment.cgi?id=165262=edit
Screen recording of the glitchy okular window

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 480377] New: Weird transparent visual glitch

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=480377

Bug ID: 480377
   Summary: Weird transparent visual glitch
Classification: Applications
   Product: okular
   Version: 24.01.90
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: k...@kuchenmampfer.de
  Target Milestone: ---

SUMMARY
***
I can not reproduce this consistently, but found a way to make it happen with
about 50% consistency:
Being on a tablet and using touch is essential here I think.
***


STEPS TO REPRODUCE
1. Open Okular and maximize it
2. Open a PDF file
3. go to the next workspace via three-finger-touch-swipe
4. Rotate the tablet to be vertical and in touch mode
5. three-finger-swipe back to the workspace with Okular in it

OBSERVED RESULT
Not always, but often times, the document area becomes transparent and a bunch
of glitches appear, see attached video

EXPECTED RESULT
No visual glitches, the document gets shown in a vertical Okular window

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.92.0
KDE Frameworks Version: 5.248.0
Qt Version: 6.7.0
Kernel Version: 6.7.1-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Pentium® CPU 4425Y @ 1.70GHz
Memory: 7.6 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 615
Manufacturer: Microsoft Corporation
Product Name: Surface Go 2
System Version: 1

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 480375] New: Recently opened files can not be opened via touch

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=480375

Bug ID: 480375
   Summary: Recently opened files can not be opened via touch
Classification: Applications
   Product: okular
   Version: 24.01.90
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: okular-de...@kde.org
  Reporter: k...@kuchenmampfer.de
  Target Milestone: ---

SUMMARY
***
On Okular's start page, I can open recently opened files with a mouse double
click, but not via touch
***


STEPS TO REPRODUCE
1. Open Okular
2. tap on one of the previously opened files
3. double tap on one of the previously opened files

OBSERVED RESULT
The file gets highlighted

EXPECTED RESULT
At least one of these actions should open the file

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.92.0
KDE Frameworks Version: 5.248.0
Qt Version: 6.7.0
Kernel Version: 6.7.1-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Pentium® CPU 4425Y @ 1.70GHz
Memory: 7.6 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 615
Manufacturer: Microsoft Corporation
Product Name: Surface Go 2
System Version: 1

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 480261] plasmashell crashing in Plasma::Corona::editModeChanged() when tapping on the desktop with two fingers at the same time

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=480261

--- Comment #4 from Tammes Burghard  ---
Maybe this info of my duplicate bug can help to reproduce it:

Steps to reproduce:

1. Have Plasma 6.0 RC1 under arch linux on a tablet (Mine is the MS Surface Go
2)
2. Have multiple Workspaces (I have 1x4) and be in the first
3. Detach keyboard to enter touch mode
4. Three-finger-swipe down once or three-finger-swipe up twice to enter the
desktop grid view
5. Tap on the second workspace to enter it
6. Wait a bit

What happens:
5. The workspace indicator in the panel says that I am still in workspace 1
even though I am in WS2 (proven by the ability to three-finger-swipe to the
right and switch to WS1)
6. Plasmashell crashes

What should have happened:
5. The workspace indicator correctly reports being in WS2
6. No crash

The crash can be reproduced every time.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kirigami] [Bug 475117] Kasts built against qt6 version: various errors, menu and dialog glitches

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=475117

--- Comment #9 from Tammes Burghard  ---
This bug report feels quite messy by now. Shall I close and replace it with
three low priority bug reports for 3, 5 and 6?

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kirigami] [Bug 475117] Kasts built against qt6 version: various errors, menu and dialog glitches

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=475117

--- Comment #8 from Tammes Burghard  ---
Update: 1, 2 and 4 are fixed

The others are less important I feel like, but I am also getting a bunch of
errors from Kirigami:

```
file:///usr/lib/qt6/qml/org/kde/kirigami/Separator.qml:50: TypeError: Cannot
read property 'Light' of undefined
file:///usr/lib/qt6/qml/org/kde/kirigami/Separator.qml:41: TypeError: Cannot
read property 'Normal' of undefined
file:///usr/lib/qt6/qml/org/kde/kirigami/Heading.qml:99: TypeError: Cannot read
property 'Secondary' of undefined
file:///usr/lib/qt6/qml/org/kde/kirigami/Heading.qml:97: TypeError: Cannot read
property 'Primary' of undefined
file:///usr/lib/qt6/qml/org/kde/kirigami/Heading.qml:75: TypeError: Cannot read
property 'Normal' of undefined
file:///usr/lib/qt6/qml/org/kde/kirigami/Separator.qml:50: TypeError: Cannot
read property 'Light' of undefined
file:///usr/lib/qt6/qml/org/kde/kirigami/Separator.qml:41: TypeError: Cannot
read property 'Normal' of undefined
file:///usr/lib/qt6/qml/org/kde/kirigami/Separator.qml:50: TypeError: Cannot
read property 'Light' of undefined
file:///usr/lib/qt6/qml/org/kde/kirigami/Separator.qml:41: TypeError: Cannot
read property 'Normal' of undefined
file:///usr/lib/qt6/qml/org/kde/kirigami/Heading.qml:99: TypeError: Cannot read
property 'Secondary' of undefined
file:///usr/lib/qt6/qml/org/kde/kirigami/Heading.qml:97: TypeError: Cannot read
property 'Primary' of undefined
file:///usr/lib/qt6/qml/org/kde/kirigami/Heading.qml:75: TypeError: Cannot read
property 'Normal' of undefined
file:///usr/lib/qt6/qml/org/kde/kirigami/Separator.qml:50: TypeError: Cannot
read property 'Light' of undefined
```

-- 
You are receiving this mail because:
You are watching all bug changes.

[Alligator] [Bug 479190] content can be scrolled out of its page

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=479190

Tammes Burghard  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |UPSTREAM

--- Comment #2 from Tammes Burghard  ---
This seems to be fixed now and I believe it was a qt 6.7 beta issue and fixed
upstream

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 480364] New: Plasmashell crash in touch mode and desktop grid

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=480364

Bug ID: 480364
   Summary: Plasmashell crash in touch mode and desktop grid
Classification: Plasma
   Product: plasmashell
   Version: 5.92.0
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: k...@kuchenmampfer.de
  Target Milestone: 1.0

Application: plasmashell (5.92.0)

Qt Version: 6.7.0
Frameworks Version: 5.248.0
Operating System: Linux 6.7.1-arch1-1 x86_64
Windowing System: Wayland
Distribution: Arch Linux
DrKonqi: 5.92.0 [CoredumpBackend]

-- Information about the crash:
Steps to reproduce:

1. Have Plasma 6.0 RC1 under arch linux on a tablet (Mine is the MS Surface Go
2)
2. Have multiple Workspaces (I have 1x4) and be in the first
3. Detach keyboard to enter touch mode
4. Three-finger-swipe down once or three-finger-swipe up twice to enter the
desktop grid view
5. Tap on the second workspace to enter it
6. Wait a bit

What happens:
5. The workspace indicator in the panel says that I am still in workspace 1
even though I am in WS2 (proven by the ability to three-finger-swipe to the
right and switch to WS1)
6. Plasmashell crashes

What should have happened:
5. The workspace indicator correctly reports being in WS2
6. No crash

The crash can be reproduced every time.

-- Backtrace:
Application: plasmashell (plasmashell), signal: Segmentation fault


This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[New LWP 1679]
[New LWP 1759]
[New LWP 1698]
[New LWP 1793]
[New LWP 1700]
[New LWP 1799]
[New LWP 1760]
[New LWP 1776]
[New LWP 2098]
[New LWP 1691]
[New LWP 1784]
[New LWP 1711]
[New LWP 1758]
[New LWP 1697]
[New LWP 1750]
[New LWP 1794]
[New LWP 1699]
[New LWP 1686]
[New LWP 1796]
[New LWP 1687]
[New LWP 1692]
[New LWP 1757]
[New LWP 1761]
[New LWP 1777]
[New LWP 1787]
[New LWP 1795]
[New LWP 1797]
[New LWP 2095]
[New LWP 2097]
[New LWP 2096]
[New LWP 1688]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `/usr/bin/plasmashell --no-respawn'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x789e1b8ac83c in ?? () from /usr/lib/libc.so.6
[Current thread is 1 (Thread 0x789e1648a9c0 (LWP 1679))]
Cannot QML trace cores :(
[Current thread is 1 (Thread 0x789e1648a9c0 (LWP 1679))]

Thread 31 (Thread 0x789e0fe006c0 (LWP 1688)):
#0  0x789e1b920f6f in poll () at /usr/lib/libc.so.6
#1  0x789e1d37da68 in ??? () at /usr/lib/libQt6WaylandClient.so.6
#2  0x789e1b4d4ae3 in ??? () at /usr/lib/libQt6Core.so.6
#3  0x789e1b8aa9eb in ??? () at /usr/lib/libc.so.6
#4  0x789e1b92e7cc in ??? () at /usr/lib/libc.so.6

Thread 30 (Thread 0x789de6a006c0 (LWP 2096)):
#0  0x789e1b8a74ae in ??? () at /usr/lib/libc.so.6
#1  0x789e1b8aa055 in pthread_cond_timedwait () at /usr/lib/libc.so.6
#2  0x789e1b4e2234 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt6Core.so.6
#3  0x789e1b4d9b52 in ??? () at /usr/lib/libQt6Core.so.6
#4  0x789e1b4d4ae3 in ??? () at /usr/lib/libQt6Core.so.6
#5  0x789e1b8aa9eb in ??? () at /usr/lib/libc.so.6
#6  0x789e1b92e7cc in ??? () at /usr/lib/libc.so.6

Thread 29 (Thread 0x789df7a006c0 (LWP 2097)):
#0  0x789e1b8a74ae in ??? () at /usr/lib/libc.so.6
#1  0x789e1b8aa055 in pthread_cond_timedwait () at /usr/lib/libc.so.6
#2  0x789e1b4e2234 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt6Core.so.6
#3  0x789e1b4d9b52 in ??? () at /usr/lib/libQt6Core.so.6
#4  0x789e1b4d4ae3 in ??? () at /usr/lib/libQt6Core.so.6
#5  0x789e1b8aa9eb in ??? () at /usr/lib/libc.so.6
#6  0x789e1b92e7cc in ??? () at /usr/lib/libc.so.6

Thread 28 (Thread 0x789de60006c0 (LWP 2095)):
#0  0x789e1b8a74ae in ??? () at /usr/lib/libc.so.6
#1  0x789e1b8aa055 in pthread_cond_timedwait () at /usr/lib/libc.so.6
#2  0x789e1b4e2234 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt6Core.so.6
#3  0x789e1b4d9b52 in ??? () at /usr/lib/libQt6Core.so.6
#4  0x789e1b4d4ae3 in ??? () at /usr/lib/libQt6Core.so.6
#5  0x789e1b8aa9eb in ??? () at /usr/lib/libc.so.6
#6  0x789e1b92e7cc in ??? () at /usr/lib/libc.so.6

Thread 27 (Thread 0x789da74006c0 (LWP 1797)):
#0  0x789e1b8a74ae in ??? () at /usr/lib/libc.so.6
#1  0x789e1b8a9d40 in pthread_cond_wait () at /usr/lib/libc.so.6
#2  0x789e0d3139dc in ??? () at /usr/lib/dri/iris_dri.so
#3  0x789e0d30ad1c in ??? () at /usr/lib/dri/iris_dri.so
#4  0x789e1b8aa9eb in ??? () at /usr/lib/libc.so.6
#5  

[plasmashell] [Bug 478259] app icons become tiny in tablet mode with unmaximized info center or okular window

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=478259

--- Comment #8 from Tammes Burghard  ---
I now set the panel to always be visible and noticed that the issue seems to
only appear when entering touch mode. Once again the steps that I did:

1. Plasma 6 RC1 with 100% scaling, breeze dark global theme, floating always
visible panel with adaptive transparency, centered and set to span width
2. Open Okular or system settings (floating or maximized makes no difference)
3. Rotate the tablet to be vertical
4. lie the tablet down flat on the table

What happens:

3. Plasma automatically enters touch mode (after a brief delay). This causes
the app icons to become tiny in case of system settings being opened and
disappear entirely when okular is opened
4. The orientation remains vertical, but if the keyboard is attached, the touch
mode gets disabled and icons go back to how they are supposed to be sized.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 478259] app icons become tiny in tablet mode with unmaximized info center or okular window

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=478259

Tammes Burghard  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Resolution|WORKSFORME  |---
 Status|RESOLVED|REOPENED

--- Comment #7 from Tammes Burghard  ---
The issue now also appears without touch mode.

And with okular, I get result 6. at step 6. with 100% scaling, breeze dark
theme and panel in dodge window mode.
Whereas with system settings, I get result 5. at step 6. with the same
settings.

Is there any easy way to reset all the panel settings to default as you
requested other than reinstalling?

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 478259] app icons become tiny in tablet mode with unmaximized info center or okular window

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=478259

--- Comment #6 from Tammes Burghard  ---
Alright, with 100% scaling, I can not reproduce 5. anymore, but 6. is still an
issue.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Alligator] [Bug 479190] content can be scrolled out of its page

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=479190

--- Comment #1 from Tammes Burghard  ---
A video of this can be found at https://kuchenmampfer.de/kde_bug_479190.mp4

-- 
You are receiving this mail because:
You are watching all bug changes.

[Alligator] [Bug 479190] New: content can be scrolled out of its page

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=479190

Bug ID: 479190
   Summary: content can be scrolled out of its page
Classification: Applications
   Product: Alligator
   Version: 24.01.85
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: fe...@posteo.de
  Reporter: k...@kuchenmampfer.de
  Target Milestone: ---

SUMMARY
***
When I scroll the content of a feed entry (which is contained in a
ScrollablePage) sideways, it leaves the page and goes over the list of feed
entries.
***


STEPS TO REPRODUCE
1. open a post
2. scroll sideways

OBSERVED RESULT
content leaves its page

EXPECTED RESULT
nothing happens

SOFTWARE/OS VERSIONS
Linux: Arch Linux
KDE Plasma Version: Plasma 6 beta 2
KDE Frameworks Version: 5.247.0
Qt Version: 6.7

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 479030] Scrollview on start and update page goes under the page title bar

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=479030

--- Comment #1 from Tammes Burghard  ---
U put a screen recording of this at https://kuchenmampfer.de/kde_bug_479030.mp4

-- 
You are receiving this mail because:
You are watching all bug changes.

[kinfocenter] [Bug 479031] New: about system page: error with loading the qml file

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=479031

Bug ID: 479031
   Summary: about system page: error with loading the qml file
Classification: Applications
   Product: kinfocenter
   Version: 5.91.0
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: k...@kuchenmampfer.de
CC: sit...@kde.org
  Target Milestone: ---

Created attachment 164450
  --> https://bugs.kde.org/attachment.cgi?id=164450=edit
window showing the error

SUMMARY
***
Instead of giving me details on my system, the about system page shows the
following error(s):

qrc:/kcm/kcm_about-distro/main.qml:15 Type KCM.SimpleKCM unavailable
qrc:/qt/qml/org/kde/kcmutils/SimpleKCM.qml:33 Type Kirigami.ScrollablePage
unavailable
file:///usr/lib/qt6/qml/org/kde/kirigami/ScrollablePage.qml:68 Type
Kirigami.Page unavailable
file:///usr/lib/qt6/qml/org/kde/kirigami/Page.qml:237 Type Kirigami.PageRow
unavailable
file:///usr/lib/qt6/qml/org/kde/kirigami/PageRow.qml:180 Type OverlayDrawer
unavailable
file:///usr/lib/qt6/qml/org/kde/kirigami/OverlayDrawer.qml:22 Type
KT.OverlayDrawer unavailable
file:///usr/lib/qt6/qml/org/kde/kirigami/templates/OverlayDrawer.qml:120 Cannot
assign object of type "KTP.IconPropertiesGroup" to property of type
"IconPropertiesGroup_QMLTYPE_60*" as the former is neither the same as the
latter nor a sub-class of it.
***


STEPS TO REPRODUCE
1. open the info center

OBSERVED RESULT
error with loading the qml file

EXPECTED RESULT
info is shown

SOFTWARE/OS VERSIONS
Linux: Arch Linux
KDE Plasma Version: 5.91.0
KDE Frameworks Version: 5.247.0
Qt Version: 6.7.0

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 479030] New: Scrollview on start and update page goes under the page title bar

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=479030

Bug ID: 479030
   Summary: Scrollview on start and update page goes under the
page title bar
Classification: Applications
   Product: Discover
   Version: 5.91.0
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: discover
  Assignee: plasma-b...@kde.org
  Reporter: k...@kuchenmampfer.de
CC: aleix...@kde.org
  Target Milestone: ---

SUMMARY
***
The start page and the update page go below the title bar which makes the
header (or first entry) unviewable.
***


STEPS TO REPRODUCE
1. Open discover on the start page
2. Try to scroll up and read the header of he first section

OBSERVED RESULT
Only a glimpse of the first sections header becomes visible and the scroll bar
handle goes under the title bar

EXPECTED RESULT
The section header gets fully visible and the scroll bar handle only reaches
the title bar

SOFTWARE/OS VERSIONS
Linux: Arch Linux
KDE Plasma Version: 5.91.0
KDE Frameworks Version: 5.247.0
Qt Version: 6.7.0

-- 
You are receiving this mail because:
You are watching all bug changes.

[kdeconnect] [Bug 478262] New: Remote input uses keyboard layout of target system

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=478262

Bug ID: 478262
   Summary: Remote input uses keyboard layout of target system
Classification: Applications
   Product: kdeconnect
   Version: 24.01.80
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: common
  Assignee: albertv...@gmail.com
  Reporter: k...@kuchenmampfer.de
CC: andrew.g.r.hol...@gmail.com
  Target Milestone: ---

SUMMARY
***
This might be a duplicate of https://bugs.kde.org/show_bug.cgi?id=405111, but I
am not sure about that and do have more detail, so I will put this into a new
bug report.

I just tried remote input from my arch linux plasma 6 euro layout laptop to my
arch linux plasma 6 de layout tablet and instead of the symbols I typed being
inserted, I got the de layout symbols of the keys I typed on my euro layout. So
for example "y[:/" became "züÖ-".
Additionally, I was not able to use the "Alt Gr" key, so I needed to copy and
paste the @ symbol.
***


STEPS TO REPRODUCE
1. Have kdeconnect on two plasma 6 machines with different keyboard layouts
2. use remote input from one of them to the other

OBSERVED RESULT
The keyboard layout of the target system gets used without the ability to use
"Alt Gr"

EXPECTED RESULT
The keyboard layout of the input system gets used

SOFTWARE/OS VERSIONS
Input:
Operating System: Crystal Linux 
KDE Plasma Version: 5.90.0
KDE Frameworks Version: 5.246.0
Qt Version: 6.6.1
Kernel Version: 6.6.4-arch1-1 (64-bit)
Graphics Platform: Wayland
Keyboard layout: eu EurKey (US)

Target:
Operating System: Arch Linux
KDE Plasma Version: 5.90.0
KDE Frameworks Version: 5.246.0
Qt Version: 6.6.1
Kernel Version: 6.6.3-arch1-1 (64-bit)
Graphics Platform: Wayland
Keyboard layout: de Deutsch

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kirigami] [Bug 475117] Kasts built against qt6 version: various errors, menu and dialog glitches

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=475117

--- Comment #7 from Tammes Burghard  ---
Update, now on Plasma 6 Beta:

1. The "show episode info" dialog looks fine, but is unscrollable and
everything that does not fit into the dialog can not be seen
2. The "chapters" dialog is still incredibly slow to open and induces heavy
load on the cpu, the same thing happens when I click on the top banner to open
episode details
3. The "more actions" menu popup on the "subscriptions" page now changes its
height when the mouse moves in the window
4. The `customizeRatesDialog` now works fine
5. That same dialog can still neither be moved nor resized, but that is already
an issue in the current release
6. When using touchpad scroll to increase the volume to 100%, lifting the
fingers from the touchpad resets the volume to 90%. This still happens.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 478259] app icons become tiny in tablet mode with unmaximized info center or okular window

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=478259

--- Comment #2 from Tammes Burghard  ---
It might also be relevant that I use 150% fractional scaling

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 478259] app icons become tiny in tablet mode with unmaximized info center or okular window

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=478259

--- Comment #1 from Tammes Burghard  ---
Created attachment 164007
  --> https://bugs.kde.org/attachment.cgi?id=164007=edit
Nonexistant app icons in vertical mode

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 478259] New: app icons become tiny in tablet mode with unmaximized info center or okular window

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=478259

Bug ID: 478259
   Summary: app icons become tiny in tablet mode with unmaximized
info center or okular window
Classification: Plasma
   Product: plasmashell
   Version: 5.90.0
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: k...@kuchenmampfer.de
CC: niccolo.venera...@gmail.com
  Target Milestone: 1.0

Created attachment 164006
  --> https://bugs.kde.org/attachment.cgi?id=164006=edit
tiny app icons horizontal

SUMMARY
***
See Screenshot, but ignore the wallpaper bug (that I don't know yet how to
consistently reproduce)
***


STEPS TO REPRODUCE
1. Have Plasma 6 on a tablet
2. Detach keyboard to enter tablet mode
3. Set the panel to 'dodge windows'
4. Open the info center or Okular (does not happen with some other apps like
dolphin)
5. Unmaximize the window and move it so that the panel appears
6. Rotate the screen to be vertical

OBSERVED RESULT
5. app icons in the panel become tiny (see screenshot)
6. app icons entirely disappear and the blue marker of which window is active
is only a vertical bar of a few pixels width

EXPECTED RESULT
App icons remain in their size and if there is not enough space (as seen in
vertical orientation), all elements (spacings) are evenly scaled down, not only
app icons.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.90.0
KDE Frameworks Version: 5.246.0
Qt Version: 6.6.1
Kernel Version: 6.6.3-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Pentium® CPU 4425Y @ 1.70GHz
Memory: 7.6 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 615
Manufacturer: Microsoft Corporation
Product Name: Surface Go 2
System Version: 1

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 478256] Panel in dodge window mode appears in front of window when screen is rotated or keyboard gets detached

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=478256

--- Comment #2 from Tammes Burghard  ---
The observed result 6. varies. I now have enabled automatic rotaion even if not
in tablet mode and now the panel (mostly) first disappears and then appears
after a second or so.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 478256] Panel in dodge window mode appears in front of window when screen is rotated or keyboard gets detached

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=478256

--- Comment #1 from Tammes Burghard  ---
The same thing happens in auto hide mode, except now it does not ever require a
full screen window.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 478256] New: Panel in dodge window mode appears in front of window when screen is rotated or keyboard gets detached

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=478256

Bug ID: 478256
   Summary: Panel in dodge window mode appears in front of window
when screen is rotated or keyboard gets detached
Classification: Plasma
   Product: plasmashell
   Version: 5.90.0
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: k...@kuchenmampfer.de
CC: niccolo.venera...@gmail.com
  Target Milestone: 1.0

SUMMARY
***
When I open an application in fullscreen on my tablet with the panel in dodge
window mode, it nicely dodges the window. But when I then rotate the screen,
the panel reappears in front of the window.
***


STEPS TO REPRODUCE
1. Set panel to dodge window mode
2. open e.g. Dolphin in fullscreen
3. detach keyboard
4. switch to empty workspace (via three finger swipe)
5. come back to previous workspace (via three finger swipe)
6. rotate vertically
7. rotate horizontally

OBSERVED RESULT
3. panel appears in front of dolphin
4. panel stays as it is
5. panel disappears/dodges window
6. panel appears but disappears after a second or so
7. panel appears in front of window and remains there

EXPECTED RESULT
3. nothing happens
4. panel appears as it was not visible before
5. panel disappears/dodges window
6. screen gets rotated, panel is not shown
7. screen gets rotated, panel is not shown

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.90.0
KDE Frameworks Version: 5.246.0
Qt Version: 6.6.1
Kernel Version: 6.6.3-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Pentium® CPU 4425Y @ 1.70GHz
Memory: 7.6 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 615
Manufacturer: Microsoft Corporation
Product Name: Surface Go 2
System Version: 1

-- 
You are receiving this mail because:
You are watching all bug changes.

[Discover] [Bug 478253] New: Finished updates disappear, but still occupy space

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=478253

Bug ID: 478253
   Summary: Finished updates disappear, but still occupy space
Classification: Applications
   Product: Discover
   Version: 5.90.0
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Updates (interactive)
  Assignee: plasma-b...@kde.org
  Reporter: k...@kuchenmampfer.de
CC: aleix...@kde.org
  Target Milestone: ---

Created attachment 164002
  --> https://bugs.kde.org/attachment.cgi?id=164002=edit
Screenshot of a bunch of black spaces in the updates list

SUMMARY
***
When I am updating flatpak applications (but I think also other packages),
packages that are finished updating disappear from the updates list, but don't
free their space so that I end up with a wall of blank space above the last
remaining updates in the end.
***


STEPS TO REPRODUCE
1. have a bunch of updates to do
2. go to the updates page
3. click 'update all'
4. wait

OBSERVED RESULT
packages that finished updating get replaced by blank space

EXPECTED RESULT
packages that are finished updating either stay in the list and are marked as
finished or are removed from the list and the other packages can take their
spaceinfo

SOFTWARE/OS VERSIONS
Operating System: Crystal Linux 
KDE Plasma Version: 5.90.0
KDE Frameworks Version: 5.246.0
Qt Version: 6.6.1
Kernel Version: 6.6.4-arch1-1 (64-bit)
Graphics Platform: Wayland

-- 
You are receiving this mail because:
You are watching all bug changes.

[Alligator] [Bug 478078] In some posts, images start to flicker when made too big

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=478078

Tammes Burghard  changed:

   What|Removed |Added

   Keywords||qt6

-- 
You are receiving this mail because:
You are watching all bug changes.

[Alligator] [Bug 478077] Choosing an individual feed shows posts of all feeds until refreshing

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=478077

--- Comment #1 from Tammes Burghard  ---
I just noticed, if the feed has a limited amount of posts in it, the number of
posts in the post list does get limited to that amount.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Alligator] [Bug 478078] In some posts, images start to flicker when made too big

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=478078

Tammes Burghard  changed:

   What|Removed |Added

 Attachment #163864|0   |1
is obsolete||

--- Comment #2 from Tammes Burghard  ---
Created attachment 163865
  --> https://bugs.kde.org/attachment.cgi?id=163865=edit
Another video of it

Here, you can see a bit more flickering in the beginning, but let me tell you,
it actually flickers more than visible here.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Alligator] [Bug 478078] In some posts, images start to flicker when made too big

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=478078

--- Comment #1 from Tammes Burghard  ---
What, the flickering is not visible in the recording, there the image just
disappears.
Wild

-- 
You are receiving this mail because:
You are watching all bug changes.

[Alligator] [Bug 478078] New: In some posts, images start to flicker when made too big

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=478078

Bug ID: 478078
   Summary: In some posts, images start to flicker when made too
big
Classification: Applications
   Product: Alligator
   Version: 24.01.80
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: fe...@posteo.de
  Reporter: k...@kuchenmampfer.de
  Target Milestone: ---

Created attachment 163864
  --> https://bugs.kde.org/attachment.cgi?id=163864=edit
Video of the flickering image

SUMMARY
***
In some posts, images flicker in front of the text when I resize the window to
a too big size.
There are window sizes where the flickering stops after a few blinks within the
flickering range.
***


STEPS TO REPRODUCE
1. Add this feed "https://events.ccc.de/feed;
2. Go to this post "Einladung zum Junghacker:innentag auf dem 37C3"
3. Play around with the size of the window

OBSERVED RESULT
The big red image starts to flicker at a certain window size. For some sizes,
the flickering eventually stops, for others, it keeps flickering.

EXPECTED RESULT
The image is stable for all window sizes

SOFTWARE/OS VERSIONS
Operating System: Crystal Linux 
KDE Plasma Version: 5.90.0
KDE Frameworks Version: 5.246.0
Qt Version: 6.6.1
Kernel Version: 6.6.3-arch1-1 (64-bit)
Graphics Platform: Wayland

-- 
You are receiving this mail because:
You are watching all bug changes.

[Alligator] [Bug 478077] New: Choosing an individual feed shows posts of all feeds until refreshing

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=478077

Bug ID: 478077
   Summary: Choosing an individual feed shows posts of all feeds
until refreshing
Classification: Applications
   Product: Alligator
   Version: 24.01.80
  Platform: Arch Linux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: fe...@posteo.de
  Reporter: k...@kuchenmampfer.de
  Target Milestone: ---

SUMMARY
***
When I choose an individual feed in the list on the left side, I get posts from
all my feeds in the post list.
Only after refreshing, posts get filtered.
***


STEPS TO REPRODUCE
1. Subscribe to multiple feeds
2. Select one of them in the list on the left

OBSERVED RESULT
Post list contains posts from all the feeds until I refresh

EXPECTED RESULT
Posts get filtered so that I only see posts of that specific feed immediately

SOFTWARE/OS VERSIONS
Operating System: Crystal Linux 
KDE Plasma Version: 5.90.0
KDE Frameworks Version: 5.246.0
Qt Version: 6.6.1
Kernel Version: 6.6.3-arch1-1 (64-bit)
Graphics Platform: Wayland

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 477826] Flickering dark box in translucent panel in front of workspace gap

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=477826

--- Comment #5 from Tammes Burghard  ---
The bug also happens when switching workspaces horizontally, but there it looks
more like a flickering because the dark area is taller than the panel.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 477826] Flickering dark box in translucent panel in front of workspace gap

[Tammes Burghard]

https://bugs.kde.org/show_bug.cgi?id=477826

Tammes Burghard  changed:

   What|Removed |Added

 Status|NEEDSINFO   |REPORTED
 Resolution|WAITINGFORINFO  |---

--- Comment #4 from Tammes Burghard  ---
Of course I can.
I just added a screenshot of my panel settings and uploaded a whole screen
recording to https://kuchenmampfer.de/kde_bug_477826.mp4.
On that, I pointed my mouse on the dark area to make it easier to find.
I didn't have a window open on any of my nine two-monitor workspaces (arranged
as a 3x3 grid).
The panel is on the bottom edge of the upper monitor.
My global theme is Breeze Dark, colors are Material You Dark generated from my
wallpaper, the rest of the relevant visual stuff is breeze.
I do the workspace switching via touchpad gesture and the mouse pointing via my
external mouse.
And the plasmoids on my desktop are various configurations of the system
monitor plasmoid and modernclock, which I ported to plasma 6 today.
But I guess that is not really relevant xD

-- 
You are receiving this mail because:
You are watching all bug changes.