[Touch-packages] [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full
Happy to discuss and help...in the support forums. This CLOSED bug report is not the appropriate location to help people troubleshoot. -- 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/1357093 Title: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full Status in unattended-upgrades package in Ubuntu: Fix Released Bug description: Currently if one chooses to use LVM or encrypted install, a /boot partition is created of 236Mb Once kernel updates start being released this partition soon fills until people are left unable to upgrade. While you and I might know that we need to watch partition space, many of the people we have installing think that a windows disk is a disk and not a partition, education is probably the key - but in the meantime support venues keep needing to deal with the fact the partition is too small and/or old kernels are not purged as new ones install. For workaround and sytem repair, see https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093/+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 1211110] Re: network manager openvpn dns push data not updating system DNS addresses
On 16.10 - Confirmed that after reboot, my VPN-pushed DNS comes back, on second connection it is missing. I've logged a fresh Bug #1644098 pertaining ONLY to this issue. (Please don't pollute it with "DNS doesn't work at all" comments!) -- 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/120 Title: network manager openvpn dns push data not updating system DNS addresses Status in network-manager package in Ubuntu: Incomplete Status in openvpn package in Ubuntu: Incomplete Bug description: [Triage Notes] This bug can no longer make progress. Please see comment 50 for details and further instructions. [Original Description] When IPv4 Method is set to Automatic VPN, DNS address recieved from OpenVPN server do not update resolv.conf. This can be achieved when using a standard openvpn config file by adding the lines: script-security 2 up /etc/openvpn/update-resolv-conf down /etc/openvpn/update-resolv-conf In Network-manager there seems to be no option to run connection specific scripts and the DNS data from the server is ignored. Ubuntu 13.04 Network-manager 0.9.8.0-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+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 1604617] Re: dhclient does not send fqdn.fqdn for DHCPv6
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: isc-dhcp (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1604617 Title: dhclient does not send fqdn.fqdn for DHCPv6 Status in isc-dhcp package in Ubuntu: Confirmed Bug description: ISC DHCP's dynamic DNS updates rely on the fqdn.fqdn option being sent in order to work for DHCPv6. This used to be done in Ubuntu, as shown in bugs #991360 and #108862, and all my Windows hosts send it. However this was removed in Ubuntu due to a regression in IPv4 functionality. As IPv6 is more widely deployed these days, this regression in IPv6 should be fixed. This bug is current as of Ubuntu 16.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1604617/+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 1644098] [NEW] Network Manager + OpenVPN does not respond to DNS server change on second connection attempt
Public bug reported: Scenario: Discovered on Kubuntu 16.10, upgraded from a fresh install of 16.04. While I only have the one computer to test with, the 16.10 is definitely relevant (I did not have this problem on 16.04) but I can't tell if the upgrade is part of it, (the upgrade may or may not be relevant). Have "full time" wired or wireless connection (does not matter which used) Part time OpenVPN connection set up via NetworkManager. Steps to reproduce 1. Fresh boot 2. ping a device on the VPN network (eg amachine.remotelan ) Result: "ping: amachine.remotelan: Name or service not known" 3. Connect to the VPN service via Network Manager. 4. ping amachine.remotelan - result: PING amachine.remotelan (192.168.68.44) 56(84) bytes of data. 64 bytes from amachine.remotelan (192.168.68.44): icmp_seq=1 ttl=127 time=7.75 ms 5. Disconnect from the VPN service again. ping result again "ping: amachine.remotelan: Name or service not known" 6. Reconnect to the VPN again, and ping again Observed: "ping: amachine.remotelan: Name or service not known" However "ping 192.168.68.44" responds successfully as expected Expected: PING ... 192.168 64 bytes from .. etc to the ping by name --- Further info I'm going to add in a subsequent comment. (just annotating syslog right now!) ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: network-manager openvpn -- 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/1644098 Title: Network Manager + OpenVPN does not respond to DNS server change on second connection attempt Status in network-manager package in Ubuntu: New Bug description: Scenario: Discovered on Kubuntu 16.10, upgraded from a fresh install of 16.04. While I only have the one computer to test with, the 16.10 is definitely relevant (I did not have this problem on 16.04) but I can't tell if the upgrade is part of it, (the upgrade may or may not be relevant). Have "full time" wired or wireless connection (does not matter which used) Part time OpenVPN connection set up via NetworkManager. Steps to reproduce 1. Fresh boot 2. ping a device on the VPN network (eg amachine.remotelan ) Result: "ping: amachine.remotelan: Name or service not known" 3. Connect to the VPN service via Network Manager. 4. ping amachine.remotelan - result: PING amachine.remotelan (192.168.68.44) 56(84) bytes of data. 64 bytes from amachine.remotelan (192.168.68.44): icmp_seq=1 ttl=127 time=7.75 ms 5. Disconnect from the VPN service again. ping result again "ping: amachine.remotelan: Name or service not known" 6. Reconnect to the VPN again, and ping again Observed: "ping: amachine.remotelan: Name or service not known" However "ping 192.168.68.44" responds successfully as expected Expected: PING ... 192.168 64 bytes from .. etc to the ping by name --- Further info I'm going to add in a subsequent comment. (just annotating syslog right now!) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1644098/+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 427775] Re: ntpdate.dhcp always ignored
Hey movement on Debian, thanks Kurt. Opening that up for the next development release merge we do. ** Changed in: ntp (Ubuntu) Status: Won't Fix => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/427775 Title: ntpdate.dhcp always ignored Status in ntp package in Ubuntu: Triaged Status in ntp source package in Trusty: Won't Fix Status in ntp package in Debian: Fix Released Bug description: Ubuntu 9.04, affects the ntpdate binary package Problem: Using dhcp a file ntpdate.dhcp is created but never used. By default NTPDATE_USE_NTP_CONF in /etc/default/ntpdate is set to "yes". This has the following consequences: /usr/sbin/ntpdate-debian parses /etc/default/ntpdate and checks for /etc/ntp.conf.dhcp /etc/ntp.conf /etc/openntpd/ntpd.conf if NTPDATE_USE_NTP_CONF is set to yes. By default ntpd is not installed therefore there is no /etc/ntp.conf.dhcp /etc/ntp.conf or /etc/openntpd/ntpd.conf. ntpdate-debian then defaults to the NTPSERVERS set in /etc/default/ntpdate, namely "ntp.ubuntu.com". Only if NTPDATE_USE_NTP_CONF is set to "no" there will be a check for /etc/default/ntpdate.dhcp and consequently the server supplied by dhcp be used. I propose to set NTPDATE_USE_NTP_CONF to "no" by default. If ntpd is installed, this will override the use of ntpdate and /etc/ntpd.conf.dhcp and /etc/default/ntpdate.dhcp will both be created by DHCP anyway, therefore both packages will use the DHCP supplied servers in any case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/427775/+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 1643870] Re: Pulseaudio fails to detect card after recent update
Also fixed on the Dell laptop. Seems to be a problem with the `squeezelite` package. See https://bugs.launchpad.net/bugs/1636253 I think this specific bug can be closed, my initial problem is resolved. -- 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/1643870 Title: Pulseaudio fails to detect card after recent update Status in pulseaudio package in Ubuntu: Invalid Bug description: For months, audio has been working fine on this Dell XPS13 laptop. It is a fresh install of 16.04, from around the time it was released. There were some pulseaudio updates installed on my machine today (see the attached apt term.log output). Since then, audio output has been unreliable. I've discussed this a small amount on AskUbuntu http://askubuntu.com/a/852277/237387 I found that running this command to reinstall the updated packages would sometimes bring back audio output - sometimes for a while, but sometimes only for a few seconds after a reboot. sudo apt install --reinstall pulseaudio pulseaudio-utils pulseaudio-module-bluetooth pulseaudio-module-x11 libpulse-mainloop- glib0 libpulse0 libpulsedsp I can see Launchpad has several almost identical sounding bugs, from many years ago. #461258, #926840, #926840, #995961, #1132982. None of those were ever resolved. I hope this does not end the same way. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Tue Nov 22 23:13:26 2016 InstallationDate: Installed on 2016-05-17 (189 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [Dell System XPS L322X, Realtek ALC3260, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0WW7PG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0WW7PG:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1643870/+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 1643870] Re: Pulseaudio fails to detect card after recent update
Found to be related to https://bugs.launchpad.net/bugs/1636253 ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Invalid -- 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/1643870 Title: Pulseaudio fails to detect card after recent update Status in pulseaudio package in Ubuntu: Invalid Bug description: For months, audio has been working fine on this Dell XPS13 laptop. It is a fresh install of 16.04, from around the time it was released. There were some pulseaudio updates installed on my machine today (see the attached apt term.log output). Since then, audio output has been unreliable. I've discussed this a small amount on AskUbuntu http://askubuntu.com/a/852277/237387 I found that running this command to reinstall the updated packages would sometimes bring back audio output - sometimes for a while, but sometimes only for a few seconds after a reboot. sudo apt install --reinstall pulseaudio pulseaudio-utils pulseaudio-module-bluetooth pulseaudio-module-x11 libpulse-mainloop- glib0 libpulse0 libpulsedsp I can see Launchpad has several almost identical sounding bugs, from many years ago. #461258, #926840, #926840, #995961, #1132982. None of those were ever resolved. I hope this does not end the same way. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Tue Nov 22 23:13:26 2016 InstallationDate: Installed on 2016-05-17 (189 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [Dell System XPS L322X, Realtek ALC3260, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0WW7PG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0WW7PG:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1643870/+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 1644098] Re: Network Manager + OpenVPN does not respond to DNS server change on second connection attempt
/etc/NetworkManager/NetworkManager.conf contains: [main] plugins=ifupdown,keyfile,ofono dns=dnsmasq [ifupdown] managed=false (There are various posts floating around to the effect that 'dns=dnsmasq' should be commented out. However this is how the Ubuntu install set it so assuming that either it is critical to correct operation or it is part of the cause). -- 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/1644098 Title: Network Manager + OpenVPN does not respond to DNS server change on second connection attempt Status in network-manager package in Ubuntu: New Bug description: Scenario: Discovered on Kubuntu 16.10, upgraded from a fresh install of 16.04. While I only have the one computer to test with, the 16.10 is definitely relevant (I did not have this problem on 16.04) but I can't tell if the upgrade is part of it, (the upgrade may or may not be relevant). Have "full time" wired or wireless connection (does not matter which used) Part time OpenVPN connection set up via NetworkManager. Steps to reproduce 1. Fresh boot 2. ping a device on the VPN network (eg amachine.remotelan ) Result: "ping: amachine.remotelan: Name or service not known" 3. Connect to the VPN service via Network Manager. 4. ping amachine.remotelan - result: PING amachine.remotelan (192.168.68.44) 56(84) bytes of data. 64 bytes from amachine.remotelan (192.168.68.44): icmp_seq=1 ttl=127 time=7.75 ms 5. Disconnect from the VPN service again. ping result again "ping: amachine.remotelan: Name or service not known" 6. Reconnect to the VPN again, and ping again Observed: "ping: amachine.remotelan: Name or service not known" However "ping 192.168.68.44" responds successfully as expected Expected: PING ... 192.168 64 bytes from .. etc to the ping by name --- Further info I'm going to add in a subsequent comment. (just annotating syslog right now!) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1644098/+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 1643997] Re: nvidia driver causes blank screen
** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-367 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1643997 Title: nvidia driver causes blank screen Status in nvidia-graphics-drivers-367 package in Ubuntu: New Bug description: I just installed ubuntu 16.04.1 64 bit (complete vanilla) 1. apt-get upgrade 2. apt-get dist-upgrade 3. install nvidia proprietary driver from "System settings -> Software & updates -> Additional Drivers" (current driver is 367.57- marked "proprietary, tested"). 4. reboot 5. blank screen as described above. I've modified grub with "nomodeset" - did not work. Removed "quiet, splash" - did not work add "set gfxpayload=text" - got some output to the screen, but not can't tell what it does and I have no idea where the data is stored - and then blank screen. disabled vesa frame buffer (vesafb.nonsense=1) - did not work My graphic HW: GTX 960 For now, I purged nvidia driver and the system is running well. I am sure the card is working properly because up until 3 days ago it had ubuntu 14.04 installed on it with nvidia driver active. Then there was an update which caused the same blank screen on 14.04. I decided to install 16.04 fresh (over the 14.04). I hoped the blank screen issue will disappear with 16.04, but it turns out it doesn't. If you need me to run some tests, I'll be more then happy to do so. I installed openssh-server on my machine, so I think I might be able to ssh into it from another machine while its in blank screen (did not test this). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 22 21:51:15 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-47-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2016-11-22 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 04/25/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1302 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7H55-M 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.:bvr1302:bd04/25/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7H55-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 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.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Nov 22 21:30:50 2016 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.2 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1643997/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1642386] Re: At least one invalid signature was encountered.
>You can fix your permissions on your trusted.gpg and trusted.gpg.d files in /etc/apt, so that the files are world-readable (chmod ugo+r /etc/apt/trusted.gpg /etc/apt/trusted.gpg.d -R) [or give access to root and _apt via acls]. That has been successful for me. -- 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/1642386 Title: At least one invalid signature was encountered. Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Triaged Bug description: Hello, a recent apt update appears to have broken apt entirely. A coworker reported seeing troubles: http://paste.ubuntu.com/23487135/ To test, I upgraded my laptop then immediately re-ran apt-get update && apt-get -u dist-upgrade: sarnold@hunt:~/Downloads$ sudo apt-get update && sudo apt-get -u dist-upgrade Hit:1 http://mirrors.kernel.org/ubuntu xenial InRelease Hit:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease Hit:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease Ign:4 http://mirrors.kernel.org/ubuntu precise InRelease Get:5 http://mirrors.kernel.org/ubuntu precise-updates InRelease [55.7 kB] Get:6 http://mirrors.kernel.org/ubuntu precise-security InRelease [55.7 kB] Get:7 http://mirrors.kernel.org/ubuntu precise-proposed InRelease [55.7 kB] Ign:8 http://mirrors.kernel.org/ubuntu trusty InRelease Get:9 http://mirrors.kernel.org/ubuntu trusty-updates InRelease [65.9 kB] Hit:10 http://mirrors.kernel.org/ubuntu trusty-security InRelease Get:11 http://mirrors.kernel.org/ubuntu trusty-proposed InRelease [65.9 kB] Get:12 http://mirrors.kernel.org/ubuntu xenial-proposed InRelease [247 kB] Err:1 http://mirrors.kernel.org/ubuntu xenial InRelease At least one invalid signature was encountered. Hit:13 http://security.debian.org jessie/updates InRelease Err:2 http://mirrors.kernel.org/ubuntu xenial-updates InRelease At least one invalid signature was encountered. Get:14 http://mirrors.kernel.org/ubuntu yakkety InRelease [247 kB] Err:3 http://mirrors.kernel.org/ubuntu xenial-security InRelease At least one invalid signature was encountered. Hit:15 http://mirrors.kernel.org/ubuntu yakkety-updates InRelease Get:16 http://mirrors.kernel.org/ubuntu yakkety-security InRelease [93.3 kB] Hit:17 http://security.debian.org wheezy/updates InRelease Get:18 http://mirrors.kernel.org/ubuntu yakkety-proposed InRelease [95.7 kB] Hit:19 http://mirrors.kernel.org/ubuntu zesty InRelease Hit:20 http://mirrors.kernel.org/ubuntu zesty-updates InRelease Hit:21 http://mirrors.kernel.org/ubuntu zesty-security InRelease Err:5 http://mirrors.kernel.org/ubuntu precise-updates InRelease At least one invalid signature was encountered. Hit:22 http://mirrors.kernel.org/ubuntu zesty-proposed InRelease Hit:23 http://mirrors.kernel.org/ubuntu precise Release Hit:24 http://mirrors.kernel.org/ubuntu trusty Release Ign:25 http://archive.canonical.com/ubuntu precise InRelease Hit:26 http://security.ubuntu.com/ubuntu xenial-security InRelease Hit:27 http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu vivid InRelease Hit:28 http://ftp.debian.org/debian unstable InRelease Err:6 http://mirrors.kernel.org/ubuntu precise-security InRelease At least one invalid signature was encountered. Err:7 http://mirrors.kernel.org/ubuntu
[Touch-packages] [Bug 1644007] Re: Intel HD Graphics 5500 Drivers Cap Resolution at 1366x768 and don't support video out for external displays
Please update the bug description to clarify if the machine with the faulty HDMI port is the one with a capped resolution. I experienced a similar issue recently. In my case it was a poor connection on the HDMI plug limiting the available resolutions. The fix for me was to plug in a fresh HDMI cable that cleaned out the socket and then gave a better connection. Full resolution returned after that. ** Changed in: xorg (Ubuntu) Status: New => Incomplete ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1644007 Title: Intel HD Graphics 5500 Drivers Cap Resolution at 1366x768 and don't support video out for external displays Status in xorg-server package in Ubuntu: Incomplete Bug description: Dell latitude e7450, Ubuntu 14.04 LTS. Swapped disk from latitude e7450 with faulty HDMI port as a quick fix while it gets repaired/replaced under warranty. "Pleasantly" surprised to find the screen resolution capped abysmally low and neither video out port working. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-101.148-generic 3.13.11-ckt39 Uname: Linux 3.13.0-101-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Tue Nov 22 15:34:21 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: vboxhost, 5.0.28, 3.13.0-101-generic, x86_64: installed vboxhost, 5.0.28, 3.13.0-91-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:062e] InstallationDate: Installed on 2015-05-01 (571 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Latitude E7450 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-101-generic root=UUID=97bccafc-0510-496c-99b5-0e03b4d0399b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/12/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 06HN6G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd01/12/2016:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn06HN6G:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7450 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Nov 22 15:09:58 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5264 vendor CMN xserver.version: 2:1.15.1-0ubuntu2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1644007/+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 1644023] Re: package libprocps4:amd64 2:3.3.10-4ubuntu2.2 failed to install/upgrade: package libprocps4:amd64 is already installed and configured
*** This bug is a duplicate of bug 1635280 *** https://bugs.launchpad.net/bugs/1635280 ** This bug has been marked a duplicate of bug 1635280 [ BUG 541595 IS BACK ] package is already installed and configured -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1644023 Title: package libprocps4:amd64 2:3.3.10-4ubuntu2.2 failed to install/upgrade: package libprocps4:amd64 is already installed and configured Status in procps package in Ubuntu: New Bug description: Automatic ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libprocps4:amd64 2:3.3.10-4ubuntu2.2 ProcVersionSignature: Ubuntu 4.4.0-47.68-lowlatency 4.4.24 Uname: Linux 4.4.0-47-lowlatency x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 Date: Tue Nov 22 13:11:21 2016 DuplicateSignature: package:libprocps4:amd64:2:3.3.10-4ubuntu2.2 Processing triggers for mime-support (3.59ubuntu1) ... dpkg: error processing package xserver-common (--configure): package xserver-common is already installed and configured ErrorMessage: package libprocps4:amd64 is already installed and configured InstallationDate: Installed on 2016-10-23 (29 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: procps Title: package libprocps4:amd64 2:3.3.10-4ubuntu2.2 failed to install/upgrade: package libprocps4:amd64 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1644023/+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 1644098] Re: Network Manager + OpenVPN does not respond to DNS server change on second connection attempt
Finally see Bug #120 particularly the later (November 2016) comments -- 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/1644098 Title: Network Manager + OpenVPN does not respond to DNS server change on second connection attempt Status in network-manager package in Ubuntu: New Bug description: Scenario: Discovered on Kubuntu 16.10, upgraded from a fresh install of 16.04. While I only have the one computer to test with, the 16.10 is definitely relevant (I did not have this problem on 16.04) but I can't tell if the upgrade is part of it, (the upgrade may or may not be relevant). Have "full time" wired or wireless connection (does not matter which used) Part time OpenVPN connection set up via NetworkManager. Steps to reproduce 1. Fresh boot 2. ping a device on the VPN network (eg amachine.remotelan ) Result: "ping: amachine.remotelan: Name or service not known" 3. Connect to the VPN service via Network Manager. 4. ping amachine.remotelan - result: PING amachine.remotelan (192.168.68.44) 56(84) bytes of data. 64 bytes from amachine.remotelan (192.168.68.44): icmp_seq=1 ttl=127 time=7.75 ms 5. Disconnect from the VPN service again. ping result again "ping: amachine.remotelan: Name or service not known" 6. Reconnect to the VPN again, and ping again Observed: "ping: amachine.remotelan: Name or service not known" However "ping 192.168.68.44" responds successfully as expected Expected: PING ... 192.168 64 bytes from .. etc to the ping by name --- Further info I'm going to add in a subsequent comment. (just annotating syslog right now!) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1644098/+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 1211110] Re: network manager openvpn dns push data not updating system DNS addresses
This might be my a-ha moment from comment # 64 "after upgrading to 16.10, yes it is even worse, the first VPN connection works as it should, but after disconnect/connect, DNS from VPN isn't propagated" I came to this bug because suddenly my VPN connection wasn't working when I *swear* it was yesterday. I didn't have (/don't remember having!) any problems under 16.04, obviously the 16.10 update was recent. I'm about to reboot - if it comes right after that, then I'll be able to confirm this diagnosis. That said, interesting discussion on http://askubuntu.com/questions/838948/16-10-fail-to-resolve-dns - is dnsmasq out of the equation now? That would suggest problems with upgrading from 16.04 to 16.10 not reconfiguring (and maybe the commenting-out of dns=dnsmasq is the missing sort of step). Also agree with Mathieu in comment # 50 that this bug report is way past its use-by date. It was started for 13.04 and now we're discussing the 16.04 to 16.10 upgrade? Similar symptoms, but highly unlikely that the same remedy would work across all these versions. -- 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/120 Title: network manager openvpn dns push data not updating system DNS addresses Status in network-manager package in Ubuntu: Incomplete Status in openvpn package in Ubuntu: Incomplete Bug description: [Triage Notes] This bug can no longer make progress. Please see comment 50 for details and further instructions. [Original Description] When IPv4 Method is set to Automatic VPN, DNS address recieved from OpenVPN server do not update resolv.conf. This can be achieved when using a standard openvpn config file by adding the lines: script-security 2 up /etc/openvpn/update-resolv-conf down /etc/openvpn/update-resolv-conf In Network-manager there seems to be no option to run connection specific scripts and the DNS data from the server is ignored. Ubuntu 13.04 Network-manager 0.9.8.0-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+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 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full
Seems to be a design flaw rather than a bug. From: Ian WeisserTo: msing...@yahoo.com Sent: Tuesday, November 22, 2016 9:26 PM Subject: [Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full Happy to discuss and help...in the support forums. This CLOSED bug report is not the appropriate location to help people troubleshoot. -- You received this bug notification because you are subscribed to a duplicate bug report (1183692). https://bugs.launchpad.net/bugs/1357093 Title: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full Status in unattended-upgrades package in Ubuntu: Fix Released Bug description: Currently if one chooses to use LVM or encrypted install, a /boot partition is created of 236Mb Once kernel updates start being released this partition soon fills until people are left unable to upgrade. While you and I might know that we need to watch partition space, many of the people we have installing think that a windows disk is a disk and not a partition, education is probably the key - but in the meantime support venues keep needing to deal with the fact the partition is too small and/or old kernels are not purged as new ones install. For workaround and sytem repair, see https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093/+subscriptions -- 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/1357093 Title: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full Status in unattended-upgrades package in Ubuntu: Fix Released Bug description: Currently if one chooses to use LVM or encrypted install, a /boot partition is created of 236Mb Once kernel updates start being released this partition soon fills until people are left unable to upgrade. While you and I might know that we need to watch partition space, many of the people we have installing think that a windows disk is a disk and not a partition, education is probably the key - but in the meantime support venues keep needing to deal with the fact the partition is too small and/or old kernels are not purged as new ones install. For workaround and sytem repair, see https://help.ubuntu.com/community/Lubuntu/Documentation/RemoveOldKernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093/+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 1643239] Re: Xorg crash on compiz login, with Intel 945
I haven't verified this yet, but it looks from the XOrg log like these systems are booting into dual head (with the SVideo out on head 2), 2128x800 total. That width over 2048 is probably what's causing the problem. I did "lose the mouse" on one, and suspected a "phantom head." I went to System Settings -> Display, it didn't show a second head but the whole desktop flickered (I suspect it turned the superfluos head off then.) I suspect it stored this in .config/monitors.xml, I'll check tomorrow if it'll now log into compiz, and if it's got some hotkey that may toggle that on and off. I guess if that works out, then there's no real X bug; perhaps compiz should fall back to llvmpipe if it sees an an otherwise-working opengl implementation, but asks for a large texture and has it fail. Kudos to the compiz, Xorg, and llvmpipe developers btw... the CPU and RAM use were already decent in 14.04 but much lower now, and llvmpipe's actually reasonably fast too. -- 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/1643239 Title: Xorg crash on compiz login, with Intel 945 Status in xorg package in Ubuntu: New Bug description: I went to install Ubuntu (via systemback) onto some Dell D620s, and found "Gnome Flashback (compiz)" crashes back to login prompt, while "Gnome Flashback (Metacity)" does not. The attached logs reflect booting up, (attempting to) log in with Flashback (compiz) then logging in with Flashback (Metacity) to file a bug report. This may be chipset-specific, as I have several other rather antiquated systems: Intel 865-based (Compaq DC5000): Works. (Using LLVMPipe -- this chip is missing a few OpenGL features compiz requires.) Intel 915-based (Dell Inspiron 2200): Works. Intel 945-based (Dell Latitude D620): Crashes to login prompt (this is the machine in this bug report.) Intel 965-based (Dell Latitude 755?): Works. Intel G35-based (slightly newer Dell Latitude 755): Works. I can rule out software differences; since I knew Compiz worked on a 915, I assumed I'd screwed up my systemback LiveUSB somehow, and test- ran it on the D620, 2200, and one of the 755s, and it worked on the 2200 and 755. Left up to me, I'd categorize this as severity "low", I'm just setting these to Flashback Metacity and then stability seems fine. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 BootLog: SB@: clean, 208182/2244608 files, 1302234/8973568 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Flashback:Unity Date: Sat Nov 19 10:12:40 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [1028:01c2] Subsystem: Dell Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [1028:01c2] InstallationDate: Installed on 2016-04-29 (203 days ago) InstallationMedia: MachineType: Dell Inc. Latitude D620 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=702f73f8-ca72-4102-9c59-48f182329bfa ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/16/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0TD761 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/16/2008:svnDellInc.:pnLatitudeD620:pvr:rvnDellInc.:rn0TD761:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D620 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 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.1 version.xserver-xorg-video-nouveau:
[Touch-packages] [Bug 1644086] [NEW] lots of errors
Public bug reported: need to figure this out ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 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 Date: Wed Nov 23 00:12:22 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] [1002:9851] (rev 45) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] [103c:8015] InstallationDate: Installed on 2016-11-16 (7 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: HP HP 15 Notebook PC ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.34 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8015 dmi.board.vendor: HP dmi.board.version: 11.27 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.34:bd12/07/2015:svnHP:pnHP15NotebookPC:pvr:rvnHP:rn8015:rvr11.27:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP 15 Notebook PC dmi.sys.vendor: HP version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 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.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Nov 22 18:29:55 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.2 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 third-party-packages 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/1644086 Title: lots of errors Status in xorg package in Ubuntu: New Bug description: need to figure this out ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 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 Date: Wed Nov 23 00:12:22 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] [1002:9851] (rev 45) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] [103c:8015] InstallationDate: Installed on 2016-11-16 (7 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: HP HP 15 Notebook PC ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.34 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8015 dmi.board.vendor: HP dmi.board.version: 11.27 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.34:bd12/07/2015:svnHP:pnHP15NotebookPC:pvr:rvnHP:rn8015:rvr11.27:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP 15 Notebook PC dmi.sys.vendor: HP version.compiz: compiz
[Touch-packages] [Bug 1644098] Re: Network Manager + OpenVPN does not respond to DNS server change on second connection attempt
Remote VPN is pfSense 2.3.2 >From syslog, expurgated (but not tampered with, no real secrets here): :: Here's the WiFi coming up (showing local LAN) :: Nov 23 19:06:41 rukbat dhclient[2169]: DHCPACK of 192.168.33.117 from 192.168.33.1 Nov 23 19:06:41 rukbat NetworkManager[1216]: [1479881201.2161] address 192.168.33.117 Nov 23 19:06:41 rukbat NetworkManager[1216]: [1479881201.2161] plen 24 (255.255.255.0) ... Nov 23 19:06:41 rukbat NetworkManager[1216]: [1479881201.2161] nameserver '192.168.33.1' ... Nov 23 19:06:41 rukbat NetworkManager[1216]: [1479881201.2162] dhcp4 (wlo1): state changed unknown -> bound ... Nov 23 19:06:41 rukbat systemd-resolved[1282]: Switching to system DNS server 127.0.1.1. ... :: Then here is the VPN coming up for the FIRST time :: .. Nov 23 19:06:45 rukbat NetworkManager[1216]: [1479881205.3847] audit: op="connection-activate" uuid="b53b592d-724d-44bf-a2c4-b7fe818add43" name="Berlin VPN" pid=1979 uid=1000 result="success" Nov 23 19:06:45 rukbat NetworkManager[1216]: [1479881205.3893] vpn-connection[0x55cd7969d200,b53b592d-724d-44bf-a2c4-b7fe818add43,"Berlin VPN",0]: Started the VPN service, PID 2379 Nov 23 19:06:45 rukbat NetworkManager[1216]: [1479881205.3952] vpn-connection[0x55cd7969d200,b53b592d-724d-44bf-a2c4-b7fe818add43,"Berlin VPN",0]: Saw the service appear; activating connection .. Nov 23 19:06:57 rukbat NetworkManager[1216]: [1479881217.9795] dns-mgr: Writing DNS information to /sbin/resolvconf Nov 23 19:06:57 rukbat dnsmasq[2179]: setting upstream servers from DBus Nov 23 19:06:57 rukbat dnsmasq[2179]: using nameserver 192.168.33.1#53(via wlo1) Nov 23 19:06:57 rukbat dnsmasq[2179]: using nameserver fd00::a96:d7ff:feb9:dbe7#53(via wlo1) Nov 23 19:06:57 rukbat dnsmasq[2179]: using nameserver 192.168.68.1#53 for domain csl Nov 23 19:06:57 rukbat dnsmasq[2179]: using nameserver 192.168.68.1#53 for domain 26.70.168.192.in-addr.arpa Nov 23 19:06:57 rukbat dnsmasq[2179]: using nameserver 192.168.68.1#53 for domain 68.168.192.in-addr.arpa Nov 23 19:06:57 rukbat dnsmasq[2179]: using nameserver 192.168.68.1#53 for domain 70.168.192.in-addr.arpa ... Nov 23 19:07:04 rukbat systemd-timesyncd[990]: Synchronized to time server 91.189.91.157:123 (ntp.ubuntu.com). Nov 23 19:07:04 rukbat systemd-resolved[1282]: Using degraded feature set (UDP) for DNS server 127.0.1.1. :: Now I disconnect from the VPN :: Nov 23 19:07:18 rukbat NetworkManager[1216]: [1479881238.8632] audit: op="connection-deactivate" uuid="b53b592d-724d-44bf-a2c4-b7fe818add43" name="Berlin VPN" pid=1979 uid=1000 result="success" Nov 23 19:07:18 rukbat NetworkManager[1216]: [1479881238.8635] dns-mgr: Writing DNS information to /sbin/resolvconf Nov 23 19:07:18 rukbat dnsmasq[2179]: setting upstream servers from DBus Nov 23 19:07:18 rukbat dnsmasq[2179]: using nameserver 192.168.33.1#53(via wlo1) ... Nov 23 19:07:23 rukbat NetworkManager[1216]: nm-openvpn[2379] openvpn[2382] exited with success Nov 23 19:07:23 rukbat nm-dispatcher: req:2 'down' [tun0]: start running ordered scripts... :: And now reconnecting again :: Nov 23 19:07:27 rukbat NetworkManager[1216]: [1479881247.5836] audit: op="connection-activate" uuid="b53b592d-724d-44bf-a2c4-b7fe818add43" name="Berlin VPN" pid=1979 uid=1000 result="success" ... Nov 23 19:07:34 rukbat NetworkManager[1216]: [1479881254.6596] dns-mgr: Writing DNS information to /sbin/resolvconf Nov 23 19:07:34 rukbat dnsmasq[2179]: setting upstream servers from DBus Nov 23 19:07:34 rukbat dnsmasq[2179]: using nameserver 192.168.33.1#53(via wlo1) Nov 23 19:07:34 rukbat dnsmasq[2179]: using nameserver fd00::a96:d7ff:feb9:dbe7#53(via wlo1) Nov 23 19:07:34 rukbat dnsmasq[2179]: using nameserver 192.168.68.1#53 for domain csl Nov 23 19:07:34 rukbat dnsmasq[2179]: using nameserver 192.168.68.1#53 for domain 26.70.168.192.in-addr.arpa Nov 23 19:07:34 rukbat dnsmasq[2179]: using nameserver 192.168.68.1#53 for domain 68.168.192.in-addr.arpa Nov 23 19:07:34 rukbat dnsmasq[2179]: using nameserver 192.168.68.1#53 for domain 70.168.192.in-addr.arpa ... Nov 23 19:07:34 rukbat NetworkManager[1216]: [1479881254.7035] device (tun0): Activation: successful, device activated. I know I've left quite a bit out but none of it appears to be DNS related - and my point is that there is no obvious difference between syslog entries for the first and second connections. ** Tags added: network-manager openvpn -- 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/1644098 Title: Network Manager + OpenVPN does not respond to DNS server change on second connection attempt Status in network-manager package in Ubuntu: New Bug description: Scenario: Discovered on Kubuntu 16.10, upgraded from a fresh install of 16.04. While I only have the one computer to test with, the 16.10 is definitely relevant (I did not
[Touch-packages] [Bug 1643481] Re: Hardware freeze when going fullscreen in certain applications with Wayland
I'm still running into that problem with 3.22.4-1ubuntu1 on Wayland. -- 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/1643481 Title: Hardware freeze when going fullscreen in certain applications with Wayland Status in Ubuntu GNOME: Fix Committed Status in gtk+3.0 package in Ubuntu: Incomplete Bug description: Every time I press "F11" in Firefox or use "F" in VLC to go into fullscreen mode my laptop will freeze, only leaving the audio playing with a frozen image, without the ability to use my keyboard or move my touch pad or mouse, forcing me to restart my computer by holding down my power button. How to reproduce the bug in Ubuntu Gnome 17.04 on Wayland: - Press "F11" by default in Firefox to go into fullscreen mode. - Press "F" by default in VLC to go into and/or leave fullscreen mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1643481/+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 1644063] [NEW] nouveau locking up glslideshow after some time
Public bug reported: XFCE4 / desktop becomes unresponsive (no mouse or keyboard) after running glslideshow for some time. The time range is unknown. Happening 100% of every session. The screensaver is NOT set to power off. Litelocker not being used. Video card temperature is low. I can ssh into locked up system. dmesg reports nouveau fatal error. xdiagnose is installed ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Nov 22 21:15:10 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation G71 [GeForce 7900 GS] [10de:0292] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation G71 [GeForce 7900 GS] [10de:0370] InstallationDate: Installed on 2016-11-05 (17 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=9b509dd9-28f8-42d9-bd9f-c2fa7eb33811 ro vebose=1 drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0605 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: A8R-MVP dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0605:bd12/09/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnA8R-MVP:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 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.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Nov 22 21:09:03 2016 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImExPS/2 Logitech Wheel Mouse MOUSE, id 9 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.2 xserver.video_driver: nouveau ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1644063 Title: nouveau locking up glslideshow after some time Status in xorg package in Ubuntu: New Bug description: XFCE4 / desktop becomes unresponsive (no mouse or keyboard) after running glslideshow for some time. The time range is unknown. Happening 100% of every session. The screensaver is NOT set to power off. Litelocker not being used. Video card temperature is low. I can ssh into locked up system. dmesg reports nouveau fatal error. xdiagnose is installed ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Nov 22 21:15:10 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation G71
[Touch-packages] [Bug 1635812] Re: atril-thumbnailer crashed with SIGSEGV in cmsGetColorSpace()
This bug was fixed in the package poppler - 0.44.0-3ubuntu3 --- poppler (0.44.0-3ubuntu3) zesty; urgency=medium * debian/patches/proper-init.patch: - Fix crashes in atril's and evince's thumbnailers on some PDFs (LP: #1635812). Patch by Marek Kasik. -- Vlad OrlovSun, 23 Oct 2016 21:04:55 +0300 ** Changed in: poppler (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1635812 Title: atril-thumbnailer crashed with SIGSEGV in cmsGetColorSpace() Status in Poppler: Unknown Status in poppler package in Ubuntu: Fix Released Bug description: atril-thumbnailer crashed with SIGSEGV in cmsGetColorSpace() ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: atril 1.12.2-1 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: MATE Date: Sat Oct 22 09:43:08 2016 ExecutablePath: /usr/bin/atril-thumbnailer InstallationDate: Installed on 2016-05-14 (160 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcCmdline: atril-thumbnailer -s 128 file:///home/username/Documents/jedi_complaint.pdf /tmp/.mate_desktop_thumbnail.8JDPPY SegvAnalysis: Segfault happened at: 0x7fdcb0258990 : mov 0x50(%rdi),%eax PC (0x7fdcb0258990) ok source "0x50(%rdi)" (0x0050) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: atril StacktraceTop: cmsGetColorSpace () from /usr/lib/x86_64-linux-gnu/liblcms2.so.2 GfxICCBasedColorSpace::parse(Array*, OutputDev*, GfxState*, int) () from /usr/lib/x86_64-linux-gnu/libpoppler.so.58 GfxColorSpace::parse(GfxResources*, Object*, OutputDev*, GfxState*, int) () from /usr/lib/x86_64-linux-gnu/libpoppler.so.58 Page::loadThumb(unsigned char**, int*, int*, int*) () from /usr/lib/x86_64-linux-gnu/libpoppler.so.58 poppler_page_get_thumbnail () from /usr/lib/x86_64-linux-gnu/libpoppler-glib.so.8 Title: atril-thumbnailer crashed with SIGSEGV in cmsGetColorSpace() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1635812/+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 1643700] Re: mousetweaks process does not get killed when entering desktop
the issue looks like bug #1637758 -- 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/1643700 Title: mousetweaks process does not get killed when entering desktop Status in lightdm package in Ubuntu: New Bug description: This problem occurs on the current development version of zesty; it does not occur on any other Ubuntu version that is currently supported. Lightdm offers the possibility to start the default on-screen keyboard Onboard. Further, Onboard offers the possibility to start the hover click, which is provided by a process called mousetweaks. The hover click consists in having the system automatically perform a left click (and optionally other click types) shortly after the pointer stops moving. It is an accessibility feature for example for people that are not able to click with an hardware device, like mouse buttons. Here is how to start the hover click in lightdm: - Start the on-screen keyboard Onboard by using the accessibility menu at the top right. - Click on the key on the at the right of the Onboard layout that has a pointer as label; an additional column with keys will appear; these are the keys to control the hover click. - Click on the key at the bottom of the column that just appeared and that shows a pointer with a little clock. This is the key to start the hover click. In fact, it starts the mousetweaks process, that provides the hover click feature. The problem now is that the mousetweaks process started by Onboard in lightdm is still running after entering the desktop session. Here is the terminal output after entering the desktop session: $ ps -ef | grep mouse lightdm 1784 1 0 22:30 ?00:00:00 mousetweaks frafu 3584 3546 1 22:31 ?00:00:00 mousetweaks frafu 4324 3105 0 22:31 pts/500:00:00 grep mouse As you can see, the mousetweaks process started under lightdm is still running. The second mousetweaks process in the terminal output was started by settings in the desktop session. This behaviour is new in zesty; in previous Ubuntu versions there was no mousetweaks process left running under lightdm after entering the desktop session. As Onboard has not been responsible until now for killing the mousetweaks process it started under lightdm, I am filing this bug against lightdm. On the other hand, one could argue that since it is Onboard that starts mousetweaks under lightdm, it is also Onboard's job to kill it when exiting lightdm. This is what we from the Onboard development team are wondering now. @ lightdm developers or maintainers Please let us know, what you think about Onboard being responsible to kill mousetweaks when switching when entering the desktop session. I don't know how difficult it will be to implement it, as Onboard cannot simply stop the hover click when it gets killed. In fact, in the desktop session, the hover click can be started independently from Onboard in the Pointing and Clicking tab from the Universal Access control panel in the System Settings. I am also subscribing the other members of the Onboard development team to this bug thread. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1643700/+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 1643737] Re: Network Manager doesn't use 802.1x password entered in GUI
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. ** Changed in: network-manager (Ubuntu) Importance: Undecided => Low -- 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/1643737 Title: Network Manager doesn't use 802.1x password entered in GUI Status in network-manager package in Ubuntu: New Bug description: This is a bug that seems to constantly re-surface across multiple versions in Ubuntu, and I've seen it in other distributions as well. Scenario: I want to enable 802.1x on a wired (*not* wireless), ethernet connection. I enter my identity, my computer cert, my ca cert, my private key file, and my password for my private key. What doesn't work: I confirm the password works by using openssl. NetworkManager does not save the password. When I am asked to re-enter it, the connection fails. I look in syslog, and it complains about the private key password being blank. Workaround: Open the file: /etc/NetworkManager/system-connections/[Your network connection] Example: $> vim /etc/NetworkManager/system-connections/Wired\ connection\ 1 Add the field: private-key-password=[your password] Example: private-key-password=UtterlyPointlessGloballyReadableStoredInPlaintextPassword Save the file. Attempt to re-connect. (and it worked for me). Look in Network Manager UI, the password seems to now be stored. Expected behavior: Entering the password in the GUI works (i.e, it is saved to the file, or at least used temporarily when connecting, either way - the latter would be more secure) Additionally, this whole thing is pretty lame, because Network Manager restricts you to using an encrypted private key, but this is dumb, because the password is then stored in a globally readable file in plaintext. Or you can decide to not save a password, and enter every time in a gui that fails to use the password you type in. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.0-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 21 17:52:44 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-11-21 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 10.0.50.1 dev eno1 proto static metric 100 10.0.50.0/23 dev eno1 proto kernel scope link src 10.0.50.207 metric 100 10.0.254.32 via 10.0.50.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 IwConfig: lono wireless extensions. eno1 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Wired connection 1 fcbffec0-f9e4-4405-acfa-1cd80dec7362 802-3-ethernet 1479779500 Mon 21 Nov 2016 05:51:40 PM PST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/0 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eno1ethernet connected /org/freedesktop/NetworkManager/Devices/0 Wired connection 1 fcbffec0-f9e4-4405-acfa-1cd80dec7362 /org/freedesktop/NetworkManager/ActiveConnection/0 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.0connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to:
[Touch-packages] [Bug 1643847] [NEW] Ubuntu 16.04 no sound after change volume
Public bug reported: I did a new ubuntu 16.04 installation. All worked great until i tried to test the speaker sound. When I did it the analog stereo option dissappeared and only had digital and hdmi option. The sound card is onboard. With ubuntu 14.04 i havent any problem. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luna 1790 F pulseaudio /dev/snd/controlC1: luna 1790 F pulseaudio CurrentDesktop: Unity Date: Tue Nov 22 08:36:07 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-11-21 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V3.3 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7374 dmi.board.vendor: MSI dmi.board.version: 1.0 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.:bvrV3.3:bd12/23/2008:svnMSI:pnMS-7374:pvr1.0:rvnMSI:rnMS-7374:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: MS-7374 dmi.product.version: 1.0 dmi.sys.vendor: MSI ** Affects: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1643847 Title: Ubuntu 16.04 no sound after change volume Status in pulseaudio package in Ubuntu: New Bug description: I did a new ubuntu 16.04 installation. All worked great until i tried to test the speaker sound. When I did it the analog stereo option dissappeared and only had digital and hdmi option. The sound card is onboard. With ubuntu 14.04 i havent any problem. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luna 1790 F pulseaudio /dev/snd/controlC1: luna 1790 F pulseaudio CurrentDesktop: Unity Date: Tue Nov 22 08:36:07 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-11-21 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V3.3 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7374 dmi.board.vendor: MSI dmi.board.version: 1.0 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.:bvrV3.3:bd12/23/2008:svnMSI:pnMS-7374:pvr1.0:rvnMSI:rnMS-7374:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: MS-7374 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1643847/+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 1641722] Re: Tapping a day often results in selecting not the day I wanted to
Thanks for the hard work guys! Glad to see lots of the bugs got fixed in today's rc-proposed. Unfortunately this bug still is happening for me. The space between rows is too small and I still hit a day which is above or below the day I want to tap. -- 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/1641722 Title: Tapping a day often results in selecting not the day I wanted to Status in ubuntu-settings-components package in Ubuntu: Fix Released Bug description: bq M10 rc-proposed silo #2195 Many times when testing after tapping a day I ended up selecting a day which was below or above the day I was aiming for. Please see short video with this and other bugs with this silo: https://youtu.be/3vg6AQZmsqE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings-components/+bug/1641722/+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 1643847] Re: Ubuntu 16.04 no sound after change volume
** Description changed: I did a new ubuntu 16.04 installation. All worked great until i tried to test the speaker sound. When I did it the analog stereo option dissappeared and only had digital and hdmi option. The sound card is - onboard. With ubuntu 14.04 i havent any problem. + onboard (A Realtek ALC888 Audio). With ubuntu 14.04 i havent any + problem. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: luna 1790 F pulseaudio - /dev/snd/controlC1: luna 1790 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: luna 1790 F pulseaudio + /dev/snd/controlC1: luna 1790 F pulseaudio CurrentDesktop: Unity Date: Tue Nov 22 08:36:07 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-11-21 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V3.3 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7374 dmi.board.vendor: MSI dmi.board.version: 1.0 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.:bvrV3.3:bd12/23/2008:svnMSI:pnMS-7374:pvr1.0:rvnMSI:rnMS-7374:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: MS-7374 dmi.product.version: 1.0 dmi.sys.vendor: MSI -- 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/1643847 Title: Ubuntu 16.04 no sound after change volume Status in pulseaudio package in Ubuntu: New Bug description: I did a new ubuntu 16.04 installation. All worked great until i tried to test the speaker sound. When I did it the analog stereo option dissappeared and only had digital and hdmi option. The sound card is onboard (A Realtek ALC888 Audio). With ubuntu 14.04 i havent any problem. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: luna 1790 F pulseaudio /dev/snd/controlC1: luna 1790 F pulseaudio CurrentDesktop: Unity Date: Tue Nov 22 08:36:07 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-11-21 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V3.3 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7374 dmi.board.vendor: MSI dmi.board.version: 1.0 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.:bvrV3.3:bd12/23/2008:svnMSI:pnMS-7374:pvr1.0:rvnMSI:rnMS-7374:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: MS-7374 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1643847/+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 1643870] Re: Pulseaudio fails to detect card after recent update
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- 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/1643870 Title: Pulseaudio fails to detect card after recent update Status in pulseaudio package in Ubuntu: Confirmed Bug description: For months, audio has been working fine on this Dell XPS13 laptop. It is a fresh install of 16.04, from around the time it was released. There were some pulseaudio updates installed on my machine today (see the attached apt term.log output). Since then, audio output has been unreliable. I've discussed this a small amount on AskUbuntu http://askubuntu.com/a/852277/237387 I found that running this command to reinstall the updated packages would sometimes bring back audio output - sometimes for a while, but sometimes only for a few seconds after a reboot. sudo apt install --reinstall pulseaudio pulseaudio-utils pulseaudio-module-bluetooth pulseaudio-module-x11 libpulse-mainloop- glib0 libpulse0 libpulsedsp I can see Launchpad has several almost identical sounding bugs, from many years ago. #461258, #926840, #926840, #995961, #1132982. None of those were ever resolved. I hope this does not end the same way. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Tue Nov 22 23:13:26 2016 InstallationDate: Installed on 2016-05-17 (189 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [Dell System XPS L322X, Realtek ALC3260, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0WW7PG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0WW7PG:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1643870/+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 1643843] Re: Distorted colours after suspend / resume cycle
This is just a display problem - a snapshot is correct, so it really looks like a radeon driver problem, instead of an xorg problem. The wrong colors are always different, so every cycle produces a different result. For a photo as background it almost looks like modern art ;-) -- 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/1643843 Title: Distorted colours after suspend / resume cycle Status in xorg package in Ubuntu: New Bug description: When waking up the system from a suspend-resume cycle, the display most times shows distorted colours. As a workaround one can switch to the linux console (VT) and back to fix the display. Alternatively triggering DPMS also fixes the problem (xset dpms force off ; sleep 0.1; xset dpms force on) Hardware: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] PCIID: 1002:6779 I've tested Ubuntu Xenial (16.04) with the latest updates: mesa 11.2.0-1ubuntu2.2 xserver-xorg-video-radeon 1:7.7.0-1 linux-image-4.4.0-47-generic 4.4.0-47.68 xserver-xorg-core 2:1.18.3-1ubuntu2.3 I've tried older kernels, xorg, linux-firmware, as a colleague claimed it started for him after some of the latest Ubuntu updates, but couldn't find a working configuration. I also checked Ubuntu Yakkety (16.10), where I couldn't reproduce with XFCE, but instantly with the Unity session, but probably XFCE was just lucky, as sometimes I also had series of working (~5) cycles. Current versions: mesa 12.0.3-1ubuntu2 xserver-xorg-video-radeon 1:7.7.1-1 linux-image-4.8.0-27-generic 4.8.0-27.29 xserver-xorg-core 2:1.18.4-1ubuntu6.1 I'm also going to test Trusty (14.04) to check if it's really a regression. At least I have never seen this problem while running it. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 22 12:21:24 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Radeon HD 6450 [1642:3a75] Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 4524BL8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic root=UUID=4dda3a4b-6e9c-49ba-a969-5d2146f02b60 ro splash quiet vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 9HKT54AUS dmi.board.vendor: LENOVO 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:bvnLENOVO:bvr9HKT54AUS:bd10/16/2012:svnLENOVO:pn4524BL8:pvrThinkCentreM91p:rvnLENOVO:rn:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: 4524BL8 dmi.product.version: ThinkCentre M91p dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Tue Nov 22 11:56:40 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1643843/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1641720] Re: Selecting a day does not display all day event for that day
I updated to today's rc-proposed on M10 (r236) and this bug is still present. -- 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/1641720 Title: Selecting a day does not display all day event for that day Status in indicator-datetime package in Ubuntu: Fix Released Bug description: bq M10 rc-proposed silo #2195 When I select a day from the calendar, I can see events for that day but it does not work with all-day events. Please see short video with this and other bugs with this silo: https://youtu.be/3vg6AQZmsqE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1641720/+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 1643870] [NEW] Pulseaudio fails to detect card after recent update
Public bug reported: For months, audio has been working fine on this Dell XPS13 laptop. It is a fresh install of 16.04, from around the time it was released. There were some pulseaudio updates installed on my machine today (see the attached apt term.log output). Since then, audio output has been unreliable. I've discussed this a small amount on AskUbuntu http://askubuntu.com/a/852277/237387 I found that running this command to reinstall the updated packages would sometimes bring back audio output - sometimes for a while, but sometimes only for a few seconds after a reboot. sudo apt install --reinstall pulseaudio pulseaudio-utils pulseaudio- module-bluetooth pulseaudio-module-x11 libpulse-mainloop-glib0 libpulse0 libpulsedsp I can see Launchpad has several almost identical sounding bugs, from many years ago. #461258, #926840, #926840, #995961, #1132982. None of those were ever resolved. I hope this does not end the same way. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Tue Nov 22 23:13:26 2016 InstallationDate: Installed on 2016-05-17 (189 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [Dell System XPS L322X, Realtek ALC3260, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0WW7PG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0WW7PG:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "excerpt from apt term.log, from when pulseaudio was upgraded" https://bugs.launchpad.net/bugs/1643870/+attachment/4781479/+files/term.log -- 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/1643870 Title: Pulseaudio fails to detect card after recent update Status in pulseaudio package in Ubuntu: New Bug description: For months, audio has been working fine on this Dell XPS13 laptop. It is a fresh install of 16.04, from around the time it was released. There were some pulseaudio updates installed on my machine today (see the attached apt term.log output). Since then, audio output has been unreliable. I've discussed this a small amount on AskUbuntu http://askubuntu.com/a/852277/237387 I found that running this command to reinstall the updated packages would sometimes bring back audio output - sometimes for a while, but sometimes only for a few seconds after a reboot. sudo apt install --reinstall pulseaudio pulseaudio-utils pulseaudio-module-bluetooth pulseaudio-module-x11 libpulse-mainloop- glib0 libpulse0 libpulsedsp I can see Launchpad has several almost identical sounding bugs, from many years ago. #461258, #926840, #926840, #995961, #1132982. None of those were ever resolved. I hope this does not end the same way. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Tue Nov 22 23:13:26 2016 InstallationDate: Installed on 2016-05-17 (189 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [Dell System XPS L322X, Realtek ALC3260, Speaker, Internal]
[Touch-packages] [Bug 1624251] Re: gsettings-qt fails test_reset() property count on Qt 5.7.1
** Changed in: qtdeclarative-opensource-src (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-qt in Ubuntu. https://bugs.launchpad.net/bugs/1624251 Title: gsettings-qt fails test_reset() property count on Qt 5.7.1 Status in gsettings-qt package in Ubuntu: Invalid Status in qtdeclarative-opensource-src package in Ubuntu: In Progress Bug description: -- FAIL! : GSettings::test_reset() property count Actual (): 0 Expected (): 1 Loc: [/«BUILDDIR»/gsettings-qt-0.1+16.04.20160329/tests/tst_GSettings.qml(102)] (process:7207): GLib-GIO-WARNING **: g_settings_set_value: value for key 'test-enum' in schema 'com.canonical.gsettings.Test' is outside of valid range -- (https://launchpadlibrarian.net/284597323/buildlog_ubuntu-yakkety- amd64.gsettings-qt_0.1+16.04.20160329-0ubuntu2~5_BUILDING.txt.gz) More information about Qt 5.7 at https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-qt/+bug/1624251/+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 1643889] [NEW] [HDA-Intel - HDA Intel PCH, playback] No sound at all
Public bug reported: Fresh Ubuntu 16.04 installation in a newly bought computer and no sound at all. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: hajer 14469 F...m pulseaudio /dev/snd/controlC0: hajer 14469 F pulseaudio CurrentDesktop: Unity Date: Tue Nov 22 14:35:47 2016 InstallationDate: Installed on 2016-11-18 (3 days ago) InstallationMedia: Ubuntu 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/pcmC0D0c: hajer 14469 F...m pulseaudio /dev/snd/controlC0: hajer 14469 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) dmi.bios.date: 08/03/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X556UQK.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X556UQK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX556UQK.208:bd08/03/2016:svnASUSTeKCOMPUTERINC.:pnX556UQK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UQK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X556UQK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1643889 Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Fresh Ubuntu 16.04 installation in a newly bought computer and no sound at all. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: hajer 14469 F...m pulseaudio /dev/snd/controlC0: hajer 14469 F pulseaudio CurrentDesktop: Unity Date: Tue Nov 22 14:35:47 2016 InstallationDate: Installed on 2016-11-18 (3 days ago) InstallationMedia: Ubuntu 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/pcmC0D0c: hajer 14469 F...m pulseaudio /dev/snd/controlC0: hajer 14469 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) dmi.bios.date: 08/03/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X556UQK.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X556UQK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX556UQK.208:bd08/03/2016:svnASUSTeKCOMPUTERINC.:pnX556UQK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UQK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X556UQK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1643889/+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 1638922] Re: [needs-packaging] tar : CVE-2016-6321 not patched in stable
Fix released USN-3132-1 ** Changed in: tar (Ubuntu) Status: New => Fix Committed ** Changed in: tar (Ubuntu) Status: Fix Committed => Fix Released ** Summary changed: - [needs-packaging] tar : CVE-2016-6321 not patched in stable + tar : CVE-2016-6321 not patched in stable -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1638922 Title: tar : CVE-2016-6321 not patched in stable Status in tar package in Ubuntu: Fix Released Bug description: CVE-2016-6321 path name extract bypass vulnerability is not patched in stable releases of yakkety, xenial and other supported releases. The maintainer appears to have only pushed the patch to zesty proposed. Please push the patch for the stable releases as this bug could have seroius implications in certain environments. Upstream debian has already pushed the patch to stable. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842339 https://people.canonical.com/~ubuntu- security/cve/2016/CVE-2016-6321.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tar/+bug/1638922/+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 1643869] [NEW] Problem using hubiC app
Public bug reported: With the hubiC app it is impossible to download a file. It is possible to send files there. ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New -- 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/1643869 Title: Problem using hubiC app Status in webbrowser-app package in Ubuntu: New Bug description: With the hubiC app it is impossible to download a file. It is possible to send files there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1643869/+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 1643789] Re: Backport packages for 16.04.2 lts-hwe stack
** Changed in: libdrm (Ubuntu) Status: New => Invalid ** Changed in: libclc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1643789 Title: Backport packages for 16.04.2 lts-hwe stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libclc source package in Xenial: New Status in libdrm source package in Xenial: New Bug description: We need a few packages backported to xenial for lts-hwe X stack. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1643789/+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 1643869] Re: Problem using hubiC app
This doesn't work in webbrowser-app either. When tapping a file to download it, a POST request is sent, but the webview never gets the download request. Here is what I get with the inspector for the POST request (for a file named "pdf.pdf"): = General = Request URL:https://hubic.com/home/browser/download/ Request Method:POST Status Code:200 OK Remote Address:178.33.124.183:443 = Response Headers = Cache-Control:no-cache, no-store, max-age=0, must-revalidate Content-Disposition:attachment;filename="pdf.pdf" Content-Length:433994 Content-Transfer-Encoding:binary Content-Type:application/pdf Date:Tue, 22 Nov 2016 12:03:25 GMT Expires:Thu, 19 Nov 1981 08:52:00 GMT Pragma:no-cache Server:nginx Strict-Transport-Security:max-age=15768000 = Request Headers = (Provisional headers are shown) Content-Type:application/x-www-form-urlencoded Origin:https://hubic.com Referer:https://hubic.com/home/browser/ Upgrade-Insecure-Requests:1 User-Agent:Mozilla/5.0 (Linux; Ubuntu 15.04 like Android 4.4) AppleWebKit/537.36 Chromium/53.0.2785.143 Mobile Safari/537.36 = Form Data = dlName:pdf.pdf X_TOKEN:2dd2802d947db8dbe68ae2d075f41418 files:["default/pdf.pdf"] ** Changed in: webbrowser-app (Ubuntu) Status: New => Confirmed ** Changed in: webbrowser-app (Ubuntu) Importance: Undecided => Medium ** Summary changed: - Problem using hubiC app + Cannot download files from hubic.com -- 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/1643869 Title: Cannot download files from hubic.com Status in webbrowser-app package in Ubuntu: Confirmed Bug description: With the hubiC app it is impossible to download a file. It is possible to send files there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1643869/+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 1637758] Re: lightdm greeter session not properly shut down at login
This bug was fixed in the package lightdm - 1.20.0-0ubuntu3 --- lightdm (1.20.0-0ubuntu3) zesty; urgency=medium * Add debian/patches/terminate-session.patch: Terminate leftover processes in greeter session. It can happen that the greeter session does not properly clean up itself on logout. This causes leaked processes like settings-daemon which act on the user session as they share the same $DISPLAY. Ask logind to terminate remaining processes in the greeter session on closing, which is more robust than trying to fix every greeter. (LP: #1637758) -- Martin PittTue, 22 Nov 2016 09:43:39 +0100 ** Changed in: lightdm (Ubuntu) Status: Fix Committed => Fix Released -- 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/1637758 Title: lightdm greeter session not properly shut down at login Status in lightdm package in Ubuntu: Fix Released Bug description: I am using lightdm with 2 seats. After 2409 revision randomly one of two seats does not work correctly. xsettings plugin from unity-settings-daemon or gnome-settings-deamon fails to start because there is already _XSESSION_S* manager running. After revision 2409 in system monitor I see that there is still running unity-settings-daemon started by lightdm. Reverting this revision fixes my problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1637758/+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 1643870] Re: Pulseaudio fails to detect card after recent update
This is the Sound configuration options. Only "Dummy Output" shows up. ** Attachment added: "sound options window" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1643870/+attachment/4781486/+files/Sound_010.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1643870 Title: Pulseaudio fails to detect card after recent update Status in pulseaudio package in Ubuntu: New Bug description: For months, audio has been working fine on this Dell XPS13 laptop. It is a fresh install of 16.04, from around the time it was released. There were some pulseaudio updates installed on my machine today (see the attached apt term.log output). Since then, audio output has been unreliable. I've discussed this a small amount on AskUbuntu http://askubuntu.com/a/852277/237387 I found that running this command to reinstall the updated packages would sometimes bring back audio output - sometimes for a while, but sometimes only for a few seconds after a reboot. sudo apt install --reinstall pulseaudio pulseaudio-utils pulseaudio-module-bluetooth pulseaudio-module-x11 libpulse-mainloop- glib0 libpulse0 libpulsedsp I can see Launchpad has several almost identical sounding bugs, from many years ago. #461258, #926840, #926840, #995961, #1132982. None of those were ever resolved. I hope this does not end the same way. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Tue Nov 22 23:13:26 2016 InstallationDate: Installed on 2016-05-17 (189 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [Dell System XPS L322X, Realtek ALC3260, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0WW7PG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0WW7PG:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1643870/+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 1643812] Re: There is no entry in 'Play sound through' list when plug in headset jack [8086:9d70].
The attachment "multiple_jacks.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- 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/1643812 Title: There is no entry in 'Play sound through' list when plug in headset jack [8086:9d70]. Status in pulseaudio package in Ubuntu: New Bug description: 1. Install 14.04.5 image on P50s 2. Login system 3. $ sudo apt-get update 4. $ apt-get dist-upgrade sudo apt-get install --install-recommends linux-generic-lts-xenial xserver-xorg-core-lts-xenial xserver-xorg-lts-xenial xserver-xorg-video-all-lts-xenial xserver-xorg-input-all-lts-xenial libwayland-egl1-mesa-lts-xenial 5. Reboot the system 6. Login system 7. Open Sound setting window 8. Plug headset jack, unplug headset jack. The kernel is 4.4.0-47, and the pulseaudio is 1:4.0-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1643812/+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 1641720] Re: Selecting a day does not display all day event for that day
Confirmed not working arale rc-proposed. Calendar shows a dot for the event but no details appear below. -- 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/1641720 Title: Selecting a day does not display all day event for that day Status in indicator-datetime package in Ubuntu: Fix Released Bug description: bq M10 rc-proposed silo #2195 When I select a day from the calendar, I can see events for that day but it does not work with all-day events. Please see short video with this and other bugs with this silo: https://youtu.be/3vg6AQZmsqE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1641720/+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 1617637] Re: wget crashing in libc if using screen output
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: wget (Ubuntu) Status: New => Confirmed -- 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/1617637 Title: wget crashing in libc if using screen output Status in wget package in Ubuntu: Confirmed Bug description: I got wget crashing repeatetly in libc if verbose or progress is enable. If use "-nv" flag it does not crash. This is dmesg: [44755.426609] wget[14324]: segfault at 564d49cc7000 ip 7f95b0686328 sp 7ffd8d1066c8 error 6 in libc-2.23.so[7f95b0514000+1c] [44760.175689] wget[14336]: segfault at 56409e4cd000 ip 7f12bb66e328 sp 7fff63a84d68 error 6 in libc-2.23.so[7f12bb4fc000+1c] [44827.776604] wget[16986]: segfault at 55b4cd4e5000 ip 7f7917462328 sp 7fff996f6a48 error 6 in libc-2.23.so[7f79172f+1c] [44831.555214] wget[17010]: segfault at 56549efa1000 ip 7f62d4acb328 sp 7ffc9f4039a8 error 6 in libc-2.23.so[7f62d4959000+1c] This is a strace of the command: write(2, "Berserk_.mp4 "..., 189Berserkmp4 2%[+> ] 9,72M 395KB/s ) = 189 select(4, [3], NULL, NULL, {0, 95}) = 1 (in [3], left {0, 949998}) read(3, "\214\22\366SA\276\312\344L\"\274:oD[\210\246\222,N\362w\253\310\\2A\360|\306\333;"..., 8192) = 8192 write(4, "\214\22\366SA\276\312\344L\"\274:oD[\210\246\222,N\362w\253\310\\2A\360|\306\333;"..., 4096) = 4096 write(4, "j\312\177l\367o\264\2220C\330\364\326Fc\375\200\303\213wa\356\237y,\236\212\315CI?\352"..., 4096) = 4096 select(4, [3], NULL, NULL, {0, 95}) = 1 (in [3], left {0, 94}) read(3, "\364\264\2640:6q\245v\265\367\230\204\30\302\236\265\335\267\242\322\\\240\364L\374\274\260\3307[\r"..., 8192) = 8192 write(4, "\364\264\2640:6q\245v\265\367\230\204\30\302\236\265\335\267\242\322\\\240\364L\374\274\260\3307[\r"..., 4096) = 4096 write(4, "Og\0233\354\324v\251\211\332\274\377\322\347\214HdD(\0028\227\337v\311\334\25s\206|\2143"..., 4096) = 4096 select(4, [3], NULL, NULL, {0, 95}) = 1 (in [3], left {0, 94}) read(3, "\2454\237\236\372;\357\270\276\212Kkd\2\302\272\343x\344Y*\201q\35\"\255h\225\203\17]\240"..., 8192) = 8192 write(4, "\2454\237\236\372;\357\270\276\212Kkd\2\302\272\343x\344Y*\201q\35\"\255h\225\203\17]\240"..., 4096) = 4096 write(4, "\316\263\213y\342\306\253\251x&\355\377m\367}\215\217Y\363\356\330}!]\326\326R\334\25!\306\236"..., 4096) = 4096 select(4, [3], NULL, NULL, {0, 95}) = 1 (in [3], left {0, 94}) read(3, "\302h\211\244\325\32\275\326'D6E\325Y/f\200w\n\25\277n]\26\362\16~b\265.\222\322"..., 8192) = 8192 write(4, "\302h\211\244\325\32\275\326'D6E\325Y/f\200w\n\25\277n]\26\362\16~b\265.\222\322"..., 4096) = 4096 write(4, "\327t\20\275}j\377(\201\336GF\372!i\31\3604o\377\\\273\361\347\277\326\376\3425~\313O"..., 4096) = 4096 select(4, [3], NULL, NULL, {0, 95}) = 1 (in [3], left {0, 94}) read(3, "\371+*\22663e0ip\30\0017w;\376\372\243\312\235\222\212Oj\225\267\315\352t\27\372\266"..., 8192) = 8192 write(4, "\371+*\22663e0ip\30\0017w;\376\372\243\312\235\222\212Oj\225\267\315\352t\27\372\266"..., 4096) = 4096 write(4, "[3\276(\205\244\3144\236\216\\\220\215\267\"Q\22\262\261P\364\332\204\344n1\fP\320\235\16s"..., 4096) = 4096 select(4, [3], NULL, NULL, {0, 95}) = 1 (in [3], left {0, 94}) read(3, "\377\371\257\274\257\244\266/C$\257\341EpU\352\3410\325F\265r\221\271\331\227w\344\v\376\34\5"..., 8192) = 8192 write(4, "\377\371\257\274\257\244\266/C$\257\341EpU\352\3410\325F\265r\221\271\331\227w\344\v\376\34\5"..., 4096) = 4096 write(4, "\23P\272\345\211E\324Jo\367T*\v\366D\362\211~\10u\34\253\10Gh\265&\206\20\321{\f"..., 4096) = 4096 select(4, [3], NULL, NULL, {0, 95}) = 1 (in [3], left {0, 94}) read(3, "(\315\265\366\307\224\32\30\245v\376\256\204\210d\311\250\315,|8\227#o\317\234\5L\21Zr\224"..., 8192) = 8192 write(4, "(\315\265\366\307\224\32\30\245v\376\256\204\210d\311\250\315,|8\227#o\317\234\5L\21Zr\224"..., 4096) = 4096 write(4, "\373\206\30\205\3\177Z\270\f\3rI\236s\244\340\377\3259\204\300\274\220W\330\7E\231\nU\301\257"..., 4096) = 4096 select(4, [3], NULL, NULL, {0, 95}) = 1 (in [3], left {0, 94}) read(3, "_\3117_?M\362ae\263\267\177HtS\206\24\260\364\341\374\217\213\351I\342\345q\372\r\36\350"..., 8192) = 8192 write(4, "_\3117_?M\362ae\263\267\177HtS\206\24\260\364\341\374\217\213\351I\342\345q\372\r\36\350"..., 4096) = 4096 write(4, "\27&\311\263\362\f\33AgYC\224R\224l\245!1\251\353\366'#jd\35tA\202T4\301"..., 4096) = 4096 select(4, [3], NULL, NULL, {0, 95}) = 1 (in [3], left {0, 94}) read(3,
[Touch-packages] [Bug 1643536] Re: User can skip wizard by opening settings from the OSK
** Description changed: - Environment: + Environment: current build number: 24 device name: frieza channel: ubuntu-touch/rc/bq-aquaris-pd.en last update: 2016-11-21 09:05:56 version version: 24 version ubuntu: 20161118 version device: 20160809.0 version custom: 20160831--42-26-vivid Steps to reproduce: - 1º Boot frieza and start wizard + 1º Boot frieza and start wizard 2º On Wi-Fi connection screen select a network 3º When the keyboard shows up tap and hold the world icon to display text options 4º Notice that settings option is available, tap on it 5º When it opens, cancel the wi-fi connection dialog and swipe from right edge to show the spread Current result: user can skip wizard config Expected result: text entry settings shouldn't be available when wizard is running Add info: on krillin/rc this option isn't listed to avoid skipping the - wizard. It is probably reproducible on frieza 64 + wizard. /o\ also happening on frieza_arm64 build nº 87 -- 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/1643536 Title: User can skip wizard by opening settings from the OSK Status in ubuntu-keyboard package in Ubuntu: New Status in unity8 package in Ubuntu: Triaged Bug description: Environment: current build number: 24 device name: frieza channel: ubuntu-touch/rc/bq-aquaris-pd.en last update: 2016-11-21 09:05:56 version version: 24 version ubuntu: 20161118 version device: 20160809.0 version custom: 20160831--42-26-vivid Steps to reproduce: 1º Boot frieza and start wizard 2º On Wi-Fi connection screen select a network 3º When the keyboard shows up tap and hold the world icon to display text options 4º Notice that settings option is available, tap on it 5º When it opens, cancel the wi-fi connection dialog and swipe from right edge to show the spread Current result: user can skip wizard config Expected result: text entry settings shouldn't be available when wizard is running Add info: on krillin/rc this option isn't listed to avoid skipping the wizard. /o\ also happening on frieza_arm64 build nº 87 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1643536/+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 1638338] Re: Can not ssh with tr_TR.UTF-8 locales (Bad configuration options)
I have encountered this bug today. You can reproduce it by launching ssh in Turkish locale environment: LC_ALL=tr_TR.UTF8 ssh u...@example.com Ubuntu version is 16.10, and openssh-client version is 1:7.3p1-1. I guess the client converts parameters in config files to lowercase when parsing and gives error because both GSSAPIAuthentication and GSSAPIDelegateCredentials parameters has "I" character. Turkish have two separate "i" character dotted and dotless. Per the Unicode standard, our lowercase "i" becomes "İ" (U+0130 "Latin Capital Letter I With Dot Above") when it moves to uppercase. Similarly, our uppercase "I" becomes "ı" (U+0131 "Latin Small Letter Dotless I") when it moves to lowercase. For additional info, you can check out the links below: http://www.moserware.com/2008/02/does-your-code-pass-turkey-test.html https://blog.codinghorror.com/whats-wrong-with-turkey/ http://mattryall.net/blog/2009/02/the-infamous-turkish-locale-bug -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1638338 Title: Can not ssh with tr_TR.UTF-8 locales (Bad configuration options) Status in openssh package in Ubuntu: Incomplete Bug description: I can not ssh to any host with Turkish locales. What I expected to happen: I expected that 'ssh some_host' command would successfully run. What actually happened 'ssh some_host' command failed with an error. Steps to produce: 1. Open a terminal 2. Run LANG=tr_TR.UTF-8 ssh some_host If I run ssh with tr_TR.UTF-8 locale, the first error I get is: $HOME/.ssh/config: line 7: Bad configuration option: Identityfile $HOME/.ssh/config: terminating, 1 bad configuration options If I commend IdentityFile option from $HOME/.ssh/config file and re- run the command, I get this: debug1: Reading configuration data ~/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * /etc/ssh/ssh_config: line 55: Bad configuration option: gssapIauthentication /etc/ssh/ssh_config: line 56: Bad configuration option: gssapIdelegatecredentials /etc/ssh/ssh_config: terminating, 2 bad configuration options If I commend GSSAPIAuthentication and GSSAPIDelegateCredentials option, I can ssh to a host. So to ssh to a host with tr_TR.UTF-8 locale, one must commend out IdentityFile, if it is used, GSSAPIAuthentication and GSSAPIDelegateCredentials optons. Workaround: LC_ALL=C ssh some_host LC_ALL=C apt-cache policy openssh-client openssh-client: Installed: 1:7.3p1-1 Candidate: 1:7.3p1-1 Version table: *** 1:7.3p1-1 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status LC_ALL=C lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.10 Release: 16.10 Codename: yakkety ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: openssh-client 1:7.3p1-1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 1 19:37:35 2016 InstallationDate: Installed on 2016-10-23 (9 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_7.3p1 Ubuntu-1, OpenSSL 1.0.2g 1 Mar 2016 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1638338/+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 1636912] Re: systemd-networkd runs too late for cloud-init.service (net)
** Changed in: systemd (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1636912 Title: systemd-networkd runs too late for cloud-init.service (net) Status in systemd: New Status in cloud-init package in Ubuntu: Triaged Status in systemd package in Ubuntu: In Progress Status in cloud-init source package in Xenial: Confirmed Status in systemd source package in Xenial: Triaged Bug description: Ubuntu Core 16 images using cloud-init fail to function when the DataSource is over the network (Like OpenStack) as networking is not yet available when cloud-init.service runs. cloud-init service unit deps look like this: [Unit] Description=Initial cloud-init job (metadata service crawler) DefaultDependencies=no Wants=cloud-init-local.service Wants=local-fs.target Wants=sshd-keygen.service Wants=sshd.service After=cloud-init-local.service After=networking.service Requires=networking.service Before=basic.target Before=dbus.socket Before=network-online.target Before=sshd-keygen.service Before=sshd.service Before=systemd-user-sessions.service Conflicts=shutdown.target Here's networkd unit deps: [Unit] Description=Network Service Documentation=man:systemd-networkd.service(8) ConditionCapability=CAP_NET_ADMIN DefaultDependencies=no # dbus.service can be dropped once on kdbus, and systemd-udevd.service can be # dropped once tuntap is moved to netlink After=systemd-udevd.service dbus.service network-pre.target systemd-sysusers.service systemd-sysctl.service Before=network.target multi-user.target shutdown.target Conflicts=shutdown.target Wants=network.target # On kdbus systems we pull in the busname explicitly, because it # carries policy that allows the daemon to acquire its name. Wants=org.freedesktop.network1.busname After=org.freedesktop.network1.busname And a critical-chain output: root@snap-test7:~# systemd-analyze critical-chain systemd-networkd Failed to get ID: Unit name systemd-networkd is not valid. The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. root@snap-test7:~# systemd-analyze critical-chain systemd-networkd.service The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. systemd-networkd.service +440ms └─dbus.service @11.461s └─basic.target @11.403s └─sockets.target @11.401s └─dbus.socket @11.398s └─cloud-init.service @10.127s +1.266s └─networking.service @9.305s +799ms └─network-pre.target @9.295s └─cloud-init-local.service @3.822s +5.469s └─local-fs.target @3.813s └─run-cgmanager-fs.mount @12.687s └─local-fs-pre.target @1.393s └─systemd-tmpfiles-setup-dev.service @1.116s +195ms └─kmod-static-nodes.service @887ms +193ms └─system.slice @783ms └─-.slice @721ms cloud-init would need networkd to run at or before 'networking.service' so it can raise networking to then find and use network-based datasources. # grep systemd /usr/share/snappy/dpkg.list ii libnss-resolve:amd64 229-4ubuntu11 amd64nss module to resolve names via systemd-resolved ii libpam-systemd:amd64 229-4ubuntu11 amd64system and service manager - PAM module ii libsystemd0:amd64 229-4ubuntu11 amd64systemd utility library ii systemd 229-4ubuntu11 amd64system and service manager ii systemd-sysv 229-4ubuntu11 amd64system and service manager - SysV links # grep cloud-init /usr/share/snappy/dpkg.list ii cloud-init 0.7.8-201610260005-gf7a5756-0ubuntu1~trunk~ubuntu16.04.1 all Init scripts for cloud instances To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1636912/+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 1643812] Re: There is no entry in 'Play sound through' list when plug in headset jack [8086:9d70].
Here is the patch. ** Patch added: "multiple_jacks.patch" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1643812/+attachment/4781414/+files/multiple_jacks.patch -- 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/1643812 Title: There is no entry in 'Play sound through' list when plug in headset jack [8086:9d70]. Status in pulseaudio package in Ubuntu: New Bug description: 1. Install 14.04.5 image on P50s 2. Login system 3. $ sudo apt-get update 4. $ apt-get dist-upgrade sudo apt-get install --install-recommends linux-generic-lts-xenial xserver-xorg-core-lts-xenial xserver-xorg-lts-xenial xserver-xorg-video-all-lts-xenial xserver-xorg-input-all-lts-xenial libwayland-egl1-mesa-lts-xenial 5. Reboot the system 6. Login system 7. Open Sound setting window 8. Plug headset jack, unplug headset jack. The kernel is 4.4.0-47, and the pulseaudio is 1:4.0-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1643812/+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 1643321] Re: In the upper bar, the keyboard section can make the phone explode
FWIW, it should get better with https://code.launchpad.net/~3v1n0 /ubuntu-settings-components/radio-menuitem/+merge/308084 (which just landed today) -- 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/1643321 Title: In the upper bar, the keyboard section can make the phone explode Status in Canonical System Image: New Status in indicator-keyboard package in Ubuntu: New Status in ubuntu-keyboard package in Ubuntu: New Bug description: I attach a screen to explain better. In my E5 I have two keyboard layout; switching fast between the two cause the phone to select both and all the CPUs to overload making the phone unusable. The only way to exit is the reboot To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1643321/+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 1643843] [NEW] Distorted colours after suspend / resume cycle
Public bug reported: When waking up the system from a suspend-resume cycle, the display most times shows distorted colours. As a workaround one can switch to the linux console (VT) and back to fix the display. Alternatively triggering DPMS also fixes the problem (xset dpms force off ; sleep 0.1; xset dpms force on) Hardware: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] PCIID: 1002:6779 I've tested Ubuntu Xenial (16.04) with the latest updates: mesa 11.2.0-1ubuntu2.2 xserver-xorg-video-radeon 1:7.7.0-1 linux-image-4.4.0-47-generic 4.4.0-47.68 xserver-xorg-core 2:1.18.3-1ubuntu2.3 I've tried older kernels, xorg, linux-firmware, as a colleague claimed it started for him after some of the latest Ubuntu updates, but couldn't find a working configuration. I also checked Ubuntu Yakkety (16.10), where I couldn't reproduce with XFCE, but instantly with the Unity session, but probably XFCE was just lucky, as sometimes I also had series of working (~5) cycles. Current versions: mesa 12.0.3-1ubuntu2 xserver-xorg-video-radeon 1:7.7.1-1 linux-image-4.8.0-27-generic 4.8.0-27.29 xserver-xorg-core 2:1.18.4-1ubuntu6.1 I'm also going to test Trusty (14.04) to check if it's really a regression. At least I have never seen this problem while running it. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 22 12:21:24 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Radeon HD 6450 [1642:3a75] Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 4524BL8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic root=UUID=4dda3a4b-6e9c-49ba-a969-5d2146f02b60 ro splash quiet vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 9HKT54AUS dmi.board.vendor: LENOVO 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:bvnLENOVO:bvr9HKT54AUS:bd10/16/2012:svnLENOVO:pn4524BL8:pvrThinkCentreM91p:rvnLENOVO:rn:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: 4524BL8 dmi.product.version: ThinkCentre M91p dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Tue Nov 22 11:56:40 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 corruption ubuntu yakkety ** Attachment added: "Broken Unity desktop after resume from suspend" https://bugs.launchpad.net/bugs/1643843/+attachment/4781443/+files/photo_desktop_broken.jpg -- 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/1643843 Title: Distorted colours after suspend / resume cycle Status in xorg package in Ubuntu: New Bug description: When waking up the system from a suspend-resume cycle, the display most times shows distorted colours. As a workaround one can switch to the linux console (VT) and back to fix the display. Alternatively triggering DPMS also fixes the problem (xset dpms force off ; sleep
[Touch-packages] [Bug 1643843] Re: Distorted colours after suspend / resume cycle
** Attachment added: "Correct Unity desktop" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1643843/+attachment/4781463/+files/photo_desktop_ok.jpg -- 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/1643843 Title: Distorted colours after suspend / resume cycle Status in xorg package in Ubuntu: New Bug description: When waking up the system from a suspend-resume cycle, the display most times shows distorted colours. As a workaround one can switch to the linux console (VT) and back to fix the display. Alternatively triggering DPMS also fixes the problem (xset dpms force off ; sleep 0.1; xset dpms force on) Hardware: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] PCIID: 1002:6779 I've tested Ubuntu Xenial (16.04) with the latest updates: mesa 11.2.0-1ubuntu2.2 xserver-xorg-video-radeon 1:7.7.0-1 linux-image-4.4.0-47-generic 4.4.0-47.68 xserver-xorg-core 2:1.18.3-1ubuntu2.3 I've tried older kernels, xorg, linux-firmware, as a colleague claimed it started for him after some of the latest Ubuntu updates, but couldn't find a working configuration. I also checked Ubuntu Yakkety (16.10), where I couldn't reproduce with XFCE, but instantly with the Unity session, but probably XFCE was just lucky, as sometimes I also had series of working (~5) cycles. Current versions: mesa 12.0.3-1ubuntu2 xserver-xorg-video-radeon 1:7.7.1-1 linux-image-4.8.0-27-generic 4.8.0-27.29 xserver-xorg-core 2:1.18.4-1ubuntu6.1 I'm also going to test Trusty (14.04) to check if it's really a regression. At least I have never seen this problem while running it. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 22 12:21:24 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Radeon HD 6450 [1642:3a75] Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 4524BL8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic root=UUID=4dda3a4b-6e9c-49ba-a969-5d2146f02b60 ro splash quiet vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 9HKT54AUS dmi.board.vendor: LENOVO 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:bvnLENOVO:bvr9HKT54AUS:bd10/16/2012:svnLENOVO:pn4524BL8:pvrThinkCentreM91p:rvnLENOVO:rn:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: 4524BL8 dmi.product.version: ThinkCentre M91p dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Tue Nov 22 11:56:40 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1643843/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages
[Touch-packages] [Bug 1637758] Re: lightdm greeter session not properly shut down at login
** Changed in: lightdm (Ubuntu) Status: In Progress => Fix Committed -- 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/1637758 Title: lightdm greeter session not properly shut down at login Status in lightdm package in Ubuntu: Fix Committed Bug description: I am using lightdm with 2 seats. After 2409 revision randomly one of two seats does not work correctly. xsettings plugin from unity-settings-daemon or gnome-settings-deamon fails to start because there is already _XSESSION_S* manager running. After revision 2409 in system monitor I see that there is still running unity-settings-daemon started by lightdm. Reverting this revision fixes my problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1637758/+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 1619600] Re: [SRU] New stable release 1.8.3
Brilliant. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1619600 Title: [SRU] New stable release 1.8.3 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Xenial: Fix Committed Status in gst-plugins-bad1.0 source package in Xenial: Fix Committed Status in gst-plugins-base1.0 source package in Xenial: Fix Committed Status in gst-plugins-good1.0 source package in Xenial: Fix Committed Status in gst-plugins-ugly1.0 source package in Xenial: Fix Committed Status in gstreamer-vaapi source package in Xenial: Incomplete Status in gstreamer1.0 source package in Xenial: Fix Committed Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.8 series that 16.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] One of the fixes could be bad. Watch out for it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1619600/+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 1553150] Re: Ubuntu One account does not stay logged in or does not sign in at all
Partially solved by removing folder /home/phablet/.config/libaccounts- glib (it removed all online accounts, obviously), now it stays logged, but I still get 401 UNAUTHORIZED when trying to install any upgrade -- 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/1553150 Title: Ubuntu One account does not stay logged in or does not sign in at all Status in ubuntuone-credentials package in Ubuntu: Confirmed Bug description: I looked up for updates this morning, but after finding an update for the Clock app, appeared the message: "Sign in to Ubuntu One to receive updates for apps." And below a button to sign in. I found it strange because I never seen this message when updating before, but the real problem is that even if I push the button and sign in, nothing changes and I can't update, same message there. I also added my Ubuntu One account to the account section of the System Settings panel, but again nothing changes, and when checking the account it had disappeared. Seems that it can't stay logged in to the Ubuntu One account or sign in at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntuone-credentials/+bug/1553150/+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 1619600] Re: [SRU] New stable release 1.8.3
Ok, reuploaded. And I forgot to do vaapi too, doing that now. ** Changed in: gstreamer-vaapi (Ubuntu Xenial) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1619600 Title: [SRU] New stable release 1.8.3 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Xenial: Fix Committed Status in gst-plugins-bad1.0 source package in Xenial: Fix Committed Status in gst-plugins-base1.0 source package in Xenial: Fix Committed Status in gst-plugins-good1.0 source package in Xenial: Fix Committed Status in gst-plugins-ugly1.0 source package in Xenial: Fix Committed Status in gstreamer-vaapi source package in Xenial: In Progress Status in gstreamer1.0 source package in Xenial: Fix Committed Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.8 series that 16.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] One of the fixes could be bad. Watch out for it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1619600/+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 1553150] Re: Ubuntu One account does not stay logged in or does not sign in at all
I was wrong, it solved it for just a few tries, then it was broken again -- 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/1553150 Title: Ubuntu One account does not stay logged in or does not sign in at all Status in ubuntuone-credentials package in Ubuntu: Confirmed Bug description: I looked up for updates this morning, but after finding an update for the Clock app, appeared the message: "Sign in to Ubuntu One to receive updates for apps." And below a button to sign in. I found it strange because I never seen this message when updating before, but the real problem is that even if I push the button and sign in, nothing changes and I can't update, same message there. I also added my Ubuntu One account to the account section of the System Settings panel, but again nothing changes, and when checking the account it had disappeared. Seems that it can't stay logged in to the Ubuntu One account or sign in at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntuone-credentials/+bug/1553150/+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 1643700] Re: mousetweaks process does not get killed when entering desktop
*** This bug is a duplicate of bug 1637758 *** https://bugs.launchpad.net/bugs/1637758 Thanks Sebastien for your input. You were probably right, as the unity- settings-daemon startted under lightdm was also running in the desktop session and version 1.20.0-0ubuntu3 that I just installed fixed the issue. ** This bug has been marked a duplicate of bug 1637758 lightdm greeter session not properly shut down at login -- 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/1643700 Title: mousetweaks process does not get killed when entering desktop Status in lightdm package in Ubuntu: New Bug description: This problem occurs on the current development version of zesty; it does not occur on any other Ubuntu version that is currently supported. Lightdm offers the possibility to start the default on-screen keyboard Onboard. Further, Onboard offers the possibility to start the hover click, which is provided by a process called mousetweaks. The hover click consists in having the system automatically perform a left click (and optionally other click types) shortly after the pointer stops moving. It is an accessibility feature for example for people that are not able to click with an hardware device, like mouse buttons. Here is how to start the hover click in lightdm: - Start the on-screen keyboard Onboard by using the accessibility menu at the top right. - Click on the key on the at the right of the Onboard layout that has a pointer as label; an additional column with keys will appear; these are the keys to control the hover click. - Click on the key at the bottom of the column that just appeared and that shows a pointer with a little clock. This is the key to start the hover click. In fact, it starts the mousetweaks process, that provides the hover click feature. The problem now is that the mousetweaks process started by Onboard in lightdm is still running after entering the desktop session. Here is the terminal output after entering the desktop session: $ ps -ef | grep mouse lightdm 1784 1 0 22:30 ?00:00:00 mousetweaks frafu 3584 3546 1 22:31 ?00:00:00 mousetweaks frafu 4324 3105 0 22:31 pts/500:00:00 grep mouse As you can see, the mousetweaks process started under lightdm is still running. The second mousetweaks process in the terminal output was started by settings in the desktop session. This behaviour is new in zesty; in previous Ubuntu versions there was no mousetweaks process left running under lightdm after entering the desktop session. As Onboard has not been responsible until now for killing the mousetweaks process it started under lightdm, I am filing this bug against lightdm. On the other hand, one could argue that since it is Onboard that starts mousetweaks under lightdm, it is also Onboard's job to kill it when exiting lightdm. This is what we from the Onboard development team are wondering now. @ lightdm developers or maintainers Please let us know, what you think about Onboard being responsible to kill mousetweaks when switching when entering the desktop session. I don't know how difficult it will be to implement it, as Onboard cannot simply stop the hover click when it gets killed. In fact, in the desktop session, the hover click can be started independently from Onboard in the Pointing and Clicking tab from the Universal Access control panel in the System Settings. I am also subscribing the other members of the Onboard development team to this bug thread. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1643700/+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 1595947] Re: brightness not changing from either u-s-s or hardkey on unity8-desktop
** Changed in: repowerd (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1595947 Title: brightness not changing from either u-s-s or hardkey on unity8-desktop Status in Canonical System Image: Confirmed Status in Mir: Invalid Status in unity8-desktop-session: Confirmed Status in mir package in Ubuntu: Invalid Status in repowerd package in Ubuntu: In Progress Status in unity-system-compositor package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: In Progress Status in unity8-desktop-session package in Ubuntu: Confirmed Bug description: Running unity8-desktop session on my macbookpro which has a hard display brightness key, currently it makes no effect. Also, opened ubuntu-sytstem-settings and changing the brightness slider also makes no effect. sorry for spamming projects, not sure which to log against. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1595947/+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 1643812] Re: There is no entry in 'Play sound through' list when plug in headset jack [8086:9d70].
I built the pulseaudio with the patch in below, it works fine after test. commit d5fec4ca7af9241d0c2ae17df40d0fb1c18c74a0 Author: Sjoerd SimonsDate: Sun Nov 16 23:15:50 2014 +0100 Alsa: Correct port availability with multiple jacks In case there are two independent jacks for one port (e.g. Dock Headphone Jack and Headphone Jack), the availability ends up being incorrect if the first one was _NO (not plugged) and the second gets _YES (plugged). Also pulse complains about the state being inconsistent which isn't true. Fix this by preferring more precise states (yes/no) over unknown and yes over others. However in case a plugged jack makes the port unavailable let that overrule everything else. -- 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/1643812 Title: There is no entry in 'Play sound through' list when plug in headset jack [8086:9d70]. Status in pulseaudio package in Ubuntu: New Bug description: 1. Install 14.04.5 image on P50s 2. Login system 3. $ sudo apt-get update 4. $ apt-get dist-upgrade sudo apt-get install --install-recommends linux-generic-lts-xenial xserver-xorg-core-lts-xenial xserver-xorg-lts-xenial xserver-xorg-video-all-lts-xenial xserver-xorg-input-all-lts-xenial libwayland-egl1-mesa-lts-xenial 5. Reboot the system 6. Login system 7. Open Sound setting window 8. Plug headset jack, unplug headset jack. The kernel is 4.4.0-47, and the pulseaudio is 1:4.0-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1643812/+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 1643812] [NEW] There is no entry in 'Play sound through' list when plug in headset jack [8086:9d70].
Public bug reported: 1. Install 14.04.5 image on P50s 2. Login system 3. $ sudo apt-get update 4. $ apt-get dist-upgrade sudo apt-get install --install-recommends linux-generic-lts-xenial xserver-xorg-core-lts-xenial xserver-xorg-lts-xenial xserver-xorg-video-all-lts-xenial xserver-xorg-input-all-lts-xenial libwayland-egl1-mesa-lts-xenial 5. Reboot the system 6. Login system 7. Open Sound setting window 8. Plug headset jack, unplug headset jack. The kernel is 4.4.0-47, and the pulseaudio is 1:4.0-0ubuntu1.1 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1643812 Title: There is no entry in 'Play sound through' list when plug in headset jack [8086:9d70]. Status in pulseaudio package in Ubuntu: New Bug description: 1. Install 14.04.5 image on P50s 2. Login system 3. $ sudo apt-get update 4. $ apt-get dist-upgrade sudo apt-get install --install-recommends linux-generic-lts-xenial xserver-xorg-core-lts-xenial xserver-xorg-lts-xenial xserver-xorg-video-all-lts-xenial xserver-xorg-input-all-lts-xenial libwayland-egl1-mesa-lts-xenial 5. Reboot the system 6. Login system 7. Open Sound setting window 8. Plug headset jack, unplug headset jack. The kernel is 4.4.0-47, and the pulseaudio is 1:4.0-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1643812/+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 1643333] Re: Ubuntu Touch web browser does not display Openstack Dashboard
I filed https://github.com/juju/juju-gui/issues/2231 to report the issue with jujucharms.com upstream. I don’t have credentials for trystack.org, so I’m unable to verify the issue. Would you mind reporting the issue upstream, similarly to what I did for jujucharms? In 95% of the cases, this turns out to be dumb UA string sniffing that disables functionality on the websites, instead of using proper APIs to detect browser capabilities. ** Bug watch added: github.com/juju/juju-gui/issues #2231 https://github.com/juju/juju-gui/issues/2231 ** Changed in: webbrowser-app (Ubuntu) Status: New => Incomplete -- 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/164 Title: Ubuntu Touch web browser does not display Openstack Dashboard Status in webbrowser-app package in Ubuntu: Incomplete Bug description: 1) Ubuntu Touch 15.04 (OTA-13) armhf Build 20160913-023544 2) Ubuntu Touch web Browser 3) Navigating without problems on OpenStack Dashboard and Juju Dashboard 4) Websites are displayed malformated Hi folks, while trying to navigate to an OpenStack Dashboard (Horizon), the web browser does not display the web site correctly. Also navigating to a Juju-Dashboard has the same effect. Examples: Horizon Dashboard https://x86.trystack.org/dashboard/auth/login/?next=/dashboard/ Juju: https://demo.jujucharms.com Its a little bit funny, that a Canonical product does not work with other Canonical products. Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/164/+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 1624251] Re: gsettings-qt fails test_reset() property count on Qt 5.7.1
Patch upstream at https://codereview.qt-project.org/#/c/177422 Let's see what they say ** Changed in: gsettings-qt (Ubuntu) Status: In Progress => Invalid ** Also affects: qtdeclarative-opensource-src (Ubuntu) Importance: Undecided Status: New ** Changed in: qtdeclarative-opensource-src (Ubuntu) Assignee: (unassigned) => Albert Astals Cid (aacid) ** Changed in: gsettings-qt (Ubuntu) Assignee: Albert Astals Cid (aacid) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-qt in Ubuntu. https://bugs.launchpad.net/bugs/1624251 Title: gsettings-qt fails test_reset() property count on Qt 5.7.1 Status in gsettings-qt package in Ubuntu: Invalid Status in qtdeclarative-opensource-src package in Ubuntu: New Bug description: -- FAIL! : GSettings::test_reset() property count Actual (): 0 Expected (): 1 Loc: [/«BUILDDIR»/gsettings-qt-0.1+16.04.20160329/tests/tst_GSettings.qml(102)] (process:7207): GLib-GIO-WARNING **: g_settings_set_value: value for key 'test-enum' in schema 'com.canonical.gsettings.Test' is outside of valid range -- (https://launchpadlibrarian.net/284597323/buildlog_ubuntu-yakkety- amd64.gsettings-qt_0.1+16.04.20160329-0ubuntu2~5_BUILDING.txt.gz) More information about Qt 5.7 at https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-qt/+bug/1624251/+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 1312673] Re: software-properties-gtk crashed with aptsources.distro.NoDistroTemplateException in get_sources(): Error: could not find a distribution template for Ubuntu/utopic
Just upgraded to Yakkety amd64, changed 3rd party sources to Yakkety, updated software and software-properties-gtk returns the error: Traceback (most recent call last): File "/usr/bin/software-properties-gtk", line 101, in app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, file=file) File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 101, in __init__ SoftwareProperties.__init__(self, options=options, datadir=datadir) File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 109, in __init__ self.reload_sourceslist() File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 599, in reload_sourceslist self.distro.get_sources(self.sourceslist) File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 89, in get_sources (self.id, self.codename)) aptsources.distro.NoDistroTemplateException: Error: could not find a distribution template for Ubuntu/zesty There is no Zesty in my sources but /etc/lsb-release is: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=17.04 DISTRIB_CODENAME=zesty DISTRIB_DESCRIPTION="Ubuntu Zesty Zapus (development branch)" So I edited it: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.10 DISTRIB_CODENAME=yakkety DISTRIB_DESCRIPTION="Ubuntu 16.10" And Software & Updates is working again. -- 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/1312673 Title: software-properties-gtk crashed with aptsources.distro.NoDistroTemplateException in get_sources(): Error: could not find a distribution template for Ubuntu/utopic Status in software-properties package in Ubuntu: Fix Released Bug description: lsb_release -rd Description:Ubuntu Utopic Unicorn (development branch) Release:14.10 apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.92.37 Candidate: 0.92.37 Version table: *** 0.92.37 0 500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 Packages 100 /var/lib/dpkg/status 0.92.36 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: software-properties-gtk 0.92.37 Uname: Linux 3.14.0-999-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 Date: Fri Apr 25 19:27:37 2014 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2012-09-30 (572 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.1) InterpreterPath: /usr/bin/python3.4 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk --open-tab 2 --toplevel 62914567 PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab', '2', '--toplevel', '62914567'] SourcePackage: software-properties Title: software-properties-gtk crashed with aptsources.distro.NoDistroTemplateException in get_sources(): Error: could not find a distribution template for Ubuntu/utopic UpgradeStatus: Upgraded to utopic on 2013-11-10 (165 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1312673/+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 1643276] Re: lightdm-gtk-greeter segv with unknown config options
** Changed in: lightdm Status: In Progress => Fix Released ** Changed in: lightdm Milestone: None => 1.21.1 -- 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/1643276 Title: lightdm-gtk-greeter segv with unknown config options Status in Light Display Manager: Fix Released Status in lightdm package in Ubuntu: In Progress Bug description: It seems that lightdm-gtk-greeter segfaults if you have an unknown option in your configuration file. Core was generated by `/usr/sbin/lightdm-gtk-greeter'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f0c4fd418a9 in config_load_from_file (config=0x100, path=0x23127d0 "/etc/lightdm/lightdm.conf", messages=0x0, error=0x7fff572556b0) at configuration.c:106 106 *messages = g_list_append (*messages, g_strdup_printf (" [%s] contains unknown option %s", group, keys[j])); [Current thread is 1 (Thread 0x7f0c51b189c0 (LWP 28281))] (gdb) p group $1 = (gchar *) 0x2265c10 "LightDM" (gdb) p keys[j] $2 = (gchar *) 0x21ecd00 "display-setup-script" (gdb) p messages $3 = (GList **) 0x0 (gdb) bt #0 0x7f0c4fd418a9 in config_load_from_file (config=0x100, path=0x23127d0 "/etc/lightdm/lightdm.conf", messages=0x0, error=0x7fff572556b0) at configuration.c:106 #1 0x7f0c4fd41fe6 in config_load_from_standard_locations (config=0x100, config_path=0x0, messages=0x0) at configuration.c:241 #2 0x7f0c4fd3f029 in update_sessions () at session.c:234 #3 0x7f0c4fd3f0f3 in lightdm_get_sessions () at session.c:269 #4 0x0040c972 in main () So it looks like a NULL message list arg is passed to config_load_from_file() while the function expects non-NULL. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1643276/+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 1642767] Re: starting any container with umask 007 breaks lxc-stop and prevents host system shutdown
** Description changed: If I run lxc-start with umask 007 (or any other value that masks the world-execute bit), my host system enters a state with the following problems: * lxc-stop hangs forever instead of stopping any container, even one that wasn't started with umask 007. * lxc-stop --kill --nolock hangs in the same way. * Attempts to reboot or shut down my host system fail, requiring a hard reset to recover. When lxc-stop hangs, messages like these appear in syslog every couple of minutes: Nov 17 01:22:11 hostbox kernel: [ 3360.091624] INFO: task systemd:12179 blocked for more than 120 seconds. Nov 17 01:22:11 hostbox kernel: [ 3360.091629] Tainted: P OE 4.4.0-47-generic #68-Ubuntu Nov 17 01:22:11 hostbox kernel: [ 3360.091631] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Nov 17 01:22:11 hostbox kernel: [ 3360.091633] systemd D 8800c6febb58 0 12179 12168 0x0104 Nov 17 01:22:11 hostbox kernel: [ 3360.091638] 8800c6febb58 8800d318d280 88040c649b80 8800d318d280 Nov 17 01:22:11 hostbox kernel: [ 3360.091641] 8800c6fec000 8800345bc088 8800345bc070 Nov 17 01:22:11 hostbox kernel: [ 3360.091644] fffe0001 8800c6febb70 81830f15 8800d318d280 Nov 17 01:22:11 hostbox kernel: [ 3360.091647] Call Trace: Nov 17 01:22:11 hostbox kernel: [ 3360.091653] [] schedule+0x35/0x80 Nov 17 01:22:11 hostbox kernel: [ 3360.091657] [] rwsem_down_write_failed+0x202/0x350 Nov 17 01:22:11 hostbox kernel: [ 3360.091662] [] ? kernfs_sop_show_options+0x40/0x40 Nov 17 01:22:11 hostbox kernel: [ 3360.091666] [] call_rwsem_down_write_failed+0x13/0x20 Nov 17 01:22:11 hostbox kernel: [ 3360.091669] [] ? down_write+0x2d/0x40 Nov 17 01:22:11 hostbox kernel: [ 3360.091672] [] grab_super+0x30/0xa0 Nov 17 01:22:11 hostbox kernel: [ 3360.091674] [] sget_userns+0x152/0x450 Nov 17 01:22:11 hostbox kernel: [ 3360.091677] [] ? kernfs_sop_show_path+0x50/0x50 Nov 17 01:22:11 hostbox kernel: [ 3360.091680] [] kernfs_mount_ns+0x7e/0x230 Nov 17 01:22:11 hostbox kernel: [ 3360.091685] [] cgroup_mount+0x2eb/0x7f0 Nov 17 01:22:11 hostbox kernel: [ 3360.091687] [] mount_fs+0x38/0x160 Nov 17 01:22:11 hostbox kernel: [ 3360.091691] [] vfs_kern_mount+0x67/0x110 Nov 17 01:22:11 hostbox kernel: [ 3360.091694] [] do_mount+0x269/0xde0 Nov 17 01:22:11 hostbox kernel: [ 3360.091698] [] SyS_mount+0x9f/0x100 Nov 17 01:22:11 hostbox kernel: [ 3360.091701] [] entry_SYSCALL_64_fastpath+0x16/0x71 When system shutdown hangs, similar messages appear on the console every couple of minutes. I'm running lxc 2.0.5-0ubuntu1~ubuntu16.04.2 on xubuntu 16.04.1 LTS amd64. My containers are all unprivileged. - I can reproduce this at will with either an old-ish container or a fresh - new one. + I can reproduce this at will with a freshly installed host OS in + VirtualBox, and with either an old-ish container or a new one. My umask at container creation time does not seem to matter. As far as I have seen, my umask only matters the first time I start a container in my login session. I can work around the bug by manually setting my umask to something more permissive before I start my first container of the day, and then setting it back again, but that's rather a hassle. (Even worse, it's very easy to forget this workaround and be left with containers that can't be stopped and a host system that won't shut down cleanly.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1642767 Title: starting any container with umask 007 breaks lxc-stop and prevents host system shutdown Status in lxc package in Ubuntu: New Bug description: If I run lxc-start with umask 007 (or any other value that masks the world-execute bit), my host system enters a state with the following problems: * lxc-stop hangs forever instead of stopping any container, even one that wasn't started with umask 007. * lxc-stop --kill --nolock hangs in the same way. * Attempts to reboot or shut down my host system fail, requiring a hard reset to recover. When lxc-stop hangs, messages like these appear in syslog every couple of minutes: Nov 17 01:22:11 hostbox kernel: [ 3360.091624] INFO: task systemd:12179 blocked for more than 120 seconds. Nov 17 01:22:11 hostbox kernel: [ 3360.091629] Tainted: P OE 4.4.0-47-generic #68-Ubuntu Nov 17 01:22:11 hostbox kernel: [ 3360.091631] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Nov 17 01:22:11 hostbox kernel: [ 3360.091633] systemd D 8800c6febb58 0 12179 12168 0x0104 Nov 17 01:22:11 hostbox kernel: [ 3360.091638] 8800c6febb58 8800d318d280 88040c649b80
[Touch-packages] [Bug 1641914] Re: Please backport two recent-manager patches
** Description changed: https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22=bf560369f2401e2cdd16f962f248e98c890835d0 https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22=a28022e9161415ef65ae3f21f0c4052f5db8558b Please apply/backport these two patches from the 3.22 branch. They fix a memory DOS, originally reported against mate-panel here: https://github.com/mate-desktop/mate-panel/issues/479 + + The GTK+2 version of this bug is bug 1641912 -- 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/1641914 Title: Please backport two recent-manager patches Status in GTK+: Unknown Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Yakkety: New Bug description: https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22=bf560369f2401e2cdd16f962f248e98c890835d0 https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22=a28022e9161415ef65ae3f21f0c4052f5db8558b Please apply/backport these two patches from the 3.22 branch. They fix a memory DOS, originally reported against mate-panel here: https://github.com/mate-desktop/mate-panel/issues/479 The GTK+2 version of this bug is bug 1641912 To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1641914/+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 1641912] Re: Please backport two recent-manager patches
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gtk+2.0 (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1641912 Title: Please backport two recent-manager patches Status in GTK+: Unknown Status in gtk+2.0 package in Ubuntu: Confirmed Status in gtk+2.0 source package in Xenial: Confirmed Status in gtk+2.0 source package in Yakkety: Confirmed Bug description: https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24=a3b2d6a65be9f592de9570c227df00f910167e9e https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24=35871edb318083b2d7e4758cbdaad6109eed60ca Please apply/backport these two patches from the 2.24 branch. They fix a memory DOS, originally reported against mate-panel here: https://github.com/mate-desktop/mate-panel/issues/479 For the GTK3 version of this bug, see bug 1641914 Note that MATE is GTK2 only for Ubuntu 16.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1641912/+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 1641912] Re: Please backport two recent-manager patches
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gtk+2.0 (Ubuntu Yakkety) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1641912 Title: Please backport two recent-manager patches Status in GTK+: Unknown Status in gtk+2.0 package in Ubuntu: Confirmed Status in gtk+2.0 source package in Xenial: Confirmed Status in gtk+2.0 source package in Yakkety: Confirmed Bug description: https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24=a3b2d6a65be9f592de9570c227df00f910167e9e https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24=35871edb318083b2d7e4758cbdaad6109eed60ca Please apply/backport these two patches from the 2.24 branch. They fix a memory DOS, originally reported against mate-panel here: https://github.com/mate-desktop/mate-panel/issues/479 For the GTK3 version of this bug, see bug 1641914 Note that MATE is GTK2 only for Ubuntu 16.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1641912/+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 1641912] Re: Please backport two recent-manager patches
** Tags added: xenial yakkety zesty ** Also affects: gtk+2.0 (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: gtk+2.0 (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1641912 Title: Please backport two recent-manager patches Status in GTK+: Unknown Status in gtk+2.0 package in Ubuntu: Confirmed Status in gtk+2.0 source package in Xenial: Confirmed Status in gtk+2.0 source package in Yakkety: Confirmed Bug description: https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24=a3b2d6a65be9f592de9570c227df00f910167e9e https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24=35871edb318083b2d7e4758cbdaad6109eed60ca Please apply/backport these two patches from the 2.24 branch. They fix a memory DOS, originally reported against mate-panel here: https://github.com/mate-desktop/mate-panel/issues/479 For the GTK3 version of this bug, see bug 1641914 Note that MATE is GTK2 only for Ubuntu 16.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1641912/+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 1641912] Re: Please backport two recent-manager patches
** Bug watch added: GNOME Bug Tracker #773587 https://bugzilla.gnome.org/show_bug.cgi?id=773587 ** Also affects: gtk via https://bugzilla.gnome.org/show_bug.cgi?id=773587 Importance: Unknown Status: Unknown ** Description changed: https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24=a3b2d6a65be9f592de9570c227df00f910167e9e https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24=35871edb318083b2d7e4758cbdaad6109eed60ca Please apply/backport these two patches from the 2.24 branch. They fix a memory DOS, originally reported against mate-panel here: https://github.com/mate-desktop/mate-panel/issues/479 + + For the GTK3 version of this bug, see bug 1641914 + Note that MATE is GTK2 only for Ubuntu 16.04 LTS. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1641912 Title: Please backport two recent-manager patches Status in GTK+: Unknown Status in gtk+2.0 package in Ubuntu: Confirmed Status in gtk+2.0 source package in Xenial: Confirmed Status in gtk+2.0 source package in Yakkety: Confirmed Bug description: https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24=a3b2d6a65be9f592de9570c227df00f910167e9e https://git.gnome.org/browse/gtk+/commit/?h=gtk-2-24=35871edb318083b2d7e4758cbdaad6109eed60ca Please apply/backport these two patches from the 2.24 branch. They fix a memory DOS, originally reported against mate-panel here: https://github.com/mate-desktop/mate-panel/issues/479 For the GTK3 version of this bug, see bug 1641914 Note that MATE is GTK2 only for Ubuntu 16.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1641912/+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 1642767] Re: starting any container with umask 007 breaks lxc-stop and prevents host system shutdown
** Description changed: If I run lxc-start with umask 007 (or any other value that masks the world-execute bit), my host system enters a state with the following problems: * lxc-stop hangs forever instead of stopping any container, even one that wasn't started with umask 007. * lxc-stop --kill --nolock hangs in the same way. * Attempts to reboot or shut down my host system fail, requiring a hard reset to recover. When lxc-stop hangs, messages like these appear in syslog every couple of minutes: Nov 17 01:22:11 hostbox kernel: [ 3360.091624] INFO: task systemd:12179 blocked for more than 120 seconds. Nov 17 01:22:11 hostbox kernel: [ 3360.091629] Tainted: P OE 4.4.0-47-generic #68-Ubuntu Nov 17 01:22:11 hostbox kernel: [ 3360.091631] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Nov 17 01:22:11 hostbox kernel: [ 3360.091633] systemd D 8800c6febb58 0 12179 12168 0x0104 Nov 17 01:22:11 hostbox kernel: [ 3360.091638] 8800c6febb58 8800d318d280 88040c649b80 8800d318d280 Nov 17 01:22:11 hostbox kernel: [ 3360.091641] 8800c6fec000 8800345bc088 8800345bc070 Nov 17 01:22:11 hostbox kernel: [ 3360.091644] fffe0001 8800c6febb70 81830f15 8800d318d280 Nov 17 01:22:11 hostbox kernel: [ 3360.091647] Call Trace: Nov 17 01:22:11 hostbox kernel: [ 3360.091653] [] schedule+0x35/0x80 Nov 17 01:22:11 hostbox kernel: [ 3360.091657] [] rwsem_down_write_failed+0x202/0x350 Nov 17 01:22:11 hostbox kernel: [ 3360.091662] [] ? kernfs_sop_show_options+0x40/0x40 Nov 17 01:22:11 hostbox kernel: [ 3360.091666] [] call_rwsem_down_write_failed+0x13/0x20 Nov 17 01:22:11 hostbox kernel: [ 3360.091669] [] ? down_write+0x2d/0x40 Nov 17 01:22:11 hostbox kernel: [ 3360.091672] [] grab_super+0x30/0xa0 Nov 17 01:22:11 hostbox kernel: [ 3360.091674] [] sget_userns+0x152/0x450 Nov 17 01:22:11 hostbox kernel: [ 3360.091677] [] ? kernfs_sop_show_path+0x50/0x50 Nov 17 01:22:11 hostbox kernel: [ 3360.091680] [] kernfs_mount_ns+0x7e/0x230 Nov 17 01:22:11 hostbox kernel: [ 3360.091685] [] cgroup_mount+0x2eb/0x7f0 Nov 17 01:22:11 hostbox kernel: [ 3360.091687] [] mount_fs+0x38/0x160 Nov 17 01:22:11 hostbox kernel: [ 3360.091691] [] vfs_kern_mount+0x67/0x110 Nov 17 01:22:11 hostbox kernel: [ 3360.091694] [] do_mount+0x269/0xde0 Nov 17 01:22:11 hostbox kernel: [ 3360.091698] [] SyS_mount+0x9f/0x100 Nov 17 01:22:11 hostbox kernel: [ 3360.091701] [] entry_SYSCALL_64_fastpath+0x16/0x71 When system shutdown hangs, similar messages appear on the console every couple of minutes. + I can reproduce this at will with a freshly-installed and fully-updated + host OS in VirtualBox, and with either an old-ish container or a new + one. + I'm running lxc 2.0.5-0ubuntu1~ubuntu16.04.2 on xubuntu 16.04.1 LTS amd64. My containers are all unprivileged. - - I can reproduce this at will with a freshly installed host OS in - VirtualBox, and with either an old-ish container or a new one. My umask at container creation time does not seem to matter. As far as I have seen, my umask only matters the first time I start a container in my login session. I can work around the bug by manually setting my umask to something more permissive before I start my first container of the day, and then setting it back again, but that's rather a hassle. (Even worse, it's very easy to forget this workaround and be left with containers that can't be stopped and a host system that won't shut down cleanly.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1642767 Title: starting any container with umask 007 breaks lxc-stop and prevents host system shutdown Status in lxc package in Ubuntu: New Bug description: If I have umask 007 (or any other value that masks the world-execute bit) when I run lxc-start for the first time after logging in, my host system enters a state with the following problems: * lxc-stop hangs forever instead of stopping any container, even one that wasn't started with umask 007. * lxc-stop --kill --nolock hangs in the same way. * Attempts to reboot or shut down the host system fail, requiring a hard reset to recover. When lxc-stop hangs, messages like these appear in syslog every couple of minutes: Nov 17 01:22:11 hostbox kernel: [ 3360.091624] INFO: task systemd:12179 blocked for more than 120 seconds. Nov 17 01:22:11 hostbox kernel: [ 3360.091629] Tainted: P OE 4.4.0-47-generic #68-Ubuntu Nov 17 01:22:11 hostbox kernel: [ 3360.091631] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Nov 17 01:22:11 hostbox kernel: [ 3360.091633] systemd D 8800c6febb58 0 12179 12168 0x0104
[Touch-packages] [Bug 1642767] Re: starting any container with umask 007 breaks lxc-stop and prevents host system shutdown
** Description changed: - If I run lxc-start with umask 007 (or any other value that masks the - world-execute bit), my host system enters a state with the following - problems: + If I have umask 007 (or any other value that masks the world-execute + bit) when I run lxc-start for the first time after logging in, my host + system enters a state with the following problems: * lxc-stop hangs forever instead of stopping any container, even one that wasn't started with umask 007. * lxc-stop --kill --nolock hangs in the same way. - * Attempts to reboot or shut down my host system fail, requiring a hard reset to recover. + * Attempts to reboot or shut down the host system fail, requiring a hard reset to recover. When lxc-stop hangs, messages like these appear in syslog every couple of minutes: Nov 17 01:22:11 hostbox kernel: [ 3360.091624] INFO: task systemd:12179 blocked for more than 120 seconds. Nov 17 01:22:11 hostbox kernel: [ 3360.091629] Tainted: P OE 4.4.0-47-generic #68-Ubuntu Nov 17 01:22:11 hostbox kernel: [ 3360.091631] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Nov 17 01:22:11 hostbox kernel: [ 3360.091633] systemd D 8800c6febb58 0 12179 12168 0x0104 Nov 17 01:22:11 hostbox kernel: [ 3360.091638] 8800c6febb58 8800d318d280 88040c649b80 8800d318d280 Nov 17 01:22:11 hostbox kernel: [ 3360.091641] 8800c6fec000 8800345bc088 8800345bc070 Nov 17 01:22:11 hostbox kernel: [ 3360.091644] fffe0001 8800c6febb70 81830f15 8800d318d280 Nov 17 01:22:11 hostbox kernel: [ 3360.091647] Call Trace: Nov 17 01:22:11 hostbox kernel: [ 3360.091653] [] schedule+0x35/0x80 Nov 17 01:22:11 hostbox kernel: [ 3360.091657] [] rwsem_down_write_failed+0x202/0x350 Nov 17 01:22:11 hostbox kernel: [ 3360.091662] [] ? kernfs_sop_show_options+0x40/0x40 Nov 17 01:22:11 hostbox kernel: [ 3360.091666] [] call_rwsem_down_write_failed+0x13/0x20 Nov 17 01:22:11 hostbox kernel: [ 3360.091669] [] ? down_write+0x2d/0x40 Nov 17 01:22:11 hostbox kernel: [ 3360.091672] [] grab_super+0x30/0xa0 Nov 17 01:22:11 hostbox kernel: [ 3360.091674] [] sget_userns+0x152/0x450 Nov 17 01:22:11 hostbox kernel: [ 3360.091677] [] ? kernfs_sop_show_path+0x50/0x50 Nov 17 01:22:11 hostbox kernel: [ 3360.091680] [] kernfs_mount_ns+0x7e/0x230 Nov 17 01:22:11 hostbox kernel: [ 3360.091685] [] cgroup_mount+0x2eb/0x7f0 Nov 17 01:22:11 hostbox kernel: [ 3360.091687] [] mount_fs+0x38/0x160 Nov 17 01:22:11 hostbox kernel: [ 3360.091691] [] vfs_kern_mount+0x67/0x110 Nov 17 01:22:11 hostbox kernel: [ 3360.091694] [] do_mount+0x269/0xde0 Nov 17 01:22:11 hostbox kernel: [ 3360.091698] [] SyS_mount+0x9f/0x100 Nov 17 01:22:11 hostbox kernel: [ 3360.091701] [] entry_SYSCALL_64_fastpath+0x16/0x71 When system shutdown hangs, similar messages appear on the console every couple of minutes. I can reproduce this at will with a freshly-installed and fully-updated host OS in VirtualBox, and with either an old-ish container or a new one. I'm running lxc 2.0.5-0ubuntu1~ubuntu16.04.2 on xubuntu 16.04.1 LTS amd64. My containers are all unprivileged. My umask at container creation time does not seem to matter. As far as I have seen, my umask only matters the first time I start a container in my login session. I can work around the bug by manually setting my umask to something more permissive before I start my first container of the day, and then setting it back again, but that's rather a hassle. (Even worse, it's very easy to forget this workaround and be left with containers that can't be stopped and a host system that won't shut down cleanly.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1642767 Title: starting any container with umask 007 breaks lxc-stop and prevents host system shutdown Status in lxc package in Ubuntu: New Bug description: If I have umask 007 (or any other value that masks the world-execute bit) when I run lxc-start for the first time after logging in, my host system enters a state with the following problems: * lxc-stop hangs forever instead of stopping any container, even one that wasn't started with umask 007. * lxc-stop --kill --nolock hangs in the same way. * Attempts to reboot or shut down the host system fail, requiring a hard reset to recover. When lxc-stop hangs, messages like these appear in syslog every couple of minutes: Nov 17 01:22:11 hostbox kernel: [ 3360.091624] INFO: task systemd:12179 blocked for more than 120 seconds. Nov 17 01:22:11 hostbox kernel: [ 3360.091629] Tainted: P OE 4.4.0-47-generic #68-Ubuntu Nov 17 01:22:11 hostbox kernel: [ 3360.091631] "echo 0 >
[Touch-packages] [Bug 1641914] Re: Please backport two recent-manager patches
Those commits were included in 3.22.4, so I'm marking this fixed for zesty: https://launchpad.net/ubuntu/+source/gtk+3.0/3.22.4-1ubuntu1 ** Tags added: yakkety zesty ** Also affects: gtk+3.0 (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: gtk+3.0 (Ubuntu) Status: Confirmed => Fix Released ** Bug watch added: GNOME Bug Tracker #773587 https://bugzilla.gnome.org/show_bug.cgi?id=773587 ** Also affects: gtk via https://bugzilla.gnome.org/show_bug.cgi?id=773587 Importance: Unknown Status: Unknown -- 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/1641914 Title: Please backport two recent-manager patches Status in GTK+: Unknown Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Yakkety: New Bug description: https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22=bf560369f2401e2cdd16f962f248e98c890835d0 https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22=a28022e9161415ef65ae3f21f0c4052f5db8558b Please apply/backport these two patches from the 3.22 branch. They fix a memory DOS, originally reported against mate-panel here: https://github.com/mate-desktop/mate-panel/issues/479 The GTK+2 version of this bug is bug 1641912 To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1641914/+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 1642767] Re: starting any container with umask 007 breaks lxc-stop and prevents host system shutdown
This sounds like a kernel bug to me. Can you please provide the output of: uname -a and try to reproduce this on a newer kernel version and report back? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1642767 Title: starting any container with umask 007 breaks lxc-stop and prevents host system shutdown Status in lxc package in Ubuntu: New Bug description: If I have umask 007 (or any other value that masks the world-execute bit) when I run lxc-start for the first time after logging in, my host system enters a state with the following problems: * lxc-stop hangs forever instead of stopping any container, even one that wasn't started with umask 007. * lxc-stop --kill --nolock hangs in the same way. * Attempts to reboot or shut down the host system fail, requiring a hard reset to recover. When lxc-stop hangs, messages like these appear in syslog every couple of minutes: Nov 17 01:22:11 hostbox kernel: [ 3360.091624] INFO: task systemd:12179 blocked for more than 120 seconds. Nov 17 01:22:11 hostbox kernel: [ 3360.091629] Tainted: P OE 4.4.0-47-generic #68-Ubuntu Nov 17 01:22:11 hostbox kernel: [ 3360.091631] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Nov 17 01:22:11 hostbox kernel: [ 3360.091633] systemd D 8800c6febb58 0 12179 12168 0x0104 Nov 17 01:22:11 hostbox kernel: [ 3360.091638] 8800c6febb58 8800d318d280 88040c649b80 8800d318d280 Nov 17 01:22:11 hostbox kernel: [ 3360.091641] 8800c6fec000 8800345bc088 8800345bc070 Nov 17 01:22:11 hostbox kernel: [ 3360.091644] fffe0001 8800c6febb70 81830f15 8800d318d280 Nov 17 01:22:11 hostbox kernel: [ 3360.091647] Call Trace: Nov 17 01:22:11 hostbox kernel: [ 3360.091653] [] schedule+0x35/0x80 Nov 17 01:22:11 hostbox kernel: [ 3360.091657] [] rwsem_down_write_failed+0x202/0x350 Nov 17 01:22:11 hostbox kernel: [ 3360.091662] [] ? kernfs_sop_show_options+0x40/0x40 Nov 17 01:22:11 hostbox kernel: [ 3360.091666] [] call_rwsem_down_write_failed+0x13/0x20 Nov 17 01:22:11 hostbox kernel: [ 3360.091669] [] ? down_write+0x2d/0x40 Nov 17 01:22:11 hostbox kernel: [ 3360.091672] [] grab_super+0x30/0xa0 Nov 17 01:22:11 hostbox kernel: [ 3360.091674] [] sget_userns+0x152/0x450 Nov 17 01:22:11 hostbox kernel: [ 3360.091677] [] ? kernfs_sop_show_path+0x50/0x50 Nov 17 01:22:11 hostbox kernel: [ 3360.091680] [] kernfs_mount_ns+0x7e/0x230 Nov 17 01:22:11 hostbox kernel: [ 3360.091685] [] cgroup_mount+0x2eb/0x7f0 Nov 17 01:22:11 hostbox kernel: [ 3360.091687] [] mount_fs+0x38/0x160 Nov 17 01:22:11 hostbox kernel: [ 3360.091691] [] vfs_kern_mount+0x67/0x110 Nov 17 01:22:11 hostbox kernel: [ 3360.091694] [] do_mount+0x269/0xde0 Nov 17 01:22:11 hostbox kernel: [ 3360.091698] [] SyS_mount+0x9f/0x100 Nov 17 01:22:11 hostbox kernel: [ 3360.091701] [] entry_SYSCALL_64_fastpath+0x16/0x71 When system shutdown hangs, similar messages appear on the console every couple of minutes. I can reproduce this at will with a freshly-installed and fully- updated host OS in VirtualBox, and with either an old-ish container or a new one. I'm running lxc 2.0.5-0ubuntu1~ubuntu16.04.2 on xubuntu 16.04.1 LTS amd64. My containers are all unprivileged. My umask at container creation time does not seem to matter. As far as I have seen, my umask only matters the first time I start a container in my login session. I can work around the bug by manually setting my umask to something more permissive before I start my first container of the day, and then setting it back again, but that's rather a hassle. (Even worse, it's very easy to forget this workaround and be left with containers that can't be stopped and a host system that won't shut down cleanly.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1642767/+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 1638338] Re: Can not ssh with tr_TR.UTF-8 locales (Bad configuration options)
This is an upstream regression very probably caused by: https://anongit.mindrot.org/openssh.git/commit/?id=65c6c6b567ab5ab12945a5ad8e0ab3a8c26119cc I'd suggest filing it upstream at https://bugzilla.mindrot.org/ - it may be possible to preserve the intent of the above change by substituting a deliberately-locale-unaware version of tolower() when parsing configuration files, or maybe just by calling setlocale() after parsing configuration files. status triaged ** Changed in: openssh (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1638338 Title: Can not ssh with tr_TR.UTF-8 locales (Bad configuration options) Status in openssh package in Ubuntu: Triaged Bug description: I can not ssh to any host with Turkish locales. What I expected to happen: I expected that 'ssh some_host' command would successfully run. What actually happened 'ssh some_host' command failed with an error. Steps to produce: 1. Open a terminal 2. Run LANG=tr_TR.UTF-8 ssh some_host If I run ssh with tr_TR.UTF-8 locale, the first error I get is: $HOME/.ssh/config: line 7: Bad configuration option: Identityfile $HOME/.ssh/config: terminating, 1 bad configuration options If I commend IdentityFile option from $HOME/.ssh/config file and re- run the command, I get this: debug1: Reading configuration data ~/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * /etc/ssh/ssh_config: line 55: Bad configuration option: gssapIauthentication /etc/ssh/ssh_config: line 56: Bad configuration option: gssapIdelegatecredentials /etc/ssh/ssh_config: terminating, 2 bad configuration options If I commend GSSAPIAuthentication and GSSAPIDelegateCredentials option, I can ssh to a host. So to ssh to a host with tr_TR.UTF-8 locale, one must commend out IdentityFile, if it is used, GSSAPIAuthentication and GSSAPIDelegateCredentials optons. Workaround: LC_ALL=C ssh some_host LC_ALL=C apt-cache policy openssh-client openssh-client: Installed: 1:7.3p1-1 Candidate: 1:7.3p1-1 Version table: *** 1:7.3p1-1 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status LC_ALL=C lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.10 Release: 16.10 Codename: yakkety ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: openssh-client 1:7.3p1-1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 1 19:37:35 2016 InstallationDate: Installed on 2016-10-23 (9 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_7.3p1 Ubuntu-1, OpenSSL 1.0.2g 1 Mar 2016 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1638338/+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 1576341] Re: fails in lxd container
Any progress with regards to this bug? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1576341 Title: fails in lxd container Status in lvm2 package in Ubuntu: Confirmed Status in lxd package in Ubuntu: Invalid Status in open-iscsi package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: The ubuntu:xenial image shows 'degraded' state in lxd on initial boot. $ lxc launch xenial x1 $ sleep 10 $ lxc file pull x1/etc/cloud/build.info - build_name: server serial: 20160420-145324 $ lxc exc x1 systemctl is-system-running degraded $ lxc exec x1 systemctl --state=failed UNIT LOAD ACTIVE SUBDESCRIPTION ● dev-hugepages.mount loaded failed failed Huge Pages File System ● iscsid.serviceloaded failed failed iSCSI initiator daemon (iscsid) ● open-iscsi.serviceloaded failed failed Login to default iSCSI targets ● systemd-remount-fs.serviceloaded failed failed Remount Root and Kernel File Systems ● systemd-sysctl.serviceloaded failed failed Apply Kernel Variables ● lvm2-lvmetad.socket loaded failed failed LVM2 metadata daemon socket ● systemd-journald-audit.socket loaded failed failed Journal Audit Socket LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB= The low-level unit activation state, values depend on unit type. 7 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: open-iscsi 2.0.873+git0.3b4b4500-14ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Thu Apr 28 17:28:04 2016 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) SourcePackage: open-iscsi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+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 1644007] [NEW] Intel HD Graphics 5500 Drivers Cap Resolution at 1366x768 and don't support video out for external displays
Public bug reported: Dell latitude e7450, Ubuntu 14.04 LTS. Swapped disk from latitude e7450 with faulty HDMI port as a quick fix while it gets repaired/replaced under warranty. "Pleasantly" surprised to find the screen resolution capped abysmally low and neither video out port working. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-101.148-generic 3.13.11-ckt39 Uname: Linux 3.13.0-101-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Tue Nov 22 15:34:21 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: vboxhost, 5.0.28, 3.13.0-101-generic, x86_64: installed vboxhost, 5.0.28, 3.13.0-91-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:062e] InstallationDate: Installed on 2015-05-01 (571 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Latitude E7450 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-101-generic root=UUID=97bccafc-0510-496c-99b5-0e03b4d0399b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/12/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 06HN6G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd01/12/2016:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn06HN6G:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7450 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Nov 22 15:09:58 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5264 vendor CMN xserver.version: 2:1.15.1-0ubuntu2.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1644007 Title: Intel HD Graphics 5500 Drivers Cap Resolution at 1366x768 and don't support video out for external displays Status in xorg package in Ubuntu: New Bug description: Dell latitude e7450, Ubuntu 14.04 LTS. Swapped disk from latitude e7450 with faulty HDMI port as a quick fix while it gets repaired/replaced under warranty. "Pleasantly" surprised to find the screen resolution capped abysmally low and neither video out port working. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-101.148-generic 3.13.11-ckt39 Uname: Linux 3.13.0-101-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Tue Nov 22 15:34:21 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: vboxhost, 5.0.28, 3.13.0-101-generic, x86_64: installed vboxhost, 5.0.28, 3.13.0-91-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:062e] InstallationDate: Installed on 2015-05-01 (571 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Latitude E7450 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-101-generic root=UUID=97bccafc-0510-496c-99b5-0e03b4d0399b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/12/2016
[Touch-packages] [Bug 1643843] Re: Distorted colours after suspend / resume cycle
Hmm - so I'm not sure what's going on here. I started bisecting v4.1 .. v4.2.8 and I couldn't find a working version in 6-7 bisects and when I checked rest of the commit set in the bisect, it couldn't find any commits to drivers/gpu?! So I decided to test Ubuntu mainline kernels a little bit more and the current status is: Broken: linux-image-4.1.3-040103-generic_4.1.3-040103.201507220129_amd64.deb Working: linux-image-4.1.4-040104-generic_4.1.4-040104.201508031330_amd64.deb So probably something was fixed and in a short time broken again during the v4.2 development cycle?! And probably I should check with other connectors too, as I currently run the monitor via DVI => VGA connector. -- 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/1643843 Title: Distorted colours after suspend / resume cycle Status in xorg package in Ubuntu: New Bug description: When waking up the system from a suspend-resume cycle, the display most times shows distorted colours. As a workaround one can switch to the linux console (VT) and back to fix the display. Alternatively triggering DPMS also fixes the problem (xset dpms force off ; sleep 0.1; xset dpms force on) Hardware: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] PCIID: 1002:6779 I've tested Ubuntu Xenial (16.04) with the latest updates: mesa 11.2.0-1ubuntu2.2 xserver-xorg-video-radeon 1:7.7.0-1 linux-image-4.4.0-47-generic 4.4.0-47.68 xserver-xorg-core 2:1.18.3-1ubuntu2.3 I've tried older kernels, xorg, linux-firmware, as a colleague claimed it started for him after some of the latest Ubuntu updates, but couldn't find a working configuration. I also checked Ubuntu Yakkety (16.10), where I couldn't reproduce with XFCE, but instantly with the Unity session, but probably XFCE was just lucky, as sometimes I also had series of working (~5) cycles. Current versions: mesa 12.0.3-1ubuntu2 xserver-xorg-video-radeon 1:7.7.1-1 linux-image-4.8.0-27-generic 4.8.0-27.29 xserver-xorg-core 2:1.18.4-1ubuntu6.1 I'm also going to test Trusty (14.04) to check if it's really a regression. At least I have never seen this problem while running it. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 22 12:21:24 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Radeon HD 6450 [1642:3a75] Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 4524BL8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic root=UUID=4dda3a4b-6e9c-49ba-a969-5d2146f02b60 ro splash quiet vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 9HKT54AUS dmi.board.vendor: LENOVO 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:bvnLENOVO:bvr9HKT54AUS:bd10/16/2012:svnLENOVO:pn4524BL8:pvrThinkCentreM91p:rvnLENOVO:rn:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: 4524BL8 dmi.product.version: ThinkCentre M91p dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1
[Touch-packages] [Bug 1643997] [NEW] nvidia driver causes blank screen
Public bug reported: I just installed ubuntu 16.04.1 64 bit (complete vanilla) 1. apt-get upgrade 2. apt-get dist-upgrade 3. install nvidia proprietary driver from "System settings -> Software & updates -> Additional Drivers" (current driver is 367.57- marked "proprietary, tested"). 4. reboot 5. blank screen as described above. I've modified grub with "nomodeset" - did not work. Removed "quiet, splash" - did not work add "set gfxpayload=text" - got some output to the screen, but not can't tell what it does and I have no idea where the data is stored - and then blank screen. disabled vesa frame buffer (vesafb.nonsense=1) - did not work My graphic HW: GTX 960 For now, I purged nvidia driver and the system is running well. I am sure the card is working properly because up until 3 days ago it had ubuntu 14.04 installed on it with nvidia driver active. Then there was an update which caused the same blank screen on 14.04. I decided to install 16.04 fresh (over the 14.04). I hoped the blank screen issue will disappear with 16.04, but it turns out it doesn't. If you need me to run some tests, I'll be more then happy to do so. I installed openssh-server on my machine, so I think I might be able to ssh into it from another machine while its in blank screen (did not test this). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 22 21:51:15 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-47-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2016-11-22 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-47-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 04/25/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1302 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7H55-M 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.:bvr1302:bd04/25/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7H55-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 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.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Nov 22 21:30:50 2016 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.2 xserver.video_driver: nouveau ** 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/1643997 Title: nvidia driver causes blank screen Status in xorg package in Ubuntu: New Bug description: I just installed ubuntu 16.04.1 64 bit (complete vanilla) 1. apt-get upgrade 2. apt-get dist-upgrade 3. install nvidia proprietary driver from "System settings -> Software & updates -> Additional Drivers" (current driver is 367.57- marked "proprietary, tested"). 4. reboot 5. blank screen as described above. I've
[Touch-packages] [Bug 1450009] Re: [HP, Dell notebooks] suspends on closed lid, does not recognized external monitors/dock
Similar issues on my Dell M4800. Even worse for me is a serious security issue: sometimes, when laptop suspends at login screen and I hit power button on docking station to wake up from suspend, I see my Desktop without ever having to enter a username and password. This is obviously a serious problem. for d in /dev/input/event*; do if ! sudo evtest --query $d EV_SW SW_DOCK; then echo $d; fi; done returns nothing. Journal.txt and monitors.txt attached ** Attachment added: "monitors.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450009/+attachment/4781644/+files/monitors.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1450009 Title: [HP, Dell notebooks] suspends on closed lid, does not recognized external monitors/dock Status in systemd package in Ubuntu: Fix Released Bug description: Using systemd as init system on a HP zbook15 notebook having 2 external monitors connected using a docking station and starting with lid closed the system goes to sleep after successfully booting and starting lightdm greeter. Sometimes there's enough time to enter username and password but system goes to sleep every time after a few seconds. The system can be woken up and used after this happens but it will not let me shutdown later. The problem is just present in docked situation starting with closed lid using systemd a init system. If notebook is used in non-docked situation with open lid and systemd the problem does not occur. Workaround: A switch back to upstart as init system resolves the issue. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd-sysv 219-7ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Wed Apr 29 14:46:09 2015 InstallationDate: Installed on 2015-04-27 (1 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450009/+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 1598300] Re: CUPS web interface stops responding after a while
fix is on the way. Till now it has not been solved. I am running last 2.1.3-4ubuntu0.1 cups. I will soon known if it fix the problem. thanks. -- 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/1598300 Title: CUPS web interface stops responding after a while Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: Fix Committed Bug description: after 6 minutes or so, cups is not responding. it do not produce error on the log, just stop working, worse, it exit with 0 ⌌—⌍ |root@cupsmachine :~# systemctl status cups | |● cups.service - CUPS Scheduler | | Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled)| | Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago | | Docs: man:cupsd(8) | | Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, status=0/SUCCESS)| | Main PID: 28686 (code=exited, status=0/SUCCESS) | | | |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler. | ⌎—⌏ I got to launch it again, so I have finish with a cron job like */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && systemctl start cups but it is a dirty solution. I have no idea of what make it stop. NB: I have seen problems related to apparmor, this machine has no apparmor package. [Impact] If you want to use the CUPS web interface in Xenial and therefore set "WebInterface Yes" in /etc/cups/cupsd.conf, CUPS could auto-shutdown when it is idle and then an attempt to access http://localhost:631/ via a web browser fails. People get confused as other access to CUPS [Testcase] Take a CUPS setup on Xenial with no shared print queues and CUPS only listening on the domain socket. Activate the web interface via cupsctl WebInterface=Yes Now you are able to access the web interface via http://localhost:631/. Wait for some minutes without accessing CUPS until the CUPS daemon shuts down automatically. Try to open the web interface again and it will not work. With the fixed CUPS package CUPS will not auto-shutdown when the web interface is activated. [Regression Potential] Low, as we are removing a simple distro patch to get back to the original, upstream behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1598300/+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 1643870] Re: Pulseaudio fails to detect card after recent update
OK, I've just started seeing this on my Toshiba W50X laptop, with Ubuntu 14.04 on it. It now shows no selectable outputs in the Sound Preferences window. I also have a desktop with an ASRock Z77 motherboard and Ubuntu 16.04 seeing the same thing! What other info should I be gathering? It doesn't seem to be kernel related, I tried installing an older kernel on the affected desktop and it didn't help at all. -- 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/1643870 Title: Pulseaudio fails to detect card after recent update Status in pulseaudio package in Ubuntu: Confirmed Bug description: For months, audio has been working fine on this Dell XPS13 laptop. It is a fresh install of 16.04, from around the time it was released. There were some pulseaudio updates installed on my machine today (see the attached apt term.log output). Since then, audio output has been unreliable. I've discussed this a small amount on AskUbuntu http://askubuntu.com/a/852277/237387 I found that running this command to reinstall the updated packages would sometimes bring back audio output - sometimes for a while, but sometimes only for a few seconds after a reboot. sudo apt install --reinstall pulseaudio pulseaudio-utils pulseaudio-module-bluetooth pulseaudio-module-x11 libpulse-mainloop- glib0 libpulse0 libpulsedsp I can see Launchpad has several almost identical sounding bugs, from many years ago. #461258, #926840, #926840, #995961, #1132982. None of those were ever resolved. I hope this does not end the same way. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Tue Nov 22 23:13:26 2016 InstallationDate: Installed on 2016-05-17 (189 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [Dell System XPS L322X, Realtek ALC3260, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0WW7PG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0WW7PG:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1643870/+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 1595947] Re: brightness not changing from either u-s-s or hardkey on unity8-desktop
** Changed in: canonical-devices-system-image Milestone: None => p1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1595947 Title: brightness not changing from either u-s-s or hardkey on unity8-desktop Status in Canonical System Image: Confirmed Status in Mir: Invalid Status in unity8-desktop-session: Confirmed Status in mir package in Ubuntu: Invalid Status in repowerd package in Ubuntu: In Progress Status in unity-system-compositor package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: In Progress Status in unity8-desktop-session package in Ubuntu: Confirmed Bug description: Running unity8-desktop session on my macbookpro which has a hard display brightness key, currently it makes no effect. Also, opened ubuntu-sytstem-settings and changing the brightness slider also makes no effect. sorry for spamming projects, not sure which to log against. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1595947/+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 1450009] Re: [HP, Dell notebooks] suspends on closed lid, does not recognized external monitors/dock
** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450009/+attachment/4781645/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1450009 Title: [HP, Dell notebooks] suspends on closed lid, does not recognized external monitors/dock Status in systemd package in Ubuntu: Fix Released Bug description: Using systemd as init system on a HP zbook15 notebook having 2 external monitors connected using a docking station and starting with lid closed the system goes to sleep after successfully booting and starting lightdm greeter. Sometimes there's enough time to enter username and password but system goes to sleep every time after a few seconds. The system can be woken up and used after this happens but it will not let me shutdown later. The problem is just present in docked situation starting with closed lid using systemd a init system. If notebook is used in non-docked situation with open lid and systemd the problem does not occur. Workaround: A switch back to upstart as init system resolves the issue. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd-sysv 219-7ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Wed Apr 29 14:46:09 2015 InstallationDate: Installed on 2015-04-27 (1 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450009/+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 1643838] Re: ureadahead trying to read entire filesystem
cloud-init's only interaction with ureadahead is in its postinst [1] where it disables ureadahead per bug 499520. curtin has no interaction with ureadahead. ureadahead gets invoked via dpkg triggers. I'm not exactly sure what it triggers off of. likely one of the packages installed or updated triggered that. -- [1] https://git.launchpad.net/cloud-init/tree/debian/cloud-init.postinst?h=ubuntu/devel ** No longer affects: cloud-init (Ubuntu) ** No longer affects: curtin -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1643838 Title: ureadahead trying to read entire filesystem Status in MAAS: Invalid Status in ureadahead package in Ubuntu: New Bug description: MAAS Version 2.1.1+bzr5544-0ubuntu1 (16.04.1), deploying Ubuntu 16.04.1 As shown in bug 1635560 and specifically in https://pastebin.canonical.com/171385/ during deployment, ureadahead (sometimes?) tries to index the whole filesystem, complaining about all of the relative paths. These are the log messages immediately before the spamminess: Nov 22 08:32:32 faraday systemd[1]: Starting Stop ureadahead data collection... Nov 22 08:32:32 faraday systemd[1]: Stopping Read required files in advance... Nov 22 08:32:32 faraday systemd[1]: Started Stop ureadahead data collection. The ureadahead lines are responsible for the vast majority of the installation log ⟫ cat faraday-installation-log | wc -l 78777 ⟫ grep ureadahead faraday-installation-log | wc -l 76799 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1643838/+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 1633227] Re: After update to 16.10 second screen background is not cleared
*** This bug is a duplicate of bug 1626935 *** https://bugs.launchpad.net/bugs/1626935 This bug was affecting me as well but seems to have been fixed in the last week or so. -- 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/1633227 Title: After update to 16.10 second screen background is not cleared Status in xorg package in Ubuntu: Incomplete Bug description: I just updated from 16.04 to 16.10 and now the window background is not cleared anymore - so when you drag windows they leave resedue which looks like the screenshot I attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1633227/+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 1642019] Re: Icons for accounts look pixelated
** Changed in: webapps-sprint Milestone: sprint-27 => sprint-28 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1642019 Title: Icons for accounts look pixelated Status in webapps-sprint: New Status in ubuntu-system-settings-online-accounts package in Ubuntu: Confirmed Bug description: bq M10 rc-proposed r231 Open Accounts and/or Add account. Notice the icons there looks pixelated, jagged. Screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/webapps-sprint/+bug/1642019/+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 1560086] Re: cannot download files with no destination app from webapps
** Changed in: webapps-sprint Milestone: sprint-27 => sprint-28 -- 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/1560086 Title: cannot download files with no destination app from webapps Status in Canonical System Image: Confirmed Status in Ubuntu UX: Triaged Status in The Webapps-core project: New Status in webapps-sprint: In Progress Status in webbrowser-app package in Ubuntu: In Progress Bug description: Using the webbrowser-app I can download any file, and will be prompted to open in an app (if apps that support that content-type exist on the system) or to download the file in the browser. The same behavior should be available webapps but is not. Steps to reproduce: - Open Gmail webapp - Open a message that has an attachment of a file of unsupported type (like a .tar, .click, etc) - click on the file to download Expected results: - I should be prompted to open the file in supported app or to download - If I choose download the file should be downloaded into ~/Downloads by the webbrowser-app Actual results: - I am told that no apps exist to support this type of file and am not allowed to download it To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1560086/+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 1643901] [NEW] flxdec security update tracking bug
*** This bug is a security vulnerability *** Public security bug reported: This bug is to track the security update to fix the flxdec out-of-bounds write. ** Affects: gst-plugins-good0.10 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: gst-plugins-good1.0 (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: gst-plugins-good0.10 (Ubuntu Precise) Importance: Medium Assignee: Marc Deslauriers (mdeslaur) Status: In Progress ** Affects: gst-plugins-good1.0 (Ubuntu Precise) Importance: Undecided Status: Invalid ** Affects: gst-plugins-good0.10 (Ubuntu Trusty) Importance: Medium Assignee: Marc Deslauriers (mdeslaur) Status: In Progress ** Affects: gst-plugins-good1.0 (Ubuntu Trusty) Importance: Medium Assignee: Marc Deslauriers (mdeslaur) Status: In Progress ** Affects: gst-plugins-good0.10 (Ubuntu Xenial) Importance: Medium Assignee: Marc Deslauriers (mdeslaur) Status: In Progress ** Affects: gst-plugins-good1.0 (Ubuntu Xenial) Importance: Medium Assignee: Marc Deslauriers (mdeslaur) Status: In Progress ** Affects: gst-plugins-good0.10 (Ubuntu Yakkety) Importance: Undecided Status: Invalid ** Affects: gst-plugins-good1.0 (Ubuntu Yakkety) Importance: Medium Assignee: Marc Deslauriers (mdeslaur) Status: In Progress ** Affects: gst-plugins-good0.10 (Ubuntu Zesty) Importance: Undecided Status: Invalid ** Affects: gst-plugins-good1.0 (Ubuntu Zesty) Importance: Undecided Status: Confirmed ** Also affects: gst-plugins-good1.0 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: gst-plugins-good1.0 (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: gst-plugins-good1.0 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: gst-plugins-good1.0 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: gst-plugins-good1.0 (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: gst-plugins-good0.10 (Ubuntu) Importance: Undecided Status: New ** Changed in: gst-plugins-good1.0 (Ubuntu Precise) Status: New => Invalid ** Changed in: gst-plugins-good0.10 (Ubuntu Yakkety) Status: New => Invalid ** Changed in: gst-plugins-good0.10 (Ubuntu Zesty) Status: New => Invalid ** Changed in: gst-plugins-good0.10 (Ubuntu Precise) Importance: Undecided => Medium ** Changed in: gst-plugins-good0.10 (Ubuntu Precise) Status: New => In Progress ** Changed in: gst-plugins-good0.10 (Ubuntu Precise) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) ** Changed in: gst-plugins-good0.10 (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: gst-plugins-good0.10 (Ubuntu Trusty) Status: New => In Progress ** Changed in: gst-plugins-good0.10 (Ubuntu Trusty) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) ** Changed in: gst-plugins-good0.10 (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: gst-plugins-good0.10 (Ubuntu Xenial) Status: New => In Progress ** Changed in: gst-plugins-good0.10 (Ubuntu Xenial) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) ** Changed in: gst-plugins-good1.0 (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: gst-plugins-good1.0 (Ubuntu Trusty) Status: New => In Progress ** Changed in: gst-plugins-good1.0 (Ubuntu Trusty) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) ** Changed in: gst-plugins-good1.0 (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: gst-plugins-good1.0 (Ubuntu Xenial) Status: New => In Progress ** Changed in: gst-plugins-good1.0 (Ubuntu Xenial) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) ** Changed in: gst-plugins-good1.0 (Ubuntu Yakkety) Importance: Undecided => Medium ** Changed in: gst-plugins-good1.0 (Ubuntu Yakkety) Status: New => In Progress ** Changed in: gst-plugins-good1.0 (Ubuntu Yakkety) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) ** Changed in: gst-plugins-good1.0 (Ubuntu Zesty) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-good1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1643901 Title: flxdec security update tracking bug Status in gst-plugins-good0.10 package in Ubuntu: Invalid Status in gst-plugins-good1.0 package in Ubuntu: Confirmed Status in gst-plugins-good0.10 source package in Precise: In Progress Status in gst-plugins-good1.0 source package in Precise: Invalid Status in gst-plugins-good0.10 source package in Trusty: In Progress Status in gst-plugins-good1.0 source package in Trusty: In Progress Status in gst-plugins-good0.10 source package in Xenial: In Progress Status in
[Touch-packages] [Bug 1639050] Re: Wrong package section, should be in "introspection"
** Changed in: webapps-sprint Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsignon-glib in Ubuntu. https://bugs.launchpad.net/bugs/1639050 Title: Wrong package section, should be in "introspection" Status in webapps-sprint: Fix Released Status in libsignon-glib package in Ubuntu: Fix Released Bug description: Packages shipping gobject introspection should be in the dedicated section "introspection". This archive section was added a while ago, see also the corresponding entry in the debian policy 3.9.3.0: 2.6. Version 3.9.3.0 Released February, 2012. 2.4 New archive sections _education_, _introspection_, and _metapackages_ added. Packages shipping gobject introspection should be named gir1.2-NAMESPACE-VERSION. Based on the output of apt-cache, the following packages are in the wrong section. I didn't file a separate bug for all of them. I would appreciate if you can adjust the archive section for all the following packages in one go. #!/bin/bash while read pkg ; do apt-cache show $pkg | grep Section | grep -v introspection -q && echo $pkg done < <( apt-cache search -n ^gir1.2 | cut -f1 -d' ' ) gir1.2-accounts-1.0 gir1.2-accountsservice-1.0 gir1.2-appindicator-0.1 gir1.2-appindicator3-0.1 gir1.2-atk-1.0 gir1.2-atspi-2.0 gir1.2-bamf-3 gir1.2-cheese-3.0 gir1.2-clutter-1.0 gir1.2-cogl-1.0 gir1.2-coglpango-1.0 gir1.2-colord-1.0 gir1.2-dbusmenu-glib-0.4 gir1.2-dbusmenu-gtk-0.4 gir1.2-dbusmenu-gtk3-0.4 gir1.2-dee-1.0 gir1.2-ebook-1.2 gir1.2-edataserver-1.2 gir1.2-fcitx-1.0 gir1.2-freedesktop gir1.2-gconf-2.0 gir1.2-gdata-0.0 gir1.2-gdesktopenums-3.0 gir1.2-gdkpixbuf-2.0 gir1.2-gkbd-3.0 gir1.2-glib-2.0 gir1.2-gmenu-3.0 gir1.2-gnomebluetooth-1.0 gir1.2-gnomedesktop-3.0 gir1.2-goa-1.0 gir1.2-gtk-2.0 gir1.2-gtk-3.0 gir1.2-gtkclutter-1.0 gir1.2-gtksource-3.0 gir1.2-gtop-2.0 gir1.2-gucharmap-2.90 gir1.2-gudev-1.0 gir1.2-gweather-3.0 gir1.2-hud-2 gir1.2-hud-client-2 gir1.2-ido3-0.1 gir1.2-json-1.0 gir1.2-lightdm-1 gir1.2-messagingmenu-1.0 gir1.2-nautilus-3.0 gir1.2-networkmanager-1.0 gir1.2-notify-0.7 gir1.2-packagekitglib-1.0 gir1.2-pango-1.0 gir1.2-peas-1.0 gir1.2-polkit-1.0 gir1.2-rb-3.0 gir1.2-rest-0.7 gir1.2-rest-extras-0.7 gir1.2-rsvg-2.0 gir1.2-signon-1.0 gir1.2-soup-2.4 gir1.2-telepathyglib-0.12 gir1.2-timezonemap-1.0 gir1.2-totem-1.0 gir1.2-totem-plparser-1.0 gir1.2-unity-5.0 gir1.2-upowerglib-1.0 gir1.2-wnck-3.0 gir1.2-evince-3.0 gir1.2-geocodeglib-1.0 gir1.2-libertine gir1.2-nmgtk-1.0 gir1.2-ubuntu-app-launch-2 gir1.2-anjuta-3.0 gir1.2-atril gir1.2-caja gir1.2-caribou-1.0 gir1.2-champlain-0.12 gir1.2-cryptui-0.0 gir1.2-diodon-1.0 gir1.2-eom gir1.2-evd-0.1 gir1.2-folks-0.6 gir1.2-gdl-3 gir1.2-gssdp-1.0 gir1.2-gtk-vnc-2.0 gir1.2-gtkchamplain-0.12 gir1.2-gupnp-1.0 gir1.2-gupnp-av-1.0 gir1.2-gupnpigd-1.0 gir1.2-indicate-0.7 gir1.2-itl-1.0 gir1.2-keybinder-3.0 gir1.2-maliit-1.0 gir1.2-mate-menu gir1.2-mate-panel gir1.2-mate-polkit gir1.2-matekbd gir1.2-mutter-3.0 gir1.2-spice-client-glib-2.0 gir1.2-spice-client-gtk-3.0 gir1.2-telepathylogger-0.2 gir1.2-urfkill-glib0 gir1.2-v-sim-1.0 gir1.2-gladeui-2.0 gir1.2-grip gir1.2-javascriptcoregtk-3.0 gir1.2-libvirt-glib-1.0 gir1.2-nemo-3.0 gir1.2-snapd-1 gir1.2-webkit-3.0 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gir1.2-accounts-1.0 1.22+16.10.20160520.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Thu Nov 3 22:02:42 2016 InstallationDate: Installed on 2011-11-10 (1819 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: libaccounts-glib UpgradeStatus: Upgraded to yakkety on 2016-11-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/webapps-sprint/+bug/1639050/+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 1639175] Re: Please add an "account-plugin-nextcloud" package
** Changed in: webapps-sprint Status: In Progress => Fix Released -- 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/1639175 Title: Please add an "account-plugin-nextcloud" package Status in webapps-sprint: Fix Released Status in account-plugins package in Ubuntu: Fix Released Bug description: Please add an account-plugin-nextcloud package. For now, this could essentially be a copy of the ownCloud provider code with different branding. Having both providers side-by-side has a few benefits: 1. we can pick which one to install to get desired branding 2. if the two projects diverge API wise, we can support each independently rather than targeting a common subset. The obvious downside though is that we'll have some duplication while they are ABI compatible. To manage notifications about this bug go to: https://bugs.launchpad.net/webapps-sprint/+bug/1639175/+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 1643843] Re: Distorted colours after suspend / resume cycle
I couldn't reproduce the problem with Trusty (14.04) using its original HWE stack (AKA Kernel 3.13). -- 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/1643843 Title: Distorted colours after suspend / resume cycle Status in xorg package in Ubuntu: New Bug description: When waking up the system from a suspend-resume cycle, the display most times shows distorted colours. As a workaround one can switch to the linux console (VT) and back to fix the display. Alternatively triggering DPMS also fixes the problem (xset dpms force off ; sleep 0.1; xset dpms force on) Hardware: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] PCIID: 1002:6779 I've tested Ubuntu Xenial (16.04) with the latest updates: mesa 11.2.0-1ubuntu2.2 xserver-xorg-video-radeon 1:7.7.0-1 linux-image-4.4.0-47-generic 4.4.0-47.68 xserver-xorg-core 2:1.18.3-1ubuntu2.3 I've tried older kernels, xorg, linux-firmware, as a colleague claimed it started for him after some of the latest Ubuntu updates, but couldn't find a working configuration. I also checked Ubuntu Yakkety (16.10), where I couldn't reproduce with XFCE, but instantly with the Unity session, but probably XFCE was just lucky, as sometimes I also had series of working (~5) cycles. Current versions: mesa 12.0.3-1ubuntu2 xserver-xorg-video-radeon 1:7.7.1-1 linux-image-4.8.0-27-generic 4.8.0-27.29 xserver-xorg-core 2:1.18.4-1ubuntu6.1 I'm also going to test Trusty (14.04) to check if it's really a regression. At least I have never seen this problem while running it. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 22 12:21:24 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Radeon HD 6450 [1642:3a75] Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 4524BL8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic root=UUID=4dda3a4b-6e9c-49ba-a969-5d2146f02b60 ro splash quiet vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 9HKT54AUS dmi.board.vendor: LENOVO 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:bvnLENOVO:bvr9HKT54AUS:bd10/16/2012:svnLENOVO:pn4524BL8:pvrThinkCentreM91p:rvnLENOVO:rn:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: 4524BL8 dmi.product.version: ThinkCentre M91p dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Tue Nov 22 11:56:40 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1643843/+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 1643838] Re: ureadahead trying to read entire filesystem
** Also affects: ureadahead (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1643838 Title: ureadahead trying to read entire filesystem Status in curtin: New Status in MAAS: Invalid Status in cloud-init package in Ubuntu: New Status in ureadahead package in Ubuntu: New Bug description: MAAS Version 2.1.1+bzr5544-0ubuntu1 (16.04.1), deploying Ubuntu 16.04.1 As shown in bug 1635560 and specifically in https://pastebin.canonical.com/171385/ during deployment, ureadahead (sometimes?) tries to index the whole filesystem, complaining about all of the relative paths. These are the log messages immediately before the spamminess: Nov 22 08:32:32 faraday systemd[1]: Starting Stop ureadahead data collection... Nov 22 08:32:32 faraday systemd[1]: Stopping Read required files in advance... Nov 22 08:32:32 faraday systemd[1]: Started Stop ureadahead data collection. The ureadahead lines are responsible for the vast majority of the installation log ⟫ cat faraday-installation-log | wc -l 78777 ⟫ grep ureadahead faraday-installation-log | wc -l 76799 To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1643838/+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 1642605] Re: maliit-framework segmentation fault with Qt 5.7.1
Valgrind trace ==30302==at 0x5211880: QSharedDataPointer (qshareddata.h:92) ==30302==by 0x5211880: QDateTime::QDateTime() (qdatetime.cpp:2965) ==30302==by 0x52168BE: QDateTime::fromMSecsSinceEpoch(long long, Qt::TimeSpec, int) (qdatetime.cpp:4314) ==30302==by 0x5216F39: QDateTime::fromTime_t(unsigned int) (qdatetime.cpp:4236) ==30302==by 0x52D1DD5: modificationTime (qfilesystemmetadata_p.h:280) ==30302==by 0x52D1DD5: QFileInfo::lastModified() const (qfileinfo.cpp:1339) ==30302==by 0x531DADF: QConfFileSettingsPrivate::syncConfFile(QConfFile*) (qsettings.cpp:1496) ==30302==by 0x531E2DA: QConfFileSettingsPrivate::sync() (qsettings.cpp:1370) ==30302==by 0x5315A05: QSettings::~QSettings() (qsettings.cpp:2717) ==30302==by 0x4ED97A7: MImSettingsQSettingsBackendFactory::~MImSettingsQSettingsBackendFactory() (mimsettingsqsettings.cpp:174) ==30302==by 0x4ED97CF: MImSettingsQSettingsBackendFactory::~MImSettingsQSettingsBackendFactory() (mimsettingsqsettings.cpp:176) ==30302==by 0x4ED8B8B: QScopedPointerDeleter::cleanup(MImSettingsBackendFactory*) (qscopedpointer.h:60) ==30302==by 0x4ED8F2A: QScopedPointer::~QScopedPointer() (qscopedpointer.h:107) ==30302==by 0x5BD6659: __cxa_finalize (cxa_finalize.c:56) ==30302== Address 0x0 is not stack'd, malloc'd or (recently) free'd -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to maliit-framework in Ubuntu. https://bugs.launchpad.net/bugs/1642605 Title: maliit-framework segmentation fault with Qt 5.7.1 Status in maliit-framework package in Ubuntu: New Bug description: It seems there is a segmentation fault with Qt 5.7.1 with maliit- framework as shown at https://launchpadlibrarian.net/293811765 /buildlog_ubuntu-zesty-amd64.maliit-framework_0.99.1+git20151118 +62bd54b-0ubuntu13~1_BUILDING.txt.gz -- TESTING_IN_SANDBOX=1 TESTPLUGIN_PATH=../plugins TESTDATA_PATH=/<>/maliit-framework-0.99.1+git20151118+62bd54b/tests LD_LIBRARY_PATH=../../lib:../../lib/plugins:../plugins: ./ut_mimsettings * Start testing of Ut_MImSettings * Config: Using QtTest library 5.7.1, Qt 5.7.1 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 6.2.0 20161109) PASS : Ut_MImSettings::initTestCase() PASS : Ut_MImSettings::testValue() PASS : Ut_MImSettings::testModifyValue() PASS : Ut_MImSettings::testUnsetValue() PASS : Ut_MImSettings::testModifyValueNotification() PASS : Ut_MImSettings::testListDirs() PASS : Ut_MImSettings::testListEntries() PASS : Ut_MImSettings::cleanupTestCase() Totals: 8 passed, 0 failed, 0 skipped, 0 blacklisted, 44ms * Finished testing of Ut_MImSettings * Segmentation fault (core dumped) Makefile:336: recipe for target 'check' failed make[4]: *** [check] Error 139 -- More information about Qt 5.7.1 at https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maliit-framework/+bug/1642605/+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 1643838] Re: ureadahead trying to read entire filesystem
curtin does not do any read-ahead configuration; ** Changed in: curtin Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1643838 Title: ureadahead trying to read entire filesystem Status in MAAS: Invalid Status in ureadahead package in Ubuntu: New Bug description: MAAS Version 2.1.1+bzr5544-0ubuntu1 (16.04.1), deploying Ubuntu 16.04.1 As shown in bug 1635560 and specifically in https://pastebin.canonical.com/171385/ during deployment, ureadahead (sometimes?) tries to index the whole filesystem, complaining about all of the relative paths. These are the log messages immediately before the spamminess: Nov 22 08:32:32 faraday systemd[1]: Starting Stop ureadahead data collection... Nov 22 08:32:32 faraday systemd[1]: Stopping Read required files in advance... Nov 22 08:32:32 faraday systemd[1]: Started Stop ureadahead data collection. The ureadahead lines are responsible for the vast majority of the installation log ⟫ cat faraday-installation-log | wc -l 78777 ⟫ grep ureadahead faraday-installation-log | wc -l 76799 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1643838/+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 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety
I have the same issue since updating to 16.04 :( I have found a consistent way to get A2DP profile working - but it has to be done on every reconnect :( I switch to HSP/HFP - and sound works. Then I stop ALL sound.. and disconnect bluetoothe device, reconnects bluetoothe device, and then switch profile to a2dp(sink) - and ONLY then, can I start the music again. -- 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/1438510 Title: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety Status in PulseAudio: Unknown Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in bluez source package in Vivid: Won't Fix Status in pulseaudio source package in Vivid: Won't Fix Bug description: Just installed 15.04 fresh from the latest ISO (beta2). I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems to have regressed in functionality. In 14.10, I was able to set the output profile either to a2dp or hsp/hfp (telephony duplex). In 15.04, it only works in telephony duplex mode. I can't get high fidelity sound playback to work at all. This thread seems to be related, though the workaround within did not solve the problem for me: https://bbs.archlinux.org/viewtopic.php?id=194006 The bug is still present in 16.04 LTS and 16.10. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1438510/+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 1309433] Re: account-console crash
** Changed in: webapps-sprint Status: In Progress => Fix Released ** Changed in: account-plugins Status: In Progress => Fix Released -- 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/1309433 Title: account-console crash Status in Online Accounts: Account plugins: Fix Released Status in webapps-sprint: Fix Released Status in account-plugins package in Ubuntu: Fix Released Bug description: jmax@jmax-CKR2 ~% account-console show 1 (process:4718): accounts-glib-WARNING **: Unable to load account 1 Traceback (most recent call last): File "/usr/bin/account-console", line 36, in show_account print >> sys.stderr, 'Account "%s" not found' % args.account TypeError: unsupported operand type(s) for >>: 'builtin_function_or_method' and '_io.TextIOWrapper' and I have to type Ctrl C To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1309433/+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 1643843] Re: Distorted colours after suspend / resume cycle
Now I tried all the Trusty HWEs and it seems to have started with Wily. xserver-xorg-video-radeon-lts-wily 1:7.5.0+git20150819-0ubuntu1~trusty1 linux-image-generic-lts-wily 4.2.0.42.34 xserver-xorg-core-lts-wily 2:1.17.2-1ubuntu9.1~trusty1 mesa-lts-wily 11.0.2-1ubuntu4~trusty1 I had once wrong colors with the Trusty initial stack (3.13), which I couldn't reproduce. And I was just told that disabling DPMS / monitor power management in KDE also prevents the problem, which might correlate with the fact, that running a DPMS "force off" / "force on" cycle also restores the colors correctly. -- 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/1643843 Title: Distorted colours after suspend / resume cycle Status in xorg package in Ubuntu: New Bug description: When waking up the system from a suspend-resume cycle, the display most times shows distorted colours. As a workaround one can switch to the linux console (VT) and back to fix the display. Alternatively triggering DPMS also fixes the problem (xset dpms force off ; sleep 0.1; xset dpms force on) Hardware: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] PCIID: 1002:6779 I've tested Ubuntu Xenial (16.04) with the latest updates: mesa 11.2.0-1ubuntu2.2 xserver-xorg-video-radeon 1:7.7.0-1 linux-image-4.4.0-47-generic 4.4.0-47.68 xserver-xorg-core 2:1.18.3-1ubuntu2.3 I've tried older kernels, xorg, linux-firmware, as a colleague claimed it started for him after some of the latest Ubuntu updates, but couldn't find a working configuration. I also checked Ubuntu Yakkety (16.10), where I couldn't reproduce with XFCE, but instantly with the Unity session, but probably XFCE was just lucky, as sometimes I also had series of working (~5) cycles. Current versions: mesa 12.0.3-1ubuntu2 xserver-xorg-video-radeon 1:7.7.1-1 linux-image-4.8.0-27-generic 4.8.0-27.29 xserver-xorg-core 2:1.18.4-1ubuntu6.1 I'm also going to test Trusty (14.04) to check if it's really a regression. At least I have never seen this problem while running it. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 22 12:21:24 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Radeon HD 6450 [1642:3a75] Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 4524BL8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic root=UUID=4dda3a4b-6e9c-49ba-a969-5d2146f02b60 ro splash quiet vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 9HKT54AUS dmi.board.vendor: LENOVO 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:bvnLENOVO:bvr9HKT54AUS:bd10/16/2012:svnLENOVO:pn4524BL8:pvrThinkCentreM91p:rvnLENOVO:rn:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: 4524BL8 dmi.product.version: ThinkCentre M91p dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Tue Nov 22 11:56:40 2016
[Touch-packages] [Bug 1643467] Re: Firefox 50 blocks Ubuntu 14.04 LTS's version of libavcodec
I concur. Ubuntu 14.04, which is an LTS release, should update libavcodec to version 54.35.1 or higher. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1643467 Title: Firefox 50 blocks Ubuntu 14.04 LTS's version of libavcodec Status in firefox package in Ubuntu: Confirmed Status in libav package in Ubuntu: Confirmed Bug description: Whenever it tries to play a video, Firefox 50 displays this message at the top of every page: "libavcodec may be vulnerable or is not supported, and should be updated to play video" https://dxr.mozilla.org/mozilla-central/source/browser/locales/en- US/chrome/browser/browser.properties?q=%22libavcodec+may+be+vulnerable%22_type=single#742 Firefox refuses any libavcodec version prior to 54.35.1 (unless media.libavcodec.allow-obsolete==true). https://dxr.mozilla.org/mozilla- central/source/dom/media/platforms/ffmpeg/FFmpegLibWrapper.cpp#60 Users should not be subjected to this warning, as it is vague (does not instruct them how to fix it). Ubuntu 14.04 LTS should ship with an updated version of libavcodec. DistroRelease: Ubuntu 14.04 Package: firefox 50.0+build2-0ubuntu0.14.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1643467/+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 1598300] Re: CUPS web interface stops responding after a while
I want to remind everyone subscribed to this bug to please test the fixed package and verify it. If you get an error during the installation process (see bug 1642966), please run the commands sudo service cups stop sudo apt-get install -f sudo service cups start in a terminal window to complete the installation (see also comment #5 in bug 1642966). Then test whether this bug is fixed. To the SRU team: Bug 1642966 cannot be caused by the fix for this bug. The fix is a trivial change in the scheduler, see the debdiff attched to comment #20 of this bug. Bug 1642966 is probably caused by some coincidence which had also broken any other update of the cups package. -- 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/1598300 Title: CUPS web interface stops responding after a while Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: Fix Committed Bug description: after 6 minutes or so, cups is not responding. it do not produce error on the log, just stop working, worse, it exit with 0 ⌌—⌍ |root@cupsmachine :~# systemctl status cups | |● cups.service - CUPS Scheduler | | Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled)| | Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago | | Docs: man:cupsd(8) | | Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, status=0/SUCCESS)| | Main PID: 28686 (code=exited, status=0/SUCCESS) | | | |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler. | ⌎—⌏ I got to launch it again, so I have finish with a cron job like */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && systemctl start cups but it is a dirty solution. I have no idea of what make it stop. NB: I have seen problems related to apparmor, this machine has no apparmor package. [Impact] If you want to use the CUPS web interface in Xenial and therefore set "WebInterface Yes" in /etc/cups/cupsd.conf, CUPS could auto-shutdown when it is idle and then an attempt to access http://localhost:631/ via a web browser fails. People get confused as other access to CUPS [Testcase] Take a CUPS setup on Xenial with no shared print queues and CUPS only listening on the domain socket. Activate the web interface via cupsctl WebInterface=Yes Now you are able to access the web interface via http://localhost:631/. Wait for some minutes without accessing CUPS until the CUPS daemon shuts down automatically. Try to open the web interface again and it will not work. With the fixed CUPS package CUPS will not auto-shutdown when the web interface is activated. [Regression Potential] Low, as we are removing a simple distro patch to get back to the original, upstream behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1598300/+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 1643901] Re: flxdec security update tracking bug
Marc, I'm assuming this is related to this https://scarybeastsecurity.blogspot.ca/2016/11/0day-exploit-advancing- exploitation.html, right? Like the author, I question the upstream decision to include FLIC support in the "good" set. Would it be possible to move that plugin to the "bad" or the "ugly" set since it's presumably a very rarely used format? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-good0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1643901 Title: flxdec security update tracking bug Status in gst-plugins-good0.10 package in Ubuntu: Invalid Status in gst-plugins-good1.0 package in Ubuntu: Confirmed Status in gst-plugins-good0.10 source package in Precise: In Progress Status in gst-plugins-good1.0 source package in Precise: Invalid Status in gst-plugins-good0.10 source package in Trusty: In Progress Status in gst-plugins-good1.0 source package in Trusty: In Progress Status in gst-plugins-good0.10 source package in Xenial: In Progress Status in gst-plugins-good1.0 source package in Xenial: In Progress Status in gst-plugins-good0.10 source package in Yakkety: Invalid Status in gst-plugins-good1.0 source package in Yakkety: In Progress Status in gst-plugins-good0.10 source package in Zesty: Invalid Status in gst-plugins-good1.0 source package in Zesty: Confirmed Bug description: This bug is to track the security update to fix the flxdec out-of- bounds write. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good0.10/+bug/1643901/+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 1643843] Re: Distorted colours after suspend / resume cycle
So I downloaded some kernels from http://kernel.ubuntu.com/~kernel- ppa/mainline/?C=N;O=D Working: linux-image-4.1.35-040135-generic_4.1.35-040135.201610241431_amd64.deb Broken: linux-image-4.2.7-040207-generic_4.2.7-040207.201512091533_amd64.deb -- 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/1643843 Title: Distorted colours after suspend / resume cycle Status in xorg package in Ubuntu: New Bug description: When waking up the system from a suspend-resume cycle, the display most times shows distorted colours. As a workaround one can switch to the linux console (VT) and back to fix the display. Alternatively triggering DPMS also fixes the problem (xset dpms force off ; sleep 0.1; xset dpms force on) Hardware: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] PCIID: 1002:6779 I've tested Ubuntu Xenial (16.04) with the latest updates: mesa 11.2.0-1ubuntu2.2 xserver-xorg-video-radeon 1:7.7.0-1 linux-image-4.4.0-47-generic 4.4.0-47.68 xserver-xorg-core 2:1.18.3-1ubuntu2.3 I've tried older kernels, xorg, linux-firmware, as a colleague claimed it started for him after some of the latest Ubuntu updates, but couldn't find a working configuration. I also checked Ubuntu Yakkety (16.10), where I couldn't reproduce with XFCE, but instantly with the Unity session, but probably XFCE was just lucky, as sometimes I also had series of working (~5) cycles. Current versions: mesa 12.0.3-1ubuntu2 xserver-xorg-video-radeon 1:7.7.1-1 linux-image-4.8.0-27-generic 4.8.0-27.29 xserver-xorg-core 2:1.18.4-1ubuntu6.1 I'm also going to test Trusty (14.04) to check if it's really a regression. At least I have never seen this problem while running it. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 22 12:21:24 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Radeon HD 6450 [1642:3a75] Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 4524BL8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic root=UUID=4dda3a4b-6e9c-49ba-a969-5d2146f02b60 ro splash quiet vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 9HKT54AUS dmi.board.vendor: LENOVO 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:bvnLENOVO:bvr9HKT54AUS:bd10/16/2012:svnLENOVO:pn4524BL8:pvrThinkCentreM91p:rvnLENOVO:rn:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: 4524BL8 dmi.product.version: ThinkCentre M91p dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Tue Nov 22 11:56:40 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1643843/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to
[Touch-packages] [Bug 1643843] Re: Distorted colours after suspend / resume cycle
While keeping the Xenial HWE stack on Ubuntu Trusty (14.04), I tried various installed HWE kernels. It seems it really broke with the Wily kernel (4.2.0.42.34). The Vivid kernel (3.19.0.74.56) has survived multiple resume cycles, while Wily instantly created the problem. -- 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/1643843 Title: Distorted colours after suspend / resume cycle Status in xorg package in Ubuntu: New Bug description: When waking up the system from a suspend-resume cycle, the display most times shows distorted colours. As a workaround one can switch to the linux console (VT) and back to fix the display. Alternatively triggering DPMS also fixes the problem (xset dpms force off ; sleep 0.1; xset dpms force on) Hardware: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] PCIID: 1002:6779 I've tested Ubuntu Xenial (16.04) with the latest updates: mesa 11.2.0-1ubuntu2.2 xserver-xorg-video-radeon 1:7.7.0-1 linux-image-4.4.0-47-generic 4.4.0-47.68 xserver-xorg-core 2:1.18.3-1ubuntu2.3 I've tried older kernels, xorg, linux-firmware, as a colleague claimed it started for him after some of the latest Ubuntu updates, but couldn't find a working configuration. I also checked Ubuntu Yakkety (16.10), where I couldn't reproduce with XFCE, but instantly with the Unity session, but probably XFCE was just lucky, as sometimes I also had series of working (~5) cycles. Current versions: mesa 12.0.3-1ubuntu2 xserver-xorg-video-radeon 1:7.7.1-1 linux-image-4.8.0-27-generic 4.8.0-27.29 xserver-xorg-core 2:1.18.4-1ubuntu6.1 I'm also going to test Trusty (14.04) to check if it's really a regression. At least I have never seen this problem while running it. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Nov 22 12:21:24 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779] (prog-if 00 [VGA controller]) Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Radeon HD 6450 [1642:3a75] Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 4524BL8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic root=UUID=4dda3a4b-6e9c-49ba-a969-5d2146f02b60 ro splash quiet vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 9HKT54AUS dmi.board.vendor: LENOVO 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:bvnLENOVO:bvr9HKT54AUS:bd10/16/2012:svnLENOVO:pn4524BL8:pvrThinkCentreM91p:rvnLENOVO:rn:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: 4524BL8 dmi.product.version: ThinkCentre M91p dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Tue Nov 22 11:56:40 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1643843/+subscriptions -- Mailing list: