This bug was fixed in the package plymouth - 0.9.3-1ubuntu10.1
---
plymouth (0.9.3-1ubuntu10.1) cosmic; urgency=medium
* debian/patches/git_helper_renderer.patch,
debian/patches/git_desactivate_renderer.patch:
- 'device-manager: free keyboards when deactivating a renderer',
This bug was fixed in the package plymouth - 0.9.3-1ubuntu7.18.04.2
---
plymouth (0.9.3-1ubuntu7.18.04.2) bionic; urgency=medium
[ Mauricio Faria de Oliveira ]
* d/p/0013-device-manager-don-t-watch-for-udev-events-when-deac_bionic.patch:
- Don't process udev events after
note on autopkgtest regression; the only failing test is systemd (i386)
which appears to be a result of bug 1824237, e.g. from the failing
autopkgtest:
Apr 10 18:53:08 autopkgtest lxd.activate[1348]: cannot locate the core
or legacy core snap (current symlink missing?): No such file or
directory
Hi Łukasz,
Just following up if you're OK with the results of the testing you
asked.
I realize you might be busy with the Disco release, so no worries if we
catch up on this next week.
Thanks,
Mauricio
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi Łukasz,
I've tested the bionic/cosmic-proposed packages with disk encryption.
Both the updates/proposed packages still show the password prompt,
and read it correctly, and move forward to the login screen.
* One caveat here, read on to the Cosmic's details.
I could reproduce the problem
Hi Łukasz,
Ok, I'll test that soon.
cheers,
Mauricio
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794292
Title:
plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in
Regarding this SRU, my question in commend #53 still remains unanswered
- did anyone test the -proposed packages with a system that has disk
encryption? Since there is regression potential in unlocking disks
(which would be a very serious regression if that happened) I would
prefer not to release
bionic-proposed:
---
$ dpkg -s plymouth | grep ^Version:
Version: 0.9.3-1ubuntu7.18.04.2
$ sudo plymouthd --no-daemon --debug --kernel-command-line=splash &
[1] 1055
$ [main.c:2066]
initialize_environment:initializing minimal work
Correction:
This is the right order for these steps:
(otherwise just run 'sudo update-initramfs -u' to get the initramfs's
modprobe.d dir updated)
"""
Install its DRM module, which should not load by default:
$ echo 'blacklist cirrus' | sudo tee /etc/modprobe.d/blacklist-cirrus.conf
$ sudo
bionic-updates
--
$ dpkg -s plymouth | grep ^Version:
Version: 0.9.3-1ubuntu7.18.04.1
$ sudo plymouthd --no-daemon --debug --kernel-command-line=splash &
[1] 1092
$ [main.c:2063]
initialize_environment:initializing
Test Case
=
For example, this Bionic Server VM:
$ uvt-simplestreams-libvirt sync release=bionic arch=amd64
$ uvt-kvm create --memory 2048 --cpu 2 --disk 8 bionic-lp1794292
release=bionic arch=amd64
$ uvt-kvm ssh bionic-lp1794292
It has a virtual Cirrus VGA
Hi Gert,
Thank you very much!
In parallel, I've been working on a synthetic test-case
with a virtual machine, and fortunately just found one!
I'll post the details shortly, but I can also confirm
that bionic-proposed resolves the problem.
cheers,
Mauricio
--
You received this bug
To reproduce the problem at bionic I had to uninstall the cryptsetup-package
and use DeviceTimeout 1 at /etc/plymouth/plymouthd.cfg.
After installing plymouth:i386 0.9.3-1ubuntu7.18.04.2, the problem disappeared.
Problem solved.
--
You received this bug notification because you are a member of
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794292
Title:
plymouthd crashed with SIGSEGV in /sbin/plymouthd:11
Hello,
Could anyone confirm if they experience this problem on Bionic too,
and if they would be able to test the package in bionic-proposed ?
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello Steve, or anyone else affected,
Accepted plymouth into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/plymouth/0.9.3-1ubuntu7.18.04.2 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Did anyone test this package on a system with disk encryption enabled? I
would like to make sure that users can still unlock their disks on
system boot before this goes to -updates, especially that it might be a
bit hard for them to actually unbrick their systems afterwards.
--
You received this
I've installed plymouth 0.9.3-1ubuntu10.1 from the cosmic-proposed
repository and I now have the Xubuntu boot splash screen back and no
longer experience a crash after logging in.
Thanks to everyone involved in fixing this.
Steve
--
You received this bug notification because you are a member
Installed packages plymouth and libplymouth4 from cosmic-proposed.
e.g: Get:1 http://archive.ubuntu.com/ubuntu cosmic-proposed/main i386 plymouth
i386 0.9.3-1ubuntu10.1
To test the fix I verified plymouth and drm-modules are not present at
initramfs.
This causes intel drm to be initiated after
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794292
Title:
plymouthd crashed with SIGSEGV in /sbin/plymouthd:11
Hello!
I've been having these crashes on two laptops nearly every reboot. I
installed plymouth 0.9.3-1ubuntu10.1 from the -proposed repository on a
fairly recently installed version 18.10 (cosmic) which contains no other
proposed updates. So far, after rebooting many times, I'm happy to
report
Hello Steve, or anyone else affected,
Accepted plymouth into cosmic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/plymouth/0.9.3-1ubuntu10.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
- A green Xubuntu splash screen with a spinning circle normally appears on
- boot up.
+ [Impact]
+ plymouth has been crashing a whole bunch and notifying users about it.
+
+ [Test Case]
+ We don't have a specific test case but luckily :-( there are thousands of
crashes
** Changed in: plymouth (Ubuntu Cosmic)
Assignee: Mathieu Trudel-Lapierre (cyphermox) => Brian Murray
(brian-murray)
** Also affects: plymouth (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: plymouth (Ubuntu Bionic)
Status: New => Triaged
** Changed in:
** Changed in: plymouth (Ubuntu Cosmic)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794292
Title:
plymouthd crashed with SIGSEGV in /sbin/plymouthd:11
** Changed in: plymouth (Ubuntu Cosmic)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794292
Title:
plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in
Fair enough. I do credit you by name already in the commit messages:
https://gitlab.freedesktop.org/plymouth/plymouth/merge_requests/10
https://gitlab.freedesktop.org/cyphermox/plymouth/commit/c46f446fe44457f599805b685547c2258bb3fa96
Sorry, we don't see it there. The emails are re-jiggled by Launchpad.
If you prefer, you can send it to me directly (cyphermox AT ubuntu.com),
or decline to provide one (since it would show up in the commit logs for
plymouth)
--
You received this bug notification because you are a member of
Gert, could you provide us with an email address so we can correctly
attribute the changes to you, given that you contributed the major part
of the patches that will go in plymouth?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry, previous information wrong.
At upgraded 18.04 I have cryptsetup and crypsetup-bin, not cryptsetup-initramfs.
At fresh 18.10 I have no package from cryptsetup.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
No.
I have cryptsetup and crypsetup-bin, not cryptsetup-initramfs.
For checking a fix for gnome-wayland I did a fresh install of 32-bits 18.10
from a "mini" (because no image available for 32-bits).
Apparently this does not automatically install cryptsetup-initramfs.
It is rather strange,
@Gert, so upstream confirmed the issue and your comments make sense.
Now looking a bit around, we should still have FRAMEBUFFER=y in the
configuration, but that file moved to cryptsetup-initramfs ... do you
have that deb installed?
--
You received this bug notification because you are a member
OK; upstream got to an idea similar to your patch. I'm away from my
usual desk right now and apparently missing some credentials to log back
in to gitlab, but I will update current PRs on gitlab to propose a fix
similar to your patch: iterating through keyboards to remove them when
freeing
This bug was fixed in the package plymouth - 0.9.3-1ubuntu11
---
plymouth (0.9.3-1ubuntu11) disco; urgency=medium
* Workaround a plugin being already deactivated when we try to remove input
watchers for keyboards in DRM mode. Also guard against races at removing
input
I spent a couple of hours looking at the disassembly for your crash
file, and I think one of the patches I applied, moving
keyboard->is_active = false earlier when removing input watches, should
improve the situation a lot. Otherwise, my next question mark is
relevant to the code optimization.
I can't get behind sponsoring that patch as-is. It seems to me like this
is patching around symptoms of an underlying issue rather than fixing
the real problem. I haven't been able to open your apport crash file yet
due to it being for i386, and I'm not set up to test that.
Let's start by making
The patch I described before solves the problem, but for some reason plymouth
does not attach the second renderer to the keyboard. Therefore switching to
text-mode by pressing escape-key does not work.
To make this work variable manager->local_console_managed must be set to false.
This causes
I do not have access to upstream and also have no idea what to add
there.
I have the impression the root cause of the plymouth crash is a configuration
problem.
I compared Ubuntu 18.04, upgraded from 16.04, with the fresh install of 18.10.
At 18.10 file
I've reported https://gitlab.freedesktop.org/plymouth/plymouth/issues/70
upstream about the new assert (but it looks a similar issue)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794292
Title:
@Gert, you seem to understand a bit what's going on/have an idea about
the problem, it would be useful if you can comment on the upstream
report with your findings
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
bug #1802993 seems the same issue
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794292
Title:
plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in
ply_renderer_set_handler_for_input_source ->
Same problem as described before.
To force I use timeout 1 and theme fade-in. But same problem also occurred at
my PC with the default timeout 5, as was on the trace.
I will upload the crashdump (which by default was ignored by apport).
Routine ply_renderer_free does a hard free of renderer. So
The latest version of plymouth in your PPA DOESN'T resolves the issue for me.
After upgrading plymouth from ppa:cyphermox/ppa nothing changed
plymouth:
Installed: 0.9.3-1ubuntu11~mtrudel4
Candidate: 0.9.3-1ubuntu11~mtrudel4
Version table:
*** 0.9.3-1ubuntu11~mtrudel4 500
500
But does it fix the crash for you? You shouldn't worry about the dates
on the files, those are in part caused by the changelog entry when
building the package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I think, I still get old stuff from 15-10
gert@Gert2:/var/cache/apt/archives$ dpkg -c
libplymouth4_0.9.3-1ubuntu11~mtrudel4_i386.deb
drwxr-xr-x root/root 0 2018-10-15 16:36 ./
drwxr-xr-x root/root 0 2018-10-15 16:36 ./lib/
drwxr-xr-x root/root 0 2018-10-15 16:36
The latest version of plymouth in your PPA resolves the issue for me.
bdmurray@lantern:~$ ls /var/crash/
bdmurray@lantern:~$ apt-cache policy plymouth
plymouth:
Installed: 0.9.3-1ubuntu11~mtrudel4
Candidate: 0.9.3-1ubuntu11~mtrudel4
Version table:
*** 0.9.3-1ubuntu11~mtrudel4 500
For context:
It looks like the issue is really with the call to
"set_handler_for_input_source()" on a plugin. renderer->plugin_interface
is null, so dereferencing that fails:
https://paste.ubuntu.com/p/tmcVcvgGXw/
All in all, much easier to comprehend when I think of looking at the
disassembly,
Actually, according to the backtraces the issue isn't with
renderer->backend; we're not even reaching that point. It's still a
potential issue though.
Same ppa as before: ppa:cyphermox/ppa
I have uploaded a new plymouth there, which should mitigate the crash
exactly as reported in the
_sbin_plymouthd.0.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794292
Title:
plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in
ply_renderer_set_handler_for_input_source ->
I have the same issue on my newly installed Ubuntu Cosmic(18.10) (laptop
ASUS K55VM)
plymouthd crashed with SIGSEGV in
ply_renderer_set_handler_for_input_source()
** Attachment added: "_sbin_plymouthd.0.crash"
Problem not solved.
I think I got 4 problems:
1)
I think the second ppa (*mtrudel2*) has exacly same contents as the first one.
At least the binaries and shared loadlibraries have the same time stamp (15
october).
So this will not contain the last version.
2)
I have the idea the shared
@Gert,
I've made some changes to your suggestion (we don't want to circumvent
creating more DRM devices than the first successful one, I think) and it
looks like the "right value" according to upstream for the compiler
warning is to return false.
Please try the new package on my ppa
Proposing next improved code
At src/libply-splash-core/ply-device-manager.c
1) at
create_devices_for_subsystem (ply_device_manager_t *manager,
const char *subsystem)
change
found_device = create_devices_for_udev_device (manager, device);
into
Unfortunately again it crashes, logging on with gdm3, both with and
without wayland.
The crash seems to be at the same place.
Syslog:
Oct 16 16:04:13 Gert2 systemd[1]: plymouth-start.service: Main process exited,
code=dumped, status=11/SEGV
Oct 16 16:04:13 Gert2 gdm3[710]: error: unexpectedly
I uploaded a test package to my ppa:
sudo add-apt-repository ppa:cyphermox/ppa
@Gert, would you mind giving it a try, see if this works for you,
assuming that you can reproduce this bug easily?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: plymouth (Ubuntu Cosmic)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794292
Title:
plymouthd crashed with
Reopening per comment #14
** Changed in: plymouth (Ubuntu Cosmic)
Status: Fix Released => Triaged
** Changed in: plymouth (Ubuntu Cosmic)
Status: Triaged => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
At my laptop it happens at (almost) every start.
FYI I attach a symbolic trace
** Attachment added: "symbolic trace of crash after released fix"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1794292/+attachment/5197512/+files/stack1.txt
--
You received this bug notification
Yeah, I feared that might be the case. This is the problem when the bug
isn't so easy to reproduce.
There's a couple of things I want to try; let's proceed now with a
package in a PPA before we randomly upload stuff to the archive --
there's definitely some cleanup code that could be added to
Unfortunately the fix does not solve the problem and still crashes.
ProblemType: Crash
Architecture: i386
Date: Thu Oct 4 16:54:33 2018
DistroRelease: Ubuntu 18.10
ExecutablePath: /sbin/plymouthd
ExecutableTimestamp: 1538408760
MachineType: Dell Inc. Latitude D620
Package: plymouth
This bug was fixed in the package plymouth - 0.9.3-1ubuntu9
---
plymouth (0.9.3-1ubuntu9) cosmic; urgency=medium
* debian/patches/git_move_renderer_deactivate_778e0fb7.patch: move the
ply_device_manager_deactivate_renderers() calls into hide_splash(). This
makes sure it is
looks like the patch being refered to has been uploaded in
https://launchpad.net/ubuntu/+source/plymouth/0.9.3-1ubuntu9 which is
still in cosmic-proposed
** Changed in: plymouth (Ubuntu Cosmic)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a
The patch should be fine, in fact I was debugging it and it looks like
that the renderers where disactivated before than the renderer
keyboards, thus the crash.
This was some gdb debugging, in case it might be useful in future:
(gdb) bt
#0 0x7ff2a56137f9 in
Is this a crash that people are able to easily reproduce? I can't figure
out how to get that crash here, but I have a patch likely to fix the
issue (and the patch is necessary anyway).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: id-5bad7286befb7a37e6f5072a
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794292
Title:
plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in
** Also affects: plymouth (Ubuntu Cosmic)
Importance: High
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794292
Title:
plymouthd crashed with SIGSEGV in
Ugh, ignore the above. Wrong issue. Sorry.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794292
Title:
plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in
This is fixed in Ubuntu MATE 18.10 via mate-screensaver 1.20.2-1 which
we will SRU to 18.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794292
Title:
plymouthd crashed with SIGSEGV in
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1794292
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Summary changed:
- plymouthd crashed with SIGSEGV in ply_renderer_set_handler_for_input_source()
+ plymouthd crashed with SIGSEGV in /sbin/plymouthd:11 in
ply_renderer_set_handler_for_input_source ->
ply_keyboard_stop_watching_for_renderer_input ->
ply_keyboard_stop_watching_for_input ->
70 matches
Mail list logo
