Today I completed the installation of KDE 4.5.1. I had previously compiled all parts of KDE 4.5.1 that could compile without pykde4-4.5.1-r1 because I had trouble with it compiling (see http://bugs.gentoo.org/show_bug.cgi?id=332503). I rebooted my PC and no apparent problems. Howeverm after I got pykde4-4.5.1-r1 compiled, and I compiled all the remaining packages of KDE 4.5.1, I rebooted again, and I noticed that the image I had been using for my desktop background was gone, and I just had a plain blue desktop. I figured that the settings simply got changed, so i went to set my desktop wallpaper back the way I wanted. Then I realized that I couldn't find the wallpaper I was using or, for that matter, and other image files I had in my /home/user directory. As far as I can tell, all other file types seemed to be untouched, but every image file I had in my /home/username/ directory was deleted. However, the images I had stored in /home/username/Pictures/ were still there, I think all teh image files I had were in .jpg format, although there might have been some .bmp images too. Very weird bug, and it would not be easy to try to reproduce this bug. Reproducible: Didn't try Steps to Reproduce: 1. have image files in ~/ directory 2. emerge -uv kde-meta 3. possibly reboot 4. check ~/ directory and see if the image files are still there. Expected Results: It should have left existing files in ~/ directory alone unless they were config files.
I guess it won't help asking if this happened again with newer kde versions? :] Seriously I have no idea what happend or what to do about this issue. Do you want to pursue this further or can we resolve it as NEEDINFO (=NOIDEA)?
(In reply to comment #1) > I guess it won't help asking if this happened again with newer kde versions? :] > > Seriously I have no idea what happend or what to do about this issue. Do you > want to pursue this further or can we resolve it as NEEDINFO (=NOIDEA)? > I'm just not sure. Apparently 4.5.1 was masked because I emerged kde-meta and went to 4.4.5, and it happened again. I'll soon be upgrading to 4.5.5, and I'll see if it happens again and see if maybe I can pinpoint what's causing it.
OK. In the meantime, since we all have no clue, I'll resolve the report...
