[Desktop-packages] [Bug 1852569] [NEW] Synaptics touchpad behaving erratically since 19.04/19.10 (it worked fine in 18.04)
Public bug reported: I don't know if xinput is the correct package to report this against but the touchpad has been messed up since 19.04 and it hasn't changed in 19.10. 18.04 worked normally. The symptom is basically that when tracking the pointer horizontally it moves very jerkily. Vertical movement is slightly better but still seems off. If I should report this against a difference package, let me know which one. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xinput 1.6.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Nov 14 11:40:28 2019 DistUpgraded: 2019-09-27 15:23:11,960 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:183f] InstallationDate: Installed on 2019-08-03 (102 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xinput UpgradeStatus: Upgraded to eoan on 2019-09-27 (47 days ago) dmi.bios.date: 09/07/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.27 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 183F dmi.board.vendor: Hewlett-Packard dmi.board.version: 56.32 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.27:bd09/07/2016:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr08871134591620100:rvnHewlett-Packard:rn183F:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: D1Q47EA#ABU dmi.product.version: 08871134591620100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xinput (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xinput in Ubuntu. https://bugs.launchpad.net/bugs/1852569 Title: Synaptics touchpad behaving erratically since 19.04/19.10 (it worked fine in 18.04) Status in xinput package in Ubuntu: New Bug description: I don't know if xinput is the correct package to report this against but the touchpad has been messed up since 19.04 and it hasn't changed in 19.10. 18.04 worked normally. The symptom is basically that when tracking the pointer horizontally it moves very jerkily. Vertical movement is slightly better but still seems off. If I should report this against a difference package, let me know which one. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xinput 1.6.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Nov 14 11:40:28 2019 DistUpgraded: 2019-09-27 15:23:11,960 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:183f] InstallationDate: Installed on 2019-08-03 (102 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xinput UpgradeStatus: Upgraded to eoan on 2019-09-27 (47 days ago) dmi.bios.date: 09/07/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.27 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 183F dmi.board.vendor: Hewlett-Packard dmi.board.version: 56.32 dmi.chassis.type: 10 dmi.chassis.vendor:
[Desktop-packages] [Bug 1720438] Re: brightness control broken nvidia
also did you do the update-grub part? but I do think this bug needs a proper fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1720438 Title: brightness control broken nvidia Status in gnome-power-manager package in Ubuntu: New Bug description: Ubuntu 17.10 beta 2 Nvidia 310M, 340.x official driver installed with Additional Drivers program The brightness control built into the laptop (Dell Vostro 3300) isn't changing the brightness. Normally I can use Fn + Up/Down arrow keys to change the brightness. The brightness control works fine in Ubuntu 16.04 with the same driver series. I don't know if this is a GNOME 3.26 bug but it's likely as I'm having the exact same problem with Fedora 26 on this laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1720438/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1720438] Re: brightness control broken nvidia
remember to click the 'This bug affects you' link near the top -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1720438 Title: brightness control broken nvidia Status in gnome-power-manager package in Ubuntu: New Bug description: Ubuntu 17.10 beta 2 Nvidia 310M, 340.x official driver installed with Additional Drivers program The brightness control built into the laptop (Dell Vostro 3300) isn't changing the brightness. Normally I can use Fn + Up/Down arrow keys to change the brightness. The brightness control works fine in Ubuntu 16.04 with the same driver series. I don't know if this is a GNOME 3.26 bug but it's likely as I'm having the exact same problem with Fedora 26 on this laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1720438/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1720438] Re: brightness control broken nvidia
I've managed to use a workaround to make the hotkeys work. I added acpi_osi=Linux to the grub config file and did an update-grub and it works. But I think it would be better if this was looked into as it did work fine without the acpi addition on Ubuntu LTS. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1720438 Title: brightness control broken nvidia Status in gnome-power-manager package in Ubuntu: New Bug description: Ubuntu 17.10 beta 2 Nvidia 310M, 340.x official driver installed with Additional Drivers program The brightness control built into the laptop (Dell Vostro 3300) isn't changing the brightness. Normally I can use Fn + Up/Down arrow keys to change the brightness. The brightness control works fine in Ubuntu 16.04 with the same driver series. I don't know if this is a GNOME 3.26 bug but it's likely as I'm having the exact same problem with Fedora 26 on this laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1720438/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1720438] Re: brightness control broken nvidia
I think this is more of a GNOME3 bug than a bug with the Nvidia driver ** Package changed: nvidia-graphics-drivers-340 (Ubuntu) => gnome- desktop3 (Ubuntu) ** Package changed: gnome-desktop3 (Ubuntu) => gnome-power-manager (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1720438 Title: brightness control broken nvidia Status in gnome-power-manager package in Ubuntu: New Bug description: Ubuntu 17.10 beta 2 Nvidia 310M, 340.x official driver installed with Additional Drivers program The brightness control built into the laptop (Dell Vostro 3300) isn't changing the brightness. Normally I can use Fn + Up/Down arrow keys to change the brightness. The brightness control works fine in Ubuntu 16.04 with the same driver series. I don't know if this is a GNOME 3.26 bug but it's likely as I'm having the exact same problem with Fedora 26 on this laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1720438/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1720438] [NEW] brightness control broken nvidia
Public bug reported: Ubuntu 17.10 beta 2 Nvidia 310M, 340.x official driver installed with Additional Drivers program The brightness control built into the laptop (Dell Vostro 3300) isn't changing the brightness. Normally I can use Fn + Up/Down arrow keys to change the brightness. The brightness control works fine in Ubuntu 16.04 with the same driver series. I don't know if this is a GNOME 3.26 bug but it's likely as I'm having the exact same problem with Fedora 26 on this laptop. ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New ** Tags: brightness control gnome-17.10 laptop nvidia -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1720438 Title: brightness control broken nvidia Status in gnome-power-manager package in Ubuntu: New Bug description: Ubuntu 17.10 beta 2 Nvidia 310M, 340.x official driver installed with Additional Drivers program The brightness control built into the laptop (Dell Vostro 3300) isn't changing the brightness. Normally I can use Fn + Up/Down arrow keys to change the brightness. The brightness control works fine in Ubuntu 16.04 with the same driver series. I don't know if this is a GNOME 3.26 bug but it's likely as I'm having the exact same problem with Fedora 26 on this laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1720438/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 901622] Re: Resume after pm-suspend with read-only ext4 root file system on USB disk (ext4 journal commit I/O error) )
Not sure if this is the same bug but I'm having problems with an ext4 USB drive being recognised in Ubuntu 16.04.3 after waking from suspend -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/901622 Title: Resume after pm-suspend with read-only ext4 root file system on USB disk (ext4 journal commit I/O error) ) Status in pm-utils package in Ubuntu: Confirmed Bug description: After the upgrade to Oneiric resume from pm-suspend no longer works, might be connected to change of kernel from 2.6.38 to 3.0.0... Issue also reported for Arch Linux and kernel 2.6.39 here: https://bbs.archlinux.org/viewtopic.php?pid=1008743 See attached dmesg output for details This is for kernel 3.0.0-14-server x86_64 (but also occured on 3.0.0-13) and a NAS booting from a USB stick. --- ApportVersion: 1.23-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 11.10 Package: pm-utils 1.4.1-8ubuntu1 PackageArchitecture: all ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Tags: oneiric running-unity Uname: Linux 3.0.0-14-generic x86_64 UpgradeStatus: Upgraded to oneiric on 2011-10-17 (51 days ago) UserGroups: adm admin audio cdrom dialout dip fax floppy fuse libvirtd lpadmin netdev plugdev powerdev sambashare scanner tape video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/901622/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1443554] [NEW] bbswitch-dkms 0.7-2ubuntu1: bbswitch kernel module failed to build
Public bug reported: module not working after 4.0 kernel update ProblemType: Package DistroRelease: Ubuntu 15.04 Package: bbswitch-dkms 0.7-2ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.17-0ubuntu2 Architecture: amd64 DKMSKernelVersion: 4.0.0-04-generic Date: Mon Apr 13 18:02:01 2015 InstallationDate: Installed on 2015-04-10 (3 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) PackageVersion: 0.7-2ubuntu1 RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: bbswitch Title: bbswitch-dkms 0.7-2ubuntu1: bbswitch kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bbswitch (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package vivid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bbswitch in Ubuntu. https://bugs.launchpad.net/bugs/1443554 Title: bbswitch-dkms 0.7-2ubuntu1: bbswitch kernel module failed to build Status in bbswitch package in Ubuntu: New Bug description: module not working after 4.0 kernel update ProblemType: Package DistroRelease: Ubuntu 15.04 Package: bbswitch-dkms 0.7-2ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.17-0ubuntu2 Architecture: amd64 DKMSKernelVersion: 4.0.0-04-generic Date: Mon Apr 13 18:02:01 2015 InstallationDate: Installed on 2015-04-10 (3 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) PackageVersion: 0.7-2ubuntu1 RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: bbswitch Title: bbswitch-dkms 0.7-2ubuntu1: bbswitch 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/1443554/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
