[Bug 1916800] Re: Unmaintained and can crash, leaving fans at minimum speed
Bump, something needs to be done about this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916800 Title: Unmaintained and can crash, leaving fans at minimum speed To manage notifications about this bug go to: https://bugs.launchpad.net/macfanctld/+bug/1916800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916800] Re: Unmaintained and can crash, leaving fans at minimum speed
** Also affects: macfanctld 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/1916800 Title: Unmaintained and can crash, leaving fans at minimum speed To manage notifications about this bug go to: https://bugs.launchpad.net/macfanctld/+bug/1916800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918468] Re: Ubuntu 20.04: GUFW doesn't display firewall information correctly when ufw issues warnings
Original bug here: https://bugs.launchpad.net/ubuntu/+source/gui- ufw/+bug/1916799. I'd like to get the above patch into Ubuntu to fix this issue, I'm assuming you have the ability to do that? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918468 Title: Ubuntu 20.04: GUFW doesn't display firewall information correctly when ufw issues warnings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gui-ufw/+bug/1918468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918468] Re: Ubuntu 20.04: GUFW doesn't display firewall information correctly when ufw issues warnings
Marked as invalid as unintentional duplicate. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918468 Title: Ubuntu 20.04: GUFW doesn't display firewall information correctly when ufw issues warnings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gui-ufw/+bug/1918468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918468] [NEW] Ubuntu 20.04: GUFW doesn't display firewall information correctly when ufw issues warnings
Public bug reported: Hello, 1) Ubuntu release: 20.04 LTS 2) GUFW version: 20.04.1-1ubuntu1 3) Firewall displays information and state correctly despite warnings from UFW. 4) Firewall displays no rules and incorrectly displays enable/disabled status. Previous discussion here: https://answers.launchpad.net/ubuntu/+source /gui-ufw/+question/695073 A little time ago, I encountered the issue at https://github.com/costales/gufw/issues/9 that was subsequently fixed. As this firewall ships with Ubuntu, and this is a fairly serious bug, would it potentially be possible to get this updated in the repos? An update to version 21.04 would fix the issue I believe, or the below patch would also fix the problem. I think this fix is definitely worth having in the repositories as misreporting the state of the firewall and the rules available (as it did for me) is quite serious. A patch for the fix is available at https://github.com/costales/gufw/files/5430823/fix_9.zip. If any further information is needed, let me know and I'll be happy to provide it. Hamish ** Affects: gui-ufw (Ubuntu) Importance: Undecided Status: Invalid ** Changed in: gui-ufw (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918468 Title: Ubuntu 20.04: GUFW doesn't display firewall information correctly when ufw issues warnings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gui-ufw/+bug/1918468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916799] Re: Ubuntu 20.04: GUFW doesn't display firewall information correctly when ufw issues warnings
Unsure how to link to focal. Hopefully someone will notice it and pick it up. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916799 Title: Ubuntu 20.04: GUFW doesn't display firewall information correctly when ufw issues warnings To manage notifications about this bug go to: https://bugs.launchpad.net/gui-ufw/+bug/1916799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 253119] Re: PPA packages do not show a changelog in update-manager
This seems to work fine now - close? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/253119 Title: PPA packages do not show a changelog in update-manager To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/253119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916799] Re: Ubuntu 20.04: GUFW doesn't display firewall information correctly when ufw issues warnings
** Also affects: gui-ufw 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/1916799 Title: Ubuntu 20.04: GUFW doesn't display firewall information correctly when ufw issues warnings To manage notifications about this bug go to: https://bugs.launchpad.net/gui-ufw/+bug/1916799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916799] Re: Ubuntu 20.04: GUFW doesn't display firewall information correctly when ufw issues warnings
Ah, I thought that was who I was reporting it to. I'll see if I can figure it out. Hamish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916799 Title: Ubuntu 20.04: GUFW doesn't display firewall information correctly when ufw issues warnings To manage notifications about this bug go to: https://bugs.launchpad.net/gui-ufw/+bug/1916799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916800] Re: Unmaintained and can crash, leaving fans at minimum speed
All done, hope this helps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916800 Title: Unmaintained and can crash, leaving fans at minimum speed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/macfanctld/+bug/1916800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916800] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1916800/+attachment/5467210/+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/1916800 Title: Unmaintained and can crash, leaving fans at minimum speed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/macfanctld/+bug/1916800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916800] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1916800/+attachment/5467209/+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/1916800 Title: Unmaintained and can crash, leaving fans at minimum speed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/macfanctld/+bug/1916800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916800] Re: Unmaintained and can crash, leaving fans at minimum speed
apport information ** Tags added: apport-collected third-party-packages ulyssa ** Description changed: Hi there, 1) Ubuntu release: 20.04 LTS (Mint 20). 2) 0.6+repack1-2 3) Software controls fans correctly without any issues. 4) Software randomly crashes, leaving fans at minimum speed regardless of temps. This package seems to have been unmaintained for several years - upstream repo at https://github.com/MikaelStrom/macfanctld hasn't been updated since 2013 and most forks don't fare any better. On my period-correct Late 2013 Macbook Pro with Ubuntu 20.04 base (Mint 20) macfanctld has apparently crashed in the background several times when the system is under load. What's bad is that this leaves the fans stuck on minimum speed - seems the firmware isn't able to take over at this point. Fortunately, I have a temperature widget so I could see the temps were getting dangerously hot, but I can definitely see this cooking machines. What's worse is that this appears to work for hours or even days before crashing sometimes - it is hard to pin down. Given the existence of another actively-maintained program in the repos - mbpfan https://github.com/linux-on-mac/mbpfan - with a solid compatibility list, I suggest removing this old program to avoid damaging people's hardware. I also imagine that given it didn't work properly on my old hardware, it has even more issues on newer machines. I have had no problems since switching to mbpfan. Hamish + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.16 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: X-Cinnamon + DistroRelease: Linux Mint 20.1 + EcryptfsInUse: Yes + InstallationDate: Installed on 2018-02-11 (1110 days ago) + InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124 + NonfreeKernelModules: wl + Package: macfanctld 0.6+repack1-2 [origin: Ubuntu] + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 + Tags: ulyssa third-party-packages + Uname: Linux 5.4.0-66-generic x86_64 + UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1916800/+attachment/5467208/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916800 Title: Unmaintained and can crash, leaving fans at minimum speed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/macfanctld/+bug/1916800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916800] [NEW] Unmaintained and can crash, leaving fans at minimum speed
Public bug reported: Hi there, 1) Ubuntu release: 20.04 LTS (Mint 20). 2) 0.6+repack1-2 3) Software controls fans correctly without any issues. 4) Software randomly crashes, leaving fans at minimum speed regardless of temps. This package seems to have been unmaintained for several years - upstream repo at https://github.com/MikaelStrom/macfanctld hasn't been updated since 2013 and most forks don't fare any better. On my period-correct Late 2013 Macbook Pro with Ubuntu 20.04 base (Mint 20) macfanctld has apparently crashed in the background several times when the system is under load. What's bad is that this leaves the fans stuck on minimum speed - seems the firmware isn't able to take over at this point. Fortunately, I have a temperature widget so I could see the temps were getting dangerously hot, but I can definitely see this cooking machines. What's worse is that this appears to work for hours or even days before crashing sometimes - it is hard to pin down. Given the existence of another actively-maintained program in the repos - mbpfan https://github.com/linux-on-mac/mbpfan - with a solid compatibility list, I suggest removing this old program to avoid damaging people's hardware. I also imagine that given it didn't work properly on my old hardware, it has even more issues on newer machines. I have had no problems since switching to mbpfan. Hamish ** Affects: macfanctld (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/1916800 Title: Unmaintained and can crash, leaving fans at minimum speed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/macfanctld/+bug/1916800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916799] [NEW] Ubuntu 20.04: GUFW doesn't display firewall information correctly when ufw issues warnings
Public bug reported: Hello, 1) Ubuntu release: 20.04 LTS 2) GUFW version: 20.04.1-1ubuntu1 3) Firewall displays information and state correctly despite warnings from UFW. 4) Firewall displays no rules and incorrectly displays enable/disabled status. Previous discussion here: https://answers.launchpad.net/ubuntu/+source /gui-ufw/+question/695073 A little time ago, I encountered the issue at https://github.com/costales/gufw/issues/9 that was subsequently fixed. As this firewall ships with Ubuntu, and this is a fairly serious bug, would it potentially be possible to get this updated in the repos? An update to version 21.04 would fix the issue I believe, or the below patch would also fix the problem. I think this fix is definitely worth having in the repositories as misreporting the state of the firewall and the rules available (as it did for me) is quite serious. A patch for the fix is available at https://github.com/costales/gufw/files/5430823/fix_9.zip. If any further information is needed, let me know and I'll be happy to provide it. Hamish ** Affects: gui-ufw (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/1916799 Title: Ubuntu 20.04: GUFW doesn't display firewall information correctly when ufw issues warnings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gui-ufw/+bug/1916799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
NB: Have been informed that this will trickle down from upstream into the 5.10 kernels for Raspberry Pi OS as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
Mentioned to Raspberry Pi people at: https://github.com/raspberrypi/linux/issues/3850 If anyone knows of a more current bug report for this issue, let me know. ** Bug watch added: github.com/raspberrypi/linux/issues #3850 https://github.com/raspberrypi/linux/issues/3850 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
Nice :) Does anyone know if this is getting into Raspberry Pi OS? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881197] Re: No network usage info presented, always 0 bytes/s.
Okay, works for me. Package version: 3.36.1-0ubuntu0.20.04.1 (amd64) Details of testing: I changed the update frequency to 0.5 and 0.25 seconds and the network graph and stats continued to work, unlike before when the graph stopped displaying meaningful information. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881197 Title: No network usage info presented, always 0 bytes/s. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-system-monitor/+bug/1881197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881197] Re: No network usage info presented, always 0 bytes/s.
Thank you! :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881197 Title: No network usage info presented, always 0 bytes/s. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-system-monitor/+bug/1881197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881197] Re: No network usage info presented, always 0 bytes/s.
I have the same issue, in my case at least it's definitely the issue you found Sebastien. As pointed out at https://answers.launchpad.net/ubuntu/+source/gnome- system-monitor/+question/693912, Ubuntu is not a rolling release, but it would improve UX, and as noted at https://wiki.ubuntu.com/StableReleaseUpdates updates with simple changes that don't affect infrastructure may be candidates. Of course, it's not my decision to make, and if there's no interest I will instead report to the Linux Mint people, but I figure trying upstream first is better. ** Changed in: gnome-system-monitor (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881197 Title: No network usage info presented, always 0 bytes/s. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1881197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881197] Re: No network usage info presented, always 0 bytes/s.
NB: I'm using Linux Mint 20, which is based on Ubuntu 20.04 and uses the gnome-system-monitor package from Ubuntu 20.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881197 Title: No network usage info presented, always 0 bytes/s. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1881197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
Have you tried the new overlay (dwc2)? It worked really well for me, thread and instructions here: https://github.com/raspberrypi/linux/issues/3843 ** Bug watch added: github.com/raspberrypi/linux/issues #3843 https://github.com/raspberrypi/linux/issues/3843 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
@scubachristopher what kernel version did that put you on? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
Also happens on Linux 5.4 on Raspbian 10. Okay, I'll keep that in mind. At the moment I'm trying a different overlay (driver) for the USB chip to see if that helps (not sure yet, though it hasn't helped with the HDD). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
NB: On Linux 4.9. I'll post here again if it happens on the new kernel (5.4). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
I'm having this issue as well, but on Raspbian 10. Symptoms seems the same, generally occurs with high load. However, I don't seem to need IPv6 packets to cause this - my network is IPv4 only. I thought I had a power problem because I am also using an external HDD (it's also working as a NAS), but with the powered hub things aren't any better. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876737] Re: GRUB refuses to boot a 32-bit kernel when in EFI mode
NB: In Debian testing (11) my Ryzen 3600 system boots and runs a 32-bit image okay. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876737 Title: GRUB refuses to boot a 32-bit kernel when in EFI mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1876737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876737] Re: GRUB refuses to boot a 32-bit kernel when in EFI mode
As discussed I suppose you can either use an older version of GRUB-EFI (which as pointed out may cause unknown problems), or perhaps you can boot in CSM mode? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876737 Title: GRUB refuses to boot a 32-bit kernel when in EFI mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1876737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876737] Re: GRUB refuses to boot a 32-bit kernel when in EFI mode
Okay then, I guess I won't report. 32-bit x86 is going away for a lot of distros so I doubt the kernel people will have any interest in doing it tbh. Glad I'm moving my Debian live disk away from doing this then if it breaks lots of stuff :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876737 Title: GRUB refuses to boot a 32-bit kernel when in EFI mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1876737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876737] Re: GRUB refuses to boot a 32-bit kernel when in EFI mode
Alkis, Do you want me to file this for RedHat, or are you/have you already done so? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876737 Title: GRUB refuses to boot a 32-bit kernel when in EFI mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1876737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876737] Re: GRUB refuses to boot a 32-bit kernel when in EFI mode
I feel like this is maybe missing the point. These things seem clear to me: 1. Loading 64-bit kernels on 32-bit UEFIs is a useful feature to have and I'm glad it was added. 2. AFAICT, the patch was not intended to break loading 32-bit kernels on 64-bit systems (and also what would be the point of such a change?), but if it was, I don't understand the reasoning behind doing this. 3. Of course booting a 64-bit kernel would work, but why should we be pushing updates that break existing installations due to what seems to be either an unintended consequence, or a "computer says no" type error even though the kernel is perfectly capable of booting. The error is misleading at best. As such, I feel like this issue still needs to be fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876737 Title: GRUB refuses to boot a 32-bit kernel when in EFI mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1876737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876737] Re: GRUB refuses to boot a 32-bit kernel when in EFI mode
That might be unrelated, unless they use Ubuntu grub packages/patches? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876737 Title: GRUB refuses to boot a 32-bit kernel when in EFI mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1876737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876737] Re: GRUB refuses to boot a 32-bit kernel when in EFI mode
Yes, it'd be good to see this fixed, even if it's not an official fix. I care more if it's affecting schools rather than just me with my weird setup. For what it's worth, Debian Buster's packages don't seem to exhibit these issues - could install those and lock the version perhaps? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876737 Title: GRUB refuses to boot a 32-bit kernel when in EFI mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1876737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876737] Re: GRUB refuses to boot a 32-bit kernel when in EFI mode
Thanks for letting me know. I'm not sure why that change is there either, but I guess there must be a reason. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876737 Title: GRUB refuses to boot a 32-bit kernel when in EFI mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1876737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876737] [NEW] GRUB refuses to boot a 32-bit kernel when in EFI mode
Public bug reported: Also reported at https://savannah.gnu.org/bugs/index.php?58300, but doesn't occur in Debian's v2.04 from Bulleye, and only occurred in the last few months, so it might be an Ubuntu bug. This is grub version 2.02-2ubuntu8.15 as reported by "apt show grub-efi" GRUB2 fails to boot a 32-bit kernel when started in EFI mode (64-bit EFI) on a 64-bit x86 CPU, and gives the message: "error: kernel doesn't support 64-bit CPUs" However, when a bios grub image made by the same version of grub is used, with the same kernel, on the same CPU, everything is normal and the kernel boots as expected. Hence, I know this kernel will boot on a 64-bit CPU, and with a previous version of GRUB 2 (unfortunately I don't know which version), it also booted fine in 64-bit mode using GRUB-EFI. Running with debug=all doesn't seem to provide any extra useful information, as far as I can tell - it just lists sectors being read and then freed. Any ideas as to what's going on? ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Description changed: Also reported at https://savannah.gnu.org/bugs/index.php?58300, but doesn't occur in Debian's v2.04 from Bulleye, and only occurred in the last few months, so it might be an Ubuntu bug. + + This is grub version 2.02-2ubuntu8.15 as reported by "apt show grub-efi" GRUB2 fails to boot a 32-bit kernel when started in EFI mode (64-bit EFI) on a 64-bit x86 CPU, and gives the message: "error: kernel doesn't support 64-bit CPUs" However, when a bios grub image made by the same version of grub is used, with the same kernel, on the same CPU, everything is normal and the kernel boots as expected. Hence, I know this kernel will boot on a 64-bit CPU, and with a previous version of GRUB 2 (unfortunately I don't know which version), it also booted fine in 64-bit mode using GRUB-EFI. Running with debug=all doesn't seem to provide any extra useful information, as far as I can tell - it just lists sectors being read and then freed. Any ideas as to what's going on? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876737 Title: GRUB refuses to boot a 32-bit kernel when in EFI mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1876737/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705064] Re: lshw doesn't have logicalname, serial number, or size for nvme device
Regardless, it'd be great for this to make it into the LTS release, but I don't know how to make that happen. It might also be too late, but I hope not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705064 Title: lshw doesn't have logicalname, serial number, or size for nvme device To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1705064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705064] Re: lshw doesn't have logicalname, serial number, or size for nvme device
Don't know if someone should mark as fix committed in this case, seeing as there are fixes out there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705064 Title: lshw doesn't have logicalname, serial number, or size for nvme device To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1705064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705064] Re: lshw doesn't have logicalname, serial number, or size for nvme device
Also works for me. In my case, I ran the binary on Ubuntu 18.04 because that's what my real hardware is using. If we can get this into Focal, that'd be great, but I wonder if we can backport into previous releases as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705064 Title: lshw doesn't have logicalname, serial number, or size for nvme device To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1705064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705064] Re: lshw doesn't have logicalname, serial number, or size for nvme device
Note that Fedora has patches in https://koji.fedoraproject.org/koji/buildinfo?buildID=1329140 that fix the NVME issue - maybe these could be used in the Ubuntu package builds too? I tried building lshw from the master branch, including the above fix (comment #1), but it didn't work. However, I can confirm the patched Fedora version works. I would be happy to help with fixing this as this problem has been a thorn in my side for a while. Hamish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705064 Title: lshw doesn't have logicalname, serial number, or size for nvme device To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1705064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851674] Re: All deb packages as being listed as "Proprietary" when opened in gnome-software
Doesn't appear to have been looked at yet, but still a longstanding issue ** Changed in: gnome-software (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851674 Title: All deb packages as being listed as "Proprietary" when opened in gnome-software To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1851674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851674] Re: All deb packages as being listed as "Proprietary" when opened in gnome-software
Possibly linked to this bug? https://bugs.launchpad.net/ubuntu/+source /gnome-software/+bug/1778607 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851674 Title: All deb packages as being listed as "Proprietary" when opened in gnome-software To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1851674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851674] Re: All deb packages as being listed as "Proprietary" when opened in gnome-software
Note that the output was from an Ubuntu 18.04 VM. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851674 Title: All deb packages as being listed as "Proprietary" when opened in gnome-software To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1851674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851674] Re: All deb packages as being listed as "Proprietary" when opened in gnome-software
Attached is the output from that command. ** Attachment added: "Output from jounralctl -b 0 on affected system" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1851674/+attachment/5304835/+files/log.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851674 Title: All deb packages as being listed as "Proprietary" when opened in gnome-software To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1851674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851674] Re: All deb packages as being listed as "Proprietary" when opened in gnome-software
** Description changed: It seems all open-source packages, including for example the official package for lshw (https://packages.ubuntu.com/disco/lshw) seem to be listed as "Proprietary" in gnome-software/Ubuntu Software. This seems to - happen from Ubuntu 18.04, with official and 3rd party packages (like - those from virtualbox.org). + happen in Ubuntu 18.04 and newer, with official and 3rd party packages + (like those from virtualbox.org). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851674 Title: All deb packages as being listed as "Proprietary" when opened in gnome-software To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1851674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851674] [NEW] All deb packages as being listed as "Proprietary" when opened in gnome-software
Public bug reported: It seems all open-source packages, including for example the official package for lshw (https://packages.ubuntu.com/disco/lshw) seem to be listed as "Proprietary" in gnome-software/Ubuntu Software. This seems to happen from Ubuntu 18.04, with official and 3rd party packages (like those from virtualbox.org). ** Affects: gnome-software (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/1851674 Title: All deb packages as being listed as "Proprietary" when opened in gnome-software To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1851674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781924] Re: Kernel wrong temperature reporting
Also affects my brand new Thinkpad X1 Extreme Gen 2. The errors pop up when the CPU is stone cold (i.e. upon waking after an overnight sleep in temps <10C) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781924 Title: Kernel wrong temperature reporting To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1781924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847540] Re: Kernel panic in 5.3.0-13-generic on Thinkpad X1-Extreme-Gen2
*** This bug is a duplicate of bug 1845454 *** https://bugs.launchpad.net/bugs/1845454 ** This bug has been marked a duplicate of bug 1845454 Kernel panic in tpm_ functions when booting kernel 5.3 in Ubuntu 19.10 (but 5.2 works) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847540 Title: Kernel panic in 5.3.0-13-generic on Thinkpad X1-Extreme-Gen2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845454] Re: Kernel panic in tpm_ functions when booting kernel 5.3 in Ubuntu 19.10 (but 5.2 works)
Fixed on my Thinkpad X1 Extreme Gen 2 with 5.3.0-18. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845454 Title: Kernel panic in tpm_ functions when booting kernel 5.3 in Ubuntu 19.10 (but 5.2 works) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847540] Re: Kernel panic in 5.3.0-13-generic on Thinkpad X1-Extreme-Gen2
Have replicated issue on other distros with 5.2 or 5.3 kernels. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847540 Title: Kernel panic in 5.3.0-13-generic on Thinkpad X1-Extreme-Gen2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847540] Re: Kernel panic in 5.3.0-13-generic on Thinkpad X1-Extreme-Gen2
Apport was generated after booting the system with the previous kernel, which works, but does not see my internal WiFi adapter ** 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/1847540 Title: Kernel panic in 5.3.0-13-generic on Thinkpad X1-Extreme-Gen2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847540] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1847540/+attachment/5296135/+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/1847540 Title: Kernel panic in 5.3.0-13-generic on Thinkpad X1-Extreme-Gen2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847540] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1847540/+attachment/5296136/+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/1847540 Title: Kernel panic in 5.3.0-13-generic on Thinkpad X1-Extreme-Gen2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847540] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1847540/+attachment/5296133/+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/1847540 Title: Kernel panic in 5.3.0-13-generic on Thinkpad X1-Extreme-Gen2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847540] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1847540/+attachment/5296134/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847540 Title: Kernel panic in 5.3.0-13-generic on Thinkpad X1-Extreme-Gen2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847540] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1847540/+attachment/5296130/+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/1847540 Title: Kernel panic in 5.3.0-13-generic on Thinkpad X1-Extreme-Gen2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847540] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1847540/+attachment/5296129/+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/1847540 Title: Kernel panic in 5.3.0-13-generic on Thinkpad X1-Extreme-Gen2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847540] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1847540/+attachment/5296127/+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/1847540 Title: Kernel panic in 5.3.0-13-generic on Thinkpad X1-Extreme-Gen2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847540] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1847540/+attachment/5296125/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847540 Title: Kernel panic in 5.3.0-13-generic on Thinkpad X1-Extreme-Gen2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847540] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1847540/+attachment/5296123/+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/1847540 Title: Kernel panic in 5.3.0-13-generic on Thinkpad X1-Extreme-Gen2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847540] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1847540/+attachment/5296132/+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/1847540 Title: Kernel panic in 5.3.0-13-generic on Thinkpad X1-Extreme-Gen2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847540] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1847540/+attachment/5296131/+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/1847540 Title: Kernel panic in 5.3.0-13-generic on Thinkpad X1-Extreme-Gen2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847540] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1847540/+attachment/5296128/+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/1847540 Title: Kernel panic in 5.3.0-13-generic on Thinkpad X1-Extreme-Gen2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847540] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1847540/+attachment/5296126/+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/1847540 Title: Kernel panic in 5.3.0-13-generic on Thinkpad X1-Extreme-Gen2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847540] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1847540/+attachment/5296124/+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/1847540 Title: Kernel panic in 5.3.0-13-generic on Thinkpad X1-Extreme-Gen2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847540] Re: Kernel panic in 5.3.0-13-generic on Thinkpad X1-Extreme-Gen2
apport information ** Tags added: apport-collected ** Description changed: After updating an Ubuntu 19.04 installation (Brand new) a subsequent update to 19.10 results in a system that panics on boot Same panic occurs when attempting an install of 19.10 from current ISO via USB stick Kernel is 5.3.0-13-generic - Have photo of panic including Call trace. The Call trace ends up in - tpm_read_log_efi + Have photo of panic including Call trace. The Call trace ends up in tpm_read_log_efi + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu7 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: hamish 1740 F pulseaudio + /dev/snd/controlC0: hamish 1740 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 19.10 + InstallationDate: Installed on 2019-10-09 (0 days ago) + InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) + MachineType: LENOVO 20QVCTO1WW + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 + RelatedPackageVersions: + linux-restricted-modules-5.0.0-31-generic N/A + linux-backports-modules-5.0.0-31-generic N/A + linux-firmware1.183 + Tags: eoan + Uname: Linux 5.0.0-31-generic x86_64 + UpgradeStatus: Upgraded to eoan on 2019-10-09 (0 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 07/26/2019 + dmi.bios.vendor: LENOVO + dmi.bios.version: N2OET36W (1.23 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 20QVCTO1WW + dmi.board.vendor: LENOVO + dmi.board.version: SDK0J40697 WIN + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: None + dmi.modalias: dmi:bvnLENOVO:bvrN2OET36W(1.23):bd07/26/2019:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QVCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: + dmi.product.family: ThinkPad X1 Extreme 2nd + dmi.product.name: 20QVCTO1WW + dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd + dmi.product.version: ThinkPad X1 Extreme 2nd + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1847540/+attachment/5296122/+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/1847540 Title: Kernel panic in 5.3.0-13-generic on Thinkpad X1-Extreme-Gen2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847540] Re: Kernel panic in 5.3.0-13-generic on Thinkpad X1-Extreme-Gen2
** Attachment added: "Photo of Panic" https://bugs.launchpad.net/ubuntu/+bug/1847540/+attachment/5296078/+files/IMG_3510.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847540 Title: Kernel panic in 5.3.0-13-generic on Thinkpad X1-Extreme-Gen2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1847540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847540] [NEW] Kernel panic in 5.3.0-13-generic on Thinkpad X1-Extreme-Gen2
Public bug reported: After updating an Ubuntu 19.04 installation (Brand new) a subsequent update to 19.10 results in a system that panics on boot Same panic occurs when attempting an install of 19.10 from current ISO via USB stick Kernel is 5.3.0-13-generic Have photo of panic including Call trace. The Call trace ends up in tpm_read_log_efi ** Affects: 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/1847540 Title: Kernel panic in 5.3.0-13-generic on Thinkpad X1-Extreme-Gen2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1847540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844518] Re: Ubuntu 19:10 - Python 3 os.path.isfile not working as expected
Agreed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1844518 Title: Ubuntu 19:10 - Python 3 os.path.isfile not working as expected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1844518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844518] [NEW] Ubuntu 19:10 - Python 3 os.path.isfile not working as expected
Public bug reported:
When one runs "os.path.isfile("/vmlinuz")" or the same for
os.path.exists, False is returned. However, given the information at:
https://docs.python.org/3.8/library/os.path.html#os.path.isfile and
https://docs.python.org/3.7/library/os.path.html#os.path.isfile, True
should be returned for links as well.
"os.path.islink("/vmlinuz")" works as expected, so I'm not sure what's
going on here.
Any ideas? It could be my VM as it's been running 19.10 for a little
while now.
Hamish
** Affects: 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/1844518
Title:
Ubuntu 19:10 - Python 3 os.path.isfile not working as expected
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1844518/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839182] Re: Error: divie by zero
Similar error for me using the PPA and ubuntu-studio installer on Ubuntu 18.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839182 Title: Error: divie by zero To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-installer/+bug/1839182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1810124] Re: package grub-legacy-ec2 18.4-0ubuntu1~16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
home fibre connection is dmz box. has been progressively upgraded from about 11-04 release, no rebuilds so could just be accumulated cruft. On Tue, 19 Feb 2019 at 15:31, Dan Watkins wrote: > Hi Hamish, > > Do you know how grub-legacy-ec2 ended up on your system? What > environment is this system running in? > > > Thanks! > > ** Changed in: cloud-init (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1810124 > > Title: > package grub-legacy-ec2 18.4-0ubuntu1~16.04.2 failed to > install/upgrade: subprocess installed post-installation script > returned error exit status 1 > > Status in cloud-init package in Ubuntu: > Incomplete > > Bug description: > dunno anything special, just ran do-release-upgrade from 16.04 > > ProblemType: Package > DistroRelease: Ubuntu 16.04 > Package: grub-legacy-ec2 18.4-0ubuntu1~16.04.2 > ProcVersionSignature: Ubuntu 3.13.0-52.86-generic 3.13.11-ckt18 > Uname: Linux 3.13.0-52-generic x86_64 > ApportVersion: 2.20.1-0ubuntu2.18 > AptOrdering: >grub-legacy-ec2: Configure >ubuntu-server: Configure >NULL: ConfigurePending > Architecture: amd64 > Date: Sun Dec 30 23:11:59 2018 > ErrorMessage: subprocess installed post-installation script returned > error exit status 1 > InstallationDate: Installed on 2011-10-25 (2623 days ago) > InstallationMedia: Ubuntu-Server 11.04 "Natty Narwhal" - Release amd64 > (20110426) > PackageArchitecture: all > RelatedPackageVersions: >dpkg 1.18.4ubuntu1.5 >apt 1.2.29 > SourcePackage: cloud-init > Title: package grub-legacy-ec2 18.4-0ubuntu1~16.04.2 failed to > install/upgrade: subprocess installed post-installation script returned > error exit status 1 > UpgradeStatus: Upgraded to xenial on 2018-12-30 (0 days ago) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1810124/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810124 Title: package grub-legacy-ec2 18.4-0ubuntu1~16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1810124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821845] Re: fort77: no output to stdout or stderr
Downgrading to f2c version 20100827-2 from 16.04 does not help. Also to mention that the test program exits cleanly with exit code 0. Hamish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821845 Title: fort77: no output to stdout or stderr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fort77/+bug/1821845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821845] [NEW] fort77: no output to stdout or stderr
Public bug reported: Hi, Run time programs compiled with fort77 on xUbuntu 18.04 are failing for me on multiple amd64 machines, and I see others complaining on the forums but no bug filed yet. It seems to compile programs ok but when you run them anything written to stdout or stderr seems to end up in /dev/null. I suspect reading from stdin is also broken. This makes the package pretty much unusable. I tried the same version of fort77 (1.15-11) on Debian Stretch and all is working as expected there, so it's specific to Ubuntu. Also tested in Ubuntu 16.04 and it works there. I'd note that 18.04 uses a newer version of f2c than 16.04 and Debian Stretch; perhaps the trouble is there? On a hunch I tried exporting LANG=C as I'm usually in en_NZ.UTF-8, but no luck. see also someone else's report at https://askubuntu.com/questions/1074077/fort77-isnt-working program hello_world implicit none c character*32 text c text = 'Hello World' write (*,*) text write (6,*) 'hello stdout' write (0,*) 'hello stderr' c end thanks, Hamish ** Affects: fort77 (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/1821845 Title: fort77: no output to stdout or stderr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fort77/+bug/1821845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806060] Re: Newer versions of killall (Ubuntu 18.04+) fail when signal specified in capitals
Tested on my production system (Mint 19.1 aka Bionic), and the test script provided in the description is now 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/1806060 Title: Newer versions of killall (Ubuntu 18.04+) fail when signal specified in capitals To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/psmisc/+bug/1806060/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810124] [NEW] package grub-legacy-ec2 18.4-0ubuntu1~16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: dunno anything special, just ran do-release-upgrade from 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: grub-legacy-ec2 18.4-0ubuntu1~16.04.2 ProcVersionSignature: Ubuntu 3.13.0-52.86-generic 3.13.11-ckt18 Uname: Linux 3.13.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: grub-legacy-ec2: Configure ubuntu-server: Configure NULL: ConfigurePending Architecture: amd64 Date: Sun Dec 30 23:11:59 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2011-10-25 (2623 days ago) InstallationMedia: Ubuntu-Server 11.04 "Natty Narwhal" - Release amd64 (20110426) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29 SourcePackage: cloud-init Title: package grub-legacy-ec2 18.4-0ubuntu1~16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2018-12-30 (0 days ago) ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810124 Title: package grub-legacy-ec2 18.4-0ubuntu1~16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1810124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806060] Re: Newer versions of killall (Ubuntu 18.04+) fail when signal specified in capitals
The script is passing in cosmic as well. Changing verification-needed-bionic and verification-needed-cosmic to verification-done-bionic and verification-done-cosmic. I'm leaving the original verification-needed tag for the moment, in case anyone else wants to test / extra testing is needed. ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806060 Title: Newer versions of killall (Ubuntu 18.04+) fail when signal specified in capitals To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/psmisc/+bug/1806060/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806060] Re: Newer versions of killall (Ubuntu 18.04+) fail when signal specified in capitals
Noted that the lower-case version is not equivalent. Just tested, and working in bionic - the script in the description works successfully for all options. Now testing in cosmic. ** 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/1806060 Title: Newer versions of killall (Ubuntu 18.04+) fail when signal specified in capitals To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/psmisc/+bug/1806060/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806060] Re: Newer versions of killall (Ubuntu 18.04+) fail when signal specified in capitals
Link to the bug: https://gitlab.com/psmisc/psmisc/issues/13 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806060 Title: Newer versions of killall (Ubuntu 18.04+) fail when signal specified in capitals To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/psmisc/+bug/1806060/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806060] Re: Newer versions of killall (Ubuntu 18.04+) fail when signal specified in capitals
Looks like this was fixed in v23.2, despite the misleading title of the bug. I will also notify the Fedora team now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806060 Title: Newer versions of killall (Ubuntu 18.04+) fail when signal specified in capitals To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/psmisc/+bug/1806060/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806060] Re: Newer versions of killall (Ubuntu 18.04+) fail when signal specified in capitals
Note: Looks like this is present in Fedora as well, do I need to report this upstream somehow as well? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806060 Title: Newer versions of killall (Ubuntu 18.04+) fail when signal specified in capitals To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/psmisc/+bug/1806060/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806060] [NEW] Newer versions of killall (Ubuntu 18.04+) fail when signal specified in capitals
Public bug reported: Newer versions of killall (Ubuntu 18.04+) display usage when the signal is passed like: killall -INT and instead require it to be passed as: killall -int In previous versions from Ubuntu 14.04 and 16.04, this doesn't happen. Is this a bug or a feature change? If so perhaps it should be noted in the usage information? The man page suggests capitals with "-SIGNAL". but that doesn't work any more. Hamish ** Affects: psmisc (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/1806060 Title: Newer versions of killall (Ubuntu 18.04+) fail when signal specified in capitals To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/psmisc/+bug/1806060/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 409739] Re: Support http_proxy
Any chance that this will be supported? At least for S3? I'm using duplicity directly, not deja-dup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/409739 Title: Support http_proxy To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/409739/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1762961] Re: Screen corruption
I wasn't getting any colour glitches, just sections of th screen that weren't getting updated, might be a different bug On Wed, 22 Aug 2018, 21:31 anarcho, <1762...@bugs.launchpad.net> wrote: > Hello Hamish, > Besides XRender what other configurations do you have in the Compositor or > otherwise. > I am experiencing green and red static over desktop icons and sometimes > screen fracturing/tearing of the wallpaper. > > Kubuntu 18.04 Precision 5520 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1762961 > > Title: > Screen corruption > > Status in xorg package in Ubuntu: > New > > Bug description: > By default, kubuntu uses the OpenGL for the rendering backend (2.0 or > 3.1) when it was in these modes, it'd show forms of screen corruption > > for example a loading bar might flicker between a longer and a shorter > bar > or a combo box would seemingly not respond, and then suddenly do > something unexpected > text entered would vanish then reappear > > ProblemType: Bug > DistroRelease: Ubuntu 17.10 > Package: xorg 1:7.7+19ubuntu3 > ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 > Uname: Linux 4.13.0-21-generic x86_64 > ApportVersion: 2.20.7-0ubuntu3.7 > Architecture: amd64 > CasperVersion: 1.387 > CompositorRunning: None > Date: Wed Apr 11 18:40:36 2018 > DistUpgraded: Fresh install > DistroCodename: artful > DistroVariant: ubuntu > DkmsStatus: >bbswitch, 0.8, 4.13.0-21-generic, x86_64: installed >nvidia-384, 384.111, 4.13.0-21-generic, x86_64: installed > ExtraDebuggingInterest: No > GraphicsCard: >Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA > controller]) > Subsystem: Dell Device [1028:07bf] > Subsystem: Dell GM107GLM [Quadro M1200 Mobile] [1028:07bf] > LiveMediaBuild: Kubuntu 17.10 "Artful Aardvark" - Release amd64 > (20180105.2) > MachineType: Dell Inc. Precision 5520 > ProcEnviron: >LANGUAGE= >TERM=xterm-256color >PATH=(custom, no user) >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi > file=/cdrom/preseed/hostname.seed boot=casper maybe-ubiquity quiet splash > --- > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 08/30/2017 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: 1.5.0 > dmi.board.name: 0R6JFH > dmi.board.vendor: Dell Inc. > dmi.board.version: A00 > dmi.chassis.type: 10 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: > dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr: > dmi.product.family: Precision > dmi.product.name: Precision 5520 > dmi.sys.vendor: Dell Inc. > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.83-1 > version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 > version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 > version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20170309-0ubuntu1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1762961/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762961 Title: Screen corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1762961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762988] [NEW] Ubiquity crashes at the bootloader installation phase
Public bug reported: Partition setup was a luks partition with an existing home directory, which I'd unlocked prior to starting ubiquity (otherwise it wouldn't even find the partition) Bootloader install partition was an efi system partition This section of syslog looks relevant, looks like it couldn't handle the encrypted disk Apr 11 10:02:32 kubuntu ubiquity: grub-install: error: attempt to install to encrypted disk without cryptodisk enabled. Set `GRUB_ENABLE_CRYPTODISK=y' in file `/etc/default/grub'. Apr 11 10:02:32 kubuntu ubiquity: dpkg: error processing package shim-signed (--configure): Apr 11 10:02:32 kubuntu ubiquity: subprocess installed post-installation script returned error exit status 1 Apr 11 10:02:32 kubuntu ubiquity: Setting up grub-efi-amd64-signed (1.85.3+2.02~beta3-4ubuntu7.3) ... Apr 11 10:02:32 kubuntu ubiquity: Installing for x86_64-efi platform. Apr 11 10:02:33 kubuntu ubiquity: File descriptor 4 (/dev/nvme0n1p1) leaked on vgs invocation. Parent PID 4675: grub-install Apr 11 10:02:33 kubuntu ubiquity: File descriptor 4 (/dev/nvme0n1p1) leaked on vgs invocation. Parent PID 4675: grub-install Apr 11 10:02:33 kubuntu ubiquity: grub-install: error: attempt to install to encrypted disk without cryptodisk enabled. Set `GRUB_ENABLE_CRYPTODISK=y' in file `/etc/default/grub'. Also this bit might be useful as well updates/main amd64 linux-headers-generic amd64 4.13.0.38.41 [2290 B] Apr 11 10:03:08 kubuntu /plugininstall.py: Exception during installation: Apr 11 10:03:08 kubuntu /plugininstall.py: Traceback (most recent call last): Apr 11 10:03:08 kubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 1721, in Apr 11 10:03:08 kubuntu /plugininstall.py: install.run() Apr 11 10:03:08 kubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 61, in wrapper Apr 11 10:03:08 kubuntu /plugininstall.py: func(self) Apr 11 10:03:08 kubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 227, in run Apr 11 10:03:08 kubuntu /plugininstall.py: self.configure_bootloader() Apr 11 10:03:08 kubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 971, in configure_bootloader Apr 11 10:03:08 kubuntu /plugininstall.py: "GrubInstaller failed with code %d" % ret) Apr 11 10:03:08 kubuntu /plugininstall.py: ubiquity.install_misc.InstallStepError: GrubInstaller failed with code 141 Apr 11 10:03:08 kubuntu /plugininstall.py: Apr 11 10:03:08 kubuntu ubiquity: umount: /target: target is busy. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubiquity 17.10.10 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CasperVersion: 1.387 Date: Wed Apr 11 20:06:47 2018 LiveMediaBuild: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.2) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash 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/1762988 Title: Ubiquity crashes at the bootloader installation phase To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1762988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762978] [NEW] ksmserver-logout-greeter crashes on logout preventing me from logging out
Public bug reported: Running on the live-usb version of kubuntu 17.10.1 on a dell precision 5520 Application: ksmserver-logout-greeter (ksmserver-logout-greeter), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3ac23d1000 (LWP 11971))] Thread 3 (Thread 0x7f3aa35e1700 (LWP 11974)): #0 0x7f3abdc8706d in __GI___libc_read (fd=7, buf=0x7f3aa35e0a20, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:26 #1 0x7f3ab3ae7073 in ?? () from /usr/lib/nvidia-384/tls/libnvidia-tls.so.384.111 #2 0x7f3ab6b04280 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3ab6abfc4b in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f3ab6ac0110 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f3ab6ac027c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f3abe5cb49b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f3abe570e3a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f3abe3903ca in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f3abf1aee45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #10 0x7f3abe39529d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f3ab88457fc in start_thread (arg=0x7f3aa35e1700) at pthread_create.c:465 #12 0x7f3abdc97b5f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f3aa8c79700 (LWP 11973)): #0 0x7f3abdc8b951 in __GI___poll (fds=0x7f3a9c004e60, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f3ab6ac0169 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f3ab6ac027c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f3abe5cb49b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f3abe570e3a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f3abe3903ca in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f3ac05ebf45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f3abe39529d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f3ab88457fc in start_thread (arg=0x7f3aa8c79700) at pthread_create.c:465 #9 0x7f3abdc97b5f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f3ac23d1000 (LWP 11971)): [KCrash Handler] #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #5 0x7f3abdbbbf5d in __GI_abort () at abort.c:90 #6 0x7f3abe380107 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f3ac0cb8787 in QSGRenderLoop::handleContextCreationFailure(QQuickWindow*, bool) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7f3ac0cb9755 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x7f3ac0cba37a in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x7f3abeb3dd35 in QWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #11 0x7f3ac0d2dd05 in QQuickWindow::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #12 0x55c454797fd1 in ?? () #13 0x7f3abf77b46c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7f3abf782d34 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7f3abe572de8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7f3abeb32e5f in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #17 0x7f3abeb33a9d in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #18 0x7f3abeb0bcab in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #19 0x7f3aaccbb5a0 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #20 0x7f3ab6abffb7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x7f3ab6ac01f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x7f3ab6ac027c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x7f3abe5cb47f in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7f3abe570e3a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7f3abe579da4 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #26 0x55c454795122 in ?? () #27
[Bug 1762961] [NEW] Screen corruption
Public bug reported: By default, kubuntu uses the OpenGL for the rendering backend (2.0 or 3.1) when it was in these modes, it'd show forms of screen corruption for example a loading bar might flicker between a longer and a shorter bar or a combo box would seemingly not respond, and then suddenly do something unexpected text entered would vanish then reappear ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CasperVersion: 1.387 CompositorRunning: None Date: Wed Apr 11 18:40:36 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-21-generic, x86_64: installed nvidia-384, 384.111, 4.13.0-21-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell GM107GLM [Quadro M1200 Mobile] [1028:07bf] LiveMediaBuild: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.2) MachineType: Dell Inc. Precision 5520 ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/hostname.seed boot=casper maybe-ubiquity quiet splash --- SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/30/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0R6JFH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful resolution ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762961 Title: Screen corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1762961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762961] Re: Screen corruption
When I switched it to XRender the corruption completely stopped -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762961 Title: Screen corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1762961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749580] Re: Weird behaviour with hybrid MBRs
** Package changed: lshw (Ubuntu) => lshw -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749580 Title: Weird behaviour with hybrid MBRs To manage notifications about this bug go to: https://bugs.launchpad.net/lshw/+bug/1749580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751524] [NEW] Installing bionic on WSL using do-release-upgrade -d,
Public bug reported: subprocess installed post-installation script returned error exit status 1 dmesg: read kernel buffer failed: Function not implemented ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd 237-3ubuntu3 ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35 Uname: Linux 4.4.0-43-Microsoft x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Function not implemented Date: Sun Feb 25 10:37:10 2018 Dmesg: ErrorMessage: subprocess installed post-installation script returned error exit status 1 Lsusb: Error: command ['lsusb'] failed with exit code 1: ProcInterrupts: ProcKernelCmdLine: BOOT_IMAGE=/kernel init=/init ro ProcModules: Error: command ['sort', '/proc/modules'] failed with exit code 2: sort: cannot read: /proc/modules: No such file or directory RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/systemd-fsck@.service → /lib/systemd/system/systemd-fsck@.service.d/cloud-init.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. Title: package systemd 237-3ubuntu3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2018-02-24 (0 days ago) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check third-party-packages uec-images xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751524 Title: Installing bionic on WSL using do-release-upgrade -d, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1751524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749580] [NEW] Weird behaviour with hybrid MBRs
Public bug reported: Occurs with: B.02.17 on Ubuntu 16.04, and also other versions (don't know which exactly, but affects every version I've tried this on over the years). Seems to affect the lshw program on other Linux distros too. I tried reporting on https://www.ezix.org/project/wiki/HardwareLiSter, but it didn't seem to work. Description: If there is a hybrid MBR present as well as a GPT, lshw reads the hybrid MBR instead of the GPT. I find this odd, given that lshw can read and understand GPT disks just fine. Expected to happen: lshw reports full disk partition information using the GPT, even when there's a hybrid MBR present on the disk. What actually happens: lshw reports partial/potentially incorrect information using the hybrid MBR, if one exists, even though there's a GPT will full information as well. Do I need to provide any further information? Hamish ** Affects: lshw (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/1749580 Title: Weird behaviour with hybrid MBRs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lshw/+bug/1749580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1743165] Re: Boot up sometimes doesn't work
Hi Christopher Thank you for getting back to me. I am sorry for taking up your time because I now think this problem may have been due to a faulty hard drive. Since I replaced that drive with a much newer 1Tb drive about a month ago, reinstalling Ubuntu, this problem has not recurred. May I take this opportunity to say how impressed I am with Ubuntu. I have a relatively old HP pc which had been running pretty well with Windows 10 - until a huge Microsoft automatic "upgrade" in December basically rendered my pc useless. I had their online remote diagnostics and supervised reinstallation of Windows, but all to no avail. It just kept crashing. Now I am back up and running with Ubuntu. Everything works and it is stable Thank you to you and all the Ubuntu community. Best wishes Hamish On 06/02/18 21:21, Christopher M. Penalver wrote: > Hamish Birchall, thank you for reporting this and helping make Ubuntu > better. > > 1) Did this start to happen after an update? > > 2) Could you please capture the details of a failed boot following > https://wiki.ubuntu.com/DebuggingKernelBoot ? > > ** Tags added: bios-outdated-5.63 > > ** Changed in: xorg (Ubuntu) > Importance: Undecided => Low > > ** Changed in: xorg (Ubuntu) > Status: New => Incomplete > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743165 Title: Boot up sometimes doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1743165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743165] [NEW] Boot up sometimes doesn't work
Public bug reported: I'm hoping it is included in the xorg report. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-108.131-generic 4.4.98 Uname: Linux 4.4.0-108-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.135 Tue Jan 17 15:26:26 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Jan 13 19:21:17 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company C61 [GeForce 6150SE nForce 430] [103c:2a72] InstallationDate: Installed on 2018-01-05 (8 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Hewlett-Packard HP Compaq dx2450 Microtower PC ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-108-generic root=UUID=5397355c-057e-45d8-a2f2-9565b5978588 ro recovery nomodeset SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/03/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 5.19 dmi.board.name: 2A72h dmi.board.vendor: OEM_MB dmi.board.version: 3.02 dmi.chassis.asset.tag: CZC8486RC1 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.19:bd11/03/2008:svnHewlett-Packard:pnHPCompaqdx2450MicrotowerPC:pvr:rvnOEM_MB:rn2A72h:rvr3.02:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.name: HP Compaq dx2450 Microtower PC dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Jan 13 14:35:29 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Keyboard KEYBOARD, id 8 inputMicrosoft Microsoft 3-Button Mouse with IntelliEye(TM) MOUSE, id 9 xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2~16.04.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743165 Title: Boot up sometimes doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1743165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656523] [NEW] LUbuntu Installer crashes on Asus TP200SA
Public bug reported: First I tried installing Lightweight Ubuntu on my new Asus Transformer TP200SA (2G RAM, 32G eMMC) with the encrypted disk + LVM option - that failed initially because I had not invoked "sudo swapoff -a" from a terminal, and then because of some other reason that I didn't understand. I then tried just LVM, but that failed. I then tried a vanilla installation, and after I'd confirmed I wanted UEFI rather than BIOS compatibility mode (I was overwriting Windows 10), the installer started copying files, so I had some lunch. When I came back I found that the installer had crashed and the bug reporter got invoked, which brought me to this page. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: ubiquity 16.10.14 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CasperVersion: 1.379 Date: Sat Jan 14 12:34:31 2017 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/lubuntu.seed boot=casper quiet splash --- LiveMediaBuild: Lubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lubuntu ubiquity-16.10.14 yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656523 Title: LUbuntu Installer crashes on Asus TP200SA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1656523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1275076] Re: pkexec cannot be used in Unity!
** Changed in: unity Status: Incomplete => Invalid ** Changed in: unity (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1275076 Title: pkexec cannot be used in Unity! To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1275076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1275076] Re: pkexec cannot be used in Unity!
No this doesn't seem to happen any more in 12.04, and I recall it working correctly with 14.04 and onwards. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1275076 Title: pkexec cannot be used in Unity! To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1275076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 701351] Re: grub-install fails to install on a raid1 array
For the record, grub-install doesn't work even if you set the target as the raw /dev/sda. Same error message. (lucid 10.04 LTS server, md raid1 metadata ver 1.2, grub 1.98-1ubuntu13) thanks, Hamish ** Changed in: grub2 (Ubuntu) Status: Invalid = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/701351 Title: grub-install fails to install on a raid1 array To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/701351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1377878] Re: PPC - GUI freezes except for mouse pointer
I'm a total novice but I have encountered these issues and for what it's worth these are the machine specs and solutions that I have used... Hardware: Mac Mini PPC G4 (PowerPC 7447A @ 1250.00MHz) Radeon 9200 When running: Lubuntu 14.04.1 With: video=radeonfb: 1024x768-32@60 Result: running fine (no freeze) but with sluggish GUI i.e. slow window drag When running: Lubuntu 14.10 With: video=radeonfb: 1024x768-32@60 Result: sluggish window drag and now freezing issue with only mouse cursor movement With: video=ofonly radeon.agpmode=-1 Result: sluggish window drag but no more freezing issue I haven't tried anything xorg.conf related as I consider this system currently in a usable state. I did go through the motions of the xorg.conf stuff under 14.04.1 but didn't changed anything as I have no idea what I would change. As I said, total novice. I would be happy to try something and report the results if someone would give me some direction. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1377878 Title: PPC - GUI freezes except for mouse pointer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1377878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1393755] Re: openshot segfaults
Sorry, but I don't have the knowledge to help you any further. I'm not sure about open shot 2 either, as it's now a year behind, and even though I was going to help develop it, it was never in a good enough state for me to build it, and there's been no activity for a few months, unfortunately. Hopefully, this'll get noticed by someone with greater knowledge fairly soon. Sorry I can't help any more, Hamish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1393755 Title: openshot segfaults To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openshot/+bug/1393755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1393755] Re: openshot segfaults
This is a wierd one... It seems you upgraded to trusty (14.04) via precise (12.04), which may mean there is some crud left over on your system that is causing this problem, although it's hard to say. This might not get fixed, because of the new openshot 2.0 coming up (hopefully) soon, so hopefully, since that will have been reweritten, this bug will no longer apply in future. Were you running any other program at the same time? Thanks, Hamish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1393755 Title: openshot segfaults To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openshot/+bug/1393755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
