[Ubuntu-x-swat] [Bug 1742365] [NEW] built-in display problem
Public bug reported: display not minimize, its shows built-in display ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Jan 10 10:52:50 2018 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-30-generic, x86_64: installed virtualbox, 4.3.36, 3.16.0-30-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GF119 [GeForce GT 610] [10de:104a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. Device [19da:6222] InstallationDate: Installed on 2016-03-01 (679 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Dell Inc. Vostro 3900 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic root=UUID=1d25c27f-72f7-40dd-a53e-0b28eecc57c8 ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UdevLog: UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0T1D10 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/08/2015:svnDellInc.:pnVostro3900:pvr:rvnDellInc.:rn0T1D10:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.name: Vostro 3900 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Jan 10 10:15:15 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputPixArt USB Optical Mouse MOUSE, id 8 inputDell Dell USB Entry Keyboard KEYBOARD, id 9 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu ** Attachment added: "Screenshot from 2018-01-10 10:56:42.png" https://bugs.launchpad.net/bugs/1742365/+attachment/5034071/+files/Screenshot%20from%202018-01-10%2010%3A56%3A42.png -- 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/1742365 Title: built-in display problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1742365/+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 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04
*** This bug is a duplicate of bug 1735594 *** https://bugs.launchpad.net/bugs/1735594 ppa:paulo-miguel-dias/pkppa worked for me. No problems since. -- 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/1741447 Title: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1741447/+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 1733083] Re: trackpoint slow and hard to move
** Changed in: libinput (Ubuntu) Status: Incomplete => New ** Also affects: libinput via https://bugs.freedesktop.org/show_bug.cgi?id=98689 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1733083 Title: trackpoint slow and hard to move To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/1733083/+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 1696929] Re: Touchpads are unresponsive and laggy for small finger movements
Actually we don't need to ignore it. We can release the fixes for the regression. The fixes are: 1. libinput: https://lists.freedesktop.org/archives/wayland-devel/2018-January/036475.html (not landed yet) 2. kernel: https://bugs.freedesktop.org/show_bug.cgi?id=104533 (not tested yet) James will need both, but as I understand it only the libinput fix is required for all touchpads in general. So we only need to wait for #1. I plan on testing it across a few laptops this week to get ahead of the ball. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1696929 Title: Touchpads are unresponsive and laggy for small finger movements To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/1696929/+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 1741914] Re: artful-proposed 4.13.0-24: kernel module failed to build [Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfutils-
linux (4.13.0-25.29) artful; urgency=low * linux: 4.13.0-25.29 -proposed tracker (LP: #1741955) * CVE-2017-5754 - Revert "UBUNTU: [Config] updateconfigs to enable PTI" - [Config] Enable PTI with UNWINDER_FRAME_POINTER ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-5754 ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: bbswitch (Ubuntu) Status: Confirmed => Invalid ** Changed in: bcmwl (Ubuntu) Status: Confirmed => Invalid ** Changed in: ndiswrapper (Ubuntu) Status: Confirmed => Invalid ** Changed in: nvidia-graphics-drivers-304 (Ubuntu) Status: Confirmed => Invalid ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: Confirmed => Invalid ** Changed in: nvidia-graphics-drivers-384 (Ubuntu) Status: Confirmed => Invalid ** Changed in: virtualbox (Ubuntu) Status: Confirmed => Invalid ** Also affects: rtl8812au (Ubuntu) Importance: Undecided Status: New ** Changed in: rtl8812au (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1741914 Title: artful-proposed 4.13.0-24: kernel module failed to build [Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1741914/+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 1735594] Re: [regression] compiz crashes after Mesa upgrade
this is a more complete command to install stock hwe stack on 16.04 sudo apt install --install-recommends xserver-xorg xserver-xorg-core xserver-xorg-video-all xserver-xorg-input-all xserver-xorg-video-intel xserver-xorg-video-qxl -- 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/1735594 Title: [regression] compiz crashes after Mesa upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1741914] Re: artful-proposed 4.13.0-24: kernel module failed to build [Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfut
Right after reporting this and 3 other bugs all at the same time, I rebooted and it got cought in a loop right before the login and I had to reinstall. Thank you for working on these issues, your way ahead of me. James On Tue, Jan 9, 2018 at 7:27 AM, Videonauth <1741...@bugs.launchpad.net> wrote: > Yes, sadly now the NVidia Driver 384.90 (I still wonder where you get > the 384.111 on artful) fails still to build even after the released fix. > But this time with a different message and build log. And without > showing me an opportunity to report the bug (except using ubuntu-bug > command which will maybe not fetch all information). > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1742039). > https://bugs.launchpad.net/bugs/1741914 > > Title: > artful-proposed 4.13.0-24: kernel module failed to build [Cannot > generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install > libelf-dev, libelf-devel or elfutils-libelf-devel] > > Status in bbswitch package in Ubuntu: > Confirmed > Status in bcmwl package in Ubuntu: > Confirmed > Status in linux package in Ubuntu: > Fix Committed > Status in ndiswrapper package in Ubuntu: > Confirmed > Status in nvidia-graphics-drivers-304 package in Ubuntu: > Confirmed > Status in nvidia-graphics-drivers-340 package in Ubuntu: > Confirmed > Status in nvidia-graphics-drivers-384 package in Ubuntu: > Confirmed > Status in virtualbox package in Ubuntu: > Confirmed > > Bug description: > After update to new kernel (4.13.0-24) the system prompted me with > this. > > ProblemType: Package > DistroRelease: Ubuntu 17.10 > Package: nvidia-384 384.90-0ubuntu3.17.10.2 > ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13 > Uname: Linux 4.13.0-22-generic x86_64 > NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia > ApportVersion: 2.20.7-0ubuntu3.7 > Architecture: amd64 > DKMSKernelVersion: 4.13.0-24-generic > Date: Mon Jan 8 16:30:09 2018 > PackageVersion: 384.90-0ubuntu3.17.10.2 > Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, > 3.6.3-0ubuntu2 > PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, > 2.7.14-2ubuntu1 > RelatedPackageVersions: >dpkg 1.18.24ubuntu1 >apt 1.5.1 > SourcePackage: nvidia-graphics-drivers-384 > Title: nvidia-384 384.90-0ubuntu3.17.10.2: nvidia-384 kernel module > failed to build > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/ > 1741914/+subscriptions > -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1741914 Title: artful-proposed 4.13.0-24: kernel module failed to build [Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1741914/+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 1696929] Re: Touchpads are unresponsive and laggy for small finger movements
I don't understand how we can ignore a well known regression? If there's a kernel patch as a result then surely we'll want it in bionic? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1696929 Title: Touchpads are unresponsive and laggy for small finger movements To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/1696929/+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 1741914] Re: artful-proposed 4.13.0-24: kernel module failed to build [Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfut
Right after reporting this and 3 other bugs all at the same time, I rebooted and it got cought in a loop right before the login and I had to reinstall. Thank you for working on these issues, your way ahead of me. James On Tue, Jan 9, 2018 at 5:17 AM, Jacques Koch <1741...@bugs.launchpad.net> wrote: > Thanks will definitely go and take a look. Only been on Linux about a month > or so and really loving it ,but still finding my feet > > On 9 Jan 2018 12:50, "Daniel van Vugt" > wrote: > > > It looks like this bug is now fixed as of 1 hour ago, in linux > > 4.13.0-25.29. You had to be unlucky to have an artful system on proposed > > do an update during the previous day and get the faulty package linux > > 4.13.0-24. That one doesn't exist any more so this bug should quieten > > down now. > > > > See bug 1741955 for updates. > > > > ** Changed in: linux (Ubuntu) > >Status: Confirmed => Fix Committed > > > > -- > > You received this bug notification because you are subscribed to a > > duplicate bug report (1742014). > > https://bugs.launchpad.net/bugs/1741914 > > > > Title: > > artful-proposed 4.13.0-24: kernel module failed to build [Cannot > > generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install > > libelf-dev, libelf-devel or elfutils-libelf-devel] > > > > Status in bbswitch package in Ubuntu: > > Confirmed > > Status in bcmwl package in Ubuntu: > > Confirmed > > Status in linux package in Ubuntu: > > Fix Committed > > Status in ndiswrapper package in Ubuntu: > > Confirmed > > Status in nvidia-graphics-drivers-304 package in Ubuntu: > > Confirmed > > Status in nvidia-graphics-drivers-340 package in Ubuntu: > > Confirmed > > Status in nvidia-graphics-drivers-384 package in Ubuntu: > > Confirmed > > Status in virtualbox package in Ubuntu: > > Confirmed > > > > Bug description: > > After update to new kernel (4.13.0-24) the system prompted me with > > this. > > > > ProblemType: Package > > DistroRelease: Ubuntu 17.10 > > Package: nvidia-384 384.90-0ubuntu3.17.10.2 > > ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13 > > Uname: Linux 4.13.0-22-generic x86_64 > > NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia > > ApportVersion: 2.20.7-0ubuntu3.7 > > Architecture: amd64 > > DKMSKernelVersion: 4.13.0-24-generic > > Date: Mon Jan 8 16:30:09 2018 > > PackageVersion: 384.90-0ubuntu3.17.10.2 > > Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, > > 3.6.3-0ubuntu2 > > PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, > > 2.7.14-2ubuntu1 > > RelatedPackageVersions: > >dpkg 1.18.24ubuntu1 > >apt 1.5.1 > > SourcePackage: nvidia-graphics-drivers-384 > > Title: nvidia-384 384.90-0ubuntu3.17.10.2: nvidia-384 kernel module > > failed to build > > UpgradeStatus: No upgrade log present (probably fresh install) > > > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/ > > 1741914/+subscriptions > > > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1742039). > https://bugs.launchpad.net/bugs/1741914 > > Title: > artful-proposed 4.13.0-24: kernel module failed to build [Cannot > generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install > libelf-dev, libelf-devel or elfutils-libelf-devel] > > Status in bbswitch package in Ubuntu: > Confirmed > Status in bcmwl package in Ubuntu: > Confirmed > Status in linux package in Ubuntu: > Fix Committed > Status in ndiswrapper package in Ubuntu: > Confirmed > Status in nvidia-graphics-drivers-304 package in Ubuntu: > Confirmed > Status in nvidia-graphics-drivers-340 package in Ubuntu: > Confirmed > Status in nvidia-graphics-drivers-384 package in Ubuntu: > Confirmed > Status in virtualbox package in Ubuntu: > Confirmed > > Bug description: > After update to new kernel (4.13.0-24) the system prompted me with > this. > > ProblemType: Package > DistroRelease: Ubuntu 17.10 > Package: nvidia-384 384.90-0ubuntu3.17.10.2 > ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13 > Uname: Linux 4.13.0-22-generic x86_64 > NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia > ApportVersion: 2.20.7-0ubuntu3.7 > Architecture: amd64 > DKMSKernelVersion: 4.13.0-24-generic > Date: Mon Jan 8 16:30:09 2018 > PackageVersion: 384.90-0ubuntu3.17.10.2 > Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, > 3.6.3-0ubuntu2 > PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, > 2.7.14-2ubuntu1 > RelatedPackageVersions: >dpkg 1.18.24ubuntu1 >apt 1.5.1 > SourcePackage: nvidia-graphics-drivers-384 > Title: nvidia-384 384.90-0ubuntu3.17.10.2: nvidia-384 kernel module > failed to build > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/bbswitc
[Ubuntu-x-swat] [Bug 1741925] Re: Unity launcher disappears on mouse-over launcher
*** This bug is a duplicate of bug 1735594 *** https://bugs.launchpad.net/bugs/1735594 no need to debug anymore, the issue is well known by now and 1735594 has more information, you should have received my emails about it -- 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/1741925 Title: Unity launcher disappears on mouse-over launcher To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1741925/+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 1741925] Re: Unity launcher disappears on mouse-over launcher
*** This bug is a duplicate of bug 1735594 *** https://bugs.launchpad.net/bugs/1735594 not emails but replies/edits to that bug -- 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/1741925 Title: Unity launcher disappears on mouse-over launcher To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1741925/+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 1735594] Re: [regression] compiz crashes after Mesa upgrade
PPA builders are unfortunately still offline because of SPECTRE :( One quick workaround for this issue is to downgrade to stock 16.04 xserver and install x-x-v-intel: sudo apt install --install-recommends xserver-xorg xserver-xorg-video- all xserver-xorg-input-all xserver-xorg-video-intel that should do it.. it'll remove a bunch of packages named -hwe-16.04 and replace them with the stock packages. -- 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/1735594 Title: [regression] compiz crashes after Mesa upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04
*** This bug is a duplicate of bug 1735594 *** https://bugs.launchpad.net/bugs/1735594 @laurel, to find your version, try in a terminal lsb_release -a If you have further questions for support or how to deal with his matter, please read: https://askubuntu.com/questions/992571/gui-unity-crashing-in-16-04-lts-after-latest-updates-compiz-segfaults -- 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/1741447 Title: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1741447/+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 433926] Re: xkbcomp error: Type "ONE_LEVEL" has 1 levels, but has 2 symbols
On 2018-01-09 18:45, H.-Dirk Schmitt wrote: > Still in xenial > affected: xkb-data 2.16-1ubuntu1 > > │Jan 8 11:49:55 user.warning /usr/lib/gdm3/gdm-x-session[3463 > > Warning: Type "ONE_LEVEL" has 1 levels, but has 2 │ This seems to be an old one. If I understand it correctly, Sergey posted a suggestion in comment #17, but got no feedback. Can someone who is affected provide some feedback to that suggestion? Please note that this is not important enough to update 16.04 or any other stable release. However, if the change would be committed upstream, it might make it into Ubuntu 18.04. -- 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/433926 Title: xkbcomp error: Type "ONE_LEVEL" has 1 levels, but has 2 symbols To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/433926/+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 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04
*** This bug is a duplicate of bug 1735594 *** https://bugs.launchpad.net/bugs/1735594 ppa:paulo-miguel-dias/pkppa works for me too No more issues -- 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/1741447 Title: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1741447/+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 1741925] Re: Unity launcher disappears on mouse-over launcher
*** This bug is a duplicate of bug 1735594 ***
https://bugs.launchpad.net/bugs/1735594
Answers:
Do you have an additional monitor connected? NO What is the display resolution
you use? 12??X800 Do things still crash if you change the resolution to
something smaller than the native NO
Thank you for your direction. In attempt to narrow the failure down I examined
the two visible symptoms:
1. Mouse-over the launcher causes the launcher and the task line at the top to
disappear
2. There appears to be a recovery time of 10 to 30 seconds and then the
launcher and all reappear
The most likely culprits appear to be:
1. Mouse software; I assume that is part of the Lunux kernel. I was unable to
find any information on the Ubuntu software stack or architecture so I could
not identify the process(es) used for the mouse.
To evaluate mouse malfunction I (a) tried both the laptop’s mouse-pad and a USB
mouse with no difference in behavior and (b) did a mouse-over of some Linux
apps where the button or widget reacts to a mouse-over; the mouse-over behavior
worked as expected.
My conclusion is that the mouse and the mouse code is behaving properly.
2. Launcher code; without a software stack the name of the process is
unknowable. Doing a query in the System Monitor gave a likely
“api-spi-bus-launcher” (see that attached image, “Launcher properties
2018-01-09 12-44-12.png”).
An strace on that pid
sudo strace -p 1488 -b execve -o launcher.txt
[sudo] password for bruce:
yielded
restart_syscall(<... resuming interrupted poll ...>) = 1
read(3, "\2\0\0\0\0\0\0\0", 16) = 8
poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}], 2, -1) = 1 ([{fd=3,
revents=POLLIN}])
read(3, "\2\0\0\0\0\0\0\0", 16) = 8
poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}], 2, -1) = 1 ([{fd=3,
revents=POLLIN}])
read(3, "\2\0\0\0\0\0\0\0", 16) = 8
poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}], 2, -1
I do not know how to read strace output. The “restart_syscall” line looks
suspiciously like an error recover execution.
The launcher disappearance behavior is captured in two images, before the
failure “Launcher failure a 2018-01-09 12-23-23.png” and during recovery
“Launcher failure b 2018-01-09 12-24-39.png”. They are
attached.?field.comment=Answers:
Do you have an additional monitor connected? NO What is the display resolution
you use? 12??X800 Do things still crash if you change the resolution to
something smaller than the native NO
Thank you for your direction. In attempt to narrow the failure down I examined
the two visible symptoms:
1. Mouse-over the launcher causes the launcher and the task line at the top to
disappear
2. There appears to be a recovery time of 10 to 30 seconds and then the
launcher and all reappear
The most likely culprits appear to be:
1. Mouse software; I assume that is part of the Lunux kernel. I was unable to
find any information on the Ubuntu software stack or architecture so I could
not identify the process(es) used for the mouse.
To evaluate mouse malfunction I (a) tried both the laptop’s mouse-pad and a USB
mouse with no difference in behavior and (b) did a mouse-over of some Linux
apps where the button or widget reacts to a mouse-over; the mouse-over behavior
worked as expected.
My conclusion is that the mouse and the mouse code is behaving properly.
2. Launcher code; without a software stack the name of the process is
unknowable. Doing a query in the System Monitor gave a likely
“api-spi-bus-launcher” (see that attached image, “Launcher properties
2018-01-09 12-44-12.png”).
An strace on that pid
sudo strace -p 1488 -b execve -o launcher.txt
[sudo] password for bruce:
yielded
restart_syscall(<... resuming interrupted poll ...>) = 1
read(3, "\2\0\0\0\0\0\0\0", 16) = 8
poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}], 2, -1) = 1 ([{fd=3,
revents=POLLIN}])
read(3, "\2\0\0\0\0\0\0\0", 16) = 8
poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}], 2, -1) = 1 ([{fd=3,
revents=POLLIN}])
read(3, "\2\0\0\0\0\0\0\0", 16) = 8
poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}], 2, -1
I do not know how to read strace output. The “restart_syscall” line looks
suspiciously like an error recover execution.
The launcher disappearance behavior is captured in two images, before the
failure “Launcher failure a 2018-01-09 12-23-23.png” and during recovery
“Launcher failure b 2018-01-09 12-24-39.png”. They are attached.
** Attachment added: "before launcher failur"
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1741925/+attachment/5033648/+files/Launcher%20failure%20a%202018-01-09%2012-23-23.png
--
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/1741925
Title:
Unity launcher disappears on mouse-over launcher
To manage notifications about this bug go to:
https://bugs.l
[Ubuntu-x-swat] [Bug 433926] Re: xkbcomp error: Type "ONE_LEVEL" has 1 levels, but has 2 symbols
Still in xenial affected: xkb-data 2.16-1ubuntu1 │Jan 8 11:49:55 user.warning /usr/lib/gdm3/gdm-x-session[3463 > Warning: Type "ONE_LEVEL" has 1 levels, but has 2 │ -- 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/433926 Title: xkbcomp error: Type "ONE_LEVEL" has 1 levels, but has 2 symbols To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/433926/+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 1713313] Re: Unable to launch pkexec'ed applications on Wayland session
synaptic confirmed on 18.04. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xdiagnose in Ubuntu. https://bugs.launchpad.net/bugs/1713313 Title: Unable to launch pkexec'ed applications on Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/backintime/+bug/1713313/+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 1713313] Re: Unable to launch pkexec'ed applications on Wayland session
Problem with `nemo` "Open as Root" is confirmed on 18.04. ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xdiagnose in Ubuntu. https://bugs.launchpad.net/bugs/1713313 Title: Unable to launch pkexec'ed applications on Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/backintime/+bug/1713313/+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 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04
*** This bug is a duplicate of bug 1735594 *** https://bugs.launchpad.net/bugs/1735594 I'm a newbie and after updating Ubuntu 16.04 on Jan 5, 2018, I experienced launcher disappearing when running over with mouse, windows disappearing and appearing, Dash not working and cannot shutdown. I get Internal Error Message: compiz crashed with SIGSERV. The error report incorrectly prints that I have amd64 architecture and that I have Ubuntu 16.04.2 LTS Release amd64 (20170215.2) when I have Ubuntu 16.04.3 This result seems not to have been commented on in the previous bug #1735594. I'm working on a Toshiba Satellite M645 laptop (2011) with an Intel Core i5 CPU, 64 bit OS and graphics is Intel Ironlake Mobile. I'm afraid to try the ppa:paulo-miguel-dias/pkppa suggestion because I am so new to this. I installed August 2017 and had no problems until Jan 5, 2018 when using the Software Updater. The good news is: I learned to use terminal commands and can access all the browsers, word processors, files, etc. that I have on my machine so I'm not down just inconvenienced. Thanks -- 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/1741447 Title: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1741447/+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 1733083] Re: trackpoint slow and hard to move
Hi Daniel, close but no cigar. I compiled libinput from master, and there are some improvements but the situation for this laptop is not solved. It appears that this model, and probably all of Elantech TrackPoints, require some custom acceleration routines as per https://bugs.freedesktop.org/show_bug.cgi?id=98689#c10 It should be mentioned that the fix that I proposed above with the new libinput relase is no necessary and will only make the trackpoint more jerky. Have a nice day, Carlo ** Bug watch added: freedesktop.org Bugzilla #98689 https://bugs.freedesktop.org/show_bug.cgi?id=98689 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1733083 Title: trackpoint slow and hard to move To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1733083/+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 1741914] Re: artful-proposed 4.13.0-24: kernel module failed to build [Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfutils-
Here a link to the new regression. not sure if this belongs here or not so i submitted it singlestanding: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-384/+bug/1742160 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1741914 Title: artful-proposed 4.13.0-24: kernel module failed to build [Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1741914/+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 1735594] Re: [regression] compiz crashes after Mesa upgrade
** Summary changed: - [regression] compiz crashes when hovering over sidebar + [regression] compiz crashes after Mesa upgrade -- 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/1735594 Title: [regression] compiz crashes after Mesa upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1741914] Re: artful-proposed 4.13.0-24: kernel module failed to build [Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfutils-
Yes, sadly now the NVidia Driver 384.90 (I still wonder where you get the 384.111 on artful) fails still to build even after the released fix. But this time with a different message and build log. And without showing me an opportunity to report the bug (except using ubuntu-bug command which will maybe not fetch all information). -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1741914 Title: artful-proposed 4.13.0-24: kernel module failed to build [Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1741914/+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 1735594] Re: [regression] compiz crashes when hovering over sidebar
** Description changed: - When I use the Unity session I automatically get logged out under these - conditions: + [Impact] + When I use the Unity session I automatically get logged out under these conditions: When I hover with my mouse over any icon of the sidebar. When I press the alt key. When I press the super key. running dmesg after this unwanted logout happens I get following information: compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0 error 4 in i965_dri.so[7fbca2af6000+7e4000] - The info about my installed compiz: + This is caused by a mesa upgrade, which added a patch for bug #1727401. The crasher is reproduced on: + - gen4 / gen5 Intel + - if using modesetting X driver, like when xserver-xorg-video-intel is not installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults to modesetting) - compiz: - Instal·lat: 1:0.9.13.1+17.10.20170901-0ubuntu1 - Candidat: 1:0.9.13.1+17.10.20170901-0ubuntu1 - Taula de versió: - *** 1:0.9.13.1+17.10.20170901-0ubuntu1 500 - 500 http://es.archive.ubuntu.com/ubuntu artful/universe amd64 Packages - 500 http://es.archive.ubuntu.com/ubuntu artful/universe i386 Packages - 100 /var/lib/dpkg/status + [Test case] + Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash. + + [Regression potential] + The backported patches need to be tested, here for regressions and on 1727401 that they fix the original bug (again). + + Best to test on a wide array of Intel HW: + gen4 (965GM/GM45/G45) + gen5 (Ironlake) + gen6 (Sandy Bridge) + gen7 (Bay Trail, Ivy Bridge, Haswell) + gen8 (Braswell, Broadwell) + gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake) -- 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/1735594 Title: [regression] compiz crashes when hovering over sidebar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1735594] Re: [regression] compiz crashes when hovering over sidebar
** Summary changed: - ubuntu automatically logs out when hovering sidebar + [regression] compiz crashes when hovering over sidebar -- 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/1735594 Title: [regression] compiz crashes when hovering over sidebar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04
*** This bug is a duplicate of bug 1735594 *** https://bugs.launchpad.net/bugs/1735594 ** This bug has been marked a duplicate of bug 1735594 ubuntu automatically logs out when hovering sidebar -- 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/1741447 Title: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1741447/+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 1741925] Re: Unity launcher disappears on mouse-over launcher
*** This bug is a duplicate of bug 1735594 *** https://bugs.launchpad.net/bugs/1735594 I was able to reproduce after all, marking as a dupe ** This bug has been marked a duplicate of bug 1735594 ubuntu automatically logs out when hovering sidebar -- 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/1741925 Title: Unity launcher disappears on mouse-over launcher To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1741925/+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 1741874] Re: if I move the arrow to the Unity, all the unity disappear , only the background still appear , and all the action freezed
*** This bug is a duplicate of bug 1735594 *** https://bugs.launchpad.net/bugs/1735594 no need, marking as a duplicate ** This bug has been marked a duplicate of bug 1735594 ubuntu automatically logs out when hovering sidebar -- 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/1741874 Title: if I move the arrow to the Unity, all the unity disappear ,only the background still appear ,and all the action freezed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1741874/+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 1735594] Re: ubuntu automatically logs out when hovering sidebar
The culprit is a patch added for bug 1727401, it needs to be replaced with a larger set of backports from 17.3... -- 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/1735594 Title: ubuntu automatically logs out when hovering sidebar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)
This patch broke the DRI driver on older gen4/4.5/5 Intel HW, see bugs 1735594 and 1741447 I've backported five commits from upstream to fix this properly, at least this backport doesn't crash on my HW anymore. ** Changed in: mesa (Ubuntu Xenial) Status: Fix Released => Triaged ** Changed in: mesa (Ubuntu) Status: Fix Released => In Progress -- 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/1727401 Title: Corruption on windowed 3D apps running on dGPU (Intel/AMD) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1727401/+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 1741914] Re: artful-proposed 4.13.0-24: kernel module failed to build [Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfut
Thanks will definitely go and take a look. Only been on Linux about a month or so and really loving it ,but still finding my feet On 9 Jan 2018 12:50, "Daniel van Vugt" wrote: > It looks like this bug is now fixed as of 1 hour ago, in linux > 4.13.0-25.29. You had to be unlucky to have an artful system on proposed > do an update during the previous day and get the faulty package linux > 4.13.0-24. That one doesn't exist any more so this bug should quieten > down now. > > See bug 1741955 for updates. > > ** Changed in: linux (Ubuntu) >Status: Confirmed => Fix Committed > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1742014). > https://bugs.launchpad.net/bugs/1741914 > > Title: > artful-proposed 4.13.0-24: kernel module failed to build [Cannot > generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install > libelf-dev, libelf-devel or elfutils-libelf-devel] > > Status in bbswitch package in Ubuntu: > Confirmed > Status in bcmwl package in Ubuntu: > Confirmed > Status in linux package in Ubuntu: > Fix Committed > Status in ndiswrapper package in Ubuntu: > Confirmed > Status in nvidia-graphics-drivers-304 package in Ubuntu: > Confirmed > Status in nvidia-graphics-drivers-340 package in Ubuntu: > Confirmed > Status in nvidia-graphics-drivers-384 package in Ubuntu: > Confirmed > Status in virtualbox package in Ubuntu: > Confirmed > > Bug description: > After update to new kernel (4.13.0-24) the system prompted me with > this. > > ProblemType: Package > DistroRelease: Ubuntu 17.10 > Package: nvidia-384 384.90-0ubuntu3.17.10.2 > ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13 > Uname: Linux 4.13.0-22-generic x86_64 > NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia > ApportVersion: 2.20.7-0ubuntu3.7 > Architecture: amd64 > DKMSKernelVersion: 4.13.0-24-generic > Date: Mon Jan 8 16:30:09 2018 > PackageVersion: 384.90-0ubuntu3.17.10.2 > Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, > 3.6.3-0ubuntu2 > PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, > 2.7.14-2ubuntu1 > RelatedPackageVersions: >dpkg 1.18.24ubuntu1 >apt 1.5.1 > SourcePackage: nvidia-graphics-drivers-384 > Title: nvidia-384 384.90-0ubuntu3.17.10.2: nvidia-384 kernel module > failed to build > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/ > 1741914/+subscriptions > -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1741914 Title: artful-proposed 4.13.0-24: kernel module failed to build [Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1741914/+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 1735594] Re: ubuntu automatically logs out when hovering sidebar
xserver-xorg-core: Installed: (none) Candidate: 2:1.18.4-0ubuntu0.7 Version table: 2:1.18.4-0ubuntu0.7 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 2:1.18.4-0ubuntu0.2 0 100 /var/lib/dpkg/status 2:1.18.3-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages -- 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/1735594 Title: ubuntu automatically logs out when hovering sidebar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1741914] Re: artful-proposed 4.13.0-24: kernel module failed to build [Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfutils-
It looks like this bug is now fixed as of 1 hour ago, in linux 4.13.0-25.29. You had to be unlucky to have an artful system on proposed do an update during the previous day and get the faulty package linux 4.13.0-24. That one doesn't exist any more so this bug should quieten down now. See bug 1741955 for updates. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1741914 Title: artful-proposed 4.13.0-24: kernel module failed to build [Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1741914/+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 1741914] Re: artful-proposed 4.13.0-24: kernel module failed to build [Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfutils-
** Changed in: nvidia-graphics-drivers-384 (Ubuntu) Status: Fix Released => Confirmed ** Also affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1741914 Title: artful-proposed 4.13.0-24: kernel module failed to build [Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1741914/+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 1742101] Re: Xorg crashed with SIGABRT in RRProviderAutoConfigGpuScreen() from xf86AutoConfigOutputDevices() from InitOutput() from dix_main() from __libc_start_main()
** Summary changed: - /usr/lib/xorg/Xorg:6:RRProviderAutoConfigGpuScreen:xf86AutoConfigOutputDevices:InitOutput:dix_main:__libc_start_main + Xorg crashed with SIGABRT in RRProviderAutoConfigGpuScreen() from xf86AutoConfigOutputDevices() from InitOutput() from dix_main() from __libc_start_main() -- 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/1742101 Title: Xorg crashed with SIGABRT in RRProviderAutoConfigGpuScreen() from xf86AutoConfigOutputDevices() from InitOutput() from dix_main() from __libc_start_main() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1742101/+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 1742101] [NEW] Xorg crashed with SIGABRT in RRProviderAutoConfigGpuScreen() from xf86AutoConfigOutputDevices() from InitOutput() from dix_main() from __libc_start_main()
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.19.5-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/d10c2e09338f4f04f7439218fd0b1fff3abaebd8 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 kylin-17.10 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/1742101 Title: Xorg crashed with SIGABRT in RRProviderAutoConfigGpuScreen() from xf86AutoConfigOutputDevices() from InitOutput() from dix_main() from __libc_start_main() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1742101/+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 1731261] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_log_handler(msg="Error sending request: Broken pipe\n...")
It looks like this is probably a result of gnome-shell crashing. That would bring down mutter which is internal to gnome-shell breaking the connection to Xwayland, making it crash. Really we need to modify Xwayland to not SIGABRT on such errors, because they are just errors and not bugs in Xwayland itself. ** Summary changed: - Xwayland crashed with SIGABRT in OsAbort() + Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_log_handler(msg="Error sending request: Broken pipe\n...") ** Information type changed from Private to Public -- 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/1731261 Title: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_log_handler(msg="Error sending request: Broken pipe\n...") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1731261/+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 1731911] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_read_events() from ospoll_wait()
** Project changed: xorg-server => ubuntu ** Changed in: ubuntu Status: Confirmed => New ** Changed in: ubuntu Remote watch: Red Hat Bugzilla #1511681 => None ** No longer affects: ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1731911 Title: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_read_events() from ospoll_wait() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1731911/+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 1732012] Re: After turning display (LCD TV) off and then back on, session ends and Ubuntu goes back to the logon screen
Next time this problem occurs, please look in /var/crash for .crash files. If any are found then please upload them using this command only: ubuntu-bug /var/crash/YOURFILE.crash And then add a comment in this bug telling us the newly-created bug ID. ** Package changed: xorg-server (Ubuntu) => gnome-shell (Ubuntu) ** 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-server in Ubuntu. https://bugs.launchpad.net/bugs/1732012 Title: After turning display (LCD TV) off and then back on, session ends and Ubuntu goes back to the logon screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1732012/+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 1736328] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_read_events() from ospoll_wait()
*** This bug is a duplicate of bug 1731911 *** https://bugs.launchpad.net/bugs/1731911 ** This bug has been marked a duplicate of bug 1731911 Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_read_events() from ospoll_wait() -- 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/1736328 Title: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_read_events() from ospoll_wait() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1736328/+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 1731911] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_read_events() from ospoll_wait()
This bug is also being tracked in: https://errors.ubuntu.com/problem/c27f5c4fef272640ec1027318712f0434c7c8857 ** Summary changed: - Xwayland crashed with SIGABRT in OsAbort() + Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_read_events() from ospoll_wait() ** Description changed: + https://errors.ubuntu.com/problem/c27f5c4fef272640ec1027318712f0434c7c8857 + + --- + no idea how to reproduce ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Mon Nov 13 13:55:16 2017 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: - bbswitch, 0.8, 4.13.0-15-generic, x86_64: installed - bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed + bbswitch, 0.8, 4.13.0-15-generic, x86_64: installed + bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed ExecutablePath: /usr/bin/Xwayland ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:1507] + Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:1507] InstallationDate: Installed on 2013-09-03 (1531 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) MachineType: ASUSTeK COMPUTER INC. UX32VD ProcCmdline: /usr/bin/Xwayland :1024 -rootless -terminate -core -listen 4 -listen 5 -displayfd 6 ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=fr_FR.UTF-8 - SHELL=/bin/false + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fr_FR.UTF-8 + SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=1004226d-a9db-46c7-bd28-eca0806c12f2 ro pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 init=/lib/systemd/systemd-bootchart Signal: 6 SourcePackage: xorg-server StacktraceTop: - OsAbort () - ?? () - FatalError () - ?? () - ?? () + OsAbort () + ?? () + FatalError () + ?? () + ?? () Title: Xwayland crashed with SIGABRT in OsAbort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: - + dmi.bios.date: 01/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32VD.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32VD 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.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX32VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.85-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 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+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-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/1731911 Title: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_read_events() from ospoll_wait() To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1731911/+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 1725180] Re: xwayland animations are not smooth
It sounds like you're referring to gnome-shell and not Xwayland. ** Package changed: xorg-server (Ubuntu) => gnome-shell (Ubuntu) ** Summary changed: - xwayland animations are not smooth + Shell animations are not smooth ** Tags added: performance ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New -- 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/1725180 Title: Shell animations are not smooth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725180/+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 1740146] Re: System slow on wayland, lagging mouse and programs on 17.10 & 18.04
** Package changed: xorg-server (Ubuntu) => gnome-shell (Ubuntu) ** Tags added: performance ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New -- 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/1740146 Title: System slow on wayland, lagging mouse and programs on 17.10 & 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1740146/+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 1742089] [NEW] Third unkown screen
Public bug reported: After updating a third unknown screen appeared, apparently connected to the vga port according to xrandr ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98 Uname: Linux 4.4.0-104-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is een map: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.90 Tue Sep 19 19:17:35 PDT 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Jan 9 09:35:25 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-104-generic, x86_64: installed nvidia-384, 384.90, 4.4.0-104-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller [1028:05cc] NVIDIA Corporation GK107GLM [Quadro K1100M] [10de:0ff6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GK107GLM [Quadro K1100M] [1028:15cc] InstallationDate: Installed on 2017-01-03 (370 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Precision M4800 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic root=UUID=21e3988f-d702-4bae-b6e3-54620f292e02 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0T3YTY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd05/14/2017:svnDellInc.:pnPrecisionM4800:pvr00:rvnDellInc.:rn0T3YTY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- 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/1742089 Title: Third unkown screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1742089/+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 1696929] Re: Touchpads are unresponsive and laggy for small finger movements
Actually we may be blocked waiting to see if the first fix for James' issue lands: https://lists.freedesktop.org/archives/wayland- devel/2018-January/036475.html We should include that if it does. The second fix for James' issue we can ignore providing it stays a kernel problem: https://bugs.freedesktop.org/show_bug.cgi?id=104533 ** Bug watch added: freedesktop.org Bugzilla #104533 https://bugs.freedesktop.org/show_bug.cgi?id=104533 ** Description changed: Some laptop touchpads are annoyingly unresponsive when the software implements any kind of hysteresis. This is a regression caused by the introduction of libinput, visible on at least Lenovo X1 Carbon gen 4 and 5, Dell XPS 13, and Apple Macbook Air. WORKAROUND (1) 1. Log into "Ubuntu on Xorg" only. This workaround only works for Xorg. 2. sudo apt install xserver-xorg-input-synaptics - 3. Tweak your personal preferences using 'synclient' (the GUI settings won't work any more). + 3. Tweak your personal preferences using 'synclient' (the GUI settings won't work any more). For example: +synclient HorizHysteresis=0 VertHysteresis=0 WORKAROUND (2) 1. Downgrade to version 1.9.4-1 of libinput: https://launchpad.net/ubuntu/+source/libinput/1.9.4-1/+build/13855729 That version contained the fix for this bug, briefly. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libinput10 1.6.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Fri Jun 9 14:52:18 2017 InstallationDate: Installed on 2017-06-08 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170607) SourcePackage: libinput UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1696929 Title: Touchpads are unresponsive and laggy for small finger movements To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/1696929/+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 1710862] Re: Synaptics s3203 touchpad on Dell XPS12-9Q33 has no working buttons after recent upgrade
Ah, yes. Seems to be there: [ 6.062] (II) LoadModule: "synaptics" [ 6.063] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so ** Changed in: xserver-xorg-input-synaptics (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1710862 Title: Synaptics s3203 touchpad on Dell XPS12-9Q33 has no working buttons after recent upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1710862/+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 1710862] Re: Synaptics s3203 touchpad on Dell XPS12-9Q33 has no working buttons after recent upgrade
Are you sure you have xserver-xorg-input-synaptics installed? Ubuntu 17.10 doesn't ship with it any more. ** Changed in: xserver-xorg-input-synaptics (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1710862 Title: Synaptics s3203 touchpad on Dell XPS12-9Q33 has no working buttons after recent upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1710862/+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 1726939] Re: Touchpad pointer shake
Please run this command on the affected machine to help us gather more information: apport-collect 1726939 Please also tell us if the problem returns if you remove xserver-xorg- input-synaptics. ** Package changed: xserver-xorg-input-synaptics (Ubuntu) => libinput (Ubuntu) ** Changed in: libinput (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1726939 Title: Touchpad pointer shake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1726939/+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 1739649] Re: Touchpad does not work, "lost sync at byte 6"
See also bug 1553264 ** Package changed: xserver-xorg-input-synaptics (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1739649 Title: Touchpad does not work, "lost sync at byte 6" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739649/+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 1696929] Re: Touchpads are unresponsive and laggy for small finger movements
** Summary changed: - Touchpads are unresponsive and laggy + Touchpads are unresponsive and laggy for small finger movements -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1696929 Title: Touchpads are unresponsive and laggy for small finger movements To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/1696929/+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 1696929] Re: Touchpads are unresponsive and laggy
** Description changed: Some laptop touchpads are annoyingly unresponsive when the software - implements any kind of hysteresis. This includes Lenovo X1 Carbon gen 4 - and 5. Such devices have lower precision and higher lag in the touchpad - hardware than you might expect, so need the software to not slow them - down further. + implements any kind of hysteresis. This is a regression caused by the + introduction of libinput, visible on at least Lenovo X1 Carbon gen 4 and + 5, Dell XPS 13, and Apple Macbook Air. - The problem now is that using libinput by default slows down all - touchpads and makes them less precise. For hardware that was already - unresponsive, introducing software that further reduces the - responsiveness is very frustrating, borderline unusable. + WORKAROUND (1) - When we were using Xorg the simple solution was to adjust hysteresis - with 'synclient'. However now we're using Wayland we're stuck with - libinput and I don't know how to fix it any more. Even Xorg logins seem - to use libinput now, so there's no 'synclient' workaround available - there anymore either. + 1. Log into "Ubuntu on Xorg" only. This workaround only works for Xorg. + 2. sudo apt install xserver-xorg-input-synaptics + 3. Tweak your personal preferences using 'synclient' (the GUI settings won't work any more). + + WORKAROUND (2) + + 1. Download and install the exact version 1.9.4-1 of libinput: https://launchpad.net/ubuntu/+source/libinput/1.9.4-1/+build/13855729 + That version contained the fix for this bug, briefly. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libinput10 1.6.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Fri Jun 9 14:52:18 2017 InstallationDate: Installed on 2017-06-08 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170607) SourcePackage: libinput UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: Some laptop touchpads are annoyingly unresponsive when the software implements any kind of hysteresis. This is a regression caused by the introduction of libinput, visible on at least Lenovo X1 Carbon gen 4 and 5, Dell XPS 13, and Apple Macbook Air. WORKAROUND (1) 1. Log into "Ubuntu on Xorg" only. This workaround only works for Xorg. 2. sudo apt install xserver-xorg-input-synaptics 3. Tweak your personal preferences using 'synclient' (the GUI settings won't work any more). WORKAROUND (2) - 1. Download and install the exact version 1.9.4-1 of libinput: https://launchpad.net/ubuntu/+source/libinput/1.9.4-1/+build/13855729 + 1. Downgrade to version 1.9.4-1 of libinput: https://launchpad.net/ubuntu/+source/libinput/1.9.4-1/+build/13855729 That version contained the fix for this bug, briefly. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libinput10 1.6.3-1ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Fri Jun 9 14:52:18 2017 InstallationDate: Installed on 2017-06-08 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170607) SourcePackage: libinput UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1696929 Title: Touchpads are unresponsive and laggy To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/1696929/+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
