FS#43874 - [unison] GUI seg. faults when creating a new profile under a QT environment.

Attached to Project: Arch Linux
Opened by Mika Norén (SysGhost) - Wednesday, 18 February 2015, 12:52 GMT
Last edited by Gaetan Bisson (vesath) - Friday, 20 February 2015, 07:50 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Powalowski (tpowa)
Gaetan Bisson (vesath)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
If one uses the Unison GUI, such as "unison-gtk" or "unison-x11" under a QT-based enviroment that applies the QT-theme/widgets to GTK2 applications, unison will crash when one tries to select folders during a profile creation.

Additional info:
* extra/unison 2.48.3-2
* extra/gtk2 2.24.25-1
* core/glibc 2.21-2

Output:
(unison-x11:24583): Gtk-CRITICAL **: gtk_tree_model_filter_get_value: assertion 'GTK_TREE_MODEL_FILTER (model)->priv->stamp == iter->stamp' failed

(unison-x11:24583): GLib-GObject-WARNING **: gtype.c:4221: type id '0' is invalid

(unison-x11:24583): GLib-GObject-WARNING **: can't peek value table for type '<invalid>' which is not currently referenced
[1] 24583 segmentation fault (core dumped) unison-x11



Steps to reproduce:
* Be under some QT-based graphical environment that applies its widget-theme to GTK2-based applications. KDE for instance.
* Start unison GUI program. Either one of "unison-gtk" or "unison-x11".
* Create a new profile by clicking the "+ Add" button from "Profile Selection" window. Follow the creation guide.
* When at selecting target folders, choose "Other" from the dropdown menu.
* Unison abruptly quits due to a segmentation fault. (Caused by previous errors. See Output above)


How to work around:
* Do not run unison GUI under a QT-based enviroment, and/or disable QT-theming of GTK-applications.
This task depends upon

Closed by  Gaetan Bisson (vesath)
Friday, 20 February 2015, 07:50 GMT
Reason for closing:  Upstream
Comment by Gaetan Bisson (vesath) - Friday, 20 February 2015, 07:50 GMT
Sorry but I see no way to solve this from a packaging perspective. This should be reported upstream to either Qt or unison.

Loading...