Bug 954072 - [abrt] newsbeuter-2.6-1.fc18: newsbeuter::view::force_redraw: Process /usr/bin/newsbeuter was killed by signal 11 (SIGSEGV)
Summary: [abrt] newsbeuter-2.6-1.fc18: newsbeuter::view::force_redraw: Process /usr/bi...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: newsbeuter
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Nobody's working on this, feel free to take it
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:5ffc3e7449c202bf41575d3a05f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-20 12:10 UTC by frywalker
Modified: 2020-11-05 09:55 UTC (History)
2 users (show)

Fixed In Version: newsbeuter-2.7-1.fc18
Clone Of:
Environment:
Last Closed: 2013-09-29 01:29:29 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (72.39 KB, text/plain)
2013-04-20 12:10 UTC, frywalker
no flags Details
File: cgroup (134 bytes, text/plain)
2013-04-20 12:10 UTC, frywalker
no flags Details
File: core_backtrace (816 bytes, text/plain)
2013-04-20 12:10 UTC, frywalker
no flags Details
File: dso_list (3.74 KB, text/plain)
2013-04-20 12:10 UTC, frywalker
no flags Details
File: environ (3.05 KB, text/plain)
2013-04-20 12:11 UTC, frywalker
no flags Details
File: limits (1.29 KB, text/plain)
2013-04-20 12:11 UTC, frywalker
no flags Details
File: maps (22.89 KB, text/plain)
2013-04-20 12:11 UTC, frywalker
no flags Details
File: open_fds (238 bytes, text/plain)
2013-04-20 12:11 UTC, frywalker
no flags Details
File: proc_pid_status (940 bytes, text/plain)
2013-04-20 12:11 UTC, frywalker
no flags Details
File: var_log_messages (411 bytes, text/plain)
2013-04-20 12:11 UTC, frywalker
no flags Details

Description frywalker 2013-04-20 12:10:46 UTC
Version-Release number of selected component:
newsbeuter-2.6-1.fc18

Additional info:
backtrace_rating: 4
cmdline:        newsbeuter
crash_function: newsbeuter::view::force_redraw
executable:     /usr/bin/newsbeuter
kernel:         3.8.5-201.fc18.x86_64
uid:            1000
ureports_counter: 1

Truncated backtrace:
Thread no. 1 (4 frames)
 #0 newsbeuter::view::force_redraw at src/view.cpp:809
 #1 newsbeuter::controller::reload_all at src/controller.cpp:895
 #2 newsbeuter::downloadthread::run at src/downloadthread.cpp:24
 #3 newsbeuter::run_thread at src/thread.cpp:45

Comment 1 frywalker 2013-04-20 12:10:49 UTC
Created attachment 737969 [details]
File: backtrace

Comment 2 frywalker 2013-04-20 12:10:53 UTC
Created attachment 737970 [details]
File: cgroup

Comment 3 frywalker 2013-04-20 12:10:55 UTC
Created attachment 737971 [details]
File: core_backtrace

Comment 4 frywalker 2013-04-20 12:10:58 UTC
Created attachment 737972 [details]
File: dso_list

Comment 5 frywalker 2013-04-20 12:11:00 UTC
Created attachment 737973 [details]
File: environ

Comment 6 frywalker 2013-04-20 12:11:02 UTC
Created attachment 737974 [details]
File: limits

Comment 7 frywalker 2013-04-20 12:11:04 UTC
Created attachment 737975 [details]
File: maps

Comment 8 frywalker 2013-04-20 12:11:07 UTC
Created attachment 737976 [details]
File: open_fds

Comment 9 frywalker 2013-04-20 12:11:09 UTC
Created attachment 737977 [details]
File: proc_pid_status

Comment 10 frywalker 2013-04-20 12:11:11 UTC
Created attachment 737978 [details]
File: var_log_messages

Comment 11 Jamie Nguyen 2013-05-26 11:58:04 UTC
What were you doing when this error occurred? Has this happened more than once? Are you able to reproduce it?

Comment 12 Štefan Gurský 2013-07-04 08:59:53 UTC
How to reproduce:
1. Have a browser set to lynx (probably any console browser would work)
2. Refresh all feeds (shortcut R)
3. While they are refreshing, open any article in browser (in one that uses same terminal window)
4. wait

After newsbeuter is done refreshing feeds it calls function force_redraw and it seems to crash if something else (other program) is displayed on newsbeuter's terminal.

Comment 13 Štefan Gurský 2013-08-31 21:38:08 UTC
I believe this is the correct bug in upstream tracker: http://code.google.com/p/newsbeuter/issues/detail?id=323 There seems to be some fix.

Comment 14 Jamie Nguyen 2013-09-03 22:32:32 UTC
newsbeuter 2.7 should fix this.

Comment 15 Fedora Update System 2013-09-03 22:33:27 UTC
newsbeuter-2.7-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/newsbeuter-2.7-1.fc19

Comment 16 Fedora Update System 2013-09-03 22:33:54 UTC
newsbeuter-2.7-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/newsbeuter-2.7-1.fc18

Comment 17 Fedora Update System 2013-09-05 01:33:09 UTC
Package newsbeuter-2.7-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing newsbeuter-2.7-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-15793/newsbeuter-2.7-1.fc18
then log in and leave karma (feedback).

Comment 18 Fedora Update System 2013-09-29 01:29:29 UTC
newsbeuter-2.7-1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 19 Fedora Update System 2013-09-29 01:41:55 UTC
newsbeuter-2.7-1.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.


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