Send plymouth mailing list submissions to
plymouth@lists.freedesktop.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.freedesktop.org/mailman/listinfo/plymouth
or, via email, send a message with subject or body 'help' to
plymouth-requ...@lists.freedesktop.org
You can reach the person managing the list at
plymouth-ow...@lists.freedesktop.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of plymouth digest..."
Today's Topics:
1. W: plymouth module (/usr/lib/x86_64-linux-gnu/plymouth//.so)
missing, skipping that theme. (Elvis Stansvik)
2. Re: W: plymouth module
(/usr/lib/x86_64-linux-gnu/plymouth//.so) missing, skipping that
theme. (Elvis Stansvik)
3. Re: W: plymouth module
(/usr/lib/x86_64-linux-gnu/plymouth//.so) missing, skipping that
theme. (Elvis Stansvik)
4. Re: W: plymouth module
(/usr/lib/x86_64-linux-gnu/plymouth//.so) missing, skipping that
theme. (Elvis Stansvik)
----------------------------------------------------------------------
Message: 1
Date: Tue, 23 Aug 2016 15:43:09 +0200
From: Elvis Stansvik <elvis.stans...@orexplore.com>
To: plymouth@lists.freedesktop.org
Subject: W: plymouth module (/usr/lib/x86_64-linux-gnu/plymouth//.so)
missing, skipping that theme.
Message-ID:
<cae-7vjkjopkwhyoh6g+kajwtwcqmj9-tii60dcyunknzhov...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
I'm getting that warning when running update-initramfs -u after having
moved my theme to /usr/share/plymouth/themes from /lib/plymouth (location
of themes changed in Ubuntu 16.04).
This is with plymouth 0.9.2 from Ubuntu packages, and the problem seems to
be the same as:
https://ubuntuforums.org/showthread.php?t=2322684
But the workaround(s) described in that thread doesn't seem to work for me.
Looking at lsinitramfs /boot/initrd.img-4.4.0-31-generic output I can
confirm that the script.so module that my custom theme uses, and the custom
theme itself, is not installed to the initramfs image. But I'm unsure how
to debug further.
The theme worked fine when it was living in /lib under Ubuntu 15.10 (which
had plymouth 0.9.0).
The warning looks strange to me (as if some sed line went wrong?).
Any tips/pointers are highly welcome, as we need this theme to work on our
Ubuntu-based product.
Thanks in advance,
Elvis Stansvik
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/plymouth/attachments/20160823/ae8e72dc/attachment-0001.html>
------------------------------
Message: 2
Date: Tue, 23 Aug 2016 15:46:40 +0200
From: Elvis Stansvik <elvis.stans...@orexplore.com>
To: plymouth@lists.freedesktop.org
Subject: Re: W: plymouth module
(/usr/lib/x86_64-linux-gnu/plymouth//.so) missing, skipping that
theme.
Message-ID:
<CAE-7VJn5=hczzy5cogydzwee47zbqqu-cyuaz-pre7eynpv...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
2016-08-23 15:43 GMT+02:00 Elvis Stansvik <elvis.stans...@orexplore.com>:
> I'm getting that warning when running update-initramfs -u after having
> moved my theme to /usr/share/plymouth/themes from /lib/plymouth (location
> of themes changed in Ubuntu 16.04).
>
> This is with plymouth 0.9.2 from Ubuntu packages, and the problem seems to
> be the same as:
>
> https://ubuntuforums.org/showthread.php?t=2322684
>
> But the workaround(s) described in that thread doesn't seem to work for me.
>
> Looking at lsinitramfs /boot/initrd.img-4.4.0-31-generic output I can
> confirm that the script.so module that my custom theme uses, and the custom
> theme itself, is not installed to the initramfs image. But I'm unsure how
> to debug further.
>
> The theme worked fine when it was living in /lib under Ubuntu 15.10 (which
> had plymouth 0.9.0).
>
> The warning looks strange to me (as if some sed line went wrong?).
>
> Any tips/pointers are highly welcome, as we need this theme to work on our
> Ubuntu-based product.
>
Here's some more Ubuntu-specific info:
estan@newton:~$ LC_ALL=C update-alternatives --display default.plymouth
default.plymouth - manual mode
link best version is
/usr/share/plymouth/themes/kubuntu-logo/kubuntu-logo.plymouth
link currently points to
/usr/share/plymouth/themes/plymouth-theme-orexplore/orexplore.plymouth
link default.plymouth is /usr/share/plymouth/themes/default.plymouth
slave default.plymouth.grub is /usr/share/plymouth/themes/default.grub
/usr/share/plymouth/themes/kubuntu-logo/kubuntu-logo.plymouth - priority 150
slave default.plymouth.grub:
/usr/share/plymouth/themes/kubuntu-logo/kubuntu-logo.grub
/usr/share/plymouth/themes/plymouth-theme-orexplore/orexplore.plymouth -
priority 100
estan@newton:~$
So currently pointing at
/usr/share/plymouth/themes/plymouth-theme-orexplore/orexplore.plymouth ,
which is my custom theme. This file looks like:
estan@newton:~$ cat
/usr/share/plymouth/themes/plymouth-theme-orexplore/orexplore.plymouth
[Plymouth Theme]
Name=Orexplore
Description=Theme showing the Orexplore logo
ModuleName=script
[script]
ImageDir=/usr/share/plymouth/themes/plymouth-theme-orexplore/images
ScriptFile=/usr/share/plymouth/themes/plymouth-theme-orexplore/orexplore.script
estan@newton:~$
The script.so plugin seems installed correctly:
estan@newton:~$ ls /usr/lib/x86_64-linux-gnu/plymouth/
totalt 184
-rw-r--r-- 1 root root 14760 maj 10 19:56 details.so
-rw-r--r-- 1 root root 10600 maj 10 19:56 label.so
-rwxr-xr-x 1 root root 967 maj 10 19:56 plymouth-generate-initrd
-rwxr-xr-x 1 root root 14709 aug 23 15:33 plymouth-populate-initrd
-rwxr-xr-x 1 root root 39 maj 10 19:56 plymouth-update-initrd
drwxr-xr-x 2 root root 4096 maj 18 09:14 renderers
-rw-r--r-- 1 root root 72632 maj 10 19:56 script.so
-rw-r--r-- 1 root root 19016 maj 10 19:56 text.so
-rw-r--r-- 1 root root 14888 maj 10 19:56 tribar.so
-rw-r--r-- 1 root root 18984 maj 10 19:56 ubuntu-text.so
estan@newton:~$
Do you folks think I'm looking at an Ubuntu 16.04 packaging bug, or a bug
in Plymouth?
Elvis
> Thanks in advance,
> Elvis Stansvik
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/plymouth/attachments/20160823/9a463ba0/attachment-0001.html>
------------------------------
Message: 3
Date: Wed, 24 Aug 2016 07:52:28 +0200
From: Elvis Stansvik <elvis.stans...@orexplore.com>
To: plymouth@lists.freedesktop.org
Subject: Re: W: plymouth module
(/usr/lib/x86_64-linux-gnu/plymouth//.so) missing, skipping that
theme.
Message-ID:
<CAE-7VJn=n7=txbvq4nmb4fx4dgrlmcjuux1wd8r28rzbn0e...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
2016-08-23 15:43 GMT+02:00 Elvis Stansvik <elvis.stans...@orexplore.com>:
> I'm getting that warning when running update-initramfs -u after having
> moved my theme to /usr/share/plymouth/themes from /lib/plymouth (location
> of themes changed in Ubuntu 16.04).
>
> This is with plymouth 0.9.2 from Ubuntu packages, and the problem seems to
> be the same as:
>
> https://ubuntuforums.org/showthread.php?t=2322684
>
> But the workaround(s) described in that thread doesn't seem to work for me.
>
> Looking at lsinitramfs /boot/initrd.img-4.4.0-31-generic output I can
> confirm that the script.so module that my custom theme uses, and the custom
> theme itself, is not installed to the initramfs image. But I'm unsure how
> to debug further.
>
> The theme worked fine when it was living in /lib under Ubuntu 15.10 (which
> had plymouth 0.9.0).
>
> The warning looks strange to me (as if some sed line went wrong?).
>
> Any tips/pointers are highly welcome, as we need this theme to work on our
> Ubuntu-based product.
>
I found something which led me to what I think was the solution.
It was this line in scripts/plymouth-populate-initrd.in:
PLYMOUTH_MODULE_NAME=$(grep "ModuleName *= *"
${PLYMOUTH_DATADIR}/plymouth/themes/${PLYMOUTH_THEME_NAME}/${PLYMOUTH_THEME_NAME}.plymouth
| sed 's/ModuleName *= *//')
The script here seems to assume the name of the .plymouth file corresponds
exactly to the name of the parent (theme) directory, which was not the case
for my custom theme. I had
orexplore-plymouth-theme/orexplore.plymouth
orexplore-plymouth-theme/et.c.
orexplore-plymouth-theme/et.c.
If I just installed the theme as
orexplore/orexplore.plymouth
orexplore/et.c.
orexplore/et.c.
instead, I got rid of the warning and the theme now works. The theme and
the script.so plugin end up in the initramfs properly.
I have no idea why it worked on Wily before, since the script looked the
same in 0.9.0 from the looks of it.
Elvis
> Thanks in advance,
> Elvis Stansvik
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/plymouth/attachments/20160824/e797ff56/attachment-0001.html>
------------------------------
Message: 4
Date: Wed, 24 Aug 2016 07:55:55 +0200
From: Elvis Stansvik <elvis.stans...@orexplore.com>
To: plymouth@lists.freedesktop.org
Subject: Re: W: plymouth module
(/usr/lib/x86_64-linux-gnu/plymouth//.so) missing, skipping that
theme.
Message-ID:
<cae-7vjmdxamrmzre0fjmvb-uur7xsj_twwsvh_v-mwnxqe4...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
2016-08-24 7:52 GMT+02:00 Elvis Stansvik <elvis.stans...@orexplore.com>:
> 2016-08-23 15:43 GMT+02:00 Elvis Stansvik <elvis.stans...@orexplore.com>:
>
>> I'm getting that warning when running update-initramfs -u after having
>> moved my theme to /usr/share/plymouth/themes from /lib/plymouth (location
>> of themes changed in Ubuntu 16.04).
>>
>> This is with plymouth 0.9.2 from Ubuntu packages, and the problem seems
>> to be the same as:
>>
>> https://ubuntuforums.org/showthread.php?t=2322684
>>
>> But the workaround(s) described in that thread doesn't seem to work for
>> me.
>>
>> Looking at lsinitramfs /boot/initrd.img-4.4.0-31-generic output I can
>> confirm that the script.so module that my custom theme uses, and the custom
>> theme itself, is not installed to the initramfs image. But I'm unsure how
>> to debug further.
>>
>> The theme worked fine when it was living in /lib under Ubuntu 15.10
>> (which had plymouth 0.9.0).
>>
>> The warning looks strange to me (as if some sed line went wrong?).
>>
>> Any tips/pointers are highly welcome, as we need this theme to work on
>> our Ubuntu-based product.
>>
>
> I found something which led me to what I think was the solution.
>
> It was this line in scripts/plymouth-populate-initrd.in:
>
> PLYMOUTH_MODULE_NAME=$(grep "ModuleName *= *" ${PLYMOUTH_DATADIR}/plymouth/
> themes/${PLYMOUTH_THEME_NAME}/${PLYMOUTH_THEME_NAME}.plymouth | sed
> 's/ModuleName *= *//')
>
> The script here seems to assume the name of the .plymouth file corresponds
> exactly to the name of the parent (theme) directory, which was not the case
> for my custom theme. I had
>
> orexplore-plymouth-theme/orexplore.plymouth
> orexplore-plymouth-theme/et.c.
> orexplore-plymouth-theme/et.c.
>
Sorry, I meant I had
plymouth-theme-orexplore/orexplore.plymouth
plymouth-theme-orexplore/et.c.
plymouth-theme-orexplore/et.c.
But the point being that the name of my .plymouth file was not
<theme_dir>/<theme_dir>.plymouth.
Elvis
> If I just installed the theme as
>
> orexplore/orexplore.plymouth
> orexplore/et.c.
> orexplore/et.c.
>
> instead, I got rid of the warning and the theme now works. The theme and
> the script.so plugin end up in the initramfs properly.
>
> I have no idea why it worked on Wily before, since the script looked the
> same in 0.9.0 from the looks of it.
>
> Elvis
>
>
>
>> Thanks in advance,
>> Elvis Stansvik
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/plymouth/attachments/20160824/2ecc65d6/attachment.html>
------------------------------
Subject: Digest Footer
_______________________________________________
plymouth mailing list
plymouth@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/plymouth
------------------------------
End of plymouth Digest, Vol 74, Issue 3
***************************************
