|
Bugzilla – Full Text Bug Listing |
| Summary: | Unable to change size/position of screen with xfine2 | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | narayan aras <narayanaras> |
| Component: | X.Org | Assignee: | Stefan Dirsch <sndirsch> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <xorg-maintainer-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | chrubis |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | SAX log | ||
|
Description
narayan aras
2007-11-30 02:18:29 UTC
The "banned" 3D sign IMHO means that graphics card driver you that is installed doesn't support 3D acceleration. - the tiny handles are simple markers for the corners of the visual area they are not meant to be dragged or clicked or something - the "banned" 3D icon means that 3D is not activated. This is either because it can't be activated or the card or the driver doesn't support 3D - if nothing happens if you click on one of the four arrow buttons this means the maximum resizing boundaries are already reached. In former times we popup a window telling that to the user but our usability people said that's an annoying thing to do so ;) - the problem I identify in your report is that you want 800x600 but got 1284x1024 which is a very strange resolution. I'm pretty sure the configuration file will include the 800x600 but the driver denies for some reason to use this resolution. As I think this is a driver problem you should provide the Xorg.*log messages for further observations. Assigned to maintainer Please attach /var/log/SaX.log. Could you please provide the requested information? Sorry for the delay. I did not have access to mail for some days. Unfortunately I had to change over to Windows XP on the PC I had described originally, as it was unable to work with HP 1020 Plus printer (despite my installing the 3rd party driver from http://foo2zjs.rkkda.com/ successfully). But the good news is that I can reproduce the same problem in my another PC, which is dual boot (Win XP, SP-2). The hardware is different, so please ask me if anything is left out. BTW the xfine2 is unable to REDUCE the screen size in x or y axis. Since it may have reached max, it cannot move in x or y direction, either. The SAW2 screen shows that the 3D acceleration is activated (there is a cross in that check box). I am attaching the log file here. Thanks. Created attachment 187973 [details]
SAX log
This is from my other PC (not the one described in the beginning of the bug).
This PC has P-4 3 GHz CPU, with HT.
This time it's Intel 915G onboard graphics using the "intel" driver. So which issues are remaining with this hardware now? Please also attach the output of "xrandr". This looks like a duplicate of Bug #257746 All problems happen in this PC also. (Actually I didn't report the problem earlier because in this PC, I could "somehow" set the desktop resolution. But in the other PC, the resolution remained so high that I was unable to read any text, menus or icons. * 3D banned (despite the fact that SAW2 shows that 3D accelerator is activated). * Cannot resize/move the screen. I will post the other file tonight. > * 3D banned (despite the fact that SAW2 shows that 3D accelerator is > activated). I think you started SaX2 on top of a running Xserver with already enabled 3D support (which is fine). Unfortunately then the test Xserver, which is started by SaX2, disables 3D support. This is a known DRI limitation and cannot easily be changed/fixed. > * Cannot resize/move the screen. See comment #2. So all in all this is a duplicate. *** This bug has been marked as a duplicate of bug 257746 *** 1. So are you saying that saX2 is normally unusable unless we close Xserver? That is terrible: All I did was to start the openSUSE GUI just as I start Windows. OK if I disable/close the running Xserver, will saX2 do its work? Should I start from the command prompt rather than GUI? And am I supposed to restart xserver afterwards? At least if this is an issue, the OpenSUSE community should post a step-by-step guidance for newbies like me; so that they don't have to grope in the dark. Bug apart, what am I supposed to DO next? 2. Bug 257746 says that only higher resolutions beyond a certain value are not accepted (In other words, in his case, xfine2 **DOES** work for the lower resolutions). But in my case xfine2 does not work at all, at any resolution. How can they be the same bug?? ad1: SaX2 does its work. 3D is enabled. It's just confusing that it makes you think it isn't enabled when running on top of a 3D enabled Xserver. Unusable is different in my opinion. Do not expect any changes in SaX2 here. ad2: 2 workarounds are available: a) using Option "PreferredMode" b) changing resolution with xrandr BTW, it's rather exotic to run a 1280x1024 monitor with a "800x600" resolution. |