[Touch-packages] [Bug 1637601] Re: UbuntuKVM: migration using NFS mount fails #190
Hi Mauricio, this being in zesty due to the merge of latest Debian as planned by Debian picking up your changes as discussed. That said, it would be very kind if you did a check if it works for you as intended. It does for me, but an ack would be nice $ id libvirt-qemu uid=64055(libvirt-qemu) gid=116(kvm) groups=116(kvm),64055(libvirt-qemu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-passwd in Ubuntu. https://bugs.launchpad.net/bugs/1637601 Title: UbuntuKVM: migration using NFS mount fails #190 Status in libvirt: Fix Released Status in base-passwd package in Ubuntu: Fix Released Status in libvirt package in Ubuntu: Fix Released Bug description: <...> Please see comments for the problem description, and summary of originally bridged comments in the description. Sorry about the inconvenience. <...> To manage notifications about this bug go to: https://bugs.launchpad.net/libvirt/+bug/1637601/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1497105] Re: Clients can't get high resolution input in Unity8
** Also affects: mir Importance: Undecided Status: New ** Changed in: mir Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mir Status: New => In Progress ** Changed in: mir Milestone: None => 0.26.0 ** Changed in: mir Importance: Undecided => Medium ** Tags added: visual-quality -- 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/1497105 Title: Clients can't get high resolution input in Unity8 Status in Canonical System Image: New Status in Mir: In Progress Status in QtMir: Invalid Status in qtmir package in Ubuntu: Invalid Status in unity8 package in Ubuntu: New Bug description: Clients can't get high resolution input in Unity8. Using native (non-nested) Mir servers, clients can get the full speed input stream if they so choose (MIR_CLIENT_INPUT_RATE=0). And it's planned that this will become a formal API feature: bug 1439590 However in Unity8, because it is a nested server, the client no longer has the option of getting this high resolution input. Examples of clients that utilize high resolution input for improved visual quality: mir_demo_client_fingerpaint -w--desktop_file_hint=unity8 mir_demo_client_target -n--desktop_file_hint=unity8 You may also want to experiment with those using ultra-high resolution input by adding a kernel parameter: usbhid.mousepoll=1 This is a tricky problem because for touch at least we do want the input stream to be throttled to the display rate from the top level down. Perhaps the answer is to enhance Unity8 to be a full-speed (non- resampled) client and then the clients of Unity8 can then still have a choice of whether they get resampling or not. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1497105/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
Hello We are running Gitlab on 16.04 LTS and had this issue which was really causing a lot of frustrations. I was waiting for the update to go through for about a month now and decided to apply this updated version. After applying it via proposed repository it has solved the issue for us as well. This must be affecting many others out there as well. Anyway, thank you so much for making this available and hopefully they will release it soon. Cheers Keith -- 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: Fix Committed Status in systemd source package in Xenial: Invalid Status in dbus source package in Yakkety: Fix Committed Status in systemd source package in Yakkety: Invalid Bug description: [Impact] The bug affects multiple users and introduces an user visible delay (~25 seconds) on SSH connections after a large number of sessions have been processed. This has a serious impact on big systems and servers running our software. The currently proposed fix is actually a safe workaround for the bug as proposed by the dbus upstream. The workaround makes uid 0 immune to the pending_fd_timeout limit that kicks in and causes the original issue. [Test Case] 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 Then checking the log file if there are any ssh sessions that are taking 25+ seconds to complete. Multiple instances of the same script can be used at the same time. [Regression Potential] The fix has a rather low regression potential as the workaround is a very small change only affecting one particular case - handling of uid 0. The fix has been tested by multiple users and has been around in zesty for a while, with multiple people involved in reviewing the change. It's also a change that has been proposed by upstream. [Original 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:
[Touch-packages] [Bug 1606418] Re: PointerConfinement.test_we_update_our_confined_region_on_a_resize
Fix committed into lp:mir at revision None, scheduled for release in mir, milestone 0.26.0 ** Changed in: mir Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1606418 Title: PointerConfinement.test_we_update_our_confined_region_on_a_resize Status in Mir: Fix Committed Status in mir package in Ubuntu: In Progress Bug description: Randomly fails 1/100 times. https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=i386,compiler=gcc,platform=mesa,release=xenial+overlay/1612/console Looking into it, most likely a race with surface resize... To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1606418/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1654023] Re: [regression] Development headers reference unknown header "mir_toolkit/mir_input_device_types.h" so some clients can't build at all any more
I take it back. Not being able to build clients would have been a critical problem. Fortunately the fix has now landed. ** Changed in: mir Importance: High => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1654023 Title: [regression] Development headers reference unknown header "mir_toolkit/mir_input_device_types.h" so some clients can't build at all any more Status in Mir: Fix Committed Status in Mir 0.25 series: Invalid Status in mir package in Ubuntu: Invalid Bug description: Trying to build GTK+ which uses mircommon and mirclient, I'm getting: In file included from /home/william/.cache/install/mir/include/mirclient/mir_toolkit/events/event.h:74:0, from /home/william/.cache/install/mir/include/mirclient/mir_toolkit/client_types.h:24, from /home/william/.cache/install/mir/include/mirclient/mir_toolkit/mir_connection.h:21, from /home/william/.cache/install/mir/include/mirclient/mir_toolkit/mir_client_library.h:21, from /home/william/Code/jhbuild/checkout/gtk+/gdk/mir/gdkmir.h:22, from /home/william/Code/jhbuild/checkout/gtk+/gdk/mir/gdkmircursor.c:22: /home/william/.cache/install/mir/include/mirclient/mir_toolkit/events/input/input_event.h:23:48: fatal error: mir_toolkit/mir_input_device_types.h: No such file or directory #include "mir_toolkit/mir_input_device_types.h" ^ compilation terminated. Makefile:652: recipe for target 'gdkmircursor.lo' failed make[4]: *** [gdkmircursor.lo] Error 1 make[4]: *** Waiting for unfinished jobs In file included from /home/william/.cache/install/mir/include/mirclient/mir_toolkit/events/event.h:74:0, from /home/william/.cache/install/mir/include/mirclient/mir_toolkit/client_types.h:24, from /home/william/.cache/install/mir/include/mirclient/mir_toolkit/mir_connection.h:21, from /home/william/.cache/install/mir/include/mirclient/mir_toolkit/mir_client_library.h:21, from /home/william/Code/jhbuild/checkout/gtk+/gdk/mir/gdkmir.h:22, from /home/william/Code/jhbuild/checkout/gtk+/gdk/mir/gdkmirdevicemanager.c:25: /home/william/.cache/install/mir/include/mirclient/mir_toolkit/events/input/input_event.h:23:48: fatal error: mir_toolkit/mir_input_device_types.h: No such file or directory #include "mir_toolkit/mir_input_device_types.h" ^ compilation terminated. Makefile:652: recipe for target 'gdkmirdevicemanager.lo' failed make[4]: *** [gdkmirdevicemanager.lo] Error 1 In file included from /home/william/.cache/install/mir/include/mirclient/mir_toolkit/events/event.h:74:0, from /home/william/.cache/install/mir/include/mirclient/mir_toolkit/client_types.h:24, from /home/william/.cache/install/mir/include/mirclient/mir_toolkit/mir_connection.h:21, from /home/william/.cache/install/mir/include/mirclient/mir_toolkit/mir_client_library.h:21, from /home/william/Code/jhbuild/checkout/gtk+/gdk/mir/gdkmir.h:22, from /home/william/Code/jhbuild/checkout/gtk+/gdk/mir/gdkmirdisplay.c:24: /home/william/.cache/install/mir/include/mirclient/mir_toolkit/events/input/input_event.h:23:48: fatal error: mir_toolkit/mir_input_device_types.h: No such file or directory #include "mir_toolkit/mir_input_device_types.h" It seems like this header was moved, or possibly it wasn't installed. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1654023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1654023] Re: [regression] Development headers reference unknown header "mir_toolkit/mir_input_device_types.h" so some clients can't build at all any more
Fix committed into lp:mir at revision None, scheduled for release in mir, milestone 0.26.0 ** Changed in: mir Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1654023 Title: [regression] Development headers reference unknown header "mir_toolkit/mir_input_device_types.h" so some clients can't build at all any more Status in Mir: Fix Committed Status in Mir 0.25 series: Invalid Status in mir package in Ubuntu: Invalid Bug description: Trying to build GTK+ which uses mircommon and mirclient, I'm getting: In file included from /home/william/.cache/install/mir/include/mirclient/mir_toolkit/events/event.h:74:0, from /home/william/.cache/install/mir/include/mirclient/mir_toolkit/client_types.h:24, from /home/william/.cache/install/mir/include/mirclient/mir_toolkit/mir_connection.h:21, from /home/william/.cache/install/mir/include/mirclient/mir_toolkit/mir_client_library.h:21, from /home/william/Code/jhbuild/checkout/gtk+/gdk/mir/gdkmir.h:22, from /home/william/Code/jhbuild/checkout/gtk+/gdk/mir/gdkmircursor.c:22: /home/william/.cache/install/mir/include/mirclient/mir_toolkit/events/input/input_event.h:23:48: fatal error: mir_toolkit/mir_input_device_types.h: No such file or directory #include "mir_toolkit/mir_input_device_types.h" ^ compilation terminated. Makefile:652: recipe for target 'gdkmircursor.lo' failed make[4]: *** [gdkmircursor.lo] Error 1 make[4]: *** Waiting for unfinished jobs In file included from /home/william/.cache/install/mir/include/mirclient/mir_toolkit/events/event.h:74:0, from /home/william/.cache/install/mir/include/mirclient/mir_toolkit/client_types.h:24, from /home/william/.cache/install/mir/include/mirclient/mir_toolkit/mir_connection.h:21, from /home/william/.cache/install/mir/include/mirclient/mir_toolkit/mir_client_library.h:21, from /home/william/Code/jhbuild/checkout/gtk+/gdk/mir/gdkmir.h:22, from /home/william/Code/jhbuild/checkout/gtk+/gdk/mir/gdkmirdevicemanager.c:25: /home/william/.cache/install/mir/include/mirclient/mir_toolkit/events/input/input_event.h:23:48: fatal error: mir_toolkit/mir_input_device_types.h: No such file or directory #include "mir_toolkit/mir_input_device_types.h" ^ compilation terminated. Makefile:652: recipe for target 'gdkmirdevicemanager.lo' failed make[4]: *** [gdkmirdevicemanager.lo] Error 1 In file included from /home/william/.cache/install/mir/include/mirclient/mir_toolkit/events/event.h:74:0, from /home/william/.cache/install/mir/include/mirclient/mir_toolkit/client_types.h:24, from /home/william/.cache/install/mir/include/mirclient/mir_toolkit/mir_connection.h:21, from /home/william/.cache/install/mir/include/mirclient/mir_toolkit/mir_client_library.h:21, from /home/william/Code/jhbuild/checkout/gtk+/gdk/mir/gdkmir.h:22, from /home/william/Code/jhbuild/checkout/gtk+/gdk/mir/gdkmirdisplay.c:24: /home/william/.cache/install/mir/include/mirclient/mir_toolkit/events/input/input_event.h:23:48: fatal error: mir_toolkit/mir_input_device_types.h: No such file or directory #include "mir_toolkit/mir_input_device_types.h" It seems like this header was moved, or possibly it wasn't installed. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1654023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1100546] Re: Power indicator favours 'not present' mouse over laptop battery level
** Branch linked: lp:~fourdollars/indicator-power/xenial -- 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/1100546 Title: Power indicator favours 'not present' mouse over laptop battery level Status in indicator-power: Triaged Status in indicator-power package in Ubuntu: Triaged Bug description: The power indicator shows the battery level for cordless mice and keyboards, even when it cannot identify the battery level. This is a problem as it seems to favour showing a "not present" mouse status over the laptop battery level in the top bar. I haven't done a good job of explaining it, so check out the screenshot - it will explain all :) Basically, the laptop battery should be shown in the top bar if the mouse/keyboard is "not present". Also hiding the mouse and keyboard when the battery level is unknown would also be useful too :) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: indicator-power 12.10.6daily12.11.21.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-0.3-generic 3.8.0-rc3 Uname: Linux 3.8.0-0-generic x86_64 ApportVersion: 2.8-0ubuntu1 Architecture: amd64 Date: Thu Jan 17 10:11:16 2013 InstallationDate: Installed on 2012-12-14 (33 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121214) MarkForUpload: True SourcePackage: indicator-power UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-power/+bug/1100546/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1100546] Re: Power indicator favours 'not present' mouse over laptop battery level
** Branch linked: lp:~fourdollars/indicator-power/zesty -- 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/1100546 Title: Power indicator favours 'not present' mouse over laptop battery level Status in indicator-power: Triaged Status in indicator-power package in Ubuntu: Triaged Bug description: The power indicator shows the battery level for cordless mice and keyboards, even when it cannot identify the battery level. This is a problem as it seems to favour showing a "not present" mouse status over the laptop battery level in the top bar. I haven't done a good job of explaining it, so check out the screenshot - it will explain all :) Basically, the laptop battery should be shown in the top bar if the mouse/keyboard is "not present". Also hiding the mouse and keyboard when the battery level is unknown would also be useful too :) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: indicator-power 12.10.6daily12.11.21.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-0.3-generic 3.8.0-rc3 Uname: Linux 3.8.0-0-generic x86_64 ApportVersion: 2.8-0ubuntu1 Architecture: amd64 Date: Thu Jan 17 10:11:16 2013 InstallationDate: Installed on 2012-12-14 (33 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121214) MarkForUpload: True SourcePackage: indicator-power UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-power/+bug/1100546/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1100546] Re: Power indicator favours 'not present' mouse over laptop battery level
This patch is for zesty. ** Patch added: "indicator-power_12.10.6+17.04.20161201-0ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1100546/+attachment/4800193/+files/indicator-power_12.10.6+17.04.20161201-0ubuntu1.debdiff -- 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/1100546 Title: Power indicator favours 'not present' mouse over laptop battery level Status in indicator-power: Triaged Status in indicator-power package in Ubuntu: Triaged Bug description: The power indicator shows the battery level for cordless mice and keyboards, even when it cannot identify the battery level. This is a problem as it seems to favour showing a "not present" mouse status over the laptop battery level in the top bar. I haven't done a good job of explaining it, so check out the screenshot - it will explain all :) Basically, the laptop battery should be shown in the top bar if the mouse/keyboard is "not present". Also hiding the mouse and keyboard when the battery level is unknown would also be useful too :) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: indicator-power 12.10.6daily12.11.21.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-0.3-generic 3.8.0-rc3 Uname: Linux 3.8.0-0-generic x86_64 ApportVersion: 2.8-0ubuntu1 Architecture: amd64 Date: Thu Jan 17 10:11:16 2013 InstallationDate: Installed on 2012-12-14 (33 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121214) MarkForUpload: True SourcePackage: indicator-power UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-power/+bug/1100546/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1291373] Re: wget. memory leaks
The attachment "wget.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wget in Ubuntu. https://bugs.launchpad.net/bugs/1291373 Title: wget. memory leaks Status in wget package in Ubuntu: New Bug description: Wget eats RAM when downloading big website. To reproduce run these on slow internet connection: bash$ wget -r -k -p -l inf -U 'Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)' 'http://bigwebsite.com/' 2> stderr.txt After one ~6 hours wget eats 1.5 GiB of RAM. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: wget 1.13.4-2ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-36.52~precise1-generic 3.8.13.14 Uname: Linux 3.8.0-36-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Wed Mar 12 15:29:05 2014 InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MarkForUpload: True SourcePackage: wget UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1291373/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1636827] Re: wireless network list disappears
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1636827 Title: wireless network list disappears Status in network-manager package in Ubuntu: Expired Bug description: On Thinkpad W520, wireless network list disappears occasionally. Restarting the network manager service fixes the issue. Please see the following bug for more information: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590985 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 26 13:57:59 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-07-12 (105 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s25 ethernet connected /org/freedesktop/NetworkManager/Devices/1 LARICS 3ad4f968-8fd1-4759-a3bc-746cb364628e /org/freedesktop/NetworkManager/ActiveConnection/2 wlp3s0 wifi connected /org/freedesktop/NetworkManager/Devices/0 FERwlan 3f100dda-2c1b-46d6-83af-064c33b51c5a /org/freedesktop/NetworkManager/ActiveConnection/3 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1636827/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1653324] Re: No wireless networks visible on resume from suspend. Erroneous Wired connection icon in nm-applet
Is NM asleep in all those failed cases? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1653324 Title: No wireless networks visible on resume from suspend. Erroneous Wired connection icon in nm-applet Status in network-manager package in Ubuntu: Confirmed Bug description: As others have reported this I just woke my Thinkpad 450 to find no network. I resolved this by manually reconnecting with "nmcli c up id " where was taken from the output of "nmcli c" on the same machine. Steps to reproduce:- This is an intermittent issue which for me happens once in a while, but not super often to be annoying. For others it appears to happen often. I suspend my laptop multiple times daily and don't see this more than once per couple of weeks, or sometimes once a month. * Use laptop in one location on wifi * Suspend (shut lid) laptop * Resume (open lid) in same location (so same wifi networks nearby) Expected behaviour:- * Network come back up Actual behaviour:- * No network connectivity * nm-applet icon shows the two arrows as if a wired connection is made * No or few wireless erroneous wireless networks shown nearby * Workaround 1 (reconnect from command line) nmcli c (lists wireless networks, look for yours in the "NAME" column, use it in command below) nmcli c up id NAME * Workaround 2 (restart entire network stack) This AskUbuntu question has one solution http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend- after-16-04-upgrade#761220 Further information:- Output of nmcli m while suspending and resuming:- alan@gort:~$ nmcli m Connectivity is now 'none' Networkmanager is now in the 'asleep' state enp0s25: unmanaged wlp3s0: unmanaged Connectivity is now 'full' Networkmanager is now in the 'connected (local only)' state enp0s25: unavailable wlp3s0: unavailable wlp3s0: disconnected Output of nmcli after using workaround 1 above:- popey_2.4g_bed: connection profile changed Connectivity is now 'none' Networkmanager is now in the 'connecting' state wlp3s0: connecting (configuring) wlp3s0: using connection 'popey_2.4g_bed' wlp3s0: connecting (getting IP configuration) Connectivity is now 'full' 'popey_2.4g_bed' is now the primary connection Networkmanager is now in the 'connected' state wlp3s0: connected popey_2.4g_bed: connection profile changed Hardware info:- Thinkpad T450 alan@gort:~$ lspci | grep -i net 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (3) I218-LM (rev 03) 03:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59) alan@gort:~$ uptime 05:31:54 up 2 days, 18:03, 7 users, load average: 0.34, 0.94, 1.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CurrentDesktop: Unity Date: Sat Dec 31 05:38:47 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-27 (247 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev wlp3s0 proto static metric 600 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 10.235.160.0/24 dev lxdbr0 proto kernel scope link src 10.235.160.1 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.95 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1653324/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1606418] Re: PointerConfinement.test_we_update_our_confined_region_on_a_resize
Again: https://mir-jenkins.ubuntu.com/job/build-2-binpkg- mir/arch=i386,compiler=gcc,platform=mesa,release=xenial+overlay/3306/consoleFull -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1606418 Title: PointerConfinement.test_we_update_our_confined_region_on_a_resize Status in Mir: In Progress Status in mir package in Ubuntu: In Progress Bug description: Randomly fails 1/100 times. https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=i386,compiler=gcc,platform=mesa,release=xenial+overlay/1612/console Looking into it, most likely a race with surface resize... To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1606418/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1654023] Re: [regression] Development headers reference unknown header "mir_toolkit/mir_input_device_types.h" so some clients can't build at all any more
Invalid for 0.25 since the bug only appeared in series 0.26. And since the bug has never been released it's not a critical problem. ** Changed in: mir/0.25 Importance: Critical => High ** Changed in: mir/0.25 Status: New => Invalid ** Changed in: mir/0.25 Milestone: 0.25.1 => None ** Changed in: mir Importance: Critical => High ** Also affects: mir (Ubuntu) Importance: Undecided Status: New ** Changed in: mir (Ubuntu) Status: New => Invalid ** Changed in: mir/0.25 Importance: High => Undecided -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1654023 Title: [regression] Development headers reference unknown header "mir_toolkit/mir_input_device_types.h" so some clients can't build at all any more Status in Mir: In Progress Status in Mir 0.25 series: Invalid Status in mir package in Ubuntu: Invalid Bug description: Trying to build GTK+ which uses mircommon and mirclient, I'm getting: In file included from /home/william/.cache/install/mir/include/mirclient/mir_toolkit/events/event.h:74:0, from /home/william/.cache/install/mir/include/mirclient/mir_toolkit/client_types.h:24, from /home/william/.cache/install/mir/include/mirclient/mir_toolkit/mir_connection.h:21, from /home/william/.cache/install/mir/include/mirclient/mir_toolkit/mir_client_library.h:21, from /home/william/Code/jhbuild/checkout/gtk+/gdk/mir/gdkmir.h:22, from /home/william/Code/jhbuild/checkout/gtk+/gdk/mir/gdkmircursor.c:22: /home/william/.cache/install/mir/include/mirclient/mir_toolkit/events/input/input_event.h:23:48: fatal error: mir_toolkit/mir_input_device_types.h: No such file or directory #include "mir_toolkit/mir_input_device_types.h" ^ compilation terminated. Makefile:652: recipe for target 'gdkmircursor.lo' failed make[4]: *** [gdkmircursor.lo] Error 1 make[4]: *** Waiting for unfinished jobs In file included from /home/william/.cache/install/mir/include/mirclient/mir_toolkit/events/event.h:74:0, from /home/william/.cache/install/mir/include/mirclient/mir_toolkit/client_types.h:24, from /home/william/.cache/install/mir/include/mirclient/mir_toolkit/mir_connection.h:21, from /home/william/.cache/install/mir/include/mirclient/mir_toolkit/mir_client_library.h:21, from /home/william/Code/jhbuild/checkout/gtk+/gdk/mir/gdkmir.h:22, from /home/william/Code/jhbuild/checkout/gtk+/gdk/mir/gdkmirdevicemanager.c:25: /home/william/.cache/install/mir/include/mirclient/mir_toolkit/events/input/input_event.h:23:48: fatal error: mir_toolkit/mir_input_device_types.h: No such file or directory #include "mir_toolkit/mir_input_device_types.h" ^ compilation terminated. Makefile:652: recipe for target 'gdkmirdevicemanager.lo' failed make[4]: *** [gdkmirdevicemanager.lo] Error 1 In file included from /home/william/.cache/install/mir/include/mirclient/mir_toolkit/events/event.h:74:0, from /home/william/.cache/install/mir/include/mirclient/mir_toolkit/client_types.h:24, from /home/william/.cache/install/mir/include/mirclient/mir_toolkit/mir_connection.h:21, from /home/william/.cache/install/mir/include/mirclient/mir_toolkit/mir_client_library.h:21, from /home/william/Code/jhbuild/checkout/gtk+/gdk/mir/gdkmir.h:22, from /home/william/Code/jhbuild/checkout/gtk+/gdk/mir/gdkmirdisplay.c:24: /home/william/.cache/install/mir/include/mirclient/mir_toolkit/events/input/input_event.h:23:48: fatal error: mir_toolkit/mir_input_device_types.h: No such file or directory #include "mir_toolkit/mir_input_device_types.h" It seems like this header was moved, or possibly it wasn't installed. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1654023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1653295] Re: Chromium and Chrome flickering
Hi Christopher, Thanks for taking a look into this issue - I've completed some troubleshooting based on your suggestions and have some more information that I hope is useful. I'm running a Chromebook using crouton to run Ubuntu in a chroot. 1. Unfortunately I'm not able to install anything other than a stable LTS on the hardware that exhibits the issue. 2. Removing the xserver-xorg-video-intel package and the conf file appears to have either resolved the issue or decreased it to the point where it is not currently noticeable. I've been running it for a day or so - will update if the issue occurs again. 3. Using UXA appeared to decrease the frequency of the issue similar to the above - however overall performance did suffer with rendering of pages slower, and I believe worse performance in Unity. 4. The issue has occurred across all the Chrome releases I've installed on this hardware (around the last two months) and occurs with the latest stable Chrome release as well. It was present with both xenial 16.04 and 16.04.1 releases. 5. It's an Acer Chromebook 11 - C730 6. Due to running on a Chromebook I'm not able to recompile the kernel - however the issue has occurred across multiple stable ChromeOS releases (from the last two months since this hardware has been running). -- 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/1653295 Title: Chromium and Chrome flickering Status in xorg package in Ubuntu: Incomplete Bug description: Chromium and Chrome 55.0.2883.87 flickering. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 3.10.18 x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Dec 31 11:19:59 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 007: ID 04f2:b490 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Gnawty ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: cros_secure console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 vroot none ro 1,0 2539520 verity payload=PARTUUID=f32d8bfa-395b-d240-bbf7-eb409533babd/PARTNROFF=1 hashtree=PARTUUID=f32d8bfa-395b-d240-bbf7-eb409533babd/PARTNROFF=1 hashstart=2539520 alg=sha1 root_hexdigest=5fb151de5f21d1172e6c0f68e3f1f582c083a5cd salt=4ce7adaeb24ff98d94fb9bff36a65ac39b743a9ecca5390ad010972810c5697a" noinitrd vt.global_cursor_default=0 kern_guid=f32d8bfa-395b-d240-bbf7-eb409533babd add_efi_memmap boot=local noresume noswap i915.modeset=1 tpm_tis.force=1 tpm_tis.interrupts=0 nmi_watchdog=panic,lapic SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2015 dmi.bios.vendor: coreboot dmi.bios.version: Google_Gnawty.5216.239.34 dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvrGoogle_Gnawty.5216.239.34:bd08/16/2015:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Gnawty dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1653295/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1590844] Re: Call with Bluetooth headset not working [Meizu Pro 5 Ubuntu Edition]
Attaching the results of the MX4 for comparison with the PRO 5. Everything worked for the MX4 ** Attachment added: "MX4_Bluetooth.txt" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590844/+attachment/4800171/+files/MX4_Bluetooth.txt -- 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/1590844 Title: Call with Bluetooth headset not working [Meizu Pro 5 Ubuntu Edition] Status in Canonical System Image: Confirmed Status in turbo: Confirmed Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in telephony-service package in Ubuntu: Confirmed Bug description: My bluetooth headset perfectly connects to my Meizu Pro 5. However, the sound quality is so poor (a lot of noise) such that you don't understand your communication partner. Note that the headset works perfectly together with Ubuntu on my Nexus 4. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590844/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590844] Re: Call with Bluetooth headset not working [Meizu Pro 5 Ubuntu Edition]
I wiped my Pro 5 so that I could roll back all of the testing configuration changes that I made and am now able to provide two more updated logs from fresh installs. I have both an MX4 and a Pro 5. The MX4 successfully handles phonecalls. The Pro 5 doesn't. Immediately after making test phonecalls on both devices, I ran the following commands on each devices: grep -i blue /var/log/syslog grep -i pulse /var/log/syslog I've attached the results for the Pro 5. ** Attachment added: "Pro5_Bluetooth.txt" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590844/+attachment/4800170/+files/Pro5_Bluetooth.txt -- 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/1590844 Title: Call with Bluetooth headset not working [Meizu Pro 5 Ubuntu Edition] Status in Canonical System Image: Confirmed Status in turbo: Confirmed Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in telephony-service package in Ubuntu: Confirmed Bug description: My bluetooth headset perfectly connects to my Meizu Pro 5. However, the sound quality is so poor (a lot of noise) such that you don't understand your communication partner. Note that the headset works perfectly together with Ubuntu on my Nexus 4. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590844/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1653402] Re: Mouse pointer leaves trail using intel 400 hd broadwell
** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1653402 Title: Mouse pointer leaves trail using intel 400 hd broadwell Status in xorg package in Ubuntu: Confirmed Bug description: I have an Intel HD 400 Broadwell Video Card and this problem is present on Ubuntu Gnome but in Ubuntu, Xubuntu, Lubuntu I don´t have it only a little glitch on the cursor certain times. Gnome on Wayland session work perfect without this problem. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sun Jan 1 01:23:01 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:1000] InstallationDate: Installed on 2016-12-24 (7 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:07dc Intel Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GIGABYTE GB-BACE-3150 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic.efi.signed root=UUID=93c44558-73ff-4f12-a85d-9c1cf7456547 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/29/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MZBSWBP-00 dmi.board.vendor: GIGABYTE dmi.board.version: 1.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd06/29/2015:svnGIGABYTE:pnGB-BACE-3150:pvr1.x:rvnGIGABYTE:rnMZBSWBP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GB-BACE-3150 dmi.product.version: 1.x dmi.sys.vendor: GIGABYTE version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1653402/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1654113] [NEW] USB drive with lvm on an encrypted partition does not unmount cleanly when removed, making it impossible to use again without a reboot or use of command line tools
Public bug reported: I have a USB drive with two partitions, one unencrypted and one encrypted. The encrypted partition serves as the physical volume for a LVM volume group. cfdisk shows me: Disk: /dev/sdb Size: 74.5 GiB, 80026361856 bytes, 156301488 sectors Label: dos, identifier: 0x0006866a DeviceBoot Start End Sectors Size Id Type >> /dev/sdb1 * 2048 500094 498047 243.2M 83 Linux /dev/sdb2 501758 156301311 15579955474.3G 5 Extended └─/dev/sdb5501760 156301311 15579955274.3G 83 Linux When I plug in the drive, one partition is mounted automatically. A popup window also appears, prompting for a password to unlock the volume. After I enter the password, four more volumes appear on my Desktop, and in /media/username: $ ls -l /media/username total 25 drwxr-xr-x 22 root root 4096 Jan 6 2014 0c321a15-e3b4-47b5-a173-05adfb5ea40c drwxrwxrwt 9 root root 12288 Dec 21 00:26 14ea30b5-5ace-4bc7-a483-7d800ee77579 drwxr-xr-x 15 root root 4096 Dec 21 00:27 41f9c7bb-62e5-4afd-b4c1-efdecfd70083 drwxr-xr-x 7 root root 4096 Nov 12 2013 42d838d8-b797-4782-8473-5d42a29667c1 drwxr-xr-x 4 root root 1024 Mar 18 2014 ba0575b2-f570-4e40-b374-f1d3dc0ca48b The output of findmnt is as follows, with my username again replaced with 'username': TARGETSOURCE FSTYPE OPTIONS / /dev/mapper/burrow-root │ext4rw,relatime,errors=remo ├─/syssysfs sysfs rw,nosuid,nodev,noexec, [snip] ├─/boot /dev/sda1 ext2rw,relatime,block_valid ├─/home /dev/mapper/burrow-home │ext4rw,relatime,data=ordere ├─/media/username/ba0575b2-f570-4e40-b374-f1d3dc0ca48b │ /dev/sdc1 ext2rw,nosuid,nodev,relatim ├─/media/username/14ea30b5-5ace-4bc7-a483-7d800ee77579 │ /dev/mapper/antler-temp │ext4rw,nosuid,nodev,relatim ├─/media/username/42d838d8-b797-4782-8473-5d42a29667c1 │ /dev/mapper/antler-home │ext4rw,nosuid,nodev,relatim ├─/media/username/41f9c7bb-62e5-4afd-b4c1-efdecfd70083 │ /dev/mapper/antler-var │ext4rw,nosuid,nodev,relatim └─/media/username/0c321a15-e3b4-47b5-a173-05adfb5ea40c /dev/mapper/antler-root ext4rw,nosuid,nodev,relatim To unmount the drive, I can right click on each volume on the desktop, choose unmount, and I receive a pop up notification that the drive has been safely removed. After unplugging the USB drive, the icon for the unencrypted volume disappears from the desktop, but the icons for the lvm volumes remain. I have attached the long errors that appear in the syslog. When plugging the drive back in, the unencrypted partition is again mounted, and I am prompted for a password. Nothing further happens. If I double click on the encryted drive icon on the desktop, I am again prompted for a password, and then receive this error: Failed to mount "80 GB Encrypted" Error unclocking /dev/sdb5: Command-line `cryptsetup luksOpen "/dev/sdb5" "luks-1d2a9dd8-91a4-4e34-9531-b0cde53579c0" ' exited with non-zero exit status 5: Device luks-1d2a9dd8-91a4-4e34-9531-b0cde53579c0 already exists. The usb drive is unusable without a reboot, or issuing this command, antler is the volume group name: $ sudo vgchange -a n antler 0 logical volume(s) in volume group "antler" now active Upon issuing this command, the icons for the four lvm volumes disappears from my desktop. If I now plug in the drive, it acts normally. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lvm2 2.02.133-1ubuntu10 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jan 4 19:40:18 2017 InstallationDate: Installed on 2016-11-28 (37 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "syslog when unplugging the USB drive" https://bugs.launchpad.net/bugs/1654113/+attachment/4800158/+files/attach.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
[Touch-packages] [Bug 1653725] Re: lxc-android-config not starting on ubuntu-touch/staging/* xenial-based images after lxc upgrade
This was fixed upstream and included in our stable branch. A cherry-pick was uploaded to Zesty and all tests were run successfully against it. I have now uploaded the same thing for xenial and yakkety, they are in the queue waiting for a SRU team member to approve them. Once the Xenial SRU is through, I'll update the trusty-backports pocket with it. ** Changed in: lxc (Ubuntu Yakkety) Status: Triaged => In Progress ** Changed in: lxc (Ubuntu Xenial) Status: Triaged => In Progress ** Description changed: - As in topic. Since the 20161217 rootfs, after upgrade of lxc from - 2.0.5-0ubuntu1~ubuntu16.04.3 to 2.0.6-0ubuntu1~ubuntu16.04.1 the lxc- - android-config service does not start - making the devices unbootable. + # SRU + ## Rationale + LXC 2.0.6 introduced a writability test for /var/lib/lxc which breaks the corner case of partly-writable systems like the Ubuntu phone. + This upload fixes this by changing the test to a simple readability one. + + ## Test case + 1) Attempt to run lxc-start with /var/lib/lxc on a read-only filesystem but /var/lib/lxc/ on a writable one. + 2) Confirm that the container now starts. + + ## Regression potential + This upload only changes the check from read/write to read so the only consequence of this should be more cases now being allowed. In the case where a writable /var/lib/lxc is in fact absolutely required for the requested operation, the operation will still fail, just a bit later and with a slightly less clear error message (as was the case pre-2.0.6). + + + # Original report + As in topic. Since the 20161217 rootfs, after upgrade of lxc from 2.0.5-0ubuntu1~ubuntu16.04.3 to 2.0.6-0ubuntu1~ubuntu16.04.1 the lxc-android-config service does not start - making the devices unbootable. The syslog only states this: Jan 3 10:50:30 ubuntu-phablet systemd[1]: Starting LXC Android Config and Container Initialization... Jan 3 10:50:30 ubuntu-phablet kernel: [5.790810] (3)[1:systemd]SLEEP_EN = 0x1 Jan 3 10:50:30 ubuntu-phablet systemd[1]: Starting Light Display Manager... Jan 3 10:50:30 ubuntu-phablet systemd-udevd[672]: Could not generate persistent MAC address for ifb0: No such file or directory Jan 3 10:50:30 ubuntu-phablet systemd-udevd[684]: Could not generate persistent MAC address for ifb1: No such file or directory Jan 3 10:50:30 ubuntu-phablet lxc-start[1220]: You lack access to /var/lib/lxc Jan 3 10:50:30 ubuntu-phablet systemd[1]: lxc-android-config.service: Control process exited, code=exited status=1 Jan 3 10:50:30 ubuntu-phablet systemd[1]: Failed to start LXC Android Config and Container Initialization. Jan 3 10:50:30 ubuntu-phablet systemd[1]: Dependency failed for force-mtp.service. Jan 3 10:50:30 ubuntu-phablet systemd[1]: force-mtp.service: Job force-mtp.service/start failed with result 'dependency'. Jan 3 10:50:30 ubuntu-phablet systemd[1]: lxc-android-config.service: Unit entered failed state. Jan 3 10:50:30 ubuntu-phablet systemd[1]: lxc-android-config.service: Failed with result 'exit-code'. This makes all of our frieza and cooler devices useless for testing purposes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1653725 Title: lxc-android-config not starting on ubuntu-touch/staging/* xenial-based images after lxc upgrade Status in Canonical System Image: Confirmed Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Trusty: Triaged Status in lxc source package in Xenial: In Progress Status in lxc source package in Yakkety: In Progress Status in lxc source package in Zesty: Fix Released Bug description: # SRU ## Rationale LXC 2.0.6 introduced a writability test for /var/lib/lxc which breaks the corner case of partly-writable systems like the Ubuntu phone. This upload fixes this by changing the test to a simple readability one. ## Test case 1) Attempt to run lxc-start with /var/lib/lxc on a read-only filesystem but /var/lib/lxc/ on a writable one. 2) Confirm that the container now starts. ## Regression potential This upload only changes the check from read/write to read so the only consequence of this should be more cases now being allowed. In the case where a writable /var/lib/lxc is in fact absolutely required for the requested operation, the operation will still fail, just a bit later and with a slightly less clear error message (as was the case pre-2.0.6). # Original report As in topic. Since the 20161217 rootfs, after upgrade of lxc from 2.0.5-0ubuntu1~ubuntu16.04.3 to 2.0.6-0ubuntu1~ubuntu16.04.1 the lxc-android-config service does not start - making the devices unbootable. The syslog only states this: Jan 3 10:50:30 ubuntu-phablet systemd[1]: Starting LXC Android Config and Container Initialization... Jan 3 10:50:30 ubuntu-phablet kernel: [
[Touch-packages] [Bug 1291373] Re: wget. memory leaks
Sorry, the indentation in my inline patch seems to have been lost. Here is the same thing as attachment. ** Patch added: "wget.patch" https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1291373/+attachment/4800156/+files/wget.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wget in Ubuntu. https://bugs.launchpad.net/bugs/1291373 Title: wget. memory leaks Status in wget package in Ubuntu: New Bug description: Wget eats RAM when downloading big website. To reproduce run these on slow internet connection: bash$ wget -r -k -p -l inf -U 'Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)' 'http://bigwebsite.com/' 2> stderr.txt After one ~6 hours wget eats 1.5 GiB of RAM. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: wget 1.13.4-2ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-36.52~precise1-generic 3.8.13.14 Uname: Linux 3.8.0-36-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Wed Mar 12 15:29:05 2014 InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MarkForUpload: True SourcePackage: wget UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1291373/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1291373] Re: wget. memory leaks
The following patch to wget 1.13.4-2ubuntu1.4 eliminates most of the leaks, except the one in CRYPTO_malloc which may be due to a memory leak in the opensll library. diff -r wget-1.13.4/src/http.c wget-1.13.4-jbk/src/http.c 2288c2288 < if (tmp) --- > if (tmp) { 2289a2290,2291 > free(tmp); > } diff -r wget-1.13.4/src/retr.c wget-1.13.4-jbk/src/retr.c 291a292 > free(line); 293a295 > char *line = fd_read_line(fd); 295c297 < if (fd_read_line (fd) == NULL) --- > if (line == NULL) 296a299,300 > else > free(line); 355,359c359,368 < if (fd_read_line (fd) == NULL) < { < ret = -1; < break; < } --- > { > char *line = fd_read_line(fd); > if (line == NULL) > { > ret = -1; > break; > } > else > xfree(line); > } -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wget in Ubuntu. https://bugs.launchpad.net/bugs/1291373 Title: wget. memory leaks Status in wget package in Ubuntu: New Bug description: Wget eats RAM when downloading big website. To reproduce run these on slow internet connection: bash$ wget -r -k -p -l inf -U 'Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)' 'http://bigwebsite.com/' 2> stderr.txt After one ~6 hours wget eats 1.5 GiB of RAM. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: wget 1.13.4-2ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-36.52~precise1-generic 3.8.13.14 Uname: Linux 3.8.0-36-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Wed Mar 12 15:29:05 2014 InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MarkForUpload: True SourcePackage: wget UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1291373/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1637601] Re: UbuntuKVM: migration using NFS mount fails #190
This bug was fixed in the package libvirt - 2.5.0-3ubuntu1 --- libvirt (2.5.0-3ubuntu1) zesty; urgency=medium * Merged with Debian unstable - this picks up a fix for migrations using NFS mounts (LP: #1637601). * Remaining changes: - Disable sheepdog (universe dependency) - Disable libssh2 support (universe dependency) - Disable firewalld support (universe dependency) - Disable selinux - Enable esx support - Add build-dep to libcurl4-gnutls-dev (required for esx) - Set qemu-group to kvm (for compat with older ubuntu) - Added changes to use the upstream apparmor profiles with added delta (configurable via apparmor profiles version). * d/p/u/000[1-6]-apparmor-* - Regularly clear AppArmor profiles for vms that no longer exist - Fix name resolution calls from virt-aa-helper profile (LP 1546674). - Add missing apparmor rule for debug-threads feature (LP 1615550). - Add new block device types to virt-aa-helpers profile (LP 1641618) - Additional apport package-hook - d/rules: debhelper start virtlogd.socket - Add sysvinit script for virtlockd - Additional debian/bug-presubj - Modifications to adapt for our delayed switch away from libvirt-bin (can be dropped after 18.04). - d/p/ubuntu/libvirtd-service-add-bin-alias.patch: alias to old libvirt-bin name. - d/p/ubuntu/libvirtd-init-add-bin-alias.patch: provides for the old libvirt-bin name. - Wait on socket in sysvinit script - Backwards compatible handling of groups (can be dropped after 18.04). - config details and autostart of default bridged network. Creating that is now the default in general, yet our solution provides the following on top as of today: - nat only on some ports - autostart the default network by default - do not autostart if 192.168.122.0 is already taken (e.g. in containers) - d/p/ubuntu/Allow-libvirt-group-to-access-the-socket.patch: This is the group based access to libvirt functions as it was used in Ubuntu for quite long. - d/p/ubuntu/daemon-augeas-fix-expected.patch fix some related tests due to the group access change. - d/p/ubuntu/dnsmasq-as-priv-user: configuration to run as extra user - d/p/ubuntu/disable-network-test.patch: disable test failing due to dnsmasq changes. - ubuntu/parallel-shutdown.patch: set parallel shutdown by default. - d/p/ubuntu/enable-kvm-spice.patch: compat with older Ubuntu qemu/kvm which provided a separate kvm-spice. - d/p/ubuntu/storage-default-permission-mode-to-0711: safer default perms for storage dirs like /var/lib/libvirt/images. - d/p/ubuntu/storage-disable-gluster-test: gluster not enabled, skip test - d/p/ubuntu/9031-enable-lxc-apparmor: enable apparmor confinement of containers by default. - d/p/ubuntu/9032-lxc-allow-no-security-driver: allow empty sec driver for libvirt-lxc. - d/p/ubuntu/ubuntu_machine_type.patch: accept ubuntu types as pci440fx - d/p/ubuntu/ubuntu-libxl-qemu-path.patch: Set common qemu path to match Debian/Ubuntu Xen packaging. - d/p/ubuntu/ubuntu-libxl-hvmloader-path.patch: Fallback for libxl xen paths (LP 1459603) - d/p/ubuntu/ubuntu-libxl-Fix-up-VRAM-to-minimum-requirements.patch: auto set VRAM to minimum requirements - d/p/ubuntu/libxl-no-dm-check.patch: Stop calling emulator to identify device-model - d/p/ubuntu/xen-default-uri.patch: set default URI on xen hosts - fixup tests to match packaging of Xen (mostly different paths) - d/p/ubuntu/libxl-fix-test-data.patch - d/p/ubuntu/fix-xen-xml-in-tests.patch - d/p/ubuntu/Debianize-virtlogd-service.patch: Adapt config file location for Debian based systems. - d/p/ubuntu/Debianize-virtlockd-init.patch: Fix default config path in virtlockd.init for Debian based systems. - d/p/ubuntu/9034-complete-9p-support: virt-aa-helper: add l to 9p file options. - d/p/ubuntu/parallel-shutdown.patch: shut guests down in parallel - d/p/ubuntu/virt-aa-helper-no-explicity-deny-for-basefiles.patch: ask for no deny rule for readonly disk elements. - d/p/ubuntu/virt-aa-helper-add-guest-agent-rule.patch: add virt-aa-helper rule allowing all private channel access - d/p/ubuntu/libvirtd-service-nolimit.patch: remove proc/file/task limits to support huge systems. - d/p/ubuntu/virt-aa-helper-apparmor-allow-usr-share-AAVMF-too.patch: virt-aa-helper to allow access to aarch64 UEFI images. - d/p/ubuntu/libvirtd-service-set-notifyaccess.patch: set NotifyAccess=all in libvirtd.service (LP 1574566). - d/p/ubuntu/apibuild-skip-libvirt-common.h: drop libvirt-common.h from included_files to avoid build failures due to duplicate definitions. - Update README.Debian with Ubuntu changes - Convert libvirt0, libnss_libvirt and libvirt-dev
[Touch-packages] [Bug 1653487] Re: seccomp argument filtering not working on trusty(?)
I've identified the additional patches to make the testsuite happy and will be testing the cherrypicked patches approach and upload to trusty- proposed once testing is completed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1653487 Title: seccomp argument filtering not working on trusty(?) Status in libseccomp package in Ubuntu: In Progress Bug description: The snapd build on trusty for amd64 fails with the following error: """ make[2]: Entering directory `/tmp/snapd-2.20.1~14.04/cmd/snap-confine/tests' ... PASS: test_restrictions_working FAIL: test_restrictions_working_args """ (see https://launchpad.net/ubuntu/+source/snapd/2.20.1~14.04/+build/11759913) The same build works for i386 and armhf. I can reproduce this in a trusty chroot, upon further investigation it looks like the version of libseccomp (2.1.1) in trusty-proposed is the culprit. When I upgrade: """ Upgrade: libseccomp2:amd64 (2.1.1-1ubuntu1~trusty1, 2.2.3-2ubuntu1~ubuntu14.04.1), libseccomp-dev:amd64 (2.1.1-1ubuntu1~trusty1, 2.2.3-2ubuntu1~ubuntu14.04.1) all tests run fine. It looks like an issue with seccomp argument filtering (bpf) on 64 bit systems. This https://github.com/seccomp/libseccomp/releases/tag/v2.2.1 might include the missing fix, however I have not looked in detail what patch exactly we may need. Fwiw, we don't see this in spread because we build the package in the spread tests with `DEB_BUILD_OPTIONS='nocheck testkeys' dpkg- buildpackage` and we do not run the integration tests of snap-confine in anything else beside the package build (until https://github.com/snapcore/snapd/pull/2433/files is merged). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1653487/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1653725] Re: lxc-android-config not starting on ubuntu-touch/staging/* xenial-based images after lxc upgrade
This bug was fixed in the package lxc - 2.0.6-0ubuntu5 --- lxc (2.0.6-0ubuntu5) zesty; urgency=medium * Cherry-pick upstream bugfix: - 0003-tools-only-check-for-O_RDONLY.patch (LP: #1653725) -- Stéphane GraberWed, 04 Jan 2017 14:11:45 -0500 ** Changed in: lxc (Ubuntu Zesty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1653725 Title: lxc-android-config not starting on ubuntu-touch/staging/* xenial-based images after lxc upgrade Status in Canonical System Image: Confirmed Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Trusty: Triaged Status in lxc source package in Xenial: Triaged Status in lxc source package in Yakkety: Triaged Status in lxc source package in Zesty: Fix Released Bug description: As in topic. Since the 20161217 rootfs, after upgrade of lxc from 2.0.5-0ubuntu1~ubuntu16.04.3 to 2.0.6-0ubuntu1~ubuntu16.04.1 the lxc- android-config service does not start - making the devices unbootable. The syslog only states this: Jan 3 10:50:30 ubuntu-phablet systemd[1]: Starting LXC Android Config and Container Initialization... Jan 3 10:50:30 ubuntu-phablet kernel: [5.790810] (3)[1:systemd]SLEEP_EN = 0x1 Jan 3 10:50:30 ubuntu-phablet systemd[1]: Starting Light Display Manager... Jan 3 10:50:30 ubuntu-phablet systemd-udevd[672]: Could not generate persistent MAC address for ifb0: No such file or directory Jan 3 10:50:30 ubuntu-phablet systemd-udevd[684]: Could not generate persistent MAC address for ifb1: No such file or directory Jan 3 10:50:30 ubuntu-phablet lxc-start[1220]: You lack access to /var/lib/lxc Jan 3 10:50:30 ubuntu-phablet systemd[1]: lxc-android-config.service: Control process exited, code=exited status=1 Jan 3 10:50:30 ubuntu-phablet systemd[1]: Failed to start LXC Android Config and Container Initialization. Jan 3 10:50:30 ubuntu-phablet systemd[1]: Dependency failed for force-mtp.service. Jan 3 10:50:30 ubuntu-phablet systemd[1]: force-mtp.service: Job force-mtp.service/start failed with result 'dependency'. Jan 3 10:50:30 ubuntu-phablet systemd[1]: lxc-android-config.service: Unit entered failed state. Jan 3 10:50:30 ubuntu-phablet systemd[1]: lxc-android-config.service: Failed with result 'exit-code'. This makes all of our frieza and cooler devices useless for testing purposes. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1653725/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1654094] Re: package linux-firmware 1.157.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- 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/1654094 Title: package linux-firmware 1.157.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: I get this error while updating linux generic kernel ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.6 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.4 Architecture: amd64 Date: Wed Jan 4 17:36:04 2017 Dependencies: DpkgHistoryLog: Start-Date: 2017-01-04 17:35:22 Commandline: aptdaemon role='role-commit-packages' sender=':1.693' Upgrade: libnss3-nssdb:amd64 (2:3.23-0ubuntu0.16.04.1, 2:3.26.2-0ubuntu0.16.04.2), unattended-upgrades:amd64 (0.90ubuntu0.2, 0.90ubuntu0.3), libnss3:amd64 (2:3.23-0ubuntu0.16.04.1, 2:3.26.2-0ubuntu0.16.04.2) ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-10-14 (448 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: initramfs-tools Title: package linux-firmware 1.157.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-08-09 (148 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1654094/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1654094] [NEW] package linux-firmware 1.157.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: I get this error while updating linux generic kernel ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.6 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.4 Architecture: amd64 Date: Wed Jan 4 17:36:04 2017 Dependencies: DpkgHistoryLog: Start-Date: 2017-01-04 17:35:22 Commandline: aptdaemon role='role-commit-packages' sender=':1.693' Upgrade: libnss3-nssdb:amd64 (2:3.23-0ubuntu0.16.04.1, 2:3.26.2-0ubuntu0.16.04.2), unattended-upgrades:amd64 (0.90ubuntu0.2, 0.90ubuntu0.3), libnss3:amd64 (2:3.23-0ubuntu0.16.04.1, 2:3.26.2-0ubuntu0.16.04.2) ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-10-14 (448 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: initramfs-tools Title: package linux-firmware 1.157.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-08-09 (148 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1654094 Title: package linux-firmware 1.157.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: I get this error while updating linux generic kernel ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.6 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.4 Architecture: amd64 Date: Wed Jan 4 17:36:04 2017 Dependencies: DpkgHistoryLog: Start-Date: 2017-01-04 17:35:22 Commandline: aptdaemon role='role-commit-packages' sender=':1.693' Upgrade: libnss3-nssdb:amd64 (2:3.23-0ubuntu0.16.04.1, 2:3.26.2-0ubuntu0.16.04.2), unattended-upgrades:amd64 (0.90ubuntu0.2, 0.90ubuntu0.3), libnss3:amd64 (2:3.23-0ubuntu0.16.04.1, 2:3.26.2-0ubuntu0.16.04.2) ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-10-14 (448 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: initramfs-tools Title: package linux-firmware 1.157.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-08-09 (148 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1654094/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1654093] [NEW] boot loop
Public bug reported: I have a dual boot system running with Windows7 and Ubuntu LTS 16.04. The first attempt to boot into ubuntu every time ends up with a boot loop with a colored magenta blank screen. After rebooting and then entering ubuntu as OS choice, an error about an "Intel pch overrun error" (error not mentioned exactly as displayed because I dont understand the error category or content) is shown but eventually after sometime ubuntu boots up normally. The next time when the system boots up, the above process have to be repeated. I am not very educated in Linux operations or grub operations but can understand and implement changes if guided. Also, Ubuntu taking unusually long time to boot up. Is it bcoz I have quite a few applications installed? But I don't have much startup applications set up? Please advice. This is the first time I am reporting a bug and pardon me for using xdiagnose for this (if I should not have used it). I don't know what bug or bugs is/are shown by xdiagnose either. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.4 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: Thu Jan 5 03:41:24 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [1043:844d] InstallationDate: Installed on 2016-12-17 (18 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 003: ID 0ac8:3450 Z-Star Microelectronics Corp. Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic root=UUID=dc488953-1b39-46a7-b2b1-c8b099adee06 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1107 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX3 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1107:bd02/25/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX3R2.0:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Jan 5 03:26:27 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id2790 vendor SAM xserver.version: 2:1.18.4-0ubuntu0.2 ** 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/1654093 Title: boot loop Status in xorg package in Ubuntu: New Bug description: I have a dual boot system running with Windows7 and Ubuntu LTS 16.04. The first attempt to boot into ubuntu every time ends up with a boot loop with a colored magenta blank screen. After rebooting and
[Touch-packages] [Bug 1653487] Re: seccomp argument filtering not working on trusty(?)
I'm not done looking at this, but I have confirmed this is a bug in libseccomp so retargeting there. What is happening is that snap-confine is getting a denial on geteuid (syscall 107) even though this syscall is included in the filter. This indicates a problem in the filter setup in libseccomp and not snap-confine itself and this patch appears to fix the issue: eece06525d58d08fe6bb20e5f635eb02fd8d6eee However, that patch needs the following to be applied: 9ca83f455562fe8a972823d0e101cc71a8063547 206da04b8b2366d9efb963569bb89fe82ed2d1ba 61fee77783fd458739eb6104f13d53bddfa389ac While with the above 4 patches applied the snap-confine testsuite passes, the libseccomp internal testsuite has many failures. I'm now investigating if it is better to continue cherrypicking patches or to pull back 2.2.3 from xenial. ** Package changed: snap-confine (Ubuntu) => libseccomp (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1653487 Title: seccomp argument filtering not working on trusty(?) Status in libseccomp package in Ubuntu: In Progress Bug description: The snapd build on trusty for amd64 fails with the following error: """ make[2]: Entering directory `/tmp/snapd-2.20.1~14.04/cmd/snap-confine/tests' ... PASS: test_restrictions_working FAIL: test_restrictions_working_args """ (see https://launchpad.net/ubuntu/+source/snapd/2.20.1~14.04/+build/11759913) The same build works for i386 and armhf. I can reproduce this in a trusty chroot, upon further investigation it looks like the version of libseccomp (2.1.1) in trusty-proposed is the culprit. When I upgrade: """ Upgrade: libseccomp2:amd64 (2.1.1-1ubuntu1~trusty1, 2.2.3-2ubuntu1~ubuntu14.04.1), libseccomp-dev:amd64 (2.1.1-1ubuntu1~trusty1, 2.2.3-2ubuntu1~ubuntu14.04.1) all tests run fine. It looks like an issue with seccomp argument filtering (bpf) on 64 bit systems. This https://github.com/seccomp/libseccomp/releases/tag/v2.2.1 might include the missing fix, however I have not looked in detail what patch exactly we may need. Fwiw, we don't see this in spread because we build the package in the spread tests with `DEB_BUILD_OPTIONS='nocheck testkeys' dpkg- buildpackage` and we do not run the integration tests of snap-confine in anything else beside the package build (until https://github.com/snapcore/snapd/pull/2433/files is merged). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1653487/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1646080] Re: Mir-backed InputDeviceModel’s count property is not updated timely
This bug was fixed in the package qtsystems-opensource-src - 5.0~git20141206~44f70d99-0ubuntu12~1 --- qtsystems-opensource-src (5.0~git20141206~44f70d99-0ubuntu12~1) zesty; urgency=medium * debian/patches/Fix-InputDeviceModel-on-Mir-count-property.patch: - Fix InputDeviceModel on Mir (LP: #1646080) -- Timo JyrinkiFri, 18 Nov 2016 09:45:02 + ** Changed in: qtsystems-opensource-src (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtsystems-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1646080 Title: Mir-backed InputDeviceModel’s count property is not updated timely Status in qtsystems-opensource-src package in Ubuntu: Fix Released Bug description: I’m trying to use InputDeviceModel from QML with the following example: import QtQuick 2.4 import QtSystemInfo 5.5 Item { InputDeviceModel { id: idm filter: InputInfo.Mouse onCountChanged: console.log("mice model count:", devices, count) onAdded: console.log("added mouse:", inputDevice, count) onRemoved: console.log("removed mouse:", deviceId, count) } readonly property bool hasMouse: idm.count > 0 onHasMouseChanged: console.log("has mouse:", hasMouse) } When I launch the example with qmlscene on my arale with no mouse connected, I’m not seeing any output (expected). Then I connect a bluetooth keyboard/mouse combo, and I’m seeing the following: mice model count: 1 0 added mouse: QInputDevice(0x17f6298) 1 (note how 'hasMouse', which supposedly was initially false, hasn’t been updated) Then I disconnect the combo, and I’m seeing the following: mice model count: 0 1 has mouse: true removed mouse: 15 0 Then I connect it again, and I’m seeing the following: mice model count: 1 0 has mouse: false added mouse: QInputDevice(0x18ee508) 1 It appears the countChanged property is emitted before a device is added to/removed from the model, and thus the row count hasn’t actually been updated yet. So any property binding that relies on 'count' will have an incorrect value. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtsystems-opensource-src/+bug/1646080/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1653487] [NEW] seccomp argument filtering not working on trusty(?)
You have been subscribed to a public bug: The snapd build on trusty for amd64 fails with the following error: """ make[2]: Entering directory `/tmp/snapd-2.20.1~14.04/cmd/snap-confine/tests' ... PASS: test_restrictions_working FAIL: test_restrictions_working_args """ (see https://launchpad.net/ubuntu/+source/snapd/2.20.1~14.04/+build/11759913) The same build works for i386 and armhf. I can reproduce this in a trusty chroot, upon further investigation it looks like the version of libseccomp (2.1.1) in trusty-proposed is the culprit. When I upgrade: """ Upgrade: libseccomp2:amd64 (2.1.1-1ubuntu1~trusty1, 2.2.3-2ubuntu1~ubuntu14.04.1), libseccomp-dev:amd64 (2.1.1-1ubuntu1~trusty1, 2.2.3-2ubuntu1~ubuntu14.04.1) all tests run fine. It looks like an issue with seccomp argument filtering (bpf) on 64 bit systems. This https://github.com/seccomp/libseccomp/releases/tag/v2.2.1 might include the missing fix, however I have not looked in detail what patch exactly we may need. Fwiw, we don't see this in spread because we build the package in the spread tests with `DEB_BUILD_OPTIONS='nocheck testkeys' dpkg- buildpackage` and we do not run the integration tests of snap-confine in anything else beside the package build (until https://github.com/snapcore/snapd/pull/2433/files is merged). ** Affects: libseccomp (Ubuntu) Importance: High Assignee: Jamie Strandboge (jdstrand) Status: In Progress -- seccomp argument filtering not working on trusty(?) https://bugs.launchpad.net/bugs/1653487 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp 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 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method
Same as post #8; this fixed it for me too... thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1638842 Title: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method Status in network-manager package in Ubuntu: Won't Fix Bug description: Hello, I installed Ubuntu 16.10 using a chroot. I use network-manager to manage connections. My system is up-to-date (so I use network-manager 1.2.4-0ubuntu1). Wifi works perfectly but I cannot connect to wired networks and using my phone's Bluetooth connection. Corresponding devices are said to be unmanaged by network-manager. nmcli dev outputs: DEVICETYPE STATE CONNECTION enp1s0ethernet unmanaged -- wlp2s0wifi disconnected -- 6C:9B:02:2C:EE:2C btunmanaged -- hfp/org/bluez/hci0/dev_6C_9B_02_2C_EE_2C gsm unmanaged -- loloopback unmanaged -- The following command has no effect: sudo nmcli dev set enp1s0 managed yes I can connect to a wired connection by doing: ifconfig enp1s0 up dhclient enp1s0 There is nothing in the file /etc/network/interfaces. Everything works perfectly if I downgrade network-manager to this version: network-manager_1.2.2-0ubuntu0.16.04.3_amd64.deb (http://packages.ubuntu.com/xenial-updates/amd64/network- manager/download). I had to install libreadline6 and downgrade nplan to meet dependencies. I don't know what to join to this bug report so please ask in case anything is needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records
I just hit this same problem, as described here: https://lists.ubuntu.com/archives/ubuntu-devel/2017-January/039623.html -- 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/1647031 Title: systemd-resolved’s 127.0.0.53 server does not follow CNAME records Status in systemd: New Status in systemd package in Ubuntu: Triaged Bug description: $ systemd-resolve www.freedesktop.org www.freedesktop.org: 131.252.210.176 2610:10:20:722:a800:ff:feda:470f (annarchy.freedesktop.org) -- Information acquired via protocol DNS in 673.6ms. -- Data is authenticated: no $ ping www.freedesktop.org ping: www.freedesktop.org: Name or service not known $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 $ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53 ;www.freedesktop.org. IN A www.freedesktop.org. 7146IN CNAME annarchy.freedesktop.org. $ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8 ;www.freedesktop.org. IN A www.freedesktop.org. 14399 IN CNAME annarchy.freedesktop.org. annarchy.freedesktop.org. 14399 IN A 131.252.210.176 I trust it needn’t be explained why this makes the internet almost completely useless in zesty. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1647031/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1589637] Re: Unable to open multiple instances of the same app
** Branch linked: lp:~ted/ubuntu-app-launch/signal-instances -- 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/1589637 Title: Unable to open multiple instances of the same app Status in Canonical System Image: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in ubuntu-app-launch package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: You're unable to open two instances of the same app. Such as gedit or firefox. qtmir needs instance-based signals: app instance started, app instance stopped, etc As in http://bazaar.launchpad.net/~indicator-applet-developers/ubuntu-app-launch/trunk.16.10/view/head:/libubuntu-app-launch/registry.h#L77 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1589637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1654075] [NEW] multiarch support broken in yakkety
Public bug reported: In Ubuntu 16.10 amd64 system the 32-bit heimdal libraries packages cannot be installed together with 64-bit packages, i.e.: $ sudo apt install libroken18-heimdal libroken18-heimdal:i386 Reading package lists... Done Building dependency tree Reading state information... Done libroken18-heimdal is already the newest version (1.7~git20160703+dfsg-1). 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: libroken18-heimdal : Breaks: libroken18-heimdal:i386 (!= 1.7~git20160703+dfsg-1) but 1.7~git20150920+dfsg-4ubuntu1 is to be installed libroken18-heimdal:i386 : Breaks: libroken18-heimdal (!= 1.7~git20150920+dfsg-4ubuntu1) but 1.7~git20160703+dfsg-1 is to be installed E: Unable to correct problems, you have held broken packages. ** Affects: heimdal (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1654075 Title: multiarch support broken in yakkety Status in heimdal package in Ubuntu: New Bug description: In Ubuntu 16.10 amd64 system the 32-bit heimdal libraries packages cannot be installed together with 64-bit packages, i.e.: $ sudo apt install libroken18-heimdal libroken18-heimdal:i386 Reading package lists... Done Building dependency tree Reading state information... Done libroken18-heimdal is already the newest version (1.7~git20160703+dfsg-1). 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: libroken18-heimdal : Breaks: libroken18-heimdal:i386 (!= 1.7~git20160703+dfsg-1) but 1.7~git20150920+dfsg-4ubuntu1 is to be installed libroken18-heimdal:i386 : Breaks: libroken18-heimdal (!= 1.7~git20150920+dfsg-4ubuntu1) but 1.7~git20160703+dfsg-1 is to be installed E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1654075/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1654070] Re: lies about upgrading pulseaudio-module-gconf
This still happens with the Zesty version of unattended-upgrades on Xenial so bears further investigation. ** Tags added: xenial zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1654070 Title: lies about upgrading pulseaudio-module-gconf Status in unattended-upgrades package in Ubuntu: New Bug description: I've been getting mail for days about pulseaudio-module-gconf and -module-zeroconf being upgraded, come to find out its not really happening. bdmurray@flash:~$ sudo /usr/bin/unattended-upgrade --debug --verbose Initial blacklisted packages: nvidia-304 Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: ['o=Ubuntu,a=xenial', 'o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates'] Checking: pulseaudio-module-gconf ([]) Checking: pulseaudio-module-zeroconf ([]) pkgs that look like they should be upgraded: pulseaudio-module-gconf pulseaudio-module-zeroconf Fetched 0 B in 0s (0 B/s) fetch.run() result: 0 blacklist: ['nvidia-304'] whitelist: [] Checking the black and whitelist: pulseaudio-module-gconf Checking the black and whitelist: pulseaudio-module-zeroconf Packages that will be upgraded: pulseaudio-module-gconf pulseaudio-module-zeroconf Writing dpkg log to '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' All upgrades installed InstCount=0 DelCount=0 BrokenCount=0 Extracting content from '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' since '2017-01-04 12:27:12' Sending mail to 'bdmurray@bizarro.watchtower.local' mail returned: 0 bdmurray@flash:~$ apt-cache policy pulseaudio-module-gconf pulseaudio-module-gconf: Installed: 1:8.0-0ubuntu3 Candidate: 1:8.0-0ubuntu3.1 Version table: 1:8.0-0ubuntu3.1 500 500 http://192.168.10.7/ubuntu xenial-updates/universe amd64 Packages *** 1:8.0-0ubuntu3 500 500 http://192.168.10.7/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654070/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1639517] Re: black screen when booting
FFab, thank you for reporting this and helping make Ubuntu better. To clarify your Bug Description: >"When booting the screen is black – backlight on – off - on." Are you noting that the laptop LCD backlight goes from 0% brightness to 100% automatically? If so, how often does it cycle between the two? If so, as per your attachment https://launchpadlibrarian.net/292333261/CurrentDmesg.txt : [0.576786] [Firmware Bug]: ACPI: No _BQC method, cannot determine initial brightness ** This bug is no longer a duplicate of bug 1597079 [HP Pavilion Notebook - 15-ab141na] Black Screen when Booting ** Summary changed: - black screen when booting + [HP Pavilion Notebook - 17-g164ng] black screen when booting ** Tags added: latest-bios-f.41 ** Description changed: - My notebook is a HP Pavilion 17-g164ng with an AMD A10-8780P APU and 2 - graphic subsystems - Carrizo, a VGA compatible controller and Topaz. - - When booting the screen is black – backlight on – off - on. - When HDD is inactive - - keyboard is not locked and I can shutdown/reboot by Alt + Print +o/b or Strg + Alt + Del + When booting the screen is black – backlight on – off - on. + When HDD is inactive + - keyboard is not locked and I can shutdown/reboot by Alt + Print +o/b or Strg + Alt + Del - remote access e.g. using ssh is possible - Testsystems: Ubuntu/Kubuntu 14.04, 15.10, 16.04, 16.10. - - Workaround, UEFI-boot, kernel parameters : - nomodeset - nomodeset xforcevesa - Resolution without/with xforcevesa: 800x600 / 1600x900 – the optimal resolution + My notebook is a HP Pavilion 17-g164ng with an AMD A10-8780P APU and 2 + graphic subsystems - Carrizo, a VGA compatible controller and Topaz. In 14.04 and 15.10 I installed fglrx – the AMD driver. It seems very similar to that described in #1597079. The bug report was generated from a remote PC. My HP notebook was started without any workaround parameters. - This apport does'nt display the second graphic subsystem Topaz R7 as an apport generated with nomodeset xforcevesa. + This apport doesn't display the second graphic subsystem Topaz R7 as an apport generated with nomodeset xforcevesa. + + WORKAROUND: When booting in UEFI mode, use kernel parameters: + nomodeset + + or: + nomodeset xforcevesa + + Resolution without xforcevesa: 800x600 + Resolution with xforcevesa: 1600x900 – the optimal resolution 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 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Nov 5 23:40:19 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: - Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c4) (prog-if 00 [VGA controller]) -Subsystem: Hewlett-Packard Company Carrizo [103c:80b6] + Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c4) (prog-if 00 [VGA controller]) + Subsystem: Hewlett-Packard Company Carrizo [103c:80b6] InstallationDate: Installed on 2016-11-03 (2 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: HP HP Pavilion Notebook ProcEnviron: - TERM=xterm - PATH=(custom, no user) - LANG=de_DE.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + LANG=de_DE.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed root=UUID=d006dbb4-8a2a-4cfe-b38e-7d35b34bca09 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.41 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 80B6 dmi.board.vendor: HP dmi.board.version: 81.32 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.41:bd09/19/2016:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn80B6:rvr81.32:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.sys.vendor: HP version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.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
[Touch-packages] [Bug 1652564] Re: [i965 gen7][regression][patch]Intel mesa driver raises SIGFPE.
Should not it be backported to 16.04 since it's LTS and it is requires only trivial patch? ** Changed in: mesa (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1652564 Title: [i965 gen7][regression][patch]Intel mesa driver raises SIGFPE. Status in mesa package in Ubuntu: Confirmed Bug description: There was a regression in intel mesa driver that caused raise of SIGFPE signal which resulted in startup error messages (about division by zero or invalid floating point operation) in some applications and games sensitive to this behavior. Currently it resolved in upstream: https://bugs.freedesktop.org/show_bug.cgi?id=95419 By following commit: https://cgit.freedesktop.org/mesa/mesa/commit/?id=01c89ccc5d1529aa1efbae80c8ef641a59abbd93 Is it possible to include foregoing patch to avoid bug in current distributions? Distribution: Ubuntu 16.04 Video card: Intel HD 4600 Mesa version: 11.2.0-1ubuntu2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1652564/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1652491] Re: Sync elfutils 0.166-2.2 (main) from Debian unstable (main)
Already in zesty-proposed, but FTBFS on s390x (retrying does not help). Please look if you can. ** Changed in: elfutils (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to elfutils in Ubuntu. https://bugs.launchpad.net/bugs/1652491 Title: Sync elfutils 0.166-2.2 (main) from Debian unstable (main) Status in elfutils package in Ubuntu: Fix Committed Bug description: Please sync elfutils 0.166-2.2 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Don't run the run-backtrace-native-biarch test. The test was fixed in -2.2. I confirmed that the package builds successfully on all normal PPA architectures. Changelog entries since current zesty version 0.166-2ubuntu1: elfutils (0.166-2.2) unstable; urgency=medium * Non-maintainer upload. * testsuite-amd64-fix-backtrace-native.patch: Backport upstream patch to fix FTBFS on amd64 (Closes: #841124) -- James ClarkeTue, 18 Oct 2016 08:13:34 +0100 elfutils (0.166-2.1) unstable; urgency=medium * Non-maintainer upload. * Build-Depend on gcc-multilib and libc6-dbg on sparc64 (Closes: #832584) -- James Clarke Fri, 07 Oct 2016 15:16:09 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/1652491/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1652478] Re: Sync json-c 0.12.1-1.1 (main) from Debian unstable (main)
This bug was fixed in the package json-c - 0.12.1-1.1 Sponsored for Jeremy Bicha (jbicha) --- json-c (0.12.1-1.1) unstable; urgency=medium * Non-maintainer upload. * debian/control: Fix Vcs-Browser URL * debian/libjson-c-dev.links: Fix library symlinks to not collide between /lib/ and /usr/lib/ (Closes: #843145, LP: #1629552) -- Martin PittMon, 14 Nov 2016 11:33:17 +0100 ** Changed in: json-c (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1652478 Title: Sync json-c 0.12.1-1.1 (main) from Debian unstable (main) Status in json-c package in Ubuntu: Fix Released Bug description: Please sync json-c 0.12.1-1.1 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * debian/libjson-c-dev.links: Fix library symlinks to not collide between /lib/ and /usr/lib/. (Closes: #843145, LP: #1629552) That change was applied in Debian Changelog entries since current zesty version 0.12.1-1ubuntu1: json-c (0.12.1-1.1) unstable; urgency=medium * Non-maintainer upload. * debian/control: Fix Vcs-Browser URL * debian/libjson-c-dev.links: Fix library symlinks to not collide between /lib/ and /usr/lib/ (Closes: #843145, LP: #1629552) -- Martin Pitt Mon, 14 Nov 2016 11:33:17 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1652478/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1653489] Re: [LTCTest][OPAL][FW860.20] Upgrade to Ubuntu 16.04.2 Alpha from Ubuntu 16.04.1 is dropping to (initramfs)
But ipr.ko is already included. There must be some other missing boot essential module. ~/ubuntu/ubuntu-yakkety$ git grep ipr debian.master/control.d/generic.inclusion-list debian.master/control.d/generic.inclusion-list:drivers/scsi/ipr.ko -- 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/1653489 Title: [LTCTest][OPAL][FW860.20] Upgrade to Ubuntu 16.04.2 Alpha from Ubuntu 16.04.1 is dropping to (initramfs) Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: @kernel-team Please move ipr module from image-extra to image package. ---Problem Description--- Upgrade to Ubuntu 16.04.2 Alpha from Ubuntu 16.04.1 is dropping to (initramfs) Contact Information = pavsu...@in.ibm.com ---uname output--- Linux (none) 4.8.0-27-generic #29~16.04.1-Ubuntu SMP Fri Nov 4 17:24:37 UTC 2016 ppc64le GNU/Linux ---Additional Hardware Info--- root@powerkvm3-lp1:~# lspci :00:00.0 PCI bridge: IBM Device 03dc :01:00.0 RAID bus controller: IBM Obsidian-E PCI-E SCSI controller (rev 01) 0001:00:00.0 PCI bridge: IBM Device 03dc 0001:01:00.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch (rev ca) 0001:02:01.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch (rev ca) 0001:02:08.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch (rev ca) 0001:02:09.0 PCI bridge: PLX Technology, Inc. PEX 8732 32-lane, 8-Port PCI Express Gen 3 (8.0 GT/s) Switch (rev ca) 0001:03:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) 0001:03:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) 0001:03:00.2 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) 0001:03:00.3 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) 0001:04:00.0 RAID bus controller: IBM PCI-E IPR SAS Adapter (ASIC) (rev 01) 0001:05:00.0 RAID bus controller: IBM PCI-E IPR SAS Adapter (ASIC) (rev 01) 0004:00:00.0 PCI bridge: IBM Device 03dc 0004:01:00.0 Fibre Channel: Emulex Corporation Lancer-X: LightPulse Fibre Channel Host Adapter (rev 10) 0004:01:00.1 Fibre Channel: Emulex Corporation Lancer-X: LightPulse Fibre Channel Host Adapter (rev 10) 0005:00:00.0 PCI bridge: IBM Device 03dc 0005:01:00.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca) 0005:02:01.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca) 0005:02:08.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca) 0005:02:09.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca) 0005:02:10.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca) 0005:02:11.0 PCI bridge: PLX Technology, Inc. Device 8748 (rev ca) 0005:03:00.0 USB controller: Texas Instruments TUSB73x0 SuperSpeed USB 3.0 xHCI Host Controller (rev 02) 0005:09:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) 0005:09:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) 0005:09:00.2 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) 0005:09:00.3 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) 0005:0f:00.0 Fibre Channel: Emulex Corporation Saturn-X: LightPulse Fibre Channel Host Adapter (rev 03) 0005:0f:00.1 Fibre Channel: Emulex Corporation Saturn-X: LightPulse Fibre Channel Host Adapter (rev 03) 0040:00:00.0 PCI bridge: IBM Device 03dc 0044:00:00.0 PCI bridge: IBM Device 03dc 0044:01:00.0 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) (rev 10) 0044:01:00.1 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) (rev 10) 0044:01:00.2 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) (rev 10) 0044:01:00.3 Ethernet controller: Emulex Corporation OneConnect NIC (Lancer) (rev 10) 0044:01:00.4 Fibre Channel: Emulex Corporation OneConnect FCoE Initiator (Lancer) (rev 10) 0044:01:00.5 Fibre Channel: Emulex Corporation OneConnect FCoE Initiator (Lancer) (rev 10) 0045:00:00.0 PCI bridge: IBM Device 03dc 0045:01:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) 0045:01:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) 0045:01:00.2 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) 0045:01:00.3 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) Machine Type = P8 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Install Ubuntu
[Touch-packages] [Bug 1654070] [NEW] lies about upgrading pulseaudio-module-gconf
Public bug reported: I've been getting mail for days about pulseaudio-module-gconf and -module-zeroconf being upgraded, come to find out its not really happening. bdmurray@flash:~$ sudo /usr/bin/unattended-upgrade --debug --verbose Initial blacklisted packages: nvidia-304 Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: ['o=Ubuntu,a=xenial', 'o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates'] Checking: pulseaudio-module-gconf ([]) Checking: pulseaudio-module-zeroconf ([]) pkgs that look like they should be upgraded: pulseaudio-module-gconf pulseaudio-module-zeroconf Fetched 0 B in 0s (0 B/s) fetch.run() result: 0 blacklist: ['nvidia-304'] whitelist: [] Checking the black and whitelist: pulseaudio-module-gconf Checking the black and whitelist: pulseaudio-module-zeroconf Packages that will be upgraded: pulseaudio-module-gconf pulseaudio-module-zeroconf Writing dpkg log to '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' All upgrades installed InstCount=0 DelCount=0 BrokenCount=0 Extracting content from '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' since '2017-01-04 12:27:12' Sending mail to 'bdmurray@bizarro.watchtower.local' mail returned: 0 bdmurray@flash:~$ apt-cache policy pulseaudio-module-gconf pulseaudio-module-gconf: Installed: 1:8.0-0ubuntu3 Candidate: 1:8.0-0ubuntu3.1 Version table: 1:8.0-0ubuntu3.1 500 500 http://192.168.10.7/ubuntu xenial-updates/universe amd64 Packages *** 1:8.0-0ubuntu3 500 500 http://192.168.10.7/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1654070 Title: lies about upgrading pulseaudio-module-gconf Status in unattended-upgrades package in Ubuntu: New Bug description: I've been getting mail for days about pulseaudio-module-gconf and -module-zeroconf being upgraded, come to find out its not really happening. bdmurray@flash:~$ sudo /usr/bin/unattended-upgrade --debug --verbose Initial blacklisted packages: nvidia-304 Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: ['o=Ubuntu,a=xenial', 'o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates'] Checking: pulseaudio-module-gconf ([]) Checking: pulseaudio-module-zeroconf ([]) pkgs that look like they should be upgraded: pulseaudio-module-gconf pulseaudio-module-zeroconf Fetched 0 B in 0s (0 B/s) fetch.run() result: 0 blacklist: ['nvidia-304'] whitelist: [] Checking the black and whitelist: pulseaudio-module-gconf Checking the black and whitelist: pulseaudio-module-zeroconf Packages that will be upgraded: pulseaudio-module-gconf pulseaudio-module-zeroconf Writing dpkg log to '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' All upgrades installed InstCount=0 DelCount=0 BrokenCount=0 Extracting content from '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' since '2017-01-04 12:27:12' Sending mail to 'bdmurray@bizarro.watchtower.local' mail returned: 0 bdmurray@flash:~$ apt-cache policy pulseaudio-module-gconf pulseaudio-module-gconf: Installed: 1:8.0-0ubuntu3 Candidate: 1:8.0-0ubuntu3.1 Version table: 1:8.0-0ubuntu3.1 500 500 http://192.168.10.7/ubuntu xenial-updates/universe amd64 Packages *** 1:8.0-0ubuntu3 500 500 http://192.168.10.7/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654070/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630516] Re: Logrotate fails repeatedly with /etc/cron.daily/logrotate: error: error creating output file /var/log/... File exists run-parts: /etc/cron.daily/logrotate exited wit
** Changed in: logrotate (Debian) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1630516 Title: Logrotate fails repeatedly with /etc/cron.daily/logrotate: error: error creating output file /var/log/... File exists run-parts: /etc/cron.daily/logrotate exited with return code 1 Status in logrotate package in Ubuntu: Confirmed Status in logrotate package in Debian: Fix Released Bug description: Good afternoon. I have started seeing something very similar to Debian Dug 734688 "Logs are not rotated for a month" but in the latest Ubuntu LTS (16.04). I seem to have $ logrotate --version logrotate 3.8.7 bundled in it. A few weeks ago I started getting root emails such as this: > Subject: Crontest -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ) > > /etc/cron.daily/logrotate: > error: error creating output file /var/log/munin/munin-node.log.1: File exists > run-parts: /etc/cron.daily/logrotate exited with return code 1 When I inspected the area of concern I was able to see that there was an existing .1 file. manager@warden:/var/log/munin$ ll total 580 drwxr-xr-x 2 munin adm 4096 Sep 27 06:31 ./ drwxr-xr-x 13 root syslog 4096 Oct 5 06:26 ../ -rw-r--r-- 1 root root 3440 Sep 26 13:39 munin-node-configure.log -rw-r--r-- 1 root root 490251 Oct 5 10:25 munin-node.log -rw-r--r-- 1 root root56598 Sep 21 02:01 munin-node.log.1 -rw-r--r-- 1 root root24576 Aug 31 02:01 munin-node.log.2 -rw-r--r-- 1 root root 1906 Sep 19 06:25 munin-node.log.8.gz The contents of the munin-node.log file seem to run from the 19th September until today. Unlike other parts of this bug the .1 and .2 files do not seem to be already compressed. I deleted all but the munin-node.log file to see if it would resolve the problem and was going to leave it at that. Then I noticed that I have had another Ubuntu machine which has been sending similar emails for the past week: > Subject: Cron test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ) > > /etc/cron.daily/logrotate: > error: error creating output file /var/log/syslog.1.gz: File exists > run-parts: /etc/cron.daily/logrotate exited with return code 1 Different file, different machine but a very similar error message. Checking on the syslog file I can see that it better fits with other reports on this bug as my duplicated .1 files has a corresponding .1.gz file. manager@trac:/var/log$ ll syslog* -rw-r- 1 syslog adm 918492 Oct 5 10:30 syslog -rw-r- 1 syslog adm 125819 Sep 30 06:25 syslog.1 -rw-r- 1 syslog adm 20638 Oct 2 02:01 syslog.1.gz -rw-r- 1 syslog adm 41989 Sep 30 02:00 syslog.2.gz -rw-r- 1 syslog adm 18654 Sep 28 02:01 syslog.3.gz -rw-r- 1 syslog adm 31720 Sep 26 06:40 syslog.4.gz -rw-r- 1 syslog adm 33151 Sep 25 02:01 syslog.5.gz -rw-r- 1 syslog adm 17290 Sep 23 02:01 syslog.6.gz -rw-r- 1 syslog adm 39275 Sep 21 06:35 syslog.7.gz There has been some speculation that a full or nearly full /var partition would cause this issue. I can confirm that /var is part of / on my systems and that presently both of them have several gigabytes of space. I run Munin an Icinga to monitor system state. Neither of these show / being completely full in the past month. They have both had /boot fill significantly. Trac had a highest use value of / being 99.28% full in the past year but warden has only had a peak of 33% in the past year. A quick search of the internet suggests a couple of other people reporting similar issues: https://github.com/gitlabhq/gitlabhq/issues/6894 http://raspberrypi.stackexchange.com/questions/22545/why-are-system-logs-not-rotating I do not believe that I have altered by logrotate configuration files but here is a copy of the ones I know about: $ cat /etc/logrotate.conf # see "man logrotate" for details # rotate log files weekly weekly # use the syslog group by default, since this is the owning group # of /var/log/syslog. su root syslog # keep 4 weeks worth of backlogs rotate 4 # create new (empty) log files after rotating old ones create # uncomment this if you want your log files compressed #compress # packages drop log rotation information into this directory include /etc/logrotate.d # no packages own wtmp, or btmp -- we'll rotate them here /var/log/wtmp { missingok monthly create 0664 root utmp rotate 1 } /var/log/btmp { missingok monthly create 0660 root utmp rotate 1 } # system-specific logs may be configured here $ cat /etc/logrotate.d/rsyslog /var/log/syslog { rotate 7 daily
[Touch-packages] [Bug 1650848] Re: Move evolution specific deps out of the bluez-obex
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1650848 Title: Move evolution specific deps out of the bluez-obex Status in bluez package in Ubuntu: Confirmed Bug description: I do not have eveolution installed so why do I have evolution-data- server-common and libedataserver-1.2-22 installed on my system? the package to fix is bluez-obexd I'm on Ubuntu 16.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1650848/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1651818] Re: busybox-initramfs needs different compile options to work with cryptroot-unlock
** Changed in: cryptsetup (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1651818 Title: busybox-initramfs needs different compile options to work with cryptroot-unlock Status in busybox package in Ubuntu: Confirmed Status in cryptsetup package in Ubuntu: Confirmed Bug description: The cryptroot-unlock script in the cryptsetup package does not work in initramfs. It fails because "ps -e" is not available in busybox for initramfs. When building the package with CONFIG_DESKTOP=y CONFIG_EXTRA_COMPAT=y the needed commands (ps, grep) with parameter are there and it works. Tetsted on Ubuntu GNOME 16.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1651818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1642622] Re: UITK E305 expected 2 blank lines after class or function definition, found 1
This bug was fixed in the package ubuntu-ui-toolkit - 1.3.2151+17.04.20161223 --- ubuntu-ui-toolkit (1.3.2151+17.04.20161223) zesty; urgency=medium [ Zsombor Egri ] * Enable mouse, touchpad and keyboard detection in UITK. Fixes LP: #1536669 * Colors revisited. * Qt5.7 related fix for theming - by Glen Whitney. [ Timo Jyrinki ] * parent = Q_NULLPTR instead of 0. Fixes LP: #1642617 * More blank lines. Fixes LP: #1642622 * Drop tst_pickerpanel.11.qml (deprecated). [ Christian Dywan ] * Include OSK input in TextArea.displayText. Fixes LP: #1595910 * Drop questionable color tests from tst_textarea.11.qml. Fixes LP: #1624342 [ Lukáš Tinkl ] * Fix slider progress rect with RTL languages. -- Marco Trevisan (Treviño)Fri, 23 Dec 2016 14:52:55 + ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1642622 Title: UITK E305 expected 2 blank lines after class or function definition, found 1 Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Bug description: When trying a build with Qt 5.7.1: --- /<>/ubuntu-ui-toolkit-1.3.2141+16.10.20161013.5+isreallystaging1~1/.bazaar/plugins/makecheck_ubuntu_ui_toolkit.py:38:1: E305 expected 2 blank lines after class or function definition, found 1 /<>/ubuntu-ui-toolkit-1.3.2141+16.10.20161013.5+isreallystaging1~1/.bazaar/plugins/packaging_sorting.py:55:1: E305 expected 2 blank lines after class or function definition, found 1 Makefile:688: recipe for target 'check' failed --- https://launchpadlibrarian.net/293823357/buildlog_ubuntu-zesty-armhf.ubuntu-ui-toolkit_1.3.2141+16.10.20161013.5+isreallystaging1~1_BUILDING.txt.gz https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1642622/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1595910] Re: review input field: send button issues with predictive OSK
This bug was fixed in the package ubuntu-ui-toolkit - 1.3.2151+17.04.20161223 --- ubuntu-ui-toolkit (1.3.2151+17.04.20161223) zesty; urgency=medium [ Zsombor Egri ] * Enable mouse, touchpad and keyboard detection in UITK. Fixes LP: #1536669 * Colors revisited. * Qt5.7 related fix for theming - by Glen Whitney. [ Timo Jyrinki ] * parent = Q_NULLPTR instead of 0. Fixes LP: #1642617 * More blank lines. Fixes LP: #1642622 * Drop tst_pickerpanel.11.qml (deprecated). [ Christian Dywan ] * Include OSK input in TextArea.displayText. Fixes LP: #1595910 * Drop questionable color tests from tst_textarea.11.qml. Fixes LP: #1624342 [ Lukáš Tinkl ] * Fix slider progress rect with RTL languages. -- Marco Trevisan (Treviño)Fri, 23 Dec 2016 14:52:55 + ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Invalid => Fix Released -- 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/1595910 Title: review input field: send button issues with predictive OSK Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Triaged Bug description: Steps to reproduce: * Make sure predictive OSK is enabled * got an app in the store and start writing a review * Just write one word, no space after it (so that it is underlined for text correction things) => actual: The send button is disabled even though the text field holds a word => expected: The send button should be enabled Most likely the Send button is enabled/disabled based on inputField.text, while it should be inputField.displayText instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1595910/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1536669] Re: "BottomEdge" component does not support automatic mouse detection
This bug was fixed in the package ubuntu-ui-toolkit - 1.3.2151+17.04.20161223 --- ubuntu-ui-toolkit (1.3.2151+17.04.20161223) zesty; urgency=medium [ Zsombor Egri ] * Enable mouse, touchpad and keyboard detection in UITK. Fixes LP: #1536669 * Colors revisited. * Qt5.7 related fix for theming - by Glen Whitney. [ Timo Jyrinki ] * parent = Q_NULLPTR instead of 0. Fixes LP: #1642617 * More blank lines. Fixes LP: #1642622 * Drop tst_pickerpanel.11.qml (deprecated). [ Christian Dywan ] * Include OSK input in TextArea.displayText. Fixes LP: #1595910 * Drop questionable color tests from tst_textarea.11.qml. Fixes LP: #1624342 [ Lukáš Tinkl ] * Fix slider progress rect with RTL languages. -- Marco Trevisan (Treviño)Fri, 23 Dec 2016 14:52:55 + ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtsystems-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1536669 Title: "BottomEdge" component does not support automatic mouse detection Status in Canonical System Image: In Progress Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Status in qtsystems-opensource-src package in Ubuntu: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Status in qtsystems-opensource-src package in Ubuntu RTM: Fix Released Bug description: BottomEdge component does not work property with mouse unless you set the: QuickUtils.mouseAttached = true This should be done automatically by SDK. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1536669/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624342] Re: tst_textarea.11.qml unit test fails
This bug was fixed in the package ubuntu-ui-toolkit - 1.3.2151+17.04.20161223 --- ubuntu-ui-toolkit (1.3.2151+17.04.20161223) zesty; urgency=medium [ Zsombor Egri ] * Enable mouse, touchpad and keyboard detection in UITK. Fixes LP: #1536669 * Colors revisited. * Qt5.7 related fix for theming - by Glen Whitney. [ Timo Jyrinki ] * parent = Q_NULLPTR instead of 0. Fixes LP: #1642617 * More blank lines. Fixes LP: #1642622 * Drop tst_pickerpanel.11.qml (deprecated). [ Christian Dywan ] * Include OSK input in TextArea.displayText. Fixes LP: #1595910 * Drop questionable color tests from tst_textarea.11.qml. Fixes LP: #1624342 [ Lukáš Tinkl ] * Fix slider progress rect with RTL languages. -- Marco Trevisan (Treviño)Fri, 23 Dec 2016 14:52:55 + ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1624342 Title: tst_textarea.11.qml unit test fails Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Bug description: Fails with Qt 5.6. FAIL! : components::TextAreaAPI::test_0_color() TextArea.color is same as TextEdit.canUndo Actual (): #5d5d5d Expected (): #00 Loc: [/tmp/buildd/ubuntu-ui-toolkit-1.3.2085+16.10.20160831.4/tests/unit/visual/tst_textarea.11.qml(141)] See https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu-ui-toolkit-ci- amd64-devel/1201/consoleFull To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1624342/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1642617] Re: UITK FTBFS on Qt 5.7.1
This bug was fixed in the package ubuntu-ui-toolkit - 1.3.2151+17.04.20161223 --- ubuntu-ui-toolkit (1.3.2151+17.04.20161223) zesty; urgency=medium [ Zsombor Egri ] * Enable mouse, touchpad and keyboard detection in UITK. Fixes LP: #1536669 * Colors revisited. * Qt5.7 related fix for theming - by Glen Whitney. [ Timo Jyrinki ] * parent = Q_NULLPTR instead of 0. Fixes LP: #1642617 * More blank lines. Fixes LP: #1642622 * Drop tst_pickerpanel.11.qml (deprecated). [ Christian Dywan ] * Include OSK input in TextArea.displayText. Fixes LP: #1595910 * Drop questionable color tests from tst_textarea.11.qml. Fixes LP: #1624342 [ Lukáš Tinkl ] * Fix slider progress rect with RTL languages. -- Marco Trevisan (Treviño)Fri, 23 Dec 2016 14:52:55 + ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1642617 Title: UITK FTBFS on Qt 5.7.1 Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Bug description: https://launchpadlibrarian.net/293820525/buildlog_ubuntu-zesty-amd64.ubuntu-ui-toolkit_1.3.2141+16.10.20161013.5build1~1_BUILDING.txt.gz --- cc1plus: all warnings being treated as errors Makefile:1005: recipe for target '.obj/header_ubuntutoolkitmodule.o' failed make[3]: *** [.obj/header_ubuntutoolkitmodule.o] Error 1 --- https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1642617/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1654053] Re: package initramfs-tools 0.122ubuntu8.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- 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/1654053 Title: package initramfs-tools 0.122ubuntu8.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: I cant install nothing. Always the system back me the same error. thanks. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu 16.04.1 LTS Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Unable to locate package pkgname 3) What you expected to happen install packages 4) What happened instead occurs the error and not installed ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8.7 ProcVersionSignature: Ubuntu 3.13.0-98.145-generic 3.13.11-ckt39 Uname: Linux 3.13.0-98-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 Date: Wed Jan 4 16:53:32 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DpkgHistoryLog: Start-Date: 2017-01-04 16:52:10 Commandline: aptdaemon role='role-commit-packages' sender=':1.158' Upgrade: libnss3-tools:amd64 (2:3.23-0ubuntu0.16.04.1, 2:3.26.2-0ubuntu0.16.04.2), libnss3-nssdb:amd64 (2:3.23-0ubuntu0.16.04.1, 2:3.26.2-0ubuntu0.16.04.2), grub-common:amd64 (2.02~beta2-36ubuntu3.2, 2.02~beta2-36ubuntu3.6), grub2-common:amd64 (2.02~beta2-36ubuntu3.2, 2.02~beta2-36ubuntu3.6), libnss3-1d:amd64 (2:3.23-0ubuntu0.16.04.1, 2:3.26.2-0ubuntu0.16.04.2), grub-efi-amd64-bin:amd64 (2.02~beta2-36ubuntu3.2, 2.02~beta2-36ubuntu3.6), grub-efi-amd64:amd64 (2.02~beta2-36ubuntu3.2, 2.02~beta2-36ubuntu3.6), grub-efi-amd64-signed:amd64 (1.66.2+2.02~beta2-36ubuntu3.2, 1.66.6+2.02~beta2-36ubuntu3.6), libnss3:amd64 (2:3.23-0ubuntu0.16.04.1, 2:3.26.2-0ubuntu0.16.04.2) ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-07-25 (163 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: initramfs-tools Title: package initramfs-tools 0.122ubuntu8.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1654053/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1651883] Re: package linux-firmware 1.157.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- 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/1651883 Title: package linux-firmware 1.157.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: during a do-release-upgrade from 14.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.6 ProcVersionSignature: Ubuntu 4.2.0-30.36~14.04.1-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 Date: Wed Dec 21 13:31:06 2016 Dependencies: ErrorMessage: subprocess installed post-installation script returned error exit status 1 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: initramfs-tools Title: package linux-firmware 1.157.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-12-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1651883/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1654053] [NEW] package initramfs-tools 0.122ubuntu8.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: I cant install nothing. Always the system back me the same error. thanks. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description:Ubuntu 16.04.1 LTS Release:16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Unable to locate package pkgname 3) What you expected to happen install packages 4) What happened instead occurs the error and not installed ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8.7 ProcVersionSignature: Ubuntu 3.13.0-98.145-generic 3.13.11-ckt39 Uname: Linux 3.13.0-98-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 Date: Wed Jan 4 16:53:32 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DpkgHistoryLog: Start-Date: 2017-01-04 16:52:10 Commandline: aptdaemon role='role-commit-packages' sender=':1.158' Upgrade: libnss3-tools:amd64 (2:3.23-0ubuntu0.16.04.1, 2:3.26.2-0ubuntu0.16.04.2), libnss3-nssdb:amd64 (2:3.23-0ubuntu0.16.04.1, 2:3.26.2-0ubuntu0.16.04.2), grub-common:amd64 (2.02~beta2-36ubuntu3.2, 2.02~beta2-36ubuntu3.6), grub2-common:amd64 (2.02~beta2-36ubuntu3.2, 2.02~beta2-36ubuntu3.6), libnss3-1d:amd64 (2:3.23-0ubuntu0.16.04.1, 2:3.26.2-0ubuntu0.16.04.2), grub-efi-amd64-bin:amd64 (2.02~beta2-36ubuntu3.2, 2.02~beta2-36ubuntu3.6), grub-efi-amd64:amd64 (2.02~beta2-36ubuntu3.2, 2.02~beta2-36ubuntu3.6), grub-efi-amd64-signed:amd64 (1.66.2+2.02~beta2-36ubuntu3.2, 1.66.6+2.02~beta2-36ubuntu3.6), libnss3:amd64 (2:3.23-0ubuntu0.16.04.1, 2:3.26.2-0ubuntu0.16.04.2) ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-07-25 (163 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: initramfs-tools Title: package initramfs-tools 0.122ubuntu8.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1654053 Title: package initramfs-tools 0.122ubuntu8.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: I cant install nothing. Always the system back me the same error. thanks. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu 16.04.1 LTS Release: 16.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Unable to locate package pkgname 3) What you expected to happen install packages 4) What happened instead occurs the error and not installed ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8.7 ProcVersionSignature: Ubuntu 3.13.0-98.145-generic 3.13.11-ckt39 Uname: Linux 3.13.0-98-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 Date: Wed Jan 4 16:53:32 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DpkgHistoryLog: Start-Date: 2017-01-04 16:52:10 Commandline: aptdaemon role='role-commit-packages' sender=':1.158' Upgrade: libnss3-tools:amd64 (2:3.23-0ubuntu0.16.04.1, 2:3.26.2-0ubuntu0.16.04.2), libnss3-nssdb:amd64 (2:3.23-0ubuntu0.16.04.1, 2:3.26.2-0ubuntu0.16.04.2), grub-common:amd64 (2.02~beta2-36ubuntu3.2, 2.02~beta2-36ubuntu3.6), grub2-common:amd64 (2.02~beta2-36ubuntu3.2, 2.02~beta2-36ubuntu3.6), libnss3-1d:amd64 (2:3.23-0ubuntu0.16.04.1, 2:3.26.2-0ubuntu0.16.04.2), grub-efi-amd64-bin:amd64 (2.02~beta2-36ubuntu3.2, 2.02~beta2-36ubuntu3.6), grub-efi-amd64:amd64 (2.02~beta2-36ubuntu3.2, 2.02~beta2-36ubuntu3.6), grub-efi-amd64-signed:amd64 (1.66.2+2.02~beta2-36ubuntu3.2, 1.66.6+2.02~beta2-36ubuntu3.6), libnss3:amd64 (2:3.23-0ubuntu0.16.04.1, 2:3.26.2-0ubuntu0.16.04.2) ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-07-25 (163 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all RelatedPackageVersions: dpkg
[Touch-packages] [Bug 1653725] Re: lxc-android-config not starting on ubuntu-touch/staging/* xenial-based images after lxc upgrade
** Also affects: lxc (Ubuntu Zesty) Importance: High Assignee: Christian Brauner (cbrauner) Status: Fix Committed ** Also affects: lxc-android-config (Ubuntu Zesty) Importance: High Status: New ** Also affects: lxc (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: lxc-android-config (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: lxc (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: lxc-android-config (Ubuntu Yakkety) Importance: Undecided Status: New ** No longer affects: lxc-android-config (Ubuntu) ** Changed in: lxc (Ubuntu Yakkety) Status: New => Triaged ** Changed in: lxc (Ubuntu Xenial) Status: New => Triaged ** Changed in: lxc (Ubuntu Yakkety) Importance: Undecided => High ** Changed in: lxc (Ubuntu Xenial) Importance: Undecided => High ** Also affects: lxc (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: lxc (Ubuntu Trusty) Status: New => Triaged ** Changed in: lxc (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: lxc (Ubuntu Xenial) Assignee: (unassigned) => Stéphane Graber (stgraber) ** Changed in: lxc (Ubuntu Yakkety) Assignee: (unassigned) => Stéphane Graber (stgraber) ** No longer affects: lxc-android-config (Ubuntu Xenial) ** No longer affects: lxc-android-config (Ubuntu Yakkety) ** No longer affects: lxc-android-config (Ubuntu Zesty) ** Changed in: lxc (Ubuntu Trusty) Assignee: (unassigned) => Stéphane Graber (stgraber) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1653725 Title: lxc-android-config not starting on ubuntu-touch/staging/* xenial-based images after lxc upgrade Status in Canonical System Image: Confirmed Status in lxc package in Ubuntu: Fix Committed Status in lxc source package in Trusty: Triaged Status in lxc source package in Xenial: Triaged Status in lxc source package in Yakkety: Triaged Status in lxc source package in Zesty: Fix Committed Bug description: As in topic. Since the 20161217 rootfs, after upgrade of lxc from 2.0.5-0ubuntu1~ubuntu16.04.3 to 2.0.6-0ubuntu1~ubuntu16.04.1 the lxc- android-config service does not start - making the devices unbootable. The syslog only states this: Jan 3 10:50:30 ubuntu-phablet systemd[1]: Starting LXC Android Config and Container Initialization... Jan 3 10:50:30 ubuntu-phablet kernel: [5.790810] (3)[1:systemd]SLEEP_EN = 0x1 Jan 3 10:50:30 ubuntu-phablet systemd[1]: Starting Light Display Manager... Jan 3 10:50:30 ubuntu-phablet systemd-udevd[672]: Could not generate persistent MAC address for ifb0: No such file or directory Jan 3 10:50:30 ubuntu-phablet systemd-udevd[684]: Could not generate persistent MAC address for ifb1: No such file or directory Jan 3 10:50:30 ubuntu-phablet lxc-start[1220]: You lack access to /var/lib/lxc Jan 3 10:50:30 ubuntu-phablet systemd[1]: lxc-android-config.service: Control process exited, code=exited status=1 Jan 3 10:50:30 ubuntu-phablet systemd[1]: Failed to start LXC Android Config and Container Initialization. Jan 3 10:50:30 ubuntu-phablet systemd[1]: Dependency failed for force-mtp.service. Jan 3 10:50:30 ubuntu-phablet systemd[1]: force-mtp.service: Job force-mtp.service/start failed with result 'dependency'. Jan 3 10:50:30 ubuntu-phablet systemd[1]: lxc-android-config.service: Unit entered failed state. Jan 3 10:50:30 ubuntu-phablet systemd[1]: lxc-android-config.service: Failed with result 'exit-code'. This makes all of our frieza and cooler devices useless for testing purposes. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1653725/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1632808] Re: Consider supporting IPv6 autoconf in configure_networking
I am also not aware of anyone in the MAAS space who _wants_ autoconf for ipv6 networks. I am aware of at least one who wants it OFF for their networks. -- 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/1632808 Title: Consider supporting IPv6 autoconf in configure_networking Status in MAAS: Triaged Status in initramfs-tools package in Ubuntu: Triaged Bug description: Because DHCPv6 only does addresses, and not routes, configure_networking needs to wait for the kernel to process a router- advertisement before returning claiming an IPv6 config (since all it will have is a /128 and no routes, making for a pretty useless network stack.) See Bug #1609898 for context. (The syntax for ip= should probably also be extended to allow SLAAC configuration. If the user said "dhcp", then we should insist on getting our answer from DHCP.) On the bright side, iscsi retries, so after 1 or more failures to connect, the router-advertisement comes in and the connect succeeds. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1632808/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1632808] Re: Consider supporting IPv6 autoconf in configure_networking
And leaving it triaged for MAAS, since once initramfs-tools supports it, MAAS will need to propagate that to the UI. -- 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/1632808 Title: Consider supporting IPv6 autoconf in configure_networking Status in MAAS: Triaged Status in initramfs-tools package in Ubuntu: Triaged Bug description: Because DHCPv6 only does addresses, and not routes, configure_networking needs to wait for the kernel to process a router- advertisement before returning claiming an IPv6 config (since all it will have is a /128 and no routes, making for a pretty useless network stack.) See Bug #1609898 for context. (The syntax for ip= should probably also be extended to allow SLAAC configuration. If the user said "dhcp", then we should insist on getting our answer from DHCP.) On the bright side, iscsi retries, so after 1 or more failures to connect, the router-advertisement comes in and the connect succeeds. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1632808/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1632808] Re: configure_networking exits without any ipv6 routes
Converting this to be the bug for ip6=stateless (or ip6=autoconf?), as the rest of it was solved with 1621507. ** Changed in: maas Status: New => Fix Released ** Summary changed: - configure_networking exits without any ipv6 routes + Consider supporting IPv6 autoconf in configure_networking ** Changed in: maas Status: Fix Released => Triaged -- 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/1632808 Title: Consider supporting IPv6 autoconf in configure_networking Status in MAAS: Triaged Status in initramfs-tools package in Ubuntu: Triaged Bug description: Because DHCPv6 only does addresses, and not routes, configure_networking needs to wait for the kernel to process a router- advertisement before returning claiming an IPv6 config (since all it will have is a /128 and no routes, making for a pretty useless network stack.) See Bug #1609898 for context. (The syntax for ip= should probably also be extended to allow SLAAC configuration. If the user said "dhcp", then we should insist on getting our answer from DHCP.) On the bright side, iscsi retries, so after 1 or more failures to connect, the router-advertisement comes in and the connect succeeds. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1632808/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1652292] Re: A typed "++" will be searched as "+" on all search engines
Thanks you for your fast fix! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1652292 Title: A typed "++" will be searched as "+" on all search engines Status in webbrowser-app package in Ubuntu: In Progress Bug description: I am on a vegetahd, rc proposed. DuckDuckGo is my default search engine. If I search "++" or any string like "C++ cout" the "++" is changed into only "+" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1652292/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1653324] Re: No wireless networks visible on resume from suspend. Erroneous Wired connection icon in nm-applet
Updating to latest didn't fix it. I suspended a few times and it failed approximately 20-30% of the time. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1653324 Title: No wireless networks visible on resume from suspend. Erroneous Wired connection icon in nm-applet Status in network-manager package in Ubuntu: Confirmed Bug description: As others have reported this I just woke my Thinkpad 450 to find no network. I resolved this by manually reconnecting with "nmcli c up id " where was taken from the output of "nmcli c" on the same machine. Steps to reproduce:- This is an intermittent issue which for me happens once in a while, but not super often to be annoying. For others it appears to happen often. I suspend my laptop multiple times daily and don't see this more than once per couple of weeks, or sometimes once a month. * Use laptop in one location on wifi * Suspend (shut lid) laptop * Resume (open lid) in same location (so same wifi networks nearby) Expected behaviour:- * Network come back up Actual behaviour:- * No network connectivity * nm-applet icon shows the two arrows as if a wired connection is made * No or few wireless erroneous wireless networks shown nearby * Workaround 1 (reconnect from command line) nmcli c (lists wireless networks, look for yours in the "NAME" column, use it in command below) nmcli c up id NAME * Workaround 2 (restart entire network stack) This AskUbuntu question has one solution http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend- after-16-04-upgrade#761220 Further information:- Output of nmcli m while suspending and resuming:- alan@gort:~$ nmcli m Connectivity is now 'none' Networkmanager is now in the 'asleep' state enp0s25: unmanaged wlp3s0: unmanaged Connectivity is now 'full' Networkmanager is now in the 'connected (local only)' state enp0s25: unavailable wlp3s0: unavailable wlp3s0: disconnected Output of nmcli after using workaround 1 above:- popey_2.4g_bed: connection profile changed Connectivity is now 'none' Networkmanager is now in the 'connecting' state wlp3s0: connecting (configuring) wlp3s0: using connection 'popey_2.4g_bed' wlp3s0: connecting (getting IP configuration) Connectivity is now 'full' 'popey_2.4g_bed' is now the primary connection Networkmanager is now in the 'connected' state wlp3s0: connected popey_2.4g_bed: connection profile changed Hardware info:- Thinkpad T450 alan@gort:~$ lspci | grep -i net 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (3) I218-LM (rev 03) 03:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59) alan@gort:~$ uptime 05:31:54 up 2 days, 18:03, 7 users, load average: 0.34, 0.94, 1.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CurrentDesktop: Unity Date: Sat Dec 31 05:38:47 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-27 (247 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev wlp3s0 proto static metric 600 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 10.235.160.0/24 dev lxdbr0 proto kernel scope link src 10.235.160.1 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.95 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1653324/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1566955] Re: transgui and lazarus not work after update to fontconfig 2.11.1-0ubuntu9
*** This bug is a duplicate of bug 1566624 *** https://bugs.launchpad.net/bugs/1566624 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: fontconfig (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1566955 Title: transgui and lazarus not work after update to fontconfig 2.11.1-0ubuntu9 Status in fontconfig package in Ubuntu: Confirmed Bug description: Transgui and lazarus not work after update from fontconfig_2.11.1-0ubuntu8_amd64.deb to 2.11.1-0ubuntu9 Versions which work as expected: <= 2.11.1-0ubuntu8 Broken versions: >= 2.11.1-0ubuntu9 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: fontconfig 2.11.1-0ubuntu9 ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6 Uname: Linux 4.4.0-17-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 6 10:53:04 2016 ProcEnviron: LANGUAGE=es_EC:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_EC.UTF-8 SHELL=/bin/bash SourcePackage: fontconfig UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1566955/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1654041] [NEW] pc stopped
Public bug reported: my linux ubuntu stopped. I needed to wait several minutes (I didn't turn off my pc) to start working. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Jan 4 18:23:06 2017 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G96M [GeForce 9700M GT] [10de:064a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. G96M [GeForce 9700M GT] [1043:19a2] InstallationDate: Installed on 2016-09-06 (120 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK Computer Inc. G71V ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic root=UUID=1794e97f-a724-4f55-b96f-7de8f8e07ec2 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G71V dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr207:bd09/22/2008:svnASUSTeKComputerInc.:pnG71V:pvr1.0:rvnASUSTeKComputerInc.:rnG71V:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: G71V dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Wed Jan 4 17:58:47 2017 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1 xserver.video_driver: nouveau ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 third-party-packages 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/1654041 Title: pc stopped Status in xorg package in Ubuntu: New Bug description: my linux ubuntu stopped. I needed to wait several minutes (I didn't turn off my pc) to start working. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Jan 4 18:23:06 2017 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G96M [GeForce 9700M GT] [10de:064a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. G96M [GeForce 9700M GT] [1043:19a2] InstallationDate: Installed on 2016-09-06 (120 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK Computer Inc. G71V ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic root=UUID=1794e97f-a724-4f55-b96f-7de8f8e07ec2 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G71V dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias:
[Touch-packages] [Bug 1646462] Re: lxc container download error (possibly HSTS related)
I see this today on a Zesty host when trying to create containers. I do not see this issue on a Xenial host however. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1646462 Title: lxc container download error (possibly HSTS related) Status in lxc package in Ubuntu: Confirmed Bug description: LXC cannot download image, seems like a server error: ~# lxc-create -t download -n test Setting up the GPG keyring Downloading the image index ERROR: Failed to download http://images.linuxcontainers.org//meta/1.0/index-user lxc-create: lxccontainer.c: create_run_template: 1290 container creation template for test failed lxc-create: tools/lxc_create.c: main: 318 Error creating container test Trying to download the file with wget gets the file OK with minor complaints: ~# wget -O /dev/null 'http://images.linuxcontainers.org//meta/1.0/index-user' URL transformed to HTTPS due to an HSTS policy --2016-12-01 12:36:58-- https://images.linuxcontainers.org//meta/1.0/index-user Resolving images.linuxcontainers.org (images.linuxcontainers.org)... 91.189.88.37, 91.189.91.21 Connecting to images.linuxcontainers.org (images.linuxcontainers.org)|91.189.88.37|:443... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: https://uk.images.linuxcontainers.org/meta/1.0/index-user [following] --2016-12-01 12:36:58-- https://uk.images.linuxcontainers.org/meta/1.0/index-user Resolving uk.images.linuxcontainers.org (uk.images.linuxcontainers.org)... 91.189.88.37 Connecting to uk.images.linuxcontainers.org (uk.images.linuxcontainers.org)|91.189.88.37|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 9102 (8.9K) Saving to: ‘/dev/null’ Seems like some SSL problem in the lxc-create binary, specifically the HSTS issue mentioned by wget. Maybe a newly introduced HSTS policy breaks the package? ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lxc 2.0.5-0ubuntu1.2 ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6 Uname: Linux 4.8.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Thu Dec 1 12:28:28 2016 InstallationDate: Installed on 2016-10-14 (47 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) dnsmasq.conf: dhcp-host=vold,10.0.3.10 dhcp-host=sftp,10.0.3.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1646462/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1646462] Re: lxc container download error (possibly HSTS related)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lxc (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1646462 Title: lxc container download error (possibly HSTS related) Status in lxc package in Ubuntu: Confirmed Bug description: LXC cannot download image, seems like a server error: ~# lxc-create -t download -n test Setting up the GPG keyring Downloading the image index ERROR: Failed to download http://images.linuxcontainers.org//meta/1.0/index-user lxc-create: lxccontainer.c: create_run_template: 1290 container creation template for test failed lxc-create: tools/lxc_create.c: main: 318 Error creating container test Trying to download the file with wget gets the file OK with minor complaints: ~# wget -O /dev/null 'http://images.linuxcontainers.org//meta/1.0/index-user' URL transformed to HTTPS due to an HSTS policy --2016-12-01 12:36:58-- https://images.linuxcontainers.org//meta/1.0/index-user Resolving images.linuxcontainers.org (images.linuxcontainers.org)... 91.189.88.37, 91.189.91.21 Connecting to images.linuxcontainers.org (images.linuxcontainers.org)|91.189.88.37|:443... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: https://uk.images.linuxcontainers.org/meta/1.0/index-user [following] --2016-12-01 12:36:58-- https://uk.images.linuxcontainers.org/meta/1.0/index-user Resolving uk.images.linuxcontainers.org (uk.images.linuxcontainers.org)... 91.189.88.37 Connecting to uk.images.linuxcontainers.org (uk.images.linuxcontainers.org)|91.189.88.37|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 9102 (8.9K) Saving to: ‘/dev/null’ Seems like some SSL problem in the lxc-create binary, specifically the HSTS issue mentioned by wget. Maybe a newly introduced HSTS policy breaks the package? ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lxc 2.0.5-0ubuntu1.2 ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6 Uname: Linux 4.8.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Thu Dec 1 12:28:28 2016 InstallationDate: Installed on 2016-10-14 (47 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) dnsmasq.conf: dhcp-host=vold,10.0.3.10 dhcp-host=sftp,10.0.3.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1646462/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1651433] Re: bluetooth mouse random disconnects
I have a Dell XPS DE, but I re-install on it a usual Ubuntu 16.04. I have the same problem and on /etc/bluetooth/main.conf there is "#AutoEnable=false" (default behavior is anyway AutoEnable=false). Even by changing it to "true" the problem is still there. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1651433 Title: bluetooth mouse random disconnects Status in bluez package in Ubuntu: Confirmed Bug description: I received the Dell XPS 13 DE (9350) accompanied by the WD15 docking station last September. Ever since I used it with my Logitech MX Master bluetooth mouse. This worked very well and reliably for September through November. But Since about start of December, it disconnects frequently and without any apparent reason. I can get it back to order by disabling and re-enabling the bluetooth radio of the notebook. After I re-enable the bt radio and move the mouse it work immediately without any delay. Sometimes it disconnects after 10 seconds. Sometimes I can work for 10 hours without any disconnect. For the entire lifetime the device has been running xenial. Currently I'm on kernel Linux XPS13ulr 4.4.0-53-generic #74-Ubuntu SMP Because the issue started happening at a certain date, I strongly believe that it was caused by and upgrade, possibly kernel. I wanted to see if the same disconnects also happen with other BT devices. But for as long as I had the Jabra Halo 2 headset connected, also the mouse worked reliably. The mouse is my only BT LE device. Maybe that makes a difference. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1651433/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1647016] Re: SRU of LXC 1.0.9 (upstream bugfix release)
Hello Stéphane, or anyone else affected, Accepted lxc into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lxc/1.0.9-0ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags removed: verification-failed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1647016 Title: SRU of LXC 1.0.9 (upstream bugfix release) Status in lxc package in Ubuntu: Invalid Status in lxc source package in Precise: In Progress Status in lxc source package in Trusty: Fix Committed Bug description: LXC upstream released LXC 1.0.9 as a bugfix release with following changelog: - Security fix for CVE-2016-8649 - utils: make detect_ramfs_rootfs() return bool - tests: add test for detect_ramfs_rootfs() - add Documentation entries to lxc and lxc@ units - mark the python examples as having utf-8 encoding - log: sanity check the returned value from snprintf() - lxc-alpine: mount /dev/shm as tmpfs - archlinux: Do DHCP on eth0 - archlinux: Fix resolving - Drop leftover references to lxc_strerror() - tests: fix image download for s390x - tools: fix coding style in lxc_attach - tools: make overlay valid backend - tools: better error reporting for lxc-start - alpine: Fix installing extra packages - lxc-alpine: do not drop setfcap - s390x: Fix seccomp handling of personalities - tools: correct the argument typo in lxc_copy - Use libtool for liblxc.so - c/r: use --external instead of --veth-pair - c/r: remember to increment netnr - c/r: add checkpoint/restore support for macvlan interfaces - ubuntu: Fix package upgrades requiring proc - c/r: drop duplicate hunk from macvlan case - c/r: use snprintf to compute device name - Tweak libtool handling to work with Android - tests: add lxc_error() and lxc_debug() - container start: clone newcgroup immediately - use python3_sitearch for including the python code - fix rpm build, include all built files, but only once - cgfs: fix invalid free() - find OpenSUSE's build also as obs-build - improve help text for --fancy and --fancy-format - improve wording of the help page for lxc-ls - cgfs: add print_cgfs_init_debuginfo() - cgfs: skip empty entries under /proc/self/cgroup - cgfs: explicitly check for NULL - tools: use correct exit code for lxc-stop - c/r: explicitly emit bind mounts as criu arguments - log: bump LXC_LOG_BUFFER_SIZE to 4096 - conf: merge network namespace move & rename on shutdown - c/r: save criu's stdout during dump too - c/r: remove extra \ns from logs - c/r: fix off-by-one error - c/r: check state before doing a checkpoint/restore - start: CLONE_NEWCGROUP after we have setup cgroups - create symlink for /var/run - utils: add lxc_append_string() - cgroups: remove isolated cpus from cpuset.cpus - Update Ubuntu release name: add zesty and remove wily - templates: add squashfs support to lxc-ubuntu-cloud.in - cgroups: skip v2 hierarchy entry - also stop lxc-net in runlevels 0 and 6 - add lxc.egg-info to gitignore - install bash completion where pkg-config tells us to - conf: do not use %m format specifier - debian: Don't depend on libui-dialog-perl - cgroups: use %zu format specifier to print size_t - lxc-checkpoint: automatically detect if --external or --veth-pair - cgroups: prevent segfault in cgfsng - utils: add lxc_preserve_ns() - start: add netnsfd to lxc_handler - conf: use lxc_preserve_ns() - attach: use lxc_preserve_ns() - lxc_user_nic: use lxc_preserve_ns() - conf, start: improve log output - conf: explicitly remove veth device from host - conf, start: be smarter when deleting networks - start, utils: improve preserve_ns() - start, error: improve log + non-functional changes - start, namespace: move ns_info to namespace.{c,h} - attach, utils: bugfixes - attach: use ns_info[LXC_NS_MAX] struct - namespace: always attach to user namespace first - cgroup: improve isolcpus handling -
[Touch-packages] [Bug 1510570] Re: BLE pairing fail
Finally both keyboard and mouse Microsoft Designer are working perfectly! - I used #25 (maybe #27 can work, I didn't try) - then #23 worked perfectly using this script: https://gist.github.com/Powiee/06129701f78f3c8a9cd23c197a35130f - I removed all BT devices using bluetoothctl (command line interface) and reboot - then I paired properly both mouse (1st) and keyboard (2nd) using #16 - both stopped working after a while (cursor not moving anymore), just switch off / on Bluetooth and TADAA: both auto-reconnect and now working without any problem! Thanks a lot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1510570 Title: BLE pairing fail Status in bluez package in Ubuntu: Confirmed Bug description: On 15.10 we now have bluez 5 so we can pair BLE devices like the Microsoft Arc Touch Bluetooth Mouse. But this pairing doesn't work very well. Mouse is seen but pairing fail. More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5 This is due to udev rule that use "hcitool" to power on device. Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used instead of udev rules. here is a commit with this parameter: http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138 And a ppa to test it: https://code.launchpad.net/~guilhem-fr/+archive/ubuntu/bluez-autoenable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1510570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1651818] Re: busybox-initramfs needs different compile options to work with cryptroot-unlock
As far as I understand this is about the debian/initramfs/cryptroot- unlock script, that is not used by default. (default unlocking is done via lightdm). Whilst indeed ps -eo pids,args is used, it doesn't have to be... if the sed regexp is modified, I think it can just use the "ps" output, no? ** Changed in: busybox (Ubuntu) Importance: Undecided => Low ** Changed in: cryptsetup (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1651818 Title: busybox-initramfs needs different compile options to work with cryptroot-unlock Status in busybox package in Ubuntu: Confirmed Status in cryptsetup package in Ubuntu: Confirmed Bug description: The cryptroot-unlock script in the cryptsetup package does not work in initramfs. It fails because "ps -e" is not available in busybox for initramfs. When building the package with CONFIG_DESKTOP=y CONFIG_EXTRA_COMPAT=y the needed commands (ps, grep) with parameter are there and it works. Tetsted on Ubuntu GNOME 16.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1651818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1450642] Re: seccomp missing many new syscalls
I'm setting the tag back to verification-needed then to prevent this from being released. ** Tags removed: verification-done ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1450642 Title: seccomp missing many new syscalls Status in Snappy: Fix Released Status in Snappy 15.04 series: Fix Released Status in libseccomp package in Ubuntu: Fix Released Status in libseccomp source package in Trusty: Fix Committed Status in libseccomp source package in Vivid: Fix Released Status in libseccomp source package in Wily: Fix Released Bug description: [Impact] Several syscalls were discovered to be missing when using the launcher on snappy. These should be added so we may properly support seccomp filtering. [Test Case] seccomp itself has a comprehensive testsuite, and while it doesn't fail the build, regressions can be seen by looking at the build log. Eg: Regression Test Summary tests run: 6494 tests skipped: 52 tests passed: 6494 tests failed: 0 tests errored: 0 Furthermore, on a snappy system, perform: # Note, for the 14.04 SRU, you'll have to install snapd from trusty-proposed $ sudo snappy install hello-world $ hello-world.env It should show the environment. On an arm system with 2.1.1-1 from the archive, this will fail due to a seccomp denial: audit: type=1326 audit(1430766107.122:16): auid=1000 uid=1000 gid=1000 ses=15 pid=1491 comm="env" exe="/bin/bash" sig=31 arch=4028 syscall=983045 compat=0 ip=0xb6fb0bd6 code=0x0 (note, snappy images have a ppa fix for this, see notes below). To test the segfault fix, do: $ scmp_sys_resolver 1024 Segmentation fault It should return: $ scmp_sys_resolver 1024 UNKNOWN For the new 3.19 syscalls: $ scmp_sys_resolver getrandom -1 it should return something like (actual number depends on arch, this is on armhf): $ scmp_sys_resolver getrandom 384 For the 14.04 SRU, test the following syscalls (expected results on amd64 are shown): $ scmp_sys_resolver getrandom 318 $ scmp_sys_resolver membarrier 324 $ scmp_sys_resolver userfaultfd 323 $ scmp_sys_resolver mlock2 325 autopkgtests for libseccomp have been added as part of this update to verify that the library recognizes all the syscalls from 3.19 and the private syscalls. These tests can be run like so (assuming you are in the unpacked source and the binaries are in ../binary): $ export REL=vivid $ adt-run `for i in ../binary/*.deb ; do echo -n "-B $i " ; done` --source ../source/*.dsc --log-file /tmp/adt.out --- adt-virt-schroot autopkgtest-$REL-amd64 || echo "** AUTOPKGTESTS FAILED" Alternatively, if you don't have autopkgtest setup, you can do: $ apt-get install dpkg-dev build-essential linux-libc-dev libseccomp-dev seccomp $ export ADTTMP=/tmp/foo ; mkdir -p "$ADTTMP" ; sh ./debian/tests/test-filter ... PASS $ export ADTTMP=/tmp/foo ; mkdir -p "$ADTTMP" ; sh ./debian/tests/test-scmp_sys_resolver ... PASS Lastly, seccomp is used by lxc. lxc can be tested by using the test case as outlined in step 4 of https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor#Desktop_only. [Regression Potential] If the above tests, regression potential is considered low. Unknown syscalls will continue to be handled as before. Description of changes: add finit_module: https://github.com/seccomp/libseccomp/commit/64152018ffdf971efefd84466db4a92002bb8b15 sync the syscall table entries - 3.16 https://github.com/seccomp/libseccomp/commit/9186136be7696ed63a8ddc06c9b397057abc5c75 https://github.com/seccomp/libseccomp/commit/3f319a9a5bc2e32f5a3c296fb0476c040b6f46c4 https://github.com/seccomp/libseccomp/commit/689f19e7488535c775c1db415b8d9895905ef8dd https://github.com/seccomp/libseccomp/commit/ac6802b300922ef2ad3e95e2c80f89b575073aeb https://github.com/seccomp/libseccomp/commit/c6205d9600983aa3fa68ca952b7624f2fec86718 https://github.com/seccomp/libseccomp/commit/76739812a3e23182504cde43403ddb9921e0e05a sync the syscall table entries - 3.17 https://github.com/seccomp/libseccomp/commit/6354f8cab5ac82a8d567005e58a9e7ff9dd843a9 sync the syscall table entries - 3.19 https://github.com/seccomp/libseccomp/commit/7b80fb2fb683cafaf5dc9ff7692437ba86e598a3 This should also be applied (fix a segfault for invalid syscall numbers): https://github.com/seccomp/libseccomp/commit/2d09a74c7f04d29ae740db1e2187ff1a1886b2c3 For the 14.04 SRU so that libseccomp can handle all of the syscalls in the 4.4 based linux-lts-xenial kernel: - membarrier and userfaultfd syscalls: https://github.com/seccomp/libseccomp/commit/d2ca11b7cdddbba3782b1e306ceacf19e898faee - x86 direct socket syscalls https://github.com/seccomp/libseccomp/commit/24114ca6703036f76be1920a7ba387d6835dd764 - mlock2 syscall
[Touch-packages] [Bug 1647333] Re: adduser misses extrausers support for group management
the added patch enables usermod to use the extrausers db for groups, we are still missing a similar patch for gpasswd which i'm now working on ** Patch added: "fix a typo ..." https://bugs.launchpad.net/snappy/+bug/1647333/+attachment/487/+files/usermod-extrausers-group.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to adduser in Ubuntu. https://bugs.launchpad.net/bugs/1647333 Title: adduser misses extrausers support for group management Status in Snappy: New Status in adduser package in Ubuntu: Confirmed Status in shadow package in Ubuntu: In Progress Bug description: trying to add a user to a group in /var/lib/extrausers by using the --extrausers option results in a "group not found" error despite adduser being supposed to be able to do this kind of modification. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1647333/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1620118] Re: [Inspiron 5559, Realtek ALC3234, Speaker, Internal] No sound at all
Did the sound reappeared after rebooting? When answered please set status back to "confirmed". Thank you. ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Incomplete -- 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/1620118 Title: [Inspiron 5559, Realtek ALC3234, Speaker, Internal] No sound at all Status in pulseaudio package in Ubuntu: Incomplete Bug description: I am new with ubuntu, I bought a new laptop it came with ubuntu 14.04 LTs installed on it and I decided to use it like that. Initially it was working correctly, but later I realized there is no sound when using any browser or playing video. So I upgraded to ubuntu 16.04 and the sound is working with firefox browser, but if I plug speaker it stop. Then I opened the sound setting and click output and there is mode of sound and I try to select so mode but then the tab disappeared and there is no sound at all. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 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: USERPID ACCESS COMMAND /dev/snd/controlC0: jhashim4153 F pulseaudio CurrentDesktop: Unity Date: Sun Sep 4 23:19:46 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150720-0 InstallationDate: Installed on 2016-02-11 (206 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06 SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jhashim4153 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [Inspiron 5559, Realtek ALC3234, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to xenial on 2016-09-04 (0 days ago) dmi.bios.date: 12/21/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.5 dmi.board.name: 05T1GT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn05T1GT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5559 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1620118/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1619844] Re: [Xenial] shutdown/reboot hangs at "Reached target Shutdown"
Does the following work-around work for you? (http://michalorman.com/2013/10/fix-ubuntu-freeze-during-restart) After answering, please set status back to "confirmed". Thank you. ** Changed in: systemd (Ubuntu) Importance: Undecided => Critical ** Changed in: systemd (Ubuntu) Status: Confirmed => Incomplete -- 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/1619844 Title: [Xenial] shutdown/reboot hangs at "Reached target Shutdown" Status in systemd package in Ubuntu: Incomplete Bug description: I tried getting more information in the debug-shell but I was unsuccessful in doing so. I was able to switch to the debug shell via ctrl+alt+f9 but I couldn't actually type anything in. I could switch back to the stuck shutdown screen via ctrl+alt+f1, and hitting NumLock would turn the light on my keyboard on and off, but I couldn't do anything else. I captured a journal of the stuck reboot. Interestingly, the journal shows a few more lines after "Reached target Shutdown", which is as far as I get on my screen. This system was installed with Xenial 16.04.1 (never been upgraded) and has had this problem since the very first boot. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu7 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 Date: Sat Sep 3 00:33:19 2016 InstallationDate: Installed on 2016-08-17 (16 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: SHELL=/bin/bash TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed root=UUID=5f709fed-48c9-4830-87be-acd13f263eb1 ro SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/mariadb.service → /etc/systemd/system/mariadb.service.d/migrated-from-my.cnf-settings.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: KYSKLi70.86A.0037.2016.0603.1032 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-404 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrKYSKLi70.86A.0037.2016.0603.1032:bd06/03/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-404:cvnIntelCorporation:ct3:cvr1.0: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1619844/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1627504] Re: [MS-7968, Realtek ALC1150, Black SPDIF Out, Rear] Underruns, dropouts or crackling sound. Test tones work but sound immediatly returns to poor quality after completi
** Changed in: alsa-driver (Ubuntu) Importance: Undecided => Medium -- 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/1627504 Title: [MS-7968, Realtek ALC1150, Black SPDIF Out, Rear] Underruns, dropouts or crackling sound. Test tones work but sound immediatly returns to poor quality after completion. Status in alsa-driver package in Ubuntu: Confirmed Bug description: Using digital audio output on Intel driver. Sound from games is barely decipherable over the distortion/crackle. Playing test tones (left/right test and on bug report) work fine but the noise returns when the clips are completed. Tried tsched=0, hda fix 1 and hda fix 2. no luck yet When first added tsched command, it blurs the screen and no audio devices are available. remove, restart, re-add and screen and audio back but problem still present (maybe just spelt wrong first time?). Help appreciated. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nytonial 1759 F pulseaudio /dev/snd/controlC0: nytonial 1759 F pulseaudio CurrentDesktop: Unity Date: Sun Sep 25 15:28:53 2016 InstallationDate: Installed on 2016-09-07 (17 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black SPDIF Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [MS-7968, Realtek ALC1150, Black SPDIF Out, Rear] Underruns, dropouts or crackling sound UpgradeStatus: Upgraded to xenial on 2016-09-08 (16 days ago) dmi.bios.date: 02/23/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.60 dmi.board.asset.tag: Default string dmi.board.name: Z170A XPOWER GAMING TITANIUM EDITION(MS-7968) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.60:bd02/23/2016:svnMSI:pnMS-7968:pvr3.0:rvnMSI:rnZ170AXPOWERGAMINGTITANIUMEDITION(MS-7968):rvr3.0:cvnMSI:ct3:cvr3.0: dmi.product.name: MS-7968 dmi.product.version: 3.0 dmi.sys.vendor: MSI modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-09-25T14:21:58.691691 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1627504/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1653529] Re: qtwebkit 5.7.1 fails to build on armhf
Continues to be a problem with forced use of gcc 6.2.1-5ubuntu1 and binutils 20161212 ubuntu version: https://launchpadlibrarian.net/301204319/buildlog_ubuntu-zesty-armhf .qtwebkit-opensource-src_5.7.1+dfsg-1build1~1_BUILDING.txt.gz The forcing was done with aid of version bumped older versions at https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/2332/+packages However with Debian variants of roughly those versions of gcc-6 and binutils a build of the identical qtwebkit source succeeded on December 16th: https://buildd.debian.org/status/fetch.php?pkg=qtwebkit- opensource-src=armhf=5.7.1%2Bdfsg-1=1481858819 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtwebkit-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1653529 Title: qtwebkit 5.7.1 fails to build on armhf Status in gcc-6 package in Ubuntu: Confirmed Status in qtwebkit-opensource-src package in Ubuntu: Confirmed Bug description: Build log: https://launchpadlibrarian.net/300952415/buildlog_ubuntu- zesty-armhf.qtwebkit-opensource-src_5.7.1+dfsg- 1build1~1_BUILDING.txt.gz --- g++ -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -Wl,--no-undefined -Wl,--no-undefined -fdebug-types-section -Wl,-O1 -Wl,--enable-new-dtags -Wl,--no-keep-memory -shared -Wl,-soname,libQt5WebKit.so.5 -o libQt5WebKit.so.5.7.1 -lQt5Gui -lQt5Core -lpthread -lQt5Network -lQt5Core -lpthread -lQt5Core -lpthread -lpthread -Wl,-whole-archive -lWebKit1 -Wl,-no-whole-archive -L/<>/qtwebkit-opensource-src-5.7.1+dfsg/Source/WebKit/ -Wl,-whole-archive -lWebKit2 -Wl,-no-whole-archive -L/<>/qtwebkit-opensource-src-5.7.1+dfsg/Source/WebKit2/ -lrt -Wl,-whole-archive -lWebCore -Wl,-no-whole-archive -L/<>/qtwebkit-opensource-src-5.7.1+dfsg/Source/WebCore/ -lz -lXrender -ljpeg -lpng -lwebp -Wl,-whole-archive -lANGLE -Wl,-no-whole-archive -L/<>/qtwebkit-opensource-src-5.7.1+dfsg/Source/ThirdParty/ANGLE/ -Wl,-whole-archive -lleveldb -Wl,-no-whole-archive -L/<>/qtwebkit-opensource-src-5.7.1+dfsg/Source/ThirdParty/leveldb/ -Wl,-whole-archive -lJa vaScriptCore -Wl,-no-whole-archive -L/<>/qtwebkit-opensource-src-5.7.1+dfsg/Source/JavaScriptCore/ -Wl,-whole-archive -lWTF -Wl,-no-whole-archive -L/<>/qtwebkit-opensource-src-5.7.1+dfsg/Source/WTF/ -lpthread -lEGL -lXext -lX11 -lm -lX11 -lxslt -lxml2 -lxml2 -lglib-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lgstreamer-1.0 -lgobject-2.0 -lglib-2.0 -lgstapp-1.0 -lgstbase-1.0 -lgstreamer-1.0 -lgobject-2.0 -lglib-2.0 -lgstbase-1.0 -lgstreamer-1.0 -lgobject-2.0 -lglib-2.0 -lgstpbutils-1.0 -lgstreamer-1.0 -lgobject-2.0 -lglib-2.0 -lgstreamer-1.0 -lgobject-2.0 -lglib-2.0 -lgstvideo-1.0 -lgstbase-1.0 -lgstreamer-1.0 -lgobject-2.0 -lglib-2.0 -lgstaudio-1.0 -lgstbase-1.0 -lgstreamer-1.0 -lgobject-2.0 -lglib-2.0 -lsqlite3 -licui18n -licuuc -licudata -lQt5Quick -lQt5Qml -lQt5Gui -lQt5Network -lQt5Core -lpthread -lQt5Qml -lQt5Network -lQt5Core -lpthread -lQt5Network -lQt5Core -lpthread -lQt5Gui -lQt5Core -lpthread -lQt5Sql -lQt5Core -lpthread -lQt5Core -lpthread -lGLESv2 /usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Gui.so:(*IND*+0x0): multiple definition of `__bss_start' /usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Gui.so:(*IND*+0x0): multiple definition of `_edata' /usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Gui.so:(*IND*+0x0): multiple definition of `_end' /usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Network.so:(*IND*+0x0): multiple definition of `_edata' /usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Network.so:(*IND*+0x0): multiple definition of `__bss_start' /usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Network.so:(*IND*+0x0): multiple definition of `_end' /usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Core.so:(*IND*+0x0): multiple definition of `__bss_start' /usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Core.so:(*IND*+0x0): multiple definition of `__bss_start' /usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Core.so:(*IND*+0x0): multiple definition of `_edata' /usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Core.so:(*IND*+0x0): multiple definition of `_edata' /usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Core.so:(*IND*+0x0): multiple definition of `_end' /usr/lib/gcc/arm-linux-gnueabihf/6/../../../arm-linux-gnueabihf/libQt5Core.so:(*IND*+0x0): multiple definition of `_end' collect2: error: ld returned 1 exit status --- This has built fine on Debian. https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-6/+bug/1653529/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1653725] Re: lxc-android-config not starting on ubuntu-touch/staging/* xenial-based images after lxc upgrade
** Changed in: lxc (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1653725 Title: lxc-android-config not starting on ubuntu-touch/staging/* xenial-based images after lxc upgrade Status in Canonical System Image: Confirmed Status in lxc package in Ubuntu: Fix Committed Status in lxc-android-config package in Ubuntu: New Bug description: As in topic. Since the 20161217 rootfs, after upgrade of lxc from 2.0.5-0ubuntu1~ubuntu16.04.3 to 2.0.6-0ubuntu1~ubuntu16.04.1 the lxc- android-config service does not start - making the devices unbootable. The syslog only states this: Jan 3 10:50:30 ubuntu-phablet systemd[1]: Starting LXC Android Config and Container Initialization... Jan 3 10:50:30 ubuntu-phablet kernel: [5.790810] (3)[1:systemd]SLEEP_EN = 0x1 Jan 3 10:50:30 ubuntu-phablet systemd[1]: Starting Light Display Manager... Jan 3 10:50:30 ubuntu-phablet systemd-udevd[672]: Could not generate persistent MAC address for ifb0: No such file or directory Jan 3 10:50:30 ubuntu-phablet systemd-udevd[684]: Could not generate persistent MAC address for ifb1: No such file or directory Jan 3 10:50:30 ubuntu-phablet lxc-start[1220]: You lack access to /var/lib/lxc Jan 3 10:50:30 ubuntu-phablet systemd[1]: lxc-android-config.service: Control process exited, code=exited status=1 Jan 3 10:50:30 ubuntu-phablet systemd[1]: Failed to start LXC Android Config and Container Initialization. Jan 3 10:50:30 ubuntu-phablet systemd[1]: Dependency failed for force-mtp.service. Jan 3 10:50:30 ubuntu-phablet systemd[1]: force-mtp.service: Job force-mtp.service/start failed with result 'dependency'. Jan 3 10:50:30 ubuntu-phablet systemd[1]: lxc-android-config.service: Unit entered failed state. Jan 3 10:50:30 ubuntu-phablet systemd[1]: lxc-android-config.service: Failed with result 'exit-code'. This makes all of our frieza and cooler devices useless for testing purposes. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1653725/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1611700] Re: package rsyslog 8.16.0-1ubuntu3 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
** Changed in: rsyslog (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1611700 Title: package rsyslog 8.16.0-1ubuntu3 failed to install/upgrade: le sous- processus script post-installation installé a retourné une erreur de sortie d'état 1 Status in rsyslog package in Ubuntu: Confirmed Bug description: I don't know this error of the system rsyslog ProblemType: Package DistroRelease: Ubuntu 16.04 Package: rsyslog 8.16.0-1ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 AptOrdering: rsyslog: Install rsyslog-mysql: Install rsyslog: Configure rsyslog-mysql: Configure NULL: ConfigurePending Architecture: i386 Date: Wed Aug 10 10:55:31 2016 ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 InstallationDate: Installed on 2016-08-09 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: rsyslog Title: package rsyslog 8.16.0-1ubuntu3 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1611700/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1617637] Re: wget crashing in libc if using screen output
** Changed in: wget (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wget in Ubuntu. https://bugs.launchpad.net/bugs/1617637 Title: wget crashing in libc if using screen output Status in wget package in Ubuntu: Confirmed Bug description: I got wget crashing repeatetly in libc if verbose or progress is enable. If use "-nv" flag it does not crash. This is dmesg: [44755.426609] wget[14324]: segfault at 564d49cc7000 ip 7f95b0686328 sp 7ffd8d1066c8 error 6 in libc-2.23.so[7f95b0514000+1c] [44760.175689] wget[14336]: segfault at 56409e4cd000 ip 7f12bb66e328 sp 7fff63a84d68 error 6 in libc-2.23.so[7f12bb4fc000+1c] [44827.776604] wget[16986]: segfault at 55b4cd4e5000 ip 7f7917462328 sp 7fff996f6a48 error 6 in libc-2.23.so[7f79172f+1c] [44831.555214] wget[17010]: segfault at 56549efa1000 ip 7f62d4acb328 sp 7ffc9f4039a8 error 6 in libc-2.23.so[7f62d4959000+1c] This is a strace of the command: write(2, "Berserk_.mp4 "..., 189Berserkmp4 2%[+> ] 9,72M 395KB/s ) = 189 select(4, [3], NULL, NULL, {0, 95}) = 1 (in [3], left {0, 949998}) read(3, "\214\22\366SA\276\312\344L\"\274:oD[\210\246\222,N\362w\253\310\\2A\360|\306\333;"..., 8192) = 8192 write(4, "\214\22\366SA\276\312\344L\"\274:oD[\210\246\222,N\362w\253\310\\2A\360|\306\333;"..., 4096) = 4096 write(4, "j\312\177l\367o\264\2220C\330\364\326Fc\375\200\303\213wa\356\237y,\236\212\315CI?\352"..., 4096) = 4096 select(4, [3], NULL, NULL, {0, 95}) = 1 (in [3], left {0, 94}) read(3, "\364\264\2640:6q\245v\265\367\230\204\30\302\236\265\335\267\242\322\\\240\364L\374\274\260\3307[\r"..., 8192) = 8192 write(4, "\364\264\2640:6q\245v\265\367\230\204\30\302\236\265\335\267\242\322\\\240\364L\374\274\260\3307[\r"..., 4096) = 4096 write(4, "Og\0233\354\324v\251\211\332\274\377\322\347\214HdD(\0028\227\337v\311\334\25s\206|\2143"..., 4096) = 4096 select(4, [3], NULL, NULL, {0, 95}) = 1 (in [3], left {0, 94}) read(3, "\2454\237\236\372;\357\270\276\212Kkd\2\302\272\343x\344Y*\201q\35\"\255h\225\203\17]\240"..., 8192) = 8192 write(4, "\2454\237\236\372;\357\270\276\212Kkd\2\302\272\343x\344Y*\201q\35\"\255h\225\203\17]\240"..., 4096) = 4096 write(4, "\316\263\213y\342\306\253\251x&\355\377m\367}\215\217Y\363\356\330}!]\326\326R\334\25!\306\236"..., 4096) = 4096 select(4, [3], NULL, NULL, {0, 95}) = 1 (in [3], left {0, 94}) read(3, "\302h\211\244\325\32\275\326'D6E\325Y/f\200w\n\25\277n]\26\362\16~b\265.\222\322"..., 8192) = 8192 write(4, "\302h\211\244\325\32\275\326'D6E\325Y/f\200w\n\25\277n]\26\362\16~b\265.\222\322"..., 4096) = 4096 write(4, "\327t\20\275}j\377(\201\336GF\372!i\31\3604o\377\\\273\361\347\277\326\376\3425~\313O"..., 4096) = 4096 select(4, [3], NULL, NULL, {0, 95}) = 1 (in [3], left {0, 94}) read(3, "\371+*\22663e0ip\30\0017w;\376\372\243\312\235\222\212Oj\225\267\315\352t\27\372\266"..., 8192) = 8192 write(4, "\371+*\22663e0ip\30\0017w;\376\372\243\312\235\222\212Oj\225\267\315\352t\27\372\266"..., 4096) = 4096 write(4, "[3\276(\205\244\3144\236\216\\\220\215\267\"Q\22\262\261P\364\332\204\344n1\fP\320\235\16s"..., 4096) = 4096 select(4, [3], NULL, NULL, {0, 95}) = 1 (in [3], left {0, 94}) read(3, "\377\371\257\274\257\244\266/C$\257\341EpU\352\3410\325F\265r\221\271\331\227w\344\v\376\34\5"..., 8192) = 8192 write(4, "\377\371\257\274\257\244\266/C$\257\341EpU\352\3410\325F\265r\221\271\331\227w\344\v\376\34\5"..., 4096) = 4096 write(4, "\23P\272\345\211E\324Jo\367T*\v\366D\362\211~\10u\34\253\10Gh\265&\206\20\321{\f"..., 4096) = 4096 select(4, [3], NULL, NULL, {0, 95}) = 1 (in [3], left {0, 94}) read(3, "(\315\265\366\307\224\32\30\245v\376\256\204\210d\311\250\315,|8\227#o\317\234\5L\21Zr\224"..., 8192) = 8192 write(4, "(\315\265\366\307\224\32\30\245v\376\256\204\210d\311\250\315,|8\227#o\317\234\5L\21Zr\224"..., 4096) = 4096 write(4, "\373\206\30\205\3\177Z\270\f\3rI\236s\244\340\377\3259\204\300\274\220W\330\7E\231\nU\301\257"..., 4096) = 4096 select(4, [3], NULL, NULL, {0, 95}) = 1 (in [3], left {0, 94}) read(3, "_\3117_?M\362ae\263\267\177HtS\206\24\260\364\341\374\217\213\351I\342\345q\372\r\36\350"..., 8192) = 8192 write(4, "_\3117_?M\362ae\263\267\177HtS\206\24\260\364\341\374\217\213\351I\342\345q\372\r\36\350"..., 4096) = 4096 write(4, "\27&\311\263\362\f\33AgYC\224R\224l\245!1\251\353\366'#jd\35tA\202T4\301"..., 4096) = 4096 select(4, [3], NULL, NULL, {0, 95}) = 1 (in [3], left {0, 94}) read(3, "\262\351A\237\267f\377\365N\335\326rm\360\277\313D\364gC\2001\10\216\0\0\2c\1\237-D"..., 8192) = 8192 write(4,
[Touch-packages] [Bug 1616695] Re: Bluetooth signal is unusably poor
** Changed in: bluez (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1616695 Title: Bluetooth signal is unusably poor Status in bluez package in Ubuntu: Confirmed Bug description: Brand new Macbook Pro 12,1. Brand new Ubuntu 16.04 install (from scratch). In MacOS the machine can connect to my bluetooth speaker from across the room and play A2DP no trouble at all. In Ubuntu 16.04 I have to literally hold up the macbook 1 inch away from the speaker to get it to connect and play, and even then it's a bit choppy. Turning off Wifi seems to help a bit, which leads me to think this is some kind of transmit power issue. Syslog is chock full of warnings about skipping audio: Aug 24 16:22:32 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 206099 us (= 36352 bytes) in audio stream Aug 24 16:22:32 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 382089 us (= 67400 bytes) in audio stream Aug 24 16:22:33 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 394108 us (= 69520 bytes) in audio stream Aug 24 16:22:33 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 328125 us (= 57880 bytes) in audio stream Aug 24 16:22:33 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 59087 us (= 10420 bytes) in audio stream Aug 24 16:22:33 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 14036 us (= 2472 bytes) in audio stream Aug 24 16:22:34 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 247134 us (= 43592 bytes) in audio stream Aug 24 16:22:34 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 342190 us (= 60360 bytes) in audio stream Aug 24 16:22:34 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 172035 us (= 30344 bytes) in audio stream Aug 24 16:22:35 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 803140 us (= 141672 bytes) in audio stream Aug 24 16:22:36 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 651085 us (= 114848 bytes) in audio stream Aug 24 16:22:36 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 202043 us (= 35640 bytes) in audio stream Aug 24 16:22:36 badassm pulseaudio[4655]: [bluetooth] module-bluez5-device.c: Skipping 265112 us (= 46764 bytes) in audio stream $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04.1 LTS" $ uname -a Linux badassm 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux $ lsusb Bus 002 Device 002: ID 05ac:8406 Apple, Inc. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05ac:0273 Apple, Inc. Bus 001 Device 003: ID 05ac:8290 Apple, Inc. Bus 001 Device 006: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0 Bus 001 Device 005: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub $ hciconfig hci0: Type: BR/EDR Bus: USB BD Address: 98:01:A7:A8:D4:6A ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:5198 acl:2 sco:0 events:269 errors:0 TX bytes:7021 acl:2 sco:0 commands:218 errors:0 [bluetooth]# show Controller 98:01:A7:A8:D4:6A Name: badassm Alias: badassm Class: 0x1c010c Powered: yes Discoverable: no Pairable: yes UUID: Headset AG(1112--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: IrMC Sync (1104--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: Vendor specific (5005--1000-8000-0002ee01) UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb) UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb) UUID: Message Access Server (1132--1000-8000-00805f9b34fb) Modalias:
[Touch-packages] [Bug 1600592] Re: package whoopsie 0.2.52.1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1
** Changed in: whoopsie (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1600592 Title: package whoopsie 0.2.52.1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1 Status in whoopsie package in Ubuntu: Confirmed Bug description: insserv: exiting now without changing boot order! update-rc.d: error: insserv rejected the script header dpkg: erro ao processar o pacote whoopsie (--configure): sub-processo script post-installation instalado retornou estado de saída de erro 1 Configurando lsb-release (9.20160110ubuntu0.2) ... Configurando snapd (2.0.10) ... Erros foram encontrados durante o processamento de: whoopsie E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: whoopsie 0.2.52.1 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 AptOrdering: libnss3-tools: Install whoopsie: Configure libnss3-tools: Configure NULL: ConfigurePending Architecture: amd64 Date: Sat Jul 9 13:58:01 2016 ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 1 InstallationDate: Installed on 2016-04-24 (76 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: apport-noui N/A SourcePackage: whoopsie Title: package whoopsie 0.2.52.1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1600592/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389775] Re: [CTA] Apps shown in permission list even when they have been uninstalled
this is also in security & privacy > program rights? > location programs don't seem to be cleaned very well after installation -- 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/1389775 Title: [CTA] Apps shown in permission list even when they have been uninstalled Status in Canonical System Image: In Progress Status in webapps-sprint: In Progress Status in click package in Ubuntu: In Progress Status in trust-store package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: If you uninstall an app that has used the location service, or any other permission, it still appears in the model but without a title or icon. Per UX design and to meet certification requirements we will remove the entry from the trust store when the app is uninstalled. These entries also occur when a framework becomes unsupported, any app requiring the deprecated framework becomes unregistered. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1389775/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1599357] Re: WARN_ON(!encoder->crtc), more warnings and unstable X on 16.04
** Changed in: xorg (Ubuntu) Importance: Undecided => High -- 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/1599357 Title: WARN_ON(!encoder->crtc), more warnings and unstable X on 16.04 Status in xorg package in Ubuntu: Confirmed Bug description: Hello, I installed ubuntu 16.04 on the vintage asus eeepc 701. However, i915 is giving me warnings on dmesg and it is unstable, specially on vt-switch (I cannot go back to X). I'll attach what dmesg shows me. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 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: Wed Jul 6 00:52:20 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Mobile 915GM/GMS/910GML Express Graphics Controller [1043:82d9] Subsystem: ASUSTeK Computer Inc. Mobile 915GM/GMS/910GML Express Graphics Controller [1043:82d9] MachineType: ASUSTeK Computer INC. 701 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-28-generic root=UUID=88e47f5f-2717-42af-a83c-05a041cf9895 ro rootflags=subvol=@ quiet splash forcepae vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0910 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 701 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0910:bd03/03/2008:svnASUSTeKComputerINC.:pn701:pvrx.x:rvnASUSTeKComputerINC.:rn701:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x: dmi.product.name: 701 dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Jul 6 00:20:43 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1599357/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1647333] Re: adduser misses extrausers support for group management
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to adduser in Ubuntu. https://bugs.launchpad.net/bugs/1647333 Title: adduser misses extrausers support for group management Status in Snappy: New Status in adduser package in Ubuntu: Confirmed Status in shadow package in Ubuntu: In Progress Bug description: trying to add a user to a group in /var/lib/extrausers by using the --extrausers option results in a "group not found" error despite adduser being supposed to be able to do this kind of modification. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1647333/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1576390] Re: [HP Compaq 6735s, Analog Devices AD1984A, Speaker, Internal] No sound at all
** Changed in: pulseaudio (Ubuntu) Importance: Undecided => High -- 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/1576390 Title: [HP Compaq 6735s, Analog Devices AD1984A, Speaker, Internal] No sound at all Status in pulseaudio package in Ubuntu: Confirmed Bug description: Tested sound with Flash or HTML5. Result no sound. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rostandii 2478 F pulseaudio CurrentDesktop: Unity Date: Thu Apr 28 21:45:25 2016 InstallationDate: Installed on 2015-09-05 (236 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB successful Symptom_Card: Built-in Audio - HDA ATI SB Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rostandii 2478 F pulseaudio Symptom_Jack: Green Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [HP Compaq 6735s, Analog Devices AD1984A, Green Speaker, Internal] No sound at all UpgradeStatus: Upgraded to xenial on 2016-04-24 (3 days ago) dmi.bios.date: 10/02/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68GPP Ver. F.06 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 30E4 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 94.1C dmi.chassis.asset.tag: CNU842079D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68GPPVer.F.06:bd10/02/2008:svnHewlett-Packard:pnHPCompaq6735s:pvrF.06:rvnHewlett-Packard:rn30E4:rvrKBCVersion94.1C:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq 6735s dmi.product.version: F.06 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1576390/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1502173] Re: Python warnings: modules imported without specifying a version first
** Description changed: [Description] - Users receive warnings about importing of python modules with a version being specified. While this isn't a big deal in itself we get lots of bug reports from people about this issue since it is so obvious. Given that Ubuntu 16.04 is an LTS release we should fix this and prevent further reporting of the issue. + Users receive warnings about importing of python modules without a version being specified. While this isn't a big deal in itself we get lots of bug reports from people about this issue since it is so obvious. Given that Ubuntu 16.04 is an LTS release we should fix this and prevent further reporting of the issue. [Test Case] 1) run /usr/share/apport/apport-gtk in a terminal 2) Observe the following /usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without specifying a version first. Use gi.require_version('Wnck', '3.0') before import to ensure that the right version gets loaded. from gi.repository import GLib, Wnck, GdkX11, Gdk /usr/share/apport/apport-gtk:16: PyGIWarning: GdkX11 was imported without specifying a version first. Use gi.require_version('GdkX11', '3.0') before import to ensure that the right version gets loaded. from gi.repository import GLib, Wnck, GdkX11, Gdk with the version of apport in -proposed you'll no longer receive the warning. - [Regression Potential] - As with any SRU this could cause a regression in the software if the fix is typo'ed so review it carefully. If there isn't a typo and then the chance of a regression is very very very low. + [Regression Potential]As with any SRU this could cause a regression in + the software if the fix is typo'ed so review it carefully. If there + isn't a typo and then the chance of a regression is very very very low. Original Description Hi, here is the problem: $ /usr/share/apport/apport-gtk /usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without specifying a version first. Use gi.require_version('Wnck', '3.0') before import to ensure that the right version gets loaded. from gi.repository import GLib, Wnck, GdkX11, Gdk /usr/share/apport/apport-gtk:16: PyGIWarning: GdkX11 was imported without specifying a version first. Use gi.require_version('GdkX11', '3.0') before import to ensure that the right version gets loaded. from gi.repository import GLib, Wnck, GdkX11, Gdk ProblemType: BugDistroRelease: Ubuntu 15.10 Package: apport-gtk 2.19-0ubuntu1 Uname: Linux 4.2.2-040202-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Fri Oct 2 16:17:14 2015 EcryptfsInUse: Yes PackageArchitecture: allSourcePackage: apport UpgradeStatus: Upgraded to wily on 2015-10-02 (0 days ago) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1502173 Title: Python warnings: modules imported without specifying a version first Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: In Progress Bug description: [Description] Users receive warnings about importing of python modules without a version being specified. While this isn't a big deal in itself we get lots of bug reports from people about this issue since it is so obvious. Given that Ubuntu 16.04 is an LTS release we should fix this and prevent further reporting of the issue. [Test Case] 1) run /usr/share/apport/apport-gtk in a terminal 2) Observe the following /usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without specifying a version first. Use gi.require_version('Wnck', '3.0') before import to ensure that the right version gets loaded. from gi.repository import GLib, Wnck, GdkX11, Gdk /usr/share/apport/apport-gtk:16: PyGIWarning: GdkX11 was imported without specifying a version first. Use gi.require_version('GdkX11', '3.0') before import to ensure that the right version gets loaded. from gi.repository import GLib, Wnck, GdkX11, Gdk with the version of apport in -proposed you'll no longer receive the warning. [Regression Potential]As with any SRU this could cause a regression in the software if the fix is typo'ed so review it carefully. If there isn't a typo and then the chance of a regression is very very very low. Original Description Hi, here is the problem: $ /usr/share/apport/apport-gtk /usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without specifying a version first. Use gi.require_version('Wnck', '3.0') before import to ensure that the right version gets loaded. from gi.repository import GLib, Wnck, GdkX11, Gdk /usr/share/apport/apport-gtk:16: PyGIWarning: GdkX11 was imported without specifying a version first. Use gi.require_version('GdkX11', '3.0') before import to
[Touch-packages] [Bug 1583227] Re: Rotated screen doesn't have rotated touch gestures
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: xorg (Ubuntu) Status: Confirmed => Invalid ** Also affects: linux via http://bugzilla.kernel.org/show_bug.cgi?id=120011 Importance: Unknown Status: Unknown ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: xorg (Ubuntu) Importance: Undecided => Medium -- 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/1583227 Title: Rotated screen doesn't have rotated touch gestures Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Invalid Bug description: When I rotate the screen on this Lenovo X230T using the button on the LCD, the touch input gestures do not rotate as well. For example, if I rotate 90 degrees a horizontal two finger drag does a vertical scroll. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 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: Wed May 18 08:32:16 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-22-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203] InstallationDate: Installed on 2016-05-09 (8 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 343522U ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=731d521d-ab9f-4b31-9434-cb6b859fe8d1 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Intel Graphics" Driver "intel" Option "TearFree" "true" EndSection dmi.bios.date: 05/28/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GCET99WW (2.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 343522U dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 343522U dmi.product.version: ThinkPad X230 Tablet dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed May 18 08:17:52 2016 xserver.configfile: /etc/X11/xorg.conf xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 728 vendor LGD xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1583227/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1653324] Re: No wireless networks visible on resume from suspend. Erroneous Wired connection icon in nm-applet
I installed dbus and friends from xenial-proposed and haven't seen the issue yet, but it happens rarely. Will keep an eye on it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1653324 Title: No wireless networks visible on resume from suspend. Erroneous Wired connection icon in nm-applet Status in network-manager package in Ubuntu: Confirmed Bug description: As others have reported this I just woke my Thinkpad 450 to find no network. I resolved this by manually reconnecting with "nmcli c up id " where was taken from the output of "nmcli c" on the same machine. Steps to reproduce:- This is an intermittent issue which for me happens once in a while, but not super often to be annoying. For others it appears to happen often. I suspend my laptop multiple times daily and don't see this more than once per couple of weeks, or sometimes once a month. * Use laptop in one location on wifi * Suspend (shut lid) laptop * Resume (open lid) in same location (so same wifi networks nearby) Expected behaviour:- * Network come back up Actual behaviour:- * No network connectivity * nm-applet icon shows the two arrows as if a wired connection is made * No or few wireless erroneous wireless networks shown nearby * Workaround 1 (reconnect from command line) nmcli c (lists wireless networks, look for yours in the "NAME" column, use it in command below) nmcli c up id NAME * Workaround 2 (restart entire network stack) This AskUbuntu question has one solution http://askubuntu.com/questions/761180/wifi-doesnt-work-after-suspend- after-16-04-upgrade#761220 Further information:- Output of nmcli m while suspending and resuming:- alan@gort:~$ nmcli m Connectivity is now 'none' Networkmanager is now in the 'asleep' state enp0s25: unmanaged wlp3s0: unmanaged Connectivity is now 'full' Networkmanager is now in the 'connected (local only)' state enp0s25: unavailable wlp3s0: unavailable wlp3s0: disconnected Output of nmcli after using workaround 1 above:- popey_2.4g_bed: connection profile changed Connectivity is now 'none' Networkmanager is now in the 'connecting' state wlp3s0: connecting (configuring) wlp3s0: using connection 'popey_2.4g_bed' wlp3s0: connecting (getting IP configuration) Connectivity is now 'full' 'popey_2.4g_bed' is now the primary connection Networkmanager is now in the 'connected' state wlp3s0: connected popey_2.4g_bed: connection profile changed Hardware info:- Thinkpad T450 alan@gort:~$ lspci | grep -i net 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection (3) I218-LM (rev 03) 03:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59) alan@gort:~$ uptime 05:31:54 up 2 days, 18:03, 7 users, load average: 0.34, 0.94, 1.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CurrentDesktop: Unity Date: Sat Dec 31 05:38:47 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-27 (247 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev wlp3s0 proto static metric 600 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 10.235.160.0/24 dev lxdbr0 proto kernel scope link src 10.235.160.1 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.95 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1653324/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1638388] Re: NetworkManager wont start at system boot
** Changed in: network-manager (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1638388 Title: NetworkManager wont start at system boot Status in network-manager package in Ubuntu: Confirmed Bug description: From time to time NetworkManager does not start at system boot. NetworkManager seems to be started, but being terminated immediately. Symptoms: * no network connection at system boot. * no network connection while logging in. * no network applet after logging in. NetworkManager isn't running after logging in. I have to execute "service NetworkManager restart". Problem: * since NetworkManager not running at system boot it is not possible to connect the system via ssh! You will need a console. Bad with headless servers: you are locked out of them after rebooting. Workaround: write a script trying to start NetworkManager every minute after reboot until it is running. Works so far, but it is a really bad hack! Seen this problem on systems migrated from Ubuntu 14.04.5 LTS to 16.04.1 LTS. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 Uname: Linux 4.8.6+ x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 1 22:13:15 2016 InstallationDate: Installed on 2011-10-19 (1840 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) IpRoute: default via 192.168.6.1 dev enp4s0 proto static metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 172.19.1.0/24 dev vmnet1 proto kernel scope link src 172.19.1.1 172.19.8.0/24 dev vmnet8 proto kernel scope link src 172.19.8.1 192.168.6.0/24 dev enp4s0 proto kernel scope link src 192.168.6.46 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to xenial on 2016-09-08 (54 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-03-03T12:29:43.912070 mtime.conffile..etc.init.network-manager.conf: 2013-03-04T17:15:37.443693 nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH muc-ews e0d03730-1e06-4998-b508-157a5a2a2ad0 802-3-ethernet 1478034710 Die 01 Nov 2016 22:11:50 CET yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated /org/freedesktop/NetworkManager/ActiveConnection/0 CVJM 0eaf8330-35e8-4eae-a922-16f0547f5c87 802-11-wireless 0 never yes 0 no /org/freedesktop/NetworkManager/Settings/0 no -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638388/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1573586] Re: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2
** Changed in: libjpeg8-empty (Ubuntu) Importance: Undecided => High ** Also affects: hundredpapercuts Importance: Undecided Status: New ** Changed in: hundredpapercuts Status: New => Confirmed ** Changed in: hundredpapercuts Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg8-empty in Ubuntu. https://bugs.launchpad.net/bugs/1573586 Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo- progs 1.3.0-0ubuntu2 Status in One Hundred Papercuts: Confirmed Status in libjpeg8-empty package in Ubuntu: Confirmed Bug description: The GUI upgrade crashed because of LP: #1573558. I resumed with apt-get install -f apt-get dist-upgrade and got this error in the middle of the dist-upgrade. It's probably a duplicate of LP: #1571195. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libjpeg-progs 8c-2ubuntu8 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Fri Apr 22 15:36:57 2016 ErrorMessage: trying to overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 InstallationDate: Installed on 2012-07-25 (1366 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: libjpeg8-empty Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: trying to overwrite '/usr/bin/rdjpgcom', which is also in package libjpeg-turbo-progs 1.3.0-0ubuntu2 UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1573586/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1573704] Re: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: podproces instalovaný post-installation skript vrátil chybový status 1
** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => High -- 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/1573704 Title: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: podproces instalovaný post-installation skript vrátil chybový status 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: during install of the nvidia-364 video driver ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Fri Apr 22 18:52:09 2016 ErrorMessage: podproces instalovaný post-installation skript vrátil chybový status 1 InstallationDate: Installed on 2016-04-22 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: podproces instalovaný post-installation skript vrátil chybový status 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/1573704/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1653725] Re: lxc-android-config not starting on ubuntu-touch/staging/* xenial-based images after lxc upgrade
** Changed in: lxc (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 in Ubuntu. https://bugs.launchpad.net/bugs/1653725 Title: lxc-android-config not starting on ubuntu-touch/staging/* xenial-based images after lxc upgrade Status in Canonical System Image: Confirmed Status in lxc package in Ubuntu: In Progress Status in lxc-android-config package in Ubuntu: New Bug description: As in topic. Since the 20161217 rootfs, after upgrade of lxc from 2.0.5-0ubuntu1~ubuntu16.04.3 to 2.0.6-0ubuntu1~ubuntu16.04.1 the lxc- android-config service does not start - making the devices unbootable. The syslog only states this: Jan 3 10:50:30 ubuntu-phablet systemd[1]: Starting LXC Android Config and Container Initialization... Jan 3 10:50:30 ubuntu-phablet kernel: [5.790810] (3)[1:systemd]SLEEP_EN = 0x1 Jan 3 10:50:30 ubuntu-phablet systemd[1]: Starting Light Display Manager... Jan 3 10:50:30 ubuntu-phablet systemd-udevd[672]: Could not generate persistent MAC address for ifb0: No such file or directory Jan 3 10:50:30 ubuntu-phablet systemd-udevd[684]: Could not generate persistent MAC address for ifb1: No such file or directory Jan 3 10:50:30 ubuntu-phablet lxc-start[1220]: You lack access to /var/lib/lxc Jan 3 10:50:30 ubuntu-phablet systemd[1]: lxc-android-config.service: Control process exited, code=exited status=1 Jan 3 10:50:30 ubuntu-phablet systemd[1]: Failed to start LXC Android Config and Container Initialization. Jan 3 10:50:30 ubuntu-phablet systemd[1]: Dependency failed for force-mtp.service. Jan 3 10:50:30 ubuntu-phablet systemd[1]: force-mtp.service: Job force-mtp.service/start failed with result 'dependency'. Jan 3 10:50:30 ubuntu-phablet systemd[1]: lxc-android-config.service: Unit entered failed state. Jan 3 10:50:30 ubuntu-phablet systemd[1]: lxc-android-config.service: Failed with result 'exit-code'. This makes all of our frieza and cooler devices useless for testing purposes. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1653725/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1653999] Re: package tzdata 2016j-0ubuntu0.14.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 29
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1653999 Title: package tzdata 2016j-0ubuntu0.14.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 29 Status in tzdata package in Ubuntu: New Bug description: Attempted to do routine acceptance of software updater suggestions in 14.04.5 LTS running in a VM. Got an error that updates failed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: tzdata 2016j-0ubuntu0.14.04 ProcVersionSignature: Ubuntu 3.13.0-93.140-generic 3.13.11-ckt39 Uname: Linux 3.13.0-93-generic x86_64 NonfreeKernelModules: rapidrecovery_vss ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Wed Jan 4 10:20:26 2017 DuplicateSignature: package:tzdata:2016j-0ubuntu0.14.04:subprocess installed post-installation script returned error exit status 29 ErrorMessage: subprocess installed post-installation script returned error exit status 29 InstallationDate: Installed on 2013-05-07 (1338 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.14 SourcePackage: tzdata Title: package tzdata 2016j-0ubuntu0.14.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 29 UpgradeStatus: Upgraded to trusty on 2014-09-24 (833 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1653999/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1653999] [NEW] package tzdata 2016j-0ubuntu0.14.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 29
Public bug reported: Attempted to do routine acceptance of software updater suggestions in 14.04.5 LTS running in a VM. Got an error that updates failed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: tzdata 2016j-0ubuntu0.14.04 ProcVersionSignature: Ubuntu 3.13.0-93.140-generic 3.13.11-ckt39 Uname: Linux 3.13.0-93-generic x86_64 NonfreeKernelModules: rapidrecovery_vss ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Wed Jan 4 10:20:26 2017 DuplicateSignature: package:tzdata:2016j-0ubuntu0.14.04:subprocess installed post-installation script returned error exit status 29 ErrorMessage: subprocess installed post-installation script returned error exit status 29 InstallationDate: Installed on 2013-05-07 (1338 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.14 SourcePackage: tzdata Title: package tzdata 2016j-0ubuntu0.14.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 29 UpgradeStatus: Upgraded to trusty on 2014-09-24 (833 days ago) ** Affects: tzdata (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1653999 Title: package tzdata 2016j-0ubuntu0.14.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 29 Status in tzdata package in Ubuntu: New Bug description: Attempted to do routine acceptance of software updater suggestions in 14.04.5 LTS running in a VM. Got an error that updates failed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: tzdata 2016j-0ubuntu0.14.04 ProcVersionSignature: Ubuntu 3.13.0-93.140-generic 3.13.11-ckt39 Uname: Linux 3.13.0-93-generic x86_64 NonfreeKernelModules: rapidrecovery_vss ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Wed Jan 4 10:20:26 2017 DuplicateSignature: package:tzdata:2016j-0ubuntu0.14.04:subprocess installed post-installation script returned error exit status 29 ErrorMessage: subprocess installed post-installation script returned error exit status 29 InstallationDate: Installed on 2013-05-07 (1338 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.14 SourcePackage: tzdata Title: package tzdata 2016j-0ubuntu0.14.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 29 UpgradeStatus: Upgraded to trusty on 2014-09-24 (833 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1653999/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1611700] Re: package rsyslog 8.16.0-1ubuntu3 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: rsyslog (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1611700 Title: package rsyslog 8.16.0-1ubuntu3 failed to install/upgrade: le sous- processus script post-installation installé a retourné une erreur de sortie d'état 1 Status in rsyslog package in Ubuntu: Confirmed Bug description: I don't know this error of the system rsyslog ProblemType: Package DistroRelease: Ubuntu 16.04 Package: rsyslog 8.16.0-1ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 AptOrdering: rsyslog: Install rsyslog-mysql: Install rsyslog: Configure rsyslog-mysql: Configure NULL: ConfigurePending Architecture: i386 Date: Wed Aug 10 10:55:31 2016 ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 InstallationDate: Installed on 2016-08-09 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: rsyslog Title: package rsyslog 8.16.0-1ubuntu3 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1611700/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1653725] Re: lxc-android-config not starting on ubuntu-touch/staging/* xenial-based images after lxc upgrade
Thanks. I think the problem is a newly introduced check for path writeability which is harmless and in fact, potentially useful in just about all cases but the weird Ubuntu Phone case where / is read-only, confusing that check. @Christian: Can you look into fixing this? I suspect we only really care about being able to access the path, not so much about being able to write to it. So it may make sense to change the check in all our tools to simply check for read rights. ** Changed in: lxc (Ubuntu) Assignee: (unassigned) => Christian Brauner (cbrauner) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1653725 Title: lxc-android-config not starting on ubuntu-touch/staging/* xenial-based images after lxc upgrade Status in Canonical System Image: Confirmed Status in lxc package in Ubuntu: New Status in lxc-android-config package in Ubuntu: New Bug description: As in topic. Since the 20161217 rootfs, after upgrade of lxc from 2.0.5-0ubuntu1~ubuntu16.04.3 to 2.0.6-0ubuntu1~ubuntu16.04.1 the lxc- android-config service does not start - making the devices unbootable. The syslog only states this: Jan 3 10:50:30 ubuntu-phablet systemd[1]: Starting LXC Android Config and Container Initialization... Jan 3 10:50:30 ubuntu-phablet kernel: [5.790810] (3)[1:systemd]SLEEP_EN = 0x1 Jan 3 10:50:30 ubuntu-phablet systemd[1]: Starting Light Display Manager... Jan 3 10:50:30 ubuntu-phablet systemd-udevd[672]: Could not generate persistent MAC address for ifb0: No such file or directory Jan 3 10:50:30 ubuntu-phablet systemd-udevd[684]: Could not generate persistent MAC address for ifb1: No such file or directory Jan 3 10:50:30 ubuntu-phablet lxc-start[1220]: You lack access to /var/lib/lxc Jan 3 10:50:30 ubuntu-phablet systemd[1]: lxc-android-config.service: Control process exited, code=exited status=1 Jan 3 10:50:30 ubuntu-phablet systemd[1]: Failed to start LXC Android Config and Container Initialization. Jan 3 10:50:30 ubuntu-phablet systemd[1]: Dependency failed for force-mtp.service. Jan 3 10:50:30 ubuntu-phablet systemd[1]: force-mtp.service: Job force-mtp.service/start failed with result 'dependency'. Jan 3 10:50:30 ubuntu-phablet systemd[1]: lxc-android-config.service: Unit entered failed state. Jan 3 10:50:30 ubuntu-phablet systemd[1]: lxc-android-config.service: Failed with result 'exit-code'. This makes all of our frieza and cooler devices useless for testing purposes. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1653725/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1653979] Re: X-Ubuntu-Rotates-Window-Contents=true not respected in trust sessions
Saviq: kenvandine: the mir work to enable orientation as a surface property is done, it has been a todo to enable that with unity8 for some time -- 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/1653979 Title: X-Ubuntu-Rotates-Window-Contents=true not respected in trust sessions Status in Canonical System Image: Triaged Status in unity8 package in Ubuntu: Triaged Bug description: If an application with X-Ubuntu-Rotates-Window-Contents=true in its desktop file is invoked within a trust prompt, the flag is not respected. To test, try on the BQ M10 (frieza) adding a photo from the messaging- app by using the camera-app. It is broken with silo 2127 installed. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1653979/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1629009] Re: Does not work inside a snap due to hardcoded paths
** Changed in: indicator-display (Ubuntu) Assignee: (unassigned) => Charles Kerr (charlesk) ** Changed in: sync-monitor (Ubuntu) Assignee: (unassigned) => Renato Araujo Oliveira Filho (renatofilho) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-service in Ubuntu. https://bugs.launchpad.net/bugs/1629009 Title: Does not work inside a snap due to hardcoded paths Status in Canonical System Image: In Progress Status in Ubuntu File Manager App: Fix Released Status in address-book-app package in Ubuntu: Fix Released Status in address-book-service package in Ubuntu: Fix Released Status in camera-app package in Ubuntu: Fix Released Status in dialer-app package in Ubuntu: Fix Released Status in gallery-app package in Ubuntu: Fix Released Status in history-service package in Ubuntu: Fix Released Status in indicator-bluetooth package in Ubuntu: Fix Released Status in indicator-display package in Ubuntu: New Status in indicator-keyboard package in Ubuntu: Fix Released Status in indicator-location package in Ubuntu: Fix Released Status in indicator-messages package in Ubuntu: Fix Released Status in indicator-network package in Ubuntu: Fix Released Status in indicator-power package in Ubuntu: Fix Released Status in indicator-session package in Ubuntu: Fix Released Status in indicator-sound package in Ubuntu: Fix Released Status in indicator-transfer package in Ubuntu: Fix Released Status in maliit-framework package in Ubuntu: In Progress Status in mediaplayer-app package in Ubuntu: Fix Released Status in mediascanner2 package in Ubuntu: Fix Released Status in messaging-app package in Ubuntu: Fix Released Status in policykit-unity8 package in Ubuntu: Fix Released Status in sync-monitor package in Ubuntu: New Status in telephony-service package in Ubuntu: Fix Released Status in ubuntu-keyboard package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: Fix Released Status in ubuntu-terminal-app package in Ubuntu: Fix Released Status in ubuntu-touch-session package in Ubuntu: Fix Released Status in unity-scope-scopes package in Ubuntu: Won't Fix Status in unity-scopes-api package in Ubuntu: Fix Released Status in unity-scopes-shell package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Fix Released Status in webbrowser-app package in Ubuntu: Fix Released Bug description: Some apps can't find their main qml file. Error messages like: "file:///build/messaging-app-gcXPE6/messaging- app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found" (in my case, the file was in /snap/unity8-session/x24/usr/share /messaging-app/messaging-app.qml) Seems due to code like the following in config.h.in. Probably needs to consider the value of $SNAP or just be a little more forgiving. inline bool isRunningInstalled() { static bool installed = (QCoreApplication::applicationDirPath() == QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath()); return installed; } inline QString messagingAppDirectory() { if (isRunningInstalled()) { return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/"); } else { return QString("@CMAKE_SOURCE_DIR@/src/qml/"); } } inline QString ubuntuPhonePluginPath() { if (isRunningInstalled()) { return QString::null; } else { return QString("@CMAKE_SOURCE_DIR@/"); } } To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1629009/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
This will also works with Martins ppa and LinuxMint18 and iOS 10.2 sudo mkdir /media/iPhone sudo chmod 777 /media/iPhone ifuse /media/iPhone/ Than when will you access your folders on the phone ;-) when finish just unmount fusermount -u /media/iPhone next time when you like to access your phone just write ifuse /media/iPhone/ Hope this will helps ;-) -- 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 1629009] Re: Does not work inside a snap due to hardcoded paths
** Changed in: camera-app (Ubuntu) Status: In Progress => Fix Released ** Changed in: history-service (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-service in Ubuntu. https://bugs.launchpad.net/bugs/1629009 Title: Does not work inside a snap due to hardcoded paths Status in Canonical System Image: In Progress Status in Ubuntu File Manager App: Fix Released Status in address-book-app package in Ubuntu: Fix Released Status in address-book-service package in Ubuntu: Fix Released Status in camera-app package in Ubuntu: Fix Released Status in dialer-app package in Ubuntu: Fix Released Status in gallery-app package in Ubuntu: Fix Released Status in history-service package in Ubuntu: Fix Released Status in indicator-bluetooth package in Ubuntu: Fix Released Status in indicator-display package in Ubuntu: New Status in indicator-keyboard package in Ubuntu: Fix Released Status in indicator-location package in Ubuntu: Fix Released Status in indicator-messages package in Ubuntu: Fix Released Status in indicator-network package in Ubuntu: Fix Released Status in indicator-power package in Ubuntu: Fix Released Status in indicator-session package in Ubuntu: Fix Released Status in indicator-sound package in Ubuntu: Fix Released Status in indicator-transfer package in Ubuntu: Fix Released Status in maliit-framework package in Ubuntu: In Progress Status in mediaplayer-app package in Ubuntu: Fix Released Status in mediascanner2 package in Ubuntu: Fix Released Status in messaging-app package in Ubuntu: Fix Released Status in policykit-unity8 package in Ubuntu: Fix Released Status in sync-monitor package in Ubuntu: New Status in telephony-service package in Ubuntu: Fix Released Status in ubuntu-keyboard package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: Fix Released Status in ubuntu-terminal-app package in Ubuntu: Fix Released Status in ubuntu-touch-session package in Ubuntu: Fix Released Status in unity-scope-scopes package in Ubuntu: Won't Fix Status in unity-scopes-api package in Ubuntu: Fix Released Status in unity-scopes-shell package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Fix Released Status in webbrowser-app package in Ubuntu: Fix Released Bug description: Some apps can't find their main qml file. Error messages like: "file:///build/messaging-app-gcXPE6/messaging- app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found" (in my case, the file was in /snap/unity8-session/x24/usr/share /messaging-app/messaging-app.qml) Seems due to code like the following in config.h.in. Probably needs to consider the value of $SNAP or just be a little more forgiving. inline bool isRunningInstalled() { static bool installed = (QCoreApplication::applicationDirPath() == QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath()); return installed; } inline QString messagingAppDirectory() { if (isRunningInstalled()) { return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/"); } else { return QString("@CMAKE_SOURCE_DIR@/src/qml/"); } } inline QString ubuntuPhonePluginPath() { if (isRunningInstalled()) { return QString::null; } else { return QString("@CMAKE_SOURCE_DIR@/"); } } To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1629009/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1652564] Re: [i965 gen7][regression][patch]Intel mesa driver raises SIGFPE.
this is fixed already in 16.10 and up ** Changed in: mesa (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1652564 Title: [i965 gen7][regression][patch]Intel mesa driver raises SIGFPE. Status in mesa package in Ubuntu: Fix Released Bug description: There was a regression in intel mesa driver that caused raise of SIGFPE signal which resulted in startup error messages (about division by zero or invalid floating point operation) in some applications and games sensitive to this behavior. Currently it resolved in upstream: https://bugs.freedesktop.org/show_bug.cgi?id=95419 By following commit: https://cgit.freedesktop.org/mesa/mesa/commit/?id=01c89ccc5d1529aa1efbae80c8ef641a59abbd93 Is it possible to include foregoing patch to avoid bug in current distributions? Distribution: Ubuntu 16.04 Video card: Intel HD 4600 Mesa version: 11.2.0-1ubuntu2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1652564/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1100546] Re: Power indicator favours 'not present' mouse over laptop battery level
This patch passed the unit tests. ** Patch added: "indicator-power_12.10.6+16.04.20160105-0ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1100546/+attachment/4799964/+files/indicator-power_12.10.6+16.04.20160105-0ubuntu1.debdiff ** Patch removed: "indicator-power_12.10.6+16.04.20160105-0ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1100546/+attachment/4799891/+files/indicator-power_12.10.6+16.04.20160105-0ubuntu1.debdiff -- 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/1100546 Title: Power indicator favours 'not present' mouse over laptop battery level Status in indicator-power: Triaged Status in indicator-power package in Ubuntu: Triaged Bug description: The power indicator shows the battery level for cordless mice and keyboards, even when it cannot identify the battery level. This is a problem as it seems to favour showing a "not present" mouse status over the laptop battery level in the top bar. I haven't done a good job of explaining it, so check out the screenshot - it will explain all :) Basically, the laptop battery should be shown in the top bar if the mouse/keyboard is "not present". Also hiding the mouse and keyboard when the battery level is unknown would also be useful too :) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: indicator-power 12.10.6daily12.11.21.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-0.3-generic 3.8.0-rc3 Uname: Linux 3.8.0-0-generic x86_64 ApportVersion: 2.8-0ubuntu1 Architecture: amd64 Date: Thu Jan 17 10:11:16 2013 InstallationDate: Installed on 2012-12-14 (33 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121214) MarkForUpload: True SourcePackage: indicator-power UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-power/+bug/1100546/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1653979] Re: X-Ubuntu-Rotates-Window-Contents=true not respected in trust sessions
** Changed in: unity8 (Ubuntu) Status: New => Triaged ** Changed in: unity8 (Ubuntu) Importance: Undecided => High ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Status: New => Triaged ** Changed in: canonical-devices-system-image Importance: Undecided => High -- 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/1653979 Title: X-Ubuntu-Rotates-Window-Contents=true not respected in trust sessions Status in Canonical System Image: Triaged Status in unity8 package in Ubuntu: Triaged Bug description: If an application with X-Ubuntu-Rotates-Window-Contents=true in its desktop file is invoked within a trust prompt, the flag is not respected. To test, try on the BQ M10 (frieza) adding a photo from the messaging- app by using the camera-app. It is broken with silo 2127 installed. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1653979/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp