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

List:       kde-bugs-dist
Subject:    [Bug 113652] New: Hang up on attempt to edit field of existing entry
From:       Vincent DiCarlo <vdicarlo () dicarlolaw ! com>
Date:       2005-09-30 21:56:03
Message-ID: 20050930235602.113652.vdicarlo () dicarlolaw ! com
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=113652         
           Summary: Hang up on attempt to edit field of existing entry
           Product: kaddressbook
           Version: 3.4
          Platform: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: tokoe kde org
        ReportedBy: vdicarlo dicarlolaw com


Version:           3.4 (using KDE 3.4.0 Level "b" , SUSE 9.3)
Compiler:          gcc version 3.3.5 20050117 (prerelease) (SUSE Linux)
OS:                Linux (i686) release 2.6.11.4-21.9-default

Edit of existing entry swamps cpu long delay (2-4 min) for keyboard entries in edit \
fields beginning when cursor is put in entry field. Same problem when start \
Kaddressbook from Kontact.

Ksysguard shows plenty of hardware memory and no swap file activity, but about 85% \
processor usage by Kaddressbook or Kontact, depending on which one is used to start \
addressbook.

Processor is Intel Pentium III (Katmai) 500mH, 512KB level I cache.
There are 512mB memory, a 1 gig swap file, and 3 or 4 gig left on the partition.

There are about 5,000 entries in the address book, most of which were added by \
importing vcard 3.0 or csv files exported from other applications.

I'm old to computers, but new to Linux and KDE. Thanks for offering us such an \
impressive free and better alternative to Microsoft. I am willing to help to the \
extent that my limited expertise permits.


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