[Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?"

2024-05-19 Thread 513G3
Thank you Daniel.  I removed the now-overruled PPA from earlier in this
thread and directly installed those 4 packages on my 22.04 workstation.
Works great after a reboot.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2059847

Title:
  Input lag or freezes on Nvidia desktops with X11 after logging
  "MetaSyncRing: Sync object is not ready -- were events handled
  properly?"

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2059847/+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

2017-07-14 Thread 513G3
Thanks all!

I uninstalled my flatpak apps, flatpak, and dbus-user-session... then
rebooted and all's well.  Uninstalling with --purge seems to have taken
care of the /etc file markuslet pointed to.

$ flatpak list
$ flatpak --system uninstall com.xamarin.MonoDevelop
$ flatpak --system uninstall org.freedessktop.Platform
$ sudo apt-get remove --purge dbus-user-session
$ sudo apt-get remove --purge flatpak
$ sudo apt-get autoremove
$ sudo reboot

-- 
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

2017-07-14 Thread 513G3
The Status dropdown is for "Affects" and flatpak affects this issue (not
that it's the sole culprit).

** Changed in: flatpak (Ubuntu)
   Status: Invalid => Confirmed

** Also affects: dbus
   Importance: Undecided
   Status: New

-- 
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

2017-07-07 Thread 513G3
FWIW, my problem started after installing PPAs about a week before I
first posted here (June 17).  I just checked my /etc/apt/sources.list
and it was last modified June 10.  Perhaps it is coincidence... but
right when some PPAs went in, my problem started.

-- 
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/ubuntu/+source/chromium-browser/+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

2017-07-07 Thread 513G3
@MikeRushton... do you have any PPAs installed on your machines without
flatpak?

-- 
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/ubuntu/+source/chromium-browser/+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

2017-07-07 Thread 513G3
** Also affects: flatpak (Ubuntu)
   Importance: Undecided
   Status: New

-- 
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/ubuntu/+source/chromium-browser/+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

2017-06-29 Thread 513G3
** Also affects: lightdm (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gdm (Ubuntu)
   Importance: Undecided
   Status: New

-- 
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/ubuntu/+source/chromium-browser/+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

2017-06-28 Thread 513G3
The problem really is isolated to gnome-keyring (as OP and others
stated).

Here's my workaround for Chrome... it might help others (like Photon).
But in the end it is only a workaround.  It does demonstrate that if you
bypass the display manager (lightdm, gdm) triggering the gnome-keyring
for you, everything works great.

By having a session not orchestrated by a display manager, apps work
correctly:

$ ssh -X localhost
$ google-chrome &

-- 
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/ubuntu/+source/chromium-browser/+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

2017-06-27 Thread 513G3
For reference... https://github.com/karma-runner/karma-chrome-
launcher/issues/76

** Bug watch added: github.com/karma-runner/karma-chrome-launcher/issues #76
   https://github.com/karma-runner/karma-chrome-launcher/issues/76

-- 
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/ubuntu/+source/chromium-browser/+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

2017-06-21 Thread 513G3
Maybe a clearer capture of something amiss... logging in and out and in
repeatedly causes the keyring daemon process to be started again and
again (as lightdm and as the user).  Please see attached.

** Attachment added: "log_in_and_out.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1689825/+attachment/4900608/+files/log_in_and_out.txt

-- 
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/ubuntu/+source/chromium-browser/+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

2017-06-21 Thread 513G3
I uncovered another problematic side effect but I am unsure of the
significance; perhaps this will trigger an idea for someone

There are three user accounts on my box.  Here's a flow:
1) Reboot box
2) Sign in as user 1
3) Examine running processes (as MikeD mentioned in #33) and observe two 
keyring processes
4) Log out as user 1
5) Log in as user 2
6) Observe that Unity (via upper-right corner power icon thing) shows two 
checkmarks indicating that both user 1 and user 2 are signed in

-- 
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/ubuntu/+source/chromium-browser/+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

2017-06-17 Thread 513G3
I agree with comments #25 and #26.  It's likely a red herring, but this
issue arose for me right after I installed the flatpak PPA and a pile of
mono/M$ stuff.  I still figure that those actions are orthogonal, but
just in case everyone else recently installed similar stuff or a new PPA
or...

-- 
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/ubuntu/+source/chromium-browser/+bug/1689825/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs