On Thursday 27 January 2011 20:21:47 you wrote:
> Dear Anne,
> thanks for the reply
>
> On Thu, 27 Jan 2011, Anne Wilson wrote:
> > I've not had this problem in korganizer, but I have seen it with other
> > kontact modules. I find that the best thing is to killall kontact and
> > wait a few secon
On Thu, 2011-01-27 at 23:10 +0100, Walter Cazzola wrote:
> just to add something to my problem, this affect only my user, from
> root korganizer starts like a charm.
General note:
When debugging, create another ordinary user account to test things. Do
not simply become root, and start debugging
On Thursday, January 27, 2011 04:10:46 pm Walter Cazzola wrote:
> Dear all,
> just to add something to my problem, this affect only my user, from root
> korganizer starts like a charm. I've noticed that it is bound to the
> akonadi server but also killing all the process related to akonadi
> korgan
Dear all,
just to add something to my problem, this affect only my user, from root
korganizer starts like a charm. I've noticed that it is bound to the
akonadi server but also killing all the process related to akonadi
korganizer from my user doesn't start.
:-(
any help is appreciated
Walter
O
Dear Anne,
thanks for the reply
On Thu, 27 Jan 2011, Anne Wilson wrote:
I've not had this problem in korganizer, but I have seen it with other kontact
modules. I find that the best thing is to killall kontact and wait a few
seconds, after which everything works again. I assume that something
On Thursday 27 January 2011 17:45:39 Walter Cazzola wrote:
> Dear all,
> today after an attempt of adding a new calendar korganizer has crashed
> and from that moment on it is impossible to access to the GUI and to my
> data. Doesn't a matter if I launch it from the tray, from the
> commandline or
Dear all,
today after an attempt of adding a new calendar korganizer has crashed
and from that moment on it is impossible to access to the GUI and to my
data. Doesn't a matter if I launch it from the tray, from the
commandline or from the menu.
When I try to launch it I get the following message:
