Bug 387120

Summary: nscd - post-inst error ...
Product: [openSUSE] openSUSE 11.0 Reporter: Michael Meeks <mmeeks>
Component: NetworkAssignee: E-mail List <bnc-team-screening>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: captain.magnus
Version: Factory   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Michael Meeks 2008-05-06 10:14:31 UTC
Just running zypper dup under a live Gnome desktop and:

Downloading package nscd-2.8-9.i586, 62.0 K (123.0 K unpacked)
Downloading: nscd-2.8-9.i586.rpm [done]
Installing: nscd-2.8-9 [done]
Installation of nscd-2.8-9 failed:
(with --nodeps --force) Error: Subprocess failed. Error: RPM failed: error: failed to stat /home/michael/.gvfs: Permission denied
insserv: Service boot.setclock has to be enabled for service nscd
insserv: exiting now!
error: %post(nscd-2.8-9.i586) scriptlet failed, exit status 1

I have:

$ ls -ld /home/michael/.gvfs
dr-x------ 2 michael users 0 2008-05-01 17:43 /home/michael/.gvfs

and:

$ mount
/dev/sda2 on / type ext3 (rw,acl,user_xattr)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
debugfs on /sys/kernel/debug type debugfs (rw)
udev on /dev type tmpfs (rw)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
/dev/sda6 on /home type ext3 (rw,acl,user_xattr)
/dev/sda1 on /os103 type ext3 (rw,acl,user_xattr)
/dev/sda5 on /sled10 type ext3 (rw,acl,user_xattr)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
securityfs on /sys/kernel/security type securityfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
gvfs-fuse-daemon on /home/michael/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=michael)
192.168.0.7:/share on /share type nfs (rw,addr=192.168.0.7)

HTH.
Comment 1 Magnus Boman 2008-05-06 10:19:51 UTC
gvfs errors is not the issues here (see https://bugzilla.novell.com/show_bug.cgi?id=368628 for more information about that)

*** This bug has been marked as a duplicate of bug 384254 ***