Bug 278834 - Bookmark icons should not be stored in cache directory
Summary: Bookmark icons should not be stored in cache directory
Status: RESOLVED WORKSFORME
Alias: None
Product: konqueror
Classification: Applications
Component: bookmarks (show other bugs)
Version: 4.6.5
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-30 07:22 UTC by Alex Hermann
Modified: 2023-01-13 05:14 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Hermann 2011-07-30 07:22:13 UTC
Version:           4.6.5
OS:                Linux

The bookmark icons are stored in the cache directory, which is, by default, not shared among different machines, like the homedir is. Because of this, a bookmark added at one machine has no icon on all other machines.

Another failure case i noticed recently is when the /var/tmp is mounted on a tmpfs (to save SSD wear, a use-case becoming more common nowadays). Being a cache, it shouldn't matter to an application if the data in it disappears between application invocations. It should only result in a somewhat slower response, not failure. Bookmark icons _do_ fail however.

Suggested fix: move icons associated with bookmarks to a persistent folder (not all favicons from visited sites).

Since i wiped the /var/tmp/kdecache-${USER} directory, bookmark icons seem to be the only persistent data missing.


Reproducible: Always

Steps to Reproduce:
1) Bookmark a site having an icon
2) Log out of KDE
3a) Wipe /var/tmp/kdecache-${USER}
OR
3b) Switch to another machine with a shared homedir
4) Log into KDE again


Actual Results:  
5) Notice how bookmark icons are gone and will not return (automatically).


Expected Results:  
5) Icons are still present

OS: Linux (x86_64) release 2.6.39-2-amd64
Compiler: gcc
Comment 1 Andrew Crouthamel 2018-11-06 15:09:49 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 2 Andrew Crouthamel 2018-11-17 04:52:51 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 3 Justin Zobel 2022-12-14 03:09:16 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 4 Bug Janitor Service 2022-12-29 05:23:59 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 5 Bug Janitor Service 2023-01-13 05:14:55 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!