Notices

I have installed version 0.92.6. Unfortunately I can't enter "all day" events. If I mark "all day" the OK button is greyed out. I haven't found someone mentioning this before and wonder if its just me? Any help is highly appreciated.

In addition I would be glad if someone could quickly summarize the function of the "Layer" in the edit of the event categories. What does Foreground, Shallow, Deep, and Background meen?

Thanks in advance,
icke

If i delete the options file it will start up, until I change any options. And unfortunatly I have the week start on monday and i cant stand 24 hour time. lol

icke: Two possibilities - Seqretary is unhappy with your time zone, or the date in the end date for the event is less than the date for the start date. If it's the first case, what does /etc/localtime link to?

munky261: You really need to get gdb installed without that all I'm doing is taking stabs in the dark (it might not help, but when it does help the problem stands out fairly quickly). It's in the Diablo tools repository - enable it in the Application Manager

I installed gdb and ran it as your instructions saaid, it opened it and when i closed it it said it closed normally. then when i typed in trace it says it requires an argument

Not "trace".. flashback to an ancient debugger. "where". But this command is only useful when the segmentation violation occurs. You just need to cause it to SEGV and type in the "where" command then.

it opens and closes fine when opening through gdb, i dont get a fault....but i get it everytime if i just try to open it in normal command line

I think I may have found the cause of the problem, I have my personal menu set to run everything as root. Mainly just for emelfm2. when I became root then ran gdb and tried to launch seqretary it cam back with this...


Starting program: /usr/bin/seqretary
E Failed to execute dbus-launch to autolaunch D-Bus session

Program exited with code 01.

You shouldn't be running things as root unless they really need it. That said, it shouldn't SEGV because of that. Try adding xterm to Personal Menu, to run as root, and run inside GDB then. Running an xterm as "user" and becoming root by means of rootsh, root, sudo gainroot and such things will not necessarily give the same result.

Also see if a "core" file gets generated outside gdb. That could be helpful too, although I have never seen a core file generated on my system so there may be some trick to getting them generated on Maemo (which I have not fully investigated).

I reset personal menu so that only emelfm2 runs as root, and it still wont open.