[Ubuntu-x-swat] [Bug 1821385] Re: Xwayland crashed with SIGABRT in wl_proxy_destroy() from wl_callback_destroy() from xwl_present_sync_callback() from ffi_call_unix64()

2019-03-25 Thread Bug Watch Updater
** Changed in: xorg-server Status: Unknown => 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/1821385 Title: Xwayland crashed with SIGABRT in wl_proxy_destroy() from

[Ubuntu-x-swat] [Bug 1816004] Re: GLVND: AARCH64 : Fix address passed to clear cache

2019-03-25 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libglvnd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libglvnd in Ubuntu. https://bugs.launchpad.net/bugs/1816004 T

[Ubuntu-x-swat] [Bug 1821385] Re: Xwayland crashed with SIGABRT in wl_proxy_destroy() from wl_callback_destroy() from xwl_present_sync_callback() from ffi_call_unix64()

2019-03-25 Thread Daniel van Vugt
** Bug watch added: gitlab.freedesktop.org/xorg/xserver/issues #645 https://gitlab.freedesktop.org/xorg/xserver/issues/645 ** Changed in: xorg-server Status: Fix Released => Unknown ** Changed in: xorg-server Remote watch: gitlab.freedesktop.org/xorg/xserver/issues #672 => gitlab.free

[Ubuntu-x-swat] [Bug 1821385] Re: Xwayland crashed with SIGABRT in wl_proxy_destroy() from wl_callback_destroy() from xwl_present_sync_callback() from ffi_call_unix64()

2019-03-25 Thread Bug Watch Updater
** Changed in: xorg-server Status: New => 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/1821385 Title: Xwayland crashed with SIGABRT in wl_proxy_destroy() from wl_c

[Ubuntu-x-swat] [Bug 1813160] Re: display problem

2019-03-25 Thread Launchpad Bug Tracker
[Expired for xserver-xorg-video-intel (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-vi

[Ubuntu-x-swat] [Bug 1821609] Re: Xorg freeze - fails to start or stay going screen blanks-grub seems involved

2019-03-25 Thread Daniel van Vugt
You seem to be booting in recovery mode, which will also break graphics support in its own way :/ Please: 1. Reboot and as soon as the purple screen appears tap Escape. Now choose a normal kernel and not recovery. 2. Reproduce the problem. 3. Reboot again into recovery mode if you need to. 4.

[Ubuntu-x-swat] [Bug 1821525] Re: totem assert failure: totem: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.

2019-03-25 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1818862 *** https://bugs.launchpad.net/bugs/1818862 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 1818862, so it is being marked as such. Please look

[Ubuntu-x-swat] [Bug 1821426] Re: Ubuntu 19.14 disco will not boot on Dell Precision5530

2019-03-25 Thread Daniel van Vugt
Please run: apport-collect 1821426 to send us more information about the machine. Please also try these potential workarounds and let us know which one(s) work: (a) Edit /etc/gdm3/custom.conf and uncomment the line: #WaylandEnable=false and reboot. (b) Disable integrated graphics/G

[Ubuntu-x-swat] [Bug 1821426] Re: Ubuntu 19.14 disco will not boot on Dell Precision5530

2019-03-25 Thread Brian Murray
** 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/1821426 Title: Ubuntu 19.14 disco will not boot on Dell Precision5530 To manage notifications about th

[Ubuntu-x-swat] [Bug 1821426] [NEW] Ubuntu 19.14 disco will not boot on Dell Precision5530

2019-03-25 Thread Launchpad Bug Tracker
You have been subscribed to a public bug: I'm uncertain which package is causing the problem, though I strongly suspect it may be nvidia related. This laptop runs 18.10 just fine, but attempting to boot 19.04 from a USB disk (tried multiple USB boot disks) results in a blank screen after Grub. Th

[Ubuntu-x-swat] [Bug 1815693] Re: Kubuntu 18.10 Xorg severe memory leak

2019-03-25 Thread Elton
It's unlikely that its a bug affecting the current distributions of Mesa, as I compile and install newer versions of Mesa every day from the Obilaf ppa. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad

[Ubuntu-x-swat] [Bug 1815693] Re: Kubuntu 18.10 Xorg severe memory leak

2019-03-25 Thread Elton
This bug also affects me. My computer has an AMD R9 280x GPU, a 16 gigs RAM, as well as a Core i7 processor. The memory allocated to Xorg triples and sometimes takes up all the available RAM when switching from themes, as from a dark theme to a light theme for instance. Kubuntu 18.10 with backports

[Ubuntu-x-swat] [Bug 1821533] Re: drm fails to accept edid version 2.4

2019-03-25 Thread Rich Drewes
** Summary changed: - failure to detect and use Intel 620 graphics pci id 3ea0 + drm fails to accept edid version 2.4 -- 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/1821533 Title: drm fa

[Ubuntu-x-swat] [Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

2019-03-25 Thread Rich Drewes
I was able to get the onboard LCD panel working, finally, as follows: First I extracted the edid file from the LCD panel using get-edid and putting that in /lib/firmware/edid/ncp.bin, and then forcing the kernel to take that using the kernel boot option drm.edid_firmware=edid/ncp.bin. This failed,

[Ubuntu-x-swat] [Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

2019-03-25 Thread Rich Drewes
Below is the EDID information from the onboard panel. Why can't drm/i915 deal with it? guest@guest-ZenBook-UX431FA:~$ sudo get-edid | parse-edid This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface No EDID on bus 0 No EDID on bus 1 No EDID on bus 2 No EDID o

[Ubuntu-x-swat] [Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

2019-03-25 Thread Rich Drewes
I think the problem is that the laptop's onboard LCD panel is reporting EDID data with version 2 and the i915 driver can only deal with version 1 at the moment. How can this be fixed? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in

[Ubuntu-x-swat] [Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

2019-03-25 Thread Rich Drewes
Correction: last message should read "Why is the driver/module expecting EDID major version *1* and getting *2*? -- 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/1821533 Title: failure to d

[Ubuntu-x-swat] [Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

2019-03-25 Thread Rich Drewes
Progress! Based on information in dmesg, pasted in at the end of this message, I thought maybe the graphics device was found OK but the laptop was trying to drive an external monitor instead of the onboard display. Sure enough, when I boot without nomodeset option and with an external HDMI monitor

[Ubuntu-x-swat] [Bug 1820899] Re: Neonode AirBar 13.3 inresponsive

2019-03-25 Thread Bug Watch Updater
** Changed in: libinput Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1820899 Title: Neonode AirBar 13.3 inresponsive To manage notifications

[Ubuntu-x-swat] [Bug 1821609] Re: Xorg freeze - fails to start or stay going screen blanks-grub seems involved

2019-03-25 Thread Derk Willem te Bokkel
this bug was filed from sda6 partition.. with this command and the following errors generated ubuntu-bug cat: /var/log/lightdm/x-0-greeter.log: No such file or directory cat: /var/log/lightdm/x-0-greeter.log.old: No such file or directory (/usr/lib/firefox/firefox:5674): dconf-WARNING **: 11:31:0

[Ubuntu-x-swat] [Bug 1821609] [NEW] Xorg freeze - fails to start or stay going screen blanks-grub seems involved

2019-03-25 Thread Derk Willem te Bokkel
Public bug reported: Okay the has happened recently at least since march 18, 2019 iso and march 22, 2019 iso are both effected very similar to one of my previously reported bugs .. which was related to xorg not being installed .. back ground .. PC is lenovo sl 500 with evo860 SSD drive 3 partio

[Ubuntu-x-swat] [Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

2019-03-25 Thread Rich Drewes
Is it known whether any machines with Intel Graphics 620 with pci id 0x3ea0 have functioning graphics with any version of Ubuntu? This is relatively new hardware, but it seems unlikely that I am the only one in the world who has tried this combination, and if other people with different machines w

[Ubuntu-x-swat] [Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

2019-03-25 Thread Rich Drewes
I tried booting 4.18.0-16-generic (which i believe is the hwe kernel) with kernel option drm.debug=0xff. When the system came up of course it had no video but I could ssh in and grab the dmesg output, which is attached to this message. dmesg had many drm-related debugging messages and i915-related

[Ubuntu-x-swat] [Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

2019-03-25 Thread Rich Drewes
Just in case my addition of i915 to initramfs was causing a problem with drm-intel-next, I removed i915 from initramfs and repeated the test. The result was the same, no video after a certain point in the boot process with nomodeset using the drm-intel-next kernel as in #8. -- You received this b

[Ubuntu-x-swat] [Bug 1794033]

2019-03-25 Thread Oss-linuxpf
Created attachment 143768 Debug trace. I got debug traces. Please see attached file. PID needs to be checked is 2602. After that this process was exited with "i965: Failed to submit batchbuffer: Bad address". At that time I repeated to copy and delete of files by rsync. Note: This is occurred on

[Ubuntu-x-swat] [Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

2019-03-25 Thread Rich Drewes
I installed kernel and modules and headers from https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/current/ and rebooted without nomodeset option. Same behavior: after the "loading initramfs" message the screen blanks and never comes back. -- You received this bug notification because

[Ubuntu-x-swat] [Bug 1818862] Re: Totem player hangs when seeking video due to [gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.]

2019-03-25 Thread El jinete sin cabeza
See LP: #1821525 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-vaapi-driver in Ubuntu. https://bugs.launchpad.net/bugs/1818862 Title: Totem player hangs when seeking video due to [gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame

[Ubuntu-x-swat] [Bug 1818862] Re: Totem player hangs when seeking video due to [gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.]

2019-03-25 Thread El jinete sin cabeza
See LP:#1821525 ** Tags added: disco -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-vaapi-driver in Ubuntu. https://bugs.launchpad.net/bugs/1818862 Title: Totem player hangs when seeking video due to [gen9_mfd.c:649: gen9_hcpd_get_re

[Ubuntu-x-swat] [Bug 1821525] Re: totem assert failure: totem: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.

2019-03-25 Thread El jinete sin cabeza
See LP: #1818862 -- 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/1821525 Title: totem assert failure: totem: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' faile

[Ubuntu-x-swat] [Bug 1821525] Re: totem assert failure: totem: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.

2019-03-25 Thread El jinete sin cabeza
** No longer affects: totem ** No longer affects: mesa -- 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/1821525 Title: totem assert failure: totem: totem: gen9_mfd.c:649: gen9_hcpd_get_referenc

[Ubuntu-x-swat] [Bug 1821525] Re: totem assert failure: totem: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.

2019-03-25 Thread El jinete sin cabeza
** Changed in: mesa (Ubuntu) Status: New => Invalid ** Description changed: https://github.com/intel/intel-vaapi-driver/issues/451 - https://bugzilla.freedesktop.org/show_bug.cgi?id=110232 + https://bugzilla.freedesktop.org/show_bug.cgi?id=110232 (No Mesa) https://gitlab.gnome.org/GNOM

[Ubuntu-x-swat] [Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

2019-03-25 Thread Timo Aaltonen
note that having 800x600 with nomodeset is perfectly normal, and expected... -- 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/1821533 Title: failure to detect and use Intel 620 graphics pci

[Ubuntu-x-swat] [Bug 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0

2019-03-25 Thread Timo Aaltonen
That pci-id should be known by all components of the stack on 19.04, so it should work with X just fine. If it doesn't, it's likely a bug in the kernel module. You could try with a mainline build of the drm-intel-next branch: https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/ install

[Ubuntu-x-swat] [Bug 1631715] Re: Password required twice returning from suspend

2019-03-25 Thread Theo Linkspfeifer
** Also affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New -- 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/1631715 Title: Password requ

[Ubuntu-x-swat] [Bug 1742711] Re: MIR: vulkan-loader

2019-03-25 Thread Alex Murray
I reviewed vulkan-loader version 1.1.101.0-2_amd64 as checked into disco. This shouldn't be considered a full security audit but rather a quick check of maintainability. - No CVE history in our database - vulkan-loader provides support for loading the main vulkan library, handling layer and driv