https://bugs.kde.org/show_bug.cgi?id=479296
--- Comment #10 from tnem...@free.fr ---
(In reply to John Kizer from comment #9)
> For what it's worth, I can't reproduce this on a Fedora KDE 42 VM.
:'(
> Just checking - does this bug still occur with files in the base folder for
> the slideshow, ex. not inside of subfolders? Just thinking if that's a
> possible factor?
I don't understand... The symlinks were (and still are) at the base folder
for the slideshow : there are no slideshow subfolders.
I tried another thing :
```bash
$ mkdir ~/Wallpapers
$ cd ~/Wallpapers
# Find all target files and link them locally with different names depending on
their path...
$ for i in ~/Images/Fonds/diaporama/* ; do j=$(realpath $i) ; l=$(basename $i)
; if echo "$j" | grep -qs Next ; then l=$(echo "$j" | sed
's,.*Breeze/\([^/]*\)/.*,\1.png,') ; fi ; ln -s $j $l ; done
$ ls -l
lrwxrwxrwx - thomas 23 juin 18:36 kali-3840x2160.png ->
/home/thomas/Images/Fonds/Kali/3840x2160.png
lrwxrwxrwx - thomas 23 juin 18:36 kali-cubism-16x9.jpg ->
/home/thomas/Images/Fonds/Kali/kali-cubism-16x9.jpg
lrwxrwxrwx - thomas 23 juin 18:36 kali-layers-16x9.png ->
/home/thomas/Images/Fonds/Kali/kali-layers-16x9.png
lrwxrwxrwx - thomas 23 juin 18:36 Next-v5.2.0.png ->
/home/thomas/Images/Fonds/Breeze/Next-v5.2.0/contents/images/2560x1440.png
lrwxrwxrwx - thomas 23 juin 18:36 Next-v5.3.0.png ->
/home/thomas/Images/Fonds/Breeze/Next-v5.3.0/contents/images/2560x1440.png
lrwxrwxrwx - thomas 23 juin 18:36 Next-v5.4.0.png ->
/home/thomas/Images/Fonds/Breeze/Next-v5.4.0/contents/images/2560x1440.png
lrwxrwxrwx - thomas 23 juin 18:36 Next-v5.6.0.png ->
/home/thomas/Images/Fonds/Breeze/Next-v5.6.0/contents/images/2560x1440.png
lrwxrwxrwx - thomas 23 juin 18:36 Next-v5.7.0.png ->
/home/thomas/Images/Fonds/Breeze/Next-v5.7.0/contents/images/2560x1440.png
lrwxrwxrwx - thomas 23 juin 18:36 Next-v5.8.0.png ->
/home/thomas/Images/Fonds/Breeze/Next-v5.8.0/contents/images/3840x2160.png
lrwxrwxrwx - thomas 23 juin 18:36 Next-v5.9.0.png ->
/home/thomas/Images/Fonds/Breeze/Next-v5.9.0/contents/images/3840x2160.png
lrwxrwxrwx - thomas 23 juin 18:36 Next-v5.10.0.png ->
/home/thomas/Images/Fonds/Breeze/Next-v5.10.0/contents/images/3840x2160.png
lrwxrwxrwx - thomas 23 juin 18:36 Next-v5.12.0.png ->
/home/thomas/Images/Fonds/Breeze/Next-v5.12.0/contents/images/3840x2160.png
lrwxrwxrwx - thomas 23 juin 18:36 Next-v5.13.0.png ->
/home/thomas/Images/Fonds/Breeze/Next-v5.13.0/contents/images/3840x2160.png
lrwxrwxrwx - thomas 23 juin 18:36 Next-v5.22.png ->
/home/thomas/Images/Fonds/Breeze/Next-v5.22/contents/images/3840x2160.png
lrwxrwxrwx - thomas 23 juin 18:36 Next-v5.24.png ->
/home/thomas/Images/Fonds/Breeze/Next-v5.24/3840x2160.jpg
lrwxrwxrwx - thomas 23 juin 18:36 Next-v5.26.png ->
/home/thomas/Images/Fonds/Breeze/Next-v5.26/3840x2160-dark.png
lrwxrwxrwx - thomas 23 juin 18:36 Next-v6.2.png ->
/home/thomas/Images/Fonds/Breeze/Next-v6.2/3840x2160.png
lrwxrwxrwx - thomas 23 juin 18:36 Next-v6.3.png ->
/home/thomas/Images/Fonds/Breeze/Next-v6.3/3840x2160.png
```
I got _exactly_ the same result as previously...
But it made me think... There are a lot of target files that have the same name
(ie: 3840x2160.png). Could that be the reason ?
[...]
I think that's it.
Here is what I did :
```bash
$ cd ~/Wallpapers
$ rm -f *
$ mkdir images
$ cd images
# Here I copy the files each under a different name in the
"~/Wallpapers/images" directory...
$ for i in ~/Images/Fonds/diaporama/* ; do j=$(realpath $i) ; l=$(basename $i)
; if echo "$j" | grep -qs Next ; then l=$(echo "$j" | sed
's,.*Breeze/\([^/]*\)/.*,\1.png,') ; fi ; cp $j $l ; done
$ cd ..
$ mkdir slideshow
$ cd slideshow
# create symlinks, each to a file with a different target name
$ ln -s ../images/* .
```
And now I have all my wallpapers !
--
You are receiving this mail because:
You are watching all bug changes.
