Custom Query (532 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (19 - 21 of 532)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
Ticket Resolution Summary Owner Reporter
#572 worksforme "Delete/Remove" old mails on quit - not working on *first* quit tboeckel Raziel
Description

Summary

When i have "deleted" mails sitting in "Trash" and quit YAM it won't delete them. When i restart YAM, those mails are still there and will get deleted when i quit YAM a second time.

Steps to reproduce

  1. Start YAM
  2. Produce some mails and delete them
  3. Quit YAM
  4. Reopen YAM - the mails are still in trash

(See below, it might be a problem with a second action performed)

Expected results

I have set Config in Startup/Quit to "Delete old mail", "Remove deleted mail" and like it to work as expected

Actual results

Deleted mails stay in Trash until i reopen YAM and quit it again

Regression

Not sure if it's a regression, i never really realized that there were mails still in Trash on a quit. I normally start YAM once and quit it once and then turn off the Amiga.

I don't know the inner workings of YAM but the only thing i could think of interfering here is the "Delete old mail" option...it's doing just that on quit, deleting mails older than 720 days in folders set up to do so.

Maybe that "search and destroy" of old mails keeps YAM from performing the second action of "removing deleted mails" and simply quits after it done it's first action?

After a restart of YAM (on the same day) there are obviously no old mails to delete (as it has been performed just before) so instead of being distracted to look for old mails YAM is actually performing the "Remove old mails" action.

That is, of course, a magnificient shot in the dark ;-)

Notes

Yam 2.9p1 [OS4/PPC] Compilation Date: 18.04.2014 (GCC 4.7.1.r7798)

AmigaOS4u6 (all updates)

#571 fixed Edit signature in external editor DSI tboeckel javierdlr
Description

Summary

When closing the external editor with the signature I'am editing I get a GR/DSI error.

#version SDH1:Comm/YAM/YAM full YAM 2.10-dev ( 5-07-2014) Copyright (C) 2000-2014 YAM Open Source Team [OS4/PPC, r8118]

Steps to reproduce

1.Go to Settings->Signature and click on 'Edit in external editor' (MSG_CO_EditSig) button 2.Without changing the signature close the external editor (in my case I use CodePad).

  1. GR/DSI error pops up

Expected results

External editor closes without any problem.

Actual results

GR/DSI when quitting external edutir with signature.

Regression

Notes

#569 worksforme Editing/saving address book sometimes corrupts it nbache
Description

Summary

Sometimes, but unfortunately not always, when I make a change in the address book and save it, the next time I start YAM, it crashes. When i check the contents of the .addressbook file, it has rearranged the entries and among other things put all the @ENDGROUP lines together at the end of the file.

I have tried starting a fresh address book and making a few groups and persons to see if I could reproduce it for this report, but unfortunately not. Today I even tried restoring my address book from my nightly backup and re-doing the exact change which made it happen, and it didn't happen again.

Steps to reproduce

  1. Have a largish address book with multiple groups and entries (?)
  2. Make a change to one of the entries
  3. Close YAM and start it again

Expected results

Normal start.

Actual results

A crash; sometimes a DSI (in fact many after each other, when one is ignored, the next one comes - eventually I just reboot), sometimes an "Unknown". I noticed LoadABook (or similar) close to the top. And I also see in the loading progress messages in the splash window that the address book is currently being loaded.

Regression

Notes

Sorry for the imperfect report. I thought I would be able to reproduce a "clean" test case and save a crash log from it, but couldn't (see above). I'll attach a crash log later if I get one. But it may not be so relevant - the crash is obviously caused by the already corrupted address book file, so the problem must be in the saving or editing of the address book. Anyway, I thought it was better to make this report than to keep silent about it.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
Note: See TracQuery for help on using queries.