During a Cauldron (M3) install ( 32-bit KDE ) an error is reported: An Error Occurred Error: 'script' failed for libgnome2-schemas-2.32.1-9.mga3.i586 Dismissing error install proceeded normally and booting to a KDE desktop was successful. After install a check of the above package indicates it successfully installed.
can you add the file /root/drakx/report.bug ?
CC: (none) => dmorganec, mageiaSeverity: normal => minor
Created attachment 3529 [details] drakx directory Here's the whole /root/drakx directory as a zip file
as it output the errors in the gui, setting the priority to blocker
Priority: Normal => release_blocker
Summary: libgnome2-schemas script protesting during cauldron install => libgnome2-schemas %post script protesting during cauldron installSource RPM: libgnome2-schemas-2.32.1-9.mga3.i586 => libgnome22.32.1-9.mga3.i586
Source RPM: libgnome22.32.1-9.mga3.i586 => libgnome2-2.32.1-9.mga3.i586
(gconftool-2:4879): GConf-WARNING **: Failed to load source "xml:readwrite:/root/.config/gconf": Failed: Could not make directory `/root/.config/gconf': No such file or directory Error setting value: Unable to store a value at key '/desktop/gnome/background/picture_options', as the configuration server has no writable databases. There are some common causes of this problem: 1) your configuration path file /etc/gconf/2/path doesn't contain any databases or wasn't found 2) somehow we mistakenly created two gconfd processes 3) your operating system is misconfigured so NFS file locking doesn't work in your home directory or 4) your NFS client machine crashed and didn't properly notify the server on reboot that file locks should be dropped. If you have two gconfd processes (or had two at the time the second was launched), logging out, killing all copies of gconfd, and logging back in may help. If you have stale locks, remove ~/.gconf*/*lock. Perhaps the problem is that you attempted to use GConf from two machines at once, and ORBit still has its default configuration that prevents remote CORBA connections - put "ORBIIOPIPv4=1" in /etc/orbitrc. As always, check the user.* syslog for details on problems gconfd encountered. There can only be one gconfd per home directory, and it must own a lockfile in ~/.gconfd and also lockfiles in individual storage locations such as ~/.gconf
CC: (none) => fundawang, olav
*** Bug 9253 has been marked as a duplicate of this bug. ***
CC: (none) => thierry.vignaud
updating as critical as it just blocks install for now.
CC: (none) => ennael1Severity: minor => critical
yesterday with a netinstall, there was this warning, then the install continue fine, you have not the same with isos ?
well that's a guess only for now as we have nearly no logs. Using iso, it just goes in a loop after printing this error in logs
On netinstall, it blocks the install by requesting a GUI response to continue. I think the issue is suspending the install until a response is given. BTW, this happens for a few other packages as well, e.g. mailman.
seems something changed in the installer, as before is was not reported in the gui, also, franck, please open a bug.
fixed with last version. bug 9267 opened for mailman
Status: NEW => RESOLVEDResolution: (none) => FIXED
Fixed here. Clean install then reboot to working desktop. No wrinkles in between. Many thanks to Manuel.
Summary: libgnome2-schemas %post script protesting during cauldron install => [RESOLVED]libgnome2-schemas %post script protesting during cauldron install