We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
According to the backtrace it seems to be a flash issue.
Can you give the result of the following commands:
apt-cache policy mozilla-plugin-gnash
and
apt-cache policy libflash-mozplugin
--
midori crashed with SIGSEGV in Private_SetWindow()
https://bugs.launchpad.net/bugs/281409
You received this
Thanks for the advice.
I followed the instructions. This time, midori did not close unexpectedly but
instead freezed. I don't know if it is the same fault. Anyway I found
"segmentation fault" in the text file.
Without being involved in midori's code base, this could very well be
not midoris faul
Please, try to obtain a backtrace:
sudo install midori-dbg gdb
and see here for backtrace https://wiki.ubuntu.com/Backtrace
Set to incomplete until we have a backtrace.
** Changed in: midori (Ubuntu)
Status: New => Incomplete
--
midori crashed with SIGSEGV in Private_SetWindow()
https:/
StacktraceTop:?? ()
?? ()
?? ()
?? () from /usr/lib/libwebkit-1.0.so.1
?? () from /usr/lib/libwebkit-1.0.so.1
** Tags removed: need-i386-retrace
** Tags added: apport-failed-retrace
** Attachment added: "Stacktrace.txt (retraced)"
http://launchpadlibrarian.net/18415127/Stacktrace.txt
--
mi
** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/18414850/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/18414857/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://launchpadlibrarian.net/18414858/Disassembly.txt
** Attachm
