I'm using gnome-panel, gnome-applets, metacity and gdm and not the rest of gnome-package. Now, I cannot create new launchers. If I trie to create one, it tells me that it "cannot write file:///home... Unknown URI". I just deleted everything that lokked like gnome, gconf or anything in my home-dir but it did not change anything. The appropriate folders are created but launchers cannot be created.
Hmm gnome-panel alone depends on quite some more gnome stuff then you mention here, exactly what version of every mentioned component do you have around ?
I did an "emerge gnome-panel gnome-applets metacity gdm" and I did emerge -u world every day in hope it would work. So if the specification of the dependencies in the gnome-panel-ebuild is correct, I should have everything I need. Which packages do you think could be missing?
I still need to know the versions... i don't say you're missing anything. Are your permissions correct in the first place ? Do you have gnome-vfs around ?
okay, here my versions: gnome-vfs: 2.0.4.1 gnome-panel: 2.0.11 gnome-applets: 2.0.4 libgnome: 2.0.6 libgnomeui: 2.0.6-r1 gtk+: 2.0.9 gnome-desktop: 2.0.10 I hope this is what you need, ask again if not.
Those seem fine to me. Are this permissions on your home-dir correct ? What is the output of 'qpkg -l gnome-vfs-2.0' ?
I checked permissions, they're alright. qpkg .. gave me just "command not found". ;-) I now emerged gentoolkit and the output is quite large, I put it onto http://bernd-wurst.de/gentoo/qpkg.txt (I did a redirect, so you can see the apropriate colors if you want, hope it's okay.)
There's your problem i think, it doesn't install the so's . Can you gimme the full output of a gnome-vfs emerge ?
Here it is: http://bernd-wurst.de/gentoo/gnome-vfs.txt Hope that helps.
After rebuiling of gnome-vfs to produce the requested output, I restarted gdm and now it works! I previously re-emerged gnome-panel but I didn't know about the importance of gnome-vfs. So it works for me now! Thanks a lot! ;-)
Hmm yeah, but now it works i can't really figure out what the real problem was.
*** Bug 11641 has been marked as a duplicate of this bug. ***
