Stefan Sauer

The backtraces would be nicer if you had debug symbols installed fro glib/gio. But the failure is this the missing schema (bt_settings_make). Unfortunately I missed a bit when renaming the...

We'd need debug symbols for glib and gtk+3. Once the debug symbols are actually picked up the backtraces: ``` #0 0x00007ffff4f7b6eb in g_logv () from /usr/lib/libglib-2.0.so.0 #1 0x00007ffff4f7b85f in g_log...

Found it, gtk-3.14 deprecated the two css attributes below. ``` /* deprecated in 3.14, should use outline-{width,padding} */ -GtkWidget-focus-line-width: 0; -GtkWidget-focus-padding: 0; ``` I am using this in bt-edit.css. I'll...

@josephgbr any better now?

This looks like another gtk+3 css deprecation :/ Seems to be https://mail.gnome.org/archives/commits-list/2015-December/msg06135.html, released in 3.19.6 I have to replace 'prelight' with 'hover'. Submitted another patch. Sorry for the troubles.

This is progress again, the deprecation issues are fixed. You could not Ctrl-C in dgb? If you can Ctrl-C and get the gdb-prompt again, you could type 'bt' to get...

The UI tests take screenshots (to /tmp) of various dialogs. Something changed in cairo/gtk to cause this assertion. Can you retry with the cairo debug symbols as well?

Not really. One thing you could try is to run the test as BT_CHECK_NO_XVFB=1 BT_CHECKS=test_bt_edit_application_create G_DEBUG="fatal_warnings" make bt_edit.gdb The tests normally run with a hidden x-server. With BT_CHECK_NO_XVFB=1 the tests...

The workaround is using 0.0 ... 400.0 as a range istead of 0.0 ... 100.0. The choice of an upper bound > 100% is intentional to also allow making quite...

GST_DEBUG="*:4" ./buzztrax-edit ... or GST_DEBUG_DUMP_DOT_DIR=$PWD ./buzztrax-edit and when the error happens, invoke the "Debug" menu -> "Dump pipeline graph and show". The last image is in $PWD as buzztrax.svg (or...