The error messages are still there in mantic:
# journalctl | grep unshare
Sep 24 10:14:08 vougeot (udev-worker)[1373]: nvme0n1: Process '/usr/bin/unshare
-m /usr/bin/snap auto-import --mount=/dev/nvme0n1' failed with exit code 1.
Sep 24 10:14:08 vougeot (udev-worker)[1373]: nvme0n1p1: Process
good catch
I renamed the file '66-snapd-autoimport.rules' to
'OFF.66-snapd-autoimport.rules.OFF'
and rebooted.
root@prod:/lib/udev/rules.d# journalctl -b |grep 'exit code 1'
root@prod:/lib/udev/rules.d# echo $?
1
--
You received this bug notification because you are a member of Ubuntu
Touch
I saw this as well.
Linux kythera-Precision-5570 6.2.0-31-generic #31~22.04.1-Ubuntu SMP
PREEMPT_DYNAMIC Wed Aug 16 13:45:26 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
I deleted /lib/udev/rules.d/66-snapd-autoimport.rules and the issues
seems to have resolved itself.
--
You received this bug
Seeing this warning message in Jammy, with snapd 2.58+22.04.1 installed.
** Also affects: snapd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
(why is this file installed in desktop systems anyway?)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1966203
Title:
Syslog shows "systemd-udevd[2837]: nvme0n1: Process
I have to imagine mardy isn't going to bother investigating further, so
lets unsubscribe him. I'm hoping that will be enough for the snap team
to see this bug again.
Thanks
** Changed in: snapd
Assignee: Alberto Mardegan (mardy) => (unassigned)
--
You received this bug notification
Hi there, I see this with "lunar" Xubuntu 23.04
bernie@prod:~/Desktop$ journalctl -b |grep 'exit code 1'
Mai 30 17:16:45 prod systemd-udevd[246]: sda: Process '/usr/bin/unshare -m
/usr/bin/snap auto-import --mount=/dev/sda' failed with exit code 1.
Mai 30 17:16:45 prod systemd-udevd[234]: sr0:
** Tags added: lunar
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1966203
Title:
Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with
exit code 1." in
"Fix" as suggested by the dev's would be upgrading to 5.x LTS with:
"snap refresh lxd --channel=5.0/stable"
Same error, however doesn't seem to affect anything anymore.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Tags added: jammy kinetic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1966203
Title:
Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with
exit code
still present in 22.10. Newest ubuntu still work against old version of
snap.
# probe for assertions, must run before udisks2
ACTION=="add", SUBSYSTEM=="block", KERNEL!="loop*", KERNEL!="ram*" \
RUN+="/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/%k"
in my rule file
--
You
@Nick
Your mentioned fix, doesn't work for me even after a reboot.
LXD with snapd still refuses to start the associated VM, but with no error
messages anymore in syslog.
I tried this on Ubuntu 22.04, Kernel 5.15 with LXD 4.x LTS which
previously worked fine, after a while it seems like
Some updates, while I'm still investigating this on a QEMU running
Ubuntu Core 22.
The "snap auto-import" command is only needed on Ubuntu Core systems, so
the plan is to remove the /lib/udev/rules.d/66-snapd-autoimport.rules
from the snapd deb package (and consequently also from the snapd snap).
Thanks Nick for pointing me to this bug; I was working on the same
issue, as reported in a duplicate bug.
As far as the classic desktop is concerned, this bug occurs not because
of the failed mount, but because of "unshare" failing (see the
discussion in bug 1971955); in any case, the analysis by
Hi Johannes,
> Rebooting a week later after living on standby, I am screwed again.
Can you please explain what problems you experienced as a result of this
bug? My previous understanding was that there was no real effect, and
just a failed udev rule (which should not be running anyways) and
I just ran into this bug also on Ubuntu 20 LTS after updating the kernel a week
ago (multiboot laptop with Ubuntu and Windows 10). After figuring out that it's
not a hardware issue (since windows still booted normally), I made the switch
to Jammy, installed Ubuntu and all my software from
Rule is triggered by all block devices, I switched it off with !="block"
but that can only be a temporary fix.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1966203
Title:
I am not sure (I am not directly involved with snapd), but I can ask
someone to take a look.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1966203
Title:
Syslog shows
Hi @Nick Rosbrook (enr0n)
Will any modification(regarding snapd udev rule) be included in the
Ubuntu 22.04 release version?
Thanks,
Regards,
Jiwei
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
After speaking with snapd folks, it was determined that these udev rules
should not be triggered on desktop or server (and in fact, should be
limited to removable media). The proper solution here is to improve the
snapd auto-import udev rules.
Given that, we do not need to make any changes to
The error messages are also shown under UEFI mode
** Attachment added: "syste log_uefi_22.04(20220328)"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1966203/+attachment/5575021/+files/system%20log_uefi.zip
--
You received this bug notification because you are a member of Ubuntu
These errors appear to be coming from the udev rules in
/lib/udev/rules.d/66-snapd-autoimport.rules. I also see the errors on my
system, but I have not experienced any other problems as a result.
Jimmy or Jiwei, can you please tell us how you came across these logs?
What other problem(s) did you
** Also affects: snapd
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1966203
Title:
Syslog shows "systemd-udevd[2837]:
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1966203
Title:
Syslog shows "systemd-udevd[2837]: nvme0n1:
Can this be reproduced in EFI mode, or is it only when in Legacy Mode?
ALso, what is the mount command you are using? Just basic like "mount
/dev/device /mountpoint"? Or is there a different mount command you are
using that is failing?
--
You received this bug notification because you are a
According to our investigation, I found that the issue is caused by the
"mount" system call can not be allowed to execute.
And after checking the upstream commit, the issue is introduced by the
following patch,
commit ee8f26180d01e3ddd4e5f20b03b81e5e737657ae
Author: Lennart Poettering
Date:
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966203/+attachment/5572464/+files/syslog
** Package changed: linux (Ubuntu) => systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
27 matches
Mail list logo
