Comment 3 for bug 128383
Revision history for this message
| Andrew Starr-Bochicchio (andrewsomething) wrote | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
One thought that I had was that maybe one of the first lines in AWN could attempt to detect a running compositor and if the test fails display a dialog saying that AWN doesn't run without a compositor. The main issue I can see with that would be that on log in often AWN starts before Compiz. I know that can be fixed but the whole point seems to make AWN easier for the normal user so do we really want them messing that much with their sessions?
To answer the question "For users who permanently can't use it, I guess I see where this might be annoying, but then why are they running it?"
It seems to be a good idea to inform them why they can't run it as opposed to making them think AWN is just messed up.