Mon 11 Jul 2016 05:12:16 AM UTC, comment #11:
No response. Closing report.
|
Fri 01 Jul 2016 10:09:07 AM UTC, comment #10:
Is the issue present on 4.0.2?
|
Sun 09 Aug 2015 12:19:50 PM UTC, comment #9:
So it may be during the process of running octave from within the installer.
|
Sat 08 Aug 2015 04:28:01 PM UTC, comment #8:
When I renamed .config and ran the Octave GUI, it took me through a couple of introductory screens and started normally.
|
Sat 01 Aug 2015 09:09:33 PM UTC, comment #7:
Bug #40444 bears some relation to this bug
|
Sat 01 Aug 2015 02:52:08 PM UTC, comment #6:
WHat happens if you delete (or rename) the .config folder and run octave?
|
Mon 27 Jul 2015 08:59:06 PM UTC, comment #5:
Now you are leading me into "less certain" territory.
I think .config may have been there, but if it was, I am thinking it was probably empty. I am pretty sure there was no octave folder in there.
I have never really understood Windows file permissions, but I am thinking it may be possible to have the rights to create a folder, but then not have the rights to put anything in it. That's what I think was the case before I recursively added myself to the permission list of all of the folders, but I'm only, say, 80% sure.
I don't seem to have this problem with other usernames' \Documents and Settings\ folders on this machine, even as myself (with admin rights). If I did see the same issue (in terms of lacking permissions), I'd try to confirm this state of affairs.
Sorry to be a bit vague at this point...
|
Mon 27 Jul 2015 07:54:20 PM UTC, comment #4:
Had it created the .config folder and the octave/4.0.0 directory inside?
|
Mon 27 Jul 2015 07:29:09 PM UTC, comment #3:
I am virtually certain I did not uncheck anything in the install process and that therefore it tried to run the application the first time from the installer, and crashed. Every time I subsequently tried to run the GUI, the same sequence of one or two dialogs happened, followed by the crash.
When I went looking for qt-settings they weren't there. Perhaps an attempt to create default settings failed (silently?).
By the time I re-installed, I had fixed the permissions problem.
I suppose there may be two questions: 1. does absence or inaccessibility of qt-settings lead to a crash; and 2. does it silently fail to create qt-settings if it does not have permission?
Just my 2 cents...
|
Mon 27 Jul 2015 12:30:26 PM UTC, comment #2:
Did you run octave for the first time through the end of the installer, or did you uncheck the run octave option and then run it after closing the installer?
|
Mon 27 Jul 2015 05:17:38 AM UTC, comment #1:
Permissions problem with .config folder in Documents and Settings...
Gave myself permission, Uninstalled / reinstalled, and it starts OK.
I have gotten around this but the crash should be fixed.
|
Mon 27 Jul 2015 04:15:44 AM UTC, original submission:
Windows XP SP3 32 bit, Lenovo R60e.
After the "Welcome to Octave sequence" upon pressing Finish button, Octave crashes with access violation fault, PC=016504E1, EAX=0
Starting from commandline with --force-gui reproduces the bug exactly.
CLI runs OK.
Looking at bug #45459 I see the advice to delete qt-settings but none seem to be currently present.
|