When Plymouth is uninstalled on a system running openSUSE 13.1 with KDE’s desktop, the system appears to Hibernate on command, but does not resume. Instead, it goes directly to a new Login at the Login Screen.
???
I thought this was fixed several openSUSE versions ago?
Can anyone confirm?
Hm, I haven’t seen such a problem when using 13.1, but I didn’t uninstall plymouth either.
Still, plymouth should not be necessary for resume to work.
I have no 13.1 system at the moment, so cannot try it. (I think I’m going to upgrade an old unused 11.4 system to 13.1 during the weekend if I find the time…)
The question I supppose is: is it not trying to resume at all, or is it resuming and the KDE session crashes?
And installing plymouth again fixes it?
Also, do you have pm-utils installed? Try without, or set SLEEP_MODULE=“kernel” in /usr/lib/pm-utils/defaults.
On 2015-04-10 07:36, Fraser Bell wrote:
>
> When Plymouth is uninstalled on a system running openSUSE 13.1 with
> KDE’s desktop, the system appears to Hibernate on command, but does not
> resume. Instead, it goes directly to a new Login at the Login Screen.
Are you sure? Perhaps it does resume, but KDE crashes?
> ???
>
> I thought this was fixed several openSUSE versions ago?
>
> Can anyone confirm?
Well, I use 13.1, I remove plymouth on all my systems, I hibernate
routinely, but… I don’t use the KDE desktop. Currently XFCE.
I hibernate by command line, “/usr/sbin/pm-hibernate”. I intentionally
avoid the desktop hibernate button (buggy, but unrelated to your issue).
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Minas Tirith))
Well, it just boots straight up to the login screen the same as any cold boot does, no apparent crash, apparently just no hibernation file created when entering the hibernation state.
And installing plymouth again fixes it?
Yes. And uninstalling plymouth cause the problem to return, then re-installing plymouth fixes the hibernation process again.
Of note: When re-installing plymouth, I noticed it downloaded and installed “suspend” … both times when re-installing plymouth. Unfortunately, I (so far) did not watch closely enough to see if this “suspend” is uninstalled when plymouth is uninstalled, but I suspect so.
Also, do you have pm-utils installed?
Yes, and it stays installed when plymouth is uninstalled.
Try without, or set SLEEP_MODULE=“kernel” in /usr/lib/pm-utils/defaults.
Have not tried this yet. Busy with lots of things, but will get around to uninstalling plymouth and looking again at these things when I get some more time to play.
Thanks for your replies, Wolfi.
See above.
> ???
>
> I thought this was fixed several openSUSE versions ago?
>
> Can anyone confirm?
Well, I use 13.1, I remove plymouth on all my systems, I hibernate
routinely, but… I don’t use the KDE desktop. Currently XFCE.
Maybe just KDE related?
I hibernate by command line, “/usr/sbin/pm-hibernate”. I intentionally
avoid the desktop hibernate button (buggy, but unrelated to your issue).
When I get time to play;), may uninstall plymouth again & try that to see if there is a difference.
Oh…
And I forgot to mention:
If I add
plymouth.enable=0
to the command line, instead of uninstalling it, hibernate works just fine.
I tried it now, and at first that (now) 13.1 system resumed just fine even with plymouth uninstalled.
I had to set SLEEP_MODULE=“kernel” in /usr/lib/pm-utils/defaults (actually I just commented out that line which has the same effect as “kernel” is the default) though to make it hibernate at all (even with plymouth installed).
As I saw errors regarding plymouthd not found on boot/resume, I tried to recreate the initrd.
And now I can reproduce your problem…
Installing suspend again (it requires libply2, so will get uninstalled if you remove that) fixes resume.
So it’s not uninstalling plymouth that causes the problem, but uninstalling suspend which apparently contains the necessary mkinitrd hooks for resume.
On 2015-04-11 12:06, wolfi323 wrote:
> Installing suspend again (it requires libply2, so will get uninstalled
> if you remove that) fixes resume.
> So it’s not uninstalling plymouth that causes the problem, but
> uninstalling suspend which apparently contains the necessary mkinitrd
> hooks for resume.
That makes sense.
I removed plymouth long ago, but not libply2. No need to.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Minas Tirith))
Makes sense. Note, though, that I went into Yast, searched on Plymouth, and selected to uninstall the top item in the list. The item is libply-boot-client2 (at least on my system). Selecting this pulls all the rest out, including libply2 and suspend. Note, though, that suspend does not show in the search list, so unless you click on the “and 5 more” line in the dialogue and carefully read all dependency actions that will take place, you do not see that suspend is automatically selected.
Since suspend does NOT require plymouth (though it requires libply2), would this not be classified as a bug? Or, at least a bad design flaw?
… No, not really.
The technically correct way to remove Plymouth in Yast is to not select the top item in the list when searching on “plymouth”, but instead select the item simply labelled “plymouth”. If uninstalled this way, “suspend” (and the required plymouth libraries) are not uninstalled along with plymouth … and hibernation continues to work as it should.
That’s how I removed “plymouth” the first time that I did it (I think I was running 12.3 at the time). But I have since learned that it is better to mark only “plymouth” itself for removal. That does remove some of the other components. But it leaves the parts that seem to be needed for hibernation. Personally, I don’t use hibernation so I have not tested this.
I’m not sure, but I think they made changes for 13.2 so that hibernation doesn’t depend on plymouth components.
On 2015-04-12 06:36, Fraser Bell wrote:
>
> Fraser_Bell;2704320 Wrote:
>> Since suspend does NOT require plymouth (though it requires libply2),
>> would this not be classified as a bug? Or, at least a bad design flaw?
>
> … No, not really.
>
> The technically correct way to remove Plymouth in Yast is to
> -not- select the top item in the list when searching on
> “plymouth”, but -instead- select the item simply
> labelled “plymouth”. If uninstalled this way, “suspend” (and the
> required plymouth libraries) are -not uninstalled-
> along with plymouth … and hibernation continues to work as it
> should.
Correct.
I have a paper note somewhere saying about exactly the same thing. I
found out years ago that removing all plymouth components wanted to
remove suspend components as well — so I backed and unticked whatever
elements of plymouth had dependencies on other core system parts.
Trick: Always have a look at the “summary” tab in YaST before proceeding
with install/remove packages.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” (Minas Tirith))
Well … yes. The smart thing to do when doing such uninstalls (or installs) is to go through the list of items carefully. Of course, as we get more used to doing these things, some(most?) of us tend to get in a hurry and a little sloppy at that … present company in this thread excluded, of course.rotfl!
Yes. I just had a look in 13.2, and suspend does not require libply2 there. So you can uninstall all of plymouth (including all libply* packages), and suspend will not be removed as a consequence.
This changelog entry in the suspend package sounds related:
* Sun May 11 2014 coolo@suse.com
- disable plymouth support once and for all - plymouth no longer
offers half the API, remove suspend-plymouth.patch
That’s probably also the reason why there’s no hibernation splash screen in 13.2 any more…