Bug 569353

Summary: [abrt] crash in barrage-1.0.2-5.fc12: Process /usr/bin/barrage was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Kostis <warlordfff>
Component: barrageAssignee: Gwyn Ciesla <gwync>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: gabriel.c.cook, gwync, jholton
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:44993aa49f98bb9e60ff6308440b0c07a74ade9c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-03-19 14:54:36 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:
Description Flags
File: backtrace none

Description Kostis 2010-03-01 12:08:15 UTC
abrt 1.0.7 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: barrage
component: barrage
executable: /usr/bin/barrage
kernel: 2.6.31.12-174.2.22.fc12.i686.PAE
package: barrage-1.0.2-5.fc12
rating: 4
reason: Process /usr/bin/barrage was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

Comment 1 Kostis 2010-03-01 12:08:19 UTC
Created attachment 397047 [details]
File: backtrace

Comment 2 John Holton 2010-03-19 06:05:37 UTC

How to reproduce
-----
1.Started Barrage
2.Screen changed to 640x480
3.Error showed
4. Had to reboot to recover resolution of 1024x768


Comment
-----
Just started up Barrage

Comment 3 Gwyn Ciesla 2010-03-19 14:09:46 UTC
You can actually go into System->Preferences->Display and correct the resolution there.  If the window for it appears off screen, right click on the taskbar box for it and click Move, then move the mouse to the left.

I'm working on this currently.  It's a buffer overflow, but I'm having a hard time tracking it down . . .

Comment 4 Gwyn Ciesla 2010-03-19 14:54:36 UTC

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