[Touch-packages] [Bug 1641505] Re: support adbd emergency shell under systemd
With the two patches, one may test adbd emergency shell manually by replacing ExecStart command with `/bin/false` in either lxc-android- config or lightdm systemd service. ** Branch linked: lp:~vicamo/lxc-android-config/adbd-emergency-shell ** Changed in: android-tools (Ubuntu) Status: New => In Progress ** Changed in: lxc-android-config (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641505 Title: support adbd emergency shell under systemd Status in Canonical System Image: New Status in android-tools package in Ubuntu: In Progress Status in lxc-android-config package in Ubuntu: In Progress Bug description: Currently adbd emergency shell is only available under upstart, so some work is needed to bring it up under systemd as well. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641505/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641505] Re: support adbd emergency shell under systemd
Patch for source package android-tools to add a systemd ExecStopPost hook /usr/lib/android-tools-adbd/start-emergency-shell for other packages. ** Patch added: "0001-Add-adbd-emergency-shell-systemd-support.patch" https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1641505/+attachment/4777092/+files/0001-Add-adbd-emergency-shell-systemd-support.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to android-tools in Ubuntu. https://bugs.launchpad.net/bugs/1641505 Title: support adbd emergency shell under systemd Status in Canonical System Image: New Status in android-tools package in Ubuntu: New Status in lxc-android-config package in Ubuntu: New Bug description: Currently adbd emergency shell is only available under upstart, so some work is needed to bring it up under systemd as well. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641505/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641505] [NEW] support adbd emergency shell under systemd
Public bug reported: Currently adbd emergency shell is only available under upstart, so some work is needed to bring it up under systemd as well. ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: android-tools (Ubuntu) Importance: Undecided Assignee: Vicamo Yang (vicamo) Status: New ** Affects: lxc-android-config (Ubuntu) Importance: Undecided Assignee: Vicamo Yang (vicamo) Status: New ** Tags: systemd ** Tags added: systemd ** Also affects: lxc-android-config (Ubuntu) Importance: Undecided Status: New ** Also affects: android-tools (Ubuntu) Importance: Undecided Status: New ** Changed in: android-tools (Ubuntu) Assignee: (unassigned) => Vicamo Yang (vicamo) ** Changed in: lxc-android-config (Ubuntu) Assignee: (unassigned) => Vicamo Yang (vicamo) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641505 Title: support adbd emergency shell under systemd Status in Canonical System Image: New Status in android-tools package in Ubuntu: New Status in lxc-android-config package in Ubuntu: New Bug description: Currently adbd emergency shell is only available under upstart, so some work is needed to bring it up under systemd as well. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641505/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1533631] Re: dhclient killed when DHCPv6 lease is out-of date
Same problem on xubuntu 16.10 with:
network-manager 1.2.4-0ubuntu1
isc-dhcp-client 4.3.3-5ubuntu15
--
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/1533631
Title:
dhclient killed when DHCPv6 lease is out-of date
Status in NetworkManager:
Confirmed
Status in isc-dhcp package in Ubuntu:
In Progress
Status in network-manager package in Ubuntu:
In Progress
Bug description:
Network Manager summarily kills the IPv6 dhclient process when the
DHCPv6 lease contained in the dhclient6-${UUID}.lease file is out-of
date, leaving the IPv6 interface without a stateful IPv6 address, or,
if the "require IPv6 address on this interface" option is enabled,
causes NM to cycle continuously deactivating and reactivating the
interface (including the IPv4 addresses).
This is effectively a Denial Of Service. It can be trivially induced
if, for example, the dhclient6-$(UUID}.lease file contains a lease
that was issued before the user went away on vacation or the PC wasn't
connected to the same network for a few days (depending on the lease
renew/rebind/expiry times). Calculation on the old lease of
start + preferred_lifetime < NOW
triggers dhclient to 'DEPREFER6' the lease (withdraw the address
record) and ask the DHCPv6 server for a new lease, but Network Manager
will kill the dhclient because it only sees an 'EXPIRE6' state change.
In summary, when the DHCPv6 state transitions from "bound" to
"unknown" then "expire" to "done" Network Manager kills the 'dhclient'
process before it has chance to request and bind a fresh lease, If
'dhclient' is run manually with the same command-line options and
allowed to continue running it correctly gains a new lease.
Network Manager doesn't know how to handle "DEPREF6", which is sent
from isc-dhcp dhclient to the helper script (set by "-sf" option).
So it seems that to correctly solve this issue Network Manager must be
taught how to handle DEPREF6.
/var/log/syslog will show a message from dhclient of the form:
dhclient: PRC: Address 2a02:8011:2007::2 depreferred.
To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1533631/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1613949] Re: vim-gtk3 Has Unmet Dependencies After `apt-get upgrade` In Ubuntu 16.04.1 Xenial
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1613949 Title: vim-gtk3 Has Unmet Dependencies After `apt-get upgrade` In Ubuntu 16.04.1 Xenial Status in vim package in Ubuntu: Expired Bug description: I have a fresh install of Ubuntu v16.04.1, then I did an `apt-get upgrade` and it only had a few seemingly-minor packages to upgrade (don't remember the list, sorry). Apparently all the core vim packages have been upgraded to 2:7.4.1689-3ubuntu1.1 but vim-gtk3 (and all the other gvim-providing packages I tested) are still held back to 2:7.4.1689-3ubuntu1 so there is a version mis-match. Now I get the following error: [[[ BEGIN PASTE ]]] root@machine:/# apt-get install vim-gtk3 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: vim-gtk3 : Depends: vim-common (= 2:7.4.1689-3ubuntu1) but 2:7.4.1689-3ubuntu1.1 is to be installed Depends: vim-runtime (= 2:7.4.1689-3ubuntu1) but 2:7.4.1689-3ubuntu1.1 is to be installed E: Unable to correct problems, you have held broken packages. [[[ END PASTE ]]] However I can still get gvim working if I force the installation of the vim-gtk3 package using dpkg. Of course this is not a good solution, because it leaves my system in a state of seemingly-broken packages! [[[ BEGIN PASTE ]]] root@machine:/# dpkg -i --force-depends ./vim-gtk3_7.4.1689-3ubuntu1_amd64.deb Selecting previously unselected package vim-gtk3. (Reading database ... 251539 files and directories currently installed.) Preparing to unpack .../vim-gtk3_7.4.1689-3ubuntu1_amd64.deb ... Unpacking vim-gtk3 (2:7.4.1689-3ubuntu1) ... dpkg: vim-gtk3: dependency problems, but configuring anyway as you requested: vim-gtk3 depends on vim-common (= 2:7.4.1689-3ubuntu1); however: Version of vim-common on system is 2:7.4.1689-3ubuntu1.1. vim-gtk3 depends on vim-runtime (= 2:7.4.1689-3ubuntu1); however: Version of vim-runtime on system is 2:7.4.1689-3ubuntu1.1. Setting up vim-gtk3 (2:7.4.1689-3ubuntu1) ... update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/vim (vim) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/vimdiff (vimdiff) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/rvim (rvim) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/rview (rview) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/vi (vi) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/view (view) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/ex (ex) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/editor (editor) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/gvim (gvim) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/gview (gview) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/rgview (rgview) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/rgvim (rgvim) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/evim (evim) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/eview (eview) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/gvimdiff (gvimdiff) in auto mode [[[ END PASTE ]]] And yes, I can confirm that gvim actually works using this method. We just need to upgrade the package versioning so that we don't have a problem with the apt-get packaging dependency system. Thanks for all your hard work. Ubuntu is #1!!! :-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1613949/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641415] Re: screen dimmed after suspend
** Package changed: lightdm (Ubuntu) => unity (Ubuntu) -- 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/1641415 Title: screen dimmed after suspend Status in unity package in Ubuntu: New Bug description: Often, waking the computer up from suspend will cause the screen brightness to be set right down (was 100% before suspend, becomes ~ 20% after waking). This happens during 40-70% of all suspends. I have not yet been able to figure out any correlations with previous activity, so the behaviour seems random. (I assume this is a LightDM problem, because it first manifests itself in the login screen, but I'm not sure.) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 13 15:39:26 2016 InstallationDate: Installed on 2016-07-15 (120 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1641415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1640443] Re: Spread lags a bit at the start
Sounds like bug 1518935? -- 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/1640443 Title: Spread lags a bit at the start Status in Canonical System Image: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: N4 rc-proposed Steps to reproduce: 1. Open a couple of apps 2. Swipe from the right edge to open the spread. Do this few times with varying speeds. What happens: The spread lags a tiny bit while the apps are being cropped into a square shape What should happen: The spread is smooth and fluid like the previous one. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1640443/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1637157] Re: App geometry cache gets corrupted
** Changed in: unity8 (Ubuntu) Importance: Undecided => High ** Changed in: unity8 (Ubuntu) Status: Incomplete => Confirmed ** Tags added: unity8-desktop ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Importance: Undecided => High ** Changed in: canonical-devices-system-image Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1637157 Title: App geometry cache gets corrupted Status in Canonical System Image: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: bq M10 rc-proposed r219 If an app does not set its minimal size, the default size of its window is too small. See the screenshot attached. And guess the opened apps To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1637157/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641341] Re: Apps don't scale with the window while using external display and windowed mode
** Tags added: android multi-monitor unity8-desktop ** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- 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/1641341 Title: Apps don't scale with the window while using external display and windowed mode Status in Canonical System Image: New Status in qtmir package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Description: When in desktop mode and connected to an external display, apps do not scale properly to its window on initial load. It will correct the scale once you resize the window. Steps to Reproduce: 1. Connect to an external display. 2. Switch to Desktop mode if not yet in this mode. 3. Open an app. Not sure if all apps are affected but the two apps open in the screenshot attached are affected. Device: Nexus 7 2013 rc-proposed I think this is a bug when the grid unit changes when using an external display. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641341/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1582979] Re: package linux-image-3.16.0-71-generic 3.16.0-71.92~14.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Finally I figured out the error seems happened when dealing with fuse, so I uninstalled fuse and fuse again, it then update all the initrm packages of each kernel, then I am able to remove old kernels. I think this is caused that once I installed libfuse from source code, it may changed the system configuration. ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1582979 Title: package linux-image-3.16.0-71-generic 3.16.0-71.92~14.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Invalid Bug description: Just happened after software update, I did not restart, instead, I powered off and powered on the next day. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-71-generic 3.16.0-71.92~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-71.92~14.04.1-generic 3.16.7-ckt27 Uname: Linux 3.16.0-71-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Tue May 17 23:32:21 2016 DuplicateSignature: package:linux-image-3.16.0-71-generic:3.16.0-71.92~14.04.1:run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2015-12-06 (163 days ago) InstallationMedia: Edubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) RelatedPackageVersions: dpkg 1.17.5ubuntu5.6 apt 1.0.1ubuntu2.13 SourcePackage: initramfs-tools Title: package linux-image-3.16.0-71-generic 3.16.0-71.92~14.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1582979/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1537036] Re: package linux-image-extra-3.16.0-55-generic 3.16.0-55.74~14.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code
My disk has lot of space available so it is caused by "No space left...": /dev/sdb1 217G 32G 174G 16% / Now I cannot update kernel, nor I cannot delete old ones. I have the followins in /lib/modules: drwxr-xr-x 5 root root 4096 Nov 13 18:20 3.16.0-55-generic drwxr-xr-x 5 root root 4096 Dec 18 2015 3.16.0-56-generic drwxr-xr-x 5 root root 4096 Dec 22 2015 3.16.0-57-generic drwxr-xr-x 5 root root 4096 Feb 7 2016 3.16.0-60-generic drwxr-xr-x 5 root root 4096 Mar 6 2016 3.16.0-62-generic drwxr-xr-x 5 root root 4096 Mar 20 2016 3.16.0-67-generic drwxr-xr-x 5 root root 4096 Apr 18 2016 3.16.0-70-generic drwxr-xr-x 5 root root 4096 Nov 13 18:19 3.16.0-71-generic and followings in my /boot: -rw-r--r-- 1 root root 1207789 Nov 17 2015 abi-3.16.0-55-generic -rw-r--r-- 1 root root 1207863 Dec 2 2015 abi-3.16.0-56-generic -rw-r--r-- 1 root root 1207863 Dec 17 2015 abi-3.16.0-57-generic -rw-r--r-- 1 root root 1207806 Jan 20 2016 abi-3.16.0-60-generic -rw-r--r-- 1 root root 1207895 Feb 26 2016 abi-3.16.0-62-generic -rw-r--r-- 1 root root 1207960 Mar 10 2016 abi-3.16.0-67-generic -rw-r--r-- 1 root root 1208280 Apr 6 2016 abi-3.16.0-70-generic -rw-r--r-- 1 root root 1208553 May 12 2016 abi-3.16.0-71-generic -rw-r--r-- 1 root root 171832 Nov 17 2015 config-3.16.0-55-generic -rw-r--r-- 1 root root 171832 Dec 2 2015 config-3.16.0-56-generic -rw-r--r-- 1 root root 171832 Dec 17 2015 config-3.16.0-57-generic -rw-r--r-- 1 root root 171832 Jan 20 2016 config-3.16.0-60-generic -rw-r--r-- 1 root root 171832 Feb 26 2016 config-3.16.0-62-generic -rw-r--r-- 1 root root 171832 Mar 10 2016 config-3.16.0-67-generic -rw-r--r-- 1 root root 171832 Apr 6 2016 config-3.16.0-70-generic -rw-r--r-- 1 root root 171832 May 12 2016 config-3.16.0-71-generic drwxr-xr-x 5 root root 4096 Aug 20 23:12 grub -rw-r--r-- 1 root root 20273671 Dec 7 2015 initrd.img-3.16.0-55-generic -rw-r--r-- 1 root root 20272605 Dec 18 2015 initrd.img-3.16.0-56-generic -rw-r--r-- 1 root root 20273721 Dec 22 2015 initrd.img-3.16.0-57-generic -rw-r--r-- 1 root root 20274736 Feb 26 2016 initrd.img-3.16.0-60-generic -rw-r--r-- 1 root root 20274434 Mar 6 2016 initrd.img-3.16.0-62-generic -rw-r--r-- 1 root root 20281508 Mar 29 2016 initrd.img-3.16.0-67-generic -rw-r--r-- 1 root root 20282111 Apr 18 2016 initrd.img-3.16.0-70-generic -rw-r--r-- 1 root root 20296847 May 11 2016 initrd.img-3.16.0-71-generic -rw-r--r-- 1 root root 176500 Mar 12 2014 memtest86+.bin -rw-r--r-- 1 root root 178176 Mar 12 2014 memtest86+.elf -rw-r--r-- 1 root root 178680 Mar 12 2014 memtest86+_multiboot.bin -rw--- 1 root root 3517011 Nov 17 2015 System.map-3.16.0-55-generic -rw--- 1 root root 3517268 Dec 2 2015 System.map-3.16.0-56-generic -rw--- 1 root root 3517268 Dec 17 2015 System.map-3.16.0-57-generic -rw--- 1 root root 3517575 Jan 20 2016 System.map-3.16.0-60-generic -rw--- 1 root root 3517939 Feb 26 2016 System.map-3.16.0-62-generic -rw--- 1 root root 3518178 Mar 10 2016 System.map-3.16.0-67-generic -rw--- 1 root root 3518365 Apr 6 2016 System.map-3.16.0-70-generic -rw--- 1 root root 3519833 May 12 2016 System.map-3.16.0-71-generic -rw--- 1 root root 6359472 Nov 17 2015 vmlinuz-3.16.0-55-generic -rw--- 1 root root 6360880 Dec 2 2015 vmlinuz-3.16.0-56-generic -rw--- 1 root root 6361776 Dec 17 2015 vmlinuz-3.16.0-57-generic -rw--- 1 root root 6364112 Jan 20 2016 vmlinuz-3.16.0-60-generic -rw--- 1 root root 6361856 Feb 26 2016 vmlinuz-3.16.0-62-generic -rw--- 1 root root 6364432 Mar 10 2016 vmlinuz-3.16.0-67-generic -rw--- 1 root root 6365328 Apr 6 2016 vmlinuz-3.16.0-70-generic -rw--- 1 root root 6376592 May 12 2016 vmlinuz-3.16.0-71-generic It tries to remove linux-image-3.16.0-73 and linux-image-3.16.0-76 even I don't have them. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1537036 Title: package linux-image-extra-3.16.0-55-generic 3.16.0-55.74~14.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d /initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: hangs after login in ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.16.0-55-generic 3.16.0-55.74~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-59.79~14.04.1-generic 3.16.7-ckt20 Uname: Linux 3.16.0-59-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 AptOrdering: linux-signed-image-3.16.0-55-generic: Purge linux-image-extra-3.16.0-55-generic: Purge linux-image-3.16.0-55-generic: Purge initramfs-tools: Configure Architecture: amd64 Date: Fri Jan 22 13:46:01 2016 DuplicateSignature: package:linux-image-extra-3.16.0-55-generic:3.16.0-55.74~14.04.1:run-parts:
[Touch-packages] [Bug 1537036] Re: package linux-image-extra-3.16.0-55-generic 3.16.0-55.74~14.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code
** Changed in: initramfs-tools (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1537036 Title: package linux-image-extra-3.16.0-55-generic 3.16.0-55.74~14.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d /initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: hangs after login in ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-extra-3.16.0-55-generic 3.16.0-55.74~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-59.79~14.04.1-generic 3.16.7-ckt20 Uname: Linux 3.16.0-59-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 AptOrdering: linux-signed-image-3.16.0-55-generic: Purge linux-image-extra-3.16.0-55-generic: Purge linux-image-3.16.0-55-generic: Purge initramfs-tools: Configure Architecture: amd64 Date: Fri Jan 22 13:46:01 2016 DuplicateSignature: package:linux-image-extra-3.16.0-55-generic:3.16.0-55.74~14.04.1:run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2015-05-19 (248 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.10 SourcePackage: initramfs-tools Title: package linux-image-extra-3.16.0-55-generic 3.16.0-55.74~14.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1537036/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641468] [NEW] systemd-resolve: fallback from resolve causes lookup of local network hosts to fail
Public bug reported: After upgrading to Ubuntu 16.10 from 16.04, DNS resolution of hosts on my local network fails. The hosts line in /etc/nsswitch.conf is: hosts: files mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] dns mdns4 If I change it to: hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4 I can resolve hosts on my local network. Appending .local to the hostname also allows DNS resolution since systemd-resolve returns a different error for that case. Ex: systemd-resolve rt-ac66u rt-ac66u: resolve call failed: All attempts to contact name servers or networks failed systemd-resolve rt-ac66u.local rt-ac66u.local: resolve call failed: No appropriate name servers or networks for name found "dig rt-ac66u" returns the correct ip. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1641468 Title: systemd-resolve: fallback from resolve causes lookup of local network hosts to fail Status in systemd package in Ubuntu: New Bug description: After upgrading to Ubuntu 16.10 from 16.04, DNS resolution of hosts on my local network fails. The hosts line in /etc/nsswitch.conf is: hosts: files mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] dns mdns4 If I change it to: hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4 I can resolve hosts on my local network. Appending .local to the hostname also allows DNS resolution since systemd-resolve returns a different error for that case. Ex: systemd-resolve rt-ac66u rt-ac66u: resolve call failed: All attempts to contact name servers or networks failed systemd-resolve rt-ac66u.local rt-ac66u.local: resolve call failed: No appropriate name servers or networks for name found "dig rt-ac66u" returns the correct ip. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1641468/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641467] [NEW] Mouse flickering and disappearing near the top of screen
Public bug reported: So I'm not sure this is an xorg bug, I couldn't figure out what xorg is. But I recently upgraded to ubuntu 16.10 and started seeing this bug where my mouse will flicker and disappear when near the top of the screen. It still works clicking-wise. It also seems to be especially severe when using Google Chrome, where it completely disappears and flickers the entire time while mousing over the menu uptions (i.e the close button, the tabs etc...). However recently I noticed this also happens when google chrome is off, though it flickers much less. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Nov 14 00:01:59 2016 DistUpgraded: 2016-11-11 16:58:41,906 DEBUG icon theme changed, re-reading DistroCodename: yakkety DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family Integrated Graphics Controller [144d:c0a5] Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5] InstallationDate: Installed on 2016-08-30 (74 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic root=UUID=8efe8f71-2303-4aff-921a-1f80026e1b6e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to yakkety on 2016-11-11 (2 days ago) dmi.bios.date: 03/02/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 15HX.M042.20120302.SSH dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: RF511/RF411/RF711 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: 15HX dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr15HX.M042.20120302.SSH:bd03/02/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pnRF511/RF411/RF711:pvr15HX:rvnSAMSUNGELECTRONICSCO.,LTD.:rnRF511/RF411/RF711:rvr15HX:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: RF511/RF411/RF711 dmi.product.version: 15HX dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Sun Nov 13 17:46:35 2016 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu yakkety -- 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/1641467 Title: Mouse flickering and disappearing near the top of screen Status in xorg package in Ubuntu: New Bug description: So I'm not sure this is an xorg bug, I couldn't figure out what xorg is. But I recently upgraded to ubuntu 16.10 and started seeing this bug where my mouse will flicker and disappear when near the top of the screen. It still works clicking-wise. It also seems to be especially severe when using Google Chrome, where it completely disappears and flickers the entire time while mousing over the menu uptions (i.e the close button, the tabs etc...). However recently I noticed this also happens when google chrome is off, though it flickers much less. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu
[Touch-packages] [Bug 1641465] Re: Battery icon changes in too rough steps
Sorry, the screenshot is zoomed by a factor of 10 (I have no clue why I wrote "two" instead). ** Description changed: - I attach a screenshot zoomed by a factor of two, showing the battery + I attach a screenshot zoomed by a factor of ten, showing the battery icon at 50% and 49% charge. At 50% charge, the bar is 11px wide out of the available 18px width. At 49% charge it's suddenly only 7px out of 18. Neither of these two make any sense to me. Could you please make the width decrease by 1px at each 5.55% of charge, and especially make it exactly half wide at 50%? (Or even nicer: increase the overall width of - the bar to 20% so that it jumps exactly 1px at every 5%?) + the bar to 20px so that it jumps exactly 1px at every 5%?) ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: indicator-power 12.10.6+16.10.20160708-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 13 23:50:45 2016 InstallationDate: Installed on 2016-11-09 (3 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: indicator-power 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 indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1641465 Title: Battery icon changes in too rough steps Status in indicator-power package in Ubuntu: New Bug description: I attach a screenshot zoomed by a factor of ten, showing the battery icon at 50% and 49% charge. At 50% charge, the bar is 11px wide out of the available 18px width. At 49% charge it's suddenly only 7px out of 18. Neither of these two make any sense to me. Could you please make the width decrease by 1px at each 5.55% of charge, and especially make it exactly half wide at 50%? (Or even nicer: increase the overall width of the bar to 20px so that it jumps exactly 1px at every 5%?) ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: indicator-power 12.10.6+16.10.20160708-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 13 23:50:45 2016 InstallationDate: Installed on 2016-11-09 (3 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: indicator-power UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1641465/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1639533] Re: Failure to update ~/.xsession-errors
** Branch linked: lp: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/1639533 Title: Failure to update ~/.xsession-errors Status in lightdm package in Ubuntu: In Progress Bug description: When there is an error in e.g. ~/.profile or /etc/profile, a zenity warning dialog is shown at login which calls the user's attention to the error. The error message should also be appended to ~/.xsession- errors, but currently it's not. Changing the line cat "$ERR" >>/dev/stderr in /usr/sbin/lightdm-session to cat "$ERR" >&2 fixes it. (It used to work in trusty, but not any longer, so in part it appears to be some SRU regression.) Since possible error messages are shown in the zenity dialog, I don't think this is important enough to backport. Prepared an MP for zesty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1639533/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641465] Re: Battery icon changes in too rough steps
** Attachment added: "Screenshots at 10x zoom" https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1641465/+attachment/4777023/+files/battery.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1641465 Title: Battery icon changes in too rough steps Status in indicator-power package in Ubuntu: New Bug description: I attach a screenshot zoomed by a factor of ten, showing the battery icon at 50% and 49% charge. At 50% charge, the bar is 11px wide out of the available 18px width. At 49% charge it's suddenly only 7px out of 18. Neither of these two make any sense to me. Could you please make the width decrease by 1px at each 5.55% of charge, and especially make it exactly half wide at 50%? (Or even nicer: increase the overall width of the bar to 20px so that it jumps exactly 1px at every 5%?) ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: indicator-power 12.10.6+16.10.20160708-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 13 23:50:45 2016 InstallationDate: Installed on 2016-11-09 (3 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: indicator-power UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1641465/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641465] [NEW] Battery icon changes in too rough steps
Public bug reported: I attach a screenshot zoomed by a factor of ten, showing the battery icon at 50% and 49% charge. At 50% charge, the bar is 11px wide out of the available 18px width. At 49% charge it's suddenly only 7px out of 18. Neither of these two make any sense to me. Could you please make the width decrease by 1px at each 5.55% of charge, and especially make it exactly half wide at 50%? (Or even nicer: increase the overall width of the bar to 20px so that it jumps exactly 1px at every 5%?) ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: indicator-power 12.10.6+16.10.20160708-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 13 23:50:45 2016 InstallationDate: Installed on 2016-11-09 (3 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: indicator-power UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: indicator-power (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1641465 Title: Battery icon changes in too rough steps Status in indicator-power package in Ubuntu: New Bug description: I attach a screenshot zoomed by a factor of ten, showing the battery icon at 50% and 49% charge. At 50% charge, the bar is 11px wide out of the available 18px width. At 49% charge it's suddenly only 7px out of 18. Neither of these two make any sense to me. Could you please make the width decrease by 1px at each 5.55% of charge, and especially make it exactly half wide at 50%? (Or even nicer: increase the overall width of the bar to 20px so that it jumps exactly 1px at every 5%?) ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: indicator-power 12.10.6+16.10.20160708-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 13 23:50:45 2016 InstallationDate: Installed on 2016-11-09 (3 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: indicator-power UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1641465/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1612367] Re: [Touch] Incoming call gets silent randomly
This affects me too on my E5. When it happens not only the ring of the call is muted but all application can't play sounds trough the bigger speaker. Please we must find a fix. I notice this since ota 11. Can someone tell me which app manages all sounds and speakers? Is it media-hub? -- 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/1612367 Title: [Touch] Incoming call gets silent randomly Status in Canonical System Image: Confirmed Status in media-hub package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I've experienced this strange issue 4-5 times after OTA-12. It seems pretty random and is hard to reproduce. When I get an incoming call, the screen turns on, the incoming call pop up appears, but there is no sound at all even though the phone is not in silent mode (and also the speaker volume is not set too low). I can accept this call and keep conversing as usual. Once I asked the same caller to call me once again after a few minutes, that time the phone rang as expected. Device: E5, OTA-12, stable channel I can provide necessary logs if this happens again. Which ones should I gather? Possibly related to bug #1614943. UPDATE: As mentioned in comment #7, it seems the phone rings for a fraction of a second and then the sound pauses abruptly. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1612367/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641341] Re: Apps don't scale with the window while using external display and windowed mode
** Also affects: qtmir (Ubuntu) Importance: Undecided Status: New -- 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/1641341 Title: Apps don't scale with the window while using external display and windowed mode Status in qtmir package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Description: When in desktop mode and connected to an external display, apps do not scale properly to its window on initial load. It will correct the scale once you resize the window. Steps to Reproduce: 1. Connect to an external display. 2. Switch to Desktop mode if not yet in this mode. 3. Open an app. Not sure if all apps are affected but the two apps open in the screenshot attached are affected. Device: Nexus 7 2013 rc-proposed I think this is a bug when the grid unit changes when using an external display. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1641341/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641440] Re: systemd-udevd does not work as expected using custom rules
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: systemd (Ubuntu)
** Package changed: ubuntu => systemd (Ubuntu)
--
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/1641440
Title:
systemd-udevd does not work as expected using custom rules
Status in systemd package in Ubuntu:
New
Bug description:
Hi!
In this example I'm using an external USB-Keyboard to trigger a rule
on plugin/-off. The same example works in Arch, but not in (K)Ubuntu
16.10.
System:
Thinkpad X220:
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.10
Release:16.10
Codename: yakkety
Kernel: Linux x220 4.8.0-27-generic #29-Ubuntu SMP Thu Oct 20 21:03:13 UTC
2016 x86_64 x86_64 x86_64 GNU/Linux
I used following steps to reproduce:
Check device:
cmd: lsusb
output: Bus 001 Device 005: ID 1267:0103 Logic3 / SpectraVideo plc G-720
Keyboard
cmd: udevadm monitor
1.Plugin keyboard
2.Check shortest path
my example: /devices/pci:00/:00:1a.0/usb1/1-1/1-1.2
cmd: udevadm -a -p /devices/pci:00/:00:1a.0/usb1/1-1/1-1.2 | egrep
"SUBSYSTEM|idProduct|idVendor"
output:
SUBSYSTEM=="usb"
ATTR{idProduct}=="0103"
ATTR{idVendor}=="1267"
Create rule:
nano /etc/udev/rules.d/99-numlocker.rules
content: ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="1267",
ATTRS{idProduct}=="0103" RUN+="/bin/sh -c '/usr/bin/touch
/home/kubuntu/plugged'", ENV{REMOVE_CMD}="/bin/sh -c '/bin/rm
/home/kubuntu/plugged'"}}}
Test rule:
cmd: udevadm test /devices/pci:00/:00:1a.0/usb1/1-1/1-1.2
shortened output:
...Reading rules file: /lib/udev/rules.d/99-systemd.rules
rules contain 393216 bytes tokens (32768 * 12 bytes), 37025 bytes strings
27127 strings (224162 bytes), 23453 de-duplicated (190812 bytes), 3675 trie
nodes used
value '[dmi/id]sys_vendor' is 'LENOVO'
value '[dmi/id]sys_vendor' is 'LENOVO'
IMPORT builtin 'usb_id' /lib/udev/rules.d/50-udev-default.rules:13
IMPORT builtin 'hwdb' /lib/udev/rules.d/50-udev-default.rules:13
MODE 0664 /lib/udev/rules.d/50-udev-default.rules:41
PROGRAM 'mtp-probe /sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.2 1 6'
/lib/udev/rules.d/69-libmtp.rules:2167
starting 'mtp-probe /sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.2 1 6'
'mtp-probe /sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.2 1 6'(out) '0'
Process 'mtp-probe /sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.2 1 6'
succeeded.
RUN '/lib/udev/tlp-usb-udev %p' /lib/udev/rules.d/85-tlp.rules:10
RUN '/bin/sh -c '/bin/rm /home/kubuntu/plugged''
/etc/udev/rules.d/99-numlocker.rules:6
handling device node '/dev/bus/usb/001/006', devnum=c189:5, mode=0664, uid=0,
gid=0
preserve permissions /dev/bus/usb/001/006, 020664, uid=0, gid=0
preserve already existing symlink '/dev/char/189:5' to '../bus/usb/001/006'
created db file '/run/udev/data/c189:5' for
'/devices/pci:00/:00:1a.0/usb1/1-1/1-1.2'
ACTION=add
BUSNUM=001
DEVNAME=/dev/bus/usb/001/006
DEVNUM=006
DEVPATH=/devices/pci:00/:00:1a.0/usb1/1-1/1-1.2
DEVTYPE=usb_device
DRIVER=usb
ID_BUS=usb
ID_MODEL=0103
ID_MODEL_ENC=0103
ID_MODEL_FROM_DATABASE=G-720 Keyboard
ID_MODEL_ID=0103
ID_REVISION=0101
ID_SERIAL=1267_0103
ID_USB_INTERFACES=:030101:03:
ID_VENDOR=1267
ID_VENDOR_ENC=1267
ID_VENDOR_FROM_DATABASE=Logic3 / SpectraVideo plc
ID_VENDOR_ID=1267
MAJOR=189
MINOR=5
PRODUCT=1267/103/101
REMOVE_CMD=/bin/sh -c '/bin/rm /home/kubuntu/plugged'
SUBSYSTEM=usb
TYPE=0/0/0
USEC_INITIALIZED=68681993
run: '/lib/udev/tlp-usb-udev /devices/pci:00/:00:1a.0/usb1/1-1/1-1.2'
run: '/bin/sh -c '/usr/bin/touch /home/kubuntu/plugged''
Unload module index
Unloaded link configuration context.
I've tried following to load rules:
> udevadm control -R
> systemctl restart systemd-udevd
> reboot
Nothing seems to work. Even after a few days and reboots it keeps the same,
BUT there's a "workaround":
After every reboot use:
systemctl stop systemd-udevd
systemctl start systemd-udevd
and the rule works.
Could anyone give me a hint why this does not work as expected in
Kubuntu 16.10 or can confirm this?
Thanks in advance!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1641440/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641440] [NEW] systemd-udevd does not work as expected using custom rules
You have been subscribed to a public bug:
Hi!
In this example I'm using an external USB-Keyboard to trigger a rule on
plugin/-off. The same example works in Arch, but not in (K)Ubuntu 16.10.
System:
Thinkpad X220:
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.10
Release:16.10
Codename: yakkety
Kernel: Linux x220 4.8.0-27-generic #29-Ubuntu SMP Thu Oct 20 21:03:13 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
I used following steps to reproduce:
Check device:
cmd: lsusb
output: Bus 001 Device 005: ID 1267:0103 Logic3 / SpectraVideo plc G-720
Keyboard
cmd: udevadm monitor
1.Plugin keyboard
2.Check shortest path
my example: /devices/pci:00/:00:1a.0/usb1/1-1/1-1.2
cmd: udevadm -a -p /devices/pci:00/:00:1a.0/usb1/1-1/1-1.2 | egrep
"SUBSYSTEM|idProduct|idVendor"
output:
SUBSYSTEM=="usb"
ATTR{idProduct}=="0103"
ATTR{idVendor}=="1267"
Create rule:
nano /etc/udev/rules.d/99-numlocker.rules
content: ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="1267",
ATTRS{idProduct}=="0103" RUN+="/bin/sh -c '/usr/bin/touch
/home/kubuntu/plugged'", ENV{REMOVE_CMD}="/bin/sh -c '/bin/rm
/home/kubuntu/plugged'"}}}
Test rule:
cmd: udevadm test /devices/pci:00/:00:1a.0/usb1/1-1/1-1.2
shortened output:
...Reading rules file: /lib/udev/rules.d/99-systemd.rules
rules contain 393216 bytes tokens (32768 * 12 bytes), 37025 bytes strings
27127 strings (224162 bytes), 23453 de-duplicated (190812 bytes), 3675 trie
nodes used
value '[dmi/id]sys_vendor' is 'LENOVO'
value '[dmi/id]sys_vendor' is 'LENOVO'
IMPORT builtin 'usb_id' /lib/udev/rules.d/50-udev-default.rules:13
IMPORT builtin 'hwdb' /lib/udev/rules.d/50-udev-default.rules:13
MODE 0664 /lib/udev/rules.d/50-udev-default.rules:41
PROGRAM 'mtp-probe /sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.2 1 6'
/lib/udev/rules.d/69-libmtp.rules:2167
starting 'mtp-probe /sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.2 1 6'
'mtp-probe /sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.2 1 6'(out) '0'
Process 'mtp-probe /sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.2 1 6'
succeeded.
RUN '/lib/udev/tlp-usb-udev %p' /lib/udev/rules.d/85-tlp.rules:10
RUN '/bin/sh -c '/bin/rm /home/kubuntu/plugged''
/etc/udev/rules.d/99-numlocker.rules:6
handling device node '/dev/bus/usb/001/006', devnum=c189:5, mode=0664, uid=0,
gid=0
preserve permissions /dev/bus/usb/001/006, 020664, uid=0, gid=0
preserve already existing symlink '/dev/char/189:5' to '../bus/usb/001/006'
created db file '/run/udev/data/c189:5' for
'/devices/pci:00/:00:1a.0/usb1/1-1/1-1.2'
ACTION=add
BUSNUM=001
DEVNAME=/dev/bus/usb/001/006
DEVNUM=006
DEVPATH=/devices/pci:00/:00:1a.0/usb1/1-1/1-1.2
DEVTYPE=usb_device
DRIVER=usb
ID_BUS=usb
ID_MODEL=0103
ID_MODEL_ENC=0103
ID_MODEL_FROM_DATABASE=G-720 Keyboard
ID_MODEL_ID=0103
ID_REVISION=0101
ID_SERIAL=1267_0103
ID_USB_INTERFACES=:030101:03:
ID_VENDOR=1267
ID_VENDOR_ENC=1267
ID_VENDOR_FROM_DATABASE=Logic3 / SpectraVideo plc
ID_VENDOR_ID=1267
MAJOR=189
MINOR=5
PRODUCT=1267/103/101
REMOVE_CMD=/bin/sh -c '/bin/rm /home/kubuntu/plugged'
SUBSYSTEM=usb
TYPE=0/0/0
USEC_INITIALIZED=68681993
run: '/lib/udev/tlp-usb-udev /devices/pci:00/:00:1a.0/usb1/1-1/1-1.2'
run: '/bin/sh -c '/usr/bin/touch /home/kubuntu/plugged''
Unload module index
Unloaded link configuration context.
I've tried following to load rules:
> udevadm control -R
> systemctl restart systemd-udevd
> reboot
Nothing seems to work. Even after a few days and reboots it keeps the same,
BUT there's a "workaround":
After every reboot use:
systemctl stop systemd-udevd
systemctl start systemd-udevd
and the rule works.
Could anyone give me a hint why this does not work as expected in
Kubuntu 16.10 or can confirm this?
Thanks in advance!
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Tags: 16.10 bot-comment rules systemd-udevd udev
--
systemd-udevd does not work as expected using custom rules
https://bugs.launchpad.net/bugs/1641440
You received this bug notification because you are a member of Ubuntu Touch
seeded packages, which is subscribed to systemd in Ubuntu.
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641450] [NEW] libxml2 requires libiconv for static build
Public bug reported: Hi. I tried to build a software (Ryzomcore, an MMO framework), as a static build, but we are facing some unexpected issues : https://git.khaganat.net/khaganat/khanat-code/builds/504 Seems like the static library still search for libiconv, which seems to have been retired. Regards, Erwan "Dremor" Georget ** Affects: libxml2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1641450 Title: libxml2 requires libiconv for static build Status in libxml2 package in Ubuntu: New Bug description: Hi. I tried to build a software (Ryzomcore, an MMO framework), as a static build, but we are facing some unexpected issues : https://git.khaganat.net/khaganat/khanat-code/builds/504 Seems like the static library still search for libiconv, which seems to have been retired. Regards, Erwan "Dremor" Georget To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1641450/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618590] Re: scoperunner crashed with SIGSEGV in QObject::disconnect()
now i forgot how to submit bugs another thing is o found some new bugs in 17.04 Zesty Zapus 1.unable to use Unity 8 2. Software center is missing 3. technically everything is missing in unity 8 that was in unity 7 4. Every time i use software updater i get this error "Repository failed" i can't remember what the error was. 5. This does not seem the correct link for bug reporting but my memory sucks. 6.in details it says i'm running 16.10 but if i go into terminal and type "lsb_release -a" is says i'm using 17.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1618590 Title: scoperunner crashed with SIGSEGV in QObject::disconnect() Status in Canonical System Image: Fix Committed Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in unity-scope-click package in Ubuntu: Invalid Bug description: crash ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: unity-scope-click 0.1.1+16.10.20160808-0ubuntu1 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 Date: Tue Aug 30 17:54:20 2016 ExecutablePath: /usr/lib/x86_64-linux-gnu/unity-scopes/scoperunner InstallationDate: Installed on 2016-08-27 (3 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcCmdline: /usr/lib/x86_64-linux-gnu/unity-scopes/scoperunner /usr/lib/x86_64-linux-gnu/unity-scopes/clickapps/clickscope.ini Scope: Apps Signal: 11 SourcePackage: unity-scope-click StacktraceTop: QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 start_thread (arg=0x7fae9eade700) at pthread_create.c:333 Title: scoperunner crashed with SIGSEGV in QObject::disconnect() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1618590/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623666] Re: iOS10 will not connect to Ubuntu
J McDonald, I recommend you learning more about public key infrastructure. Essentially, encryption and security have different options available to it (called algorithms and parameters to said algorithms). libimobiledevice, using the GnuTLS library, specified incompatible options for it to work in iOS 10. When it was built with another library (OpenSSL instead of GnuTLS), it worked. TL;DR Ubuntu used GnuTLS version of libimobiledevice which had the bug and said bug has was fixed in libimobiledevice. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1623666 Title: iOS10 will not connect to Ubuntu Status in gnutls28 package in Ubuntu: Confirmed Status in libimobiledevice package in Ubuntu: Confirmed Bug description: Plug in iOS10 device, and it doesn't show the documents on it. Please package the recent fix in libimobiledevice: https://github.com/libimobiledevice/libimobiledevice/issues/327 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1623666/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1450009] Re: [HP, Dell notebooks] suspends on closed lid, does not recognized external monitors/dock
Found a workaround, edit /etc/systemd/logind.conf to set HandleLidSwitch=ignore. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1450009 Title: [HP, Dell notebooks] suspends on closed lid, does not recognized external monitors/dock Status in systemd package in Ubuntu: Fix Released Bug description: Using systemd as init system on a HP zbook15 notebook having 2 external monitors connected using a docking station and starting with lid closed the system goes to sleep after successfully booting and starting lightdm greeter. Sometimes there's enough time to enter username and password but system goes to sleep every time after a few seconds. The system can be woken up and used after this happens but it will not let me shutdown later. The problem is just present in docked situation starting with closed lid using systemd a init system. If notebook is used in non-docked situation with open lid and systemd the problem does not occur. Workaround: A switch back to upstart as init system resolves the issue. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd-sysv 219-7ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Wed Apr 29 14:46:09 2015 InstallationDate: Installed on 2015-04-27 (1 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450009/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641441] [NEW] suspends on closed lid, does not recognized external monitors/dock for dell E6420
Public bug reported: The defect 1450009 is closed. But it doesn't fix docked Dell E6420. You can see from comments that several people still suffer from it. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1641441 Title: suspends on closed lid, does not recognized external monitors/dock for dell E6420 Status in systemd package in Ubuntu: New Bug description: The defect 1450009 is closed. But it doesn't fix docked Dell E6420. You can see from comments that several people still suffer from it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1641441/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1450009] Re: [HP, Dell notebooks] suspends on closed lid, does not recognized external monitors/dock
It doesn't work for me on a docked E6420 as well -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1450009 Title: [HP, Dell notebooks] suspends on closed lid, does not recognized external monitors/dock Status in systemd package in Ubuntu: Fix Released Bug description: Using systemd as init system on a HP zbook15 notebook having 2 external monitors connected using a docking station and starting with lid closed the system goes to sleep after successfully booting and starting lightdm greeter. Sometimes there's enough time to enter username and password but system goes to sleep every time after a few seconds. The system can be woken up and used after this happens but it will not let me shutdown later. The problem is just present in docked situation starting with closed lid using systemd a init system. If notebook is used in non-docked situation with open lid and systemd the problem does not occur. Workaround: A switch back to upstart as init system resolves the issue. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd-sysv 219-7ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Wed Apr 29 14:46:09 2015 InstallationDate: Installed on 2015-04-27 (1 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450009/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641438] [NEW] package systemd-shim 9-1bzr4ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2
Public bug reported: while installing this was shown ProblemType: Package DistroRelease: Ubuntu 16.10 Package: systemd-shim 9-1bzr4ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 Date: Sun Nov 13 23:15:13 2016 ErrorMessage: subprocess installed post-removal script returned error exit status 2 InstallationDate: Installed on 2016-11-12 (1 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.2.12~ubuntu16.04.1 SourcePackage: systemd-shim Title: package systemd-shim 9-1bzr4ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 UpgradeStatus: Upgraded to yakkety on 2016-11-13 (0 days ago) mtime.conffile..etc.dbus-1.system.d.org.freedesktop.systemd1.conf: 2016-10-26T16:41:33 ** Affects: systemd-shim (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 need-duplicate-check yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1641438 Title: package systemd-shim 9-1bzr4ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 Status in systemd-shim package in Ubuntu: New Bug description: while installing this was shown ProblemType: Package DistroRelease: Ubuntu 16.10 Package: systemd-shim 9-1bzr4ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 Date: Sun Nov 13 23:15:13 2016 ErrorMessage: subprocess installed post-removal script returned error exit status 2 InstallationDate: Installed on 2016-11-12 (1 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.2.12~ubuntu16.04.1 SourcePackage: systemd-shim Title: package systemd-shim 9-1bzr4ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 UpgradeStatus: Upgraded to yakkety on 2016-11-13 (0 days ago) mtime.conffile..etc.dbus-1.system.d.org.freedesktop.systemd1.conf: 2016-10-26T16:41:33 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1641438/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623666] Re: iOS10 will not connect to Ubuntu
So if this is resolved, could someone provide an answer that doesn't require a PhD in computer science to figure out? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1623666 Title: iOS10 will not connect to Ubuntu Status in gnutls28 package in Ubuntu: Confirmed Status in libimobiledevice package in Ubuntu: Confirmed Bug description: Plug in iOS10 device, and it doesn't show the documents on it. Please package the recent fix in libimobiledevice: https://github.com/libimobiledevice/libimobiledevice/issues/327 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1623666/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1638177] Re: libimobiledevice: GnuTLS does not work with iOS10
*** This bug is a duplicate of bug 1623666 *** https://bugs.launchpad.net/bugs/1623666 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libimobiledevice (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1638177 Title: libimobiledevice: GnuTLS does not work with iOS10 Status in libimobiledevice package in Ubuntu: Confirmed Bug description: Problem: The libimobiledevice package for Ubuntu was built with --disable-openssl which forces GnuTLS. GnuTLS does not work with the recent iOS10 update. Solution: rebuild the package so that it links against OpenSSL again. This will resolve issues connecting to iOS 10 devices. I tested the latest development version of GnuTLS (@ commit 1e84b90feed97ee458b7113665300e6bc444798f of master HEAD) and it does not work with iOS 10 devices. Upstream issue reference: https://github.com/libimobiledevice/ifuse/issues/32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1638177/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641417] [NEW] Ubuntu 16.04 unable to detect/connect to and work properly with iPhone 4.
Public bug reported: Action 1: Plug an iPhone 4 to a just booted up Ubuntu 16.04 workstation. Result 1: 2 iPhone connections appear in Nautilus. 1st connect is mount via gphoto2, where access is limited to viewing and copying photos and videos. The 2nd connection that is mounted via afc fail to work, hence other folders in iPhone are not accessible. Action 2: Unplugged and re-plugged iPhone 4 to the workstation. Result 2: iPhone 4 does not reappear in Nautilus at all. No iPhone mount point appear. Checks and Remedy used: 1. "ideviceinfo" and lsusb command show iPhone 4 is connected. 2. "idevicepair validate" command shows "SUCCESS: Validated pairing with device [UDID]" 3. After running "ifuse /media/iPhone" command, iPhone 4 reappears in Nautilus as mounted in /media/iPhone. Furthermore, all folders of iPhone 4 appears and are accessible. I believe the 1st mounting of iPhone 4 on Nautilus is due to the "gvfs- backends" package. W/o it, auto detection/connection of iPhone 4 would not occur and appear in Nautilus. However, the afc mount failed to work The 2nd mounting is caused by ifuse. This works perfectly but requires manual mounting and unmounting. Questions: 1. How to overcome issues/failures mentioned in Result 1 & 2? 2. Ideally, i would like the automatic detection-connection between Ubuntu and iPhone to work. If not, is there a way to automate connection via ifuse? System and package info: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.1 LTS Release:16.04 Codename: xenial $ uname -or 4.4.0-47-generic GNU/Linux $ dpkg -l | grep iPhone ii ifuse1.1.2-0.1build3 amd64 FUSE module for iPhone and iPod Touch devices ii libimobiledevice-utils 1.2.0+dfsg-3~ubuntu0.2 amd64 Library for communicating with iPhone and iPod Touch devices ii libimobiledevice6:amd64 1.2.0+dfsg-3~ubuntu0.2 amd64 Library for communicating with the iPhone and iPod Touch ii libusbmuxd-tools 1.0.10-2ubuntu0.1 amd64 USB multiplexor daemon for iPhone and iPod Touch devices - tools ii libusbmuxd4:amd641.0.10-2ubuntu0.1 amd64 USB multiplexor daemon for iPhone and iPod Touch devices - library ii usbmuxd 1.1.0-2 amd64 USB multiplexor daemon for iPhone and iPod Touch devices $ dpkg -l | grep libusb ii libgusb2:amd64 0.2.9-0ubuntu1 amd64 GLib wrapper around libusb1 ii libusb-0.1-4:amd64 2:0.1.12-28 amd64 userspace USB programming library ii libusb-1.0-0:amd64 2:1.0.20-1 amd64 userspace USB programming library ii libusb-1.0-0:i3862:1.0.20-1 i386userspace USB programming library ii libusbmuxd-tools 1.0.10-2ubuntu0.1 amd64 USB multiplexor daemon for iPhone and iPod Touch devices - tools ii libusbmuxd4:amd641.0.10-2ubuntu0.1 amd64 USB multiplexor daemon for iPhone and iPod Touch devices - library ii libusbredirhost1:amd64 0.7.1-1 amd64 Implementing the usb-host (*) side of a usbredir connection (runtime) ii libusbredirparser1:amd64 0.7.1-1 amd64 Parser for the usbredir protocol (runtime) $ dpkg -l | grep gvfs ii gvfs:amd64 1.28.2-1ubuntu1~16.04.1amd64 userspace virtual filesystem - GIO module ii gvfs-backends 1.28.2-1ubuntu1~16.04.1amd64 userspace virtual filesystem - backends ii gvfs-bin1.28.2-1ubuntu1~16.04.1amd64 userspace virtual filesystem - binaries ii gvfs-common 1.28.2-1ubuntu1~16.04.1alluserspace virtual filesystem - common data files ii gvfs-daemons1.28.2-1ubuntu1~16.04.1amd64 userspace virtual filesystem - servers ii gvfs-fuse 1.28.2-1ubuntu1~16.04.1amd64 userspace virtual filesystem - fuse server ii gvfs-libs:amd64 1.28.2-1ubuntu1~16.04.1amd64 userspace virtual filesystem - private libraries ** Affects: libimobiledevice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1641417 Title: Ubuntu 16.04 unable to detect/connect to and work properly with iPhone 4. Status in libimobiledevice package in Ubuntu: New Bug description: Action 1: Plug an iPhone 4 to a just booted up Ubuntu 16.04 workstation. Result 1: 2 iPhone connections appear in Nautilus. 1st connect is mount via gphoto2, where access is limited to viewing and copying photos and videos. The 2nd connection that is mounted via afc fail to work, hence other folders in iPhone are not accessible. Action 2: Unplugged and re-plugged iPhone 4 to the workstation. Result 2: iPhone 4 does not reappear in Nautilus at all. No iPhone mount point appear. Checks and Remedy used: 1. "ideviceinfo" and lsusb command show iPhone 4 is connected. 2. "idevicepair
[Touch-packages] [Bug 1641416] [NEW] A core of the CPU always reloaded after restart
Public bug reported: When the computer is started or rebooted, a core of the CPU is always at least 90% loaded. When the Xorg process is terminated via the system monitor, everything is fine. A complete new installation did not fix the problem either. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Nov 13 15:33:11 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:14c7] InstallationDate: Installed on 2016-11-13 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: ASUSTeK COMPUTER INC. X75A1 ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=c1ff67b4-45e1-49de-ad32-9a1d8766b6b7 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X75A1.410 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X75A1 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.:bvrX75A1.410:bd12/26/2012:svnASUSTeKCOMPUTERINC.:pnX75A1:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX75A1:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X75A1 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Nov 13 15:31:47 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12623 vendor SEC xserver.version: 2:1.18.4-0ubuntu0.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1641416 Title: A core of the CPU always reloaded after restart Status in xorg package in Ubuntu: New Bug description: When the computer is started or rebooted, a core of the CPU is always at least 90% loaded. When the Xorg process is terminated via the system monitor, everything is fine. A complete new installation did not fix the problem either. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Nov 13 15:33:11 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:14c7] InstallationDate: Installed on 2016-11-13 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: ASUSTeK COMPUTER INC. X75A1 ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic
[Touch-packages] [Bug 1641415] [NEW] screen dimmed after suspend
Public bug reported: Often, waking the computer up from suspend will cause the screen brightness to be set right down (was 100% before suspend, becomes ~ 20% after waking). This happens during 40-70% of all suspends. I have not yet been able to figure out any correlations with previous activity, so the behaviour seems random. (I assume this is a LightDM problem, because it first manifests itself in the login screen, but I'm not sure.) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 13 15:39:26 2016 InstallationDate: Installed on 2016-07-15 (120 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1641415 Title: screen dimmed after suspend Status in lightdm package in Ubuntu: New Bug description: Often, waking the computer up from suspend will cause the screen brightness to be set right down (was 100% before suspend, becomes ~ 20% after waking). This happens during 40-70% of all suspends. I have not yet been able to figure out any correlations with previous activity, so the behaviour seems random. (I assume this is a LightDM problem, because it first manifests itself in the login screen, but I'm not sure.) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 13 15:39:26 2016 InstallationDate: Installed on 2016-07-15 (120 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1641415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1591411] Re: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay
Will fix, 1.10.10-1ubuntu2, enter 16.04 LTS? -- 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/1591411 Title: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay Status in D-Bus: Unknown Status in systemd: Unknown Status in dbus package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in dbus source package in Xenial: Confirmed Status in systemd source package in Xenial: Invalid Status in dbus source package in Yakkety: Confirmed Status in systemd source package in Yakkety: Invalid Bug description: I noticed on a system that accepts large numbers of SSH connections that after awhile, SSH sessions were taking ~25 seconds to complete. Looking in /var/log/auth.log, systemd-logind starts failing with the following: Jun 10 23:55:28 test sshd[3666]: pam_unix(sshd:session): session opened for user ubuntu by (uid=0) Jun 10 23:55:28 test systemd-logind[105]: New session c1052 of user ubuntu. Jun 10 23:55:28 test systemd-logind[105]: Failed to abandon session scope: Transport endpoint is not connected Jun 10 23:55:28 test sshd[3666]: pam_systemd(sshd:session): Failed to create session: Message recipient disconnected from message bus without replying I reproduced this in an LXD container by doing something like: lxc launch ubuntu:x test lxc exec test -- login -f ubuntu ssh-import-id Then ran a script as follows (passing in ubuntu@): while [ 1 ]; do (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log done In my case, after 1052 logins, the 1053rd and thereafter were taking 25+ seconds to complete. Here are some snippets from the log file: $ cat log | grep 0m0 | wc -l 1052 $ cat log | grep 0m25 | wc -l 4 $ tail -5 log real 0m0.222s real 0m25.232s real 0m25.235s real 0m25.236s real 0m25.239s ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sat Jun 11 00:09:34 2016 MachineType: Notebook W230SS ProcEnviron: TERM=xterm-256color PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W230SS dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: W230SS dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1591411/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1622730] Re: No sound on headphones after suspend
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/1622730 Title: No sound on headphones after suspend Status in alsa-driver package in Ubuntu: Confirmed Bug description: This seems to be a common problem on XMG Clevo W230SS there is no output on the headphone jack after suspend. The headphones are detected and the speakers are muted, but there is no output to the headphones. Init-headphones does not help: sudo init-headphone WARNING:root:Kernel parameter is missing: acpi_enforce_resources=lax WARNING:root:Module is not loaded: i2c_dev ERROR:root:Can't find i2c bus ERROR:root:Operation failed Any workaround beside reboot? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: pia 23276 F pulseaudio /dev/snd/controlC0: pia 23276 F pulseaudio CurrentDesktop: GNOME-Classic:GNOME Date: Mon Sep 12 21:56:08 2016 InstallationDate: Installed on 2015-11-05 (312 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W230SS dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: W230SS dmi.product.version: Not Applicable dmi.sys.vendor: Notebook modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-02-15T00:43:38.504815 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1622730/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641399] [NEW] package click 0.4.45.1+16.10.20160916-0ubuntu1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error
Public bug reported: When I turn on my laptop Dell inspiron 1545. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: click 0.4.45.1+16.10.20160916-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-26.28-lowlatency 4.8.0 Uname: Linux 4.8.0-26-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Fri Nov 11 22:31:10 2016 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2016-05-23 (173 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: click Title: package click 0.4.45.1+16.10.20160916-0ubuntu1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: click (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1641399 Title: package click 0.4.45.1+16.10.20160916-0ubuntu1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 Status in click package in Ubuntu: New Bug description: When I turn on my laptop Dell inspiron 1545. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: click 0.4.45.1+16.10.20160916-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-26.28-lowlatency 4.8.0 Uname: Linux 4.8.0-26-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Fri Nov 11 22:31:10 2016 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2016-05-23 (173 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: click Title: package click 0.4.45.1+16.10.20160916-0ubuntu1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1641399/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641400] [NEW] package click-apparmor 0.3.17 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1
Public bug reported: When I turn on my laptop Dell inspiron 1545. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: click-apparmor 0.3.17 ProcVersionSignature: Ubuntu 4.8.0-26.28-lowlatency 4.8.0 Uname: Linux 4.8.0-26-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Fri Nov 11 22:31:11 2016 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2016-05-23 (173 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: click-apparmor Title: package click-apparmor 0.3.17 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: click-apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click-apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1641400 Title: package click-apparmor 0.3.17 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 Status in click-apparmor package in Ubuntu: New Bug description: When I turn on my laptop Dell inspiron 1545. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: click-apparmor 0.3.17 ProcVersionSignature: Ubuntu 4.8.0-26.28-lowlatency 4.8.0 Uname: Linux 4.8.0-26-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Fri Nov 11 22:31:11 2016 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2016-05-23 (173 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: click-apparmor Title: package click-apparmor 0.3.17 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click-apparmor/+bug/1641400/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1160048] Re: add-apt-repository won't uncomment a commented-out source
Currently add-apt-repository also has --remove option which removes the .list file (or entry?), but does not remove/downgrade packages. ** Description changed: Assume you're frequently testing software, so you add, remove (purge) and re-add PPAs. - sudo add-apt-repository lp:someteam/ppa + sudo add-apt-repository ppa:someteam/ppa sudo apt-get uppdate sudo apt-get install someprogram ... time passes and you no longer need that program, or wish to test your system without it .. - sudo ppa-purge lp:someteam/ppa + sudo ppa-purge ppa:someteam/ppa This will remove the ppa by commenting out the "deb ..." line in the sources file in /etc/apt/sources.list.d Later, you need to do more testing of the app or some other app from the same ppa so you re-add it:- - sudo add-apt-repository lp:someteam/ppa + sudo add-apt-repository ppa:someteam/ppa However, this does _not_ add the PPA because the line/file already exists, albeit with a # in front of the "deb ...". Some might argue that it is the fault of ppa-purge for commenting the line out. I disagree. I believe ppa-purge _should_ comment out the "deb ..." line because sometimes you want to go back to the file to remind yourself what the ppa was that you got something from, or to just manually re-enable it. Given the single role of add-apt-repository is to add a ppa, I'd conclude it's add-apt-repository which is broken, given it doesn't add one in this common scenario. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: software-properties-common 0.92.17 ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4 Uname: Linux 3.8.0-14-generic x86_64 ApportVersion: 2.9.2-0ubuntu4 Architecture: amd64 Date: Mon Mar 25 21:39:42 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2012-06-29 (269 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to raring on 2013-01-18 (66 days ago) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1160048 Title: add-apt-repository won't uncomment a commented-out source Status in software-properties package in Ubuntu: Triaged Bug description: Assume you're frequently testing software, so you add, remove (purge) and re-add PPAs. sudo add-apt-repository ppa:someteam/ppa sudo apt-get uppdate sudo apt-get install someprogram ... time passes and you no longer need that program, or wish to test your system without it .. sudo ppa-purge ppa:someteam/ppa This will remove the ppa by commenting out the "deb ..." line in the sources file in /etc/apt/sources.list.d Later, you need to do more testing of the app or some other app from the same ppa so you re-add it:- sudo add-apt-repository ppa:someteam/ppa However, this does _not_ add the PPA because the line/file already exists, albeit with a # in front of the "deb ...". Some might argue that it is the fault of ppa-purge for commenting the line out. I disagree. I believe ppa-purge _should_ comment out the "deb ..." line because sometimes you want to go back to the file to remind yourself what the ppa was that you got something from, or to just manually re-enable it. Given the single role of add-apt-repository is to add a ppa, I'd conclude it's add-apt-repository which is broken, given it doesn't add one in this common scenario. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: software-properties-common 0.92.17 ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4 Uname: Linux 3.8.0-14-generic x86_64 ApportVersion: 2.9.2-0ubuntu4 Architecture: amd64 Date: Mon Mar 25 21:39:42 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2012-06-29 (269 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: Upgraded to raring on 2013-01-18 (66 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1160048/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574278] Re: AbiWord text cursor starts to flicker after adding some text
add to grub, radeon.dpm=1, according to this link https://help.ubuntu.com/community/RadeonDriver#Testing_the_driver makes flickering slower but it does not stop. GLX version 1.4 and AMD RV710 I changed grub as xorg used high cpu, when opening abi documents. -- 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/1574278 Title: AbiWord text cursor starts to flicker after adding some text Status in AbiWord: In Progress Status in abiword package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: Fix Released Status in lubuntu-artwork package in Ubuntu: Invalid Status in abiword source package in Xenial: Invalid Status in gtk+3.0 source package in Xenial: Confirmed Status in lubuntu-artwork source package in Xenial: Invalid Bug description: After adding some text in a new document, the entire document (including gray page background, text, text cursor) starts to flicker very fast. The UI above does not flicker. This happens too on a different system in VirtualBox. (Lubuntu 16.04 i386) Workaround == 1. Open the Lubuntu menu. 2. Open Preferences>Customize Look and Feel 3. Change the theme to something other than Lubuntu-default or Lubuntu-dark-panel ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: abiword 3.0.1-6 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 CurrentDesktop: LXDE Date: Sun Apr 24 16:12:14 2016 ExecutablePath: /usr/bin/abiword InstallationDate: Installed on 2016-04-22 (2 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release i386 (20151021) ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: abiword UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/abiword/+bug/1574278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641389] [NEW] Bay Trail - PC just hangs user cannot do anything
Public bug reported: My laptop host a bay trail Intel CPU after upgrading to 16.04 through clean install the laptop started going into hung state very often. Touch pad would not work even after recovering from hung state by logging out and then again logging in. tried to add max.idle_cstate or similar command as suggested by on of the forum but that would also not work sometime. Please provide correct patch for the same. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-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: Sun Nov 13 16:00:23 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1025:0845] InstallationDate: Installed on 2016-07-19 (116 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b3f6 Chicony Electronics Co., Ltd HD WebCam (Acer) Bus 001 Device 005: ID 04ca:300b Lite-On Technology Corp. Atheros AR3012 Bluetooth Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer E1-510 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=57c0d8ae-90f3-4404-8880-a0da976ed6b3 ro quiet splash intel_idle.max_cstate=1 vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2015 dmi.bios.vendor: Acer dmi.bios.version: V2.14 dmi.board.name: E1-510 dmi.board.vendor: Acer dmi.board.version: V2.14 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAcer:bvrV2.14:bd11/13/2015:svnAcer:pnE1-510:pvrV2.14:rvnAcer:rnE1-510:rvrV2.14:cvnAcer:ct10:cvrChassisVersion: dmi.product.name: E1-510 dmi.product.version: V2.14 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Nov 13 15:56:38 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1072 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1641389 Title: Bay Trail - PC just hangs user cannot do anything Status in xorg package in Ubuntu: New Bug description: My laptop host a bay trail Intel CPU after upgrading to 16.04 through clean install the laptop started going into hung state very often. Touch pad would not work even after recovering from hung state by logging out and then again logging in. tried to add max.idle_cstate or similar command as suggested by on of the forum but that would also not work sometime. Please provide correct patch for the same. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-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: Sun Nov 13 16:00:23 2016 DistUpgraded: Fresh install DistroCodename:
[Touch-packages] [Bug 1637758] Re: lightdm greeter session not properly shut down at login
Confirmed. With 232-3 I also get the duplicate nm-applet, one is from the lightdm session. ** Changed in: lightdm (Ubuntu) Status: Triaged => In Progress ** Changed in: lightdm (Ubuntu) Milestone: None => ubuntu-16.11 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1637758 Title: lightdm greeter session not properly shut down at login Status in lightdm package in Ubuntu: In Progress Status in systemd package in Ubuntu: New Bug description: I am using lightdm with 2 seats. After 2409 revision randomly one of two seats does not work correctly. xsettings plugin from unity-settings-daemon or gnome-settings-deamon fails to start because there is already _XSESSION_S* manager running. After revision 2409 in system monitor I see that there is still running unity-settings-daemon started by lightdm. Reverting this revision fixes my problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1637758/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1576424] Re: Gimp crashes with text tool & caps lock
** Changed in: gtk+2.0 (Ubuntu Xenial) Importance: Undecided => High ** Changed in: gtk+2.0 (Ubuntu Yakkety) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1576424 Title: Gimp crashes with text tool & caps lock Status in GTK+: Fix Released Status in gtk+2.0 package in Ubuntu: Fix Committed Status in gtk+2.0 source package in Xenial: In Progress Status in gtk+2.0 source package in Yakkety: In Progress Bug description: [Impact] Gimp crashes with a segfault when I use caps lock while renaming a layer. It is possible Caps lock causes crashes in other events also. [Test Case] Steps to reproduce: 1. Open a new blank gimp document 2. select the text tool 3. type a couple of words of text (gimp will create a text layer above the background layer) 4. with the text tool still selected, click on the background layer (just to move away from the text layer) 5. now double click on the text layer to rename the layer (layer name gets highlighted) 6. press the caps lock key 7. click on the background layer again (without renaming or doing anything to the text layer) Now repeat steps 5 and 6. Gimp crashes. [Regression Potential] None expected. The patch used has been taken from upstream development. https://git.gnome.org/browse/gtk%2B/commit/?id=2811221d7039bd82265ce36a1b0dd9a0eeb431ad Packages for Xenial and Yakkety have been built in a PPA and regression tested. [ Other Info ] I can force this to happen every time I launch Gimp. Rebooting makes no difference. It seems to be the second time I press caps lock that forces the crash. I tried launching Gimp with caps lock on vs caps lock off, but I don't believe it made any difference. I can force a crash every time following the above sequence. I deleted my gimp preferences folder then rebooted for good measure. Gimp created a fresh preferences folder, but it hasn't solved the problem. I was originally in single window mode, but the new preferences folder put me back to multi window, but it crashes either way. I ran dmesg | tail after the crash and got the following line: gimp-2.8[2976]: segfault at 14 ip 7ff5100e0cd9 sp 7ffef11bfcb0 error 4 in libgtk-x11-2.0.so.0.2400.30[7ff51001b000+43e000] I'm using a fresh install of Xubuntu 16.04 with nvidia 361.42 driver (available from the Additional Drivers tab). In that same tab, I also have enabled Processor microcode firmware for Intel CPUs. Terminal tells me Gimp version is 2.8.16-1ubuntu1 I'm not very experienced with bug reporting and not sure what other information I need to supply. Gimp was absolutely rock solid on this machine with 15.10, so it may be a Xubuntu issue. Hope someone can take a look at this. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1576424/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1640456] Re: Switching to USB sound device stops USB mouse clicks from registering #2
Hi 1. I tested now with an 12.04 live DVD and that worked without any problem. I just got the hardware so I have not tested with other installed versions except for 16.04 and 16.10. 2. It is resolved with the daily live Zesty Ubuntu and Kubuntu image. Meanwhile I will continue to use /usr/share/X11/xorg.conf.d/50-jabra.conf workaround from #1581626 -- Johan Thelmén -- 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/1640456 Title: Switching to USB sound device stops USB mouse clicks from registering #2 Status in xorg package in Ubuntu: Incomplete Bug description: Switching to USB sound device stops USB mouse clicks from registering #2. -- Johan ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Wed Nov 9 12:38:58 2016 DistUpgraded: 2016-10-15 18:27:45,511 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: yakkety DistroVariant: kubuntu DkmsStatus: virtualbox, 5.1.6, 4.8.0-22-generic, x86_64: installed virtualbox, 5.1.6, 4.8.0-26-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad T61p [17aa:20d9] InstallationDate: Installed on 2013-08-08 (1188 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) LightdmGreeterLogOld: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Filen eller katalogen finns inte QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: Unable to assign [undefined] to QString usersession MachineType: LENOVO 6458VJJ PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-26-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to yakkety on 2016-10-15 (24 days ago) dmi.bios.date: 07/01/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETC1WW (2.21 ) dmi.board.name: 6458VJJ 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:bvr7LETC1WW(2.21):bd07/01/2008:svnLENOVO:pn6458VJJ:pvrThinkPadT61p:rvnLENOVO:rn6458VJJ:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 6458VJJ dmi.product.version: ThinkPad T61p dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Wed Nov 9 08:12:53 2016 xserver.configfile: default xserver.errors: /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1640456/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
