[Bug 1977646] Re: Snap apps launch time are EXTREMELY slow
*** This bug is a duplicate of bug 1833004 *** https://bugs.launchpad.net/bugs/1833004 Thanks Islam for reporting this. I'm going to mark this as a duplicate, as we already have this issue reported as bug 1833004. ** This bug has been marked a duplicate of bug 1833004 Application SNAP is slower than DEB at first launch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977646 Title: Snap apps launch time are EXTREMELY slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1977646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778375] Re: All snap loops are being output for lsblk, blkid, and fdisk -l.
Hi Anthony, thanks for reporting this bug (I just found it accidentally while browsing through the existing bugs. I'm afraid that there's little we can do about the fact that these programs also list the mounted snaps -- there might be even scripts, by now, which rely on this behaviour. Where I think we could do something, it's about the fact that the same snap can appear twice, if there are two revisions of it installed; I guess we could avoid mounting the old one -- I'll check with the rest of the team to understand if there is a reason why it has to be this way. ** Changed in: snapd (Ubuntu) Assignee: (unassigned) => Alberto Mardegan (mardy) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778375 Title: All snap loops are being output for lsblk, blkid, and fdisk -l. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1778375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976161] Re: Session restarts when opening Pluma or GitHub link in browser
Hi Fernando, and thanks for reporting this bug! If, as you wrote in the bug description, you reproduce it when logging in with your uername and password, then this bug is not related to bug 1593407, which is about the "guest session" (that is the session for those users who don't have a login in the machine). There appears to be something wrong with the user session. Are you using Wayland or Xorg? Also, can you please attach the output of these commands (you can run them before opening the troublesome link in firefox, while your session is still working): systemctl --user status xdg-document-portal.service systemctl --user status snap.snapd-desktop-integration.snapd-desktop-integration.service ** Changed in: snapd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976161 Title: Session restarts when opening Pluma or GitHub link in browser To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1976161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959417] Re: browsers and other apps packaged as snaps can't read files under ~/.local/share/
For the record, I've opened a discussion in the jupiter-notebook forums: https://github.com/jupyter/notebook/discussions/6436 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959417 Title: browsers and other apps packaged as snaps can't read files under ~/.local/share/ To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1959417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871148] Re: services start before apparmor profiles are loaded
Oh, this is interesting! Then, Etienne, my suggestion is the following: re-enable the snapd.apparmor service, and if that (as I expect) fixes the bug, let's stop discussing this issue here, and instead open a separate issue about the service being disabled. It may be that something went wrong during the upgrade to Jammy. If we file this as a separate bug, we might be able to see if other people have met the same issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871148 Title: services start before apparmor profiles are loaded To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1871148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871148] Re: services start before apparmor profiles are loaded
Oh, thanks Alex, I forgot that we have our own service for loading the AppArmor profiles of the snaps! Etienne, could you please show the output of sudo systemctl status snapd.apparmor ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871148 Title: services start before apparmor profiles are loaded To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1871148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966203] Re: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04
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). We do still need it in UC, but as a matter of fact the script is already provided by the Ubuntu Core repositories: - UC22: https://github.com/snapcore/core-base/blob/main/static/usr/lib/udev/rules.d/66-snapd-autoimport.rules - UC20: https://github.com/snapcore/core20/blob/master/static/usr/lib/udev/rules.d/66-snapd-autoimport.rules - UC18: https://github.com/snapcore/core18/blob/master/static/lib/udev/rules.d/66-snapd-autoimport.rules - UC16: **missing** The file in UC22 seems already correct, in that it does not call unshare. So the only one left out is UC16, where we will add the udev rule that we currently have in snapd; after that, we will remove the rule from snapd and this bug for the desktop will be gone for good. There is a remaining problem, however: the systemd-udevd.service in Ubuntu 22 disallows the mount operation, so we'll have to update the unit file to allow it. I think we'll also need to update the auto-import command itself, because it appears that all errors while accessing the devices are silenced, so we would have never known of this problem, if it wasn't for this bug report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966203 Title: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1966203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966203] Re: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04
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 Jiwei Sun is correct: it's happening because of the added SystemCallFilter entry to the udev unit file. ** Changed in: snapd Assignee: (unassigned) => Alberto Mardegan (mardy) ** Changed in: snapd Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966203 Title: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1966203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971955] Re: systemd-udevd call unshare process when attaching nvme volume
*** This bug is a duplicate of bug 1966203 *** https://bugs.launchpad.net/bugs/1966203 Thanks Nick, indeed! I'm closing this since 1966203 was reported first. ** This bug has been marked a duplicate of bug 1966203 Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971955 Title: systemd-udevd call unshare process when attaching nvme volume To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1971955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971955] Re: systemd-udevd call unshare process when attaching nvme volume
** Changed in: snapd (Ubuntu) Assignee: (unassigned) => Alberto Mardegan (mardy) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971955 Title: systemd-udevd call unshare process when attaching nvme volume To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1971955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971955] Re: systemd-udevd call unshare process when attaching nvme volume
Hi again Vincent :-) Please ignore the part about adding more attributes to the SystemCallFilter list; I don't think it's a road we want to follow. What would be more important for me to know, is whether things work if you change the RUN line to just RUN+="/usr/bin/snap auto-import --mount=/dev/%k" Please let me know if this works. :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971955 Title: systemd-udevd call unshare process when attaching nvme volume To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1971955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971955] Re: systemd-udevd call unshare process when attaching nvme volume
Thanks Vincent. I think I got some hints: I downloaded the package from Jammy, I unpacked it and then ran a diff on the systemd unit file for the udev service (since in the documentation of udev[1] it's written that programs are executed in a sandbox) from the version in Focal: == --- /lib/systemd/system/systemd-udevd.service 2022-04-21 15:54:39.0 +0300 +++ lib/systemd/system/systemd-udevd.service2022-04-07 22:28:15.0 +0300 @@ -1,4 +1,4 @@ -# SPDX-License-Identifier: LGPL-2.1+ +# SPDX-License-Identifier: LGPL-2.1-or-later # # This file is part of systemd. # @@ -8,7 +8,7 @@ # (at your option) any later version. [Unit] -Description=udev Kernel Device Manager +Description=Rule-based Manager for Device Events and Files Documentation=man:systemd-udevd.service(8) man:udev(7) DefaultDependencies=no After=systemd-sysusers.service systemd-hwdb-update.service @@ -16,8 +16,10 @@ ConditionPathIsReadWrite=/sys [Service] +DeviceAllow=block-* rwm +DeviceAllow=char-* rwm Type=notify -# Note that udev also adjusts the OOM score internally and will reset the value internally for its workers +# Note that udev will reset the value internally for its workers OOMScoreAdjust=-1000 Sockets=systemd-udevd-control.socket systemd-udevd-kernel.socket Restart=always @@ -27,11 +29,14 @@ KillMode=mixed TasksMax=infinity PrivateMounts=yes +ProtectClock=yes ProtectHostname=yes MemoryDenyWriteExecute=yes RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6 RestrictRealtime=yes RestrictSUIDSGID=yes +SystemCallFilter=@system-service @module @raw-io bpf +SystemCallErrorNumber=EPERM LockPersonality=yes IPAddressDeny=any WatchdogSec=3min == I need to double-check, but I suspect that the SystemCallFilterAddition might be causing problems. Vince, can you please make a backup copy of /lib/systemd/system/systemd- udevd.service, then remove the two SystemCallFilter and SystemCallErrorNumber lines, reboot and see if the errors are gone? If they are, then please restore the original file, and try adding "@process" to the SystemCallFilter list; then reboot and see if it helped. Or you can have a look at the possible values here [2] and try understanding which ones are necessary. Though if you don't have time, don't worry too much with this: it's something that we should be able to determine ourselves. [1]: https://www.freedesktop.org/software/systemd/man/udev.html [2]: https://www.freedesktop.org/software/systemd/man/systemd.exec.html#SystemCallFilter= -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971955 Title: systemd-udevd call unshare process when attaching nvme volume To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1971955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968878] Re: systemd-udevd: video4linux: Process '/usr/lib/snapd/snap-device-helper add ... /class/video4linux 0:0' failed with exit code 1.
Hi Paul and Laurent, thanks for your bug report. Can you please check what happens when you manually run tha same commands that you see as failed? For example, from Laurent's log: sudo /usr/lib/snapd/snap-device-helper add snap_brave_brave /class/video4linux 0:0 && echo ok Also, if you don't mind, please attach the syslog when such error occurs (by the way, do they happen at every boot, or irregularly?) sudo journalctl -b I suspect that this and bug 1971955 might be related. ** Changed in: snapd (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968878 Title: systemd-udevd: video4linux: Process '/usr/lib/snapd/snap-device-helper add ... /class/video4linux 0:0' failed with exit code 1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1968878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871148] Re: services start before apparmor profiles are loaded
Thanks Etienne, this is a bit surprising! Do I understand correctly, that on the slower machine (where you are seeing this bug) you will not be able to start firefox until you have run that apparmor_parser command? Not even if you try starting firefox well after the login? It's strange, because your logs show that the apparmor.service unit was started can you please also attach the output of these commands: sudo systemctl status apparmor sudo journalctl -b _SYSTEMD_UNIT=apparmor.service + SYSLOG_IDENTIFIER=audit And then also this (make sure you haven't previously started firefox in this boot): SNAPD_DEBUG=1 firefox And after that, let's have a look at the full system log (I have no clear idea what to look for, actually, but maybe I'll spot something suspicious): sudo journalctl -b -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871148 Title: services start before apparmor profiles are loaded To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1871148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971955] Re: systemd-udevd call unshare process when attaching nvme volume
Mmm... I'm running out of ideas! Mayve it's something with the environment? Vincent, can you try changing the rule to RUN+="/bin/bash -c 'set > /tmp/set.log'" and attach set.log here? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971955 Title: systemd-udevd call unshare process when attaching nvme volume To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1971955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776800] Re: Unable to start snap applications if user's home directory is not /home/$USER
Hi Jeffrey and Erik! You are being heard :-) But this is not an easy task, and the amount of work required to support the case of home directories nested somewhere deeper inside /home is very different (read: lower) than that required to support home directories located elsewhere in the system. We are first tackling the first problem, and this bug will be closed once that part is fixed. The bug that best describe your use-case is https://bugs.launchpad.net/snappy/+bug/1620771, so I recommend you to subscribe to that one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776800 Title: Unable to start snap applications if user's home directory is not /home/$USER To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776800] Re: Unable to start snap applications if user's home directory is not /home/$USER
** Changed in: snapd Assignee: (unassigned) => Alberto Mardegan (mardy) ** Changed in: snapd Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776800 Title: Unable to start snap applications if user's home directory is not /home/$USER To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784774] Re: snapd is not autofs aware and fails with nfs home dir
Hi Erik, I see now what's the problem (this is specific to your setup -- this probably does not concern other people who commented here): your home directories are under /staff, whereas currently snaps only support the traditional /home// scheme. Please subscribe to https://bugs.launchpad.net/snapd/+bug/1776800, we are working on it :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1784774 Title: snapd is not autofs aware and fails with nfs home dir To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1784774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971955] Re: systemd-udevd call unshare process when attaching nvme volume
Vincent, maybe the udev rules are running under a user lacking some privileges? Can you please try changing the rule to RUN+="/bin/bash -c 'id > /tmp/id.log'" and then paste here the output of id.log? (hopefully I didn't mess up the quoting in the command :-) ) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971955 Title: systemd-udevd call unshare process when attaching nvme volume To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1971955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784774] Re: snapd is not autofs aware and fails with nfs home dir
Thanks Erik and Andrew for the logs! It looks like we have more than one bug here: 1) Andrew's logs show that after restarting the snapd service, NFS was correctly detected and there are no more AppArmor denials on that. But on Erik's machine, for some reason, that did not happen. 2) Even if the network rules are added, snaps still fail to start; I believe that the root cause is the same as in https://bugs.launchpad.net/bugs/1973321 (despite the fact that that bug is about sshfs) I will continue investigating the first issue here. Whereas, for the second one, Andrew, can you please check if snaps start once you "cd" to another directory, like "/snap"? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1784774 Title: snapd is not autofs aware and fails with nfs home dir To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1784774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871148] Re: services start before apparmor profiles are loaded
Hi Etienne, can you be a bit more explicit about what is the issue that you are seeing? What are the services which are not starting? Also please attach the SVG file generated by "sudo systemd-analyze plot", it might help us. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871148 Title: services start before apparmor profiles are loaded To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1871148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784774] Re: snapd is not autofs aware and fails with nfs home dir
I believe that this is a duplicate of bug 1884299. A few questions to people affected by this bug: 1) are you using autofs? 2) can you please try running "sudo systemctl restart snapd" after logging in into your $HOME, and then try running a snap again? 3) If that still fails, can you paste the journal logs here (from the time that snapd was restarted)? ** Changed in: snapd (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1784774 Title: snapd is not autofs aware and fails with nfs home dir To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1784774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971955] Re: systemd-udevd call unshare process when attaching nvme volume
Hi Vincent, if I understand it correctly, this command scans the inserted media for snapd assertions and imports them. It's still not clear to me what's happening: even if you are running on a classic system, the "auto-import is disabled on classic" is just a notification and not an error: the program still exits with a 0 exist status. Yet, in the logs you provided, it appears as if the exist status is 1. Could it be that the error is not coming from "snap auto-import", but rather from the "unshare" command? Can you please try to manually edit the file (after making a copy of it!) and change the RUN line into RUN+="/usr/bin/unshare -m /bin/echo hello" and see if you still get those errors in the log? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971955 Title: systemd-udevd call unshare process when attaching nvme volume To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1971955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959375] Re: [SRU] Please support group manipulation with "extrausers"
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959375 Title: [SRU] Please support group manipulation with "extrausers" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959375] Re: [SRU] Please support group manipulation with "extrausers"
Hi Brian, I finally tested the new packages on Ubuntu Core 18 (with the bionic packages) and Ubuntu Core 20 (with the focal ones). I first tried to reproduce the issue in Ubuntu Desktop, by making /etc/groups and /etc/passwd read-only and indeed I couldn't add my user to a group, but unfortunately then I couldn't get the extrausers database setup correctly, so I gave up and just ran a quick smoke test to verify that the new binaries work as expected and instead focused on Ubuntu Core, that's where we initially had the issue. The only problem is that I didn't test the entire deb packages, since the root FS in UC is read-only and not debian-based, but I just extrated the binaries from the passwd deb package and bind-mounted them over the original UC ones. Then I was able to add my user to a group, without needing to specify the --extrausers parameter. I hope that this is good enough as a verification. ** Tags removed: verification-needed-bionic verification-needed-focal ** Tags added: verification-done-bionic verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959375 Title: [SRU] Please support group manipulation with "extrausers" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1662552] Re: snaps don't work with NFS home
We did some progress in investigating this, and it appears that a problem still exists: if the system is using autofs and snapd is started before any NFS home directory is mounted, snapd will fail to detect the fact that the system is using autofs (or NFS), and will not grant snap- confine those permissions needed to use the network. Given that this bug is old and that indeed a (partial) fix landed, I suggest to keep it closed; I noticed that someone else filed a new bug which explicitly mentions the autofs case, so I suggest continuing the discussion there: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1884299 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1662552 Title: snaps don't work with NFS home To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1662552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884299] Re: Chromium snap won't run with nfs home drive
A similar issue was discussed in the forums: https://forum.snapcraft.io/t/cannot-open-path-of-the-current-working- directory-permission-denied-bis/28704 If the system is using autofs and snapd is started before any NFS home directory is mounted, snapd will fail to detect the fact that the system is using autofs (or NFS), and will not grant snap-confine those permissions needed to use the network. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884299 Title: Chromium snap won't run with nfs home drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1884299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971955] Re: systemd-udevd call unshare process when attaching nvme volume
Hi Vincent, thanks for reporting this. There should be some message printed by the "snap auto-import" command when it fails. Can you please try to manually run (as root) the command /usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n239 and paste here the output? ** Changed in: snapd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971955 Title: systemd-udevd call unshare process when attaching nvme volume To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1971955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969842] Re: No font available after installing in user space
Access to the "$HOME/.local/share/fonts/" is provided by the "desktop" interface. The libreoffice snap should add this interface to its plugs, and then fonts from this location should become usable. I'm marking this bug as invalid for snapd (since it does not appear that we need to do anything there about it), whereas the bug stays valid for libreoffice. ** Changed in: snapd (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969842 Title: No font available after installing in user space To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1969842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969529] Re: snapd slow to seed firefox on Pi 400
Hi Dave, I did not see any I/O errors from the kernel, but in your first boot log (https://errors.ubuntu.com/oops/fa9433d0-c022-11ec-8ae0-fa163e993415) there are plenty of errors which might be related to missing files: === Apr 19 21:46:38 localhost.localdomain pulseaudio[841]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="platform-fef05700.hdmi" card_name="alsa_card.platform-fef05700.hdmi" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no card_properties="module-udev-detect.discovered=1""): initialization failed. ... Apr 19 21:46:42 localhost.localdomain udisksd[985]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory ... Apr 19 21:53:20 miss-piggy pipewire-media-session[840]: ms.core: error id:0 seq:701 res:-32 (Broken pipe): connection error Apr 19 21:53:21 miss-piggy accounts-daemon[934]: failed to check if user 'oem' in cache dir is present on system: No such file or directory Apr 19 21:53:21 miss-piggy tracker-miner-f[970]: Could not delete '.meta.isrunning': No such file or directory ... Apr 19 21:53:31 miss-piggy pulseaudio[34513]: Failed to open cookie file '/var/lib/gdm3/.config/pulse/cookie': No such file or directory === plus plenty of driver initialization errors; but on the other hand, it may be that all of that is normal -- I just wanted to make sure that we don't have to deal with a corrupted image. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969529 Title: snapd slow to seed firefox on Pi 400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1969529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969529] Re: snapd failing to seed firefox on Pi 400
Hello again, Dave! Looking at the logs, it doesn't seem that your problem is related to bug 1969162. What I'm left to suspect is a storage issue, since there are many errors about files failing to load in the logs. I've had similar issues with a RPi3, where I had to flash the same Ubuntu image over the SD card a couple of times before the boot succeeded. Would you mind trying the same? That is, just reflash the image a couple of times, and only afterwards you try booting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969529 Title: snapd failing to seed firefox on Pi 400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1969529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969529] Re: snapd failing to seed firefox on Pi 400
Thanks Brian! :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969529 Title: snapd failing to seed firefox on Pi 400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1969529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969515] Re: regression (Apr 9): `autopkgtest-build-lxd ubuntu-daily:jammy` times out, snapd.seeded.service seems to hang
*** This bug is a duplicate of bug 1969162 *** https://bugs.launchpad.net/bugs/1969162 Thanks Julian! I believe that this is the same bug as 1969162, but feel free to comment back if you believe that's not the case. ** This bug has been marked a duplicate of bug 1969162 bad interaction between snapd and update-notifier when snapd package is being upgraded -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969515 Title: regression (Apr 9): `autopkgtest-build-lxd ubuntu-daily:jammy` times out, snapd.seeded.service seems to hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1969515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969529] Re: snapd failing to seed firefox on Pi 400
Hi Dave, and thanks for reporting this. As you wrote about the "10 minutes", a bell rang in my head. :-) Could it be the same issue as https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1969162? The problem is that I don't think this should happen on a fresh install -- but on the other hand, I don't know exactly what operations happen on a newly installed system, so it may be that's related. Unfortunately I don't have access to the OOPS pages so I can't see the error details, but maybe you can have a look at the other bug and report back in case you notice some common patterns? ** Changed in: snapd (Ubuntu) Status: New => Triaged ** Changed in: snapd (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969529 Title: snapd failing to seed firefox on Pi 400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1969529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969162] Re: bad interaction between snapd and update-notifier when snapd package is being upgraded
Here's the PR: https://github.com/snapcore/snapd/pull/11680 And please forget what I wrote about our prerm script: that script is not stopping snapd, but only all the systemd service installed *by snap packages*, so it should be fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969162 Title: bad interaction between snapd and update-notifier when snapd package is being upgraded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1969162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969162] Re: bad interaction between snapd and update-notifier when snapd package is being upgraded
Hi Steve, thanks for reporting this, and for the hint on how to fix it. We currently have a shell script in our prerm script, which manually stops all our systemd units: https://github.com/snapcore/snapd/blob/master/packaging/ubuntu-16.04/snapd.prerm Do I correctly understand that your suggestion is not to do that? I'm actually a bit confused (though this is probably a question for my own team) why we have that prerm script, when we are already using dh_systemd_start in out debian/rules file: == override_dh_systemd_start: # Due to https://github.com/systemd/systemd/issues/8102 # debhelper supporting --remaining like behaviour here would # have been useful # (Re-)start socket first dh_systemd_start snapd.socket # Then service dh_systemd_start snapd.service # Then the rest dh_systemd_start $(filter-out snapd.socket snapd.service, $(shell ls debian/snapd/lib/systemd/system/)) == wouldn't this rule already cause the units to be stopped at the prerm step (we are using debhelper compatibility level 9)? Anyway, I'm soon going to propose a PR, so we can discuss over it. ** Bug watch added: github.com/systemd/systemd/issues #8102 https://github.com/systemd/systemd/issues/8102 ** Changed in: snapd (Ubuntu) Assignee: (unassigned) => Alberto Mardegan (mardy) ** Changed in: snapd (Ubuntu) Importance: Undecided => High ** Changed in: snapd (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969162 Title: bad interaction between snapd and update-notifier when snapd package is being upgraded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1969162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968908] Re: Snaps stop working when used through XRDP
Hi Pablo, and thanks for reporting this issue.
snapd requires the systemd user session to be running, but according to
the information you provided ("systemctl --user") that's not the case in
your xRDP session. I did a quick research, and it seems that there's
quite a few of similar problems reported by the xRDP community (and not
related to snapd), and the causes can be different.
You can have a look at these two issues (and the many issues linked to them):
- https://github.com/neutrinolabs/xrdp/issues/778
- https://github.com/neutrinolabs/xrdp/issues/1684
If you cannot find an answer, then I'd recommend you to file an issue on
the xRDP github project; hopefully people will be able to help.
I'm closing this bug report, because there's nothing we can do about it
from the snapd side. But if you manage to find a solution or a
workaround, you are very welcome to share it here too :-)
** Bug watch added: github.com/neutrinolabs/xrdp/issues #778
https://github.com/neutrinolabs/xrdp/issues/778
** Bug watch added: github.com/neutrinolabs/xrdp/issues #1684
https://github.com/neutrinolabs/xrdp/issues/1684
** Changed in: snapd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968908
Title:
Snaps stop working when used through XRDP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1968908/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967799] Re: firefox, chromium and other snap apps can't print
Just yesterday we landed a fix in snapd to address some issues with cups: https://github.com/snapcore/snapd/pull/11616 Unfortunately I do not know the details of the issue that this change solves, but maybe someone with more knowledge of cups can tell if that change could fix this bug too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967799 Title: firefox, chromium and other snap apps can't print To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1967799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951666] Re: /usr/share/libdrm/amdgpu.ids: No such file or directory
Hi Richard, I can confirm the issue: I do have the /usr/share/libdrm/amdgpu.ids file in my host, but it's probably not visible to the snap (and no AppArmor denial appears in the logs). But whether this means that GPU acceleration is disabled, this is something that would be better answered by the authors of (s)mplayer. It might not make any practical difference. As for the publisher verification, the whole point of snaps is to provide users a better security *without* the need for the users to trust the publishers, because snap applications run under confinement. If you run snap connections smplayer you can see what interfaces are used by smplayer (active ones are those with the plug and slot columns both set), and you can look up their meaning in https://snapcraft.io/docs/supported-interfaces Hope this helps :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951666 Title: /usr/share/libdrm/amdgpu.ids: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1951666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965468] Re: refresh app awareness: snapd thinks clion is running, but it isn't
The code managing this situation actually has the information about the PIDs of the running processes. Samuele, do you think we should print them as part of the error message? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965468 Title: refresh app awareness: snapd thinks clion is running, but it isn't To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1965468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959375] Re: [SRU] Please support group manipulation with "extrausers"
** Description changed: [Impact] * In order to use the microk8s snap in Ubuntu Core, one currently needs to be root. This is far from optimal, since normally (on desktop and server installations) this is not necessary. * This make it hard to provide consistent documentation on microk8s across all supported device, if we have to take the "sudo" command into account, and how file permissions for generated files might be affected. [Test Plan] The issue can be reproduced on Ubuntu Core 18, 20 and 22. The steps are as following (replace "" with the actual path of your Ubuntu Core image file: - qemu-system-x86_64 -enable-kvm -smp 2 -m 1500 \ - -netdev user,id=mynet0,hostfwd=tcp::8022-:22,hostfwd=tcp::8090-:80 \ - -device virtio-net-pci,netdev=mynet0 \ - -drive file=,format=raw + qemu-system-x86_64 -enable-kvm -smp 2 -m 1500 \ + -netdev user,id=mynet0,hostfwd=tcp::8022-:22,hostfwd=tcp::8090-:80 \ + -device virtio-net-pci,netdev=mynet0 \ + -drive file=,format=raw - + After configuring your account, connect to youd device via SSH: + ssh @localhost -p 8022 + + And issue these commands + + sudo snap install microk8s --channel=latest/edge/stable + + # microk8s is going to eat up all your disk space, so stop it as soon + # as the prompt comes back: + sudo microk8s stop + + # Add your user to the microk8s group + sudo usermod -G snap_microk8s $(whoami) + + The last command will fail unless this bug is fixed. If the bug is + fixed, the command will succeed, and after logging out and in again, you + can verify that you've been added to the snap_microk8s group by running + the "groups" command. + + + [Where problems could occur] + + * The patch only touches error code paths and adds a fallback mechanism + in them. Therefore, "normal" operations, where these commands would have + succeeded before, will not be affected at all. + + * In those cases when usermod fails because it failed to find or load + the requested user/group, we reset the user/group database paths to our + writable user/group databases, and retry the operation. Note that the + path for our database is hardcoded in the program source, so the + security risk seems contained. We do not add additional command-line + parameters. + + + [Other Info] Original bug description Currently doing something like: sudo usermod -a -G snap_microk8s dbeamonte on a Ubuntu Core system will fail with usermod: /etc/group.15965: Read-only file system This is because the existing usermod patches to detect the extrausers file do not cover this case. Attached a simple patch that enables it. I will give this patch a test run in our image PPA for jammy and if things look good I would like upload to 22.04 and SRU for 20.04 and 18.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959375 Title: [SRU] Please support group manipulation with "extrausers" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959375] Re: [SRU] Please support group manipulation with "extrausers"
** Description changed: + [Impact] + + * In order to use the microk8s snap in Ubuntu Core, one currently needs + to be root. This is far from optimal, since normally (on desktop and + server installations) this is not necessary. + + * This make it hard to provide consistent documentation on microk8s + across all supported device, if we have to take the "sudo" command into + account, and how file permissions for generated files might be affected. + + + [Test Plan] + + The issue can be reproduced on Ubuntu Core 18, 20 and 22. The steps are + as following (replace "" with the actual path of your Ubuntu + Core image file: + + qemu-system-x86_64 -enable-kvm -smp 2 -m 1500 \ + -netdev user,id=mynet0,hostfwd=tcp::8022-:22,hostfwd=tcp::8090-:80 \ + -device virtio-net-pci,netdev=mynet0 \ + -drive file=,format=raw + + + + + Original bug description + + Currently doing something like: - sudo usermod -a -G snap_microk8s dbeamonte + sudo usermod -a -G snap_microk8s dbeamonte on a Ubuntu Core system will fail with - usermod: /etc/group.15965: Read-only file system + usermod: /etc/group.15965: Read-only file system This is because the existing usermod patches to detect the extrausers file do not cover this case. Attached a simple patch that enables it. I will give this patch a test run in our image PPA for jammy and if things look good I would like upload to 22.04 and SRU for 20.04 and 18.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959375 Title: [SRU] Please support group manipulation with "extrausers" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959375] Re: [SRU] Please support group manipulation with "extrausers"
Marking as Invalid for Impish, since the issue only happens with a read- only rootfs like we use in Ubuntu Core, and UC is only based on LTS releases. ** Changed in: shadow (Ubuntu Impish) Status: New => Won't Fix ** Changed in: shadow (Ubuntu Impish) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959375 Title: [SRU] Please support group manipulation with "extrausers" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959375] Re: [SRU] Please support group manipulation with "extrausers"
** Patch added: "debdiff for Bionic" https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+attachment/5568639/+files/0001-Bionic-patch-for-LP-1959375.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959375 Title: [SRU] Please support group manipulation with "extrausers" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959375] Re: [SRU] Please support group manipulation with "extrausers"
** Patch added: "debdiff for Jammy" https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+attachment/5568614/+files/0001-Jammy-changes-for-LP-1797786.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959375 Title: [SRU] Please support group manipulation with "extrausers" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959375] Re: [SRU] Please support group manipulation with "extrausers"
** Patch removed: "debdiff for Focal" https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+attachment/5568607/+files/0001-Add-automatic-detection-of-extrausers-for-usermod-G.patch ** Patch added: "debdiff for Focal" https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+attachment/5568613/+files/0001-Add-automatic-detection-of-extrausers-for-usermod-G.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959375 Title: [SRU] Please support group manipulation with "extrausers" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959375] Re: [SRU] Please support group manipulation with "extrausers"
** Patch removed: "Patch for focal" https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+attachment/5568568/+files/0001-Add-automatic-detection-of-extrausers-for-usermod-G.patch ** Patch added: "debdiff for Focal" https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+attachment/5568607/+files/0001-Add-automatic-detection-of-extrausers-for-usermod-G.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959375 Title: [SRU] Please support group manipulation with "extrausers" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959375] Re: [SRU] Please support group manipulation with "extrausers"
I tested a newer version of the patch that Michael sent me, and I verify that it works properly :-) I'm attaching it here; it includes changes to the 1015_add_zsys_support.patch, but that's only as a result of a quilt refresh, since the patch did not apply cleanly anymore (since src/usermod.c was modified in our patch before). I've been testing this on Focal. ** Patch added: "Patch for focal" https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+attachment/5568568/+files/0001-Add-automatic-detection-of-extrausers-for-usermod-G.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959375 Title: [SRU] Please support group manipulation with "extrausers" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962718] Re: Firefox snap crashes on every upgrade
Thanks Roman, we are working on it in https://github.com/snapcore/snapd/pull/10676 ** Changed in: snapd (Ubuntu) Status: New => Confirmed ** Changed in: snapd (Ubuntu) Importance: Undecided => High ** Changed in: snapd (Ubuntu) Assignee: (unassigned) => Alberto Mardegan (mardy) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962718 Title: Firefox snap crashes on every upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1962718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961418] Re: snap failed to run with '/usr/bin/snap wait system seed.loaded'
Hi Gene, thanks for reporting this! I have no idea what the problem might be, but please try this: 1) Since you are already root, try not using sudo (though I'm almost sure that this is not causing any issues) 2) Please post the output of these commands (after re-trying to enable livepatch): systemctl status snapd systemctl status snapd.socket journalctl -b -u snapd ** Changed in: snapd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961418 Title: snap failed to run with '/usr/bin/snap wait system seed.loaded' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1961418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961365] Re: 2.54.3+18.04 update on bionic breaks fish shell
Hi Xavier, thanks for reporting this issue, and sorry for the regression! Do you think that this is the same bug as https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1960972? Comment #2 in that bug has a workaround; can you please try and see if that helps you too? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961365 Title: 2.54.3+18.04 update on bionic breaks fish shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1961365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959417] Re: unable to use jupyter-notebook package with snap'd browsers like firefox or chromium
Unfortunately this is by design: the snapd "home" interface allows access to all files in a user's home, except from the "snap" dir and all toplevel hidden directories. So, ~/.i/love/dot/folders is not allowed, but ~/i/.love/dot/folders is. The point is that toplevel hidden directories in your home dir generally do not contain user data, but configuration, cache, and other data which we generally don't want applications to mess with. I wonder if we should make an exception for "~/.local/", though, since that generally contains data which could potentially be useful for applications. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959417 Title: unable to use jupyter-notebook package with snap'd browsers like firefox or chromium To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1959417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935667] Re: snapd FTBFS when built with libfuse3-dev
Hi Christian, we already merged support of fuse3 in master; Now we have a dependency on `libfuse-dev | libfuse3-dev`, and it should just be a matter of rebuilding the code. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935667 Title: snapd FTBFS when built with libfuse3-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1935667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851250] Re: [snap] chromium-browser snap cannot upload files outside ~
Here are the changes we'd need to backport to Focal in order to fix this bug there: To package xdg-desktop-portal-gtk: - https://github.com/flatpak/xdg-desktop-portal-gtk/commit/920afdde7afc023e77ecfeb4e174cb42f22cbfe3 To package xdg-desktop-portal: - https://github.com/flatpak/xdg-desktop-portal/commit/c616b491fe0ac67f78a14bcaf0d3a150bfadfd82 - https://github.com/flatpak/xdg-desktop-portal/commit/00b28db5ca45bcbdfea0ddfff8447a3f8836bfd9 - https://github.com/flatpak/xdg-desktop-portal/commit/80915e6a5bd9466c17d46011bf6d16b4a57118a0 - https://github.com/flatpak/xdg-desktop-portal/commit/470cc132f4993ebbc514eaef6ad7af8000c388ba I'll check with the Release team to see how they feel about this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851250 Title: [snap] chromium-browser snap cannot upload files outside ~ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851250] Re: [snap] chromium-browser snap cannot upload files outside ~
Hi Olivier, let me take some time to investigate what are the changes to the next major version, because if we are lucky and they are small and safe, we could really think about a SRU. At least for 20.04, which is going to be supported for quite a few years from now. Also, let's keep in mind that Firefox and other apps will also be affected by this (version 3 of the XDG spec add the "directory mode" to the file chooser, which is likely useful to many applications). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851250 Title: [snap] chromium-browser snap cannot upload files outside ~ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851250] Re: [snap] chromium-browser snap cannot upload files outside ~
Hi Olivier! I tried on hirsute, and it's working :-) Then I guess that the only series still supported by Canonical and affected by this bug are the LTSes. ** Also affects: chromium-browser (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: chromium-browser (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: chromium-browser (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851250 Title: [snap] chromium-browser snap cannot upload files outside ~ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851250] Re: [snap] chromium-browser snap cannot upload files outside ~
After some good hints from Oliver I did some investigation on this issue. Indeed it looks like the chromium snap is doing the right thing: it first checks if the D-Bus service "org.freedesktop.portal.Desktop" is running (if not, it falls back on calling ListActivatableNames, which is not ideal because this currently gets blocked by AppArmor -- but in my tests the call to NameHasOwner works, so this path is not even taken), and then it checks that the "version" property on the "org.freedesktop.portal.FileChooser" interface is at least 3. Unfortunately, on my Focal system this version is 2 (version 3 was released just about at the time when Focal was: https://github.com/flatpak/xdg-desktop- portal/commit/00b28db5ca45bcbdfea0ddfff8447a3f8836bfd9), so the portal dialog is not used. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851250 Title: [snap] chromium-browser snap cannot upload files outside ~ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954711] Re: application can't open a window without network-manager connection
Hi Tobias, thank you for getting in touch! I just tried installing the
manuskript snap, and verified that indeed it does not start. After a few
seconds it prints this line:
Qt: Session management error: Could not open network socket
I'm not sure where this error comes from; I suspected that it could be
coming from the QSessionManager class, but a quick grep in manuskript
source code did not find anything (though maybe it's being used by some
of manuskript's dependencies?).
A useful tool to debug such cases is `snappy-debug`: you just start it
with the -f flag, and then start the application you want to debug:
snappy-debug -f
This will start monitoring the system log for error messages, and print
out some information that might be useful to fix the issue. In our case,
it prints:
===
= AppArmor =
Time: Dec 14 09:50:27
Log: apparmor="DENIED" operation="capable"
profile="/snap/core/11993/usr/lib/snapd/snap-confine" pid=16204
comm="snap-confine" capability=4 capname="fsetid"
Capability: fsetid
Suggestions:
* adjust program to not require 'CAP_FSETID' (see 'man 7 capabilities')
* add one of 'account-control' to 'plugs'
* do nothing if program otherwise works properly
= AppArmor =
Time: Dec 14 09:50:56
Log: apparmor="DENIED" operation="open" profile="snap.manuskript.manuskript"
name="/proc/16204/mounts" pid=16204 comm="python3" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=1000
File: /proc/16204/mounts (read)
Suggestions:
* adjust program to not access '@{PROC}/@{pid}/mounts'
* add one of 'mount-observe, network-control' to 'plugs'
= Seccomp =
Time: Dec 14 09:50:58
Log: auid=1000 uid=1000 gid=1000 ses=3 pid=16204 comm="python3"
exe="/snap/manuskript/467/usr/bin/python3.6" sig=0 arch=c03e 41(socket)
compat=0 ip=0x7efe6992dd57 code=0x5
Syscall: socket
Suggestions:
* add account-control (if using NETLINK_AUDIT)
* add audio-playback (if using NETLINK_KOBJECT_UEVENT)
* add bluetooth-control (if using AF_{ALG,BLUETOOTH})
* add firewall-control (if using
NETLINK_{FIREWALL,IP6_FW,NETFILTER,NF_LOG,ROUTE})
* add hardware-observe (if using NETLINK_{GENERIC,KOBJECT_UEVENT})
* add netlink-audit (if using NETLINK_AUDIT)
* add netlink-connector (if using NETLINK_CONNECTOR)
* add network (if using AF_INET{,6}, AF_CONN, NETLINK_ROUTE)
* add network-bind (if using AF_INET{,6}, NETLINK_ROUTE)
* add network-control (if using
AF_{APPLETALK,BRIDGE,INET,INET6,IPX,PACKET,PPPOX,SNA},
NETLINK_{DNRTMSG,FIB_LOOKUP,GENERIC,INET_DIAG,ISCSI,KOBJECT_UEVENT,RDMA,ROUTE,XFRM})
* add network-observe (if using SOCK_RAW, AF_INET{,6}),
NETLINK_{GENERIC,INET_DIAG,KOBJECT_UEVENT,ROUTE})
* add raw-usb (if using NETLINK_KOBJECT_UEVENT)
* add time-control (if using NETLINK_AUDIT)
* add unity7 (if using NETLINK_KOBJECT_UEVENT)
* add upower-observe (if using NETLINK_KOBJECT_UEVENT)
* add x11 (if using NETLINK_KOBJECT_UEVENT)
= AppArmor =
Time: Dec 14 09:50:58
Log: apparmor="DENIED" operation="dbus_method_call" bus="system"
path="/org/freedesktop/NetworkManager"
interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send"
name="org.freedesktop.NetworkManager" pid=16204
label="snap.manuskript.manuskript" peer_pid=3317 peer_label="unconfined"
DBus access
Suggestion:
* try adding one of 'network-manager, network-manager-observe' to 'plugs'
===
There are a few things we can do at this point. The first one, in my
opinion, is to figure out where in manuskript code these operations are
triggered, and understand what they are used for, and whether they are
really needed (maybe there are other ways to accomplish the same task).
Once we have decided that all these operations are necessary, we need to
find out which of the denials above is actually preventing the
application from working: it's very well possible that not all of the
denials are fatal, and maybe we just need to fix one of them. The
instructions given by Ian in the forum thread you linked to
(https://forum.snapcraft.io/t/request-for-auto-connection-of-jami-
network-manager/22833/17) can be adapted here too.
Please let me know if you manage to find out what exactly is blocking
manuskript, and then we can discuss on how to proceed.
Also related:
- https://github.com/olivierkes/manuskript/issues/678
- https://github.com/olivierkes/manuskript/issues/900
** Bug watch added: github.com/olivierkes/manuskript/issues #678
https://github.com/olivierkes/manuskript/issues/678
** Bug watch added: github.com/olivierkes/manuskript/issues #900
https://github.com/olivierkes/manuskript/issues/900
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954711
Title:
application can't open a window without network-manager connection
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1954711/+subscriptions
--
ubuntu-bugs
[Bug 1851250] Re: [snap] chromium-browser snap cannot upload files outside ~
Hi Olivier (or whoever knows about Chromium), I see that the upstream support for the XDG file selector portal landed somewhere in July this year (https://chromium- review.googlesource.com/c/chromium/src/+/2992214/), but I cannot find information on which Chromium version contains this change. I'm using chromium from the "latest/stable" channel (96.0.4664.45), and according to a quick test with d-feet, it appears that the FileChooser method is working on my desktop -- but I still cannot upload files stored in /tmp. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851250 Title: [snap] chromium-browser snap cannot upload files outside ~ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1650688] Re: timedatectl set-timezone fails on UC16
** Patch added: "Support-system-image-read-only-etc.patch" https://bugs.launchpad.net/snappy/+bug/1650688/+attachment/5543088/+files/Support-system-image-read-only-etc.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1650688 Title: timedatectl set-timezone fails on UC16 To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1650688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1650688] Re: timedatectl set-timezone fails on UC16
I can confirm that Ratchanan's patches work (well, I only tried the one on timedated, as the one on timedatectl is not essential to fix this bug). But I don't think that it should be treated separately from the existing patch we have, so I'm attaching a refreshed patch which includes Ratchanan's change. Still, we probably want to explore other solutions, since Dan (@ddstreet) is also right that carrying hacks for 7 years is something we should avoid doing. But I don't have many alternative ideas :-( Unfortunately, bind-mounting /etc/writable/localtime over /etc/localtime does not work, because when mounting, the kernel follows all symbolic links, so we end up bind- mounting the timezone file (for example "/usr/share/zoneinfo/Europe/Berlin") on top of itself :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1650688 Title: timedatectl set-timezone fails on UC16 To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1650688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950855] Re: Can't enable snap to print on a usb printer
We should be able to suppress the warnings by generating "deny" rules in snapd. What is important now to know is if the application can work even without the rules you manually added. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950855 Title: Can't enable snap to print on a usb printer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1950855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950634] Re: package snapd (not installed) failed to install/upgrade: installed snapd package post-removal script subprocess returned error exit status 1
This has been addressed in https://github.com/snapcore/snapd/pull/11055 ** Changed in: snapd (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950634 Title: package snapd (not installed) failed to install/upgrade: installed snapd package post-removal script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1950634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18
Thanks Lukas! It's very likely that there are several issues in this area, because while I can confirm that your latest image fixes the reproducer I pasted before (in the Google cloud, too), the spread test failure is still reproducible with the "tests/main/services-disabled- kept-happy" test. I need to have a closer look at this test case, to understand what exact steps snapd is taking, and see if we can again find a reproducer without involving snapd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949089 Title: systemd randomly fails to activate mount units in Ubuntu Core 18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950634] Re: package snapd (not installed) failed to install/upgrade: installed snapd package post-removal script subprocess returned error exit status 1
Thanks David! (feel free to ignore the following: I'm just writing some notes here for my colleagues, as a starting point to fix the issue) Indeed, out post-remove script (located in debian/snapd.postrm in the source tree) does echo "Final directory cleanup" for d in "/snap/bin" "/snap" "/var/snap"; do # Force remove due to directories for old revisions could still exist rm -rf "$d" if [ -d "$d" ]; then echo "Cannot remove directory $d" fi done which leaves open the possibility of a failed "rm" causing the whole script to fail. The dpkg terminal log provided by David clearly show that this was the case: ``` Final directory cleanup rm: cannot remove '/var/snap': Device or resource busy dpkg: error processing package snapd (--purge): installed snapd package post-removal script subprocess returned error exit status 1 ``` Since the error is logged anyway, I think we should not fail here and instead proceed no matter what. ** Changed in: snapd (Ubuntu) Importance: Undecided => Low ** Changed in: snapd (Ubuntu) Assignee: (unassigned) => Alberto Mardegan (mardy) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950634 Title: package snapd (not installed) failed to install/upgrade: installed snapd package post-removal script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1950634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950634] Re: package snapd (not installed) failed to install/upgrade: installed snapd package post-removal script subprocess returned error exit status 1
** Changed in: snapd (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950634 Title: package snapd (not installed) failed to install/upgrade: installed snapd package post-removal script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1950634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950855] Re: Can't enable snap to print on a usb printer
Hi Hadmut, and thanks for reporting this. Could you please paste the full journald audit log (`journald -t audit`)? I'd like to see if those AppArmor denials you are seeing are the only ones, or if there's more. I cannot see any interface in snapd that would grant access to the "/sys/devices/pnp*" tree; but it might also be that these warnings are not fatal, and cura-slicer proceeds to do other operations? ** Changed in: snapd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950855 Title: Can't enable snap to print on a usb printer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1950855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950634] Re: package snapd (not installed) failed to install/upgrade: installed snapd package post-removal script subprocess returned error exit status 1
Thanks for the information, David. But is apt happy now, or is it still complaining about the snapd package state? What happens if you run "apt -f install"? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950634 Title: package snapd (not installed) failed to install/upgrade: installed snapd package post-removal script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1950634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18
One more update: I verified that the steps from comment #17 can be used to reproduce the issue in an Ubuntu Core image started in qemu, and without using the spread. I verified it with the 20211105 image provided by Lukas in https://people.ubuntu.com/~slyon/uc18/ To reproduce it, start the image in QEMU: qemu-system-x86_64 -enable-kvm -smp 2 -m 1500 \ -netdev user,id=mynet0,hostfwd=tcp::8022-:22,hostfwd=tcp::8090-:80 \ -device virtio-net-pci,netdev=mynet0 \ -drive file=~/Downloads/uc18-20211105+systemd+3G.img,format=raw \ -drive file=/usr/share/OVMF/OVMF_CODE.fd,if=pflash,format=raw,unit=0,readonly=on configure it as usual, and install a snap. Then: sudo snap install hello-world sudo systemctl start 'snap-hello\x2dworld-29.mount' sudo systemctl daemon-reload sudo systemctl stop 'snap-hello\x2dworld-29.mount' sudo systemctl start 'snap-hello\x2dworld-29.mount' The last command will hang for 90 seconds, after which the logs (`sudo journalctl -xe`) will say: ``` Nov 15 06:10:20 localhost systemd[1]: dev-loop6.device: Job dev-loop6.device/start timed out. Nov 15 06:10:20 localhost systemd[1]: Timed out waiting for device /dev/loop6. -- Subject: Unit dev-loop6.device has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Unit dev-loop6.device has failed. -- -- The result is RESULT. Nov 15 06:10:20 localhost systemd[1]: Dependency failed for Mount unit for hello-world, revision 29. -- Subject: Unit snap-hello\x2dworld-29.mount has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Unit snap-hello\x2dworld-29.mount has failed. -- -- The result is RESULT. Nov 15 06:10:20 localhost systemd[1]: snap-hello\x2dworld-29.mount: Job snap-hello\x2dworld-29.mount/start failed with result 'dependency'. Nov 15 06:10:20 localhost systemd[1]: dev-loop6.device: Job dev-loop6.device/start failed with result 'timeout'. ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949089 Title: systemd randomly fails to activate mount units in Ubuntu Core 18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950634] Re: package snapd (not installed) failed to install/upgrade: installed snapd package post-removal script subprocess returned error exit status 1
Hi David! I'm sorry to read that you had this bad experience. What is the current situation? I see from the logs that the error occurred because the snapd post- removal script found that the /var/snap directory was in use. Can you please check what are its contents now (you could run `tree /var/snap` to find out, or just `find /var/snap`, if "tree" is not installed)? Also please run these commands for me, and paste the results: - ls /snap/ - ls /etc/systemd/system/snap* ** Changed in: snapd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950634 Title: package snapd (not installed) failed to install/upgrade: installed snapd package post-removal script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1950634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18
Might be related to https://github.com/systemd/systemd/issues/11342 ** Bug watch added: github.com/systemd/systemd/issues #11342 https://github.com/systemd/systemd/issues/11342 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949089 Title: systemd randomly fails to activate mount units in Ubuntu Core 18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18
An update to the comment above. We have found out a sequence of commands that seems to reproduce the issue reliably: in the spread session started by the command from the comment above, if you type this: systemctl stop 'snap-disabled\x2dsvcs\x2dkept-x1.mount' systemctl daemon-reload # The two commands above are just to ensure that the unit is in the unmounted state systemctl start 'snap-disabled\x2dsvcs\x2dkept-x1.mount' systemctl daemon-reload systemctl stop 'snap-disabled\x2dsvcs\x2dkept-x1.mount' systemctl start 'snap-disabled\x2dsvcs\x2dkept-x1.mount' The last command will hang for 90 seconds, after which the job will fail and `journalctl -xe` will show that it failed because systemd timed out while activating a loop device. In reality, the loop device is already there and is available, but somehow the `deamon-reload` operation broke the internal status. If you remove the line with `systemctl daemon-reload` (or, on the other hand, add one such line even after the `stop` command), then everything proceeds normally. I'm EOD now, but tomorrow I'll verify if this happens on classic too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949089 Title: systemd randomly fails to activate mount units in Ubuntu Core 18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18
> can you provide steps on how this is reproducable then? So far we have not been able to isolate the problem, so the only way so far is to run the spread tests from the snapd directory (from the master branch): spread -debug -repeat 20 google:ubuntu- core-18-64:tests/main/services-disabled-kept-happy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949089 Title: systemd randomly fails to activate mount units in Ubuntu Core 18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18
I'm coming with bad news. Today both me and Michael have individually retested both snaps you provided (20211102 and 20211105), and the bug happened with both of them. It's possible that yesterday Michael accidentally used QEMU for his tests, without realizing (and in QEMU it seems that this bug is not reproducible). Here are the spread logs (plus "journalctl -xe") obtained in the 21211105 snap: https://paste.ubuntu.com/p/CnnyXNC2Tt/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949089 Title: systemd randomly fails to activate mount units in Ubuntu Core 18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949084] Re: problem in dispaly menus with chromium snap
Interestingly, I cannot open the image. Abdenour, can you please try uploading again after renaming the file to a different name? I wonder if it's because of the accented letters. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949084 Title: problem in dispaly menus with chromium snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1949084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949089] [NEW] systemd randomly fails to activate mount units in Ubuntu Core 18
Public bug reported: Since a month or so, we've been seeing random failures in our snapd spread tests where systemd could not start the mount unit associated with a snap because of a failed dependency. The issue is described in the comments to PR https://github.com/snapcore/snapd/pull/10935, but I'll summarize it here. When starting a snap, snapd creates a mount unit to mount the snap's squashfs (the template is https://github.com/snapcore/snapd/blob/release/2.53/systemd/systemd.go#L1186-L1205). The snapd asks systemd to reload the configuration, and starts the mount unit. The failure we've observed is that sometimes systemd decides to stop our mount unit (search for "Unmounting Mount unit for test-snapd-svc-flip- flop" in the attached log), and then tries to reactivate it again, and at that point it fails. When I asked for help, Lukas pointed out that the latest update contains a patch that is related to reload handling and mount units: http://launchpadlibrarian.net/555420796/systemd_237-3ubuntu10.51_237-3ubuntu10.52.diff.gz (the patch itself is better visible at https://github.com/systemd/systemd/commit/f0831ed2a03fcef582660be1c3b1a9f3e267e656). When looking at the systemd git log, though, I noticed another patch that was applied shortly after this one, which also seems related but was not backported: https://github.com/systemd/systemd/commit/04eb582acc203eab0bc5c2cc5e13986f16e09df0 Since the stopping of our mount unit happens immediately after a systemd reload, it actually seems very likely that the inclusion of f0831ed2a03fcef582660be1c3b1a9f3e267e656 in the systemd update is what causes our woes (though, indeed, the issue is not reliably reproducible, so we cannot be sure). ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: regression-update ** Attachment added: "journald log" https://bugs.launchpad.net/bugs/1949089/+attachment/5536819/+files/journal.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949089 Title: systemd randomly fails to activate mount units in Ubuntu Core 18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873550] Re: Snappy daemon reaches 1min30s timeout during shutdown process
I believe that this is the same issue as #1946656, which will be fixed in snapd 2.53: https://github.com/snapcore/snapd/commit/da1caa8b12c0f839320f29012b4565d1f702eb42 ** Changed in: snapd (Ubuntu) Assignee: (unassigned) => Alberto Mardegan (mardy) ** Changed in: snapd (Ubuntu) Importance: Undecided => High ** Changed in: snapd (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873550 Title: Snappy daemon reaches 1min30s timeout during shutdown process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1873550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942431] Re: Latest chromium crashes after opening Yandex search page
I closed this too soon. The crash still happens, but I cannot reproduce it reliably: there are moments when any search leads to a crash, but after some time it stops crashing and continues working for hours. From the console, the crash appears like this: == $ chromium-browser [456694:456694:0910/101452.681280:ERROR:gpu_init.cc(441)] Passthrough is not supported, GL is swiftshader [456696:456718:0910/101501.133462:ERROR:broker_posix.cc(40)] Recvmsg error: Connection reset by peer (104) [456696:456718:0910/101501.135073:ERROR:broker_posix.cc(110)] Error sending sync broker message: Broken pipe (32) [456696:456718:0910/101501.135349:ERROR:broker_posix.cc(110)] Error sending sync broker message: Broken pipe (32) [456696:456718:0910/101501.136203:ERROR:broker_posix.cc(110)] Error sending sync broker message: Broken pipe (32) Trace/breakpoint trap == ** Changed in: chromium-browser (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942431 Title: Latest chromium crashes after opening Yandex search page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1942431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942431] Re: Latest chromium crashes after opening Yandex search page
Wow, I wanted to provide an example URL, but now it doesn't crash anymore. Before, I had it reliably crashing several times on any Yandex search result page. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942431 Title: Latest chromium crashes after opening Yandex search page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1942431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942431] Re: Latest chromium crashes after opening Yandex search page
Closing, will reopen if I happen to reproduce it again. :-) ** Changed in: chromium-browser (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942431 Title: Latest chromium crashes after opening Yandex search page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1942431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942431] [NEW] Latest chromium crashes after opening Yandex search page
Public bug reported: After upgrading to `93.0.4577.63`, Chromium crashes after opening Yandex search pages: the page is briefly shown, and then immediately afterwards Chromium crashes. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942431 Title: Latest chromium crashes after opening Yandex search page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1942431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930995] Re: snapd too heavy for lubuntu
snapd could be changed not to be run all the time: the `snap` command could start snapd if it's not running, and this would address the first and third points mentioned by Ian (because when a snap program is run, what is first executed is actually /usr/bin/snap), and it should be possible to handle automatic updates by running some snap command at some defined moments. This would come at a cost, though: the startup times of snap applications could be considerably longer if snapd has to be cold started. It may be that the performance impact of starting snapd is negligible on faster machines, but if the whole point of this operation is to improve support for lubuntu, which is typically run on older machines, then changing the snapd behaviour to start on demand might not be doing a favour to lubuntu users. We might want to sit down and weigh pros and cons, but at first sight the gain seems not to be worth the efforts. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930995 Title: snapd too heavy for lubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1930995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898415] [NEW] [snap] Migration script can be run multiple times in parallel
Public bug reported: I just updated to Ubuntu 20.04, and when I started Chromium nothing happened. Since I am a dumb user, I clicked the Chromium icon three times, thinking that maybe the first clicks hadn't been registered. Chromium finally started after a while, but at that point I noticed that there were other two instances of the wrapper script running, first both doing a `du` and later a `cp` of the Chromium config into the snap/ folder. The script should probably check if another instance is already running and not try to migrate all the chrome config again. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898415 Title: [snap] Migration script can be run multiple times in parallel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1898415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795115] [NEW] Package should be marked "Multi-Arch: foreign"
Public bug reported: Similarly to python3-setuptools, which was handled in https://bugs.launchpad.net/ubuntu/+source/doxyqml/+bug/1585517, all the Python packages should be marked as "Multi-Arch: foreign" to allow proper cross installation. ** Affects: python-flake8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795115 Title: Package should be marked "Multi-Arch: foreign" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-flake8/+bug/1795115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1502820] Re: Battery graph not showing full history
This is now fixed in Ubports :-) https://github.com/ubports/system-settings/pull/81 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1502820 Title: Battery graph not showing full history To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1502820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793382] [NEW] Add aethercast support in AppArmor file
Public bug reported: Canonical modified the AppArmor policy in order to make authercast work: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-phone-overlay/+files/isc-dhcp_4.3.1-5ubuntu2_4.3.1-5ubuntu2.4~overlay1.diff.gz (only the first chunk of the patch is relevant to this issue) This was added to the package we were using in the phone overlay PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable- phone-overlay/+packages?batch=75=75=75 Now we need the same in Ubports, but it would be convenient if we added this in Ubuntu, to reduce the delta. ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New ** Description changed: Canonical modified the AppArmor policy in order to make authercast work: - https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable- - phone-overlay/+files/isc- - dhcp_4.3.1-5ubuntu2_4.3.1-5ubuntu2.4~overlay1.diff.gz + https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-phone-overlay/+files/isc-dhcp_4.3.1-5ubuntu2_4.3.1-5ubuntu2.4~overlay1.diff.gz + (only the first chunk of the patch is relevant to this issue) This was added to the package we were using in the phone overlay PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable- phone-overlay/+packages?batch=75=75=75 Now we need the same in Ubports, but it would be convenient if we added this in Ubuntu, to reduce the delta. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793382 Title: Add aethercast support in AppArmor file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1793382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776183] [NEW] pkg-config file is not installed
Public bug reported: The projects has a pkg-config file, but it's not present in the Ubuntu package. ** Affects: log4cplus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776183 Title: pkg-config file is not installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/log4cplus/+bug/1776183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1070873] Re: kde-telepathy, impossible to connect to gmail accounts
Hi Brandon (and everyone else experiencing the signin-ui crash), in order to fix this bug I need to get the exact backtrace of the signon-ui program. Could you please run apport-bug /var/crash/...[pick the signon-ui crash file] from a terminal, so that launchpad can analyze the crash? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1070873 Title: kde-telepathy, impossible to connect to gmail accounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meta-kde-telepathy/+bug/1070873/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1695928] Re: Please remove obsolete UOA packages
As far as I can see, there is no plan to remove these packages (please confirm,
Jeremy). And indeed I'm going to maintain these packages in the future as well:
libsignon-{qt,glib}, signond, libaccounts-{qt,glib}
I'm also willing to maintain other packages mentioned in this bug, such
as online-accounts-api and ubuntu-system-settings-online-accounts, but
since these are effectively used only on the phone, I'll be maintaining
them as part of the ubports project and I have no objection on removing
them from the archive.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1695928
Title:
Please remove obsolete UOA packages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center-signon/+bug/1695928/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1676893] Re: Inform client if ContentHub service is not available
** Changed in: content-hub (Ubuntu) Status: New => In Progress ** Changed in: content-hub (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1676893 Title: Inform client if ContentHub service is not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1676893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1676893] Re: Inform client if ContentHub service is not available
** Changed in: content-hub (Ubuntu) Assignee: (unassigned) => Alberto Mardegan (mardy) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1676893 Title: Inform client if ContentHub service is not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1676893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1676893] [NEW] Inform client if ContentHub service is not available
Public bug reported: An app using the Content Hub QML API might have the need to know whether service is actually available, in order to fall back to other means if it isn't. This is especially relevant for snaps: if the snap uses the content from ubuntu-app-platform, the QML module of the ContentHub will be available, but this doesn't guarantee that the CH service is running. It might not be installed (for example, in another distro), not running or maybe not reachable due to confinement. I propose adding a "valid" property to the ContentHub singleton which would tell whether the service is available. ** Affects: content-hub (Ubuntu) Importance: Undecided Assignee: Alberto Mardegan (mardy) Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1676893 Title: Inform client if ContentHub service is not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1676893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1676219] Re: package account-plugin-google 0.12+15.04.20150415.1-0ubuntu2 failed to install/upgrade: trying to overwrite '/usr/share/accounts/services/google-im.service', which is also in package
*** This bug is a duplicate of bug 1451728 *** https://bugs.launchpad.net/bugs/1451728 ** This bug has been marked a duplicate of bug 1451728 [master] kde-config-telepathy-accounts package install error -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1676219 Title: package account-plugin-google 0.12+15.04.20150415.1-0ubuntu2 failed to install/upgrade: trying to overwrite '/usr/share/accounts/services /google-im.service', which is also in package kde-config-telepathy- accounts 4:15.08.2-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1676219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1673984] Re: Can not add google account any more (Zesty)
Fix available here, waiting for QA: https://bileto.ubuntu.com/#/ticket/2608 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1673984 Title: Can not add google account any more (Zesty) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1673984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1675273] Re: Can't add online account
The "Add account" button should simply show you a list of account providers on the right side of the system settings panel. Then you need to click on one of them, in order to start the account creation. If that does not work, please provide a screenshot. ** Changed in: account-plugins (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1675273 Title: Can't add online account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1675273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1029289] Re: Need to authorize my google account each time I boot the computer
Eugene (and others), if you are still affected by this bug, please follow bug 1666285 instead. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1029289 Title: Need to authorize my google account each time I boot the computer To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1029289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1673984] Re: Can not add google account any more (Zesty)
** Branch linked: lp:~mardy/signon-ui/unity-crash-1673984 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1673984 Title: Can not add google account any more (Zesty) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1673984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1673984] Re: Can not add google account any more (Zesty)
Thanks for the report, Alam! I can confirm this. Here's the stack trace: signon: browser-request.cpp 585 buildDialog Dialog was built signon: request.cpp 137 setWindow Requesting window embedding Thread 1 "signon-ui" received signal SIGSEGV, Segmentation fault. QWindow::show (this=0x0) at kernel/qwindow.cpp:1851 1851kernel/qwindow.cpp: No such file or directory. (gdb) bt #0 0x740bf8de in QWindow::show() (this=0x0) at kernel/qwindow.cpp:1851 #1 0x5558b5e2 in SignOnUi::RequestPrivate::setWindow(QWindow*) (this=this@entry=0x558d0070, window=0x0) at request.cpp:139 #2 0x5558b7e0 in SignOnUi::Request::setWidget(QWidget*) (this=, widget=0x558d07f0) at request.cpp:308 #3 0x5556c25b in SignOnUi::BrowserRequestPrivate::start() (this=0x558d01f0) at browser-request.cpp:599 #4 0x5558d794 in SignOnUi::ServicePrivate::runQueue(QQueue<SignOnUi::Request*>&) (this=this@entry=0x558ba200, queue=...) at service.cpp:141 #5 0x5558da62 in SignOnUi::ServicePrivate::enqueue(SignOnUi::Request*) (this=this@entry=0x558ba200, request=request@entry=0x558d03a0) at service.cpp:126 #6 0x5558def0 in SignOnUi::Service::queryDialog(QMap<QString, QVariant> const&) (this=0x558ba790, parameters=...) at service.cpp:227 #7 0x55593571 in SignOnUi::Service::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=, _c=, _id=, _a=0x7fffd360) at moc_service.cpp:107 #8 0x555936d8 in SignOnUi::Service::qt_metacall(QMetaObject::Call, int, void**) (this=0x558ba790, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x7fffd360) at moc_service.cpp:169 #9 0x73d56650 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #10 0x73d5a4fd in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #11 0x73d5aadc in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #12 0x73d5d5ae in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #13 0x721bb359 in QObject::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7484835c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7484fb11 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7218e8a0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7219102d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x721e2b03 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x72ca2377 in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x72ca25e0 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x72ca268c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x721e2f0f in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7218c88a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x72194ffc in QCoreApplication::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x55566b03 in main(int, char**) (argc=, argv=) at main.cpp:99 ** Package changed: account-plugins (Ubuntu) => signon-ui (Ubuntu) ** Changed in: signon-ui (Ubuntu) Importance: Undecided => Critical ** Changed in: signon-ui (Ubuntu) Status: New => Confirmed ** Changed in: signon-ui (Ubuntu) Assignee: (unassigned) => Alberto Mardegan (mardy) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1673984 Title: Can not add google account any more (Zesty) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1673984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1673697] [NEW] App switcher crashes unity8 with MeshLab
Public bug reported: Please install the meshlab-mardy snap. This Qt application works fine in unity7, and actually mostly works in unity8 too. However, as soon as it starts, for some reason it creates a secondary black window for a few seconds (title being something like "MeshLab_64bit"), which then gets closed shortly after the main window appears. This works fine in unity7. However, in unity8, this secondary window never closes. Also, the splashscreen window is never closed, and its spinner continues rotating. But the real problem comes when pressing "Alt+Tab": the task switcher appears for a second, then unity8 restarts. I'm using unity8-desktop-session (therefore classic Ubuntu) in VirtualBox. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Description changed: Please install the meshlab-mardy snap. This Qt application works fine in unity7, and actually mostly works in unity8 too. However, as soon as it starts, for some reason it creates a secondary black window for a few seconds (title being something like "MeshLab_64bit"), which then gets closed shortly after the main window appears. This works fine in unity7. - However, in unity8, this secondary window never closed. Also, the + However, in unity8, this secondary window never closes. Also, the splashscreen window never closed, and its spinner continues rotating. But the real problem comes when pressing "Alt+Tab": the task switcher appears for a second, then unity8 restarts. I'm using unity8-desktop-session (therefore classic Ubuntu) in VirtualBox. ** Description changed: Please install the meshlab-mardy snap. This Qt application works fine in unity7, and actually mostly works in unity8 too. However, as soon as it starts, for some reason it creates a secondary black window for a few seconds (title being something like "MeshLab_64bit"), which then gets closed shortly after the main window appears. This works fine in unity7. However, in unity8, this secondary window never closes. Also, the - splashscreen window never closed, and its spinner continues rotating. + splashscreen window is never closed, and its spinner continues rotating. But the real problem comes when pressing "Alt+Tab": the task switcher appears for a second, then unity8 restarts. I'm using unity8-desktop-session (therefore classic Ubuntu) in VirtualBox. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1673697 Title: App switcher crashes unity8 with MeshLab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1673697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1673423] [NEW] QML test failure on powerpc
Public bug reported: I'm filing this bug on QtDeclarative, though I'm not sure at all that the bug is there. I've got some QML tests that today started failing (two out of two builds): https://launchpadlibrarian.net/311109197/buildlog_ubuntu-zesty-powerpc .ubuntu-system-settings-online- accounts_0.7+17.04.20170316-0ubuntu1_BUILDING.txt.gz Note how the same tests passed one week ago: https://launchpadlibrarian.net/310116263/buildlog_ubuntu-zesty-powerpc .ubuntu-system-settings-online- accounts_0.7+17.04.20170308.2-0ubuntu1_BUILDING.txt.gz I'll temporarily disable tests in Online Accounts. ** Affects: qtdeclarative-opensource-src (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1673423 Title: QML test failure on powerpc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1673423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
