[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 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 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 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 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 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
[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 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
[Bug 922196] Re: openshot cuts off the last second of video when exporting to bluray
Does this still occur in new versions of openshot and Ubuntu? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/922196 Title: openshot cuts off the last second of video when exporting to bluray To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openshot/+bug/922196/+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!
** Project changed: unity = unity (Ubuntu) -- 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/ubuntu/+source/unity/+bug/1275076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 543059] Re: openshot crashed with AttributeError in on_btnCancel_clicked()
Probably because 10.04 is out of support and no one's been able to reproduce it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/543059 Title: openshot crashed with AttributeError in on_btnCancel_clicked() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openshot/+bug/543059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1169691] Re: Update-manager progress bar doesn't fully reach the right
Additional information found: The progress bar moves as expect until dpkg starts processing triggers. Then the bar is completely still, therefore the progress bar for update-manager may have some code missing from it. This does not occour when performing operations with the Synaptic Package Manager. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1169691 Title: Update-manager progress bar doesn't fully reach the right To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1169691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1169691] Re: Update-manager progress bar doesn't fully reach the right
It may be helpful if an attempt to reproduce this was made. Even though this is unimportant, it makes Ubuntu look a little rough around the edges. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1169691 Title: Update-manager progress bar doesn't fully reach the right To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1169691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1169691] [NEW] Update-manager progress bar doesn't fully reach the right
Public bug reported: All updates apply successfully, but the progress bar doesn't reach the right. My ubuntu version is precsie, running on an emachines er1402 from 2011. Output of lsb_release -rd: Description:Ubuntu 12.04.2 LTS Release:12.04 Output of apt-cache policy update-manager: update-manager: Installed: 1:0.156.14.11 Candidate: 1:0.156.14.11 Version table: *** 1:0.156.14.11 0 500 http://gb.archive.ubuntu.com/ubuntu/ precise-updates/main i386 Packages 100 /var/lib/dpkg/status 1:0.156.14.5 0 500 http://security.ubuntu.com/ubuntu/ precise-security/main i386 Packages 1:0.156.14 0 500 http://gb.archive.ubuntu.com/ubuntu/ precise/main i386 Packages. What should happen is the progress indicator reaches the right on the last stage of setting up the package(s). ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: ui ** Tags added: ui -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1169691 Title: Update-manager progress bar doesn't fully reach the right To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1169691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
