[Touch-packages] [Bug 1600506] Re: mediascanner-service-2.0 crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediascanner2 in Ubuntu. https://bugs.launchpad.net/bugs/1600506 Title: mediascanner-service-2.0 crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() Status in mediascanner2 package in Ubuntu: Confirmed Bug description: Appears at login ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: mediascanner2.0 0.111+16.10.20160526-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13 Uname: Linux 4.4.0-30-generic x86_64 ApportVersion: 2.20.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 10 00:45:07 2016 ExecutablePath: /usr/bin/mediascanner-service-2.0 ProcCmdline: /usr/bin/mediascanner-service-2.0 Signal: 6 SourcePackage: mediascanner2 StacktraceTop: __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ScannerDaemon::setupBus() () Title: mediascanner-service-2.0 crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1600506/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1497593] Re: webbrowser-app crashed with SIGABRT in __assert_fail_base()
and it's not only the web browser it's all the web apps and anything related. -- 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/1497593 Title: webbrowser-app crashed with SIGABRT in __assert_fail_base() Status in webbrowser-app package in Ubuntu: New Bug description: webbrowser-app crashed with SIGABRT in __assert_fail_base() ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: webbrowser-app 0.23+15.10.20150913-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-10.12-generic 4.2.0 Uname: Linux 4.2.0-10-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 19 20:05:51 2015 ExecutablePath: /usr/bin/webbrowser-app InstallationDate: Installed on 2015-09-18 (1 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150918) ProcCmdline: webbrowser-app Signal: 6 SourcePackage: webbrowser-app StacktraceTop: __assert_fail_base (fmt=0x7f1aba6fd028 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7f1aa469f879 "kref", file=file@entry=0x7f1aa469f85a "../../nouveau/pushbuf.c", line=line@entry=726, function=function@entry=0x7f1aa469f8a0 "nouveau_pushbuf_data") at assert.c:92 __GI___assert_fail (assertion=0x7f1aa469f879 "kref", file=0x7f1aa469f85a "../../nouveau/pushbuf.c", line=726, function=0x7f1aa469f8a0 "nouveau_pushbuf_data") at assert.c:101 nouveau_pushbuf_data () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 nouveau_pushbuf_data () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 Title: webbrowser-app crashed with SIGABRT in __assert_fail_base() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1497593/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
When using AfterShokz's Trekz Titanium, the result is still the same... This issue still has not been addressed. -- bq Aquaris E5 HD Ubuntu Edition: * OS build number: OTA-13 * Ubuntu Image part: 20160913 * Ubuntu build description: Ubuntu 15.04 - armhf (20160913-023544) * Device Image part: 20160606-540a47f * Device build description: VEGETA01A-S23A_BQ_L100EN_2015_160913 * Customization Image part: 20160831-991-38-18 -- 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 1629849] Re: network-manager 1.2.2-0ubuntu0.16.04.1 ADT test failure with linux 4.4.0-41.61
*** This bug is a duplicate of bug 1609898 *** https://bugs.launchpad.net/bugs/1609898 Fixed in -proposed, duplicate of bug 1609898 ** This bug has been marked a duplicate of bug 1609898 dhclient incorrectly assumes a /64 ipv6 prefix -- 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/1629849 Title: network-manager 1.2.2-0ubuntu0.16.04.1 ADT test failure with linux 4.4.0-41.61 Status in network-manager package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/network-manager/20161001_130521@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/n/network-manager/20161001_153354@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/n/network-manager/20160930_222540@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1629849/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630136] Re: flaky test test_zoomableImageOpenClose
** Changed in: unity8 (Ubuntu) Importance: Undecided => Medium ** Changed in: unity8 (Ubuntu) Assignee: (unassigned) => Albert Astals Cid (aacid) ** Changed in: unity8 (Ubuntu) Status: New => In Progress ** Branch linked: lp:~aacid/unity8/waitForTransitionsOnInit -- 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/1630136 Title: flaky test test_zoomableImageOpenClose Status in unity8 package in Ubuntu: In Progress Bug description: See for example: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-vivid-ci-train-ppa- service-2035/vivid/amd64/u/unity8/20161003_212514@/log.gz -- QWARN : qmltestrunner::PreviewZoomableImageTest::test_zoomableImageOpenClose() file:///tmp/autopkgtest.PQVgh9/build.m75/unity8-8.14+15.04.20160922/qml/Dash/Previews/PreviewOverlay.qml:100:5: QML Loader: Binding loop detected for property "yScale" QWARN : qmltestrunner::PreviewZoomableImageTest::test_zoomableImageOpenClose() [PERFORMANCE]: Last frame took 91 ms to render. FAIL! : qmltestrunner::PreviewZoomableImageTest::test_zoomableImageOpenClose() property visible Actual (): false Expected (): true Loc: [/tmp/autopkgtest.PQVgh9/build.m75/unity8-8.14+15.04.20160922/tests/qmltests/Dash/Previews/tst_PreviewZoomableImage.qml(100)] -- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1630136/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1627950] Re: Stopped (with error) ... messages on encrypted LVM shutdown
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/1627950 Title: Stopped (with error) ... messages on encrypted LVM shutdown Status in systemd package in Ubuntu: Confirmed Bug description: Install (Default + crypted LVM) in Ubuntu Server s390x in Yakkety Daily Everything seems to work only on shutdown there is a bunch of "fail" messages related to the disks from systemd: [ OK ] Stopped Network Time Synchronization. [ 33.971312] systemd[1]: Stopped (with error) /dev/disk/by-id/dm-name-vda2_crypt. [FAILED] Stopped (with error) /dev/disk/by-id/dm-name-vda2_crypt. [ 33.971469] systemd[1]: Stopped (with error) /dev/disk/by-id/dm-uuid-CRYPT-LUKS1-ef8aced3ceb640fe80c2c700c4504ccb-vda2_crypt. [FAILED] Stopped (with error) /dev/disk/by-i...40fe80c2c700c4504ccb-vda2_crypt. [ 33.971595] systemd[1]: Stopped (with error) /dev/disk/by-id/lvm-pv-uuid-9hfIOG-dPqq-MpWQ-DzEr-njkh-t2LD-XT3kxq. [FAILED] Stopped (with error) /dev/disk/by-i...dPqq-MpWQ-DzEr-njkh-t2LD-XT3kxq. [FAILED] Stopped (with error) /dev/mapper/vda2_crypt. [FAILED] Stopped (with error) /dev/dm-0. [FAILED] Stopped (with error) /sys/devices/virtual/block/dm-0. [ OK ] Stopped Create Volatile Files and Directories. [ OK ] Stopped Raise network interfaces. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1627950/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630152] [NEW] package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 - general issues with a
Public bug reported: Just an overall problem with apt-update from the CL after a fresh install. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: fontconfig 2.11.94-0ubuntu1.1 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 Date: Tue Oct 4 02:28:16 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-10-04 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 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) ** Affects: fontconfig (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1630152 Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 - general issues with apt-update as well. Status in fontconfig package in Ubuntu: New Bug description: Just an overall problem with apt-update from the CL after a fresh install. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: fontconfig 2.11.94-0ubuntu1.1 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 Date: Tue Oct 4 02:28:16 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-10-04 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 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/1630152/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630152] Re: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 - general issues with apt
** 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/1630152 Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 - general issues with apt-update as well. Status in fontconfig package in Ubuntu: New Bug description: Just an overall problem with apt-update from the CL after a fresh install. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: fontconfig 2.11.94-0ubuntu1.1 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 Date: Tue Oct 4 02:28:16 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-10-04 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 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/1630152/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
** Description changed: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. 2. Install systemd-sysv rather than upstart-sysv (Bug 1625023) 2.1. rebuild latest ubuntu-touch package from source [2] with patch [3] applied. 2.2. download latest systemd-sysv package [4]. 2.3. dpkg -i ubuntu-touch_*.deb systemd-sysv_*.deb 3. Install android-tools-adbd for systemd (Bug 1627613) 3.1. Install prebuilt package [5] or recompile it from source [6] with patch [7] applied. 3.2. Install the package from Terminal app because it will break adb connection and interrupt the installation process leaving a very bad state of the package. 4. Modify lxc-android-config package systemd service file by hand as the merge proposal [8][9][10][11] does. (Bug 1625445, bug 1625916, bug 1626012, bug 1627613). 5. Recompile upstart with merge proposal [12] include and install at least the built binary /sbin/upstart-local-bridge. 6. Reboot. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/u/ubuntu-touch-meta/ [3]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch [4]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/s/systemd/ [5]: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1627613/+attachment/4751442/+files/android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb [6]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/a/android-tools/ [7]: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1627613/+attachment/4750792/+files/0001-install-systemd-service-files.patch [8]: https://code.launchpad.net/~vicamo/lxc-android-config/fix-systemd-service-startup/+merge/306435 [9]: https://code.launchpad.net/~vicamo/lxc-android-config/add-upstart-local-bridge/+merge/307144 [10]: https://code.launchpad.net/~vicamo/lxc-android-config/systemd-writable-paths/+merge/306184 [11]: https://code.launchpad.net/~vicamo/lxc-android-config/disable-systemd-alsa-restore/+merge/306587 [12]: https://code.launchpad.net/~vicamo/upstart/xenial-escape-systemd-strings/+merge/307140 [All Pending MPs] 1. ubuntu-touch-meta: * https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch 2. lxc-android-config: * https://code.launchpad.net/~vicamo/lxc-android-config/fix-systemd-service-startup/+merge/306435 * https://code.launchpad.net/~vicamo/lxc-android-config/add-upstart-local-bridge/+merge/307144 * https://code.launchpad.net/~vicamo/lxc-android-config/systemd-writable-paths/+merge/306184 * https://code.launchpad.net/~vicamo/lxc-android-config/disable-systemd-alsa-restore/+merge/306587 3. upstart: * https://code.launchpad.net/~vicamo/upstart/xenial-escape-systemd-strings/+merge/307140 [Prebuilt rootfs tarball] - https://private-fileshare.canonical.com/~vicamo/avila/images/systemd/ubuntu/20161004/rootfs-systemd.tar.bz2 - md5sum: dd185cf1c7aada1623e57319ae139c72 + https://private-fileshare.canonical.com/~vicamo/avila/images/systemd/ubuntu/20161004/rootfs-systemd.tar.bz2 (updated 15:55 +0800) + md5sum: 220c811b8ad7cb978d6b695679ad21fc build_number: 49 version_detail: ubuntu=20161001,device=20160919.0,custom=20161001,version=49 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: Confirmed Status in android-tools package in Ubuntu: Confirmed Status in lxc-android-config package in Ubuntu: Confirmed Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. 2. Install systemd-sysv rather than upstart-sysv (Bug 1625023) 2.1. rebuild latest ubuntu-touch package from source [2] with patch [3] applied. 2.2. download latest systemd-sysv package [4]. 2.3. dpkg -i ubuntu-touch_*.deb systemd-sysv_*.deb 3. Install android-tools-adbd for systemd (Bug 1627613) 3.1. Install prebuilt package [5] or recompile it from source [6] with patch [7] applied. 3.2. Install the package from Terminal app because it will break adb connection and interrupt the installation process leaving a very bad state of the
[Touch-packages] [Bug 1630156] [NEW] No password needed to Log in after cancel the password and then reset again
Public bug reported: OS: 14.04 trusty 1. Go to path "System Setting --> User Accounts--> Unlock" to unlock system setting. 2. Click "Password --> Action --> Log in without password -->Change to clear Log in password. 3. Reboot and log to desktop without password. 4. Then do the similar action "Set a password now" as the same way to set Log in password. 5. Reboot but still no password needed at Log in interface. ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1630156 Title: No password needed to Log in after cancel the password and then reset again Status in lightdm package in Ubuntu: New Bug description: OS: 14.04 trusty 1. Go to path "System Setting --> User Accounts--> Unlock" to unlock system setting. 2. Click "Password --> Action --> Log in without password -->Change to clear Log in password. 3. Reboot and log to desktop without password. 4. Then do the similar action "Set a password now" as the same way to set Log in password. 5. Reboot but still no password needed at Log in interface. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1630156/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1629275] Re: Clients and server all crash
** This bug is no longer a duplicate of bug 1607812 When stressed by a load of clients starting at once: Failed to get PRIME fd from gbm bo ** Description changed: mir-24 on yakkety (or mir-0.21 on xenial, or lp:mir on yakkety) Start a Mir-on-X11 session: - $ mir_demo_server_minimal & - $ mirrun gnome-terminal + $ mir_demo_server_minimal & + $ mirrun gnome-terminal In the terminal: - $ mir_demo_client_all& + $ mir_demo_client_all& (A script that launches all the Mir demo clients - attached) Expect: all the clients open Actual (most times): gnome-terminal and all the clients crash Actual (frequently): gnome-terminal, all the clients, and the server crash Actual (occasionally): all the clients open + + The "frequent" server crash is lp:1607812, this bug is for the client + crash ** Branch unlinked: lp:~alan-griffiths/mir/fix-server-crash -- 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/1629275 Title: Clients and server all crash Status in Mir: Incomplete Status in MirAL: Triaged Status in mir package in Ubuntu: New Bug description: mir-24 on yakkety (or mir-0.21 on xenial, or lp:mir on yakkety) Start a Mir-on-X11 session: $ mir_demo_server_minimal & $ mirrun gnome-terminal In the terminal: $ mir_demo_client_all& (A script that launches all the Mir demo clients - attached) Expect: all the clients open Actual (most times): gnome-terminal and all the clients crash Actual (frequently): gnome-terminal, all the clients, and the server crash Actual (occasionally): all the clients open The "frequent" server crash is lp:1607812, this bug is for the client crash To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1629275/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1627795] Re: unity8-dash crashed with SIGSEGV in QQmlData::isSignalConnected from QObjectPrivate::isSignalConnected from QMetaObject::activate from QMetaObject::activate from QAb
** Changed in: unity-scopes-shell (Ubuntu) Status: Confirmed => In Progress ** Branch linked: lp:~marcustomlinson/unity-scopes-shell/lp-1627795 -- 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/1627795 Title: unity8-dash crashed with SIGSEGV in QQmlData::isSignalConnected from QObjectPrivate::isSignalConnected from QMetaObject::activate from QMetaObject::activate from QAbstractItemModel::modelAboutToBeReset Status in unity-scopes-shell package in Ubuntu: In Progress Status in unity8 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity8. This problem was most recently seen with version 8.14+15.04.20160831.3-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/0168de360a9e17b6337e0304609320555b011747 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1627795/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1629275] Re: Clients and server all crash
OK, see also: bug 1607812 -- 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/1629275 Title: Clients and server all crash Status in Mir: Incomplete Status in MirAL: Triaged Status in mir package in Ubuntu: New Bug description: mir-24 on yakkety (or mir-0.21 on xenial, or lp:mir on yakkety) Start a Mir-on-X11 session: $ mir_demo_server_minimal & $ mirrun gnome-terminal In the terminal: $ mir_demo_client_all& (A script that launches all the Mir demo clients - attached) Expect: all the clients open Actual (most times): gnome-terminal and all the clients crash Actual (frequently): gnome-terminal, all the clients, and the server crash Actual (occasionally): all the clients open The "frequent" server crash is lp:1607812, this bug is for the client crash To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1629275/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615703] Re: [regression] mir demo server fails to start with mx4
** Branch unlinked: lp:mir -- 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/1615703 Title: [regression] mir demo server fails to start with mx4 Status in Mir: Fix Committed Status in mir package in Ubuntu: Invalid Bug description: mir_demo_server fails to start with mx4. I'd guess failure indicates the u8 stack wouldn't start either. Should be fixed for 0.25 series. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1615703/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1506846] Re: [multimonitor] nested server surface positioning incorrect
** Branch unlinked: lp:mir -- 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/1506846 Title: [multimonitor] nested server surface positioning incorrect Status in Mir: Fix Released Status in Unity System Compositor: Confirmed Status in mir package in Ubuntu: Fix Released Bug description: Flo and Mir 0.17. For multimonitor, it appears USC often positions the 2 nested server surfaces on the same screen, as if noth surfaces are positioned at (0,0) in the virtual desktop space - and not side-by-side. This screenshot may not be the clearest: https://chinstrap.canonical.com/~gerboland/mm2.jpg but I got it through moving the egltriangle surface to the right, and it appeared on the left! Steps to repro: 1. SSH into device and do: sudo stop lightdm 2. You'll want your backllight back, mirbacklight didn't work for me, so I called this as root: echo 255 > /sys/devices/platform/msm_fb.591617/leds/lcd-backlight/brightness 3. Run sudo unity-system-compositor --debug-without-dm --disable-inactivity-policy true --enable-hardware-cursor=true --debug-active-session-name=Test sudo chmod 777 /tmp/mir_socket 4. Start nested server mir_demo_server --host /tmp/mir_socket --display-config sidebyside --launch-client /usr/bin/mir_demo_client_egltriangle You should see the spinny triangle. 5. Now plug in the slimport cable. The display will flicker while the external display is being incorporated. 6. Use 3 fingers, move the triangle surface to the right. Expected result: It should appear on the external display Actual result: It pops in on the left of the internal display. See screenshot above. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1506846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630152] Re: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 - general issues with apt
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: fontconfig (Ubuntu) Importance: Undecided => Low ** Changed in: fontconfig (Ubuntu) Status: New => Invalid -- 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/1630152 Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 - general issues with apt-update as well. Status in fontconfig package in Ubuntu: Invalid Bug description: Just an overall problem with apt-update from the CL after a fresh install. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: fontconfig 2.11.94-0ubuntu1.1 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 Date: Tue Oct 4 02:28:16 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-10-04 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 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/1630152/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630163] Re: tracker-extract crashed with SIGABRT in g_assertion_message()
*** This bug is a duplicate of bug 1543354 *** https://bugs.launchpad.net/bugs/1543354 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 #1543354, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1630163/+attachment/4754062/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1630163/+attachment/4754064/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1630163/+attachment/4754067/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1630163/+attachment/4754068/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1630163/+attachment/4754069/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1630163/+attachment/4754070/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1630163/+attachment/4754071/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1543354 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1630163 Title: tracker-extract crashed with SIGABRT in g_assertion_message() Status in tracker package in Ubuntu: New Bug description: Crash report generated at system startup ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: tracker-extract 1.10.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Tue Oct 4 09:06:19 2016 ExecutablePath: /usr/lib/tracker/tracker-extract InstallationDate: Installed on 2014-11-05 (698 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcCmdline: /usr/lib/tracker/tracker-extract Signal: 6 SourcePackage: tracker StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgstaudio-1.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgstaudio-1.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgstaudio-1.0.so.0 Title: tracker-extract crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip libvirt libvirtd lpadmin lxd netdev plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1630163/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630167] [NEW] When SlotsLayout uses a Column as mainSlot and view is resized horizontally an inifinite resize loop starts
Public bug reported:
With a simple code such as
import QtQuick 2.4
import Ubuntu.Components 1.3
import QtQuick.Window 2.0
Window {
SlotsLayout {
id: slotsLayout
onHeightChanged: print("SlotsLayout height",height)
width: parent.width
mainSlot: Column {
onHeightChanged: print("COlumn height",height)
onWidthChanged: console.log("Column width", width)
Rectangle {
id: rect
width: parent.width
onWidthChanged: console.log("RECT WIDTH", width)
onHeightChanged: console.log("RECT HEIGHT!", height)
height: 5
}
}
}
}
Or something similar (http://archive.is/N0jnM), when resizing the view
horizontally to only use few pixels, an infinite resizing loop starts and the
view freezes.
** Affects: ubuntu-ui-toolkit (Ubuntu)
Importance: Medium
Assignee: Andrea Bernabei (faenil)
Status: Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1630167
Title:
When SlotsLayout uses a Column as mainSlot and view is resized
horizontally an inifinite resize loop starts
Status in ubuntu-ui-toolkit package in Ubuntu:
Triaged
Bug description:
With a simple code such as
import QtQuick 2.4
import Ubuntu.Components 1.3
import QtQuick.Window 2.0
Window {
SlotsLayout {
id: slotsLayout
onHeightChanged: print("SlotsLayout height",height)
width: parent.width
mainSlot: Column {
onHeightChanged: print("COlumn height",height)
onWidthChanged: console.log("Column width", width)
Rectangle {
id: rect
width: parent.width
onWidthChanged: console.log("RECT WIDTH", width)
onHeightChanged: console.log("RECT HEIGHT!", height)
height: 5
}
}
}
}
Or something similar (http://archive.is/N0jnM), when resizing the view
horizontally to only use few pixels, an infinite resizing loop starts and the
view freezes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1630167/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630171] Re: sudo crashed with SIGSEGV in kill()
*** This bug is a duplicate of bug 1618602 *** https://bugs.launchpad.net/bugs/1618602 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 #1618602, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1630171/+attachment/4754096/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1630171/+attachment/4754098/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1630171/+attachment/4754101/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1630171/+attachment/4754102/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1630171/+attachment/4754103/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1630171/+attachment/4754105/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1630171/+attachment/4754107/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1618602 sudo crashed with SIGSEGV in kill() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1630171 Title: sudo crashed with SIGSEGV in kill() Status in sudo package in Ubuntu: New Bug description: run sudo ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: sudo 1.8.16-0ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: MATE Date: Tue Oct 4 10:58:47 2016 ExecutablePath: /usr/bin/sudo InstallationDate: Installed on 2016-08-24 (40 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Alpha amd64 (20160727.1) ProcCmdline: sudo dpkg -i teamviewer_11.0.57095_i386.deb Signal: 11 SourcePackage: sudo StacktraceTop: kill () at ../sysdeps/unix/syscall-template.S:84 ?? () __libc_start_main (main=0x55fe3ef9f9f0, argc=4, argv=0x7ffc03075118, init=, fini=, rtld_fini=, stack_end=0x7ffc03075108) at ../csu/libc-start.c:291 ?? () Title: sudo crashed with SIGSEGV in kill() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1630171/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630167] Re: When SlotsLayout uses a Column as mainSlot and view is resized horizontally an inifinite resize loop starts
info for my future self:
I investigated this bug a few days ago, when Trevinho first reported it
directly to me.
It turns out the loop is triggered when the view is resized so that the
column gets a *negative* width.
At that point you see columns height going 0 to 5 (which is rectangle's
height) and back to 0, in a loop, and width going -X to 0 to -X again.
** Summary changed:
- When SlotsLayout uses a Column as mainSlot and view is resized horizontally
an inifinite resize loop starts
+ SlotsLayout with Column as mainSlot: endless loop when resizing view so that
Column has negative width
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1630167
Title:
SlotsLayout with Column as mainSlot: endless loop when resizing view
so that Column has negative width
Status in ubuntu-ui-toolkit package in Ubuntu:
Triaged
Bug description:
With a simple code such as
import QtQuick 2.4
import Ubuntu.Components 1.3
import QtQuick.Window 2.0
Window {
SlotsLayout {
id: slotsLayout
onHeightChanged: print("SlotsLayout height",height)
width: parent.width
mainSlot: Column {
onHeightChanged: print("COlumn height",height)
onWidthChanged: console.log("Column width", width)
Rectangle {
id: rect
width: parent.width
onWidthChanged: console.log("RECT WIDTH", width)
onHeightChanged: console.log("RECT HEIGHT!", height)
height: 5
}
}
}
}
Or something similar (http://archive.is/N0jnM), when resizing the view
horizontally to only use few pixels, an infinite resizing loop starts and the
view freezes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1630167/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1532358] Re: flaky autopkgtests cause migration issues
** Changed in: unity-scopes-shell (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 unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1532358 Title: flaky autopkgtests cause migration issues Status in Canonical System Image: Fix Released Status in unity-scope-click package in Ubuntu: In Progress Status in unity-scopes-shell package in Ubuntu: Fix Released Bug description: A few times recently when unity8 got into xenial-proposed for migration, unity-scope-click's autopkgtest failed on the first run, having passed on the next: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/u/unity-scope-click/20160105_174239@/log.gz https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/u/unity-scope-click/20160108_185317@/log.gz https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-ci-train-ppa-service-landing-030/xenial/armhf/u/unity-scope-click/20160111_213558@/log.gz This delays migration until someone notices the failure and asks for a re-run, which usually passes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity-scope-click 0.1.1+16.04.20151216.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 Uname: Linux 4.3.0-5-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jan 9 00:29:21 2016 SourcePackage: unity-scope-click UpgradeStatus: Upgraded to xenial on 2015-10-28 (72 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1532358/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630188] Re: tab options from context menu are unfocused
** Attachment added: "tab_options_.png" https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1630188/+attachment/4754144/+files/tab_options_.png -- 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/1630188 Title: tab options from context menu are unfocused Status in webbrowser-app package in Ubuntu: New Bug description: Enviroment: Desktp Xenial+overlay Steps to reproduce: 1º Open webbrowser app and visit any web site 2º Right click over any tab Current result: Tab options shown when right click are unfocused Expected result: Tab options should be focused To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1630188/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630188] [NEW] tab options from context menu are unfocused
Public bug reported: Enviroment: Desktp Xenial+overlay Steps to reproduce: 1º Open webbrowser app and visit any web site 2º Right click over any tab Current result: Tab options shown when right click are unfocused Expected result: Tab options should be focused ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Attachment added: "tab_options_.png" https://bugs.launchpad.net/bugs/1630188/+attachment/4754143/+files/tab_options_.png ** Attachment removed: "tab_options_.png" https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1630188/+attachment/4754143/+files/tab_options_.png -- 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/1630188 Title: tab options from context menu are unfocused Status in webbrowser-app package in Ubuntu: New Bug description: Enviroment: Desktp Xenial+overlay Steps to reproduce: 1º Open webbrowser app and visit any web site 2º Right click over any tab Current result: Tab options shown when right click are unfocused Expected result: Tab options should be focused To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1630188/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630191] [NEW] MTU settings not always applied after reboot
Public bug reported: On a node with two 10G interfaces, we configure a bond interface from these two interfaces and then a vlan interface on top of it. The MTU of these interfaces shall be set to be 1550 instead of the default 1500, so we have these settings in /etc/network/interfaces.d: root@controller-node13:~# cat /etc/network/interfaces.d/xge0 auto xge0 iface xge0 inet manual bond-master xiondata root@controller-node13:~# cat /etc/network/interfaces.d/xge1 auto xge1 iface xge1 inet manual bond-master xiondata root@controller-node13:~# cat /etc/network/interfaces.d/xiondata auto xiondata iface xiondata inet manual bond-slaves xge0 xge1 bond-miimon 100 bond-lacp-rate 1 bond-mode 4 mtu 1550 root@controller-node13:~# cat /etc/network/interfaces.d/xiondata.200 auto xiondata.200 iface xiondata.200 inet static address 10.80.1.13/24 vlan_raw_device xiondata mtu 1550 After a reboot, the correct MTU is applied to the vlan interface only 50% of the time, on the other attempts, it stays at 1500, leading to broken connectivity. If I restart the interfaces manually, by doing "ifdown xiondata; ifup -a" the MTU settings seem to be applied correctly every time. root@controller-node13:~# apt policy ifupdown ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 Version table: *** 0.8.10ubuntu1 500 500 http://eu.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ifupdown 0.8.10ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Oct 4 09:44:40 2016 ProcEnviron: LANGUAGE=en_US: TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: ifupdown UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ifupdown (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1630191 Title: MTU settings not always applied after reboot Status in ifupdown package in Ubuntu: New Bug description: On a node with two 10G interfaces, we configure a bond interface from these two interfaces and then a vlan interface on top of it. The MTU of these interfaces shall be set to be 1550 instead of the default 1500, so we have these settings in /etc/network/interfaces.d: root@controller-node13:~# cat /etc/network/interfaces.d/xge0 auto xge0 iface xge0 inet manual bond-master xiondata root@controller-node13:~# cat /etc/network/interfaces.d/xge1 auto xge1 iface xge1 inet manual bond-master xiondata root@controller-node13:~# cat /etc/network/interfaces.d/xiondata auto xiondata iface xiondata inet manual bond-slaves xge0 xge1 bond-miimon 100 bond-lacp-rate 1 bond-mode 4 mtu 1550 root@controller-node13:~# cat /etc/network/interfaces.d/xiondata.200 auto xiondata.200 iface xiondata.200 inet static address 10.80.1.13/24 vlan_raw_device xiondata mtu 1550 After a reboot, the correct MTU is applied to the vlan interface only 50% of the time, on the other attempts, it stays at 1500, leading to broken connectivity. If I restart the interfaces manually, by doing "ifdown xiondata; ifup -a" the MTU settings seem to be applied correctly every time. root@controller-node13:~# apt policy ifupdown ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 Version table: *** 0.8.10ubuntu1 500 500 http://eu.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ifupdown 0.8.10ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Oct 4 09:44:40 2016 ProcEnviron: LANGUAGE=en_US: TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: ifupdown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1630191/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630087] Re: Can't log onto Unity8 because can't figure out keyboard layout, as there is no textbox to test it in.
Also related to this bug: lp:1626435 -- 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/1630087 Title: Can't log onto Unity8 because can't figure out keyboard layout, as there is no textbox to test it in. Status in Canonical System Image: Incomplete Status in Ubuntu UX: New Status in unity8 package in Ubuntu: Incomplete Bug description: I use colemak, and a funky character in my password that requires altgr shift level 3. On 16.10, logging out of Unity7 brings me to the Unity8 login prompt. There is a label with my account name, and a text box for my password. I have no idea what I am typing, and what regularly works for me on lightdm, is not working for me on Unity8's login prompt. I simply can not login. I need a way to figure out what I am typing. There is no means to figure out what is being typed. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1630087/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630188] Re: tab options from context menu are unfocused
** Description changed: Enviroment: Desktp Xenial+overlay - - + webbrowser app 0.23+15.04.20160928-0ubuntu1 Steps to reproduce: 1º Open webbrowser app and visit any web site 2º Right click over any tab - Current result: Tab options shown when right click are unfocused Expected result: Tab options should be focused -- 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/1630188 Title: tab options from context menu are unfocused Status in webbrowser-app package in Ubuntu: New Bug description: Enviroment: Desktp Xenial+overlay webbrowser app 0.23+15.04.20160928-0ubuntu1 Steps to reproduce: 1º Open webbrowser app and visit any web site 2º Right click over any tab Current result: Tab options shown when right click are unfocused Expected result: Tab options should be focused To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1630188/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi
I have been running a manual script ten times a day for half a year to live with this bug. The bug I reported upstream are either waiting for us here on launchpad or the bug's not being taken serious. Are there anyone reading this that knows anything about how we can get this fixed, I don't have the experience or the skills to set things in motion. It does seem like there only a handful of us regular users that's aware of this problem. Please anyone? -- 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/1589401 Title: cannot view wifi networks after re-enabling wifi Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Incomplete Bug description: after re enabling wifi, up-down arrows just like wired network. cannot see any wifi ssid. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630090] Re: $XMODIFIERS not set correctly
** Also affects: upstart (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1630090 Title: $XMODIFIERS not set correctly Status in im-config package in Ubuntu: New Status in upstart package in Ubuntu: New Bug description: The XMODIFIERS environment variable is not set correctly. $ echo $XMODIFIERS @im $ The value should be - for ibus: "@im=ibus" - for fcitx: "@im=fcitx" - for xim: "@im=none" The issue is present in Ubuntu/Unity 16.10. I don't see it in Ubuntu GNOME, neither in Ubuntu 16.04. Actually I don't think the affected package is im-config, because the issue is present also after having downgraded im-config to 0.29-1ubuntu12 (the Xenial version). But I wanted to file the bug somewhere, so here it is. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1630090/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630188] Re: tab options from context menu are unfocused
** Attachment added: "focused.png" https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1630188/+attachment/4754150/+files/focused.png ** Description changed: Enviroment: Desktp Xenial+overlay webbrowser app 0.23+15.04.20160928-0ubuntu1 Steps to reproduce: - 1º Open webbrowser app and visit any web site - 2º Right click over any tab + 1º Open webbrowser app and open 3 tabs + 2º Right click over each tab - Current result: Tab options shown when right click are unfocused - Expected result: Tab options should be focused + Current result: Tab options are unfocused for all tabs except for the first one, that is correctly shown + Expected result: Tab options should be all focused -- 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/1630188 Title: tab options from context menu are unfocused Status in webbrowser-app package in Ubuntu: New Bug description: Enviroment: Desktp Xenial+overlay webbrowser app 0.23+15.04.20160928-0ubuntu1 Steps to reproduce: 1º Open webbrowser app and open 3 tabs 2º Right click over each tab Current result: Tab options are unfocused for all tabs except for the first one, that is correctly shown Expected result: Tab options should be all focused To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1630188/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630188] Re: tab options from context menu are unfocused
** Attachment removed: "tab_options_.png" https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1630188/+attachment/4754144/+files/tab_options_.png ** Attachment added: "unfocused.png" https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1630188/+attachment/4754149/+files/unfocused.png -- 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/1630188 Title: tab options from context menu are unfocused Status in webbrowser-app package in Ubuntu: New Bug description: Enviroment: Desktp Xenial+overlay webbrowser app 0.23+15.04.20160928-0ubuntu1 Steps to reproduce: 1º Open webbrowser app and open 3 tabs 2º Right click over each tab Current result: Tab options are unfocused for all tabs except for the first one, that is correctly shown Expected result: Tab options should be all focused To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1630188/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1628134] Re: OP banking website not working
I can reliably reproduce on arale. ** 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/1628134 Title: OP banking website not working Status in webbrowser-app package in Ubuntu: Confirmed Bug description: https://kokeile.op.fi/ (OP/Osuuspankki's new mobile friendly web site) fails first immediately with the browser. However: with UA - Mozilla/5.0 (Linux; Android 7.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.124 Mobile Safari/537.36 - it does give you the mobile web site. But as soon as you click the big image at the center top, you get to a page which essentially says "Service use blocked". However 2: in Firefox desktop version's Responsive Design Mode (Ctrl- Shift-M) with the same UA set in the Custom User Agent field, it does give the mobile site and not block when going further. Tested on krillin and frieza. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1628134/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630188] Re: tab options from context menu are unfocused
Also happening on Frieza r201 -- 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/1630188 Title: tab options from context menu are unfocused Status in webbrowser-app package in Ubuntu: New Bug description: Enviroment: Desktp Xenial+overlay webbrowser app 0.23+15.04.20160928-0ubuntu1 Steps to reproduce: 1º Open webbrowser app and open 3 tabs 2º Right click over each tab Current result: Tab options are unfocused for all tabs except for the first one, that is correctly shown Expected result: Tab options should be all focused To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1630188/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630199] [NEW] [Torino Z200, Realtek ALC269VB, Speaker, Internal] No sound at all
Public bug reported: No sound via speaker, sound is obtainable by using alsamixer and increasing the volume of the 'headset' the control labelled 'speaker' does not have any apparent effect. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mick 1728 F pulseaudio CurrentDesktop: MATE Date: Tue Oct 4 11:21:27 2016 InstallationDate: Installed on 2016-09-29 (4 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mick 1728 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Torino Z200, Realtek ALC269VB, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.01 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 079114 dmi.board.vendor: DSG Retail Ltd dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: DSG Retail Ltd dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.01:bd02/08/2014:svnAdvent:pnTorinoZ200:pvr1.01:rvnDSGRetailLtd:rn079114:rvrTobefilledbyO.E.M.:cvnDSGRetailLtd:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: Torino Z200 dmi.product.version: 1.01 dmi.sys.vendor: Advent ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1630199 Title: [Torino Z200, Realtek ALC269VB, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: No sound via speaker, sound is obtainable by using alsamixer and increasing the volume of the 'headset' the control labelled 'speaker' does not have any apparent effect. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mick 1728 F pulseaudio CurrentDesktop: MATE Date: Tue Oct 4 11:21:27 2016 InstallationDate: Installed on 2016-09-29 (4 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mick 1728 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Torino Z200, Realtek ALC269VB, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.01 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 079114 dmi.board.vendor: DSG Retail Ltd dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: DSG Retail Ltd dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.01:bd02/08/2014:svnAdvent:pnTorinoZ200:pvr1.01:rvnDSGRetailLtd:rn079114:rvrTobefilledbyO.E.M.:cvnDSGRetailLtd:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: Torino Z200 dmi.product.version: 1.01 dmi.sys.vendor: Advent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1630199/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1576698] Re: ntpdate-debian not working
Since there was no other response I verified that on my own. Proposed works just fine now. ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1576698 Title: ntpdate-debian not working Status in ntp package in Ubuntu: Fix Released Status in ntp source package in Xenial: Fix Committed Status in ntp package in Debian: New Bug description: [Impact] * ntpdate-debian fails to work if ntp is installed at the same time due to a conflict in the updated ntp config to the ntpdate-debian script. [Test Case] # e.g. spawn xenial container # Note: only occurs when ntp is installed as well $ apt-get install ntpdate ntp $ ntpdate-debian (Note for latter verification enable proposed in that container and re-update ntpdate) [Regression Potential] * There could exists a custom user conf that had a mixed server AND pool specified, that now will use the first of both types while instead formerly it would have used the first server entry. The chance for this is super-low IMHO, but this case exists. in 16.04 I get this # ntpdate-debian 28 Apr 09:54:14 ntpdate[30747]: no servers can be used, exiting The problem is that ntpdate-debian parse /etc/ntp.conf, searchin for the word "server", but the format of the file as changed a bit < server 0.ubuntu.pool.ntp.org < server 1.ubuntu.pool.ntp.org < server 2.ubuntu.pool.ntp.org < server 3.ubuntu.pool.ntp.org --- > pool 0.ubuntu.pool.ntp.org iburst > pool 1.ubuntu.pool.ntp.org iburst > pool 2.ubuntu.pool.ntp.org iburst > pool 3.ubuntu.pool.ntp.org iburst 25c24 < server ntp.ubuntu.com --- > pool ntp.ubuntu.com the word server as been replaced by "pool" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1576698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630188] Re: tab options from context menu are unfocused
*** This bug is a duplicate of bug 1606489 *** https://bugs.launchpad.net/bugs/1606489 ** This bug has been marked a duplicate of bug 1606489 Right clicking on the webbrowser-app location bar, the popup is blurry (e.g. Select All, Paste) -- 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/1630188 Title: tab options from context menu are unfocused Status in webbrowser-app package in Ubuntu: New Bug description: Enviroment: Desktp Xenial+overlay webbrowser app 0.23+15.04.20160928-0ubuntu1 Steps to reproduce: 1º Open webbrowser app and open 3 tabs 2º Right click over each tab Current result: Tab options are unfocused for all tabs except for the first one, that is correctly shown Expected result: Tab options should be all focused To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1630188/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1606489] Re: Right clicking on the webbrowser-app location bar, the popup is blurry (e.g. Select All, Paste)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1606489 Title: Contents of popover are blurry (not pixel-aligned?) Status in Canonical System Image: New Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Right clicking on the location bar, the popup is blurry (e.g. Select All, Paste). It looks like the pop-up is not pixel-aligned. The rest of the app, including right clicking on a web page is clear and has no such problem. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1606489/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1606489] Re: Contents of popover are blurry (not pixel-aligned?)
** Summary changed: - Right clicking on the webbrowser-app location bar, the popup is blurry (e.g. Select All, Paste) + Contents of popover are blurry (not pixel-aligned?) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1606489 Title: Contents of popover are blurry (not pixel-aligned?) Status in Canonical System Image: New Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: Right clicking on the location bar, the popup is blurry (e.g. Select All, Paste). It looks like the pop-up is not pixel-aligned. The rest of the app, including right clicking on a web page is clear and has no such problem. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1606489/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630191] Re: MTU settings not always applied after reboot
*** This bug is a duplicate of bug 1224007 *** https://bugs.launchpad.net/bugs/1224007 ** This bug has been marked a duplicate of bug 1224007 mtu not always set properly on bond/vlan interface -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1630191 Title: MTU settings not always applied after reboot Status in ifupdown package in Ubuntu: New Bug description: On a node with two 10G interfaces, we configure a bond interface from these two interfaces and then a vlan interface on top of it. The MTU of these interfaces shall be set to be 1550 instead of the default 1500, so we have these settings in /etc/network/interfaces.d: root@controller-node13:~# cat /etc/network/interfaces.d/xge0 auto xge0 iface xge0 inet manual bond-master xiondata root@controller-node13:~# cat /etc/network/interfaces.d/xge1 auto xge1 iface xge1 inet manual bond-master xiondata root@controller-node13:~# cat /etc/network/interfaces.d/xiondata auto xiondata iface xiondata inet manual bond-slaves xge0 xge1 bond-miimon 100 bond-lacp-rate 1 bond-mode 4 mtu 1550 root@controller-node13:~# cat /etc/network/interfaces.d/xiondata.200 auto xiondata.200 iface xiondata.200 inet static address 10.80.1.13/24 vlan_raw_device xiondata mtu 1550 After a reboot, the correct MTU is applied to the vlan interface only 50% of the time, on the other attempts, it stays at 1500, leading to broken connectivity. If I restart the interfaces manually, by doing "ifdown xiondata; ifup -a" the MTU settings seem to be applied correctly every time. root@controller-node13:~# apt policy ifupdown ifupdown: Installed: 0.8.10ubuntu1 Candidate: 0.8.10ubuntu1 Version table: *** 0.8.10ubuntu1 500 500 http://eu.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ifupdown 0.8.10ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Oct 4 09:44:40 2016 ProcEnviron: LANGUAGE=en_US: TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: ifupdown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1630191/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630211] [NEW] Moving a tab quickly when there are many tabs open, sometimes causes tab to left in a incorrect position
Public bug reported: What happened: 1) Open the webbrowser and many tabs 2) Select the first tab 3) Drag the tab quickly from the left side to the right 4) Notice that as you are dragging the tab lags and is sometimes left at a previous position (not the end) What I expected to happen: At step 4 for the tab to be in the correct position. This occurs because the tab move() only moves +/- 1 at any time, and is performed onXChanged. Which occurs from the animation of the change X position from the mouse. However if you move fast enough the animation skips certain values, causing some moves to be missed. ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Assignee: Andrew Hayzen (ahayzen) Status: In Progress ** Changed in: webbrowser-app (Ubuntu) Assignee: (unassigned) => Andrew Hayzen (ahayzen) ** Changed in: webbrowser-app (Ubuntu) Status: New => 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/1630211 Title: Moving a tab quickly when there are many tabs open, sometimes causes tab to left in a incorrect position Status in webbrowser-app package in Ubuntu: In Progress Bug description: What happened: 1) Open the webbrowser and many tabs 2) Select the first tab 3) Drag the tab quickly from the left side to the right 4) Notice that as you are dragging the tab lags and is sometimes left at a previous position (not the end) What I expected to happen: At step 4 for the tab to be in the correct position. This occurs because the tab move() only moves +/- 1 at any time, and is performed onXChanged. Which occurs from the animation of the change X position from the mouse. However if you move fast enough the animation skips certain values, causing some moves to be missed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1630211/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630090] Re: $XMODIFIERS not set correctly
Just updated the description. The problem is now understood, and we worked around the upstart bug in gnome-session and im-config. ** Description changed: + When "initctl set-env -g" is called, upstart calls D-Bus to also update + its activation environment (the environment that D-Bus activated + services get). There is a bug here: + + - SetEnv takes a parameter of the form "VARIABLE=VALUE" + - This is split on "=" to determine the two parts + - If the VALUE has an "=" character in it, everything after the first "=" is lost, because all "=" characters are split and not the first one + + In this case, XMODIFIERS=@im=ibus was being turned into XMODIFIERS=@im. + + upstart should only split on the first "=", and keep the rest of the + string unsplit. It doesn't look like nih_str_split is going to be very + helpful here. + + [ Original description ] + The XMODIFIERS environment variable is not set correctly. $ echo $XMODIFIERS @im $ The value should be - for ibus: "@im=ibus" - for fcitx: "@im=fcitx" - for xim: "@im=none" The issue is present in Ubuntu/Unity 16.10. I don't see it in Ubuntu GNOME, neither in Ubuntu 16.04. Actually I don't think the affected package is im-config, because the issue is present also after having downgraded im-config to 0.29-1ubuntu12 (the Xenial version). But I wanted to file the bug somewhere, so here it is. ** Changed in: im-config (Ubuntu) Status: New => Fix Committed ** Changed in: upstart (Ubuntu) Status: New => Triaged ** Changed in: upstart (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1630090 Title: $XMODIFIERS not set correctly Status in im-config package in Ubuntu: Fix Committed Status in upstart package in Ubuntu: Triaged Bug description: When "initctl set-env -g" is called, upstart calls D-Bus to also update its activation environment (the environment that D-Bus activated services get). There is a bug here: - SetEnv takes a parameter of the form "VARIABLE=VALUE" - This is split on "=" to determine the two parts - If the VALUE has an "=" character in it, everything after the first "=" is lost, because all "=" characters are split and not the first one In this case, XMODIFIERS=@im=ibus was being turned into XMODIFIERS=@im. upstart should only split on the first "=", and keep the rest of the string unsplit. It doesn't look like nih_str_split is going to be very helpful here. [ Original description ] The XMODIFIERS environment variable is not set correctly. $ echo $XMODIFIERS @im $ The value should be - for ibus: "@im=ibus" - for fcitx: "@im=fcitx" - for xim: "@im=none" The issue is present in Ubuntu/Unity 16.10. I don't see it in Ubuntu GNOME, neither in Ubuntu 16.04. Actually I don't think the affected package is im-config, because the issue is present also after having downgraded im-config to 0.29-1ubuntu12 (the Xenial version). But I wanted to file the bug somewhere, so here it is. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1630090/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1629275] Re: Clients all crash (and sometimes server too)
** Summary changed: - Clients and server all crash + Clients all crash (and sometimes server too) -- 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/1629275 Title: Clients all crash (and sometimes server too) Status in Mir: Incomplete Status in MirAL: Triaged Status in mir package in Ubuntu: New Bug description: mir-24 on yakkety (or mir-0.21 on xenial, or lp:mir on yakkety) Start a Mir-on-X11 session: $ mir_demo_server_minimal & $ mirrun gnome-terminal In the terminal: $ mir_demo_client_all& (A script that launches all the Mir demo clients - attached) Expect: all the clients open Actual (most times): gnome-terminal and all the clients crash Actual (frequently): gnome-terminal, all the clients, and the server crash Actual (occasionally): all the clients open The "frequent" server crash is lp:1607812, this bug is for the client crash To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1629275/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1628159] Re: power button doesn't react, camera, clock, broweser, telegram, notes crashes
Thank you for taking the time to report bugs. Unfortunately, the Nexus 5 is not an officially supported device. Please report bugs to the project that creates the port for the Nexus 5. ** Changed in: unity8 (Ubuntu) Status: New => Invalid -- 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/1628159 Title: power button doesn't react, camera, clock, broweser, telegram, notes crashes Status in unity8 package in Ubuntu: Invalid Bug description: On my Nexus 5 the power button doesn't react properly, camera, browser, clock, facebook, telegram, notes, weather crashes on startup ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity8 8.14+15.04.20160831.3-0ubuntu1 Uname: Linux 3.4.0-1-hammerhead armv7l ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf CurrentDesktop: Unity Date: Tue Sep 27 16:55:43 2016 InstallationDate: Installed on 2016-09-13 (14 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20160913-023544) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1628159/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1629275] Re: Clients all crash (and sometimes server too)
** Changed in: miral Status: Triaged => Invalid -- 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/1629275 Title: Clients all crash (and sometimes server too) Status in Mir: Incomplete Status in MirAL: Invalid Status in mir package in Ubuntu: New Bug description: mir-24 on yakkety (or mir-0.21 on xenial, or lp:mir on yakkety) Start a Mir-on-X11 session: $ mir_demo_server_minimal & $ mirrun gnome-terminal In the terminal: $ mir_demo_client_all& (A script that launches all the Mir demo clients - attached) Expect: all the clients open Actual (most times): gnome-terminal and all the clients crash Actual (frequently): gnome-terminal, all the clients, and the server crash Actual (occasionally): all the clients open The "frequent" server crash is lp:1607812, this bug is for the client crash To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1629275/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1443052] Re: User accounts login history showing incorrect history
This bug was fixed in the package gnome-control-center - 1:3.20.1-2ubuntu2 --- gnome-control-center (1:3.20.1-2ubuntu2) yakkety; urgency=medium * Cherrypick commits from the 3.20 branch since there was never a 3.20.2 release. See patch headers or git for descriptions of issues fixed. - 0002-mouse-Make-touchpad-capability-checking-on-wayland-w.patch - 0007-universal-access-allow-focus-on-row-switches.patch - 0008-mouse-allow-focus-on-switches-in-the-Touchpad-sectio.patch - 0014-network-fix-some-SSID-escaping-issues.patch - 0016-user-accounts-Fix-missing-records-in-the-history-dia.patch (LP: #1443052) - 0020-privacy-React-to-changes-in-permissions-store.patch - 0021-privacy-Update-for-PermissionStore-DBus-API-changes.patch - 0025-power-Fix-hiding-wi-fi-mobile-broadband-toggles.patch - 0026-power-Fix-wifi-device-state-when-opening-power-panel.patch - 0027-printers-Fix-compilation-warning.patch - 0028-display-Fix-possible-crash-on-startup.patch -- Jeremy Bicha Tue, 04 Oct 2016 06:52:59 -0400 ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1443052 Title: User accounts login history showing incorrect history Status in accountsservice: Unknown Status in gnome-control-center: Unknown Status in Ubuntu GNOME: Confirmed Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Confirmed Bug description: I have found that in "System Settings > User Accounts" that if you select an account and then select the button called "History" (which is meant to show the login history for that account), it will show you when you last logged in as "Session Started", but it will show that you "Session Ended" just before you login the next time. To clarify what I mean, let's say that yesterday I logged into my account on this machine at 14:29, and then sometime near 23:00 I logged out, and then this morning I logged into my account somewhere around 11:20, it will show this: Today 11:20 Session Started Today 11:19 Session Ended Yesterday, 14:29 Session Started So it assumes that the last session ended when you log into a new one, so the bug seems to be that it does not log when a session ends properly, and only logs it when a new session starts. I have attached a screenshot to show my example as I see it in the History GUI. I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04, Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME 3.20. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1443052/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1552100] Re: Move to .snap
** Also affects: ubuntu-rssreader-app Importance: Undecided Status: New ** Summary changed: - Move to .snap + Move to Snappy -- 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/1552100 Title: Move to Snappy Status in Canonical System Image: Opinion Status in Ubuntu Music App: Triaged Status in Ubuntu Notes app: Triaged Status in Telegram app: Triaged Status in Ubuntu Calendar App: In Progress Status in Ubuntu Clock App: Triaged Status in Ubuntu Document Viewer App: Triaged Status in Ubuntu File Manager App: Triaged Status in Ubuntu Shorts App: New Status in Ubuntu Terminal App: Triaged Status in Ubuntu Weather App: Triaged Status in webbrowser-app package in Ubuntu: Invalid Bug description: Move all packages and the system to .snap (snappy) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552100/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1552100] Re: Create .snap packages of core apps
** Summary changed: - Move to Snappy + Create .snap packages of core apps -- 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/1552100 Title: Create .snap packages of core apps Status in Canonical System Image: Opinion Status in Ubuntu Music App: Triaged Status in Ubuntu Notes app: Triaged Status in Telegram app: Triaged Status in Ubuntu Calendar App: In Progress Status in Ubuntu Clock App: Triaged Status in Ubuntu Document Viewer App: Triaged Status in Ubuntu File Manager App: Triaged Status in Ubuntu Shorts App: New Status in Ubuntu Terminal App: Triaged Status in Ubuntu Weather App: Triaged Status in webbrowser-app package in Ubuntu: Invalid Bug description: Move all packages and the system to .snap (snappy) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552100/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1489489] Re: The org.freedesktop.DBus.GetConnectionAppArmorSecurityContext() method is deprecated
** Branch linked: lp:~mardy/online-accounts-api/apparmor-1489489 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1489489 Title: The org.freedesktop.DBus.GetConnectionAppArmorSecurityContext() method is deprecated Status in Ubuntu Online Accounts API: Confirmed Status in apparmor package in Ubuntu: In Progress Status in content-hub package in Ubuntu: Confirmed Status in dbus package in Ubuntu: Triaged Status in media-hub package in Ubuntu: Confirmed Status in mediascanner2 package in Ubuntu: Fix Released Status in signon-apparmor-extension package in Ubuntu: Confirmed Status in ubuntu-download-manager package in Ubuntu: Confirmed Status in ubuntu-system-settings-online-accounts package in Ubuntu: Confirmed Bug description: When upstream D-Bus merged the AppArmor mediation patches, they did not like the GetConnectionAppArmorSecurityContext() bus method. Instead, they decided to expose a peer's AppArmor context using the org.freedesktop.DBus.GetConnectionCredentials() bus method. All users of the GetConnectionAppArmorSecurityContext() method should switch to the GetConnectionCredentials() method as soon as possible so that Ubuntu can drop the patch that implements GetConnectionAppArmorSecurityContext() by the time 16.04 LTS is released. In order to switch to the new method, you'll need to depend on libapparmor 2.10 or newer. I'll be adding example code that illustrates how to switch from GetConnectionAppArmorSecurityContext() to GetConnectionCredentials(). content-hub, media-hub, mediascanner2, signon-apparmor-extension, ubuntu-download-manager, and ubuntu-system-settings-online-accounts all need to transition to the new method of obtaining the AppArmor label. The apparmor package should be updated to drop the libapparmor- mention-dbus-method-in-getcon-man.patch patch and the dbus package should be updated to drop the aa-get-connection-apparmor-security- context.patch patch. To manage notifications about this bug go to: https://bugs.launchpad.net/online-accounts-api/+bug/1489489/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1165382] Re: No sound output/input to Plantronics .Audio 478 USB
16.04, now sound is ok, but no input from microphone. -- 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/1165382 Title: No sound output/input to Plantronics .Audio 478 USB Status in pulseaudio package in Ubuntu: Invalid Bug description: Plantronics .Audio 478 USB works well with Ubuntu 12.04. Ubuntu 13.04 beta2 has option for sound output to it but really sound outputs to standart laptop speakers. There is no Plantronics .Audio 478 in input devices list and sound input not work from it. lsusb: Bus 003 Device 004: ID 047f:c011 Plantronics, Inc. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: pulseaudio 1:3.0-0ubuntu4b2 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 4416 F pulseaudio /dev/snd/controlC0: ubuntu 3483 F pulseaudio ubuntu 4416 F pulseaudio /dev/snd/pcmC0D0c: ubuntu 3483 F...m pulseaudio CasperVersion: 1.330 Date: Sat Apr 6 11:57:20 2013 ExecutablePath: /usr/bin/pulseaudio LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2008 dmi.bios.vendor: Acer dmi.bios.version: V3.13 dmi.board.name: Navarro dmi.board.vendor: Acer dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrV3.13:bd08/22/2008:svnAcer:pnAspire5110:pvrV3.13:rvnAcer:rnNavarro:rvrN/A:cvnAcer:ct10:cvrN/A: dmi.product.name: Aspire 5110 dmi.product.version: V3.13 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1165382/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1629797] Re: resolve service in nsswitch.conf adds 25 seconds to failed lookups before systemd-resolved is up
A convenient way to test this is to install libnss-resolve and cloud-
init into a yakkety container. Then cloud-init will basically hang
forever, looping on
2016-10-04 12:58:48,716 - url_helper.py[WARNING]: Calling
'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed
[100/120s]: request error [HTTPConnectionPool(host='169.254.169.254',
port=80): Max retries exceeded with url: /2009-04-04/meta-data/instance-
id (Caused by
NewConnectionError(': Failed to establish a new connection: [Errno
113] No route to host',))]
and since cloud-init.service runs during early boot, not much else
(dbus, resolved, etc.) has started at that time. During that, name
resolution is indeed broken.
I think nss-resolve should quickly fall back to DNS if D-Bus isn't
running yet.
** Changed in: systemd (Ubuntu)
Status: New => Triaged
--
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/1629797
Title:
resolve service in nsswitch.conf adds 25 seconds to failed lookups
before systemd-resolved is up
Status in cloud-init package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
Triaged
Bug description:
During boot, cloud-init does DNS resolution checks to if particular
metadata services are available (in order to determine which cloud it
is running on). These checks happen before systemd-resolved is up[0]
and if they resolve unsuccessfully they take 25 seconds to complete.
This has substantial impact on boot time in all contexts, because
cloud-init attempts to resolve three known-invalid addresses ("does-
not-exist.example.com.", "example.invalid." and a random string) to
enable it to detect when it's running in an environment where a DNS
server will always return some sort of redirect. As such, we're
talking a minimum impact of 75 seconds in all environments. This
increases when cloud-init is configured to check for multiple
environments.
This means that yakkety is consistently taking 2-3 minutes to boot on
EC2 and GCE, compared to the ~30 seconds of the first boot and ~10
seconds thereafter in xenial.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1629797/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1617204] Re: NM does not offer VPN options
Solved. Turns out Lubuntu also needs network-manager-pptp-gnome -- 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/1617204 Title: NM does not offer VPN options Status in network-manager package in Ubuntu: New Bug description: network-manager-pptp is installed, but when I select "Configure VPN" NM offers only Hardware and Virtual options, no VPN options., Observed on two Lubuntu 16.04 and one LXLE 16.04 system; everything works as expected on Lubuntu 14.04. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.0-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Aug 26 09:05:44 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-08-08 (17 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) IpRoute: default via 172.16.0.27 dev wlp2s0 proto static metric 600 172.16.0.0/16 dev wlp2s0 proto kernel scope link src 172.16.0.182 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected /org/freedesktop/NetworkManager/Devices/0 haywiredcce62ca8-d2bd-480e-b67b-f4cf93a54d8b /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.0connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1617204/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1594944] Re: Setup.exec() for existing account type results in blank full screen window
** Changed in: canonical-devices-system-image Milestone: backlog => 14 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1594944 Title: Setup.exec() for existing account type results in blank full screen window Status in Canonical System Image: Fix Committed Status in webapps-sprint: In Progress Status in ubuntu-system-settings-online-accounts package in Ubuntu: Fix Released Bug description: If an account already exists, calling Setup.exec() again results in a blank window being overlaid on top of the application which made the request. There is no way to close this window. This API is what the online accounts integration in the scopes API relies upon, to allow logging in to accounts, and so we have come to rely upon this API as well in multiple places, as a means to log into the Ubuntu One account, when it is necessary to do so. However, due to this issue, the only way to reliably present a login window at an appropriate time, is to delete the account when it appears to have been invalidated by the server, and to then present the login window to create a new account. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1594944/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1629797] Re: resolve service in nsswitch.conf adds 25 seconds to failed lookups before systemd-resolved is up
Simpler reproducer without cloud-init: Add "ExecStartPre=/bin/sleep
1000" to /lib/systemd/system/dbus.service. This happens if dbus.socket
is already running, but dbus.service isn't yet as it's blocked by cloud-
init.service.
--
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/1629797
Title:
resolve service in nsswitch.conf adds 25 seconds to failed lookups
before systemd-resolved is up
Status in cloud-init package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
Triaged
Bug description:
During boot, cloud-init does DNS resolution checks to if particular
metadata services are available (in order to determine which cloud it
is running on). These checks happen before systemd-resolved is up[0]
and if they resolve unsuccessfully they take 25 seconds to complete.
This has substantial impact on boot time in all contexts, because
cloud-init attempts to resolve three known-invalid addresses ("does-
not-exist.example.com.", "example.invalid." and a random string) to
enable it to detect when it's running in an environment where a DNS
server will always return some sort of redirect. As such, we're
talking a minimum impact of 75 seconds in all environments. This
increases when cloud-init is configured to check for multiple
environments.
This means that yakkety is consistently taking 2-3 minutes to boot on
EC2 and GCE, compared to the ~30 seconds of the first boot and ~10
seconds thereafter in xenial.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1629797/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630090] Re: $XMODIFIERS not set correctly
This bug was fixed in the package im-config - 0.29-1ubuntu16 --- im-config (0.29-1ubuntu16) yakkety; urgency=medium * debian/user/im-config.service: Reverse the order of "initctl set-env" and "dbus-update-activation-environment". $XMODIFIERS can contain an "=" (its value might be, for example, "@im=ibus"). upstart forwards "set-env -g" calls to D-Bus, but it constructs the parameters to the call incorrectly and splits on "=" characters in the value, discarding anything which follows. We can work around this bug by calling "initctl set-env -g" first, and then "dbus-update-activation-environment" to overwrite the buggy value. (LP: #1630090) * debian/user/im-config.service: Get rid of one eval - "dbus-update-activation-environment" will look up the variable in the environment if you don't specify a value. -- Iain Lane Tue, 04 Oct 2016 12:28:35 +0100 ** Changed in: im-config (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 upstart in Ubuntu. https://bugs.launchpad.net/bugs/1630090 Title: $XMODIFIERS not set correctly Status in im-config package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Triaged Bug description: When "initctl set-env -g" is called, upstart calls D-Bus to also update its activation environment (the environment that D-Bus activated services get). There is a bug here: - SetEnv takes a parameter of the form "VARIABLE=VALUE" - This is split on "=" to determine the two parts - If the VALUE has an "=" character in it, everything after the first "=" is lost, because all "=" characters are split and not the first one In this case, XMODIFIERS=@im=ibus was being turned into XMODIFIERS=@im. upstart should only split on the first "=", and keep the rest of the string unsplit. It doesn't look like nih_str_split is going to be very helpful here. [ Original description ] The XMODIFIERS environment variable is not set correctly. $ echo $XMODIFIERS @im $ The value should be - for ibus: "@im=ibus" - for fcitx: "@im=fcitx" - for xim: "@im=none" The issue is present in Ubuntu/Unity 16.10. I don't see it in Ubuntu GNOME, neither in Ubuntu 16.04. Actually I don't think the affected package is im-config, because the issue is present also after having downgraded im-config to 0.29-1ubuntu12 (the Xenial version). But I wanted to file the bug somewhere, so here it is. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1630090/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1629797] Re: resolve service in nsswitch.conf adds 25 seconds to failed lookups before systemd-resolved is up
So, the root cause is completely clear: dbus.socket starts early, then
cloud-init starts which blocks the entire basic.target (early boot) on
network operations, thus dbus.service cannot start. nss-resolve already
sees dbus.socket and thus can connect (instead of failing fast), and
then gets the 25s D-Bus timeout as D-Bus is blocked.
- Moving dbus.service into early boot would be a bold step, and I don't
think such a large change is appropriate two weeks before release.
- Rearranging nsswitch.conf and modify it on the fly also sounds like a
big no.
- I'd also not like to generally move dbus.socket into late boot, as
that would break other services during early boot which queue up a
connection to D-Bus.
- So far the cleanest way out of this would be to also make dbus.socket
wait for cloud-init.service, as that already blocks dbus.service. I
verified that name resolution is then fast again. This also doesn't
cause dependency loops as both cloud-init.service and sockets.target run
in early boot.
Could you try adding "Before=dbus.socket" to /lib/systemd/system/cloud-
init.service and confirm that this helps? (Does for me in a container,
but I don't have access to GCE or EC2)
--
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/1629797
Title:
resolve service in nsswitch.conf adds 25 seconds to failed lookups
before systemd-resolved is up
Status in cloud-init package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
Triaged
Bug description:
During boot, cloud-init does DNS resolution checks to if particular
metadata services are available (in order to determine which cloud it
is running on). These checks happen before systemd-resolved is up[0]
and if they resolve unsuccessfully they take 25 seconds to complete.
This has substantial impact on boot time in all contexts, because
cloud-init attempts to resolve three known-invalid addresses ("does-
not-exist.example.com.", "example.invalid." and a random string) to
enable it to detect when it's running in an environment where a DNS
server will always return some sort of redirect. As such, we're
talking a minimum impact of 75 seconds in all environments. This
increases when cloud-init is configured to check for multiple
environments.
This means that yakkety is consistently taking 2-3 minutes to boot on
EC2 and GCE, compared to the ~30 seconds of the first boot and ~10
seconds thereafter in xenial.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1629797/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1165382] Re: No sound output/input to Plantronics .Audio 478 USB
UPDATE: working after disabling the Intel HD on motherboard, seem bug in Pulseaudio UI. -- 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/1165382 Title: No sound output/input to Plantronics .Audio 478 USB Status in pulseaudio package in Ubuntu: Invalid Bug description: Plantronics .Audio 478 USB works well with Ubuntu 12.04. Ubuntu 13.04 beta2 has option for sound output to it but really sound outputs to standart laptop speakers. There is no Plantronics .Audio 478 in input devices list and sound input not work from it. lsusb: Bus 003 Device 004: ID 047f:c011 Plantronics, Inc. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: pulseaudio 1:3.0-0ubuntu4b2 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 4416 F pulseaudio /dev/snd/controlC0: ubuntu 3483 F pulseaudio ubuntu 4416 F pulseaudio /dev/snd/pcmC0D0c: ubuntu 3483 F...m pulseaudio CasperVersion: 1.330 Date: Sat Apr 6 11:57:20 2013 ExecutablePath: /usr/bin/pulseaudio LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/22/2008 dmi.bios.vendor: Acer dmi.bios.version: V3.13 dmi.board.name: Navarro dmi.board.vendor: Acer dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrV3.13:bd08/22/2008:svnAcer:pnAspire5110:pvrV3.13:rvnAcer:rnNavarro:rvrN/A:cvnAcer:ct10:cvrN/A: dmi.product.name: Aspire 5110 dmi.product.version: V3.13 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1165382/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630245] [NEW] after starting ubuntu 16.10 -- no keyboard, no mouse
Public bug reported: After starting Ubuntu 16.10 keyboard and mouse are dead. Since it works with an older kernel but not with the latest one, I'd assume the newer kernel does not initialize the devices the right way. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Oct 4 15:27:52 2016 InstallationDate: Installed on 2012-12-12 (1391 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) 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 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago) dmi.bios.date: 07/02/2015 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/2015: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. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1630245 Title: after starting ubuntu 16.10 -- no keyboard, no mouse Status in systemd package in Ubuntu: New Bug description: After starting Ubuntu 16.10 keyboard and mouse are dead. Since it works with an older kernel but not with the latest one, I'd assume the newer kernel does not initialize the devices the right way. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Oct 4 15:27:52 2016 InstallationDate: Installed on 2012-12-12 (1391 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) 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 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago) dmi.bios.date: 07/02/2015 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/2015: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/systemd/+bug/1630245/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630243] [NEW] WebWhatsapp App (v. 1.02) - Problem when trying to record a message, issue with webview
Public bug reported: I'm trying to use your WebWhatsapp App (v. 1.02) and it works well on Meizu MX4. Starting from OTA 12 Ubuntu Touch web browser support the WebRTC Api, that permits to send audio message. But I have a problem to doing this. Here what I'm doing: 1. Open WebWhatsapp, and in a chat press the "microphone" icon; 2. I need to accept the microphone access permission every single time that I open the App, after that I need to click again on the microphone icon; 3. Then the recording starts; 4. After the end of the recording, if you try to record another audio message, you can't, the template open and close the keyboard and the recording doesn't start. 5. You need to close and reopen the App and starting again from point 1. Probably there's a problem with CSS and webview template. ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Description changed: I'm trying to use your WebWhatsapp App (v. 1.02) and it works well on Meizu MX4. Starting from OTA 12 Ubuntu Touch web browser support the WebRTC Api, that permits to send audio message. But I have a problem to doing this. Here what I'm doing: 1. Open WebWhatsapp, and in a chat press the "microphone" icon; - 2. I need to accept the microphone access permission every single time that I open the App and I click on the microphone icon; + 2. I need to accept the microphone access permission every single time that I open the App, after that I need to click again on the microphone icon; 3. Then the recording starts; 4. After the end of the recording, if you try to record another audio message, you can't, the template open and close the keyboard and the recording doesn't start. 5. You need to close and reopen the App and starting again from point 1. Probably there's a problem with CSS and webview template. -- 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/1630243 Title: WebWhatsapp App (v. 1.02) - Problem when trying to record a message, issue with webview Status in webbrowser-app package in Ubuntu: New Bug description: I'm trying to use your WebWhatsapp App (v. 1.02) and it works well on Meizu MX4. Starting from OTA 12 Ubuntu Touch web browser support the WebRTC Api, that permits to send audio message. But I have a problem to doing this. Here what I'm doing: 1. Open WebWhatsapp, and in a chat press the "microphone" icon; 2. I need to accept the microphone access permission every single time that I open the App, after that I need to click again on the microphone icon; 3. Then the recording starts; 4. After the end of the recording, if you try to record another audio message, you can't, the template open and close the keyboard and the recording doesn't start. 5. You need to close and reopen the App and starting again from point 1. Probably there's a problem with CSS and webview template. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1630243/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624381] Re: add additional shortcut support for zoom/unzoom in US keyboards
This bug was fixed in the package webbrowser-app - 0.23+16.10.20160928-0ubuntu1 --- webbrowser-app (0.23+16.10.20160928-0ubuntu1) yakkety; urgency=medium [ Andrew Hayzen ] * Change use of ActionList.actions to ActionList.children and use modelData in Repeaters (LP: #1624470) * Clip the Loader containing NewTabView so that it doesn't overlap the bottom edge hint (LP: #1568740) * Modify calendar ua-override to allow anything before google.com (allowing calendar.google.com) [ Olivier Tilloy ] * Add "Ctrl+=" and "Ctrl+_" as shortcuts for zoom in and zoom out actions, (LP: #1624381) * Strip out problematic apparmor rule that prevents camera detection on desktop (LP: #1626611) [ Andrew Hayzen, Olivier Tilloy ] * Multiple window support in webbrowser-app. -- Olivier Tilloy Wed, 28 Sep 2016 08:25:12 + ** Changed in: webbrowser-app (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 webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1624381 Title: add additional shortcut support for zoom/unzoom in US keyboards Status in webbrowser-app package in Ubuntu: Fix Released Bug description: On US keyboards, the "+" (plus) key is in shifted position, and the "-" (minus) is not. All the other browsers (chrome, chromium, firefox) support the following shortcuts for zoom/unzoom and we should do the same, so user does not have to press ctrl+shift as that is not expected. zoom in: ctrl+plus ctrl+equals zoom out: ctrl+underscore ctrl+minus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1624381/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1626611] Re: camera not detected when running confined on desktop
This bug was fixed in the package webbrowser-app - 0.23+16.10.20160928-0ubuntu1 --- webbrowser-app (0.23+16.10.20160928-0ubuntu1) yakkety; urgency=medium [ Andrew Hayzen ] * Change use of ActionList.actions to ActionList.children and use modelData in Repeaters (LP: #1624470) * Clip the Loader containing NewTabView so that it doesn't overlap the bottom edge hint (LP: #1568740) * Modify calendar ua-override to allow anything before google.com (allowing calendar.google.com) [ Olivier Tilloy ] * Add "Ctrl+=" and "Ctrl+_" as shortcuts for zoom in and zoom out actions, (LP: #1624381) * Strip out problematic apparmor rule that prevents camera detection on desktop (LP: #1626611) [ Andrew Hayzen, Olivier Tilloy ] * Multiple window support in webbrowser-app. -- Olivier Tilloy Wed, 28 Sep 2016 08:25:12 + ** Changed in: webbrowser-app (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 webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1626611 Title: camera not detected when running confined on desktop Status in apparmor-easyprof-ubuntu package in Ubuntu: Invalid Status in webbrowser-app package in Ubuntu: Fix Released Bug description: Running on xenial + xenial overlay. The camera cannot be accessed. Seeing the following apparmor denials: bfiller@blackhorse:~$ tail -f /var/log/syslog | grep DEN Sep 22 11:14:11 blackhorse dbus[1811]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/gtk/vfs/Daemon" interface="org.gtk.vfs.Daemon" member="ListMonitorImplementations" mask="send" name=":1.7" pid=4207 label="webbrowser-app" peer_pid=1919 peer_label="unconfined" Sep 22 11:14:11 blackhorse kernel: [ 2448.215755] audit: type=1400 audit(1474557251.512:59): apparmor="DENIED" operation="open" profile="webbrowser-app" name="/usr/share/gvfs/remote-volume-monitors/" pid=4207 comm="webbrowser-app" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Sep 22 11:14:11 blackhorse kernel: [ 2448.224997] audit: type=1400 audit(1474557251.524:60): apparmor="DENIED" operation="open" profile="webbrowser-app" name="/sys/bus/" pid=4207 comm="webbrowser-app" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Sep 22 11:14:11 blackhorse kernel: [ 2448.225064] audit: type=1400 audit(1474557251.524:61): apparmor="DENIED" operation="open" profile="webbrowser-app" name="/sys/class/drm/" pid=4207 comm="webbrowser-app" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Sep 22 11:14:11 blackhorse dbus[1811]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker" member="ListMountableInfo" mask="send" name=":1.7" pid=4207 label="webbrowser-app" peer_pid=1919 peer_label="unconfined" Sep 22 11:14:11 blackhorse kernel: [ 2448.663730] audit: type=1400 audit(1474557251.960:62): apparmor="DENIED" operation="open" profile="webbrowser-app//oxide_helper" name="/sys/devices/system/cpu/cpufreq/policy0/cpuinfo_max_freq" pid=4220 comm="oxide-renderer" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Sep 22 11:14:11 blackhorse kernel: [ 2448.670941] audit: type=1400 audit(1474557251.968:63): apparmor="DENIED" operation="open" profile="webbrowser-app//oxide_helper" name="/opt/google/chrome/PepperFlash/manifest.json" pid=4220 comm="oxide-renderer" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Sep 22 11:14:11 blackhorse kernel: [ 2448.675938] audit: type=1400 audit(1474557251.972:64): apparmor="DENIED" operation="open" profile="webbrowser-app" name="/sys/bus/" pid=4207 comm="webbrowser-app" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Sep 22 11:14:11 blackhorse kernel: [ 2448.675983] audit: type=1400 audit(1474557251.972:65): apparmor="DENIED" operation="open" profile="webbrowser-app" name="/sys/class/drm/" pid=4207 comm="webbrowser-app" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Sep 22 11:14:11 blackhorse kernel: [ 2448.680663] audit: type=1400 audit(1474557251.976:66): apparmor="DENIED" operation="open" profile="webbrowser-app" name="/opt/google/chrome/PepperFlash/manifest.json" pid=4207 comm="webbrowser-app" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Sep 22 11:14:12 blackhorse kernel: [ 2448.723161] audit: type=1400 audit(1474557252.020:67): apparmor="DENIED" operation="open" profile="webbrowser-app" name="/dev/shm/lttng-ust-wait-6-1000" pid=4243 comm="QQmlThread" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Sep 22 11:14:12 blackhorse kernel: [ 2448.723181] audit: type=1400 audit(1474557252.020:68): apparmor="DENIED" operation="open" profile="webbrowser-app" name="/dev/shm/lttng-ust-wait-6" pid=4242 comm="QQmlThread" requested_mask="r" denied_mask="r" fsuid=1000 ouid=108 Sep 22 11:14:17 blackhorse kernel: [ 2453.723913] audit: type=1400 audit(14
[Touch-packages] [Bug 1568740] Re: top sites previews overlap bottom edge bar
This bug was fixed in the package webbrowser-app - 0.23+16.10.20160928-0ubuntu1 --- webbrowser-app (0.23+16.10.20160928-0ubuntu1) yakkety; urgency=medium [ Andrew Hayzen ] * Change use of ActionList.actions to ActionList.children and use modelData in Repeaters (LP: #1624470) * Clip the Loader containing NewTabView so that it doesn't overlap the bottom edge hint (LP: #1568740) * Modify calendar ua-override to allow anything before google.com (allowing calendar.google.com) [ Olivier Tilloy ] * Add "Ctrl+=" and "Ctrl+_" as shortcuts for zoom in and zoom out actions, (LP: #1624381) * Strip out problematic apparmor rule that prevents camera detection on desktop (LP: #1626611) [ Andrew Hayzen, Olivier Tilloy ] * Multiple window support in webbrowser-app. -- Olivier Tilloy Wed, 28 Sep 2016 08:25:12 + ** Changed in: webbrowser-app (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 webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1568740 Title: top sites previews overlap bottom edge bar Status in webbrowser-app package in Ubuntu: Fix Released Bug description: Visible on a phone with a bluetooth mouse connected. A screenshot is worth a thousand words, see attached one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1568740/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624470] Re: webbrowser_app.tests.test_contextmenu.TestContextMenuTextArea.test_actions hangs on desktop
This bug was fixed in the package webbrowser-app - 0.23+16.10.20160928-0ubuntu1 --- webbrowser-app (0.23+16.10.20160928-0ubuntu1) yakkety; urgency=medium [ Andrew Hayzen ] * Change use of ActionList.actions to ActionList.children and use modelData in Repeaters (LP: #1624470) * Clip the Loader containing NewTabView so that it doesn't overlap the bottom edge hint (LP: #1568740) * Modify calendar ua-override to allow anything before google.com (allowing calendar.google.com) [ Olivier Tilloy ] * Add "Ctrl+=" and "Ctrl+_" as shortcuts for zoom in and zoom out actions, (LP: #1624381) * Strip out problematic apparmor rule that prevents camera detection on desktop (LP: #1626611) [ Andrew Hayzen, Olivier Tilloy ] * Multiple window support in webbrowser-app. -- Olivier Tilloy Wed, 28 Sep 2016 08:25:12 + ** Changed in: webbrowser-app (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 webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1624470 Title: webbrowser_app.tests.test_contextmenu.TestContextMenuTextArea.test_actions hangs on desktop Status in webbrowser-app package in Ubuntu: Fix Released Bug description: This is a fairly recent regression, that test used to pass reliably on desktop. As not much has changed in the browser code itself, I suspect changes somewhere else in the stack maybe. When run on my xenial+overlay laptop in a unity7 session, webbrowser_app.tests.test_contextmenu.TestContextMenuTextArea.test_actions hangs and eventually times out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1624470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1605511] Re: openssl engine error if trying to exploit hw crypto on z due to library issue
** Changed in: openssl (Ubuntu) Status: Confirmed => Invalid ** Changed in: libica (Ubuntu) Status: Confirmed => Invalid ** Also affects: openssl (Ubuntu Yakkety) Importance: Undecided Assignee: Dimitri John Ledkov (xnox) Status: Invalid ** Also affects: libica (Ubuntu Yakkety) Importance: Undecided Assignee: Dimitri John Ledkov (xnox) Status: Invalid ** Also affects: openssl-ibmca (Ubuntu Yakkety) Importance: Undecided Assignee: Dimitri John Ledkov (xnox) Status: Confirmed ** Also affects: openssl (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: libica (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: openssl-ibmca (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: openssl (Ubuntu Xenial) Status: New => Invalid ** Changed in: openssl-ibmca (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: libica (Ubuntu Xenial) Status: New => Invalid ** Changed in: openssl-ibmca (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1605511 Title: openssl engine error if trying to exploit hw crypto on z due to library issue Status in libica package in Ubuntu: Invalid Status in openssl package in Ubuntu: Invalid Status in openssl-ibmca package in Ubuntu: Confirmed Status in libica source package in Xenial: Invalid Status in openssl source package in Xenial: Invalid Status in openssl-ibmca source package in Xenial: Confirmed Status in libica source package in Yakkety: Invalid Status in openssl source package in Yakkety: Invalid Status in openssl-ibmca source package in Yakkety: Confirmed Bug description: openssl-ibmca usually requires libica2 and libica-utils for proper functioning and all required tooling (like icainfo, icastats, etc.) But after the installation of these packages and the configuration, with is like this: sudo tee -a /etc/ssl/openssl.cnf < /usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample sudo vi /etc/ssl/openssl.cnf adding the following line as the first active one: openssl_conf = openssl_def and removing or commenting all other occurrences of that line in the config file and saving and closing the openssl.cnf file this output of the openssl engine command is expected: $ openssl engine (dynamic) Dynamic engine loading support (ibmca) Ibmca hardware engine support or even more precise these chiphers should be listed in case of "-c": $ openssl engine -c (dynamic) Dynamic engine loading support (ibmca) Ibmca hardware engine support [RAND, DES-ECB, DES-CBC, DES-OFB, DES-CFB, DES-EDE3, DES-EDE3-CBC, DES-EDE3-OFB, DES-EDE3-CFB, AES-128-ECB, AES-192-ECB, AES-256-ECB, AES-128-CBC, AES-192-CBC, AES-256-CBC, AES-128-OFB, AES-192-OFB, AES-256-OFB, AES-128-CFB, AES-192-CFB, AES-256-CFB, SHA1, SHA256, SHA512] But instead openssl is giving this error, due to a missing "libica.so": $ openssl engine Error configuring OpenSSL 4395950360208:error:25066067:DSO support routines:DLFCN_LOAD:could not load the shared library:dso_dlfcn.c:187:filename(libica.so): libica.so: cannot open shared object file: No such file or directory 4395950360208:error:25070067:DSO support routines:DSO_load:could not load the shared library:dso_lib.c:233: 4395950360208:error:80066068:lib(128):IBMCA_INIT:dso failure:e_ibmca.c:1286: 4395950360208:error:25066067:DSO support routines:DLFCN_LOAD:could not load the shared library:dso_dlfcn.c:187:filename(libica.so): libica.so: cannot open shared object file: No such file or directory 4395950360208:error:25070067:DSO support routines:DSO_load:could not load the shared library:dso_lib.c:233: 4395950360208:error:80066068:lib(128):IBMCA_INIT:dso failure:e_ibmca.c:1286: 4395950360208:error:260BC066:engine routines:INT_ENGINE_CONFIGURE:engine configuration error:eng_cnf.c:191:section=ibmca_section, name=init, value=1 4395950360208:error:0E07606D:configuration file routines:MODULE_RUN:module initialization error:conf_mod.c:223:module=engines, value=engine_section, retcode=-1 $ There is no libica.so that is shipped with any of the above packages (verified with dpkg -l) or otherwise available in the filesystem: $ sudo find / -name "libica.so" 2>/dev/null ubuntu@HWE0001:~$ But there is a different verison of that libica: $ sudo find / -name "*libica.so*" 2>/dev/null /usr/lib/s390x-linux-gnu/libica.so.2 /usr/lib/s390x-linux-gnu/libica.so.2.6.1 $ So there are right now two workarounds: 1) creating a (symbolic) link from libica.so.2 to libica.so, like $ sudo ln -s /usr/lib/s390x-linux-gnu/libica.so.2 /usr/lib/s390x-linux-gnu/libica.so that allows openssl to find a library named 'libica.so': 18:15:00: frank.hei...@canonical.com:
[Touch-packages] [Bug 1276186] Re: System becomes unresponsive, ibus-ui-daemon takes ~150 % cpu
I had the same issue on ubuntu 16.04. When I used F2 to rename files, nautilus crashed when I did it to the third file. After that I didn't give up. Still the nautilus crashed when I left-clicked the nautilus. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1276186 Title: System becomes unresponsive, ibus-ui-daemon takes ~150 % cpu Status in ibus package in Ubuntu: Confirmed Bug description: As stated the graphical desktop became unresponsive. Dropping to CTRL + ALT + F1 terminal and `top`showed ibus-ui-daemon taking around 150 % cpu time and ibus-ui-gtk3 taking around 50 % cpu time. (names may contain minor errors) Tried to kill processes, rebooted. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ibus 1.5.3-6ubuntu2.1 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Tue Feb 4 16:41:03 2014 InstallationDate: Installed on 2013-09-10 (147 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: ibus UpgradeStatus: Upgraded to saucy on 2013-10-23 (104 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1276186/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1629863] Re: snap apps require hardcode --desktop-file-hint to launch
So we think this is qtmir resolving the apparmor label incorrectly. Apparmor labels are now "snap.$(pkg).$(app)" instead of "$(pkg)_$(app)" so it isn't getting the AppID of the application correctly. ** Also affects: qtmir Importance: Undecided Status: New ** Changed in: qtmir Status: New => Confirmed ** Changed in: ubuntu-app-launch (Ubuntu) Status: Confirmed => Invalid ** Changed in: unity8 (Ubuntu) Status: Confirmed => Invalid -- 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/1629863 Title: snap apps require hardcode --desktop-file-hint to launch Status in Canonical System Image: Confirmed Status in QtMir: Confirmed Status in ubuntu-app-launch package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: Apps installed by snap does not launch from dash icon unless you hardcode the wrapper file adding "--desktop_file_hint=unity8" on the argument list. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1629863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1629275] Re: Clients all crash (and sometimes server too)
Console log from gnome-terminal (with MIR_CLIENT_RPC_REPORT=log) [2016-10-04 15:41:58.721290] rpc: Invocation request: id: 52 method_name: submit_buffer [2016-10-04 15:41:58.721397] rpc: Invocation succeeded: id: 52 method_name: submit_buffer [2016-10-04 15:41:58.727375] rpc: Invocation request: id: 53 method_name: submit_buffer [2016-10-04 15:41:58.727437] rpc: Invocation succeeded: id: 53 method_name: submit_buffer [2016-10-04 15:41:58.737226] rpc: Result received: id: 52 [2016-10-04 15:41:58.737269] rpc: Complete response: id: 52 [2016-10-04 15:41:58.739094] rpc: Result received: id: 53 [2016-10-04 15:41:58.739187] rpc: Complete response: id: 53 *** Error in `/usr/lib/gnome-terminal/gnome-terminal-server': double free or corruption (out): 0x7f90bcb0c010 *** === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(+0x7911b)[0x7f90d96d311b] /lib/x86_64-linux-gnu/libc.so.6(+0x827aa)[0x7f90d96dc7aa] /lib/x86_64-linux-gnu/libc.so.6(cfree+0x4c)[0x7f90d96e01dc] ** Tags added: gtk-mir -- 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/1629275 Title: Clients all crash (and sometimes server too) Status in Mir: Incomplete Status in MirAL: Invalid Status in mir package in Ubuntu: New Bug description: mir-24 on yakkety (or mir-0.21 on xenial, or lp:mir on yakkety) Start a Mir-on-X11 session: $ mir_demo_server_minimal & $ mirrun gnome-terminal In the terminal: $ mir_demo_client_all& (A script that launches all the Mir demo clients - attached) Expect: all the clients open Actual (most times): gnome-terminal and all the clients crash Actual (frequently): gnome-terminal, all the clients, and the server crash Actual (occasionally): all the clients open The "frequent" server crash is lp:1607812, this bug is for the client crash To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1629275/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
I am having the laggy bluetooth mouse issue with a Logitech MX Anywhere 2 and a Lenovo T450s. The modprobe suggestion from @cribari has worked for me so far, but I've only done 5 minutes of testing at this point, and only one suspend- resume cycle. Order of operations: 1) suspend/resume/suspend/resume, etc. 2) turn on bluetooth on notebook (mouse was paired weeks ago) [10:19:31 in log below] 3) turn on mouse and experience lag [10:19:36 in log below] 4) execute these commands "sudo modprobe -rv btusb && sleep 1s && sudo modprobe -v btusb" [10:22:33 in log below] 5) mouse is no longer laggy 6) suspend/resume (once) 7) mouse is still not laggy, and appears to be working fine Oct 4 10:19:31 tbob kernel: [588896.204026] Bluetooth: hci0: read Intel version: 370810011003110e00 Oct 4 10:19:31 tbob kernel: [588896.205078] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq Oct 4 10:19:31 tbob kernel: [588896.521054] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated Oct 4 10:19:31 tbob systemd[1]: Reached target Bluetooth. Oct 4 10:19:31 tbob bluetoothd[3094]: Failed to obtain handles for "Service Changed" characteristic Oct 4 10:19:31 tbob bluetoothd[3094]: Not enough free handles to register service Oct 4 10:19:31 tbob bluetoothd[3094]: Error adding Link Loss service Oct 4 10:19:31 tbob bluetoothd[3094]: Not enough free handles to register service Oct 4 10:19:31 tbob bluetoothd[3094]: message repeated 2 times: [ Not enough free handles to register service] Oct 4 10:19:31 tbob bluetoothd[3094]: Current Time Service could not be registered Oct 4 10:19:31 tbob bluetoothd[3094]: gatt-time-server: Input/output error (5) Oct 4 10:19:31 tbob bluetoothd[3094]: Not enough free handles to register service Oct 4 10:19:31 tbob bluetoothd[3094]: Not enough free handles to register service Oct 4 10:19:31 tbob bluetoothd[3094]: Sap driver initialization failed. Oct 4 10:19:31 tbob bluetoothd[3094]: sap-server: Operation not permitted (1) Oct 4 10:19:31 tbob bluetoothd[3094]: Endpoint registered: sender=:1.72 path=/MediaEndpoint/A2DPSource Oct 4 10:19:31 tbob bluetoothd[3094]: Endpoint registered: sender=:1.72 path=/MediaEndpoint/A2DPSink Oct 4 10:19:36 tbob bluetoothd[3094]: Unable to register GATT service with handle 0x000c for device EA:4C:A8:24:2D:95 Oct 4 10:19:36 tbob bluetoothd[3094]: Unable to register GATT service with handle 0x001b for device EA:4C:A8:24:2D:95 Oct 4 10:19:36 tbob bluetoothd[3094]: Unable to register GATT service with handle 0x003f for device EA:4C:A8:24:2D:95 Oct 4 10:19:37 tbob bluetoothd[3094]: bt_uhid_send: Invalid argument (22) Oct 4 10:19:37 tbob kernel: [588902.501689] input: MX Anywhere 2 as /devices/virtual/misc/uhid/0005:046D:B013.007C/input/input95 Oct 4 10:19:37 tbob kernel: [588902.502135] hid-generic 0005:046D:B013.007C: input,hidraw4: BLUETOOTH HID v0.07 Keyboard [MX Anywhere 2] on 10:02:B5:80:73:A1 Oct 4 10:19:37 tbob bluetoothd[3094]: message repeated 12 times: [ bt_uhid_send: Invalid argument (22)] Oct 4 10:22:33 tbob kernel: [589078.328418] usbcore: deregistering interface driver btusb Oct 4 10:22:33 tbob systemd[1]: bluetooth.target: Unit not needed anymore. Stopping. Oct 4 10:22:33 tbob systemd[1]: Stopped target Bluetooth. Oct 4 10:22:33 tbob bluetoothd[3094]: Endpoint unregistered: sender=:1.72 path=/MediaEndpoint/A2DPSource Oct 4 10:22:33 tbob bluetoothd[3094]: Endpoint unregistered: sender=:1.72 path=/MediaEndpoint/A2DPSink Oct 4 10:22:34 tbob kernel: [589079.485951] usbcore: registered new interface driver btusb Oct 4 10:22:34 tbob kernel: [589079.500790] Bluetooth: hci0: read Intel version: 370810011003110e23 Oct 4 10:22:34 tbob kernel: [589079.500793] Bluetooth: hci0: Intel device is already patched. patch num: 23 Oct 4 10:22:34 tbob bluetoothd[3094]: Failed to obtain handles for "Service Changed" characteristic Oct 4 10:22:34 tbob bluetoothd[3094]: Not enough free handles to register service Oct 4 10:22:34 tbob bluetoothd[3094]: Error adding Link Loss service Oct 4 10:22:34 tbob bluetoothd[3094]: Not enough free handles to register service Oct 4 10:22:34 tbob bluetoothd[3094]: message repeated 2 times: [ Not enough free handles to register service] Oct 4 10:22:34 tbob bluetoothd[3094]: Current Time Service could not be registered Oct 4 10:22:34 tbob bluetoothd[3094]: gatt-time-server: Input/output error (5) Oct 4 10:22:34 tbob bluetoothd[3094]: Not enough free handles to register service Oct 4 10:22:34 tbob systemd[1]: Reached target Bluetooth. Oct 4 10:22:34 tbob bluetoothd[3094]: Not enough free handles to register service Oct 4 10:22:34 tbob bluetoothd[3094]: Sap driver initialization failed. Oct 4 10:22:34 tbob bluetoothd[3094]: sap-server: Operation not permitted (1) Oct 4 10:22:34 tbob bluetoothd[3094]: Endpoint registered: sender=:1.72 path=/MediaEndpoint/A2DPSource Oct 4 10:22:34 tbob bluetoothd[3094]: Endpoint registered: se
[Touch-packages] [Bug 1630245] Re: after starting ubuntu 16.10 -- no keyboard, no mouse
** Package changed: systemd (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1630245 Title: after starting ubuntu 16.10 -- no keyboard, no mouse Status in linux package in Ubuntu: New Bug description: After starting Ubuntu 16.10 keyboard and mouse are dead. Since it works with an older kernel but not with the latest one, I'd assume the newer kernel does not initialize the devices the right way. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Oct 4 15:27:52 2016 InstallationDate: Installed on 2012-12-12 (1391 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) 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 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago) dmi.bios.date: 07/02/2015 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/2015: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/linux/+bug/1630245/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1565804] Re: ifup of vlan interfaces failing during networking start - RTNETLINK answers: File exists
*** This bug is a duplicate of bug 1224007 *** https://bugs.launchpad.net/bugs/1224007 ** This bug has been marked a duplicate of bug 1224007 mtu not always set properly on bond/vlan interface -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1565804 Title: ifup of vlan interfaces failing during networking start - RTNETLINK answers: File exists Status in ifupdown package in Ubuntu: Confirmed Bug description: /e/n/i: auto lo iface lo inet loopback dns-nameservers 10.245.168.2 dns-search dellstack auto eth0 iface eth0 inet static gateway 10.245.168.1 address 10.245.168.17/21 dns-nameservers 10.245.168.2 mtu 1500 auto eth1 iface eth1 inet manual mtu 1500 auto eth1.2667 iface eth1.2667 inet static address 10.245.184.20/24 vlan-raw-device eth1 mtu 9000 vlan_id 2667 output from networking startup: ● networking.service - Raise network interfaces Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled) Drop-In: /run/systemd/generator/networking.service.d └─50-insserv.conf-$network.conf Active: failed (Result: exit-code) since Mon 2016-04-04 12:14:26 UTC; 1h 33min ago Docs: man:interfaces(5) Process: 1255 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE) Process: 868 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list --exclude=lo)" ] && udevadm settle (code=exited, Main PID: 1255 (code=exited, status=1/FAILURE) Apr 04 12:14:25 reflecting-attraction systemd[1]: Starting Raise network interfaces... Apr 04 12:14:26 reflecting-attraction ifup[1255]: Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config Apr 04 12:14:26 reflecting-attraction ifup[1255]: RTNETLINK answers: File exists Apr 04 12:14:26 reflecting-attraction ifup[1255]: Failed to bring up eth1.2667. Apr 04 12:14:26 reflecting-attraction systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE Apr 04 12:14:26 reflecting-attraction systemd[1]: Failed to start Raise network interfaces. Apr 04 12:14:26 reflecting-attraction systemd[1]: networking.service: Unit entered failed state. Apr 04 12:14:26 reflecting-attraction systemd[1]: networking.service: Failed with result 'exit-code'. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ifupdown 0.8.10ubuntu1 ProcVersionSignature: User Name 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 Date: Mon Apr 4 13:42:48 2016 SourcePackage: ifupdown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1565804/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630278] [NEW] Multiple selector cursors present in Notes app
Public bug reported: Hi, If I open Notes on my phone and create or edit a note, then activate a cursor/selector and keep it active while switching out and back to the app again I can now see the old handles (can't get rid of those) and I can create a new one. This way I can bring up as many cursors/selectors as I'd like. The old ones are not usable, but they are present when clearly they should not, as visible in the attached screenshot. I am running rc-proposed on MX4 - and yesterday was the first time I've seen this behaviour but I am not sure if it is a new bug or not. Thank you ** Affects: reminders-app Importance: Undecided Status: New ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "screenshot20161003_121837232.png" https://bugs.launchpad.net/bugs/1630278/+attachment/4754339/+files/screenshot20161003_121837232.png ** Also affects: reminders-app Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1630278 Title: Multiple selector cursors present in Notes app Status in Ubuntu Notes app: New Status in unity8 package in Ubuntu: New Bug description: Hi, If I open Notes on my phone and create or edit a note, then activate a cursor/selector and keep it active while switching out and back to the app again I can now see the old handles (can't get rid of those) and I can create a new one. This way I can bring up as many cursors/selectors as I'd like. The old ones are not usable, but they are present when clearly they should not, as visible in the attached screenshot. I am running rc-proposed on MX4 - and yesterday was the first time I've seen this behaviour but I am not sure if it is a new bug or not. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/reminders-app/+bug/1630278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1625595] Re: Libre Office Icons unreadability on YY with Intel Drivers
** Also affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New -- 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/1625595 Title: Libre Office Icons unreadability on YY with Intel Drivers Status in xorg package in Ubuntu: Incomplete Status in xserver-xorg-video-intel package in Ubuntu: New Bug description: glxinfo | grep -i vendor server glx vendor string: SGI client glx vendor string: Mesa Project and SGI Vendor: Intel Open Source Technology Center (0x8086) OpenGL vendor string: Intel Open Source Technology Center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1625595/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1576698] Re: ntpdate-debian not working
This bug was fixed in the package ntp - 1:4.2.8p4+dfsg-3ubuntu5.2 --- ntp (1:4.2.8p4+dfsg-3ubuntu5.2) xenial; urgency=medium * Fix ntpdate-debian to be able to parse new config of ntp (LP: #1576698) -- Christian Ehrhardt Tue, 20 Sep 2016 14:24:29 +0200 ** Changed in: ntp (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 ntp in Ubuntu. https://bugs.launchpad.net/bugs/1576698 Title: ntpdate-debian not working Status in ntp package in Ubuntu: Fix Released Status in ntp source package in Xenial: Fix Released Status in ntp package in Debian: New Bug description: [Impact] * ntpdate-debian fails to work if ntp is installed at the same time due to a conflict in the updated ntp config to the ntpdate-debian script. [Test Case] # e.g. spawn xenial container # Note: only occurs when ntp is installed as well $ apt-get install ntpdate ntp $ ntpdate-debian (Note for latter verification enable proposed in that container and re-update ntpdate) [Regression Potential] * There could exists a custom user conf that had a mixed server AND pool specified, that now will use the first of both types while instead formerly it would have used the first server entry. The chance for this is super-low IMHO, but this case exists. in 16.04 I get this # ntpdate-debian 28 Apr 09:54:14 ntpdate[30747]: no servers can be used, exiting The problem is that ntpdate-debian parse /etc/ntp.conf, searchin for the word "server", but the format of the file as changed a bit < server 0.ubuntu.pool.ntp.org < server 1.ubuntu.pool.ntp.org < server 2.ubuntu.pool.ntp.org < server 3.ubuntu.pool.ntp.org --- > pool 0.ubuntu.pool.ntp.org iburst > pool 1.ubuntu.pool.ntp.org iburst > pool 2.ubuntu.pool.ntp.org iburst > pool 3.ubuntu.pool.ntp.org iburst 25c24 < server ntp.ubuntu.com --- > pool ntp.ubuntu.com the word server as been replaced by "pool" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1576698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1627013] Re: Qt Drag and Drop across two windows of the same app is not detected
** Also affects: qtmir (Ubuntu) Importance: Undecided Status: New ** Also affects: qtmir Importance: Undecided Status: New ** No longer affects: qtmir ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: qtmir (Ubuntu) Assignee: (unassigned) => Nick Dedekind (nick-dedekind) ** Changed in: qtmir (Ubuntu) Status: New => Confirmed ** No longer affects: unity8 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1627013 Title: Qt Drag and Drop across two windows of the same app is not detected Status in Canonical System Image: New Status in Mir: New Status in mir package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Bug description: What happened: 1) Installed multi-window silo for the webbrowser [0] and installed demo app [1] 2) Launched the multi window drag and drop example app, note sometimes the windows are spawned on top of each other, so you may need to move one to see both 3) Attempt to drag one of the red boxes into the centre of the other window 4) Notice that on unity7 the centre of the window turns green whereas on unity8 nothing happens 5) Notice on unity7 that when the mouse is released the red box is moved into that window What I expected to happen: On unity8 for it to act the same as unity7, for the drag handle to work correctly and for the window droparea detection to work. Note at step 3 while dragging the box that on unity7 a handle correctly appears near the mouse and follows it, whereas on unity8 it spawns a window with the image for the handle but it doesn't follow the mouse. I am assuming this is linked to other existing bugs within unity8/mir where showing menus appear in separate windows? But I'm not sure which bug that is? I am currently assuming that either the increased security of Mir between windows is preventing the Qt drag system from being to detect when the mouse is over another window? (even though they are the same app) Or is the issue that this functionality has not been implemented yet? I have the a xenial desktop with the stable overlay and the multi- window silo for the webbrowser [0]. The demo mini-app I have linked to this bug and can be found at [1]. Let me know if you need help running it. The use case for this scenario, is moving tabs in the webbrowser between multiple windows and dragging a tab out of a window to spawn a new window. 0 - https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-084/+packages 1 - https://code.launchpad.net/~ahayzen/+junk/multi-window-dnd-cpp-001 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1627013/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1629863] Re: snap apps require hardcode --desktop-file-hint to launch
** No longer affects: unity8 (Ubuntu) ** Also affects: qtmir (Ubuntu) Importance: Undecided Status: New ** No longer affects: qtmir ** Changed in: qtmir (Ubuntu) Status: New => Confirmed ** Changed in: qtmir (Ubuntu) Assignee: (unassigned) => Nick Dedekind (nick-dedekind) ** Changed in: qtmir (Ubuntu) Importance: Undecided => High ** No longer affects: ubuntu-app-launch (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1629863 Title: snap apps require hardcode --desktop-file-hint to launch Status in Canonical System Image: Confirmed Status in qtmir package in Ubuntu: Confirmed Bug description: Apps installed by snap does not launch from dash icon unless you hardcode the wrapper file adding "--desktop_file_hint=unity8" on the argument list. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1629863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1576698] Update Released
The verification of the Stable Release Update for ntp 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 ntp in Ubuntu. https://bugs.launchpad.net/bugs/1576698 Title: ntpdate-debian not working Status in ntp package in Ubuntu: Fix Released Status in ntp source package in Xenial: Fix Released Status in ntp package in Debian: New Bug description: [Impact] * ntpdate-debian fails to work if ntp is installed at the same time due to a conflict in the updated ntp config to the ntpdate-debian script. [Test Case] # e.g. spawn xenial container # Note: only occurs when ntp is installed as well $ apt-get install ntpdate ntp $ ntpdate-debian (Note for latter verification enable proposed in that container and re-update ntpdate) [Regression Potential] * There could exists a custom user conf that had a mixed server AND pool specified, that now will use the first of both types while instead formerly it would have used the first server entry. The chance for this is super-low IMHO, but this case exists. in 16.04 I get this # ntpdate-debian 28 Apr 09:54:14 ntpdate[30747]: no servers can be used, exiting The problem is that ntpdate-debian parse /etc/ntp.conf, searchin for the word "server", but the format of the file as changed a bit < server 0.ubuntu.pool.ntp.org < server 1.ubuntu.pool.ntp.org < server 2.ubuntu.pool.ntp.org < server 3.ubuntu.pool.ntp.org --- > pool 0.ubuntu.pool.ntp.org iburst > pool 1.ubuntu.pool.ntp.org iburst > pool 2.ubuntu.pool.ntp.org iburst > pool 3.ubuntu.pool.ntp.org iburst 25c24 < server ntp.ubuntu.com --- > pool ntp.ubuntu.com the word server as been replaced by "pool" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1576698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1605511] Re: openssl engine error if trying to exploit hw crypto on z due to library issue
Please try packages from: sudo add-apt-repository ppa:ci-train-ppa-service/2043 sudo apt update sudo apt full-upgrade With packages there, libica.so is still attempted to be loaded first. If that fails, libica.so.2 is attempted to be loaded, and that should succeed. Before: $ openssl engine ibmca (ibmca) Ibmca hardware engine support 4396855273104:error:25066067:DSO support routines:DLFCN_LOAD:could not load the shared library:dso_dlfcn.c:187:filename(libica.so): libica.so: cannot open shared object file: No such file or directory 4396855273104:error:25070067:DSO support routines:DSO_load:could not load the shared library:dso_lib.c:233: 4396855273104:error:80066068:lib(128):IBMCA_INIT:dso failure:e_ibmca.c:1286: After: $ openssl engine ibmca (ibmca) Ibmca hardware engine support 4396661810832:error:25066067:DSO support routines:DLFCN_LOAD:could not load the shared library:dso_dlfcn.c:187:filename(libica.so): libica.so: cannot open shared object file: No such file or directory 4396661810832:error:25070067:DSO support routines:DSO_load:could not load the shared library:dso_lib.c:233: Which is still a bit ugly messaging, but should work out of the box. ** Changed in: openssl-ibmca (Ubuntu Xenial) Status: Confirmed => In Progress ** Changed in: openssl-ibmca (Ubuntu Yakkety) Status: Confirmed => Fix Committed ** Changed in: openssl-ibmca (Ubuntu Yakkety) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1605511 Title: openssl engine error if trying to exploit hw crypto on z due to library issue Status in libica package in Ubuntu: Invalid Status in openssl package in Ubuntu: Invalid Status in openssl-ibmca package in Ubuntu: Fix Committed Status in libica source package in Xenial: Invalid Status in openssl source package in Xenial: Invalid Status in openssl-ibmca source package in Xenial: In Progress Status in libica source package in Yakkety: Invalid Status in openssl source package in Yakkety: Invalid Status in openssl-ibmca source package in Yakkety: Fix Committed Bug description: openssl-ibmca usually requires libica2 and libica-utils for proper functioning and all required tooling (like icainfo, icastats, etc.) But after the installation of these packages and the configuration, with is like this: sudo tee -a /etc/ssl/openssl.cnf < /usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample sudo vi /etc/ssl/openssl.cnf adding the following line as the first active one: openssl_conf = openssl_def and removing or commenting all other occurrences of that line in the config file and saving and closing the openssl.cnf file this output of the openssl engine command is expected: $ openssl engine (dynamic) Dynamic engine loading support (ibmca) Ibmca hardware engine support or even more precise these chiphers should be listed in case of "-c": $ openssl engine -c (dynamic) Dynamic engine loading support (ibmca) Ibmca hardware engine support [RAND, DES-ECB, DES-CBC, DES-OFB, DES-CFB, DES-EDE3, DES-EDE3-CBC, DES-EDE3-OFB, DES-EDE3-CFB, AES-128-ECB, AES-192-ECB, AES-256-ECB, AES-128-CBC, AES-192-CBC, AES-256-CBC, AES-128-OFB, AES-192-OFB, AES-256-OFB, AES-128-CFB, AES-192-CFB, AES-256-CFB, SHA1, SHA256, SHA512] But instead openssl is giving this error, due to a missing "libica.so": $ openssl engine Error configuring OpenSSL 4395950360208:error:25066067:DSO support routines:DLFCN_LOAD:could not load the shared library:dso_dlfcn.c:187:filename(libica.so): libica.so: cannot open shared object file: No such file or directory 4395950360208:error:25070067:DSO support routines:DSO_load:could not load the shared library:dso_lib.c:233: 4395950360208:error:80066068:lib(128):IBMCA_INIT:dso failure:e_ibmca.c:1286: 4395950360208:error:25066067:DSO support routines:DLFCN_LOAD:could not load the shared library:dso_dlfcn.c:187:filename(libica.so): libica.so: cannot open shared object file: No such file or directory 4395950360208:error:25070067:DSO support routines:DSO_load:could not load the shared library:dso_lib.c:233: 4395950360208:error:80066068:lib(128):IBMCA_INIT:dso failure:e_ibmca.c:1286: 4395950360208:error:260BC066:engine routines:INT_ENGINE_CONFIGURE:engine configuration error:eng_cnf.c:191:section=ibmca_section, name=init, value=1 4395950360208:error:0E07606D:configuration file routines:MODULE_RUN:module initialization error:conf_mod.c:223:module=engines, value=engine_section, retcode=-1 $ There is no libica.so that is shipped with any of the above packages (verified with dpkg -l) or otherwise available in the filesystem: $ sudo find / -name "libica.so" 2>/dev/null ubuntu@HWE0001:~$ But there is a different verison of that libica: $ sudo find / -name "*libica.so*" 2>/dev/null /usr/lib/s390x-linux-gnu/libica.so.2 /usr
[Touch-packages] [Bug 1628260] Re: Upgrade libglew package to also include libglew2
libglew2 seems to be included in Debian unstable: https://launchpad.net/debian/+source/glew -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glew in Ubuntu. https://bugs.launchpad.net/bugs/1628260 Title: Upgrade libglew package to also include libglew2 Status in glew package in Ubuntu: New Bug description: Currently glew package only includes versions up to 1.13, but the latest release is 2.0. As a developer, it would be best to have libglew2 and libglew2-dev available on Ubuntu. See http://glew.sourceforge.net/ for more information about the new (and previous) version(s). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glew/+bug/1628260/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630090] Re: Upstart sets D-Bus activation environment incorrectly if variable's value contains an "=" (was: $XMODIFIERS not set correctly)
** Summary changed: - $XMODIFIERS not set correctly + Upstart sets D-Bus activation environment incorrectly if variable's value contains an "=" (was: $XMODIFIERS not set correctly) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1630090 Title: Upstart sets D-Bus activation environment incorrectly if variable's value contains an "=" (was: $XMODIFIERS not set correctly) Status in im-config package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Triaged Bug description: When "initctl set-env -g" is called, upstart calls D-Bus to also update its activation environment (the environment that D-Bus activated services get). There is a bug here: - SetEnv takes a parameter of the form "VARIABLE=VALUE" - This is split on "=" to determine the two parts - If the VALUE has an "=" character in it, everything after the first "=" is lost, because all "=" characters are split and not the first one In this case, XMODIFIERS=@im=ibus was being turned into XMODIFIERS=@im. upstart should only split on the first "=", and keep the rest of the string unsplit. It doesn't look like nih_str_split is going to be very helpful here. [ Original description ] The XMODIFIERS environment variable is not set correctly. $ echo $XMODIFIERS @im $ The value should be - for ibus: "@im=ibus" - for fcitx: "@im=fcitx" - for xim: "@im=none" The issue is present in Ubuntu/Unity 16.10. I don't see it in Ubuntu GNOME, neither in Ubuntu 16.04. Actually I don't think the affected package is im-config, because the issue is present also after having downgraded im-config to 0.29-1ubuntu12 (the Xenial version). But I wanted to file the bug somewhere, so here it is. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1630090/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1522414] Re: [Ubuntu 15.10] GDB improvements
** Tags removed: targetmilestone-inin1610 ** Tags added: targetmilestone-inin1704 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1522414 Title: [Ubuntu 15.10] GDB improvements Status in gdb package in Ubuntu: Invalid Bug description: This is a feature to track the new features on GDB on Ubuntu 15.10. The request is to add TAR register support, PPR, DSCR as miscellaneous registers. This request also covers a set of TM related ptrace requests covering related SPR and various check-pointed registers. Leader: Edjunior Barbosa Bugs: https://bugs.launchpad.net/tasty-taco/+bug/1278706 ( gdb not able to display TAR register ) == Comment: #1 - Edjunior Barbosa Machado - 2014-07-11 10:27:00 == It depends on kernel enablement, updating Power ptrace interface to have access to the new registers (bug #104280) == Comment: #2 - Breno Henrique Leitao - 2014-07-14 08:45:19 == Ed, It seems that the patch was finally accepted in https://git.kernel.org/cgit/linux/kernel/git/next/linux- next.git/commit/?id=96d016108640bc2b7fb0ee800737f80923847294 Is it correct? == Comment: #3 - Edjunior Barbosa Machado - 2014-07-14 08:54:37 == (In reply to comment #2) > Ed, > > It seems that the patch was finally accepted in > > https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/ > ?id=96d016108640bc2b7fb0ee800737f80923847294 > > Is it correct? This is actually a fix for a issue related to DSCR value that were being discussed when the ptrace patch was submitted (as mentioned in https://bugzilla.linux.ibm.com/show_bug.cgi?id=104280#c5). The patchset updating the ptrace interface to include the new registers is still waiting for review in the kernel mailing list. == Comment: #4 - Breno Henrique Leitao - 2014-07-14 15:49:53 == > the patchset > updating the ptrace interface to include the new registers is still waiting > for review in the kernel mailing list. Right, what is the status on the GDB part? Is it already done, or, does it depend on those patches accepted before starting the development? == Comment: #5 - Edjunior Barbosa Machado - 2014-07-14 16:15:07 == (In reply to comment #4) > > the patchset > > updating the ptrace interface to include the new registers is still waiting > > for review in the kernel mailing list. > Right, what is the status on the GDB part? Is it already done, or, does it > depend on those patches accepted before starting the development? GDB part is depending on the kernel side patches to start the development. == Comment: #6 - Breno Henrique Leitao - 2014-08-25 16:22:58 == This is going to be deferred to Ubuntu 15.04. Si Yuan, let me know if it doesn't work for you. == Comment: #7 - Application Cdeadmin - 2014-11-10 12:01:35 == default problem description == Comment: #11 - Breno Henrique Leitao - 2015-01-27 07:15:01 == Deferring to 15.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1522414/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1576989] Re: stale lock files freeze apps
I just ran into this with Contacts. The lock file was created in April
but removing it restored the app. Seems it got corrupted on a recent
run. I was testing startup time and opening and closing the apps.
Do we have any line on a fix for this? or is it no longer present for
5.6?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1576989
Title:
stale lock files freeze apps
Status in Canonical System Image:
Confirmed
Status in qtbase-opensource-src package in Ubuntu:
Confirmed
Status in qtbase-opensource-src package in Ubuntu RTM:
Confirmed
Bug description:
Debugging why the Notes app would freeze for some people, I found
there were some stale .lock files around. Those .lock files are
autocreated by QSettings (with QLockFile) when this file is edited.
Problem is, that it sometimes seems to happen that the app is
suspended by our lifecycle and then killed (either by closing from
spread or OOM killed) and those .lock files stick around. I have
implemented a workaround in the notes app[1] to clear up those stale
locks when the app starts app, however, today I ran twice in a row
into the issue that the very same happened to music app. It would just
freeze on startup and never come back. Digging around a bit I found
such a stale lock file on its config file which is created with the
QML Settings element. This implies that every app using QSettings or
QML Settings {} are potentially affected. I suspect many more app
freezes can be traced down to this.
Now, there is some code in Qt to detect stale lock files [2], however,
not sure why it doesn't detect those lock files as stale ones and
decides to wait on them forever though. Probably a bug in the code or
some of the wrong #ifdefs are triggered for our package builds.
[1]
https://code.launchpad.net/~mzanetti/reminders-app/remove-stale-lock-files/+merge/293355
[2]
http://code.qt.io/cgit/qt/qtbase.git/tree/src/corelib/io/qlockfile_unix.cpp
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1576989/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630291] [NEW] last update tension
Public bug reported: after last update, no more desktop : no button no sidebar nothing just the background pict and info coming like wifi connection... i tried the recovery mode but still. thanks for your help, work.. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Oct 4 19:39:41 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:246a] Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 940M] [1043:246a] InstallationDate: Installed on 2016-05-08 (149 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: ASUSTeK COMPUTER INC. X556UB ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=d89eb2d2-2577-4fc1-a25e-748f361946c0 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X556UB.402 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X556UB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX556UB.402:bd03/09/2016:svnASUSTeKCOMPUTERINC.:pnX556UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X556UB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Oct 4 18:02:09 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 14573 vendor AUO xserver.version: 2:1.18.3-1ubuntu2.3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1630291 Title: last update tension Status in xorg package in Ubuntu: New Bug description: after last update, no more desktop : no button no sidebar nothing just the background pict and info coming like wifi connection... i tried the recovery mode but still. thanks for your help, work.. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Oct 4 19:39:41 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:246a] Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 940M] [1043:246a] InstallationDate: Installed on 2016-05-08 (149 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: ASUSTeK COMPUTER INC. X556UB ProcEnviron: LANGUAGE=fr_FR PAT
[Touch-packages] [Bug 1624014] Update Released
The verification of the Stable Release Update for klibc 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 klibc in Ubuntu. https://bugs.launchpad.net/bugs/1624014 Title: Wrong bit set in klibc PXE dhcp/bootp flags Status in klibc package in Ubuntu: Fix Released Status in klibc source package in Trusty: Fix Committed Status in klibc source package in Xenial: Fix Released Status in klibc source package in Yakkety: Fix Released Bug description: [Description] The patch for bug 1327412 set the wrong bit in the bootp flags field. It set flags to 0x800, but the correct value is 0x8000. That sets the "broadcast" bit, and the spec requires all other bits to be 0. Setting one of the "must be zero" bits in the flags field causes some DHCP relay agents to drop the packets, causing PXE to fail. [Test Case] Get a DHCP relay agent that drops PXE packets with an invalid bootp.flags bit set, and try to PXE boot; it fails. [Regression] None, the previous patch introduced this regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1624014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624014] Re: Wrong bit set in klibc PXE dhcp/bootp flags
This bug was fixed in the package klibc - 2.0.4-8ubuntu1.16.04.2 --- klibc (2.0.4-8ubuntu1.16.04.2) xenial; urgency=medium * debian/patches/fix_broadcast_flag-bit.patch: the previous patch set the wrong bit in the bootp flags field, instead of 0x800 it must be 0x8000. (LP: #1624014) -- Dan Streetman Tue, 20 Sep 2016 14:20:36 -0500 ** Changed in: klibc (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 klibc in Ubuntu. https://bugs.launchpad.net/bugs/1624014 Title: Wrong bit set in klibc PXE dhcp/bootp flags Status in klibc package in Ubuntu: Fix Released Status in klibc source package in Trusty: Fix Committed Status in klibc source package in Xenial: Fix Released Status in klibc source package in Yakkety: Fix Released Bug description: [Description] The patch for bug 1327412 set the wrong bit in the bootp flags field. It set flags to 0x800, but the correct value is 0x8000. That sets the "broadcast" bit, and the spec requires all other bits to be 0. Setting one of the "must be zero" bits in the flags field causes some DHCP relay agents to drop the packets, causing PXE to fail. [Test Case] Get a DHCP relay agent that drops PXE packets with an invalid bootp.flags bit set, and try to PXE boot; it fails. [Regression] None, the previous patch introduced this regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1624014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630297] [NEW] open window titles not shown in launcher menu
Public bug reported: webbrowser-app with multi-window support just landed and works in unity8 the launcher icon shows dots representing the windows, but when right clicking on the launcher icon I expected to see the window titles in the menu (like unity7) but these are not shown ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1630297 Title: open window titles not shown in launcher menu Status in unity8 package in Ubuntu: New Bug description: webbrowser-app with multi-window support just landed and works in unity8 the launcher icon shows dots representing the windows, but when right clicking on the launcher icon I expected to see the window titles in the menu (like unity7) but these are not shown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1630297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630090] Re: Upstart sets D-Bus activation environment incorrectly if variable's value contains an "=" (was: $XMODIFIERS not set correctly)
Can confirm that XMODIFIERS is set correctly with the latest versions of the im-config and gnome-session-* packages. Thanks for a quick workaround. :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1630090 Title: Upstart sets D-Bus activation environment incorrectly if variable's value contains an "=" (was: $XMODIFIERS not set correctly) Status in im-config package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Triaged Bug description: When "initctl set-env -g" is called, upstart calls D-Bus to also update its activation environment (the environment that D-Bus activated services get). There is a bug here: - SetEnv takes a parameter of the form "VARIABLE=VALUE" - This is split on "=" to determine the two parts - If the VALUE has an "=" character in it, everything after the first "=" is lost, because all "=" characters are split and not the first one In this case, XMODIFIERS=@im=ibus was being turned into XMODIFIERS=@im. upstart should only split on the first "=", and keep the rest of the string unsplit. It doesn't look like nih_str_split is going to be very helpful here. [ Original description ] The XMODIFIERS environment variable is not set correctly. $ echo $XMODIFIERS @im $ The value should be - for ibus: "@im=ibus" - for fcitx: "@im=fcitx" - for xim: "@im=none" The issue is present in Ubuntu/Unity 16.10. I don't see it in Ubuntu GNOME, neither in Ubuntu 16.04. Actually I don't think the affected package is im-config, because the issue is present also after having downgraded im-config to 0.29-1ubuntu12 (the Xenial version). But I wanted to file the bug somewhere, so here it is. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1630090/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1621413] Re: 16.10 default wallpapers
Is this any better? ** Attachment added: "test2.png" https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1621413/+attachment/4754359/+files/test2.png -- 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/1621413 Title: 16.10 default wallpapers Status in ubuntu-wallpapers package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: New Bug description: Attached are the new wallpapers for 16.10. They are in PNG_8, PNG_24 and the same for greyscale, along with mobile formatted ones. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1621413/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1627013] Re: Qt Drag and Drop across two windows of the same app is not detected
We do not yet have support for drag and drop between windows. -- 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/1627013 Title: Qt Drag and Drop across two windows of the same app is not detected Status in Canonical System Image: New Status in Mir: New Status in mir package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Confirmed Bug description: What happened: 1) Installed multi-window silo for the webbrowser [0] and installed demo app [1] 2) Launched the multi window drag and drop example app, note sometimes the windows are spawned on top of each other, so you may need to move one to see both 3) Attempt to drag one of the red boxes into the centre of the other window 4) Notice that on unity7 the centre of the window turns green whereas on unity8 nothing happens 5) Notice on unity7 that when the mouse is released the red box is moved into that window What I expected to happen: On unity8 for it to act the same as unity7, for the drag handle to work correctly and for the window droparea detection to work. Note at step 3 while dragging the box that on unity7 a handle correctly appears near the mouse and follows it, whereas on unity8 it spawns a window with the image for the handle but it doesn't follow the mouse. I am assuming this is linked to other existing bugs within unity8/mir where showing menus appear in separate windows? But I'm not sure which bug that is? I am currently assuming that either the increased security of Mir between windows is preventing the Qt drag system from being to detect when the mouse is over another window? (even though they are the same app) Or is the issue that this functionality has not been implemented yet? I have the a xenial desktop with the stable overlay and the multi- window silo for the webbrowser [0]. The demo mini-app I have linked to this bug and can be found at [1]. Let me know if you need help running it. The use case for this scenario, is moving tabs in the webbrowser between multiple windows and dragging a tab out of a window to spawn a new window. 0 - https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-084/+packages 1 - https://code.launchpad.net/~ahayzen/+junk/multi-window-dnd-cpp-001 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1627013/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380364] Re: lightdm writes XDISPLAY instead of tty device name to utmp record
> We could filter out non-graphical logins by checking if the tty is less than 7 gdm3 in Ubuntu GNOME 16.10 (and backported to 16.04 via the Staging PPA because why not?) starts on vt1 and the first login is vt2, etc. That change was made in Debian's gdm3 packaging. -- 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/1380364 Title: lightdm writes XDISPLAY instead of tty device name to utmp record Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: New Status in Light Display Manager 1.14 series: New Status in Light Display Manager 1.16 series: New Status in lightdm package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: In Progress Bug description: Until now, I've been using good old gdm-2.20.11 and wanted to switch to lightdm-1.12.1. If you list users logged in via the 'w' or 'who' command, it shows you who is logged in and what they are doing. Especially, on which tty. Example: USER TTYLOGIN@ IDLE JCPU PCPU WHAT usertty9 03Oct14 16days 1:52m 0.01s /bin/sh /etc/xdg/xfce4/xinitrc -- /etc/X11/xinit/xserverrc Also, 'who' gives this information: usertty9 Oct 3 22:34 (:20) However, lightdm does not follow that tradition. Instead, it prints :0 instead of the actual tty, and something weird for other values (like ?xdm? instead of the idle value etc.) 'w': USER TTYLOGIN@ IDLE JCPU PCPU WHAT user:019:50 ?xdm? 23.82s 0.01s /bin/sh /etc/xdg/xfce4/xinitrc -- /etc/X11/xinit/xserverrc Note: :0 is not tty, it is DISPLAY env. 'who': user:0 2014-10-12 19:50 (:0) The same for this one. I wonder, is this a bug (to me it seems so, because for every other program the correct values are reported)? It is a problem for me, because I have written scripts for automation etc. that parse w and who output to determine which tty is in use by which DISPLAY. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1380364/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1628474] Re: keyboard keys in GtkShortcuts should have different color than background
** Tags removed: rls-y-tracking ** Tags added: rls-y-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1628474 Title: keyboard keys in GtkShortcuts should have different color than background Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: Many GNOME apps have a new Keyboard Shortcuts popup window available in their app menu (this feature was introduced in GTK 3.20). Ambiance and Radiance don't style this window correctly - there's no contrast between the displayed keyboard keys and the background. I'm attaching screenshots of evince's Keyboard Shortcuts popup (available in Help > Keyboard Shortcuts) with Ambiance and Adwaita. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1628474/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1443052] Re: User accounts login history showing incorrect history
** Also affects: gnome-control-center (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: accountsservice (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: unity-control-center (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: accountsservice (Ubuntu Xenial) Importance: Undecided => Low ** Changed in: accountsservice (Ubuntu Xenial) Status: New => Triaged ** Changed in: gnome-control-center (Ubuntu Xenial) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu Xenial) Status: New => Triaged ** Changed in: unity-control-center (Ubuntu Xenial) Importance: Undecided => Low ** Changed in: unity-control-center (Ubuntu Xenial) Status: New => Triaged ** Changed in: ubuntu-gnome Status: Confirmed => Triaged ** Changed in: ubuntu-gnome Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1443052 Title: User accounts login history showing incorrect history Status in accountsservice: Unknown Status in gnome-control-center: Unknown Status in Ubuntu GNOME: Triaged Status in accountsservice package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Confirmed Status in accountsservice source package in Xenial: Triaged Status in gnome-control-center source package in Xenial: Triaged Status in unity-control-center source package in Xenial: Triaged Bug description: I have found that in "System Settings > User Accounts" that if you select an account and then select the button called "History" (which is meant to show the login history for that account), it will show you when you last logged in as "Session Started", but it will show that you "Session Ended" just before you login the next time. To clarify what I mean, let's say that yesterday I logged into my account on this machine at 14:29, and then sometime near 23:00 I logged out, and then this morning I logged into my account somewhere around 11:20, it will show this: Today 11:20 Session Started Today 11:19 Session Ended Yesterday, 14:29 Session Started So it assumes that the last session ended when you log into a new one, so the bug seems to be that it does not log when a session ends properly, and only logs it when a new session starts. I have attached a screenshot to show my example as I see it in the History GUI. I have found this bug to be present in Ubuntu 14.04, Ubuntu 15.04, Ubuntu GNOME 15.10 with GNOME 3.18, and Ubuntu GNOME 16.04 with GNOME 3.20. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1443052/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630310] Re: Please add degree to the list of special charaters
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-keyboard (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1630310 Title: Please add degree to the list of special charaters Status in ubuntu-keyboard package in Ubuntu: Confirmed Bug description: Hi, I am constantly missing degree (°) character on my Ubuntu Phone which means that I am unable to write stuff like "It seems it will be almost freezing at night, Google says it should only be 4°C early in the morning". From time to time I have the urge to complain about the weather and then I would like to send stuff like this via Telegram to some people just as I did when I was still using Android. So could this bee please added to the Ubuntu keyboard? Thank you very much To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1630310/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630309] [NEW] plasma panel auto hide - panel disappears and does not come back
Public bug reported: I have to open plasmashellrc and set planelVisibility to 0 to make it return. Simple reboot doesn't solve the problem. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Tue Oct 4 13:33:15 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: kubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0591] InstallationDate: Installed on 2016-07-27 (68 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 3421 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed root=UUID=11cb0acd-e2d1-4040-8e64-08167dfa22cf ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/07/2014:svnDellInc.:pnInspiron3421:pvrNotSpecified:rvnDellInc.:rn:rvrA12:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3421 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Oct 4 08:52:12 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5238 vendor CMN xserver.version: 2:1.18.3-1ubuntu2.3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kubuntu third-party-packages 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/1630309 Title: plasma panel auto hide - panel disappears and does not come back Status in xorg package in Ubuntu: New Bug description: I have to open plasmashellrc and set planelVisibility to 0 to make it return. Simple reboot doesn't solve the problem. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Tue Oct 4 13:33:15 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: kubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0591] InstallationDate: Installed on 2016-07-27 (68 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 3421 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic.efi.signed root=UUID=11cb0acd-e2d1-4040-8e64-08167dfa22cf ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/07/2014:svnDellInc.:pnInspiron3421:pvrNotSpecified:rvnDellInc.:rn:rvrA12:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3421 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2
[Touch-packages] [Bug 1630310] [NEW] Please add degree to the list of special charaters
Public bug reported: Hi, I am constantly missing degree (°) character on my Ubuntu Phone which means that I am unable to write stuff like "It seems it will be almost freezing at night, Google says it should only be 4°C early in the morning". >From time to time I have the urge to complain about the weather and then I >would like to send stuff like this via Telegram to some people just as I did >when I was still using Android. So could this bee please added to the Ubuntu >keyboard? Thank you very much ** Affects: ubuntu-keyboard (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1630310 Title: Please add degree to the list of special charaters Status in ubuntu-keyboard package in Ubuntu: Confirmed Bug description: Hi, I am constantly missing degree (°) character on my Ubuntu Phone which means that I am unable to write stuff like "It seems it will be almost freezing at night, Google says it should only be 4°C early in the morning". From time to time I have the urge to complain about the weather and then I would like to send stuff like this via Telegram to some people just as I did when I was still using Android. So could this bee please added to the Ubuntu keyboard? Thank you very much To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1630310/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1617005] Re: [MIR] zmqpp
Pre-promoting per discussion with management, to unblock building of images with unity8 enabled so these get some burn-in before release. Override component to main zmqpp 4.1.2-0ubuntu1 in yakkety: universe/libs -> main libzmqpp-dev 4.1.2-0ubuntu1 in yakkety amd64: universe/libdevel/optional/100% -> main libzmqpp-dev 4.1.2-0ubuntu1 in yakkety arm64: universe/libdevel/optional/100% -> main libzmqpp-dev 4.1.2-0ubuntu1 in yakkety armhf: universe/libdevel/optional/100% -> main libzmqpp-dev 4.1.2-0ubuntu1 in yakkety i386: universe/libdevel/optional/100% -> main libzmqpp-dev 4.1.2-0ubuntu1 in yakkety powerpc: universe/libdevel/optional/100% -> main libzmqpp-dev 4.1.2-0ubuntu1 in yakkety ppc64el: universe/libdevel/optional/100% -> main libzmqpp-dev 4.1.2-0ubuntu1 in yakkety s390x: universe/libdevel/optional/100% -> main libzmqpp4 4.1.2-0ubuntu1 in yakkety amd64: universe/libs/optional/100% -> main libzmqpp4 4.1.2-0ubuntu1 in yakkety arm64: universe/libs/optional/100% -> main libzmqpp4 4.1.2-0ubuntu1 in yakkety armhf: universe/libs/optional/100% -> main libzmqpp4 4.1.2-0ubuntu1 in yakkety i386: universe/libs/optional/100% -> main libzmqpp4 4.1.2-0ubuntu1 in yakkety powerpc: universe/libs/optional/100% -> main libzmqpp4 4.1.2-0ubuntu1 in yakkety ppc64el: universe/libs/optional/100% -> main libzmqpp4 4.1.2-0ubuntu1 in yakkety s390x: universe/libs/optional/100% -> main 15 publications overridden. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zmqpp in Ubuntu. https://bugs.launchpad.net/bugs/1617005 Title: [MIR] zmqpp Status in zmqpp package in Ubuntu: New Bug description: [Availability] * Available in universe. [Rationale] * This package is required by unity-scopes-api. [Security] * No known security issues at this time, it has been in active use on our touch devices since a very long time already. [Quality assurance] * This package comes with a set of unit tests that are all being run during build-time. [Dependencies] Most dependencies are already in main, with only a small nitpick: * libboost-test-dev is in universe, but its source boost-defaults is already in main. * zeromq3 has a MIR filled as well (https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1597439) [Maintenance] * This package is used by Canonical upstream projects so the packaging is maintained by Canonical. The upstream code is actively maintained and developed by the zeromq team. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zmqpp/+bug/1617005/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1612461] Re: [MIR] unity-scopes-api
Override component to main unity-scopes-api 1.0.7+16.10.20160921-0ubuntu2 in yakkety: universe/libs -> main libunity-scopes-cli 1.0.7+16.10.20160921-0ubuntu2 in yakkety amd64: universe/devel/optional/100% -> main libunity-scopes-cli 1.0.7+16.10.20160921-0ubuntu2 in yakkety arm64: universe/devel/optional/100% -> main libunity-scopes-cli 1.0.7+16.10.20160921-0ubuntu2 in yakkety armhf: universe/devel/optional/100% -> main libunity-scopes-cli 1.0.7+16.10.20160921-0ubuntu2 in yakkety i386: universe/devel/optional/100% -> main libunity-scopes-cli 1.0.7+16.10.20160921-0ubuntu2 in yakkety powerpc: universe/devel/optional/100% -> main libunity-scopes-cli 1.0.7+16.10.20160921-0ubuntu2 in yakkety ppc64el: universe/devel/optional/100% -> main libunity-scopes-cli 1.0.7+16.10.20160921-0ubuntu2 in yakkety s390x: universe/devel/optional/100% -> main libunity-scopes-dev 1.0.7+16.10.20160921-0ubuntu2 in yakkety amd64: universe/libdevel/optional/100% -> main libunity-scopes-dev 1.0.7+16.10.20160921-0ubuntu2 in yakkety arm64: universe/libdevel/optional/100% -> main libunity-scopes-dev 1.0.7+16.10.20160921-0ubuntu2 in yakkety armhf: universe/libdevel/optional/100% -> main libunity-scopes-dev 1.0.7+16.10.20160921-0ubuntu2 in yakkety i386: universe/libdevel/optional/100% -> main libunity-scopes-dev 1.0.7+16.10.20160921-0ubuntu2 in yakkety powerpc: universe/libdevel/optional/100% -> main libunity-scopes-dev 1.0.7+16.10.20160921-0ubuntu2 in yakkety ppc64el: universe/libdevel/optional/100% -> main libunity-scopes-dev 1.0.7+16.10.20160921-0ubuntu2 in yakkety s390x: universe/libdevel/optional/100% -> main libunity-scopes-doc 1.0.7+16.10.20160921-0ubuntu2 in yakkety amd64: universe/doc/optional/100% -> main libunity-scopes-doc 1.0.7+16.10.20160921-0ubuntu2 in yakkety arm64: universe/doc/optional/100% -> main libunity-scopes-doc 1.0.7+16.10.20160921-0ubuntu2 in yakkety armhf: universe/doc/optional/100% -> main libunity-scopes-doc 1.0.7+16.10.20160921-0ubuntu2 in yakkety i386: universe/doc/optional/100% -> main libunity-scopes-doc 1.0.7+16.10.20160921-0ubuntu2 in yakkety powerpc: universe/doc/optional/100% -> main libunity-scopes-doc 1.0.7+16.10.20160921-0ubuntu2 in yakkety ppc64el: universe/doc/optional/100% -> main libunity-scopes-doc 1.0.7+16.10.20160921-0ubuntu2 in yakkety s390x: universe/doc/optional/100% -> main libunity-scopes-qt-dev 1.0.7+16.10.20160921-0ubuntu2 in yakkety amd64: universe/libdevel/optional/100% -> main libunity-scopes-qt-dev 1.0.7+16.10.20160921-0ubuntu2 in yakkety arm64: universe/libdevel/optional/100% -> main libunity-scopes-qt-dev 1.0.7+16.10.20160921-0ubuntu2 in yakkety armhf: universe/libdevel/optional/100% -> main libunity-scopes-qt-dev 1.0.7+16.10.20160921-0ubuntu2 in yakkety i386: universe/libdevel/optional/100% -> main libunity-scopes-qt-dev 1.0.7+16.10.20160921-0ubuntu2 in yakkety powerpc: universe/libdevel/optional/100% -> main libunity-scopes-qt-dev 1.0.7+16.10.20160921-0ubuntu2 in yakkety ppc64el: universe/libdevel/optional/100% -> main libunity-scopes-qt-dev 1.0.7+16.10.20160921-0ubuntu2 in yakkety s390x: universe/libdevel/optional/100% -> main libunity-scopes-qt-doc 1.0.7+16.10.20160921-0ubuntu2 in yakkety amd64: universe/doc/optional/100% -> main libunity-scopes-qt-doc 1.0.7+16.10.20160921-0ubuntu2 in yakkety arm64: universe/doc/optional/100% -> main libunity-scopes-qt-doc 1.0.7+16.10.20160921-0ubuntu2 in yakkety armhf: universe/doc/optional/100% -> main libunity-scopes-qt-doc 1.0.7+16.10.20160921-0ubuntu2 in yakkety i386: universe/doc/optional/100% -> main libunity-scopes-qt-doc 1.0.7+16.10.20160921-0ubuntu2 in yakkety powerpc: universe/doc/optional/100% -> main libunity-scopes-qt-doc 1.0.7+16.10.20160921-0ubuntu2 in yakkety ppc64el: universe/doc/optional/100% -> main libunity-scopes-qt-doc 1.0.7+16.10.20160921-0ubuntu2 in yakkety s390x: universe/doc/optional/100% -> main libunity-scopes-qt0.2 1.0.7+16.10.20160921-0ubuntu2 in yakkety amd64: universe/libs/optional/100% -> main libunity-scopes-qt0.2 1.0.7+16.10.20160921-0ubuntu2 in yakkety arm64: universe/libs/optional/100% -> main libunity-scopes-qt0.2 1.0.7+16.10.20160921-0ubuntu2 in yakkety armhf: universe/libs/optional/100% -> main libunity-scopes-qt0.2 1.0.7+16.10.20160921-0ubuntu2 in yakkety i386: universe/libs/optional/100% -> main libunity-scopes-qt0.2 1.0.7+16.10.20160921-0ubuntu2 in yakkety powerpc: universe/libs/optional/100% -> main libunity-scopes-qt0.2 1.0.7+16.10.20160921-0ubuntu2 in yakkety ppc64el: universe/libs/optional/100% -> main libunity-scopes-qt0.2 1.0.7+16.10.20160921-0ubuntu2 in yakkety s390x: universe/libs/optional/100% -> main libunity-scopes1.0 1.0.7+16.10.20160921-0ubuntu2 in yakkety amd64: universe/libs/optional/100% -> main libunity-scopes1.0 1.0.7+16.10.20160921-0ubuntu2 in yakkety arm64: universe/libs/optional/100% -> main libunity-scopes1.0 1.0.7+16.10.20160921-0ubuntu2 in yakkety armhf: universe/libs/optional/100% -> main libunity-scopes1.0 1.0.7+16.10.20160921-0ubunt
[Touch-packages] [Bug 1576424] Re: Gimp crashes with text tool & caps lock
** Changed in: gtk+2.0 (Ubuntu) Assignee: (unassigned) => Martin Wimpress (flexiondotorg) ** Changed in: gtk+2.0 (Ubuntu) Status: Confirmed => In Progress ** Changed in: gtk+2.0 (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1576424 Title: Gimp crashes with text tool & caps lock Status in GTK+: Fix Released Status in gtk+2.0 package in Ubuntu: In Progress Bug description: [Impact] Gimp crashes with a segfault when I use caps lock while renaming a layer. It is possible Caps lock causes crashes in other events also. [Test Case] Steps to reproduce: 1. Open a new blank gimp document 2. select the text tool 3. type a couple of words of text (gimp will create a text layer above the background layer) 4. with the text tool still selected, click on the background layer (just to move away from the text layer) 5. now double click on the text layer to rename the layer (layer name gets highlighted) 6. press the caps lock key 7. click on the background layer again (without renaming or doing anything to the text layer) Now repeat steps 5 and 6. Gimp crashes. [Regression Potential] None expected. The patch used has been taken from upstream development. https://git.gnome.org/browse/gtk%2B/commit/?id=2811221d7039bd82265ce36a1b0dd9a0eeb431ad Packages for Xenial and Yakkety have been built in a PPA and regression tested. [ Other Info ] I can force this to happen every time I launch Gimp. Rebooting makes no difference. It seems to be the second time I press caps lock that forces the crash. I tried launching Gimp with caps lock on vs caps lock off, but I don't believe it made any difference. I can force a crash every time following the above sequence. I deleted my gimp preferences folder then rebooted for good measure. Gimp created a fresh preferences folder, but it hasn't solved the problem. I was originally in single window mode, but the new preferences folder put me back to multi window, but it crashes either way. I ran dmesg | tail after the crash and got the following line: gimp-2.8[2976]: segfault at 14 ip 7ff5100e0cd9 sp 7ffef11bfcb0 error 4 in libgtk-x11-2.0.so.0.2400.30[7ff51001b000+43e000] I'm using a fresh install of Xubuntu 16.04 with nvidia 361.42 driver (available from the Additional Drivers tab). In that same tab, I also have enabled Processor microcode firmware for Intel CPUs. Terminal tells me Gimp version is 2.8.16-1ubuntu1 I'm not very experienced with bug reporting and not sure what other information I need to supply. Gimp was absolutely rock solid on this machine with 15.10, so it may be a Xubuntu issue. Hope someone can take a look at this. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1576424/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1612357] Re: [FFe] unity8-desktop-session installed by default in 16.10
Override component to main unity8-desktop-session 1.0.13+16.10.20160921-0ubuntu1 in yakkety: universe/misc -> main unity8-desktop-session 1.0.13+16.10.20160921-0ubuntu1 in yakkety amd64: universe/misc/optional/100% -> main unity8-desktop-session 1.0.13+16.10.20160921-0ubuntu1 in yakkety arm64: universe/misc/optional/100% -> main unity8-desktop-session 1.0.13+16.10.20160921-0ubuntu1 in yakkety armhf: universe/misc/optional/100% -> main unity8-desktop-session 1.0.13+16.10.20160921-0ubuntu1 in yakkety i386: universe/misc/optional/100% -> main unity8-desktop-session 1.0.13+16.10.20160921-0ubuntu1 in yakkety powerpc: universe/misc/optional/100% -> main unity8-desktop-session 1.0.13+16.10.20160921-0ubuntu1 in yakkety ppc64el: universe/misc/optional/100% -> main unity8-desktop-session 1.0.13+16.10.20160921-0ubuntu1 in yakkety s390x: universe/misc/optional/100% -> main unity8-desktop-session-mir 1.0.13+16.10.20160921-0ubuntu1 in yakkety amd64: universe/misc/optional/100% -> main unity8-desktop-session-mir 1.0.13+16.10.20160921-0ubuntu1 in yakkety arm64: universe/misc/optional/100% -> main unity8-desktop-session-mir 1.0.13+16.10.20160921-0ubuntu1 in yakkety armhf: universe/misc/optional/100% -> main unity8-desktop-session-mir 1.0.13+16.10.20160921-0ubuntu1 in yakkety i386: universe/misc/optional/100% -> main unity8-desktop-session-mir 1.0.13+16.10.20160921-0ubuntu1 in yakkety powerpc: universe/misc/optional/100% -> main unity8-desktop-session-mir 1.0.13+16.10.20160921-0ubuntu1 in yakkety ppc64el: universe/misc/optional/100% -> main unity8-desktop-session-mir 1.0.13+16.10.20160921-0ubuntu1 in yakkety s390x: universe/misc/optional/100% -> main 15 publications overridden. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1612357 Title: [FFe] unity8-desktop-session installed by default in 16.10 Status in ubuntu-meta package in Ubuntu: Fix Committed Status in unity8-desktop-session package in Ubuntu: Fix Released Bug description: [Availability] * Available in universe [Rationale] * This package is required as the basis for making the Unity 8 shell available as an alternate login session in Ubuntu [Security] * No known security issues at this time. This package has been ACKed by the security team in advance. [Quality assurance] * This package is effectively a metapackage with some lightdm configuration files. Functional testing is a documented manual process with simple (you can log in or not) results. [Dependencies] * mir-graphics-drivers-desktop is in universe, but its source mir is already in main * policykit-unity8 binary and source package is in universe, but a request to file a MIR bug has been sent out * qtmir-desktop binary and source package is in universe [bug #1612358] * qtubuntu-desktop binary and source package is in universe [bug #1612346] * unity-system-compositor binary and source package is in universe [bug #1613601] * unity8 binary and source package is in universe [bug #1613638] * url-dispatcher is in universe, but its source url-dispatcher is already in main * address-book-app binary and source package is in universe, but can be demoted from 'recommends' to 'suggests' * camera-app binary and source package is in universe, but can be demoted from 'recommends' to 'suggests' * gallery-app binary and source package is in universe, but can be demoted from 'recommends' to 'suggests' * indicator-transfer binary and source package is in universe, but can be demoted from 'recommends' to 'suggests' * mediaplayer-app binary and source package is in universe, but can be demoted from 'recommends' to 'suggests' * unity-scope-click binary and source package is in universe, but a merge proposal to remove it as a dependency is pending [Standards compliance] * This package uses autotools. It has no translatable strings other than the (trade mark) "Unity8" presented as a selection at login time, which should not need translation. [Maintenance] * This package is maintained by Canonical and has been available through the archives since 2013 with some media promotion for early adopters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1612357/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1613638] Re: [MIR] unity8
Override component to main unity8 8.14+16.10.20160922-0ubuntu2 in yakkety: universe/x11 -> main indicators-client 8.14+16.10.20160922-0ubuntu2 in yakkety amd64: universe/x11/optional/100% -> main indicators-client 8.14+16.10.20160922-0ubuntu2 in yakkety armhf: universe/x11/optional/100% -> main indicators-client 8.14+16.10.20160922-0ubuntu2 in yakkety i386: universe/x11/optional/100% -> main unity-scope-tool 8.14+16.10.20160922-0ubuntu2 in yakkety amd64: universe/x11/optional/100% -> main unity-scope-tool 8.14+16.10.20160922-0ubuntu2 in yakkety armhf: universe/x11/optional/100% -> main unity-scope-tool 8.14+16.10.20160922-0ubuntu2 in yakkety i386: universe/x11/optional/100% -> main unity8 8.14+16.10.20160922-0ubuntu2 in yakkety amd64: universe/x11/optional/100% -> main unity8 8.14+16.10.20160922-0ubuntu2 in yakkety armhf: universe/x11/optional/100% -> main unity8 8.14+16.10.20160922-0ubuntu2 in yakkety i386: universe/x11/optional/100% -> main unity8-autopilot 8.14+16.10.20160922-0ubuntu2 in yakkety amd64: universe/x11/optional/100% -> main unity8-autopilot 8.14+16.10.20160922-0ubuntu2 in yakkety arm64: universe/x11/optional/100% -> main unity8-autopilot 8.14+16.10.20160922-0ubuntu2 in yakkety armhf: universe/x11/optional/100% -> main unity8-autopilot 8.14+16.10.20160922-0ubuntu2 in yakkety i386: universe/x11/optional/100% -> main unity8-autopilot 8.14+16.10.20160922-0ubuntu2 in yakkety powerpc: universe/x11/optional/100% -> main unity8-autopilot 8.14+16.10.20160922-0ubuntu2 in yakkety ppc64el: universe/x11/optional/100% -> main unity8-autopilot 8.14+16.10.20160922-0ubuntu2 in yakkety s390x: universe/x11/optional/100% -> main unity8-common 8.14+16.10.20160922-0ubuntu2 in yakkety amd64: universe/x11/optional/100% -> main unity8-common 8.14+16.10.20160922-0ubuntu2 in yakkety arm64: universe/x11/optional/100% -> main unity8-common 8.14+16.10.20160922-0ubuntu2 in yakkety armhf: universe/x11/optional/100% -> main unity8-common 8.14+16.10.20160922-0ubuntu2 in yakkety i386: universe/x11/optional/100% -> main unity8-common 8.14+16.10.20160922-0ubuntu2 in yakkety powerpc: universe/x11/optional/100% -> main unity8-common 8.14+16.10.20160922-0ubuntu2 in yakkety ppc64el: universe/x11/optional/100% -> main unity8-common 8.14+16.10.20160922-0ubuntu2 in yakkety s390x: universe/x11/optional/100% -> main unity8-doc 8.14+16.10.20160922-0ubuntu2 in yakkety amd64: universe/doc/optional/100% -> main unity8-doc 8.14+16.10.20160922-0ubuntu2 in yakkety arm64: universe/doc/optional/100% -> main unity8-doc 8.14+16.10.20160922-0ubuntu2 in yakkety armhf: universe/doc/optional/100% -> main unity8-doc 8.14+16.10.20160922-0ubuntu2 in yakkety i386: universe/doc/optional/100% -> main unity8-doc 8.14+16.10.20160922-0ubuntu2 in yakkety powerpc: universe/doc/optional/100% -> main unity8-doc 8.14+16.10.20160922-0ubuntu2 in yakkety ppc64el: universe/doc/optional/100% -> main unity8-doc 8.14+16.10.20160922-0ubuntu2 in yakkety s390x: universe/doc/optional/100% -> main unity8-fake-env 8.14+16.10.20160922-0ubuntu2 in yakkety amd64: universe/x11/optional/100% -> main unity8-fake-env 8.14+16.10.20160922-0ubuntu2 in yakkety armhf: universe/x11/optional/100% -> main unity8-fake-env 8.14+16.10.20160922-0ubuntu2 in yakkety i386: universe/x11/optional/100% -> main unity8-greeter 8.14+16.10.20160922-0ubuntu2 in yakkety amd64: universe/x11/optional/100% -> main unity8-greeter 8.14+16.10.20160922-0ubuntu2 in yakkety armhf: universe/x11/optional/100% -> main unity8-greeter 8.14+16.10.20160922-0ubuntu2 in yakkety i386: universe/x11/optional/100% -> main unity8-private 8.14+16.10.20160922-0ubuntu2 in yakkety amd64: universe/x11/optional/100% -> main unity8-private 8.14+16.10.20160922-0ubuntu2 in yakkety armhf: universe/x11/optional/100% -> main unity8-private 8.14+16.10.20160922-0ubuntu2 in yakkety i386: universe/x11/optional/100% -> main 40 publications overridden. ** Changed in: unity8 (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 unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1613638 Title: [MIR] unity8 Status in unity8 package in Ubuntu: Fix Released Bug description: [Availability] * Available in universe [Rationale] * This package is planned for inclusion in main for 16.10 [Security] * No known security issues at this time. It has been reviewed by security in the past for use on the phone. [Quality assurance] * This package has both unit tests and autopkgtests [Dependencies] The whole list of dependencies being MIR'ed is being tracked by https://trello.com/b/mab4G8UQ/unity-8-in-16-10 * indicator-network [bug #1612619] * libusermetrics [bug #1612259] * pay-service [bug #1614202] * qmenumodel [bug #1612363] * qtmir [bug #1612358] * qtsystems-opensource-src [bug #1552860] * thumbnailer [bug #1613561] * ubuntu-settings-components [
[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi
'sudo iw dev wlan0 scan' (or in my case wlp13s0 instead of wlan0) doesn't work for me. Here's the output: command failed: Device or resource busy (-16) -- 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/1589401 Title: cannot view wifi networks after re-enabling wifi Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Incomplete Bug description: after re enabling wifi, up-down arrows just like wired network. cannot see any wifi ssid. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1576424] Re: Gimp crashes with text tool & caps lock
Attached is a debdiff for gtk+2.0 (Yakkety) that adds a patch to explicitly disconnect keymap signals. ** Patch added: "gtk2-yakkety-explicitly-disconnect-keymap-signals.diff" https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1576424/+attachment/4754403/+files/gtk2-yakkety-explicitly-disconnect-keymap-signals.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1576424 Title: Gimp crashes with text tool & caps lock Status in GTK+: Fix Released Status in gtk+2.0 package in Ubuntu: In Progress Bug description: [Impact] Gimp crashes with a segfault when I use caps lock while renaming a layer. It is possible Caps lock causes crashes in other events also. [Test Case] Steps to reproduce: 1. Open a new blank gimp document 2. select the text tool 3. type a couple of words of text (gimp will create a text layer above the background layer) 4. with the text tool still selected, click on the background layer (just to move away from the text layer) 5. now double click on the text layer to rename the layer (layer name gets highlighted) 6. press the caps lock key 7. click on the background layer again (without renaming or doing anything to the text layer) Now repeat steps 5 and 6. Gimp crashes. [Regression Potential] None expected. The patch used has been taken from upstream development. https://git.gnome.org/browse/gtk%2B/commit/?id=2811221d7039bd82265ce36a1b0dd9a0eeb431ad Packages for Xenial and Yakkety have been built in a PPA and regression tested. [ Other Info ] I can force this to happen every time I launch Gimp. Rebooting makes no difference. It seems to be the second time I press caps lock that forces the crash. I tried launching Gimp with caps lock on vs caps lock off, but I don't believe it made any difference. I can force a crash every time following the above sequence. I deleted my gimp preferences folder then rebooted for good measure. Gimp created a fresh preferences folder, but it hasn't solved the problem. I was originally in single window mode, but the new preferences folder put me back to multi window, but it crashes either way. I ran dmesg | tail after the crash and got the following line: gimp-2.8[2976]: segfault at 14 ip 7ff5100e0cd9 sp 7ffef11bfcb0 error 4 in libgtk-x11-2.0.so.0.2400.30[7ff51001b000+43e000] I'm using a fresh install of Xubuntu 16.04 with nvidia 361.42 driver (available from the Additional Drivers tab). In that same tab, I also have enabled Processor microcode firmware for Intel CPUs. Terminal tells me Gimp version is 2.8.16-1ubuntu1 I'm not very experienced with bug reporting and not sure what other information I need to supply. Gimp was absolutely rock solid on this machine with 15.10, so it may be a Xubuntu issue. Hope someone can take a look at this. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1576424/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1576424] Re: Gimp crashes with text tool & caps lock
Attached is a debdiff for gtk+2.0 (Xenial) that adds a patch to explicitly disconnect keymap signals. ** Patch added: "gtk2-xenial-explicitly-disconnect-keymap-signals.diff" https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1576424/+attachment/4754404/+files/gtk2-xenial-explicitly-disconnect-keymap-signals.diff ** Description changed: + [Impact] + Gimp crashes with a segfault when I use caps lock while renaming a - layer. Steps to reproduce: + layer. It is possible Caps lock causes crashes in other events also. + + [Test Case] + + Steps to reproduce: 1. Open a new blank gimp document 2. select the text tool 3. type a couple of words of text (gimp will create a text layer above the background layer) 4. with the text tool still selected, click on the background layer (just to move away from the text layer) 5. now double click on the text layer to rename the layer (layer name gets highlighted) 6. press the caps lock key 7. click on the background layer again (without renaming or doing anything to the text layer) Now repeat steps 5 and 6. Gimp crashes. + + [Regression Potential] + + None expected. The patch used has been taken from upstream development. + + https://git.gnome.org/browse/gtk%2B/commit/?id=2811221d7039bd82265ce36a1b0dd9a0eeb431ad + + Packages for Xenial and Yakkety have been built in a PPA and regression + tested. + + [ Other Info ] I can force this to happen every time I launch Gimp. Rebooting makes no difference. It seems to be the second time I press caps lock that forces the crash. I tried launching Gimp with caps lock on vs caps lock off, but I don't believe it made any difference. I can force a crash every time following the above sequence. I deleted my gimp preferences folder then rebooted for good measure. Gimp created a fresh preferences folder, but it hasn't solved the problem. I was originally in single window mode, but the new preferences folder put me back to multi window, but it crashes either way. I ran dmesg | tail after the crash and got the following line: gimp-2.8[2976]: segfault at 14 ip 7ff5100e0cd9 sp 7ffef11bfcb0 error 4 in libgtk-x11-2.0.so.0.2400.30[7ff51001b000+43e000] I'm using a fresh install of Xubuntu 16.04 with nvidia 361.42 driver (available from the Additional Drivers tab). In that same tab, I also have enabled Processor microcode firmware for Intel CPUs. Terminal tells me Gimp version is 2.8.16-1ubuntu1 I'm not very experienced with bug reporting and not sure what other information I need to supply. Gimp was absolutely rock solid on this machine with 15.10, so it may be a Xubuntu issue. Hope someone can take a look at this. Thanks. ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1576424 Title: Gimp crashes with text tool & caps lock Status in GTK+: Fix Released Status in gtk+2.0 package in Ubuntu: In Progress Bug description: [Impact] Gimp crashes with a segfault when I use caps lock while renaming a layer. It is possible Caps lock causes crashes in other events also. [Test Case] Steps to reproduce: 1. Open a new blank gimp document 2. select the text tool 3. type a couple of words of text (gimp will create a text layer above the background layer) 4. with the text tool still selected, click on the background layer (just to move away from the text layer) 5. now double click on the text layer to rename the layer (layer name gets highlighted) 6. press the caps lock key 7. click on the background layer again (without renaming or doing anything to the text layer) Now repeat steps 5 and 6. Gimp crashes. [Regression Potential] None expected. The patch used has been taken from upstream development. https://git.gnome.org/browse/gtk%2B/commit/?id=2811221d7039bd82265ce36a1b0dd9a0eeb431ad Packages for Xenial and Yakkety have been built in a PPA and regression tested. [ Other Info ] I can force this to happen every time I launch Gimp. Rebooting makes no difference. It seems to be the second time I press caps lock that forces the crash. I tried launching Gimp with caps lock on vs caps lock off, but I don't believe it made any difference. I can force a crash every time following the above sequence. I deleted my gimp preferences folder then rebooted for good measure. Gimp created a fresh preferences folder, but it hasn't solved the problem. I was originally in single window mode, but the new preferences folder put me back to multi window, but it crashes either way. I ran dmesg | tail after the crash and got the following line: gimp-2.8[2976]: segfault at 14 ip 7ff5100e0cd9 sp 7ffef11bfcb0 error 4 in libgtk-x11-2.0.so.0.2400.30[7ff51001b000+43e000] I'm using a fresh install of Xubuntu 16.04 with nvidia 361.42 driver
