Calendar Crashes On 3.10 / 5500

[eekee]

About the first thing I noticed when I flashed 3.10 was that the calendar crashes when switched into month view. It dies immediately after (or in the last stages of) displaying the month layout, and the only extra info I get from starting it from the command line is qeclient_sendcommand(): server child accidentally finished! It's a particular nuisance because the calendar is the only app on there that I can't do without and I only ever use the month & day views. I would say I could get by with the week and year views but I'd lose newly-entered data to this problem often enough for it to be a real nuisance.

Is this a known problem that would be fixed with the 3.13 rom or suchlike? Could it have been a fault during the flashing session that maybe won't happen again? (hope hope hope!) I've no idea what to think, other than finding it mildy ironic that it was the calendar's broken before I've had a chance to start working on my own.

[acpkendo]

This is a well-documented bug. . . you have OpenSSH installed, don't you?

When calendar opens, it scans all of the files in the home directory (/home/zaurus on the Sharp ROM, IIRC).  The OpenSSH files in your home directory are readable only by root.  Calendar tries to read these files, can't, and crashes.

The solution is to change the permissions on the OpenSSH folder in your home directory to be world-readable (chmod 711 OpenSSH), or move them to another directory.

[Stubear]

It's not just openssh, but it is the most likely culprit.

Any folder or file under /home/zaurus that is not owned by zaurus will cause calendar to crash when switching to month view - this is because the calendar puts a little pin for every file you have modified and marks the modified date on the calendar.

The same is true for all folders/files under /mnt/card/Documents and /mnt/cf/Documents.

You can chmod them or chown them to be owned by zaurus or qpe group

Stu

[doseas]

Any folder or file under /home/zaurus that is not owned by zaurus will cause calendar to crash when switching to month view - this is because the calendar puts a little pin for every file you have modified and marks the modified date on the calendar.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=91343\"][{POST_SNAPBACK}][/a][/div]

You can turn off this feature by Option > Link File > (SD or CF) in the calendar.  You'll obviously have to be in some view other than Month View to run the app & turn it off, or do it by editing /home/zaurus/Settings/DateBook.conf:
  enableCF = 1
  enableSD = 1
(change the 1 to 0 in each of the above lines).

I believe that you need to kill the process and restart the calendar app, if you have it fast-loaded, before it sees the config file change.

[Stubear]

You can turn off this feature by Option > Link File > (SD or CF) in the calendar.  You'll obviously have to be in some view other than Month View to run the app & turn it off, or do it by editing /home/zaurus/Settings/DateBook.conf:
  enableCF = 1
  enableSD = 1
(change the 1 to 0 in each of the above lines).

I believe that you need to kill the process and restart the calendar app, if you have it fast-loaded, before it sees the config file change.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=91916\"][{POST_SNAPBACK}][/a][/div]

Or you can turn it off by changing to Ko/Pi

That was my solution cause when I'm testing stuff too directories get dodgy permissions to bother fooling around with, and the todo is combined with the calendar as I like it.

Stu

[beermad]

It's not just openssh, but it is the most likely culprit.

Any folder or file under /home/zaurus that is not owned by zaurus will cause calendar to crash when switching to month view - this is because the calendar puts a little pin for every file you have modified and marks the modified date on the calendar.

The same is true for all folders/files under /mnt/card/Documents and /mnt/cf/Documents.

You can chmod them or chown them to be owned by zaurus or qpe group

Stu
[div align=\"right\"][a href=\"index.php?act=findpost&pid=91343\"][{POST_SNAPBACK}][/a][/div]

Seems like it's not just the Documents subdirectory on the cards that it looks at. After I installed Perl and some other stuff on my SD card, the calendar suddenly started taking an amazingly long time to initialise (even when it was being kept in memory.) Seems that looking at 4 1/2 thousand files was a bit hard for it  

You've also explained what the little pin symbols were all about. I was wondering.

Cheers
Tony Green
http:www.beermad.org.uk

[danboid]

I'm getting exactly the same error mentioned in the first post on this thread and I can't start the calendar at all under Cacko 1.23b on C3000- well it flashes up briefly before closing itself.

I checked the Datebook.conf and those 2 options were already set to 0 and every file under the mentioned dirs is either owned by zaurus or root. I tried renaming datebook.conf then running the calendar again but I just get the same error. OpenSSH isn't installed and this only started happening after testing out a new battery which didn't work. The original is back in now and working fine.

By the sounds of things you're recommending I run a command like this:

chmod -R 711 /hdd3/Documents (everything under there is owner by root as ever)

chmod -R 711 /hdd2/Applications

I picked these two as they are linked to by default under /home/zaurus and owned by root whereas everthing else is owned by zaurus. I've not run those commands as I really don't think they will fix the problem as I know those dirs and there files were owned by root before this happened so I can't see it fixing anything, only causing more problems.

I don't want to reflash. I want to get this fixed as I could reflash and then it could happen again.