Re: [Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04
On Fri 2016-12-30 20:19:04 -0500, Colin Watson wrote: > Sounds like the problem is that this build leaves processes hanging > around from its tests. Unfortunately this currently causes builds to > hang, basically because launchpad-buildd uses sbuild's sudo mode rather > than its schroot mode. So the hang is a known bug in launchpad-buildd, > but it should still be possible to fix this: make sure that the test > suite cleans up all its processes on exit, which is something that > should be actionable with a bit of care. it wouldn't surprise me if there are indeed processes still hanging around due to modern GnuPG's multi-process model (with dirmngr and gpg-agent getting launched as-needed). If you're doing the build on a modern linux system, and you haven't explicitly disabled the GnuPG's inotify support, and the test suite deletes any temporary GNUPGHOME homedirs, the subprocesses should notice the deletion and terminate promptly. This might depend on relatively recent versions of "modern" GnuPG, though (debian's currently shipping 2.1.17, fwiw). --dkg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1647204 Title: 1.8.0-2 FTBFS in zesty 17.04 Status in gpgme1.0 package in Ubuntu: Confirmed Bug description: 1.8.0-2 synced from debian in Zesty Zapus 17.04 fails to build on all architectures from source with the error: checking whether a simple qt program can be built... no configure: error: *** *** Qt5 (Qt5Core) is required for Qt binding. *** The packages builds without this issue in debian unstable. A little experimentation shows that is a ubuntu sbuild/pbuilder and ppa, setting -pie in the hardening options allows the build to proceed with the Qt bindings building properly. Not being overly familiar with the hardening, I am unsure if dropping that feature set is relatively harmless, or massively undesirable and potentially harmful. However, in a ppa build, but NOT in my local sbuild/pbuilder chroot, the resulting build then hangs on the (python?) tests on starting or stopping gpg-agent, and the build is eventually killed due to inactivity after 150 mins as follows GNUPGHOME=/<>/lang/python/tests LC_ALL=C GPG_AGENT_INFO= top_srcdir=../../.. srcdir=. LD_LIBRARY_PATH="../../../src/.libs:" /usr/bin/python3 ./run-tests.py \ --interpreters="/usr/bin/python /usr/bin/python3" --srcdir=. \ initial.py t-wrapper.py t-callbacks.py t-data.py t-encrypt.py t-encrypt-sym.py t-encrypt-sign.py t-sign.py t-signers.py t-decrypt.py t-verify.py t-decrypt-verify.py t-sig-notation.py t-export.py t-import.py t-trustlist.py t-edit.py t-keylist.py t-wait.py t-encrypt-large.py t-file-name.py t-idiomatic.py t-protocol-assuan.py final.py starting gpg-agent Session terminated, terminating shell...make[1]: *** wait: No child processes. Stop. make[1]: *** Waiting for unfinished jobs make[1]: *** wait: No child processes. Stop. make[3]: *** wait: No child processes. Stop. make[3]: *** Waiting for unfinished jobs make[3]: *** wait: No child processes. Stop. ...terminated. make: *** wait: No child processes. Stop. make: *** Waiting for unfinished jobs make: *** wait: No child processes. Stop. Makefile:457: recipe for target 'check-recursive' failed make[2]: *** [check-recursive] Terminated Makefile:602: recipe for target 'xcheck' failed make[4]: *** [xcheck] Terminated Build killed with signal TERM after 150 minutes of inactivity I would note that this is the first gpgme version from gpg directly, with the Qt bindings built. These will be essential for future KDE applications and frameworks, as the gpgmepp previously built in KDE's own packages is being dropped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1647204/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1582191] Re: Boot stalls for 90 seconds on mdadm
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1582191 Title: Boot stalls for 90 seconds on mdadm Status in systemd package in Ubuntu: Confirmed Bug description: On a fresh Ubuntu Xenial 16.04 LTS Server install, the boot stalls for exactly 90 seconds when using a fairly complex partitioning setup. After this, everything works as expected. The partitioning is as follows: /sda GPT /sda1 ESP (/boot/efi) /sda2 raid1 md0 ext4 (/boot) /sda3 raid1 md1 luks,passphrase ext4 (/) /sda4 raid1 md2 luks,key zfs /sdb GPT /sdb1 ESP (copy of /boot/efi) /sdb2 raid1 md0 ext4 (/boot) /sdb3 raid1 md1 luks,passphrase ext4 (/) /sdb4 raid1 md2 luks,key zfs /sdc GPT /sdc1 luks,key xfs /sdd GPT /sdd1 luks,key xfs /sdd2 luks,random swap This may be an installer or mdadm bug instead - I have not been able to exactly determine the cause of the bug. I have several identical servers, all showing the same symptom, so it should not be due to broken hardware (although design flaws are on the table). The key seems to be in these lines from journalctl: ... May 16 14:06:08 molnix kernel: bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this. May 16 14:06:08 molnix kernel: device eno1 entered promiscuous mode May 16 14:06:08 molnix systemd-udevd[689]: Process '/lib/udev/hdparm' failed with exit code 5. May 16 14:06:08 molnix systemd-udevd[701]: Process '/lib/udev/hdparm' failed with exit code 5. May 16 14:06:08 molnix systemd-udevd[707]: Process '/lib/udev/hdparm' failed with exit code 5. May 16 14:06:08 molnix systemd[1]: Started Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling. May 16 14:06:08 molnix systemd-udevd[701]: Process '/sbin/mdadm --incremental /dev/sda2 --offroot' failed with exit code 1. May 16 14:06:08 molnix systemd-udevd[707]: Process '/sbin/mdadm --incremental /dev/sda3 --offroot' failed with exit code 1. May 16 14:06:08 molnix systemd[1]: Found device Samsung_SSD_850_EVO_250GB EFI\x20System\x20Partition. May 16 14:06:08 molnix systemd-udevd[708]: Process '/sbin/mdadm --incremental /dev/sda4 --offroot' failed with exit code 1. May 16 14:06:08 molnix systemd-udevd[689]: Process '/sbin/mdadm --incremental /dev/sdb3 --offroot' failed with exit code 1. May 16 14:06:08 molnix systemd[1]: Reached target Local File Systems (Pre). May 16 14:06:08 molnix systemd-udevd[701]: Process '/sbin/mdadm --incremental /dev/sdb4 --offroot' failed with exit code 1. May 16 14:06:08 molnix systemd-udevd[699]: Process '/sbin/mdadm --incremental /dev/sdb2 --offroot' failed with exit code 1. May 16 14:06:08 molnix systemd-udevd[706]: Process '/lib/udev/hdparm' failed with exit code 5. May 16 14:06:08 molnix kernel: ipmi_si IPI0001:00: The BMC does not support clearing the recv irq bit, compensating, but the BMC needs to be fixed. May 16 14:06:08 molnix kernel: ipmi_si IPI0001:00: Found new BMC (man_id: 0x002a7c, prod_id: 0x086d, dev_id: 0x20) ... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Mon May 16 14:17:31 2016 InstallationDate: Installed on 2016-05-15 (0 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) MachineType: Supermicro Super Server ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=0ca65308-3f70-4231-8f5f-e68583a6d5b3 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 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.0c dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X10SDV-4C-TLN4F dmi.board.vendor: Supermicro dmi.board.version: 2.00 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.0c:bd01/04/2016:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX10SDV-4C-TLN4F:rvr2.00:cvnSupermicro:ct17:cvr0123456789: dmi.product.name: Super Server dmi.product.version: 0123456789 dmi.sys.vend
[Touch-packages] [Bug 1653629] [NEW] unity 8 flaky test test_unfavoriteScope
Public bug reported: I got the following for 1 out of 4 runs (xenial/zesty, i386/amd64): FAIL! : qmltestrunner::DashContent::test_unfavoriteScope() function returned unexpected result Actual (): false Expected (): true Full log: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-xenial-ci-train-ppa- service-2326/xenial/i386/u/unity8/20170102_123818_311bd@/log.gz ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: flaky -- 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/1653629 Title: unity 8 flaky test test_unfavoriteScope Status in unity8 package in Ubuntu: New Bug description: I got the following for 1 out of 4 runs (xenial/zesty, i386/amd64): FAIL! : qmltestrunner::DashContent::test_unfavoriteScope() function returned unexpected result Actual (): false Expected (): true Full log: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-xenial-ci-train-ppa- service-2326/xenial/i386/u/unity8/20170102_123818_311bd@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1653629/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1647204] Re: 1.8.0-2 FTBFS in zesty 17.04
On 31/12/16 01:19, Colin Watson wrote: > Sounds like the problem is that this build leaves processes hanging > around from its tests. Unfortunately this currently causes builds to > hang, basically because launchpad-buildd uses sbuild's sudo mode rather > than its schroot mode. So the hang is a known bug in launchpad-buildd, > but it should still be possible to fix this: make sure that the test > suite cleans up all its processes on exit, which is something that > should be actionable with a bit of care. > As discussed, the hang is not on exit/completion of the testsuite though, but seems to be at a particular call midway through a one test. So seems there is something a little different at play here. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1647204 Title: 1.8.0-2 FTBFS in zesty 17.04 Status in gpgme1.0 package in Ubuntu: Confirmed Bug description: 1.8.0-2 synced from debian in Zesty Zapus 17.04 fails to build on all architectures from source with the error: checking whether a simple qt program can be built... no configure: error: *** *** Qt5 (Qt5Core) is required for Qt binding. *** The packages builds without this issue in debian unstable. A little experimentation shows that is a ubuntu sbuild/pbuilder and ppa, setting -pie in the hardening options allows the build to proceed with the Qt bindings building properly. Not being overly familiar with the hardening, I am unsure if dropping that feature set is relatively harmless, or massively undesirable and potentially harmful. However, in a ppa build, but NOT in my local sbuild/pbuilder chroot, the resulting build then hangs on the (python?) tests on starting or stopping gpg-agent, and the build is eventually killed due to inactivity after 150 mins as follows GNUPGHOME=/<>/lang/python/tests LC_ALL=C GPG_AGENT_INFO= top_srcdir=../../.. srcdir=. LD_LIBRARY_PATH="../../../src/.libs:" /usr/bin/python3 ./run-tests.py \ --interpreters="/usr/bin/python /usr/bin/python3" --srcdir=. \ initial.py t-wrapper.py t-callbacks.py t-data.py t-encrypt.py t-encrypt-sym.py t-encrypt-sign.py t-sign.py t-signers.py t-decrypt.py t-verify.py t-decrypt-verify.py t-sig-notation.py t-export.py t-import.py t-trustlist.py t-edit.py t-keylist.py t-wait.py t-encrypt-large.py t-file-name.py t-idiomatic.py t-protocol-assuan.py final.py starting gpg-agent Session terminated, terminating shell...make[1]: *** wait: No child processes. Stop. make[1]: *** Waiting for unfinished jobs make[1]: *** wait: No child processes. Stop. make[3]: *** wait: No child processes. Stop. make[3]: *** Waiting for unfinished jobs make[3]: *** wait: No child processes. Stop. ...terminated. make: *** wait: No child processes. Stop. make: *** Waiting for unfinished jobs make: *** wait: No child processes. Stop. Makefile:457: recipe for target 'check-recursive' failed make[2]: *** [check-recursive] Terminated Makefile:602: recipe for target 'xcheck' failed make[4]: *** [xcheck] Terminated Build killed with signal TERM after 150 minutes of inactivity I would note that this is the first gpgme version from gpg directly, with the Qt bindings built. These will be essential for future KDE applications and frameworks, as the gpgmepp previously built in KDE's own packages is being dropped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1647204/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1653183] Re: package ntp 1:4.2.8p4+dfsg-3ubuntu5.3 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1
Hi, thank you for reporting this bug and your help to make Ubuntu better. The logs point to two potential reasons: One is: name server cannot be used: Temporary failure in name resolution (-3) The other is: ntp (1:4.2.8p4+dfsg-3ubuntu5.3) ... insserv: warning: script 'php-fpm5.3' missing LSB tags and overrides insserv: warning: script 'php-fpm5.2.17' missing LSB tags and overrides insserv: script virtualbox: service vboxdrv already provided! insserv: script virtualbox: service virtualbox already provided! insserv: There is a loop between service nginx and php-fpm5.3 if stopped insserv: loop involving service php-fpm5.3 at depth 2 insserv: loop involving service nginx at depth 1 insserv: Stopping php-fpm5.3 depends on nginx and therefore on system facility `$all' which can not be true! insserv: Stopping php-fpm5.2.17 depends on nginx and therefore on system facility `$all' which can not be true! insserv: exiting now without changing boot order! update-rc.d: error: insserv rejected the script header Not sure on the second one, it mostly shows up on custom non-archive packages and init scripts. But sometimes due to bugs in the package dependencies - often that can be resolved by removing and reinstalling the offending pacakges. For the fist it might be due to a special or incomplete network setup - could that be the case for you? ** Changed in: ntp (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1653183 Title: package ntp 1:4.2.8p4+dfsg-3ubuntu5.3 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1 Status in ntp package in Ubuntu: Incomplete Bug description: null ProblemType: Package DistroRelease: Ubuntu 16.04 Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.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 AptOrdering: libopts25: Install ntp: Install libopts25: Configure ntp: Configure NULL: ConfigurePending Architecture: amd64 Date: Thu Dec 29 18:50:18 2016 ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 1 InstallationDate: Installed on 2016-07-21 (161 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) NtpStatus: ntpq: read: Connection refused ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic root=UUID=19d3594c-dd8f-40d3-902b-68ac5e1276d9 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: ntp Title: package ntp 1:4.2.8p4+dfsg-3ubuntu5.3 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1653183/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1653635] [NEW] cmake unable to report INCLUDE_DIRS and LIBRARIES
Public bug reported:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.1 LTS
Release:16.04
Codename: xenial
$ dpkg -l|grep libjsoncpp
ii libjsoncpp-dev:amd64 1.7.2-1
amd64library for reading and writing JSON for C++ (devel
files)
ii libjsoncpp1:amd64 1.7.2-1
amd64library for reading and writing JSON for C++
When try to use jsoncpp, the ${jsoncpp_INCLUDE_DIRS} and
${jsoncpp_LIBRARIES} fail to report.
CMakeLists.txt
cmake_minimum_required(VERSION 2.6.2)
project(jsoncpp_test)
find_package(jsoncpp REQUIRED)
message("FOUND CONFIG: ${jsoncpp_CONFIG}")
message("INCLUDE DIRS: ${jsoncpp_INCLUDE_DIRS}")
message("LIBRARIES: ${jsoncpp_LIBRARIES}")
The actual result is:
FOUND CONFIG: /usr/lib/x86_64-linux-gnu/cmake/jsoncpp/jsoncppConfig.cmake
INCLUDE DIRS:
LIBRARIES:
** Affects: libjsoncpp (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libjsoncpp in Ubuntu.
https://bugs.launchpad.net/bugs/1653635
Title:
cmake unable to report INCLUDE_DIRS and LIBRARIES
Status in libjsoncpp package in Ubuntu:
New
Bug description:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.1 LTS
Release: 16.04
Codename: xenial
$ dpkg -l|grep libjsoncpp
ii libjsoncpp-dev:amd64 1.7.2-1
amd64library for reading and writing JSON for C++ (devel
files)
ii libjsoncpp1:amd64 1.7.2-1
amd64library for reading and writing JSON for C++
When try to use jsoncpp, the ${jsoncpp_INCLUDE_DIRS} and
${jsoncpp_LIBRARIES} fail to report.
CMakeLists.txt
cmake_minimum_required(VERSION 2.6.2)
project(jsoncpp_test)
find_package(jsoncpp REQUIRED)
message("FOUND CONFIG: ${jsoncpp_CONFIG}")
message("INCLUDE DIRS: ${jsoncpp_INCLUDE_DIRS}")
message("LIBRARIES: ${jsoncpp_LIBRARIES}")
The actual result is:
FOUND CONFIG: /usr/lib/x86_64-linux-gnu/cmake/jsoncpp/jsoncppConfig.cmake
INCLUDE DIRS:
LIBRARIES:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjsoncpp/+bug/1653635/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1653657] [NEW] FTBFS on s390x
Public bug reported: 0.168-0.2 ftbfs on s390x. ** Affects: elfutils (Ubuntu) Importance: Undecided Assignee: Dimitri John Ledkov (xnox) Status: New ** Tags: s390x -- 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/1653657 Title: FTBFS on s390x Status in elfutils package in Ubuntu: New Bug description: 0.168-0.2 ftbfs on s390x. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/1653657/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
Same source built in Debian two weeks ago even for armhf, so maybe gcc-6 6.3.0 is related. ** Also affects: gcc-6 (Ubuntu) Importance: Undecided Status: New -- 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: New Status in qtwebkit-opensource-src package in Ubuntu: New 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@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)
Moving the ipr module from linux-image-extra to linux-image package should resolve this issue as well, no? Essential modules for booting should be kept in the linux-image package, whilst auxiliary can be kept in the -extra package. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Description changed: + @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 - + + 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) + 0045:01:00.3 Ethernet controller: Broadcom Corporation NetXtreme BCM5719 Gigabit Ethernet PCIe (rev 01) - - Machine Type = P8 - + Ma
[Touch-packages] [Bug 1649352] Re: http direct to terminals?
This bug was fixed in the package base-files - 9.6ubuntu9 --- base-files (9.6ubuntu9) zesty; urgency=medium * Fix LP: #1649352 - use https://motd.ubuntu.com in the default file - enforce that every news server must be https - take at most the first 10 lines, and first 80 chars per line - remove all control characters (except newline) -- Dustin Kirkland Sat, 17 Dec 2016 09:19:53 -0600 ** Changed in: base-files (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 base-files in Ubuntu. https://bugs.launchpad.net/bugs/1649352 Title: http direct to terminals? Status in base-files package in Ubuntu: Fix Released Bug description: Hi Dustin, Some recent changes introduced what looks to be a serious problem: http://launchpadlibrarian.net/296647523/base- files_9.6ubuntu7_9.6ubuntu8.diff.gz -SERVER="https://motd.ubuntu.com"; +# White space separated list of 0 to many news services +SERVER="http://motd.ubuntu.com"; [...] + if curl --connect-timeout "$WAIT" --max-time "$WAIT" -A "$USER_AGENT" -o- "$s" >"$NEWS" 2>"$ERR"; then + echo + # At most, 2 lines of at most 80 characters + cat "$NEWS" | tail -n 2 | cut -c -80 This allows any network man-in-the-middle attacker, DNS response forger, or BGP forger, to write 160 raw bytes directly to terminals. The previous version wasn't good (open for abuse by anyone who could trick one of the myriad x.509 Certificate Authorities to mis-issue a certificate) but this version is open for abuse by significantly more attackers. While most terminals are reasonably safe against outright maliciousness this has been a recurring exploitation theme for twenty years, and even what is "safe" for them to display could be wildly confusing to users unfamiliar with maliciously controlled terminals. (And users have wide tastes in terminals, some are fairly brittle.) cat(1) does not do any filtering for 'safe' display of arbitrary inputs. less(1) does, assuming -r is not in LESS environment variable or the less(1) command line. If you wish to keep the pipeline, perhaps tr(1)'s -d flag could be useful. On a related note, is there a reason why the motd.ubuntu.com server can't do HTTPS? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1649352/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1653666] [NEW] know not what to put here
Public bug reported: post initramfs ??? error satus 1, or something like that new to ubuntu and don't know much about commandline and how to find and repair problems; please help thank you much James Street ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-51.72-lowlatency 4.4.30 Uname: Linux 4.4.0-51-lowlatency 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 Date: Tue Jan 3 06:02:15 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:1526] Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:1526] InstallationDate: Installed on 2016-11-20 (44 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160125) MachineType: Hewlett-Packard HP 620 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-51-lowlatency root=/dev/mapper/ubuntu--studio--vg-root ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PVI Ver. F.20 dmi.board.name: 1526 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.0E dmi.chassis.asset.tag: 5CG104013Q dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PVIVer.F.20:bd12/12/2011:svnHewlett-Packard:pnHP620:pvrF.20:rvnHewlett-Packard:rn1526:rvrKBCVersion71.0E:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP 620 dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard 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 xserver.bootTime: Tue Jan 3 05:38:23 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9196 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1653666 Title: know not what to put here Status in xorg package in Ubuntu: New Bug description: post initramfs ??? error satus 1, or something like that new to ubuntu and don't know much about commandline and how to find and repair problems; please help thank you much James Street ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-51.72-lowlatency 4.4.30 Uname: Linux 4.4.0-51-lowlatency 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 Date: Tue Jan 3 06:02:15 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:1526] Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:1526] InstallationDate: Installed on 2016-11-20 (44 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160125) MachineType: Hewlett-Packard HP 620 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-51-lowlatency root=/dev/mapper/ubuntu--studio--vg-root ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PVI Ver. F.20 dmi.board.name: 1526 dmi.board.vendor
[Touch-packages] [Bug 1653529] Re: qtwebkit 5.7.1 fails to build on armhf
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gcc-6 (Ubuntu) Status: New => Confirmed -- 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@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
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: qtwebkit-opensource-src (Ubuntu) Status: New => Confirmed -- 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@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1653675] [NEW] OpenVPN network-manager does not correctly import .crt and .key files when importing .ovpn file, instead it will import a useless .pem file
Public bug reported: When importing .ovpn file from a provider in network-manager, Under VPN tab > it auto-populates the CA Certificate field with a default .pem file which i am not sure where it even found that. Also under VPN > Advanced > Key File - it would auto-populate the field with a .pem as well. Are these .pem files system generated? because it surely does not come from the .ovpn file itself. It is true that the .ovpn file includes both the .crt and .key within the file.ovpn, because from Terminal it connects perfectly and does not require an external .crt and .key to be included in the command # openvpn vpnserver.tcp443.com.ovpn OpenVPN does not correctly import .crt and .key files when importing .ovpn file in network-manager, This makes it difficult for the user when importing many vpn servers, to go to the CA and tls key field and import the correct certificates manually everytime. Whats supposed to happen is, Network-Manager is supposed to import the CA and tls key correctly which come from the .ovpn file itself once .ovpn file gets imported. Can this be fixed? On a side note: it would be heavily appreciated if network-manager is able to mass import all .ovpn files at once correctly WITH ca and tls keys in place. At the moment, it is to my understanding that there is not even a way to backup ovpn profiles and to import them backup all at once to a new PC. Everything has to be done manually. Hope this can be included in the bug fix. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: xenial -- 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/1653675 Title: OpenVPN network-manager does not correctly import .crt and .key files when importing .ovpn file, instead it will import a useless .pem file Status in network-manager package in Ubuntu: New Bug description: When importing .ovpn file from a provider in network-manager, Under VPN tab > it auto-populates the CA Certificate field with a default .pem file which i am not sure where it even found that. Also under VPN > Advanced > Key File - it would auto-populate the field with a .pem as well. Are these .pem files system generated? because it surely does not come from the .ovpn file itself. It is true that the .ovpn file includes both the .crt and .key within the file.ovpn, because from Terminal it connects perfectly and does not require an external .crt and .key to be included in the command # openvpn vpnserver.tcp443.com.ovpn OpenVPN does not correctly import .crt and .key files when importing .ovpn file in network-manager, This makes it difficult for the user when importing many vpn servers, to go to the CA and tls key field and import the correct certificates manually everytime. Whats supposed to happen is, Network-Manager is supposed to import the CA and tls key correctly which come from the .ovpn file itself once .ovpn file gets imported. Can this be fixed? On a side note: it would be heavily appreciated if network-manager is able to mass import all .ovpn files at once correctly WITH ca and tls keys in place. At the moment, it is to my understanding that there is not even a way to backup ovpn profiles and to import them backup all at once to a new PC. Everything has to be done manually. Hope this can be included in the bug fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1653675/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
** Tags added: papercuts2017 -- 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/1585863 Title: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it. Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in network-manager package in Ubuntu: Confirmed Bug description: Description:Ubuntu Yakkety Yak (development branch) Release:16.10 Packages: libnm-glib-vpn1:amd64 1.2.2-0ubuntu2 libnm-glib4:amd64 1.2.2-0ubuntu2 libnm-util2:amd64 1.2.2-0ubuntu2 libnm0:amd641.2.2-0ubuntu2 network-manager 1.2.2-0ubuntu2 Reproduce steps: 1. Install fwts by `sudo apt-get install fwts`. 2. Run the suspend & resume stress test. sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 --s3-delay-delta=5 Expected result: The WiFi still functioned. Actual result: The WiFi can not connect to any access point and we have to execute `sudo wpa_cli scan` manually to make it work again. P.S. Ubuntu 16.04 also has the same issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1585863/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
** Tags added: papercuts2017 -- 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 1620636] Re: Fails to pair with Bose QC35 headphones
** Tags added: papercuts2017 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1620636 Title: Fails to pair with Bose QC35 headphones Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: In Progress Bug description: I am unable to pair the Bose QC35 BT headphones with Ubuntu, either Ubuntu desktop running 16.04 LTS with bluez 5.37 (also tried bluez 5.41 from installed from yakkety archive), nor using Ubuntu Touch rc- proposed build for Turbo #174. I'm trying to pair through the normal bluetooth control panel brought up through the bluetooth indicator. I've attached some logs that show it failing to pair. If I can provide anymore useful information about the headphones, please let me know. Syslog with bluetoothd debugging enabled: http://pastebin.ubuntu.com/23141394/ btmon output: http://pastebin.ubuntu.com/23141446/ bluetoothctl output: http://pastebin.ubuntu.com/23141510/ With Linux kernel 4.8.0 and bluez 4.52: --- bluetoothctl: http://pastebin.ubuntu.com/23256457/ btmon: http://pastebin.ubuntu.com/23256471/ To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620636/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1607390] Re: serious bug on bluetooth (Ubuntu 16.04 LTS)
** Tags added: papercuts2017 -- 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/1607390 Title: serious bug on bluetooth (Ubuntu 16.04 LTS) Status in bluez package in Ubuntu: Confirmed Bug description: I've recently installed ubuntu 16.04 LTS twice -and i discovered that the problem was from the tool katoolin so i didn't install it- after i installed ubuntu the bluetooth didn't work for me. P.S:the bluetooth was working when my laptop was ubuntu 15.04 when i turn bluetooth on to connect my mouse the switch was on but it said that Bluetooth is disabled i entered the command sudo rfkill unblock bluetooth it worked but didn't connect to the mouse even after the next restart i also tried to editing the file /etc/rc.local (putting sudo rfkill unblock bluetooth before last line and restarting) and i've tried **sudo hciconfig hci0 reset** with output > Can't init device hci0: Connection timed out (110) my lsusb; rfkill list output: 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 004: ID 1bcf:2883 Sunplus Innovation Technology Inc. Bus 001 Device 014: ID 04ca:3005 Lite-On Technology Corp. 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 Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 04d9:1503 Holtek Semiconductor, Inc. Keyboard Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 0: asus-wlan: Wireless LAN Soft blocked: no Hard blocked: no 1: asus-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 11: hci0: Bluetooth Soft blocked: no Hard blocked: no and output of **dmesg | grep -Ei 'ath3k|blue'** [1.727681] usb 1-1.1: Product: Bluetooth USB Host Controller [ 34.157120] Bluetooth: Core ver 2.21 [ 34.157135] Bluetooth: HCI device and connection manager initialized [ 34.157138] Bluetooth: HCI socket layer initialized [ 34.157140] Bluetooth: L2CAP socket layer initialized [ 34.157145] Bluetooth: SCO socket layer initialized [ 35.604410] usbcore: registered new interface driver ath3k [ 51.744300] usb 1-1.1: Product: Bluetooth USB Host Controller [ 53.810045] Bluetooth: hci0 command 0x0c25 tx timeout [ 55.814079] Bluetooth: hci0 command 0x0c38 tx timeout [ 57.818111] Bluetooth: hci0 command 0x0c39 tx timeout [ 59.822149] Bluetooth: hci0 command 0x0c05 tx timeout [ 66.997548] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 66.997552] Bluetooth: BNEP filters: protocol multicast [ 66.997556] Bluetooth: BNEP socket layer initialized [ 195.105902] usb 1-1.1: Product: Bluetooth USB Host Controller [ 195.328480] Bluetooth: RFCOMM TTY layer initialized [ 195.328488] Bluetooth: RFCOMM socket layer initialized [ 195.328495] Bluetooth: RFCOMM ver 1.11 [ 199.131870] Bluetooth: hci0 command 0x1009 tx timeout [ 276.169130] usb 1-1.1: Product: Bluetooth USB Host Controller [ 294.258992] Bluetooth: hci0 command 0x1005 tx timeout [ 296.263065] Bluetooth: hci0 command 0x0c23 tx timeout [ 298.267076] Bluetooth: hci0 command 0x0c14 tx timeout [ 306.361529] usb 1-1.1: Product: Bluetooth USB Host Controller [ 346.417970] Bluetooth: hci0 command 0x0c56 tx timeout [ 348.421916] Bluetooth: hci0 command 0x0c45 tx timeout [ 350.425782] Bluetooth: hci0 command 0x0c58 tx timeout [ 352.429744] Bluetooth: hci0 command 0x1004 tx timeout [ 366.099802] usb 1-1.1: Product: Bluetooth USB Host Controller [ 368.145218] Bluetooth: hci0 command 0x1001 tx timeout [ 370.149130] Bluetooth: hci0 command 0x1009 tx timeout [ 410.346611] usb 1-1.1: Product: Bluetooth USB Host Controller [ 421.612041] Bluetooth: hci0 command 0x0c23 tx timeout [ 423.616060] Bluetooth: hci0 command 0x0c14 tx timeout [ 425.620018] Bluetooth: hci0 command 0x0c25 tx timeout [ 427.623984] Bluetooth: hci0 command 0x0c38 tx timeout [ 442.650168] usb 1-1.1: Product: Bluetooth USB Host Controller [ 444.727752] Bluetooth: hci0 command 0x0c52 tx timeout [ 446.731800] Bluetooth: hci0 command 0x0c45 tx timeout [ 448.735743] Bluetooth: hci0 command 0x0c58 tx timeout [ 450.739762] Bluetooth: hci0 command 0x1004 tx timeout [ 4000.639722] usb 1-1.1: Product: Bluetooth USB Host Controller [ 4011.801141] Bluetooth: hci0 command 0x2002 tx timeout [ 4013.805106] Bluetooth: hci0 command 0x2003 tx timeout [ 4015.809139] Bluetooth: hci0 command 0x
[Touch-packages] [Bug 1510570] Re: BLE pairing fail
** Tags added: papercuts2017 -- 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 1454450] Re: Bluetooth mouse laggy and erratic
** Tags added: papercuts2017 -- 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/1454450 Title: Bluetooth mouse laggy and erratic Status in bluez package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: I installed Ubuntu 15.04 (64 bit) on a DELL XPS 13 (model 9343, bios A03) notebook. I use a DELL bluetooth mouse but sometimes it behaves erratically (laggy, jumpy). The problem happens after a few (sometimes one) suspend and resume. I am attaching below some info on my system. Thank you. cribari@darwin4:~$ uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetooth Linux darwin4 3.19.0-17-generic #17-Ubuntu SMP Wed May 6 16:46:12 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux 02:00.0 Network controller [0280]: Broadcom Corporation BCM4352 802.11ac Wireless Network Adapter [14e4:43b1] (rev 03) Subsystem: Dell Device [1028:0019] Kernel driver in use: wl Bus 003 Device 002: ID 8087:8001 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:216f Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [2.174367] Bluetooth: Core ver 2.20 [2.174669] Bluetooth: HCI device and connection manager initialized [2.174792] Bluetooth: HCI socket layer initialized [2.174795] Bluetooth: L2CAP socket layer initialized [2.175449] Bluetooth: SCO socket layer initialized [2.592936] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1624 lmp_ver=06 lmp_subver=220e [3.203438] Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=1624 lmp_ver=06 lmp_subver=220e [3.542418] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [3.542421] Bluetooth: BNEP filters: protocol multicast [3.542425] Bluetooth: BNEP socket layer initialized [3.551641] Bluetooth: RFCOMM TTY layer initialized [3.551649] Bluetooth: RFCOMM socket layer initialized [3.551654] Bluetooth: RFCOMM ver 1.11 [ 26.569283] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 26.569287] Bluetooth: HIDP socket layer initialized [ 26.576971] input: Dell Travel Mouse WM524 as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:11/0005:046D:B00E.0003/input/input15 [ 26.577172] hid-generic 0005:046D:B00E.0003: input,hidraw2: BLUETOOTH HID v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c [ 72.448281] input: Dell Travel Mouse WM524 as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:12/0005:046D:B00E.0004/input/input16 [ 72.448526] hid-generic 0005:046D:B00E.0004: input,hidraw2: BLUETOOTH HID v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c [ 2994.842547] input: Dell Travel Mouse WM524 as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:13/0005:046D:B00E.0005/input/input17 [ 2994.842810] hid-generic 0005:046D:B00E.0005: input,hidraw2: BLUETOOTH HID v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c [ 3694.214037] Bluetooth: hci0: BCM: patching hci_ver=06 hci_rev=1000 lmp_ver=06 lmp_subver=220e [ 3694.861578] Bluetooth: hci0: BCM: firmware hci_ver=06 hci_rev=1624 lmp_ver=06 lmp_subver=220e [ 3811.777260] input: Dell Travel Mouse WM524 as /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/bluetooth/hci0/hci0:11/0005:046D:B00E.0006/input/input20 [ 3811.777571] hid-generic 0005:046D:B00E.0006: input,hidraw2: BLUETOOTH HID v8.00 Mouse [Dell Travel Mouse WM524] on ac:d1:b8:c0:6f:5c [ 5579.876192] Modules linked in: huawei_cdc_ncm cdc_wdm cdc_ncm option usb_wwan usbserial usbnet mii uas usb_storage hid_generic hidp nvram msr binfmt_misc rfcomm bnep nls_iso8859_1 intel_rapl iosf_mbi x86_pkg_temp_thermal dell_wmi sparse_keymap intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul dell_laptop dcdbas btusb crc32_pclmul bluetooth ghash_clmulni_intel hid_multitouch aesni_intel aes_x86_64 lrw uvcvideo gf128mul videobuf2_vmalloc glue_helper wl(POE) videobuf2_memops ablk_helper videobuf2_core cryptd v4l2_common videodev media joydev i915_bpo serio_raw i915 dell_led rtsx_pci_ms intel_ips memstick snd_hda_codec_realtek snd_soc_rt286 snd_hda_codec_generic cfg80211 snd_soc_core drm_kms_helper mei_me lpc_ich shpchp mei snd_compress snd_hda_intel snd_hda_controller drm snd_hda_codec i2c_algo_bit [ 5579.876223] Workqueue: hci0 hci_power_on [bluetooth] [ 5579.876261] [] hci_dev_do_open+0xe1/0xa90 [bluetooth] [ 5579.876266] [] hci_power_on+0x40/0x200 [bluetooth] [ 5579.876284] bluetooth hci0: firmware: brcm/BCM20702A0-0a5c-216f.hcd will not be loaded [ 5579.876286] Bluetooth: hci0: BCM:
[Touch-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety
** Tags added: papercuts2017 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1438510 Title: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety Status in PulseAudio: Unknown Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in bluez source package in Vivid: Won't Fix Status in pulseaudio source package in Vivid: Won't Fix Bug description: Just installed 15.04 fresh from the latest ISO (beta2). I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems to have regressed in functionality. In 14.10, I was able to set the output profile either to a2dp or hsp/hfp (telephony duplex). In 15.04, it only works in telephony duplex mode. I can't get high fidelity sound playback to work at all. This thread seems to be related, though the workaround within did not solve the problem for me: https://bbs.archlinux.org/viewtopic.php?id=194006 The bug is still present in 16.04 LTS and 16.10. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1438510/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1531925] Re: Can't connect Logitech K830 - no PIN prompt [LE]
** Tags added: papercuts2017 -- 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/1531925 Title: Can't connect Logitech K830 - no PIN prompt [LE] Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: Cannot connect a Logitech Illuminated Living Room keyboard to a device running bluez5. There are two versions of the keyboard, a unifying receiver version, and a Bluetooth version. The latter has a BT symbol on the 'del' key. To put the BT version in pairing mode, power on the keyboard, then briefly hold the FN and 'del' key together and release. A green LED at the top right of the keyboard should start flashing quickly. Once in pairing mode, the device will become visible on desktop using the BT settings UI, however it's *never* shown in the UI on a device running the latest Touch ( OTA9.1+ ). Note, this includes devices running a silo version of bluez 5.37, including both arale and krillin. On both devices, the keyboard *is* viewable using bluetoothctl. It should be noted that LE keyboard support on touch should be a considered a missing feature. Here's the reported attributes of the device from my macair running 15.10 + bluez 5.37: Device DF:08:A9:A0:13:93 Name: K830 Alias: K830 Appearance: 0x03c1 Icon: input-keyboard Paired: yes Trusted: no Blocked: no Connected: yes LegacyPairing: no UUID: Generic Access Profile (1800--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: Device Information (180a--1000-8000-00805f9b34fb) UUID: Battery Service (180f--1000-8000-00805f9b34fb) UUID: Human Interface Device (1812--1000-8000-00805f9b34fb) UUID: Vendor specific (0001--1000-8000-011f246d) Modalias: usb:v046DpB335d0010 From bluetoothctl on both my laptop and my desktop, I'm able to pair, trust and connect the device, and info reflects these changes, however the device never actually connects, it's LED remains blinking fast, and the keyboard cannot be used. Note, before pairing, I issued the command 'agent KeyboardOnly' and 'default-agent'. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1531925/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1398193] Re: The bluetooth headset can not control the media playback
** Tags added: papercuts2017 -- 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/1398193 Title: The bluetooth headset can not control the media playback Status in Canonical System Image: Triaged Status in bluez package in Ubuntu: Triaged Status in media-hub package in Ubuntu: Invalid Status in media-hub package in Ubuntu RTM: Invalid Bug description: [Preconditions] 1.The DUT pair with bluetooth headset [Procedures] 1.Play a video using the mediaplayer-app 2.Play/pause video by bluetooth headset [Expect results] The bluetooth headset can play/pause video [Actual results] The bluetooth headset can not control the video playback. [Reproduce] Always Same for audio playback To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1398193/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1546603] Re: Bluetooth mouse connects but doesn't work
** Tags added: papercuts2017 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1546603 Title: Bluetooth mouse connects but doesn't work Status in bluez package in Ubuntu: Confirmed Bug description: I have a bluetooth mouse that I can get to connect via the gnome bluetooth settings panel, but even after it's connected it doesn't move the pointer or register any clicks. the following shows up in the journal : $ $ journalctl -b 0 |grep bluetooth Feb 17 07:18:22 spiny bluetoothd[1009]: Bluetooth daemon 5.36 Feb 17 07:18:22 spiny bluetoothd[1009]: Starting SDP server Feb 17 07:18:22 spiny bluetoothd[1009]: Bluetooth management interface 1.10 initialized Feb 17 07:18:22 spiny bluetoothd[1009]: Failed to obtain handles for "Service Changed" characteristic Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register service Feb 17 07:18:22 spiny bluetoothd[1009]: Error adding Link Loss service Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register service Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register service Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register service Feb 17 07:18:22 spiny bluetoothd[1009]: Current Time Service could not be registered Feb 17 07:18:22 spiny bluetoothd[1009]: gatt-time-server: Input/output error (5) Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register service Feb 17 07:18:22 spiny bluetoothd[1009]: Not enough free handles to register service Feb 17 07:18:22 spiny bluetoothd[1009]: Sap driver initialization failed. Feb 17 07:18:22 spiny bluetoothd[1009]: sap-server: Operation not permitted (1) Feb 17 07:18:22 spiny NetworkManager[1062]: Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so) Feb 17 07:18:24 spiny bluetoothd[1009]: Endpoint registered: sender=:1.42 path=/MediaEndpoint/A2DPSource Feb 17 07:18:24 spiny bluetoothd[1009]: Endpoint registered: sender=:1.42 path=/MediaEndpoint/A2DPSink Feb 17 07:18:42 spiny bluetoothd[1009]: Endpoint registered: sender=:1.71 path=/MediaEndpoint/A2DPSource Feb 17 07:18:42 spiny bluetoothd[1009]: Endpoint registered: sender=:1.71 path=/MediaEndpoint/A2DPSink Feb 17 07:18:42 spiny bluetoothd[1009]: RFCOMM server failed for Headset Voice gateway: rfcomm_bind: Address already in use (98) Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** (gnome-control-center.real:2717): WARNING **: Ignoring launcher gufw (missing desktop file) Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** (gnome-control-center.real:2717): WARNING **: Ignoring launcher landscape-client-settings (missing desktop file) Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** (gnome-control-center.real:2717): WARNING **: Ignoring launcher language-selector (missing desktop file) Feb 17 07:18:52 spiny gnome-bluetooth-panel.desktop[2717]: ** (gnome-control-center.real:2717): WARNING **: Ignoring launcher ubuntuone-installer (missing desktop file) Feb 17 07:19:00 spiny gnome-bluetooth-panel.desktop[2717]: (gnome-control-center.real:2717): GLib-CRITICAL **: g_ascii_strdown: assertion 'str != NULL' failed Feb 17 07:19:01 spiny bluetoothd[1009]: No cache for F2:3F:5C:A1:F9:F7 Feb 17 07:19:06 spiny bluetoothd[1009]: Unable to register GATT service with handle 0x000c for device F2:3F:5C:A1:F9:F7 Feb 17 07:19:06 spiny bluetoothd[1009]: Unable to register GATT service with handle 0x001b for device F2:3F:5C:A1:F9:F7 Feb 17 07:19:06 spiny bluetoothd[1009]: Unable to register GATT service with handle 0x003f for device F2:3F:5C:A1:F9:F7 Feb 17 07:19:06 spiny bluetoothd[1009]: Report Map read failed: Attribute requires authentication before read/write Feb 17 07:19:06 spiny bluetoothd[1009]: Protocol Mode characteristic read failed: Attribute requires authentication before read/write Feb 17 07:19:06 spiny bluetoothd[1009]: HID Information read failed: Attribute requires authentication before read/write Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor failed: Attribute requires authentication before read/write Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor failed: Attribute requires authentication before read/write Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor failed: Attribute requires authentication before read/write Feb 17 07:19:06 spiny bluetoothd[1009]: Read Report Reference descriptor failed: Attribute requires authentication before read/write Feb 17 07:19:08 spiny gnome-bluetooth-panel.desktop[2717]: (gnome-control-center.real:2717): GLib-CRITICAL **: g_ascii_strdown: assertion 'str != NULL' failed Feb 17 07:19:08 spiny gnome-bluetooth-panel.desktop[2717]: (gnome-
[Touch-packages] [Bug 1283003] Re: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates
** Tags added: papercuts2017 -- 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/1283003 Title: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates Status in Blueman: New Status in blueman package in Ubuntu: Fix Released Status in bluez package in Ubuntu: Confirmed Status in gnome-bluetooth package in Ubuntu: Confirmed Bug description: Hi, I found a bug in Ubuntu 14.04 ! I tried to pair a bluetooth stereo headset (A2DP compatible). The pairing process goes well, but after that I can't select it on the audio preferences. When I select it, it only shows the last selected item options and don't do anything. (he should switch to the headset output). I must mention that it worked very well on Ubuntu 12.04. This bug can be in the bluetooth stack or in unity-control-center or maybe pulseaudio. I actually have no idea. To manage notifications about this bug go to: https://bugs.launchpad.net/blueman/+bug/1283003/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389336] Re: Use geoclue-2.0
** Changed in: webkitgtk (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 qtlocation-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1389336 Title: Use geoclue-2.0 Status in empathy package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in libunity-webapps package in Ubuntu: Confirmed Status in qtlocation-opensource-src package in Ubuntu: In Progress Status in ubuntu-geoip package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Fix Released Status in webkitgtk package in Ubuntu: Fix Released Status in qtlocation-opensource-src package in Debian: Fix Released Bug description: Geoclue2 (source package geoclue-2.0) is a separate, parallel- installable version of geoclue1 (source package geoclue). We will likely shortly have both in main (see MIR bug 1388294) and it would be great to be able to demote geoclue1 to universe and only support one version of the service. The packages associated with this bug all have a reverse depends on geoclue1 in some form or patches to remove support for geoclue-2.0 because it wasn't in main yet (e.g. gnome-settings-daemon). Porting from geoclue-1.0 to 2.0 apparently isn't terribly trivial. But we have at least six months to do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1389336/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389336] Re: Use geoclue-2.0
Humm, the qtlocation 5.6 did land to yakkety so marking this as fixed. ** Changed in: qtlocation-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 qtlocation-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1389336 Title: Use geoclue-2.0 Status in empathy package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in libunity-webapps package in Ubuntu: Confirmed Status in qtlocation-opensource-src package in Ubuntu: Fix Released Status in ubuntu-geoip package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Fix Released Status in webkitgtk package in Ubuntu: Fix Released Status in qtlocation-opensource-src package in Debian: Fix Released Bug description: Geoclue2 (source package geoclue-2.0) is a separate, parallel- installable version of geoclue1 (source package geoclue). We will likely shortly have both in main (see MIR bug 1388294) and it would be great to be able to demote geoclue1 to universe and only support one version of the service. The packages associated with this bug all have a reverse depends on geoclue1 in some form or patches to remove support for geoclue-2.0 because it wasn't in main yet (e.g. gnome-settings-daemon). Porting from geoclue-1.0 to 2.0 apparently isn't terribly trivial. But we have at least six months to do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1389336/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1651217] Re: package util-linux 2.29-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
You have a broken third party service installed named "mymacchanger" that you will need to remove. ** Changed in: util-linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1651217 Title: package util-linux 2.29-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in util-linux package in Ubuntu: Invalid Bug description: upgrade partial latest ubuntu zesty ProblemType: Package DistroRelease: Ubuntu 16.04 Package: util-linux 2.29-1ubuntu2 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.4 Architecture: amd64 Date: Mon Dec 19 20:01:37 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-07-07 (165 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: util-linux Title: package util-linux 2.29-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1651217/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1653721] [NEW] plantage de l'ordi n'importe quand
Public bug reported: Bonjour, Cela fait plusieurs mois que mon ordi, un ordinateur portable, plante de façon aléatoire et sans raisons apparentes. Que puis-je faire ? Merci, Ka ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-58.79-generic 4.4.35 Uname: Linux 4.4.0-58-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: Tue Jan 3 15:41:13 2017 DistUpgraded: 2016-12-17 18:35:04,265 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (L'exécution du processus fils « ./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type)) DistroCodename: xenial DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1558:5471] InstallationDate: Installed on 2016-01-05 (363 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Notebook W51XTU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-58-generic root=UUID=8bbbc809-ca02-489d-b6ea-29e39fcca521 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-12-17 (16 days ago) dmi.bios.date: 12/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W51XTU dmi.board.vendor: Notebook dmi.board.version: V1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd12/01/2014:svnNotebook:pnW51XTU:pvrNotApplicable:rvnNotebook:rnW51XTU:rvrV1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: W51XTU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook 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: Tue Jan 3 15:33:25 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 40180 vendor APP xserver.version: 2:1.18.4-0ubuntu0.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1653721 Title: plantage de l'ordi n'importe quand Status in xorg package in Ubuntu: New Bug description: Bonjour, Cela fait plusieurs mois que mon ordi, un ordinateur portable, plante de façon aléatoire et sans raisons apparentes. Que puis-je faire ? Merci, Ka ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-58.79-generic 4.4.35 Uname: Linux 4.4.0-58-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: Tue Jan 3 15:41:13 2017 DistUpgraded: 2016-12-17 18:35:04,265 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (L'exécution du processus fils « ./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type)) DistroCodename: xenial DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1558:5471] InstallationDate: Installed on 2016-01-05 (363 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd
[Touch-packages] [Bug 1653725] [NEW] lxc-android-config not starting on ubuntu-touch/staging/* xenial-based images after lxc upgrade
Public bug reported: 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. ** Affects: canonical-devices-system-image Importance: Critical Status: Confirmed ** Affects: lxc (Ubuntu) Importance: High Status: New ** Affects: lxc-android-config (Ubuntu) Importance: High Status: New ** Also affects: lxc (Ubuntu) Importance: Undecided Status: New ** Changed in: lxc (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/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 1653725] Re: lxc-android-config not starting on ubuntu-touch/staging/* xenial-based images after lxc upgrade
** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Importance: Undecided => Critical ** Changed in: canonical-devices-system-image Milestone: None => x1 ** Changed in: canonical-devices-system-image Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to 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 1653721] Re: plantage de l'ordi n'importe quand
Hello Karine ton laptop vient d'etre upgradé il y a quelques jours: est-ce que le problème existait avant (avec Trusty) ? Si non, il est temps de faire un nettoyage du system avec deborphan et bleachbit (en 'root' mais lit deux fois avant de cocher les cases). Au niveau materiel, est-ce que le(s) ventilateur(s) sont plus bruyant qu'à la normale ? Dans ce cas, note que la chaleur dégagée (fonctionnement normal) a besoin d'etre évacuée. Un nettoyage du ventilateur est peu etre nécessaire (enlever la poussière). Dans tous les cas ne pas obstruer les orifices de sortie de la chaleur, ni le poser sur une source de chaleur. D'autre part, le processeur est un 'atom' (faible puissance) et le système graphique n'est pas très puissant non plus; donc 'ubuntu' qui est assez gourmand, doit etre un peu trop demander à ce matériel (d'ou l'exces de chaleur entrainant le plantage). Un meilleur choix pour cette configuration serait d'installer 'Lubuntu' qui est beaucoup plus léger graphiquement, mais aussi esthétique. https://help.ubuntu.com/community/Installation/MinimalCD (choisir 32 bits iso) note: Si tu peut reporter en anglais, c'est très recommandé évidemment. note2: les logs n'ont rien enregistré d'anormal, d'ou la forte hypothèse de surchauffe, signifiant qu'il ne s'agit pas d'un 'bug'. note3: usuellement une demende d'aide se fait sur le(s) forum(s) avant de reporter un 'bug' ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1653721 Title: plantage de l'ordi n'importe quand Status in ubiquity package in Ubuntu: Incomplete Bug description: Bonjour, Cela fait plusieurs mois que mon ordi, un ordinateur portable, plante de façon aléatoire et sans raisons apparentes. Que puis-je faire ? Merci, Ka ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-58.79-generic 4.4.35 Uname: Linux 4.4.0-58-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: Tue Jan 3 15:41:13 2017 DistUpgraded: 2016-12-17 18:35:04,265 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (L'exécution du processus fils « ./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type)) DistroCodename: xenial DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1558:5471] InstallationDate: Installed on 2016-01-05 (363 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Notebook W51XTU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-58-generic root=UUID=8bbbc809-ca02-489d-b6ea-29e39fcca521 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-12-17 (16 days ago) dmi.bios.date: 12/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W51XTU dmi.board.vendor: Notebook dmi.board.version: V1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd12/01/2014:svnNotebook:pnW51XTU:pvrNotApplicable:rvnNotebook:rnW51XTU:rvrV1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: W51XTU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook 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: Tue Jan 3 15:33:25 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 40180 vend
[Touch-packages] [Bug 1653727] [NEW] infectado con arcivos cript desde windows seven
Public bug reported: dicsco compartido con windos seven ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-74.82-generic 3.19.8-ckt22 Uname: Linux 3.19.0-74-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.7 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 Date: Tue Jan 3 10:47:22 2017 DistUpgraded: 2016-09-22 00:37:21,126 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DpkgLog: GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Elitegroup Computer Systems Device [1019:3184] InstallationDate: Installed on 2015-02-16 (686 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) MachineType: ECS H61H2-CM ProcEnviron: LANGUAGE=es_VE:es PATH=(custom, no user) LANG=es_VE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-74-generic root=UUID=8426958f-20c8-4974-b61a-da41d6109d75 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to vivid on 2016-09-22 (103 days ago) dmi.bios.date: 08/12/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.name: H61H2-CM dmi.board.vendor: ECS dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: ECS dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd08/12/2011:svnECS:pnH61H2-CM:pvr:rvnECS:rnH61H2-CM:rvr1.0:cvnECS:ct3:cvr: dmi.product.name: H61H2-CM dmi.sys.vendor: ECS version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Tue Jan 3 10:33:48 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputSIGMACHIP Usb Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 59776 vendor LCD xserver.version: 2:1.17.1-0ubuntu3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 third-party-packages ubuntu vivid -- 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/1653727 Title: infectado con arcivos cript desde windows seven Status in xorg package in Ubuntu: New Bug description: dicsco compartido con windos seven ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-74.82-generic 3.19.8-ckt22 Uname: Linux 3.19.0-74-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.7 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 Date: Tue Jan 3 10:47:22 2017 DistUpgraded: 2016-09-22 00:37:21,126 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DpkgLog: GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Elitegroup Computer Systems Device [1019:3184] InstallationDate: Installed on 2015-02-16 (686 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) MachineType: ECS H61H2-CM ProcEnviron: LANGUAGE=es_VE:es PATH=(custom, no user) LANG=es_VE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-74-generic root=UUID=8426958f-20c8-4974-b61a-da41d6109d75 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to vivid on 2016-09-22 (103 days ago) dmi.bios.date: 08/12/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.4 dmi.board.name: H61H2-CM dmi.board.vendor: ECS dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: ECS dmi.modalias: dmi:bvnAmeri
[Touch-packages] [Bug 1653721] Re: plantage de l'ordi n'importe quand
Il semble que l'upgrade a été mal finalisé: " PostInstallScript ./xorg_fix_proprietary.py (L'exécution du processus fils « ./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type)) " note: une fraiche installation est toujours préférable à un 'upgrade' ou ce genre d'erreur peut etre problématique à résoudre. ** Package changed: xorg (Ubuntu) => ubiquity (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1653721 Title: plantage de l'ordi n'importe quand Status in ubiquity package in Ubuntu: Incomplete Bug description: Bonjour, Cela fait plusieurs mois que mon ordi, un ordinateur portable, plante de façon aléatoire et sans raisons apparentes. Que puis-je faire ? Merci, Ka ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-58.79-generic 4.4.35 Uname: Linux 4.4.0-58-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: Tue Jan 3 15:41:13 2017 DistUpgraded: 2016-12-17 18:35:04,265 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (L'exécution du processus fils « ./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type)) DistroCodename: xenial DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Atom Processor Z36xxx/Z37xxx Series Graphics & Display [1558:5471] InstallationDate: Installed on 2016-01-05 (363 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Notebook W51XTU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-58-generic root=UUID=8bbbc809-ca02-489d-b6ea-29e39fcca521 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-12-17 (16 days ago) dmi.bios.date: 12/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W51XTU dmi.board.vendor: Notebook dmi.board.version: V1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd12/01/2014:svnNotebook:pnW51XTU:pvrNotApplicable:rvnNotebook:rnW51XTU:rvrV1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: W51XTU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook 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: Tue Jan 3 15:33:25 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 40180 vendor APP xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1653721/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
I tested silo 2326 on desktop and frieza (both on xenial+overlay), and I
confirm that it fixes the issue. Thanks!
--
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:
In Progress
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 1651222] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gconf (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1651222 Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Confirmed Bug description: upgrade done with fail to install package gconf2 3.2.6ubuntu7 ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Mon Dec 19 13:13:09 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-11-19 (29 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to yakkety on 2016-12-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1651222/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 297143] Re: Xorg eats processor cycles while waiting for slow Internet
** Changed in: firefox Importance: Medium => 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/297143 Title: Xorg eats processor cycles while waiting for slow Internet Status in Mozilla Firefox: Confirmed Status in Mozilla Thunderbird: New Status in X.Org X server: Invalid Status in xorg package in Ubuntu: Invalid Bug description: Top shows that xorg is using >40% of CPU when there's no reason for it to be doing so. High CPU usage by xorg seems to be associated with slow/flaky Internet, e.g. slow sending of email with Thunderbird or slow loading of Launchpad in Firefox over a WiFi connection. It seems like xorg goes mental until it receives notification that the Internet transfer has completed successfully. At least Thunderbird and Firefox are involved, wget doesn't cause the same problem. I'm using an up-to-date Hardy (64-bit) on a Sony Vaio SZ650 (intel 965 graphics) and iwlagn / iwl4965 WiFi. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/297143/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
It’s not just duckduckgo, it’s an app-wide issue, as the second "+" is truncated for all search engines. ** Summary changed: - A typed "++" will be searched as "+" on DuckDuckGo + A typed "++" will be searched as "+" on all search engines ** Changed in: webbrowser-app (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1652292 Title: A typed "++" will be searched as "+" on all search engines Status in webbrowser-app package in Ubuntu: Confirmed 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 1650259] Re: [XPS 13 9350, Realtek ALC3246, Speaker, Internal] No sound at all after making sound test
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1650259 Title: [XPS 13 9350, Realtek ALC3246, Speaker, Internal] No sound at all after making sound test Status in pulseaudio package in Ubuntu: Confirmed Bug description: The problem is that there is no sound at the jack for the headphones. I was trying the sound test and after I change the surround option available in the sound test, the whole sound disappear and the default output device disappear in the Audio settings. Trying to fix an existing unresolved problem actually made it worse. Now I do not have any sound at all internal and from the jack for the headphone. By the way I tested a windows 10 live and the sound worked also from the jack for the headphones!!! Have not being using windows for the last 10 years I was impressed how they have improved. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jaki 2355 F pulseaudio CurrentDesktop: Unity Date: Thu Dec 15 12:41:55 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-06-25 (173 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06 ProcEnviron: LANGUAGE=it PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Audio interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jaki 2355 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [XPS 13 9350, Realtek ALC3246, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to xenial on 2016-09-07 (98 days ago) dmi.bios.date: 06/14/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.4 dmi.board.name: 0H67KH dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.4:bd06/14/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0H67KH:rvrA03:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1650259/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
** Changed in: webbrowser-app (Ubuntu) Importance: Undecided => High ** Changed in: webbrowser-app (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: webbrowser-app (Ubuntu) Status: Confirmed => In Progress -- 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 1652292] Re: A typed "++" will be searched as "+" on all search engines
** Branch linked: lp:~osomon/webbrowser-app/escape-all-html-entities-in- search-queries -- 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 1653725] Re: lxc-android-config not starting on ubuntu-touch/staging/* xenial-based images after lxc upgrade
What are the permissions on /var/lib/lxc on such devices? -- 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 1407928] Re: [phone] Does not auto-switch to available, known WiFi
Seems still be broken in 16.04.1 LTS Desktop. Note: The network I was experiencing this issue with is a hidden WLAN network. When using a visible WLAN network, the issue might not occur. Command line Workaround (see Bug #1542733) works for me to reconnect manually (tested only on Desktop) nmcli c up id But I would expect that a reconnect always takes place automatically and in a timely manner. But my experience is: Sometimes it works, but often it does not. Can someone confirm that it is related to a hidden WLAN network? -- 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/1407928 Title: [phone] Does not auto-switch to available, known WiFi Status in Canonical System Image: Confirmed Status in indicator-network package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Confirmed Bug description: This might not be the place for this bug, please reassign as appropriate. I was only able to reproduce this on mako/rtm, krillin/vivid seems to behave better (but I do remember the same issue there). Steps: * connect to a password-protected WiFi network * go out of range * make sure a GSM connection is established * go back in the WiFi range Expected: * phone connects to the known WiFi automatically Current: * phone does not connect to WiFi Please find attached network-test-session logs from when I toggled WiFi and Plane mode to get some data on the issue. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: indicator-network 0.5.1+15.04.20141215~rtm-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Tue Jan 6 12:01:55 2015 InstallationDate: Installed on 2014-12-18 (18 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141218-163635) SourcePackage: indicator-network UpgradeStatus: No upgrade log present (probably fresh install) indicator-network.log: Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered upstart.indicator-network.log: Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1407928/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1575757] Re: Can't install kernel-nfs-server inside lxc container
@Justin: The second entry isn't ignored, it will be used when the container starts. Though as Christian said, you do need to restart the container for this to apply. -- 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/1575757 Title: Can't install kernel-nfs-server inside lxc container Status in lxc package in Ubuntu: Confirmed Bug description: I'm trying to virtualize a package that depends on NFS by installing it in an LXC container. The commands sudo apt-get install nfs-kernel-server sudo lxc-create -n nfstest -t download -- -d ubuntu -r xenial -a amd64 sudo lxc-start -n nfstest sudo lxc-attach -n nfstest apt-get update sudo lxc-attach -n nfstest apt-get install nfs-kernel-server should install NFS server software inside the container, but instead fail with ... Not creating home directory `/var/lib/nfs'. nfs-utils.service is a disabled or a static unit, not starting it. Setting up nfs-kernel-server (1:1.2.8-9ubuntu12) ... A dependency job for nfs-server.service failed. See 'journalctl -xe' for details. nfs-server.service couldn't start. Creating config file /etc/exports with new version Creating config file /etc/default/nfs-kernel-server with new version A dependency job for nfs-server.service failed. See 'journalctl -xe' for details. invoke-rc.d: initscript nfs-kernel-server, action "start" failed. dpkg: error processing package nfs-kernel-server (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for libc-bin (2.23-0ubuntu3) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for systemd (229-4ubuntu4) ... Errors were encountered while processing: nfs-kernel-server E: Sub-process /usr/bin/dpkg returned an error code (1) sudo lxc-attach -n nfstest journalctl -xe reports: Apr 27 15:42:59 nfstest systemd[1]: Failed to mount NFSD configuration filesystem -- Subject: Unit proc-fs-nfsd.mount has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Unit proc-fs-nfsd.mount has failed. -- The result is failed. Presumably this is intended, and there is a way to configure lxc to allow running nfs servers inside it (there are rumors of success on the web), but https://help.ubuntu.com/lts/serverguide/lxc.html is silent on the issue, and doesn't even mention the word nfs. Likewise, https://help.ubuntu.com/lts/serverguide/network-file-system.html doesn't even mention lxc. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lxc 2.0.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 27 08:19:41 2016 InstallationDate: Installed on 2016-03-26 (32 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) PackageArchitecture: all SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1575757/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1575757] Re: Can't install kernel-nfs-server inside lxc container
stgraber@dakara:~$ lxc launch ubuntu:16.04 nfs -c security.privileged=true -c raw.lxc=lxc.aa_profile=unconfined Creating nfs Starting nfs stgraber@dakara:~$ lxc exec nfs bash root@nfs:~# apt install nfs-kernel-server Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: keyutils libnfsidmap2 libpython-stdlib libpython2.7-minimal libpython2.7-stdlib libtirpc1 nfs-common python python-minimal python2.7 python2.7-minimal rpcbind Suggested packages: watchdog python-doc python-tk python2.7-doc binutils binfmt-support The following NEW packages will be installed: keyutils libnfsidmap2 libpython-stdlib libpython2.7-minimal libpython2.7-stdlib libtirpc1 nfs-common nfs-kernel-server python python-minimal python2.7 python2.7-minimal rpcbind 0 upgraded, 13 newly installed, 0 to remove and 0 not upgraded. Need to get 4383 kB of archives. After this operation, 18.5 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 libnfsidmap2 amd64 0.25-5 [32.2 kB] Get:2 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libpython2.7-minimal amd64 2.7.12-1ubuntu0~16.04.1 [339 kB] Get:3 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 python2.7-minimal amd64 2.7.12-1ubuntu0~16.04.1 [1295 kB] Get:4 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 python-minimal amd64 2.7.11-1 [28.2 kB] Get:5 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 libpython2.7-stdlib amd64 2.7.12-1ubuntu0~16.04.1 [1884 kB] Get:6 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 python2.7 amd64 2.7.12-1ubuntu0~16.04.1 [224 kB] Get:7 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 libpython-stdlib amd64 2.7.11-1 [7656 B] Get:8 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 python amd64 2.7.11-1 [137 kB] Get:9 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 libtirpc1 amd64 0.2.5-1 [75.6 kB] Get:10 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 keyutils amd64 1.5.9-8ubuntu1 [47.1 kB] Get:11 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 rpcbind amd64 0.2.3-0.2 [40.3 kB] Get:12 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 nfs-common amd64 1:1.2.8-9ubuntu12 [185 kB] Get:13 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 nfs-kernel-server amd64 1:1.2.8-9ubuntu12 [88.0 kB] Fetched 4383 kB in 1s (3169 kB/s) Selecting previously unselected package libnfsidmap2:amd64. (Reading database ... 25465 files and directories currently installed.) Preparing to unpack .../libnfsidmap2_0.25-5_amd64.deb ... Unpacking libnfsidmap2:amd64 (0.25-5) ... Selecting previously unselected package libpython2.7-minimal:amd64. Preparing to unpack .../libpython2.7-minimal_2.7.12-1ubuntu0~16.04.1_amd64.deb ... Unpacking libpython2.7-minimal:amd64 (2.7.12-1ubuntu0~16.04.1) ... Selecting previously unselected package python2.7-minimal. Preparing to unpack .../python2.7-minimal_2.7.12-1ubuntu0~16.04.1_amd64.deb ... Unpacking python2.7-minimal (2.7.12-1ubuntu0~16.04.1) ... Selecting previously unselected package python-minimal. Preparing to unpack .../python-minimal_2.7.11-1_amd64.deb ... Unpacking python-minimal (2.7.11-1) ... Selecting previously unselected package libpython2.7-stdlib:amd64. Preparing to unpack .../libpython2.7-stdlib_2.7.12-1ubuntu0~16.04.1_amd64.deb ... Unpacking libpython2.7-stdlib:amd64 (2.7.12-1ubuntu0~16.04.1) ... Selecting previously unselected package python2.7. Preparing to unpack .../python2.7_2.7.12-1ubuntu0~16.04.1_amd64.deb ... Unpacking python2.7 (2.7.12-1ubuntu0~16.04.1) ... Selecting previously unselected package libpython-stdlib:amd64. Preparing to unpack .../libpython-stdlib_2.7.11-1_amd64.deb ... Unpacking libpython-stdlib:amd64 (2.7.11-1) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for mime-support (3.59ubuntu1) ... Setting up libpython2.7-minimal:amd64 (2.7.12-1ubuntu0~16.04.1) ... Setting up python2.7-minimal (2.7.12-1ubuntu0~16.04.1) ... Linking and byte-compiling packages for runtime python2.7... Setting up python-minimal (2.7.11-1) ... Selecting previously unselected package python. (Reading database ... 26221 files and directories currently installed.) Preparing to unpack .../python_2.7.11-1_amd64.deb ... Unpacking python (2.7.11-1) ... Selecting previously unselected package libtirpc1:amd64. Preparing to unpack .../libtirpc1_0.2.5-1_amd64.deb ... Unpacking libtirpc1:amd64 (0.2.5-1) ... Selecting previously unselected package keyutils. Preparing to unpack .../keyutils_1.5.9-8ubuntu1_amd64.deb ... Unpacking keyutils (1.5.9-8ubuntu1) ... Selecting previously unselected package rpcbind. Preparing to unpack .../rpcbind_0.2.3-0.2_amd64.deb ... Unpacking rpcbind (0.2.3-0.2) ... Selecting previously unselected package nfs-common. Preparing to unpack .../nfs-common_1%3a1.2.8-9ubuntu12_amd64.deb ... Unpacking nfs-common (1:1.2.8-9ubuntu12) ...
[Touch-packages] [Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings
patch filename and Subject: had 'string_escape=release', fixed to
'string_escape=replace'. Actual patch contents were correct and aren't
changed in this patch.
--
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/1647485
Title:
NVMe symlinks broken by devices with spaces in model or serial strings
Status in systemd:
New
Status in systemd package in Ubuntu:
New
Bug description:
[Impact]
After including the patch from bug 1642903, NVMe devices that include spaces
in their model or serial strings result in incorrect symlinks, e.g. if the
model string is "XYZ Corp NVMe drive" then instead of creating:
/dev/disk/by-id/nvme-XYZ Corp NVMe drive_SERIAL -> ../../nvme0n1
it creates:
/dev/disk/by-id/nvme-XYZ -> ../../nvme0n1
/dev/Corp -> nvme0n1
/dev/NVMe -> nvme0n1
/dev/drive_SERIAL -> nvme0n1
This is because of the way udev handles the SYMLINK value strings; by
default, it does not do any whitespace replacement. To enable
whitespace replacement of a symlink value, the rule must also include
OPTIONS+="string_escape=replace". This is done for 'md' and 'dm'
devices in their rules. However, there are no rules that actually
want to specify multiple symlinks, and defaulting to not replacing
whitespace makes no sense; instead, the default should be to replace
all whitespace in each symlink value, unless the rule explicitly
specifies OPTIONS+="string_escape=none".
[Test Case]
This assumes using udev with the patch from bug 1642903.
Without this patch, when using a NVMe drive that contains spaces in
its model and/or serial strings, check the /dev/disk/by-id/ directory.
It should contain a partially-correct symlink to the NVMe drive, with
the name up to the first space. All following space-separated parts
of the mode/serial string should have symlinks in the /dev/ directory.
This is the incorrect behavior.
With this patch, check the /dev/disk/by-id/ directory. It should
contain a fully-correct symlink to the NVMe drive, and no part of the
drive's model/serial number string should be a link in the /dev
directory.
An example of the correct/incorrect naming is in the Impact section.
There should be no other changes to any of the symlinks under /dev
before and after this patch. Typical locations for symlinks are
/dev/, /dev/disk/by-name/, /dev/disk/by-id/, /dev/disk/by-uuid/,
/dev/disk/by-label/
[Regression Potential]
Errors in udev rules can lead to an unbootable or otherwise completely
broken system if they unintentionally break or clobber existing
/dev/disks/ symlinks.
[Other Info]
This is also tracked with upstream systemd (udev) bug 4833:
https://github.com/systemd/systemd/issues/4833
Also note, this can be worked around in individual rules ONLY (i.e.
not fixed for all rules) by appending OPTIONS+="string_escape=replace"
to each of the NVMe rules with SYMLINK+="..." assignment, e.g.:
KERNEL=="nvme*[0-9]n*[0-9]", ENV{DEVTYPE}=="disk", ATTRS{model}=="?*",
ENV{ID_SERIAL_SHORT}=="?*",
ENV{ID_SERIAL}="$attr{model}_$env{ID_SERIAL_SHORT}", SYMLINK+="disk
/by-id/nvme-$env{ID_SERIAL}", OPTIONS+="string_escape=replace"
To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1647485/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1647485] Re: NVMe symlinks broken by devices with spaces in model or serial strings
** Patch removed: "workaround-use-string_escape-release-for-nvme-symlin.patch"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1647485/+attachment/4790906/+files/workaround-use-string_escape-release-for-nvme-symlin.patch
** Patch added: "workaround-use-string_escape-replace-for-nvme-symlin.patch"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1647485/+attachment/4799497/+files/workaround-use-string_escape-replace-for-nvme-symlin.patch
--
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/1647485
Title:
NVMe symlinks broken by devices with spaces in model or serial strings
Status in systemd:
New
Status in systemd package in Ubuntu:
New
Bug description:
[Impact]
After including the patch from bug 1642903, NVMe devices that include spaces
in their model or serial strings result in incorrect symlinks, e.g. if the
model string is "XYZ Corp NVMe drive" then instead of creating:
/dev/disk/by-id/nvme-XYZ Corp NVMe drive_SERIAL -> ../../nvme0n1
it creates:
/dev/disk/by-id/nvme-XYZ -> ../../nvme0n1
/dev/Corp -> nvme0n1
/dev/NVMe -> nvme0n1
/dev/drive_SERIAL -> nvme0n1
This is because of the way udev handles the SYMLINK value strings; by
default, it does not do any whitespace replacement. To enable
whitespace replacement of a symlink value, the rule must also include
OPTIONS+="string_escape=replace". This is done for 'md' and 'dm'
devices in their rules. However, there are no rules that actually
want to specify multiple symlinks, and defaulting to not replacing
whitespace makes no sense; instead, the default should be to replace
all whitespace in each symlink value, unless the rule explicitly
specifies OPTIONS+="string_escape=none".
[Test Case]
This assumes using udev with the patch from bug 1642903.
Without this patch, when using a NVMe drive that contains spaces in
its model and/or serial strings, check the /dev/disk/by-id/ directory.
It should contain a partially-correct symlink to the NVMe drive, with
the name up to the first space. All following space-separated parts
of the mode/serial string should have symlinks in the /dev/ directory.
This is the incorrect behavior.
With this patch, check the /dev/disk/by-id/ directory. It should
contain a fully-correct symlink to the NVMe drive, and no part of the
drive's model/serial number string should be a link in the /dev
directory.
An example of the correct/incorrect naming is in the Impact section.
There should be no other changes to any of the symlinks under /dev
before and after this patch. Typical locations for symlinks are
/dev/, /dev/disk/by-name/, /dev/disk/by-id/, /dev/disk/by-uuid/,
/dev/disk/by-label/
[Regression Potential]
Errors in udev rules can lead to an unbootable or otherwise completely
broken system if they unintentionally break or clobber existing
/dev/disks/ symlinks.
[Other Info]
This is also tracked with upstream systemd (udev) bug 4833:
https://github.com/systemd/systemd/issues/4833
Also note, this can be worked around in individual rules ONLY (i.e.
not fixed for all rules) by appending OPTIONS+="string_escape=replace"
to each of the NVMe rules with SYMLINK+="..." assignment, e.g.:
KERNEL=="nvme*[0-9]n*[0-9]", ENV{DEVTYPE}=="disk", ATTRS{model}=="?*",
ENV{ID_SERIAL_SHORT}=="?*",
ENV{ID_SERIAL}="$attr{model}_$env{ID_SERIAL_SHORT}", SYMLINK+="disk
/by-id/nvme-$env{ID_SERIAL}", OPTIONS+="string_escape=replace"
To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1647485/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1603815] Re: after updating to ubuntu 16.04 the network manager is unable to connect me to the wifi network. I can see the network, but once I introduce the password, it asks me
Can you check the password in network-manager view and edit it there? I think that the "wrong password - enter new"-dialog does not save the entered password and thus a reconnect with the old wrong password always fails. See also Bug #1542733 which I have experienced together with this one. -- 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/1603815 Title: after updating to ubuntu 16.04 the network manager is unable to connect me to the wifi network. I can see the network, but once I introduce the password, it asks me for the password after a few seconds and never connects. Status in network-manager package in Ubuntu: Confirmed Bug description: after updating to ubuntu 16.04 the network manager is unable to connect me to the wifi network. I can see the network, but once I introduce the password, it asks me for the password after a few seconds and never connects. I use different devices connected to the same wifi so it is not a problem of writting the wrong password. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 17 16:58:17 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-07-16 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.2.1 dev enp2s0 proto static metric 100 169.254.0.0/16 dev enp2s0 scope link metric 1000 192.168.2.0/24 dev enp2s0 proto kernel scope link src 192.168.2.242 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Conexión cableada 1 9e376788-1744-46de-a314-eeb07aad8c13 802-3-ethernet 1468789026 dom 17 jul 2016 16:57:06 CDT yes 4294966297no /org/freedesktop/NetworkManager/Settings/2 yes enp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 BELL419 28bd64cc4-181f-449b-95a3-edc74cf2a9a6 802-11-wireless 0 never yes 0 no /org/freedesktop/NetworkManager/Settings/1 no -- -- -- nmcli-dev: DEVICETYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp2s0ethernet connected /org/freedesktop/NetworkManager/Devices/1 Conexión cableada 1 9e376788-1744-46de-a314-eeb07aad8c13 /org/freedesktop/NetworkManager/ActiveConnection/1 wlp3s0b1 wifi disconnected /org/freedesktop/NetworkManager/Devices/0 -- ---- loloopback unmanaged /org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1603815/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390709] Re: Wifi doesn't reconnect after waking from sleep
As not everybody experiences this issue:
Is the issue related to the WLAN network being HIDDEN/VISIBLE?
--
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/1390709
Title:
Wifi doesn't reconnect after waking from sleep
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
Upgraded from 14.04 to 14.10. Before Wifi would reconnect after waking
up from sleep mode. After Update reconnect fails with wlan0: aborting
authentication with 1c:c6:3c:95:e7:74 by local choice (Reason:
3=DEAUTH_LEAVING).
I worked around this by killing wpa_supplicant with a script in
/etc/pm/sleep.d
#!/bin/sh
case "$1" in
thaw|resume)
{ killall wpa_supplicant ; } 2>/dev/null
;;
*)
;;
esac
exit $?
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: network-manager 0.9.8.8-0ubuntu28
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
Uname: Linux 3.16.0-24-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: KDE
Date: Sat Nov 8 11:43:15 2014
EcryptfsInUse: Yes
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2013-04-19 (567 days ago)
InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
IpRoute:
default via 192.168.138.251 dev wlan0 proto static
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
192.168.138.0/24 dev wlan0 proto kernel scope link src 192.168.138.143
metric 9
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to utopic on 2014-11-07 (0 days ago)
nmcli-nm:
RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE
WIFI WWAN-HARDWARE WWAN
running 0.9.8.8connected enabled enabled
enabledenabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1390709/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1652586] Re: package python3-cryptography 1.2.3-1ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am unable to reproduce the error message obtained above. I am fairly certain this is not a bug in python- cryptography and looks more like some local configuration issue. Since there isn't enough information in your report to differentiate between a local configuration problem and a bug in Ubuntu, I'm marking this bug as Incomplete. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New. If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community ** Changed in: python-cryptography (Ubuntu) Status: New => Invalid ** Changed in: python3-defaults (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1652586 Title: package python3-cryptography 1.2.3-1ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in python-cryptography package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Incomplete Bug description: i dont know. I'm new to ubuntu. It said ubuntu had an internal error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python3-cryptography 1.2.3-1ubuntu0.1 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 Date: Mon Dec 26 09:00:00 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-12-24 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: python-cryptography Title: package python3-cryptography 1.2.3-1ubuntu0.1 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/python-cryptography/+bug/1652586/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1638345] Re: avahi-daemon crashes multiple times an hour
Could somebody on the Desktop team take a look at this? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1638345 Title: avahi-daemon crashes multiple times an hour Status in avahi package in Ubuntu: Confirmed Bug description: Ever since upgrading to 16.10, avahi-daemon crashes multiple times an hour, leading to the prompt to report the issue to Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: avahi-daemon 0.6.32-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 1 10:48:35 2016 InstallationDate: Installed on 2016-07-08 (115 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: avahi UpgradeStatus: Upgraded to yakkety on 2016-10-31 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1638345/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1653635] Re: cmake unable to report INCLUDE_DIRS and LIBRARIES
** Tags added: xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libjsoncpp in Ubuntu.
https://bugs.launchpad.net/bugs/1653635
Title:
cmake unable to report INCLUDE_DIRS and LIBRARIES
Status in libjsoncpp package in Ubuntu:
New
Bug description:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.1 LTS
Release: 16.04
Codename: xenial
$ dpkg -l|grep libjsoncpp
ii libjsoncpp-dev:amd64 1.7.2-1
amd64library for reading and writing JSON for C++ (devel
files)
ii libjsoncpp1:amd64 1.7.2-1
amd64library for reading and writing JSON for C++
When try to use jsoncpp, the ${jsoncpp_INCLUDE_DIRS} and
${jsoncpp_LIBRARIES} fail to report.
CMakeLists.txt
cmake_minimum_required(VERSION 2.6.2)
project(jsoncpp_test)
find_package(jsoncpp REQUIRED)
message("FOUND CONFIG: ${jsoncpp_CONFIG}")
message("INCLUDE DIRS: ${jsoncpp_INCLUDE_DIRS}")
message("LIBRARIES: ${jsoncpp_LIBRARIES}")
The actual result is:
FOUND CONFIG: /usr/lib/x86_64-linux-gnu/cmake/jsoncpp/jsoncppConfig.cmake
INCLUDE DIRS:
LIBRARIES:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjsoncpp/+bug/1653635/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1638345] Re: avahi-daemon crashes multiple times an hour
** Changed in: avahi (Ubuntu) Assignee: (unassigned) => Canonical Desktop Team (canonical-desktop-team) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1638345 Title: avahi-daemon crashes multiple times an hour Status in avahi package in Ubuntu: Confirmed Bug description: Ever since upgrading to 16.10, avahi-daemon crashes multiple times an hour, leading to the prompt to report the issue to Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: avahi-daemon 0.6.32-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 1 10:48:35 2016 InstallationDate: Installed on 2016-07-08 (115 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: avahi UpgradeStatus: Upgraded to yakkety on 2016-10-31 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1638345/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
Maybe it's a already known information but I see that every string composed of an x number of '+' is searched as only "+". For example "+++" or "+++" or "++", them all are searched only as "+" -- 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 1390709] Re: Wifi doesn't reconnect after waking from sleep
FWIW, my networks were not hidden.
--
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/1390709
Title:
Wifi doesn't reconnect after waking from sleep
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
Upgraded from 14.04 to 14.10. Before Wifi would reconnect after waking
up from sleep mode. After Update reconnect fails with wlan0: aborting
authentication with 1c:c6:3c:95:e7:74 by local choice (Reason:
3=DEAUTH_LEAVING).
I worked around this by killing wpa_supplicant with a script in
/etc/pm/sleep.d
#!/bin/sh
case "$1" in
thaw|resume)
{ killall wpa_supplicant ; } 2>/dev/null
;;
*)
;;
esac
exit $?
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: network-manager 0.9.8.8-0ubuntu28
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
Uname: Linux 3.16.0-24-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: KDE
Date: Sat Nov 8 11:43:15 2014
EcryptfsInUse: Yes
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2013-04-19 (567 days ago)
InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1)
IpRoute:
default via 192.168.138.251 dev wlan0 proto static
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
192.168.138.0/24 dev wlan0 proto kernel scope link src 192.168.138.143
metric 9
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to utopic on 2014-11-07 (0 days ago)
nmcli-nm:
RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE
WIFI WWAN-HARDWARE WWAN
running 0.9.8.8connected enabled enabled
enabledenabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1390709/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1651944] Re: Kernel panic when we call pipework to setup virtual network for docker containers
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc2 ** Tags added: kernel-da-key ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Importance: Medium => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1651944 Title: Kernel panic when we call pipework to setup virtual network for docker containers Status in AppArmor: New Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I found a kernel panic issue when I was using pipework to config the network of a docker container on an x86 board with all-snap image. The issue is related to the auditing module of Linux kernel. So it should be an issue of pc-kernel-snap. I created a simple test snap to reproduce the issue and upload it to github. https://github.com/pliu6/docker-snap-test Software environment to reproduce the bug: #snap list Name Version Rev Developer Notes core 16.04.1 714 canonical - docker 1.11.2-956 canonical devmode dockertest 0.0.1 x12 devmode pc 16.04-0.8 9canonical - pc-kernel4.4.0-53-2 51 canonical - The log is below: [ 504.783341] BUG: unable to handle kernel paging request at fff3 [ 504.867186] IP: [] strlen+0x0/0x20 [ 504.926879] PGD 1e0d067 PUD 1e0f067 PMD 0 [ 504.976588] Oops: [#1] SMP [ 505.015690] Modules linked in: veth xt_addrtype br_netfilter ipt_REJECT nf_reject_ipv4 ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_comment xt_conntrack iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack bridge stp llc overlay aufs arc4 ath9k ath9k_common ath9k_hw ath mac80211 c fg80211 kvm_amd uas kvm irqbypass k10temp r8169 mii sp5100_tco mac_hid i2c_piix4 shpchp iptable_filter ip_tables ip6table_filter ip6_tables x_tables aut ofs4 mmc_block sdhci_acpi sdhci_pci sdhci virtio_scsi nls_iso8859_1 usb_storage ahci libahci [ 505.599099] CPU: 1 PID: 2414 Comm: snap-confine Not tainted 4.4.0-53-generic #74-Ubuntu [ 505.694977] Hardware name: PC Engines APU, BIOS SageBios_PCEngines_APU-45 04/05/2014 [ 505.787738] task: 880037637080 ti: 880061a7 task.ti: 880061a7 [ 505.877382] RIP: 0010:[] [] strlen+0x0/0x20 [ 505.966192] RSP: 0018:880061a73a20 EFLAGS: 00010246 [ 506.029835] RAX: 880061a73b20 RBX: fff3 RCX: [ 506.115320] RDX: 014e RSI: fff3 RDI: fff3 [ 506.200802] RBP: 880061a73a38 R08: 88005c835138 R09: 880061a73a94 [ 506.286283] R10: 000e R11: 88005c835131 R12: 88007aff0480 [ 506.371767] R13: 880037637080 R14: 81399fc0 R15: fff3 [ 506.457251] FS: 7fa9f36aa740() GS:88007df0() knlGS: [ 506.554170] CS: 0010 DS: ES: CR0: 80050033 [ 506.623014] CR2: fff3 CR3: 7853e000 CR4: 06e0 [ 506.708497] Stack: [ 506.732624] 81122a1a 88007aff0480 880061a73b00 880061a73a60 [ 506.822056] 8139a028 88007aff0480 880061a73b00 880037637080 [ 506.911490] 880061a73ad8 8136f088 812285c0 880061a73af0 [ 507.000926] Call Trace: [ 507.030263] [] ? audit_log_untrustedstring+0x1a/0x30 [ 507.109502] [] audit_cb+0x68/0x3f0 [ 507.170027] [] common_lsm_audit+0x1b8/0x740 [ 507.239910] [] ? alloc_inode+0x50/0x90 [ 507.304593] [] ? prepend_path+0xc6/0x2a0 [ 507.371358] [] aa_audit+0x5f/0x170 [ 507.431880] [] audit_mount+0x152/0x160 [ 507.496567] [] match_mnt_path_str+0x1dd/0x490 [ 507.568529] [] ? dentry_path+0x18/0x70 [ 507.633213] [] match_mnt+0xda/0x150 [ 507.694776] [] aa_bind_mount+0x100/0x180 [ 507.761540] [] wrap_apparmor_sb_mount+0x1c0/0x270 [ 507.837664] [] security_sb_mount+0x57/0x80 [ 507.906506] [] do_mount+0xab/0xde0 [ 507.967032] [] ? __kmalloc_track_caller+0x1b4/0x250 [ 508.045236] [] ? hrtimer_try_to_cancel+0xd1/0x130 [ 508.121361] [] ? memdup_user+0x42/0x70 [ 508.186042] [] SyS_mount+0x9f/0x100 [ 508.247607] [] entry_SYSCALL_64_fastpath+0x16/0x71 [ 508.324765] Code: 89 f8 48 89
[Touch-packages] [Bug 1653687] [NEW] No sound after some time
You have been subscribed to a public bug: Since a few weeks the sound is suddenly stopping on my laptop after some time. This can happen when I play music with Spotify, talk with Skype or play with Steam. The only way to get the sound back is to restart the computer. I tried to follow the sound troubleshooting procedure (https://help.ubuntu.com/community/SoundTroubleshootingProcedure) but it didn't solved my issue. Attached are the information generated by the also-info script and the pulseaudio log taken while the issue occurred. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- No sound after some time https://bugs.launchpad.net/bugs/1653687 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio 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 1652292] Re: A typed "++" will be searched as "+" on all search engines
Thanks Emanuele for the report and the investigation. I have submitted a trivial patch that fixes the issue, see the branch attached if you’re interested in the details. -- 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 1653687] Re: No sound after some time
** Package changed: ubuntu => pulseaudio (Ubuntu) -- 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/1653687 Title: No sound after some time Status in pulseaudio package in Ubuntu: New Bug description: Since a few weeks the sound is suddenly stopping on my laptop after some time. This can happen when I play music with Spotify, talk with Skype or play with Steam. The only way to get the sound back is to restart the computer. I tried to follow the sound troubleshooting procedure (https://help.ubuntu.com/community/SoundTroubleshootingProcedure) but it didn't solved my issue. Attached are the information generated by the also-info script and the pulseaudio log taken while the issue occurred. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1653687/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1651944] Re: Kernel panic when we call pipework to setup virtual network for docker containers
Ignore the request to test the upstream kernel, for the moment. In this case the apparmor code that is in the trace does not exist upstream. Instead could you test the kernel in http://people.canonical.com/~jj/lp1648143/ While listed as being for bug 1648143, it contains several fixes including a fix to the bind mount code. That will be pushed up to the ubuntu kernel this week. If this still exhibits the fault then, please test the upstream kernel to verify that the bug is indeed in apparmor, and not being triggered else where and showing up in apparmor. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1651944 Title: Kernel panic when we call pipework to setup virtual network for docker containers Status in AppArmor: New Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I found a kernel panic issue when I was using pipework to config the network of a docker container on an x86 board with all-snap image. The issue is related to the auditing module of Linux kernel. So it should be an issue of pc-kernel-snap. I created a simple test snap to reproduce the issue and upload it to github. https://github.com/pliu6/docker-snap-test Software environment to reproduce the bug: #snap list Name Version Rev Developer Notes core 16.04.1 714 canonical - docker 1.11.2-956 canonical devmode dockertest 0.0.1 x12 devmode pc 16.04-0.8 9canonical - pc-kernel4.4.0-53-2 51 canonical - The log is below: [ 504.783341] BUG: unable to handle kernel paging request at fff3 [ 504.867186] IP: [] strlen+0x0/0x20 [ 504.926879] PGD 1e0d067 PUD 1e0f067 PMD 0 [ 504.976588] Oops: [#1] SMP [ 505.015690] Modules linked in: veth xt_addrtype br_netfilter ipt_REJECT nf_reject_ipv4 ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_comment xt_conntrack iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack bridge stp llc overlay aufs arc4 ath9k ath9k_common ath9k_hw ath mac80211 c fg80211 kvm_amd uas kvm irqbypass k10temp r8169 mii sp5100_tco mac_hid i2c_piix4 shpchp iptable_filter ip_tables ip6table_filter ip6_tables x_tables aut ofs4 mmc_block sdhci_acpi sdhci_pci sdhci virtio_scsi nls_iso8859_1 usb_storage ahci libahci [ 505.599099] CPU: 1 PID: 2414 Comm: snap-confine Not tainted 4.4.0-53-generic #74-Ubuntu [ 505.694977] Hardware name: PC Engines APU, BIOS SageBios_PCEngines_APU-45 04/05/2014 [ 505.787738] task: 880037637080 ti: 880061a7 task.ti: 880061a7 [ 505.877382] RIP: 0010:[] [] strlen+0x0/0x20 [ 505.966192] RSP: 0018:880061a73a20 EFLAGS: 00010246 [ 506.029835] RAX: 880061a73b20 RBX: fff3 RCX: [ 506.115320] RDX: 014e RSI: fff3 RDI: fff3 [ 506.200802] RBP: 880061a73a38 R08: 88005c835138 R09: 880061a73a94 [ 506.286283] R10: 000e R11: 88005c835131 R12: 88007aff0480 [ 506.371767] R13: 880037637080 R14: 81399fc0 R15: fff3 [ 506.457251] FS: 7fa9f36aa740() GS:88007df0() knlGS: [ 506.554170] CS: 0010 DS: ES: CR0: 80050033 [ 506.623014] CR2: fff3 CR3: 7853e000 CR4: 06e0 [ 506.708497] Stack: [ 506.732624] 81122a1a 88007aff0480 880061a73b00 880061a73a60 [ 506.822056] 8139a028 88007aff0480 880061a73b00 880037637080 [ 506.911490] 880061a73ad8 8136f088 812285c0 880061a73af0 [ 507.000926] Call Trace: [ 507.030263] [] ? audit_log_untrustedstring+0x1a/0x30 [ 507.109502] [] audit_cb+0x68/0x3f0 [ 507.170027] [] common_lsm_audit+0x1b8/0x740 [ 507.239910] [] ? alloc_inode+0x50/0x90 [ 507.304593] [] ? prepend_path+0xc6/0x2a0 [ 507.371358] [] aa_audit+0x5f/0x170 [ 507.431880] [] audit_mount+0x152/0x160 [ 507.496567] [] match_mnt_path_str+0x1dd/0x490 [ 507.568529] [] ? dentry_path+0x18/0x70 [ 507.633213] [] match_mnt+0xda/0x150 [ 507.694776] [] aa_bind_mount+0x100/0x180 [ 507.761540] [] wrap_apparmor_sb_mount+0x1c0/0x270 [ 507.837664] [] security_sb_mount+0x57/0x80 [ 507.906506] [] do_mount+0xab/0xde0 [ 507.967032] [] ? __kmalloc_track_caller+0x1b4/0x250 [ 508.045236] [] ? hrtimer_try_to_cancel+0xd1/0x130 [ 508.121361] [] ? memdup_user+0x42/0x70 [ 508.186042] [] SyS_mount+0x9f/0x100 [ 508.247607] [] entry_SYSCALL_64_fastpath+0x16/0x71 [ 508.324765] Code: 89 f8 48 89 e5 f6 82 a0 05 a5 81 20 74 10 48 83 c0 01 0f b6 10 f6 82 a0 05 a5 81 20 75 f0 5d c3 90 66 2e 0f 1f 84 00 00 00 00 00
[Touch-packages] [Bug 1651944] Re: Kernel panic when we call pipework to setup virtual network for docker containers
Actually, this bug was found with Ubuntu all-snap version. So I am not able to try the kernel.deb. Could you tell me how to get the latest version of the kernel snap for 16.04? Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1651944 Title: Kernel panic when we call pipework to setup virtual network for docker containers Status in AppArmor: New Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I found a kernel panic issue when I was using pipework to config the network of a docker container on an x86 board with all-snap image. The issue is related to the auditing module of Linux kernel. So it should be an issue of pc-kernel-snap. I created a simple test snap to reproduce the issue and upload it to github. https://github.com/pliu6/docker-snap-test Software environment to reproduce the bug: #snap list Name Version Rev Developer Notes core 16.04.1 714 canonical - docker 1.11.2-956 canonical devmode dockertest 0.0.1 x12 devmode pc 16.04-0.8 9canonical - pc-kernel4.4.0-53-2 51 canonical - The log is below: [ 504.783341] BUG: unable to handle kernel paging request at fff3 [ 504.867186] IP: [] strlen+0x0/0x20 [ 504.926879] PGD 1e0d067 PUD 1e0f067 PMD 0 [ 504.976588] Oops: [#1] SMP [ 505.015690] Modules linked in: veth xt_addrtype br_netfilter ipt_REJECT nf_reject_ipv4 ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_comment xt_conntrack iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack bridge stp llc overlay aufs arc4 ath9k ath9k_common ath9k_hw ath mac80211 c fg80211 kvm_amd uas kvm irqbypass k10temp r8169 mii sp5100_tco mac_hid i2c_piix4 shpchp iptable_filter ip_tables ip6table_filter ip6_tables x_tables aut ofs4 mmc_block sdhci_acpi sdhci_pci sdhci virtio_scsi nls_iso8859_1 usb_storage ahci libahci [ 505.599099] CPU: 1 PID: 2414 Comm: snap-confine Not tainted 4.4.0-53-generic #74-Ubuntu [ 505.694977] Hardware name: PC Engines APU, BIOS SageBios_PCEngines_APU-45 04/05/2014 [ 505.787738] task: 880037637080 ti: 880061a7 task.ti: 880061a7 [ 505.877382] RIP: 0010:[] [] strlen+0x0/0x20 [ 505.966192] RSP: 0018:880061a73a20 EFLAGS: 00010246 [ 506.029835] RAX: 880061a73b20 RBX: fff3 RCX: [ 506.115320] RDX: 014e RSI: fff3 RDI: fff3 [ 506.200802] RBP: 880061a73a38 R08: 88005c835138 R09: 880061a73a94 [ 506.286283] R10: 000e R11: 88005c835131 R12: 88007aff0480 [ 506.371767] R13: 880037637080 R14: 81399fc0 R15: fff3 [ 506.457251] FS: 7fa9f36aa740() GS:88007df0() knlGS: [ 506.554170] CS: 0010 DS: ES: CR0: 80050033 [ 506.623014] CR2: fff3 CR3: 7853e000 CR4: 06e0 [ 506.708497] Stack: [ 506.732624] 81122a1a 88007aff0480 880061a73b00 880061a73a60 [ 506.822056] 8139a028 88007aff0480 880061a73b00 880037637080 [ 506.911490] 880061a73ad8 8136f088 812285c0 880061a73af0 [ 507.000926] Call Trace: [ 507.030263] [] ? audit_log_untrustedstring+0x1a/0x30 [ 507.109502] [] audit_cb+0x68/0x3f0 [ 507.170027] [] common_lsm_audit+0x1b8/0x740 [ 507.239910] [] ? alloc_inode+0x50/0x90 [ 507.304593] [] ? prepend_path+0xc6/0x2a0 [ 507.371358] [] aa_audit+0x5f/0x170 [ 507.431880] [] audit_mount+0x152/0x160 [ 507.496567] [] match_mnt_path_str+0x1dd/0x490 [ 507.568529] [] ? dentry_path+0x18/0x70 [ 507.633213] [] match_mnt+0xda/0x150 [ 507.694776] [] aa_bind_mount+0x100/0x180 [ 507.761540] [] wrap_apparmor_sb_mount+0x1c0/0x270 [ 507.837664] [] security_sb_mount+0x57/0x80 [ 507.906506] [] do_mount+0xab/0xde0 [ 507.967032] [] ? __kmalloc_track_caller+0x1b4/0x250 [ 508.045236] [] ? hrtimer_try_to_cancel+0xd1/0x130 [ 508.121361] [] ? memdup_user+0x42/0x70 [ 508.186042] [] SyS_mount+0x9f/0x100 [ 508.247607] [] entry_SYSCALL_64_fastpath+0x16/0x71 [ 508.324765] Code: 89 f8 48 89 e5 f6 82 a0 05 a5 81 20 74 10 48 83 c0 01 0f b6 10 f6 82 a0 05 a5 81 20 75 f0 5d c3 90 66 2e 0f 1f 84 00 00 00 00 00 <8 0> 3f 00 55 48 89 e5 74 11 48 89 f8 48 83 c0 01 80 38 00 75 f7 [ 508.564156] RIP [] strlen+0x0/0x20 [ 508.624889] RSP [ 508.96] CR2: fff3 [ 508.706425] ---[ end trace 9a8196367a1a3630 ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1651944/+subscriptions -- Mailing list: https://launchpad.n
[Touch-packages] [Bug 1651433] Re: bluetooth mouse random disconnects
It looks like on OEM systems, we tweak /etc/bluetooth/main.conf by adding "AutoEnable=true". Can you check what that's set to on your system? -- 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 1570749] Re: Upgrade to 11.7 from May 2016
Yakkety and Xenial have already been released. Packages do not get updated after release. Specific critcal bugs can be fixed through the Stable Release Updates (SRU) process. However, in the case of libav, this package was removed from Ubuntu after the vivid release, in favour of ffmpeg. Perhaps you can use that library instead? ** Changed in: libav (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1570749 Title: Upgrade to 11.7 from May 2016 Status in libav package in Ubuntu: Invalid Bug description: Please, upgrade to 11.6 from February 2016, see https://libav.org/ and https://git.libav.org/?p=libav.git;a=blob;f=Changelog;hb=refs/tags/v11.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1570749/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630860] Re: [HDA-Intel - HDA Intel PCH, playback] Playback problem
As Paul I have this issue with a Lenovo P50 and the Dock. Kernel is 4.4.0-57-generic with a Ubuntu 16.04.1 LTS. Does anybody know when to expect a solution to this problem? It's really annoying working under those conditions! -- 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/1630860 Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Debian: New Bug description: Lenovo Thinkpad P50 with docking station Issues: Headphone jack on station not detected; no sound (works without docking station) Issues: Sound via HDMI on station not detected; no sound (works without docking station) Since all outputs are routed via the Thunderbolt chip, my guess is that it's related to the pin setup (lenovo-dock) in Alsa. Without the dock, everything works, headphone/mic jack on the P50 itself is hotplug (switches from speaker to headphones right away). Screenshots (with and without docking station) attached. Thanks and LG, Wolfgang ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-38.57~14.04.1-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: symap_custom_dkms_x86_64 nvidia ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wjl2943 F pulseaudio /dev/snd/controlC0: wjl2943 F pulseaudio CurrentDesktop: Unity Date: Wed Oct 5 14:14:02 2016 InstallationDate: Installed on 2016-09-10 (24 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: HDA NVidia - HDA NVidia Symptom_Type: Only some of outputs are working Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET52W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EQS1EH0B dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET52W(1.26):bd05/10/2016:svnLENOVO:pn20EQS1EH0B:pvrThinkPadP50:rvnLENOVO:rn20EQS1EH0B:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20EQS1EH0B dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO mtime.conffile..etc.modprobe.d.alsa.base.conf: 2016-10-04T12:48:36.270399 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1630860/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1652288] Re: indicator-network uses urfkill on desktop if installed, breaking wifi drivers
This bug was fixed in the package indicator-network - 0.9.0+17.04.20161223.3-0ubuntu1 --- indicator-network (0.9.0+17.04.20161223.3-0ubuntu1) zesty; urgency=medium [ Dimitri John Ledkov ] * Remove xdg autolaunch desktop files (LP: #1648360) [ Pete Woods ] * Use plain NetworkManager radio control on desktop, URFKill on phablet (LP: #1652288) -- Pete Woods Fri, 23 Dec 2016 13:58:36 + ** Changed in: indicator-network (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 indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1652288 Title: indicator-network uses urfkill on desktop if installed, breaking wifi drivers Status in indicator-network package in Ubuntu: Fix Released Bug description: THe indicator needs to determine at startup if we are in a urfkill- supported environment or not, and behave accordingly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1652288/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1651201] Re: package vim-runtime 2:7.4.1689-3ubuntu1.2 failed to install/upgrade: trying to overwrite '/usr/share/man/fr/man1/vimtutor.1.gz', which is also in package vim 2016121
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1651201 Title: package vim-runtime 2:7.4.1689-3ubuntu1.2 failed to install/upgrade: trying to overwrite '/usr/share/man/fr/man1/vimtutor.1.gz', which is also in package vim 20161216-1 Status in vim package in Ubuntu: New Bug description: I have installed vim from scratch using checkinstall (instead of make install) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: vim-runtime 2:7.4.1689-3ubuntu1.2 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 Date: Sat Dec 17 03:19:43 2016 DuplicateSignature: package:vim-runtime:2:7.4.1689-3ubuntu1.2 Unpacking vim-common (2:7.4.1689-3ubuntu1.2) ... dpkg: error processing archive /var/cache/apt/archives/vim-common_2%3a7.4.1689-3ubuntu1.2_amd64.deb (--unpack): trying to overwrite '/usr/share/man/fr/man1/vimdiff.1.gz', which is also in package vim 20161216-1 ErrorMessage: trying to overwrite '/usr/share/man/fr/man1/vimtutor.1.gz', which is also in package vim 20161216-1 InstallationDate: Installed on 2016-12-16 (2 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: vim Title: package vim-runtime 2:7.4.1689-3ubuntu1.2 failed to install/upgrade: trying to overwrite '/usr/share/man/fr/man1/vimtutor.1.gz', which is also in package vim 20161216-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1651201/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1648360] Re: indicator-network, under systemd, starts on u7 when it shouldn't
This bug was fixed in the package indicator-network - 0.9.0+17.04.20161223.3-0ubuntu1 --- indicator-network (0.9.0+17.04.20161223.3-0ubuntu1) zesty; urgency=medium [ Dimitri John Ledkov ] * Remove xdg autolaunch desktop files (LP: #1648360) [ Pete Woods ] * Use plain NetworkManager radio control on desktop, URFKill on phablet (LP: #1652288) -- Pete Woods Fri, 23 Dec 2016 13:58:36 + ** Changed in: indicator-network (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 indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1648360 Title: indicator-network, under systemd, starts on u7 when it shouldn't Status in indicator-network package in Ubuntu: Fix Released Bug description: indicator-network is meant to not start on u7, it should only be wanted by u8 session. $ cat /usr/lib/systemd/user/indicator-network.service [Unit] Description=Indicator Network Backend PartOf=graphical-session.target After=indicators-pre.target Wants=indicator-network-secret-agent.service [Service] ExecStart=/usr/lib/x86_64-linux-gnu/indicator-network/indicator-network-service Restart=on-failure vs in upstart user session: pre-start script # NOTE: Only used on Unity8 today, not 7 # Still allows manual starting if [ "x$DESKTOP_SESSION" != "xubuntu-touch" ] && [ "x$DESKTOP_SESSION" != "xunity8" ]; then if [ "x$UPSTART_EVENTS" != "x" ] ; then stop; exit 0 fi fi end script ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: indicator-network 0.8.0+17.04.2016-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Thu Dec 8 09:54:18 2016 InstallationDate: Installed on 2016-01-26 (317 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160125) SourcePackage: indicator-network UpgradeStatus: Upgraded to zesty on 2016-12-05 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1648360/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1652785] Re: package unattended-upgrades 0.90ubuntu0.2 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 unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1652785 Title: package unattended-upgrades 0.90ubuntu0.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in unattended-upgrades package in Ubuntu: New Bug description: Was playing a game in fullscreen mode while the updates ran, in case that affects things. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90ubuntu0.2 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic i686 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: i386 Date: Tue Dec 27 09:26:49 2016 DuplicateSignature: package:unattended-upgrades:0.90ubuntu0.2 Installing new version of config file /etc/logrotate.d/unattended-upgrades ... frontend: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. dpkg: error processing package unattended-upgrades (--configure): subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-09-04 (844 days ago) InstallationMedia: It PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: unattended-upgrades Title: package unattended-upgrades 0.90ubuntu0.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-12-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1652785/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1652228] Re: package gir1.2-gst-plugins-base-1.0 1.2.4-1~ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attemptin
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1652228 Title: package gir1.2-gst-plugins-base-1.0 1.2.4-1~ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in gst-plugins-base1.0 package in Ubuntu: New Bug description: I already try to reinstall the package ProblemType: Package DistroRelease: Ubuntu 14.04 Package: gir1.2-gst-plugins-base-1.0 1.2.4-1~ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 Uname: Linux 3.13.0-106-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook ApportVersion: 2.14.1-0ubuntu3.23 AptOrdering: gir1.2-gst-plugins-base-1.0: Configure Architecture: amd64 Date: Thu Dec 22 07:53:26 2016 DpkgTerminalLog: dpkg: error processing package gir1.2-gst-plugins-base-1.0 (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration DuplicateSignature: package:gir1.2-gst-plugins-base-1.0:1.2.4-1~ubuntu2:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2014-07-29 (878 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: gst-plugins-base1.0 Title: package gir1.2-gst-plugins-base-1.0 1.2.4-1~ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base1.0/+bug/1652228/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1652516] Re: package linux-image-4.4.0-57-generic 4.4.0-57.78 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 139
** 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/1652516 Title: package linux-image-4.4.0-57-generic 4.4.0-57.78 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 139 Status in initramfs-tools package in Ubuntu: New Bug description: I DON'T KNOW ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-57-generic 4.4.0-57.78 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jayachitra 1514 F pulseaudio Date: Sun Dec 25 19:52:55 2016 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 139 HibernationDevice: RESUME=UUID=73e2f5bd-93f6-4c8f-aec4-6090372de0b4 InstallationDate: Installed on 2016-07-28 (149 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: enp2s0no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 003: ID 0458:003a KYE Systems Corp. (Mouse Systems) NetScroll+ Mini Traveler / Genius NetScroll 120 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 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic root=UUID=1aba02be-eab0-416e-8f86-52396085f8a8 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.2 RfKill: SourcePackage: initramfs-tools Title: package linux-image-4.4.0-57-generic 4.4.0-57.78 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: HOH6110H.86A.0010.2012.0424.1632 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH61HO dmi.board.vendor: Intel Corporation dmi.board.version: AAG62445-102 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrHOH6110H.86A.0010.2012.0424.1632:bd04/24/2012:svn:pn:pvr:rvnIntelCorporation:rnDH61HO:rvrAAG62445-102:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1652516/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1650981] Re: package libsystemd0:amd64 231-9ubuntu2 failed to install/upgrade: package libsystemd0:amd64 231-9ubuntu2 cannot be configured because libsystemd0:i386 is at a differ
** Tags removed: need-duplicate-check -- 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/1650981 Title: package libsystemd0:amd64 231-9ubuntu2 failed to install/upgrade: package libsystemd0:amd64 231-9ubuntu2 cannot be configured because libsystemd0:i386 is at a different version (231-9ubuntu1) Status in systemd package in Ubuntu: New Bug description: during routine aptitude upgrade ubuntu 16.10 libsystemd 231-9ubuntu2 ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libsystemd0:amd64 231-9ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Sun Dec 18 15:08:03 2016 DuplicateSignature: package:libsystemd0:amd64:231-9ubuntu2 Unpacking libsystemd0:amd64 (231-9ubuntu2) over (231-9ubuntu1) ... dpkg: error processing package libsystemd0:amd64 (--configure): package libsystemd0:amd64 231-9ubuntu2 cannot be configured because libsystemd0:i386 is at a different version (231-9ubuntu1) ErrorMessage: package libsystemd0:amd64 231-9ubuntu2 cannot be configured because libsystemd0:i386 is at a different version (231-9ubuntu1) InstallationDate: Installed on 2016-07-23 (148 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.3 SourcePackage: systemd Title: package libsystemd0:amd64 231-9ubuntu2 failed to install/upgrade: package libsystemd0:amd64 231-9ubuntu2 cannot be configured because libsystemd0:i386 is at a different version (231-9ubuntu1) UpgradeStatus: Upgraded to yakkety on 2016-10-14 (65 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1650981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1651222] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1632415 *** https://bugs.launchpad.net/bugs/1632415 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1632415, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1632415 package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1651222 Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Confirmed Bug description: upgrade done with fail to install package gconf2 3.2.6ubuntu7 ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Mon Dec 19 13:13:09 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-11-19 (29 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to yakkety on 2016-12-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1651222/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1653571] Re: package python2.7 2.7.6-8ubuntu0.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1653571 Title: package python2.7 2.7.6-8ubuntu0.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139 Status in python2.7 package in Ubuntu: New Bug description: a ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python2.7 2.7.6-8ubuntu0.3 ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30 Uname: Linux 3.13.0-74-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Tue Jan 3 08:59:18 2017 DuplicateSignature: package:python2.7:2.7.6-8ubuntu0.3:subprocess installed post-installation script returned error exit status 139 ErrorMessage: subprocess installed post-installation script returned error exit status 139 InstallationDate: Installed on 2016-01-07 (361 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: python2.7 Title: package python2.7 2.7.6-8ubuntu0.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1653571/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1652586] Re: package python3-cryptography 1.2.3-1ubuntu0.1 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 python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1652586 Title: package python3-cryptography 1.2.3-1ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in python-cryptography package in Ubuntu: Invalid Status in python3-defaults package in Ubuntu: Incomplete Bug description: i dont know. I'm new to ubuntu. It said ubuntu had an internal error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python3-cryptography 1.2.3-1ubuntu0.1 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 Date: Mon Dec 26 09:00:00 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-12-24 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: python-cryptography Title: package python3-cryptography 1.2.3-1ubuntu0.1 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/python-cryptography/+bug/1652586/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1652927] Re: package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de s
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1652927 Title: package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed to install/upgrade: el subproceso instalado el script post- installation devolvió el código de salida de error 1 Status in unity-scopes-api package in Ubuntu: New Bug description: Second error by actualization from 16.04 to 16.10. First system reboot by terminal. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Wed Dec 28 12:15:32 2016 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2016-04-21 (250 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.3 SourcePackage: unity-scopes-api Title: package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 UpgradeStatus: Upgraded to yakkety on 2016-12-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1652927/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1653096] Re: package systemd 229-4ubuntu13 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1653096 Title: package systemd 229-4ubuntu13 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2 Status in systemd package in Ubuntu: Confirmed Bug description: The error message appears after the desktop loads on Ubuntu 16.04 which I recently upgraded from 15.10. The system asks me if I want to report the problem, other than that, I know nothing. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu13 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic i686 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: i386 Date: Tue Dec 13 22:09:56 2016 DpkgTerminalLog: Preparing to unpack .../systemd_229-4ubuntu12_i386.deb ... De-configuring udev (225-1ubuntu9.1) ... dpkg: error processing archive /var/cache/apt/archives/systemd_229-4ubuntu12_i386.deb (--unpack): subprocess installed pre-removal script returned error exit status 2 DuplicateSignature: package:systemd:229-4ubuntu13 De-configuring udev (225-1ubuntu9.1) ... dpkg: error processing archive /var/cache/apt/archives/systemd_229-4ubuntu12_i386.deb (--unpack): subprocess installed pre-removal script returned error exit status 2 ErrorMessage: subprocess installed pre-removal script returned error exit status 2 InstallationDate: Installed on 2016-01-03 (360 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release i386 (20151021) MachineType: Acer TravelMate 5320 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic root=UUID=63b32cbb-033e-4b56-8773-0d6ab4127c58 ro noquiet nosplash RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /etc/systemd/system/display-manager.service → /lib/systemd/system/display-manager.service.d/xdiagnose.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 3 overridden configuration files found. Title: package systemd 229-4ubuntu13 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2 UpgradeStatus: Upgraded to xenial on 2016-12-13 (15 days ago) dmi.bios.date: 07/03/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.35 dmi.board.name: Columbia dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.asset.tag: None dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.35:bd07/03/2008:svnAcer:pnTravelMate5320:pvr0100:rvnAcer:rnColumbia:rvrRev:cvnAcer:ct10:cvrN/A: dmi.product.name: TravelMate 5320 dmi.product.version: 0100 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1653096/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1653566] 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/1653566 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: after installing libguestfs-tools ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8.7 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic i686 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: i386 Date: Tue Jan 3 01:11:46 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-12-22 (11 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) 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/1653566/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1652314] Re: package fontconfig 2.11.94-0ubuntu1.1 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 fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1652314 Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in fontconfig package in Ubuntu: New Bug description: ARM banana pi platform ProblemType: Package DistroRelease: Ubuntu 16.04 Package: fontconfig 2.11.94-0ubuntu1.1 Uname: Linux 3.4.39-BPI-M3-Kernel armv7l ApportVersion: 2.20.1-0ubuntu2.4 Architecture: armhf Date: Thu Dec 22 09:58:28 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: fontconfig Title: package fontconfig 2.11.94-0ubuntu1.1 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/fontconfig/+bug/1652314/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1653364] Re: package unattended-upgrades 0.90 failed to install/upgrade: package unattended-upgrades is not ready for configuration cannot configure (current status 'half-install
** Tags removed: need-duplicate-check -- 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/1653364 Title: package unattended-upgrades 0.90 failed to install/upgrade: package unattended-upgrades is not ready for configuration cannot configure (current status 'half-installed') Status in unattended-upgrades package in Ubuntu: New Bug description: system report ProblemType: Package DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Dec 8 08:20:51 2016 DuplicateSignature: package:unattended-upgrades:0.90 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ... dpkg: error processing package unattended-upgrades (--configure): package unattended-upgrades is not ready for configuration ErrorMessage: package unattended-upgrades is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2016-10-06 (86 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: unattended-upgrades Title: package unattended-upgrades 0.90 failed to install/upgrade: package unattended-upgrades is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1653364/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1651082] Re: package procps 2:3.3.10-4ubuntu2.3 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 procps in Ubuntu. https://bugs.launchpad.net/bugs/1651082 Title: package procps 2:3.3.10-4ubuntu2.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in procps package in Ubuntu: Confirmed Bug description: "there was an error installing package" that is the massage i receive every time i install a package using terminal. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: procps 2:3.3.10-4ubuntu2.3 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.4 Architecture: amd64 Date: Mon Dec 19 13:13:39 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-06-15 (186 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: procps Title: package procps 2:3.3.10-4ubuntu2.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1651082/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1650546] Re: package url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 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 url-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1650546 Title: package url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in url-dispatcher package in Ubuntu: New Bug description: ProblemType: Package DistroRelease: Ubuntu 16.10 Package: url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-30.32-lowlatency 4.8.6 Uname: Linux 4.8.0-30-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Fri Dec 16 01:00:55 2016 DuplicateSignature: package:url-dispatcher:amd64:0.1+16.10.20160816.1-0ubuntu1 Setting up click (0.4.45.1+16.10.20160916-0ubuntu1) ... Cannot start click due to a conflict with a different locally-installed Python 'click' package. Remove it using Python packaging tools and try again. dpkg: error processing package click (--configure): subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-05-23 (206 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.2ubuntu0.1 SourcePackage: url-dispatcher Title: package url-dispatcher:amd64 0.1+16.10.20160816.1-0ubuntu1 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/url-dispatcher/+bug/1650546/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1650825] Re: package linux-image-extra-4.4.0-53-generic 4.4.0-53.74 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1650825 Title: package linux-image-extra-4.4.0-53-generic 4.4.0-53.74 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 Status in initramfs-tools package in Ubuntu: New Bug description: clean new load on vmware 10, error message on first reboot. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.4.0-53-generic 4.4.0-53.74 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: craig 1034 F lxpanel Date: Sat Dec 17 16:30:27 2016 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 HibernationDevice: RESUME=UUID=8ea0593d-b792-40e2-9b36-afd9595d82c5 InstallationDate: Installed on 2016-12-17 (0 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: ens33 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-53-generic root=/dev/mapper/lubuntu--vg-root ro quiet splash RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.2 RfKill: SourcePackage: initramfs-tools Title: package linux-image-extra-4.4.0-53-generic 4.4.0-53.74 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2012 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2012:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1650825/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
** 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/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: New 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 1651041] Re: Bad version in Recommends
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1651041 Title: Bad version in Recommends Status in upower package in Ubuntu: New Bug description: not really sure what to say am a novice ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-httplib2 0.9.1+dfsg-1 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 Date: Sun Dec 18 23:25:18 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-12-14 (4 days ago) InstallationMedia: PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: python-httplib2 Title: package python-httplib2 0.9.1+dfsg-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-12-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1651041/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1652084] Re: package libgtk2.0-0 2.24.30-4ubuntu2 [modified: usr/share/doc/libgtk2.0-0/changelog.Debian.gz usr/share/doc/libgtk2.0-0/copyright] failed to install/upgrade: trying
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1652084 Title: package libgtk2.0-0 2.24.30-4ubuntu2 [modified: usr/share/doc/libgtk2.0-0/changelog.Debian.gz usr/share/doc/libgtk2.0-0/copyright] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgtk2.0-0/changelog.Debian.gz', which is different from other instances of package libgtk2.0-0:i386 Status in gtk+2.0 package in Ubuntu: New Bug description: Unable to perform any software updates. "The package system is broken" -- not very helpful. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libgtk2.0-0 2.24.30-4ubuntu2 [modified: usr/share/doc/libgtk2.0-0/changelog.Debian.gz usr/share/doc/libgtk2.0-0/copyright] ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 AptOrdering: libgtk2.0-0:i386: Install libgail18:i386: Install libgail-common:i386: Install NULL: ConfigurePending Architecture: amd64 Date: Sat Nov 12 15:35:46 2016 DpkgHistoryLog: Start-Date: 2016-11-12 15:35:45 Commandline: apt-get install -f Requested-By: dennison (1000) Install: libgail-common:i386 (2.24.30-4ubuntu2, automatic), libgail18:i386 (2.24.30-4ubuntu2, automatic) Upgrade: libgtk2.0-0:i386 (2.24.25-3+deb8u1, 2.24.30-4ubuntu2) DpkgTerminalLog: Preparing to unpack .../0-libgtk2.0-0_2.24.30-4ubuntu2_i386.deb ... Unpacking libgtk2.0-0:i386 (2.24.30-4ubuntu2) over (2.24.25-3+deb8u1) ... dpkg: error processing archive /tmp/apt-dpkg-install-TQWxBx/0-libgtk2.0-0_2.24.30-4ubuntu2_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libgtk2.0-0/changelog.Debian.gz', which is different from other instances of package libgtk2.0-0:i386 DuplicateSignature: package:libgtk2.0-0:2.24.30-4ubuntu2 [modified: usr/share/doc/libgtk2.0-0/changelog.Debian.gz usr/share/doc/libgtk2.0-0/copyright] Unpacking libgtk2.0-0:i386 (2.24.30-4ubuntu2) over (2.24.25-3+deb8u1) ... dpkg: error processing archive /tmp/apt-dpkg-install-TQWxBx/0-libgtk2.0-0_2.24.30-4ubuntu2_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libgtk2.0-0/changelog.Debian.gz', which is different from other instances of package libgtk2.0-0:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libgtk2.0-0/changelog.Debian.gz', which is different from other instances of package libgtk2.0-0:i386 InstallationDate: Installed on 2015-02-24 (667 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: gtk+2.0 Title: package libgtk2.0-0 2.24.30-4ubuntu2 [modified: usr/share/doc/libgtk2.0-0/changelog.Debian.gz usr/share/doc/libgtk2.0-0/copyright] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgtk2.0-0/changelog.Debian.gz', which is different from other instances of package libgtk2.0-0:i386 UpgradeStatus: Upgraded to yakkety on 2016-10-25 (57 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1652084/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1650419] Re: package ca-certificates 20160104ubuntu1 failed to install/upgrade: triggers looping, abandoned
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1650419 Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: triggers looping, abandoned Status in bamf package in Ubuntu: New Status in ca-certificates package in Ubuntu: New Bug description: while upgrading from ubuntu 16.04 LTS to 60.10 ProblemType: Package DistroRelease: Ubuntu 16.10 Package: ca-certificates 20160104ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Fri Dec 16 02:48:58 2016 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2016-02-12 (307 days ago) InstallationMedia: It PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: ca-certificates Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to yakkety on 2016-12-16 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1650419/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618900] Update Released
The verification of the Stable Release Update for unattended-upgrades has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1618900 Title: [Xenial/0.90] Systemd dependencies issues when used in "Shutdown mode" Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Yakkety: Fix Released Bug description: [Impact] There are some race conditions in unattended-upgrades when it is used in shutdown mode. It is possible that the network has already been brought down or for a local file system, like /var/, to be unmounted before the unattended-upgrades script is run. This then causes the updates not to be installed thereby making systems less secure - if security updates are enabled. [Test Case] Because this is a race condition, I haven't actually been able to recreate the bug. However, the fix is straightforward and testing for regressions should be sufficient. 1) On a freshly installed system. 2) Modify /etc/apt/apt.conf.d/50unattended-upgrades so that Unattended-Upgrade::InstallOnShutdown "true"; is not commented out. 3) Reboot and watch updates being installed 4) Verify updates were installed by reviewing /var/log/unattended-upgrades/unattended-upgrades.log 5) Uncomment -updates in 50unattended-upgrades Repeats steps 3 and 4 again. There isn't any need to run unattended- upgrades in *not* shutdown mode because we have only modified the systemd service file. [Regression Potential] There is little chance of a regression, but because of the change (and this feature now working better) its possible the shutdown process will take longer and surprise users. Original Description Using unattended-upgrades 0.90 in "Shutdown mode" on Ubuntu Xenial, we encounter the following systemd dependencies issues : - The network is often down when unattended-upgrades is running, so packages can not be downloaded (can be mitigated by using APT::Periodic::Download-Upgradeable-Packages "1";) : => ERROR An error occurred: 'Could not resolve host: .fr' => ERROR The URI 'https://.fr:33000/ubuntu-security/pool/main/libi/libidn/libidn11_1.32-3ubuntu1.1_amd64.deb' failed to download, aborting - Important mountpoints like /boot are unmounted before unattended-upgrades is running, so newer kernels can not be installed properly (ramdisk and grub configuration can not be generated) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1618900/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618900] Re: [Xenial/0.90] Systemd dependencies issues when used in "Shutdown mode"
This bug was fixed in the package unattended-upgrades - 0.90ubuntu0.3 --- unattended-upgrades (0.90ubuntu0.3) xenial-proposed; urgency=medium * Ensure that network and local filesystems are available when running unattended-upgrades during shutdown mode. (LP: #1618900) -- Brian Murray Wed, 14 Dec 2016 13:38:32 -0800 ** Changed in: unattended-upgrades (Ubuntu Xenial) Status: Fix Committed => Fix Released -- 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/1618900 Title: [Xenial/0.90] Systemd dependencies issues when used in "Shutdown mode" Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Yakkety: Fix Released Bug description: [Impact] There are some race conditions in unattended-upgrades when it is used in shutdown mode. It is possible that the network has already been brought down or for a local file system, like /var/, to be unmounted before the unattended-upgrades script is run. This then causes the updates not to be installed thereby making systems less secure - if security updates are enabled. [Test Case] Because this is a race condition, I haven't actually been able to recreate the bug. However, the fix is straightforward and testing for regressions should be sufficient. 1) On a freshly installed system. 2) Modify /etc/apt/apt.conf.d/50unattended-upgrades so that Unattended-Upgrade::InstallOnShutdown "true"; is not commented out. 3) Reboot and watch updates being installed 4) Verify updates were installed by reviewing /var/log/unattended-upgrades/unattended-upgrades.log 5) Uncomment -updates in 50unattended-upgrades Repeats steps 3 and 4 again. There isn't any need to run unattended- upgrades in *not* shutdown mode because we have only modified the systemd service file. [Regression Potential] There is little chance of a regression, but because of the change (and this feature now working better) its possible the shutdown process will take longer and surprise users. Original Description Using unattended-upgrades 0.90 in "Shutdown mode" on Ubuntu Xenial, we encounter the following systemd dependencies issues : - The network is often down when unattended-upgrades is running, so packages can not be downloaded (can be mitigated by using APT::Periodic::Download-Upgradeable-Packages "1";) : => ERROR An error occurred: 'Could not resolve host: .fr' => ERROR The URI 'https://.fr:33000/ubuntu-security/pool/main/libi/libidn/libidn11_1.32-3ubuntu1.1_amd64.deb' failed to download, aborting - Important mountpoints like /boot are unmounted before unattended-upgrades is running, so newer kernels can not be installed properly (ramdisk and grub configuration can not be generated) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1618900/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1652734] Re: installing kernel 4.9.0 and this crash happened installing package libglib2.0-0:amd64 2.48.1-1~ubuntu16.04.1 [origin: Ubuntu] failed to install/upgrade: dependency p
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1652734 Title: installing kernel 4.9.0 and this crash happened installing package libglib2.0-0:amd64 2.48.1-1~ubuntu16.04.1 [origin: Ubuntu] failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in glib2.0 package in Ubuntu: New Bug description: installing via dpkg ProblemType: Package DistroRelease: elementary 0.4 Package: libglib2.0-0:amd64 2.48.1-1~ubuntu16.04.1 [origin: Ubuntu] Uname: Linux 4.6.3-040603-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 Date: Tue Dec 27 18:13:28 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-03-10 (291 days ago) InstallationMedia: elementary OS 0.3.2 "Freya" - Stable amd64 (20151209) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15ubuntu0.2 SourcePackage: glib2.0 Title: package libglib2.0-0:amd64 2.48.1-1~ubuntu16.04.1 [origin: Ubuntu] failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1652734/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618900] Re: [Xenial/0.90] Systemd dependencies issues when used in "Shutdown mode"
This bug was fixed in the package unattended-upgrades - 0.92ubuntu1.2 --- unattended-upgrades (0.92ubuntu1.2) yakkety; urgency=medium * Ensure that network and local filesystems are available when running unattended-upgrades during shutdown mode. (LP: #1618900) -- Brian Murray Wed, 14 Dec 2016 13:31:31 -0800 ** Changed in: unattended-upgrades (Ubuntu Yakkety) Status: Fix Committed => Fix Released -- 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/1618900 Title: [Xenial/0.90] Systemd dependencies issues when used in "Shutdown mode" Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Yakkety: Fix Released Bug description: [Impact] There are some race conditions in unattended-upgrades when it is used in shutdown mode. It is possible that the network has already been brought down or for a local file system, like /var/, to be unmounted before the unattended-upgrades script is run. This then causes the updates not to be installed thereby making systems less secure - if security updates are enabled. [Test Case] Because this is a race condition, I haven't actually been able to recreate the bug. However, the fix is straightforward and testing for regressions should be sufficient. 1) On a freshly installed system. 2) Modify /etc/apt/apt.conf.d/50unattended-upgrades so that Unattended-Upgrade::InstallOnShutdown "true"; is not commented out. 3) Reboot and watch updates being installed 4) Verify updates were installed by reviewing /var/log/unattended-upgrades/unattended-upgrades.log 5) Uncomment -updates in 50unattended-upgrades Repeats steps 3 and 4 again. There isn't any need to run unattended- upgrades in *not* shutdown mode because we have only modified the systemd service file. [Regression Potential] There is little chance of a regression, but because of the change (and this feature now working better) its possible the shutdown process will take longer and surprise users. Original Description Using unattended-upgrades 0.90 in "Shutdown mode" on Ubuntu Xenial, we encounter the following systemd dependencies issues : - The network is often down when unattended-upgrades is running, so packages can not be downloaded (can be mitigated by using APT::Periodic::Download-Upgradeable-Packages "1";) : => ERROR An error occurred: 'Could not resolve host: .fr' => ERROR The URI 'https://.fr:33000/ubuntu-security/pool/main/libi/libidn/libidn11_1.32-3ubuntu1.1_amd64.deb' failed to download, aborting - Important mountpoints like /boot are unmounted before unattended-upgrades is running, so newer kernels can not be installed properly (ramdisk and grub configuration can not be generated) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1618900/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1420914] Re: secret-tool does not run on headless system
** Tags removed: utopic vivid ** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsecret in Ubuntu. https://bugs.launchpad.net/bugs/1420914 Title: secret-tool does not run on headless system Status in libsecret package in Ubuntu: Confirmed Bug description: Description: Ubuntu 14.04 LTS Release: 14.04 libsecret-tools: Installed: 0.16-0ubuntu1 Candidate: 0.16-0ubuntu1 Version table: *** 0.16-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status I expected to be able to run secret-tool on a headless sytem, but got this message after running it. secret-tool store ... (secret-tool:26626): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed secret-tool: Cannot autolaunch D-Bus without X11 $DISPLAY # didn't expect thisto work, but thought I'd give it a try. export DISPLAY=:0 secret-tool store ... (secret-tool:26639): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed secret-tool: Error spawning command line 'dbus-launch --autolaunch=0feb8b37e7d1bdde6782aa3e537cfda6 --binary-syntax --close-stderr': Child process exited with code 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsecret/+bug/1420914/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1263356] Re: Asks for authentication repeatedly, never establishes connection
Try to reproduce as follows: 1) Connect to Wifi network and enter WRONG password the first time 2) Connection failed, enter a new password and save it. 3) Connection fails? 3) Check in the edit connection dialog which password is stored. Is it the one entered in 1) or the new one entered? -- 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/1263356 Title: Asks for authentication repeatedly, never establishes connection Status in network-manager package in Ubuntu: New Bug description: I will try to connect to a wireless network. Every few moments, I'm asked for authentication again. A connection is never established. Tried multiple networks with different security types, the same problem on all of them. Able to connect on a wired connection just fine. Intel Centrino Wireless-N 2230 is the wireless hardware. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu22 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sat Dec 21 11:23:23 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-12-11 (9 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IpRoute: default via 10.0.0.1 dev eth0 proto static 10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.17 metric 1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 1498dbdcf-33fc-4388-ad11-8170fd1f3668 802-3-ethernet1387642926 Sat 21 Dec 2013 11:22:06 AM ESTyes no /org/freedesktop/NetworkManager/Settings/1 RINGNETGEAR de8f4e94-29a4-4c08-a2ef-7f7e30970a33 802-11-wireless 0never yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless disconnected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1263356/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1263356] Re: Asks for authentication repeatedly, never establishes connection
You can go to the edit connections dialog to view the password in plain text and compare it to the one entered in the failed-connection dialog. If the password stored is not the one you have entered, you have found a bug, that the entered password is not stored. You can try to change it in the edit connections dialog, if it is wrong. Then verify if the password has actually been changed. I have experienced such a problem together with Bug #1542733 with a ubuntu 16.04.1 LTS live cd. -- 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/1263356 Title: Asks for authentication repeatedly, never establishes connection Status in network-manager package in Ubuntu: New Bug description: I will try to connect to a wireless network. Every few moments, I'm asked for authentication again. A connection is never established. Tried multiple networks with different security types, the same problem on all of them. Able to connect on a wired connection just fine. Intel Centrino Wireless-N 2230 is the wireless hardware. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu22 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sat Dec 21 11:23:23 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-12-11 (9 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IpRoute: default via 10.0.0.1 dev eth0 proto static 10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.17 metric 1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 1498dbdcf-33fc-4388-ad11-8170fd1f3668 802-3-ethernet1387642926 Sat 21 Dec 2013 11:22:06 AM ESTyes no /org/freedesktop/NetworkManager/Settings/1 RINGNETGEAR de8f4e94-29a4-4c08-a2ef-7f7e30970a33 802-11-wireless 0never yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless disconnected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1263356/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1649453] Re: systemd starts postfix before resolver
@Scott: https://git.launchpad.net/postfix/commit/?h=stable/v3.1&id=1a190cf17cc02 looks rather complicated and also creates an unmanaged config file. Why not just always add those After= to the .service? If resolved is not enabled, then After=systemd-resolved is a no-op (it's only ordering, not a dependency -- that would be Requires= or Wants=). Also, not sure why you added network-online.target, but if you actually do want to wait for the network then you also need a corresponding Wants =network-online.target (see man systemd.special). ** No longer affects: systemd (Ubuntu) ** Tags added: resolved -- 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/1649453 Title: systemd starts postfix before resolver Status in postfix package in Ubuntu: Fix Committed Bug description: Postfix starts before systemd-resolved.service, resulting in postfix reporting that it can't find MX records for outgoing mail, as shown in the trace below: $ systemd-analyze critical-chain postfix.service systemd-resolved.service The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. postfix.service +1ms └─network.target @5.811s └─NetworkManager.service @5.690s +91ms └─dbus.service @5.627s └─basic.target @5.597s └─sockets.target @5.597s └─snapd.socket @5.597s +269us └─sysinit.target @5.596s └─systemd-timesyncd.service @5.420s +175ms └─systemd-tmpfiles-setup.service @5.408s +8ms └─local-fs.target @5.390s └─zfs-mount.service @3.879s +1.511s └─zfs-import-cache.service @2.539s +1.303s └─systemd-udev-settle.service @256ms +2.252s └─systemd-udev-trigger.service @208ms +47ms └─systemd-udevd-control.socket @148ms └─-.mount @122ms └─system.slice @124ms └─-.slice @122ms systemd-resolved.service +268ms └─network.target @5.811s └─NetworkManager.service @5.690s +91ms └─dbus.service @5.627s └─basic.target @5.597s └─sockets.target @5.597s └─snapd.socket @5.597s +269us └─sysinit.target @5.596s └─systemd-timesyncd.service @5.420s +175ms └─systemd-tmpfiles-setup.service @5.408s +8ms └─local-fs.target @5.390s └─zfs-mount.service @3.879s +1.511s └─zfs-import-cache.service @2.539s +1.303s └─systemd-udev-settle.service @256ms +2.252s └─systemd-udev-trigger.service @208ms +47ms └─systemd-udevd-control.socket @148ms └─-.mount @122ms └─system.slice @124ms └─-.slice @122ms The postfix service needs to start after systemd-resolved.service. $ lsb_release -rd Description: Ubuntu 16.10 Release: 16.10 $ apt-cache policy systemd systemd: Installed: 231-9ubuntu1 Candidate: 231-9ubuntu1 Version table: *** 231-9ubuntu1 500 500 http://mirror.aarnet.edu.au/pub/ubuntu/archive yakkety-updates/main amd64 Packages 100 /var/lib/dpkg/status 231-9git1 500 500 http://mirror.aarnet.edu.au/pub/ubuntu/archive yakkety/main amd64 Packages $ apt-cache policy postfix postfix: Installed: 3.1.0-5 Candidate: 3.1.0-5 Version table: *** 3.1.0-5 500 500 http://mirror.aarnet.edu.au/pub/ubuntu/archive yakkety/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1649453/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1653745] [NEW] core dump after system poweroff
You have been subscribed to a public bug: Ubuntu 16.04.1 x64 with systemd 229 and xorg 1.18.4 Core file dump after every shutdown with poweroff commmand and no core dump when using gui shutdown file /core output: ELF 64-bit LSB core file x86-64, version 1 (SYSV), SVR4-style, from '/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -noliste' ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- core dump after system poweroff https://bugs.launchpad.net/bugs/1653745 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm 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 1653745] Re: core dump after system poweroff
** Package changed: ubuntu => lightdm (Ubuntu) ** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1653745 Title: core dump after system poweroff Status in lightdm package in Ubuntu: New Bug description: Ubuntu 16.04.1 x64 with systemd 229 and xorg 1.18.4 Core file dump after every shutdown with poweroff commmand and no core dump when using gui shutdown file /core output: ELF 64-bit LSB core file x86-64, version 1 (SYSV), SVR4-style, from '/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -noliste' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1653745/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
Note bug #1653487 which says that this SRU is not enough to get seccomp working with snaps on 64 bit systems. -- 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 https://github.com/seccomp/libseccomp/commit/173b96ba8d3
[Touch-packages] [Bug 1653789] Re: DisplayConfigurationTest.configure_session_removed_display failure
** Branch linked: lp:~brandontschaefer/mir/fix-remove-display-test ** Changed in: mir Status: New => In Progress ** Also affects: mir (Ubuntu) Importance: Undecided Status: New ** Changed in: mir (Ubuntu) Status: New => In Progress ** Changed in: mir (Ubuntu) Importance: Undecided => High ** Changed in: mir (Ubuntu) Assignee: (unassigned) => Brandon Schaefer (brandontschaefer) ** Changed in: mir Milestone: None => 0.26.0 -- 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/1653789 Title: DisplayConfigurationTest.configure_session_removed_display failure Status in Mir: In Progress Status in mir package in Ubuntu: In Progress Bug description: https://mir-jenkins.ubuntu.com/job/build-2-binpkg- mir/arch=amd64,compiler=gcc,platform=mesa,release=xenial+overlay/3294/consoleFull To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1653789/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1576951] Re: System hangs if apple magic mouse is connected via bluetooth
i had the same experience with bq M10 and Microsoft Arc Touch mouse while pairing/connecting to bluetooth, unity 8 freezes/crashes -- 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/1576951 Title: System hangs if apple magic mouse is connected via bluetooth Status in Canonical System Image: Confirmed Status in frieza: New Status in turbo: New Status in bluez package in Ubuntu: Confirmed Bug description: If you connect apple magic mouse via bluetooth the system hangs completely. After 1 minute the system restarts. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1576951/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1576951] Re: System hangs if apple magic mouse is connected via bluetooth
on rc/proposed (ota14+) -- 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/1576951 Title: System hangs if apple magic mouse is connected via bluetooth Status in Canonical System Image: Confirmed Status in frieza: New Status in turbo: New Status in bluez package in Ubuntu: Confirmed Bug description: If you connect apple magic mouse via bluetooth the system hangs completely. After 1 minute the system restarts. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1576951/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
