[Bug 1689825] Re: ubuntu 16.04 Chrome and Chromium asking for keyring.
I'm not positive when an update was pushed out that caused this - my machine gets updates automatically every night but I rarely reboot. I rebooted yesterday and was immediately affected by it. -- 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: ubuntu 16.04 Chrome and Chromium asking for keyring. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1689825/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 744619] Re: Screen doesn't unlock; stuck on "Checking"
Actually one more comment - I was digging into my auth.log and it may be video related. The logs when it failed to unlock and when it succeeds are identical. I then noticed that one of my three monitors shows garbage at the bottom when I tap the top left corner to bring up the app chooser view in Gnome 3. It makes me wonder if the screensaver isn't authenticating you properly, then just failing to go away... Logs on a successful unlock and on a failure look identical: May 17 10:31:46 river gnome-screensaver-dialog: pam_unix(gnome-screensaver:auth): authentication failure; logname= uid=1000 euid=1000 tty=:0.0 ruser= rhost= user=tony May 17 10:31:47 river gnome-screensaver-dialog: pam_sss(gnome-screensaver:auth): authentication success; logname= uid=1000 euid=1000 tty=:0.0 ruser= rhost= user=tony May 17 10:31:47 river gnome-screensaver-dialog: gkr-pam: unlocked login keyring -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/744619 Title: Screen doesn't unlock; stuck on "Checking" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/744619/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 744619] Re: Screen doesn't unlock; stuck on "Checking"
Thanks for that tip Michael. Sad, but after updating to 16.04 the problem persists. I can't seem to find a permanent fix. I've also changed video cards (nvidia 960 now) so the vid card itself apparently wasn't involved. This is an upgrade install all the way from 12.04 if I remember correctly, so I wonder if it's a leftover setting of some sort that's screwing it up. The other possibility for me that is different is I use LDAP authentication (using sssd now, but previously directly with ldap and pam) so I wonder if it's something in the underlying authentication system and gnome 3 that causes it. I'm the only person in the organization running Gnome 3, everyone else is on Unity and doesn't experience it. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/744619 Title: Screen doesn't unlock; stuck on "Checking" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/744619/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 744619] Re: Screen doesn't unlock; stuck on "Checking"
This is still an issue for me on 15.04. I have to alt-f1, log in and kill gnome-screensaver. Then I need to save everything and reboot because every few seconds the screen will turn black after doing this. I don't use ecryptfs, I don't have several copies of gnome-screensaver running when this happens, and it's not a hibernation issue with me because it happens from a simple screensaver lock timeout - my music remains playing in the background. It occurs about once per 30 or so screensaver locks, and usually Chrome is the only major thing I have open when my screen locks. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/744619 Title: Screen doesn't unlock; stuck on "Checking" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/744619/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 830840] Re: Chat window will not open
This is happening to me as well. As described by Rodrigo, after a reboot it may work ok for a while. If I click Quit from the chat menu and launch it again sometimes it works for a while as well. I've tried launching Empathy from a console to see if it logs anything but nothing shows. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/830840 Title: Chat window will not open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/830840/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 830840] Re: Chat window will not open
To bil21al: Exact steps? Seemed pretty exact above but simply log in to Gnome 3 Shell in Ubuntu Natty, launch Empathy. Wait a while. Maybe an hour, maybe a day. Try to chat with someone, no chat window opens. If they send you a chat it pops up in the Gnome Shell widget thingy at the bottom, but right clicking their name and picking open from the tray does nothing. Double click their name in the Empathy user list does nothing. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/830840 Title: Chat window will not open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/830840/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 862677] Re: Can no longer create IMAP folders
I can confirm the issue. I have noticed though that in IMAP+ on one of my machines it will create the folder and it's saved on the IMAP server, but it doesn't show in the treeview inside Evolution until you close and restart Evolution - you can't even refresh the subscription list to see it. On my other machine - that appears to be configured identically - it looks like it creates the folder but the folder is never actually created on the server. On this one when I watch the Cyrus server logs it never shows any activity from the Evolution client. I'm beginning to see why they went with Thunderbird as the default mail client now. Running Evolution 3.2.0 from Oneiric. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/862677 Title: Can no longer create IMAP folders To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/862677/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 465464] Re: Gnome panels continuously crash, then reload
I'll confirm it's caused by removing the notification area, and point to a bug in the Debian list that references details: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=547093 I was able to get back in by logging into an xterm session instead of gnome and do the following: cd .gconf/apps/ rm -R -f panel exit Then, log back into a gnome session and the default panel has returned, minus the crash loop. Hardware details: Dual Nvidia 9800GT PCI-X cards Two monitors on each card, twinview for each desktop (total 4 monitors, 2 desktops) Proprietary nvidia drivers installed with the hardware drivers tool. ** Bug watch added: Debian Bug tracker #547093 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=547093 -- Gnome panels continuously crash, then reload https://bugs.launchpad.net/bugs/465464 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
