On Fri, Aug 12, 2005 at 04:56:55PM +0200, Loïc Minier wrote: > Do you have access to a machine running Debian unstable (sid)? Could > you please try with Gedit in versions 2.10.x?
So, on a test machine: - with sarge: gedit 2.8.3-4sarge1 Print, Generic Postscript, Custom, /tmp/bla.sh /tmp/bla.sh is an executable shell script message: ** (gedit:1481): WARNING **: Opening '/tmp/bla.sh' for output failed strace shows nothing todo with bla.sh - taking sid's source and recompiling (2-10.3-4) under sarge Print, Generic Postscript, Custom, /tmp/bla.sh SAME BUG NOTES - had to force (-d) depends to libpspell-dev (expected 0.60.3-2, present 0.60.2+20050121-2) - taking sid's source for libgnomeprintui2.2-dev (libgnomeprintui-2.10.2-2), libgnomeprint2.2-dev (libgnomeprint_2.10.3-2) and libgnomecups-0.2.0. BUG FIXED I shall then assume the bug was probably in libgnomeprint. Installing just the fixed libs: dpkg -i libgnomeprint2.2-0_2.10.3-2_i386.deb libgnomecups1.0-1_0.2.0-2_i386.deb libgnomeprint2.2-data_2.10.3-2_all.deb fixed the bug. Then I installed apt-get source libgnomeprint2.2 from stable, and did some diffing. It looks like it's bug http://bugzilla.gnome.org/show_bug.cgi?id=169963 and http://bugzilla.gnome.org/show_bug.cgi?id=169997 (aka http://bugzilla.gnome.org/show_bug.cgi?id=167325). Will Debian backport those grave functionnality bugs ? Or just document those ? Thank you for your help!