<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-text-flowed" style="font-family: -moz-fixed;
font-size: 12px;" lang="x-western">Le 27/01/2012 03:16, Andrew
Starr-Bochicchio a écrit :
<br>
<blockquote type="cite" style="color: #000000;">On Thu, Jan 26,
2012 at 8:04 PM, Marc Deslauriers
<br>
<a class="moz-txt-link-rfc2396E"
href="mailto:marc.deslauriers@canonical.com"><marc.deslauriers@canonical.com></a>
wrote:
<br>
<blockquote type="cite" style="color: #000000;">
<blockquote type="cite" style="color: #000000;">Of course, the
correct way to solve this issue is far more complicated
<br>
than just removing a package from the archive, it require
solving
<br>
bugs, bringing new code in Unity while avoiding unwanted
side effects
<br>
on compiz and basically requires more manpower.
<br>
</blockquote>
If someone would step up and fix CCSM so a novice user can't
mess up
<br>
their desktop with two mouse clicks, we wouldn't be having
this
<br>
discussion.
<br>
</blockquote>
Just what would that look like? As someone who hasn't run into
these
<br>
issues, it's hard to tell from this thread what would be enough
for
<br>
people to consider CCSM "fixed." A lot of the opposition to CCSM
seems
<br>
to be based on the nature of the tool itself rather than any
specific
<br>
bugs (though judging from Launchpad it certainly has its share
of
<br>
those). Are there specific plugins or options that are
considered
<br>
harmful or especially problematic? Are these found in the core
plugins
<br>
that are installed by default? Perhaps they should be broken out
into
<br>
one of the universe plugin-extras packages? Or are they in one
of the
<br>
universe packages already? Maybe we could better split the
plugin
<br>
packages?
<br>
</blockquote>
<br>
They are already split sincce Oneiric. For plugins that are
"officially suppported" upstream, we only install those that are
used with the unity session right now (25 plugins exactly). Those
are installed by compiz-plugins-default and
compiz-plugins-main-default, the others are in compiz-plugins and
compiz-plugins-main which are not installed by default (but are
still there if you upgraded your machine from a version
pre-oneiric).
<br>
<br>
<blockquote type="cite" style="color: #000000;">
<blockquote type="cite" style="color: #000000;">- Since it's
settings are separate from Unity a "unity --reset"
<br>
doesn't fix it, you have to blow away .compiz or some other
dotfile
<br>
directories to get a desktop back.
<br>
</blockquote>
Is this true? I just tested this by exporting my compiz settings
using
<br>
CCSM and running a "unity --reset" All my custom settings seem
to have
<br>
been cleared. Using CCSM, I was then easily able to re-import my
<br>
backed up settings and restore them all. The unity python
wrapper
<br>
seems to try and wipe all your compiz settings if --reset is
used. It
<br>
calls:
<br>
<br>
subprocess.Popen(["gconftool-2", "--recursive-unset",
"/apps/compiz-1"])
<br>
<br>
Is there a bug in unity's --reset option where this doesn't work
in
<br>
some cases? Should the option to reset all options to their
default
<br>
be made more prominent in CCSM?
<br>
</blockquote>
<br>
No, Jorge wasn't quite right on this one, unity --reset indeed
reset the whole compiz settings, not just the unity one <span
class="moz-smiley-s1" title=":)"></span>
<br>
<br>
<br>
<blockquote type="cite" style="color: #000000;">
<br>
<blockquote type="cite" style="color: #000000;">- I'm sure at
UDS you've seen didrocks show you one of the ways it
<br>
breaks even when using parts of it that shouldn't break.
<br>
</blockquote>
I'll take his word on this.
<br>
<br>
<br>
I'd love to hear some more specific issues.
<br>
</blockquote>
<br>
I've added some on my other post in this thread.
<br>
<br>
Cheers,
<br>
Didier
<br>
<br>
</div>
</body>
</html>