A debian user reported [0] that Orage was outputting gtk critical message in the console, related to timezone. I can reproduce here, and it seems related to events timezone and not the timezone configured in orage (changing it doesn't change the messages). I can see: ** (orage:12264): CRITICAL **: convert_to_timezone: builtin timezone /softwarestudio.org/Tzfile/Europe/Paris not found, conversion failed. By the way, orage is really verbose in console at the moment, it'd be nice if it was a bit quieter. Thanks for the work. Cheers, -- Yves-Alexis
Can I see the orage.ics file, please. It seems like the timezone entry is corrupted. It should only be the Europe/Paris instead of the full path. Also the full path looks strange. It should not contain Tzfile but instead Olson_20011030_5 About verbosity....There is an undocumented parameter Logging level in the ~/.config/orage/oragerc file. Set that 50 or even to 100 and there will be much less messages. Logging level=60
Mine are generated by evolution so maybe there's a problem here. I'll ask the user if he can provide a simple ics file, and will try to reproduce here with a simple one. Btw, for the logging level, 0 is max and 100 is min? Could a default be set to something quieter anyway? :)
Evolution seems to use different timezones indeeed. It is fairly easy to make Orage compatible for those. But the original error report is clearly a corruption and it really would help to know if somebody can reproduce it or if it was created with earlier release of Orage. There has been bugs in the timezone selection, but those should be fixed in the current releases. Earlier corruptions in data, however, are not fixed.
(In reply to comment #3) > Evolution seems to use different timezones indeeed. > It is fairly easy to make Orage compatible for those. Ok. That would be nice :) (do you want me to open another "wishlist" bug for this?) > > But the original error report is clearly a corruption and it really would help > to > know if somebody can reproduce it or if it was created with earlier release > of Orage. There has been bugs in the timezone selection, but those should be > fixed in the current releases. Earlier corruptions in data, however, are not > fixed. > I've asked the initial bug reporter an sample ics file, I'll report back when I have it. Cheers,
Ok. That would be nice :) (do you want me to open another "wishlist" bug for this?) That would be nice actually. There may be more than the timezone compatibility issue and new BUB would make it much clearer than combining it there.
HMhmh, the user reported that it was only an “old” Orage file.
Then it is known and fixed issues. Orage 4.3 could create corrupted timezones. This is then duplicate of: Bug 2441 - crash on selecting timezones *** This bug has been marked as a duplicate of bug 2441 ***