[Ubuntu-x-swat] [Bug 1801572] Re: package libdrm-nouveau2 2.4.95-1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libdrm-nouveau2/changelog.Debian.gz', which is different from o
looks like your mirror doesn't provide i386 builds, so use another one if necessary ** Changed in: libdrm (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1801572 Title: package libdrm-nouveau2 2.4.95-1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libdrm-nouveau2/changelog.Debian.gz', which is different from other instances of package libdrm- nouveau2:i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1801572/+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 1801410] Re: Icons.keep.flashing
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** 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/1801410 Title: Icons.keep.flashing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1801410/+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 1801225] Re: cmake files are misplaced
LLVM is maintained by Debian, nothing is happening on the Ubuntu side. You should report this kind of bugs on the Debian side. Thanks -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to llvm-toolchain-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1801225 Title: cmake files are misplaced To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-6.0/+bug/1801225/+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 1801716] [NEW] Xorg freeze (black screen after ubuntu logo during boot)
Public bug reported: I experienced this bug ever since I have upgraded my laptop from 16.04. But it got resolved in my last update after I reported the bug. However, I forgot to go back to Launchpad to mark it as resolved and now the problem comes again after I just updated the system. So, as the title stated, I can't get in the system due to the infinite black screen I am facing. I am only able to report this bug under the recovery mode. Besides, there's something wrong with the lock screen too. I can't get back to the system if I just put the system into "sleep mode". Black screen again! What's worst, the brightness of my display can't be adjusted as well! I feel like being blind at night! Please help!!! Thank you! And I think there might be the compatibility problem between my laptop and the new desktop -- Gnome, which is the default in 18.04. What should do? I really love using Ubuntu, as I really learned a lot in these days I used it as my study os for CS. Any help is appreciated, thanks in advance! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 4.17.0-041700rc3-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 5 19:49:36 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Today GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 08) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5300 [1043:15fd] InstallationDate: Installed on 2018-04-04 (215 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: ASUSTeK COMPUTER INC. T300FA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-041700rc3-generic root=UUID=63fcbd04-ec8b-462c-ba66-4f45c229353c ro recovery nomodeset Renderer: Software SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T300FA.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T300FA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT300FA.214:bd09/01/2015:svnASUSTeKCOMPUTERINC.:pnT300FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT300FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: T dmi.product.name: T300FA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-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 xserver.bootTime: Tue Nov 6 03:47:33 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic freeze 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/1801716 Title: Xorg freeze (black screen after ubuntu logo during boot) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1801716/+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 1801716] Re: Xorg freeze (black screen after ubuntu logo during boot)
-> http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19.1 -- Cristian -- 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/1801716 Title: Xorg freeze (black screen after ubuntu logo during boot) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801716/+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 1801716] Re: Xorg freeze (black screen after ubuntu logo during boot)
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete ** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1801716 Title: Xorg freeze (black screen after ubuntu logo during boot) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801716/+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 1740894] Re: KEY_RFKILL is not passed to userspace
@Mario, does disable/enabling airplane mode works if done from gnome- control-center (the wifi panel has the control)? Not sure that qualify as a verification-failed though, the fix there is to make the key being recognized, and that seems to work. The fact that the backend fails to re-enable is probably another problem. Also could you attach your journalctl log after getting the "fail to re- enable" issue? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+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 1778011] Re: SRU: PRIME Power Saving mode draws too much power
@Alberto, As you suggest, I did some tests with lightdm on Ubuntu 18.10 and it's working. Low battery usage with Intel and second monitor working with Nvidia. Thanks for your answer. Renato -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+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 1801747] Re: External display not recognized, internal one goes to black
Behavior is different, Ican't see the image on one or the other display, system now recognize the second screen but as soon as I switch the screens keyboard freezes, mouse icon react but no button working, have to switch off the computer with the on/off button :( Daniel -- 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/1801747 Title: External display not recognized, internal one goes to black To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801747/+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 1801747] [NEW] External display not recognized, internal one goes to black
Public bug reported: Hi, I have 10 notebooks HP 1410s on which I replace XP/Vista with Ubuntu 18.04.1 I face a problem on ALL of them, as soon as I connect an external screen, doesn't matter VGA or HDMI, the internal screen goes black, only mouse icon is their, blinking from time to time but reacting. External screen does show nothing but there is no "no signal" info what means that source is recognized. As soon as I release the video cable from external display, the internal one come back to live after few seconds. The BIOS was updated to latest available. Daniel tootai@hirondelle:~$ lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompositorRunning: None Date: Mon Nov 5 16:30:38 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-29-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:3072] Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:3072] InstallationDate: Installed on 2018-10-19 (17 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP ProBook 4510s ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=6ddf18e3-f14e-4d1c-b2fd-ae58c6f697ed ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PZI Ver. F.18 dmi.board.name: 3072 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 24.0F dmi.chassis.asset.tag: CNU0012B8R dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PZIVer.F.18:bd12/02/2010:svnHewlett-Packard:pnHPProBook4510s:pvrF.18:rvnHewlett-Packard:rn3072:rvrKBCVersion24.0F:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP ProBook 4510s dmi.product.version: F.18 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-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/1801747 Title: External display not recognized, internal one goes to black To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1801747/+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 1801747] Re: External display not recognized, internal one goes to black
** Tags added: kernel-bug-exists-upstream -- 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/1801747 Title: External display not recognized, internal one goes to black To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801747/+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 1801747] Re: External display not recognized, internal one goes to black
Err: to read is "I can see the image on one or the other display" ** Changed in: xorg-server (Ubuntu) Status: New => 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/1801747 Title: External display not recognized, internal one goes to black To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801747/+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 1801747] Re: External display not recognized, internal one goes to black
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19.1 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete ** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1801747 Title: External display not recognized, internal one goes to black To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801747/+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 1801747] Re: External display not recognized, internal one goes to black
Hi Cristian. No update/upgrade, straight HDD format + new install of Ubuntu. I will test the latest kernel. Thanks for your support Daniel -- 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/1801747 Title: External display not recognized, internal one goes to black To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801747/+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 1752053] Re: nvidia-390 fails to boot graphical display
The uncommenting #WaylandEnable=false worked a treat for me as with the previous posters. This is the answer to this problem and needs pinning to the thread! -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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
Re: [Ubuntu-x-swat] [Bug 1800555] Re: Computer slow. Error reports appear.
My system is running much better. Thank you. From: Marc Deslauriers To: larma...@yahoo.com Sent: Thursday, November 1, 2018 12:46 PM Subject: [Bug 1800555] Re: Computer slow. Error reports appear. Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1800555 Title: Computer slow. Error reports appear. Status in xorg package in Ubuntu: New Bug description: Computer slow. Error reports appear. Says system is running on low graphics sometimes. Makes me log in most of the time. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155 Uname: Linux 4.4.0-138-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: [[0;32m OK [0m] Stopped WPA supplicant. [[0;32m OK [0m] Started Show Plymouth Boot Screen. Starting Hold until boot process finishes up... CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Oct 29 17:37:27 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4200] [1002:9710] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company RS880 [Radeon HD 4200] [103c:2ab1] InstallationDate: Installed on 2016-09-11 (778 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard p6710f ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-138-generic root=UUID=03dbc475-0f36-4145-a3a0-9293828af31a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/04/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6.07 dmi.board.name: 2AB1 dmi.board.vendor: FOXCONN dmi.board.version: 1.00 dmi.chassis.asset.tag: 4CE0480TV4 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6.07:bd05/04/2011:svnHewlett-Packard:pnp6710f:pvr:rvnFOXCONN:rn2AB1:rvr1.00:cvnHewlett-Packard:ct3:cvr: dmi.product.name: p6710f dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Oct 29 17:32:25 2018 xserver.configfile: default xserver.devices: input Power Button KEYBOARD, id 6 input Power Button KEYBOARD, id 7 input CHICONY HP USB Multimedia Keyboard KEYBOARD, id 8 input CHICONY HP USB Multimedia Keyboard KEYBOARD, id 9 input Logitech USB Optical Mouse MOUSE, id 10 xserver.errors: /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1800555/+subscriptions -- 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/1800555 Title: Computer slow. Error reports appear. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1800555/+subscriptions ___ Mailing list:
Re: [Ubuntu-x-swat] [Bug 1800555] Re: Computer slow. Error reports appear.
My system is running much better. Thank you. From: Daniel van Vugt To: larma...@yahoo.com Sent: Thursday, November 1, 2018 9:41 PM Subject: [Bug 1800555] Re: Computer slow. Error reports appear. ** Tags added: radeon -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1800555 Title: Computer slow. Error reports appear. Status in xorg-server package in Ubuntu: New Bug description: Computer slow. Error reports appear. Says system is running on low graphics sometimes. Makes me log in most of the time. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155 Uname: Linux 4.4.0-138-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: [[0;32m OK [0m] Stopped WPA supplicant. [[0;32m OK [0m] Started Show Plymouth Boot Screen. Starting Hold until boot process finishes up... CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Oct 29 17:37:27 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4200] [1002:9710] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company RS880 [Radeon HD 4200] [103c:2ab1] InstallationDate: Installed on 2016-09-11 (778 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard p6710f ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-138-generic root=UUID=03dbc475-0f36-4145-a3a0-9293828af31a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/04/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6.07 dmi.board.name: 2AB1 dmi.board.vendor: FOXCONN dmi.board.version: 1.00 dmi.chassis.asset.tag: 4CE0480TV4 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6.07:bd05/04/2011:svnHewlett-Packard:pnp6710f:pvr:rvnFOXCONN:rn2AB1:rvr1.00:cvnHewlett-Packard:ct3:cvr: dmi.product.name: p6710f dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Oct 29 17:32:25 2018 xserver.configfile: default xserver.devices: input Power Button KEYBOARD, id 6 input Power Button KEYBOARD, id 7 input CHICONY HP USB Multimedia Keyboard KEYBOARD, id 8 input CHICONY HP USB Multimedia Keyboard KEYBOARD, id 9 input Logitech USB Optical Mouse MOUSE, id 10 xserver.errors: /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1800555/+subscriptions -- 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/1800555 Title: Computer slow. Error reports appear. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1800555/+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 1801747] Re: External display not recognized, internal one goes to black
This may be a regression, please try older kernels like v4.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/1801747 Title: External display not recognized, internal one goes to black To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1801747/+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 1801747] Re: External display not recognized, internal one goes to black
The machine seems to have an Intel CPU/GPU from 2009, which makes me think this might be related somehow to bug 1727356. Can you please try booting Ubuntu 18.10 as a test? http://releases.ubuntu.com/18.10/ -- 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/1801747 Title: External display not recognized, internal one goes to black To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1801747/+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 1740894] Re: KEY_RFKILL is not passed to userspace
@Sebastien: Yes, enable/disable airplane mode works from gnome-control-center. It also works to disalbe it from the Gnome panel manu. (Remember that it previously also could be enabled and disabled with the dedicated Fn+Pos1 key as long as xkb-data was 2.23). As for the verification-failed: I obviously accept the maintainers' decision. If you think that the xkb-data update is the right path forward despite this regression, by all means please go ahead. It would be good to fix the regression though. It seems that a very similar machine is sold as a Developer Edition with Ubuntu (Dell Precision 5530, https://bartongeorge.io/2018/05/24/welcome-the-new-dell-precision- developer-editions/) The failed disable of the airplane mode (i.e., failed re-enable of Wifi/BT) leaves this in journalctl: Nov 06 00:00:49 chronic systemd[1]: Starting Load/Save RF Kill Switch Status... Nov 06 00:00:49 chronic NetworkManager[777]: [1541458849.3593] manager: rfkill: WiFi now enabled by radio killswitch Nov 06 00:00:49 chronic systemd[1]: Started Load/Save RF Kill Switch Status. Nov 06 00:00:50 chronic kernel: ath10k_pci :02:00.0: Unknown eventid: 118809 Nov 06 00:00:50 chronic kernel: ath10k_pci :02:00.0: Unknown eventid: 90118 Nov 06 00:00:50 chronic kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready Nov 06 00:00:50 chronic NetworkManager[777]: [1541458850.2459] device (wlp2s0): device not up after timeout! Nov 06 00:00:50 chronic NetworkManager[777]: [1541458850.2462] manager: rfkill: WiFi now disabled by radio killswitch Nov 06 00:00:50 chronic NetworkManager[777]: [1541458850.2514] manager: rfkill: WWAN hardware radio set enabled Nov 06 00:00:50 chronic NetworkManager[777]: [1541458850.2516] audit: op="radio-control" arg="wwan-enabled" pid=2286 uid=1000 result="success" Nov 06 00:00:50 chronic NetworkManager[777]: [1541458850.2584] manager: rfkill: WWAN hardware radio set disabled Nov 06 00:00:50 chronic NetworkManager[777]: [1541458850.2586] audit: op="radio-control" arg="wwan-enabled" pid=2286 uid=1000 result="success" -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+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 1801747] Re: External display not recognized, internal one goes to black
Also, do you think this might be bug 1723025? ** Also affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Changed in: gdm3 (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: xorg-server (Ubuntu) Status: Confirmed => Incomplete -- 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/1801747 Title: External display not recognized, internal one goes to black To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1801747/+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 1801747] Re: External display not recognized, internal one goes to black
** Tags added: multimonitor -- 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/1801747 Title: External display not recognized, internal one goes to black To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801747/+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 1801716] Re: Xorg freeze (black screen after ubuntu logo during boot)
The machine is stuck in recovery mode, according to the kernel command line: [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.17.0-041700rc3-generic root=UUID=63fcbd04 -ec8b-462c-ba66-4f45c229353c ro recovery nomodeset To fix this, you need to reboot and then press Esc as soon as the purple screen appears. Now select the proper kernel that is not recovery mode. ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- 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/1801716 Title: Xorg freeze (black screen after ubuntu logo during boot) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801716/+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 1754693] Re: Xwayland crashed with SIGABRT in st_renderbuffer_delete() [often when running Skype or Slack snaps]
I have the same issue on 18.04, Wayland: ``` $ snap list skype Name VersionRev Tracking Publisher Notes skype 8.33.0.41 63 stableskype✓ classic ``` -- 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/1754693 Title: Xwayland crashed with SIGABRT in st_renderbuffer_delete() [often when running Skype or Slack snaps] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1754693/+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 1801716] Re: Xorg freeze (black screen after ubuntu logo during boot)
Thanks for all you guys reply!! And since there are two different suggestion, so I will reply respectively. To Cristian, Yes, the issue I am facing happens after I upgraded from Ubuntu 16.04 to 18.04. But no, or correctly, I don't know. As I followed what you suggested and do the test with the installation of latest kernel, V4.19, I can't even get to the phase where I can see the Ubuntu logo! Only a screen filled with error messages, which I took the photo and attach it as follow. So, let me rephrase what happened again. I headed to the kernel mainline page under V4.19. And download these three, as I followed the steps in the https://wiki.ubuntu.com/Kernel/MainlineBuilds: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19.1/linux-headers-4.19.1-041901_4.19.1-041901.201811041431_all.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19.1/linux-headers-4.19.1-041901-generic_4.19.1-041901.201811041431_i386.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19.1/linux-image-4.19.1-041901-generic_4.19.1-041901.201811041431_i386.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19.1/linux-modules-4.19.1-041901-generic_4.19.1-041901.201811041431_i386.deb and after 'wget' done in the terminal (the files have been downloaded in the folder I chose) I use the command: "sudo dpkg -i *.deb" Then reboot. Then what's on the screen was what you see in the attachment. I think it might be my laptop does not support this kernel? Since my laptop is so weird, meaning the screen of my laptop is touch-screen and detachable. So, sorry for your inconvenience of making the Ubuntu be compatible with my rare device, sorry. As for Daniel, So thank you for your advice, however, the issue I am facing is not when I tried to get in recovery mode or I was stuck at the recovery mode. No. I am only in the recovery mode is because this is the only way I can report this bug because I can not get in when it's in the regular mode and for some reason, I am able to access the Ubuntu when I am in the recovery mode. And this is how I get in: When I stuck at the black screen which show up after the Ubuntu logo. I did turn off the laptop forcefully buy long press the "turn on laptop" button, then turn on again. But this time I switch from "Ubuntu" to "Advance something something option" and get to the menu where I can chose to boot under the recovery mode. When I selected recovery mode, press enter, after all those scripts loading finish, and press "enter" or enter "Y" for one or two times, I reach to another menu where I can see, "Resume something" (or some words else but it's the first option in the menu), then I chose it, press enter, here I am! So... was I clear in my above description? And thank you all so much for the help and suggestion! All your active reply is why I love Ubuntu so much, even my device is such a pain, which I am sorry! ** Attachment added: "The error in the boot screen when I tried to boot in kernel V4.19" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1801716/+attachment/5209502/+files/error-message-on-the-screen-when-boot-v419.jpg -- 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/1801716 Title: Xorg freeze (black screen after ubuntu logo during boot) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801716/+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 1801870] Re: /usr/lib/xorg/Xorg:6:st_renderbuffer_delete:_mesa_reference_renderbuffer_:_mesa_reference_renderbuffer:_mesa_free_framebuffer_data:_mesa_destroy_framebuffer
*** This bug is a duplicate of bug 1754693 *** https://bugs.launchpad.net/bugs/1754693 ** This bug has been marked a duplicate of bug 1754693 Xwayland/Xorg crashed with SIGABRT in st_renderbuffer_delete() [often when running Skype or Slack snaps] -- 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/1801870 Title: /usr/lib/xorg/Xorg:6:st_renderbuffer_delete:_mesa_reference_renderbuffer_:_mesa_reference_renderbuffer:_mesa_free_framebuffer_data:_mesa_destroy_framebuffer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1801870/+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 1801870] [NEW] /usr/lib/xorg/Xorg:6:st_renderbuffer_delete:_mesa_reference_renderbuffer_:_mesa_reference_renderbuffer:_mesa_free_framebuffer_data:_mesa_destroy_framebuffer
*** This bug is a duplicate of bug 1754693 *** https://bugs.launchpad.net/bugs/1754693 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:1.20.1-3ubuntu2, the problem page at https://errors.ubuntu.com/problem/a1e7fe67e388164abd73462b322cb79ac2773fae contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic cosmic kylin-17.10 xenial yakkety zesty -- 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/1801870 Title: /usr/lib/xorg/Xorg:6:st_renderbuffer_delete:_mesa_reference_renderbuffer_:_mesa_reference_renderbuffer:_mesa_free_framebuffer_data:_mesa_destroy_framebuffer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1801870/+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 1754693] Re: Xwayland crashed with SIGABRT in st_renderbuffer_delete() [often when running Skype or Slack snaps]
Now tracking in both: https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca https://errors.ubuntu.com/problem/a1e7fe67e388164abd73462b322cb79ac2773fae ** Description changed: https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca + https://errors.ubuntu.com/problem/a1e7fe67e388164abd73462b322cb79ac2773fae --- Steps to reproduce: Install 'slack' snap: sudo snap install slack --classic Run slack: slack Instacrash. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.6-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell] CompositorRunning: None CurrentDesktop: GNOME Date: Fri Mar 9 10:31:06 2018 DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExecutablePath: /usr/bin/Xwayland ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] MachineType: ASUS All Series ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=1 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so Title: Xwayland crashed with SIGABRT UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago) UserGroups: adm admin audio cdrom chroot-admin dialout dip egbuild fax floppy fuse libvirt libvirtd lpadmin lxd plugdev sambashare sudo tape video wireshark dmi.bios.date: 10/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2702 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 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 1:2.10.5-1ubuntu1 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 xserver.bootTime: Mon Oct 16 18:18:18 2017 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.3-1ubuntu1.2 ** Summary changed: - Xwayland crashed with SIGABRT in st_renderbuffer_delete() [often when running Skype or Slack snaps] + Xwayland/Xorg crashed with SIGABRT in st_renderbuffer_delete() [often when running Skype or Slack snaps] ** Summary changed: -
