Fixed it by removing the package :
sudo apt remove libp11-kit-gnome-keyring
sudo apt --fix-broken install
--
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/1769509
Title:
packa
Same here on Ubuntu 18.04 upgrade from Ubuntu 16.04 LTS
--
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/1769509
Title:
package libp11-kit-gnome-keyring 3.28.0.2-1ubuntu1 faile
Hello,
Same than Serguei for me, the folder .cache/shotwell had bad permissions
:
d---rwxrwx 2 amael amael 4,0K juil. 6 2013 shotwell/
The timestamp is over two years ago so it might be a very old bug that left
over the folder in this state.
Everything works now.
** Changed in: shotwell
Hello again,
after further investigation, it wasn't gnome-screensaver resetting my
nvidia settings but totem.
Found this bug and can reproduce it manually :
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/512493
--
You received this bug notification because you are a member of Ubuntu
Deskt
Hello,
I can confirm this bug in Ubuntu Natty 11.04. Also had it in Ubuntu
Maverick 10.10.
Steps to reproduce :
- launch a movie with Totem
- change the brightness setting in Totem preferences
- quit totem
- launch the same movie with vlc
-> the brightness will be the same configured in Tote
** Changed in: totem (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/512493
Title:
Totem changed settings, kills nvidia settings
--
desktop-bugs mailin
ng it, without touching any
parameter.
I found a thread talking about this problem (french), so I know that we aren't
only 3 persons affected :
http://forum.ubuntu-fr.org/viewtopic.php?id=218111
Some informations about my system :
amael@amserv:~$ /usr/lib/nux/unity_support_test -p
Ope
Same problem for me with upgrade from Hardy to Intrepid RC1, I had this problem
for several days now and you just gave me the solution, thanx !
Manually moving /etc/rc*.d/S20gdm to /etc/rc*.d/S30gdm solved the problem.
--
gdm startup is not moved from 21 to 30 on upgrade
https://bugs.launchpad.
