dolfin team mailing list archive

[Johannes Ring <615250@xxxxxxxxxxxxxxxxxx>]

OK, thanks.

** Changed in: dolfin
       Status: New => Fix Committed

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

Title:
  Failed X connection corrupts root filesystem

Status in DOLFIN:
  Fix Committed

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