[Touch-packages] [Bug 2065932] Re: Only adds the weak key for PPAs dual-signed with both weak and strong keys
I removed then re-added the ppas which had the warnings. After running 'apt update', I don't get warnings anymore. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2065932 Title: Only adds the weak key for PPAs dual-signed with both weak and strong keys Status in software-properties package in Ubuntu: Invalid Bug description: After running ‘add-apt-repository ppa:git-core/ppa’ on Ubuntu 24.04, ‘apt update’ gives this warning: W: https://ppa.launchpadcontent.net/git- core/ppa/ubuntu/dists/noble/InRelease: Signature by key E1DD270288B4E6030699E45FA1715D88E1DF1F24 uses weak algorithm (rsa1024) But this PPA is dual-signed by two keys, only one of which is weak. add-apt-repository has chosen to install the rsa1024 key in sources.list.d. It should choose the rsa4096 key instead. $ curl 'https://ppa.launchpadcontent.net/git-core/ppa/ubuntu/dists/noble/InRelease' | gpgv … gpg: Signature made Thu 16 May 2024 05:22:18 AM PDT gpg:using RSA key F911AB184317630C59970973E363C90F8F1B6217 gpg: Good signature from "Launchpad PPA for Ubuntu Git Maintainers" [unknown] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: F911 AB18 4317 630C 5997 0973 E363 C90F 8F1B 6217 gpg: Signature made Thu 16 May 2024 05:22:18 AM PDT gpg:using RSA key E1DD270288B4E6030699E45FA1715D88E1DF1F24 gpg: Good signature from "Launchpad PPA for Ubuntu Git Maintainers" [unknown] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: E1DD 2702 88B4 E603 0699 E45F A171 5D88 E1DF 1F24 $ gpg --list-keys F911AB184317630C59970973E363C90F8F1B6217 E1DD270288B4E6030699E45FA1715D88E1DF1F24 pub rsa1024 2009-01-22 [SC] E1DD270288B4E6030699E45FA1715D88E1DF1F24 uid [ unknown] Launchpad PPA for Ubuntu Git Maintainers pub rsa4096 2024-04-24 [SC] F911AB184317630C59970973E363C90F8F1B6217 uid [ unknown] Launchpad PPA for Ubuntu Git Maintainers Context: https://discourse.ubuntu.com/t/new-requirements-for-apt- repository-signing-in-24-04/42854 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2065932/+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 2024661] Re: Unable to configure Wireguard connection at NetworkManager interface
If I understand the bug description correctly, I don't think the problem is related to netplan. I am experiencing the same issue in Fedora 39 KDE. After editing WireGuard peer settings using Plasma's network settings and pressing 'OK', the 'Apply' button remains grayed out and I am unable to save settings. After closing and re-opening network settings, my changes are gone. -- 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/2024661 Title: Unable to configure Wireguard connection at NetworkManager interface Status in netplan.io package in Ubuntu: In Progress Status in network-manager package in Ubuntu: Invalid Bug description: Repro steps: 1) Open NetworkManager GUI. 2) Click "Add new Connection" and select "Wireguard" connection type. 3) Then you have to configure new connection. Basic configuration looks like that: a) Write down connection name, b) Write down local private key, c) Create new peer and populate peer's parameters: public key of the peer, allowed IPs (i.e. 0.0.0.0/0), peer's IP address and port. 4) Click "OK" and "Save". 5) Open "Peers" again. Ensure that settings were not stored. All fields are empty. Found in Kubuntu flavor version 23.10 (development), Plasma Network Manager interface. netplan.io 0.106.1-2 network-manager 1.42.4-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2024661/+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 1886161] Re: Unattended upgrades should work on roaming laptops
@Julian Thanks for the explanation and the tip. Auto-retries would be a really beneficial feature but I get that you have a lot on your plate. Thanks for your work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1886161 Title: Unattended upgrades should work on roaming laptops Status in apt package in Ubuntu: New Status in gnome-settings-daemon package in Ubuntu: Invalid Bug description: For many if not most laptop computers, Unattended Upgrades seems all but useless by design. For upgrades to happen, with default config, 3 conditions must be met: - an internet connection must be up and running when the timer or cron or anacron tries the unattended upgrade - the connection must not be metered, whatever that means (Skip-Updates-On-Metered-Connections "true") - the computer must be plugged in (OnlyOnACPower "true") These are insurmountable problems for many laptops on the go. Inevitably, security upgrades will almost never run unattended on such computers. I discovered with shock that Unattended Upgrades had almost never run on my laptop. I tried all possible config tweaks. Nothing worked reliably and in the end I gave up and wrote a upgrade script which uses Network Manager's connection-up hook. Unattended Upgrades needs to do something like this out of the box. Users should not need to write scripts to ensure security upgrades. Unattended upgrades is an excellent project for servers. But it really needs to work, out of the box, on laptops too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1886161/+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 1946714] [NEW] Unable to locally verify the issuer's authority.
Public bug reported: In a terminal, when I run the following: wget https://www.linz.govt.nz/sites/default/files/media/ntm/bsb/BSB_UPDATE.zip I get an error message about certificates, as follows. ERROR: cannot verify www.linz.govt.nz's certificate, issued by ‘CN=Thawte RSA CA 2018,OU=www.digicert.com,O=DigiCert Inc,C=US’: The file is not downloaded. I contacted the maintainers of the site, they declared there is no problem with the certificate. Of course, this probably isn't a problem with wget, or with curl which gives a similar error and the advice to go to this page: https://curl.se/docs/sslcerts.html Unfortunately that's way over my head, so I'm hoping someone helpful here can shed some light on the matter. Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: wget 1.20.3-1ubuntu1 Uname: Linux 5.14.11-051411-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Flashback:GNOME Date: Tue Oct 12 19:19:54 2021 InstallationDate: Installed on 2019-05-26 (869 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: wget UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: wget (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wget in Ubuntu. https://bugs.launchpad.net/bugs/1946714 Title: Unable to locally verify the issuer's authority. Status in wget package in Ubuntu: New Bug description: In a terminal, when I run the following: wget https://www.linz.govt.nz/sites/default/files/media/ntm/bsb/BSB_UPDATE.zip I get an error message about certificates, as follows. ERROR: cannot verify www.linz.govt.nz's certificate, issued by ‘CN=Thawte RSA CA 2018,OU=www.digicert.com,O=DigiCert Inc,C=US’: The file is not downloaded. I contacted the maintainers of the site, they declared there is no problem with the certificate. Of course, this probably isn't a problem with wget, or with curl which gives a similar error and the advice to go to this page: https://curl.se/docs/sslcerts.html Unfortunately that's way over my head, so I'm hoping someone helpful here can shed some light on the matter. Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: wget 1.20.3-1ubuntu1 Uname: Linux 5.14.11-051411-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Flashback:GNOME Date: Tue Oct 12 19:19:54 2021 InstallationDate: Installed on 2019-05-26 (869 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: wget UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1946714/+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 1886161] Re: Unattended upgrades should work on roaming laptops
** Summary changed: - UU should work on roaming laptops + Unattended upgrades should work on roaming laptops -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1886161 Title: Unattended upgrades should work on roaming laptops Status in apt package in Ubuntu: New Status in gnome-settings-daemon package in Ubuntu: Invalid Bug description: For many if not most laptop computers, Unattended Upgrades seems all but useless by design. For upgrades to happen, with default config, 3 conditions must be met: - an internet connection must be up and running when the timer or cron or anacron tries the unattended upgrade - the connection must not be metered, whatever that means (Skip-Updates-On-Metered-Connections "true") - the computer must be plugged in (OnlyOnACPower "true") These are insurmountable problems for many laptops on the go. Inevitably, security upgrades will almost never run unattended on such computers. I discovered with shock that Unattended Upgrades had almost never run on my laptop. I tried all possible config tweaks. Nothing worked reliably and in the end I gave up and wrote a upgrade script which uses Network Manager's connection-up hook. Unattended Upgrades needs to do something like this out of the box. Users should not need to write scripts to ensure security upgrades. Unattended upgrades is an excellent project for servers. But it really needs to work, out of the box, on laptops too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1886161/+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 1886161] Re: Unattended upgrades should work on roaming laptops
Just an update, for what it's worth. I solved this problem with a shell script triggered by Network Manager's "up" hook. Because UU does not update the package list, I had to resort to a `apt-get update && apt-get dist-upgrade` with `DEBIAN_FRONTEND=noninteractive` and a whole bunch of options to make sure everything runs reliably in the background. Convoluted and laborious. But now my Ubuntu is *always* up to date. Before, it regularly went *months* without a security update. Putting aside whose fault it is, this absolutely IS a problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1886161 Title: Unattended upgrades should work on roaming laptops Status in apt package in Ubuntu: New Status in gnome-settings-daemon package in Ubuntu: Invalid Bug description: For many if not most laptop computers, Unattended Upgrades seems all but useless by design. For upgrades to happen, with default config, 3 conditions must be met: - an internet connection must be up and running when the timer or cron or anacron tries the unattended upgrade - the connection must not be metered, whatever that means (Skip-Updates-On-Metered-Connections "true") - the computer must be plugged in (OnlyOnACPower "true") These are insurmountable problems for many laptops on the go. Inevitably, security upgrades will almost never run unattended on such computers. I discovered with shock that Unattended Upgrades had almost never run on my laptop. I tried all possible config tweaks. Nothing worked reliably and in the end I gave up and wrote a upgrade script which uses Network Manager's connection-up hook. Unattended Upgrades needs to do something like this out of the box. Users should not need to write scripts to ensure security upgrades. Unattended upgrades is an excellent project for servers. But it really needs to work, out of the box, on laptops too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1886161/+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 1829621] [NEW] No sound after suspend
Public bug reported: On my Laptop sound is working only after a fresh reboot. Every time I suspend the laptop, I can no longer use the internal speakers or any headphones. I tried a lot of solutions suggested online none of them working for me. Since this problem is very annoying I would really appreciate if a fix would be available. Thanks a lot :) Additional information: Laptop: HP 14-ma0307ng Ubuntu 19.04 Audio: sudo lspci -v | grep -A7 -i "audio" 00:0e.0 Audio device: Intel Corporation Device 3198 (rev 03) Subsystem: Hewlett-Packard Company Device 84b6 Flags: bus master, fast devsel, latency 0, IRQ 25 Memory at a131 (64-bit, non-prefetchable) [size=16K] Memory at a100 (64-bit, non-prefetchable) [size=1M] Capabilities: [50] Power Management version 3 Capabilities: [80] Vendor Specific Information: Len=14 Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+ ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: harry 5835 F pulseaudio /dev/snd/pcmC0D0c: harry 5835 F...m pulseaudio /dev/snd/pcmC0D0p: harry 5835 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat May 18 19:12:01 2019 InstallationDate: Installed on 2019-04-30 (18 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84B6 dmi.board.vendor: HP dmi.board.version: KBC Version 76.17 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.05:bd04/09/2018:svnHP:pnHPLaptop14-ma0xxx:pvrType1ProductConfigId:rvnHP:rn84B6:rvrKBCVersion76.17:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 14-ma0xxx dmi.product.sku: 4DL72EA#ABD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: 19.04 suspend-resume -- 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/1829621 Title: No sound after suspend Status in pulseaudio package in Ubuntu: New Bug description: On my Laptop sound is working only after a fresh reboot. Every time I suspend the laptop, I can no longer use the internal speakers or any headphones. I tried a lot of solutions suggested online none of them working for me. Since this problem is very annoying I would really appreciate if a fix would be available. Thanks a lot :) Additional information: Laptop: HP 14-ma0307ng Ubuntu 19.04 Audio: sudo lspci -v | grep -A7 -i "audio" 00:0e.0 Audio device: Intel Corporation Device 3198 (rev 03) Subsystem: Hewlett-Packard Company Device 84b6 Flags: bus master, fast devsel, latency 0, IRQ 25 Memory at a131 (64-bit, non-prefetchable) [size=16K] Memory at a100 (64-bit, non-prefetchable) [size=1M] Capabilities: [50] Power Management version 3 Capabilities: [80] Vendor Specific Information: Len=14 Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+ ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: harry 5835 F pulseaudio /dev/snd/pcmC0D0c: harry 5835 F...m pulseaudio /dev/snd/pcmC0D0p: harry 5835 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat May 18 19:12:01 2019 InstallationDate: Installed on 2019-04-30 (18 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84B6 dmi.board.vendor: HP dmi.board.version: KBC Version 76.17 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.05:bd04/09/2018:svnHP:pnHPLaptop14-ma0xxx:pvrType1ProductConfigId:rvnHP:rn84B6:rvrKBCVersion76.17:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 14-ma0xxx dmi.product.sku: 4DL72EA#ABD dmi.product.version: Type1ProductConfigI
[Touch-packages] [Bug 1829621] Re: [HP Laptop 14-ma0xxx] No sound after suspend
@vanvugt Thank you for your answer. I tried the kernel versions 5.0.0-13 and 4.3.0-04 as well. For the first one, the same problem occured (sound only after a fresh boot) and the second one couldn't be installed correctly because of missing libraries (a boot was possible, but e.g. the mouse pointer was not moving). I have already tried to reconfigure pulseaudio, to force alsa-audio to reload (it does reload but doesn't change anything). Here is my output of aplay: $ aplay -L default Playback/recording through the PulseAudio sound server null Discard all samples (playback) or generate zero samples (capture) jack JACK Audio Connection Kit pulse PulseAudio Sound Server sysdefault:CARD=PCH HDA Intel PCH, ALC236 Analog Default Audio Device front:CARD=PCH,DEV=0 HDA Intel PCH, ALC236 Analog Front speakers surround21:CARD=PCH,DEV=0 HDA Intel PCH, ALC236 Analog 2.1 Surround output to Front and Subwoofer speakers surround40:CARD=PCH,DEV=0 HDA Intel PCH, ALC236 Analog 4.0 Surround output to Front and Rear speakers surround41:CARD=PCH,DEV=0 HDA Intel PCH, ALC236 Analog 4.1 Surround output to Front, Rear and Subwoofer speakers surround50:CARD=PCH,DEV=0 HDA Intel PCH, ALC236 Analog 5.0 Surround output to Front, Center and Rear speakers surround51:CARD=PCH,DEV=0 HDA Intel PCH, ALC236 Analog 5.1 Surround output to Front, Center, Rear and Subwoofer speakers surround71:CARD=PCH,DEV=0 HDA Intel PCH, ALC236 Analog 7.1 Surround output to Front, Center, Side, Rear and Woofer speakers hdmi:CARD=PCH,DEV=0 HDA Intel PCH, HDMI 0 HDMI Audio Output hdmi:CARD=PCH,DEV=1 HDA Intel PCH, HDMI 1 HDMI Audio Output hdmi:CARD=PCH,DEV=2 HDA Intel PCH, HDMI 2 HDMI Audio Output hdmi:CARD=PCH,DEV=3 HDA Intel PCH, HDMI 3 HDMI Audio Output hdmi:CARD=PCH,DEV=4 HDA Intel PCH, HDMI 4 HDMI Audio Output dmix:CARD=PCH,DEV=0 HDA Intel PCH, ALC236 Analog Direct sample mixing device dmix:CARD=PCH,DEV=3 HDA Intel PCH, HDMI 0 Direct sample mixing device dmix:CARD=PCH,DEV=7 HDA Intel PCH, HDMI 1 Direct sample mixing device dmix:CARD=PCH,DEV=8 HDA Intel PCH, HDMI 2 Direct sample mixing device dmix:CARD=PCH,DEV=9 HDA Intel PCH, HDMI 3 Direct sample mixing device dmix:CARD=PCH,DEV=10 HDA Intel PCH, HDMI 4 Direct sample mixing device dsnoop:CARD=PCH,DEV=0 HDA Intel PCH, ALC236 Analog Direct sample snooping device dsnoop:CARD=PCH,DEV=3 HDA Intel PCH, HDMI 0 Direct sample snooping device dsnoop:CARD=PCH,DEV=7 HDA Intel PCH, HDMI 1 Direct sample snooping device dsnoop:CARD=PCH,DEV=8 HDA Intel PCH, HDMI 2 Direct sample snooping device dsnoop:CARD=PCH,DEV=9 HDA Intel PCH, HDMI 3 Direct sample snooping device dsnoop:CARD=PCH,DEV=10 HDA Intel PCH, HDMI 4 Direct sample snooping device hw:CARD=PCH,DEV=0 HDA Intel PCH, ALC236 Analog Direct hardware device without any conversions hw:CARD=PCH,DEV=3 HDA Intel PCH, HDMI 0 Direct hardware device without any conversions hw:CARD=PCH,DEV=7 HDA Intel PCH, HDMI 1 Direct hardware device without any conversions hw:CARD=PCH,DEV=8 HDA Intel PCH, HDMI 2 Direct hardware device without any conversions hw:CARD=PCH,DEV=9 HDA Intel PCH, HDMI 3 Direct hardware device without any conversions hw:CARD=PCH,DEV=10 HDA Intel PCH, HDMI 4 Direct hardware device without any conversions plughw:CARD=PCH,DEV=0 HDA Intel PCH, ALC236 Analog Hardware device with all software conversions plughw:CARD=PCH,DEV=3 HDA Intel PCH, HDMI 0 Hardware device with all software conversions plughw:CARD=PCH,DEV=7 HDA Intel PCH, HDMI 1 Hardware device with all software conversions plughw:CARD=PCH,DEV=8 HDA Intel PCH, HDMI 2 Hardware device with all software conversions plughw:CARD=PCH,DEV=9 HDA Intel PCH, HDMI 3 Hardware device with all software conversions plughw:CARD=PCH,DEV=10 HDA Intel PCH, HDMI 4 Hardware device with all software conversions usbstream:CARD=PCH HDA Intel PCH USB Stream Output -- 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/1829621 Title: [HP Laptop 14-ma0xxx] No sound after suspend Status in pulseaudio package in Ubuntu: Incomplete Bug description: On my Laptop sound is working only after a fresh reboot. Every time I suspend the laptop, I can no longer use the internal speakers or any headphones. I tried a lot of solutions suggested online none of them working for me. Since this problem is very annoying I would really appreciate if a fix would be available. Thanks a lot :) Additional information: Laptop: HP 14-ma0307ng Ubuntu 19.04 Audio: sudo lspci -v | grep -A7 -i "audio" 00:0e.0 Audio device: Intel Corporation Device 3198 (rev 03) Subsystem: Hewlett-Packard Company Devi
[Touch-packages] [Bug 1829621] Re: [HP Laptop 14-ma0xxx] No sound after suspend
It also affects kernel version 5.0.0-16 (installed from disco-proposed) -- 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/1829621 Title: [HP Laptop 14-ma0xxx] No sound after suspend Status in pulseaudio package in Ubuntu: Incomplete Bug description: On my Laptop sound is working only after a fresh reboot. Every time I suspend the laptop, I can no longer use the internal speakers or any headphones. I tried a lot of solutions suggested online none of them working for me. Since this problem is very annoying I would really appreciate if a fix would be available. Thanks a lot :) Additional information: Laptop: HP 14-ma0307ng Ubuntu 19.04 Audio: sudo lspci -v | grep -A7 -i "audio" 00:0e.0 Audio device: Intel Corporation Device 3198 (rev 03) Subsystem: Hewlett-Packard Company Device 84b6 Flags: bus master, fast devsel, latency 0, IRQ 25 Memory at a131 (64-bit, non-prefetchable) [size=16K] Memory at a100 (64-bit, non-prefetchable) [size=1M] Capabilities: [50] Power Management version 3 Capabilities: [80] Vendor Specific Information: Len=14 Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+ ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: harry 5835 F pulseaudio /dev/snd/pcmC0D0c: harry 5835 F...m pulseaudio /dev/snd/pcmC0D0p: harry 5835 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat May 18 19:12:01 2019 InstallationDate: Installed on 2019-04-30 (18 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84B6 dmi.board.vendor: HP dmi.board.version: KBC Version 76.17 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.05:bd04/09/2018:svnHP:pnHPLaptop14-ma0xxx:pvrType1ProductConfigId:rvnHP:rn84B6:rvrKBCVersion76.17:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 14-ma0xxx dmi.product.sku: 4DL72EA#ABD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1829621/+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 1829621] Re: [HP Laptop 14-ma0xxx] No sound after suspend
I was now able to try a few different versions leading to the following results: * The bug does not affect kernel version 4.18.0-15 (Tested using a Live install of 18.04.2) * The bug does not affect kernel version 4.20.17-042017 (Tested on my install of 19.04 with a manually installed kernel) * The bug does not affect kernel version 5.0.1-050001 (Tested on my install of 19.04 with a manually installed kernel) * The bug does affect newly build kernel version 5.1.5-050105 (Tested on my install of 19.04 with a manually installed kernel) So the bug must be introduced between 4.20.17 and 5.0.0-15. I hope this can be a good starting point for troubleshooting. -- 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/1829621 Title: [HP Laptop 14-ma0xxx] No sound after suspend Status in pulseaudio package in Ubuntu: Incomplete Bug description: On my Laptop sound is working only after a fresh reboot. Every time I suspend the laptop, I can no longer use the internal speakers or any headphones. I tried a lot of solutions suggested online none of them working for me. Since this problem is very annoying I would really appreciate if a fix would be available. Thanks a lot :) Additional information: Laptop: HP 14-ma0307ng Ubuntu 19.04 Audio: sudo lspci -v | grep -A7 -i "audio" 00:0e.0 Audio device: Intel Corporation Device 3198 (rev 03) Subsystem: Hewlett-Packard Company Device 84b6 Flags: bus master, fast devsel, latency 0, IRQ 25 Memory at a131 (64-bit, non-prefetchable) [size=16K] Memory at a100 (64-bit, non-prefetchable) [size=1M] Capabilities: [50] Power Management version 3 Capabilities: [80] Vendor Specific Information: Len=14 Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+ ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: harry 5835 F pulseaudio /dev/snd/pcmC0D0c: harry 5835 F...m pulseaudio /dev/snd/pcmC0D0p: harry 5835 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat May 18 19:12:01 2019 InstallationDate: Installed on 2019-04-30 (18 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84B6 dmi.board.vendor: HP dmi.board.version: KBC Version 76.17 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.05:bd04/09/2018:svnHP:pnHPLaptop14-ma0xxx:pvrType1ProductConfigId:rvnHP:rn84B6:rvrKBCVersion76.17:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 14-ma0xxx dmi.product.sku: 4DL72EA#ABD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1829621/+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 1829621] Re: [HP Laptop 14-ma0xxx] No sound after suspend
Indeed my conclusion was wrong because I mixed up the versions. The bug does affect some newer versions although it seems that it was solved in the meantime before reappearing again. To correct, I observed the following: * The bug does NOT affect kernel version 4.18.0-15 (Tested using a Live install of 18.04.2) * The bug does NOT affect kernel version 4.20.17-042017 (Tested on my install of 19.04 with a manually installed kernel) * The bug DOES affect kernel version 5.0.0-13 (Tested on my install of 19.04 with a manually installed kernel) * The bug DOES affect kernel version 5.0.0-15 (I used this version when I filed the bug report some days after I installed Ubuntu on my laptop) * The bug DOES affect kernel version 5.0.0-16 (Tested on my install of 19.04 with an update from disco-proposed using apt-get) * The bug does NOT affect kernel version 5.0.1-050001 (Tested on my install of 19.04 with a manually installed kernel) * The bug DOES affect newly build kernel version 5.1.5-050105 (Tested on my install of 19.04 with a manually installed kernel) I conclude, that the bug was introduced between 4.20.17 and 5.0.0-13, then solved between 5.0.0-16 and 5.0.1 only to be reintroduced in the most recent build (5.1.5). As you might notice, I am only a user, so I have limited skills. The change might also come from something else but I did not purposely change any setting or behavior while I tried the different versions. I tested the sound using the button in the sound-settings of Ubuntu and Spotify (both after a fresh boot and after suspend). -- 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/1829621 Title: [HP Laptop 14-ma0xxx] No sound after suspend Status in pulseaudio package in Ubuntu: Incomplete Bug description: On my Laptop sound is working only after a fresh reboot. Every time I suspend the laptop, I can no longer use the internal speakers or any headphones. I tried a lot of solutions suggested online none of them working for me. Since this problem is very annoying I would really appreciate if a fix would be available. Thanks a lot :) Additional information: Laptop: HP 14-ma0307ng Ubuntu 19.04 Audio: sudo lspci -v | grep -A7 -i "audio" 00:0e.0 Audio device: Intel Corporation Device 3198 (rev 03) Subsystem: Hewlett-Packard Company Device 84b6 Flags: bus master, fast devsel, latency 0, IRQ 25 Memory at a131 (64-bit, non-prefetchable) [size=16K] Memory at a100 (64-bit, non-prefetchable) [size=1M] Capabilities: [50] Power Management version 3 Capabilities: [80] Vendor Specific Information: Len=14 Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+ ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: harry 5835 F pulseaudio /dev/snd/pcmC0D0c: harry 5835 F...m pulseaudio /dev/snd/pcmC0D0p: harry 5835 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat May 18 19:12:01 2019 InstallationDate: Installed on 2019-04-30 (18 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84B6 dmi.board.vendor: HP dmi.board.version: KBC Version 76.17 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.05:bd04/09/2018:svnHP:pnHPLaptop14-ma0xxx:pvrType1ProductConfigId:rvnHP:rn84B6:rvrKBCVersion76.17:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 14-ma0xxx dmi.product.sku: 4DL72EA#ABD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1829621/+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 1585084] Re: Volume notification keeps popping up constantly (the notify-OSD bubble on top-right corner)
I have had this on ubuntu 18.04. Makes watching stuff with VLC so annoying put the mp4 onto a memory stick ad booted into the windows parition. -- 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/1585084 Title: Volume notification keeps popping up constantly (the notify-OSD bubble on top-right corner) Status in pulseaudio package in Ubuntu: Confirmed Bug description: I upgraded to Ubuntu 16.04 yesterday, I did a clean install while preserving the home directory which is mounted in a separate partition. Even during the installation I had constant volume notification bubble appearing on the top-right corner of my screen, it would come and go about twice every minute. I just thought it was due to installing hardware drivers or something but the problem persisted even when I booted into the freshly installed system. I did some searching and two users reported the exact problem. And one more suggested this happens because constant disconnect and reconnect of the sound card which makes sense as the sound settings flashes briefly during every popup. Someone on IRC suggested to kill pulseaudio and thus restart it, that does not fix the issue. I also tried the Live environment thinking it might be due to some old config files in home partition (which was preserved during upgrade), but this problem happens in the live environment as well, which makes sense because it was present during installation as well. Users with the same issue: http://ubuntuforums.org/showthread.php?t=2323815 http://askubuntu.com/questions/773008/constant-volume-osd-in-16-04 http://askubuntu.com/questions/767466/sound-card-being-disconnected-reconnected-constantly Thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: sidd 1651 F pulseaudio /dev/snd/controlC0: sidd 1651 F pulseaudio /dev/snd/controlC1: sidd 1651 F pulseaudio CurrentDesktop: Unity Date: Tue May 24 12:31:12 2016 InstallationDate: Installed on 2016-05-23 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0705 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A97EVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1585084/+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 1273275] Re: The osk shouldn't assume that active layout = language in use
This is definitely a bug, because layout does *not* imply typing language, as OP says. It is also surely the most important missing feature of the OSK. Lots of us are in this frustrating situation, having to choose between the right layout and the right dictionary. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1273275 Title: The osk shouldn't assume that active layout = language in use Status in ubuntu-keyboard: Confirmed Status in ubuntu-keyboard package in Ubuntu: Confirmed Bug description: The topic came while discussing https://wiki.ubuntu.com/LanguageAndText#phone-spelling It's quite frequent for users to stick to the keymap they know and use it to type in different language. By example a french user is going to use an azerty keymap even when writting english bug reports (example right here ;-) The current code makes the assumption that you want to spellcheck in the language matching the current keyboard layout, that's not true and should be changed. The design indicated earlier allows selecting several language which would be nice (so somebody using both his language and english could select both and not need to go change the settings between e.g emails) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-keyboard/+bug/1273275/+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 1427995] Re: lscpu -p is showing wrong values for Node component
For reference, the deployed fix shows correct result on an Intel i7 processor: Prior to update: … # CPU,Core,Socket,Node,,L1d,L1i,L2,L3 0,0,0,0,,0,0,0,0 1,1,0,0,,1,1,1,0 2,2,0,0,,2,2,2,0 3,3,0,0,,3,3,3,0 4,0,0,0,,0,0,0,0 5,1,0,0,,1,1,1,0 6,2,0,65,,2,2,2,0 7,3,0,0,,3,3,3,0 After update: … # CPU,Core,Socket,Node,,L1d,L1i,L2,L3 0,0,0,0,,0,0,0,0 1,1,0,0,,1,1,1,0 2,2,0,0,,2,2,2,0 3,3,0,0,,3,3,3,0 4,0,0,0,,0,0,0,0 5,1,0,0,,1,1,1,0 6,2,0,0,,2,2,2,0 7,3,0,0,,3,3,3,0 Note the previously incorrect result for CPU 6 is corrected on the updated version of lscpu -p -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1427995 Title: lscpu -p is showing wrong values for Node component Status in util-linux package in Ubuntu: Invalid Status in util-linux source package in Trusty: Fix Released Bug description: [Impact] Any user of lscpu on systems with multiple NUMA nodes. [Test case] On a POWER8 system: 1) Run 'lscpu'; take note of the values for "NUMA node# CPU(s)". 2) Run 'lscpu -p'. The values on the fourth column in lscpu -p output should match the node for which the CPU (first column) is listed (or contained in the displayed range). For example: $ lscpu [...] NUMA node0 CPU(s): 0-12,14-39 [...] NUMA node3 CPU(s): 13,40-79 [...] $ lscpu -p [...] 12,1,0,0,,1,1,1,1 13,1,0,3,,1,1,1,1 [...] 39,4,0,0,,4,4,4,4 40,5,1,3,,5,5,5,5 [..] The fourth column for CPU 12 and 39 is "0", which matches the "node0" range of 0-12,14-39. The fourth column for CPU 13 and 40 is "3", which matches the "node3" range 13,40-79. [Regression potential] This change is limited to the output of a command that can be parsed; so any regression would be erroneous values for node "names" or numbers, which may throw off data retrieved by parsing the output of lscpu. This particular bug constitutes the fix to a regression in a previous SRU (ubuntu7.4), which included changes to support discontinuous NUMA nodes, and introduced the code this SRU changes, so the regression potential is minimal (this particular feature of lscpu is already broken). --- ---Problem Description--- lscpu -p is showing wrong values for Node component ---uname output--- Linux ubuntu 3.16.0-25-generic #14-Ubuntu ppc64le ppc64le ppc64le GNU/Linux Machine Type = P8 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Install a P8 machine with Ubuntu 14.04.02 ISO image in Power NV mode. Then execute the below test scenario. root@ubuntu-daily:~# lscpu -p # The following is the parsable format, which can be fed to other # programs. Each different item in every column has an unique ID # starting from zero. # CPU,Core,Socket,Node,,L1d,L1i,L2,L3 0,0,0,0,,0,0,0,0 1,0,0,1,,0,0,0,0 2,0,0,16,,0,0,0,0 3,0,0,17,,0,0,0,0 4,0,0,0,,0,0,0,0 5,0,0,0,,0,0,0,0 6,0,0,33,,0,0,0,0 7,0,0,0,,0,0,0,0 8,1,0,0,,1,1,1,1 9,1,0,0,,1,1,1,1 10,1,0,-1429431768,,1,1,1,1 11,1,0,16383,,1,1,1,1 12,1,0,1852125029,,1,1,1,1 13,1,0,777213279,,1,1,1,1 14,1,0,81,,1,1,1,1 15,1,0,0,,1,1,1,1 16,2,0,1920169263,,2,2,2,2 17,2,0,1634235183,,2,2,2,2 18,2,0,1815045490,,2,2,2,2 19,2,0,1818321775,,2,2,2,2 20,2,0,1852125029,,2,2,2,2 21,2,0,777213279,,2,2,2,2 22,2,0,759583829,,2,2,2,2 23,2,0,1953836600,,2,2,2,2 24,3,0,1278163046,,3,3,3,3 25,3,0,1162698563,,3,3,3,3 26,3,0,1195463507,,3,3,3,3 27,3,0,1966035781,,3,3,3,3 28,3,0,762079604,,3,3,3,3 29,3,0,1970170220,,3,3,3,3 30,3,0,1869426296,,3,3,3,3 31,3,0,0,,3,3,3,3 32,4,1,0,,4,4,4,4 33,4,1,0,,4,4,4,4 34,4,1,177,,4,4,4,4 35,4,1,0,,4,4,4,4 36,4,1,269092192,,4,4,4,4 37,4,1,256,,4,4,4,4 38,4,1,1,,4,4,4,4 39,4,1,16383,,4,4,4,4 40,5,1,0,,5,5,5,5 41,5,1,0,,5,5,5,5 42,5,1,269096544,,5,5,5,5 43,5,1,256,,5,5,5,5 44,5,1,269092512,,5,5,5,5 45,5,1,256,,5,5,5,5 46,5,1,269097536,,5,5,5,5 47,5,1,256,,5,5,5,5 48,6,1,269092688,,6,6,6,6 49,6,1,256,,6,6,6,6 50,6,1,269098208,,6,6,6,6 51,6,1,256,,6,6,6,6 52,6,1,269096960,,6,6,6,6 53,6,1,256,,6,6,6,6 54,6,1,269097456,,6,6,6,6 55,6,1,256,,6,6,6,6 56,7,1,269096544,,7,7,7,7 57,7,1,256,,7,7,7,7 58,7,1,269098592,,7,7,7,7 59,7,1,256,,7,7,7,7 60,7,1,269097344,,7,7,7,7 61,7,1,256,,7,7,7,7 62,7,1,269098016,,7,7,7,7 63,7,1,256,,7,7,7,7 64,8,2,269096880,,8,8,8,8 65,8,2,256,,8,8,8,8 66,8,2,269098400,,8,8,8,8 67,8,2,256,,8,8,8,8 68,8,2,269097184,,8,8,8,8 69,8,2,256,,8,8,8,8 70,8,2,269097856,,8,8,8,8 71,8,2,256,,8,8,8,8 72,9,2,269096672,,9,9,9,9 73,9,2,256,,9,9,9,9 74,9,2,0,,9,9,9,9 75,9,2,0,,9,9,9,9 76,9,2,0,,9,9,9,9 77,9,2,0,,9,9,9,9 78,9,2,65,,9,9,9,9 79,9,2,0,,9,9,9,9 80,10,2,1920169263,,10,10,10,10 81,10,2,1634235183,,10,10,10,10 82,10,2,1815045490,,10,10,10,10 83,10,2,1818321775,,10,10,10,10 84,10,2,1852125029,,10,10,10,10 85,10,2,777213279,,
[Touch-packages] [Bug 1677934] [NEW] package libnss3 2:3.26.2-0ubuntu0.16.04.2 [modified: usr/share/doc/libnss3/changelog.Debian.gz] failed to install/upgrade: tentative de remplacement de « /usr/shar
Public bug reported: I would install a package and I have this problem. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libnss3 2:3.26.2-0ubuntu0.16.04.2 [modified: usr/share/doc/libnss3/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.8.0-45.48~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 AptOrdering: libnss3: Install libnss3: Configure libnss3: Configure NULL: ConfigurePending Architecture: amd64 Date: Fri Mar 31 02:45:46 2017 ErrorMessage: tentative de remplacement de « /usr/share/doc/libnss3/changelog.Debian.gz », qui est différent d'autres instances du paquet libnss3:i386 InstallationDate: Installed on 2017-03-08 (22 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: nss Title: package libnss3 2:3.26.2-0ubuntu0.16.04.2 [modified: usr/share/doc/libnss3/changelog.Debian.gz] failed to install/upgrade: tentative de remplacement de « /usr/share/doc/libnss3/changelog.Debian.gz », qui est différent d'autres instances du paquet libnss3:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nss (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1677934 Title: package libnss3 2:3.26.2-0ubuntu0.16.04.2 [modified: usr/share/doc/libnss3/changelog.Debian.gz] failed to install/upgrade: tentative de remplacement de « /usr/share/doc/libnss3/changelog.Debian.gz », qui est différent d'autres instances du paquet libnss3:i386 Status in nss package in Ubuntu: New Bug description: I would install a package and I have this problem. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libnss3 2:3.26.2-0ubuntu0.16.04.2 [modified: usr/share/doc/libnss3/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.8.0-45.48~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 AptOrdering: libnss3: Install libnss3: Configure libnss3: Configure NULL: ConfigurePending Architecture: amd64 Date: Fri Mar 31 02:45:46 2017 ErrorMessage: tentative de remplacement de « /usr/share/doc/libnss3/changelog.Debian.gz », qui est différent d'autres instances du paquet libnss3:i386 InstallationDate: Installed on 2017-03-08 (22 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: nss Title: package libnss3 2:3.26.2-0ubuntu0.16.04.2 [modified: usr/share/doc/libnss3/changelog.Debian.gz] failed to install/upgrade: tentative de remplacement de « /usr/share/doc/libnss3/changelog.Debian.gz », qui est différent d'autres instances du paquet libnss3:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1677934/+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 1651923] Re: apt https method decodes redirect locations and sends them to the destination undecoded.
Just checked apt 1.2.9 from proposed on an x86_64 16.04 system . The package ttf-mscorefonts-installer version 3.4+nmu1ubuntu2 fails to download font files, but rather returns a 403 error on the first file download attempt. Directly accessing the failed link through a browser gives the expected result of a download being offered. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1651923 Title: apt https method decodes redirect locations and sends them to the destination undecoded. Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Committed Status in apt source package in Yakkety: Fix Committed Bug description: [Impact] Downloads via HTTPS fail if the URL contains a space. This breaks packages like ttf-mscorefonts-installer and various third party hosters. [Test case] Check that /usr/lib/apt/apt-helper download-file http://kxstudio.linuxaudio.org/repo/pool/free/ardour4_4.7.0-1kxstudio1_i386.deb test.deb can successfully download the file (or at least start downloading it) and does not fail early with a 505 HTTP version not supported error message. [Regression potential] The added code is: Uri.Path = QuoteString(Uri.Path, "+~ "); Some servers might not like + or ~ being quoted. We use the same quoting call for the http method too, though, so it seems highly unlikely to cause an issue. [Original bug report] Distributor ID: Ubuntu Description: Ubuntu 16.10 Release: 16.10 Codename: yakkety apt version 1.3.3 (also tried 1.4-beta2 .deb, same results) When trying to install a package hosted on s3 from the kxstudio repo, the download fails with an HTTP error: nico@nico-lenovo-ubuntu:~/Downloads$ sudo apt-get install wineasio-amd64 Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: wine1.6-amd64 The following NEW packages will be installed wine1.6-amd64 wineasio-amd64 0 to upgrade, 2 to newly install, 0 to remove and 1 not to upgrade. Need to get 30.9 kB/32.6 kB of archives. After this operation, 184 kB of additional disk space will be used. Do you want to continue? [Y/n] y Err:1 http://kxstudio.linuxaudio.org/repo stable/free amd64 wineasio-amd64 amd64 0.9.0+git20110613-2kxstudio3 505 HTTP Version not supported E: Failed to fetch https://github-cloud.s3.amazonaws.com/releases/39372848/0f048802-2fb5-11e5-9d8c-907ec7b97c46.deb?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAISTNZFOVBIJMK3TQ/20161222/us-east-1/s3/aws4_request&X-Amz-Date=20161222T022041Z&X-Amz-Expires=300&X-Amz-Signature=750f9b2ee076dcb8ae6992cae911f43208b3eec41976362cebf694e3c72b7aef&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment; filename=wineasio-amd64_0.9.0.git20110613-2kxstudio3_amd64.deb&response-content-type=application/octet-stream 505 HTTP Version not supported E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? Error allegedly not present in Ubuntu 14.04 and 16.04 More details in these forum posts: https://github.com/KXStudio/Repository/issues/73#issuecomment-268649503 https://www.linuxmusicians.com/viewtopic.php?t=16056 https://www.drupal.org/node/2324991 (clues on root cause) ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: apt 1.3.3 ProcVersionSignature: Ubuntu 4.8.0-30.32-lowlatency 4.8.6 Uname: Linux 4.8.0-30-lowlatency x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Thu Dec 22 02:31:47 2016 InstallationDate: Installed on 2016-10-20 (62 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1651923/+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 1886161] [NEW] UU is almost useless on itinerant laptops
Public bug reported: For many if not most laptop computers, Unattended Upgrades seems all but useless by design. For upgrades to happen, with default config, 3 conditions must be met: - an internet connection must be up and running when the timer or cron or anacron tries the unattended upgrade - the connection must not be metered, whatever that means (Skip-Updates-On-Metered-Connections "true") - the computer must be plugged in (OnlyOnACPower "true") These are insurmountable problems for many laptops on the go. Inevitably, security upgrades will almost never run unattended on such computers. I discovered with shock that Unattended Upgrades had almost never run on my laptop. I tried all possible config tweaks. Nothing worked reliably and in the end I gave up and wrote a upgrade script which uses Network Manager's connection-up hook. Unattended Upgrades needs to do something like this out of the box. Users should not need to write scripts to ensure security upgrades. Unattended upgrades is an excellent project for servers. But it really needs to work, out of the box, on laptops too. ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1886161 Title: UU is almost useless on itinerant laptops Status in unattended-upgrades package in Ubuntu: New Bug description: For many if not most laptop computers, Unattended Upgrades seems all but useless by design. For upgrades to happen, with default config, 3 conditions must be met: - an internet connection must be up and running when the timer or cron or anacron tries the unattended upgrade - the connection must not be metered, whatever that means (Skip-Updates-On-Metered-Connections "true") - the computer must be plugged in (OnlyOnACPower "true") These are insurmountable problems for many laptops on the go. Inevitably, security upgrades will almost never run unattended on such computers. I discovered with shock that Unattended Upgrades had almost never run on my laptop. I tried all possible config tweaks. Nothing worked reliably and in the end I gave up and wrote a upgrade script which uses Network Manager's connection-up hook. Unattended Upgrades needs to do something like this out of the box. Users should not need to write scripts to ensure security upgrades. Unattended upgrades is an excellent project for servers. But it really needs to work, out of the box, on laptops too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1886161/+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 1886161] Re: UU should work on roaming laptops
** Summary changed: - UU is almost useless on itinerant laptops + UU should work on roaming laptops -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1886161 Title: UU should work on roaming laptops Status in unattended-upgrades package in Ubuntu: New Bug description: For many if not most laptop computers, Unattended Upgrades seems all but useless by design. For upgrades to happen, with default config, 3 conditions must be met: - an internet connection must be up and running when the timer or cron or anacron tries the unattended upgrade - the connection must not be metered, whatever that means (Skip-Updates-On-Metered-Connections "true") - the computer must be plugged in (OnlyOnACPower "true") These are insurmountable problems for many laptops on the go. Inevitably, security upgrades will almost never run unattended on such computers. I discovered with shock that Unattended Upgrades had almost never run on my laptop. I tried all possible config tweaks. Nothing worked reliably and in the end I gave up and wrote a upgrade script which uses Network Manager's connection-up hook. Unattended Upgrades needs to do something like this out of the box. Users should not need to write scripts to ensure security upgrades. Unattended upgrades is an excellent project for servers. But it really needs to work, out of the box, on laptops too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1886161/+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 1886161] Re: UU should work on roaming laptops
@rbalint As I detailed, the problems cannot *all* be resolved by config. The biggest one, the first above, is still there. If you turn on a laptop when (1) an update is overdue and (2) there is not yet an internet connection, then the update will not run even if the connection becomes available 5 minutes later. This is an **absolutely typical** situation when on the go and connecting to new wifi networks. Perhaps this is anacron's fault, or systemd's or something, I am not sure. What is certain is that, in the real world, in this common situation, unattended upgrades does not upgrade Ubuntu unattended. I believe that is a significant problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1886161 Title: UU should work on roaming laptops Status in unattended-upgrades package in Ubuntu: Invalid Bug description: For many if not most laptop computers, Unattended Upgrades seems all but useless by design. For upgrades to happen, with default config, 3 conditions must be met: - an internet connection must be up and running when the timer or cron or anacron tries the unattended upgrade - the connection must not be metered, whatever that means (Skip-Updates-On-Metered-Connections "true") - the computer must be plugged in (OnlyOnACPower "true") These are insurmountable problems for many laptops on the go. Inevitably, security upgrades will almost never run unattended on such computers. I discovered with shock that Unattended Upgrades had almost never run on my laptop. I tried all possible config tweaks. Nothing worked reliably and in the end I gave up and wrote a upgrade script which uses Network Manager's connection-up hook. Unattended Upgrades needs to do something like this out of the box. Users should not need to write scripts to ensure security upgrades. Unattended upgrades is an excellent project for servers. But it really needs to work, out of the box, on laptops too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1886161/+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 1882112] [NEW] Xorg freeze
Public bug reported: This may be correlated to the move to Bionic Beaver(?) LTS, now 18.04.4. It may also be correlated to getting low on disk space on my system drive (50GB SSD) and putting pressure on swap space. e.g when system HDD <= 1GB. My secondary HDD is a 1TB USB spinning device that sometimes seems to go into sleep mode and then fails to rapidly respond to IO request or may be is in a 'hot IO' state. On my Bus I have a low capacity HDD that is essentially unused because it rarely comes ready when I boot. If it is partially alive it is conceivable that it might be chattering and so competing for IO interrupt handling bandwidth? The problem only occurs when I have selected the desktop management tile from the 'side tray' and if I then shuffle or better align the windows inside one of the four desktops so as to stop them running into the neighbouring desktop area. Particularly, it seems to me, when at least one of the desktops is quite busy with windows open in it and the overlapped desktop has a few also. The fewer windows in total across the desktops the less likely it seems that rearranging a few will have any bad effect. When the freeze occurs then 60%(?) of the time it ends in a 'big red switch' reboot. The cursor stays active but ineffective. Keyboard combinations, like Alt+W, will sometimes succeed in bringing up to full screen mode and active the desktop that was in focus and constitutes a recovery. Other times, and keys, will delete focussed windows in the focussed desktop, and Tab will move focus around the 4 desktops. SHIFT+Print Screen also executes but just takes the whole screen and dumps it somewhere I haven't yet located... with sound effect. Hope this helps... I am not at fully at home with Ubuntu/Linux yet... having spent a lifetime on glasshouse legacy IBM mainframe field systems engineering. I am making myself more system disk space meanwhile, and while extract my old Maxtor. It would be nice if I didn't have to up my system disk to hundreds of GB! best regards, Rob ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 Uname: Linux 4.15.0-101-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Jun 4 11:31:56 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: I don't know GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7480D] [1002:9993] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Trinity [Radeon HD 7480D] [1043:8526] InstallationDate: Installed on 2016-11-27 (1284 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=1d959d4a-ac83-43a5-8c0f-a6956d68c1f8 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0802 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A55BM-E dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0802:bd10/10/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA55BM-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Aug 18 06:53:30 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd6
[Touch-packages] [Bug 1875985] Re: [Inspiron 13-5368, Realtek ALC3253, Speaker, Internal] No sound at all after kernel upgrade to 4.15.0-99-generic on Ubuntu 18.04.4
Bug confirmed for another Inspiron 13-5368. Under kernel 4.15.0-99 & Ubuntu 18.04.4 & Gnome desktop, there is no sound from internal speaker or on headphone jack, and also no microphone input signal. Other outputs (HDMI & BlueTooth) still work Previous kernel (4.15.0-96) works as expected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1875985 Title: [Inspiron 13-5368, Realtek ALC3253, Speaker, Internal] No sound at all after kernel upgrade to 4.15.0-99-generic on Ubuntu 18.04.4 Status in alsa-driver package in Ubuntu: New Bug description: VERSION="18.04.4 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.4 LTS" Running it in the flavour of Xubuntu. Just like in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875916 my sound stopped working with the new kernel "4.15.0-99-generic #100-Ubuntu SMP Wed Apr 22 20:32:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux". Rebooting into "4.15.0-96-generic #97-Ubuntu SMP Wed Apr 1 03:25:46 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux" sound works again. With 4.15.0-99-generic I do see a signal on the meters of the sound/volume control app, but physically there is no sound on either internal speakers nor on the headphones. With 4.15.0-96-generic everything is back to normal. My touchpad is working though (#1875916 seems to suggest that the touchpad stops working with 4.15.0-99-generic). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rkm1814 F pulseaudio CurrentDesktop: XFCE Date: Wed Apr 29 23:45:15 2020 InstallationDate: Installed on 2016-10-20 (1287 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rkm1814 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Inspiron 13-5368, Realtek ALC3253, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to bionic on 2018-08-31 (607 days ago) dmi.bios.date: 05/26/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.03.00 dmi.board.name: 0RJ0RW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.03.00:bd05/26/2016:svnDellInc.:pnInspiron13-5368:pvr:rvnDellInc.:rn0RJ0RW:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 13-5368 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1875985/+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 1382302] Re: Broadcom Corporation BCM4352 bluetooth adapter not finding any bluetooth devices
The description in #5 is not a fix, but rather a hack, which will have to be repeated for every kernel update. A true fix would involve: a) amending the btusb file b) including the fully BT capable firmware in a package If only a) is done, that would be a big improvement! Please note that 14.04 LTS will be using the 3.13.0 kernel until 2019, so this bug needs a robust fix! Thanks to redfox for getting to the bottom of it! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1382302 Title: Broadcom Corporation BCM4352 bluetooth adapter not finding any bluetooth devices Status in bluez package in Ubuntu: Fix Released Bug description: Broadcom Corporation BCM4352 wi-fi/bluetooth adapter is unable to find/detect Bluetooth devices, and Bluetooth devices can not see the Ubuntu PC, even when in pairing mode. (Here is a similar bug, but for a different Broadcom device: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1264311) MOTHERBOARD INFO $ sudo dmidecode -t baseboard # dmidecode 2.12 SMBIOS 2.7 present. Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: ASRock Product Name: Z87E-ITX Version: Serial Number: E80-34027900563 Asset Tag: Features: Board is a hosting board Board is replaceable Location In Chassis: Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 UBUNTU INFO $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.04.1 LTS Release: 14.04 Codename: trusty $ uname -a Linux Computer 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux WI-FI DEVICE INFO $ lspci | grep Broadcom 03:00.0 Network controller: Broadcom Corporation BCM4352 802.11ac Wireless Network Adapter (rev 03) Note, the BCM4352 802.11ac device is a combination Wi-Fi + Bluetooth adapter. BLUETOOTH DEVICE INFO $ lsusb Bus 002 Device 002: ID 8087:8000 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 13d3:3404 IMC Networks Bus 001 Device 002: ID 8087:8008 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 004: ID 1b1c:0c04 Corsair Bus 003 Device 003: ID 046d:0826 Logitech, Inc. Bus 003 Device 002: ID 09da:024f A4 Tech Co., Ltd RF Receiver and G6-20D Wireless Optical Mouse Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The system log does not show any errors when the btusb module is loaded... kernel: [36245.996355] usbcore: registered new interface driver btusb bluetoothd[833]: Unknown command complete for opcode 19 bluetoothd[833]: Endpoint registered: sender=:1.1820 path=/MediaEndpoint/HFPAG bluetoothd[833]: Endpoint registered: sender=:1.1820 path=/MediaEndpoint/HFPHS bluetoothd[833]: Endpoint registered: sender=:1.1820 path=/MediaEndpoint/A2DPSource bluetoothd[833]: Endpoint registered: sender=:1.1820 path=/MediaEndpoint/A2DPSink bluetoothd[833]: Endpoint registered: sender=:1.77 path=/MediaEndpoint/HFPAG bluetoothd[833]: Endpoint registered: sender=:1.77 path=/MediaEndpoint/HFPHS bluetoothd[833]: Endpoint registered: sender=:1.77 path=/MediaEndpoint/A2DPSource bluetoothd[833]: Endpoint registered: sender=:1.77 path=/MediaEndpoint/A2DPSink bluetoothd[833]: Adapter /org/bluez/833/hci0 has been enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1382302/+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 1634151] [NEW] package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: vereistenproblemen - triggers blijven onbehandeld
Public bug reported: Did an upgrade from Ubuntu 16.04 to 16.10, after rebooting the system the message occured ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 Uname: Linux 4.4.0-43-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Mon Oct 17 13:29:10 2016 ErrorMessage: vereistenproblemen - triggers blijven onbehandeld InstallationDate: Installed on 2016-05-04 (166 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: vereistenproblemen - triggers blijven onbehandeld UpgradeStatus: Upgraded to yakkety on 2016-10-17 (0 days ago) ** Affects: gconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1634151 Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: vereistenproblemen - triggers blijven onbehandeld Status in gconf package in Ubuntu: New Bug description: Did an upgrade from Ubuntu 16.04 to 16.10, after rebooting the system the message occured ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 Uname: Linux 4.4.0-43-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Mon Oct 17 13:29:10 2016 ErrorMessage: vereistenproblemen - triggers blijven onbehandeld InstallationDate: Installed on 2016-05-04 (166 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: vereistenproblemen - triggers blijven onbehandeld UpgradeStatus: Upgraded to yakkety on 2016-10-17 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1634151/+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 1458014] Re: audit_printk_skb slowing down boot
Hello I am tracking this bug as a very bemused sufferer. Please see attached bootchart from my system - hope it helps. ** Attachment added: "mopsie-trusty-20160301-1.png" https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1458014/+attachment/4585443/+files/mopsie-trusty-20160301-1.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1458014 Title: audit_printk_skb slowing down boot Status in apparmor package in Ubuntu: Confirmed Bug description: Subjectively, my system slowed down after the recent GRUB update. As you can see from the following, audit_printk_skb is consuming a lot of boot time: [ 13.243280] vboxdrv: Successfully loaded version 4.3.10_Ubuntu (interface 0x001a0007). [ 13.257947] vboxpci: IOMMU not found (not registered) [ 13.862999] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 13.865996] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 14.195776] r8169 :04:00.0 eth0: link down [ 14.195796] r8169 :04:00.0 eth0: link down [ 14.195827] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 14.196138] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 15.769090] r8169 :04:00.0 eth0: link up [ 15.769097] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 16.223084] init: plymouth-upstart-bridge main process ended, respawning [ 42.424836] audit_printk_skb: 195 callbacks suppressed [ 42.424839] type=1400 audit(1431891089.974:77): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=2632 comm="apparmor_parser" [ 42.424844] type=1400 audit(1431891089.974:78): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=2632 comm="apparmor_parser" [ 42.425185] type=1400 audit(1431891089.974:79): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=2632 comm="apparmor_parser" (END) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apparmor 2.8.95~2430-0ubuntu5.1 ProcVersionSignature: Ubuntu 3.13.0-53.88-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic i686 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: i386 CurrentDesktop: Unity Date: Fri May 22 14:18:46 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-04-29 (388 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=8cf458ab-4ff9-4505-9a16-27da1ea7ec10 ro quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1458014/+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 1563812] Re: gdb crashed with SIGABRT in dump_core()
*** This bug is a duplicate of bug 1544144 *** https://bugs.launchpad.net/bugs/1544144 ** Description changed: - banshee crashed while iPhone 5s is connected. + rhythmbox crashed while iPhone 5s is connected. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: gdb 7.11-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Mar 30 13:30:11 2016 ExecutablePath: /usr/bin/gdb InstallationDate: Installed on 2016-01-12 (77 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/bin/gdb -ex attach\ 18140 --ex info\ threads --ex thread\ apply\ all\ bt --batch Signal: 6 SourcePackage: gdb StacktraceTop: - dump_core () - ?? () - internal_verror () - internal_error () - ?? () + dump_core () + ?? () + internal_verror () + internal_error () + ?? () Title: gdb crashed with SIGABRT in dump_core() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1563812 Title: gdb crashed with SIGABRT in dump_core() Status in gdb package in Ubuntu: New Bug description: rhythmbox crashed while iPhone 5s is connected. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: gdb 7.11-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Mar 30 13:30:11 2016 ExecutablePath: /usr/bin/gdb InstallationDate: Installed on 2016-01-12 (77 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/bin/gdb -ex attach\ 18140 --ex info\ threads --ex thread\ apply\ all\ bt --batch Signal: 6 SourcePackage: gdb StacktraceTop: dump_core () ?? () internal_verror () internal_error () ?? () Title: gdb crashed with SIGABRT in dump_core() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1563812/+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 1511247] Re: Ubuntu 15.10 Could not apply the stored configuration for monitors
Got the same problem as described above by Crapouille. Using an Intel NUC with 42" LG TV screen (1920 X 1080) and Ubuntu 15.10. The image overflows but will fit with lower resolution, requiring changing DISPLAY settings. But at every startup the same annoying message appears again requiring re-entering the DISPLAY settings. Blindly deleting files may be a work around, but it is not really the solution. -- 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/1511247 Title: Ubuntu 15.10 Could not apply the stored configuration for monitors Status in xorg package in Ubuntu: Confirmed Bug description: I just did a fresh install of ubuntu 15.10 on my Nuc5i5ryh with a iiyama Prolite B2888UHSU and everytime I boot I get the message "Could not apply the stored configuration for monitors". When I kill the message it puts me back on a undesired resolution, and I have to set the resolution setting up again. Also when I set up the "Displays" settings , it shows screen resolution that souldn't be there (4:3, 16:10..). I tried removing monitors.xml just in case, doesn't work. I ran xrandr and sudo get-edid|parse-edid (see attached), it shows inconsistency between edid data and xrandr. I had Ubuntu 15.04 just before and I hadn't this error. Thanks ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu4 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: Thu Oct 29 16:19:11 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1626] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2057] InstallationDate: Installed on 2015-10-26 (2 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.vendor: Intel Corporation dmi.bios.version: RYBDWi35.86A.0350.2015.0812.1722 dmi.board.name: NUC5i5RYB dmi.board.vendor: Intel Corporation dmi.board.version: H40999-502 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0350.2015.0812.1722:bd08/12/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-502:cvn:ct3:cvr: version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Thu Oct 29 12:57:07 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 28932 vendor IVM xserver.version: 2:1.17.2-1ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1511247/+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 1511247] Re: Ubuntu 15.10 Could not apply the stored configuration for monitors
You describe more precisely exactly the same as I am seeing, with just a single screen. Now, being a total Newbie to Linux, I thought initially it was pilot error. I also need to use the Command Line commands, and after setting the screen size, I used the GUI desktop "Terminal" to access the login .. this works OK (against the purple background). But if I access the Command Line via "Ctrl+Alt+F1" (as recommended) the screen changes size back to overflowing (black background) and so you cannot see the prompts, which overflow on the left side. I notice also that an incorrect keyboard layout is now selected. I don't think this can be normal, so could this be something to do with the same bug? Or maybe its just my ignorance of the quirks of Ubuntu, and I still need to configure something else. -- 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/1511247 Title: Ubuntu 15.10 Could not apply the stored configuration for monitors Status in xorg package in Ubuntu: Confirmed Bug description: I just did a fresh install of ubuntu 15.10 on my Nuc5i5ryh with a iiyama Prolite B2888UHSU and everytime I boot I get the message "Could not apply the stored configuration for monitors". When I kill the message it puts me back on a undesired resolution, and I have to set the resolution setting up again. Also when I set up the "Displays" settings , it shows screen resolution that souldn't be there (4:3, 16:10..). I tried removing monitors.xml just in case, doesn't work. I ran xrandr and sudo get-edid|parse-edid (see attached), it shows inconsistency between edid data and xrandr. I had Ubuntu 15.04 just before and I hadn't this error. Thanks ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu4 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: Thu Oct 29 16:19:11 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1626] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2057] InstallationDate: Installed on 2015-10-26 (2 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.vendor: Intel Corporation dmi.bios.version: RYBDWi35.86A.0350.2015.0812.1722 dmi.board.name: NUC5i5RYB dmi.board.vendor: Intel Corporation dmi.board.version: H40999-502 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0350.2015.0812.1722:bd08/12/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-502:cvn:ct3:cvr: version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Thu Oct 29 12:57:07 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 28932 vendor IVM xserver.version: 2:1.17.2-1ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1511247/+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 1966787] Re: Totem crashes on launch | GStreamer-GL-CRITICAL **: Failed to flush Wayland connection | Gdk-Message: Error flushing display: Protocol error
*** This bug is a duplicate of bug 1965563 *** https://bugs.launchpad.net/bugs/1965563 Totem works in 22.10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1966787 Title: Totem crashes on launch | GStreamer-GL-CRITICAL **: Failed to flush Wayland connection | Gdk-Message: Error flushing display: Protocol error Status in NVIDIA / egl-wayland: Unknown Status in egl-wayland package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in totem package in Ubuntu: Confirmed Bug description: If I launch totem, it crashes pretty much immediately. I resolved this by deleting .config/totem. I had moved some video files that had been previously opened within it recently, so possibly it was trying to reference them (for thumbnails or whatever) and that broke it. robin@malik:~$ totem (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.832: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection (totem:5573): GStreamer-GL-CRITICAL **: 18:00:17.833: Failed to flush Wayland connection Gdk-Message: 18:00:17.844: Error flushing display: Protocol error robin@malik:~$ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: totem 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 28 18:00:39 2022 InstallationDate: Installed on 2022-03-23 (5 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/egl-wayland/+bug/1966787/+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 1822269] [NEW] mktemp does not handle -p option when --tmpdir option goes after -p option
Public bug reported: # This is correct. The printed temp file name is in folder / $ mktemp -u --tmpdir -p / /tmp.aFd4MwfGDU # after swapping the options, mktemp do not handle the -p option correctly. # swapping options should not affect the output. $ mktemp -u -p / --tmpdir /tmp/tmp.FkTPrEsTMs This should be a software bug, not relevant to any hardware. ** Affects: coreutils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1822269 Title: mktemp does not handle -p option when --tmpdir option goes after -p option Status in coreutils package in Ubuntu: New Bug description: # This is correct. The printed temp file name is in folder / $ mktemp -u --tmpdir -p / /tmp.aFd4MwfGDU # after swapping the options, mktemp do not handle the -p option correctly. # swapping options should not affect the output. $ mktemp -u -p / --tmpdir /tmp/tmp.FkTPrEsTMs This should be a software bug, not relevant to any hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1822269/+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 1822269] Re: mktemp does not handle -p option when --tmpdir option goes after -p option
Note: coreutils verions as shown by dpkg -l command: $ dpkg -l coreutils Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=-===-===-=== ii coreutils 8.21-1ubuntu5.4 amd64 GNU core utilities -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1822269 Title: mktemp does not handle -p option when --tmpdir option goes after -p option Status in coreutils package in Ubuntu: New Bug description: # This is correct. The printed temp file name is in folder / $ mktemp -u --tmpdir -p / /tmp.aFd4MwfGDU # after swapping the options, mktemp do not handle the -p option correctly. # swapping options should not affect the output. $ mktemp -u -p / --tmpdir /tmp/tmp.FkTPrEsTMs This should be a software bug, not relevant to any hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1822269/+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 1829885] [NEW] Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1)
Public bug reported: Encountered during a do-release-upgrade from 16.04.6 LTS to 18.04.2 LTS. Processing triggers for resolvconf (1.79ubuntu10.18.04.3) ... Errors were encountered while processing: ca-certificates ubuntu-release-upgrader-core update-manager-core update-notifier-common snapd ubuntu-core-launcher software-properties-common python3-httplib2 python3-certifi python3-requests python3-requests-unixsocket python3-apport apport landscape-common ubuntu-server ssh-import-id Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ca-certificates 20180409 ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176 Uname: Linux 4.4.0-145-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue May 21 16:11:17 2019 ErrorMessage: installed ca-certificates package post-installation script subprocess returned error exit status 23 InstallationDate: Installed on 2017-01-30 (840 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.10 SourcePackage: ca-certificates Title: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 23 UpgradeStatus: Upgraded to bionic on 2019-05-21 (0 days ago) ** Affects: ca-certificates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1829885 Title: Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) Status in ca-certificates package in Ubuntu: New Bug description: Encountered during a do-release-upgrade from 16.04.6 LTS to 18.04.2 LTS. Processing triggers for resolvconf (1.79ubuntu10.18.04.3) ... Errors were encountered while processing: ca-certificates ubuntu-release-upgrader-core update-manager-core update-notifier-common snapd ubuntu-core-launcher software-properties-common python3-httplib2 python3-certifi python3-requests python3-requests-unixsocket python3-apport apport landscape-common ubuntu-server ssh-import-id Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ca-certificates 20180409 ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176 Uname: Linux 4.4.0-145-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue May 21 16:11:17 2019 ErrorMessage: installed ca-certificates package post-installation script subprocess returned error exit status 23 InstallationDate: Installed on 2017-01-30 (840 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.10 SourcePackage: ca-certificates Title: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 23 UpgradeStatus: Upgraded to bionic on 2019-05-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1829885/+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 1771917] [NEW] com.ubuntu.apport-gtk-root
Public bug reported: com.ubuntu.apport-gtk-root ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 Uname: Linux 4.4.0-124-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 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: Thu May 17 22:36:12 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Haswell-ULT Integrated Graphics Controller [1179:f931] InstallationDate: Installed on 2016-04-21 (756 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: TOSHIBA Satellite L70-B ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic root=UUID=f8cee356-0708-45ca-8480-9665f2b427ff ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.20 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: MP dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.20:bd05/27/2014:svnTOSHIBA:pnSatelliteL70-B:pvrPSKRLC-00Y00G:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite L70-B dmi.product.version: PSKRLC-00Y00G dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu May 17 22:29:19 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 20555 vendor SEC xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- 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/1771917 Title: com.ubuntu.apport-gtk-root Status in xorg package in Ubuntu: New Bug description: com.ubuntu.apport-gtk-root ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 Uname: Linux 4.4.0-124-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 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: Thu May 17 22:36:12 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Haswell-ULT Integrated Graphics Controller [1179:f931] InstallationDate: Installed on 2016-04-21 (756 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: TOSHIBA Satellite L70-B ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic root=UUID=f8cee356-0708-45ca-8480-9665f2b427ff ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.20
[Touch-packages] [Bug 1771917] Re: com.ubuntu.apport-gtk-root
help me get rid of this error box, comes up everytime. I was trying to get access to adobe to download some coupons and I think that caused the problem. I still can't load adobe to print. -- 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/1771917 Title: com.ubuntu.apport-gtk-root Status in xorg package in Ubuntu: New Bug description: com.ubuntu.apport-gtk-root ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 Uname: Linux 4.4.0-124-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 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: Thu May 17 22:36:12 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Haswell-ULT Integrated Graphics Controller [1179:f931] InstallationDate: Installed on 2016-04-21 (756 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: TOSHIBA Satellite L70-B ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic root=UUID=f8cee356-0708-45ca-8480-9665f2b427ff ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.20 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: MP dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr1.20:bd05/27/2014:svnTOSHIBA:pnSatelliteL70-B:pvrPSKRLC-00Y00G:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite L70-B dmi.product.version: PSKRLC-00Y00G dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu May 17 22:29:19 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 20555 vendor SEC xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1771917/+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 1785236] [NEW] "dm-tool add-nested-seat" doesn't work normally
Public bug reported: Hello, since I've installed Xubuntu 18-04 (on 15 july 2018). The command "dm-tool add-nested-seat" doesn't work normally. I have a blank screen instead of a login screen. Maybe the problem is due to greeter cause when I set autologin for an user, then everything seems to work normally. The login screen is just skipped. [Impact] "dm-tool add-nested-seat" doesn't work (excepted when autologin-user is set). [Test Case] 1. Log in 2. From a terminal run "dm-tool add-nested-seat" [Expected result] A window opens with a login screen [Observed result] A window opens with a complete black screen if autologin-user isn't set in /etc/lightdm/lightdm.conf No error in the terminal. If autologin is set in /etc/lightdm/lightdm.conf, then it works normally. [used distribution] Xubuntu 18-04, up to date. I didn't have this trouble in may 2018 while I was under Xubuntu 17-10. [related trouble] maybe it's related to this bug: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1529454 But I don't exactly have the same trouble. So I thought I should open a new one. Sorry if I was wrong. ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: dm-tool lighdm -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1785236 Title: "dm-tool add-nested-seat" doesn't work normally Status in lightdm package in Ubuntu: New Bug description: Hello, since I've installed Xubuntu 18-04 (on 15 july 2018). The command "dm-tool add-nested-seat" doesn't work normally. I have a blank screen instead of a login screen. Maybe the problem is due to greeter cause when I set autologin for an user, then everything seems to work normally. The login screen is just skipped. [Impact] "dm-tool add-nested-seat" doesn't work (excepted when autologin-user is set). [Test Case] 1. Log in 2. From a terminal run "dm-tool add-nested-seat" [Expected result] A window opens with a login screen [Observed result] A window opens with a complete black screen if autologin-user isn't set in /etc/lightdm/lightdm.conf No error in the terminal. If autologin is set in /etc/lightdm/lightdm.conf, then it works normally. [used distribution] Xubuntu 18-04, up to date. I didn't have this trouble in may 2018 while I was under Xubuntu 17-10. [related trouble] maybe it's related to this bug: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1529454 But I don't exactly have the same trouble. So I thought I should open a new one. Sorry if I was wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1785236/+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 1785236] Re: "dm-tool add-nested-seat" doesn't work normally
** Description changed: Hello, - since I've installed Xubuntu 18-04 (on 15 july 2018). The command "dm-tool add-nested-seat" doesn't work normally. I have a blank screen instead of a login screen. Maybe the problem is due to greeter cause when I set autologin for an user, then everything seems to work normally. The login screen is just skipped. + since I installed Xubuntu 18-04 (on 15 july 2018). The command "dm-tool add-nested-seat" hasn't worked normally. I have a blank screen instead of a login screen. Maybe the problem is due to greeter cause when I set autologin for an user, then everything seems to work normally. The login screen is just skipped. [Impact] "dm-tool add-nested-seat" doesn't work (excepted when autologin-user is set). [Test Case] 1. Log in 2. From a terminal run "dm-tool add-nested-seat" [Expected result] A window opens with a login screen [Observed result] A window opens with a complete black screen if autologin-user isn't set in /etc/lightdm/lightdm.conf No error in the terminal. If autologin is set in /etc/lightdm/lightdm.conf, then it works normally. [used distribution] Xubuntu 18-04, up to date. I didn't have this trouble in may 2018 while I was under Xubuntu 17-10. [related trouble] maybe it's related to this bug: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1529454 But I don't exactly have the same trouble. So I thought I should open a new one. Sorry if I was wrong. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1785236 Title: "dm-tool add-nested-seat" doesn't work normally Status in lightdm package in Ubuntu: New Bug description: Hello, since I installed Xubuntu 18-04 (on 15 july 2018). The command "dm-tool add-nested-seat" hasn't worked normally. I have a blank screen instead of a login screen. Maybe the problem is due to greeter cause when I set autologin for an user, then everything seems to work normally. The login screen is just skipped. [Impact] "dm-tool add-nested-seat" doesn't work (excepted when autologin-user is set). [Test Case] 1. Log in 2. From a terminal run "dm-tool add-nested-seat" [Expected result] A window opens with a login screen [Observed result] A window opens with a complete black screen if autologin-user isn't set in /etc/lightdm/lightdm.conf No error in the terminal. If autologin is set in /etc/lightdm/lightdm.conf, then it works normally. [used distribution] Xubuntu 18-04, up to date. I didn't have this trouble in may 2018 while I was under Xubuntu 17-10. [related trouble] maybe it's related to this bug: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1529454 But I don't exactly have the same trouble. So I thought I should open a new one. Sorry if I was wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1785236/+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 1747871] [NEW] package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: I can't proceed with the update. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: util-linux 2.27.1-6ubuntu3.3 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Wed Feb 7 16:45:49 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2018-01-26 (12 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.19 SourcePackage: util-linux Title: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1747871 Title: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in util-linux package in Ubuntu: New Bug description: I can't proceed with the update. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: util-linux 2.27.1-6ubuntu3.3 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Wed Feb 7 16:45:49 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2018-01-26 (12 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.19 SourcePackage: util-linux Title: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1747871/+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 1515924] [NEW] Indicator-datetime events are in wrong time format with other language
Public bug reported: Hey! Indicator-datetime events are in wrong time format with other language.I use the rc-channel with the build of 12th November. I changed the language to Hungarian and added some events in the calendar, then I checked the datetime indicator: Expected: Névtelen17.00 NévtelenHolnap 9.00 Riasztás H 7.00 NévtelenNov. 21. Szo 9.00 What I see: Névtelen17:00 NévtelenTomorrow 09:00 Riasztás H 7:00 NévtelenSzo 21. nov. 09:00 So it's fully untranslated (tomorrow), partly untranslated (H 7:00) and in wrong format (Szo 21. nov. 09:00) It was okay with OTA-7. ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Status: Confirmed ** Attachment added: "screenshot20151113_101637990.png" https://bugs.launchpad.net/bugs/1515924/+attachment/4518086/+files/screenshot20151113_101637990.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1515924 Title: Indicator-datetime events are in wrong time format with other language Status in indicator-datetime package in Ubuntu: Confirmed Bug description: Hey! Indicator-datetime events are in wrong time format with other language.I use the rc-channel with the build of 12th November. I changed the language to Hungarian and added some events in the calendar, then I checked the datetime indicator: Expected: Névtelen17.00 NévtelenHolnap 9.00 Riasztás H 7.00 NévtelenNov. 21. Szo 9.00 What I see: Névtelen17:00 NévtelenTomorrow 09:00 Riasztás H 7:00 NévtelenSzo 21. nov. 09:00 So it's fully untranslated (tomorrow), partly untranslated (H 7:00) and in wrong format (Szo 21. nov. 09:00) It was okay with OTA-7. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1515924/+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 1512924] Re: Timestamps not localized in notifications
I'm coming from this bug: https://bugs.launchpad.net/ubuntu/+source /indicator-datetime/+bug/1515924 But I'm not sure this is the same issue. But what is more important: Is the milestone for this bug ww02-2016? But why? This is a really serious issue, I think it is a release-stopper for OTA-8. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1512924 Title: Timestamps not localized in notifications Status in Canonical System Image: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: Test case. - Flash the phone (krillin, with an external card inserted). - Select Spanish. - Reboot it. - Open the messaging menu. Expected result. - The storage notification timestamp is localized. Actual result. - Timestamp is shown in English. current build number: 163 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512924/+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 1506217] [NEW] Battery critical and will suspend in 30 seconds - at 54% charged
Public bug reported: I got a warning saying my Kubuntu laptop would suspend in 30 seconds because the battery level was critical. I plugged it into AC power in less than 30 seconds, however, it had already suspend by that point. When I pressed the power button to resume the laptop, the KDE login screen showed the battery at 54% charged, which does not seem like it should be considered critical. Ubuntu 15.04 ** Affects: upower (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1506217 Title: Battery critical and will suspend in 30 seconds - at 54% charged Status in upower package in Ubuntu: New Bug description: I got a warning saying my Kubuntu laptop would suspend in 30 seconds because the battery level was critical. I plugged it into AC power in less than 30 seconds, however, it had already suspend by that point. When I pressed the power button to resume the laptop, the KDE login screen showed the battery at 54% charged, which does not seem like it should be considered critical. Ubuntu 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1506217/+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 1439958] Re: Always receive duplicated SMS ans MMS
I don't know I saw this bug or an other, but two days ago I got an MMS and from this point I recieve it everyday the same time again and again, like a new message. But only with MMS. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1439958 Title: Always receive duplicated SMS ans MMS Status in messaging-app package in Ubuntu: Confirmed Bug description: When someone send me a SMS or MMS, I always receive it twice and sometimes for the MMS is 10 times. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1439958/+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 1447654] Re: installing policykit-1 hangs under systemd
Hi, I just encountered this bug on a mini computer board (Intel Celeron J1900 x4, 2GHz with 4096 MB of RAM). Ubuntu 15.04 Server for AMD64 I can give you every details for having this reproduced With a minimalist installation as I always do with Debian (approximately nothing is installed but Linux Kernel and apt-get - then I choose what I need and nothing else) For doing that : - I used "expert mode" by pressing "F6" at the boot of the installer (Legacy mode, not UEFI). - I didn't execute "Select and Install software". (because it loads and install many things I'm not going to use) I use the following sources.list : http://62.210.206.25:82/html/sources.list (extracted from a fully installed Ubuntu server 15.04 amd64) because when "Select and Install software" is not done, sources.list is keept untouched (so I replaced it manually from a live usb stick) Then I typed the following commands apt-get update apt-get upgrade apt-get install mate-desktop-environment lightdm Then it's freezing many times, whatever I try it always fails returning the same error : Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24) Failed to execute operation: Connection timed out dpkg: error processing package systemd (--unpack): subprocess installed post-installation script returned error exit status 1 Processing triggers for dbus (1.8.12-1ubuntu5) ... Errors were encountered while processing: systemd E: Sub-process /usr/bin/dpkg returned an error code (1) also : "error calling StartServiceByName for org.freedesktop.PolicyKit" or also : "cannot open /run/systemd/was-enabled no such file" But it continues after a while and then finish by Errors were encountered while processing: systemd E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1447654 Title: installing policykit-1 hangs under systemd Status in policykit-1 package in Ubuntu: Confirmed Status in policykit-1 source package in Vivid: Fix Released Bug description: I've installed 15.04 using the current amd64 netboot.tar.gz (MD5 = 6566065bf73a9c81feeddf5520dda122). It installs fine, but I'm getting errors installing packages (such as lubuntu-core). Last few lines from apt-get: Processing triggers for systemd (219-7ubuntu3) ... Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24) Failed to execute operation: Connection timed out dpkg: error processing package systemd (--unpack): subprocess installed post-installation script returned error exit status 1 Processing triggers for libglib2.0-0:amd64 (2.44.0-1ubuntu3) ... Processing triggers for shared-mime-info (1.3-1) ... Processing triggers for mime-support (3.58ubuntu1) ... Processing triggers for udev (219-7ubuntu3) ... Processing triggers for dbus (1.8.12-1ubuntu5) ... Errors were encountered while processing: systemd E: Sub-process /usr/bin/dpkg returned an error code (1) I've done a second install using the server iso and lubuntu-core installs fine on that. The only thing different was my install media. SRU INFORMATION === Test case: - Boot a minimal VM and purge "apport policykit-1", or do the above netboot installation. - sudo apt-get install policykit-1 apport - The above hangs on the systemd triggers and eventually fails in vivid final. It should succeed fine with this update. Regression potential: Very low: polkitd does not keep state, so one can restart it fine. The postinst shell modification is simple and obvious. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1447654/+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 1459310] [NEW] [HDA-Intel - HDA Intel PCH, playback] No sound at all
Public bug reported: all sound suddenly stoped working, no audio device is available in the sound settings menu. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robin 1231 F pulseaudio CurrentDesktop: Unity Date: Wed May 27 17:37:08 2015 InstallationDate: Installed on 2015-05-10 (17 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all ProcEnviron: LANGUAGE=sv PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Inbyggt ljud - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robin 1231 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1459310 Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: all sound suddenly stoped working, no audio device is available in the sound settings menu. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robin 1231 F pulseaudio CurrentDesktop: Unity Date: Wed May 27 17:37:08 2015 InstallationDate: Installed on 2015-05-10 (17 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all ProcEnviron: LANGUAGE=sv PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Inbyggt ljud - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robin 1231 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1459310/+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 1464187] [NEW] USB headphones too loud after suspend
Public bug reported: I have a pair of Plantronics 655 DSP USB headphones. They work fine but after suspend to RAM and resume, the volume is too loud. It fixes itself when I press a volume button on the device, when the volume reduces to the volume Ubuntu thinks it should have been (+/- 1 increment, because I am pressing the volume increase/decrease button). Driver is snd-usb-audio. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1464187 Title: USB headphones too loud after suspend Status in alsa-driver package in Ubuntu: New Bug description: I have a pair of Plantronics 655 DSP USB headphones. They work fine but after suspend to RAM and resume, the volume is too loud. It fixes itself when I press a volume button on the device, when the volume reduces to the volume Ubuntu thinks it should have been (+/- 1 increment, because I am pressing the volume increase/decrease button). Driver is snd-usb-audio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1464187/+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 1484980] Re: AVRCP support for Ubuntu Phone
Sorry, the volume buttons work, just the next and previous track buttons don't. ** Description changed: Hey! - I bought a bluetooth headphone, but the volume, next and previous track - buttons don't work with my Ubuntu Phone, because it doesn't support - AVRCP. So please implement this feature. :) + I bought a bluetooth headphone, but the next and previous track buttons + don't work with my Ubuntu Phone, because it doesn't support AVRCP. So + please implement this feature. :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1484980 Title: AVRCP support for Ubuntu Phone Status in Canonical System Image: Confirmed Status in indicator-sound package in Ubuntu: Confirmed Bug description: Hey! I bought a bluetooth headphone, but the next and previous track buttons don't work with my Ubuntu Phone, because it doesn't support AVRCP. So please implement this feature. :) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1484980/+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 1439958] Re: Always receive duplicated SMS ans MMS
Yes, it looks goodfor me too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1439958 Title: Always receive duplicated SMS ans MMS Status in messaging-app package in Ubuntu: Confirmed Bug description: When someone send me a SMS or MMS, I always receive it twice and sometimes for the MMS is 10 times. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1439958/+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 1471948] [NEW] package liblightdm-gobject-1-0 1.10.5-0ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting
Public bug reported: just booted and logged me in, then tryed to install the updates ProblemType: Package DistroRelease: Ubuntu 14.04 Package: liblightdm-gobject-1-0 1.10.5-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-55.94-generic 3.13.11-ckt20 Uname: Linux 3.13.0-55-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.11 AptOrdering: p7zip-full: Install liblightdm-gobject-1-0: Configure p7zip-full: Configure Architecture: amd64 Date: Mon Jul 6 20:59:10 2015 DuplicateSignature: package:liblightdm-gobject-1-0:1.10.5-0ubuntu1.1:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2011-08-13 (1423 days ago) InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 (20110720.1) LightdmConfig: [SeatDefaults] greeter-session=unity-greeter user-session=ubuntu SourcePackage: lightdm Title: package liblightdm-gobject-1-0 1.10.5-0ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to trusty on 2014-04-24 (437 days ago) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1471948 Title: package liblightdm-gobject-1-0 1.10.5-0ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in lightdm package in Ubuntu: New Bug description: just booted and logged me in, then tryed to install the updates ProblemType: Package DistroRelease: Ubuntu 14.04 Package: liblightdm-gobject-1-0 1.10.5-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-55.94-generic 3.13.11-ckt20 Uname: Linux 3.13.0-55-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.11 AptOrdering: p7zip-full: Install liblightdm-gobject-1-0: Configure p7zip-full: Configure Architecture: amd64 Date: Mon Jul 6 20:59:10 2015 DuplicateSignature: package:liblightdm-gobject-1-0:1.10.5-0ubuntu1.1:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2011-08-13 (1423 days ago) InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 (20110720.1) LightdmConfig: [SeatDefaults] greeter-session=unity-greeter user-session=ubuntu SourcePackage: lightdm Title: package liblightdm-gobject-1-0 1.10.5-0ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to trusty on 2014-04-24 (437 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1471948/+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
Re: [Touch-packages] [Bug 1383470] Re: scp does not work (fails at 'Sending command scp -v -t')
From: Serhiy Zahoriya <1383...@bugs.launchpad.net> Subject: [Bug 1383470] Re: scp does not work (fails at 'Sending command scp -v -t') Date: Mon, 22 May 2017 10:51:47 - > I've found a clue. It's a server with limited bandwidth and it's > currently using all of it. Not sure how the limit works, but I'm sure > that's the problem: something is placing nginx traffic above scp traffic > and the latter waits for hours. Thanks for this. Since the time of this initial report, I've changed server. At that time, I was on a DSL (!) connection, which of course had limited bandwidth, since fiber wasn't available at my location. However, I have seen an occasional long hang on scp and also on ssh since then, so the issue is perhaps still around (it was ATT in both cases, though now it's "Uverse", which does have a known problem with periodic drops on ssh connections, though ATT doesn't provide any help about this). > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1383470 > > Title: > scp does not work (fails at 'Sending command scp -v -t') > > Status in openssh package in Ubuntu: > Incomplete > > Bug description: > Following the last update of Ubuntu 14.02, scp (in the default system) has > ceased working. It hangs after authentication at the point where it wold > start an interactive session. I've verified that the problem is in my > system: scp still works at the target machine and scp won't work on my > machine to various hosts. Output below. > rasmith@rasmith-Lemur-Ultra:~$ scp -v testfil apacentral.org: > Executing: program /usr/bin/ssh host apacentral.org, user (unspecified), > command scp -v -t . > OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014 > debug1: Reading configuration data /home/rasmith/.ssh/config > debug1: /home/rasmith/.ssh/config line 17: Applying options for * > debug1: /home/rasmith/.ssh/config line 20: Deprecated option > "rhostsauthentication" > debug1: /home/rasmith/.ssh/config line 25: Deprecated option "fallbacktorsh" > debug1: /home/rasmith/.ssh/config line 26: Deprecated option "usersh" > debug1: Reading configuration data /etc/ssh/ssh_config > debug1: /etc/ssh/ssh_config line 19: Applying options for * > debug1: Connecting to apacentral.org [65.19.130.61] port 22. > debug1: Connection established. > debug1: could not open key file '/etc/ssh/ssh_host_key': No such file or > directory > debug1: could not open key file '/etc/ssh/ssh_host_dsa_key': Permission > denied > debug1: could not open key file '/etc/ssh/ssh_host_ecdsa_key': Permission > denied > debug1: could not open key file '/etc/ssh/ssh_host_rsa_key': Permission > denied > debug1: could not open key file '/etc/ssh/ssh_host_ed25519_key': No such > file or directory > debug1: could not open key file '/etc/ssh/ssh_host_dsa_key': Permission > denied > debug1: could not open key file '/etc/ssh/ssh_host_ecdsa_key': Permission > denied > debug1: could not open key file '/etc/ssh/ssh_host_rsa_key': Permission > denied > debug1: could not open key file '/etc/ssh/ssh_host_ed25519_key': No such > file or directory > debug1: identity file /home/rasmith/.ssh/identity type 0 > debug1: identity file /home/rasmith/.ssh/identity-cert type -1 > debug1: Remote protocol version 2.0, remote software version > OpenSSH_6.4_hpn13v11 FreeBSD-2013 > debug1: match: OpenSSH_6.4_hpn13v11 FreeBSD-2013 pat OpenSSH* compat > 0x0400 > debug1: Enabling compatibility mode for protocol 2.0 > debug1: Local version string SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2 > debug1: SSH2_MSG_KEXINIT sent > debug1: SSH2_MSG_KEXINIT received > debug1: kex: server->client aes128-ctr hmac-md5-...@openssh.com none > debug1: kex: client->server aes128-ctr hmac-md5-...@openssh.com none > debug1: sending SSH2_MSG_KEX_ECDH_INIT > debug1: expecting SSH2_MSG_KEX_ECDH_REPLY > debug1: Server host key: RSA 61:40:9f:26:85:d2:57:34:f9:52:7b:c3:47:9d:7a:ae > debug1: Host 'apacentral.org' is known and matches the RSA host key. > debug1: Found key in /home/rasmith/.ssh/known_hosts:26 > debug1: ssh_rsa_verify: signature correct > debug1: SSH2_MSG_NEWKEYS sent > debug1: expecting SSH2_MSG_NEWKEYS > debug1: SSH2_MSG_NEWKEYS received > debug1: Roaming not allowed by server > debug1: SSH2_MSG_SERVICE_REQUEST sent > debug1: SSH2_MSG_SERVICE_ACCEPT received > debug1: Authentications that can continue: publickey,keyboard-interactive > debug1: Next authentication method: publickey > debug1: Offering DSA public key: rasm...@aristotle.tamu.edu > debug1: Server accepts key: pkalg ssh-dss blen 433 > debug1: Authentication succeeded (publickey). > Authenticated to apacentral.org ([65.19.130.61]:22). > debug1: channel 0: new [client-session] > debug1: Requesting no-more-sessi...@openssh.com > debug1: Entering interactive session. > debug1: Sending environment. > debug1: Sending env LANG = e
[Touch-packages] [Bug 1696880] [NEW] Numbers overlap in the 'Dash to Dock' extension gui.
Public bug reported: There is some number overlap in the 'Dash to Dock' gui. In the 'Icon size limit' section. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170518-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Jun 8 18:38:13 2017 InstallationDate: Installed on 2017-06-08 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170607) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1696880 Title: Numbers overlap in the 'Dash to Dock' extension gui. Status in ubuntu-themes package in Ubuntu: New Bug description: There is some number overlap in the 'Dash to Dock' gui. In the 'Icon size limit' section. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170518-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Jun 8 18:38:13 2017 InstallationDate: Installed on 2017-06-08 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170607) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1696880/+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 1609700] Re: username is not saved in openconnect connection dialog
I'm also running into this bug and would like to see the fixed code reach Ubuntu 16.10. I was previously running Debian testing (Stretch) where I had the problem for a long time, but it eventually got patched. -- 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/1609700 Title: username is not saved in openconnect connection dialog Status in network-manager package in Ubuntu: Confirmed Status in network-manager-openconnect package in Ubuntu: Confirmed Status in Fedora: Unknown Bug description: Hi, I clicked on "save passwords" but only the password is filled in automatically when I open the connection dialog. The "Username" field is empty! This happens for a SSLVPN configuration. For another VPN config (don't know which type) everything is ok. openconnect: 7.06-2build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1609700/+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 1681513] Re: Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi adapters from working (MAC Address Randomization issue)
Many, many thanks, Jesse, for the fix! I have been using an ASUS N-13 adaptor, and up to Ubuntu 17.04 had no trouble. At first I suspected the adaptor and bought another one - quite unnecessarily as it turns out. Fortunately I had my little old friend, an ASUS Eee (also running Ubuntu 17.04), to help me, and so I was able to use it to ferret about, finally ending up at your posting. It worked! Evidently - and fortunately for me - the "improvement" to the network manager doesn't affect the Eee wifi card. Couldn't agree more with the above comments about the irresponsibility of the development team in fielding such a vital piece of software without very careful and extensive testing. Shame on you lot! There are probably a lot of ordinary users like me out there who just don't have a clue what is happening now their network connection isn't working. -- 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/1681513 Title: Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi adapters from working (MAC Address Randomization issue) Status in network-manager package in Ubuntu: Confirmed Bug description: According to https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0/ there is a new privacy feature in the new version of NetworkManager. This privacy feature can cause some USB WiFi adapters to stop working while they used to work with older versions of NetworkManager (Ubuntu 16.10 or older). The purpose of this privacy feature is to get your computer to report a new random MAC address whenever you connect to a WiFi network. This privacy feature is especially useful when you connect to public WiFi networks, so that the operators cannot identify you when you connect multiple times. The downside of this privacy feature is that some USB WiFi adapters misbehave when NetworkManager tries to change their MAC address repeatedly. The result is that those USB WiFi adapters cannot connect anymore to the WiFi network. Original report follows: My Panda USB wi-fi adapter works just fine on 16.10, but when I try to connect to my wi-fi router in 17.04, GNOME network manager reports "Connection failed." I did some tinkering, and noticed that my MAC address for my wifi adapter, according to GNOME, is DIFFERENT every time I make it forget my wifi settings and try to reconnect. Weird, right? Any leads on a possible fix or work-around? I'm running the latest beta of Ubuntu GNOME 17.04, kernel 4.10.0-19-generic, GNOME 3.24.0. https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in- networkmanager-1-4-0/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513/+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 1688023] [NEW] libcupsimage2-dev cannot be installed both in amd64 and i386
Public bug reported: Firstly, you should know that the bug reporting software did not work on the target machine. I have therefore been forced to make this bug report from a completely different machine, which means that the nicely automatically packaged information will all be utterly useless to you. The target machine is a freshly installed 16.04 64bit installation. I did: dpkg --add-architecture i386 after which: $ sudo dpkg --print-architecture amd64 $ sudo dpkg --print-foreign-architectures i386 I installed various C packages: sudo apt-get install gcc-multilib and I can happily build things in both 64bit and 32bit modes. Yay! Now, Ghostscript requires libcupsimage, but when I tried to build a 32bit ghostscript, I was told that libcupsimage was not found on the system. So I tried: sudo apt-get install libcupsimage2-dev:i386 whereupon it uninstalled libcupsimage2-dev:amd64. Doing: sudo apt-get install libcupsimage2-dev uninstalled the 64bit version. It looks like the 2 conflict: artifex@kilometers:~$ sudo apt-get install libcupsimage2-dev libcupsimage2-dev:i386 Reading package lists... Done Building dependency tree Reading state information... Done libcupsimage2-dev:i386 is already the newest version (2.1.3-4). Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libcupsimage2-dev : Depends: libcupsfilters-dev (>= 1.0~b1) but it is not going to be installed Conflicts: libcupsimage2-dev:i386 but 2.1.3-4 is to be installed libcupsimage2-dev:i386 : Conflicts: libcupsimage2-dev but 2.1.3-4 is to be installed E: Unable to correct problems, you have held broken packages. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libcupsimage2-dev 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-71.92-generic 4.4.49 Uname: Linux 4.4.0-71-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log' CurrentDesktop: Unity Date: Wed May 3 16:41:28 2017 InstallationDate: Installed on 2016-04-22 (375 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-71-generic root=UUID=6d12bf99-97ae-494a-a20d-ab13ca5de276 ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1688023 Title: libcupsimage2-dev cannot be installed both in amd64 and i386 Status in cups package in Ubuntu: New Bug description: Firstly, you should know that the bug reporting software did not work on the target machine. I have therefore been forced to make this bug report from a completely different machine, which means that the nicely automatically packaged information will all be utterly useless to you. The target machine is a freshly installed 16.04 64bit installation. I did: dpkg --add-architecture i386 after which: $ sudo dpkg --print-architecture amd64 $ sudo dpkg --print-foreign-architectures i386 I installed va
[Touch-packages] [Bug 1688023] Re: libcupsimage2-dev cannot be installed both in amd64 and i386
** Description changed: Firstly, you should know that the bug reporting software did not work on the target machine. I have therefore been forced to make this bug report from a completely different machine, which means that the nicely automatically packaged information will all be utterly useless to you. The target machine is a freshly installed 16.04 64bit installation. I did: - dpkg --add-architecture i386 + dpkg --add-architecture i386 after which: - $ sudo dpkg --print-architecture - amd64 - $ sudo dpkg --print-foreign-architectures - i386 + $ sudo dpkg --print-architecture + amd64 + $ sudo dpkg --print-foreign-architectures + i386 I installed various C packages: - sudo apt-get install gcc-multilib + sudo apt-get install gcc-multilib and I can happily build things in both 64bit and 32bit modes. Yay! Now, Ghostscript requires libcupsimage, but when I tried to build a 32bit ghostscript, I was told that libcupsimage was not found on the system. So I tried: - sudo apt-get install libcupsimage2-dev:i386 + sudo apt-get install libcupsimage2-dev:i386 whereupon it uninstalled libcupsimage2-dev:amd64. Doing: - sudo apt-get install libcupsimage2-dev + sudo apt-get install libcupsimage2-dev - uninstalled the 64bit version. + uninstalled the 32bit version. It looks like the 2 conflict: artifex@kilometers:~$ sudo apt-get install libcupsimage2-dev libcupsimage2-dev:i386 Reading package lists... Done Building dependency tree Reading state information... Done libcupsimage2-dev:i386 is already the newest version (2.1.3-4). Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: - libcupsimage2-dev : Depends: libcupsfilters-dev (>= 1.0~b1) but it is not going to be installed - Conflicts: libcupsimage2-dev:i386 but 2.1.3-4 is to be installed - libcupsimage2-dev:i386 : Conflicts: libcupsimage2-dev but 2.1.3-4 is to be installed + libcupsimage2-dev : Depends: libcupsfilters-dev (>= 1.0~b1) but it is not going to be installed + Conflicts: libcupsimage2-dev:i386 but 2.1.3-4 is to be installed + libcupsimage2-dev:i386 : Conflicts: libcupsimage2-dev but 2.1.3-4 is to be installed E: Unable to correct problems, you have held broken packages. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libcupsimage2-dev 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-71.92-generic 4.4.49 Uname: Linux 4.4.0-71-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log' CurrentDesktop: Unity Date: Wed May 3 16:41:28 2017 InstallationDate: Installed on 2016-04-22 (375 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: - Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. -Users in the 'systemd-journal' group can see all messages. Pass -q to -turn off this notice. - No journal files were opened due to insufficient permissions. + Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. + Users in the 'systemd-journal' group can see all messages. Pass -q to + turn off this notice. + No journal files were opened due to insufficient permissions. Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub - Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse - Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub + Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse + Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-71-generic root=UUID=6d12bf99-97ae-494a-a20d-ab13ca5de276 ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version:
Re: [Touch-packages] [Bug 1383470] Re: scp does not work (fails at 'Sending command scp -v -t')
From: Joshua Powers Subject: [Bug 1383470] Re: scp does not work (fails at 'Sending command scp -v -t') Date: Wed, 17 May 2017 21:33:14 - > Hi, > > This is an older bug, but came up during the daily server team bug > triage because of the recent comments. The last comment seems to > indicate that this is no longer an issue. I did attempt to do an scp > from trusty to another system using version 6.6p1-2ubuntu2.8 and found > no issues. > > If this is still an issue can you please comment confirming the issue > and provide your steps to reproduce? As you've surmised, this ancient issue is long gone. Robin Smith > > Thanks! > > ** Changed in: openssh (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1383470 > > Title: > scp does not work (fails at 'Sending command scp -v -t') > > Status in openssh package in Ubuntu: > Incomplete > > Bug description: > Following the last update of Ubuntu 14.02, scp (in the default system) has > ceased working. It hangs after authentication at the point where it wold > start an interactive session. I've verified that the problem is in my > system: scp still works at the target machine and scp won't work on my > machine to various hosts. Output below. > rasmith@rasmith-Lemur-Ultra:~$ scp -v testfil apacentral.org: > Executing: program /usr/bin/ssh host apacentral.org, user (unspecified), > command scp -v -t . > OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014 > debug1: Reading configuration data /home/rasmith/.ssh/config > debug1: /home/rasmith/.ssh/config line 17: Applying options for * > debug1: /home/rasmith/.ssh/config line 20: Deprecated option > "rhostsauthentication" > debug1: /home/rasmith/.ssh/config line 25: Deprecated option "fallbacktorsh" > debug1: /home/rasmith/.ssh/config line 26: Deprecated option "usersh" > debug1: Reading configuration data /etc/ssh/ssh_config > debug1: /etc/ssh/ssh_config line 19: Applying options for * > debug1: Connecting to apacentral.org [65.19.130.61] port 22. > debug1: Connection established. > debug1: could not open key file '/etc/ssh/ssh_host_key': No such file or > directory > debug1: could not open key file '/etc/ssh/ssh_host_dsa_key': Permission > denied > debug1: could not open key file '/etc/ssh/ssh_host_ecdsa_key': Permission > denied > debug1: could not open key file '/etc/ssh/ssh_host_rsa_key': Permission > denied > debug1: could not open key file '/etc/ssh/ssh_host_ed25519_key': No such > file or directory > debug1: could not open key file '/etc/ssh/ssh_host_dsa_key': Permission > denied > debug1: could not open key file '/etc/ssh/ssh_host_ecdsa_key': Permission > denied > debug1: could not open key file '/etc/ssh/ssh_host_rsa_key': Permission > denied > debug1: could not open key file '/etc/ssh/ssh_host_ed25519_key': No such > file or directory > debug1: identity file /home/rasmith/.ssh/identity type 0 > debug1: identity file /home/rasmith/.ssh/identity-cert type -1 > debug1: Remote protocol version 2.0, remote software version > OpenSSH_6.4_hpn13v11 FreeBSD-2013 > debug1: match: OpenSSH_6.4_hpn13v11 FreeBSD-2013 pat OpenSSH* compat > 0x0400 > debug1: Enabling compatibility mode for protocol 2.0 > debug1: Local version string SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2 > debug1: SSH2_MSG_KEXINIT sent > debug1: SSH2_MSG_KEXINIT received > debug1: kex: server->client aes128-ctr hmac-md5-...@openssh.com none > debug1: kex: client->server aes128-ctr hmac-md5-...@openssh.com none > debug1: sending SSH2_MSG_KEX_ECDH_INIT > debug1: expecting SSH2_MSG_KEX_ECDH_REPLY > debug1: Server host key: RSA 61:40:9f:26:85:d2:57:34:f9:52:7b:c3:47:9d:7a:ae > debug1: Host 'apacentral.org' is known and matches the RSA host key. > debug1: Found key in /home/rasmith/.ssh/known_hosts:26 > debug1: ssh_rsa_verify: signature correct > debug1: SSH2_MSG_NEWKEYS sent > debug1: expecting SSH2_MSG_NEWKEYS > debug1: SSH2_MSG_NEWKEYS received > debug1: Roaming not allowed by server > debug1: SSH2_MSG_SERVICE_REQUEST sent > debug1: SSH2_MSG_SERVICE_ACCEPT received > debug1: Authentications that can continue: publickey,keyboard-interactive > debug1: Next authentication method: publickey > debug1: Offering DSA public key: rasm...@aristotle.tamu.edu > debug1: Server accepts key: pkalg ssh-dss blen 433 > debug1: Authentication succeeded (publickey). &g
[Touch-packages] [Bug 1342429] Re: ubuntu-bug crashes when there's no sources.list
This is still a bug in a supported version. robin@taniwha:/etc/apt$ sudo mv sources.list sources.list.bak [sudo] wachtwoord voor robin: robin@taniwha:/etc/apt$ ubuntu-bug apport Gtk-Message: 11:56:56.196: GtkDialog mapped without a transient parent. This is discouraged. [... displays the message in the attached screenshot ...] robin@taniwha:/etc/apt$ sudo mv sources.list.bak sources.list robin@taniwha:/etc/apt$ ubuntu-bug apport [... proceeds to collect data like normal ...] robin@taniwha:/etc/apt$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.4 LTS Release:18.04 Codename: bionic ** Attachment added: "Selectie_417.png" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1342429/+attachment/5334264/+files/Selectie_417.png ** Changed in: apport (Ubuntu) Status: Incomplete => 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/1342429 Title: ubuntu-bug crashes when there's no sources.list Status in apport package in Ubuntu: New Bug description: $ ubuntu-bug apport *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. Traceback (most recent call last): File "/usr/bin/apport-cli", line 365, in if not app.run_argv(): File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 554, in run_argv return self.run_report_bug() File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 359, in run_report_bug self.collect_info(symptom_script) File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 874, in collect_info icthread.exc_raise() File "/usr/lib/python2.7/dist-packages/apport/REThread.py", line 34, in run self._retval = self.__target(*self.__args, **self.__kwargs) File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 74, in thread_collect_info report.add_package_info(package) File "/usr/lib/python2.7/dist-packages/apport/report.py", line 219, in add_package_info version = packaging.get_version(package) File "/usr/lib/python2.7/dist-packages/apport/packaging_impl.py", line 92, in get_version pkg = self._apt_pkg(package) File "/usr/lib/python2.7/dist-packages/apport/packaging_impl.py", line 85, in _apt_pkg return self._cache()[package] File "/usr/lib/python2.7/dist-packages/apport/packaging_impl.py", line 53, in _cache self._apt_cache = apt.Cache(progress, rootdir='/') File "/usr/lib/python2.7/dist-packages/apt/cache.py", line 101, in __init__ self._check_and_create_required_dirs(rootdir) File "/usr/lib/python2.7/dist-packages/apt/cache.py", line 131, in _check_and_create_required_dirs open(rootdir + f, "w").close() IOError: [Errno 13] Permission denied: '//etc/apt/sources.list' If I run it with sudo, then it makes a zero-byte sources.list file. The reason we don't have a sources.list is that puppet manages the files in /etc/apt/sources.list.d according to the needs of the server. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: apport 2.0.1-0ubuntu17.6 ProcVersionSignature: Ubuntu 3.8.0-42.63~precise1-generic 3.8.13.23 Uname: Linux 3.8.0-42-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 CrashReports: 640:3276:106:13876:2014-07-16 11:35:09.958702133 +1200:2014-07-16 11:35:09.958702133 +1200:/var/crash/_usr_bin_apport-bug.3276.crash Date: Wed Jul 16 11:46:54 2014 MarkForUpload: True PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1342429/+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 1414677] [NEW] Tab completion for new "apt" command doesn't work in trusty
Public bug reported: The one problem I've found with the new "apt" command (in trusty) is that unlike with "apt-get", tab completion doesn't work. Someone's posted a solution here: http://askubuntu.com/questions/445637/can-i-enable-bash-completion-for- the-new-apt-command It looks like this might be a bash-level problem (or zsh, or whetever shell you use), rather than apt-specific, but I thought I'd post it here as people who care about this project should presumably also care about tab completion working properly. Do you think it's feasible to expect tab-completion by 1504? ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Description changed: The one problem I've found with the new "apt" command (in trusty) is that unlike with "apt-get", tab completion doesn't work. Someone's posted a solution here: http://askubuntu.com/questions/445637/can-i-enable-bash-completion-for- the-new-apt-command It looks like this might be a bash-level problem (or zsh, or whetever shell you use), rather than apt-specific, but I thought I'd post it here as people who care about this project should presumably also care about tab completion working properly. - Do you think we could have tab-completion by 1504? + Do you think it's feasible to expect tab-completion by 1504? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1414677 Title: Tab completion for new "apt" command doesn't work in trusty Status in apt package in Ubuntu: New Bug description: The one problem I've found with the new "apt" command (in trusty) is that unlike with "apt-get", tab completion doesn't work. Someone's posted a solution here: http://askubuntu.com/questions/445637/can-i-enable-bash-completion- for-the-new-apt-command It looks like this might be a bash-level problem (or zsh, or whetever shell you use), rather than apt-specific, but I thought I'd post it here as people who care about this project should presumably also care about tab completion working properly. Do you think it's feasible to expect tab-completion by 1504? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1414677/+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 1357321] Re: scope images do not load in HSDPA or 3G
Sounds like a problem in the QtNetwork bearer plugin you're using. I'd guess that would be networkmanager (qtbase/src/plugins/bearer/networkmanager/), but I'm not sure if that's correct. P.S. (re comment #6): Bearer plugins, while platform specific, are not related to QPA. QPA is strictly for graphical abstraction, as the network backend is not tied to the display system used (for instance, Sailfish uses ConnMan, even though many desktop Linuxes use NM). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1357321 Title: scope images do not load in HSDPA or 3G Status in Platform API: New Status in The Savilerow project: New Status in The Unity 8 shell: Opinion Status in “qtubuntu” package in Ubuntu: New Bug description: scope images load fine in wifi, but not on hsdpa even when there is good connectivity and browsing works well. Results are return, but images do not load. To manage notifications about this bug go to: https://bugs.launchpad.net/platform-api/+bug/1357321/+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 1442105] Re: GPS not working on my BQ Ubuntu Touch
I affected too. I'm using the last release (r21) on the bq device. GPS on, HERE terms accepted, SIM inserted, mobile data enabled (it works for browsing) and last day I tried outside for about 40 minutes without luck. Any idea? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-location in Ubuntu. https://bugs.launchpad.net/bugs/1442105 Title: GPS not working on my BQ Ubuntu Touch Status in indicator-location package in Ubuntu: Confirmed Bug description: Hi. I tried to use GPS (HERE maps, Google Maps) on my Ubuntu Touch from BQ (I am on update 20), but the app dont detect my location. I have to mention that I check Here terms & Condition and GPS and location are checked. I attached some screenshot from what I did. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1442105/+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 1442105] Re: GPS not working on my BQ Ubuntu Touch
Today I tried it again. I sat out to the balcon, so I didn't move. And it worked. :) With enabled GPS and mobile data, it took 15 minutes to got a signal. So it works, but 15 minutes is too much time. In my Android phone it took about 2 minutes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-location in Ubuntu. https://bugs.launchpad.net/bugs/1442105 Title: GPS not working on my BQ Ubuntu Touch Status in indicator-location package in Ubuntu: Confirmed Bug description: Hi. I tried to use GPS (HERE maps, Google Maps) on my Ubuntu Touch from BQ (I am on update 20), but the app dont detect my location. I have to mention that I check Here terms & Condition and GPS and location are checked. I attached some screenshot from what I did. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1442105/+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 1648354] [NEW] Autoload with Opcache allows importing conflicting class name to namespace
Public bug reported: There is a buf in php which was fixed regarding php/opcache. Is there a chance of backporting this? => https://bugs.php.net/bug.php?id=66773 ** Affects: php5 (Ubuntu) Importance: Undecided Status: Invalid ** Package changed: upstart (Ubuntu) => php5 (Ubuntu) ** Bug watch added: bugs.php.net/ #66773 http://bugs.php.net/bug.php?id=66773 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1648354 Title: Autoload with Opcache allows importing conflicting class name to namespace Status in php5 package in Ubuntu: Invalid Bug description: There is a buf in php which was fixed regarding php/opcache. Is there a chance of backporting this? => https://bugs.php.net/bug.php?id=66773 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1648354/+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 1620636] Re: Fails to pair with Bose QC35 headphones
This is ubuntu desktop. I found that if I did: sudo hciconfig hci0 lp HOLD,SNIFF while everything was disconnected, then the audio started working properly. Now I'm back here because after a reboot it wouldn't connect at all, so I guess I need to fix the pairing or something. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1620636 Title: Fails to pair with Bose QC35 headphones Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: In Progress Bug description: I am unable to pair the Bose QC35 BT headphones with Ubuntu, either Ubuntu desktop running 16.04 LTS with bluez 5.37 (also tried bluez 5.41 from installed from yakkety archive), nor using Ubuntu Touch rc- proposed build for Turbo #174. I'm trying to pair through the normal bluetooth control panel brought up through the bluetooth indicator. I've attached some logs that show it failing to pair. If I can provide anymore useful information about the headphones, please let me know. Syslog with bluetoothd debugging enabled: http://pastebin.ubuntu.com/23141394/ btmon output: http://pastebin.ubuntu.com/23141446/ bluetoothctl output: http://pastebin.ubuntu.com/23141510/ With Linux kernel 4.8.0 and bluez 4.52: --- bluetoothctl: http://pastebin.ubuntu.com/23256457/ btmon: http://pastebin.ubuntu.com/23256471/ To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620636/+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 1574568] Re: Missing dual monitor support
Why is this a "whish"? I use this feature everyday on Unity7. This should be a basic feature on Unity8 too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1574568 Title: Missing dual monitor support Status in Canonical System Image: In Progress Status in qtmir package in Ubuntu: In Progress Status in unity8 package in Ubuntu: In Progress Bug description: A wish list suggestion to use the tablet along with the monitor or TV like if we were using 2 monitors. Duplicate screens, share screens etc... to use them as two different work desktops To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1574568/+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 1588526] Re: [mako] Alarm doesn't ring when screen locked
Is Nexus4 a no longer supported device? :O This is the only phone what a new user can buy. I don't think it's a good decision. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1588526 Title: [mako] Alarm doesn't ring when screen locked Status in Canonical System Image: Incomplete Status in Ubuntu Clock App: Confirmed Status in indicator-datetime package in Ubuntu: Confirmed Bug description: Hello, I noticed couple of time, difficult to reproduce that the alarm does not ring at the correct time but ring as soon the screen is on. Mako Rc-proposed bq-aquaris R324. Regards Edit : to make ring the phone i just need to wake up the phone and the alarm start to ring. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588526/+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 1408963] Re: [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945 0000:03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from... by lo
I had never heard of this problem until upgrading to 16.10 yesterday. Now my HP DV6000 is suffering from this exact problem, about 5 times in less than 24 hours since the upgrade. -- 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/1408963 Title: [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945 :03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from... by local choice (Reason: 3=DEAUTH_LEAVING), Status in network-manager package in Ubuntu: Incomplete Bug description: From time to time, the system loses all wireles networks and kubuntu network manager applet goes blank - not even one network is shown. All wifi connections are broken. Rebooting fixes the issue, switching to WICD on-the-fly enables to continue browsing without rebooting, so it seems to be no hardware issue or iwl3945 issue. What to expect: stable connections and flawless network managing. What happens: so above. Further informations about the system, the network configuration, the package version can be found in the attachment, also parts of rsyslog and dmesg. Interesting, according to some helpers, are the following lines: dmesg: wlan0: deauthenticating from 02:26:4d:ac:8f:45 by local choice (Reason: 3=DEAUTH_LEAVING) lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.10 Release:14.10 Codename: utopic apt-cache policy network-manager network-manager: Installiert: 0.9.8.8-0ubuntu28 Installationskandidat: 0.9.8.8-0ubuntu28 Versionstabelle: *** 0.9.8.8-0ubuntu28 0 500 http://de.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1408963/+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 1421923] Re: No notifications for new mails
Any update on this? As I know the work is ready on Ubuntu's side, no we only need a new Dekko release, don't we? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1421923 Title: No notifications for new mails Status in Online Accounts: Account plugins: New Status in Canonical System Image: In Progress Status in Dekko: In Progress Status in account-plugins package in Ubuntu: In Progress Status in account-polld package in Ubuntu: In Progress Bug description: Hi! In the BQ E4.5 Ubuntu Edition, I'm not getting notificactions for new mails. Testing (by example) 1. Kill Dekko. 2. Send you an email. 3. Open Dekko. 4. Change quickly to another app before Dekko starts. 5. Bug: No notification 6. Go to Dekko: You'll see your new mail. FYI as improvement, for me, in Dekko is not clear if Dekko checks the mail after X minutes or is a push notification. Thanks in advance! To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1421923/+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 1620636] Re: Fails to pair with Bose QC35 headphones
Following the instructions here: http://askubuntu.com/questions/833322 /pair-bose-quietcomfort-35-with-ubuntu-16-04-over-bluetooth I managed to make it pair and appear as an audio device. While playback technically worked, it wasn't useable as it came across as though there wasn't enough bandwidth - the audio was choppy and got delayed. It seemed that pulse gave up sending to it after a point, and nothing would play back then. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1620636 Title: Fails to pair with Bose QC35 headphones Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: In Progress Bug description: I am unable to pair the Bose QC35 BT headphones with Ubuntu, either Ubuntu desktop running 16.04 LTS with bluez 5.37 (also tried bluez 5.41 from installed from yakkety archive), nor using Ubuntu Touch rc- proposed build for Turbo #174. I'm trying to pair through the normal bluetooth control panel brought up through the bluetooth indicator. I've attached some logs that show it failing to pair. If I can provide anymore useful information about the headphones, please let me know. Syslog with bluetoothd debugging enabled: http://pastebin.ubuntu.com/23141394/ btmon output: http://pastebin.ubuntu.com/23141446/ bluetoothctl output: http://pastebin.ubuntu.com/23141510/ With Linux kernel 4.8.0 and bluez 4.52: --- bluetoothctl: http://pastebin.ubuntu.com/23256457/ btmon: http://pastebin.ubuntu.com/23256471/ To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620636/+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 1421923] Re: No notifications for new mails
Will this land in OTA-13? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1421923 Title: No notifications for new mails Status in Online Accounts: Account plugins: New Status in Canonical System Image: In Progress Status in Dekko: In Progress Status in account-plugins package in Ubuntu: In Progress Status in account-polld package in Ubuntu: In Progress Bug description: Hi! In the BQ E4.5 Ubuntu Edition, I'm not getting notificactions for new mails. Testing (by example) 1. Kill Dekko. 2. Send you an email. 3. Open Dekko. 4. Change quickly to another app before Dekko starts. 5. Bug: No notification 6. Go to Dekko: You'll see your new mail. FYI as improvement, for me, in Dekko is not clear if Dekko checks the mail after X minutes or is a push notification. Thanks in advance! To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1421923/+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 1469220] Re: [dialer] Dialer should allow me to block nuisance calls
There's a number, who calls me a lot in the early hours, and I can't block it, because this feature is missing, as a workaround I need to turn off my phone every evening, which is not the best solution. :) Is there any plan to support this in an upcoming OTA release, like OTA-14? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1469220 Title: [dialer] Dialer should allow me to block nuisance calls Status in Ubuntu UX: Confirmed Status in dialer-app package in Ubuntu: Confirmed Bug description: Title says it all. I have a very old number and get a lot of businesses trying to get my custom (by annoying me, ironically). I had them block on my last phone but I'm getting them again. Please implement this. The messages app equivalent is bug 1469535. --- UX comment & resolution --- To block a number: 1. Open dialer 2. Carry out a bottom edge swipe to access your Recent calls 3. Swipe towards the left on the entry/number you would like to block 4. tap the Info icon 5. see the revealed details about the caller and select the BLOCK option at the bottom of the page Please refer to the latest UX spec here: https://docs.google.com/document/d/1BRy9 -DEXr3A1D7PHkJaXmjbe7xbRmxKkzANXuu-F6lc/edit Please refer to the latest visual spec here: https://docs.google.com/presentation/d/1XMHRg7T3KxMizExeRTmXJGar0WOUyBQ4A8lEMnQvcqA/edit#slide=id.g34bd6a2bc_417 Visuals attached to bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1469220/+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 1584965] Re: [browser] scrolling uneven and queues up
This is one of the most annoying issues with the browsing experience. Could you figure out a solution for OTA-14? I'd really appreciate it. Thanks. :) -- 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/1584965 Title: [browser] scrolling uneven and queues up Status in Canonical System Image: Confirmed Status in Oxide: New Status in webbrowser-app package in Ubuntu: Confirmed Bug description: I've noticed this on a bunch of websites, mainly on Arale but also on krillin, both running latest rc-proposed with and without oxide 1.15 The scenario is I'm on page A, navigate to page B, press back button, then try to scroll page A (flicking up). The page doesn't move for a short time then scrolls super fast almost to the bottom. Seems like the scroll events are getting queued up and then all applied at once. This site reproduces it pretty easy for me: 1) goto boston.craigslist.org 2) type "kayak" in the search field 3) you'll get a page full of results 4) click on one of the results 5) wait till page fully loads, flick quickly a few times, first flicks ignored. then press back button 6) wait till page fully loads and then start scrolling (flicking up, multiple times), first flicks ignored/queued then scrolling happens fast Expected results: the page should start scrolling immediately and keep up with action of finger Actual results: the page is not responsive for a few seconds then scrolls super fast toward the bottom To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1584965/+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 1590776] Re: hide selection handle when start typing
Has this feature landed yet? Because I tried with today's image from rc- proposed channel, and I don't find it. :) -- 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/1590776 Title: hide selection handle when start typing Status in Canonical System Image: In Progress Status in Oxide: Fix Released Status in Oxide 1.15 series: Fix Released Status in Oxide 1.16 series: Fix Released Status in webbrowser-app package in Ubuntu: Invalid Bug description: we are showing the selection handle (in addition to the cursor) whenever entering a text field that already has text in it. For example, if you are replying to a Gmail message, you have an annoying blue selection handle blinking where you are trying to type and you can't turn it off. Or on a form, focusing on a field to append text will also show the selection handle. Or a multi line text area, adding a new line and typing at the beginning. Tested Chrome on Android and it behaves differently, and think we should do similar: 1. Show the selection handle initially, but have it disappear when you press any key (space, character, etc.) 2. Tapping anywhere in the field will cause handle to be shown again 3. Also, can we put the selection handle on the bottom of the cursor instead of the top? This is the behavior on Chrome for Android and the rest of our non-html platform in Ubuntu touch. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590776/+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 1590776] Re: hide selection handle when start typing
Yes, I know that OTA-12 hasn't been released yet. My question is about the rc-proposed channel. :) As I see Oxide 1.16.8 was released on 23th of August in this image: http://people.canonical.com/~lzemczak/landing- team/ubuntu-touch/rc-proposed/bq-aquaris.en/krillin/413.commitlog -- 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/1590776 Title: hide selection handle when start typing Status in Canonical System Image: In Progress Status in Oxide: Fix Released Status in Oxide 1.15 series: Fix Released Status in Oxide 1.16 series: Fix Released Status in webbrowser-app package in Ubuntu: Invalid Bug description: we are showing the selection handle (in addition to the cursor) whenever entering a text field that already has text in it. For example, if you are replying to a Gmail message, you have an annoying blue selection handle blinking where you are trying to type and you can't turn it off. Or on a form, focusing on a field to append text will also show the selection handle. Or a multi line text area, adding a new line and typing at the beginning. Tested Chrome on Android and it behaves differently, and think we should do similar: 1. Show the selection handle initially, but have it disappear when you press any key (space, character, etc.) 2. Tapping anywhere in the field will cause handle to be shown again 3. Also, can we put the selection handle on the bottom of the cursor instead of the top? This is the behavior on Chrome for Android and the rest of our non-html platform in Ubuntu touch. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590776/+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 1590776] Re: hide selection handle when start typing
Oh, I think I got it now. Yes, it hides the selection handle if it's "closed". If it's "open", so the Copy/Paste items are visible, it doesn't hide them, if If I start typing. Plus as I see it doesn't work at all in the Messaging app. By the way, thanks for your answers and the feature too of course. :) -- 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/1590776 Title: hide selection handle when start typing Status in Canonical System Image: In Progress Status in Oxide: Fix Released Status in Oxide 1.15 series: Fix Released Status in Oxide 1.16 series: Fix Released Status in webbrowser-app package in Ubuntu: Invalid Bug description: we are showing the selection handle (in addition to the cursor) whenever entering a text field that already has text in it. For example, if you are replying to a Gmail message, you have an annoying blue selection handle blinking where you are trying to type and you can't turn it off. Or on a form, focusing on a field to append text will also show the selection handle. Or a multi line text area, adding a new line and typing at the beginning. Tested Chrome on Android and it behaves differently, and think we should do similar: 1. Show the selection handle initially, but have it disappear when you press any key (space, character, etc.) 2. Tapping anywhere in the field will cause handle to be shown again 3. Also, can we put the selection handle on the bottom of the cursor instead of the top? This is the behavior on Chrome for Android and the rest of our non-html platform in Ubuntu touch. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590776/+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 1590776] Re: hide selection handle when start typing
I've attached a video. It is a Nexus4 with the latest rc-proposed image. I opened the Browser, when the menu is closed it disappears if I start typing. But if it's open, it doesn't. ** Attachment added: "video20160825_105050088.mp4" https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1590776/+attachment/4727430/+files/video20160825_105050088.mp4 -- 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/1590776 Title: hide selection handle when start typing Status in Canonical System Image: In Progress Status in Oxide: Fix Released Status in Oxide 1.15 series: Fix Released Status in Oxide 1.16 series: Fix Released Status in webbrowser-app package in Ubuntu: Invalid Bug description: we are showing the selection handle (in addition to the cursor) whenever entering a text field that already has text in it. For example, if you are replying to a Gmail message, you have an annoying blue selection handle blinking where you are trying to type and you can't turn it off. Or on a form, focusing on a field to append text will also show the selection handle. Or a multi line text area, adding a new line and typing at the beginning. Tested Chrome on Android and it behaves differently, and think we should do similar: 1. Show the selection handle initially, but have it disappear when you press any key (space, character, etc.) 2. Tapping anywhere in the field will cause handle to be shown again 3. Also, can we put the selection handle on the bottom of the cursor instead of the top? This is the behavior on Chrome for Android and the rest of our non-html platform in Ubuntu touch. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590776/+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 1616841] [NEW] hide selection handle when start typing
Public bug reported: This is a similar bug report as this: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1590776 Just this is about the standard UI toolkit component for text input, not for the oxide ones. I think it would be good if the system manages this the same everywhere. So please implement the same feature for this too. Thanks. Description of the Oxide bug report for easier understand: we are showing the selection handle (in addition to the cursor) whenever entering a text field that already has text in it. For example, if you are replying to a Gmail message, you have an annoying blue selection handle blinking where you are trying to type and you can't turn it off. Or on a form, focusing on a field to append text will also show the selection handle. Or a multi line text area, adding a new line and typing at the beginning. Tested Chrome on Android and it behaves differently, and think we should do similar: 1. Show the selection handle initially, but have it disappear when you press any key (space, character, etc.) 2. Tapping anywhere in the field will cause handle to be shown again 3. Also, can we put the selection handle on the bottom of the cursor instead of the top? This is the behavior on Chrome for Android and the rest of our non-html platform in Ubuntu touch. ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1616841 Title: hide selection handle when start typing Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: This is a similar bug report as this: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1590776 Just this is about the standard UI toolkit component for text input, not for the oxide ones. I think it would be good if the system manages this the same everywhere. So please implement the same feature for this too. Thanks. Description of the Oxide bug report for easier understand: we are showing the selection handle (in addition to the cursor) whenever entering a text field that already has text in it. For example, if you are replying to a Gmail message, you have an annoying blue selection handle blinking where you are trying to type and you can't turn it off. Or on a form, focusing on a field to append text will also show the selection handle. Or a multi line text area, adding a new line and typing at the beginning. Tested Chrome on Android and it behaves differently, and think we should do similar: 1. Show the selection handle initially, but have it disappear when you press any key (space, character, etc.) 2. Tapping anywhere in the field will cause handle to be shown again 3. Also, can we put the selection handle on the bottom of the cursor instead of the top? This is the behavior on Chrome for Android and the rest of our non-html platform in Ubuntu touch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1616841/+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 1590776] Re: hide selection handle when start typing
Thanks, I've filled a bug report and sorry for the confusion. :) https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1616841 -- 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/1590776 Title: hide selection handle when start typing Status in Canonical System Image: In Progress Status in Oxide: Fix Released Status in Oxide 1.15 series: Fix Released Status in Oxide 1.16 series: Fix Released Status in webbrowser-app package in Ubuntu: Invalid Bug description: we are showing the selection handle (in addition to the cursor) whenever entering a text field that already has text in it. For example, if you are replying to a Gmail message, you have an annoying blue selection handle blinking where you are trying to type and you can't turn it off. Or on a form, focusing on a field to append text will also show the selection handle. Or a multi line text area, adding a new line and typing at the beginning. Tested Chrome on Android and it behaves differently, and think we should do similar: 1. Show the selection handle initially, but have it disappear when you press any key (space, character, etc.) 2. Tapping anywhere in the field will cause handle to be shown again 3. Also, can we put the selection handle on the bottom of the cursor instead of the top? This is the behavior on Chrome for Android and the rest of our non-html platform in Ubuntu touch. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590776/+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 1602522] [NEW] The new Calendar on indicator doesn't use the translation's date format
Public bug reported: On the rc-proposed channel there is a calendar (again) on the datetime indicator, but it doesn't use the date format of the system's language. See the screenshot It shows „Július 2016”, but as you see above on the image, it should be „2016 július”. ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Status: Confirmed ** Attachment added: "screenshot20160713_082439609.png" https://bugs.launchpad.net/bugs/1602522/+attachment/4699860/+files/screenshot20160713_082439609.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1602522 Title: The new Calendar on indicator doesn't use the translation's date format Status in indicator-datetime package in Ubuntu: Confirmed Bug description: On the rc-proposed channel there is a calendar (again) on the datetime indicator, but it doesn't use the date format of the system's language. See the screenshot It shows „Július 2016”, but as you see above on the image, it should be „2016 július”. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1602522/+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 1368788] Re: Ubuntu One T&C string/link not in pot file
Still happens on OTA-10.1 and rc-proposed too. Any update on this? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntuone-credentials in Ubuntu. https://bugs.launchpad.net/bugs/1368788 Title: Ubuntu One T&C string/link not in pot file Status in Ubuntu Translations: Triaged Status in ubuntuone-credentials package in Ubuntu: Triaged Bug description: This string has not been catched by the xgettext 'I agree to the https://one.ubuntu.com/terms/";>Ubuntu One T&Cs' So currently is not translated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1368788/+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 1582173] Re: Missing translation from the content hub
@Ken: Sorry for the late reply, the language of the device is Hungarian. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to content-hub in Ubuntu. https://bugs.launchpad.net/bugs/1582173 Title: Missing translation from the content hub Status in Canonical System Image: Confirmed Status in Telegram app: Fix Committed Status in content-hub package in Ubuntu: Invalid Bug description: Missing translation (Choose) on the content hub. It is not available for translation on Launchpad. See the attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1582173/+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 1373463] Re: [indicators] Impossible to disable cellular data from indicator
I don't see the toggle/switch on the indicator with the latest rc- proposed image. Has this update landed yet? -- 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/1373463 Title: [indicators] Impossible to disable cellular data from indicator Status in Canonical System Image: In Progress Status in Ubuntu UX: Triaged Status in indicator-network package in Ubuntu: Fix Released Status in ubuntu-system-settings package in Ubuntu: Fix Released Bug description: I was wondering : Why it isn't possible to disable data from the network indicator ? Probably with a switch button that offer the choice between no data or data activated (with the last data activated state (2g only or 2G,3G,4G). Why this ? Because it's the first setting to change to save battery, and probably one of the most used (I asked around me, everyone agreed they would prefer that over Wi-Fi if only one was possible). I think it's stupid to go to the settings app for the most common action (and very frustrating). Of course, this also apply for the battery setting page (that already contain Wi-Fi, GPS, Bluetooth and brightness settings). I asked that on the phone ML, I've been invited to file a wishlist bug there to "help" designers with next iteration of network indicator. So here it is ! [1] : mailing list discussion with already some support to this idea : https://lists.launchpad.net/ubuntu-phone/msg09910.html To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1373463/+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 1569582] Re: Add Bluetooth apparmor policy
@Michael: Does this mean after OTA-11 you can publich your Bluetooth app to the official Ubuntu Store? :) Or we will still need to use wich is published in the OpenStore? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1569582 Title: Add Bluetooth apparmor policy Status in Canonical System Image: Fix Committed Status in apparmor-easyprof-ubuntu package in Ubuntu: Fix Released Bug description: I have created a content hub plugin that allows sending files via Bluetooth. At this point this only works when unconfined so here is a request to extend the apparmor policies to allow some things over Bluetooth. This plugin does a device discovery and then uses Bluez' obex client to transmit the file. When turning on apparmor on it, it first bails out with the messages below. However, once those are resolved, it'll probably want some more. I have attached the confined package to this bug so it can be easily tested. Please disregard the app in there completey and only evaluate the shareplugin in the package. After installing the click, open the gallery, share an image and select Bluetooth to start the process: [65927.602181] type=1107 audit(1460496066.496:2509): pid=891 uid=102 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name="org.bluez" pid=25873 label="ubtd.mzanetti_shareplugin_0.1" peer_pid=911 peer_label="unconfined" [65927.602199] exe="/usr/bin/dbus-daemon" sauid=102 hostname=? addr=? terminal=?' [65927.607588] type=1107 audit(1460496066.506:2510): pid=891 uid=102 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.bluez.Manager" member="DefaultAdapter" mask="send" name="org.bluez" pid=25873 label="ubtd.mzanetti_shareplugin_0.1" peer_pid=911 peer_label="unconfined" [65927.607606] exe="/usr/bin/dbus-daemon" sauid=102 hostname=? addr=? terminal=?' [65928.611714] type=1107 audit(1460496067.506:2511): pid=891 uid=102 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.bluez.Manager" member="DefaultAdapter" mask="send" name="org.bluez" pid=25873 label="ubtd.mzanetti_shareplugin_0.1" peer_pid=911 peer_label="unconfined" [65928.611733] exe="/usr/bin/dbus-daemon" sauid=102 hostname=? addr=? terminal=?' [65929.615630] type=1107 audit(1460496068.516:2512): pid=891 uid=102 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.bluez.Manager" member="DefaultAdapter" mask="send" name="org.bluez" pid=25873 label="ubtd.mzanetti_shareplugin_0.1" peer_pid=911 peer_label="unconfined" [65929.615649] exe="/usr/bin/dbus-daemon" sauid=102 hostname=? addr=? terminal=?' [65930.619178] type=1107 audit(1460496069.516:2513): pid=891 uid=102 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.bluez.Manager" member="DefaultAdapter" mask="send" name="org.bluez" pid=25873 label="ubtd.mzanetti_shareplugin_0.1" peer_pid=911 peer_label="unconfined" [65930.619197] exe="/usr/bin/dbus-daemon" sauid=102 hostname=? addr=? terminal=?' [65931.622804] type=1107 audit(1460496070.516:2514): pid=891 uid=102 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.bluez.Manager" member="DefaultAdapter" mask="send" name="org.bluez" pid=25873 label="ubtd.mzanetti_shareplugin_0.1" peer_pid=911 peer_label="unconfined" [65931.622822] exe="/usr/bin/dbus-daemon" sauid=102 hostname=? addr=? terminal=?' [65932.626550] type=1107 audit(1460496071.526:2515): pid=891 uid=102 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.bluez.Manager" member="DefaultAdapter" mask="send" name="org.bluez" pid=25873 label="ubtd.mzanetti_shareplugin_0.1" peer_pid=911 peer_label="unconfined" [65932.626569] exe="/usr/bin/dbus-daemon" sauid=102 hostname=? addr=? terminal=?' [65933.630102] type=1107 audit(1460496072.526:2516): pid=891 uid=102 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.bluez.Manager" member="DefaultAdapter" mask="send" name="org.bluez" pid=25873 label="ubtd.mzanetti_shareplugin_0.1" peer_pid=911 peer_label="unconfined" [65933.630121] exe="/usr/bin/dbus-daemon" sauid=102 hostname=? addr=? terminal=?' [65934.633739] type=1107 audit(1460496073.536:2517): pid=891 uid=102 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.bluez.Manager"
[Touch-packages] [Bug 1488170] Re: Bluetooth initiated after quitting airplane mode
Did something change with this? Because I can't reproduce this any more on my bq Aquaris E4.5 phone with OTA-11. With OTA-10.1 this happened every time. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1488170 Title: Bluetooth initiated after quitting airplane mode Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in urfkill package in Ubuntu: Confirmed Bug description: This happens despite bluetooth not being enabled when entering airplane mode. On Aquaris E5 OTA-5. Boot with bluetooth disabled Turn on flight mode turn off flight mode Bluetooth gets enabled See bug #1421249 for related symptoms To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1488170/+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 1588252] Re: [File Manager] Display issue: big white gap below header (portrait) & top gets cut off (landscape) after OTA-11
FYI, this bug was available in OTA-10 and OTA-10.1 too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1588252 Title: [File Manager] Display issue: big white gap below header (portrait) & top gets cut off (landscape) after OTA-11 Status in Canonical System Image: Confirmed Status in Ubuntu File Manager App: New Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: After the OTA-11 update, File Manager shows a big white space just below the header in portrait mode. https://launchpadlibrarian.net/262898404/screenshot20160602_150103754.png And also as Davide mentioned, top part goes off the display in landscape mode. https://launchpadlibrarian.net/262958275/screenshot20160602_184130460.png This only happens on E4.5 and E5, not on MX4 or M10 0.4.525 of file manager To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588252/+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 1546603] Re: Bluetooth mouse connects but doesn't work
I took a different approach to getting my mouse working: I installed blueman and used that to configure it. I guess it enables experimental features itself. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1546603 Title: Bluetooth mouse connects but doesn't work Status in bluez package in Ubuntu: Confirmed Bug description: I have a bluetooth mouse that I can get to connect via the gnome bluetooth settings panel, but even after it's connected it doesn't move the pointer or register any clicks. the following shows up in the journal : $ $ journalctl -b 0 |grep bluetooth Feb 17 07:18:22 spiny bluetoothd[1009]: Bluetooth daemon 5.36 Feb 17 07:18:22 spiny bluetoothd[1009]: Starting SDP server Feb 17 07:18:22 spiny bluetoothd[1009]: Bluetooth management interface 1.10 initialized Feb 17 07:18:22 spiny bluetoothd[1009]: Failed to obtain handles for "Service Changed" characteristic Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register service Feb 17 07:18:22 spiny bluetoothd[1009]: Error adding Link Loss service Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register service Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register service Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register service Feb 17 07:18:22 spiny bluetoothd[1009]: Current Time Service could not be registered Feb 17 07:18:22 spiny bluetoothd[1009]: gatt-time-server: Input/output error (5) Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register service Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register service Feb 17 07:18:22 spiny bluetoothd[1009]: Sap driver initialization failed. Feb 17 07:18:22 spiny bluetoothd[1009]: sap-server: Operation not permitted (1) Feb 17 07:18:22 spiny NetworkManager[1062]: Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so) Feb 17 07:18:24 spiny bluetoothd[1009]: Endpoint registered: sender=:1.42 path=/MediaEndpoint/A2DPSource Feb 17 07:18:24 spiny bluetoothd[1009]: Endpoint registered: sender=:1.42 path=/MediaEndpoint/A2DPSink Feb 17 07:18:42 spiny bluetoothd[1009]: Endpoint registered: sender=:1.71 path=/MediaEndpoint/A2DPSource Feb 17 07:18:42 spiny bluetoothd[1009]: Endpoint registered: sender=:1.71 path=/MediaEndpoint/A2DPSink Feb 17 07:18:42 spiny bluetoothd[1009]: RFCOMM server failed for Headset Voice gateway: rfcomm_bind: Address already in use (98) Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** (gnome-control-center.real:2717): WARNING **: Ignoring launcher gufw (missing desktop file) Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** (gnome-control-center.real:2717): WARNING **: Ignoring launcher landscape-client-settings (missing desktop file) Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** (gnome-control-center.real:2717): WARNING **: Ignoring launcher language-selector (missing desktop file) Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** (gnome-control-center.real:2717): WARNING **: Ignoring launcher ubuntuone-installer (missing desktop file) Feb 17 07:19:00 spiny gnome-bluetooth-panel.desktop[2717]: (gnome-control-center.real:2717): GLib-CRITICAL **: g_ascii_strdown: assertion 'str != NULL' failed Feb 17 07:19:01 spiny bluetoothd[1009]: No cache for F2:3F:5C:A1:F9:F7 Feb 17 07:19:06 spiny bluetoothd[1009]: Unable to register GATT service with handle 0x000c for device F2:3F:5C:A1:F9:F7 Feb 17 07:19:06 spiny bluetoothd[1009]: Unable to register GATT service with handle 0x001b for device F2:3F:5C:A1:F9:F7 Feb 17 07:19:06 spiny bluetoothd[1009]: Unable to register GATT service with handle 0x003f for device F2:3F:5C:A1:F9:F7 Feb 17 07:19:06 spiny bluetoothd[1009]: Report Map read failed: Attribute requires authentication before read/write Feb 17 07:19:06 spiny bluetoothd[1009]: Protocol Mode characteristic read failed: Attribute requires authentication before read/write Feb 17 07:19:06 spiny bluetoothd[1009]: HID Information read failed: Attribute requires authentication before read/write Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor failed: Attribute requires authentication before read/write Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor failed: Attribute requires authentication before read/write Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor failed: Attribute requires authentication before read/write Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor failed: Attribute requires authentication before read/write Feb 17 07:19:08 spiny gnome-bluetooth-panel.desktop[2717]: (gnome-control-center.real:2717): GLib-CRI
[Touch-packages] [Bug 1607713] Re: 'The website says "%2"' sentence's missing from translations
** Changed in: canonical-devices-system-image
Status: New => Confirmed
--
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/1607713
Title:
'The website says "%2"' sentence's missing from translations
Status in Canonical System Image:
Confirmed
Status in webbrowser-app package in Ubuntu:
Confirmed
Bug description:
Website authentication's second sentence is missing from translations:
In the code:
text: request ? i18n.tr('The website at %1 requires authentication. The
website says "%2"').arg(request.host).arg(request.realm) : ""
On Launchpad:
The website %1 requires authentication.
So the 'The website says "%2"' part is missing.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607713/+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 1421923] Re: No notifications for new mails
Hi! Any progress with this? It was reported more than a year. :( -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1421923 Title: No notifications for new mails Status in Online Accounts: Account plugins: New Status in Canonical System Image: In Progress Status in Dekko: In Progress Status in account-plugins package in Ubuntu: In Progress Status in account-polld package in Ubuntu: In Progress Bug description: Hi! In the BQ E4.5 Ubuntu Edition, I'm not getting notificactions for new mails. Testing (by example) 1. Kill Dekko. 2. Send you an email. 3. Open Dekko. 4. Change quickly to another app before Dekko starts. 5. Bug: No notification 6. Go to Dekko: You'll see your new mail. FYI as improvement, for me, in Dekko is not clear if Dekko checks the mail after X minutes or is a push notification. Thanks in advance! To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1421923/+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 1477855] Re: Add alternative shutter methods
This would be a really useful feature. :) ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1477855 Title: Add alternative shutter methods Status in camera-app: Confirmed Status in Canonical System Image: Confirmed Status in camera-app package in Ubuntu: Confirmed Bug description: Feature request: Problem: On a large phone like the MX4 it is very difficult to use the camera app with one hand because when you first set the focus point, then it is usually impossible to reach the shutter icon without moving the phone. Possible solutions: - When setting the focus point, directly take an image when it is focused. This could be an option or gesture based (e.g. double tap on screen). - use one of the hardware buttons as shutter button. E.g. volume control. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1477855/+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 1373463] Re: [indicators] Impossible to disable cellular data from indicator
First, thanks four your work, it will be very useful for a lot of us :) I tried it on a Nexus 4 (rc-proposed, latest image). I've found some issues: At the first run the toogle was disabled (can't turn it on/off) on the indicator, I needed to enable in System Settings first, then it worked as expected on the indicator too. Then I rebooted my phone, and the toggle worked well, then I turned it off, after that, both toggles were disabled (on the Indicator and in the System Settings too). So sometimes the toggle be disabled. I can provide logs, just tell me which one needed. Thanks. :) -- 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/1373463 Title: [indicators] Impossible to disable cellular data from indicator Status in Canonical System Image: In Progress Status in Ubuntu UX: Triaged Status in indicator-network package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: In Progress Bug description: I was wondering : Why it isn't possible to disable data from the network indicator ? Probably with a switch button that offer the choice between no data or data activated (with the last data activated state (2g only or 2G,3G,4G). Why this ? Because it's the first setting to change to save battery, and probably one of the most used (I asked around me, everyone agreed they would prefer that over Wi-Fi if only one was possible). I think it's stupid to go to the settings app for the most common action (and very frustrating). Of course, this also apply for the battery setting page (that already contain Wi-Fi, GPS, Bluetooth and brightness settings). I asked that on the phone ML, I've been invited to file a wishlist bug there to "help" designers with next iteration of network indicator. So here it is ! [1] : mailing list discussion with already some support to this idea : https://lists.launchpad.net/ubuntu-phone/msg09910.html To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1373463/+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 1373463] Re: [indicators] Impossible to disable cellular data from indicator
Thanks for the fast reply, Antti :) Here are the files: config.inis: http://paste.ubuntu.com/17608571/ I changed my sim ID to xxx, but it's the same everywhere. modems: http://paste.ubuntu.com/17608759/ I changed my sim ID in one file (before). The other two files (after reboot, and after disable) look really weird. These are a python files instead of the command output. Maybe a bug in the code? And it doesn't run, just echo the file's content? Maybe this is the reason of the disabled toggles. I checked it three times, and it looks the same everytime. -- 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/1373463 Title: [indicators] Impossible to disable cellular data from indicator Status in Canonical System Image: In Progress Status in Ubuntu UX: Triaged Status in indicator-network package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: In Progress Bug description: I was wondering : Why it isn't possible to disable data from the network indicator ? Probably with a switch button that offer the choice between no data or data activated (with the last data activated state (2g only or 2G,3G,4G). Why this ? Because it's the first setting to change to save battery, and probably one of the most used (I asked around me, everyone agreed they would prefer that over Wi-Fi if only one was possible). I think it's stupid to go to the settings app for the most common action (and very frustrating). Of course, this also apply for the battery setting page (that already contain Wi-Fi, GPS, Bluetooth and brightness settings). I asked that on the phone ML, I've been invited to file a wishlist bug there to "help" designers with next iteration of network indicator. So here it is ! [1] : mailing list discussion with already some support to this idea : https://lists.launchpad.net/ubuntu-phone/msg09910.html To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1373463/+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 1373463] Re: [indicators] Impossible to disable cellular data from indicator
Thanks, let me know when I can test it :) -- 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/1373463 Title: [indicators] Impossible to disable cellular data from indicator Status in Canonical System Image: In Progress Status in Ubuntu UX: Triaged Status in indicator-network package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: In Progress Bug description: I was wondering : Why it isn't possible to disable data from the network indicator ? Probably with a switch button that offer the choice between no data or data activated (with the last data activated state (2g only or 2G,3G,4G). Why this ? Because it's the first setting to change to save battery, and probably one of the most used (I asked around me, everyone agreed they would prefer that over Wi-Fi if only one was possible). I think it's stupid to go to the settings app for the most common action (and very frustrating). Of course, this also apply for the battery setting page (that already contain Wi-Fi, GPS, Bluetooth and brightness settings). I asked that on the phone ML, I've been invited to file a wishlist bug there to "help" designers with next iteration of network indicator. So here it is ! [1] : mailing list discussion with already some support to this idea : https://lists.launchpad.net/ubuntu-phone/msg09910.html To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1373463/+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 1373463] Re: [indicators] Impossible to disable cellular data from indicator
Thanks Antti, it's working well now. :) -- 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/1373463 Title: [indicators] Impossible to disable cellular data from indicator Status in Canonical System Image: In Progress Status in Ubuntu UX: Triaged Status in indicator-network package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: In Progress Bug description: I was wondering : Why it isn't possible to disable data from the network indicator ? Probably with a switch button that offer the choice between no data or data activated (with the last data activated state (2g only or 2G,3G,4G). Why this ? Because it's the first setting to change to save battery, and probably one of the most used (I asked around me, everyone agreed they would prefer that over Wi-Fi if only one was possible). I think it's stupid to go to the settings app for the most common action (and very frustrating). Of course, this also apply for the battery setting page (that already contain Wi-Fi, GPS, Bluetooth and brightness settings). I asked that on the phone ML, I've been invited to file a wishlist bug there to "help" designers with next iteration of network indicator. So here it is ! [1] : mailing list discussion with already some support to this idea : https://lists.launchpad.net/ubuntu-phone/msg09910.html To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1373463/+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 1540850] [NEW] The "Scopes" label should be translatable on the App Scope's loading page
Public bug reported: The "Scopes" label should be translatable on the App Scope's loading page. See attached screenshot. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "screenshot20160129_160257946.png" https://bugs.launchpad.net/bugs/1540850/+attachment/4562034/+files/screenshot20160129_160257946.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1540850 Title: The "Scopes" label should be translatable on the App Scope's loading page Status in unity8 package in Ubuntu: New Bug description: The "Scopes" label should be translatable on the App Scope's loading page. See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1540850/+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 1500039] Re: Ubuntu Phone is not getting a mobile network cell triangulation position
Any update on this? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1500039 Title: Ubuntu Phone is not getting a mobile network cell triangulation position Status in Canonical System Image: Confirmed Status in location-service package in Ubuntu: Confirmed Bug description: Hi! I think that the mobile network cell triangulation position is not working in Ubuntu Phone OS. The position should be really fast (~1 - 5") and I'm thinking that Ubuntu Phone is waiting for a real GPS position every time. A good test could be this: - Go to a room, way out of a sky to avoid a real GPS signal. - Set WiFi service OFF. - Set GPS service ON. - Set data connection ON. - Go to this website via webbrowser-app: http://leafletjs.com/examples/mobile-example.html The website will ask you to allow access to the current location. - Make sure to not have a GPS position cached. In a PC or *any* Android you'll see your position immediately. Bug: In Ubuntu Phone an error will appears. This error is because the geoposition (https://developer.mozilla.org/en-US/docs/Web/API/Geolocation/Using_geolocation) is not working with the cell triangulation network data. You can try a lot of apps like Google Maps, OSMTouch, HERE map, uNAV... and a fast position from data connection is not happening, unless you be with a WIFI connection. If you try Google Maps in Android, the position will be really fast just with data connection. Thanks in advance! To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1500039/+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 1436912] Re: Unlocalized notification option ("Message")
Please fix this bug. This is about one year old.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-settings-components
in Ubuntu.
https://bugs.launchpad.net/bugs/1436912
Title:
Unlocalized notification option ("Message")
Status in Canonical System Image:
In Progress
Status in ubuntu-settings-components package in Ubuntu:
Fix Released
Bug description:
Test case.
- Switch the device to Spanish.
- From another device, make a phone call, don't accept it.
- Open message indicator.
Expected result.
- Notification options are localized.
Actual result.
- "Message" is not localized.
"Call back" is localized, but "Message" is not. Actually, I don't find
"Message" in telephone-service source code, but "Send".
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1436912/+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 1436912] Re: Unlocalized notification option ("Message")
Is it already in the rc-proposed channel? If yes I will try it later
today.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-settings-components
in Ubuntu.
https://bugs.launchpad.net/bugs/1436912
Title:
Unlocalized notification option ("Message")
Status in Canonical System Image:
Fix Committed
Status in ubuntu-settings-components package in Ubuntu:
Fix Released
Bug description:
Test case.
- Switch the device to Spanish.
- From another device, make a phone call, don't accept it.
- Open message indicator.
Expected result.
- Notification options are localized.
Actual result.
- "Message" is not localized.
"Call back" is localized, but "Message" is not. Actually, I don't find
"Message" in telephone-service source code, but "Send".
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1436912/+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 1566341] Re: ``Tomorrow'' appears untranslated
I think it is not just the indicator-datetime, maybe it is the UUITK? See my attached screenshots. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1566341 Title: ``Tomorrow'' appears untranslated Status in indicator-datetime package in Ubuntu: Confirmed Bug description: Reported in the ubuntu-phone mailing list's ``Landing team 31.03.16'' thread: Richard Somlói: > "Tomorrow" should be "Holnap" in Hungarian, and it worked well with the previous images. Could somebody confirm it with another language? sil2100: > I just checked the indicator-datetime language pack and see Tomorrow as translated in all possible places there, so at least it's not a problem with the langpack itself. I would recommend filling in a bug against indicator-datetime so that the developers can take a look what's wrong. > But there is certainly something wrong since I get the same issue with the Polish locale. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1566341/+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 1566341] Re: ``Tomorrow'' appears untranslated
** Attachment added: "screenshot20160409_115719600.png" https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1566341/+attachment/4630049/+files/screenshot20160409_115719600.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1566341 Title: ``Tomorrow'' appears untranslated Status in indicator-datetime package in Ubuntu: Confirmed Bug description: Reported in the ubuntu-phone mailing list's ``Landing team 31.03.16'' thread: Richard Somlói: > "Tomorrow" should be "Holnap" in Hungarian, and it worked well with the previous images. Could somebody confirm it with another language? sil2100: > I just checked the indicator-datetime language pack and see Tomorrow as translated in all possible places there, so at least it's not a problem with the langpack itself. I would recommend filling in a bug against indicator-datetime so that the developers can take a look what's wrong. > But there is certainly something wrong since I get the same issue with the Polish locale. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1566341/+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 1566341] Re: ``Tomorrow'' appears untranslated
** Attachment added: "screenshot20160409_115151981.png" https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1566341/+attachment/4630048/+files/screenshot20160409_115151981.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1566341 Title: ``Tomorrow'' appears untranslated Status in indicator-datetime package in Ubuntu: Confirmed Bug description: Reported in the ubuntu-phone mailing list's ``Landing team 31.03.16'' thread: Richard Somlói: > "Tomorrow" should be "Holnap" in Hungarian, and it worked well with the previous images. Could somebody confirm it with another language? sil2100: > I just checked the indicator-datetime language pack and see Tomorrow as translated in all possible places there, so at least it's not a problem with the langpack itself. I would recommend filling in a bug against indicator-datetime so that the developers can take a look what's wrong. > But there is certainly something wrong since I get the same issue with the Polish locale. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1566341/+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 1468020] Re: Two GPS compatible apps conflict and loose GPS
I've just tested it and it works well for me. Tested with Here and uNav. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1468020 Title: Two GPS compatible apps conflict and loose GPS Status in Canonical System Image: Incomplete Status in location-service package in Ubuntu: Incomplete Bug description: Meizu MX4 with Ubuntu 15.04 r2 1. run OSMscout (for example) 2. drive/cycle a distance to confirm that GPS tracking is working fine 3. run the camera app (for example) 4. take a few photos (they'll be tagged with GPS info) 5. switch to OSMscout 6. drive/cycle and OSM will now not update from GPS Haven't tested this with other apps as yet, but it seems that one app will take control of the GPS and not hand it back. (For want of a better explanation.) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1468020/+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 1519235] Re: Nexus 4 - HDMI-Slimport adapter can't charge the phone and display the screen at the same time.
I bought a new replacement adapter and it works well. So something is wrong with the previous one. Sorry for the false alarm. :) ** Changed in: mir (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1519235 Title: Nexus 4 - HDMI-Slimport adapter can't charge the phone and display the screen at the same time. Status in mir package in Ubuntu: Invalid Bug description: I have a Nexus4 device and I bought a MyDP HDMI-SlimPort adapter, which is compatible with N4. But I can't charge my phone and display the screen on the external display at the same time. If I connect the charger the screen switches back to the device, If I disconnect the charger, the screen switches to the external display. It works well with Android. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1519235/+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 1313004] Re: IPv6 static routes without gateway fail to be set
This is fixed in 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/1313004 Title: IPv6 static routes without gateway fail to be set Status in network-manager package in Ubuntu: New Bug description: When using network-manager, and specifying the IPv6 routes, I am able to enter and save IPv6 Settings static routes with no gateway or metric. Upon hitting "save", the dialog closes apparently successfully but this entry appears in the syslog (actual address defaced): Apr 25 19:28:26 zanfur-fb NetworkManager[7181]: keyfile: ipv6.route2: route defa:cede:face:defa::/64 gateway 0 metric 0 Apr 25 19:28:26 zanfur-fb NetworkManager[7181]: build_ip6_address_or_route: ignoring invalid IPv6 gateway '0' Additionally, upon opening the connection again through the same dialog, the routes are empty. Checking the connection file in /etc/NetworkManager/system-connections, the routes are unlisted. When editing the connection file directly, upon saving I see a similar syslog entry, even when I put '::' in for the gateway. When I leave it as a zero-width string, the message says '' instead of '0' but is otherwise the same. When attempting to connect, the connection completes just fine but the route is of course ignored. EXPECTED BEHAVIOR: Able to save ipv6 routes with no gateway, and have them established upon connection (e.g. for VPN connections, where there is typically no gateway other than the VPN endpont itself). ACTUAL BEHAVIOR: IPv6 routes without a gateway are silently dropped from the config. SYSTEM: Ubuntu trusty tahr 14.04, network-manager 0.9.8.8-0ubuntu7, network- manager-openconnect-gnome 0.9.8.0-1ubuntu2, kernel "3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux". Running on a Lenovo T440s, though that doesn't much matter here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1313004/+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 1351299] Re: [Location Indicator Menu] GPS switch should be turned off when "Location detection" is off
Hi! Any progress with this issue? I really don't like the new behaviour of the Location Indicator. Now if I want to navigate with my phone, I need to enable Location Detection on the indicator, then go to the System Settings app -> Battery -> and enable the GPS. This is not the best solution. I don't want the GPS enabled all the time, so now I need to open the System Settings every time to enable/disable it, and the app starts really slow... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1351299 Title: [Location Indicator Menu] GPS switch should be turned off when "Location detection" is off Status in Canonical System Image: In Progress Status in Ubuntu UX: Fix Committed Status in indicator-location package in Ubuntu: Fix Committed Status in location-service package in Ubuntu: Incomplete Status in trust-store package in Ubuntu: Incomplete Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: After a conversation with tvoss, I understand that if I turn the "Location detection" switch off, effectively GPS will be turned off too. However, the two switches are independent: I can switch "Location detection" off and the "GPS" switch will stay on. This might be confusing for users: I'd expect both switches to go off when turning "Location detection" off. -- UX Comment -- Location section in the Indicators spec has been updated with latest visuals and desired behaviour. On tap of 'Location settings...', users can choose to use 'GPS only' (without using Here services) in the relevant System settings screen. https://docs.google.com/document/edit?hgd=1&id=1810KDpFl2Mxsn1z3wehPU9pkbS6R6o-j1-pmYpkYb7A#heading=h.jh8j7gb6bo0s To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1351299/+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
