Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#21797 - [midori] memory segmentation fault
Attached to Project:
Arch Linux
Opened by Eivind (mokkurkalve) - Tuesday, 23 November 2010, 09:32 GMT
Last edited by Andreas Radke (AndyRTR) - Saturday, 12 February 2011, 23:30 GMT
Opened by Eivind (mokkurkalve) - Tuesday, 23 November 2010, 09:32 GMT
Last edited by Andreas Radke (AndyRTR) - Saturday, 12 February 2011, 23:30 GMT
|
DetailsDescription:
The several last versions of midori have very easily segfaulted. This last version segfaults immediately when trying to remove or input text in address bar. The console only reports "segfault" but I tried the DDD, data display debugger, a tool I'm not familiar with. Anyways it reports the following from te moment of segfault: Program received signal SIGSEGV, Segmentation fault. 0xb786d72e in g_markup_escape_text () from /usr/lib/libglib-2.0.so.0 (gdb) Additional info: * package version(s) 0.2.9-1 * config and/or log files etc. Steps to reproduce: Try to backspace over or input new url in address bar |
This task depends upon
Closed by Andreas Radke (AndyRTR)
Saturday, 12 February 2011, 23:30 GMT
Reason for closing: Works for me
Additional comments about closing: no reproducable segfaults here. many packages including glib2, glibc and midori had updates since the reports. no response from the user so far.
Saturday, 12 February 2011, 23:30 GMT
Reason for closing: Works for me
Additional comments about closing: no reproducable segfaults here. many packages including glib2, glibc and midori had updates since the reports. no response from the user so far.
Comment by Andreas Radke (AndyRTR) -
Wednesday, 24 November 2010, 17:01 GMT
you may try to downgrade the glib2 pkg. a pkg rebuild is also worth a try. but probably this is an upstream bug and should be reported there.