Text becomes grainy/pixelated after compiz crashes

Bug #1112992 reported by Daniel Cooper
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Text becomes grainy/less-defined when compiz comes back after crashing. It's quite minor but is rather annoying and clearly shouldn't be doing it. Not sure what causes it other than the earlier signs of compiz crashing and the same thing happening.

I first found that compiz would crash when using a display indicator (disper-indicator) when switching to a single desktop mode too early after logging in. It then might do it randomly and now it just does it as soon as I log in.

Screenshot attached.

Please help me provide more description and/or terminal outputs.

Revision history for this message
Daniel Cooper (d4nc00per) wrote :
Revision history for this message
Sam Spilsbury (smspillaz) wrote :

Does this only happen in certain applications?

Revision history for this message
Daniel Cooper (d4nc00per) wrote :

It seems to be on all applications and anywhere with text, it's hard to tell without having a comparison. Nautilus looks fairly normal, but it may be something to do with the way that font is rendered compared to others?

summary: - Text is fuzzy/out of focus
+ Text becomes grainy/pixelated after compiz crashes
description: updated
Revision history for this message
penalvch (penalvch) wrote :

Daniel Cooper, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y upgrade && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line:
gksudo gedit /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and try to file the crash report again via:
ubuntu-bug /var/crash/_my_crash_report.crash

Please follow https://wiki.ubuntu.com/DebuggingCompiz when you file this crash report so the necessary information is provided.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Changed in compiz (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.