Jump to content
Ultimaker Community of 3D Printing Experts
Sign in to follow this  
viralata

Bug (?) with cura 13.06.5 on linux

Recommended Posts

Hello all,

Coming back from hollidays, I wanted to see if I have better luck with the new version of Cura.

I found somewher this trick to make ite slice:

in a terminal, first type:

export LC_TIME=en_US.utf8

then type

cura

to launch it.

Now it slices, it is very fast indeed, but on my laptop it's not instant, and I like complex geometry... so I would definitely prefer a Slice button :-)

But then, it's the second time that the printer stop after several hours, thing that never happend with 13.04. I got this message:

 

Traceback (most recent call last):

File "/usr/share/cura/Cura/gui/mainWindow.py", line 62, in <lambda>

self.Bind(wx.EVT_MENU, lambda e: self.scene.showPrintWindow(), i)

File "/usr/share/cura/Cura/gui/sceneView.py", line 200, in showPrintWindow

self._slicer.submitSliceInfoOnline()

File "/usr/share/cura/Cura/util/sliceEngine.py", line 317, in submitSliceInfoOnline

'profile': profile.getGlobalProfileString(),

AttributeError: 'module' object has no attribute 'getGlobalProfileString'

>>The program 'python' received an X Window System error.

>>This probably reflects a bug in the program.

>>The error was 'BadAlloc (insufficient resources for operation)'.

>> (Details: serial 14155592 error_code 11 request_code 53 minor_code 0)

>> (Note to programmers: normally, X errors are reported asynchronously;

>> that is, you will receive the error a while after causing it.

>> To debug your program, run it with the --sync command line

>> option to change this behavior. You can then get a meaningful

>> backtrace from your debugger if you break on the gdk_x_error() function.)

 

I used to trust very much Cura and leave it to print for nights with no fear. Should I go back to 13.04, or anybody understands this error an can tell me what I should do.

 

Share this post


Link to post
Share on other sites

There are 2 errors there. The first bit can safely be ignored (it's an exception by a bug by me. But it only means that the "upload use stats" does not work)

The part with ">>" is some other bug, not sure what, as it comes from the X window system. So could be a bug in your wxPython version.

 

Share this post


Link to post
Share on other sites

Thanks for your quick answer. I tried a third time... let's see what happen.

Could not make my desktop fresh linuxmint15 install connect to the printer (added user to dialin, I don't remember if there is something else to do...) Please, please, why is it so annotying to make it work under linux ? I'm just so happy when it works that I'm affraid to update, as every time I have to find on the net new tricks to make it work.

Update: 3rd try and failure again...

Going back to cura 13.04 :-(

 

Share this post


Link to post
Share on other sites

I get a similar error after printing for an hour or so. Happened two times so far. Now I will try using pronterface.

 

>>The program 'python' received an X Window System error.

>>This probably reflects a bug in the program.

>>The error was 'BadAlloc (insufficient resources for operation)'.

>> (Details: serial 12339207 error_code 11 request_code 53 minor_code 0)

>> (Note to programmers: normally, X errors are reported asynchronously;

>> that is, you will receive the error a while after causing it.

>> To debug your program, run it with the --sync command line

>> option to change this behavior. You can then get a meaningful

>> backtrace from your debugger if you break on the gdk_x_error() function.)

 

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×

Important Information

Welcome to the Ultimaker Community of 3D printing experts. Visit the following links to read more about our Terms of Use or our Privacy Policy. Thank you!