Summary: | kcalendar-4.8.5 fails to update a calendar resource (ics) when it is changed | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Christian <k> |
Component: | ICal file resource | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | lasse.liehu, smartins |
Priority: | NOR | ||
Version: | 4.8 | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
Screenshot
english dialog |
Description
Christian
2012-09-08 10:53:47 UTC
Created attachment 73740 [details]
Screenshot
By the way, Kontact-4.8.3 had the same behaviour. > According to the text in the configuration dialog, when "read-only" is set and another program changes the ics file, Kontact will refresh the calendar to take into account the changes.
Can you double check that ? This text is the one for the third checkbox ("Enable file monitoring")
Created attachment 73746 [details]
english dialog
Here's a screenshot of the untranslated dialog
(In reply to comment #3) > Can you double check that ? This text is the one for the third checkbox > ("Enable file monitoring") Oh yes, you are right, the text is in the last checkbox called "Observation" ("Tarkkailu"). Maybe it's not clear enough... The text explains about the backup copy, but it does also say that whenever the file is changed its contents will be reloaded. So maybe what I don't get is why the notifications look like error messages. They should just be informations, if they are shown at all. In the case when "file monitoring" is not enabled and the file changes, maybe that should be an error? But in any case, if I tell Korganizer that it should monitor for changes, then it should of course also show me the current file contents in the calendar and not some old backup version. (It always shows the correct contents when I force it to refresh by e.g. logging out and logging in). Observation Observe the file (checkbox is checked) If observation is in use, the data source re-loads the file whenever other applications change its contents. It also attempts to create a backup copy in case of conflicts, if possible. Thanks. Changing the product > Oh yes, you are right, the text is in the last checkbox called "Observation" ("Tarkkailu").
Which locale do you use ? As you're using a yandex.ru address, I looked at the russian translation but that doesn't seem to match :-)
#. i18n: ectx: property (title), widget (QGroupBox, groupBox_MonitorFile)
#: singlefileresourceconfigdialog_desktop.ui:132
msgid "Monitoring"
msgstr "Мониторинг"
[...]
#. i18n: ectx: property (text), widget (QCheckBox, kcfg_MonitorFile)
#: singlefileresourceconfigdialog_desktop.ui:148
#: singlefileresourceconfigdialog_mobile.ui:65
msgid "Enable file &monitoring"
msgstr "Включить мониторинг файлов"
forget that, found it :) Adding the finnish translator Lasse, can you have a look at the comment #5 please ? this string is in akonadi_singlefile_resource.po I don't see anything wrong with the translations of "Monitoring" and "Enable file &monitoring", but suggestions are welcome. There was a mistake with the longer text, and the fixed version is: #. i18n: ectx: property (text), widget (QLabel, label_5) #: singlefileresourceconfigdialog_desktop.ui:138 msgid "" "If file monitoring is enabled the resource will reload the file when changes " "are made by other programs. It also tries to create a backup in case of " "conflicts whenever possible." msgstr "" "Jos tarkkailu on käytössä, tietolähde lataa tiedoston uudelleen muiden " "ohjelmien muutettua sitä. Se yrittää myös luoda varmuuskopion ristiriitojen " "varalta aina kun mahdollista." (change was: "muiden tiedostojen muutettua" -> "muiden ohjelmien muutettua") Thanks, guys! I'm on the Finnish locale. So the text seems to be correct in both Finnish and English, but the behaviour of Kontact is what I am referring to in my bug. When some other application updates the file and I have marked Kontact to "monitor" it, then the changes in the file should appear in Kontact when they happen. (Not just after I restart Kontact.) Or what do you think should happen? Can you tell me the exact phrasing of "Calendar - Writing to a read-only resource is being attempted.", in english ? I'd like to see where it's coming from Sorry for the delay. Here's the exact message in Finnish. ("E...R calendar" is the name of my calendar file.) "E...R calendar file: Tiedosto ”file:///home/ca/Projects/Technical/E...R calendar.ics” muuttui levyllä. Varotoimenpiteenä varmuuskopio sen aiemmasta sisällöstä luotiin kohteeseen ”file:///home/ca/.kde4/share/apps/akonadi_ical_resource_1/E...R calendar.ics-1”. Literally, it means "The file... has been changed on the disk. As a backup, a safety copy of its earlier contents has been created to the destination ..." Also, note that I'm now on 4.10.2 and the behaviour is still the same. Kontact was not even running while this notification was given. Judging from Christian's comment #12, the Finnish message is: Tiedosto ”%1” muuttui levyllä. Varotoimenpiteenä varmuuskopio sen aiemmasta sisällöstä luotiin kohteeseen ”%2”. And the English one is then: The file '%1' was changed on disk. As a precaution, a backup of its previous contents has been created at '%2'. from kdepim-runtime/resources/shared/singlefireresourcebase.cpp (line 230 in master) "Trying to write to a read-only file: '%1'." comes from kdepim-runtime/resources/shared/singlefileresource.h (line 168 in master). (By the way, the same message, only without the full stop, is also in kdepim-runtime/resources/contacts/contactsresource.cpp at lines 277 and 327 in master) This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present? If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months. Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input. |