[Touch-packages] [Bug 1432171] Re: Starting version 219 "systemd-boot"
Quite agree this is a bug (low priority though). We'll give it a look. However, it seems you have another bug, you shouldn't get 40s of black screen and be transitionned quickly to plymouth (as with upstart). Mind filing another bug report with additional debug information (let's keep this bug separated)? Attaching the journal (journactl -b) output would be helpful on this bug report. ** Changed in: systemd (Ubuntu) Importance: Undecided => Low ** Changed in: systemd (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1432171 Title: Starting version 219 "systemd-boot" Status in systemd package in Ubuntu: Triaged Bug description: Everytime the system is booted up I get a "Starting version 219" which it seems is the version number for systemd. Ubuntu version: Kubuntu 15.04 Beta 1 systemd package: systemd219-4ubuntu5 "systemd-boot" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432171/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1431743] Re: fails to boot due to read-ony file system
It seems that they are 2 independent issues that were mixed in this bug report. As Vasco seems to have something closer to the initial issue, let's use if for it. i'll try ssdm and poke Eugene if more info were needed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1431743 Title: fails to boot due to read-ony file system Status in systemd package in Ubuntu: Confirmed Bug description: I have just recently done a sudo apt-get upgrade, noting something about an included 219 update -- after consequent reboot, the system now hangs at starting 219. No light on Caps Lock. I have since been using upstart. Kernel using - I am on: Linux kubuntu 3.19.0-9-generic #9-Ubuntu SMP Wed Mar 11 17:50:03 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Same error when I try the 3.19.0.7-generic kernel. I have updated Grub, no change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431743/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1283551] Re: gjs-console crashed with signal 5
I just had this one pop up again for the first time since the fix was released. Using 14.04.2 w/HWE and GNOME 3.12.2 via PPA. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gobject-introspection in Ubuntu. https://bugs.launchpad.net/bugs/1283551 Title: gjs-console crashed with signal 5 Status in GNOME Spidermonkey Javascript binding: Fix Released Status in The "G" Library - GLib: Fix Released Status in Ubuntu GNOME: Triaged Status in gjs package in Ubuntu: Fix Released Status in gobject-introspection package in Ubuntu: Fix Released Status in gjs source package in Trusty: Fix Released Status in gobject-introspection source package in Trusty: Fix Released Bug description: [Impact] This is #1 crasher for gjs on errors.u.c, with thousands of hits per week. https://errors.ubuntu.com/bucket/?id=/usr/bin/gjs- console%3A5%3Aobject_instance_finalize%3Afinalize%3Afinalize%3AFinalizeTypedArenas%3AFinalizeArenas [Testcase] There is no specific testcase, this crash can be triggered by any function that frees its instance arguments. [Regression Potential] This adds a new attribute to g-i, for it to be effective however it requires typelibs to be rebuilt. See Comment #25 below === Original Bug Report === Connect Bluethooth ProblemType: CrashDistroRelease: Ubuntu 14.04 Package: gjs 1.39.90-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Feb 22 17:44:13 2014 ExecutablePath: /usr/bin/gjs-console InstallationDate: Installed on 2014-01-23 (30 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140122) ProcCmdline: /usr/bin/gjs-console -I /usr/share/gnome-documents/js -c const\ Main\ =\ imports.main;\ Main.start(); --no-default-windowSignal: 5SourcePackage: gjs StacktraceTop: ?? () from /usr/lib/libgjs.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0 Title: gjs-console crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1283551/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 836616] Re: 100% cpu usage in lightdm
Same problem for me (Ubuntu 12.04.5 LTS and 1.2.3-0ubuntu2.6 lightdm) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/836616 Title: 100% cpu usage in lightdm Status in Light Display Manager: Fix Released Status in lightdm package in Ubuntu: Triaged Bug description: Hey, it seems that there's an issue with 0.9.4 cpu usage. It doesn't look like it's a resurgence of #770725 since it appears as soon as lightdm is launched, not after login. Strac'ing the process doesn't give anything. If you need anything more, please ask. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/836616/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432493] Re: ntp dhcp hook doesn't check if ntp.conf has been updated
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ntp (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1432493 Title: ntp dhcp hook doesn't check if ntp.conf has been updated Status in ntp package in Ubuntu: Confirmed Bug description: /etc/dhcp/dhclient-exit-hooks.d/ntp doesn't check if /etc/ntp.conf has been updated since the last time dhclient ran. A simple addition of a check to see if /etc/ntp.conf is newer than /var/lib/ntp/ntp.conf.dhcp, and if so letting it add the servers would be sufficient. This is occuring on a Trusty host with ntp version 1:4.2.6.p5+dfsg- 3ubuntu2.14.04.2. Please let me know if you need any further information. $ dpkg-query -W ntp ntp 1:4.2.6.p5+dfsg-3ubuntu2.14.04.2 $ lsb_release -d Description: Ubuntu 14.04.2 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1432493/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432538] [NEW] gnome-codec-install vs sessioninstaller
Public bug reported: Totem 'suggest' gnome-codec-install but Vivid is using 'sessioninstaller' for software-center & file-roller as sessioninstaller replace gnome-codec-install, it should be better to set sessioninstaller as a 'suggest' totem's dependency ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libgstreamer1.0-0 1.4.5-1 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu3 Architecture: i386 CurrentDesktop: GNOME Date: Mon Mar 16 10:17:21 2015 SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: totem (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 gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1432538 Title: gnome-codec-install vs sessioninstaller Status in totem package in Ubuntu: New Bug description: Totem 'suggest' gnome-codec-install but Vivid is using 'sessioninstaller' for software-center & file- roller as sessioninstaller replace gnome-codec-install, it should be better to set sessioninstaller as a 'suggest' totem's dependency ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libgstreamer1.0-0 1.4.5-1 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu3 Architecture: i386 CurrentDesktop: GNOME Date: Mon Mar 16 10:17:21 2015 SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1432538/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432538] Re: gnome-codec-install vs sessioninstaller
does not understand why 'ubuntu-bug totem' have opened & gstreamer1.0 bug; so setting back to totem ** Package changed: gstreamer1.0 (Ubuntu) => totem (Ubuntu) ** Summary changed: - gnome-codec-install vs sessioninstaller + [3.14.2] gnome-codec-install vs sessioninstaller -- 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/1432538 Title: [3.14.2] gnome-codec-install vs sessioninstaller Status in totem package in Ubuntu: New Bug description: Totem 'suggest' gnome-codec-install but Vivid is using 'sessioninstaller' for software-center & file- roller as sessioninstaller replace gnome-codec-install, it should be better to set sessioninstaller as a 'suggest' totem's dependency ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libgstreamer1.0-0 1.4.5-1 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu3 Architecture: i386 CurrentDesktop: GNOME Date: Mon Mar 16 10:17:21 2015 SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1432538/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413865] Re: No default setting for "When power is critically low" in Power settings
** Branch linked: lp:ubuntu/vivid-proposed/ubuntu-settings -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1413865 Title: No default setting for "When power is critically low" in Power settings Status in Ubuntu Kylin: Fix Committed Status in ubuntu-settings package in Ubuntu: New Bug description: No default setting for "When power is critically low" in Power settings. 电源设置中”电量严重不足时“没有默认选项 Steps: 1. Install the latest Ubuntu kylin Vivid x64 OS 2. Enter into System settings-->Power 3. Check the default value of "When power is critically low" -->Failed. No default value for it Configuration: OS: Ubuntu Kylin vivid Daily build 20150122 x64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntukylin/+bug/1413865/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1362640] Re: Remove qtwebkit from touch image
** Branch linked: lp:ubuntu/vivid-proposed/ubuntu-touch-meta -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1362640 Title: Remove qtwebkit from touch image Status in the base for Ubuntu mobile products: In Progress Status in Cordova Ubuntu: Fix Released Status in Web Browser App: Triaged Status in signon-ui package in Ubuntu: Triaged Status in ubuntu-html5-theme package in Ubuntu: Triaged Status in ubuntu-touch-meta package in Ubuntu: In Progress Status in webbrowser-app package in Ubuntu: Triaged Bug description: The argument to remove this is based on the following: The qtwebkit webview is deprecated for our sdk and we will not be supporting it long term We are supporting an Oxide/Chromium solution for the Ubuntu.Webview This was done largely for security reasons The qtwebkit package is large and we would like to reduce image and install size We want to discourage app devs from using this api any longer, the review tools have indicated this for several months To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1362640/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1109029] Re: Depend on linux-initramfs-tools
** Changed in: linux (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/1109029 Title: Depend on linux-initramfs-tools Status in apparmor package in Ubuntu: New Status in console-setup package in Ubuntu: Confirmed Status in kbd package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Committed Status in lvm2 package in Ubuntu: Confirmed Status in multipath-tools package in Ubuntu: Confirmed Status in plymouth package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Invalid Status in udev package in Ubuntu: Confirmed Status in watershed package in Ubuntu: New Bug description: Many core packages depend on initramfs-tools when they should actually depend on linux-initramfs-tools (virtual package provided by initramfs-tools and dracut). Debian seems to be using "Depends: initramfs-tools | linux-initramfs- tools" for almost every relevant package. See also bug #1108987, which is about the fact that dracut shouldn't conflict with initramfs-tools. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1109029/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1338163] Re: unity lock screen provides no way to force-logout a user
** Changed in: unity Status: In Progress => Triaged ** Changed in: unity (Ubuntu) Status: In Progress => 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/1338163 Title: unity lock screen provides no way to force-logout a user Status in Unity: Triaged Status in unity package in Ubuntu: Confirmed Bug description: Let me start by saying that I realize that unity's screen locker is not the same thing as gnome-screensaver. That having been said, there are major regressions in functionality with the advent of Trusty. Virtually every site that uses Linux in any sort of public computing areas makes use (or used to, at least) of gnome-screensaver's "logout- delay" and "logout-enabled" functionality, which would, after the screen had been locked for a pre-determined amount of time, present a "Log Out" button that would end the user's session, optionally running a custom command to do so. This is vital, lest people walk away from their workstations, rendering them unusable by others until they are rebooted. unity's lock screen mode provides no way to do this. Right up until the final beta, it was possible to swap out unity's lockscreen mode for gnome-screensaver, but that was removed as well. I wouldn't mind if it was possible to configure the alternate use of a screensaver, but Unity goes out of its way to ensure you can't do this. If there's some magic way to do this, by adding an applet to the panel when in lockscreen mode, or by invoking some D-Bus black magic, I'd be happy to hear about it. But really, removing this level of functionality while simultaneously preventing any workarounds, is a real problem. Steps to reproduce: 1) Log in to a unity session. 2) Lock the screen. 3) Observe that org.gnome.desktop.screensaver gsettings keys are not honored. 4) Examine the com.canonical.unity* schemas and observe there is no way to enable this behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1338163/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 878318] Re: Dash, Launcher - Dash should allow dragging lenses onto the launcher
** Changed in: unity Status: In Progress => Triaged ** Changed in: unity/7.2 Status: In Progress => Triaged ** Changed in: unity (Ubuntu) Status: In Progress => 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/878318 Title: Dash, Launcher - Dash should allow dragging lenses onto the launcher Status in Ayatana Design: Fix Committed Status in Unity: Triaged Status in Unity 7.2 series: Triaged Status in unity package in Ubuntu: Confirmed Bug description: I remember talking about this at UDS and how it was supposed to be this way, and we all knew that, but I can't find a bug to track it so here it is. You're supposed to be able to drag a lens from the dash and onto the launcher, so that people can have their app or files lenses right on their launchers like we did for 11.04. --- Desired solution: - A user should be able to add a Lens icon to the Launcher by dragging the relevant icon from the Dash Nav to the Launcher (a user can position a Lens icon in any position they choose on the Launcher). - All Lens icons should always remain in the Dash Nav; they are not removable from this location. - Lens icons in the Launcher can be removed at any time by dragging and dropping them into the Trash - See attached visual design "unity_desktop_24_06_11_02.png" for details of how the Launcher lens icons should appear. Contact Rosie for the required visual assets. - The Dash Nav should not change, icons that are dragged to the Launcher also remain in the Dash Nav To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/878318/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1430893] Re: [FFe] Install Fcitx for Chinese users
What is the current proposed change? I don't think it's to seed fcitx* onto desktop as the merge proposal attached here is doing. Is it to add to pkg_depends in language-selector as in bug #1431337? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1430893 Title: [FFe] Install Fcitx for Chinese users Status in im-config package in Ubuntu: Confirmed Status in language-selector package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: There are currently two main supported input method frameworks available for CJK users: IBus (current default) and Fcitx. Both are mature projects, but Fcitx is better suited to Chinese users than IBus is, and is already the default in Ubuntu Kylin. IBus is increasingly moving in the direction of removing features upstream like tracking input state on a per-context basis. Also, the leading input method provider in China with more than 300 million users, Sogou, only supports Fcitx under Linux. Skinning support is non-existent in IBus. We've added support for Fcitx on the same level as IBus in Unity, so this FFe is a proposal to make Fcitx the default for Chinese locales this cycle, as a transition towards making Fcitx the default for all users next cycle. The changes should simply be seeding Fcitx and its related packages on the CD image, as well as possible changes to im- config. Those who have explicitly selected IBus as their chosen input method should be unaffected; these changes will only affect new users, and users who have never explicitly chosen an input method framework in their language settings. Also, this FFe propose to make language-selector to install more input method packages for Chinese users to their Fcitx equivalents (currently IBus) when adding/completing Chinese language support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1430893/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1424653] Re: Cannot unlock lock screen when using user without password
*** This bug is a duplicate of bug 1413790 *** https://bugs.launchpad.net/bugs/1413790 Somehow this bug is a duplicated of this one: 1413790 ** This bug has been marked a duplicate of bug 1413790 It's possible to bypasss lockscreen if user is in nopasswdlogin group. -- 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/1424653 Title: Cannot unlock lock screen when using user without password Status in Unity: New Status in unity package in Ubuntu: New Bug description: Creating a new user without login password makes the lock screen (Ctrl+Alt+L) unlockable because it asks for a password and none works (even blank). Ubuntu 14.04 and Ubuntu 14.10 clean installs and fully updated. In Ubuntu 14.10: Unity 7.3.1+14.10.20141016-0ubuntu1 Expected: No password to unlock and unlock the screen. What happens: The lock screens request a password to the user without it and doesn't unlock the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1424653/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413865] Re: No default setting for "When power is critically low" in Power settings
This bug was fixed in the package ubuntu-settings - 15.04.2 --- ubuntu-settings (15.04.2) vivid; urgency=medium [ F.J Kong ] * d/ubuntu-settings.gsettings-override: set critical-battery-action = 'shutdown' (LP: #1413865) -- Daniel HolbachMon, 16 Mar 2015 10:19:40 +0100 ** Changed in: ubuntu-settings (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1413865 Title: No default setting for "When power is critically low" in Power settings Status in Ubuntu Kylin: Fix Committed Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: No default setting for "When power is critically low" in Power settings. 电源设置中”电量严重不足时“没有默认选项 Steps: 1. Install the latest Ubuntu kylin Vivid x64 OS 2. Enter into System settings-->Power 3. Check the default value of "When power is critically low" -->Failed. No default value for it Configuration: OS: Ubuntu Kylin vivid Daily build 20150122 x64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntukylin/+bug/1413865/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1431107] Re: ordering cycles with early boot rcS scripts with inappropriate rc2.d links
Hi Martin, I think I can reproduce the appaprmor failure on every boot: $ systemctl status apparmor.service -l ● apparmor.service - LSB: AppArmor initialization Loaded: loaded (/etc/init.d/apparmor) Active: failed (Result: exit-code) since So 2015-03-15 22:42:54 CET; 12h ago Docs: man:systemd-sysv-generator(8) Process: 543 ExecStart=/etc/init.d/apparmor start (code=exited, status=123) Mär 15 22:42:54 benediktZ50-70 apparmor[543]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mär 15 22:42:54 benediktZ50-70 apparmor[543]: AppArmor parser error for /etc/apparmor.d/usr.sbin.mysqld-akonadi in /etc/apparmor.d/usr.sbin.mysqld-akonadi at line 31: Could not open 'local/usr.sbin.mysqld-akonadi' Mär 15 22:42:54 benediktZ50-70 apparmor[543]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mär 15 22:42:54 benediktZ50-70 apparmor[543]: AppArmor parser error for /etc/apparmor.d/usr.sbin.mysqld-akonadi in /etc/apparmor.d/usr.sbin.mysqld-akonadi at line 31: Could not open 'local/usr.sbin.mysqld-akonadi' Mär 15 22:42:54 benediktZ50-70 apparmor[543]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mär 15 22:42:54 benediktZ50-70 apparmor[543]: ...fail! Mär 15 22:42:54 benediktZ50-70 systemd[1]: apparmor.service: control process exited, code=exited status=123 Mär 15 22:42:54 benediktZ50-70 systemd[1]: Failed to start LSB: AppArmor initialization. Mär 15 22:42:54 benediktZ50-70 systemd[1]: Unit apparmor.service entered failed state. Mär 15 22:42:54 benediktZ50-70 systemd[1]: apparmor.service failed. However I have only one symlink in rcS: ls -l /etc/rc*/*lvm2 lrwxrwxrwx 1 root root 14 Dez 21 01:18 /etc/rcS.d/S08lvm2 -> ../init.d/lvm2 I will now try a debug boot. System: Kubuntu 15.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1431107 Title: ordering cycles with early boot rcS scripts with inappropriate rc2.d links Status in systemd package in Ubuntu: Triaged Bug description: After switching to systemd, the AppArmor service often fails to start on boot. This seems to happen at least 50% of the times I turn on the system. If I attempt to start the process again after the system is otherwise finished booting, it works fine. I also have another system with the same software configuration but a much slower storage system (HDD instead of SSD) which never suffers from this problem, so I think it is probably a race condition. If I do "systemctl status apparmor", I get the following output: michael@mamarley-laptop:~$ sudo systemctl status apparmor ● apparmor.service - LSB: AppArmor initialization Loaded: loaded (/etc/init.d/apparmor) Active: failed (Result: exit-code) since Wed 2015-03-11 21:25:44 EDT; 1min 5s ago Docs: man:systemd-sysv-generator(8) Process: 237 ExecStart=/etc/init.d/apparmor start (code=exited, status=123) Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 11 21:25:44 mamarley-laptop apparmor[237]: mkstemp: Read-only file system Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 11 21:25:44 mamarley-laptop systemd[1]: apparmor.service: control process exited, code=exited status=123 Mar 11 21:25:44 mamarley-laptop apparmor[237]: ...fail! Mar 11 21:25:44 mamarley-laptop systemd[1]: Failed to start LSB: AppArmor initialization. Mar 11 21:25:44 mamarley-laptop systemd[1]: Unit apparmor.service entered failed state. Mar 11 21:25:44 mamarley-laptop systemd[1]: apparmor.service failed. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-9.9-lowlatency 3.19.1 Uname: Linux 3.19.0-9-lowlatency x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Wed Mar 11 21:30:08 2015 InstallationDate: Installed on 2014-06-01 (283 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) MachineType: LENOVO 2359CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-lowlatency root=UUID=1f7829ef-ffb8-4182-ac92-40d613ea78c9 ro elevator=deadline intel_pstate=enable "acpi_osi=Windows 2012" SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETA2WW (2.62 ) dmi.board.asset.tag: Not Available dmi.board.name: 2359CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.
[Touch-packages] [Bug 1431877] Re: [FFe] Merge fixes from debian/sid
** Branch linked: lp:ubuntu/vivid-proposed/apt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1431877 Title: [FFe] Merge fixes from debian/sid Status in apt package in Ubuntu: Triaged Bug description: I would like to merge the latest fixes from the debian/sid apt branch. Those are. It also includes a fix for #1429041. apt (1.0.9.7) unstable; urgency=medium [ Tomasz Buchert ] * Fix crash in the apt-transport-https when Owner is NULL (Closes: #778375) -- Michael Vogt Mon, 23 Feb 2015 12:54:03 +0100 apt (1.0.9.6) unstable; urgency=medium [ Michael Vogt ] * Fix missing URIStart() for https downloads * Add regression test for the previous commit [ David Kalnischkies ] * 128 KiB DSC files ought to be enough for everyone (Closes: 774893) * award points for positive dependencies again (Closes: 774924) -- Michael Vogt Fri, 16 Jan 2015 08:37:25 +0100 apt (1.0.9.5) unstable; urgency=medium [ David Kalnischkies ] * dispose http(s) 416 error page as non-content (Closes: 768797) * do not make PTY slave the controlling terminal (Closes: 772641) * always run 'dpkg --configure -a' at the end of our dpkg callings (Closes: 769609) * pass-through stdin fd instead of content if not a terminal (Closes: 773061) [ James McCoy ] * tighten filtering of kernel images in apt.auto-removal (Closes: 772732) [ Jean-Pierre Giraud ] * French manpages translation update (Closes: 771967) [ Zhou Mo ] * Chinese (simplified) program translation update (Closes: 771982) [ Kenshi Muto ] * Japanese program translation update (Closes: 772678) [ Theppitak Karoonboonyanan ] * Thai program translation update (Closes: 772913) -- David Kalnischkies Tue, 23 Dec 2014 13:22:42 +0100 apt (1.0.9.4) unstable; urgency=medium [ David Kalnischkies ] * use 'best' hash for source authentication (LP: 1098738) * deprecate the Section member from package struct * allow options between command and -- on commandline * re-enable support for -s (and co) in apt-get source (Closes: 742578) * change codenames to jessie as stable POV in docs * close leaking slave fd after setting up pty magic (Closes: 767774) * fix PTY interaction on linux and kfreebsd (Closes: 765687) [ James McCoy ] * support long keyids in "apt-key del" instead of ignoring them (Closes: 754436) [ Michael Vogt ] * Use sysconf(_SC_ARG_MAX) to find the size of Dpkg::MaxArgBytes [ Frans Spiesschaert ] * Dutch program translation update (Closes: 771039) [ Julien Patriarca ] * French program translation update (Closes: 766755) [ Zhou Mo ] * Chinese (simplified) program translation update (Closes: 766170) [ Miroslav Kure ] * Czech program translation update (Closes: 764055) [ Mert Dirik ] * Turkish program translation update (Closes: 763379) [ Kenshi Muto ] * Japanese program translation update (Closes: 763033) [ Manuel "Venturi" Porras Peralta ] * Spanish program translation update (Closes: 771815) -- David Kalnischkies Wed, 03 Dec 2014 14:26:04 +0100 All of those changes are pretty safe and got past the feature freeze of debian 7.0. All tests pass: # ./test/integration/run-tests ... Statistics: 151 tests were run: 151 successfully and 0 failed All tests seem to have been run successfully. What could possibly go wrong? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1431877/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1431107] Re: ordering cycles with early boot rcS scripts with inappropriate rc2.d links
$ systemctl show --no-pager -p After apparmor After=system.slice systemd-journald.socket local-fs.target and: $ systemctl list-dependencies local-fs.target local-fs.target ● ├─-.mount ● ├─boot-efi.mount ● ├─home.mount ● ├─systemd-fsck-root.service ● └─systemd-remount-fs.service I think this is another bug that only shows the same symptoms as this bug. Could you please confirm this, before I open a new bug? ** Attachment added: "debug.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431107/+attachment/4346988/+files/debug.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1431107 Title: ordering cycles with early boot rcS scripts with inappropriate rc2.d links Status in systemd package in Ubuntu: Triaged Bug description: After switching to systemd, the AppArmor service often fails to start on boot. This seems to happen at least 50% of the times I turn on the system. If I attempt to start the process again after the system is otherwise finished booting, it works fine. I also have another system with the same software configuration but a much slower storage system (HDD instead of SSD) which never suffers from this problem, so I think it is probably a race condition. If I do "systemctl status apparmor", I get the following output: michael@mamarley-laptop:~$ sudo systemctl status apparmor ● apparmor.service - LSB: AppArmor initialization Loaded: loaded (/etc/init.d/apparmor) Active: failed (Result: exit-code) since Wed 2015-03-11 21:25:44 EDT; 1min 5s ago Docs: man:systemd-sysv-generator(8) Process: 237 ExecStart=/etc/init.d/apparmor start (code=exited, status=123) Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 11 21:25:44 mamarley-laptop apparmor[237]: mkstemp: Read-only file system Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 11 21:25:44 mamarley-laptop systemd[1]: apparmor.service: control process exited, code=exited status=123 Mar 11 21:25:44 mamarley-laptop apparmor[237]: ...fail! Mar 11 21:25:44 mamarley-laptop systemd[1]: Failed to start LSB: AppArmor initialization. Mar 11 21:25:44 mamarley-laptop systemd[1]: Unit apparmor.service entered failed state. Mar 11 21:25:44 mamarley-laptop systemd[1]: apparmor.service failed. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-9.9-lowlatency 3.19.1 Uname: Linux 3.19.0-9-lowlatency x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Wed Mar 11 21:30:08 2015 InstallationDate: Installed on 2014-06-01 (283 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) MachineType: LENOVO 2359CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-lowlatency root=UUID=1f7829ef-ffb8-4182-ac92-40d613ea78c9 ro elevator=deadline intel_pstate=enable "acpi_osi=Windows 2012" SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETA2WW (2.62 ) dmi.board.asset.tag: Not Available dmi.board.name: 2359CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ETA2WW(2.62):bd08/21/2014:svnLENOVO:pn2359CTO:pvrThinkPadT530:rvnLENOVO:rn2359CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2359CTO dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431107/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1404302] Re: liblttng-ust0 Error opening shm /lttng-ust-wait-5
This also happen with libvirtd apparmor profile in enforce mode: virtual machines (ie sub profiles with libvirt-someUUID) will constantly complain they are denied read access to /dev/shm/lttng-ust-wait-5 -- 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/1404302 Title: liblttng-ust0 Error opening shm /lttng-ust-wait-5 Status in Platform API: New Status in QT Ubuntu: New Status in ust package in Ubuntu: Confirmed Bug description: Confined apps don't have access to this and continuously produce this error message in stderr: libust[31283/31285]: Error: Error opening shm /lttng-ust-wait-5 (in get_wait_shm() at lttng-ust-comm.c:958) This is printed to the application's log about once every other second and makes it hard to read the application's own debug output. For a better app developer experience this message should be silenced. To manage notifications about this bug go to: https://bugs.launchpad.net/platform-api/+bug/1404302/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1430893] Re: [FFe] Install Fcitx for Chinese users
We just discussed this on #ubuntu-desktop - I think this is the plan - Add fcitx & friends to 'live' seed (dropping ibus-pinyin & others at the same time), so that it's installed in the live session (it needs to be started up before the session starts) but not in the target by default. - Add it to pkg_depends of language-selector (per #1431337), so that check-language-support -l zh_CN returns fcitx packages. + This will cause the installer to keep fcitx only when the selected language is Chinese, and remove it otherwise. + In installed systems, language-selector will prompt to install fcitx. - If necessary (not sure if it is), fix language-selector to select fcitx as IM for Chinese when there is no pre-existing configuration. + We don't try to change .xinputrc for existing users. To test this effectively, we have to do the seed change - the rest can be done locally. Not acking the FFe yet, but please (temporarily for now) go ahead with the above seed change. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1430893 Title: [FFe] Install Fcitx for Chinese users Status in im-config package in Ubuntu: Confirmed Status in language-selector package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: There are currently two main supported input method frameworks available for CJK users: IBus (current default) and Fcitx. Both are mature projects, but Fcitx is better suited to Chinese users than IBus is, and is already the default in Ubuntu Kylin. IBus is increasingly moving in the direction of removing features upstream like tracking input state on a per-context basis. Also, the leading input method provider in China with more than 300 million users, Sogou, only supports Fcitx under Linux. Skinning support is non-existent in IBus. We've added support for Fcitx on the same level as IBus in Unity, so this FFe is a proposal to make Fcitx the default for Chinese locales this cycle, as a transition towards making Fcitx the default for all users next cycle. The changes should simply be seeding Fcitx and its related packages on the CD image, as well as possible changes to im- config. Those who have explicitly selected IBus as their chosen input method should be unaffected; these changes will only affect new users, and users who have never explicitly chosen an input method framework in their language settings. Also, this FFe propose to make language-selector to install more input method packages for Chinese users to their Fcitx equivalents (currently IBus) when adding/completing Chinese language support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1430893/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 819620] Re: tex syntax highlighting error
Bug is fixed in latest LaTeX Suite.
$ lsb_release -rd
Description:Ubuntu 14.10
Release:14.10
$ apt-cache policy vim-latexsuite
vim-latexsuite:
Installed: 20130116.788-1
Candidate: 20130116.788-1
Version table:
*** 20130116.788-1 0
500 http://au.archive.ubuntu.com/ubuntu/ utopic/universe amd64 Packages
100 /var/lib/dpkg/status
** Changed in: vim (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/819620
Title:
tex syntax highlighting error
Status in vim package in Ubuntu:
Fix Released
Bug description:
TeX syntax highlighting is incorrect for:
$X_{\{i\}}$ for $k$ in $S$ some text!?!
There seems to be some confusion arising from the nested { } and \{ \}
in the subscript. The highlighting is wrong from the i onward in this
example. Highlighting is correct if the _ or the \{ \} pair is
removed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/819620/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1294732] Re: [meet ubuntu] "phone" string in tablet oobe; oobe should have "tablet" or generic term
** Changed in: ubuntu-ux Assignee: Estibaliz Landa Torres (estilanda) => (unassigned) ** Changed in: ubuntu-ux Status: Fix Committed => Triaged -- 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/1294732 Title: [meet ubuntu] "phone" string in tablet oobe; oobe should have "tablet" or generic term Status in Ubuntu UX bugs: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: build r237 the oobe on the tablet (nexus 7) refers to a "phone" it should refer to a "tablet" or a generic like "your device" See also bug 1258211. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1294732/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432599] [NEW] Network-manager tries to manage virbr0, which it should not
Public bug reported: Since a recent upgrade in vivid, nm is trying to manage virbr0. This results in my main machine not getting a real IP address on eth0, and virtual machines not being able to use the network. This is probably related to https://bugzilla.redhat.com/show_bug.cgi?id=1166199 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 16 12:36:07 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-12-13 (92 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IpRoute: default via 10.0.0.1 dev eth0 proto static metric 1024 10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.75 192.168.111.0/24 dev wlan0 proto kernel scope link src 192.168.111.8 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) http_proxy: http://localhost:8118/ nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. no_proxy: localhost,127.0.0.0/8,::1 ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- 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/1432599 Title: Network-manager tries to manage virbr0, which it should not Status in network-manager package in Ubuntu: New Bug description: Since a recent upgrade in vivid, nm is trying to manage virbr0. This results in my main machine not getting a real IP address on eth0, and virtual machines not being able to use the network. This is probably related to https://bugzilla.redhat.com/show_bug.cgi?id=1166199 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 16 12:36:07 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-12-13 (92 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IpRoute: default via 10.0.0.1 dev eth0 proto static metric 1024 10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.75 192.168.111.0/24 dev wlan0 proto kernel scope link src 192.168.111.8 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) http_proxy: http://localhost:8118/ nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432599/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410618] Re: MacBook Air 6, 2 TRRS Headset Mic Not Working
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/1410618 Title: MacBook Air 6,2 TRRS Headset Mic Not Working Status in alsa-driver package in Ubuntu: Confirmed Bug description: Hello, I'm running Ubuntu Gnome 14.04 on a new MacBookAir6,2 with the Cirrus Logic CS4208 and would love to get the microphone part of the TRRS connector working. Mac OS picks up and utilizes the TRRS headset mic without issue so I know the hardware is a go. With the headset plugged in, running sudo hdajacksensetest -a results in: Pin 0x05 ( Digital Out, HDMI): present = No Pin 0x06 ( Digital Out, HDMI): present = No Pin 0x07 ( Digital Out, HDMI): present = No AlsaInfo output here: http://www.alsa-project.org/db/?f=cabc8cab44d308c8a3898c66d48d9be4fc5ccf83 I opened up hdajackretask to find four pins: Green Headphone Pin ID: 0x10 Headphone Internal Speaker Pin ID: 0x12 Internal speaker Pink Mic Pin ID: 0x18 Not connected Internal Mic Pin ID: 0x1c Internal mic Unplugging and replugging the headset changes the Output device in sound settings from Headphones to Speakers so that works, but nothing in the input tab ever changes. It always lists two devices: Internal Microphone and Microphone. Both of these seem to actually be the internal microphone in the mac - either works without the headset connected at all. So I'm not really sure how to proceed from here, but I'd be happy to run whatever diagnostic tests might prove useful and/or even contribute code toward a fix - but I just have no idea where to start. Is it as simple as just finding the right pin and telling the system to use it as a microphone? Similar bug report here: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/950494 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1410618/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410618] Re: MacBook Air 6, 2 TRRS Headset Mic Not Working
Same issue (with same board) on mac book pro 11, 3. https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1393502 -- 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/1410618 Title: MacBook Air 6,2 TRRS Headset Mic Not Working Status in alsa-driver package in Ubuntu: Confirmed Bug description: Hello, I'm running Ubuntu Gnome 14.04 on a new MacBookAir6,2 with the Cirrus Logic CS4208 and would love to get the microphone part of the TRRS connector working. Mac OS picks up and utilizes the TRRS headset mic without issue so I know the hardware is a go. With the headset plugged in, running sudo hdajacksensetest -a results in: Pin 0x05 ( Digital Out, HDMI): present = No Pin 0x06 ( Digital Out, HDMI): present = No Pin 0x07 ( Digital Out, HDMI): present = No AlsaInfo output here: http://www.alsa-project.org/db/?f=cabc8cab44d308c8a3898c66d48d9be4fc5ccf83 I opened up hdajackretask to find four pins: Green Headphone Pin ID: 0x10 Headphone Internal Speaker Pin ID: 0x12 Internal speaker Pink Mic Pin ID: 0x18 Not connected Internal Mic Pin ID: 0x1c Internal mic Unplugging and replugging the headset changes the Output device in sound settings from Headphones to Speakers so that works, but nothing in the input tab ever changes. It always lists two devices: Internal Microphone and Microphone. Both of these seem to actually be the internal microphone in the mac - either works without the headset connected at all. So I'm not really sure how to proceed from here, but I'd be happy to run whatever diagnostic tests might prove useful and/or even contribute code toward a fix - but I just have no idea where to start. Is it as simple as just finding the right pin and telling the system to use it as a microphone? Similar bug report here: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/950494 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1410618/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432599] Re: Network-manager tries to manage virbr0, which it should not
** Description changed: - Since a recent upgrade in vivid, nm is tryoing to manage virbr0. This + Since a recent upgrade in vivid, nm is trying to manage virbr0. This results in my main machine not getting a real IP address on eth0, and virtual machines not being able to use the network. This is probably related to https://bugzilla.redhat.com/show_bug.cgi?id=1166199 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 16 12:36:07 2015 IfupdownConfig: - # interfaces(5) file used by ifup(8) and ifdown(8) - auto lo - iface lo inet loopback + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback InstallationDate: Installed on 2014-12-13 (92 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IpRoute: - default via 10.0.0.1 dev eth0 proto static metric 1024 - 10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.75 - 192.168.111.0/24 dev wlan0 proto kernel scope link src 192.168.111.8 - 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 + default via 10.0.0.1 dev eth0 proto static metric 1024 + 10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.75 + 192.168.111.0/24 dev wlan0 proto kernel scope link src 192.168.111.8 + 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 NetworkManager.state: - [main] - NetworkingEnabled=true - WirelessEnabled=true - WWANEnabled=true - WimaxEnabled=true + [main] + NetworkingEnabled=true + WirelessEnabled=true + WWANEnabled=true + WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) http_proxy: http://localhost:8118/ nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. no_proxy: localhost,127.0.0.0/8,::1 -- 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/1432599 Title: Network-manager tries to manage virbr0, which it should not Status in network-manager package in Ubuntu: New Bug description: Since a recent upgrade in vivid, nm is trying to manage virbr0. This results in my main machine not getting a real IP address on eth0, and virtual machines not being able to use the network. This is probably related to https://bugzilla.redhat.com/show_bug.cgi?id=1166199 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 16 12:36:07 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-12-13 (92 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IpRoute: default via 10.0.0.1 dev eth0 proto static metric 1024 10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.75 192.168.111.0/24 dev wlan0 proto kernel scope link src 192.168.111.8 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) http_proxy: http://localhost:8118/ nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432599/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1424466] Re: Devel package not installable in 14.04.2 (mesa-lts-utopic
yes, the problem with fglrx is well known and I'm working on it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1424466 Title: Devel package not installable in 14.04.2 (mesa-lts-utopic Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Trusty: Fix Committed Bug description: [Impact] * Some -dev packages like ubuntu-sdk and libglew-dev cannot be installed when the lts-utopic stack is used. [Test Case] * Install the lts-utopic stack. * apt-get install ubuntu-sdk * Good: you get a whole list of packages to install. * Bad: apt-get install fails like pasted in the original bug report. * Also test the same without the lts-utopic stack, to make sure there are no regressions. [Regression Potential] * Low, this has been done for precise before, and mesa packaging has to be updated for every LTS release. Unfortunately there are no alternatives. :( [Other Info] * There's probably an apt bug in here too. Nudging the resolver by specifying libgl1-mesa-dev-lts-utopic and libgles2-mesa-dev-lts-utopic works, but I didn't find a good way to express this in the depends, and that would have to be done for every package. [Original bug report] Not the first, likely not the last devel to not be installable in 14.04.2 or any mesa-lts-utopic install Another one is libglew-dev sudo apt-get install freeglut3-dev Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libcheese-gtk23 : Depends: libclutter-gtk-1.0-0 (>= 0.91.8) but it is not going to be installed Depends: libcogl15 (>= 1.15.8) but it is not going to be installed libcheese7 : Depends: libclutter-gst-2.0-0 (>= 0.10.0) but it is not going to be installed Depends: gstreamer1.0-clutter but it is not going to be installed libclutter-1.0-0 : Depends: libcogl-pango15 (>= 1.15.8) but it is not going to be installed Depends: libcogl15 (>= 1.15.8) but it is not going to be installed ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: freeglut3-dev (not installed) ProcVersionSignature: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 22 18:03:30 2015 InstallationDate: Installed on 2015-02-08 (14 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150203.2) SourcePackage: freeglut UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1424466/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432610] [NEW] Libav security fixes March 2015
*** This bug is a security vulnerability *** Public security bug reported: Libav 0.8.17, 9.18 and 11.3 are out that fix a number of security issues. version 0.8.17: - utvideodec: Handle slice_height being zero (CVE-2014-9604) - tiff: Check that there is no aliasing in pixel format selection (CVE-2014-8544) - rmenc: limit packet size - eamad: check for out of bounds read (CID/1257500) - h264_cabac: Break infinite loops - matroskadec: Fix read-after-free in matroska_read_seek() (chromium/427266) - gifdec: refactor interleave end handling (CVE-2014-8547) - smc: fix the bounds check (CVE-2014-8548) - mmvideo: check frame dimensions (CVE-2014-8543) - jvdec: check frame dimensions (CVE-2014-8542) - mov: avoid a memleak when multiple stss boxes are present - apetag: Fix APE tag size check - x86: Only use optimizations with cmov if the CPU supports the instruction - x86: Add CPU flag for the i686 cmov instruction version 9.18: - tiff: Check that there is no aliasing in pixel format selection (CVE-2014-8544) - utvideodec: Handle slice_height being zero (CVE-2014-9604) - rmenc: limit packet size - rv10: check size of s->mb_width * s->mb_height - eamad: check for out of bounds read (CID/1257500) - arm: Suppress tags about used cpu arch and extensions - img2dec: correctly use the parsed value from -start_number - h264_cabac: Break infinite loops - matroskadec: Fix read-after-free in matroska_read_seek() (chromium/427266) - smc: fix the bounds check (CVE-2014-8548) - gifdec: refactor interleave end handling (CVE-2014-8547) - mmvideo: check frame dimensions (CVE-2014-8543) - jvdec: check frame dimensions (CVE-2014-8542) - mov: avoid a memleak when multiple stss boxes are present - mp3enc: fix a triggerable assert - apetag: Fix APE tag size check version 11.3: - utvideodec: Handle slice_height being zero (CVE-2014-9604) - adxdec: set avctx->channels in adx_read_header - rmenc: limit packet size - webp: validate the distance prefix code - rv10: check size of s->mb_width * s->mb_height - eamad: check for out of bounds read (CID/1257500) - mdec: check for out of bounds read (CID/1257501) - configure: Properly fail when libcdio/cdparanoia is not found - tiff: Check that there is no aliasing in pixel format selection (CVE-2014-8544) - aic: Fix decoding files with odd dimensions - vorbis: Check the vlc value in setup_classifs - arm: Suppress tags about used cpu arch and extensions - prores: Extend the padding check to 16bit - icecast: Do not use chunked post, allows feeding to icecast properly - img2dec: correctly use the parsed value from -start_number - h264_cabac: Break infinite loops - hevc_deblock: Fix compilation with nasm (libav #795) - h264: initialize H264Context.avctx in init_thread_copy - h264: Do not share rbsp_buffer across threads - h264: only ref cur_pic in update_thread_context if it is initialized - matroskadec: Fix read-after-free in matroska_read_seek() (chromium #427266) - log: Unbreak no-tty support on 256color terminals ** Affects: libav (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: libav (Ubuntu Precise) Importance: Undecided Assignee: Marc Deslauriers (mdeslaur) Status: Confirmed ** Affects: libav (Ubuntu Trusty) Importance: Undecided Assignee: Marc Deslauriers (mdeslaur) Status: Confirmed ** Affects: libav (Ubuntu Utopic) Importance: Undecided Status: Confirmed ** Affects: libav (Ubuntu Vivid) Importance: Undecided Status: Confirmed ** Also affects: libav (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: libav (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: libav (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: libav (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: libav (Ubuntu Precise) Status: New => Confirmed ** Changed in: libav (Ubuntu Trusty) Status: New => Confirmed ** Changed in: libav (Ubuntu Utopic) Status: New => Confirmed ** Changed in: libav (Ubuntu Vivid) Status: New => Confirmed ** Changed in: libav (Ubuntu Precise) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) ** Changed in: libav (Ubuntu Trusty) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1432610 Title: Libav security fixes March 2015 Status in libav package in Ubuntu: Confirmed Status in libav source package in Precise: Confirmed Status in libav source package in Trusty: Confirmed Status in libav source package in Utopic: Confirmed Status in libav source package in Vivid: Confirmed Bug description: Libav 0.8.17, 9.18 and 11.3 are out that fix a number of security issues. version 0.8.17: - utvideodec: Handle slice_height being zero (CVE-2014-9604) - tiff: Check
[Touch-packages] [Bug 1432611] [NEW] Tweak assert_discard_popover to work better with textfield in header
Public bug reported: In the ongoing landing of 2015.03.16 the ubuntuuitoolkit.tests.components.test_textinput.InsertModeTextInputTestCase.test_popover_visible_after_dragging_caret(header) fails. It means that we need to tweak assert_discard_popover to work better with textfield in header. ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Medium Assignee: Christian Dywan (kalikiana) Status: Fix Committed ** Branch linked: lp:~ubuntu-sdk-team/ubuntu-ui- toolkit/tweakAssertDiscardPopover -- 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/1432611 Title: Tweak assert_discard_popover to work better with textfield in header Status in ubuntu-ui-toolkit package in Ubuntu: Fix Committed Bug description: In the ongoing landing of 2015.03.16 the ubuntuuitoolkit.tests.components.test_textinput.InsertModeTextInputTestCase.test_popover_visible_after_dragging_caret(header) fails. It means that we need to tweak assert_discard_popover to work better with textfield in header. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1432611/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1425155] Re: totem 3.14's OSD looks bad in Ambiance
After quite some tinkering with backgrounds and borders to give these widgets a buttony feel (like Adwaita does) while trying to make them look similar to our other buttons, I gave up and decided for a very minimal approach. Branch is attached. Please let me know what you think. ** Branch linked: lp:~larsu/ubuntu-themes/osd-totem -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1425155 Title: totem 3.14's OSD looks bad in Ambiance Status in ubuntu-themes package in Ubuntu: New Bug description: In our theme, totem's OSD (player controls) doesn't look very nice. It's not really styled. Just play a video and look at the in-window controls to see this. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: totem 3.14.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 24 16:01:38 2015 InstallationDate: Installed on 2012-10-07 (869 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007) SourcePackage: totem UpgradeStatus: Upgraded to vivid on 2013-05-07 (658 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1425155/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1362640] Re: Remove qtwebkit from touch image
This bug was fixed in the package ubuntu-touch-meta - 1.216 --- ubuntu-touch-meta (1.216) vivid; urgency=medium [ Timo Jyrinki ] * Refreshed dependencies * Added liboxideqt-qmlplugin to sdk-libs * Removed libqt5webkit5-dev from sdk-libs-dev (LP: #1362640) * Removed qml-module-qtwebkit from sdk-libs -- Daniel HolbachMon, 16 Mar 2015 10:11:26 +0100 ** Changed in: ubuntu-touch-meta (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1362640 Title: Remove qtwebkit from touch image Status in the base for Ubuntu mobile products: In Progress Status in Cordova Ubuntu: Fix Released Status in Web Browser App: Triaged Status in signon-ui package in Ubuntu: Triaged Status in ubuntu-html5-theme package in Ubuntu: Triaged Status in ubuntu-touch-meta package in Ubuntu: Fix Released Status in webbrowser-app package in Ubuntu: Triaged Bug description: The argument to remove this is based on the following: The qtwebkit webview is deprecated for our sdk and we will not be supporting it long term We are supporting an Oxide/Chromium solution for the Ubuntu.Webview This was done largely for security reasons The qtwebkit package is large and we would like to reduce image and install size We want to discourage app devs from using this api any longer, the review tools have indicated this for several months To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1362640/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1425155] Re: totem 3.14's OSD looks bad in Ambiance
Screenshot of totem with the new theme. ** Attachment added: "totem-osd.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1425155/+attachment/4347063/+files/totem-osd.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1425155 Title: totem 3.14's OSD looks bad in Ambiance Status in ubuntu-themes package in Ubuntu: New Bug description: In our theme, totem's OSD (player controls) doesn't look very nice. It's not really styled. Just play a video and look at the in-window controls to see this. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: totem 3.14.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 24 16:01:38 2015 InstallationDate: Installed on 2012-10-07 (869 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007) SourcePackage: totem UpgradeStatus: Upgraded to vivid on 2013-05-07 (658 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1425155/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432614] [NEW] lightdm crashes on login
Public bug reported: I can't login using lightgdm, the error show "X Configure error". ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.2.3-0ubuntu2.5 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 Date: Mon Mar 16 09:22:22 2015 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) MarkForUpload: True ProcEnviron: LANGUAGE=es_AR:en TERM=xterm PATH=(custom, no user) LANG=es_AR.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1432614 Title: lightdm crashes on login Status in lightdm package in Ubuntu: New Bug description: I can't login using lightgdm, the error show "X Configure error". ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.2.3-0ubuntu2.5 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 Date: Mon Mar 16 09:22:22 2015 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) MarkForUpload: True ProcEnviron: LANGUAGE=es_AR:en TERM=xterm PATH=(custom, no user) LANG=es_AR.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1432614/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432613] [NEW] Facebook and MSN shutting down
Public bug reported: The march towards a future of silos carries on. https://developers.facebook.com/docs/chat - the XMPP gateway for Facebook will shut down on April 30. http://ismsndeadyet.com/ - Microsoft are removing MSN endpoints. I guess we need to correspondingly remove IM support for these services & SRU it back. ** Affects: account-plugins Importance: Undecided Status: New ** Affects: account-plugins (Ubuntu) Importance: Undecided Status: New ** Also affects: account-plugins Importance: Undecided Status: New ** Description changed: The march towards a future of silos carries on. https://developers.facebook.com/docs/chat - the XMPP gateway for Facebook will shut down on April 30. http://ismsndeadyet.com/ - Microsoft are removing MSN endpoints. - I guess we need to correspondingly remove these services & SRU it back. + I guess we need to correspondingly remove IM support for these services + & SRU it back. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1432613 Title: Facebook and MSN shutting down Status in Online Accounts: Account plugins: New Status in account-plugins package in Ubuntu: New Bug description: The march towards a future of silos carries on. https://developers.facebook.com/docs/chat - the XMPP gateway for Facebook will shut down on April 30. http://ismsndeadyet.com/ - Microsoft are removing MSN endpoints. I guess we need to correspondingly remove IM support for these services & SRU it back. To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1432613/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432613] Re: Facebook and MSN shutting down
** Changed in: account-plugins Status: New => Confirmed ** Changed in: account-plugins Importance: Undecided => High ** Changed in: account-plugins Assignee: (unassigned) => Alberto Mardegan (mardy) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1432613 Title: Facebook and MSN shutting down Status in Online Accounts: Account plugins: Confirmed Status in account-plugins package in Ubuntu: New Bug description: The march towards a future of silos carries on. https://developers.facebook.com/docs/chat - the XMPP gateway for Facebook will shut down on April 30. http://ismsndeadyet.com/ - Microsoft are removing MSN endpoints. I guess we need to correspondingly remove IM support for these services & SRU it back. To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1432613/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432484] Re: ctrl+alt+t hot key doesn't open terminal
Testing on a fully up-to-date (as of 2015-03-06) Vivid Vervet session fails to reproduce this problem. Please open a terminal (using eg. alt-f2 and typing x-terminal-emulator) and enter the following command. gsettings get org.gnome.settings-daemon.plugins.media-keys terminal and paste the result into this bug report. ** Changed in: unity (Ubuntu) Status: New => Incomplete -- 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/1432484 Title: ctrl+alt+t hot key doesn't open terminal Status in unity package in Ubuntu: Incomplete Bug description: 1) Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 2) unity: Installed: 7.3.1+15.04.20150227-0ubuntu1 Candidate: 7.3.1+15.04.20150227-0ubuntu1 Version table: *** 7.3.1+15.04.20150227-0ubuntu1 0 500 http://mirrors.accretive-networks.net/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status 3) ctrl+alt+t should open terminal 4) nothing happens ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20150227-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Mar 15 21:55:08 2015 DistUpgraded: 2015-03-15 19:32:57,918 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.19.0-9-generic, x86_64: installed nvidia-346-updates, 346.47, 3.19.0-9-generic, x86_64: installed nvidia-346-updates-uvm, 346.47, 3.19.0-9-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: NVIDIA Corporation GK104 [GeForce GTX 660 Ti] [10de:1183] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:3662] InstallationDate: Installed on 2014-04-21 (329 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=d43fa8fe-98d7-4cbc-9f5a-845fe940823f ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-03-16 (0 days ago) dmi.bios.date: 05/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1605 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6T DELUXE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1605:bd05/19/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.59+git20150310.fcff9e21-0ubuntu0ricotz~utopic version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.0~git20150310.5750595c-0ubuntu0ricotz3~utopic version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.0~git20150310.5750595c-0ubuntu0ricotz3~utopic version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 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: Sun Mar 15 21:49:49 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputMicrosoft Microsoft IntelliMouse® Optical MOUSE, id 8 inputDarfon Wireless Keyboard & Mouse KEYBOARD, id 9 inputDarfon Wireless Keyboard & Mouse KEYBOARD, id 10 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output DVI-0 DisplayPort-0 HDMI-0 product id9896 vendor HWP xserver.version: 2:1.17.1-0ubuntu2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1432484/+subscriptions -- Mailing list: https://launchpad.net
[Touch-packages] [Bug 1432484] Re: ctrl+alt+t hot key doesn't open terminal
The result of above command: 't' -- 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/1432484 Title: ctrl+alt+t hot key doesn't open terminal Status in unity package in Ubuntu: Incomplete Bug description: 1) Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 2) unity: Installed: 7.3.1+15.04.20150227-0ubuntu1 Candidate: 7.3.1+15.04.20150227-0ubuntu1 Version table: *** 7.3.1+15.04.20150227-0ubuntu1 0 500 http://mirrors.accretive-networks.net/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status 3) ctrl+alt+t should open terminal 4) nothing happens ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20150227-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Mar 15 21:55:08 2015 DistUpgraded: 2015-03-15 19:32:57,918 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.19.0-9-generic, x86_64: installed nvidia-346-updates, 346.47, 3.19.0-9-generic, x86_64: installed nvidia-346-updates-uvm, 346.47, 3.19.0-9-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: NVIDIA Corporation GK104 [GeForce GTX 660 Ti] [10de:1183] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:3662] InstallationDate: Installed on 2014-04-21 (329 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=d43fa8fe-98d7-4cbc-9f5a-845fe940823f ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-03-16 (0 days ago) dmi.bios.date: 05/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1605 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6T DELUXE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1605:bd05/19/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.59+git20150310.fcff9e21-0ubuntu0ricotz~utopic version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.0~git20150310.5750595c-0ubuntu0ricotz3~utopic version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.0~git20150310.5750595c-0ubuntu0ricotz3~utopic version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 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: Sun Mar 15 21:49:49 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputMicrosoft Microsoft IntelliMouse® Optical MOUSE, id 8 inputDarfon Wireless Keyboard & Mouse KEYBOARD, id 9 inputDarfon Wireless Keyboard & Mouse KEYBOARD, id 10 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output DVI-0 DisplayPort-0 HDMI-0 product id9896 vendor HWP xserver.version: 2:1.17.1-0ubuntu2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1432484/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432177] Re: #1432171
*** This bug is a duplicate of bug 1432171 *** https://bugs.launchpad.net/bugs/1432171 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1432177 Title: #1432171 Status in systemd package in Ubuntu: Confirmed Bug description: I can confirm the bug with "Starting version 219 "systemd-boot" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432177/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1429913] Re: [P25, Realtek ALC282, Speaker, Internal] No sound at all 15.04
It's Looks like It's speakers problem ** Changed in: alsa-driver (Ubuntu) Status: New => Invalid -- 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/1429913 Title: [P25, Realtek ALC282, Speaker, Internal] No sound at all 15.04 Status in alsa-driver package in Ubuntu: Invalid Bug description: System: ubuntu 15.04 fresh install no sound, just beep sometimes when I press the mute/unmute on mute button. description: Audio device produit: Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller fabriquant: Intel Corporation identifiant matériel: 3 information bus: pci@:00:03.0 version: 06 bits: 64 bits horloge: 33MHz fonctionnalités: pm msi pciexpress bus_master cap_list configuration: driver=snd_hda_intel latency=0 ressources: irq:36 mémoire:f7414000-f7417fff ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: psychojau 1862 F pulseaudio /dev/snd/controlC0: psychojau 1862 F pulseaudio CurrentDesktop: Unity Date: Mon Mar 9 16:57:58 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-22 (15 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150221) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Audio interne - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: psychojau 1862 F pulseaudio /dev/snd/controlC0: psychojau 1862 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [P25, Realtek ALC282, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P25.010 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P25 dmi.board.vendor: GIGABYTE dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP25.010:bd05/19/2014:svnGIGABYTE:pnP25:pvrTobefilledbyO.E.M.:rvnGIGABYTE:rnP25:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: P25 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: GIGABYTE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1429913/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1362640] Re: Remove qtwebkit from touch image
The meta package update means webkit would drop from the images if the three remaining source packages would stop depending on it in the binaries installed on device. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1362640 Title: Remove qtwebkit from touch image Status in the base for Ubuntu mobile products: In Progress Status in Cordova Ubuntu: Fix Released Status in Web Browser App: Triaged Status in signon-ui package in Ubuntu: Triaged Status in ubuntu-html5-theme package in Ubuntu: Triaged Status in ubuntu-touch-meta package in Ubuntu: Fix Released Status in webbrowser-app package in Ubuntu: Triaged Bug description: The argument to remove this is based on the following: The qtwebkit webview is deprecated for our sdk and we will not be supporting it long term We are supporting an Oxide/Chromium solution for the Ubuntu.Webview This was done largely for security reasons The qtwebkit package is large and we would like to reduce image and install size We want to discourage app devs from using this api any longer, the review tools have indicated this for several months To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1362640/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432636] [NEW] Scopes with a helper app show up as apps in the store
Public bug reported: Click packages that have both a main scope and a helper app don't show up as Scopes in the app store, but instead they show up as apps. Eg: untappd scope. Also, after installation they show the "Open" button to start the helper app, instead of the "Search" button to show the scope. ** Affects: unity-scope-click (Ubuntu) Importance: Undecided Status: New -- 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/1432636 Title: Scopes with a helper app show up as apps in the store Status in unity-scope-click package in Ubuntu: New Bug description: Click packages that have both a main scope and a helper app don't show up as Scopes in the app store, but instead they show up as apps. Eg: untappd scope. Also, after installation they show the "Open" button to start the helper app, instead of the "Search" button to show the scope. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1432636/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1431041] Re: cups-browsed crashed with SIGSEGV in timeout_free()
Tim, he stack traces attached to comment #4, #5, and #6 seem to contain symbols. I am adding an Avahi task, to check whether it is perhaps really an Avahi problem. ** Changed in: cups-filters (Ubuntu) Status: Confirmed => Incomplete ** Also affects: avahi (Ubuntu) Importance: Undecided Status: New ** Changed in: avahi (Ubuntu) Status: New => Incomplete ** Changed in: avahi (Ubuntu) Importance: Undecided => High ** Changed in: cups-filters (Ubuntu) Importance: Medium => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1431041 Title: cups-browsed crashed with SIGSEGV in timeout_free() Status in avahi package in Ubuntu: Incomplete Status in cups-filters package in Ubuntu: Incomplete Bug description: happened during update. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: cups-browsed 1.0.67-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-8.8-generic 3.19.1 Uname: Linux 3.19.0-8-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CupsErrorLog: Date: Wed Mar 11 22:46:42 2015 ExecutablePath: /usr/sbin/cups-browsed InstallationDate: Installed on 2015-03-01 (10 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Alpha amd64 (20150224) Lpstat: device for WF-2530: dnssd://EPSON%20WF-2530%20Series._ipp._tcp.local/?uuid=cfe92100-67c4-11d4-a45f-b0e89258fe55 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Papersize: a4 PpdFiles: WF-2530: Epson WF-2530 Series - epson-inkjet-printer 1.0.0-1lsb3.2 (Seiko Epson Corporation LSB 3.2) ProcAttrCurrent: /usr/sbin/cups-browsed (enforce) ProcCmdline: /usr/sbin/cups-browsed ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-8-generic root=UUID=b98daf80-990b-45f5-aa26-844ab2d42789 ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7f03e1e4815a:movl $0x1,0xa8(%rax) PC (0x7f03e1e4815a) ok source "$0x1" ok destination "0xa8(%rax)" (0x00a8) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: cups-filters StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libavahi-glib.so.1 ?? () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 ?? () from /usr/lib/x86_64-linux-gnu/libavahi-glib.so.1 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: cups-browsed crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/08/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.70 dmi.board.name: 970DE3/U3S3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd04/08/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970DE3/U3S3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1431041/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432636] Re: Scopes with a helper app show up as apps in the store
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity-scope-click (Ubuntu) Status: New => Confirmed -- 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/1432636 Title: Scopes with a helper app show up as apps in the store Status in unity-scope-click package in Ubuntu: Confirmed Bug description: Click packages that have both a main scope and a helper app don't show up as Scopes in the app store, but instead they show up as apps. Eg: untappd scope. Also, after installation they show the "Open" button to start the helper app, instead of the "Search" button to show the scope. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1432636/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432646] [NEW] 14.04: thinpool metadata repair is not supported
Public bug reported: from https://answers.launchpad.net/ubuntu/+question/253962: I was looking into how to repair LVM2 thin pool metadata and noticed that Ubuntu ships with LVM2 tools 2.02.98-6. In 2.02.98-9 (in Fedora), the option to swap a thin pool metadata device was added: Add lvconvert support to swap thin pool metadata volume -- https://apps.fedoraproject.org/packages/lvm2/changelog. It's also present in the 2.02.99 release of LVM2 itself: http://upstream- tracker.org/changelogs/lvm2/2.02.99/changelog.html. Without this option, it's difficult (I can't figure out at the moment how, exactly) to take a thin pool metadata device offline to perform metadata repair. Would be great to include a fix for this in Ubuntu. ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1432646 Title: 14.04: thinpool metadata repair is not supported Status in lvm2 package in Ubuntu: New Bug description: from https://answers.launchpad.net/ubuntu/+question/253962: I was looking into how to repair LVM2 thin pool metadata and noticed that Ubuntu ships with LVM2 tools 2.02.98-6. In 2.02.98-9 (in Fedora), the option to swap a thin pool metadata device was added: Add lvconvert support to swap thin pool metadata volume -- https://apps.fedoraproject.org/packages/lvm2/changelog. It's also present in the 2.02.99 release of LVM2 itself: http://upstream- tracker.org/changelogs/lvm2/2.02.99/changelog.html. Without this option, it's difficult (I can't figure out at the moment how, exactly) to take a thin pool metadata device offline to perform metadata repair. Would be great to include a fix for this in Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1432646/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410260] Re: Image provider blocking the UI thread
** Branch linked: lp:ubuntu/vivid-proposed/thumbnailer -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to thumbnailer in Ubuntu. https://bugs.launchpad.net/bugs/1410260 Title: Image provider blocking the UI thread Status in Thumbnail generator for all kinds of files: In Progress Status in thumbnailer package in Ubuntu: In Progress Bug description: Steps: * add some music to your device (phone or desktop is fine) * [on desktop] install unity8 and run "unity8-dash -mousetouch" * bottom-swipe to the Manage screen * select the "My Music" scope * scroll quickly Expected: * scope scrolls smoothly, even if there's no images Current: * scope scrolling blocked for seconds at a time This seems to be most visible the first time, when images are not cached on disk yet. AFAIK the impact of this is elevated by the fact that Qt serializes requests to image providers, so when it's blocked to download one image, it will not continue to the next image etc. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: qtdeclarative5-ubuntu-thumbnailer0.1 1.3+15.04.20150106-0ubuntu1 Uname: Linux 3.18.0-031800rc4-generic x86_64 ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 13 14:26:35 2015 SourcePackage: thumbnailer SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/thumbnailer/+bug/1410260/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1394731] Re: [MIR] grilo-plugins
Steve, I'll continue to comment on this bug, since grilo is the proximate cause of this discussion. So you are correct that main implies Canonical support. In the case of a flavor-only package, Canonical presumably doesn't want to depend on a community flavor team, nor does that community flavor team presumably want to be depended on by Canonical in that way. I think the confusion is partly historical. Back in the day, flavors were much more "in the fold" and Canonical *was* willing to offer support for them (like Kubuntu/GNOME). So having a flavor team look after packages in main wasn't odd. After Canonical dropped support for Kubuntu/GNOME, they were demoted from main. But there are still shared packages that cause problems like this grilo bug. Where for purely technical/packaging reasons, Canonical gets asked to support a feature they don't use and may end up blocking that feature from being offered in a community flavor. Which neither side is thrilled with. Is there no way to mark a package in main as 'not supported?' I remember that we have some way to mark a universe package as supported. Can we do the inverse? That would let us promote grilo without putting Canonical on the hook. In any case, historically the MIR team did not *require* a team looking after the package. Only recently have we started blocking promotion based on that. And even then, we haven't required that the team be from Canonical. Should we loop someone from Canonical's support team in? See how they handle flavor packages like this? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grilo-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1394731 Title: [MIR] grilo-plugins Status in grilo-plugins package in Ubuntu: Fix Committed Bug description: Availability: In universe, builds on all archs Rational: grilo-plugins is now a dependency of totem and is hard to patch out. See lp:1393067 Security: No known CVEs Quality Assurance: No bugs in debian or ubuntu, most upstream bugs are feature requests. Active debian maintainer. Has watch file. Tests are run during build. UI standards: The package is translated upstream. Dependencies: All deps in main Standards compliance: No issues Maintenance: Actively maintained in debian. ubuntu-gnome team will subscribe in ubuntu. Background info: Grilo is a framework focused on making media discovery and browsing easy for application developers. This package contains it's plugins, including the tracker one, which is now needed by totem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grilo-plugins/+bug/1394731/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400297] Re: PageHeadState doens't correctly update head.contents
*** This bug is a duplicate of bug 1341814 *** https://bugs.launchpad.net/bugs/1341814 ** This bug has been marked a duplicate of bug 1341814 Using search in the header can sometimes have a text field from a different tab -- 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/1400297 Title: PageHeadState doens't correctly update head.contents Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu RTM: New Bug description: See this small example code: http://paste.ubuntu.com/9426167/ As you can see, I set both PageHeadState to change their 'contents' property when changing state. The expected behavior would be to have in the page head a Label when state is "default" and a TextEntry when in "search" state. However after some interactions (switching state 2 times) both the Label and the Entry are shown. As this doesn't happen with other properties, this should not happen with contents. I can set a 'visible' property to each component as workaround though. Thanks, Giulio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1400297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1341814] Re: Using search in the header can sometimes have a text field from a different tab
The bug is still present in RTM. There is a workaround here (thanks gcollura and nik90): http://paste.ubuntu.com/10609646/ Since we are switching rtm to vivid soon, it is probably not worth the effort to backport the fix. -- 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/1341814 Title: Using search in the header can sometimes have a text field from a different tab Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu RTM: New Bug description: In the linked branch there are two pages inside separate tabs. Both have searching enabled, when something is entered in the textfield the same text should appear in the label within the page. However upon switching between the tabs and using the textfield sometimes it appears as if the textfield from the other tab is shown as no text appears in the label (also note the tracing in the debug output). Test Plan: Select search Select text field Enter Te * Check Te appears in label Select back Switch to World Select search Select text field Do no enter anything Select back Switch to Hello Select search Select text field Enter Te * Notice label is not updated ** Repeat switching between tabs and entering data in the text field if the issue doesn't occur first time ** To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1341814/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432636] Re: Scopes with a helper app show up as apps in the store
I'd like to point out one thing: if a click package consists of more than one items (be it a scope, app, online accounts plugin, whatnot), it's something that users might not understand. "I installed just one app, why do I have two?" "I uninstalled the scope, where did my app go?" What is the use case we're solving for bundling multiple entities within the same click package? ** Description changed: Click packages that have both a main scope and a helper app don't show up as Scopes in the app store, but instead they show up as apps. Eg: untappd scope. Also, after installation they show the "Open" button to start the helper app, instead of the "Search" button to show the scope. + + The ML thread that started this: https://lists.launchpad.net/ubuntu- + phone/msg11465.html ** 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 unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1432636 Title: Scopes with a helper app show up as apps in the store Status in Ubuntu UX bugs: New Status in unity-scope-click package in Ubuntu: Confirmed Bug description: Click packages that have both a main scope and a helper app don't show up as Scopes in the app store, but instead they show up as apps. Eg: untappd scope. Also, after installation they show the "Open" button to start the helper app, instead of the "Search" button to show the scope. The ML thread that started this: https://lists.launchpad.net/ubuntu- phone/msg11465.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1432636/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1394731] Re: [MIR] grilo-plugins
Just a note: grilo itself isn't an issue as per see, but we have multiple examples of those instances I guess throughout the archive (even kubuntu things). As Steve told, let's focus on the main issue (actually I see many): 1. what to do in similar case where we have a build-dep/dep for build-time requirements where only community flavors are interested in? 2. how to ensure that the strict binary separation are not overlooked in the future? For instance, we have from the tracker source the libs in main, but not the tracker/miner services. -> The canonical desktop team are ok to "support" the libs, but not the services. -> What if one day, something starts to recommends/deps on the service. Then, an archive admin runs check-mir on the package and see " * tracker is in universe, but its source tracker is already in main; file an ubuntu-archive bug for promoting the current preferred alternative". The AA will then just promote it, without having the background info that the canonical desktop team didn't want to support the service, and we end up in the same situation. 3. what procedure to require the AA to follow in case of promotion/demotion so that we can get the historical context easily on launchpad? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grilo-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1394731 Title: [MIR] grilo-plugins Status in grilo-plugins package in Ubuntu: Fix Committed Bug description: Availability: In universe, builds on all archs Rational: grilo-plugins is now a dependency of totem and is hard to patch out. See lp:1393067 Security: No known CVEs Quality Assurance: No bugs in debian or ubuntu, most upstream bugs are feature requests. Active debian maintainer. Has watch file. Tests are run during build. UI standards: The package is translated upstream. Dependencies: All deps in main Standards compliance: No issues Maintenance: Actively maintained in debian. ubuntu-gnome team will subscribe in ubuntu. Background info: Grilo is a framework focused on making media discovery and browsing easy for application developers. This package contains it's plugins, including the tracker one, which is now needed by totem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grilo-plugins/+bug/1394731/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410260] Re: Image provider blocking the UI thread
This bug was fixed in the package thumbnailer - 1.3+15.04.20150312-0ubuntu1 --- thumbnailer (1.3+15.04.20150312-0ubuntu1) vivid; urgency=medium [ Albert Astals Cid ] * Use own QDBusConnection (LP: #1410260) -- CI Train BotThu, 12 Mar 2015 08:38:44 + ** Changed in: thumbnailer (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to thumbnailer in Ubuntu. https://bugs.launchpad.net/bugs/1410260 Title: Image provider blocking the UI thread Status in Thumbnail generator for all kinds of files: In Progress Status in thumbnailer package in Ubuntu: Fix Released Bug description: Steps: * add some music to your device (phone or desktop is fine) * [on desktop] install unity8 and run "unity8-dash -mousetouch" * bottom-swipe to the Manage screen * select the "My Music" scope * scroll quickly Expected: * scope scrolls smoothly, even if there's no images Current: * scope scrolling blocked for seconds at a time This seems to be most visible the first time, when images are not cached on disk yet. AFAIK the impact of this is elevated by the fact that Qt serializes requests to image providers, so when it's blocked to download one image, it will not continue to the next image etc. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: qtdeclarative5-ubuntu-thumbnailer0.1 1.3+15.04.20150106-0ubuntu1 Uname: Linux 3.18.0-031800rc4-generic x86_64 ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 13 14:26:35 2015 SourcePackage: thumbnailer SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/thumbnailer/+bug/1410260/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432484] Re: ctrl+alt+t hot key doesn't open terminal
Also, please paste the output of "update-alternatives --display x -terminal-emulator" -- 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/1432484 Title: ctrl+alt+t hot key doesn't open terminal Status in unity package in Ubuntu: Incomplete Bug description: 1) Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 2) unity: Installed: 7.3.1+15.04.20150227-0ubuntu1 Candidate: 7.3.1+15.04.20150227-0ubuntu1 Version table: *** 7.3.1+15.04.20150227-0ubuntu1 0 500 http://mirrors.accretive-networks.net/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status 3) ctrl+alt+t should open terminal 4) nothing happens ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20150227-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Mar 15 21:55:08 2015 DistUpgraded: 2015-03-15 19:32:57,918 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.19.0-9-generic, x86_64: installed nvidia-346-updates, 346.47, 3.19.0-9-generic, x86_64: installed nvidia-346-updates-uvm, 346.47, 3.19.0-9-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: NVIDIA Corporation GK104 [GeForce GTX 660 Ti] [10de:1183] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:3662] InstallationDate: Installed on 2014-04-21 (329 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=d43fa8fe-98d7-4cbc-9f5a-845fe940823f ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-03-16 (0 days ago) dmi.bios.date: 05/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1605 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6T DELUXE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1605:bd05/19/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.59+git20150310.fcff9e21-0ubuntu0ricotz~utopic version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.0~git20150310.5750595c-0ubuntu0ricotz3~utopic version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.0~git20150310.5750595c-0ubuntu0ricotz3~utopic version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 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: Sun Mar 15 21:49:49 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputMicrosoft Microsoft IntelliMouse® Optical MOUSE, id 8 inputDarfon Wireless Keyboard & Mouse KEYBOARD, id 9 inputDarfon Wireless Keyboard & Mouse KEYBOARD, id 10 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output DVI-0 DisplayPort-0 HDMI-0 product id9896 vendor HWP xserver.version: 2:1.17.1-0ubuntu2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1432484/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1394731] Re: [MIR] grilo-plugins
I thought for #2/#3, the AA is supposed to look up the old MIR bug and read the relevant history. At least, that's the only procedure we can follow with current tools, to my knowledge. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grilo-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1394731 Title: [MIR] grilo-plugins Status in grilo-plugins package in Ubuntu: Fix Committed Bug description: Availability: In universe, builds on all archs Rational: grilo-plugins is now a dependency of totem and is hard to patch out. See lp:1393067 Security: No known CVEs Quality Assurance: No bugs in debian or ubuntu, most upstream bugs are feature requests. Active debian maintainer. Has watch file. Tests are run during build. UI standards: The package is translated upstream. Dependencies: All deps in main Standards compliance: No issues Maintenance: Actively maintained in debian. ubuntu-gnome team will subscribe in ubuntu. Background info: Grilo is a framework focused on making media discovery and browsing easy for application developers. This package contains it's plugins, including the tracker one, which is now needed by totem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grilo-plugins/+bug/1394731/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1328183] Re: User-Agent string results in poor UX on web
I’m changing the status of the bug to confirmed/triaged to acknoledge the issue, and to serve as a reference for similar future reports. Note however that as discussed at length already, there’s no good fix for this. ** Also affects: webbrowser-app Importance: Undecided Status: New ** Changed in: webbrowser-app Status: New => Triaged ** Changed in: webbrowser-app (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1328183 Title: User-Agent string results in poor UX on web Status in Web Browser App: Triaged Status in webbrowser-app package in Ubuntu: Confirmed Bug description: The User-Agent string for the browser is similar enough to the Android browser User-Agent, that it creates a poor experience when browsing the web on an Ubuntu phone. An inordinately large number of web sites persistently advertise to "install our app" instead of providing the best web experience; an app which cannot be installed. This is exacerbated by the pervasiveness of webapps on Ubuntu phone, which simply embed the mobile web site with webapp-container, and still result in seeing such advertisements, despite the fact that the "app" on Ubuntu is already installed, and the Android apps being advertised are simply not installable. Having all the big web sites telling users of Ubuntu that they should be using Android instead, is not very good for the user experience at all. To manage notifications about this bug go to: https://bugs.launchpad.net/webbrowser-app/+bug/1328183/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432484] Re: ctrl+alt+t hot key doesn't open terminal
Also, please attach $HOME/.cache/upstart/unity-settings-daemon.log -- 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/1432484 Title: ctrl+alt+t hot key doesn't open terminal Status in unity package in Ubuntu: Incomplete Bug description: 1) Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 2) unity: Installed: 7.3.1+15.04.20150227-0ubuntu1 Candidate: 7.3.1+15.04.20150227-0ubuntu1 Version table: *** 7.3.1+15.04.20150227-0ubuntu1 0 500 http://mirrors.accretive-networks.net/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status 3) ctrl+alt+t should open terminal 4) nothing happens ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20150227-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Mar 15 21:55:08 2015 DistUpgraded: 2015-03-15 19:32:57,918 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.19.0-9-generic, x86_64: installed nvidia-346-updates, 346.47, 3.19.0-9-generic, x86_64: installed nvidia-346-updates-uvm, 346.47, 3.19.0-9-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: NVIDIA Corporation GK104 [GeForce GTX 660 Ti] [10de:1183] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:3662] InstallationDate: Installed on 2014-04-21 (329 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=d43fa8fe-98d7-4cbc-9f5a-845fe940823f ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-03-16 (0 days ago) dmi.bios.date: 05/19/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1605 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6T DELUXE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1605:bd05/19/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.59+git20150310.fcff9e21-0ubuntu0ricotz~utopic version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.0~git20150310.5750595c-0ubuntu0ricotz3~utopic version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.0~git20150310.5750595c-0ubuntu0ricotz3~utopic version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 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: Sun Mar 15 21:49:49 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputMicrosoft Microsoft IntelliMouse® Optical MOUSE, id 8 inputDarfon Wireless Keyboard & Mouse KEYBOARD, id 9 inputDarfon Wireless Keyboard & Mouse KEYBOARD, id 10 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output DVI-0 DisplayPort-0 HDMI-0 product id9896 vendor HWP xserver.version: 2:1.17.1-0ubuntu2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1432484/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1410260] Re: Image provider blocking the UI thread
** Changed in: thumbnailer Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to thumbnailer in Ubuntu. https://bugs.launchpad.net/bugs/1410260 Title: Image provider blocking the UI thread Status in Thumbnail generator for all kinds of files: Fix Released Status in thumbnailer package in Ubuntu: Fix Released Bug description: Steps: * add some music to your device (phone or desktop is fine) * [on desktop] install unity8 and run "unity8-dash -mousetouch" * bottom-swipe to the Manage screen * select the "My Music" scope * scroll quickly Expected: * scope scrolls smoothly, even if there's no images Current: * scope scrolling blocked for seconds at a time This seems to be most visible the first time, when images are not cached on disk yet. AFAIK the impact of this is elevated by the fact that Qt serializes requests to image providers, so when it's blocked to download one image, it will not continue to the next image etc. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: qtdeclarative5-ubuntu-thumbnailer0.1 1.3+15.04.20150106-0ubuntu1 Uname: Linux 3.18.0-031800rc4-generic x86_64 ApportVersion: 2.15.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 13 14:26:35 2015 SourcePackage: thumbnailer SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/thumbnailer/+bug/1410260/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1409696] Re: There is no 'headset' icon in the indicator bar when a headset is connected
Is there any clear on this bug? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1409696 Title: There is no 'headset' icon in the indicator bar when a headset is connected Status in Ubuntu UX bugs: Triaged Status in indicator-sound package in Ubuntu: Incomplete Bug description: Reported by an OEM who's phone currently does have such an icon, there is no visual indication that a wired headset has been connected to the phone and in use: [Procedures] 1.insert the earphone [Expect results] should be has earphone icon and notification shows in Status Bar [Actual results] There is no earphone icon in indicator Bar when inserting the earphone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1409696/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432681] [NEW] Lubuntu boot very slow
Public bug reported: Lubuntu boot very slow after last update and sometimes it spontaneously crash and i must re-boot ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic i686 ApportVersion: 2.16.2-0ubuntu3 Architecture: i386 CurrentDesktop: LXDE Date: Mon Mar 16 15:46:50 2015 InstallationDate: Installed on 2013-03-16 (730 days ago) InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-9-generic root=/dev/mapper/lubuntu-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2015-02-27 (16 days ago) dmi.bios.date: 07/25/2005 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: K8T800-8237 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: 1.x dmi.chassis.type: 3 dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd07/25/2005:svn:pn:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnK8T800-8237:rvr1.x:cvn:ct3:cvr: ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 vivid ** Description changed: - Lubuntu boot very slow after last update + Lubuntu boot very slow after last update and sometimes it spontaneously + crash and i must re-boot ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic i686 ApportVersion: 2.16.2-0ubuntu3 Architecture: i386 CurrentDesktop: LXDE Date: Mon Mar 16 15:46:50 2015 InstallationDate: Installed on 2013-03-16 (730 days ago) InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-9-generic root=/dev/mapper/lubuntu-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2015-02-27 (16 days ago) dmi.bios.date: 07/25/2005 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: K8T800-8237 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: 1.x dmi.chassis.type: 3 dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd07/25/2005:svn:pn:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnK8T800-8237:rvr1.x:cvn:ct3:cvr: -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1432681 Title: Lubuntu boot very slow Status in systemd package in Ubuntu: New Bug description: Lubuntu boot very slow after last update and sometimes it spontaneously crash and i must re-boot ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic i686 ApportVersion: 2.16.2-0ubuntu3 Architecture: i386 CurrentDesktop: LXDE Date: Mon Mar 16 15:46:50 2015 InstallationDate: Installed on 2013-03-16 (730 days ago) InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.1) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-9-generic root=/dev/mapper/lubuntu-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2015-02-27 (16 days ago) dmi.bios.date: 07/25/2005 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: K8T800-8237 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: 1.x dmi.chassis.type: 3 dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd07/25/2005:svn:pn:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnK8T800-8237:rvr1.x:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432681/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1423185] Re: Calendar app crash
This bug was fixed in the package qtorganizer5-eds - 0.1.1+15.04.20150309-0ubuntu1 --- qtorganizer5-eds (0.1.1+15.04.20150309-0ubuntu1) vivid; urgency=medium [ Renato Araujo Oliveira Filho ] * Fixed engine crash while destroying and requests still running. (LP: #1423185) -- CI Train BotMon, 09 Mar 2015 13:48:42 + ** Changed in: qtorganizer5-eds (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtorganizer5-eds in Ubuntu. https://bugs.launchpad.net/bugs/1423185 Title: Calendar app crash Status in Qt Organizer - EDS plugin: New Status in Calendar application for Ubuntu devices: In Progress Status in qtorganizer5-eds package in Ubuntu: Fix Released Bug description: Tapping on a day in Year view, crashed calendar app. See attached file. TEST CASE: 1. Switch to 'Year' view 2. Tap on any day 3. Repeat steps 1 and 2 up to 10 times ACTUAL RESULT The app crashes after a few attempts To manage notifications about this bug go to: https://bugs.launchpad.net/qtorganizer5-eds/+bug/1423185/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432683] [NEW] apt-get install lxc doesn't load required apparmor profiles
Public bug reported: I'm trying to use LXC on my openstack instance which runs vivid daily: $ sudo apt-get install lxc -y $ sudo lxc-create -t ubuntu-cloud --name=vivid -- --flush-cache --stream=daily --release=vivid $ sudo lxc-start --name vivid --logfile=lxc.log lxc-start: lxc_start.c: main: 344 The container failed to start. lxc-start: lxc_start.c: main: 346 To get more details, run the container in foreground mode. lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options. In the log file (lxc.log) I observe the following error: lxc-start 1426516387.814 ERRORlxc_apparmor - lsm/apparmor.c:apparmor_process_label_set:183 - No such file or directory - failed to change apparmor profile to lxc-container-default This profile *exists* under /etc/apparmor.d/lxc/lxc-default but was not loaded appropriately. This issue disappears if I: (a) reload apparmor profile manually: sudo /etc/init.d/apparmor reload or (b) reboot the instance I'd expect that 'apt-get install lxc' has to load all appropriate apparmor profiles to allow starting containers w/o profile reloading / rebooting. ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Description changed: I'm trying to use LXC on my openstack instance which runs vivid daily: $ sudo apt-get install lxc -y $ sudo lxc-create -t ubuntu-cloud --name=vivid -- --flush-cache --stream=daily --release=vivid $ sudo lxc-start --name vivid --logfile=lxc.log lxc-start: lxc_start.c: main: 344 The container failed to start. lxc-start: lxc_start.c: main: 346 To get more details, run the container in foreground mode. lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options. In the log file (lxc.log) I observe the following error: lxc-start 1426516387.814 ERRORlxc_apparmor - lsm/apparmor.c:apparmor_process_label_set:183 - No such file or directory - failed to change apparmor profile to lxc-container-default This profile *exists* under /etc/apparmor.d/lxc/lxc-default but was not loaded appropriately. This issue disappears if I: (a) reload apparmor profile manually: sudo /etc/init.d/apparmor reload or (b) reboot the instance - I'd expert that 'apt-get install lxc' has to load all appropriate + I'd expect that 'apt-get install lxc' has to load all appropriate apparmor profiles to allow starting containers w/o profile reloading / rebooting. -- 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/1432683 Title: apt-get install lxc doesn't load required apparmor profiles Status in lxc package in Ubuntu: New Bug description: I'm trying to use LXC on my openstack instance which runs vivid daily: $ sudo apt-get install lxc -y $ sudo lxc-create -t ubuntu-cloud --name=vivid -- --flush-cache --stream=daily --release=vivid $ sudo lxc-start --name vivid --logfile=lxc.log lxc-start: lxc_start.c: main: 344 The container failed to start. lxc-start: lxc_start.c: main: 346 To get more details, run the container in foreground mode. lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options. In the log file (lxc.log) I observe the following error: lxc-start 1426516387.814 ERRORlxc_apparmor - lsm/apparmor.c:apparmor_process_label_set:183 - No such file or directory - failed to change apparmor profile to lxc-container-default This profile *exists* under /etc/apparmor.d/lxc/lxc-default but was not loaded appropriately. This issue disappears if I: (a) reload apparmor profile manually: sudo /etc/init.d/apparmor reload or (b) reboot the instance I'd expect that 'apt-get install lxc' has to load all appropriate apparmor profiles to allow starting containers w/o profile reloading / rebooting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1432683/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1420556] Comment bridged from LTC Bugzilla
--- Comment From emach...@br.ibm.com 2015-03-16 14:58 EDT---
Hi,
any news regarding this issue? Is there anything we can do from our side
to help?
I managed to retest this using community gcc 4.9 and the aforementioned
problem of the unexpected place where 'breakpoint main' hits is not
reproducible, as well as the additional .loc directive is not included
in the assembler code.
Thanks for your support.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1420556
Title:
gdb source tests are failing in Ubuntu 15.04
Status in gdb package in Ubuntu:
New
Bug description:
---Problem Description---
gdb source tests are failing in Ubuntu 15.04
---uname output---
Linux ubuntu 3.18.0-12-generic #13-Ubuntu SMP Thu Jan 29 13:44:26 UTC 2015
ppc64le ppc64le ppc64le GNU/Linux
Machine Type = P8
---Steps to Reproduce---
Install a Power VM LPAR with Ubuntu 15.04 ISO.
Then install gdb source and build and execute the same.
root@ubuntu:~# apt-get source gdb
root@ubuntu:~# cd gdb-7.8.2/
root@ubuntu:~/gdb-7.8.2# dpkg-buildpackage -b
=== gdb Summary ===
# of expected passes25147
# of unexpected failures280
# of unexpected successes 2
# of expected failures 66
# of unknown successes 1
# of known failures 59
# of unresolved testcases 11
# of untested testcases 21
# of unsupported tests 99
/root/gdb-7.8.2/build/objdir/gdb/testsuite/../../gdb/gdb version
7.8.2-0ubuntu1) -nw -nx -data-directory
/root/gdb-7.8.2/build/objdir/gdb/testsuite/../data-directory
Package: gdb-7.8.2-0ubuntu1
I've reproduced the tests and looking at gdb.log, noticed that for
some reason breakpoints for main() are being hit in an unexpected
place and this is causing a lot of testcase failures. Also, this
problem happens only when using gcc 4.9 (Ubuntu 15.04 default); it's
not reproducible on gcc 4.8 or 5. This is still being investigated.
Moreover, in the gdb.python/python.exp specifically, there is this
commit 55cfb2c4c8accd5031fd7c8167988fc4624e847c from upstream gdb that
fixes the testcase, removing 19 of the unexpected failures.
I've created this testcase that exemplifies the issue with the
'breakpoint main' hit the unexpected place:
ubuntu@ubuntu:~$ cat array.c
int main (void)
{
int array[1];
return 0;
}
ubuntu@ubuntu:~$ gcc array.c -g -o array-4.9
ubuntu@ubuntu:~$ gdb -q ./array-4.9 -ex 'break main' -ex run
Reading symbols from ./array-4.9...done.
Breakpoint 1 at 0x160c: file array.c, line 3.
Starting program: /home/ubuntu/array-4.9
Breakpoint 1, main () at array.c:3
3 {
(gdb)
While with gcc-4.8, gdb stops at the expected place:
ubuntu@ubuntu:~$ gcc-4.8 array.c -g -o array-4.8
ubuntu@ubuntu:~$ gdb -q ./array-4.8 -ex 'break main' -ex run
Reading symbols from ./array-4.8...done.
Breakpoint 1 at 0x15a0: file array.c, line 6.
Starting program: /home/ubuntu/array-4.8
Breakpoint 1, main () at array.c:6
6 return 0;
(gdb)
Comparing the assembly output generated by both gcc's, we can also
notice a repeated '.loc 1 3 0' in the code that seems to cause this
misplaced breakpoint:
ubuntu@ubuntu:~$ gcc array.c -g -o array-4.9.s -S
ubuntu@ubuntu:~$ cat array-4.9.s
(...)
main:
.LFB0:
.file 1 "array.c"
.loc 1 3 0
.cfi_startproc
0: addis 2,12,.TOC.-0b@ha
addi 2,2,.TOC.-0b@l
.localentry main,.-main
mflr 0
std 0,16(1)
std 31,-8(1)
stdu 1,-64(1)
.cfi_def_cfa_offset 64
.cfi_offset 65, 16
.cfi_offset 31, -8
mr 31,1
.cfi_def_cfa_register 31
.loc 1 3 0 <-- repeated .loc
ld 9,-28688(13)
std 9,40(31)
li 9,0
.loc 1 6 0
li 9,0
.loc 1 7 0
mr 3,9
ld 10,40(31)
ld 9,-28688(13)
cmpld 7,10,9
li 10,0
li 9,0
beq 7,.L3
bl __stack_chk_fail
nop
.L3:
(...)
If this additional .loc is removed, gdb is able to hit the breakpoint at the
correct place.
Moreover, it might be worth mentioning that this additional .loc doesn't
appear on gcc-5 output too, where this breakpoint issue is not reproducible as
well.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1420556/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1424609] Re: Can not print in landscape
Another workaround: 1. Print to pdf file choosing the format A5 Portrait; 2. Open the pdf and print choosing the format A4 Landscape. -- 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/1424609 Title: Can not print in landscape Status in cups package in Ubuntu: New Bug description: All jobs are printed in portrait. No matter which file is (pdf, odt, jpg). Even from command line (lp -o landscape file.pdf) the problem persist. Different paper sizes also do not matter (A4, A5). Changing printer makes no difference. Changing connection (usb, network attached) also makes no difference. Attached an example file that could not be printed in landscape. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.2-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CupsErrorLog: E [23/Feb/2015:08:15:48 -0300] [cups-deviced] PID 13945 (mfp) stopped with status 127! CurrentDesktop: Unity Date: Mon Feb 23 08:48:37 2015 InstallationDate: Installed on 2014-05-01 (297 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) KernLog: Lpstat: device for ML-1860: usb://Samsung/ML-1860%20Series?serial=Z5M7BDAB501185X. MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC Papersize: a5 PpdFiles: ML-1860: Samsung ML-1860 Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=/dev/mapper/ubuntu--vg-root ro SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/03/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.13 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3659 dmi.board.vendor: Hewlett-Packard dmi.board.version: 32.23 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.13:bd12/03/2009:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr049D212412102:rvnHewlett-Packard:rn3659:rvr32.23:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: 049D212412102 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1424609/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432689] [NEW] No indicator-sound sometimes after switching language
Public bug reported: Sometimes the indicator-sound does not start correctly (only a 'gear' if you expand the notification bar and no 'speaker' icon), this was found while testing changing language for the music-app and it should be noted that in the instance where the indicator didn't start I couldn't also play and audio. Steps: 1) Start phone, note if the indicator-sound has started correct (with an icon) 2) Open system-settings->Language & Text->Display language 3) Change the language to something else (I cycled through EN, ES, FR) and accept the reboot 4) Upon reboot go back to step 1 until the indicator starts incorrectly (usually happens within 5-10 boots for me) When the issue occurred this was in my indicator-sound.log (process:2761): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed indicator-sound stop/pre-start, process 3380 $ system-image-cli -i current build number: 214 device name: mako channel: ubuntu-touch/ubuntu-rtm/devel-proposed alias: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-03-12 01:42:23 version version: 214 version ubuntu: 20150312 version device: 20150116 version custom: mako-1.1 ** Affects: indicator-sound (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1432689 Title: No indicator-sound sometimes after switching language Status in indicator-sound package in Ubuntu: New Bug description: Sometimes the indicator-sound does not start correctly (only a 'gear' if you expand the notification bar and no 'speaker' icon), this was found while testing changing language for the music-app and it should be noted that in the instance where the indicator didn't start I couldn't also play and audio. Steps: 1) Start phone, note if the indicator-sound has started correct (with an icon) 2) Open system-settings->Language & Text->Display language 3) Change the language to something else (I cycled through EN, ES, FR) and accept the reboot 4) Upon reboot go back to step 1 until the indicator starts incorrectly (usually happens within 5-10 boots for me) When the issue occurred this was in my indicator-sound.log (process:2761): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed indicator-sound stop/pre-start, process 3380 $ system-image-cli -i current build number: 214 device name: mako channel: ubuntu-touch/ubuntu-rtm/devel-proposed alias: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-03-12 01:42:23 version version: 214 version ubuntu: 20150312 version device: 20150116 version custom: mako-1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1432689/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393542] Re: SRU: exfat not detected by blkid
Here I'm attaching a debdiff with the backported fix. ** Changed in: util-linux (Ubuntu Utopic) Assignee: (unassigned) => Felipe Reyes (freyes) ** Summary changed: - SRU: exfat not detected by blkid + [SRU] exfat not detected by blkid ** Patch added: "lp_1393542_utopic.debdiff" https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1393542/+attachment/4347170/+files/lp_1393542_utopic.debdiff ** Changed in: util-linux (Ubuntu Utopic) Status: Confirmed => In Progress ** Description changed: [Impact] Due to a upstream bug blkid is unable to detect exfat partitions. This breaks proper detection and automount of exfat formatted partitions (e.g. SD cards or USB sticks) in Ubuntu 14.10. [Test Case] Insert an exfat formatted SD Card (card is neither detected nor automounted) or run as root: blkid [partition] + Without the fix: + sudo blkid -p /dev/sde1 + /dev/sde1: ambivalent result (probably more filesystems on the device, use wipefs(8) to see more details) + + With the fix applied: + sudo blkid -p /dev/sde1 + /dev/sde1: UUID="BE12-8543" VERSION="1.0" TYPE="exfat" USAGE="filesystem" PTTYPE="dos" PART_ENTRY_SCHEME="dos" PART_ENTRY_TYPE="0x7" PART_ENTRY_FLAGS="0x80" PART_ENTRY_NUMBER="1" PART_ENTRY_OFFSET="32768" PART_ENTRY_SIZE="124702720" PART_ENTRY_DISK="8:64" + [Regression Potential] None known, the bugfix is simple and part of already released upstream stable release (2.25.2). [Other Info] Bug reference: bug #1389021 Upstream issue: https://github.com/karelzak/util-linux/issues/119 Upstream bugfix commit: https://github.com/karelzak/util-linux/commit/98b539c25caede8534ffaf06e67a694eeb3bc6cb ** Tags added: cts -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1393542 Title: [SRU] exfat not detected by blkid Status in util-linux package in Ubuntu: Confirmed Status in util-linux source package in Trusty: Invalid Status in util-linux source package in Utopic: In Progress Bug description: [Impact] Due to a upstream bug blkid is unable to detect exfat partitions. This breaks proper detection and automount of exfat formatted partitions (e.g. SD cards or USB sticks) in Ubuntu 14.10. [Test Case] Insert an exfat formatted SD Card (card is neither detected nor automounted) or run as root: blkid [partition] Without the fix: sudo blkid -p /dev/sde1 /dev/sde1: ambivalent result (probably more filesystems on the device, use wipefs(8) to see more details) With the fix applied: sudo blkid -p /dev/sde1 /dev/sde1: UUID="BE12-8543" VERSION="1.0" TYPE="exfat" USAGE="filesystem" PTTYPE="dos" PART_ENTRY_SCHEME="dos" PART_ENTRY_TYPE="0x7" PART_ENTRY_FLAGS="0x80" PART_ENTRY_NUMBER="1" PART_ENTRY_OFFSET="32768" PART_ENTRY_SIZE="124702720" PART_ENTRY_DISK="8:64" [Regression Potential] None known, the bugfix is simple and part of already released upstream stable release (2.25.2). [Other Info] Bug reference: bug #1389021 Upstream issue: https://github.com/karelzak/util-linux/issues/119 Upstream bugfix commit: https://github.com/karelzak/util-linux/commit/98b539c25caede8534ffaf06e67a694eeb3bc6cb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1393542/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1395724] Re: Cannot type into account login input boxes
Hi, I have reproduced it while entering a facebook account or a ubuntu account from telegram to active the notifications. I am currently testing on r19. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1395724 Title: Cannot type into account login input boxes Status in the base for Ubuntu mobile products: Fix Released Status in ubuntu-system-settings-online-accounts package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Triaged Status in ubuntu-system-settings-online-accounts package in Ubuntu RTM: Confirmed Bug description: 1. Open system settings and go to accounts. 2. tap on 'Google' to add a google account 3. When the login page opens drag down the indicator bar from the top 4. Now try to type into the username/password boxes. What happens: OSK does not appear to type in there. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: ubuntu-system-settings-online-accounts 0.5+14.10.20141029~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Mon Nov 24 13:29:58 2014 InstallationDate: Installed on 2014-11-21 (2 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141121-220606) SourcePackage: ubuntu-system-settings-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1395724/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432696] [NEW] [SDK] Bottom edge header improvement
Public bug reported: When user does a bottom edge gesture to show a new view (Address Book, Dialer, Clock, etc) the new header should never have a chevron pointing left, as it seems to suggest the wrong direction for the movement. The header of the new View should always have a chevron pointing down. Also, it should allow people using a gesture and dismiss the new screen by dragging or swiping the title of the header downward UX here: https://www.dropbox.com/s/ypmhej7ie2hrc9a/down_chevron_for_manage_dash_01%28wireframe%29.tiff?dl=0 VD: https://www.dropbox.com/s/1wuihy8tf7no7iw/Music_Down_Chevron.jpg?dl=0 ** Affects: clock Importance: Undecided Status: New ** Affects: dekko Importance: Undecided Status: New ** Affects: ubuntu-calendar-app Importance: Undecided Status: New ** Affects: ubuntu-ux Importance: High Assignee: Giorgio Venturi (giorgio-venturi) Status: Fix Committed ** Affects: address-book-app (Ubuntu) Importance: Undecided Status: New ** Affects: dialer-app (Ubuntu) Importance: Undecided Status: New ** Affects: messaging-app (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-clock-app (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New ** Also affects: dekko Importance: Undecided Status: New ** Also affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New ** Summary changed: - [SDK] Bottom edge header refinement + [SDK] Bottom edge header improvement ** Description changed: When user does a bottom edge gesture to show a new view (Address Book, Dialer, Clock, etc) the new header should never have a chevron pointing left, as it seems to suggest the wrong direction for the movement. The header of the new View should always have a chevron pointing down. - Also, it should allow people using a gesture to dismiss the new screen + Also, it should allow people using a gesture and dismiss the new screen by dragging or swiping the title of the header downward UX here: https://www.dropbox.com/s/ypmhej7ie2hrc9a/down_chevron_for_manage_dash_01%28wireframe%29.tiff?dl=0 VD: https://www.dropbox.com/s/1wuihy8tf7no7iw/Music_Down_Chevron.jpg?dl=0 ** Also affects: address-book-app (Ubuntu) Importance: Undecided Status: New ** Also affects: dialer-app (Ubuntu) Importance: Undecided Status: New ** Also affects: messaging-app (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-clock-app (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-calendar-app 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/1432696 Title: [SDK] Bottom edge header improvement Status in Clock: New Status in Dekko: New Status in Calendar application for Ubuntu devices: New Status in Ubuntu UX bugs: Fix Committed Status in address-book-app package in Ubuntu: New Status in dialer-app package in Ubuntu: New Status in messaging-app package in Ubuntu: New Status in ubuntu-clock-app package in Ubuntu: New Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: When user does a bottom edge gesture to show a new view (Address Book, Dialer, Clock, etc) the new header should never have a chevron pointing left, as it seems to suggest the wrong direction for the movement. The header of the new View should always have a chevron pointing down. Also, it should allow people using a gesture and dismiss the new screen by dragging or swiping the title of the header downward UX here: https://www.dropbox.com/s/ypmhej7ie2hrc9a/down_chevron_for_manage_dash_01%28wireframe%29.tiff?dl=0 VD: https://www.dropbox.com/s/1wuihy8tf7no7iw/Music_Down_Chevron.jpg?dl=0 To manage notifications about this bug go to: https://bugs.launchpad.net/clock/+bug/1432696/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1330959] Re: Art in cards with backgrounds are Ubuntu-shaped
** Changed in: unity8 (Ubuntu) Assignee: (unassigned) => Andrea Cimitan (cimi) ** Changed in: unity8 (Ubuntu RTM) Assignee: (unassigned) => Andrea Cimitan (cimi) -- 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/1330959 Title: Art in cards with backgrounds are Ubuntu-shaped Status in the base for Ubuntu mobile products: Confirmed Status in unity8 package in Ubuntu: Triaged Status in unity8 package in Ubuntu RTM: New Bug description: When a card has its background enabled, the art should not have its bottom edge shaped. Until the new shape item comes, we should probably use the UbuntuShapeForItem component. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1330959/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432696] Re: [SDK] Bottom edge header improvement
** Also affects: clock Importance: Undecided Status: New ** No longer affects: clock -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1432696 Title: [SDK] Bottom edge header improvement Status in Dekko: New Status in Calendar application for Ubuntu devices: New Status in Ubuntu UX bugs: Fix Committed Status in address-book-app package in Ubuntu: New Status in dialer-app package in Ubuntu: New Status in messaging-app package in Ubuntu: New Status in ubuntu-clock-app package in Ubuntu: New Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: When user does a bottom edge gesture to show a new view (Address Book, Dialer, Clock, etc) the new header should never have a chevron pointing left, as it seems to suggest the wrong direction for the movement. The header of the new View should always have a chevron pointing down. Also, it should allow people using a gesture and dismiss the new screen by dragging or swiping the title of the header downward UX here: https://www.dropbox.com/s/ypmhej7ie2hrc9a/down_chevron_for_manage_dash_01%28wireframe%29.tiff?dl=0 VD: https://www.dropbox.com/s/1wuihy8tf7no7iw/Music_Down_Chevron.jpg?dl=0 To manage notifications about this bug go to: https://bugs.launchpad.net/dekko/+bug/1432696/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390393] Re: It's too easy to trigger a volume notification when taking a screenshot
Hi, the screenshot problem has been fixed, but then the device is locked. It should recognized that when pressing the three bottoms at the same time, it should just take an screenshot. -- 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/1390393 Title: It's too easy to trigger a volume notification when taking a screenshot Status in the base for Ubuntu mobile products: Fix Released Status in unity8 package in Ubuntu: Fix Released Status in unity8 package in Ubuntu RTM: Fix Released Bug description: On Mako, I'm unable to take a screenshot (Vol up + Vol down) without changing the volume, which causes a notification to appear on the screenshot, and changes the volume when taking a screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1390393/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1422359] Re: heimdal-kdc: kdc process leaks memory
I have now installed the following packages on Trusty (by asking for heimdal-kdc): Do you want to continue? [Y/n] Get:1 http://se.archive.ubuntu.com/ubuntu/ trusty/main krb5-config all 2.3 [23.4 kB] Get:2 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main libhdb9-heimdal amd64 1.6~git20131207+dfsg-1ubuntu1.1 [59.2 kB] Get:3 http://se.archive.ubuntu.com/ubuntu/ trusty/main libfile-copy-recursive-perl all 0.38-1 [20.6 kB] Get:4 http://se.archive.ubuntu.com/ubuntu/ trusty/main update-inetd all 4.43 [19.2 kB] Get:5 http://se.archive.ubuntu.com/ubuntu/ trusty/main openbsd-inetd amd64 0.20091229-2ubuntu3 [30.8 kB] Get:6 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main libkadm5clnt7-heimdal amd64 1.6~git20131207+dfsg-1ubuntu1.1 [18.5 kB] Get:7 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main libkadm5srv8-heimdal amd64 1.6~git20131207+dfsg-1ubuntu1.1 [28.8 kB] Get:8 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main libkafs0-heimdal amd64 1.6~git20131207+dfsg-1ubuntu1.1 [15.1 kB] Get:9 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main libkdc2-heimdal amd64 1.6~git20131207+dfsg-1ubuntu1.1 [52.8 kB] Get:10 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main libotp0-heimdal amd64 1.6~git20131207+dfsg-1ubuntu1.1 [29.8 kB] Get:11 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main libsl0-heimdal amd64 1.6~git20131207+dfsg-1ubuntu1.1 [13.3 kB] Get:12 http://archive.ubuntu.com/ubuntu/ trusty-proposed/universe heimdal-clients amd64 1.6~git20131207+dfsg-1ubuntu1.1 [264 kB] Get:13 http://archive.ubuntu.com/ubuntu/ trusty-proposed/universe heimdal-kdc amd64 1.6~git20131207+dfsg-1ubuntu1.1 [91.9 kB] Fetched 667 kB in 2s (284 kB/s) I can confirm these packages fix the leak on Trusty. ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1422359 Title: heimdal-kdc: kdc process leaks memory Status in heimdal package in Ubuntu: Fix Released Status in heimdal source package in Trusty: Fix Committed Status in heimdal source package in Utopic: Fix Committed Status in heimdal package in Debian: Fix Released Bug description: SRU information appears in comment #7: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1422359/comments/7 I have a KDC running Trusty Tahr. The machine has been up for 74 days and the kdc process has allocated almost all of the 8GB RAM available to the machine. When asking about this on heimdal-discuss, GALAMBOS Daniel pointed me to a relevant bug report (and fix) for Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746486 It seems likely this is the same problem I am experiencing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1422359/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1044927] Re: Laucher background not blurred when Dash is opened
This seems fixed as no new activity has occurred for this bug in some time. I also cannot reproduce, albeit, on an Intel graphics machine. Going to mark it Fixed Released. We can either reopen this bug or submit a new bug report if it still occurs for anyone. ** Changed in: unity Status: Incomplete => Fix Released ** Changed in: unity Milestone: 7.3.2 => None ** Changed in: unity/7.2 Status: Incomplete => Fix Released ** Changed in: unity (Ubuntu) Status: Incomplete => Fix Released -- 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/1044927 Title: Laucher background not blurred when Dash is opened Status in Unity: Fix Released Status in Unity 7.2 series: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: The launcher background is occasionally left without blur (see attached screenshot). This is a regression after updating unity from version 6.2.0-0ubuntu4 to 6.4.0-0ubuntu1. Steps to reproduce: Make sure that launcher is set to autohide and it's not visible. 1. Open dash pressing Super 2. Notice that the launcher background is not blurred. This happens only when dash is opened pressing Super button. If launcher happens to be visible prior to opening dash, for example opening dash from BFB, the launcher background is blurred properly. If you open dash by using lens shortcuts (Super+F for example), the launcher background is blurred correctly most of the time. Also, if the launcher background has no blur and you click something with your mouse inside dash, the launcher background gets blurred. I think this is somehow related to bug 1044926 because the launcher background is never blurred if the dash is shown before the launcher. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.4.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2 Uname: Linux 3.5.0-11-generic x86_64 ApportVersion: 2.5.1-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sun Sep 2 10:37:48 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices [AMD] nee ATI RV620 [Mobility Radeon HD 3400 Series] [1002:95c4] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:19e2] InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120807.1) MachineType: ASUSTeK Computer Inc. F5SR ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-11-generic root=UUID=40b6854e-96f6-477e-843b-810512211444 ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 210 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: F5SR dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr210:bd04/01/2009:svnASUSTeKComputerInc.:pnF5SR:pvr1.0:rvnPEGATRONCORPORATION:rnF5SR:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr: dmi.product.name: F5SR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.8.0-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.38-0ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20120821.c1114c61-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0~git20120821.c1114c61-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.12.99.905-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120713.6ef1ad6a-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.3-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.1-4~ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1044927/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1422359] Re: heimdal-kdc: kdc process leaks memory
I added the verification-done tag. I did not remove the verification- needed tag because I have no looked at Utopic. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1422359 Title: heimdal-kdc: kdc process leaks memory Status in heimdal package in Ubuntu: Fix Released Status in heimdal source package in Trusty: Fix Committed Status in heimdal source package in Utopic: Fix Committed Status in heimdal package in Debian: Fix Released Bug description: SRU information appears in comment #7: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1422359/comments/7 I have a KDC running Trusty Tahr. The machine has been up for 74 days and the kdc process has allocated almost all of the 8GB RAM available to the machine. When asking about this on heimdal-discuss, GALAMBOS Daniel pointed me to a relevant bug report (and fix) for Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746486 It seems likely this is the same problem I am experiencing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1422359/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1395098] Re: Please merge openldap 2.4.40-4 (main) from Debian unstable (main)
Unsubscribed sponsors for now. Needs rebasing again for Ubuntu changes, and there will probably be another Debian upload too. I'll try again for W. ** Changed in: openldap (Ubuntu) Assignee: (unassigned) => Ryan Tandy (rtandy) ** Changed in: openldap (Ubuntu) Status: Confirmed => In Progress -- 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/1395098 Title: Please merge openldap 2.4.40-4 (main) from Debian unstable (main) Status in openldap package in Ubuntu: In Progress Bug description: Debian unstable has openldap at version 2.4.40 but the version in the latest stable Ubuntu release (14.10) is 2.4.31 (released upstream in April 2012). A lot of bugs have been fixed since then [1]. Please put version 2.4.40 into the next release of Ubuntu (15.04). [1]: http://www.openldap.org/software/release/changes.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1395098/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432711] [NEW] signon-ui fails to build in vivd
Public bug reported: seen in a test rebuild in vivid: https://launchpad.net/ubuntu/+archive/test-rebuild-20150202/+build/6841984 https://launchpad.net/ubuntu/+archive/test-rebuild-20150202/+build/6841986 g++ -c -m64 -pipe -fno-exceptions -fno-rtti -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -D_REENTRANT -pthread -Wall -W -fPIE -DFORCE_FOREIGN_QWINDOW -DUSE_UBUNTU_WEB_VIEW -DDEBUG_ENABLED -DI18N_DOMAIN=\"signon-ui\" -DHTTP_WARNING_HELP=\"help:web-credentials/http-warning\" -DQT_NO_DEBUG -DQT_WEBKITWIDGETS_LIB -DQT_WEBKIT_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_DBUS_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -I. -I. -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtWebKitWidgets -isystem /usr/include/x86_64-linux-gnu/qt5/QtWebKit -isystem /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem /usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem /usr/include/signon-plugins -isystem /usr/include/signon-plugins/SignOn -isys tem /usr/include/gdk-pixbuf-2.0 -isystem /usr/include/libpng12 -isystem /usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -isystem /usr/include/accounts-qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtXml -isystem /usr/include/signon-qt5 -isystem /usr/include/signon-qt5/SignOn -o qquick-dialog.o qquick-dialog.cpp In file included from qquick-dialog.cpp:24:0: qquick-dialog.h:25:22: fatal error: QQuickView: No such file or directory #include ^ compilation terminated. Makefile.signon-ui:747: recipe for target 'qquick-dialog.o' failed make[3]: *** [qquick-dialog.o] Error 1 make[3]: Leaving directory '/build/buildd/signon-ui-0.17+14.10.20140916/src' Makefile:40: recipe for target 'sub-signon-ui-pro-make_first' failed make[2]: *** [sub-signon-ui-pro-make_first] Error 2 make[2]: Leaving directory '/build/buildd/signon-ui-0.17+14.10.20140916/src' Makefile:87: recipe for target 'sub-src-make_first-ordered' failed make[1]: *** [sub-src-make_first-ordered] Error 2 ** Affects: signon-ui (Ubuntu) Importance: High Status: Confirmed ** Affects: signon-ui (Ubuntu Vivid) Importance: High Status: Confirmed ** Tags: ftbfs ** Also affects: signon-ui (Ubuntu Vivid) Importance: High Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1432711 Title: signon-ui fails to build in vivd Status in signon-ui package in Ubuntu: Confirmed Status in signon-ui source package in Vivid: Confirmed Bug description: seen in a test rebuild in vivid: https://launchpad.net/ubuntu/+archive/test-rebuild-20150202/+build/6841984 https://launchpad.net/ubuntu/+archive/test-rebuild-20150202/+build/6841986 g++ -c -m64 -pipe -fno-exceptions -fno-rtti -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -D_REENTRANT -pthread -Wall -W -fPIE -DFORCE_FOREIGN_QWINDOW -DUSE_UBUNTU_WEB_VIEW -DDEBUG_ENABLED -DI18N_DOMAIN=\"signon-ui\" -DHTTP_WARNING_HELP=\"help:web-credentials/http-warning\" -DQT_NO_DEBUG -DQT_WEBKITWIDGETS_LIB -DQT_WEBKIT_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_DBUS_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -I. -I. -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtWebKitWidgets -isystem /usr/include/x86_64-linux-gnu/qt5/QtWebKit -isystem /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem /usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem /usr/include/signon-plugins -isystem /usr/include/signon-plugins/SignOn -is ystem /usr/include/gdk-pixbuf-2.0 -isystem /usr/include/libpng12 -isystem /usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -isystem /usr/include/accounts-qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtXml -isystem /usr/include/signon-qt5 -isystem /usr/include/signon-qt5/SignOn -o qquick-dialog.o qquick-dialog.cpp In file included from qquick-dialog.cpp:24:0: qquick-dialog.h:25:22: fatal error: QQuickView: No such file or directory #include ^ compilation terminated. Makefile.signon-ui:747: recipe for target 'qquick-dialog.o' failed make[3]: *** [qquick-dialog.o] Error 1 make[3]: Leaving directory '/build/buildd/signon-ui-0.17+14.10.20140916/src' Makefile:40: recipe for target 'sub-signon-ui-pro-make_first' failed make[2]: *** [sub-signon-ui-pro-make_first] Error 2 make[2]: Leaving directory '/build/buildd/signon-ui-0.17+14.10.20140916/src' Makefile:
[Touch-packages] [Bug 1381583] Re: [Gallery] imported pictures should show in Event for today
** Changed in: ubuntu-ux Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1381583 Title: [Gallery] imported pictures should show in Event for today Status in the base for Ubuntu mobile products: Fix Released Status in Gallery App: Fix Released Status in Ubuntu UX bugs: Fix Released Status in gallery-app package in Ubuntu: Fix Released Status in gallery-app package in Ubuntu RTM: Fix Released Bug description: When pictures are imported into the gallery, via content-hub, we should always display them in the Event for the current day. Right now, the picture is played in the Event that corresponds to the metadata creation date which is very confusing because after the picture is imported you can't find it easily. Arthur and I discussed modifiying one of the standard exif tags (like DateTime, but don't modify CreationDate) with the current date of import as the gallery already sorts by a series of tags. Another solution would be to add a custom tag like (importDate) and change the sort to use that if it exists before falling back to other tags. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1381583/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432123] Re: mountall service unavailable on systemd, preventing full zfs integration
The masking of mountall when booting with systemd is deliberate; mountall is a component of upstart's boot system and should not be used with systemd. So if there are any problems with mounting filesystems at boot when booting with systemd, that's a systemd bug. Reassigning. ** Package changed: mountall (Ubuntu) => systemd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1432123 Title: mountall service unavailable on systemd, preventing full zfs integration Status in systemd package in Ubuntu: New Bug description: I am test-driving Vivid and made the switch to systemd. I'd like to report that the mountall service is now unavailable. root# systemctl status mountall mountall.service Loaded: masked (/dev/null) Active: inactive (dead) root# ll /lib/systemd/system/mountall.service lrwxrwxrwx 1 root root 9 Mar 11 11:22 /lib/systemd/system/mountall.service -> /dev/null Per https://github.com/zfsonlinux/pkg-zfs/issues/132 I assume this is what is keeping all of my zfs filesystems from being automounted at boot. Things worked fine with upstart. zfs-pkg bug report: https://github.com/zfsonlinux/pkg-zfs/issues/145 systemd bug report: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432122 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432123/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376565] [NEW] Utopic system log wrong design
You have been subscribed to a public bug: On ubuntu 14.10 gnome-system-log has the new headerbars (look at the screenshot). It should look like all other ubuntu applications. ** Affects: ubuntu-themes (Ubuntu) Importance: Medium Status: In Progress ** Tags: utopic -- Utopic system log wrong design https://bugs.launchpad.net/bugs/1376565 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1044927] Re: Laucher background not blurred when Dash is opened
** Changed in: unity/7.2 Milestone: 7.2.5 => None -- 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/1044927 Title: Laucher background not blurred when Dash is opened Status in Unity: Fix Released Status in Unity 7.2 series: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: The launcher background is occasionally left without blur (see attached screenshot). This is a regression after updating unity from version 6.2.0-0ubuntu4 to 6.4.0-0ubuntu1. Steps to reproduce: Make sure that launcher is set to autohide and it's not visible. 1. Open dash pressing Super 2. Notice that the launcher background is not blurred. This happens only when dash is opened pressing Super button. If launcher happens to be visible prior to opening dash, for example opening dash from BFB, the launcher background is blurred properly. If you open dash by using lens shortcuts (Super+F for example), the launcher background is blurred correctly most of the time. Also, if the launcher background has no blur and you click something with your mouse inside dash, the launcher background gets blurred. I think this is somehow related to bug 1044926 because the launcher background is never blurred if the dash is shown before the launcher. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.4.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2 Uname: Linux 3.5.0-11-generic x86_64 ApportVersion: 2.5.1-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sun Sep 2 10:37:48 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices [AMD] nee ATI RV620 [Mobility Radeon HD 3400 Series] [1002:95c4] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:19e2] InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120807.1) MachineType: ASUSTeK Computer Inc. F5SR ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-11-generic root=UUID=40b6854e-96f6-477e-843b-810512211444 ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 210 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: F5SR dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr210:bd04/01/2009:svnASUSTeKComputerInc.:pnF5SR:pvr1.0:rvnPEGATRONCORPORATION:rnF5SR:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr: dmi.product.name: F5SR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.8.0-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.38-0ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20120821.c1114c61-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0~git20120821.c1114c61-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.12.99.905-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120713.6ef1ad6a-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.3-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.1-4~ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1044927/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1422345] Re: stop being nice does not work
Works fine in an unprivileged container. Thanks! ** Tags removed: verification-needed-trusty verification-needed-utopic ** Tags added: verification-done-trusty verification-done-utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1422345 Title: stop being nice does not work Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Trusty: Fix Committed Status in unattended-upgrades source package in Utopic: Fix Committed Status in unattended-upgrades package in Debian: New Bug description: Test Case - 1) Install apache2 from the -release pocket 2) Run unattended-upgrades 3) Observe apache2 running with a niceness of 19 4) Downgrade apache2 to the version from the -release pocket 5) Install the version of unattended-upgrades from -proposed 6) Run unattended-upgrades 7) Observe apache2 running with a niceness of 0 i.e. no niceness Since version 0.81, unattended-upgrades does the upgrade calculation with os.nice(19). To finish the nice block in /usr/bin/unattended-upgrade, the following call is used: os.nice(0) Since the argument is interpreted as incremental, this should be: os.nice(-19) Without this fix, this problem is back: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701850 "unattended-upgrades: nice 19/ionice idle inherited by restarted processes" Found in the trusty version (0.82.1ubuntu2), but probably in any version (including Debian) since 0.81. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1422345/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376565] Re: Utopic system log wrong design
This is a bug in the theme, not in gnome-system-log. ** Branch linked: lp:~larsu/ubuntu-themes/titlebars ** Package changed: gnome-system-log (Ubuntu) => ubuntu-themes (Ubuntu) ** Changed in: ubuntu-themes (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1376565 Title: Utopic system log wrong design Status in ubuntu-themes package in Ubuntu: In Progress Bug description: On ubuntu 14.10 gnome-system-log has the new headerbars (look at the screenshot). It should look like all other ubuntu applications. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1376565/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390393] Re: It's too easy to trigger a volume notification when taking a screenshot
Noemi, don't press the power button, it's just the two volume buttons that you need to press. -- 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/1390393 Title: It's too easy to trigger a volume notification when taking a screenshot Status in the base for Ubuntu mobile products: Fix Released Status in unity8 package in Ubuntu: Fix Released Status in unity8 package in Ubuntu RTM: Fix Released Bug description: On Mako, I'm unable to take a screenshot (Vol up + Vol down) without changing the volume, which causes a notification to appear on the screenshot, and changes the volume when taking a screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1390393/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 762193] Re: No launcher icon or Alt+Tab entry for xchat/xchat-gnome windows
As has been mentioned before, this seems to be an issue with apps using "Minimize to Tray" when there is no "tray" in Unity. Marking this as Fix Released in Unity as the core issue of showing the running app in the Launcher is fixed. ** Changed in: unity Status: Triaged => Fix Released ** Changed in: unity (Ubuntu) Status: Triaged => Fix Released ** Changed in: unity Milestone: 7.3.2 => None ** Changed in: unity/5.0 Status: Triaged => Fix Released ** Changed in: unity/5.0 Milestone: 5.24.0 => None -- 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/762193 Title: No launcher icon or Alt+Tab entry for xchat/xchat-gnome windows Status in Unity: Fix Released Status in Unity 5.0 series: Fix Released Status in Unity 6.0 series: Won't Fix Status in unity package in Ubuntu: Fix Released Status in xchat package in Ubuntu: Triaged Bug description: Binary package hint: unity Running Xchat (see scrennshot) Unity fails to show that the application is running. If I minimize Xchat, Unity still won't be showing that the app is running. If I click on the Xchat icon again it will start a new instance while the old one is still running. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: unity 3.8.8-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 NonfreeKernelModules: wl Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unityshell] Date: Fri Apr 15 17:05:47 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110407) ProcEnviron: LANGUAGE=en_CA:en LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/762193/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432711] Re: signon-ui fails to build in vivd
** Changed in: signon-ui (Ubuntu Vivid) Assignee: (unassigned) => Alberto Mardegan (mardy) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1432711 Title: signon-ui fails to build in vivd Status in signon-ui package in Ubuntu: Confirmed Status in signon-ui source package in Vivid: Confirmed Bug description: seen in a test rebuild in vivid: https://launchpad.net/ubuntu/+archive/test-rebuild-20150202/+build/6841984 https://launchpad.net/ubuntu/+archive/test-rebuild-20150202/+build/6841986 g++ -c -m64 -pipe -fno-exceptions -fno-rtti -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -D_REENTRANT -pthread -Wall -W -fPIE -DFORCE_FOREIGN_QWINDOW -DUSE_UBUNTU_WEB_VIEW -DDEBUG_ENABLED -DI18N_DOMAIN=\"signon-ui\" -DHTTP_WARNING_HELP=\"help:web-credentials/http-warning\" -DQT_NO_DEBUG -DQT_WEBKITWIDGETS_LIB -DQT_WEBKIT_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_DBUS_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -I. -I. -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtWebKitWidgets -isystem /usr/include/x86_64-linux-gnu/qt5/QtWebKit -isystem /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem /usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem /usr/include/signon-plugins -isystem /usr/include/signon-plugins/SignOn -is ystem /usr/include/gdk-pixbuf-2.0 -isystem /usr/include/libpng12 -isystem /usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -isystem /usr/include/accounts-qt5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtXml -isystem /usr/include/signon-qt5 -isystem /usr/include/signon-qt5/SignOn -o qquick-dialog.o qquick-dialog.cpp In file included from qquick-dialog.cpp:24:0: qquick-dialog.h:25:22: fatal error: QQuickView: No such file or directory #include ^ compilation terminated. Makefile.signon-ui:747: recipe for target 'qquick-dialog.o' failed make[3]: *** [qquick-dialog.o] Error 1 make[3]: Leaving directory '/build/buildd/signon-ui-0.17+14.10.20140916/src' Makefile:40: recipe for target 'sub-signon-ui-pro-make_first' failed make[2]: *** [sub-signon-ui-pro-make_first] Error 2 make[2]: Leaving directory '/build/buildd/signon-ui-0.17+14.10.20140916/src' Makefile:87: recipe for target 'sub-src-make_first-ordered' failed make[1]: *** [sub-src-make_first-ordered] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1432711/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1422345] Re: stop being nice does not work
I can confirm, worked fine in my LXC containers. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1422345 Title: stop being nice does not work Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Trusty: Fix Committed Status in unattended-upgrades source package in Utopic: Fix Committed Status in unattended-upgrades package in Debian: New Bug description: Test Case - 1) Install apache2 from the -release pocket 2) Run unattended-upgrades 3) Observe apache2 running with a niceness of 19 4) Downgrade apache2 to the version from the -release pocket 5) Install the version of unattended-upgrades from -proposed 6) Run unattended-upgrades 7) Observe apache2 running with a niceness of 0 i.e. no niceness Since version 0.81, unattended-upgrades does the upgrade calculation with os.nice(19). To finish the nice block in /usr/bin/unattended-upgrade, the following call is used: os.nice(0) Since the argument is interpreted as incremental, this should be: os.nice(-19) Without this fix, this problem is back: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701850 "unattended-upgrades: nice 19/ionice idle inherited by restarted processes" Found in the trusty version (0.82.1ubuntu2), but probably in any version (including Debian) since 0.81. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1422345/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390393] Re: It's too easy to trigger a volume notification when taking a screenshot
Ok 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/1390393 Title: It's too easy to trigger a volume notification when taking a screenshot Status in the base for Ubuntu mobile products: Fix Released Status in unity8 package in Ubuntu: Fix Released Status in unity8 package in Ubuntu RTM: Fix Released Bug description: On Mako, I'm unable to take a screenshot (Vol up + Vol down) without changing the volume, which causes a notification to appear on the screenshot, and changes the volume when taking a screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1390393/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1423185] Re: Calendar app crash
** Changed in: qtorganizer5-eds (Ubuntu) Assignee: (unassigned) => Renato Araujo Oliveira Filho (renatofilho) ** No longer affects: qtorganizer5-eds -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtorganizer5-eds in Ubuntu. https://bugs.launchpad.net/bugs/1423185 Title: Calendar app crash Status in Calendar application for Ubuntu devices: In Progress Status in qtorganizer5-eds package in Ubuntu: Fix Released Bug description: Tapping on a day in Year view, crashed calendar app. See attached file. TEST CASE: 1. Switch to 'Year' view 2. Tap on any day 3. Repeat steps 1 and 2 up to 10 times ACTUAL RESULT The app crashes after a few attempts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1423185/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1431798] Re: unity8-dash crashed with signal 7 in QMutex::lock() when switching scopes
** Changed in: unity8 (Ubuntu) Status: Incomplete => Triaged ** Changed in: unity8 (Ubuntu) Status: Triaged => In Progress ** Changed in: unity8 (Ubuntu) Assignee: (unassigned) => Albert Astals Cid (aacid) -- 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/1431798 Title: unity8-dash crashed with signal 7 in QMutex::lock() when switching scopes Status in unity8 package in Ubuntu: In Progress Bug description: Original is bug #1431440: I was simply paging through the scopes ad got this crash. I swiped in in the open dialer app and then I see the scopes restarting Reproduced three times in a row,and after a reboot. mako running 213 rtm ProblemType: Crash DistroRelease: Ubuntu RTM 14.09 Package: unity8 8.02+15.04.20150226~rtm-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf CurrentDesktop: Unity Date: Thu Mar 12 12:05:54 2015 ExecutablePath: /usr/bin/unity8-dash ExecutableTimestamp: 1424989859 InstallationDate: Installed on 2015-03-12 (1 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20150312-002053) LocalLibraries: /android/system/lib/libadreno_utils.so /android/system/lib/egl/eglsubAndroid.so /android/system/lib/libcorkscrew.so /android/system/lib/libGLESv1_CM.so /android/system/lib/libGLES_trace.so /android/system/lib/hw/gralloc.msm8960.so /android/system/lib/libmemalloc.so /android/system/lib/libui.so /android/system/lib/libGLESv2.so /android/system/lib/libhardware.so /android/system/lib/libc.so /android/system/lib/libstdc++.so /android/system/lib/libstlport.so /android/system/lib/libdsyscalls.so /android/system/lib/libm.so /android/system/lib/libsync.so /android/system/lib/libsc-a3xx.so /android/system/lib/libz.so /android/system/lib/libcutils.so /android/system/lib/egl/libGLESv1_CM_adreno.so /android/system/lib/libqdutils.so /android/system/lib/libgccdemangle.so /android/system/lib/libgsl.so /android/system/lib/libutils.so /android/system/lib/egl/libEGL_adreno.so /android/system/lib/egl/libGLESv2_adreno.so /android/system/lib/liblog.so /android/system/lib/libEGL.so ProcCmdline: unity8-dash --desktop_file_hint=/usr/share/applications/unity8-dash.desktop ProcCwd: /home/phablet Signal: 7 SourcePackage: unity8 StacktraceTop: QMutex::lock() () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5 QCoreApplication::postEvent(QObject*, QEvent*, int) () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5 ?? () from /usr/lib/arm-linux-gnueabihf/libQt5Quick.so.5 Title: unity8-dash crashed with signal 7 in QMutex::lock() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip plugdev sudo tty video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1431798/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432725] [NEW] Crash disabling/enabling settings
Public bug reported: Test case. - Go to music scope. - Go to settings. - Disable 7digital and Grooveshark. - Go back to scope. - Check results are displayed correctly. - Go back to settings. - Re-enable 7digital and Grooveshark. - Go back to scope. Expected result. - After refresh, all the selected content is displayed. Actual result. - No content at all is displayed. Crash available in /var/crash. Test also with Video scope. After disabling/enabling YouTube and Vimeo videos, got a crash. current build number: 147 device name: krillin channel: ubuntu-touch/devel-proposed ** Affects: unity-scopes-shell (Ubuntu) Importance: Undecided Status: New ** Tags: qa-silo ** Attachment added: "_usr_lib_arm-linux-gnueabihf_unity-scopes_scoperunner.32011.crash" https://bugs.launchpad.net/bugs/1432725/+attachment/4347204/+files/_usr_lib_arm-linux-gnueabihf_unity-scopes_scoperunner.32011.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1432725 Title: Crash disabling/enabling settings Status in unity-scopes-shell package in Ubuntu: New Bug description: Test case. - Go to music scope. - Go to settings. - Disable 7digital and Grooveshark. - Go back to scope. - Check results are displayed correctly. - Go back to settings. - Re-enable 7digital and Grooveshark. - Go back to scope. Expected result. - After refresh, all the selected content is displayed. Actual result. - No content at all is displayed. Crash available in /var/crash. Test also with Video scope. After disabling/enabling YouTube and Vimeo videos, got a crash. current build number: 147 device name: krillin channel: ubuntu-touch/devel-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1432725/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1427991] Re: Stop build-depending on private Qt headers
** Branch linked: lp:ubuntu/vivid-proposed/ubuntu-push-qml -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1427991 Title: Stop build-depending on private Qt headers Status in ubuntu-keyboard package in Ubuntu: New Status in ubuntu-push-qml package in Ubuntu: New Status in ubuntu-settings-components package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: In Progress Bug description: Your package is build-depending on either qtbase5-private-dev or qtdeclarative5-private-dev, but it does not seem to use any symbols marked as private. Even if it would use private headers, please consider stopping using those since there may be incompatible changes in future Qt versions. Depend only on the qtbase5-dev and/or qtdeclarative5-dev. The reason for this bug is to both limit private headers usage and to keep better track of the users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1427991/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1425155] Re: totem 3.14's OSD looks bad in Ambiance
** Description changed: In our theme, totem's OSD (player controls) doesn't look very nice. It's not really styled. - Just play a video and look at the in-window controls to see this. + Fixing this involves only changes to css files, and in there only adding + rules for the .osd style class (and sub widgets). + + Rationale for including this after UI freeze: it's really quite ugly and + it's hard to discern the overlay widgets from the video as they are + missing a background. Please see the attached screenshots. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: totem 3.14.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 24 16:01:38 2015 InstallationDate: Installed on 2012-10-07 (869 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007) SourcePackage: totem UpgradeStatus: Upgraded to vivid on 2013-05-07 (658 days ago) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1425155 Title: totem 3.14's OSD looks bad in Ambiance Status in ubuntu-themes package in Ubuntu: New Bug description: In our theme, totem's OSD (player controls) doesn't look very nice. It's not really styled. Fixing this involves only changes to css files, and in there only adding rules for the .osd style class (and sub widgets). Rationale for including this after UI freeze: it's really quite ugly and it's hard to discern the overlay widgets from the video as they are missing a background. Please see the attached screenshots. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: totem 3.14.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 24 16:01:38 2015 InstallationDate: Installed on 2012-10-07 (869 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007) SourcePackage: totem UpgradeStatus: Upgraded to vivid on 2013-05-07 (658 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1425155/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376565] Re: Utopic system log wrong design
** Description changed: On ubuntu 14.10 gnome-system-log has the new headerbars (look at the screenshot). It should look like all other ubuntu applications. + + Fixing this entails changing the style of header bars in css files and + adding new icons which are used for the window buttons (close, minimize, + maximize, restore). "window-close-symbolic" is also used on tab widgets + in some applications, such as gnome-terminal and gedit. Those look + slightly different with the change. + + Rationale for including this after UI freeze: more than anticipated + GNOME applications in the archive got updated to use a header bar + instead of a traditional title bar. We've patched default applications, + but there's a lot of apps left (for example, gnome-system-logs, devhelp, + gnome-font-viewer). Making them look a bit more consistent with other + apps is desirable, as they look very much out of place now. ** Summary changed: - Utopic system log wrong design + GNOME apps with headerbars look out of place in Unity ** Changed in: ubuntu-themes (Ubuntu) Status: In Progress => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1376565 Title: GNOME apps with headerbars look out of place in Unity Status in ubuntu-themes package in Ubuntu: New Bug description: On ubuntu 14.10 gnome-system-log has the new headerbars (look at the screenshot). It should look like all other ubuntu applications. Fixing this entails changing the style of header bars in css files and adding new icons which are used for the window buttons (close, minimize, maximize, restore). "window-close-symbolic" is also used on tab widgets in some applications, such as gnome-terminal and gedit. Those look slightly different with the change. Rationale for including this after UI freeze: more than anticipated GNOME applications in the archive got updated to use a header bar instead of a traditional title bar. We've patched default applications, but there's a lot of apps left (for example, gnome- system-logs, devhelp, gnome-font-viewer). Making them look a bit more consistent with other apps is desirable, as they look very much out of place now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1376565/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1356222] Re: [MIR] fcitx and related packages
Override component to main extra-cmake-modules 1.7.0-0ubuntu2 in vivid: universe/libs -> main extra-cmake-modules 1.7.0-0ubuntu2 in vivid amd64: universe/libs/optional/100% -> main extra-cmake-modules 1.7.0-0ubuntu2 in vivid arm64: universe/libs/optional/100% -> main extra-cmake-modules 1.7.0-0ubuntu2 in vivid armhf: universe/libs/optional/100% -> main extra-cmake-modules 1.7.0-0ubuntu2 in vivid i386: universe/libs/optional/100% -> main extra-cmake-modules 1.7.0-0ubuntu2 in vivid powerpc: universe/libs/optional/100% -> main extra-cmake-modules 1.7.0-0ubuntu2 in vivid ppc64el: universe/libs/optional/100% -> main 7 publications overridden. ** Changed in: extra-cmake-modules (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tinyxml in Ubuntu. https://bugs.launchpad.net/bugs/1356222 Title: [MIR] fcitx and related packages Status in extra-cmake-modules package in Ubuntu: Fix Released Status in fcitx package in Ubuntu: Fix Released Status in fcitx-anthy package in Ubuntu: Fix Committed Status in fcitx-chewing package in Ubuntu: Fix Committed Status in fcitx-cloudpinyin package in Ubuntu: Fix Released Status in fcitx-configtool package in Ubuntu: Fix Released Status in fcitx-googlepinyin package in Ubuntu: Fix Committed Status in fcitx-hangul package in Ubuntu: Fix Committed Status in fcitx-m17n package in Ubuntu: Fix Committed Status in fcitx-qimpanel package in Ubuntu: Fix Released Status in fcitx-qt5 package in Ubuntu: Fix Released Status in fcitx-sunpinyin package in Ubuntu: Fix Committed Status in fcitx-table-extra package in Ubuntu: Fix Committed Status in fcitx-table-other package in Ubuntu: Fix Committed Status in libgooglepinyin package in Ubuntu: Fix Committed Status in presage package in Ubuntu: Fix Released Status in tinyxml package in Ubuntu: Fix Released Bug description: [Availability] Currently in universe [Rationale] Fcitx is a replacement candidate for IBus [Security: ] CVE entries: none Security history: none Any binaries running as root or suid/sgid ? Any daemons ? -- all running as per user session, and /usr/bin/fcitx and /usr/bin/fcitx-qimpanel will run as daemon, /usr/bin/fcitx-dbus-watcher will be pulled up when fcitx is running. Network activity: does it open any port ? Does it handle incoming network data ? -- fcitx-cloudpinyin deals with network data by using libcurl and interact with remote API from several user-choosable providers. Does it directly (not through a library) process binary (video, audio, etc) or structured (PDF, etc) data ? -- no, it doesn't Any source code review performed ? (The approver will do a quick and shallow check.) -- no. [Quality Assurance] Package works out of the box with no prompting. There is no reproducible major bugs in Ubuntu and Debian. Upstream is active. Package is team maintained at Debian, and is the same people working on Debian and Ubuntu. Upstream bug tracker: https://github.com/fcitx/fcitx Hardware: Does this package deal with hardware and if so how exotic is it ? -- no Is there a test suite in the upstream source or packaging ? Is it enabled to run in the build ? -- yes, some fundamental tests [UI standards] User-visible strings are internationalized using standard gettext system ? -- yes Package with translatable strings builds a PO template during package build ? -- yes End-user applications ship a desktop file? -- fcitx and fcitx-ui-qimpanel do. [Standards Compliance] FHS and Debian Policy compliant. Packaging system (debhelper/cdbs/dbs) ? Patch system ? Any packaging oddities ? -- package is using debhelper, [Maintenance] Desktop Team will take care of them [Dependencies] librime and brise are for fcitx-rime. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/extra-cmake-modules/+bug/1356222/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1264711] Re: SIGSEV: [matroska, webm] Unknown entry
Is this still an issue? If it is, please follow https://libav.org/bugreports.html and report the issue upstream. ** Changed in: libav (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1264711 Title: SIGSEV: [matroska,webm] Unknown entry Status in libav package in Ubuntu: Incomplete Bug description: Attached is a gdb backtrace. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libav-tools 6:9.10-1ubuntu7 ProcVersionSignature: Uname: Linux 3.12.4-custom x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.12.7-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Dec 28 10:36:30 2013 InstallationDate: Installed on 2013-11-25 (32 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: libav UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1264711/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432725] Re: Crash disabling/enabling settings
** Changed in: unity-scopes-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1432725 Title: Crash disabling/enabling settings Status in unity-scopes-shell package in Ubuntu: Confirmed Bug description: Test case. - Go to music scope. - Go to settings. - Disable 7digital and Grooveshark. - Go back to scope. - Check results are displayed correctly. - Go back to settings. - Re-enable 7digital and Grooveshark. - Go back to scope. Expected result. - After refresh, all the selected content is displayed. Actual result. - No content at all is displayed. Crash available in /var/crash. Test also with Video scope. After disabling/enabling YouTube and Vimeo videos, got a crash. current build number: 147 device name: krillin channel: ubuntu-touch/devel-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1432725/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1431798] Re: unity8-dash crashed with signal 7 in QMutex::lock() when switching scopes
I can't prove it since i can not reproduce it but after staring at the backtrace a lot and reading the code even more lots i came up with https://codereview.qt-project.org/#/c/108700/ That seems like it should be a proper patch for fixing this crash. Let's see what upstream thinks -- 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/1431798 Title: unity8-dash crashed with signal 7 in QMutex::lock() when switching scopes Status in unity8 package in Ubuntu: In Progress Bug description: Original is bug #1431440: I was simply paging through the scopes ad got this crash. I swiped in in the open dialer app and then I see the scopes restarting Reproduced three times in a row,and after a reboot. mako running 213 rtm ProblemType: Crash DistroRelease: Ubuntu RTM 14.09 Package: unity8 8.02+15.04.20150226~rtm-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf CurrentDesktop: Unity Date: Thu Mar 12 12:05:54 2015 ExecutablePath: /usr/bin/unity8-dash ExecutableTimestamp: 1424989859 InstallationDate: Installed on 2015-03-12 (1 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20150312-002053) LocalLibraries: /android/system/lib/libadreno_utils.so /android/system/lib/egl/eglsubAndroid.so /android/system/lib/libcorkscrew.so /android/system/lib/libGLESv1_CM.so /android/system/lib/libGLES_trace.so /android/system/lib/hw/gralloc.msm8960.so /android/system/lib/libmemalloc.so /android/system/lib/libui.so /android/system/lib/libGLESv2.so /android/system/lib/libhardware.so /android/system/lib/libc.so /android/system/lib/libstdc++.so /android/system/lib/libstlport.so /android/system/lib/libdsyscalls.so /android/system/lib/libm.so /android/system/lib/libsync.so /android/system/lib/libsc-a3xx.so /android/system/lib/libz.so /android/system/lib/libcutils.so /android/system/lib/egl/libGLESv1_CM_adreno.so /android/system/lib/libqdutils.so /android/system/lib/libgccdemangle.so /android/system/lib/libgsl.so /android/system/lib/libutils.so /android/system/lib/egl/libEGL_adreno.so /android/system/lib/egl/libGLESv2_adreno.so /android/system/lib/liblog.so /android/system/lib/libEGL.so ProcCmdline: unity8-dash --desktop_file_hint=/usr/share/applications/unity8-dash.desktop ProcCwd: /home/phablet Signal: 7 SourcePackage: unity8 StacktraceTop: QMutex::lock() () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5 QCoreApplication::postEvent(QObject*, QEvent*, int) () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5 ?? () from /usr/lib/arm-linux-gnueabihf/libQt5Quick.so.5 Title: unity8-dash crashed with signal 7 in QMutex::lock() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip plugdev sudo tty video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1431798/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1356222] Re: [MIR] fcitx and related packages
Override component to main fcitx-cloudpinyin 0.3.4-2 in vivid: universe/utils -> main fcitx-module-cloudpinyin 0.3.4-2 in vivid amd64: universe/utils/optional/100% -> main fcitx-module-cloudpinyin 0.3.4-2 in vivid arm64: universe/utils/optional/100% -> main fcitx-module-cloudpinyin 0.3.4-2 in vivid armhf: universe/utils/optional/100% -> main fcitx-module-cloudpinyin 0.3.4-2 in vivid i386: universe/utils/optional/100% -> main fcitx-module-cloudpinyin 0.3.4-2 in vivid powerpc: universe/utils/optional/100% -> main fcitx-module-cloudpinyin 0.3.4-2 in vivid ppc64el: universe/utils/optional/100% -> main fcitx-qimpanel 2.0.0-0ubuntu1 in vivid: universe/utils -> main fcitx-ui-qimpanel 2.0.0-0ubuntu1 in vivid amd64: universe/utils/optional/100% -> main fcitx-ui-qimpanel 2.0.0-0ubuntu1 in vivid arm64: universe/utils/optional/100% -> main fcitx-ui-qimpanel 2.0.0-0ubuntu1 in vivid armhf: universe/utils/optional/100% -> main fcitx-ui-qimpanel 2.0.0-0ubuntu1 in vivid i386: universe/utils/optional/100% -> main fcitx-ui-qimpanel 2.0.0-0ubuntu1 in vivid powerpc: universe/utils/optional/100% -> main fcitx-ui-qimpanel 2.0.0-0ubuntu1 in vivid ppc64el: universe/utils/optional/100% -> main ** Changed in: fcitx-cloudpinyin (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: fcitx-qimpanel (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tinyxml in Ubuntu. https://bugs.launchpad.net/bugs/1356222 Title: [MIR] fcitx and related packages Status in extra-cmake-modules package in Ubuntu: Fix Released Status in fcitx package in Ubuntu: Fix Released Status in fcitx-anthy package in Ubuntu: Fix Committed Status in fcitx-chewing package in Ubuntu: Fix Committed Status in fcitx-cloudpinyin package in Ubuntu: Fix Released Status in fcitx-configtool package in Ubuntu: Fix Released Status in fcitx-googlepinyin package in Ubuntu: Fix Committed Status in fcitx-hangul package in Ubuntu: Fix Committed Status in fcitx-m17n package in Ubuntu: Fix Committed Status in fcitx-qimpanel package in Ubuntu: Fix Released Status in fcitx-qt5 package in Ubuntu: Fix Released Status in fcitx-sunpinyin package in Ubuntu: Fix Committed Status in fcitx-table-extra package in Ubuntu: Fix Committed Status in fcitx-table-other package in Ubuntu: Fix Committed Status in libgooglepinyin package in Ubuntu: Fix Committed Status in presage package in Ubuntu: Fix Released Status in tinyxml package in Ubuntu: Fix Released Bug description: [Availability] Currently in universe [Rationale] Fcitx is a replacement candidate for IBus [Security: ] CVE entries: none Security history: none Any binaries running as root or suid/sgid ? Any daemons ? -- all running as per user session, and /usr/bin/fcitx and /usr/bin/fcitx-qimpanel will run as daemon, /usr/bin/fcitx-dbus-watcher will be pulled up when fcitx is running. Network activity: does it open any port ? Does it handle incoming network data ? -- fcitx-cloudpinyin deals with network data by using libcurl and interact with remote API from several user-choosable providers. Does it directly (not through a library) process binary (video, audio, etc) or structured (PDF, etc) data ? -- no, it doesn't Any source code review performed ? (The approver will do a quick and shallow check.) -- no. [Quality Assurance] Package works out of the box with no prompting. There is no reproducible major bugs in Ubuntu and Debian. Upstream is active. Package is team maintained at Debian, and is the same people working on Debian and Ubuntu. Upstream bug tracker: https://github.com/fcitx/fcitx Hardware: Does this package deal with hardware and if so how exotic is it ? -- no Is there a test suite in the upstream source or packaging ? Is it enabled to run in the build ? -- yes, some fundamental tests [UI standards] User-visible strings are internationalized using standard gettext system ? -- yes Package with translatable strings builds a PO template during package build ? -- yes End-user applications ship a desktop file? -- fcitx and fcitx-ui-qimpanel do. [Standards Compliance] FHS and Debian Policy compliant. Packaging system (debhelper/cdbs/dbs) ? Patch system ? Any packaging oddities ? -- package is using debhelper, [Maintenance] Desktop Team will take care of them [Dependencies] librime and brise are for fcitx-rime. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/extra-cmake-modules/+bug/1356222/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378350] Re: [Browser] Need to allow multiple apps to handle the same url patterns
I removed myself from the UX task, as I am not responsible for the content hub ** Changed in: ubuntu-ux Assignee: Giorgio Venturi (giorgio-venturi) => (unassigned) ** Changed in: ubuntu-ux Assignee: (unassigned) => Magdalena Mirowicz (magdalena-mirowicz) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to content-hub in Ubuntu. https://bugs.launchpad.net/bugs/1378350 Title: [Browser] Need to allow multiple apps to handle the same url patterns Status in Ubuntu UX bugs: Confirmed Status in content-hub package in Ubuntu: New Status in url-dispatcher package in Ubuntu: Triaged Bug description: Steps: * install gmail and dekko apps Expected: * when using a mailto: URL (see bug #1351222) URL, the user should be asked which app to open (and cache the response optionally?) Current: * not sure what would happen ;) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1378350/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1395724] Re: Cannot type into account login input boxes
I think it will stay as a known issue in the current RTM release, until we switch phones OTA with vivid in the next few months. The issue is annoying, but users can easily get back to a known working state, by restarting a signup session. ** Changed in: ubuntu-system-settings-online-accounts (Ubuntu RTM) Assignee: David Barth (dbarth) => (unassigned) ** Changed in: unity8 (Ubuntu) Assignee: Josh Arenson (josharenson) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1395724 Title: Cannot type into account login input boxes Status in the base for Ubuntu mobile products: Fix Released Status in ubuntu-system-settings-online-accounts package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Triaged Status in ubuntu-system-settings-online-accounts package in Ubuntu RTM: Confirmed Bug description: 1. Open system settings and go to accounts. 2. tap on 'Google' to add a google account 3. When the login page opens drag down the indicator bar from the top 4. Now try to type into the username/password boxes. What happens: OSK does not appear to type in there. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: ubuntu-system-settings-online-accounts 0.5+14.10.20141029~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Mon Nov 24 13:29:58 2014 InstallationDate: Installed on 2014-11-21 (2 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141121-220606) SourcePackage: ubuntu-system-settings-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1395724/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1427991] Re: Stop build-depending on private Qt headers
This bug was fixed in the package ubuntu-push-qml - 0.1+15.04.20150312-0ubuntu1 --- ubuntu-push-qml (0.1+15.04.20150312-0ubuntu1) vivid; urgency=medium [ Roberto Alsina ] * Don't leak watchers. (LP: #1425132) [ Timo Jyrinki ] * Don't build-depend on Qt private header packages. (LP: #1427991) (LP: #1427991) -- CI Train BotThu, 12 Mar 2015 12:42:28 + ** Changed in: ubuntu-push-qml (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1427991 Title: Stop build-depending on private Qt headers Status in ubuntu-keyboard package in Ubuntu: New Status in ubuntu-push-qml package in Ubuntu: Fix Released Status in ubuntu-settings-components package in Ubuntu: New Status in ubuntu-system-settings package in Ubuntu: In Progress Bug description: Your package is build-depending on either qtbase5-private-dev or qtdeclarative5-private-dev, but it does not seem to use any symbols marked as private. Even if it would use private headers, please consider stopping using those since there may be incompatible changes in future Qt versions. Depend only on the qtbase5-dev and/or qtdeclarative5-dev. The reason for this bug is to both limit private headers usage and to keep better track of the users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1427991/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1394731] Re: [MIR] grilo-plugins
had to add the -dbg package to the extra-excludes in the seeds, depends on the extra package ** Changed in: grilo-plugins (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grilo-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1394731 Title: [MIR] grilo-plugins Status in grilo-plugins package in Ubuntu: Fix Released Bug description: Availability: In universe, builds on all archs Rational: grilo-plugins is now a dependency of totem and is hard to patch out. See lp:1393067 Security: No known CVEs Quality Assurance: No bugs in debian or ubuntu, most upstream bugs are feature requests. Active debian maintainer. Has watch file. Tests are run during build. UI standards: The package is translated upstream. Dependencies: All deps in main Standards compliance: No issues Maintenance: Actively maintained in debian. ubuntu-gnome team will subscribe in ubuntu. Background info: Grilo is a framework focused on making media discovery and browsing easy for application developers. This package contains it's plugins, including the tracker one, which is now needed by totem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grilo-plugins/+bug/1394731/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
