snap.snapd-desktop-integration.snapd-desktop-integration.service fails to start during boot #23
Comments
|
Can you try to run from a terminal...? |
|
I think I'm on the latest version: |
|
Mmm... very odd... Can you try to uninstall it and reinstall? |
and after rebooting: |
|
Mmmm... "Sorry, home directories outside of /home are not currently supported." That's odd... have you moved your home folder outside /home? |
|
There are extra info about how to proceed in that case here: https://forum.snapcraft.io/t/support-for-non-home-homedirs/11209/11 |
Nope, nothing out of the ordinary, my own user's home directory is |
|
Mmm... Can you open your /etc/passwd file and check if any of the entries have an user with an UID equal or greater than 1000 and a home folder pointing to something different to /home/XXX? (but don't paste the file here) |
|
Hm, I looked before but didn't realize this one exists: No idea where it's coming from. |
|
Nah... I have that one too... |
|
So it isn't a problem with passwd... |
|
What happens if you run it manually? I mean: |
|
It doesn't fail at least: And then it just keeps running without outputting anything. |
|
And if you run from inside the container? |
|
Same behaviour: |
|
Ok... then the bug isn't here, in snapd-desktop-integration, but it seems that it is in snapd itself... |
|
Ok. Happy to help testing things if it can help us pinpoint the issue. |
|
Thank you! |
|
Just another question: which version of snapd do you have? |
I seem to have run into the same problem on Ubuntu 22.04.1 LTS and have been trying to fix it for a week without success. TStart-Date: 2022-10-21 04:20:28 |
|
No, no... I need you to run "snap list snapd" from a command line. Snapd is updated as a snap, no matter if you have a different .deb package installed. |
snapd 2.57.4 17336 latest/stable canonical✓ snapd |
|
I found this thread while I was investigating a similar message in Logs. Following the steps listed further up: There are three (human) users with UIDs >= 1000, but all three of them have their home directory in the usual place ( Interestingly, I haven't done any customization with themes or touched snap at all (to my knowledge), other than using it through the Ubuntu Software GUI to install Firefox. I just noticed the message while I was looking into something else. |
|
UPD. snapd 2.57.5 17576 latest/stable canonical✓ snapd OS: Ubuntu 22.04.1 LTS Yesterday I got the snapd update to version 2.57.5 (17576), after rebooting everything that was broken on 2.57.4 (17336) is fixed. And yes, I also see error messages in the log: |
|
Seeing it also in my 22.04.1 LTS, removed snapd-desktop-integration in the end for the time being
|
|
Ok, the error message is normal, and should be "not problematic": it's because the daemon is being launched at the same time than the desktop, and sometimes it is "too early" and can't connect into it; but it is relaunched two second after that, and then it would work fine (if it is still too early, it will be relaunched again two seconds after...). |
|
But I'm getting this error message every 2 seconds in syslog; it's restarting indefinitely. This started on an upgrade from Ubuntu 20.04 to 22.04.1; snapd v2.57.6. I have 5 users at or above uid 1000: myself and vmail, both in /home, and nobody, snapd-range-524288-root, and snap_daemon, all in /nonexistent. Would any more information be useful? |
|
Oh, ok... that's a different problem: currently, due to some limitations in snapd, snapd-desktop-integration is launched in any session, not only in graphical ones, and, as you can imagine, they will fail in those cases. That's why they keep relaunching. We are already working on both the right solution(tm), which will require some time because it will require modifying snapd, and a quick fix to avoid these messages in the meantime. |
|
Ok, thanks. Unfortunately, this also happens when running over vnc. However, I can confirm that the restarts stop if I kill vncserver, find the physical computer, plug a monitor on to it, and log in. Short term, I'm afraid that I've removed |
|
I am also on Ubuntu 22.04.1 and it also filled /var/log/messages with messages like Running manually |
|
I am seeing a lot of also. |
|
There are at least two discussions about the atk-bridge issue on AskUbuntu. Here's the one with the most comments: https://askubuntu.com/questions/1443676/snapd-desktop-integration-syslog-spam/1443857 |
|
Ok, this error should be fixed partly in the current stable (it won't show anymore errors from the GDM session, the one about not allowing HOME folders outside /home), and completely in the candidate (it won't show errors neither from GDM, nor from SSH sessions). |
|
@sergio-costas Where is the correct place to report the unresolved issue of ssh-triggered syslog messages? This are still happening with snapd-desktop-integration:0.1 rev 49 which is listed as "latest/stable". If this issue has been resolved in a later release, please provide instructions to upgrade. Thanks. |
|
@hickst All these problems have been fixed with the last merges. You can install the "latest/candidate" version, but to make it fully functional you must manually connect the login-session-observe plug ( sudo snap connect snapd-desktop-integration:login-session-observe ). |
|
That connection will be automatic when that version is moved into stable. |
|
Yesterday I got the snapd update to version 2.58 (17950), and the dark theme has changed back to a light theme in snap-based applications, and most of them now won't start at all. In short, the same symptoms I experienced with the problematic 2.57.4 (17336) update It seems that the developers neglect to test snapd updates before sending them to the stable branch. This seems very strange, given that this problem occurs for the second time in the last three months, being on an LTS release |
|
@Dan-Master Can you try to launch one of those applications that won't start from a command line with: and paste here the error message shown in the screen? |
|
@sergio-costas Most of my critical applications have been converted to flatpak since the problem started last time, but here are a couple of examples of snap-apps that I still have and won't run now: I'll also add the error messages I see in the logs: |
|
Mmm... that's an odd message... It's like the gnome snap isn't installed. Do you have installed gnome-3-28-1804? Can you check if those packages have the gnome plug connected to that package? (for this last thing, run "snap connections package-name") |
Excerpt from snap list Here is an example of Translatium, which does not even start forcibly, despite the fact that it is added to the autorun |
|
I installed those two programs and they do work fine... Can you try to uninstall and reinstall them? |
So, on your recommendation, I reinstalled several applications to check: clipto, translatium and todoist. This seems to be the reason why snap-store is now only displayed in a light color scheme, despite the dark theme globally installed on the system. |
|
Do you have a theme different than the default one? Which one? (to do tests) |
No third-party themes are installed, I use the standard Yaru-Dark. Let me tell you right away that I have already tried to manually activate the Yaru-Dark theme for applications through the User Themes extension with Gnome tweaks. Thus, the global theme changes, exactly as well as through the system settings, but in Chromium and SnapStore remains invariably light. I also note that above the active elements of the browser pages that have a hyperlink, I now see the outdated cursor in the form of a hand, rather than the system cursor in the form of an arrow. I have a feeling that Chromium doesn't see which theme is used globally by the system, and since this problem occurred again after the update to snapd 2.58 (17950) I assume that either some dependencies were broken or no appropriate attributes for sandboxing shared libraries were provided. Chromium log |
|
Mmm... Try using "Yaru" instead of "Yaru dark", and set the dark theme in the gnome menu. That way it does work fine for me.
|
|
As far as I know, the Dark Mode menu item is a feature of Gnome since version 43.
|
|
Ops... Ooook... I'll install a virtual machine and check this. |
Hi @sergio-costas, is there any timeframe for when this will happen? This is still happening on a fully refreshed 22.04 system when logging in via ssh: $ lsb_release -sd
Ubuntu 22.04.1 LTS
$ snap list snapd snapd-desktop-integration
Name Version Rev Tracking Publisher Notes
snapd 2.58.2 18357 latest/stable canonical✓ snapd
snapd-desktop-integration 0.1 49 latest/stable/… canonical✓ -
$ journalctl -n10
Feb 17 12:00:38 sec-jammy-amd64 systemd[1016]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Scheduled restart job, restart counter is at 158.
Feb 17 12:00:38 sec-jammy-amd64 systemd[1016]: Stopped Service for snap application snapd-desktop-integration.snapd-desktop-integration.
Feb 17 12:00:38 sec-jammy-amd64 systemd[1016]: Started Service for snap application snapd-desktop-integration.snapd-desktop-integration.
Feb 17 12:00:39 sec-jammy-amd64 snapd-desktop-i[11519]: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it.
Feb 17 12:00:39 sec-jammy-amd64 snapd-desktop-integration.snapd-desktop-integration[11519]: Failed to do gtk init
Feb 17 12:00:41 sec-jammy-amd64 systemd[1016]: snap.snapd-desktop-integration.snapd-desktop-integration.service: Scheduled restart job, restart counter is at 159.
Feb 17 12:00:41 sec-jammy-amd64 systemd[1016]: Stopped Service for snap application snapd-desktop-integration.snapd-desktop-integration.
Feb 17 12:00:41 sec-jammy-amd64 systemd[1016]: Started Service for snap application snapd-desktop-integration.snapd-desktop-integration.
Feb 17 12:00:41 sec-jammy-amd64 snapd-desktop-i[11580]: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it.
Feb 17 12:00:41 sec-jammy-amd64 snapd-desktop-integration.snapd-desktop-integration[11580]: Failed to do gtk init
$ date
Fri Feb 17 12:00:45 PM PST 2023 |
|
@stevebeattie I don't have a precise time frame. But the candidate version does have the fix, and what's better, it autoconnects the login-session-observe, so it should be ready. I'll try to push it today. |
|
The candidate version has been promoted to stable, so this should be fixed. |
snap.snapd-desktop-integration.snapd-desktop-integration.servicefails to start during boot for me with the following being logged:I'm not sure if I'm having any issues caused by this, but was advised to log an issue for it anyway. My installation is upgraded from Ubuntu 20.04 (and possibly from 18.04 before that, can't recall).
I saw #12, but none of the steps the author of that issue took has fixed it for me. What can I do to help pinpointing the issue?
The text was updated successfully, but these errors were encountered: