Bug 679172

Summary: [abrt] nntpgrab-gui-0.6.91-2.fc14: strncpy: Process /usr/bin/nntpgrab_gui was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: vafr <rf.av>
Component: nntpgrabAssignee: Erik van Pienbroek <erik-fedora>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: erik-fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:9408679140f164b235e8ef971861568a59fdd083
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 21:26:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description vafr 2011-02-21 19:44:05 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 30200 bytes
cmdline: nntpgrab_gui /tmp/Another.Day.in.Paradise.2008.1080p.BluRay.x264-HD4U.rar.nzb
component: nntpgrab
Attached file: coredump, 68694016 bytes
crash_function: strncpy
executable: /usr/bin/nntpgrab_gui
kernel: 2.6.35.11-83.fc14.x86_64
package: nntpgrab-gui-0.6.91-2.fc14
rating: 4
reason: Process /usr/bin/nntpgrab_gui was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1298316757
uid: 500

comment
-----
Now nntpgrab just dissapears from my desktop (crashes) every time when asked to 'Add thecontents of the NZB file toa new collection' 

How to reproduce
-----
1.Used nntpgrab without problems when using fc12
2.Upgraded to fc14. Restored my home directory with grsync and reinstalled nntpgrab
3.Now nntpgrab just dissapears from my desktop (crashes) every time when asked to 'Add thecontents of the NZB file toa new collection'

Comment 1 vafr 2011-02-21 19:44:08 UTC
Created attachment 479983 [details]
File: backtrace

Comment 2 Erik van Pienbroek 2011-02-21 22:33:17 UTC
What NZB search engine did you use? I think that the search engine in question produced an invalid NZB file which triggers a crash in NNTPGrab

Comment 3 vafr 2011-02-22 18:19:30 UTC
Same as before upgrading, used www.NZBIndex.nl (through firefox) to create an nzb file. This has worked without problems before, until I upgraded to fc14. 

I will check to verify if the same problem occurs with other nzb files from other sources.

Will keep you updated...

Comment 4 vafr 2011-02-22 18:28:13 UTC
by the way... these are the contents of the nzb file;

<?xml version="1.0" encoding="iso-8859-1" ?>
<!DOCTYPE nzb PUBLIC "-//newzBin//DTD NZB 1.0//EN" "http://www.newzbin.com/DTD/nzb/nzb-1.0.dtd">
<!-- NZB Generated by NZBIndex -->
<nzb xmlns="http://www.newzbin.com/DTD/2003/nzb">
<file poster="JBinUp.com (JBinUp)" date="1298153515" subject="Another.Day.in.Paradise.2008.1080p.BluRay.x264-HD4U.rar (1/17)">
<groups>
<group>alt.binaries.b4e</group>
<group>alt.binaries.boneless</group>
<group>alt.binaries.comp</group>
<group>alt.binaries.highspeed</group>
<group>alt.binaries.mom</group>
<group>alt.binaries.multimedia</group>
</groups>
<segments>
<segment bytes="199220" number="1">4d604028$3$17127$4c497a88</segment>
<segment bytes="197839" number="2">4d604028$4$17127$4c497a88</segment>
<segment bytes="196544" number="3">4d604028$5$17127$4c497a88</segment>
<segment bytes="196546" number="4">4d604028$6$17127$4c497a88</segment>
<segment bytes="196544" number="5">4d604029$0$17127$4c497a88</segment>
<segment bytes="196547" number="6">4d604029$1$17127$4c497a88</segment>
<segment bytes="196546" number="7">4d604029$2$17127$4c497a88</segment>
<segment bytes="196481" number="8">4d604029$3$17127$4c497a88</segment>
<segment bytes="196448" number="9">4d604029$4$17127$4c497a88</segment>
<segment bytes="196550" number="10">4d604029$6$17127$4c497a88</segment>
<segment bytes="196450" number="11">4d60402a$0$17127$4c497a88</segment>
<segment bytes="196483" number="12">4d60402a$1$17127$4c497a88</segment>
<segment bytes="196588" number="13">4d60402a$2$17127$4c497a88</segment>
<segment bytes="196483" number="14">4d60402a$3$17127$4c497a88</segment>
<segment bytes="196477" number="15">4d60402a$4$17127$4c497a88</segment>
<segment bytes="196452" number="16">4d60402a$5$17127$4c497a88</segment>
<segment bytes="76796" number="17">4d60402b$0$17127$4c497a88</segment>
</segments>
</file>
</nzb>

Comment 5 vafr 2011-02-23 18:32:49 UTC
problem solved (I think)...

Turned out that some of the directories NNTGrab uses ( NNTPGrab/NZB , NNTPGrab/Temp and some in NNTGrab/Downloads) were restored with incorrect properties (uid root , gid root).

Corrected them and now all seems to be ok.

Perhaps this is an (g)rsync issue instead. 

Happy now that it works as reliable and easy as it did before |-))

Comment 6 Fedora End Of Life 2012-08-16 21:26:44 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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 to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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