Bug 884778 - [abrt] dillo-3.0.2-3.fc18: next_visible_or_not: Process /usr/bin/dillo was killed by signal 11 (SIGSEGV)
Summary: [abrt] dillo-3.0.2-3.fc18: next_visible_or_not: Process /usr/bin/dillo was ki...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: dillo
Version: 18
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Andreas Bierfert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:4c01ce473d4f4cb053138e40a47...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-06 17:34 UTC by Sergio
Modified: 2014-02-05 22:54 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-05 22:54:35 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (23.99 KB, text/plain)
2012-12-06 17:34 UTC, Sergio
no flags Details
File: cgroup (128 bytes, text/plain)
2012-12-06 17:34 UTC, Sergio
no flags Details
File: core_backtrace (3.08 KB, text/plain)
2012-12-06 17:34 UTC, Sergio
no flags Details
File: dso_list (3.71 KB, text/plain)
2012-12-06 17:34 UTC, Sergio
no flags Details
File: environ (1015 bytes, text/plain)
2012-12-06 17:34 UTC, Sergio
no flags Details
File: limits (1.29 KB, text/plain)
2012-12-06 17:34 UTC, Sergio
no flags Details
File: maps (11.60 KB, text/plain)
2012-12-06 17:34 UTC, Sergio
no flags Details
File: open_fds (193 bytes, text/plain)
2012-12-06 17:34 UTC, Sergio
no flags Details
File: proc_pid_status (769 bytes, text/plain)
2012-12-06 17:34 UTC, Sergio
no flags Details
File: var_log_messages (277 bytes, text/plain)
2012-12-06 17:34 UTC, Sergio
no flags Details

Description Sergio 2012-12-06 17:34:13 UTC
Description of problem:
I was browsing/selecting stuff in bugzilla.redhat.com 'advanced search' page and it crashed. Unfortunately I couldn't reproduce the crash (I couldn't even make that page open afterwards :-)  ).
Dillo has crashed before for me in Fedora 18. I have no idea if it was related to the fltk update or not.

Version-Release number of selected component:
dillo-3.0.2-3.fc18

Additional info:
backtrace_rating: 4
cmdline:        dillo
crash_function: next_visible_or_not
executable:     /usr/bin/dillo
kernel:         3.6.9-4.fc18.i686
remote_result:  NOTFOUND
uid:            1000
xsession_errors: 

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 next_visible_or_not at Fl_Menu.cxx:52
 #1 Fl_Menu_Item::next at Fl_Menu.cxx:74
 #2 setitem at Fl_Menu.cxx:598
 #3 menuwindow::early_hide_handle at Fl_Menu.cxx:764
 #4 menuwindow::handle at Fl_Menu.cxx:635
 #5 send at Fl.cxx:1104
 #6 Fl::handle_ at Fl.cxx:1281
 #7 Fl::handle at Fl.cxx:1184
 #8 do_queued_events at Fl_x.cxx:208
 #9 fl_wait at Fl_x.cxx:275

Comment 1 Sergio 2012-12-06 17:34:16 UTC
Created attachment 658893 [details]
File: backtrace

Comment 2 Sergio 2012-12-06 17:34:18 UTC
Created attachment 658894 [details]
File: cgroup

Comment 3 Sergio 2012-12-06 17:34:20 UTC
Created attachment 658895 [details]
File: core_backtrace

Comment 4 Sergio 2012-12-06 17:34:22 UTC
Created attachment 658896 [details]
File: dso_list

Comment 5 Sergio 2012-12-06 17:34:25 UTC
Created attachment 658897 [details]
File: environ

Comment 6 Sergio 2012-12-06 17:34:27 UTC
Created attachment 658898 [details]
File: limits

Comment 7 Sergio 2012-12-06 17:34:29 UTC
Created attachment 658899 [details]
File: maps

Comment 8 Sergio 2012-12-06 17:34:31 UTC
Created attachment 658900 [details]
File: open_fds

Comment 9 Sergio 2012-12-06 17:34:33 UTC
Created attachment 658901 [details]
File: proc_pid_status

Comment 10 Sergio 2012-12-06 17:34:35 UTC
Created attachment 658902 [details]
File: var_log_messages

Comment 11 Sergio 2012-12-07 13:24:06 UTC
I linked this bug in the Dillo bug tracker so the devs may look at it.
# 1109 at http://www.dillo.org/cgi-bin/bugtrack/Dillo_query.cgi?what=se&Submit=Find+It!

Comment 12 Sergio 2012-12-14 13:27:33 UTC
I received an email from Dillo developer Jorge Arellano Cid because I reported this on Dillo's bug tracker too. Quoting:

" Corvid found there're issues with fltk-1.3.0, that don't happen
with fltk-1.3.1. Details [1], full thread [2].
  (if  you  continue  the Fedora bug thread, make them know this,
and BTW that the current fltk is fltk-1.3.2; a bug fix release).


[1] http://lists.auriga.wearlab.de/pipermail/dillo-dev/2012-December/009609.html
[2] http://lists.auriga.wearlab.de/pipermail/dillo-dev/2012-December/009603.html
"

Comment 13 Fedora End Of Life 2013-12-21 15:14:18 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.

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 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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.

Comment 14 Fedora End Of Life 2014-02-05 22:54:35 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.


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