Hi!

JFYI as this might (partly) be packaging related.

I found the following bugs with Akonadi since I upgraded to KDE 4.4.3
happening often, possibly always when I start Kontact for the first time
after starting a KDE session. On further starts of Kontact it works as
expected:

Bug 236535 - sometimes can't open and log timezone and privilege tables
https://bugs.kde.org/236535

Bug 236538 - often does not find resource agents on first start of Kontact
https://bugs.kde.org/236538

Bug 236539 - dbus session bus not available on first start of Kontact -
race condition?
https://bugs.kde.org/236539

Expected results:

Akonadi just works all the time and doesn't confuse the casual user with
lots of cryptic error messages . At least I wouldn't want to explain my
father why Akonadi doesn't work correctly this time. Especially when I do
not get either.

Possibly some of these where here with earlier KDE 4.4 versions, but at
least now it shows up often, if not everytime on first start of contact.

Ciao,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7

[Martin Steigerwald - Donnerstag 06 Mai 2010 11:34:57]
>
> Hi!
>
> JFYI as this might (partly) be packaging related.
>
> I found the following bugs with Akonadi since I upgraded to KDE 4.4.3
> happening often, possibly always when I start Kontact for the first time
> after starting a KDE session. On further starts of Kontact it works as
> expected:

Umm, that's interesting. I had this since KDE 4.4.0 (self-compiled) and
it vanished when switching from the 4.4.2 debs to the 4.4.3 ones.
So I thought it was just fixed for 4.4.3. Now I wonder what I did to
make it work.

Regards


--
To UNSUBSCRIBE, email to debian-kde-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201005061144.03642.schwarzerf@gmail.com">http://lists.debian.org/201005061144.03642.schwarzerf@gmail.com

On 2010-05-06 Martin Steigerwald wrote:
> Bug 236538 - often does not find resource agents on first start of Kontact
> https://bugs.kde.org/236538
>
> Bug 236539 - dbus session bus not available on first start of Kontact -
> race condition?
> https://bugs.kde.org/236539

I can confirm both of these bugs.
Possible 'workaround' can be found at: http://userbase.kde.org/Akonadi_4.4/Troubleshooting

ie wrt 236538: close Kontact. Start KAddressBook standalone. Quit KAddressBook. Start Kontact.


Diederik


--
To UNSUBSCRIBE, email to debian-kde-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201005061157.58112.didi.debian@cknow.org">http://lists.debian.org/201005061157.58112.didi.debian@cknow.org

Am Donnerstag 06 Mai 2010 schrieb Frederik Schwarzer:
> [Martin Steigerwald - Donnerstag 06 Mai 2010 11:34:57]
>
> > Hi!
> >
> > JFYI as this might (partly) be packaging related.
> >
> > I found the following bugs with Akonadi since I upgraded to KDE 4.4.3
> > happening often, possibly always when I start Kontact for the first
> > time after starting a KDE session. On further starts of Kontact it
> > works as
>
> > expected:
> Umm, that's interesting. I had this since KDE 4.4.0 (self-compiled) and
> it vanished when switching from the 4.4.2 debs to the 4.4.3 ones.
> So I thought it was just fixed for 4.4.3. Now I wonder what I did to
> make it work.

Well: Thats what I mean. Do you *understand* whats going on there?

I am a Linux trainer, consultant and administrator since >5 years and
still don't get *why* this happen and *what* it triggers. I might get it
when I study MySQL, DBUS, Resource Agents, Nepomuk, *whatever* else it
uses - but I am and I want to be *just a user* of this stuff.

So I think this is for upstream to solve - and if it ain't work reliably
in KDE 4.4 I think it has to be fixed within KDE 4.4 series. Akonadi might
use MySQL or not, but it if uses it, KAddressBook should still just work
*predictably*.

Thus I suggest reporting anything like that upstream - especially to you,
Boyd - complaining here probably just won't help. And if upstream does not
get bug reports they probably don't even know that something is broken on
probably only *some* systems.

Some issues might be packaging related, but then I hope to get hints back
from upstream developers so that I can file debian bug reports with proper
suggestions. Until then I think I default to reporting upstream, unless
someone convinces me to do elsewise.

Ciao,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7

Am Donnerstag 06 Mai 2010 schrieb Diederik de Haas:
> On 2010-05-06 Martin Steigerwald wrote:
> > Bug 236538 - often does not find resource agents on first start of
> > Kontact https://bugs.kde.org/236538
> >
> > Bug 236539 - dbus session bus not available on first start of
> > Kontact - race condition?
> > https://bugs.kde.org/236539
>
> I can confirm both of these bugs.
> Possible 'workaround' can be found at:
> http://userbase.kde.org/Akonadi_4.4/Troubleshooting
>
> ie wrt 236538: close Kontact. Start KAddressBook standalone. Quit
> KAddressBook. Start Kontact.

Where? I just found a work-around for the MySQL issue under "Table 'mysql.
servers' doesn't exist" that I do not believe to really fix the bug. I
believe that /etc/akonadi/mysql-global.conf should just work. This might
be one of the packaging related issues, but I'd like to have upstream
feedback on that one as well.

My current work-around is just to close Kontact completely again and start
it another time. This will work for now.

Apart from that I am not interested in work-arounds. I am interested in
*fixes*.

Oh well and then there is:

---------------------------------------------------------------------
Environment Setup
The Akonadi server searches for Akonadi agents and resources in the paths
defined in the XDG_DATA_DIRS environment variable. If Akonadi complains
about not finding agents or resources, check if this variable is set
correctly. Also keep in mind that even if set in a current console
session, it might not have been set when starting the server. Starting the
server manually in the current console session excludes this cause.
---------------------------------------------------------------------

But why should I set it when it works automatically out of the box on
second start of Kontact?

I am hesitant to *fix* things by work-arounds that customize my Akonadi
installation and possible create problems on upgrades. I expect Akonadi to
just work *out of the box* and rather help with getting it into this
shape, by reporting each and any bug I find. Thats as much I can do as long
as I do not want to dig into Akonadi as a developer.

Ciao,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7

On 2010-05-06 Martin Steigerwald wrote:
> > Possible 'workaround' can be found at:
> > http://userbase.kde.org/Akonadi_4.4/Troubleshooting
> >
> > ie wrt 236538: close Kontact. Start KAddressBook standalone. Quit
> > KAddressBook. Start Kontact.
>
> Where?

3.8 I can't see any details in my Address Book

At the moment, the cause of this is not identified, but the cure is simple. Close Kontact, and start
KAddressBook as a stand-alone application. After you close it you will be able to use it within
Kontact. It seems that something is not being triggered when Kontact launches, and I expect this to
be identified and fixed soon. This seems to mainly affect version 4.4.0.

> My current work-around is just to close Kontact completely again and start
> it another time. This will work for now.
>
> Apart from that I am not interested in work-arounds. I am interested in
> *fixes*.

I'm interesting in fixes as well and not (so much) in workarounds.
But a workaround _could_ help in fixing the bug, although I'm not too sure in this case, since I got
the workaround from userbase.kde.org.

btw, I'm just confirming your findings, no need to bite my head off.

Diederik


--
To UNSUBSCRIBE, email to debian-kde-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 201005061230.16397.didi.debian@cknow.org">http://lists.debian.org/201005061230.16397.didi.debian@cknow.org

Am Donnerstag, 6. Mai 2010, 12:14:41 schrieb Martin Steigerwald:
> My current work-around is just to close Kontact completely again and start
> it another time. This will work for now.

The same here. The same problems, the same "work-around" and the same "I don't
wan't workarounds but bug fixes".

Hopefully this'll get fixed soon.

--
Mit freundlichen Grüßen / Best Regards
Dominik

Am Donnerstag 06 Mai 2010 schrieb Diederik de Haas:
> On 2010-05-06 Martin Steigerwald wrote:
> > > Possible 'workaround' can be found at:
> > > http://userbase.kde.org/Akonadi_4.4/Troubleshooting
> > >
> > > ie wrt 236538: close Kontact. Start KAddressBook standalone. Quit
> > > KAddressBook. Start Kontact.
> >
> > Where?
>
> 3.8 I can't see any details in my Address Book
>
> At the moment, the cause of this is not identified, but the cure is
> simple. Close Kontact, and start KAddressBook as a stand-alone
> application. After you close it you will be able to use it within
> Kontact. It seems that something is not being triggered when Kontact
> launches, and I expect this to be identified and fixed soon. This
> seems to mainly affect version 4.4.0.

Thanks. I overlooked this. For me its enough to just stop Kontact and
start it another time.

> > My current work-around is just to close Kontact completely again and
> > start it another time. This will work for now.
> >
> > Apart from that I am not interested in work-arounds. I am interested
> > in *fixes*.
>
> I'm interesting in fixes as well and not (so much) in workarounds.
> But a workaround _could_ help in fixing the bug, although I'm not too
> sure in this case, since I got the workaround from userbase.kde.org.
>
> btw, I'm just confirming your findings, no need to bite my head off.

Hey, I did not meant to bite your head off. I eat mostly vegan, but at
least vegetarian.

Thanks for your help!

Ciao,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7

Am Donnerstag 06 Mai 2010 schrieb Dominik Schulz:
> Am Donnerstag, 6. Mai 2010, 12:14:41 schrieb Martin Steigerwald:
> > My current work-around is just to close Kontact completely again and
> > start it another time. This will work for now.
>
> The same here. The same problems, the same "work-around" and the same
> "I don't wan't workarounds but bug fixes".
>
> Hopefully this'll get fixed soon.

Kevin Krammer fixed it. Thanks a lot!

See: http://bugs.debian.org/583566

For users with a 32-Bit Intel I uploaded Kevin's adapted package to

http://martin-steigerwald.de/tmp/debian-bug-583566/libakonadi-
kde4_4.4.4-1_i386.deb

temporalily.

Please test.

--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7