Hi all,

I thought I'd try here first, in case somebody here has seen anything similar to my issue.

Whenever I use Eclipse or Anjuta, and attempt to import an existing project by locating it from the file system, both applications will crash.

Steps to reproduce:
- Eclipse (Luna, downloaded from Eclipse website): File -> Import -> General -> Existing Projects into Workspace -> Next = Crash!
- Anjuta (3.10.2. installed via apt-get): Import an existing project -> Import from folder -> Other = Crash!

KDevelop, on the other hand, is fine. Something to do with the encrypted home causing problems with non-KDE apps?

I'm running Kubuntu 14.40 LTS. Essentially it's a pretty clean system, I only installed the OS five weeks ago. I've got an encrypted home on a separate disk from the root, and I've got an NTFS-formatted disk too.

Any help gratefully received!

If I run Anjuta direct from Konsole, I get this output:

(anjuta:4996): Gtk-CRITICAL **: gtk_tree_model_filter_get_value: assertion 'GTK_TREE_MODEL_FILTER (model)->priv->stamp == iter->stamp' failed

(anjuta:4996): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.40.2/./gobject/gtype.c:4210: type id '0' is invalid

(anjuta:4996): GLib-GObject-WARNING **: can't peek value table for type '<invalid>' which is not currently referenced
Segmentation fault (core dumped)

Anybody got any ideas? Is there a better place I can post?

google says it's maybe a problem with the oxygen gtk theme.
=> switch to some other gtk theme (there's a gtk+ config module for systemsetiings, if not installed, you might want to try gtk-chtheme or similar) and if that "fixes" it, report a bug against oxygen/gtk-style component at bugs.kde.org

Thanks luebking, that's solved the problem

I went to System Settings -> Application Appearance -> GTK, then:
Changed the GTK2 Theme from oxygen-gtk to Raleigh - this fixes Eclipse.
Changed the GTK3 Theme from oxygen-gtk to Default - this fixes Anjuta.

Makes some things a little uglier now, but at least they're working.

Looks like this has already been fixed:
https://bugs.kde.org/show_bug.cgi?id=339174