Fatal IO Error

[Mark Bennison]

Ubuntu 12.04, 64bit
Mundus 2.3.0 (from ppa)

I was attempting to clean blender when the program hit a fatal error as it said it didn't have permissions to remove a file. It turns out that this was a link to /usr/share which I manually removed. I then re-ran mundus, which claimed it was running (but it wasn't) and I got the following dialogue on cleaning blender again:

Cleaning directory ~/.blender/scripts Done
Cleaning directory ~/.blender/bpydata Directory has content
Cleaning file ~/.blender/bpydata/readme.txt Done
Cleaning file ~/.blender/bpydata/KUlang.txt Done
Cleaning directory ~/.blender/bpydata/config Directory has content
Cleaning file ~/.blender/bpydata/config/readme.txt Done
Deleting directory ~/.blender/bpydata/config Done
Deleting directory ~/.blender/bpydata Done
Deleting directory ~/.blender Done
Main.CheckProgram.109: #45: File or directory does not exist
1: Main.Main.70
Modules.Get.123: Module is corrupted: Blender
mundus: Fatal IO error: client killed

Now the application won't start up at all - I get:

Main.CheckProgram.109: #42: System error #14: Bad address
1: Main.CheckProgram.109
2: Main.Main.39
mundus: Fatal IO error: client killed

I had to re-install and remove the .mundus folder to get the application to start.

[sebikul (sebikul)]

I can't reproduce the crash, nor the module corruption. Does it still happen if you try to clean blender again?

[Mark Bennison (mark-bennison)]

Well, I don't have blender installed now, so I can't reproduce it! In the interest of seeing whether or not this is a genuine bug, I will re-install and try to clean after removing it again. More later...

[Mark Bennison (mark-bennison)]

OK so I re-installed blender, did a couple of things so that I had a .blender folder. Uninstalled it and attempted a clean. Worked OK. No errors.

My only thought is that I have had blender installed since Ubuntu 9.04 and the various distro updates since then (and blender updates too) caused some confusion. After previously cleaning it then I have done a 'clean' install and all works.

I'd mark this bug as nor reproducible or closed, but I don't have that option!

Thanks!

[sebikul (sebikul)]

Done. Thanks for the interest!