I just don't understand. Why are dev versions available when they crash immediately? They crash - please fix those crashes, then release. I mean, something drastic has happened between 11-22 and 12-03 and has remained. I started 1.3 2022-12-03 or 2022-12-12, immediately go to About - CRASH - no message other than an error was encountered. This is a complete waste of guinea pig time and effort.
1.2.2 (the initial release) suffered the same issue. It seems to have been fixed in 2022-12-09.
So, why bother releasing dev versions if they crash immediately?
That will be your experience. In my case, I use 1.3 a lot and it works very well, although of course it sometimes crashes. It has many new features that are being tested and that is precisely the point, to test the new and help to correct bugs.
Tyler - what an arrogant answer. I am trying to use dev version, have done for several years, the developers put it out there to test, but before any real interaction happens, it crashes consistently, virtually instantaneously.
I use Win 10, not 11. Perhaps that's a clue?
So, Tyler, my question still stands....why bother releasing dev versions if they crash immediately? NOT a rhetorical question!
Thanks Marcos. These rashes are on separate machines, both Win 10. I'd like to check out then new features, but it ain't can't happening here. They (the Gods of Inkscape) figured the issue with the first release of 1.2.2, perhaps it's not part of the 1.3 agenda? Maybe it is a Win 10 issue?
Yet another arrogant answer Tyler... or is it tyler?
Of course I am AWARE of these conditions - but can't even get the application to fire up without crashing. That, in itself should be a flag. Hopefully you are in the back room in your job - you'd make a sensational front-office sales person. Have the day you deserve.
Beyond the Basics Why bother making dev versions available???
Inkscape.org
I just don't understand. Why are dev versions available when they crash immediately? They crash - please fix those crashes, then release. I mean, something drastic has happened between 11-22 and 12-03 and has remained. I started 1.3 2022-12-03 or 2022-12-12, immediately go to About - CRASH - no message other than an error was encountered. This is a complete waste of guinea pig time and effort.
1.2.2 (the initial release) suffered the same issue. It seems to have been fixed in 2022-12-09.
So, why bother releasing dev versions if they crash immediately?
Dev versions are for community testing. Don't use them if you are not willing to experience instabilities.
That will be your experience. In my case, I use 1.3 a lot and it works very well, although of course it sometimes crashes. It has many new features that are being tested and that is precisely the point, to test the new and help to correct bugs.
Tyler - what an arrogant answer. I am trying to use dev version, have done for several years, the developers put it out there to test, but before any real interaction happens, it crashes consistently, virtually instantaneously.
I use Win 10, not 11. Perhaps that's a clue?
So, Tyler, my question still stands....why bother releasing dev versions if they crash immediately? NOT a rhetorical question!
Thanks Marcos. These rashes are on separate machines, both Win 10. I'd like to check out then new features, but it
ain'tcan't happeninghere. They (the Gods of Inkscape) figured the issue with the first release of 1.2.2, perhaps it's not part of the 1.3 agenda? Maybe it is a Win 10 issue?I can state with confidence that the developers test prior to release and would not release if the version crashed on their test machines.
Yet another arrogant answer Tyler... or is it tyler?
Of course I am AWARE of these conditions - but can't even get the application to fire up without crashing. That, in itself should be a flag. Hopefully you are in the back room in your job - you'd make a sensational front-office sales person. Have the day you deserve.
As pointed out in the initial post, the issue seems to have been resolved and a hotfix released.
This would not be the case, were it not for community testing and reporting on the bug-tracker, without histrionics or ad hominem attacks.
I believe the question has been answered, so I will close this topic.