[Bug 226636] New: kontact freezes when adding new event after using summary view

Robert Voinea rvoinea at gmail.com
Sat Feb 13 06:51:28 GMT 2010


https://bugs.kde.org/show_bug.cgi?id=226636

           Summary: kontact freezes when adding new event after using
                    summary view
           Product: kontact
           Version: unspecified
          Platform: Gentoo Packages
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kdepim-bugs at kde.org
        ReportedBy: rvoinea at gmail.com


Version:            (using KDE 4.4.0)
OS:                Linux
Installed from:    Gentoo Packages

KDE 4.4.0 Gentoo.

I have only 2 calendars set, both of them through Akonadi as "Calendar in Local
Directory".
Sometimes, when I add an event to a calendar Kontact does not allow me to
interact with it, although resizing the window refreshes the view.
I see that it happens every time I use the Summary View.
If I use the Summary View, go back to Kontact/organizer and then add an event,
the interface does not allow any kind of input, but the event is added to the
organizer.
Using Kontact/Organizer without checking the Summary View everything is OK.

The last lines of debug output are these:

kontact(5102)/kdepimlibs (kabc) KABC::LockNull::lock: LockNull::lock() force
success. Doesn't actually lock.
kontact(5102)/libakonadi Akonadi::SessionPrivate::dataReceived: Server protocol
version is: 23
kontact(5102)/kdepimlibs (kcal): Can't decrement change count. It already is 0.
kontact(5102)/libakonadi Akonadi::SessionPrivate::dataReceived: Server protocol
version is: 23

strace on Kontact shows this:

read(3, "\0", 16)                       = 1
read(3, 0xbfeab8e0, 16)                 = -1 EAGAIN (Resource temporarily
unavailable)
clock_gettime(CLOCK_MONOTONIC, {2263, 183856371}) = 0
read(9, 0x86a3560, 4096)                = -1 EAGAIN (Resource temporarily
unavailable)
clock_gettime(CLOCK_MONOTONIC, {2263, 183912240}) = 0
clock_gettime(CLOCK_MONOTONIC, {2263, 183939128}) = 0
clock_gettime(CLOCK_MONOTONIC, {2263, 183965768}) = 0
select(25, [3 5 9 10 12 16 19 22 23 24], [], [], {0, 19688}) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {2263, 203811258}) = 0
clock_gettime(CLOCK_MONOTONIC, {2263, 203864573}) = 0
read(9, 0x86a3560, 4096)                = -1 EAGAIN (Resource temporarily
unavailable)
clock_gettime(CLOCK_MONOTONIC, {2263, 203938982}) = 0
clock_gettime(CLOCK_MONOTONIC, {2263, 203970602}) = 0
clock_gettime(CLOCK_MONOTONIC, {2263, 203999879}) = 0
select(25, [3 5 9 10 12 16 19 22 23 24], [], [], {0, 979599}) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {2264, 184740121}) = 0
gettimeofday({1266042071, 257030}, NULL) = 0
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2195, ...}) = 0
write(4, "\0", 1)                       = 1
clock_gettime(CLOCK_MONOTONIC, {2264, 185331102}) = 0
clock_gettime(CLOCK_MONOTONIC, {2264, 185379996}) = 0
clock_gettime(CLOCK_MONOTONIC, {2264, 185413630}) = 0
clock_gettime(CLOCK_MONOTONIC, {2264, 185443117}) = 0
read(9, 0x86a3560, 4096)                = -1 EAGAIN (Resource temporarily
unavailable)
clock_gettime(CLOCK_MONOTONIC, {2264, 185509635}) = 0
clock_gettime(CLOCK_MONOTONIC, {2264, 185536613}) = 0
clock_gettime(CLOCK_MONOTONIC, {2264, 185563366}) = 0
select(25, [3 5 9 10 12 16 19 22 23 24], [], [], {0, 19934}) = 1 (in [3], left
{0, 19930})

and keeps repeating... and repeating... and repeating...

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the Kdepim-bugs mailing list