Bug 761346 - X Window crashes when executing "gvim -geometry 1680x1050+0+0" on a Radeon HD 2400 system
Summary: X Window crashes when executing "gvim -geometry 1680x1050+0+0" on a Radeon HD...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: 16
Hardware: i686
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Jérôme Glisse
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-08 06:26 UTC by Need Real Name
Modified: 2013-02-13 14:58 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 14:58:34 UTC
Type: ---


Attachments (Terms of Use)
Xorg.0.log. (47.88 KB, text/plain)
2012-02-13 07:41 UTC, Need Real Name
no flags Details

Description Need Real Name 2011-12-08 06:26:05 UTC
Description of problem:
On an ATI Radeon HD 2400 PRO 1680x1050 display, the X window crashes when executing the command "gvim -geometry 1680x1050+0+0"

Version-Release number of selected component (if applicable):
xorg-x11-drv-ati-6.14.3-3.20111125git534fb6e41.fc16.i686
vim-X11-7.3.315-1.fc16.i686

How reproducible:
Always.

Steps to Reproduce:
1. Launch the command "gvim -geometry 1680x1050+0+0" in a terminal window
2. 
3.
  
Actual results:
The window system crashes.

Expected results:
gvim window

Additional info:

Comment 1 Dave Airlie 2012-02-12 20:05:22 UTC
can you post /var/log/Xorg.0.log it should have a backtrace in it.

Also please try latest X server and ati driver from F16 updates.

Comment 2 Need Real Name 2012-02-13 07:41:04 UTC
Created attachment 561433 [details]
Xorg.0.log.

Xorg.0.log attached. Do I need to add some options to the X server in order to get a backtrace?

Comment 3 Dave Airlie 2012-02-13 07:57:07 UTC
EXA: malloc failed for size 1860064000 bytes

that looks bad, will see if I can work out why

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

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

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 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 to click on 
"Clone This Bug" 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

Comment 5 Fedora End Of Life 2013-02-13 14:58:38 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.

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.