Bug 628761
| Summary: | [abrt] midori-0.2.6-1.fc13: Process /usr/bin/midori was killed by signal 11 (SIGSEGV) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | dedanna <skeeter1029> | ||||
| Component: | midori | Assignee: | Kevin Fenzi <kevin> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 13 | CC: | kevin, maxamillion, peter | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i686 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | abrt_hash:433b48fc623ee464b1cc5148f254b65f61f76f57 | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-06-28 13:40:54 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Created an attachment (id=442070) File: backtrace Sadly, something went wrong here with abrt and this debug trace is missing most all info. ;( Can you get it to happen everytime you login to facebook? Or is it sporadic? Can you try and get it to happen again and see if it sends a better trace? Sure, I can resubmit, but have a feeling it will file a new bug. I can mark it as a duplicate to this one. I never last any more than a couple of minutes in Midori, so if that doesn't work, I'll just run it again and let it crash, mark it as a dup to this. May be tomorrow though. Bedtime here. Thanks. Package: midori-0.2.6-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. I tried to sign into Facebook via the home page link (the page where you can choose up to six of your most-used links) 2. Midori crashed 3. Comment ----- Start Midori, go to your favorite site or use one of the shortcuts that it gives you on your home page for it, and it crashes. Not much else to say. I think I'll just let it crash tomorrow. It actually found this bug, but didn't give the backtrace. I tried again, and this time it let me go into Facebook from the Speed Dial page, I made a couple of posts there, logged out, and clicked off Midori with the "X". That's when it crashed this time. It did file a new bug; the backtrace I could get was this: [New Thread 22581] [New Thread 22582] [New Thread 22583] [New Thread 22584] [New Thread 22749] warning: "/var/cache/abrt-di/usr/lib/debug/.build-id/b0/92e943ad63f83804af87c5bc62b0c1a9610a8d.debug": separate debug info file has no debug info Core was generated by `midori'. Program terminated with signal 11, Segmentation fault. #0 pango_layout_clear_lines (layout=0xbfe259a8) at pango-layout.c:2726 2726 pango-layout.c: No such file or directory. in pango-layout.c Timeout exceeded: 60 second, killing gdb Debuginfo absent: 014c45265615b500bfafa82232e2e9c441ed5f2a Debuginfo absent: 2aa8814d66f4508fc86c528d2f5fb23efd7422e5 Debuginfo absent: 43bb5b65b6bc1af0b2c4a41c2d8b72766c7c7936 Debuginfo absent: 48f7deddb3f2fcd45325ebe4c430e8355a17ea8a Debuginfo absent: 54cc7ce3ac9cc177ae2cc26e1c60b7ddb76fb3ac Debuginfo absent: 71d9e8f607d342765cd9a026987e562ae7d0eaa1 Debuginfo absent: 79cc7d3a448126aa8c086754f82177b9469ed0b2 Debuginfo absent: 85566d6e6d0df58cbcc48a834b472ba80dea1c17 Debuginfo absent: 893e32b347fff835250434714c9534c2f97b8e98 Debuginfo absent: 8e02802b491297a7c88ad8c6432dff932321a941 Debuginfo absent: b168f3a86b0ab8d3f0f7542b09a846002cb4202d Debuginfo absent: be58d91b4aa12a72cd4c80f370336fd62e669094 Debuginfo absent: ca1f57b08c6d0360bea4bfb3d93bdbcb5742791e Debuginfo absent: f5d20bf9973e5167df4cbb7d2d1615167a4b3bd4 Debuginfo absent: faf069d959d6feeb62fea69772842a5aaa06edb5 ... which still isn't much, I'm afraid. :( *** Bug 629167 has been marked as a duplicate of this bug. *** Yeah, weird. How about trying this: su debuginfo-install midori then duplicate the crash again and see if it generates a better backtrace? I'll note that here I can login to facebook just fine... ;( Sure. I'll try that. I really don't think the fact that whether one can or can't login to facebook has much to do with it. I think it may have to do more with Speed Dial, or another issue. I'm also wondering on pango: "pango_layout_clear_lines (layout=0xbfe259a8) at pango-layout.c:2726 2726 pango-layout.c: No such file or directory. in pango-layout.c" well, pango is the text layout library. Are you using default midori/fedora fonts? Have you changed those settings? If you create a brand new user, login as them and run midori, does the same crash occur? That would tell us if it was a user setting or a system wide issue. I'm using default midori/fedora, didn't change anything, other than place some favorites on Speed Dial. I'll try with a new user maybe tomorrow or the next day. Thanks. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. Can you try with: http://koji.fedoraproject.org/koji/taskinfo?taskID=2950913 and see if the problem persists? Sure, if it would take me to an actual package, and not to another page. Thanks. Scratch builds only stick around for 2 weeks. :) It's been a bit longer than that. I will see about whipping up a new one. Thanks. Sorry, due to financial constraints, I can't be online consistently. For this, many apologies. No problem. :) Sorry for the delay getting back to you here... Try this one: http://koji.fedoraproject.org/koji/taskinfo?taskID=3071208 Okay, so shoot me. I failed to mention that I upgraded to F14 since this bug was first reported, via preupgrade, etc. The version of Midori now is 0.2.9, and *so far* doesn't seem to be crashing; however, I haven't given it a full test run yet in it. Keep in mind, this is on the exact same desktop, just was upgraded to F14, so this was not a user issue. We need to find someone still on F13 to test it now, and see if they get the same as in the original post to this bug. Again, apologies. It didn't even dawn on me to mention it earlier. It did when I noticed the package you just referred me to was an F13 package. And, thank you for your time an attention on this. No problem. Go ahead and test out the f14 one, and if you run into issues, please report a new bug. We can leave this open and I can try and duplicate it again on a f13 host. Failing that it will get closed out when f13 reaches end of life. This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 WONTFIX if it remains open with a Fedora 'version' of '13'. 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 prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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. Thank you for reporting this bug and we are sorry it could not be fixed. |
abrt version: 1.1.13 architecture: i686 cmdline: midori comment: Start Midori, go to your favorite site or use one of the shortcuts that it gives you on your home page for it, and it crashes. Not much else to say. component: midori executable: /usr/bin/midori kernel: 2.6.33.8-149.fc13.i686 package: midori-0.2.6-1.fc13 rating: 4 reason: Process /usr/bin/midori was killed by signal 11 (SIGSEGV) release: Fedora release 13 (Goddard) time: 1283215381 uid: 500 backtrace ----- [New Thread 11205] [New Thread 11206] [New Thread 11207] [New Thread 11208] [New Thread 11370] warning: "/var/cache/abrt-di/usr/lib/debug/.build-id/b0/92e943ad63f83804af87c5bc62b0c1a9610a8d.debug": separate debug info file has no debug info Core was generated by `midori'. Program terminated with signal 11, Segmentation fault. #0 0x005b562b in addons_context_ready_cb (web_view= 0x94fe548 [WebKitWebView], web_frame=0x9754c60 [WebKitWebFrame], js_context=0xa8048324, js_window=0xac20b400, extension=0xbf884798) at ../extensions/addons.c:919 Timeout exceeded: 60 second, killing gdb Debuginfo absent: 014c45265615b500bfafa82232e2e9c441ed5f2a Debuginfo absent: 2aa8814d66f4508fc86c528d2f5fb23efd7422e5 Debuginfo absent: 43bb5b65b6bc1af0b2c4a41c2d8b72766c7c7936 Debuginfo absent: 48f7deddb3f2fcd45325ebe4c430e8355a17ea8a Debuginfo absent: 54cc7ce3ac9cc177ae2cc26e1c60b7ddb76fb3ac Debuginfo absent: 71d9e8f607d342765cd9a026987e562ae7d0eaa1 Debuginfo absent: 79cc7d3a448126aa8c086754f82177b9469ed0b2 Debuginfo absent: 85566d6e6d0df58cbcc48a834b472ba80dea1c17 Debuginfo absent: 893e32b347fff835250434714c9534c2f97b8e98 Debuginfo absent: 8e02802b491297a7c88ad8c6432dff932321a941 Debuginfo absent: b168f3a86b0ab8d3f0f7542b09a846002cb4202d Debuginfo absent: be58d91b4aa12a72cd4c80f370336fd62e669094 Debuginfo absent: ca1f57b08c6d0360bea4bfb3d93bdbcb5742791e Debuginfo absent: f5d20bf9973e5167df4cbb7d2d1615167a4b3bd4 Debuginfo absent: faf069d959d6feeb62fea69772842a5aaa06edb5 How to reproduce ----- 1. I tried to sign into Facebook 2. Midori crashed 3.