From: Antonio Malcolm <antonio...@gmail.com>
To: voidlinux@googlegroups.com
Subject: Re: Decent Starting Point For Rolling A Desktop Environment?
Date: Mon, 2 Feb 2015 13:35:25 -0800 (PST) [thread overview]
Message-ID: <92b13c50-f3ce-4aec-99b8-553fffb3cffe@googlegroups.com> (raw)
In-Reply-To: <9386866b-d729-4587-bd55-ab639a2da6ed@googlegroups.com>
[-- Attachment #1.1: Type: text/plain, Size: 1348 bytes --]
Well, ok, an update: Cinnamon breaks BADLY with the most recent Nvidia
drivers. Add to that, it does irritating things, with either overriding
some Xorg settings, and (at least the HOW of) its use of Xorg settings in
its own settings (I had lots of fun getting my trackpad to work
predictably). Solutions, from around the web, for solving the Cinnamon +
Nvidia debacle, range from such magic, as install bumblebee, and *MAGIC*,
cinnamon will suddenly work, to reinstalling Nvidia drivers, from the
Nvidia website and *MAGIC*, Cinnamon will suddenly work, to reinstalling
your entire Linux setup and *MAGIC*, everything will just work. Yeah, no
thanks.
Anyhow, I've ended up happily chugging along with a
lightdm+openbox+compton+thunar stack. Quite happily.
Add tint2 and kupfer to the equation, and it's a golden setup, which
behaves just as expected- as configured.
When you're going to set things via config files, anyhow, you may as well
go all the way, and go with the solution which operates almost solely
according to those configs, without adding so much cruft atop them.
Lessons learned!
The only two bits of cruft, in my current setup are obconf and
lxappearance, as they do make setting the general "look and feel" stuffs
easier. And lightdm appears to work easily with whatever you put behind it.
[-- Attachment #1.2: Type: text/html, Size: 1358 bytes --]
next prev parent reply other threads:[~2015-02-02 21:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 14:58 Antonio Malcolm
2015-01-22 15:07 ` Christian Neukirchen
2015-01-22 15:09 ` Enno Boland
2015-01-22 18:35 ` Antonio Malcolm
2015-01-22 21:02 ` Logen Kain
2015-01-23 3:04 ` Antonio Malcolm
2015-01-23 3:19 ` Logen Kain
2015-01-23 16:08 ` Antonio Malcolm
2015-01-24 8:27 ` Antonio Malcolm
2015-01-27 1:43 ` Logen Kain
2015-01-27 1:52 ` Logen Kain
2015-01-27 1:57 ` Logen Kain
2015-01-27 8:55 ` Juan RP
2015-01-29 0:55 ` Antonio Malcolm
2015-02-02 21:35 ` Antonio Malcolm [this message]
2015-02-03 9:46 ` Logen Kain
2015-02-03 9:58 ` Stefan Mühlinghaus
2015-02-04 0:38 ` Antonio Malcolm
2015-02-05 10:39 ` Logen Kain
2015-02-09 18:56 ` Antonio Malcolm
2015-02-11 9:06 ` Logen Kain
2015-02-11 20:36 ` Antonio Malcolm
2015-02-04 7:47 ` Stefan Mühlinghaus
2015-02-04 18:34 ` Antonio Malcolm
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=92b13c50-f3ce-4aec-99b8-553fffb3cffe@googlegroups.com \
--to="antonio..."@gmail.com \
--cc=voidlinux@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).