...and leaves tons of sNNN.tmp files in the xfcalendar data directory. Sometimes the whole calendar data gets corrupted and not recoverable - Dunno if it's related to DBH? backtrace follows: #0 0x40720da2 in chunk_free (ar_ptr=0x407d4620, p=0x8187408) at malloc.c:3252 #1 0x40720bf4 in __libc_free (mem=0x8187410) at malloc.c:3154 #2 0x404aadd1 in DBH_close (node=0x80db238) at dbh_v.c:155 #3 0x404abae6 in DBH_regen (node=0x80db238) at dbh_v.c:536 #4 0x0804d53d in keep_tidy () at eval.c:41 #5 0x0804f4ad in main () at eval.c:41 #6 0x406bc507 in __libc_start_main (main=0x804f29c <main>, argc=5, ubp_av=0xbffff884, init=0x804c384 <_init>, fini=0x8051410 <_fini>, rtld_fini=0x4000dc14 <_dl_fini>, stack_end=0xbffff87c) at ../sysdeps/generic/libc-start.c:129
Trace back would tend to point to dbh, but nothing has changed here in a long time... Maybe there is some particular circumstance which is triggering the problem. I've noticed that if a system crash or something of the sort messes up the dbh file without messing up the header part of the file, problems may ensue. If you move your appointments.dbh file out of the way (do not delete, for further testing), and start afresh, does the problem remain? If so, is there anything particular about the data you introduce in your appointments?
Nothing special, except the the homedir is a NFS mounted directory.
I've just tested xfcalendar with a homedir set to a nfs mount, but no problem ensues. From the information that you have tons of sNNN.tmp files means that xfcalendar has been crashing many times in your case (one file for each crash). My suspicion is that your appointments.dbh file is corrupt, and therefore the crash. Does the problem dissappear if you remove $HOME/.config/xfce4/xfcalendar/appointments.dbh? If negative, then my guess is an incorrect memory access somewhere in xfcalendar.
I'll take a look after work this eve. Sorry for the late reply.
I think the could stem from a corrupt dbh file. In this case an easy fix is to check for the existance of sNNN.tmp files. If any exists, it means xfcalendar crashed while trying to regenerate the dbh file. So it would have to be deleted along with appointments.dbh. A popup dialog could inform the user or an error log file created. If the problem is not a corrupt dbh file, the above need not apply.
The crash occurs when updating the module. Unavoidable IMO.
Is this still active ? 4.3 is not using dbh anymore. Can we close this one?
I believe the bug could be due to a free to a dbh pointer that the application should not mess around with. Since this is no longer a possibilty, the bug report should be closed IMO.
not relevant with 4.4 and will not be fixed for 4.2
Moving all bugs to new Orage product.