dolfin team mailing list archive

[Chris Richardson <615250@xxxxxxxxxxxxxxxxxx>]

It is still trying to do it (this is the latest development version of
dolfin):-


[pid  2407] stat("/", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
[pid  2407] open("/", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = 3
[pid  2407] getdents(3, /* 41 entries */, 32768) = 1160
[pid  2407] unlink("//opt")             = -1 EACCES (Permission denied)
[pid  2407] unlink("//initrd.img.old")  = -1 EACCES (Permission denied)
[pid  2407] unlink("//initrd.img")      = -1 EACCES (Permission denied)
[pid  2407] unlink("//lib64")           = -1 EACCES (Permission denied)
[pid  2407] unlink("//vmlinuz.old")     = -1 EACCES (Permission denied)
[pid  2407] unlink("//vmlinuz")         = -1 EACCES (Permission denied)
[pid  2407] getdents(3, /* 0 entries */, 32768) = 0
[pid  2407] close(3)                    = 0
[pid  2407] open("/", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = 3
[pid  2407] getdents(3, /* 41 entries */, 32768) = 1160
[pid  2407] close(3)                    = 0

-- 
Failed X connection corrupts root filesystem
https://bugs.launchpad.net/bugs/615250
You received this bug notification because you are a member of DOLFIN
Team, which is subscribed to DOLFIN.

Status in DOLFIN: New

Bug description:
I noticed this problem a while ago, and just fell victim to it again this morning.

I was doing a dolfin install from bzr as root on Ubuntu Lucid 10.4 64-bit server.
When running a demo, if the X forwarding is not correctly set, then the code crashes in a plot() call, with a PETSC error. Subsequently, the root file system is severely damaged, and the only option seems to be a complete reinstall of the OS.

I know, this can be avoided by not running the demos as root, but it is an easy mistake to make after doing a system-wide install.
I presume it is a bug in viper.

Any ideas?

Thanks

Chris Richardson