Bug 167329 - taglib has no possibility to open a file readonly
Summary: taglib has no possibility to open a file readonly
Status: RESOLVED WORKSFORME
Alias: None
Product: taglib
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: Scott Wheeler
URL:
Keywords:
: 269395 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-07-24 00:20 UTC by lariamat
Modified: 2023-01-14 05:11 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description lariamat 2008-07-24 00:20:27 UTC
Version:           1.5 (using KDE 3.5.8)
Installed from:    Unspecified Linux
OS:                Linux

as far as I can see there is no possibility to open a file readonly with taglib. 
this affects tracker/beagle/strigi/any other indexer that uses inotify, because these reindex the file after reading the tag with taglib.
Comment 1 Lukáš Lalinský 2011-06-09 19:11:12 UTC
*** Bug 269395 has been marked as a duplicate of this bug. ***
Comment 2 anirudha.deglurkar 2012-02-01 18:17:45 UTC
Hi,

Any updates on this issue? This really creates problems for components that use inotify. They pick up spurious changes, when other components using Taglib ready the media files just to get the metadata. Any chance this can be fixed?
Comment 3 Manuel Amador (Rudd-O) 2012-02-01 22:26:39 UTC
Yes!  The inotify situation I also noticed.  Opening a file for write signals apps that want to know this.

NO APP should EVER open a file for writing UNLESS it is truly for writing.  Scanning tags is not that operation.
Comment 4 lariamat 2012-02-01 22:51:17 UTC
Wow. After 3.5 years this bug gets 2 comments on one evening but still is not confirmed.
I think I gave up on this topic 3.2 years ago.
Comment 5 Nikhil Marathe 2012-03-22 16:19:03 UTC
I notice that FileStream in master, does sport a openReadOnly attribute, but it is not being propagated up to the public API. Is this to preserve binary compatibility? Does this mean having to wait till 2.0?
Comment 6 Andrew Crouthamel 2018-11-06 15:05:06 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Andrew Crouthamel 2018-11-17 05:00:08 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Justin Zobel 2022-12-15 05:48:58 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 9 Bug Janitor Service 2022-12-30 05:22:17 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 10 Bug Janitor Service 2023-01-14 05:11:21 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!