@illuminarti: It doesn't matter whether Cura is running or is already stopped when the computer hybernates. I cannot rule out every possibility, but I'm quite confident it is caused by Cura.
@illuminarti: It doesn't matter whether Cura is running or is already stopped when the computer hybernates. I cannot rule out every possibility, but I'm quite confident it is caused by Cura.
but I'm quite confident it is caused by Cura.
If that would be the case I wouldn't be able to sit at my desk right now. Cura actually touches at little from the system as possible, as this makes it easier to go cross-platform.
I think it has something do with my macbook.
Maybe some strange hard to find hardware/software combo problem. The problem is that I am not able to reproduce the situation.
Here's an idea. Enable remote login (ssh) and when it happens again, log-in from another system via ssh and inspect the process list (ps -alx). If cura is running, try to kill it by hand and see if you can log-in. But I doubt that's the cause.
You could also take a look at the console app. It agregates all logs. Just search for the latest entries (before the shutdown).
I didn't have this problem with Cura, but it happened to me before. Even on a new retina mbp and with Mavericks :/
Thnx UM2, will try that.
Till now I experienced three situations:
- Sometimes the screen remains black, but the keyboard lighting is responsive.
- The login screen appears for a second and then dissapears.
- Thw login screen appears, but I cannot enter the password (no cursor)
Haha, I meant : thanx Nicolinux
Recommended Posts
illuminarti 18
That's weird, I haven't seen it in my system. Does it matter whether Cura is still running or not? Are you absolutely sure that it's dependent on Cura?
Link to post
Share on other sites