[Touch-packages] [Bug 1818249] [NEW] Panel screen does not turn on after login if notebook was suspended by closing the lid
Public bug reported: On Xubuntu 18.04, if it's set on power manager settings to suspend the notebook if the lid is closed, when it's open, the login screen appears but after the login the screen turns off. It was observed with xrandr that no resolution is set. To fix this, I have to do one of these three actions: 1) Use the xrandr command blindly; 2) Restart LightDM from a TTY; 3) Reboot. When suspending using the Whisker Menu or using systemctl suspend, the notebook panel turns on normally after login. It's happening only when suspending by closing the notebook lid. Maybe it detects no screen connected and then unset all resolutions? The notebook model page is: https://pcsupport.lenovo.com/br/pt/products /laptops-and-netbooks/300-series/310-14isk/80ug/80ugbr ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 1 12:24:33 2019 InstallationDate: Installed on 2017-06-13 (625 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: lightdm UpgradeStatus: Upgraded to bionic on 2017-10-20 (497 days ago) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1818249 Title: Panel screen does not turn on after login if notebook was suspended by closing the lid Status in lightdm package in Ubuntu: New Bug description: On Xubuntu 18.04, if it's set on power manager settings to suspend the notebook if the lid is closed, when it's open, the login screen appears but after the login the screen turns off. It was observed with xrandr that no resolution is set. To fix this, I have to do one of these three actions: 1) Use the xrandr command blindly; 2) Restart LightDM from a TTY; 3) Reboot. When suspending using the Whisker Menu or using systemctl suspend, the notebook panel turns on normally after login. It's happening only when suspending by closing the notebook lid. Maybe it detects no screen connected and then unset all resolutions? The notebook model page is: https://pcsupport.lenovo.com/br/pt/products/laptops-and- netbooks/300-series/310-14isk/80ug/80ugbr ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 1 12:24:33 2019 InstallationDate: Installed on 2017-06-13 (625 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: lightdm UpgradeStatus: Upgraded to bionic on 2017-10-20 (497 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1818249/+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 1763537] [NEW] libpulse-dev don't provide the required files to build static programs
Public bug reported: The package libpulse-dev don't provide the static libraries files required to build static programs using libpulse-dev but, when building pulseaudio, there is a option to build static libraries. Could they be added to the package libpulse-dev? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libpulse-dev 1:11.1-1ubuntu7 Uname: Linux 4.16.1-041601-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: usuario1945 F...m pulseaudio /dev/snd/controlC0: usuario1945 F pulseaudio /dev/snd/seq:usuario1926 F timidity CurrentDesktop: XFCE Date: Thu Apr 12 20:13:18 2018 InstallationDate: Installed on 2017-06-13 (303 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: pulseaudio UpgradeStatus: Upgraded to bionic on 2017-10-20 (174 days ago) dmi.bios.date: 07/10/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.modalias: dmi:bvnLENOVO:bvr0XCN43WW:bd07/10/2017:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UG dmi.product.version: Lenovo ideapad 310-14ISK dmi.sys.vendor: LENOVO ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1763537 Title: libpulse-dev don't provide the required files to build static programs Status in pulseaudio package in Ubuntu: New Bug description: The package libpulse-dev don't provide the static libraries files required to build static programs using libpulse-dev but, when building pulseaudio, there is a option to build static libraries. Could they be added to the package libpulse-dev? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libpulse-dev 1:11.1-1ubuntu7 Uname: Linux 4.16.1-041601-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: usuario1945 F...m pulseaudio /dev/snd/controlC0: usuario1945 F pulseaudio /dev/snd/seq:usuario1926 F timidity CurrentDesktop: XFCE Date: Thu Apr 12 20:13:18 2018 InstallationDate: Installed on 2017-06-13 (303 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: pulseaudio UpgradeStatus: Upgraded to bionic on 2017-10-20 (174 days ago) dmi.bios.date: 07/10/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.modalias: dmi:bvnLENOVO:bvr0XCN43WW:bd07/10/2017:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UG dmi.product.version: Lenovo ideapad 310-14ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1763537/+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 1687353] Re: System freezes due to ALSA error and recovers after significant time
This was corrected and is no longer happening to me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1687353 Title: System freezes due to ALSA error and recovers after significant time Status in alsa-lib package in Ubuntu: Confirmed Bug description: Hello I have a Lenovo Ideapad 310. I was having issues with power management, and was using upstream kernels. I noticed they had frequent freezes, so I decided to use the standard from Ubuntu 16.04 (today, 4.4.0-75). But now it has this freezes too, so something which was bugged on the newer kernel was inserted on 4.4.0-75, as previous version (4.4.0-72) hadn't this issue. What is happening is: the system freezes. The sound that was being played loops endlessly. Everything freezes, Ctrl+Alt+Fnumber don't work. The system completely stops. Normally, I would just power the computer off keeping the power button pressed. But this time I tried to recover it, as the syslog ended always corrupted. I needed to gets the logs at least once. So I started to disconnect hardware parts: battery charger, external USB HDD (it was not being accessed), USB mouse, USB keyboard. When I disconnected the sound jack, I noticed the mouse moved, so it was recoverable. I waited for 100 seconds until the system recovered. When it recovered, looked like nothing had happened, and now I'm writing this report from the computer, without restarting. Steps to reproduce: 1) open Audacious or VLC; 2) play a music/video on Audacious or VLC; 3) open another program with sound (Steam, a browser (I use Opera), etc); 4) use the computer until a freeze happens. Observations: -Audacious + Steam + Starbound is nearly 100% chance of triggering it (SDL?). -VLC + Opera + Firefox (on start page) was enough for trigger it once, even with the only program with media opened being VLC. The freeze I was able to recover had: Opera Developer (YouTube video playing) + Audacious (playing) + Steam with audio streams opened on pavucontrol. Additionally, Thunderbird and Evince were opened, and intel-gpu-overlay was opened inside a Xnest window. The syslog says to report to alsa, so I'm writing the report here. However, it should be noted that there is a i915 error too, maybe it was a consequence, maybe it was the cause. $ lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 $ uname -a Linux usuario-Lenovo-ideapad-310-14ISK 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Thank you. Edit: one thing I noticed with indicator-multiload, the internal HDD activity completely stopped while this problem was happening and soon after it started to function. It was like the computer was recovering with the internal HDD turned off. The HDD usage ramped up and the system returned to normal. May this be related with the power management issues? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libasound2 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59 Uname: Linux 4.4.0-75-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Apr 30 23:43:29 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libasound2-data 1.1.0-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1:6.0.1-0ubuntu1 InstallationDate: Installed on 2016-12-31 (121 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: alsa-lib UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1687353/+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 1750421] Re: package libfontconfig1-dev 2.12.6-0ubuntu1 failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz' partilhado,
** Description changed: Hi I "upgraded" from Xubuntu 17.10 to 18.04 using the information from this post: https://community.ubuntu.com/t/bionic-daily-is-out/1530/4 - When libfontconfig-dev:amd64 tried to update it failed. I tried again + When libfontconfig1-dev:amd64 tried to update it failed. I tried again and it failed again, then I opened synaptic and noticed that the - libfontconfig-dev:i386 was already updated to the last version. After + libfontconfig1-dev:i386 was already updated to the last version. After the i386 version was purged, the amd64 version could be updated and the upgrade finished. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libfontconfig1-dev 2.12.6-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Mon Feb 19 14:38:06 2018 ErrorMessage: a tentar sobreescrever '/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz' partilhado, que é diferente de outras instâncias do pacote libfontconfig1-dev:amd64 InstallationDate: Installed on 2017-06-13 (250 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: - dpkg 1.19.0.5ubuntu1 - apt 1.6~alpha7ubuntu2 + dpkg 1.19.0.5ubuntu1 + apt 1.6~alpha7ubuntu2 SourcePackage: fontconfig Title: package libfontconfig1-dev 2.12.6-0ubuntu1 failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz' partilhado, que é diferente de outras instâncias do pacote libfontconfig1-dev:amd64 UpgradeStatus: Upgraded to bionic on 2017-10-20 (122 days ago) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1750421 Title: package libfontconfig1-dev 2.12.6-0ubuntu1 failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libfontconfig1-dev/fontconfig- devel.pdf.gz' partilhado, que é diferente de outras instâncias do pacote libfontconfig1-dev:amd64 Status in fontconfig package in Ubuntu: New Bug description: Hi I "upgraded" from Xubuntu 17.10 to 18.04 using the information from this post: https://community.ubuntu.com/t/bionic-daily-is-out/1530/4 When libfontconfig1-dev:amd64 tried to update it failed. I tried again and it failed again, then I opened synaptic and noticed that the libfontconfig1-dev:i386 was already updated to the last version. After the i386 version was purged, the amd64 version could be updated and the upgrade finished. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libfontconfig1-dev 2.12.6-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Mon Feb 19 14:38:06 2018 ErrorMessage: a tentar sobreescrever '/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz' partilhado, que é diferente de outras instâncias do pacote libfontconfig1-dev:amd64 InstallationDate: Installed on 2017-06-13 (250 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~alpha7ubuntu2 SourcePackage: fontconfig Title: package libfontconfig1-dev 2.12.6-0ubuntu1 failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz' partilhado, que é diferente de outras instâncias do pacote libfontconfig1-dev:amd64 UpgradeStatus: Upgraded to bionic on 2017-10-20 (122 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1750421/+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 1750421] [NEW] package libfontconfig1-dev 2.12.6-0ubuntu1 failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz' partilhado
Public bug reported: Hi I "upgraded" from Xubuntu 17.10 to 18.04 using the information from this post: https://community.ubuntu.com/t/bionic-daily-is-out/1530/4 When libfontconfig-dev:amd64 tried to update it failed. I tried again and it failed again, then I opened synaptic and noticed that the libfontconfig-dev:i386 was already updated to the last version. After the i386 version was purged, the amd64 version could be updated and the upgrade finished. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libfontconfig1-dev 2.12.6-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Mon Feb 19 14:38:06 2018 ErrorMessage: a tentar sobreescrever '/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz' partilhado, que é diferente de outras instâncias do pacote libfontconfig1-dev:amd64 InstallationDate: Installed on 2017-06-13 (250 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~alpha7ubuntu2 SourcePackage: fontconfig Title: package libfontconfig1-dev 2.12.6-0ubuntu1 failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz' partilhado, que é diferente de outras instâncias do pacote libfontconfig1-dev:amd64 UpgradeStatus: Upgraded to bionic on 2017-10-20 (122 days ago) ** Affects: fontconfig (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1750421 Title: package libfontconfig1-dev 2.12.6-0ubuntu1 failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libfontconfig1-dev/fontconfig- devel.pdf.gz' partilhado, que é diferente de outras instâncias do pacote libfontconfig1-dev:amd64 Status in fontconfig package in Ubuntu: New Bug description: Hi I "upgraded" from Xubuntu 17.10 to 18.04 using the information from this post: https://community.ubuntu.com/t/bionic-daily-is-out/1530/4 When libfontconfig-dev:amd64 tried to update it failed. I tried again and it failed again, then I opened synaptic and noticed that the libfontconfig-dev:i386 was already updated to the last version. After the i386 version was purged, the amd64 version could be updated and the upgrade finished. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libfontconfig1-dev 2.12.6-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Mon Feb 19 14:38:06 2018 ErrorMessage: a tentar sobreescrever '/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz' partilhado, que é diferente de outras instâncias do pacote libfontconfig1-dev:amd64 InstallationDate: Installed on 2017-06-13 (250 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~alpha7ubuntu2 SourcePackage: fontconfig Title: package libfontconfig1-dev 2.12.6-0ubuntu1 failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libfontconfig1-dev/fontconfig-devel.pdf.gz' partilhado, que é diferente de outras instâncias do pacote libfontconfig1-dev:amd64 UpgradeStatus: Upgraded to bionic on 2017-10-20 (122 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1750421/+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 1687353] Re: System freezes due to ALSA error and recovers after significant time
I think this is the same bug I am having: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838 But this is happening with 4.4.0-75 too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1687353 Title: System freezes due to ALSA error and recovers after significant time Status in alsa-lib package in Ubuntu: Confirmed Bug description: Hello I have a Lenovo Ideapad 310. I was having issues with power management, and was using upstream kernels. I noticed they had frequent freezes, so I decided to use the standard from Ubuntu 16.04 (today, 4.4.0-75). But now it has this freezes too, so something which was bugged on the newer kernel was inserted on 4.4.0-75, as previous version (4.4.0-72) hadn't this issue. What is happening is: the system freezes. The sound that was being played loops endlessly. Everything freezes, Ctrl+Alt+Fnumber don't work. The system completely stops. Normally, I would just power the computer off keeping the power button pressed. But this time I tried to recover it, as the syslog ended always corrupted. I needed to gets the logs at least once. So I started to disconnect hardware parts: battery charger, external USB HDD (it was not being accessed), USB mouse, USB keyboard. When I disconnected the sound jack, I noticed the mouse moved, so it was recoverable. I waited for 100 seconds until the system recovered. When it recovered, looked like nothing had happened, and now I'm writing this report from the computer, without restarting. Steps to reproduce: 1) open Audacious or VLC; 2) play a music/video on Audacious or VLC; 3) open another program with sound (Steam, a browser (I use Opera), etc); 4) use the computer until a freeze happens. Observations: -Audacious + Steam + Starbound is nearly 100% chance of triggering it (SDL?). -VLC + Opera + Firefox (on start page) was enough for trigger it once, even with the only program with media opened being VLC. The freeze I was able to recover had: Opera Developer (YouTube video playing) + Audacious (playing) + Steam with audio streams opened on pavucontrol. Additionally, Thunderbird and Evince were opened, and intel-gpu-overlay was opened inside a Xnest window. The syslog says to report to alsa, so I'm writing the report here. However, it should be noted that there is a i915 error too, maybe it was a consequence, maybe it was the cause. $ lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 $ uname -a Linux usuario-Lenovo-ideapad-310-14ISK 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Thank you. Edit: one thing I noticed with indicator-multiload, the internal HDD activity completely stopped while this problem was happening and soon after it started to function. It was like the computer was recovering with the internal HDD turned off. The HDD usage ramped up and the system returned to normal. May this be related with the power management issues? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libasound2 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59 Uname: Linux 4.4.0-75-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Apr 30 23:43:29 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libasound2-data 1.1.0-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1:6.0.1-0ubuntu1 InstallationDate: Installed on 2016-12-31 (121 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: alsa-lib UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1687353/+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 1687353] Re: System freezes due to ALSA error and recovers after significant time
Hello With the kernel from linux-generic-hwe-16.04-edge, I was able to obtain in one crash the part of a log file which I was unable before, but corrupted the content after this. This new part refers to a file called swapops.h. I have attached the syslog file with the new information. As in the other times, this is the valid data, as the rest of the syslog ended corrupted (it appears # on LibreOffice and \00\00\00\00\00\00\00\00\ on gedit). At 16:17, cron run and the system is fine. At 16:39, the system locked and I waited some time, until I turned the computer off. I am not a developer, but from what I understood, the swap operation is the cause of this, and the ALSA error is a consequence of the swap error. This is happening with Starbound when teleporting so frequently because while it loads the map, it could start to use swap memory, and then this crash happens. Also, this explains why the computer recovers itself rarely. The operations which triggered it had ended, so the system was able to recover. With the game opened, the operations are always happening, so it would never recover. I hope this interpretation is correct. Thank you. ** Attachment added: "kcrash" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1687353/+attachment/4873696/+files/kcrash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1687353 Title: System freezes due to ALSA error and recovers after significant time Status in alsa-lib package in Ubuntu: Confirmed Bug description: Hello I have a Lenovo Ideapad 310. I was having issues with power management, and was using upstream kernels. I noticed they had frequent freezes, so I decided to use the standard from Ubuntu 16.04 (today, 4.4.0-75). But now it has this freezes too, so something which was bugged on the newer kernel was inserted on 4.4.0-75, as previous version (4.4.0-72) hadn't this issue. What is happening is: the system freezes. The sound that was being played loops endlessly. Everything freezes, Ctrl+Alt+Fnumber don't work. The system completely stops. Normally, I would just power the computer off keeping the power button pressed. But this time I tried to recover it, as the syslog ended always corrupted. I needed to gets the logs at least once. So I started to disconnect hardware parts: battery charger, external USB HDD (it was not being accessed), USB mouse, USB keyboard. When I disconnected the sound jack, I noticed the mouse moved, so it was recoverable. I waited for 100 seconds until the system recovered. When it recovered, looked like nothing had happened, and now I'm writing this report from the computer, without restarting. Steps to reproduce: 1) open Audacious or VLC; 2) play a music/video on Audacious or VLC; 3) open another program with sound (Steam, a browser (I use Opera), etc); 4) use the computer until a freeze happens. Observations: -Audacious + Steam + Starbound is nearly 100% chance of triggering it (SDL?). -VLC + Opera + Firefox (on start page) was enough for trigger it once, even with the only program with media opened being VLC. The freeze I was able to recover had: Opera Developer (YouTube video playing) + Audacious (playing) + Steam with audio streams opened on pavucontrol. Additionally, Thunderbird and Evince were opened, and intel-gpu-overlay was opened inside a Xnest window. The syslog says to report to alsa, so I'm writing the report here. However, it should be noted that there is a i915 error too, maybe it was a consequence, maybe it was the cause. $ lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 $ uname -a Linux usuario-Lenovo-ideapad-310-14ISK 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Thank you. Edit: one thing I noticed with indicator-multiload, the internal HDD activity completely stopped while this problem was happening and soon after it started to function. It was like the computer was recovering with the internal HDD turned off. The HDD usage ramped up and the system returned to normal. May this be related with the power management issues? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libasound2 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59 Uname: Linux 4.4.0-75-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Apr 30 23:43:29 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libasound2-data 1.1.0-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1:6.0.1-0ubuntu1 InstallationDate: Installed on 2016-12-31 (121 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: alsa-lib UpgradeStatus: No upgrade log present (probably fresh install) To manage
[Touch-packages] [Bug 1687353] Re: System freezes due to ALSA error and recovers after significant time
The easiest way to reproduce it was in the game Starbound. Teleporting, quickly the computer would freeze. I could freeze the computer in seconds doing this. While the 4.10 kernel available to install with linux-generic- hwe-16.04-edge has this bug, I believe this problem is corrected in the 4.11 kernel I downloaded at http://kernel.ubuntu.com/~kernel- ppa/mainline/v4.11/ I was able to play for many hours without the problem since I installed the kernel version 4.11. There are change notes regarding ALSA on kernel.org, I believe they are related with the problem I was having. Or I am being absurdly lucky or the bug was corrected on upstream. ** Tags added: kernel-fixed-upstream -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1687353 Title: System freezes due to ALSA error and recovers after significant time Status in alsa-lib package in Ubuntu: Confirmed Bug description: Hello I have a Lenovo Ideapad 310. I was having issues with power management, and was using upstream kernels. I noticed they had frequent freezes, so I decided to use the standard from Ubuntu 16.04 (today, 4.4.0-75). But now it has this freezes too, so something which was bugged on the newer kernel was inserted on 4.4.0-75, as previous version (4.4.0-72) hadn't this issue. What is happening is: the system freezes. The sound that was being played loops endlessly. Everything freezes, Ctrl+Alt+Fnumber don't work. The system completely stops. Normally, I would just power the computer off keeping the power button pressed. But this time I tried to recover it, as the syslog ended always corrupted. I needed to gets the logs at least once. So I started to disconnect hardware parts: battery charger, external USB HDD (it was not being accessed), USB mouse, USB keyboard. When I disconnected the sound jack, I noticed the mouse moved, so it was recoverable. I waited for 100 seconds until the system recovered. When it recovered, looked like nothing had happened, and now I'm writing this report from the computer, without restarting. Steps to reproduce: 1) open Audacious or VLC; 2) play a music/video on Audacious or VLC; 3) open another program with sound (Steam, a browser (I use Opera), etc); 4) use the computer until a freeze happens. Observations: -Audacious + Steam + Starbound is nearly 100% chance of triggering it (SDL?). -VLC + Opera + Firefox (on start page) was enough for trigger it once, even with the only program with media opened being VLC. The freeze I was able to recover had: Opera Developer (YouTube video playing) + Audacious (playing) + Steam with audio streams opened on pavucontrol. Additionally, Thunderbird and Evince were opened, and intel-gpu-overlay was opened inside a Xnest window. The syslog says to report to alsa, so I'm writing the report here. However, it should be noted that there is a i915 error too, maybe it was a consequence, maybe it was the cause. $ lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 $ uname -a Linux usuario-Lenovo-ideapad-310-14ISK 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Thank you. Edit: one thing I noticed with indicator-multiload, the internal HDD activity completely stopped while this problem was happening and soon after it started to function. It was like the computer was recovering with the internal HDD turned off. The HDD usage ramped up and the system returned to normal. May this be related with the power management issues? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libasound2 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59 Uname: Linux 4.4.0-75-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Apr 30 23:43:29 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libasound2-data 1.1.0-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1:6.0.1-0ubuntu1 InstallationDate: Installed on 2016-12-31 (121 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: alsa-lib UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1687353/+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 1687353] Re: System freezes due to ALSA error and recovers after significant time
** Description changed: Hello I have a Lenovo Ideapad 310. I was having issues with power management, and was using upstream kernels. I noticed they had frequent freezes, so I decided to use the standard from Ubuntu 16.04 (today, 4.4.0-75). But now it has this freezes too, so something which was bugged on the newer kernel was inserted on 4.4.0-75, as previous version (4.4.0-72) hadn't this issue. What is happening is: the system freezes. The sound that was being played loops endlessly. Everything freezes, Ctrl+Alt+Fnumber don't work. The system completely stops. Normally, I would just power the computer off keeping the power button pressed. But this time I tried to recover it, as the syslog ended always corrupted. I needed to gets the logs at least once. So I started to disconnect hardware parts: battery charger, external USB HDD (it was not being accessed), USB mouse, USB keyboard. When I disconnected the sound jack, I noticed the mouse moved, so it was recoverable. I waited for 100 seconds until the system recovered. When it recovered, looked like nothing had happened, and now I'm writing this report from the computer, without restarting. Steps to reproduce: 1) open Audacious or VLC; 2) play a music/video on Audacious or VLC; 3) open another program with sound (Steam, a browser (I use Opera), etc); 4) use the computer until a freeze happens. Observations: -Audacious + Steam + Starbound is nearly 100% chance of triggering it (SDL?). -VLC + Opera + Firefox (on start page) was enough for trigger it once, even with the only program with media opened being VLC. The freeze I was able to recover had: Opera Developer (YouTube video playing) + Audacious (playing) + Steam with audio streams opened on pavucontrol. Additionally, Thunderbird and Evince were opened, and intel-gpu-overlay was opened inside a Xnest window. The syslog says to report to alsa, so I'm writing the report here. However, it should be noted that there is a i915 error too, maybe it was a consequence, maybe it was the cause. $ lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 $ uname -a Linux usuario-Lenovo-ideapad-310-14ISK 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Thank you. + Edit: one thing I noticed with indicator-multiload, the internal HDD + activity completely stopped while this problem was happening and soon + after it started to function. It was like the computer was recovering + with the internal HDD turned off. The HDD usage ramped up and the system + returned to normal. May this be related with the power management + issues? + ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libasound2 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59 Uname: Linux 4.4.0-75-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Apr 30 23:43:29 2017 Dependencies: - gcc-6-base 6.0.1-0ubuntu1 - libasound2-data 1.1.0-0ubuntu1 - libc6 2.23-0ubuntu7 - libgcc1 1:6.0.1-0ubuntu1 + gcc-6-base 6.0.1-0ubuntu1 + libasound2-data 1.1.0-0ubuntu1 + libc6 2.23-0ubuntu7 + libgcc1 1:6.0.1-0ubuntu1 InstallationDate: Installed on 2016-12-31 (121 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: alsa-lib UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1687353 Title: System freezes due to ALSA error and recovers after significant time Status in alsa-lib package in Ubuntu: New Bug description: Hello I have a Lenovo Ideapad 310. I was having issues with power management, and was using upstream kernels. I noticed they had frequent freezes, so I decided to use the standard from Ubuntu 16.04 (today, 4.4.0-75). But now it has this freezes too, so something which was bugged on the newer kernel was inserted on 4.4.0-75, as previous version (4.4.0-72) hadn't this issue. What is happening is: the system freezes. The sound that was being played loops endlessly. Everything freezes, Ctrl+Alt+Fnumber don't work. The system completely stops. Normally, I would just power the computer off keeping the power button pressed. But this time I tried to recover it, as the syslog ended always corrupted. I needed to gets the logs at least once. So I started to disconnect hardware parts: battery charger, external USB HDD (it was not being accessed), USB mouse, USB keyboard. When I disconnected the sound jack, I noticed the mouse moved, so it was recoverable. I waited for 100 seconds until the system recovered. When it recovered, looked like nothing had happened, and now I'm writing this report from the computer, without
[Touch-packages] [Bug 1687353] [NEW] System freezes due to ALSA error and recovers after significant time
Public bug reported: Hello I have a Lenovo Ideapad 310. I was having issues with power management, and was using upstream kernels. I noticed they had frequent freezes, so I decided to use the standard from Ubuntu 16.04 (today, 4.4.0-75). But now it has this freezes too, so something which was bugged on the newer kernel was inserted on 4.4.0-75, as previous version (4.4.0-72) hadn't this issue. What is happening is: the system freezes. The sound that was being played loops endlessly. Everything freezes, Ctrl+Alt+Fnumber don't work. The system completely stops. Normally, I would just power the computer off keeping the power button pressed. But this time I tried to recover it, as the syslog ended always corrupted. I needed to gets the logs at least once. So I started to disconnect hardware parts: battery charger, external USB HDD (it was not being accessed), USB mouse, USB keyboard. When I disconnected the sound jack, I noticed the mouse moved, so it was recoverable. I waited for 100 seconds until the system recovered. When it recovered, looked like nothing had happened, and now I'm writing this report from the computer, without restarting. Steps to reproduce: 1) open Audacious or VLC; 2) play a music/video on Audacious or VLC; 3) open another program with sound (Steam, a browser (I use Opera), etc); 4) use the computer until a freeze happens. Observations: -Audacious + Steam + Starbound is nearly 100% chance of triggering it (SDL?). -VLC + Opera + Firefox (on start page) was enough for trigger it once, even with the only program with media opened being VLC. The freeze I was able to recover had: Opera Developer (YouTube video playing) + Audacious (playing) + Steam with audio streams opened on pavucontrol. Additionally, Thunderbird and Evince were opened, and intel-gpu-overlay was opened inside a Xnest window. The syslog says to report to alsa, so I'm writing the report here. However, it should be noted that there is a i915 error too, maybe it was a consequence, maybe it was the cause. $ lsb_release -rd Description:Ubuntu 16.04.2 LTS Release:16.04 $ uname -a Linux usuario-Lenovo-ideapad-310-14ISK 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Thank you. Edit: one thing I noticed with indicator-multiload, the internal HDD activity completely stopped while this problem was happening and soon after it started to function. It was like the computer was recovering with the internal HDD turned off. The HDD usage ramped up and the system returned to normal. May this be related with the power management issues? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libasound2 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59 Uname: Linux 4.4.0-75-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Apr 30 23:43:29 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libasound2-data 1.1.0-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1:6.0.1-0ubuntu1 InstallationDate: Installed on 2016-12-31 (121 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: alsa-lib UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: alsa-lib (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "syslog when the freeze occurred" https://bugs.launchpad.net/bugs/1687353/+attachment/4870156/+files/PULSEKERNELALSA -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1687353 Title: System freezes due to ALSA error and recovers after significant time Status in alsa-lib package in Ubuntu: New Bug description: Hello I have a Lenovo Ideapad 310. I was having issues with power management, and was using upstream kernels. I noticed they had frequent freezes, so I decided to use the standard from Ubuntu 16.04 (today, 4.4.0-75). But now it has this freezes too, so something which was bugged on the newer kernel was inserted on 4.4.0-75, as previous version (4.4.0-72) hadn't this issue. What is happening is: the system freezes. The sound that was being played loops endlessly. Everything freezes, Ctrl+Alt+Fnumber don't work. The system completely stops. Normally, I would just power the computer off keeping the power button pressed. But this time I tried to recover it, as the syslog ended always corrupted. I needed to gets the logs at least once. So I started to disconnect hardware parts: battery charger, external USB HDD (it was not being accessed), USB mouse, USB keyboard. When I disconnected the sound jack, I noticed the mouse moved, so it was recoverable. I waited for 100 seconds until the system recovered. When it recovered, looked like nothing had happened, and now I'm writing this report from the computer, without restarting.
[Touch-packages] [Bug 1665432] [NEW] Error with cups-daemon package when reinstalling many packages to recover wireless connection with QCA9377
Public bug reported: I had a issue with my Wireless and Bluetooth card, Qualcomm Atheros Device [168c:0042] (rev 30), which appears on Windows 10 as QCA9377, and to solve it I have searched and tried different alternatives. The one that worked was to reinstall many packages, all the ones I have found when searching for, firstly, "wireless", then "wifi" and then "internet", on synaptic. When doing the "internet" reinstall, a error happened on cups-daemon and it crashed. When I tried again, it worked. I rebooted the computer and the Wireless is functioning again (Bluetooth was already OK). I am using the Kernel 4.9.10-040910-generic from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9.10/ because I was trying to solve this issue and because the official Kernles 4.4 and 4.8 don't eject external HDDs from the USB 3.0 correctly. The notebook model is Lenovo Ideapad 310-14ISK. While this window to report the bug appeared saying cups is the culprit, all this only happened because the wireless device QCA9377 was not working. usuario@usuario-Lenovo-ideapad-310-14ISK:~$ lsb_release -rd Description:Ubuntu 16.04.2 LTS Release:16.04 usuario@usuario-Lenovo-ideapad-310-14ISK:~$ uname -a Linux usuario-Lenovo-ideapad-310-14ISK 4.9.10-040910-generic #201702141931 SMP Wed Feb 15 00:33:24 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux I hope this information may be helpful. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 Uname: Linux 4.9.10-040910-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CupsErrorLog: W [16/Feb/2017:14:42:01 -0200] Notifier for subscription 298 (dbus://) went away, retrying! Date: Thu Feb 16 16:05:14 2017 ErrorMessage: sub-processo novo script pre-removal retornou estado de saída de erro 1 InstallationDate: Installed on 2016-12-31 (47 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lpstat: device for Deskjet-2050-J510-series: hp:/usb/Deskjet_2050_J510_series?serial=BR1C1FK1K005D1 MachineType: LENOVO 80UG Papersize: a4 PpdFiles: Deskjet-2050-J510-series: HP Deskjet 2050 j510 Series, hpcups 3.16.3 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.9.10-040910-generic root=UUID=0fbb0f28-6764-4447-a890-dc966d1f8adf ro ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.10-040910-generic root=UUID=0fbb0f28-6764-4447-a890-dc966d1f8adf ro RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: sub-processo novo script pre-removal retornou estado de saída de erro 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN37WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.modalias: dmi:bvnLENOVO:bvr0XCN37WW:bd10/03/2016:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK: dmi.product.name: 80UG dmi.product.version: Lenovo ideapad 310-14ISK dmi.sys.vendor: LENOVO ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1665432 Title: Error with cups-daemon package when reinstalling many packages to recover wireless connection with QCA9377 Status in cups package in Ubuntu: New Bug description: I had a issue with my Wireless and Bluetooth card, Qualcomm Atheros Device [168c:0042] (rev 30), which appears on Windows 10 as QCA9377, and to solve it I have searched and tried different alternatives. The one that worked was to reinstall many packages, all the ones I have found when searching for, firstly, "wireless", then "wifi" and then "internet", on synaptic. When doing the "internet" reinstall, a error happened on cups-daemon and it crashed. When I tried again, it worked. I rebooted the computer and the Wireless is functioning again (Bluetooth was already OK). I am using the Kernel 4.9.10-040910-generic from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9.10/ because I was trying to solve this issue and because the official Kernles 4.4 and 4.8 don't eject external HDDs from the USB 3.0 correctly. The notebook model is Lenovo Ideapad 310-14ISK. While this window to report the bug appeared saying cups is the culprit, all this only happened because the wireless device QCA9377 was not working. usuario@usuario-Lenovo-ideapad-310-14ISK:~$ lsb_release -rd Description: Ubuntu 16.04.2 LTS Release: 16.04 usuario@usuario-Lenovo-ideapad-310-14ISK:~$ uname -a Linux usuario-Lenovo-ideapad-310-14ISK
