[Touch-packages] [Bug 1450568] Re: Requests are not cleared if a client dies unexpectedly and drops from the bus
** Changed in: powerd (Ubuntu) Assignee: (unassigned) = Ricardo Mendoza (ricmm) ** Changed in: powerd (Ubuntu) Status: New = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1450568 Title: Requests are not cleared if a client dies unexpectedly and drops from the bus Status in the base for Ubuntu mobile products: New Status in PowerD: In Progress Status in powerd package in Ubuntu: In Progress Bug description: Power requests (wakelocks) are not released if the owner process unexpectedly exits and drops off the bus. This causes a stale request that holds the device awake, which can result in extreme battery drain. For example, the vibration sensor can unexpectedly die while holding a vibration/alarm lock and at the point the phone would never again suspend. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1450568/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1444937] Re: QML cache gets stale too easily
It really depends on exactly what the problem scenario is. Currently, whenever *any* QML file changes, the whole cache is dropped and rebuilt. This includes SDK and base QML deps, not only files shipped by the app itself. The only case where it is currently not rebuilt is when a provider library changes its QML bindings ABI. For this we are looking into ways to encode library versions on the magic headers of the cache file, although for now considering libraries are only updated on image upgrade, the cache should ensure validity. The only breaking case is when the developer pushes a new QML plugin with different ABI than what the cache was built against. So I guess the question is: What was the scenario/issue that happened which lead to this bug? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1444937 Title: QML cache gets stale too easily Status in qtdeclarative-opensource-src package in Ubuntu: Confirmed Bug description: It's happened many times now that after looking for an issue the source of it ended up to be stale QML cache. We need the cache to be cleared more aggressively, likely on any QML- related package installation. App-specific cache should be (if it's not) cleared on install (or maybe better - removal) and upgrade. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libqt5qml5 5.4.1-1ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic x86_64 ApportVersion: 2.17.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 16 12:25:21 2015 SourcePackage: qtdeclarative-opensource-src SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1444937/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1442166] Re: Calendar alarms rings forever if Low Battery dialog visible
** Branch linked: lp:~ricmm/usensord/vibrate-no-sleep -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1442166 Title: Calendar alarms rings forever if Low Battery dialog visible Status in the base for Ubuntu mobile products: Confirmed Status in indicator-datetime package in Ubuntu: Confirmed Status in usensord package in Ubuntu: Confirmed Bug description: I'm on rtm build 258 on krillin Steps to reproduce: - let battery run down on phone (was sitting unplugged for 1 or 2 days) - in the morning, a calendar alarm starting ringing/vibrating and would not stop - when I looked at the phone, the screen was on and I see the Low Battery dialog - after dismissing the dialog, then I see the notification for the alarm, and only after 5-10 more seconds does the ringing stop Seems like while the Low Battery dialog is displayed it keeps the alarm ringing forever To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1442166/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1437320] Re: Adapt QML Cache patch for Qt 5.5
I'll find some time this week to look at it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1437320 Title: Adapt QML Cache patch for Qt 5.5 Status in qtdeclarative-opensource-src package in Ubuntu: New Bug description: QML cache patch QML-Compilation-unit-caching-and-JIT-changes.patch does not apply against Qt 5.5, and would need adjusting. Bug #1426288 is a bug about upstreaming it so that it wouldn't need to be carried in the first place. More information about Qt 5.5 at https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1437320/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1442166] Re: Calendar alarms rings forever if Low Battery dialog visible
From the description this seems like a different case of the vibration. Does it keep *ringing* literally, or just vibrating? Is it with the screen off? or on. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1442166 Title: Calendar alarms rings forever if Low Battery dialog visible Status in the base for Ubuntu mobile products: Confirmed Status in indicator-datetime package in Ubuntu: New Status in usensord package in Ubuntu: New Bug description: I'm on rtm build 258 on krillin Steps to reproduce: - let battery run down on phone (was sitting unplugged for 1 or 2 days) - in the morning, a calendar alarm starting ringing/vibrating and would not stop - when I looked at the phone, the screen was on and I see the Low Battery dialog - after dismissing the dialog, then I see the notification for the alarm, and only after 5-10 more seconds does the ringing stop Seems like while the Low Battery dialog is displayed it keeps the alarm ringing forever To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1442166/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1419405] Re: indicator-location-service crashed with SIGABRT in internal::ToBackend::exit_module()
** Branch linked: lp:~ricmm/platform-api/no-abort-default-dummy ** Changed in: platform-api (Ubuntu) Assignee: (unassigned) = Ricardo Mendoza (ricmm) ** Changed in: unity8-desktop-session (Ubuntu) Assignee: (unassigned) = Ricardo Mendoza (ricmm) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-location in Ubuntu. https://bugs.launchpad.net/bugs/1419405 Title: indicator-location-service crashed with SIGABRT in internal::ToBackend::exit_module() Status in indicator-location package in Ubuntu: Confirmed Status in platform-api package in Ubuntu: Confirmed Status in unity8-desktop-session package in Ubuntu: New Bug description: :( ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: indicator-location 13.10.0+14.10.20141007-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-12.13-generic 3.18.4 Uname: Linux 3.18.0-12-generic x86_64 ApportVersion: 2.16-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Thu Feb 5 06:11:38 2015 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-location/indicator-location-service InstallationDate: Installed on 2014-10-13 (117 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141012) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-location/indicator-location-service ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/false Signal: 6 SourcePackage: indicator-location StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2 ua_location_service_create_controller () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2 UbuntuAppLocController::UbuntuAppLocController() () SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown Title: indicator-location-service crashed with SIGABRT in ua_location_service_create_controller() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1419405/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1422879] Re: GPS stays active after location data is used by a scope (even after not not using the scopes anymore)
From looking at the unity-scopes-shell code for the location provider, it seems like there is no direct correlation with the client request and the active location lookup service side. The request seems to be continuous and always on, is this is so, then we have a problem as this means the GPS hardware is active and signalling even though the user is not interested in location data at the moment. -- 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/1422879 Title: GPS stays active after location data is used by a scope (even after not not using the scopes anymore) Status in the base for Ubuntu mobile products: Confirmed Status in location-service package in Ubuntu: New Status in unity-scopes-api package in Ubuntu RTM: New Bug description: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 237 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-02-17 17:04:34 version version: 237 version ubuntu: 20150217 version device: 20150216-fe747ac version custom: 20150207-538-29-183 You can easily see if the GPS is active or not by checking the logcat output (running as root). In this case the hardware remains on (consumed by the location-service) after opening a scope such as the weather channel one, and retrieving location. To reproduce: 1 - Reboot the phone; 2 - Open logcat as root: sudo /system/bin/logcat 3 - From today's scope, click on the weather icon (opening the weather channel scopes) 4 - See that the GPS is active and location works as expected 5 - Move away from that scope, and check logcat's output (it will stay active, meaning that the location-service is still active). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1422879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1415472] Re: QML cache prevents the QtCreator profiler (interpreter) from running
** Changed in: qtdeclarative-opensource-src (Ubuntu) Status: New = Confirmed ** Changed in: qtdeclarative-opensource-src (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1415472 Title: QML cache prevents the QtCreator profiler (interpreter) from running Status in the base for Ubuntu mobile products: Confirmed Status in qtdeclarative-opensource-src package in Ubuntu: Confirmed Status in qtdeclarative-opensource-src package in Ubuntu RTM: Confirmed Bug description: When on a device that has the QML cache installed, the visual profiler from QtCreator cannot run as it relies on falling back to interpreter based QML (older, 5.3.1 model) and this does not play ball with the cache. Fix: Disable cache when instruction selection mode requested != QV4 JIT. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1415472/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1415472] Re: QML cache prevents the QtCreator profiler (interpreter) from running
** Changed in: qtdeclarative-opensource-src (Ubuntu) Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1415472 Title: QML cache prevents the QtCreator profiler (interpreter) from running Status in the base for Ubuntu mobile products: Confirmed Status in qtdeclarative-opensource-src package in Ubuntu: Fix Committed Status in qtdeclarative-opensource-src package in Ubuntu RTM: Confirmed Bug description: When on a device that has the QML cache installed, the visual profiler from QtCreator cannot run as it relies on falling back to interpreter based QML (older, 5.3.1 model) and this does not play ball with the cache. Fix: Disable cache when instruction selection mode requested != QV4 JIT. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1415472/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408263] Re: Edge gestures still get lost
No real reason for this mako-only bug to happen comes to mind. My advise is to trace back the event to the source, first by lighting up QtUbuntu's input.cc to spew out all events before pushing them to the client, and also mirclient's input delivery loop to see if it is actively dropping the events somehow. If none of those places show anything, you need to look into the imported Android input stack inside of Mir to make sure it is working, then down to the input device it is. It might be an underlying bug with the Mako input stack itself. -- 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/1408263 Title: Edge gestures still get lost Status in unity8 package in Ubuntu: Triaged Bug description: There are still cases where edge gestures are lost. Over the christmas holidays It happened about 5 times to me (in 2 weeks). Only way to recover is to reboot the phone. It always happened while the phone was in my pocket. When pulling it out of the pocket the edge gestures (launcher and right edge) were gone. This is most likely related to random taps on the screen, maybe in combination with the display toggling on/off. Haven't found a way yet to manually trigger it. Will keep on trying. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1408263/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1402650] Re: 3 seconds delay before sending SIGSTOP (changing apps, suspending phone) seems too much
** Also affects: qtmir Importance: Undecided Status: New ** Branch linked: lp:~ricmm/qtmir/reduce-timeout -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to platform-api in Ubuntu. https://bugs.launchpad.net/bugs/1402650 Title: 3 seconds delay before sending SIGSTOP (changing apps, suspending phone) seems too much Status in Qt integration with the Mir display server: New Status in platform-api package in Ubuntu: New Status in qtmir package in Ubuntu: New Bug description: current build number: 51 device name: mako channel: ubuntu-touch/vivid-proposed last update: 2014-12-11 15:02:13 version version: 51 version ubuntu: 20141211 version device: 20141209 version custom: 20141211 Currently it takes around 3 seconds for the app to get the SIGSTOP signal when the app moves to background (when changing apps, moving to the home scopes, suspending the phone, etc), which is specially annoying if the app has an active audio stream (you can still hear the sound for a few seconds before it stops completely). I know we export signals for the apps to react when they are moved out of focus, but I also believe the platform could react a bit sooner than the current 3 seconds timeouts (in order to improve the user experience for webapps, for example). To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1402650/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1319582] Re: emulator: 'Failed to start RenderThread' after opening/closing applications
** Changed in: android (Ubuntu) Assignee: (unassigned) = Ricardo Mendoza (ricmm) ** Changed in: qtubuntu (Ubuntu) Assignee: (unassigned) = Ricardo Mendoza (ricmm) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1319582 Title: emulator: 'Failed to start RenderThread' after opening/closing applications Status in Mir: Triaged Status in android package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: New Bug description: Using: ubuntu-emulator 0.2+14.10.20140429.1-0ubuntu1 ubuntu-emulator-runtime 20140501-2310-0ubuntu3 Emulator starts fine, but after a few opening/closing apps in a row (a bunch of times, at least 20), emulator gives the 'Failed to start RenderThread' error. At that point the emulator can't do much more, and you need to abort and run it again. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1319582/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380848] Re: Apps and services use large amount of CPU after unity8 resets
*** This bug is a duplicate of bug 1394204 *** https://bugs.launchpad.net/bugs/1394204 ** This bug has been marked a duplicate of bug 1394204 dbus daemon spinning with NM AP properties change event -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1380848 Title: Apps and services use large amount of CPU after unity8 resets Status in Media Hub: In Progress Status in dbus-cpp package in Ubuntu: In Progress Status in media-hub package in Ubuntu: Fix Released Status in media-hub package in Ubuntu RTM: Fix Released Bug description: I noticed that media-hub-service can get into a state where it uses a large amount of CPU. Steps to reproduce 1) Start music-app 2) Play music 3) Pause music 4) Close the music-app 5) $ pkill unity8 (to emulate unity crashing a resetting) Notice that media-hub-service is now using a large amount of CPU, note this [0] is the media-hub.log at the time. The device has to be reset to get the CPU usage back to normal. 0 - http://pastebin.ubuntu.com/8553411/ To manage notifications about this bug go to: https://bugs.launchpad.net/media-hub/+bug/1380848/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1394380] Re: QML cache not regenerated correctly on image update
Olivier and I had a chat already on IRC about this, to sum it up: This situation happens because there was no change in the actual QML files, however an underlying QML plugin did change. In my opinion, this change comes with an ABI break and there was no version bump for it. Had there been a version bump, com.canonical.Oxide would've gone from 1.0 to 1.x and the QML file would've changed, thus wiping the cache. In details, the ABI break is probably a change in the vtable for the plugin. Changing the ordering of property helpers and invokables result in different property IDs in the cache, this breaks the precompiled QML because it expects things in the wrong place. This however is not something we can fully rely on as there will always be situations when an ABI breakage lands in the archive; so I vote to go with ogra's OTA hook for wiping all application caches. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1394380 Title: QML cache not regenerated correctly on image update Status in “android” package in Ubuntu: Invalid Status in “lxc-android-config” package in Ubuntu: Confirmed Status in “lxc-android-config” package in Ubuntu RTM: Confirmed Bug description: image rtm-proposed 166 Multiple problems here, due to the fact that oxide was updated (a new release) and webrowser-app was updated 1) webbrowser-app cache was not updated on the image upgrade in .cache/QML/Apps/webbrowser-app and desktop versions of web pages are displayed until the cache is destroyed or regenerated. Try cnn.com or nytimes.com 2) no webbapps cache is regenerated, so launching of the webapps displays wrong pages (.cache/QML/Apps/*webapps*) due to stale cache. You can try Google Maps for an example. Deleting the cache makes them work again properly. Expected Results: - after image upgrade, either all of the apps should be regenerated smartly, or we should blow away all of the caches to prevent an issue when a library (like oxide) is upgraded and causes an invalid cache. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android/+bug/1394380/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1362469] Re: AppArmor unrequested reply protection generates unallowable denials
Whats the status of this? We might have a serious issue that needs forwarding dbus to 1.8, however we haven't tracked it down to a single commit that we could cherry pick yet. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1362469 Title: AppArmor unrequested reply protection generates unallowable denials Status in “dbus” package in Ubuntu: Triaged Bug description: Starting with utopic's dbus 1.8.6-1ubuntu1 package, the new AppArmor unrequested reply protections can generate some denials that can't easily be allowed in policy. For example, when running a confined pasaffe, you see these denials when starting and closing pasaffe: apparmor=DENIED operation=dbus_error bus=session error_name=org.freedesktop.DBus.Error.UnknownMethod mask=send name=:1.22 pid=4993 profile=/usr/bin/pasaffe peer_pid=3624 peer_profile=unconfined It isn't obvious how to construct an AppArmor D-Bus rule to allow that operation. A bare dbus, rule allows it but that's not acceptable for profiles implementing tight D-Bus confinement. The code that implements unrequested reply protections should be reviewed for issues and, if everything looks good there, investigations into how to allow the operation that triggers the above denial should occur. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1362469/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380848] Re: [TOPBLOCKER] Apps and services use large amount of CPU after unity8 resets
Do you guys have any way to reproduce the dbus-daemon or location- service spinning issues? Due to a fix of mine + tvoss's other branch I can no longer see the media-hub problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1380848 Title: [TOPBLOCKER] Apps and services use large amount of CPU after unity8 resets Status in Media Hub: In Progress Status in “dbus-cpp” package in Ubuntu: New Bug description: I noticed that media-hub-service can get into a state where it uses a large amount of CPU. Steps to reproduce 1) Start music-app 2) Play music 3) Pause music 4) Close the music-app 5) $ pkill unity8 (to emulate unity crashing a resetting) Notice that media-hub-service is now using a large amount of CPU, note this [0] is the media-hub.log at the time. The device has to be reset to get the CPU usage back to normal. 0 - http://pastebin.ubuntu.com/8553411/ To manage notifications about this bug go to: https://bugs.launchpad.net/media-hub/+bug/1380848/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380848] Re: [TOPBLOCKER] Apps and services use large amount of CPU after unity8 resets
** Branch linked: lp:~ricmm/media-hub/use-new-hybris-dead-cb -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1380848 Title: [TOPBLOCKER] Apps and services use large amount of CPU after unity8 resets Status in Media Hub: In Progress Status in “dbus-cpp” package in Ubuntu: New Bug description: I noticed that media-hub-service can get into a state where it uses a large amount of CPU. Steps to reproduce 1) Start music-app 2) Play music 3) Pause music 4) Close the music-app 5) $ pkill unity8 (to emulate unity crashing a resetting) Notice that media-hub-service is now using a large amount of CPU, note this [0] is the media-hub.log at the time. The device has to be reset to get the CPU usage back to normal. 0 - http://pastebin.ubuntu.com/8553411/ To manage notifications about this bug go to: https://bugs.launchpad.net/media-hub/+bug/1380848/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380848] Re: [TOPBLOCKER] Apps and services use large amount of CPU after unity8 resets
** Changed in: media-hub Assignee: Jim Hodapp (jhodapp) = Ricardo Mendoza (ricmm) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1380848 Title: [TOPBLOCKER] Apps and services use large amount of CPU after unity8 resets Status in Media Hub: In Progress Status in “dbus-cpp” package in Ubuntu: New Bug description: I noticed that media-hub-service can get into a state where it uses a large amount of CPU. Steps to reproduce 1) Start music-app 2) Play music 3) Pause music 4) Close the music-app 5) $ pkill unity8 (to emulate unity crashing a resetting) Notice that media-hub-service is now using a large amount of CPU, note this [0] is the media-hub.log at the time. The device has to be reset to get the CPU usage back to normal. 0 - http://pastebin.ubuntu.com/8553411/ To manage notifications about this bug go to: https://bugs.launchpad.net/media-hub/+bug/1380848/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380120] Re: Manage Scopes - All Is Unusable
** Changed in: qtdeclarative-opensource-src (Ubuntu RTM) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1380120 Title: Manage Scopes - All Is Unusable Status in “unity8” package in Ubuntu: Invalid Status in “qtdeclarative-opensource-src” package in Ubuntu RTM: Fix Released Bug description: This only happens when upgraded with deltas: $ ubuntu-device-flash --channel=ubuntu-touch/ubuntu-rtm/14.09-proposed --revision=96 and OTA to r100 Steps: 1. Got to manage scopes 2. Click all Observed: The UI is unusable as in attached picture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1380120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1362658] Re: screen locks while recording video
** Branch linked: lp:~ricmm/media-hub/keep-display-recording-1362658 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libhybris in Ubuntu. https://bugs.launchpad.net/bugs/1362658 Title: screen locks while recording video Status in Media Hub: In Progress Status in “libhybris” package in Ubuntu: New Status in “media-hub” package in Ubuntu: In Progress Bug description: krilling image r9 launch camera app start recording a video after 1 mintute the screen shuts off and the phone locks, which causes recording to stop Expected results: - All screen dimming and locking should be disabled while recording To manage notifications about this bug go to: https://bugs.launchpad.net/media-hub/+bug/1362658/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1379840] Re: corrupted QML cache for messaging app makes it crash at startup
** Changed in: qtdeclarative-opensource-src (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1379840 Title: corrupted QML cache for messaging app makes it crash at startup Status in “qtdeclarative-opensource-src” package in Ubuntu: Fix Released Bug description: This is on krillin image #95 from the 14.09-proposed channel. How I got there: - sent an MMS with a vodafone SIM card - switched off the phone, removed the SIM, inserted a movistar SIM in place, switched the phone back on - unlocked the SIM by entering pin, tapped on the messaging app icon At this point the messaging app failed to start, it crashed reliably at startup. Removing the QML cache under ~/.cache/QML/Apps/messaging- app/ solved the issue. I’m attaching an archive containing the corrupted cache. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: libqt5qml5 5.3.0-3ubuntu13~test1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu5 Architecture: armhf Date: Fri Oct 10 17:45:59 2014 InstallationDate: Installed on 2014-10-10 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141010-030205) SourcePackage: qtdeclarative-opensource-src UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1379840/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380120] Re: Manage Scopes - All Is Unusable
** Changed in: qtdeclarative-opensource-src (Ubuntu RTM) Status: Confirmed = Fix Committed -- 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/1380120 Title: Manage Scopes - All Is Unusable Status in “unity8” package in Ubuntu: Invalid Status in “qtdeclarative-opensource-src” package in Ubuntu RTM: Fix Committed Bug description: This only happens when upgraded with deltas: $ ubuntu-device-flash --channel=ubuntu-touch/ubuntu-rtm/14.09-proposed --revision=96 and OTA to r100 Steps: 1. Got to manage scopes 2. Click all Observed: The UI is unusable as in attached picture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1380120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380120] Re: Manage Scopes - All Is Unusable
Silo 17 will soon have some fresh code to test, it should prevent this issue. -- 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/1380120 Title: Manage Scopes - All Is Unusable Status in “unity8” package in Ubuntu: Invalid Status in “qtdeclarative-opensource-src” package in Ubuntu RTM: Confirmed Bug description: This only happens when upgraded with deltas: $ ubuntu-device-flash --channel=ubuntu-touch/ubuntu-rtm/14.09-proposed --revision=96 and OTA to r100 Steps: 1. Got to manage scopes 2. Click all Observed: The UI is unusable as in attached picture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1380120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1379840] Re: corrupted QML cache for messaging app makes it crash at startup
The issue at hand is a wrong assumption done by the cache loader that if the changes to the source files are minimal, a single recompile of the changed files is enough. This has proven to be not true, instead, a full recompilation needs to happen as the QML meta tree might have changed in ways that could cause weird application behaviour, or outright crashes. The solution is: 1. Invalidate the full cache if any of the source files has been changed, and recompile in full. 2. If an application crashes during startup, wipe its cache to increase stability. ** Changed in: qtdeclarative-opensource-src (Ubuntu) Assignee: (unassigned) = Ricardo Mendoza (ricmm) ** Changed in: qtdeclarative-opensource-src (Ubuntu) Importance: Undecided = Critical ** Changed in: qtdeclarative-opensource-src (Ubuntu) Status: Confirmed = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1379840 Title: corrupted QML cache for messaging app makes it crash at startup Status in “qtdeclarative-opensource-src” package in Ubuntu: In Progress Bug description: This is on krillin image #95 from the 14.09-proposed channel. How I got there: - sent an MMS with a vodafone SIM card - switched off the phone, removed the SIM, inserted a movistar SIM in place, switched the phone back on - unlocked the SIM by entering pin, tapped on the messaging app icon At this point the messaging app failed to start, it crashed reliably at startup. Removing the QML cache under ~/.cache/QML/Apps/messaging- app/ solved the issue. I’m attaching an archive containing the corrupted cache. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: libqt5qml5 5.3.0-3ubuntu13~test1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu5 Architecture: armhf Date: Fri Oct 10 17:45:59 2014 InstallationDate: Installed on 2014-10-10 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141010-030205) SourcePackage: qtdeclarative-opensource-src UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1379840/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376361] [NEW] Need to open up path for cached QML bytecode
Public bug reported:
The upcoming introduction of cacheable QML compilation units require an
application-specific path to store the binaries.
The proposed and accepted path is
$HOME/.cache/QML/Apps/$APP_ID
where $APP_ID = @{APP_PKGNAME}_@{APP_APPNAME}_@{APP_VERSION} for click apps
and simple desktop file name for legacy apps.
** Affects: apparmor-easyprof-ubuntu (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu
in Ubuntu.
https://bugs.launchpad.net/bugs/1376361
Title:
Need to open up path for cached QML bytecode
Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
New
Bug description:
The upcoming introduction of cacheable QML compilation units require
an application-specific path to store the binaries.
The proposed and accepted path is
$HOME/.cache/QML/Apps/$APP_ID
where $APP_ID = @{APP_PKGNAME}_@{APP_APPNAME}_@{APP_VERSION} for click apps
and simple desktop file name for legacy apps.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor-easyprof-ubuntu/+bug/1376361/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
