> However, if you are suffering from the same issue, could you please
> email in the same details from your system. They're in the second
> message down in the bug report.

I'll save you some time--I was more than happy to send in those details
from my system (as a matter of fact, I was tempted to respond on the bug
submitters' behalf when he didn't), however while I was in the process
of going through them I found that the output of
ldd /usr/lib/mozilla/plugins32/libflashplayer.so
is:
        linux-gate.so.1 =>  (0xffffe000)
        libdl.so.2 => /var/chroot/sid-ia32/lib/libdl.so.2 (0xf7844000)
        libpthread.so.0 => /var/chroot/sid-ia32/lib/libpthread.so.0 (0xf782d000)
        libX11.so.6 => /var/chroot/sid-ia32/usr/lib/libX11.so.6 (0xf7741000)
        libXext.so.6 => /var/chroot/sid-ia32/usr/lib/libXext.so.6 (0xf7733000)
        libXt.so.6 => /var/chroot/sid-ia32/usr/lib/libXt.so.6 (0xf76e2000)
        libfreetype.so.6 => /var/chroot/sid-ia32/usr/lib/libfreetype.so.6 
(0xf7673000)
        libfontconfig.so.1 => /var/chroot/sid-ia32/usr/lib/libfontconfig.so.1 
(0xf7648000)
        libgtk-x11-2.0.so.0 => /var/chroot/sid-ia32/usr/lib/libgtk-x11-2.0.so.0 
(0xf72f8000)
        libgobject-2.0.so.0 => /var/chroot/sid-ia32/usr/lib/libgobject-2.0.so.0 
(0xf72bd000)
        libglib-2.0.so.0 => /var/chroot/sid-ia32/usr/lib/libglib-2.0.so.0 
(0xf7227000)
        libm.so.6 => /var/chroot/sid-ia32/lib/libm.so.6 (0xf7201000)
        libc.so.6 => /var/chroot/sid-ia32/lib/libc.so.6 (0xf70b9000)
        /lib/ld-linux.so.2 (0x56555000)
        libXau.so.6 => /var/chroot/sid-ia32/usr/lib/libXau.so.6 (0xf70b6000)
        libXdmcp.so.6 => /var/chroot/sid-ia32/usr/lib/libXdmcp.so.6 (0xf70b1000)
        libSM.so.6 => /var/chroot/sid-ia32/usr/lib/libSM.so.6 (0xf70a8000)
        libICE.so.6 => /var/chroot/sid-ia32/usr/lib/libICE.so.6 (0xf7090000)
        libz.so.1 => /var/chroot/sid-ia32/usr/lib/libz.so.1 (0xf707b000)
        libexpat.so.1 => /var/chroot/sid-ia32/usr/lib/libexpat.so.1 (0xf705b000)
        libgdk_pixbuf-2.0.so.0 => 
/var/chroot/sid-ia32/usr/lib/libgdk_pixbuf-2.0.so.0 (0xf7045000)
        libgdk-x11-2.0.so.0 => /var/chroot/sid-ia32/usr/lib/libgdk-x11-2.0.so.0 
(0xf6fc1000)
        libpangocairo-1.0.so.0 => 
/var/chroot/sid-ia32/usr/lib/libpangocairo-1.0.so.0 (0xf6fb8000)
        libpango-1.0.so.0 => /var/chroot/sid-ia32/usr/lib/libpango-1.0.so.0 
(0xf6f7a000)
        libXfixes.so.3 => /var/chroot/sid-ia32/usr/lib/libXfixes.so.3 
(0xf6f75000)
        libatk-1.0.so.0 => /var/chroot/sid-ia32/usr/lib/libatk-1.0.so.0 
(0xf6f5b000)
        libgmodule-2.0.so.0 => /var/chroot/sid-ia32/usr/lib/libgmodule-2.0.so.0 
(0xf6f57000)
        libcairo.so.2 => /var/chroot/sid-ia32/usr/lib/libcairo.so.2 (0xf6ee1000)
        libXrender.so.1 => /var/chroot/sid-ia32/usr/lib/libXrender.so.1 
(0xf6ed9000)
        libXinerama.so.1 => /var/chroot/sid-ia32/usr/lib/libXinerama.so.1 
(0xf6ed6000)
        libXi.so.6 => /var/chroot/sid-ia32/usr/lib/libXi.so.6 (0xf6ece000)
        libXrandr.so.2 => /var/chroot/sid-ia32/usr/lib/libXrandr.so.2 
(0xf6ec7000)
        libXcursor.so.1 => /var/chroot/sid-ia32/usr/lib/libXcursor.so.1 
(0xf6ebe000)
        libpangoft2-1.0.so.0 => 
/var/chroot/sid-ia32/usr/lib/libpangoft2-1.0.so.0 (0xf6e93000)
        libpng12.so.0 => /var/chroot/sid-ia32/usr/lib/libpng12.so.0 (0xf6e70000

This led me to wonder whether the fact that I haven't updated my chroot
(which despite its directory name runs Lenny just like my primary system)
in entirely too long (I tend to neglect it) might be the problem.
Indeed, after a simple package update on my chroot the problem
disappeared.  

This appeared to be the issue, and was likely why you couldn't reproduce
the bug.  I really appreciate your assistance here, and don't feel
terribly bright for not figuring this one out on my own.  Hope this
helps someone else as well...

                                                --Ben.
--

"I find it kind of funny, I find it kind of sad
The dreams in which I'm dying are the best I've ever had."  
                          --Tears for Fears, "Mad World"


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to