A fancy error on startup

Bug #1397510 reported by Oleg Dozorov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Midori Web Browser
Fix Released
High
Unassigned

Bug Description

I can not explain enough clearly after what of my actions exactly this happened, but at present my Windows Midori 0.5.9 exe refuses to start :(.. It only displays an error message "failed to attach database" \a screen of that window is attached\. When I click "Ignore", Midori starts and immediately crashes. and when I click "Cancel", it does not run al all.
My system is genuine Windows 7 RU x64, with 4 gigabytes of RAM and Intel processor, Midori is downloaded and installed in a quite usual way. The computer was built approximately in 2009. Of coarse, I have fresh Flash and Java versions installed, there are also a bunch of Microsoft redistributables and frameworks. I am using free MSE antivirus, µTorrent and Miranda are always running.

UPD.: after some discussion with Tuxator on this issue I have managed to make a manual temporary solution for this: now I start Midori 0.5.9 with a "--config=F:\mcfg" parameter written in the shortcut on my win7 desktop. But this does NOT refer to a normal "easy" case when such parameter is not written in the shortcut.

Tags: crash error win32

Related branches

Revision history for this message
Oleg Dozorov (fernitoid) wrote :
Revision history for this message
Paweł Forysiuk (tuxator) wrote :

Looks like your bookmark file got corrupted. This should not happen by just using midori. I could happen if you are very unfortunate and forcibly quit the process when it was in the middle of db operations (really should not happen during normal use).

You may want to rename/move your bookmarks.db (and maybe history.db) from your config directory
Example: C:\Users\MyLogin\AppData\Local\midori on win8. If you can run midori from command line
you can run midori -p and then go to about:paths to find out the config dir. Alternatively on windows
there is --portable switch that uses "portable" folder to store midori files instead of system folders.

Revision history for this message
Oleg Dozorov (fernitoid) wrote :

It would be nice if I could solve that by just deleting bookmarks.db from appdata\local :D.. I had already tried such an obvious tricks before posting this bug.
That gains nothing. And portably running midori -p starts ok (it shows empty about:private page then), but immediately hangs up when I try to goto any web address of open the preferences window :(((...
BTW, a 7zipped Midori version crashes the same way as an installed one crashes.

Revision history for this message
Paweł Forysiuk (tuxator) wrote :

Well on the first run (and others if you foribly stop it) webkit (more like fontconfig) makes fonts cache on the first run (or when fonts folder change as well) because that is how the current webkit code is (ideally it should just use native win api). If you dont let it make the cache (could take _a couple of minutes_ sometimes ;/) it will try again. Once cache is done midori should start quickly then. As for the crash i dont know what would that be. Maybe you can run midori under gdb.exe? Or tell exactly what you do to make it crash if this happens every time. Here on win8 i dont see such crash.

Changed in midori:
status: New → Incomplete
importance: Undecided → High
Revision history for this message
Paweł Forysiuk (tuxator) wrote :

As for preferences file types for "open with" function are queried and it may appear that midori hung on some machines i guess. Please give us more info with that stuff in mind.

Revision history for this message
Oleg Dozorov (fernitoid) wrote :

Thank you a lot \once more :)\ for your understanding and kind support, Paweł!...
Pretty much things happened after I read your most recent advices, but I will first show some screen-shots from my desktop that I suppose to be most informative for you...

Revision history for this message
Paweł Forysiuk (tuxator) wrote :

can you show me the output of about:paths maybe? Does this happen every time you move config files aka clean first start? also running under gdb is mostly useful when something crasher, i cannot really tell what is happpening from the description. Maybe you can also go on #midori irc channel on freenode for more realtime feedback?

Revision history for this message
Oleg Dozorov (fernitoid) wrote :

I have just cleared the appdata config files, and the error remains even on clean start... But now Midori seems to work properly (except the error message on the start-up), and I can read about:paths, here is what it says:
{
config: C:\Users\Username\AppData\Local\midori
res: F:\Program Files 2 (x86)\Midori\share\midori\res\about.css
data: C:\Users\Username\AppData\Local/midori
lib: F:\Program Files 2 (x86)\Midori\lib\midori
cache: C:\Users\Username\AppData\Local\Microsoft\Windows\Temporary Internet Files\midori
tmp: C:\Users\Username\AppData\Local\midori
}
Well, IRC.. I have never used it before, but I can try to connect via Miranda - I would make an IRC account in my client program. Maybe then I will be able to communicate in realtime :)

Revision history for this message
Oleg Dozorov (fernitoid) wrote :

Hello, I just want to thank mr. Forysiuk for his kind on-line assistance with solving this question.
As I understand, we know much more about this error now. But it is still appearing, and a solution for it is still required.

P. S.: I have noticed that someone has removed my old report about browsing backwards in tabs that were restored from the closed state. There was a question several weeks ago about this problem I have reported in that thread, which has now gone along with the whole report. I can say now that the problem with browsing in restored tabs is now solved, and the tabs restored after closing are completely browsable now. Thank you for keeping that my question in mind for such a long time :)

Best regards,
Dozorov O.

Changed in midori:
status: Incomplete → Confirmed
milestone: none → 0.6.0
Changed in midori:
status: Confirmed → Fix Committed
Oleg Dozorov (fernitoid)
description: updated
Cris Dywan (kalikiana)
Changed in midori:
status: Fix Committed → Fix Released
Cris Dywan (kalikiana)
Changed in midori:
milestone: 0.6.0 → 0.5.10
Revision history for this message
Oleg Dozorov (fernitoid) wrote :

I have checked these days if Midori 0.5.10 runs ok on a genuine Win7x32 Starter RU. It runs ok :)
Other bugs reported by me are to be checked for consistence on next Midori. Of coarse, I can make it on 0.5.10, if somebody wish that.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.