Activity log for bug #265126

Date Who What changed Old value New value Message
2008-09-05 17:48:09 Steve Beattie bug added bug
2008-09-05 17:48:09 Steve Beattie bug added attachment 'xubuntu-font-problems.png' (screenshot 1)
2008-09-05 17:48:48 Steve Beattie bug added attachment 'xubuntu-font-problems2.png' (screenshot 2)
2008-09-05 17:49:43 Steve Beattie bug added attachment 'xubuntu-font-problems3.png' (screenshot 3 - monster terminal)
2008-09-05 17:50:45 Steve Beattie bug added attachment 'xubuntu-font-problems-fixed-with-dpi-set-to-96.png' (screenshot 4: after setting DPI explicitly to 96 DPI and restarting session, things look normal)
2008-09-05 22:07:19 Michael Casadevall xubuntu-meta: status New Confirmed
2008-09-05 22:07:19 Michael Casadevall xubuntu-meta: importance Undecided High
2008-09-05 22:07:19 Michael Casadevall xubuntu-meta: statusexplanation Confirming this one on the LiveCD. I can't currently install Xubuntu onto a machine; does this issue persist after installation?
2008-09-30 20:10:22 Michael Casadevall xubuntu-meta: assignee sonicmctails
2008-09-30 20:10:22 Michael Casadevall xubuntu-meta: statusexplanation Confirming this one on the LiveCD. I can't currently install Xubuntu onto a machine; does this issue persist after installation? It took me awhile to understand why this is an issue, but I realized why it was a problem specifically. I'm working now to fix this. Can you please give step-by-step directions to reset the DPI to fix the fonts? (I'm not sure if your changing the Xfce DPI or the Xorg one).
2008-09-30 20:10:22 Michael Casadevall xubuntu-meta: milestone ubuntu-8.10
2009-03-04 20:00:19 Steve Beattie xubuntu-meta: status Confirmed Fix Released
2009-03-04 20:00:19 Steve Beattie xubuntu-meta: statusexplanation It took me awhile to understand why this is an issue, but I realized why it was a problem specifically. I'm working now to fix this. Can you please give step-by-step directions to reset the DPI to fix the fonts? (I'm not sure if your changing the Xfce DPI or the Xorg one). Yep, I just verified that this has been fixed. Thanks, closing.