Screenshots returned to provoce some troubles
See original GitHub issueBy sometime, screenshots function returned to things. Very often, it refuse to convert the image and stop working. In the log, there’s always something like this:
[2017-08-11 20:40:35Z] Unable to open screenshot 'd:\Users\Andrea\Pictures\Frontier Developments\Elite Dangerous\Screenshot_0000.bmp': Could not find file 'd:\Users\Andrea\Pictures\Frontier Developments\Elite Dangerous\Screenshot_0000.bmp'.
[2017-08-11 20:40:35Z] Exception watcher: Could not find file 'd:\Users\Andrea\Pictures\Frontier Developments\Elite Dangerous\Screenshot_0000.bmp'.
[2017-08-11 20:40:35Z] Trace: at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
[2017-08-11 20:40:35Z] at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
[2017-08-11 20:40:35Z] at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
[2017-08-11 20:40:35Z] at EDDiscovery.ImageHandler.ImageConverter.GetScreenshot(String inputfile, String cur_sysname, Int32 cmdrid, JournalScreenshot& ss, String& store_name, Point& finalsize, FileInfo& fi) in C:\projects\eddiscovery\EDDiscovery\ImageHandler.cs:line 772
[2017-08-11 20:40:35Z] at EDDiscovery.ImageHandler.ImageConverter.Convert() in C:\projects\eddiscovery\EDDiscovery\ImageHandler.cs:line 674
[2017-08-11 20:40:35Z] at EDDiscovery.ImageHandler.ScreenshotDirectoryWatcher.ProcessScreenshot(String filename, String sysname, JournalScreenshot ss, Int32 cmdrid, ImageConverter cp) in C:\projects\eddiscovery\EDDiscovery\ImageHandler.cs:line 608
[2017-08-11 20:40:35Z] Error in executing image conversion, try another screenshot, check output path settings. (Exception Could not find file 'd:\Users\Andrea\Pictures\Frontier Developments\Elite Dangerous\Screenshot_0000.bmp'.
Curiously, the image is where it is supposed to be, and the folders are perfectly in place…
I have to close and restart EDDiscovery to have it working by a while, before the problem reappear.
Issue Analytics
- State:
- Created 6 years ago
- Comments:16 (16 by maintainers)
Top Results From Across the Web
Is it illegal to post screenshots of a private conversation ...
Whether or not you post the image is immaterial; it is not unlawful in the United States to take a screenshot of a...
Read more >Android Screenshot Not Working? Try These Fixes
If trying to take an Android screenshot is not working, nothing may happen or you may get an error message. Use these tips...
Read more >Troubleshoot an unreachable instance - AWS Documentation
You can use the following information to help you troubleshoot an unreachable instance based on screenshots returned by the service. Log on screen...
Read more >Fixed: Print Screen Not Working on Windows 10
How to Fix the Print Screen Not Working on Windows 10. Here are 6 solutions to fix the print screen not working in...
Read more >Worries Grow That TikTok Is New Home for Manipulated ...
Misleading edits, fake news stories and deepfake images of politicians are starting to warp reality on the popular video platform.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Re-uploading Log.zip with the EGO API key masqueraded.
I’m looking around for what might be the issue behind this, and am having troubles. Are you running Elite: Discovery as an administrator, or have any fancy NTFS permissions set for that folder? I’m assuming that you can actually browse and create files there; is that correct?
The release of 8.2.3 should see this resolved. Please re-open if issues occur again.