[Bug 1969607] [NEW] Schwerer Fehler bei unbuntu installation
Public bug reported: The report has be sent ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.17 ProcVersionSignature: Ubuntu 5.4.0-84.94~18.04.1-generic 5.4.133 Uname: Linux 5.4.0-84-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.26 Architecture: amd64 CasperVersion: 1.394.3 Date: Wed Apr 20 12:14:28 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash --- LiveMediaBuild: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.17 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969607 Title: Schwerer Fehler bei unbuntu installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1969607/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969603] [NEW] Installation von Ubuntu mit schwerem Fehler abgebrocchen
Public bug reported: I have sent the report ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.17 ProcVersionSignature: Ubuntu 5.4.0-84.94~18.04.1-generic 5.4.133 Uname: Linux 5.4.0-84-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.26 Architecture: amd64 CasperVersion: 1.394.3 Date: Wed Apr 20 11:05:22 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash --- LiveMediaBuild: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.17 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969603 Title: Installation von Ubuntu mit schwerem Fehler abgebrocchen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1969603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958718] [NEW] Crash on wake with kernel version 5.13
Public bug reported: With "linux-image-5.13.0-27-generic" on Ubuntu 20.04.3 LTS, my notebook (Thinkpad T14) crashes when waking up after being suspended. The screen displays what I would describe as "colourful snow" with some vertical stripes on the right edge of the display. The only thing I can do is power off the machine by holding the power button for several seconds and then restart. With "linux-image-5.11.0-46-generic", this does not happen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 22 16:05:18 2022 InstallationDate: Installed on 2020-12-28 (389 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.13 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958718 Title: Crash on wake with kernel version 5.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908931] Re: Kubuntu 20.04 System Settings Online Accounts - unable to add Google account
yeah, if fact it is not a gnome-control-center bug, but a problem with libWebKit2gtk-4.0 under Wayland. This affects both, Kubuntu as well as stock Ubuntu (also in 21.04, which I use). ** No longer affects: gnome-control-center (Ubuntu) ** Also affects: webkit2gtk (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/1908931 Title: Kubuntu 20.04 System Settings Online Accounts - unable to add Google account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemsettings/+bug/1908931/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908931] Re: Kubuntu 20.04 System Settings Online Accounts - unable to add Google account
** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908931 Title: Kubuntu 20.04 System Settings Online Accounts - unable to add Google account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1908931/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908931] Re: Kubuntu 20.04 System Settings Online Accounts - unable to add Google account
I have encountered the same problem while using Cisco AnyConnect. Found out that it is libwebkit2gtk related. It seems it can't cope with wayland. Does it work if you launch with # WAYLAND_DISPLAY=no gnome-control-center ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908931 Title: Kubuntu 20.04 System Settings Online Accounts - unable to add Google account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemsettings/+bug/1908931/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396379] Re: installer uses first EFI system partition found even when directed otherwise
Thanks to all you guys for the description of the problem and the suggested fix by changing the boot flag of the preexisting efi partition. I spent quite some timee trying to fix this, since I thought i might have done something wrong. If I understand the problem correctly, Ubuntu has a bug for mor than 6 years, which breaks the system when a user wants two efi partitions to use dual boot with Windows. This would be the only installation method that would not be hampered with interferences by windows updates. And it is a problem which does not occur with Debian, on which ubuntu is based on. This raises the question for me if repairing the ubuntu installation is the right choice for me. I just want an easy to use system without too much digging. I really have to think about whether I want to apply this workaround. It also makes me a little less furious that Microsoft decided to just revert any changes on *their* efi partition during updates, when they notice tempering from other OS, since *other* OS might be a little bit careless by risking harm not only for their own installation but also for Windows. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396379 Title: installer uses first EFI system partition found even when directed otherwise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1396379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925800] Re: Many failures on Kubutu 20.10
Sorry, I'm no longer on Kubuntu and no longer using Firejail. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925800 Title: Many failures on Kubutu 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firejail/+bug/1925800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925800] [NEW] Many failures on Kubutu 20.10
Public bug reported: Sorry that this will be light on detail. Consider it something of a "quick glance" at the current state of Firejail from a normal user's POV. I gave Firejail a try on my Kubuntu 20.10 system, by running "sudo firecfg" and then rebooting, and mostly it was a disaster: - Dolphin couldn't run shell scripts that contained sudo. - Firefox wouldn't launch, then then it would, then it wouldn't again. Looked at errors on CLI, it seemed to be network or dbus problems. Tried making my own .local file to fix those, every single line (except comments) got rejected for various reasons. - VSCode launched once, then it wouldn't. - Liferea was able to send links to Firefox (once I made Firefox non- Firejailed), but always opened a new instance of Firefox, didn't use the existing instance. These are similar to some issues I've seen with some Flatpaks and Snaps. So I concluded (fairly or not) that Firejail is not usable for me. "sudo firecfg --clean". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: firejail 0.9.62.4-3 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Apr 23 15:26:25 2021 InstallationDate: Installed on 2021-02-03 (79 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: firejail UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: firejail (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925800 Title: Many failures on Kubutu 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firejail/+bug/1925800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921640] [NEW] Profile file should include app version number(s)
Public bug reported: Each profile file in /etc/firejail should contain a line saying what version(s) of the app it applies to. And maybe a warning should be logged if there is a version mismatch. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: firejail 0.9.62.4-3 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun Mar 28 20:32:30 2021 InstallationDate: Installed on 2021-02-03 (53 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: firejail UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: firejail (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921640 Title: Profile file should include app version number(s) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firejail/+bug/1921640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921641] [NEW] Man page should say Docker not supported
Public bug reported: Man page says Snap and Flatpak not supported; I think it also should say that Docker is not supported, right ? ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: firejail 0.9.62.4-3 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun Mar 28 20:37:06 2021 InstallationDate: Installed on 2021-02-03 (53 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: firejail UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: firejail (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921641 Title: Man page should say Docker not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firejail/+bug/1921641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914816] Re: ufw not logging if it decides to stop all traffic ? Confused
Okay, thanks, check-requirements gives: WARN: detected other firewall applications: firewalld (if enabled, these applications may interfere with ufw) Is there some way this check could be done in more places, and a warning given to the user in each place ? The ufw and gufw GUI applications should do that each time they are launched. It would be great to have this warning in the system log, too. Maybe even the install scripts for ufw and gufw should check too. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914816 Title: ufw not logging if it decides to stop all traffic ? Confused To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1914816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914606] Re: Wiping .cache makes gufw fail, cuts network access ?
What I am seeing seems to be a state change that happens at boot time, so I can't capture it in gufw cli. I have filed https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1914816 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914606 Title: Wiping .cache makes gufw fail, cuts network access ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gui-ufw/+bug/1914606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914816] [NEW] ufw not logging if it decides to stop all traffic ? Confused
Public bug reported: Sorry, this is going to be a very bad report. Here's what I did: - installed gufw and enabled it, no rules, just default incoming=deny outgoing=accept - rebooted - Ethernet says it connected - no network access; ping 1.1.1.1 fails - launch gufw, and it says it's disabled (the whole firewall) - I think eventually I figured out that iptables had been emptied and INPUT chain set to DROP After many travails, I captured a piece of dmesg output as the system was booting, and I think it shows ufw trying to check IPv6 status and deciding to stop everything. At least logging (which was set to full in gufw) suddenly stops. In network manager, I've tried to say "ignore IPv6". I'm not sure if this trouble is related to fiddling with the "only work if IPv4 is enabled" check-box, which seems to have a ToolTip that is exactly backwards. My ISP does not give IPv6 service. I've tried many settings of the IPv6 drop-down in System Settings / Network GUI, setting and clearing the IPv4 and IPv6 required check-boxes, etc. So, I'm totally confused, but I think the log shows that logging suddenly stops (from full to zero), which must mean ufw detected some condition that made it empty out the iptables and set everything to DROP ? If so, ufw should have logged a message saying it was doing so, and I don't see such a message. So, if I'm right, at least this is a feature request that ufw should log a message when it decides to stop all IPv4 or IPv6 traffic and/or stop logging and/or wipe out all rules. Sorry about the mess of a report. I'm using Kubuntu 20.10, gufw 20.10.0-0ubuntu1, ufw 0.36-7 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ufw (not installed) ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Feb 5 20:35:18 2021 InstallationDate: Installed on 2021-02-03 (2 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: ufw UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ufw (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ** Attachment added: "dmesg1.txt" https://bugs.launchpad.net/bugs/1914816/+attachment/5460643/+files/dmesg1.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914816 Title: ufw not logging if it decides to stop all traffic ? Confused To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1914816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914606] Re: Wiping .cache makes gufw fail, cuts network access ?
I guess I can't close this issue myself, so please close it for me. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914606 Title: Wiping .cache makes gufw fail, cuts network access ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gui-ufw/+bug/1914606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914606] Re: Wiping .cache makes gufw fail, cuts network access ?
Okay, now I'm convinced my problems have nothing to do with ~/.cache, so I'm closing this issue. But I'm still having gufw show "disabled" after a reboot. When it happens, is that just reacting to some change that ufw made to the iptables ? Such as setting the INPUT chain to empty ? I think I've found an issue I'm going to file against ufw. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914606 Title: Wiping .cache makes gufw fail, cuts network access ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gui-ufw/+bug/1914606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914606] Re: Wiping .cache makes gufw fail, cuts network access ?
Maybe ufw stores something important in ~/.cache ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914606 Title: Wiping .cache makes gufw fail, cuts network access ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gui-ufw/+bug/1914606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914606] Re: Wiping .cache makes gufw fail, cuts network access ?
Could it be something used by gufw ? Firewalld or iptables or something ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914606 Title: Wiping .cache makes gufw fail, cuts network access ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gui-ufw/+bug/1914606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914606] [NEW] Wiping .cache makes gufw fail, cuts network access ?
Public bug reported: I added a line to /etc/fstab to put my ~/.cache on a tmpfs: tmpfs /home/user1/.cache tmpfs nodev,nosuid,mode=1777,size=1G,defaults 0 0 or: tmpfs /home/user1/.cache tmpfs noatime,nodiratime,nodev,nosuid,mode=1777,size=1G,defaults 0 0 [I tried a couple of versions, and rebooted a number of times, not sure of the exact configuration, sorry.] After reboot, the system had no network access. "ping 1.1.1.1" or similar failed. I am using wired Ethernet. Tried various fixes. I eventually fixed the problem by uninstalling gufw. I'm not 100% positive gufw was the problem. But now (with first form of fstab line) everything works. Is gufw storing something in ~/.cache that it shouldn't be ? I should be able to wipe ~/.cache and reboot and have everything work, correct ? I had no rules set in gufw, just enabled and Incoming=Deny. System worked okay with gufw before I added that fstab line and rebooted. I'm on Kubuntu 20.10, kernel 5.8.0-41-generic, gufw 20.10.0-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gufw (not installed) ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Feb 4 14:07:32 2021 InstallationDate: Installed on 2021-02-03 (1 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: gui-ufw UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gui-ufw (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914606 Title: Wiping .cache makes gufw fail, cuts network access ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gui-ufw/+bug/1914606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900983] Re: Multiple heap buffer overflows caused by int overflow
** Description changed: The CImg library uses an unsafe pattern to calculate memory allocations size. At least in the PNM file format parser, an attacker can trivially supply width/height fields that overflow the heap and result in arbitrary heap writes. This probably also affects other file format parsers in CImg. The most prominent user of CImg is gmic. The gmic commandline tool directly exposes the load_pnm() functions (and also the other file format load functions) to the user and thus is affected. The issue is public and fixed in: https://github.com/dtschump/CImg/pull/295 Redhat bug: https://bugzilla.redhat.com/show_bug.cgi?id=1892577 + https://bugzilla.redhat.com/show_bug.cgi?id=1893377 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900983 Title: Multiple heap buffer overflows caused by int overflow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cimg/+bug/1900983/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900983] Re: Multiple heap buffer overflows caused by int overflow
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-25693 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900983 Title: Multiple heap buffer overflows caused by int overflow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cimg/+bug/1900983/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900983] Re: Multiple heap buffer overflows caused by int overflow
** Description changed: The CImg library uses an unsafe pattern to calculate memory allocations size. At least in the PNM file format parser, an attacker can trivially supply width/height fields that overflow the heap and result in arbitrary heap writes. This probably also affects other file format parsers in CImg. The most prominent user of CImg is gmic. The gmic commandline tool directly exposes the load_pnm() functions (and also the other file format load functions) to the user and thus is affected. The issue is public and fixed in: https://github.com/dtschump/CImg/pull/295 + + Redhat bug: + https://bugzilla.redhat.com/show_bug.cgi?id=1892577 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900983 Title: Multiple heap buffer overflows caused by int overflow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cimg/+bug/1900983/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897856] [NEW] snap launch fails: symbol lookup error
Public bug reported: Using snap 3.38.0+git1.ffa3fd98 on Ubuntu MATE 20.04: /snap/evince/532/usr/bin/evince: symbol lookup error: /snap/evince/532/usr/lib/x86_64-linux-gnu/libevdocument3.so.4: undefined symbol: gdk_pixbuf_init_modules ** Affects: evince (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/1897856 Title: snap launch fails: symbol lookup error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1897856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897711] Re: No UI feedback while updating snaps
Sorry, I should have filed against update-manager. Can you please move the bug over to there ? It would be nice if these apps had "About" menu items. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897711 Title: No UI feedback while updating snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1897711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883250] Re: Behavior while checking/updating snaps
I've been using various Snaps for about 5 months now, and I've never seen any of those UI things appear. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883250 Title: Behavior while checking/updating snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1883250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897711] [NEW] No UI feedback while updating snaps
Public bug reported: While updating Snaps, the Details button doesn't work, and there is no indication of what is happening or did happen, and no progress indicator. Please fix/add these. Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: update-notifier 3.192.30 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Tue Sep 29 11:45:24 2020 InstallationDate: Installed on 2020-09-26 (3 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: update-notifier UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: update-notifier (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897711 Title: No UI feedback while updating snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1897711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897455] Re: Notifications don't say which VPN and network interface
Okay, filed https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/543 ** Bug watch added: gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues #543 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/543 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897455 Title: Notifications don't say which VPN and network interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1897455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897455] [NEW] Notifications don't say which VPN and network interface
Public bug reported: In Ubuntu MATE 20.04: If I connect to or disconnect from a VPN, I get a notification that says something like "disconnected from Network". This is too generic. Every notification involving a VPN change should specify the VPN connection name, and the underlying network interface name too. Every notification involving a network interface change (such as enabling/disabling Wi-Fi or Ethernet) should specify the network interface name. Every notification involving Wi-Fi should specify the Wi-Fi network name. Always give as much information as possible and reasonable. Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sun Sep 27 15:04:15 2020 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d InstallationDate: Installed on 2020-09-26 (1 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled disabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897455 Title: Notifications don't say which VPN and network interface To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1897455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897453] [NEW] Removable device notifications should give name
Public bug reported: In Ubuntu MATE 20.04: If you click on the icon next to a removable device to dismount and eject it, the notifications you get are something like "Writing to the drive, don't remove it yet" and "It is now safe to remove the drive". If you have multiple devices attached/mounted, this is not clear enough. Please specify the filesystem label (if possible) and device file name in each notification. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: caja 1.24.0-1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sun Sep 27 14:56:56 2020 InstallationDate: Installed on 2020-09-26 (1 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: caja UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: caja (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897453 Title: Removable device notifications should give name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1897453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897451] [NEW] Installer partial info in dialog about disk partitions
Public bug reported: Installing Ubuntu MATE 20.04: After choosing options such as LVM, before partitioning occurs, a dialog appears saying "Write the changes to disks ?". Some information seems to be missing or truncated. See last line in attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sun Sep 27 14:50:54 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu-mate.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2020-09-26 (1 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: ubiquity Symptom: installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.2 ** Attachment added: "MATE-Installer_20200926_100528.jpg" https://bugs.launchpad.net/bugs/1897451/+attachment/5414683/+files/MATE-Installer_20200926_100528.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897451 Title: Installer partial info in dialog about disk partitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1897451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897450] [NEW] Installer no way to see LVM password while you are setting it
Public bug reported: Ubuntu MATE 20.04 installer: While user is setting password to use on LVM encryption of disk, there should be some way for the user to see the password they have typed, to make sure it is correct, no typos. Maybe a hide/show toggle icon. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sun Sep 27 14:11:29 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu-mate.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2020-09-26 (1 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: ubiquity Symptom: installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897450 Title: Installer no way to see LVM password while you are setting it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1897450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896491] [NEW] Boot messages write over top of GRUB recovery menu
Public bug reported: 1. Hold down Shift key while booting, to get into GRUB 2. Choose options to get into Recovery menu (I forget exact wording) 3. As Ubuntu continues to finish booting, boot messages write over top of GRUB menu (see attached screenshot) 4. I think you can use up/down arrow keys to make the menu items appear again. But if a user gets confused and manages to click OK on something they can't read, they could damage their system. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: grub-pc 2.04-1ubuntu26.4 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Sep 21 15:25:31 2020 InstallationDate: Installed on 2020-04-29 (145 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "screenshot" https://bugs.launchpad.net/bugs/1896491/+attachment/5412957/+files/IMG_20200921_085056.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896491 Title: Boot messages write over top of GRUB recovery menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1896491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896489] [NEW] UI for "drop to root shell" is confusing
Public bug reported: 1. Boot into GRUB recovery menu. 2. Select menu item "Drop to root shell prompt". 3. Get prompt that says "Press Enter for maintenance (or press control-D to continue):" This is confusing, and actually backwards. Control-D doesn't "continue" with the menu item you selected, it ends the root shell and goes back to the menu. You want to press Enter if you want to continue on and get a root shell prompt. Please reword the prompt to something like "Press Enter to go to the root shell (or press control-D to go back to the menu):". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: grub-pc 2.04-1ubuntu26.4 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Sep 21 15:16:18 2020 InstallationDate: Installed on 2020-04-29 (145 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "screenshot" https://bugs.launchpad.net/bugs/1896489/+attachment/5412953/+files/IMG_20200921_085330.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896489 Title: UI for "drop to root shell" is confusing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1896489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893119] [NEW] Restart-required dialog gives no feedback
Public bug reported: I uninstall something that affects Nautilus, such as the MEGA sync package. I get a dialog that says "Nautilus Restart Required" (see attached screenshot). I click the "Restart Nautilus" button. I get no feedback that anything happened. I sit there wondering if it worked. I click the button a few more times. Eventually I go looking at other windows and find that yes, clicking that button makes any open Nautilus windows close, so I think a restart actually does happen. But the dialog gives me no feedback, no "restarted" message or anything. It should do so. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-44.48-generic 5.4.55 Uname: Linux 5.4.0-44-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 26 20:17:34 2020 InstallationDate: Installed on 2020-04-29 (119 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "screenshot of dialog" https://bugs.launchpad.net/bugs/1893119/+attachment/5404892/+files/Screenshot%20from%202020-08-26%2020-16-17.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893119 Title: Restart-required dialog gives no feedback To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1893119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889447] Re: Progress dialog looks frozen for multi-file 7z archives
Maybe use these steps to create the archives, then double-click on the first resulting archive file (tmp1.7z.001) and do an extract. mkdir tmp1 cd tmp1 for f in a b c d e f g h i j do for g in a b c d e f g h i j do for h in a b c d e f g h i j do dd if=/bin/ls of="$f$g$h" count=200 done done done cd .. 7za a -v10m -mx=0 tmp1.7z tmp1/* mv tmp1 tmp2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889447 Title: Progress dialog looks frozen for multi-file 7z archives To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1889447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889447] [NEW] Progress dialog looks frozen for multi-file 7z archives
Public bug reported: Suppose you have a four-file archive with files a.7z.001 a.7z.002 a.7z.003 a.7z.004 containing 500 files. While extracting from it, the progress dialog will show filename "a.7z.001" and "500 files remaining" and the progress-bar will stay near the left end, for the whole time, until extracting finishes. If it's not possible to display progress (maybe file-roller is launching 7zip in the background and there's no feedback mechanism ?), the dialog should say so. Give what information it has (total number of files that will be extracted, maybe), say progress can not be monitored, and don't give the appearance of a frozen extraction process. I don't know if the same happens for other file types. Same should apply to them. Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: file-roller 3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 18:49:48 2020 InstallationDate: Installed on 2020-04-29 (91 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: file-roller UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: file-roller (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889447 Title: Progress dialog looks frozen for multi-file 7z archives To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1889447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885130] Re: Please add a way to show only open-source apps
Okay, filed https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1021 Would be nice if ubuntu-bug sent me there directly. I'm getting tired of having to file a lot of bug reports twice. Sometimes downstream says go to upstream, sometimes upstream says go to downstream. The app displays as Ubuntu Software, but its CLI / package name is gnome- software. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-software/-/issues #1021 https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1021 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885130 Title: Please add a way to show only open-source apps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1885130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885130] [NEW] Please add a way to show only open-source apps
Public bug reported: Please add a setting in the store app to show only open-source apps, hiding proprietary apps. Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 25 15:07:51 2020 InstallationDate: Installed on 2020-04-29 (57 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InstalledPlugins: gnome-software-plugin-flatpak 3.36.0-0ubuntu3 gnome-software-plugin-snap3.36.0-0ubuntu3 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885130 Title: Please add a way to show only open-source apps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1885130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884387] Re: fwupdmgr file read error on RTL810xE PCI Express Fast Ethernet controller
Filed https://github.com/fwupd/fwupd/issues/2197 ** Bug watch added: github.com/fwupd/fwupd/issues #2197 https://github.com/fwupd/fwupd/issues/2197 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884387 Title: fwupdmgr file read error on RTL810xE PCI Express Fast Ethernet controller To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1884387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884387] Re: fwupdmgr file read error on RTL810xE PCI Express Fast Ethernet controller
Please change the status of this bug to "wishlist". Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884387 Title: fwupdmgr file read error on RTL810xE PCI Express Fast Ethernet controller To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1884387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884385] Re: fwupdmgr missing files, says "no results for XPath query"
Okay, filed https://github.com/fwupd/fwupd/issues/2196 ** Bug watch added: github.com/fwupd/fwupd/issues #2196 https://github.com/fwupd/fwupd/issues/2196 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884385 Title: fwupdmgr missing files, says "no results for XPath query" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1884385/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884387] Re: fwupdmgr file read error on RTL810xE PCI Express Fast Ethernet controller
Okay, thanks for the info. Should there be a less-alarming message ? Something like "this device does not support the verify operation" ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884387 Title: fwupdmgr file read error on RTL810xE PCI Express Fast Ethernet controller To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1884387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884387] [NEW] fwupdmgr file read error on RTL810xE PCI Express Fast Ethernet controller
Public bug reported: sudo fwupdmgr verify [DEVICEID] gives failed to verify RTL810xE PCI Express Fast Ethernet controller: failed to read firmware: Error reading from file: Input/output error Is there some file-permission error in the system, or the fwupd definition for this device is wrong, or something ? The device is not updatable according to fwupdmgr; maybe that is causing the error ? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: fwupd 1.3.9-4ubuntu0.1 ProcVersionSignature: Ubuntu 5.4.0-38.42-generic 5.4.44 Uname: Linux 5.4.0-38-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 20 21:38:44 2020 InstallationDate: Installed on 2020-04-29 (52 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: fwupd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fwupd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884387 Title: fwupdmgr file read error on RTL810xE PCI Express Fast Ethernet controller To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1884387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884385] [NEW] fwupdmgr missing files, says "no results for XPath query"
Public bug reported: fwupdmgr --show-all-devices get-devices does show three devices, one updatable. fwupdmgr refresh says "Successfully downloaded new metadata: 0 local devices supported" sudo fwupdmgr verify [DEVICEID] gives failed to verify [DEVICENAME]: no results for XPath query 'components/component/provides/firmware[@type='flashed'][text()='[DEVICEGUID]']/../../releases/release' for Intel Core Processor Integrated Graphics Controller (not updatable) and disk drive (updatable). Has the package or fwupdmgr failed to create some needed directory tree ".../components/component/provides/firmware/..." ? Or should the message be something better such as "unsupported device" or "no firmware available for this device" or something ? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: fwupd 1.3.9-4ubuntu0.1 ProcVersionSignature: Ubuntu 5.4.0-38.42-generic 5.4.44 Uname: Linux 5.4.0-38-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 20 21:28:35 2020 InstallationDate: Installed on 2020-04-29 (52 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: fwupd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fwupd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884385 Title: fwupdmgr missing files, says "no results for XPath query" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1884385/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884327] [NEW] installer should give easy options for common choices
Public bug reported: I installed Ubuntu 20.04 GNOME LTS a month or so ago. IIRC, the only easy choices given to the user were to encrypt using LVM, and to use ZFS, and there was little or no explanation of them. The installer should give simple radio-button or check-box ways to choose: - ZFS or not - encrypt Linux partitions using an LVM group, or not - encrypt home dirs using eCryptfs, or not - only a / partition, or separate / and /home partitions (and specify size for /) - choose swap partition (and specify size), or swapfile (and specify size), or no swap Each of these should have a significant help / explanation available in the installer. ** Affects: base-installer (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/1884327 Title: installer should give easy options for common choices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-installer/+bug/1884327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884245] [NEW] installer crash reporting should be simpler
Public bug reported: I installed Ubuntu 20.04 GNOME LTS, and during installation / partitioning some background process (partitioner ?) crashed. So the installer led me into creating or logging in to an UbuntuOne account, filing a bug report, etc. Who has access to their account information in the middle of a fresh install, or wants to be creating an account then ? There should be a much simpler, automatic bug-reporting mechanism in that context, similar to the desktop "something crashed, send / don't send a report ?" mechanism. ** Affects: base-installer (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/1884245 Title: installer crash reporting should be simpler To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-installer/+bug/1884245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883491] [NEW] Sound is played through wrong Output Device
Public bug reported: Since a few days my Ubuntu 20.04 systems shows the following behavior: The sound settings panel in part ignores the selected output device. I can switch between the devices and in turn all volume controls seem to affect that device (including the hotkeys etc.). But the sound is only every played through the Speakers port. The only way to temporarily fix this (until reboot or even suspend) is to open pavucontrol and manually change the port of the built in audio to "headphone". After this the sound is correctly played through the bluetooth headphones. Description:Ubuntu 20.04 LTS Release:20.04 pulseaudio 13.99.1 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: Confirmed ** Attachment added: "sound settings.png" https://bugs.launchpad.net/bugs/1883491/+attachment/5383904/+files/sound%20settings.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883491 Title: Sound is played through wrong Output Device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1883491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883250] [NEW] Behavior while checking/updating snaps
Public bug reported: In the Software Updater application, while checking/updating snaps: - the Details button does not work - there is no percent-progress indicator shown Please fix/improve these. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: update-manager 1:20.04.10.1 ProcVersionSignature: Ubuntu 5.4.0-38.42-generic 5.4.44 Uname: Linux 5.4.0-38-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.3 Aptdaemon: Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jun 12 14:14:28 2020 InstallationDate: Installed on 2020-04-29 (44 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: update-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal package-from-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883250 Title: Behavior while checking/updating snaps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1883250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880119] CurrentDmesg.txt
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1880119/+attachment/5375551/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880119 Title: System hangs on shut down Kernel 5.3.0-53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880119] ProcEnviron.txt
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1880119/+attachment/5375556/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880119 Title: System hangs on shut down Kernel 5.3.0-53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880119] Lspci.txt
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1880119/+attachment/5375552/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880119 Title: System hangs on shut down Kernel 5.3.0-53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880119] UdevDb.txt
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1880119/+attachment/5375560/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880119 Title: System hangs on shut down Kernel 5.3.0-53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880119] WifiSyslog.txt
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1880119/+attachment/5375561/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880119 Title: System hangs on shut down Kernel 5.3.0-53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880119] ProcModules.txt
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1880119/+attachment/5375558/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880119 Title: System hangs on shut down Kernel 5.3.0-53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880119] PulseList.txt
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1880119/+attachment/5375559/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880119 Title: System hangs on shut down Kernel 5.3.0-53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880119] ProcInterrupts.txt
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1880119/+attachment/5375557/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880119 Title: System hangs on shut down Kernel 5.3.0-53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880119] ProcCpuinfo.txt
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1880119/+attachment/5375554/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880119 Title: System hangs on shut down Kernel 5.3.0-53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880119] ProcCpuinfoMinimal.txt
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1880119/+attachment/537/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880119 Title: System hangs on shut down Kernel 5.3.0-53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880119] Lsusb.txt
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1880119/+attachment/5375553/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880119 Title: System hangs on shut down Kernel 5.3.0-53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880119] CRDA.txt
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1880119/+attachment/5375550/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880119 Title: System hangs on shut down Kernel 5.3.0-53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880119] Re: System hangs on shut down Kernel 5.3.0-53
*** This bug is a duplicate of bug 1879997 *** https://bugs.launchpad.net/bugs/1879997 apport information ** Tags added: apport-collected tricia ** Description changed: System does not shut down properly with this Kernel: Kernel 5.3.0-51 seems to work OK This is on a system running Mint 19.3 and "ubuntu-bug linux" is not working. Attached is version.log and the output of inxi + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.14 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC2: toni 1676 F pulseaudio + /dev/snd/controlC1: toni 1676 F pulseaudio + /dev/snd/controlC0: toni 1676 F pulseaudio + CurrentDesktop: X-Cinnamon + DistroRelease: Linux Mint 19.3 + HibernationDevice: RESUME=UUID=d0307c73-ce08-4c07-bb9b-1cf668a42a00 + InstallationDate: Installed on 2019-07-25 (301 days ago) + InstallationMedia: Linux Mint 19.2 "Tina" - Release amd64 20190711 + IwConfig: + enp8s0no wireless extensions. + + lono wireless extensions. + MachineType: Gigabyte Technology Co., Ltd. B450M S2H + Package: linux (not installed) + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-53-generic root=UUID=c5a03a46-cc90-417d-97fc-906910b14c02 ro idle=nomwait quiet splash processor.max_cstate=5 vt.handoff=1 + ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 + RelatedPackageVersions: + linux-restricted-modules-5.3.0-53-generic N/A + linux-backports-modules-5.3.0-53-generic N/A + linux-firmware1.173.18 + RfKill: + + Tags: tricia + Uname: Linux 5.3.0-53-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm backup cdrom dip lp lpadmin messagebus plugdev sambashare saned scanner ssh sudo vboxusers + _MarkForUpload: True + dmi.bios.date: 11/27/2019 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: F50 + dmi.board.asset.tag: Default string + dmi.board.name: B450M S2H + dmi.board.vendor: Gigabyte Technology Co., Ltd. + dmi.board.version: x.x + dmi.chassis.asset.tag: Default string + dmi.chassis.type: 3 + dmi.chassis.vendor: Default string + dmi.chassis.version: Default string + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MS2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MS2H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: + dmi.product.family: Default string + dmi.product.name: B450M S2H + dmi.product.sku: Default string + dmi.product.version: Default string + dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1880119/+attachment/5375549/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880119 Title: System hangs on shut down Kernel 5.3.0-53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880119] [NEW] System hangs on shut down Kernel 5.3.0-53
Public bug reported: System does not shut down properly with this Kernel: Kernel 5.3.0-51 seems to work OK This is on a system running Mint 19.3 and "ubuntu-bug linux" is not working. Attached is version.log and the output of inxi ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "version and inxi output" https://bugs.launchpad.net/bugs/1880119/+attachment/5375547/+files/version.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880119 Title: System hangs on shut down Kernel 5.3.0-53 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783994] Re: systemd spams log with "Failed to dissect: Input/output error" on systems with mmc
I can confirm, that the package in -proposed fixed the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783994 Title: systemd spams log with "Failed to dissect: Input/output error" on systems with mmc To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1783994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754836] Re: Xubuntu: (not really an error at all) ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activ
Similar happens in Linux Mint 19 system with no Bluetooth devices. In Settings/Bluetooth, I have no Bluetooth devices and all settings are set to "off". In output of journalctl, I see this while booting: pulseaudio[2770]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. P... dbus-daemon[853]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.157' (uid=1000) dbus-daemon[853]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) and the last two lines are repeated occasionally as the system runs. Boot log contains: Linux version 4.15.0-38-generic (buildd@lcy01-amd64-023) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #41-Ubuntu SMP Wed Oct 10 10:59:38 UTC 2018 (Ubuntu 4.15.0-38.41-generic 4.15.18) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754836 Title: Xubuntu: (not really an error at all) ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1754836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys
I see the messages (starting with "Could not find key with description") on a fresh install of Linux Mint 19 Cinnamon. Second line of kern.log says: "Linux version 4.15.0-36-generic (buildd@lgw01-amd64-031) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 (Ubuntu 4.15.0-36.39-generic 4.15.18)" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718658 Title: ecryptfs-mount-private fails to initialize ecryptfs keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783746] Re: ipmmu is always registered
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783746 Title: ipmmu is always registered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787945] Re: Tango platform uses __initcall without further checks
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787945 Title: Tango platform uses __initcall without further checks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752411] Re: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck
I found a source reference here: https://github.com/fanf2/bind-9/blob/master/lib/isc/unix/socket.c#L4127 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752411 Title: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1752411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752411] Re: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck
also attching a gdb full bt, which shows that epoll_wait is called it a timeout value of "-1" (infinite) in thread #4. ** Attachment added: "gdb.txt" https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1752411/+attachment/5182603/+files/gdb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752411 Title: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1752411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752411] Re: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck
in fact, there are two host commands running, both show wchan=sigsuspend, perf shows nothing and strace shows commands is suspended. new strace is attached. ** Attachment added: "strace.txt" https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1752411/+attachment/5182590/+files/strace.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752411 Title: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1752411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787945] Re: Tango platform uses __initcall without further checks
well, I think you forgot to attach the patch. So I called editconfig myself and disabled the TANGO platform. For unknown reasons, this also enables CONFIG_ARCH_HAS_FILTER_PGPROT in config.common.ubuntu... Anyway, the new kernel boots and suspends/resume just fine. ** Patch added: "q.diff" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787945/+attachment/5179894/+files/q.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787945 Title: Tango platform uses __initcall without further checks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787945] Re: Tango platform uses __initcall without further checks
Thanks for picking this up. While disabling all non-dt platforms seems a bit rude, disabling all "non-multi_v7" defconfig platforms seems to be a good idea to start with in order to avoid more of such problems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787945 Title: Tango platform uses __initcall without further checks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787945] Re: Tango platform uses __initcall without further checks
** 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/1787945 Title: Tango platform uses __initcall without further checks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787945] [NEW] Tango platform uses __initcall without further checks
Public bug reported: The TANGO platform is enabled by default in the multiplatform ARM kernel. However, it calls __initcall in arch/arm/mach-tango/pm.c without a check whether it actually runs on this hw. This causes an OOPS during suspend on my Tegra platform. Please disable this (multiplatform incompatible) arch. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787945 Title: Tango platform uses __initcall without further checks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783746] Re: ipmmu is always registered
It is possible that it didn't show up in older kernels (4.4 for X) because Tegra didn't used the IOMMU at that time. ** 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/1783746 Title: ipmmu is always registered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783746] Re: ipmmu is always registered
It started after upgrade from X to B. This may only show up on Tegra2, which does not have an IOMMU, and which creates problems if one is registered. Sorry, I don't understand the technical details. AFAICT, the whole driver is still broken in mainline kernel (since 3.20). An upstream fixed is currently proposed. See: https://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git/commit/?h=next=5c5c87411488af3cd082221e567498d813d0fe83 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783746 Title: ipmmu is always registered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783994] Re: systemd spams log with "Failed to dissect: Input/output error" on systems with mmc
here is an updated fix: https://github.com/systemd/systemd/commit/cde942f61bf231ea4a0d50780cdb4e744458daeb #diff-5be2770e81c14245e90d2916ded39491 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783994 Title: systemd spams log with "Failed to dissect: Input/output error" on systems with mmc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783994] [NEW] systemd spams log with "Failed to dissect: Input/output error" on systems with mmc
Public bug reported: If a device has an mmc installed, systemd-gpt-auto-generator will fail because of "special partition" (rpmb, boot) and record a log message: systemd-gpt-auto-generator[207]: Failed to dissect: Input/output error This issue was discussed here: https://github.com/systemd/systemd/issues/5806 and a fix is proposed for new systemd versions. Please include in bionic. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783994 Title: systemd spams log with "Failed to dissect: Input/output error" on systems with mmc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783746] Re: ipmmu is always registered
** 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/1783746 Title: ipmmu is always registered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783746] [NEW] ipmmu is always registered
Public bug reported: Hi, booting the bionic kernel (4.15.0-29-generic) on my Tegra20 device (no iommu), I found it crashes during display driver setup. The bootlog (and crash) is attached. Asking on Tegra IRC channel, digetx found that this is caused by the IPMMU-VMSA driver which is always registered via initcall. Adding "initcall_blacklist=ipmmu_init" to the kernel parameters makes it boot fine. Maybe this buggy driver should be disabled in the config (or fixed somehow)? ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bionic ** Attachment added: "bootlog" https://bugs.launchpad.net/bugs/1783746/+attachment/5168044/+files/paste_1035175 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783746 Title: ipmmu is always registered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1032456] Re: Canon inkjets (and some other printers) print only half of the last page after 20120801 upgrade to v1.5.3-0ubuntu2
I have been an issue with my printer for few days. I have tried your method but I got no result after that I visit https://printerssupport.org/ricoh-printer-support/ this site and they give me to guide me to set up. Now My printer is working fine -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1032456 Title: Canon inkjets (and some other printers) print only half of the last page after 20120801 upgrade to v1.5.3-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1032456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754075] Re: apt-setup uses apt-key but probably should not anymore
Hello, I have build locally an updated apt-setup.udeb with the patch from #12 and it works for me. Installation of the rebuild udeb is a bit hacky via early_command: d-i preseed/early_command string wget -q -O /tmp/apt-setup.udeb http:///apt-setup-udeb_0.104ubuntu5_amd64.udeb; udpkg -i /tmp/apt-setup.udeb I have used a preseed file, which contains 2 local repositories: # Ubuntu DESY Repository d-i apt-setup/local0/repository string \ deb http:///extra/desy/ bionic desy d-i apt-setup/local0/source boolean false d-i apt-setup/local0/comment string desy d-i apt-setup/local0/key string http:///extra/desy/DESY-Debian-key.asc # Puppet PC1 d-i apt-setup/local1/repository string \ deb http:///extra/puppet.apt.timeline/current/ bionic PC1 d-i apt-setup/local1/source boolean false d-i apt-setup/local1/comment string puppetlabs d-i apt-setup/local1/key string http:///extra/puppet.apt.timeline/current/pubkey.gpg The updated udeb downloads the keys and copies them to /target/etc/apt/trusted/gpg.d: ~ # ls -la /target/etc/apt/trusted.gpg.d/ drwxr-xr-x2 root root 4096 Apr 11 20:32 . drwxr-xr-x6 root root 4096 Apr 11 20:32 .. -rw-r--r--1 root root 971 Feb 25 2015 desy.asc -rw-r--r--1 root root 3139 Feb 22 23:34 puppetlabs.asc -rw-r--r--1 root root 2796 Feb 6 17:15 ubuntu-keyring-2012-archive.gpg -rw-r--r--1 root root 2794 Feb 6 17:15 ubuntu-keyring-2012-cdimage.gpg Additionally, detection of non-binary format for the puppetlabs key worked as well, as it now contains the .asc extension. Side remark, a similar bug entry exists for debian-installer on launchpad as well: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1761030 Regards, Stefan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754075 Title: apt-setup uses apt-key but probably should not anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-setup/+bug/1754075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752411] Re: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck
My system was upgraded, so maybe a leftover. So I uninstalled ifupdown and upstart. Problem still persists :-( I will attach a ltrace -Sf host output - maybe it helps... ** Attachment added: "output of "trace -Sf host -d -v -w5 -t soa local."" https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1752411/+attachment/5107990/+files/ltrace.txt.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752411 Title: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1752411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761895] Re: Post-install boot loop: "System BootOrder not found."
I found the reason for this problem: it turned out to be the BIOS setting "Boot Order Lock". After disabling it, I saw the above message one more time, then Ubuntu started properly (and a new boot entry called "ubuntu" appeared in the BIOS). I don't know if this is possible, but it would be a good idea to detect that the "ubuntu" boot entry wasn't actually created and display an error message. If it's not possible, an additional hint about "Boot Order Lock" or similar BIOS settings might be helpful (as well as showing the message for more than a split-second). ** Package changed: ubiquity (Ubuntu) => grub2 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761895 Title: Post-install boot loop: "System BootOrder not found." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1761895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761911] Re: Have to manually "sudo ifconfig eth0 up" and "sudo dhclient eth0" after every reboot
Before I submitted this, I had run the following command, per the web page mentioned above. sudo apt-get install libnl-3-200=3.2.21-1 libnl-route-3-200=3.2.21-1 libnl-genl-3-200=3.2.21-1 After submitting this, I ran the following commands: sudo apt-get update sudo apt-get install network-manager network-manager was reinstalled, and my server gets connected to the LAN again automatically after I reboot. network-manager-gnome was also reinstalled. I'd like to know if I can safely do sudo apt-mark unhold libnl-3-200 libnl-genl-3-200 libnl-route-3-200 For now, I'll just stick with the downgraded libnl packages as I don't want to have more networking problems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761911 Title: Have to manually "sudo ifconfig eth0 up" and "sudo dhclient eth0" after every reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1761911/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761911] [NEW] Have to manually "sudo ifconfig eth0 up" and "sudo dhclient eth0" after every reboot
Public bug reported: I did an upgrade with "sudo apt-get dist-upgrade", and it removed network-manager and network-manager-gnome. I could not connect to my LAN afer that. I was able to find instructions for downgrading the libnl packages at https://askubuntu.com/questions/727127/last-upgrade-crashes-network-manager-no-internet-connection-no-applet I am able to get online again by running the following commands sudo ifconfig eth0 up sudo dhclient eth0 (Fortunately, I have a Ethernet I can plug in to.) I have to do this every time I reboot. This is inconvenient as a usually use Desktop Sharing with another computer as the client. I use an SSH tunnel for security. This means that every time I reboot, I have to physically access the computer's console to enter the ifconfig and dhclient commands to get the computer back on the network. I tried to reinstall network-manager and network-manager-gnome, but the command results said there were dependencies that prevented the installation. The fixes in the web page referenced above do not help, so I'm reporting this as a bug. Thanks for your assistance. $ sudo lsb_release -rd [sudo] password for wally: Description:Ubuntu 14.04.1 LTS Release:14.04 $ $ apt-cache policy network-manager network-manager: Installed: (none) Candidate: 0.9.8.8-0ubuntu7.1 Version table: 0.9.8.8-0ubuntu7.1 0 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 0.9.8.8-0ubuntu7 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages $ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager (not installed) ProcVersionSignature: Ubuntu 3.13.0-144.193-generic 3.13.11-ckt39 Uname: Linux 3.13.0-144-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 6 21:21:27 2018 InstallationDate: Installed on 2014-10-22 (1262 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761911 Title: Have to manually "sudo ifconfig eth0 up" and "sudo dhclient eth0" after every reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1761911/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761895] [NEW] Post-install boot loop: "System BootOrder not found."
Public bug reported: Bionic Beaver Final Beta doesn't install properly on my computer (Thinkpad E480 with an NVMe SSD, no SATA disk). After finishing the installation, the machine repeatedly shows these messages and reboots: System BootOrder not found. Initializing defaults. Creating boot entry "Boot" with label "ubuntu" for file "\EFI\ubuntu\shimx64.efi" Reset System This happens both with automatic and manual partitioning. Setting the "UEFI/Legacy" switch in the BIOS to "Both" or "UEFI Only" also doesn't make a difference. (The installer doesn't boot at all when choosing "Legacy Only".) I checked the EFI partition and the file "\EFI\ubuntu\shimx64.efi" does exist. ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761895 Title: Post-install boot loop: "System BootOrder not found." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1761895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752411] Re: Can not ping IP addresses on remote network after connect
If you define "infinite" as longer than 10 seconds - yes. Something is quite bogus here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752411 Title: Can not ping IP addresses on remote network after connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1752411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752411] Re: Can not ping IP addresses on remote network after connect
in fact, the "host" command is hanging, sorry. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752411 Title: Can not ping IP addresses on remote network after connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1752411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752411] Re: Can not ping IP addresses on remote network after connect
I'm also affected. Looking at the process list (ps ax) I found: 23386 pts/4 S+ 0:00 openconnect -v -s /usr/share/vpnc-scripts/vpnc-script vpn.example.com 23400 pts/4 S+ 0:00 /bin/sh -c /usr/share/vpnc-scripts/vpnc-script 23405 pts/4 S+ 0:00 /bin/sh /usr/share/vpnc-scripts/vpnc-script 23440 ? Ssl 0:00 /usr/lib/NetworkManager/nm-dispatcher 23443 ? S 0:00 /bin/sh -e /etc/NetworkManager/dispatcher.d/01-ifupdown tun0 up 23468 pts/4 S+ 0:00 run-parts --arg=-a --arg=tun0 /etc/resolvconf/update.d 23479 pts/4 S+ 0:00 run-parts /etc/resolvconf/update-libc.d 23500 ? S 0:00 /bin/sh /etc/network/if-up.d/ntpdate 23502 ? S 0:00 flock -n /run/lock/ntpdate /usr/sbin/ntpdate-debian -s 23504 ? S< 0:00 /usr/sbin/ntpdate -s de.pool.ntp.org 23515 pts/4 S+ 0:00 /bin/sh /usr/lib/avahi/avahi-daemon-check-dns.sh 23534 pts/4 Sl+ 0:00 host -t soa local. 23539 ? S 0:00 run-parts /etc/network/if-up.d 23550 ? S 0:00 /bin/sh /usr/lib/avahi/avahi-daemon-check-dns.sh 23567 ? Sl 0:00 host -t soa local. 23574 pts/3 R+ 0:00 ps ax the "avahi-daemon-check-dns.sh" process hangs, maybe because the route to dns isn't setup yet (vpnc-script still running). If I kill this process (pid 23550) the script continues to run and the connect is alive and stable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752411 Title: Can not ping IP addresses on remote network after connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1752411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731328] Re: Periodically drops Tx frames and requires disconnect/reconnect
sorry, above comment was meant to be added to bug 1752411. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731328 Title: Periodically drops Tx frames and requires disconnect/reconnect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1731328/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731328] Re: Periodically drops Tx frames and requires disconnect/reconnect
I'm also affected. Looking at the process list (ps ax) I found: 23386 pts/4S+ 0:00 openconnect -v -s /usr/share/vpnc-scripts/vpnc-script vpn.example.com 23400 pts/4S+ 0:00 /bin/sh -c /usr/share/vpnc-scripts/vpnc-script 23405 pts/4S+ 0:00 /bin/sh /usr/share/vpnc-scripts/vpnc-script 23440 ?Ssl0:00 /usr/lib/NetworkManager/nm-dispatcher 23443 ?S 0:00 /bin/sh -e /etc/NetworkManager/dispatcher.d/01-ifupdown tun0 up 23468 pts/4S+ 0:00 run-parts --arg=-a --arg=tun0 /etc/resolvconf/update.d 23479 pts/4S+ 0:00 run-parts /etc/resolvconf/update-libc.d 23500 ?S 0:00 /bin/sh /etc/network/if-up.d/ntpdate 23502 ?S 0:00 flock -n /run/lock/ntpdate /usr/sbin/ntpdate-debian -s 23504 ?S< 0:00 /usr/sbin/ntpdate -s de.pool.ntp.org 23515 pts/4S+ 0:00 /bin/sh /usr/lib/avahi/avahi-daemon-check-dns.sh 23534 pts/4Sl+0:00 host -t soa local. 23539 ?S 0:00 run-parts /etc/network/if-up.d 23550 ?S 0:00 /bin/sh /usr/lib/avahi/avahi-daemon-check-dns.sh 23567 ?Sl 0:00 host -t soa local. 23574 pts/3R+ 0:00 ps ax the "avahi-daemon-check-dns.sh" process hangs, maybe because the route to dns isn't setup yet (vpnc-script still running). If I kill this process (pid 23550) the script continues to run and the connect is alive and stable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731328 Title: Periodically drops Tx frames and requires disconnect/reconnect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1731328/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748747] Re: Laptop turns of when secondary battery is empty while main battery is still charged.
Apparently it is known for quite a while (read 6 years) that UPower has some problem with dual battery systems: https://bugs.freedesktop.org/show_bug.cgi?id=55278 ** Bug watch added: freedesktop.org Bugzilla #55278 https://bugs.freedesktop.org/show_bug.cgi?id=55278 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748747 Title: Laptop turns of when secondary battery is empty while main battery is still charged. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748747] Re: Laptop turns of when secondary battery is empty while main battery is still charged.
Joseph, since I am using the laptop as main working device I am very reluctant to switch from the ubuntu custom kernel to mainline and let the machine die willingly. I got a pointer via AskUbuntu (https://askubuntu.com/questions/961278/how-to-prevent-shutdown-when- one-of-two-batteries-is-empty) that UPower is likely to be the real culprit (https://forums.lenovo.com/t5/Linux-Discussion/How-to-get-dual- battery-to-switch-without-powering-off-in-Linux/td-p/3890605). I will now tell UPower to warn instead of shutting down, turn on the gnome power management again and check whether the problem stays. If that is the case I will go ahead an run 4.16 :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748747 Title: Laptop turns of when secondary battery is empty while main battery is still charged. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1333017] Re: update ac100 support
patch above misses the device-tree, correction attached. ** Patch added: "db.diff" https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1333017/+attachment/5056934/+files/db.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1333017 Title: update ac100 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1333017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1333017] Re: update ac100 support
** Patch added: "patch to the machine db" https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1333017/+attachment/5053491/+files/db.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1333017 Title: update ac100 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1333017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1333017] Re: update ac100 support
Sorry for the late reply. Yes, current kernel works fine with the AC100. I'll send an updated boot script and db patch. The old android/fastboot bootloader is no longer used. The boot script should work on all tegras AFAIK. ** Attachment added: "Boot script for Tegra SoCs (using uboot)" https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1333017/+attachment/5053490/+files/bootscr.tegra -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1333017 Title: update ac100 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1333017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748747] [NEW] Laptop turns of when secondary battery is empty while main battery is still charged.
Public bug reported: I'm using a Lenovo T460s with two batteries running Ubuntu 17.10. The indicator shows the combined charge of both batteries and I was at 40% when the laptop simply turned off. After the reboot I saw that the main battery was at 88% while the extra battery was at 0%. For some reason the OS deemed it necessary to perform an emergency shutdown without any warning. I don't know whether this is a problem in gnome power management or the kernel but please, please find a fix for this! Or provide some workaround. Best regards Christoph Grimmer-Dietrich ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: battery manager power -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748747 Title: Laptop turns of when secondary battery is empty while main battery is still charged. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741284] [NEW] installation fail
Public bug reported: during installation, when the bootloader should be written to a selected partition the system hangs. System Ubuntu budgie 17.10 (downloaded). release: 2.20.7-0ubuntu3 ? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubiquity 17.10.10 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CasperVersion: 1.387 CurrentDesktop: Budgie Date: Thu Jan 4 16:22:58 2018 LiveMediaBuild: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcEnviron: LANGUAGE=de_DE.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741284 Title: installation fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1741284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 60442] Re: Dual / Two Batteries, shutdown on empty expansion battery.
I'm running Ubuntu 17.04 on a Lenovo Thinkpad T460s. My Laptop just shut down when the 2nd battery was empty and the 1st was at about 40% capacity. That really sucks especially since this happend for the first time in a year. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/60442 Title: Dual / Two Batteries, shutdown on empty expansion battery. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/60442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
