SIGSEGV with corrupt history file
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Midori Web Browser |
Fix Released
|
High
|
Unassigned |
Bug Description
Package: midori
(Debian) Version: 0.4.3-1
Severity: normal
Dear Midori folks,
after a system crash my history files was corrupt and Midori recovering from the force closed(?) session warned me about it and I chose »Ignore« and in the next dialog to open and reload the opened tabs from the last session.
Then opening a new window and entering a character in the URL field Midori crashed reliably probably because of the corrupt history file. Moving the file `~/.config/
Please find the backtrace captured with GDB attached.
While I deliberatly chose to ignore the corrupt history file, Midori should still not crash when accessing it and maybe should not access it at all or ignore errors from SQLite(?).
Thanks,
Paul
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (x86_64)
Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=
Shell: /bin/sh linked to /bin/bash
Versions of packages midori depends on:
ii dbus-x11 1.4.16-1
ii libc6 2.13-24
ii libcairo2 1.10.2-6.2
ii libgdk-pixbuf2.0-0 2.24.0-2
ii libglib2.0-0 2.30.2-4
ii libgtk2.0-0 2.24.8-2
ii libjavascriptco
ii libnotify4 0.7.4-1
ii libpango1.0-0 1.29.4-2
ii libsoup2.4-1 2.36.1-1
ii libsqlite3-0 3.7.9-2
ii libunique-1.0-0 1.1.6-4
ii libwebkitgtk-1.0-0 1.6.1-5+b1
ii libx11-6 2:1.4.4-4
ii libxml2 2.7.8.dfsg-5
ii libxss1 1:1.2.1-2
Versions of packages midori recommends:
ii gnome-icon-theme 3.2.1.2-1
midori suggests no packages.
-- no debconf information
Changed in midori: | |
status: | Fix Committed → Fix Released |
I think this should be the same backtrace from a session started after the crash to reproduce the issue.