[Touch-packages] [Bug 1538934] [NEW] qml test fails with vanilla xenial installation
Public bug reported: On a fresh xenial install, the qml test fails. I'm running it from the qml test dir like this: $ ../../../tools/run-xvfb.sh ./qml_test -import `pwd`/../../plugins Output is in the attached trace file. ** Affects: thumbnailer (Ubuntu) Importance: Undecided Assignee: James Henstridge (jamesh) Status: New ** Attachment added: "Test output" https://bugs.launchpad.net/bugs/1538934/+attachment/4558147/+files/trace ** Changed in: thumbnailer (Ubuntu) Assignee: (unassigned) => James Henstridge (jamesh) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to thumbnailer in Ubuntu. https://bugs.launchpad.net/bugs/1538934 Title: qml test fails with vanilla xenial installation Status in thumbnailer package in Ubuntu: New Bug description: On a fresh xenial install, the qml test fails. I'm running it from the qml test dir like this: $ ../../../tools/run-xvfb.sh ./qml_test -import `pwd`/../../plugins Output is in the attached trace file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thumbnailer/+bug/1538934/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1538934] Re: qml test fails with vanilla xenial installation
After installing the thumbnailer from the archive, the messages about the missing .service files disappear. But there are still two tests that fail (see second attached file). ** Attachment added: "trace2" https://bugs.launchpad.net/ubuntu/+source/thumbnailer/+bug/1538934/+attachment/4558149/+files/trace2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to thumbnailer in Ubuntu. https://bugs.launchpad.net/bugs/1538934 Title: qml test fails with vanilla xenial installation Status in thumbnailer package in Ubuntu: New Bug description: On a fresh xenial install, the qml test fails. I'm running it from the qml test dir like this: $ ../../../tools/run-xvfb.sh ./qml_test -import `pwd`/../../plugins Output is in the attached trace file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thumbnailer/+bug/1538934/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413818] Re: Notification sounds aren't being played back on E4.5 (ubuntu-push restricts directories and block custom sounds)
Same here, Aquaris message ringtone is not played with Telegram push notifications tested with: Vegeta OTA9 Krillin rc 244 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-session in Ubuntu. https://bugs.launchpad.net/bugs/1413818 Title: Notification sounds aren't being played back on E4.5 (ubuntu-push restricts directories and block custom sounds) Status in Canonical System Image: Fix Released Status in The Savilerow project: Confirmed Status in ubuntu-push package in Ubuntu: Fix Committed Status in ubuntu-touch-session package in Ubuntu: Confirmed Bug description: This affects mostly the push notifications based alerts, SMS et.al. work fine. With export PULSE_PROP='media.role=alert' This has no audible output: paplay /usr/share/sounds/ubuntu/notifications/Slick.ogg This does: paplay /usr/share/sounds/ubuntu/ringtones/Soul.ogg $ system-image-cli -i current build number: 14 device name: mako channel: ubuntu-touch/stable alias: ubuntu-touch/ubuntu-rtm/14.09 last update: 2015-01-16 13:12:29 version version: 14 version ubuntu: 20150116 version device: 20141119 version custom: mako-1.1 The hunch is some buffering going on on the android side for short sound bytes. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1413818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413818] Re: Notification sounds aren't being played back on E4.5 (ubuntu-push restricts directories and block custom sounds)
Again... no luck with OTA-9, please reopen... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-session in Ubuntu. https://bugs.launchpad.net/bugs/1413818 Title: Notification sounds aren't being played back on E4.5 (ubuntu-push restricts directories and block custom sounds) Status in Canonical System Image: Fix Released Status in The Savilerow project: Confirmed Status in ubuntu-push package in Ubuntu: Fix Committed Status in ubuntu-touch-session package in Ubuntu: Confirmed Bug description: This affects mostly the push notifications based alerts, SMS et.al. work fine. With export PULSE_PROP='media.role=alert' This has no audible output: paplay /usr/share/sounds/ubuntu/notifications/Slick.ogg This does: paplay /usr/share/sounds/ubuntu/ringtones/Soul.ogg $ system-image-cli -i current build number: 14 device name: mako channel: ubuntu-touch/stable alias: ubuntu-touch/ubuntu-rtm/14.09 last update: 2015-01-16 13:12:29 version version: 14 version ubuntu: 20150116 version device: 20141119 version custom: mako-1.1 The hunch is some buffering going on on the android side for short sound bytes. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1413818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1504084] Re: On unity8 desktop, websites serve mobile version
The user agent we send now depends on the screen size (not the window size). On nexus 7, getting mobile sites is expected. If you connect an external monitor, you should be getting desktop sites (but there is a known issue that prevents this, bug #1534682). -- 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/1504084 Title: On unity8 desktop, websites serve mobile version Status in Canonical System Image: Fix Released Status in webbrowser-app package in Ubuntu: Fix Released Bug description: On unity8 on desktop, the webbrowser-app shows the mobile version of websites. This can be reproduced with e.g. http://github.com To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1504084/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1537139] Re: Selecting new dept should cancel current query
** Changed in: unity-scopes-shell (Ubuntu) Status: New => Confirmed -- 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/1537139 Title: Selecting new dept should cancel current query Status in The Savilerow project: New Status in unity-scopes-shell package in Ubuntu: Confirmed Bug description: Selecting a new department should cancel any query currently running. For example, open News scope. Select the Sports departments. While it is running, select the Finance department. Unexpected result: Sports results display, but Finance department appears selected. To manage notifications about this bug go to: https://bugs.launchpad.net/savilerow/+bug/1537139/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1535349] Re: `df /dev/sda1` no longer reports information for /dev/sda1
It looks like the addition of "resolve_device" to initramfs- tool/scripts/functions and to local fixes the uuid mount that I was seeing on my trusty machine. I will have to do additional work to get initramfs-tools resolved, but it looks like the patch is good. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1535349 Title: `df /dev/sda1` no longer reports information for /dev/sda1 Status in coreutils package in Ubuntu: Invalid Status in coreutils source package in Trusty: Confirmed Bug description: [Impact] * df fails to process devices that are specified on the command line. [Test Case] * Actual $ df -h /dev/sda1 Filesystem Size Used Avail Use% Mounted on udev1.8G 8.0K 1.8G 1% /dev * Expected $ df -h /dev/sda1 Filesystem Size Used Avail Use% Mounted on /dev/sda1 9.9G 978M 8.5G 11% / [Regression Potential] * This patch is a partial backport of functions as they exist in vivid to help minimize the regression potential. * That being said I had to do some backporting so as to avoid ui changes. * This once again significantly changes the mount search and matching logic within df, but it is localized to df. [Other Info] * Anything else you think is useful to include * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board * and address these questions in advance Original Description--- It appears that the latest version of coreutils uploaded to trusty-updates has a regression in it. We have scripting that checks how much space we have left on a partition using `df /dev/sda1`. Using coreutils 8.21-1ubuntu5.1, we can do the following: $ df -h /dev/sda1 Filesystem Size Used Avail Use% Mounted on /dev/sda1 9.9G 978M 8.5G 11% / This is a valid way of using the tool per the manpage: "If an argument is the absolute file name of a disk device node containing a mounted file system, df shows the space available on that file system rather than on the file system containing the device node" It appears that either 8.21-1ubuntu5.2 or 8.21-1ubuntu5.3 broke this, however. We now get output for the udev filesystem that is mounted at /dev, instead of the device we pass in. $ df -h /dev/sda1 Filesystem Size Used Avail Use% Mounted on udev1.8G 8.0K 1.8G 1% /dev This is both a behaviour change, and contravenes the manpage, so it would be good to get this fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1535349/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1511735] Re: libnl: fail to bind() netlink sockets
** Changed in: libnl3 (Ubuntu) Importance: Undecided => Medium ** Changed in: libnl3 (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: libnl3 (Ubuntu Trusty) Status: New => Triaged ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1511735 Title: libnl: fail to bind() netlink sockets Status in libnl3 package in Ubuntu: Fix Released Status in libnl3 source package in Trusty: Triaged Status in libnl3 package in Debian: New Bug description: [Impact] * Applications in Trusty using libnl-3-200 which frequently open and close netlink sockets can easily fail when attempting to bind the local socket. The problem happens when libnl choose a port id already used by another application and subsequently libnl fails instead of trying another port id. The original bug was discovered when attempting to start a virtual machine under libvirt, which is a user of this library. * Backporting fixes from upstream release fixes a real bug in the current version of the library in Trusty. The alternative is for all applications to manually manage their local port allocation, or as upstream has accepted allowing libnl to attempt to try for other local ports. * All patches applied are already accepted upstream and newer Ubuntu releases are not affected. [Test Case] * On a Trusty 14.04 system 1. sudo apt-get install libnl-3-200 libnl-3-dev libnl-3-dev \ libnl-genl-3-dev libnl-route-3-200 \ make gcc build-essential libnl1 2. download and unpack attachment: lp_1511735_test.tar 3. Run testcases: % if ./example.sh; then echo "libnl OK"; else echo "libnl FAILED"; fi gcc -o example -I/usr/include/libnl3 example.c -lnl-3 -lnl-genl-3 set manually the local port to 6975 (pid: 6974) local port has been set by the libnl to 6975 (pid: 6975) ERROR: genl_connect(): Object exists (local port: 6975, pid: 6975) libnl FAILED % python libnl3-test-rh1249158.py a b c d ulimit(NOFILE) = (2048, 4096) Test: PID=6978 TEST (a)... Traceback (most recent call last): File "libnl3-test-rh1249158.py", line 226, in locals()["TEST_" + arg]() File "libnl3-test-rh1249158.py", line 140, in TEST_a sk = nl_get_socket() File "libnl3-test-rh1249158.py", line 115, in nl_get_socket raise IOError(-err, _nl_geterror()) OSError: [Errno 6] b'Unspecific failure' 4. After applying the updated packages: % if ./example.sh; then echo "libnl OK"; else echo "libnl FAILED"; fi gcc -o example -I/usr/include/libnl3 example.c -lnl-3 -lnl-genl-3 set manually the local port to 11295 (pid: 11294) local port has been set by the libnl to 2894081055 (pid: 11295) libnl OK % python libnl3-test-rh1249158.py a b c d ulimit(NOFILE) = (2048, 4096) Test: PID=11296 TEST (a)... ...done TEST (b)... ...done TEST (c)... ...done TEST (d)... ...done [Regression Potential] * There are quite a few high profile packages that depend on this package, notably libvirt and network-manager. The complete list is here: # on Trusty % apt-rdepends -r libnl-3-200 | head -n 33 libnl-3-200 Reverse Depends: batctl (>= 2013.4.0-2) Reverse Depends: bmon (>= 1:3.1-1) Reverse Depends: crda (>= 1.1.2-1ubuntu2) Reverse Depends: hostapd (>= 1:2.1-0ubuntu1) Reverse Depends: ipvsadm (>= 1:1.26-2ubuntu1) Reverse Depends: iw (>= 3.4-1) Reverse Depends: keepalived (>= 1:1.2.7-1ubuntu1) Reverse Depends: kismet (>= 2013.03.R1b-3) Reverse Depends: knemo (>= 0.7.6-2) Reverse Depends: libfsobasics3 (>= 0.12.0-4) Reverse Depends: libnetcf1 (>= 1:0.2.3-4ubuntu1) Reverse Depends: libnl-3-200-dbg (= 3.2.21-1) Reverse Depends: libnl-3-dev (= 3.2.21-1) Reverse Depends: libnl-cli-3-200 (= 3.2.21-1) Reverse Depends: libnl-genl-3-200 (= 3.2.21-1) Reverse Depends: libnl-nf-3-200 (= 3.2.21-1) Reverse Depends: libnl-route-3-200 (= 3.2.21-1) Reverse Depends: libnl-utils (>= 3.2.21-1) Reverse Depends: libnss-gw-name (>= 0.3-2) Reverse Depends: libvirt-bin (>= 1.2.2-0ubuntu13) Reverse Depends: libvirt0 (>= 1.2.2-0ubuntu13) Reverse Depends: lowpan-test-tools (>= 0.3-1) Reverse Depends: lowpan-tools (>= 0.3-1) Reverse Depends: neard (>= 0.11-1) Reverse Depends: neard-tools (>= 0.11-1) Reverse Depends: network-manager (>= 0.9.8.8-0ubuntu7) Reverse Depends: ntrack-module-libnl-0 (>= 016-1.2ubuntu2) Reverse Depends: plainbox-provider-resource-g
[Touch-packages] [Bug 1477855] Re: Add alternative shutter methods
I also agree with using hardware volume control buttons - one for autofocus, another for shooting. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1477855 Title: Add alternative shutter methods Status in camera-app: Confirmed Status in camera-app package in Ubuntu: Confirmed Bug description: Feature request: Problem: On a large phone like the MX4 it is very difficult to use the camera app with one hand because when you first set the focus point, then it is usually impossible to reach the shutter icon without moving the phone. Possible solutions: - When setting the focus point, directly take an image when it is focused. This could be an option or gesture based (e.g. double tap on screen). - use one of the hardware buttons as shutter button. E.g. volume control. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1477855/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1496226] Re: Top-left menu disappears after viewing a photo
Seems to have been fixed in some update since. ** Changed in: gallery-app (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1496226 Title: Top-left menu disappears after viewing a photo Status in gallery-app package in Ubuntu: Invalid Bug description: Take a few photos with the camera. Start gallery app. Tap on one of the photos in the events view. Tap on the photo and then on the "back" chevron. Now the events view shows again, and the menu at the top-left has disappeared. (It's now a black box and tapping on that doesn't activate the menu.) It appears that there is no way to recover from this other than to kill and re-start the app. I'm seeing this on Mako with image 240. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1496226/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1536082] Re: No update since OTA-8
camera-app finally got updated with the OTA-9 update -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1536082 Title: No update since OTA-8 Status in camera-app package in Ubuntu: New Bug description: I believe my phone's (bq Aquaris E5 HD) camera app stopped getting updates since OTA-8. It didn't detect any update for a long time. Hence I don't get to see the recent changes (e.g. HDR disabled in video mode, selecting photo resolution etc.) Other apps are getting updated as usual. I uninstalled and reinstalled camera-app (using apt- get), but still no updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1536082/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1538884] [NEW] apport dialog should open other browser if default browser fails
Public bug reported: If opening the default browser (e.g. firefox) fails (e.g. because `~/.mozilla` is a broken symlink) `apport` should open another browser in order to avoid unnecessary steps to be retaken by the user. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: apport 2.19.1-0ubuntu5 Uname: Linux 4.3.3-040303-generic x86_64 ApportLog: ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jan 28 05:05:57 2016 InstallationDate: Installed on 2015-12-12 (46 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1538884 Title: apport dialog should open other browser if default browser fails Status in apport package in Ubuntu: New Bug description: If opening the default browser (e.g. firefox) fails (e.g. because `~/.mozilla` is a broken symlink) `apport` should open another browser in order to avoid unnecessary steps to be retaken by the user. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: apport 2.19.1-0ubuntu5 Uname: Linux 4.3.3-040303-generic x86_64 ApportLog: ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jan 28 05:05:57 2016 InstallationDate: Installed on 2015-12-12 (46 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1538884/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1463059] Re: [browser] Secure connection icon should indicate level of verification
Status changed to 'Confirmed' because the bug affects multiple users. ** 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/1463059 Title: [browser] Secure connection icon should indicate level of verification Status in Ubuntu UX: Triaged Status in webbrowser-app package in Ubuntu: Confirmed Bug description: It should show different icons for self-signed/failed to verify, verified standard and verified EV certificates. (copied from https://lists.launchpad.net/ubuntu-phone/msg13087.html ) E.g. https://bugs.launchpad.net could be a green lock icon instead of the grey one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1463059/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1537136] Comment bridged from LTC Bugzilla
--- Comment From chngu...@us.ibm.com 2016-01-27 23:03 EDT--- (In reply to comment #34) > Our system is hitting another bug. We will verify this soon after we get > some news on other bug. Thanks -- 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/1537136 Title: ISST-LTE: no network after install due to interface order change Status in debian-installer package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in debian-installer source package in Trusty: Fix Committed Status in systemd source package in Trusty: Fix Committed Bug description: == Comment: #0 - Chanh H. Nguyen - 2015-12-10 20:32:29 == We use the network to install Ubuntu 14.04.4 version. The installation is successful but then there is no network after system reboot in post install. Checking the network and I saw the order of interface are changed. This is causing no network at all. There is 2 cards (Houston 4ports & Mellanox 2 ports). We are using the Mellanox interface for this installation. At the installation menu, we select this interface eth2 (mellanox card) ??? [!!] Configure the network ? ? ? Your system has multiple network interfaces. Choose the one to use as ? ? the primary network interface during the installation. If possible, ? ? the first connected network interface found has been selected. ? ? ? ? Primary network interface: ? ? ? ? eth0: Emulex Corporation OneConnect NIC (Lancer) ? ? eth1: Emulex Corporation OneConnect NIC (Lancer) ? ? eth2: Mellanox Technologies MT27500 Family [ConnectX-3] ? ? eth3: Mellanox Technologies MT27500 Family [ConnectX-3] ? ? eth4: Emulex Corporation OneConnect NIC (Lancer) ? ? eth5: Emulex Corporation OneConnect NIC (Lancer) ? ? ? ?? ? ? ??? After install, root@monklp3:~# ifconfig eth2 Link encap:Ethernet HWaddr 00:00:c9:d1:be:28 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:32 errors:0 dropped:0 overruns:0 frame:0 TX packets:32 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2368 (2.3 KB) TX bytes:2368 (2.3 KB) root@monklp3:~# ifconfig -a|grep eth eth0 Link encap:Ethernet HWaddr 00:00:c9:d1:be:26 eth1 Link encap:Ethernet HWaddr 00:00:c9:d1:be:27 eth2 Link encap:Ethernet HWaddr 00:00:c9:d1:be:28 eth3 Link encap:Ethernet HWaddr 00:02:c9:b7:60:b0 eth4 Link encap:Ethernet HWaddr 00:02:c9:b7:60:b1 eth5 Link encap:Ethernet HWaddr 00:00:c9:d1:be:29 root@monklp3:~# cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth2 iface eth2 inet dhcp root@monklp3:~# dmesg |grep "eth" [0.950725] ibmveth: IBM Power Virtual Ethernet Driver 1.05 [0.950735] ehea: IBM eHEA ethernet device driver (Release EHEA_0107) [9.810472] mlx4_en: eth3: Link Up [ 40.554271] be2net 0001:80:00.2 eth2: Link is Down [ 40.560738] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready root@monklp3:~# The mellanox inteface is now on eth3 but on the /etc/network/interface file, it is set on eth2. SRU TEST CASE: -- * Do a netboot install in a VM or machine with more than one NIC. If you use a VM, take care to not use the default MAC addresses as they are blacklisted from the persistent net generator. E. g. use "-net nic,model=virtio,macaddr=A4:4E:31:12:34:XX" with QEMU. * In the d-i environment, switch to a console with Alt+F2 after the base system
[Touch-packages] [Bug 1537798] Re: NestedServer.client_sees_set_scaling_factor intermittent failure
** Changed in: mir Status: Confirmed => In Progress ** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- 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/1537798 Title: NestedServer.client_sees_set_scaling_factor intermittent failure Status in Mir: In Progress Status in mir package in Ubuntu: New Bug description: https://mir-jenkins.ubuntu.com/job/mir-xenial-amd64-ci/135/consoleFull And ive seen it fail on other CI runs: 11: [ OK ] NestedServer.shell_sees_set_scaling_factor (4539 ms) 12:38:44 11: [ RUN ] NestedServer.client_sees_set_scaling_factor 12:38:44 11: [1453725524.246945] mirserver: Starting 12:38:44 11: [1453725524.247985] mirserver: Selected driver: dummy (version 0.19.0) 12:38:44 11: [1453725524.261749] mirserver: Using software cursor 12:38:44 11: [1453725524.264347] mirserver: Selected input driver: mir:stub-input (version: 0.19.0) 12:38:44 11: [1453725524.264837] mirserver: Mir version 0.19.0 12:38:44 11: [1453725524.277504] mirserver: Starting 12:38:44 11: [1453725524.283012] mirserver: Using nested cursor 12:38:44 11: [1453725524.576879] mirserver: Initial display configuration: 12:38:44 11: [1453725524.577826] mirserver: 1.1: VGA 0.0" 0x0mm 12:38:44 11: [1453725524.577940] mirserver: Current mode 640x480 60.00Hz 12:38:44 11: [1453725524.578037] mirserver: Preferred mode 640x480 60.00Hz 12:38:44 11: [1453725524.578114] mirserver: Logical position +0+0 12:38:44 11: [1453725524.578649] mirserver: 1.2: VGA 0.0" 0x0mm 12:38:44 11: [1453725524.578751] mirserver: Current mode 1920x1080 60.00Hz 12:38:44 11: [1453725524.578854] mirserver: Preferred mode 1920x1080 60.00Hz 12:38:44 11: [1453725524.578925] mirserver: Logical position +640+0 12:38:44 11: [1453725524.583100] mirserver: Mir version 0.19.0 12:38:44 11: [1453725524.590109] mirserver: New display configuration: 12:38:44 11: [1453725524.593785] mirserver: 1.1: VGA 0.0" 0x0mm 12:38:44 11: [1453725524.593895] mirserver: Current mode 640x480 60.00Hz 12:38:44 11: [1453725524.593989] mirserver: Preferred mode 640x480 60.00Hz 12:38:44 11: [1453725524.594066] mirserver: Logical position +0+0 12:38:44 11: [1453725524.594639] mirserver: 1.2: VGA 0.0" 0x0mm 12:38:44 11: [1453725524.594752] mirserver: Current mode 1920x1080 60.00Hz 12:38:44 11: [1453725524.594854] mirserver: Preferred mode 1920x1080 60.00Hz 12:38:44 11: [1453725524.594938] mirserver: Logical position +640+0 12:38:44 11: /tmp/buildd/mir-0.19.0bzr3267pkg0xenial135/tests/acceptance-tests/test_nested_mir.cpp:546: Failure 12:38:44 11: Value of: mir_surface_output_event_get_form_factor(surface_event) 12:38:44 11: Expected: is equal to 4 12:38:44 11: Actual: 3 (of type MirFormFactor) 12:38:44 11: /tmp/buildd/mir-0.19.0bzr3267pkg0xenial135/tests/acceptance-tests/test_nested_mir.cpp:547: Failure 12:38:44 11: Value of: mir_surface_output_event_get_scale(surface_event) 12:38:44 11: Expected: is equal to 2.3 12:38:44 11: Actual: 1 (of type float) 12:38:44 11: [1453725524.846521] mirserver: Stopping 12:38:44 11: [1453725524.870936] mirserver: Stopping 12:38:44 11: [ FAILED ] NestedServer.client_sees_set_scaling_factor (656 ms) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1537798/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1488056] Re: Rejected send message, 10 matched rules; type="method_return", sender=":1.84"
Also affecting Kubuntu 16.04 (kubuntu 15.10+dist-upgrade) dbus[] [system] Rejected send message, 10 matched rules; type="method_return", sender=":1.47" (uid=0 pid=2075 comm="/usr/sbin/dnsmasq --no-resolv --keep-in-foreground") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.2" (uid=0 pid=846 comm="/usr/sbin/NetworkManager --no-daemon ") -- 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/1488056 Title: Rejected send message, 10 matched rules; type="method_return", sender=":1.84" Status in bind9 package in Ubuntu: Expired Status in network-manager package in Ubuntu: Confirmed Bug description: Seeing lots of those log entries. Here an example Aug 24 20:14:36 M1 NetworkManager[748]: [1440404076.494991] [dns-manager/nm-dns-dnsmasq.c:398] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name Aug 24 20:14:36 M1 dbus[792]: [system] Rejected send message, 10 matched rules; type="method_return", sender=":1.84" (uid=0 pid=3300 comm="/usr/sbin/dnsmasq --no-resolv --keep-in-foreground") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.7" (uid=0 pid=748 comm="/usr/sbin/NetworkManager --no-daemon ") Attached info might help locating the issue. Thanks for any clues. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dnsmasq 2.72-3ubuntu0.1 ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 Date: Mon Aug 24 23:08:37 2015 InstallationDate: Installed on 2014-10-31 (297 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) PackageArchitecture: all SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1488056/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1434517] Re: 480p and 1080p video appear to use the same bitrate
Hi Simon, I have just checked in qtubuntu-camera and it is indeed done this way. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1434517 Title: 480p and 1080p video appear to use the same bitrate Status in Canonical System Image: In Progress Status in camera-app package in Ubuntu: In Progress Status in libhybris package in Ubuntu: Confirmed Bug description: I just recorded two 10 second videos of the the same object using my Nexus 4, one using the 1080p setting and the other 480p. Both videos came out at roughly 8MB, each with approximately a 6.3 Mb/s video bit rate and 96 kb/s audio bit rate. This seems a bit weird to me: the only reason I can think of to offer multiple resolutions is to let the user pick the quality / storage space trade off they want. If the lower resolution videos take up just as much space as the high resolution ones, then this doesn't make sense. I am running build 143 on a Nexus 4, which looks to have camera-app 3.0.0.516 installed: current build number: 143 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-03-20 07:05:06 version version: 143 version ubuntu: 20150320 version device: 20150210 version custom: 20150320 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1434517/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1538865] [NEW] display arrangement fails to load after login
Public bug reported: Only a dialog with could not assign CRTCs to outputs: Trying modes for CRTC 63 CRTC 63: trying mode 1366x768@60Hz with output at 1366x768@60Hz (pass 0) none of the selected modes were compatible with the possible modes: Trying modes for CRTC 63 CRTC 63: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 0) CRTC 63: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 1) Trying modes for CRTC 64 CRTC 64: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 0) CRTC 64: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 1) Trying modes for CRTC 65 CRTC 65: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 0) CRTC 65: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 1) Trying modes for CRTC 66 CRTC 66: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 0) CRTC 66: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 1) CRTC 63: trying mode 1360x768@60Hz with output at 1366x768@60Hz (pass 0) CRTC 63: trying mode 1360x768@60Hz with output at 1366x768@60Hz (pass 0) CRTC 63: trying mode 1280x720@60Hz with output at 1366x768@60Hz (pass 0) CRTC 63: trying mode 1024x768@60Hz with output at 1366x768@60Hz (pass 0) CRTC 63: trying mode 1024x576@60Hz with output at 1366x768@60Hz (pass 0) CRTC 63: trying mode 960x540@60Hz with output at 1366x768@60Hz (pass 0) CRTC 63: trying mode 800x600@60Hz with output at 1366x768@60Hz (pass 0) CRTC 63: trying mode 800x600@56Hz with output at 1366x768@60Hz (pass 0) CRTC 63: trying mode 864x486@60Hz with output at 1366x768@60Hz (pass 0) CRTC 63: trying mode 640x480@60Hz with output at 1366x768@60Hz (pass 0) CRTC 63: trying mode 720x405@60Hz with output at 1366x768@60Hz (pass 0) CRTC 63: trying mode 680x384@60Hz with output at 1366x768@60Hz (pass 0) CRTC 63: trying mode 640x360@60Hz with output at 1366x768@60Hz (pass 0) CRTC 63: trying mode 1366x768@60Hz with output at 1366x768@60Hz (pass 1) none of the selected modes were compatible with the possible modes: Trying modes for CRTC 63 CRTC 63: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 0) CRTC 63: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 1) Trying modes for CRTC 64 CRTC 64: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 0) CRTC 64: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 1) Trying modes for CRTC 65 CRTC 65: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 0) CRTC 65: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 1) Trying modes for CRTC 66 CRTC 66: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 0) CRTC 66: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 1) CRTC 63: trying mode 1360x768@60Hz with output at 1366x768@60Hz (pass 1) CRTC 63: trying mode 1360x768@60Hz with output at 1366x768@60Hz (pass 1) CRTC 63: trying mode 1280x720@60Hz with output at 1366x768@60Hz (pass 1) CRTC 63: trying mode 1024x768@60Hz with output at 1366x768@60Hz (pass 1) CRTC 63: trying mode 1024x576@60Hz with output at 1366x768@60Hz (pass 1) CRTC 63: trying mode 960x540@60Hz with output at 1366x768@60Hz (pass 1) CRTC 63: trying mode 800x600@60Hz with output at 1366x768@60Hz (pass 1) CRTC 63: trying mode 800x600@56Hz with output at 1366x768@60Hz (pass 1) CRTC 63: trying mode 864x486@60Hz with output at 1366x768@60Hz (pass 1) CRTC 63: trying mode 640x480@60Hz with output at 1366x768@60Hz (pass 1) CRTC 63: trying mode 720x405@60Hz with output at 1366x768@60Hz (pass 1) CRTC 63: trying mode 680x384@60Hz with output at 1366x768@60Hz (pass 1) CRTC 63: trying mode 640x360@60Hz with output at 1366x768@60Hz (pass 1) Trying modes for CRTC 64 CRTC 64: trying mode 1366x768@60Hz with output at 1366x768@60Hz (pass 0) none of the selected modes were compatible with the possible modes: Trying modes for CRTC 63 CRTC 63: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 0) CRTC 63: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 1) Trying modes for CRTC 64 CRTC 64: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 0) CRTC 64: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 1) Trying modes for CRTC 65 CRTC 65: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 0) CRTC 65: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 1) Trying modes for CRTC 66 CRTC 66: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 0) CRTC 66: trying mode 1680x1050@60Hz with output at 1920x1080@60Hz (pass 1) CRTC 64: trying mode 1360x768@60Hz with output at 1366x768@60Hz (pass 0) CRTC 64: trying mode 1360x768@60Hz with output at 1366x768@60Hz (pass 0) CRTC 64: t
[Touch-packages] [Bug 1460149] Re: Visible corruption in SDL apps (Neverball, Neverputt) on Nexus 4 / Nexus 7.
AFAIK, the required Mir bits are in vivid-overlay already. We just need to get the latest libsdl2 into the overlay. P.S. It's not great for wily at all. The fix is apparently not in wily. Only xenial. -- 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/1460149 Title: Visible corruption in SDL apps (Neverball, Neverputt) on Nexus 4 / Nexus 7. Status in Mir: Fix Released Status in libsdl2 package in Ubuntu: Fix Released Status in mir package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Invalid Bug description: https://github.com/pseuudonym404/neverball-touch/issues/2 Install neverball or neverputt from the click store:- https://uappexplorer.com/app/neverputt.lb https://uappexplorer.com/app/neverball.lb Note they work fine on krillin and arale, however there's corruption making the games unusable on Nexus 4 and Nexus 7. Simpler test cases are provided at the above linked github issue. Attaching them to this bug for persistence. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1460149/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1538866] [NEW] apport dialog only ask which debugging work the user is willing to do if no package is specified to ubuntu-bug
Public bug reported: If the user invokes `ubuntu-bug` without argument he_she is asked which additional debugging work he_she is willing to do, but not if `ubuntu- bug` is invoked with a package as argument. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: apport-gtk 2.19.1-0ubuntu5 Uname: Linux 4.3.0-040300-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jan 28 04:41:29 2016 InstallationDate: Installed on 2013-10-17 (832 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to wily on 2015-11-19 (69 days ago) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1538866 Title: apport dialog only ask which debugging work the user is willing to do if no package is specified to ubuntu-bug Status in apport package in Ubuntu: New Bug description: If the user invokes `ubuntu-bug` without argument he_she is asked which additional debugging work he_she is willing to do, but not if `ubuntu-bug` is invoked with a package as argument. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: apport-gtk 2.19.1-0ubuntu5 Uname: Linux 4.3.0-040300-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jan 28 04:41:29 2016 InstallationDate: Installed on 2013-10-17 (832 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to wily on 2015-11-19 (69 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1538866/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1531875] Re: release new camera-app click with updated translations
** Changed in: camera-app (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1531875 Title: release new camera-app click with updated translations Status in Canonical System Image: Confirmed Status in camera-app package in Ubuntu: Confirmed Bug description: release a new click package that contains new translations that are needed for prompts to the user when they don't have correct permissions to allow camera/mic access by the app To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1531875/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1460149] Re: Visible corruption in SDL apps (Neverball, Neverputt) on Nexus 4 / Nexus 7.
While this is great for Wily, the phones which exhibit this issue are running Vivid, where the issue isn't fixed. Can the fix please be backported to vivid? -- 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/1460149 Title: Visible corruption in SDL apps (Neverball, Neverputt) on Nexus 4 / Nexus 7. Status in Mir: Fix Released Status in libsdl2 package in Ubuntu: Fix Released Status in mir package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Invalid Bug description: https://github.com/pseuudonym404/neverball-touch/issues/2 Install neverball or neverputt from the click store:- https://uappexplorer.com/app/neverputt.lb https://uappexplorer.com/app/neverball.lb Note they work fine on krillin and arale, however there's corruption making the games unusable on Nexus 4 and Nexus 7. Simpler test cases are provided at the above linked github issue. Attaching them to this bug for persistence. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1460149/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1538632] Re: ui freezes when simultaneously moving mouse & plug/unplug hdmi
** Changed in: mir
Milestone: None => 0.20.0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1538632
Title:
ui freezes when simultaneously moving mouse & plug/unplug hdmi
Status in canonical-pocket-desktop:
New
Status in Mir:
In Progress
Status in Unity System Compositor:
New
Status in unity-system-compositor package in Ubuntu:
New
Bug description:
confirmed to happen in latest image with usc0.3 and previous images
with usc0.2
steps
1) flash ubuntu-touch/rc-proposed/ubuntu-pd
2) connect bt mouse and see unity8 go into windowed mode
3) move mouse about screen while at the same time connect slimport hdmi cable
ui will then freeze but seems content, let it sit for 30 min no reboot or
restart, no crash files, power button does not do anything.
It's also possible to have the slimport already connected - move mouse around
disconnect, the ui will freeze altho in this case unity8 always seems to
restart.
There are no usc crash files.
The problem is a dead lock on the Display/DisplaySyncGroup mutexes
between CompositingFunctor->SystemWindowManager->GraphicsDisplayLayout
and DisplayInputRegion.
Thread 6 (Thread 0xb0dff3d0 (LWP 1530)):
#0 0xb6cd5d44 in __libc_do_syscall () from
/lib/arm-linux-gnueabihf/libpthread.so.0
No symbol table info available.
#1 0xb6cd395c in __lll_lock_wait () from
/lib/arm-linux-gnueabihf/libpthread.so.0
No symbol table info available.
#2 0xb6ccf19e in pthread_mutex_lock () from
/lib/arm-linux-gnueabihf/libpthread.so.0
No symbol table info available.
#3 0xb6426f02 in __gthread_mutex_lock (__mutex=0x1b34f14)
at /usr/include/arm-linux-gnueabihf/c++/4.9/bits/gthr-default.h:748
No locals.
#4 lock (this=0x1b34f14) at /usr/include/c++/4.9/mutex:135
No locals.
#5 lock_guard (__m=..., this=0xb0dfeaf0) at /usr/include/c++/4.9/mutex:377
No locals.
#6 mir::graphics::android::Display::configuration (this=0x1b34ef8)
at
/build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/platforms/android/server/display.cpp:231
lock = {_M_device = @0x1b34f14}
#7 0xb6e656ca in mir::shell::GraphicsDisplayLayout::place_in_output
(this=, id=...,
rect=...)
at
/build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/server/shell/graphics_display_layout.cpp:72
config = std::unique_ptr
containing 0xb6eb69c8
placed = false
#8 0xb6e6a888 in mir::shell::SystemCompositorWindowManager::add_display
(this=0x1d07b24)
at
/build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/server/shell/system_compositor_window_manager.cpp:1
output_id =
rect = {top_left = {x = {value = 0}, y = {value = 0}}, size = {width
= {value = 768}, height = {
value = 1280}}}
surface = std::shared_ptr (count 3, weak 4) 0x0
__for_range =
lock = {_M_device = @0x1d07b3c}
#9 0xb6e1ab32 in operator() (buffer=..., __closure=)
at
/build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/server/compositor/multi_threaded_compositor.cpp:96
No locals.
#10 std::_Function_handler::_M_invoke(std::_Any_data
const&, mir::graphics::DisplayBuffer&) (__functor=..., __args#0=...)
at /usr/include/c++/4.9/functional:2039
No locals.
#11 0xb64288a8 in operator() (__args#0=..., this=0xb0dfeca0) at
/usr/include/c++/4.9/functional:2439
No locals.
#12
mir::graphics::android::DisplayGroup::for_each_display_buffer(std::function const&) (this=0x1b35024, f=...)
at
/build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/platforms/android/server/display_group.cpp:51
__for_range = std::map with 1 elements = {
[mir::graphics::android::DisplayName::primary] =
std::unique_ptr containing
0x1c0db40}
lk = {_M_device = 0x1b35028, _M_owns = true}
#13 0xb6e1b896 in operator() (__closure=)
at
/build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/server/compositor/multi_threaded_compositor.cpp:96
No locals.
#14 PairedCalls (deleter=, creator=,
this=0xb0dfec84)
at
/build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/include/common/mir/raii.h:33
No locals.
#15
paired_calls,
mir::compositor::CompositingFunctor::operator()():: >
(deleter=, creator=)
at
/build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/include/common/mir/raii.h:66
No locals.
#16 mir::compositor::CompositingFunctor::operator() (this=0x1d112d8)
at
/build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/server/compositor/multi_threaded_compositor.cpp:98
disp_listener = std::shared_ptr (count 5, weak 2) 0x1d07aac
display_registration = {deleter = {__this = 0x1d112d8,
__disp_listener = std::shared_ptr (count 5, weak 2) 0x1d07aac},
owner = true}
compositor_registration =
compositors = std::vector of length 1, capacity 1 = {std::tuple
containing = {[1] = 0x1c0db4
[Touch-packages] [Bug 1483475] Re: lintian: E: mir-test-tools: arch-dependent-file-not-in-arch-specific-directory
** Changed in: mir Milestone: 0.20.0 => 0.19.0 ** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- 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/1483475 Title: lintian: E: mir-test-tools: arch-dependent-file-not-in-arch-specific- directory Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: Lintian reports: E: mir-test-tools: arch-dependent-file-not-in-arch-specific-directory usr/bin/mir_acceptance_tests E: mir-test-tools: arch-dependent-file-not-in-arch-specific-directory usr/bin/mir_integration_tests E: mir-test-tools: arch-dependent-file-not-in-arch-specific-directory usr/bin/mir_performance_tests E: mir-test-tools: arch-dependent-file-not-in-arch-specific-directory usr/bin/mir_privileged_tests E: mir-test-tools: arch-dependent-file-not-in-arch-specific-directory usr/bin/mir_stress E: mir-test-tools: arch-dependent-file-not-in-arch-specific-directory usr/bin/mir_test_reload_protobuf E: mir-test-tools: arch-dependent-file-not-in-arch-specific-directory usr/bin/mir_unit_tests To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1483475/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1527449] Re: Mir clients leak all driver modules including the unused ones, keeping them resident
** Changed in: mir Milestone: 0.20.0 => 0.19.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1527449 Title: Mir clients leak all driver modules including the unused ones, keeping them resident Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: Mir clients leak all driver modules including the unused ones, keeping them resident. $ sudo mir_demo_server $ sudo mir_demo_client_egltriangle $ sudo grep client- /proc/`pidof mir_demo_client_egltriangle`/maps 7f7ff23e7000-7f7ff23f5000 r-xp 08:02 6050064 /usr/lib/x86_64-linux-gnu/mir/client-platform/mesa.so.3 7f7ff23f5000-7f7ff25f5000 ---p e000 08:02 6050064 /usr/lib/x86_64-linux-gnu/mir/client-platform/mesa.so.3 7f7ff25f5000-7f7ff25f6000 r--p e000 08:02 6050064 /usr/lib/x86_64-linux-gnu/mir/client-platform/mesa.so.3 7f7ff25f6000-7f7ff25f7000 rw-p f000 08:02 6050064 /usr/lib/x86_64-linux-gnu/mir/client-platform/mesa.so.3 7f7ff2c22000-7f7ff2c35000 r-xp 08:02 6051608 /usr/lib/x86_64-linux-gnu/mir/client-platform/android.so.3 7f7ff2c35000-7f7ff2e35000 ---p 00013000 08:02 6051608 /usr/lib/x86_64-linux-gnu/mir/client-platform/android.so.3 7f7ff2e35000-7f7ff2e36000 r--p 00013000 08:02 6051608 /usr/lib/x86_64-linux-gnu/mir/client-platform/android.so.3 7f7ff2e36000-7f7ff2e37000 rw-p 00014000 08:02 6051608 /usr/lib/x86_64-linux-gnu/mir/client-platform/android.so.3 I think this also explains bug 1526658 as some people might also have mesa.so.2 still installed. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1527449/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1534929] Re: [USB-Audio - USB PnP Sound Device, playback] volume slider problem: USB headset playback suddenly drops to inaudible when volume is set below a certain level
You need pulseaudio ignore hardware volume control by specify ignore_DB=1 when pulseaudio load module-udev-detect -- 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/1534929 Title: [USB-Audio - USB PnP Sound Device, playback] volume slider problem: USB headset playback suddenly drops to inaudible when volume is set below a certain level Status in alsa-driver package in Ubuntu: New Bug description: With this headset: [ 9922.706941] usb 1-1.4: new full-speed USB device number 4 using ehci-pci [ 9922.805274] usb 1-1.4: New USB device found, idVendor=1ea7, idProduct=0055 [ 9922.805279] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 9922.805282] usb 1-1.4: Product: USB PnP Sound Device [ 9922.805284] usb 1-1.4: Manufacturer: C-Media Electronics Inc. [ 9922.806688] input: C-Media Electronics Inc. USB PnP Sound Device as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.3/input/input12 [ 9922.806802] hid-generic 0003:1EA7:0055.0002: input,hidraw1: USB HID v1.00 Device [C-Media Electronics Inc. USB PnP Sound Device] on usb-:00:1a.0-1.4/input3 [ 9922.872746] usbcore: registered new interface driver snd-usb-audio called "CSL Stormrider Wired Headset", playback becomes suddenly inaudible when the volume slider in the unity sound preferences (accessed via indicator → loudspeaker icon → sound settings) is set to below circa 40 %. Setting to above ~40 % restores playback volume to what you would expect. In alsamixer, the same problem occurs when going from volume level 02 to volume level 01. At alsamixer level 02, the volume is about what you would expect when setting a volume slider to about 40 %. This is annoying since 40 % can already be rather loud. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30 Uname: Linux 3.13.0-74-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jan 16 14:25:15 2016 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Integrated Rate Matching Hub - USB PnP Sound Device Symptom_Type: Volume slider, or mixer problems Title: [USB-Audio - USB PnP Sound Device, playback] volume slider problem UpgradeStatus: Upgraded to trusty on 2014-05-24 (602 days ago) dmi.bios.date: 12/10/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: B75 Pro3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd12/10/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB75Pro3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1534929/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1526658] Re: Mir may use incompatible client platform to validate server display and crash in XGetXCBConnection()
** Changed in: mir Milestone: 0.20.0 => 0.19.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1526658 Title: Mir may use incompatible client platform to validate server display and crash in XGetXCBConnection() Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: The mir egl platform fails to load under certain circumstances producing the following stack trace: #0 0x73a996e7 in XGetXCBConnection () from /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1 #1 0x7534dc74 in dri2_initialize_x11_dri2 (drv=, disp=0x6d1b90) at ../../../../src/egl/drivers/dri2/platform_x11.c:1268 #2 dri2_initialize_x11 (drv=, disp=0x6d1b90) at ../../../../src/egl/drivers/dri2/platform_x11.c:1357 #3 0x75347adf in _eglMatchAndInitialize (dpy=0x6d1b90) at ../../../../src/egl/main/egldriver.c:261 #4 0x75347b99 in _eglMatchDriver (dpy=dpy@entry=0x6d1b90, test_only=test_only@entry=0) at ../../../../src/egl/main/egldriver.c:292 #5 0x75343b32 in eglInitialize (dpy=0x6d1b90, major=0x7fffdac8, minor=0x7fffdacc) at ../../../../src/egl/main/eglapi.c:482 #6 0x7686cc1f in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.36 #7 0x7686cd7b in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.36 #8 0x7686d420 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.36 #9 0x759dd82c in mir::graphics::OverlappingOutputGrouping::for_each_group(std::function const&) () from /usr/lib/x86_64-linux-gnu/libmirplatform.so.11 #10 0x7686de6b in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.36 #11 0x7686e450 in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.36 #12 0x767fef3c in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.36 #13 0x767ff87d in ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.36 #14 0x767fde31 in mir::DefaultServerConfiguration::the_display() () from /usr/lib/x86_64-linux-gnu/libmirserver.so.36 In the given case a 0.17.1 mirclient9 was combined with a 0.18 mirserver36. mirserver36 is compatible with mirclient9. The mirserver36 works with mirclient9. The significant difference lies in the client and server platforms. The native display used for egl initialization is created by the server. Mesa then uses a function from the client platform to validate the native display. For yet unknown reason the 0.17.1 libmirclient9 did select mesa.so.2 (from mir-client-platform-mesa2 0.14). Thus the validation failed. It did so probably because that version was a left over of the 0.14 release with a partially bumped ABI. So the remaining issue is that there is an ABI we have to care about between the native EGL Display given to mesa, and the client platform that validates it. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1526658/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1483472] Re: lintian: W: mir-doc: embedded-javascript-library usr/share/doc/mir-doc/html/jquery.js please use libjs-jquery
** Changed in: mir Milestone: 0.20.0 => 0.19.0 ** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- 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/1483472 Title: lintian: W: mir-doc: embedded-javascript-library usr/share/doc/mir- doc/html/jquery.js please use libjs-jquery Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: W: mir-doc: embedded-javascript-library usr/share/doc/mir- doc/html/jquery.js please use libjs-jquery To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1483472/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1476201] Re: Dynamic double buffering fails to detect inertial dash scrolling as slow; and stutters instead of scaling up to triple buffers.
** Changed in: mir Milestone: 0.20.0 => 0.19.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1476201 Title: Dynamic double buffering fails to detect inertial dash scrolling as slow; and stutters instead of scaling up to triple buffers. Status in Mir: Fix Committed Status in QtMir: Opinion Status in mir package in Ubuntu: Invalid Status in qtmir package in Ubuntu: Opinion Bug description: Dynamic double buffering fails to detect inertial dash scrolling as slow; and stutters... [1437388267.960199] perf: Scopes: 37.69 FPS, render time 17.79ms, buffer lag 34.87ms (2 buffers) [1437388268.985012] perf: Scopes: 30.27 FPS, render time 25.22ms, buffer lag 40.29ms (2 buffers) [1437388269.993894] perf: Scopes: 31.74 FPS, render time 23.42ms, buffer lag 40.46ms (2 buffers) [1437388271.002470] perf: Scopes: 36.70 FPS, render time 19.13ms, buffer lag 35.59ms (2 buffers) [1437388272.021942] perf: Scopes: 44.16 FPS, render time 15.96ms, buffer lag 29.12ms (2 buffers) [1437388273.043734] perf: Scopes: 40.15 FPS, render time 17.85ms, buffer lag 31.90ms (2 buffers) whereas forcing triple buffers it runs more smoothly: [1437389981.872839] perf: Scopes: 57.71 FPS, render time 13.86ms, buffer lag 38.31ms (3 buffers) [1437389982.877556] perf: Scopes: 56.77 FPS, render time 15.72ms, buffer lag 37.31ms (3 buffers) [1437389983.887702] perf: Scopes: 57.42 FPS, render time 13.53ms, buffer lag 38.76ms (3 buffers) [1437389984.894372] perf: Scopes: 55.66 FPS, render time 16.02ms, buffer lag 38.12ms (3 buffers) [1437389985.912328] perf: Scopes: 60.96 FPS, render time 13.72ms, buffer lag 34.99ms (3 buffers) [1437389986.929857] perf: Scopes: 59.98 FPS, render time 14.49ms, buffer lag 35.67ms (3 buffers) You can see that unity8-dash is right on the edge here. Surprisingly the problem is not detectable if you keep your finger on the screen. Then the dash actually renders faster. The problem only seems to happen with inertial scrolling; when you fling the surface and lift your finger off. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1476201/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1535297] Re: Unity8 crashes on session logout on desktop
Indeed libprotobuf-lite is more desirable than libprotobuf. It was a significant step forward when Alberto made it possible for Mir to switch to "lite". Although both protobuf versions suffer for coexistence problems, obviously. ** Changed in: mir (Ubuntu) Status: New => Won't Fix ** Changed in: mir Status: Invalid => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1535297 Title: Unity8 crashes on session logout on desktop Status in Mir: Won't Fix Status in libphonenumber package in Ubuntu: New Status in mir package in Ubuntu: Won't Fix Status in telephony-service package in Ubuntu: New Status in unity8 package in Ubuntu: Confirmed Bug description: This is happening on a fresh setup, which is basically: Xenial 17Jan iso + unity8-desktop-session-mir package When I logout, I get a black screen. Turns out unity8 is crashing with a "double free or linked list corruption" Please find unity8.log attached To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1535297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1532202] Re: [android] External monitor slows rendering
** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- 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/1532202 Title: [android] External monitor slows rendering Status in canonical-pocket-desktop: In Progress Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: Seen on mako (mir-0.18) - Gerry reports also on Flo. Setup: sudo stop lightdm mirbacklight $ mir_demo_server --file host --window-manager system-compositor --display-config sidebyside& $ MIR_CLIENT_PERF_REPORT=log bin/mir_demo_server --host host --display-config sidebyside --launch-client mir_demo_client_egltriangle Observe: triangle spins evenly with FPS around 60. Test: Plug in external monitor Expect: triangle spins evenly with FPS around 60. Actual: triangle motion slows and jerks with FPS around 50. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1532202/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1530946] Re: Setting a surface keymap crashes in xkbcommon: xkb_keymap_new_from_names()
** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- 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/1530946 Title: Setting a surface keymap crashes in xkbcommon: xkb_keymap_new_from_names() Status in The Avila project: New Status in Canonical System Image: Triaged Status in canonical-pocket-desktop: Triaged Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: Trying to set a keymap on a Mir surface crashes somewhere between Mir and xkbcommon with this backtrace: http://paste.ubuntu.com/14399228/ Code from: https://code.launchpad.net/~lukas-kde/qtmir/kbdLayout and https://code.launchpad.net/~lukas-kde/unity8/kbdLayout The xkb_names structure (four char*) is sent over the wire as four addresses. Our tests do not fail because they use the in process client.. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1530946/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1523900] Re: Buffer leak during repeated mirscreencasts causes server to be killed
** Changed in: mir (Ubuntu) Status: New => Triaged ** Changed in: mir (Ubuntu) Importance: Undecided => High -- 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/1523900 Title: Buffer leak during repeated mirscreencasts causes server to be killed Status in Mir: Fix Committed Status in Mir 0.18 series: Fix Committed Status in mir package in Ubuntu: Triaged Bug description: Nexus 4 running latest stable image - current build number: 25 device name: mako channel: ubuntu-touch/stable/ubuntu last update: 2015-12-08 11:53:16 version version: 25 version ubuntu: 20151118.2 version tag: OTA-8 version device: 20150911 version custom: 20151118.2 I'm running the following command to capture a screenshot of a running app, the unity shell, the splash screen when apps load etc. adb shell mirscreencast -m /var/run/mir_socket -n1 I'm doing this in a script, across many hundreds of apps, so I'm doing it a lot. I'm seeing my script get wedged fairly often with errors such as this one:- [1449575031.562843] MirConnectionAPI: Caught exception at client library boundary (in release): /build/mir-AHj2eT/mir-0.17.1+15.04.20151105.1/src/client/rpc/stream_socket_transport.cpp(168): Throw in function virtual void mir::client::rpc::StreamSocketTransport::send_message(const std::vector&, const std::vector&) Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorIN3mir25socket_disconnected_errorE std::exception::what: Failed to send message to server: Broken pipe To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1523900/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1528082] Re: [regression] Mir servers choose graphics-dummy (or no driver at all) over mesa-kms on a desktop
** Changed in: mir (Ubuntu) Importance: Undecided => Medium ** Changed in: mir (Ubuntu) Status: New => Triaged -- 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/1528082 Title: [regression] Mir servers choose graphics-dummy (or no driver at all) over mesa-kms on a desktop Status in Mir: Fix Committed Status in Mir 0.18 series: Fix Committed Status in mir package in Ubuntu: Triaged Bug description: Mir demo servers fail to start without additional help. Running the latest code on a xenial system, I find the Mir demo servers fail to start when run from ssh and I am logged into X (or on the login screen): [1450665937.536318] mirserver: Selected driver: dummy (version 0.19.0) ... ERROR: /home/dan/bzr/mir/trunk/src/renderers/gl/renderer.cpp(51): Throw in function mir::renderer::gl::CurrentRenderTarget::CurrentRenderTarget(mir::graphics::DisplayBuffer*) Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: DisplayBuffer does not support GL rendering This is obviously wrong, because for Mir to choose the dummy driver means mesa-kms has returned a platform priority of zero (unsupported). Mesa-kms is not "unsupported", it's the right platform! To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1528082/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1536662] Re: [regression] Mir blocks at system boot due to reading from /dev/random
** Changed in: unity-system-compositor Status: Fix Committed => In Progress ** Changed in: unity-system-compositor Milestone: 0.4.0 => 0.4.1 -- 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/1536662 Title: [regression] Mir blocks at system boot due to reading from /dev/random Status in Mir: Confirmed Status in Unity System Compositor: In Progress Status in mir package in Ubuntu: New Bug description: cookie_factory attempts to read data from /dev/random at boot, and blocks until it has enough random data or timesout after 30 seconds. How I can reproduce 1. Run the Unity8 greeter as a mir server 2. Reboot Expected behavior: Greeter is displayed as mir && USC run happily Actual behavior: Mir throws an exception after 30 seconds Work-around: Play with the trackpad at bootup to generate entropy. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1536662/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1517205] Re: [mali gpu] egl_demo_client_flicker has graphics corruption on android
** Changed in: mir (Ubuntu) Status: In Progress => Triaged -- 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/1517205 Title: [mali gpu] egl_demo_client_flicker has graphics corruption on android Status in The Avila project: New Status in canonical-pocket-desktop: In Progress Status in Mir: In Progress Status in mir package in Ubuntu: Triaged Bug description: Investigation of lp: #1406725 yielded two different problems, this is the second problem that affected mir_demo_client_flicker most heavily. When running mir_demo_client_flicker against "mir_demo_server --disable-overlays true", you could see cache-line artifacts, as well as an occasional tile-render-gpu artifact displayed on screen. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1517205/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1509846] Re: lightdm crashes on window open in Ubuntu 15.10 intel
This stream of comments is difficult to follow. If one of the most knowledgeable people could summarize where we are, it might be useful. I am experiencing this problem also, on a Lenovo X230 under Ubuntu 15.10, since a month or so ago. "sudo apt-get dist-upgrade" certainly is not a solution for me (indeed, you might say that's what started the problem!), and I don't actually think Christopher M. Penalver was suggesting that as a fix. This is certainly a "critical" problem, and most frustrating a development for what was a stable machine. As I understand it: it will still be useful if I do a "ubuntu-bug xorg" after the next time it crashes, and after logging back in? (or from a tty login, before logging back in?). I have xdiagnose installed. -- 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/1509846 Title: lightdm crashes on window open in Ubuntu 15.10 intel Status in Light Display Manager: Confirmed Status in lightdm package in Ubuntu: Triaged Bug description: Symptom: xorg crashes on windows creation How to reproduce: No 100% reproducibility, however intensively using 2D/3D acceleration triggers the bug (e.g. by opening several new windows and/or menus in a Unity desktop environment) Affected hardware: Intel HD Graphics 4400/5000 etc Affected software: - kernel 4.2.0-16-generic #19-Ubuntu SMP Thu Oct 8 15:35:06 UTC 2015 x86_64 - Ubuntu 15.10 with Unity (because of compiz 2D/3D acceleration) - any other software using direct rendering (e.g. VLC) Workaround: - Disable window animations in Compiz reduces the frequency of the crashes. Use compizconfig-settings-manager for this tweak (sudo apt-get install compizconfig-settings-manager) [original description below] I get crashes, when I open a new window in an already started application. It happens irregularely, but I can force the crash if I open several new message windows in thunderbird. But it also happens in other applilcations, for example a new terminal window. This is the output during the crash in /var/log/Xorg.0.log [ 253.500] (EE) [ 253.500] (EE) Backtrace: [ 253.500] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55f09075b62e] [ 253.500] (EE) 1: /usr/bin/X (0x55f0905a7000+0x1b8999) [0x55f09075f999] [ 253.500] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f44130a8000+0x352f0) [0x7f44130dd2f0] [ 253.500] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f440f47f000+0x24f18) [0x7f440f4a3f18] [ 253.500] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f440f47f000+0x26157) [0x7f440f4a5157] [ 253.500] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f440f47f000+0x2b4b1) [0x7f440f4aa4b1] [ 253.500] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f440f47f000+0x804e4) [0x7f440f4ff4e4] [ 253.501] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f440f47f000+0x80e2c) [0x7f440f4ffe2c] [ 253.501] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f440f47f000+0x82e1a) [0x7f440f501e1a] [ 253.501] (EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f440f47f000+0x4197c) [0x7f440f4c097c] [ 253.501] (EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f440f47f000+0x59906) [0x7f440f4d8906] [ 253.501] (EE) 11: /usr/bin/X (_CallCallbacks+0x34) [0x55f090604654] [ 253.501] (EE) 12: /usr/bin/X (WriteToClient+0x244) [0x55f09075f274] [ 253.501] (EE) 13: /usr/bin/X (WriteEventsToClient+0x1e2) [0x55f09060a502] [ 253.501] (EE) 14: /usr/bin/X (0x55f0905a7000+0xf495a) [0x55f09069b95a] [ 253.501] (EE) 15: /usr/bin/X (0x55f0905a7000+0xf5ef5) [0x55f09069cef5] [ 253.501] (EE) 16: /usr/bin/X (0x55f0905a7000+0x5818f) [0x55f0905ff18f] [ 253.501] (EE) 17: /usr/bin/X (0x55f0905a7000+0x5c34b) [0x55f09060334b] [ 253.501] (EE) 18: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7f44130c8a40] [ 253.501] (EE) 19: /usr/bin/X (_start+0x29) [0x55f0905ed6c9] [ 253.501] (EE) [ 253.501] (EE) Segmentation fault at address 0x0 [ 253.501] (EE) Fatal server error: [ 253.501] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 253.501] (EE) [ 253.501] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 253.501] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 253.502] (EE) [ 253.502] (II) AIGLX: Suspending AIGLX clients for VT switch [ 253.588] (EE) Server terminated with error (1). Closing log file. --- .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true DistUpgraded: Fresh install DistroC
[Touch-packages] [Bug 1460149] Re: Visible corruption in SDL apps (Neverball, Neverputt) on Nexus 4 / Nexus 7.
It appears the required fix is now in xenial (but not in wily) with 2.0.4+dfsg1-2ubuntu1 - https://launchpad.net/ubuntu/+source/libsdl2 I haven't tested the new libsdl2 myself, but the source code seems to be doing the right thing now :) ** Changed in: libsdl2 (Ubuntu) Status: Incomplete => Fix Released -- 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/1460149 Title: Visible corruption in SDL apps (Neverball, Neverputt) on Nexus 4 / Nexus 7. Status in Mir: Fix Released Status in libsdl2 package in Ubuntu: Fix Released Status in mir package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Invalid Bug description: https://github.com/pseuudonym404/neverball-touch/issues/2 Install neverball or neverputt from the click store:- https://uappexplorer.com/app/neverputt.lb https://uappexplorer.com/app/neverball.lb Note they work fine on krillin and arale, however there's corruption making the games unusable on Nexus 4 and Nexus 7. Simpler test cases are provided at the above linked github issue. Attaching them to this bug for persistence. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1460149/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1523100] Re: Alsa not detecting internal microphone [ALC255]
If only internal mic is missing , hp, internal speaker and mic jack work as expected, you need to retask the remaining unconnected pin complex with pincap IN one by one, set as bopt defaul and reboot to test the internmal mic -- 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/1523100 Title: Alsa not detecting internal microphone [ALC255] Status in alsa-driver package in Ubuntu: Confirmed Bug description: I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer Aspire VN7-792G and noticed, that the internal microphone doesn't work. The computer has been released a couple of months ago and it's Intel Skylake -based with a Sunrise Point -based motherboard. INFO: The problem exists in Ubuntu 15.10 too, only microphone jack detected. Currently using Ubuntu 16.04 for proper hardware support. Alsa reports the audio device to be: Card: HDA Intel PCH Chip: Intel Skylake HDMI The speakers are working fine, but both alsamixer and pavucontrol (Pulseaudio Volume Control) raport the unplugged external microphone connector as the only sound input. I have tried many of the alsa model configurations (options snd-hda- intel model=something) without success, alsa finds only the microphone jack, which works fine when I plug an external microphone in it. Here's some info: lspci | grep -I audio: 00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H HD Audio (rev 31) cat /proc/asound/cards: 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x8432 irq 128 And a clip from dmesg | grep snd: [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs: [3.047514] snd_hda_codec_realtek hdaudioC0D0: Mic=0x1a One problem is that I can't find any model options (options snd-hda- intel model=something) or other parameters for the card's model (ALC255), I suppose this issue is relatively new. /Dennis --- ApportVersion: 2.19.2-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dennis 1180 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-11-11 (23 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151110) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Tags: xenial Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/25/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.02 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire VN7-792G dmi.board.vendor: Acer dmi.board.version: V1.02 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02: dmi.product.name: Aspire VN7-792G dmi.product.version: V1.02 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1538823] [NEW] Menu bar menu options are small and do not reflect system font changes
Public bug reported: Just upgraded to Ubuntu 15.10 The individual menu bar menu options are very small. I am not talking about the menu bar title or the menu names e.g. "File" "Edit" etc., I'm talking about the individual options within each menu. I expect the text of the menu items to be the same as other UI text, e.g. the Ubuntu Default font. Also, I would expect the size of the menu options text to change with the setting System Settings > Universal Access > Large Text but it does not. See attached image for two screen shots, one with Large Text disabled and one with it enabled. The text "Contents", "Universal Access", and "Quit" is the text that I expect to be bigger, and that I expect to get larger when enabling the Large Text setting. Further, the size of the menu item text is not affected by any of the font settings exposed by the app "ubuntu-tweak" which lets you change the default font, etc. This problem exists whether the menu bar is pinned to the top of the screen, or to the title bar of the individual application windows. I think this is a bug in xorg, but I am not sure. lsb_release -rd Description:Ubuntu 15.10 Release:15.10 apt-cache policy xorg xorg: Installed: 1:7.7+7ubuntu4 Candidate: 1:7.7+7ubuntu4 Version table: *** 1:7.7+7ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Two screenshots of small menu items; Large Text disabled and enabled." https://bugs.launchpad.net/bugs/1538823/+attachment/4558006/+files/LargeTextEnabledAndDisabled-SideBySide.png -- 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/1538823 Title: Menu bar menu options are small and do not reflect system font changes Status in xorg package in Ubuntu: New Bug description: Just upgraded to Ubuntu 15.10 The individual menu bar menu options are very small. I am not talking about the menu bar title or the menu names e.g. "File" "Edit" etc., I'm talking about the individual options within each menu. I expect the text of the menu items to be the same as other UI text, e.g. the Ubuntu Default font. Also, I would expect the size of the menu options text to change with the setting System Settings > Universal Access > Large Text but it does not. See attached image for two screen shots, one with Large Text disabled and one with it enabled. The text "Contents", "Universal Access", and "Quit" is the text that I expect to be bigger, and that I expect to get larger when enabling the Large Text setting. Further, the size of the menu item text is not affected by any of the font settings exposed by the app "ubuntu-tweak" which lets you change the default font, etc. This problem exists whether the menu bar is pinned to the top of the screen, or to the title bar of the individual application windows. I think this is a bug in xorg, but I am not sure. lsb_release -rd Description: Ubuntu 15.10 Release: 15.10 apt-cache policy xorg xorg: Installed: 1:7.7+7ubuntu4 Candidate: 1:7.7+7ubuntu4 Version table: *** 1:7.7+7ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1538823/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1515067] Re: Redundant requests for artist art
** Changed in: music-app Milestone: None => ota10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to thumbnailer in Ubuntu. https://bugs.launchpad.net/bugs/1515067 Title: Redundant requests for artist art Status in Ubuntu Music App: In Progress Status in thumbnailer package in Ubuntu: Triaged Bug description: I'm seeing redundant requests in the thumbnailer for every artist. For example: thumbnailer-service: [00:33:58.397] "artist: Mamady Keïta/Afö (512,512): 5.732672 [q: 4.476239, d: 1.065771] sec (MISS)" thumbnailer-service: [00:33:58.439] "artist: Mamady Keïta/ (512,512): 5.774881 [q: 3.434976, d: 2.267816] sec (MISS)" thumbnailer-service: [00:33:56.041] "artist: Passport/ (512,512): 3.741614 [d: 3.681184] sec (MISS)" thumbnailer-service: [00:33:56.144] "artist: Passport/Passport to Paradise (512,512): 3.480054 [d: 3.446207] sec (MISS)" thumbnailer-service: [00:34:02.958] "artist: Pink Floyd/The Dark Side Of The Moon [2011 - Remaster] (512,512): 10.288417 [q: 6.923973, d: 3.262566] sec (MISS)" thumbnailer-service: [00:34:04.315] "artist: Pink Floyd/ (512,512): 11.646238 [q: 10.182878, d: 1.348939] sec (MISS)" For every artist, it appears that a request is sent for the artist with an empty album title, plus a request for the artist with an album title. This is not great because it results in two remote server accesses for each artist. This hammers the CPU and the network on the phone, as well as the server on dash.ubuntu.com. To manage notifications about this bug go to: https://bugs.launchpad.net/music-app/+bug/1515067/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1509291] Re: CI Failures: ClientLatency.throttled_input_rate_yields_lower_latency
I suspect you're right. Although I suspect the problem possibly returned with r3254. I keep seeing acceptance test failures locally. Then get suspicious and when I look again they are passing :S -- 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/1509291 Title: CI Failures: ClientLatency.throttled_input_rate_yields_lower_latency Status in Mir: Fix Committed Status in mir package in Ubuntu: New Bug description: The test may fail easily https://jenkins.qa.ubuntu.com/job/mir-mediumtests-runner-touch/7175/consoleFull [ RUN ClientLatency.throttled_input_rate_yields_lower_latency /tmp/buildd/mir-0.17.0+15.10.20151008.2bzr3050pkg0wily4549+autopilot0/tests/acceptance-tests/test_latency.cpp:259: Failure Value of: observed_latency Expected: is < 1.1 Actual: 1.19 (of type float) [ FAILED ] ClientLatency.throttled_input_rate_yields_lower_latency (2334 ms) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1509291/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378143] Re: [Music App and Scope] Consistent use of "Songs" or "Tracks" between Music app and Music scope
** Changed in: music-app Milestone: None => ota10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-mediascanner in Ubuntu. https://bugs.launchpad.net/bugs/1378143 Title: [Music App and Scope] Consistent use of "Songs" or "Tracks" between Music app and Music scope Status in Ubuntu Music App: Triaged Status in Ubuntu UX: Fix Committed Status in unity-scope-mediascanner package in Ubuntu: Triaged Bug description: It'd be ideal if both the Music app (which currently uses "Songs") and the Music scope (which uses "Tracks") used similar terminology. To manage notifications about this bug go to: https://bugs.launchpad.net/music-app/+bug/1378143/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1504084] Re: On unity8 desktop, websites serve mobile version
I still get mobile sites on my Nexus 7 even on desktop mode. Is this bug only for the desktop and not for touch devices? -- 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/1504084 Title: On unity8 desktop, websites serve mobile version Status in Canonical System Image: Fix Released Status in webbrowser-app package in Ubuntu: Fix Released Bug description: On unity8 on desktop, the webbrowser-app shows the mobile version of websites. This can be reproduced with e.g. http://github.com To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1504084/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1444682] Re: Software properties gtk implies my cpu is unknown and not working.
Confirmed in Lubuntu Xenial Xerus Alpha 2. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1444682 Title: Software properties gtk implies my cpu is unknown and not working. Status in software-properties package in Ubuntu: Triaged Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: To reproduce install lubuntu 415 i386 on a t6500 core 2 duo cpu. I know I am installing 32 bit on 64 but it will show like in with both a braodcom 4322 which I have not yet installed the prorpietary driver and this intel cpu. Open additional drivers from the menu in lxde. software-properties-gtk: Installed: 0.96.4 Candidate: 0.96.4 Version table: *** 0.96.4 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main i386 Packages 100 /var/lib/dpkg/status Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 https://gist.github.com/dabcbbc9bdcb7ed8d87d is the hardware tracker profile for this laptop. I expected software-properties-gtk to not say my processor is unkown and not working because I have not installed the latest microcode. Instead it said this device which can use the proprietary intel microcode driver is unknown and not working and the only device this makes sense to be is the cpu. I have a screenshot attached of the messages that make no sense. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: software-properties-gtk 0.96.4 ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic i686 ApportVersion: 2.17.1-0ubuntu1 Architecture: i386 CurrentDesktop: LXDE Date: Wed Apr 15 13:11:51 2015 InstallationDate: Installed on 2015-04-15 (0 days ago) InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Beta i386 (20150415) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1444682/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1333522] Re: add README file
The app can be run with the qmlscene command: qmlscene path/to/app/messaging-app.qml -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1333522 Title: add README file Status in messaging-app package in Ubuntu: In Progress Bug description: The project needs a README with at least: - what the project is - how to build it - how to test it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1333522/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1538723] Re: rsyslog user process faults on s390x
attached gdb session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1538723 Title: rsyslog user process faults on s390x Status in rsyslog package in Ubuntu: New Bug description: [ 38.553696] User process fault: interruption code 003b ilc:3 in lmnsd_gtls.so[3ff9120+8000] [ 38.553701] failing address: TEID: 0800 [ 38.553703] Fault in primary space mode while using user ASCE. [ 38.553706] AS:0001b6d4c1c7 R3:0024 [ 38.553710] CPU: 3 PID: 4218 Comm: in:imtcp Tainted: GE 4.3.0-6-generic #17-Ubuntu [ 38.553711] task: 0001f2e60a78 ti: 0001dafc4000 task.ti: 0001dafc4000 [ 38.553712] User PSW : 070520018000 03ff91202f8e [ 38.553713]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0 EA:3 User GPRS: 03ff897fd1b8 0050 [ 38.553715] 03ff6c003c90 [ 38.553715]0001 [ 38.553716]03ff91c9c000 03ff897fd1b8 03ff91202f78 03ff897fd048 [ 38.553721] User Code: 03ff91202f7c: e54cd001 mvhi 0(%r13),1 03ff91202f82: e310d0080024 stg %r1,8(%r13) #03ff91202f88: e54cd011 mvhi 16(%r13),1 >03ff91202f8e: e31020580004 lg %r1,88(%r2) 03ff91202f94: a729 lghi%r2,0 03ff91202f98: e310d0180024 stg %r1,24(%r13) 03ff91202f9e: e54cd020 mvhi 32(%r13),0 03ff91202fa4: e340f114 lg %r4,272(%r15) [ 38.553730] Last Breaking-Event-Address: [ 38.553731] [<03ff9104bb66>] 0x3ff9104bb66 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1538723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1538723] Re: rsyslog user process faults on s390x
smells bad -> Backtrace stopped: previous frame inner to this frame (corrupt stack?) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1538723 Title: rsyslog user process faults on s390x Status in rsyslog package in Ubuntu: New Bug description: [ 38.553696] User process fault: interruption code 003b ilc:3 in lmnsd_gtls.so[3ff9120+8000] [ 38.553701] failing address: TEID: 0800 [ 38.553703] Fault in primary space mode while using user ASCE. [ 38.553706] AS:0001b6d4c1c7 R3:0024 [ 38.553710] CPU: 3 PID: 4218 Comm: in:imtcp Tainted: GE 4.3.0-6-generic #17-Ubuntu [ 38.553711] task: 0001f2e60a78 ti: 0001dafc4000 task.ti: 0001dafc4000 [ 38.553712] User PSW : 070520018000 03ff91202f8e [ 38.553713]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0 EA:3 User GPRS: 03ff897fd1b8 0050 [ 38.553715] 03ff6c003c90 [ 38.553715]0001 [ 38.553716]03ff91c9c000 03ff897fd1b8 03ff91202f78 03ff897fd048 [ 38.553721] User Code: 03ff91202f7c: e54cd001 mvhi 0(%r13),1 03ff91202f82: e310d0080024 stg %r1,8(%r13) #03ff91202f88: e54cd011 mvhi 16(%r13),1 >03ff91202f8e: e31020580004 lg %r1,88(%r2) 03ff91202f94: a729 lghi%r2,0 03ff91202f98: e310d0180024 stg %r1,24(%r13) 03ff91202f9e: e54cd020 mvhi 32(%r13),0 03ff91202fa4: e340f114 lg %r4,272(%r15) [ 38.553730] Last Breaking-Event-Address: [ 38.553731] [<03ff9104bb66>] 0x3ff9104bb66 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1538723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1538723] Re: rsyslog user process faults on s390x
** Attachment added: "rsyslogd.txt" https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1538723/+attachment/4557992/+files/rsyslogd.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1538723 Title: rsyslog user process faults on s390x Status in rsyslog package in Ubuntu: New Bug description: [ 38.553696] User process fault: interruption code 003b ilc:3 in lmnsd_gtls.so[3ff9120+8000] [ 38.553701] failing address: TEID: 0800 [ 38.553703] Fault in primary space mode while using user ASCE. [ 38.553706] AS:0001b6d4c1c7 R3:0024 [ 38.553710] CPU: 3 PID: 4218 Comm: in:imtcp Tainted: GE 4.3.0-6-generic #17-Ubuntu [ 38.553711] task: 0001f2e60a78 ti: 0001dafc4000 task.ti: 0001dafc4000 [ 38.553712] User PSW : 070520018000 03ff91202f8e [ 38.553713]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0 EA:3 User GPRS: 03ff897fd1b8 0050 [ 38.553715] 03ff6c003c90 [ 38.553715]0001 [ 38.553716]03ff91c9c000 03ff897fd1b8 03ff91202f78 03ff897fd048 [ 38.553721] User Code: 03ff91202f7c: e54cd001 mvhi 0(%r13),1 03ff91202f82: e310d0080024 stg %r1,8(%r13) #03ff91202f88: e54cd011 mvhi 16(%r13),1 >03ff91202f8e: e31020580004 lg %r1,88(%r2) 03ff91202f94: a729 lghi%r2,0 03ff91202f98: e310d0180024 stg %r1,24(%r13) 03ff91202f9e: e54cd020 mvhi 32(%r13),0 03ff91202fa4: e340f114 lg %r4,272(%r15) [ 38.553730] Last Breaking-Event-Address: [ 38.553731] [<03ff9104bb66>] 0x3ff9104bb66 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1538723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1528673] Re: App doesn't have a qml-project file
*** This bug is a duplicate of bug 1333522 *** https://bugs.launchpad.net/bugs/1333522 You could import project via CMakeLists.txt. The README file should be upgraded to handle this. ** This bug has been marked a duplicate of bug 1333522 add README file -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1528673 Title: App doesn't have a qml-project file Status in messaging-app package in Ubuntu: New Bug description: There is no way to open this up as a project in Qt Creator because there isn't a .qml-project file that can be opened by Qt Creator. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1528673/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1465766] Re: low sound volume
I haven't dual boot ** Attachment added: "my alsa-info" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1465766/+attachment/4557991/+files/alsa-info.txt.0hiyUMfdaO -- 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/1465766 Title: low sound volume Status in alsa-driver package in Ubuntu: Expired Bug description: this is a thinkpad x1 carbon 3rd gen running xubuntu 15.04 sound volume is very low compared to windows (dual boot), even with alsa and pulseaudio controls set to 100% (or greater). this applies to all apps. i can get really loud sound with: pactl set-sink-volume 1 30 but then it is very distorted. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: smwilson 1577 F pulseaudio /dev/snd/controlC0: smwilson 1577 F pulseaudio CurrentDesktop: XFCE Date: Tue Jun 16 06:44:39 2015 InstallationDate: Installed on 2015-06-04 (11 days ago) InstallationMedia: Xubuntu Core 15.04 - amd64 - 20150425 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: Volume slider, or mixer problems Title: [20BSCTO1WW, Realtek ALC3232, Speaker, Internal] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2014 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET25W (1.03 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BSCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET25W(1.03):bd12/01/2014:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BSCTO1WW dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1465766/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1507151] Re: sysv-rc.postinst calls insserv by name, but insserv package does not provide the command in a bin directory
Using the modified test case, a release upgrade from Trusty to Wily would disable -proposed, I was able to verify the fix for this bug and successfully update the sysv-rc package. ** Description changed: Test Case - - Perform a release upgrade from Trusty to Wily + Perform a hokey upgrade from Trusty to Wily - 1) Modify /etc/update-manager/meta-release URI line to be http://www.murraytwins.com/tmp/meta-release (This is only necessary because Vivid is still a supported release.) - 2) Ensure /etc/update-manager/release-upgrades has Prompt=normal - 3) Run do-release-upgrade -p (because only the proposed version of the release upgrader supports this upgrade path) + 1) Modify /etc/apt/sources.list from trusty to wily + 2) Run apt-get update + 3) Try to install the wily version of sysv-rc With the current version of sysvinit the upgrade process will fail with messages like: Setting up sysv-rc (2.88dsf-59.2ubuntu2) ...^M info: Reordering boot system, log to /var/lib/insserv/run-20160122T1444.log^M error: Something failed while migrating.^M ^M error: Unable to migrate to dependency based boot sequencing.^M ^M See http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot for^M more information about dependency based boot sequencing. To^M With the version of the package in -proposed we should see no such error. -- After update ProblemType: PackageDistroRelease: Ubuntu 15.10 Package: sysv-rc 2.88dsf-59.2ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 Date: Wed Oct 14 05:47:58 2015 DuplicateSignature: package:sysv-rc:2.88dsf-59.2ubuntu2:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-10-14 (3 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.2ubuntu4 apt 1.0.10.2ubuntu1SourcePackage: sysvinit Title: package sysv-rc 2.88dsf-59.2ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to wily on 2015-10-14 (3 days ago) ** 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 sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1507151 Title: sysv-rc.postinst calls insserv by name, but insserv package does not provide the command in a bin directory Status in sysvinit package in Ubuntu: Fix Released Status in sysvinit source package in Wily: Fix Committed Bug description: Test Case - Perform a hokey upgrade from Trusty to Wily 1) Modify /etc/apt/sources.list from trusty to wily 2) Run apt-get update 3) Try to install the wily version of sysv-rc With the current version of sysvinit the upgrade process will fail with messages like: Setting up sysv-rc (2.88dsf-59.2ubuntu2) ...^M info: Reordering boot system, log to /var/lib/insserv/run-20160122T1444.log^M error: Something failed while migrating.^M ^M error: Unable to migrate to dependency based boot sequencing.^M ^M See http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot for^M more information about dependency based boot sequencing. To^M With the version of the package in -proposed we should see no such error. -- After update ProblemType: PackageDistroRelease: Ubuntu 15.10 Package: sysv-rc 2.88dsf-59.2ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 Date: Wed Oct 14 05:47:58 2015 DuplicateSignature: package:sysv-rc:2.88dsf-59.2ubuntu2:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-10-14 (3 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.2ubuntu4 apt 1.0.10.2ubuntu1SourcePackage: sysvinit Title: package sysv-rc 2.88dsf-59.2ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to wily on 2015-10-14 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1507151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/Li
[Touch-packages] [Bug 1535349] Re: `df /dev/sda1` no longer reports information for /dev/sda1
It looks like the issue of reporting the uuid device instead of the actual device is a initramfs issue. Basically df will report whatever is in /proc/self/mountinfo, and this appears to be an issue with how fstab is processed. I still have to fully root cause that. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1535349 Title: `df /dev/sda1` no longer reports information for /dev/sda1 Status in coreutils package in Ubuntu: Invalid Status in coreutils source package in Trusty: Confirmed Bug description: [Impact] * df fails to process devices that are specified on the command line. [Test Case] * Actual $ df -h /dev/sda1 Filesystem Size Used Avail Use% Mounted on udev1.8G 8.0K 1.8G 1% /dev * Expected $ df -h /dev/sda1 Filesystem Size Used Avail Use% Mounted on /dev/sda1 9.9G 978M 8.5G 11% / [Regression Potential] * This patch is a partial backport of functions as they exist in vivid to help minimize the regression potential. * That being said I had to do some backporting so as to avoid ui changes. * This once again significantly changes the mount search and matching logic within df, but it is localized to df. [Other Info] * Anything else you think is useful to include * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board * and address these questions in advance Original Description--- It appears that the latest version of coreutils uploaded to trusty-updates has a regression in it. We have scripting that checks how much space we have left on a partition using `df /dev/sda1`. Using coreutils 8.21-1ubuntu5.1, we can do the following: $ df -h /dev/sda1 Filesystem Size Used Avail Use% Mounted on /dev/sda1 9.9G 978M 8.5G 11% / This is a valid way of using the tool per the manpage: "If an argument is the absolute file name of a disk device node containing a mounted file system, df shows the space available on that file system rather than on the file system containing the device node" It appears that either 8.21-1ubuntu5.2 or 8.21-1ubuntu5.3 broke this, however. We now get output for the udev filesystem that is mounted at /dev, instead of the device we pass in. $ df -h /dev/sda1 Filesystem Size Used Avail Use% Mounted on udev1.8G 8.0K 1.8G 1% /dev This is both a behaviour change, and contravenes the manpage, so it would be good to get this fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1535349/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1538774] Re: thumbnailer-admin fails with relative path
** Branch linked: lp:~michihenning/thumbnailer/fix-admin-relative-paths -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to thumbnailer in Ubuntu. https://bugs.launchpad.net/bugs/1538774 Title: thumbnailer-admin fails with relative path Status in thumbnailer package in Ubuntu: In Progress Bug description: $ cd /tmp $ ls xxx.mp3 xxx.mp3 $ thumbnailer-admin get xxx.mp3 thumbnailer-admin: DBusInterface::GetThumbnail(): xxx.mp3: unity::ResourceException: Thumbnailer::get_thumbnail(): boost::filesystem::canonical: No such file or directory: "/xxx.mp3" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thumbnailer/+bug/1538774/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432696] Re: [SDK] Bottom edge header improvement
** Changed in: messaging-app (Ubuntu) Status: Confirmed => Fix Released ** Also affects: messaging-app Importance: Undecided Status: New ** Changed in: messaging-app Status: New => In Progress ** Changed in: messaging-app Assignee: (unassigned) => Bartosz Kosiorek (gang65) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1432696 Title: [SDK] Bottom edge header improvement Status in Dekko: Fix Released Status in messaging-app: In Progress Status in Ubuntu Calendar App: Invalid Status in Ubuntu Clock App: Fix Released Status in Ubuntu Document Viewer App: Fix Released Status in Ubuntu UX: Fix Committed Status in address-book-app package in Ubuntu: Fix Released Status in dialer-app package in Ubuntu: Confirmed Status in messaging-app package in Ubuntu: Fix Released Status in ubuntu-clock-app package in Ubuntu: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: When user does a bottom edge gesture to show a new view (Address Book, Dialer, Clock, etc) the new header should never have a chevron pointing left, as it seems to suggest the wrong direction for the movement. The header of the new View should always have a chevron pointing down. Also, it should allow people using a gesture and dismiss the new screen by dragging or swiping the [chevron & title area of the header] downward UX here: https://www.dropbox.com/s/ypmhej7ie2hrc9a/down_chevron_for_manage_dash_01%28wireframe%29.tiff?dl=0 VD: https://www.dropbox.com/s/1wuihy8tf7no7iw/Music_Down_Chevron.jpg?dl=0 To manage notifications about this bug go to: https://bugs.launchpad.net/dekko/+bug/1432696/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393683] Re: notification indicator shows new messages as being from yesterday
This issue was already solved. ** Changed in: messaging-app (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1393683 Title: notification indicator shows new messages as being from yesterday Status in messaging-app package in Ubuntu: Fix Released Bug description: If I receive SMS messages, they appear in the notification indicator as having happened "yesterday", immediately after being received. I suspect this is an issue with calculating times in UTC instead of local time. I noticed it less than 7 hours before midnight, and I'm in UTC-7, so in UTC it's technically already tomorrow, and my local "today" is technically yesterday. The actual time of day displayed in the indicator is correct, but the day itself is wrong. I noticed this on rtm krillin image 162. It probably isn't an issue in places near UTC, but it definitely shows up in the west hemisphere. I wouldn't be surprised if eastern time zones have the opposite symptom, showing "tomorrow" sometimes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1393683/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1465766] Re: low sound volume
I have also this issue with lenovo x1 charbon -- 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/1465766 Title: low sound volume Status in alsa-driver package in Ubuntu: Expired Bug description: this is a thinkpad x1 carbon 3rd gen running xubuntu 15.04 sound volume is very low compared to windows (dual boot), even with alsa and pulseaudio controls set to 100% (or greater). this applies to all apps. i can get really loud sound with: pactl set-sink-volume 1 30 but then it is very distorted. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: smwilson 1577 F pulseaudio /dev/snd/controlC0: smwilson 1577 F pulseaudio CurrentDesktop: XFCE Date: Tue Jun 16 06:44:39 2015 InstallationDate: Installed on 2015-06-04 (11 days ago) InstallationMedia: Xubuntu Core 15.04 - amd64 - 20150425 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: Volume slider, or mixer problems Title: [20BSCTO1WW, Realtek ALC3232, Speaker, Internal] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2014 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET25W (1.03 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BSCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET25W(1.03):bd12/01/2014:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BSCTO1WW dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1465766/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1197542] Re: System Info module not integrated with platform
another note to self: /etc/machine-info ** Changed in: qtsystems-opensource-src (Ubuntu) Assignee: (unassigned) => Lorn Potter (lorn-potter) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtsystems-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1197542 Title: System Info module not integrated with platform Status in Ubuntu UI Toolkit: Invalid Status in qtsystems-opensource-src package in Ubuntu: Confirmed Bug description: The DeviceInfo item provides correct information for some functions on both desktop and Touch The BatteryInfo items do not yield correct results in any case. Did not try the other interfaces libqt5systeminfo5: Installed: 5.0~git20130123-0ubuntu1~test2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1197542/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1379421] Re: [messaing-app] shouldn't rotate into landscape mode as causes issues with compose and main view
The overlay issue was already fixed in OTA-9. Also rotation is working well ** Changed in: messaging-app (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1379421 Title: [messaing-app] shouldn't rotate into landscape mode as causes issues with compose and main view Status in Ubuntu UX: Fix Committed Status in messaging-app package in Ubuntu: Fix Released Bug description: Build r93 The messaging app rotates to make it easier to type and read messaging threads. However, this causes issues in the compose and main views. If you rotate the app into landscape mode on the landing view, there is no way to carry out a bottom edge swipe to compose a new message. In the compose view, the landscape mode doesn't show the header. This one is needed, to add ppl to the recipient list. Recommendation: The ideal case is that we would have a custom header for landscape views because the current one in portrait mode is too large for certain devices. This needs further investigation from design and probably SDK. Plus there is still the issue of the bottom edge swipe in landscape, which needs to be addressed by Unity. Therefor it would be best to remove this feature for the RTM release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1379421/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1536195] Re: Can't receive calls and sms while the other SIM is using data
** Summary changed: - Can't receive calls and sms while Hotspot is active + Can't receive calls and sms while the other SIM is using data -- 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/1536195 Title: Can't receive calls and sms while the other SIM is using data Status in indicator-network package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Invalid Status in ofono package in Ubuntu: Invalid Bug description: Using 2 Sim Cards Sim 1 for using telephone calls (Provider: Telering (Austria)) Sim 2 for using mobile internet (Provider: 3 AT; this Sim is a Data-Only Sim) While activating Hotspot (using/sharing the internet using Sim 2) I cant receive any calls (number from Sim 1) or SMS. When calling me the caller always get a message from tel-provider: "The customer is currently not accessible...", it seems like the phone switched of. But I can make calls during the phone is in "Hotspot"-mode without problems. Calls and SMS are related to SIM 1 Data is related to Sim 2 (is running in 2G/3G mode) After ending Hotspot I am not reachable at all. I have to reboot (sometimes twice) to be accessible again. -- Using bq Aquarius E4.5 Ubuntu Edition with Ubuntu 15.04 OTA-8.5 20151210 Phone is runing as it was delivered, no developer mode - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1536195/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1356369] Re: [shell] Please disable screen rotation till unity8 supports it as well
** Changed in: messaging-app (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1356369 Title: [shell] Please disable screen rotation till unity8 supports it as well Status in Ubuntu UX: Fix Released Status in messaging-app package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Fix Released Bug description: Screen rotation conflicts with on screen notifications. 1. In landscape mode try to write an SMS 2. Ensure an incoming message while you are typing What happens: Notification appears over keyboard and you end up tapping on the notification losing your written text. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: messaging-app 0.1+14.10.20140806-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.5-0ubuntu4 Architecture: armhf Date: Wed Aug 13 18:21:57 2014 InstallationDate: Installed on 2014-08-13 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140813-020204) SourcePackage: messaging-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1356369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1287709] Re: [Messaging app] shows wrong icon when adding a contact during Compose
In current implementation two icons are shown: One to send SMS and second to Call. ** Changed in: messaging-app (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1287709 Title: [Messaging app] shows wrong icon when adding a contact during Compose Status in Ubuntu UX: Fix Released Status in messaging-app package in Ubuntu: Fix Released Bug description: If I open the messaging app, then swipe up the toolbar and select Compose, I am presented with the compose window (good). If I then click the add Contact icon, then select a contact, a list is displayed that shows the number and "View contact's profile". This is fine, but the list shows a telephone icon rather than a message icon. If I select the telephone icon, the contact is added to the message and all is fine. This isn't a major issue, but can be confusing and is inconsistent with the dialer app's call log, where if you click an item in the call log, a list is displayed that shows a telephone icon with 'Call now' and a message icon with 'Send text message'. I would expect that the message icon always be used when dealing with messages and the telephone icon when dealing with calls. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1287709/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1278790] Re: [Messaging] Show number of characters used and numver of messages
** Summary changed: - [Messaging] Show number of characters used + [Messaging] Show number of characters used and numver of messages ** Summary changed: - [Messaging] Show number of characters used and numver of messages + [Messaging] Show number of characters used and number of messages ** Summary changed: - [Messaging] Show number of characters used and number of messages + [Messaging] Show number of characters used and number of messages to send -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1278790 Title: [Messaging] Show number of characters used and number of messages to send Status in Ubuntu UX: Triaged Status in messaging-app package in Ubuntu: Incomplete Bug description: As many carriers charge per text message sent, it'd be nice to show how many characters were used for the message, so the sender knows how many sent text messages this boils down to. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1278790/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1527106] Re: Fatal exception failure of unattended-upgrade
** 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 unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1527106 Title: Fatal exception failure of unattended-upgrade Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Wily: Fix Committed Bug description: Every morning, since I upgraded to Ubuntu 15.10, I get a mail (root) reporting a fatal exception in unatteded-upgrade containing the following. /etc/cron.daily/apt: Exception: unsupported operand type(s) for %: 'bytes' and 'tuple' Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1435, in main(options) File "/usr/bin/unattended-upgrade", line 1382, in main pkgs, pkg_install_success, pkgs_kept_back, mem_log, log_content) File "/usr/bin/unattended-upgrade", line 815, in send_summary_mail host(), res) TypeError: unsupported operand type(s) for %: 'bytes' and 'tuple' As a consequence no automatic updates are performed anymore, including security updates. For this reason I flag this as a security vulnerability although it is only indirect. Manual updates is still working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1527106/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1474962] Re: Amount of SMS's used to send a message is not shown
*** This bug is a duplicate of bug 1278790 *** https://bugs.launchpad.net/bugs/1278790 ** This bug has been marked a duplicate of bug 1278790 [Messaging] Show number of characters used and number of messages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1474962 Title: Amount of SMS's used to send a message is not shown Status in messaging-app package in Ubuntu: New Bug description: For people who don't have an unlimited amount of SMS's or who pay per SMS, it is useful to know if they are about to send a message that needs more than one SMS, using Concatenated SMS. I would propose to show this information above the Send button, as in the attached mockup. As in the mockup, an info button could be provided. It would open an information screen informing the user that the message has to be sent using multiple SMS's, and that they probably will be charged multiple messages by the provider. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1474962/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1392619] Re: Should show up in 'Communication' department
*** This bug is a duplicate of bug 1379348 *** https://bugs.launchpad.net/bugs/1379348 ** This bug has been marked a duplicate of bug 1379348 App should be in department Communications -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1392619 Title: Should show up in 'Communication' department Status in messaging-app package in Ubuntu: Confirmed Bug description: I think messaging (and dialer) app's should show up in 'Communication' department, rather than utilities. They're not utilities, like things like Calculator, Clock or System Settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1392619/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1290031] Re: Support japanese language
Sorry, that's largely down to me; I've been a bit busy with other projects recently so keyboard stuff has slipped a bit; there's just one last fixed required in this branch which I'll implement next week and then we can get this landed ready for OTA-10. -- 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/1290031 Title: Support japanese language Status in ubuntu-keyboard: Confirmed Status in ubuntu-keyboard package in Ubuntu: In Progress Bug description: Please support to input japanese language from ubuntu-keyboard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-keyboard/+bug/1290031/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1538705] Re: convert scripts to python3
$ bzr commit -m "Remove unused tools bugs_against_version and fetch_failed_core_dumps they are likely left over from the whoopsie-daisy days." --fixes lp:1538075 Committing to: /home/bdmurray/source-trees/whoopsie/trunk/ deleted tools/bugs_against_version.py deleted tools/fetch_failed_core_dumps.py Committed revision 673. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1538705 Title: convert scripts to python3 Status in Whoopsie: Fix Released Status in whoopsie package in Ubuntu: Invalid Bug description: now that launchpadlib is available for Python3, the scripts can be converted to python3 To manage notifications about this bug go to: https://bugs.launchpad.net/whoopsie/+bug/1538705/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1524901] Re: When an application starts there is temporarily a white gap at the top
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) => Tim Peeters (tpeeters) -- 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/1524901 Title: When an application starts there is temporarily a white gap at the top Status in Canonical System Image: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: When an application starts there is temporarily a white gap at the top, note I think this has started happening on the rc-proposed channel since around when OTA8 was released. This is seen with apps using v1.3 of the uitk The symptom varies depending on the app, some jump up (contacts) some jump down (messaging) as they initially display. What happened: 1) Launch an application such as Music, dekko, messaging app 2) As it is launched watch the very top 3) Notice that for a few frames there is a white box that pushes all of the content down (most visible on music due to black app colour) What was expected to happen: At step 3 for there to be no white box at the top of the app on startup $ system-image-cli -i current build number: 184 device name: mako channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-12-10 15:02:28 version version: 184 version ubuntu: 20151210.1 version device: 20150911 version custom: mako-1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1524901/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1417759] Re: allready written message lost after restart
*** This bug is a duplicate of bug 1229950 *** https://bugs.launchpad.net/bugs/1229950 ** This bug has been marked a duplicate of bug 1229950 [messaging-app]"draft" messages aren't saved -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1417759 Title: allready written message lost after restart Status in messaging-app package in Ubuntu: Confirmed Bug description: writte a message without sending it restart phone and message is lost Ubuntu development branch Build 186 (20150203-030204) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1417759/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1501300] Re: [SRU] Wily (15.10) this package got not compiled with __cxx11 support
Yes, now clang is built on top of gcc-5 ** 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 llvm-toolchain-3.4 in Ubuntu. https://bugs.launchpad.net/bugs/1501300 Title: [SRU] Wily (15.10) this package got not compiled with __cxx11 support Status in llvm-toolchain-3.4 package in Ubuntu: Invalid Status in llvm-toolchain-3.4 source package in Wily: Fix Committed Bug description: [Impact] * with gcc-5 default, and llvm-3.4 built with the gcc-4.9, people can't link programs using cxx11 support [Test Case] * compile a program using cxx11 e.g. using boost libraries [Regression Potential] * llvm-3.4 is a compiler, and the change should affect only cxx11 support (since the library is ABI compatible). So, fixing cxx11 support shouln't have any regression, only the feature will start working, while it wasn't before [Other Info] * Doko ack'd the SRU, and it should be the best voice here, for sure better than mine :) This packages does not contain any __cxx11 symbols when installed. This causes the problem that user-space applications cannot link successfully to it. Recompile the (untouched) dpkg source package on the same machine and installing it solved the problem. There seems something in the package generation broken. Steps to reproduce try to compile the attached minimal example https://github.com/goldhoorn/clang-sandbox Errors: CMakeFiles/main.dir/main.cpp.o: In function `foo()': /tmp/clang-sandbox/main.cpp:25: undefined reference to `clang::NamedDecl::getQualifiedNameAsString[abi:cxx11]() const' CMakeFiles/main.dir/main.cpp.o: In function `clang::QualType::getAsString[abi:cxx11](clang::SplitQualType)': /usr/lib/llvm-3.4/include/clang/AST/Type.h:868: undefined reference to `clang::QualType::getAsString[abi:cxx11](clang::Type const*, clang::Qualifiers)' CMakeFiles/main.dir/main.cpp.o: In function `clang::ast_matchers::internal::matcher_matchesName0Matcher::matches(clang::NamedDecl const&, clang::ast_matchers::internal::ASTMatchFinder*, clang::ast_matchers::internal::BoundNodesTreeBuilder*) const': /usr/lib/llvm-3.4/include/clang/ASTMatchers/ASTMatchers.h:1439: undefined reference to `clang::NamedDecl::getQualifiedNameAsString[abi:cxx11]() const' CMakeFiles/main.dir/main.cpp.o: In function `clang::ast_matchers::internal::matcher_hasName0Matcher::matches(clang::NamedDecl const&, clang::ast_matchers::internal::ASTMatchFinder*, clang::ast_matchers::internal::BoundNodesTreeBuilder*) const': /usr/lib/llvm-3.4/include/clang/ASTMatchers/ASTMatchers.h:1411: undefined reference to `clang::NamedDecl::getQualifiedNameAsString[abi:cxx11]() const' /usr/lib/llvm-3.4/lib/libclangAST.a(ExprConstant.o): In function `handleIntIntBinOp((anonymous namespace)::EvalInfo&, clang::Expr const*, llvm::APSInt const&, clang::BinaryOperatorKind, llvm::APSInt, llvm::APSInt&)': (.text+0x6a35): undefined reference to `llvm::APInt::toString(unsigned int, bool) const' /usr/lib/llvm-3.4/lib/libclangAST.a(StmtPrinter.o): In function `(anonymous namespace)::StmtPrinter::VisitIntegerLiteral(clang::IntegerLiteral*) [clone .isra.302]': ... This example is workign on privious ubuntus and debians Sysinfo: Description: Ubuntu Wily Werewolf (development branch) Release: 15.10 In a VirtualBox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.4/+bug/1501300/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1538705] Re: convert scripts to python3
** Also affects: whoopsie Importance: Undecided Status: New ** Changed in: whoopsie Status: New => Fix Released ** Changed in: whoopsie Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: whoopsie Importance: Undecided => Low ** Changed in: whoopsie (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1538705 Title: convert scripts to python3 Status in Whoopsie: Fix Released Status in whoopsie package in Ubuntu: Invalid Bug description: now that launchpadlib is available for Python3, the scripts can be converted to python3 To manage notifications about this bug go to: https://bugs.launchpad.net/whoopsie/+bug/1538705/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1533993] Re: Cannot in-line playback the online tracks from main view of music scope
I understand that the card type used in the soundcloud scope does not support inline playback just yet, so we should either add that to the card (in unity8), or we should make the scope use the right card type. I'm adding pawel for further comments. ** Changed in: unity-scopes-shell (Ubuntu) Assignee: (unassigned) => Pawel Stolowski (stolowski) ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Also affects: unity-scope-soundcloud Importance: Undecided Status: New -- 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/1533993 Title: Cannot in-line playback the online tracks from main view of music scope Status in Canonical System Image: Confirmed Status in Unity SoundCloud Scope: New Status in unity-scopes-shell package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: New Bug description: Test Environment: $ system-image-cli -i current build number: 228 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-01-13 07:38:39 version version: 228 version ubuntu: 20160113 version device: 20160108-efc96d8 version custom: 2015--36-46-vivid Steps: 1.Go to Music Scope 2.Select a local track from My Music section and tap on the thumbnail to play =>Be able to playback the track on main view 3.Scroll down a little bit to SoundCloud section 4.Select an on-line track from SoundCloud section and try to in-line play it on main view Actual result: Cannot in-line playback the on-line tracks from main view Expected result: According to UX spec of Media consumption for Scopes(https://docs.google.com/document/d/18jRyUvJ29ykAKgQ9zk7q6FJEvz51mMFBT8_TFUUclDY/edit), on-line tracks can be in-line played as well To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1533993/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1518940] Re: libllvm mistakenly compiled with gcc 4.9
Fix ongoing ** Changed in: llvm-toolchain-3.4 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to llvm-toolchain-3.4 in Ubuntu. https://bugs.launchpad.net/bugs/1518940 Title: libllvm mistakenly compiled with gcc 4.9 Status in llvm-toolchain-3.4 package in Ubuntu: Fix Released Bug description: Hi guys, we're utilising libllvm3.4 to build Blender and prerequisites and noticed after an update to 15.10 that we're suddenly not able to link our OSL libs after building any more. After a long and tedious error analysis we think that we found the issue - an ABI incompatibility caused by libllvm depending on gcc 4.9 - and not on gcc 5.2 like on newest debian. Could you have a look at this? If you need direct help (maybe to have a remote access to a 15.10 ubuntu) to investigate the issue just come to #blendercoders and ask me (plasmasolutions) there. Many greetings, Thomas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.4/+bug/1518940/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1538705] Re: convert scripts to python3
I didn't realize that these scripts were in the whoopsie code and I've never actually used them, additionally nothing calls them and they aren't part of the package so we might as well remove them. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1538705 Title: convert scripts to python3 Status in whoopsie package in Ubuntu: New Bug description: now that launchpadlib is available for Python3, the scripts can be converted to python3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1538705/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1536843] Re: vlc refuses to compile against qtbase-opensource-src
** Bug watch added: VLC Trac #16497 http://trac.videolan.org/vlc/ticket/16497 ** Also affects: vlc via http://trac.videolan.org/vlc/ticket/16497 Importance: Unknown Status: Unknown -- 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/1536843 Title: vlc refuses to compile against qtbase-opensource-src Status in VLC media player: Unknown Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in vlc package in Ubuntu: New Bug description: The daily builds of vlc 2.2.x refuse to compile against qtbase- opensource-src on xenial: configure: error: "You cannot build VLC with Qt-5.5.0. You need to backport I78ef29975181ee22429c9bd4b11d96d9e68b7a9c" Build recipe: https://code.launchpad.net/~videolan/+recipe/stable-daily.xenial Full log: https://launchpad.net/~videolan/+archive/ubuntu/stable-daily/+build/8859183 Please backport that commit to xenial. To manage notifications about this bug go to: https://bugs.launchpad.net/vlc/+bug/1536843/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1532500] Re: [Samsung NP940Z5L-X01US] Trackpad doesn't work after login
I confirm that this recipe fixes the problem. Thank you very much! -- 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/1532500 Title: [Samsung NP940Z5L-X01US] Trackpad doesn't work after login Status in xorg package in Ubuntu: Triaged Bug description: On a Samsung Ativ Book 9 Pro laptop, Ubuntu 15.10 Prior to login, the trackpad moves the cursor. After login, the trackpad does not move the cursor. The touchscreen works as expected for clicking and region-selecting. I expected the trackpad and the touchscreen to work simultaneously. An external USB mouse works normally before and after login. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Jan 9 18:41:06 2016 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c12b] Subsystem: Samsung Electronics Co Ltd Device [144d:c12b] InstallationDate: Installed on 2015-12-22 (18 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: SAMSUNG ELECTRONICS CO., LTD. 940Z5L ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-23-generic.efi.signed root=UUID=24c27814-5135-4a80-9ce1-b932e2513949 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P04AFC.084.151020.SH dmi.board.asset.tag: No Asset Tag dmi.board.name: NP940Z5L-X01US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL8554A1H-C01-G001-S0001+10.0.10240 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP04AFC.084.151020.SH:bd10/20/2015:svnSAMSUNGELECTRONICSCO.,LTD.:pn940Z5L:pvrP04AFC:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP940Z5L-X01US:rvrSGL8554A1H-C01-G001-S0001+10.0.10240:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 940Z5L dmi.product.version: P04AFC dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Jan 9 18:08:08 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16714 vendor SDC xserver.version: 2:1.17.2-1ubuntu9.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1532500/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1536843] Re: vlc refuses to compile against qtbase-opensource-src
configure.ac does only a version check: PKG_CHECK_EXISTS([Qt5Core >= 5.5.0 Qt5Core < 5.6.0], [ AC_MSG_ERROR(["You cannot build VLC with Qt-5.5.0. You need to backport I78ef29975181ee22429c9bd4b11d96d9e68b7a9c"]) ]) -- 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/1536843 Title: vlc refuses to compile against qtbase-opensource-src Status in VLC media player: Unknown Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in vlc package in Ubuntu: New Bug description: The daily builds of vlc 2.2.x refuse to compile against qtbase- opensource-src on xenial: configure: error: "You cannot build VLC with Qt-5.5.0. You need to backport I78ef29975181ee22429c9bd4b11d96d9e68b7a9c" Build recipe: https://code.launchpad.net/~videolan/+recipe/stable-daily.xenial Full log: https://launchpad.net/~videolan/+archive/ubuntu/stable-daily/+build/8859183 Please backport that commit to xenial. To manage notifications about this bug go to: https://bugs.launchpad.net/vlc/+bug/1536843/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1401322] Re: Upgrade to Python 2.7.9
For the people annoyed at the idea to move to 16.04: There are some alternative ways to get an updated Python version, without relying on the one shipped by default in Ubuntu: Pythonz: https://github.com/saghul/pythonz (disclaimer: I submitted some patches and integrated pythonz into my own project: https://github.com/berdario/pew ) Pyenv: https://github.com/yyuu/pyenv The deadsnakes ppa: https://launchpad.net/~fkrull/+archive/ubuntu/deadsnakes-python2.7?field.series_filter=precise (this is not the main PPA, but it's the one created specially for this purpose) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1401322 Title: Upgrade to Python 2.7.9 Status in python-defaults package in Ubuntu: Fix Released Bug description: Python 2.7.9 contains numerous security improvements for Python. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1401322/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1536843] Re: vlc refuses to compile against qtbase-opensource-src
FTR, qtbase-opensource-src 5.5.1+dfsg-10ubuntu2 ships set_WA_OutsideWSRange_for_native_widgets.patch I'll open an upstream bug for it. -- 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/1536843 Title: vlc refuses to compile against qtbase-opensource-src Status in VLC media player: Unknown Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in vlc package in Ubuntu: New Bug description: The daily builds of vlc 2.2.x refuse to compile against qtbase- opensource-src on xenial: configure: error: "You cannot build VLC with Qt-5.5.0. You need to backport I78ef29975181ee22429c9bd4b11d96d9e68b7a9c" Build recipe: https://code.launchpad.net/~videolan/+recipe/stable-daily.xenial Full log: https://launchpad.net/~videolan/+archive/ubuntu/stable-daily/+build/8859183 Please backport that commit to xenial. To manage notifications about this bug go to: https://bugs.launchpad.net/vlc/+bug/1536843/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1538774] [NEW] thumbnailer-admin fails with relative path
Public bug reported: $ cd /tmp $ ls xxx.mp3 xxx.mp3 $ thumbnailer-admin get xxx.mp3 thumbnailer-admin: DBusInterface::GetThumbnail(): xxx.mp3: unity::ResourceException: Thumbnailer::get_thumbnail(): boost::filesystem::canonical: No such file or directory: "/xxx.mp3" ** Affects: thumbnailer (Ubuntu) Importance: Medium Assignee: Michi Henning (michihenning) Status: In Progress ** Changed in: thumbnailer (Ubuntu) Assignee: (unassigned) => Michi Henning (michihenning) ** Changed in: thumbnailer (Ubuntu) Status: New => In Progress ** Changed in: thumbnailer (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to thumbnailer in Ubuntu. https://bugs.launchpad.net/bugs/1538774 Title: thumbnailer-admin fails with relative path Status in thumbnailer package in Ubuntu: In Progress Bug description: $ cd /tmp $ ls xxx.mp3 xxx.mp3 $ thumbnailer-admin get xxx.mp3 thumbnailer-admin: DBusInterface::GetThumbnail(): xxx.mp3: unity::ResourceException: Thumbnailer::get_thumbnail(): boost::filesystem::canonical: No such file or directory: "/xxx.mp3" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thumbnailer/+bug/1538774/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1535349] Re: `df /dev/sda1` no longer reports information for /dev/sda1
I have been doing some more testing with this, and would appreciate some more eyes on this before upload. I have created a ppa with test packages here. https://launchpad.net/~chiluk/+archive/ubuntu/df Thanks ahead of time to anyone who can test the PPA. I've already noticed that on one of my machines I got this unexpected behavior. Although better this is not expected. chiluk@bonus:/tmp$ df -h /dev/sda2 Filesystem Size Used Avail Use% Mounted on /dev/disk/by-uuid/dc918cc3-dc63-4049-bce1-96fec88f77d1 30G 26G 2.0G 93% / ** Patch removed: "lp1535349.trusty.debdiff" https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1535349/+attachment/4557958/+files/lp1535349.trusty.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1535349 Title: `df /dev/sda1` no longer reports information for /dev/sda1 Status in coreutils package in Ubuntu: Invalid Status in coreutils source package in Trusty: Confirmed Bug description: [Impact] * df fails to process devices that are specified on the command line. [Test Case] * Actual $ df -h /dev/sda1 Filesystem Size Used Avail Use% Mounted on udev1.8G 8.0K 1.8G 1% /dev * Expected $ df -h /dev/sda1 Filesystem Size Used Avail Use% Mounted on /dev/sda1 9.9G 978M 8.5G 11% / [Regression Potential] * This patch is a partial backport of functions as they exist in vivid to help minimize the regression potential. * That being said I had to do some backporting so as to avoid ui changes. * This once again significantly changes the mount search and matching logic within df, but it is localized to df. [Other Info] * Anything else you think is useful to include * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board * and address these questions in advance Original Description--- It appears that the latest version of coreutils uploaded to trusty-updates has a regression in it. We have scripting that checks how much space we have left on a partition using `df /dev/sda1`. Using coreutils 8.21-1ubuntu5.1, we can do the following: $ df -h /dev/sda1 Filesystem Size Used Avail Use% Mounted on /dev/sda1 9.9G 978M 8.5G 11% / This is a valid way of using the tool per the manpage: "If an argument is the absolute file name of a disk device node containing a mounted file system, df shows the space available on that file system rather than on the file system containing the device node" It appears that either 8.21-1ubuntu5.2 or 8.21-1ubuntu5.3 broke this, however. We now get output for the udev filesystem that is mounted at /dev, instead of the device we pass in. $ df -h /dev/sda1 Filesystem Size Used Avail Use% Mounted on udev1.8G 8.0K 1.8G 1% /dev This is both a behaviour change, and contravenes the manpage, so it would be good to get this fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1535349/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1538772] [NEW] Stop build-depending on libfarstream-0.1-dev
Public bug reported: This is the old gst0.10 farstream, you don't want this anymore. This is keeping the following source packages unnessarily in main (and maybe existing): gstreamer0.10-nice libfarstream-0.1-0 Bug in xenial. ** Affects: telepathy-qt5 (Ubuntu) Importance: Undecided Status: New ** Tags: gst0.10 ** Tags added: gst0.10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-qt5 in Ubuntu. https://bugs.launchpad.net/bugs/1538772 Title: Stop build-depending on libfarstream-0.1-dev Status in telepathy-qt5 package in Ubuntu: New Bug description: This is the old gst0.10 farstream, you don't want this anymore. This is keeping the following source packages unnessarily in main (and maybe existing): gstreamer0.10-nice libfarstream-0.1-0 Bug in xenial. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-qt5/+bug/1538772/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1532500] Re: [Samsung NP940Z5L-X01US] Trackpad doesn't work after login
I noticed that the trackpad is working after installing http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-wily/linux- image-4.4.0-040400-generic_4.4.0-040400.201601101930_amd64.deb and linux-firmware 1.55 from http://packages.ubuntu.com/xenial/all/linux- firmware/download -- 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/1532500 Title: [Samsung NP940Z5L-X01US] Trackpad doesn't work after login Status in xorg package in Ubuntu: Triaged Bug description: On a Samsung Ativ Book 9 Pro laptop, Ubuntu 15.10 Prior to login, the trackpad moves the cursor. After login, the trackpad does not move the cursor. The touchscreen works as expected for clicking and region-selecting. I expected the trackpad and the touchscreen to work simultaneously. An external USB mouse works normally before and after login. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Jan 9 18:41:06 2016 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c12b] Subsystem: Samsung Electronics Co Ltd Device [144d:c12b] InstallationDate: Installed on 2015-12-22 (18 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: SAMSUNG ELECTRONICS CO., LTD. 940Z5L ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-23-generic.efi.signed root=UUID=24c27814-5135-4a80-9ce1-b932e2513949 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P04AFC.084.151020.SH dmi.board.asset.tag: No Asset Tag dmi.board.name: NP940Z5L-X01US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL8554A1H-C01-G001-S0001+10.0.10240 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP04AFC.084.151020.SH:bd10/20/2015:svnSAMSUNGELECTRONICSCO.,LTD.:pn940Z5L:pvrP04AFC:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP940Z5L-X01US:rvrSGL8554A1H-C01-G001-S0001+10.0.10240:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 940Z5L dmi.product.version: P04AFC dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Jan 9 18:08:08 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16714 vendor SDC xserver.version: 2:1.17.2-1ubuntu9.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1532500/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1538591] Re: Add a control to toggle between windowed and staged modes
** Changed in: canonical-pocket-desktop Assignee: (unassigned) => kevin gunn (kgunn72) -- 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/1538591 Title: Add a control to toggle between windowed and staged modes Status in Canonical System Image: Confirmed Status in canonical-pocket-desktop: In Progress Status in Ubuntu UX: New Status in unity8 package in Ubuntu: Confirmed Bug description: A new toggle will be added to the rotation (to be display) indicator to allow the user to switch between windowed (for desktop) and staged (for phone and tablet) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1538591/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1517597] Re: [regression] mouse pointer support on emulator is broken
It's not off our radar i promise -- 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/1517597 Title: [regression] mouse pointer support on emulator is broken Status in Client Developer Experience: New Status in Canonical System Image: Confirmed Status in Mir: Invalid Status in Mir 0.18 series: Invalid Status in android package in Ubuntu: Confirmed Status in mir package in Ubuntu: Invalid Bug description: STEPS: 1. Flash with sudo ubuntu-emulator create --channel ubuntu-touch/rc/ubuntu rc-test 2. Wait for it to build 3. Run with ubuntu-emulator run rc-test 4. Starts up but the mouse never moves meaning you can't leave the first page of the welcome wizard EXPECTED: I expect the emulator cursor to follow the mouse cursor and be able to click on things ACTUAL: Emulator cursors stay in the top left preventing movement. As noted below F6 toggles the input mode. The pointer movement is quite slow and jerky. You also can no longer initiate an edge swipe even in trackball mode. This is a major regression from how the emulator used to perform. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-developer-experience/+bug/1517597/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1538760] [NEW] battery icon gone
Public bug reported: Usually the power/battery indicator works as expected. However, now I turned on my laptop while not connected to AC power, and there is no battery icon at all. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: indicator-power 12.10.6+15.10.20151005.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6 Uname: Linux 4.2.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jan 27 22:10:15 2016 InstallationDate: Installed on 2013-10-11 (838 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: indicator-power UpgradeStatus: Upgraded to wily on 2016-01-18 (9 days ago) ** Affects: indicator-power (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1538760 Title: battery icon gone Status in indicator-power package in Ubuntu: New Bug description: Usually the power/battery indicator works as expected. However, now I turned on my laptop while not connected to AC power, and there is no battery icon at all. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: indicator-power 12.10.6+15.10.20151005.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6 Uname: Linux 4.2.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jan 27 22:10:15 2016 InstallationDate: Installed on 2013-10-11 (838 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: indicator-power UpgradeStatus: Upgraded to wily on 2016-01-18 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1538760/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1290031] Re: Support japanese language
Hi,I just updated my mobile to the latest Ubuntu build (20160123-115651) and the problem still exists. The problem is that I can show Japanese characters, but I can't enter them.On my Ubuntu based laptop I can enter Japanese characters, so I hope to do the same on my mobile.よろしくお願いします。 Thank you for your support!Best regards,Peter From: tmtvl To: peterleifrasmus...@yahoo.com Sent: Wednesday, January 27, 2016 9:13 PM Subject: [Bug 1290031] Re: Support japanese language Okay, it's been a while since the last activity, what's going on? If you could outline what still needs fixing, I'll take a look at it. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1290031 Title: Support japanese language Status in ubuntu-keyboard: Confirmed Status in ubuntu-keyboard package in Ubuntu: In Progress Bug description: Please support to input japanese language from ubuntu-keyboard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-keyboard/+bug/1290031/+subscriptions -- 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/1290031 Title: Support japanese language Status in ubuntu-keyboard: Confirmed Status in ubuntu-keyboard package in Ubuntu: In Progress Bug description: Please support to input japanese language from ubuntu-keyboard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-keyboard/+bug/1290031/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1538755] Re: /usr/lib/arm-linux-gnueabihf/thumbnailer/thumbnailer-service:11:QMap:QNetworkManagerInterfaceDeviceWired::carrier:QNetworkManagerEngine::parseConnection:QNetworkMana
This doesn't look like a thumbnailer problem per se. Seems like it just exposed an issue in Qt networking code. ** Also affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New ** Changed in: thumbnailer (Ubuntu) Status: New => Triaged -- 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/1538755 Title: /usr/lib/arm-linux-gnueabihf/thumbnailer/thumbnailer- service:11:QMap:QNetworkManagerInterfaceDeviceWired::carrier:QNetworkManagerEngine::parseConnection:QNetworkManagerEngine::newConnection:QNetworkManagerEngine::setupConfigurations Status in qtbase-opensource-src package in Ubuntu: New Status in thumbnailer package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding thumbnailer. This problem was most recently seen with version 2.3+15.04.20151102.2-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/4d8506d5cef09939bd7de656ced14576d34f1e9a contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1538755/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1538755] [NEW] /usr/lib/arm-linux-gnueabihf/thumbnailer/thumbnailer-service:11:QMap:QNetworkManagerInterfaceDeviceWired::carrier:QNetworkManagerEngine::parseConnection:QNetworkMa
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding thumbnailer. This problem was most recently seen with version 2.3+15.04.20151102.2-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/4d8506d5cef09939bd7de656ced14576d34f1e9a contains more details. ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New ** Affects: thumbnailer (Ubuntu) Importance: Undecided Status: Triaged ** Tags: vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to thumbnailer in Ubuntu. https://bugs.launchpad.net/bugs/1538755 Title: /usr/lib/arm-linux-gnueabihf/thumbnailer/thumbnailer- service:11:QMap:QNetworkManagerInterfaceDeviceWired::carrier:QNetworkManagerEngine::parseConnection:QNetworkManagerEngine::newConnection:QNetworkManagerEngine::setupConfigurations Status in qtbase-opensource-src package in Ubuntu: New Status in thumbnailer package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding thumbnailer. This problem was most recently seen with version 2.3+15.04.20151102.2-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/4d8506d5cef09939bd7de656ced14576d34f1e9a contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1538755/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1494514] Re: When the screen timeout is set to one minute, the screen doesn't dim before going off
** No longer affects: ubuntu-system-settings (Ubuntu) ** No longer affects: unity8 (Ubuntu) ** Changed in: unity-system-compositor Importance: Undecided => High ** Changed in: unity-system-compositor Assignee: (unassigned) => Alexandros Frantzis (afrantzis) ** Changed in: unity-system-compositor (Ubuntu) Assignee: (unassigned) => Alexandros Frantzis (afrantzis) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1494514 Title: When the screen timeout is set to one minute, the screen doesn't dim before going off Status in Canonical System Image: Confirmed Status in Ubuntu UX: Triaged Status in Unity System Compositor: New Status in unity-system-compositor package in Ubuntu: Confirmed Bug description: When set to two mins or more, the screen dims for 10 secs then goes off. (I also thought the intended time on dim was 15 secs or more not 10, its a bit too quick to react to) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1494514/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1538635] Re: Dependency typo
lightdm-greeter is actually a provides field for a greeter - so all three greeters provide one. We should probably just correct this field to: Recommends: lightdm-greeter -- 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/1538635 Title: Dependency typo Status in lightdm package in Ubuntu: New Bug description: Lightdm package recommends: unity-greeter | lightdm-greeter | lightdm- kde-greeter but lightdm-gtk-greeter is the real package-name So this needs to be corrected to : unity-greeter | lightdm-gtk-greeter | lightdm-kde-greeter note: actually the default 'unity-greeter' is used, but i get logged: (unity-settings-daemon:1570): WARNING **: Unable to register client: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method 'RegisterClient' Seems existing since a while: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1334079 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.17.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-1.15-generic 4.4.0 Uname: Linux 4.4.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.4-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jan 27 17:06:52 2016 SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1538635/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1535349] Re: `df /dev/sda1` no longer reports information for /dev/sda1
** Description changed: - It appears that the latest version of coreutils uploaded to trusty- - updates has a regression in it. We have scripting that checks how much - space we have left on a partition using `df /dev/sda1`. Using coreutils - 8.21-1ubuntu5.1, we can do the following: + [Impact] + + * df fails to process devices that are specified on the command line. + + [Test Case] + + * Actual + $ df -h /dev/sda1 + Filesystem Size Used Avail Use% Mounted on + udev1.8G 8.0K 1.8G 1% /dev + + * Expected + $ df -h /dev/sda1 + Filesystem Size Used Avail Use% Mounted on + /dev/sda1 9.9G 978M 8.5G 11% / + + [Regression Potential] + + * This patch is a partial backport of functions as they exist in vivid + to help minimize the regression potential. + + * That being said I had to do some backporting so as to avoid ui changes. + + * This once again significantly changes the mount search and matching +logic within df, but it is localized to df. + + [Other Info] + + * Anything else you think is useful to include + * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board + * and address these questions in advance + + + Original Description--- + It appears that the latest version of coreutils uploaded to trusty-updates has a regression in it. We have scripting that checks how much space we have left on a partition using `df /dev/sda1`. Using coreutils 8.21-1ubuntu5.1, we can do the following: $ df -h /dev/sda1 Filesystem Size Used Avail Use% Mounted on /dev/sda1 9.9G 978M 8.5G 11% / This is a valid way of using the tool per the manpage: "If an argument is the absolute file name of a disk device node containing a mounted file system, df shows the space available on that file system rather than on the file system containing the device node" It appears that either 8.21-1ubuntu5.2 or 8.21-1ubuntu5.3 broke this, however. We now get output for the udev filesystem that is mounted at /dev, instead of the device we pass in. - $ df -h /dev/sda1 + $ df -h /dev/sda1 Filesystem Size Used Avail Use% Mounted on udev1.8G 8.0K 1.8G 1% /dev This is both a behaviour change, and contravenes the manpage, so it would be good to get this fixed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1535349 Title: `df /dev/sda1` no longer reports information for /dev/sda1 Status in coreutils package in Ubuntu: Invalid Status in coreutils source package in Trusty: Confirmed Bug description: [Impact] * df fails to process devices that are specified on the command line. [Test Case] * Actual $ df -h /dev/sda1 Filesystem Size Used Avail Use% Mounted on udev1.8G 8.0K 1.8G 1% /dev * Expected $ df -h /dev/sda1 Filesystem Size Used Avail Use% Mounted on /dev/sda1 9.9G 978M 8.5G 11% / [Regression Potential] * This patch is a partial backport of functions as they exist in vivid to help minimize the regression potential. * That being said I had to do some backporting so as to avoid ui changes. * This once again significantly changes the mount search and matching logic within df, but it is localized to df. [Other Info] * Anything else you think is useful to include * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board * and address these questions in advance Original Description--- It appears that the latest version of coreutils uploaded to trusty-updates has a regression in it. We have scripting that checks how much space we have left on a partition using `df /dev/sda1`. Using coreutils 8.21-1ubuntu5.1, we can do the following: $ df -h /dev/sda1 Filesystem Size Used Avail Use% Mounted on /dev/sda1 9.9G 978M 8.5G 11% / This is a valid way of using the tool per the manpage: "If an argument is the absolute file name of a disk device node containing a mounted file system, df shows the space available on that file system rather than on the file system containing the device node" It appears that either 8.21-1ubuntu5.2 or 8.21-1ubuntu5.3 broke this, however. We now get output for the udev filesystem that is mounted at /dev, instead of the device we pass in. $ df -h /dev/sda1 Filesystem Size Used Avail Use% Mounted on udev1.8G 8.0K 1.8G 1% /dev This is both a behaviour change, and contravenes the manpage, so it would be good to get this fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1535349/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1446865]
Yes indeed, it doesn't work because ignoring close events cancels logout. Damn. -- 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/1446865 Title: KDE5/Qt5 does not support session restoration Status in KDE Base Workspace: Confirmed Status in Qt: New Status in plasma-workspace package in Ubuntu: Confirmed Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: KDE5/Qt5 does not support proper session restoration. ProblemType: Bug DistroRelease: Ubuntu 15.10 To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1446865]
(In reply to Thomas Lübking from comment #24) > (In reply to Alexey Chernov from comment #23) > > > Comments like this clearly don't help > Seriously, you asked for breaking clients because that's what you'd "like" > to do - what did you expect to hear? That's simply not an acceptable stance. No one here presents any absolutely true point, otherwise there were no discussion. I just wrote my point of view and emphasized that it's just mine and not some ultimate truth. > > Never mentioned minor update or particular version. Please don't distort. > So you meant to schedule this for Qt6? No. I just stated that I didn't mention any particular version, no other implications. As to your question, I'd prefer properly test the patch, including success scenario for the default not-aware-of-session- management application, and release it as soon as possible. > > Users were already hit when the significant part of functionality important > > for someone's every day use case is broken. > Let's be honest: session restorage is apparently relevant for only a > minority of users. According to what? Your assumption? It's not too evident for me, sorry. > Loosing your data is however relevant for everyone. And the latter is the by > far more severe issue. Restarting applications is merely an annoyance, > loosing your work is truely expensive. Hey, how could session management be "apparently relevant for only a minority of users", but fixes in its behaviour be crucial for a lot of them? Don't you contradict with yourself in these two points? Anyway, it's very subjective and I wouldn't argue on what's more important. I agree that data loss is the worst thing which could happen. I just think it doesn't mean it should result in some messy API or library code when someone's relying on the undocumented side-effects. Just because it will surely lead to more bugs and more data loss in the future. It's just the bugs which should be fixed either in library and its clients. It's better to fix them when no one really relies on the stability too much. It looks like this time is now for KF5-based application and environment. > Also there's absolutely NO reason why we should not care about both - except > that you'd "like" to break client code and risk data loss for some reason > that completely escapes me. No, that's just postponing and messing up the whole problem. If, as you stated, almost no one implemented easy and pretty simple interaction appeared in Qt5, even less would care of possible bugs and corner cases of the workaround, more complex protocol with close event you propose. There would be just another argument that it's just too messy, not to mention already existing argument that no one uses session management. > > Still better than a couple of API methods like "enableSpecifiedBehaviour()" > > I fully agree on that proposal to be of little help - it will be mostly > ignored or used w/o accounting the implications. Ok. > > Once again: we all could already apply the fix of Andreas and be busy fixing > > the necessary applications rather than keep discussing here. > > It does NOT only affect KDE applications, there're hundreds of Qt > applications which might have adopted this pattern - or simply don't care > about session management itfp. > Also the proper order is to fix and roll out clients, *then* remove the > deprecated upstream code. That's why "=> Qt6" for this approach. Fully agree here, but we should confirm that nobody said in the beggining that upstream changes were about to break session management for KF5 applications. It was just broken. Since we have what we have, there's no other way than to start fixing it on both sides. I think nobody is against if it would be synchronized. > > On the Qt6 release you would say that everyone already rely on the > > workaround there was in Qt5 etc. etc. > > No. Because you would tell people during Qt5 don't do this and don't rely on > it because it's not gonna work with Qt6, so that when things are ported to > Qt6, client code has to be fixed. Oh, you're too optimistic here. Why it's still not fixed during porting on Qt5? Only because it just works. It won't be fixed until it's broken or would be planned to fix as we discussed above. > Breaking it now and depending client behavior on whether it's linked against > Qt 5.6 or Qt 5.7 is plain wrong and begging for trouble. That's again due to your assumption that session management is of lower priority. I'm pretty sure there would be packages that would require just most recent Qt version, and it would be acceptable. What's wrong in relying on changes in recent Qt release and informing the maintainer of it with more strict requirement? There're backports if someone is interested in special cases. > > I just kindly remind your description of current Plasma 5 and it's > > application state: https://bugs.kde.org/show_bug.cgi?id=341930#c30. > Off topic? This was a global statement. Session management in particular is
[Touch-packages] [Bug 1433590] Re: apparmor dbus denial for org.freedesktop.Accounts and make Other vibrations work
** Changed in: usensord (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu
in Ubuntu.
https://bugs.launchpad.net/bugs/1433590
Title:
apparmor dbus denial for org.freedesktop.Accounts and make Other
vibrations work
Status in Canonical System Image:
Confirmed
Status in apparmor-easyprof-ubuntu package in Ubuntu:
Fix Released
Status in ubuntu-system-settings package in Ubuntu:
Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
Confirmed
Status in usensord package in Ubuntu:
In Progress
Bug description:
This affects vivid and (somewhat recently?) 14.09.
At some point, apps started to request access to
org.freedesktop.Accounts for something, but I'm not sure what. It has
been conjectured in this bug that it is due to vibration settings.
Filing against ubuntu-system-settings for now, but please feel free to
move to the correct package.
This happens with webapps:
Apr 7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED"
operation="dbus_method_call" bus="system" path="/org/freedesktop/Accounts"
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send"
name="org.freedesktop.Accounts" pid=2632
profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26"
peer_pid=1596 peer_profile="unconfined"
Apr 7 08:42:17 ubuntu-phablet dbus[797]: apparmor="DENIED"
operation="dbus_method_call" bus="system" path="/org/freedesktop/Accounts"
interface="org.freedesktop.Accounts" member="FindUserById" mask="send"
name="org.freedesktop.Accounts" pid=2632
profile="com.ubuntu.developer.webapps.webapp-facebook_webapp-facebook_1.0.26"
peer_pid=1596 peer_profile="unconfined"
and QML apps:
Apr 7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED"
operation="dbus_method_call" bus="system" path="/org/freedesktop/Accounts"
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send"
name="org.freedesktop.Accounts" pid=3377
profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596
peer_profile="unconfined"
Apr 7 08:43:40 ubuntu-phablet dbus[797]: apparmor="DENIED"
operation="dbus_method_call" bus="system" path="/org/freedesktop/Accounts"
interface="org.freedesktop.Accounts" member="FindUserById" mask="send"
name="org.freedesktop.Accounts" pid=3377
profile="com.ubuntu.calculator_calculator_1.3.339" peer_pid=1596
peer_profile="unconfined"
The following rules allow the requested access:
dbus (send)
bus=system
path="/org/freedesktop/Accounts"
interface="org.freedesktop.DBus.{Introspectable,Properties}"
member=Introspect
peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
bus=system
path="/org/freedesktop/Accounts"
interface="org.freedesktop.Accounts"
member=FindUserById
peer=(name=org.freedesktop.Accounts,label=unconfined),
dbus (send)
bus=system
path="/org/freedesktop/Accounts/User[0-9]*"
interface="org.freedesktop.DBus.Properties"
member=Get
peer=(name=org.freedesktop.Accounts,label=unconfined),
However, the above is too lenient and constitutes a privacy leak for
apps. FindUserById could be used by a malicious app to enumerate
usernames on multiuser systems and because we can't mediate method
data with apparmor, the Get() method can be used to obtain any
information provided by this interface.
The following can be used to see what can be leaked to a malicious app:
gdbus introspect --system -d org.freedesktop.Accounts -o
/org/freedesktop/Accounts/User`id -u phablet`
This can be solved in a couple of ways:
1. add whatever information the app is trying to access to a new helper
service that only exposes things that the app needs. This could be a single
standalone service, perhaps something from ubuntu-system-settings, that could
expose any number of things-- the current locale, if the locale changed, if the
grid units changed, the vibration settings, etc. Since this service wouldn't
have any sensitive information, you could use standard dbus
properties/Get()/etc
2. add a new dbus API to an existing service such that apparmor rules can
then be used to allow by method (eg, GetVibration() or something)
I won't dictate the implementation except to mention that '1' seems
like something generally useful and I believe that it was something
the ubuntu-system-settings devs were already looking at for detecting
locale changes without rebooting.
Original description
starting an app in vivid (image 135 on arale currently)
produces a bunch of dbus denials in syslog ... (there is also a
/dev/tty one but i think this is just because soemthing tries to write
an error to console ... so transient)
http://paste.ubuntu.com/10620834/
To manage notifications about this b
[Touch-packages] [Bug 1538632] Re: ui freezes when simultaneously moving mouse & plug/unplug hdmi
** Description changed:
confirmed to happen in latest image with usc0.3 and previous images with
usc0.2
steps
1) flash ubuntu-touch/rc-proposed/ubuntu-pd
2) connect bt mouse and see unity8 go into windowed mode
3) move mouse about screen while at the same time connect slimport hdmi cable
ui will then freeze but seems content, let it sit for 30 min no reboot or
restart, no crash files, power button does not do anything.
It's also possible to have the slimport already connected - move mouse around
disconnect, the ui will freeze altho in this case unity8 always seems to
restart.
There are no usc crash files.
+
+ The problem is a dead lock on the Display/DisplaySyncGroup mutexes
+ between CompositingFunctor->SystemWindowManager->GraphicsDisplayLayout
+ and DisplayInputRegion.
+
+ Thread 6 (Thread 0xb0dff3d0 (LWP 1530)):
+ #0 0xb6cd5d44 in __libc_do_syscall () from
/lib/arm-linux-gnueabihf/libpthread.so.0
+ No symbol table info available.
+ #1 0xb6cd395c in __lll_lock_wait () from
/lib/arm-linux-gnueabihf/libpthread.so.0
+ No symbol table info available.
+ #2 0xb6ccf19e in pthread_mutex_lock () from
/lib/arm-linux-gnueabihf/libpthread.so.0
+ No symbol table info available.
+ #3 0xb6426f02 in __gthread_mutex_lock (__mutex=0x1b34f14)
+ at /usr/include/arm-linux-gnueabihf/c++/4.9/bits/gthr-default.h:748
+ No locals.
+ #4 lock (this=0x1b34f14) at /usr/include/c++/4.9/mutex:135
+ No locals.
+ #5 lock_guard (__m=..., this=0xb0dfeaf0) at /usr/include/c++/4.9/mutex:377
+ No locals.
+ #6 mir::graphics::android::Display::configuration (this=0x1b34ef8)
+ at
/build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/platforms/android/server/display.cpp:231
+ lock = {_M_device = @0x1b34f14}
+ #7 0xb6e656ca in mir::shell::GraphicsDisplayLayout::place_in_output
(this=, id=...,
+ rect=...)
+ at
/build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/server/shell/graphics_display_layout.cpp:72
+ config = std::unique_ptr
containing 0xb6eb69c8
+ placed = false
+ #8 0xb6e6a888 in mir::shell::SystemCompositorWindowManager::add_display
(this=0x1d07b24)
+ at
/build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/server/shell/system_compositor_window_manager.cpp:1
output_id =
+ rect = {top_left = {x = {value = 0}, y = {value = 0}}, size = {width
= {value = 768}, height = {
+ value = 1280}}}
+ surface = std::shared_ptr (count 3, weak 4) 0x0
+ __for_range =
+ lock = {_M_device = @0x1d07b3c}
+ #9 0xb6e1ab32 in operator() (buffer=..., __closure=)
+ at
/build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/server/compositor/multi_threaded_compositor.cpp:96
+ No locals.
+ #10 std::_Function_handler::_M_invoke(std::_Any_data
const&, mir::graphics::DisplayBuffer&) (__functor=..., __args#0=...)
+ at /usr/include/c++/4.9/functional:2039
+ No locals.
+ #11 0xb64288a8 in operator() (__args#0=..., this=0xb0dfeca0) at
/usr/include/c++/4.9/functional:2439
+ No locals.
+ #12
mir::graphics::android::DisplayGroup::for_each_display_buffer(std::function const&) (this=0x1b35024, f=...)
+ at
/build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/platforms/android/server/display_group.cpp:51
+ __for_range = std::map with 1 elements = {
+ [mir::graphics::android::DisplayName::primary] =
std::unique_ptr containing
0x1c0db40}
+ lk = {_M_device = 0x1b35028, _M_owns = true}
+ #13 0xb6e1b896 in operator() (__closure=)
+ at
/build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/server/compositor/multi_threaded_compositor.cpp:96
+ No locals.
+ #14 PairedCalls (deleter=, creator=,
this=0xb0dfec84)
+ at
/build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/include/common/mir/raii.h:33
+ No locals.
+ #15
paired_calls,
mir::compositor::CompositingFunctor::operator()():: >
(deleter=, creator=)
+ at
/build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/include/common/mir/raii.h:66
+ No locals.
+ #16 mir::compositor::CompositingFunctor::operator() (this=0x1d112d8)
+ at
/build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/server/compositor/multi_threaded_compositor.cpp:98
+ disp_listener = std::shared_ptr (count 5, weak 2) 0x1d07aac
+ display_registration = {deleter = {__this = 0x1d112d8,
+ __disp_listener = std::shared_ptr (count 5, weak 2) 0x1d07aac},
owner = true}
+ compositor_registration =
+ compositors = std::vector of length 1, capacity 1 = {std::tuple
containing = {[1] = 0x1c0db40,
+ [2] = std::unique_ptr
containing 0xb0499848}}
+ lock = {_M_device = 0xb0402c44, _M_owns = true}
+ #17 0xb6e8aa58 in operator() (this=0xb0dfed84) at
/usr/include/c++/4.9/functional:2439
+ No locals.
+ #18 execute (this=0xb0dfed84)
+ at
/build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/server/thread/basic_thread_pool.cpp:40
+ No locals.
+ #19 operator() (this=0x1d1ce88)
+ at
/build/mir-ua35pY/mir-0.19.0+15.04.20160126.1/src/server/th
[Touch-packages] [Bug 1446865]
(In reply to Thomas Lübking from comment #22) > > 5. I completely don't like the proposed way to preserve the compatibility > > with (4) and make > > the use case of broken session management client implementation legal and > > default, but > > also try to allow proper-written apps to still survive somehow, adding some > > strange > > workarounds to Qt as closing all the windows, but not too much, or API > > properties to enable > > proper processing of SM messages. > > No ofense, but what you "like" is completely irrelevant. Comments like this clearly don't help the discussion or solving the problem, especially when you start your reply with them. I won't answer you the same style, but given that it's not the first one from you, my earnest request to you is to please respect each other and avoid such comments in future. In case of any questions feel free to consult https://www.kde.org/code-of-conduct/. Thank you. > You propose to intentionally break clients by library changes in some minor > update Never mentioned minor update or particular version. Please don't distort. > to teach developers to do right No intention to do it, but any specs probably means something like that. > but while you might aim their face, you're gonna hit the users (and probably yours) Users were already hit when the significant part of functionality important for someone's every day use case is broken. I just can't get why it's OK to break everything for one part of users and ultimately save broken implementation to preserve some ephemeral compatibility for another. That's probably the biggest question for me in this thread. Maybe I'm wrong and those who use sessions are somewhat less important than users that sometimes save their data on quitting? It's worth mentioning then, and I'll immediately give up. > We had that (I kindly remind of the qDeleteAll fix ...) and it cooked up > hell. Still better than a couple of API methods like "enableSpecifiedBehaviour()" or deleting and trying to catch SIGSEGV, right?) > commitDataRequest hardly shows up in lxr.kde.org, what means it's probably > not used at all and aboutToQuit (which isn't used but could come to rescue) > isn't used too much either. > > The BY FAR! omnipresent pattern is to listen to queryClose() which is > called/emitted on -guess what- close events from KMainWindow. > And that's for pretty much sure why the (wrong) behavior in QSessionManager > exists. If it wasn't done before for some reason, it's better to just fix the applications, especially given that you don't need any changes in Qt to have just the same functionality with the new approach. If it's still too much to change while porting to Qt5/KF5, I really wonder what porting is. Once again: we all could already apply the fix of Andreas and be busy fixing the necessary applications rather than keep discussing here. > Is this behavior correct? No. > Does this matter? NO! > > It's ok to spam a #warning that this behavior is shit and deprecate and kill > it for Qt6 On the Qt6 release you would say that everyone already rely on the workaround there was in Qt5 etc. etc. That's an endless story. By the way, do you really think it's so much major change that it can't be changed before Qt6? Seriously, with no API change and with just removing unexpected actions? > and we might even bail out (aka "fix") KMainWindow applications > NOW by invoking queryClose() on QGuiApplicationPrivate::commitData() but > regardless, we MUST assume this to be a global default pattern that > applications (also beyond KDE) rely on (also because it's absolutely natural > to intercept closing to save data and not think of closing on session end > could be something entirely different - actually the illegal behavior > happens to be the most sane one...) I just kindly remind your description of current Plasma 5 and it's application state: https://bugs.kde.org/show_bug.cgi?id=341930#c30. It was written months ago, but nothing changed too dramatically from then. Even if the proper fix could break some apps, they all are *already in* transition process, Wayland is just around the corner with another transition process, so now it's the perfect time to fix something to make it finally working properly rather than make life easier for now and have this pain for years again and again. > > Now, *actually* closing windows to test interaction on session end is of > course just as wrong - if the user cancels the logout by such incident, we > should not have closed random other windows before (letting alone that it > causes this but) - therefore I frankly do not understand what's so > complicated about just faking a close event to serve the present "save your > stuff" pattern in a majority in clients without causing the destructive > close itself which may not only be a bit premature, but also triggers this > bug. > > It's the least invasive solution that does not require everyone to signal > "yes, i can sessionmanagement" (what's not g
[Touch-packages] [Bug 1446865]
(In reply to Thomas Lübking from comment #26) > (In reply to Alexey Chernov from comment #25) > > > According to what? > According to "This is not fixed in years and each and every session > management code was ported as "#if 0"" > If there was some relevant interest, it would be fixed long time, since it's > really not that hard. Rather interesting indicator. Why don't you apply it to Qt5 or KF5 then? What a selective vision :) > > > Loosing your data is however relevant for everyone. And the latter is the > > > by > > > far more severe issue. Restarting applications is merely an annoyance, > > > loosing your work is truely expensive. > > > Hey, how could session management be "apparently relevant for only a > > minority of users", but fixes in its behaviour be crucial for a lot of them? > [...] > > Fully agree here, but we should confirm that nobody said in the beggining > > that upstream changes were about to break session management for KF5 > > applications. It was just broken. > > Errr... what? > Session management (in terms of "please restore the desktop as I left it") > doesn't seem very important, but if you click "logout" and *booom*, gone is > your work of the last two hours because the application had no chance (or, > well, listened to the wrong events) to ask you to save it, that's pretty > important... Hmmm... so session management "doesn't seem very important", but there're applications which expect a) to be closed gently, and also b) to have an opportunity to interact to the user the very special way, so that the rest of the world is waiting for them and doesn't logout, but it's surely not session management. Nice. Following this way we have, I think, thousands of apps which don't use X, kernel etc. and other not so important stuff. > We're apparently talking past each other. > There're two steps: > a) logout, clients ask to save your stuff. That works (because of the close > event) > b) login, clients should restart. That's broken (because the close event is > not just an event, but the window "illegally" being withdrawn during logout) > > You propse to fix (b) by breaking (a) and I'm trying to convince you that > this is a really bad idea. The matter is just that if you like the fruitful results of some service or protocol, you need to follow the rules of it. If you violate them and currently it just works, it's natural that anyone can change something internally and you are going to fail. Rather atomic thing. My proposal is just to have library code of Qt following the proper interaction process, which is expected by anyone who haven't read this discussion and just wants to support session management in the application. Nothing against any workarounds in KSMServer, KF wrappers or anywhere else downstream. > > bugs which should be fixed either in library and its clients. It's better to > > fix them when no one really relies on the stability too much. It looks like > > this time is now for KF5-based application and environment. > Yes, we should fix KMainWindow now (if faking close events is finally not > considered a permanent behavior despite the majority of clients will > probably do that in return to the data commit request - with a fair share > actually just calling close() ...) but that has absolutely no implications > on whether it's ok to easily break away from established (even though maybe > wrong) behavior. There's no one accepted fix of Qt to fix anything against. There's a way to fix applications to interact with session manager properly though and add some fixes and workarounds to make it work somehow, at least with any local Qt patch. According to the comments of https://codereview.qt-project.org/#/c/146566/, that's something what Andreas is doing. > > No, that's just postponing and messing up the whole problem. If, as you > > stated, almost no one implemented easy and pretty simple interaction > > appeared in Qt5, even less would care of possible bugs and corner cases of > > the workaround, more complex protocol with close event you propose. There > > would be just another argument that it's just too messy, not to mention > > already existing argument that no one uses session management. > > Sorry, but I really cannot read any sense into this paragraph. > Please try to rephrase it. The above isn't English grammar at all. Again. Please try to reread it: https://www.kde.org/code-of-conduct/. Hopefully, it's English would impress you more. > > It won't be fixed until it's broken > So you demand to jeopardize userdata because otherwise code won't be fixed. > Sorry, but there's no way you're ever gonna convince me in this. > Any solution that builds upon "jeopardize userdata" is not a solution at > all. It's malicious. Just one workaround to close the clients gently (with timeout or whatever) in session server would save anyone who is afraid of "jeopardize userdata". I just don't want this apparently kind purpose of preserving good old behaviour to "jeopar
[Touch-packages] [Bug 1446865]
(In reply to Alexey Chernov from comment #30) > The same way commercial customers or applications would be affected with API > changes. How an ABI styable API extension could affect anyone is frankly beyond me - I doubt it will help to resolve the problem but there's really no problem with it. -- 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/1446865 Title: KDE5/Qt5 does not support session restoration Status in KDE Base Workspace: Confirmed Status in Qt: New Status in plasma-workspace package in Ubuntu: Confirmed Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: KDE5/Qt5 does not support proper session restoration. ProblemType: Bug DistroRelease: Ubuntu 15.10 To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1446865/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
