Bug 84219 - Single threading assumption causes incorrect bookmarks update in Konqueror
Summary: Single threading assumption causes incorrect bookmarks update in Konqueror
Status: RESOLVED UNMAINTAINED
Alias: None
Product: konqueror
Classification: Applications
Component: bookmarks (show other bugs)
Version: 3.1
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
: 92588 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-06-29 20:04 UTC by Robert Dick
Modified: 2012-06-18 14:11 UTC (History)
1 user (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 Robert Dick 2004-06-29 20:04:08 UTC
Version:           unknown (using KDE 3.1.4)
Installed from:    SuSE
Compiler:          gcc version 3.3.1 (SuSE Linux)
OS:                Linux (i686) release 2.4.21-226-athlon

If a instance of konqueror running on another machine modifies a shared bookmarks file, konqueror does not notice this.  Konqueror, therefore, gets out of sync with its own bookmars file.  This problem is aggravated by the use of preloaded konqueror instances.  However, the right fix is checking the bookmarks file for changes, not manually making things single-threaded by killing all konqueror instances whenever a process on another machine changes the bookmarks file.  This problem could be fixed by checking the bookmarks file for changes, or checking its timestamp, each time the bookmarks menu is accessed.
Comment 1 Daniel Teske 2005-07-01 02:54:00 UTC
*** Bug 92588 has been marked as a duplicate of this bug. ***
Comment 2 Jaime Torres 2008-07-20 00:28:32 UTC
If I modify the bookmark.xml file manually, the bookmark menu is not altered, but the bookmark editor reads the file and uses it.
Tested in 4.1.60 svn trunk 831729
Comment 3 Myriam Schweingruber 2012-06-18 14:11:13 UTC
Message from the Bugsquad and Konqueror teams:
This bug is closed as outdated, as we do not have the manpower to maintain the KDE3 version anymore.
If you still can reproduce this issue with Konqueror 4.8.4 or later, please open a new report.
Thank you for your understanding.