Bug 1037789
| Summary: | Midori segfaults when using default search engine | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Paul Whalen <pwhalen> | ||||||||||
| Component: | webkitgtk | Assignee: | Kevin Fenzi <kevin> | ||||||||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 20 | CC: | huzaifas, kevin, martin.sourada, mruckman, mtasaka, tpopela | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | arm | ||||||||||||
| OS: | Linux | ||||||||||||
| Whiteboard: | AcceptedFreezeException | ||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2015-06-30 00:45:47 UTC | Type: | Bug | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Bug Depends On: | |||||||||||||
| Bug Blocks: | 245418, 980657 | ||||||||||||
| Attachments: |
|
||||||||||||
Created attachment 832282 [details]
Midori gdb
Can you get a 'where' in the gdb to see where it's actually crashing? Also, can you try the midori update thats already in updates-testing? 'yum --enablerepo=updates-testing update midori' Created attachment 832285 [details]
Midori gdb2
Updated to midori-0.5.6-1.fc20, new log for gdb. ok. Does: /usr/libexec/webkitgtk/GtkLauncher behave the same way when going to duckduckgo? Can you: debuginfo-install webkitgtk and re-run the gdb? (In reply to Kevin Fenzi from comment #5) > ok. > > Does: > > /usr/libexec/webkitgtk/GtkLauncher > > behave the same way when going to duckduckgo? It does. > > Can you: > > debuginfo-install webkitgtk > > and re-run the gdb? webkitgtk-debuginfo-2.2.2-1.fc20.armv7hl was installed ok, then the actual issue is in webkitgtk. Moving to there. Discussed in 2013-12-04 Blocker Review Meeting [1]. Voted as an AcceptedFreezeException. A fix will be considered past freeze if the fix is timely and does not affect other architectures. [1] http://meetbot.fedoraproject.org/fedora-blocker-review/2013-12-04/ Can you also try the webkitgtk from this scratch build: http://koji.fedoraproject.org/koji/taskinfo?taskID=6256937 It has some cflags change to hopefully make more useful debuginfo (you will also need to install the debuginfo from it instead of the repo version). Thanks Created attachment 833251 [details]
midori gdb 4
Attached new log including the above scratch build and midori-0.5.6-1.fc20. I've made a scratch build[1] of new unstable webkitgtk release and it's not crashing there. So good news is that it is fixed and now we have to find the right commit. [1] - http://koji.fedoraproject.org/koji/taskinfo?taskID=6278926 This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. 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 Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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 Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |
Created attachment 832281 [details] Midora Strace Description of problem: Attempting to use the default search engine 'Duck Duck Go' results in crash. Version-Release number of selected component (if applicable): midori-0.5.5-2.fc20 How reproducible: Everytime Steps to Reproduce: 1. Launch Midori in F20-TC4 ARM XFCE image 2. Enter text in 'Duck Duck Go' search toolbar Actual results: Page attempts to load search results and quickly crashes. Expected results: Search results. Additional info: gdb,strace logs attached.