https://bugs.kde.org/show_bug.cgi?id=481741
--- Comment #16 from Fushan Wen ---
That indicates there is a deeper problem in plasmashell
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=481741
--- Comment #15 from Oded Arbel ---
My current workaround - with the bug fix - is to extract the image file using
the command `qdbus org.kde.plasmashell /PlasmaShell
org.kde.PlasmaShell.wallpaper 1 | awk '$1=="Image:"{print$2}' | sed
s,file://,,`
The
https://bugs.kde.org/show_bug.cgi?id=481741
--- Comment #14 from Oded Arbel ---
Thank you Fushan Wen. With the current version of plasma-workspace in Neon
testing, I can see that the D-Bus API response for `org.kde.plasmashell
/PlasmaShell org.kde.plasmashell.wallpaper` does indeed return the
https://bugs.kde.org/show_bug.cgi?id=481741
Fushan Wen changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
https://bugs.kde.org/show_bug.cgi?id=481741
Fushan Wen changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/plas
|
https://bugs.kde.org/show_bug.cgi?id=481741
--- Comment #11 from Oded Arbel ---
I pushed an MR with what I was doing and I would appreciate any feedback.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=481741
Bug Janitor Service changed:
What|Removed |Added
Status|CONFIRMED |ASSIGNED
--- Comment #10 from Bug
https://bugs.kde.org/show_bug.cgi?id=481741
--- Comment #9 from Nate Graham ---
Your plan sounds great!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=481741
--- Comment #8 from Oded Arbel ---
Thinking about it a bit more - as I've mentioned, I don't actually care about
the contents of the on-disk file, I just want the DBus APIs (direct responses
and shell scripting) to see the changes. I wonder if there's
https://bugs.kde.org/show_bug.cgi?id=481741
--- Comment #7 from Oded Arbel ---
(In reply to Nate Graham from comment #6)
> In the worst-case scenario where the user has the wallpaper changing every 5
> seconds and keeps the system on 24/7, that's over 17,000 writes daily--far
> more than the
https://bugs.kde.org/show_bug.cgi?id=481741
--- Comment #6 from Nate Graham ---
Sure, that's why I marked it as CONFIRMED. :) My point is that we need to
consider as a part of this how to avoid excessive config file writes. In the
worst-case scenario where the user has the wallpaper changing
https://bugs.kde.org/show_bug.cgi?id=481741
--- Comment #5 from Oded Arbel ---
(In reply to Nate Graham from comment #4)
> Depends on how much we want to prioritize avoiding writes to the config
> file, I guess. If the user does something silly like change their wallpaper
> every 5 seconds, we
https://bugs.kde.org/show_bug.cgi?id=481741
Nate Graham changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=481741
--- Comment #3 from Oded Arbel ---
This works better:
diff --git a/wallpapers/image/plugin/imagebackend.cpp
b/wallpapers/image/plugin/imagebackend.cpp
index e8d51ba2bf..754fb7077b 100644
--- a/wallpapers/image/plugin/imagebackend.cpp
+++
https://bugs.kde.org/show_bug.cgi?id=481741
--- Comment #2 from Oded Arbel ---
(In reply to Fushan Wen from comment #1)
> KConfigPropertyMapPrivate::writeConfigValue doesn't sync the config
> immediately
Can it? Should it? I understand performance reasons because disk IO sth sth,
but:
1. Will
https://bugs.kde.org/show_bug.cgi?id=481741
--- Comment #1 from Fushan Wen ---
KConfigPropertyMapPrivate::writeConfigValue doesn't sync the config immediately
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=481741
Bug Janitor Service changed:
What|Removed |Added
Keywords||qt6
--
You are receiving this mail
17 matches
Mail list logo
