Troubleshooting
- Web Browser report
- Microsoft Defender SmartScreen report
- Antivirus report
- Verify the setup.exe file is safe
- Install on Mac OS X
Download, Install problem
Web Browser report
Microsoft edgeMay report something like
Make sure you trust HomeBank-x.y.z-setup.exe before...
- click on ... (more action)
- select 'Keep' menu entry
- unfold 'Show more'
- click on 'Keep anyway'
The installer file HomeBank-x.y.z-setup.exe is sometimes reported as malicious.
Read also: Verify the setup.exe file is safe
Microsoft Defender SmartScreen report
You may encounter a popup that say:
starting. Running this app might put your PC at risk.
More info
- click on 'More info' link
- click on [Run anyway] button
More information about Microsoft Defender SmartScreen
Antivirus report
To create the installer setup, HomeBank uses Inno Setup and as some known viruses coders uses the same tool to create their setup, some anti-virus detection consider any setup where they find Inno setup signature as a potential virus as well, this stupid, but this is how it works, and why it fails. So this is usual that some antivirus report a virus or malware, this is especially the case for Avast, AVG and few other that report a virus for the setup file at every release...
This is of course probably a false positive, those anti-virus seems to use a perfectible detection, and honestly you should avoid pay for such poor software if you do.
At least, please report false positive, maybe... they will fix something somehow.
Read also: Verify the setup.exe file is safe
Verify the setup.exe file is safe
A) Check the SHA256
- launch a command window
certutil -hashfile HomeBank-x.y.z-setup.exe SHA256
- launch a powershell
Get-FileHash HomeBank-x.y.z-setup.exe
B) Check for virus or malware
- online reliable suggestion is virustotal
- or f-secure.
C) Report false positive
If you own an antivirus, most of the time you can submit a false positive report to the editor, just google for page with webform or email where to report.
AVG report form
Avast report form
D) Contact me
If someone is to find a true positive result, then he can contact me
Install on Mac OS X
First, this is a third party port, so if you encounter problems installing HomeBank, in despite of the instructions below that were provided by a mac user, please try to get some help on macports, or brew or on a mac dedicated forum.
Using Homebrew package
using command in terminal
- proceed homebrew package manager:
$ruby -e "$(curl -fsSL https://raw.github.com/mxcl/homebrew/go)" - proceed Homebank:
$brew install homebank
Using MacPort (on Mac OSX 10.6 (Snow Leopard)
- Check X11 is installed, if not, you have to use your Mac OS X Installation DVD to install it
- Install MacPort from install page
- Start a Terminal
- Type: sudo port install homebank
If it gives you error "install-sh: Permission denied", report to ticket 24431 - Start Applications/Utilities/X11
- Type: homebank
When icons are missing (e.g. at the toolbar), do 3 more steps
- Exit the HomeBank application
- At Termnial, type: sudo port install hicolor-icon-theme
- At X11, type: homebank
Windows: Report or complete a bug with gdb.exe
Preparation
- download the zip of latest gdb
- download the zip file of HB with debug symbol, available in /public folder, usually named for example HomeBank-5.6-debug.zip
- uncompress the 2 zips into C:\Program Files (x86)\HomeBank (with admin rights)
- launch a cmd.exe from the location (replace C:\Program Files (x86)\HomeBank by cmd and press ENTER)
- or launch a cmd.exe and change the folder to C:\Program Files (x86)\HomeBank
The debug session
A) Automated session
- type:
HomeBank_debug.bat
- on prompt (of gdb), type:
run, then ENTER
- reproduce the step into HomeBank until it crash
- HomeBank will freeze, don't close it
- go back to the cmd console, you should have focus
- type:
bt, then ENTER
- this will log the debug log and hopefully the crash location/dll area
- copy all this into the clipboard
- paste this to a new text file with notepad or similar
- add this text file as an attachment into your bug report
B) For manual session (without the .bat file)
- type
set PYTHONHOME=.
(required for latest gdb.exe > 8) - type
gdb.exe --data-directory=./share/gdb HomeBank_debug.exe
- then follow steps above starting at 2.
GNU/Linux: Report or complete a bug with gdb.exe
Instruction below is for debian derivative distribution, adapt the install part if you derive from Arch or others
- install gdb with:
sudo apt get install gdb
- open a terminal
- type:
gdb homebank
- on prompt (of gdb), type:
run, then ENTER
- reproduce the step into HomeBank until it crash
- HomeBank will freeze, don't close it
- go back to the cmd console, you should have focus
- type:
bt, then ENTER
- this will log the debug log and hopefully the crash location/dll area
- copy all this into the clipboard
- paste this to a new text file with notepad or similar
- add this text file as an attachment into your bug report
Compile from source (GNU/Linux)
Get source from launchpad
Please visit LaunchPad help page related to this.
Compiling for GNU/Linux distribution
The compiling instruction will differ depending on the distribution you uses.
Requisites
- gcc
- automake tools
- libgtk3.0 development files
- libofx
- libofx development files
- libsoup
- libsoup development files
- intltool (if you have problems with .po file compilation)
Debian/Ubuntu distribution
Here are the instructions for compiling on debian/ubuntu:
- open a terminal
- type:
sudo apt-get install build-essential libgtk-3-dev libofx7 libofx-dev libsoup2.4 libsoup2.4-dev intltool
- uncompress the archive file:
tar -zxpf homebank-x.x.tar.gz
- move to HomeBank folder:
cd homebank-x.x
- type:
./configure --prefix=/usr
- type:
make
- type:
sudo make install