Bug 74886 - Annoying Error-messages when trying to set Background-Images from a reiserfs4-partition.
Summary: Annoying Error-messages when trying to set Background-Images from a reiserfs4...
Status: RESOLVED WORKSFORME
Alias: None
Product: kcontrol
Classification: Miscellaneous
Component: kcmbackground (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-10 23:41 UTC by Mehdi Salem
Modified: 2007-04-30 23:00 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mehdi Salem 2004-02-10 23:41:24 UTC
Version:            (using KDE KDE 3.2.0)
Installed from:    Compiled From Sources
Compiler:          gcc-3.2.3 
OS:          Linux

I have disconvered a problem with KDE that I suspect to be a bug. I have compiled KDE-3.2.0 the first day after its release and was very impressed. But then, when trying to set the background-image for my desktop to some favourite pictures I realized, this wouldn't work without an Error message that said picture.xy was a file, but a folder was expected. I recompiled kde many times to be sure nothing had gone wrong during the compilation and installation (I had used some selfwritten shellscripts to do that, and I thought I could have done something wrong) but this didn't solve the problem so I went on experimenting until I discovered, that this problem only happens when the images are on a reiserfs4 partition. Reiserfs3 just works fine. I got rid of the problem by moving all the images onto a reiserfs3 partition. I found another interesting bugreport regarding reiserfs4 on the kde-bug lists (BUG 69349) : 
1)reiserfs4 have files that are also directories
http://www.namesys.com/v4/v4.html#files_dirs.
Will the problem be solved before the stable Version of reiserfs4 is released soon, and is it a bug at all or did I do something wrong or missed to set some flags for the filesystem?
Comment 1 Waldo Bastian 2005-03-31 14:13:18 UTC

*** This bug has been marked as a duplicate of 69349 ***
Comment 2 Waldo Bastian 2005-03-31 14:16:26 UTC
Oops that was a different bugreport than I thought...
Comment 3 Philip Rodrigues 2007-03-08 23:04:33 UTC
Does this problem still occur with KDE 3.5?
Comment 4 Philip Rodrigues 2007-04-30 23:00:29 UTC
Feedback timeout, but please reopen if the problem still occurs in KDE 3.5. Thanks!