[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()
** 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.freedesktop.org/xorg/xserver/issues #645 -- 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_callback_destroy() from xwl_present_sync_callback() from ffi_call_unix64() To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1821385/+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 1821385] Re: Xwayland crashed with SIGABRT in wl_proxy_destroy() from wl_callback_destroy() from xwl_present_sync_callback() from ffi_call_unix64()
** 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_callback_destroy() from xwl_present_sync_callback() from ffi_call_unix64() To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1821385/+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 1813160] Re: display problem
[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-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1813160 Title: display problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1813160/+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 1821609] Re: Xorg freeze - fails to start or stay going screen blanks-grub seems involved
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. Run this command to collect the log from the previous (failed) boot: journalctl -b-1 > prevboot.txt and send us the file 'prevboot.txt'. 5. Run this command: dpkg -l > allpackages.txt and send us the file 'allpackages.txt'. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1821609 Title: Xorg freeze - fails to start or stay going screen blanks-grub seems involved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1821609/+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 1821525] Re: totem assert failure: totem: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.
*** 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 at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1818862 Totem player hangs when seeking video due to [gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.] -- 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' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/1821525/+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 1821426] Re: Ubuntu 19.14 disco will not boot on Dell Precision5530
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/GPU in your BIOS (c) Add 'nomodeset' to your kernel cmdline in /etc/default/grub and then run: sudo update-initramfs and reboot. ** Package changed: xorg (Ubuntu) => gdm3 (Ubuntu) ** Changed in: gdm3 (Ubuntu) Status: New => Incomplete ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1821426/+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 1821426] Re: Ubuntu 19.14 disco will not boot on Dell Precision5530
** 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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1821426/+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 1821426] [NEW] Ubuntu 19.14 disco will not boot on Dell Precision5530
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. The video will go between black with back light and black without back light. I cannot switch to a TTY, I cannot get further, keyboard seems to respond (lights up when keys are pressed). Additionally, when trying to upgrade from 18.10 the same result happens. After running the upgrade and rebooting, I cannot get it to boot unless I first start in recovery mode from grub. After that I can get to the desktop (nouveau driver seems to be installed by default). Any attempt to boot normally results in a black screen. Attempting to switch to proprietary nvidia driver results in never getting the luks screen (encrypted disk). I get no luks screen when booting normally either. lspci 00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers (rev 07) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 07) 00:02.0 VGA compatible controller: Intel Corporation Device 3e9b 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 07) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10) 00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10) 00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10) 00:15.0 Serial bus controller [0c80]: Intel Corporation Device a368 (rev 10) 00:15.1 Serial bus controller [0c80]: Intel Corporation Device a369 (rev 10) 00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10) 00:17.0 SATA controller: Intel Corporation Device a353 (rev 10) 00:1b.0 PCI bridge: Intel Corporation Device a340 (rev f0) 00:1c.0 PCI bridge: Intel Corporation Device a338 (rev f0) 00:1c.4 PCI bridge: Intel Corporation Device a33c (rev f0) 00:1d.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port 9 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device a30e (rev 10) 00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10) 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI Controller (rev 10) 01:00.0 3D controller: NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] (rev a1) 3b:00.0 Network controller: Intel Corporation Wireless-AC 9260 (rev 29) 3c:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 3d:00.0 Non-Volatile memory controller: Toshiba America Info Systems Device 011a ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Ubuntu 19.14 disco will not boot on Dell Precision5530 https://bugs.launchpad.net/bugs/1821426 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg 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 1815693] Re: Kubuntu 18.10 Xorg severe memory leak
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.net/bugs/1815693 Title: Kubuntu 18.10 Xorg severe memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1815693/+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 1815693] Re: Kubuntu 18.10 Xorg severe memory leak
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 ppa is enabled and installed on the computer. -- 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/1815693 Title: Kubuntu 18.10 Xorg severe memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1815693/+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 1821533] Re: drm fails to accept edid version 2.4
** 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 fails to accept edid version 2.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1821533/+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 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0
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, and dmesg said that the ncp.bin file had a "bad block 0". Possibly that means that nothing within Linux can accept edid version 2.4? Then I grabbed a generic 1920x1080.bin edid file from edid-generator github and put that one in /lib/firmware/edid/ and used that one with drm.edid_firmware and the display worked for the first time! I am still unsure why Linux couldn't accept the version 2.4 edid data from the LCD panel. -- 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 id 3ea0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1821533/+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 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0
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 on bus 3 No EDID on bus 4 1 potential busses found: 5 128-byte EDID successfully retrieved from i2c bus 5 Looks like i2c was successful. Have a good day. Checksum Correct Section "Monitor" Identifier "" ModelName "" VendorName "NCP" # Monitor Manufactured week 1 of 2018 # EDID version 2.4 # Digital Display DisplaySize 310 170 Gamma 2.20 Option "DPMS" "false" Modeline"Mode 0" 138.50 1920 1968 2000 2080 1080 1083 1088 +hsync -vsync EndSection -- 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 id 3ea0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1821533/+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 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0
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. https://bugs.launchpad.net/bugs/1821533 Title: failure to detect and use Intel 620 graphics pci id 3ea0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1821533/+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 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0
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 detect and use Intel 620 graphics pci id 3ea0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1821533/+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 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0
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 attached the system does display to the external monitor with proper 1920x1080 resolution. What does the "EDID is invalid:" message mean? Why is the driver/module expecting EDID major version 2 and getting 1? Does this have to do with the version of kbl_dmc firmware loaded to the graphics device? guest@guest-ZenBook-UX431FA:~$ dmesg | egrep "drm|i915" [3.196687] fb: switching to inteldrmfb from EFI VGA [3.196881] [drm] Replacing VGA console driver [3.210304] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [3.210306] [drm] Driver supports precise vblank timestamp query. [3.212814] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [3.214857] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) [3.228865] [drm] EDID has major version 2, instead of 1 [3.236620] [drm] EDID has major version 2, instead of 1 [3.240878] [drm] EDID has major version 2, instead of 1 [3.244590] [drm] EDID has major version 2, instead of 1 [3.244595] i915 :00:02.0: eDP-1: EDID is invalid: [3.244597] [drm] EDID has major version 2, instead of 1 [3.290049] [drm] Initialized i915 1.6.0 20180514 for :00:02.0 on minor 0 [3.326674] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [3.356268] fbcon: inteldrmfb (fb0) is primary device [4.724973] i915 :00:02.0: fb0: inteldrmfb frame buffer device -- 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 id 3ea0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1821533/+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 1820899] Re: Neonode AirBar 13.3 inresponsive
** 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 about this bug go to: https://bugs.launchpad.net/libinput/+bug/1820899/+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 1821609] Re: Xorg freeze - fails to start or stay going screen blanks-grub seems involved
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:02.271: Unable to open /var/lib/snapd/desktop/dconf/profile/user: Permission denied -- 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/1821609 Title: Xorg freeze - fails to start or stay going screen blanks-grub seems involved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1821609/+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 1821609] [NEW] Xorg freeze - fails to start or stay going screen blanks-grub seems involved
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 partions contain installs of disco sda1 -- main working system -- I usually install grub from here as master .. sda6 and sda7 are test installs of disco daily iso's 03-18-2019, 03-22-2019 repectively on the test installs as long as the iso is using the grub boot loader installed from that install the system will boot normally .. the display manger tends to flicker on and off but does final start and login can proceed. but if another install re-installs grub as master the display manager fails to stay active or even come-up for sda6 or sda7 only if their own grubs are reinstalled will they work normally sda1 display manager/xorg login works always no matter which "grub- source" is in control. if I use rescue boot from any grub as master I can get the displays to work by running dpkg fix which does nothing .. and then resuming the boot .. then things work normally.. if the "non-rescue" boots are used the screen/computer locks and only a power down and reboot gives access. (sometime requiring radical depowering .. unpluging and removing battery) now the is a message that appears that RCs??? level is missing. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu11 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Mar 25 11:25:58 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2019-03-23 (1 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322) MachineType: LENOVO 2746CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6AET64WW dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 2746CTO dmi.board.vendor: LENOVO dmi.board.version: LENOVO 6AET64WW dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LENOVO 6AET64WW dmi.modalias: dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW: dmi.product.name: 2746CTO dmi.product.version: ThinkPad SL500 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco freeze has-workaround regression reproducible 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/1821609 Title: Xorg freeze - fails to start or stay going screen blanks-grub seems involved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1821609/+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 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0
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 with the same 0x3ea0 pci id do have working graphics then that would suggest that the problem is some quirk of my particular ASUS UX431FA (perhaps some initialization timing quirk or hardware/design bug that is worked-around for the Windows 10 installation that came with the system). -- 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 id 3ea0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1821533/+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 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0
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 messages, but none of it was particularly helpful to me yet. ** Attachment added: "dmesg-drm.debug.txt" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1821533/+attachment/5249204/+files/dmesg-drm.debug.txt -- 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 id 3ea0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1821533/+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 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0
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 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 id 3ea0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1821533/+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 1794033]
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 core i3-6100E. Software version are same as the above. -- 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/1794033 Title: i965: Failed to submit batchbuffer: Bad address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1794033/+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 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0
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 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 id 3ea0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1821533/+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 1818862] Re: Totem player hangs when seeking video due to [gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.]
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_id: Assertion `0' failed.] To manage notifications about this bug go to: https://bugs.launchpad.net/libva/+bug/1818862/+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 1818862] Re: Totem player hangs when seeking video due to [gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.]
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_reference_picture_frame_id: Assertion `0' failed.] To manage notifications about this bug go to: https://bugs.launchpad.net/libva/+bug/1818862/+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 1821525] Re: totem assert failure: totem: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.
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' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/1821525/+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 1821525] Re: totem assert failure: totem: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.
** 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_reference_picture_frame_id: Assertion `0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/1821525/+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 1821525] Re: totem assert failure: totem: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.
** 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/GNOME/totem/issues/315 (No totem) --- Watching movie 4k, forward and back. - ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: totem 3.32.0-1ubuntu1 Uname: Linux 5.0.4-050004-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AssertionMessage: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple. CurrentDesktop: ubuntu:GNOME Date: Sun Mar 24 11:18:37 2019 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (111 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=es_CL:es PATH=(custom, no user) LANG=es_CL.UTF-8 Signal: 6 SourcePackage: totem StacktraceTop: __assert_fail_base (fmt=0x7f06f2ac2d6a , assertion=0x7f06b2cbcba4 "0", file=0x7f06b29b1cd0 "gen9_mfd.c", line=649, function=) at assert.c:92 __GI___assert_fail (assertion=0x7f06b2cbcba4 "0", file=0x7f06b29b1cd0 "gen9_mfd.c", line=649, function=0x7f06b29b23e0 "gen9_hcpd_get_reference_picture_frame_id") at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so vaEndPicture () from /usr/lib/x86_64-linux-gnu/libva.so.2 Title: totem assert failure: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple. UpgradeStatus: Upgraded to disco on 2018-12-02 (111 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: -- 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' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1821525/+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 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0
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 id 3ea0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1821533/+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 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0
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 linux-image-unsigned and linux-modules for amd64, then boot without nomodeset -- 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 id 3ea0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1821533/+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 1631715] Re: Password required twice returning from suspend
** 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 required twice returning from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1631715/+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 1742711] Re: MIR: vulkan-loader
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 driver management including multi-gpu support to dispatch API calls to the correct driver and layer. - Depends: debhelper, cmake, googletest, libwayland-dev, libx11-dev, libxcb1-dev, libxrandr-dev, pkg-config, python3 - Does not itself do networking - No cryptography - Does not daemonize - No pre/post inst/rm - No init scripts - No dbus services - No setuid files - No binaries in the PATH - No sudo fragments - No udev rules - A test suite is run during the build (as noted in the log, 23 of the tests fail due to missing vulkan driver but as this is expected this is not a concern) - No cron jobs - 3 warnings in build logs about memory allocation functions which declare as returning void * but are used for functions which expect an unsigned long * return value - these can safely be ignored - No cppcheck warnings - No subprocesses spawned - Memory management is very careful in general, however I noticed that the loader allocates a buffer on stack for reading in ICD JSON descriptions - this uses the length of the JSON file as the length of the buffer to allocate and since these files can be user controlled it could be relatively easily exploited by dropping a very large JSON file to overrun the stack (since uses alloca() internally which has undefined behaviour if stack is overflown) - this might be worth investigating further but is really only a denial of service issue so not a high priority and no chance of privilege escalation etc - Otherwise most memory management is quite careful, allocation return values are checked for failure, buffer lengths are checked, string lengths are checked and handled correctly etc. - Does not itself do file IO beyond reading JSON as described above - Logging is careful - Uses the following environment variables: - VK_LOADER_DISABLE_INST_EXT_FILTER - VK_LOADER_DEBUG - XDG_CONFIG_DIRS - XDG_DATA_DIRS - XDG_DATA_HOME - HOME - No privileged code sections - No privileged functions - No networking - No temp files - No WebKit - No PolKit Security team ACK for promoting vulkan-loader to main for disco. ** Changed in: vulkan-loader (Ubuntu) Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to vulkan-loader in Ubuntu. https://bugs.launchpad.net/bugs/1742711 Title: MIR: vulkan-loader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vulkan-loader/+bug/1742711/+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 1821533] Re: failure to detect and use Intel 620 graphics pci id 3ea0
Based on a lead from an Arch Linux blog post, I tried adding the i915 module to the initramfs. This could possibly lead to earlier initialization of the graphics device and it also seems consistent with the DragonFlyBSD "probe early" patch I linked to in my initial bug report which may have fixed the graphics problem in DragonFlyBSD (I cannot tell for certain if the graphics problem was fixed there due to another, unrelated problem, but the fix definitely allowed the boot to proceed further and the text did seem to switch to full screen resolution). The update-initramfs operation failed on the v5.1-rc2 kernel because of two missing firmware files. The update-initramfs operation succeeded on the 4.x kernels I had installed, one of which is the hwe kernel (I believe). I verified the presence of the i915 module in the initramfs for those kernels using lsinitramfs. Unfortunately, booting with i915 in the initramfs on the 4.x kernels and without nomodeset did not solve the problem. -- 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 id 3ea0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1821533/+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 1821508] Re: there is a lagging while i am accessing the software or browing
** Package changed: xorg (Ubuntu) => 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/1821508 Title: there is a lagging while i am accessing the software or browing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1821508/+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
