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 780683 - Build application doesn't correspond to the ran application
Build application doesn't correspond to the ran application
Status: RESOLVED OBSOLETE
Product: gnome-builder
Classification: Other
Component: general
3.24.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME Builder Maintainers
GNOME Builder Maintainers
Depends on:
Blocks: 781010
 
 
Reported: 2017-03-29 13:58 UTC by Carlos Soriano
Modified: 2018-01-11 10:24 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Carlos Soriano 2017-03-29 13:58:34 UTC 
Pressing the play button (with flatpak Nautilus) builds nautilus and then runs the application. However seems for some reason the build application is sometimes not the binary that is ran.

What fixes it is removing ~/.cache/gnome-builder.

I have the feeling is something to do with flatpak installation of the app being wrong and launching an old instance. The process that is launched is definitely from flatpak (looking at the process absolute path).
But not sure how to debug further.
Comment 1 Christian Hergert 2017-03-29 17:16:08 UTC 
One thing to keep in mind is that we run the application without a full path (I think). That should probably be fixed if it is the case, as we should know the installation directory.

So if somehow it got installed in two places ...

If you run Builder nightly with -vvvv you'll get debug+trace information about executed processes, which should give you the information you need.

> flatpak run org.gnome.Builder -vvvv
Comment 2 GNOME Infrastructure Team 2018-01-11 10:24:02 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/208.