(gtk3) G_REGEX_MULTILINE issue

Bug #1560989 reported by Egmont Koblinger
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Terminator
Fix Released
Low
Unassigned

Bug Description

When starting up terminator-gtk3 (bzr) with vte-0.44, the following is printed a couple of times:

(terminator:12345): Vte-WARNING **: (vtegtk.cc:1704):int vte_terminal_match_add_gregex(VteTerminal*, GRegex*, GRegexMatchFlags): runtime check failed: (g_regex_get_compile_flags(gregex) & G_REGEX_MULTILINE)

The following changes are relevant:
https://git.gnome.org/browse/vte/commit/?id=d847452
https://git.gnome.org/browse/vte/commit/?id=7fdb3d1

Related branches

Revision history for this message
Stephen Boddy (stephen-j-boddy) wrote :

Does this cause Terminator to fail to start, break searches, or is it just a warning?

I'm guessing here but I suppose I have to add the multiline flag in the call if the VTE version is 0.44+

Revision history for this message
Egmont Koblinger (egmont-gmail) wrote :

Just a warning.

> I'm guessing here but I suppose I have to add the multiline flag in the call if the VTE version is 0.44+

I guess so too. Haven't verified.

Revision history for this message
Egmont Koblinger (egmont-gmail) wrote :

I think you can add that flag unconditionally. Don't know for sure, though.

Revision history for this message
Stephen Boddy (stephen-j-boddy) wrote :

Egmont, can you check this is OK with vte 0.44 (or newer). It doesn't cause any issue with my 0.42.5. If it works for you I'll commit it, then if it causes issues with older versions it's a trivial test for the version to adjust the regex_flags variable.

Changed in terminator:
status: New → Incomplete
importance: Undecided → Low
Revision history for this message
Egmont Koblinger (egmont-gmail) wrote :

Looks okay (URLs are still underlined as expected, warnings are gone).

Just for the record: This is with vte-0.44, as reported originally. With vte-0.47.90 there are no warnings even without the patch. Apparently works equally good with and without this patch. Still, I guess this patch is the way to go.

Revision history for this message
Stephen Boddy (stephen-j-boddy) wrote :

For sure, or we just get bug reports from everyone on 0.44 all the time. I'll commit it.

Revision history for this message
Stephen Boddy (stephen-j-boddy) wrote :

Committed revision 1737.

Changed in terminator:
status: Incomplete → Fix Committed
Changed in terminator:
status: Fix Committed → 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.