-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Service snapd-desktop-integration reloads every 2 seconds #71
Comments
Marking myself as affected by this too. For me, it seems to crop up specifically if I choose |
Mmm... good point the Ubuntu on Xorg detail... checking it... |
I'm still unable to reproduce this bug. Can you check the logs? (open a terminal and type |
Still happens on Ubuntu 22.04.4 LTS. This just repeat endlessly, there are no other logs between. This happens after a desktop is launched. Here are all the logs when this begins: [code] |
Mmm... it is failing to initialize gtk... that's odd... |
Do you have the last version of snapd? ( |
snapd says it is up-to-date. The only one that doesn't have a plug: The rest is fine (it won't format properly here) |
Ok, I can reproduce it in a virtual machine... odd... |
Odd... I rebooted the VM and now it does work fine... |
Can you try this from a terminal?
and see if that fixes it, at least for the current session? |
Restarting doesn't do the trick for me. It seems to restart itself anyway
I am connecting remotely to the machine and was trying to set up chrome remote desktop, which doesn't seem to work and I'm guessing the 2 issues are related. uname -a
|
Oh, ok... so you are connecting remotely... Can you specify how are you connecting? SSH with -X? Other...? |
FYI, I see this error with Sway (I upgraded to Ubuntu 24.04.1, but I installed Sway ex novo, so it's a default Sway configuration) For now, I'm just sticking with i3 (while I keep using Sway on Nixos) |
I see the error while using XRDP (which is X + VNC) or X2Go (uses SSH). Both can be installed natively and work pretty much out of the box. Although I don’t see how that would be a problem as XRDP is just rendering the desktop locally and has nothing to do with snaps. |
snapd-desktop-integration is a systemd user daemon that needs to have access to the screen (it uses Gtk). To avoid having it relaunching over and over again when a ssh connection is made, it checks if the current session is graphical. If not, it waits until the user opens a graphical session. And when there is a graphical session, it launches a child that does gtk_init(). For some reason, the daemon recognizes Sway as a graphical session, but can't launch a graphical instance on it. The same for XRDP. |
This problem started after upgrading to Ubuntu 24.10 from 24.04. Version: latest/stable: 0.9 2024-10-11 |
For me, I can see also errors from apparmor:
Is it somehow trying to read some other processes' proc filesystem data? |
@esapulkkinen But does that error appear over and over again? Or is it just a one-shot error? The later is the expected behavior. |
@sergio-costas It happens once every 2 seconds. So very verbose in terms of syslog logging. |
@esapulkkinen But how are you login into? As a normal, local, graphical user? As a remote graphical user using VNC/whatever? As a remote text user (SSH)? |
@sergio-costas Normal local graphical user, This is an Ubuntu 24.04 LTS desktop with wayland. |
Can you check the installed version? (snap list snapd-desktop-integration). It should be 0.9 and be installed from latest/stable... |
@sergio-costas Yes it is. 0.9, Rev 253. from latest/stable/ubuntu-24.04. |
@esapulkkinen It's not the latest, but it should be latest enough... Maybe there are unconnected plugs? Can you check it with |
On an up to date Ubuntu 22.04.3 installation the snapd-desktop-integration service reloads every 2 seconds, spamming journalctl with the following messages:
Based on forum threads I could find (e.g. https://askubuntu.com/questions/1443676/snapd-desktop-integration-syslog-spam) it looks like this issue should be solved with the version released earlier this year, but with v0.9 from the stable or candidate channel the issue seems to persist even when running in a graphical desktop session.
The text was updated successfully, but these errors were encountered: