Known issues
Hugin 0.4.59 does not open on a profile that has been used for a while, and 0.4.60 repairs it. What to do, what not to do, and how to confirm the repair.
Hugin 0.4.59 does not open
If you are on 0.4.59 and Hugin does not open, this is a known bug in that version. It is fixed in 0.4.60.
The in-app updater cannot get you out of it, because the app never starts far enough to check for an update. Download 0.4.60 from hugin.nu/download yourself and install it over the copy you have.
Do not delete or move your existing profile or database. 0.4.60 repairs it the first time it starts, and your captured traffic is kept. Deleting the profile is the one action that turns a slow start into lost work.
The first start after the upgrade takes about a minute on a 10 GB profile. It is working, not hung, so let it finish.
What went wrong
The 0.4.59 upgrade rewrote the stored host names one row at a time. Every
rewritten row fired a full-text index trigger, and that trigger's delete arm
searched the whole index instead of the single entry it was removing, at about
59 ms per row across a store with a few hundred thousand rows. The rewrite
therefore never finished, and it held the database write lock for the whole
time. The window stayed blank, and anything else that opened the database,
including the MCP server, exited with database is locked. 0.4.60 does the same
rewrite in one pass with the triggers suspended, rebuilds both full-text
indexes once at the end, and drops the lock.
A profile that was already interrupted is not damaged. The rewrite is idempotent and runs to completion on the first start of 0.4.60.
Confirm the repair
- The app opens.
hugin --versionreports0.4.60. - The Sitemap shows one node per host. A host that used to
appear twice, as
www.example.comand aswww.example.com:443, appears once. A tunnel's port is the scheme's default, so it is no longer part of the host name; a real non-default port such ashpanel.hostinger.com:8080stays. - Your captured traffic is intact. History still lists the flows you had before the upgrade, and search finds them.
If the app still does not open after the manual install, the profile is at
~/.hugin/hugin.db. Move that file aside (do not delete it) and start Hugin
again to see whether the app itself is the problem, then report what happened at
hugin.nu/contact with the file kept for inspection.
Related
- Install Hugin — download and install paths.
- Configuration — where the profile and database live.