[Ubuntu-x-swat] [Bug 1769819] Re: Xorg crashes after system sleep / wakeup

It's at the top of bug 994921. Additionally, or alternatively please uncomment this option from /etc/gdm3/custom.conf: # Additionally lets the X server dump core if it crashes #Enable=true and reboot. -- You received this bug notification because you are a member of Ubuntu-X, which is subscrib

[Ubuntu-x-swat] [Bug 1769819] Re: Xorg crashes after system sleep / wakeup

can you be more specific about the workaround. I read but 994921, but didn't find a clear reference as to what would need to be done -- 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/1769819 T

[Ubuntu-x-swat] [Bug 1769824] [NEW] Xorg crash

Public bug reported: System was idle at the time. It displayed the background wall paper, but did NOT display the login screen. I had to go to console, and restart lightdm. Wayno ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.2

[Ubuntu-x-swat] [Bug 1769822] [NEW] VGA Resolution Detect with KVM

Public bug reported: Detects fine with direct connect, but when through kvm (works fine with windows) will not detect proper resolution. Log files should show: 1. Boot with KVM attached. 2. Plug monitor direct to motherboard (bypass) - old resolution for instant, then change to proper resolutio

[Ubuntu-x-swat] [Bug 1769819] Re: Xorg crashes after system sleep / wakeup

In order to debug a crash we will need a crash report. To create one, please: 1. Apply the workaround from bug 994921. 2. Reproduce the crash. 3. Look in /var/crash for crash files and when found, run: ubuntu-bug /var/crash/YOURFILE.crash 4. Add a comment here telling us the ID of the new bu

[Ubuntu-x-swat] [Bug 1769819] [NEW] Xorg crashes after system sleep / wakeup

Public bug reported: after putting the system to sleep, and waking it up, Xorg crashes, and I'm lead to a new greeter / login screen. naturally the state of my desktop is lost in this process, and I'm stuck with a new login with no apps running. the error reporter says: Error: [Errno 21] is a di

[Ubuntu-x-swat] [Bug 1754296] Re: [bionic] startx / xinit crashes with GLX backtrace if Composite Disabled in xorg.conf (intel mesa driver)

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) -- 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/1754296 Title: [bionic] startx / xinit crashes with GLX backtrace if Composite D

[Ubuntu-x-swat] [Bug 1754177] Re: [bionic] xserver / startx crashes with Composite Disabled in xorg.conf

*** This bug is a duplicate of bug 1754296 *** https://bugs.launchpad.net/bugs/1754296 ** This bug has been marked a duplicate of bug 1754296 [bionic] startx / xinit crashes with GLX backtrace if Composite Disabled in xorg.conf (intel mesa driver) -- You received this bug notification be

[Ubuntu-x-swat] [Bug 1754177] Re: [bionic] xserver / startx crashes with Composite Disabled in xorg.conf

[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launc

[Ubuntu-x-swat] [Bug 1720820] Re: [radeon] Totem with gstreamer1.0-vaapi and Wayland is just a black screen, then crashes.

See also bug 1767312. ** Summary changed: - Totem with gstreamer1.0-vaapi and Wayland is just a black screen, then crashes on AMD/radeon graphics + [radeon] Totem with gstreamer1.0-vaapi and Wayland is just a black screen, then crashes. ** No longer affects: totem (Ubuntu) -- You received th

[Ubuntu-x-swat] [Bug 1767312] Re: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos

** Summary changed: - [radeon] totem wrong color on h264 videos + [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos ** Description changed: Ii've found a bug on Ubuntu 18.04 (other distros, as fedora 27, debian stable, debian testing) aren't affected). When i try t

[Ubuntu-x-swat] [Bug 1767559] Re: Provide libinput 1.10.6 in bionic-updates to fix specific touchpad and keyboard issues

We now have version 1.10.6 in cosmic :) Q: What else do I need to do to get this provided as an SRU to Bionic? A: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure Although the prerequisite for a bionic SRU has been met (cosmic updated first), I suggest it might be better engineering practic

[Ubuntu-x-swat] [Bug 1762536] Re: double tap on touchpad isn't recognized as double click on ubuntu 18.04 bionic

That's correct. We can, in theory, consider upgrading libinput in 18.04 so long as it's to a bug fix release only. Not a feature release. So yeah we could consider 1.10.5/6 for bionic. Longer term however it will be interesting to see how we handle bug fixes to bionic's libinput. Especially after

[Ubuntu-x-swat] [Bug 1767559] Re: Provide libinput 1.10.6 in bionic-updates to fix specific touchpad and keyboard issues

** Summary changed: - Provide libinput 1.10.5 in bionic-updates to fix specific touchpad and keyboard issues + Provide libinput 1.10.6 in bionic-updates to fix specific touchpad and keyboard issues ** Description changed: - This is an SRU request to bring the libinput 1.10.5 microrelease to +

[Ubuntu-x-swat] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

Is there any way possible to gain early access to the "FIX RELEASED" files??? -- 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/1752053 Title: nvidia-390 fails to boot graphical display To manage

[Ubuntu-x-swat] [Bug 1762536] Re: double tap on touchpad isn't recognized as double click on ubuntu 18.04 bionic

libinput10 1.10.5 does have that fix. seems to be fixed in cosmic ubuntu 18.10 daily since 2018-05-06. (double tap is working as expected) but bionic ubuntu 18.04 LTS release still uses libinput10 (1.10.4) (got no upgrade to 1.10.5 yet) -- You received this bug notification because you are a me

[Ubuntu-x-swat] [Bug 1769727] Re: Black Screen on Wake

see also: https://bugs.launchpad.net/ubuntu-mate/+bug/1769726 older references: https://bugs.launchpad.net/ubuntu-mate/+bug/1688716/+activity -- 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/1769727

[Ubuntu-x-swat] [Bug 1769727] [NEW] Black Screen on Wake

Public bug reported: Mate 18.04 (64bit) MacbookAir 1,1 Intel i915 Blackscreen after every resume. All other features work. Just no backlight. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-2

[Ubuntu-x-swat] [Bug 1769500] Re: will not update

** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1769500 Title: will not update To manage notifications about this bug go to: https://b

[Ubuntu-x-swat] [Bug 1757180] Re: nvidia-prime can't switch off the discrete GPU

And more. Different output of the command: cat /sys/kernel/debug/vgaswitcheroo/switch nouveau driver: 0:IGD:+:Pwr::00:02.0 1:DIS: :DynOff::01:00.0 nvidia 390.48, after prime-select intel: 0:IGD:+:Pwr::00:02.0 1:DIS: :Off::01:00.0 You can see the different status of the discrete c

[Ubuntu-x-swat] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

Back to where I started with a non-bootable machine, after modifying xorg.conf listed in post #121. I will go aheada purge these nvidia drivers again, and try #123 to see if that works. This is a crazy mess!! -- You received this bug notification because you are a member of Ubuntu-X, which is s

[Ubuntu-x-swat] [Bug 1769616] Re: pc no stop

*** This bug is a duplicate of bug 1769615 *** https://bugs.launchpad.net/bugs/1769615 ** This bug has been marked a duplicate of bug 1769615 pc no stop -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpa

[Ubuntu-x-swat] [Bug 1588192] Re: GL interfaces seem wedged for Krita on nvidia

I'm marking the snappy task as fix released. We have greatly improved nvidia support from Ubuntu 16.04 to Ubuntu 18.04 and on other distributions as well. Please reopen if you find it still affects you somehow. ** Changed in: snappy Status: In Progress => Fix Released -- You received this

[Ubuntu-x-swat] [Bug 1769616] [NEW] pc no stop

Public bug reported: mon ne veut pas s'arrêter merci ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7 Architecture:

[Ubuntu-x-swat] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

I just tested the thing in #123 and I can only conclude: i am writing this note in 18.04 with nvidia-396 drivers on a Lenovo Y720. So I can only agree to what Thijs says. This sounds like a timing problem. -- You received this bug notification because you are a member of Ubuntu-X, which is su

[Ubuntu-x-swat] [Bug 1769615] [NEW] pc no stop

Public bug reported: mon pc ne veut pas s'arrêter Merci ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7 Architec

[Ubuntu-x-swat] [Bug 1767559] Re: Provide libinput 1.10.5 in bionic-updates to fix specific touchpad and keyboard issues

I can see libinput 1.10.5 is now in Cosmic: https://packages.ubuntu.com/cosmic/libinput10 What else do I need to do to get this provided as an SRU to Bionic? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libinput in Ubuntu. https://bugs.launch

Re: [Ubuntu-x-swat] [Bug 1769029] Re: Display on Dell 1440x900 is not available

And now it is working on Dell 1440x900. Thanks a lot for the immediate support. -VK Joseph On Sat, May 5, 2018 at 12:29 PM, Launchpad Bug Tracker < 1769...@bugs.launchpad.net> wrote: > Status changed to 'Confirmed' because the bug affects multiple users. > > ** Changed in: xorg (Ubuntu) >

[Ubuntu-x-swat] [Bug 1737598] Re: Xorg crashed with SIGABRT [SIGSEGV in open_restricted (path=0x0...]

** Summary changed: - Xorg crashed with SIGABRT + Xorg crashed with SIGABRT [SIGSEGV in open_restricted (path=0x0...] -- 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/1737598 Title: Xorg c

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

I've just done a little tidy up of some of the hottest xorg-server crashes. This one is presently #64 of the xorg-server crashes affecting bionic. There have been 7 reports of it on errors.ubuntu.com in the past year. -- You received this bug notification because you are a member of Ubuntu-X, whi

[Ubuntu-x-swat] [Bug 1753963] Re: Xorg crashed with SIGABRT [SEGV in recreate_growing_buffer() from intel_batchbuffer_reset()]

** Summary changed: - Xorg crashed with SIGABRT + Xorg crashed with SIGABRT [SEGV in recreate_growing_buffer() from intel_batchbuffer_reset()] -- 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/bug

[Ubuntu-x-swat] [Bug 1751508] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from InitOutput()

See also: https://errors.ubuntu.com/problem/d239c29b34bc845bb8b3ede5c7e671a0ae269955 -- 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

[Ubuntu-x-swat] [Bug 1736146] Re: Xorg crashed with SIGABRT

** Information type changed from Private to Public ** Summary changed: - Xorg crashed with SIGABRT + Xorg crashed with SIGABRT [SIGSEGV in list_del() from pb_slab_reclaim()] ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags added: radeon -- You received this b

[Ubuntu-x-swat] [Bug 1279274] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from exaPrepareAccessReg_mixed()

** Summary changed: - Xorg crashed with SIGABRT in OsAbort(EXA: malloc failed for size) + Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from exaPrepareAccessReg_mixed() -- You received this bug notification because you are a member of Ubuntu-X, which is subscri

[Ubuntu-x-swat] [Bug 1234095] Re: [xmir] Xorg crashed with SIGABRT in OsAbort()

Thank you for reporting this bug to Ubuntu. Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But

[Ubuntu-x-swat] [Bug 1297409] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from OsSigHandler(signo=11) from ??

Unfortunately we're missing information about what code location crashed. ** Summary changed: - Xorg crashed with SIGABRT in OsAbort() + Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from OsSigHandler(signo=11) from ?? ** Changed in: xorg-server (Ubuntu)

[Ubuntu-x-swat] [Bug 1341037] Re: Xorg crashed with SIGABRT in OsAbort()

*** This bug is a duplicate of bug 1338492 *** https://bugs.launchpad.net/bugs/1338492 ** This bug has been marked a duplicate of bug 1338492 Xorg crashed with SIGABRT in OsAbort() -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-serv

[Ubuntu-x-swat] [Bug 1502518] Re: Xorg crashed with SIGABRT in OsAbort()

Thank you for reporting this bug to Ubuntu. Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016. Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old a

[Ubuntu-x-swat] [Bug 1597654] Re: Xorg crashed with SIGABRT during system resume after suspend

*** This bug is a duplicate of bug 1421808 *** https://bugs.launchpad.net/bugs/1421808 ** This bug has been marked a duplicate of bug 1421808 Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xf86VTEnter() -- You received this bug notification because you a

[Ubuntu-x-swat] [Bug 1615540] Re: Xorg crashes with modeset driver on kernel 4.8-rc3 with SIGABRT in OsAbort()

** Changed in: xorg-server (Ubuntu) Status: Confirmed => Fix Released -- 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/1615540 Title: Xorg crashes with modeset driver on kernel 4.8-r

[Ubuntu-x-swat] [Bug 1714627] Re: Xorg crashed with SIGABRT in OsAbort()

*** This bug is a duplicate of bug 1543192 *** https://bugs.launchpad.net/bugs/1543192 ** This bug is no longer a duplicate of private bug 1562639 ** This bug has been marked a duplicate of bug 1543192 Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from dix_mai

[Ubuntu-x-swat] [Bug 1640146] Re: Xserver crashes (SIGABRT) when switching tty

*** This bug is a duplicate of bug 1421808 *** https://bugs.launchpad.net/bugs/1421808 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1421808, so it is being marked as such. Please look

[Ubuntu-x-swat] [Bug 1716687] Re: Xorg crashed with SIGABRT in OsAbort()

*** This bug is a duplicate of bug 1543192 *** https://bugs.launchpad.net/bugs/1543192 ** This bug is no longer a duplicate of private bug 1562639 ** This bug has been marked a duplicate of bug 1543192 Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from dix_mai

[Ubuntu-x-swat] [Bug 1726696] Re: Xorg crashed with SIGABRT in OsAbort()

*** This bug is a duplicate of bug 1543192 *** https://bugs.launchpad.net/bugs/1543192 ** This bug is no longer a duplicate of private bug 1562639 ** This bug has been marked a duplicate of bug 1543192 Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from dix_mai

[Ubuntu-x-swat] [Bug 1745799] Re: OsAbort() from AbortServer() from FatalError() from xwl_log_handler() from wl_log() ["wl_registry@2: error 0: invalid global wl_output (20)\n"]

** Summary changed: - Xwayland crashed with SIGABRT in OsAbort() + OsAbort() from AbortServer() from FatalError() from xwl_log_handler() from wl_log() ["wl_registry@2: error 0: invalid global wl_output (20)\n"] -- You received this bug notification because you are a member of Ubuntu-X, which is

[Ubuntu-x-swat] [Bug 1746656] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_log_handler() from wl_log() ["wl_drm@4: error 0: authenicate failed\n"]

** Summary changed: - Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_log_handler() from wl_log() + Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_log_handler() from wl_log() ["wl_drm@4: error 0: authenicate fail

[Ubuntu-x-swat] [Bug 1751508] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from InitOutput()

** Summary changed: - Xwayland crashed with SIGABRT in OsAbort() + Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from InitOutput() -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://

[Ubuntu-x-swat] [Bug 1673649] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xf86PostProbe()

** Summary changed: - Xorg crashed with SIGABRT in OsAbort() + Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xf86PostProbe() -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.