[Kernel-packages] [Bug 1937897] Re: GPIO error logs in start and dmesg after update of kernel
Yes I can confirm that the updated HWE kernel 5.11.0-36.40~20.04.1-generic didn't work; same log errors. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937897 Title: GPIO error logs in start and dmesg after update of kernel Status in linux package in Ubuntu: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Released Bug description: [Impact] After upgrade kernel to 5.11.0-25 which introduce some ODM patches from AAEON, user encounters below errors [ 5.852182] gpio gpiochip2: (gpio_aaeon): tried to insert a GPIO chip with zero lines [5.852187] gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to register, -22 [5.852194] gpio-aaeon: probe of gpio-aaeon.0 failed with error -22 [Fix] AAEON provides a patch to check the BFPI version before loading the driver. Which fixes the issue introduced by Hirsute: 45a8bb8699cc UBUNTU: ODM: mfd: Add support for IO functions of AAEON devices Impish: 424945128781 UBUNTU: ODM: mfd: Add support for IO functions of AAEON devices [Test] Verified by AAEON. [Where problems could occur] It adds a check while probing the driver, should have no impact to normal user. = After update from kernel 5.11.0-22 to 5.11.0-25 i see next logs error to gpio: 5.852182] gpio gpiochip2: (gpio_aaeon): tried to insert a GPIO chip with zero lines [5.852187] gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to register, -22 [5.852194] gpio-aaeon: probe of gpio-aaeon.0 failed with error -22 On pc: description: Desktop Computer product: System Product Name (SKU) vendor: ASUS version: System Version serial: System Serial Number width: 64 bits capabilities: smbios-3.3.0 dmi-3.3.0 smp vsyscall32 configuration: boot=normal chassis=desktop family=To be filled by O.E.M. sku=SKU uuid=0ABCA172-BFA8-2AC5-FC37-3C7C3FD88FE4 *-core description: Motherboard product: TUF GAMING B550M-PLUS (WI-FI) vendor: ASUSTeK COMPUTER INC. physical id: 0 version: Rev X.0x serial: 201176738701636 slot: Default string *-firmware description: BIOS vendor: American Megatrends Inc. physical id: 0 version: 2403 date: 06/16/2021 size: 64KiB capacity: 16MiB capabilities: pci apm upgrade shadowing cdboot bootselect socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer acpi usb biosbootspecification uefi *-memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937897] Re: GPIO error logs in start and dmesg after update of kernel
OOps, this this isn't the same kernel!? Ignore my comment then! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937897 Title: GPIO error logs in start and dmesg after update of kernel Status in linux package in Ubuntu: In Progress Status in linux source package in Hirsute: In Progress Status in linux source package in Impish: In Progress Bug description: [Impact] After upgrade kernel to 5.11.0-25, user encounters below errors [ 5.852182] gpio gpiochip2: (gpio_aaeon): tried to insert a GPIO chip with zero lines [5.852187] gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to register, -22 [5.852194] gpio-aaeon: probe of gpio-aaeon.0 failed with error -22 [Fix] AAEON provides a patch to check the BFPI version before loading the driver. [Test] Verified by AAEON. [Where problems could occur] It adds a check while probing the driver, should have no impact to normal user. = After update from kernel 5.11.0-22 to 5.11.0-25 i see next logs error to gpio: 5.852182] gpio gpiochip2: (gpio_aaeon): tried to insert a GPIO chip with zero lines [5.852187] gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to register, -22 [5.852194] gpio-aaeon: probe of gpio-aaeon.0 failed with error -22 On pc: description: Desktop Computer product: System Product Name (SKU) vendor: ASUS version: System Version serial: System Serial Number width: 64 bits capabilities: smbios-3.3.0 dmi-3.3.0 smp vsyscall32 configuration: boot=normal chassis=desktop family=To be filled by O.E.M. sku=SKU uuid=0ABCA172-BFA8-2AC5-FC37-3C7C3FD88FE4 *-core description: Motherboard product: TUF GAMING B550M-PLUS (WI-FI) vendor: ASUSTeK COMPUTER INC. physical id: 0 version: Rev X.0x serial: 201176738701636 slot: Default string *-firmware description: BIOS vendor: American Megatrends Inc. physical id: 0 version: 2403 date: 06/16/2021 size: 64KiB capacity: 16MiB capabilities: pci apm upgrade shadowing cdboot bootselect socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer acpi usb biosbootspecification uefi *-memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937897] Re: GPIO error logs in start and dmesg after update of kernel
No it unfortunately did not work. With the new HWE kernel Ubuntu 5.11.0-27.29~20.04.1-generic (same as above?). The failing lines are at two places in the log. Boot is very quick though but it is annoying seeing the red lines. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937897 Title: GPIO error logs in start and dmesg after update of kernel Status in linux package in Ubuntu: In Progress Status in linux source package in Hirsute: In Progress Status in linux source package in Impish: In Progress Bug description: [Impact] After upgrade kernel to 5.11.0-25, user encounters below errors [ 5.852182] gpio gpiochip2: (gpio_aaeon): tried to insert a GPIO chip with zero lines [5.852187] gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to register, -22 [5.852194] gpio-aaeon: probe of gpio-aaeon.0 failed with error -22 [Fix] AAEON provides a patch to check the BFPI version before loading the driver. [Test] Verified by AAEON. [Where problems could occur] It adds a check while probing the driver, should have no impact to normal user. = After update from kernel 5.11.0-22 to 5.11.0-25 i see next logs error to gpio: 5.852182] gpio gpiochip2: (gpio_aaeon): tried to insert a GPIO chip with zero lines [5.852187] gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to register, -22 [5.852194] gpio-aaeon: probe of gpio-aaeon.0 failed with error -22 On pc: description: Desktop Computer product: System Product Name (SKU) vendor: ASUS version: System Version serial: System Serial Number width: 64 bits capabilities: smbios-3.3.0 dmi-3.3.0 smp vsyscall32 configuration: boot=normal chassis=desktop family=To be filled by O.E.M. sku=SKU uuid=0ABCA172-BFA8-2AC5-FC37-3C7C3FD88FE4 *-core description: Motherboard product: TUF GAMING B550M-PLUS (WI-FI) vendor: ASUSTeK COMPUTER INC. physical id: 0 version: Rev X.0x serial: 201176738701636 slot: Default string *-firmware description: BIOS vendor: American Megatrends Inc. physical id: 0 version: 2403 date: 06/16/2021 size: 64KiB capacity: 16MiB capabilities: pci apm upgrade shadowing cdboot bootselect socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer acpi usb biosbootspecification uefi *-memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937897/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1728446] Re: Middle clicking isn't working properly Logitech M705
apport information ** Attachment added: "lsusb" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728446/+attachment/4999652/+files/lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1728446 Title: Middle clicking isn't working properly Logitech M705 Status in linux package in Ubuntu: New Bug description: I'm using Ubuntu 16.04, (stock install 16.04.3, not HWE LTS) with a newly bought mouse, Logitech M705 (which are using Logitech Unifying Receiver). When I connected the mouse everything was working as expected, except that the middle clicking wasn't working. The mouse has the following map: 1Left 2Middle (push roller down) 3Right 4Roller Forward 5Roller Back 6Roller tilt left 7Roller tilt right 8Side button, forward 9Side Button, rearward 10 Extra button (app switching) When I tried the mouse with 'xev | grep button', the button Left was nr 1, Right nr 3, Roller Forward nr 4, Roller Back nr 5, Roller tilt left nr 6, Roller tilt right nr 7, Side button, forward nr 8, Side Button, rearward nr 9 and Extra button was nr 10. But Middle button was the same as Roller tilt left namely nr 6. It should have been number 2 not 6. Thus the middle click button wasn't properly detected and not working as expected. I can remap the mouse button nr 6 to nr 2 with xinput and get middle clicking but then the left tilt functionality disappear, this button (nr 6) also become a middle click button, nr 2. What is it that makes that two different buttons get the same number? xinput list shows: xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech M705 id=8[slave pointer (2)] ⎜ ↳ Logitech K520 id=9[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Power Buttonid=7[slave keyboard (3)] ↳ Eee PC WMI hotkeys id=10 [slave keyboard (3)] And xinput list 8 Logitech M705 id=8[slave pointer (2)] Reporting 7 classes: Class originated from: 8. Type: XIButtonClass Buttons supported: 24 Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" "Button Side" "Button Extra" "Button Forward" "Button Back" "Button Task" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" Button state: Class originated from: 8. Type: XIValuatorClass Detail for Valuator 0: Label: Rel X Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 8. Type: XIValuatorClass Detail for Valuator 1: Label: Rel Y Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 8. Type: XIValuatorClass Detail for Valuator 2: Label: Rel Horiz Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 8. Type: XIValuatorClass Detail for Valuator 3: Label: Rel Vert Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 8. Type: XIScrollClass Scroll info for Valuator 2 type: 2 (horizontal) increment: 1.00 flags: 0x0 Class originated from: 8. Type: XIScrollClass Scroll info for Valuator 3 type: 1 (vertical) increment: -1.00 flags: 0x2 ( preferred ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728446/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1728446] Re: Middle clicking isn't working properly Logitech M705
apport information ** Attachment added: "Dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728446/+attachment/4999650/+files/dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1728446 Title: Middle clicking isn't working properly Logitech M705 Status in linux package in Ubuntu: New Bug description: I'm using Ubuntu 16.04, (stock install 16.04.3, not HWE LTS) with a newly bought mouse, Logitech M705 (which are using Logitech Unifying Receiver). When I connected the mouse everything was working as expected, except that the middle clicking wasn't working. The mouse has the following map: 1Left 2Middle (push roller down) 3Right 4Roller Forward 5Roller Back 6Roller tilt left 7Roller tilt right 8Side button, forward 9Side Button, rearward 10 Extra button (app switching) When I tried the mouse with 'xev | grep button', the button Left was nr 1, Right nr 3, Roller Forward nr 4, Roller Back nr 5, Roller tilt left nr 6, Roller tilt right nr 7, Side button, forward nr 8, Side Button, rearward nr 9 and Extra button was nr 10. But Middle button was the same as Roller tilt left namely nr 6. It should have been number 2 not 6. Thus the middle click button wasn't properly detected and not working as expected. I can remap the mouse button nr 6 to nr 2 with xinput and get middle clicking but then the left tilt functionality disappear, this button (nr 6) also become a middle click button, nr 2. What is it that makes that two different buttons get the same number? xinput list shows: xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech M705 id=8[slave pointer (2)] ⎜ ↳ Logitech K520 id=9[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Power Buttonid=7[slave keyboard (3)] ↳ Eee PC WMI hotkeys id=10 [slave keyboard (3)] And xinput list 8 Logitech M705 id=8[slave pointer (2)] Reporting 7 classes: Class originated from: 8. Type: XIButtonClass Buttons supported: 24 Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" "Button Side" "Button Extra" "Button Forward" "Button Back" "Button Task" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" Button state: Class originated from: 8. Type: XIValuatorClass Detail for Valuator 0: Label: Rel X Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 8. Type: XIValuatorClass Detail for Valuator 1: Label: Rel Y Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 8. Type: XIValuatorClass Detail for Valuator 2: Label: Rel Horiz Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 8. Type: XIValuatorClass Detail for Valuator 3: Label: Rel Vert Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 8. Type: XIScrollClass Scroll info for Valuator 2 type: 2 (horizontal) increment: 1.00 flags: 0x0 Class originated from: 8. Type: XIScrollClass Scroll info for Valuator 3 type: 1 (vertical) increment: -1.00 flags: 0x2 ( preferred ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728446/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1728446] Re: Middle clicking isn't working properly Logitech M705
Using Ubuntu 4.4.0-97.120-generic 4.4.87 Latest Nvidia driver 384.90 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1728446 Title: Middle clicking isn't working properly Logitech M705 Status in linux package in Ubuntu: New Bug description: I'm using Ubuntu 16.04, (stock install 16.04.3, not HWE LTS) with a newly bought mouse, Logitech M705 (which are using Logitech Unifying Receiver). When I connected the mouse everything was working as expected, except that the middle clicking wasn't working. The mouse has the following map: 1Left 2Middle (push roller down) 3Right 4Roller Forward 5Roller Back 6Roller tilt left 7Roller tilt right 8Side button, forward 9Side Button, rearward 10 Extra button (app switching) When I tried the mouse with 'xev | grep button', the button Left was nr 1, Right nr 3, Roller Forward nr 4, Roller Back nr 5, Roller tilt left nr 6, Roller tilt right nr 7, Side button, forward nr 8, Side Button, rearward nr 9 and Extra button was nr 10. But Middle button was the same as Roller tilt left namely nr 6. It should have been number 2 not 6. Thus the middle click button wasn't properly detected and not working as expected. I can remap the mouse button nr 6 to nr 2 with xinput and get middle clicking but then the left tilt functionality disappear, this button (nr 6) also become a middle click button, nr 2. What is it that makes that two different buttons get the same number? xinput list shows: xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech M705 id=8[slave pointer (2)] ⎜ ↳ Logitech K520 id=9[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Power Buttonid=7[slave keyboard (3)] ↳ Eee PC WMI hotkeys id=10 [slave keyboard (3)] And xinput list 8 Logitech M705 id=8[slave pointer (2)] Reporting 7 classes: Class originated from: 8. Type: XIButtonClass Buttons supported: 24 Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" "Button Side" "Button Extra" "Button Forward" "Button Back" "Button Task" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" Button state: Class originated from: 8. Type: XIValuatorClass Detail for Valuator 0: Label: Rel X Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 8. Type: XIValuatorClass Detail for Valuator 1: Label: Rel Y Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 8. Type: XIValuatorClass Detail for Valuator 2: Label: Rel Horiz Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 8. Type: XIValuatorClass Detail for Valuator 3: Label: Rel Vert Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 8. Type: XIScrollClass Scroll info for Valuator 2 type: 2 (horizontal) increment: 1.00 flags: 0x0 Class originated from: 8. Type: XIScrollClass Scroll info for Valuator 3 type: 1 (vertical) increment: -1.00 flags: 0x2 ( preferred ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728446/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1728446] Re: Middle clicking isn't working properly Logitech M705
apport information ** Attachment added: "lspci" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728446/+attachment/4999651/+files/lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1728446 Title: Middle clicking isn't working properly Logitech M705 Status in linux package in Ubuntu: New Bug description: I'm using Ubuntu 16.04, (stock install 16.04.3, not HWE LTS) with a newly bought mouse, Logitech M705 (which are using Logitech Unifying Receiver). When I connected the mouse everything was working as expected, except that the middle clicking wasn't working. The mouse has the following map: 1Left 2Middle (push roller down) 3Right 4Roller Forward 5Roller Back 6Roller tilt left 7Roller tilt right 8Side button, forward 9Side Button, rearward 10 Extra button (app switching) When I tried the mouse with 'xev | grep button', the button Left was nr 1, Right nr 3, Roller Forward nr 4, Roller Back nr 5, Roller tilt left nr 6, Roller tilt right nr 7, Side button, forward nr 8, Side Button, rearward nr 9 and Extra button was nr 10. But Middle button was the same as Roller tilt left namely nr 6. It should have been number 2 not 6. Thus the middle click button wasn't properly detected and not working as expected. I can remap the mouse button nr 6 to nr 2 with xinput and get middle clicking but then the left tilt functionality disappear, this button (nr 6) also become a middle click button, nr 2. What is it that makes that two different buttons get the same number? xinput list shows: xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech M705 id=8[slave pointer (2)] ⎜ ↳ Logitech K520 id=9[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Power Buttonid=7[slave keyboard (3)] ↳ Eee PC WMI hotkeys id=10 [slave keyboard (3)] And xinput list 8 Logitech M705 id=8[slave pointer (2)] Reporting 7 classes: Class originated from: 8. Type: XIButtonClass Buttons supported: 24 Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" "Button Side" "Button Extra" "Button Forward" "Button Back" "Button Task" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" Button state: Class originated from: 8. Type: XIValuatorClass Detail for Valuator 0: Label: Rel X Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 8. Type: XIValuatorClass Detail for Valuator 1: Label: Rel Y Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 8. Type: XIValuatorClass Detail for Valuator 2: Label: Rel Horiz Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 8. Type: XIValuatorClass Detail for Valuator 3: Label: Rel Vert Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 8. Type: XIScrollClass Scroll info for Valuator 2 type: 2 (horizontal) increment: 1.00 flags: 0x0 Class originated from: 8. Type: XIScrollClass Scroll info for Valuator 3 type: 1 (vertical) increment: -1.00 flags: 0x2 ( preferred ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728446/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1728446] [NEW] Middle clicking isn't working properly Logitech M705
Public bug reported: I'm using Ubuntu 16.04, (stock install 16.04.3, not HWE LTS) with a newly bought mouse, Logitech M705 (which are using Logitech Unifying Receiver). When I connected the mouse everything was working as expected, except that the middle clicking wasn't working. The mouse has the following map: 1 Left 2 Middle (push roller down) 3 Right 4 Roller Forward 5 Roller Back 6 Roller tilt left 7 Roller tilt right 8 Side button, forward 9 Side Button, rearward 10 Extra button (app switching) When I tried the mouse with 'xev | grep button', the button Left was nr 1, Right nr 3, Roller Forward nr 4, Roller Back nr 5, Roller tilt left nr 6, Roller tilt right nr 7, Side button, forward nr 8, Side Button, rearward nr 9 and Extra button was nr 10. But Middle button was the same as Roller tilt left namely nr 6. It should have been number 2 not 6. Thus the middle click button wasn't properly detected and not working as expected. I can remap the mouse button nr 6 to nr 2 with xinput and get middle clicking but then the left tilt functionality disappear, this button (nr 6) also become a middle click button, nr 2. What is it that makes that two different buttons get the same number? xinput list shows: xinput list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ Logitech M705 id=8[slave pointer (2)] ⎜ ↳ Logitech K520 id=9[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Power Button id=7[slave keyboard (3)] ↳ Eee PC WMI hotkeysid=10 [slave keyboard (3)] And xinput list 8 Logitech M705 id=8[slave pointer (2)] Reporting 7 classes: Class originated from: 8. Type: XIButtonClass Buttons supported: 24 Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" "Button Side" "Button Extra" "Button Forward" "Button Back" "Button Task" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" Button state: Class originated from: 8. Type: XIValuatorClass Detail for Valuator 0: Label: Rel X Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 8. Type: XIValuatorClass Detail for Valuator 1: Label: Rel Y Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 8. Type: XIValuatorClass Detail for Valuator 2: Label: Rel Horiz Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 8. Type: XIValuatorClass Detail for Valuator 3: Label: Rel Vert Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 8. Type: XIScrollClass Scroll info for Valuator 2 type: 2 (horizontal) increment: 1.00 flags: 0x0 Class originated from: 8. Type: XIScrollClass Scroll info for Valuator 3 type: 1 (vertical) increment: -1.00 flags: 0x2 ( preferred ) ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1728446 Title: Middle clicking isn't working properly Logitech M705 Status in linux package in Ubuntu: New Bug description: I'm using Ubuntu 16.04, (stock install 16.04.3, not HWE LTS) with a newly bought mouse, Logitech M705 (which are using Logitech Unifying Receiver). When I connected the mouse everything was working as expected, except that the middle clicking wasn't working. The mouse has the following map: 1Left 2Middle (push roller down) 3Right 4Roller Forward 5Roller Back 6Roller tilt left 7Roller tilt
[Kernel-packages] [Bug 1581088] Re: Middle mouse (wheel-click) button stopped working after upgrade to 16.04
More testing shows that the problem isn't resolved. Two buttons on my mouse have the same number, number 6 (middle click and roller tilt left). But number 2 which should be the middle button isn't there, I can remap button 6 to button 2 for middle click to work but then the 'real' button 6 disappears (roller tilt left) and I've only roller tilt right on button 7. Ubuntu can't detect the button 2. What to do? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1581088 Title: Middle mouse (wheel-click) button stopped working after upgrade to 16.04 Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to 16.04 clicking the middle mouse button (scroll wheel) on my Logitech M185 stopped working. xev does not even show the event for clicking the wheel, while it shows other button clicks and scroll wheel up/down events. xinput list shows the USB receiver 2 times: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=9[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=10 [slave pointer (2)] ⎜ ↳ HID 046a:0023 id=13 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=16 [slave pointer (2)] ⎜ ↳ TPPS/2 IBM TrackPoint id=17 [slave pointer (2)] Listing the capabilities looks like this: $ xinput list 9 Logitech USB Receiver id=9[slave pointer (2)] Reporting 7 classes: Class originated from: 9. Type: XIButtonClass Buttons supported: 24 Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" "Button Side" "Button Extra" "Button Forward" "Button Back" "Button Task" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" Button state: Class originated from: 9. Type: XIValuatorClass Detail for Valuator 0: Label: Rel X Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 1: Label: Rel Y Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 2: Label: Rel Horiz Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 3: Label: Rel Vert Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIScrollClass Scroll info for Valuator 2 type: 2 (horizontal) increment: 1.00 flags: 0x0 Class originated from: 9. Type: XIScrollClass Scroll info for Valuator 3 type: 1 (vertical) increment: -1.00 flags: 0x2 ( preferred ) $ xinput list 10 Logitech USB Receiver id=10 [slave pointer (2)] Reporting 6 classes: Class originated from: 10. Type: XIButtonClass Buttons supported: 7 Button labels: "Button 0" "Button Unknown" "Button Unknown" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" Button state: Class originated from: 10. Type: XIKeyClass Keycodes supported: 248 Class originated from: 10. Type: XIValuatorClass Detail for Valuator 0: Label: Rel X Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 10. Type: XIValuatorClass Detail for Valuator 1: Label: Rel Y Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 10. Type: XIValuatorClass Detail for Valuator 2: Label: Rel Horiz Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 10. Type: XIScrollClass Scroll info for Valuator 2 type: 2 (horizontal) increment: 1.00 flags: 0x0 Does anyone have an idea how I can attempt to further debug that issue? Or maybe even a solution? Should I consider this issue a bug? Can I provide more info? --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: toby 11625 F pulseaudio /dev/snd/controlC0: toby 11625 F pulseaudio /dev/snd/pcmC1D0p: toby 11625 F...m pulseaudio
[Kernel-packages] [Bug 1581088] Re: Middle mouse (wheel-click) button stopped working after upgrade to 16.04
Nevermind it worked if I remapped the mouse with xinput. I discovered that the middle button actually was recognized, but it wasn't showing as button 2 as expected but 6. 1. The command "xev | grep button", gave me the button 6 if I clicked in the xev window with the middle button. Then I had to remap the mouse buttons from 6 to 2 (2 is the middle button): 2. The command "xinput get-button-map 8" was giving me my buttons "1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24" Then I remapped them: 3. "xinput set-button-map 8 1 2 3 4 5 2 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24", the sequence remapped my sixth button to number 2, the middle click was after that working. To get it loaded each time I start Unity I autostarted that last command at login. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1581088 Title: Middle mouse (wheel-click) button stopped working after upgrade to 16.04 Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to 16.04 clicking the middle mouse button (scroll wheel) on my Logitech M185 stopped working. xev does not even show the event for clicking the wheel, while it shows other button clicks and scroll wheel up/down events. xinput list shows the USB receiver 2 times: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=9[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=10 [slave pointer (2)] ⎜ ↳ HID 046a:0023 id=13 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=16 [slave pointer (2)] ⎜ ↳ TPPS/2 IBM TrackPoint id=17 [slave pointer (2)] Listing the capabilities looks like this: $ xinput list 9 Logitech USB Receiver id=9[slave pointer (2)] Reporting 7 classes: Class originated from: 9. Type: XIButtonClass Buttons supported: 24 Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" "Button Side" "Button Extra" "Button Forward" "Button Back" "Button Task" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" Button state: Class originated from: 9. Type: XIValuatorClass Detail for Valuator 0: Label: Rel X Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 1: Label: Rel Y Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 2: Label: Rel Horiz Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 3: Label: Rel Vert Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIScrollClass Scroll info for Valuator 2 type: 2 (horizontal) increment: 1.00 flags: 0x0 Class originated from: 9. Type: XIScrollClass Scroll info for Valuator 3 type: 1 (vertical) increment: -1.00 flags: 0x2 ( preferred ) $ xinput list 10 Logitech USB Receiver id=10 [slave pointer (2)] Reporting 6 classes: Class originated from: 10. Type: XIButtonClass Buttons supported: 7 Button labels: "Button 0" "Button Unknown" "Button Unknown" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" Button state: Class originated from: 10. Type: XIKeyClass Keycodes supported: 248 Class originated from: 10. Type: XIValuatorClass Detail for Valuator 0: Label: Rel X Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 10. Type: XIValuatorClass Detail for Valuator 1: Label: Rel Y Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 10. Type: XIValuatorClass Detail for Valuator 2: Label: Rel Horiz Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 10. Type: XIScrollClass Scroll info for Valuator 2 type: 2 (horizontal) increment: 1.00 flags: 0x0 Does anyone have an idea how I can attempt to further debug that issue? Or maybe
[Kernel-packages] [Bug 1581088] Re: Middle mouse (wheel-click) button stopped working after upgrade to 16.04
As info06 clearly states this isn't a hardware issue, because of my newly acquired mouse (yesterday). Have also tried the LTS HWE xorg and kernel (4.10) but to no effect. Now I've downgraded again to the 4.4 stable kernel. But as the bugreporter in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704430 says, may the mainline kernel 4.13.0-041300rc1-generic fix the problem. I haven't time to test this but may it be possible that someone else could test this? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1581088 Title: Middle mouse (wheel-click) button stopped working after upgrade to 16.04 Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to 16.04 clicking the middle mouse button (scroll wheel) on my Logitech M185 stopped working. xev does not even show the event for clicking the wheel, while it shows other button clicks and scroll wheel up/down events. xinput list shows the USB receiver 2 times: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=9[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=10 [slave pointer (2)] ⎜ ↳ HID 046a:0023 id=13 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=16 [slave pointer (2)] ⎜ ↳ TPPS/2 IBM TrackPoint id=17 [slave pointer (2)] Listing the capabilities looks like this: $ xinput list 9 Logitech USB Receiver id=9[slave pointer (2)] Reporting 7 classes: Class originated from: 9. Type: XIButtonClass Buttons supported: 24 Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" "Button Side" "Button Extra" "Button Forward" "Button Back" "Button Task" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" Button state: Class originated from: 9. Type: XIValuatorClass Detail for Valuator 0: Label: Rel X Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 1: Label: Rel Y Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 2: Label: Rel Horiz Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 3: Label: Rel Vert Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIScrollClass Scroll info for Valuator 2 type: 2 (horizontal) increment: 1.00 flags: 0x0 Class originated from: 9. Type: XIScrollClass Scroll info for Valuator 3 type: 1 (vertical) increment: -1.00 flags: 0x2 ( preferred ) $ xinput list 10 Logitech USB Receiver id=10 [slave pointer (2)] Reporting 6 classes: Class originated from: 10. Type: XIButtonClass Buttons supported: 7 Button labels: "Button 0" "Button Unknown" "Button Unknown" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" Button state: Class originated from: 10. Type: XIKeyClass Keycodes supported: 248 Class originated from: 10. Type: XIValuatorClass Detail for Valuator 0: Label: Rel X Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 10. Type: XIValuatorClass Detail for Valuator 1: Label: Rel Y Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 10. Type: XIValuatorClass Detail for Valuator 2: Label: Rel Horiz Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 10. Type: XIScrollClass Scroll info for Valuator 2 type: 2 (horizontal) increment: 1.00 flags: 0x0 Does anyone have an idea how I can attempt to further debug that issue? Or maybe even a solution? Should I consider this issue a bug? Can I provide more info? --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: toby 11625 F pulseaudio /dev/snd/controlC0: toby 11625 F pulseaudio
[Kernel-packages] [Bug 1581088] Re: Middle mouse (wheel-click) button stopped working after upgrade to 16.04
Just bought a Logitech M705 in a combo with a K520 keyboard. In Ubuntu 16.04 the middle button is not activated and not working. I've a stock Ubuntu 16.04 with all recent updates. I'm using Unity. Output: xinput --list-props 8 Device 'Logitech M705': Device Enabled (153): 1 Coordinate Transformation Matrix (155): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 Device Accel Profile (283): 0 Device Accel Constant Deceleration (284): 1.00 Device Accel Adaptive Deceleration (285): 1.00 Device Accel Velocity Scaling (286):10.00 Device Product ID (272):1133, 4123 Device Node (273): "/dev/input/event3" Evdev Axis Inversion (287): 0, 0 Evdev Axes Swap (289): 0 Axis Labels (290): "Rel X" (163), "Rel Y" (164), "Rel Horiz Wheel" (281), "Rel Vert Wheel" (282) Button Labels (291):"Button Left" (156), "Button Middle" (157), "Button Right" (158), "Button Wheel Up" (159), "Button Wheel Down" (160), "Button Horiz Wheel Left" (161), "Button Horiz Wheel Right" (162), "Button Side" (276), "Button Extra" (277), "Button Forward" (278), "Button Back" (279), "Button Task" (280), "Button Unknown" (275), "Button Unknown" (275), "Button Unknown" (275), "Button Unknown" (275), "Button Unknown" (275), "Button Unknown" (275), "Button Unknown" (275), "Button Unknown" (275), "Button Unknown" (275), "Button Unknown" (275), "Button Unknown" (275), "Button Unknown" (275) Evdev Scrolling Distance (292): 1, 1, 1 Evdev Middle Button Emulation (293):0 Evdev Middle Button Timeout (294): 50 Evdev Third Button Emulation (295): 0 Evdev Third Button Emulation Timeout (296): 1000 Evdev Third Button Emulation Button (297): 3 Evdev Third Button Emulation Threshold (298): 20 Evdev Wheel Emulation (299):0 Evdev Wheel Emulation Axes (300): 0, 0, 4, 5 Evdev Wheel Emulation Inertia (301):10 Evdev Wheel Emulation Timeout (302):200 Evdev Wheel Emulation Button (303): 4 Evdev Drag Lock Buttons (304): 0 Even if I enable "Evdev Middle Button Emulation", "Evdev Third Button Emulation" and "Evdev Wheel Emulation" it will not work. I hope that some will come with a solution. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1581088 Title: Middle mouse (wheel-click) button stopped working after upgrade to 16.04 Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to 16.04 clicking the middle mouse button (scroll wheel) on my Logitech M185 stopped working. xev does not even show the event for clicking the wheel, while it shows other button clicks and scroll wheel up/down events. xinput list shows the USB receiver 2 times: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=9[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=10 [slave pointer (2)] ⎜ ↳ HID 046a:0023 id=13 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=16 [slave pointer (2)] ⎜ ↳ TPPS/2 IBM TrackPoint id=17 [slave pointer (2)] Listing the capabilities looks like this: $ xinput list 9 Logitech USB Receiver id=9[slave pointer (2)] Reporting 7 classes: Class originated from: 9. Type: XIButtonClass Buttons supported: 24 Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" "Button Side" "Button Extra" "Button Forward" "Button Back" "Button Task" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" Button state: Class originated from: 9. Type: XIValuatorClass Detail for Valuator 0: Label: Rel X Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 1: Label: Rel Y Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 2: Label: Rel Horiz Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative Class originated from: 9. Type: XIValuatorClass Detail for Valuator 3: Label: Rel Vert Wheel Range:
[Kernel-packages] [Bug 1478873] Re: Odd behaviour in some applications
Also Wine applications behave odd which after the upgrade to 3.13.0-59 don't run. When I reboot in 3.13.0-58 kernel they work again. I'm now forced to boot into the earlier kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1478873 Title: Odd behaviour in some applications Status in linux package in Ubuntu: Confirmed Bug description: Earlier today I installed linux-headers-3.13.0-59 linux-headers-3.13.0-59-generic linux-image-3.13.0-59-generic linux-image-extra-3.13.0-59-generic and after that some applications, most notably steam, started to behave strange, e.g. in steam installed software was invisible and the application install dialog stated Disk Space Available: 0 Counter checks by booting some older kernels (48 to 58) fixed that behaviour. A very quick cross check with another system seem to prove this observation. I do an educated guess: my steam is sitting on /archive/steam so I can share it over network and local users. /archive is a soft link to /home/archive coz I often move this one around a lot. I have the odd feeling kernel -59 is having issues with soft links and/or steam is handling soft links in a weird way which broke with -59. All other software affected is somehow connected to soft links, be it a small readlink from bash or postgresql. Sorry for being a bit vague right now, more details after I return from work and have time to experiment with avoiding soft links while using my affected applications. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-59-generic 3.13.0-59.98 ProcVersionSignature: Ubuntu 3.13.0-58.97-generic 3.13.11-ckt22 Uname: Linux 3.13.0-58-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: brandtc2790 F pulseaudio /dev/snd/pcmC0D0p: brandtc2790 F...m pulseaudio CRDA: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 'iw' CurrentDesktop: LXDE CurrentDmesg: [ 35.700956] nvidia :01:00.0: irq 50 for MSI/MSI-X [ 35.793778] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: acl [ 36.993771] init: plymouth-upstart-bridge main process ended, respawning [ 636.471258] perf samples too long (2501 2500), lowering kernel.perf_event_max_sample_rate to 5 Date: Tue Jul 28 11:40:00 2015 HibernationDevice: RESUME=/dev/mapper/vgsys-lvswap MachineType: Gigabyte Technology Co., Ltd. 965G-DS3 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-58-generic root=UUID=7f7fd8ba-d814-4ead-9ea4-53089785459c ro nomodeset video=uvesafb:mode_option=1920x1200-24,mtrr=3,scroll=ywrap libata.force=1.5 zswap.enabled=1 zswap.max_pool_percent=25 nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-3.13.0-58-generic N/A linux-backports-modules-3.13.0-58-generic N/A linux-firmware 1.127.14 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2008 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F10M dmi.board.name: 965G-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF10M:bd09/18/2008:svnGigabyteTechnologyCo.,Ltd.:pn965G-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn965G-DS3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: 965G-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1478873/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
