Summary: | [FEATURES=test failure] gnome-base/nautilus-2.26.3 fails tests | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Patrick Lauer <patrick> |
Component: | New packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 69343, 263083 |
Description
Patrick Lauer
![]() Could you give the output of the following command line ? : $ pgrep -lu $USER gconfd-2 (In reply to comment #1) > Could you give the output of the following command line ? : > $ pgrep -lu $USER gconfd-2 > That's empty. Okay(In reply to comment #2) > (In reply to comment #1) > > Could you give the output of the following command line ? : > > $ pgrep -lu $USER gconfd-2 > > > > That's empty. > Okay the problem is these testsuites need to have a GConf daemon started to be executed correctly (apparently). Could you try to start /usr/libexec/gconfd-2 (in user) and try the testsuite again ? @herd: This problem is annoying in case where nautilus is merged on a non-GNOME environment without gconf running, like fluxbox or fvwm if the user wants to use nautilus as filemanager (I've a doubt but theorically nautilus should work even if gconf isn't running ? I meant it could use default settings ?) (In reply to comment #3) > > Could you try to start /usr/libexec/gconfd-2 (in user) and try the testsuite > again ? > It's just an idea for now, but it builds just fine here with gconf running... I ran the testsuite in a chroot logging in as root via ssh so it could not access the gconf from my user, unless it's doing something mystical, testsuite worked just fine. I'm pushing changes to fix bug #246136 in a minute without a bump, could you retry when you get those changes ? |