[kwin] [Bug 373043] New: Kwin crashing everytime I start chromium

[Christian]

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

Bug ID: 373043
   Summary: Kwin crashing everytime I start chromium
   Product: kwin
   Version: 5.8.4
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: christian_bur...@yahoo.com
  Target Milestone: ---

Application: kwin_x11 (5.8.4)
 (Compiled from sources)
Qt Version: 5.6.2
Frameworks Version: 5.28.0
Operating System: Linux 4.8.0 x86_64
Distribution (Platform): Gentoo Packages

-- Information about the crash:
- What I was doing when the application crashed:
Started konsole and dolphin as root, chromium as normal user.

- Unusual behavior I noticed:
Kwin crashes always.

- Custom settings of the application:
explained above, nothing much other then running as root konsole and dolphin.
I'm using gentoo, which means everything is compiled locally.
I can't run opengl nvidia libraries, they won't allow running  plasma 5, so
here follows the configuration for these libraries:
# eselect opencl list
Available OpenCL implementations:
  [1]   mesa *
  [2]   nvidia
# eselect opengl list
Available OpenGL implementations:
  [1]   nvidia
  [2]   xorg-x11 *

The crash can be reproduced every time.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f79dbf7b880 (LWP 778))]

Thread 14 (Thread 0x7f79b5cd9700 (LWP 994)):
#0  0x7f79dba9e33b in clock_gettime () from /lib64/libc.so.6
#1  0x7f79d98755f3 in ?? () from /usr/lib64/libQt5Core.so.5
#2  0x7f79d99c4e89 in QTimerInfoList::updateCurrentTime() () from
/usr/lib64/libQt5Core.so.5
#3  0x7f79d99c436b in
QEventDispatcherUNIXPrivate::doSelect(QFlags,
timespec*) () from /usr/lib64/libQt5Core.so.5
#4  0x7f79d99c491a in
QEventDispatcherUNIX::processEvents(QFlags) ()
from /usr/lib64/libQt5Core.so.5
#5  0x7f79d9976182 in
QEventLoop::exec(QFlags) () from
/usr/lib64/libQt5Core.so.5
#6  0x7f79d97d381e in QThread::exec() () from /usr/lib64/libQt5Core.so.5
#7  0x7f79d46bf805 in ?? () from /usr/lib64/libQt5Qml.so.5
#8  0x7f79d97d7eaf in ?? () from /usr/lib64/libQt5Core.so.5
#9  0x7f79d57893c6 in start_thread () from /lib64/libpthread.so.0
#10 0x7f79dba9161d in clone () from /lib64/libc.so.6

Thread 13 (Thread 0x7f7918ec2700 (LWP 961)):
#0  0x7f79d578ef3f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f7925549043 in ?? () from /usr/lib64/dri/swrast_dri.so
#2  0x7f7925548e7f in ?? () from /usr/lib64/dri/swrast_dri.so
#3  0x7f79d57893c6 in start_thread () from /lib64/libpthread.so.0
#4  0x7f79dba9161d in clone () from /lib64/libc.so.6

Thread 12 (Thread 0x7f79196c3700 (LWP 960)):
#0  0x7f79d578ef3f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f7925549043 in ?? () from /usr/lib64/dri/swrast_dri.so
#2  0x7f7925548e7f in ?? () from /usr/lib64/dri/swrast_dri.so
#3  0x7f79d57893c6 in start_thread () from /lib64/libpthread.so.0
#4  0x7f79dba9161d in clone () from /lib64/libc.so.6

Thread 11 (Thread 0x7f7919ec4700 (LWP 959)):
#0  0x7f79d578ef3f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f7925549043 in ?? () from /usr/lib64/dri/swrast_dri.so
#2  0x7f7925548e7f in ?? () from /usr/lib64/dri/swrast_dri.so
#3  0x7f79d57893c6 in start_thread () from /lib64/libpthread.so.0
#4  0x7f79dba9161d in clone () from /lib64/libc.so.6

Thread 10 (Thread 0x7f791a6c5700 (LWP 958)):
#0  0x7f79d578ef3f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f7925549043 in ?? () from /usr/lib64/dri/swrast_dri.so
#2  0x7f7925548e7f in ?? () from /usr/lib64/dri/swrast_dri.so
#3  0x7f79d57893c6 in start_thread () from /lib64/libpthread.so.0
#4  0x7f79dba9161d in clone () from /lib64/libc.so.6

Thread 9 (Thread 0x7f791aec6700 (LWP 957)):
#0  0x7f79d578ef3f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f7925549043 in ?? () from /usr/lib64/dri/swrast_dri.so
#2  0x7f7925548e7f in ?? () from /usr/lib64/dri/swrast_dri.so
#3  0x7f79d57893c6 in start_thread () from /lib64/libpthread.so.0
#4  0x7f79dba9161d in clone () from /lib64/libc.so.6

Thread 8 (Thread 0x7f791b6c7700 (LWP 956)):
#0  0x7f79d578ef3f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f7925549043 in ?? () from /usr/lib64/dri/swrast_dri.so
#2  0x7f7925548e7f in ?? () from /usr/lib64/dri/swrast_dri.so
#3  0x7f79d57893c6 in start_thread () from /lib64/libpthread.so.0
#4  0x7f79dba9161d in clone () from /lib64/libc.so.6

Thread 7 (Thread 0x7f791bec8700 (LWP 955)):
#0  0x7f79d578ef3f in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib64/libpthread.so.0
#1  0x7f

[kwin] [Bug 449846] New: Missing features for replacing present windows

[Christian]

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

Bug ID: 449846
   Summary: Missing features for replacing present windows
   Product: kwin
   Version: 5.24.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: task
  Priority: NOR
 Component: effects-overview
  Assignee: kwin-bugs-n...@kde.org
  Reporter: k...@fuchsnet.ch
  Target Milestone: ---

As per discussion in the VDG, currently missing features in the overview effect
to be able to replace the other effect(s): 

-- needed before replacement

* Show only windows of a specific desktop
* Show only windows of a specific application

(With keybindings each) 

These are needed because e.g. task manager has an option to use the effect in
which the windows of a grouped application are shown 

* Possibility to set a flag to disable the virtual desktop bar on top

needed for the above, mostly, since it doesn't make sense to have a desktop bar
in this situation 

--- would be good before replacement

* Possibility to configure mouse buttons and their effects, mainly for pulling
a window to the current workspace, but also for people who want to disable
closing 

* show the window previews of the windows matching the filter you just entered
in the text field 


Present windows also has some other options, e.g. ignoring minimized windows
and a more fine grained configurability of placement and presentation, not sure
if / how often these are used. The above are more functionality than aesthetics
and I think at least some of them are a must have before present windows can be
replaced.

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

[systemsettings] [Bug 449853] New: Systemsettings 5.24 crashes when switching from icon view to sidebar view

[Christian]

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

Bug ID: 449853
   Summary: Systemsettings 5.24 crashes when switching from icon
view to sidebar view
   Product: systemsettings
   Version: 5.24.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: k...@fuchsnet.ch
  Target Milestone: ---

Application: systemsettings (5.24.0)

Qt Version: 5.15.2
Frameworks Version: 5.90.0
Operating System: Linux 5.16.5-200.fc35.x86_64 x86_64
Windowing System: X11
Distribution: Fedora Linux 35 (KDE Plasma)
DrKonqi: 5.24.0 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:

Switching from icon view to sidebar view via the button in the toolbar. 

This is 100% reproducible, see attached backtrace.

Happens since the update to 5.24

The crash can be reproduced every time.

-- Backtrace:
Application: Systemeinstellungen (systemsettings), signal: Segmentation fault

[KCrash Handler]
#4  0x7f333cdc2738 in QAbstractAnimation::stop() () from
/lib64/libQt5Core.so.5
#5  0x7f333cdc785b in QPropertyAnimation::~QPropertyAnimation() () from
/lib64/libQt5Core.so.5
#6  0x7f3329850c37 in Breeze::Animation::~Animation() () from
/usr/lib64/qt5/plugins/styles/breeze.so
#7  0x7f333cfc07ca in QObjectPrivate::deleteChildren() () from
/lib64/libQt5Core.so.5
#8  0x7f333cfc80cc in QObject::~QObject() () from /lib64/libQt5Core.so.5
#9  0x7f3329846f01 in Breeze::WidgetStateData::~WidgetStateData() () from
/usr/lib64/qt5/plugins/styles/breeze.so
#10 0x7f333cfc1d71 in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#11 0x7f333db71443 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#12 0x7f333cf977d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#13 0x7f333cf9ad46 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#14 0x7f333cfe9117 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5Core.so.5
#15 0x7f333aca805f in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#16 0x7f333acfd2a8 in g_main_context_iterate.constprop () from
/lib64/libglib-2.0.so.0
#17 0x7f333aca5853 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#18 0x7f333cfe8bb8 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#19 0x7f333cf961e2 in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#20 0x7f333cf9e724 in QCoreApplication::exec() () from
/lib64/libQt5Core.so.5
#21 0x559bc2e0e1e1 in main ()
[Inferior 1 (process 21830) detached]

Possible duplicates by query: bug 374941.

Reported using DrKonqi

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

[kwin] [Bug 450777] New: (un)shading broken, window has a way too small size after unshading

[Christian]

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

Bug ID: 450777
   Summary: (un)shading broken, window has a way too small size
after unshading
   Product: kwin
   Version: 5.24.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: k...@fuchsnet.ch
  Target Milestone: ---

Created attachment 147087
  --> https://bugs.kde.org/attachment.cgi?id=147087&action=edit
videocap of the issue

STEPS TO REPRODUCE
1.  Open a Window
2.  Shade it  ("roll it up")
3.  Unshade it ("unroll it")

OBSERVED RESULT
Window is way to small, first manual resize makes it jump quite a bit in size

EXPECTED RESULT
Window has the same size as it did before shading

Operating System: Fedora Linux 35
KDE Plasma Version: 5.24.2
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.2
Kernel Version: 5.16.9-200.fc35.x86_64 (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3070/PCIe/SSE2

ADDITIONAL INFORMATION
Reproducable on different machines with different GPUs / drivers, including an
Intel laptop and an nvidia desktop. See attached video for an example with
konsole.

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

[lattedock] [Bug 454544] New: Latte dock is blurred when changing global scale in Wayland

[Christian]

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

Bug ID: 454544
   Summary: Latte dock is blurred when changing global scale in
Wayland
   Product: lattedock
   Version: 0.10.8
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: application
  Assignee: mvourla...@gmail.com
  Reporter: christian.tall...@gmx.de
  Target Milestone: ---

SUMMARY
After changing the global scale in Wayland latte-dock is blurred panels are
blurred (x-wayland ?).

STEPS TO REPRODUCE
1. Start a Plasma Wayland session and start Latte Dock.
2. Change the global scale to 125 % under display settings.
3. Inspect the latte-dock panels.

OBSERVED RESULT
Latte Dock panels are blurred.

EXPECTED RESULT
Latte Dock panels should be as sharp as other applications.

SOFTWARE/OS VERSIONS 
Linux/KDE Plasma:  Kubuntu 22.04
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3

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

[lattedock] [Bug 454544] Latte dock is blurred when changing global scale in Wayland

[Christian]

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

Christian  changed:

   What|Removed |Added

 CC||christian.tall...@gmx.de

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

[kwin] [Bug 450582] Some change between 5.24.0 and 5.24.1 broke windows shade/shutter feature

[Christian]

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

--- Comment #14 from Christian (Fuchs)  ---
It would be really nice if we could get that revert into a release, unless that
breaks other things. Because right now as is, shade is still broken in both
released versions, the upcoming 5.25 release and on main.

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

[kwin] [Bug 455332] New: Regressions in present windows effect compared to pre-5.25

[Christian]

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

Bug ID: 455332
   Summary: Regressions in present windows effect compared to
pre-5.25
   Product: kwin
   Version: 5.25.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: effects-present-windows
  Assignee: kwin-bugs-n...@kde.org
  Reporter: k...@fuchsnet.ch
  Target Milestone: ---

The following list are regressions of the present window effect rewritten in
QML over the 5.24 one: 

Functional regressions:
- Mouse buttons can't be configured, e.g. to pull a window to the current
workspace
- filtering does only filter windows of the current screen instead of all
screens, which is extra critical since the effect is used to show multiple
windows of the grouped app if you click it in the taskbar, you then can't
properly filter
- filtering isn't re-enabled on typing when you choose windows via keyboard nav
(input field loses focus and doesn't regain it)
- close buttons can't be disabled by config

Visual regressions:
- Panel can't be configured to be shown
- blur can't be disabled (oddly enough it can be in the other effect?)


I consider the functional ones of high criticality, especially the broken
filtering. The rest is more of a "nice to have"

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

[plasmashell] [Bug 455334] New: Regression in 5.25: Window previews no longer shown on task hover

[Christian]

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

Bug ID: 455334
   Summary: Regression in 5.25: Window previews no longer shown on
task hover
   Product: plasmashell
   Version: 5.25.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: grave
  Priority: NOR
 Component: Task Manager and Icons-Only Task Manager
  Assignee: plasma-b...@kde.org
  Reporter: k...@fuchsnet.ch
  Target Milestone: 1.0

Created attachment 149746
  --> https://bugs.kde.org/attachment.cgi?id=149746&action=edit
screenshot of the issue

SUMMARY
Since updating to 5.25, I no longer get preview thumbnails when hovering tasks
in the task manager, only the application icon.

STEPS TO REPRODUCE
1. Have taskmanager
2. Open a window, e.g. dolphin
3. Hover task

OBSERVED RESULT
No thumbnail

EXPECTED RESULT
Thumbnail

Previews do work everywhere else, including the present window effect or the
show thumbnail effect, only broken in task manager.

Operating System: Fedora Linux 36
KDE Plasma Version: 5.25.0
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.3
Kernel Version: 5.17.13-300.fc36.x86_64 (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 31.2 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3070/PCIe/SSE2

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

[kwin] [Bug 455338] New: Regression in desktop grid effect since pre-5.25

[Christian]

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

Bug ID: 455338
   Summary: Regression in desktop grid effect since pre-5.25
   Product: kwin
   Version: 5.25.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: effects-desktop-grid
  Assignee: kwin-bugs-n...@kde.org
  Reporter: k...@fuchsnet.ch
  Target Milestone: ---

The following regressions are new in the rewritten desktop grid effect in 5.25

 - There is no visual indicator of which virtual desktop is currently chosen if
you switch them via keyboard (or mouse), other than the focussed window in it
being slightly highlighted. The desktop itself should be highlighted.

- There is no way to completely deactive the present window effect, the only
options are "closest" and "natural", there should be "none" which does only
trigger desktop grid, and not also present windows

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

[plasma-nm] [Bug 455340] New: QR Code functionality shown for wired dhcp network, but does nothing

[Christian]

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

Bug ID: 455340
   Summary: QR Code functionality shown for wired dhcp network,
but does nothing
   Product: plasma-nm
   Version: 5.25.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: applet
  Assignee: jgrul...@redhat.com
  Reporter: k...@fuchsnet.ch
  Target Milestone: ---

SUMMARY

There is a new functionality to show a QR code of a network, however, this
doesn't make sense for wired (dhcp) networks, and clicking on it does nothing


STEPS TO REPRODUCE
1. Have a wired network that is configured via DHCP
2. Open the plasma-nm applet

OBSERVED RESULT
A  "Show QR Code" button is shown, clicking it does nothing

EXPECTED RESULT
The button is not shown at all since it doens't make sense for that kind of
network

Operating System: Fedora Linux 36
KDE Plasma Version: 5.25.0
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.3
Kernel Version: 5.17.13-300.fc36.x86_64 (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 31.2 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3070/PCIe/SSE2

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

[plasmashell] [Bug 455334] Regression in 5.25: Window previews no longer shown on task hover

[Christian]

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

--- Comment #1 from Christian (Fuchs)  ---
Potentially not in kwin but rather in frameworks, and potentially fixed by 

https://invent.kde.org/frameworks/plasma-framework/-/commit/dff1b034c1162062aa2292099d3d01fc53dafdf6

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

[kwin] [Bug 453999] new grid implementation is lacking a mouse-hover indication for the active desktop

[Christian]

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

--- Comment #3 from Christian (Fuchs)  ---
Since my bug got marked as a dupe, just to add: 

it does not only lack the mouse hover indication, it also lacks a keyboard
selection indication  (which does work, you just don't see which one is
selected, but you can switch via keyboard)

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

[kwin] [Bug 455350] New: Regression in 5.25: present windows can't be deactivated for desktop grid

[Christian]

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

Bug ID: 455350
   Summary: Regression in 5.25: present windows can't be
deactivated for desktop grid
   Product: kwin
   Version: 5.25.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: effects-desktop-grid
  Assignee: kwin-bugs-n...@kde.org
  Reporter: k...@fuchsnet.ch
  Target Milestone: ---

SUMMARY

As per https://bugs.kde.org/show_bug.cgi?id=455338

there is no way to deactivate the present windows effect in the desktop grid
effect. Therefore it is not possible to arrange windows using that effect. You
can pull them on a different desktop, but positioning them is very hard.

STEPS TO REPRODUCE
1.  Update to 5.25
2.  Start Desktop Grid Effect
3.  Try to arrange windows

OBSERVED RESULT
Can't, because present desktop effect is active which places them randomly 

EXPECTED RESULT
Can

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

[kwin] [Bug 455332] Regressions in present windows effect compared to pre-5.25

[Christian]

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

--- Comment #2 from Christian (Fuchs)  ---
(In reply to Nate Graham from comment #1)
> One issue per bugzilla ticket please. :) 
> 
> That said,
> > - close buttons can't be disabled by config
> > - Panel can't be configured to be shown
> > - blur can't be disabled (oddly enough it can be in the other effect?)
> 
> I don't think these are likely to come back. Gone are the days of excessive
> over-configurability in KDE software. :)

I assume the other new effect is over-configurable then, given that it has a
checkbox for blur. 

Oh well, local patches it is.

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

[kwin] [Bug 455353] New: Regression: filtering is per screen instead of global

[Christian]

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

Bug ID: 455353
   Summary: Regression: filtering is per screen instead of global
   Product: kwin
   Version: 5.25.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: effects-present-windows
  Assignee: kwin-bugs-n...@kde.org
  Reporter: k...@fuchsnet.ch
  Target Milestone: ---

SUMMARY
As per https://bugs.kde.org/show_bug.cgi?id=455332

Typing to filter windows is per screen instead of global. Which especially
breaks the workflow if the effect is called due to clicking on a grouped app in
task manager

STEPS TO REPRODUCE
1. Open present window, e.g. by clicking on a grouped app, say, konsole, that
has windows on all screens
2. Try to filter by typing to the one you want

OBSERVED RESULT
Can't, since the filter only applies to the current screen

EXPECTED RESULT
Can, because filter applies to all screens

Operating System: Fedora Linux 36
KDE Plasma Version: 5.25.0
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.3
Kernel Version: 5.17.13-300.fc36.x86_64 (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 31.2 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3070/PCIe/SSE2

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

[kwin] [Bug 455354] New: filtering isn't re-enabled on typing when you choose windows via keyboard nav

[Christian]

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

Bug ID: 455354
   Summary: filtering isn't re-enabled on typing when you choose
windows via keyboard nav
   Product: kwin
   Version: 5.25.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: effects-present-windows
  Assignee: kwin-bugs-n...@kde.org
  Reporter: k...@fuchsnet.ch
  Target Milestone: ---

SUMMARY
As per https://bugs.kde.org/show_bug.cgi?id=455332


STEPS TO REPRODUCE
1. Open Present Windows
2. Filter
3. Choose a Window with your keyboard
4. Filter

OBSERVED RESULT
Can't, because the filter bar lost focus and doesn't regain it on typing

EXPECTED RESULT
Can, typing goes to filter bar no matter which window is chosen

Sidenote: reverting focus back to filter bar will potentially "forget" which
window was chosen via keyboard, which would be a regression, ideally typing
that aren't nav buttons would go to the filter regardless of focus.

Operating System: Fedora Linux 36
KDE Plasma Version: 5.25.0
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.3
Kernel Version: 5.17.13-300.fc36.x86_64 (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 31.2 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3070/PCIe/SSE2

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

[kwin] [Bug 455355] New: Regression in 5.25: Mouse no longer configurable / pull action completely gone

[Christian]

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

Bug ID: 455355
   Summary: Regression in 5.25: Mouse no longer configurable /
pull action completely gone
   Product: kwin
   Version: 5.25.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: effects-present-windows
  Assignee: kwin-bugs-n...@kde.org
  Reporter: k...@fuchsnet.ch
  Target Milestone: ---

SUMMARY
As per https://bugs.kde.org/show_bug.cgi?id=455332

Pulling a window to the current workspace is no longer possible (plus not
configurable), 
closing windows is possible but neither explained / visible to users nor
configurable

STEPS TO REPRODUCE
1. Open the config for present windows
2. Try to configure mouse buttons to pull / close

OBSERVED RESULT
Can't

EXPECTED RESULT
Can, as in < 5.25 you could choose a mouse button to close (which is a good
feature, but not so great if people can't configure it _plus_ don't know that
it exists, as currently it is not exposed via the GUI) and you could choose a
mouse button to pull the window to the current desktop  (which is a good
feature, but no longer there)

Operating System: Fedora Linux 36
KDE Plasma Version: 5.25.0
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.3
Kernel Version: 5.17.13-300.fc36.x86_64 (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 31.2 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3070/PCIe/SSE2

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

[plasmashell] [Bug 455231] Task manager window thumbnails missing on x11

[Christian]

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

--- Comment #10 from Christian (Fuchs)  ---
(In reply to Nate Graham from comment #2)
> Fixed with
> https://invent.kde.org/frameworks/plasma-framework/-/commit/
> dff1b034c1162062aa2292099d3d01fc53dafdf6 in Frameworks 5.96, but good
> distros should be backporting it to 5.95 as we emailed them specifically
> requesting this.

For Fedora users the fix is now in Zawertuns copr, see
https://github.com/ZaWertun/fedora-copr-kde5/issues/115

> This only affected X11, which most developers aren't using and testing
> anymore, so I guess that's why it was missed prior to the release. If folks
> want to keep the Plasma X11from deteriorating too badly before it's killed
> off altogether (which may happen in Plasma 6)

Probably a bit off-topic, but as long as Wayland isn't production ready stable
(and I consider kwin dying meaning all your applications are force-closed and
data thus lost not being production ready stable) it would be nice if at least
some tests were done on X11, since a good amount of our userbase is probably
still using it for one reason or another.

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

[kwin] [Bug 455368] New: Present Windows effect uses the wrong icon

[Christian]

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

Bug ID: 455368
   Summary: Present Windows effect uses the wrong icon
   Product: kwin
   Version: 5.25.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: effects-present-windows
  Assignee: kwin-bugs-n...@kde.org
  Reporter: k...@fuchsnet.ch
  Target Milestone: ---

Created attachment 149762
  --> https://bugs.kde.org/attachment.cgi?id=149762&action=edit
screenshot of the issue

SUMMARY
The present window effect uses the wrong icon, e.g. if there is a plasma
provides icon (used for the systray) it uses that instead of the coloured
application icon it uses in the window title / task manager.

STEPS TO REPRODUCE
1. Open an app with a plasma icon  (e.g. konversation or cantata)
2. Open present window effect

OBSERVED RESULT
The monochrome icon meant for systray etc. is used

EXPECTED RESULT
The regular app icon is used

Operating System: Fedora Linux 36
KDE Plasma Version: 5.25.0
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.3
Kernel Version: 5.17.13-300.fc36.x86_64 (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 31.2 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3070/PCIe/SSE2

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

[kalendar] [Bug 455369] New: Calendar event notifications lead to segfault if closed by notification button

[Christian]

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

Bug ID: 455369
   Summary: Calendar event notifications lead to segfault if
closed by notification button
   Product: kalendar
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: claudio.cam...@gmail.com
  Reporter: k...@fuchsnet.ch
CC: c...@carlschwan.eu
  Target Milestone: ---

Application: kalendarac (5.20.2)

Qt Version: 5.15.3
Frameworks Version: 5.95.0
Operating System: Linux 5.17.13-300.fc36.x86_64 x86_64
Windowing System: X11
Distribution: Fedora Linux 36 (KDE Plasma)
DrKonqi: 5.25.0 [KCrashBackend]

-- Information about the crash:
Calender events that were previously handled by korgac now create regular
notifications, which do provide a button to dismiss them. However, whenever I
dismiss one via said button, the application crashes with a segfault. See
attached bug report.

The crash can be reproduced every time.

-- Backtrace:
Application: Erinnerungen (kalendarac), signal: Segmentation fault

[KCrash Handler]
#4  0x7fdb84e801a0 in QUtf8::convertFromUnicode(QChar const*, int) () from
/lib64/libQt5Core.so.5
#5  0x7fdb84cfa0b4 in QString::toUtf8_helper(QString const&) () from
/lib64/libQt5Core.so.5
#6  0x7fdb85807c6f in KConfigBase::isGroupImmutable(QString const&) const
() from /lib64/libKF5ConfigCore.so.5
#7  0x7fdb858121c3 in KConfigGroup::KConfigGroup(KConfigBase*, QString
const&) () from /lib64/libKF5ConfigCore.so.5
#8  0x55c42791f960 in KalendarAlarmClient::dismiss(AlarmNotification*) ()
#9  0x7fdb84e5fc36 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#10 0x7fdb85cf6a87 in KNotification::close() () from
/lib64/libKF5Notifications.so.5
#11 0x7fdb84e5fc36 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#12 0x7fdb85cf3c33 in KNotificationPlugin::finished(KNotification*) () from
/lib64/libKF5Notifications.so.5
#13 0x7fdb85d0b349 in NotifyByPopup::onNotificationClosed(unsigned int,
unsigned int) () from /lib64/libKF5Notifications.so.5
#14 0x7fdb84e5fc36 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#15 0x7fdb85d175e9 in
OrgFreedesktopNotificationsInterface::qt_static_metacall(QObject*,
QMetaObject::Call, int, void**) () from /lib64/libKF5Notifications.so.5
#16 0x7fdb85d17fdb in
OrgFreedesktopNotificationsInterface::qt_metacall(QMetaObject::Call, int,
void**) () from /lib64/libKF5Notifications.so.5
#17 0x7fdb8513be7b in QDBusConnectionPrivate::deliverCall(QObject*, int,
QDBusMessage const&, QVector const&, int) () from /lib64/libQt5DBus.so.5
#18 0x7fdb84e56694 in QObject::event(QEvent*) () from
/lib64/libQt5Core.so.5
#19 0x7fdb84e2c658 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5
#20 0x7fdb84e2f9b4 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /lib64/libQt5Core.so.5
#21 0x7fdb84e7d807 in postEventSourceDispatch(_GSource*, int (*)(void*),
void*) () from /lib64/libQt5Core.so.5
#22 0x7fdb82811faf in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#23 0x7fdb828672c8 in g_main_context_iterate.constprop () from
/lib64/libglib-2.0.so.0
#24 0x7fdb8280f940 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#25 0x7fdb84e7d2fa in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt5Core.so.5
#26 0x7fdb84e2b0ba in
QEventLoop::exec(QFlags) () from
/lib64/libQt5Core.so.5
#27 0x7fdb84e33162 in QCoreApplication::exec() () from
/lib64/libQt5Core.so.5
#28 0x55c42791cefd in main ()
[Inferior 1 (process 2131) detached]

Reported using DrKonqi

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

[kwin] [Bug 455368] Present Windows effect uses the wrong icon

[Christian]

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

--- Comment #1 from Christian (Fuchs)  ---
Additional note: 

this could be fixed by adding

usesPlasmaTheme: false

to the Plasma.IconItem that is used in that effect, but it seems that the qml
sources for it are a bit spread across various places, so I didn't find it with
a quick search.

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

[kwin] [Bug 455368] Present Windows effect uses the wrong icon

[Christian]

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

--- Comment #2 from Christian (Fuchs)  ---
Oh, nevermind,  the fix is: 

--- WindowHeap.qml  2022-06-16 00:33:35.627845270 +0200
+++ WindowHeapOrig.qml  2022-06-16 00:34:06.419713139 +0200
@@ -235,7 +235,6 @@

 PlasmaCore.IconItem {
 id: icon
+   usesPlasmaTheme: false 
 width: PlasmaCore.Units.iconSizes.large
 height: width
 source: thumb.client.icon

This. Some developer who knows where that file actually comes from repo-wise
please fix it, thanks :)

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

[kwin] [Bug 454842] Window highlight effect is now rather faint and easy to miss

[Christian]

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

Christian (Fuchs)  changed:

   What|Removed |Added

 CC||k...@fuchsnet.ch

--- Comment #3 from Christian (Fuchs)  ---
I assume that's the bug that Nate meant in the VDG group, thus suggesting that
here: 

--- WindowHeap.qml  2022-06-16 00:33:35.627845270 +0200
+++ WindowHeapOrig.qml  2022-06-16 00:34:06.419713139 +0200

PlasmaCore.FrameSvgItem {
anchors.fill: parent
-   anchors.margins: -PlasmaCore.Units.smallSpacing
+  anchors.margins: -PlasmaCore.Units.largeSpacing * 2  

would lead to the attachment I'll upload in a sec which would be a lot easier
to notice, it would also surround the window label. 
If people prefer a smaller one that doesn't surround the label, mediumSpacing
would probably do

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

[kwin] [Bug 454842] Window highlight effect is now rather faint and easy to miss

[Christian]

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

--- Comment #4 from Christian (Fuchs)  ---
Created attachment 149765
  --> https://bugs.kde.org/attachment.cgi?id=149765&action=edit
original size of the highlight

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

[kwin] [Bug 454842] Window highlight effect is now rather faint and easy to miss

[Christian]

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

--- Comment #5 from Christian (Fuchs)  ---
Created attachment 149766
  --> https://bugs.kde.org/attachment.cgi?id=149766&action=edit
suggested bigger highlight

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

[kwin] [Bug 455100] Selecting the search bar with the keyboard is only possible once

[Christian]

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

Christian (Fuchs)  changed:

   What|Removed |Added

 CC||k...@fuchsnet.ch

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

[kwin] [Bug 455101] Using the mouse and then the keyboard results in double focus

[Christian]

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

Christian (Fuchs)  changed:

   What|Removed |Added

 CC||k...@fuchsnet.ch

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

[kwin] [Bug 455099] Switching focus away from the search bar with down arrow key highlights nothing on first keypress; second one highlights a window

[Christian]

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

Christian (Fuchs)  changed:

   What|Removed |Added

 CC||k...@fuchsnet.ch

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

[kwin] [Bug 455355] Regression in 5.25: Mouse no longer configurable / pull action completely gone

[Christian]

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

--- Comment #2 from Christian (Fuchs)  ---
(In reply to Nate Graham from comment #1)
> Can you explain what "Pulling a window to the current workspace is no longer
> possible" means? I don't have this usage mode so I'm not familiar with how
> it used to work.

Sure, so on the old effect you could bind actions to mouse buttons, activate
(obvious), close (obvious) and at least pull to current desktop, maybe others,
but these are the ones I used. 

What pull to current desktop does: Say you have 6 virtual desktops, and you are
currently on desktop 1, and start the effect: with that mouse button you could
pull windows from desktops 2-6 to desktop 1, which is very handy and efficient
to manage multiple windows at once, e.g. if you want to pull a code editor and
a browser with documentation quickly to the same virtual desktop

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

[kwin] [Bug 455354] filtering isn't re-enabled on typing when you choose windows via keyboard nav

[Christian]

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

--- Comment #2 from Christian (Fuchs)  ---
(In reply to Nate Graham from comment #1)
> Cannot reproduce on Wayland; must be one of those weird X11-only focus bugs,
> of which we have a few.

Most likely fixed by
https://invent.kde.org/plasma/kwin/-/commit/a4b41c84e146062851b8adf96b9cd4ee512f52df
at least currently I can't reproduce it with these changes applied, easily can
without.

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

[kwin] [Bug 455355] Regression in 5.25: Mouse no longer configurable / pull action completely gone

[Christian]

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

--- Comment #3 from Christian (Fuchs)  ---
A very crude way to get that behaviour again would be to modify the main.qml of
windowview to 

onWindowClicked: {
if (eventPoint.event.button == Qt.MiddleButton) {
window.closeWindow();
}
else if (eventPoint.event.button == Qt.RightButton) {
window.desktop = KWinComponents.Workspace.currentDesktop;
}
else {
   return;
}
}


but imho this should be configurable, as in: users can configure what the left,
right and middle button do, possibilities being activate, pull, close, nothing.
Plus probably there should be some checks, e.g. I have no idea how
currentDesktop behaves in some edge cases / on Wayland, and
https://develop.kde.org/docs/extend/plasma/kwin/api/#read-write-properties  is
a bit bare. But if you want to see what the functionality would do: the above
will do just that.

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

[kwin] [Bug 455355] Regression in 5.25: Mouse no longer configurable / pull action completely gone

[Christian]

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

--- Comment #5 from Christian (Fuchs)  ---
(In reply to Nate Graham from comment #4)
> Thanks, that's helpful. Confirmed. Marking as a bug rather than a wishlist
> item since the intention was to preserve feature parity with the QML port.
> 
> Given that re-adding this feature would require adding new UI and new
> strings, I'm afraid it'll have to be merged for 5.26 rather than a 5.25
> bugfix release.

That's sad but was somewhat to be expected, I'll have to live with local
patches for a good while anyway, since it's not the only thing missing. And
thanks to it being QML, people affected can patch it locally with their
preferred actions hardcoded, example see above. 

Wrt UI: for the sake of consistency and (half of the) strings: icon only task
manager has a UI for exactly this (middle click entries). 
I suggest just using that for each mouse button. I think configuring the plasma
desktop -> mouse also has one of these, but that's very flexible (you can add
and remove mouse buttons), not sure if we want to go that whole mile, but if
so: that would be a good template for it.

Fuchs

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

[xdg-desktop-portal-kde] [Bug 460985] portal-based open-with implementation lacks choosing custom binary

[Christian]

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

--- Comment #9 from Christian (Fuchs)  ---
It seems 5.27 got released without this, so if you as a user now need to open a
certain file with a custom application, you simply can't.

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

[xdg-desktop-portal-kde] [Bug 460985] portal-based open-with implementation lacks choosing custom binary

[Christian]

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

--- Comment #11 from Christian (Fuchs)  ---
(In reply to Nate Graham from comment #10)
> Oops.

I'd say this needs fixing urgently, but unfortunately we probably can't within
the 27er release, and given there is no 28 and some distributions are probably
not going to upgrade to Qt6 based plasma 6, so we are going to be stuck with
this for a while :/

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

[Breeze] [Bug 465948] Option to disable window border introduced in 5.27

[Christian]

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

Christian (Fuchs)  changed:

   What|Removed |Added

 CC||k...@fuchsnet.ch

--- Comment #4 from Christian (Fuchs)  ---
Agreed on offering an option or a customizable colour (including "none"), since
it unfortunately doesn't look that good on some colour combinations, including
mine  (dark blue)

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

[kwin] [Bug 455350] Regression in 5.25: present windows can't be deactivated for desktop grid

[Christian]

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

--- Comment #26 from Christian (Fuchs)  ---
(In reply to Martin van Es from comment #25)
> In can confirm the old behaviour has been restored as Windows Layout "None"
> in plasma 5.27.
> Thx!

Almost, the layout is indeed as it was before and works nicely, unfortunately
dragging around windows to change their position (not their workspace) doesn't
work, as they "snap back" into a certain position.

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

[Breeze] [Bug 465948] Option to disable window border introduced in 5.27

[Christian]

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

--- Comment #12 from Christian (Fuchs)  ---
(In reply to breakingspell from comment #11)
> Sorry, hit enter by accident and submitted. 
> 
> The code checks for "no borders" and "no side-borders" to choose where to
> draw the outline, could that check be used to completely hide the border
> rather than adding "yet-another-checkbox"?

Imho no, since there are people who want a border but no outline (e.g. me), and
most certainly also people who want no borders but the outline, since
apparently it was added for accessibility.

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

[xdg-desktop-portal-kde] [Bug 460985] portal-based open-with implementation lacks choosing custom binary

[Christian]

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

--- Comment #18 from Christian (Fuchs)  ---
(In reply to Harald Sitter from comment #14)
> Same question for your proposal
> 
> What happens when one has picked a file or entered the path and hit enter?
> Does it just open with that file? 

I think the old (and imho correct) behaviour was indeed to just call that
binary with the path of the file as the first and only argument, yes.

> What I don't get btw, why do you have applications that don't have a desktop
> file? What kind of applications are those? And couldn't they just have a
> desktop file to begin with? So kickoff/krunner and this dialog have an
> easier time finding them?

A whole fun mixture of  "binaries you downloaded" via "binaries you compiled
yourself" to "scripts you wrote" etc. pp.
In an ideal world every app would have a corresponding .desktop file, yes. But
we do not live in this ideal world and, more importantly, we as KDE can't
enforce / control it. So to not put users in front of a very-hard-to-resolve
problem (writing their own .desktop file, and I know this can technically be
done through means such as menu editor, but: they don't) we can just give them
a manual override.

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

[xdg-desktop-portal-kde] [Bug 460985] portal-based open-with implementation lacks choosing custom binary

[Christian]

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

--- Comment #21 from Christian (Fuchs)  ---
As an addition to the "does it create a .desktop file" if you choose a custom
binary: 

imho either no, as things should be explicit and not implicit, or yes, but only
when you check a 
[x] always open $filetype with this application
checkbox of sorts. Because otherwise for the case of temporary binaries (e.g.
imagine something you build a new binary under a new path/name for every
version) you'll end up with a hard to clean mess of old cruft.

Other than that, I am fine with whatever, but I do agree with Nate that an
explicit dialogue is nicer.
For brevity such as wished by Ilia if we have a keyboard shortcut to open the
file chooser it should still be reasonably fast (assuming correct focus so you
can shortcut and type)

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

[Breeze] [Bug 465948] Option to disable window border introduced in 5.27

[Christian]

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

--- Comment #15 from Christian (Fuchs)  ---
Could we please try to stay friendly and within the KDE CoC?
I would have preferred an option, but it's easy enough to revert for now
without breakage (just downgrade one single .so file), and attacking designers,
devs or anyone really doesn't help matters at all.

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

[frameworks-plasma] [Bug 463061] qBittorrent System tray icon flashes constantly on KDE Plasma

[Christian]

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

Christian (Fuchs)  changed:

   What|Removed |Added

 CC||k...@fuchsnet.ch

--- Comment #16 from Christian (Fuchs)  ---
The flashing is still very annoying even reduced, couldn't whatever caused this
in 5.101.0 be reverted?

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

[frameworks-plasma] [Bug 466357] New: Flickering in systray for apps that change tooltip or on mouse hover

[Christian]

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

Bug ID: 466357
   Summary: Flickering in systray for apps that change tooltip or
on mouse hover
Classification: Frameworks and Libraries
   Product: frameworks-plasma
   Version: 5.103.0
  Platform: unspecified
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: libplasma
  Assignee: plasma-b...@kde.org
  Reporter: k...@fuchsnet.ch
CC: m...@ratijas.tk, notm...@gmail.com
  Target Milestone: ---

Created attachment 156678
  --> https://bugs.kde.org/attachment.cgi?id=156678&action=edit
screencast of the issue, first half is app only with no user interaction,
second half is mouse hover

SUMMARY
The flickering in https://bugs.kde.org/show_bug.cgi?id=463685 /
https://bugs.kde.org/show_bug.cgi?id=463061 is still present, new bug report
because it's not specific to qbittorrrent (even though that's a good candidate
to trigger it) and the others are closed.

STEPS TO REPRODUCE
1. Have an icon in the systray that changes its tooltip
2. Alternatively mouse-hover an icon such as volume

OBSERVED RESULT
Heavy flickering, which (especially when not caused by mouse hover but rather
by the app itself) causes the eyes to focus there as there is movement

EXPECTED RESULT
No flickering

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 37
KDE Plasma Version: 5.27.1
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.1.12-200.fc37.x86_64 (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 7700X 8-Core Processor
Memory: 31.1 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 4080/PCIe/SSE2
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7D70
System Version: 1.0

Sidenote: also reproducible on my notebook which has an Intel CPU and GPU, same
software versions

ADDITIONAL INFORMATION
Introduced by
https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/649
Not fixed yet by
https://invent.kde.org/frameworks/plasma-framework/commit/3fcd43a6ed03d0aff188dfc190cc464c34302a1f

The question if this is caused by an animation to fade-in / -out is if that
animation is really needed as is.
Because if it is mainly / just for aesthetics, this most certainly does the
opposite of what it tries to achieve.
Also: is it needed for the icon to reload / do that whenever the tooltip
changes? If not, disabling that would at least fix it for the case where there
is no user interaction, which would be a good start

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

[frameworks-plasma] [Bug 463061] qBittorrent System tray icon flashes constantly on KDE Plasma

[Christian]

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

--- Comment #18 from Christian (Fuchs)  ---
(In reply to Nate Graham from comment #17)
> You're experiencing the same issue with qBittorrent or other 3rd-party SNIs?
> Or are plasmoids flickering? Or both?

Both. Tested with ktorrent and plasmoids, e.g. the volume one, see video in
466357

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

[frameworks-plasma] [Bug 466357] Flickering in systray for apps that change tooltip or on mouse hover

[Christian]

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

--- Comment #4 from Christian (Fuchs)  ---
(In reply to Arjen Hiemstra from comment #3)

> With regards to the issues mentioned here specifically, for the qBittorrent
> case we should improve how we detect icon changes rather than trying to work
> around it in other places, as the core of the issue there is the icon being
> detected as changed but not actually changing.

Yes. The case of "flickering without user interaction" being solved would
already do a lot, since at least when you mouse-hover or do something, chances
are your eyes are already focussed on the systray area, so you won't be
distracted by a flickering in the corner of your field of view. That would help
a lot. 

Still: 

> For the other icon, when you
> hover over an item in the systray, there is a highlight effect applied that
> is done by changing the icon pixels, so the icon changes and the animation
> is triggered. As the icon uses semi-transparency for muting the colour, it
> ends up being drawn twice and you end up with an effect where the "muted"
> lines are slightly less muted for a short moment.

while I use a custom  (older, but official) volume icon and the newer one might
not suffer as much from it, the current (wireless) network icon does. As do
probably do a handful others, so preferably this would also be fixed not in the
icons or how they use transparency, but rather the effect.

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

[xdg-desktop-portal-kde] [Bug 460985] portal-based open-with implementation lacks choosing custom binary

[Christian]

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

--- Comment #26 from Christian (Fuchs)  ---
(In reply to Nate Graham from comment #25)
> Rodrigo, I'm starting to come to that conclusion myself. Perhaps the
> switchover was premature, and we can delay it until we have all the missing
> features from the old dialog implemented in the new one. I plan to look into
> this soon.

I'd +1 reverting delaying switching over until 6.* which is a major new version
and "breaking" changes are less of an issue, plus it will get frequent feature
updates, which will make changes easier. Thanks a lot for looking into this :)

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

[xdg-desktop-portal-kde] [Bug 460985] portal-based open-with implementation lacks choosing custom binary

[Christian]

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

--- Comment #27 from Christian (Fuchs)  ---
(In reply to Christian (Fuchs) from comment #26)

> I'd +1 reverting delaying switching over until 6.* which is a major new
> version and "breaking" changes are less of an issue, plus it will get
> frequent feature updates, which will make changes easier. Thanks a lot for
> looking into this :)

err,  "reverting the switch and delaying ..." of course, sorry, paws faster
than brain, sorry for the spam.

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

[dolphin] [Bug 466796] New: Opening search sometimes messes up layout (sidebar sizes)

[Christian]

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

Bug ID: 466796
   Summary: Opening search sometimes messes up layout (sidebar
sizes)
Classification: Applications
   Product: dolphin
   Version: 22.12.3
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: view-engine: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: k...@fuchsnet.ch
CC: kfm-de...@kde.org
  Target Milestone: ---

Created attachment 156976
  --> https://bugs.kde.org/attachment.cgi?id=156976&action=edit
Video of the issue, first half is as it should be, second half is the bug

SUMMARY
Opening the search bar in dolphin sometimes messes up your layout (the width of
the sidebars) and doesn't restore them after closing the search, so you need to
manually re-adjust them every time

STEPS TO REPRODUCE
1. Open dolphin
2. Have at least one sidebar
3. Seems to be easier to reproduce in a folder with many items
4. Open the search

OBSERVED RESULT
Your preferred layout (e.g. sidebar width) is modified, sidebars are being made
a lot thinner  (second half of video)

EXPECTED RESULT
Your preferred layout stays as is, and the search doesn't take more space than
it is allowed to (first half of video)

Operating System: Fedora Linux 37
KDE Plasma Version: 5.27.2
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 6.1.14-200.fc37.x86_64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i5-8365U CPU @ 1.60GHz
Memory: 15.3 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: LENOVO
Product Name: 20NQS5TD01
System Version: ThinkPad X390 Yoga

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

[dolphin] [Bug 440663] New Dolphin window or tab opened after compression/extraction when certain default options are disabled, or when the job is canceled, or when the Dolphin window that initiated i

[Christian]

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

--- Comment #79 from Christian (Fuchs)  ---
I can confirm that this bug re-surfaced again, and I did see the revert on
GitLab with "We no longer need this", yes, we do, and please keep the
"workaround" or indeed do remove the misfeature that causes this bug.

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

[dolphin] [Bug 440663] New Dolphin window or tab opened after compression/extraction when certain default options are disabled, or when the job is canceled, or when the Dolphin window that initiated i

[Christian]

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

--- Comment #84 from Christian (Fuchs)  ---
For me it's been 100% reproducible when _creating_ an archive, not when
extracting it. This is regardless of any settings in either dolphin or ark. It
came with a recent update of either frameworks or plasma. 

What is worth mentioning is that this is on X11, while I don't see why it
should make a difference, it actually did make one in the past where that bug
was not (always) reproducible on wayland but on X11.

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

[dolphin] [Bug 440663] New Dolphin window or tab opened after compression/extraction when certain default options are disabled, or when the job is canceled, or when the Dolphin window that initiated i

[Christian]

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

--- Comment #89 from Christian (Fuchs)  ---
While I see your argument, I think there is no, absolutely zero, gain in
opening a new window after _creating_ an archive. Extracting could be debated,
but I don't see why anyone would expect creating a new archive to open a new
window. Even more so with cancelling an ongoing operation. 

>From a UX perspective, neither of these operations should imho open a window.
If it can be disabled, but only by altering other behaviour of dolphin with the
same setting, then I'd consider that a bug that needs fixing. And if there is a
setting which does alter this and only this behaviour, I think the default
setting should be "do not open a new window", since I don't see the use case of
opening one after creating an archive or cancelling an archive process.

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

[kmail2] [Bug 459341] Kmail crash when trying to write recipent address in the new mail window

[Christian]

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

Christian (Fuchs)  changed:

   What|Removed |Added

 CC||k...@fuchsnet.ch

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

[Spectacle] [Bug 467942] New: Windows Powertoys Text Extractor

[Christian]

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

Bug ID: 467942
   Summary: Windows Powertoys Text Extractor
Classification: Applications
   Product: Spectacle
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: christian.tall...@gmx.de
CC: k...@david-redondo.de
  Target Milestone: ---

SUMMARY
***
The Windows Powertoys Text Extractor is a nice tool that works similar to the
sniping tool or Greenshot or KDE-Spectacle.
You can select a rectangular part of the screen and it runs a OCR on the
content and copies the text into your clipboard.
I think a feature like that for Spectacle would be a really productive
enhancement.
It would be great if you could assign a different Hot-Key than the Screenshot
Hot-Key for it.
**

Currently you could take a screenshot with Spectacle.
Run an OCR software on the saved screenshot e.g. Tesseract and then copy the
results.

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

[Discover] [Bug 470437] New: Installing flatpak file opens Discover but "Loading" animation continuously loops; flackpak does not install.

[Christian]

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

Bug ID: 470437
   Summary: Installing flatpak file opens Discover but "Loading"
animation continuously loops; flackpak does not
install.
Classification: Applications
   Product: Discover
   Version: 5.27.2
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: Flatpak Backend
  Assignee: plasma-b...@kde.org
  Reporter: qris...@gmail.com
CC: aleix...@kde.org, jgrul...@redhat.com,
trav...@redhat.com
  Target Milestone: ---

Created attachment 159338
  --> https://bugs.kde.org/attachment.cgi?id=159338&action=edit
discover screen shot

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Download com.jetbrains.PyCharm-Community.flatpakref
2. Double click to install
Note: this also happens when searching inside Discover for PyCharm Community
and clicking install button.

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Debian 12 Bookworm testing branch
(available in About System)
KDE Plasma Version: 5.27.2
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION

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

[kdeconnect] [Bug 469331] New: Send tab from IOS Device to Plasma Desktop

[Christian]

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

Bug ID: 469331
   Summary: Send tab from IOS Device to Plasma Desktop
Classification: Applications
   Product: kdeconnect
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: ios-application
  Assignee: lucas.w...@tuta.io
  Reporter: christian.tall...@gmx.de
  Target Milestone: ---

SUMMARY

You can already send tabs with the plasma browser integration from the PC to
your iOS device.
On iOS devices you can touch the share button in safari to send a tab via
AirDrop, Mail or various other apps.
It would be nice if you could select the KDEConnect app and send the tab to
your connected PC.

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

[kwin] [Bug 469503] New: UX: Disable window snapping back to old position in layout mode "none"

[Christian]

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

Bug ID: 469503
   Summary: UX: Disable window snapping back to old position in
layout mode "none"
Classification: Plasma
   Product: kwin
   Version: master
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: effects-present-windows
  Assignee: kwin-bugs-n...@kde.org
  Reporter: k...@fuchsnet.ch
  Target Milestone: ---

SUMMARY
Technically the bug can be reproduced in "desktop grid", but code-wise I think
it's in present windows.

As per user requests due to this having been missing in the QML rewrite, a new
layout mode "None" was implemented, so that windows in desktop grid (which
triggers the present window effect) have their original size and position so
they can be moved around. This was implemented in the last release, however,
moving windows around (on the current virtual desktop, not moving it to other
desktops) does not work as expected, as the windows always snap back to their
previous position when moved.

STEPS TO REPRODUCE
1. Configure desktop grid to have the window layout "None"
2.  Trigger desktop grid
3.  Try to move a window to a new position

OBSERVED RESULT
Window snaps to a previous / fixed position

EXPECTED RESULT
Window is _exactly_ where the user places it and stays there

Operating System: Fedora Linux 38
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.105.0
Qt Version: 5.15.9
Kernel Version: 6.2.14-300.fc38.x86_64 (64-bit)
Graphics Platform: X11

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

[ark] [Bug 469762] Give us a way to configure if the destination opens or not after creating an archive via "Compress to..." option from the context menus

[Christian]

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

Christian (Fuchs)  changed:

   What|Removed |Added

 CC||k...@fuchsnet.ch

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

[plasmashell] [Bug 460310] New: 3rd party plasmoids break if size but not implicit size is set in fullRepresentation

[Christian]

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

Bug ID: 460310
   Summary: 3rd party plasmoids break if size but not implicit
size is set in fullRepresentation
Classification: Plasma
   Product: plasmashell
   Version: 5.25.90
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: k...@fuchsnet.ch
CC: k...@davidedmundson.co.uk
  Target Milestone: 1.0

Created attachment 152749
  --> https://bugs.kde.org/attachment.cgi?id=152749&action=edit
screenshot of the issue, on the left is 5.26 sizing, on the right is 5.25

STEPS TO REPRODUCE
1. Get a third party plasmoid that doesn't set implicitWidth and implicitHeight
(e.g. weather-applet) 
2.  Update to plasma 5.26
3.  Click to expand

OBSERVED RESULT
Completely wrong sizing (see screenshot)

EXPECTED RESULT
Correct sizing as with 5.25   (implicitWidth = width)

Operating System: Fedora Linux 36
KDE Plasma Version: 5.26.0
KDE Frameworks Version: 5.99.0
Qt Version: 5.15.6
Kernel Version: 5.19.14-200.fc36.x86_64 (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3070/PCIe/SSE2
System Version: 1.0

Additional Information: 

the plasmoid doesn't offer resizing as others do with 5.26, but even if
manually resized (via the alt+mouseButton shortcut) the custom size is lost
after a plasma restart.

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

[kwin] [Bug 107302] Per-screen virtual desktops

[Christian]

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

Christian (Fuchs)  changed:

   What|Removed |Added

 CC||k...@fuchsnet.ch

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

[kwin] [Bug 486850] Regression: Windows of other workspaces not shown when "organize windows in the grid view" is NOT selected

[Christian]

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

--- Comment #1 from Christian (Fuchs)  ---
This bug is still present in 6.1 and basically makes the grid unusable, since
you only see windows of one workspace.

Probably this would just need a trigger to show all windows, as the present
windows effect does, which is not triggered if you don't check the "organize
windows in the grid view" option.

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

[plasmashell] [Bug 489099] New: Keyboard navigation broken since reorg of switch

[Christian]

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

Bug ID: 489099
   Summary: Keyboard navigation broken since reorg of switch
Classification: Plasma
   Product: plasmashell
   Version: 6.1.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Battery Monitor
  Assignee: plasma-b...@kde.org
  Reporter: k...@fuchsnet.ch
CC: k...@privat.broulik.de, m...@ratijas.tk,
natalie_clar...@yahoo.de
  Target Milestone: 1.0

SUMMARY
Since re-ordering the inhibit action from the header into the plasmoid (why?)
keyboard navigation is now broken.
The down arrow works as expected, the up arrow depends on what item the focus
is currently at, but it's wrong.

STEPS TO REPRODUCE
1.  Update to plasma >= 6.1
2.  Open the battery plasmoid
3.  Try to navigate by keyboard

OBSERVED RESULT
Up arrow doesn't work as it's still bound to the old layout

EXPECTED RESULT
Keys work as expected

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

[kwin] [Bug 489100] New: Regression since effect merge: no reliable keyboard navigation for workspaces

[Christian]

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

Bug ID: 489100
   Summary: Regression since effect merge: no reliable keyboard
navigation for workspaces
Classification: Plasma
   Product: kwin
   Version: 6.1.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: effects-overview
  Assignee: kwin-bugs-n...@kde.org
  Reporter: k...@fuchsnet.ch
  Target Milestone: ---

SUMMARY
Since the overview effect is now used both for the desktop grid and the present
windows effect, there are some regressions. Keyboard navigation for navigating
workspaces in the grid is no longer reliable, since depending on how many
windows there are on a workspace and how the effect ordered them, the amount of
arrow presses to navigate to the next / previous / above / below workspace is
random.

STEPS TO REPRODUCE
1. Open the overview effect in the grid mode  (workspaces ordered as a grid)
2. Try to navigate via keyboard navigation

OBSERVED RESULT
Amount of button presses to navigate e.g. two workspaces to the right or one
down and one left is dependant on how many windows there are, how they are
ordered by the effect and which window is considered e.g. below in the effect.

EXPECTED RESULT
Have a reliable way to navigate workspace only, and not windows
(e.g. by either having a separate keyboard shortcut like wasd  to navigate
workspaces, or an option to skip windows in this view)

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

[ksplash] [Bug 487632] New: theme config is ignored

[Christian]

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

Bug ID: 487632
   Summary: theme config is ignored
Classification: Plasma
   Product: ksplash
   Version: 6.0.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: k...@fuchsnet.ch
  Target Milestone: ---

SUMMARY
Since Upgrading to plasma 6.* I have the problem that my chosen theme for
ksplash is completely ignored.
I have a theme called org.kde.oxygen (which is indeed an old, ported oxygen
theme) which appears in systemsettings and I can choose it. The config in
~/.config/ksplashrc is correct. Regardless of that, the default breeze theme is
shown, both when I log in, but also when I do press the play button in
systemsettings.

However, if I just blindly copy the contents of
/usr/share/plasma/look-and-feel/org.kde.oxygen/contents/splash/ into
/usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/splash/, my
theme is shown on login, thus the theme itself is not faulty.

STEPS TO REPRODUCE
1.  Have a custom kspash theme, say
/usr/share/plasma/look-and-feel/org.kde.oxygen/contents/splash/
2.  Choose it in systemsettings
3.  Log in 

OBSERVED RESULT
Wrong theme (default breeze) is shown

EXPECTED RESULT
Chosen theme is shown

Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.0
Kernel Version: 6.8.10-300.fc40.x86_64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i5-8265U CPU @ 1.60GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: LENOVO
Product Name: 20NQS30W00
System Version: ThinkPad X390 Yoga

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

[ksplash] [Bug 487632] theme config is ignored

[Christian]

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

Christian (Fuchs)  changed:

   What|Removed |Added

 Resolution|WAITINGFORINFO  |LATER
 Status|NEEDSINFO   |RESOLVED

--- Comment #2 from Christian (Fuchs)  ---
(In reply to David Redondo from comment #1)
> Any interesting output in  ksplashqml --test ?
> 
> Does your theme have metadata.json? (metadata.desktop is no longer supported)

Thanks for the pointer, I was able to resolve it, but I think ksplash /
systemsettings could prevent that.
The output of ksplashqml --test was empty with no error message, but it just
showed a blank screen, 

fuchs@comfox /usr/share/plasma % ksplashqml
/usr/share/plasma/look-and-feel/org.kde.oxygen/   
^C
fuchs@comfox /usr/share/plasma % ksplashqml 
^C


There was a metadata.json in the top level folder that was probably converted
from the old format, and the new folders have a .desktop suffix while the old
ones didn't, so the id line did not exactly match the folder name.
Thus the theme was shown and selectable in systemsettings, but it did not work.

Maybe a test could be added that checks for the presence of the folder name and
show a warning / error on the command line if it is not there, and potentially
also make the theme not selectable in systemsettings.

In either case, I'd consider this resolved, but it would be nice if such a
check would be added.

Thanks and have a nice $timeofday :)

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

[plasmashell] [Bug 487987] New: Regression: (X11) Primary Selection no longer appears in history

[Christian]

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

Bug ID: 487987
   Summary: Regression: (X11) Primary Selection  no longer appears
in history
Classification: Plasma
   Product: plasmashell
   Version: 6.0.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Clipboard
  Assignee: plasma-b...@kde.org
  Reporter: k...@fuchsnet.ch
  Target Milestone: 1.0

SUMMARY
On my desktop I have plasma 5.27.11, on my notebook I upgraded to 6.0.5. 
The clipboard settings are (visually, in the GUI) the same, but the behaviour
on 6.0.5 changed.

Selecting text  (X11 Primary Selection) appears in the history on 5.*, while it
no longer does on 6.* unless I activate the option to keep the clipboard and
selection in sync, which I do not want.

There is an option, but it only becomes editable if the sync is enabled, and
doesn't allow me to configure it the way 5.* behaves (or I didn't find out how)

Please fix this regression, as managing both the selection and the clipboard
content is an important usecase to me.
I also don't see why this should not be possible option-wise, as in: why this
specific combination can't be configured.

STEPS TO REPRODUCE
1. Update to Plasma 6.*
2.  Use X11 (potentially same in Wayland, didn't test, not sure about selection
there in general)
3. Mark text with mouse

OBSERVED RESULT
Text doesn't appear in clipboard history

EXPECTED RESULT
Text does appear, as it did in 5.*

If you think this is confusing for users, please at least offer an option
(since the GUI seems somewhat prepared to that) to change that behaviour.

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

[dolphin] [Bug 479695] In icons view mode, file name moves left during rename

[Christian]

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

Christian (Fuchs)  changed:

   What|Removed |Added

 CC||k...@fuchsnet.ch

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

[kwin] [Bug 465858] shift + drag does not interact with the tiling layout if Both Shifts together enable Caps Lock

[Christian]

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

Christian  changed:

   What|Removed |Added

 CC||christian.tall...@gmx.de

--- Comment #13 from Christian  ---
Is there a way to detect what shortcut causes the problem?
I am on openSuse Tumbleweed Plasma 6 and can start the tiling editor but
holding shift + moving the window does not work.
I don´t have the mentioned shortcuts enabled, but there seems to be no way to
configure the tiling action.

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

[plasmashell] [Bug 485046] New: Opacity Adaptive not working when Visibility Dodge Windows is active

[Christian]

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

Bug ID: 485046
   Summary: Opacity Adaptive not working when Visibility Dodge
Windows is active
Classification: Plasma
   Product: plasmashell
   Version: 6.0.3
  Platform: openSUSE
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Panel
  Assignee: plasma-b...@kde.org
  Reporter: christian.tall...@gmx.de
CC: niccolo.venera...@gmail.com
  Target Milestone: 1.0

Created attachment 168155
  --> https://bugs.kde.org/attachment.cgi?id=168155&action=edit
Picture of the Problem

SUMMARY
When using a floating panel that has Visibility="Dodge Windows" and
Opacity="Adaptive" the panel correctly dodges, but is always translucent for
me.
When a Window is maximized, I would expect the panel to be opaque when moving
the cursor down, to show the panel.

STEPS TO REPRODUCE
1. Create a floating panel.
2. Set Visibility to "Dodge Windows"
3. Set Opacity to "Adaptive"
4. Maximize a Window.
5. Move the cursor down to show the floating panel.

OBSERVED RESULT
The Panel is translucent.

EXPECTED RESULT
The Panel should be opaque.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: openSUSE Tumbleweed 20240403
KDE Plasma Version: 6.0.3
KDE Frameworks Version: 6.0.0 
Qt Version: 6.6.3

ADDITIONAL INFORMATION
Graphics Platform: X11

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

[plasmashell] [Bug 485046] Opacity Adaptive not working when Visibility Dodge Windows is active

[Christian]

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

Christian  changed:

   What|Removed |Added

 CC||christian.tall...@gmx.de

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

[kwin] [Bug 486849] New: Regression: Grid Overview not available as corner action

[Christian]

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

Bug ID: 486849
   Summary: Regression: Grid Overview not available as corner
action
Classification: Plasma
   Product: kwin
   Version: 6.0.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: effects-overview
  Assignee: kwin-bugs-n...@kde.org
  Reporter: k...@fuchsnet.ch
  Target Milestone: ---

SUMMARY
Since the merging of various effects into the overview effect (Plasma 6), the
grid overview that has been added (including a keyboard shortcut) can't be
triggered as a corner action (the thing where moving the mouse cursor into a
screen corner triggers something)

STEPS TO REPRODUCE
1.  Go to system settings
2.  Go to screen corner actions
3.  Try to add the grid effect of overview

OBSERVED RESULT
You can't, it's not in the list

EXPECTED RESULT
You can, as it was possible pre-plasma-6 when this was a separate effect

Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.8.8-300.fc40.x86_64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i5-8265U CPU @ 1.60GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: LENOVO
Product Name: 20NQS30W00
System Version: ThinkPad X390 Yoga

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

[kwin] [Bug 486850] New: Regression: Windows of other workspaces not shown when "organize windows in the grid view" is NOT selected

[Christian]

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

Bug ID: 486850
   Summary: Regression: Windows of other workspaces not shown when
"organize windows in the grid view" is NOT selected
Classification: Plasma
   Product: kwin
   Version: 6.0.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: effects-overview
  Assignee: kwin-bugs-n...@kde.org
  Reporter: k...@fuchsnet.ch
  Target Milestone: ---

SUMMARY
Thank you very much for the "organize windows in the grid view" option, it is
crucial to me. 
However, it seems that in 6.0.4 it is buggy. If that checkbox is NOT ticket,
only windows from the current virtual desktop are shown in the overview,
windows on all other virtual desktops are hidden.

STEPS TO REPRODUCE
1. uncheck "organize windows in the grid view"
2. have multiple virtual desktops, e.g. I have 6, split over two rows
3. open windows on various virtual desktops, then switch to one
4. open the overview effect

OBSERVED RESULT
Only windows from the current virtual desktop are shown in the grid, other
virtual desktops are all empty

EXPECTED RESULT
All windows are shown

Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.8.8-300.fc40.x86_64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i5-8265U CPU @ 1.60GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: LENOVO
Product Name: 20NQS30W00
System Version: ThinkPad X390 Yoga

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

[frameworks-kglobalaccel] [Bug 486852] New: Global Keyboard Shortcut migration from Plasma 5 to Plasma 6 broken, leaves zombie entries

[Christian]

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

Bug ID: 486852
   Summary: Global Keyboard Shortcut migration from Plasma 5 to
Plasma 6 broken, leaves zombie entries
Classification: Frameworks and Libraries
   Product: frameworks-kglobalaccel
   Version: 6.1.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdelibs-b...@kde.org
  Reporter: k...@fuchsnet.ch
  Target Milestone: ---

SUMMARY
I upgraded to a new fedora version which brought Plasma / Frameworks / KDE 6.*
instead of 5.*, and I was noticing that all my custom global keyboard shortcuts
were broken, as in: they didn't trigger the action they were configured to.
Interestingly enough they were still listed under systemsettings in the
keyboard shortcuts, under the service for custom / personal keyboard shortcuts,
and trying to re-assign the key combination did lead to a warning that that
combination is already assigned.

STEPS TO REPRODUCE
1.  Have KDE Plasma, Frameworks etc. pp. 5.* 
2.  Have custom keyboard shorcuts
3.  Upgrade to Plasma, Frameworks etc. pp. 6.*

OBSERVED RESULT
Keyboard shorcuts are listed in settings, but they do not work (the action does
not trigger)

EXPECTED RESULT
Preferably they are migrated in a way so they work, but if that is not feasible
for whatever reason, then they should at least be cleaned out

Probably important sidenote: this is from X11 to X11, no wayland / switch
involved.

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.8.8-300.fc40.x86_64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i5-8265U CPU @ 1.60GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: LENOVO
Product Name: 20NQS30W00
System Version: ThinkPad X390 Yoga
ADDITIONAL INFORMATION

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

[frameworks-baloo] [Bug 486853] New: Baloo file extractor crashes a dozen times after updating to Plasma / KDE / Frameworks 6

[Christian]

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

Bug ID: 486853
   Summary: Baloo file extractor crashes a dozen times after
updating to Plasma / KDE / Frameworks 6
Classification: Frameworks and Libraries
   Product: frameworks-baloo
   Version: 6.1.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: Baloo File Daemon
  Assignee: baloo-bugs-n...@kde.org
  Reporter: k...@fuchsnet.ch
  Target Milestone: ---

Application: baloo_file_extractor (6.1.0)

Qt Version: 6.7.0
Frameworks Version: 6.1.0
Operating System: Linux 6.8.8-300.fc40.x86_64 x86_64
Windowing System: X11
Distribution: "Fedora Linux 40 (KDE Plasma)"
DrKonqi: 6.0.4 [CoredumpBackend]

-- Information about the crash:
After re-installing my laptop with Fedora 40 and putting my /home backup back 
(excluding the baloo folder under .local/share and excluding baloo config under
.config, as I epxected that to be problematic) baloo started re-indexing and
crashed a couple of dozen times in a short row.
I hope the backtrace is somewhat helpful in finding the root cause, else feel
free to get back to me if you need further information.

The crash can be reproduced every time.

-- Backtrace:
Application: Baloo-Dateiinfosammler (baloo_file_extractor), 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 9643]
[New LWP 9688]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/libexec/kf6/baloo_file_extractor'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7fc2120ab144 in __pthread_kill_implementation () from
/lib64/libc.so.6
[Current thread is 1 (Thread 0x7fc20e151f40 (LWP 9643))]
Cannot QML trace cores :(
[Current thread is 1 (Thread 0x7fc20e151f40 (LWP 9643))]

Thread 2 (Thread 0x7f8206c0 (LWP 9688)):
#0  0x7fc21211d72d in poll () from /lib64/libc.so.6
#1  0x7fc210d7c724 in g_main_context_iterate_unlocked.isra () from
/lib64/libglib-2.0.so.0
#2  0x7fc210d1cb03 in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#3  0x7fc212a7bf83 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /lib64/libQt6Core.so.6
#4  0x7fc2127a26b3 in
QEventLoop::exec(QFlags) () from
/lib64/libQt6Core.so.6
#5  0x7fc2128b402f in QThread::exec() () from /lib64/libQt6Core.so.6
#6  0x7fc21256faf1 in QDBusConnectionManager::run() () from
/lib64/libQt6DBus.so.6
#7  0x7fc21294f35c in QThreadPrivate::start(void*) () from
/lib64/libQt6Core.so.6
#8  0x7fc2120a91b7 in start_thread () from /lib64/libc.so.6
#9  0x7fc21212b39c in clone3 () from /lib64/libc.so.6

Thread 1 (Thread 0x7fc20e151f40 (LWP 9643)):
[KCrash Handler]
#4  0x7fc21280fd83 in QVariant::QVariant(QString const&) () from
/lib64/libQt6Core.so.6
#5  0x7fc211b44aac in standardDeclarationForNode(QTextHtmlParserNode
const&) () from /lib64/libQt6Gui.so.6
#6  0x7fc211b45bc2 in QTextHtmlParser::declarationsForNode(int) const ()
from /lib64/libQt6Gui.so.6
#7  0x7fc211b46830 in QTextHtmlParser::parseTag() () from
/lib64/libQt6Gui.so.6
#8  0x7fc211b46df0 in QTextHtmlParser::parse() () from
/lib64/libQt6Gui.so.6
#9  0x7fc211aeb2ea in QTextHtmlImporter::QTextHtmlImporter(QTextDocument*,
QString const&, QTextHtmlImporter::ImportMode, QTextDocument const*) () from
/lib64/libQt6Gui.so.6
#10 0x7fc211ad3f16 in QTextDocument::setHtml(QString const&) () from
/lib64/libQt6Gui.so.6
#11 0x7fc20e11fb7f in
KFileMetaData::MobiExtractor::extract(KFileMetaData::ExtractionResult*) () from
/usr/lib64/qt6/plugins/kf6/kfilemetadata/kfilemetadata_mobiextractor.so
#12 0x5606c85350cf in Baloo::App::index(Baloo::Transaction*, QString
const&, unsigned long long) ()
#13 0x5606c8536745 in Baloo::App::processNextFile() ()
#14 0x7fc2127fa3f4 in void doActivate(QObject*, int, void**) () from
/lib64/libQt6Core.so.6
#15 0x7fc212707496 in QSingleShotTimer::timerEvent(QTimerEvent*) () from
/lib64/libQt6Core.so.6
#16 0x7fc2127ebccf in QObject::event(QEvent*) () from
/lib64/libQt6Core.so.6
#17 0x7fc212795a99 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt6Core.so.6
#18 0x7fc21294d797 in QTimerInfoList::activateTimers() () from
/lib64/libQt6Core.so.6
#19 0x7fc212a7bdb9 in timerSourceDispatch(_GSource*, int (*)(void*), void*)
() from /lib64/libQt6Core.so.6
#20 0x7fc210d1b68c in g_main_context_dispatch_unlocked.lto_priv () from
/lib64/libglib-2.0.so.0
#21 0x7fc210d7c788 in g_main_context_iterate_unlocked.isra () from
/lib64/libglib-2.0.so

[frameworks-baloo] [Bug 486853] Baloo file extractor crashes a dozen times after updating to Plasma / KDE / Frameworks 6

[Christian]

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

--- Comment #2 from Christian (Fuchs)  ---
(In reply to tagwerk19 from comment #1)
> (In reply to Christian (Fuchs) from comment #0)
> > #5  0x7fc211b44aac in standardDeclarationForNode(QTextHtmlParserNode
> > const&) () from /lib64/libQt6Gui.so.6
> > #6  0x7fc211b45bc2 in QTextHtmlParser::declarationsForNode(int) const ()
> > from /lib64/libQt6Gui.so.6
> > #7  0x7fc211b46830 in QTextHtmlParser::parseTag() () from
> > /lib64/libQt6Gui.so.6
> > #8  0x7fc211b46df0 in QTextHtmlParser::parse() () from
> > /lib64/libQt6Gui.so.6
> > #9  0x7fc211aeb2ea in
> > QTextHtmlImporter::QTextHtmlImporter(QTextDocument*, QString const&,
> > QTextHtmlImporter::ImportMode, QTextDocument const*) () from
> > /lib64/libQt6Gui.so.6
> > #10 0x7fc211ad3f16 in QTextDocument::setHtml(QString const&) () from
> > /lib64/libQt6Gui.so.6
> > #11 0x7fc20e11fb7f in
> > KFileMetaData::MobiExtractor::extract(KFileMetaData::ExtractionResult*) ()
> > from /usr/lib64/qt6/plugins/kf6/kfilemetadata/kfilemetadata_mobiextractor.so
> It's looking like a "messed up" ebook (a .mobi with embedded HTML?). There's
> also Bug 475730 and, perhaps more usefully, Bug 475975...

Thanks for the links, I'll go subscribe to the latter. In an ideal world
though, a malformed file should not lead to baloo crashing, very visibly to the
end user as it spams the systray with a dozen of Dr. Konqi instances. If there
is malformed content produced by a third party library, there should be the
equivalent of a catch around that so it could fail on that file gracefully (and
potentially mark it to not re-index)

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

[Akonadi] [Bug 486871] New: Can't fetch caldav or carddav from Nextcloud in Fedora 40, driver error

[Christian]

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

Bug ID: 486871
   Summary: Can't fetch caldav or carddav from Nextcloud in Fedora
40, driver error
Classification: Frameworks and Libraries
   Product: Akonadi
   Version: 6.0.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: DAV Resource
  Assignee: kdepim-b...@kde.org
  Reporter: k...@fuchsnet.ch
CC: c...@carlschwan.eu
  Target Milestone: ---

SUMMARY
Since re-installing a fresh Fedora 40 after using Fedora 39, I am no longer
able to add my nextcloud calendar or addressbooks in akonadi. The error message
shown in the window is completely useless (driver error, on German, couldn't
get it to show it in English), on the console it's a bit more usefull, 

org.kde.pim.akonadiserver: Handler exception when handling command
FetchCollections on connection akonadi_davgroupware_resource_0 (0x560355340ab0)
: Hierarchical RID does not specify an existing collection
org.kde.pim.davresource: Unable to fetch collections 320 "Ungültige Antwort des
Treibers"

STEPS TO REPRODUCE
1. Install Fedora 40 with akonadi 6.0.2
2.  Try to add a nextcloud ressource, either via the built in Nextcloud setting
in the drop down or by specifying the URLs manually

OBSERVED RESULT
You get the above error


EXPECTED RESULT
It works

The same nextcloud instance works with other software, e.g. a still running KDE
5.* based kontact on my desktop box, davx on Android etc. 

Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.8.9-300.fc40.x86_64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i5-8265U CPU @ 1.60GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: LENOVO
Product Name: 20NQS30W00
System Version: ThinkPad X390 Yoga

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

[plasmashell] [Bug 486921] New: Days with a sublabel are oddly shifted up in grid view due to height calculation

[Christian]

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

Bug ID: 486921
   Summary: Days with a sublabel are oddly shifted up in grid view
due to height calculation
Classification: Plasma
   Product: plasmashell
   Version: 6.0.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Calendar
  Assignee: plasma-b...@kde.org
  Reporter: k...@fuchsnet.ch
  Target Milestone: 1.0

Created attachment 169398
  --> https://bugs.kde.org/attachment.cgi?id=169398&action=edit
Screenshot of current behaviour, misaligned (left), next to proposed aligned
behaviour (can be improved)

SUMMARY
Apparently in Plasma 6.* in the digital clock calender popup, days with
holidays now not only show a coloured dot, but also the name of that holiday as
a label.

Unfortunately these then have a different height than all the other items in
the grid, which makes them stick out like a sore spot.

Changing 

contentItem: Item {
// ColumnLayout makes scrolling too slow, so use anchors to position
labels

PlasmaComponents3.ToolTip.delay: Kirigami.Units.toolTipDelay
PlasmaComponents3.ToolTip.text: model.subLabel || ""
PlasmaComponents3.ToolTip.visible: !!model.subLabel &&
(Kirigami.Settings.isMobile ? dayStyle.pressed : dayStyle.hovered)

Kirigami.Heading {
id: label
anchors {
left: parent.left
right: parent.right
top: parent.top
// bottom: subDayLabel.top
bottom: parent.bottom + Kirigami.Units.smallSpacing
}

fixes that, but that is probably an ugly hack that might not work on all DPI /
resolution combinations, thus a more robust calculation would be nice.

STEPS TO REPRODUCE
1.  Have Plasma 6
2.  Have a digital clock
3.  Have the holiday plugin enabled
4. Be in a month with a public holiday of sorts
5. Click on the clock to make the popup pop up

OBSERVED RESULT
Grid is not well aligned, days with holidays stick out despite there being
plenty of space

EXPECTED RESULT
Grid is well aligned

Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.8.9-300.fc40.x86_64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i5-8265U CPU @ 1.60GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: LENOVO
Product Name: 20NQS30W00
System Version: ThinkPad X390 Yoga

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

[plasmashell] [Bug 486921] Days with a sublabel are oddly shifted up in grid view due to height calculation

[Christian]

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

--- Comment #1 from Christian (Fuchs)  ---
Somewhat related, and could be looked into as well when changing the layout:
https://bugs.kde.org/show_bug.cgi?id=470014

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

[plasmashell] [Bug 483390] Task Manager window previews hide almost immediately when moving from one task to another in almost all panel orientations and movement directions

[Christian]

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

Christian (Fuchs)  changed:

   What|Removed |Added

 CC||k...@fuchsnet.ch

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

[kontact] [Bug 487025] New: kmail systray click is broken in 6.* if opened through kontact instead of kmail

[Christian]

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

Bug ID: 487025
   Summary: kmail systray click is broken in 6.* if opened through
kontact instead of kmail
Classification: Applications
   Product: kontact
   Version: 6.0.2
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: mail
  Assignee: kdepim-b...@kde.org
  Reporter: k...@fuchsnet.ch
  Target Milestone: ---

SUMMARY
Kmail has an option to show a systray icon for unread mails.
Clicking on this icon used to (and is supposed to, I guess, see below) toggle
showing kmail if clicked.
This no longer works in Plasma 6 / with KDEPim 6 if and only if kmail was
started through kontact. It does work when starting kmail directly. It also
occasionally starts working again after closing kontact, opening kmail, closing
kmail, opening kontact.

STEPS TO REPRODUCE
1. Configure kmail to show a systray icon
2. Start kontact
3. Click the icon

OBSERVED RESULT
The kmail (or kontact) window should toggle  (minimize and un-minimize)

EXPECTED RESULT
Nothing happens on click

Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.0
Kernel Version: 6.8.9-300.fc40.x86_64 (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i5-8265U CPU @ 1.60GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: LENOVO
Product Name: 20NQS30W00
System Version: ThinkPad X390 Yoga

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

[plasmashell] [Bug 487026] New: Use symbolic icons for systray app if present

[Christian]

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

Bug ID: 487026
   Summary: Use symbolic icons for systray app if present
Classification: Plasma
   Product: plasmashell
   Version: 6.0.4
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: wishlist
  Priority: NOR
 Component: XembedSNIProxy
  Assignee: plasma-b...@kde.org
  Reporter: k...@fuchsnet.ch
CC: mate...@gmail.com
  Target Milestone: 1.0

SUMMARY
As per a discussion in the VDG group: 
I propose adding either an option  (or, as per Nate, just a new default) of
using the -symbolic icon for an app, if present.

Usecase: have icon themes / apps that want to support it by shipping a
-symbolic icon to follow our usually monochrome icons in systray.

Logic would basically be: when loading an icon, check if there is a -symbolic
suffixed version of that icon for that size, if yes: use that, if no: use the
requested icon.

Argument against hardcoding it: would override apps explicit wishes.
Argument against an option: it's an option, and it might not always work, thus
give users wrong expectations if not clearly worded  (e.g. should be [ ] use
monochrome icon if available, not [ ] use monochrome icon)

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

[Akonadi] [Bug 485132] DAV resource: invalid response from backend

[Christian]

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

Christian (Fuchs)  changed:

   What|Removed |Added

 CC||k...@fuchsnet.ch

--- Comment #5 from Christian (Fuchs)  ---
Potentially the same as https://bugs.kde.org/show_bug.cgi?id=486871, the error
message is indeed not helpful, but I got the same.
And I can confirm that the ressource is working with every other client,
including akonadi < 6.*, so this is not a bug in the ressource, but in akonadi.

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

[ark] [Bug 440663] Ark opens a new instance of Dolphin after compression/extraction via Dolphin

[Christian]

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

--- Comment #32 from Christian (Fuchs)  ---
(In reply to Luke Horwell from comment #31)

> Currently in 5.23.3 / Frameworks 5.88, there are similar instance-related
> bugs, and possibly causing confusion and/or may be related to this change:
> - When compressing a file, and the window is closed, Dolphin crashes and the
> compression doesn't complete.
> - When extracting a file, and is cancelled via notification, Dolphin
> continues to extract in the background.

Are there bug reports for these you could link? At least the first one sounds
critical enough to warrant a revert for now, and personally I think the first
one would also warrant raising the criticality.

Thanks in advance and kind regards

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

[dolphin] [Bug 440663] New Dolphin window or tab opened after compression/extraction when certain default options disabled

[Christian]

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

--- Comment #36 from Christian (Fuchs)  ---
(In reply to Nate Graham from comment #35)
> Looks like the bug was only half-fixed, indeed. When the "Open new folders
> in tabs" and "Show on Startup: Folder, tabs, and window state from last
> time" options are in use, everything is fine. When one or both are
> unchecked, the issue re-appears.

Is "everything is fine" with regards to opening a new tab / window only, or
does it also cover the cases Luke mentioned?  (Closing the dolphin window
aborting the extraction, cancelling via the notification not actually
cancelling the operation)

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

[dolphin] [Bug 440663] New Dolphin window or tab opened after compression/extraction when certain default options are disabled, or when the job is canceled, or when the Dolphin window that initiated i

[Christian]

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

--- Comment #43 from Christian (Fuchs)  ---
Since that merge request seems to mainly tackle the tabs: can we, for the
current branch, get the original change reverted so at least until a proper fix
is found people who don't have a very specific configuration won't get a new
dolphin window/tab every time they compress / uncompress something?

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

[plasmashell] [Bug 451267] Plasma crashed in WorkspaceScripting::Applet::writeConfig() after changing wallpaper using context menu item

[Christian]

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

Christian  changed:

   What|Removed |Added

 CC||christianmillona...@msn.com

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

[plasmashell] [Bug 451267] Plasma crashed in WorkspaceScripting::Applet::writeConfig() after changing wallpaper using context menu item

[Christian]

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

--- Comment #7 from Christian  ---
Created attachment 148540
  --> https://bugs.kde.org/attachment.cgi?id=148540&action=edit
New crash information added by DrKonqi

plasmashell (5.24.4) using Qt 5.15.3

- What I was doing when the application crashed:

I changed the wallpaper through Dolphin.

- Unusual behavior I noticed:

I changed the wallpaper through Dolphin because I couldn't open the context
menu on my main screen. This happens when connected to my Dell D600 dock with
the latest DisplayLink driver installed.

-- Backtrace (Reduced):
#6  0x563d5daf5006 in qobject_cast (object=) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:519
#7  QtPrivate::QVariantValueHelper::object (v=...) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qvariant.h:753
#8  QtPrivate::ObjectInvoker, QVariant
const&, QObject*>::invoke (a=...) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qvariant.h:107
#9  qvariant_cast (v=...) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qvariant.h:879
#10 QVariant::value (this=0x7fffbb878a70) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qvariant.h:367

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

[korganizer] [Bug 452507] Item details no longer shown in sidebar

[Christian]

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

Christian (Fuchs)  changed:

   What|Removed |Added

 CC||k...@fuchsnet.ch

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

[konversation] [Bug 453816] konversation: show tray ico

[Christian]

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

Christian (Fuchs)  changed:

   What|Removed |Added

 CC||k...@fuchsnet.ch
 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #1 from Christian (Fuchs)  ---
That feature has been available for a very long time, 
Settings -> Configure Konversation -> Behaviour -> General Behaviour   [x]
Enable System Tray. 

In addition you can also configure konversation to mark the taskbar entry for
certain events, e.g. a highlight, which makes this visible without needing a
tray icon.

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

[konversation] [Bug 453816] konversation: show tray ico

[Christian]

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

--- Comment #3 from Christian (Fuchs)  ---
(In reply to Elmar Stellnberger (AT/K) from comment #2)
> I have tested it. Konversation does in deed show a tray icon with these
> settings. However if you close the main window the program will terminate.

Not reproducible, here when I quit the app when systray is enabled there is
even a dialogue specifically telling me that konversation will keep running in
the systray, and it does that, as expected.

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

[frameworks-plasma] [Bug 452555] New: PlasmaComponents.Highlight (e.g. in LegacyKickoff) invisible since update

[Christian]

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

Bug ID: 452555
   Summary: PlasmaComponents.Highlight (e.g. in LegacyKickoff)
invisible since update
   Product: frameworks-plasma
   Version: 5.93.0
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: components
  Assignee: plasma-b...@kde.org
  Reporter: k...@fuchsnet.ch
CC: m...@ratijas.tk, notm...@gmail.com
  Target Milestone: ---

Created attachment 148122
  --> https://bugs.kde.org/attachment.cgi?id=148122&action=edit
screenshot of issue, left correct, right wrong, both highlight the same item
(konsole)

Filing as per discussion in the VDG group: 

since upgrading to KF 5.93  (could have been 92, maybe I skipped a version) the 
PlasmaComponents.Highlight  used by LegacyKickoff
(https://store.kde.org/p/1468103) is invisible. 

It is marked as deprecated but still available in the api docs, so this might
also hit other products.

STEPS TO REPRODUCE
1. Install https://store.kde.org/p/1468103
2. Open
3. Hover a list item

OBSERVED RESULT
Highlight overlay not visible (see screenshot)

EXPECTED RESULT
Highlight overlay visible

Betriebssystem: Fedora Linux 36
KDE-Plasma-Version: 5.24.4
KDE-Frameworks-Version: 5.93.0
Qt-Version: 5.15.3
Kernel-Version: 5.17.2-300.fc36.x86_64 (64-bit)
Grafik-Plattform: X11

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

[kwin] [Bug 455783] New: Regression (since pre 5.25): in present window, windows on a second screen can't be chosen by keyboard

[Christian]

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

Bug ID: 455783
   Summary: Regression (since pre 5.25): in present window,
windows on a second screen can't be chosen by keyboard
   Product: kwin
   Version: 5.25.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: effects-present-windows
  Assignee: kwin-bugs-n...@kde.org
  Reporter: k...@fuchsnet.ch
  Target Milestone: ---

SUMMARY

While the filter / search has now been fixed to filter windows on all monitors,
you can only switch through windows on your current screen with the keyboard

STEPS TO REPRODUCE
1. Have more than one screen
2. Place some on the currently not active one
3. Start present window effect and try to select that window with the keyboard

OBSERVED RESULT
You can't, you can only switch between windows on your current screen

EXPECTED RESULT
You can choose all windows with your keyboard

Operating System: Fedora Linux 36
KDE Plasma Version: 5.25.1
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.3
Kernel Version: 5.18.5-200.fc36.x86_64 (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 31.2 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3070/PCIe/SSE2

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

[kwin] [Bug 455786] New: Filter isn't reset after effect ends, thus e.g. breaking it for choosing grouped windows

[Christian]

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

Bug ID: 455786
   Summary: Filter isn't reset after effect ends, thus e.g.
breaking it for choosing grouped windows
   Product: kwin
   Version: 5.25.1
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: effects-present-windows
  Assignee: kwin-bugs-n...@kde.org
  Reporter: k...@fuchsnet.ch
  Target Milestone: ---

SUMMARY
There is a filter function which filters windows based on its title.
Unfortunately it is not cleared after the effect ends.

STEPS TO REPRODUCE
1. Open present window effect
2. Type something in the filter, e.g. firefox
3. Close the effect
4. Click on grouped tasks in the taskmanager, e.g. if you have two console
windows open

OBSERVED RESULT
You can't choose between the two console windows, since the filter on "firefox"
is still active

EXPECTED RESULT
Filter is cleared, effect works as expected

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 36
KDE Plasma Version: 5.25.1
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.3
Kernel Version: 5.18.5-200.fc36.x86_64 (64-bit)
Graphics Platform: X11
Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor
Memory: 31.2 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3070/PCIe/SSE2

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

[kwin] [Bug 455786] Filter isn't reset after effect ends, thus e.g. breaking it for choosing grouped windows

[Christian]

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

--- Comment #1 from Christian (Fuchs)  ---
A workaround (or maybe even fix) is to simply

--- main.qml.orig   2022-06-22 14:55:29.527338810 +0200
+++ main.qml2022-06-22 14:54:58.916537416 +0200
@@ -28,6 +28,7 @@
 function start() {
 container.animationEnabled = true;
 container.organized = true;
+effect.searchText = ""
 }

 function stop() {


but since I don't know what else might trigger that effect, this might come
with side effects. Imho the correct behaviour, UX wise, would be to always
clear the filter when the effect is freshly started though, no matter what
triggered this. I'll poke VDG folk about it.

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

[kwin] [Bug 455786] Filter isn't reset after effect ends, thus e.g. breaking it for choosing grouped windows

[Christian]

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

--- Comment #2 from Christian (Fuchs)  ---
Created attachment 150049
  --> https://bugs.kde.org/attachment.cgi?id=150049&action=edit
Current behaviour, notice that on click on the taskmanager the user gets
presented with a blurred screen of nothing

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

[kwin] [Bug 455786] Filter isn't reset after effect ends, thus e.g. breaking it for choosing grouped windows

[Christian]

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

--- Comment #3 from Christian (Fuchs)  ---
Created attachment 150050
  --> https://bugs.kde.org/attachment.cgi?id=150050&action=edit
Suggested behaviour, effect works as expected on re-activating it

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

[kwin] [Bug 455786] Filter isn't reset after effect ends, thus e.g. breaking it for choosing grouped windows

[Christian]

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

--- Comment #5 from Christian (Fuchs)  ---
Oh, aw, and I was currently setting up kdesrc-build, next time, then. 

Thanks for the heads up

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

[kwin] [Bug 455786] Filter isn't reset after effect ends, thus e.g. breaking it for choosing grouped windows

[Christian]

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

--- Comment #7 from Christian (Fuchs)  ---
(In reply to Niklas Stephanblome from comment #6)
> (In reply to Christian (Fuchs) from comment #5)
> > Oh, aw, and I was currently setting up kdesrc-build, next time, then. 
> > 
> > Thanks for the heads up
> 
> Didn't see this bug report earlier, just noticed that it wasn't clearing
> while working on it yesterday, so I thought I might aswell fix it with one
> line.

That's perfectly fine, I'm sure I'll find other simple things to start work on. 

Sidenote: probably less simple and thus not for me, but  probably also a
candidate for the current effort, if not fixed already:
https://bugs.kde.org/show_bug.cgi?id=455783

Thanks for your work :)

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

[kwin] [Bug 454842] Window highlight effect is now rather faint and easy to miss

[Christian]

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

--- Comment #8 from Christian (Fuchs)  ---
(In reply to Niklas Stephanblome from comment #6)
> It doesn't have to be THAT huge as in your 2nd attachement but I do agree
> that it could be bigger.

The problem on an in-between is that it will most likely go right through the
window title label. 
If we change it, I guess it either has to just not, or also include the window
label (which imho is correct, since that label is part of what the user
selected. If you e.g. select a file in a file manager, the file name is also
part of the selection highlight). 

But maybe that whole label could be a bit repositioned.

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

[kwin] [Bug 454842] Window highlight effect is now rather faint and easy to miss

[Christian]

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

--- Comment #10 from Christian (Fuchs)  ---
(In reply to Niklas Stephanblome from comment #9)
> > The problem on an in-between is that it will most likely go right through
> > the window title label. 
> > If we change it, I guess it either has to just not, or also include the
> > window label 
> Or we could leave the highlighting box as it is and instead make all
> unselected windows darker. Then it would be very noticable but still look
> good. What do you think?

Hm, sorry but imho that would be the worse solution for mainly two reasons: 

1) it would not be consistent, the highlight is sort of the same that we use in
lists and it looks similar enough to non-QML qt app selections
2) The darker windows part was discussed in a different bug report about the
desktop grid, where in the past the non-active ones were darker. People
argumented, imo correctly so, that in an overview you should be able to easily
"read" all elements, and making some elements darker works a bit against that. 

Note that my above patch is a quick and dirty solution, it could probably be
fine-tuned, it could be done in a way so that there is still a margin between
windows  (which is what currently makes it look bad) and maybe the label could
be re-thought and -positioned, then I think a bigger selection box would solve
the problem and look nice.

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

[kwin] [Bug 455783] Regression (since pre 5.25): in present window, windows on a second screen can't be chosen by keyboard

[Christian]

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

--- Comment #3 from Christian (Fuchs)  ---
(In reply to Carlos Colorado from comment #2)
> Also note that "the search bar" is not clean up when the effect is launched. 
> The previous search (and filtering) would be still active but perhaps that's
> a second bug report?

Yes, see https://bugs.kde.org/show_bug.cgi?id=455786

I reported a couple of bugs since the new effect has plenty, but it's prefered
to have one report per problem.
The problem you mention is known and should be fixed whenever that other merge
request gets merged and lands in a release, if you need a temporary workaround,
see the bug report linked above, it's a one-liner.

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