[Ubuntu-x-swat] [Bug 2037604] Re: Backport packages for 22.04.4 HWE stack
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2037604] Re: Backport packages for 22.04.4 HWE stack
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 subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037604 Title: Backport packages for 22.04.4 HWE stack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2037604] Please test proposed package
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://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2051068] Re: GUI crashed after installed proposed package libegl-mesa0
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://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mesa (Ubuntu Jammy) Status: Triaged => Fix Committed ** Tags added: verification-needed 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/2051068 Title: GUI crashed after installed proposed package libegl-mesa0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2051068/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2051068] Re: GUI crashed after installed proposed package libegl-mesa0
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 libegl-mesa0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2051068/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1806242] Re: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A/B/C
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 06:15:56 2023] i915 :00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=161109 end=161110) time 209 us, min 1783, max 1799, scanline start 1775, end 1811 [qua nov 1 22:22:34 2023] i915 :00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=50827 end=50828) time 270 us, min 1783, max 1799, scanline start 1767, end 1812 [qua nov 1 22:32:50 2023] i915 :00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=90592 end=90593) time 278 us, min 1783, max 1799, scanline start 1768, end 1814 [qua nov 1 22:35:42 2023] i915 :00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=100359 end=100360) time 168 us, min 1783, max 1799, scanline start 1779, end 1807 [qua nov 1 23:29:19 2023] i915 :00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=259865 end=259866) time 276 us, min 1783, max 1799, scanline start 1770, end 1817 [qui nov 2 03:54:09 2023] i915 :00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=317370 end=317371) time 264 us, min 1783, max 1799, scanline start 1756, end 1801 [qui nov 2 03:57:36 2023] i915 :00:02.0: [drm] *ERROR* Atomic update failure on pipe A (start=331393 end=331394) time 279 us, min 1783, max 1799, scanline start 1769, end 1816 [qui nov 2 04:00:05 2023] i915 :00:02.0: [drm] *ERROR* Atomic update failure on pipe C (start=317726 end=317727) time 255 us, min 2146, max 2159, scanline start 2140, end 2173 [qui nov 2 04:48:44 2023] i915 :00:02.0: [drm] *ERROR* Atomic update failure on pipe C (start=492825 end=492826) time 272 us, min 2146, max 2159, scanline start 2123, end 2159 Hardware is a lenovo x1 10th gen, with intel "alderlake gen12" according to intel_gpu_top, and I'm running xorg (not wayland). ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1806242 Title: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A/B/C To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806242/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2033433] Re: Chromium leaks tens of gigabytes of pixmaps (in the Xorg process) after using hardware accelerated video
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/2033433 Title: Chromium leaks tens of gigabytes of pixmaps (in the Xorg process) after using hardware accelerated video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2033433/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2033433] Re: Chromium leaks tens of gigabytes of pixmaps (in the Xorg process) after using hardware accelerated video
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 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) after using hardware accelerated video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2033433/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2033433] Re: Chromium leaks tens of gigabytes of pixmaps (in the Xorg process) after using hardware accelerated video
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 Xorg process) after using hardware accelerated video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2033433/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2033433] Re: Chromium leaks tens of gigabytes of pixmaps (in the Xorg process) after using hardware accelerated video
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 to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2033433 Title: Chromium leaks tens of gigabytes of pixmaps (in the Xorg process) after using hardware accelerated video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2033433/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2033433] Re: Chromium leaks tens of gigabytes of pixmaps (in the Xorg process) after using hardware accelerated video
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) after using hardware accelerated video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2033433/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2033433] Re: Chromium leaks tens of gigabytes of pixmaps (in the Xorg process) after using hardware accelerated video
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 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) after using hardware accelerated video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2033433/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2033433] Re: Chromium leaks tens of gigabytes of pixmaps (in the Xorg process) after using hardware accelerated video
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 pixmaps (in the Xorg process) after using hardware accelerated video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2033433/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2033433] Re: Xorg 100% CPU and frozen desktop after closing chromium
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 467499 18815550K 18815550K 12:10:38 555089 20869237K 20869237K 12:13:06 7170710 24679650K 24679650K 12:17:06 9399011 29960587K 29960587K 12:30:17 157769 11 45126262K 45126262K 12:35:06 175712 2 49397850K 49397850K The last one, 12:35:06, is just before I closed chromium. It stayed frozen like that, the xrestop app froze just like the rest of the desktop (I was running it over ssh, so I could still ctrl-c it, but it was frozen). Attached is the last screenshot. ** Attachment added: "Screenshot from 2023-09-01 12-35-06.png" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2033433/+attachment/5697229/+files/Screenshot%20from%202023-09-01%2012-35-06.png ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Confirmed ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => New -- 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: Xorg 100% CPU and frozen desktop after closing chromium To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2033433/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2033433] Re: Xorg 100% CPU and frozen desktop after closing chromium
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/2033433/+attachment/5696833/+files/xorg.backtrace -- 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: Xorg 100% CPU and frozen desktop after closing chromium To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2033433/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2033433] Re: Xorg 100% CPU and frozen desktop after closing chromium
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/1806242 -- 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: Xorg 100% CPU and frozen desktop after closing chromium To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2033433/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2033433] Re: Xorg 100% CPU and frozen desktop after closing chromium
> "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: 2880x1800 instead of 3840x2160), everything at 100% scaling. But I have seen those "Atomic update failure" messages while at a sprint, where I only had my laptop and no external monitor. Back then, another symptom was the screen shifting a few pixels at random time, as if in an earthquake. I filed a kernel bug, and even found what looked like a patch we didn't have yet, but failed to pursue it as back home with the external monitor, that screen shifting problem didn't appear anymore. I"m trying to find that bug at the moment. -- 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: Xorg 100% CPU and frozen desktop after closing chromium To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2033433/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2020604] Re: After Mesa upgrades, Chrome won't show graphics
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 that future update of lunar, no?
--
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/2020604
Title:
After Mesa upgrades, Chrome won't show graphics
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2020604/+subscriptions
___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2023623] Re: [SRU] Disable pressure for Precision5680 2nd source touchpad
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 without this patch? I also don't see a kinetic upload, can you please clarify that you are skipping kinetic on purpose, and why? ** Also affects: libinput (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: libinput (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: libinput (Ubuntu Jammy) Status: New => Incomplete ** Changed in: libinput (Ubuntu Lunar) Status: New => Incomplete -- 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/2023623 Title: [SRU] Disable pressure for Precision5680 2nd source touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2023623/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1990089] Re: Screen freeze when performing memory stress in Wayland mode
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 https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mesa (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed 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/1990089 Title: Screen freeze when performing memory stress in Wayland mode To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1990089/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2003339] Please test proposed package
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://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/2003339 Title: kwin_x11: The X11 connection broke: I/O error (code 1) To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2003339] Re: kwin_x11: The X11 connection broke: I/O error (code 1)
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 notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2003339 Title: kwin_x11: The X11 connection broke: I/O error (code 1) To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2017142] Re: [jammy] VA-API doesn't work on DCN 3.1.4
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://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mesa (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed 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/2017142 Title: [jammy] VA-API doesn't work on DCN 3.1.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2017142/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2004237] Update Released
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 that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-media-driver in Ubuntu. https://bugs.launchpad.net/bugs/2004237 Title: Intel Raptor Lake-P support for intel-media-driver in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/2004237/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2004237] Re: Intel Raptor Lake-P support for intel-media-driver in jammy
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 is no halted phasing on a previous update. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-media-driver in Ubuntu. https://bugs.launchpad.net/bugs/2004237 Title: Intel Raptor Lake-P support for intel-media-driver in jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/2004237/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1999008] Re: Xorg crashed with SIGABRT in xf86ModeVRefresh() from drmmode_output_add_gtf_modes() from drmmode_output_get_modes() from xf86ProbeOutputModes() from xf86InitialConfig
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 with xorg- server/2:21.1.4-2ubuntu1.4. Can someone address it please? -- 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/1999008 Title: Xorg crashed with SIGABRT in xf86ModeVRefresh() from drmmode_output_add_gtf_modes() from drmmode_output_get_modes() from xf86ProbeOutputModes() from xf86InitialConfiguration() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1999008/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1998893] Re: NV reverse prime HDMI has no output
** 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 notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998893/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1998893] Re: NV reverse prime HDMI has no output
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]. It was deemed to be a problem introduced by some other jammy-proposed upload (unclear which one). A new upload was made to jammy unapproved[5] (still missing an update- maintainer run, btw), stating: Changes: mesa (22.0.5-0ubuntu0.4) jammy; urgency=medium . * Add a patch to build with a newer directx-headers. (LP: #1998893) . mesa (22.0.5-0ubuntu0.3) jammy; urgency=medium . * crocus-fix-leak-in-query-code.patch: Drop the patch so the other fix can get through to updates. . mesa (22.0.5-0ubuntu0.2) jammy; urgency=medium . * crocus-fix-leak-in-query-code.patch: Fix gnome-shell crashing on older Intel hw. (LP: #1972977) * patches: Update pci-id's for ADL-S/RPL-S. (LP: #1998893) That is quite a big patch in an area I know nothing about. My concerns are: - shouldn't we have a separate bug for the FTBFS? This bug here is about PCI IDs. - what is the other package in jammy proposed that is breaking this build? Must it be released at the same time as mesa? - the original PR[6] mentioned in the DEP3 header of the FTBFS patch is huge and complex, is that (and the backport done here) really the minimal fix for the FTBFS? - what are the other changes incurring via this patch, now the the build is fixed? What else is changing? What is the risk analysis of that change? I feel there is a lot of missing information, but it could just be because I'm not familiar with mesa and the graphic/3d stack. So I prefer to leave this review for another SRU team member, but thought I should leave this comment here instead of just "disappearing" :) 1. https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1972977/comments/15 2. https://launchpad.net/ubuntu/+source/mesa/22.0.5-0ubuntu0.3 3. https://launchpad.net/ubuntu/+source/mesa/22.0.5-0ubuntu0.3/+build/25458695 4. https://launchpad.net/ubuntu/+source/mesa/22.0.5-0ubuntu0.3/+build/25458694 5. https://launchpadlibrarian.net/645131833/mesa_22.0.5-0ubuntu0.4_source.changes 6. https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/15751/diffs -- 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 notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998893/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1998893] Re: NV reverse prime HDMI has no output
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 as such there is an even lesser risk of regression due to that. -- 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 notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998893/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1998893] Re: NV reverse prime HDMI has no output
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://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done verification-done-jammy ** Tags added: verification-needed 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/1998893 Title: NV reverse prime HDMI has no output To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998893/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1972977] Re: gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_qu
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.net/bugs/1972977 Title: gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_query() To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1972977/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1972977] Re: gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_qu
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 https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-failed-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/1972977 Title: gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_query() To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1972977/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1818879] Re: pull cirrus.ko into main kernel package
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 to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818879/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1818879] Re: pull cirrus.ko into main kernel package
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. https://bugs.launchpad.net/bugs/1818879 Title: pull cirrus.ko into main kernel package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818879/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1719038] Re: X Server crashes during log in VM since 16.04.2
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 subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1719038 Title: X Server crashes during log in VM since 16.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1719038/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1755806] Re: X crashed, maybe related to touchpad
*** 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: Assertion `tp->tap.nfingers_down > 0' failed. -- 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/1755806 Title: X crashed, maybe related to touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1755806/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1751086] Re: Xorg assert failure: Xorg: ../src/evdev-mt-touchpad-tap.c:1002: tp_tap_handle_state: Assertion `tp->tap.nfingers_down > 0' failed.
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 Synaptics TouchPad: kernel bug: Touch jump detected and discarded. Mar 21 08:50:26 nsnx /usr/lib/gdm3/gdm-x-session[4968]: See https://wayland.freedesktop.org/libinput/doc/1.10.3/touchpad_jumping_cursor.html for details Mar 21 08:50:27 nsnx /usr/lib/gdm3/gdm-x-session[4968]: (EE) event5 - SynPS/2 Synaptics TouchPad: kernel bug: Touch jump detected and discarded. Mar 21 08:50:27 nsnx /usr/lib/gdm3/gdm-x-session[4968]: See https://wayland.freedesktop.org/libinput/doc/1.10.3/touchpad_jumping_cursor.html for details -- 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: Assertion `tp->tap.nfingers_down > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/1751086/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1751086] Re: Xorg assert failure: Xorg: ../src/evdev-mt-touchpad-tap.c:1002: tp_tap_handle_state: Assertion `tp->tap.nfingers_down > 0' failed.
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/doc/1.10.1//absolute_coordinate_ranges.html for details Mar 20 11:08:19 nsnx /usr/lib/gdm3/gdm-x-session[16817]: (EE) event5 - SynPS/2 Synaptics TouchPad: libinput bug: invalid tap event TAP_EVENT_PALM in state TAP_STATE_TAPPED Mar 20 11:08:19 nsnx /usr/lib/gdm3/gdm-x-session[16817]: (EE) event5 - SynPS/2 Synaptics TouchPad: libinput bug: invalid tap event TAP_EVENT_PALM in state TAP_STATE_TAPPED Mar 20 11:08:29 nsnx /usr/lib/gdm3/gdm-x-session[16817]: Xorg: ../src/evdev-mt-touchpad-tap.c:1002: tp_tap_handle_state: Assertion `tp->tap.nfingers_down > 0' failed. Mar 20 11:08:29 nsnx /usr/lib/gdm3/gdm-x-session[16817]: (EE) Mar 20 11:08:29 nsnx /usr/lib/gdm3/gdm-x-session[16817]: (EE) Backtrace: Mar 20 11:08:29 nsnx /usr/lib/gdm3/gdm-x-session[16817]: (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x565247c457fd] Mar 20 11:08:29 nsnx /usr/lib/gdm3/gdm-x-session[16817]: (EE) 1: /usr/lib/xorg/Xorg (0x565247a8d000+0x1bc599) [0x565247c49599] Mar 20 11:08:29 nsnx /usr/lib/gdm3/gdm-x-session[16817]: (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f28775c1000+0x12890) [0x7f28775d3890] Mar 20 11:08:29 nsnx /usr/lib/gdm3/gdm-x-session[16817]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xc7) [0x7f287720ee97] Mar 20 11:08:29 nsnx /usr/lib/gdm3/gdm-x-session[16817]: (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x141) [0x7f2877210801] Mar 20 11:08:29 nsnx /usr/lib/gdm3/gdm-x-session[16817]: (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (0x7f28771d+0x3039a) [0x7f287720039a] Mar 20 11:08:29 nsnx /usr/lib/gdm3/gdm-x-session[16817]: (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (0x7f28771d+0x30412) [0x7f2877200412] Mar 20 11:08:29 nsnx /usr/lib/gdm3/gdm-x-session[16817]: (EE) 7: /usr/lib/x86_64-linux-gnu/libinput.so.10 (0x7f28741aa000+0x1da40) [0x7f28741c7a40] Mar 20 11:08:29 nsnx /usr/lib/gdm3/gdm-x-session[16817]: (EE) 8: /usr/lib/x86_64-linux-gnu/libinput.so.10 (0x7f28741aa000+0x18e17) [0x7f28741c2e17] Mar 20 11:08:29 nsnx /usr/lib/gdm3/gdm-x-session[16817]: (EE) 9: /usr/lib/x86_64-linux-gnu/libinput.so.10 (0x7f28741aa000+0x1ad90) [0x7f28741c4d90] Mar 20 11:08:29 nsnx /usr/lib/gdm3/gdm-x-session[16817]: (EE) 10: /usr/lib/x86_64-linux-gnu/libinput.so.10 (0x7f28741aa000+0xf5e1) [0x7f28741b95e1] Mar 20 11:08:29 nsnx /usr/lib/gdm3/gdm-x-session[16817]: (EE) 11: /usr/lib/x86_64-linux-gnu/libinput.so.10 (libinput_dispatch+0x5f) [0x7f28741b560f] Mar 20 11:08:29 nsnx /usr/lib/gdm3/gdm-x-session[16817]: (EE) 12: /usr/lib/xorg/modules/input/libinput_drv.so (0x7f28743fa000+0x8988) [0x7f2874402988] Mar 20 11:08:29 nsnx /usr/lib/gdm3/gdm-x-session[16817]: (EE) 13: /usr/lib/xorg/Xorg (0x565247a8d000+0x1ba973) [0x565247c47973] Mar 20 11:08:29 nsnx /usr/lib/gdm3/gdm-x-session[16817]: (EE) 14: /usr/lib/xorg/Xorg (0x565247a8d000+0x1bd071) [0x565247c4a071] Mar 20 11:08:29 nsnx /usr/lib/gdm3/gdm-x-session[16817]: (EE) 15: /usr/lib/xorg/Xorg (0x565247a8d000+0x1ba7be) [0x565247c477be] Mar 20 11:08:29 nsnx /usr/lib/gdm3/gdm-x-session[16817]: (EE) 16: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f28775c1000+0x76db) [0x7f28775c86db] Mar 20 11:08:29 nsnx /usr/lib/gdm3/gdm-x-session[16817]: (EE) 17: /lib/x86_64-linux-gnu/libc.so.6 (clone+0x3f) [0x7f28772f188f] Mar 20 11:08:29 nsnx /usr/lib/gdm3/gdm-x-session[16817]: (EE) Mar 20 11:08:29 nsnx /usr/lib/gdm3/gdm-x-session[16817]: (EE) Mar 20 11:08:29 nsnx /usr/lib/gdm3/gdm-x-session[16817]: Fatal server error: Mar 20 11:08:29 nsnx /usr/lib/gdm3/gdm-x-session[16817]: (EE) Caught signal 6 (Aborted). Server aborting Mar 20 11:08:29 nsnx /usr/lib/gdm3/gdm-x-session[16817]: (EE) Mar 20 11:08:29 nsnx /usr/lib/gdm3/gdm-x-session[16817]: (EE) Mar 20 11:08:29 nsnx /usr/lib/gdm3/gdm-x-session[16817]: Please consult the The X.Org Foundation support Mar 20 11:08:29 nsnx /usr/lib/gdm3/gdm-x-session[16817]: #011 at http://wiki.x.org Mar 20 11:08:29 nsnx /usr/lib/gdm3/gdm-x-session[16817]: for help. Mar 20 11:08:29 nsnx /usr/lib/gdm3/gdm-x-session[16817]: (EE) Please also check the log file at "/home/andreas/.local/share/xorg/Xorg.0.log" for additional information. Mar 20 11:08:29 nsnx /usr/lib/gdm3/gdm-x-session[16817]: (EE) Mar 20 11:08:29 nsnx /usr/lib/gdm3/gdm-x-session[16817]: (II) AIGLX: Suspending AIGLX clients for VT switch Mar 20 11:08:30 nsnx /usr/lib/gdm3/gdm-x-session[16817]: (EE) Server terminated with error (1). Closing log file. All I need to do is swipe my palm from left to right over the touchpad. ** Attachment added: "swipe-of-death.mp4" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1751086/+attachment/5084938/+files/swipe-of-death.mp4 ** Changed in: libinput (Ubuntu) Status: Incomplete => Confirmed -- You received this bug
[Ubuntu-x-swat] [Bug 1751086] Re: Xorg assert failure: Xorg: ../src/evdev-mt-touchpad-tap.c:1002: tp_tap_handle_state: Assertion `tp->tap.nfingers_down > 0' failed.
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: Assertion `tp->tap.nfingers_down > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/1751086/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1755806] Re: X crashed, maybe related to touchpad
*** 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 discarded. Mar 14 09:54:21 nsnx /usr/lib/gdm3/gdm-x-session[5239]: See https://wayland.freedesktop.org/libinput/doc/1.10.1/touchpad_jumping_cursor.html for details Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: Xorg: ../src/evdev-mt-touchpad-tap.c:1028: tp_tap_handle_state: Assertion `tp->tap.nfingers_down >= 1' failed. Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) Backtrace: Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x55ab4d64391d] Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) 1: /usr/lib/xorg/Xorg (0x55ab4d48b000+0x1bc6b9) [0x55ab4d6476b9] Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fbf1f27f000+0x12890) [0x7fbf1f291890] Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xc7) [0x7fbf1eecce97] Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x141) [0x7fbf1eece801] Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (0x7fbf1ee8e000+0x3039a) [0x7fbf1eebe39a] Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (0x7fbf1ee8e000+0x30412) [0x7fbf1eebe412] Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) 7: /usr/lib/x86_64-linux-gnu/libinput.so.10 (0x7fbf1be69000+0x1d9e3) [0x7fbf1be869e3] Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) 8: /usr/lib/x86_64-linux-gnu/libinput.so.10 (0x7fbf1be69000+0x18e17) [0x7fbf1be81e17] Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) 9: /usr/lib/x86_64-linux-gnu/libinput.so.10 (0x7fbf1be69000+0x1ad90) [0x7fbf1be83d90] Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) 10: /usr/lib/x86_64-linux-gnu/libinput.so.10 (0x7fbf1be69000+0xf5e1) [0x7fbf1be785e1] Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) 11: /usr/lib/x86_64-linux-gnu/libinput.so.10 (libinput_dispatch+0x5f) [0x7fbf1be7460f] Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) 12: /usr/lib/xorg/modules/input/libinput_drv.so (0x7fbf1c0b8000+0x8988) [0x7fbf1c0c0988] Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) 13: /usr/lib/xorg/Xorg (0x55ab4d48b000+0x1baa93) [0x55ab4d645a93] Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) 14: /usr/lib/xorg/Xorg (0x55ab4d48b000+0x1bd191) [0x55ab4d648191] Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) 15: /usr/lib/xorg/Xorg (0x55ab4d48b000+0x1ba8de) [0x55ab4d6458de] Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) 16: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fbf1f27f000+0x76db) [0x7fbf1f2866db] Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) 17: /lib/x86_64-linux-gnu/libc.so.6 (clone+0x3f) [0x7fbf1efaf88f] Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: Fatal server error: Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) Caught signal 6 (Aborted). Server aborting Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: Please consult the The X.Org Foundation support Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: #011 at http://wiki.x.org Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: for help. Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) Please also check the log file at "/home/andreas/.local/share/xorg/Xorg.0.log" for additional information. Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (II) AIGLX: Suspending AIGLX clients for VT switch Mar 14 09:54:23 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) Server terminated with error (1). Closing log file. Mar 14 09:54:23 nsnx kernel: [30169.675729] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Mar 14 09:54:28 nsnx hexchat.desktop[8618]: hexchat: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Mar 14 09:54:28 nsnx update-notifier[8801]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. ** This bug has been marked a duplicate of private bug 1753735 -- You received this bug notification because you are a member of Ubuntu-X,
[Ubuntu-x-swat] [Bug 1755806] [NEW] X crashed, maybe related to touchpad
*** 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 the touchpad. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Wed Mar 14 09:57:47 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 (ThinkPad X1 Carbon 5th Gen) [17aa:224f] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 138a:0097 Validity Sensors, Inc. Bus 001 Device 003: ID 04f2:b5ce Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HRCTO1WW ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic.efi.signed root=ZFS=hostname/ROOT/ubuntu ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET41W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1MET41W(1.26):bd11/09/2017:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 5th dmi.product.name: 20HRCTO1WW dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- 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/1755806 Title: X crashed, maybe related to touchpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1755806/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1731796] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [gdbus:2878]
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: BUG: soft lockup - CPU#0 stuck for 23s! [gdbus:2878] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1731796/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1731796] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [gdbus:2878]
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 watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [gdbus:2878] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1731796/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1731796] Re: 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
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: BUG: soft lockup - CPU#0 stuck for 23s! [gdbus:2878] -- 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: BUG: soft lockup - CPU#0 stuck for 23s! [gdbus:2878] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1731796/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1731796] Re: 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
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: samba (Ubuntu) => nvidia-graphics-drivers (Ubuntu) -- 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: BUG: soft lockup - CPU#0 stuck for 23s! [gdbus:2878] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1731796/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1726595] Re: Running Matlab (R) from ssh session with X forwarding doesn't work anymore in 17.10
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 Mesa 17.2.2 So something to do with opengl over remote X11 connections. I'll switch the bug over to wayland, and maybe add a xorg task ** Package changed: openssh (Ubuntu) => wayland (Ubuntu) ** Changed in: wayland (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1726595 Title: Running Matlab (R) from ssh session with X forwarding doesn't work anymore in 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1726595/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 929384] Re: nvidia drivers broken by the recent libc update on i386 arch
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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/929384/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 929384] Re: nvidia drivers broken by the recent libc update on i386 arch
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, 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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/929384/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 927570] [NEW] Bad screen redraw with nouveau driver
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 DistroRelease: Ubuntu 12.04 Package: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 ProcVersionSignature: Ubuntu 3.2.0-14.23-generic-pae 3.2.3 Uname: Linux 3.2.0-14-generic-pae i686 .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 1.91-0ubuntu1 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,gnomecompat,compiztoolbox,mousepoll,wall,snap,imgpng,vpswitch,regex,resize,place,move,grid,session,animation,fade,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Mon Feb 6 09:23:18 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu DkmsStatus: nvidia-current-updates, 290.10, 3.2.0-14-generic-pae, i686: installed ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GraphicsCard: NVIDIA Corporation GF119 [Quadro NVS 4200M] [10de:1057] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21ce] InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha i386 (20120201.2) MachineType: LENOVO 4177CTO ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-14-generic-pae root=/dev/mapper/vg0-root ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/28/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET67WW (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 4177CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr83ET67WW(1.37):bd11/28/2011:svnLENOVO:pn4177CTO:pvrThinkPadT420:rvnLENOVO:rn4177CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4177CTO dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu8 version.libdrm2: libdrm2 2.4.30-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0~rc2-0ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0~rc2-0ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.11.3-0ubuntu10 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.99.901-1ubuntu3 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 precise reproducible running-unity single-occurrence ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/927570 Title: Bad screen redraw with nouveau driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/927570/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 927570] Re: Garbled screen with nouveau driver
** 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 doesn't + 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 DistroRelease: Ubuntu 12.04 Package: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 ProcVersionSignature: Ubuntu 3.2.0-14.23-generic-pae 3.2.3 Uname: Linux 3.2.0-14-generic-pae i686 .tmp.unity.support.test.0: - + .tmp.unity.support.test.1: - + ApportVersion: 1.91-0ubuntu1 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,gnomecompat,compiztoolbox,mousepoll,wall,snap,imgpng,vpswitch,regex,resize,place,move,grid,session,animation,fade,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Mon Feb 6 09:23:18 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu DkmsStatus: nvidia-current-updates, 290.10, 3.2.0-14-generic-pae, i686: installed ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GraphicsCard: - NVIDIA Corporation GF119 [Quadro NVS 4200M] [10de:1057] (rev a1) (prog-if 00 [VGA controller]) -Subsystem: Lenovo Device [17aa:21ce] + NVIDIA Corporation GF119 [Quadro NVS 4200M] [10de:1057] (rev a1) (prog-if 00 [VGA controller]) + Subsystem: Lenovo Device [17aa:21ce] InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha i386 (20120201.2) MachineType: LENOVO 4177CTO ProcEnviron: - LANGUAGE=en_US:en - PATH=(custom, user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_US:en + PATH=(custom, user) + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-14-generic-pae root=/dev/mapper/vg0-root ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/28/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET67WW (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 4177CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr83ET67WW(1.37):bd11/28/2011:svnLENOVO:pn4177CTO:pvrThinkPadT420:rvnLENOVO:rn4177CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4177CTO dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu8 version.libdrm2: libdrm2 2.4.30-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0~rc2-0ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0~rc2-0ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.11.3-0ubuntu10 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.99.901-1ubuntu3 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/927570 Title: Bad screen redraw with nouveau driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/927570/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 875309] Re: [Thinkpad T420] External video inoperative with Noveau
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 controller: nVidia Corporation Device 1057 (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device 21ce Flags: fast devsel, IRQ 16 Memory at f200 (32-bit, non-prefetchable) [size=16M] Memory at e000 (64-bit, prefetchable) [size=256M] Memory at f000 (64-bit, prefetchable) [size=32M] I/O ports at 5000 [size=128] Expansion ROM at f308 [disabled] [size=512K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Endpoint, MSI 00 Capabilities: [b4] Vendor Specific Information: Len=14 ? Capabilities: [100] Virtual Channel Capabilities: [128] Power Budgeting ? Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 ? Kernel modules: nouveau, nvidiafb -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/875309 Title: [Thinkpad T420] External video inoperative with Noveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/875309/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 685017] Re: Jockey should warn on insufficient disk space in LiveCD environment, else get error package nvidia-current 260.19.21-0ubuntu1 failed to install/upgrade: subprocess in
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-resolution-extra Suggested packages: diffutils-doc The following NEW packages will be installed: dkms fakeroot nvidia-current nvidia-settings patch screen-resolution-extra 0 upgraded, 6 newly installed, 0 to remove and 244 not upgraded. Need to get 27.6 MB of archives. After this operation, 81.8 MB of additional disk space will be used. Do you want to continue [Y/n]? Get:1 http://br.archive.ubuntu.com/ubuntu/ natty/main patch i386 2.6-3 [122 kB] Get:2 http://br.archive.ubuntu.com/ubuntu/ natty/main dkms all 2.1.1.2-5ubuntu1 [71.9 kB] Get:3 http://br.archive.ubuntu.com/ubuntu/ natty/main fakeroot i386 1.14.4-1ubuntu1 [118 kB] Get:4 http://br.archive.ubuntu.com/ubuntu/ natty/restricted nvidia-current i386 260.19.21-0ubuntu1 [26.4 MB] Get:5 http://br.archive.ubuntu.com/ubuntu/ natty/main screen-resolution-extra all 0.14 [13.9 kB] Get:6 http://br.archive.ubuntu.com/ubuntu/ natty/main nvidia-settings i386 260.19.21-0ubuntu2 [844 kB] Fetched 27.6 MB in 22s (1,218 kB/s) Selecting previously deselected package patch. (Reading database ... 129416 files and directories currently installed.) Unpacking patch (from .../archives/patch_2.6-3_i386.deb) ... Selecting previously deselected package dkms. Unpacking dkms (from .../dkms_2.1.1.2-5ubuntu1_all.deb) ... Selecting previously deselected package fakeroot. Unpacking fakeroot (from .../fakeroot_1.14.4-1ubuntu1_i386.deb) ... Selecting previously deselected package nvidia-current. Unpacking nvidia-current (from .../nvidia-current_260.19.21-0ubuntu1_i386.deb) ... Selecting previously deselected package screen-resolution-extra. Unpacking screen-resolution-extra (from .../screen-resolution-extra_0.14_all.deb) ... Selecting previously deselected package nvidia-settings. Unpacking nvidia-settings (from .../nvidia-settings_260.19.21-0ubuntu2_i386.deb) ... Processing triggers for man-db ... Setting up patch (2.6-3) ... Setting up dkms (2.1.1.2-5ubuntu1) ... Setting up fakeroot (1.14.4-1ubuntu1) ... update-alternatives: using /usr/bin/fakeroot-sysv to provide /usr/bin/fakeroot (fakeroot) in auto mode. Setting up nvidia-current (260.19.21-0ubuntu1) ... update-alternatives: using /usr/lib/nvidia-current/ld.so.conf to provide /etc/ld.so.conf.d/GL.conf (gl_conf) in auto mode. update-alternatives: warning: skip creation of /usr/lib32/vdpau/libvdpau_nvidia.so.1 because associated file /usr/lib32/nvidia-current/vdpau/libvdpau_nvidia.so.1 (of link group gl_conf) doesn't exist. update-alternatives: warning: skip creation of /usr/lib32/libvdpau_nvidia.so because associated file /usr/lib32/nvidia-current/vdpau/libvdpau_nvidia.so (of link group gl_conf) doesn't exist. update-initramfs: deferring update (trigger activated) cp: cannot stat `/vmlinuz': No such file or directory dpkg: error processing nvidia-current (--configure): subprocess installed post-installation script returned error exit status 1 Setting up screen-resolution-extra (0.14) ... Processing triggers for python-central ... Setting up nvidia-settings (260.19.21-0ubuntu2) ... Processing triggers for python-gmenu ... Rebuilding /usr/share/applications/desktop.en_US.utf8.cache... Processing triggers for bamfdaemon ... Rebuilding /usr/share/applications/bamf.index... Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.37-7-generic cryptsetup: WARNING: failed to detect canonical device of aufs cryptsetup: WARNING: could not determine root device from /etc/fstab cp: cannot stat `/vmlinuz': No such file or directory dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for python-support ... Errors were encountered while processing: nvidia-current initramfs-tools E: Sub-process /usr/bin/dpkg returned an error code (1) r...@ubuntu:~# -- 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: Jockey should warn on insufficient disk space in LiveCD environment, else get error package nvidia-current 260.19.21-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help :
[Ubuntu-x-swat] [Bug 685017] Re: Jockey should warn on insufficient disk space in LiveCD environment, else get error package nvidia-current 260.19.21-0ubuntu1 failed to install/upgrade: subprocess in
/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-12-01 04:00 abi-2.6.37-7-generic -rw-r--r-- 1 root root 132160 2010-12-01 04:00 config-2.6.37-7-generic drwxr-xr-x 2 root root 60 2010-12-08 13:10 grub/ -rw-r--r-- 1 root root 17922686 2010-12-08 13:16 initrd.img-2.6.37-7-generic -rw-r--r-- 1 root root 160988 2010-10-22 11:43 memtest86+.bin -rw-r--r-- 1 root root 163168 2010-10-22 11:43 memtest86+_multiboot.bin -rw-r--r-- 1 root root 1939255 2010-12-01 04:00 System.map-2.6.37-7-generic -rw-r--r-- 1 root root 1191 2010-12-01 04:02 vmcoreinfo-2.6.37-7-generic -- 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: Jockey should warn on insufficient disk space in LiveCD environment, else get error package nvidia-current 260.19.21-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 685017] Re: package nvidia-current 260.19.21-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
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 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 685017] Re: Jockey should warn on insufficient disk space in LiveCD environment, else get error package nvidia-current 260.19.21-0ubuntu1 failed to install/upgrade: subprocess in
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.launchpad.net/bugs/685017 Title: Jockey should warn on insufficient disk space in LiveCD environment, else get error package nvidia-current 260.19.21-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 685017] Re: Jockey should warn on insufficient disk space in LiveCD environment, else get error package nvidia-current 260.19.21-0ubuntu1 failed to install/upgrade: subprocess in
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 /dev/sde1 3.8G 1.3G 2.6G 32% /cdrom /dev/loop0684M 684M 0 100% /rofs none 1006M 104K 1006M 1% /dev/shm tmpfs1006M 28K 1006M 1% /tmp none 1006M 88K 1006M 1% /var/run none 1006M 4.0K 1006M 1% /var/lock ubu...@ubuntu:~$ I did create this USB boot pendrive using 512Mb of space for documents and settings, FWIW. Here is the mount output: ubu...@ubuntu:~$ mount aufs on / type aufs (rw) none on /proc type proc (rw,noexec,nosuid,nodev) none on /sys type sysfs (rw,noexec,nosuid,nodev) fusectl on /sys/fs/fuse/connections type fusectl (rw) none on /dev type devtmpfs (rw,mode=0755) none on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620) /dev/sde1 on /cdrom type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro) /dev/loop0 on /rofs type squashfs (ro,noatime) none on /sys/kernel/debug type debugfs (rw) none on /sys/kernel/security type securityfs (rw) none on /dev/shm type tmpfs (rw,nosuid,nodev) tmpfs on /tmp type tmpfs (rw,nosuid,nodev) none on /var/run type tmpfs (rw,nosuid,mode=0755) none on /var/lock type tmpfs (rw,noexec,nosuid,nodev) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev) gvfs-fuse-daemon on /home/ubuntu/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=ubuntu) -- 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: Jockey should warn on insufficient disk space in LiveCD environment, else get error package nvidia-current 260.19.21-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 685017] [NEW] package nvidia-current 260.19.21-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
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: Ubuntu 11.04 Package: nvidia-current 260.19.21-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.37-7.19-generic 2.6.37-rc3 Uname: Linux 2.6.37-7-generic i686 Architecture: i386 Date: Fri Dec 3 23:57:10 2010 DkmsStatus: ErrorMessage: subprocess installed post-installation script returned error exit status 1 GdmLog1: Error: command ['cat', '/var/log/gdm/:0.log.1'] failed with exit code 1: cat: /var/log/gdm/:0.log.1: No such file or directory GdmLog2: Error: command ['cat', '/var/log/gdm/:0.log.2'] failed with exit code 1: cat: /var/log/gdm/:0.log.2: No such file or directory LiveMediaBuild: Ubuntu 11.04 Natty Narwhal - Alpha i386 (20101203) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity SourcePackage: nvidia-graphics-drivers Title: package nvidia-current 260.19.21-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 dmi.bios.date: 11/23/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1226 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5B-Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1226:bd11/23/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer glxinfo: Error: [Errno 2] No such file or directory system: distro: Ubuntu codename: natty architecture: i686 kernel: 2.6.37-7-generic ** Affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 natty -- 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 script returned error exit status 1 ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 685017] Re: package nvidia-current 260.19.21-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
-- 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 script returned error exit status 1 ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 538071] Re: KMS driver blacklisting with /usr on separate partition fails (Lucid)
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 S word) and say why, even if it's obvious to you. -- KMS driver blacklisting with /usr on separate partition fails (Lucid) https://bugs.launchpad.net/bugs/538071 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 538071] Re: Nouveau blacklisting with /usr on seperate partition fails (Lucid Alpha3)
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 off. It doesn't fit the screen anymore. Did you guys also get this? It started happening at exactly the first boot after I installed the nvidia driver. ** Attachment added: 2010-04-05 08.56.49.jpg http://launchpadlibrarian.net/43152284/2010-04-05%2008.56.49.jpg -- 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-X, which is subscribed to nvidia-graphics-drivers in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 538071] Re: Nouveau blacklisting with /usr on seperate partition fails (Lucid Alpha3)
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-X, which is subscribed to nvidia-graphics-drivers in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 535339] Re: nvidia/lucid deinstall of nvidia'current causes X11 mayhem
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, which is subscribed to nvidia-graphics-drivers in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 538071] Re: Nouveau blacklisting with /usr on seperate partition fails (Lucid Alpha3)
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-X, which is subscribed to nvidia-graphics-drivers in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 538071] Re: Nouveau blacklisting with /usr on seperate partition fails (Lucid Alpha3)
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) https://bugs.launchpad.net/bugs/538071 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 372725] Re: thinkpad t61 slash/question key not working
*** 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 a member of Ubuntu-X, which is subscribed to xserver-xorg-input-keyboard in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
