retitle 263952 xserver-xfree86: rendering problems with xclock on some XINERAMA screens reassign 263952 xserver-xfree86 tag 263952 + moreinfo upstream thanks
On Fri, Aug 06, 2004 at 01:46:07PM +0200, Jan-Benedict Glaw wrote: > Package: xbase-clients > Version: 4.3.0.dfsg.1-6 > Distribution: sid > Architecture: i386 > > Hi! > > If I start xclock on my xinerama screen (three horizontally ordered > CRTs), hour and minute pointers and the outer scale are only visible > when the window in on the middle screen (which is the "primary" screen > of the three. The other two are declared as LeftOf/RightOf the middle > one.) This is almost certainly a driver problem, so I'm going need more information about your X server. I've placed some instructions for gathering that information at the end of this message. One way to prove that this *isn't* a driver problem is to do a screen capture (say, with xwd, but the GNOME and KDE desktops have apps for this as well) of the xclock window when it's on one of the screens where it renders wrong. If the screen capture *doesn't* the pointers and scale, then this may be an xclock bug (or possibly widget library bug) after all. But I'm betting they'll be there, and definitely show up when you view the screen capture image in the middle screen. [The following is a form letter.] Dear bug submitter, Since the XFree86 X server is a large and complex piece of software, some more information is required of you before this bug can be handled. Please run the following commands from a shell prompt to gather and deliver this information to us: $ /usr/share/bug/xserver-xfree86 > /tmp/output 3>&1 $ mailx -s "Re: Bug#BUGNUMBER" [EMAIL PROTECTED] < /tmp/output If you do not have a "mailx" command on your system, you can get it by installing the "mailx" Debian package; for example, with the "aptitude install mailx" or "apt-get install mailx" commands as root. Alternatively, you can also use a mail command that is compatible with mailx's command-line syntax, such as "mutt". One very good way to file bugs with the Debian Bug Tracking System is to use the "reportbug" package and command of the same name. The reportbug program does a lot of automatic information-gathering that helps package maintainers to understand your system configuration, and also ensures that your message to the Debian Bug Tracking System is well-formed so that it is processed correctly by the automated tools that manage the reports. (If you've ever gotten a "bounce" message from the Debian Bug Tracking System that tells you your message couldn't be processed, you might appreciate this latter feature.) Therefore, I strongly urge you to give "reportbug" a try as your primary bug reporting tool for the Debian System in the future. If you *did* use reportbug to file your report, then you're receiving this message because the information we expected to see was not present. If you deliberately deleted this information from the report, please don't do that in the future, even if it seems like it makes the mail too large. 50 kB (kilobytes) of configuration and log data is typical. Only if the included information greatly exceeds this amount (more than 100 kB) should you consider omitting it; instead, put it up on the World Wide Web somewhere and provide URLs to it in your report, or in subsequent followup by mailing <[EMAIL PROTECTED]>. Thank you! -- G. Branden Robinson | Reality is what refuses to go away Debian GNU/Linux | when I stop believing in it. [EMAIL PROTECTED] | -- Philip K. Dick http://people.debian.org/~branden/ |
signature.asc
Description: Digital signature
