[Touch-packages] [Bug 1711087] Re: ad2p sink profile mic not available
As you can see there are no recording devices present. ** Attachment added: "ad2p sink; no input devices.png" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1711087/+attachment/5025541/+files/ad2p%20sink%3B%20no%20input%20devices.png -- 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/1711087 Title: ad2p sink profile mic not available Status in pulseaudio package in Ubuntu: New Bug description: I have a bose soundsport bluetooth headset. When I select the ad2p sink profile there is no microphone available. Only with the HSP profile my microphone is available. It's really annoying to have to switch between profiles to make a call or to listen to normal quality music. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jeroen 3801 F pulseaudio /dev/snd/controlC0: jeroen 3801 F pulseaudio CurrentDesktop: KDE Date: Wed Aug 16 11:02:37 2017 InstallationDate: Installed on 2017-05-10 (98 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1773IMS.106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1773 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.B dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1773IMS.106:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS702QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1773:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.name: GS70 2QE dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1711087/+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 1711087] Re: ad2p sink profile mic not available
When I select the ad2p source/sink profile the mic won't work anywhere. ** Attachment added: "bluetooth profile selection screen" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1711087/+attachment/5025540/+files/ad2p%20sink%20profile.png -- 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/1711087 Title: ad2p sink profile mic not available Status in pulseaudio package in Ubuntu: New Bug description: I have a bose soundsport bluetooth headset. When I select the ad2p sink profile there is no microphone available. Only with the HSP profile my microphone is available. It's really annoying to have to switch between profiles to make a call or to listen to normal quality music. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jeroen 3801 F pulseaudio /dev/snd/controlC0: jeroen 3801 F pulseaudio CurrentDesktop: KDE Date: Wed Aug 16 11:02:37 2017 InstallationDate: Installed on 2017-05-10 (98 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1773IMS.106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1773 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.B dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1773IMS.106:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS702QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1773:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.name: GS70 2QE dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1711087/+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 1711087] Re: ad2p sink profile mic not available
However if I select the HSP/HPF profile, it is. However with very low quality audio. The strange thing that if I switch back to the AD2p Source profile. The microphone is available. I've tested this using Skype version 8.11.0.4 ** Attachment added: "HSP,HPF profile; bose input devices present.png" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1711087/+attachment/5025542/+files/HSP%2CHPF%20profile%3B%20bose%20input%20devices%20present.png ** Changed in: pulseaudio (Ubuntu) Status: Invalid => New -- 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/1711087 Title: ad2p sink profile mic not available Status in pulseaudio package in Ubuntu: New Bug description: I have a bose soundsport bluetooth headset. When I select the ad2p sink profile there is no microphone available. Only with the HSP profile my microphone is available. It's really annoying to have to switch between profiles to make a call or to listen to normal quality music. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jeroen 3801 F pulseaudio /dev/snd/controlC0: jeroen 3801 F pulseaudio CurrentDesktop: KDE Date: Wed Aug 16 11:02:37 2017 InstallationDate: Installed on 2017-05-10 (98 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1773IMS.106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1773 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.B dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1773IMS.106:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS702QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1773:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.name: GS70 2QE dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1711087/+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 1711087] Re: ad2p sink profile mic not available
It keeps the high quality. -- 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/1711087 Title: ad2p sink profile mic not available Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have a bose soundsport bluetooth headset. When I select the ad2p sink profile there is no microphone available. Only with the HSP profile my microphone is available. It's really annoying to have to switch between profiles to make a call or to listen to normal quality music. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jeroen 3801 F pulseaudio /dev/snd/controlC0: jeroen 3801 F pulseaudio CurrentDesktop: KDE Date: Wed Aug 16 11:02:37 2017 InstallationDate: Installed on 2017-05-10 (98 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1773IMS.106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1773 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.B dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1773IMS.106:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS702QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1773:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.name: GS70 2QE dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1711087/+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 1711087] Re: ad2p sink profile mic not available
*** This bug is a duplicate of bug 508522 *** https://bugs.launchpad.net/bugs/508522 Actually it's a duplicate of a bug that has been fixed before (with high priority). ** This bug has been marked a duplicate of bug 508522 Mic is not available with A2DP Bluetooth profile -- 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/1711087 Title: ad2p sink profile mic not available Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have a bose soundsport bluetooth headset. When I select the ad2p sink profile there is no microphone available. Only with the HSP profile my microphone is available. It's really annoying to have to switch between profiles to make a call or to listen to normal quality music. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jeroen 3801 F pulseaudio /dev/snd/controlC0: jeroen 3801 F pulseaudio CurrentDesktop: KDE Date: Wed Aug 16 11:02:37 2017 InstallationDate: Installed on 2017-05-10 (98 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1773IMS.106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1773 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.B dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1773IMS.106:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS702QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1773:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.name: GS70 2QE dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1711087/+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 1711087] Re: ad2p sink profile mic not available
*** This bug is a duplicate of bug 508522 *** https://bugs.launchpad.net/bugs/508522 It seems like PulseAudio can handle ad2p correctly but maybe the audio configuration is not using the right parameters to initialize the sound system. I'm a Java developer. I'm willing to take a look at the source code but it would take me some time to get started. I have no Linux developer experience. -- 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/1711087 Title: ad2p sink profile mic not available Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have a bose soundsport bluetooth headset. When I select the ad2p sink profile there is no microphone available. Only with the HSP profile my microphone is available. It's really annoying to have to switch between profiles to make a call or to listen to normal quality music. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jeroen 3801 F pulseaudio /dev/snd/controlC0: jeroen 3801 F pulseaudio CurrentDesktop: KDE Date: Wed Aug 16 11:02:37 2017 InstallationDate: Installed on 2017-05-10 (98 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1773IMS.106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1773 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.B dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1773IMS.106:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS702QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1773:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.name: GS70 2QE dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1711087/+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 1711087] Re: ad2p sink profile mic not available
*** This bug is a duplicate of bug 508522 *** https://bugs.launchpad.net/bugs/508522 Can you maybe re-open bug 508522? It will ensure that this issue get's the priority it deserves. -- 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/1711087 Title: ad2p sink profile mic not available Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have a bose soundsport bluetooth headset. When I select the ad2p sink profile there is no microphone available. Only with the HSP profile my microphone is available. It's really annoying to have to switch between profiles to make a call or to listen to normal quality music. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jeroen 3801 F pulseaudio /dev/snd/controlC0: jeroen 3801 F pulseaudio CurrentDesktop: KDE Date: Wed Aug 16 11:02:37 2017 InstallationDate: Installed on 2017-05-10 (98 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1773IMS.106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1773 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.B dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1773IMS.106:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS702QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1773:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.name: GS70 2QE dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1711087/+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 1711087] Re: ad2p sink profile mic not available
*re-open #508522 -- 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/1711087 Title: ad2p sink profile mic not available Status in pulseaudio package in Ubuntu: Invalid Bug description: I have a bose soundsport bluetooth headset. When I select the ad2p sink profile there is no microphone available. Only with the HSP profile my microphone is available. It's really annoying to have to switch between profiles to make a call or to listen to normal quality music. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jeroen 3801 F pulseaudio /dev/snd/controlC0: jeroen 3801 F pulseaudio CurrentDesktop: KDE Date: Wed Aug 16 11:02:37 2017 InstallationDate: Installed on 2017-05-10 (98 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1773IMS.106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1773 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.B dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1773IMS.106:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS702QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1773:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.name: GS70 2QE dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1711087/+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 1711087] Re: ad2p sink profile mic not available
Yes, this is a duplicate of bug #508522. IMHO I think that we should close this issue and re-open bug #508533. -- 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/1711087 Title: ad2p sink profile mic not available Status in pulseaudio package in Ubuntu: Invalid Bug description: I have a bose soundsport bluetooth headset. When I select the ad2p sink profile there is no microphone available. Only with the HSP profile my microphone is available. It's really annoying to have to switch between profiles to make a call or to listen to normal quality music. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jeroen 3801 F pulseaudio /dev/snd/controlC0: jeroen 3801 F pulseaudio CurrentDesktop: KDE Date: Wed Aug 16 11:02:37 2017 InstallationDate: Installed on 2017-05-10 (98 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1773IMS.106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1773 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.B dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1773IMS.106:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS702QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1773:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.name: GS70 2QE dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1711087/+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 508522] Re: Mic is not available with A2DP Bluetooth profile
I'm on kubuntu 17.04 with pulseaudio 10.0, I'm still having this issue. Is this a kubuntu only issue? -- 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/508522 Title: Mic is not available with A2DP Bluetooth profile Status in pulseaudio package in Ubuntu: Fix Released Bug description: Binary package hint: pulseaudio I'm testing a Nokia BH-905i headset (see http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The Bluetooth module correctly identifies the headset and the both audio profiles "HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music playback only A2DP is suitable (HSP/HFP sounds like listening to music played through an old telephone). A2DP does not have an INPUT mode, so use of the headset for VoiP isn't possible. What would be needed is a separate selection to allow to select A2DP for output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do that (or they switch on the fly?). Formal structure: 1) Ubuntu 10.10 2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1 consisting og pluseaudio, pulseaudio-esound-compat, pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, pulseaudio-utils 3) Select high quality audio output and still use the Bluetooth microphone 4) Had to choose: either high quality audio or "telephone quality" with microphone I can change the profile without the Bluetooth connection dropping, but that's ridiculous. E.g. listening to music, a call comes in. Then I would need to switch the profile before answering. Please note that in Windows, Mac OS, iOS, Android, and Windows Mobile it's done automatically. Check out attached screencast. ProblemType: Bug AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oivasyuv 2309 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17' Mixer name : 'Analog Devices AD1984A' Components : 'HDA:11d4194a,103c30e8,00100400' Controls : 22 Simple ctrls : 14 Date: Sat Jan 16 22:31:41 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) Package: pulseaudio 1:0.9.19-0ubuntu4 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae SourcePackage: pulseaudio Uname: Linux 2.6.31-17-generic-pae i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/508522/+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 1711087] [NEW] ad2p sink profile mic not available
Public bug reported: I have a bose soundsport bluetooth headset. When I select the ad2p sink profile there is no microphone available. Only with the HSP profile my microphone is available. It's really annoying to have to switch between profiles to make a call or to listen to normal quality music. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jeroen 3801 F pulseaudio /dev/snd/controlC0: jeroen 3801 F pulseaudio CurrentDesktop: KDE Date: Wed Aug 16 11:02:37 2017 InstallationDate: Installed on 2017-05-10 (98 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1773IMS.106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1773 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.B dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1773IMS.106:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS702QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1773:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.name: GS70 2QE dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- 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/1711087 Title: ad2p sink profile mic not available Status in pulseaudio package in Ubuntu: New Bug description: I have a bose soundsport bluetooth headset. When I select the ad2p sink profile there is no microphone available. Only with the HSP profile my microphone is available. It's really annoying to have to switch between profiles to make a call or to listen to normal quality music. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jeroen 3801 F pulseaudio /dev/snd/controlC0: jeroen 3801 F pulseaudio CurrentDesktop: KDE Date: Wed Aug 16 11:02:37 2017 InstallationDate: Installed on 2017-05-10 (98 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1773IMS.106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1773 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.B dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1773IMS.106:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS702QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1773:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.name: GS70 2QE dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1711087/+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 508522] Re: Mic is not available with A2DP Bluetooth profile
I've created a new bug report to provide more information: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1711087 -- 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/508522 Title: Mic is not available with A2DP Bluetooth profile Status in pulseaudio package in Ubuntu: Fix Released Bug description: Binary package hint: pulseaudio I'm testing a Nokia BH-905i headset (see http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The Bluetooth module correctly identifies the headset and the both audio profiles "HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music playback only A2DP is suitable (HSP/HFP sounds like listening to music played through an old telephone). A2DP does not have an INPUT mode, so use of the headset for VoiP isn't possible. What would be needed is a separate selection to allow to select A2DP for output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do that (or they switch on the fly?). Formal structure: 1) Ubuntu 10.10 2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1 consisting og pluseaudio, pulseaudio-esound-compat, pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, pulseaudio-utils 3) Select high quality audio output and still use the Bluetooth microphone 4) Had to choose: either high quality audio or "telephone quality" with microphone I can change the profile without the Bluetooth connection dropping, but that's ridiculous. E.g. listening to music, a call comes in. Then I would need to switch the profile before answering. Please note that in Windows, Mac OS, iOS, Android, and Windows Mobile it's done automatically. Check out attached screencast. ProblemType: Bug AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oivasyuv 2309 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17' Mixer name : 'Analog Devices AD1984A' Components : 'HDA:11d4194a,103c30e8,00100400' Controls : 22 Simple ctrls : 14 Date: Sat Jan 16 22:31:41 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) Package: pulseaudio 1:0.9.19-0ubuntu4 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae SourcePackage: pulseaudio Uname: Linux 2.6.31-17-generic-pae i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/508522/+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 1711087] Re: ad2p sink profile mic not available
Then why is it that it works perfectly in android? -- 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/1711087 Title: ad2p sink profile mic not available Status in pulseaudio package in Ubuntu: Invalid Bug description: I have a bose soundsport bluetooth headset. When I select the ad2p sink profile there is no microphone available. Only with the HSP profile my microphone is available. It's really annoying to have to switch between profiles to make a call or to listen to normal quality music. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jeroen 3801 F pulseaudio /dev/snd/controlC0: jeroen 3801 F pulseaudio CurrentDesktop: KDE Date: Wed Aug 16 11:02:37 2017 InstallationDate: Installed on 2017-05-10 (98 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1773IMS.106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1773 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.B dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1773IMS.106:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS702QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1773:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.name: GS70 2QE dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1711087/+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 1711087] Re: ad2p sink profile mic not available
not a bug but a feature then lol? -- 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/1711087 Title: ad2p sink profile mic not available Status in pulseaudio package in Ubuntu: Invalid Bug description: I have a bose soundsport bluetooth headset. When I select the ad2p sink profile there is no microphone available. Only with the HSP profile my microphone is available. It's really annoying to have to switch between profiles to make a call or to listen to normal quality music. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jeroen 3801 F pulseaudio /dev/snd/controlC0: jeroen 3801 F pulseaudio CurrentDesktop: KDE Date: Wed Aug 16 11:02:37 2017 InstallationDate: Installed on 2017-05-10 (98 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1773IMS.106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1773 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.B dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1773IMS.106:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS702QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1773:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.name: GS70 2QE dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1711087/+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 1711087] Re: ad2p sink profile mic not available
PS Sorry I didn't mean to be disrespectful, I love (K)ubuntu, it has been my main operating system for a decade now. Just a bit disappointed that the relatively new android operating system is more mature here. I will provide more info later. Thanks for the help so far. -- 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/1711087 Title: ad2p sink profile mic not available Status in pulseaudio package in Ubuntu: Invalid Bug description: I have a bose soundsport bluetooth headset. When I select the ad2p sink profile there is no microphone available. Only with the HSP profile my microphone is available. It's really annoying to have to switch between profiles to make a call or to listen to normal quality music. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jeroen 3801 F pulseaudio /dev/snd/controlC0: jeroen 3801 F pulseaudio CurrentDesktop: KDE Date: Wed Aug 16 11:02:37 2017 InstallationDate: Installed on 2017-05-10 (98 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1773IMS.106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1773 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.B dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1773IMS.106:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGS702QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1773:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.name: GS70 2QE dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1711087/+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 433231] Re: xorg: directory "/usr/share/fonts/X11/cyrillic" does not exist.
sudo apt-get install xfonts-cyrillic fixed it on ubuntu 18.04 ** Changed in: xorg (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/433231 Title: xorg: directory "/usr/share/fonts/X11/cyrillic" does not exist. Status in X.Org X server: Invalid Status in xorg package in Ubuntu: New Bug description: Hello, I run on Kubuntu Karmic 64, 2.6.31-10-genericx86 64 In my log are this error: Avertissement The directory "/usr/share/fonts/X11/cyrillic" does not exist. [lspci] 01:00.0 VGA compatible controller [0300]: nVidia Corporation G92 [GeForce 9800 GTX] [10de:0612] (rev a2) Subsystem: ASUSTeK Computer Inc. Device [1043:82a6] To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/433231/+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 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space
Like #84, I ran into this issue after only a few weeks of running a standard Ubuntu installation with full disk encryption. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/798414 Title: update-initramfs should produce a more helpful error when there isn't enough free space Status in initramfs-tools: Confirmed Status in initramfs-tools package in Ubuntu: Triaged Bug description: Binary package hint: initramfs-tools When generating a new initramfs there is no check for available free space, subsequently its possible for update-initramfs to fail due to a lack of free space. This is resulting in package installation failures for initramfs-tools. For example: Setting up initramfs-tools (0.98.8ubuntu3) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 WORKAROUND: Remove unused kernels using computer janitor (not in repositories for 14.04 or later) or manually free space on your partition containing the /boot file system. To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/798414/+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 1958267] Re: wpa can't connect to servers using TLS 1.1 or older
I enabled propsed and updated wpasupplicant to 2:2.10-6ubuntu2 and I'm now able to connect to the corporate WiFi network again. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: wpa can't connect to servers using TLS 1.1 or older Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Jammy: Fix Committed Status in wpa package in Debian: New Bug description: * Impact wpa built with in openssl3 fails to connect to TLS 1.1 or lower server * Test case try to connect to a TLS <= 1.1 access point * Regression potential the patch lowers the security level in some situation for compatibility, it shouldn't prevent connecting to newer hardware, still try to connect to different type of wifi with different security levels --- those uses MD5-SHA1 as digest in its signature algorithm which no longer meets OpenSSL default level of security of 80 bits http://lists.infradead.org/pipermail/hostap/2022-May/040563.html Workaround are described in #22 and #36 by basically using CipherString = DEFAULT@SECLEVEL=0 which lowers the security level --- With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1851833] [NEW] Unable to adjust brightness of backlight
Public bug reported: I am unable to adjust the brightness of the backlight of my laptop screen either by using the slider of by changing the value in /sys/class/backlight/intel_backlight/brightness directly. I have tried changing my GRUB configuration: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor" But that did not help. I am using Ubuntu 19.10 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Nov 8 14:03:33 2019 DistUpgraded: 2019-10-09 11:42:34,460 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-19-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer UHD Graphics 630 (Mobile) [1558:65d1] NVIDIA Corporation TU106M [GeForce RTX 2070 Mobile] [10de:1f10] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer TU106M [GeForce RTX 2070 Mobile] [1558:65d1] InstallationDate: Installed on 2019-10-09 (30 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Notebook PB50_70RF,RD,RC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-10-09 (30 days ago) dmi.bios.date: 02/01/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.07 dmi.board.asset.tag: Tag 12345 dmi.board.name: PB50_70RF,RD,RC dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.07:bd02/01/2019:svnNotebook:pnPB50_70RF,RD,RC:pvrNotApplicable:rvnNotebook:rnPB50_70RF,RD,RC:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: PB50_70RF,RD,RC dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1851833 Title: Unable to adjust brightness of backlight Status in xorg package in Ubuntu: New Bug description: I am unable to adjust the brightness of the backlight of my laptop screen either by using the slider of by changing the value in /sys/class/backlight/intel_backlight/brightness directly. I have tried changing my GRUB configuration: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor" But that did not help. I am using Ubuntu 19.10 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module
[Touch-packages] [Bug 1792790] [NEW] mismatch on package
Public bug reported: LANG=C; sudo apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following packages were automatically installed and are no longer required: linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-image-4.15.0-32-generic linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: libnvidia-gl-390 libnvidia-gl-390:i386 The following NEW packages will be installed: libnvidia-gl-390 libnvidia-gl-390:i386 0 upgraded, 2 newly installed, 0 to remove and 4 not upgraded. 3 not fully installed or removed. Need to get 0 B/29.1 MB of archives. After this operation, 147 MB of additional disk space will be used. Do you want to continue? [Y/n] y (Reading database ... 256831 files and directories currently installed.) Preparing to unpack .../libnvidia-gl-390_390.48-0ubuntu3_i386.deb ... diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to /usr/lib/i386-linux-gnu/libGL.so.1.distrib by nvidia-340 dpkg-divert: error: mismatch on package when removing 'diversion of /usr/lib/i386-linux-gnu/libGL.so.1 by libnvidia-gl-390' found 'diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to /usr/lib/i386-linux-gnu/libGL.so.1.distrib by nvidia-340' dpkg: error processing archive /var/cache/apt/archives/libnvidia-gl-390_390.48-0ubuntu3_i386.deb (--unpack): new libnvidia-gl-390:i386 package pre-installation script subprocess returned error exit status 2 Preparing to unpack .../libnvidia-gl-390_390.48-0ubuntu3_amd64.deb ... diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 to /usr/lib/x86_64-linux-gnu/libGL.so.1.distrib by nvidia-340 dpkg-divert: error: mismatch on package when removing 'diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 by libnvidia-gl-390' found 'diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 to /usr/lib/x86_64-linux-gnu/libGL.so.1.distrib by nvidia-340' dpkg: error processing archive /var/cache/apt/archives/libnvidia-gl-390_390.48-0ubuntu3_amd64.deb (--unpack): new libnvidia-gl-390:amd64 package pre-installation script subprocess returned error exit status 2 Errors were encountered while processing: /var/cache/apt/archives/libnvidia-gl-390_390.48-0ubuntu3_i386.deb /var/cache/apt/archives/libnvidia-gl-390_390.48-0ubuntu3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1792790 Title: mismatch on package Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: LANG=C; sudo apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following packages were automatically installed and are no longer required: linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-image-4.15.0-32-generic linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: libnvidia-gl-390 libnvidia-gl-390:i386 The following NEW packages will be installed: libnvidia-gl-390 libnvidia-gl-390:i386 0 upgraded, 2 newly installed, 0 to remove and 4 not upgraded. 3 not fully installed or removed. Need to get 0 B/29.1 MB of archives. After this operation, 147 MB of additional disk space will be used. Do you want to continue? [Y/n] y (Reading database ... 256831 files and directories currently installed.) Preparing to unpack .../libnvidia-gl-390_390.48-0ubuntu3_i386.deb ... diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to /usr/lib/i386-linux-gnu/libGL.so.1.distrib by nvidia-340 dpkg-divert: error: mismatch on package when removing 'diversion of /usr/lib/i386-linux-gnu/libGL.so.1 by libnvidia-gl-390' found 'diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to /usr/lib/i386-linux-gnu/libGL.so.1.distrib by nvidia-340' dpkg: error processing archive /var/cache/apt/archives/libnvidia-gl-390_390.48-0ubuntu3_i386.deb (--unpack): new libnvidia-gl-390:i386 package pre-installation script subprocess returned error exit status 2 Preparing to unpack .../libnvidia-gl-390_390.48-0ubuntu3_amd64.deb ... diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 to /usr/lib/x86_64-linux-gnu/libGL.so.1.distrib by nvidia-340 dpkg-divert: error: mismatch on package when removing 'diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 by libnvidia-gl-390' found 'diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 to /usr/lib/x86_64-linux-gnu/libGL.so.1.distrib by nvidia-340' dpkg: error processing archive /var/cache/apt/archives/libnvidia-gl-390
[Touch-packages] [Bug 1792790] Re: mismatch on package
What to do next, I cannot update my desktop. ** Also affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** No longer affects: apport (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1792790 Title: mismatch on package Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: LANG=C; sudo apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following packages were automatically installed and are no longer required: linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-image-4.15.0-32-generic linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: libnvidia-gl-390 libnvidia-gl-390:i386 The following NEW packages will be installed: libnvidia-gl-390 libnvidia-gl-390:i386 0 upgraded, 2 newly installed, 0 to remove and 4 not upgraded. 3 not fully installed or removed. Need to get 0 B/29.1 MB of archives. After this operation, 147 MB of additional disk space will be used. Do you want to continue? [Y/n] y (Reading database ... 256831 files and directories currently installed.) Preparing to unpack .../libnvidia-gl-390_390.48-0ubuntu3_i386.deb ... diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to /usr/lib/i386-linux-gnu/libGL.so.1.distrib by nvidia-340 dpkg-divert: error: mismatch on package when removing 'diversion of /usr/lib/i386-linux-gnu/libGL.so.1 by libnvidia-gl-390' found 'diversion of /usr/lib/i386-linux-gnu/libGL.so.1 to /usr/lib/i386-linux-gnu/libGL.so.1.distrib by nvidia-340' dpkg: error processing archive /var/cache/apt/archives/libnvidia-gl-390_390.48-0ubuntu3_i386.deb (--unpack): new libnvidia-gl-390:i386 package pre-installation script subprocess returned error exit status 2 Preparing to unpack .../libnvidia-gl-390_390.48-0ubuntu3_amd64.deb ... diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 to /usr/lib/x86_64-linux-gnu/libGL.so.1.distrib by nvidia-340 dpkg-divert: error: mismatch on package when removing 'diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 by libnvidia-gl-390' found 'diversion of /usr/lib/x86_64-linux-gnu/libGL.so.1 to /usr/lib/x86_64-linux-gnu/libGL.so.1.distrib by nvidia-340' dpkg: error processing archive /var/cache/apt/archives/libnvidia-gl-390_390.48-0ubuntu3_amd64.deb (--unpack): new libnvidia-gl-390:amd64 package pre-installation script subprocess returned error exit status 2 Errors were encountered while processing: /var/cache/apt/archives/libnvidia-gl-390_390.48-0ubuntu3_i386.deb /var/cache/apt/archives/libnvidia-gl-390_390.48-0ubuntu3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1792790/+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 1726124] Re: DNS domain search paths not updated when VPN started
I hope something can be worked out before this lands in the next LTS- release. This breaks one of the most common uses of a VPN (remote work). Right now a workaround is using this script after connecting to a VPN- server: https://github.com/jonathanio/update-systemd-resolved It calls systemd-resolved via DBus to add the proper settings after the OpenVPN connection is established. Of course this means abandoning NetworkManager for use with OpenVPN, because there is also no way to specify --up and --down parameters. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1726124 Title: DNS domain search paths not updated when VPN started Status in network-manager package in Ubuntu: Confirmed Status in network-manager-openvpn package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I connect to work with openvpn through network-manager-openvpn. I'm selecting automatic (DHCP) to get an IP address, and "Use this connection only for resources on its network" to support split tunneling. In the last few versions of Ubuntu I used, this all worked fine. In Ubuntu 17.10 (fresh install, not upgrade) I can access hosts on both my VPN network and the internet, BUT I have to use FQDN for my VPN network hosts: the updates to the DNS search path provided by my VPN DHCP server are never being applied. Investigating the system I see that /etc/resolv.conf is pointing to /run/systemd/resolve/stub-resolv.conf and that resolv.conf does not have any of the VPN's search path settings in it: # This file is managed by man:systemd-resolved(8). Do not edit. # # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search home In previous versions of Ubuntu, where NetworkManager controlled the resolver not systemd, /etc/resolv.conf pointed to /run/NetworkManager/resolv.conf and there was a local dnsmasq instance that managed all the complexity. In Ubuntu 17.10 when I look in /run/NetworkManager/resolv.conf file, I see that the search paths ARE properly updated there: $ cat /run/NetworkManager/resolv.conf # Generated by NetworkManager search internal.mycorp.com other.mycorp.com home nameserver 127.0.1.1 However this file isn't being used, and also there's no dnsmasq running on the system so if I switch my /etc/resolv.conf to point to this file instead, then all lookups fail. Strangely, if I look at the systemd-resolv status I see that in theory systemd-resolve does seem to know about the proper search paths: $ systemd-resolve --status ... Link 3 (tun0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 10.3.0.10 10.8.42.2 DNS Domain: ~internal.mycorp.com ~other.mycorp.com but for whatever reason the search domains are not getting put into the resolv.conf file: $ host mydesk ;; connection timed out; no servers could be reached $ host mydesk.internal.mycorp.com mydesk.internal.mycorp.com has address 10.8.37.74 (BTW, the timeout in the failed attempt above takes 10s: it is SUPER frustrating when all your host lookups are taking that long just to fail). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 22 15:08:57 2017 InstallationDate: Installed on 2017-10-21 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi
[Touch-packages] [Bug 1516153] [NEW] Wifi does not work after suspending.
Public bug reported: After resuming from a suspend, sometimes(very often) the wifi does not show any connections. Even if i uncheck and recheck the Enable wifi checkbox it still does not show any connections. I am using Ubuntu 15.10. NetworkManager is at version 1.0.4. My hardware is a Asus X750J. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 Date: Fri Nov 13 22:07:24 2015 ExecutablePath: /usr/sbin/NetworkManager IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-10-27 (17 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp3s0 ethernet connected /org/freedesktop/NetworkManager/Devices/0 Wired connection 1 a6283be3-2692-4d49-87d6-4c2f7cf00e2f /org/freedesktop/NetworkManager/ActiveConnection/4 tun0tun connected /org/freedesktop/NetworkManager/Devices/3 tun08a335ba2-ebce-4e08-9431-d8a4322cfa26 /org/freedesktop/NetworkManager/ActiveConnection/5 wlp2s0 wifi disconnected /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1516153 Title: Wifi does not work after suspending. Status in network-manager package in Ubuntu: New Bug description: After resuming from a suspend, sometimes(very often) the wifi does not show any connections. Even if i uncheck and recheck the Enable wifi checkbox it still does not show any connections. I am using Ubuntu 15.10. NetworkManager is at version 1.0.4. My hardware is a Asus X750J. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 Date: Fri Nov 13 22:07:24 2015 ExecutablePath: /usr/sbin/NetworkManager IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-10-27 (17 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp3s0 ethernet connected /org/freedesktop/NetworkManager/Devices/0 Wired connection 1 a6283be3-2692-4d49-87d6-4c2f7cf00e2f /org/freedesktop/NetworkManager/ActiveConnection/4 tun0tun connected /org/freedesktop/NetworkManager/Devices/3 tun08a335ba2-ebce-4e08-9431-d8a4322cfa26 /org/freedesktop/NetworkManager/ActiveConnection/5 wlp2s0 wifi disconnected /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1516153/+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 1516153] Re: Wifi does not work after suspending.
** Description changed: After resuming from a suspend, sometimes(very often) the wifi does not show any connections. Even if i uncheck and recheck the Enable wifi checkbox it still does not show any connections. I am using Ubuntu 15.10. NetworkManager is at version 1.0.4. My hardware is a Asus X750J. + + A quick workaround is restarting the NetworkManager service. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 Date: Fri Nov 13 22:07:24 2015 ExecutablePath: /usr/sbin/NetworkManager IfupdownConfig: - # interfaces(5) file used by ifup(8) and ifdown(8) - auto lo - iface lo inet loopback + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback InstallationDate: Installed on 2015-10-27 (17 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) NetworkManager.state: - [main] - NetworkingEnabled=true - WirelessEnabled=true - WWANEnabled=true - WimaxEnabled=true + [main] + NetworkingEnabled=true + WirelessEnabled=true + WWANEnabled=true + WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: - DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH - enp3s0 ethernet connected /org/freedesktop/NetworkManager/Devices/0 Wired connection 1 a6283be3-2692-4d49-87d6-4c2f7cf00e2f /org/freedesktop/NetworkManager/ActiveConnection/4 - tun0tun connected /org/freedesktop/NetworkManager/Devices/3 tun08a335ba2-ebce-4e08-9431-d8a4322cfa26 /org/freedesktop/NetworkManager/ActiveConnection/5 - wlp2s0 wifi disconnected /org/freedesktop/NetworkManager/Devices/2 -- ---- - lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- + DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH + enp3s0 ethernet connected /org/freedesktop/NetworkManager/Devices/0 Wired connection 1 a6283be3-2692-4d49-87d6-4c2f7cf00e2f /org/freedesktop/NetworkManager/ActiveConnection/4 + tun0tun connected /org/freedesktop/NetworkManager/Devices/3 tun08a335ba2-ebce-4e08-9431-d8a4322cfa26 /org/freedesktop/NetworkManager/ActiveConnection/5 + wlp2s0 wifi disconnected /org/freedesktop/NetworkManager/Devices/2 -- ---- + lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1516153 Title: Wifi does not work after suspending. Status in network-manager package in Ubuntu: New Bug description: After resuming from a suspend, sometimes(very often) the wifi does not show any connections. Even if i uncheck and recheck the Enable wifi checkbox it still does not show any connections. I am using Ubuntu 15.10. NetworkManager is at version 1.0.4. My hardware is a Asus X750J. A quick workaround is restarting the NetworkManager service. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 Date: Fri Nov 13 22:07:24 2015 ExecutablePath: /usr/sbin/NetworkManager IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-10-27 (17 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp3s0 ethernet connected /org/freedesktop/NetworkManager/Devices/0 Wired connection 1 a6283be3-2692-4d49-87d6-4c2f7cf00e2f /org/freedesktop/NetworkManager/Acti
[Touch-packages] [Bug 1665893] Re: DNS resolution of VPN hosts stopped working
*** This bug is a duplicate of bug 1667825 *** https://bugs.launchpad.net/bugs/1667825 I am running into DNS issues with OpenVPN as well. When connected `dig ddg.gg` fails, but `dig ddg.gg @8.8.8.8` works. This started after running updates yesterday. I can't tell if bug #1667825 is the same issue, but I get the same problem regardless of whether I start OpenVPN from the command line or via the Network-Manager. (I'm not sure if the latter makes the connection 'managed' or not.) Can this issue be scaled up in importance if confirmed? Users not being able to use a VPN service (e.g., in a place with free public wifi) is a huge security risk! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1665893 Title: DNS resolution of VPN hosts stopped working Status in dnsmasq package in Ubuntu: Confirmed Bug description: I have been using 17.04 for a few weeks now, but a recent update seems to have broken DNS resolution for VPN hosts. The local network is 192.168.50.*, with DNS at 192.168.50.2. The remote network is 192.168.0.*, with DNS at 192.168.0.2. I can ping remote hosts, but I can't resolve their names, although syslog says the following: systemd-resolved[2865]: Switching to DNS server 192.168.0.2 for interface tun0. The remote DNS domain is ozone.caligrafix.cl. Here is what does and doesn't work, using a valid remote host name (cali00): dig cali00: fails dig cali00.ozone.caligrafix.cl: fails dig cali00 @192.168.0.2: works dig cali00.ozone.caligrafix.cl @192.168.0.2: works Here is the complete log of VPN connection setup: Feb 18 11:56:34 tadzim3 NetworkManager[2242]: [1487429794.9928] audit: op="connection-activate" uuid="ae3693ea-df59-414e-95a8-bf280a65b8db" name="cali-fw" pid=4439 uid=1000 result="success" Feb 18 11:56:34 tadzim3 NetworkManager[2242]: [1487429794.9976] vpn-connection[0x5622aa56c370,ae3693ea-df59-414e-95a8-bf280a65b8db,"cali-fw",0]: Started the VPN service, PID 7173 Feb 18 11:56:35 tadzim3 NetworkManager[2242]: [1487429795.0048] vpn-connection[0x5622aa56c370,ae3693ea-df59-414e-95a8-bf280a65b8db,"cali-fw",0]: Saw the service appear; activating connection Feb 18 11:56:35 tadzim3 NetworkManager[2242]: [1487429795.1165] vpn-connection[0x5622aa56c370,ae3693ea-df59-414e-95a8-bf280a65b8db,"cali-fw",0]: VPN plugin: state changed: starting (3) Feb 18 11:56:35 tadzim3 NetworkManager[2242]: [1487429795.1170] vpn-connection[0x5622aa56c370,ae3693ea-df59-414e-95a8-bf280a65b8db,"cali-fw",0]: VPN connection: (ConnectInteractive) reply received Feb 18 11:56:35 tadzim3 nm-openvpn[7180]: OpenVPN 2.4.0 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Feb 10 2017 Feb 18 11:56:35 tadzim3 nm-openvpn[7180]: library versions: OpenSSL 1.0.2g 1 Mar 2016, LZO 2.08 Feb 18 11:56:35 tadzim3 nm-openvpn[7180]: WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info. Feb 18 11:56:35 tadzim3 nm-openvpn[7180]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts Feb 18 11:56:35 tadzim3 nm-openvpn[7180]: TCP/UDP: Preserving recently used remote address: [AF_INET]186.103.161.74:25402 Feb 18 11:56:35 tadzim3 nm-openvpn[7180]: UDP link local: (not bound) Feb 18 11:56:35 tadzim3 nm-openvpn[7180]: UDP link remote: [AF_INET]186.103.161.74:25402 Feb 18 11:56:35 tadzim3 nm-openvpn[7180]: NOTE: chroot will be delayed because of --client, --pull, or --up-delay Feb 18 11:56:35 tadzim3 nm-openvpn[7180]: NOTE: UID/GID downgrade will be delayed because of --client, --pull, or --up-delay Feb 18 11:56:36 tadzim3 nm-openvpn[7180]: [cali-fw-vpn] Peer Connection Initiated with [AF_INET]186.103.161.74:25402 Feb 18 11:56:37 tadzim3 nm-openvpn[7180]: TUN/TAP device tun0 opened Feb 18 11:56:37 tadzim3 nm-openvpn[7180]: /usr/lib/NetworkManager/nm-openvpn-service-openvpn-helper --debug 0 7173 --bus-name org.freedesktop.NetworkManager.openvpn.Connection_6 --tun -- tun0 1500 1558 10.8.1.2 255.255.255.0 init Feb 18 11:56:37 tadzim3 NetworkManager[2242]: [1487429797.1267] manager: (tun0): new Tun device (/org/freedesktop/NetworkManager/Devices/7) Feb 18 11:56:37 tadzim3 NetworkManager[2242]: [1487429797.1368] devices added (path: /sys/devices/virtual/net/tun0, iface: tun0) Feb 18 11:56:37 tadzim3 NetworkManager[2242]: [1487429797.1368] device added (path: /sys/devices/virtual/net/tun0, iface: tun0): no ifupdown configuration found. Feb 18 11:56:37 tadzim3 NetworkManager[2242]: [1487429797.1443] vpn-connection[0x5622aa56c370,ae3693ea-df59-414e-95a8-bf280a65b8db,"cali-fw",0]: VPN connection: (IP Config Get) reply received. Feb 18 11:56:37 tadzim3 NetworkManager[2242]: [1487429797.1463] vpn-connection[0x5622aa56c370,ae3693ea-df59-414e-95a8-bf28
[Touch-packages] [Bug 1890190] [NEW] package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade: subproces van pakket initramfs-tools werd script post-installation geïnstalleerd gaf de foutwaard
Public bug reported: don't know ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.2 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Aug 3 20:34:56 2020 ErrorMessage: subproces van pakket initramfs-tools werd script post-installation geïnstalleerd gaf de foutwaarde 1 terug InstallationDate: Installed on 2014-03-02 (2346 days ago) InstallationMedia: Ubuntu-Server 12.04.4 LTS "Precise Pangolin" - Release amd64 (20140204) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade: subproces van pakket initramfs-tools werd script post-installation geïnstalleerd gaf de foutwaarde 1 terug UpgradeStatus: Upgraded to focal on 2020-08-03 (0 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1890190 Title: package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade: subproces van pakket initramfs-tools werd script post-installation geïnstalleerd gaf de foutwaarde 1 terug Status in initramfs-tools package in Ubuntu: New Bug description: don't know ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.2 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Aug 3 20:34:56 2020 ErrorMessage: subproces van pakket initramfs-tools werd script post-installation geïnstalleerd gaf de foutwaarde 1 terug InstallationDate: Installed on 2014-03-02 (2346 days ago) InstallationMedia: Ubuntu-Server 12.04.4 LTS "Precise Pangolin" - Release amd64 (20140204) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade: subproces van pakket initramfs-tools werd script post-installation geïnstalleerd gaf de foutwaarde 1 terug UpgradeStatus: Upgraded to focal on 2020-08-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1890190/+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 1607291] Re: Dual SIM devices show "No SIM" icon in indicators if there is only one SIM installed
If this becomes an option in 'custom tarball', does that mean I can access that option with the regular OTA updates? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1607291 Title: Dual SIM devices show "No SIM" icon in indicators if there is only one SIM installed Status in Canonical System Image: Confirmed Status in Ubuntu UX: New Status in indicator-network package in Ubuntu: Incomplete Bug description: rc-proposed, since about a week I have 2 SIM icons in the indicators panel. One that shows the signal strength for the installed SIM card (which is fine), and then a second one which shows the "no SIM card" icon. When there is a SIM card installed, the indicator should not show a "no SIM installed" icon, even though there would be a second free slot available. See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607291/+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 1587321] Re: Browser: Path component of URL is hidden by default
It is an understandable design decision, and from an aesthetic standpoint truncating the URL does make sense. My objection is twofold. One problem is that in my opinion truncating the URL limits the usability of the browser. Even though plenty of website do make a mess of anything behind the /, other websites and services do have understandable, bookmarkable URLs that aid the user in his or her browsing. Thankfully the URL is still a usable part of many websites, and modern Javasript frameworks too (traditionally the place where URLs were mangled for technical reasons) are now once again embracing proper and usable URLs (e.g., EmberJS). Philosophically, I worry about hiding something as empowering and basic to the web as the URL. While I can sympathise with the notion that the path, query, and fragment parts of a HTTP URL are often technical details that may clutter the UI and confuse some users, I feel that hiding it is not in the spirit of the open web, and does not benefit users in the long run. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1587321 Title: Browser: Path component of URL is hidden by default Status in Canonical System Image: Incomplete Status in Ubuntu UX: New Status in webbrowser-app package in Ubuntu: Confirmed Bug description: Current behaviour: In the web browser the URL gets truncated to just the (sub)domain part. For example, the URL of the 'report a bug' form on Launchpad is: https://bugs.launchpad.net/canonical-devices-system-image/+filebug What is displayed in the browser is: bugs.launchpad.net The rest of the URL won't show until you touch the address bar. This behaviour is problematic, because it hides one of the primary attributes of the open web. Expected behaviour: By default the URL should not be hidden. Because space is constrained on the typical devices this browser is used on, the protocol part can be omitted by default, as long as the typical lock icon is present for HTTPS URL (see attached image). So by default: bugs.launchpad.net/canonical-devices-system-image/+filebug On touch on the address bar: https://bugs.launchpad.net/canonical-devices-system-image/+filebug I would recommend following the standard behaviour of modern web browsers to emphasize the domain part of the URL in black (with the rest of the URL in grey) as well. Device: Meizu Pro 5 (OTA 10.2) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1587321/+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 1536307] Re: Unknown albums and unknown artists should not be shown
I have the same problem, but with a music collection that is actually quite well-tagged. For a lot of (pop) music the actual album something came from is irrelevant and undesirable to have tagged, because it clutters up the album view of (other) music players. When I am browsing albums, I expect to see only albums I own in their entirety, not 'albums' that contain only that one-off hit and miss all other tracks. The problem here is that any song that lacks the album tag, gets shown in the album view as a unique artist/album combination. Right now I have a thousand or so stand-alone tracks (starting with 10cc – Unknown Album and ending with ZZ Top – Unknown Album) to swipe-scroll through before I get to the real albums. This takes about two minutes, and has to be done every time you open the music app. Rather unworkable. I would suggest grouping all tracks that lack an album tag into a single 'Unknown Album' pseudo-album, regardless of artist. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to thumbnailer in Ubuntu. https://bugs.launchpad.net/bugs/1536307 Title: Unknown albums and unknown artists should not be shown Status in Ubuntu Music App: New Status in thumbnailer package in Ubuntu: Triaged Bug description: Unpack the attached archive into the Music folder and wait for mediascanner to finish indexing (takes a few minutes). Now look at the album tab in the music app. There are hundreds of unknown albums at the beginning of the list. The attached music collection has a lot of poorly tagged songs in it (just like many users' collections will have imperfectly tagged songs). There are lots of songs with an empty album tag. (Such songs are legit too because I might add, say, audio recordings of a meeting or audio books to my collection.) The music app shows a separate "Unknown Album" for each and every song with an empty album tag. That's wrong. It should not show any album at all in this case because, by definition, a song with no album tag isn't part of any album--it's a stand-along song. (Note that collapsing all songs without an album tag into a single album not an option because it would conflate many unrelated tracks into a single album that doesn't exist.) This is how the mediascanner scope deals with empty albums; the music app should do the same thing. To manage notifications about this bug go to: https://bugs.launchpad.net/music-app/+bug/1536307/+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 1536307] Re: Unknown albums and unknown artists should not be shown
(Problem present in OTA-11) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to thumbnailer in Ubuntu. https://bugs.launchpad.net/bugs/1536307 Title: Unknown albums and unknown artists should not be shown Status in Ubuntu Music App: New Status in thumbnailer package in Ubuntu: Triaged Bug description: Unpack the attached archive into the Music folder and wait for mediascanner to finish indexing (takes a few minutes). Now look at the album tab in the music app. There are hundreds of unknown albums at the beginning of the list. The attached music collection has a lot of poorly tagged songs in it (just like many users' collections will have imperfectly tagged songs). There are lots of songs with an empty album tag. (Such songs are legit too because I might add, say, audio recordings of a meeting or audio books to my collection.) The music app shows a separate "Unknown Album" for each and every song with an empty album tag. That's wrong. It should not show any album at all in this case because, by definition, a song with no album tag isn't part of any album--it's a stand-along song. (Note that collapsing all songs without an album tag into a single album not an option because it would conflate many unrelated tracks into a single album that doesn't exist.) This is how the mediascanner scope deals with empty albums; the music app should do the same thing. To manage notifications about this bug go to: https://bugs.launchpad.net/music-app/+bug/1536307/+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 1536307] Re: Unknown albums and unknown artists should not be shown
Temporary workaround: In the album view, enter a single space in the search field. This seems to filter out all the 'Unknown Albums'. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to thumbnailer in Ubuntu. https://bugs.launchpad.net/bugs/1536307 Title: Unknown albums and unknown artists should not be shown Status in Ubuntu Music App: New Status in thumbnailer package in Ubuntu: Triaged Bug description: Unpack the attached archive into the Music folder and wait for mediascanner to finish indexing (takes a few minutes). Now look at the album tab in the music app. There are hundreds of unknown albums at the beginning of the list. The attached music collection has a lot of poorly tagged songs in it (just like many users' collections will have imperfectly tagged songs). There are lots of songs with an empty album tag. (Such songs are legit too because I might add, say, audio recordings of a meeting or audio books to my collection.) The music app shows a separate "Unknown Album" for each and every song with an empty album tag. That's wrong. It should not show any album at all in this case because, by definition, a song with no album tag isn't part of any album--it's a stand-along song. (Note that collapsing all songs without an album tag into a single album not an option because it would conflate many unrelated tracks into a single album that doesn't exist.) This is how the mediascanner scope deals with empty albums; the music app should do the same thing. To manage notifications about this bug go to: https://bugs.launchpad.net/music-app/+bug/1536307/+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 1592108] Re: No option to disable album/artist/track art requests
Do I understand correctly that the thumbnailer uses a remote service (7digital?) by default? >From a user's perspective I would expect to be able to reach this setting from the Music App, but if the use of this remote service is something that is done by the thumbnailer, I am not sure if adding it as an option to only the Music App is correct. If I understand correctly; from an engineering perspective the thumbnailer's job is to get the art, the Music App uses the art, but does not care how the thumbnailer got it. Perhaps this should be a system-wide setting under 'Security & Privacy' instead? I must admit that I am not wholly comfortable with the idea of a daemon (thumbnailer) contacting commercial third party resources without being able to turn it off. ** Summary changed: - No option to disable album/artist/track art requests + No option to disable remote album/artist/track art requests -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to thumbnailer in Ubuntu. https://bugs.launchpad.net/bugs/1592108 Title: No option to disable remote album/artist/track art requests Status in Ubuntu Music App: New Status in Ubuntu UX: New Status in thumbnailer package in Ubuntu: New Bug description: The Music App appears to download album/artist/track art automatically. Is there a way to disable this functionality to save bandwidth? The Music App does not appear to have any user settings at all (unless I am overlooking them). The service used to fetch the art from is far from bug-free. For an album called 'Musik für festliche Stunden' I get an album cover for 'Strauss zum Saubermachen'. While that does seem like an interesting album (clean the house with Strauss?) it is not even remotely the correct album. To manage notifications about this bug go to: https://bugs.launchpad.net/music-app/+bug/1592108/+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 1592108] Re: No option to disable remote album/artist/track art requests
Thanks for the in-depth reply. It is reassuring to hear that dash.ubuntu.com acts as a proxy. On a personal level I find this to be more tolerable than a direct interface with a commercial service I have no customer relation with. The data aspect alone is probably enough to warrant inclusion of a toggle for this feature, or perhaps an option to only download this kind of data when connected to wifi. That said, I politely disagree on the privacy aspect. Please indulge me — an avid Ubuntu user — in relating my personal view on this matter. >From a principled standpoint there are two things that would help in maintaining Ubuntu's reputation with regards to privacy. One is informed consent. It would like to be informed about what kind of data is being automatically transmitted to other parties. Perhaps via a page in the documentation that lists the various types of external connections that are being made on a stock release of Ubuntu Touch (and probably the normal Ubuntu OS). Is such a list available? One reason that I mention this is that the default behaviour of the dash in stock desktop Ubuntu used to be to search Amazon automatically with search terms entered. This has since been disabled by default, but did raise valid privacy concerns. I feel strongly that Ubuntu is the kind of OS where users are actively given a chance to influence the data they are broadcasting, especially in this age of mass surveillance and mass tracking. But to do that, users must be aware of what is happening and who they are communicating with. As you mention it makes quite a difference if artwork requests are done directly to 7digital or via Canonical's proxy. The second is perhaps an extension of that, and is simply to enable users to disable this kind of behaviour. Ideally users can disable third party communications like these (indirect) requests to 7digital at will from the Privacy and Security settings. I will admit that music artwork does seem lot less sensitive in terms of its privacy impact than general searches in the dash, but I feel strongly that this decision should be left with the user, especially for stock software included with the OS, and bundled services of the OS (e.g., the thumbnailer). A hypothetical case that comes to my mind is this. Consider Wikipedia's list of controversial album art¹. If I was visiting a country with strict laws regarding nudity and sexuality and an active policy of examining your personal electronic devices at the border (sadly, not unlikely these days) it would be unpleasant — at the very least — to have a Music App fetch the album covers for, say, Nirvana – Nevermind or The Scorpions – Virgin Killer (!). Needless to say that even if the music itself was allowed, possession of these kind of images is highly illegal in such jurisdictions, with punishments that are no laughing matter. If our hypothetical Scorpions- fan took care not to upload any music tagged with album covers to his device, he would still end up with those covers in plain view to any customs officer inspecting his phone or tablet. 1: https://en.wikipedia.org/wiki/List_of_controversial_album_art -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to thumbnailer in Ubuntu. https://bugs.launchpad.net/bugs/1592108 Title: No option to disable remote album/artist/track art requests Status in Ubuntu Music App: Invalid Status in Ubuntu UX: New Status in thumbnailer package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: New Bug description: The Music App appears to download album/artist/track art automatically. Is there a way to disable this functionality to save bandwidth? The Music App does not appear to have any user settings at all (unless I am overlooking them). The service used to fetch the art from is far from bug-free. For an album called 'Musik für festliche Stunden' I get an album cover for 'Strauss zum Saubermachen'. While that does seem like an interesting album (clean the house with Strauss?) it is not even remotely the correct album. To manage notifications about this bug go to: https://bugs.launchpad.net/music-app/+bug/1592108/+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 1455097] Re: /etc/pm/sleep.d/ is no more processed
On 2016-04-06 17:46, ChristianEhrhardt wrote: > I did the task of identifying the remaining packages that are affected. > > $ apt-file search /etc/pm/sleep.d/ > > aiccu: /etc/pm/sleep.d/60aiccu There has been a bug out for this for 4 years already that this should never ever have existed: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689584 Short version: please remove any kind of trace from /etc/pm/sleep.d for aiccu. That should take care of your bug report for aiccu at least. Greets, Jeroen ** Bug watch added: Debian Bug tracker #689584 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689584 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1455097 Title: /etc/pm/sleep.d/ is no more processed Status in aiccu package in Ubuntu: New Status in ceph package in Ubuntu: New Status in grub2 package in Ubuntu: New Status in ifplugd package in Ubuntu: New Status in lizardfs package in Ubuntu: New Status in oss4 package in Ubuntu: New Status in pm-utils package in Ubuntu: Won't Fix Status in toshset package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: New Bug description: I added a new script in /etc/pm/sleep.d/ that worked fine before the upgrade to vivid. I was wondering why it doesn't work and I find out that /var/log/pm-suspend.log is empty, and pm-powersave.log too (last logs from pm-suspend were on Apr 28, when I upgraded from utopic to vivid. The laptop suspends and wakes fine, it just seems that no pm scripts are run after suspend/powersave. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: pm-utils 1.4.1-15 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 14 15:36:26 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 EcryptfsInUse: Yes InstallationDate: Installed on 2013-03-12 (792 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08 PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1455097/+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 1446571] Re: Playlist is emptied by itself
on my bq aquaris 4.5 ubuntu edition We encouter the same problem since we updated last week. Greetings, Jeroen Vyncke -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediaplayer-app in Ubuntu. https://bugs.launchpad.net/bugs/1446571 Title: Playlist is emptied by itself Status in mediaplayer-app package in Ubuntu: Incomplete Bug description: When using the Music app on the Ubuntu Phone, I added some tracks to a playlist. The next day when trying to open the playlist, it was now empty -- all entries had gone. The playlist itself still existed, and the files were still on the phone, but the playlist had emptied itself. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mediaplayer-app/+bug/1446571/+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 1437765] Re: No desktop after upgrade to 14.10
Saw a bunch of at-spi2 errors in .xsession-errors. Reinstalled at- spi2-core, and those errors went away. Still no desktop. Deleting .config/dconf/user did the trick. -- 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/1437765 Title: No desktop after upgrade to 14.10 Status in unity package in Ubuntu: New Bug description: After upgrading my desktop machine from 14.04 to 14.10, I no longer have a desktop. The login screen works, but after logging in, I get just the backdrop image and a mouse pointer. Nothing else. The pointer responds to mouse movements, and I can switch to a text console using ctrl-alt-F, which is how I installed KDE in order to file this bug. But I can no longer open a terminal with ctrl-alt-T, or switch workspaces with ctrl-alt-. My .xsession-errors after logging in showed: X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 155 (GLX) Minor opcode of failed request: 19 (X_GLXQueryServerString) Serial number of failed request: 22 Current serial number in output stream: 22 openConnection: connect: No such file or directory cannot connect to brltty at :0 Script for ibus started at run_im. Script for auto started at run_im. Script for default started at run_im. upstart: hud main process (2389) terminated with status 1 upstart: unity-settings-daemon main process (2393) terminated with status 1 upstart: unity7 main process (2405) terminated with status 1 upstart: gnome-session (Unity) main process (2411) terminated with status 1 upstart: unity-panel-service main process (2422) terminated with status 1 upstart: indicator-keyboard main process (2496) terminated with status 1 upstart: indicator-printers main process (2502) terminated with status 1 upstart: upstart-dbus-session-bridge main process (2366) terminated with status 1 upstart: indicator-bluetooth main process (2485) killed by TERM signal upstart: indicator-power main process (2486) killed by TERM signal upstart: indicator-datetime main process (2494) killed by TERM signal upstart: indicator-sound main process (2501) killed by TERM signal upstart: indicator-session main process (2503) killed by TERM signal upstart: indicator-application main process (2536) killed by TERM signal upstart: Disconnected from notified D-Bus bus This is quite a slow machine, so normally it'd take a while to complete a graphical login. But now, when I log in and immediately switch to a graphical console to run "top," it doesn't show much going on. External filesystem volumes are not auto-mounted under /media the way they usually are. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-33.44-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic i686 NonfreeKernelModules: fglrx ApportVersion: 2.14.7-0ubuntu8.2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: KDE Date: Sun Mar 29 09:23:52 2015 InstallationDate: Installed on 2012-11-25 (853 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2015-03-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1437765/+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 1721472] Re: package console-setup 1.166ubuntu6 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)
See also https://askubuntu.com/questions/960749/update-stuck-at-setting- up-keyboard-configuration-1-166ubuntu6. Postinstall script hangs waiting for "plymouth --ping". Killing "plymouth --ping" allows it to continue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1721472 Title: package console-setup 1.166ubuntu6 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) Status in console-setup package in Ubuntu: Confirmed Bug description: Post install for console-setup failed. Had to edit postinstall script to exit 0 to install other packages ProblemType: Package DistroRelease: Ubuntu 17.10 Package: console-setup 1.166ubuntu6 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Wed Oct 4 09:24:06 2017 DpkgTerminalLog: Setting up keyboard-configuration (1.166ubuntu6) ... Setting up console-setup-linux (1.166ubuntu6) ... Setting up console-setup (1.166ubuntu6) ... [1mdpkg:[0m error processing package console-setup (--configure): subprocess installed post-installation script was killed by signal (Terminated) ErrorMessage: subprocess installed post-installation script was killed by signal (Terminated) InstallationDate: Installed on 2017-10-04 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.2-1ubuntu4 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: console-setup Title: package console-setup 1.166ubuntu6 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1721472/+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 1721472] Re: package console-setup 1.166ubuntu6 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)
See attached for strace output ** Attachment added: "strace plymouth --ping" https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1721472/+attachment/4975665/+files/strace.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1721472 Title: package console-setup 1.166ubuntu6 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) Status in console-setup package in Ubuntu: Incomplete Bug description: Post install for console-setup failed. Had to edit postinstall script to exit 0 to install other packages ProblemType: Package DistroRelease: Ubuntu 17.10 Package: console-setup 1.166ubuntu6 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Wed Oct 4 09:24:06 2017 DpkgTerminalLog: Setting up keyboard-configuration (1.166ubuntu6) ... Setting up console-setup-linux (1.166ubuntu6) ... Setting up console-setup (1.166ubuntu6) ... [1mdpkg:[0m error processing package console-setup (--configure): subprocess installed post-installation script was killed by signal (Terminated) ErrorMessage: subprocess installed post-installation script was killed by signal (Terminated) InstallationDate: Installed on 2017-10-04 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.2-1ubuntu4 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: console-setup Title: package console-setup 1.166ubuntu6 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1721472/+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 1721472] Re: package console-setup 1.166ubuntu6 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)
To add to the above strace output, 'plymouth --ping' continues to hang. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1721472 Title: package console-setup 1.166ubuntu6 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) Status in console-setup package in Ubuntu: Incomplete Bug description: Post install for console-setup failed. Had to edit postinstall script to exit 0 to install other packages ProblemType: Package DistroRelease: Ubuntu 17.10 Package: console-setup 1.166ubuntu6 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Wed Oct 4 09:24:06 2017 DpkgTerminalLog: Setting up keyboard-configuration (1.166ubuntu6) ... Setting up console-setup-linux (1.166ubuntu6) ... Setting up console-setup (1.166ubuntu6) ... [1mdpkg:[0m error processing package console-setup (--configure): subprocess installed post-installation script was killed by signal (Terminated) ErrorMessage: subprocess installed post-installation script was killed by signal (Terminated) InstallationDate: Installed on 2017-10-04 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.2-1ubuntu4 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: console-setup Title: package console-setup 1.166ubuntu6 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1721472/+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 1437765] [NEW] No desktop after upgrade to 14.10
Public bug reported: After upgrading my desktop machine from 14.04 to 14.10, I no longer have a desktop. The login screen works, but after logging in, I get just the backdrop image and a mouse pointer. Nothing else. The pointer responds to mouse movements, and I can switch to a text console using ctrl-alt-F, which is how I installed KDE in order to file this bug. But I can no longer open a terminal with ctrl-alt-T, or switch workspaces with ctrl-alt-. My .xsession-errors after logging in showed: X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 155 (GLX) Minor opcode of failed request: 19 (X_GLXQueryServerString) Serial number of failed request: 22 Current serial number in output stream: 22 openConnection: connect: No such file or directory cannot connect to brltty at :0 Script for ibus started at run_im. Script for auto started at run_im. Script for default started at run_im. upstart: hud main process (2389) terminated with status 1 upstart: unity-settings-daemon main process (2393) terminated with status 1 upstart: unity7 main process (2405) terminated with status 1 upstart: gnome-session (Unity) main process (2411) terminated with status 1 upstart: unity-panel-service main process (2422) terminated with status 1 upstart: indicator-keyboard main process (2496) terminated with status 1 upstart: indicator-printers main process (2502) terminated with status 1 upstart: upstart-dbus-session-bridge main process (2366) terminated with status 1 upstart: indicator-bluetooth main process (2485) killed by TERM signal upstart: indicator-power main process (2486) killed by TERM signal upstart: indicator-datetime main process (2494) killed by TERM signal upstart: indicator-sound main process (2501) killed by TERM signal upstart: indicator-session main process (2503) killed by TERM signal upstart: indicator-application main process (2536) killed by TERM signal upstart: Disconnected from notified D-Bus bus This is quite a slow machine, so normally it'd take a while to complete a graphical login. But now, when I log in and immediately switch to a graphical console to run "top," it doesn't show much going on. External filesystem volumes are not auto-mounted under /media the way they usually are. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-33.44-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic i686 NonfreeKernelModules: fglrx ApportVersion: 2.14.7-0ubuntu8.2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: KDE Date: Sun Mar 29 09:23:52 2015 InstallationDate: Installed on 2012-11-25 (853 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2015-03-28 (0 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 utopic -- 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/1437765 Title: No desktop after upgrade to 14.10 Status in unity package in Ubuntu: New Bug description: After upgrading my desktop machine from 14.04 to 14.10, I no longer have a desktop. The login screen works, but after logging in, I get just the backdrop image and a mouse pointer. Nothing else. The pointer responds to mouse movements, and I can switch to a text console using ctrl-alt-F, which is how I installed KDE in order to file this bug. But I can no longer open a terminal with ctrl-alt-T, or switch workspaces with ctrl-alt-. My .xsession-errors after logging in showed: X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 155 (GLX) Minor opcode of failed request: 19 (X_GLXQueryServerString) Serial number of failed request: 22 Current serial number in output stream: 22 openConnection: connect: No such file or directory cannot connect to brltty at :0 Script for ibus started at run_im. Script for auto started at run_im. Script for default started at run_im. upstart: hud main process (2389) terminated with status 1 upstart: unity-settings-daemon main process (2393) terminated with status 1 upstart: unity7 main process (2405) terminated with status 1 upstart: gnome-session (Unity) main process (2411) terminated with status 1 upstart: unity-panel-service main process (2422) terminated with status 1 upstart: indicator-keyboard main process (2496) terminated with status 1 upstart: indicator-printers main process (2502) terminated with status 1 upstart: upstart-dbus-session-bridge main process (2366) terminated with status 1 upstart: indicator-bluetooth main process (2485) killed by TERM signal upstart: indicato
[Touch-packages] [Bug 1437765] Re: No desktop after upgrade to 14.10
While the system is in this state, "ps" does show a compiz process. -- 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/1437765 Title: No desktop after upgrade to 14.10 Status in unity package in Ubuntu: New Bug description: After upgrading my desktop machine from 14.04 to 14.10, I no longer have a desktop. The login screen works, but after logging in, I get just the backdrop image and a mouse pointer. Nothing else. The pointer responds to mouse movements, and I can switch to a text console using ctrl-alt-F, which is how I installed KDE in order to file this bug. But I can no longer open a terminal with ctrl-alt-T, or switch workspaces with ctrl-alt-. My .xsession-errors after logging in showed: X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 155 (GLX) Minor opcode of failed request: 19 (X_GLXQueryServerString) Serial number of failed request: 22 Current serial number in output stream: 22 openConnection: connect: No such file or directory cannot connect to brltty at :0 Script for ibus started at run_im. Script for auto started at run_im. Script for default started at run_im. upstart: hud main process (2389) terminated with status 1 upstart: unity-settings-daemon main process (2393) terminated with status 1 upstart: unity7 main process (2405) terminated with status 1 upstart: gnome-session (Unity) main process (2411) terminated with status 1 upstart: unity-panel-service main process (2422) terminated with status 1 upstart: indicator-keyboard main process (2496) terminated with status 1 upstart: indicator-printers main process (2502) terminated with status 1 upstart: upstart-dbus-session-bridge main process (2366) terminated with status 1 upstart: indicator-bluetooth main process (2485) killed by TERM signal upstart: indicator-power main process (2486) killed by TERM signal upstart: indicator-datetime main process (2494) killed by TERM signal upstart: indicator-sound main process (2501) killed by TERM signal upstart: indicator-session main process (2503) killed by TERM signal upstart: indicator-application main process (2536) killed by TERM signal upstart: Disconnected from notified D-Bus bus This is quite a slow machine, so normally it'd take a while to complete a graphical login. But now, when I log in and immediately switch to a graphical console to run "top," it doesn't show much going on. External filesystem volumes are not auto-mounted under /media the way they usually are. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-33.44-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic i686 NonfreeKernelModules: fglrx ApportVersion: 2.14.7-0ubuntu8.2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: KDE Date: Sun Mar 29 09:23:52 2015 InstallationDate: Installed on 2012-11-25 (853 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2015-03-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1437765/+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 1437765] Re: No desktop after upgrade to 14.10
A piece of good news: I did get a working desktop when booting from the 14.10 installer, for the same architecture. -- 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/1437765 Title: No desktop after upgrade to 14.10 Status in unity package in Ubuntu: New Bug description: After upgrading my desktop machine from 14.04 to 14.10, I no longer have a desktop. The login screen works, but after logging in, I get just the backdrop image and a mouse pointer. Nothing else. The pointer responds to mouse movements, and I can switch to a text console using ctrl-alt-F, which is how I installed KDE in order to file this bug. But I can no longer open a terminal with ctrl-alt-T, or switch workspaces with ctrl-alt-. My .xsession-errors after logging in showed: X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 155 (GLX) Minor opcode of failed request: 19 (X_GLXQueryServerString) Serial number of failed request: 22 Current serial number in output stream: 22 openConnection: connect: No such file or directory cannot connect to brltty at :0 Script for ibus started at run_im. Script for auto started at run_im. Script for default started at run_im. upstart: hud main process (2389) terminated with status 1 upstart: unity-settings-daemon main process (2393) terminated with status 1 upstart: unity7 main process (2405) terminated with status 1 upstart: gnome-session (Unity) main process (2411) terminated with status 1 upstart: unity-panel-service main process (2422) terminated with status 1 upstart: indicator-keyboard main process (2496) terminated with status 1 upstart: indicator-printers main process (2502) terminated with status 1 upstart: upstart-dbus-session-bridge main process (2366) terminated with status 1 upstart: indicator-bluetooth main process (2485) killed by TERM signal upstart: indicator-power main process (2486) killed by TERM signal upstart: indicator-datetime main process (2494) killed by TERM signal upstart: indicator-sound main process (2501) killed by TERM signal upstart: indicator-session main process (2503) killed by TERM signal upstart: indicator-application main process (2536) killed by TERM signal upstart: Disconnected from notified D-Bus bus This is quite a slow machine, so normally it'd take a while to complete a graphical login. But now, when I log in and immediately switch to a graphical console to run "top," it doesn't show much going on. External filesystem volumes are not auto-mounted under /media the way they usually are. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-33.44-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic i686 NonfreeKernelModules: fglrx ApportVersion: 2.14.7-0ubuntu8.2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: KDE Date: Sun Mar 29 09:23:52 2015 InstallationDate: Installed on 2012-11-25 (853 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2015-03-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1437765/+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 1437765] Re: No desktop after upgrade to 14.10
So to be clear: my desktop is still utterly broken, but the one on an installer disc for the same version is not. Hopefully there is a simple configuration problem. I haven't done anything very special, I thought. -- 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/1437765 Title: No desktop after upgrade to 14.10 Status in unity package in Ubuntu: New Bug description: After upgrading my desktop machine from 14.04 to 14.10, I no longer have a desktop. The login screen works, but after logging in, I get just the backdrop image and a mouse pointer. Nothing else. The pointer responds to mouse movements, and I can switch to a text console using ctrl-alt-F, which is how I installed KDE in order to file this bug. But I can no longer open a terminal with ctrl-alt-T, or switch workspaces with ctrl-alt-. My .xsession-errors after logging in showed: X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 155 (GLX) Minor opcode of failed request: 19 (X_GLXQueryServerString) Serial number of failed request: 22 Current serial number in output stream: 22 openConnection: connect: No such file or directory cannot connect to brltty at :0 Script for ibus started at run_im. Script for auto started at run_im. Script for default started at run_im. upstart: hud main process (2389) terminated with status 1 upstart: unity-settings-daemon main process (2393) terminated with status 1 upstart: unity7 main process (2405) terminated with status 1 upstart: gnome-session (Unity) main process (2411) terminated with status 1 upstart: unity-panel-service main process (2422) terminated with status 1 upstart: indicator-keyboard main process (2496) terminated with status 1 upstart: indicator-printers main process (2502) terminated with status 1 upstart: upstart-dbus-session-bridge main process (2366) terminated with status 1 upstart: indicator-bluetooth main process (2485) killed by TERM signal upstart: indicator-power main process (2486) killed by TERM signal upstart: indicator-datetime main process (2494) killed by TERM signal upstart: indicator-sound main process (2501) killed by TERM signal upstart: indicator-session main process (2503) killed by TERM signal upstart: indicator-application main process (2536) killed by TERM signal upstart: Disconnected from notified D-Bus bus This is quite a slow machine, so normally it'd take a while to complete a graphical login. But now, when I log in and immediately switch to a graphical console to run "top," it doesn't show much going on. External filesystem volumes are not auto-mounted under /media the way they usually are. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-33.44-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic i686 NonfreeKernelModules: fglrx ApportVersion: 2.14.7-0ubuntu8.2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: KDE Date: Sun Mar 29 09:23:52 2015 InstallationDate: Installed on 2012-11-25 (853 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2015-03-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1437765/+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 1437765] Re: No desktop after upgrade to 14.10
After some searching, I found a comment suggesting that resetting my ATI graphics driver using "aticonfig --initial" might help. I did that, and now I get slightly further. Now when I log in I get the basic file management functionality on the desktop: icons and a context menu. But no Unity buttons on the left- hand side of the screen, no Super key, and no terminal when I press ctrl-alt-T. Also, no window decorations with drag bars, close button and so on. -- 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/1437765 Title: No desktop after upgrade to 14.10 Status in unity package in Ubuntu: New Bug description: After upgrading my desktop machine from 14.04 to 14.10, I no longer have a desktop. The login screen works, but after logging in, I get just the backdrop image and a mouse pointer. Nothing else. The pointer responds to mouse movements, and I can switch to a text console using ctrl-alt-F, which is how I installed KDE in order to file this bug. But I can no longer open a terminal with ctrl-alt-T, or switch workspaces with ctrl-alt-. My .xsession-errors after logging in showed: X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 155 (GLX) Minor opcode of failed request: 19 (X_GLXQueryServerString) Serial number of failed request: 22 Current serial number in output stream: 22 openConnection: connect: No such file or directory cannot connect to brltty at :0 Script for ibus started at run_im. Script for auto started at run_im. Script for default started at run_im. upstart: hud main process (2389) terminated with status 1 upstart: unity-settings-daemon main process (2393) terminated with status 1 upstart: unity7 main process (2405) terminated with status 1 upstart: gnome-session (Unity) main process (2411) terminated with status 1 upstart: unity-panel-service main process (2422) terminated with status 1 upstart: indicator-keyboard main process (2496) terminated with status 1 upstart: indicator-printers main process (2502) terminated with status 1 upstart: upstart-dbus-session-bridge main process (2366) terminated with status 1 upstart: indicator-bluetooth main process (2485) killed by TERM signal upstart: indicator-power main process (2486) killed by TERM signal upstart: indicator-datetime main process (2494) killed by TERM signal upstart: indicator-sound main process (2501) killed by TERM signal upstart: indicator-session main process (2503) killed by TERM signal upstart: indicator-application main process (2536) killed by TERM signal upstart: Disconnected from notified D-Bus bus This is quite a slow machine, so normally it'd take a while to complete a graphical login. But now, when I log in and immediately switch to a graphical console to run "top," it doesn't show much going on. External filesystem volumes are not auto-mounted under /media the way they usually are. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-33.44-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic i686 NonfreeKernelModules: fglrx ApportVersion: 2.14.7-0ubuntu8.2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: KDE Date: Sun Mar 29 09:23:52 2015 InstallationDate: Installed on 2012-11-25 (853 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2015-03-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1437765/+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 1300557] Re: Screen resolution no longer works
I'm trying the BIOS upgrade as per those instructions. The only applicable option was the flashrom one, which seems to have hosed my BIOS. It's still on now, but I won't be able to boot it again. Kindly mark this bug New again to give me time to recover and retry! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works Status in xorg package in Ubuntu: Incomplete Bug description: My display's native resolution is 2560×1440 pixels. Prior to, I think, Saucy I could only reach this resolution by adding it using xrandr, and then calling xrandr on boot/login to select that resolution. The Display preferences did not show any higher options than 1920×1200. In Saucy, the native resolution just worked, and I could stop using xrandr. It also worked in Trusty in the alpha releases, up to (and I think including) beta-1. But today (this is not an April's fool, is it?) I rebooted after an upgrade, and found myself back in 1920×1200. Again, the Display preferences list that resolution as the highest possible. But this time, attempts to ‘xrandr --addmode’ my native resolution failed. The error message wasn't very helpful; I'll try to reproduce it later but it throws my display into yet a lower resolution that's hard to work with. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 1 09:59:00 2014 DistUpgraded: 2014-01-22 17:01:10,909 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2013-08-03 (240 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=12085c8d-328f-4c75-a04c-184c592f61ee ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-01-22 (68 days ago) dmi.bios.date: 05/16/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-D3HP-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd05/16/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z87-D3HP dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Apr 1 09:52:36 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16510 vendor DEL xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1300557/+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 1300557] Re: Screen resolution no longer works
Okay, I got out of that situation with the help of the flashrom people. My BIOS is now updated. It helped a bit in that I can now define and add my resolution again using xrandr. It won't stay added though: I need to define and add it every time I boot. Otherwise, the resolution is not in the Displays settings dropdown. The dmidecode output is: F7 08/12/2014 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works Status in xorg package in Ubuntu: Incomplete Bug description: My display's native resolution is 2560×1440 pixels. Prior to, I think, Saucy I could only reach this resolution by adding it using xrandr, and then calling xrandr on boot/login to select that resolution. The Display preferences did not show any higher options than 1920×1200. In Saucy, the native resolution just worked, and I could stop using xrandr. It also worked in Trusty in the alpha releases, up to (and I think including) beta-1. But today (this is not an April's fool, is it?) I rebooted after an upgrade, and found myself back in 1920×1200. Again, the Display preferences list that resolution as the highest possible. But this time, attempts to ‘xrandr --addmode’ my native resolution failed. The error message wasn't very helpful; I'll try to reproduce it later but it throws my display into yet a lower resolution that's hard to work with. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 1 09:59:00 2014 DistUpgraded: 2014-01-22 17:01:10,909 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2013-08-03 (240 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=12085c8d-328f-4c75-a04c-184c592f61ee ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-01-22 (68 days ago) dmi.bios.date: 05/16/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-D3HP-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd05/16/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z87-D3HP dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Apr 1 09:52:36 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16510 vendor DEL xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1300557/+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 1300557] Re: Screen resolution no longer works
Something happened to this bug's conversation: the message asking me to upgrade the BIOS has been removed/hidden. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works Status in xorg package in Ubuntu: Incomplete Bug description: My display's native resolution is 2560×1440 pixels. Prior to, I think, Saucy I could only reach this resolution by adding it using xrandr, and then calling xrandr on boot/login to select that resolution. The Display preferences did not show any higher options than 1920×1200. In Saucy, the native resolution just worked, and I could stop using xrandr. It also worked in Trusty in the alpha releases, up to (and I think including) beta-1. But today (this is not an April's fool, is it?) I rebooted after an upgrade, and found myself back in 1920×1200. Again, the Display preferences list that resolution as the highest possible. But this time, attempts to ‘xrandr --addmode’ my native resolution failed. The error message wasn't very helpful; I'll try to reproduce it later but it throws my display into yet a lower resolution that's hard to work with. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 1 09:59:00 2014 DistUpgraded: 2014-01-22 17:01:10,909 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2013-08-03 (240 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=12085c8d-328f-4c75-a04c-184c592f61ee ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-01-22 (68 days ago) dmi.bios.date: 05/16/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-D3HP-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd05/16/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z87-D3HP dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Apr 1 09:52:36 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16510 vendor DEL xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1300557/+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 1300557] Re: Screen resolution no longer works
I first upgraded to 14.10; that didn't change anything. Trying 15.04 now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works Status in xorg package in Ubuntu: Incomplete Bug description: My display's native resolution is 2560×1440 pixels. Prior to, I think, Saucy I could only reach this resolution by adding it using xrandr, and then calling xrandr on boot/login to select that resolution. The Display preferences did not show any higher options than 1920×1200. In Saucy, the native resolution just worked, and I could stop using xrandr. It also worked in Trusty in the alpha releases, up to (and I think including) beta-1. But today (this is not an April's fool, is it?) I rebooted after an upgrade, and found myself back in 1920×1200. Again, the Display preferences list that resolution as the highest possible. But this time, attempts to ‘xrandr --addmode’ my native resolution failed. The error message wasn't very helpful; I'll try to reproduce it later but it throws my display into yet a lower resolution that's hard to work with. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 1 09:59:00 2014 DistUpgraded: 2014-01-22 17:01:10,909 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2013-08-03 (240 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=12085c8d-328f-4c75-a04c-184c592f61ee ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-01-22 (68 days ago) dmi.bios.date: 05/16/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-D3HP-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd05/16/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z87-D3HP dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Apr 1 09:52:36 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16510 vendor DEL xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1300557/+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 1300557] Re: Screen resolution no longer works
No change in 15.04. I can add the resolution with xrandr, and after that I can use it. But after reboot, I have to do it again. The upgrade got stuck with a black screen and no networking, but I eventually got out of it with the "apt-get dist-upgrade" dance from the console. I hope that hasn't messed things up. It may matter that I've got the monitor's DVI port hooked up to my computer's HDMI port. It was the only way to get things working: the monitor doesn't support its full native resolution on HDMI, and the Haswell builtin graphics only supports the resolution on HDMI. But, the hardware can do it and it used to work from the settings GUI without hackery. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works Status in xorg package in Ubuntu: Incomplete Bug description: My display's native resolution is 2560×1440 pixels. Prior to, I think, Saucy I could only reach this resolution by adding it using xrandr, and then calling xrandr on boot/login to select that resolution. The Display preferences did not show any higher options than 1920×1200. In Saucy, the native resolution just worked, and I could stop using xrandr. It also worked in Trusty in the alpha releases, up to (and I think including) beta-1. But today (this is not an April's fool, is it?) I rebooted after an upgrade, and found myself back in 1920×1200. Again, the Display preferences list that resolution as the highest possible. But this time, attempts to ‘xrandr --addmode’ my native resolution failed. The error message wasn't very helpful; I'll try to reproduce it later but it throws my display into yet a lower resolution that's hard to work with. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 1 09:59:00 2014 DistUpgraded: 2014-01-22 17:01:10,909 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2013-08-03 (240 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=12085c8d-328f-4c75-a04c-184c592f61ee ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-01-22 (68 days ago) dmi.bios.date: 05/16/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-D3HP-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd05/16/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z87-D3HP dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Apr 1 09:52:36 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16510 vendor DEL xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bu
[Touch-packages] [Bug 1300557] Re: Screen resolution no longer works
According to the dpkg.log for that date, quite a lot: libc-bin for amd64. Also gcc-4.8, gcc-4.9, along with g++, cpp, libgcc1, libstdc++6 etc, for amd64 and i386; and libitm1, libgomp1, libgfortran3, libasan0, libatomic1, libtsan0, libquadmath0, libthumbnailer0, apport, apport-gtk, python3-problem-report, python3-apport, binfmt-support, dh-apport, libgtk2-perl, python-boto, python-lxml, python3-lxml, unity-webapps-qml, mobile-broadband-provider-info, python-keystoneclient, The day before I upgraded among other things libffi6 (for i386 and amd64) and libffi-dev, dconf-gsettings-backend, dconf-service, libdconf1, various dconf tools and frontends, libglib2.0-*, libunity- control-center1 and unity-control-center, libido3-0.1-0, lxc and related packages, libapparmor1 and apparmor, libqt5positioning5, libunity-gtk3-parser0, openjdk-7 and icedtea-7, ubuntu-release-upgrader and update-manager, libcompizconfig0, compiz-gnome, compiz-plugins- default, libdecoration0, compiz-core, compiz, im-config, kerneloops- daemon, indicator-*, unity-scope-*, libreoffice, unity, libunity- core-6.0.9, unity-services, ubuntu-mono, libvirt, the kernel, and dh- apparmor. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works Status in xorg package in Ubuntu: Incomplete Bug description: My display's native resolution is 2560×1440 pixels. Prior to, I think, Saucy I could only reach this resolution by adding it using xrandr, and then calling xrandr on boot/login to select that resolution. The Display preferences did not show any higher options than 1920×1200. In Saucy, the native resolution just worked, and I could stop using xrandr. It also worked in Trusty in the alpha releases, up to (and I think including) beta-1. But today (this is not an April's fool, is it?) I rebooted after an upgrade, and found myself back in 1920×1200. Again, the Display preferences list that resolution as the highest possible. But this time, attempts to ‘xrandr --addmode’ my native resolution failed. The error message wasn't very helpful; I'll try to reproduce it later but it throws my display into yet a lower resolution that's hard to work with. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 1 09:59:00 2014 DistUpgraded: 2014-01-22 17:01:10,909 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2013-08-03 (240 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=12085c8d-328f-4c75-a04c-184c592f61ee ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-01-22 (68 days ago) dmi.bios.date: 05/16/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-D3HP-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd05/16/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z87-D3HP dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
[Touch-packages] [Bug 1300557] Re: Screen resolution no longer works
The version that was installed on March 31 was 3.13.0.20.24. The version I uninstalled right after that was 3.13.0.18.38. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1300557 Title: Screen resolution no longer works Status in xorg package in Ubuntu: Incomplete Bug description: My display's native resolution is 2560×1440 pixels. Prior to, I think, Saucy I could only reach this resolution by adding it using xrandr, and then calling xrandr on boot/login to select that resolution. The Display preferences did not show any higher options than 1920×1200. In Saucy, the native resolution just worked, and I could stop using xrandr. It also worked in Trusty in the alpha releases, up to (and I think including) beta-1. But today (this is not an April's fool, is it?) I rebooted after an upgrade, and found myself back in 1920×1200. Again, the Display preferences list that resolution as the highest possible. But this time, attempts to ‘xrandr --addmode’ my native resolution failed. The error message wasn't very helpful; I'll try to reproduce it later but it throws my display into yet a lower resolution that's hard to work with. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 1 09:59:00 2014 DistUpgraded: 2014-01-22 17:01:10,909 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2013-08-03 (240 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=12085c8d-328f-4c75-a04c-184c592f61ee ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-01-22 (68 days ago) dmi.bios.date: 05/16/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-D3HP-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd05/16/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z87-D3HP dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Apr 1 09:52:36 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16510 vendor DEL xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1300557/+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 1251257] Re: [SRU] avahi fails in containers
MAAS trunk no longer includes Avahi, so closing this bug there. ** Changed in: maas Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1251257 Title: [SRU] avahi fails in containers Status in MAAS: Fix Released Status in MAAS 1.4 series: Triaged Status in “avahi” package in Ubuntu: Fix Released Status in “avahi” source package in Precise: Fix Released Status in “avahi” source package in Saucy: Fix Released Status in “avahi” source package in Trusty: Fix Released Bug description: installed a brand new maas server on suacy into an lxc container from archive and http:///MAAS is not accessible although http:// is accessible http:///MAAS is getting logged to /var/log/apache2/access.log though so request is making it through danwest: can you please pastebin apache2's error and access.log http://paste.ubuntu.com/6405411/ http://paste.ubuntu.com/6405412/ danwest: I know what it is danwest: dbus/avahi danwest: try to restart whatever avahi service there is "dbus" reminds me of https://bugs.launchpad.net/juju-core/+bug/1248283 but that was about the units, not maas itself https://pastebin.canonical.com/100290/ same problem danwest: yeah the avahi daemon is failing to start, causing maas to fail danwest: maybe restart whatever dbus serviice it is, and then the avahi-daemon danwest, restart dbus and avahi-daemon, see https://bugs.launchpad.net/maas/+bug/1221059 danwest: did avahi-daemon restart corrrectly? nope danwest: i guess then an issue with dbus is preventing avahi from working... hence maas failing roaksoax: should not matter but the only thing that is a little unique is that this is in a saucy container danwest: ah so then thats the issue... what, the container? yeah how so? avahi might have issues running in a container hallyn: roaksoax: what should I file that lxc/avahi /maas bug that I hit this morning against? danwest: i think maas should work around it by unsetting rlimit-nproc (and/or by running on trusty in a private user ns smoser: fwiw the problem is that avahi sets its nproc rlimit to exaclty 3, but in a container it's using a uid that is in use on the host - so it exceeds 3 tasks (i.e. it's reusing uid which is ntp on the host, and ntp is running; or just another avahi) ok... so that doesn't seem like maas's problem to me nor juju's really. smoser: it is. it needs to pick a unique uid, or configure avahi to ignore the rlimit maas isn't running avahi is it ? i duno what's actually running it :) it's *for* maas, but it probably is juju what if there was a bug in php, and a user used maas to deploy php. should we fix that in maas ? you're talking about a bug. i'm talking about a resource conflict having avahi alwasy run without nprocs, for protection, would be wrong for this. fix is still up for debate on this one... [Impact] Avahi sets the rlimit_nproc to 3, causing avahi to fail running in containers. This This option should not be set in containers at all. This causes avahi-daemon to fail, hence all the applications that use avahi will also fail. In this particular case, MAAS fails because of this. [Test Case] 1. Install a container. 2. Install MAAS 3. Check apache2 log for errors, such as those in [1]. [Regression Potential] Minimal. This has been tested and works as expected. [1]: http://paste.ubuntu.com/6405412/ To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1251257/+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 1290847] Re: pyvenv fails due to mising ensurepip module
I can confirm what Mali says. No python3[*]-venv in the repositories. And the python3 -m venv gives the error that kickstarted this lengthy fix process. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1290847 Title: pyvenv fails due to mising ensurepip module Status in python3-defaults package in Ubuntu: Fix Released Status in python3.4 package in Ubuntu: Fix Released Status in python3.4 package in Debian: Fix Released Bug description: Hello, I noticed the following # fails python3.4 -m venv --clear python-venv Error: Command '['.../external/python-venv/bin/python3.4', '-Im', 'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit status 1 # works, but no pip python3.4 -m venv --clear --without-pip python-venv Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1290847/+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 1441253] Re: hanging suspend job prevents shutdown
Xubuntu 16.04 user here on EXT4. I don't use suspend on my Dell Latitude laptop at all. Was just trying to reboot after noticing my network manager indicator icon was in limbo and 'lo and behold: % sudo -H shutdown -P now Failed to start poweroff.target: Transaction is destructive. See system logs and 'systemctl status poweroff.target' for details. % systemctl status poweroff.target ● poweroff.target - Power-Off Loaded: loaded (/lib/systemd/system/poweroff.target; disabled; vendor preset: disabled) Active: inactive (dead) Docs: man:systemd.special(7) % ps ax | grep systemd 359 ?Ss 0:00 /lib/systemd/systemd-journald 412 ?Ss 0:00 /lib/systemd/systemd-udevd 1187 ?Ss 0:00 /lib/systemd/systemd-logind 1217 ?Ss 0:02 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation 2014 ?Ss 0:00 /lib/systemd/systemd --user 27605 ?Ss 0:00 /lib/systemd/systemd-sleep suspend I work with the lid closed on a dual monitor system. Digging through the journal is interesting due to: dec 21 10:52:38 2-1b systemd-logind[1187]: Suspending... dec 21 10:52:38 2-1b NetworkManager[1253]: [1482313958.2467] manager: sleep requested (sleeping: no enabled: yes) dec 21 10:52:38 2-1b NetworkManager[1253]: [1482313958.2468] manager: sleeping... dec 21 10:52:38 2-1b NetworkManager[1253]: [1482313958.2468] device (wlp3s0): state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37] dec 21 10:52:38 2-1b NetworkManager[1253]: [1482313958.2477] manager: NetworkManager state is now ASLEEP dec 21 10:52:38 2-1b whoopsie[1255]: [10:52:38] offline dec 21 10:52:38 2-1b obexd[2450]: Terminating dec 21 10:52:38 2-1b polkitd(authority=local)[1433]: Unregistered Authentication Agent for unix-session:c2 (system bus name :1.46, object path /org/gnome/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus) dec 21 10:52:38 2-1b systemd[1]: Reached target Sleep. dec 21 10:52:38 2-1b lightdm[1688]: pam_unix(lightdm:session): session closed for user jeroenr dec 21 10:52:38 2-1b systemd[1]: Starting Suspend... dec 21 10:52:38 2-1b systemd-sleep[27605]: Failed to connect to non-global ctrl_ifname: (nil) error: No such file or directory dec 21 10:52:38 2-1b NetworkManager[1253]: [1482313958.3907] dns-mgr: Writing DNS information to /sbin/resolvconf dec 21 10:52:38 2-1b dnsmasq[1706]: setting upstream servers from DBus dec 21 10:52:38 2-1b systemd-sleep[27613]: /lib/systemd/system-sleep/wpasupplicant failed with error code 255. dec 21 10:52:38 2-1b dnsmasq[1706]: using nameserver 8.8.8.8#53 dec 21 10:52:38 2-1b systemd-sleep[27605]: Suspending system... dec 21 10:52:38 2-1b dnsmasq[1706]: using nameserver 8.8.4.4#53 dec 21 10:52:38 2-1b kernel: PM: Syncing filesystems ... done. dec 21 10:52:38 2-1b kernel: PM: Preparing system for sleep (mem) Somehow the system was trying to go to sleep with me actually working on it. Unless... I did log out and in again for fixing up my input methods. But why would systemd register a XFCE logout as a request to suspend? -- 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/1441253 Title: hanging suspend job prevents shutdown Status in systemd package in Ubuntu: Won't Fix Bug description: poweroff (systemd poweroff) and reboot no longer work running sudo sytemd poweroff generates this: Failed to start poweroff.target: Transaction is destructive. journal log also shows: Apr 07 18:30:12 alice polkitd(authority=local)[1088]: Registered Authentication Agent for unix-process:32412:2895609 (system bus name :1.194 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) Apr 07 18:30:12 alice systemd[1]: Requested transaction contradicts existing jobs: Transaction is destructive. Apr 07 18:30:12 alice polkitd(authority=local)[1088]: Unregistered Authentication Agent for unix-process:32412:2895609 (system bus name :1.194, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus) Output of systemctl list-jobs JOB UNITTYPE STATE 6009 suspend.target start waiting 6010 systemd-suspend.service start running 6014 anacron-resume.service start waiting ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-6ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.17-0ubuntu1 Architecture: amd64 Date: Tue Apr 7 18:32:27 2015 MachineType: Hewlett-Packard HP EliteBook 8560w ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-
[Touch-packages] [Bug 1633003] [NEW] (Cisco) VPN name resolution breaks after upgrade to 1.2.2-0ubuntu0.16.04.3
Public bug reported: After upgrading my 16.04 installation today I noticed my VPN sessions suddenly had no name resolution anymore. Digging through /var/log/apt/history.log I noticed these were the updates: Start-Date: 2016-10-13 09:00:37 Commandline: apt dist-upgrade Requested-By: jeroenr (1000) Upgrade: libnm-glib4:amd64 (1.2.2-0ubuntu0.16.04.1, 1.2.2-0ubuntu0.16.04.3), libsystemd0:amd64 (229-4ubuntu10, 229-4ubuntu11), libsystemd0:i386 (229-4ubuntu10, 229-4ubuntu11), libdbusmenu-glib4:amd64 (12.10.3+16.04.20160223.1-0ubuntu1, 16.04.1+16.04.20160927-0ubuntu1), google-chrome-stable:amd64 (53.0.2785.143-1, 54.0.2840.59-1), libnm-glib-vpn1:amd64 (1.2.2-0ubuntu0.16.04.1, 1.2.2-0ubuntu0.16.04.3), udev:amd64 (229-4ubuntu10, 229-4ubuntu11), libnm0:amd64 (1.2.2-0ubuntu0.16.04.1, 1.2.2-0ubuntu0.16.04.3), network-manager:amd64 (1.2.2-0ubuntu0.16.04.1, 1.2.2-0ubuntu0.16.04.3), libdbusmenu-gtk4:amd64 (12.10.3+16.04.20160223.1-0ubuntu1, 16.04.1+16.04.20160927-0ubuntu1), kbd:amd64 (1.15.5-1ubuntu4, 1.15.5-1ubuntu5), libudev1:amd64 (229-4ubuntu10, 229-4ubuntu11), libudev1:i386 (229-4ubuntu10, 229-4ubuntu11), libnm-util2:amd64 (1.2.2-0ubuntu0.16.04.1, 1.2.2-0ubuntu0.16.04.3), libappstream-glib8:amd64 (0.5.13-1ubuntu3, 0.5.13-1ubuntu4), gnome-calculator:amd64 (1:3.18.3-0ubuntu1, 1:3.18.3-0ub untu1.16.04.1), systemd-sysv:amd64 (229-4ubuntu10, 229-4ubuntu11), libpam-systemd:amd64 (229-4ubuntu10, 229-4ubuntu11), systemd:amd64 (229-4ubuntu10, 229-4ubuntu11), gir1.2-dbusmenu-glib-0.4:amd64 (12.10.3+16.04.20160223.1-0ubuntu1, 16.04.1+16.04.20160927-0ubuntu1), libdbusmenu-gtk3-4:amd64 (12.10.3+16.04.20160223.1-0ubuntu1, 16.04.1+16.04.20160927-0ubuntu1), lightdm:amd64 (1.18.2-0ubuntu2, 1.18.3-0ubuntu1), liblightdm-gobject-1-0:amd64 (1.18.2-0ubuntu2, 1.18.3-0ubuntu1) End-Date: 2016-10-13 09:01:06 After downloading version 1.2.2-0ubuntu0.16.04.1 copies of libnm-glib- vpn1:amd64 libnm-glib4:amd64 libnm-util2:amd64 libnm0:amd64 network- manager:amd64 and installing them via: sudo -H dpkg -i *.deb my name resolution started working again. Additional information: % lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 % apt-cache policy libnm-glib-vpn1 libnm-glib4 libnm-util2 libnm0 network-manager libnm-glib-vpn1: Installed: 1.2.2-0ubuntu0.16.04.1 Candidate: 1.2.2-0ubuntu0.16.04.3 Version table: 1.2.2-0ubuntu0.16.04.3 500 500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages *** 1.2.2-0ubuntu0.16.04.1 100 100 /var/lib/dpkg/status 1.1.93-0ubuntu4 500 500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages libnm-glib4: Installed: 1.2.2-0ubuntu0.16.04.1 Candidate: 1.2.2-0ubuntu0.16.04.3 Version table: 1.2.2-0ubuntu0.16.04.3 500 500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages *** 1.2.2-0ubuntu0.16.04.1 100 100 /var/lib/dpkg/status 1.1.93-0ubuntu4 500 500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages libnm-util2: Installed: 1.2.2-0ubuntu0.16.04.1 Candidate: 1.2.2-0ubuntu0.16.04.3 Version table: 1.2.2-0ubuntu0.16.04.3 500 500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages *** 1.2.2-0ubuntu0.16.04.1 100 100 /var/lib/dpkg/status 1.1.93-0ubuntu4 500 500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages libnm0: Installed: 1.2.2-0ubuntu0.16.04.1 Candidate: 1.2.2-0ubuntu0.16.04.3 Version table: 1.2.2-0ubuntu0.16.04.3 500 500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages *** 1.2.2-0ubuntu0.16.04.1 100 100 /var/lib/dpkg/status 1.1.93-0ubuntu4 500 500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages network-manager: Installed: 1.2.2-0ubuntu0.16.04.1 Candidate: 1.2.2-0ubuntu0.16.04.3 Version table: 1.2.2-0ubuntu0.16.04.3 500 500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages *** 1.2.2-0ubuntu0.16.04.1 100 100 /var/lib/dpkg/status 1.1.93-0ubuntu4 500 500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages % apt-cache policy vpnc vpnc: Installed: 0.5.3r550-2build1 Candidate: 0.5.3r550-2build1 Version table: *** 0.5.3r550-2build1 500 500 http://nl.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status Expected After updating that connecting to my existing and working Cisco VPN would work What happened Name resolution failed. Could not ping hosts over VPN anymore. Most likely cause It seems that /etc/resolv.conf is not getting the search argument added to the file anymore. With .3 installed I only had a nameserver 127.0.0.1 line. Now with .1 installed I see that I have both that nameserver 127.0.0.1 line as well as search ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification b
[Touch-packages] [Bug 1374759] Re: >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
This is still happening on a fresh 15.04 install and then updating it completely with apt/aptitude. Kernel version 3.19.0-26. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1374759 Title: >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Triaged Status in os-prober package in Ubuntu: Confirmed Bug description: [ 556.734157] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [ 556.746268] JFS: nTxBlock = 8192, nTxLock = 65536 [ 556.763789] ntfs: driver 2.1.30 [Flags: R/O MODULE]. [ 556.792231] QNX4 filesystem 0.2.3 registered. [ 557.922469] EXT4-fs (sda4): unable to read superblock [ 557.925868] EXT4-fs (sda4): unable to read superblock [ 557.928967] EXT4-fs (sda4): unable to read superblock [ 557.931784] FAT-fs (sda4): bogus number of reserved sectors [ 557.931791] FAT-fs (sda4): Can't find a valid FAT filesystem [ 557.946740] XFS (sda4): Invalid superblock magic number [ 557.951904] FAT-fs (sda4): bogus number of reserved sectors [ 557.951911] FAT-fs (sda4): Can't find a valid FAT filesystem [ 557.959099] MINIX-fs: unable to read superblock [ 557.965712] attempt to access beyond end of device [ 557.965721] sda4: rw=16, want=3, limit=2 [ 557.965725] hfsplus: unable to find HFS+ superblock [ 557.968487] qnx4: no qnx4 filesystem (no root dir). [ 557.971203] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 557.974459] hfs: can't find a HFS filesystem on dev sda4 [ 564.034208] EXT4-fs (sda4): unable to read superblock [ 564.040322] EXT4-fs (sda4): unable to read superblock [ 564.043485] EXT4-fs (sda4): unable to read superblock [ 564.047076] FAT-fs (sda4): bogus number of reserved sectors [ 564.047083] FAT-fs (sda4): Can't find a valid FAT filesystem [ 564.059578] XFS (sda4): Invalid superblock magic number [ 564.064473] FAT-fs (sda4): bogus number of reserved sectors [ 564.064489] FAT-fs (sda4): Can't find a valid FAT filesystem [ 564.072080] MINIX-fs: unable to read superblock [ 564.074564] attempt to access beyond end of device [ 564.074571] sda4: rw=16, want=3, limit=2 [ 564.074576] hfsplus: unable to find HFS+ superblock [ 564.076688] qnx4: no qnx4 filesystem (no root dir). [ 564.078847] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 564.080902] hfs: can't find a HFS filesystem on dev sda4 [ 570.554296] EXT4-fs (sda4): unable to read superblock [ 570.557647] EXT4-fs (sda4): unable to read superblock [ 570.560516] EXT4-fs (sda4): unable to read superblock [ 570.563451] FAT-fs (sda4): bogus number of reserved sectors [ 570.563460] FAT-fs (sda4): Can't find a valid FAT filesystem [ 570.574953] XFS (sda4): Invalid superblock magic number [ 570.580796] FAT-fs (sda4): bogus number of reserved sectors [ 570.580806] FAT-fs (sda4): Can't find a valid FAT filesystem [ 570.588340] MINIX-fs: unable to read superblock [ 570.590983] attempt to access beyond end of device [ 570.590993] sda4: rw=16, want=3, limit=2 [ 570.590999] hfsplus: unable to find HFS+ superblock [ 570.593321] qnx4: no qnx4 filesystem (no root dir). [ 570.595556] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 570.597775] hfs: can't find a HFS filesystem on dev sda4 [ 576.795014] EXT4-fs (sda4): unable to read superblock [ 576.797554] EXT4-fs (sda4): unable to read superblock [ 576.800063] EXT4-fs (sda4): unable to read superblock [ 576.802647] FAT-fs (sda4): bogus number of reserved sectors [ 576.802655] FAT-fs (sda4): Can't find a valid FAT filesystem [ 576.813305] XFS (sda4): Invalid superblock magic number [ 576.820257] FAT-fs (sda4): bogus number of reserved sectors [ 576.820276] FAT-fs (sda4): Can't find a valid FAT filesystem [ 576.830945] MINIX-fs: unable to read superblock [ 576.834108] attempt to access beyond end of device [ 576.834119] sda4: rw=16, want=3, limit=2 [ 576.834125] hfsplus: unable to find HFS+ superblock [ 576.837264] qnx4: no qnx4 filesystem (no root dir). [ 576.840408] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|
