[Bug 2018504] Re: cups-browsed is using an excessive amount of CPU
Please file a new bug. If you run "ubuntu-bug cups-browsed" to start writing your report, it'll automatically include some relevant diagnostics. If there are any relevant log messages in the journal, that would be useful too. Marking a bug as duplicate is very easy to do. Untangling two problems that have been mixed into one bug report is a lot harder. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2018504 Title: cups-browsed is using an excessive amount of CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2018504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2018504] Re: cups-browsed is using an excessive amount of CPU
@Raffaele: I'm not saying that there isn't a problem: rather that the cause is probably different to the one from this closed bug, even if the symptom is the same. You'd be better off reporting a new bug, or looking through the open bug reports to see if any of those match what you're seeing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2018504 Title: cups-browsed is using an excessive amount of CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2018504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2018504] Re: cups-browsed is using an excessive amount of CPU
Note that the problem this bug was opened to address was fixed in an update to 23.04. If you are seeing a problem on 24.04, it is most likely a different issue (possibly bug 2049315). Comments on long closed bug reports are likely to be missed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2018504 Title: cups-browsed is using an excessive amount of CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2018504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968635] Re: Chromium window empty
*** This bug is a duplicate of bug 1966108 *** https://bugs.launchpad.net/bugs/1966108 ** This bug has been marked a duplicate of bug 1966108 Chromium snap on Jammy system with nvidia-510 does not start -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968635 Title: Chromium window empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1968635/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
> Is there any option to do this via portals - ie can evince use > org.freedesktop.portal.OpenURI to open the URI? Would then this > allow to avoid going via xdg-open? Evince is using g_app_info_launch_default_for_uri(), which can use the portal interface: https://gitlab.gnome.org/GNOME/evince/-/blob/main/shell/ev- window.c#L6775-6778 However, it only does this as a fallback if no desktop file supports the URI. This is intended to allow a confined app to handle some file types within the sandbox before falling back to portals for everything else. In the case of Evince running on the host system and seeing all the desktop files in /usr/share/applications and other locations, it likely won't ever call the portal API. It'd be possible to code in explicit portal API calls, but it isn't something that Evince packaged as a flatpak or snap would need. So it might end up as a distro patch we'd be on the hook to maintain forever. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965805] Re: Ubiquity failure - Error while installing packages Ubuntu Jammy
** Changed in: ubiquity (Ubuntu Jammy) Milestone: None => ubuntu-22.04-beta -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965805 Title: Ubiquity failure - Error while installing packages Ubuntu Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1965805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965805] Re: Ubiquity failure - Error while installing packages Ubuntu Jammy
I just tried installing a system using the 20220324.3 daily image (which includes the new snapd). The installation completed successfully, and the /usr/bin/snap panic I'd previously observed when run under "sudo chroot /target" was now gone. ** Changed in: ubiquity (Ubuntu Jammy) Status: Confirmed => Fix Released ** Changed in: ubiquity (Ubuntu Jammy) Milestone: ubuntu-22.04-beta => None -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965805 Title: Ubiquity failure - Error while installing packages Ubuntu Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1965805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965805] Re: Ubiquity failure - Error while installing packages Ubuntu Jammy
Looking further, it seems this is a problem that has already been fixed in snapd: https://github.com/snapcore/snapd/pull/11275 The change was included in snapd 2.55. The ENOENT check is not present in 2.54.4, as is being used in the installer environment: https://github.com/snapcore/snapd/blob/5d1db242a82a8e3b2460a0877c9890ec99cd9b60/osutil/user.go#L306-L317 I can see that an upload of snapd 2.55.2 was made to jammy 2 days ago, so I suspect that would likely correct the problem when the next image is spun. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965805 Title: Ubiquity failure - Error while installing packages Ubuntu Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1965805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965805] Re: Ubiquity failure - Error while installing packages Ubuntu Jammy
I tried to do a clean install in a VM with the current daily install media and managed to reproduce the problem. The Firefox preinst script was stuck in its loop calling "snap info firefox", so I opened a shell with "sudo chroot /proc/$pid/root" and ran the same command. That led to a panic that I've attached below. The panic occurs when it is trying to get the caller's home directory, picking the sudo user in preference: https://github.com/snapcore/snapd/blob/6541efe9d6daad221447a2220c6de544b1741f46/client/login.go#L97-L100 The called function checks the SUDO_USER environment variable: https://github.com/snapcore/snapd/blob/6541efe9d6daad221447a2220c6de544b1741f46/osutil/user.go#L309-L347 The /proc/$pid/environ file shows that the preinst script is being run with SUDO_USER=ubuntu, which is essentially the same environment I happened to create with "sudo chroot". The user lookup fails because there is no user by that name in the file system being set up for the install. ** Attachment added: "Output of "snap info firefox"" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1965805/+attachment/5572359/+files/snap.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965805 Title: Ubiquity failure - Error while installing packages Ubuntu Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1965805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928360] Re: Switch to Fcitx 5 for Chinese
> Is there such a snap you could point me to so I can test? The candidate channel of the gedit snap is built with core20 and the gnome-3-38-2004 platform snap. But as I said, I don't think that platform snap currently includes the fcitx5 input module. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928360 Title: Switch to Fcitx 5 for Chinese To manage notifications about this bug go to: https://bugs.launchpad.net/lubuntu-default-settings/+bug/1928360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928360] Re: Switch to Fcitx 5 for Chinese
I hadn't realised that they renamed the IM module with the version bump: that means snaps built against older platforms won't load the old (but working) Fcitx 4 module when run on a host system configured with Fcitx 5. We can certainly look at adding the new IM module to the platform snaps, but that will also switch to the new IPC protocol. From a quick look through the source it will probably be allowed by existing AppArmor rules in the "desktop" interface, but that will need testing. It's probably going to be easiest to see if we can get things working with a core20 based platform snap though, since we have fcitx5 packages there (albeit for a git prerelease version). For the core18 based platform snaps, we would need to backport the fcitx5 packages themselves. Alternatively, I wonder if we could get away with symlinking the old module name to the new one? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928360 Title: Switch to Fcitx 5 for Chinese To manage notifications about this bug go to: https://bugs.launchpad.net/lubuntu-default-settings/+bug/1928360/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838038] Re: [snap] Snapped apps do not work with .local mdns/avahi name resolution
Just repeating what I said on the forum, I believe this could be implemented through updates to the base snaps with no changes to snapd or any application snaps. The mdns4_minimal NSS plugin is an 18K binary (which compresses to about 6KB) that delegates its lookups to avahi-daemon using a single purpose lookups-only unix socket protocol (i.e. no D-Bus access). The AppArmor policy fragment grants access to this socket, so any snap plugging "network" already has permission to communicate. If the plugin cannot connect to Avahi, it should error out very quickly. Updating the base snaps to include the NSS plugin and reference it in their nsswitch.conf file would likely be all that is needed. It should work equally well for applications on classic distros and those on Ubuntu Core with the avahi snap installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838038 Title: [snap] Snapped apps do not work with .local mdns/avahi name resolution To manage notifications about this bug go to: https://bugs.launchpad.net/snap-core18/+bug/1838038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897224] Re: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display)
I've updated the description with the SRU bug template. I think this includes all the relevant info? ** Description changed: - I'm trying to run chromium installed via snap in Ubuntu 20.10 when - running Ubuntu Wayland session. Unfortunately, chromium wouldn't start: + [Impact] - > chromium + * Users who select the Wayland session on Ubuntu 20.10 cannot run snap +confined X11 applications, due to gnome-shell no longer listening on an +abstract socket for connections. + + * The fix, which has been accepted into upstream's gnome-3-38 branch +reverts the change removing the abstract socket, and fixes the bug that +prompted it's removal. + + [Test Case] + + * Start with a stock Ubuntu 20.10 desktop install. + + * At the GDM login screen, after selecting your user account use the gear +icon to select the "Ubuntu on Wayland" session, and log in. + + * Ensure Chromium is installed by running "sudo snap install chromium". + + * Try to run "chromium" from the terminal. Without the fix, it will fail +with the error "Unable to open X display". With the fix applied, it +will launch as normal. + + [Regression Potential] + + * The patch modifies the logic gnome-shell uses to launch Xwayland. So +there is a potential that the change could break X11 application +support on the Wayland session. + + * The default configuration for gnome-shell is to launch Xwayland on +session start, so it should be immediately obvious if there are +problems. + + * In addition to checking snapped X11 apps like Chromium, verify that a +few classic X11 apps still launch correctly (e.g. xterm, xeyes, etc). + + [Other Info] + + * Running "ss -xlp | grep Xwayland" should show that it is listening on +both "/tmp/.X11-unix/X0" (the regular unix domain socket) and +"@/tmp/.X11-unix/X0" (the abstract socket). + + --- + I'm trying to run chromium installed via snap in Ubuntu 20.10 when running Ubuntu Wayland session. Unfortunately, chromium wouldn't start: + + > chromium [49244:49244:0925/094607.732169:ERROR:browser_main_loop.cc(1417)] Unable to open X display. I am able to run Firefox just fine (assuming that Firefox still runs on xwayland) and also Intellij snap works fine. ProblemType: Bug DistroRelease: Ubuntu 20.10 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 Uname: Linux 5.8.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu47 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 25 09:45:16 2020 InstallationDate: Installed on 2016-09-05 (1480 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Snap: chromium 85.0.4183.121 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: [Impact] - * Users who select the Wayland session on Ubuntu 20.10 cannot run snap -confined X11 applications, due to gnome-shell no longer listening on an -abstract socket for connections. + * Users who select the Wayland session on Ubuntu 20.10 cannot run snap + confined X11 applications, due to gnome-shell no longer listening on an + abstract socket for connections. - * The fix, which has been accepted into upstream's gnome-3-38 branch -reverts the change removing the abstract socket, and fixes the bug that -prompted it's removal. + * The fix, which has been accepted into upstream's gnome-3-38 branch + reverts the change removing the abstract socket, and fixes the bug that + prompted it's removal: + +https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1508 [Test Case] - * Start with a stock Ubuntu 20.10 desktop install. + * Start with a stock Ubuntu 20.10 desktop install. - * At the GDM login screen, after selecting your user account use the gear -icon to select the "Ubuntu on Wayland" session, and log in. + * At the GDM login screen, after selecting your user account use the gear + icon to select the "Ubuntu on Wayland" session, and log in. - * Ensure Chromium is installed by running "sudo snap install chromium". + * Ensure Chromium is installed by running "sudo snap install chromium". - * Try to run "chromium" from the terminal. Without the fix, it will fail -with the error "Unable to open X display". With the fix applied, it -will launch as normal. + * Try to run "chromium" from the terminal. Without the fix, it will fail + with the error "Unable to open X display". With the fix applied, it + will launch as normal. [Regression Potential] - * The patch modifies the logic gnome-shell uses to launch Xwayland. So -there is a potential that the change could break X11 application -support on the Wayland session. + * The patch modifies the logic gnome-shell uses to launch Xwayland. So + there is a potential that the change could break X11
[Bug 1897224] Re: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display)
I had a go at fixing this in https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1508 -- taking the patches from that MR and applying them to the Groovy mutter source package gave me a Wayland session that supported X11 snaps again. It is probably worth waiting for a review from upstream before going further. I've done the testing they asked for with the "autostart- xwayland" feature enabled, so hopefully that will come soon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897224 Title: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1897224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897224] Re: [snap] chromium won't start on Xwayland in Ubuntu 20.10: Unable to open X display
I've filed https://gitlab.gnome.org/GNOME/mutter/-/issues/1454 upstream about this regression. ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1454 https://gitlab.gnome.org/GNOME/mutter/-/issues/1454 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897224 Title: [snap] chromium won't start on Xwayland in Ubuntu 20.10: Unable to open X display To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1897224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897224] Re: [snap] chromium won't start on Xwayland in Ubuntu 20.10: Unable to open X display
Looking at the reasoning behind that change, Mutter introduced lazy initialisation of Xwayland: binding the two sockets, and starting Xwayland when someone connected to the abstract namespace socket. Flatpak apps apparently can't speak to the abstract namespace socket, so would hang forever when started since the connection to the non-abstract /tmp/.X11-unix socket was never accepted. Rather than fixing the initialisation logic to start Xwayland on connect to either socket, they dropped the abstract namespace socket. I'll talk to the snapd folks about it, but this sounds like it should be dealt with on the Mutter side. ** Changed in: mutter (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897224 Title: [snap] chromium won't start on Xwayland in Ubuntu 20.10: Unable to open X display To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1897224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897224] Re: [snap] chromium won't start on Xwayland in Ubuntu 20.10: Unable to open X display
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1424 is definitely the culprit here. Snaps depend on access to the abstract namespace socket to function correctly. Inside the sandboxes, snaps see a private /tmp that is under their complete control. So there is no /tmp/.X11-unix directory there. They can see the abstract namespace socket though, which the client libraries will use automatically. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897224 Title: [snap] chromium won't start on Xwayland in Ubuntu 20.10: Unable to open X display To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1897224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886854] Re: Race in load-module snap policy check in classic confinement
This is the in-progress fix I've been working on. It does not quite work right though: switching to an async hook for these commands is resulting in the daemon killing the client on a protocol error. This might be a problem with the hooks patch set itself. I need to investigate a bit further. ** Patch added: "allow-classic.diff" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1886854/+attachment/5413365/+files/allow-classic.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886854 Title: Race in load-module snap policy check in classic confinement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1886854/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886854] Re: Race in load-module snap policy check in classic confinement
Sorry for taking so long to get back to you. I now understand the non- deterministic behaviour you're seeing. I'm working on a fix for the server side to allow classic snaps to access these commands. It will require a small change to your Pulse Audio client library to fix the non-determinism though. I'll share more information soon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886854 Title: Race in load-module snap policy check in classic confinement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1886854/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889092] Re: getent does not support extrausers on uc18
getent isn't the problem here: it is just returning whatever data the nameservice switch provides. The underlying cause is that libnss-extrausers ignores entries in the extrausers database that have a uid or gid less than 500: https://git.launchpad.net/ubuntu/+source/libnss- extrausers/tree/s_config.h The docker user and group as defined fall into that category. It's not at all clear that it's a good idea to have low ID users and groups in extrausers anyway: it seems like it's just asking for conflicts with future updates of the base snap. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889092 Title: getent does not support extrausers on uc18 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1889092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886854] Re: Race in load-module snap policy check in classic confinement
I think I need to dig into this further. The fact you're seeing a few successful module loads with different module indexes would indicate it is the same Pulse Audio instance. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886854 Title: Race in load-module snap policy check in classic confinement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1886854/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886854] Re: Race in load-module snap policy check in classic confinement
I think there's two issues at play here. The hooks we added for module loading/unloading as part of USN-4355-1 simply check if the client has an AppArmor label that looks like it belongs to a snap and denies access if found. This will also deny access to classic snaps, which is probably a mistake. The race condition you've encountered is probably a case of "policy module not in effect" vs. "policy module in effect" rather than a race in the behaviour of the policy module itself. This probably indicates that Pulse is servicing client requests before it has completely started. For the first issue, we can make the hook request info about the snap and allow access to classic snaps. For the second, I think we just need to load module-snap-policy earlier during start up. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886854 Title: Race in load-module snap policy check in classic confinement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1886854/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858636] Re: snapd generates incomplete fontconfig caches, result in emoji rendering issue in chromium
I've just been reading through the code used to build the bin/fc- cache-v6 and bin/fc-cache-v7 binaries in the core snap: https://github.com/snapcore/fc-cache-static-builder I think I understand what the problem is: while it is rebuilding copies of xenial's and bionic's fontconfig tools that statically link to libfontconfig, it's using the xenial version of libfreetype2 for both. I suspect that this old freetype version does not understand all the features of the font (e.g. the scalable colour emoji), so the generated cache also misses them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858636 Title: snapd generates incomplete fontconfig caches, result in emoji rendering issue in chromium To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1858636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881232] Re: AppArmor blocks ibus input when IBUS_USE_PORTAL=1
This looks like a good candidate for the "desktop" interface. Security is significantly better than the traditional IBus communication method, since access to IBusContexts are restricted to their owner: https://github.com/ibus/ibus/blob/master/portal/portal.c#L354-L370 ... and IBusContext signals are unicast to the owner rather than broadcast: https://github.com/ibus/ibus/blob/master/portal/portal.c#L408-L414 Further more, IBus's non-portal communication method goes over a separate socket connection. So any session bus rules we add should not inadvertently provide access to the insecure API. I would also consider merging the last two proposed rules into one like so: dbus (send, receive) bus=session path=/org/freedesktop/IBus/InputContext_[0-9]* interface=org.freedesktop.IBus.InputContext peer=(label=unconfined), It doesn't look like there is any methods with different level of privilege on the interface, and this avoids incompatibilities if IBus evolves in future. We probably also want to allow communication with peer=(name=org.freedesktop.portal.IBus) for the base CreateInputContext API, since the service file does not contain an AssumedAppArmorLabel field that would allow service activation to succeed otherwise. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881232 Title: AppArmor blocks ibus input when IBUS_USE_PORTAL=1 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876237] [NEW] QDesktopServices::openUrl() fails when called on local files from within a snap
Public bug reported: This is something we might want to fix to help people who build snaps based on Focal's Qt. The QGenericUnixServices implementation of openUrl() passes an O_PATH file descriptor to xdg-desktop-portal when it detects it is running under snap confinement. This is rejected because xdg-desktop-portal expects an O_RDONLY file descriptor, leading to the operation failing. More details are available in the upstream bug report I filed: https://bugreports.qt.io/browse/QTBUG-83939 This originated from a report on the Snapcraft forum here: https://forum.snapcraft.io/t/xdg-open-or-gvfs-open-qdesktopservices- openurl-file-somelocation-file-txt-wont-open-the-file/16824?u=jamesh ** Affects: qtbase-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/1876237 Title: QDesktopServices::openUrl() fails when called on local files from within a snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1876237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867080] Re: No mouse cursor drawn in Wayland session
** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867080/+attachment/5335924/+files/lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867080 Title: [radeon] No mouse cursor drawn in Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1867080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867080] [NEW] No mouse cursor drawn in Wayland session
Public bug reported: When I upgraded my desktop yesterday, I could no longer see the mouse cursor on the screen. It still responded to mouse clicks (e.g. context menu on right click, pushing the mouse to the top left and left clicking went to spread mode, etc). This only seems to affect the Wayland session: when I switched back to X11 the mouse cursor was visible again. I also noticed that the mouse cursor is absent on the GDM login screen, which I understand is also a Wayland based gnome-shell session. I tried reproducing the bug on my laptop, but the mouse cursor shows just fine there. The main differences between the systems are the GPU (radeon vs. intel) and number of monitors (dual screen vs. single). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 12 10:28:55 2020 DisplayManager: gdm3 InstallationDate: Installed on 2013-10-29 (2325 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-02-02 (38 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867080 Title: No mouse cursor drawn in Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865371] Re: Mouse Cursor or Touchpad indicator/pointer not working
I noticed something like this on my desktop system after upgrading. It only seems to affect Wayland sessions (i.e. GDM login screen and Ubuntu on Wayland). The mouse still works (i.e. desktop responds to clicks), but no cursor is drawn. Everything seems fine on my laptop though. The main differences between the two systems are: 1. Radeon graphics on the desktop vs. Intel on the laptop 2. dual monitors on the desktop 3. The desktop is using a "Thinkpad Compact USB Keyboard" as the mouse (i.e. single USB device exposing two HID interfaces). Given that the reporter here is using an AMD APU, I wonder if this is an interaction between gnome-shell and the radeon driver? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865371 Title: Mouse Cursor or Touchpad indicator/pointer not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861791] Re: Server incompatible with Focal clients
I detailed the configuration file workaround here: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1856428/comments/2 I wonder if the underlying cause of the problem is that Bionic's Mumble is compiled against Qt 4, which predates the newer TLS versions. I would have thought it'd get new versions automatically through new OpenSSL releases, but perhaps there is some incompatibility in there. If that's the case, I wonder if Bionic's Mumble client can successfully connect to Focal's Mumble server? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861791 Title: Server incompatible with Focal clients To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mumble/+bug/1861791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856428] Re: Disable TLS below 1.2 by default
For anyone who finds this bug, and wonders about the "Users can override this behaviour with a config file" part, here's what I did to get an OpenSSL-using application to talk to an old server that only supported TLSv1 (in my case, an old Mumble server): 1. create an "openssl.cnf" file somewhere with the following contents: openssl_conf = openssl_init [openssl_init] ssl_conf = ssl_sect [ssl_sect] system_default = system_default_sect [system_default_sect] CipherString = DEFAULT@SECLEVEL=1 2. set the OPENSSL_CONF environment variable to this file's path when running the application. I wouldn't recommend making the change to the global /etc/ssl/openssl.cnf, or setting $OPENSSL_CONF for situations where it isn't needed, since this does reduce the default security. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856428 Title: Disable TLS below 1.2 by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1856428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861791] Re: Server incompatible with Focal clients
Sure. But if this is controllable from a configuration file, then it might be possible to come up with a temporary work around until the server you want to connect to is upgraded. With any luck, the configuration can be changed in such a way that only Mumble is affected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861791 Title: Server incompatible with Focal clients To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mumble/+bug/1861791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861791] Re: Server incompatible with Focal clients
This is likely caused by bug 1856428, which indicates that support for the older TLS versions can be enabled in a configuration file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861791 Title: Server incompatible with Focal clients To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mumble/+bug/1861791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861791] Re: Server incompatible with Focal clients
I encountered this today too. This seems to be an OpenSSL problem, given that "openssl s_client" refuses to connect to the server, where it succeeds with older releases. Presumably the server only supports ciphers or TLS versions the new OpenSSL rejects. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861791 Title: Server incompatible with Focal clients To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mumble/+bug/1861791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862158] Re: gnome-software tries to install snap updates in the background, causing unprompted polkit authentication for authorisation to install packages
Is there some way gnome-software can inform the plugin that it is performing a non-interactive operation? If so, then the plugin could use snapd_client_set_allow_interaction() to suppress any potential pokit dialogs from the operation. It wouldn't allow the operation to succeed, but it also wouldn't leave the user with an authentication dialog open when they unlock their screen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862158 Title: gnome-software tries to install snap updates in the background, causing unprompted polkit authentication for authorisation to install packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1862158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856054] Re: pulseaudio now depends on libsnapd-glib1 which recommends snapd
If you are worried about what the Pulse Audio change is actually doing, here's a description: 1. there is a new "snap-policy" PA module that is loaded by default. 2. when a client attempts to use the microphone and has a "snap.*" AppArmor label, it contacts snapd to check whether that app has permission to record audio (as opposed to simply playing sounds). 3. if the client is not a snap application or it is a snap application with record access, then PA will create record stream. So there should be no problem with removing snapd again. In fact the policy module should effectively be inert if no snaps are ever run, not even trying to talk to snapd. The "Recommends: snapd" is definitely too strong for the way Pulse Audio is using libsnapd-glib. Once snapd-glib's dependency is relaxed, we should be able to push this update again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856054 Title: pulseaudio now depends on libsnapd-glib1 which recommends snapd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781428] Re: please enable snap mediation support
The two packages are in the upload queue now: https://launchpad.net/ubuntu/xenial/+queue?queue_state=1_text=pulseaudio https://launchpad.net/ubuntu/bionic/+queue?queue_state=1_text=pulseaudio One additional acceptance test would be to verify that the policy module continues to work across snapd restarts. So at the end of the test script, add something like: The policy module continues to function over snapd restarts: $ sudo systemctl restart snapd.service $ test-snapd-audio-record.record /tmp/out.wav && echo yes # should pass ... ^Cyes This was a problem with old versions of snapd-glib (before 1.44, I think), but shouldn't be a problem now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781428 Title: please enable snap mediation support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1781428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781428] Re: please enable snap mediation support
Attached is a debdiff for the Xenial version of the backport. In addition to the snap policy module patches, this includes a backport of the libjson-c dependency removal changes from Pulse Audio 10.0 (which applied cleanly without modification). This is required because libjson-c and libjson-glib declare a few symbols with the same name, causing problems for the policy module. Based on discussion in https://bugs.freedesktop.org/show_bug.cgi?id=95135, the libjson-c dependency was causing problems for other applications too. I was able to complete @jdstrand's test plan on a clean 16.04 install with these updates. pulseaudio (1:8.0-0ubuntu3.11) xenial; urgency=medium * Backport the snap policy module to make access to audio recording conditional on plugging the "pulseaudio" or "audio-record" interfaces (LP: #1781428): - 0450-modules-add-snappy-policy-module.patch: rewrite to query snapd for the client's plugged interfaces. - 0451-enable-snap-policy-module.patch: enable the module in the default configuration. - Build depend on libsnapd-glib-dev. * Backport libjson-c dependency removal from Pulse Audio 10. This is required by the snap policy module due to a symbol name clash with libjson-glib. - 0805-remove-libjson-c-dependency.patch: new file. -- James Henstridge Tue, 05 Nov 2019 17:16:22 +0800 ** Bug watch added: freedesktop.org Bugzilla #95135 https://bugs.freedesktop.org/show_bug.cgi?id=95135 ** Patch added: "pulseaudio_8.0-0ubuntu3.10_8.0-0ubuntu3.11.diff" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1781428/+attachment/5303806/+files/pulseaudio_8.0-0ubuntu3.10_8.0-0ubuntu3.11.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781428 Title: please enable snap mediation support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1781428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781428] Re: please enable snap mediation support
Attached is a debdiff for the bionic backport. I've run through @jdstrand's test plan on a clean Ubuntu 18.04 install, and everything appears to be behaving as expected. pulseaudio (1:11.1-1ubuntu7.5) bionic; urgency=medium * Update snap policy to make access to audio recording conditional on plugging the "pulseaudio" or "audio-record" interfaces (LP: #1781428): - 0700-modules-add-snappy-policy-module.patch: rewrite to query snapd for the client's plugged interfaces. - 0701-enable-snap-policy-module.patch: enable the module in the default configuration. - Build depend on libsnapd-glib-dev. * Remove module-trust-store patch set: - 0409-Trust-store-patch.patch: trimmed down to pulsecore changes. - 0410-Add-thread-to-activate-trust-store-interface.patch: removed. - 0417-increase-timeout-check-apparmor.patch: removed. -- James Henstridge Wed, 05 Nov 2019 17:16:25 +0800 ** Patch added: "pulseaudio_11.1-1ubuntu7.4_11.1-1ubuntu7.5.diff" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1781428/+attachment/5303689/+files/pulseaudio_11.1-1ubuntu7.4_11.1-1ubuntu7.5.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781428 Title: please enable snap mediation support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1781428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781428] Re: please enable snap mediation support
The xenial backport is non-functional due to a symbol collision between libjson-c.so (required by libpulse) and libjson-glib.so (required by snapd-glib). This doesn't affect the Bionic backport though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781428 Title: please enable snap mediation support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1781428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843764] Re: sane-backends ftbfs in eoan (armhf)
Does it actually make sense to have symbols files for plugins? As long as they work with the libsane.so.1 that they're shipped with, does it matter what symbols they export? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843764 Title: sane-backends ftbfs in eoan (armhf) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1843764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640514] Re: /snap/bin is not added to the PATH when using zsh
I've put together a PR to set XDG_DATA_DIRS via environment.d, as was done for PATH: https://github.com/snapcore/snapd/pull/6813 When this is merged and released, it should remove the need for any special user configuration. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640514 Title: /snap/bin is not added to the PATH when using zsh To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1640514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811707] Re: gnome-calculator snap does not respect shell theme
If you are running an X session, then you are running into a different issue. The set of circumstances that lead to the problem on Wayland (different gsettings defaults inside and outside of confinement) do not apply to X11 where the theme is exposed by the host over XSETTINGS (so sees the default of the host system). I'd suggest filing a new bug with more details if you're on an X11 session. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811707 Title: gnome-calculator snap does not respect shell theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1811707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816436] Re: gnome-terminal window shrinks when changing tabs
At didrocks' request, I've also filed this here: https://github.com/ubuntu/yaru/issues/1196 ** Bug watch added: github.com/ubuntu/yaru/issues #1196 https://github.com/ubuntu/yaru/issues/1196 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816436 Title: gnome-terminal window shrinks when changing tabs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1816436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816436] [NEW] gnome-terminal window shrinks when changing tabs
Public bug reported: I am using gnome-terminal 3.31.90-1ubuntu1 on a Disco desktop. If I create a gnome-terminal window and add a second tab, the window will shrink by one line each time I switch tabs. This seems to be theme related, since it happens with Yaru but not with Adwaita. Some aspects of my configuration that seem to be relevant: 1. Using yaru-theme-gtk version 19.04 2. Under the org.gnome.desktop.interface gsettings schema, I have scaling-factor set to 1 and text-scaling-factor set to 1.5 This may lead to some widgets size being dictated by the text height where they might be governed by min-height otherwise. I suspect that the height notebook tabs are changing when changing from selected to unselected state, and gnome-terminal then tries to resize the window to align to the terminal character grid. ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Also affects: yaru-theme (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/1816436 Title: gnome-terminal window shrinks when changing tabs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1816436/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810757] Re: /usr/libexec/xdg-document-portal:6:g_assertion_message:g_assertion_message_expr:xdp_inode_destroy:xdp_inode_unref_internal:xdp_inode_unref_internal
This bug occurs when using the "SaveFile" desktop portal API and the user chooses a new file name rather than overwriting an existing file. It can easily be reproduced with the following steps: 1. install the test-snapd-portal-client snap: snap install --edge test-snapd-portal-client 2. run the save-file test: test-snapd-portal-client save-file "foo" 3. in the file chooser, select a file name that does not exist. The command will fail with a ConnectionAbortedError exception, and xdg- document-portal will crash with the following in the log: Jan 07 17:38:06 scruffy xdg-document-portal[30685]: error: Invalid id snap.test-snapd-portal-client: Names must contain at least 2 periods Jan 07 17:38:06 scruffy xdg-document-portal[30685]: error: ** Jan 07 17:38:06 scruffy xdg-document-portal[30685]: xdg-desktop-portal:ERROR:document-portal/document-portal-fuse.c:206:xdp_inode_destroy: assertion failed: (inode->dir_fd == -1) The problem does not occur with xdg-desktop-portal 1.0.3, so it is likely that one of the patches alexl mentioned at https://bugs.launchpad.net/ubuntu/+source/xdg-desktop- portal/+bug/1691649/comments/10 would fix it. With that said, backporting 1.0.3 might be the better option if we want working portals. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810757 Title: /usr/libexec/xdg-document- portal:6:g_assertion_message:g_assertion_message_expr:xdp_inode_destroy:xdp_inode_unref_internal:xdp_inode_unref_internal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1810757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810755] [NEW] xdg-document-portal 1.0.2-1ubuntu1 crashes when trying to save to a non-existant file
*** This bug is a duplicate of bug 1810757 *** https://bugs.launchpad.net/bugs/1810757 Public bug reported: When using the desktop portal API to save a file, the xdg-document- portal service crashes if we try to save to a new file name. Steps to reproduce: 1. On an Ubuntu 18.10 system, install the test-snapd-portal-client snap: snap install --edge test-snapd-portal-client 2. run the save-file test: test-snapd-portal-client save-file "foo" 3. in the file chooser, select a file name that does not exist. Actual results: The command exits with the following error (eliding the traceback): ConnectionAbortedError: [Errno 103] Software caused connection abort: '/run/user/1000/doc/eca716d3/xyz.txt' Furthermore, "systemctl --user status xdg-document-portal.service" reports the following error: Jan 07 17:38:06 scruffy xdg-document-portal[30685]: error: Invalid id snap.test-snapd-portal-client: Names must contain at least 2 periods Jan 07 17:38:06 scruffy xdg-document-portal[30685]: error: ** Jan 07 17:38:06 scruffy xdg-document-portal[30685]: xdg-desktop-portal:ERROR:document-portal/document-portal-fuse.c:206:xdp_inode_destroy: assertion failed: (inode->dir_fd == -1) Expected results: The file should be created with the contents "foo". The problem is not present with xdg-desktop-portal 1.0.3. I suspect the fix is one of these extra patches alexl suggested we take: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop- portal/+bug/1691649/comments/10 ** Affects: xdg-desktop-portal (Ubuntu) Importance: Undecided Status: New ** This bug has been marked a duplicate of bug 1810757 /usr/libexec/xdg-document-portal:6:g_assertion_message:g_assertion_message_expr:xdp_inode_destroy:xdp_inode_unref_internal:xdp_inode_unref_internal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810755 Title: xdg-document-portal 1.0.2-1ubuntu1 crashes when trying to save to a non-existant file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1810755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803534] Re: Backport uuid based cache file naming scheme
** Description changed: Fontconfig 2.13.0 changed the cache file naming scheme to be based on the contents of ".uuid" file in the directory rather than a hash of the directory name. On a pure debs system this doesn't really matter since everything is using the same libfontconfig.so. When snaps are involved, it can lead to some apps not seeing the cache files produced by a different fontconfig version. In particular, while libfontconfig 2.13 can reuse 2.12's cache files for read only directories, the reverse is not true. This will be a problem for apps built on top of the "core18" base snap when run on later Ubuntu releases (cosmic, disco, etc). By providing a backport of the UUID cache file feature to bionic for use by snap applications, we'd avoid this. Having it in bionic-updates would be ideal so that snapcraft picks it up automatically. + + [Impact] + + * This update changes how fontconfig cache files are named, instead of + using md5($dir), it instead uses the contents of a $dir/.uuid file. No + changes are made to the format of the cache file contents. + + * This change is primarily intended for use by snap applications built + with core18: as the updated libfontconfig will fall back to the md5 + cache file names for read-only directories without a .uuid file, they + will be able to reuse cache files from any host system running + fontconfig >= 2.11.95 + + [Test Case] + + * After installing the update, cache files should be generated in + /var/cache/fontconfig/ with names like "07b67f7a-16ea-4440-9b6c- + 21fc9153568c-le64.cache-7" (note the extra dashes not present in the MD5 + based cache file names). + + [Regression Potential] + + * Applications using a non-default libfontconfig could end up not + finding the new cache files and regenerating them in + ~/.cache/fontconfig. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803534 Title: Backport uuid based cache file naming scheme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1803534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
Looking at the gnome-shell JS code referenced by the stack trace, it appears it is indeed disabling extensions when locking the screen. The screenShield.js code handles the lock screen, and pushes and pops a "session mode" of "lock-screen". In sessioMode.js, the "lock-screen" mode is defined with allowExtensions=false. Finally, extensionSystem.js watches session mode changes and calls the various extension enable/disable callbacks as needed. So somehow ubuntu-dock has a stale window in Transparency._trackedWindows that triggers an exception while trying to disable the dock when locking the screen. It fails to fully disable the dock, so it displays over the top of the lock screen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769383 Title: Ubuntu dock/launcher is shown on the lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
The above stack trace seems to be tied to this other message:
Nov 16 11:41:38 scruffy gnome-shell[5626]: Object Meta.WindowActor
(0x560d5092bb00), has been already deallocated — impossible to access
it. This might be caused by the object having been destroyed from C code
using something such as destroy(), dispose(), or remove() vfuncs.
The error seems to be on the disconnect() call in
Transparency.disable():
for (let key of this._trackedWindows.keys())
this._trackedWindows.get(key).forEach(id => {
key.disconnect(id);
});
this._trackedWindows.clear();
Presumably the remainder of the clean-up performed by this function and
its callers is not performed, leaving the shell in an inconsistent
state.
I'm still not sure why gnome-shell is trying to disable the extension.
Does it disable extensions when locking the screen?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769383
Title:
Ubuntu dock/launcher is shown on the lock screen
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
I noticed this behaviour on my Ubuntu 18.10 system. It is running the Wayland session, and I only have the ubuntu-d...@ubuntu.com and ubuntu- appindicat...@ubuntu.com extensions installed (i.e. no upstream dash-to- dock). I looked in the journal and found the attached GJS stack trace, which seems to be triggered by the disable() call. I haven't been manually enabling/disabling extensions, so don't know why the code path would have been triggered. It might mean some crud was left behind though. ** Attachment added: "stacktrace.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1769383/+attachment/5213307/+files/stacktrace.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769383 Title: Ubuntu dock/launcher is shown on the lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803534] Re: Backport uuid based cache file naming scheme
A backport of the UUID cache file directory feature from fontconfig 2.13. ** Patch added: "fontconfig_2.12.6-0ubuntu2_2.12.6-0ubuntu3.diff" https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1803534/+attachment/5213086/+files/fontconfig_2.12.6-0ubuntu2_2.12.6-0ubuntu3.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803534 Title: Backport uuid based cache file naming scheme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1803534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803534] [NEW] Backport uuid based cache file naming scheme
Public bug reported: Fontconfig 2.13.0 changed the cache file naming scheme to be based on the contents of ".uuid" file in the directory rather than a hash of the directory name. On a pure debs system this doesn't really matter since everything is using the same libfontconfig.so. When snaps are involved, it can lead to some apps not seeing the cache files produced by a different fontconfig version. In particular, while libfontconfig 2.13 can reuse 2.12's cache files for read only directories, the reverse is not true. This will be a problem for apps built on top of the "core18" base snap when run on later Ubuntu releases (cosmic, disco, etc). By providing a backport of the UUID cache file feature to bionic for use by snap applications, we'd avoid this. Having it in bionic-updates would be ideal so that snapcraft picks it up automatically. ** Affects: fontconfig (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/1803534 Title: Backport uuid based cache file naming scheme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1803534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691649] Re: xdg-desktop-portal crashed with SIGSEGV
The patch was accepted upstream as is, so we can backport it: https://github.com/flatpak/xdg-desktop- portal/commit/1737e30f5115fea144ab5e3f5f455e40d43dc974 While chatting on IRC, Alex suggested the following set of crash fixes for the xdg-document-portal from 1.0.3 that we may want to consider including: https://github.com/flatpak/xdg-desktop-portal/commit/7c9f69a20b02b25846f12dd74dc6da94b3faaa05 https://github.com/flatpak/xdg-desktop-portal/commit/b28e903ca3f6d3f8e2dec7af700b4734e418f8c8 https://github.com/flatpak/xdg-desktop-portal/commit/47b2b594075d34f7658cd7c70f3f2518c5c3921e I'm not sure whether it is worth trying to include them or wait to SRU a later xdg-document-portal post release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691649 Title: xdg-desktop-portal crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1691649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691649] Re: xdg-desktop-portal crashed with SIGSEGV
I've submitted a patch upstream here: https://github.com/flatpak/xdg-desktop-portal/pull/236 I'll give them a chance to respond and then look at putting together an update to our package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691649 Title: xdg-desktop-portal crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1691649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691649] Re: xdg-desktop-portal crashed with SIGSEGV
So judging by the logs in some of the related error reports, we get the
following log messages:
xdg-desktop-por[3113]: Failed to create file chooser proxy: Error calling
StartServiceByName for org.freedesktop.impl.portal.desktop.gtk: Timeout was
reached
xdg-desktop-por[3113]: g_dbus_interface_skeleton_set_flags: assertion
'G_IS_DBUS_INTERFACE_SKELETON (interface_)' failed
xdg-desktop-por[3113]: invalid (NULL) pointer instance
xdg-desktop-por[3113]: g_signal_connect_data: assertion
'G_TYPE_CHECK_INSTANCE (instance)' failed
xdg-desktop-por[3113]: g_dbus_interface_skeleton_export: assertion
'G_IS_DBUS_INTERFACE_SKELETON (interface_)' failed
This centres around the following code, which is the first portal whose
export depends on the presence of a UI implementation:
https://github.com/flatpak/xdg-desktop-portal/blob/1.0.2/src/xdg-
desktop-portal.c#L382-L385
implementation = find_portal_implementation
("org.freedesktop.impl.portal.FileChooser");
if (implementation != NULL)
export_portal_implementation (connection,
file_chooser_create (connection, implementation->dbus_name));
The first line looks up a backend implementation of the FileChooser
portal based on the implementations registered in /usr/share/xdg-
desktop-portal/portals, and picks xdg-desktop-portal-gtk.
The file_chooser_create method then tries to activate the selected D-Bus
name:
https://github.com/flatpak/xdg-desktop-portal/blob/1.0.2/src/file-
chooser.c#L578-L589
This corresponds to the first log message, and indicates that starting
xdg-desktop-portal-gtk timed out. It returns NULL, and
export_portal_implementation() contains no checks for NULL as a second
argument leading to the other messages. It ends with a
g_return_val_if_fail() check causing g_dbus_interface_skeleton_export()
to return FALSE without setting an error. We then get a segfault trying
to dereference a NULL GError pointer.
So there's two issues to address:
1. xdg-desktop-portal-gtk startup is timing out in some instances.
2. xdg-desktop-portal is not handling this timeout error correctly.
I'll look at addressing (2) since it is the immediate cause of the crash
reports, but portals are of limited use if they can't rely on any of the
GUI helpers for things like file choosers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691649
Title:
xdg-desktop-portal crashed with SIGSEGV
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1691649/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793298] [NEW] snapd-glib changes needed for pulseaudio snap policy module xenial backport
Public bug reported: The xenial backport of the fix for 1781428 malfunctioned due to the use of snapd-glib behaviour introduced after the version included in xenial: namely auto-connection (and reconnection) to the snapd socket that was introduced in snapd-glib 1.24. With the policy module loaded, Pulse Audio will contact snapd to check the interfaces plugged by a client in order to decide whether to provide access to the microphone. As the Pulse Audio daemon is long lived, it is not uncommon for the socket connection to be disconnected (either due to a timeout, or because snapd is upgraded while the user is logged in). So simply adding a snapd_client_connect() call at module initialisation time is not sufficient. The specific snapd-glib calls that could be affected are: * snapd_client_list_one_async * snapd_client_get_interfaces_async ** Affects: snapd-glib (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/1793298 Title: snapd-glib changes needed for pulseaudio snap policy module xenial backport To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1793298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790432] Re: skilion base repo appears abandonded; recommend rebase to abraunegg fork
This appears to be referring to the "onedrive" package in current versions of Ubuntu, rather than the discontinued Ubuntu Phone "storage- provider-onedrive" package. ** Project changed: storage-provider-onedrive => onedrive (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790432 Title: skilion base repo appears abandonded; recommend rebase to abraunegg fork To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onedrive/+bug/1790432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787324] Re: Snap policy module denies recording access to classic snaps
Here is a debdiff based on the attached branch. ** Patch added: "pulseaudio_12.2-0ubuntu2_12.2-0ubuntu3.diff" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1787324/+attachment/5181694/+files/pulseaudio_12.2-0ubuntu2_12.2-0ubuntu3.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787324 Title: Snap policy module denies recording access to classic snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1787324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787324] Re: Snap policy module denies recording access to classic snaps
** Merge proposal linked: https://code.launchpad.net/~ubuntu-audio-dev/pulseaudio/+git/pulseaudio/+merge/353214 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787324 Title: Snap policy module denies recording access to classic snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1787324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787324] [NEW] Snap policy module denies recording access to classic snaps
Public bug reported: With the recent updates to the snap policy module, recording access is denied to clients with a snap AppArmor label when that snap doesn't have a connected plug for "pulseaudio" or "audio-record". This is not appropriate for classic confinement snaps, which will have an AppArmor label but should still have access to recording even when there is no plug, as described by @jdstrand: https://forum.snapcraft.io/t/pulseaudio-recording/6361/14?u=jamesh This is broken with the 1:12.2-0ubuntu2 release, as can be seen with e.g.: $ aa-exec -p snap.skype.skype /usr/bin/parecord foo.wav Stream error: Access denied [note that the Skype app itself still functions because it bypasses PulseAudio all together] The above command should result in audio being recorded from the microphone. ** Affects: pulseaudio (Ubuntu) Importance: High Assignee: James Henstridge (jamesh) Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787324 Title: Snap policy module denies recording access to classic snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1787324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781428] Re: pulseaudio built with --enable-snappy but 'Enable Snappy support: no'
Attached is a debdiff for a 1:12.2-0ubuntu2 release of pulseaudio with an updated snap policy module and the default configuration modified to enable it. I also took the opportunity to remove the Ubuntu Phone era trust-store module, which hasn't been built since February. ** Patch added: "pulseaudio_12.2-0ubuntu1_12.2-0ubuntu2.diff" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1781428/+attachment/5173727/+files/pulseaudio_12.2-0ubuntu1_12.2-0ubuntu2.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781428 Title: pulseaudio built with --enable-snappy but 'Enable Snappy support: no' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1781428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774560] Re: xdg-desktop-portal-gtk malfunctions on Wayland: wl_display@1.error(zxdg_imported_v1@36, 0, "set_parent_of was called with an invalid child")
bionic-proposed has a 3.28.2 package, so this should be resolved for that release shortly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774560 Title: xdg-desktop-portal-gtk malfunctions on Wayland: wl_display@1.error(zxdg_imported_v1@36, 0, "set_parent_of was called with an invalid child") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1774560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774560] [NEW] xdg-desktop-portal-gtk malfunctions on Wayland: wl_display@1.error(zxdg_imported_v1@36, 0, "set_parent_of was called with an invalid child")
Public bug reported: When running on a Wayland session, if xdg-desktop-portal-gtk is asked to display a window on behalf of a Wayland app, it gets disconnected from gnome-shell with one of these messages: Gdk-Message: 09:49:31.837: Lost connection to Wayland compositor. Gdk-Message: 09:50:28.438: Error 71 (Protocol error) dispatching to Wayland display. Running it with WAYLAND_DEBUG=1, the underlying error message that GDK seems to eat is: [3471970.531] wl_display@1.error(zxdg_imported_v1@36, 0, "set_parent_of was called with an invalid child") That is, when it tries to associate the dialog box with the confined application's window. It seems the underlying bug is in in Mutter: https://gitlab.gnome.org/GNOME/mutter/issues/138 According to duflu, the patch referenced in that bug report has been merged for 3.28.2 and 3.29.2. It seems like a candidate to backport to bionic if we want portals to work on the (non-default) Wayland session. ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Affects: xdg-desktop-portal-gtk (Ubuntu) Importance: Undecided Status: New ** Also affects: mutter (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/1774560 Title: xdg-desktop-portal-gtk malfunctions on Wayland: wl_display@1.error(zxdg_imported_v1@36, 0, "set_parent_of was called with an invalid child") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1774560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1661590] Re: GNOME Software only supports running one application from a snap
@simosx: I gave this another test on a clean xenial VM with the same gnome-software version as you. Each time it launched the main "libreoffice" command (showing a window asking to open recent files or create a new document in one of the libreoffice applications). gnome-software continues running when you close the window, so is it possible you were still running the old version when you saw the failure? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1661590 Title: GNOME Software only supports running one application from a snap To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1661590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1672716] Re: Inverted colors on screenshots
** Bug watch added: GNOME Bug Tracker #793473 https://bugzilla.gnome.org/show_bug.cgi?id=793473 ** Also affects: gnome-screenshot via https://bugzilla.gnome.org/show_bug.cgi?id=793473 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672716 Title: Inverted colors on screenshots To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screenshot/+bug/1672716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690280] Re: Classic confined snaps don't install
** Description changed: [Impact] Apps that use classic confinement show up in search results but don't install. [Test Case] 1. Open GNOME Software 2. Search for a classic snap, e.g. "atom" 3. Install snap Expected result: Either: a) Snap is installed b) Snap is not installed and error given c) Snap is installed but user needs to provide some sort of confirmation since it is not confined. Observed result: Snap is not installed, no error given. + + [Regression Potential] + Patch changes the code path used to request installation of all snap packages. Ensure that strict confined snaps continue to be installed with correct confinement. + + For example, try installing "ohmygiraffe" via gnome-software, then run + "snap info ohmygiraffe" from a terminal. The "installed:" line should + not include the word "classic". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690280 Title: Classic confined snaps don't install To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1690280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690280] Re: Classic confined snaps don't install
Here's a debdiff for the Xenial package update based on Robert's work. I don't have upload rights to upload it myself. ** Patch added: "gnome-software_3.20.5-0ubuntu0.16.04.7_3.20.5-0ubuntu0.16.04.8.diff" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1690280/+attachment/5032747/+files/gnome-software_3.20.5-0ubuntu0.16.04.7_3.20.5-0ubuntu0.16.04.8.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690280 Title: Classic confined snaps don't install To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1690280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721735] Re: UbuntuOne auth dialog is displayed when polkit auth dialog is dismissed
I've got an (as yet unmerged) snapd branch to help with this: https://github.com/snapcore/snapd/pull/4055 It got a review yesterday, so should go in the next snapd release. This is basically doing (1), returning a Forbidden error when the user dismisses the dialog. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721735 Title: UbuntuOne auth dialog is displayed when polkit auth dialog is dismissed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1721735/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724316] Re: "Sorry, something went wrong cannot authenticate to snap store ..." without any way to fix
Snapd side changes: https://github.com/snapcore/snapd/pull/4061 It looks like snapd-glib might need a change too, since it looks like this will still be mapped to SNAPD_ERROR_FAILED in parse_result() (I think falling back to treating 401 as SNAPD_AUTH_DATA_REQUIRED will do). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724316 Title: "Sorry, something went wrong cannot authenticate to snap store ..." without any way to fix To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1724316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724316] Re: "Sorry, something went wrong cannot authenticate to snap store ..." without any way to fix
Yep. There is code to prevent refreshing the macaroon if the user has changed their password since it was created: http://bazaar.launchpad.net/~canonical-isd-hackers/canonical-identity- provider/trunk/view/head:/src/identityprovider/auth.py#L661 This should help in reproducing the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724316 Title: "Sorry, something went wrong cannot authenticate to snap store ..." without any way to fix To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1724316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724316] Re: "Sorry, something went wrong cannot authenticate to snap store ..." without any way to fix
** Also affects: snapd 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/1724316 Title: "Sorry, something went wrong cannot authenticate to snap store ..." without any way to fix To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1724316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724316] Re: "Sorry, something went wrong cannot authenticate to snap store ..." without any way to fix
Discussion started here: https://forum.snapcraft.io/t/handling-invalid-credentials/2526 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724316 Title: "Sorry, something went wrong cannot authenticate to snap store ..." without any way to fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1724316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724316] Re: "Sorry, something went wrong cannot authenticate to snap store ..." without any way to fix
So further investigation, the "cannot authenticate to snap store: " part of the error is only added by snapd for an unexpected error: https://github.com/snapcore/snapd/blob/master/store/auth.go#L190-L204 I believe this is being called via the refreshDischarges() method, intended to keep the store macaroon up to date. This is called by any snapd API that talks to the store, so it isn't surprising we'd hit it during gnome-software start up. I wonder if changing your Ubuntu One password would be enough for the store to refuse to refresh the macaroon? So it looks like the fix probably requires the following: 1. snapd to handle the INVALID_CREDENTIALS response from the store and produce an error response that snapd-glib can distinguish. 2. snapd-glib to handle this error case and map it to one of its error codes (either a new one, or fold it into invalid-auth-data?) 3. if snapd-glib produces a new error code, for gnome-software's snap plugin to map this to an appropriate error code. The end result should be for gnome-software to call the /v2/login end point again, probably passing its existing macaroon so it updates the existing snapd user rather than creating another (i.e. what would happen to paid snaps for a discarded snapd user ID when it comes time to refresh?). I'll follow up with the snappy team to verify that this is the way forward. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724316 Title: "Sorry, something went wrong cannot authenticate to snap store ..." without any way to fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1724316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724316] Re: "Sorry, something went wrong cannot authenticate to snap store ..." without any way to fix
The "Provided email/password is not correct." part of the error message appears to be coming through straight from the store. This most likely means you logged in to gnome-software using Ubuntu One credentials at some point in the past, and the credentials snapd has stored are no longer valid. It might be possible to reproduce this by logging in in gnome-software (currently possible by cancelling the polkit dialog), stopping snapd, editing /var/lib/snapd/state.json to tamper with the store-macaroon value and starting snapd again. I'll need to verify if this happens. The "Sorry, something went wrong" comes from gnome-software itself, and indicates that the error could not be classified as one of the GS_PLUGIN_ERROR_* error codes. The code in gnome-software's snap plugin specifically checks for various authentication related error conditions (SNAPD_ERROR_AUTH_DATA_REQUIRED and SNAPD_ERROR_AUTH_DATA_REQUIRED in particular), but that clearly isn't being hit. So I think there are two possibilities here: 1. libsnapd-glib isn't returning the correct error type for this case 2. snapd isn't providing enough info to libsnapd-glib to decode the error -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724316 Title: "Sorry, something went wrong cannot authenticate to snap store ..." without any way to fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1724316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1722195] Re: no policy kit auth dialog to install or remove a snap
I set up a clean VM running up to date artful, which includes snapd-2.28.5+17.10 (so no copying of policy files or changing channel for core snap), and couldn't reproduce this. I started gnome-software, and tried to install the Hiri snap and got the expected polkit prompt. I did get the following message though: Unable to install Hiri Failed to read from snapd: Error receiving data: Connection reset by peer Snapd restarted during the install, presumably after it installed the core snap, so this seems like another variation of bug 1718170. If you got a polkit prompt from the command line "snap" utility but not in gnome-software, that would indicate that it was not sending the X -Allow-Interaction header. We added that in snapd-glib 1.19, and you've got 1.23 installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722195 Title: no policy kit auth dialog to install or remove a snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1722195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720331] Re: Whoopsie continually relaunching
Changing the gnome-control-center task to low priority, since the restart loop is gone with the new whoopsie-preferences that has landed in the archive. The gnome-control-center change is nice, but I don't think it is critical to releasing 17.10 any more. ** Changed in: gnome-control-center (Ubuntu) Importance: Medium => Low ** Changed in: whoopsie-preferences (Ubuntu) Assignee: (unassigned) => James Henstridge (jamesh) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720331 Title: Whoopsie continually relaunching To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1720331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720331] Re: Whoopsie continually relaunching
** Also affects: whoopsie-preferences (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/1720331 Title: Whoopsie continually relaunching To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1720331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720331] Re: Whoopsie continually relaunching
So I think I've got things sorted out by (a) switching to call SetReportCrashes async to avoid blocking the UI, and (b) not calling SetReportCrashes if we're asked to set it to the current (cached) value of the property. I've noticed that if whoopsie-preferences exits while the privacy panel is open, I get a bit of a bounce when toggling the switch next. This seems to be due to whoopsie-preferences sending out a stray change notification signal on start up: method call time=1507538340.672978 sender=:1.1499 -> destination=com.ubuntu.WhoopsiePreferences serial=30 path=/com/ubuntu/WhoopsiePreferences; interface=com.ubuntu.WhoopsiePreferences; member=SetReportCrashes boolean false signal time=1507538340.756225 sender=:1.1507 -> destination=(null destination) serial=9 path=/com/ubuntu/WhoopsiePreferences; interface=org.freedesktop.DBus.Properties; member=PropertiesChanged string "com.ubuntu.WhoopsiePreferences" array [ dict entry( string "ReportMetrics" variant boolean true ) dict entry( string "ReportCrashes" variant boolean true ) ] array [ ] method call time=1507538340.756590 sender=:1.1499 -> destination=:1.1507 serial=31 path=/com/ubuntu/WhoopsiePreferences; interface=org.freedesktop.DBus.Properties; member=GetAll string "com.ubuntu.WhoopsiePreferences" method call time=1507538340.757395 sender=:1.1499 -> destination=com.ubuntu.WhoopsiePreferences serial=32 path=/com/ubuntu/WhoopsiePreferences; interface=com.ubuntu.WhoopsiePreferences; member=SetReportCrashes boolean true signal time=1507538341.034321 sender=:1.1507 -> destination=(null destination) serial=14 path=/com/ubuntu/WhoopsiePreferences; interface=org.freedesktop.DBus.Properties; member=PropertiesChanged string "com.ubuntu.WhoopsiePreferences" array [ dict entry( string "ReportCrashes" variant boolean false ) ] array [ ] method call time=1507538341.035076 sender=:1.1499 -> destination=:1.1507 serial=33 path=/com/ubuntu/WhoopsiePreferences; interface=com.ubuntu.WhoopsiePreferences; member=SetReportCrashes boolean false So essentially whoopsie-preferences is sending out an unsolicited PropertiesChanged signal on startup with the initial values before processing the SetReportCrashes method call. Then gnome-control-center responds by trying to match the switch state leading to the bounce. So I guess I'll have to dive into the whoopsie-preferences code to see if I can silence the stray signal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720331 Title: Whoopsie continually relaunching To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1720331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720331] Re: Whoopsie continually relaunching
This is definitely a gnome-control-center bug rather than whoopsie. I can reproduce it like so: 1. open gnome-control-center, and select the privacy panel. 2. ensure that problem reporting is turned on. 3. wait for whoopsie-preferences to exit on timeout (or manually kill it). I then see traffic like the following on the system bus: method call time=1507286449.661622 sender=:1.325 -> destination=:1.336 serial=96 path=/com/ubuntu/WhoopsiePreferences; interface=com.ubuntu.WhoopsiePreferences; member=SetReportCrashes boolean false method call time=1507286449.918969 sender=:1.325 -> destination=:1.336 serial=97 path=/com/ubuntu/WhoopsiePreferences; interface=com.ubuntu.WhoopsiePreferences; member=SetReportCrashes boolean true method call time=1507286450.216068 sender=:1.325 -> destination=:1.336 serial=98 path=/com/ubuntu/WhoopsiePreferences; interface=com.ubuntu.WhoopsiePreferences; member=SetReportCrashes boolean false method call time=1507286450.529908 sender=:1.325 -> destination=:1.336 serial=99 path=/com/ubuntu/WhoopsiePreferences; interface=com.ubuntu.WhoopsiePreferences; member=SetReportCrashes boolean true ... which continues until I kill gnome-control-center. Whoopsie relaunching is a direct consequence of these D-Bus method calls coming from gnome- control-center. It looks like the logic controlling the GtkSwitch gets into a loop when whoopsie-preferences stops. The D-Bus method calls are synchronous, so this also ends up locking the UI. I'll have a look into this properly next week. ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-control-center (Ubuntu) Status: New => Triaged ** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => James Henstridge (jamesh) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720331 Title: Whoopsie continually relaunching To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1720331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720331] Re: Whoopsie continually relaunching
** Also affects: gnome-control-center (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/1720331 Title: Whoopsie continually relaunching To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1720331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715479] Re: Touchpad won't stay disabled after resuming from suspend
** Bug watch added: Red Hat Bugzilla #1448962 https://bugzilla.redhat.com/show_bug.cgi?id=1448962 ** Also affects: libinput (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1448962 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715479 Title: Touchpad won't stay disabled after resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715479] Re: Touchpad won't stay disabled after resuming from suspend
While looking around for code that might resume the touchpad, I noticed that the libinput master code was a bit different to the version we ship: there's a tp_resume_conditional() function that checks sendevents. And checking the history shows up this patch: https://cgit.freedesktop.org/wayland/libinput/commit/src?id=53d53dd18ef14484d632421027cd7b6130013cf0 Fedora is also shipping this as a patch against their libinput-1.8.2 in Fedora 27: https://src.fedoraproject.org/rpms/libinput/blob/f27/f/0001-touchpad- don-t-resume-a-disabled-touchpad.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715479 Title: Touchpad won't stay disabled after resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1715479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1715479] Re: Touchpad won't stay disabled after resuming from suspend
So, I don't think there is any problem on the gnome-control-center side: it just sets the org.gnome.desktop.peripherals.touchpad/send-events GSetting key to disabled, and that is persisting over sleeps. The code in mutter watches this key, and calls MetaInputSettings::set_send_events() on each touchpad device, and ensures it is called on each new input device. https://git.gnome.org/browse/mutter/tree/src/backends/meta-input- settings.c#n667 In a Wayland session, this calls libinput_device_config_send_events_set_mode(): https://git.gnome.org/browse/mutter/tree/src/backends/native/meta-input- settings-native.c#n36 The touchpad implementation of this is found here: https://cgit.freedesktop.org/wayland/libinput/tree/src/evdev-mt- touchpad.c#n3089 ... which calls tp_suspend: https://cgit.freedesktop.org/wayland/libinput/tree/src/evdev-mt- touchpad.c#n1670 Which will either leave the touchpad enabled to support soft buttons, or call evdev_device_suspend() otherwise, which closes the underlying device. Looking in /proc, gnome-shell definitely doesn't have the touchpad evdev device open when I disable the touchpad, but somehow opens it again after resume. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715479 Title: Touchpad won't stay disabled after resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1715479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1698035] Re: FFe: gnome-control-center lacks any replacement for unity-control-center's Diagnostics tab for managing crash reports
I've sent our patch upstream to see if we can get a version of it included. I suspect it'll need some changes in order to be acceptable, assuming they want it. So I'll try to address that as needed. ** Bug watch added: GNOME Bug Tracker #788216 https://bugzilla.gnome.org/show_bug.cgi?id=788216 ** Also affects: gnome-control-center via https://bugzilla.gnome.org/show_bug.cgi?id=788216 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1698035 Title: FFe: gnome-control-center lacks any replacement for unity-control- center's Diagnostics tab for managing crash reports To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1698035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1698035] Re: gnome-control-center lacks any replacement for unity-control-center's Diagnostics tab for managing crash reports
** Branch linked: lp:~jamesh/gnome-control-center/ubuntu-whoopsie- support -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1698035 Title: gnome-control-center lacks any replacement for unity-control-center's Diagnostics tab for managing crash reports To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1698035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581713] Re: Ubuntu Software always asks for an Ubuntu Single Sign-On account when installing or removing a snap package
The snapd side of things has been committed. Both on master: https://github.com/snapcore/snapd/commit/44611140566f6e6aa2a3b583e0b2970b69c8f53f ... and the release/2.28 branch: https://github.com/snapcore/snapd/commit/69a00bc4f4e54d7e0312c253b46b97fca834b736 Together with the already released snapd-glib 1.19, this version of snapd will let you install snaps via gnome-software without an Ubuntu One account. Instead you'll get a graphical prompt for your local password, similar to when installing debs. ** Changed in: snapd (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: snapd (Ubuntu) Assignee: (unassigned) => James Henstridge (jamesh) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581713 Title: Ubuntu Software always asks for an Ubuntu Single Sign-On account when installing or removing a snap package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1581713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1704162] Re: Add on/off switch for network connectivity check
** Bug watch added: GNOME Bug Tracker #785117 https://bugzilla.gnome.org/show_bug.cgi?id=785117 ** Also affects: network-manager via https://bugzilla.gnome.org/show_bug.cgi?id=785117 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1704162 Title: Add on/off switch for network connectivity check To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1704162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690280] Re: Classic confined snaps don't install
** Bug watch added: GNOME Bug Tracker #784773 https://bugzilla.gnome.org/show_bug.cgi?id=784773 ** Also affects: gnome-software via https://bugzilla.gnome.org/show_bug.cgi?id=784773 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690280 Title: Classic confined snaps don't install To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1690280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1661590] Re: GNOME Software only supports running one application from a snap
** Bug watch added: GNOME Bug Tracker #784600 https://bugzilla.gnome.org/show_bug.cgi?id=784600 ** Also affects: gnome-software via https://bugzilla.gnome.org/show_bug.cgi?id=784600 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1661590 Title: GNOME Software only supports running one application from a snap To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1661590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1661590] Re: GNOME Software only supports running one application from a snap
I put together a gnome-software patch to use the extra info from mvo's snapd change: https://code.launchpad.net/~jamesh/gnome-software/+git/gnome- software/+ref/pick-launch-app It still only supports running one application, but it now favours apps that provide a desktop file, and the snap's main app as a tie breaker. For Libreoffice, this reliably picks the main "libreoffice" binary. It also launches the app via the desktop file if available, so we don't have to guess whether it needs a terminal in that case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1661590 Title: GNOME Software only supports running one application from a snap To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1661590/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690280] Re: Classic confined snaps don't install
I've made some simple UI changes in the following branch forked from ubuntu-master, based on Robert's patch: https://code.launchpad.net/~jamesh/gnome-software/+git/gnome- software/+ref/classic-snap-install This adds a warning message at the top of the details list when viewing an snap that is not using strict confinement. If we get the text of this right, then this could be enough. Currently it reads: This third party package is not sandboxed. It will have access to your documents. Thinking about it, this warning is equally valid for strictly confined snaps that connect to the home interface. I don't think there is a way to identify such apps based on the metadata returned by "find" API requests though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690280 Title: Classic confined snaps don't install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1690280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665160] Re: MachineSuite.TestMachineWorkers timed out waiting for workers zesty because dbus is in interactive mode
With Chris's help we got the tests to get past the D-Bus errors on Zesty by creating a file /etc/polkit-1/localauthority/50-local.d/manage- units.pkla on the test system with the following contents: # Allow the "ubuntu" user to manage systemd units unconditionally for testing [Allow manage-units] Identity=unix-user:ubuntu Action=org.freedesktop.systemd1.manage-units;org.freedesktop.systemd1.manage-unit-files ResultAny=yes ResultInactive=yes ResultActive=yes (It turned out that manage-unit-files was also needed to enable/disable services). This basically instructs polkitd to tell systemd that it is okay for the "ubuntu" user to manage system services without having to re-enter their password. Assuming that's what you expect while running the tests, the CI scripts should be updated to add this file to the container. There shouldn't be any need to special case this for Zesty: it should be fine to create the .pkla file on older releases too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665160 Title: MachineSuite.TestMachineWorkers timed out waiting for workers zesty because dbus is in interactive mode To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1665160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665160] Re: MachineSuite.TestMachineWorkers timed out waiting for workers zesty because dbus is in interactive mode
Anastasia asked me to take a look at this. I'm still not sure what the underlying cause is, but here is some of what I've discovered so far. 1. There has been a change in policykit-1 that sounds like it might be relevant. Namely: [ Martin Pitt ] * Use PAM's common-session-noninteractive modules for pkexec instead of common-session. The latter also runs pam_systemd (the only difference normally) which is a no-op under the classic session-centric D-BUS/graphical login model (as it won't start a new one if it is already running within a logind session), but very expensive when using dbus-user-session and being called from a service that runs outside the PAM session. This causes long delays in e. g. gnome-settings-daemon's backlight helpers. (LP: #1626651) So if something is being run by pkexec, it is no longer executing pam_systemd.so. That module is responsible for registering with logind, setting up the user bus, etc. So it seems possible that there is some code in the test suite that looked like it was running under an interactive user session on Xenial, but doesn't any more on Zesty. 2. The default policies for systemd1.manage-units haven't changed between versions. In both cases, it reads: auth_admin auth_admin auth_admin_keep So it is possible that the test works on previous versions by piggy backing off a previous authorisation via auth_admin_keep. If we look like a non-interactive invocation on Zesty, we may need authentication every time now. 3. Maybe we can bypass all of this by configuring the polkit local authority to allow the test process to manage units unconditionally. This would work for all versions irrespective of whether we look like an interactive session. This would involve placing a policy file under /etc/polkit-1/localauthority/50-local.d before running the tests. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665160 Title: MachineSuite.TestMachineWorkers timed out waiting for workers zesty because dbus is in interactive mode To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1665160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682357] [NEW] Unicode decode problems with fast-export
Public bug reported: [this is in conjunction with python-fastimport 0.9.6-2] While trying to use "bzr fast-export" on some of my branches, I ran into a few unicode related problems: 1. it seems python-fastimport expects the user's name/email to be in Unicode now. 2. python-fastimport expects the target of a symlink to be passed as a byte string. Attached is a patch to address both issues. ** Affects: bzr-fastimport (Ubuntu) Importance: Undecided Status: New ** Affects: bzr-fastimport (Debian) Importance: Unknown Status: Unknown ** Patch added: "unicode-fixes.patch" https://bugs.launchpad.net/bugs/1682357/+attachment/4861075/+files/unicode-fixes.patch ** Bug watch added: Debian Bug tracker #860232 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860232 ** Also affects: bzr-fastimport (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860232 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682357 Title: Unicode decode problems with fast-export To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bzr-fastimport/+bug/1682357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1676690] [NEW] keeper command line client does not exit when run with no arguments
Public bug reported: If I run the keeper command line client with no arguments, it prints a debug message and then sits sits hangs seemingly doing nothing: $ /usr/lib/x86_64-linux-gnu/keeper/keeper [debug] More or none arguments (src/cli/command-line.cpp:98) I assume the tool is intended to only be called with a sub-command as an argument, so in this case I would expect it to print an error and exit immediately. ** Affects: keeper (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/1676690 Title: keeper command line client does not exit when run with no arguments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keeper/+bug/1676690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1676688] [NEW] keeper command line client can't be killed with ctrl+C
Public bug reported: When I was running through the storage-provider-webdav test plan, I had the backup stall due to bug 1676361. I tried using ctrl+C to kill the client, but it just kept on running. It also seems to ignore SIGTERM, so I could only kill it with SIGKILL or ctrl+\. ** Affects: keeper (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/1676688 Title: keeper command line client can't be killed with ctrl+C To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keeper/+bug/1676688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1676361] Re: keeper-service segfaults inside ubuntu::app_launch::helper_impls::Base::launch
** Description changed: While running through the test plan for storage-framework, I had keeper- service segfault inside libubuntu-app-launch I suspect that this is related to the recent ubuntu-app-launch 0.11 landing, which says it removes upstart and click support. Attached is a backtrace I captured on a xenial+overlay system with debug - symbols installed. + symbols installed. It occurred when running through the following test + plan at the "keeper backup" step: + + https://wiki.ubuntu.com/Process/Merges/TestPlan/storage-provider-webdav -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1676361 Title: keeper-service segfaults inside ubuntu::app_launch::helper_impls::Base::launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keeper/+bug/1676361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1676361] [NEW] keeper-service segfaults inside ubuntu::app_launch::helper_impls::Base::launch
Public bug reported: While running through the test plan for storage-framework, I had keeper- service segfault inside libubuntu-app-launch I suspect that this is related to the recent ubuntu-app-launch 0.11 landing, which says it removes upstart and click support. Attached is a backtrace I captured on a xenial+overlay system with debug symbols installed. ** Affects: keeper (Ubuntu) Importance: Critical Status: New ** Attachment added: "backtrace.txt" https://bugs.launchpad.net/bugs/1676361/+attachment/4847033/+files/backtrace.txt ** Changed in: keeper (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1676361 Title: keeper-service segfaults inside ubuntu::app_launch::helper_impls::Base::launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keeper/+bug/1676361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1604640] Re: provider-test dumps core if second instance is started
** Changed in: storage-framework (Ubuntu) Status: In Progress => 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/1604640 Title: provider-test dumps core if second instance is started To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/storage-framework/+bug/1604640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1668872] Re: provider::Item should have its own header file
** Changed in: storage-framework (Ubuntu) Status: In Progress => 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/1668872 Title: provider::Item should have its own header file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/storage-framework/+bug/1668872/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
