Bug#1136555: plasma-workspace uses pidof but does not depend on procps

Aurélien COUDERC <[email protected]>
Newsgroups gmane.linux.debian.devel.bugs.general,gmane.linux.debian.devel.qt-kde
Message-ID <2195645.KlZ2vcFHjT@grummly>
Le jeudi 14 mai 2026, 01:30:45 heure d’été d’Europe centrale Gioele Barabucci a écrit :

> Dear maintainer(s) of plasma-workspace,

Hi,

> it appears that plasma-workspace uses `pidof` in its testsuite, or that
> at least one of its binary packages uses `pidof` at runtime.
> Historically, `pidof` was provided by the Essential package
> `sysvinit-tools`, making an explicit dependency unnecessary. However
> `pidof` will soon be moved to `procps` and will no longer be part of
> the Essential set.

> It is believed that plasma-workspace uses `pidof` due to the following
> code snippets:
> 
> ```
> path: plasma-workspace_4:6.5.4-3/appiumtests/applets/cameraindicatortest.py
>         cls.driver = webdriver.Remote(command_executor=f'http://127.0.0.1:{os.getenv("FLASK_PORT", "4723")}', options=options)
>         cls.pipewire_already_running_before_test = subprocess.Popen(["pidof", "pipewire"]).wait() == 0
>     def tearDown(self) -> None:

we don’t currently run appiumtests (appium not packaged in Debian) so closing.


Happy hacking,
--
Aurélien
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.