Hello Yancy, or anyone else affected,
Accepted quassel into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/quassel/1:0.14.0-1ubuntu0.22.04.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
This bug was fixed in the package quassel - 1:0.14.0-1ubuntu1
---
quassel (1:0.14.0-1ubuntu1) kinetic; urgency=medium
* d/usr.bin.quasselcore:
- Update apparmor profile to allow running in lxd (LP: #1814302)
-- Dave Jones Sun, 12 Jun 2022 20:52:19
+0100
** Changed in:
I've proposed the change to Debian: https://salsa.debian.org/sdeziel-
guest/quassel/-/merge_requests/1
--
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/1814302
Title:
I've sponsored/uploaded both the Jammy and Kinetic debdiffs. Kinetic is
accepted, jammy-proposed has to go through SRU.
Removing Sponsors as there is nothing more to sponsor here.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Patch added: "1-1814301-jammy.debdiff"
https://bugs.launchpad.net/ubuntu/jammy/+source/quassel/+bug/1814302/+attachment/5597063/+files/1-1814301-jammy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in
** Patch added: "1-1814301-kinetic.debdiff"
https://bugs.launchpad.net/ubuntu/jammy/+source/quassel/+bug/1814302/+attachment/5596890/+files/1-1814301-kinetic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Looks like this is back in jammy (and beyond); the sync from Debian
dropped the patch to d/usr.bin.quasselcore for lxd.
** Also affects: apparmor (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: quassel (Ubuntu Jammy)
Importance: Undecided
Status: New
**
This bug was fixed in the package quassel - 1:0.12.4-3ubuntu1.18.04.2
---
quassel (1:0.12.4-3ubuntu1.18.04.2) bionic; urgency=medium
* d/usr.bin.quasselcore:
- Update apparmor profile to allow running in lxd (LP: #1814302)
-- Dan Streetman Sun, 28 Jun 2020 11:01:19
-0400
This bug was fixed in the package quassel - 1:0.13.1-3ubuntu2.1
---
quassel (1:0.13.1-3ubuntu2.1) focal; urgency=medium
* d/usr.bin.quasselcore:
- Update apparmor profile to allow running in lxd (LP: #1814302)
-- Dan Streetman Sun, 28 Jun 2020 11:01:19
-0400
** Changed in:
bionic:
ubuntu@lp1814302-b:~$ systemd-detect-virt
lxc
ubuntu@lp1814302-b:~$ dpkg -l|grep quassel
ii quassel-core 1:0.12.4-3ubuntu1.18.04.1 amd64
distributed IRC client - core component
ubuntu@lp1814302-b:~$ /usr/bin/quasselcore
Segmentation fault
focal:
ubuntu@lp1814302-f:~$ systemd-detect-virt
lxc
ubuntu@lp1814302-f:~$ dpkg -l|grep quassel-core
ii quassel-core 1:0.13.1-3ubuntu2 amd64
distributed IRC client - core component
ubuntu@lp1814302-f:~$ /usr/bin/quasselcore
Segmentation fault
Hello Yancy, or anyone else affected,
Accepted quassel into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/quassel/1:0.13.1-3ubuntu2.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
This bug was fixed in the package quassel - 1:0.13.1-3ubuntu3
---
quassel (1:0.13.1-3ubuntu3) groovy; urgency=medium
*
d/p/lp1885436/0001-common-Disable-enum-type-stream-operators-for-Qt-5.1.patch,
d/p/lp1885436/0002-common-Always-let-QVariant-fromValue-deduce-the-type.patch,
** Description changed:
- Fresh install of Ubuntu 18.04. lxd installed from snap. Fresh 18.04
- container. Everything up todate via apt.
+ [impact]
+
+ quasselcore cannot start inside lxd container
+
+ [test case]
+
+ create lxd container, install quassel-core, check quasselcore service:
+
+
** Also affects: apparmor (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: quassel (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: apparmor (Ubuntu Groovy)
Importance: Undecided
Status: Confirmed
** Also affects: quassel (Ubuntu
The above workaround isn't enough to totally resolve the issues with
AppArmor and this application inside LXD. I also had to switch to aa-
complain for PostgreSQL migration so features will have to be thoroughly
tested to identify it. I'm willing to setup a secondary instance to do
any testing
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: quassel (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apparmor (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
** Also affects: apparmor
Importance: Undecided
Status: New
** Also affects: quassel (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
19 matches
Mail list logo
