View Issue Details

IDProjectCategoryView StatusLast Update
0004020FreeCADBugpublic2019-06-14 17:16
ReporterfremanAssigned To 
PrioritynormalSeverityminorReproducibilityalways
Status newResolutionopen 
Product Version0.19 
Target VersionFixed in Version 
Summary0004020: untrapped file error on start up.
DescriptionDue to manual changes to file ownerships, some file has become a problem when starting FreeCAD. However, the error does not seem to be trapped at the point where the file is accessed and just bubbles up to be caught as an untrapped error which is so general as to not be any help in identifying and resolving the problem

https://forum.freecadweb.org/viewtopic.php?f=3&t=37021&p=314367#p314367

freeCAD wrote

connect failed: No such file or directory
Unhandled std::exception caught in GUIApplication::notify.
The error message is: Permission denied


An error report which stated the full file path and name would allow this to be fixed immediately.

It seems that whatever function is attempting this file access is not trapping any file access errors and assumes it always works.


While the cause in this case is outside FreeCAD, it seems it should trap any errors in file access.
TagsNo tags attached.

Activities

freman

2019-06-14 07:26

reporter   ~0013211

OS: Linux
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.18.15303 (Git)
Build type: Release
Branch: master
Hash: 6199c95fd71eacb9cc168426e55254aa79a42034
Python version: 2.7.15
Qt version: 4.8.7
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: English/UnitedKingdom (en_GB)

openBrain

2019-06-14 16:03

developer   ~0013212

@freman as required in the bug submission guidelines, could you please confirm bug is still present in the latest release version (yours is outdated) ?
If possible, could also provide a way to reproduce the issue ?

freman

2019-06-14 17:16

reporter   ~0013214

yes, still present on new build of 0.19 master today.

However, as discussed in thread, there are two things happening here. The file permissions problem disappeared after a reboot, so the cause will be undetermined unless it happens again.

the other connection message seems to be be LVM related coming from Qt. It is probably banal.

This still reflects the need for better error trapping at a lower level, though it will not be possible to work out exactly where in this case until and unless it reoccurs. It seems some file access was being attempted without the success being tested. Knowing what file it was would have enabled it being resolved in minutes instead of not detected properly after hours.

If I see it again , I will report back.

Issue History

Date Modified Username Field Change
2019-06-14 07:23 freman New Issue
2019-06-14 07:26 freman Note Added: 0013211
2019-06-14 16:03 openBrain Note Added: 0013212
2019-06-14 17:16 freman Note Added: 0013214