[Ubuntu-x-swat] [Bug 1876867] Re: [nvidia] Xorg process loads CPU heavily after resuming suspended laptop HP Probook 470 G4

2021-11-29 Thread Beowulf
I don't experience this issue anymore, it can be closed. -- 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/1876867 Title: [nvidia] Xorg process loads CPU heavily after resuming suspended l

[Ubuntu-x-swat] [Bug 1751508] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("Couldn't add screen\n") from InitOutput()

2021-11-29 Thread Daniel van Vugt
Yep OK it's definitely in jammy now. ** Also affects: xwayland (Ubuntu) Importance: Undecided Status: New ** Changed in: xwayland (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in

[Ubuntu-x-swat] [Bug 1952619] Re: Xwayland crashed with SIGABRT in __libc_start_call_main()

2021-11-29 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1751508 *** https://bugs.launchpad.net/bugs/1751508 After getting an identical Xwayland crash on my own machine today I can confirm it really is bug 1751508. ** This bug has been marked a duplicate of bug 1751508 Xwayland crashed with SIGABRT in OsAbort()

[Ubuntu-x-swat] [Bug 1952709] Re: /usr/bin/Xwayland:6:OsAbort:AbortServer:FatalError:InitOutput:dix_main

2021-11-29 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1751508 *** https://bugs.launchpad.net/bugs/1751508 ** This bug has been marked a duplicate of bug 1751508 Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("Couldn't add screen\n") from InitOutput() -- You received this bug

[Ubuntu-x-swat] [Bug 1952619] Re: Xwayland crashed with SIGABRT in __libc_start_call_main()

2021-11-29 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1751508 *** https://bugs.launchpad.net/bugs/1751508 See also bug 1952708 (currently private) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1952619 Titl

[Ubuntu-x-swat] [Bug 1952709] [NEW] /usr/bin/Xwayland:6:OsAbort:AbortServer:FatalError:InitOutput:dix_main

2021-11-29 Thread errors.ubuntu.com bug bridge
*** This bug is a duplicate of bug 1751508 *** https://bugs.launchpad.net/bugs/1751508 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:21.1.2-0ubuntu1, the problem pag

[Ubuntu-x-swat] [Bug 1952708] Re: Xwayland crashed with SIGABRT in __libc_start_call_main()

2021-11-29 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1751508 *** https://bugs.launchpad.net/bugs/1751508 See also bug 1952619 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1952708 Title: Xwayland crashe

[Ubuntu-x-swat] [Bug 1751508] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("Couldn't add screen\n") from InitOutput()

2021-11-29 Thread Apport retracing service
** Tags added: jammy -- 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/1751508 Title: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("Couldn't add screen\n")

[Ubuntu-x-swat] [Bug 1952708] Re: Xwayland crashed with SIGABRT in __libc_start_call_main()

2021-11-29 Thread Apport retracing service
*** This bug is a duplicate of bug 1751508 *** https://bugs.launchpad.net/bugs/1751508 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1751508, so is being marked as such.

[Ubuntu-x-swat] [Bug 1952619] Re: Xwayland crashed with SIGABRT in __libc_start_call_main()

2021-11-29 Thread Daniel van Vugt
Please also ensure you have libmutter >= 40.5-1ubuntu3 for bug 1948894. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1952619 Title: Xwayland crashed with SIGABRT in __libc_start_call_main(

[Ubuntu-x-swat] [Bug 1751508] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("Couldn't add screen\n") from InitOutput()

2021-11-29 Thread Daniel van Vugt
** Tags removed: jammy -- 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/1751508 Title: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("Couldn't add screen\n

[Ubuntu-x-swat] [Bug 1952619] Re: Xwayland crashed with SIGABRT in __libc_start_call_main()

2021-11-29 Thread Daniel van Vugt
Look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent Xwayland crashes on that page? If so then please send the links to us. ** This bug is no longer a duplicate of bug 1751508 Xwayland crashed wit

[Ubuntu-x-swat] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"

2021-11-29 Thread Seth Forshee
** Changed in: linux-firmware (Ubuntu) Assignee: Seth Forshee (sforshee) => (unassigned) -- 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/1928393 Title: linux-firmware 1.197 causes kernel to

[Ubuntu-x-swat] [Bug 1952619] Re: Xwayland crashed with SIGABRT in __libc_start_call_main()

2021-11-29 Thread Jonathan Kamens
*** This bug is a duplicate of bug 1751508 *** https://bugs.launchpad.net/bugs/1751508 It's hard to see why the retracing service marked this as a duplicate of 1751508. I'm fairly certain it is not. -- You received this bug notification because you are a member of Ubuntu-X, which is subscrib

[Ubuntu-x-swat] [Bug 1751508] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("Couldn't add screen\n") from InitOutput()

2021-11-29 Thread Apport retracing service
** Tags added: jammy -- 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/1751508 Title: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("Couldn't add screen\n")

[Ubuntu-x-swat] [Bug 1952619] Re: Xwayland crashed with SIGABRT in __libc_start_call_main()

2021-11-29 Thread Apport retracing service
*** This bug is a duplicate of bug 1751508 *** https://bugs.launchpad.net/bugs/1751508 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1751508, so is being marked as such.

[Ubuntu-x-swat] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"

2021-11-29 Thread Juerg Haefliger
@antonio-petricca, What series? What kernel? I can produce a hirsute linux-firmware package with the reverted sdma firmware but need someone to verify it on hirsute with the hirsute kernel. Any takers? Or have you all moved on to impish? -- You received this bug notification because you are a me

[Ubuntu-x-swat] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"

2021-11-29 Thread Lancillotto
With latest firmare https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/snapshot/linux-firmware-20211027.tar.gz is much more stable. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.n

[Ubuntu-x-swat] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"

2021-11-29 Thread Juerg Haefliger
** Also affects: mesa (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Hirsute) Importance: Undecided Status: New ** No longer affects: mesa (Ubuntu Hirsute) ** Changed in: mesa (Ubuntu) Status: Confirmed => Invalid ** Changed

[Ubuntu-x-swat] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"

2021-11-29 Thread Juerg Haefliger
@antonio-petricca, sorry but 5.15.2 is not a supported Ubuntu kernel and especially not on Bionic with (old) Bionic firmware. -- 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/1928393 Title: linux-

[Ubuntu-x-swat] [Bug 1952581] Re: ACPI Error: No handler for Region [VRTC]

2021-11-29 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => linux (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/1952581 Title: ACPI Error: No handler for Region [VRTC] To manage notifications about this bug

[Ubuntu-x-swat] [Bug 1952581] Re: ACPI Error: No handler for Region [VRTC]

2021-11-29 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (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/1952581 Title: ACPI Error: No handler for Region [VRTC] To manage notifications about this bug go to:

[Ubuntu-x-swat] [Bug 1952581] [NEW] ACPI Error: No handler for Region [VRTC]

2021-11-29 Thread Launchpad Bug Tracker
You have been subscribed to a public bug: >From sniffing around seems to be something Kernal related specific to the >recent Razor Blade laptops with GPUs. https://bugzilla.kernel.org/show_bug.cgi?id=205665 I don't think its Xorg but its graphic related? Fully documented here with screen shot h