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

            Bug ID: 523053
           Summary: Single-clicking (selecting) an icon in Folder View
                    intermittently disables KRunner invocation via desktop
                    typing, without changing the persisted useTypeAhead
                    config value
    Classification: Plasma
           Product: plasmashell
      Version First 6.7.1
       Reported In:
          Platform: Fedora RPMs
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: Application Dashboard widget
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: 1.0

Component: Folder View / Desktop Containment (plasma-org.kde.plasma.folder)

Version: Plasma 6.7.1

OS: Fedora 44, Wayland session

Summary of the bug:

On Plasma 6.7.1, typing on an empty desktop is supposed to invoke KRunner,
governed by the useTypeAhead boolean under each Folder View applet's
[Configuration][General] group in plasma-org.kde.plasma.desktop-appletsrc
(default false). Instead, typing intermittently triggers Folder View's icon
type-ahead (jump-to-matching-icon) behavior instead of opening KRunner — even
though useTypeAhead=false is correctly set and persisted on disk at all times,
before and after the bug occurs.

Steps to reproduce:

  1.  Confirm baseline: on a freshly booted session, type on the empty desktop
— KRunner opens correctly.
  2.  Single-click any desktop icon (select only, do not launch it).
  3.  Type on the empty desktop again.

Expected result: KRunner opens, as in step 1.

Actual result: Folder View's type-ahead activates instead (selection jumps to a
matching icon), even though the on-disk useTypeAhead value is unchanged and
still false.

Additional observations:

 -   Reproduced with multiple different icons/launchers including ones with
standard well-formed .desktop files — not specific to any one file or its
contents.
 -   Reproduced on both screens independently (dual-4K setup, scale 1.75), and
also when booting single-monitor (right screen only).
 -   The bug is silent: journalctl --user -f shows no log entry at the moment
the break occurs. (One log line, Final member StackingOrder is overridden in
class QQmlDMAbstractItemModelData, was suspected as a signature at one point,
but testing showed it only appears on actually launching an application via
double-click, not on the single-click selection that triggers the bug — it is
unrelated noise.)
 -   Config on disk (~/.config/plasma-org.kde.plasma.desktop-appletsrc) was
checked repeatedly during bug episodes and always shows useTypeAhead=false
correctly persisted for all Folder View applets. This suggests the bug is a
runtime state issue (e.g. the Folder View QML item-model delegate not correctly
re-applying the config-bound property when the model/delegate is recreated on
selection) rather than a config persistence issue.
 -   Ruled out as causes: kconf_update re-firing, config file sync/permissions,
krunner migration scripts, Plasma session restore mode, wallpaper slideshow
timers, idle time/boot delay, KRunner itself being unresponsive (confirmed
alive via qdbus org.kde.krunner /App display during an active bug episode).
 -   No crash, coredump, or plasmashell restart coincides with any occurrence.

Workaround in use: Binding a global shortcut via KWin (kwriteconfig6 --file
kglobalshortcutsrc ... / System Settings → Shortcuts → Custom Shortcuts) to
launch a specific application directly, bypassing KRunner and the
desktop-typing path entirely. This avoids the bug but doesn't address the
underlying Folder View state issue.

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

Reply via email to