Bug#951523: dolphin: installing dolphin on xfce is missing a kde component for file transfer

2020-02-18 Thread Jonah Brüchert
As said, you only need the plasma-workspace package, not plasma-desktop. 
Removing packages after installing plasma-desktop will not lead to a different 
conclusion, because plasma-workspace contains the binary you seem to need.

On 18 February 2020 19:45:29 CET, Schrotty  wrote:
>Hi,
>
>yes, as I wrote in my original post, that will "fix" the problem of the
>missing dialog. But it pulls so much ridiculous dependencies which are
>taking 1GB of diskspace.
>
>I first tried to add package after package to see which one solves the
>problem, without select the big "base" package. But I did not manage.
>
>In a 2nd attempt I went the opposite way: Installing the plasma-desktop
>monster and starting to remove packages. So far I have eliminated the
>following packages:
>- plasma-discover
>- plasma-framework
>- plasma-desktop-data
>- plasma-pa
>
>
>Mrs. Spammy and Mrs Schrotty
>schr...@coole-files.de
>
>On 2/18/20 7:29 PM, Jonah Brüchert wrote:
>> [disclaimer: I'm not the package maintainer]
>>
>> Hi,
>>
>> kuiserver is part of the plasma-workspace package, installing it
>could
>> probably fix the problem.
>>
>>> Package: dolphin
>>> Version: 4:18.08.0-1
>>> Severity: normal
>>>
>>> Dear Maintainer,
>>>
>>> Installing dolpin using xfce as desktop environment on debian 10.3.
>>>
>>> Copying files do NOT show the file transfer dialog. So you never
>know
>>> when it is done. This is particular bad when copying to a slow USB
>>> stick. As the stick might be removed before the transfer is
>finished,
>>> corrupting the file system
>>> It seems the problem has been also detected already with Manjaro:
>>>
>https://forum.manjaro.org/t/bug-kde-applications-do-not-pull-in-kuiserver-which-now-is-in-plasma-workspace/69675
>>>
>>>
>>> Unfortunatlly there is no kuiserver package in debian.
>>> Installing the complete plasma-desktop as a workaround pulls in a
>lot
>>> of dependencies filling 1GB of diskspace. Thus only adding this as a
>>> dependency might not be the best idea. But I could not figure out
>>> which packet is acctually needed.
>>>
>>>
>>>
>>> -- System Information:
>>> Debian Release: 10.3
>>>    APT prefers stable-updates
>>>    APT policy: (500, 'stable-updates'), (500, 'stable')
>>> Architecture: amd64 (x86_64)
>>>
>>> Kernel: Linux 5.4.0-0.bpo.3-amd64 (SMP w/4 CPU cores)
>>> Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
>>> Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8),
>>> LANGUAGE=en_US:en (charmap=UTF-8)
>>> Shell: /bin/sh linked to /usr/bin/dash
>>> Init: systemd (via /run/systemd/system)
>>> LSM: AppArmor: enabled
>>>
>>> Versions of packages dolphin depends on:
>>> ii  baloo-kf5  5.54.0-1
>>> ii  kinit  5.54.0-1
>>> ii  kio    5.54.1-1
>>> ii  libc6  2.28-10
>>> ii  libdolphinvcs5 4:18.08.0-1
>>> ii  libkf5baloo5   5.54.0-1
>>> ii  libkf5baloowidgets5    4:18.08.1-1
>>> ii  libkf5bookmarks5   5.54.0-1
>>> ii  libkf5codecs5  5.54.0-1
>>> ii  libkf5completion5  5.54.0-1
>>> ii  libkf5configcore5  5.54.0-1+deb10u1
>>> ii  libkf5configgui5   5.54.0-1+deb10u1
>>> ii  libkf5configwidgets5   5.54.0-1
>>> ii  libkf5coreaddons5  5.54.0-1
>>> ii  libkf5crash5   5.54.0-1
>>> ii  libkf5dbusaddons5  5.54.0-1
>>> ii  libkf5filemetadata3    5.54.0-1
>>> ii  libkf5i18n5    5.54.0-1
>>> ii  libkf5iconthemes5  5.54.0-1
>>> ii  libkf5itemviews5   5.54.0-1
>>> ii  libkf5jobwidgets5  5.54.0-1
>>> ii  libkf5kcmutils5    5.54.0-1
>>> ii  libkf5kiocore5 5.54.1-1
>>> ii  libkf5kiofilewidgets5  5.54.1-1
>>> ii  libkf5kiowidgets5  5.54.1-1
>>> ii  libkf5newstuff5    5.54.0-2
>>> ii  libkf5notifications5   5.54.0-1
>>> ii  libkf5parts5   5.54.0-1
>>> ii  libkf5service-bin  5.54.0-1
>>> ii  libkf5service5 5.54.0-1
>>> ii  libkf5solid5   5.54.0-1
>>> ii  libkf5textwidgets5 5.54.0-1
>>> ii  libkf5widgetsaddons5   5.54.0-1
>>> ii  libkf5xmlgui5  5.54.0-1
>>> ii  libphonon4qt5-4    4:4.10.2-1
>>> ii  libqt5core5a   5.11.3+dfsg1-1+deb10u3
>>> ii  libqt5dbus5    5.11.3+dfsg1-1+deb10u3
>>> ii  libqt5gui5 5.11.3+dfsg1-1+deb10u3
>>> ii  libqt5widgets5 5.11.3+dfsg1-1+deb10u3
>>> ii  libqt5xml5 5.11.3+dfsg1-1+deb10u3
>>> ii  libstdc++6 8.3.0-6
>>> ii  phonon4qt5 4:4.10.2-1
>>>
>>> Versions of packages dolphin recommends:
>>> ii  kimageformat-plugins  5.54.0-1
>>> ii  kio-extras    4:18.08.3-1
>>> ii  ruby  1:2.5.1
>>>
>>> Versions of packages dolphin suggests:
>>> pn  dolphin-plugins  
>>>
>>> -- no debconf information
>>>
>>


Bug#951523: dolphin: installing dolphin on xfce is missing a kde component for file transfer

2020-02-18 Thread Jonah Brüchert

[disclaimer: I'm not the package maintainer]

Hi,

kuiserver is part of the plasma-workspace package, installing it could
probably fix the problem.


Package: dolphin
Version: 4:18.08.0-1
Severity: normal

Dear Maintainer,

Installing dolpin using xfce as desktop environment on debian 10.3.

Copying files do NOT show the file transfer dialog. So you never know when it 
is done. This is particular bad when copying to a slow USB stick. As the stick 
might be removed before the transfer is finished, corrupting the file system
It seems the problem has been also detected already with Manjaro: 
https://forum.manjaro.org/t/bug-kde-applications-do-not-pull-in-kuiserver-which-now-is-in-plasma-workspace/69675

Unfortunatlly there is no kuiserver package in debian.
Installing the complete plasma-desktop as a workaround pulls in a lot of 
dependencies filling 1GB of diskspace. Thus only adding this as a dependency 
might not be the best idea. But I could not figure out which packet is 
acctually needed.



-- System Information:
Debian Release: 10.3
   APT prefers stable-updates
   APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.4.0-0.bpo.3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dolphin depends on:
ii  baloo-kf5  5.54.0-1
ii  kinit  5.54.0-1
ii  kio5.54.1-1
ii  libc6  2.28-10
ii  libdolphinvcs5 4:18.08.0-1
ii  libkf5baloo5   5.54.0-1
ii  libkf5baloowidgets54:18.08.1-1
ii  libkf5bookmarks5   5.54.0-1
ii  libkf5codecs5  5.54.0-1
ii  libkf5completion5  5.54.0-1
ii  libkf5configcore5  5.54.0-1+deb10u1
ii  libkf5configgui5   5.54.0-1+deb10u1
ii  libkf5configwidgets5   5.54.0-1
ii  libkf5coreaddons5  5.54.0-1
ii  libkf5crash5   5.54.0-1
ii  libkf5dbusaddons5  5.54.0-1
ii  libkf5filemetadata35.54.0-1
ii  libkf5i18n55.54.0-1
ii  libkf5iconthemes5  5.54.0-1
ii  libkf5itemviews5   5.54.0-1
ii  libkf5jobwidgets5  5.54.0-1
ii  libkf5kcmutils55.54.0-1
ii  libkf5kiocore5 5.54.1-1
ii  libkf5kiofilewidgets5  5.54.1-1
ii  libkf5kiowidgets5  5.54.1-1
ii  libkf5newstuff55.54.0-2
ii  libkf5notifications5   5.54.0-1
ii  libkf5parts5   5.54.0-1
ii  libkf5service-bin  5.54.0-1
ii  libkf5service5 5.54.0-1
ii  libkf5solid5   5.54.0-1
ii  libkf5textwidgets5 5.54.0-1
ii  libkf5widgetsaddons5   5.54.0-1
ii  libkf5xmlgui5  5.54.0-1
ii  libphonon4qt5-44:4.10.2-1
ii  libqt5core5a   5.11.3+dfsg1-1+deb10u3
ii  libqt5dbus55.11.3+dfsg1-1+deb10u3
ii  libqt5gui5 5.11.3+dfsg1-1+deb10u3
ii  libqt5widgets5 5.11.3+dfsg1-1+deb10u3
ii  libqt5xml5 5.11.3+dfsg1-1+deb10u3
ii  libstdc++6 8.3.0-6
ii  phonon4qt5 4:4.10.2-1

Versions of packages dolphin recommends:
ii  kimageformat-plugins  5.54.0-1
ii  kio-extras4:18.08.3-1
ii  ruby  1:2.5.1

Versions of packages dolphin suggests:
pn  dolphin-plugins  

-- no debconf information





Bug#944860: udevadm trigger fails in chroot

2019-11-16 Thread Jonah Brüchert

Thanks for looking into the issue.


Can you be more specific how you setup your chroot so we have a chance
to reproduce the problem?


The exact setup is a little more complicated.

The chroot is created using debos, which if I remember correctly uses a
chroot inside qemu if that's relevent.

The exact command is `./bin/debos-docker -t variant:plasma-mobile
halium.yml`, ran inside the following git repository:
https://gitlab.com/debian-pm/tools/rootfs-builder-debos.

Whether debos-docker or a normal debos package / binary is used should
not matter, since the build process always happens inside a virtual machine.

After slightly looking into the debos source code it seems also possible
that it uses a systemd-spawn container in some cases
(https://github.com/go-debos/debos/blob/2764eed783b1b0ffb5d09f796338f09a4e2594b6/commands.go#L15)

The ci log can be found here in case useful:
https://travis-ci.com/debian-pm-tools/rootfs-builder-debos/jobs/257249532#L7353.


As reduced test case the following debos recipe could be used to save
some time:

`debos testcase.yml --debug-shell`


testcase.yml:

```

architecture: amd64

actions:
  - action: debootstrap
    suite: unstable
    components:
  - main
    mirror: https://deb.debian.org/debian
    variant: minbase

  - action: apt
    packages: [ udisks2 ]

```