I'm running Inkscape on a Lenovo Yoga 530 touchscreen. Inkscape shuts down after monitor going into sleep mode and all unsaved work is lost. Anybody else who have my problem and is there a solution for if other than turning of energy savings mode?
This sounds like something that should be reported. What version of Inkscape are you using? Also please tell us which operating system? Have you seen this happen repeatedly? Or did it only happen once?
Yeah, I have my monitor set to switch to a screensaver, if I go away for more than 20 minutes. But I have not seen Inkscape shut down. However, I'm not sure if that's the same thing as sleep mode.
Would you also please tell us whether the computer itself is going into sleep mode? Or is it just the monitor and just the screensaver coming on? (I don't think Inkscape should shut down either way, but details are important if we need to make a report.)
Could you clarify what "monitor going into sleep mode" means? Is it really only the display being switched off (i.e. computer is still running normally)? Or is your computer going into standby or hybernation mode?
Also we need to understand what "Inkscape shuts down" means. Does it crash or does it quit normally (as it would when you close it yourself)? You could figure that out by checking if preferences are lost (Inkscape won't be able to save any changed preferences when crashing). If it looses you work, that suggests a crash, though, in which case it would help if you start "inkscape.com" from a command prompt and check if any errors are printed to the console during the process.
To Patrick. As wrote earlier, it happens when laptop enters energy savings mode (stand by), not when monitor shuts itself down. That's the weird part usually when something like this happens, a dialog box from windows appears with a message that a program has crashed. But that was in the good ol days of win 95 98 ME ;)
I can certanly do that. Will report on any discoveries.
To bynn. I'll do that after I've done a command line start as Patrick suggested.
Thanks for taking the time trying to solve this mystery
When I run the inkscape.com file everything is fine. The .exe file shuts down and the command promt is just like normal, no error messages and changes in preferences is not saved.
Hm, so a crash seems likely. At least with standby I can not trigger the issue on my end.
In the beta version, can you run "gdb_create_backtrace.bat"? It will open Inkscape for you while running it through a debugger. You can then repeat the cycle (i.e. go into standby once) and if it crashes it might give us some additional pointers (just follow the steps explained in the command prompt in order to provide us with the necessary data)
Sorry for the delay. Two feverish children who needed my attention, baked 8 pizzas and 2 breads.
Here comes the info gathered.
--- BACKTRACE --- [New Thread 9052.0x2838] [New Thread 9052.0xd08] [New Thread 9052.0x334c] [New Thread 9052.0x45d8] [New Thread 9052.0x247c] [New Thread 9052.0x39ec] [New Thread 9052.0x3d88] [New Thread 9052.0x3b08] [New Thread 9052.0x31d4] [New Thread 9052.0x3fd8] [New Thread 9052.0x37c4] [New Thread 9052.0x211c] [New Thread 9052.0x2474] [New Thread 9052.0x4e14] [New Thread 9052.0x3ba0] [New Thread 9052.0x1598] [New Thread 9052.0x12a8] [New Thread 9052.0x1090] Warning: limit of 200 snap sources reached, some will be ignored [Thread 9052.0x1090 exited with code 0] [Thread 9052.0x334c exited with code 0] [Thread 9052.0xd08 exited with code 0] [Thread 9052.0x2838 exited with code 0] [Thread 9052.0x45d8 exited with code 0] [Thread 9052.0x247c exited with code 0] [Thread 9052.0x12a8 exited with code 0] [Thread 9052.0x1598 exited with code 0] [New Thread 9052.0x284c] [Thread 9052.0x284c exited with code 0] [New Thread 9052.0x3cdc] [Thread 9052.0x3cdc exited with code 0]
Thread 8 received signal SIGSEGV, Segmentation fault. [Switching to Thread 9052.0x3d88] 0x00007ffe1071ce29 in WacomExtHook () from C:\Windows\SYSTEM32\ISD_Tablet.dll #0 0x00007ffe1071ce29 in WacomExtHook () from C:\Windows\SYSTEM32\ISD_Tablet.dll #1 0x00007ffe1071f8f7 in WacomExtHook () from C:\Windows\SYSTEM32\ISD_Tablet.dll #2 0x00007ffe1071bfb8 in WacomExtHook () from C:\Windows\SYSTEM32\ISD_Tablet.dll #3 0x00007ffe1071c878 in WacomExtHook () from C:\Windows\SYSTEM32\ISD_Tablet.dll #4 0x00007ffe1071edbf in WacomExtHook () from C:\Windows\SYSTEM32\ISD_Tablet.dll #5 0x00007ffe107571d9 in WacomExtHook () from C:\Windows\SYSTEM32\ISD_Tablet.dll #6 0x00007ffe44347974 in KERNEL32!BaseThreadInitThunk () from C:\Windows\System32\kernel32.dll #7 0x00007ffe44d9a271 in ntdll!RtlUserThreadStart () from C:\Windows\SYSTEM32\ntdll.dll #8 0x0000000000000000 in ?? () Backtrace stopped: previous frame inner to this frame (corrupt stack?)
This problem persists. I simply closed my laptop, putting it in sleep mode, and while my code in VS Code was fine, my PG Admin in Chrome maintained, but Inkscape closed and I lost 4 hours of diagraming a deployment pipeline and wow. That hurts bad. It was looking so good too. I guess it is my fault as I never saved, but I assumed a ~temp file was created at the least. I'm finding that to be sadly untrue.
Hi!
I'm running Inkscape on a Lenovo Yoga 530 touchscreen.
Inkscape shuts down after monitor going into sleep mode and all unsaved work is lost.
Anybody else who have my problem and is there a solution for if other than turning of energy savings mode?
Welcome to the forum!
This sounds like something that should be reported. What version of Inkscape are you using? Also please tell us which operating system? Have you seen this happen repeatedly? Or did it only happen once?
If not already using, would you be willing to try installing 1.0beta2, to test if the problem is happening there? https://inkscape.org/release/inkscape-1.0/?latest=1
Yeah, I have my monitor set to switch to a screensaver, if I go away for more than 20 minutes. But I have not seen Inkscape shut down. However, I'm not sure if that's the same thing as sleep mode.
Would you also please tell us whether the computer itself is going into sleep mode? Or is it just the monitor and just the screensaver coming on? (I don't think Inkscape should shut down either way, but details are important if we need to make a report.)
Thank you!
Should first mention that I really like this program. Not that difficult to understand. Think it's better than Illustrator in many ways.
I'm using Inkscape 0.92.4 on Windows 10 home1809.
I'ts reccurring, sadly, but now I know that I must save my work before leaving the laptop alone for a while.
It happens when laptop enters energy savings mode, not monitor sleep and it only effects Inkscape.
I will try Beta version and se if that fixes the issue.
I'll report back in a while.
The same happens in Beta version aswell.
Well that's a bummer.
Do you feel comfortable to make a bug report? Info: https://inkscape.org/forums/beyond/how-to-report-bugs-or-request-new-features/
I can do it if you don't want to. But it's better if you do it, in case developers have further questions. I might not be able to answer them.
Could you clarify what "monitor going into sleep mode" means?
Is it really only the display being switched off (i.e. computer is still running normally)?
Or is your computer going into standby or hybernation mode?
Also we need to understand what "Inkscape shuts down" means.
Does it crash or does it quit normally (as it would when you close it yourself)? You could figure that out by checking if preferences are lost (Inkscape won't be able to save any changed preferences when crashing).
If it looses you work, that suggests a crash, though, in which case it would help if you start "inkscape.com" from a command prompt and check if any errors are printed to the console during the process.
To Patrick. As wrote earlier, it happens when laptop enters energy savings mode (stand by), not when monitor shuts itself down.
That's the weird part usually when something like this happens, a dialog box from windows appears with a message that a program has crashed. But that was in the good ol days of win 95 98 ME ;)
I can certanly do that. Will report on any discoveries.
To bynn. I'll do that after I've done a command line start as Patrick suggested.
Thanks for taking the time trying to solve this mystery
When I run the inkscape.com file everything is fine.
The .exe file shuts down and the command promt is just like normal, no error messages and changes in preferences is not saved.
Hm, so a crash seems likely. At least with standby I can not trigger the issue on my end.
In the beta version, can you run "gdb_create_backtrace.bat"?
It will open Inkscape for you while running it through a debugger. You can then repeat the cycle (i.e. go into standby once) and if it crashes it might give us some additional pointers (just follow the steps explained in the command prompt in order to provide us with the necessary data)
Sorry for the delay. Two feverish children who needed my attention, baked 8 pizzas and 2 breads.
Here comes the info gathered.
--- BACKTRACE ---
[New Thread 9052.0x2838]
[New Thread 9052.0xd08]
[New Thread 9052.0x334c]
[New Thread 9052.0x45d8]
[New Thread 9052.0x247c]
[New Thread 9052.0x39ec]
[New Thread 9052.0x3d88]
[New Thread 9052.0x3b08]
[New Thread 9052.0x31d4]
[New Thread 9052.0x3fd8]
[New Thread 9052.0x37c4]
[New Thread 9052.0x211c]
[New Thread 9052.0x2474]
[New Thread 9052.0x4e14]
[New Thread 9052.0x3ba0]
[New Thread 9052.0x1598]
[New Thread 9052.0x12a8]
[New Thread 9052.0x1090]
Warning: limit of 200 snap sources reached, some will be ignored
[Thread 9052.0x1090 exited with code 0]
[Thread 9052.0x334c exited with code 0]
[Thread 9052.0xd08 exited with code 0]
[Thread 9052.0x2838 exited with code 0]
[Thread 9052.0x45d8 exited with code 0]
[Thread 9052.0x247c exited with code 0]
[Thread 9052.0x12a8 exited with code 0]
[Thread 9052.0x1598 exited with code 0]
[New Thread 9052.0x284c]
[Thread 9052.0x284c exited with code 0]
[New Thread 9052.0x3cdc]
[Thread 9052.0x3cdc exited with code 0]
Thread 8 received signal SIGSEGV, Segmentation fault.
[Switching to Thread 9052.0x3d88]
0x00007ffe1071ce29 in WacomExtHook () from C:\Windows\SYSTEM32\ISD_Tablet.dll
#0 0x00007ffe1071ce29 in WacomExtHook () from C:\Windows\SYSTEM32\ISD_Tablet.dll
#1 0x00007ffe1071f8f7 in WacomExtHook () from C:\Windows\SYSTEM32\ISD_Tablet.dll
#2 0x00007ffe1071bfb8 in WacomExtHook () from C:\Windows\SYSTEM32\ISD_Tablet.dll
#3 0x00007ffe1071c878 in WacomExtHook () from C:\Windows\SYSTEM32\ISD_Tablet.dll
#4 0x00007ffe1071edbf in WacomExtHook () from C:\Windows\SYSTEM32\ISD_Tablet.dll
#5 0x00007ffe107571d9 in WacomExtHook () from C:\Windows\SYSTEM32\ISD_Tablet.dll
#6 0x00007ffe44347974 in KERNEL32!BaseThreadInitThunk () from C:\Windows\System32\kernel32.dll
#7 0x00007ffe44d9a271 in ntdll!RtlUserThreadStart () from C:\Windows\SYSTEM32\ntdll.dll
#8 0x0000000000000000 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
Hmm, this shows that the crash is inside the driver (ISD_Tablet.dll) for a Wacom tablet, possibly your notebook's touchscreen.
I'm not sure there's much we *can* do, as this will be almost impossible to reproduce on a developer's machine.
I'm not sure what to suggest here - disabling the Wacom tablet could possibly avoid the crash, but I assume you want to use it with Inkscape...
Must be the touchscreen then.
Just have to live with it then.
Thanks for the help understanding the problem.
This problem persists. I simply closed my laptop, putting it in sleep mode, and while my code in VS Code was fine, my PG Admin in Chrome maintained, but Inkscape closed and I lost 4 hours of diagraming a deployment pipeline and wow. That hurts bad. It was looking so good too. I guess it is my fault as I never saved, but I assumed a ~temp file was created at the least. I'm finding that to be sadly untrue.
Windows 10
Inkscape 0.92.4
I’m sad to hear that you lost all your work.
lt must be a compatibility problem between the program and the driver. VLC shuts down in the same way. So far, just these two apps who shuts down.