[Touch-packages] [Bug 1135038] Re: friends-dispatcher crashed with friends.errors.AuthorizationError in _login_cb(): GDBus.Error:com.google.code.AccountsSSO.SingleSignOn.Error.UserInteraction: userAct
I have the same problem with Evolution too: GDBus.Error:com.google.code.AccountsSSO.SingleSignOn.Error.UserInteraction: userActionFinished error: 10 What can we do ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to friends in Ubuntu. https://bugs.launchpad.net/bugs/1135038 Title: friends-dispatcher crashed with friends.errors.AuthorizationError in _login_cb(): GDBus.Error:com.google.code.AccountsSSO.SingleSignOn.Error.UserInteraction: userActionFinished error: 10 (account: 1) Status in Online Accounts: Sign-on UI: Fix Released Status in “friends” package in Ubuntu: Fix Released Bug description: This crash came up right after booting up my laptop. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: friends-dispatcher 0.1.1bzr13.02.25-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-8.17-generic 3.8.0 Uname: Linux 3.8.0-8-generic i686 ApportVersion: 2.8-0ubuntu4 Architecture: i386 Date: Wed Feb 27 20:09:36 2013 ExecutablePath: /usr/bin/friends-dispatcher InstallationDate: Installed on 2012-10-25 (125 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) InterpreterPath: /usr/bin/python3.3 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/friends-dispatcher -o ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 PythonArgs: ['/usr/bin/friends-dispatcher', '-o'] SourcePackage: friends Title: friends-dispatcher crashed with friends.errors.AuthorizationError in _login_cb(): GDBus.Error:com.google.code.AccountsSSO.SingleSignOn.Error.UserInteraction: userActionFinished error: 10 (account: 1) Traceback: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/friends/utils/authentication.py", line 69, in _login_cb raise AuthorizationError(self.account.id, error.message) friends.errors.AuthorizationError: GDBus.Error:com.google.code.AccountsSSO.SingleSignOn.Error.UserInteraction: userActionFinished error: 10 (account: 1) UpgradeStatus: Upgraded to raring on 2013-02-22 (5 days ago) UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/signon-ui/+bug/1135038/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371439] [NEW] missing xdg-user-dirs:i386 package
Public bug reported: Utopic 64 bits installation, running gnome-shell (genuine fresh installation) Today libglib2.0-0 upgrade (2.41.5-1) wants to: -remove: ubuntu-desktop, xdg-user-dirs, xdg-user-dirs-gtk -install: xdg-user-dirs:i386 (but that one does not exist inside the archive) Please fix the dependencies. ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 bot-stop-nagging utopic ** Tags added: amd64 bot-stop-nagging utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1371439 Title: missing xdg-user-dirs:i386 package Status in “glib2.0” package in Ubuntu: New Bug description: Utopic 64 bits installation, running gnome-shell (genuine fresh installation) Today libglib2.0-0 upgrade (2.41.5-1) wants to: -remove: ubuntu-desktop, xdg-user-dirs, xdg-user-dirs-gtk -install: xdg-user-dirs:i386 (but that one does not exist inside the archive) Please fix the dependencies. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1371439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1349309] Re: Require special menu type for settings menus
@charles . at the moment I'm searching the action names for the word "settings" an styling accordingly, so it's working for now. No immediate rush, but would like to remove the hack from the code. -- 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/1349309 Title: Require special menu type for settings menus Status in Bluetooth Menu: Triaged Status in The Date and Time Indicator: Triaged Status in Network Menu: Triaged Status in The Power Indicator: Triaged Status in Sound Menu: New Status in “unity8” package in Ubuntu: Confirmed Bug description: The settings menus should have a custom type so that we can specialize them in the UI. com.canonical.indicator.link Attached image to show what design want. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-bluetooth/+bug/1349309/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1353951] Re: gnome online accounts require autentication on startup
@Brian - I have no such problems at all. Tested it on 2 Laptops running Ubuntu 14.04. I have never seen a black window. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1353951 Title: gnome online accounts require autentication on startup Status in Evolution Data Server: Fix Released Status in “evolution-data-server” package in Ubuntu: Fix Released Status in “gnome-online-accounts” package in Ubuntu: Invalid Status in “evolution-data-server” source package in Trusty: Fix Committed Status in “gnome-online-accounts” source package in Trusty: Invalid Bug description: [Impact] Google calendar integration is broken, and users are requested to re-enter their Google password everytime they log in, or everytime they enable/disable their Google account from the System Settings. [Test Case] 1) open gnome-online-accounts 2) click + and add a google account 3) enter user name and password 4) confirm permissions for gnome 5) Black window pops up and asks for google password, but does not accept the correct password. Google Contacts are not available in Gnome or Thunderbird [Regression Potential] Minimal: the fix is a backport of a patch from the evolution-data-server code which is already in 14.10, and which only touches the calendar code (which is currently broken). Gnome online accounts requires autentication on startup, but even typing the correct password in the box, the program says the password is wrong. By the way evolution and other programs work well with online accounts. I'm using Ubuntu-gnome 14.04 LTS 64bit on different machines and have the same behaviour. Just to be clear: online-accounts works well, just at startup it opens an "administration" window where it requires to insert the password for my google accounts; if I type the correct password it says that the password is wrong, the only way to close the window is to click on "discard" and then all works well. To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1353951/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368436] Re: camera-app crashes after quickly opening and closing app
Bill, mind assigning this bug to Florian or someone else in your team? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1368436 Title: camera-app crashes after quickly opening and closing app Status in “camera-app” package in Ubuntu: Invalid Status in “libhybris” package in Ubuntu: Invalid Status in “qtubuntu-camera” package in Ubuntu: New Bug description: summary: camera-app crashes after quickly opening and closing app steps: 1. open camera app 2. close camera app 3. open camera app 4. close camera app expected result: no crash happens actual results: camera app crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1368436/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368436] Re: camera-app crashes after quickly opening and closing app
Made a simple patch to avoid this crash, but it's now showing up a
different one in libQt5QML, so this needs to be investigated by someone
that knows the stack better than I do.
Patch I used to avoid the crash described by this bug:
rsalveti@evasys:/tmp/camera/qtubuntu-camera$ bzr diff
=== modified file 'src/aalcameraexposurecontrol.cpp'
--- src/aalcameraexposurecontrol.cpp2014-07-10 14:59:10 +
+++ src/aalcameraexposurecontrol.cpp2014-09-19 06:06:32 +
@@ -65,7 +65,8 @@
return false;
}
-if (parameter == QCameraExposureControl::ExposureMode) {
+if ((parameter == QCameraExposureControl::ExposureMode) &&
+
(m_service->androidControl() != NULL)) {
m_requestedExposureMode = value.value();
Q_EMIT requestedValueChanged(QCameraExposureControl::ExposureMode);
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to camera-app in Ubuntu.
https://bugs.launchpad.net/bugs/1368436
Title:
camera-app crashes after quickly opening and closing app
Status in “camera-app” package in Ubuntu:
Invalid
Status in “libhybris” package in Ubuntu:
Invalid
Status in “qtubuntu-camera” package in Ubuntu:
New
Bug description:
summary:
camera-app crashes after quickly opening and closing app
steps:
1. open camera app
2. close camera app
3. open camera app
4. close camera app
expected result:
no crash happens
actual results:
camera app crashes
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1368436/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 299838] Re: /etc/cron.daily/find should be deleted when upgrading or it should use ionice -n instead of -p
Wheee this bug manifested on my server after I upgraded Ubuntu 10.04 to 12.04 to 14.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to findutils in Ubuntu. https://bugs.launchpad.net/bugs/299838 Title: /etc/cron.daily/find should be deleted when upgrading or it should use ionice -n instead of -p Status in GNU Find Utilities: New Status in “findutils” package in Ubuntu: Confirmed Bug description: Binary package hint: findutils In a fresh install of Intrepid there is no '/etc/cron.daily/find' file. However, when upgrading from Hardy to Intrepid, a previously existing '/etc/cron.daily/find' is retained (and even included in /var/lib/dpkg/info/findutils.list which I find strange). The problem with the retained '/etc/cron.daily/find' file is that it uses the 'ionice' command with a wrong argument '-p', supplying a scheduling-class specific priority value as an argument of '-p' which takes actually a PID value. The correct option would be '-n', and this is correct in the Intrepid '/etc/cron.daily/locate' coming from the locate package. The use of '-p' makes '/etc/cron.daily/find' fail with 'exit 1' randomly, depending on if there is a process with a PID equal to a priority value running in the system. If you purge 'findutils' from an upgraded Intrepid system and then reinstall it, the '/etc/cron.daily/find' file disappears and all is well. However, this should probably happen automatically when findutils is upgraded. Description: Ubuntu 8.10 Release: 8.10 Linux version 2.6.27-7-generic (buildd@palmer) (gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu11) ) #1 SMP Tue Nov 4 19:33:20 UTC 2008 findutils: 4.4.0-2ubuntu3 locate: 4.4.0-2ubuntu3 both come from source package findutils To manage notifications about this bug go to: https://bugs.launchpad.net/findutils/+bug/299838/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371058] Re: Regression: Latest apt security update returns Hash Sum mismatch for file: URI:s
Hi Michael, - Updated apt from ppa mvo/lp1371058 - Did a new 14.04 64bit installation with our repository and with apt 1.0.1ubuntu2.4~ppa1 - Installation succeeded - apt-get update && apt-get dist-upgrade succeeded, too Thanks! -- 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/1371058 Title: Regression: Latest apt security update returns Hash Sum mismatch for file: URI:s Status in “apt” package in Ubuntu: In Progress Status in “apt” source package in Lucid: Confirmed Status in “apt” source package in Precise: Confirmed Status in “apt” source package in Trusty: Confirmed Status in “apt” source package in Utopic: In Progress Status in “apt” package in Debian: New Bug description: When running 'apt-get update' on Ubuntu Lucid using 0.7.25.3ubuntu9.16 I get Hash Sum mismatch when using file: URI:s. First time running apt-get update after cleaning /var/lib/dpkg/lists/ and /var/lib/dpkg/lists/partial it works. However the second time I get: root@crepes:/etc/apt# apt-get update Ign file:/mirrors/ubuntu/ubuntu/ lucid-security/main Translation-en_DK Ign file:/mirrors/ubuntu/ubuntu/ lucid-security/restricted Translation-en_DK Ign file:/mirrors/ubuntu/ubuntu/ lucid-security/universe Translation-en_DK Ign file:/mirrors/ubuntu/ubuntu/ lucid-security/multiverse Translation-en_DK Get:1 file: lucid-security Release.gpg [198B] Get:2 file: lucid-security Release [57,3kB] Hit http://security.ubuntu.com lucid-security Release.gpg Ign http://security.ubuntu.com/ubuntu/ lucid-security/main Translation-en_DK Ign http://security.ubuntu.com/ubuntu/ lucid-security/restricted Translation-en_DK Ign http://security.ubuntu.com/ubuntu/ lucid-security/universe Translation-en_DK Ign http://security.ubuntu.com/ubuntu/ lucid-security/multiverse Translation-en_DK Hit http://security.ubuntu.com lucid-security Release Hit http://security.ubuntu.com lucid-security/main Packages Hit http://security.ubuntu.com lucid-security/restricted Packages Hit http://security.ubuntu.com lucid-security/universe Packages Hit http://security.ubuntu.com lucid-security/multiverse Packages W: Failed to fetch file:/mirrors/ubuntu/ubuntu/dists/lucid-security/main/binary-amd64/Packages.bz2 Hash Sum mismatch W: Failed to fetch file:/mirrors/ubuntu/ubuntu/dists/lucid- security/restricted/binary-amd64/Packages.bz2 Hash Sum mismatch W: Failed to fetch file:/mirrors/ubuntu/ubuntu/dists/lucid- security/universe/binary-amd64/Packages.bz2 Hash Sum mismatch W: Failed to fetch file:/mirrors/ubuntu/ubuntu/dists/lucid- security/multiverse/binary-amd64/Packages.bz2 Hash Sum mismatch E: Some index files failed to download, they have been ignored, or old ones used instead. Runnng apt-get -o Acquire::CompressionTypes::Order="gz" changing to bz2 every second it works. Reverting back to 0.7.25.3ubuntu9.15 it works. And, of course, it works if only using http: URI:s. Looks like a regression in 0.7.25.3ubuntu9.16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1371058/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368436] Re: camera-app crashes after quickly opening and closing app
Yeah, even when hybris is actually working with a proper assert, that still causes a crash with an abort. The real fix here is in qtubuntu- camera, to make sure control is actually valid when using it. This is a race when shutting down the app, and seems to be easier to crash now that for some unknown reason the startup is a bit slower. ** Changed in: libhybris (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1368436 Title: camera-app crashes after quickly opening and closing app Status in “camera-app” package in Ubuntu: Invalid Status in “libhybris” package in Ubuntu: Invalid Status in “qtubuntu-camera” package in Ubuntu: New Bug description: summary: camera-app crashes after quickly opening and closing app steps: 1. open camera app 2. close camera app 3. open camera app 4. close camera app expected result: no crash happens actual results: camera app crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1368436/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371293] Re: console-kit-daemon[5037]: GLib-CRITICAL: Source ID 40 was not found when attempting to remove it
*** This bug is a duplicate of bug 1313042 *** https://bugs.launchpad.net/bugs/1313042 ** This bug has been marked a duplicate of bug 1313042 console-kit-daemon Glib-CRITICAL warning -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to consolekit in Ubuntu. https://bugs.launchpad.net/bugs/1371293 Title: console-kit-daemon[5037]: GLib-CRITICAL: Source ID 40 was not found when attempting to remove it Status in “consolekit” package in Ubuntu: New Bug description: Hi, In syslog there is critical error/s: Sep 18 21:15:38 hostname console-kit-daemon[5037]: GLib-CRITICAL: Source ID 40 was not found when attempting to remove it Sep 18 21:15:38 hostname console-kit-daemon[5037]: GLib-CRITICAL: Source ID 49 was not found when attempting to remove it apt-cache policy consolekit consolekit: Installed: 0.4.6-5 Candidate: 0.4.6-5 Version table: *** 0.4.6-5 0 500 http://archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status lsb_release -rd Description: Ubuntu Utopic Unicorn (development branch) Release: 14.10 Thank You, Kind Regards, Martin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/1371293/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1353379] Re: VoiceMail notification pretends there are 255 messages. It is not true there are only 2
I recommend to check the behaviour in reference phone with those SIM cards. I would not be surprised if T-Mobile for example just does not update the count. Also it would be interesting to know what was your exact test sequence. Did you see the lp1353379-krillin.png run time or after restarting ofono? If you did it see it run-time, did the message count change after restarting the ofono? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/1353379 Title: VoiceMail notification pretends there are 255 messages. It is not true there are only 2 Status in “indicator-messages” package in Ubuntu: Invalid Status in “ofono” package in Ubuntu: Triaged Bug description: Mako build #175 The VoiceMail notification indicates there are 255 voice messages (cf screenshot) on voice mail while there were only 2 new messages. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: indicator-messages 13.10.1+14.10.20140725-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.5-0ubuntu3 Architecture: armhf Date: Wed Aug 6 11:57:43 2014 InstallationDate: Installed on 2014-08-06 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140806-020204) SourcePackage: indicator-messages UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1353379/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371318] Re: tracker-extract crashed with SIGSEGV in gst_base_parse_push_frame()
*** This bug is a duplicate of bug 1301914 *** https://bugs.launchpad.net/bugs/1301914 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1301914, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1371318/+attachment/4208056/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1371318/+attachment/4208058/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1371318/+attachment/4208059/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1371318/+attachment/4208060/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1371318/+attachment/4208061/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1371318/+attachment/4208062/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1371318/+attachment/4208063/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1301914 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1371318 Title: tracker-extract crashed with SIGSEGV in gst_base_parse_push_frame() Status in “tracker” package in Ubuntu: New Bug description: ? ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: tracker-extract 1.0.4-0ubuntu1 Uname: Linux 3.16.3-031603-generic x86_64 NonfreeKernelModules: fglrx wl ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Thu Sep 18 23:22:01 2014 ExecutablePath: /usr/lib/tracker/tracker-extract InstallationDate: Installed on 2014-09-08 (10 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140826) ProcCmdline: /usr/lib/tracker/tracker-extract ProcEnviron: LD_LIBRARY_PATH= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f8b904150a8:mov%rbx,0x48(%rax) PC (0x7f8b904150a8) ok source "%rbx" ok destination "0x48(%rax)" (0x0048) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: tracker StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgstaudio-1.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgstaudio-1.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgstaudio-1.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 gst_base_parse_push_frame () from /usr/lib/x86_64-linux-gnu/libgstbase-1.0.so.0 Title: tracker-extract crashed with SIGSEGV in gst_base_parse_push_frame() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1371318/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371217] Re: tracker-extract crashed with SIGABRT in g_malloc0()
*** This bug is a duplicate of bug 1364780 *** https://bugs.launchpad.net/bugs/1364780 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1364780, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1371217/+attachment/4207732/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1371217/+attachment/4207734/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1371217/+attachment/4207736/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1371217/+attachment/4207737/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1371217/+attachment/4207738/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1371217/+attachment/4207739/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1371217/+attachment/4207740/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1364780 tracker-extract crashed with SIGABRT in g_malloc0() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1371217 Title: tracker-extract crashed with SIGABRT in g_malloc0() Status in “tracker” package in Ubuntu: New Bug description: tracker-extract crashed with SIGABRT in g_malloc0() ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: tracker-extract 1.0.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2 Uname: Linux 3.16.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Thu Sep 18 20:26:16 2014 ExecutablePath: /usr/lib/tracker/tracker-extract InstallationDate: Installed on 2014-07-10 (70 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) ProcCmdline: /usr/lib/tracker/tracker-extract Signal: 6 SourcePackage: tracker StacktraceTop: g_malloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_slice_free1 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_queue_pop_tail () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: tracker-extract crashed with SIGABRT in g_malloc0() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1371217/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1272686] Re: indicator-bluetooth-service crashed with SIGSEGV in org_bluez_adapter_set_property()
I also got this bug manifest itself when my BT controller stopped working for some reason (another bug?) lsusb -s 024 -v Bus 001 Device 024: ID 13d3:3362 IMC Networks Couldn't open device, some information will be missing Asus notebook model N76V, internal USB adapter -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1272686 Title: indicator-bluetooth-service crashed with SIGSEGV in org_bluez_adapter_set_property() Status in “indicator-bluetooth” package in Ubuntu: Triaged Bug description: After activating bluetooth. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: indicator-bluetooth 0.0.6+14.04.20140124-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-1.16-generic 3.13.0-rc7 Uname: Linux 3.13.0-1-generic x86_64 ApportVersion: 2.13.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jan 25 15:02:43 2014 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-bluetooth/indicator-bluetooth-service InstallationDate: Installed on 2013-12-10 (45 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64+mac (20131210) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-bluetooth/indicator-bluetooth-service SegvAnalysis: Segfault happened at: 0x40d880: mov(%rbx),%rdi PC (0x0040d880) ok source "(%rbx)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: indicator-bluetooth StacktraceTop: ?? () ?? () ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: indicator-bluetooth-service crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1272686/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368436] Re: camera-app crashes after quickly opening and closing app
** Also affects: qtubuntu-camera (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1368436 Title: camera-app crashes after quickly opening and closing app Status in “camera-app” package in Ubuntu: Invalid Status in “libhybris” package in Ubuntu: Confirmed Status in “qtubuntu-camera” package in Ubuntu: New Bug description: summary: camera-app crashes after quickly opening and closing app steps: 1. open camera app 2. close camera app 3. open camera app 4. close camera app expected result: no crash happens actual results: camera app crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1368436/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1192651] Re: subunit should depend on python3-junitxml
[Expired for subunit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: subunit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to subunit in Ubuntu. https://bugs.launchpad.net/bugs/1192651 Title: subunit should depend on python3-junitxml Status in “subunit” package in Ubuntu: Expired Bug description: $ trial --reporter=subunit landscape/lib/tests/test_bpickle.py | /usr/bin/subunit2junitxml python-junitxml (https://launchpad.net/pyjunitxml or http://pypi.python.org/pypi/junitxml) is required for this filter.Traceback (most recent call last): File "/usr/bin/subunit2junitxml", line 27, in from junitxml import JUnitXmlResult ImportError: No module named 'junitxml' There is no "python3-junitxml" in the repositories. python-junitxml is installed on the system but only contains 2.7 libraries. UPDATE: as of now, there is a python3-junitxml. It just needs to be included as a dep. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subunit/+bug/1192651/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1345664] Re: [PI945GCM, SigmaTel STAC9221 A2, Green Speaker, Rear] No sound at all
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1345664 Title: [PI945GCM, SigmaTel STAC9221 A2, Green Speaker, Rear] No sound at all Status in “pulseaudio” package in Ubuntu: Expired Bug description: I can't hear any sounds on the computer ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vibhas 1745 F pulseaudio vibhas 2010 F volti /dev/snd/pcmC0D1p: vibhas 1745 F...m pulseaudio CurrentDesktop: Unity Date: Sun Jul 20 23:16:56 2014 InstallationDate: Installed on 2014-06-18 (32 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vibhas 1745 F pulseaudio vibhas 2010 F volti /dev/snd/pcmC0D1p: vibhas 1745 F...m pulseaudio Symptom_Jack: Green Speaker, Rear Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [PI945GCM, SigmaTel STAC9221 A2, Green Speaker, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080012 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: PI945GCM dmi.board.vendor: Kobian dmi.board.version: ECS dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Kobian dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080012:bd08/16/2007:svnKobian:pnPI945GCM:pvr1.X:rvnKobian:rnPI945GCM:rvrECS:cvnKobian:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: PI945GCM dmi.product.version: 1.X dmi.sys.vendor: Kobian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1345664/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368436] Re: camera-app crashes after quickly opening and closing app
This seems to be a mix of issues, but the crash itself is caused because android_camera_set_scene_mode gets called after control gets released. In theory the correct result here would be an abort, but it seems assert is not behaving properly, which I'm now investigating why. Besides that, the release/closing race seems to be actually part of qtubuntu-camera, and not hybris. #0 my_pthread_mutex_lock (__mutex=0x8) at hooks.c:479 #1 0xa9d66f9c in android::Mutex::lock (this=this@entry=0x8) at system/core/include/utils/Mutex.h:112 #2 0xa9d67266 in Autolock (mutex=..., this=0xbef1ba70) at system/core/include/utils/Mutex.h:65 #3 android_camera_set_scene_mode (control=0x0, mode=SCENE_MODE_AUTO) at ubuntu/libhybris/compat/camera/camera_compatibility_layer.cpp:304 #4 0xac3413e4 in android_camera_set_scene_mode (n1=0x0, n2=SCENE_MODE_AUTO) at camera.c:50 #5 0xac37f848 in AalCameraExposureControl::setValue(QCameraExposureControl::ExposureParameter, QVariant const&) () from /usr/lib/arm-linux-gnueabihf/qt5/plugins/mediaservice/libaalcamera.so #6 0xacd1c0fc in AdvancedCameraSettings::setHdrEnabled(bool) () from /usr/share/click/preinstalled/com.ubuntu.camera/3.0.0.387/lib/arm-linux-gnueabihf/CameraApp/libcamera-qml.so #7 0xacd2147c in AdvancedCameraSettings::qt_metacall(QMetaObject::Call, int, void**) () from /usr/share/click/preinstalled/com.ubuntu.camera/3.0.0.387/lib/arm-linux-gnueabihf/CameraApp/libcamera-qml.so #8 0xb6620c74 in QQmlPropertyPrivate::write(QObject*, QQmlPropertyData const&, QVariant const&, QQmlContextData*, QFlags) () from /usr/lib/arm-linux-gnueabihf/libQt5Qml.so.5 #9 0xb662135a in QQmlPropertyPrivate::writeValueProperty(QObject*, QQmlPropertyData const&, QVariant const&, QQmlContextData*, QFlags) () from /usr/lib/arm-linux-gnueabihf/libQt5Qml.so.5 #10 0xb66213f4 in QQmlPropertyPrivate::writeValueProperty(QVariant const&, QFlags) () from /usr/lib/arm-linux-gnueabihf/libQt5Qml.so.5 #11 0xb6621474 in QQmlProperty::write(QVariant const&) const () from /usr/lib/arm-linux-gnueabihf/libQt5Qml.so.5 #12 0xb66995b6 in ?? () from /usr/lib/arm-linux-gnueabihf/libQt5Qml.so.5 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1368436 Title: camera-app crashes after quickly opening and closing app Status in “camera-app” package in Ubuntu: Invalid Status in “libhybris” package in Ubuntu: Confirmed Bug description: summary: camera-app crashes after quickly opening and closing app steps: 1. open camera app 2. close camera app 3. open camera app 4. close camera app expected result: no crash happens actual results: camera app crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1368436/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1360606] Re: libcairo.so for Ubuntu 14.04 is dead-slow compared to Ubuntu 13.10
Thanks peter and chris, sounds like the issue is resolved so I'll close the bug as suggested. ** Changed in: cairo (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1360606 Title: libcairo.so for Ubuntu 14.04 is dead-slow compared to Ubuntu 13.10 Status in “cairo” package in Ubuntu: Fix Released Bug description: I'm running the video mixer software called Snowmix that uses libcairo extensively. After updating to Ubuntu 14.04 Desktop amd64, I noticed that mixing video required 8 times more CPU compared to Ubuntu 13.10. Using oprofile I discovered the heavy CPU load was taking place in libpixman used by libcairo. However libpixman is currently the same release in Ubuntu 14.04 and 13.10. However I did notice that libcairo got upgraded from libcairo.so.2.11200.16 in Ubuntu 13.10 to libcairo.so.2.11301.0 in Uuntu 14.04. Snowmix uses libcairo2 primarily for scaling and rotating images and overlay them in memory. Replacing libcairo.so.2.11301.0 with libcairo.so.2.11200.16 in Ubuntu 14.04 lower the CPU usage by at least 8 times. So I suspect that libcairo for Ubuntu 14.04 somehow got compiled without the hardware acceleration such as MMX/SSE2/SSE3 etc. This is quite bad if this is the case. If it is not the case, something else is seriously wrong with libcairo2. 1)Description:Ubuntu 14.04.1 LTS Release:14.04 2) libcairo2: Installed: 1.13.0~20140204-0ubuntu1 Candidate: 1.13.0~20140204-0ubuntu1 Version table: *** 1.13.0~20140204-0ubuntu1 0 500 http://dk.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status 3) I expected libcairo2 (libcairo.so.2.11301.0) for Ubuntu14.04 to work as efficient as libcairo2 (libcairo.so.2.11200.16)for Ubuntu13.10. 4) Libcairo2 for Ubuntu 14.04 works 8 times slower indicating a lack of MMX/SSE2/SSE3 etc acceleration. For the source, you have the source for libcairo2 for Ubuntu14.04. I can provide you with the source code for Snowmix using libcairo2, but I don't expected you need it nor want it. Best regards Peter Maersk-Moller ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libcairo2 1.13.0~20140204-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Sat Aug 23 15:23:38 2014 InstallationDate: Installed on 2013-06-21 (428 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cairo UpgradeStatus: Upgraded to trusty on 2014-08-20 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1360606/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1086295] Re: Cannot log in with more passwd entries with the same UID
** Changed in: lightdm Status: New => Triaged ** Changed in: lightdm (Ubuntu) Status: New => Triaged ** Also affects: lightdm/1.10 Importance: Undecided Status: New ** Changed in: lightdm/1.10 Status: New => Triaged ** Changed in: lightdm/1.10 Importance: Undecided => Medium -- 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/1086295 Title: Cannot log in with more passwd entries with the same UID Status in Light Display Manager: Triaged Status in Light Display Manager 1.10 series: Triaged Status in “lightdm” package in Ubuntu: Triaged Bug description: I am not sure if it's a bug, however this works on the text console without problem since years. Yes, that is ugly, I know: sometimes I need to test (while developing) softwares run as a specific unix user. To make this simple I often used the trick to add a line to /etc/passwd with different user name but the same numeric uid/gid as my account used to log in at lightdm's prompt. Usually I remove that line then, but I forgot it, and after reboot I couldn't log in. According to /var/log/lightdm/lightdm.log lightdm treated as I want to use as this "phantom" user, which is not true. Using simple console login there is no such a problem. AFAIK it's not so nice/legal to use /etc/passed entries refeering for the same unix numerical uid, so I am not sure if it's a bug which should be fixed, or it's something I shouldn't do, but as I've written above, it works (and always worked since 1995 on Debian/Ubuntu/Slackware/RedHat systems - as far as I can recall) on console logins at least. By the way, I haven't added /etc/shadow entry for the user, only /etc/passwd. And of course I tried to log in with my "normal" user, not the "phantom". thanks! ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: lightdm 1.4.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Uname: Linux 3.5.0-19-generic i686 ApportVersion: 2.6.1-0ubuntu7 Architecture: i386 Date: Tue Dec 4 09:39:42 2012 InstallationDate: Installed on 2012-03-01 (277 days ago) InstallationMedia: Ubuntu-Server 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.2) MarkForUpload: True SourcePackage: lightdm UpgradeStatus: Upgraded to quantal on 2012-03-01 (277 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1086295/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371146] Re: packaging bug in ubuntu-location-service-2/com/ubuntu/location/units/units.h
** Changed in: location-service (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1371146 Title: packaging bug in ubuntu-location- service-2/com/ubuntu/location/units/units.h Status in “location-service” package in Ubuntu: In Progress Bug description: units.h contains this include: #include http://bazaar.launchpad.net/~phablet-team/location-service/trunk/view/head:/include/location_service/com/ubuntu/location/units/units.h#L21 which is only available in the libboost-dev package: $ apt-file search boost/units/cmath.hpp libboost1.54-dev: /usr/include/boost/units/cmath.hpp libboost1.55-dev: /usr/include/boost/units/cmath.hpp which are not in the build dependencies of the location service dev package. This causes problems for downstreams like platform-api, which only averts the build problem by including other dependencies that rely on boost (mir specifically) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1371146/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371401] [NEW] randomly freezing
Public bug reported: Seems to be related to https://bugs.launchpad.net/ubuntu/+source/nvidia- prime/+bug/1220426 ASUS N550JK Touchscreen nVidia 343 graphics on Geforce GTX 850M Latest Linux kernel 3.16, Ubuntu 14.04 with xfce Screen can be unfrozen by doing ctrl+alt+f6 and then back with ctrl+alt+f6. Sometimes the touch screen and keyboard will continue to work but the touchpad will not. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 Uname: Linux 3.16.0-031600-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 343.13 Thu Jul 31 19:06:44 PDT 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Sep 18 23:12:46 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-35-generic, x86_64: installed bbswitch, 0.7, 3.16.0-031600-generic, x86_64: installed nvidia-343, 343.13, 3.16.0-031600-generic, x86_64: installed psmouse, elantech-x551c, 3.13.0-35-generic, x86_64: installed psmouse, elantech-x551c, 3.16.0-031600-generic, x86_64: installed GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:11cd] Subsystem: ASUSTeK Computer Inc. Device [1043:11cd] InstallationDate: Installed on 2014-09-17 (1 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: ASUSTeK COMPUTER INC. N550JK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-031600-generic root=UUID=31b12bbb-0095-44fd-b6e6-6964171a74b2 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N550JK.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N550JK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN550JK.204:bd01/23/2014:svnASUSTeKCOMPUTERINC.:pnN550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Sep 18 22:30:52 2014 xserver.configfile: /etc/X11/xorg.conf xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug possible-manual-nvidia-install third-party-packages trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1371401 Title: randomly freezing Status in “xorg” package in Ubuntu: New Bug description: Seems to be related to https://bugs.launchpad.net/ubuntu/+source /nvidia-prime/+bug/1220426 ASUS N550JK Touchscreen nVidia 343 graphics on Geforce GTX 850M Latest Linux kernel 3.16, Ubuntu 14.04 with xfce Screen can be unfrozen by doing ctrl+alt+f6 and then back with ctrl+alt+f6. Sometimes the touch screen and keyboard will continue to work but the touchpad will not. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 Uname: Linux 3.16.0-031600-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 343.13 Thu Jul 31 19:06:44 PDT 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Sep 18 23:12:46 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-35-generic, x86_64: installed bbswitch, 0.7, 3.16.0-031600-generic, x86_64: installed nvidia-343, 343.13, 3.16.0-031600-generic, x86_64: installed psmouse
[Touch-packages] [Bug 1370866] Re: Overly strict libmirplatform* dependencies are blocking CI
Dropped importance. We now have a workaround to unblock CI while the build machines still have the overly strict 0.7.2 installed on them. ** Changed in: mir Importance: Critical => High ** Changed in: mir/0.7 Importance: Critical => High ** Changed in: mir (Ubuntu) Importance: Critical => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1370866 Title: Overly strict libmirplatform* dependencies are blocking CI Status in Mir: Fix Committed Status in Mir 0.7 series: Fix Committed Status in “mir” package in Ubuntu: Triaged Bug description: Overly strict libmirplatform* dependencies are blocking CI. But fortunately we already landed a fix for this in 0.8. Just needs backporting to 0.7 ASAP... Starting pkgProblemResolver with broken count: 2 Starting 2 pkgProblemResolver with broken count: 2 Investigating (0) libmirplatformgraphics-android [ armhf ] < 0.7.2+14.10.20140912-0ubuntu1 > ( universe/libs ) Broken libmirplatformgraphics-android:armhf Depends on libmirplatform2 [ armhf ] < 0.7.2+14.10.20140912-0ubuntu1 -> 0.7.2+14.10.20140912bzr1917pkg0utopic713+autopilot0 > ( libs ) (= 0.7.2+14.10.20140912-0ubuntu1) Considering libmirplatform2:armhf 10006 as a solution to libmirplatformgraphics-android:armhf 1 Removing libmirplatformgraphics-android:armhf rather than change libmirplatform2:armhf Investigating (0) ubuntu-touch [ armhf ] < 1.185 > ( universe/metapackages ) Broken ubuntu-touch:armhf Depends on libmirplatformgraphics-android [ armhf ] < 0.7.2+14.10.20140912-0ubuntu1 > ( universe/libs ) Considering libmirplatformgraphics-android:armhf 1 as a solution to ubuntu-touch:armhf 0 Removing ubuntu-touch:armhf rather than change libmirplatformgraphics-android:armhf Investigating (0) libmirplatformgraphics-mesa [ armhf ] < 0.7.2+14.10.20140912-0ubuntu1 > ( libs ) Broken libmirplatformgraphics-mesa:armhf Depends on libmirplatform2 [ armhf ] < 0.7.2+14.10.20140912-0ubuntu1 -> 0.7.2+14.10.20140912bzr1917pkg0utopic713+autopilot0 > ( libs ) (= 0.7.2+14.10.20140912-0ubuntu1) Considering libmirplatform2:armhf 10006 as a solution to libmirplatformgraphics-mesa:armhf 0 Removing libmirplatformgraphics-mesa:armhf rather than change libmirplatform2:armhf Investigating (1) libmirserver25 [ armhf ] < 0.7.2+14.10.20140912-0ubuntu1 > ( libs ) Broken libmirserver25:armhf Depends on libmirplatformgraphics-mesa [ armhf ] < 0.7.2+14.10.20140912-0ubuntu1 > ( libs ) (= 0.7.2+14.10.20140912-0ubuntu1) Considering libmirplatformgraphics-mesa:armhf 0 as a solution to libmirserver25:armhf 3 Added libmirplatformgraphics-mesa:armhf to the remove list Broken libmirserver25:armhf Depends on libmirplatformgraphics-android [ armhf ] < 0.7.2+14.10.20140912-0ubuntu1 > ( universe/libs ) (= 0.7.2+14.10.20140912-0ubuntu1) Considering libmirplatformgraphics-android:armhf 1 as a solution to libmirserver25:armhf 3 Added libmirplatformgraphics-android:armhf to the remove list Fixing libmirserver25:armhf via keep of libmirplatformgraphics-mesa:armhf Fixing libmirserver25:armhf via keep of libmirplatformgraphics-android:armhf Investigating (1) libmirplatformgraphics-android [ armhf ] < 0.7.2+14.10.20140912-0ubuntu1 > ( universe/libs ) Broken libmirplatformgraphics-android:armhf Depends on libmirplatform2 [ armhf ] < 0.7.2+14.10.20140912-0ubuntu1 -> 0.7.2+14.10.20140912bzr1917pkg0utopic713+autopilot0 > ( libs ) (= 0.7.2+14.10.20140912-0ubuntu1) Considering libmirplatform2:armhf 10006 as a solution to libmirplatformgraphics-android:armhf 1 Removing libmirplatformgraphics-android:armhf rather than change libmirplatform2:armhf Investigating (1) libmirplatformgraphics-mesa [ armhf ] < 0.7.2+14.10.20140912-0ubuntu1 > ( libs ) Broken libmirplatformgraphics-mesa:armhf Depends on libmirplatform2 [ armhf ] < 0.7.2+14.10.20140912-0ubuntu1 -> 0.7.2+14.10.20140912bzr1917pkg0utopic713+autopilot0 > ( libs ) (= 0.7.2+14.10.20140912-0ubuntu1) Considering libmirplatform2:armhf 10006 as a solution to libmirplatformgraphics-mesa:armhf 0 Removing libmirplatformgraphics-mesa:armhf rather than change libmirplatform2:armhf Investigating (2) libmirserver25 [ armhf ] < 0.7.2+14.10.20140912-0ubuntu1 > ( libs ) Broken libmirserver25:armhf Depends on libmirplatformgraphics-mesa [ armhf ] < 0.7.2+14.10.20140912-0ubuntu1 > ( libs ) (= 0.7.2+14.10.20140912-0ubuntu1) Considering libmirplatformgraphics-mesa:armhf 0 as a solution to libmirserver25:armhf 3 Added libmirplatformgraphics-mesa:armhf to the remove list Broken libmirserver25:armhf Depends on libmirplatformgraphics-android [ armhf ] < 0.7.2+14.10.20140912-0ubuntu1 > ( universe/libs ) (= 0.7.2+14.10.20140912-0ubuntu1) Considering libmirplatformgraphics-android:armhf 1 as a solution to libmirserver25:armhf 3 Added libmirplatformgraphi
[Touch-packages] [Bug 1367883] Re: Add Microsoft-owned MAC address to 75-persistent-net-generator.rules
This bug was fixed in the package systemd - 208-8ubuntu4 --- systemd (208-8ubuntu4) utopic; urgency=medium * debian/tests/boot-and-services: Accept lower-case spelling of "command line" in dmesg log. Curiously the case differs between amd64 and i386.. -- Martin PittThu, 18 Sep 2014 21:10:42 +0200 ** Changed in: systemd (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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1367883 Title: Add Microsoft-owned MAC address to 75-persistent-net-generator.rules Status in “systemd” package in Ubuntu: Fix Released Status in “systemd” source package in Precise: Triaged Status in “systemd” source package in Trusty: Triaged Bug description: Impact: As Microsoft expands its public cloud offering it may need to utilize additional MAC address prefixes. If a user launches a Cloud instance when the MAC address is from a Microsoft-owned MAC address that is not in the exclusion list, eth0 is persistently named for the first NIC seen. If a user rebundles, or the machines has its MAC address changed (e.g. VM resize or VM is moved to another host), it will lose network connectivity. Fix: Please add the following Microsoft-owned MAC address to the 75 -persistent-net-generator.rules file: 00:25:ae Microsoft Corporation Test Case : - Launch Hyper-V VM with MAC address with prefix 00:25:ae - Install updated Udev/systemd - Delete any existing udev rule - Reboot and confirm that no new UDEV rule was added To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1367883/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1359933] Re: [Hyper-V] hyperv_fb kernel module is not automatically loaded on Ubuntu 14.10
This bug was fixed in the package systemd - 208-8ubuntu4 --- systemd (208-8ubuntu4) utopic; urgency=medium * debian/tests/boot-and-services: Accept lower-case spelling of "command line" in dmesg log. Curiously the case differs between amd64 and i386.. -- Martin PittThu, 18 Sep 2014 21:10:42 +0200 ** Changed in: systemd (Ubuntu Utopic) Status: Fix Committed => Fix Released -- 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/1359933 Title: [Hyper-V] hyperv_fb kernel module is not automatically loaded on Ubuntu 14.10 Status in “systemd” package in Ubuntu: Fix Released Status in “systemd” source package in Utopic: Fix Released Bug description: System details: Linux ubuntu 3.16.0-9-generic #14-Ubuntu SMP Fri Aug 15 15:03:57 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Ubuntu Server 14.10 Daily build from 19th Aug. During the testing we've discovered that the hyperv_fb module is not automatically loaded by the system. The module is used for the 2D FB functionality and in 14.04 and older it was loaded along with all the other Hyper-V LIS kernel modules. Please make the necessary corrections to include hyperv_fb as well. This affects all Windows Server editions, from 2008R2, WS 2012 and WS 2012 R2. The module is also used in runlevel 3, and our test setup has the X server and GUI installed. root@ubuntu:~# lsmod | grep hyperv_fb root@ubuntu:~# root@ubuntu:~# modprobe hyperv_fb root@ubuntu:~# modinfo hyperv_fb filename: /lib/modules/3.16.0-9-generic/kernel/drivers/video/fbdev/hyperv_fb.ko description:Microsoft Hyper-V Synthetic Video Frame Buffer Driver license:GPL srcversion: 7DB9F1496E075EBB679974C alias: pci:v1414d5353svsdbc*sc*i* alias: vmbus:02780ada77e3ac4a8e770558eb1073f8 depends:hv_vmbus intree: Y vermagic: 3.16.0-9-generic SMP mod_unload modversions signer: Magrathea: Glacier signing key sig_key:2A:50:05:BD:65:41:55:43:B9:4A:39:62:EB:AC:4A:19:C5:06:CE:81 sig_hashalgo: sha512 --- ApportVersion: 2.14.6-0ubuntu1 Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 InstallationDate: Installed on 2014-08-19 (2 days ago) InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Alpha amd64 (20140819) IwConfig: eth0 no wireless extensions. lono wireless extensions. virbr0no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-9-generic root=/dev/mapper/hostname--vg-root ro crashkernel=128M@64M ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-9-generic N/A linux-backports-modules-3.16.0-9-generic N/A linux-firmware1.132 RfKill: Tags: utopic Uname: Linux 3.16.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090006 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 1037-8395-2404-3263-1476-7555-72 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090006:bd05/23/2012:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine dmi.product.version: 7.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1359933/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
This bug was fixed in the package systemd - 208-8ubuntu4 --- systemd (208-8ubuntu4) utopic; urgency=medium * debian/tests/boot-and-services: Accept lower-case spelling of "command line" in dmesg log. Curiously the case differs between amd64 and i386.. -- Martin PittThu, 18 Sep 2014 21:10:42 +0200 ** Changed in: systemd (Ubuntu Utopic) Status: Fix Committed => Fix Released -- 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/1367241 Title: Incorrect udev-fallback-graphics.conf Status in “systemd” package in Ubuntu: Fix Released Status in “udev” package in Ubuntu: Invalid Status in “udev” source package in Precise: Fix Committed Status in “systemd” source package in Trusty: Fix Committed Status in “systemd” source package in Utopic: Fix Released Bug description: [Impact] * When setting up primary display driver fails an attempt to load vesafb module is undertaken. This fails since from 3.13.0-16.36 version vesafb is compiled in the kernel (so no actual modprobing is needed). This causes false alert in the log: "Starting load fallback graphic devices: [fail]" [Test Case] * Start Ubuntu unable to load primary graphics driver (the simplest way is to remove module responsible for the device). * Wait for loading graphics devices. * If the primary device module has failed to load, falling back to vesafb will be attempted. [Regression Potential] * Implemented by the bug reported. * Affects only the debian/ directory. [Other Info] * Original bug description: The udev-fallback-graphics.conf script tries to load vesafb module if PRIMARY_DEVICE_FOR_DISPLAY has not been set earlier. The problem is that from kernel version 3.13.0-16.36 vesafb is compiled in permanently into the kernel (CONFIG_FB_VESA=y), so whenever the fallback mode is triggered this script will FAIL confusing the users. Most probably this file is no longer needed (or it just be used to print informative message). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1367241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1370329] Re: systemd's reboot/shutdown programs don't work under upstart
This bug was fixed in the package systemd - 208-8ubuntu4 --- systemd (208-8ubuntu4) utopic; urgency=medium * debian/tests/boot-and-services: Accept lower-case spelling of "command line" in dmesg log. Curiously the case differs between amd64 and i386.. -- Martin PittThu, 18 Sep 2014 21:10:42 +0200 ** Changed in: systemd (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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1370329 Title: systemd's reboot/shutdown programs don't work under upstart Status in “systemd” package in Ubuntu: Fix Released Bug description: Installing systemd-sysv replaces upstart's "reboot", "poweroff" and friends. systemd's binaries currently don't know how to talk to upstart to "forward" the request to upstart. This breaks a transition to systemd as default init which doesn't just change the boot= kernel parameter but installs systemd-sysv. The same problem happens when systemd-sysv is installed but the system gets booted with init=/sbin/upstart. It would be useful if one could do "initctl reboot", so that there's always a way to reboot the system when using a different init= than /sbin/init. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1370329/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371390] [NEW] pictures taken with camera have wrong timestamp
Public bug reported: krillin rtm build 46 - phone is set for Eastern time zone (utc -4) - take a picture with the camera - apt-get install exiv2 onto the phone - cd ~/Pictures/com.ubuntu.camera - exiv2 .jpg Expected results: Image Timestamp in meta data should match the local time on the phone, with TZ offset applied Actual results: Image Timestamp is 6 hours ahead of my timezone The problem with this is the gallery app uses the timestamps found in the exiv data to display events, so a photos are showing up on the incorrect day ** Affects: qtubuntu-camera (Ubuntu) Importance: High Assignee: Ugo Riboni (uriboni) Status: New ** Tags: rtm14 ** Tags added: rtm14 ** Changed in: qtubuntu-camera (Ubuntu) Importance: Undecided => High ** Changed in: qtubuntu-camera (Ubuntu) Assignee: (unassigned) => Ugo Riboni (uriboni) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu-camera in Ubuntu. https://bugs.launchpad.net/bugs/1371390 Title: pictures taken with camera have wrong timestamp Status in “qtubuntu-camera” package in Ubuntu: New Bug description: krillin rtm build 46 - phone is set for Eastern time zone (utc -4) - take a picture with the camera - apt-get install exiv2 onto the phone - cd ~/Pictures/com.ubuntu.camera - exiv2 .jpg Expected results: Image Timestamp in meta data should match the local time on the phone, with TZ offset applied Actual results: Image Timestamp is 6 hours ahead of my timezone The problem with this is the gallery app uses the timestamps found in the exiv data to display events, so a photos are showing up on the incorrect day To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtubuntu-camera/+bug/1371390/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1348110] Re: [dialer-app] "Please enter a number" label is too big for some translations
** Branch linked: lp:~boiko/dialer-app/resize_text_hint -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1348110 Title: [dialer-app] "Please enter a number" label is too big for some translations Status in Dialer app for Ubuntu Touch: In Progress Status in Ubuntu UX bugs: Fix Committed Status in “dialer-app” package in Ubuntu: In Progress Bug description: Here's a screenshot from German translation. I guess the font size should be reduced in such cases. To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1348110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1348110] Re: [dialer-app] "Please enter a number" label is too big for some translations
** Changed in: dialer-app Status: Confirmed => In Progress ** Changed in: dialer-app (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1348110 Title: [dialer-app] "Please enter a number" label is too big for some translations Status in Dialer app for Ubuntu Touch: In Progress Status in Ubuntu UX bugs: Fix Committed Status in “dialer-app” package in Ubuntu: In Progress Bug description: Here's a screenshot from German translation. I guess the font size should be reduced in such cases. To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1348110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1318008] Re: Core apps .desktop files do not include translated strings
Fix committed into lp:ubuntu-rssreader-app at revision 313, scheduled for release in ubuntu-rssreader-app, milestone alpha-1 ** Changed in: ubuntu-rssreader-app Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1318008 Title: Core apps .desktop files do not include translated strings Status in Address Book App: Fix Released Status in Camera App: Fix Released Status in Dialer app for Ubuntu Touch: Fix Released Status in Dropping Letters: Invalid Status in Gallery App: In Progress Status in Media Player App: Fix Released Status in Messaging App: Fix Released Status in Music application for Ubuntu devices: Fix Released Status in Notes App: In Progress Status in Sudoku game for Ubuntu Touch: New Status in Calculator application for Ubuntu devices: Fix Released Status in Calendar application for Ubuntu devices: Fix Released Status in Clock application for Ubuntu devices: Fix Released Status in Ubuntu Clock App reboot series: In Progress Status in File Manager application for Ubuntu devices: Fix Committed Status in RSS Feed Reader application for Ubuntu devices: Fix Committed Status in Terminal application for Ubuntu devices: Fix Committed Status in Ubuntu Translations: Triaged Status in Weather application for Ubuntu devices: Fix Released Status in Web Browser App: Fix Released Status in “camera-app” package in Ubuntu: Fix Released Status in “dialer-app” package in Ubuntu: Fix Released Status in “messaging-app” package in Ubuntu: Fix Released Status in “ubuntu-system-settings” package in Ubuntu: Fix Released Status in “webbrowser-app” package in Ubuntu: Fix Released Bug description: As other apps cannot know where .mo files might be located for click packages, and unity8 apparently does not know about X-Ubuntu-Gettext- Domain for deb packages, the .desktop files for any applications will need to have their translations merged back into the .desktop file itself. This at a minimum should include the following .desktop fields: Name Comment Keywords (semicolon-separated list of strings) To manage notifications about this bug go to: https://bugs.launchpad.net/address-book-app/+bug/1318008/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1369644] Re: [enhancement] Should be possible to take a screen shot on the phone from the phone itself
I suggest some simple glReadPixels is sufficient :)
Mir's current screen{shot,cast} infrastructure is a bit complicated and
designed on the assumption that rendering everything twice is faster
than rendering everything once with a glReadPixels in the loop. I think
that assumption may yet be proven false. So a simple glReadPixels could
work (even from inside QtMir).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1369644
Title:
[enhancement] Should be possible to take a screen shot on the phone
from the phone itself
Status in Mir:
Opinion
Status in Qt integration with the Mir display server:
In Progress
Status in “mir” package in Ubuntu:
Opinion
Status in “unity8” package in Ubuntu:
New
Bug description:
Currently, the only way to take a screenshot is to attach the phone to
a computer via USB and use phablet-screenshot.
There should be a way to take a screenshot from the phone. Otherwise,
it will be hard for people to share how great their phone is on social
media, as well as other functions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1369644/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1370866] Re: Overly strict libmirplatform* dependencies are blocking CI
** Also affects: mir (Ubuntu) Importance: Undecided Status: New ** Changed in: mir (Ubuntu) Status: New => Triaged ** Changed in: mir (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1370866 Title: Overly strict libmirplatform* dependencies are blocking CI Status in Mir: Fix Committed Status in Mir 0.7 series: Fix Committed Status in “mir” package in Ubuntu: Triaged Bug description: Overly strict libmirplatform* dependencies are blocking CI. But fortunately we already landed a fix for this in 0.8. Just needs backporting to 0.7 ASAP... Starting pkgProblemResolver with broken count: 2 Starting 2 pkgProblemResolver with broken count: 2 Investigating (0) libmirplatformgraphics-android [ armhf ] < 0.7.2+14.10.20140912-0ubuntu1 > ( universe/libs ) Broken libmirplatformgraphics-android:armhf Depends on libmirplatform2 [ armhf ] < 0.7.2+14.10.20140912-0ubuntu1 -> 0.7.2+14.10.20140912bzr1917pkg0utopic713+autopilot0 > ( libs ) (= 0.7.2+14.10.20140912-0ubuntu1) Considering libmirplatform2:armhf 10006 as a solution to libmirplatformgraphics-android:armhf 1 Removing libmirplatformgraphics-android:armhf rather than change libmirplatform2:armhf Investigating (0) ubuntu-touch [ armhf ] < 1.185 > ( universe/metapackages ) Broken ubuntu-touch:armhf Depends on libmirplatformgraphics-android [ armhf ] < 0.7.2+14.10.20140912-0ubuntu1 > ( universe/libs ) Considering libmirplatformgraphics-android:armhf 1 as a solution to ubuntu-touch:armhf 0 Removing ubuntu-touch:armhf rather than change libmirplatformgraphics-android:armhf Investigating (0) libmirplatformgraphics-mesa [ armhf ] < 0.7.2+14.10.20140912-0ubuntu1 > ( libs ) Broken libmirplatformgraphics-mesa:armhf Depends on libmirplatform2 [ armhf ] < 0.7.2+14.10.20140912-0ubuntu1 -> 0.7.2+14.10.20140912bzr1917pkg0utopic713+autopilot0 > ( libs ) (= 0.7.2+14.10.20140912-0ubuntu1) Considering libmirplatform2:armhf 10006 as a solution to libmirplatformgraphics-mesa:armhf 0 Removing libmirplatformgraphics-mesa:armhf rather than change libmirplatform2:armhf Investigating (1) libmirserver25 [ armhf ] < 0.7.2+14.10.20140912-0ubuntu1 > ( libs ) Broken libmirserver25:armhf Depends on libmirplatformgraphics-mesa [ armhf ] < 0.7.2+14.10.20140912-0ubuntu1 > ( libs ) (= 0.7.2+14.10.20140912-0ubuntu1) Considering libmirplatformgraphics-mesa:armhf 0 as a solution to libmirserver25:armhf 3 Added libmirplatformgraphics-mesa:armhf to the remove list Broken libmirserver25:armhf Depends on libmirplatformgraphics-android [ armhf ] < 0.7.2+14.10.20140912-0ubuntu1 > ( universe/libs ) (= 0.7.2+14.10.20140912-0ubuntu1) Considering libmirplatformgraphics-android:armhf 1 as a solution to libmirserver25:armhf 3 Added libmirplatformgraphics-android:armhf to the remove list Fixing libmirserver25:armhf via keep of libmirplatformgraphics-mesa:armhf Fixing libmirserver25:armhf via keep of libmirplatformgraphics-android:armhf Investigating (1) libmirplatformgraphics-android [ armhf ] < 0.7.2+14.10.20140912-0ubuntu1 > ( universe/libs ) Broken libmirplatformgraphics-android:armhf Depends on libmirplatform2 [ armhf ] < 0.7.2+14.10.20140912-0ubuntu1 -> 0.7.2+14.10.20140912bzr1917pkg0utopic713+autopilot0 > ( libs ) (= 0.7.2+14.10.20140912-0ubuntu1) Considering libmirplatform2:armhf 10006 as a solution to libmirplatformgraphics-android:armhf 1 Removing libmirplatformgraphics-android:armhf rather than change libmirplatform2:armhf Investigating (1) libmirplatformgraphics-mesa [ armhf ] < 0.7.2+14.10.20140912-0ubuntu1 > ( libs ) Broken libmirplatformgraphics-mesa:armhf Depends on libmirplatform2 [ armhf ] < 0.7.2+14.10.20140912-0ubuntu1 -> 0.7.2+14.10.20140912bzr1917pkg0utopic713+autopilot0 > ( libs ) (= 0.7.2+14.10.20140912-0ubuntu1) Considering libmirplatform2:armhf 10006 as a solution to libmirplatformgraphics-mesa:armhf 0 Removing libmirplatformgraphics-mesa:armhf rather than change libmirplatform2:armhf Investigating (2) libmirserver25 [ armhf ] < 0.7.2+14.10.20140912-0ubuntu1 > ( libs ) Broken libmirserver25:armhf Depends on libmirplatformgraphics-mesa [ armhf ] < 0.7.2+14.10.20140912-0ubuntu1 > ( libs ) (= 0.7.2+14.10.20140912-0ubuntu1) Considering libmirplatformgraphics-mesa:armhf 0 as a solution to libmirserver25:armhf 3 Added libmirplatformgraphics-mesa:armhf to the remove list Broken libmirserver25:armhf Depends on libmirplatformgraphics-android [ armhf ] < 0.7.2+14.10.20140912-0ubuntu1 > ( universe/libs ) (= 0.7.2+14.10.20140912-0ubuntu1) Considering libmirplatformgraphics-android:armhf 1 as a solution to libmirserver25:armhf 3 Added libmirplatformgraphics-android:armhf to the remove list Fixing libmirserver25:armhf via keep of libmirplatformgraphics-mesa:
[Touch-packages] [Bug 1236508] Re: unity8+Mir draws more current and wakes up 100 times more often than unity8 with surfaceflinger
** Changed in: ubuntu-power-consumption Status: New => Incomplete -- 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/1236508 Title: unity8+Mir draws more current and wakes up 100 times more often than unity8 with surfaceflinger Status in Mir: Incomplete Status in The Ubuntu Power Consumption Project: Incomplete Status in Unity Mir: Incomplete Status in “unity8” package in Ubuntu: Incomplete Bug description: I've looked at the CPU, wakeup event and current drawn on a LG Nexus 4 comparing the Mir enabled and non-Mir versions of Unity8 with today's image + updates (at 18:00 UTC, 7th Oct 2013). I ran a 5 minute idle soak test with the screen set to be un-blanked at full brightness and measured the current drawn at 0.5 second intervals. The Mir enabled version of Unity is drawing on average ~143.7mA where as the non-Mir version is drawing 138.7mA, or around 5mA less current (~3.6% difference) Measuring CPU load (just Mir) Mir: 0.70% user,0.63% system, 1.33% total CPU usage Non-Mir: 0.17% user, 0.07% system, 0.23% total CPU usage Context Switches: Mir: 219.24 context switches/sec Non-Mir: 22.32 context switches/sec poll/epoll/nanosleeps Mir: 4.9664/sec Non-Mir: 3.1333/sec Total CPU of system: Mir: 0.87% Non-Mir: 0.70% So it seems that the Mir variant of Unity8 is busier and consumes more power than the non-Mir variety when idle. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1236508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1350006] Re: "Calling" screen is shown after answering a call
** Changed in: dialer-app Status: Confirmed => In Progress ** Changed in: dialer-app (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1350006 Title: "Calling" screen is shown after answering a call Status in Dialer app for Ubuntu Touch: In Progress Status in “dialer-app” package in Ubuntu: In Progress Bug description: build 157 Nexus 4 - make sure dialer is not running - call the Ubuntu phone - answer from the snap decision Expected result: - The live call screen should be shown Actual result: - After a long pause the "Calling" screen is shown and then it transitions to the live call screen To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1350006/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1350006] Re: "Calling" screen is shown after answering a call
** Branch linked: lp:~boiko/dialer-app/do_not_show_calling_screen -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1350006 Title: "Calling" screen is shown after answering a call Status in Dialer app for Ubuntu Touch: In Progress Status in “dialer-app” package in Ubuntu: In Progress Bug description: build 157 Nexus 4 - make sure dialer is not running - call the Ubuntu phone - answer from the snap decision Expected result: - The live call screen should be shown Actual result: - After a long pause the "Calling" screen is shown and then it transitions to the live call screen To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1350006/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1349309] Re: Require special menu type for settings menus
** Changed in: indicator-sound Assignee: (unassigned) => Charles Kerr (charlesk) ** Changed in: indicator-sound Importance: Undecided => Medium -- 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/1349309 Title: Require special menu type for settings menus Status in Bluetooth Menu: Triaged Status in The Date and Time Indicator: Triaged Status in Network Menu: Triaged Status in The Power Indicator: Triaged Status in Sound Menu: New Status in “unity8” package in Ubuntu: Confirmed Bug description: The settings menus should have a custom type so that we can specialize them in the UI. com.canonical.indicator.link Attached image to show what design want. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-bluetooth/+bug/1349309/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1353379] Re: VoiceMail notification pretends there are 255 messages. It is not true there are only 2
Also tested RTM #44 with krillin, and I get a different result yet again. This time the indicator just states "VoiceMail Messages" with no count. This is using a single T-Mobile pre-paid SIM in slot #1. ** Attachment added: "lp1353379-krillin.png" https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1353379/+attachment/4208250/+files/lp1353379-krillin.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/1353379 Title: VoiceMail notification pretends there are 255 messages. It is not true there are only 2 Status in “indicator-messages” package in Ubuntu: Invalid Status in “ofono” package in Ubuntu: Triaged Bug description: Mako build #175 The VoiceMail notification indicates there are 255 voice messages (cf screenshot) on voice mail while there were only 2 new messages. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: indicator-messages 13.10.1+14.10.20140725-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.5-0ubuntu3 Architecture: armhf Date: Wed Aug 6 11:57:43 2014 InstallationDate: Installed on 2014-08-06 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140806-020204) SourcePackage: indicator-messages UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1353379/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1353379] Re: VoiceMail notification pretends there are 255 messages. It is not true there are only 2
As I'd mentioned before, there are numerous methods of indicating voice- mail waiting message counts. It appears that some of these methods work, and some don't. It seems we have more investigation needed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/1353379 Title: VoiceMail notification pretends there are 255 messages. It is not true there are only 2 Status in “indicator-messages” package in Ubuntu: Invalid Status in “ofono” package in Ubuntu: Triaged Bug description: Mako build #175 The VoiceMail notification indicates there are 255 voice messages (cf screenshot) on voice mail while there were only 2 new messages. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: indicator-messages 13.10.1+14.10.20140725-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.5-0ubuntu3 Architecture: armhf Date: Wed Aug 6 11:57:43 2014 InstallationDate: Installed on 2014-08-06 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140806-020204) SourcePackage: indicator-messages UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1353379/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1353379] Re: VoiceMail notification pretends there are 255 messages. It is not true there are only 2
Just tested RTM #39 on mako with AT&T SIM. As screenshot shows, the indicator shows two waiting messages. ** Attachment added: "lp1353379-mako.png" https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1353379/+attachment/4208249/+files/lp1353379-mako.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/1353379 Title: VoiceMail notification pretends there are 255 messages. It is not true there are only 2 Status in “indicator-messages” package in Ubuntu: Invalid Status in “ofono” package in Ubuntu: Triaged Bug description: Mako build #175 The VoiceMail notification indicates there are 255 voice messages (cf screenshot) on voice mail while there were only 2 new messages. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: indicator-messages 13.10.1+14.10.20140725-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.5-0ubuntu3 Architecture: armhf Date: Wed Aug 6 11:57:43 2014 InstallationDate: Installed on 2014-08-06 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140806-020204) SourcePackage: indicator-messages UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1353379/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 965341] Re: watch command line utility crashes with segfault when processing binary output
** Changed in: procps (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/965341 Title: watch command line utility crashes with segfault when processing binary output Status in “procps” package in Ubuntu: Fix Released Status in “procps” package in Debian: Fix Released Bug description: Running the command: $ watch 'tail sample.dat' where sample.dat contains binary data, causes 'watch' to crash with segmentation fault. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: procps 1:3.2.8-10ubuntu5 ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20 Uname: Linux 3.0.0-16-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Mon Mar 26 11:22:09 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: procps UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/965341/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1280759] Re: Unity shortcuts (Super+A/F/M/C/V) do not work on non-latin layout in Trusty - shortcuts are defined via keyboard layout, not the keys
I experienced the following issue, I think It's related to the same bug. I have two keyboard layouts: English and Aabic (Azerty). I typed a text in the search box on Firefox then tried to select it with CTRL+A shortcut. With Arabic layout activated this had caused Firefox to close. In the other hand, when English layout is activated this had behaved normally (selecting all the text in the box). I switched back to Cinnamon because of this issue. User experience in Unity become very complicated when using a non latin layout with a latin one. -- 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/1280759 Title: Unity shortcuts (Super+A/F/M/C/V) do not work on non-latin layout in Trusty - shortcuts are defined via keyboard layout, not the keys Status in Unity: Triaged Status in Unity Settings Daemon: Confirmed Status in “unity” package in Ubuntu: Triaged Bug description: There are shortcuts to open lenses in Unity, for example "Super + A" for App Lens, or "Super + F" for Files Lens, etc. There are also shortcuts in the Launcher "Super + 1 to 9" to launch apps from the Launcher. These shortcuts don't work if the keyboard layout is set to a non-Latin layout, in my case Persian, where almost all the keys are mapped to new characters. HOW TO REPRODUCE: Add a new Persian keyboard layout to the system, in addition to English, via keyboard layout indicator --> Text Entry Settings. Switch to the Persian layout (by clicking on the keyboard layout indicator). Press "Super + F". WHAT HAPPENS: Dash is not open. Nothing happens. WHAT SHOULD HEPPEN: The Files Lens in the dash should open. The shortcuts should be associated with the keys on the keyboard, not to the characters they are associated with (which depends on the active keyboard layout). When I am typing something in Persian, and I want to search for a file, it is not reasonable that I should first switch back to the English layout before I can use a particular shortcut. This problem does not happen in some other apps like gedit or Firefox. COMPARE TO GEDIT: Open gedit text editor. Write something. Switch to the Persian layout. Press "Ctrl + S" (the shortcut to save the document). WHAT HAPPENS, AND WHAT SHOULD HAPPEN: The save dialoge box appears. I think this problem happens for all keyboard layouts that don't use Latin characters. Layout-wise, when I press "Ctrl + S" while Persian layout is active, I am typing "Ctrl + س". But keyboard-wise, I am always pressing the same keyboard binding. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libunity9 7.1.4+14.04.20140210-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 16 12:04:10 2014 InstallationDate: Installed on 2014-02-15 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140211) SourcePackage: libunity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1280759/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1339792] Re: Panel network icon - too much latency when network type changes
This bug was reported in July and never confirmed ( hence the New ), so someone should've tried to reproduce with a current image before marking it Critical for RTM. I just re-ran the original scenarios on RTM image #44. I can still reproduce the original problem, however the overall latency has come way down ( 10-15s max for state transition vs. almost a minute maximum before ). In scenario one, we should check the indicator's logic and see when the connect attempt is made to the newly selected network. It seems that a disconnect always happens when a network is selected, even when the user the clicks cancel. My guess is that this may have something to do with the NM agent prompting mechanism used to tell the indicator to collect a password. Anyways, again in scenario 1, I get a ~10s overlap of the icon showing 2G, and the network-menu showing the connected AP. After the 10s, the icon updates to the appropriate WiFi icon. My guess about the latency is that even though we may be connected, it takes awhile for NM to prepare the connection and maybe it notified the indicator that it's connected prior to the connection being fully setup??? I'm less concerned about scenario 2 as there's no conflicting icons / menu states, it just takes awhile to switch back to 2G. Maybe this could be marked High instead of Critical? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1339792 Title: Panel network icon - too much latency when network type changes Status in “indicator-network” package in Ubuntu: New Bug description: Testing image #u122 this morning, I ran into two separate scenarios where the panel network icon didn't always accurately reflect the current network technology due to some kind of latency detecting network changes ( ie. WiFi -> 3G -> WiFi ). Both scenarios were reproduced on mako. Scenario 1: 3G: online WiFi: enabled; connected to AP 1 - display network menu - tap another secure network - tap cancel when Password dialog is displayed At this point the indicator shows '3G' whereas the network menu still shows the original AP 1 as connected. After some period of time ( 10s - 1m ), the icon will change back to show that WiFi is connected. Scenario 2: 3G: online WiFi: connected to AP 1 - go to System Settings::WiFi - click "Previous Networks" - select the currently connected AP/network - click Forget Network - go back to WiFi settings The WiFi settings correctly shows the AP is no longer connected, however again the network icon takes some time ( 10s - 1m ) to reflect the change back to "3G". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1339792/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1339792] Re: Panel network icon - too much latency when network type changes
Here's a screen shot of the menu contradicting the icon. ** Attachment added: "lp1339793-kril-scenario-1.png" https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1339792/+attachment/4208142/+files/lp1339793-kril-scenario-1.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1339792 Title: Panel network icon - too much latency when network type changes Status in “indicator-network” package in Ubuntu: New Bug description: Testing image #u122 this morning, I ran into two separate scenarios where the panel network icon didn't always accurately reflect the current network technology due to some kind of latency detecting network changes ( ie. WiFi -> 3G -> WiFi ). Both scenarios were reproduced on mako. Scenario 1: 3G: online WiFi: enabled; connected to AP 1 - display network menu - tap another secure network - tap cancel when Password dialog is displayed At this point the indicator shows '3G' whereas the network menu still shows the original AP 1 as connected. After some period of time ( 10s - 1m ), the icon will change back to show that WiFi is connected. Scenario 2: 3G: online WiFi: connected to AP 1 - go to System Settings::WiFi - click "Previous Networks" - select the currently connected AP/network - click Forget Network - go back to WiFi settings The WiFi settings correctly shows the AP is no longer connected, however again the network icon takes some time ( 10s - 1m ) to reflect the change back to "3G". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1339792/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1354092] Re: Location service needs internationalization
** Changed in: location-service (Ubuntu) Status: Confirmed => In Progress ** Changed in: ubuntu-translations Status: Triaged => In Progress ** Branch linked: lp:~thomas-voss/location-service/fix-1354092 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1354092 Title: Location service needs internationalization Status in Ubuntu Translations: In Progress Status in “location-service” package in Ubuntu: In Progress Bug description: The location dialog is displayed untranslated. Test case. - Switch the phone to Spanish. - Open webbrowser-app. - Go to maps.google.com - Accept to use location in the app. - Dialog appears. Expected result. - The dialog should be displayed in Spanish. Actual result. - The dialog appears untranslated: "unconfined: An unconfined application wants to access your current location. Deny, Allow". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1354092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371344] [NEW] [Ubuntu Touch] Timezone defaults to UTC and does not change automatically in Nexus 5
Public bug reported: In Ubuntu Touch during first time setup, the timezone defaults to UTC. Even when the carrier network and internet is available, the timezone does not automatically change to the current timezone. I have to manually change the timezone. Funnily, the setting says it's set to Automatic. ** Affects: ubuntu-touch-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1371344 Title: [Ubuntu Touch] Timezone defaults to UTC and does not change automatically in Nexus 5 Status in “ubuntu-touch-meta” package in Ubuntu: New Bug description: In Ubuntu Touch during first time setup, the timezone defaults to UTC. Even when the carrier network and internet is available, the timezone does not automatically change to the current timezone. I have to manually change the timezone. Funnily, the setting says it's set to Automatic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1371344/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371347] [NEW] nouveau E[Xorg[966]] failed to idle channel 0xcccc0001
Public bug reported: After the fresh install, I properly saw the boot progress with the plymouth Xubuntu theme up to a step where the screen has no more the progress image but a odd screen content which doesn't represent anything (from my knowledges). Next, I could get a virtual console (tty1) after many attempts of key strokes (CTRL-ALT-F1). Each ~10-30 seconds I get a console message in this screen like : "nouveau E[Xorg[966]] failed to idle channel 0x0001 [Xorg[966]]" I achieved to log in and execute 'sudo initctl stop lightdm'. The 'ps axf' command showed that X was still running. I first tried the command "sudo kill 966" with no success. Then I executed the command "sudo kill -KILL 966". Finally, I decided to install the proprietary driver with the command "sudo apt-get install nvidia-current". I reboot and the problem disappeared. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Sep 19 00:45:06 2014 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1371347 Title: nouveau E[Xorg[966]] failed to idle channel 0x0001 Status in “xorg” package in Ubuntu: New Bug description: After the fresh install, I properly saw the boot progress with the plymouth Xubuntu theme up to a step where the screen has no more the progress image but a odd screen content which doesn't represent anything (from my knowledges). Next, I could get a virtual console (tty1) after many attempts of key strokes (CTRL-ALT-F1). Each ~10-30 seconds I get a console message in this screen like : "nouveau E[Xorg[966]] failed to idle channel 0x0001 [Xorg[966]]" I achieved to log in and execute 'sudo initctl stop lightdm'. The 'ps axf' command showed that X was still running. I first tried the command "sudo kill 966" with no success. Then I executed the command "sudo kill -KILL 966". Finally, I decided to install the proprietary driver with the command "sudo apt-get install nvidia-current". I reboot and the problem disappeared. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Sep 19 00:45:06 2014 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1371347/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371343] [NEW] keeps crashing
Public bug reported: its the first time ive used ubuntu and iam new to computers your help would help me no end ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Sep 19 00:02:00 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV710 [Radeon HD 4350/4550] [1002:954f] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:0354] InstallationDate: Installed on 2014-09-06 (12 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-35-generic root=/dev/mapper/ubuntu--gnome--vg-root ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.80 dmi.board.name: B75 Pro3-M 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.80:bd07/12/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB75Pro3-M: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. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Sep 18 23:37:10 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Keyboard KEYBOARD, id 8 inputMosart Wireless Mouse MOUSE, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.1 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1371343 Title: keeps crashing Status in “xorg” package in Ubuntu: New Bug description: its the first time ive used ubuntu and iam new to computers your help would help me no end ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Sep 19 00:02:00 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV710 [Radeon HD 4350/4550] [1002:954f] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:0354] InstallationDate: Installed on 2014-09-06 (12 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-35-generic root=/dev/mapper/ubuntu--gnome--vg-root ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.80 dmi.board.name: B75 Pro3-M 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 Fill
[Touch-packages] [Bug 1370215] Re: unity menu scrolls itself up from time to time
** Package changed: ubuntu => unity (Ubuntu) -- 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/1370215 Title: unity menu scrolls itself up from time to time Status in “unity” package in Ubuntu: New Bug description: I had big trouble to describe it, and the problem bothers me so much that guided by the motto "a picture is worth thousand words" I decided to record a video that shows it: https://www.youtube.com/watch?v=UkWYYbYu2FY In other words sometimes when I hover an icon, then menu instead of stopping on this icon scrolls itself up instead. Note that I do not have two monitors so my cursor does not go beyond the edge of the monitor. moreover, this happens only sometimes. Description: Ubuntu 14.04.1 LTS Release: 14.04 unity 7.2.2+14.04.20140714-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1370215/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1370215] [NEW] unity menu scrolls itself up from time to time
You have been subscribed to a public bug: I had big trouble to describe it, and the problem bothers me so much that guided by the motto "a picture is worth thousand words" I decided to record a video that shows it: https://www.youtube.com/watch?v=UkWYYbYu2FY In other words sometimes when I hover an icon, then menu instead of stopping on this icon scrolls itself up instead. Note that I do not have two monitors so my cursor does not go beyond the edge of the monitor. moreover, this happens only sometimes. Description:Ubuntu 14.04.1 LTS Release:14.04 unity 7.2.2+14.04.20140714-0ubuntu1.1 ** Affects: unity (Ubuntu) Importance: Undecided Status: New -- unity menu scrolls itself up from time to time https://bugs.launchpad.net/bugs/1370215 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity 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 1370189] Re: Previously functional SIM is reported as Unknown (instead of Locked)
@Jussi This has been reported on the ubuntu-phone mailing list recently too. I've seen it myself once during urfkill testing, however I was restarting lots of things, so it's not really a fair comparison. Note, if the enter-pin script works, then ofono is in a PIN-locked state. @Thomas If you manage to recreate this again, can you please grab the output from list-modems ( in /usr/share/ofono/scripts; run as root )? Also what device and image # were used? ** Tags added: rtm14 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1370189 Title: Previously functional SIM is reported as Unknown (instead of Locked) Status in “indicator-network” package in Ubuntu: New Bug description: Right after boot, a previously working, PIN-locked SIM is no longer working and reported as Unknown. Manually entering the PIN via ofono scripts solves the issue and things start working again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1370189/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371332] [NEW] No SIM card deteced for UBuntu Touch when dual booting with Android on Nexus 5
Public bug reported: When I dual boot from Android 4.4.4 to Ubuntu Touch latest RTM build #41, and with the Utopic builds, most of the times the SIM card is not detected. To enable SIM card, I have to Toggle the Aeroplane mode to get the SIM card working. There are certain times when this fails and I have to go to /usr/share/urfkill and set flight-mode to 0, then 1 and then back to 0 to get the SIM card working. I am using Nexus 5 with Multirom Manager for dual booting ** Affects: ubuntu-touch-meta (Ubuntu) Importance: Undecided Status: New ** Description changed: When I dual boot from Android 4.4.4 to Ubuntu Touch latest RTM build #41, and with the Utopic builds, most of the times the SIM card is not detected. To enable SIM card, I have to Toggle the Aeroplane mode to get the SIM card working. There are certain times when this fails and I have to go to /usr/share/urfkill and set flight-mode to 0, then 1 and then back to 0 to get the SIM card working. + + I am using Nexus 5 with Multirom Manager for dual booting -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1371332 Title: No SIM card deteced for UBuntu Touch when dual booting with Android on Nexus 5 Status in “ubuntu-touch-meta” package in Ubuntu: New Bug description: When I dual boot from Android 4.4.4 to Ubuntu Touch latest RTM build #41, and with the Utopic builds, most of the times the SIM card is not detected. To enable SIM card, I have to Toggle the Aeroplane mode to get the SIM card working. There are certain times when this fails and I have to go to /usr/share/urfkill and set flight-mode to 0, then 1 and then back to 0 to get the SIM card working. I am using Nexus 5 with Multirom Manager for dual booting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1371332/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1369644] Re: [enhancement] Should be possible to take a screen shot on the phone from the phone itself
I agree that it makes more sense to do it in the unity8 server. However, the screencast plumbing cannot be used as is as qtmir implements Compositor not DisplayBufferCompositor. The screenshots obtained would be recomposed using our default compositor which wouldn't match qtmir compositor output. Since the screenshotting will be done in unity8 shell on the server side, I think its easier to just implement the required functionality in qtmir (i.e. dumping it's display buffer) directly instead of trying to adapt the screencast plumbing. Adapting it would require qtmir to at least implement DisplayBufferCompositor and DisplayBufferCompositorFactory. ** Also affects: qtmir Importance: Undecided Status: New ** Changed in: qtmir Assignee: (unassigned) => Alberto Aguirre (albaguirre) ** Changed in: unity8 (Ubuntu) Assignee: (unassigned) => Alberto Aguirre (albaguirre) ** Changed in: qtmir Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1369644 Title: [enhancement] Should be possible to take a screen shot on the phone from the phone itself Status in Mir: Opinion Status in Qt integration with the Mir display server: In Progress Status in “mir” package in Ubuntu: Opinion Status in “unity8” package in Ubuntu: New Bug description: Currently, the only way to take a screenshot is to attach the phone to a computer via USB and use phablet-screenshot. There should be a way to take a screenshot from the phone. Otherwise, it will be hard for people to share how great their phone is on social media, as well as other functions. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1369644/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371310] Re: docker.io doesn't work with 3.0 RC1 kernel
** Changed in: apparmor (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1371310 Title: docker.io doesn't work with 3.0 RC1 kernel Status in “apparmor” package in Ubuntu: New Status in “docker.io” package in Ubuntu: New Status in “linux” package in Ubuntu: Confirmed Bug description: Steps to reproduce (from https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor): 1. sudo apt-get install docker.io # 1.2.0~dfsg1-1 2. sudo docker pull ubuntu:trusty 3. sudo docker run ubuntu:trusty uptime 2014/09/18 15:48:48 Error response from daemon: Cannot start container fcdfaaf7945bcd9455fb5e0bde9950451152af14556880033818df7b50ddb1f4: set apparmor profile docker-default: permission denied What is expected? uptime to return something like: $ sudo docker run ubuntu:trusty uptime 20:31:21 up 1 min, 0 users, load average: 0.09, 0.06, 0.03 I set 'sudo sysctl -w kernel.printk_ratelimit=0' but there is nothing apparmor related in the logs. If I boot an earlier kernel without the 3.0 RC1 patches, it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1371310/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1360593] Re: unity8 freezes randomly
re-assigned to kgunn as saviq is on holiday. ** Changed in: unity8 (Ubuntu) Assignee: Michał Sawicz (saviq) => kevin gunn (kgunn72) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1360593 Title: unity8 freezes randomly Status in “unity8” package in Ubuntu: Confirmed Bug description: krillin #205 [Sorry for the poor description] On krillin UI freeze randomly. For example on the screenshot it occurred while dragging the greeter to unlock the phone. I was playing music, woke up the phone with the power button to turn the display on and did a right edge swipe to remove the greeter. This has been reported by several people in the past days, but I didn't find a pattern to reproduce this bug reliably. There is no crash in /var/crash and no apport activity. If I press the power button to turn the screen off/on again, the greeter is completely displayed (ie. doesn't cover half of the screen like the screenshot) but the UI is not responsive to gestures or input events. A long press on the power button shows the shutdown dialog but none of the button can be pressed. top doesn't show any specific process going crazy ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 8.00+14.10.20140822-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.6-0ubuntu2 Architecture: armhf Date: Sat Aug 23 14:18:00 2014 InstallationDate: Installed on 2014-08-23 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140823-020205) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1360593/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371320] Re: Network Indicator crashes and doesn't restart
This is probably the same bug as https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1343341 We'll leave this bug open for verification after the fix for 1343341 lands in the rtm image -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1371320 Title: Network Indicator crashes and doesn't restart Status in “indicator-network” package in Ubuntu: New Bug description: Device/Image: krillin / rtm #44; writable image, test version of urfkill w/hybris Wi-Fi mode enabled. While testing the new version of urfkill on krillin, I tried to reproduce bug #1339794 ( toggling Flight-Mode too fast leads to bad things ). Every so often the menu would flash, which meant the indicator crashed, and it would be re-started as expected. After doing this for awhile longer, the indicator crashed, and wasn't automatically restarted. I'll attach a screen shot which shows that the menu just reads "Empty!", and the output of 'ps -ale' ( run as root ) shows no indicator-network process running: root@ubuntu-phablet:/home/phablet# ps -ale | grep indica 0 S 32011 3102 1819 0 80 0 - 13749 poll_s ?00:00:00 indicator-trans 0 S 32011 3103 1819 0 80 0 - 11656 poll_s ?00:00:00 indicator-messa 0 S 32011 3104 1819 0 80 0 - 9357 poll_s ?00:00:00 indicator-bluet 0 S 32011 3106 1819 0 80 0 - 17391 poll_s ?00:00:00 indicator-locat 0 S 32011 3107 1819 0 80 0 - 9388 poll_s ?00:00:46 indicator-power 0 S 32011 3113 1819 0 80 0 - 33843 poll_s ?00:00:00 indicator-datet 0 S 32011 3117 1819 0 80 0 - 29521 poll_s ?00:00:00 indicator-sound There is an uploaded indicator-network crash file in /var/crash, however it looks like it's from yesterday. I reviewed the syslog, but it looks like it's been size limited so there aren't any upstart messages I can see. Are you relying on upstart to re-start the indicator when it dies? If you are, you could be hitting upstart's respawn limit. Note, I had the screen pinned on via 'powerd-cli screen on', but I don't think this would have any effect on the indicator's failure to respawn. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1371320/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1363929] Re: Flight mode indicator and network bars are seen onscreen simultaneously
** Changed in: ofono (Ubuntu) Status: Incomplete => Invalid ** Changed in: urfkill (Ubuntu) Status: Incomplete => In Progress ** Changed in: urfkill (Ubuntu) Importance: Undecided => High ** Changed in: urfkill (Ubuntu) Assignee: (unassigned) => Tony Espy (awe) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1363929 Title: Flight mode indicator and network bars are seen onscreen simultaneously Status in “indicator-network” package in Ubuntu: Invalid Status in “ofono” package in Ubuntu: Invalid Status in “urfkill” package in Ubuntu: In Progress Bug description: USED IMAGE: current build number: 7 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2014-08-26 04:03:20 version version: 7 version ubuntu: 20140826 version device: 20140811.1 TEST STEPS: -Enable flight mode from Network Indicator EXPEXTED RESULT: -Network bars disappear first and flight mode indicator appears after that ACTUAL RESULT: -Flight mode indicator appears before network bars disappear. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1363929/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371310] Re: docker.io doesn't work with 3.0 RC1 kernel
Adding the following to /etc/apparmor.d/docker does not help: audit unix, audit signal, audit ptrace, change_profile -> *, -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1371310 Title: docker.io doesn't work with 3.0 RC1 kernel Status in “apparmor” package in Ubuntu: New Status in “docker.io” package in Ubuntu: New Status in “linux” package in Ubuntu: Confirmed Bug description: Steps to reproduce (from https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor): 1. sudo apt-get install docker.io # 1.2.0~dfsg1-1 2. sudo docker pull ubuntu:trusty 3. sudo docker run ubuntu:trusty uptime 2014/09/18 15:48:48 Error response from daemon: Cannot start container fcdfaaf7945bcd9455fb5e0bde9950451152af14556880033818df7b50ddb1f4: set apparmor profile docker-default: permission denied What is expected? uptime to return something like: $ sudo docker run ubuntu:trusty uptime 20:31:21 up 1 min, 0 users, load average: 0.09, 0.06, 0.03 I set 'sudo sysctl -w kernel.printk_ratelimit=0' but there is nothing apparmor related in the logs. If I boot an earlier kernel without the 3.0 RC1 patches, it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1371310/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371310] Re: docker.io doesn't work with 3.0 RC1 kernel
The target profile is loaded: $ sudo aa-status|grep docker docker-default I tried this on the 3.16.0-9.14 and 3.16.0-16.22 distro kernels. The 'docker run' command succeeds. If I do this: $ sudo docker run -i -t ubuntu:trusty /bin/sh I can verify the container is launched under confinement here: sudo aa-status|grep docker docker-default docker-default (2209) $ ps -Z 2209 LABEL PID TTY STAT TIME COMMAND docker-default 2209 pts/1Ss+0:00 /bin/sh -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1371310 Title: docker.io doesn't work with 3.0 RC1 kernel Status in “apparmor” package in Ubuntu: New Status in “docker.io” package in Ubuntu: New Status in “linux” package in Ubuntu: Confirmed Bug description: Steps to reproduce (from https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor): 1. sudo apt-get install docker.io # 1.2.0~dfsg1-1 2. sudo docker pull ubuntu:trusty 3. sudo docker run ubuntu:trusty uptime 2014/09/18 15:48:48 Error response from daemon: Cannot start container fcdfaaf7945bcd9455fb5e0bde9950451152af14556880033818df7b50ddb1f4: set apparmor profile docker-default: permission denied What is expected? uptime to return something like: $ sudo docker run ubuntu:trusty uptime 20:31:21 up 1 min, 0 users, load average: 0.09, 0.06, 0.03 I set 'sudo sysctl -w kernel.printk_ratelimit=0' but there is nothing apparmor related in the logs. If I boot an earlier kernel without the 3.0 RC1 patches, it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1371310/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371310] Re: docker.io doesn't work with 3.0 RC1 kernel
Installing auditd does not help. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1371310 Title: docker.io doesn't work with 3.0 RC1 kernel Status in “apparmor” package in Ubuntu: New Status in “docker.io” package in Ubuntu: New Status in “linux” package in Ubuntu: Confirmed Bug description: Steps to reproduce (from https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor): 1. sudo apt-get install docker.io # 1.2.0~dfsg1-1 2. sudo docker pull ubuntu:trusty 3. sudo docker run ubuntu:trusty uptime 2014/09/18 15:48:48 Error response from daemon: Cannot start container fcdfaaf7945bcd9455fb5e0bde9950451152af14556880033818df7b50ddb1f4: set apparmor profile docker-default: permission denied What is expected? uptime to return something like: $ sudo docker run ubuntu:trusty uptime 20:31:21 up 1 min, 0 users, load average: 0.09, 0.06, 0.03 I set 'sudo sysctl -w kernel.printk_ratelimit=0' but there is nothing apparmor related in the logs. If I boot an earlier kernel without the 3.0 RC1 patches, it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1371310/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371320] Re: Network Indicator crashes and doesn't restart
Here's a screenshot of the "Empty!" menu. ** Attachment added: "ind-net-no-menu.png" https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1371320/+attachment/4208065/+files/ind-net-no-menu.png ** Description changed: Device/Image: krillin / rtm #44; writable image, test version of urfkill w/hybris Wi-Fi mode enabled. While testing the new version of urfkill on krillin, I tried to reproduce bug #1339794 ( toggling Flight-Mode too fast leads to bad things ). Every so often the menu would flash, which meant the indicator crashed, and it would be re-started as expected. After doing this for awhile longer, the indicator crashed, and wasn't automatically restarted. I'll attach a screen shot which shows that the menu just reads "Empty!", and the output of 'ps -ale' ( run as root ) shows no indicator-network process running: root@ubuntu-phablet:/home/phablet# ps -ale | grep indica 0 S 32011 3102 1819 0 80 0 - 13749 poll_s ?00:00:00 indicator-trans 0 S 32011 3103 1819 0 80 0 - 11656 poll_s ?00:00:00 indicator-messa 0 S 32011 3104 1819 0 80 0 - 9357 poll_s ?00:00:00 indicator-bluet 0 S 32011 3106 1819 0 80 0 - 17391 poll_s ?00:00:00 indicator-locat 0 S 32011 3107 1819 0 80 0 - 9388 poll_s ?00:00:46 indicator-power 0 S 32011 3113 1819 0 80 0 - 33843 poll_s ?00:00:00 indicator-datet 0 S 32011 3117 1819 0 80 0 - 29521 poll_s ?00:00:00 indicator-sound There is an uploaded indicator-network crash file in /var/crash, however it looks like it's from yesterday. I reviewed the syslog, but it looks like it's been size limited so there aren't any upstart messages I can see. Are you relying on upstart to re-start the indicator when it dies? If you are, you could be hitting upstart's respawn limit. + + Note, I had the screen pinned on via 'powerd-cli screen on', but I don't + think this would have any effect on the indicator's failure to respawn. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1371320 Title: Network Indicator crashes and doesn't restart Status in “indicator-network” package in Ubuntu: New Bug description: Device/Image: krillin / rtm #44; writable image, test version of urfkill w/hybris Wi-Fi mode enabled. While testing the new version of urfkill on krillin, I tried to reproduce bug #1339794 ( toggling Flight-Mode too fast leads to bad things ). Every so often the menu would flash, which meant the indicator crashed, and it would be re-started as expected. After doing this for awhile longer, the indicator crashed, and wasn't automatically restarted. I'll attach a screen shot which shows that the menu just reads "Empty!", and the output of 'ps -ale' ( run as root ) shows no indicator-network process running: root@ubuntu-phablet:/home/phablet# ps -ale | grep indica 0 S 32011 3102 1819 0 80 0 - 13749 poll_s ?00:00:00 indicator-trans 0 S 32011 3103 1819 0 80 0 - 11656 poll_s ?00:00:00 indicator-messa 0 S 32011 3104 1819 0 80 0 - 9357 poll_s ?00:00:00 indicator-bluet 0 S 32011 3106 1819 0 80 0 - 17391 poll_s ?00:00:00 indicator-locat 0 S 32011 3107 1819 0 80 0 - 9388 poll_s ?00:00:46 indicator-power 0 S 32011 3113 1819 0 80 0 - 33843 poll_s ?00:00:00 indicator-datet 0 S 32011 3117 1819 0 80 0 - 29521 poll_s ?00:00:00 indicator-sound There is an uploaded indicator-network crash file in /var/crash, however it looks like it's from yesterday. I reviewed the syslog, but it looks like it's been size limited so there aren't any upstart messages I can see. Are you relying on upstart to re-start the indicator when it dies? If you are, you could be hitting upstart's respawn limit. Note, I had the screen pinned on via 'powerd-cli screen on', but I don't think this would have any effect on the indicator's failure to respawn. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1371320/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371320] Re: Network Indicator crashes and doesn't restart
Here's the upstart indicator-network.log. ** Attachment added: "indicator-network.log" https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1371320/+attachment/4208066/+files/indicator-network.log ** Tags added: rtm14 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1371320 Title: Network Indicator crashes and doesn't restart Status in “indicator-network” package in Ubuntu: New Bug description: Device/Image: krillin / rtm #44; writable image, test version of urfkill w/hybris Wi-Fi mode enabled. While testing the new version of urfkill on krillin, I tried to reproduce bug #1339794 ( toggling Flight-Mode too fast leads to bad things ). Every so often the menu would flash, which meant the indicator crashed, and it would be re-started as expected. After doing this for awhile longer, the indicator crashed, and wasn't automatically restarted. I'll attach a screen shot which shows that the menu just reads "Empty!", and the output of 'ps -ale' ( run as root ) shows no indicator-network process running: root@ubuntu-phablet:/home/phablet# ps -ale | grep indica 0 S 32011 3102 1819 0 80 0 - 13749 poll_s ?00:00:00 indicator-trans 0 S 32011 3103 1819 0 80 0 - 11656 poll_s ?00:00:00 indicator-messa 0 S 32011 3104 1819 0 80 0 - 9357 poll_s ?00:00:00 indicator-bluet 0 S 32011 3106 1819 0 80 0 - 17391 poll_s ?00:00:00 indicator-locat 0 S 32011 3107 1819 0 80 0 - 9388 poll_s ?00:00:46 indicator-power 0 S 32011 3113 1819 0 80 0 - 33843 poll_s ?00:00:00 indicator-datet 0 S 32011 3117 1819 0 80 0 - 29521 poll_s ?00:00:00 indicator-sound There is an uploaded indicator-network crash file in /var/crash, however it looks like it's from yesterday. I reviewed the syslog, but it looks like it's been size limited so there aren't any upstart messages I can see. Are you relying on upstart to re-start the indicator when it dies? If you are, you could be hitting upstart's respawn limit. Note, I had the screen pinned on via 'powerd-cli screen on', but I don't think this would have any effect on the indicator's failure to respawn. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1371320/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371320] [NEW] Network Indicator crashes and doesn't restart
Public bug reported: Device/Image: krillin / rtm #44; writable image, test version of urfkill w/hybris Wi-Fi mode enabled. While testing the new version of urfkill on krillin, I tried to reproduce bug #1339794 ( toggling Flight-Mode too fast leads to bad things ). Every so often the menu would flash, which meant the indicator crashed, and it would be re-started as expected. After doing this for awhile longer, the indicator crashed, and wasn't automatically restarted. I'll attach a screen shot which shows that the menu just reads "Empty!", and the output of 'ps -ale' ( run as root ) shows no indicator-network process running: root@ubuntu-phablet:/home/phablet# ps -ale | grep indica 0 S 32011 3102 1819 0 80 0 - 13749 poll_s ?00:00:00 indicator-trans 0 S 32011 3103 1819 0 80 0 - 11656 poll_s ?00:00:00 indicator-messa 0 S 32011 3104 1819 0 80 0 - 9357 poll_s ?00:00:00 indicator-bluet 0 S 32011 3106 1819 0 80 0 - 17391 poll_s ?00:00:00 indicator-locat 0 S 32011 3107 1819 0 80 0 - 9388 poll_s ?00:00:46 indicator-power 0 S 32011 3113 1819 0 80 0 - 33843 poll_s ?00:00:00 indicator-datet 0 S 32011 3117 1819 0 80 0 - 29521 poll_s ?00:00:00 indicator-sound There is an uploaded indicator-network crash file in /var/crash, however it looks like it's from yesterday. I reviewed the syslog, but it looks like it's been size limited so there aren't any upstart messages I can see. Are you relying on upstart to re-start the indicator when it dies? If you are, you could be hitting upstart's respawn limit. Note, I had the screen pinned on via 'powerd-cli screen on', but I don't think this would have any effect on the indicator's failure to respawn. ** Affects: indicator-network (Ubuntu) Importance: Critical Assignee: Antti Kaijanmäki (kaijanmaki) Status: New ** Tags: rtm14 ** Changed in: indicator-network (Ubuntu) Importance: Undecided => Critical ** Changed in: indicator-network (Ubuntu) Assignee: (unassigned) => Antti Kaijanmäki (kaijanmaki) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1371320 Title: Network Indicator crashes and doesn't restart Status in “indicator-network” package in Ubuntu: New Bug description: Device/Image: krillin / rtm #44; writable image, test version of urfkill w/hybris Wi-Fi mode enabled. While testing the new version of urfkill on krillin, I tried to reproduce bug #1339794 ( toggling Flight-Mode too fast leads to bad things ). Every so often the menu would flash, which meant the indicator crashed, and it would be re-started as expected. After doing this for awhile longer, the indicator crashed, and wasn't automatically restarted. I'll attach a screen shot which shows that the menu just reads "Empty!", and the output of 'ps -ale' ( run as root ) shows no indicator-network process running: root@ubuntu-phablet:/home/phablet# ps -ale | grep indica 0 S 32011 3102 1819 0 80 0 - 13749 poll_s ?00:00:00 indicator-trans 0 S 32011 3103 1819 0 80 0 - 11656 poll_s ?00:00:00 indicator-messa 0 S 32011 3104 1819 0 80 0 - 9357 poll_s ?00:00:00 indicator-bluet 0 S 32011 3106 1819 0 80 0 - 17391 poll_s ?00:00:00 indicator-locat 0 S 32011 3107 1819 0 80 0 - 9388 poll_s ?00:00:46 indicator-power 0 S 32011 3113 1819 0 80 0 - 33843 poll_s ?00:00:00 indicator-datet 0 S 32011 3117 1819 0 80 0 - 29521 poll_s ?00:00:00 indicator-sound There is an uploaded indicator-network crash file in /var/crash, however it looks like it's from yesterday. I reviewed the syslog, but it looks like it's been size limited so there aren't any upstart messages I can see. Are you relying on upstart to re-start the indicator when it dies? If you are, you could be hitting upstart's respawn limit. Note, I had the screen pinned on via 'powerd-cli screen on', but I don't think this would have any effect on the indicator's failure to respawn. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1371320/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1318008] Re: Core apps .desktop files do not include translated strings
** Changed in: mediaplayer-app Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1318008 Title: Core apps .desktop files do not include translated strings Status in Address Book App: Fix Released Status in Camera App: Fix Released Status in Dialer app for Ubuntu Touch: Fix Released Status in Dropping Letters: Invalid Status in Gallery App: In Progress Status in Media Player App: Fix Released Status in Messaging App: Fix Released Status in Music application for Ubuntu devices: Fix Released Status in Notes App: In Progress Status in Sudoku game for Ubuntu Touch: New Status in Calculator application for Ubuntu devices: Fix Released Status in Calendar application for Ubuntu devices: Fix Released Status in Clock application for Ubuntu devices: Fix Released Status in Ubuntu Clock App reboot series: In Progress Status in File Manager application for Ubuntu devices: Fix Committed Status in RSS Feed Reader application for Ubuntu devices: In Progress Status in Terminal application for Ubuntu devices: Fix Committed Status in Ubuntu Translations: Triaged Status in Weather application for Ubuntu devices: Fix Released Status in Web Browser App: Fix Released Status in “camera-app” package in Ubuntu: Fix Released Status in “dialer-app” package in Ubuntu: Fix Released Status in “messaging-app” package in Ubuntu: Fix Released Status in “ubuntu-system-settings” package in Ubuntu: Fix Released Status in “webbrowser-app” package in Ubuntu: Fix Released Bug description: As other apps cannot know where .mo files might be located for click packages, and unity8 apparently does not know about X-Ubuntu-Gettext- Domain for deb packages, the .desktop files for any applications will need to have their translations merged back into the .desktop file itself. This at a minimum should include the following .desktop fields: Name Comment Keywords (semicolon-separated list of strings) To manage notifications about this bug go to: https://bugs.launchpad.net/address-book-app/+bug/1318008/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1362199] Re: [FFe] apparmor abstract, anonymous and netlink socket mediation
** Also affects: linux-mako (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-goldfish (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-flo (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-manta (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-mako (Ubuntu) Importance: Undecided => High ** Changed in: linux-mako (Ubuntu) Status: New => In Progress ** Changed in: linux-mako (Ubuntu) Importance: High => Critical ** Changed in: linux-goldfish (Ubuntu) Importance: Undecided => High ** Changed in: linux-goldfish (Ubuntu) Status: New => In Progress ** Changed in: linux-manta (Ubuntu) Importance: Undecided => High ** Changed in: linux-manta (Ubuntu) Status: New => In Progress ** Changed in: linux-flo (Ubuntu) Importance: Undecided => High ** Changed in: linux-flo (Ubuntu) Status: New => In Progress ** Changed in: linux-mako (Ubuntu) Importance: Critical => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1362199 Title: [FFe] apparmor abstract, anonymous and netlink socket mediation Status in “apparmor” package in Ubuntu: Fix Released Status in “apparmor-easyprof-ubuntu” package in Ubuntu: Fix Released Status in “isc-dhcp” package in Ubuntu: Fix Released Status in “libvirt” package in Ubuntu: Fix Released Status in “lightdm” package in Ubuntu: Fix Released Status in “linux” package in Ubuntu: In Progress Status in “linux-flo” package in Ubuntu: In Progress Status in “linux-goldfish” package in Ubuntu: In Progress Status in “linux-mako” package in Ubuntu: In Progress Status in “linux-manta” package in Ubuntu: In Progress Status in “rsyslog” package in Ubuntu: Fix Released Status in “tlsdate” package in Ubuntu: Fix Released Bug description: Background: kernel and apparmor userspace updates to support abstract, anonymous and fine-grained netlink socket mediation. These packages are listed in one bug because they are related, but the FFes may be granted and the uploads may happen at different times. = apparmor userspace = Summary: This feature freeze exception is requested for abstract, anonymous and fine-grained netlink socket for apparmor userspace. When used with a compatible kernel, 'unix' and 'network netlink' rules are supported. When used without a compatible apparmor userspace (eg, on a trusty system with an utopic backport kernel), abstract, anonymous and fine-grained netlink socket mediation is not enforced (ie, you can use this userspace with an old kernel without any issues). Testing: * 14.10 system with current kernels lacking abstract, anonymous and fine-grained netlink socket mediation (non-Touch): * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: DONE (exploratory manual testing, lxc, libvirt, etc) * 14.10 system kernel capable of supporting abstract, anonymous and fine-grained netlink socket mediation (non-Touch): * https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor: INPROGRESS (includes test-apparmor.py, exploratory manual testing, lxc, libvirt, etc) * Verify everything in https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/AppArmorProfiles: DONE (except juju since it doesn't have policy itself) Justification: This feature is required to support comprehensive application confinement on Ubuntu Touch. This feature adds a security benefit to libvirt's qemu guest isolation which is fundamental to Ubuntu on Server/Cloud. This feature also adds a welcome improvement to administrators wishing to further protect their systems. Extra information: While the apparmor userspace and kernel changes to support abstract, anonymous and fine-grained netlink socket can happen at different times, the apparmor userspace upload must correspond with uploads for packages that ship AppArmor policy that require updates (eg, libvirt, lightdm, etc). The packages outlined in https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/AppArmorProfiles have been tested to either work without modification to the policy or updated and tested to work with updated policy. Common rules will be added to the apparmor base abstraction such that most packages shipping apparmor policy will not require updating. These updates will be prepared, tested and published en masse via a silo ppa. = linux = Summary: This feature freeze exception is requested for abstract, anonymous and fine-grained netlink socket via apparmor in the kernel. When used with a compatible apparmor userspace, 'unix' and 'network netlink' rules are supported. When used without a compatible apparmor userspace (eg, on a trusty system with an utopic backport kernel), abstract, anonymous and fine-grained netlink socket mediation is not enforced (ie, you can use this kernel with
[Touch-packages] [Bug 1360593] Re: unity8 freezes randomly
** Changed in: unity8 (Ubuntu) Assignee: (unassigned) => Michał Sawicz (saviq) -- 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/1360593 Title: unity8 freezes randomly Status in “unity8” package in Ubuntu: Confirmed Bug description: krillin #205 [Sorry for the poor description] On krillin UI freeze randomly. For example on the screenshot it occurred while dragging the greeter to unlock the phone. I was playing music, woke up the phone with the power button to turn the display on and did a right edge swipe to remove the greeter. This has been reported by several people in the past days, but I didn't find a pattern to reproduce this bug reliably. There is no crash in /var/crash and no apport activity. If I press the power button to turn the screen off/on again, the greeter is completely displayed (ie. doesn't cover half of the screen like the screenshot) but the UI is not responsive to gestures or input events. A long press on the power button shows the shutdown dialog but none of the button can be pressed. top doesn't show any specific process going crazy ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 8.00+14.10.20140822-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.6-0ubuntu2 Architecture: armhf Date: Sat Aug 23 14:18:00 2014 InstallationDate: Installed on 2014-08-23 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140823-020205) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1360593/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
** Branch linked: lp:ubuntu/precise-proposed/udev -- 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/1367241 Title: Incorrect udev-fallback-graphics.conf Status in “systemd” package in Ubuntu: Fix Committed Status in “udev” package in Ubuntu: Invalid Status in “udev” source package in Precise: Fix Committed Status in “systemd” source package in Trusty: Fix Committed Status in “systemd” source package in Utopic: Fix Committed Bug description: [Impact] * When setting up primary display driver fails an attempt to load vesafb module is undertaken. This fails since from 3.13.0-16.36 version vesafb is compiled in the kernel (so no actual modprobing is needed). This causes false alert in the log: "Starting load fallback graphic devices: [fail]" [Test Case] * Start Ubuntu unable to load primary graphics driver (the simplest way is to remove module responsible for the device). * Wait for loading graphics devices. * If the primary device module has failed to load, falling back to vesafb will be attempted. [Regression Potential] * Implemented by the bug reported. * Affects only the debian/ directory. [Other Info] * Original bug description: The udev-fallback-graphics.conf script tries to load vesafb module if PRIMARY_DEVICE_FOR_DISPLAY has not been set earlier. The problem is that from kernel version 3.13.0-16.36 vesafb is compiled in permanently into the kernel (CONFIG_FB_VESA=y), so whenever the fallback mode is triggered this script will FAIL confusing the users. Most probably this file is no longer needed (or it just be used to print informative message). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1367241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1360593] Re: unity8 freezes randomly
** Attachment added: "unity8.log" https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1360593/+attachment/4208054/+files/unity8.log -- 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/1360593 Title: unity8 freezes randomly Status in “unity8” package in Ubuntu: Confirmed Bug description: krillin #205 [Sorry for the poor description] On krillin UI freeze randomly. For example on the screenshot it occurred while dragging the greeter to unlock the phone. I was playing music, woke up the phone with the power button to turn the display on and did a right edge swipe to remove the greeter. This has been reported by several people in the past days, but I didn't find a pattern to reproduce this bug reliably. There is no crash in /var/crash and no apport activity. If I press the power button to turn the screen off/on again, the greeter is completely displayed (ie. doesn't cover half of the screen like the screenshot) but the UI is not responsive to gestures or input events. A long press on the power button shows the shutdown dialog but none of the button can be pressed. top doesn't show any specific process going crazy ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 8.00+14.10.20140822-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.6-0ubuntu2 Architecture: armhf Date: Sat Aug 23 14:18:00 2014 InstallationDate: Installed on 2014-08-23 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140823-020205) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1360593/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1360593] Re: unity8 freezes randomly
there are no crash files. -- 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/1360593 Title: unity8 freezes randomly Status in “unity8” package in Ubuntu: Confirmed Bug description: krillin #205 [Sorry for the poor description] On krillin UI freeze randomly. For example on the screenshot it occurred while dragging the greeter to unlock the phone. I was playing music, woke up the phone with the power button to turn the display on and did a right edge swipe to remove the greeter. This has been reported by several people in the past days, but I didn't find a pattern to reproduce this bug reliably. There is no crash in /var/crash and no apport activity. If I press the power button to turn the screen off/on again, the greeter is completely displayed (ie. doesn't cover half of the screen like the screenshot) but the UI is not responsive to gestures or input events. A long press on the power button shows the shutdown dialog but none of the button can be pressed. top doesn't show any specific process going crazy ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 8.00+14.10.20140822-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.6-0ubuntu2 Architecture: armhf Date: Sat Aug 23 14:18:00 2014 InstallationDate: Installed on 2014-08-23 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140823-020205) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1360593/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1360593] Re: unity8 freezes randomly
** Attachment added: "unity8-dash.log" https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1360593/+attachment/4208055/+files/unity8-dash.log -- 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/1360593 Title: unity8 freezes randomly Status in “unity8” package in Ubuntu: Confirmed Bug description: krillin #205 [Sorry for the poor description] On krillin UI freeze randomly. For example on the screenshot it occurred while dragging the greeter to unlock the phone. I was playing music, woke up the phone with the power button to turn the display on and did a right edge swipe to remove the greeter. This has been reported by several people in the past days, but I didn't find a pattern to reproduce this bug reliably. There is no crash in /var/crash and no apport activity. If I press the power button to turn the screen off/on again, the greeter is completely displayed (ie. doesn't cover half of the screen like the screenshot) but the UI is not responsive to gestures or input events. A long press on the power button shows the shutdown dialog but none of the button can be pressed. top doesn't show any specific process going crazy ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 8.00+14.10.20140822-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.6-0ubuntu2 Architecture: armhf Date: Sat Aug 23 14:18:00 2014 InstallationDate: Installed on 2014-08-23 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140823-020205) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1360593/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1360593] Re: unity8 freezes randomly
** Attachment added: "gdb.txt" https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1360593/+attachment/4208053/+files/gdb.txt -- 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/1360593 Title: unity8 freezes randomly Status in “unity8” package in Ubuntu: Confirmed Bug description: krillin #205 [Sorry for the poor description] On krillin UI freeze randomly. For example on the screenshot it occurred while dragging the greeter to unlock the phone. I was playing music, woke up the phone with the power button to turn the display on and did a right edge swipe to remove the greeter. This has been reported by several people in the past days, but I didn't find a pattern to reproduce this bug reliably. There is no crash in /var/crash and no apport activity. If I press the power button to turn the screen off/on again, the greeter is completely displayed (ie. doesn't cover half of the screen like the screenshot) but the UI is not responsive to gestures or input events. A long press on the power button shows the shutdown dialog but none of the button can be pressed. top doesn't show any specific process going crazy ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 8.00+14.10.20140822-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.6-0ubuntu2 Architecture: armhf Date: Sat Aug 23 14:18:00 2014 InstallationDate: Installed on 2014-08-23 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140823-020205) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1360593/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1360593] Re: unity8 freezes randomly
I had this happen again on image 44 phablet@ubuntu-phablet:~$ cat /etc/system-image/channel.ini [service] base: system-image.ubuntu.com http_port: 80 https_port: 443 channel: ubuntu-touch/ubuntu-rtm/14.09-proposed device: krillin build_number: 44 version_detail: ubuntu=20140916,device=20140912-23825b8,custom=1410739265,version=44 This time the cpu was not being pegged qmlscene or anything else. -- 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/1360593 Title: unity8 freezes randomly Status in “unity8” package in Ubuntu: Confirmed Bug description: krillin #205 [Sorry for the poor description] On krillin UI freeze randomly. For example on the screenshot it occurred while dragging the greeter to unlock the phone. I was playing music, woke up the phone with the power button to turn the display on and did a right edge swipe to remove the greeter. This has been reported by several people in the past days, but I didn't find a pattern to reproduce this bug reliably. There is no crash in /var/crash and no apport activity. If I press the power button to turn the screen off/on again, the greeter is completely displayed (ie. doesn't cover half of the screen like the screenshot) but the UI is not responsive to gestures or input events. A long press on the power button shows the shutdown dialog but none of the button can be pressed. top doesn't show any specific process going crazy ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 8.00+14.10.20140822-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.6-0ubuntu2 Architecture: armhf Date: Sat Aug 23 14:18:00 2014 InstallationDate: Installed on 2014-08-23 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140823-020205) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1360593/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1238979] Re: Scope result models are cleared on updates
I agree that accidental activation is a problem. It's not nice if I tap something only to find that, a split second before my finger touched the glass, the list was updated and I've activated something else. If we animate new items into view, we have to make sure that a new item cannot displace an already-displayed item. Otherwise, if I have, say, five items on the list and I want to activate the fifth item, and now a new item slots in a position 3, shifting everything below it down, I'll end up accidentally activating the fourth item. I think the key to making sure that accidental activation doesn't happen is to enforce that an existing item cannot change physical location when a new item arrives. -- 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/1238979 Title: Scope result models are cleared on updates Status in Ubuntu UX bugs: New Status in Unity Media Scanner Scope: Invalid Status in API for Unity scopes integration: Invalid Status in QML plugin for Scopes: In Progress Status in “unity8” package in Ubuntu: Triaged Bug description: The result models are cleared when updated, which causes abrupt changes in the dash. We need a better way for updating the models without clearing them :/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1238979/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371313] Re: [krillin] Wi-Fi toggle disappears from menu when Wi-Fi disabled
Here's a test package with the latest urfkill changes. It's required to reproduce this bug along with the following instructions: 1. Make your image writable 2. Add the following pre-start script to the urfkill upstart job ( this will live in the device tarball when released ): pre-start script setprop urfkill.hybris.wlan 1 end script 3. Disable the Android wlan status script run on boot: - - adb reboot recovery - adb shell # mkdir /mnt # mount /dev/block/mmcblk0p6 /mnt # mkdir /mnt2 # mount /mnt/var/lib/lxc/android/system.img /mnt2 # cd bin # delete or comment-out the 'setprop' command ( or just remove the file ) in set_wlan_driver_status.sh # cd # umount /mnt2 # umount /mnt # sync Note, you may get errors when trying to unmount /mnt. If this happens to me, I just make sure to sync, exit and reboot using adb. ** Attachment added: "urfkill_0.6.0~20140918.070106.886990d-0ubuntu1~test1_armhf.deb" https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1371313/+attachment/4208019/+files/urfkill_0.6.0%7E20140918.070106.886990d-0ubuntu1%7Etest1_armhf.deb ** Changed in: indicator-network (Ubuntu) Importance: Undecided => Critical ** Changed in: indicator-network (Ubuntu) Assignee: (unassigned) => Antti Kaijanmäki (kaijanmaki) ** Tags added: rtm14 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1371313 Title: [krillin] Wi-Fi toggle disappears from menu when Wi-Fi disabled Status in “indicator-network” package in Ubuntu: New Bug description: Device/Image: krillin / rtm #44. Krillin's Wi-Fi driver has a broken rfkill implementation. As such, urfkill has been updated to allow control over Wi-Fi power via libhybris. When this mechanism is used to disable Wi-Fi on krillin, the Wi-Fi driver is unloaded as a result, with the corresponding system/NM devices going away as well. This causes the Wi-Fi enable/disable toggle to disappear from the indicator menu, making it impossible to re-enable Wi-Fi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1371313/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1318008] Re: Core apps .desktop files do not include translated strings
** Changed in: ubuntu-rssreader-app Status: New => In Progress ** Branch linked: lp:~dpm/ubuntu-rssreader-app/desktop-i18n ** Changed in: ubuntu-weather-app Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1318008 Title: Core apps .desktop files do not include translated strings Status in Address Book App: Fix Released Status in Camera App: Fix Released Status in Dialer app for Ubuntu Touch: Fix Released Status in Dropping Letters: Invalid Status in Gallery App: In Progress Status in Media Player App: In Progress Status in Messaging App: Fix Released Status in Music application for Ubuntu devices: Fix Released Status in Notes App: In Progress Status in Sudoku game for Ubuntu Touch: New Status in Calculator application for Ubuntu devices: Fix Released Status in Calendar application for Ubuntu devices: Fix Released Status in Clock application for Ubuntu devices: Fix Released Status in Ubuntu Clock App reboot series: In Progress Status in File Manager application for Ubuntu devices: Fix Committed Status in RSS Feed Reader application for Ubuntu devices: In Progress Status in Terminal application for Ubuntu devices: Fix Committed Status in Ubuntu Translations: Triaged Status in Weather application for Ubuntu devices: Fix Released Status in Web Browser App: Fix Released Status in “camera-app” package in Ubuntu: Fix Released Status in “dialer-app” package in Ubuntu: Fix Released Status in “messaging-app” package in Ubuntu: Fix Released Status in “ubuntu-system-settings” package in Ubuntu: Fix Released Status in “webbrowser-app” package in Ubuntu: Fix Released Bug description: As other apps cannot know where .mo files might be located for click packages, and unity8 apparently does not know about X-Ubuntu-Gettext- Domain for deb packages, the .desktop files for any applications will need to have their translations merged back into the .desktop file itself. This at a minimum should include the following .desktop fields: Name Comment Keywords (semicolon-separated list of strings) To manage notifications about this bug go to: https://bugs.launchpad.net/address-book-app/+bug/1318008/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371313] Re: [krillin] Wi-Fi toggle disappears from menu when Wi-Fi disabled
Here's a screenshot after Wi-Fi has been disabled. ** Attachment added: "net-menu-lp1371313.png" https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1371313/+attachment/4208008/+files/net-menu-lp1371313.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1371313 Title: [krillin] Wi-Fi toggle disappears from menu when Wi-Fi disabled Status in “indicator-network” package in Ubuntu: New Bug description: Device/Image: krillin / rtm #44. Krillin's Wi-Fi driver has a broken rfkill implementation. As such, urfkill has been updated to allow control over Wi-Fi power via libhybris. When this mechanism is used to disable Wi-Fi on krillin, the Wi-Fi driver is unloaded as a result, with the corresponding system/NM devices going away as well. This causes the Wi-Fi enable/disable toggle to disappear from the indicator menu, making it impossible to re-enable Wi-Fi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1371313/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371313] [NEW] [krillin] Wi-Fi toggle disappears from menu when Wi-Fi disabled
Public bug reported: Device/Image: krillin / rtm #44. Krillin's Wi-Fi driver has a broken rfkill implementation. As such, urfkill has been updated to allow control over Wi-Fi power via libhybris. When this mechanism is used to disable Wi-Fi on krillin, the Wi-Fi driver is unloaded as a result, with the corresponding system/NM devices going away as well. This causes the Wi-Fi enable/disable toggle to disappear from the indicator menu, making it impossible to re-enable Wi- Fi. ** Affects: indicator-network (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-network in Ubuntu. https://bugs.launchpad.net/bugs/1371313 Title: [krillin] Wi-Fi toggle disappears from menu when Wi-Fi disabled Status in “indicator-network” package in Ubuntu: New Bug description: Device/Image: krillin / rtm #44. Krillin's Wi-Fi driver has a broken rfkill implementation. As such, urfkill has been updated to allow control over Wi-Fi power via libhybris. When this mechanism is used to disable Wi-Fi on krillin, the Wi-Fi driver is unloaded as a result, with the corresponding system/NM devices going away as well. This causes the Wi-Fi enable/disable toggle to disappear from the indicator menu, making it impossible to re-enable Wi-Fi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1371313/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371310] Re: docker.io doesn't work with 3.0 RC1 kernel
Oh can we also test against the distro kernel that the RC1 patches are based on to ensure that there aren't other changes in play -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1371310 Title: docker.io doesn't work with 3.0 RC1 kernel Status in “apparmor” package in Ubuntu: New Status in “docker.io” package in Ubuntu: New Status in “linux” package in Ubuntu: Confirmed Bug description: Steps to reproduce (from https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor): 1. sudo apt-get install docker.io # 1.2.0~dfsg1-1 2. sudo docker pull ubuntu:trusty 3. sudo docker run ubuntu:trusty uptime 2014/09/18 15:48:48 Error response from daemon: Cannot start container fcdfaaf7945bcd9455fb5e0bde9950451152af14556880033818df7b50ddb1f4: set apparmor profile docker-default: permission denied What is expected? uptime to return something like: $ sudo docker run ubuntu:trusty uptime 20:31:21 up 1 min, 0 users, load average: 0.09, 0.06, 0.03 I set 'sudo sysctl -w kernel.printk_ratelimit=0' but there is nothing apparmor related in the logs. If I boot an earlier kernel without the 3.0 RC1 patches, it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1371310/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371310] Re: docker.io doesn't work with 3.0 RC1 kernel
a failure in change_profile from unconfined is NOT expected to log a message. Can you please verify that the target profile is loaded. The only reason apparmor rejects change_profile for unconfined is that the profile could not be found. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1371310 Title: docker.io doesn't work with 3.0 RC1 kernel Status in “apparmor” package in Ubuntu: New Status in “docker.io” package in Ubuntu: New Status in “linux” package in Ubuntu: Confirmed Bug description: Steps to reproduce (from https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor): 1. sudo apt-get install docker.io # 1.2.0~dfsg1-1 2. sudo docker pull ubuntu:trusty 3. sudo docker run ubuntu:trusty uptime 2014/09/18 15:48:48 Error response from daemon: Cannot start container fcdfaaf7945bcd9455fb5e0bde9950451152af14556880033818df7b50ddb1f4: set apparmor profile docker-default: permission denied What is expected? uptime to return something like: $ sudo docker run ubuntu:trusty uptime 20:31:21 up 1 min, 0 users, load average: 0.09, 0.06, 0.03 I set 'sudo sysctl -w kernel.printk_ratelimit=0' but there is nothing apparmor related in the logs. If I boot an earlier kernel without the 3.0 RC1 patches, it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1371310/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1367241] Re: Incorrect udev-fallback-graphics.conf
Hello Dariusz, or anyone else affected, Accepted udev into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/udev/175-0ubuntu9.7 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: udev (Ubuntu Precise) Status: In Progress => Fix Committed -- 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/1367241 Title: Incorrect udev-fallback-graphics.conf Status in “systemd” package in Ubuntu: Fix Committed Status in “udev” package in Ubuntu: Invalid Status in “udev” source package in Precise: Fix Committed Status in “systemd” source package in Trusty: Fix Committed Status in “systemd” source package in Utopic: Fix Committed Bug description: [Impact] * When setting up primary display driver fails an attempt to load vesafb module is undertaken. This fails since from 3.13.0-16.36 version vesafb is compiled in the kernel (so no actual modprobing is needed). This causes false alert in the log: "Starting load fallback graphic devices: [fail]" [Test Case] * Start Ubuntu unable to load primary graphics driver (the simplest way is to remove module responsible for the device). * Wait for loading graphics devices. * If the primary device module has failed to load, falling back to vesafb will be attempted. [Regression Potential] * Implemented by the bug reported. * Affects only the debian/ directory. [Other Info] * Original bug description: The udev-fallback-graphics.conf script tries to load vesafb module if PRIMARY_DEVICE_FOR_DISPLAY has not been set earlier. The problem is that from kernel version 3.13.0-16.36 vesafb is compiled in permanently into the kernel (CONFIG_FB_VESA=y), so whenever the fallback mode is triggered this script will FAIL confusing the users. Most probably this file is no longer needed (or it just be used to print informative message). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1367241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368420] Re: Prices shown incorrectly in some locales
** Also affects: libjsoncpp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1368420 Title: Prices shown incorrectly in some locales Status in “libjsoncpp” package in Ubuntu: New Status in “unity-scope-click” package in Ubuntu: Triaged Bug description: In some locales, some prices seem to be shown incorrectly. For example, a price of "2.99" for an app is being shown as "2,00" when using the Spanish locale. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjsoncpp/+bug/1368420/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371310] [NEW] docker.io doesn't work with 3.0 RC1 kernel
Public bug reported: Steps to reproduce (from https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor): 1. sudo apt-get install docker.io # 1.2.0~dfsg1-1 2. sudo docker pull ubuntu:trusty 3. sudo docker run ubuntu:trusty uptime 2014/09/18 15:48:48 Error response from daemon: Cannot start container fcdfaaf7945bcd9455fb5e0bde9950451152af14556880033818df7b50ddb1f4: set apparmor profile docker-default: permission denied What is expected? uptime to return something like: $ sudo docker run ubuntu:trusty uptime 20:31:21 up 1 min, 0 users, load average: 0.09, 0.06, 0.03 I set 'sudo sysctl -w kernel.printk_ratelimit=0' but there is nothing apparmor related in the logs. If I boot an earlier kernel without the 3.0 RC1 patches, it works. ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Affects: docker.io (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Also affects: docker.io (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1371310 Title: docker.io doesn't work with 3.0 RC1 kernel Status in “apparmor” package in Ubuntu: New Status in “docker.io” package in Ubuntu: New Status in “linux” package in Ubuntu: Confirmed Bug description: Steps to reproduce (from https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor): 1. sudo apt-get install docker.io # 1.2.0~dfsg1-1 2. sudo docker pull ubuntu:trusty 3. sudo docker run ubuntu:trusty uptime 2014/09/18 15:48:48 Error response from daemon: Cannot start container fcdfaaf7945bcd9455fb5e0bde9950451152af14556880033818df7b50ddb1f4: set apparmor profile docker-default: permission denied What is expected? uptime to return something like: $ sudo docker run ubuntu:trusty uptime 20:31:21 up 1 min, 0 users, load average: 0.09, 0.06, 0.03 I set 'sudo sysctl -w kernel.printk_ratelimit=0' but there is nothing apparmor related in the logs. If I boot an earlier kernel without the 3.0 RC1 patches, it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1371310/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1359332] Missing SRU information
Thanks for uploading the fix for this bug report to -proposed. However, when reviewing the package in -proposed and the details of this bug report I noticed that the bug description is missing information required for the SRU process. You can find full details at http://wiki.ubuntu.com/StableReleaseUpdates#Procedure but essentially this bug is missing some of the following: a statement of impact, a test case and details regarding the regression potential. Thanks in advance! -- 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/1359332 Title: Need to allow for both Unity 8 desktop "bare metal" and LXC sessions Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Released Status in Unity 8 Desktop Session: Fix Committed Status in unity8-desktop-session trusty series: In Progress Status in Unity8 Desktop Preview in LXC: Fix Committed Status in “lightdm” package in Ubuntu: Fix Released Status in “unity8-desktop-session” package in Ubuntu: Fix Released Status in “lightdm” source package in Trusty: New Status in “unity8-desktop-session” source package in Trusty: New Status in “lightdm” source package in Utopic: Fix Released Status in “unity8-desktop-session” source package in Utopic: Fix Released Bug description: It would be desirable to allow both the Unity 8 desktop preview session from the archive and the Unity 8 desktop preview in the LXC to be installed at the same time. Currently, the Unity 8 desktop preview in LXC conflicts the "bare metal" Unity 8 desktop preview session. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1359332/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1359332] Re: Need to allow for both Unity 8 desktop "bare metal" and LXC sessions
Here is the diff for future reviewers: diff -Nru unity8-desktop-session-1.0.10+14.04.20140417.1/data/55-unity8.conf unity8-desktop-session-1.0.10+14.04.20140915/data/55-unity8.conf --- unity8-desktop-session-1.0.10+14.04.20140417.1/data/55-unity8.conf 2014-04-17 05:07:47.0 -0700 +++ unity8-desktop-session-1.0.10+14.04.20140915/data/55-unity8.conf 2014-09-15 05:32:54.0 -0700 @@ -1,2 +1,4 @@ [SeatDefaults] +user-session=unity8-mir +unity-compositor-command=/usr/sbin/unity-system-compositor session-wrapper=lightdm-unity8-session diff -Nru unity8-desktop-session-1.0.10+14.04.20140417.1/data/lightdm-unity8-session unity8-desktop-session-1.0.10+14.04.20140915/data/lightdm-unity8-session --- unity8-desktop-session-1.0.10+14.04.20140417.1/data/lightdm-unity8-session 2014-04-17 05:07:47.0 -0700 +++ unity8-desktop-session-1.0.10+14.04.20140915/data/lightdm-unity8-session 2014-09-15 05:32:54.0 -0700 @@ -4,7 +4,7 @@ # traditional X-based desktop session startup. # -if test -z "$DISPLAY"; then +if test -z "$DISPLAY" && [ $DESKTOP_SESSION != "unity8-mir-lxc" ]; then exec init --user else exec /usr/sbin/lightdm-session "$@" diff -Nru unity8-desktop-session-1.0.10+14.04.20140417.1/debian/changelog unity8-desktop-session-1.0.10+14.04.20140915/debian/changelog --- unity8-desktop-session-1.0.10+14.04.20140417.1/debian/changelog 2014-09-18 13:49:23.0 -0700 +++ unity8-desktop-session-1.0.10+14.04.20140915/debian/changelog 2014-09-18 13:49:23.0 -0700 @@ -1,3 +1,12 @@ +unity8-desktop-session (1.0.10+14.04.20140915-0ubuntu1) trusty; urgency=low + + [ Chris Townsend ] + * Add check to see if the Unity8 LXC session is not being started +before calling the init script. Also, add explicit call to +/usr/sbin/unity-system-compositor. (LP: #1359332) + + -- Ubuntu daily release Mon, 15 Sep 2014 12:33:09 + + unity8-desktop-session (1.0.10+14.04.20140417.1-0ubuntu1) trusty; urgency=low [ Michał Sawicz ] -- 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/1359332 Title: Need to allow for both Unity 8 desktop "bare metal" and LXC sessions Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Released Status in Unity 8 Desktop Session: Fix Committed Status in unity8-desktop-session trusty series: In Progress Status in Unity8 Desktop Preview in LXC: Fix Committed Status in “lightdm” package in Ubuntu: Fix Released Status in “unity8-desktop-session” package in Ubuntu: Fix Released Status in “lightdm” source package in Trusty: New Status in “unity8-desktop-session” source package in Trusty: New Status in “lightdm” source package in Utopic: Fix Released Status in “unity8-desktop-session” source package in Utopic: Fix Released Bug description: It would be desirable to allow both the Unity 8 desktop preview session from the archive and the Unity 8 desktop preview in the LXC to be installed at the same time. Currently, the Unity 8 desktop preview in LXC conflicts the "bare metal" Unity 8 desktop preview session. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1359332/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371246] Re: netns ifconfig problem
** Package changed: ubuntu => iproute2 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1371246 Title: netns ifconfig problem Status in “iproute2” package in Ubuntu: New Bug description: I am using IP name space virtualization feature in Ubuntu 14.04. The simplest script for this is: #! /bin/sh ip netns add test ip link set dev eth1 netns test ip netns exec ip addr add 10.4.1.21/16 dev eth1 ip netns exec test ip link set dev eth1 up The node has eth0 with 10.4.1.20/16 and connected eth0 to eth1 by external cable. All had worked fine during updating Ubuntu 14.04 at the 14th or 15th of September. All is OK in Ubuntu 12.04 LTS. After the starting script I have a wrong result for 'sudo ip netns exec test ifconfig eth1' output as zero's broadcast address in test IP name space. Command 'sudo ip netns exec test ping 10.4.21.1' has failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1371246/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351092] Re: Configuration of the Droid Sans Fallback font
** Branch linked: lp:ubuntu/trusty-proposed/fonts-android -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-android in Ubuntu. https://bugs.launchpad.net/bugs/1351092 Title: Configuration of the Droid Sans Fallback font Status in “fonts-android” package in Ubuntu: Fix Released Status in “language-selector” package in Ubuntu: Fix Released Status in “fonts-android” source package in Trusty: Fix Committed Status in “language-selector” source package in Trusty: Fix Committed Status in “fonts-android” package in Debian: New Bug description: [Impact] fontconfig configuration settings, aimed at making the Droid Sans Fallback font be used to render Chinese, fails sometimes in an unpredictable way. This seems to be caused by the file 65-droid-sans- fonts.conf, which is currently installed by fonts-droid. Consequently that file is proposed to be dropped from fonts-droid. Some fontconfig files in language-selector are proposed to be changed accordingly. Example problems: * One of the AR PL UMing fonts is sometimes used instead of Droid Sans Fallback in case of a Chinese locale. * Buggy rendering of Chinese contents in qt apps in case of a non-Chinese locale (bug #1334495). * Droid Sans Fallback can't be used in Ubuntu Touch (see discussion at bug #1346766). [Test Case] Since the behaviour is not always buggy, it's hard to present a proper test case. Instead I have to refer to the discussions in this bug report as well as the above mentioned bugs. [Regression Potential] While the fonts-droid package installs a bunch of fonts for various languages, only the Droid Sans Fallback font is used as part of Ubuntu's default font configuration. The regression risk for Chinese users is reasonably very low. There is a risk, though, that this change leads to surprise changes for individual users who make use of other fonts but Droid Sans Fallback. There is no indication that those other fonts are widely used. [Original description] There are currently several open issues related to the use of Droid Sans Fallback for rendering Chinese content: * Two mixed fonts when rendering Chinese in KDE/QT apps with Droid Sans fonts https://launchpad.net/bugs/1334495 * Droid Sans no longer preferred font for Chinese https://launchpad.net/bugs/1335482 * Chinese in Ubuntu Touch should use Heiti style sans serif font https://launchpad.net/bugs/1346766 Unlike e.g. fonts-wqy-microhei, the fonts-droid package installs a bunch of fonts, of which only one is needed for Chinese. In an attempt to sort things out I have built the fonts-android source package in my PPA with the DroidSansFallbackFull.ttf font broken out to a separate binary package named fonts-droid-cjk. The PPA also includes a version of language-selector where the changes in version 0.129.2 have been reverted. To test it in Trusty, you should: * Uninstall the fonts-droid package * Install fonts-droid-cjk and language-selector-common from my PPA at https://launchpad.net/~gunnarhj/+archive/ubuntu/droid-test My own tests indicate that the change to language-selector due to bug #1335482 was a step in the wrong direction. With DroidSansFallbackFull.ttf as the only installed font from the Droid Sans family, you get rid of possible confusion that might have resulted in the issue reported in that bug. $ LANG=zh_CN.UTF-8 fc-match -s 'sans-serif' | head -n 5 DroidSansFallbackFull.ttf: "Droid Sans Fallback" "Regular" uming.ttc: "AR PL UMing CN" "Light" uming.ttc: "AR PL UMing HK" "Light" ukai.ttc: "AR PL UKai CN" "Book" DejaVuSans.ttf: "DejaVu Sans" "Book" Also, if we would take this route, it might be easier to fix a configuration that makes Droid Sans Fallback work well with qt apps. (This is pure theory/hope so far.) Looking forward to your comments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1351092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1334495] Re: Two mixed fonts when rendering Chinese in KDE/QT apps with Droid Sans fonts
** Branch linked: lp:ubuntu/trusty-proposed/fonts-android -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-android in Ubuntu. https://bugs.launchpad.net/bugs/1334495 Title: Two mixed fonts when rendering Chinese in KDE/QT apps with Droid Sans fonts Status in “fonts-android” package in Ubuntu: Fix Released Status in “language-selector” package in Ubuntu: Fix Released Status in “fonts-android” source package in Trusty: Fix Committed Status in “language-selector” source package in Trusty: Fix Committed Bug description: [Info for the Trusty SRU request] Please see the description at bug #1351092. [Original description] Bug: In all desktop applications, two different fonts are mixed to display Chinese text. I attached a screenshot of a paragraph of Chinese text in Kmail - some characters are displayed using a "italic" font, others in a "normal" font. The same problem exists in other applications, for example Dolphin or even Konsole. In Xterm, only the "normal" characters are displayed, where Dolphin displays italic characters Xterm leaves a white space. Websites are displayed fine, if I open the same mail in the web interface only one font is used. Background I' am using Kubuntu 14.04 with the language set to German in KDE settings. The output of "locale" looks a bit messed up, I don't know why, as in the KDE settings all formats are consistently set to German standard. "locale LANG=de_DE.UTF-8 LANGUAGE=de:en:zh:en LC_CTYPE="de_DE.UTF-8" LC_NUMERIC=zh_CN.UTF-8 LC_TIME=zh_CN.UTF-8 LC_COLLATE="de_DE.UTF-8" LC_MONETARY=zh_CN.UTF-8 LC_MESSAGES="de_DE.UTF-8" LC_PAPER=zh_CN.UTF-8 LC_NAME=zh_CN.UTF-8 LC_ADDRESS=zh_CN.UTF-8 LC_TELEPHONE=zh_CN.UTF-8 LC_MEASUREMENT=zh_CN.UTF-8 LC_IDENTIFICATION=zh_CN.UTF-8 LC_ALL= " fc-match: »DejaVuSans.ttf: "DejaVu Sans" "Book"« This is my first bug filed at launchpad. I filed it for language- selector as other related bugs I found were filed for the same package. If it isn't language-selector, perhaps you can point me to the right package? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1334495/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371246] [NEW] netns ifconfig problem
You have been subscribed to a public bug: I am using IP name space virtualization feature in Ubuntu 14.04. The simplest script for this is: #! /bin/sh ip netns add test ip link set dev eth1 netns test ip netns exec ip addr add 10.4.1.21/16 dev eth1 ip netns exec test ip link set dev eth1 up The node has eth0 with 10.4.1.20/16 and connected eth0 to eth1 by external cable. All had worked fine during updating Ubuntu 14.04 at the 14th or 15th of September. All is OK in Ubuntu 12.04 LTS. After the starting script I have a wrong result for 'sudo ip netns exec test ifconfig eth1' output as zero's broadcast address in test IP name space. Command 'sudo ip netns exec test ping 10.4.21.1' has failed. ** Affects: iproute2 (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment netns -- netns ifconfig problem https://bugs.launchpad.net/bugs/1371246 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 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 1371303] Re: missing MultiArch breaks multiarch packages that depend on realpath
** Package changed: realpath (Ubuntu) => coreutils (Ubuntu) ** Summary changed: - missing MultiArch breaks multiarch packages that depend on realpath + realpath missing MultiArch breaks multiarch packages that depend on realpath -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1371303 Title: realpath missing MultiArch breaks multiarch packages that depend on realpath Status in “coreutils” package in Ubuntu: New Bug description: the transitional package seems to have dropped MultiArch: foreign, and that breaks depending on it from a multiarch:same package. Can we have it back please? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1371303/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371303] [NEW] missing MultiArch breaks multiarch packages that depend on realpath
You have been subscribed to a public bug: the transitional package seems to have dropped MultiArch: foreign, and that breaks depending on it from a multiarch:same package. Can we have it back please? ** Affects: coreutils (Ubuntu) Importance: Undecided Status: New -- missing MultiArch breaks multiarch packages that depend on realpath https://bugs.launchpad.net/bugs/1371303 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils 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 1364368] Re: Something has a memory leak
*** This bug is a duplicate of bug 1206146 *** https://bugs.launchpad.net/bugs/1206146 ** This bug has been marked a duplicate of bug 1206146 /system/lib/libubuntu_application_api.so leaks memory constantly -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to maliit-framework in Ubuntu. https://bugs.launchpad.net/bugs/1364368 Title: Something has a memory leak Status in QT Ubuntu Sensors: New Status in “maliit-framework” package in Ubuntu: New Bug description: I've tracked memory utilisation of maliit-server over a 12 hour period and can see that the heap is growing at about 1700 bytes a second. One can see this by strac'ing the process and seeing glib's malloc performing 4K mprotects every ~2.4 seconds and the occasional 1MB mmap2 to anonymous memory (aka heap) every 600-620 seconds. [pid 2708] 12:48:57 mprotect(0xa01fa000, 4096, PROT_READ|PROT_WRITE) = 0 [pid 2708] 12:48:59 mprotect(0xa01fb000, 4096, PROT_READ|PROT_WRITE) = 0 [pid 2708] 12:49:02 mprotect(0xa01fc000, 4096, PROT_READ|PROT_WRITE) = 0 [pid 2708] 12:49:04 mprotect(0xa01fd000, 4096, PROT_READ|PROT_WRITE) = 0 [pid 2708] 12:49:07 mprotect(0xa01fe000, 4096, PROT_READ|PROT_WRITE) = 0 [pid 2708] 12:49:09 mprotect(0xa01ff000, 4096, PROT_READ|PROT_WRITE) = 0 [pid 2708] 12:49:11 mmap2(0xa020, 1048576, PROT_NONE, MAP_PRIVATE|MAP_ANONY MOUS|MAP_NORESERVE, -1, 0) = 0xa020 [pid 2708] 12:49:11 mprotect(0xa020, 135168, PROT_READ|PROT_WRITE) = 0 Over a period of 1 day this will leak 140MB. To manage notifications about this bug go to: https://bugs.launchpad.net/qtubuntu-sensors/+bug/1364368/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371028] Re: YouTube scope depends on pending scopes release
** Tags removed: rtm-14 ** Tags added: rtm14 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1371028 Title: YouTube scope depends on pending scopes release Status in QML plugin for Scopes: Invalid Status in “unity-scopes-api” package in Ubuntu: Fix Committed Bug description: - this only happens since r47 in krillin Reproduction: - favourite the youtube scope - make sure it works - reboot the phone Outcome: youtube scope is not populated the following log appears in /home/phablet/.cache/upstart/scope-registry.log http://paste.ubuntu.com/8371069/ Same problem happens with the my pictures scope To manage notifications about this bug go to: https://bugs.launchpad.net/unity-scopes-shell/+bug/1371028/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1334495] Re: Two mixed fonts when rendering Chinese in KDE/QT apps with Droid Sans fonts
Hello Lukas, or anyone else affected, Accepted language-selector into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/language- selector/0.129.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-android in Ubuntu. https://bugs.launchpad.net/bugs/1334495 Title: Two mixed fonts when rendering Chinese in KDE/QT apps with Droid Sans fonts Status in “fonts-android” package in Ubuntu: Fix Released Status in “language-selector” package in Ubuntu: Fix Released Status in “fonts-android” source package in Trusty: Fix Committed Status in “language-selector” source package in Trusty: Fix Committed Bug description: [Info for the Trusty SRU request] Please see the description at bug #1351092. [Original description] Bug: In all desktop applications, two different fonts are mixed to display Chinese text. I attached a screenshot of a paragraph of Chinese text in Kmail - some characters are displayed using a "italic" font, others in a "normal" font. The same problem exists in other applications, for example Dolphin or even Konsole. In Xterm, only the "normal" characters are displayed, where Dolphin displays italic characters Xterm leaves a white space. Websites are displayed fine, if I open the same mail in the web interface only one font is used. Background I' am using Kubuntu 14.04 with the language set to German in KDE settings. The output of "locale" looks a bit messed up, I don't know why, as in the KDE settings all formats are consistently set to German standard. "locale LANG=de_DE.UTF-8 LANGUAGE=de:en:zh:en LC_CTYPE="de_DE.UTF-8" LC_NUMERIC=zh_CN.UTF-8 LC_TIME=zh_CN.UTF-8 LC_COLLATE="de_DE.UTF-8" LC_MONETARY=zh_CN.UTF-8 LC_MESSAGES="de_DE.UTF-8" LC_PAPER=zh_CN.UTF-8 LC_NAME=zh_CN.UTF-8 LC_ADDRESS=zh_CN.UTF-8 LC_TELEPHONE=zh_CN.UTF-8 LC_MEASUREMENT=zh_CN.UTF-8 LC_IDENTIFICATION=zh_CN.UTF-8 LC_ALL= " fc-match: »DejaVuSans.ttf: "DejaVu Sans" "Book"« This is my first bug filed at launchpad. I filed it for language- selector as other related bugs I found were filed for the same package. If it isn't language-selector, perhaps you can point me to the right package? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1334495/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1334495] Please test proposed package
Hello Lukas, or anyone else affected, Accepted fonts-android into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/fonts- android/1:4.3-3ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-android in Ubuntu. https://bugs.launchpad.net/bugs/1334495 Title: Two mixed fonts when rendering Chinese in KDE/QT apps with Droid Sans fonts Status in “fonts-android” package in Ubuntu: Fix Released Status in “language-selector” package in Ubuntu: Fix Released Status in “fonts-android” source package in Trusty: Fix Committed Status in “language-selector” source package in Trusty: Fix Committed Bug description: [Info for the Trusty SRU request] Please see the description at bug #1351092. [Original description] Bug: In all desktop applications, two different fonts are mixed to display Chinese text. I attached a screenshot of a paragraph of Chinese text in Kmail - some characters are displayed using a "italic" font, others in a "normal" font. The same problem exists in other applications, for example Dolphin or even Konsole. In Xterm, only the "normal" characters are displayed, where Dolphin displays italic characters Xterm leaves a white space. Websites are displayed fine, if I open the same mail in the web interface only one font is used. Background I' am using Kubuntu 14.04 with the language set to German in KDE settings. The output of "locale" looks a bit messed up, I don't know why, as in the KDE settings all formats are consistently set to German standard. "locale LANG=de_DE.UTF-8 LANGUAGE=de:en:zh:en LC_CTYPE="de_DE.UTF-8" LC_NUMERIC=zh_CN.UTF-8 LC_TIME=zh_CN.UTF-8 LC_COLLATE="de_DE.UTF-8" LC_MONETARY=zh_CN.UTF-8 LC_MESSAGES="de_DE.UTF-8" LC_PAPER=zh_CN.UTF-8 LC_NAME=zh_CN.UTF-8 LC_ADDRESS=zh_CN.UTF-8 LC_TELEPHONE=zh_CN.UTF-8 LC_MEASUREMENT=zh_CN.UTF-8 LC_IDENTIFICATION=zh_CN.UTF-8 LC_ALL= " fc-match: »DejaVuSans.ttf: "DejaVu Sans" "Book"« This is my first bug filed at launchpad. I filed it for language- selector as other related bugs I found were filed for the same package. If it isn't language-selector, perhaps you can point me to the right package? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1334495/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351092] Please test proposed package
Hello Gunnar, or anyone else affected, Accepted fonts-android into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/fonts- android/1:4.3-3ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-android in Ubuntu. https://bugs.launchpad.net/bugs/1351092 Title: Configuration of the Droid Sans Fallback font Status in “fonts-android” package in Ubuntu: Fix Released Status in “language-selector” package in Ubuntu: Fix Released Status in “fonts-android” source package in Trusty: Fix Committed Status in “language-selector” source package in Trusty: Fix Committed Status in “fonts-android” package in Debian: New Bug description: [Impact] fontconfig configuration settings, aimed at making the Droid Sans Fallback font be used to render Chinese, fails sometimes in an unpredictable way. This seems to be caused by the file 65-droid-sans- fonts.conf, which is currently installed by fonts-droid. Consequently that file is proposed to be dropped from fonts-droid. Some fontconfig files in language-selector are proposed to be changed accordingly. Example problems: * One of the AR PL UMing fonts is sometimes used instead of Droid Sans Fallback in case of a Chinese locale. * Buggy rendering of Chinese contents in qt apps in case of a non-Chinese locale (bug #1334495). * Droid Sans Fallback can't be used in Ubuntu Touch (see discussion at bug #1346766). [Test Case] Since the behaviour is not always buggy, it's hard to present a proper test case. Instead I have to refer to the discussions in this bug report as well as the above mentioned bugs. [Regression Potential] While the fonts-droid package installs a bunch of fonts for various languages, only the Droid Sans Fallback font is used as part of Ubuntu's default font configuration. The regression risk for Chinese users is reasonably very low. There is a risk, though, that this change leads to surprise changes for individual users who make use of other fonts but Droid Sans Fallback. There is no indication that those other fonts are widely used. [Original description] There are currently several open issues related to the use of Droid Sans Fallback for rendering Chinese content: * Two mixed fonts when rendering Chinese in KDE/QT apps with Droid Sans fonts https://launchpad.net/bugs/1334495 * Droid Sans no longer preferred font for Chinese https://launchpad.net/bugs/1335482 * Chinese in Ubuntu Touch should use Heiti style sans serif font https://launchpad.net/bugs/1346766 Unlike e.g. fonts-wqy-microhei, the fonts-droid package installs a bunch of fonts, of which only one is needed for Chinese. In an attempt to sort things out I have built the fonts-android source package in my PPA with the DroidSansFallbackFull.ttf font broken out to a separate binary package named fonts-droid-cjk. The PPA also includes a version of language-selector where the changes in version 0.129.2 have been reverted. To test it in Trusty, you should: * Uninstall the fonts-droid package * Install fonts-droid-cjk and language-selector-common from my PPA at https://launchpad.net/~gunnarhj/+archive/ubuntu/droid-test My own tests indicate that the change to language-selector due to bug #1335482 was a step in the wrong direction. With DroidSansFallbackFull.ttf as the only installed font from the Droid Sans family, you get rid of possible confusion that might have resulted in the issue reported in that bug. $ LANG=zh_CN.UTF-8 fc-match -s 'sans-serif' | head -n 5 DroidSansFallbackFull.ttf: "Droid Sans Fallback" "Regular" uming.ttc: "AR PL UMing CN" "Light" uming.ttc: "AR PL UMing HK" "Light" ukai.ttc: "AR PL UKai CN" "Book" DejaVuSans.ttf: "DejaVu Sans" "Book" Also, if we would take this route, it might be easier to fix a configuration that makes Droid Sans Fallback work well with qt apps. (This is pure theory/hope so far.) Looking forward to your comments. To manage notifications about this bug go to: https://bugs.l
[Touch-packages] [Bug 1351092] Re: Configuration of the Droid Sans Fallback font
Hello Gunnar, or anyone else affected, Accepted language-selector into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/language- selector/0.129.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-android in Ubuntu. https://bugs.launchpad.net/bugs/1351092 Title: Configuration of the Droid Sans Fallback font Status in “fonts-android” package in Ubuntu: Fix Released Status in “language-selector” package in Ubuntu: Fix Released Status in “fonts-android” source package in Trusty: Fix Committed Status in “language-selector” source package in Trusty: Fix Committed Status in “fonts-android” package in Debian: New Bug description: [Impact] fontconfig configuration settings, aimed at making the Droid Sans Fallback font be used to render Chinese, fails sometimes in an unpredictable way. This seems to be caused by the file 65-droid-sans- fonts.conf, which is currently installed by fonts-droid. Consequently that file is proposed to be dropped from fonts-droid. Some fontconfig files in language-selector are proposed to be changed accordingly. Example problems: * One of the AR PL UMing fonts is sometimes used instead of Droid Sans Fallback in case of a Chinese locale. * Buggy rendering of Chinese contents in qt apps in case of a non-Chinese locale (bug #1334495). * Droid Sans Fallback can't be used in Ubuntu Touch (see discussion at bug #1346766). [Test Case] Since the behaviour is not always buggy, it's hard to present a proper test case. Instead I have to refer to the discussions in this bug report as well as the above mentioned bugs. [Regression Potential] While the fonts-droid package installs a bunch of fonts for various languages, only the Droid Sans Fallback font is used as part of Ubuntu's default font configuration. The regression risk for Chinese users is reasonably very low. There is a risk, though, that this change leads to surprise changes for individual users who make use of other fonts but Droid Sans Fallback. There is no indication that those other fonts are widely used. [Original description] There are currently several open issues related to the use of Droid Sans Fallback for rendering Chinese content: * Two mixed fonts when rendering Chinese in KDE/QT apps with Droid Sans fonts https://launchpad.net/bugs/1334495 * Droid Sans no longer preferred font for Chinese https://launchpad.net/bugs/1335482 * Chinese in Ubuntu Touch should use Heiti style sans serif font https://launchpad.net/bugs/1346766 Unlike e.g. fonts-wqy-microhei, the fonts-droid package installs a bunch of fonts, of which only one is needed for Chinese. In an attempt to sort things out I have built the fonts-android source package in my PPA with the DroidSansFallbackFull.ttf font broken out to a separate binary package named fonts-droid-cjk. The PPA also includes a version of language-selector where the changes in version 0.129.2 have been reverted. To test it in Trusty, you should: * Uninstall the fonts-droid package * Install fonts-droid-cjk and language-selector-common from my PPA at https://launchpad.net/~gunnarhj/+archive/ubuntu/droid-test My own tests indicate that the change to language-selector due to bug #1335482 was a step in the wrong direction. With DroidSansFallbackFull.ttf as the only installed font from the Droid Sans family, you get rid of possible confusion that might have resulted in the issue reported in that bug. $ LANG=zh_CN.UTF-8 fc-match -s 'sans-serif' | head -n 5 DroidSansFallbackFull.ttf: "Droid Sans Fallback" "Regular" uming.ttc: "AR PL UMing CN" "Light" uming.ttc: "AR PL UMing HK" "Light" ukai.ttc: "AR PL UKai CN" "Book" DejaVuSans.ttf: "DejaVu Sans" "Book" Also, if we would take this route, it might be easier to fix a configuration that makes Droid Sans Fallback work well with qt apps. (This is pure theory/hope so far.) Looking forward to your comments. To manage notifications a
[Touch-packages] [Bug 1370175] Re: Libav security fixes Sept 2014
thank you Seth -- 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/1370175 Title: Libav security fixes Sept 2014 Status in “libav” package in Ubuntu: Confirmed Status in “libav” source package in Precise: Fix Released Status in “libav” source package in Trusty: Confirmed Status in “libav” source package in Utopic: Confirmed Bug description: Libav 9.17 and 0.8.16 are out, and fix "a number of critical functional and security issues (many of which have CVE identifiers assigned)" http://www.libav.org/news.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1370175/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371159] Re: MacBookPro 11, 1 (Haswell, retina) fails to both suspend and hibernate with ubuntu 14.04
Further info: turns out that the system is running without swap space: $ sudo blkid /dev/sda2: UUID="" TYPE="ext4" ... lists only one, when it shoud list also the swap partition. So: $ sudo swapon -a swapon: /dev/mapper/cryptswap1: stat failed: No such file or directory The /etc/fstab lists the swap partition under /dev/mapper/cryptswap1. While I never chose to encrypt swap, during the installation I did choose to encrypt my home directory. Perhaps the installer encrypted swap as well, and that is creating the problem with the lack of suspend and hibernate. Attempting to run "sudo swapon -U " fails as well. I used the UUID listed in a comment in fstab. Any specific solutions to this problem? Perhaps this would solve the suspend/hibernate as well. Thank you. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1371159 Title: MacBookPro 11,1 (Haswell, retina) fails to both suspend and hibernate with ubuntu 14.04 Status in “pm-utils” package in Ubuntu: New Bug description: Cannot make a MacBookPro 11,1 suspend. 1. When putting the lid down, acpi_listen prints: $ acpi_listen button/lid LID close button/lid LID open ... so the lid is signalling correctly. Upon opening, the screensaver prompt is present, and typing in the password brings me back to the desktop. Nothing is found in dmesg. 2. When choosing "suspend" from the top-right power menu, the screen goes black and shortly lights up again, showing the screensaver login prompt. Typing in the password brings me back to the desktop as if nothing had happened. 3. To remark that the power menu in the System Settings shows sometimes "Suspend" as greyed out, and hibernate is not listed. Perhaps this is related to the suspend process taking very long (minutes) as reported in other bugs, but I have never waited so long to find out. 4. When attempting to hibernate instead, using: $ sudo pm-hibernate ... something similar to triggering a suspend happens, but this time dmesg lists one error: [ 1434.487141] [drm:hsw_unclaimed_reg_clear] *ERROR* Unknown unclaimed register before writing to 2030 The whole relevant part of the dmesg is below, containing the sequence towards hibernation and then the sequence towards power up, cropped at the CPUs. [ 1434.121698] init: anacron main process (6746) killed by TERM signal [ 1434.160094] PM: Syncing filesystems ... done. [ 1434.164415] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 1434.166115] PM: Marking nosave pages: [mem 0x00058000-0x00058fff] [ 1434.166116] PM: Marking nosave pages: [mem 0x0008f000-0x0008] [ 1434.166117] PM: Marking nosave pages: [mem 0x0009f000-0x000f] [ 1434.166119] PM: Marking nosave pages: [mem 0x8ad14000-0x8ad52fff] [ 1434.166121] PM: Marking nosave pages: [mem 0x8ad62000-0x8ad75fff] [ 1434.166122] PM: Marking nosave pages: [mem 0x8ad77000-0x8ad8efff] [ 1434.166123] PM: Marking nosave pages: [mem 0x8af4b000-0x8afe4fff] [ 1434.166125] PM: Marking nosave pages: [mem 0x8b00-0x] [ 1434.166977] PM: Basic memory bitmaps created [ 1434.167010] PM: Preallocating image memory... done (allocated 872683 pages) [ 1434.484991] PM: Allocated 3490732 kbytes in 0.31 seconds (11260.42 MB/s) [ 1434.484993] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 1434.486307] Suspending console(s) (use no_console_suspend to debug) [ 1434.487014] mei_me :00:16.0: H_RDY is not cleared 0x80141418 [ 1434.487141] [drm:hsw_unclaimed_reg_clear] *ERROR* Unknown unclaimed register before writing to 2030 [ 1435.603939] PM: freeze of devices complete after 1118.720 msecs [ 1435.604106] PM: late freeze of devices complete after 0.166 msecs [ 1435.604950] PM: noirq freeze of devices complete after 0.843 msecs [ 1435.605211] ACPI: Preparing to enter system sleep state S4 [ 1435.605985] PM: Saving platform NVS memory [ 1435.606140] Disabling non-boot CPUs ... [ 1435.607323] kvm: disabling virtualization on CPU1 [ 1435.607606] smpboot: CPU 1 is now offline [ 1435.608996] kvm: disabling virtualization on CPU2 [ 1435.710785] smpboot: CPU 2 is now offline [ 1435.712130] kvm: disabling virtualization on CPU3 [ 1435.814678] smpboot: CPU 3 is now offline [ 1435.815042] PM: Creating hibernation image: [ 1435.994507] PM: Need to copy 871520 pages [ 1435.994508] PM: Normal pages needed: 871520 + 1024, available pages: 3299080 [ 1436.710789] PM: Hibernation image created (871520 pages copied) [ 1435.816195] Enabling non-boot CPUs ... [ 1435.816221] x86: Booting SMP configuration: [ 1435.816222] smpboot: Booting Node 0 Processor 1 APIC 0x2 [ 1435.828025] kvm: enabling virtualization on CPU1 [ 1435.830204] CPU1 is up [ 1435.830216] smpboot: Booting Node 0 Processor 2 APIC 0x1 [ 1435.842013] kvm: enabling virtuali
[Touch-packages] [Bug 969343] Re: Unable to connect to WPA enterprise wireless
** Changed in: wpa (Debian) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/969343 Title: Unable to connect to WPA enterprise wireless Status in OEM Priority Project: Fix Released Status in OEM Priority Project precise series: Fix Released Status in OpenSSL cryptography and SSL/TLS toolkit: New Status in Linux WPA/WPA2/IEEE 802.1X Supplicant: In Progress Status in “openssl” package in Ubuntu: Invalid Status in “wpa” package in Ubuntu: Fix Released Status in “wpasupplicant” package in Ubuntu: Invalid Status in “openssl” source package in Precise: Invalid Status in “wpa” source package in Precise: Invalid Status in “wpasupplicant” source package in Precise: Fix Released Status in “wpa” package in Debian: Fix Released Status in “openssl” package in Fedora: New Status in “wpasupplicant” package in Fedora: Unknown Bug description: [Impact] Breaks 802.1x (PEAP) authentication for wireless networks using specific authentication servers and/or AP hardware. Aruba network devices specifically are known to be affected; and is a popular device type used in enterprises to secure wireless networks. [Test Case] This issue is hardware specific and may or may not be limited to Aruba authentication servers. 1) Attempt to connect / authenticate to a wireless, 802.1x network requiring Protected EAP (or possibly other auth mechanisms). 2) (optionally) Watch SSL traffic between the station and authentication server using wireshark/tcpdump, looking for auth failures and the extensions passed. [Regression Potential] Since this changes the SSL extensions and options used to connect to 802.1x wireless networks; some networks specifically configured to request or make use of the session ticket extension could be made impossible to successfully authenticate to; up to the point where multiple connection failures could lock the accounts used in highly-restricted networks. Also, there is a potential (again, due to the change in SSL options) for other networks (using specific AP hardware) that don't support the extensions used to fail authentication. --- Using identical settings as in 11.10, I am unable to make a wpa enterprise connection using xubuntu precise beta 2. This is a Lenovo X220 with a Centrino Advanced-N 6205 wireless interface. During the attempted logon, I am not presented with a certificate to approve, although wireless instructions for OSX suggest that I should be. However, I never had to approve a certificate when connecting with 11.10 -- I just ignored the certificate screen and everything worked. This seems like the relevant excerpt from syslog: Mar 30 10:39:01 fin8344m2 wpa_supplicant[1116]: Trying to associate with 00:11:92:3e:79:80 (SSID='Northwestern' freq=2462 MHz) Mar 30 10:39:01 fin8344m2 NetworkManager[848]: (wlan0): supplicant interface state: scanning -> associating Mar 30 10:39:01 fin8344m2 kernel: [ 2201.940422] wlan0: authenticated Mar 30 10:39:01 fin8344m2 kernel: [ 2201.940974] wlan0: associate with 00:11:92:3e:79:80 (try 1) Mar 30 10:39:01 fin8344m2 kernel: [ 2201.943165] wlan0: RX ReassocResp from 00:11:92:3e:79:80 (capab=0x431 status=0 aid=222) Mar 30 10:39:01 fin8344m2 kernel: [ 2201.943174] wlan0: associated Mar 30 10:39:01 fin8344m2 wpa_supplicant[1116]: Associated with 00:11:92:3e:79:80 Mar 30 10:39:01 fin8344m2 wpa_supplicant[1116]: CTRL-EVENT-EAP-STARTED EAP authentication started Mar 30 10:39:01 fin8344m2 NetworkManager[848]: (wlan0): supplicant interface state: associating -> associated Mar 30 10:39:01 fin8344m2 wpa_supplicant[1116]: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=25 Mar 30 10:39:01 fin8344m2 wpa_supplicant[1116]: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected Mar 30 10:39:01 fin8344m2 wpa_supplicant[1116]: SSL: SSL3 alert: read (remote end reported an error):fatal:bad certificate Mar 30 10:39:01 fin8344m2 wpa_supplicant[1116]: OpenSSL: openssl_handshake - SSL_connect error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate Mar 30 10:39:01 fin8344m2 wpa_supplicant[1116]: CTRL-EVENT-EAP-FAILURE EAP authentication failed Mar 30 10:39:01 fin8344m2 kernel: [ 2201.969742] wlan0: deauthenticated from 00:11:92:3e:79:80 (Reason: 23) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 2.0-0ubuntu1 Architecture: amd64 Date: Fri Mar 30 10:34:13 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnvi
[Touch-packages] [Bug 1353951] Re: gnome online accounts require autentication on startup
@Felix - are you having problems with the -proposed package like yazid describes? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1353951 Title: gnome online accounts require autentication on startup Status in Evolution Data Server: Fix Released Status in “evolution-data-server” package in Ubuntu: Fix Released Status in “gnome-online-accounts” package in Ubuntu: Invalid Status in “evolution-data-server” source package in Trusty: Fix Committed Status in “gnome-online-accounts” source package in Trusty: Invalid Bug description: [Impact] Google calendar integration is broken, and users are requested to re-enter their Google password everytime they log in, or everytime they enable/disable their Google account from the System Settings. [Test Case] 1) open gnome-online-accounts 2) click + and add a google account 3) enter user name and password 4) confirm permissions for gnome 5) Black window pops up and asks for google password, but does not accept the correct password. Google Contacts are not available in Gnome or Thunderbird [Regression Potential] Minimal: the fix is a backport of a patch from the evolution-data-server code which is already in 14.10, and which only touches the calendar code (which is currently broken). Gnome online accounts requires autentication on startup, but even typing the correct password in the box, the program says the password is wrong. By the way evolution and other programs work well with online accounts. I'm using Ubuntu-gnome 14.04 LTS 64bit on different machines and have the same behaviour. Just to be clear: online-accounts works well, just at startup it opens an "administration" window where it requires to insert the password for my google accounts; if I type the correct password it says that the password is wrong, the only way to close the window is to click on "discard" and then all works well. To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-data-server/+bug/1353951/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
