Apparently, that's the fate of early adopters...
I've managed to "hand-craft" following apparmor profile and place it in:
/etc/apparmor.d/cri-containerd.apparmor.d as a temporary solution for
this problem.
** Attachment added: "Temporary working profile for apparmor"
Forgot to paste link to PR related to issue above :/
https://github.com/containerd/containerd/pull/10129
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065423
Title:
Update AppArmor template to
Public bug reported:
Is there any chance that this PR can be implemented to current Ubuntu
release?
Because as for now apparmor denies signals from runc and this results in
many pods kept in Terminating state:
audit: type=1400 audit(1715342953.323:200): apparmor="DENIED"
operation="signal"
That previous comment was false-positive, I was probably still booted to
6.5.0-26 and on 6.5.0-28 this bug is still present. After resume from
suspend in 6.5.0-28 keyboard is not-responsive.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
It seems that this is already fixed with 6.5.0-28-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062562
Title:
Keyboard not working after resume from suspend on Dell XPS 13 laptop
To
Maybe this is related with this: https://lore.kernel.org/linux-
input/20240126160724.13278-1-hdego...@redhat.com/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062562
Title:
Keyboard not working
Public bug reported:
After upgrade to 6.5.0-27-generic keyboard stopped working when laptop comes
back to life after suspend.
When booted with 6.5.0-26-generic everything is fine.
** Affects: linux-signed (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
Debian supplied version 3.20.1 of evince works fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1427974
Title:
Evince keyboard input fails
To manage notifications about this bug go to:
Ubuntu 16.04 with evince 3.18.2
Not able to change file name in save dialog - no keyboard input, no
keyboard shortcuts (copy & paste) - but mouse copy & paste works fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
From about a week back I get this annoying situation every time. After
start-up, no VPN connection secrets are visible to nm, need to remove
.gconf file, logout, login. Killing nm-applet after removing file does
not fix it, logout-login required.
--
You received this bug notification because you
Public bug reported:
Not sure that this is Ubuntu/Debian issue but after upgrading 14.04 to
14.10 (with new perl package 5.20) due to lack of these two files I
wasn't able to build for ex. Session::Token module from source.
Solution was simple:
sudo touch
I've recently upgraded my ubuntu to 14.10 and problem also occurred.
I've removed bumblebee and primus (just remove not purge) and it didn't help.
Downgrading ubuntu-drivers-common to 0.2.91.4 also failed.
But I've found out that my X.org is complaining about missing nvidia
module, and indeed
*** This bug is a duplicate of bug 1365695 ***
https://bugs.launchpad.net/bugs/1365695
Forcibly uninstalling installing of this package seems to fix my
missing alternatives to provide nvidia_drv.so
** Package changed: ubuntu-drivers-common (Ubuntu) = nvidia-graphics-
drivers-331 (Ubuntu)
*** This bug is a duplicate of bug 1365695 ***
https://bugs.launchpad.net/bugs/1365695
** Description changed:
- After upgrading to version 0.2.91.7 my X.org stopped working - it could
- not find nvidia drivers. Downgrading to 0.2.91.4 (from releease) fixes
- this problem.
+ During my update
.
Only difference between them is that working one contains a link:
nvidia-graphics-drivers.conf -
/etc/alternatives/x86_64-linux-gnu_nvidia_modconf
Also refering to your bug #1376966, file bumblebee.conf contains
blacklist entry for nvidia.
--
Sebastian Podjasek
--
You received this bug
After dropping to root in recovery mode please try to downgrade ubuntu-
drivers-common to release version:
apt-get install ubuntu-drivers-common=1:0.2.91.4
This might be related to my bug #1374871...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Log of working X.org after downgrade to 0.2.91.4
** Attachment added: Xorg.0.log.0.2.91.4.gz
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1374871/+attachment/4217725/+files/Xorg.0.log.0.2.91.4.gz
--
You received this bug notification because you are a member of
Public bug reported:
After upgrading to version 0.2.91.7 my X.org stopped working - it could
not find nvidia drivers. Downgrading to 0.2.91.4 (from releease) fixes
this problem.
** Affects: ubuntu-drivers-common (Ubuntu)
Importance: Undecided
Status: New
** Attachment added:
Public bug reported:
Could you please add support for this card reader, vendor=0x04e6,
product=0x5116 - patch below...
** Affects: gnupg (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Patch added: Patch to add SCR3310
https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/1076987/+attachment/3428768/+files/gnupg-scm.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1076987
After some investigation I got this network working - changing from WPA(TKIP)
to WPA2(AES) solved problem for me.
Now network is working fine, but it just won't work with TKIP. This might be
Access Point issue - it's just low-budget Planet AP.
--
Intel wireless cannot connect using WPA
Same problem here using Ubuntu karmic 9.10.
In jaunty it worked fine with same hardware. I think there's some problem with
WPA, because it works when I turn encryption off on AP.
Package: network-manager
Status: install ok installed
Architecture: amd64
Version:
System is fully upgraded. Strange thing is that 'wicd' works fine with
this network, and previous distro version on 'network-manager' also
worked fine...
# LC_ALL=C apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly
Public bug reported:
Binary package hint: dvdrip
Problem appears when transcoding in cluster mode, when final step to merge
chunks is taken.
Merging is made with 'avimerge' command - which comes from 'transcode-utils'
package.
Log entry from DVD::Rip Cluster Control
Thu Sep 24 21:02:04 2009
Public bug reported:
General problem with dpkg after upgrade.
# dpkg --configure -a
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
Aborted
I'm not able to do anything related to packages.
dpkg: error processing foomatic-filters (--configure):
package
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/22074252/Dependencies.txt
** Attachment added: DpkgTerminalLog.txt
http://launchpadlibrarian.net/22074253/DpkgTerminalLog.txt
--
dpkg reporting some problems after last gtk upgrade
https://bugs.launchpad.net/bugs/326513
duplicates #326326
--
dpkg reporting some problems after last gtk upgrade
https://bugs.launchpad.net/bugs/326513
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
*** This bug is a duplicate of bug 262451 ***
https://bugs.launchpad.net/bugs/262451
** This bug has been marked a duplicate of bug 262451
dpkg: ../../src/packages.c:221: process_queue: Assertion `dependtry = 4'
failed.
--
dpkg reporting some problems after last gtk upgrade
28 matches
Mail list logo
