https://bugs.kde.org/show_bug.cgi?id=522210

            Bug ID: 522210
           Summary: KRunner emits warning logs every invocation: "Chrome
                    runner: could not open iconFile for writing."
    Classification: Plasma
           Product: krunner
      Version First 6.7.1
       Reported In:
          Platform: Gentoo Packages
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: bookmarks
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected], [email protected]
  Target Milestone: ---

DESCRIPTION
Every time when KRunner is invoked, a lot of warning logs are emitted in the
syslog:

Jun 26 16:46:07 kita krunner[3654]: Chrome runner: could not open iconFile 
"/home/user/.cache/bookmarksrunner/KRunner-Favicons-Profile 3/45588_favicon" 
for writing.
Jun 26 16:46:07 kita krunner[3654]: Chrome runner: could not open iconFile 
"/home/user/.cache/bookmarksrunner/KRunner-Favicons-Profile 3/43376_favicon" 
for writing.
Jun 26 16:46:07 kita krunner[3654]: Chrome runner: could not open iconFile 
"/home/user/.cache/bookmarksrunner/KRunner-Favicons-Profile 3/51653_favicon" 
for writing.
Jun 26 16:46:07 kita krunner[3654]: Chrome runner: could not open iconFile 
"/home/user/.cache/bookmarksrunner/KRunner-Favicons-Profile 3/14495_favicon" 
for writing.

STEPS TO REPRODUCE
1. Enable the "Bookmarks runner" and have some bookmarks.
2. Invoke KRunner and observe the logs.

OBSERVED RESULT
There should not be any warning logs.

EXPECTED RESULT
KRunner emits a lot of warning logs.
The directory at "/home/user/.cache/bookmarksrunner/KRunner-Favicons-Profile 3"
does not exist. Manually creating it doesn't help - the directory gets removed
and the logs still appear.

SOFTWARE/OS VERSIONS
Operating System (available in the Info Center app, or by running `kinfo` in a
terminal window):
KDE Plasma Version: 6.7.1
KDE Frameworks Version: 6.27.0
Qt Version: 6.11.1

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to