Bug 134175 - KOrganizer crashes on boot; won't open
Summary: KOrganizer crashes on boot; won't open
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: 3.3
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-16 19:01 UTC by Holly
Modified: 2010-06-20 16:23 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
KOrganizer Console Output (5.01 KB, text/plain)
2006-09-20 03:37 UTC, Holly
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Holly 2006-09-16 19:01:35 UTC
Version:           3.3 (using KDE KDE 3.5.4)
Installed from:    Ubuntu Packages
OS:                Linux

A couple days ago, the KOrganizer daemon disappeared from the system tray, leaving a blank space where it was suppose to be. Upon reboot, it started up in an open window (the daemon didn't open) and just sat there until it crashed via the Terminate message.

After that, opening it failed. It appears on the taskbar, does the bouncing cursor thing and just disappears. However, oddly, a process for it is created in the process table. Two, actually; one of them is always using about 30+% system resources. I've found that if I leave that process running and reboot, it does the same thing as I noted above (starts in open window, crashes). I fear it might be a problem with the systray, but that doesn't make sense because everything else is working fine. Other KDEPIM apps also work fine.

I tried to reinstall it, though I didn't reboot between the uninstall and the reinstall (I'm afraid of what removing the kubuntu-desktop package will do to my system).

Please advise; I really need KOrganizer...

Thanks!
Comment 1 Holly 2006-09-16 21:44:05 UTC
Okay... I removed everything for KDE PIM, rebooted, and then reinstalled KOrganizer. Now it will only start as root, and that's only if I told it to start before rebooting. The systray daemon doesn't work anymore, either. Starting it in the console informs me that it crashed.

Is there any way for me to toally remove KDE PIM, as if it was never installed, and start from scratch with it again? Without having to reinstall Kubuntu, as I'm sick of doing OS reinstalls... I had that enough with Suse. Simply reinstalling it doesn't effect it at all.. I'm starting to think something else is preventing it from working right.
Comment 2 Allen Winter 2006-09-17 23:44:13 UTC
Holly,

The name of the KOrganizer reminder daemon program is "korgac".

Could you try running korgac from a konsole command line?
And then post the output (if any) from korgac?

I wonder if you put a reminder into your KOrganizer calendar that simply confuses the heck out of korgac.
Comment 3 Philip Rodrigues 2006-09-18 00:09:18 UTC
You could also try creating a new user and running korgac with that user. If it works there, you've probably got a config problem with your initial user
Comment 4 Holly 2006-09-18 15:22:45 UTC
Oh... "korgac" is something for KOrganizer? In the process table, whenever I ran KOrganizer, that would be there, too. I think it stayed there whenever I killed KOrganizer, too.... *checks* No, wait, no it doesn't.. I saw it there once though.

At any rate; I get absolutely nothing running it in the terminal. Same with KOrganizer; I type it, hit enter and it makes it look like it's going to do something but then it just sits there and doesn't let me type anythinge else.

The user thing sounds like a good idea; I'll try it since KOrganizer does seem to run in root, albeit in a strange way (see above).

Thanks, guys!
Comment 5 Holly 2006-09-18 22:10:58 UTC
Alright, I made a new user account and KOrganizer does indeed work just fine in it. It opens and everything. Kontact also opens, despite throwing me the "could not find mail part" error, which it gives me in my primary user account before not opening.

So, how do I go about fixing my user config so KOrganizer can work again? I'd rather not switch over to the new user account, since it comes with problems: my sound card isn't recognised and for some reason I can't login as root, although that might be due to my lack of understanding with KDE's user system.

Thanks!
Comment 6 Allen Winter 2006-09-18 22:59:45 UTC
We still don't know if the problem is in your korganizer configuration or in your korganizer calendar.

Next step:  copy your "bad" user's korganizerrc into your new user account, like so

As root:
cp /home/olduser/.kde/share/config/korganizerrc /home/newuser/.kde/share/config
chown newuser:newusergroup /home/newuser/.kde/share/config/korganizerrc

then start korganizer for newuser.

see if that works.  if it does, the problem is almost certainly in the "bad" users calendar
Comment 7 Holly 2006-09-19 05:18:13 UTC
Alrighty; I did it and KOrganizer still works just fine in the new user. Should I give you the contents of the RC file?
Comment 8 Allen Winter 2006-09-19 22:49:34 UTC
Holly,

This makes me believe that you have a reminder in your calendar(s) that simply drives korgac nuts.

The next test is to start with a fresh, empty calendar as your regular user.

Move the current calendar to a safe place:
Quit KOrganizer (or Kontact)
% cd ~/.kde/share/apps/korganizer; mv std.ics std-save.ics

Logout and back in again.  See if korgac starts ok.

We really should take this to a mailing list.  Would you like to join the kdepim-users@kde.org mailing list?  That way we might find others who have had the same problem.  See https://mail.kde.org/mailman/listinfo/kdepim-users

Comment 9 Holly 2006-09-20 03:36:32 UTC
Alrighty; I joined the mailing list.

I also changed the name of the calendar file, but it didn't do any good. However, I went into the directory and was able to open the file just fine (it's empty, I assume that's because of the number of times I uninstalled, reinstalled KOrganizer, Kontact, etc.) KOrganizer won't open by itself, though, but this time I did get a readout when I entered it in the console and it still creates a process for it. I've attached the console readout.

Running "korgac" still doesn't do anything, and it still isn't listed with KOrganizer on the process table.
Comment 10 Holly 2006-09-20 03:37:57 UTC
Created attachment 17846 [details]
KOrganizer Console Output
Comment 11 Reinhold Kainhofer 2006-11-02 19:22:13 UTC
Reassigning all KOrganizer bug reports and wishes to the newly created 
korganizer-devel mailing list.
Comment 12 FiNeX 2008-11-19 20:24:31 UTC
Changed severity to "crash". I hope to have selected only the right bugs (>100) :-)
Comment 13 frederico pflug 2008-12-10 01:05:50 UTC
hi folks,
i was having the same issue with kde4.1. it was working with new user.
i updated kdepim* today to 4.1.3-71.3 and together with that libical0 to 0.40-2.1. all working fine now.
Comment 14 Sergio Martins 2009-03-09 03:42:36 UTC
Holly, did the suggestion in comment 13 work for you?
Comment 15 Sergio Martins 2010-06-20 16:23:13 UTC
No feedback in one year, and fixed for commenter #13