The verification of the Stable Release Update for mesa has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a reg
** No longer affects: cloud-init (Ubuntu)
** No longer affects: cloud-init (Ubuntu Jammy)
** No longer affects: cloud-init (Ubuntu Noble)
** No longer affects: ubuntu-advantage-tools (Ubuntu)
** No longer affects: ubuntu-advantage-tools (Ubuntu Noble)
** No longer affects: ubuntu-advantage-too
The verification of the Stable Release Update for egl-wayland has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encount
So
https://bugs.launchpad.net/ubuntu/+source/egl-wayland/+bug/1965563/comments/40
tested the proposed package on an hybrid system, with nvidia 550, thus
satisfying the test plan criteria. The statement "everything works correctly"
is very vague, though, and I would like a more accurate descript
** Tags removed: verification-done-jammy
** Tags added: verification-needed-jammy
--
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/2037604
Title:
Backport packages for 22.04.4 HWE stack
To manage
Technically, the verification from prior comments was performed on
23.2.1-1ubuntu3.1~22.04.1, not 23.2.1-1ubuntu3.1~22.04.2. I think they
need to be done on the mesa package that is in proposed now, which is
.2.
--
You received this bug notification because you are a member of Ubuntu-X,
which is
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.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:/
Hello Lee, 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.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
Please amend the test case to test with both the GA and the (affected)
6.1 OEM kernels.
--
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/2051068
Title:
GUI crashed after installed proposed package
I still get this error in Ubuntu Lunar, with kernel 6.2.0-35-generic.
Sample:
$ sudo dmesg -T|grep Atomic
[qua nov 1 05:52:03 2023] i915 :00:02.0: [drm] *ERROR* Atomic update
failure on pipe A (start=78023 end=78024) time 305 us, min 1783, max 1799,
scanline start 1753, end 1804
[qua nov 1
Chromium played a local video just fine, and that video was recognized
like this by mpv:
(+) Video --vid=1 (*) (h264 1920x1080 60.000fps)
--
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/203
I used that snap in a few long calls already, and did not experience the
Pxms leak. Closing the browser after such calls also did not leave xorg
at 100% cpu like before.
Haven't checked x264 playback yet, but as Daniel said, I doubt it would
regress because of this patch.
--
You received this bu
Please ping here when a new chromium snap is available in latest/edge.
--
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/2033433
Title:
Chromium leaks tens of gigabytes of pixmaps (in the Xo
Upstream bug got an update:
https://bugs.chromium.org/p/chromium/issues/detail?id=1467689#c41
Patch?
https://chromium.googlesource.com/chromium/src/+/42d57d016f5fb6d2a1a354743b9be911c1be87e8%5E%21/
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
This bug is easy to reproduce, what we need now is a 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/2033433
Title:
Chromium leaks tens of gigabytes of pixmaps (in the Xorg process)
The output from `top` was always well behaved while chromium was open,
until it was closed, at which point xorg cpu's usage went through the
roof.
The test case here is indeed watching "Pxms" in xrestop while chromium
is displaying hw accelerated video.
--
You received this bug notification beca
Thanks for guiding the troubleshooting on this one, I learned a new tool
;) (xrestop)
--
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/2033433
Title:
Chromium leaks tens of gigabytes of pix
So I took some screenshots of `xrestop` while chromium was in the google
meet.
There was an "unknown PID" listed, but given other characteristics of
that line, I assume that it is related to chromium.
Here are some of the columns over time:
Pxms MiscPxm memTotal
12:09:28
I attached gdb to xorg while the bug was happening (100% cpu usage after
closing chromium), and got the backtrace with symbols. I hope this
helps, but maybe it missed the loop, I don't know.
** Attachment added: "xorg.backtrace"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/203343
Found it, and I closed it because the screen flickering is gone:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018448
But the "Atomic update" error was there, on pipe A if that makes any
difference. I see it on A/B/C, very much like
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/180
> "Atomic update failure" may also be specific to the OLED panel that it
> looks like Andreas is using. I have one of those but have never run Xorg
> on it.
FWIW, I'm using two external 4k Dell monitors via usb-c, plus the laptop
panel also at its max resolution (a bit lower then the monitors:
288
What's up with the lunar task that is still open? Lunar didn't have a
mesa update yet, so it can't have regressed. I understand if we want to
avoid future regressions in lunar too, of course, but the fix ("set
VERSION so that it also includes the packaging version") should be
bundled together with
Regarding the impact section:
[ Impact ]
* It will disable pressure event for i2c touchpad vid 0x06cb pid 0xcfa0
You are describing what the update will do, but not why. Why do we need to
"disable pressure event" for this device? What's going on? What happens to
users of this hardware witho
Hello jeremyszu, 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.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
ht
Hello Kai, 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.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
The revert is not in Kinetic, implying it could be affected by this bug
too. Do you intend to skip kinetic, or is it not affected?
** Changed in: mesa (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Tags added: verification-needed verification-needed-jammy
--
You received this bug
Hello Mario, 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.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:
The verification of the Stable Release Update for intel-media-driver-
non-free has completed successfully and the package is now being
released to -updates. Subsequently, the Ubuntu Stable Release Updates
Team is being unsubscribed and will not receive messages about this bug
report. In the event
I verified the test results and am satisfied that they show the executed
planned test case, and that the results are correct.
The package built correctly in all architectures and Ubuntu releases it
was meant for.
There are no DEP8 regressions.
There is no SRU freeze ongoing at the moment.
There
In Kinetic, there is a DEP8 regression on armhf that was not addressed
yet:
autopkgtest for openmsx-catapult/18.0-1: amd64: Pass, arm64: Pass,
armhf: Regression ♻ , ppc64el: Pass, s390x: Pass
I see it was retried multiple times, and a migration-reference/0 run
passed, so it's indeed a regression
** Changed in: mesa (Ubuntu Jammy)
Status: Fix Committed => In Progress
--
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/1998893
Title:
NV reverse prime HDMI has no output
To manage notifi
I think this bug/SRU snowballed. Let's take a step back.
It started with fixing two bugs: this one, and bug #1972977. At some
point later, #1972977 was deemed not really fixed[1], and was dropped in
the 0ubuntu0.3 upload[2].
That upload failed to build in jammy-proposed on arm64[3] and amd64[4].
I ran update-maintainer on the mesa source and uploaded again.
Give the removal of PCI IDs, and the vague statement in the "Where
things could go wrong" section of the bug description, I'd like to see a
more clear statement saying that these IDs are already not available in
the jammy kernel, and a
Hello Kai-Chuan, 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.0.5-0ubuntu0.3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wi
I accepted 22.0.5-0ubuntu0.3 which does NOT fix this bug, so I'm
reopening it.
** Changed in: mesa (Ubuntu Jammy)
Status: Fix Committed => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.ne
Hello errors.ubuntu.com, 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.0.5-0ubuntu0.3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
ht
Adding a test for xorg for their consideration.
--
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/1818879
Title:
pull cirrus.ko into main kernel package
To manage notifications about this bug go t
Another alternative would be to have vesa specify a working bpp value,
if that is the only problem there.
** Also affects: xorg (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Upstream bug https://gitlab.freedesktop.org/spice/spice-gtk/issues/66
was closed, but if I understood it correctly, only for 18.04. Is this
still an issue for 16.04, and does the patch from comment #5 help there?
--
You received this bug notification because you are a member of Ubuntu-X,
which is
*** This bug is a duplicate of bug 1751086 ***
https://bugs.launchpad.net/bugs/1751086
** This bug is no longer a duplicate of private bug 1753735
** This bug has been marked a duplicate of bug 1751086
Xorg assert failure: Xorg: ../src/evdev-mt-touchpad-tap.c:1002:
tp_tap_handle_state: Ass
With libinput 1.10.3-2, the crash doesn't happen anymore. I just get
these EE lines in /var/log/syslog when I repeat the gesture that
previously crashed it (and these were there with the older libinput as
well):
Mar 21 08:50:26 nsnx /usr/lib/gdm3/gdm-x-session[4968]: (EE) event5 - SynPS/2
Synapt
I can trigger this reliably with my thinkpad X1 5th gen on bionic's xorg:
Mar 20 11:08:19 nsnx /usr/lib/gdm3/gdm-x-session[16817]: (II) Axis 0x35 value 0
is outside expected range [1045, 5896]
Mar 20 11:08:19 nsnx /usr/lib/gdm3/gdm-x-session[16817]: See
https://wayland.freedesktop.org/libinput/do
xserver-xorg 1:7.7+19ubuntu5 currently
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1751086
Title:
Xorg assert failure: Xorg: ../src/evdev-mt-touchpad-tap.c:1002:
tp_tap_handle_state: As
*** This bug is a duplicate of bug 1753735 ***
https://bugs.launchpad.net/bugs/1753735
Looks like the backtrace isn't in the attached logs, let me fix that.
Mar 14 09:54:21 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) event5 - SynPS/2
Synaptics TouchPad: kernel bug: Touch jump detected and
*** This bug is a duplicate of bug 1753735 ***
https://bugs.launchpad.net/bugs/1753735
Public bug reported:
Happened twice now. During normal usage, the screen just goes blank and
I'm thrown back at the GUI login prompt. Logs show X crashed, have a
backtrace, and it looks like it's related to
I added an nvidia task to the bug so its maintainer can take a look to
see if it's related or not.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/1731796
Title:
NMI watchdog:
Or nvidia
** Also affects: nvidia-graphics-drivers (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/1731796
Title:
NMI watc
Sorry, it's actually gdbus that is soft locking
** Package changed: nvidia-graphics-drivers (Ubuntu) => glib2.0 (Ubuntu)
** Summary changed:
- package samba 2:4.3.11+dfsg-0ubuntu0.16.04.10 failed to install/upgrade:
subprocess new pre-removal script returned error exit status 1
+ NMI watchdog:
Thanks for filing this bug in Ubuntu.
Sorry for the troubles you are having, but indeed your logs show a lot
of "soft lockups" in the kernel, and all seem to be in the nvidia
module.
I'm going to change this bug as affecting nvidia, since I don't believe
it's samba specific.
** Package changed:
Interesting:
Exception in thread "AWT-EventQueue-1" com.jogamp.opengl.GLException: Caught
GLException: AWT-EventQueue-1: createImpl ARB n/a but required, profile > GL2
requested (OpenGL >= 3.1). Requested: GLProfile[GL3bc/GL3bc.sw], current: 3.0
(Compat profile, compat[ES2], FBO, software) - 3.0
Public bug reported:
I have an old NVidia GeForce 7900GT (G71) that needs the NVidia-304
driver. The kernel module cannot be loaded while using artful:
Unknown symbol init_mm (err 0)
Kernel is 4.12.0-11-generic #12 64bits
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: nvidia-304-updates
Same here. I'm on:
Linux duo 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:32:24 UTC 2015 i686
i686 i686 GNU/Linux
Card is:
04:00.0 VGA compatible controller: NVIDIA Corporation G71 [GeForce 7900 GT/GTO]
(rev a1)
--
You received this bug notification because you are a member of Ubuntu-X,
which
Working fine here too.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/929384
Title:
nvidia drivers broken by the recent libc update on i386 arch
To manage notifications about
output of nvidia-bug-report.sh attached
** Attachment added: "nvidia-bug-report.log.gz"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/929384/+attachment/2727566/+files/nvidia-bug-report.log.gz
--
You received this bug notification because you are a member of Ubuntu-X
** Attachment added: "vid.mpg"
https://bugs.launchpad.net/bugs/927570/+attachment/2719166/+files/vid.mpg
** Summary changed:
- Garbled screen with nouveau driver
+ Bad screen redraw with nouveau driver
** Description changed:
- On this T420 lenov0, when using the nouveau driver, the screen d
Public bug reported:
On this T420 lenovo, when using the nouveau driver, the screen doesn't
redraw properly when windows change. I'll attach a small video to
illustrate the problem. Sorry about the quality, I wanted to keep it
small, but I think it's possible to see the issue.
ProblemType: Bug
Di
On my t420 running 11.10 (oneiric), after I enabled nvidia in the bios
(as a discrete card, not optimus), jockey still can't find it:
andreas@nsn7:~$ jockey-text
Additional Drivers
Searching for available drivers...
andreas@nsn7:~$
Maybe that's what the OP meant.
01:00.0 VGA compatible control
/vmlinuz is a broken link:
lrwxrwxrwx 1 root root 29 2010-12-03 08:12 vmlinuz ->
boot/vmlinuz-2.6.37-7-generic
r...@ubuntu:~# ll /boot/
total 20569
drwxr-xr-x 4 root root 80 2010-12-08 13:16 ./
drwxr-xr-x 33 root root 320 2010-12-08 13:09 ../
-rw-r--r-- 1 root root 714835 2010-
I get this when trying to install nvidia-current with apt-get:
r...@ubuntu:~# apt-get install nvidia-current
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
dkms fakeroot nvidia-settings patch screen-r
Where exactly should there be sufficient disk space? The df output below shows
the free space right after I got the error:
ubu...@ubuntu:~$ df -h
FilesystemSize Used Avail Use% Mounted on
aufs 1006M 213M 794M 22% /
none 1000M 352K 1000M 1% /dev
/d
Wait, you mean the slider in startup-disk-creator where you can choose
how much space you want for settings and documents, right? Or something
else?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in ubuntu.
https://bugs.l
That may be the case. Let me try again with 512Mb (it's a 4Gb pendrive).
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in ubuntu.
https://bugs.launchpad.net/bugs/685017
Title:
package nvidia-current 260.19.21-0ubuntu1
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in ubuntu.
https://bugs.launchpad.net/bugs/685017
Title:
package nvidia-current 260.19.21-0ubuntu1 failed to install/upgrade:
subprocess installed post-installation scri
Public bug reported:
Booted from usb disk
Got a notice saying that unity was not available because I didn't have
3D.
Went to System->Administration->Hardware drivers, selected to install
nvidia drivers.
Apport detected crash, driver installation failed.
ProblemType: Package
DistroRelease: Ubun
Scott, you should refrain from offending people who try to help and
actually managed to debug this problem. What this accomplishes is that
they won't even file a bug the next time this happens, even less try to
fix it.
A more constructive change would be to just say it's wrong (and not
include the
Assuming this is Lucid, do you have /usr as a separate partition? If you
do, then this is likely a duplicate of bug #538071
--
nvidia/lucid deinstall of nvidia'current causes X11 mayhem
https://bugs.launchpad.net/bugs/535339
You received this bug notification because you are a member of Ubuntu-X,
BTW, what is a conf file doing in /usr/lib? Doesn't that violate at
least one of the gazillion Debian policies?
--
Nouveau blacklisting with /usr on seperate partition fails (Lucid Alpha3)
https://bugs.launchpad.net/bugs/538071
You received this bug notification because you are a member of Ubuntu
I'm also getting another issue, which may warrant another bug report
entirely, but I wanted to show it here since it started happening as
soon as I installed the nvidia related packages.
In the attached screenshot, you can see my bootsplash. It's "wrong". The
colors are off, the resolution is also
I believe the fix worked. Before I had zeroed-out the nouveau.ko files,
to make sure they were not being loaded at all. I now reinstalled the
kernel, made sure the module existed, and rebooted. Got my screen back,
phew
--
Nouveau blacklisting with /usr on seperate partition fails (Lucid Alpha3)
h
Sometimes I wish I were a "normal" user, with no fancy partitioning ;)
Same problem here, will try the fix now.
--
Nouveau blacklisting with /usr on seperate partition fails (Lucid Alpha3)
https://bugs.launchpad.net/bugs/538071
You received this bug notification because you are a member of Ubuntu
*** This bug is a duplicate of bug 309402 ***
https://bugs.launchpad.net/bugs/309402
** This bug has been marked a duplicate of bug 309402
ipv6 support
--
thinkpad t61 slash/question key not working
https://bugs.launchpad.net/bugs/372725
You received this bug notification because you are
71 matches
Mail list logo
