Bug 796652 - Partially wrong card layout in aisleriot (cards of value 10 and 5)
Summary: Partially wrong card layout in aisleriot (cards of value 10 and 5)
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: aisleriot
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-23 11:46 UTC by Joachim Backes
Modified: 2012-03-29 11:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-29 11:28:05 UTC
Type: ---


Attachments (Terms of Use)
Displays wrong cards of value 10 (135.28 KB, image/png)
2012-02-23 11:46 UTC, Joachim Backes
no flags Details

Description Joachim Backes 2012-02-23 11:46:20 UTC
Created attachment 565280 [details]
Displays wrong cards of value 10

Description of problem:

In some card styles, cards of value 10 are not correctly displayed: Value 10 appears as value 0 (zero). If cards have the value 5 (five), the cipher 5 is uncomplete.

I saw this in the gnomangelo card style if running under gnome-shell.

Version-Release number of selected component (if applicable):
aisleriot-3.3.0-1.fc17.x86_64

How reproducible:
always

Steps to Reproduce:
1.See description
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Matthias Clasen 2012-03-07 19:40:56 UTC
Probably the same issue as
https://bugzilla.gnome.org/show_bug.cgi?id=669319

Comment 2 Matthias Clasen 2012-03-07 20:27:41 UTC
Does running sol with GDK_RENDERING=image in the environment make the problem go away ?

Comment 3 Joachim Backes 2012-03-08 06:12:06 UTC
(In reply to comment #2)
> Does running sol with GDK_RENDERING=image in the environment make the problem
> go away ?

Yes, it does :-)

Comment 4 Matthias Clasen 2012-03-08 15:33:06 UTC
probably a driver issue then

Comment 5 Joachim Backes 2012-03-29 11:28:05 UTC
Problem went away (runs correctly without GDK_RENDERING=image) too after having applied all F17 updates available until today (march 29).


Note You need to log in before you can comment on or make changes to this bug.