Bug 19556 - regexxer preferences do not work; glibmm-CRITICAL
Summary: regexxer preferences do not work; glibmm-CRITICAL
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: All Packagers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-09 18:24 CEST by Morgan Leijström
Modified: 2016-10-10 05:46 CEST (History)
1 user (show)

See Also:
Source RPM: regexxer-0.10-7.mga6.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Morgan Leijström 2016-10-09 18:24:22 CEST 
Running on fully updated cauldron, 64 bit, Plasma

Seen in terminal where started from:

$ LC_ALL=C regexxer

(regexxer:27810): Gtk-WARNING **: Theme parsing error: <data>:3:47: The style property GtkWidget:interior-focus is deprecated and shouldn't be used anymore. It will be removed in a future version

(regexxer:27810): Gtk-WARNING **: Theme parsing error: <data>:4:28: The style property GtkWidget:focus-padding is deprecated and shouldn't be used anymore. It will be removed in a future version

------------------------
Visually it looks OK and seem to work, but i in its menu select Edit > Preferences :
nothing happens, and in terminal this is output:
------------------------

(regexxer:27810): glibmm-CRITICAL **: 
unhandled exception (type Glib::Error) in signal handler:
domain: gtk-builder-error-quark
code  : 11
what  : /usr/share/regexxer/prefdialog.ui:28:37 Invalid property: gtkmm__GtkDialog.has_separator
David Walser 2016-10-09 21:02:39 CEST

CC: (none) => jani.valimaa
Assignee: bugsquad => pkg-bugs

Comment 1 Jani Välimaa 2016-10-09 21:08:50 CEST 
Version 0.10 is quite old (5 years). Anyhow, I've added a patch to -8.mga6 from upstream GIT to fix this issue. Closing as FIXED.

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 2 Morgan Leijström 2016-10-10 05:46:00 CEST 
That was quick, thanks :)
Note You need to log in before you can comment on or make changes to this bug.