[opensuse-factory] Re: [opensuse-project] Maintainers wanted for Dracut and Plymouth
On Sunday 02 February 2014 12:24:29 sfalken@opensuse.org wrote:
I could take one of them over, Raymond. Don't have any particular knowledge about either package, but I've got the time.
Hi Shawn, Great. Thanks a lot. As discussed on IRC, I will transfer today the "ownership" of DRACUT to you on OBS and bugzilla. Only package remaining is Plymouth and I guess that people rather see it disappear than to help out. Regards Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le mardi 04 février 2014 à 06:14 +0100, Raymond Wooninck a écrit :
On Sunday 02 February 2014 12:24:29 sfalken@opensuse.org wrote:
I could take one of them over, Raymond. Don't have any particular knowledge about either package, but I've got the time.
Hi Shawn,
Great. Thanks a lot. As discussed on IRC, I will transfer today the "ownership" of DRACUT to you on OBS and bugzilla.
Only package remaining is Plymouth and I guess that people rather see it disappear than to help out.
No, I don't want to see it disappear at all (since it has replaced all
other boot splash alternative, for the good) but I don't have time to
maintain it.
--
Frederic Crozat
Frederic Crozat wrote:
Le mardi 04 février 2014 à 06:14 +0100, Raymond Wooninck a écrit :
On Sunday 02 February 2014 12:24:29 sfalken@opensuse.org wrote:
I could take one of them over, Raymond. Don't have any particular knowledge about either package, but I've got the time.
Hi Shawn,
Great. Thanks a lot. As discussed on IRC, I will transfer today the "ownership" of DRACUT to you on OBS and bugzilla.
Only package remaining is Plymouth and I guess that people rather see it disappear than to help out.
No, I don't want to see it disappear at all (since it has replaced all other boot splash alternative, for the good) but I don't have time to maintain it.
How long does the average system nowadays take until X starts up? If there is a black screen for a few seconds, so what? That's the time the initrd takes to load if plymouth is in there anyways ;-) cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 04.02.2014 10:41, schrieb Ludwig Nussel:
Frederic Crozat wrote:
Le mardi 04 février 2014 à 06:14 +0100, Raymond Wooninck a écrit :
On Sunday 02 February 2014 12:24:29 sfalken@opensuse.org wrote:
I could take one of them over, Raymond. Don't have any particular knowledge about either package, but I've got the time.
Hi Shawn,
Great. Thanks a lot. As discussed on IRC, I will transfer today the "ownership" of DRACUT to you on OBS and bugzilla.
Only package remaining is Plymouth and I guess that people rather see it disappear than to help out.
No, I don't want to see it disappear at all (since it has replaced all other boot splash alternative, for the good) but I don't have time to maintain it.
How long does the average system nowadays take until X starts up? If there is a black screen for a few seconds, so what? That's the time the initrd takes to load if plymouth is in there anyways ;-)
since 13.1 it takes around 2 minutes until my X comes up on my desktop machine and nobody can (or want to) help/tell me why. But I agree it was not long for 12.3. Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le mardi 04 février 2014 à 10:41 +0100, Ludwig Nussel a écrit :
Frederic Crozat wrote:
Le mardi 04 février 2014 à 06:14 +0100, Raymond Wooninck a écrit :
On Sunday 02 February 2014 12:24:29 sfalken@opensuse.org wrote:
I could take one of them over, Raymond. Don't have any particular knowledge about either package, but I've got the time.
Hi Shawn,
Great. Thanks a lot. As discussed on IRC, I will transfer today the "ownership" of DRACUT to you on OBS and bugzilla.
Only package remaining is Plymouth and I guess that people rather see it disappear than to help out.
No, I don't want to see it disappear at all (since it has replaced all other boot splash alternative, for the good) but I don't have time to maintain it.
How long does the average system nowadays take until X starts up? If there is a black screen for a few seconds, so what? That's the time the initrd takes to load if plymouth is in there anyways ;-)
Plymouth also allows smooth transition (no flicker) between splash and
display manager. And it can display a non frightening UI to request
passphrase for encrypted disk.
--
Frederic Crozat
On 4 February 2014 10:47, Wolfgang Rosenauer
Am 04.02.2014 10:41, schrieb Ludwig Nussel:
How long does the average system nowadays take until X starts up? If there is a black screen for a few seconds, so what? That's the time the initrd takes to load if plymouth is in there anyways ;-)
since 13.1 it takes around 2 minutes until my X comes up on my desktop machine and nobody can (or want to) help/tell me why. But I agree it was not long for 12.3.
Wolfgang
I'm rather torn on this topic myself - as one of the maintainers of our branding packages I want the distribution to look slick and a nice boot process is part of that experience. On the flipside, I own a machine that boots so fast, every time I change the branding package for Plymouth, I need to build a second version with enforced delays to purposefully slow the boot process down in order to test whether or not the changes I've made are working, because normally plymouth is finished and X is launching before my LCD has changed it's resolution from Grub2 to Plymouth.. so in my case, Plymouth is actually adding needless seconds to my boot process and causing more flickers than if it wasn't there But as wolfgangs reply shows, my situation is not universal. If someone steps up and maintains it, great Wolfgang - have you installed systemd-analyze and run "systemd-analyze blame" and "systemd-analyze plot > output.svg" to get a picture of what is taking so long on your boot? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi, Am 04.02.2014 10:53, schrieb Richard Brown:
But as wolfgangs reply shows, my situation is not universal.
It's a fast machine still but it has no SSD for example.
If someone steps up and maintains it, great
Wolfgang - have you installed systemd-analyze and run "systemd-analyze blame" and "systemd-analyze plot > output.svg" to get a picture of what is taking so long on your boot?
Since it's slightly offtopic here, this is the reference to another thread about it: http://lists.opensuse.org/opensuse/2013-12/msg00865.html 34.449s systemd-udev-settle.service Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Tue, 04 Feb 2014 10:52:15 +0100 schrieb Frederic Crozat:
Le mardi 04 février 2014 à 10:41 +0100, Ludwig Nussel a écrit :
Frederic Crozat wrote:
Le mardi 04 février 2014 à 06:14 +0100, Raymond Wooninck a écrit :
On Sunday 02 February 2014 12:24:29 sfalken@opensuse.org wrote:
I could take one of them over, Raymond. Don't have any particular knowledge about either package, but I've got the time.
Hi Shawn,
Great. Thanks a lot. As discussed on IRC, I will transfer today the "ownership" of DRACUT to you on OBS and bugzilla.
Only package remaining is Plymouth and I guess that people rather see it disappear than to help out.
No, I don't want to see it disappear at all (since it has replaced all other boot splash alternative, for the good) but I don't have time to maintain it.
How long does the average system nowadays take until X starts up? If there is a black screen for a few seconds, so what? That's the time the initrd takes to load if plymouth is in there anyways ;-)
Plymouth also allows smooth transition (no flicker) between splash and display manager. And it can display a non frightening UI to request passphrase for encrypted disk.
displaying the non frightening (G)UI to request the passphrase seems (often) not to work in 13.1: https://bugzilla.novell.com/show_bug.cgi?id=851960 Regards, Dieter -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2014-02-04 10:52, Frederic Crozat wrote:
Plymouth also allows smooth transition (no flicker) between splash and display manager. And it can display a non frightening UI to request passphrase for encrypted disk.
Others intentionally remove plymouth because we want a boot process with all the beautiful text messages flowing by :-) In some cases, removing plymouth solves problems. For instance, it doubles the size of initrd, meaning that some people with a separate /boot partition had it overflowed; yes, even on fresh installs, because YaST was not adapted to suggest a bigger boot (bigger initrd, and up to 3 kernels by default during updates). Some new installs got a "/boot" of only 80 megs (yes, there are bugzillas about this. Not mine, I don't know the numbers). Some people had problems with plymouth interfering with X startup. I don't remember the details. I suppose there are bugzillas. Yes, I understand that many people like a nice graphical boot process. No objection to that, as long as others can easily disable it. - -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlLwvRoACgkQtTMYHG2NR9U2DQCePB56fP/IcJ6MkE8MYl/TZy+p wiYAn22pEhoFtl8fR7XVD7jxIKmIoIvQ =1OiW -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Frederic Crozat wrote:
Le mardi 04 février 2014 à 10:41 +0100, Ludwig Nussel a écrit :
Frederic Crozat wrote:
Le mardi 04 février 2014 à 06:14 +0100, Raymond Wooninck a écrit :
On Sunday 02 February 2014 12:24:29 sfalken@opensuse.org wrote:
I could take one of them over, Raymond. Don't have any particular knowledge about either package, but I've got the time.
Hi Shawn,
Great. Thanks a lot. As discussed on IRC, I will transfer today the "ownership" of DRACUT to you on OBS and bugzilla.
Only package remaining is Plymouth and I guess that people rather see it disappear than to help out.
No, I don't want to see it disappear at all (since it has replaced all other boot splash alternative, for the good) but I don't have time to maintain it.
How long does the average system nowadays take until X starts up? If there is a black screen for a few seconds, so what? That's the time the initrd takes to load if plymouth is in there anyways ;-)
Plymouth also allows smooth transition (no flicker) between splash and display manager.
Ok, that sentence compares plymouth to other splash solutions but it makes no statement about the situation compared to a boot with no splash at all. Isn't it simply bootloader -> resolution switch -> black screen -> X rather than bootloader -> resolution switch -> fancy screen -> X
And it can display a non frightening UI to request passphrase for encrypted disk.
It could but it doesn't in 13.1 because it's broken. So plymouth gets disabled if root is encrypted and the initrd prompts in text mode. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Frederic Crozat
Le mardi 04 février 2014 à 10:41 +0100, Ludwig Nussel a écrit :
Frederic Crozat wrote:
Le mardi 04 février 2014 à 06:14 +0100, Raymond Wooninck a écrit :
On Sunday 02 February 2014 12:24:29 sfalken@opensuse.org wrote:
I could take one of them over, Raymond. Don't have any particular knowledge about either package, but I've got the time.
Hi Shawn,
Great. Thanks a lot. As discussed on IRC, I will transfer today the "ownership" of DRACUT to you on OBS and bugzilla.
Only package remaining is Plymouth and I guess that people rather see it disappear than to help out.
No, I don't want to see it disappear at all (since it has replaced all other boot splash alternative, for the good) but I don't have time to maintain it.
How long does the average system nowadays take until X starts up? If there is a black screen for a few seconds, so what? That's the time the initrd takes to load if plymouth is in there anyways ;-)
Plymouth also allows smooth transition (no flicker) between splash and display manager. And it can display a non frightening UI to request passphrase for encrypted disk.
Since 13.1 there is none, you get a plain text prompt. Also if you use suspen/hibernate (as I do) you also never get to see a splash screen either. Since this is the status quo, plymouth is probably not as important as some may think... -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le mardi 04 février 2014 à 11:13 +0100, Ludwig Nussel a écrit :
Frederic Crozat wrote:
Le mardi 04 février 2014 à 10:41 +0100, Ludwig Nussel a écrit :
Frederic Crozat wrote:
Le mardi 04 février 2014 à 06:14 +0100, Raymond Wooninck a écrit :
On Sunday 02 February 2014 12:24:29 sfalken@opensuse.org wrote:
I could take one of them over, Raymond. Don't have any particular knowledge about either package, but I've got the time.
Hi Shawn,
Great. Thanks a lot. As discussed on IRC, I will transfer today the "ownership" of DRACUT to you on OBS and bugzilla.
Only package remaining is Plymouth and I guess that people rather see it disappear than to help out.
No, I don't want to see it disappear at all (since it has replaced all other boot splash alternative, for the good) but I don't have time to maintain it.
How long does the average system nowadays take until X starts up? If there is a black screen for a few seconds, so what? That's the time the initrd takes to load if plymouth is in there anyways ;-)
Plymouth also allows smooth transition (no flicker) between splash and display manager.
Ok, that sentence compares plymouth to other splash solutions but it makes no statement about the situation compared to a boot with no splash at all.
Isn't it simply bootloader -> resolution switch -> black screen -> X rather than bootloader -> resolution switch -> fancy screen -> X
Not everybody is lucky to have an SSD and a system booting in 5s.
And it can display a non frightening UI to request passphrase for encrypted disk.
It could but it doesn't in 13.1 because it's broken. So plymouth gets disabled if root is encrypted and the initrd prompts in text mode.
Strange, I'm still getting a passphrase prompt in plymouth on 13.1 on my
system ;)
--
Frederic Crozat
Le mardi 04 février 2014 à 11:12 +0100, Carlos E. R. a écrit :
On 2014-02-04 10:52, Frederic Crozat wrote:
Plymouth also allows smooth transition (no flicker) between splash and display manager. And it can display a non frightening UI to request passphrase for encrypted disk.
Others intentionally remove plymouth because we want a boot process with all the beautiful text messages flowing by :-)
In some cases, removing plymouth solves problems. For instance, it doubles the size of initrd, meaning that some people with a separate /boot partition had it overflowed; yes, even on fresh installs, because YaST was not adapted to suggest a bigger boot (bigger initrd, and up to 3 kernels by default during updates). Some new installs got a "/boot" of only 80 megs (yes, there are bugzillas about this. Not mine, I don't know the numbers).
Some people had problems with plymouth interfering with X startup. I don't remember the details. I suppose there are bugzillas.
Yes, I understand that many people like a nice graphical boot process. No objection to that, as long as others can easily disable it.
Why are you stating it it mandatory, since it isn't and nobody is
speaking about make it mandatory ?
--
Frederic Crozat
Le mardi 04 février 2014 à 11:12 +0100, dieter a écrit :
Am Tue, 04 Feb 2014 10:52:15 +0100 schrieb Frederic Crozat:
Le mardi 04 février 2014 à 10:41 +0100, Ludwig Nussel a écrit :
Frederic Crozat wrote:
Le mardi 04 février 2014 à 06:14 +0100, Raymond Wooninck a écrit :
On Sunday 02 February 2014 12:24:29 sfalken@opensuse.org wrote:
I could take one of them over, Raymond. Don't have any particular knowledge about either package, but I've got the time.
Hi Shawn,
Great. Thanks a lot. As discussed on IRC, I will transfer today the "ownership" of DRACUT to you on OBS and bugzilla.
Only package remaining is Plymouth and I guess that people rather see it disappear than to help out.
No, I don't want to see it disappear at all (since it has replaced all other boot splash alternative, for the good) but I don't have time to maintain it.
How long does the average system nowadays take until X starts up? If there is a black screen for a few seconds, so what? That's the time the initrd takes to load if plymouth is in there anyways ;-)
Plymouth also allows smooth transition (no flicker) between splash and display manager. And it can display a non frightening UI to request passphrase for encrypted disk.
displaying the non frightening (G)UI to request the passphrase seems (often) not to work in 13.1: https://bugzilla.novell.com/show_bug.cgi?id=851960
Which is exactly why we need somebody to actively maintain plymouth..
--
Frederic Crozat
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2014-02-04 11:17, Frederic Crozat wrote:
Le mardi 04 février 2014 à 11:12 +0100, Carlos E. R. a écrit :
Why are you stating it it mandatory, since it isn't and nobody is speaking about make it mandatory ?
Huh? I have not said it is mandatory. Did I? :-? It is installed by default, yes. And some people had to remove it later to get their system work, yes. I stand by that. You just need to have a perusal of what problems users report on the forums to get an idea of what normal users find and do. - -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlLwwiIACgkQtTMYHG2NR9VdkwCfbvw9NQTO4+Ps93SFBN05tsON ydEAn1LCGMVp43wSveXsh7NomFrbe1cl =u3wk -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Frederic Crozat wrote:
Le mardi 04 février 2014 à 11:13 +0100, Ludwig Nussel a écrit :
Ok, that sentence compares plymouth to other splash solutions but it makes no statement about the situation compared to a boot with no splash at all.
Isn't it simply bootloader -> resolution switch -> black screen -> X rather than bootloader -> resolution switch -> fancy screen -> X
Not everybody is lucky to have an SSD and a system booting in 5s.
Are you saying systemd didn't make your system boot fast? ;-P Seriously, what big offenders in the boot time of a desktop installation are left? How many seconds are the pain threshold of staring at a black screen?
And it can display a non frightening UI to request passphrase for encrypted disk.
It could but it doesn't in 13.1 because it's broken. So plymouth gets disabled if root is encrypted and the initrd prompts in text mode.
Strange, I'm still getting a passphrase prompt in plymouth on 13.1 on my system ;)
Plymouth is only disabled if the passphrase is prompted in initrd. Normal system boot still uses plymouth as the race condition doesn't seem to appear so often there. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le mardi 04 février 2014 à 11:34 +0100, Carlos E. R. a écrit :
On 2014-02-04 11:17, Frederic Crozat wrote:
Le mardi 04 février 2014 à 11:12 +0100, Carlos E. R. a écrit :
Why are you stating it it mandatory, since it isn't and nobody is speaking about make it mandatory ?
Huh? I have not said it is mandatory. Did I? :-?
I find strange to ask for "will we be able to still disable it ?" while
it wasn't part of the discussion at all since we are discussing about
finding somebody willing to maintain plymouth.
--
Frederic Crozat
Le mardi 04 février 2014, à 11:13 +0100, Ludwig Nussel a écrit :
Frederic Crozat wrote:
And it can display a non frightening UI to request passphrase for encrypted disk.
It could but it doesn't in 13.1 because it's broken. So plymouth gets disabled if root is encrypted and the initrd prompts in text mode.
FWIW, I'm using an encrypted /home partition (not root), and things work fine with plymouth. And I feel it'd be a regression to go back to asking the passphrase in a console. Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Tue, 04 Feb 2014 11:18:39 +0100 schrieb Frederic Crozat:
... And it can display a non frightening UI to request passphrase for encrypted disk.
displaying the non frightening (G)UI to request the passphrase seems (often) not to work in 13.1: https://bugzilla.novell.com/show_bug.cgi?id=851960
Which is exactly why we need somebody to actively maintain plymouth..
I am aware there are users who prefer graphical boot screens. I just followed the hint of https://bugzilla.novell.com/show_bug.cgi?id=834063#c3 to uninstall plymouth and run mkinitrd and the initrds shrinked from 22.8MB to 10.4MB which is quite a benefit for the small default boot partitions of systems with encrypted rootfs and with multiverse kernels. Maybe this hint could even be added to the release-notes of 13.1 :-) Regards, Dieter -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le mardi 04 février 2014 à 11:41 +0100, Ludwig Nussel a écrit :
Frederic Crozat wrote:
Le mardi 04 février 2014 à 11:13 +0100, Ludwig Nussel a écrit :
Ok, that sentence compares plymouth to other splash solutions but it makes no statement about the situation compared to a boot with no splash at all.
Isn't it simply bootloader -> resolution switch -> black screen -> X rather than bootloader -> resolution switch -> fancy screen -> X
Not everybody is lucky to have an SSD and a system booting in 5s.
Are you saying systemd didn't make your system boot fast? ;-P
As a Project (and Release) Manager and as somebody who has been contributing on Desktop Linux distributions for almost 15 years, I'm trying to not apply just my own feelings and stuff I'm seeing on my system as a general rule to take a decision. In that regard, even if I've recently switched to SDD on some of my systems, I also know a lot of people don't have SSD systems and usually have a boot time around 30s (to sometime one minute).
Seriously, what big offenders in the boot time of a desktop installation are left?
Disk access and slow CPU, usually, something we can't fix :(
How many seconds are the pain threshold of staring at a black screen?
For any regular user, if you don't see anything happening after 5s,
something is wrong, I'd say (can't find studies on that matter, I'm
speaking from memory there).
--
Frederic Crozat
On 02/04/2014 10:01 PM, Frederic Crozat wrote:
Frederic Crozat wrote:
Le mardi 04 février 2014 à 11:13 +0100, Ludwig Nussel a écrit :
Ok, that sentence compares plymouth to other splash solutions but it makes no statement about the situation compared to a boot with no splash at all.
Isn't it simply bootloader -> resolution switch -> black screen -> X rather than bootloader -> resolution switch -> fancy screen -> X Not everybody is lucky to have an SSD and a system booting in 5s. Are you saying systemd didn't make your system boot fast? ;-P As a Project (and Release) Manager and as somebody who has been contributing on Desktop Linux distributions for almost 15 years, I'm
Le mardi 04 février 2014 à 11:41 +0100, Ludwig Nussel a écrit : trying to not apply just my own feelings and stuff I'm seeing on my system as a general rule to take a decision.
In that regard, even if I've recently switched to SDD on some of my systems, I also know a lot of people don't have SSD systems and usually have a boot time around 30s (to sometime one minute).
Seriously, what big offenders in the boot time of a desktop installation are left? Disk access and slow CPU, usually, something we can't fix :(
How many seconds are the pain threshold of staring at a black screen? For any regular user, if you don't see anything happening after 5s, something is wrong, I'd say (can't find studies on that matter, I'm speaking from memory there).
I still run openSUSE on a old laptop that takes 30+ seconds to boot, my work box needs to mount several network drives and network authentication on start up which is a slow process over a minute. For the second system it is defiantly the reason you would want to keep it, unless of course you can detect or use the previous boot time to enable / disable it. Cheers Simon -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tuesday 04 February 2014 10:41:15 Ludwig Nussel wrote:
Frederic Crozat wrote:
Le mardi 04 février 2014 à 06:14 +0100, Raymond Wooninck a écrit :
On Sunday 02 February 2014 12:24:29 sfalken@opensuse.org wrote:
Only package remaining is Plymouth and I guess that people rather see it disappear than to help out.
No, I don't want to see it disappear at all (since it has replaced all other boot splash alternative, for the good) but I don't have time to maintain it.
To be honest, I also don't want to see it disappear. But sometimes a harsh statement is required to get attention. And it worked in this case, however as seems to be normal for this mailinglist, the discussion went into a different direction. :(
How long does the average system nowadays take until X starts up? If there is a black screen for a few seconds, so what? That's the time the initrd takes to load if plymouth is in there anyways ;-)
As already has been indicated, not everyone has super deluxe systems with high performance SATA and SSD drives. Let's also not forget why we implemented Plymouth. It was a long time request from our users to implement it in order to achieve a more seamless looking boot process from grub to login manager. We managed to integrate plymouth in 12.3 and it was received very well. by our users and also we got good reviews for it. Yes, Plymouth might not be 100% optimal for all possible configurations and we saw (and still see) issues with certain NVidia drivers and for some also using encryption does not always show the required login prompt. Unfortunately I was never able to reproduce the last issue, as that I don't have any LUKS or encryption setup on my small laptop. Ludwig is indicating that a black boot screen might be acceptable by our users, but the question arises then, what is going to establish that black boot screen ? I never tried it, but I guess with Plymouth disabled we will just have the systemd status messages scrolling over the screen. Is this really what we want to present to our users ? Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le mardi 04 février 2014 à 12:44 +0100, Raymond Wooninck a écrit :
On Tuesday 04 February 2014 10:41:15 Ludwig Nussel wrote:
Frederic Crozat wrote:
Le mardi 04 février 2014 à 06:14 +0100, Raymond Wooninck a écrit :
On Sunday 02 February 2014 12:24:29 sfalken@opensuse.org wrote:
Only package remaining is Plymouth and I guess that people rather see it disappear than to help out.
No, I don't want to see it disappear at all (since it has replaced all other boot splash alternative, for the good) but I don't have time to maintain it.
To be honest, I also don't want to see it disappear. But sometimes a harsh statement is required to get attention. And it worked in this case, however as seems to be normal for this mailinglist, the discussion went into a different direction. :(
If nobody else is volunteering, I'll take the ownership of the package..
How long does the average system nowadays take until X starts up? If there is a black screen for a few seconds, so what? That's the time the initrd takes to load if plymouth is in there anyways ;-)
As already has been indicated, not everyone has super deluxe systems with high performance SATA and SSD drives. Let's also not forget why we implemented Plymouth. It was a long time request from our users to implement it in order to achieve a more seamless looking boot process from grub to login manager. We managed to integrate plymouth in 12.3 and it was received very well. by our users and also we got good reviews for it.
Yes, Plymouth might not be 100% optimal for all possible configurations and we saw (and still see) issues with certain NVidia drivers and for some also using encryption does not always show the required login prompt. Unfortunately I was never able to reproduce the last issue, as that I don't have any LUKS or encryption setup on my small laptop.
Ludwig is indicating that a black boot screen might be acceptable by our users, but the question arises then, what is going to establish that black boot screen ? I never tried it, but I guess with Plymouth disabled we will just have the systemd status messages scrolling over the screen. Is this really what we want to present to our users ?
Clearly, no, unless we target server people ..
--
Frederic Crozat
On 2014-02-04 04:47 (GMT-0500) Wolfgang Rosenauer composed:
since 13.1 it takes around 2 minutes until my X comes up on my desktop machine and nobody can (or want to) help/tell me why. But I agree it was not long for 12.3.
Is your installation pure 13.1? Are you aware cups can cause boot delay if newer? e.g. https://bugzilla.novell.com/show_bug.cgi?id=860394 -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 04.02.2014 13:24, schrieb Felix Miata:
On 2014-02-04 04:47 (GMT-0500) Wolfgang Rosenauer composed:
since 13.1 it takes around 2 minutes until my X comes up on my desktop machine and nobody can (or want to) help/tell me why. But I agree it was not long for 12.3.
Is your installation pure 13.1? Are you aware cups can cause boot delay if newer? e.g. https://bugzilla.novell.com/show_bug.cgi?id=860394
It's pretty pure 13.1 with only very few exceptions and cups is not amongst them. Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Raymond Wooninck wrote:
Ludwig is indicating that a black boot screen might be acceptable by our users, but the question arises then, what is going to establish that black boot screen ? I never tried it, but I guess with Plymouth disabled we will just have the systemd status messages scrolling over the screen. Is this really what we want to present to our users ?
With the quiet option the screen just stays black, you only see what initrd prints until a getty or xdm is started. With some cleverness in systemd it could even print something useful if it notices that some service takes extraordinarily long. I think it already does that in verbose mode. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Frederic Crozat wrote:
In that regard, even if I've recently switched to SDD on some of my systems, I also know a lot of people don't have SSD systems and usually have a boot time around 30s (to sometime one minute).
Did you check on those systems what exactly is causing this? By default at least there shouldn't be much to start. So if those systems fail to get to X quickly maybe it's because systemd starts too much in parallel instead of looking at the critical path first. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le mardi 04 février 2014 à 13:44 +0100, Ludwig Nussel a écrit :
Raymond Wooninck wrote:
Ludwig is indicating that a black boot screen might be acceptable by our users, but the question arises then, what is going to establish that black boot screen ? I never tried it, but I guess with Plymouth disabled we will just have the systemd status messages scrolling over the screen. Is this really what we want to present to our users ?
With the quiet option the screen just stays black, you only see what initrd prints until a getty or xdm is started. With some cleverness in systemd it could even print something useful if it notices that some service takes extraordinarily long.
This part has been improved in upstream systemd
I think it already does that in verbose mode.
Or when you press esc and you are running plymouth ;)
--
Frederic Crozat
Vincent Untz wrote:
Le mardi 04 février 2014, à 11:13 +0100, Ludwig Nussel a écrit :
Frederic Crozat wrote:
And it can display a non frightening UI to request passphrase for encrypted disk.
It could but it doesn't in 13.1 because it's broken. So plymouth gets disabled if root is encrypted and the initrd prompts in text mode.
FWIW, I'm using an encrypted /home partition (not root), and things work fine with plymouth. And I feel it'd be a regression to go back to asking the passphrase in a console.
Yes, it works during normal boot *usually*. I got at least one report where the password prompt didn't work during boot. I couldn't reproduce it though. In initrd it was pretty much 100% reproducible though, so for encrypted root plymouth is disabled in 13.1. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le mardi 04 février 2014 à 13:54 +0100, Ludwig Nussel a écrit :
Frederic Crozat wrote:
In that regard, even if I've recently switched to SDD on some of my systems, I also know a lot of people don't have SSD systems and usually have a boot time around 30s (to sometime one minute).
Did you check on those systems what exactly is causing this? By default at least there shouldn't be much to start. So if those systems fail to get to X quickly maybe it's because systemd starts too much in parallel instead of looking at the critical path first.
Yes, and it is IO saturation and low cpu power.. Try booting an old
Athlon or a netbook and you'll see :)
--
Frederic Crozat
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2014-02-04 11:44, Frederic Crozat wrote:
Le mardi 04 février 2014 à 11:34 +0100, Carlos E. R. a écrit :
On 2014-02-04 11:17, Frederic Crozat wrote:
Le mardi 04 février 2014 à 11:12 +0100, Carlos E. R. a écrit :
Why are you stating it it mandatory, since it isn't and nobody is speaking about make it mandatory ?
Huh? I have not said it is mandatory. Did I? :-?
I find strange to ask for "will we be able to still disable it ?" while it wasn't part of the discussion at all since we are discussing about finding somebody willing to maintain plymouth.
But I never asked that question ("will we be able to still disable it ?"). That must have been somebody else. I was just commenting on why some of us have to remove it from our installs. I'm not suggesting to remove it from the distribution, I'm just saying it causes problems that need to be addressed. And removing it also causes some issues that should be addressed as well. - -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlLw8FwACgkQtTMYHG2NR9U08wCbBm2sTHCHMZMLEH1Jaj4+eDUD OasAn2yHJbHurnuNl3Imq5OuiufxrzY1 =aTqh -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2014-02-04 12:31, Frederic Crozat wrote:
In that regard, even if I've recently switched to SDD on some of my systems, I also know a lot of people don't have SSD systems and usually have a boot time around 30s (to sometime one minute).
Several minutes here (287834ms). Not a simple desktop, though. And no, I'm not complaining, I accept that time :-) - -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlLw8dUACgkQtTMYHG2NR9WD9wCePQ7pEr39VErRJV9h3mur8yUl 8+IAn2DDyJpg77/0hDJD+LLJ1elRLmU1 =Tk31 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2014-02-04 12:44, Raymond Wooninck wrote:
I never tried it, but I guess with Plymouth disabled we will just have the systemd status messages scrolling over the screen. Is this really what we want to present to our users ?
To the general public, no. To people like me, yes :-) - -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlLw82IACgkQtTMYHG2NR9WcpwCeLLJjGG5ACc+I+JVmANwKpGGx +6gAnjllVSB7LKw22MtUjl3yKHeNie2x =3nre -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 04.02.2014 10:47, schrieb Wolfgang Rosenauer:
since 13.1 it takes around 2 minutes until my X comes up on my desktop machine and nobody can (or want to) help/tell me why. But I agree it was not long for 12.3.
mv /var/log/journal /var/log/journal.disabled && reboot -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue, Feb 04, Frederic Crozat wrote:
Strange, I'm still getting a passphrase prompt in plymouth on 13.1 on my system ;)
Did you ever try to execute the error paths? bnc#848220 went from "have to wait a few minutes until timeout" to "boot hangs forever" with the updates released in the last 4 weeks. And thats even with plymouth uninstalled. Also, do you consider the passphrase prompt "sane"? I mean its both misplaced on screen (lower right part of screen) and oddly named (whole /etc/crypttab line dumped to the screen). Olaf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le mardi 04 février 2014 à 17:21 +0100, Olaf Hering a écrit :
On Tue, Feb 04, Frederic Crozat wrote:
Strange, I'm still getting a passphrase prompt in plymouth on 13.1 on my system ;)
Did you ever try to execute the error paths? bnc#848220 went from "have to wait a few minutes until timeout" to "boot hangs forever" with the updates released in the last 4 weeks. And thats even with plymouth uninstalled.
Well, if there are issues when plymouth is uninstalled, we can't blame plymouth..
Also, do you consider the passphrase prompt "sane"? I mean its both misplaced on screen (lower right part of screen) and oddly named (whole /etc/crypttab line dumped to the screen).
That means nobody cared enough to fix the branding package, I'd say..
--
Frederic Crozat
On 4 February 2014 17:25, Frederic Crozat
Also, do you consider the passphrase prompt "sane"? I mean its both misplaced on screen (lower right part of screen) and oddly named (whole /etc/crypttab line dumped to the screen).
That means nobody cared enough to fix the branding package, I'd say..
Excuse me, I cared :) The prompt appearing on 'lower right part of the screen' is news to me, if someone can point me in the direction of a bug report I'll certainly take a look at it - On all of my test machines, the prompt is in the lower center, as it should be The whole /etc/crypttab line being dumped appears (as far as I could find out) be an upstream plymouth 'feature' (as in, something I could not find a way of fixing), but I tried; I'll admit to taking my foot off the accelerator trying to fix this when I realised that full disk encryption didn't use the pretty plymouth prompt, as my logic was that most people hitting the horrifically long text in the branded prompt would have much shorter /etc/crypttab lines (eg /dev/sda2 vs /dev/good/lord/this/is/a/long/device/id) I may have a flaw in my logic, but it certainly isn't due to a lack of caring, far from it. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Le mardi 04 février 2014 à 18:11 +0100, Richard Brown a écrit :
On 4 February 2014 17:25, Frederic Crozat
wrote: Also, do you consider the passphrase prompt "sane"? I mean its both misplaced on screen (lower right part of screen) and oddly named (whole /etc/crypttab line dumped to the screen).
That means nobody cared enough to fix the branding package, I'd say..
Excuse me, I cared :)
The prompt appearing on 'lower right part of the screen' is news to me, if someone can point me in the direction of a bug report I'll certainly take a look at it - On all of my test machines, the prompt is in the lower center, as it should be
The whole /etc/crypttab line being dumped appears (as far as I could find out) be an upstream plymouth 'feature' (as in, something I could not find a way of fixing), but I tried; I'll admit to taking my foot off the accelerator trying to fix this when I realised that full disk encryption didn't use the pretty plymouth prompt, as my logic was that most people hitting the horrifically long text in the branded prompt would have much shorter /etc/crypttab lines (eg /dev/sda2 vs /dev/good/lord/this/is/a/long/device/id)
I may have a flaw in my logic, but it certainly isn't due to a lack of caring, far from it.
I'll fill a bug report with some screenshots ;)
--
Frederic Crozat
Am 04.02.2014 15:31, schrieb Stefan Seyfried:
Am 04.02.2014 10:47, schrieb Wolfgang Rosenauer:
since 13.1 it takes around 2 minutes until my X comes up on my desktop machine and nobody can (or want to) help/tell me why. But I agree it was not long for 12.3.
mv /var/log/journal /var/log/journal.disabled && reboot
I don't have /var/log/journal Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (13)
-
Carlos E. R.
-
dieter
-
Felix Miata
-
Frederic Crozat
-
Guido Berhoerster
-
Ludwig Nussel
-
Olaf Hering
-
Raymond Wooninck
-
Richard Brown
-
Simon
-
Stefan Seyfried
-
Vincent Untz
-
Wolfgang Rosenauer