277116 - Drag and Drop a Message Crashes TB 1.0/Linux

Status: RESOLVED FIXED

(Thunderbird :: Mail Window Front End, defect)

Description

[Russ Fink]

When I click on a message and start to drag it into a folder, TB 1.0 crashes. 
The workaround is to right-click on the message, and select "Move To" and
specify the folder.  Note that I was able to drag messages on an earlier version
of Thunderbird, possibly Thunderbird 0.7.  I upgraded to 1.0 and now am
experiencing this problem.

Steps:
1. Left click (and hold) on a message in the message list (upper-right hand
subject/message/date list)
2. Begin to drag.  Cursor changes to the left-angle-bracket-with-plus-sign icon.
3. Within moments of the cursor change, the application crashes.

I am running a stock Red Hat Linux release 9 (Shrike) on the following platform:
 Linux.i686/glibc2.3.2/gcc3.2.2 using the stock KDE that came with RH 9.

Comment 1

[Russ Fink]

I was previously using Thunderbird 0.6 and drag/drop worked fine.  Russ.

Comment 2

[Russ Fink]

This was caused by a faulty (or incorrectly installed) libpng12.so
implementation.  I discovered it when trying to install a different package,
Firefox 1.0.1, and noted that the installer outright failed to run because of
the message below.  

When I removed the faulty binary from my LD_LIBRARY_PATH, the Firefox installer
worked, and on a hunch, I retested drag-and-drop on Thunderbird, and found it
now works as well.  (The hunch was based on a faint recollection that I
installed a new version of libpng around the same time I upgraded Thunderbird.)

Here is the error I saw, which was previously piped to dev null and so was never
seen until I ran it on the command line this morning:

thunderbird-bin: relocation error: /home/rfink/lib/Linux2.4.20/libpng12.so.0:
undefined symbol: inflateInit_

If anyone sees this drag/drop/crash behavior in Thunderbird, check for this
error message.  Also, it would behoove you to "ldd thunderbird-bin" and see
where it's getting its shared libraries from.

I'm setting this to "fixed" so it might show up in queries, you know, for future
generations and stuff.