Add a workaround to get "run on device" with Ctrl+F12 working again

Bug #1291906 reported by David Planella
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu Calculator App
Fix Released
Low
Unassigned
Ubuntu Calendar App
Fix Released
Low
Unassigned
Ubuntu Clock App
Fix Released
Low
Nekhelesh Ramananthan
Ubuntu File Manager App
Fix Released
Low
Unassigned
Ubuntu Music App
Fix Released
Low
Unassigned
Ubuntu Shorts App
Fix Released
Low
Unassigned
Ubuntu Terminal App
Fix Released
Low
Unassigned

Bug Description

After the migration to CMake, the functionality to quickly run an app on the device with Ctrl+F12 got broken because the Qt Creator script expects a .desktop file to be present. With CMake, the .desktop file is only generated at build time from a .desktop.in (or desktop.in.in) file, and since we don't execute any build steps with the script, it is never created and thus the script fails.

After having talked to the SDK guys, my understanding is that there won't be a fix coming any time soon, so I'd recommend to an easy workaround by simply committing a static .desktop file to the code. This way we'll keep the Ctrl+F12 script happy and we'll be able to easily run on device again without any manual steps to generate the .desktop file first.

Tags: bitesize

Related branches

David Planella (dpm)
tags: added: bitesize
Changed in ubuntu-calculator-app:
importance: Undecided → Low
status: New → Triaged
Changed in ubuntu-calendar-app:
status: New → Triaged
Changed in ubuntu-clock-app:
status: New → Triaged
Changed in ubuntu-filemanager-app:
status: New → Triaged
Changed in music-app:
status: New → Triaged
Changed in ubuntu-rssreader-app:
status: New → Triaged
Changed in ubuntu-terminal-app:
status: New → Triaged
Changed in ubuntu-calendar-app:
importance: Undecided → Low
Changed in ubuntu-clock-app:
importance: Undecided → Low
Changed in ubuntu-filemanager-app:
importance: Undecided → Low
Changed in music-app:
importance: Undecided → Low
Changed in ubuntu-rssreader-app:
importance: Undecided → Low
Changed in ubuntu-terminal-app:
importance: Undecided → Low
Revision history for this message
Nicholas Skaggs (nskaggs) wrote :

dpm, why can't qtcreator just reference the new file?

Revision history for this message
David Planella (dpm) wrote : Re: [Bug 1291906] Re: Add a workaround to get "run on device" with Ctrl+F12 working again

On Fri, Mar 14, 2014 at 1:53 AM, Nicholas Skaggs <
<email address hidden>> wrote:

> dpm, why can't qtcreator just reference the new file?
>
>
Can you be more specific? Which new file?

> --
> You received this bug notification because you are subscribed to the bug
> report.
> Matching subscriptions: File Manager App Bugmail, Ubuntu RSS Reader Bugmail
> https://bugs.launchpad.net/bugs/1291906
>
> Title:
> Add a workaround to get "run on device" with Ctrl+F12 working again
>
> Status in Music application for Ubuntu devices:
> Triaged
> Status in Calculator application for Ubuntu devices:
> Triaged
> Status in Calendar application for Ubuntu devices:
> Triaged
> Status in Clock application for Ubuntu devices:
> Triaged
> Status in File Manager application for Ubuntu devices:
> Triaged
> Status in RSS Feed Reader application for Ubuntu devices:
> Triaged
> Status in Terminal application for Ubuntu devices:
> Triaged
>
> Bug description:
> After the migration to CMake, the functionality to quickly run an app
> on the device with Ctrl+F12 got broken because the Qt Creator script
> expects a .desktop file to be present. With CMake, the .desktop file
> is only generated at build time from a .desktop.in (or desktop.in.in)
> file, and since we don't execute any build steps with the script, it
> is never created and thus the script fails.
>
> After having talked to the SDK guys, my understanding is that there
> won't be a fix coming any time soon, so I'd recommend to an easy
> workaround by simply committing a static .desktop file to the code.
> This way we'll keep the Ctrl+F12 script happy and we'll be able to
> easily run on device again without any manual steps to generate the
> .desktop file first.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/music-app/+bug/1291906/+subscriptions
>

Revision history for this message
Nicholas Skaggs (nskaggs) wrote :

Nevermind, I think this approach is fine. Sorry!

Revision history for this message
brian larochelle (larochelle-brian) wrote :

it looks like this may require a change to:
/usr/share/qtcreator/ubuntu/scripts/qtc_device_run_app

likely related to this bug:
https://bugs.launchpad.net/qtcreator-plugin-ubuntu/+bug/1276790
problem and possible solution detailed here:
https://lists.launchpad.net/ubuntu-phone/msg07176.html

i would be willing to contact that sdk team see if i can resolve their bug and then come back to this bug.

please let me know if that sounds acceptable and i'll get started.

Revision history for this message
Nekhelesh Ramananthan (nik90) wrote :

In the old clock app, we have circumvented this issue by committing a static desktop file. Hence marking it as fix released. In the new clock app, that is not required.

Changed in ubuntu-clock-app:
assignee: nobody → Nekhelesh Ramananthan (nik90)
status: Triaged → Fix Committed
status: Fix Committed → Fix Released
Revision history for this message
David Planella (dpm) wrote :

On file manager app, the migration to a CMake project a while ago fixed it, thus closing the task.

Changed in ubuntu-filemanager-app:
status: Triaged → Fix Released
Revision history for this message
Ubuntu Phone Apps Jenkins Bot (ubuntu-phone-apps-jenkins-bot) wrote :

Fix committed into lp:ubuntu-calendar-app at revision 340, scheduled for release in ubuntu-calendar-app, milestone alpha-1

Changed in ubuntu-calendar-app:
status: Triaged → Fix Committed
Changed in ubuntu-calendar-app:
status: Fix Committed → Fix Released
David Planella (dpm)
Changed in music-app:
status: Triaged → Fix Released
Changed in ubuntu-rssreader-app:
status: Triaged → Fix Released
Changed in ubuntu-terminal-app:
status: Triaged → Fix Released
Changed in ubuntu-calculator-app:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.