[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    Bug#9151: marked as done (KNode Crash)
From:       owner () bugs ! kde ! org (Stephan Kulow)
Date:       2000-08-29 23:33:03
[Download RAW message or body]

Your message dated Wed, 30 Aug 2000 01:26:07 +0200
with message-id <39AC468F.C2AEC182@bigfoot.com>
and subject line KNode Crash
has caused the attached bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I'm
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Stephan Kulow
(administrator, KDE bugs database)

Received: (at submit) by bugs.kde.org; 27 Aug 2000 13:51:53 +0000
From dlentz@localhost.localdomain Sun Aug 27 15:51:53 2000
Received: from dns.dockpoint.net ([206.107.107.88]:772 "EHLO
        localhost.localdomain") by master.kde.org with ESMTP
        id <S223992AbQHXWoj>; Fri, 25 Aug 2000 00:44:39 +0200
Received: by localhost.localdomain (Postfix, from userid 501)
        id 868CD1D0C3; Thu, 24 Aug 2000 18:48:38 -0400 (EDT)
From:   David Lentz <dlentz@dockpoint.net>
To:     submit@bugs.kde.org
Subject: KNode Crash
Message-Id: <20000824224838.868CD1D0C3@localhost.localdomain>
Date:   Thu, 24 Aug 2000 18:48:38 -0400 (EDT)
Sender: dlentz@localhost.localdomain
Return-Path: <dlentz@localhost.localdomain>
X-Orcpt: rfc822;submit@bugs.kde.org

Package: knode
Version: 0.2 (KDE 1.93 Beta >= 20000809mdk)
Severity: normal

Here is how to reproduce this error:

1. Start KNode
2. Go into the 'Add Newsgroup' window
3. Click on the 'New List' button and then, before it gets back, press the 'Ok' button.


Thanks,
David Lentz


Here is a backtrace generated by DrKonqi:
(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)...0x4115bd49 in wait4 () from /lib/libc.so.6
#0  0x4115bd49 in wait4 () from /lib/libc.so.6
#1  0x411bc800 in ?? () from /lib/libc.so.6
#2  0x410b30cb in waitpid () from /lib/libpthread.so.0
#3  0x4076c3a0 in KCrash::defaultCrashHandler ()
   from /opt/kde2/lib/libkdecore.so.3
#4  0x410f8fc8 in sigaction () from /lib/libc.so.6
#5  0x0 in ?? ()

[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic