Bug 629167 - [abrt] midori-0.2.6-1.fc13: Process /usr/bin/midori was killed by signal 11 (SIGSEGV)
Summary: [abrt] midori-0.2.6-1.fc13: Process /usr/bin/midori was killed by signal 11 (...
Keywords:
Status: CLOSED DUPLICATE of bug 628761
Alias: None
Product: Fedora
Classification: Fedora
Component: midori
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Peter Gordon
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:a501a5d624b652994ca82947dc6...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-01 06:41 UTC by dedanna
Modified: 2010-09-01 06:45 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-09-01 06:45:04 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (1.36 KB, text/plain)
2010-09-01 06:42 UTC, dedanna
no flags Details

Description dedanna 2010-09-01 06:41:58 UTC
abrt version: 1.1.13
architecture: i686
cmdline: midori
comment: See also bug # 628761, if this files a new bug. That was the purpose of this. Thanks.
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: 1283322969
uid: 500

backtrace
-----
[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

How to reproduce
-----
1. I clicked Facebook from Speed Dial
2. Went into Facebook, posted a couple things, and then logged out
3. I clicked off Midori, and that's when it crashed

Comment 1 dedanna 2010-09-01 06:42:00 UTC
Created an attachment (id=442341)
File: backtrace

Comment 2 dedanna 2010-09-01 06:45:04 UTC

*** This bug has been marked as a duplicate of bug 628761 ***


Note You need to log in before you can comment on or make changes to this bug.