Bug#1072344: kio-extras-data: package is architecture all but contains architecture dependent service file.
Package: kio-extras-data
Version: 4:23.08.4-1
Severity: normal
X-Debbugs-Cc: buebelacker@mailbox.org
Dear Maintainer,
I upgraded lately an i386 installation to Bookworm and tried to
access files on a connected Android phone.
Unfortunately there was not visible response from the UI when
clicking in the connected devices menu.
This was shown in "journal --user":
dbus-daemon[1030]: [session uid=1000 pid=1030] Activating service name='org.kde.kmtpd5' requested by ':1.82' (uid=1000 pid=2985 comm="/lib/i386-linux-gnu/libexec/kf5/kioslave5 /usr/lib")
dbus-daemon[1030]: [session uid=1000 pid=1030] Activated service 'org.kde.kmtpd5' failed: Failed to execute program org.kde.kmtpd5: No such file or directory
And the service file contains this:
$ cat /usr/share/dbus-1/services/org.kde.kmtpd5.service
[D-BUS Service]
Name=org.kde.kmtpd5
Exec=/usr/lib/x86_64-linux-gnu/libexec/kf5/kiod5
But the executable is in a i386 directory instead of x86_64:
$ dpkg -S kf5/kiod5
kio: /usr/lib/i386-linux-gnu/libexec/kf5/kiod5
Unfortunately this seems to be the case for Bookworm/stable and Trixie/testing.
If I understand it right, because of kio-extras-data being "Architecture: all",
this package got build at amd64 but used at all archs?
Would moving the file "org.kde.kmtpd5.service" from
package kio-extras-data to kio-extras already be sufficient?
Kind regards,
Bernhard
-- System Information:
Debian Release: trixie/sid
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 6.7.12-686-pae (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_SOFTLOCKUP
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages kio-extras-data depends on:
ii perl 5.38.2-4
kio-extras-data recommends no packages.
kio-extras-data suggests no packages.
-- no debconf information
Reply to: