[Bug 1966780] [NEW] transmission-qt crashes when UI element is destroyed before RPC call gets to update it
Public bug reported: Currently Transmission (Qt client) crashes really often when you just use it against a distant server. This is because the RPC callback tries to update an UI element that is often destroyed. Please backport this patch to Ubuntu releases as soon as possible as this crash is very frequent for some users. https://github.com/transmission/transmission/pull/1604 ** Affects: transmission Importance: Unknown Status: Unknown ** Affects: transmission (Ubuntu) Importance: Undecided Status: Confirmed ** Changed in: transmission (Ubuntu) Status: New => Confirmed ** Bug watch added: github.com/transmission/transmission/issues #1510 https://github.com/transmission/transmission/issues/1510 ** Also affects: transmission via https://github.com/transmission/transmission/issues/1510 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/1966780 Title: transmission-qt crashes when UI element is destroyed before RPC call gets to update it To manage notifications about this bug go to: https://bugs.launchpad.net/transmission/+bug/1966780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908928] Re: locales 2.27-3ubuntu1.4 enabled random locales
** Changed in: glibc (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908928 Title: locales 2.27-3ubuntu1.4 enabled random locales To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1908928/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965535] Re: Stop recommending snap
It's also worth pointing out how snap does not offer feature parity. VA- API and native-component extensions are broken to this day with Chromium snap, for four years now. The latter meaning that entire countries can not use chromium snap if they wish to use their national authentication and signature system on the web. Broken for millions of potential users and nobody cares. Seeing how shipping fully-working software seems not doable with snaps, recommending it as a default is an user-hostile decision at this point in time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965535 Title: Stop recommending snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1965535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960307] Re: No gstreamer dependency causes high-fidelity codecs to be missing for Bluetooth devices
** Bug watch added: Debian Bug tracker #991597 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991597 ** Also affects: pulseaudio via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991597 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/1960307 Title: No gstreamer dependency causes high-fidelity codecs to be missing for Bluetooth devices To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1960307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960307] Re: No gstreamer dependency causes high-fidelity codecs to be missing for Bluetooth devices
** Also affects: gstreamer1.0 (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/1960307 Title: No gstreamer dependency causes high-fidelity codecs to be missing for Bluetooth devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1960307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location
@dimitri-papadopoulos If there's a high likelihood that ceph will be used on a desktop distribution then its choice of snapshot directory has been incorrect in two ways. The way forward would be to not ignore conventions designed to avoid such issues :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575053 Title: Please move the "$HOME/snap" directory to a less obtrusive location To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1575053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960307] [NEW] No gstreamer dependency causes high-fidelity codecs to be missing for Bluetooth devices
Public bug reported: After the announcements of PulseAudio 15 and Gstreamer 1.20, which both advertised LDAC and AptX (HD) support, I expected that jammy (22.04) would support those codecs. Though in reality it seems that something is missing, gstreamer reports that those codecs are supported but "pactl [...] list-codec" only lists sbc (and variants). Checking here https://packages.ubuntu.com/jammy/pulseaudio-module- bluetooth it seems that PulseAudio is not built with gstreamer support, is that the current blocker? ** Affects: gst-plugins-bad1.0 (Ubuntu) Importance: Undecided Status: New ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Also affects: gst-plugins-bad1.0 (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/1960307 Title: No gstreamer dependency causes high-fidelity codecs to be missing for Bluetooth devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1960307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908928] Re: locales 2.27-3ubuntu1.4 enabled random locales
The upgrade was done on a totally pristine Kubuntu 18.04 install that didn't have anything out-of-standard installed. So it's a package in the default repositories. I think I'm not the only one who has noticed these anomalies either (an AskUbuntu thread that's 2mo old): https://askubuntu.com/questions/1301908/locale-gen-generates-not- selected-locales -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908928 Title: locales 2.27-3ubuntu1.4 enabled random locales To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1908928/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908928] Re: locales 2.27-3ubuntu1.4 enabled random locales
I ran an upgrade from 18.04 to 20.04 and it generated these locales: ``` Generating locales (this might take a while)... en_AG.UTF-8... done en_AU.UTF-8... done en_BW.UTF-8... done en_CA.UTF-8... done en_DK.UTF-8... done en_GB.UTF-8... done en_HK.UTF-8... done en_IE.UTF-8... done en_IL.UTF-8... done en_IN.UTF-8... done en_NG.UTF-8... done en_NZ.UTF-8... done en_PH.UTF-8... done en_SG.UTF-8... done en_US.UTF-8... done en_ZA.UTF-8... done en_ZM.UTF-8... done en_ZW.UTF-8... done et_EE.UTF-8... done Generation complete. ``` While only `et_EE.UTF-8`, `en_GB.UTF-8` and `en_US.UTF-8` were enabled. This is `/var/lib/locales/supported.d/en` after the release upgrade: ``` en_HK.UTF-8 UTF-8 en_DK.UTF-8 UTF-8 en_IN UTF-8 en_IL UTF-8 en_ZM UTF-8 en_ZW.UTF-8 UTF-8 en_NZ.UTF-8 UTF-8 en_PH.UTF-8 UTF-8 en_NG UTF-8 en_US.UTF-8 UTF-8 en_GB.UTF-8 UTF-8 en_AU.UTF-8 UTF-8 en_SG.UTF-8 UTF-8 en_BW.UTF-8 UTF-8 en_AG UTF-8 en_ZA.UTF-8 UTF-8 en_CA.UTF-8 UTF-8 en_IE.UTF-8 UTF-8 ``` I think the locale package is still overriding user wishes and some installation script is generating files it should not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908928 Title: locales 2.27-3ubuntu1.4 enabled random locales To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1908928/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914918] Re: The snap being updated in the background causes both old and new tabs to die to SIGTRAP
> I've seen no problems for last 5 days, while before, I had to restart browser every couple hours. Similar experience here with refresh-app-awareness + no robust-mount- namespace-updates. One problem I did see was related to audio output breaking. Restart fixed it. Might just be a Chromium anomaly I wouldn't attribute to snap. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914918 Title: The snap being updated in the background causes both old and new tabs to die to SIGTRAP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1914918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914918] Re: The snap being updated in the background causes both old and new tabs to die to SIGTRAP
Ran it, will report back how it affects behaviour, thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914918 Title: The snap being updated in the background causes both old and new tabs to die to SIGTRAP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1914918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914918] Re: The snap being updated in the background causes both old and new tabs to die to SIGTRAP
There are no good workarounds either, it observably causes anomalies in apps. Some PWAs lose their state after a restart and it's infuriating. Canonical should dogfood their own known breaking changes. ** Also affects: snapd (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/1914918 Title: The snap being updated in the background causes both old and new tabs to die to SIGTRAP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1914918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914918] [NEW] The snap being updated in the background causes both old and new tabs to die to SIGTRAP
Public bug reported: The last few background updates of chromium have made some old tabs suddenly crash with SIGTRAP and it also makes it impossible to open new tabs, those die instantly with a SIGTRAP as well. This is incredibly destructive to whatever might be the dying tabs' unsaved state and there's no warning about it. Yet again a snap-related change rolled out to users with absolutely amateur-tier testing. Ubuntu: 20.04.2 Snap: 2.48+20.04 Chromium: 88.0.4324.150 ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914918 Title: The snap being updated in the background causes both old and new tabs to die to SIGTRAP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1914918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913609] Re: Ungraceful failure when locale postinstallation script can't modify files it shouldn't
*** This bug is a duplicate of bug 1908928 *** https://bugs.launchpad.net/bugs/1908928 Even if we ignore all that, the very least it should prompt the user if the file should be replaced with the maintainer version or be kept as is. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913609 Title: Ungraceful failure when locale postinstallation script can't modify files it shouldn't To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1913609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913609] Re: Ungraceful failure when locale postinstallation script can't modify files it shouldn't
*** This bug is a duplicate of bug 1908928 *** https://bugs.launchpad.net/bugs/1908928 Not really blindly, there are other situations where configuration files might be locked. Plus technically an update shouldn't demand write access unless its actually needed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913609 Title: Ungraceful failure when locale postinstallation script can't modify files it shouldn't To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1913609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913609] Re: Ungraceful failure when locale postinstallation script can't modify files it shouldn't
*** This bug is a duplicate of bug 1908928 *** https://bugs.launchpad.net/bugs/1908928 @gunnarhj Ideally the post-installation script didn't fail if it can't modify the file, irrelevant of the reason why it's not writable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913609 Title: Ungraceful failure when locale postinstallation script can't modify files it shouldn't To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1913609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908928] Re: locales 2.27-3ubuntu1.4 enabled random locales
# dpkg -l | grep -E 'language-pack-\w+-base' # -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908928 Title: locales 2.27-3ubuntu1.4 enabled random locales To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1908928/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908928] Re: locales 2.27-3ubuntu1.4 enabled random locales
At that point, no permissions were changed because no such issue had occured. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908928 Title: locales 2.27-3ubuntu1.4 enabled random locales To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1908928/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908928] Re: locales 2.27-3ubuntu1.4 enabled random locales
locale.gen was last modified in 11-03-2019 before these updates were applied. Some package amongst those decided to enable 25 new locales. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908928 Title: locales 2.27-3ubuntu1.4 enabled random locales To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1908928/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908928] Re: locales 2.27-3ubuntu1.4 enabled random locales
@gunnarhj > I meant to ask which package updates result in generation of new locales. One of these, but locale/libc is the only one really related to this functionality: dpkg.log.2.gz:2020-12-21 18:41:36 startup archives unpack dpkg.log.2.gz:2020-12-21 18:41:38 upgrade libc6-i386:amd64 2.27-3ubuntu1.3 2.27-3ubuntu1.4 dpkg.log.2.gz:2020-12-21 18:41:38 status triggers-pending libc-bin:amd64 2.27-3ubuntu1.3 dpkg.log.2.gz:2020-12-21 18:41:38 status half-configured libc6-i386:amd64 2.27-3ubuntu1.3 dpkg.log.2.gz:2020-12-21 18:41:38 status unpacked libc6-i386:amd64 2.27-3ubuntu1.3 dpkg.log.2.gz:2020-12-21 18:41:38 status half-installed libc6-i386:amd64 2.27-3ubuntu1.3 dpkg.log.2.gz:2020-12-21 18:41:39 status half-installed libc6-i386:amd64 2.27-3ubuntu1.3 dpkg.log.2.gz:2020-12-21 18:41:39 status unpacked libc6-i386:amd64 2.27-3ubuntu1.4 dpkg.log.2.gz:2020-12-21 18:41:39 status unpacked libc6-i386:amd64 2.27-3ubuntu1.4 dpkg.log.2.gz:2020-12-21 18:41:39 upgrade libc6-dev:amd64 2.27-3ubuntu1.3 2.27-3ubuntu1.4 dpkg.log.2.gz:2020-12-21 18:41:39 status half-configured libc6-dev:amd64 2.27-3ubuntu1.3 dpkg.log.2.gz:2020-12-21 18:41:39 status unpacked libc6-dev:amd64 2.27-3ubuntu1.3 dpkg.log.2.gz:2020-12-21 18:41:39 status half-installed libc6-dev:amd64 2.27-3ubuntu1.3 dpkg.log.2.gz:2020-12-21 18:41:40 status half-installed libc6-dev:amd64 2.27-3ubuntu1.3 dpkg.log.2.gz:2020-12-21 18:41:40 status unpacked libc6-dev:amd64 2.27-3ubuntu1.4 dpkg.log.2.gz:2020-12-21 18:41:40 status unpacked libc6-dev:amd64 2.27-3ubuntu1.4 dpkg.log.2.gz:2020-12-21 18:41:40 upgrade libc-dev-bin:amd64 2.27-3ubuntu1.3 2.27-3ubuntu1.4 dpkg.log.2.gz:2020-12-21 18:41:40 status half-configured libc-dev-bin:amd64 2.27-3ubuntu1.3 dpkg.log.2.gz:2020-12-21 18:41:40 status unpacked libc-dev-bin:amd64 2.27-3ubuntu1.3 dpkg.log.2.gz:2020-12-21 18:41:40 status half-installed libc-dev-bin:amd64 2.27-3ubuntu1.3 dpkg.log.2.gz:2020-12-21 18:41:40 status triggers-pending man-db:amd64 2.8.3-2ubuntu0.1 dpkg.log.2.gz:2020-12-21 18:41:41 status half-installed libc-dev-bin:amd64 2.27-3ubuntu1.3 dpkg.log.2.gz:2020-12-21 18:41:41 status unpacked libc-dev-bin:amd64 2.27-3ubuntu1.4 dpkg.log.2.gz:2020-12-21 18:41:41 status unpacked libc-dev-bin:amd64 2.27-3ubuntu1.4 dpkg.log.2.gz:2020-12-21 18:41:41 upgrade libc6:amd64 2.27-3ubuntu1.3 2.27-3ubuntu1.4 dpkg.log.2.gz:2020-12-21 18:41:41 status half-configured libc6:amd64 2.27-3ubuntu1.3 dpkg.log.2.gz:2020-12-21 18:41:41 status unpacked libc6:amd64 2.27-3ubuntu1.3 dpkg.log.2.gz:2020-12-21 18:41:41 status half-installed libc6:amd64 2.27-3ubuntu1.3 dpkg.log.2.gz:2020-12-21 18:41:42 status half-installed libc6:amd64 2.27-3ubuntu1.3 dpkg.log.2.gz:2020-12-21 18:41:42 status unpacked libc6:amd64 2.27-3ubuntu1.4 dpkg.log.2.gz:2020-12-21 18:41:42 status unpacked libc6:amd64 2.27-3ubuntu1.4 dpkg.log.2.gz:2020-12-21 18:41:42 startup packages configure dpkg.log.2.gz:2020-12-21 18:41:42 configure libc6:amd64 2.27-3ubuntu1.4 dpkg.log.2.gz:2020-12-21 18:41:42 status unpacked libc6:amd64 2.27-3ubuntu1.4 dpkg.log.2.gz:2020-12-21 18:41:42 status unpacked libc6:amd64 2.27-3ubuntu1.4 dpkg.log.2.gz:2020-12-21 18:41:42 status half-configured libc6:amd64 2.27-3ubuntu1.4 dpkg.log.2.gz:2020-12-21 18:41:43 status installed libc6:amd64 2.27-3ubuntu1.4 dpkg.log.2.gz:2020-12-21 18:41:43 startup archives unpack dpkg.log.2.gz:2020-12-21 18:41:43 upgrade locales:all 2.27-3ubuntu1.3 2.27-3ubuntu1.4 dpkg.log.2.gz:2020-12-21 18:41:43 status half-configured locales:all 2.27-3ubuntu1.3 dpkg.log.2.gz:2020-12-21 18:41:43 status unpacked locales:all 2.27-3ubuntu1.3 dpkg.log.2.gz:2020-12-21 18:41:43 status half-installed locales:all 2.27-3ubuntu1.3 dpkg.log.2.gz:2020-12-21 18:41:44 status half-installed locales:all 2.27-3ubuntu1.3 dpkg.log.2.gz:2020-12-21 18:41:44 status unpacked locales:all 2.27-3ubuntu1.4 dpkg.log.2.gz:2020-12-21 18:41:44 status unpacked locales:all 2.27-3ubuntu1.4 dpkg.log.2.gz:2020-12-21 18:41:44 upgrade libc-bin:amd64 2.27-3ubuntu1.3 2.27-3ubuntu1.4 dpkg.log.2.gz:2020-12-21 18:41:44 status half-configured libc-bin:amd64 2.27-3ubuntu1.3 dpkg.log.2.gz:2020-12-21 18:41:44 status unpacked libc-bin:amd64 2.27-3ubuntu1.3 dpkg.log.2.gz:2020-12-21 18:41:44 status half-installed libc-bin:amd64 2.27-3ubuntu1.3 dpkg.log.2.gz:2020-12-21 18:41:45 status half-installed libc-bin:amd64 2.27-3ubuntu1.3 dpkg.log.2.gz:2020-12-21 18:41:45 status unpacked libc-bin:amd64 2.27-3ubuntu1.4 dpkg.log.2.gz:2020-12-21 18:41:45 status unpacked libc-bin:amd64 2.27-3ubuntu1.4 dpkg.log.2.gz:2020-12-21 18:41:45 startup packages configure dpkg.log.2.gz:2020-12-21 18:41:45 configure libc-bin:amd64 2.27-3ubuntu1.4 dpkg.log.2.gz:2020-12-21 18:41:45 status unpacked libc-bin:amd64 2.27-3ubuntu1.4 dpkg.log.2.gz:2020-12-21 18:41:45 status unpacked libc-bin:amd64 2.27-3ubuntu1.4 dpkg.log.2.gz:2020-12-21 18:41:45 status unpacked libc-bin:amd64 2.27-3ubuntu1.4 dpkg.log.2.gz:2020-12-21 18:41:45 status unpacked libc-bin:amd64 2.27-3ubuntu1.4 dpkg.log.2
[Bug 1913609] Re: Ungraceful failure when locale postinstallation script can't modify files it shouldn't
I answered under the issue about unwanted locales being enabled. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913609 Title: Ungraceful failure when locale postinstallation script can't modify files it shouldn't To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1913609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913609] Re: Ungraceful failure when locale postinstallation script can't modify files it shouldn't
> Exactly which updates are you talking about? That is listed in https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1908928 This issue is about the postinstallation script failing ungracefully if it can't sed the configuration files. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913609 Title: Ungraceful failure when locale postinstallation script can't modify files it shouldn't To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1913609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908928] Re: locales 2.27-3ubuntu1.4 enabled random locales
That configuration was already done. Package upgrade changed it. ** Changed in: glibc (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908928 Title: locales 2.27-3ubuntu1.4 enabled random locales To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1908928/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913609] Re: Ungraceful failure when locale postinstallation script can't modify files it shouldn't
That configuration is already done. ** Changed in: glibc (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913609 Title: Ungraceful failure when locale postinstallation script can't modify files it shouldn't To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1913609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913609] [NEW] Ungraceful failure when locale postinstallation script can't modify files it shouldn't
Public bug reported: When the files /etc/locale.gen, /etc/default/locale and /var/lib/locales/supported.d/en are locked down to avoid any unnecessary modifications done to them, the post-installation script of locales fails ungracefully when trying to sed (due to write permission denial). Those files are locked down because some updates decide to suddenly start generating a massive amount of locales and it can have disastrous effects if there's not a lot of storage e.g. https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1908928 There should really be no need to overwrite or modify those files by the package's installation without asking, this needs an user prompt or the user config must be kept. ** Affects: glibc (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Ungraceful failure when locale postinstallation script can't modify files + Ungraceful failure when locale postinstallation script can't modify files it shouldn't ** Description changed: When the files /etc/locale.gen, /etc/default/locale and /var/lib/locales/supported.d/en are locked down to avoid any unnecessary modifications done to them, the post-installation script of locales - fails ungracefully when trying to sed. + fails ungracefully when trying to sed (due to write permission denial). Those files are locked down because some updates decide to suddenly start generating a massive amount of locales and it can have disastrous effects if there's not a lot of storage e.g. https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1908928 There should really be no need to overwrite or modify those files by the package's installation without asking, this needs an user prompt or the user config must be kept. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913609 Title: Ungraceful failure when locale postinstallation script can't modify files it shouldn't To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1913609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900679] Re: [snap] Apparmor audit messages for calls to sched_setaffinity
Ubuntu 20.04.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900679 Title: [snap] Apparmor audit messages for calls to sched_setaffinity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900679] Re: [snap] chromium spams dmesg
I see sched_setaffinity also used in base/cpu_affinity_posix.cc, so I doubt it's only beneficial on ARM. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900679 Title: [snap] chromium spams dmesg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900679] Re: [snap] chromium spams dmesg
> @avamander, do you have a reproducer for this? I'm just using it on a Ryzen 9 3900x and Radeon R7 360. I have GPU acceleration enabled to the extent it is possible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900679 Title: [snap] chromium spams dmesg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887804] Re: chromium-browser does not follow XDG base directory specification
@~malakai1197 You're out of luck really, switch distributions that don't use half- baked snaps. Maintainers think that this usability regression is an "opinion" and that tells really more than enough. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887804 Title: chromium-browser does not follow XDG base directory specification To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1887804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900679] Re: [snap] chromium spams dmesg
[pid 1278591] sched_setaffinity(1278591, 128, [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128, 129, 130, 131, 132, 133, 134, 135, 136, 137, 138, 139, 140, 141, 142, 143, 144, 145, 146, 147, 148, 149, 150, 151, 152, 153, 154, 155, 156, 157, 158, 159, 160, 161, 162, 163, 164, 165, 166, 167, 168, 169, 170, 171, 172, 173, 174, 175, 176, 177, 178, 179, 180, 181, 182, 183, 184, 185, 186, 187, 188, 189, 190, 191, 192, 193, 194, 195, 196, 197, 198, 199, 200, 201, 202, 203, 204, 205, 206, 207, 208, 209, 210, 211, 212, 213, 214, 215, 216, 217, 218, 219, 220, 221, 222, 223, 224, 225, 226, 227, 228, 229, 230, 231, 232, 233, 234, 235, 236, 237, 238, 239, 240, 241, 242, 243, 244, 245, 246, 247, 248, 249, 250, 251, 252, 253, 254, 255, 256, 257, 258, 259, 260, 261, 262, 263, 264, 265, 266, 267, 268, 269, 270, 271, 272, 273, 274, 275, 276, 277, 278, 279, 280, 281, 282, 283, 284, 285, 286, 287, 288, 289, 290, 291, 292, 293, 294, 295, 296, 297, 298, 299, 300, 301, 302, 303, 304, 305, 306, 307, 308, 309, 310, 311, 312, 313, 314, 315, 316, 317, 318, 319, 320, 321, 322, 323, 324, 325, 326, 327, 328, 329, 330, 331, 332, 333, 334, 335, 336, 337, 338, 339, 340, 341, 342, 343, 344, 345, 346, 347, 348, 349, 350, 351, 352, 353, 354, 355, 356, 357, 358, 359, 360, 361, 362, 363, 364, 365, 366, 367, 368, 369, 370, 371, 372, 373, 374, 375, 376, 377, 378, 379, 380, 381, 382, 383, 384, 385, 386, 387, 388, 389, 390, 391, 392, 393, 394, 395, 396, 397, 398, 399, 400, 401, 402, 403, 404, 405, 406, 407, 408, 409, 410, 411, 412, 413, 414, 415, 416, 417, 418, 419, 420, 421, 422, 423, 424, 425, 426, 427, 428, 429, 430, 431, 432, 433, 434, 435, 436, 437, 438, 439, 440, 441, 442, 443, 444, 445, 446, 447, 448, 449, 450, 451, 452, 453, 454, 455, 456, 457, 458, 459, 460, 461, 462, 463, 464, 465, 466, 467, 468, 469, 470, 471, 472, 473, 474, 475, 476, 477, 478, 479, 480, 481, 482, 483, 484, 485, 486, 487, 488, 489, 490, 491, 492, 493, 494, 495, 496, 497, 498, 499, 500, 501, 502, 503, 504, 505, 506, 507, 508, 509, 510, 511, 512, 513, 514, 515, 516, 517, 518, 519, 520, 521, 522, 523, 524, 525, 526, 527, 528, 529, 530, 531, 532, 533, 534, 535, 536, 537, 538, 539, 540, 541, 542, 543, 544, 545, 546, 547, 548, 549, 550, 551, 552, 553, 554, 555, 556, 557, 558, 559, 560, 561, 562, 563, 564, 565, 566, 567, 568, 569, 570, 571, 572, 573, 574, 575, 576, 577, 578, 579, 580, 581, 582, 583, 584, 585, 586, 587, 588, 589, 590, 591, 592, 593, 594, 595, 596, 597, 598, 599, 600, 601, 602, 603, 604, 605, 606, 607, 608, 609, 610, 611, 612, 613, 614, 615, 616, 617, 618, 619, 620, 621, 622, 623, 624, 625, 626, 627, 628, 629, 630, 631, 632, 633, 634, 635, 636, 637, 638, 639, 640, 641, 642, 643, 644, 645, 646, 647, 648, 649, 650, 651, 652, 653, 654, 655, 656, 657, 658, 659, 660, 661, 662, 663, 664, 665, 666, 667, 668, 669, 670, 671, 672, 673, 674, 675, 676, 677, 678, 679, 680, 681, 682, 683, 684, 685, 686, 687, 688, 689, 690, 691, 692, 693, 694, 695, 696, 697, 698, 699, 700, 701, 702, 703, 704, 705, 706, 707, 708, 709, 710, 711, 712, 713, 714, 715, 716, 717, 718, 719, 720, 721, 722, 723, 724, 725, 726, 727, 728, 729, 730, 731, 732, 733, 734, 735, 736, 737, 738, 739, 740, 741, 742, 743, 744, 745, 746, 747, 748, 749, 750, 751, 752, 753, 754, 755, 756, 757, 758, 759, 760, 761, 762, 763, 764, 765, 766, 767, 768, 769, 770, 771, 772, 773, 774, 775, 776, 777, 778, 779, 780, 781, 782, 783, 784, 785, 786, 787, 788, 789, 790, 791, 792, 793, 794, 795, 796, 797, 798, 799, 800, 801, 802, 803, 804, 805, 806, 807, 808, 809, 810, 811, 812, 813, 814, 815, 816, 817, 818, 819, 820, 821, 822, 823, 824, 825, 826, 827, 828, 829, 830, 831, 832, 833, 834, 835, 836, 837, 838, 839, 840, 841, 842, 843, 844, 845, 846, 847, 848, 849, 850, 851, 852, 853, 854, 855, 856, 857, 858, 859, 860, 861, 862, 863, 864, 865, 866, 867, 868, 869, 870, 871, 872, 873, 874, 875, 876, 877, 878, 879, 880, 881, 882, 883, 884, 885, 886, 887, 888, 889, 890, 891, 892, 893, 894, 895, 896, 897, 898, 899, 900, 901, 902, 903, 904, 905, 906, 907, 908, 909, 910, 911, 912, 913, 914, 915, 916, 917, 918, 919, 920, 921, 922, 923, 924, 925, 926, 927, 928, 929, 930, 931, 932, 933, 934, 935, 936, 937, 938, 939, 940, 941, 942, 943, 944, 945, 946, 947, 948, 949, 950, 951, 952, 953, 954, 955, 956, 957, 958, 959, 960, 961, 962, 963, 964, 965, 966, 967, 968, 969, 970, 971, 972, 973, 974, 975, 976, 977, 978, 979, 980, 981, 982, 983, 984, 985, 986, 987, 988, 989, 990, 991, 992, 993, 994, 995, 996, 997, 998, 999, 1
[Bug 1900679] Re: [snap] chromium spams dmesg
[pid 1278569] sched_setaffinity(1278640, 128, [18, 19, 20, 21, 22, 23] [pid 1278569] <... sched_setaffinity resumed>) = -1 EPERM (Operation not permitted) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900679 Title: [snap] chromium spams dmesg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900679] Re: [snap] chromium spams dmesg
> Can someone who is experiencing this bug run an strace to determine what argument chromium is trying to use with sched_setaffinity ? I'm not sure how its possible to strace a snap container ran under a specific user. Could you provide the command? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900679 Title: [snap] chromium spams dmesg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900679] Re: [snap] chromium spams dmesg
It doesn't break it visibly. I would prefer if it were allowed to set its affinity, but if that can't be done, silencing is a must. This is incredibly spammy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900679 Title: [snap] chromium spams dmesg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900679] Re: [snap] chromium spams dmesg
The rulesets still don't explicitly forbid this syscall and it still gets massively logged into dmesg, making it totally unusable. ``` audit: type=1326 audit(1610482813.754:1835962): auid=1000 uid=1000 gid=1000 ses=4 pid=2201984 comm="chrome" exe="/snap/chromium/1444/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f1190d36c7f code=0x5 ``` Current Chromium snap AppArmor profile needs fixing, this level of logging is not okay. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900679 Title: [snap] chromium spams dmesg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908928] Re: locales 2.27-3ubuntu1.4 enabled random locales
> Are you claiming that Ubuntu somehow uncommented those locales in /etc/locale.gen without your knowledge? Yes, the first thing I do on new installs is only leave the two previously mentioned locales uncommented. Always. I get annoyed waiting for unused locales to be generated. On this specific machine I've seen numerous locale-gen runs and this is the first I saw where these new ones appeared. I will post more information tomorrow, like dpkg.log of the last few days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908928 Title: locales 2.27-3ubuntu1.4 enabled random locales To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1908928/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908928] Re: locales 2.27-3ubuntu1.4 enabled random locales
# grep -vE '^(#|$)' /etc/locale.gen > bg_BG CP1251 > bg_BG.UTF-8 UTF-8 > cs_CZ ISO-8859-2 > cs_CZ.UTF-8 UTF-8 > de_DE ISO-8859-1 > de_DE.UTF-8 UTF-8 > en_US ISO-8859-1 > en_US.UTF-8 UTF-8 > es_ES ISO-8859-1 > es_ES.UTF-8 UTF-8 > et_EE.UTF-8 UTF-8 > fr_FR ISO-8859-1 > fr_FR.UTF-8 UTF-8 > it_IT ISO-8859-1 > it_IT.UTF-8 UTF-8 > ja_JP.UTF-8 UTF-8 > ko_KR.UTF-8 UTF-8 > pl_PL ISO-8859-2 > pl_PL.UTF-8 UTF-8 > pt_PT ISO-8859-1 > pt_PT.UTF-8 UTF-8 > ru_RU ISO-8859-5 > ru_RU.UTF-8 UTF-8 > zh_CN GB2312 > zh_CN.UTF-8 UTF-8 > zh_TW BIG5 > zh_TW.UTF-8 UTF-8 # cat /var/lib/locales/supported.d/* > zsh: no matches found: /var/lib/locales/supported.d/* Keep in mind I had only "en_US.UTF-8" and "et_EE.UTF-8" enabled, suddenly the rest were added. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908928 Title: locales 2.27-3ubuntu1.4 enabled random locales To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1908928/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908928] [NEW] locales 2.27-3ubuntu1.4 enabled random locales
Public bug reported: The installation of locales 2.27-3ubuntu1.4 enabled random locales. This is annoying. apt output: ``` Generating locales (this might take a while)... bg_BG.CP1251... done bg_BG.UTF-8... done cs_CZ.ISO-8859-2... done cs_CZ.UTF-8... done de_DE.ISO-8859-1... done de_DE.UTF-8... done en_US.ISO-8859-1... done en_US.UTF-8... done es_ES.ISO-8859-1... done es_ES.UTF-8... done et_EE.UTF-8... done fr_FR.ISO-8859-1... done fr_FR.UTF-8... done it_IT.ISO-8859-1... done it_IT.UTF-8... done ja_JP.UTF-8... done ko_KR.UTF-8... done pl_PL.ISO-8859-2... done pl_PL.UTF-8... done pt_PT.ISO-8859-1... done pt_PT.UTF-8... done ru_RU.ISO-8859-5... done ru_RU.UTF-8... done zh_CN.GB2312... done zh_CN.UTF-8... done zh_TW.BIG5... done zh_TW.UTF-8... done Generation complete. ``` Most of these locales were NOT previously enabled. ** Affects: langpack-locales (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/1908928 Title: locales 2.27-3ubuntu1.4 enabled random locales To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/langpack-locales/+bug/1908928/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900679] Re: snap chromium spams dmesg
Your rulesets are bad, it's not apparmor's fault. ** Changed in: chromium-browser (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900679 Title: snap chromium spams dmesg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900679] [NEW] snap chromium spams dmesg
Public bug reported: [T okt 20 12:25:09 2020] audit: type=1326 audit(1603185912.099:210734): auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5 [T okt 20 12:25:09 2020] audit: type=1326 audit(1603185912.099:210735): auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5 [T okt 20 12:25:12 2020] audit: type=1326 audit(1603185915.095:210736): auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5 [T okt 20 12:25:12 2020] audit: type=1326 audit(1603185915.095:210737): auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5 [T okt 20 12:25:14 2020] audit: type=1326 audit(1603185917.419:210738): auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5 [T okt 20 12:25:14 2020] audit: type=1326 audit(1603185917.419:210739): auid=1000 uid=1000 gid=1000 ses=3 pid=53766 comm="chrome" exe="/snap/chromium/1350/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f46a3f19b9f code=0x5 Things like these just get repeated endlessly and very often, making any potential debugging very annoying. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Affects: snap (Ubuntu) Importance: Undecided Status: New ** Also affects: chromium (Ubuntu) Importance: Undecided Status: New ** No longer affects: chromium (Ubuntu) ** Also affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900679 Title: snap chromium spams dmesg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location
> Not in your preferred timeline, unfortunately, but we have many more issues and voices to pay attention to. How do you have "many more" voices to pay attention to? 1018 people have marked this issue as it affects them, if anything, you have *many fewer* voices to listen to elsewhere. > waiting for your pet peeve to be fixed may be unsettling and frustrating > We'll stay here, improving things meanwhile. This is exactly the thin-veiled condescension I mentioned earlier. "I'm sorry you chose to feel insulted or blamed by earlier comments by dvnrrs." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575053 Title: Please move the "$HOME/snap" directory to a less obtrusive location To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1575053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location
So are we now shaming people because that they are personally affected by a bug for years, that decided to participate in the community? I suspect the reaction would be a lot milder without all this thinly- veiled condescension constantly thrown at people here. I'm personally appalled. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575053 Title: Please move the "$HOME/snap" directory to a less obtrusive location To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1575053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location
> In addition the ~/snap directory is very explicitly, and non-trivially baked into apparmor profiles that are currently global to the system. And whose fault is that? Should've thought about it sooner. > Lastly .config and .local and .cache are just top-level directories with absolutely no structure inside. And whose fault is that? You're absolutely free to create the structure you want, you've already mangled it, what does it matter now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575053 Title: Please move the "$HOME/snap" directory to a less obtrusive location To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1575053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892093] Re: mem_encrypt=on makes radeon driver crash during startup
Dmesg output of encountering non-working graphics ** Attachment added: "dmesg2" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1892093/+attachment/5402600/+files/dmesg2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892093 Title: mem_encrypt=on makes radeon driver crash during startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1892093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892093] [NEW] mem_encrypt=on makes radeon driver crash during startup
Public bug reported: lspci output: 08:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XTX [Radeon R7 260X/360] [1002:6658] dmesg error output: [drm:cik_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x3010C)=0xCAFEDEAD) radeon :08:00.0: disabling GPU acceleration kernel parameters with issue: quiet splash amd_iommu=on mem_encrypt=on Issue appears on kernels 5.4.0-26-generic 5.4.0-40-generic 5.4.0-42-generic 5.6.0-1021-oem ** Affects: xserver-xorg-video-ati (Ubuntu) Importance: Undecided Status: New ** Package changed: ubuntu => xserver-xorg-video-ati (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892093 Title: mem_encrypt=on makes radeon driver crash during startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1892093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887804] Re: chromium-browser does not follow XDG base directory specification
> Bug reports should stick to fact, using wording like 'Snap-mangled' I'm sorry, that's factually what happened. Should I have worded it Snap- disfigured, Snap-distorted, Snap-impaired or Snap-wrecked instead? > isn't appropriate and not a basis for any discussion. I have **never** had any software on Linux in the past ten years that has caused this many issues because of the stuff it does, how that behaviour is forced on me and which's developers are **this** dismissive and inappropriate. Issues, some major, have been open for years. You should have enough empathy to understand that users don't take that behaviour very kindly for any significant period of time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887804 Title: chromium-browser does not follow XDG base directory specification To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1887804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887804] Re: chromium-browser does not follow XDG base directory specification
Just to be sure you didn't miss a few facts here as you really like to rub it under people's noses: * Snap mangles Chromium's configuration directory * Snap-mangled Chromium configuration directory is not backupable * Snap-mangled Chromium configuration directory is not compliant with the de facto interpretation of XDG-BD specification * Snap-mangled Chromium configuration directory is not compliant with the spirit of the XDG-BD specification * Snap-mangled Chromium configuration directory is unnecessarily not portable between distributions because it assumes the existence of snap I see a common denominator here - snap's mangling that should really not be done. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887804 Title: chromium-browser does not follow XDG base directory specification To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1887804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887804] Re: chromium-browser does not follow XDG base directory specification
> Anything else has little objective value. That's just your opinion. > That's not an assumption, it's a fact: https://snapcraft.io/docs /installing-snapd. It's an assumption, there are a lot of distributions that stay away from snap. > Most (average) users don't care about packaging formats at all (nor do they care where software stores their cache/config, for that matter). That's just your opinion and really not up to you to decide. > That's just your opinion/perception. That's really just your opinion. > I'm marking again this bug as a duplicate of bug #1575053. It's not! The location of the snap directory is totally separate from where chromium's configuration is stored. ** This bug is no longer a duplicate of bug 1575053 Please move the "$HOME/snap" directory to a less obtrusive location -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887804 Title: chromium-browser does not follow XDG base directory specification To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1887804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887804] Re: chromium-browser does not follow XDG base directory specification
> I don't think the specification¹ mandates how folders should be structured under $XDG_DATA_HOME and $XDG_CONFIG_HOME. `$XDG_CONFIG_HOME/$SOFTWARE_NAME` is the de facto way, snap ignores it. Technically, yes, you're absolutely free to use hashes instead of your software's name when you store things in the configuration folder, really doesn't mean it's a good idea. > Hopefully snapd behaves (mostly) the same on all supported distributions, so distro-hopping shouldn't be a concern either. You're making three assumptions. That snap will behave the same across distributions, that snap is supported on different distributions at all, and that someone even wants to install the snap package. All of them are frankly really bad assumptions and just cause people pain. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887804 Title: chromium-browser does not follow XDG base directory specification To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1887804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887804] Re: chromium-browser does not follow XDG base directory specification
> How so? The actual software of which the configuration belongs to is chromium (or "notes"), not snap, snap is "just there" in the middle. Say I want to wipe snap's configuration, I should be able to wipe `$XDG_DATA_HOME/snap` without losing my n+1 snap application's data. Very simply put, `$XDG_DATA_HOME/snap` is for snap, `$XDG_DATA_HOME/chromium` is for chromium. It would be equally silly to have i386 software use ``$XDG_DATA_HOME/i386/software`. Thirdly, it creates a discrepancy in configuration folder location between distributions, which is pointlessly annoying and hinders distro- hopping. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887804 Title: chromium-browser does not follow XDG base directory specification To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1887804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887804] Re: chromium-browser does not follow XDG base directory specification
> Therefore snap packages should base the value of SNAP_USER_DATA on the value of XDG_DATA_HOME (or its specified default). For the "notes" snap, this would be "$HOME/.local/share/snap/notes/1". That's still incorrect. > As to comment #6, can you elaborate on how you copied the existing profile? Literally just did that, copied the folder over. It didn't work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887804 Title: chromium-browser does not follow XDG base directory specification To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1887804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887804] Re: chromium-browser does not follow XDG base directory specification
Oh and I didn't confirm my own bug, that was done by the janitor because someone else felt that this affects them, I just restored the previous status. ** Also affects: chromium-browser 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/1887804 Title: chromium-browser does not follow XDG base directory specification To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1887804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887804] Re: chromium-browser does not follow XDG base directory specification
I also have to repeat that currently, copying over the folder contents you mentioned did NOT result in a working instance of Chromium. All of my extensions broke, databases failed to open, the common folder is just incomplete and needs attention. Please do try it yourself. That absolutely 100% NOT a duplicate of the general snap lunacy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887804 Title: chromium-browser does not follow XDG base directory specification To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1887804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887804] Re: chromium-browser does not follow XDG base directory specification
Upstream bug report that would resolve a half of this issue: https://bugs.chromium.org/p/chromium/issues/detail?id=1106754 Just to summarize what's left broken by this specific Ubuntu package: * Config and cache are not in the folders defined by the base directory specification * Current `common`/configuration folder is incomplete - can't be backed up and restored -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887804 Title: chromium-browser does not follow XDG base directory specification To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1887804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887804] Re: chromium-browser does not follow XDG base directory specification
> You're right, it does contain cache data. That would be an upstream bug, can you please file it at https://bugs.chromium.org/p/chromium/issues/entry ? I will > I just found bug #1575053 which looks very similar to your issue, so I'm going to mark it as duplicate, and I encourage you to read all the comments to understand the rationale. They're not duplicates because that one is about moving ~/snap, this one is making the package actually XDG base directory specification compliant. If Snap does not offer basic mount features, then this is also a bug in snapd. ** This bug is no longer a duplicate of bug 1575053 Please move the "$HOME/snap" directory to a less obtrusive location -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887804 Title: chromium-browser does not follow XDG base directory specification To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1887804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location
> this now seems to be a priority bug which will be fixed fairly soon Indicated by the status "Wishlist"? > Nobody "wants to piss off" anyone, that is silly. Oh it absolutely is. But two years, people have their limits when assuming good faith. > Most of us here are not paying customers, perhaps it would be good that we remember that. Do you think they'll get more paying customers basically ignoring a thousand + 1 people? The community and it's voice matters - ignoring it will just cause people to not support Ubuntu. Support comes in many forms, money is just one of them. Support contracts aren't the only method either, people will take their donations elsewhere, they will influence the companies they work for not to choose Ubuntu. Some people will switch distributions, they will not recommend Ubuntu and might not even help people using Ubuntu. The effect is really not something to simply scoff at. And I can't not mention how it absolutely is not in the spirit of FOSS to exclude people who are less well off. "If you don't pay, don't dare say anything" is such a privileged attitude. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575053 Title: Please move the "$HOME/snap" directory to a less obtrusive location To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1575053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887804] Re: chromium-browser does not follow XDG base directory specification
> The chromium snap is strictly confined, and that means that it cannot read/write to hidden directories inside the user's home folder (such as $HOME/.config or $HOME/.cache). Change the folder it's confined to. > That one is stored in $HOME/chromium/common/.cache/ No, not really. The profile folder contains gigabytes of cache files. > The default profile directory is stored in $HOME/chromium/common/chromium/. No, not really. Copying it over resulted in a utterly broken profile, some vital files are not in the common folder. > Given all this, I'm not really sure what the bug really is about? Can you share concrete use cases? I'm not sure what's unclear, XDG base directory specification is NOT followed, my environment variables are ignored and the wrong folder is used for everything. That has multiple negative effects, as I listed. ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887804 Title: chromium-browser does not follow XDG base directory specification To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1887804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location
The very least make it hidden. It's simply horrible in my neat home folder, there's really no arguing against that. The resistance to fix it baffles me the most. Add a dot to the damn path and make the snapd package install script `mv` the folder if it exists before the upgrade. It's not that hard, you simply want to piss off more than a thousand users. That's not okay. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575053 Title: Please move the "$HOME/snap" directory to a less obtrusive location To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1575053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1616650] Re: snap refresh while command is running may cause issues
This issue is related to it and probably both could be fixed at the same time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1616650 Title: snap refresh while command is running may cause issues To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1616650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1616650] Re: snap refresh while command is running may cause issues
I opened https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1887804 to address the fact that chromium-browser-snap is not following XDG base directory specification and that breaks backing up the snap's configuration and wiping it's cache properly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1616650 Title: snap refresh while command is running may cause issues To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1616650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887804] [NEW] chromium-browser does not follow XDG base directory specification
Public bug reported: Currently Chromium does not follow the XDG base directory specification which means that the cache and configuration folder aren't properly used. This causes the issue that it's nearly impossible to properly migrate or back up Chromium configuration (between computers) and it makes for example mounting cache as tmpfs or wiping it very very difficult. I felt those both immensely when trying to migrate my home folder, gigabytes of cache in ~/snap/chromium/[id]/.config/chromium/[folder] (and ~/snap itself is also not XDG base directory specification compliant, shame!). There's also the issue that the previous configuration that is located properly, isn't migrated by the migrational package. In order to fix this bug, it would require making the snap package follow the XDG base directory specification. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Summary changed: - chromium-browser does not follow xdg base directory specification + chromium-browser does not follow XDG base directory specification ** Description changed: Currently Chromium does not follow the XDG base directory specification which means that the cache and configuration folder aren't properly used. This causes the issue that it's nearly impossible to properly migrate or back up Chromium configuration (between computers) and it makes for example mounting cache as tmpfs or wiping it very very difficult. I felt those both immensely when trying to migrate my home folder, - gigabytes of cache in ~/snap (also not XDG base directory specification + gigabytes of cache in ~/snap/chromium/[id]/.config/chromium/[folder] + (and ~/snap itself is also not XDG base directory specification compliant, shame!). There's also the issue that the previous configuration that is located properly, isn't migrated by the migrational package. In order to fix this bug, it would require making the snap package follow the XDG base directory specification. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887804 Title: chromium-browser does not follow XDG base directory specification To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1887804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857639] Re: DNS server capability detection is broken and has fatal consequences to resolving when DNSSEC is enabled
** Summary changed: - DNS server capability detection is broken and has critical consequences when DNSSEC is enabled + DNS server capability detection is broken and has fatal consequences to resolving when DNSSEC is enabled -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857639 Title: DNS server capability detection is broken and has fatal consequences to resolving when DNSSEC is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1857639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887717] [NEW] mpv falls back to XDG base directory incompliant behaviour
Public bug reported: Due to this commit: https://github.com/mpv- player/mpv/commit/269f0e743e5634691f0c9d5b1b8a4bb68eedbbd0 mpv will fall back on incorrect XDG base directory speficiation incompliant behaviour by default. In order to avoid that, Ubuntu should during installation create the folder ~/$XDG_CONFIG_HOME/mpv and fix that regression. This is more of a request to Ubuntu maintainers to update the installation script because upstream clearly does not wish to collaborate. ** Affects: mpv (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/1887717 Title: mpv falls back to XDG base directory incompliant behaviour To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpv/+bug/1887717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 307152] Re: Get rid of .hplip folder and follow fd.o specifications
Unfortunately this is still a minor problem. It would be nice to not have hplip clutter people's home directories. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/307152 Title: Get rid of .hplip folder and follow fd.o specifications To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/307152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886084] [NEW] certbot service file is incomplete and has bad defaults
Public bug reported: For some reason, the certbot.service hasn't been marked with `After=network.target`, which can cause it to be triggered when there isn't network yet. If people use things `nginx` as their web server and proxy certbot, it also doesn't respect that dependency, it would be a good idea to leave a comment highlighting that. Second issue is that it has `PrivateTmp=true`, it breaks such setups where certbot's webroot is in `/tmp`, this is not a good default. It is a very common setup. Third issue is that the service lacks things like `NoNewPrivileges=yes`, `ProtectHome=yes` and other similar hardening flags, which would be a bit more useful and less likely to interfere with any reasonable setups. This exists on Ubuntu 20.04 LTS and Ubuntu 18.04 LTS. ** Affects: python-certbot (Ubuntu) Importance: Undecided Status: New ** Description changed: For some reason, the certbot.service hasn't been marked with `After=network.target`, which can cause it to be triggered when there isn't network yet. Second issue is that it has `PrivateTmp=true`, it breaks such setups - where certbot's webroot is in `/tmp`, this is not a good default. + where certbot's webroot is in `/tmp`, this is not a good default. It is + a very common setup. Third issue is that instead, the service lacks things like `NoNewPrivileges=yes`, `ProtectHome=yes` and other similar hardening flags, which would be much more useful and less likely to interfere with any reasonable setups. ** Description changed: For some reason, the certbot.service hasn't been marked with `After=network.target`, which can cause it to be triggered when there isn't network yet. Second issue is that it has `PrivateTmp=true`, it breaks such setups where certbot's webroot is in `/tmp`, this is not a good default. It is a very common setup. Third issue is that instead, the service lacks things like `NoNewPrivileges=yes`, `ProtectHome=yes` and other similar hardening flags, which would be much more useful and less likely to interfere with any reasonable setups. + + This exists on Ubuntu 20.04 LTS and Ubuntu 18.04 LTS. ** Description changed: For some reason, the certbot.service hasn't been marked with `After=network.target`, which can cause it to be triggered when there isn't network yet. Second issue is that it has `PrivateTmp=true`, it breaks such setups where certbot's webroot is in `/tmp`, this is not a good default. It is a very common setup. - Third issue is that instead, the service lacks things like - `NoNewPrivileges=yes`, `ProtectHome=yes` and other similar hardening - flags, which would be much more useful and less likely to interfere with - any reasonable setups. + Third issue is that the service lacks things like `NoNewPrivileges=yes`, + `ProtectHome=yes` and other similar hardening flags, which would be a + bit more useful and less likely to interfere with any reasonable setups. This exists on Ubuntu 20.04 LTS and Ubuntu 18.04 LTS. ** Description changed: For some reason, the certbot.service hasn't been marked with `After=network.target`, which can cause it to be triggered when there isn't network yet. + + If people use things `nginx` as their web server and proxy certbot, it + also doesn't respect that dependency, it would be a good idea to leave a + comment highlighting that. Second issue is that it has `PrivateTmp=true`, it breaks such setups where certbot's webroot is in `/tmp`, this is not a good default. It is a very common setup. Third issue is that the service lacks things like `NoNewPrivileges=yes`, `ProtectHome=yes` and other similar hardening flags, which would be a bit more useful and less likely to interfere with any reasonable setups. This exists on Ubuntu 20.04 LTS and Ubuntu 18.04 LTS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886084 Title: certbot service file is incomplete and has bad defaults To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-certbot/+bug/1886084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1616650] Re: snap refresh while command is running may cause issues
This is still an issue. The notification is a nice rub of salt in the wound, but doesn't fix the issue. Absolutely inane, I hope whoever decided to turn chromium-browser gets a kernel panic when they're updating their system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1616650 Title: snap refresh while command is running may cause issues To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1616650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879831] Re: Raspberry Pi 3/4 camera configuration options are missing/undocumented on the generic RPi server image
** Also affects: rpi-packages 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/1879831 Title: Raspberry Pi 3/4 camera configuration options are missing/undocumented on the generic RPi server image To manage notifications about this bug go to: https://bugs.launchpad.net/rpi-packages/+bug/1879831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883398] [NEW] USB serial device passtrough causes qemu to segfault and kill the VM
Public bug reported: What happens: When I pass trough my CH340G (very common USB-TTL serial module) with high-baud data coming in to my Windows 10 VM. qemu segfaults and dirtily shuts down my VM at some random point. The higher the baudrate, the more likely it is to happen. 921600 means the death to my VM in somewhere between 10 seconds and a few minutes. There's no blue screen or anything, it's qemu dying and taking the VM with it. So far I've also determined: * It does not crash as often on lower baudrates. * It does not seem to crash if there's no data coming in. * It does not matter if something is reading the data or not. * It does not matter what software is reading the serial device. What should happen: Qemu shouldn't crash on a device being passed trough. System details: Host - Ubuntu 20.04, qemu-system-common 4.2-3ubuntu6.1 (and everything else as well latest from repository) VM - Windows 10, latest updates installed Diagnostics info: dmesg output: [19511.277076] qemu-system-x86[35900]: segfault at 558c4c00 ip 7fee658ce8a2 sp 7ffc6015f720 error 4 in libc-2.31.so[7fee65856000+178000] [19511.277082] Code: a8 02 75 34 48 8b 15 f5 d4 14 00 64 48 83 3a 00 0f 84 9a 00 00 00 48 8d 3d eb e2 14 00 a8 04 74 0c 48 89 f0 48 25 00 00 00 fc <48> 8b 38 31 d2 48 83 c4 18 e9 10 c1 ff ff 8b 15 fe d9 14 00 85 d2 lsusb output (this is a CH340G module, very very widespread and cheap): Bus 002 Device 018: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC ** Affects: qemu (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/1883398 Title: USB serial device passtrough causes qemu to segfault and kill the VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1883398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879421] Re: package initramfs-tools 0.133ubuntu10 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
** Attachment added: "Dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879421/+attachment/5373805/+files/Dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879421 Title: package initramfs-tools 0.133ubuntu10 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879421] [NEW] package initramfs-tools 0.133ubuntu10 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Public bug reported: Low disk space in /var/tmp mount causes post-installation script to fail. It should probably detect it. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: initramfs-tools 0.133ubuntu10 ProcVersionSignature: Ubuntu 5.3.0-1023.25-raspi2 5.3.18 Uname: Linux 5.3.0-1023-raspi2 aarch64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: arm64 Date: Tue May 19 00:23:34 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.133ubuntu10 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to eoan on 2020-05-19 (0 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package arm64 eoan third-party-packages uec-images ** Attachment removed: "Dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879421/+attachment/5373800/+files/Dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879421 Title: package initramfs-tools 0.133ubuntu10 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879421/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868189] Re: Low memory situations result in root partition being remounted read-only
I'm still encountering this once a month or so. It's really awful. How do I make sure that the kernel **always** has enough memory for buffers and drivers? It is absolutely inane that a chrome tab can ever cause filesystem corruption. ** Also affects: linux Importance: Undecided Status: New ** Project changed: linux => cryptsetup -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868189 Title: Low memory situations result in root partition being remounted read- only To manage notifications about this bug go to: https://bugs.launchpad.net/cryptsetup/+bug/1868189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868189] Re: Low memory situations result in root partition being remounted read-only
Last occurance happened with 5.4.0-29-generic on Ubuntu 20.04 LTS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868189 Title: Low memory situations result in root partition being remounted read- only To manage notifications about this bug go to: https://bugs.launchpad.net/cryptsetup/+bug/1868189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877430] Re: AppArmor policy blocks the usage of PPS devices
Upstream bug: https://gitlab.com/gpsd/gpsd/-/issues/73 Describes how I found a fix for this specific issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877430 Title: AppArmor policy blocks the usage of PPS devices To manage notifications about this bug go to: https://bugs.launchpad.net/gpsd/+bug/1877430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877430] [NEW] AppArmor policy blocks the usage of PPS devices
Public bug reported: Using Ubuntu 20.04 with latest gpsd (and everything else) When one adds a pps device to be used by gpsd then gpsd is denied permission to modify that pps device, that breaks the pps functionality. It is solved by adding capability sys_time to the AppArmor profile. ** Affects: gpsd Importance: Unknown Status: Unknown ** Affects: gpsd (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.com/gpsd/gpsd/-/issues #73 https://gitlab.com/gpsd/gpsd/-/issues/73 ** Also affects: gpsd via https://gitlab.com/gpsd/gpsd/-/issues/73 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/1877430 Title: AppArmor policy blocks the usage of PPS devices To manage notifications about this bug go to: https://bugs.launchpad.net/gpsd/+bug/1877430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876182] [NEW] Running do-release-upgrade displays text two-decades out-of-date
Public bug reported: When one runs `do-release-upgrade` it calculates download speeds based on 56k dial-up modem as one of the examples and there's no estimate for even 10Mbps. It really deserves an update. Example: ``` You have to download a total of 2 704 M. This download will take about 5 hours with a 1Mbit DSL connection and about 4 days 8 hours with a 56k modem. ``` ** Affects: ubuntu-release-upgrader (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/1876182 Title: Running do-release-upgrade displays text two-decades out-of-date To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1876182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1616650] Re: snap refresh while command is running may cause issues
@osomon No, as already said, refresh-app-awareness doesn't work as a solution. I still get unannounced data loss. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1616650 Title: snap refresh while command is running may cause issues To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1616650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870861] Re: chromium-browser is unable to open downloads
> Also please include any additional information, if any, on how to reproduce this problem. To reproduce I just have to download something and try to open it, that's it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870861 Title: chromium-browser is unable to open downloads To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1870861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870861] Re: chromium-browser is unable to open downloads
> The invalid opcode error seems odd, are you running on an uncommon > architecture/cpu? > Could you provide more information about the hardware you're running on such > as the /proc/cpuinfo output? I have a Ryzen 9 3900x, I don't think it's uncommon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870861 Title: chromium-browser is unable to open downloads To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1870861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857639] Re: DNS server capability detection is broken and has critical consequences when DNSSEC is enabled
** Changed in: systemd (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857639 Title: DNS server capability detection is broken and has critical consequences when DNSSEC is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1857639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870861] [NEW] chromium-browser is unable to open downloads
Public bug reported: Current outcome: Clicking a completed download does nothing. Expected outcome: The file opens using the specified file format handler as asked. dmesg log when rapidly clicking on a downloaded file: ``` [ 1297.615318] kauditd_printk_skb: 39 callbacks suppressed [ 1297.615321] audit: type=1326 audit(1586053541.718:5246): auid=1000 uid=1000 gid=1000 ses=3 pid=3886 comm="chrome" exe="/snap/chromium/1071/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f916862ab8f code=0x5 [ 1297.615350] audit: type=1326 audit(1586053541.718:5247): auid=1000 uid=1000 gid=1000 ses=3 pid=3886 comm="chrome" exe="/snap/chromium/1071/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f916862ab8f code=0x5 [ 1297.717954] traps: xdg-open[13136] trap invalid opcode ip:7f40922b6b9c sp:7ffeac92d918 error:0 in ld-2.27.so[7f4092297000+27000] [ 1297.898569] traps: xdg-open[13139] trap invalid opcode ip:7f54bf46eb9c sp:7fff6aa8a5e8 error:0 in ld-2.27.so[7f54bf44f000+27000] [ 1297.983483] audit: type=1326 audit(1586053542.086:5248): auid=1000 uid=1000 gid=1000 ses=3 pid=3886 comm="chrome" exe="/snap/chromium/1071/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f916862ab8f code=0x5 [ 1297.983517] audit: type=1326 audit(1586053542.086:5249): auid=1000 uid=1000 gid=1000 ses=3 pid=3886 comm="chrome" exe="/snap/chromium/1071/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f916862ab8f code=0x5 [ 1298.077793] traps: xdg-open[13142] trap invalid opcode ip:7fbc5ebebb9c sp:7ffd31966ae8 error:0 in ld-2.27.so[7fbc5ebcc000+27000] [ 1298.250473] traps: xdg-open[13145] trap invalid opcode ip:7f5fb989ab9c sp:7ffeda270f18 error:0 in ld-2.27.so[7f5fb987b000+27000] [ 1298.332210] audit: type=1326 audit(1586053542.438:5250): auid=1000 uid=1000 gid=1000 ses=3 pid=3886 comm="chrome" exe="/snap/chromium/1071/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f916862ab8f code=0x5 [ 1298.332230] audit: type=1326 audit(1586053542.438:5251): auid=1000 uid=1000 gid=1000 ses=3 pid=3886 comm="chrome" exe="/snap/chromium/1071/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f916862ab8f code=0x5 [ 1302.681195] kauditd_printk_skb: 32 callbacks suppressed [ 1302.681197] audit: type=1326 audit(1586053546.786:5272): auid=1000 uid=1000 gid=1000 ses=3 pid=3886 comm="chrome" exe="/snap/chromium/1071/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f916862ab8f code=0x5 [ 1302.681257] audit: type=1326 audit(1586053546.786:5273): auid=1000 uid=1000 gid=1000 ses=3 pid=3886 comm="chrome" exe="/snap/chromium/1071/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f916862ab8f code=0x5 [ 1302.880296] audit: type=1326 audit(1586053546.986:5274): auid=1000 uid=1000 gid=1000 ses=3 pid=3886 comm="chrome" exe="/snap/chromium/1071/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f916862ab8f code=0x5 [ 1302.880368] audit: type=1326 audit(1586053546.986:5275): auid=1000 uid=1000 gid=1000 ses=3 pid=3886 comm="chrome" exe="/snap/chromium/1071/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f916862ab8f code=0x5 [ 1303.114233] audit: type=1326 audit(1586053547.218:5276): auid=1000 uid=1000 gid=1000 ses=3 pid=3886 comm="chrome" exe="/snap/chromium/1071/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f916862ab8f code=0x5 [ 1303.114317] audit: type=1326 audit(1586053547.218:5277): auid=1000 uid=1000 gid=1000 ses=3 pid=3886 comm="chrome" exe="/snap/chromium/1071/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f916862ab8f code=0x5 [ 1303.297741] audit: type=1326 audit(1586053547.402:5278): auid=1000 uid=1000 gid=1000 ses=3 pid=3886 comm="chrome" exe="/snap/chromium/1071/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f916862ab8f code=0x5 [ 1303.297814] audit: type=1326 audit(1586053547.402:5279): auid=1000 uid=1000 gid=1000 ses=3 pid=3886 comm="chrome" exe="/snap/chromium/1071/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f916862ab8f code=0x5 [ 1303.615901] audit: type=1326 audit(1586053547.718:5280): auid=1000 uid=1000 gid=1000 ses=3 pid=3886 comm="chrome" exe="/snap/chromium/1071/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f916862ab8f code=0x5 [ 1303.615933] audit: type=1326 audit(1586053547.722:5281): auid=1000 uid=1000 gid=1000 ses=3 pid=3886 comm="chrome" exe="/snap/chromium/1071/usr/lib/chromium-browser/chrome" sig=0 arch=c03e syscall=203 compat=0 ip=0x7f916862ab8f code=0x5 [ 1307.777161] kauditd_printk_skb: 29 callbacks suppressed [ 1307.777163] audit: type=1326 audit(1586053551.882:5304): au
[Bug 1868189] Re: Low memory situations result in root partition being remounted read-only
** Description changed: Instead of killing something with a high niceness low memory situations seem to hang something super-ultra-so-very vital, writes fail and the root partition is remounted read-only. After that systemd-journald starts stupidly spamming and earlier logs are rendered unusable. I'd post more logs but https://github.com/systemd/systemd/issues/2339 hasn't been fixed in years. This has happened at least four times, across many kernel versions. With Ubuntu 18.10, 19.04 and 19.10. - ``` [827788.409138] sd 5:0:0:0: [sdb] tag#12 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409141] sd 5:0:0:0: [sdb] tag#12 CDB: Write(10) 2a 00 01 e0 b8 f0 00 00 10 00 [827788.409143] blk_update_request: I/O error, dev sdb, sector 31504624 op 0x1:(WRITE) flags 0x0 phys_seg 2 prio class 0 [827788.409151] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871518) [827788.409154] Buffer I/O error on device dm-1, logical block 3871518 [827788.409163] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871519) [827788.409164] Buffer I/O error on device dm-1, logical block 3871519 [827788.409172] sd 5:0:0:0: [sdb] tag#11 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409174] sd 5:0:0:0: [sdb] tag#11 CDB: Write(10) 2a 00 01 e0 bb 70 00 00 08 00 [827788.409175] blk_update_request: I/O error, dev sdb, sector 31505264 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 [827788.409179] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871598) [827788.409180] Buffer I/O error on device dm-1, logical block 3871598 [827788.409188] sd 5:0:0:0: [sdb] tag#10 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409189] sd 5:0:0:0: [sdb] tag#10 CDB: Write(10) 2a 00 01 e0 ba 60 00 00 38 00 [827788.409190] blk_update_request: I/O error, dev sdb, sector 31504992 op 0x1:(WRITE) flags 0x0 phys_seg 7 prio class 0 [827788.409194] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871564) [827788.409195] Buffer I/O error on device dm-1, logical block 3871564 [827788.409196] Buffer I/O error on device dm-1, logical block 3871565 [827788.409198] Buffer I/O error on device dm-1, logical block 3871566 [827788.409199] Buffer I/O error on device dm-1, logical block 3871567 [827788.409201] Buffer I/O error on device dm-1, logical block 3871568 [827788.409202] Buffer I/O error on device dm-1, logical block 3871569 [827788.409203] Buffer I/O error on device dm-1, logical block 3871570 [827788.409210] sd 5:0:0:0: [sdb] tag#9 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409211] sd 5:0:0:0: [sdb] tag#9 CDB: Write(10) 2a 00 01 e0 ba 30 00 00 08 00 [827788.409212] blk_update_request: I/O error, dev sdb, sector 31504944 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 [827788.409216] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871558) [827788.409220] sd 5:0:0:0: [sdb] tag#8 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409221] sd 5:0:0:0: [sdb] tag#8 CDB: Write(10) 2a 00 01 e0 ba 50 00 00 08 00 [827788.409222] blk_update_request: I/O error, dev sdb, sector 31504976 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 [827788.409225] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871562) [827788.409228] sd 5:0:0:0: [sdb] tag#4 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409229] sd 5:0:0:0: [sdb] tag#4 CDB: Write(10) 2a 00 01 e0 bb 88 00 00 08 00 [827788.409230] blk_update_request: I/O error, dev sdb, sector 31505288 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 [827788.409233] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871601) [827818.628273] sd 5:0:0:0: [sdb] tag#31 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827818.628276] sd 5:0:0:0: [sdb] tag#31 CDB: Write(10) 2a 00 01 cf 12 38 00 00 30 00 [827818.628279] blk_update_request: I/O error, dev sdb, sector 30347832 op 0x1:(WRITE) flags 0x800 phys_seg 6 prio class 0 [827818.628347] sd 5:0:0:0: [sdb] tag#28 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827818.628351] sd 5:0:0:0: [sdb] tag#28 CDB: Write(10) 2a 00 01 93 2f b0 00 00 08 00 [827818.628353] blk_update_request: I/O error, dev sdb, sector 26423216 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 [827818.628358] Aborting journal on device dm-1-8. [827818.628374] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 323634
[Bug 1616650] Re: snap refresh while command is running may cause issues
Enabled the "refresh-app-awareness", still, without warning Chromium suddenly stops recording history, keeping state and sessions. Incredibly annoying and causes unavoidable data loss. It's is frankly inane to roll out new snaps when it has been known for FOUR. YEARS. that there's a major bug that causes data loss. ** Also affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1616650 Title: snap refresh while command is running may cause issues To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1616650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector
** Also affects: kdeconnect (Ubuntu) Importance: Undecided Status: New ** Also affects: goopg (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/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1741074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543767] Re: ssh logins doesn't show the MOTD when connecting with public key authorisation
** Changed in: server-papercuts Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/543767 Title: ssh logins doesn't show the MOTD when connecting with public key authorisation To manage notifications about this bug go to: https://bugs.launchpad.net/server-papercuts/+bug/543767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870829] [NEW] AptX and AptX HD unavailable as Bluetooth audio quality options
Public bug reported: Current situation: When one connects a Bluetooth audio device, at best one can choose between "Headset Head Unit (HSP/HFP)" and "High Fidelity Playback (A2DP Sink)". That is sad when the audio device supports AptX or AptX HD. Expected situation: One can select AptX or AptX HD as the Bluetooth audio output profile. ** Affects: pulseaudio (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/1870829 Title: AptX and AptX HD unavailable as Bluetooth audio quality options To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868189] Re: Low memory situations result in root partition being remounted read-only
I can't run this command because permanent logging stops and temporary logging is flooded by systemd. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868189 Title: Low memory situations result in root partition being remounted read- only To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868189] Re: Low memory situations result in root partition being remounted read-only
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868189 Title: Low memory situations result in root partition being remounted read- only To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868189] [NEW] Low memory situations result in root partition being remounted read-only
Public bug reported: Instead of killing something with a high niceness low memory situations seem to hang something super-ultra-so-very vital, writes fail and the root partition is remounted read-only. After that systemd-journald starts stupidly spamming and earlier logs are rendered unusable. I'd post more logs but https://github.com/systemd/systemd/issues/2339 hasn't been fixed in years. This has happened at least four times, across many kernel versions. With Ubuntu 18.10, 19.04 and 19.10. ``` [827788.409138] sd 5:0:0:0: [sdb] tag#12 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409141] sd 5:0:0:0: [sdb] tag#12 CDB: Write(10) 2a 00 01 e0 b8 f0 00 00 10 00 [827788.409143] blk_update_request: I/O error, dev sdb, sector 31504624 op 0x1:(WRITE) flags 0x0 phys_seg 2 prio class 0 [827788.409151] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871518) [827788.409154] Buffer I/O error on device dm-1, logical block 3871518 [827788.409163] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871519) [827788.409164] Buffer I/O error on device dm-1, logical block 3871519 [827788.409172] sd 5:0:0:0: [sdb] tag#11 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409174] sd 5:0:0:0: [sdb] tag#11 CDB: Write(10) 2a 00 01 e0 bb 70 00 00 08 00 [827788.409175] blk_update_request: I/O error, dev sdb, sector 31505264 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 [827788.409179] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871598) [827788.409180] Buffer I/O error on device dm-1, logical block 3871598 [827788.409188] sd 5:0:0:0: [sdb] tag#10 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409189] sd 5:0:0:0: [sdb] tag#10 CDB: Write(10) 2a 00 01 e0 ba 60 00 00 38 00 [827788.409190] blk_update_request: I/O error, dev sdb, sector 31504992 op 0x1:(WRITE) flags 0x0 phys_seg 7 prio class 0 [827788.409194] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871564) [827788.409195] Buffer I/O error on device dm-1, logical block 3871564 [827788.409196] Buffer I/O error on device dm-1, logical block 3871565 [827788.409198] Buffer I/O error on device dm-1, logical block 3871566 [827788.409199] Buffer I/O error on device dm-1, logical block 3871567 [827788.409201] Buffer I/O error on device dm-1, logical block 3871568 [827788.409202] Buffer I/O error on device dm-1, logical block 3871569 [827788.409203] Buffer I/O error on device dm-1, logical block 3871570 [827788.409210] sd 5:0:0:0: [sdb] tag#9 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409211] sd 5:0:0:0: [sdb] tag#9 CDB: Write(10) 2a 00 01 e0 ba 30 00 00 08 00 [827788.409212] blk_update_request: I/O error, dev sdb, sector 31504944 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 [827788.409216] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871558) [827788.409220] sd 5:0:0:0: [sdb] tag#8 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409221] sd 5:0:0:0: [sdb] tag#8 CDB: Write(10) 2a 00 01 e0 ba 50 00 00 08 00 [827788.409222] blk_update_request: I/O error, dev sdb, sector 31504976 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 [827788.409225] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871562) [827788.409228] sd 5:0:0:0: [sdb] tag#4 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827788.409229] sd 5:0:0:0: [sdb] tag#4 CDB: Write(10) 2a 00 01 e0 bb 88 00 00 08 00 [827788.409230] blk_update_request: I/O error, dev sdb, sector 31505288 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 [827788.409233] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3871601) [827818.628273] sd 5:0:0:0: [sdb] tag#31 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827818.628276] sd 5:0:0:0: [sdb] tag#31 CDB: Write(10) 2a 00 01 cf 12 38 00 00 30 00 [827818.628279] blk_update_request: I/O error, dev sdb, sector 30347832 op 0x1:(WRITE) flags 0x800 phys_seg 6 prio class 0 [827818.628347] sd 5:0:0:0: [sdb] tag#28 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [827818.628351] sd 5:0:0:0: [sdb] tag#28 CDB: Write(10) 2a 00 01 93 2f b0 00 00 08 00 [827818.628353] blk_update_request: I/O error, dev sdb, sector 26423216 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 [827818.628358] Aborting journal on device dm-1-8. [827818.628374] EXT4-fs warning (device dm-1): ext4_end_bio:309: I/O error 10 writing to inode 1577543 (offset 0 size 0 starting block 3236342) [827818.628379] buffer_io_error: 3 callbacks suppressed [827818.628381] Buffer I/O error on device dm-1, logical
[Bug 1856539] Re: wireguard package doesn't work on ubuntu eon
This is what I see in `/var/crash/wireguard-dkms.0.crash`: ``` ProblemType: Package DKMSBuildLog: DKMS make.log for wireguard-0.0.20190913 for kernel 5.3.0-1018-raspi2 (aarch64) Tue Feb 18 20:52:38 UTC 2020 make: Entering directory '/usr/src/linux-headers-5.3.0-1018-raspi2' CC [M] /var/lib/dkms/wireguard/0.0.20190913/build/main.o CC [M] /var/lib/dkms/wireguard/0.0.20190913/build/noise.o CC [M] /var/lib/dkms/wireguard/0.0.20190913/build/device.o CC [M] /var/lib/dkms/wireguard/0.0.20190913/build/peer.o CC [M] /var/lib/dkms/wireguard/0.0.20190913/build/timers.o CC [M] /var/lib/dkms/wireguard/0.0.20190913/build/queueing.o CC [M] /var/lib/dkms/wireguard/0.0.20190913/build/send.o CC [M] /var/lib/dkms/wireguard/0.0.20190913/build/receive.o CC [M] /var/lib/dkms/wireguard/0.0.20190913/build/socket.o CC [M] /var/lib/dkms/wireguard/0.0.20190913/build/peerlookup.o CC [M] /var/lib/dkms/wireguard/0.0.20190913/build/allowedips.o CC [M] /var/lib/dkms/wireguard/0.0.20190913/build/ratelimiter.o /var/lib/dkms/wireguard/0.0.20190913/build/socket.c: In function ‘send6’: /var/lib/dkms/wireguard/0.0.20190913/build/socket.c:145:20: error: ‘const struct ipv6_stub’ has no member named ‘ipv6_dst_lookup’; did you mean ‘ipv6_dst_lookup_flow’? 145 | ret = ipv6_stub->ipv6_dst_lookup(sock_net(sock), sock, &dst, |^~~ |ipv6_dst_lookup_flow make[1]: *** [scripts/Makefile.build:290: /var/lib/dkms/wireguard/0.0.20190913/build/socket.o] Error 1 make[1]: *** Waiting for unfinished jobs make: *** [Makefile:1658: _module_/var/lib/dkms/wireguard/0.0.20190913/build] Error 2 make: Leaving directory '/usr/src/linux-headers-5.3.0-1018-raspi2' DKMSKernelVersion: 5.3.0-1018-raspi2 Date: Tue Feb 18 20:52:52 2020 DuplicateSignature: dkms:wireguard-dkms:0.0.20190913-1ubuntu1:/var/lib/dkms/wireguard/0.0.20190913/build/socket.c:145:20: error: ‘const struct ipv6_stub’ has no member named ‘ipv6_dst_lookup’; did you mean ‘ipv6_dst_lookup_flow’? Package: wireguard-dkms 0.0.20190913-1ubuntu1 PackageVersion: 0.0.20190913-1ubuntu1 SourcePackage: wireguard Title: wireguard-dkms 0.0.20190913-1ubuntu1: wireguard kernel module failed to build ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856539 Title: wireguard package doesn't work on ubuntu eon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856539] Re: wireguard package doesn't work on ubuntu eon
This issue is marked as a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858807 so I'm commenting here. Unlink and move comments if they're not actually duplicates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856539 Title: wireguard package doesn't work on ubuntu eon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856539] Re: wireguard package doesn't work on ubuntu eon
Mine says `wireguard, 0.0.20190913: added`, but updating failed and I suspect it's going to stop working after a reboot. I'd upload logs with apport but it doesn't let me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856539 Title: wireguard package doesn't work on ubuntu eon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858807] Re: Wireguard install fails on 19.10
*** This bug is a duplicate of bug 1856539 *** https://bugs.launchpad.net/bugs/1856539 I just encountered this too -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858807 Title: Wireguard install fails on 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858807/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860137] Re: Chromium-browser Snap is amnesiac
I enabled the flag, still encountered this issue. This time when I restarted Chromium my tabs were lost and restoring previous session just did nothing. Thankfully the extension "Tab Suspender" allowed me to recover my tabs but a few services logged me off. I guess the flag improves situation, thanks for that, but isn't flawless. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860137 Title: Chromium-browser Snap is amnesiac To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1860137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector
KDE Connect is also affected by this. I'm wondering though, unable to find the answer online, why was the transition to snap-based chromium made? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1741074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860137] Re: Chromium-browser Snap is amnesiac
I enabled the flag, will report back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860137 Title: Chromium-browser Snap is amnesiac To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1860137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833793] Re: Updating to 19.04 audio keeps clicking when nothing is playing audio
@rphair Please try the package @hui.wang posted and upload the asked alsa- info.txt, that way it can be possibly fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833793 Title: Updating to 19.04 audio keeps clicking when nothing is playing audio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860137] [NEW] Chromium-browser Snap is amnesiac
Public bug reported: I'm using Ubuntu 19.10, latest Chromium(-browser) installed. The issue is that after the switch to snap-based Chromium it started forgetting my logged in sessions very very often. This is not isolated to one online service, I have to log back in to everything I use, including Chromium itself. It also forgets any "Remember this device" checkmarks. History, downloads or extensions however do not suffer from any data loss. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860137 Title: Chromium-browser Snap is amnesiac To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1860137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833880] Re: KDE freezes randomly
** Changed in: kinit (Ubuntu) Status: New => Fix Released ** No longer affects: kinit (Ubuntu) ** No longer affects: xorg-server -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1833880 Title: KDE freezes randomly To manage notifications about this bug go to: https://bugs.launchpad.net/xf86-video-amd/+bug/1833880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857639] Re: DNS server capability detection is broken and has critical consequences when DNSSEC is enabled
``` systemd[1]: Starting Network Name Resolution... systemd-resolved[1392]: Positive Trust Anchors: systemd-resolved[1392]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5 systemd-resolved[1392]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d systemd-resolved[1392]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 2 systemd-resolved[1392]: Using system hostname 'machine'. systemd[1]: Started Network Name Resolution. systemd-resolved[1392]: DNSSEC validation failed for question 0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN DS: no-signature systemd-resolved[1392]: DNSSEC validation failed for question 0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN SOA: no-signature systemd-resolved[1392]: DNSSEC validation failed for question 2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN DS: no-signature systemd-resolved[1392]: DNSSEC validation failed for question 2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN SOA: no-signature systemd-resolved[1392]: DNSSEC validation failed for question 2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN DS: no-signature systemd-resolved[1392]: DNSSEC validation failed for question 2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN SOA: no-signature systemd-resolved[1392]: DNSSEC validation failed for question 3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN DS: no-signature systemd-resolved[1392]: DNSSEC validation failed for question 3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN SOA: no-signature systemd-resolved[1392]: DNSSEC validation failed for question c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN DS: no-signature systemd-resolved[1392]: DNSSEC validation failed for question c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN SOA: no-signature systemd-resolved[1392]: DNSSEC validation failed for question c.c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN DS: no-signature systemd-resolved[1392]: DNSSEC validation failed for question c.c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN SOA: no-signature systemd-resolved[1392]: DNSSEC validation failed for question 9.c.c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN DS: no-signature systemd-resolved[1392]: DNSSEC validation failed for question 9.c.c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN SOA: no-signature systemd-resolved[1392]: DNSSEC validation failed for question b.9.c.c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN DS: no-signature systemd-resolved[1392]: DNSSEC validation failed for question b.9.c.c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN SOA: no-signature systemd-resolved[1392]: DNSSEC validation failed for question 1.b.9.c.c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN DS: no-signature systemd-resolved[1392]: DNSSEC validation failed for question 1.b.9.c.c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN SOA: no-signature systemd-resolved[1392]: DNSSEC validation failed for question d.1.b.9.c.c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN DS: no-signature systemd-resolved[1392]: DNSSEC validation failed for question d.1.b.9.c.c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN SOA: no-signature systemd-resolved[1392]: DNSSEC validation failed for question f.d.1.b.9.c.c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN DS: no-signature systemd-resolved[1392]: DNSSEC validation failed for question f.d.1.b.9.c.c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN SOA: no-signature systemd-resolved[1392]: DNSSEC validation failed for question 0.f.d.1.b.9.c.c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN DS: no-signature systemd-resolved[1392]: DNSSEC validation failed for question 0.f.d.1.b.9.c.c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN SOA: no-signature systemd-resolved[1392]: DNSSEC validation failed for question 4.0.f.d.1.b.9.c.c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN DS: no-signature systemd-resolved[1392]: DNSSEC validation failed for question 4.0.f.d.1.b.9.c.c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN SOA: no-signature systemd-resolved[1392]: DNSSEC validation failed for question f.4.0.f.d.1.b.9.c.c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN DS: no-signature systemd-resolved[1392]: DNSSEC validation failed for question f.4.0.f.d.1.b.9.c.c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN SOA: no-signature systemd-resolved[1392]: DNSSEC validation failed for question f.4.0.f.d.1.b.9.c.c.3.2.2.0.a.c.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa IN PTR: no-signature systemd-resolved[1392]: Using degraded feature set (UDP+EDNS0+DO) for DNS server 8.8.8.8. systemd-resolved[1392]: Using degraded feature set (
[Bug 1857639] Re: DNS server capability detection is broken and has critical consequences when DNSSEC is enabled
I will need to wait for the bug to trigger again, logs have rotated since the last time I had `yes` in the config. Also, those "single line"s are actually what I did see repeatedly until I had to stop and reconfigure resolved because it made internet usage impossible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857639 Title: DNS server capability detection is broken and has critical consequences when DNSSEC is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1857639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857639] Re: DNS server capability detection is broken and has critical consequences when DNSSEC is enabled
> HOW do you have DNSSEC configured. Not a yes/no question. Actually it's exactly a "yes" in the 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/1857639 Title: DNS server capability detection is broken and has critical consequences when DNSSEC is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1857639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
