** Tags removed: rls-y-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636
Title:
plymouthd crashed with SIGSEGV in script_obj_deref_direct()
To manage notifications about this bug go to:
** Changed in: plymouth
Status: Confirmed => Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636
Title:
plymouthd crashed with SIGSEGV in script_obj_deref_direct()
To manage notific
This bug was fixed in the package plymouth - 0.8.8-0ubuntu17.2
---
plymouth (0.8.8-0ubuntu17.2) trusty; urgency=medium
*debian/patches/misc-changes.patch: Drop call to stop_animation as it would
unreference a bunch of variables and cause a crash writing a NULL VMA.
(LP: #92763
This bug was fixed in the package plymouth - 0.9.2-3ubuntu13.5
---
plymouth (0.9.2-3ubuntu13.5) xenial; urgency=medium
*debian/patches/misc-changes.patch: Drop call to stop_animation as it would
unreference a bunch of variables and cause a crash writing a NULL VMA.
(LP: #92763
This bug was fixed in the package plymouth - 0.9.2-3ubuntu20
---
plymouth (0.9.2-3ubuntu20) artful; urgency=medium
*debian/patches/misc-changes.patch: Drop call to stop_animation as it would
unreference a bunch of variables and cause a crash writing a NULL VMA.
(LP: #927636)
I think a couple of weeks is long enough to wait, additionally with the
phased-updater and the number of users with plymouth installed we'll
have an extra layer of protection from any regressions.
I'm pretty confident in the fix and don't think smoke testing is
necessary.
--
You received this bu
> While I'm checking the Error Tracker for new plymouth crashes
regularly it would be best to let this SRU age for longer than the 7 day
period to be sure nothing is amiss.
How long do you think we should wait?
Separately, would it be worth manually smoke testing plymouth from the
proposed pocket
The errors bucket does not contain any crashes from the version of the
package in -proposed.
** Tags removed: verification-needed-artful verification-needed-trusty
verification-needed-xenial
** Tags added: verification-done-artful verification-done-trusty
verification-done-xenial
--
You receiv
** Tags added: id-5ae73e3eeb6dee8e1438bb11
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636
Title:
plymouthd crashed with SIGSEGV in script_obj_deref_direct()
To manage notifications about this
Hello James, or anyone else affected,
Accepted plymouth into trusty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/plymouth/0.8.8-0ubuntu17.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https
** Description changed:
+ [Impact]
+ Plymouth is crashing regularly for users of releases before Ubuntu 18.04. The
crash reporting dialogs must be annoying for those experiencing the crash.
+
+ [Test Case]
+ We have not figured out how to recreate the crash, but the errors bucket
(https://error
** Changed in: plymouth (Ubuntu Trusty)
Assignee: (unassigned) => Brian Murray (brian-murray)
** Changed in: plymouth (Ubuntu Artful)
Assignee: (unassigned) => Brian Murray (brian-murray)
** Changed in: plymouth (Ubuntu Trusty)
Importance: Undecided => High
** Changed in: plymouth (
A variation of this bug, bug1745406, was fixed in Ubuntu 18.04 with
plymouth version 0.9.3-1ubuntu7. That being said this still needs fixing
in every supported release of Ubuntu.
** Changed in: plymouth (Ubuntu)
Status: Triaged => Fix Released
** Changed in: plymouth (Ubuntu)
Assigne
I've been using Brian's PPA test package for almost a week and I haven't
been getting this error anymore.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636
Title:
plymouthd crashed with SIGSEGV i
running unbuntu 18.04 upgraded from 17.10 (do-release-updrade -d)
and it seems that everytime I
sudo apt update, sudo apt upgrade, reboot... I get this error (plymouth)
i am running mythtv frontend, which is set to auto-start after login.
i think i get it every reboot... will reboot to see..
I've uploaded a version of plymouth for bionic to test with to my PPA.
https://launchpad.net/~brian-murray/+archive/ubuntu/ppa
If you'd like it for a different release please let me know.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
It happens randomly few times a week, I'd say once every 4 or 5 reboots
on average. After installing a test package, I could provide a
reasonable feedback with after a few days (maybe a week).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Is this something that happens repeatedly on the same system? I mean if
a test package were provided would someone be able to say that the crash
isn't happening any more for them.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
This error occurred on Ubuntu 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/927636
Title:
plymouthd crashed with SIGSEGV in script_obj_deref_direct()
To manage notifications about this bug go
installing google chrome. then got the bug.
clean installed unbuntu daily bionic Iso, this plymount bug happen just
before the usual update of programs right after it completed.
will be back with the debug file... will uninstall chrome, and then
reinstall it.
--
You received this bug notificati
** Attachment added: "plymouth-debug.log"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/927636/+attachment/5108485/+files/plymouth-debug.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
plymouth-debug.log
** Attachment added: "plymouth-debug.log"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/927636/+attachment/5106113/+files/plymouth-debug.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
It might be helpful to get some plymouth debug log files, you can have
plymouth run in debug mode by adding 'plymouth.debug' to
/etc/default/grub and then running sudo update-grub. Here's what the
correct line in /etc/default/grub might look like.
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash plymouth.
Worked for a couple of iterations but soon went back.
On Sun, Apr 1, 2018 at 7:55 AM bart <927...@bugs.launchpad.net> wrote:
> dpkg-reconfigure plymouth seems to have solved the problem for me
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bu
dpkg-reconfigure plymouth seems to have solved the problem for me
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636
Title:
plymouthd crashed with SIGSEGV in script_obj_deref_direct()
To manage n
Still occurring, even after today's plymouth update (Vanilla Gnome).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636
Title:
plymouthd crashed with SIGSEGV in script_obj_deref_direct()
To manag
Didn't work for me on Bionic. However since this mornings massive update
(Bionic) didn't get it on subsequent reboot. So, keeping fingers crossed ...
On Fri, Mar 23, 2018 at 10:35 AM Milan Jovanovic
wrote:
> I can confirm that after doing dpkg-reconfigure plymouth the issue is
> not appearing (n
I can confirm that after doing dpkg-reconfigure plymouth the issue is
not appearing (no errors showing)
$ apt-cache policy plymouth
plymouth:
Installed: 0.9.3-1ubuntu2
Candidate: 0.9.3-1ubuntu2
Version table:
*** 0.9.3-1ubuntu2 500
500 http://rs.archive.ubuntu.com/ubuntu bioni
$ lsb_release -rd
Description:Ubuntu Bionic Beaver (development branch)
after a bit of reading did a:
dpkg-reconfigure plymouth
have done many reboots no issues
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636
Title:
plymouthd crashed with SIGSEGV in script_obj_der
new install of bionic
Linux steve-nuc 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636
Title:
plymou
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636
Title:
plymouthd crashed with SIGSEGV in script_obj_deref_direct()
To manage notifications about this bug go to:
https://b
On Ubuntu 17.10...
TEST 1 - NO ISSUE:
1. Set onboard graphics as primary in BIOS.
2. Logged into Ubuntu.
3. Everything was fine.
4. Restarted machine.
TEST 2 - ISSUE:
1. Set GeForce GTX 670 in BIOS.
2. Logged into Ubuntu 17.10.
3. Surprisingly, I was given option of "GNOME" or "GNOME Xorg" in G
** Tags added: artful
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636
Title:
plymouthd crashed with SIGSEGV in script_obj_deref_direct()
To manage notifications about this bug go to:
https://b
just inserted an usb pen containing an iso created with startup disk
creator
corrado@corrado-art-gnome:~$ inxi -Fx
System:Host: corrado-art-gnome Kernel: 4.10.0-22-generic x86_64 (64 bit
gcc: 6.3.0)
Desktop: Gnome 3.24.2 (Gtk 3.22.15-0ubuntu1) Distro: Ubuntu Artful
Aardvark (devel
I wasn't willing to chmod 777 anything so I have lived with this bug for
about 4 years... (not my primary machine). Anyway, at some point after
upgrading to 17.04 it seems to have disappeared for me. I am currently
on version 0.9.2-3ubuntu15 of plymouth, and am not seeing the crash
reporter popup f
I have to add the solution in my post #44 seems to work on my desktop,
but not on my laptop: it worked for a while but then the problem
appeared again. Actually, on laptop I had to update /etc/default/grub
adding "noplymouth" in GRUB_CMDLINE_LINUX_DEFAULT options... (which is
of course not a soluti
I also get this error since long time ago, however is not always, it's
just sometimes. When it happens i'm not able to login. After i input
username+pw and click login it gets blocked and I can do nothing but
rebooting the bad way.
In my error report generated by Ubuntu I have the following:
"p
I experienced the same issue, I tried to launch plymouth manually from
an X session:
~$ sudo ./plymouth start
the screen becomes black (with a message at the top about /dev/sda), it
is not possible to interact at all. CTRL-F2 to switch to a console, ps
-ef does not show any plymouth service, how
You should not "sudo chmod -R 777 /sbin/plymouthd".
Doing this to make "never again appear the popup annoying window" is not
good.
This will make the whole machine available for any local user. All of
it. Any file, any device.
--
You received this bug notification because you are a member of Ub
this "sudo chmod -R 777 /sbin/plymouthd" not work with Ubuntu Gnome
16.10... problem still present!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636
Title:
plymouthd crashed with SIGSEGV in scri
Still present in Ubuntu Yakkety (16.10 Beta)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636
Title:
plymouthd crashed with SIGSEGV in script_obj_deref_direct()
To manage notifications about th
** Tags added: rls-y-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636
Title:
plymouthd crashed with SIGSEGV in script_obj_deref_direct()
To manage notifications about this bug go to:
h
I would not recommend making /sbin/plymouthd world-writable.
Someone should fix the actual problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636
Title:
plymouthd crashed with SIGSEGV in scr
i run "sudo chmod -R 777 /sbin/plymouthd" on Ubuntu Gnome 16.04 and
reboot and after that never again appear the popup annoying window for
plymouthd crash. good workaround.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
Just happened to me also on Ubuntu Gnome 16.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636
Title:
plymouthd crashed with SIGSEGV in script_obj_deref_direct()
To manage notifications about
Still happens on 16.04, on multiple machines, all fresh installs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636
Title:
plymouthd crashed with SIGSEGV in script_obj_deref_direct()
To manage n
** Attachment added: "plymouth-debug.log"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/927636/+attachment/4705156/+files/plymouth-debug.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Still happening on Xenial.
The workaround suggested is not valid in xenial anymore.
The suggested directory might now be /usr/lib/x86_64-linux-gnu/plymouth
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
same in xenial GNOME:
corrado@corrado-xenial-gnome:~$ uname -a
Linux corrado-xenial-gnome 4.4.0-8-generic #23-Ubuntu SMP Wed Feb 24 20:45:30
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Seeing this in Xenial
** Tags removed: precise quantal raring saucy
** Tags added: xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636
Title:
plymouthd crashed with SIGSEGV in script_obj_de
fix: chown -R user:user /lib/plymouth
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636
Title:
plymouthd crashed with SIGSEGV in script_obj_deref_direct()
To manage notifications about this bug
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/927636
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Debug log as requested.
** Attachment added: "PlymouthDebug.txt"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/927636/+attachment/4471037/+files/PlymouthDebug.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
Plymouth crashed again with this. Luckily I had debugging on.
Unfortunately, apport gobbled up the log file which you can find here:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1497563
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
is anyone able to get debug logs for this crash?
boot with kernel param: plymouth.debug
then grab /var/log/plymouth-debug.log after reproducing and attach it to this
bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
I get this bug occasionally ever since the new plymouth loading screen
was done for Ubuntu GNOME.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636
Title:
plymouthd crashed with SIGSEGV in script
** Tags added: wily
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636
Title:
plymouthd crashed with SIGSEGV in script_obj_deref_direct()
To manage notifications about this bug go to:
https://bug
The error message from 3.19.0-12 is:
[ 1.6795441 ACPI PCC probe failed
[ 1.713110 tpm_tis 00:03: A TPM error (7) occurred attempting to read a pcr
value
starting version 219
My system is:
Linux adj-HP-Compaq-6910p-GX978UC-ABE 3.19.0-11-lowlatency #11-Ubuntu SMP
PREEMPT Tue Mar 31 22:48:17 UTC
** Tags added: vivid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636
Title:
plymouthd crashed with SIGSEGV in script_obj_deref_direct()
To manage notifications about this bug go to:
https://bu
Occurs at every boot. running 14.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636
Title:
plymouthd crashed with SIGSEGV in script_obj_deref_direct()
To manage notifications about this bug g
I saw this problem consistently on a newly installed 14.04 system with
an SSD. The error went away when I did "chmod 775 /lib/plymouth"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636
Title:
pl
I get the two errors every so often on my Precision M4700 running on SSD
running 14.04.1 (lubuntu or xubuntu - both give the error). Anyone know
how to debug this thing? Can we just get rid of plymouth and the
graphical splash?
--
You received this bug notification because you are a member of Ubu
I would not recommend making /lib/plymouth world-writable.
Someone should fix the actual problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636
Title:
plymouthd crashed with SIGSEGV in scrip
There is NO CRASH at all in my system, except for this annoying crash report
EVERY time that I boot into Ubuntu 14.04
After a few months, I finally decided to look into it because it's getting to
be pretty annoying, I thought it would have been fixed by now.
I will try the:
sudo chmod..
It
Launchpad has imported 1 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=81608.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help
It's estimated to have a moderate impact on a large portion of Ubuntu
users.
** Changed in: plymouth (Ubuntu)
Importance: Medium => High
** Bug watch added: freedesktop.org Bugzilla #81608
https://bugs.freedesktop.org/show_bug.cgi?id=81608
** Also affects: plymouth via
https://bugs.free
This is 14.10:
DISTRIB_DESCRIPTION="Ubuntu Utopic Unicorn (development branch)"
Linux Aspire1 3.15.0-6-generic #11-Ubuntu SMP Thu Jun 12 00:40:00 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
I tried the above chmod from normal command line, didn't work. Now
trying sudo chomd
Let me reboot to s
This is 14.10:
DISTRIB_DESCRIPTION="Ubuntu Utopic Unicorn (development branch)"
Linux Aspire1 3.15.0-6-generic #11-Ubuntu SMP Thu Jun 12 00:40:00 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
I tried the above chmod from normal command line, didn't work. Now
trying sudo chomd
Let me reboot to s
Based on one trial, no plymouthd error this time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636
Title:
plymouthd crashed with SIGSEGV in script_obj_deref_direct()
To manage notifications abo
The workaround which worked for me to get it temporarly fixed is to
change the permission for plymouth as shown below. It may not be secure.
My system is Ubuntu 14.04.
# chmod -R 777 /lib/plymouth
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I am still seeing this on 14.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636
Title:
plymouthd crashed with SIGSEGV in script_obj_deref_direct()
To manage notifications about this bug go to:
thanks for replying...
On 3 April 2014 01:42, wgroiss wrote:
> For me, i didn't really fix it. It was a "1 time-bug". After some other
> updates and reboot, the bug has gone!???
> I had some other troubles with external ppa (e.g. dropbox), but does not
> fit here to this bug description.
>
> --
For me, i didn't really fix it. It was a "1 time-bug". After some other updates
and reboot, the bug has gone!???
I had some other troubles with external ppa (e.g. dropbox), but does not fit
here to this bug description.
--
You received this bug notification because you are a member of Ubuntu
Bu
how did you fix it ??
On 1 April 2014 03:13, wgroiss wrote:
> It happened to me, when i updated from saucy to trusty with "update-
> manager -d".
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1284978).
> https://bugs.launchpad.net/bugs/92763
It happened to me, when i updated from saucy to trusty with "update-
manager -d".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636
Title:
plymouthd crashed with SIGSEGV in script_obj_deref_direc
Randomly segfaults and when it reboots comes up with this error. Happens
roughly every 2-3 hours, can't find a way to reproduce.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636
Title:
plymouthd
I get this on my Ubuntu Studio 14.04 as well now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636
Title:
plymouthd crashed with SIGSEGV in script_obj_deref_direct()
To manage notifications abo
** Tags added: trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636
Title:
plymouthd crashed with SIGSEGV in script_obj_deref_direct()
To manage notifications about this bug go to:
https://b
Now the crash happens in trusty as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636
Title:
plymouthd crashed with SIGSEGV in script_obj_deref_direct()
To manage notifications about this b
** Tags added: bugpattern-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636
Title:
plymouthd crashed with SIGSEGV in script_obj_deref_direct()
To manage notifications about this bug go to
** Tags added: saucy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636
Title:
plymouthd crashed with SIGSEGV in script_obj_deref_direct()
To manage notifications about this bug go to:
https://bu
Yes, this is happening in raring.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636
Title:
plymouthd crashed with SIGSEGV in script_obj_deref_direct()
To manage notifications about this bug go t
** Tags added: raring
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636
Title:
plymouthd crashed with SIGSEGV in script_obj_deref_direct()
To manage notifications about this bug go to:
https://b
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927636
Title:
plymouthd crashed with SIGSEGV in script_obj_deref_direct()
To manage notifications about this bug go to
85 matches
Mail list logo
