After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 781015 - Provide terminal with flatpak-builder --run enviroment for debugging with gdb or other tasks
Provide terminal with flatpak-builder --run enviroment for debugging with gdb...
Status: RESOLVED OBSOLETE
Product: gnome-builder
Classification: Other
Component: general
3.23.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME Builder Maintainers
GNOME Builder Maintainers
Depends on:
Blocks: 781010
 
 
Reported: 2017-04-07 08:46 UTC by Carlos Soriano
Modified: 2018-01-11 10:25 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Carlos Soriano 2017-04-07 08:46:27 UTC 
Although there is plans to have debugger and different tools to not need the terminal, there is always going to be a case that we need the terminal for some tasks, and even more in this first stage of development of Flatpak integration.

For that, would be good to have a way to go directly to the run environment of the app, instead of finding where the builddir is (i.e. ~/.cache/gnome-builder/flatpak/staging/Nautilus/flatpak:org.gnome.Platform-x86_64-master) and doing 
$ flatpak-builder --run ~/.cache/gnome-builder/flatpak/staging/nautilus/flatpak:org.gnome.Platform-x86_64-master ~/Projects/Nautilus/org.gnome.Nautilus.json sh
manually to be able to run gdb or other tools with the binary.

This is important for newcomers initiative, not much for them, but for us to be able to give them a way to shortcome the missing functionality, debug, gotchas and other issues we will (fairly) find on the upcoming months.
Comment 1 Christian Hergert 2017-04-07 09:17:31 UTC 
Nightly and the stable branch (gnome-3-24) should both be using flatpak-builder --run now.

However, you will probably still need to export DISPLAY=:0 when using ctrl+alt+shift+t until we have another solution.
Comment 2 Carlos Soriano 2017-04-07 11:41:26 UTC 
I just tried and I have the same issues as before (not being able to access some host system folders or others issues). FWIW as mentioned I can run manually:
$ flatpak-builder --run ~/.cache/gnome-builder/flatpak/staging/nautilus/flatpak:org.gnome.Platform-x86_64-master ~/Projects/Nautilus/org.gnome.Nautilus.json sh
In a regular terminal inside builder and it just works.
However the ctrl+shift+alt+t doesn't behave in this way for some reason, and it causes the permission issues.
Comment 3 GNOME Infrastructure Team 2018-01-11 10:25:08 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-builder/issues/213.