dolfin team mailing list archive

[Anders Logg <logg@xxxxxxxxx>]

This sounds very bad but also very strange. How is it possible to
damage the file system? As far as I know, all we do is read and write
regular files in the current directory and sometimes in either
~/.instant/cache or /tmp.

--
Anders


On Mon, Aug 09, 2010 at 07:56:43AM -0000, Chris Richardson wrote:
> Public bug reported:
>
> 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
>
> ** Affects: dolfin
>      Importance: Undecided
>          Status: New
>

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