FS#17004 - [claws-mail] on i686 displays corrupted fonts

Attached to Project: Arch Linux
Opened by Rob (Painless) - Wednesday, 04 November 2009, 14:00 GMT
Last edited by Andrea Scarpino (BaSh) - Wednesday, 04 November 2009, 23:51 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Andreas Radke (AndyRTR)
Architecture i686
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

After upgrading from 3.7.2-1 to 3.7.3-1, claws-mail on i686 displays corrupted fonts in the folder list on starting - http://www.hyborian.demon.co.uk/claws/1_opening.png

When a folder is selected, the messages panel displays a similar effect - http://www.hyborian.demon.co.uk/claws/2_select.png

Selecting an e-mail does not help, although the e-mail contents are displayed clearly - http://www.hyborian.demon.co.uk/claws/3_view_e-mail.png

Minimising and restoring the claws-mail window restores the correct view in both the folders and messages panels - http://www.hyborian.demon.co.uk/claws/4_after_min-restore.png

From that point onwards, selecting additional messages corrupt that particular message's entry in the messages panel until min-restore is performed again.

I have tried changing the font used in Configuration -> Preferences -> Display -> Fonts, but this made no difference.

Additional info:
* package version(s): claws-mail 3.7.3-1
* config and/or log files etc.


Steps to reproduce: See screenshots
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Wednesday, 04 November 2009, 23:51 GMT
Reason for closing:  Works for me
Additional comments about closing:  see comments
Comment by Andreas Radke (AndyRTR) - Wednesday, 04 November 2009, 17:29 GMT
Make sure your whole system is up to date. It's working for me on several x86_64 and i686 systems. Try also to backup your ~/.claws-mail folder and remove it. Maybe something got corrupted there.
Comment by Rob (Painless) - Wednesday, 04 November 2009, 20:34 GMT
Hi Andreas,

Yes the system is fully up to date. I have tried renaming ~/.claws-mail and re-creating a profile from scratch, but I get the same artifacts on the screen.

I do have an idea though. Could this be caused by the KMS driver in kernel 2.6.31? This machine is a laptop with an ATI Radeon Mobility 7500 graphics card. I have disabled KMS (using radeon.modeset=0 on the kernel line in /boot/grub/menu.lst), but I've noticed some unusual screen displays before gnome-screensaver kicks in.
Comment by Rob (Painless) - Wednesday, 04 November 2009, 21:23 GMT
Hi Andreas,

Yes the system is fully up to date. I have tried renaming ~/.claws-mail and re-creating a profile from scratch, but I get the same artifacts on the screen.

I do have an idea though. Could this be caused by the KMS driver in kernel 2.6.31? This machine is a laptop with an ATI Radeon Mobility 7500 graphics card. I have disabled KMS (using radeon.modeset=0 on the kernel line in /boot/grub/menu.lst), but I've noticed some unusual screen displays before gnome-screensaver kicks in.
Comment by Rob (Painless) - Wednesday, 04 November 2009, 21:27 GMT
Sorry about the duplicated comment. :(

I've fixed this, it's not claws-mail, it was a radeon driver configuration problem. I added the following options to xorg.conf:

Option "DRI" "on"
Option "DynamicPM" "on" # Dynamic powersaving.
Option "ClockGating" "on" # Assisting option for powersaving.
Option "AccelMethod" "EXA" # EXA should fit most cases.
Option "EXAVSync" "on" # EXAVSync is explained above.
Option "DMAForXv" "on" # Forced option in order to enable Xv overlay.
Option "ScalerWidth" "2048" # That should fix some very rare bugs.
Option "EnablePageFlip" "on" # It will not be enabled on R5xx cards.
Option "RenderAccel" "on" # Optional. It should be enabled by default.
Option "AccelDFS" "on" #Optional. See the man page.

And one of them fixed it.

Sorry for not checking this more thoroughly earlier. Please close the bug.
Comment by Jan de Groot (JGC) - Wednesday, 04 November 2009, 23:06 GMT
I guess it's AccelMethod EXA that fixes it. I think the ati driver still uses XAA by default, which isn't developed or tested anymore.

Loading...