Bug#831453: meld crashed when invoked from command line after recent upgrade (suspect GTK)
Chris Tillman
toff.tillman at gmail.com
Sat Jul 16 09:29:48 UTC 2016
Package: meld
Version: 3.16.1-1
Severity: normal
Dear Maintainer,
Hi,
I invoked meld with two small documents.
$ meld 6100.1.chk 6100.2.chk
The result was
No protocol specified
Unable to init server: Could not connect: Connection refused
No protocol specified
Unable to init server: Could not connect: Connection refused
(meld:14422): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: assertion
'GDK_IS_SCREEN (screen)' failed
Traceback (most recent call last):
File "/usr/bin/meld", line 260, in <module>
setup_resources()
File "/usr/bin/meld", line 193, in setup_resources
Gtk.IconTheme.get_default().append_search_path(icon_dir)
AttributeError: 'NoneType' object has no attribute 'append_search_path'
I noticed bug 830952, so checked my GTK version; it was 3.20.6-2. Perhaps "too
new"?
When I opened meld through the menu instead, I was able to use it to view the
diff.
Let me just say that I think meld provides the most attractive diff result
display I have ever seen, it's a joy to use just because of that.
-- System Information:
Debian Release: stretch/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 4.6.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_NZ.utf8, LC_CTYPE=en_NZ.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages meld depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.24.0-2
ii gir1.2-gtksource-3.0 3.20.4-1
ii libcanberra-gtk3-module 0.30-2.1
ii libgtk-3-0 3.20.6-2
ii libgtksourceview-3.0-1 3.20.4-1
ii patch 2.7.5-1
ii python-gi 3.18.2-2+b1
ii python-gi-cairo 3.18.2-2+b1
pn python:any <none>
Versions of packages meld recommends:
ii yelp 3.20.1-1
meld suggests no packages.
-- no debconf information
More information about the pkg-gnome-maintainers
mailing list