[Touch-packages] [Bug 869881] Re: rsyslogd fails to load lmnsd_gtls.so
I tested a rsyslog client talking to a rsyslog server both using `rsyslog-gnutls 8.2112.0-2ubuntu2.2` on Ubuntu 22.04 and it worked fine. There, there is no error loading "/usr/lib/x86_64-linux- gnu/rsyslog/lmnsd_gtls.so" as long as the `-gnutls` package is installed. I used only a cert (from Let's Encrypt) on the server side but I enabled Apparmor on both sides. I'm not sure if your error could have been due to having enabled the Apparmor profile and using certificate files stored under `/root/ssl` which isn't permitted by the Apparmor profile? Marking as incomplete until you can report on the Apparmor profile situation. ** Changed in: rsyslog (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/869881 Title: rsyslogd fails to load lmnsd_gtls.so Status in rsyslog package in Ubuntu: Incomplete Bug description: rsyslog fails to load tls functionality. Relevant section from rsyslog.conf: (full file is attached, contents of /etc/rsyslog.d is unmodified from package defaults, and running `rsyslogd -f /etc/rsyslog.conf -c4 -N1` does not show any configuration errors. The remote logging section is copy-pasted from a working debian 6 box) REMOTE LOGGING # certificate files $DefaultNetstreamDriverCAFile /root/ssl/ca.pem $DefaultNetstreamDriverCertFile /root/ssl/generic-cert.pem $DefaultNetstreamDriverKeyFile /root/ssl/generic-key.pem # set up the action $DefaultNetstreamDriver gtls # use gtls netstream driver $ActionSendStreamDriverMode 1 # require TLS for the connection $ActionSendStreamDriverAuthMode x509/certvalid *.* @@(o)10.181.60.127:10514 # send (all) messages Error written to syslog: Oct 7 09:59:01 alpha rsyslogd-2068: could not load module '/usr/lib/rsyslog/lmnsd_gtls.so', rsyslog error -2078 Relevant info from running in debug mode (full debug output is attached): 7508.666438320:main queue:Reg/w0: unexpected GnuTLS error -64 in nsd_gtls.c:574: Error while reading file. I have also attached strace output from rsyslog. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: rsyslog-gnutls 4.2.0-2ubuntu8.1 Uname: Linux 2.6.35.4-rscloud x86_64 Architecture: amd64 Date: Fri Oct 7 09:38:03 2011 ProcEnviron: SHELL=/bin/bash SourcePackage: rsyslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/869881/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1926139] Re: dhclient: thread concurrency race leads to DHCPOFFER packets not being received
** Summary changed: - dhclient doesn't receive dhcp offer from kernel + dhclient: thread concurrency race leads to DHCPOFFER packets not being received -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1926139 Title: dhclient: thread concurrency race leads to DHCPOFFER packets not being received Status in bind9-libs package in Ubuntu: Fix Released Status in isc-dhcp package in Ubuntu: Invalid Status in bind9-libs source package in Focal: In Progress Status in bind9-libs source package in Jammy: In Progress Bug description: Platform: Qemu/libvirt on AMD64 Ubuntu version: 20.04 isc-dhcp-client version: 4.4.1-2.1ubuntu5 Problem: When dhclient is used during boot every few reboots the DHCP OFFER packets aren't pushed from the kernel to dhclient. The DISCOVER packets can be seen in strace and tcpdump. The OFFER packets can be seen in tcpdump, but no read event is triggered. Ubuntu 18.04 doesn't have the problem, neither does Debian 10. Building these dhclient versions on Ubuntu 20.04 alleviates the problem a little, but it still occurs. So this issue might also be kernel related. Attached diff shows a strace of all threads and a pcap showing the tcpdump output. Edit: - Sometimes the dhclient command does receive the OFFER packet and connection is restored. - In my testing running dhclient manually from the terminal when the OFFERs aren't received will result in a new dhclient session which does receive the OFFER packet and connection is restored. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9-libs/+bug/1926139/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1926139] Re: dhclient doesn't receive dhcp offer from kernel
Attached is a debdiff for Jammy which fixes this bug. ** Patch added: "Debdiff for bind9-libs for Jammy" https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1926139/+attachment/5641516/+files/lp1926139_jammy.debdiff ** Tags added: focal jammy sts ** Also affects: bind9-libs (Ubuntu) Importance: Undecided Status: New ** Also affects: isc-dhcp (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: bind9-libs (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: isc-dhcp (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: bind9-libs (Ubuntu Focal) Importance: Undecided Status: New ** No longer affects: isc-dhcp (Ubuntu Focal) ** No longer affects: isc-dhcp (Ubuntu Jammy) ** Changed in: isc-dhcp (Ubuntu) Status: New => Invalid ** Changed in: bind9-libs (Ubuntu Focal) Status: New => In Progress ** Changed in: bind9-libs (Ubuntu Jammy) Status: New => In Progress ** Changed in: bind9-libs (Ubuntu) Status: New => Fix Released ** Changed in: bind9-libs (Ubuntu Focal) Importance: Undecided => High ** Changed in: bind9-libs (Ubuntu Jammy) Importance: Undecided => High ** Changed in: bind9-libs (Ubuntu Focal) Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Changed in: bind9-libs (Ubuntu Jammy) Assignee: (unassigned) => Matthew Ruffell (mruffell) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1926139 Title: dhclient doesn't receive dhcp offer from kernel Status in bind9-libs package in Ubuntu: Fix Released Status in isc-dhcp package in Ubuntu: Invalid Status in bind9-libs source package in Focal: In Progress Status in bind9-libs source package in Jammy: In Progress Bug description: Platform: Qemu/libvirt on AMD64 Ubuntu version: 20.04 isc-dhcp-client version: 4.4.1-2.1ubuntu5 Problem: When dhclient is used during boot every few reboots the DHCP OFFER packets aren't pushed from the kernel to dhclient. The DISCOVER packets can be seen in strace and tcpdump. The OFFER packets can be seen in tcpdump, but no read event is triggered. Ubuntu 18.04 doesn't have the problem, neither does Debian 10. Building these dhclient versions on Ubuntu 20.04 alleviates the problem a little, but it still occurs. So this issue might also be kernel related. Attached diff shows a strace of all threads and a pcap showing the tcpdump output. Edit: - Sometimes the dhclient command does receive the OFFER packet and connection is restored. - In my testing running dhclient manually from the terminal when the OFFERs aren't received will result in a new dhclient session which does receive the OFFER packet and connection is restored. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9-libs/+bug/1926139/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1926139] Re: dhclient doesn't receive dhcp offer from kernel
Attached is a debdiff for Focal which fixes this bug. ** Patch added: "Debdiff for bind9-libs for Focal" https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1926139/+attachment/5641515/+files/lp1926139_focal.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1926139 Title: dhclient doesn't receive dhcp offer from kernel Status in bind9-libs package in Ubuntu: Fix Released Status in isc-dhcp package in Ubuntu: Invalid Status in bind9-libs source package in Focal: In Progress Status in bind9-libs source package in Jammy: In Progress Bug description: Platform: Qemu/libvirt on AMD64 Ubuntu version: 20.04 isc-dhcp-client version: 4.4.1-2.1ubuntu5 Problem: When dhclient is used during boot every few reboots the DHCP OFFER packets aren't pushed from the kernel to dhclient. The DISCOVER packets can be seen in strace and tcpdump. The OFFER packets can be seen in tcpdump, but no read event is triggered. Ubuntu 18.04 doesn't have the problem, neither does Debian 10. Building these dhclient versions on Ubuntu 20.04 alleviates the problem a little, but it still occurs. So this issue might also be kernel related. Attached diff shows a strace of all threads and a pcap showing the tcpdump output. Edit: - Sometimes the dhclient command does receive the OFFER packet and connection is restored. - In my testing running dhclient manually from the terminal when the OFFERs aren't received will result in a new dhclient session which does receive the OFFER packet and connection is restored. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9-libs/+bug/1926139/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
Hi guys, I want to share my success story: It happened after I've updated to CUDA repo's nvidia drivers :) my `initrd.img-5.15.0-58-generic` (`ls -lah /boot`) was about 192M and using tuning option of the `/etc/initramfs-tools/initramfs.conf` file I've decreased it (`sudo update-initramfs -c -k 5.15.0-58-generic`) to 116M and now it works =) my `/etc/initramfs-tools/initramfs.conf` ``` # # initramfs.conf # Configuration file for mkinitramfs(8). See initramfs.conf(5). # # Note that configuration options from this file can be overridden # by config files in the /etc/initramfs-tools/conf.d directory. # # MODULES: [ most | netboot | dep | list ] # # most - Add most filesystem and all harddrive drivers. # # dep - Try and guess which modules to load. # # netboot - Add the base modules, network modules, but skip block devices. # # list - Only include modules from the 'additional modules' list # # original #MODULES=most # patch MODULES=dep # # BUSYBOX: [ y | n | auto ] # # Use busybox shell and utilities. If set to n, klibc utilities will be used. # If set to auto (or unset), busybox will be used if installed and klibc will # be used otherwise. # BUSYBOX=auto # # COMPRESS: [ gzip | bzip2 | lz4 | lzma | lzop | xz | zstd ] # # original # COMPRESS=zstd COMPRESS=xz # # DEVICE: ... # # Specify a specific network interface, like eth0 # Overridden by optional ip= or BOOTIF= bootarg # DEVICE= # # NFSROOT: [ auto | HOST:MOUNT ] # NFSROOT=auto # # RUNSIZE: ... # # The size of the /run tmpfs mount point, like 256M or 10% # Overridden by optional initramfs.runsize= bootarg # RUNSIZE=10% # # FSTYPE: ... # # The filesystem type(s) to support, or "auto" to use the current root # filesystem type # FSTYPE=auto # patch export XZ_OPT='--lzma2=preset=0,dict=8M' ``` Hope it will help you (and don't forget about `sudo update-initramfs -c -k YOUR_VERSION-generic`). Keep yourself safe (from kernel panics too) and Glory to Ukraine! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1842320 Title: Can't boot: "error: out of memory." immediately after the grub menu Status in grub: Unknown Status in OEM Priority Project: Triaged Status in grub2-signed package in Ubuntu: Fix Committed Status in grub2-unsigned package in Ubuntu: Fix Released Status in initramfs-tools package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Confirmed Bug description: [Workaround] Some workarounds have been suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/comments/125 [Impact] * In some cases, if the users’ initramfs grow bigger, then it’ll likely not be able to be loaded by grub2. * Some real cases from OEM projects: In many built-in 4k monitor laptops with nvidia drivers, the u-d-c puts the nvidia*.ko to initramfs which grows the initramfs to ~120M. Also the gfxpayload=auto will remain to use 4K resolution since it’s what EFI POST passed. In this case, the grub isn't able to load initramfs because the grub_memalign() won't be able to get suitable memory for the larger file: ``` #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376 #1 0x7dd7b074 in grub_malloc (size=592214020) at ../../../grub-core/kern/mm.c:408 #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076) at ../../../grub-core/kern/verifiers.c:150 #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 "/boot/initrd.img-5.17.0-1011-oem", type=131076) at ../../../grub-core/kern/file.c:121 #4 0x7bcd5a30 in ?? () #5 0x7fe21247 in ?? () #6 0x7bc030c8 in ?? () #7 0x00017fe21238 in ?? () #8 0x7bcd5320 in ?? () #9 0x7fe21250 in ?? () #10 0x in ?? () ``` Based on grub_mm_dump, we can see the memory region starvation in <1G addresses: Type StartEnd # Pages Attributes Available -00086FFF 0087 000F BS_Data00087000-00087FFF 0001 000F Available 00088000-0009EFFF 0017 000F Reserved 0009F000-0009 0001 000F Available 0010-00FF 0F00 000F LoaderCode 0100-01021FFF 0022 000F Available 01022000-238A7FFF 00022886 000F BS_Data238A8000-23927FFF 0080 000F Available 23928000-28860FFF 4F39 000F BS_Data28861000-2AB09FFF 22A9 000F LoaderCode 2AB0A000-2ACF8FFF 01EF 000F BS_Data
[Touch-packages] [Bug 2002923] Re: Please merge 2.5.0-4 into lunar
** Changed in: python-testtools (Ubuntu) Status: New => In Progress ** Changed in: python-testtools (Ubuntu) Assignee: (unassigned) => Vladimir Petko (vpa1977) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-testtools in Ubuntu. https://bugs.launchpad.net/bugs/2002923 Title: Please merge 2.5.0-4 into lunar Status in python-testtools package in Ubuntu: In Progress Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-testtools/+bug/2002923/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2002923] Re: Please merge 2.5.0-4 into lunar
** Merge proposal linked: https://code.launchpad.net/~vpa1977/ubuntu/+source/python-testtools/+git/python-testtools/+merge/435788 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-testtools in Ubuntu. https://bugs.launchpad.net/bugs/2002923 Title: Please merge 2.5.0-4 into lunar Status in python-testtools package in Ubuntu: New Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-testtools/+bug/2002923/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2002923] [NEW] Please merge 2.5.0-4 into lunar
Public bug reported: tracking bug ** Affects: python-testtools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-testtools in Ubuntu. https://bugs.launchpad.net/bugs/2002923 Title: Please merge 2.5.0-4 into lunar Status in python-testtools package in Ubuntu: New Bug description: tracking bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-testtools/+bug/2002923/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2002918] Re: ERROR: rejecting excluded file-list name:
** Description changed: Problems related to --exclude and --filter=protect options are raising - error while executiong rsync. + error while execution of rsync. - The following error is launched: ERROR: rejecting excluded file-list name: + The following error is launched: + ERROR: rejecting excluded file-list name: rsync error: protocol incompatibility (code 2) at flist.c(994) [receiver=3.2.5] rsync: [sender] write error: Broken pipe (32) It was already reported in: https://github.com/WayneD/rsync/issues/375 There is also a patch released. --- lsb_release -rd Description:Ubuntu 22.10 Release:22.10 apt-cache policy rsync rsync: - Instalado: 3.2.5-1 - Candidato: 3.2.5-1 + Instalado: 3.2.5-1 + Candidato: 3.2.5-1 ** Summary changed: - ERROR: rejecting excluded file-list name: + ERROR: rejecting excluded file-list name -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/2002918 Title: ERROR: rejecting excluded file-list name Status in rsync package in Ubuntu: New Bug description: Problems related to --exclude and --filter=protect options are raising error while execution of rsync. The following error is launched: ERROR: rejecting excluded file-list name: rsync error: protocol incompatibility (code 2) at flist.c(994) [receiver=3.2.5] rsync: [sender] write error: Broken pipe (32) It was already reported in: https://github.com/WayneD/rsync/issues/375 There is also a patch released. --- lsb_release -rd Description:Ubuntu 22.10 Release:22.10 apt-cache policy rsync rsync: Instalado: 3.2.5-1 Candidato: 3.2.5-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2002918/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2002918] [NEW] ERROR: rejecting excluded file-list name
Public bug reported: Problems related to --exclude and --filter=protect options are raising error while execution of rsync. The following error is launched: ERROR: rejecting excluded file-list name: rsync error: protocol incompatibility (code 2) at flist.c(994) [receiver=3.2.5] rsync: [sender] write error: Broken pipe (32) It was already reported in: https://github.com/WayneD/rsync/issues/375 There is also a patch released. --- lsb_release -rd Description:Ubuntu 22.10 Release:22.10 apt-cache policy rsync rsync: Instalado: 3.2.5-1 Candidato: 3.2.5-1 ** Affects: rsync (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/2002918 Title: ERROR: rejecting excluded file-list name Status in rsync package in Ubuntu: New Bug description: Problems related to --exclude and --filter=protect options are raising error while execution of rsync. The following error is launched: ERROR: rejecting excluded file-list name: rsync error: protocol incompatibility (code 2) at flist.c(994) [receiver=3.2.5] rsync: [sender] write error: Broken pipe (32) It was already reported in: https://github.com/WayneD/rsync/issues/375 There is also a patch released. --- lsb_release -rd Description:Ubuntu 22.10 Release:22.10 apt-cache policy rsync rsync: Instalado: 3.2.5-1 Candidato: 3.2.5-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2002918/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1664501] Re: Unable to wake up monitor after it goes to sleep (after locking x session, for example)
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: xorg (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1664501 Title: Unable to wake up monitor after it goes to sleep (after locking x session, for example) Status in xorg package in Ubuntu: Incomplete Bug description: Additional info: lsb_release: Description: Ubuntu 16.04.1 LTS Release: 16.04 I'm using an external monitor attached via VGA (seen as DP2 in xrandr output) in an extended desktop configuration (not cloned). Whenever the X session starts some kind of screen saving (for example, after locking the screen), the external monitor and the laptop screen both go to a saving power state. After that, If I try to wake them up (moving cursor, touch keys, etc.), only the laptop's panel goes back. The external monitor stays in a suspended state. If I force it to wake up and scan inputs, it doesn't find any, and it doesn't appear as conencted in xrandr otput. The only way I've found to wake it up is by performing the following sequence of operations: ALT+F1 [switch to first tty/console] --> this does wake up and activate the monitor, mirroring login as my user $ xrandr -d :0 #DP2 still doesn't appear logout ALT+F7 [go back to X] At this point, the external monitor is working and X detects it and re-enables the extended desktop Doing just ALT+F1/ALT+F7, doesn't work (I need to execute xrandr in order to make the whole thing work) Doing xrandr from the graphical environment (directly in a xterminal in the Xsession) doesn't wake up the monitor Looks like there's no need to add any addictional operation/parameter to xrandr in order to make this process work, no need to set output settings, etc. Just issue "xrandr -d :0" and things magically work Thanks in advance ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 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 Feb 14 10:54:19 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:8079] MachineType: HP HP EliteBook 840 G3 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-62-generic root=ZFS=rpool/ROOT/ubuntu ro boot=zfs quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2016 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.05 dmi.board.name: 8079 dmi.board.vendor: HP dmi.board.version: KBC Version 85.61 dmi.chassis.asset.tag: 5CG6247TWJ dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN75Ver.01.05:bd03/22/2016:svnHP:pnHPEliteBook840G3:pvr:rvnHP:rn8079:rvrKBCVersion85.61:cvnHP:ct10:cvr: dmi.product.name: HP EliteBook 840 G3 dmi.sys.vendor: HP version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 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: Tue Feb 14 10:49:09 2017 xserver.configfile: default xserver.errors:
[Touch-packages] [Bug 1432413] Re: Synaptic Touchpad xevents are hijacked under X
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: xorg (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1432413 Title: Synaptic Touchpad xevents are hijacked under X Status in xorg package in Ubuntu: Incomplete Bug description: Synaptic Touchpad xevents are hijacked under X11. I have a problem with the synaptic touch-pad on my Acer Aspire that started around a week ago. The problem can be described as that there is a massive amount of xevents being generated and appearing to originate from the touch-pad even though the touch-pad is not used. I have tested the HW which seems to work fine. The test performed is to start a terminal session (Ctrl + Alt + 2) before the fault occurs and check the xevents by running ~$ sudo evtest /dev/input/eventX where the X to use is found in /proc/bus/input/devices and found by running ~$ cat /proc/bus/input/devices |grep mouse No matter how much the touch-pad is used will the console show the corresponding events which indicates that HW and driver works OK as long it is not under X When the problem has occurred (in Desktop mode) is it easy (but inconvenient) to get back to normal by key combo Fn+F7 twice, turn off touch-pad and then turn on again. And more, one can get unlucky in the sense that the generated events could click somewhere one do not want to click. During the problem is it impossible to use the mouse since it flies around (mostly going in a bottom to top of screen direction) but one can check the generated events using evtest again. How can I help troubleshooting the problem? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 .tmp.unity.support.test.0: 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: Sun Mar 15 19:51:13 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation ValleyView Gen7 [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0933] InstallationDate: Installed on 2015-02-21 (22 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Acer Aspire E3-112 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic root=UUID=a97d0b51-4244-48ca-ba87-bc3a38a8b62d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: R2 dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd08/20/2014:svnAcer:pnAspireE3-112:pvrV1.08:rvnAcer:rnR2:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire E3-112 dmi.product.version: V1.08 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 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: Sun Mar 15 18:59:07 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1576 vendor BOE xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 To manage
[Touch-packages] [Bug 1664596] Re: xset led on, enables mouse-keys
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1664596 Title: xset led on, enables mouse-keys Status in xorg package in Ubuntu: Incomplete Bug description: I have a backlit keyboard on a stationary PC. The back-light goes off at random intervals. I'm a heavy user of numeric keypad. That turns into mouse-keys at intervals as well. Both issues results in a rather annoying user experience. I have not been able to determine the reason or what lead up to this. But it often happen whenever I take a short break. (after a few minutes of inactivity) Therefore I periodically run a script to turn the back-light back on and disable mouse-keys. It turns out that setting the back-light on, enables the mouse-keys again! Something is wired with this. But this last part is easy to reproduce with this script: #!/bin/sh /usr/bin/gsettings set org.gnome.desktop.a11y.keyboard mousekeys-enable false # disables mouse-keys /usr/bin/gsettings get org.gnome.desktop.a11y.keyboard mousekeys-enable # reports false and mouse-keys are actually disabled xset led on /usr/bin/gsettings get org.gnome.desktop.a11y.keyboard mousekeys-enable # reports false, but mouse-keys are actually enabled! /usr/bin/gsettings set org.gnome.desktop.a11y.keyboard mousekeys-enable false # disables mouse-keys again. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 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 Feb 14 15:17:53 2017 DistUpgraded: 2016-06-03 10:07:29,690 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] [1002:683d] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Cape Verde XT [Radeon HD 7770/8760 / R7 250X] [1682:3232] InstallationDate: Installed on 2015-07-29 (565 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: ASUSTeK Computer INC. CM6330_CM6630_CM6730_CM6830-8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic root=UUID=458544bf-05e1-4b76-93ee-1c5cfa8f7683 ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-06-03 (256 days ago) dmi.bios.date: 08/27/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0402 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: CM6330_CM6630_CM6730_CM6830 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev x.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0402:bd08/27/2012:svnASUSTeKComputerINC.:pnCM6330_CM6630_CM6730_CM6830-8:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCM6330_CM6630_CM6730_CM6830:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: CM6330_CM6630_CM6730_CM6830-8 dmi.product.version: System Version dmi.sys.vendor: ASUSTeK Computer 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.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 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: Tue Feb 14 12:39:26 2017 xserver.configfile: default
[Touch-packages] [Bug 1589056] Re: HDMI does not work
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: xorg (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1589056 Title: HDMI does not work Status in xorg package in Ubuntu: Incomplete Bug description: xrandr displays "HDMI-1 disconnected (normal left inverted right x axis y axis)" even if it is connected using a HDMI cable to a Samsung monitor (model S27B350H) that has both HDMI and VGA connectors. WORKAROUND: Use the Nvidia proprietary driver. Graphics by lspci -vvv: 01:00.0 VGA compatible controller: NVIDIA Corporation G84GLM [Quadro FX 570M] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device 30c5 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- [disabled] Capabilities: Kernel driver in use: nouveau --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: root: clean, 247512/1281120 files, 1867600/512 blocks [[0;1;31mFAILED[0m] Failed to start Automatically refresh installed snaps. See 'systemctl status snapd.refresh.service' for details. [[0;32m OK [0m] Started Authenticate and Authorize Users to Run Privileged Tasks. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: 2016-06-24 18:11:48,939 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G84GLM [Quadro FX 570M] [103c:30c5] InstallationDate: Installed on 2015-11-21 (228 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic root=UUID=bdc3be24-dee9-4ead-bca0-c9b1e45a87e5 ro persistent quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Tags: xenial ubuntu Uname: Linux 4.4.0-28-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-06-24 (12 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1589056/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615864] Re: Screen resolution not saved after reboot or logout and back in
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. I'm setting the status of this bug to 'Incomplete' as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know which one(s) otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: xorg (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1615864 Title: Screen resolution not saved after reboot or logout and back in Status in xorg package in Ubuntu: Incomplete Bug description: The issue is that Ubuntu 16.04 does not save or read the saved screen resolution settings of 1920x1080 from my Vizio 42 inch TV HDMI connected to my computer. When booting into the desktop the mouse pointer is small as if in 1920x1080 but then changes to a larger pointer then the resolution is then 1280x720 which seems to what 16.04 falls back to. The TV reports the proper information under xrandr. gee@HTPC:~$ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 4096 x 4096 VGA-0 disconnected (normal left inverted right x axis y axis) TV-0 disconnected (normal left inverted right x axis y axis) HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 980mm x 580mm 1280x720 60.00 + 59.94 1920x1080 59.9459.94* 60.0560.0050.04 720x576 50.0050.08 720x480 59.94 640x480 59.93 WORKAROUND: Type at the terminal: xrandr -s 1920x1080 --- .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.131 Sun Nov 8 21:43:33 PST 2015 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.131, 4.4.0-34-generic, x86_64: installed nvidia-304, 304.131, 4.4.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation C68 [GeForce 7050 PV / nForce 630a] [10de:053a] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] C68 [GeForce 7050 PV / nForce 630a] [1462:349f] InstallationDate: Installed on 2016-08-20 (12 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 099a:7202 Zippy Technology Corp. Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: MSI MS-7349 NonfreeKernelModules: nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=377930d2-4053-4a10-96ef-8cac652e4c24 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Tags: xenial ubuntu Uname: Linux 4.4.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev pulse pulse-access sambashare sudo video _MarkForUpload: True dmi.bios.date: 03/19/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: CaptiveWorks CW-3000HD V2.37 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7349 dmi.board.vendor: MSI dmi.board.version: 1.0 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.:bvrCaptiveWorksCW-3000HDV2.37:bd03/19/2008:svnMSI:pnMS-7349:pvr1.0:rvnMSI:rnMS-7349:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: MS-7349 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
[Touch-packages] [Bug 1300620] Re: [Lenovo ThinkPad S1 Yoga] Middle button does not work for scrolling
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.
I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this is still an issue when using a currently
maintained release of Ubuntu then please let us know which one(s)
otherwise this bug report can be left to expire in approximately 60 days
time.
** Changed in: xorg (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1300620
Title:
[Lenovo ThinkPad S1 Yoga] Middle button does not work for scrolling
Status in xorg package in Ubuntu:
Incomplete
Bug description:
On my clickpad (Touchpad with no button) the middle mouse button
doesn't work for scrolling with trackpoint. I've configured a soft
middlemouse button area via the following script:
#!/bin/bash
TOUCHPAD="SynPS/2 Synaptics TouchPad"
TRACKPOINT="TPPS/2 IBM TrackPoint"
killall -9 syndaemon
echo "touchpad on"
xinput set-prop "${TOUCHPAD}" "Synaptics Off" 0
echo "setting soft button areas"
#Order: RightButtonAreaLeft, RightButtonAreaRight, RightButtonAreaTop,
RightButtonAreaBottom, MiddleButtonAreaLeft, MiddleButtonAreaRight,
MitddleButtonAreaTop, MiddleButtonAreaBottom"
xinput set-prop "${TOUCHPAD}" "Synaptics Soft Button Areas" 4000, 0, 4063, 0,
3000, 4000, 4063, 1500
#xinput set-prop "${TOUCHPAD}" "Synaptics Soft Button Areas" 4000, 0, 0,
4466, 3000, 3999, 0, 1500
echo "enable twofingerscrolling in both directions"
xinput set-prop "${TOUCHPAD}" "Synaptics Two-Finger Scrolling" 1, 1
echo "shortening upper and lower edge to reserve space for 'just button'
actions. Order: left, right, top, bottom"
xinput set-prop "${TOUCHPAD}" "Synaptics Area" 0, 0, 1500, 4000
#workaround for just scrolling
#xinput set-prop "${TOUCHPAD}" "Synaptics Area" 0, 4000, 1500, 0
echo "enabling palm detection"
xinput set-prop "${TOUCHPAD}" "Synaptics Palm Detection" 1
#echo "Middle mouse button emulation for scrolling on trackpoint"
#xinput set-prop "${TRACKPOINT}" "Evdev Wheel Emulation" 1
#xinput set-prop "${TRACKPOINT}" "Evdev Wheel Emulation Button" 2
#xinput set-prop "${TRACKPOINT}" "Evdev Wheel Emulation Timeout" 200
#xinput set-prop "${TRACKPOINT}" "Evdev Wheel Emulation Axes" 6 7 4 5 #
horizontal und vertikal
echo "enable tap events"
# RTCornerButton, RBCornerButton, LTCornerButton, LBCornerButton, TapButton1,
TapButton2, TapButton3
xinput set-prop "${TOUCHPAD}" "Synaptics Tap Action" 2, 3, 1, 1, 1, 3, 0
echo "list actual properties"
xinput list-props "${TOUCHPAD}"
echo "no touch while typing"
syndaemon -i 0.5 -d
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
Uname: Linux 3.13.0-20-generic x86_64
ApportVersion: 2.14-0ubuntu1
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: kwin
CurrentDesktop: KDE
Date: Tue Apr 1 09:02:37 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: kubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16]
(rev 0b) (prog-if 00 [VGA controller])
Subsystem: Lenovo Device [17aa:2217]
InstallationDate: Installed on 2014-03-25 (6 days ago)
InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140324)
LightdmGreeterLog:
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei
oder Verzeichnis nicht gefunden
QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
Bus::open: Can not get ibus-daemon's address.
IBusInputContext::createInputContext: no connection to ibus-daemon
file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135:
Unable to assign [undefined] to QString usersession
LightdmGreeterLogOld:
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Datei
oder Verzeichnis nicht gefunden
QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
Bus::open: Can not get ibus-daemon's address.
IBusInputContext::createInputContext: no connection to ibus-daemon
file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135:
Unable to assign [undefined] to QString usersession
MachineType: LENOVO 20C0S0AX00
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-20-generic.efi.signed
root=UUID=389305e0-f86b-4068-a352-fe5597926b87 ro rootflags=subvol=@
kopt=root=/dev/mapper/ray-root quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus:
