Making Studio work with more than one DE

lukefromdc at lukefromdc at
Wed May 22 20:07:31 UTC 2013

Concerning multiple DE's: What about Cinnamon? Of all DE's I've tried,
it is the one that can be configured to look and feel the most like the
Ubuntustudio  desktop I knew and loved in 2008. When using the 
"GNOME" theme in Cinnamon with the UbuntuStudio-legacy icons
and GTK 3/2 theme I privately maintain, it is absolutely spectacular.

Cinnamon is a bit heavy, as it is based on gnome-shell, but seems to 
be a bit lighter than gnome-shell. MATE is much lighter, enough so to allow
a 2GHZ Pentium 4 to just play 720p video, but as it is based on Gnome 2
there are questions about its long-term mantainability. Cinnamon is based 
on current code and available from a PPA in Ubuntu. I would not be at all
surprised to see it offered in Universe at some point.

Cinnamon's sound applet normally works with Pulseaudio, doesn't work if
Pulse is not running. Volti, however, appears in Cinnamon's tray and works

This is a legacy, not a current version of the Ubuntustudio theme, icons, etc
that I use, but be aware that they all exist and all work together for me, I've just
never played with packaging things as debian packages yet.

On 05/22/2013 at 3:39 PM, "Kaj Ailomaa" <zequence at> wrote:
>On Wed, May 22, 2013, at 08:09 PM, Eric Hedekar wrote:
>> This really was one of the most dramatic train/thread 
>derailments I've
>> seen
>> in a while.  Impressive.
>> As far as other desktop environments are concerned, part of me 
>is in
>> favour
>> of this mindset being adopted (as I've never left gnome despite 
>Same here. But I did find going with XFCE as the default desktop 
>was the
>best choice at that time nevertheless, because of the uncertainty 
>other DEs.
>Also, the custom menu is not a bad addition, even if I'd rather 
>try push
>new categorizations upstream, and do as little customization at the
>Ubuntu Studio end, as possible.
>> Studio's switch to xfce - I just don't like that DE).  If a 
>modular front
>> end was adopted then it would encourage wider usage and a better 
>> design.  However, what Hartmut may have been trying to state was 
>> this
>> is development is probably not the best use of developer's time. 
> There
>> have almost always been stability issues, bugs, and lack of 
>> in Ubuntu Studio that the user sees as more drastic to their 
>> than
>Yes. But, the way I see it, the people who want to fix those 
>things are
>already working on that. And it would not help the situation 
>anyway by
>not allowing people who can't help fix those issues to not be 
>allowed to
>do what they want to do. So, there's really no conflict there.
>Is anyone against the idea of multiple DE support for Ubuntu 
>Studio? If
>yes, then please explain why? Otherwise, I think it's just good 
>that we
>have work going on in as many fields as possible.
>Right now, we are mainly experimenting with adding new DEs to the 
>Something I'm sure a lot of users will appreciate. Also, while 
>that, we get insight in problems we weren't aware of before.
>I don't see any conflict in planning here. I'd rather see more 
>helping out, but I suppose that will always be the situation for 
>volunteer project :).
>> annoying quirks from the given DE.  So yeah, apply force to the 
>> problems, but it would be a prudent philosophy to reduce the 
>amount of
>> xfce-specific code that ships with the distro.  We don't know 
>how long
>> into
>> the future the xfce platform will best suit our needs (very 
>> warning
>> was given during the gnome/unity move that prompted our switch 
>to xfce in
>> the first place), and the lack of DE-specific code the easier it 
>will be
>> for those of us who love a different DE to just switch.
>We don't actually have that much custom work on the DE right now, 
>as it
>is mostly based on Xubuntu (len is working on that mostly). The 
>menu is
>probably the biggest part of that, and it would be nice to have a
>generic solution to that which would work on all DEs, and the 
>in that are becoming clear now that we are trying out different 
>So, the effort in changing DE, or adding more of them is not that 
>The more people learn how you develop them, the easier it becomes 
>on the
>whole team as well. Right now, we have 4 different people working 
>on the
>different aspects of these DEs, not counting our art lead, who 
>will also
>be involved in making them look nice. Out of those four, only one 
>even patching Ubuntu code. So, there you have it. 
>Most of the problems in jack and PA integration are in coding, so 
>is actually mostly up to the coders to fix, and currently, no one 
>in the
>Ubuntu Studio team is working on developing either pulseaudio or 
>But, of course, we have a special position in that we can 
>communicate to
>the coders and help make clear different issues. We can establish 
>a good
>overview of the problems, etc. Doesn't require any coding skills. 
>requires for someone to put some time into it, and it could be 
>A good first step is always a bug report, as mentioned. Then, 
>has to put time on finding ways to solve the problem.
>> -Eric Hedekar
>> *
>> Eric Hedekar
>> *
>Ubuntu-Studio-devel mailing list
>Ubuntu-Studio-devel at
>Modify settings or unsubscribe at: 

More information about the Ubuntu-Studio-devel mailing list