Bug 155319 - Xgl on Pegasos PPC problems: writing in xterm
Summary: Xgl on Pegasos PPC problems: writing in xterm
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Xgl (show other bugs)
Version: Beta 6
Hardware: PowerPC Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: David Reveman
QA Contact: Stefan Dirsch
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-05 15:23 UTC by peter czanik
Modified: 2007-02-01 17:44 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
screen shot of corrupted xterm (53.03 KB, image/png)
2006-03-05 15:23 UTC, peter czanik 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description peter czanik 2006-03-05 15:23:04 UTC 
Xgl runs fine on Pegasos, it's a very nice eye candy. But there are some problems: if someone types text in xterm (or any other terminal emulator I tried), most of the characters are replaced by black blocks or just garbage on screen.
When one clicks on the window, garbage is replaced by correct characters on screen.
Comment 1 peter czanik 2006-03-05 15:23:44 UTC 
Created attachment 71275 [details]
screen shot of corrupted xterm
Comment 2 Matthias Fruehauf 2006-05-04 19:50:10 UTC 
Peter, is this still an issue with latest Betas/RCs?
Comment 3 peter czanik 2006-05-04 21:32:08 UTC 
Xgl in the latest RCs did not work at all. I'm just downloading factory, as I see, that there were significant changes recently. I'll check it tomorrow.
Comment 4 peter czanik 2006-05-05 09:12:22 UTC 
Just tested this morning on a freshly downloaded factory: Xgl practically does not work at all on now PPC & OSS Radeon driver. KDE crashes a few seconds after it started, KDM is extremely slow, GNOME starts, but does not respond to anything.
Comment 6 JP Rosevear 2007-02-01 17:44:48 UTC 
I'm going to close this, this likely a driver bug and the X guys have said ppc/3D support is inherently flakey.