Win: portable version not functionnal when path contain 'bin'
Bug #1741692 reported by
cybermcm
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| HomeBank |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
OS: Windows 10 (fully patched 2018-01-06)
Homebank: Portable installation: 5.1.6
Bug: Homebank isn't useable if portable version is placed in a subfolder of bin, e.g. C:\bin\Homebank.
It seems that Homebank isn't able to load the settings file if placed in such a folder. It seems a hardcoded bug because if the same installation is moved to a different folder it works.
See screenshot, program isn't useable. After clicking on a button program crashes.
Revision history for this message
| cybermcm (cybermcm) wrote | #1 |
Revision history for this message
| Maxime DOYEN (mdoyen) wrote | #2 |
| Changed in homebank: | |
| status: | New → In Progress |
| importance: | Undecided → Low |
| assignee: | nobody → Maxime Doyen (mdoyen) |
| summary: |
- Windows portable version not useable if placed in specific path + Win: portable version crash is in a path containing 'bin' |
| summary: |
- Win: portable version crash is in a path containing 'bin' + Win: portable version not fucntionnal is in a path containing 'bin' |
Revision history for this message
| Maxime DOYEN (mdoyen) wrote Re: Win: portable version not fucntionnal is in a path containing 'bin' | #3 |
| summary: |
- Win: portable version not fucntionnal is in a path containing 'bin' + Win: portable version not fucntionnal when path contain 'bin' |
| summary: |
- Win: portable version not fucntionnal when path contain 'bin' + Win: portable version not functionnal when path contain 'bin' |
| Changed in homebank: | |
| status: | In Progress → Confirmed |
Revision history for this message
| Maxime DOYEN (mdoyen) wrote | #4 |
| Changed in homebank: | |
| assignee: | Maxime Doyen (mdoyen) → nobody |
| importance: | Low → Undecided |
| status: | Confirmed → Invalid |
To post a comment you must log in.
this seems to be in the gtk/glib stack (or system)
as procmon shows that the current program path (for gtk/glib) in that case is c:\ and not c:\bin\homebank
if you just rename bin to mybin it works
this is weird and not related to homebank itself