Midori starts normally, and tabs with previously loaded url's may load normally. However if one selects a link in a loaded page, or enters a new url in a blank tab, midori crashes. This includes selecting links in a midori home site (midori-browser.org) to another page in the same site. In some cases it crashes if select a tab that was already loaded from a previous session. Note that did not have this problem under mga3, and maybe not at first under mga4. (Don't yet regularly use Midori.) Running in console gives : ---- 00:15 ~ $ midori & [1] 2194 00:15 ~ $ (midori4:2194): Gtk-WARNING **: Error loading theme icon 'text-x-javascript' for stock: L'icône « text-x-javascript » n'est pas présente dans le thème (midori4:2194): Gtk-WARNING **: Error loading theme icon 'application-x-shockwave-flash' for stock: L'icône « application-x-shockwave-flash » n'est pas présente dans le thème #just-before-select-url# pure virtual method called terminate called without an active exception #just after-select-url# [1]+ Abandon midori ---- The output (and crash) is identical 1) if click on a link in an already loaded page, or 2) if press return after typing (or copy/paste) a new link a blank tab, or 3) (sometimes) if select another already loaded tab. Note also that other functions, such as editting preferences and scanning the menus, seem to work normally.
also 23:59 ~ $ midori --version Midori midori-0.5.5 ((null)) GTK+ 2.24.22 (2.24.22) Glib 2.38.1 (2.38.2) WebKitGTK+ 2.2.0 (2.2.2) libSoup 2.44.1 cairo 1.12.16 (1.12.16) libnotify 0.7.6 gcr No granite No single instance libunique 1.1.6 (all mga4 up to date) This may have the same cause as mga#13791 on cauldron, i586 reported 2 months ago.
Status: NEW => UNCONFIRMEDEver confirmed: 1 => 0
CC'ing Cesar and Jani.
CC: (none) => cvargas, jani.valimaa, remi
The midori faq page cites a similar problem with glib 2.16 and recommends updating to glib 2.18. Note that comment 1 shows that glib is already at 2.38
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Status: UNCONFIRMED => RESOLVEDResolution: (none) => OLD