After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 6050 - ** WARNING **: wire_read: error for all the plug-ins
** WARNING **: wire_read: error for all the plug-ins
Status: VERIFIED FIXED
Product: GIMP
Classification: Other
Component: General
1.x
Other OSF/1
: Normal major
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on: 2742
Blocks:
 
 
Reported: 2000-02-08 18:15 UTC by jeremie.petit
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description jeremie.petit 2001-01-28 15:48:41 UTC
Package: gimp
Version: 1.1.15

Name........: Jeremie Petit
Email.......: jeremie.petit@compaq.com
Platform....: Alpha, Tru64 4.0f
GIMP Version: 1.1.15
GTK Version.: 1.2.6


-- Other system notes:
I compiled the gimp with Tru64 native C compiler.
--

-- Problem description:
When I launch the Gimp, when it processes the plug-ins, I've
got lots of "** WARNING **: wire_read: error".
Then when I look at the Filters menu, most of its entries
are empty. The only filters that are available are:
Colors/Map/Alien Map2
Colors/Border Average
Noise/Spread
Distorts/Whirl And Pinch
--


-- How to repeat:
Compile the Gimp with the native Tru64 C compiler.
--


-- Other comments:

--




------- Additional Comments From Daniel.Egger@suse.de 2000-02-10 09:48:04 ----

Subject: True64 problems...
From: Daniel.Egger@suse.de
To: 6050@bugs.gnome.org
Message-Id: <20000210144805.E568D3D990@degger.muc.suse.de>
Date: Thu, 10 Feb 2000 15:48:04 +0100 (CET)

Hiho!

 Unfortunately I can't reproduce this one because I don't
 have such a machine but it seems that the wire protocol
 can't pipe it's data through either because:
 - wrong datatypes are used
 or
 - Tru64 causes problems here because <unknown reason>

 Is there any way to let me play a bit on this machine remotely?

-- 

Servus,
       Daniel




------- Additional Comments From yasuhiro@awa.tohoku.ac.jp 2000-02-13 09:46:14 ----

Subject: Tru64 ?
From: SHIRASAKI Yasuhiro <yasuhiro@awa.tohoku.ac.jp>
To: 6050@bugs.gnome.org
Message-Id: <200002131446.XAA10506@syssrv.awa.tohoku.ac.jp>
Date: Sun, 13 Feb 2000 23:46:14 +0900

Hi,

I've just compiled gimp 1.1.15 and 1.1.17 with native C compiler
on our Tru64 4.0D and they worked well. Something is different
between 4.0D and 4.0F?

% cc -V
cc  (cc)
        Digital UNIX Compiler Driver 3.11
DEC C V5.6-079 on Digital UNIX V4.0 (Rev. 878)

% env CC='cc' ./configure --prefix=/foo/bar \
--disable-perl --disable-static
% gmake
% gmake install

--
yasuhiro




------- Additional Comments From jschmid@klizix.mpi-stuttgart.mpg.de 2000-02-16 04:52:51 ----

Subject: gimp
From: "Joerg D. Schmid" <jschmid@klizix.mpi-stuttgart.mpg.de>
To: 6050@bugs.gnome.org
Message-Id: <38AA7373.D3D969CF@klizix.mpi-stuttgart.mpg.de>
Date: Wed, 16 Feb 2000 10:52:51 +0100

I had the same error messages described in gimp-bug 6050
with gimp-1.1.16 on i386 .
They went away when I did :

ln -s /usr/local/lib/libgimp-1.1.so.16.0.0
/usr/local/lib/libgimp-1.1.so.14

I'm not sure if I did something wrong with the installation or if
there's
a bug that causes some scripts to look for an older lib.

--
Joerg Schmid
jschmid@klizix.mpi-stuttgart.mpg.de
MPI fuer Festkoerperforschung
Stuttgart




------- Additional Comments From jeremie_petit@geocities.com 2000-02-16 12:35:24 ----

Subject: Further info
From: Jeremie Petit <jeremie_petit@geocities.com>
To: 6050@bugs.gnome.org
Message-Id: <38AADFDC.7928AF88@geocities.com>
Date: Wed, 16 Feb 2000 18:35:24 +0100

Hello,

  Well, it's the same with the Gimp 1.1.17, out that Fractal Trace seems
to work (at least when it
does not makes floating point exceptions). On Tru64 4.0f, the C compiler
is the following (cc -V):

  DEC C V5.9-008 on Digital UNIX V4.0 (Rev. 1229)

  Daniel may be right about some wrong datatypes used, there are some
problems of
that kind that are being solved for fvwm2 at the moment.

  Unfortunately I can't give you access to this machine, it's behind a
firewall.

  What I can offer is compiling/running any kind of test you can imagine
on Tru64 4.0f and
give you the result.

	Best regards,

	Jeremie Petit.

-- 
		Jeremie Iahhel PETIT <jeremie_petit@geocities.com>
		http://www.geocities.com/Broadway/3525/cds




------- Additional Comments From gosgood@idt.net 2000-03-12 08:17:28 ----

Subject: Later manifestation of #2742 [gimp-bug] plug-ins do not load
From: "Garry R. Osgood" <gosgood@idt.net>
To: 6050@bugs.gnome.org
Message-Id: <38CB98E7.B490BB29@idt.net>
Date: Sun, 12 Mar 2000 08:17:28 -0500

This bug appears to be a later manifestation of #2742; this report is more complete than #2742.
G. R. Osgood




------- Bug moved to this database by debbugs-export@bugzilla.gnome.org 2001-01-28 10:48 -------
This bug was previously known as bug 6050 at http://bugs.gnome.org/
http://bugs.gnome.org/show_bug.cgi?id=6050
Originally filed under the gimp product and general component.

The original reporter (jeremie.petit@compaq.com) of this bug does not have an account here.
Reassigning to the exporter, debbugs-export@bugzilla.gnome.org.
Reassigning to the default owner of the component, egger@suse.de.

Comment 1 Daniel Egger 2001-02-07 12:32:30 UTC
I'd like to know:
a) whether this bug is still there with 1.2.1 which is the latest
stable version
b) whether it works with a more recent than the buggy 4.0F version
Comment 2 Raphaël Quinet 2001-04-26 18:10:36 UTC
Re-assigning all Gimp bugs to default component owner (Gimp bugs list)
Comment 3 Garry R. Osgood 2001-04-28 02:07:57 UTC
The Signal Crew had linked this bug to 2742 last summer, and it was
cross-referenced with that critter in the old bugs.gnome.org database.
The temporary hack by Mitch Natterer to put #2742 to fitful rest
has likely quieted this one down as well, so it is not reproducable
currently. Its resolution is the same as that of 2742, one that
really depends on g_iochannel modification for a true fix, which are
not in GLIB 1.2.9. See 2742 long comment for bloody details. When
2742 goes to bed, this one should follow.

Garry Osgood 27-Apr-2001 
 
Comment 4 Sven Neumann 2002-08-28 04:30:52 UTC
Since I've just closed bug #2742, I'll close this one as well just
like Garry suggested.
Comment 5 Raphaël Quinet 2003-06-20 18:04:20 UTC
The fix is part of the stable release 1.2.4 (or earlier, hopefully). 
Closing this bug.