gnome-builder issueshttps://gitlab.gnome.org/GNOME/gnome-builder/-/issues2024-01-25T23:51:59Zhttps://gitlab.gnome.org/GNOME/gnome-builder/-/issues/2106Vim mode Broken in Gnome-Builder 44.22024-01-25T23:51:59ZChris HalbersmaVim mode Broken in Gnome-Builder 44.2# Affected version
- Nightly installed via Flatpak
- 44.2 Installed From Flathub
# Steps to reproduce
1. Enable Vim mode in Preferences -> Plugins -> Keyboard Shortcuts
2. Observe Vim Keybindings Dont' Work
# Expected behavior
1. Enabl...# Affected version
- Nightly installed via Flatpak
- 44.2 Installed From Flathub
# Steps to reproduce
1. Enable Vim mode in Preferences -> Plugins -> Keyboard Shortcuts
2. Observe Vim Keybindings Dont' Work
# Expected behavior
1. Enable Vim mode in Preferences -> Plugins -> Keyboard Shortcuts
2. Vim Keybindings Workhttps://gitlab.gnome.org/GNOME/gnome-builder/-/issues/2041Black bar over code2023-05-09T00:01:22ZDiamond WhiteBlack bar over code<!--
Please test if the issue has already been fixed in the Nightly version.
You can install the Nightly version in parallel with the regular version with these instructions:
1. Make sure that Flatpak is installed (see http...<!--
Please test if the issue has already been fixed in the Nightly version.
You can install the Nightly version in parallel with the regular version with these instructions:
1. Make sure that Flatpak is installed (see https://flatpak.org/setup )
2. Copy and run the following command in a Terminal:
flatpak install --user --from https://nightly.gnome.org/repo/appstream/org.gnome.Builder.flatpakref
3) The Nightly version can now be launched from Activities, or with this command: flatpak run org.gnome.Builder.Devel
-->
# Affected version
- Nightly flatpak: Yes
# Steps to reproduce
open any file or project
# Current behavior
There is a black line near the file navigation bar which does not allow you to select text under it and disrupts the ui
# Expected behavior
The line shouldn't be there
# Additional information
![image](/uploads/9ba4575393e614357a8148c7e0dae710/image.png)
This is not an issue with my theme as it is also present with the default adwaita theme. This issue only started when I update to gnome 44 on arch
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/1978paths opened from debugger are escaped2023-02-03T19:11:23Ztwopaths opened from debugger are escaped# Affected version
- Nightly flatpak: Can't test it because #1977
- Other: flathub stable
# Steps to reproduce
<!--
Explain in detail the steps on how the issue can be reproduced.
-->
1. build a flatpak
2. start it with debugger
3....# Affected version
- Nightly flatpak: Can't test it because #1977
- Other: flathub stable
# Steps to reproduce
<!--
Explain in detail the steps on how the issue can be reproduced.
-->
1. build a flatpak
2. start it with debugger
3. pause the program
4. click on a function in the project (not from a submodule!) in the stack trace
# Current behavior
Builder tries to open the file path with each byte octal escaped, e.g. `\320`, which opens an empty document because such file doesn't exist
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/1926Clone Repository window can't be maximized depending on the screen resolution2023-02-05T01:57:59ZGhost UserClone Repository window can't be maximized depending on the screen resolution<!--
Please test if the issue has already been fixed in the Nightly version.
You can install the Nightly version in parallel with the regular version with these instructions:
1. Make sure that Flatpak is installed (see http...<!--
Please test if the issue has already been fixed in the Nightly version.
You can install the Nightly version in parallel with the regular version with these instructions:
1. Make sure that Flatpak is installed (see https://flatpak.org/setup )
2. Copy and run the following command in a Terminal:
flatpak install --user --from https://nightly.gnome.org/repo/appstream/org.gnome.Builder.flatpakref
3) The Nightly version can now be launched from Activities, or with this command: flatpak run org.gnome.Builder.Devel
-->
# Affected version
- Nightly flatpak: Issue also happens
- Other: 43.3 (flatpak)
# Steps to reproduce
<!--
Explain in detail the steps on how the issue can be reproduced.
-->
1. Start a VM (I used Boxes), without using the fullscreen feature
2. Open Builder > Clone Repository
# Current behavior
The window won't maximize. After making the Boxes window fullscreen, I can maximize the clone repository window. I guess people with 1280x720 displays might facing this bug, then.
![Screencast_from_2022-12-02_20-18-32](/uploads/ef9bebd6435ba0557c9fdd098248f32b/Screencast_from_2022-12-02_20-18-32.webm)
# Expected behavior
The window maximizing.
# Additional information
N/A
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/1852Cursor becoming invisible after Color Scheme change2022-10-11T12:18:31ZNils MartelCursor becoming invisible after Color Scheme change
- Other: Fedora OS
Don't really know how to get more information or how to install nightly, my software application is stuck
# Steps to reproduce
- 0.) Set light theme
- 1.) Enable vim mode
- 2.) Place cursor in some textfile
- 3.) Se...
- Other: Fedora OS
Don't really know how to get more information or how to install nightly, my software application is stuck
# Steps to reproduce
- 0.) Set light theme
- 1.) Enable vim mode
- 2.) Place cursor in some textfile
- 3.) Set dark theme
# Current behavior
The cursor is now gone
# Expected behavior
The beloved cursor is visible
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/1833Default build config using cmake cannot find libraries2022-10-01T20:01:40ZMarc barbierDefault build config using cmake cannot find libraries# Affected version
- Nightly flatpak: Yes
# Steps to reproduce
1. Create a cmake project with "pkg_search_module(audit REQUIRED libaudit)"
2. set the environment to system.
3. try to build
# Current behavior
it errors out
```
-- Checki...# Affected version
- Nightly flatpak: Yes
# Steps to reproduce
1. Create a cmake project with "pkg_search_module(audit REQUIRED libaudit)"
2. set the environment to system.
3. try to build
# Current behavior
it errors out
```
-- Checking for one of the modules 'libaudit'
CMake Error at /usr/share/cmake/Modules/FindPkgConfig.cmake:894 (message):
None of the required 'libaudit' found
Call Stack (most recent call first):
```
# Expected behavior
it should compile properly
# Additional information
I'm running Arch Linux, and I'm using the nightly flatpak.
The project build perfectly using the terminal integrated in builder.
<!-- Ignore the text under this line. -->https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/1634Builder is unable to run some GUI software from its integrated terminal2022-06-02T06:32:36ZNewbyteBuilder is unable to run some GUI software from its integrated terminalI'm using GNOME Builder from GNOME's nightly repo, and some GUI software I try to invoke from the built-in terminal crashes. This includes things like GNOME's keyring popups, so I can't sign my commits and pushing via ssh falls back to a...I'm using GNOME Builder from GNOME's nightly repo, and some GUI software I try to invoke from the built-in terminal crashes. This includes things like GNOME's keyring popups, so I can't sign my commits and pushing via ssh falls back to a CLI password prompt. Thunderbird gives a particularly interesting error:
$ flatpak run org.mozilla.Thunderbird
Error: no DISPLAY environment variable specified
However, some things work. Examples of working programs include supertux2 and Nautilus. Also worth noting is that everything here works if I launch it from e.g. GNOME Terminal instead.
This issue has been around for a while and I'm not sure when it started.
Relevant software versions:
- Host OS: Fedora 35 Workstation (last updated yesterday)
- GNOME Builder version: 42.alpha1 (42.alpha1-102-gbe074e3ea) flatpak-nightly (all permissions set to their default values)
- Mutter version: 41.4 (Wayland session)
- NVIDIA GPU driver: 510.47.03 (in case this would be relevant)https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/1576Enable Rust support by adding extension to manifest2021-12-07T23:24:55ZMurmeleEnable Rust support by adding extension to manifestAt the moment Rust Extension is not added to the manifest, because of that, rust is not supported correctly.
Would be nice to add the Rust Extension:
sdk-extensions: org.freedesktop.Sdk.Extension.rust-stableAt the moment Rust Extension is not added to the manifest, because of that, rust is not supported correctly.
Would be nice to add the Rust Extension:
sdk-extensions: org.freedesktop.Sdk.Extension.rust-stablehttps://gitlab.gnome.org/GNOME/gnome-builder/-/issues/1455Rust Analyzer doesn't work anymore with Builder nightly2021-05-16T19:43:44ZFelix Häckerhaeckerfelix@gnome.orgRust Analyzer doesn't work anymore with Builder nightlyWith Builder nightly the rust-analyzer integration doesn't work anymore. I don't see a `rust-analyzer` process running.
Project configuration:
```
{
"app-id": "de.haeckerfelix.Fragments.Devel",
"runtime": "org.gnome.Platform",
...With Builder nightly the rust-analyzer integration doesn't work anymore. I don't see a `rust-analyzer` process running.
Project configuration:
```
{
"app-id": "de.haeckerfelix.Fragments.Devel",
"runtime": "org.gnome.Platform",
"runtime-version": "40",
"sdk": "org.gnome.Sdk",
"sdk-extensions" : [
"org.freedesktop.Sdk.Extension.rust-stable"
],
"command": "fragments",
"tags" : [
"nightly"
],
```
Builder version
```
41.alpha
(3.40.0-125-ge4e9db33a+)
flatpak-nightly
```
I wasn't able to test if that issue also applies to the current stable build, since https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/1448 prevents me to build Rust projects entirely.
Logs
[gnome-builder-2.log](/uploads/a76bc9c9f512ae10d25f37fd6a53baa9/gnome-builder-2.log)
[verbose_logs](/uploads/e96169a8392fc86cde6917da077524ce/verbose_logs)https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/1446Crash on pressing Export Bundle2022-11-13T00:06:38ZIvan Molodetskikhyalterz@gmail.comCrash on pressing Export Bundle```
Program terminated with signal SIGSEGV, Segmentation fault.
#0 g_cancellable_is_cancelled (cancellable=<optimized out>, cancellable=<optimized out>) at ../gio/gcancellable.c:297
297 return cancellable != NULL && g_atomic_int_get (...```
Program terminated with signal SIGSEGV, Segmentation fault.
#0 g_cancellable_is_cancelled (cancellable=<optimized out>, cancellable=<optimized out>) at ../gio/gcancellable.c:297
297 return cancellable != NULL && g_atomic_int_get (&cancellable->priv->cancelled);
[Current thread is 1 (Thread 0x7f6709bc6d00 (LWP 2))]
(gdb) bt
#0 g_cancellable_is_cancelled (cancellable=<optimized out>, cancellable=<optimized out>) at ../gio/gcancellable.c:297
#1 g_cancellable_is_cancelled (cancellable=0x75422f7070632f65) at ../gio/gcancellable.c:295
#2 0x00007f6714e284db in g_cancellable_cancel (cancellable=0x75422f7070632f65) at ../gio/gcancellable.c:491
#3 0x000055a16b00dfb6 in ide_subprocess_communicate_cancelled (user_data=<optimized out>) at ../src/libide/threading/ide-flatpak-subprocess.c:676
#4 0x00007f6714c8fe1f in g_main_dispatch (context=0x55a16db62160) at ../glib/gmain.c:3337
#5 g_main_context_dispatch (context=0x55a16db62160) at ../glib/gmain.c:4055
#6 0x00007f6714c901c8 in g_main_context_iterate (context=context@entry=0x55a16db62160, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/gmain.c:4131
#7 0x00007f6714c90293 in g_main_context_iteration (context=context@entry=0x55a16db62160, may_block=may_block@entry=1) at ../glib/gmain.c:4196
#8 0x00007f6714eba66d in g_application_run (application=0x55a16db1a120 [IdeApplication], argc=2001850708, argv=<optimized out>) at ../gio/gapplication.c:2560
#9 0x000055a16af0102d in main (argc=<optimized out>, argv=<optimized out>) at ../src/main.c:296
(gdb) bt full
#0 g_cancellable_is_cancelled (cancellable=<optimized out>, cancellable=<optimized out>) at ../gio/gcancellable.c:297
#1 g_cancellable_is_cancelled (cancellable=0x75422f7070632f65) at ../gio/gcancellable.c:295
#2 0x00007f6714e284db in g_cancellable_cancel (cancellable=0x75422f7070632f65) at ../gio/gcancellable.c:491
priv = <optimized out>
#3 0x000055a16b00dfb6 in ide_subprocess_communicate_cancelled (user_data=<optimized out>) at ../src/libide/threading/ide-flatpak-subprocess.c:676
state = <optimized out>
#4 0x00007f6714c8fe1f in g_main_dispatch (context=0x55a16db62160) at ../glib/gmain.c:3337
dispatch = 0x7f6714e27ce0 <cancellable_source_dispatch>
prev_source = 0x0
begin_time_nsec = 0
was_in_call = 0
user_data = 0x55a16edf85f0
callback = 0x55a16b00dfa0 <ide_subprocess_communicate_cancelled>
cb_funcs = <optimized out>
cb_data = 0x55a16e81b5e0
need_destroy = <optimized out>
source = 0x55a16e9ef080
current = 0x55a16db00ad0
i = 2
__func__ = "g_main_dispatch"
#5 g_main_context_dispatch (context=0x55a16db62160) at ../glib/gmain.c:4055
#6 0x00007f6714c901c8 in g_main_context_iterate (context=context@entry=0x55a16db62160, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/gmain.c:4131
max_priority = 0
timeout = 0
some_ready = 1
nfds = <optimized out>
allocated_nfds = <optimized out>
fds = 0x55a16e962660
#7 0x00007f6714c90293 in g_main_context_iteration (context=context@entry=0x55a16db62160, may_block=may_block@entry=1) at ../glib/gmain.c:4196
retval = <optimized out>
#8 0x00007f6714eba66d in g_application_run (application=0x55a16db1a120 [IdeApplication], argc=2001850708, argv=<optimized out>) at ../gio/gapplication.c:2560
arguments = 0x55a16dbe45a0
status = 0
context = 0x55a16db62160
acquired_context = <optimized out>
__func__ = "g_application_run"
#9 0x000055a16af0102d in main (argc=<optimized out>, argv=<optimized out>) at ../src/main.c:296
plugin = 0x0
type = 0x0
dbus_address = 0x0
app = 0x55a16db1a120 [IdeApplication]
desktop = 0x7fff7751ec24 "GNOME"
standalone = 0
ret = <optimized out>
```
F34 Silverblue, Builder 40 from Flathub.
```
Commit: f77c46ff9fa1e8104d0d29a1c8ec1aa71ebf5a7e4961facadf8ab88a4f6df50a
Parent: 9a2a2b1a1d2d6f3db459877ff2a4c400b06e20235f8e9e4ee38129958b92d55c
Subject: fix null dereference (7f5e479a)
Date: 2021-04-25 00:11:08 +0000
```https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/1445Rust GTK4 Gnome app template doesn't compile2021-04-27T10:50:16ZMek101mek101-dev.inv@slmail.meRust GTK4 Gnome app template doesn't compileReporting a different error than #1370
I created a new Rust GTK4 Gnome application using Builder's wizard. Attempting to compile it, without changing anything fails with this cli:
```
Creating directory “/home/mek101/.var/app/org.gnom...Reporting a different error than #1370
I created a new Rust GTK4 Gnome application using Builder's wizard. Attempting to compile it, without changing anything fails with this cli:
```
Creating directory “/home/mek101/.var/app/org.gnome.Builder/cache/gnome-builder/projects/Flatpak_GTK4_test_app/flatpak/repo”
Creating directory “/home/mek101/.var/app/org.gnome.Builder/cache/gnome-builder/projects/Flatpak_GTK4_test_app/flatpak/staging/x86_64-master”
flatpak build-init --arch=x86_64 /home/mek101/.var/app/org.gnome.Builder/cache/gnome-builder/projects/Flatpak_GTK4_test_app/flatpak/staging/x86_64-master org.codeberg.mek101.FlatpakGtk4Test org.gnome.Sdk org.gnome.Platform 40
flatpak-builder --arch=x86_64 --ccache --force-clean --state-dir /home/mek101/.var/app/org.gnome.Builder/cache/gnome-builder/flatpak-builder --download-only --disable-updates --stop-at=flatpak_gtk4_test_app /home/mek101/.var/app/org.gnome.Builder/cache/gnome-builder/projects/Flatpak_GTK4_test_app/flatpak/staging/x86_64-master /drives/linux_data/mek101/Progetti/Programmazione/Flatpak_GTK4_test_app/org.codeberg.mek101.FlatpakGtk4Test.json
Emptying app dir '/home/mek101/.var/app/org.gnome.Builder/cache/gnome-builder/projects/Flatpak_GTK4_test_app/flatpak/staging/x86_64-master'
Downloading sources
Stopping at module flatpak_gtk4_test_app
flatpak-builder --arch=x86_64 --ccache --force-clean --disable-updates --disable-download --state-dir /home/mek101/.var/app/org.gnome.Builder/cache/gnome-builder/flatpak-builder --stop-at=flatpak_gtk4_test_app /home/mek101/.var/app/org.gnome.Builder/cache/gnome-builder/projects/Flatpak_GTK4_test_app/flatpak/staging/x86_64-master /drives/linux_data/mek101/Progetti/Programmazione/Flatpak_GTK4_test_app/org.codeberg.mek101.FlatpakGtk4Test.json
Error opening cache: opening repo: opendir(objects): File o directory non esistente
```
(the last line translates to "File or directory doesn't exist")
Installed from flatpak, flathub stable repo. Version 3.40.0https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/1390Uncomment shortcut not working.2022-11-13T00:11:09ZPavanUncomment shortcut not working.* OS: ArchLinux
* Package: [Link](https://archlinux.org/packages/extra/x86_64/gnome-builder/)
* Issue: I wanted to try this editor, I downloaded and opened up a C++ source file. Quickly looked at shortcuts and `<Ctrl-m>` makes the line c...* OS: ArchLinux
* Package: [Link](https://archlinux.org/packages/extra/x86_64/gnome-builder/)
* Issue: I wanted to try this editor, I downloaded and opened up a C++ source file. Quickly looked at shortcuts and `<Ctrl-m>` makes the line commented and `<Shift-Ctrl-m>` does the inverse. But it seems the inverse operation working.https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/1069GNOME Builder 3.34.1 Hangs when I select a Comic Mono font.2019-11-06T09:03:37ZBruce BigbyGNOME Builder 3.34.1 Hangs when I select a Comic Mono font.GNOME Builder 3.34.1 on Fedora 31 hangs when I select the font, Comic Mono, while within a project. It is a True Type font. The interface becomes unusable and Builder is unable to accept any input so I have to pkill it. After restartin...GNOME Builder 3.34.1 on Fedora 31 hangs when I select the font, Comic Mono, while within a project. It is a True Type font. The interface becomes unusable and Builder is unable to accept any input so I have to pkill it. After restarting, the font is still Comic Mono, and everything is fine until I actually open a project; it becomes unresponsive. Other applications like Atom, Eclipse, Gnome Shell, VSCode, etc., handle the font just fine, but for some reason, GNOME Builder doesn't. I obtained the font from here:
https://dtinth.github.io/comic-mono-font/
[ComicMono.ttf](/uploads/fae01fc62ca70d5d0efbd4a822ad95b0/ComicMono.ttf)https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/1010GNOME GJS Example Application does not run2021-02-06T17:39:03ZBastian Ilsø Hougaardbastianilso@gnome.orgGNOME GJS Example Application does not runWhen I try to create a GNOME GJS Example Application and run it from Builder, I get the following error below. Running/Creating the GNOME C Application works fine.
```
Application started at 12:09:18
bwrap: execvp com.bastianilso.Podium...When I try to create a GNOME GJS Example Application and run it from Builder, I get the following error below. Running/Creating the GNOME C Application works fine.
```
Application started at 12:09:18
bwrap: execvp com.bastianilso.Podium: No such file or directory
Application exited
```
This is the output from the build process:
```
Creating directory “/home/bastian/.var/app/org.gnome.Builder/cache/gnome-builder/projects/Podium/flatpak/repo”
Creating directory “/home/bastian/.var/app/org.gnome.Builder/cache/gnome-builder/projects/Podium/flatpak/staging/x86_64-master”
flatpak build-init --arch=x86_64 /home/bastian/.var/app/org.gnome.Builder/cache/gnome-builder/projects/Podium/flatpak/staging/x86_64-master com.bastianilso.Podium org.gnome.Sdk org.gnome.Platform 3.32
flatpak-builder --arch=x86_64 --ccache --force-clean --state-dir /home/bastian/.var/app/org.gnome.Builder/cache/gnome-builder/flatpak-builder --download-only --disable-updates --stop-at=podium /home/bastian/.var/app/org.gnome.Builder/cache/gnome-builder/projects/Podium/flatpak/staging/x86_64-master '/home/bastian/Sync/Croquis app/Podium/com.bastianilso.Podium.json'
Emptying app dir '/home/bastian/.var/app/org.gnome.Builder/cache/gnome-builder/projects/Podium/flatpak/staging/x86_64-master'
Downloading sources
Stopping at module podium
flatpak-builder --arch=x86_64 --ccache --force-clean --disable-updates --disable-download --state-dir /home/bastian/.var/app/org.gnome.Builder/cache/gnome-builder/flatpak-builder --stop-at=podium /home/bastian/.var/app/org.gnome.Builder/cache/gnome-builder/projects/Podium/flatpak/staging/x86_64-master '/home/bastian/Sync/Croquis app/Podium/com.bastianilso.Podium.json'
Initializing build dir
Committing stage init to cache
Starting build of com.bastianilso.Podium
Stopping at module podium
Pruning cache
flatpak build-init --arch=x86_64 /home/bastian/.var/app/org.gnome.Builder/cache/gnome-builder/projects/Podium/flatpak/staging/x86_64-master com.bastianilso.Podium org.gnome.Sdk org.gnome.Platform 3.32
sh -c 'git submodule init && git submodule update'
flatpak-builder --arch=x86_64 --ccache --force-clean --state-dir /home/bastian/.var/app/org.gnome.Builder/cache/gnome-builder/flatpak-builder --download-only --stop-at=podium /home/bastian/.var/app/org.gnome.Builder/cache/gnome-builder/projects/Podium/flatpak/staging/x86_64-master '/home/bastian/Sync/Croquis app/Podium/com.bastianilso.Podium.json'
Emptying app dir '/home/bastian/.var/app/org.gnome.Builder/cache/gnome-builder/projects/Podium/flatpak/staging/x86_64-master'
Downloading sources
Stopping at module podium
flatpak-builder --arch=x86_64 --ccache --force-clean --disable-updates --disable-download --state-dir /home/bastian/.var/app/org.gnome.Builder/cache/gnome-builder/flatpak-builder --stop-at=podium /home/bastian/.var/app/org.gnome.Builder/cache/gnome-builder/projects/Podium/flatpak/staging/x86_64-master '/home/bastian/Sync/Croquis app/Podium/com.bastianilso.Podium.json'
Starting build of com.bastianilso.Podium
Stopping at module podium
Everything cached, checking out from cache
Pruning cache
flatpak build-init --arch=x86_64 /home/bastian/.var/app/org.gnome.Builder/cache/gnome-builder/projects/Podium/flatpak/staging/x86_64-master com.bastianilso.Podium org.gnome.Sdk org.gnome.Platform 3.32
flatpak-builder --arch=x86_64 --ccache --force-clean --state-dir /home/bastian/.var/app/org.gnome.Builder/cache/gnome-builder/flatpak-builder --download-only --stop-at=podium /home/bastian/.var/app/org.gnome.Builder/cache/gnome-builder/projects/Podium/flatpak/staging/x86_64-master '/home/bastian/Sync/Croquis app/Podium/com.bastianilso.Podium.json'
Emptying app dir '/home/bastian/.var/app/org.gnome.Builder/cache/gnome-builder/projects/Podium/flatpak/staging/x86_64-master'
Downloading sources
Stopping at module podium
flatpak-builder --arch=x86_64 --ccache --force-clean --disable-updates --disable-download --state-dir /home/bastian/.var/app/org.gnome.Builder/cache/gnome-builder/flatpak-builder --stop-at=podium /home/bastian/.var/app/org.gnome.Builder/cache/gnome-builder/projects/Podium/flatpak/staging/x86_64-master '/home/bastian/Sync/Croquis app/Podium/com.bastianilso.Podium.json'
Starting build of com.bastianilso.Podium
Stopping at module podium
Everything cached, checking out from cache
Pruning cache
```https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/955Builder crashes when entering meson configure options2019-07-26T03:16:19ZTimur KristófBuilder crashes when entering meson configure options1. Open mesa with builder
2. Go to build preferences
3. Enter any meson configure options, either a short one like `-Dbuildtype=debug` or a full one, for example: `-Ddri-drivers= -Dgallium-drivers=radeonsi,swrast,iris -Dvulkan-drivers=in...1. Open mesa with builder
2. Go to build preferences
3. Enter any meson configure options, either a short one like `-Dbuildtype=debug` or a full one, for example: `-Ddri-drivers= -Dgallium-drivers=radeonsi,swrast,iris -Dvulkan-drivers=intel,amd -Dgallium-nine=true -Dosmesa=gallium -Dtools=nir -Dbuildtype=debug`
Then it crashes.
Interestingly enough, the crash only happens when launching Builder from the UI (gnome-shell) but doesn't happen if `gnome-builder` is started from the terminal.https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/875Builder 3.32 from Flatpak doesn't respect .editorconfig2022-11-12T23:51:34ZGNBuilder 3.32 from Flatpak doesn't respect .editorconfigFor instance I have a default of `indent_style = space`, but a new (unsaved) document defaults to tabs, and for YAML I have `indent_size = 2`, but Builder uses 4 spaces.
Builder 3.28 via RPM picks up `.editorconfig` settings correctly.For instance I have a default of `indent_style = space`, but a new (unsaved) document defaults to tabs, and for YAML I have `indent_size = 2`, but Builder uses 4 spaces.
Builder 3.28 via RPM picks up `.editorconfig` settings correctly.https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/828Crashes when opening a second instance2019-02-25T23:53:06ZFrank BrüttingCrashes when opening a second instance`3.31.91 flatpak-nightly`
* Builder first always crashed when I opened up a second instance (i.e. when I middle-click on the dock icon). Didn’t happen a few days ago!
* Then, after a few tries, it crashed when clicking on a project in t...`3.31.91 flatpak-nightly`
* Builder first always crashed when I opened up a second instance (i.e. when I middle-click on the dock icon). Didn’t happen a few days ago!
* Then, after a few tries, it crashed when clicking on a project in the second instance’s project chooser.
* Then, after two more tries, I can open multiple instances, but there sometimes is a bigger lag when I open a project.
Attached find the console log.
[log](/uploads/c1452891ecb2509686fec981335c63b8/log)https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/611Build log file is incomplete2018-09-04T18:38:02ZSteve PricksBuild log file is incomplete**How to reproduce:**
1. Build a project and watch the output in Builder's terminal window.
2. In the end click the 'Save build log' button to write the whole build log to a file.
3. Open the file and check its content.
**Expected resu...**How to reproduce:**
1. Build a project and watch the output in Builder's terminal window.
2. In the end click the 'Save build log' button to write the whole build log to a file.
3. Open the file and check its content.
**Expected result:**
The file contains the whole terminal output of the build. This allows the user for instance to see the configure output from the beginning of the build process.
**Actual result:**
The file only contains the last lines of the output, i.e. the same lines that are shown in Builder's terminal window. The user is not able to see earlier output.
**Version:**
Builder 3.28.4 (flatpak) on Linux Mint 19https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/577Java snippets make Builder to crash2020-01-14T19:49:28ZRicardo Silva VelosoJava snippets make Builder to crashTwo snippets make Builder to crash: `clas` and `iface`, because of formatters in `package` line.Two snippets make Builder to crash: `clas` and `iface`, because of formatters in `package` line.https://gitlab.gnome.org/GNOME/gnome-builder/-/issues/573Automatic indetation on new line not working2018-07-21T15:33:22ZVictor Aurélio SantosAutomatic indetation on new line not working**Steps to reproduce:**
- Open a C project
- Write some code on current line and press `enter`
**What happens:**
New line is created with cursor at begging.
**What's expected:**
New line is created with cursor with a indentation ma...**Steps to reproduce:**
- Open a C project
- Write some code on current line and press `enter`
**What happens:**
New line is created with cursor at begging.
**What's expected:**
New line is created with cursor with a indentation matching closest block.