On Mon, Feb 7, 2011 at 7:46 AM, ~suv <[email protected]> wrote:
> On 7/2/11 03:35, Rainer Müller wrote: > > On 3/2/11 17:08, Jasper Frumau wrote: > > > >> Gtk:ERROR:gtkrecentmanager.c:1942:get_icon_fallback: assertion failed: > >> (retval != NULL) > >> Abort trap > > > I just installed gedit to try this myself. But it works out of the box > > for me. I even disabled my ~/.gtkrc-2.0 to rule out any configuration > > issues. > > > > I get the same warnings as you at startup, but that is common for Gtk+ > > based programs and should not be a problem: > > <...> > > > But gedit even works for me if I deactivate the gnome-icon-theme port, > > which provides these icons. > > Does it still work after you have saved some files from within Gedit > (which will then be listed as recently opened files)? > > AFAIU it is a problem affecting many applications [1][2], mostly on > non-Gnome desktops like KDE and MacPorts (using Oxygen or no explicit - > i.e. stock/hicolor - icon theme), triggered by a change in GTK+ 2.22.x > for stock and fallback icons [3]. > > A known workaround e.g. for Inkscape 0.48.0 [4] and MyPaint is to > actually use the Gnome or Tango icon theme (via ~/.gtkrc-2.0) as main or > fallback icon theme. Just having the icon theme installed is not > sufficient to prevent the crash in the GtkRecentManager object. Try > adding this line to ~/.gtkrc-2.0 to prevent the crash: > > gtk-fallback-icon-theme="gnome" > > or, alternatively (if you prefer Tango icons): > > gtk-fallback-icon-theme="tango" > If I do not have "~/.gtkrc-2.0" I can just add I suppose? > > > ~suv > > > > Related links: > > [1] Bug #651678 <https://bugs.launchpad.net/gtk/+bug/651678> > "crashes with assertion failure on startup" > -> upstream <https://bugzilla.gnome.org/show_bug.cgi?id=629878> > > [2] Bug #665725 <https://bugs.launchpad.net/linuxmint/+bug/665725> > "[mint-x] gtk+2.0-2.22.0 Error Gedit and Gnome panels crashing" > > [3] Bug 626474 – use standard icon names for stock icons > <https://bugzilla.gnome.org/show_bug.cgi?id=626474> > The change for this upstream GTK+ issue seems to be the trigger: > < > http://git.gnome.org/browse/gtk+/commit/?h=gtk-2-22&id=5c74a696d5c1593be0f6b801cb85a4baf1087883 > > > > [4] Inkscape 0.48.1 includes a fix >
_______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
