dolfin team mailing list archive

[Chris Richardson <615250@xxxxxxxxxxxxxxxxxx>]

I have reproduced the bug on a 64-bit machine, here is some output... 
First, I ran the poisson demo as a regular user, and save the output from "strace -f python demo.py" - attached.


** Attachment added: "strace -f python demo.py"
   http://launchpadlibrarian.net/53409019/snapshot.png

-- 
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