SIGFPE in create_dpis() in QPaintDevice::~QPaintDevice
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | qt-x11-free (Debian) |
Fix Released
|
Unknown
|
||
| | qt-x11-free (Ubuntu) |
Medium
|
Simon Law | ||
Bug Description
The fglrx binary driver has a bug in it when you suspend and resume or when you use XRandR. It will set your screen size to 0x0mm, which is an impossible situation.
In this nonsense case, we want to assume the screen is some reasonable default so that our applications will just work. This could be the Xft.dpi resource or if that doesn't exist, then fallback to 96dpi which is the KDE standard.
| Simon Law (sfllaw) wrote : | #1 |
| Changed in qt-x11-free: | |
| assignee: | nobody → sfllaw |
| importance: | Undecided → Medium |
| status: | Unconfirmed → In Progress |
| Changed in qt-x11-free: | |
| status: | Unknown → Unconfirmed |
| Daniel Holbach (dholbach) wrote : | #2 |
Simon: how's this going?
| Changed in qt-x11-free: | |
| status: | In Progress → Needs Info |
| Ken Phillis Jr (kphillisjr) wrote : | #3 |
i can confirm this bug, it occurs when your using TV output.
| Ken Phillis Jr (kphillisjr) wrote : | #4 |
i got the information that is required, and it's not to hard.... just look at the xdpyinfo for each effected box, it should turn out somethin like this ( notice screen # 1 on my box )
xdpyinfo | grep -a2 dimen
screen #0:
dimensions: 1280x1024 pixels (370x280 millimeters)
resolution: 88x93 dots per inch
depths (7): 24, 1, 4, 8, 15, 16, 32
--
screen #1:
dimensions: 800x600 pixels (0x0 millimeters)
resolution: -2147483648x-
depths (7): 24, 1, 4, 8, 15, 16, 32
| Ken Phillis Jr (kphillisjr) wrote : | #5 |
got a patch that fixes the issues with the dpi's, but the problem might still occure with other apps, please resort to testing them as to figure this out, and so far i am certain that the new control panel for ati cards that is in the binary package is not fixed by this repair.
| Simon Law (sfllaw) wrote : | #6 |
The patch looks like it solves the problem, although you probably only want one test for (DisplayWidthMM
Thanks!
| Ken Phillis Jr (kphillisjr) wrote : | #7 |
actually, i wanted to check the height and width, and if i am checking width twice, taht means that the second test needs to be for this statement here:
(DisplayHeightM
instead of what it is now, which is:
(DisplayWidthMM
change that line to the appropriate check and it'll work even better, because it won't let the applications crash due to having a 0 for the height and/or width.
| Ken Phillis Jr (kphillisjr) wrote : | #8 |
just upgraded to feisty, and the pesky bug returned, but of course i didn't patch my install with my own patch so it is verified.
| Ken Phillis Jr (kphillisjr) wrote : | #9 |
I just updated the patch to feisty level, so here's the new patch.
| Jonathan Riddell (jr) wrote : | #10 |
Patch applied in qt-x11-
| Changed in qt-x11-free: | |
| status: | Needs Info → Fix Released |
| Ken Phillis Jr (kphillisjr) wrote : | #11 |
on my machine it works just fine, no word from others who had this issue.
| Changed in qt-x11-free: | |
| status: | New → Fix Released |
I'll hack on this.