Bug 2780

Created attachment 2773 [details]
selected dbus, systemd and journal info from Stretch host easystreet

Created attachment 2774 [details]
dmesg from Stretch host easystreet

Attachment 2772 [details] (comment 0) omitted the following:
ii  udisks2	2.1.8-1		amd64	D-Bus service to access and manipulate storage devices

It's strange. I tried to reproduce the problem on my test notebook - the current status of Debian Stretch, TDE 14.0.5~pre (tdelibs with a few patches in connection with bug 2748) - after inserting the usb key, the disc notification window opens. And mount / umount is done properly (using udisks2).

It seems that exploring the problem will be more complicated than I hoped :(

Did you try starting with only tdebase-trinity on top of APT::Install-Recommends "0"; APT::Install-Suggests "0";?

I've spent several hours since comment 5 trying to find any existing installation here on which this bug does not exist. On 1 Jessie, 1 Mageia 5, 3 Stretch, 3 openSUSE Tumbleweed and 5 openSUSE Leap 42.1/42.2/42.3 installations across 4 hosts (big31, big41, gx62b, k8mmv), none with 14.0.5 or 14.0.4 notify, while all 5 with KDE3, and all 3 with Plasma, notify. None of the KDE3 provide any systemtray object to facilitate safe removal or ejection, while all KDE3 produce a failure to eject error message accompanying the unmount success message for USB devices, when safe removal is selected from Konq.

Host easystreet of comment 0 was not my machine. It went back to the hands of its owner the day after comment 5. Before its return, I did an upgrade from openSUSE 13.1/KDE3 to openSUSE 42.2. The result of that did include a systemtray object to facilitate safe removal or ejection. The only way I've encountered 100% satisfactory/expected notification and device removal results since filing this has been in openSUSE Tumbleweed using Plasma5. In all these tests, dmesg has reliably indicated attachment/insertion of the removable media.

Host easystreet has AMD chipset. Host k8mmv has VIA chipset. All others have Intel CPUs and chipsets, one with ATI video, another with GeForce.

Now, I did another test on another test machine with Stretch - the notification was displayed. However, wrongly for both the partition and the disk itself.

It is a fact that both machines I tested were updated from earlier releases of Debian.

Most, maybe all, of my Stretch installations, began as minimal Jessies. Always in openSUSE, onto a minimal X with 'solver.onlyRequires = true' in /etc/zypp/zypp.conf, sufficient to run IceWM and no other WM or DE besides the required TWM, trinity-tdebase was installed, and trinity-desktop was not installed. Similarly with Stretch and with recommends and/or suggests disabled in /etc/apt/, tdebase-trinity was installed, and tde-trinity was not installed.

Interesting - now I've checked it again:

1) Notebook with Stretch and current TDE 14.0.5~pre - 32bit
2) Desktop same Stretch and same TDE 14.0.5~pre - 64bit.

The same USB flash drive tested sequentially on both machines:

1) on notebook: everything works as expected
2) on desktop: incorrectly reported both - the partition and the device as a whole

Different behavior, although on the same system, the same kernel, the same udev, the same TDE. It seems to be really interesting to solve this bug :(

Created attachment 2792 [details]
tail -n55 of systemd journal plus entire output of dpkg -l

Fresh minimal 64 bit Stretch installation to host gx745 yesterday, followed by configuring apt with
APT::Install-Recommends "false";
and then
apt install tdebase-trinity tdm-trinity kmix-trinity ksnapshot-trinity kcalc-trinity konsole-trinity
(and various sound and sundry optional packages)
produces same absence of TDE session USB insertion notification  as in comment 0. I tried
apt install libstartup-notification0 notification-daemon notify-osd pam-dbus-notify libnotify-bin
but it didn't help. Same host booted to openSUSE 42.3beta produces expected notification.

(In reply to Felix Miata from comment #10)
> Same host booted to openSUSE 42.3beta produces expected notification.

Possibly I failed to make it clear that this was KDE3 that produced expected notification, not TDE. :-(

Fresh Stretch/TDE 14.0.5pre26 installation (host gx78b) still produces no apparent TDE session response to USB stick insertion that dmesg -w immediately reports:
# dpkg -l | egrep -i 'dbus|udisk'
ii dbus                      1.10.26-0+deb9u1 simple interprocess messaging system (daemon and utilities)
ii kdbusnotification-trinity 4:14.0.4-0debian9.0.0+0~a a DBUS notification service [Trinity]
ii libdbus-1-3:amd64         1.10.26-0+deb9u1 simple interprocess messaging system (library)
ii libdbus-1-tqt             4:14.0.5~pre7-0debian9.0.0+0~a dbus bindings for the Trinity Qt [TQt] interface
ii libdbus-glib-1-2:amd64    0.108-2 simple interprocess messaging system (GLib-based shared library)
ii libudisks2-0:amd64        2.1.8-1 GObject based library to access udisks2
ii udisks2                   2.1.8-1 D-Bus service to access and manipulate storage devices
# aptitude search notif | wc -l
121
# aptitude search notif | grep -i trinity
#i kdbusnotification-trinity 4:14.0.4-0debian9.0.0+0~a a DBUS notification service [Trinity]

I fail to find any material difference between Stretch above and same PC running openSUSE 15.0RC using openSUSE TW repos. Both TDE sessions ignore what the kernel and journal plainly see.

Adding kdbusnotification to Stretch drew a total of 19 (mostly gnome/gtk) packages. Doing same to 15.0 drew in 4.

Created attachment 2848 [details]
.xsession-errors and "lsof | egrep 'io|part' | grep -v ion" from running KDE3 on openSUSE 42.3 (hos msi85)

Created attachment 2849 [details]
.xsession-errors and "lsof | egrep 'io|part' | grep -v ion" from running TDE on openSUSE 15.0RC (using TW TDE repos; host gx78b)

Maybe someone can find a useful clue from perusing these two attachments?

Felix, I have been trying to reproduce this problem here, but without luck.
Two questions.

1) When you see this problem, are you actually able to see and mount the USB stick from CLI?

2) Are you able to reproduce this problem on a virtual box machine? 

Thanks

(In reply to Michele Calgaro from comment #15)
> 1) When you see this problem, are you actually able to see and mount the USB
> stick from CLI?

(openSUSE 15.0 host gx780)
(dmesg reports USB device attached 301.148732)
(Nothing apparent happens on TDE desktop)
$ mount -t auto /dev/sdb1 mnt
mount: only root can use "--types" option
$ mount /dev/sdb1 mnt
mount: only root can to that

> 2) Are you able to reproduce this problem on a virtual box machine? 

Except for DOS in OS/2, I only do hardware, so I have no idea what might be possible in a VM.

Same results in Stretch/14.0.5pre26 on host gx780. I also noticed that /run/media does not exist in either Stretch or 15.0.

> $ mount -t auto /dev/sdb1 mnt
> mount: only root can use "--types" option
> $ mount /dev/sdb1 mnt
> mount: only root can to that
What happens if you try as root or using sudo?
I am trying to understand if the USB is available and mountable but TDE does not give any notification, or instead if the USB is not available at system level.
The reason for asking this is because during my testing (with VM), one time I had the same messages as you in dmesg but the USB was not available at system level for some reasons (totally non mountable for some weird reasons that I have not been able to reproduce anymore).
Thanks

I don't sudo, even on my few *buntus. 

		# mount -t auto /dev/sdb1 mnt

(root on OS 15.0 host gx780 which has no USB3 ports) works as expected.

		# mount -t auto /dev/sdb1 mnt

(root on Buster host gx78b which also has no USB3 ports) works as expected. Regular user has same failure as comments 0, 17 & elsewhere.

Thanks again, Felix.
I tried to replicate the problem following the steps in comment 10 inside a VM, but again I am not able to replicate the problem.
Slavek is now trying to test on his machines.

I'd like to help more so I can make the switch from KDE3 on my primary PC and my 95% blind friend's PC, but have no idea how to not reproduce. I have well over 30 installations across Debian, Mageia, openSUSE, Kubuntu and Fedora, both x86 and x86_64. AFAIR, none have ever failed to fail going back at least a year if not much longer.

a-865 on #freenode

Problem exists on host gx780 booted to Xenial 16.04.4 4.4.0-128-generic.

Thanks the additional feedback Felix.

Slavek has also tested on his machines (both real and VM) and he is also unable to reproduce the problem.
Although we acknowledge that there is an issue as all your post shows, since we are unable to replicate the problem there is nothing we can do about it at this present time.
Therefore for the time being we are removing this bug from the R14.0.5 bug list.
The bug remains open. If we can find a way to reproduce this (possibly on a VM to make it fully hardware independent), we will work on a solution.
Sorry for not being able to be of more help :-(

What package or packages constitute "device notifier"?

Created attachment 2865 [details]
dpkg -l prior to installing any TDE/TDM packages on Butch on host gb250

# /root/.bash_history much culled to reduce noise from irrelevancies and harmless mistakes
# first boot
dpkg-reconfigure console-setup
apt update
apt install mc inxi mesa-utils dmidecode unzip aptitude zip hddtemp lm-sensors tree x11-utils x11-xserver-utils arj dbview dnsutils
cd /var/log/apt
touch term.log
touch history.log

# phase two
apt install nfs-kernel-server cifs-utils ntfs-3g libntfs-3g88 samba smbclient watchdog ntp
apt install xserver-xorg-video-vesa xserver-xorg-video-fbdev xserver-xorg-input-libinput xserver-xorg-input-evdev xserver-xorg-core xorgxrdp xfonts-scalable xorg xserver-xorg-legacy x11-xfs-utils
apt install fonts-stix
which startx
apt install dirmngr
wget http://mirror.xcer.cz/trinity-sb/pool/main-r14/a/axis-archive-keyring/axis-archive-keyring_2014.06.21.a_all.deb
ll
dpkg -i axis-archive-keyring_2014.06.21.a_all.deb 
apt install gnupg
apt install gnupg-utils
apt --fix-broken install
apt install dbus-user-session
apt --fix-broken install 
apt install dbus-user-session
apt install exfat-utils exfat-fuse udisks2 imagemagick ffmpeg alsa-tools alsa-utils pulseaudio-utils lpr curl xdg-utils libasound2-plugins pulseaudio xfsprogs dosfstools pavucontrol 
apt install read-edid
apt update
aptitude search konq
aptitude search arts
aptitude search trinity | grep gtk
aptitude search trinity
aptitude search trinity | egrep -i 'udev|dbus'
aptitude search trinity | egrep -i 'notif'
dpkg -l | sort > pkgs-pre-tde.txt
mc
mv .bash_history .bash_history01
touch .bash_history

# phase three (install TDE/TDM)
apt update
apt upgrade
sh tdeiD10.sh

Created attachment 2866 [details]
dpkg -l subsequent to installing TDE/TDM packages on Butch on host gb250

I replicated the failure yet again with a fresh Debian Buster installation to M.2 storage with Kaby Lake CPU.

/etc/apt includes /etc/apt/apt.conf.d/00InstallRecommends containing
APT::Install-Recommends "false";
which debian-installer created.

The installation was created using the net installer using this cmdline to initialize:
linuxefi /deb10/linux showopts vga=791 --- net.ifnames=0 ipv6.disable=1 biosdevname=0 netcfg/get_hostname=gb250 netcfg/get_domain=ij.net netcfg/disable_autoconfig=true netcfg/get_ipaddress=192.168.###.###/24 netcfg/get_gateway=192.168.###.### netcfg/get_nameservers=8.8.4.4 netcfg/confirm_static=true tasks=standard base-installer/install-recommends=false 

This is the script used to install TDE/TDM:
apt install \
arts-trinity \
gtk2-engines-gtk-qt-trinity \
gtk2-engines-oxygen \
gtk3-tqt-engine-trinity \
gtk-qt-engine-trinity \
gwenview-trinity \
kcalc-trinity \
kdbusnotification-trinity \
kgtk-qt3-trinity \
kipi-plugins-trinity \
kmix-trinity \
konqueror-trinity \
kpdf-trinity \
kruler-trinity \
ksensors-trinity \
ksnapshot-trinity \
mpeglib-trinity \
oxygen-icon-theme \
tdebase-trinity \
tdemultimedia-tdeio-plugins-trinity \
tdm-trinity \
tdmtheme-trinity \
twin-trinity

Created attachment 2867 [details]
.tgz of /var/log immediately after Butch installation on host gb250

Created attachment 2868 [details]
.tgz of /var/log immediately after TDE/TDM installation on Butch on host gb250

Contained /var/log/apt/ has *01 files, which are original files mv'd prior to installing TDE/TDM, so that the smaller versions could include almost exclusively TDE/TDM installation transactions.

Created attachment 2869 [details]
tee from 'apt install tde-trinity'

I cloned the gb250 Butch installation to another partition on same M.2 device, booted it, ran 'apt install tde-trinity' (470 additional packages, 921MB), rebooted, logged in, inserted a USB stick, saw 'dmesg -w' announce the insertion, and saw no evidence on the TDE desktop having anything to do with USB or device insertion or attachment. Then I inserted a (known good Knoppix 8.2 first try, a video second try) DVD, and even dmesg didn't notice either time.

Felix, thanks for the great feedback. I will try once again to replicate the problem on my VM, following your detailed instructions. Let's hope this time we have more luck :-)

Created attachment 2870 [details]
Screenshot of correct USB notification

Felix, I followed your exact steps (even compared the package list one by one to make sure the same environment is installed), but as you can see in the picture, my USB stick showed up correctly (tested 2 of them actually).
The only difference is that I tested inside a VirtualBox VM, since I can't do otherwise.

If you want to provide more feedback, here are two things you can try:

1) in an environment different from TDE where USB notifications are working, install VirtualBox, then try to replicate the exact steps inside the VM and see if the USB can mount (you need to link the USB from the Device -> USB-> <select your USB> to make the guest in the VM see the USB stick direcly.

2) try a clean installation as follow:
 - debian buster net-install, minimal system without any DE.
 - add TDE following the instruction on the wiki page. please use Slavek's PSB

3) can try the same thing using R14.1 preliminary testing build. Same steps as in 2) but the repo is now ...../trinity-tb buster deps main 
Please note that there is no -r14 in the names.

Once again, I can't help further unless I am able to reproduce the issue here :-(

(In reply to Michele Calgaro from comment #32)
> Created attachment 2870 [details]
> Screenshot of correct USB notification

That's the same thing I see in KDE3. What do top and/or lsof show when that is onscreen? (I don't spot anything in KDE3, or in plasma5 for that matter, but don't know what to look for.) What exactly constitutes "device notifier"? Surely there must be a missing dependency to something that should be provided by the distro that is causing this.
 
> Felix, I followed your exact steps (even compared the package list one by
> one to make sure the same environment is installed),

Buster, or Ubuntu, or something else?

> but as you can see in
> the picture, my USB stick showed up correctly (tested 2 of them actually).
> The only difference is that I tested inside a VirtualBox VM, since I can't
> do otherwise.

This kind of trouble is why all my PCs are multiboot and VMs aren't needed, or wanted. Because devs are committed to testing mainly only in VMs, I test only what mere mortals use, hardware.

> If you want to provide more feedback, here are two things you can try:
 
> 1) in an environment different from TDE where USB notifications are working,
> install VirtualBox, then try to replicate the exact steps inside the VM and
> see if the USB can mount (you need to link the USB from the Device -> USB->
> <select your USB> to make the guest in the VM see the USB stick direcly.

I've never tried VB. My installations are minimalist on minimal / filesystems, most on 5600MB or less, with no room for LO, and probably no room for VB. Most have less than 4GB RAM. How much space and RAM does VB need?
 
> 2) try a clean installation as follow:
>  - debian buster net-install, minimal system without any DE.
>  - add TDE following the instruction on the wiki page. please use Slavek's
> PSB

This sounds pretty close to exactly what I did yesterday in comments 26-29, 'apt install tdebase-trinity tdm-trinity' on the wiki plus the few basic apps I always need, konsole, ksnapshot, etc.
 
> 3) can try the same thing using R14.1 preliminary testing build. Same steps
> as in 2) but the repo is now ...../trinity-tb buster deps main 
> Please note that there is no -r14 in the names.

so instead of

	deb http://mirror.xcer.cz/trinity-sb buster deps-r14 main-r14

use

	deb http://mirror.xcer.cz/trinity-tb buster deps main

???

I did 'zypper in trinity-tdebase' (see bug 2940) on iMac host i2134's openSUSE 15.0/Plasma installation, then opened a TDE session (from SDDM), and inserted a USB stick. TDE Daemon opened up asking what I want to do with it.

What next?

Created attachment 2871 [details]
dmesg from USB stick insertions and removals on openSUSE 15.0 host i2134

I submitted comment 34 too soon. Two TDE Daemons open up asking what to do, one behind the Konsole window, that when second is selected open in new window it opens Konq window, but fails to display anything, and produces message:

Unable to mount this device. Potential reasons include: Improper device and/or user privilege level, Corrupt data on storage device. Technical details: org.freedesktop.DBus.Error.UnknownMethod: No such interface 'org.freedesktop.UDisks2.Filesystem' on object at path /org/freedesktop/UDisks2/block_devices/sdb. OK

The double notices (both behind the Konsole window) repeat with other sticks.

On insertion I briefly see kded (not kded5) appear in top.

On host gb250 with the "fat" Buster installation in a root TDE session I did 'apt install plasma-workspace' (262 newly installed, 427MB additional space will be used). I logged out, then logged in as ordinary user, inserted a stick, dmesg reported attachment, but no TDE Daemon appeared. Then I logged out and tried to log into a Plasma session, and was confronted with "All shell packages missing. This is an installation issue, please contact your distribution. OK", and neither working session, nor return to TDM.

Continuing from comment 36, I restarted PC, opened ordinary TDE session, opened top, and see command 'notification-da' hugging the top of the list, 1st, 2nd or 3rd continually without any USB devices attached. On stick insertion, dmesg reported sdf, but no TDE Daemon appeared, and no apparent change of notification-da position or activity in top.

> What exactly constitutes "device notifier"? 
Not sure I understand the question...

> Buster, or Ubuntu, or something else?
buster, R14.0.5 PSB from Slavek


> This kind of trouble is why all my PCs are multiboot and VMs aren't needed, or wanted. 
> Because devs are committed to testing mainly only in VMs, I test only what mere 
> mortals use, hardware.
I used to have a real machine till two years ago, now TDE only in VM.

 
> I've never tried VB. My installations are minimalist on minimal / filesystems, most on 
> 5600MB or less, with no room for LO, and probably no room for VB. Most have less than 
> 4GB RAM. How much space and RAM does VB need?
VB can run on a 4 GB machine. You can allocate 1GB to the VM, or even less. Disk space is only what you need if you use incermental disk allocation.

 
> This sounds pretty close to exactly what I did yesterday in comments 26-29
I followed comments 26-27 exactly

Trying with a standard install as described on the wiki seems to work on real computer as well (Slavek's), so it is just a test to see if perhaps the problem is caused by a missing dependency in your minimalistic installation
 

> deb http://mirror.xcer.cz/trinity-tb buster deps main
yes. or 
deb http://mirror.ppa.trinitydesktop.org/trinity-tb buster deps main
R14.1 has a new hardware monitor tray icon. I don't expect differences, but worth a try.

Created attachment 2872 [details]
15.0 host i2134 journal tail of plasma session's USB stick insertion, mounting, umounting, and removal

Created attachment 2873 [details]
15.0 host i2134 journal tail of subsequent TDE session's USB stick insertion, (absent device notification) & removal

(In reply to Michele Calgaro from comment #38)
> > What exactly constitutes "device notifier"? 
> Not sure I understand the question...

A binary or script or some combination of the two, or more, that collectively are responsible for causing something on a desktop to notify the user that some device has newly been attached and asks how to respond to its availability.

> A binary or script or some combination of the two, or more, that collectively are  
> responsible for causing something on a desktop to notify the user that some device has
> newly been attached and asks how to respond to its availability.
mostly udev and udisk2 AFAIK. There are probably other packages too, but those are the one most used (again AFAICT, I may be wrong)

Created attachment 2874 [details]
.tgz of installed package lists from the 4 installations on host gb250

14.1.0pre on Bionic on host gb250 has a device tray, and it announces stick insertion, much like Plasma, instead of a popup window like in comment 32. dpkg query shows it has an asynchronous event notification library package installed named libevent-2.1-6, same as 14.0.5pre on gb250's Busters, while 14.0.5pre on TW has 2_1-8. Bionic has 761 total packages installed. Buster has 786. BusterFat has 1520. TW has 692.

How can I determine what tdehwdevicetray is depending on to function, or is replacing whatever is missing in 14.0.x?

Created attachment 2875 [details]
redacted /root/.bash_history including initial boot from Bionic on host gb250

As can be inferred from perusing this, neither IceWM nor TDE require a working X in order to be installed. :-p

So in TDE 14.1 USB insertion is working correctly?
Then the problem is either in different dependencies or in some software difference.
you can look at the dependency of tdelibs or tdebase packages, the tdehwlib is part of the tdecore stuff.

Obviously this is a missing package(s) problem, and apparently no one but me has tried to replicate using a _minimal_ install as a foundation, meaning the inclusion on the installer cmdline

	base-installer/install-recommends=false

or whatever its preseed equivalent might be. I just did another Butch/14.0.5pre installation, except only for omitting that installation parameter, and the notifier works just as it does in KDE3.

Installing TDE consisted of the following from .bash_history:

dpkg-reconfigure console-setup
(Reboot)
df /
dfh
apt update
apt install mc inxi dmidecode samba cifs-utils smbclient nfs-kernel-server read-edid arj dbview zip unzip ntp acl 
mc
sh getkey-xcer.sh 
apt update
apt install tdebase-trinity tdm-trinity
systemctl get-default
(Reboot)
dmesg -w
top

So the question remains how to figure out which package(s) are missing when installing minimal:

(In reply to Michele Calgaro from comment #45)
> you can look at the dependency of tdelibs or tdebase packages, the tdehwlib
> is part of the tdecore stuff.

How is that done?

comment 46 installation was on host ab250. On my initial (minimal) Buster installation copied to host ab250 from gb250, after loading the outputs of dpkg -l of the copied gb250 installation and the comment 46 installation into kdiff3, and noticing libdaemon0 was missing from the first, I installed it there, and the notifier came right up. However, Konq announces unable to mount device:

Potential reasons include:
Improperr device and/or user privilege level
Corrupt data on storage device

Technical details:
org.freedesktop.UDisks2.Error.NotAuthorized: Not authorized to perform operation (polkit authority not available and caller is not uid 0)
OK

First openSUSE installation I checked doesn't have libdaemon0 installed either....

> I just did another Butch/14.0.5pre installation, except only for omitting that 
> installation parameter, and the notifier works just as it does in KDE3.
Then now it will be simple to find the missing package.

1) do minimal installation without recommend = false. Save package list. Result notification wor
2) do minimal installation with recommend = false. Save package list. Result notification don't work
3) compare the two lists
4) add the missing packages one by one and test. At some point the notification will work again as in 1). The last package installed should be the one required.

Please let us know what the package is.

Buster with tasks=standard base-installer/install-recommends=false installed 326 packages and consumed 935808 blocks, 13% of 8061880 blocks. .bash_history:
dpkg -l > pkglst-deb124.txt
ls -l
less < pkglst-deb124.txt 
dpkg -l | wc -l
dpkg -l | wc -l >> pkglst-deb124.txt 
reboot

Buster with tasks=standard installed 328 packages and consumed 956180 blocks, 13% of 8061880 blocks.
.bash_history:
dpkg -l  > pkglst-deb125.txt
dpkg -l | wc -l >> pkglst-deb125.txt
dpkg -l | wc -l
reboot

Relevant excerpts from diff -u of the two package lists:
+ii iso-codes 3.79-1 all ...
+ii os-prober 1.76 amd64 ...

Installing iso-codes in the ab250 clone of Buster of comment 26 failed to enable the popup window, but on stick insertion top shows variously among top 5: notification-da, artsd, knotify, pulseaudio, usb-storage, tde_dbus_hardw, tdekbdledsync, twin, systemd, kicker, udisksd.

From the kdiff3 comparison between working Kubuntu and a non-working Butch I selected each of the following to install one at a time on ab250's Butch Fat and test. It still doesn't work.

 libdevmapper-event
 libdevmapper-event1.02.1
 libevent-core
 libevent-core-2.1-6
 libevent-pthreads-2.1-6
 libfontembed1
 libgirepository-1.0-1
 libhpmud0
 libibverbs1
 libjim0.77
 libjxr0
 libjxr-tools
 liblcms2-utils
 liblvm2app2.2
 librdmacm1
 libtcl8.5
 libtcl8.6
 libtk8.5
 libtk8.6
 libtqt
 libtqt3-integration-trinity
 liburcu6
 libvolume-key1
 libwacom-bin
 libwebpdemux2
 libxatracker2
 mscompress
 netpbm
 netpbm
 python-certifi
 python-cffi-backend
 python-chardet
 python-cryptography
 python-jwt
 python-openssl
 python-prettytable
 python-requests
 python3-dbus
 python3-gi
 python3-olefile
 python3-pexpect
 python3-pil
 python3-renderpm
 python3-reportlab-accel
 python3-reportlab
 sntp
 ssl-cert
 tcl
 tix
 tk8.6
 usb-modeswitch-data
 usb-modeswitch

The list is roughly half of the packages missing from the non-working. Most not selected to try were either obviously not candidates, such as *samba*, dictionaries, *cups*, poppler*, *print*,*fonts*, *ghostscript*, *hp*, *photo*, *magick*, *pdf*, *sane* or turned out to have already been installed.

Felix,
we need your help to fix this since we can't reproduce the problem but you can.
Once again proceed as follow.

1) do minimal Butch/14.0.5pre installation WITHOUT "base-installer/install-recommends=false". This should result in notification working, as per your comment 46. Save the list of all packages installed.

2) on the same machine, do minimal Butch/14.0.5pre installation WITH "base-installer/install-recommends=false". This should result in notification NOT working, as per several of your comments. Save the list of all packages installed.

3) please post the two lists here for info.

4) Take any package in the first list that is not in the second list. Install it on machine 2). Test notification. 
  - If it works, that is the package required
  - If it does not work, select another package and repeat step 4)

5) Continue repeating step 4 until you find the package that is required. When found, save the list of all packages installed.

6) please post the additional list here for info.

Created attachment 2878 [details]
.tgz of before and after package lists for with and without install-recommends Buster installations

Comment 49 was the initial phase of what Michelle asked for in comment 51. Whether base-installer/install-recommends=false is included with a base install only differed by two packages, and that difference may have been a fluke caused by my going back at the bootloader step in 125. Apparently it's the addition of /etc/apt/apt.conf.d/00InstallRecommends 'APT::Install-Recommends "false";' during the initial installation that makes a difference at and after first boot.

Phase 2:
Butch124 used 1357580 1K blocks, 483 packages
Butch125 used 1698140 1K blocks, 735 packages
Difference: 252 more packages, 152.2% consumption by package count

Only the 125 installation currently opens a TDE session (and Device Notifier works). Apparently with APT::Install-Recommends "false"; none of Xorg gets installed as a dependency of any of TDE....

Note each instance of (Debian) "Butch" I made here should have been (Debian) "Buster".

Today in the 125 installation the notifier did not work, so I reformatted that partition and repeated the installation, again without "base-installer/install-recommends=false" on installation cmdline and without /etc/apt/apt.conf.d/00InstallRecommends 'APT::Install-Recommends "false";' while doing 'apt install tdebase-trinty tdm-trinity'. Again the notifier failed to appear. I'm at a total loss where the basis for comment 46 could have come from. ATM, the only installations that have a working notifier are the Bionic and the Fat Buster. Fat Buster has 1581 installed packages compared to the fresh 125's 735.

Since notifier was working in Fat Buster, I tried to verify it would continue to work, and a couple of other things, and notifier quit working, even after logging out and back in more than once, and rebooting. I fixed it by logging out, deleting the content of ~/.trinity/, and NOT making any desktop, clock or KControl alterations. After more hours of fiddling, logging out, logging in, more fiddling, etc., etc., it's apparent this has nothing directly to do with what packages are or are not installed.

All that's necessary is a desire for a clean desktop. Either of two things can make this reproducible on Buster, Stretch, or openSUSE 15.0 or Tumbleweed on hosts ab250 or gx78b:

	1-deselect show device icons, or
	2-deselect show icons on desktop

It may be necessary to log out and back in for the fail or succeed toggle to take effect.

In openSUSE, the notification window appears twice per device insertion.

> Either of two things can make this reproducible on Buster, Stretch, or openSUSE 15.0 or 
> Tumbleweed on hosts ab250 or gx78b:
> 1-deselect show device icons, or
> 2-deselect show icons on desktop

Thanks Felix, I am finally able to reproduce the problem in my VM.
Bug added back to R14.0.5 list.

In addition to the reported problem, in R14.1.0 the "show device icons" does not seem to work, i.e. icons are not shown on the desktop.

Also applies to Jessie (host big31).

Back to work on this bug.

Felix, can you help testing the steps below and provide feedback? Just want to make sure we are seeing the same things. I am using debian/buster TDE R14.0.5 updated to today. You can try with the same distro or with another version if you wish.

1) make sure "show icons on desktop" is active and "show device icons" is deselected. Apply settings. Close ALL windows so only the desktop and icons are visible.

2) Remove any USB or CD in your computer.

3) Reboot your computer and login

4) Without opening any window, insert a USB stick. Nothing happens, no notification.

5) Click "My computer", then "Services" and "Storage media". This should show your disks and the USB stick that was inserted at point 4)

6) Right click the USB stick and choose "safely remove". When all done, remove USB stick from your computer.

7) Close Konqueror so that only the desktop is visible.

8) Without opening any window, insert the same USB stick again. This time the notification dialog opens correctly.

The same sequence also happens when using a CD-ROM instead of a USB stick.
Please test and let me know if you see the same or not, and in the latter case what are the differences.
Thanks

I can confirm: R14.0.5 on the virtual machine - the behavior is exactly as Michele describes in comment 56!

(In reply to Michele Calgaro from comment #56)
> 1) make sure "show icons on desktop" is active and "show device icons" is
> deselected. Apply settings. Close ALL windows so only the desktop and icons
> are visible.

(host big41; Stretch/14.0.5 freshly updated) sorta check. I always have Konsole automatically open via leaving it running with two tabs on logout, particularly for exercises like these, so I can use dmesg -w, top, df, etc.

> 2) Remove any USB or CD in your computer.

check

> 3) Reboot your computer and login

check
 
> 4) Without opening any window, insert a USB stick. Nothing happens, no
> notification.

Correct, nothing happens.
 
> 5) Click "My computer", then "Services" and "Storage media". This should
> show your disks and the USB stick that was inserted at point 4)

My computers have no "my" anything. That's for Windows users. I looked in TCC > TDE Components > Service Manager, but don't see "storage media", but do see KDED Media Manager not running.

> 6) Right click the USB stick and choose "safely remove". When all done,
> remove USB stick from your computer.

I opened Konq from Kicker to storage media and was able to "safely remove".
 
> 7) Close Konqueror so that only the desktop is visible.

sorta check again
 
> 8) Without opening any window, insert the same USB stick again. This time
> the notification dialog opens correctly.

It does.
 
> The same sequence also happens when using a CD-ROM instead of a USB stick.
> Please test and let me know if you see the same or not, and in the latter
> case what are the differences.

Shortly after above USB stick test, insert of DVD was announced, then I ejected through Konq. I then logged out, logged back in, reinserted the DVD, and got no notification. I ejected through Konq, closed Konq, reinserted the DVD, and again got no notification, other than in dmesg -w, which displayed 8 4or5 line sets of [sr1] Buffer I/O errors.

I rebooted, logged in, restarted dmesg -w, inserted DVD in other OM drive, got nothing appended to dmesg, and got no notification. I ejected with Konq, closed Konq, selected show device icons, found desktop freshly littered with NFS shares of 20+ unbooted hosts and a small handful of NFS shares of booted hosts, inserted DVD, got notification after annoying (15-30 seconds?) wait.

Same host big41 also has Buster/14.0.5 experiencing this bug.

Thanks Slavek and Felix for testing.

Following commit should fix this bug:
R14.1.x: 4317c3e7 (tdebase) and 068aed6bc (tde-packaging)
R14.0.x: 0066e314 (tdebase) and e6d40c43e (tde-packaging)

Felix,
when the new packages are available in PSB, can you please test on your machine and let us know if the problem is now fixed? You need a reboot after the update to make sure the fix is active.

> In addition to the reported problem, in R14.1.0 the "show device icons" does not seem 
> to work, i.e. icons are not shown on the desktop.

This is now covered as part of bug 2947, which refers only to R14.1.x.

Fixed in 14.0.5pre45-0debian10.0.0+7a Buster on host ab250 without necessity to reboot.

Thanks for confirming this, Felix. Bug closed.