[Touch-packages] [Bug 1676912] Re: Kernel 4.9+ regression: Suspend - Freezing of tasks failed
** Summary changed: - Kernel 4.10+ regression: Suspend - Freezing of tasks failed + Kernel 4.9+ regression: Suspend - Freezing of tasks failed ** Description changed: Recently I replaced Ubuntu 16.04 on my Lenovo Yoga 3 11 with Ubuntu Gnome 17.04 and since then sometimes my Laptop won't suspend when I close the lid. The power led does not blink like it is supposed to do and when I open the Laptop the lockscreen appears but freezes after a short time, followed by a blackscreen until eventually it reappears and allows me to unlock it. After that certain application can not be started anymore and would freeze if they were running before. These include Chrome, Gedit and Gnome System Monitor for example. Also my Laptop will not connect to my WLAN until I restart it. In syslog I found the line: "Freezing of tasks failed after 20.005 seconds (18 tasks refusing to freeze, wq_busy=0):" According to syslog network-nanaeger whoopsie cups-browsed wpa-supplicant geoclue packagekitd several evolution-related processes goa-daemon gnome-software geary dropbox deja-dup-monitor are responsible. I tried disabling some of them, but it did not solve the problem. Update: I tested different Kernel versions in the last days. So far there were no issues with suspend/resume using Kernel 4.8 and 4.9. The problem is present in 4.10 and 4.11. + Update 2: I just encountered this issue with Kernel 4.9. + ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-19 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 28 16:27:34 2017 InstallationDate: Installed on 2017-03-24 (3 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) MachineType: LENOVO 80J8 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic.efi.signed root=UUID=8c63f102-527f-412a-bafe-7b9075ea6b56 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2015 dmi.bios.vendor: LENOVO dmi.bios.version: B8CN31WW(V2.09) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Paganini dmi.board.vendor: LENOVO dmi.board.version: 31900058 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 3 11 dmi.modalias: dmi:bvnLENOVO:bvrB8CN31WW(V2.09):bd07/15/2015:svnLENOVO:pn80J8:pvrLenovoYoga311:rvnLENOVO:rnPaganini:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga311: dmi.product.name: 80J8 dmi.product.version: Lenovo Yoga 3 11 dmi.sys.vendor: LENOVO -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1676912 Title: Kernel 4.9+ regression: Suspend - Freezing of tasks failed Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Recently I replaced Ubuntu 16.04 on my Lenovo Yoga 3 11 with Ubuntu Gnome 17.04 and since then sometimes my Laptop won't suspend when I close the lid. The power led does not blink like it is supposed to do and when I open the Laptop the lockscreen appears but freezes after a short time, followed by a blackscreen until eventually it reappears and allows me to unlock it. After that certain application can not be started anymore and would freeze if they were running before. These include Chrome, Gedit and Gnome System Monitor for example. Also my Laptop will not connect to my WLAN until I restart it. In syslog I found the line: "Freezing of tasks failed after 20.005 seconds (18 tasks refusing to freeze, wq_busy=0):" According to syslog network-nanaeger whoopsie cups-browsed wpa-supplicant geoclue packagekitd several evolution-related processes goa-daemon gnome-software geary dropbox deja-dup-monitor are responsible. I tried disabling some of them, but it did not solve the problem. Update: I tested different Kernel versions in the last days. So far there were no issues with suspend/resume using Kernel 4.8 and 4.9. The problem is present in 4.10 and 4.11. Update 2: I just encountered this issue with Kernel 4.9. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-19 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 28 16:27:34 2017 InstallationDate: Installed on 2017-03-24 (3 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) MachineType: LENOVO 80J8
[Touch-packages] [Bug 1676912] Re: Suspend - Freezing of tasks failed
** Description changed: Recently I replaced Ubuntu 16.04 on my Lenovo Yoga 3 11 with Ubuntu Gnome 17.04 and since then sometimes my Laptop won't suspend when I close the lid. The power led does not blink like it is supposed to do and when I open the Laptop the lockscreen appears but freezes after a short time, followed by a blackscreen until eventually it reappears and allows me to unlock it. After that certain application can not be started anymore and would freeze if they were running before. These include Chrome, Gedit and Gnome System Monitor for example. Also my Laptop will not connect to my WLAN until I restart it. In syslog I found the line: "Freezing of tasks failed after 20.005 seconds (18 tasks refusing to freeze, wq_busy=0):" According to syslog network-nanaeger whoopsie cups-browsed wpa-supplicant geoclue packagekitd several evolution-related processes goa-daemon gnome-software geary dropbox deja-dup-monitor are responsible. I tried disabling some of them, but it did not solve the problem. + Update: I tested different Kernel versions in the last days. So far + there were no issues with suspend/resume using Kernel 4.8 and 4.9. The + problem is present in 4.10 and 4.11. + ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-19 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 28 16:27:34 2017 InstallationDate: Installed on 2017-03-24 (3 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) MachineType: LENOVO 80J8 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=de_DE.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=de_DE.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic.efi.signed root=UUID=8c63f102-527f-412a-bafe-7b9075ea6b56 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2015 dmi.bios.vendor: LENOVO dmi.bios.version: B8CN31WW(V2.09) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Paganini dmi.board.vendor: LENOVO dmi.board.version: 31900058 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 3 11 dmi.modalias: dmi:bvnLENOVO:bvrB8CN31WW(V2.09):bd07/15/2015:svnLENOVO:pn80J8:pvrLenovoYoga311:rvnLENOVO:rnPaganini:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga311: dmi.product.name: 80J8 dmi.product.version: Lenovo Yoga 3 11 dmi.sys.vendor: LENOVO ** Summary changed: - Suspend - Freezing of tasks failed + Kernel 4.10+ regression: Suspend - Freezing of tasks failed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1676912 Title: Kernel 4.10+ regression: Suspend - Freezing of tasks failed Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Recently I replaced Ubuntu 16.04 on my Lenovo Yoga 3 11 with Ubuntu Gnome 17.04 and since then sometimes my Laptop won't suspend when I close the lid. The power led does not blink like it is supposed to do and when I open the Laptop the lockscreen appears but freezes after a short time, followed by a blackscreen until eventually it reappears and allows me to unlock it. After that certain application can not be started anymore and would freeze if they were running before. These include Chrome, Gedit and Gnome System Monitor for example. Also my Laptop will not connect to my WLAN until I restart it. In syslog I found the line: "Freezing of tasks failed after 20.005 seconds (18 tasks refusing to freeze, wq_busy=0):" According to syslog network-nanaeger whoopsie cups-browsed wpa-supplicant geoclue packagekitd several evolution-related processes goa-daemon gnome-software geary dropbox deja-dup-monitor are responsible. I tried disabling some of them, but it did not solve the problem. Update: I tested different Kernel versions in the last days. So far there were no issues with suspend/resume using Kernel 4.8 and 4.9. The problem is present in 4.10 and 4.11. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-19 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 28 16:27:34 2017 InstallationDate: Installed on 2017-03-24 (3 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) MachineType: LENOVO 80J8 ProcEnviron: TERM=xterm-256color
[Touch-packages] [Bug 1676918] Re: Kernel 4.10+ regression: blackscreen when trying to resume from suspend
** Summary changed: - blackscreen when trying to resume from suspend + Kernel 4.10+ regression: blackscreen when trying to resume from suspend ** Description changed: When trying to resume after suspending my Lenovo Yoga 3 11, sometimes the screen remains black. The power LED switches from blinking to continuous light like it should but nothing else happens. The system does not react to anything. I tried to find something in the logs, but at least kern.log syslog and xorg.log never have any entries from this event. This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and Wayland. I'm currently testing Kernel 4.8 from the mainline ppa because of this other suspend resume bug, that appeared only with 17.04: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1676912 + + Update: So far I did not encounter any issues with suspend/resume with + Kernel 4.8 and 4.9. This seems to be a regression in 4.10. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-03-24 (4 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) Package: systemd 232-19 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Tags: zesty wayland-session Uname: Linux 4.8.17-040817-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1676918 Title: Kernel 4.10+ regression: blackscreen when trying to resume from suspend Status in gnome-power-manager package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: When trying to resume after suspending my Lenovo Yoga 3 11, sometimes the screen remains black. The power LED switches from blinking to continuous light like it should but nothing else happens. The system does not react to anything. I tried to find something in the logs, but at least kern.log syslog and xorg.log never have any entries from this event. This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and Wayland. I'm currently testing Kernel 4.8 from the mainline ppa because of this other suspend resume bug, that appeared only with 17.04: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1676912 Update: So far I did not encounter any issues with suspend/resume with Kernel 4.8 and 4.9. This seems to be a regression in 4.10. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-03-24 (4 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) Package: systemd 232-19 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Tags: zesty wayland-session Uname: Linux 4.8.17-040817-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1676918/+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 1676918] Re: blackscreen when trying to resume from suspend
Got a blackscreen with Kernel 4.11. Unfortunately kern.log and syslog don't have any entries about it. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1676918 Title: blackscreen when trying to resume from suspend Status in gnome-power-manager package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: When trying to resume after suspending my Lenovo Yoga 3 11, sometimes the screen remains black. The power LED switches from blinking to continuous light like it should but nothing else happens. The system does not react to anything. I tried to find something in the logs, but at least kern.log syslog and xorg.log never have any entries from this event. This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and Wayland. I'm currently testing Kernel 4.8 from the mainline ppa because of this other suspend resume bug, that appeared only with 17.04: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1676912 --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-03-24 (4 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) Package: systemd 232-19 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Tags: zesty wayland-session Uname: Linux 4.8.17-040817-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1676918/+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 1676918] Re: blackscreen when trying to resume from suspend
Trying Kernel 4.11 since yesterday. So far no blackscreens but I think I should test it for a longer duration. Unfortunately Kernel 4.11 is no real solution for me because of another suspend/resume bug that as far as I can tell at the moment might exist since Kernel 4.9. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1676918 Title: blackscreen when trying to resume from suspend Status in gnome-power-manager package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: When trying to resume after suspending my Lenovo Yoga 3 11, sometimes the screen remains black. The power LED switches from blinking to continuous light like it should but nothing else happens. The system does not react to anything. I tried to find something in the logs, but at least kern.log syslog and xorg.log never have any entries from this event. This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and Wayland. I'm currently testing Kernel 4.8 from the mainline ppa because of this other suspend resume bug, that appeared only with 17.04: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1676912 --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-03-24 (4 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) Package: systemd 232-19 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Tags: zesty wayland-session Uname: Linux 4.8.17-040817-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1676918/+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 1676912] Re: Suspend - Freezing of tasks failed
I had some similar suspend/resume issues when trying mainline Kernels in 16.04. Every Kernel since 4.9 would cause terribly slow system after resuming. I will test Kernel 4.8 in next days to see if this problem is present there too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1676912 Title: Suspend - Freezing of tasks failed Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Recently I replaced Ubuntu 16.04 on my Lenovo Yoga 3 11 with Ubuntu Gnome 17.04 and since then sometimes my Laptop won't suspend when I close the lid. The power led does not blink like it is supposed to do and when I open the Laptop the lockscreen appears but freezes after a short time, followed by a blackscreen until eventually it reappears and allows me to unlock it. After that certain application can not be started anymore and would freeze if they were running before. These include Chrome, Gedit and Gnome System Monitor for example. Also my Laptop will not connect to my WLAN until I restart it. In syslog I found the line: "Freezing of tasks failed after 20.005 seconds (18 tasks refusing to freeze, wq_busy=0):" According to syslog network-nanaeger whoopsie cups-browsed wpa-supplicant geoclue packagekitd several evolution-related processes goa-daemon gnome-software geary dropbox deja-dup-monitor are responsible. I tried disabling some of them, but it did not solve the problem. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-19 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 28 16:27:34 2017 InstallationDate: Installed on 2017-03-24 (3 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) MachineType: LENOVO 80J8 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic.efi.signed root=UUID=8c63f102-527f-412a-bafe-7b9075ea6b56 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2015 dmi.bios.vendor: LENOVO dmi.bios.version: B8CN31WW(V2.09) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Paganini dmi.board.vendor: LENOVO dmi.board.version: 31900058 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 3 11 dmi.modalias: dmi:bvnLENOVO:bvrB8CN31WW(V2.09):bd07/15/2015:svnLENOVO:pn80J8:pvrLenovoYoga311:rvnLENOVO:rnPaganini:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga311: dmi.product.name: 80J8 dmi.product.version: Lenovo Yoga 3 11 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676912/+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 1676912] Re: Suspend - Freezing of tasks failed
This problem also appears whenn using Kernel 4.11 from the mainline ppa. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1676912 Title: Suspend - Freezing of tasks failed Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Recently I replaced Ubuntu 16.04 on my Lenovo Yoga 3 11 with Ubuntu Gnome 17.04 and since then sometimes my Laptop won't suspend when I close the lid. The power led does not blink like it is supposed to do and when I open the Laptop the lockscreen appears but freezes after a short time, followed by a blackscreen until eventually it reappears and allows me to unlock it. After that certain application can not be started anymore and would freeze if they were running before. These include Chrome, Gedit and Gnome System Monitor for example. Also my Laptop will not connect to my WLAN until I restart it. In syslog I found the line: "Freezing of tasks failed after 20.005 seconds (18 tasks refusing to freeze, wq_busy=0):" According to syslog network-nanaeger whoopsie cups-browsed wpa-supplicant geoclue packagekitd several evolution-related processes goa-daemon gnome-software geary dropbox deja-dup-monitor are responsible. I tried disabling some of them, but it did not solve the problem. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-19 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 28 16:27:34 2017 InstallationDate: Installed on 2017-03-24 (3 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) MachineType: LENOVO 80J8 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic.efi.signed root=UUID=8c63f102-527f-412a-bafe-7b9075ea6b56 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2015 dmi.bios.vendor: LENOVO dmi.bios.version: B8CN31WW(V2.09) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Paganini dmi.board.vendor: LENOVO dmi.board.version: 31900058 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 3 11 dmi.modalias: dmi:bvnLENOVO:bvrB8CN31WW(V2.09):bd07/15/2015:svnLENOVO:pn80J8:pvrLenovoYoga311:rvnLENOVO:rnPaganini:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga311: dmi.product.name: 80J8 dmi.product.version: Lenovo Yoga 3 11 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676912/+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 1676912] Re: Suspend - Freezing of tasks failed
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1676912 Title: Suspend - Freezing of tasks failed Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Recently I replaced Ubuntu 16.04 on my Lenovo Yoga 3 11 with Ubuntu Gnome 17.04 and since then sometimes my Laptop won't suspend when I close the lid. The power led does not blink like it is supposed to do and when I open the Laptop the lockscreen appears but freezes after a short time, followed by a blackscreen until eventually it reappears and allows me to unlock it. After that certain application can not be started anymore and would freeze if they were running before. These include Chrome, Gedit and Gnome System Monitor for example. Also my Laptop will not connect to my WLAN until I restart it. In syslog I found the line: "Freezing of tasks failed after 20.005 seconds (18 tasks refusing to freeze, wq_busy=0):" According to syslog network-nanaeger whoopsie cups-browsed wpa-supplicant geoclue packagekitd several evolution-related processes goa-daemon gnome-software geary dropbox deja-dup-monitor are responsible. I tried disabling some of them, but it did not solve the problem. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-19 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 28 16:27:34 2017 InstallationDate: Installed on 2017-03-24 (3 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) MachineType: LENOVO 80J8 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic.efi.signed root=UUID=8c63f102-527f-412a-bafe-7b9075ea6b56 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2015 dmi.bios.vendor: LENOVO dmi.bios.version: B8CN31WW(V2.09) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Paganini dmi.board.vendor: LENOVO dmi.board.version: 31900058 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 3 11 dmi.modalias: dmi:bvnLENOVO:bvrB8CN31WW(V2.09):bd07/15/2015:svnLENOVO:pn80J8:pvrLenovoYoga311:rvnLENOVO:rnPaganini:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga311: dmi.product.name: 80J8 dmi.product.version: Lenovo Yoga 3 11 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676912/+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 1676918] Re: blackscreen when trying to resume from suspend
** Description changed: When trying to resume after suspending my Lenovo Yoga 3 11, sometimes the screen remains black. The power LED switches from blinking to continuous light like it should but nothing else happens. The system does not react to anything. I tried to find something in the logs, but at least kern.log syslog and xorg.log never have any entries from this event. This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and Wayland. - --- + + I'm currently testing Kernel 4.8 from the mainline ppa because of this + other suspend resume bug, that appeared only with 17.04: + + https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1676912 + + --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-03-24 (4 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) Package: systemd 232-19 PackageArchitecture: amd64 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=de_DE.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=de_DE.UTF-8 + SHELL=/bin/bash Tags: zesty wayland-session Uname: Linux 4.8.17-040817-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1676918 Title: blackscreen when trying to resume from suspend Status in gnome-power-manager package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: When trying to resume after suspending my Lenovo Yoga 3 11, sometimes the screen remains black. The power LED switches from blinking to continuous light like it should but nothing else happens. The system does not react to anything. I tried to find something in the logs, but at least kern.log syslog and xorg.log never have any entries from this event. This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and Wayland. I'm currently testing Kernel 4.8 from the mainline ppa because of this other suspend resume bug, that appeared only with 17.04: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1676912 --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-03-24 (4 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) Package: systemd 232-19 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Tags: zesty wayland-session Uname: Linux 4.8.17-040817-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1676918/+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 1676918] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1676918/+attachment/4849418/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1676918 Title: blackscreen when trying to resume from suspend Status in gnome-power-manager package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: When trying to resume after suspending my Lenovo Yoga 3 11, sometimes the screen remains black. The power LED switches from blinking to continuous light like it should but nothing else happens. The system does not react to anything. I tried to find something in the logs, but at least kern.log syslog and xorg.log never have any entries from this event. This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and Wayland. I'm currently testing Kernel 4.8 from the mainline ppa because of this other suspend resume bug, that appeared only with 17.04: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1676912 --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-03-24 (4 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) Package: systemd 232-19 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Tags: zesty wayland-session Uname: Linux 4.8.17-040817-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1676918/+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 1676918] Re: blackscreen when trying to resume from suspend
apport information ** Tags added: apport-collected wayland-session zesty ** Description changed: When trying to resume after suspending my Lenovo Yoga 3 11, sometimes the screen remains black. The power LED switches from blinking to continuous light like it should but nothing else happens. The system does not react to anything. I tried to find something in the logs, but at least kern.log syslog and xorg.log never have any entries from this event. This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and Wayland. + --- + ApportVersion: 2.20.4-0ubuntu2 + Architecture: amd64 + CurrentDesktop: GNOME + DistroRelease: Ubuntu 17.04 + InstallationDate: Installed on 2017-03-24 (4 days ago) + InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) + Package: systemd 232-19 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=de_DE.UTF-8 + SHELL=/bin/bash + Tags: zesty wayland-session + Uname: Linux 4.8.17-040817-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1676918/+attachment/4849417/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1676918 Title: blackscreen when trying to resume from suspend Status in gnome-power-manager package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: When trying to resume after suspending my Lenovo Yoga 3 11, sometimes the screen remains black. The power LED switches from blinking to continuous light like it should but nothing else happens. The system does not react to anything. I tried to find something in the logs, but at least kern.log syslog and xorg.log never have any entries from this event. This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and Wayland. I'm currently testing Kernel 4.8 from the mainline ppa because of this other suspend resume bug, that appeared only with 17.04: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1676912 --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-03-24 (4 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) Package: systemd 232-19 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Tags: zesty wayland-session Uname: Linux 4.8.17-040817-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1676918/+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 1676918] Re: blackscreen when trying to resume from suspend
** Package changed: ubuntu => linux (Ubuntu) ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1676918 Title: blackscreen when trying to resume from suspend Status in gnome-power-manager package in Ubuntu: New Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: When trying to resume after suspending my Lenovo Yoga 3 11, sometimes the screen remains black. The power LED switches from blinking to continuous light like it should but nothing else happens. The system does not react to anything. I tried to find something in the logs, but at least kern.log syslog and xorg.log never have any entries from this event. This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and Wayland. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1676918/+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 1676912] [NEW] Suspend - Freezing of tasks failed
Public bug reported: Recently I replaced Ubuntu 16.04 on my Lenovo Yoga 3 11 with Ubuntu Gnome 17.04 and since then sometimes my Laptop won't suspend when I close the lid. The power led does not blink like it is supposed to do and when I open the Laptop the lockscreen appears but freezes after a short time, followed by a blackscreen until eventually it reappears and allows me to unlock it. After that certain application can not be started anymore and would freeze if they were running before. These include Chrome, Gedit and Gnome System Monitor for example. Also my Laptop will not connect to my WLAN until I restart it. In syslog I found the line: "Freezing of tasks failed after 20.005 seconds (18 tasks refusing to freeze, wq_busy=0):" According to syslog network-nanaeger whoopsie cups-browsed wpa-supplicant geoclue packagekitd several evolution-related processes goa-daemon gnome-software geary dropbox deja-dup-monitor are responsible. I tried disabling some of them, but it did not solve the problem. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-19 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 28 16:27:34 2017 InstallationDate: Installed on 2017-03-24 (3 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) MachineType: LENOVO 80J8 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic.efi.signed root=UUID=8c63f102-527f-412a-bafe-7b9075ea6b56 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2015 dmi.bios.vendor: LENOVO dmi.bios.version: B8CN31WW(V2.09) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Paganini dmi.board.vendor: LENOVO dmi.board.version: 31900058 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 3 11 dmi.modalias: dmi:bvnLENOVO:bvrB8CN31WW(V2.09):bd07/15/2015:svnLENOVO:pn80J8:pvrLenovoYoga311:rvnLENOVO:rnPaganini:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga311: dmi.product.name: 80J8 dmi.product.version: Lenovo Yoga 3 11 dmi.sys.vendor: LENOVO ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug suspend-resume zesty ** Attachment added: "Syslog" https://bugs.launchpad.net/bugs/1676912/+attachment/4848876/+files/syslog.1 ** Tags removed: wayland-session ** Tags added: suspend-resume -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1676912 Title: Suspend - Freezing of tasks failed Status in systemd package in Ubuntu: New Bug description: Recently I replaced Ubuntu 16.04 on my Lenovo Yoga 3 11 with Ubuntu Gnome 17.04 and since then sometimes my Laptop won't suspend when I close the lid. The power led does not blink like it is supposed to do and when I open the Laptop the lockscreen appears but freezes after a short time, followed by a blackscreen until eventually it reappears and allows me to unlock it. After that certain application can not be started anymore and would freeze if they were running before. These include Chrome, Gedit and Gnome System Monitor for example. Also my Laptop will not connect to my WLAN until I restart it. In syslog I found the line: "Freezing of tasks failed after 20.005 seconds (18 tasks refusing to freeze, wq_busy=0):" According to syslog network-nanaeger whoopsie cups-browsed wpa-supplicant geoclue packagekitd several evolution-related processes goa-daemon gnome-software geary dropbox deja-dup-monitor are responsible. I tried disabling some of them, but it did not solve the problem. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-19 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 28 16:27:34 2017 InstallationDate: Installed on 2017-03-24 (3 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) MachineType: LENOVO 80J8 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic.efi.signed root=UUID=8c63f102-527f-412a-bafe-7b9075ea6b56 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2015 dmi.bios.vendor: LENOVO dmi.bios.version: B8CN31WW(V2.09) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Paganini dmi.board.vendor: LENOVO
[Touch-packages] [Bug 1511735] Re: libnl: fail to bind() netlink sockets
This update broke Network-Manager on my system. Used these steps to manually downgrade libnl to get network connections working again. http://askubuntu.com/questions/727127/last-upgrade-crashes-network- manager-no-internet-connection-no-applet -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1511735 Title: libnl: fail to bind() netlink sockets Status in libnl3 package in Ubuntu: Fix Released Status in libnl3 source package in Trusty: Fix Released Status in libnl3 package in Debian: Fix Released Bug description: [Triage Notes] The proposed fix for this bug in libnl3 caused a regression in trusty- proposed, tracked in bug 1539634. The regression is caused by a latent bug in Network Manager. We expect to fix this by landing a fix for the bug in Network Manager in trusty-updates at the same time as this fix. [Impact] * Applications in Trusty using libnl-3-200 which frequently open and close netlink sockets can easily fail when attempting to bind the local socket. The problem happens when libnl choose a port id already used by another application and subsequently libnl fails instead of trying another port id. The original bug was discovered when attempting to start a virtual machine under libvirt, which is a user of this library. * Backporting fixes from upstream release fixes a real bug in the current version of the library in Trusty. The alternative is for all applications to manually manage their local port allocation, or as upstream has accepted allowing libnl to attempt to try for other local ports. * All patches applied are already accepted upstream and newer Ubuntu releases are not affected. [Test Case] * On a Trusty 14.04 system 1. sudo apt-get install libnl-3-200 libnl-3-dev libnl-3-dev \ libnl-genl-3-dev libnl-route-3-200 \ make gcc build-essential libnl1 2. download and unpack attachment: lp_1511735_test.tar 3. Run testcases: % if ./example.sh; then echo "libnl OK"; else echo "libnl FAILED"; fi gcc -o example -I/usr/include/libnl3 example.c -lnl-3 -lnl-genl-3 set manually the local port to 6975 (pid: 6974) local port has been set by the libnl to 6975 (pid: 6975) ERROR: genl_connect(): Object exists (local port: 6975, pid: 6975) libnl FAILED % python libnl3-test-rh1249158.py a b c d ulimit(NOFILE) = (2048, 4096) Test: PID=6978 TEST (a)... Traceback (most recent call last): File "libnl3-test-rh1249158.py", line 226, in locals()["TEST_" + arg]() File "libnl3-test-rh1249158.py", line 140, in TEST_a sk = nl_get_socket() File "libnl3-test-rh1249158.py", line 115, in nl_get_socket raise IOError(-err, _nl_geterror()) OSError: [Errno 6] b'Unspecific failure' 4. After applying the updated packages: % if ./example.sh; then echo "libnl OK"; else echo "libnl FAILED"; fi gcc -o example -I/usr/include/libnl3 example.c -lnl-3 -lnl-genl-3 set manually the local port to 11295 (pid: 11294) local port has been set by the libnl to 2894081055 (pid: 11295) libnl OK % python libnl3-test-rh1249158.py a b c d ulimit(NOFILE) = (2048, 4096) Test: PID=11296 TEST (a)... ...done TEST (b)... ...done TEST (c)... ...done TEST (d)... ...done [Regression Potential] * There are quite a few high profile packages that depend on this package, notably libvirt and network-manager. The complete list is here: # on Trusty % apt-rdepends -r libnl-3-200 | head -n 33 libnl-3-200 Reverse Depends: batctl (>= 2013.4.0-2) Reverse Depends: bmon (>= 1:3.1-1) Reverse Depends: crda (>= 1.1.2-1ubuntu2) Reverse Depends: hostapd (>= 1:2.1-0ubuntu1) Reverse Depends: ipvsadm (>= 1:1.26-2ubuntu1) Reverse Depends: iw (>= 3.4-1) Reverse Depends: keepalived (>= 1:1.2.7-1ubuntu1) Reverse Depends: kismet (>= 2013.03.R1b-3) Reverse Depends: knemo (>= 0.7.6-2) Reverse Depends: libfsobasics3 (>= 0.12.0-4) Reverse Depends: libnetcf1 (>= 1:0.2.3-4ubuntu1) Reverse Depends: libnl-3-200-dbg (= 3.2.21-1) Reverse Depends: libnl-3-dev (= 3.2.21-1) Reverse Depends: libnl-cli-3-200 (= 3.2.21-1) Reverse Depends: libnl-genl-3-200 (= 3.2.21-1) Reverse Depends: libnl-nf-3-200 (= 3.2.21-1) Reverse Depends: libnl-route-3-200 (= 3.2.21-1) Reverse Depends: libnl-utils (>= 3.2.21-1) Reverse Depends: libnss-gw-name (>= 0.3-2) Reverse Depends: libvirt-bin (>= 1.2.2-0ubuntu13) Reverse Depends: libvirt0 (>= 1.2.2-0ubuntu13) Reverse Depends: lowpan-test-tools (>= 0.3-1)
[Touch-packages] [Bug 1572653] Re: keyboard does not show up on xenial
Entering env | grep QT_DEVICE_PIXEL_RATIO in a terminal, gives me no output. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1572653 Title: keyboard does not show up on xenial Status in ubuntu-keyboard package in Ubuntu: New Bug description: Expected behaviour: Install ubuntu-keyboard, run maliit-server, click on place to enter text -> keyboard shows up. What happens: Running maliit-server after installing ubuntu-keyboard-english in terminal shows following error: WARNING: void MIMPluginManagerPrivate::_q_setActiveSubView(const QString&, Maliit::HandlerState) "libubuntu-keyboard-plugin.so" "en" is not enabled Clicking on fields for entering text, does not cause the keyboard to show up. What I tried so far: export QT_IM_MODULE=Maliit export GTK_IM_MODULE=Maliit and gconftool-2 -s --type list --list-type string /maliit/onscreen/enabled "[llibubuntu-keyboard-plugin.so,en_gb]" gconftool-2 -s --type list --list-type string /maliit/onscreen/active "[libubuntu-keyboard-plugin.so,en_gb]" according to https://github.com/maliit/framework and https://github.com/maliit/plugins but it still won't show up. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-keyboard 0.99.trunk.phablet2+16.04.20160226.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 20 18:03:03 2016 InstallationDate: Installed on 2016-04-03 (16 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-keyboard UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.xdg.maliit.org.server.conf: [modified] mtime.conffile..etc.xdg.maliit.org.server.conf: 2016-04-20T17:40:50.856195 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1572653/+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 1572653] Re: keyboard does not show up on xenial
QT_IM_MODULE=maliitphablet qmlscene Works for me too, but GTK_IM_MODULE=maliitphablet gedit or GTK_IM_MODULE=maliitphablet nautilus does not. Might be a problem with the gtk module. Is there any way to unhide the keyboard manually for usage with unsupported applications like chrome or steam or to bypass the problem with gtk? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1572653 Title: keyboard does not show up on xenial Status in ubuntu-keyboard package in Ubuntu: New Bug description: Expected behaviour: Install ubuntu-keyboard, run maliit-server, click on place to enter text -> keyboard shows up. What happens: Running maliit-server after installing ubuntu-keyboard-english in terminal shows following error: WARNING: void MIMPluginManagerPrivate::_q_setActiveSubView(const QString&, Maliit::HandlerState) "libubuntu-keyboard-plugin.so" "en" is not enabled Clicking on fields for entering text, does not cause the keyboard to show up. What I tried so far: export QT_IM_MODULE=Maliit export GTK_IM_MODULE=Maliit and gconftool-2 -s --type list --list-type string /maliit/onscreen/enabled "[llibubuntu-keyboard-plugin.so,en_gb]" gconftool-2 -s --type list --list-type string /maliit/onscreen/active "[libubuntu-keyboard-plugin.so,en_gb]" according to https://github.com/maliit/framework and https://github.com/maliit/plugins but it still won't show up. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-keyboard 0.99.trunk.phablet2+16.04.20160226.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 20 18:03:03 2016 InstallationDate: Installed on 2016-04-03 (16 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-keyboard UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.xdg.maliit.org.server.conf: [modified] mtime.conffile..etc.xdg.maliit.org.server.conf: 2016-04-20T17:40:50.856195 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1572653/+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 1572653] Re: keyboard does not show up on xenial
Next problem: when trying QT_IM_MODULE=maliitphablet qmlscene the keyboard hides again, when I press on its keys. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1572653 Title: keyboard does not show up on xenial Status in ubuntu-keyboard package in Ubuntu: New Bug description: Expected behaviour: Install ubuntu-keyboard, run maliit-server, click on place to enter text -> keyboard shows up. What happens: Running maliit-server after installing ubuntu-keyboard-english in terminal shows following error: WARNING: void MIMPluginManagerPrivate::_q_setActiveSubView(const QString&, Maliit::HandlerState) "libubuntu-keyboard-plugin.so" "en" is not enabled Clicking on fields for entering text, does not cause the keyboard to show up. What I tried so far: export QT_IM_MODULE=Maliit export GTK_IM_MODULE=Maliit and gconftool-2 -s --type list --list-type string /maliit/onscreen/enabled "[llibubuntu-keyboard-plugin.so,en_gb]" gconftool-2 -s --type list --list-type string /maliit/onscreen/active "[libubuntu-keyboard-plugin.so,en_gb]" according to https://github.com/maliit/framework and https://github.com/maliit/plugins but it still won't show up. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-keyboard 0.99.trunk.phablet2+16.04.20160226.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 20 18:03:03 2016 InstallationDate: Installed on 2016-04-03 (16 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-keyboard UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.xdg.maliit.org.server.conf: [modified] mtime.conffile..etc.xdg.maliit.org.server.conf: 2016-04-20T17:40:50.856195 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1572653/+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 1572653] Re: keyboard does not show up on xenial
I tried maliitphablet, but I still can't find a way to get the keyboard to show up. ** Changed in: ubuntu-keyboard (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1572653 Title: keyboard does not show up on xenial Status in ubuntu-keyboard package in Ubuntu: New Bug description: Expected behaviour: Install ubuntu-keyboard, run maliit-server, click on place to enter text -> keyboard shows up. What happens: Running maliit-server after installing ubuntu-keyboard-english in terminal shows following error: WARNING: void MIMPluginManagerPrivate::_q_setActiveSubView(const QString&, Maliit::HandlerState) "libubuntu-keyboard-plugin.so" "en" is not enabled Clicking on fields for entering text, does not cause the keyboard to show up. What I tried so far: export QT_IM_MODULE=Maliit export GTK_IM_MODULE=Maliit and gconftool-2 -s --type list --list-type string /maliit/onscreen/enabled "[llibubuntu-keyboard-plugin.so,en_gb]" gconftool-2 -s --type list --list-type string /maliit/onscreen/active "[libubuntu-keyboard-plugin.so,en_gb]" according to https://github.com/maliit/framework and https://github.com/maliit/plugins but it still won't show up. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-keyboard 0.99.trunk.phablet2+16.04.20160226.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 20 18:03:03 2016 InstallationDate: Installed on 2016-04-03 (16 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-keyboard UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.xdg.maliit.org.server.conf: [modified] mtime.conffile..etc.xdg.maliit.org.server.conf: 2016-04-20T17:40:50.856195 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1572653/+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 1572653] [NEW] keyboard does not show up on xenial
Public bug reported: Expected behaviour: Install ubuntu-keyboard, run maliit-server, click on place to enter text -> keyboard shows up. What happens: Running maliit-server after installing ubuntu-keyboard-english in terminal shows following error: WARNING: void MIMPluginManagerPrivate::_q_setActiveSubView(const QString&, Maliit::HandlerState) "libubuntu-keyboard-plugin.so" "en" is not enabled Clicking on fields for entering text, does not cause the keyboard to show up. What I tried so far: export QT_IM_MODULE=Maliit export GTK_IM_MODULE=Maliit and gconftool-2 -s --type list --list-type string /maliit/onscreen/enabled "[llibubuntu-keyboard-plugin.so,en_gb]" gconftool-2 -s --type list --list-type string /maliit/onscreen/active "[libubuntu-keyboard-plugin.so,en_gb]" according to https://github.com/maliit/framework and https://github.com/maliit/plugins but it still won't show up. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-keyboard 0.99.trunk.phablet2+16.04.20160226.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 20 18:03:03 2016 InstallationDate: Installed on 2016-04-03 (16 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-keyboard UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.xdg.maliit.org.server.conf: [modified] mtime.conffile..etc.xdg.maliit.org.server.conf: 2016-04-20T17:40:50.856195 ** Affects: ubuntu-keyboard (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1572653 Title: keyboard does not show up on xenial Status in ubuntu-keyboard package in Ubuntu: New Bug description: Expected behaviour: Install ubuntu-keyboard, run maliit-server, click on place to enter text -> keyboard shows up. What happens: Running maliit-server after installing ubuntu-keyboard-english in terminal shows following error: WARNING: void MIMPluginManagerPrivate::_q_setActiveSubView(const QString&, Maliit::HandlerState) "libubuntu-keyboard-plugin.so" "en" is not enabled Clicking on fields for entering text, does not cause the keyboard to show up. What I tried so far: export QT_IM_MODULE=Maliit export GTK_IM_MODULE=Maliit and gconftool-2 -s --type list --list-type string /maliit/onscreen/enabled "[llibubuntu-keyboard-plugin.so,en_gb]" gconftool-2 -s --type list --list-type string /maliit/onscreen/active "[libubuntu-keyboard-plugin.so,en_gb]" according to https://github.com/maliit/framework and https://github.com/maliit/plugins but it still won't show up. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-keyboard 0.99.trunk.phablet2+16.04.20160226.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 20 18:03:03 2016 InstallationDate: Installed on 2016-04-03 (16 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-keyboard UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.xdg.maliit.org.server.conf: [modified] mtime.conffile..etc.xdg.maliit.org.server.conf: 2016-04-20T17:40:50.856195 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1572653/+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 1413165] Re: Regression: Default on-screen keyboard Onboard not properly above dash
Well I guess I fixed this bug by myself now. I've done the most stupid thing possible and installed unity-7.3.2 from the vivid repository on a trusty installation. Its a miracle that the system is not broken, but now Onboard works with the Dashboard again. :D -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1413165 Title: Regression: Default on-screen keyboard Onboard not properly above dash Status in Unity: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: Hi, Some recent update of broke the default on-screen Onboard to work properly on dash. In fact, Onboard is shown in dash, as if it was located under dash. It is particularly visible, when the dash is maximized and covers the whole screen. However, if I drag Onboard to position it under an icon in dash and I click on the icon, the corresponding application is not started; the click goes down to Onboard, which types the letter of the Onboard key placed at the position of the click. So, in a few words: dash draws Onboard as if it was covered by dash, but Onboard behaves as if it is located over dash. Having a vivid backup from about one month ago, we were able to determine that the regression seem to have happened because of the update of libunity-core and the related packages somewhere between one month ago and today. In fact, the problem appeared in the test after updating the following packages and versions to the version shipping currently in the repositories. libunity-core-6.0-9 7.3.1+15.04.20141128-0ubuntu1 libcairo-gobject2 1.13.0~20140204-0ubuntu1 libcairo-script-interpreter2 1.13.0~20140204-0ubuntu1 libcairo2 1.13.0~20140204-0ubuntu1 libcairo2-dev 1.13.0~20140204-0ubuntu1 unity 7.3.1+15.04.20141128-0ubuntu1 unity-schemas 7.3.1+15.04.20141128-0ubuntu1 unity-services 7.3.1+15.04.20141128-0ubuntu1 Cheers To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1413165/+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 1413165] Re: Regression: Default on-screen keyboard Onboard not properly above dash
I'm getting this bug now in trusty. Any chance to backport the fix? Here is the output of sudo apt-chache policy unity unity: Installiert: 7.2.4+14.04.20150316-0ubuntu1 Installationskandidat: 7.2.4+14.04.20150316-0ubuntu1 Versionstabelle: *** 7.2.4+14.04.20150316-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 7.2.2+14.04.20140714-0ubuntu1.1 0 500 http://archive.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 7.2.0+14.04.20140416-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Package I'm using Ubuntu on a tablet computer, so I pretty much depend on a working onscreen keyboard. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1413165 Title: Regression: Default on-screen keyboard Onboard not properly above dash Status in Unity: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: Hi, Some recent update of broke the default on-screen Onboard to work properly on dash. In fact, Onboard is shown in dash, as if it was located under dash. It is particularly visible, when the dash is maximized and covers the whole screen. However, if I drag Onboard to position it under an icon in dash and I click on the icon, the corresponding application is not started; the click goes down to Onboard, which types the letter of the Onboard key placed at the position of the click. So, in a few words: dash draws Onboard as if it was covered by dash, but Onboard behaves as if it is located over dash. Having a vivid backup from about one month ago, we were able to determine that the regression seem to have happened because of the update of libunity-core and the related packages somewhere between one month ago and today. In fact, the problem appeared in the test after updating the following packages and versions to the version shipping currently in the repositories. libunity-core-6.0-9 7.3.1+15.04.20141128-0ubuntu1 libcairo-gobject2 1.13.0~20140204-0ubuntu1 libcairo-script-interpreter2 1.13.0~20140204-0ubuntu1 libcairo2 1.13.0~20140204-0ubuntu1 libcairo2-dev 1.13.0~20140204-0ubuntu1 unity 7.3.1+15.04.20141128-0ubuntu1 unity-schemas 7.3.1+15.04.20141128-0ubuntu1 unity-services 7.3.1+15.04.20141128-0ubuntu1 Cheers To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1413165/+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