[Touch-packages] [Bug 1572653] Re: keyboard does not show up on xenial
First of all, I am sorry that I misjudged where my problem belonged to. Secondly, I am very thankful for your reply and happy to confirm that following steps in ubuntu phone shell allowed for a gtk application running within xmir did enable OSK in this app: $ sudo mount -o remount,rw / $ sudo apt-get install maliit-inputcontext-gtk3 maliit-inputcontext-gtk2 $ sudo mount -o remount,ro / -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1572653 Title: keyboard does not show up on xenial Status in ubuntu-keyboard package in Ubuntu: Confirmed Bug description: Expected behaviour: Install ubuntu-keyboard, run maliit-server, click on place to enter text -> keyboard shows up. What happens: Running maliit-server after installing ubuntu-keyboard-english in terminal shows following error: WARNING: void MIMPluginManagerPrivate::_q_setActiveSubView(const QString&, Maliit::HandlerState) "libubuntu-keyboard-plugin.so" "en" is not enabled Clicking on fields for entering text, does not cause the keyboard to show up. What I tried so far: export QT_IM_MODULE=Maliit export GTK_IM_MODULE=Maliit and gconftool-2 -s --type list --list-type string /maliit/onscreen/enabled "[llibubuntu-keyboard-plugin.so,en_gb]" gconftool-2 -s --type list --list-type string /maliit/onscreen/active "[libubuntu-keyboard-plugin.so,en_gb]" according to https://github.com/maliit/framework and https://github.com/maliit/plugins but it still won't show up. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-keyboard 0.99.trunk.phablet2+16.04.20160226.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 20 18:03:03 2016 InstallationDate: Installed on 2016-04-03 (16 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-keyboard UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.xdg.maliit.org.server.conf: [modified] mtime.conffile..etc.xdg.maliit.org.server.conf: 2016-04-20T17:40:50.856195 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1572653/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1605350] Re: apport info dialog about application crash doesn't contain application name
[Expired for apport (Ubuntu) because there has been no activity for 60 days.] ** Changed in: apport (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1605350 Title: apport info dialog about application crash doesn't contain application name Status in apport package in Ubuntu: Expired Bug description: It's possible that `apport` displays a dialog which informs about the crash of an application which doesn't contain the name of the application which makes the dialog almost useless in comparison to a dialog which would contain the name (see screenshot for details). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apport-gtk 2.20.1-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: openafs ApportLog: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jul 21 20:05:29 2016 InstallationDate: Installed on 2015-12-12 (222 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to xenial on 2016-03-14 (129 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1605350/+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 1627421]
StacktraceTop: dhcp6_start (self=self@entry=0x561ce8cfa890, wait_for_ll=wait_for_ll@entry=0, reason=reason@entry=0x0) at devices/nm-device.c:5446 nm_device_dhcp6_renew (self=self@entry=0x561ce8cfa890, release=release@entry=0) at devices/nm-device.c:5466 nm_device_update_dynamic_ip_setup (self=0x561ce8cfa890) at devices/nm-device.c:1298 carrier_changed (device=0x561ce8cfa890, carrier=1) at devices/nm-device-ethernet.c:1576 nm_device_set_carrier (self=0x561ce8cfa890, carrier=1) at devices/nm-device.c:1436 -- 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/1627421 Title: NetworkManager crashed with SIGSEGV in dhcp6_start() Status in network-manager package in Ubuntu: New Bug description: miked@free-yak:~$ lsb_release -rd Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 miked@free-yak:~$ apt-cache policy NetworkManager N: Unable to locate package NetworkManager miked@free-yak:~$ apt-cache policy nm_device_update_dynamic_ip_setup N: Unable to locate package nm_device_update_dynamic_ip_setup miked@free-yak:~$ I don't know what was expected to happen, this crashed happened. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.2-0ubuntu10 ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7 Uname: Linux 4.8.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Sat Sep 24 20:06:02 2016 ExecutablePath: /usr/sbin/NetworkManager IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-03 (174 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IpRoute: default via 10.0.0.1 dev enp0s17 proto static metric 100 default via 10.0.0.1 dev wlp8s9 proto static metric 600 10.0.0.0/24 dev enp0s17 proto kernel scope link src 10.0.0.84 metric 100 10.0.0.0/24 dev wlp8s9 proto kernel scope link src 10.0.0.218 metric 600 169.254.0.0/16 dev enp0s17 scope link metric 1000 NetworkManager.conf: [main] plugins=ifupdown,keyfile,ofono [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcCmdline: /usr/sbin/NetworkManager --no-daemon ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Signal: 11 SourcePackage: network-manager StacktraceTop: ?? () nm_device_update_dynamic_ip_setup () ?? () nm_device_set_carrier () ?? () Title: NetworkManager crashed with SIGSEGV in nm_device_update_dynamic_ip_setup() UpgradeStatus: Upgraded to yakkety on 2016-08-28 (28 days ago) UserGroups: nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH enp0s17 ethernet connected/org/freedesktop/NetworkManager/Devices/1 Wired connection 1 0a821d1a-0aa1-33eb-a8e8-d691b38de9f0 /org/freedesktop/NetworkManager/ActiveConnection/0 wlp8s9 wifi connected/org/freedesktop/NetworkManager/Devices/3 FREE2U2.4WI-FI 6784f99c-73d0-4d8b-8fb0-d39d3ef01313 /org/freedesktop/NetworkManager/ActiveConnection/1 enp0s18 ethernet unavailable /org/freedesktop/NetworkManager/Devices/0 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1627421/+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 1627421] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1627421/+attachment/4748223/+files/ThreadStacktrace.txt ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1627421/+attachment/4748202/+files/CoreDump.gz ** Changed in: network-manager (Ubuntu) Importance: Undecided => Medium ** Summary changed: - NetworkManager crashed with SIGSEGV in nm_device_update_dynamic_ip_setup() + NetworkManager crashed with SIGSEGV in dhcp6_start() ** Tags removed: need-amd64-retrace -- 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/1627421 Title: NetworkManager crashed with SIGSEGV in dhcp6_start() Status in network-manager package in Ubuntu: New Bug description: miked@free-yak:~$ lsb_release -rd Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 miked@free-yak:~$ apt-cache policy NetworkManager N: Unable to locate package NetworkManager miked@free-yak:~$ apt-cache policy nm_device_update_dynamic_ip_setup N: Unable to locate package nm_device_update_dynamic_ip_setup miked@free-yak:~$ I don't know what was expected to happen, this crashed happened. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.2-0ubuntu10 ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7 Uname: Linux 4.8.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Sat Sep 24 20:06:02 2016 ExecutablePath: /usr/sbin/NetworkManager IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-03 (174 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IpRoute: default via 10.0.0.1 dev enp0s17 proto static metric 100 default via 10.0.0.1 dev wlp8s9 proto static metric 600 10.0.0.0/24 dev enp0s17 proto kernel scope link src 10.0.0.84 metric 100 10.0.0.0/24 dev wlp8s9 proto kernel scope link src 10.0.0.218 metric 600 169.254.0.0/16 dev enp0s17 scope link metric 1000 NetworkManager.conf: [main] plugins=ifupdown,keyfile,ofono [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcCmdline: /usr/sbin/NetworkManager --no-daemon ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Signal: 11 SourcePackage: network-manager StacktraceTop: ?? () nm_device_update_dynamic_ip_setup () ?? () nm_device_set_carrier () ?? () Title: NetworkManager crashed with SIGSEGV in nm_device_update_dynamic_ip_setup() UpgradeStatus: Upgraded to yakkety on 2016-08-28 (28 days ago) UserGroups: nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH enp0s17 ethernet connected/org/freedesktop/NetworkManager/Devices/1 Wired connection 1 0a821d1a-0aa1-33eb-a8e8-d691b38de9f0 /org/freedesktop/NetworkManager/ActiveConnection/0 wlp8s9 wifi connected/org/freedesktop/NetworkManager/Devices/3 FREE2U2.4WI-FI 6784f99c-73d0-4d8b-8fb0-d39d3ef01313 /org/freedesktop/NetworkManager/ActiveConnection/1 enp0s18 ethernet unavailable /org/freedesktop/NetworkManager/Devices/0 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1627421/+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 1627421] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1627421/+attachment/4748221/+files/Stacktrace.txt -- 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/1627421 Title: NetworkManager crashed with SIGSEGV in dhcp6_start() Status in network-manager package in Ubuntu: New Bug description: miked@free-yak:~$ lsb_release -rd Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 miked@free-yak:~$ apt-cache policy NetworkManager N: Unable to locate package NetworkManager miked@free-yak:~$ apt-cache policy nm_device_update_dynamic_ip_setup N: Unable to locate package nm_device_update_dynamic_ip_setup miked@free-yak:~$ I don't know what was expected to happen, this crashed happened. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.2-0ubuntu10 ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7 Uname: Linux 4.8.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Sat Sep 24 20:06:02 2016 ExecutablePath: /usr/sbin/NetworkManager IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-03 (174 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IpRoute: default via 10.0.0.1 dev enp0s17 proto static metric 100 default via 10.0.0.1 dev wlp8s9 proto static metric 600 10.0.0.0/24 dev enp0s17 proto kernel scope link src 10.0.0.84 metric 100 10.0.0.0/24 dev wlp8s9 proto kernel scope link src 10.0.0.218 metric 600 169.254.0.0/16 dev enp0s17 scope link metric 1000 NetworkManager.conf: [main] plugins=ifupdown,keyfile,ofono [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcCmdline: /usr/sbin/NetworkManager --no-daemon ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Signal: 11 SourcePackage: network-manager StacktraceTop: ?? () nm_device_update_dynamic_ip_setup () ?? () nm_device_set_carrier () ?? () Title: NetworkManager crashed with SIGSEGV in nm_device_update_dynamic_ip_setup() UpgradeStatus: Upgraded to yakkety on 2016-08-28 (28 days ago) UserGroups: nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH enp0s17 ethernet connected/org/freedesktop/NetworkManager/Devices/1 Wired connection 1 0a821d1a-0aa1-33eb-a8e8-d691b38de9f0 /org/freedesktop/NetworkManager/ActiveConnection/0 wlp8s9 wifi connected/org/freedesktop/NetworkManager/Devices/3 FREE2U2.4WI-FI 6784f99c-73d0-4d8b-8fb0-d39d3ef01313 /org/freedesktop/NetworkManager/ActiveConnection/1 enp0s18 ethernet unavailable /org/freedesktop/NetworkManager/Devices/0 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1627421/+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 1627421] Re: NetworkManager crashed with SIGSEGV in nm_device_update_dynamic_ip_setup()
miked@free-yak:~$ sudo apt-get update sudo: unable to resolve host free-yak: Resource temporarily unavailable [sudo] password for miked: Hit:1 http://archive.ubuntu.com/ubuntu yakkety InRelease Hit:2 http://archive.ubuntu.com/ubuntu yakkety-updates InRelease Hit:3 http://archive.canonical.com/ubuntu yakkety InRelease Hit:4 http://archive.ubuntu.com/ubuntu yakkety-backports InRelease Hit:5 http://archive.ubuntu.com/ubuntu yakkety-security InRelease Hit:6 http://archive.ubuntu.com/ubuntu yakkety-proposed InRelease Reading package lists... Done miked@free-yak:~$ -- 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/1627421 Title: NetworkManager crashed with SIGSEGV in dhcp6_start() Status in network-manager package in Ubuntu: New Bug description: miked@free-yak:~$ lsb_release -rd Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 miked@free-yak:~$ apt-cache policy NetworkManager N: Unable to locate package NetworkManager miked@free-yak:~$ apt-cache policy nm_device_update_dynamic_ip_setup N: Unable to locate package nm_device_update_dynamic_ip_setup miked@free-yak:~$ I don't know what was expected to happen, this crashed happened. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.2-0ubuntu10 ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7 Uname: Linux 4.8.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Sat Sep 24 20:06:02 2016 ExecutablePath: /usr/sbin/NetworkManager IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-03 (174 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IpRoute: default via 10.0.0.1 dev enp0s17 proto static metric 100 default via 10.0.0.1 dev wlp8s9 proto static metric 600 10.0.0.0/24 dev enp0s17 proto kernel scope link src 10.0.0.84 metric 100 10.0.0.0/24 dev wlp8s9 proto kernel scope link src 10.0.0.218 metric 600 169.254.0.0/16 dev enp0s17 scope link metric 1000 NetworkManager.conf: [main] plugins=ifupdown,keyfile,ofono [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcCmdline: /usr/sbin/NetworkManager --no-daemon ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Signal: 11 SourcePackage: network-manager StacktraceTop: ?? () nm_device_update_dynamic_ip_setup () ?? () nm_device_set_carrier () ?? () Title: NetworkManager crashed with SIGSEGV in nm_device_update_dynamic_ip_setup() UpgradeStatus: Upgraded to yakkety on 2016-08-28 (28 days ago) UserGroups: nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH enp0s17 ethernet connected/org/freedesktop/NetworkManager/Devices/1 Wired connection 1 0a821d1a-0aa1-33eb-a8e8-d691b38de9f0 /org/freedesktop/NetworkManager/ActiveConnection/0 wlp8s9 wifi connected/org/freedesktop/NetworkManager/Devices/3 FREE2U2.4WI-FI 6784f99c-73d0-4d8b-8fb0-d39d3ef01313 /org/freedesktop/NetworkManager/ActiveConnection/1 enp0s18 ethernet unavailable /org/freedesktop/NetworkManager/Devices/0 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1627421/+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 1627421] StacktraceSource.txt
** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/1627421/+attachment/4748222/+files/StacktraceSource.txt -- 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/1627421 Title: NetworkManager crashed with SIGSEGV in dhcp6_start() Status in network-manager package in Ubuntu: New Bug description: miked@free-yak:~$ lsb_release -rd Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 miked@free-yak:~$ apt-cache policy NetworkManager N: Unable to locate package NetworkManager miked@free-yak:~$ apt-cache policy nm_device_update_dynamic_ip_setup N: Unable to locate package nm_device_update_dynamic_ip_setup miked@free-yak:~$ I don't know what was expected to happen, this crashed happened. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.2-0ubuntu10 ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7 Uname: Linux 4.8.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Sat Sep 24 20:06:02 2016 ExecutablePath: /usr/sbin/NetworkManager IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-03 (174 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IpRoute: default via 10.0.0.1 dev enp0s17 proto static metric 100 default via 10.0.0.1 dev wlp8s9 proto static metric 600 10.0.0.0/24 dev enp0s17 proto kernel scope link src 10.0.0.84 metric 100 10.0.0.0/24 dev wlp8s9 proto kernel scope link src 10.0.0.218 metric 600 169.254.0.0/16 dev enp0s17 scope link metric 1000 NetworkManager.conf: [main] plugins=ifupdown,keyfile,ofono [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcCmdline: /usr/sbin/NetworkManager --no-daemon ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Signal: 11 SourcePackage: network-manager StacktraceTop: ?? () nm_device_update_dynamic_ip_setup () ?? () nm_device_set_carrier () ?? () Title: NetworkManager crashed with SIGSEGV in nm_device_update_dynamic_ip_setup() UpgradeStatus: Upgraded to yakkety on 2016-08-28 (28 days ago) UserGroups: nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH enp0s17 ethernet connected/org/freedesktop/NetworkManager/Devices/1 Wired connection 1 0a821d1a-0aa1-33eb-a8e8-d691b38de9f0 /org/freedesktop/NetworkManager/ActiveConnection/0 wlp8s9 wifi connected/org/freedesktop/NetworkManager/Devices/3 FREE2U2.4WI-FI 6784f99c-73d0-4d8b-8fb0-d39d3ef01313 /org/freedesktop/NetworkManager/ActiveConnection/1 enp0s18 ethernet unavailable /org/freedesktop/NetworkManager/Devices/0 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1627421/+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 1627421] Re: NetworkManager crashed with SIGSEGV in nm_device_update_dynamic_ip_setup()
miked@free-yak:~$ apt-cache policy network-manager network-manager: Installed: 1.2.2-0ubuntu10 Candidate: 1.2.2-0ubuntu10 Version table: *** 1.2.2-0ubuntu10 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status miked@free-yak:~$ -- 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/1627421 Title: NetworkManager crashed with SIGSEGV in dhcp6_start() Status in network-manager package in Ubuntu: New Bug description: miked@free-yak:~$ lsb_release -rd Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 miked@free-yak:~$ apt-cache policy NetworkManager N: Unable to locate package NetworkManager miked@free-yak:~$ apt-cache policy nm_device_update_dynamic_ip_setup N: Unable to locate package nm_device_update_dynamic_ip_setup miked@free-yak:~$ I don't know what was expected to happen, this crashed happened. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.2-0ubuntu10 ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7 Uname: Linux 4.8.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Sat Sep 24 20:06:02 2016 ExecutablePath: /usr/sbin/NetworkManager IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-03 (174 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IpRoute: default via 10.0.0.1 dev enp0s17 proto static metric 100 default via 10.0.0.1 dev wlp8s9 proto static metric 600 10.0.0.0/24 dev enp0s17 proto kernel scope link src 10.0.0.84 metric 100 10.0.0.0/24 dev wlp8s9 proto kernel scope link src 10.0.0.218 metric 600 169.254.0.0/16 dev enp0s17 scope link metric 1000 NetworkManager.conf: [main] plugins=ifupdown,keyfile,ofono [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcCmdline: /usr/sbin/NetworkManager --no-daemon ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Signal: 11 SourcePackage: network-manager StacktraceTop: ?? () nm_device_update_dynamic_ip_setup () ?? () nm_device_set_carrier () ?? () Title: NetworkManager crashed with SIGSEGV in nm_device_update_dynamic_ip_setup() UpgradeStatus: Upgraded to yakkety on 2016-08-28 (28 days ago) UserGroups: nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH enp0s17 ethernet connected/org/freedesktop/NetworkManager/Devices/1 Wired connection 1 0a821d1a-0aa1-33eb-a8e8-d691b38de9f0 /org/freedesktop/NetworkManager/ActiveConnection/0 wlp8s9 wifi connected/org/freedesktop/NetworkManager/Devices/3 FREE2U2.4WI-FI 6784f99c-73d0-4d8b-8fb0-d39d3ef01313 /org/freedesktop/NetworkManager/ActiveConnection/1 enp0s18 ethernet unavailable /org/freedesktop/NetworkManager/Devices/0 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1627421/+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 1627421] [NEW] NetworkManager crashed with SIGSEGV in dhcp6_start()
Public bug reported: miked@free-yak:~$ lsb_release -rd Description:Ubuntu Yakkety Yak (development branch) Release:16.10 miked@free-yak:~$ apt-cache policy NetworkManager N: Unable to locate package NetworkManager miked@free-yak:~$ apt-cache policy nm_device_update_dynamic_ip_setup N: Unable to locate package nm_device_update_dynamic_ip_setup miked@free-yak:~$ I don't know what was expected to happen, this crashed happened. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.2-0ubuntu10 ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7 Uname: Linux 4.8.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Sat Sep 24 20:06:02 2016 ExecutablePath: /usr/sbin/NetworkManager IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-03 (174 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IpRoute: default via 10.0.0.1 dev enp0s17 proto static metric 100 default via 10.0.0.1 dev wlp8s9 proto static metric 600 10.0.0.0/24 dev enp0s17 proto kernel scope link src 10.0.0.84 metric 100 10.0.0.0/24 dev wlp8s9 proto kernel scope link src 10.0.0.218 metric 600 169.254.0.0/16 dev enp0s17 scope link metric 1000 NetworkManager.conf: [main] plugins=ifupdown,keyfile,ofono [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcCmdline: /usr/sbin/NetworkManager --no-daemon ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Signal: 11 SourcePackage: network-manager StacktraceTop: ?? () nm_device_update_dynamic_ip_setup () ?? () nm_device_set_carrier () ?? () Title: NetworkManager crashed with SIGSEGV in nm_device_update_dynamic_ip_setup() UpgradeStatus: Upgraded to yakkety on 2016-08-28 (28 days ago) UserGroups: nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH enp0s17 ethernet connected/org/freedesktop/NetworkManager/Devices/1 Wired connection 1 0a821d1a-0aa1-33eb-a8e8-d691b38de9f0 /org/freedesktop/NetworkManager/ActiveConnection/0 wlp8s9 wifi connected/org/freedesktop/NetworkManager/Devices/3 FREE2U2.4WI-FI 6784f99c-73d0-4d8b-8fb0-d39d3ef01313 /org/freedesktop/NetworkManager/ActiveConnection/1 enp0s18 ethernet unavailable /org/freedesktop/NetworkManager/Devices/0 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Medium Status: New ** Tags: amd64 apport-crash yakkety ** Information type changed from Private to Public -- 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/1627421 Title: NetworkManager crashed with SIGSEGV in dhcp6_start() Status in network-manager package in Ubuntu: New Bug description: miked@free-yak:~$ lsb_release -rd Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 miked@free-yak:~$ apt-cache policy NetworkManager N: Unable to locate package NetworkManager miked@free-yak:~$ apt-cache policy nm_device_update_dynamic_ip_setup N: Unable to locate package nm_device_update_dynamic_ip_setup miked@free-yak:~$ I don't know what was expected to happen, this crashed happened. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.2-0ubuntu10 ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7 Uname: Linux 4.8.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Sat Sep 24 20:06:02 2016 ExecutablePath: /usr/sbin/NetworkManager IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-03 (174 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IpRoute: default via 10.0.0.1 dev enp0s17 proto static metric 100 default via 10.0.0.1 dev wlp8s9 proto static metric 600 10.0.0.0/24 dev enp0s17 proto kernel scope link src 10.0.0.84 metric 100 10.0.0.0/24 dev wlp8s9 proto ker
[Touch-packages] [Bug 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)
Hi guys, I am experiencing the same issue from my Plantronics Backbeat Go 2 bluetooth headphones (PLT_BBTGO2). The headphones pair correctly, but then disconnect 2 seconds afterwards. The headphones are confirmed to be pairing and working correctly on Nexus 5 stock Android, and Windows 10. I am running Xenial: Ubuntu 16.04.1 LTS with kernel 4.4.0-38-generic Prior to this I was running 12.04 LTS and they worked correctly. My pulseaudio log shows (among less relevant stuff): Sep 25 12:51:13 kathyreid-N76VZ pulseaudio[13654]: [pulseaudio] backend-native.c: connect(): Function not implemented Sep 25 12:51:13 kathyreid-N76VZ pulseaudio[13654]: [pulseaudio] volume.c: Assertion 'pa_channels_valid(channels)' failed at pulse/volume.c:74, function pa_cvolume_set(). Aborting. The pulseaudio bluetooth module is installed. ofono is installed (I installed it to try and get it working) I am NOT using blueant. Before installing Joakim's PPA is there anything you'd like me to test / get logs of? I'd be very happy to test Joakim's PPA / provide any other debug information that may be of assistance. (A huge thanks to all the people in this thread - this is excellent debugging information). Kind regards, Kathy -- 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/1574324 Title: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?) Status in pulseaudio package in Ubuntu: In Progress Bug description: When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04 pulseaudio crashes, this does *NOT* happen with a Jambox which leads me to believe it's an intermittent problem with some hardware. This did not happen on Ubuntu 15.10 (which was an upgrade of 15.04). Ubuntu Release: Description: Ubuntu 16.04 LTS Release: 16.04 Pulseaudio Version: pulseaudio: Installed: 1:8.0-0ubuntu3 Candidate: 1:8.0-0ubuntu3 Version table: *** 1:8.0-0ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status Device info: [bluetooth]# info 44:5E:F3:B4:07:29 Device 44:5E:F3:B4:07:29 Name: BlueBuds X Alias: BlueBuds X Class: 0x240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: Unknown (80ff--1000-8000-00805f9b34fb) I have also attached a debug dump of Pulseaudio when attempting to connect to the headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324/+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 1627310] Re: Guest session fails to log out
Tested with Ubuntu MATE, and the guest session works fine there, so the issue is probably not caused by lightdm. Possibly the Xubuntu specific parts of lightdm-gtk-greeter should be looked at. -- 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/1627310 Title: Guest session fails to log out Status in lightdm package in Ubuntu: Confirmed Status in xfce4-session package in Ubuntu: Confirmed Bug description: Vanilla Xubuntu install. When logging out from the guest session, everything is closed and the desktop wallpaper is the only thing that remains. The user is never returned to the login screen. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xfce4-session 4.12.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Uname: Linux 4.8.0-11-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Sep 24 09:18:31 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921) SourcePackage: xfce4-session UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921) Package: lightdm 1.19.4-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Tags: yakkety Uname: Linux 4.8.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1627310/+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 1627304] Re: User locking problems - guest login crashing
Tested with Ubuntu MATE, and the guest session works fine there, so the issue is probably not caused by lightdm. -- 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/1627304 Title: User locking problems - guest login crashing Status in gnome-session package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in lightdm-gtk-greeter package in Ubuntu: Confirmed Status in unity-greeter package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: Confirmed Bug description: Vanilla Ubuntu install. Lock user - login to guest account, desktop crashes. Ctrl+Alt+F7 allows you to resume user after unlocking. Add new user - am able to switch between locked users properly. Can logout of one user and be able to resume other locked session. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 24 13:38:09 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1627304/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421923] Re: No notifications for new mails
So will IMAP IDLE work when this bug is fixed or is there no hope of it working for Ubuntu Touch given the lifecycle policy. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1421923 Title: No notifications for new mails Status in Online Accounts: Account plugins: New Status in Canonical System Image: In Progress Status in Dekko: In Progress Status in account-plugins package in Ubuntu: In Progress Status in account-polld package in Ubuntu: In Progress Bug description: Hi! In the BQ E4.5 Ubuntu Edition, I'm not getting notificactions for new mails. Testing (by example) 1. Kill Dekko. 2. Send you an email. 3. Open Dekko. 4. Change quickly to another app before Dekko starts. 5. Bug: No notification 6. Go to Dekko: You'll see your new mail. FYI as improvement, for me, in Dekko is not clear if Dekko checks the mail after X minutes or is a push notification. Thanks in advance! To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1421923/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1504254] Re: IdleAction=suspend specified in logind.conf must systematically be inhibited during user interaction
IdleAction=suspend DOES NOT WORK AT ALL in systemd version 231-6git1 from Ubuntu 16.10 Yakkety Beta. -- 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/1504254 Title: IdleAction=suspend specified in logind.conf must systematically be inhibited during user interaction Status in systemd package in Ubuntu: New Bug description: I want my computer to suspend when there is NO opened user session. So, I have activated following lines inside '/etc/systemd/logind.conf' : IdleAction=suspend IdleActionSec=15min - Systematically , under Ubuntu Vivid (15.04), this works correctly : During user interaction, the computer does NOT automatically suspend, but stays continuously alive. Once all users have closed their session, the computer automatically suspends after 15 min. - But systematically , under Ubuntu Wily (15.10 beta2), the computer automatically suspends after 15 min EVEN during user interaction. Hitting the keyboard makes the computer resume without data loss, but this is still annoying. In fact, 'IdleAction=suspend' specified in '/etc/systemd/logind.conf' must systematically be inhibited during user interaction. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-14-generic 4.2.0-14.16 ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2 Uname: Linux 4.2.0-14-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: z_admin1665 F pulseaudio /dev/snd/controlC1: z_admin1665 F pulseaudio CurrentDesktop: GNOME Date: Thu Oct 8 19:26:59 2015 HibernationDevice: RESUME=UUID=ccecc437-66d2-4e39-ac56-76ab11e18140 InstallationDate: Installed on 2015-09-27 (10 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150924) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-14-generic root=UUID=a5c156d8-eac3-47fa-835c-b2c4ebda969d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-14-generic N/A linux-backports-modules-4.2.0-14-generic N/A linux-firmware1.149 RfKill: SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/07/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1504254/+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 1467930] Re: 0cf3:3004 bluetooth not working atheros 10
*** This bug is a duplicate of bug 1451689 *** https://bugs.launchpad.net/bugs/1451689 ** Information type changed from Public to Public Security -- 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/1467930 Title: 0cf3:3004 bluetooth not working atheros 10 Status in bluez package in Ubuntu: Confirmed Bug description: see original bug. reported this because the bug also affects me and on apport-collect launchpad told me to create a new bug report and mark it as clone. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jun 23 14:31:15 2015 InstallationDate: Installed on 2015-06-19 (3 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) InterestingModules: btusb bluetooth MachineType: Micro-Star International Co., Ltd. GT72 2QE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic root=UUID=4fabaada-02c5-4230-a634-0b88cf228b5f ro quiet splash SourcePackage: bluez UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1781IMS.10H dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1781 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10H:bd11/21/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: GT72 2QE dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. hciconfig: rfkill: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1467930/+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 1627252] Re: Recognize album artwork with "Album title.supported_extension" filename
Whilst I can only speak for myself, I know that Fiio's music players support such a format for album artwork, and back when I used to use Microsoft Windows-based operating systems exclusively, a number of programs also supported album artwork in this format. We also have Sony Blu-Ray Disk players and various-brand televisions that detect album artwork based on this filename format. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to thumbnailer in Ubuntu. https://bugs.launchpad.net/bugs/1627252 Title: Recognize album artwork with "Album title.supported_extension" filename Status in Ubuntu Music App: Invalid Status in mediascanner2 package in Ubuntu: New Status in thumbnailer package in Ubuntu: New Bug description: At this time, Music currently supports the following filenames for local album artwork (i.e. album artwork which is stored locally in the same folder as the music for which it should be associated): * cover * album * albumart * .folder * folder These filenames must have one of the following extensions: * jpeg * jpg * png However most applications and programs also support (provided it matches the folder name and metadata album title exactly): Album Title.supported_extension I propose that "Album Title.supported_extension" be added to the list of recognized filenames for album artwork, to bring Music into line with most other music players... To manage notifications about this bug go to: https://bugs.launchpad.net/music-app/+bug/1627252/+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 1627252] Re: Recognize album artwork with "Album title.supported_extension" filename
Do you have any examples for music players that recognise .? (I'm not aware of any at this point.) The existing list of file names exists because they are widely used by various players, so we are just following established precedent here. We can look at supporting this, but I'd prefer to do this only if there are popular music players that already support this. If not, I don't think we'd be doing the world a favour by adding yet another file name convention to the already messy situation. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to thumbnailer in Ubuntu. https://bugs.launchpad.net/bugs/1627252 Title: Recognize album artwork with "Album title.supported_extension" filename Status in Ubuntu Music App: Invalid Status in mediascanner2 package in Ubuntu: New Status in thumbnailer package in Ubuntu: New Bug description: At this time, Music currently supports the following filenames for local album artwork (i.e. album artwork which is stored locally in the same folder as the music for which it should be associated): * cover * album * albumart * .folder * folder These filenames must have one of the following extensions: * jpeg * jpg * png However most applications and programs also support (provided it matches the folder name and metadata album title exactly): Album Title.supported_extension I propose that "Album Title.supported_extension" be added to the list of recognized filenames for album artwork, to bring Music into line with most other music players... To manage notifications about this bug go to: https://bugs.launchpad.net/music-app/+bug/1627252/+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 1627252] Re: Recognize album artwork with "Album title.supported_extension" filename
** Also affects: mediascanner2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediascanner2 in Ubuntu. https://bugs.launchpad.net/bugs/1627252 Title: Recognize album artwork with "Album title.supported_extension" filename Status in Ubuntu Music App: Invalid Status in mediascanner2 package in Ubuntu: New Status in thumbnailer package in Ubuntu: New Bug description: At this time, Music currently supports the following filenames for local album artwork (i.e. album artwork which is stored locally in the same folder as the music for which it should be associated): * cover * album * albumart * .folder * folder These filenames must have one of the following extensions: * jpeg * jpg * png However most applications and programs also support (provided it matches the folder name and metadata album title exactly): Album Title.supported_extension I propose that "Album Title.supported_extension" be added to the list of recognized filenames for album artwork, to bring Music into line with most other music players... To manage notifications about this bug go to: https://bugs.launchpad.net/music-app/+bug/1627252/+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 1543352] Re: inet6 dhcp doesn't wait for link-local address to leave tentative - dhclient fails to bind
@jacob11, I understand your frustration. All I can do is fix the bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1543352 Title: inet6 dhcp doesn't wait for link-local address to leave tentative - dhclient fails to bind Status in ifupdown package in Ubuntu: Triaged Bug description: = Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 = With an /etc/network/interfaces file containing: auto eno16780032 iface eno16780032 inet dhcp iface eno16780032 inet6 dhcp On boot, ifup starts 'dhclient -6' before the link local address has completed Duplicate Address Discovery (the address is marked 'tentative'). In turn, dhclient reports 'Can't bind to dhcp address: Cannot assign requested address', and fails almost immediately. It would seem that either wait-for-ll6.sh should wait for the link local address to come up AND stop being tentative, or the dhcp method for inet6 should call settle-dad.sh after wait-for-ll6? This is partly a race condition, so on slower devices the dad may complete by the time dhclient has got started, however I can regularly reproduce this on a virtual machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1543352/+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 1626883] Re: libssl 1.0.2g-1ubuntu4.4 and 1.0.1f-1ubuntu2.20 cause PHP SSL cert validation to segfault
** No longer affects: openssl (Ubuntu Yakkety) ** Changed in: openssl (Ubuntu) Status: Invalid => Fix Released ** Tags added: regression-update -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1626883 Title: libssl 1.0.2g-1ubuntu4.4 and 1.0.1f-1ubuntu2.20 cause PHP SSL cert validation to segfault Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Precise: Fix Released Status in openssl source package in Trusty: Fix Released Status in openssl source package in Xenial: Fix Released Bug description: Last night unattended-upgrades upgraded the openssl packages (libssl1.0.0, libssl-dev, openssl) from version 1.0.2g-1ubuntu4.1 to version 1.0.2g-1ubuntu4.4 on a CI build server. Then everything that used PHP to connect to a HTTPS site started crashing when verifying the server cert. Like this: ``` jenkins@ubuntutemplate:/var/lib/jenkins/workspace/imt-erp-e2e-flaky/webshop/vagrant/wordpress$ DATABASE_DATABASE=wordpressmastere2e catchsegv wp plugin install --force --activate wp-cfm Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; WP_Import has a deprecated constructor in /var/lib/jenkins/workspace/imt-erp-e2e-flaky/webshop /vagrant/wordpress/wp-content/plugins/wordpress-importer/wordpress-importer.php on line 38 Notice: Undefined offset: 4 in phar:///usr/local/bin/wp/php/WP_CLI/DocParser.php on line 124 Segmentation fault (core dumped) *** Segmentation fault Register dump: RAX: RBX: 0001 RCX: RDX: 000c RSI: 55665071af59 RDI: RBP: 556650a49e4e R8 : 556652364720 R9 : R10: R11: 7fdb3c081730 R12: 55665071af59 R13: 000c R14: R15: 7fdb39418cf0 RSP: 7ffc4bad7a08 RIP: 7fdb3bf77d16 EFLAGS: 00010293 CS: 0033 FS: GS: Trap: 000e Error: 0004 OldMask: CR2: FPUCW: 027f FPUSW: TAG: RIP: RDP: ST(0) ST(1) ST(2) ST(3) ST(4) ST(5) ST(6) ST(7) mxcsr: 1fa0 XMM0: XMM1: XMM2: XMM3: XMM4: XMM5: XMM6: XMM7: XMM8: XMM9: XMM10: XMM11: XMM12: XMM13: XMM14: XMM15: Backtrace: /lib/x86_64-linux-gnu/libc.so.6(strlen+0x26)[0x7fdb3bf77d16] php(add_assoc_string_ex+0x32)[0x556650677b12] php(zif_openssl_x509_parse+0x17c)[0x5566505312ec] php(dtrace_execute_internal+0x2a)[0x556650664b3a] php(+0x2e37e0)[0x5566506f97e0] php(execute_ex+0x1b)[0x5566506b4e2b] php(dtrace_execute_ex+0xb1)[0x5566506649d1] php(+0x2e391d)[0x5566506f991d] php(execute_ex+0x1b)[0x5566506b4e2b] php(dtrace_execute_ex+0xb1)[0x5566506649d1] php(+0x2e391d)[0x5566506f991d] php(execute_ex+0x1b)[0x5566506b4e2b] php(dtrace_execute_ex+0xb1)[0x5566506649d1] php(+0x2e391d)[0x5566506f991d] php(execute_ex+0x1b)[0x5566506b4e2b] php(dtrace_execute_ex+0xb1)[0x5566506649d1] php(+0x2e391d)[0x5566506f991d] php(execute_ex+0x1b)[0x5566506b4e2b] php(dtrace_execute_ex+0xb1)[0x5566506649d1] php(+0x2e391d)[0x5566506f991d] php(execute_ex+0x1b)[0x5566506b4e2b] php(dtrace_execute_ex+0xb1)[0x5566506649d1] php(+0x2e391d)[0x5566506f991d] php(execute_ex+0x1b)[0x5566506b4e2b] php(dtrace_execute_ex+0xb1)[0x5566506649d1] php(+0x2e391d)[0x5566506f991d] php(execute_ex+0x1b)[0x5566506b4e2b] php(dtrace_execute_ex+0xb1)[0x5566506649d1] php(+0x2e391d)[0x5566506f991d] php(execute_ex+0x1b)[0x5566506b4e2b] php(dtrace_execute_ex+0xb1)[0x5566506649d1] php(+0x2e391d)[0x5566506f991d] php(execute_ex+0x1b)[0x5566506b4e2b] php(dtrace_execute_ex+0xb1)[0x5566506649d1] php(zend_call_function+0x749)[0x55665039] php(zif_call_user_func+0xb5)[0x5566505b39d5] php(dtrace_execute_internal+0x2a)[0x556650664b3a] php(+0x2e37e0)[0x5566506f97e0] php(execute_ex+0x1b)[0x5566506b4e2b] php(dtrace_execute_ex+0xb1)[0x5566506649d1] php(zend_call_function+0x749)[0x55665039] php(zif_call_user_func+0xb5)[0x
[Touch-packages] [Bug 1627395] Re: Skip zenity guest warning dialog in MATE
** Branch linked: lp:~gunnarhj/lightdm/lp-1627395 -- 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/1627395 Title: Skip zenity guest warning dialog in MATE Status in ubuntu-mate: New Status in lightdm package in Ubuntu: In Progress Bug description: When you enter a guest session, a zenity warning dialog is started to explain the nature of the guest session. In Ubuntu MATE a welcome window is shown when a regular user logs in for the first time. When you enter a guest session, an adapted version of that welcome window is shown, which essentially provides the same information as the zenity dialog and makes the latter redundant. Hence the zenity dialog should not be shown when you enter a guest session in Ubuntu MATE. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1627395/+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 1522675] Re: Can't drop privileges for downloading : _apt user not allowed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apt (Ubuntu) Status: New => Confirmed -- 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/1522675 Title: Can't drop privileges for downloading : _apt user not allowed Status in apt package in Ubuntu: Confirmed Status in dpkg package in Ubuntu: Confirmed Status in synaptic package in Debian: New Bug description: Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+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 1627395] [NEW] Skip zenity guest warning dialog in MATE
Public bug reported: When you enter a guest session, a zenity warning dialog is started to explain the nature of the guest session. In Ubuntu MATE a welcome window is shown when a regular user logs in for the first time. When you enter a guest session, an adapted version of that welcome window is shown, which essentially provides the same information as the zenity dialog and makes the latter redundant. Hence the zenity dialog should not be shown when you enter a guest session in Ubuntu MATE. ** Affects: ubuntu-mate Importance: Undecided Status: New ** Affects: lightdm (Ubuntu) Importance: Medium Assignee: Gunnar Hjalmarsson (gunnarhj) Status: In Progress ** Also affects: ubuntu-mate Importance: Undecided Status: New -- 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/1627395 Title: Skip zenity guest warning dialog in MATE Status in ubuntu-mate: New Status in lightdm package in Ubuntu: In Progress Bug description: When you enter a guest session, a zenity warning dialog is started to explain the nature of the guest session. In Ubuntu MATE a welcome window is shown when a regular user logs in for the first time. When you enter a guest session, an adapted version of that welcome window is shown, which essentially provides the same information as the zenity dialog and makes the latter redundant. Hence the zenity dialog should not be shown when you enter a guest session in Ubuntu MATE. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1627395/+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 1610499] Re: /bin/kill in ubuntu16.04 has bug in killing process group
I met exactly the same problem when using hadoop in ubuntu 16.04, and
copied /bin/kill in ubuntu14.04 to ubuntu16.04 following Dongdong88's
suggestion. However it renders /bin/kill simply unusable due to the lack
of shared library (the built-in "kill" still works though). I created a
link file libprocps.so.3 in /lib/x86_64-linux-gnu and targeted it to
libprocps.so.4.0.0. But I am not sure if that will make the issue come
back again. We may try copying and use libprocps.so.3.0.0 in ubuntu16.04
if so. I haven't got a chance to test it yet.
--
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/1610499
Title:
/bin/kill in ubuntu16.04 has bug in killing process group
Status in alsa-driver package in Ubuntu:
Confirmed
Bug description:
when i run hadoop in ubuntu 16.04, ssh will exit, all process which
belong to hadoop user will be killed ,through debug ,i found the
/bin/kill in ubuntu16.04 has a bug , it has bug in killing process
group .
Ubuntu version is:
Description:Ubuntu 16.04.1 LTS
Release:16.04
(1)The way to repeat this bug
It is easy to repeat this bug , run “/bin/kill -15 -12345” or any like
“/bin/kill -15 -1” in ubuntu16.04 , it will kill all the process .
(2)Cause analysis
The code of /bin/kill in ubuntu16.04 come from procps-3.3.10 , when I run
“/bin/kill -15 -1” , it actually send signal 15 to -1 ,
-1 mean it will kill all the process .
(3)The bug in procps-3.3.10/skill.c ,I think the code "pid =
(long)('0' - optopt) " is not right .
static void __attribute__ ((__noreturn__)) kill_main(int argc, char
**argv)
{
case '?':
if (!isdigit(optopt)) {
xwarnx(_("invalid argument %c"), optopt);
kill_usage(stderr);
} else {
/* Special case for signal digit negative
* PIDs */
pid = (long)('0' - optopt);
if (kill((pid_t)pid, signo) != 0)
exitvalue = EXIT_FAILURE;
exit(exitvalue);
}
loop=0;
}
(4) the cause
sometimes when the resource is tight or a hadoop container lost connection
in sometime, the nodemanager will kill this container , it send a signal to
kill this jvm process ,it is a normal behavior for hadoop to kill a task and
then reexecute this task. but with this kill bug ,it kill all the process
belong to a hadoop user .
(5) The way to workaround
I copy /bin/kill in ubuntu14.04 to override /bin/kill in ubuntu16.04, it is
ok in this way . I also think it is better to ask procps-3.3.10 maintainer to
solve their bug,but i don't know how to contact them .
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1610499/+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 1223592] Re: No sound at all because output options were stuck in (maybe) previous plugged device
(attaching alsamixer card-views, per last comment) ** Attachment added: "card-0_vs_card-1_top-vs-bottom.png" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1223592/+attachment/4748140/+files/card-0_vs_card-1_top-vs-bottom.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/1223592 Title: No sound at all because output options were stuck in (maybe) previous plugged device Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm not sure this is a pulseaudio problem or a Ubuntu System Settings one. Since yesterday I noticed there was no sound at all, and restarting pulseaudio and the computer didn't do the trick. I reported this problem to a friend and he suggested to look closely at the output options in the Sound Settings, and although there was no headset or headphone plugged in and the "Built-in Audio" was the only device displayed, the "Mode" options in "Settings for Speakers" were HDMI ones, not the Analog that should be there for my built-in device. After seeing that, I only clicked the combobox and it immediately reloaded its options with the Analog ones, the sound started working again in the moment that happened. I'm not sure how to trigger that behaviour. At the moment my notebook is in a minidock, with two monitors connected to it via DVI. I used my computer connected to a TV a few days ago, then using an HDMI cable, and that was about all the contact my machine had to HDMI. I haven't tested sound after that, only noticed yesterday it wasn't working so probably never worked since then. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pulseaudio 1:4.0-0ubuntu2+build1 ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0 Uname: Linux 3.11.0-5-generic i686 ApportVersion: 2.12.1-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ursula18183 F pulseaudio /dev/snd/pcmC0D0c: ursula18183 F...m pulseaudio /dev/snd/pcmC0D0p: ursula18183 F...m pulseaudio Date: Tue Sep 10 19:52:49 2013 InstallationDate: Installed on 2013-05-27 (106 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 (20130213) MarkForUpload: True SourcePackage: pulseaudio UpgradeStatus: Upgraded to saucy on 2013-07-29 (43 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET56WW (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 4286CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET56WW(1.26):bd12/01/2011:svnLENOVO:pn4286CTO:pvrThinkPadX220:rvnLENOVO:rn4286CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4286CTO dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1223592/+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 1223592] Re: No sound at all because output options were stuck in (maybe) previous plugged device
Sorry, I failed to mention in comment #9 that the actual *problem* is I no longer hear any audio, and no longer have microphone access. Another screenshot attached (of sound settings UI - upon initial installation, this was non-empty). Here's my current output for `grep "Codec:" /proc/asound/card*/codec*` /proc/asound/card0/codec#0:Codec: Intel Broadwell HDMI /proc/asound/card1/codec#0:Codec: Realtek ALC286 (per https://wiki.ubuntu.com/Audio/HDAGeneric from https://wiki.ubuntu.com/DebuggingSoundProblems) Also, `alsamixer --card=1` shows me audio level bars. Where as `alsamixer` (default: card 0) shows me nothing~ish (zero-height bar- toggles) - also attahed screenshot ** Attachment added: "Empty gnome sound settings UI" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1223592/+attachment/4748139/+files/empty-sound-settings.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/1223592 Title: No sound at all because output options were stuck in (maybe) previous plugged device Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm not sure this is a pulseaudio problem or a Ubuntu System Settings one. Since yesterday I noticed there was no sound at all, and restarting pulseaudio and the computer didn't do the trick. I reported this problem to a friend and he suggested to look closely at the output options in the Sound Settings, and although there was no headset or headphone plugged in and the "Built-in Audio" was the only device displayed, the "Mode" options in "Settings for Speakers" were HDMI ones, not the Analog that should be there for my built-in device. After seeing that, I only clicked the combobox and it immediately reloaded its options with the Analog ones, the sound started working again in the moment that happened. I'm not sure how to trigger that behaviour. At the moment my notebook is in a minidock, with two monitors connected to it via DVI. I used my computer connected to a TV a few days ago, then using an HDMI cable, and that was about all the contact my machine had to HDMI. I haven't tested sound after that, only noticed yesterday it wasn't working so probably never worked since then. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pulseaudio 1:4.0-0ubuntu2+build1 ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0 Uname: Linux 3.11.0-5-generic i686 ApportVersion: 2.12.1-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ursula18183 F pulseaudio /dev/snd/pcmC0D0c: ursula18183 F...m pulseaudio /dev/snd/pcmC0D0p: ursula18183 F...m pulseaudio Date: Tue Sep 10 19:52:49 2013 InstallationDate: Installed on 2013-05-27 (106 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 (20130213) MarkForUpload: True SourcePackage: pulseaudio UpgradeStatus: Upgraded to saucy on 2013-07-29 (43 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET56WW (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 4286CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET56WW(1.26):bd12/01/2011:svnLENOVO:pn4286CTO:pvrThinkPadX220:rvnLENOVO:rn4286CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4286CTO dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1223592/+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 1626808] Re: Unable to log in from bq Aquaris tablet
Hi Rodney I have wiped the entire system and flashed the device with a new installation I am now able to log in to Ubuntu One It's hard to understand what that problem was, but it is not a problem for me now thank you for contacting me, Mark On Sat, Sep 24, 2016 at 5:53 AM, Rodney Dawes <1626...@bugs.launchpad.net> wrote: > Can you attach before/after screenshots? You should be able to take a > screenshot by pressing both Vol Up+Vol Dn at the same time. You should > be able to attach them to the bug via the browser on the M10 or transfer > them via USB to a PC for attaching to the bug. > > If you attach with USB and with developer mode enabled, you can use the > "phablet-shell" tool on Ubuntu to shell in to the tablet, and watch > /home/phablet/.cache/upstart/dbus.log while trying to log in. There may > be some indication of what's going on printed to this file while > attempting to log in. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1626808 > > Title: > Unable to log in from bq Aquaris tablet > > Status in Canonical SSO provider: > New > Status in ubuntuone-credentials package in Ubuntu: > New > > Bug description: > Hi > > I have five Aquaris tablets I am installing some new products I have > built onto. > > On one tablet, when I try to log in to the Ubuntu One so I can get the > terminal app, I enter my email and password (correct) to log in, but I > am not logged in and the terminal app does not download. > > Without the terminal app installed I cannot run any diagnostics or get > any information about what is going wrong. > > This setup, where terminal is not on the Tablet OS by default, totally > SUCKS. > > I need support urgently. > > I cannot provide log files to you or anything else. Presumably the > Ubuntu Web web site logs will say that I am trying to log in from a > Tablet device. I wish I had some logs myself... > > Mark Anson > > To manage notifications about this bug go to: > https://bugs.launchpad.net/canonical-identity-provider/+ > bug/1626808/+subscriptions > -- Mobile 0423 799 972 -- 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/1626808 Title: Unable to log in from bq Aquaris tablet Status in Canonical SSO provider: New Status in ubuntuone-credentials package in Ubuntu: New Bug description: Hi I have five Aquaris tablets I am installing some new products I have built onto. On one tablet, when I try to log in to the Ubuntu One so I can get the terminal app, I enter my email and password (correct) to log in, but I am not logged in and the terminal app does not download. Without the terminal app installed I cannot run any diagnostics or get any information about what is going wrong. This setup, where terminal is not on the Tablet OS by default, totally SUCKS. I need support urgently. I cannot provide log files to you or anything else. Presumably the Ubuntu Web web site logs will say that I am trying to log in from a Tablet device. I wish I had some logs myself... Mark Anson To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-identity-provider/+bug/1626808/+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 1168742] Re: [udev] Disks are not unmounted when physical eject button is used
I can confirm this problem still exists with Xubuntu 16.04 x64. I hope it's fixed someday. It's difficult to win Windows users over when common things like this don't work, it's very confusing for them and they just want me to reinstall Windows :( -- 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/1168742 Title: [udev] Disks are not unmounted when physical eject button is used Status in systemd: Confirmed Status in systemd package in Ubuntu: Fix Released Bug description: In 13.04, disks (DVDs, CDS) are not unmounted when ejected via the hardware button on the drive. After ejecting disks via the hardware button, an entry for the disk still shows up in the file manager, and shows when I run df. If I do a soft eject (ie from the right click menu from the icon on the launcher), however, everything works properly. Just as a note, as per https://wiki.ubuntu.com/Bugs/FindRightPackage#Hardware_Malfunctions, I attempted to report this using ubuntu-bug storage, however there is not an option dealing with unmounting devices, and clicking other tells you that you should run ubuntu-bug again with a specific package name. In an attempt to get this to a semi-relevant audience, I ended up just saying that a disk wasn't auto-mounted, clicking through the next few popups, and ended up here. If this isn't the right place to report this bug, I apologize. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-17-generic 3.8.0-17.27 ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6 Uname: Linux 3.8.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chris 1590 F pulseaudio /dev/snd/controlC0: chris 1590 F pulseaudio Date: Sat Apr 13 12:54:33 2013 GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HibernationDevice: RESUME=UUID=bd2c881c-7bf8-4996-8b05-7efbd9852333 HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2013-03-26 (18 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130325) MachineType: ASUSTeK COMPUTER INC. G55VW MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-17-generic root=UUID=f44b6481-8a06-4cf1-a494-0e4c233720c8 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.8.0-17-generic N/A linux-backports-modules-3.8.0-17-generic N/A linux-firmware1.105 SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 12:54:42.343: The udisks-daemon is running (name-owner :1.39). UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/05/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G55VW.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G55VW 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.:bvrG55VW.206:bd04/05/2012:svnASUSTeKCOMPUTERINC.:pnG55VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG55VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: G55VW dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1168742/+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 1223592] Re: No sound at all because output options were stuck in (maybe) previous plugged device
disclaimer: I'm trying to confirm if this affects me (so, please chime in if someone reading this can point me elsewhere or confirm)... I found on initial install - of Ubuntu 16.04, on Samsung ATIV 9, 12inch laptop - that audio/mic. worked perfectly without issue. Now, since multiple boots and updates, I am finding that volume up/down icon (in gnome 3's grey overlay -- attached screenshot) indicates "HDMI / DisplayPort" I *do* have a micro display port on the side of this laptop (I believe called HDMI "type d"), but I haven't once plugged into since purchasing the laptop. ** Attachment added: "Gnomeshell overlay indicating that my volume controls are interacting with "HDMI / DisplayPort"" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1223592/+attachment/4748138/+files/Screenshot_2016-09-24%2017-49-28_Indication-of-HDMI-port-Intercepting.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/1223592 Title: No sound at all because output options were stuck in (maybe) previous plugged device Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm not sure this is a pulseaudio problem or a Ubuntu System Settings one. Since yesterday I noticed there was no sound at all, and restarting pulseaudio and the computer didn't do the trick. I reported this problem to a friend and he suggested to look closely at the output options in the Sound Settings, and although there was no headset or headphone plugged in and the "Built-in Audio" was the only device displayed, the "Mode" options in "Settings for Speakers" were HDMI ones, not the Analog that should be there for my built-in device. After seeing that, I only clicked the combobox and it immediately reloaded its options with the Analog ones, the sound started working again in the moment that happened. I'm not sure how to trigger that behaviour. At the moment my notebook is in a minidock, with two monitors connected to it via DVI. I used my computer connected to a TV a few days ago, then using an HDMI cable, and that was about all the contact my machine had to HDMI. I haven't tested sound after that, only noticed yesterday it wasn't working so probably never worked since then. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pulseaudio 1:4.0-0ubuntu2+build1 ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0 Uname: Linux 3.11.0-5-generic i686 ApportVersion: 2.12.1-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ursula18183 F pulseaudio /dev/snd/pcmC0D0c: ursula18183 F...m pulseaudio /dev/snd/pcmC0D0p: ursula18183 F...m pulseaudio Date: Tue Sep 10 19:52:49 2013 InstallationDate: Installed on 2013-05-27 (106 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 (20130213) MarkForUpload: True SourcePackage: pulseaudio UpgradeStatus: Upgraded to saucy on 2013-07-29 (43 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET56WW (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 4286CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET56WW(1.26):bd12/01/2011:svnLENOVO:pn4286CTO:pvrThinkPadX220:rvnLENOVO:rn4286CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4286CTO dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1223592/+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 1627252] Re: Recognize album artwork with "Album title.supported_extension" filename
Thank you for taking the time to report this bug and helping to make Ubuntu better. The album art is done via the thumbnailer service, so I had added them to the bug report and set the music-app as invalid. Others note this bug is a feature request, original discussion was bug 1607531. ** Also affects: thumbnailer (Ubuntu) Importance: Undecided Status: New ** Changed in: music-app Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to thumbnailer in Ubuntu. https://bugs.launchpad.net/bugs/1627252 Title: Recognize album artwork with "Album title.supported_extension" filename Status in Ubuntu Music App: Invalid Status in thumbnailer package in Ubuntu: New Bug description: At this time, Music currently supports the following filenames for local album artwork (i.e. album artwork which is stored locally in the same folder as the music for which it should be associated): * cover * album * albumart * .folder * folder These filenames must have one of the following extensions: * jpeg * jpg * png However most applications and programs also support (provided it matches the folder name and metadata album title exactly): Album Title.supported_extension I propose that "Album Title.supported_extension" be added to the list of recognized filenames for album artwork, to bring Music into line with most other music players... To manage notifications about this bug go to: https://bugs.launchpad.net/music-app/+bug/1627252/+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 1607531] Re: Music ignores local album artwork.
The bug being marked as invalid across all affected projects, is effectively 'deleted'. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to thumbnailer in Ubuntu. https://bugs.launchpad.net/bugs/1607531 Title: Music ignores local album artwork. Status in Ubuntu Music App: Invalid Status in thumbnailer package in Ubuntu: Invalid Bug description: When using "Music", local album artwork is ignored, seemingly in favor of online album artwork, which is frequently incorrect. This appears to be a different issue to https://bugs.launchpad.net/thumbnailer/+bug/1372000 , because https://bugs.launchpad.net/thumbnailer/+bug/1372000 is apparently "fixed" and I still experience this issue. -- Reproduce: - Copy music to your Ubuntu mobile device, ensuring that each folder contains appropriately-named album artwork (in my case, exactly the same name as the album and the folder in which the music is contained). - Launch/open Music, browse your library and playback music. Result: - Most tracks are shown with no or incorrect album artwork. Expectation: - That Music would utilize or otherwise prioritize local album artwork. -- Music: 2.4.1003 bq Aquaris E5 HD Ubuntu Edition: * OS build number: OTA-12 * Ubuntu Image part: 20160708 * Ubuntu build description: Ubuntu 15.04 - armhf (20160708-091336) * Device Image part: 20160606-540a47f * Device build description: VEGETA01A-S23A_BQ_L100EN_2014_160708 * Customization Image part: 20160701-981-38-14 To manage notifications about this bug go to: https://bugs.launchpad.net/music-app/+bug/1607531/+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 1511074] Re: camera constantly refocuses when recording a video
It is urgent to fix this bug because it is a convenient way to give proof of what is failing when reporting a bug-id. Thanks for you all, you are working hard. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1511074 Title: camera constantly refocuses when recording a video Status in Canonical System Image: Confirmed Status in camera-app package in Ubuntu: Triaged Bug description: camera is missing auto focus options ON/OFF i really need to turn OFF auto focus. i can't record the screen without turning OFF the auto focus, but there is no settings... Sample video showing the refocusing https://www.youtube.com/watch?v=8Zdpp7mZEQs Its a bit odd that its going out of focus at all, wonder if there is a way to improve the configuration. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1511074/+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 1543352] Re: inet6 dhcp doesn't wait for link-local address to leave tentative - dhclient fails to bind
I have no idea why are you having two bugs for the same issue open. The other bug has been reported over 16 months ago, yet made it into LTS release. Oneliner patch, fixed upstream, 16 month ago. Can we expect the thing released before the long term support is over for Xenial? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1543352 Title: inet6 dhcp doesn't wait for link-local address to leave tentative - dhclient fails to bind Status in ifupdown package in Ubuntu: Triaged Bug description: = Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 = With an /etc/network/interfaces file containing: auto eno16780032 iface eno16780032 inet dhcp iface eno16780032 inet6 dhcp On boot, ifup starts 'dhclient -6' before the link local address has completed Duplicate Address Discovery (the address is marked 'tentative'). In turn, dhclient reports 'Can't bind to dhcp address: Cannot assign requested address', and fails almost immediately. It would seem that either wait-for-ll6.sh should wait for the link local address to come up AND stop being tentative, or the dhcp method for inet6 should call settle-dad.sh after wait-for-ll6? This is partly a race condition, so on slower devices the dad may complete by the time dhclient has got started, however I can regularly reproduce this on a virtual machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1543352/+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 1613852] Re: My system is trying to assassinate me using sound
White noise `pactl list`: http://paste.ubuntu.com/23226468/ Proper `pactl list`: http://paste.ubuntu.com/23226477/ -- 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/1613852 Title: My system is trying to assassinate me using sound Status in pulseaudio package in Ubuntu: New Status in vlc package in Ubuntu: Invalid Bug description: Most modern video formats that I find on the interwebs, when I try to play them with VLC, the sound is such a loud white noise, that I thought maybe it is an assassination attempt on my life. Totem refuses to play, claiming an error loading supporting library. Attached is a recording of what it sounds like. This started happening some one month ago or so. Until then, I've been enjoying all kinds of videos and their audio without issues. Likely not a VLC issue, although it would be nice if players could protect me from such atrocities. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: vlc-nox 2.2.2-5 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Aug 16 21:51:33 2016 ExecutablePath: /usr/bin/vlc InstallationDate: Installed on 2010-10-12 (2135 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) SourcePackage: vlc UpgradeStatus: Upgraded to xenial on 2015-11-13 (277 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1613852/+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
I had the problem with Ubuntu 16.04 out-of-the-box. After a full week of 12 hour days trying to resolve this issue, I was finally about to fix it. I made a longer post about it here. http://askubuntu.com/questions/829204/dns-routing-fails-for-vpn- connections-on-ubuntu-16-04-out-of-the-box Here's the abbreviated version. Step 1: Goto GitHub and clone the following repo to your home folder: https://github.com/masterkorp/openvpn-update-resolv-conf Step 2: Move the .sh files from your cloned rep to the /etc/openvpn folder: sudo chmod +x *.sh && sudo mv *.sh /etc/openvpn Step 3: Run the following command to install new packages for DNS: sudo apt-get install openresolv nscd unbound Step 4: Append the following line to your OpenVPN Client Configuration files (*.ovpn or *.conf). I did this after the configuration directives but before my inline certs ( tag): script-security 2 up "/etc/openvpn/update-resolv-conf.sh /etc/openvpn/update-systemd-network.sh" down "/etc/openvpn/update-resolv-conf.sh /etc/openvpn/update-systemd-network.sh" This should resolve the DNS resolution problem. Dmitry has the right steps, but I needed the 2nd script for my system to update. Works like my 14.04 system... before I upgraded to 16.04... -- 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 1613852] Re: My system is trying to assassinate me using sound
Could you dump the output of pactl list when the output is white noise and when it is proper? -- 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/1613852 Title: My system is trying to assassinate me using sound Status in pulseaudio package in Ubuntu: New Status in vlc package in Ubuntu: Invalid Bug description: Most modern video formats that I find on the interwebs, when I try to play them with VLC, the sound is such a loud white noise, that I thought maybe it is an assassination attempt on my life. Totem refuses to play, claiming an error loading supporting library. Attached is a recording of what it sounds like. This started happening some one month ago or so. Until then, I've been enjoying all kinds of videos and their audio without issues. Likely not a VLC issue, although it would be nice if players could protect me from such atrocities. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: vlc-nox 2.2.2-5 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Aug 16 21:51:33 2016 ExecutablePath: /usr/bin/vlc InstallationDate: Installed on 2010-10-12 (2135 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) SourcePackage: vlc UpgradeStatus: Upgraded to xenial on 2015-11-13 (277 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1613852/+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 1627304] Re: User locking problems - guest login crashing
>From Xubuntu, see same symptoms as seen previously - that is, can log in to Guest - logout fails. Dialogue looks ok for us. -- 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/1627304 Title: User locking problems - guest login crashing Status in gnome-session package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in lightdm-gtk-greeter package in Ubuntu: Confirmed Status in unity-greeter package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: Confirmed Bug description: Vanilla Ubuntu install. Lock user - login to guest account, desktop crashes. Ctrl+Alt+F7 allows you to resume user after unlocking. Add new user - am able to switch between locked users properly. Can logout of one user and be able to resume other locked session. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 24 13:38:09 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1627304/+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 1613852] Re: My system is trying to assassinate me using sound
So... I've figured out a workaround for this issue. Works every time.
1. Turn off both my built-in audio device and my HDMI device
2. Run VLC with the video I wish to play
3. While it is playing turn the HDMI device back on
Viola! Audio instead of unbearable noise!
Turning off/on the audio devices that I mention above I do via
pavucontrol ("Volume Control").
--
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/1613852
Title:
My system is trying to assassinate me using sound
Status in pulseaudio package in Ubuntu:
New
Status in vlc package in Ubuntu:
Invalid
Bug description:
Most modern video formats that I find on the interwebs, when I try to
play them with VLC, the sound is such a loud white noise, that I
thought maybe it is an assassination attempt on my life.
Totem refuses to play, claiming an error loading supporting library.
Attached is a recording of what it sounds like.
This started happening some one month ago or so.
Until then, I've been enjoying all kinds of videos and their audio
without issues.
Likely not a VLC issue, although it would be nice if players could
protect me from such atrocities.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: vlc-nox 2.2.2-5
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Aug 16 21:51:33 2016
ExecutablePath: /usr/bin/vlc
InstallationDate: Installed on 2010-10-12 (2135 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
SourcePackage: vlc
UpgradeStatus: Upgraded to xenial on 2015-11-13 (277 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1613852/+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 1627304] Re: User locking problems - guest login crashing
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xubuntu-default-settings (Ubuntu) Status: New => Confirmed -- 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/1627304 Title: User locking problems - guest login crashing Status in gnome-session package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in lightdm-gtk-greeter package in Ubuntu: Confirmed Status in unity-greeter package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: Confirmed Bug description: Vanilla Ubuntu install. Lock user - login to guest account, desktop crashes. Ctrl+Alt+F7 allows you to resume user after unlocking. Add new user - am able to switch between locked users properly. Can logout of one user and be able to resume other locked session. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 24 13:38:09 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1627304/+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 1627304] Re: User locking problems - guest login crashing
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-session (Ubuntu) Status: New => Confirmed -- 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/1627304 Title: User locking problems - guest login crashing Status in gnome-session package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in lightdm-gtk-greeter package in Ubuntu: Confirmed Status in unity-greeter package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: Confirmed Bug description: Vanilla Ubuntu install. Lock user - login to guest account, desktop crashes. Ctrl+Alt+F7 allows you to resume user after unlocking. Add new user - am able to switch between locked users properly. Can logout of one user and be able to resume other locked session. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 24 13:38:09 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1627304/+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 1627304] Re: User locking problems - guest login crashing
I could reproduce the issue on Ubuntu 16.10. Additional observations: * Logging in to a guest session fails also when you do it from the login screen without being logged in as a regular user, so I doubt that the issue is related to screen locking. * The zenity warning dialog shows up, but without its title bar - can it possibly be compiz related? (The rest of the screen is simply black.) -- 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/1627304 Title: User locking problems - guest login crashing Status in gnome-session package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in lightdm-gtk-greeter package in Ubuntu: Confirmed Status in unity-greeter package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: Confirmed Bug description: Vanilla Ubuntu install. Lock user - login to guest account, desktop crashes. Ctrl+Alt+F7 allows you to resume user after unlocking. Add new user - am able to switch between locked users properly. Can logout of one user and be able to resume other locked session. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 24 13:38:09 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1627304/+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 1413710] Re: Xorg crash - Fullscreen causing crash
Just filed a new bug report at https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1627365 and subcribed you Christopher. Thanks. -- 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/1413710 Title: Xorg crash - Fullscreen causing crash Status in xorg package in Ubuntu: Invalid Bug description: I was listening to this YouTube video: http://www.infinitelooper.com/?v=-tJYN-eG1zk&p=n When I decided to make it full screen, but it didn't want to go, so I very quickly double-clicked on it twice, and then the entire screen went black. And no matter what I did, it go away. Although I could still hear the music from the video. As I couldn't do anything really about it I had to hold down my power button and force it to shutdown. And when it started up the screen was fine. It is a laptop so I don't think that the monitor just turned off or something. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8.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 CurrentDesktop: Unity Date: Thu Jan 22 19:26:26 2015 DistUpgraded: 2014-12-13 16:39:34,851 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:5002] InstallationDate: Installed on 2014-12-06 (47 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 62742SG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-29-generic root=UUID=3883b8c8-34cb-4ec2-8834-fe85bbd10f52 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to utopic on 2014-12-13 (40 days ago) dmi.bios.date: 11/15/2012 dmi.bios.vendor: LENOVO dmi.bios.version: H5ET69WW (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 62742SG dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK IPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH5ET69WW(1.12):bd11/15/2012:svnLENOVO:pn62742SG:pvrLenovoB590:rvnLENOVO:rn62742SG:rvrWin8ProDPKIPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 62742SG dmi.product.version: Lenovo B590 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Thu Jan 22 19:19:28 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 827 vendor LGD xserver.version: 2:1.16.0-1ubuntu1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1413710/+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 1627365] [NEW] Screen frezes, only mouse pointer can move
Public bug reported: This issue only occurs when I use certain gaming software like Emulation Station, ppsspp and ppsspp-sdl on Fullscreen Mode. As of https://wiki.ubuntu.com/X/Troubleshooting/Freeze says, my symptoms are: - X stops responding to input (sometimes mouse cursor can still move, but clicking has no effect) - The screen displays but does not update. Sometimes there is screen corruption too, sometimes the screen goes black. - Often, X cannot be killed from the console or if it can, it won't restart properly; only a reboot clears the state I can go to TTY with Ctrl+Alt+F1, login and reboot, or go back back to frozen desktop/application with Ctrl+Alt+F7. I would like to reproduce this issue and collect the necessary data over ethernet, but I don't how to do it. - I'm experience this lockup when I go Fullscreen in PPSSPP (Sony PlayStation Portable Emulator), Emulation Station (Frontend for Emulators) and a couple of minutes pass, so I can't go back to Windowed mode. I've tried with VLC fullscreen mode without issues. I'll make a more detailed report of apps later on comments. - I first noticed it aprox. after installing this repos: http://ppa.launchpad.net/canonical-x/vulkan/ubuntu http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu - I'm using Unity, so I can't be sure if this is happening in other DE's - Like I said before, this happens when switching from fullscreen mode to windowed mode, in some applications. I haven't had problems with streaming video (youtube player, jwplayer, vimeo player, etc...) in fullscreen mode. Thanks! Technical Info. Machine: Lenovo G400s (Laptop) ~$ lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 ~$ apt-cache policy xorg xorg: Instalados: 1:7.7+13ubuntu3 Candidato: 1:7.7+13ubuntu3 Tabla de versión: *** 1:7.7+13ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status Phoronix Test Suite v6.4.0 Interactive Benchmarking System Software / Hardware Information Hardware: Processor: Intel Core i3-3110M @ 2.40GHz (4 Cores), Motherboard: LENOVO, Chipset: Intel 3rd Gen Core DRAM, Memory: 6144MB, Disk: 500GB Seagate ST500LT012-9WS14, Graphics: Intel HD 4000 (1000MHz), Audio: Conexant CX20757, Network: Qualcomm Atheros QCA8172 Fast + Qualcomm Atheros AR9485 Wireless Software: OS: Ubuntu 16.04, Kernel: 4.7.2-040702-generic (x86_64), Desktop: Unity 7.4.0, Display Server: X Server 1.18.4, Display Driver: intel 2.99.917, OpenGL: 3.3 Mesa 12.1.0-devel, Compiler: GCC 5.4.0 20160609, File-System: ext4, Screen Resolution: 1366x768 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.7.2-040702-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: Sat Sep 24 10:11:14 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3977] InstallationDate: Installed on 2015-07-08 (444 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: LENOVO 20244 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.7.2-040702-generic root=UUID=aeda239d-fc39-47e7-a775-53cef3aa6e11 ro quiet splash pciehp.pciehp_force=1 vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 7BCN36WW(V2.02) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 31900059Std dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G400s dmi.modalias: dmi:bvnLENOVO:bvr7BCN36WW(V2.02):bd08/28/2013:svnLENOVO:pn20244:pvrLenovoG400s:rvnLENOVO:rnINVALID:rvr31900059Std:cvnLENOVO:ct10:cvrLenovoG400s: dmi.product.name: 20244 dmi.product.version: Lenovo G400s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70+git1609171830.065955~gd~x version.libgl1-mesa-dri: libgl1-mesa-dri 12.1~git1609240730.cb7c2c~gd~x version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.1~git1609240730.cb7c2c~gd~x version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati:
[Touch-packages] [Bug 1497666] Re: No right channel sound on Creative Xtreme Audio (CA0106) in Ubuntu 14.04-15.10
Verified fixed with a clean install of Ubuntu 16.10. $ uname -a Linux luke-PowerEdge-T105 4.4.0-9136-generic #55-Ubuntu SMP Fri Aug 26 05:58:34 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Raymond, Thank you so much for all your help on this issue! ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Fix Released ** Summary changed: - No right channel sound on Creative Xtreme Audio (CA0106) in Ubuntu 14.04-15.10 + No right channel sound on Creative Xtreme Audio (CA0106) in Ubuntu 14.04-16.04 -- 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/1497666 Title: No right channel sound on Creative Xtreme Audio (CA0106) in Ubuntu 14.04-16.04 Status in alsa-driver package in Ubuntu: Fix Released Bug description: After a fresh install of Ubuntu 14.04, 15.04, 15.10 and on the liveCD, There is no sound on right channel. But it works perfectly in Win 7/10. It also worked perfectly on Ubuntu 12.04 My sound card is Creative Xtreme Audio (PCI CA0106). In the forum, many users also have experienced this bug with the incorrect default alsamixer settings. http://ubuntuforums.org/showthread.php?t=2217724 Here are my alsa-info.sh results. http://www.alsa- project.org/db/?f=e3ae99437c3d283b35cac7c33ace996bedf43a16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1497666/+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 1543179] Re: Audio does not get routed to BT headset/speaker
Same on my bq E5 hd (otq 13, as well as the previous 11.12 & 10, only ota9 was fully working wella) paired with car kenwood kca bt200 hands free + hifi bt interface. Audio hici is working but with some glitch. If a call is coming ( as,well as,generated) the system establish a connection, as it sould be, but no call audio (neither micro is wotking) Bt volume is different from zero. Need to switch manually to phone speaker to talk. If the call is terminated, the bt system restarts to play music. -- 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/1543179 Title: Audio does not get routed to BT headset/speaker Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Confirmed Bug description: STEPS: 1. Flash the latest daily rc-proposed image to a phone 2. Connect a bluetooth headset to the phone 3. Connect a speaker to the phone. EXPECTED: I expect the devices to connect and play audio ACTUAL: Speakers just connect and instantly disconnect Headsets don't get trusted and disconnect instantly, Once you trust it and then turn the headset off and back on again it connect can accept calls but the audio from both the mic and earpiece don't function. Image: 242 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1543179/+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 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
** Changed in: initramfs-tools (Ubuntu Xenial) Importance: Undecided => High ** Changed in: isc-dhcp (Ubuntu Xenial) Importance: Undecided => High ** Changed in: open-iscsi (Ubuntu) Importance: Undecided => High ** Changed in: open-iscsi (Ubuntu Xenial) Importance: Undecided => High -- 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/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses Status in MAAS: Confirmed Status in initramfs-tools package in Ubuntu: In Progress Status in isc-dhcp package in Ubuntu: In Progress Status in klibc package in Ubuntu: New Status in open-iscsi package in Ubuntu: Fix Committed Status in initramfs-tools source package in Xenial: Fix Committed Status in isc-dhcp source package in Xenial: Fix Committed Status in klibc source package in Xenial: New Status in open-iscsi source package in Xenial: Fix Committed Status in klibc package in Debian: New Bug description: initramfs' configure_networking function uses ipconfig to configure the network. ipconfig does not support dhcpv6. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164 Related bugs: * bug 1229458: grub2 needed changes * bug 1621615: network not configured when ipv6 netbooted into cloud-init [Impact] It is not possible to netboot Ubuntu with a network-based root filesystem in an ipv6-only environment. Anyone wanting to netboot in an ipv6-only environment is affected. These uploads address this by replacing the one-off klibc dhcp client (IPv4-only) with the defacto standard isc-dhcp-client, and thereby provide both ipv6 and ipv4 DHCP configuration. [Test Case] See Bug 1229458. Configure radvd, dhcpd, and tftpd for your ipv6-only netbooting world. Pass the boot process an ipv6 address to talk to, and see it fail to configure the network. [Regression Potential] 1) This increases the uncompressed initramfs size by approximately 500KB, since isc-dhcp-client is added, but klibc is still needed for some other things, and is therefore present. On systems with a very small /boot partition, this could result in failure to upgrade the initramfs. 2) In at least some cases, DHCP network configuration shifts from klibc's ipconfig to isc-dhcp-client's dhclient. This should be of minimal risk, as isc-dhcp-client is in very very widespread use. In the event of a regression, network boot would fail, but the prior kernel should still be bootable. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+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 1578396] Re: missing dependencies are not listed
** Description changed: Hi, ubuntu 16.04 here. Using gdebi I've noticed it does not display the list of missing dependencies : http://hpics.li/6ca144f but yet works fine. + + + 2016-09-24 : other example here https://forum.ubuntu- + fr.org/viewtopic.php?pid=21595751#p21595751 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1578396 Title: missing dependencies are not listed Status in gdebi package in Ubuntu: Confirmed Bug description: Hi, ubuntu 16.04 here. Using gdebi I've noticed it does not display the list of missing dependencies : http://hpics.li/6ca144f but yet works fine. 2016-09-24 : other example here https://forum.ubuntu- fr.org/viewtopic.php?pid=21595751#p21595751 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1578396/+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 1522675] Re: Can't drop privileges for downloading : _apt user not allowed
Michael and I don't have any different opinion here at all. You are complaining about root/.synaptic/tmp//tmp_cl - which is owned by synaptics - not about the /var/cache/apt/archives/partial or another apt owned directory. A directory inside your (well, root's) home directory is a different case altogether: It *should* be owned by you, not by _apt. -- 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/1522675 Title: Can't drop privileges for downloading : _apt user not allowed Status in apt package in Ubuntu: New Status in dpkg package in Ubuntu: Confirmed Status in synaptic package in Debian: New Bug description: Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+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 1627349] Re: Tapping the indicator panel does some weird things
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity8 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1627349 Title: Tapping the indicator panel does some weird things Status in unity8 package in Ubuntu: Confirmed Bug description: bq M10 rc-proposed r196 Tap the indicator bar on the left hand side. If you do that when you have an app opened, you'll see the current scope for a split second. If you do that from a scope, you will see the screen going black for a moment. This does not happen in the Desktop mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1627349/+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 1627349] [NEW] Tapping the indicator panel does some weird things
Public bug reported: bq M10 rc-proposed r196 Tap the indicator bar on the left hand side. If you do that when you have an app opened, you'll see the current scope for a split second. If you do that from a scope, you will see the screen going black for a moment. This does not happen in the Desktop mode. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1627349 Title: Tapping the indicator panel does some weird things Status in unity8 package in Ubuntu: Confirmed Bug description: bq M10 rc-proposed r196 Tap the indicator bar on the left hand side. If you do that when you have an app opened, you'll see the current scope for a split second. If you do that from a scope, you will see the screen going black for a moment. This does not happen in the Desktop mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1627349/+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 1585723] Re: UbuntuShape on intel i915 (Atom) uses fallback CPU rendering
Hi Emanuele, I asked the developer of Ubuntu Shape, and he said the new
(improved!) version of the UbuntuShape should not have this problem.
It will still take a few weeks before that is released though, as there
are a lot of pieces involved.
But still, I hope that's good news for you :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1585723
Title:
UbuntuShape on intel i915 (Atom) uses fallback CPU rendering
Status in ubuntu-ui-toolkit package in Ubuntu:
Confirmed
Bug description:
I'm digging into unity8 performance problems on older generation Intel
GPUs - specifically i915 Atom GPUs.
I've tested a simple QML file with a single empty UbuntuShape in it:
import QtQuick 2.4
import Ubuntu.Components 1.3
Rectangle {
width: 400
height: 300
color: "blue"
UbuntuShape {}
}
Running it with INTEL_DEBUG=perf env var set, I get this output:
i915_program_error: Exceeded max ALU instructions (76 out of 64)
ENTER FALLBACK 1: Program
Mapping a busy BO, causing a stall on the GPU.
which implies that MESA was unable to compile one of the UbuntuShape
shaders as it created more ALU instructions than the GPU could deal
with. MESA falls back to CPU rendering as a result.
The GPU stall message I guess is related to that.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1585723/+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 298781] Re: qt4-qtconfig does not save font settings
Solution on Xubuntu 16.04 x64: After upgrade from 14.04 to 16.04 my default font was 'Droid Sans'. But that font wasn't present anymore. 1. sudo fc-cache -f -v (possible affect this, it show some messages about invalid records) 2. Changing default font in 'Apperance' settings to 'Noto Sans' After that it's possible to change font in GTK theme to system font (Noto Sans). qtconfig window shows the wrong font style but qt apps are using the correct one. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/298781 Title: qt4-qtconfig does not save font settings Status in qt4-x11 package in Ubuntu: Confirmed Bug description: If you run qtconfig-qt4 and then make any changes to the font settings, they are never applied. If you open qtconfig again, the old font settings will be there. It is not possible to change them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/298781/+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 1438612] Re: remote file systems hang on shutdown, D-BUS stops too early
after years of suffering with this bug, I found a solution that works for me. I put a pre-down dispatch script for network manager to dismount nfs shares when bringing the network down. This works even if a reboot is run from a shell. In /etc/NetworkManager/dispatcher.d/nfs.sh: /etc/NetworkManager/dispatcher.d/pre-down has a link to it as well. #!/bin/bash IF=$1 STATUS=$2 logger -s "** NetworkManager dispatch script nfs, IF="$1" STATUS="$2 case "$2" in pre-down) umount -a -t nfs service cups stop ;; up) mount -a -t nfs ;; esac I do NOT use the systemd automount fstab option as it'll try to automount when this script is trying to dismount the nfs shares. I also have it stop cups as kubuntu sometimes hangs bringing cups down. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1438612 Title: remote file systems hang on shutdown, D-BUS stops too early Status in D-Bus: Won't Fix Status in dbus package in Ubuntu: Fix Released Bug description: (part of bug 1431774). During shutdown, D-Bus stops too early. In particular, it stops before NetworkManager and remote-fs.target, so that any network unmount will cause errors and hang the boot. This can be seen with $ journalctl -b -1 | egrep 'Stop.*(D-Bus|Network M|Remote F)' Mär 30 19:05:19 donald systemd[1]: Stopping D-Bus System Message Bus... Mär 30 19:05:19 donald systemd[1]: Stopped D-Bus System Message Bus. Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems. Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems. Mär 30 19:05:19 donald systemd[1]: Stopped target Remote File Systems (Pre). Mär 30 19:05:19 donald systemd[1]: Stopping Remote File Systems (Pre). Mär 30 19:05:19 donald systemd[1]: Stopping Network Manager... Mär 30 19:05:42 donald systemd[1]: Stopped Network Manager. Mär 30 19:05:42 donald systemd[1]: Stopping D-Bus System Message Bus Socket. A quick workaround is to add After=dbus.service to /lib/systemd/system/NetworkManager.service's [Unit] section, but this should be fixed in a more general fashion. To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1438612/+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 945430] Re: Lists lack zebra-striping
The functionality got removed in 3.18 but hopefully it will be added back: https://bugzilla.gnome.org/show_bug.cgi?id=757495 ** Bug watch added: GNOME Bug Tracker #757495 https://bugzilla.gnome.org/show_bug.cgi?id=757495 ** Also affects: gtk via https://bugzilla.gnome.org/show_bug.cgi?id=757495 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/945430 Title: Lists lack zebra-striping Status in GTK+: Unknown Status in light-themes: Fix Released Status in Ubuntu theme: Fix Released Status in light-themes package in Ubuntu: Fix Released Status in ubuntu-themes package in Ubuntu: Triaged Bug description: We had it before and was taken out in Precise. We need this back. It makes apps like Rhythmbox much easier to handle. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/945430/+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 1412492] Re: can't change the keyboard layout
Update: With BQ M10 Ubuntu OTA 13, it is now possible to select the keyboard layout in: Settings/Language & Text/Keyboard Layouts/External keyboard (option displayed when an external keyboard is plugged) However, the change is not saved. So, it still does not work... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1412492 Title: can't change the keyboard layout Status in Mir: Incomplete Status in mir package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Fix Released Bug description: Using the current vivid version, it seems like there is no way to configure/change the keyboard layout (using a real keyboard, not the osk), that feature is needed for desktop users To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1412492/+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 1625437] Re: systemd-resolved crashed with SIGSEGV in sd_event_source_unref()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1625437 Title: systemd-resolved crashed with SIGSEGV in sd_event_source_unref() Status in systemd package in Ubuntu: Confirmed Bug description: I'm getting this crash when starting the computer. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: systemd 231-6 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Sat Sep 17 20:21:42 2016 ExecutablePath: /lib/systemd/systemd-resolved InstallationDate: Installed on 2013-11-28 (1026 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Dell Inc. Latitude E6530 ProcCmdline: /lib/systemd/systemd-resolved ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic root=UUID=409b2104-0062-403c-8b6b-f07948051f69 ro quiet splash vt.handoff=7 Signal: 11 SourcePackage: systemd StacktraceTop: sd_event_source_unref () from /lib/systemd/libsystemd-shared-231.so ?? () ?? () ?? () ?? () from /lib/systemd/libsystemd-shared-231.so Title: systemd-resolved crashed with SIGSEGV in sd_event_source_unref() UpgradeStatus: Upgraded to yakkety on 2016-08-31 (19 days ago) UserGroups: dmi.bios.date: 08/27/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd08/27/2013:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1625437/+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
Hi all. It really problem now on 16.04. But i found funny fix for it. It is not very pretty, but i think it is helps someone. First step: Add script-security 2 up /etc/openvpn/update-resolv-conf down /etc/openvpn/update-resolv-conf in your .ovpn client file. Second step: Ubuntu can't have more that 3 dns records in /etc/resolv.conf So, add 3 dns records in server.conf using push-dns push "dhcp-option DNS firstdns" push "dhcp-option DNS seconddns" push "dhcp-option DNS thirddns" where firstdns,seconddns,thirddns put your dns servers. It is resolved problem for me without disable dnsmasq or other manipulations. I hope, i help to someone. I will waiting a normal resolve this problem with all. -- 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 1626435] Re: Keyboard layout not applied on the shell
** Changed in: mir (Ubuntu) Status: New => In Progress ** Changed in: canonical-devices-system-image Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1626435 Title: Keyboard layout not applied on the shell Status in Canonical System Image: In Progress Status in mir package in Ubuntu: In Progress Status in qtmir package in Ubuntu: In Progress Status in unity8 package in Ubuntu: In Progress Bug description: Split out from bug #1611859: Steps: * connect a BT or a physical keyboard * wipe or remove ~/.config/ubuntu-system-settings/wizard-has-run* and reboot * go through the wizard Expected: * I can use the selected layout in the wizard * and in snap decisions Current: * you can only use us layout in the shell ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity8 8.14+16.04.20160914-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-landing-078] ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 22 10:07:47 2016 InstallationDate: Installed on 2016-05-06 (138 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1626435/+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 1622002] Re: dhcp_release6 can be called when it is not present
Reviewed: https://review.openstack.org/375645 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=f74a6c047f02e077e4fd943e2eb256df82e05509 Submitter: Jenkins Branch:stable/newton commit f74a6c047f02e077e4fd943e2eb256df82e05509 Author: Brian Haley Date: Tue Sep 6 14:44:41 2016 -0400 Fix dhcp_release6 error when not supported If the system does not have a version of dnsmasq that supports dhcp_release6, warn about but otherwise handle it gracefully, and also don't even try to execute it the next time. Closes-Bug: #1622002 Related-Bug: #1624079 (cherry picked from commit d4f92ede9ed52cd0b9059d993e3cf1f42d5ff57e) Change-Id: I6bb9547f9d9a9fcfb2357521f3f5bd1dc1dd5136 ** Tags added: in-stable-newton -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1622002 Title: dhcp_release6 can be called when it is not present Status in neutron: Fix Released Status in dnsmasq package in Ubuntu: New Bug description: If someone enables dhcpv6-stateful addressing on a subnet, but they are running an old version of dnsmasq (<2.76), then the dhcp agent could try and run dhcp_release6 even though it isn't present. An example: http://logs.openstack.org/53/365653/5/check/gate-tempest-dsvm-neutron- multinode-full-ubuntu- xenial/813d16d/logs/screen-q-dhcp.txt.gz#_2016-09-06_11_40_02_272 Checking it's present first would fix this problem. Since the change to call dhcp_release6 was just added in https://review.openstack.org/#/c/301747/ we should fix this before Newton ships and people complain. There is also an effort to get Cirros to support DHCPv6 so that we can test this in the gate, https://bugs.launchpad.net/cirros/+bug/1487041 - hopefully that gets done so we can add a functional test. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1622002/+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 1554504] Re: Calendar reminder does not wake phone when airplane mode is enabled
Pat, yes we use the com.canonical.powerd interface's requestWakeup method to wakeup the phone when a clock alarm or calendar event needs a notification. indicator-datetime doesn't have any airplane mode logic in it at all, so I'm not sure what's going on there. I'm not able to reproduce this on a n4 running 15.04 (r531) by turning on airplane mode and trying calendar events and a clock-app alarm. Is this issue reproducible for anyone? ** Changed in: canonical-devices-system-image Status: Confirmed => Incomplete ** Changed in: indicator-datetime (Ubuntu) Status: Confirmed => Incomplete -- 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/1554504 Title: Calendar reminder does not wake phone when airplane mode is enabled Status in Canonical System Image: Incomplete Status in indicator-datetime package in Ubuntu: Incomplete Bug description: If airplane mode is enabled, the phone seems to go into a deep sleep where it doesn't wake up for a calendar reminder. The reminder does not sound until the power button is pressed to wake the phone, in some cases this has been more than an hour after the reminder was scheduled for. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1554504/+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 1627329] Re: package linux-image-4.4.0-38-generic 4.4.0-38.57 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with return code 2
** Tags removed: need-duplicate-check -- 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/1627329 Title: package linux-image-4.4.0-38-generic 4.4.0-38.57 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with return code 2 Status in apt package in Ubuntu: New Bug description: no idea ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-38-generic 4.4.0-38.57 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ravi 2362 F pulseaudio Date: Sat Sep 24 20:15:21 2016 DuplicateSignature: package:linux-image-4.4.0-38-generic:4.4.0-38.57 Setting up libapache2-mod-fastcgi (2.4.7~0910052141-1.2) ... dpkg: error processing package libapache2-mod-fastcgi (--configure): subprocess installed post-installation script returned error exit status 1 ErrorMessage: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with return code 2 HibernationDevice: RESUME=UUID=0a2b9a66-fac5-4339-81e8-348a6208535a InstallationDate: Installed on 2012-08-25 (1490 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: Hewlett-Packard HP ProBook 4530s ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=62db2609-e23d-4edc-94a2-5e7fbf21eb3f ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.2 SourcePackage: apt Title: package linux-image-4.4.0-38-generic 4.4.0-38.57 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with return code 2 UpgradeStatus: Upgraded to xenial on 2016-09-24 (0 days ago) dmi.bios.date: 04/21/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SRR Ver. F.07 dmi.board.name: 167C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 22.1A dmi.chassis.asset.tag: CNU11657V4 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SRRVer.F.07:bd04/21/2011:svnHewlett-Packard:pnHPProBook4530s:pvrAC02:rvnHewlett-Packard:rn167C:rvrKBCVersion22.1A:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 4530s dmi.product.version: AC02 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1627329/+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 1522675] Re: Can't drop privileges for downloading : _apt user not allowed
** Description changed: Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. - === - The real problem is : there is no _apt user on the system (see #808802 MV comments) + oem@u64:~$ ls -l .synaptic + total 4 + -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options + -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf - grep -B2 _apt /var/lib/dpkg/info/apt.postinst + oem@u64:~$ ls -l /var/lib/apt/lists/ + + -rw-r- 1 root root0 Sep 20 06:36 lock + drwx-- 2 _apt root16384 Sep 24 15:25 partial + .. - # add unprivileged user for the apt methods - adduser --force-badname --system --home /nonexistent \ - --no-create-home --quiet _apt || true - - # Fixup any mistake in the home directory of the _apt user - if dpkg --compare-versions "$2" lt-nl 1.1~exp10~; then - usermod --home /nonexistent _apt - == - and also a workaround: - sudo chown _apt /var/lib/update-notifier/package-data-downloads/partial/ + oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ + . + drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1522675 Title: Can't drop privileges for downloading : _apt user not allowed Status in apt package in Ubuntu: New Status in dpkg package in Ubuntu: Confirmed Status in synaptic package in Debian: New Bug description: Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+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 1626345] Re: After rebooting for updates, reboot is still required.
** Changed in: unattended-upgrades (Ubuntu) Status: Incomplete => Confirmed -- 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/1626345 Title: After rebooting for updates, reboot is still required. Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: Yesterday unattended-upgrades required a reboot for kernel updates as expected. But today unattended-upgrades required a reboot even though there were no updates. 2016-09-20 05:20:10,409 INFO Initial blacklisted packages: 2016-09-20 05:20:10,410 INFO Initial whitelisted packages: 2016-09-20 05:20:10,411 INFO Starting unattended upgrades script 2016-09-20 05:20:10,411 INFO Allowed origins are: ['o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates'] 2016-09-20 05:21:13,118 INFO Packages that will be upgraded: linux-generic linux-headers-generic linux-image-generic linux-libc-dev 2016-09-20 05:21:13,119 INFO Writing dpkg log to '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' 2016-09-20 05:24:17,405 INFO All upgrades installed 2016-09-20 05:24:24,959 WARNING Found /var/run/reboot-required, rebooting 2016-09-21 05:10:54,080 INFO Initial blacklisted packages: 2016-09-21 05:10:54,088 INFO Initial whitelisted packages: 2016-09-21 05:10:54,089 INFO Starting unattended upgrades script 2016-09-21 05:10:54,089 INFO Allowed origins are: ['o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates'] 2016-09-21 05:11:02,624 INFO No packages found that can be upgraded unattended and no pending auto-removals 2016-09-21 05:11:02,624 WARNING Found /var/run/reboot-required, rebooting On this machine (16.04 server) unattended-upgrades is configured to reboot automatically. This also happened on another 16.04 server with default unattended- upgrades configuration. It displayed the ***System restart required*** message. The same on a 14.04 server and a 14.04 desktop. Expected behaviour: Not to do an unnecessary reboot. Let me know what other information I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1626345/+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 1627329] [NEW] package linux-image-4.4.0-38-generic 4.4.0-38.57 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with return code 2
Public bug reported: no idea ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-38-generic 4.4.0-38.57 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ravi 2362 F pulseaudio Date: Sat Sep 24 20:15:21 2016 DuplicateSignature: package:linux-image-4.4.0-38-generic:4.4.0-38.57 Setting up libapache2-mod-fastcgi (2.4.7~0910052141-1.2) ... dpkg: error processing package libapache2-mod-fastcgi (--configure): subprocess installed post-installation script returned error exit status 1 ErrorMessage: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with return code 2 HibernationDevice: RESUME=UUID=0a2b9a66-fac5-4339-81e8-348a6208535a InstallationDate: Installed on 2012-08-25 (1490 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: Hewlett-Packard HP ProBook 4530s ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=62db2609-e23d-4edc-94a2-5e7fbf21eb3f ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.2 SourcePackage: apt Title: package linux-image-4.4.0-38-generic 4.4.0-38.57 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with return code 2 UpgradeStatus: Upgraded to xenial on 2016-09-24 (0 days ago) dmi.bios.date: 04/21/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SRR Ver. F.07 dmi.board.name: 167C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 22.1A dmi.chassis.asset.tag: CNU11657V4 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SRRVer.F.07:bd04/21/2011:svnHewlett-Packard:pnHPProBook4530s:pvrAC02:rvnHewlett-Packard:rn167C:rvrKBCVersion22.1A:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 4530s dmi.product.version: AC02 dmi.sys.vendor: Hewlett-Packard ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1627329 Title: package linux-image-4.4.0-38-generic 4.4.0-38.57 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with return code 2 Status in apt package in Ubuntu: New Bug description: no idea ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-38-generic 4.4.0-38.57 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ravi 2362 F pulseaudio Date: Sat Sep 24 20:15:21 2016 DuplicateSignature: package:linux-image-4.4.0-38-generic:4.4.0-38.57 Setting up libapache2-mod-fastcgi (2.4.7~0910052141-1.2) ... dpkg: error processing package libapache2-mod-fastcgi (--configure): subprocess installed post-installation script returned error exit status 1 ErrorMessage: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with return code 2 HibernationDevice: RESUME=UUID=0a2b9a66-fac5-4339-81e8-348a6208535a InstallationDate: Installed on 2012-08-25 (1490 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: Hewlett-Packard HP ProBook 4530s ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=62db2609-e23d-4edc-94a2-5e7fbf21eb3f ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.2 SourcePackage: apt Title: package linux-image-4.4.0-38-generic 4.4.0-38.57 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with return code 2 UpgradeStatus: Upgraded to xenial on 2016-09-24 (0 days ago) dmi.bios.date: 04/21/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SRR Ver. F.07 dmi.board.name: 167C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 22.1A dmi.chassis.asset.tag: CNU11657V4 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SRRVer.F.07:bd04/21/2011:svnHewlett-Packard:pnHPProBook4530s:pvrAC02:rvnHewlett-Packard:rn167C:rvrKBCVersion22.1A:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 4530s dmi.product.version: AC02 dmi.sys.vendor: Hewlett-Packard To manage notifications about th
[Touch-packages] [Bug 1522675] Re: Can't drop privileges for downloading : _apt user not allowed
For the record, an other case has been fixed about _apt sandboxing https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806406 oem@u64:~$ getent passwd . _apt:x:123:65534::/nonexistent:/bin/false ** Bug watch added: Debian Bug tracker #806406 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806406 -- 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/1522675 Title: Can't drop privileges for downloading : _apt user not allowed Status in apt package in Ubuntu: New Status in dpkg package in Ubuntu: Confirmed Status in synaptic package in Debian: New Bug description: Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. === The real problem is : there is no _apt user on the system (see #808802 MV comments) grep -B2 _apt /var/lib/dpkg/info/apt.postinst # add unprivileged user for the apt methods adduser --force-badname --system --home /nonexistent \ --no-create-home --quiet _apt || true # Fixup any mistake in the home directory of the _apt user if dpkg --compare-versions "$2" lt-nl 1.1~exp10~; then usermod --home /nonexistent _apt == and also a workaround: sudo chown _apt /var/lib/update-notifier/package-data-downloads/partial/ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+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 941826] Re: dlopen(libGL.so) resolves to mesa rather than nvidia
** Also affects: nvidia-graphics-drivers-340 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/941826
Title:
dlopen(libGL.so) resolves to mesa rather than nvidia
Status in NVIDIA Drivers Ubuntu:
New
Status in mesa package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
New
Status in pyqt5 package in Ubuntu:
Invalid
Status in python-qt4 package in Ubuntu:
Invalid
Bug description:
I'm having trouble with a combination of NVIDIA + Python + Qt +
Opengl.
I tried using a QGraphicsView on a QGLWidget. I'm getting a white window and
errors like this these:
QGLShader: could not create shader
Vertex shader for simpleShaderProg (MainVertexShader
&PositionOnlyVertexShader) failed to compile
This is an example application triggering the problem:
http://pastebin.com/R0aa8ejs
The 'same' program works flawlessly when using C++/Qt. I'm seeing the exact
behavior when using PySide instead of PyQt4 by the way. I'm also seeing this
error when trying the original demo application from python-qt4-doc. Also,
calling
QtGui.QApplication.setGraphicsSystem("opengl")
produces the same errors.
I'm experiencing this problems on 11.10 and 12.04 with the ubuntu-
provided nvidia drivers (where 12.04 includes the most recent driver
for now). After installing the driver using the original NVidia
installer, the applications work as expected.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/941826/+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 1384354] Re: Should ellipsize events names
This should be handled in the rendering, rather than in the strings we pass across the bus to Unity ** Package changed: indicator-datetime (Ubuntu) => unity8 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1384354 Title: Should ellipsize events names Status in unity8 package in Ubuntu: Confirmed Bug description: Using utopic, if you calendar contains an event with a long name the indicator menu is stretched to contain it which looks weird, ellipsizing those would be nice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1384354/+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 1522675] Re: Can't drop privileges for downloading : _apt user not allowed
@juliank (#16) Michael Vogt has a different opinion that yours, so blaming apt again https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808802 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808802#20 "This is a bug indeed, the question is how it got triggered, that dir should be owend by the _apt user." oem@u64:~$ ls -dl /var/cache/apt/archives/partial/ drwx-- 2 _apt root 4096 Sep 24 05:26 /var/cache/apt/archives/partial/ oem@u64:~$ grep -B2 _apt /var/lib/dpkg/info/apt.postinst # add unprivileged user for the apt methods adduser --force-badname --system --home /nonexistent \ --no-create-home --quiet _apt || true # Fixup any mistake in the home directory of the _apt user if dpkg --compare-versions "$2" lt-nl 1.1~exp10~; then usermod --home /nonexistent _apt -- 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/1522675 Title: Can't drop privileges for downloading : _apt user not allowed Status in apt package in Ubuntu: New Status in dpkg package in Ubuntu: Confirmed Status in synaptic package in Debian: New Bug description: Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. === The real problem is : there is no _apt user on the system (see #808802 MV comments) grep -B2 _apt /var/lib/dpkg/info/apt.postinst # add unprivileged user for the apt methods adduser --force-badname --system --home /nonexistent \ --no-create-home --quiet _apt || true # Fixup any mistake in the home directory of the _apt user if dpkg --compare-versions "$2" lt-nl 1.1~exp10~; then usermod --home /nonexistent _apt == and also a workaround: sudo chown _apt /var/lib/update-notifier/package-data-downloads/partial/ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+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 1522675] Re: Can't drop privileges for downloading : _apt user not allowed
** Also affects: apt (Ubuntu) Importance: Undecided Status: New -- 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/1522675 Title: Can't drop privileges for downloading : _apt user not allowed Status in apt package in Ubuntu: New Status in dpkg package in Ubuntu: Confirmed Status in synaptic package in Debian: New Bug description: Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. === The real problem is : there is no _apt user on the system (see #808802 MV comments) grep -B2 _apt /var/lib/dpkg/info/apt.postinst # add unprivileged user for the apt methods adduser --force-badname --system --home /nonexistent \ --no-create-home --quiet _apt || true # Fixup any mistake in the home directory of the _apt user if dpkg --compare-versions "$2" lt-nl 1.1~exp10~; then usermod --home /nonexistent _apt == and also a workaround: sudo chown _apt /var/lib/update-notifier/package-data-downloads/partial/ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+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 1627310] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1627310/+attachment/4747751/+files/JournalErrors.txt -- 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/1627310 Title: Guest session fails to log out Status in lightdm package in Ubuntu: Confirmed Status in xfce4-session package in Ubuntu: Confirmed Bug description: Vanilla Xubuntu install. When logging out from the guest session, everything is closed and the desktop wallpaper is the only thing that remains. The user is never returned to the login screen. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xfce4-session 4.12.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Uname: Linux 4.8.0-11-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Sep 24 09:18:31 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921) SourcePackage: xfce4-session UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921) Package: lightdm 1.19.4-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Tags: yakkety Uname: Linux 4.8.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1627310/+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 1627304] Re: User locking problems - guest login crashing
In Xubuntu we can login to the gues user desktop - but it crashes on logout rather than logging in. -- 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/1627304 Title: User locking problems - guest login crashing Status in gnome-session package in Ubuntu: New Status in lightdm package in Ubuntu: Confirmed Status in lightdm-gtk-greeter package in Ubuntu: Confirmed Status in unity-greeter package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: New Bug description: Vanilla Ubuntu install. Lock user - login to guest account, desktop crashes. Ctrl+Alt+F7 allows you to resume user after unlocking. Add new user - am able to switch between locked users properly. Can logout of one user and be able to resume other locked session. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 24 13:38:09 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1627304/+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 1627310] Re: Guest session fails to log out
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xfce4-session (Ubuntu) Status: New => Confirmed -- 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/1627310 Title: Guest session fails to log out Status in lightdm package in Ubuntu: Confirmed Status in xfce4-session package in Ubuntu: Confirmed Bug description: Vanilla Xubuntu install. When logging out from the guest session, everything is closed and the desktop wallpaper is the only thing that remains. The user is never returned to the login screen. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xfce4-session 4.12.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Uname: Linux 4.8.0-11-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Sep 24 09:18:31 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921) SourcePackage: xfce4-session UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921) Package: lightdm 1.19.4-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Tags: yakkety Uname: Linux 4.8.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1627310/+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 1627310] Re: Guest session fails to log out
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (Ubuntu) Status: New => Confirmed -- 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/1627310 Title: Guest session fails to log out Status in lightdm package in Ubuntu: Confirmed Status in xfce4-session package in Ubuntu: Confirmed Bug description: Vanilla Xubuntu install. When logging out from the guest session, everything is closed and the desktop wallpaper is the only thing that remains. The user is never returned to the login screen. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xfce4-session 4.12.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Uname: Linux 4.8.0-11-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Sep 24 09:18:31 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921) SourcePackage: xfce4-session UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921) Package: lightdm 1.19.4-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Tags: yakkety Uname: Linux 4.8.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1627310/+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 1627310] LightdmLog.txt
apport information ** Attachment added: "LightdmLog.txt" https://bugs.launchpad.net/bugs/1627310/+attachment/4747754/+files/LightdmLog.txt -- 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/1627310 Title: Guest session fails to log out Status in lightdm package in Ubuntu: Confirmed Status in xfce4-session package in Ubuntu: Confirmed Bug description: Vanilla Xubuntu install. When logging out from the guest session, everything is closed and the desktop wallpaper is the only thing that remains. The user is never returned to the login screen. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xfce4-session 4.12.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Uname: Linux 4.8.0-11-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Sep 24 09:18:31 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921) SourcePackage: xfce4-session UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921) Package: lightdm 1.19.4-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Tags: yakkety Uname: Linux 4.8.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1627310/+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 1627310] Re: Guest session fails to log out
Comments #2 - 8 are from using apport-collect with lightdm -- 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/1627310 Title: Guest session fails to log out Status in lightdm package in Ubuntu: Confirmed Status in xfce4-session package in Ubuntu: Confirmed Bug description: Vanilla Xubuntu install. When logging out from the guest session, everything is closed and the desktop wallpaper is the only thing that remains. The user is never returned to the login screen. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xfce4-session 4.12.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Uname: Linux 4.8.0-11-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Sep 24 09:18:31 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921) SourcePackage: xfce4-session UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921) Package: lightdm 1.19.4-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Tags: yakkety Uname: Linux 4.8.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1627310/+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 1627310] LightdmGreeterLog.txt
apport information ** Attachment added: "LightdmGreeterLog.txt" https://bugs.launchpad.net/bugs/1627310/+attachment/4747753/+files/LightdmGreeterLog.txt -- 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/1627310 Title: Guest session fails to log out Status in lightdm package in Ubuntu: Confirmed Status in xfce4-session package in Ubuntu: Confirmed Bug description: Vanilla Xubuntu install. When logging out from the guest session, everything is closed and the desktop wallpaper is the only thing that remains. The user is never returned to the login screen. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xfce4-session 4.12.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Uname: Linux 4.8.0-11-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Sep 24 09:18:31 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921) SourcePackage: xfce4-session UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921) Package: lightdm 1.19.4-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Tags: yakkety Uname: Linux 4.8.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1627310/+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 1627310] LightdmDisplayLog.txt
apport information ** Attachment added: "LightdmDisplayLog.txt" https://bugs.launchpad.net/bugs/1627310/+attachment/4747752/+files/LightdmDisplayLog.txt -- 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/1627310 Title: Guest session fails to log out Status in lightdm package in Ubuntu: Confirmed Status in xfce4-session package in Ubuntu: Confirmed Bug description: Vanilla Xubuntu install. When logging out from the guest session, everything is closed and the desktop wallpaper is the only thing that remains. The user is never returned to the login screen. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xfce4-session 4.12.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Uname: Linux 4.8.0-11-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Sep 24 09:18:31 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921) SourcePackage: xfce4-session UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921) Package: lightdm 1.19.4-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Tags: yakkety Uname: Linux 4.8.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1627310/+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 1627310] LightdmUsersConfig.txt
apport information ** Attachment added: "LightdmUsersConfig.txt" https://bugs.launchpad.net/bugs/1627310/+attachment/4747755/+files/LightdmUsersConfig.txt -- 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/1627310 Title: Guest session fails to log out Status in lightdm package in Ubuntu: Confirmed Status in xfce4-session package in Ubuntu: Confirmed Bug description: Vanilla Xubuntu install. When logging out from the guest session, everything is closed and the desktop wallpaper is the only thing that remains. The user is never returned to the login screen. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xfce4-session 4.12.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Uname: Linux 4.8.0-11-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Sep 24 09:18:31 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921) SourcePackage: xfce4-session UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921) Package: lightdm 1.19.4-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Tags: yakkety Uname: Linux 4.8.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1627310/+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 1627310] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1627310/+attachment/4747756/+files/ProcEnviron.txt -- 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/1627310 Title: Guest session fails to log out Status in lightdm package in Ubuntu: Confirmed Status in xfce4-session package in Ubuntu: Confirmed Bug description: Vanilla Xubuntu install. When logging out from the guest session, everything is closed and the desktop wallpaper is the only thing that remains. The user is never returned to the login screen. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xfce4-session 4.12.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Uname: Linux 4.8.0-11-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Sep 24 09:18:31 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921) SourcePackage: xfce4-session UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921) Package: lightdm 1.19.4-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Tags: yakkety Uname: Linux 4.8.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1627310/+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 1627310] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1627310/+attachment/4747750/+files/Dependencies.txt -- 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/1627310 Title: Guest session fails to log out Status in lightdm package in Ubuntu: Confirmed Status in xfce4-session package in Ubuntu: Confirmed Bug description: Vanilla Xubuntu install. When logging out from the guest session, everything is closed and the desktop wallpaper is the only thing that remains. The user is never returned to the login screen. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xfce4-session 4.12.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Uname: Linux 4.8.0-11-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Sep 24 09:18:31 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921) SourcePackage: xfce4-session UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921) Package: lightdm 1.19.4-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Tags: yakkety Uname: Linux 4.8.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1627310/+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 1627310] [NEW] Guest session fails to log out
Public bug reported: Vanilla Xubuntu install. When logging out from the guest session, everything is closed and the desktop wallpaper is the only thing that remains. The user is never returned to the login screen. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xfce4-session 4.12.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Uname: Linux 4.8.0-11-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Sep 24 09:18:31 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921) SourcePackage: xfce4-session UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921) Package: lightdm 1.19.4-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Tags: yakkety Uname: Linux 4.8.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True ** Affects: lightdm (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: xfce4-session (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug apport-collected yakkety ** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags added: apport-collected ** Description changed: Vanilla Xubuntu install. When logging out from the guest session, everything is closed and the desktop wallpaper is the only thing that remains. The user is never returned to the login screen. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xfce4-session 4.12.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Uname: Linux 4.8.0-11-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Sep 24 09:18:31 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921) SourcePackage: xfce4-session UpgradeStatus: No upgrade log present (probably fresh install) + --- + ApportVersion: 2.20.3-0ubuntu7 + Architecture: amd64 + CurrentDesktop: XFCE + DistroRelease: Ubuntu 16.10 + InstallationDate: Installed on 2016-09-24 (0 days ago) + InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921) + Package: lightdm 1.19.4-0ubuntu1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 + Tags: yakkety + Uname: Linux 4.8.0-11-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1627310 Title: Guest session fails to log out Status in lightdm package in Ubuntu: Confirmed Status in xfce4-session package in Ubuntu: Confirmed Bug description: Vanilla Xubuntu install. When logging out from the guest session, everything is closed and the desktop wallpaper is the only thing that remains. The user is never returned to the login screen. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xfce4-session 4.12.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Uname: Linux 4.8.0-11-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Sep 24 09:18:31 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921) SourcePackage: xfce4-session UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160921) Package: lightdm 1.19.4-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Tags: yakkety Uname: Linux 4.8.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1627310/+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 1622303] Re: Fails to unlock/ resumes to black screen
I tagged LightDM and LightDM GTK+ Greeter since they may be directly related. ** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Also affects: lightdm-gtk-greeter (Ubuntu) Importance: Undecided Status: New -- 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/1622303 Title: Fails to unlock/ resumes to black screen Status in light-locker package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: New Status in lightdm-gtk-greeter package in Ubuntu: New Bug description: Lock screen (or suspend) System allows for password to unlock No desktop shown after unlocking ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xfce4-power-manager 1.4.4-4ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Sep 11 10:04:39 2016 InstallationDate: Installed on 2016-06-11 (91 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160611) SourcePackage: xfce4-power-manager UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-06-11 (95 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160611) Package: light-locker 1.7.0-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Tags: yakkety Uname: Linux 4.4.0-9136-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1622303/+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 1627304] Re: User locking problems - guest login crashing
** Also affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Also affects: xubuntu-default-settings (Ubuntu) Importance: Undecided Status: New -- 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/1627304 Title: User locking problems - guest login crashing Status in gnome-session package in Ubuntu: New Status in lightdm package in Ubuntu: Confirmed Status in lightdm-gtk-greeter package in Ubuntu: Confirmed Status in unity-greeter package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: New Bug description: Vanilla Ubuntu install. Lock user - login to guest account, desktop crashes. Ctrl+Alt+F7 allows you to resume user after unlocking. Add new user - am able to switch between locked users properly. Can logout of one user and be able to resume other locked session. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 24 13:38:09 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1627304/+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 1627304] Re: User locking problems - guest login crashing
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity-greeter (Ubuntu) Status: New => Confirmed -- 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/1627304 Title: User locking problems - guest login crashing Status in gnome-session package in Ubuntu: New Status in lightdm package in Ubuntu: Confirmed Status in lightdm-gtk-greeter package in Ubuntu: Confirmed Status in unity-greeter package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: New Bug description: Vanilla Ubuntu install. Lock user - login to guest account, desktop crashes. Ctrl+Alt+F7 allows you to resume user after unlocking. Add new user - am able to switch between locked users properly. Can logout of one user and be able to resume other locked session. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 24 13:38:09 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1627304/+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 1627304] Re: User locking problems - guest login crashing
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm-gtk-greeter (Ubuntu) Status: New => Confirmed -- 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/1627304 Title: User locking problems - guest login crashing Status in gnome-session package in Ubuntu: New Status in lightdm package in Ubuntu: Confirmed Status in lightdm-gtk-greeter package in Ubuntu: Confirmed Status in unity-greeter package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: New Bug description: Vanilla Ubuntu install. Lock user - login to guest account, desktop crashes. Ctrl+Alt+F7 allows you to resume user after unlocking. Add new user - am able to switch between locked users properly. Can logout of one user and be able to resume other locked session. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 24 13:38:09 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1627304/+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 1627304] Re: User locking problems - guest login crashing
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (Ubuntu) Status: New => Confirmed -- 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/1627304 Title: User locking problems - guest login crashing Status in gnome-session package in Ubuntu: New Status in lightdm package in Ubuntu: Confirmed Status in lightdm-gtk-greeter package in Ubuntu: Confirmed Status in unity-greeter package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: New Bug description: Vanilla Ubuntu install. Lock user - login to guest account, desktop crashes. Ctrl+Alt+F7 allows you to resume user after unlocking. Add new user - am able to switch between locked users properly. Can logout of one user and be able to resume other locked session. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 24 13:38:09 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1627304/+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 1627304] Re: User locking problems - guest login crashing
A similar issue exists in Xubuntu. Default xubuntu install however does not allow to resume a locked session at all. We've experimented with changing locker from light-locker to gnome- screensaver and xscreensaver - when using gnome-screensaver we see the same as with the Ubuntu issue. bug 1622303 -- 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/1627304 Title: User locking problems - guest login crashing Status in gnome-session package in Ubuntu: New Status in lightdm package in Ubuntu: Confirmed Status in lightdm-gtk-greeter package in Ubuntu: Confirmed Status in unity-greeter package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: New Bug description: Vanilla Ubuntu install. Lock user - login to guest account, desktop crashes. Ctrl+Alt+F7 allows you to resume user after unlocking. Add new user - am able to switch between locked users properly. Can logout of one user and be able to resume other locked session. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 24 13:38:09 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1627304/+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 1627304] [NEW] User locking problems - guest login crashing
Public bug reported: Vanilla Ubuntu install. Lock user - login to guest account, desktop crashes. Ctrl+Alt+F7 allows you to resume user after unlocking. Add new user - am able to switch between locked users properly. Can logout of one user and be able to resume other locked session. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 24 13:38:09 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Affects: lightdm (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: lightdm-gtk-greeter (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: unity-greeter (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: xubuntu-default-settings (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety ** Also affects: lightdm-gtk-greeter (Ubuntu) Importance: Undecided Status: New ** Also affects: unity-greeter (Ubuntu) Importance: Undecided Status: New -- 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/1627304 Title: User locking problems - guest login crashing Status in gnome-session package in Ubuntu: New Status in lightdm package in Ubuntu: Confirmed Status in lightdm-gtk-greeter package in Ubuntu: Confirmed Status in unity-greeter package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: New Bug description: Vanilla Ubuntu install. Lock user - login to guest account, desktop crashes. Ctrl+Alt+F7 allows you to resume user after unlocking. Add new user - am able to switch between locked users properly. Can logout of one user and be able to resume other locked session. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 24 13:38:09 2016 InstallationDate: Installed on 2016-09-24 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1627304/+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 1627299] Re: systemd-resolved crashed with SIGSEGV in sd_event_dispatch()
*** This bug is a duplicate of bug 1621396 *** https://bugs.launchpad.net/bugs/1621396 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1621396, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1627299/+attachment/4747688/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1627299/+attachment/4747691/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1627299/+attachment/4747698/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1627299/+attachment/4747700/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1627299/+attachment/4747701/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1627299/+attachment/4747703/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1627299/+attachment/4747706/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1621396 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1627299 Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch() Status in systemd package in Ubuntu: New Bug description: the crash showed up by itself ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: systemd 231-6git1 ProcVersionSignature: Ubuntu 4.8.0-15.16-generic 4.8.0-rc7 Uname: Linux 4.8.0-15-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Fri Sep 23 12:17:54 2016 ExecutablePath: /lib/systemd/systemd-resolved InstallationDate: Installed on 2013-06-06 (1205 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X ProcCmdline: /lib/systemd/systemd-resolved ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-15-generic root=UUID=2850be62-a05e-4ab9-af2b-5f1fd159ce5d ro quiet splash vt.handoff=7 Signal: 11 SourcePackage: systemd StacktraceTop: ?? () ?? () ?? () from /lib/systemd/libsystemd-shared-231.so sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so sd_event_run () from /lib/systemd/libsystemd-shared-231.so Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch() UpgradeStatus: Upgraded to yakkety on 2016-09-03 (21 days ago) UserGroups: dmi.bios.date: 04/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0PJHXN 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.:rn0PJHXN: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/systemd/+bug/1627299/+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 1377600] Re: ufw errors after ctr+c interupt
Is there any update on the outlook of this? we are hitting ansible failures due to this bug sometimes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1377600 Title: ufw errors after ctr+c interupt Status in ufw package in Ubuntu: Confirmed Bug description: in ufw.util.get_netfilter_capabilities ``` # Cleanup cmd([exe, '-F', chain]) (rc, out) = cmd([exe, '-X', chain]) if rc != 0: raise OSError(errno.ENOENT, out) # pragma: no cover ``` if the `ufw xxx` command is interrupt by ctrl+c, the cleanup is not called, so every ufw cmd afterwards cause error: ``` ERROR: initcaps [Errno 2] iptables: Chain already exists. ``` I think we should catch error and cleanup in a finally statement. Or cleanup related rules before ufw init. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1377600/+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 1543352] Re: inet6 dhcp doesn't wait for link-local address to leave tentative - dhclient fails to bind
This is being worked in bug 1447715. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1543352 Title: inet6 dhcp doesn't wait for link-local address to leave tentative - dhclient fails to bind Status in ifupdown package in Ubuntu: Triaged Bug description: = Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 = With an /etc/network/interfaces file containing: auto eno16780032 iface eno16780032 inet dhcp iface eno16780032 inet6 dhcp On boot, ifup starts 'dhclient -6' before the link local address has completed Duplicate Address Discovery (the address is marked 'tentative'). In turn, dhclient reports 'Can't bind to dhcp address: Cannot assign requested address', and fails almost immediately. It would seem that either wait-for-ll6.sh should wait for the link local address to come up AND stop being tentative, or the dhcp method for inet6 should call settle-dad.sh after wait-for-ll6? This is partly a race condition, so on slower devices the dad may complete by the time dhclient has got started, however I can regularly reproduce this on a virtual machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1543352/+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 1510098] Re: /etc/network/interfaces ipv6 static gateway not set
15.10 is EOL, and this does seem to work in 16.04. Please reopen if you still have this problem in 16.04. ** Changed in: ifupdown (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1510098 Title: /etc/network/interfaces ipv6 static gateway not set Status in ifupdown package in Ubuntu: Invalid Bug description: After installing 15.10 ipv6 gateway not set on start up. In 15.04 it worked fine andrej@nikel:~$ cat /etc/network/interfaces auto lo enp4s0 iface lo inet loopback iface enp4s0 inet manual iface enp4s0 inet6 static address :200:8221::--- netmask 64 gateway 198:20- andrej@nikel:~$ ip -6 route ---0:8221::/64 dev enp4s0 proto kernel metric 256 mtu 1500 pref medium fe80::/64 dev enp4s0 proto kernel metric 256 mtu 1500 pref medium fe80::/64 dev lxcbr0 proto kernel metric 256 pref medium fe80::/64 dev docker0 proto kernel metric 256 pref medium 3: enp4s0: mtu 9000 qdisc pfifo_fast state UP group default qlen 1000 link/ether --7:98 brd ff:ff:ff:ff:ff:ff inet 10.0.4.1/8 brd 10.255.255.255 scope global enp4s0 valid_lft forever preferred_lft forever inet6 200:8221::--/64 scope global valid_lft forever preferred_lft forever inet6 -15:17ff:fe9e:b798/64 scope global mngtmpaddr dynamic valid_lft 83024sec preferred_lft 11024sec inet6 fe80::215:17ff:fe9e:b798/64 scope link valid_lft forever preferred_lft forever andrej@nikel:~$ cat /etc/sysctl.conf net.ipv4.conf.default.rp_filter= 1 net.ipv4.conf.all.rp_filter= 1 net.ipv4.tcp_syncookies= 1 net.ipv6.conf.all.use_tempaddr = 2 net.ipv6.conf.default.use_tempaddr = 2 net.ipv6.conf.enp4s0.use_tempaddr = 2 andrej@nikel:/proc/sys/net/ipv6/conf/enp4s0$ for i in *; do echo -n "$i: " ; cat $i ; done accept_dad: 1 accept_ra: 0 accept_ra_defrtr: 1 accept_ra_from_local: 0 accept_ra_mtu: 1 accept_ra_pinfo: 1 accept_ra_rt_info_max_plen: 0 accept_ra_rtr_pref: 1 accept_redirects: 1 accept_source_route: 0 autoconf: 0 dad_transmits: 1 disable_ipv6: 0 force_mld_version: 0 force_tllao: 0 forwarding: 0 hop_limit: 64 max_addresses: 16 max_desync_factor: 600 mc_forwarding: 0 mldv1_unsolicited_report_interval: 1 mldv2_unsolicited_report_interval: 1000 mtu: 1500 ndisc_notify: 0 proxy_ndp: 0 regen_max_retry: 3 router_probe_interval: 60 router_solicitation_delay: 1 router_solicitation_interval: 4 router_solicitations: 3 cat: stable_secret: Permission denied stable_secret: suppress_frag_ndisc: 1 temp_prefered_lft: 86400 temp_valid_lft: 604800 use_tempaddr: 2 Maybe related: https://bugs.launchpad.net/ubuntu/+source/miredo/+bug/1510047 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ifupdown 0.7.54ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 Date: Mon Oct 26 14:41:55 2015 JournalErrors: No journal files were found. -- No entries -- SourcePackage: ifupdown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1510098/+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 1607681] Re: Mouse cursor goes missing in Gnome apps (GTK on Mir) like Aisleriot and Calculator
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gtk+3.0 (Ubuntu) Status: New => Confirmed -- 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/1607681 Title: Mouse cursor goes missing in Gnome apps (GTK on Mir) like Aisleriot and Calculator Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Mouse cursor goes missing in Gnome apps (GTK on Mir) like Aisleriot and Calculator Just run '/usr/games/sol' under Mir. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1607681/+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 1013597] Re: No default route for stateful DHCPv6
** Changed in: ifupdown (Ubuntu)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: ifupdown (Ubuntu Precise)
Assignee: (unassigned) => Dan Streetman (ddstreet)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1013597
Title:
No default route for stateful DHCPv6
Status in ifupdown package in Ubuntu:
Fix Released
Status in ifupdown source package in Precise:
Triaged
Bug description:
The default route cannot be provided via DHCPv6, it must be obtained
from router advertisements. However, when using the dhcp method for
inet6 in /etc/network/interfaces (e.g. "iface eth0 inet6 dhcp"), ifup
will set net.ipv6.conf..accept_ra=0, resulting in no default
route for IPv6. Instead, it should explicitly set accept_ra=1.
A workaround is to set it in a post-up script. However, Linux
apparently only sends router solicitations when the interface is
brought up, so if unsolicited RA:s are infrequent the host will be
without a default route until the next RA.
Another problem is that when bringing the interface down on dual-stack
hosts, there will be a long timeout. This is because bringing down
IPv4 also brings the interface link down, and afterwards dhclient
cannot release the DHCPv6 lease due to the link being down ("RTNETLINK
answers: Cannot assign requested address"). The workaround is to bring
the link back up before bringing IPv6 down.
So the workarounds (which obviously should not be needed) for a dual-
stack dhcp client look like this:
iface eth0 inet dhcp
iface eth0 inet6 dhcp
up sysctl net.ipv6.conf.$IFACE.accept_ra=1
pre-down ip link set dev $IFACE up
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1013597/+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 1625023] Re: switch to systemd on ubuntu phone xenial
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lxc-android-config (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: Confirmed Status in android-tools package in Ubuntu: Confirmed Status in lxc-android-config package in Ubuntu: Confirmed Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. 2. Install systemd-sysv rather than upstart-sysv (Bug 1625023) 2.1. rebuild latest ubuntu-touch package from source [2] with patch [3] applied. 2.2. download latest systemd-sysv package [4]. 2.3. dpkg -i ubuntu-touch_*.deb systemd-sysv_*.deb 3. Install android-tools-adbd for systemd (Bug 1625023) 3.1. download prebuilt package [5] or recompile it from source [6] with patch [7] applied. 3.2. Install the package from Terminal app because it will break adb connection and interrupt the installation process leaving a very bad state of the package. 4. Install prebuilt lxc-android-config package [8] or just correct its systemd service file by hand as the merge proposal [9] does. (Bug 1625445, bug 1625916 and bug 1626012). 5. Reboot. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/u/ubuntu-touch-meta/ [3]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch [4]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/s/systemd/ [5]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744111/+files/android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb [6]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/a/android-tools/ [7]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4746154/+files/force-adbd.patch [8]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4746148/+files/lxc-android-config_0.230+16.04.20160728-0ubuntu1_all.deb [9]: https://code.launchpad.net/~vicamo/lxc-android-config/fix-systemd-service-startup/+merge/306435 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+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 1625023] Re: switch to systemd on ubuntu phone xenial
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: android-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: Confirmed Status in android-tools package in Ubuntu: Confirmed Status in lxc-android-config package in Ubuntu: Confirmed Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. 2. Install systemd-sysv rather than upstart-sysv (Bug 1625023) 2.1. rebuild latest ubuntu-touch package from source [2] with patch [3] applied. 2.2. download latest systemd-sysv package [4]. 2.3. dpkg -i ubuntu-touch_*.deb systemd-sysv_*.deb 3. Install android-tools-adbd for systemd (Bug 1625023) 3.1. download prebuilt package [5] or recompile it from source [6] with patch [7] applied. 3.2. Install the package from Terminal app because it will break adb connection and interrupt the installation process leaving a very bad state of the package. 4. Install prebuilt lxc-android-config package [8] or just correct its systemd service file by hand as the merge proposal [9] does. (Bug 1625445, bug 1625916 and bug 1626012). 5. Reboot. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/u/ubuntu-touch-meta/ [3]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch [4]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/s/systemd/ [5]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744111/+files/android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb [6]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/a/android-tools/ [7]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4746154/+files/force-adbd.patch [8]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4746148/+files/lxc-android-config_0.230+16.04.20160728-0ubuntu1_all.deb [9]: https://code.launchpad.net/~vicamo/lxc-android-config/fix-systemd-service-startup/+merge/306435 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+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 1627294] [NEW] 'cd' command missing features
Public bug reported: I was surprised to discover that 'cd..' command which i have used in the past, now is unknown. cd. & cd.. features are so simple to use, to step back one level or two, i can't imagine they have been dropped by decisions. Please set them back. oem@u64:~$ cd /var/ oem@u64:/var$ cd lib oem@u64:/var/lib$ cd. No command 'cd.' found, did you mean: Command 'cde' from package 'cde' (universe) Command 'cdv' from package 'codeville' (universe) Command 'cd5' from package 'cd5' (universe) Command 'cdw' from package 'cdw' (universe) Command 'cdo' from package 'cdo' (universe) Command 'cdi' from package 'cdo' (universe) Command 'cdb' from package 'tinycdb' (main) Command 'cdp' from package 'irpas' (multiverse) cd.: command not found oem@u64:/var/lib$ cd.. cd..: command not found ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: bash 4.3-15ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7 Uname: Linux 4.8.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Sep 24 13:18:40 2016 SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bash (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages yakkety ** Description changed: - I was surprised to discover that 'cd..' command which have used in the + I was surprised to discover that 'cd..' command which i have used in the past, now is unknown. cd. & cd.. features are so simple to use, to step back one level or two, i can't imagine they have been dropped by decisions. Please set them back. oem@u64:~$ cd /var/ oem@u64:/var$ cd lib oem@u64:/var/lib$ cd. No command 'cd.' found, did you mean: - Command 'cde' from package 'cde' (universe) - Command 'cdv' from package 'codeville' (universe) - Command 'cd5' from package 'cd5' (universe) - Command 'cdw' from package 'cdw' (universe) - Command 'cdo' from package 'cdo' (universe) - Command 'cdi' from package 'cdo' (universe) - Command 'cdb' from package 'tinycdb' (main) - Command 'cdp' from package 'irpas' (multiverse) + Command 'cde' from package 'cde' (universe) + Command 'cdv' from package 'codeville' (universe) + Command 'cd5' from package 'cd5' (universe) + Command 'cdw' from package 'cdw' (universe) + Command 'cdo' from package 'cdo' (universe) + Command 'cdi' from package 'cdo' (universe) + Command 'cdb' from package 'tinycdb' (main) + Command 'cdp' from package 'irpas' (multiverse) cd.: command not found oem@u64:/var/lib$ cd.. cd..: command not found ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: bash 4.3-15ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7 Uname: Linux 4.8.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Sep 24 13:18:40 2016 SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1627294 Title: 'cd' command missing features Status in bash package in Ubuntu: New Bug description: I was surprised to discover that 'cd..' command which i have used in the past, now is unknown. cd. & cd.. features are so simple to use, to step back one level or two, i can't imagine they have been dropped by decisions. Please set them back. oem@u64:~$ cd /var/ oem@u64:/var$ cd lib oem@u64:/var/lib$ cd. No command 'cd.' found, did you mean: Command 'cde' from package 'cde' (universe) Command 'cdv' from package 'codeville' (universe) Command 'cd5' from package 'cd5' (universe) Command 'cdw' from package 'cdw' (universe) Command 'cdo' from package 'cdo' (universe) Command 'cdi' from package 'cdo' (universe) Command 'cdb' from package 'tinycdb' (main) Command 'cdp' from package 'irpas' (multiverse) cd.: command not found oem@u64:/var/lib$ cd.. cd..: command not found ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: bash 4.3-15ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7 Uname: Linux 4.8.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Sep 24 13:18:40 2016 SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1627294/+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/Li
[Touch-packages] [Bug 1445376] Re: A2DP skips when conneted to handsfree device
Hi all, Me too Ican notice a great improvement by updating OTA13. Many thanks fo make my phone being able to: -pair immediantly with in-car hands free kac bt200. -downloading and sync contacts phonebooks. I can also browse contacts from my car dissplay controller, and start a call too. - starting as well as receiving a call by ringing tone and muting car audi systems. But phone call audio still does not work. I neinther both direction. I always need to switch manually from bt audio to phone internal speaker. Always BQ E5 HD Ota 13. BR D -- 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/1445376 Title: A2DP skips when conneted to handsfree device Status in Canonical System Image: Incomplete Status in bluez package in Ubuntu: Confirmed Bug description: When I connect my Aquaris E4.5 to my car's handsfree device (Funkwerk Ego Flash) via Bluetooth I experience a skipping problem when playing sound files through A2DP. Half a second for each second there is a pause. The rest of that half second seems to clear a buffer which results in "extra fast" audio. To illustrate, listening to a podcast I would expect to hear something like "bla bla bla". However, what I do get to hear sounds more like "flapflapflap - pause - flapflapflap - pause - ...". When I connect my Aquaris to my A2DP speakers at home, the audio is perfect. Also, handsfree telephony in my car works like a charm. So I guess it's just the combination of A2DP while connected to the handsfree device which causes the trouble. In the past I've used several phones with the Funkwerk device (always with handsfree *and* A2DP functionality) including an N900 running Maemo. There have never been any problems with those. OS build number 21 KRILIN01A-S15A_BQ_L100EN_2021_150410 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445376/+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 1627291] Re: Apps scope empty
** Attachment added: "unity8-dash.log" https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1627291/+attachment/4747670/+files/unity8-dash.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1627291 Title: Apps scope empty Status in unity8 package in Ubuntu: New Bug description: Apps scope empty ubuntu 16.10 + proposed / x86 / nvidia unity8/yakkety-proposed,now 8.14+16.10.20160922-0ubuntu1 amd64 [installed,automatic] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1627291/+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 1627291] Re: Apps scope empty
** Attachment added: "scope-registry.log" https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1627291/+attachment/4747668/+files/scope-registry.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1627291 Title: Apps scope empty Status in unity8 package in Ubuntu: New Bug description: Apps scope empty ubuntu 16.10 + proposed / x86 / nvidia unity8/yakkety-proposed,now 8.14+16.10.20160922-0ubuntu1 amd64 [installed,automatic] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1627291/+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
