This is a Tumbleweed system that has been (mostly) zypper dup-ed
for a bit more than two years.
rpm -qa gnome* | grep -v 3.26 | sort gives the following, and I
wonder to what extent I can/should simply remove these packages?
gnome-icon-theme-3.12.0-4.2.noarch
gnome-icon-theme-extras-3.12.0-3.3.noarch
gnome-icon-theme-symbolic-3.12.0-3.3.noarch
gnome-keyring-3.20.1-3.4.x86_64
gnome-keyring-pam-3.20.1-3.4.x86_64
gnome-mahjongg-3.22.0-1.3.x86_64
gnome-menus-3.13.3-2.4.x86_64
gnome-menus-branding-openSUSE-42.1-1.4.noarch
gnome-nettool-3.8.1-8.6.x86_64
gnome-power-manager-3.25.90-1.1.x86_64
gnome-shell-search-provider-seahorse-3.20.0-2.8.x86_64
gnome-themes-accessibility-3.22.3-1.3.noarch
gnome-themes-accessibility-gtk2-3.22.3-1.3.noarch
gnome-user-share-3.18.3-1.3.x86_64
gnome-vfs2-2.24.4-29.2.x86_64
gnome-video-effects-0.4.3-1.2.noarch
And, more importantly, should we get them removed via zypper dup?
Gerald
--
To unsubscribe, e-mail: opensuse-gnome+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-gnome+owner(a)opensuse.org
Once an USB storage device with several partitions gets connected to the system, something automatically mounts each filesystem on a partition in read-write mode. Filesystems on LVM volumes are recognized, but not automatically mounted. LUKS partitions are entirely ignored.
To avoid datacorruption during a crash, one can unmount these partitions easily in the Nautilus UI. But once the screen is locked, and later unlocked, something mounts the filesystems again.
To me it is not clear at all what the benefit of that action would be.
The question is: what must be done to avoid these automounts during screen unlock?
Olaf
