[Touch-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap

2023-02-17 Thread Frédéric Grosshans
The bug still exist on Kinetic. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is

[Touch-packages] [Bug 1771000] [NEW] do-release-upgrade on a server with encrypted swap does not boot

2018-05-13 Thread Frédéric Grosshans
Public bug reported: I’ve upgraded a server to bionic beaver, and it couldn’t boot anymore. Using the “recovery boot” option hanged a long time with the message "waiting for resume device". Some googling lead be to the bug #206358, and I deduced that do-release- upgrade “messed with my swap” (as

[Touch-packages] [Bug 1574333] Re: LVM-based filesystem does not boot with kernel 4.4 (but works with 4.2)

2016-10-23 Thread Frédéric Grosshans
For 4.4.0-45, it only works in recovery mode, one hit on the return key + two confirmations to resume normal boot. Everything works fine withe the 4.8.0-26 kernel of Yaketty Yak (Ubuntu 16.10) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which

[Touch-packages] [Bug 1574333] Re: LVM-based server does not boot with kernel 4.4 (but works with 4.2)

2016-05-22 Thread Frédéric Grosshans
Update : It works now with 4.4.0-22, in recovery mode, and continuing the normal boot sequence. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1574333 Title: LVM-based

[Touch-packages] [Bug 1574333] [NEW] LVM-based server does not boot with kernel 4.4 (but works with 4.2)

2016-04-24 Thread Frédéric Grosshans
Public bug reported: I‘ve updated my home-made NAS from wily to xenial and it stopped booting. Selecting the 4.2 kernel on the grub menu makes it work again. The working kernel is 4.2.0-35-generic The failing kernel is 4.4.0-21-generic. When the booting sequence freezes, I can have a terminal