[Touch-packages] [Bug 1471398] Re: Sync ust 2.6.2-2 (main) from Debian unstable (main)
This bug was fixed in the package ust - 2.6.2-2 Sponsored for Artur Rona (ari-tczew) --- ust (2.6.2-2) unstable; urgency=medium [ Michael Jeanson ] * [f1bd937] Default to no unaligned access on unsupported archs * [9663c9a] Add java subpackages * [a23d3b8] Use python3 for lttng-gen-tp (Closes: #789790) -- Jon Bernard jbern...@debian.org Thu, 02 Jul 2015 19:10:06 + ** Changed in: ust (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ust in Ubuntu. https://bugs.launchpad.net/bugs/1471398 Title: Sync ust 2.6.2-2 (main) from Debian unstable (main) Status in ust package in Ubuntu: Fix Released Bug description: Please sync ust 2.6.2-2 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Merge from Debian unstable. (LP: #1468345) Remaining changes: - debian/control, debian/patches/use-python3.patch: + Switch to use python3. (Closes: #789790) * Drop following changes, fixed in Debian / upstream: - debian/patches/0001-Add-aarch64-host-cpu-in-configure.ac.patch: + Add arm64 host_cpu stanzas in configure.ac - debian/liblttng-ust0.symbols: + Update symbols file. - debian/control: + Enable builds on arm64 and ppc64el. Debian has merged Ubuntu changes related to python3 support. Changelog entries since current wily version 2.6.2-1ubuntu1: ust (2.6.2-2) unstable; urgency=medium [ Michael Jeanson ] * [f1bd937] Default to no unaligned access on unsupported archs * [9663c9a] Add java subpackages * [a23d3b8] Use python3 for lttng-gen-tp (Closes: #789790) -- Jon Bernard jbern...@debian.org Thu, 02 Jul 2015 19:10:06 + To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ust/+bug/1471398/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1462346] Re: Wrong size of folder-drag-accept/gnome-fs-directory-accept icon at zoom levels bigger than 100% in Nautilus
** Changed in: humanity-icon-theme (Ubuntu) Status: New = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to humanity-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1462346 Title: Wrong size of folder-drag-accept/gnome-fs-directory-accept icon at zoom levels bigger than 100% in Nautilus Status in humanity-icon-theme package in Ubuntu: In Progress Bug description: Hello, the icon size of the folder-drag-accept/gnome-fs-directory-accept icon in Nautilus is too small when a zoom level bigger than 100% in the icon view is used. This can be reproduced the following way: - Start Nautilus (or Nemo) - Open a directory that contains at least one subdirectory plus at least one file (or a second subdirectory) - Switch to icon view, set a zoom level bigger than 100% - Try to move a file/directory into another directory - When the mouse moves over the target directory, it's icon will switch to the folder-drag-accept/gnome-fs-directory-accept icon, but in a version that is no larger than 48x48, even if the zoom level (and thus the icon size) is set greater. I have attached a screenshot that illustrates the problem. With the Adwaita icon theme the problem does not happen, the icon seems to get the correct size at all zoom levels. Currently the Humanity icon theme contains (as symlink) a svg file of the responsible folder-drag-accept/gnome-fs-directory-accept icon in the directories Humanity/status/24 and Humanity/48. The dirs for bigger icons (e.g. 128) do not contain that icons, so I assumed it may be a quick fix to symlink them to also to those dirs. But that caused just other problems - now the icons had always the 128x128 size regardless of zoom level and was often too big instead of too small! A way to fix this seems to be to place png files of the icons in all of the Humanity/status/[icon size]-directories, each png scaled to the appropriate size. That is a bit more hassle but seems to work for the Adwaita theme. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: humanity-icon-theme 0.6.8 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jun 5 10:53:39 2015 InstallationDate: Installed on 2015-04-16 (49 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150415) PackageArchitecture: all SourcePackage: humanity-icon-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1462346/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1462489] Re: Allow apps to keep the screen on
Back from holidays, integrating Michael's patch into qtsystems- opensource-src. ** Also affects: qtsystems-opensource-src (Ubuntu) Importance: Undecided Status: New ** Changed in: qtsystems-opensource-src (Ubuntu) Assignee: (unassigned) = Timo Jyrinki (timo-jyrinki) ** Changed in: qtsystems-opensource-src (Ubuntu) Importance: Undecided = High ** Changed in: qtsystems-opensource-src (Ubuntu) Status: New = In Progress ** Also affects: qtsystems-opensource-src (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: qtsystems-opensource-src (Ubuntu RTM) Importance: Undecided = High ** Changed in: qtsystems-opensource-src (Ubuntu RTM) Assignee: (unassigned) = Timo Jyrinki (timo-jyrinki) -- 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/1462489 Title: Allow apps to keep the screen on Status in the base for Ubuntu mobile products: Confirmed Status in apparmor-easyprof-ubuntu package in Ubuntu: Confirmed Status in qtsystems-opensource-src package in Ubuntu: In Progress Status in qtubuntu package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Status in qtsystems-opensource-src package in Ubuntu RTM: New Bug description: Support an interface in QML and HTML to allow an app to keep the screen on while the app is active. This has come up in several scenarios, such as an ebook reader, a clock in night mode. First step is to hook up QtSystemInfo screenSaverEnabled One solution to inhibit the screen blanking: Add a new dbus rule to the default template Provide a mediator (unity8) to control this, so it can restore the screen blanking when the app is not active or has been closed Prompt the user for confirmation the first time the app accesses it use the trust store to avoid prompts each time add to the System settings Other app access panel an entry for Screen or Display so the setting could be revoked To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1462489/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471716] Re: counting down can not be stopped in camera app after taping power key .
Actual result : After step 5, Counting down can not be stopped. when counting down is stooped, picture can not be taken sometimes. -- 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/1471716 Title: counting down can not be stopped in camera app after taping power key . Status in camera-app package in Ubuntu: New Bug description: system-image-cli -i current build number: 56 device name: krillin plast update: 2015-07-06 04:16:52 version version: 56 version ubuntu: 20150703 version device: 20150529-8e13c5f version custom: 20150528-722-29-15-vivid step by step 1. Open camera app 2.Set counting down to 15s /5s 3.Tap camera key 4.Tap power key during counting down 5.Tap power key again. Expected result After step 5, Counting down stopped. Actual result After step 5, Counting down can not be stopped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1471716/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448623] Re: package click 0.4.38.5 failed to install/upgrade: 子进程 新的 pre-removal 脚本 返回错误状态 1
I don't know if my problem is caused by this bug. Here are my summary: $ sudo apt-get purge click [sudo] password for chen: 正在读取软件包列表... 完成 正在分析软件包的依赖关系树 正在读取状态信息... 完成 下列软件包将被【卸载】: click* 升级了 0 个软件包,新安装了 0 个软件包,要卸载 1 个软件包,有 0 个软件包未被升级。 解压缩后将会空出 166 kB 的空间。 您希望继续执行吗? [Y/n] y (正在读取数据库 ... 系统当前共安装有 313386 个文件和目录。) 正在卸载 click (0.4.38.5) ... Traceback (most recent call last): File /usr/bin/click, line 31, in module from click import commands ImportError: cannot import name 'commands' dpkg: 处理软件包 click (--purge)时出错: 子进程 已安装 pre-removal 脚本 返回错误状态 1 Job for click-system-hooks.service failed. See systemctl status click-system-hooks.service and journalctl -xe for details. click-system-hooks.service couldn't start. 在处理时有错误发生: click E: Sub-process /usr/bin/dpkg returned an error code (1) chen@Chen-Server:~$ systemctl status click-system-hooks.service ● click-system-hooks.service - Run Click system-level hooks Loaded: loaded (/lib/systemd/system/click-system-hooks.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since 一 2015-07-06 18:21:06 CST; 10s ago Docs: man:click(1) Process: 4032 ExecStart=/usr/bin/click hook run-system (code=exited, status=1/FAILURE) Main PID: 4032 (code=exited, status=1/FAILURE) 7月 06 18:21:06 Chen-Server systemd[1]: Starting Run Click system-level hooks... 7月 06 18:21:06 Chen-Server click[4032]: Traceback (most recent call last): 7月 06 18:21:06 Chen-Server click[4032]: File /usr/bin/click, line 31, in module 7月 06 18:21:06 Chen-Server click[4032]: from click import commands 7月 06 18:21:06 Chen-Server click[4032]: ImportError: cannot import name 'commands' 7月 06 18:21:06 Chen-Server systemd[1]: click-system-hooks.service: main process exited, code=exited, status=1/FAILURE 7月 06 18:21:06 Chen-Server systemd[1]: Failed to start Run Click system-level hooks. 7月 06 18:21:06 Chen-Server systemd[1]: Unit click-system-hooks.service entered failed state. 7月 06 18:21:06 Chen-Server systemd[1]: click-system-hooks.service failed. $ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1448623 Title: package click 0.4.38.5 failed to install/upgrade: 子进程 新的 pre-removal 脚本 返回错误状态 1 Status in click package in Ubuntu: Confirmed Bug description: The package cannot be installed. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: click 0.4.38.5 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Sun Apr 26 14:39:56 2015 DpkgHistoryLog: Start-Date: 2015-04-26 14:39:55 Commandline: apt-get -f dist-upgrade Upgrade: click:amd64 (0.4.33, 0.4.38.5), click-apparmor:amd64 (0.2.11.2, 0.3.8), ubuntu-app-launch:amd64 (0.4+14.10.20141006-0ubuntu1, 0.4+15.04.20150410-0ubuntu1) DuplicateSignature: package:click:0.4.38.5:子进程 新的 pre-removal 脚本 返回错误状态 1 ErrorMessage: 子进程 新的 pre-removal 脚本 返回错误状态 1 RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: click Title: package click 0.4.38.5 failed to install/upgrade: 子进程 新的 pre-removal 脚本 返回错误状态 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1448623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471597] Re: MX4 ubuntu version screen won't auto-lock
Ah, also the weird thing is the phone does wake up for notifications and such, so I think the monitor is still working, just neglects to turn off after stay awake time runs out. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1471597 Title: MX4 ubuntu version screen won't auto-lock Status in powerd package in Ubuntu: New Bug description: I'm running 15.04 r2. Initially, the screen locked nicely, but I turned that off for a while (for USB access etc). Now it's turned back on again, and it seems not to lock automatically anymore. Due to battery consumption this is a pretty annoying bug. I ran powerd-cli test: all passed except the first: Test: checkForDbusName(test_dbusname, 0, requests, TRUE) result: FAILED Attached is the full output and the syslog entries for a period where I turn on the screen, wait for 2 minutes, and turn it off again. (lock time is 1 minute. Also doesn't turn off after 1hr) What does it mean that testdbus_name is failing? What should happen when screen autolocks? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1471597/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471752] [NEW] apport fails to capture Package field when pinger from squid3 crashes
Public bug reported: Summary: The problem is either that apport fails to associate /usr/lib/squid3/pinger with the squid3 package, or that apport-retrace fails to parse a crash report. Apport has captured some information in a crash file (attached) regarding a crash of the pinger process from the squid3 package. When I run apport-retrace, I get the following error message: # apport-retrace -s -S system /var/crash/_usr_lib_squid3_pinger.0.crash ERROR: report file does not contain one of the required fields: CoreDump DistroRelease Package ExecutablePath The crash report contains the CoreDump, DistroRelease and ExecutablePath fields, but does not contain the Package field. This line appears in the kernel log when pinger crashes: [6017418.123570] pinger[16002]: segfault at 3e822f940098 ip 7f9d3be37845 sp 7ffc798fcbb0 error 4 in libc-2.19.so[7f9d3bdb9000+1bb000] What I expect should happen: apport captures the Package field in the crash report, and apport-retrace is able to process the crash report. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apport-retrace 2.14.1-0ubuntu3.11 ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CrashReports: 640:0:0:58707:2015-07-06 07:54:44.017688187 +0100:2015-07-06 11:28:22.003206431 +0100:/var/crash/_usr_lib_squid3_pinger.0.crash Date: Mon Jul 6 11:38:22 2015 InstallationDate: Installed on 2012-03-26 (1196 days ago) InstallationMedia: Mythbuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to trusty on 2014-07-20 (350 days ago) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: crash file that apport-retrace has trouble with https://bugs.launchpad.net/bugs/1471752/+attachment/4425021/+files/_usr_lib_squid3_pinger.0.crash -- 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/1471752 Title: apport fails to capture Package field when pinger from squid3 crashes Status in apport package in Ubuntu: New Bug description: Summary: The problem is either that apport fails to associate /usr/lib/squid3/pinger with the squid3 package, or that apport-retrace fails to parse a crash report. Apport has captured some information in a crash file (attached) regarding a crash of the pinger process from the squid3 package. When I run apport-retrace, I get the following error message: # apport-retrace -s -S system /var/crash/_usr_lib_squid3_pinger.0.crash ERROR: report file does not contain one of the required fields: CoreDump DistroRelease Package ExecutablePath The crash report contains the CoreDump, DistroRelease and ExecutablePath fields, but does not contain the Package field. This line appears in the kernel log when pinger crashes: [6017418.123570] pinger[16002]: segfault at 3e822f940098 ip 7f9d3be37845 sp 7ffc798fcbb0 error 4 in libc-2.19.so[7f9d3bdb9000+1bb000] What I expect should happen: apport captures the Package field in the crash report, and apport-retrace is able to process the crash report. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apport-retrace 2.14.1-0ubuntu3.11 ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CrashReports: 640:0:0:58707:2015-07-06 07:54:44.017688187 +0100:2015-07-06 11:28:22.003206431 +0100:/var/crash/_usr_lib_squid3_pinger.0.crash Date: Mon Jul 6 11:38:22 2015 InstallationDate: Installed on 2012-03-26 (1196 days ago) InstallationMedia: Mythbuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to trusty on 2014-07-20 (350 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1471752/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471448] Re: webrtc don't working, no access to cam and mic
*** This bug is a duplicate of bug 1410996 *** https://bugs.launchpad.net/bugs/1410996 ** This bug has been marked a duplicate of bug 1410996 Add WebView.mediaAccessPermissionRequested API -- 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/1471448 Title: webrtc don't working, no access to cam and mic Status in webbrowser-app package in Ubuntu: New Bug description: Webrtc in Webpages like: www.vline.com can't access cam and mic. Please fix this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1471448/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1470580] Re: unprivileged lxc containers fails with custom bridge
Also, what does Quota reached. mean? What kind of quota is that? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1470580 Title: unprivileged lxc containers fails with custom bridge Status in lxc package in Ubuntu: Confirmed Bug description: Using 15.04 x86_64 with all the updates installed. I'd like 2 containers to communicate with each other via bridge interface. For that I've created interface as follows: /etc/systemd/network/internalbridge1.netdev: [NetDev] Name=ibr1 Kind=bridge /etc/lxc/lxc-usernet: # USERNAME TYPE BRIDGE COUNT x veth ibr1 8 The 'x' is my username, it's first and only user configured in the system so default id map should work fine. The container network is configured as follows: lxc.network.type = veth lxc.network.link = ibr1 lxc.network.flags = up lxc.network.name = internal lxc.network.ipv4 = 10.1.8.2/24 lxc.network.ipv4.gateway = 10.1.8.1 I've enabled the service and brought the bridge up - showing ok via 'ip a' and 'brctl show'. Also works fine with priviledged containers. However with unpriviledged containers it fails: lxc-start -n asterisk -l debug -F --logfile lxc-user.log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1470580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1470580] Re: unprivileged lxc containers fails with custom bridge
lxc-start -n asterisk -F Quota reached. lxc-start: start.c: lxc_spawn: 1000 failed to create configured network lxc-start: start.c: __lxc_start: 1164 failed to spawn 'asterisk' lxc-start: start.c: main: 344 The container failed to start. lxc-start: start.c: main 348 Additional information can be obtained by setting the --logfile and --logpriority options. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1470580 Title: unprivileged lxc containers fails with custom bridge Status in lxc package in Ubuntu: Confirmed Bug description: Using 15.04 x86_64 with all the updates installed. I'd like 2 containers to communicate with each other via bridge interface. For that I've created interface as follows: /etc/systemd/network/internalbridge1.netdev: [NetDev] Name=ibr1 Kind=bridge /etc/lxc/lxc-usernet: # USERNAME TYPE BRIDGE COUNT x veth ibr1 8 The 'x' is my username, it's first and only user configured in the system so default id map should work fine. The container network is configured as follows: lxc.network.type = veth lxc.network.link = ibr1 lxc.network.flags = up lxc.network.name = internal lxc.network.ipv4 = 10.1.8.2/24 lxc.network.ipv4.gateway = 10.1.8.1 I've enabled the service and brought the bridge up - showing ok via 'ip a' and 'brctl show'. Also works fine with priviledged containers. However with unpriviledged containers it fails: lxc-start -n asterisk -l debug -F --logfile lxc-user.log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1470580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1470580] Re: unprivileged lxc containers fails with custom bridge
Btw, is there a way to make logging to actually work and log everything? Maybe add --logging-indeed-log or smth like that in addition to existing -l and --logfile? ** Changed in: lxc (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1470580 Title: unprivileged lxc containers fails with custom bridge Status in lxc package in Ubuntu: Confirmed Bug description: Using 15.04 x86_64 with all the updates installed. I'd like 2 containers to communicate with each other via bridge interface. For that I've created interface as follows: /etc/systemd/network/internalbridge1.netdev: [NetDev] Name=ibr1 Kind=bridge /etc/lxc/lxc-usernet: # USERNAME TYPE BRIDGE COUNT x veth ibr1 8 The 'x' is my username, it's first and only user configured in the system so default id map should work fine. The container network is configured as follows: lxc.network.type = veth lxc.network.link = ibr1 lxc.network.flags = up lxc.network.name = internal lxc.network.ipv4 = 10.1.8.2/24 lxc.network.ipv4.gateway = 10.1.8.1 I've enabled the service and brought the bridge up - showing ok via 'ip a' and 'brctl show'. Also works fine with priviledged containers. However with unpriviledged containers it fails: lxc-start -n asterisk -l debug -F --logfile lxc-user.log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1470580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1470580] Re: unprivileged lxc containers fails with custom bridge
cat /etc/lxc/lxc-usernet # USERNAME TYPE BRIDGE COUNT x veth ibr1 8 x veth xbr1 8 x veth ubr1 8 cat .local/share/lxc/asterisk/config # Template used to create this container: /usr/share/lxc/templates/lxc-download # Parameters passed to the template: -d ubuntu -r vivid -a amd64 # For additional config options, please look at lxc.container.conf(5) # Distribution configuration lxc.include = /usr/share/lxc/config/ubuntu.common.conf lxc.include = /usr/share/lxc/config/ubuntu.userns.conf lxc.arch = x86_64 # Container specific configuration lxc.include = /etc/lxc/default.conf lxc.id_map = u 0 10 65536 lxc.id_map = g 0 10 65536 lxc.rootfs = /home/x/.local/share/lxc/asterisk/rootfs lxc.utsname = asterisk # Network configuration lxc.network.type = veth lxc.network.link = ubr1 lxc.network.flags = up lxc.network.name = internal #lxc.network.ipv4 = 10.1.8.2/24 #lxc.network.ipv4.gateway = 10.1.8.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1470580 Title: unprivileged lxc containers fails with custom bridge Status in lxc package in Ubuntu: Confirmed Bug description: Using 15.04 x86_64 with all the updates installed. I'd like 2 containers to communicate with each other via bridge interface. For that I've created interface as follows: /etc/systemd/network/internalbridge1.netdev: [NetDev] Name=ibr1 Kind=bridge /etc/lxc/lxc-usernet: # USERNAME TYPE BRIDGE COUNT x veth ibr1 8 The 'x' is my username, it's first and only user configured in the system so default id map should work fine. The container network is configured as follows: lxc.network.type = veth lxc.network.link = ibr1 lxc.network.flags = up lxc.network.name = internal lxc.network.ipv4 = 10.1.8.2/24 lxc.network.ipv4.gateway = 10.1.8.1 I've enabled the service and brought the bridge up - showing ok via 'ip a' and 'brctl show'. Also works fine with priviledged containers. However with unpriviledged containers it fails: lxc-start -n asterisk -l debug -F --logfile lxc-user.log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1470580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1468738] Re: Requesting desktop view
*** This bug is a duplicate of bug 1377033 *** https://bugs.launchpad.net/bugs/1377033 ** This bug has been marked a duplicate of bug 1377033 [Browser] Ability to switch to the desktop mode (desktop version) -- 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/1468738 Title: Requesting desktop view Status in webbrowser-app package in Ubuntu: New Bug description: Many times it is handy for user to request the desktop view of a site. Sometimes the mobile version of a website is either limited or broken. Android handle it like this: http://cdn.cultofandroid.com/wp- content/uploads/2012/05/desktopsite.jpg We could have a similar checkbox in browser app settings. The user-agent of browser would then change to one of a desktop browser, resulting in the sites displaying the desktop version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1468738/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1433141] Re: [FFe] Bottom-edge gesture to open tabs list in the browser application
** Changed in: webbrowser-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 webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1433141 Title: [FFe] Bottom-edge gesture to open tabs list in the browser application Status in webbrowser-app package in Ubuntu: Fix Released Bug description: This bug is to request a feature freeze exception in order to land the work done to implement bottom-edge gesture commanded tabs view in webbrowser-app, on touch devices. On desktop, the mechanism to open the list of open tabs remains unchanged (from the drawer menu), although the view itself has been revamped a bit to conform to the latest visual designs (and that affects both touch and desktop). Note that this doesn’t affect at all the webapp container. The relevant merge request is: https://code.launchpad.net/~osomon/webbrowser-app/bottom-edge/+merge/248019. Although the diff is huge, most of it is code imported from lp:unity8 to leverage the DirectionalDragArea component, which is not available publicly in the UITK yet (but is being considered for inclusion). This imported code will eventually go away, I am actively lobbying to get it integrated in the UITK. The feature itself has been in development for several months (since the beginning of the vivid cycle really, with many interruptions in between). I was hoping to land it before feature freeze, but it didn’t happen because of shuffled priorities. The design specification is available at https://docs.google.com/a/canonical.com/presentation/d/1Qrd4Flfs3EH- fI79IfrYgLdAx2nce-L7ve8NKLCX324/edit#slide=id.g2acbd6553_031. This is a partial implementation only, agreed upon with design (the complete feature will land in several iterations). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1433141/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1350891] Re: [Scopes] Suru Background should scroll
** Changed in: ubuntu-clock-app Assignee: Nekhelesh Ramananthan (nik90) = (unassigned) -- 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/1350891 Title: [Scopes] Suru Background should scroll Status in the base for Ubuntu mobile products: Invalid Status in Clock application for Ubuntu devices: Triaged Status in Ubuntu UX bugs: Triaged Status in unity8 package in Ubuntu: Invalid Status in unity8 package in Ubuntu RTM: Invalid Bug description: On the dash, the Suru paper folds stays fixed at the bottom, while it should rather scroll away. We should also 'tile' the background, so the paper fold is displayed again after scrolling a certain amount of vertical space. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1350891/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1412732] Re: [browser] visuals for multi-select mode in history view need update
** Branch linked: lp:~osomon/webbrowser-app/multi-select-close-icon -- 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/1412732 Title: [browser] visuals for multi-select mode in history view need update Status in Ubuntu UX bugs: Fix Committed Status in Web Browser App: Fix Released Status in webbrowser-app package in Ubuntu: Fix Released Status in webbrowser-app package in Ubuntu RTM: Fix Released Bug description: Multi-select mode in the history view was implemented as part of bug #1351167. But the visuals do not match the visual spec exactly. Spec: https://docs.google.com/a/canonical.com/presentation/d/1woHjO8K4iqyVZZlfQ4BXL0DhYbwkEmZ7wvcUhYzHDRk/edit#slide=id.g354125fb9_0110 Screenshot: https://launchpadlibrarian.net/195323251/browser- multiselect.png In particular, padding and spacing need to be adjusted. The buttons at the top should have a label, too. [UX Comment] All appears correct other than a back chevron () being shown for cancel instead of the cancel icon (X) See: https://docs.google.com/presentation/d/1woHjO8K4iqyVZZlfQ4BXL0DhYbwkEmZ7wvcUhYzHDRk/edit#slide=id.g354125fb9_0110 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1412732/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1289434] Re: uninstall confirmation and error previews send close_preview action, which causes scope to send installed preview
This bug was fixed in the package unity-scope-click 0.1.1+15.04.20150701.2-0ubuntu1 in https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/stable-phone-overlay --- unity-scope-click (0.1.1+15.04.20150701.2-0ubuntu1) vivid; urgency=medium [ CI Train Bot ] * New rebuild forced. [ Rodney Dawes ] * Move libpay abstraction from store scope into libclickscope. Split CLOSE_PREVIEW action into SHOW_INSTALLED and SHOW_UNINSTALLED. Refunds UI elements (disabled for now). (LP: #1289434) -- CI Train Bot ci-train-...@canonical.com Wed, 01 Jul 2015 19:49:20 + ** Changed in: unity-scope-click (Ubuntu RTM) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1289434 Title: uninstall confirmation and error previews send close_preview action, which causes scope to send installed preview Status in the base for Ubuntu mobile products: New Status in unity-scope-click package in Ubuntu: Fix Released Status in unity-scope-click source package in Vivid: New Status in unity-scope-click package in Ubuntu RTM: Fix Released Bug description: So if the user sees a download error and clicks 'close', they will be shown a screen that looks like the app was installed, when it really wasn't. The error previews should use an action that lets the scope know which error was displayed, so it can show the correct next preview. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1289434/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1467609] Re: vibrations on MSI gt72 2qe scren
hmm maybe I was not clear I d/l the .zip BIO file, unzip it on desktop. It contains a how to updaqte BIOS.txt file which only contains a link : http://www.msi.com/files/pdf/How_to_update_bios_en.pdf The .zip has only, beside the 3 .txt (which I assume are the same link for different language), -- 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/1467609 Title: vibrations on MSI gt72 2qe scren Status in xorg package in Ubuntu: Incomplete Bug description: bought it last week, GPU is NVidia Ge Force 980M. With nouveau installed I only use the small intel chipset ; I installed nvidia 352 from their site, and it works good for the external screen I have but now the integrated screen has those problems. The description is, like the front of the screen was vibrating. I think a better term could be used, see attached screenshot. As you can notice, lines are shifted to left/right on several positions of the screen. It makes the use of the screen very unpleasant. So I usually switch it off. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 352.21 Tue Jun 9 21:53:31 PDT 2015 GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jun 22 18:40:33 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.19.0-15-generic, x86_64: installed bbswitch, 0.7, 3.19.0-21-generic, x86_64: installed nvidia-352, 352.21, 3.19.0-21-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GM204M [GeForce GTX 980M] [10de:13d7] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1129] InstallationDate: Installed on 2015-06-19 (2 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: Micro-Star International Co., Ltd. GT72 2QE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic root=UUID=4fabaada-02c5-4230-a634-0b88cf228b5f ro quiet splash SourcePackage: xorg Symptom: display UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1781IMS.10H dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1781 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10H:bd11/21/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: GT72 2QE dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.61+git20150614.97be70b4-0ubuntu0ricotz~vivid version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.0~git20150616+10.6.5d327b37-0ubuntu0ricotz~vivid version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.0~git20150616+10.6.5d327b37-0ubuntu0ricotz~vivid version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.99+git20150521.d64a13eb-0ubuntu0ricotz~vivid version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150528.fb1643f0-0ubuntu0sarvatt~vivid version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11+git20150528.27234dbe-0ubuntu0sarvatt~vivid xserver.bootTime: Mon Jun 22 18:11:59 2015 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1467609/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1296364] Re: [browser] No option for deleting cache
@James: I filed bug #1471747 to track the lack of a confirmation dialog. Feel free to close this one. ** Changed in: webbrowser-app (Ubuntu RTM) Assignee: (unassigned) = Olivier Tilloy (osomon) -- 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/1296364 Title: [browser] No option for deleting cache Status in Ubuntu UX bugs: Fix Committed Status in Web Browser App: Fix Released Status in webbrowser-app package in Ubuntu: Fix Released Status in webbrowser-app package in Ubuntu RTM: Fix Released Bug description: The only way to do this is by deleting the respective files in /home/phablet/.local/share/webbrowser-app/. -- SOLUTION -- Clearing the cache will be available from the settings screen, once this is implemented. https://docs.google.com/a/canonical.com/presentation/d/1Qrd4Flfs3EH-fI79IfrYgLdAx2nce-L7ve8NKLCX324/edit#slide=id.g3583da3f4_00 [UX Comment] Setting is present but a 'Clear Cache' confirmation dialogue required, as described here: https://docs.google.com/presentation/d/1Qrd4Flfs3EH-fI79IfrYgLdAx2nce-L7ve8NKLCX324/edit#slide=id.g3583da3f4_00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1296364/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471747] [NEW] Missing confirmation dialog when clearing browsing data
Public bug reported: According to the UX specification (https://docs.google.com/presentation/d/1Qrd4Flfs3EH-fI79IfrYgLdAx2nce- L7ve8NKLCX324/edit#slide=id.g3583da3f4_00), when clearing browsing data (under Settings Privacy), there should be a confirmation dialog to give the user a chance to cancel the action. ** Affects: ubuntu-ux Importance: Undecided Status: New ** Affects: webbrowser-app (Ubuntu) Importance: Medium Status: Confirmed ** Also affects: ubuntu-ux Importance: Undecided Status: New -- 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/1471747 Title: Missing confirmation dialog when clearing browsing data Status in Ubuntu UX bugs: New Status in webbrowser-app package in Ubuntu: Confirmed Bug description: According to the UX specification (https://docs.google.com/presentation/d/1Qrd4Flfs3EH- fI79IfrYgLdAx2nce-L7ve8NKLCX324/edit#slide=id.g3583da3f4_00), when clearing browsing data (under Settings Privacy), there should be a confirmation dialog to give the user a chance to cancel the action. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1471747/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1468664] Re: Whole session crashes after opening LibreOffice in 15.04
Chris, I am attaching my crash file. ** Attachment added: Crash file https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1468664/+attachment/4424918/+files/_usr_bin_Xorg.0.crash ** Changed in: xorg (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1468664 Title: Whole session crashes after opening LibreOffice in 15.04 Status in xorg package in Ubuntu: New Bug description: In 15.04 when opening Libreoffice I get: starting version 219 [drm:radeon_acpi_init [radeon]] *ERROR* cannot find a backlight controller and the whole session crashes. The session didn't crash in 14.04.2. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Thu Jun 25 10:26:14 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] [1002:9851] (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:381a] InstallationDate: Installed on 2015-06-20 (4 days ago) InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: LENOVO 80E3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic root=UUID=db4352a7-efc2-4393-bfe9-7804d7eb71fc ro quiet splash vt.handoff=7 SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A2CN23WW(V1.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5B2 dmi.board.vendor: LENOVO dmi.board.version: 31900058 STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-45 dmi.modalias: dmi:bvnLENOVO:bvrA2CN23WW(V1.05):bd07/08/2014:svnLENOVO:pn80E3:pvrLenovoG50-45:rvnLENOVO:rnLancer5B2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoG50-45: dmi.product.name: 80E3 dmi.product.version: Lenovo G50-45 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Sun Jun 21 09:24:57 2015 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1468664/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1462346] Re: Wrong size of folder-drag-accept/gnome-fs-directory-accept icon at zoom levels bigger than 100% in Nautilus
** Branch linked: lp:~larsu/humanity/all-sizes-for-draw-accept -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to humanity-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1462346 Title: Wrong size of folder-drag-accept/gnome-fs-directory-accept icon at zoom levels bigger than 100% in Nautilus Status in humanity-icon-theme package in Ubuntu: In Progress Bug description: Hello, the icon size of the folder-drag-accept/gnome-fs-directory-accept icon in Nautilus is too small when a zoom level bigger than 100% in the icon view is used. This can be reproduced the following way: - Start Nautilus (or Nemo) - Open a directory that contains at least one subdirectory plus at least one file (or a second subdirectory) - Switch to icon view, set a zoom level bigger than 100% - Try to move a file/directory into another directory - When the mouse moves over the target directory, it's icon will switch to the folder-drag-accept/gnome-fs-directory-accept icon, but in a version that is no larger than 48x48, even if the zoom level (and thus the icon size) is set greater. I have attached a screenshot that illustrates the problem. With the Adwaita icon theme the problem does not happen, the icon seems to get the correct size at all zoom levels. Currently the Humanity icon theme contains (as symlink) a svg file of the responsible folder-drag-accept/gnome-fs-directory-accept icon in the directories Humanity/status/24 and Humanity/48. The dirs for bigger icons (e.g. 128) do not contain that icons, so I assumed it may be a quick fix to symlink them to also to those dirs. But that caused just other problems - now the icons had always the 128x128 size regardless of zoom level and was often too big instead of too small! A way to fix this seems to be to place png files of the icons in all of the Humanity/status/[icon size]-directories, each png scaled to the appropriate size. That is a bit more hassle but seems to work for the Adwaita theme. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: humanity-icon-theme 0.6.8 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jun 5 10:53:39 2015 InstallationDate: Installed on 2015-04-16 (49 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150415) PackageArchitecture: all SourcePackage: humanity-icon-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1462346/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471680] [NEW] there is no copy and paste options when long pressing the number in dialer
Public bug reported: current build number: 47 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-06 05:43:41 version version: 47 version ubuntu: 20150706 version device: 20150701-cdd791c version custom: 20150602-731-5-32 Steps: 1.open the dialer app 2.input some numbers 3.long press the numbers Expectations: After step3#,the numbers should be chosen and there will be two options: copy,select Actual result: after step3#, there is nothing appears ** Affects: dialer-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1471680 Title: there is no copy and paste options when long pressing the number in dialer Status in dialer-app package in Ubuntu: New Bug description: current build number: 47 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-06 05:43:41 version version: 47 version ubuntu: 20150706 version device: 20150701-cdd791c version custom: 20150602-731-5-32 Steps: 1.open the dialer app 2.input some numbers 3.long press the numbers Expectations: After step3#,the numbers should be chosen and there will be two options: copy,select Actual result: after step3#, there is nothing appears To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1471680/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471720] Re: package libgstreamer-plugins-base1.0-0 1.2.4-1~ubuntu1 failed to install/upgrade: 28.4211:package libgstreamer-plugins-base1.0-0:amd64 is not ready for configuration
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1471720 Title: package libgstreamer-plugins-base1.0-0 1.2.4-1~ubuntu1 failed to install/upgrade: 28.4211:package libgstreamer-plugins-base1.0-0:amd64 is not ready for configuration cannot configure (current status `half-installed') Status in gst-plugins-base1.0 package in Ubuntu: New Bug description: got this error during upgrade ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libgstreamer-plugins-base1.0-0 1.2.4-1~ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Mon Jul 6 17:11:38 2015 DuplicateSignature: package:libgstreamer-plugins-base1.0-0:1.2.4-1~ubuntu1:28.4211:package libgstreamer-plugins-base1.0-0:amd64 is not ready for configuration cannot configure (current status `half-installed') ErrorMessage: 28.4211:package libgstreamer-plugins-base1.0-0:amd64 is not ready for configuration cannot configure (current status `half-installed') InstallationDate: Installed on 2014-10-23 (256 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: gst-plugins-base1.0 Title: package libgstreamer-plugins-base1.0-0 1.2.4-1~ubuntu1 failed to install/upgrade: 28.4211:package libgstreamer-plugins-base1.0-0:amd64 is not ready for configuration cannot configure (current status `half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base1.0/+bug/1471720/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471705] [NEW] when playing path wind , press the volume down to silience, but after playing a while , we can still hear the sound
Public bug reported: current build number: 47 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-06 05:43:41 version version: 47 version ubuntu: 20150706 version device: 20150701-cdd791c version custom: 20150602-731-5-32 Steps: 1.open the path wind app 2.play the game , turn off the music by pressing down the volume key to zero 3.continue playing the game Expectation: as long as i play this game without quiting, there shouldn't be any sound Actual result: After playing this game a while , the sound appears again automaticly ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1471705 Title: when playing path wind , press the volume down to silience, but after playing a while ,we can still hear the sound Status in pulseaudio package in Ubuntu: New Bug description: current build number: 47 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-06 05:43:41 version version: 47 version ubuntu: 20150706 version device: 20150701-cdd791c version custom: 20150602-731-5-32 Steps: 1.open the path wind app 2.play the game , turn off the music by pressing down the volume key to zero 3.continue playing the game Expectation: as long as i play this game without quiting, there shouldn't be any sound Actual result: After playing this game a while , the sound appears again automaticly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1471705/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471706] [NEW] when playing path wind , press the volume down to silience, but after playing a while , we can still hear the sound
*** This bug is a duplicate of bug 1471705 *** https://bugs.launchpad.net/bugs/1471705 Public bug reported: current build number: 47 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-06 05:43:41 version version: 47 version ubuntu: 20150706 version device: 20150701-cdd791c version custom: 20150602-731-5-32 Steps: 1.open the path wind app 2.play the game , turn off the music by pressing down the volume key to zero 3.continue playing the game Expectation: as long as i play this game without quiting, there shouldn't be any sound Actual result: After playing this game a while , the sound appears again automaticly ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1471706 Title: when playing path wind , press the volume down to silience, but after playing a while ,we can still hear the sound Status in pulseaudio package in Ubuntu: New Bug description: current build number: 47 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-06 05:43:41 version version: 47 version ubuntu: 20150706 version device: 20150701-cdd791c version custom: 20150602-731-5-32 Steps: 1.open the path wind app 2.play the game , turn off the music by pressing down the volume key to zero 3.continue playing the game Expectation: as long as i play this game without quiting, there shouldn't be any sound Actual result: After playing this game a while , the sound appears again automaticly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1471706/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471706] Re: when playing path wind , press the volume down to silience, but after playing a while , we can still hear the sound
*** This bug is a duplicate of bug 1471705 *** https://bugs.launchpad.net/bugs/1471705 ** This bug has been marked a duplicate of bug 1471705 when playing path wind , press the volume down to silience, but after playing a while ,we can still hear the sound -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1471706 Title: when playing path wind , press the volume down to silience, but after playing a while ,we can still hear the sound Status in pulseaudio package in Ubuntu: New Bug description: current build number: 47 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-06 05:43:41 version version: 47 version ubuntu: 20150706 version device: 20150701-cdd791c version custom: 20150602-731-5-32 Steps: 1.open the path wind app 2.play the game , turn off the music by pressing down the volume key to zero 3.continue playing the game Expectation: as long as i play this game without quiting, there shouldn't be any sound Actual result: After playing this game a while , the sound appears again automaticly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1471706/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1396768] Re: pcre3 vulnerability CVE-2014-8964
** Description changed: + SRU Justification + + [Impact] + + CVE-2014-8964 + + [Test Case] + + [Regression Potential] + + [Other Info] + https://security-tracker.debian.org/tracker/CVE-2014-8964 https://bugzilla.redhat.com/show_bug.cgi?id=1166147 http://bugs.exim.org/show_bug.cgi?id=1546 Requires some heavy backporting to older releases, see: https://bugzilla.redhat.com/show_bug.cgi?id=1166147#c2. ** Changed in: pcre3 (Ubuntu Trusty) Status: New = In Progress ** Changed in: pcre3 (Ubuntu Trusty) Assignee: (unassigned) = Seyeong Kim (xtrusia) ** Patch added: trusty-cve-2014-8964.debdiff https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1396768/+attachment/4424951/+files/trusty-cve-2014-8964.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcre3 in Ubuntu. https://bugs.launchpad.net/bugs/1396768 Title: pcre3 vulnerability CVE-2014-8964 Status in pcre3 package in Ubuntu: Confirmed Status in pcre3 source package in Precise: New Status in pcre3 source package in Trusty: In Progress Status in pcre3 source package in Utopic: New Bug description: SRU Justification [Impact] CVE-2014-8964 [Test Case] [Regression Potential] [Other Info] https://security-tracker.debian.org/tracker/CVE-2014-8964 https://bugzilla.redhat.com/show_bug.cgi?id=1166147 http://bugs.exim.org/show_bug.cgi?id=1546 Requires some heavy backporting to older releases, see: https://bugzilla.redhat.com/show_bug.cgi?id=1166147#c2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1396768/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471709] [NEW] Dialer app does not pop up answering panel for incoming call
Public bug reported: This is a random symptom, I have no reproduction hints yet. It happens 2-3 times a week (BQ Aquaris, Ubuntu 15.04 updated with OTA): Prerequisites: The phone is in active status (display open, no fading, no sleeping) EVENT before: 1. Incoming call rings the call sound EXPECTED: - The phone pops up an incoming bubble so that user could answer or reject the incoming call. HAPPENED: - The phone does not pop up any bubble to answer incoming Tried to swipe to dialer, but it shows the initial state (inactive call button, no phone number in the entry field). So no way to answer the call. One can find the missed call in the recent list. WORKAROUND: Rebooting the device solves the problem. ** Affects: dialer-app (Ubuntu) Importance: Undecided Status: New ** Tags: answer incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1471709 Title: Dialer app does not pop up answering panel for incoming call Status in dialer-app package in Ubuntu: New Bug description: This is a random symptom, I have no reproduction hints yet. It happens 2-3 times a week (BQ Aquaris, Ubuntu 15.04 updated with OTA): Prerequisites: The phone is in active status (display open, no fading, no sleeping) EVENT before: 1. Incoming call rings the call sound EXPECTED: - The phone pops up an incoming bubble so that user could answer or reject the incoming call. HAPPENED: - The phone does not pop up any bubble to answer incoming Tried to swipe to dialer, but it shows the initial state (inactive call button, no phone number in the entry field). So no way to answer the call. One can find the missed call in the recent list. WORKAROUND: Rebooting the device solves the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1471709/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1123347] Re: Zeitgeist using too much RAM memory
I'm using Ubuntu 14.04 and zeitgeist-fts uses 1.6 GB of RAM memory! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeitgeist in Ubuntu. https://bugs.launchpad.net/bugs/1123347 Title: Zeitgeist using too much RAM memory Status in zeitgeist package in Ubuntu: Confirmed Bug description: zeitgeist is using 30% of 8GB of RAM. Seems like way too much. PID TTY STAT TIME MAJFL TRS DRS RSS %MEM COMMAND 2245 ?Sl 0:21 2 312 2719715 2485852 30.5 /usr/lib/zeitgeist/zeitgeist-fts ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: zeitgeist-core 0.9.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-5.10-generic 3.8.0-rc6 Uname: Linux 3.8.0-5-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Date: Tue Feb 12 12:49:49 2013 ExecutablePath: /usr/lib/zeitgeist/zeitgeist-fts InstallationDate: Installed on 2012-04-07 (311 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328) MarkForUpload: True ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR=set PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: zeitgeist UpgradeStatus: Upgraded to raring on 2013-02-11 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1123347/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471609] Re: Cannot unlock phone in landscape
This might be a dupe of the one I reported for the tablet, but I'll leave it open as it happening on the phone makes it more critical. Daniel, feel free to mark the other one as dupe if so. ** Changed in: unity8 (Ubuntu) Assignee: (unassigned) = Daniel d'Andrada (dandrader) ** Changed in: unity8 (Ubuntu) Importance: Undecided = Critical -- 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/1471609 Title: Cannot unlock phone in landscape Status in unity8 package in Ubuntu: New Bug description: Under some circumstances it's possible to have the phone locked, with some of the numbers for pin-unlock being off-screen, and thus untouchable. See screenshot. In this instance it's impossible to unlock the phone if your pin contains those off-screen digits. The only way out is to reboot the phone. The shell should probably rotate in lock screen and the digits should be on screen when in landscape. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1471609/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1442512] Re: Apport-kde crash when reporting bugs
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apport (Ubuntu Vivid) Status: New = Confirmed -- 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/1442512 Title: Apport-kde crash when reporting bugs Status in Apport crash detection/reporting: Confirmed Status in apport package in Ubuntu: Triaged Status in apport source package in Vivid: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with version 2.17-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/1b2e1c9cdac684074f5f97db85ae78c1b8a2b3ac contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1442512/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1396768] Re: pcre3 vulnerability CVE-2014-8964
** Changed in: pcre3 (Ubuntu Utopic) Status: New = In Progress ** Changed in: pcre3 (Ubuntu Utopic) Assignee: (unassigned) = Seyeong Kim (xtrusia) ** Patch added: utopic-cve-2014-8964.debdiff https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1396768/+attachment/4424961/+files/utopic-cve-2014-8964.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcre3 in Ubuntu. https://bugs.launchpad.net/bugs/1396768 Title: pcre3 vulnerability CVE-2014-8964 Status in pcre3 package in Ubuntu: Confirmed Status in pcre3 source package in Precise: New Status in pcre3 source package in Trusty: In Progress Status in pcre3 source package in Utopic: In Progress Bug description: SRU Justification [Impact] CVE-2014-8964 [Test Case] [Regression Potential] [Other Info] https://security-tracker.debian.org/tracker/CVE-2014-8964 https://bugzilla.redhat.com/show_bug.cgi?id=1166147 http://bugs.exim.org/show_bug.cgi?id=1546 Requires some heavy backporting to older releases, see: https://bugzilla.redhat.com/show_bug.cgi?id=1166147#c2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1396768/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1469761] Re: Recent landing made desktop load the phone greeter/lock screen
confirmed resolved with the update, thanks -- 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/1469761 Title: Recent landing made desktop load the phone greeter/lock screen Status in unity8 package in Ubuntu: Fix Released Bug description: Using wily desktop, unity8 used to show a desktop greeter with a password entry, since 8.10+15.10.20150616.1-0ubuntu1 it's showing the phone greeter instead Corresponding upload https://launchpad.net/ubuntu/+source/unity8/8.10+15.10.20150616.1-0ubuntu1 Seems like due to this change https://code.launchpad.net/~josharenson/unity8/greeter_mode/+merge/256385 WORKAROUND: 1. Swipe from the edge like the phone or move mouse to the left to reveal Launcher and click the Ubuntu logo. 2. Just type your user password and you will see dots appear in place of your password and hit 'Enter'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1469761/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1303249] Re: Indicator-datetime doesn't show evolution/eds calendar color for all-day events (Trusty/Utopic/Vivid)
Khurshid, the part you quoted I wrote in January 2011. https://wiki.ubuntu.com/TimeAndDate?action=diffrev2=17rev1=16 I meant that the icon should be in the same color, in the menu, as its calendar is in Evolution. That would help distinguish items with the same title, but it wouldn't be a complete solution, because the colors might be similar, and some people are color-blind. Please report a separate bug on that. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1303249 Title: Indicator-datetime doesn't show evolution/eds calendar color for all- day events (Trusty/Utopic/Vivid) Status in indicator-datetime package in Ubuntu: Confirmed Bug description: It used to show respective calendar color from evolution for all-day events clock/alarm icon for events with time. But with latest update, it seems it has stopped showing evolution calendar color for all-day events in indicator-datetime. However alarm/clock icon still appears as usual. I have attached a screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1303249/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1468130] Re: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene:11:Change:QVector:resize:pop:QAbstractItemModel::endMoveRows
This seems to happen in shapeTextureHigh in UITK. ** Package changed: qtdeclarative-opensource-src (Ubuntu) = ubuntu-ui- toolkit (Ubuntu) -- 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/1468130 Title: /usr/lib/arm-linux- gnueabihf/qt5/bin/qmlscene:11:Change:QVector:resize:pop:QAbstractItemModel::endMoveRows Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding qtdeclarative-opensource-src. This problem was most recently seen with version 5.4.2-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/8cb1515635eda3760f6f6921d5418aa7eb454352 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1468130/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471716] [NEW] counting down can not be stopped in camera app after taping power key .
Public bug reported: system-image-cli -i current build number: 56 device name: krillin plast update: 2015-07-06 04:16:52 version version: 56 version ubuntu: 20150703 version device: 20150529-8e13c5f version custom: 20150528-722-29-15-vivid step by step 1. Open camera app 2.Set counting down to 15s /5s 3.Tap camera key 4.Tap power key during counting down 5.Tap power key again. Expected result After step 5, Counting down stopped. Actual result After step 5, Counting down can not be stopped. ** Affects: camera-app (Ubuntu) Importance: Undecided Status: New -- 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/1471716 Title: counting down can not be stopped in camera app after taping power key . Status in camera-app package in Ubuntu: New Bug description: system-image-cli -i current build number: 56 device name: krillin plast update: 2015-07-06 04:16:52 version version: 56 version ubuntu: 20150703 version device: 20150529-8e13c5f version custom: 20150528-722-29-15-vivid step by step 1. Open camera app 2.Set counting down to 15s /5s 3.Tap camera key 4.Tap power key during counting down 5.Tap power key again. Expected result After step 5, Counting down stopped. Actual result After step 5, Counting down can not be stopped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1471716/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471720] [NEW] package libgstreamer-plugins-base1.0-0 1.2.4-1~ubuntu1 failed to install/upgrade: 28.4211:package libgstreamer-plugins-base1.0-0:amd64 is not ready for configurati
Public bug reported: got this error during upgrade ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libgstreamer-plugins-base1.0-0 1.2.4-1~ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Mon Jul 6 17:11:38 2015 DuplicateSignature: package:libgstreamer-plugins-base1.0-0:1.2.4-1~ubuntu1:28.4211:package libgstreamer-plugins-base1.0-0:amd64 is not ready for configuration cannot configure (current status `half-installed') ErrorMessage: 28.4211:package libgstreamer-plugins-base1.0-0:amd64 is not ready for configuration cannot configure (current status `half-installed') InstallationDate: Installed on 2014-10-23 (256 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: gst-plugins-base1.0 Title: package libgstreamer-plugins-base1.0-0 1.2.4-1~ubuntu1 failed to install/upgrade: 28.4211:package libgstreamer-plugins-base1.0-0:amd64 is not ready for configuration cannot configure (current status `half-installed') UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gst-plugins-base1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package dist-upgrade trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1471720 Title: package libgstreamer-plugins-base1.0-0 1.2.4-1~ubuntu1 failed to install/upgrade: 28.4211:package libgstreamer-plugins-base1.0-0:amd64 is not ready for configuration cannot configure (current status `half-installed') Status in gst-plugins-base1.0 package in Ubuntu: New Bug description: got this error during upgrade ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libgstreamer-plugins-base1.0-0 1.2.4-1~ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Mon Jul 6 17:11:38 2015 DuplicateSignature: package:libgstreamer-plugins-base1.0-0:1.2.4-1~ubuntu1:28.4211:package libgstreamer-plugins-base1.0-0:amd64 is not ready for configuration cannot configure (current status `half-installed') ErrorMessage: 28.4211:package libgstreamer-plugins-base1.0-0:amd64 is not ready for configuration cannot configure (current status `half-installed') InstallationDate: Installed on 2014-10-23 (256 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: gst-plugins-base1.0 Title: package libgstreamer-plugins-base1.0-0 1.2.4-1~ubuntu1 failed to install/upgrade: 28.4211:package libgstreamer-plugins-base1.0-0:amd64 is not ready for configuration cannot configure (current status `half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base1.0/+bug/1471720/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1467609] Re: vibrations on MSI gt72 2qe scren
I tried to upgrade bios. placing the files on a (FAT) USB pen drive, going in the bios menu and selecting bios upgrade I got a wrong file format ?? it also takes ages to boot when I plug in my pen drive. (usually more than two minutes) I tried to follow the instruction of putting EFI files on the pen drive and booting from it but I just can't boot when the pen drive is plugged in, blocked on the MSI screen with my keyboard blinking (blue or green). It took me more than two hours to check everything and try, again and again. next part : $ sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date E1781IMS.10H 11/21/2014 I will try to upgrade bios again … -- 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/1467609 Title: vibrations on MSI gt72 2qe scren Status in xorg package in Ubuntu: Incomplete Bug description: bought it last week, GPU is NVidia Ge Force 980M. With nouveau installed I only use the small intel chipset ; I installed nvidia 352 from their site, and it works good for the external screen I have but now the integrated screen has those problems. The description is, like the front of the screen was vibrating. I think a better term could be used, see attached screenshot. As you can notice, lines are shifted to left/right on several positions of the screen. It makes the use of the screen very unpleasant. So I usually switch it off. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 352.21 Tue Jun 9 21:53:31 PDT 2015 GCC version: gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jun 22 18:40:33 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.19.0-15-generic, x86_64: installed bbswitch, 0.7, 3.19.0-21-generic, x86_64: installed nvidia-352, 352.21, 3.19.0-21-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GM204M [GeForce GTX 980M] [10de:13d7] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1129] InstallationDate: Installed on 2015-06-19 (2 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: Micro-Star International Co., Ltd. GT72 2QE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic root=UUID=4fabaada-02c5-4230-a634-0b88cf228b5f ro quiet splash SourcePackage: xorg Symptom: display UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1781IMS.10H dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1781 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10H:bd11/21/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: GT72 2QE dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.61+git20150614.97be70b4-0ubuntu0ricotz~vivid version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.0~git20150616+10.6.5d327b37-0ubuntu0ricotz~vivid version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.0~git20150616+10.6.5d327b37-0ubuntu0ricotz~vivid version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.99+git20150521.d64a13eb-0ubuntu0ricotz~vivid version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150528.fb1643f0-0ubuntu0sarvatt~vivid version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11+git20150528.27234dbe-0ubuntu0sarvatt~vivid xserver.bootTime: Mon Jun 22 18:11:59 2015 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log
[Touch-packages] [Bug 1462841] Re: window spread causes system logout
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1462841 Title: window spread causes system logout Status in Unity: New Status in unity package in Ubuntu: Confirmed Bug description: Expect to happen: -window spread upon super w - no intempestive logout when tweaking window spread with the unity-tweak-tool What happened instead: -After installing unity tweak, turning ON the window spread caused a system logout when I clicked on any icon with multiple windows open. -A logout also happens if hot corners is enabled with the action set to window spread, and the mouse pointer directed to the preset hot corner. -A logout also happened when i press super-w but in an unpredictable manner (super w sometimes have the desired effect without logout) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-tweak-tool 0.0.6ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jun 8 09:49:51 2015 InstallationDate: Installed on 2013-08-29 (647 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) PackageArchitecture: all SourcePackage: unity-tweak-tool UpgradeStatus: Upgraded to trusty on 2015-04-20 (48 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1462841/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447169] Re: [notifications] Swipe to remove phone notifications should not use Delete
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity8 (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1447169 Title: [notifications] Swipe to remove phone notifications should not use Delete Status in Ubuntu UX bugs: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: Ubuntu phone notifications 14.10 (r21) When you swipe right to remove a notification it indicates a dustbin icon and says delete - this is confusing as you think it may delete the message or email. You don't really talk of deleting notifications. It should say Clear like it does for the Clear All below the notifications, because all you are doing is clearing the notification. The icon should also be changed from a dustbin to a check mark of some sort. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1447169/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1462841] Re: window spread causes system logout
I have the same issue, + 1 to disabling window spread in unity tweak tools: solves the problem (at the expense of having no window spread) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1462841 Title: window spread causes system logout Status in Unity: New Status in unity package in Ubuntu: Confirmed Bug description: Expect to happen: -window spread upon super w - no intempestive logout when tweaking window spread with the unity-tweak-tool What happened instead: -After installing unity tweak, turning ON the window spread caused a system logout when I clicked on any icon with multiple windows open. -A logout also happens if hot corners is enabled with the action set to window spread, and the mouse pointer directed to the preset hot corner. -A logout also happened when i press super-w but in an unpredictable manner (super w sometimes have the desired effect without logout) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-tweak-tool 0.0.6ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jun 8 09:49:51 2015 InstallationDate: Installed on 2013-08-29 (647 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) PackageArchitecture: all SourcePackage: unity-tweak-tool UpgradeStatus: Upgraded to trusty on 2015-04-20 (48 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1462841/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1359486] Re: Use LibreOffice Dialogs setting is ignored in KDE
cleary, thanks for the info! Repository size: 1.1 GiB (52.62%) of 2.0 GiB - yes, there are no free space to create builds for other versions of Ubuntu, but I use 14.10 :( Will wait when this will be officially fixed in Ubuntu packages... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1359486 Title: Use LibreOffice Dialogs setting is ignored in KDE Status in LibreOffice Productivity Suite: Won't Fix Status in libreoffice package in Ubuntu: Confirmed Status in qt4-x11 package in Ubuntu: Confirmed Bug description: Kubuntu 14.04 (KDE Desktop Environment) [update] This is now affecting packages from main ubuntu (trusty) repositories: libreoffice Version: 4.2.8-0ubuntu2 0 qt4-x11 Version: 4:4.8.5+git192-g085f851+dfsg-2ubuntu4.1 [/update] LibreOffice uses it's native filepicker/save dialogs, regardless of whether the config option Use LibreOffice Dialogs is ticked or not. Related Bugs: https://bugreports.qt-project.org/browse/QTBUG-38585 https://bugreports.qt-project.org/browse/QTBUG-34614 According to the LO team, both these bugs have patches that address the automatic disabling of Qt dialogs at runtime (if buggy Qt is detected.) Initial report/discussion on LO bugtracker (now closed) here: https://bugs.freedesktop.org/show_bug.cgi?id=82598 [obsolete] Packages from this ppa: https://launchpad.net/~libreoffice Version: 4.3.0-3ubuntu2~trusty1 (as reported by dpkg, note updated packages as of about 1 hour ago) or 4.3.0.4 Build ID: 430m0(Build:4) as reported by LibreOffice about dialog. This is a regression from 4.2.4-0ubuntu2 currently in the main ubuntu security repository. [/obsolete] To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1359486/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471790] [NEW] Audiotrak MAYA U5 not fully supported
Public bug reported: I have a problem with usb-audio Audiotrack Maya U5 on Ubuntu 14.04.2: Steps to reproduce: 1) Try to play a sound 2) You can either get a sound out of the speakers or not which is random 3) Stop the sound and wait ~5 seconds for the device to suspend (light on device stops blinking) 4) You are back at point 2 Another way to reproduce it: 1) Try to play a sound 2) If the sound is not playing open pavucontrol try to change profile between analog stereo output and digital stereo output several times until it “clicks” and you get a sound through one of this outputs With analog speakers connected sound should be playing only with analog output and it should not reset outputs upon device suspend. This problem started after I upgraded firmware from Audiotrack's website (http://audiotrack.net/en/download/421) to RELEASE 10. I tried to downgrade firmware but with no luck. Other problem is that there are no inputs – either digital, line in or microphone in pavucotrol. I tried several kernels from 3.2 to 4.1 and this bug is present at all that I tested. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-41.57~14.04.1-generic 3.16.7-ckt11 Uname: Linux 3.16.0-41-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: drkp 1515 F...m pulseaudio /dev/snd/controlC1: drkp 1515 F pulseaudio /dev/snd/controlC0: drkp 1515 F pulseaudio CurrentDesktop: Unity Date: Mon Jul 6 13:49:07 2015 InstallationDate: Installed on 2015-07-01 (4 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/19/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Q77M-D2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd04/19/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnQ77M-D2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1471790 Title: Audiotrak MAYA U5 not fully supported Status in alsa-driver package in Ubuntu: New Bug description: I have a problem with usb-audio Audiotrack Maya U5 on Ubuntu 14.04.2: Steps to reproduce: 1) Try to play a sound 2) You can either get a sound out of the speakers or not which is random 3) Stop the sound and wait ~5 seconds for the device to suspend (light on device stops blinking) 4) You are back at point 2 Another way to reproduce it: 1) Try to play a sound 2) If the sound is not playing open pavucontrol try to change profile between analog stereo output and digital stereo output several times until it “clicks” and you get a sound through one of this outputs With analog speakers connected sound should be playing only with analog output and it should not reset outputs upon device suspend. This problem started after I upgraded firmware from Audiotrack's website (http://audiotrack.net/en/download/421) to RELEASE 10. I tried to downgrade firmware but with no luck. Other problem is that there are no inputs – either digital, line in or microphone in pavucotrol. I tried several kernels from 3.2 to 4.1 and this bug is present at all that I tested. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-41.57~14.04.1-generic 3.16.7-ckt11 Uname: Linux 3.16.0-41-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: drkp 1515 F...m pulseaudio /dev/snd/controlC1: drkp 1515 F pulseaudio /dev/snd/controlC0: drkp 1515 F pulseaudio CurrentDesktop: Unity Date: Mon Jul 6 13:49:07 2015 InstallationDate: Installed on 2015-07-01 (4 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh
[Touch-packages] [Bug 1471783] [NEW] poppler-data package is missing on devices' image
Public bug reported: On the ubuntu-phone mailing list[1] has been reported an issue about the libpoppler rendering. Any attempt to load the following document: http://www.math.sci.osaka-u.ac.jp/~msj-si-2015/msj_si_2015_schedule.pdf Results in a badly rendered document on the phone (at the first time it was reported for a Bq E4.5, but it's reproducible on any device - personally verified with a Nexus 5). Testing the same document on a PC, using Document Viewer and other PDF viewer based on the Poppler library, everything is ok. After a check of the installed packages, both on device and on desktop, and after a search on Google for the error returned in the application log[2], it seemed that the issue was due to a suggested dependency missing on Ubuntu devices (poppler-data). By removing that package on my desktop, I am able to reproduce this issue with any viewer. What I'd suggest is to add the poppler-data package in the device system image. I mark this bug as critical for Document Viewer, since we may want to support all the possible PDF documents and the package is default on dekstop image. This issue affects also all the third party application that use libpoppler to render PDF documents (e.g. Beru, which includes a PDF viewer), and may be even more relevant. === [1] https://lists.launchpad.net/ubuntu-phone/msg13932.html [2] http://paste.ubuntu.com/11830506/ ** Affects: ubuntu-docviewer-app Importance: Critical Status: Triaged ** Affects: ubuntu-touch-meta (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-docviewer-app Importance: Undecided Status: New ** Changed in: ubuntu-docviewer-app Status: New = Triaged ** Changed in: ubuntu-docviewer-app Importance: Undecided = Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1471783 Title: poppler-data package is missing on devices' image Status in Document Viewer application for Ubuntu devices: Triaged Status in ubuntu-touch-meta package in Ubuntu: New Bug description: On the ubuntu-phone mailing list[1] has been reported an issue about the libpoppler rendering. Any attempt to load the following document: http://www.math.sci.osaka-u.ac.jp/~msj-si-2015/msj_si_2015_schedule.pdf Results in a badly rendered document on the phone (at the first time it was reported for a Bq E4.5, but it's reproducible on any device - personally verified with a Nexus 5). Testing the same document on a PC, using Document Viewer and other PDF viewer based on the Poppler library, everything is ok. After a check of the installed packages, both on device and on desktop, and after a search on Google for the error returned in the application log[2], it seemed that the issue was due to a suggested dependency missing on Ubuntu devices (poppler-data). By removing that package on my desktop, I am able to reproduce this issue with any viewer. What I'd suggest is to add the poppler-data package in the device system image. I mark this bug as critical for Document Viewer, since we may want to support all the possible PDF documents and the package is default on dekstop image. This issue affects also all the third party application that use libpoppler to render PDF documents (e.g. Beru, which includes a PDF viewer), and may be even more relevant. === [1] https://lists.launchpad.net/ubuntu-phone/msg13932.html [2] http://paste.ubuntu.com/11830506/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-docviewer-app/+bug/1471783/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1077829] Re: ASUS Xonar U3 volume slider problem
I have this problem on Ubuntu 14.04 LTS, with Linux 3.18.1 (or official Ubuntu kernel), this bug is always existent 2years later? :o -- 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/1077829 Title: ASUS Xonar U3 volume slider problem Status in The Linux Kernel: New Status in alsa-driver package in Ubuntu: Confirmed Bug description: I got an ASUS Xonar U3 USB sound card for my Thinkpad T420 for my birthday this year and tried to use it on Ubuntu 12.10. Unfortunately, its sound output is either bearably noticeable or - if I increase the volume by even the slightest notch with the audio indicator - EXTREMELY loud (and, because I use earphones, pretty painfully so). I did some experiments with alsamixer, and it seems as if the complete volume range that I would expect to be stretched over the complete slider is compressed in the PCM levels between 1 and ~7. This means the only way I can sanefully use the USB sound card right now is by turning the volume in each application very, very low so that I have some amount of precision with the global volume slider (which I can control with function keys), but every time I forget this somewhere, it's a pretty painful surprise, so I hope this can be fixed. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: alsa-base 1.0.25+dfsg-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Mon Nov 12 08:19:30 2012 InstallationDate: Installed on 2012-09-09 (63 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: USB Advanced Audio Device - USB Advanced Audio Device Symptom_Type: Volume slider, or mixer problems Title: [USB-Audio - USB Advanced Audio Device, playback] volume slider problem UpgradeStatus: Upgraded to quantal on 2012-10-18 (24 days ago) dmi.bios.date: 06/12/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET70WW (1.40 ) dmi.board.asset.tag: Not Available dmi.board.name: 4180PH1 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr83ET70WW(1.40):bd06/12/2012:svnLENOVO:pn4180PH1:pvrThinkPadT420:rvnLENOVO:rn4180PH1:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4180PH1 dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1077829/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1470750] Re: scoperegistry uses 45% CPU after applying updates from the store, draining battery quickly
I have seen this happening in OTA-4 krillin. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1470750 Title: scoperegistry uses 45% CPU after applying updates from the store, draining battery quickly Status in the base for Ubuntu mobile products: Confirmed Status in unity-scopes-api package in Ubuntu: Confirmed Bug description: current build number: 44 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-02 07:10:44 version version: 44 version ubuntu: 20150702 version device: 20150608-6e66f3c version custom: 20150602-731-5-32 Suddenly this morning, the battery started discharging very quickly, 'top' revealed that scoperegistry was using around 45% CPU steadily. PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 2207 phablet 20 0 377996 9576 6200 S 46,0 0,5 67:34.54 scoperegistry Around the same time that the battery started dropping, I applied all the updates from the store, in the list of apps to update were: - Terminal - BBC Sport - BBC - Euronews - Engadget - Cnet I pressed 'Update all' and waited until it's done then closed system- settings. There is no crash file corresponding to this event. I reproduced it on ubuntu-touch/rc-proposed/bq-aquaris.en/krillin #55 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1470750/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1241986] Re: Cannot connect to WPA/WPA2, EAP-PEAP, MSCHAPV2 network
** Branch linked: lp:~jonas-drange/ubuntu-system-settings/handle-ssid- bssid -- 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/1241986 Title: Cannot connect to WPA/WPA2, EAP-PEAP, MSCHAPV2 network Status in the base for Ubuntu mobile products: In Progress Status in indicator-network package in Ubuntu: New Status in network-manager package in Ubuntu: Triaged Status in ubuntu-system-settings package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: New Bug description: On Ubuntu for Phones final image on mako I can see a network but cannot connect because I never get prompted for the username/password. https://wiki.ubuntu.com/Networking#wi-fi-authentication-variations: In both the ‘Connect to “{network name}”’ and “Connect to Hidden Network” dialogs, the contents of the dialog, and the behavior of the “Connect” button, should vary depending on the security and authentication methods... To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1241986/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1466273] Re: gstreamer fails intermittently
It may be that the process is swapped out, so the delivery of the SIGKILL takes a while for it to be swapped back in and to hence get the signal. To test this hypothesis: a) one could disable swap and see if the process can be delivered the SIGKILL and how quickly it responds to that. However, turning swap off may cause the OOM killer to change the way things behave and hence is not a viable test pattern. b) run smemstat (from ppa:colin-king/white) and see how much memory of the given blocked process is swapped out compared to the memory resident. If it is mostly swapped out, it could indicate why it is taken a while to get swapped back in and to respond to the SIGKILL. c) one could add a mlockall() to the slow responding process or even mlock() on the range of text pages that handle the signal and do the ppoll so it's not swapped out. Note that one needs to allow the process to have the CAP_IPC_LOCK capability or one could tweak the RLIMIT_MEMLOCK soft limit using ulimit -l -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1466273 Title: gstreamer fails intermittently Status in Thumbnail generator for all kinds of files: New Status in gstreamer1.0 package in Ubuntu: New Bug description: gstreamer occasionally fails to extract a thumbnail from a video file. It's clearly a race condition because, almost all of the time, it succeeds. To reproduce: Check out the thumbnailer/devel branch at r217 and build it. Then: cd build/src/vs-thumb ./vs-thumb fd://0 ./x.jpg ../../../tests/media/testvideo.ogg Point a browser at the generated x.jpg file and check that the image was extracted correctly. Now run while ./vs-thumb fd://0 ./x.jpg ../../../tests/media/testvideo.ogg ; do :; done Within maybe a hundred iterations or so, I get: Error creating thumbnail: ThumbnailExtractor: change_state(): reading async messages: GStreamer error: negotiation problem. To manage notifications about this bug go to: https://bugs.launchpad.net/thumbnailer/+bug/1466273/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471783] Re: poppler-data package is missing on devices' image
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-touch-meta (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1471783 Title: poppler-data package is missing on devices' image Status in Document Viewer application for Ubuntu devices: Triaged Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: On the ubuntu-phone mailing list[1] has been reported an issue about the libpoppler rendering. Any attempt to load the following document: http://www.math.sci.osaka-u.ac.jp/~msj-si-2015/msj_si_2015_schedule.pdf Results in a badly rendered document on the phone (at the first time it was reported for a Bq E4.5, but it's reproducible on any device - personally verified with a Nexus 5). Testing the same document on a PC, using Document Viewer and other PDF viewer based on the Poppler library, everything is ok. After a check of the installed packages, both on device and on desktop, and after a search on Google for the error returned in the application log[2], it seemed that the issue was due to a suggested dependency missing on Ubuntu devices (poppler-data). By removing that package on my desktop, I am able to reproduce this issue with any viewer. What I'd suggest is to add the poppler-data package in the device system image. I mark this bug as critical for Document Viewer, since we may want to support all the possible PDF documents and the package is default on dekstop image. This issue affects also all the third party application that use libpoppler to render PDF documents (e.g. Beru, which includes a PDF viewer), and may be even more relevant. === [1] https://lists.launchpad.net/ubuntu-phone/msg13932.html [2] http://paste.ubuntu.com/11830506/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-docviewer-app/+bug/1471783/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1462489] Re: Allow apps to keep the screen on
What templates should this be for? Seems at least ubuntu-sdk and ubuntu- webapp. Should scopes also have this ability? -- 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/1462489 Title: Allow apps to keep the screen on Status in the base for Ubuntu mobile products: Confirmed Status in apparmor-easyprof-ubuntu package in Ubuntu: Confirmed Status in qtsystems-opensource-src package in Ubuntu: In Progress Status in qtubuntu package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Status in qtsystems-opensource-src package in Ubuntu RTM: New Bug description: Support an interface in QML and HTML to allow an app to keep the screen on while the app is active. This has come up in several scenarios, such as an ebook reader, a clock in night mode. First step is to hook up QtSystemInfo screenSaverEnabled One solution to inhibit the screen blanking: Add a new dbus rule to the default template Provide a mediator (unity8) to control this, so it can restore the screen blanking when the app is not active or has been closed Prompt the user for confirmation the first time the app accesses it use the trust store to avoid prompts each time add to the System settings Other app access panel an entry for Screen or Display so the setting could be revoked To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1462489/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471311] Re: Calendar events dates are in wrong time format for other languages in indicator
** Also affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New ** Changed in: indicator-datetime (Ubuntu) Assignee: (unassigned) = Alejandro J. Cura (alecu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1471311 Title: Calendar events dates are in wrong time format for other languages in indicator Status in the base for Ubuntu mobile products: New Status in indicator-datetime package in Ubuntu: New Bug description: The calendar event dates aren't in the right format. See the attached screenshot, the date should be júl. 11., szo 08.00 instead of this. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1471311/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1387691] Re: Media Player should not be visible in the app scope and launcher
This bug was fixed in the package mediaplayer-app 0.20.5+15.04.20150701-0ubuntu1 in https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/stable-phone-overlay --- mediaplayer-app (0.20.5+15.04.20150701-0ubuntu1) vivid; urgency=medium [ Bill Filler ] * use OnlyShowIn=Old to hide from Apps scope (LP: #1387691) [ Renato Araujo Oliveira Filho ] * Fixed slider positioning. (LP: #1470331) mediaplayer-app (0.20.5+15.10.20150630-0ubuntu1) wily; urgency=medium [ Renato Araujo Oliveira Filho ] * Updated app icon. (LP: #1457424) mediaplayer-app (0.20.5+15.10.20150522-0ubuntu1) wily; urgency=medium [ Jim Hodapp ] * Quit playback after fatal playback error. (LP: #1435088) mediaplayer-app (0.20.5+15.04.20150428-0ubuntu1) vivid; urgency=medium [ CI Train Bot ] * Resync trunk. [ Ricardo Mendoza ] * Bug #1417006 Performance/Rendering fixes: * Remove clipping on video loader * Remove unused rectangles (overdraw) (LP: #1417006) -- CI Train Bot ci-train-...@canonical.com Wed, 01 Jul 2015 21:53:38 + ** Changed in: mediaplayer-app (Ubuntu RTM) Status: Invalid = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1387691 Title: Media Player should not be visible in the app scope and launcher Status in the base for Ubuntu mobile products: In Progress Status in Ubuntu UX bugs: Fix Committed Status in mediaplayer-app package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Invalid Status in url-dispatcher package in Ubuntu: Fix Released Status in mediaplayer-app package in Ubuntu RTM: Fix Released Status in url-dispatcher package in Ubuntu RTM: Invalid Bug description: The mediaplayer is an 'auxiliary app' in the current design approach. That means that its purpouse it playback media launched by other apps (e.g Messaging) or scopes (e.g. Videos). It should not be launched from the App scopes. However, the 'Update' section System Settings should still display it when an update to mediaplayer is available. Current behaviour - Mediaplayer app displayed in App Scope, Launcher and Settings Desired behaviour - Mediaplayer app not displayed in App Scope or Launcher - Mediaplayer displayed in Settings Update To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1387691/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471311] Re: Calendar event dates are in wrong time format for other languages in indicator
** Summary changed: - Calendar events dates are in wrong time format for other languages in indicator + Calendar event dates are in wrong time format for other languages in indicator -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1471311 Title: Calendar event dates are in wrong time format for other languages in indicator Status in the base for Ubuntu mobile products: New Status in indicator-datetime package in Ubuntu: New Bug description: The calendar event dates aren't in the right format. See the attached screenshot, the date should be júl. 11., szo 08.00 instead of this. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1471311/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471803] [NEW] Mouse not detected
Public bug reported: Microsoft Intellimouse 3.0 is connected but is not being detected. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic i686 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: i386 CurrentDesktop: LXDE Date: Mon Jul 6 22:29:09 2015 InstallationDate: Installed on 2013-01-04 (913 days ago) InstallationMedia: Lubuntu 12.04 Precise Pangolin - Release i386 (20120423) SourcePackage: xorg UpgradeStatus: Upgraded to vivid on 2015-06-27 (9 days ago) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 third-party-packages vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1471803 Title: Mouse not detected Status in xorg package in Ubuntu: New Bug description: Microsoft Intellimouse 3.0 is connected but is not being detected. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic i686 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: i386 CurrentDesktop: LXDE Date: Mon Jul 6 22:29:09 2015 InstallationDate: Installed on 2013-01-04 (913 days ago) InstallationMedia: Lubuntu 12.04 Precise Pangolin - Release i386 (20120423) SourcePackage: xorg UpgradeStatus: Upgraded to vivid on 2015-06-27 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1471803/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1470235] Re: PolicyKit high memory usage
A couple more data points: Last week, I rebooted my machine and logged in right away. polkitd was only using 7 MB of memory: $ ps aux | grep polkitd | grep -v grep root 1219 0.1 0.0 281164 7244 ?Sl 16:36 0:00 /usr/lib/policykit-1/polkitd --no-debug Two days later, polkitd was using only marginally more memory: $ uptime 17:08:55 up 2 days, 32 min, 2 users, load average: 1.42, 0.78, 0.37 $ ps aux | grep polkitd | grep -v grep root 1219 0.0 0.0 291208 7664 ?Sl Jun30 0:00 /usr/lib/policykit-1/polkitd --no-debug On Friday, I installed updates and then rebooted without logging in. This morning, before logging in, polkitd was already using nearly 1 GB of memory: $ uptime 09:09:38 up 3 days, 15:57, 1 user, load average: 0.06, 0.05, 0.05 $ ps aux | grep polkitd | grep -v grep root 1034 0.4 11.2 1137788 912732 ? Sl Jul02 23:23 /usr/lib/policykit-1/polkitd --no-debug $ date Mon Jul 6 09:11:17 EDT 2015 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1470235 Title: PolicyKit high memory usage Status in policykit-1 package in Ubuntu: Confirmed Bug description: Periodically I install updates on my computer and reboot without logging in. When I come back to my computer and log in, polkitd is using a large chunk of memory. At the moment it's using 2.3 GiB of memory on a machine with 8 GB RAM: $ ps aux | grep polkit root 1229 0.4 29.8 2652532 2420916 ? Sl Jun19 67:38 /usr/lib/policykit-1/polkitd --no-debug Killing the process frees the memory until I reboot again. I'm currently using the latest version of policykit-1: $ apt-file search /usr/lib/policykit-1/polkitd policykit-1: /usr/lib/policykit-1/polkitd $ apt-cache policy policykit-1 policykit-1: Installed: 0.105-4ubuntu2.14.04.1 Candidate: 0.105-4ubuntu2.14.04.1 Version table: *** 0.105-4ubuntu2.14.04.1 0 500 http://ca.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.105-4ubuntu2 0 500 http://ca.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages $ sudo apt-get upgrade policykit-1 Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done policykit-1 is already the newest version. Other information: $ lsb_release -rd Description: Ubuntu 14.04.2 LTS Release: 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: policykit-1 0.105-4ubuntu2.14.04.1 ProcVersionSignature: Ubuntu 3.16.0-41.55~14.04.1-generic 3.16.7-ckt11 Uname: Linux 3.16.0-41-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Tue Jun 30 16:14:51 2015 InstallationDate: Installed on 2014-08-25 (309 days ago) InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140723) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: policykit-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1470235/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471806] [NEW] package libtiff5:i386 4.0.3-7ubuntu0.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configura
Public bug reported: Got an error while trying to update. Don't really know much else about it. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libtiff5:i386 4.0.3-7ubuntu0.3 ProcVersionSignature: Ubuntu 3.16.0-41.57~14.04.1-generic 3.16.7-ckt11 Uname: Linux 3.16.0-41-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Mon Jul 6 06:33:50 2015 DpkgHistoryLog: Start-Date: 2015-07-06 06:33:38 Commandline: aptdaemon role='role-commit-packages' sender=':1.87' Upgrade: postgresql-9.3:amd64 (9.3.8-0ubuntu0.4.04, 9.3.9-0ubuntu0.14.04), xserver-xorg-video-intel-lts-utopic:amd64 (2.99.914-1~exp1ubuntu4.2~trusty1, 2.99.914-1~exp1ubuntu4.3~trusty1), postgresql-contrib-9.3:amd64 (9.3.8-0ubuntu0.4.04, 9.3.9-0ubuntu0.14.04), postgresql-client-9.3:amd64 (9.3.8-0ubuntu0.4.04, 9.3.9-0ubuntu0.14.04), libpq5:amd64 (9.3.8-0ubuntu0.4.04, 9.3.9-0ubuntu0.14.04) DuplicateSignature: package:libtiff5:i386:4.0.3-7ubuntu0.3:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2015-05-26 (41 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) PackageArchitecture: i386 SourcePackage: tiff Title: package libtiff5:i386 4.0.3-7ubuntu0.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: tiff (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1471806 Title: package libtiff5:i386 4.0.3-7ubuntu0.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in tiff package in Ubuntu: New Bug description: Got an error while trying to update. Don't really know much else about it. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libtiff5:i386 4.0.3-7ubuntu0.3 ProcVersionSignature: Ubuntu 3.16.0-41.57~14.04.1-generic 3.16.7-ckt11 Uname: Linux 3.16.0-41-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Mon Jul 6 06:33:50 2015 DpkgHistoryLog: Start-Date: 2015-07-06 06:33:38 Commandline: aptdaemon role='role-commit-packages' sender=':1.87' Upgrade: postgresql-9.3:amd64 (9.3.8-0ubuntu0.4.04, 9.3.9-0ubuntu0.14.04), xserver-xorg-video-intel-lts-utopic:amd64 (2.99.914-1~exp1ubuntu4.2~trusty1, 2.99.914-1~exp1ubuntu4.3~trusty1), postgresql-contrib-9.3:amd64 (9.3.8-0ubuntu0.4.04, 9.3.9-0ubuntu0.14.04), postgresql-client-9.3:amd64 (9.3.8-0ubuntu0.4.04, 9.3.9-0ubuntu0.14.04), libpq5:amd64 (9.3.8-0ubuntu0.4.04, 9.3.9-0ubuntu0.14.04) DuplicateSignature: package:libtiff5:i386:4.0.3-7ubuntu0.3:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2015-05-26 (41 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) PackageArchitecture: i386 SourcePackage: tiff Title: package libtiff5:i386 4.0.3-7ubuntu0.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1471806/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1387691] Re: Media Player should not be visible in the app scope and launcher
** Branch linked: lp:ubuntu/wily-proposed/mediaplayer-app -- 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/1387691 Title: Media Player should not be visible in the app scope and launcher Status in the base for Ubuntu mobile products: In Progress Status in Ubuntu UX bugs: Fix Committed Status in mediaplayer-app package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Invalid Status in url-dispatcher package in Ubuntu: Fix Released Status in mediaplayer-app package in Ubuntu RTM: Fix Released Status in url-dispatcher package in Ubuntu RTM: Invalid Bug description: The mediaplayer is an 'auxiliary app' in the current design approach. That means that its purpouse it playback media launched by other apps (e.g Messaging) or scopes (e.g. Videos). It should not be launched from the App scopes. However, the 'Update' section System Settings should still display it when an update to mediaplayer is available. Current behaviour - Mediaplayer app displayed in App Scope, Launcher and Settings Desired behaviour - Mediaplayer app not displayed in App Scope or Launcher - Mediaplayer displayed in Settings Update To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1387691/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1470331] Re: the progress bar not start from very begining place when play form 0:00:00
** Branch linked: lp:ubuntu/wily-proposed/mediaplayer-app -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediaplayer-app in Ubuntu. https://bugs.launchpad.net/bugs/1470331 Title: the progress bar not start from very begining place when play form 0:00:00 Status in mediaplayer-app package in Ubuntu: In Progress Bug description: system-image-cli -i current build number: 41 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-01 10:28:01 version version: 41 version ubuntu: 20150630 version device: 20150608-6e66f3c version custom: 20150602-731-5-32 reproduce steps: 1.play a video by mediaplayer 2.when start play from 0:00:00 the progress begin to move expect result: 1.the progress bar should start from the very begining place when play from :0:00:00 actually result; the progress bar not start form the very begining place. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mediaplayer-app/+bug/1470331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471806] Re: package libtiff5:i386 4.0.3-7ubuntu0.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurati
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1471806 Title: package libtiff5:i386 4.0.3-7ubuntu0.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in tiff package in Ubuntu: New Bug description: Got an error while trying to update. Don't really know much else about it. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libtiff5:i386 4.0.3-7ubuntu0.3 ProcVersionSignature: Ubuntu 3.16.0-41.57~14.04.1-generic 3.16.7-ckt11 Uname: Linux 3.16.0-41-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Mon Jul 6 06:33:50 2015 DpkgHistoryLog: Start-Date: 2015-07-06 06:33:38 Commandline: aptdaemon role='role-commit-packages' sender=':1.87' Upgrade: postgresql-9.3:amd64 (9.3.8-0ubuntu0.4.04, 9.3.9-0ubuntu0.14.04), xserver-xorg-video-intel-lts-utopic:amd64 (2.99.914-1~exp1ubuntu4.2~trusty1, 2.99.914-1~exp1ubuntu4.3~trusty1), postgresql-contrib-9.3:amd64 (9.3.8-0ubuntu0.4.04, 9.3.9-0ubuntu0.14.04), postgresql-client-9.3:amd64 (9.3.8-0ubuntu0.4.04, 9.3.9-0ubuntu0.14.04), libpq5:amd64 (9.3.8-0ubuntu0.4.04, 9.3.9-0ubuntu0.14.04) DuplicateSignature: package:libtiff5:i386:4.0.3-7ubuntu0.3:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2015-05-26 (41 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) PackageArchitecture: i386 SourcePackage: tiff Title: package libtiff5:i386 4.0.3-7ubuntu0.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tiff/+bug/1471806/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1470750] Re: scoperegistry uses 45% CPU after applying updates from the store, draining battery quickly
** Branch linked: lp:~stolowski/unity-scopes-api/revert-delayed-removal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1470750 Title: scoperegistry uses 45% CPU after applying updates from the store, draining battery quickly Status in the base for Ubuntu mobile products: Confirmed Status in unity-scopes-api package in Ubuntu: Confirmed Bug description: current build number: 44 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-02 07:10:44 version version: 44 version ubuntu: 20150702 version device: 20150608-6e66f3c version custom: 20150602-731-5-32 Suddenly this morning, the battery started discharging very quickly, 'top' revealed that scoperegistry was using around 45% CPU steadily. PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 2207 phablet 20 0 377996 9576 6200 S 46,0 0,5 67:34.54 scoperegistry Around the same time that the battery started dropping, I applied all the updates from the store, in the list of apps to update were: - Terminal - BBC Sport - BBC - Euronews - Engadget - Cnet I pressed 'Update all' and waited until it's done then closed system- settings. There is no crash file corresponding to this event. I reproduced it on ubuntu-touch/rc-proposed/bq-aquaris.en/krillin #55 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1470750/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471747] Re: Missing confirmation dialog when clearing browsing data
** Changed in: webbrowser-app (Ubuntu) Status: Confirmed = In Progress ** Changed in: webbrowser-app (Ubuntu) Assignee: (unassigned) = Olivier Tilloy (osomon) -- 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/1471747 Title: Missing confirmation dialog when clearing browsing data Status in Ubuntu UX bugs: New Status in webbrowser-app package in Ubuntu: In Progress Bug description: According to the UX specification (https://docs.google.com/presentation/d/1Qrd4Flfs3EH- fI79IfrYgLdAx2nce-L7ve8NKLCX324/edit#slide=id.g3583da3f4_00), when clearing browsing data (under Settings Privacy), there should be a confirmation dialog to give the user a chance to cancel the action. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1471747/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471747] Re: Missing confirmation dialog when clearing browsing data
** Branch linked: lp:~osomon/webbrowser-app/clear-browsing-data-confirm- dialog -- 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/1471747 Title: Missing confirmation dialog when clearing browsing data Status in Ubuntu UX bugs: New Status in webbrowser-app package in Ubuntu: In Progress Bug description: According to the UX specification (https://docs.google.com/presentation/d/1Qrd4Flfs3EH- fI79IfrYgLdAx2nce-L7ve8NKLCX324/edit#slide=id.g3583da3f4_00), when clearing browsing data (under Settings Privacy), there should be a confirmation dialog to give the user a chance to cancel the action. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1471747/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1470750] Re: scoperegistry uses 45% CPU after applying updates from the store, draining battery quickly
Ok, we've narrowed this issue down to a single change we made to delay notifying the dash when a scope is removed. Makes sense that it was triggered upon uninstalling a scope. A fix is in the pipeline. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1470750 Title: scoperegistry uses 45% CPU after applying updates from the store, draining battery quickly Status in the base for Ubuntu mobile products: Confirmed Status in unity-scopes-api package in Ubuntu: Confirmed Bug description: current build number: 44 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-02 07:10:44 version version: 44 version ubuntu: 20150702 version device: 20150608-6e66f3c version custom: 20150602-731-5-32 Suddenly this morning, the battery started discharging very quickly, 'top' revealed that scoperegistry was using around 45% CPU steadily. PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 2207 phablet 20 0 377996 9576 6200 S 46,0 0,5 67:34.54 scoperegistry Around the same time that the battery started dropping, I applied all the updates from the store, in the list of apps to update were: - Terminal - BBC Sport - BBC - Euronews - Engadget - Cnet I pressed 'Update all' and waited until it's done then closed system- settings. There is no crash file corresponding to this event. I reproduced it on ubuntu-touch/rc-proposed/bq-aquaris.en/krillin #55 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1470750/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471633] Re: Display Error
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a regular (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1471633 Title: Display Error Status in xorg package in Ubuntu: New Bug description: Could you please find this issue. I do not know if this is bug or hardware problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Jul 6 10:46:25 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7788] InstallationDate: Installed on 2015-06-25 (10 days ago) InstallationMedia: It MachineType: MSI MS-7788 ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) LANG=en_PH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic root=UUID=6e853639-c518-4298-873b-85f73833ffda ro vesafb.invalid=1 splash quiet nopat plymouth:debug=1=1=1 vt.handoff=7 SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V3.6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-P31/W8 (MS-7788) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.6:bd09/29/2013:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P31/W8(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7788 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Sun Jul 5 23:16:48 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1471633/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471590] Re: package python2.7-minimal 2.7.6-8ubuntu0.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1471590 Title: package python2.7-minimal 2.7.6-8ubuntu0.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 Status in python2.7 package in Ubuntu: New Bug description: bug ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python2.7-minimal 2.7.6-8ubuntu0.2 ProcVersionSignature: Ubuntu 3.13.0-54.91-generic 3.13.11-ckt20 Uname: Linux 3.13.0-54-generic i686 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: i386 Date: Sun Jul 5 15:44:23 2015 DuplicateSignature: package:python2.7-minimal:2.7.6-8ubuntu0.2:subprocess installed post-installation script returned error exit status 127 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationDate: Installed on 2011-06-06 (1490 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: python2.7 Title: package python2.7-minimal 2.7.6-8ubuntu0.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: Upgraded to trusty on 2014-09-20 (288 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1471590/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471459] Re: Launching nano with sudo creates a root owned directory in $HOME
** Changed in: nano (Ubuntu) Status: Invalid = New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1471459 Title: Launching nano with sudo creates a root owned directory in $HOME Status in nano package in Ubuntu: New Bug description: If nano is started with sudo then a root owned directory .nano is created i a user's $HOME directory. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: nano 2.4.1-1 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.3-0ubuntu4 Architecture: amd64 Date: Sat Jul 4 20:06:16 2015 InstallationDate: Installed on 2015-02-25 (128 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Alpha amd64 (20150224) SourcePackage: nano UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1471459/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471598] Re: Autopilot tests on Krillin run in windowed mode
Why is it low? It broke all autopilot tests. All. Not only the unity8 but all the UITK and all the project. There is a workaround to locally force the Staged mode when tests are run, but for people who are validating MR with running AP tests it is far from obvious. -- 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/1471598 Title: Autopilot tests on Krillin run in windowed mode Status in unity8 package in Ubuntu: Confirmed Bug description: The autopilot tests on Krillin run in windowed mode. I don't think this should ever happen on that form factor. See also a bunch of dubious errors below. Tests running... terminate called after throwing an instance of 'boost::exception_detail::clone_implboost::exception_detail::error_info_injectormir::socket_disconnected_error ' what(): Failed to send message to server: Broken pipe Failed to connect to server. Error was :Failed to connect to server socket: Connection refused (process:5172): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. /bin/bash: line 1: 5172 Terminated SUPPRESS_DEPRECATED_NOTE=yes autopilot3 run ubuntuuitoolkit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1471598/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471986] [NEW] App remains installed after clicking on Cancel Purchase
Public bug reported: While testing silo landing-006, on latest vivid, every existing refund bug seems to be fixed, but this popped up: how to reproduce: - purchase an app in the Ubuntu Store scope - within 15 minutes of purchasing, go to the app preview page in the Store scope - click on the Cancel Purchase button expected: - app gets refunded - app is uninstalled what happens: - app gets refunded - app remains installed phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 58 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-07-06 18:18:21 version version: 58 version ubuntu: 20150706.1 version device: 20150529-8e13c5f version custom: 20150528-722-29-15-vivid phablet@ubuntu-phablet:~$ dpkg -l unity-scope-click | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=-=--= ii unity-scope-click 0.1.1+15.04.20150706-0ubuntu1 armhfClick Packages Scope for Unity ** Affects: unity-scope-click (Ubuntu) Importance: Critical Assignee: Rodney Dawes (dobey) Status: New ** Changed in: unity-scope-click (Ubuntu) Importance: Undecided = Critical ** Changed in: unity-scope-click (Ubuntu) Assignee: (unassigned) = Rodney Dawes (dobey) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1471986 Title: App remains installed after clicking on Cancel Purchase Status in unity-scope-click package in Ubuntu: New Bug description: While testing silo landing-006, on latest vivid, every existing refund bug seems to be fixed, but this popped up: how to reproduce: - purchase an app in the Ubuntu Store scope - within 15 minutes of purchasing, go to the app preview page in the Store scope - click on the Cancel Purchase button expected: - app gets refunded - app is uninstalled what happens: - app gets refunded - app remains installed phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 58 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-07-06 18:18:21 version version: 58 version ubuntu: 20150706.1 version device: 20150529-8e13c5f version custom: 20150528-722-29-15-vivid phablet@ubuntu-phablet:~$ dpkg -l unity-scope-click | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=-=--= ii unity-scope-click 0.1.1+15.04.20150706-0ubuntu1 armhfClick Packages Scope for Unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1471986/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471598] Re: Autopilot uses mouse events, puts device in windowed mode
For now I'm changing the default setting in unity to stick to Staged mode. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to autopilot in Ubuntu. https://bugs.launchpad.net/bugs/1471598 Title: Autopilot uses mouse events, puts device in windowed mode Status in autopilot package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: AP tests emulating mouse to run, which puts the device into windowed mode. mouse presence is used to toggle the windowed mode on mobile devices. orig bug The autopilot tests on Krillin run in windowed mode. I don't think this should ever happen on that form factor. See also a bunch of dubious errors below. Tests running... terminate called after throwing an instance of 'boost::exception_detail::clone_implboost::exception_detail::error_info_injectormir::socket_disconnected_error ' what(): Failed to send message to server: Broken pipe Failed to connect to server. Error was :Failed to connect to server socket: Connection refused (process:5172): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. /bin/bash: line 1: 5172 Terminated SUPPRESS_DEPRECATED_NOTE=yes autopilot3 run ubuntuuitoolkit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopilot/+bug/1471598/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471598] Re: Autopilot uses mouse events, puts device in windowed mode
Actually the requirement should be to enable autopilot tests to choose different input devices. For example some function method decoration to specify which types of input devices (touchscreens, keyboards, mice..) should be plugged for a particular test. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to autopilot in Ubuntu. https://bugs.launchpad.net/bugs/1471598 Title: Autopilot uses mouse events, puts device in windowed mode Status in autopilot package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: AP tests emulating mouse to run, which puts the device into windowed mode. mouse presence is used to toggle the windowed mode on mobile devices. orig bug The autopilot tests on Krillin run in windowed mode. I don't think this should ever happen on that form factor. See also a bunch of dubious errors below. Tests running... terminate called after throwing an instance of 'boost::exception_detail::clone_implboost::exception_detail::error_info_injectormir::socket_disconnected_error ' what(): Failed to send message to server: Broken pipe Failed to connect to server. Error was :Failed to connect to server socket: Connection refused (process:5172): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. /bin/bash: line 1: 5172 Terminated SUPPRESS_DEPRECATED_NOTE=yes autopilot3 run ubuntuuitoolkit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopilot/+bug/1471598/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1470750] Re: scoperegistry uses 45% CPU after applying updates from the store, draining battery quickly
** Changed in: canonical-devices-system-image Importance: High = Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1470750 Title: scoperegistry uses 45% CPU after applying updates from the store, draining battery quickly Status in the base for Ubuntu mobile products: In Progress Status in unity-scopes-api package in Ubuntu: In Progress Bug description: current build number: 44 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-02 07:10:44 version version: 44 version ubuntu: 20150702 version device: 20150608-6e66f3c version custom: 20150602-731-5-32 Suddenly this morning, the battery started discharging very quickly, 'top' revealed that scoperegistry was using around 45% CPU steadily. PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 2207 phablet 20 0 377996 9576 6200 S 46,0 0,5 67:34.54 scoperegistry Around the same time that the battery started dropping, I applied all the updates from the store, in the list of apps to update were: - Terminal - BBC Sport - BBC - Euronews - Engadget - Cnet I pressed 'Update all' and waited until it's done then closed system- settings. There is no crash file corresponding to this event. I reproduced it on ubuntu-touch/rc-proposed/bq-aquaris.en/krillin #55 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1470750/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471459] Re: Launching nano with sudo creates a root owned directory in $HOME
Ubuntu Mate 15.10 also affected by this bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1471459 Title: Launching nano with sudo creates a root owned directory in $HOME Status in nano package in Ubuntu: Confirmed Bug description: If nano is started with sudo then a root owned directory .nano is created i a user's $HOME directory. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: nano 2.4.1-1 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.3-0ubuntu4 Architecture: amd64 Date: Sat Jul 4 20:06:16 2015 InstallationDate: Installed on 2015-02-25 (128 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Alpha amd64 (20150224) SourcePackage: nano UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1471459/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1462489] Re: Allow apps to keep the screen on
Per Pat, this is for both wily and stable-phone-overlay. -- 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/1462489 Title: Allow apps to keep the screen on Status in the base for Ubuntu mobile products: Confirmed Status in apparmor-easyprof-ubuntu package in Ubuntu: Confirmed Status in qtsystems-opensource-src package in Ubuntu: In Progress Status in qtubuntu package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Status in qtsystems-opensource-src package in Ubuntu RTM: New Bug description: Support an interface in QML and HTML to allow an app to keep the screen on while the app is active. This has come up in several scenarios, such as an ebook reader, a clock in night mode. First step is to hook up QtSystemInfo screenSaverEnabled One solution to inhibit the screen blanking: Add a new dbus rule to the default template Provide a mediator (unity8) to control this, so it can restore the screen blanking when the app is not active or has been closed Prompt the user for confirmation the first time the app accesses it use the trust store to avoid prompts each time add to the System settings Other app access panel an entry for Screen or Display so the setting could be revoked To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1462489/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1462489] Re: Allow apps to keep the screen on
We discussed this on irc. This a) should not include scopes and b) should not require a trust prompt since it will be clear that the foreground app is inhibiting the screen. If this is extended to scopes in the futures, we should revisit the trust prompt discussion. -- 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/1462489 Title: Allow apps to keep the screen on Status in the base for Ubuntu mobile products: Confirmed Status in apparmor-easyprof-ubuntu package in Ubuntu: Confirmed Status in qtsystems-opensource-src package in Ubuntu: In Progress Status in qtubuntu package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Status in qtsystems-opensource-src package in Ubuntu RTM: New Bug description: Support an interface in QML and HTML to allow an app to keep the screen on while the app is active. This has come up in several scenarios, such as an ebook reader, a clock in night mode. First step is to hook up QtSystemInfo screenSaverEnabled One solution to inhibit the screen blanking: Add a new dbus rule to the default template Provide a mediator (unity8) to control this, so it can restore the screen blanking when the app is not active or has been closed Prompt the user for confirmation the first time the app accesses it use the trust store to avoid prompts each time add to the System settings Other app access panel an entry for Screen or Display so the setting could be revoked To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1462489/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1470750] Re: scoperegistry uses 45% CPU after applying updates from the store, draining battery quickly
** Changed in: unity-scopes-api (Ubuntu) Assignee: (unassigned) = Pawel Stolowski (stolowski) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1470750 Title: scoperegistry uses 45% CPU after applying updates from the store, draining battery quickly Status in the base for Ubuntu mobile products: Confirmed Status in unity-scopes-api package in Ubuntu: Confirmed Bug description: current build number: 44 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-02 07:10:44 version version: 44 version ubuntu: 20150702 version device: 20150608-6e66f3c version custom: 20150602-731-5-32 Suddenly this morning, the battery started discharging very quickly, 'top' revealed that scoperegistry was using around 45% CPU steadily. PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 2207 phablet 20 0 377996 9576 6200 S 46,0 0,5 67:34.54 scoperegistry Around the same time that the battery started dropping, I applied all the updates from the store, in the list of apps to update were: - Terminal - BBC Sport - BBC - Euronews - Engadget - Cnet I pressed 'Update all' and waited until it's done then closed system- settings. There is no crash file corresponding to this event. I reproduced it on ubuntu-touch/rc-proposed/bq-aquaris.en/krillin #55 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1470750/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1293425] Re: 1002:6741 [Dell Vostro 3550] Display resolution keeps switching with external monitor connected
*** This bug is a duplicate of bug 907381 *** https://bugs.launchpad.net/bugs/907381 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1293425 Title: 1002:6741 [Dell Vostro 3550] Display resolution keeps switching with external monitor connected Status in xorg package in Ubuntu: Confirmed Bug description: If I use external monitor and extend my desktop to both the built-in laptop display and the external LCD, the display settings are auto- changed by the system. This may include resetting to a mirrored display at 1024x768, a single display on the laptop panel, or a single display on the external monitor. If I use just the AMD GPU via the AMD CCC, my monitors keep switching between resolutions, mirroring switches on and off every minute or so. WORKAROUND: If I switch to just the Intel GPU via the AMD GPU, or never install AMD drivers and just use the Intel GPU out-of-the-box, I can go a day without spontaneous switching of resolutions and/or mirroring displays, sometimes it happens like 2 or 3 times per day. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-35.50-generic 3.8.13.13 Uname: Linux 3.8.0-35-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Mar 17 09:36:31 2014 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:04cd] Advanced Micro Devices [AMD] nee ATI Whistler [Radeon HD 6600M/6700M/7600M Series] [1002:6741] (rev ff) (prog-if ff) InstallationDate: Installed on 2014-03-17 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: Dell Inc. Vostro 3550 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-35-generic root=UUID=d9ac2de5-de02-45d6-af39-3588757a6e61 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.vendor: Dell Inc. dmi.board.version: A11 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA11:bd08/03/2012:svnDellInc.:pnVostro3550:pvrNotSpecified:rvnDellInc.:rn:rvrA11:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 3550 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.9~daily13.06.19~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu0.1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.7-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.7-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1293425/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1447601] Re: Phone app settings are oddly in System Settings
** Also affects: ubuntu-system-settings Importance: Undecided Status: New ** Also affects: ubuntu-ux Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1447601 Title: Phone app settings are oddly in System Settings Status in Ubuntu Touch System Settings: New Status in Ubuntu UX bugs: New Status in dialer-app package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: In System Settings, most of the Phone settings are about things that happen inside, or (in the case of ringtone) when you are about to use, the Phone app. Therefore it is weird for those settings to be accessed from System Settings. Probably they should be moved to the Phone app. Implementation of this move should be coordinated with that of (private) bug 1388012. [Realized during discussion of bug 1306078.] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-settings/+bug/1447601/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1461276] Re: off-by-one in LDIF length
This bug can be closed out now in favor of just building a new package for 2.4.41, since that release is now available and includes the fix: http://www.openldap.org/software/release/changes.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1461276 Title: off-by-one in LDIF length Status in openldap package in Ubuntu: New Bug description: Would it be possible to include the patch for ITS#8003 in the next build of the 2.4.40 package? http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=patch;h=c8353f7acdec4a42f537b0d475aaae005ba72363 It fixes a bug that causes slapd to crash when the audit log is enabled and a large base64-encoded attribute is printed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1461276/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1459362] Re: DirectionalDragArea lets a long press event through when a drag is detected
Just updated my update-dda branch with the latest code drop from lp:unity8, and I’m still seeing this issue. I’m also seeing another related issue: sometimes the bottom-edge drag doesn’t trigger a long press event (i.e. no selection is shown), however it seems to leave the webview’s touch detection in an inconsistent state, where scrolling up and down with one finger results in zooming in/out, as if there was still a pending touch point that hadn’t been released. Adding an oxide task. ** Also affects: oxide Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1459362 Title: DirectionalDragArea lets a long press event through when a drag is detected Status in Oxide Webview: New Status in unity8 package in Ubuntu: Incomplete Status in webbrowser-app package in Ubuntu: New Bug description: I recently build a branch of lp:webbrowser-app with the latest code drop for DirectionalDragArea from lp:unity8. The branch is there: lp:~osomon/webbrowser-app/update-dda. The DDA is used to detect a bottom edge drag over a WebView component, and display the tabs view accordingly. This works well, but often when a drag is detected the WebView under it gets a long press event, thus triggering the selection mechanism that it implements. According to Daniel with whom I discussed the issue prior to filing this bug: Yes, the recognition parameters (and algorithm) were changed a bit. So it's perfectly possible that what you consider a long press (don't know how many milliseconds of pressed are needed for that) can happen before the DirectionalDragArea reaches a decision on whether the gesture is a directional drag gesture or not. The threshold duration for a long press to be detected by the WebView is 500ms. I’ve rebuilt my branch with DIRECTIONALDRAGAREA_DEBUG set to 1, and here is what I’m seeing when observing the issue: [DDA()] 10035 TouchBegin (id:8, state:pressed, scenePos:(268.503,917.002)) [DDA()] WaitingForTouch - Undecided [DDA()] Unowned 10072 TouchUpdate (id:8, state:moved, scenePos:(268.503,917.002)) [DDA()] Sill within composition window. Let's wait more. [DDA()] Unowned 10089 TouchUpdate (id:8, state:moved, scenePos:(268.503,917.002)) [DDA()] Sill within composition window. Let's wait more. [DDA()] Unowned 10106 TouchUpdate (id:8, state:moved, scenePos:(268.503,917.002)) [DDA()] movedFarEnoughAlongGestureAxis: scalarProjection=0, distanceThreshold=15.748 [DDA()] Didn't move far enough yet. Let's wait more. [DDA()] Unowned 10123 TouchUpdate (id:8, state:moved, scenePos:(267.006,911.008)) [DDA()] movedFarEnoughAlongGestureAxis: scalarProjection=2.05677, distanceThreshold=15.748 [DDA()] Didn't move far enough yet. Let's wait more. [DDA()] Unowned 10139 TouchUpdate (id:8, state:moved, scenePos:(267.505,891.706)) [DDA()] movedFarEnoughAlongGestureAxis: scalarProjection=21.3591, distanceThreshold=15.748 [DDA()] grabbing touch [DDA()] Undecided - Recognized [DDA()] 10150 TouchUpdate (id:8, state:moved, scenePos:(267.505,891.706)) [DDA()] 10186 TouchUpdate (id:8, state:moved, scenePos:(268.503,845.866)) [DDA()] 10215 TouchUpdate (id:8, state:moved, scenePos:(270.853,799.68)) [DDA()] 10238 TouchUpdate (id:8, state:moved, scenePos:(271.996,774.151)) [DDA()] 10248 TouchUpdate (id:8, state:moved, scenePos:(272.212,747.697)) [DDA()] 10260 TouchUpdate (id:8, state:moved, scenePos:(274.196,721.618)) [DDA()] 10288 TouchUpdate (id:8, state:moved, scenePos:(275.736,663.346)) [DDA()] 10345 TouchUpdate (id:8, state:moved, scenePos:(278.203,582.836)) [DDA()] 10465 TouchUpdate (id:8, state:moved, scenePos:(280.481,432.403)) [DDA()] 10483 TouchUpdate (id:8, state:moved, scenePos:(281.486,382.402)) [DDA()] 10501 TouchUpdate (id:8, state:moved, scenePos:(282.613,359.847)) [DDA()] 10522 TouchUpdate (id:8, state:moved, scenePos:(283.838,335.342)) [DDA()] 10532 TouchUpdate (id:8, state:moved, scenePos:(284.972,311.133)) [DDA()] 10545 TouchUpdate (id:8, state:moved, scenePos:(286.124,288.236)) [DDA()] 10590 TouchUpdate (id:8, state:moved, scenePos:(287.307,265.747)) [DDA()] 10600 TouchUpdate (id:8, state:moved, scenePos:(288.466,228.588)) [DDA()] 10601 TouchEnd (id:8, state:released, scenePos:(288.466,228.588)) [DDA()] Recognized - WaitingForTouch Let me know if I can provide more useful information. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1459362/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471848] [NEW] Autopilot always wants to emulate Nexus10 on desktop for UITK gallery tests
Public bug reported: I get a lot of failures like this: Traceback (most recent call last): File /home/tim/dev/ubuntu-ui-toolkit/m/multiColumnHeader/tests/autopilot/ubuntuuitoolkit/tests/gallery/__init__.py, line 54, in setUp self.resize_window() File /home/tim/dev/ubuntu-ui-toolkit/m/multiColumnHeader/tests/autopilot/ubuntuuitoolkit/tests/gallery/__init__.py, line 77, in resize_window Eventually(Equals((self.app_width, self.app_height File /usr/lib/python3/dist-packages/testtools/testcase.py, line 423, in assertThat raise mismatch_error testtools.matchers._impl.MismatchError: After 10.0 seconds test failed: (1280, 800) != (1280, 776) because my screen resolution is not high enough to emulate Nexus10. Those scenarios should only be executed when the screen resolution is sufficient. ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New -- 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/1471848 Title: Autopilot always wants to emulate Nexus10 on desktop for UITK gallery tests Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: I get a lot of failures like this: Traceback (most recent call last): File /home/tim/dev/ubuntu-ui-toolkit/m/multiColumnHeader/tests/autopilot/ubuntuuitoolkit/tests/gallery/__init__.py, line 54, in setUp self.resize_window() File /home/tim/dev/ubuntu-ui-toolkit/m/multiColumnHeader/tests/autopilot/ubuntuuitoolkit/tests/gallery/__init__.py, line 77, in resize_window Eventually(Equals((self.app_width, self.app_height File /usr/lib/python3/dist-packages/testtools/testcase.py, line 423, in assertThat raise mismatch_error testtools.matchers._impl.MismatchError: After 10.0 seconds test failed: (1280, 800) != (1280, 776) because my screen resolution is not high enough to emulate Nexus10. Those scenarios should only be executed when the screen resolution is sufficient. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1471848/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1444840] Re: MMS wrongly reported as sent or not received
@alfonso - is this something you know you fixed? Or does the report rely on SIMs, etc that BQ used? ** Changed in: canonical-devices-system-image Status: Confirmed = Fix Committed ** Changed in: canonical-devices-system-image Assignee: Canonical Phone Foundations (canonical-phonedations-team) = (unassigned) ** Changed in: canonical-devices-system-image Milestone: ww24-2015 = ww28-2015 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-download-manager in Ubuntu. https://bugs.launchpad.net/bugs/1444840 Title: MMS wrongly reported as sent or not received Status in the base for Ubuntu mobile products: Fix Committed Status in nuntium package in Ubuntu: Confirmed Status in ubuntu-download-manager package in Ubuntu: Confirmed Bug description: I tried to send an MMS. It took a bit longer than usual (~1 minute). While doing it I was checking the list of open contexts with list- context ofono script. The MMS IP context was opened at a point, but then it was closed, and messaging app still reported it was sending the MMS for 30 or more seconds. In the end messaging app showed reported success sending. The message never arrived. However, I sent another MMS right after that and that one was sent in just a few seconds and was received on the other end. Taking a look at ~/.cache/upstart/dbus.log I see this error for the penultimate MMS sent: E0416 06:55:58.113751 11223 file_upload.cpp:345] Upload ID{ e685ebedf31046ada4300c8b3113c07f } http://www.pepephone.com ERROR::Network error ContentNotFoundError: the remote content was not found at the server (similar to HTTP error 404) This points to this error not being propagated to messaging app somewhat. Maybe nuntium is not the culprit here, but I did not know where to report this, so please add to the right project. Logs attached in tarball. krillin / RTM proposed image 270 The same error (ContentNotFoundError) can be also seen when *receiving* an MMS, when *uploading* the confirmation of MMS received to the server. The MMS is never shown as received. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1444840/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 964580] Re: Icons of currently installing applications should go to Software Center installation screen when selected in the launcher
As described in bug 676453, the Launcher icon is supposed to fill up as the installation completes. This would make clear that the app is not launchable yet. Even if it didn't, launching Ubuntu Software Center to its screen for the app would not be useful in this case. There's nothing useful to do there in this situation. ** Changed in: ayatana-design Status: New = Invalid ** Changed in: unity Status: Incomplete = Invalid ** Changed in: software-center (Ubuntu) Status: Incomplete = Invalid ** No longer affects: ayatana-design ** Changed in: unity (Ubuntu) Status: Incomplete = Invalid ** Changed in: software-center (Ubuntu) Assignee: (unassigned) = Matthew Paul Thomas (mpt) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/964580 Title: Icons of currently installing applications should go to Software Center installation screen when selected in the launcher Status in Unity: Invalid Status in software-center package in Ubuntu: Invalid Status in unity package in Ubuntu: Invalid Bug description: A new behaviour of Unity 5.8 is to animatedly move the icon of an application being installed in the Software Center to the dash. This is quite a good idea but it falls apart when clicking on said icon doesn't actually do anything during installation. While installing, it should go to the installation progress page of the Software Center. When the installation is complete, it should launch the application instead. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/964580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471866] [NEW] /usr/bin/unity8:11:google::protobuf::internal::Mutex::Lock:MutexLock:google::protobuf::internal::OnShutdown:google::protobuf::internal::FunctionClosure0::Run:googl
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity8. This problem was most recently seen with version 8.10+15.10.20150618-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/6dd79ceb66dc9064311bc33ccfd5351784198bb1 contains more details. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: vivid wily -- 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/1471866 Title: /usr/bin/unity8:11:google::protobuf::internal::Mutex::Lock:MutexLock:google::protobuf::internal::OnShutdown:google::protobuf::internal::FunctionClosure0::Run:google::protobuf::GoogleOnceInitImpl Status in unity8 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity8. This problem was most recently seen with version 8.10+15.10.20150618-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/6dd79ceb66dc9064311bc33ccfd5351784198bb1 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1471866/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471865] [NEW] /usr/bin/mediascanner-service-2.0:11:magazine_chain_pop_head:thread_memory_magazine1_alloc:g_slice_alloc:g_slice_alloc0:g_type_create_instance
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding mediascanner2. This problem was most recently seen with version 0.105+15.10.20150604-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/2e01b62d802a47b91e0afe45ae6723ba25e8fee5 contains more details. ** Affects: mediascanner2 (Ubuntu) Importance: Undecided Status: New ** Tags: rtm-14.09 vivid wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediascanner2 in Ubuntu. https://bugs.launchpad.net/bugs/1471865 Title: /usr/bin/mediascanner- service-2.0:11:magazine_chain_pop_head:thread_memory_magazine1_alloc:g_slice_alloc:g_slice_alloc0:g_type_create_instance Status in mediascanner2 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding mediascanner2. This problem was most recently seen with version 0.105+15.10.20150604-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/2e01b62d802a47b91e0afe45ae6723ba25e8fee5 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1471865/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1463430] Re: Clock app crashes when renabling an alarm
From IRC: nik90 john-mcaleely: regarding bug https://bugs.launchpad.net/ubuntu-clock-app/+bug/1463430, it has been fixed in the SDK MP linked, but not released. I am afraid you will have to check with the sdk developers. ubot5 Launchpad bug 1463430 in ubuntu-ui-toolkit (Ubuntu) Clock app crashes when renabling an alarm [Critical,Confirmed] john-mcaleely nik90, aha, thank you -- 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/1463430 Title: Clock app crashes when renabling an alarm Status in the base for Ubuntu mobile products: New Status in QT Ubuntu: Invalid Status in Clock application for Ubuntu devices: Confirmed Status in qtbase-opensource-src package in Ubuntu: Invalid Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: It seems clock app crashes when reenabling an alarm that just went off. Steps to reproduce the bug: 1. Set an alarm to ring in +1 or +2 minutes 2. Let it ring. 3. Dismiss it 4. Switch back to clock app and then renable that alarm What happens (sometimes) Clock app crashes Out of 10-11 tries, I was able to reproduce the crash only once on my N4 running ubuntu-touch/rc-proposed/ubuntu-developer image #1. phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 1 device name: mako channel: ubuntu-touch/rc-proposed/ubuntu-developer last update: 2015-06-03 16:58:46 version version: 1 version ubuntu: 20150602 version device: 20150210 version custom: 20150508-685-1-11 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1463430/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471890] Re: cacheSizeHint computation for webapps is incorrect due to apparmor denials
Tentatively added an apparmor-easyprof-ubuntu task (although I’m not really sure what the way forward is to fix this bug). ** Changed in: webbrowser-app (Ubuntu) Status: New = Confirmed ** Changed in: webbrowser-app (Ubuntu) Importance: Undecided = High ** Changed in: webbrowser-app (Ubuntu) Assignee: (unassigned) = Olivier Tilloy (osomon) -- 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/1471890 Title: cacheSizeHint computation for webapps is incorrect due to apparmor denials Status in apparmor-easyprof-ubuntu package in Ubuntu: New Status in webbrowser-app package in Ubuntu: Confirmed Bug description: Since http://bazaar.launchpad.net/~phablet-team/webbrowser- app/trunk/revision/1019, the webapp container (and all other embedders using an Ubuntu WebView) dynamically computes the cache size hint based on the available disk space. This doesn’t work in the general case, when the app is confined by apparmor, because the computation relies on QStorageInfo::bytesAvailable() (http://doc.qt.io/qt-5/qstorageinfo.html#bytesAvailable), which triggers apparmor denials: Jul 6 18:34:07 ubuntu-phablet kernel: [17458.604265]type=1400 audit(1436200447.375:184): apparmor=DENIED operation=open profile=com.ubuntu.developer.webapps.webapp-amazon-int_webapp-amazon_1.0.10 name=/proc/7424/mounts pid=7424 comm=webapp-containe requested_mask=r denied_mask=r fsuid=32011 ouid=32011 Jul 6 18:34:07 ubuntu-phablet kernel: [17458.604407]type=1400 audit(1436200447.375:185): apparmor=DENIED operation=open profile=com.ubuntu.developer.webapps.webapp-amazon-int_webapp-amazon_1.0.10 name=/dev/disk/by-label/ pid=7424 comm=webapp-containe requested_mask=r denied_mask=r fsuid=32011 ouid=0 This essentially means that the computation of the cache size hint is broken. It has also been reported that this breaks other apps’ functionality: https://lists.launchpad.net/ubuntu-phone/msg13622.html. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor-easyprof-ubuntu/+bug/1471890/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1463430] Re: Clock app crashes when renabling an alarm
It has been approved and waiting for landing into trunk. We prepared the MR against trunk in case we are asked to do a super critical landing, so it got obsolete from staging landing :/ Sorry for the pickup, it'll be included in the next toolkit landing. -- 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/1463430 Title: Clock app crashes when renabling an alarm Status in the base for Ubuntu mobile products: In Progress Status in QT Ubuntu: Invalid Status in Clock application for Ubuntu devices: Confirmed Status in qtbase-opensource-src package in Ubuntu: Invalid Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: It seems clock app crashes when reenabling an alarm that just went off. Steps to reproduce the bug: 1. Set an alarm to ring in +1 or +2 minutes 2. Let it ring. 3. Dismiss it 4. Switch back to clock app and then renable that alarm What happens (sometimes) Clock app crashes Out of 10-11 tries, I was able to reproduce the crash only once on my N4 running ubuntu-touch/rc-proposed/ubuntu-developer image #1. phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 1 device name: mako channel: ubuntu-touch/rc-proposed/ubuntu-developer last update: 2015-06-03 16:58:46 version version: 1 version ubuntu: 20150602 version device: 20150210 version custom: 20150508-685-1-11 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1463430/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471602] Re: Google Docs print not working on CUPS
** Summary changed: - Google Docs print not working on CUPs + Google Docs print not working on CUPS -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1471602 Title: Google Docs print not working on CUPS Status in cups package in Ubuntu: New Bug description: HP Color LaserJet 2600N prints majority of files fine from Google, PDFs etc. Example job of uploaded Word doc, converted to Google Doc then printed to CUPs doesn't print and there are no errors in the logs from the print job. Current configuration answering questions from https://wiki.ubuntu.com/DebuggingPrintingProblems : Ubuntu 14.04 LTS root@kiki:/sataTBpool/GeneralShare# uname -a Linux kiki 3.13.0-55-generic #94-Ubuntu SMP Thu Jun 18 00:27:10 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux root@kiki:/sataTBpool/GeneralShare# lsb_release -rd Description:Ubuntu 14.04.2 LTS Release:14.04 Printer Model: HP Color LaserJet 2600n Error log attached separately for viewing. No errors found in my reviews of the logs. Job 158 is the prime example that I am attaching here on this situation not working. Input file is copied from /var/spool/cups. root@kiki:/sataTBpool/GeneralShare# file d00158-001 d00158-001: PDF document, version 1.7 If I run pdftops from Attempts to send this directly using unfiltered printing doesn't work or psdebug or raw or changing the default renderer. If I install the pdftops, pstops and pstopdf files from poppler-utils and run them like this: pdftops filein filein.ps pstops filein.ps filein-new.ps pstopdf filein-new.ps filein-new.pdf Then this PDF prints fine. Also if I install the hp-plugin driver it works fine. How can we fix this so this PDF can print successfully when sent through CUPS standard suite? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.2-0ubuntu1.6 ProcVersionSignature: Ubuntu 3.13.0-55.94-generic 3.13.11-ckt20 Uname: Linux 3.13.0-55-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Sun Jul 5 15:52:19 2015 InstallationDate: Installed on 2015-01-17 (168 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.3) Lpstat: device for Color_lj2600n_kiki: socket://192.168.69.60 device for ColorLaserJet-HPPlugin: hp:/net/HP_Color_LaserJet_2600n?ip=192.168.69.60 device for HP_LaserJet_1200_kiki: hp:/usb/HP_LaserJet_1200?serial=00CNBQ127192 Lsusb: Bus 001 Device 003: ID 1058:1100 Western Digital Technologies, Inc. Bus 001 Device 002: ID 1058:1001 Western Digital Technologies, Inc. External Hard Disk [Elements] Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: NVIDIA MCP55S Papersize: letter PpdFiles: Color_lj2600n_kiki: HP Color LaserJet 2600n Foomatic/foo2hp (recommended) ColorLaserJet-HPPlugin: HP Color LaserJet 2600n, hpcups 3.14.3, requires proprietary plugin HP_LaserJet_1200_kiki: HP LaserJet 1200 - CUPS+Gutenprint v5.2.10-pre2 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-55-generic root=/dev/mapper/hostname--vg-root ro SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/15/2007 dmi.bios.vendor: ARIMA CORPORATION. dmi.bios.version: NM46X 1.08 dmi.board.name: MCP55S dmi.board.vendor: NVIDIA dmi.board.version: REFERENCE dmi.chassis.asset.tag: N/A dmi.chassis.type: 23 dmi.chassis.vendor: AMD dmi.chassis.version: N/A dmi.modalias: dmi:bvnARIMACORPORATION.:bvrNM46X1.08:bd11/15/2007:svnNVIDIA:pnMCP55S:pvrREFERENCE:rvnNVIDIA:rnMCP55S:rvrREFERENCE:cvnAMD:ct23:cvrN/A: dmi.product.name: MCP55S dmi.product.version: REFERENCE dmi.sys.vendor: NVIDIA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1471602/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1470331] Re: the progress bar not start from very begining place when play form 0:00:00
** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Importance: Undecided = High ** Changed in: canonical-devices-system-image Status: New = Fix Released ** Changed in: canonical-devices-system-image Milestone: None = ww28-2015 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediaplayer-app in Ubuntu. https://bugs.launchpad.net/bugs/1470331 Title: the progress bar not start from very begining place when play form 0:00:00 Status in the base for Ubuntu mobile products: Fix Released Status in mediaplayer-app package in Ubuntu: Fix Released Bug description: system-image-cli -i current build number: 41 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-07-01 10:28:01 version version: 41 version ubuntu: 20150630 version device: 20150608-6e66f3c version custom: 20150602-731-5-32 reproduce steps: 1.play a video by mediaplayer 2.when start play from 0:00:00 the progress begin to move expect result: 1.the progress bar should start from the very begining place when play from :0:00:00 actually result; the progress bar not start form the very begining place. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1470331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471459] Re: Launching nano with sudo creates a root owned directory in $HOME
Changed to confirmed as two users affected, me and one other. Please ignore comment #2. ** Changed in: nano (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1471459 Title: Launching nano with sudo creates a root owned directory in $HOME Status in nano package in Ubuntu: Confirmed Bug description: If nano is started with sudo then a root owned directory .nano is created i a user's $HOME directory. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: nano 2.4.1-1 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.3-0ubuntu4 Architecture: amd64 Date: Sat Jul 4 20:06:16 2015 InstallationDate: Installed on 2015-02-25 (128 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Alpha amd64 (20150224) SourcePackage: nano UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1471459/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471736] Re: Xorg freeze
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a regular (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1471736 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: fires x -server ati radeon x260 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-41.57~14.04.1-generic 3.16.7-ckt11 Uname: Linux 3.16.0-41-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: X-Cinnamon Date: Mon Jul 6 12:59:30 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: No GpuHangFrequency: I don't know GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] [1002:683d] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e244] InstallationDate: Installed on 2015-05-19 (47 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-41-generic root=UUID=78b0b1ac-9887-40b9-851c-0aad32632288 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88X-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF6:bd04/09/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88X-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Jul 6 12:58:52 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1471736/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471598] Re: Autopilot tests on Krillin run in windowed mode
ok, i misunderstood - i thot you were running in windowed mode on purpose or something. After some further discussion: understanding is that AP is emulating mouse events unfortunately for convergence, mouse events is precisely the trigger for windowed mode so need to find a solution for AP that can work in the presence of converged code base. ** Changed in: unity8 (Ubuntu) Importance: Low = Medium ** Also affects: autopilot (Ubuntu) Importance: Undecided Status: New ** Changed in: autopilot (Ubuntu) Importance: Undecided = High ** Changed in: unity8 (Ubuntu) Importance: Medium = High ** Changed in: autopilot (Ubuntu) Status: New = Confirmed ** Summary changed: - Autopilot tests on Krillin run in windowed mode + Autopilot uses mouse events, puts device in windowed mode ** Description changed: - The autopilot tests on Krillin run in windowed mode. I don't think this - should ever happen on that form factor. + AP tests emulating mouse to run, which puts the device into windowed mode. + mouse presence is used to toggle the windowed mode on mobile devices. + + orig bug + The autopilot tests on Krillin run in windowed mode. I don't think this should ever happen on that form factor. See also a bunch of dubious errors below. Tests running... terminate called after throwing an instance of 'boost::exception_detail::clone_implboost::exception_detail::error_info_injectormir::socket_disconnected_error ' what(): Failed to send message to server: Broken pipe Failed to connect to server. Error was :Failed to connect to server socket: Connection refused (process:5172): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. /bin/bash: line 1: 5172 Terminated SUPPRESS_DEPRECATED_NOTE=yes autopilot3 run ubuntuuitoolkit -- 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/1471598 Title: Autopilot uses mouse events, puts device in windowed mode Status in autopilot package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: AP tests emulating mouse to run, which puts the device into windowed mode. mouse presence is used to toggle the windowed mode on mobile devices. orig bug The autopilot tests on Krillin run in windowed mode. I don't think this should ever happen on that form factor. See also a bunch of dubious errors below. Tests running... terminate called after throwing an instance of 'boost::exception_detail::clone_implboost::exception_detail::error_info_injectormir::socket_disconnected_error ' what(): Failed to send message to server: Broken pipe Failed to connect to server. Error was :Failed to connect to server socket: Connection refused (process:5172): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. /bin/bash: line 1: 5172 Terminated SUPPRESS_DEPRECATED_NOTE=yes autopilot3 run ubuntuuitoolkit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopilot/+bug/1471598/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471459] Re: Launching nano with sudo creates a root owned directory in $HOME
Using sudo nano /etc/fstab still makes a hidden root-owned .nano folder in my home, so as far as I'm concerned the bug is still live. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1471459 Title: Launching nano with sudo creates a root owned directory in $HOME Status in nano package in Ubuntu: Invalid Bug description: If nano is started with sudo then a root owned directory .nano is created i a user's $HOME directory. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: nano 2.4.1-1 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.3-0ubuntu4 Architecture: amd64 Date: Sat Jul 4 20:06:16 2015 InstallationDate: Installed on 2015-02-25 (128 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Alpha amd64 (20150224) SourcePackage: nano UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1471459/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1469266] Re: Voicemail message shown after a reboot when there are no messages
any update? -- 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/1469266 Title: Voicemail message shown after a reboot when there are no messages Status in the base for Ubuntu mobile products: Confirmed Status in ofono package in Ubuntu: New Status in telephony-service package in Ubuntu: Confirmed Bug description: As of today every time I reboot the arale on ota4 the notification center reports a voice message. Dialing the voicemail ATT says there are no messages. If an actual message is left, it functions properly but clearing it does not fix the errant reporting on the next boot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1469266/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471459] Re: Launching nano with sudo creates a root owned directory in $HOME
Paul, I assume you are aware of the forum thread at http://ubuntuforums.org/showthread.php?t=2285298 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nano in Ubuntu. https://bugs.launchpad.net/bugs/1471459 Title: Launching nano with sudo creates a root owned directory in $HOME Status in nano package in Ubuntu: Confirmed Bug description: If nano is started with sudo then a root owned directory .nano is created i a user's $HOME directory. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: nano 2.4.1-1 ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.3-0ubuntu4 Architecture: amd64 Date: Sat Jul 4 20:06:16 2015 InstallationDate: Installed on 2015-02-25 (128 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Alpha amd64 (20150224) SourcePackage: nano UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1471459/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1470572] Re: native-origins.d information causes apport to strip origin information from Package
** Also affects: apport (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: apport (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: apport (Ubuntu Trusty) Status: New = Triaged ** Changed in: apport (Ubuntu Vivid) Status: New = Triaged ** Changed in: apport (Ubuntu Trusty) Importance: Undecided = High ** Changed in: apport (Ubuntu Vivid) Importance: Undecided = High -- 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/1470572 Title: native-origins.d information causes apport to strip origin information from Package Status in Apport crash detection/reporting: Fix Released Status in apport package in Ubuntu: Fix Committed Status in apport source package in Trusty: Triaged Status in apport source package in Vivid: Triaged Bug description: I've discovered that if you have a file in /etc/apport/native- origins.d/ for a PPA then that origin information is stripped from the Package field of the report. Test Case 1) Ensure that /etc/apport/native-origins.d/thunderbird contains LP-PPA-mozillateam-thunderbird-next 2) sudo add-apt-repository ppa:mozillateam/thunderbird-next 3) sudo apt-get update 4) sudo apt-get install thunderbird 5) ubuntu-bug thunderbird (apport-cli thunderbird) 6) view package field in the report Package: thunderbird 1:38.0~b6+build2-0ubuntu1 Instead I would expect the Package field to contain a [origin: LP- PPA-mozillateam-thunderbird-next] after the Package name. Additionally, my branch to retrace packages from PPAs depends on the origin information being there. Discussing this with pitti he said that this needs fixing. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1470572/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471890] [NEW] cacheSizeHint computation for webapps is incorrect due to apparmor denials
Public bug reported: Since http://bazaar.launchpad.net/~phablet-team/webbrowser- app/trunk/revision/1019, the webapp container (and all other embedders using an Ubuntu WebView) dynamically computes the cache size hint based on the available disk space. This doesn’t work in the general case, when the app is confined by apparmor, because the computation relies on QStorageInfo::bytesAvailable() (http://doc.qt.io/qt-5/qstorageinfo.html#bytesAvailable), which triggers apparmor denials: Jul 6 18:34:07 ubuntu-phablet kernel: [17458.604265]type=1400 audit(1436200447.375:184): apparmor=DENIED operation=open profile=com.ubuntu.developer.webapps.webapp-amazon-int_webapp-amazon_1.0.10 name=/proc/7424/mounts pid=7424 comm=webapp-containe requested_mask=r denied_mask=r fsuid=32011 ouid=32011 Jul 6 18:34:07 ubuntu-phablet kernel: [17458.604407]type=1400 audit(1436200447.375:185): apparmor=DENIED operation=open profile=com.ubuntu.developer.webapps.webapp-amazon-int_webapp-amazon_1.0.10 name=/dev/disk/by-label/ pid=7424 comm=webapp-containe requested_mask=r denied_mask=r fsuid=32011 ouid=0 This essentially means that the computation of the cache size hint is broken. It has also been reported that this breaks other apps’ functionality: https://lists.launchpad.net/ubuntu-phone/msg13622.html. ** Affects: apparmor-easyprof-ubuntu (Ubuntu) Importance: Undecided Status: New ** Affects: webbrowser-app (Ubuntu) Importance: High Assignee: Olivier Tilloy (osomon) Status: Confirmed ** Also affects: apparmor-easyprof-ubuntu (Ubuntu) Importance: Undecided Status: New -- 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/1471890 Title: cacheSizeHint computation for webapps is incorrect due to apparmor denials Status in apparmor-easyprof-ubuntu package in Ubuntu: New Status in webbrowser-app package in Ubuntu: Confirmed Bug description: Since http://bazaar.launchpad.net/~phablet-team/webbrowser- app/trunk/revision/1019, the webapp container (and all other embedders using an Ubuntu WebView) dynamically computes the cache size hint based on the available disk space. This doesn’t work in the general case, when the app is confined by apparmor, because the computation relies on QStorageInfo::bytesAvailable() (http://doc.qt.io/qt-5/qstorageinfo.html#bytesAvailable), which triggers apparmor denials: Jul 6 18:34:07 ubuntu-phablet kernel: [17458.604265]type=1400 audit(1436200447.375:184): apparmor=DENIED operation=open profile=com.ubuntu.developer.webapps.webapp-amazon-int_webapp-amazon_1.0.10 name=/proc/7424/mounts pid=7424 comm=webapp-containe requested_mask=r denied_mask=r fsuid=32011 ouid=32011 Jul 6 18:34:07 ubuntu-phablet kernel: [17458.604407]type=1400 audit(1436200447.375:185): apparmor=DENIED operation=open profile=com.ubuntu.developer.webapps.webapp-amazon-int_webapp-amazon_1.0.10 name=/dev/disk/by-label/ pid=7424 comm=webapp-containe requested_mask=r denied_mask=r fsuid=32011 ouid=0 This essentially means that the computation of the cache size hint is broken. It has also been reported that this breaks other apps’ functionality: https://lists.launchpad.net/ubuntu-phone/msg13622.html. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor-easyprof-ubuntu/+bug/1471890/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1470258] Re: browser is up side down on rotated screens
I am able to reproduce the issue with my laptop connected to an external display with a rotation applied. ** Changed in: webbrowser-app (Ubuntu) Status: New = Confirmed ** Changed in: webbrowser-app (Ubuntu) Importance: Undecided = Medium -- 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/1470258 Title: browser is up side down on rotated screens Status in webbrowser-app package in Ubuntu: Confirmed Bug description: I have an external screen that's attached to my laptop. The screen is rotated clockwise (portrait view). When I launch the Ubuntu browser and move it to the rotated screen, it flips upside down. When I drag it back to the laptop screen, it flips to the proper orientation (right side up). Please see screenshot attached. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: webbrowser-app 0.23+15.04.20150416-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 Date: Tue Jun 30 18:02:56 2015 InstallationDate: Installed on 2015-04-24 (67 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1470258/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 772709] Re: Network Manager Icon Is not changin when VPN is connected (nm-device-wired-secure icon is missing)
** Also affects: gnome-icon-theme Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/772709 Title: Network Manager Icon Is not changin when VPN is connected (nm-device- wired-secure icon is missing) Status in GNOME Icon Theme: New Status in elementary-icon-theme package in Ubuntu: Confirmed Status in gnome-icon-theme package in Ubuntu: Confirmed Status in lubuntu-artwork package in Ubuntu: Fix Released Status in network-manager-applet package in Ubuntu: Invalid Status in tango-icon-theme package in Ubuntu: Confirmed Bug description: Binary package hint: gnome-icon-theme Ater upgrading to 11.04 in gnome icon the (humanity and unity themes works fine) is see bad icons when connecting VPN and VPN is connected. Connected VPN icon is the same as original Network Manager. And connectin icon doen't show the Network manager icon only the flashing yellow lock (that must be over network manger icon) ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-icon-theme 2.31.0-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Fri Apr 29 01:05:10 2011 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-icon-theme UpgradeStatus: Upgraded to natty on 2011-04-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-icon-theme/+bug/772709/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp