Version: Unbekannt (using 4.2.96 (KDE 4.2.96 (KDE 4.3 RC2)) "release 140", KDE:KDE4:Factory:Desktop / openSUSE_11.0) Compiler: gcc OS: Linux (x86_64) release 2.6.25.20-0.4-default I want to report a bug in the "download new wallpapers" tool within the desktop config dialog and hope this is the right place to do so. With this tool, there exists the problem that when you download a new wallpaper from kde-look, its title gets screwed up, some number is put in front of the real title. For example, if there is a wallpaper with the title "Nice Picture" it will show up in the wallaper list as something like "389457-nicepic". Of course, the real title would be much nicer :-)
Bug 138115 could be related.
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!
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? Thank you for helping us make KDE software even better for everyone!
This bug is still an issue for Plasma 5.22.5 on Manjaro (Linux 5.13.13-1), random numbers are placed in front of descriptive names. New wallpapers added through Desktop Folder Settings have a descriptive name preceded by a six digit number if there is only one size option for the image. If there is a choice of image size the filename is set as the image size in the format "0000x0000.jpg" and asks whether to overwrite the existing file of the same name, which would be the previous image of that size installed. My current solution is to rename the file manually after install and reload Desktop Folder Settings to see the newly renamed image in the wallpaper list.
Hi, kdelibs (version 4 and earlier) is no longer maintained since a few years. KDE Frameworks 5 or 6 might already have resolved this bug. If not, please re-open against the matching framework if feasible or against the application that shows the issue. We then can still dispatch it to the right Bugzilla product or component. Greetings Christoph Cullmann