[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: KMail crash on attaching a file (Debian testing packages)



On Wednesday 02 January 2002 07:01 am, Rachel Andrew wrote:
> hy>
> Resent-From: debian-kde@lists.debian.org
> X-Mailing-List: <debian-kde@lists.debian.org> archive/latest/6129
> X-Loop: debian-kde@lists.debian.org
> Precedence: list
> Resent-Sender: debian-kde-request@lists.debian.org
>
> Hi
>
> I have a Debian Woody system with the KDE packages from testing, all is
> running really well apart from a couple of issues with KMail, the worst of
> which is if I try to attach a file it crashes with a Signal 11, when I OK
> the file I have selected by browsing to it. I've pasted the backtrace
> below. The crash happens every time i try to attach a file.
>
> Its a standard up to date install from the testing packages on an Athlon
> 1gig machine, Abit KT7A mainboard.
>
> Rachel
>
> (no debugging symbols found)...(no debugging symbols found)...
> (no debugging symbols found)...(no debugging symbols found)...
> (no debugging symbols found)...(no debugging symbols found)...
> (no debugging symbols found)...(no debugging symbols found)...
> (no debugging symbols found)...(no debugging symbols found)...
> (no debugging symbols found)...(no debugging symbols found)...
> (no debugging symbols found)...(no debugging symbols found)...
> (no debugging symbols found)...(no debugging symbols found)...
> (no debugging symbols found)...(no debugging symbols found)...
> (no debugging symbols found)...(no debugging symbols found)...
> (no debugging symbols found)...(no debugging symbols found)...
> (no debugging symbols found)..
> .(no debugging symbols found)...
> (no debugging symbols found)...(no debugging symbols found)...
> (no debugging symbols found)...(no debugging symbols found)...
> (no debugging symbols found)...(no debugging symbols found)...
> (no debugging symbols found)...(no debugging symbols found)...
> (no debugging symbols found)...(no debugging symbols found)...
> (no debugging symbols found)...(no debugging symbols found)...
> (no debugging symbols found)...(no debugging symbols found)...
> (no debugging symbols found)...(no debugging symbols found)...
> (no debugging symbols found)...0x40fd78f9 in wait4 ()
> from /lib/libc.so.6
> #0  0x40fd78f9 in wait4 () from /lib/libc.so.6
> #1  0x410501f0 in __check_rhosts_file () from /lib/libc.so.6
> #2  0x407e70b8 in KCrash::defaultCrashHandler () from
> /usr/lib/libkdecore.so.3 #3  0x40f60848 in sigaction () from /lib/libc.so.6
> #4  0x080cfecd in KDialog::marginHint ()
> #5  0x080ad0d9 in KDialog::marginHint ()
> #6  0x40492a6f in KIO::Job::result () from /usr/lib/libkio.so.3
> #7  0x40479d7c in KIO::Job::emitResult () from /usr/lib/libkio.so.3
> #8  0x4047ab96 in KIO::SimpleJob::slotFinished () from /usr/lib/libkio.so.3
> #9  0x4047ccc1 in KIO::TransferJob::slotFinished () from
> /usr/lib/libkio.so.3 #10 0x40a6ea0d in QObject::activate_signal () from
> /usr/lib/libqt.so.2 #11 0x4046ccd5 in KIO::SlaveInterface::finished () from
> /usr/lib/libkio.so.3 #12 0x4046911c in KIO::SlaveInterface::dispatch ()
> from /usr/lib/libkio.so.3 #13 0x40468e68 in KIO::SlaveInterface::dispatch
> () from /usr/lib/libkio.so.3 #14 0x40467aa0 in KIO::Slave::gotInput () from
> /usr/lib/libkio.so.3 #15 0x40a6ecce in QObject::activate_signal () from
> /usr/lib/libqt.so.2 #16 0x40ac6658 in QSocketNotifier::activated () from
> /usr/lib/libqt.so.2 #17 0x40aa5242 in QSocketNotifier::event () from
> /usr/lib/libqt.so.2 #18 0x40a1aa87 in QApplication::notify () from
> /usr/lib/libqt.so.2 #19 0x40755da4 in KApplication::notify () from
> /usr/lib/libkdecore.so.3 #20 0x409e53ba in qt_set_socket_handler () from
> /usr/lib/libqt.so.2 #21 0x409e
> 5abe in QApplication::processNextEvent () from /usr/lib/libqt.so.2
> #22 0x40a1cf4f in QApplication::enter_loop () from /usr/lib/libqt.so.2
> #23 0x409ec9c3 in QApplication::exec () from /usr/lib/libqt.so.2
> #24 0x08133ae3 in KDialog::marginHint ()
> #25 0x40f5065f in __libc_start_main () from /lib/libc.so.6

    Rachel:

That is correct.  If you are running a pure Woody box, then parts of KDE are 
broken and we are kind of in limbo waiting for some new packages to trickle 
down from Sid to fix these problems.  

An option is to install the Sid version of KDE, or wait until the repaired 
newer packages make it into Woody.

tatah

-- 

Jaye Inabnit\ARS ke6sls\/A GNU-Debian linux user\/ http://www.qsl.net/ke6sls
If it's stupid, but works, it ain't stupid. I SHOUT JUST FOR FUN.
Free software, in a free world, for a free spirit. Please Support freedom!



Reply to: