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

            Bug ID: 527287
           Summary: systemd-sysext should be exempted from triggering the
                    "new device plugged in"-dialog in the system tray
    Classification: Frameworks and Libraries
           Product: frameworks-solid
      Version First unspecified
       Reported In:
          Platform: Aurora Linux
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected], [email protected]
  Target Milestone: ---

DESCRIPTION
Plasma has this really great feature where this dialog in the system tray shows
up as soon as a device like a usb flash drive is plugged in so you can do
things like browsing it with dolphin, mounting and things of that nature.

STEPS TO REPRODUCE
1. Build/acquire a systemd system extension (it needs to be a .raw file like an
erofs image and not a directory or else you can't reproduce it)
Inspect the raw file first if you use the one I provided :) (it only has the
bare minimum metadata)

sudo systemd-dissect --mtree path/to/example.raw

2. copy the raw file into /run/extensions or other supported paths

(3. run systemd-sysext to verify it was actually recognized)

4. run sudo systemd-sysext merge

5. run sudo systemd-sysext refresh (you can run this as often as you'd like,
the dialog will always show up)

OBSERVED RESULT
The dialog in the system tray shows up with no new device to list and may
confuse users who are not super familiar with the underlying technologies of
their system.

This can be a little bit frustrating as the dialog also steals the window focus
and may interrupt what you are currently doing.

EXPECTED RESULT
The dialog doesn't show up as system extensions are essentially just another
way of installing software and not what I imagine is the intended use case of
this dialog here of showing some kind of device.

I'm not sure what a good way would be to exempt/differentiate sysexts here,
maybe using the sysext source what is displayed in findmnt?

findmnt --source=sysext

TARGET SOURCE FSTYPE  OPTIONS
/usr   sysext overlay
ro,nodev,relatime,seclabel,lowerdir=/run/systemd/sysext/meta/usr:/run/systemd/sysext/extensions/example/usr:/usr,redirect_dir=on

SOFTWARE/OS VERSIONS
Operating System: Aurora 45
KDE Plasma Version: 6.8.80
KDE Frameworks Version: 6.32.0
Qt Version: 6.11.2

ADDITIONAL INFORMATION

If you don't want to use the raw file from me then you can make your own sysext
using erofs images for testing:

mkdir -p ~/example/usr/lib/extension-release.d
echo "ID=_any" >
~/example/usr/lib/extension-release.d/extension-release.example
mkfs.erofs --all-root example.raw ~/example

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

Reply via email to