Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 31330

Summary: background selected in control panel for kdm does not work if not in kde's wallpaper dir
Product: Gentoo Linux Reporter: Rick Warner <rick>
Component: [OLD] KDEAssignee: Gentoo KDE team <kde>
Status: RESOLVED FIXED    
Severity: normal CC: greg_g
Priority: High    
Version: 1.4   
Hardware: x86   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Rick Warner 2003-10-16 21:28:04 UTC
I use /usr/share/wallpapers for my custom wallpapers/backgrounds.  When choosing 
a background for kdm in 'control panel->system administration->login manager', 
wallpapers in /usr/share/wallpapers show up in the list without needing to go to the 
browser button.  They are selected and applied without error.  kdm does not show 
the background however.  It seems the /usr/share/wallpapers/ prefix is left off of the 
file name that is saved in /usr/kde/3.1/share/config/kdm/backgroundrc.  After adding 
the full path, it loaded the file fine. 

Reproducible: Always
Steps to Reproduce:
1.put some wallpaper in /usr/share/wallpapers 
2.select that wallpaper for background in control panel->sys admin->login manager 
3.check kdm- wallpaper is not shown 
Actual Results:  
background not shown	 

Expected Results:  
background shown 

I don't think any additional info is needed for this problem.  Email me if more info is 
needed.
Comment 1 Olle Hällnäs 2004-02-07 11:56:36 UTC
run genkdmconf, it will update the configfile and add an entry named BackgroundCfg in /usr/kde/3.2/share/config/kdm/kdmrc
This should solve it.
Comment 2 Dominik Stadler (RETIRED) gentoo-dev 2004-02-10 12:21:24 UTC
Did the suggested resolution fix the problem?
Comment 3 Rick Warner 2004-02-10 16:21:00 UTC
genkdmconf does not exist in the 3.1 series kde.  I was able to work around the problem by manually editting kdmrc and setting the full path to the background image
Comment 4 Dominik Stadler (RETIRED) gentoo-dev 2004-03-19 10:13:13 UTC
Workaround available and as far as I can see should not be a problem in 3.2.x, therefore closing this bug. Please reopen if this is still an issue.