** Changed in: webkit2gtk (Ubuntu)
Milestone: ubuntu-24.04 => noble-updates
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2037015
Title:
Screen corruption of webkit2gtk apps in X11 on
This is targeted to 24.04 and marked as 'in progress' but is definitely
not landing before 24.04 GA on Thursday. What is the overall plan here?
should this go to SRU? (It can, but in that case doesn't benefit users
wrt the corruption issue in the *installer* until 24.04.1.)
--
You received
** Also affects: xorg-server (Ubuntu Noble)
Importance: High
Status: Triaged
** Also affects: xwayland (Ubuntu Noble)
Importance: High
Status: Triaged
** Also affects: xorg-server (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: xwayland (Ubuntu
I have prepared test packages for ubuntu 22.04 LTS/jammy in the
https://launchpad.net/~ubuntu-security-
proposed/+archive/ubuntu/ppa/+packages PPA for both xorg-server:
https://launchpad.net/~ubuntu-security-
proposed/+archive/ubuntu/ppa/+sourcepub/15921802/+listing-archive-extra
and for
The reproducer https://bugs.freedesktop.org/attachment.cgi?id=28621 from
the original 2009 bug report
https://bugs.freedesktop.org/show_bug.cgi?id=23286 does seem to work at
triggering this issue, at least under Xwalyand.
** Bug watch added: freedesktop.org Bugzilla #23286
Are people seeing this issue with any other Ubuntu releases, which also
received updates addressing CVE-2024-31083, or is this strictly
affecting the version in 22.04/jammy?
It looks like
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1476 has a
proposed fix, in
mesa bootstrap had not been unwound all the way. Fixed mesa is building
now.
** Package changed: auto-multiple-choice (Ubuntu) => mesa (Ubuntu)
** Changed in: mesa (Ubuntu)
Status: New => Fix Released
** Changed in: mesa (Ubuntu)
Assignee: (unassigned) => Steve Langase
Hello Timo, or anyone else affected,
Accepted mesa into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/23.2.1-1ubuntu3.1~22.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Mate, or anyone else affected,
Accepted mesa into mantic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mesa/23.2.1-1ubuntu3.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
The directx-headers part of this is easy because it's just a build-
dependency of mesa, but mesa itself is a big delta to a library that
affects all users of the graphics stack: unlike the kernel, which has
both GA and HWE versions where the user can opt out of the rolling
kernel updates on the
Hello Timo, or anyone else affected,
Accepted directx-headers into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/directx-
headers/1.610.2-2~ubuntu0.22.04.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this
Hello Timo, or anyone else affected,
Accepted mesa-amber into jammy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/mesa-
amber/21.3.9-0ubuntu1~22.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Hello Timo, or anyone else affected,
Accepted mesa into lunar-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/23.0.4-0ubuntu1~23.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Sam, or anyone else affected,
Accepted mesa into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/22.2.5-0ubuntu0.1~22.04.3 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Daniel, or anyone else affected,
Accepted intel-media-driver-non-free into jammy-proposed. The package
will build now and be available at
https://launchpad.net/ubuntu/+source/intel-media-driver-non-
free/22.3.1+ds1-1ubuntu0.1 in a few hours, and then in the -proposed
repository.
Please
Hello Daniel, or anyone else affected,
Accepted intel-media-driver into jammy-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/intel-
media-driver/22.3.1+dfsg1-1ubuntu2 in a few hours, and then in the
-proposed repository.
Please help us by testing
This mention of version numbers in the test plan makes no sense. Please
clear up the test plan so it's understandable.
** Changed in: intel-media-driver-non-free (Ubuntu Jammy)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
filed upstream as
https://gitlab.freedesktop.org/libinput/libinput/-/issues/886
** Bug watch added: gitlab.freedesktop.org/libinput/libinput/-/issues #886
https://gitlab.freedesktop.org/libinput/libinput/-/issues/886
--
You received this bug notification because you are a member of Ubuntu-X,
https://unix.stackexchange.com/questions/685039/x11-how-to-invert-axis-
on-touchscreen-matrix has commands that seem to work (xinput set-prop
"Coordinate Transformation Matrix") but the specific values listed
there still have the vertical access reversed.
'xinput set-prop "UGTABLET 11.6 inch
I find recent references to being able to swap the axes with 'xinput
set-prop "Evdev Axes Swap" 1. This fails for me with:
property 'Evdev Axes Swap' doesn't exist, you need to specify its type
and format
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Public bug reported:
On jammy, an XP Pen 13 tablet (shown in the hardware as "UGTABLET 11.6
inch PenDisplay") is unusable because the axes for the stylus are
swapped: moving the stylus up on the screen moves the cursor to the
left, moving it down moves it right, moving the stylus to the left
This got done, the i386 binaries got handled via the NBS process.
** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
Hello Yao, or anyone else affected,
Accepted xorg-server into jammy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/xorg-
server/2:21.1.3-2ubuntu2.8 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Hello Yao, or anyone else affected,
Accepted xorg-server into kinetic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/xorg-
server/2:21.1.4-2ubuntu1.6 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Public bug reported:
The set of binaries from nvidia-graphics-drivers-390 on i386 has been
reduced to:
libnvidia-compute-390 | 390.157-0ubuntu3 | lunar-proposed/restricted | i386
libnvidia-decode-390 | 390.157-0ubuntu3 | lunar-proposed/restricted | i386
libnvidia-encode-390 |
Removing packages from lunar:
libcuda1-384 390.154-0ubuntu1 in lunar armhf
libnvidia-cfg1-390 390.154-0ubuntu1 in lunar armhf
libnvidia-compute-390 390.154-0ubuntu1 in lunar armhf
libnvidia-fbc1-390 390.154-0ubuntu1 in lunar armhf
libnvidia-gl-390
packages in main should not pull in packages in universe by default.
Either libnet-dns-perl needs to list libnet-libidn-perl as the first
alternative, or libnet-libidn2-perl needs to be promoted.
** Changed in: libnet-dns-perl (Ubuntu)
Status: New => Triaged
** Changed in: libnet-dns-perl
Fixed/Working as expected in Gnome-Online-Accounts
On Sat, Dec 3, 2022 at 4:00 AM Michael Catanzaro <1966...@bugs.launchpad.net>
wrote:
> Is this still a problem?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1968764).
>
Hi Mikko, thanks for the report. Given the public issues elsewhere, I'm
opening this bug up publicly as well.
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in
ok closing this as invalid as I expect there's nothing else for the
archive admins to track, spirv-llvm-translator should fall out of the
archive once it's no longer used in kinetic+1
** Changed in: spirv-llvm-translator (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug
Unfortunately, for the last one it hasn't been removed because despite
Debian saying it's no longer used, reverse-depends appears to disagree:
Reverse-Depends
* libllvmspirvlib-11-dev(for libllvmspirvlib11)
* libopencl-clang11 (for libllvmspirvlib11)
* libopencl-clang13
In fact, three of these I removed today following their removal from
Debian.
** Changed in: intel-opencl-clang (Ubuntu)
Status: New => Fix Released
** Changed in: opencl-clang-11 (Ubuntu)
Status: New => Fix Released
** Changed in: spirv-llvm-translator-11 (Ubuntu)
Status:
** Changed in: esmtp (Ubuntu)
Status: Fix Released => Won't Fix
** Changed in: xterm (Ubuntu)
Status: Fix Released => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xterm in Ubuntu.
I re-installed the HP Pavilion dvb Core Duo with Intel graphics with
regular Ubuntu 22.04 with GNOME and Wayland, and didn't have any crashes
during a week of regular usage. The regular Ubuntu is actually pretty
responsive on this older hardware (using an SSD) and the installation
chose an
Public bug reported:
Crashes X11 back to login screen typically when running the browser.
I refurbish old laptops, and this older HP Pavilion dvb Core Duo with
Intel graphics is probably no longer supported by Mesa 22 from the
searching of the core problems that I did.
Please consider some
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1982501
Title:
NVIDIA CVE-2022-{31607|31608}
To
Public bug reported:
When using the default wayland-based session in Ubuntu 22.04, trying to
use +/- to control window placement doesn't work. E.g. the following
should give me a gnome-terminal window in the lower-right corner of the
screen:
gnome-terminal --geometry -0-0
It does not;
On Wed, Apr 20, 2022 at 03:58:40AM -, Gunnar Hjalmarsson wrote:
> Alternate Charters Key to None + Compose key to Right Alt
> -
> $ gsettings get org.gnome.desktop.input-sources xkb-options
> ['lv3:ralt_alt', 'compose:ralt']
> Right Alt
> And AFAICT gnome-control-center sets the expected XKB options,
> so it's not a g-c-c bug. Maybe an xkeyboard-config bug.
>From my initial bug report:
Setting Alternate Characters Key to None, and moving the Compose Key
setting around between different options (and then back to Right Alt),
the
Override component to main
mesa-amber 21.3.7-0ubuntu1 in jammy: universe/graphics -> main
libegl-amber0 21.3.7-0ubuntu1 in jammy amd64: universe/libs/optional/100% ->
main
libegl-amber0 21.3.7-0ubuntu1 in jammy arm64: universe/libs/optional/100% ->
main
libegl-amber0 21.3.7-0ubuntu1 in jammy
This looks incomplete from the perspective of an FFe. Is this actually
a complete description of the new features present in this new upstream
version? An FFe should address the full scope of new features in order
to assess the risk of taking it as a late change, not just the feature
you're
Removing packages from jammy:
xserver-xorg-video-trident 1:1.3.8-2build1 in jammy
xserver-xorg-video-trident 1:1.3.8-2build1 in jammy amd64
xserver-xorg-video-trident 1:1.3.8-2build1 in jammy arm64
xserver-xorg-video-trident 1:1.3.8-2build1
Removing packages from jammy:
xserver-xorg-video-tdfx 1:1.5.0-4 in jammy
xserver-xorg-video-tdfx 1:1.5.0-4 in jammy amd64
xserver-xorg-video-tdfx 1:1.5.0-4 in jammy arm64
xserver-xorg-video-tdfx 1:1.5.0-4 in jammy armhf
Removing packages from jammy:
xserver-xorg-input-mutouch 1:1.3.0-2build1 in jammy
xserver-xorg-input-mutouch 1:1.3.0-2build1 in jammy amd64
xserver-xorg-input-mutouch 1:1.3.0-2build1 in jammy arm64
xserver-xorg-input-mutouch 1:1.3.0-2build1
Removing packages from jammy:
xserver-xorg-input-elographics 1:1.4.2-1 in jammy
xserver-xorg-input-elographics 1:1.4.2-1 in jammy amd64
xserver-xorg-input-elographics 1:1.4.2-1 in jammy arm64
xserver-xorg-input-elographics 1:1.4.2-1 in jammy
Removing packages from jammy:
xserver-xorg-input-aiptek 1:1.4.1-3build1 in jammy
xserver-xorg-input-aiptek 1:1.4.1-3build1 in jammy amd64
xserver-xorg-input-aiptek 1:1.4.1-3build1 in jammy arm64
xserver-xorg-input-aiptek 1:1.4.1-3build1 in
geode doesn't seem to have been readded, but I've added it to the sync
blacklist.
** Changed in: xserver-xorg-video-geode (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev
Removing packages from jammy:
xserver-xorg-video-savage 1:2.3.9-4 in jammy
xserver-xorg-video-savage 1:2.3.9-4 in jammy amd64
xserver-xorg-video-savage 1:2.3.9-4 in jammy arm64
xserver-xorg-video-savage 1:2.3.9-4 in jammy armhf
Removing packages from jammy:
xserver-xorg-video-siliconmotion 1:1.7.9-3build1 in jammy
xserver-xorg-video-siliconmotion 1:1.7.9-3build1 in jammy amd64
xserver-xorg-video-siliconmotion 1:1.7.9-3build1 in jammy arm64
Removing packages from jammy:
xserver-xorg-video-neomagic 1:1.3.0-2build1 in jammy
xserver-xorg-video-neomagic 1:1.3.0-2build1 in jammy amd64
xserver-xorg-video-neomagic 1:1.3.0-2build1 in jammy arm64
xserver-xorg-video-neomagic
Removing packages from jammy:
xserver-xorg-video-mach64 6.9.6-3 in jammy
xserver-xorg-video-mach64 6.9.6-3 in jammy amd64
xserver-xorg-video-mach64 6.9.6-3 in jammy arm64
xserver-xorg-video-mach64 6.9.6-3 in jammy armhf
Removing packages from jammy:
xserver-xorg-video-sisusb 1:0.9.7-2build1 in jammy
xserver-xorg-video-sisusb 1:0.9.7-2build1 in jammy amd64
xserver-xorg-video-sisusb 1:0.9.7-2build1 in jammy arm64
xserver-xorg-video-sisusb 1:0.9.7-2build1 in
Override component to main
egl-wayland 1:1.1.9-1.1 in jammy: universe/misc -> main
libnvidia-egl-wayland-dev 1:1.1.9-1.1 in jammy amd64:
universe/libdevel/optional/100% -> main
libnvidia-egl-wayland-dev 1:1.1.9-1.1 in jammy arm64:
universe/libdevel/optional/100% -> main
libnvidia-egl-wayland-dev
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: update-manager (Ubuntu Precise)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: pvr-omap4 (Ubuntu Precise)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xf86-video-omap in Ubuntu.
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: xdiagnose (Ubuntu Precise)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xdiagnose in Ubuntu.
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: xorg-server (Ubuntu Precise)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: xkeyboard-config (Ubuntu Precise)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xkeyboard-config
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: libwacom (Ubuntu Precise)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libwacom in Ubuntu.
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: xorg-server (Ubuntu Precise)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: xserver-xorg-video-intel (Ubuntu Precise)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: xserver-xorg-video-nouveau (Ubuntu Precise)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: intel-linux-graphics-installer (Ubuntu Precise)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: binary-driver-fglrx (Ubuntu Precise)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: xserver-xorg-video-intel (Ubuntu Precise)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: xserver-xorg-video-nouveau (Ubuntu Precise)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: fglrx-installer (Ubuntu Precise)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: nvidia-graphics-drivers (Ubuntu Precise)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: xserver-xorg-video-intel (Ubuntu Precise)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: apport (Ubuntu Precise)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: nvidia-graphics-drivers (Ubuntu Precise)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: xorg-server (Ubuntu Precise)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: xserver-xorg-video-intel (Ubuntu Precise)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: xdiagnose (Ubuntu Precise)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xdiagnose in Ubuntu.
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: nvidia-graphics-drivers-319-updates (Ubuntu Precise)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: xserver-xorg-input-synaptics (Ubuntu Precise)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: mesa (Ubuntu Precise)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
** Changed in: linux (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1933980
Title:
NVIDIA CVE-2021-{1093|1094|1094}
To manage notifications
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
@Shih-Yuan Lee:
I see you use a similar dockingstation and you made patch
(https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/443/)
But I have exact the same behaviour - see my bug
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-460/+bug/1935951
It is almost a
** Attachment added: "Software info and version"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1935951/+attachment/5510719/+files/desktopcrash_after_resume.zip
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Public bug reported:
X11 crashes on resume and my current desktop is lost and the login
manager appears.
I posted a bugreported here
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1197
with configu details.
But it seems to be nvidia, but may be a workaround is possible in Ubuntu?
This
Can this bug status change to open or should I create a new bug report?
--
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/1493921
Title:
X server fails to set correct mode on resume from sleep
I have exactly the same issue and can't use Linux for Home office: daily
docking/undocking cycles:
See bugreport [1] Linux for HomeOffice - Sporadic X11 crash when
docking/undocking "Failed to enter VT"
My system config:
Most recent Ubuntu 20.04LTS and KDE Plasma version
Dell Precision 15"
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
I just solved my 30bit problem with an Displayport to HDMI adapter[1].
Now the screens operate at 4k 60Hz 24bits in Linux and no more screen
corruption.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
I came across this bug because of my problem which I described in
https://askubuntu.com/questions/1314639/weird-graphics-artifacts-
monitor-off-with-ubuntu-20-04-and-nvidia-rtx-5000/1343876#1343876
In my case the Dell monitors tell, they can support 30bit.
I came to the conclusion, that the
Thank you for using Ubuntu and taking the time to report a bug. Your
report should contain, at a minimum, the following information so we can
better find the source of the bug and work to resolve it.
Submitting the bug about the proper source package is essential. For
help see
** Information type changed from Private Security to Public
--
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/1919285
Title:
Nvidia
To manage notifications about this bug go to:
Publication to focal-updates for nvidia-driver-440-server
440.95.01-0ubuntu0.20.04.1 and for groovy happened as well, closing
tasks.
** Changed in: nvidia-graphics-drivers-440-server (Ubuntu Focal)
Status: Fix Committed => Fix Released
** Changed in: nvidia-graphics-drivers-440-server
Removing packages:
xserver-xorg-input-void 1:1.4.1-1build3 in groovy
xserver-xorg-input-void 1:1.4.1-1build3 in groovy amd64
xserver-xorg-input-void 1:1.4.1-1build3 in groovy arm64
xserver-xorg-input-void 1:1.4.1-1build3 in groovy armhf
Modifications to the grub scripts will not be overwritten by the grub
security update.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1845801
Title:
[nvidia] Automatic
hugh, you will need to coordinate this with the Foundations Team, as
there are a number of grub changes currently queued for SRU.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
** Changed in: libxpresent (Ubuntu Disco)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxpresent in Ubuntu.
https://bugs.launchpad.net/bugs/1565496
Title:
Marco tearing with composite enabled.
To manage
** Changed in: xorg-server (Ubuntu Disco)
Status: Confirmed => Won't Fix
--
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/1795135
Title:
XFCE window buttons are not clickable at the
** Changed in: nvidia-settings (Ubuntu Disco)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1822937
Title:
NVIDIA settings won't write to
** Changed in: linux (Ubuntu Disco)
Status: Confirmed => Won't Fix
** Changed in: linux (Ubuntu Cosmic)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
1 - 100 of 1216 matches
Mail list logo
