Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

Xfce4 default for Jessie? systemd + GNOME + delicious drama!

User discussion about Debian Development, Debian Project News and Announcements. Not for support questions.
Message
Author
tomazzi
Posts: 730
Joined: 2013-08-02 21:33

Re: Xfce4 default for Jessie? systemd + GNOME + delicious dr

#161 Post by tomazzi »

vbrummond: I'm sorry, but I didn't get your posts correctly (apparently)...

nimby is known to suggest just switching to alternative distro, but since THAT many of distros are dependant on Debian, it is obviously not a solution....

If we consider switching to systemd as a political decision, then all the results are "magically" become clear - Debian is (or maybe was) the most important system on servers. RedHat is selling mainly servers -> kill the Debian and "we" are fine... - what if they have a special version of systremd? (not broken by using calls to assert?)
Arch and others are not that significant - so they were functioning as a testing ground....

That's only suspiction, not covered by any proofs ;)
Odi profanum vulgus

User avatar
TobiSGD
Posts: 859
Joined: 2010-05-08 22:27
Location: Hannover, Germany

Re: Xfce4 default for Jessie? systemd + GNOME + delicious dr

#162 Post by TobiSGD »

nimby wrote:
TobiSGD wrote:I would guess it depends how you define simple.
Simple = complex "under the hood" code to make it "simple" to the end user / RHEL sysadmin.
Just like tools like vim, grep, awk, sed, ...
Simple = programs which do one thing and do it well,
systemd is collection of programs that do just that
simple configuration files in plain text,
systemd configuration files are plain text
shell scripts which can be examined, modified as necessary
Possibly, but one could argue that systemd's unit files are pretty much that, plain text interpreted by a binary program, like shell scripts are plain text interpreted by a binary program. But I give you one here, if that is your definition of simplicity.
I believe the end goal of systemd is to provide GUI admin tools (a la windows) and getting rid of rc scripts is one of the primary objectives to achieving this end.
Of course replacing rc scripts with systemd's config and unit files is a goal, that is not a secret. But I seriously doubt that Poettering, Red Hat or other distributions using systemd believe that running a GUI on a server is a good idea (for that matter, even Windows Server 2012 can be installed and used without GUI).

But as I said, it is a matter of definitions and it seems that when it comes to simplicity every one has its own definition.

nimby
Posts: 67
Joined: 2014-05-27 10:44

Re: Xfce4 default for Jessie? systemd + GNOME + delicious dr

#163 Post by nimby »

vbrummond wrote:I have already looked at Slackware, Crux, and the BSDs. I have been around the block and back again, I am far beyond needing anyone's advice. If I am complaining about something it means I there is probably no good solution. I probably will have to hack one up myself.
Sorry I had no idea you were so elite and already knew everything... :lol:
tomazzi wrote:nimby is known to suggest just switching to alternative distro, but since THAT many of distros are dependant on Debian, it is obviously not a solution....
None of those I listed is dependent on Debian. I see no problem in changing distro if one does not like what their distro of choice is doing. As an end user it's pretty much all you can do.
TobiSGD wrote:systemd configuration files are plain text
Sort of... but logging is binary as you know.
Last edited by nimby on 2014-07-01 12:58, edited 1 time in total.

vbrummond
Posts: 4432
Joined: 2010-03-02 01:42

Re: Xfce4 default for Jessie? systemd + GNOME + delicious dr

#164 Post by vbrummond »

Yes. I am weary of people telling me to try the grass on the other side (try Arch it feels faster!). I am not elite, but no one is ever able to help me with my questions and I am sick of answering theirs. I am willing to build something right myself rather than wait on everyone else.
Always on Debian Testing

User avatar
TobiSGD
Posts: 859
Joined: 2010-05-08 22:27
Location: Hannover, Germany

Re: Xfce4 default for Jessie? systemd + GNOME + delicious dr

#165 Post by TobiSGD »

nimby wrote:
TobiSGD wrote:systemd configuration files are plain text
Sort of... but logging is binary as you know.
No, not "sort of", they are plain text.
Regarding logging, it was pointed out already that you simply can attach a plain text logger to systemd, so that is a non-issue.

tomazzi
Posts: 730
Joined: 2013-08-02 21:33

Re: Xfce4 default for Jessie? systemd + GNOME + delicious dr

#166 Post by tomazzi »

TobiSGD wrote: Regarding logging, it was pointed out already that you simply can attach a plain text logger to systemd, so that is a non-issue.
Not true, at least not fully true:
Text-mode logging service must be started by systemd before it can catch events -> some events can't be logged as text using f.e. rsyslogd (etc.)
if systemd fails *before* launching the text-mode logging service, then the logs are lost - i.e. available only in binary form - or not available at all, if the reason of failure comes from journald.

I'm considering binary logs as a design fault - there's no way to read them without using *matching* version of journalctl. Binary logs are completely ok for "userland" class of applications, but not for system-critical tasks/services.

Ever heard of JSON? - although it's a shitty XML format, it can be easily made parser-version-independant, so any version of journalctl could read it (or maybe even some external editor/parser)

Regards.
Odi profanum vulgus

User avatar
Ardouos
Posts: 1075
Joined: 2013-11-03 00:30
Location: Elicoor II
Has thanked: 1 time
Been thanked: 4 times

Re: Xfce4 default for Jessie? systemd + GNOME + delicious dr

#167 Post by Ardouos »

On topic with title.

I do not have any bias of what desktop environment as default. As both DE's are good in their own way. But I found this on Reddit which I thought you would find interesting.

http://www.reddit.com/r/debian/comments ... n_jessies/
There is only one Debian | Do not break Debian | Stability and Debian | Backports

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀

User avatar
Gyokuro
Posts: 44
Joined: 2013-03-06 19:33

Re: Xfce4 default for Jessie? systemd + GNOME + delicious dr

#168 Post by Gyokuro »

I have no influence which one get the default one for Jessie but after some time with Gnome3 I will stay with XFCE4 or Mate and my opinion about the default init system is mine - I only know that none of them is perfect (I worked with sysv, smf why not another one ;-) ). Various people make a drama now about systemd and the same people would make the same big drama in case upstart is the default one.

User avatar
harrycaul
Posts: 105
Joined: 2008-12-23 17:06

Re: Xfce4 default for Jessie? systemd + GNOME + delicious dr

#169 Post by harrycaul »

via Distrowatch Weekly-
Thu, 07 Aug 2014
I still don't have a title » A pile of reasons why GNOME should be Debian jessie’s default desktop environment

GNOME has, for some reason or another, always been the default desktop environment in Debian since the installer is able to install a full desktop environment by default. Release after release, Debian has been shipping different versions of GNOME, first based on the venerable 1.2/1.4 series, then moving to the time-based GNOME 2.x series, and finally to the newly designed 3.4 series for the last stable release, Debian 7 ‘wheezy’.

During the final stages of wheezy’s development, it was pointed out that the first install CD image would not longer hold all of the required packages to install a full GNOME desktop environment. There was lots of discussion surrounding this bug or fact, and there were two major reactions to it. The Debian GNOME team rebuilt some key packages so they would be compressed using xz instead of gzip, saving the few megabytes that were needed to squeeze everything in the first CD. In parallel, the tasksel maintainer decided switching to Xfce as default desktop was another obvious fix. This change, unannounced and two days before the freeze, was very contested and spurred the usual massive debian-devel threads. In the end, and after a few default desktop flip flops, it was agreed that GNOME would remain as the default for the already frozen wheezy release, and this issue would be revisited later on during jessie’s development.

And indeed, some months ago, Xfce was again reinstated as Debian’s default desktop for jessie as announced:

Change default desktop to xfce.

This will be re-evaluated before jessie is frozen. The evaluation will
start around the point of DebConf (August 2014). If at that point gnome
looks like a better choice, it’ll go back as the default.

Some criteria for that choice will include:

* Popcon numbers for gnome on jessie. If gnome installations continue to
rise fast enough despite xfce being the default (compared with, say
kde installations), then we’ll know that users prefer gnome.
Currently we have no data about how many users would choose gnome when
it’s not the default. Part of the reason for switching to xfce now
is to get such data.

* The state of accessability support, particularly for the blind.

* How well the UI works for both new and existing users. Gnome 3
seems to be adding back many gnome 2 features that existing users
expect, as well as making some available via addons. If it feels
comfortable to gnome 2 (and xfce) users, that would go a long way
toward switching back to it as the default. Meanwhile, Gnome 3 is also
breaking new ground in its interface; if the interface seems more
welcoming to new users, or works better on mobile devices, etc, that
would again point toward switching back.

* Whatever size constraints exist for CD or other images at the time.

--

Hello to all the tech journalists out there. This is pretty boring.
Why don’t you write a story about monads instead?
― Joey Hess in dfca406eb694e0ac00ea04b12fc912237e01c9b5.

Suffice to say that the Debian GNOME team participants have never been thrilled about how the whole issue is being handled, and we’ve been wondering if we should be doing anything about it, or just move along and enjoy the smaller amount of bug reports against GNOME packages that this change would bring us, if it finally made it through to the final release. During our real life meet-ups in FOSDEM and the systemd+GNOME sprint in Antwerp, most members of the team did feel Debian would not be delivering a graphical environment with the polish we think our users deserve, and decided we at least should try to convince the rest of the Debian project and our users that Debian will be best suited by shipping GNOME 3.12 by default. Power users, of course, can and know how to get around this default and install KDE, Xfce, Cinnamon, MATE or whatever other choice they have. For the average user, though, we think we should be shipping GNOME by default, and tasksel should revert the above commit again. Some of our reasons are:

Accessibility: GNOME continues to be the only free desktop environment that provides full accessibility coverage, right from login screen. While it’s true GNOME 3.0 was lacking in many areas, and GNOME 3.4 (which we shipped in wheezy) was just barely acceptable thanks to some last minute GDM fixes, GNOME 3.12 should have ironed out all of the issues and our non-expert understanding is that a11y support is now on par with what GNOME 2.30 from squeeze offered.
Downstream health: The number of active members in the team taking care of GNOME in Debian is around 5-10 persons, while it is 1-2 in the case of Xfce. Being the default desktop draws a lot of attention (and bug reports) that only a bigger team might have the resources to handle.
Upstream health: While GNOME is still committed to its time-based release schedule and ships new versions every 6 months, Xfce upstream is, unfortunately, struggling a bit more to keep up with new plumbing technology. Only very recently it has regained support to suspend/hibernate via logind, or support for Bluez 5.x, for example.
Community: GNOME is one of the biggest free software projects, and is lucky to have created an ecosystem of developers, documenters, translators and users that interact regularly in a live social community. Users and developers gather in hackfests and big, annual conferences like GUADEC, the Boston Summit, or GNOME.Asia. Only KDE has a comparable community, the rest of the free desktop projects don’t have the userbase or humanpower to sustain communities like this.
Localization: Localization is more extensive and complete in GNOME. Xfce has 18 languages above 95% of coverage, and 2 at 100% (excluding English). GNOME has 28 languages above 95%, 9 of them being complete (excluding English).
Documentation: Documentation coverage is extensive in GNOME, with most of the core applications providing localized, up to date and complete manuals, available in an accessible format via the Help reader.
Integration: The level of integration between components is very high in GNOME. For example, instant messaging, agenda and accessibility components are an integral part of the desktop. GNOME is closely integrated to NetworkManager, PulseAudio, udisks and upower so that the user has access to all the plumbing in a single place. GNOME also integrates easily with online accounts and services (ownCloud, Google, MS Exchange…).
Hardware: GNOME 3.12 will be one of the few desktop environments to support HiDPI displays, now very common on some laptop models. Lack of support for HiDPI means non-technical users will get an unreadable desktop by default, and no hints on how to fix that.
Security: GNOME is more secure. There are no processes launched with root permissions on the user’s session. All everyday operations (package management, disk partitioning and formatting, date/time configuration…) are accomplished through PolicyKit wrappers.
Privacy: One of the latest focuses of GNOME development is improving privacy, and work is being done to make it easy to run GNOME applications in isolated containers, integrate Tor seamlessly in the desktop experience, better disk encryption support and other features that should make GNOME a more secure desktop environment for end users.
Popularity: One of the metrics discussed by the tasksel change proponents mentioned popcon numbers. 8 months after the desktop change, Xfce does not seem to have made a dent on install numbers. The Debian GNOME team doesn’t feel popcon’s data is any better than a random online poll though, as it’s an opt-in service which the vast majority of users don’t enable.
systemd embracing: One of the reasons to switch to Xfce was that it didn’t depend on systemd. But now that systemd is the default, that shouldn’t be a problem. Also given ConsoleKit is deprecated and dead upstream, KDE and Xfce are switching or are planning to switch to systemd/logind.
Adaptation: Debian forced a big desktop change with the wheezy release, switching from the traditional GNOME 2.x to the new GNOME Shell environment. Switching again would mean more adaptation for uses when they’ve had two years to experience GNOME 3.4. Furthermore, GNOME 3.12 means two years of improvements and polishing to GNOME 3.4, which should help with some of the rough edges found in the GNOME release shipped with wheezy.
Administration: GNOME is easy to administrate. All the default settings can be defined by administrators, and mandatory settings can be forced to users, which is required in some companies and administrations; Xfce cannot do that. The close integration with freedesktop components (systemd, NM, PulseAudio…) also gives access to specific and useful administration tools.
In short, we think defaulting to GNOME is the best option for the Debian release, and in contrast, shipping Xfce as the default desktop could mean delivering a desktop experience that has some incomplete or rough edges, and not on par with Debian quality standards for a stable release. We believe tasksel should again revert the change and be uploaded as soon as possible, in order to get people testing images with GNOME the sooner the better, with the freeze only two months away.

We would also like that in the future, changes of this nature will not be announced in a git commit log, but widely discussed in debian-project and the other usual development/decision channels, like the change of init system happened recently. We will, whichever the final decision is, continue to package GNOME with great care to ensure our users get the best possible desktop experience Debian can offer.

User avatar
Ardouos
Posts: 1075
Joined: 2013-11-03 00:30
Location: Elicoor II
Has thanked: 1 time
Been thanked: 4 times

Re: Xfce4 default for Jessie? systemd + GNOME + delicious dr

#170 Post by Ardouos »

Not 100% on this, but now I think the default DE for Jessie will be Gnome again:

http://www.webupd8.org/2014/09/debian-s ... -xfce.html
There is only one Debian | Do not break Debian | Stability and Debian | Backports

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀

User avatar
harrycaul
Posts: 105
Joined: 2008-12-23 17:06

Re: Xfce4 default for Jessie? systemd + GNOME + delicious dr

#171 Post by harrycaul »

https://lists.debian.org/debian-devel-a ... 00002.html
* Gnome is now the default desktop environment on Linux again.

Post Reply