public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] kdepim-4.6.0 woes
Date: Tue, 21 Jun 2011 01:40:47 +0200	[thread overview]
Message-ID: <1370928.tS5hQM40xH@nazgul> (raw)

Before, I beginning, I need dox, not solutions :-)

I'm having the devil's own time with kdepim after upgrading to 4.6.0.

Apart from the calendar (more on this later), everything seemed fine. 
Several kontact restarts and several reboots later it was still fine. 
Then suddenly kmail decided to throw away all my filters after #11 - 
they simply get removed from kmail2rc silently and the file is 
rewritten when kmail closes. I recreated the filters, and today it 
chucked everything away. Twice. Seriously, I'm now getting hugely 
pissed off. I can add the filters back in from a backup copy, but they 
still get discarded.

Today, kmail hung while accessing my Exchange account over IMAP. The 
folder list showed 100+ unread mails, but none of them were in the 
view pane. Deleting that account and recreating it brought everything 
back.

The calendar in korganizer just does not work. Period. It is empty. 
But all the todos in it are listed in the Kontact summary view! An 
invite is displayed as raw ical data, missing the usual Accept|Reject|
etc links. And the calendar is apparently read-only: right-click on a 
time-slot gives a greyed-out context menu so I can't select "Add 
event"

My pim config has come a long ways, from somewhere early in the 3-
series and just got updated every time. I tried a kdepim-4.6 beta a 
while ago but that was not a happy experience so went back to 4.4, and 
am now back at 4.6. I strongly suspect a very unhappy outdated config, 
but the apps themselves are not helping to nail it down.

There's nothing in .xsession-errors that gives a clue, nothing on the 
console with the appropriate kdebug options set, and lots of google 
searches have not revealed any kind of config validation script.

If any of you fine folks can point me at a link containing useful 
debugging techniques for kdepim, this here crotchy old sysadmin will 
be eternally grateful. I might even DHL some cookies as a token of 
gratitude :-)


-- 
alan dot mckinnon at gmail dot com



             reply	other threads:[~2011-06-21  0:11 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-20 23:40 Alan McKinnon [this message]
2011-06-21  6:12 ` [gentoo-user] kdepim-4.6.0 woes Mick
2011-06-21 19:19   ` Michael Schreckenbauer
2011-06-21 17:28 ` Alex Schuster
2011-06-21 19:16 ` Michael Schreckenbauer
2011-06-22  7:26   ` Alan McKinnon
2011-06-22 12:05     ` Mick
2011-06-22 12:16       ` Alan McKinnon
2011-06-22 12:56         ` Mick
2011-06-22 13:14         ` Dale
2011-06-22 15:32           ` Alan McKinnon
2011-06-22 14:36         ` Alan McKinnon
2011-06-22 15:23           ` Indi
2011-06-22 15:37             ` Alan McKinnon
2011-06-22 16:24               ` Indi
2011-06-22 15:44           ` Dale
2011-06-22 16:02             ` Alan McKinnon
2011-06-23  8:22               ` Joost Roeleveld
2011-06-23 10:53                 ` Dale
2011-06-23 11:36                   ` Joost Roeleveld
2011-06-23 20:12                     ` Alan McKinnon
2011-06-23 20:03                 ` Alan McKinnon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1370928.tS5hQM40xH@nazgul \
    --to=alan.mckinnon@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox