[Bug 1689825] Re: gnome-keyring not unlocked on boot
It might have changed in the newer releases of Ubuntu, but on 16.04 (Unity desktop) `dbus-user-session` is NOT installed by default and NOT a dependency of any standard packages. I myself got it as dependency of Anbox. Now that this is gone, the only remaining thing that points to this package is `dbus`, but as a suggestion. Suggestions are optional dependencies that do not automatically get installed unless you explicitly command `apt` to do so. Also if you would remove something which another (meta-)package recommends or suggests (not hard dependencies), that wouldn't uninstall this other package. And even if so, in case of the desktop meta-packages like `ubuntu-desktop` it would not make a difference anyway, as these don't have a function other than initially installing all stuff. No harm in them being removed. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on boot To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1689825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1689825] Re: gnome-keyring not unlocked on boot
Seems to me like `dbus-user-session` was the real culprit causing all the trouble. I got it installed with anbox and that is when the problem started. I got my keyring daemon to correctly start, the Login keyring to unlock automatically while still being encrypted with my account password again this way: - Purge `dbus-user-session`, e.g. by running `sudo apt purge dbus-user-session` - Revert files in `/etc/pam.d` back to their original state. I had commented out a line in `/etc/pam.d/lightdm` to work around the `gnome-keyring-daemon` not starting in the correct mode issue. - Set my account password on the Login keyring again (using seahorse). I had removed the password and left the keyring unprotected to avoid being asked for the password each session. - Set my user account password to something completely different and then back to my normal password using the `passwd` command. Before doing this, it seemed like the Login keyring and account password weren't yet synced correctly despite being equal. When I rebooted before the `passwd`, it still asked for the keyring password to be entered manually. - Reboot. On my next login, it asked for the Login keyring password to be entered manually one last time, but offered a checkbox to enable unlocking that keyring automatically on boot, which I checked. After this procedure, my system seems to be as good as new again. Running 16.04 with vanilla Unity desktop and lightdm btw. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on boot To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1689825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1626724] [NEW] Extracting iso changes target directory's permissions
Public bug reported: I have an ISO archive and opened it with file-roller. Then I clicked the big [Extract] button, selected my Desktop as target directory (options "Extract: All files" and "Actions: Keep directory structure" checked) and confirmed. It extracted the files successfully, but also changed the permissions of the target directory itself (to r-xr-xr-x). This is not expected and not intended. Actually I could no longer create or delete files in my Desktop directory after that, until I fixed the permissions again. I confirmed the behaviour with a different location as well. Extracting anything into a location should never modify permissions of the target location itself! If you're interested, here's what I did (extracting to ~/Desktop/testdir ; the "Extract" dialog window can be seen at https://i.stack.imgur.com/rlUvS.png): $ ls -l Desktop/ total 4 drwxrwxr-x 2 bytecommander bytecommander 4096 Sep 22 21:58 testdir/ $ file-roller test.iso $ ls -l Desktop/ total 4 dr-xr-xr-x 4 bytecommander bytecommander 4096 Sep 22 16:20 testdir/ System info: $ lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 $ apt policy file-roller file-roller: Installed: 3.16.5-0ubuntu1.2 Candidate: 3.16.5-0ubuntu1.2 Version table: *** 3.16.5-0ubuntu1.2 500 500 http://ftp.uni-stuttgart.de/ubuntu xenial-updates/main amd64 Packages 500 http://ftp.uni-stuttgart.de/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 3.16.4-1ubuntu3 500 500 http://ftp.uni-stuttgart.de/ubuntu xenial/main amd64 Packages ** Affects: file-roller (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1626724 Title: Extracting iso changes target directory's permissions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1626724/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
