[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 a snap

Status in apparmor package in Ubuntu:
  Confirmed
Status in evince package in Ubuntu:
  Triaged
Status in apparmor source package in Jammy:
  Confirmed
Status in evince source package in Jammy:
  Confirmed
Status in evince package in Debian:
  New

Bug description:
  [Impact]

   * Users cannot open a hyperlink in a PDF opened with evince when the default 
browser is a snap.
   * The fix creates a snap_browsers abstraction on AppArmor which can be used 
in a transition for when the browser is executed. The snap_browsers abstraction 
provides the minimal amount of permissions required to execute a browser 
provided through snaps. This is a workaround since AppArmor currently does not 
provide mediation/filtering on enhanced environment variables.

  [Test Plan]

   * Make sure the default browser is provided through the snap store.
   * Open a PDF that contains a hyperlink using evince and click on the URL.
   * The browser should open the requested URL. 

  [Where problems could occur]

   * If the browser or snap core update to have new requirements for
  opening a browser, then the current policy could become obsolete and
  will need to be updated again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[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 said by @aldebx on there). This was a
LVM set-up with an encrypted swap, which may explain the bug.

My workaround, form the root login of the recovery mode was the following 
1. comment out the RESUME line in /etc/initramfs-tools/conf.d/resume 
2. rebuild the initramfs with update-initramfs -u
3. mount the /boot partiton to actually put the initramfs on the correct place

Now the systems boots again, but this problem shouldn’t have happened in
the first place.

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bionic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1771000

Title:
  do-release-upgrade on a server with encrypted swap does not boot

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  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 said by @aldebx on there).
  This was a LVM set-up with an encrypted swap, which may explain the
  bug.

  My workaround, form the root login of the recovery mode was the following 
  1. comment out the RESUME line in /etc/initramfs-tools/conf.d/resume 
  2. rebuild the initramfs with update-initramfs -u
  3. mount the /boot partiton to actually put the initramfs on the correct place

  Now the systems boots again, but this problem shouldn’t have happened
  in the first place.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1771000/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[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 is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1574333

Title:
  LVM-based filesystem does not boot with kernel 4.4 (but works with
  4.2)

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  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 with the
  following text :

   lvmetad is not active yet, using direct activation during sysinit
  Scannig for Btrfs flesystems
  _

  Actually my set-up is lvm based, and the correponding lines of the
  output of a mount command are

  /dev/mapper/clio-root on / type btrfs 
(rw,relatime,nospace_cache,subvolid=256,subvol=/@)
  /dev/mapper/clio-root on /mnt/clio-root type btrfs 
(rw,relatime,nospace_cache,subvolid=5,subvol=/)
  /dev/mapper/clio-root on /home type btrfs 
(rw,relatime,nospace_cache,subvolid=257,subvol=/@home)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1574333/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[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 server does not boot with kernel 4.4 (but works with 4.2)

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  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 with the
  following text :

   lvmetad is not active yet, using direct activation during sysinit
  Scannig for Btrfs flesystems
  _

  Actually my set-up is lvm based, and the correponding lines of the
  output of a mount command are

  /dev/mapper/clio-root on / type btrfs 
(rw,relatime,nospace_cache,subvolid=256,subvol=/@)
  /dev/mapper/clio-root on /mnt/clio-root type btrfs 
(rw,relatime,nospace_cache,subvolid=5,subvol=/)
  /dev/mapper/clio-root on /home type btrfs 
(rw,relatime,nospace_cache,subvolid=257,subvol=/@home)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1574333/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[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 with the
following text :

 lvmetad is not active yet, using direct activation during sysinit
Scannig for Btrfs flesystems
_

Actually my set-up is lvm based, and the correponding lines of the
output of a mount command are

/dev/mapper/clio-root on / type btrfs 
(rw,relatime,nospace_cache,subvolid=256,subvol=/@)
/dev/mapper/clio-root on /mnt/clio-root type btrfs 
(rw,relatime,nospace_cache,subvolid=5,subvol=/)
/dev/mapper/clio-root on /home type btrfs 
(rw,relatime,nospace_cache,subvolid=257,subvol=/@home)

** Affects: lvm2 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: kernel

-- 
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 server does not boot with kernel 4.4 (but works with 4.2)

Status in lvm2 package in Ubuntu:
  New

Bug description:
  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 with the
  following text :

   lvmetad is not active yet, using direct activation during sysinit
  Scannig for Btrfs flesystems
  _

  Actually my set-up is lvm based, and the correponding lines of the
  output of a mount command are

  /dev/mapper/clio-root on / type btrfs 
(rw,relatime,nospace_cache,subvolid=256,subvol=/@)
  /dev/mapper/clio-root on /mnt/clio-root type btrfs 
(rw,relatime,nospace_cache,subvolid=5,subvol=/)
  /dev/mapper/clio-root on /home type btrfs 
(rw,relatime,nospace_cache,subvolid=257,subvol=/@home)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1574333/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp