CRITICAL **: unable to create directory '/root/.cache/dconf': Permission denied. dconf will not work properly. message on amd64 vm installation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubiquity (Ubuntu) |
Expired
|
Low
|
Unassigned |
Bug Description
The above message was seen in the terminal wondow when a networkless installation of 20120914 quantal desktop amd64 on a vm appeared to be hung.
The installation continued though without any issues after some time.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: ubiquity (not installed)
ProcVersionSign
Uname: Linux 3.5.0-14-generic x86_64
ApportVersion: 2.5.1-0ubuntu7
Architecture: amd64
Date: Sat Sep 15 19:57:55 2012
InstallCmdLine: noprompt cdrom-detect/
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120914)
ProcEnviron:
LANGUAGE=en_GB:en
TERM=xterm
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in ubiquity (Ubuntu): | |
importance: | Undecided → Low |
status: | New → Triaged |
tags: | added: rls-q-incoming |
11:26 <psivaa> cjwatson, just wondering if you need any further information for bug 1051388 before i go onto destroy the vm
11:28 <cjwatson> psivaa: in general we don't spend much effort on fixing messages that only appear in terminal output and that have no practical effect
11:29 <cjwatson> psivaa: we don't need anything else but it's low-priority
11:30 <psivaa> cjwatson, agree i saw a similar bug, just reported not to miss anything ::
11:30 <psivaa> :)
11:32 <xnox> psivaa: it's a bug in dconf.... and critical is a bit misleading since it doesn't crash nor burst into flames.
11:34 <psivaa> xnox, yes it was a little alarming at the time of that installation coz my hardware is not that powerful and the installation seemed very slow, and at times seemed hung.
11:35 <xnox> psivaa: the reason why your installation hang is unknown, but it's interesting that it was a networkless install and in the end of the syslog there are messages of "not being able to resolve host ubuntu"
11:35 <psivaa> yep that was going to be my next question, it correctly detected during the inital stage that there is no network
11:37 <psivaa> xnox, i.e. when it laid the checked conditions for available memory, power source and network connection.