Thanks for the patch!
I am looking forward to an updated package...
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2081692
Title:
apparmor profile too restrictive : kernel logs spammed wi
Fix submitted for AppArmor upstream:
https://gitlab.com/apparmor/apparmor/-/merge_requests/1333
Until the fix arrives in Ubuntu, you can add the additional lines to
your /etc/apparmor.d/abstractions/mesa or (better) create a file
/etc/apparmor.d/abstractions/mesa.d/lp2081692 with the added lines.
** Changed in: xorg-server (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2081692
Title:
apparmor profile too restrictive : kernel logs spammed with
Though this kernel message is unusual and might be related:
i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun: transcoder,
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because
Thanks for the bug report. Please try adding this kernel parameter:
i915.enable_psr=0
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2081250
Title:
Dual Monitor - Builtin Screen shake
To man
It looks like 'vmmon' (part of VMware) is causing frequent kernel
errors. What makes you say this is related to ACPI?
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member
Thanks for the bug report. There doesn't seem to be any Nvidia driver
loaded, which is at least one explanation for not being able to control
the monitor.
Please open the 'Additional Drivers' app and use it to install an Nvidia
driver. If you have already done that then see bug 1975650.
** Packag
> Reopened in bug 2081291(?)
Yeah, that's a different bug. A new regression with nvidia 560, for
Vulkan apps this time. The fact that gtk4 now defaults to Vulkan makes
it show up as the same bug...
I directed that issue to a new bug rather than adding more "affected
projects" here to not disturb
new instance
** Attachment added: "recentjournal.txt"
https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2080966/+attachment/5821362/+files/recentjournal.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xwayland in Ubuntu.
https://bu
new instance
** Attachment added: "recentjournal.txt"
https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2080966/+attachment/5821363/+files/recentjournal.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xwayland in Ubuntu.
https://bu
Reopened in bug 2081291(?)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to egl-wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1965563
Title:
GNOME apps crash with "Protocol error" in NVIDIA Wayland sessions
To manage notifications about t
See also bug 2080361.
** Summary changed:
- I have random log out
+ gnome-shell: Xwayland terminated, exiting since it was mandatory
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xwayland in Ubuntu.
https://bugs.launchpad.net/bugs/2080966
T
See also bug 2080966.
** Summary changed:
- Ubuntu 24.04.1 LTS Wayland crashes
+ gnome-shell: Xwayland terminated, exiting since it was mandatory
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xwayland in Ubuntu.
https://bugs.launchpad.net/bug
13 matches
Mail list logo
