#1104667 kde-plasma-desktop: KDE desktop: Launching applications from the start menu fails for section Games and Found objects

Package:
kde-plasma-desktop
Source:
kde-plasma-desktop
Description:
KDE Plasma Desktop and minimal set of applications
Submitter:
Adrian Kiess (adrian)
Date:
2025-05-29 18:43:01 UTC
Severity:
normal
#1104667#5
Date:
2025-05-04 08:26:00 UTC
From:
To:
Dear Maintainer,

   * What led up to the situation?
     Switching to KDE desktop for primary usage on Debian/testing
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
     Try to launch application through the start menu for sections Games and
Found objects (last entry in the menu)
   * What was the outcome of this action?
     Notification: Impossible de trouver le programme « JuliaSet.sh ».
   * What outcome did you expect instead?
     Launch the application successfully, as it is possible with all other
program sections in the start menu

Thank you!

Sincerely,

Adrian Kiess

#1104667#10
Date:
2025-05-21 14:06:37 UTC
From:
To:
Dear Maintainer,

this described bug seems to happen only on Wayland.

I also launched KDE Plasma 6.3 on Debian/testing on Xorg, where the
execution of applications from Games or the last category do work!

I also already created an all new guest user with newly created home
folder, with which the problem on Wayland persists.

Thank you for your attention.

I also noticed this bug already in the #debian-next channel on OFTC IRC,
already once.

Adrian Kiess

#1104667#15
Date:
2025-05-22 05:19:56 UTC
From:
To:
Dear Maintainer,

I queried the Internet, to my reported problem.

The bug may arouse because launching the Plasma Wayland session through
GDM3 with WaylandEnable=true in the [daemons] stanza.

It looks like, the path names /usr/games and ~/bin are missing from PATH
environment variable.

I checked zsh, bash and dash: When I launch a shell session, above path
names are part of the PATH variable.

Thank you.

Adrian Kiess

#1104667#20
Date:
2025-05-29 18:36:25 UTC
From:
To:
Dear Maintainer,

I switched my display manager from GDM3 to SDDM — which fixes my
described problem.

Problem resides when using GDM3.

Thank you.

Adrian Kiess