SoylentNews is people
SoylentNews
Debian Jesse is going to have Gnome3 as the default desktop.
The desktop re-qualification page, used to help choose which desktop will be default, has in the Jesse version a weight for systemd integration, and of course only Gnome3 does it (at least for now). This will surely make the systemd/gnome3 fanbase happy, but possibly will make others unhappy, as it [may] be seen as another step towards mono-culture, until we soon end up with all distros being redhat clones.
This discussion has been archived.
No new comments can be posted.
Integration with systemd Making Gnome3 the Default Debian Desktop
|
Log In/Create an Account
| Top
| 135 comments
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
You are the only person to ever get this message.
(Score: 0) by Anonymous Coward on Wednesday September 24 2014, @03:24PM
Incorrect. Systemd is needed even for Gimp in debian Jessie.
It's either systemd or get the fuck out.
(Score: 2) by CRCulver on Wednesday September 24 2014, @06:22PM
(Score: 0) by Anonymous Coward on Wednesday September 24 2014, @11:17PM
As far as I'm concerned, systemd-shim is just as bad as systemd. They both should be totally unnecessary.
(Score: 1) by coolgopher on Thursday September 25 2014, @02:13AM
As of a couple of weeks ago, it's not. At least if you're using something which depends on PolicyKit. The only solution for me was to hold PolicyKit back to a pre-systemd version, and reconfigure it to give all users full access. I hadn't known what PolicyKit was before this, and now that I know I'd really rather not have it installed, but I do use the udisks2 package for convenient mounting of removable disks (via wmvolman), so for now I'm stuck with it. At the rate Debian is going, my next upgrade will be to Slack or Gentoo I suppose.
(Score: 2) by CRCulver on Thursday September 25 2014, @02:51AM
You are doing something wrong. Running GIMP even with current Debian unstable does not require running systemd as your init system.
Perhaps you are confusing the fact that some systemd packages will have to be installed in order to use GNOME apps, but that doesn't oblige the user to run systemd as his/her init system. With the systemd-shim package, you can continue to run sysvinit as your init, and at the same time install a bare minimum of systemd dependencies to run such desktop applications.
(Score: 0) by Anonymous Coward on Thursday September 25 2014, @05:19AM
Yes it does, this has even been discussed on the mailing list in the last day or so.
And it is all by design.
(Score: 1) by coolgopher on Thursday September 25 2014, @08:07AM
I'm doing something wrong? Well, you know what, perhaps you're right.
But that doesn't really excuse the mess - rather it reinforces the fact that it is a mess. Never before in my experience has the choice of init system had such a nasty impact on, well, everything else. If systemd truly was a choice in Debian at this point, I wouldn't be bitching about having to hold packages and mess with configuration settings I've never had to muck around with before. Sure, I'm running Jessie, so I shouldn't expect everything to be smooth sailing, but at the end of the day I'm coming away with the feeling that Debian is no longer a good choice of distro for me, as a user and developer.
(Score: 0) by Anonymous Coward on Wednesday September 24 2014, @06:58PM
Citation, please.
(Score: 1) by quixote on Wednesday September 24 2014, @08:44PM
Sheesh, man. You're the one posting as AC and you want a citation?
Tell you what. Start Synaptic (leftmost upper or lower corner main menu button > System > Synaptic), enter password at the prompt, type systemd-shim in the search box, install, close Synaptic, reboot, aaand see what happens. (Precise instructions in case you're really as clueless as you sound.)