** Changed in: sysvinit (Ubuntu Lucid)
Status: Fix Released = Fix Committed
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - Please no more
confirmations/comments
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member of
** Changed in: sysvinit (Ubuntu Lucid)
Status: Fix Committed = Fix Released
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - Please no more
confirmations/comments
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member of
** Changed in: sysvinit (Ubuntu)
Status: Fix Released = Fix Committed
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - Please no more
confirmations/comments
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member of Ubuntu
** Changed in: sysvinit (Ubuntu)
Status: Fix Committed = Fix Released
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - Please no more
confirmations/comments
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member of Ubuntu
** Changed in: sysvinit (Ubuntu Lucid)
Status: Fix Released = Fix Committed
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - Please no more
confirmations/comments
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member of
** Changed in: sysvinit (Ubuntu Lucid)
Status: Fix Committed = Fix Released
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - Please no more
confirmations/comments
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member of
** Changed in: sysvinit (Ubuntu Lucid)
Status: Fix Released = Fix Committed
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - Please no more
confirmations/comments
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member of
** Changed in: sysvinit (Ubuntu Lucid)
Status: Fix Committed = Fix Released
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - Please no more
confirmations/comments
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member of
** Changed in: sysvinit (Ubuntu Lucid)
Status: Fix ** = Fix **
Could you please stop messing around...?
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - Please no more
confirmations/comments
https://bugs.launchpad.net/bugs/537262
You received this bug notification
** Visibility changed to: Private
** This bug has been flagged as a security vulnerability
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - Please no more
confirmations/comments
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member
** Visibility changed to: Public
** This bug is no longer flagged as a security vulnerability
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - Please no more
confirmations/comments
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a
I can't provide much information other than to express my extreme
frustration with the nVidia drivers and/or inability to retain screen
resolutions in karmic and lucid beta 1. Six weeks ago this was not a
problem. Now it is a problem.
Recently I have been able to manually set the resolution to
** Package changed: plymouth (Ubuntu Lucid) = sysvinit (Ubuntu Lucid)
** Changed in: sysvinit (Ubuntu Lucid)
Assignee: Scott James Remnant (scott) = Steve Langasek (vorlon)
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - Please no more
confirmations/comments
This bug was fixed in the package sysvinit - 2.87dsf-4ubuntu17
---
sysvinit (2.87dsf-4ubuntu17) lucid; urgency=low
* debian/initscripts/etc/init.d/sendsigs: additional upstart jobs may be
/started/ on shutdown after this script has first been invoked; so don't
assume the
** Changed in: apport (Ubuntu Lucid)
Status: Fix Committed = Fix Released
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - Please no more
confirmations/comments
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member of Ubuntu
** Visibility changed to: Private
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - Please no more
confirmations/comments
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
** Visibility changed to: Public
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - Please no more
confirmations/comments
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
** Changed in: apport (Ubuntu Lucid)
Status: Fix Released = In Progress
** Changed in: apport (Ubuntu Lucid)
Status: In Progress = Fix Committed
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - Please no more
confirmations/comments
** Changed in: apport (Ubuntu Lucid)
Status: Fix Released = Fix Committed
** Changed in: apport (Ubuntu Lucid)
Status: Fix Committed = Fix Released
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - Please no more
confirmations/comments
When is the fix going to be released? I'm still running plymouth
0.8.0~-17 here. I just updated. Oddly enough, on my Desktop, directly
connected to the internet via an ethernet cable, with an Ati video card,
I don't have this problem. I only have it with my Lenovo G530 with a
Broadcom bcm4312 rev
On Wed, Mar 24, 2010 at 09:56:00PM -, bobbyjean58 wrote:
When is the fix going to be released?
After we've figured out what's causing it - which we haven't yet.
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - Please no more
confirmations/comments
I don't know exact why but plymouthd has stopped crashing on me. No
crash reports in /var/crash...nothing. And this is with multiple
reboots, too. I'm sure it has nothing to do with it but the only thing I
did differently after the first crash, following an update and reboot,
is I reinstalled
** Changed in: apport (Ubuntu Lucid)
Status: Fix Released = Fix Committed
** Changed in: apport (Ubuntu Lucid)
Status: Fix Committed = Fix Released
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - Please no more
confirmations/comments
how can this be fixed
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - Please no more
confirmations/comments
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs
** Changed in: apport (Ubuntu Lucid)
Status: Fix Released = Fix Committed
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - Please no more
confirmations/comments
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member of Ubuntu
** Changed in: apport (Ubuntu Lucid)
Status: Fix Committed = Fix Released
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - Please no more
confirmations/comments
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member of Ubuntu
** Changed in: plymouth
Status: Invalid = Incomplete
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - Please no more
confirmations/comments
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
** Changed in: plymouth
Status: Incomplete = Invalid
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - Please no more
confirmations/comments
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
yeah, I get the same bug report popping up still. Can't release this to the
commons with it popping up crash reports. Sorry.
If anyone needs/wants anymore information, please ask, and instruct!
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - Please no more
Not sure what fixed it, but after todays updates I no longer get the crash
notification. Note: it had crashed just prior to the updates. Following updates
I shut down, restarted, and no further crashes or reports in /var/crash Latest
updates today:
Commit Log for Mon Mar 22 16:15:38 2010
** Changed in: plymouth
Assignee: (unassigned) = Martin Pitt (pitti)
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - Please no more
confirmations/comments
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member of Ubuntu
Bugs,
Hi, there
Apport brought me here. Got this bug today after a reboot
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - PLEASE NO MORE
CONFIRMATIONS/COMMENTS
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member of Ubuntu
Bugs,
Hi, there
Apport came up again after download the newest fixes and reboot.
Lucid 32-bit on a Dell Optiplex dual PentiumD with 3GB Ram.
There seems nothing fixed...
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - PLEASE NO MORE
CONFIRMATIONS/COMMENTS
open or close I am not shure but maybe it is related on KMS on wich it
is supposed to work ... becouse KMS isnt working quite well on my
laptop... there are strange interfirances seen on my screen ... some
white lines are going up and down on my screen ... so Bug Description
maybe you dont know
GUYS, IN ORDER 2 FIX THE PROBLEM: YOU NEED 2 INSTALL BETA 1 AS A CLEAN
INSTALL! UPGRADING FROM A3 WILL NOT FIX YOUR PROBLEMS WITH IT!
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - PLEASE NO MORE
CONFIRMATIONS/COMMENTS
https://bugs.launchpad.net/bugs/537262
You received this
I installed Beta1 and got the bug again.
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - PLEASE NO MORE
CONFIRMATIONS/COMMENTS
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
Kevin,
So you are saying there is no upgrade path from Lucid alpha 3 to a set
up that works? Is the same true for people on Karminc, that there is no
upgrade path to a working system?
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - PLEASE NO MORE
CONFIRMATIONS/COMMENTS
RUSS: WHAT I AM SAYING IS THAT THE BUG IS FIXED WHEN YOU DO A CLEAN
INSTALL OF BETA 1! I VERIFYED THIS ON 2 DIFFERENT PC'S!
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - PLEASE NO MORE
CONFIRMATIONS/COMMENTS
https://bugs.launchpad.net/bugs/537262
You received this bug
Kevin,
That is great for people installing afresh, but this still leaves the
question of how to correct the problem for people who are upgrading.
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - PLEASE NO MORE
CONFIRMATIONS/COMMENTS
https://bugs.launchpad.net/bugs/537262
You
No, this also exists on clean install of beta1. and please read the bug
description again. It says no more comments.
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - PLEASE NO MORE
CONFIRMATIONS/COMMENTS
https://bugs.launchpad.net/bugs/537262
You received this bug notification
This bug is still open. That means the problem still exists, and we just
need to wait for it to get fixed. People who upgrade will be covered by
the fix, which is expected to be available before the release of beta 2
in a few weeks.
--
plymouth pid missing from OMITPIDS and terminated by
Assus EEEPC 1201HA
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - PLEASE NO MORE
CONFIRMATIONS/COMMENTS
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing
On Sun, Mar 21, 2010 at 02:46:17PM -, Kevin John Panzke wrote:
GUYS, IN ORDER 2 FIX THE PROBLEM: YOU NEED 2 INSTALL BETA 1 AS A CLEAN
INSTALL! UPGRADING FROM A3 WILL NOT FIX YOUR PROBLEMS WITH IT!
No. This bug is still outstanding.
--
Steve Langasek Give me a lever long
@Kevin John Panzke: Please write in lower case. Comments in all caps are
considered as shouting, which is against our Code of Conduct.
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - PLEASE NO MORE
CONFIRMATIONS/COMMENTS
https://bugs.launchpad.net/bugs/537262
You received
Just crashed in Beta 1, installed cleanly just yesterday and all updates
applied. I had just installed GRUB 1 so I could use grub-choose-default
on a dual boot system (apparently it doesn't work with GRUB 2). Anyway,
this occurred trying to run gksu grub-choose-default and just after
entering my
Sorry, didn't see the NO MORE COMMENTS. But since apport sends you
here by default, isn't it a bit unrealistic to shout in the heading like
that?
This is understandably frustrating from the maintainers point of view.
It is equally disconcerting to get this kind of reception when this is
the first
Sorry to disappoint, but I have just finished installing a clean
installation of the 9.10 and the do-release-upgrade -d also fails
I mean, it works, but I keep getting the bug report to send via apport
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - PLEASE NO MORE
** Summary changed:
- plymouth pid missing from OMITPIDS and terminated by sendsigs - PLEASE NO
MORE CONFIRMATIONS/COMMENTS
+ plymouth pid missing from OMITPIDS and terminated by sendsigs - Please no
more confirmations/comments
--
plymouth pid missing from OMITPIDS and terminated by sendsigs
Affects me too, this bug appeared after updates been installed and a PC
was restarted.
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - PLEASE NO MORE
CONFIRMATIONS/COMMENTS
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member of
The 3-19 request asks for no more comments, yet on 3-20 post fixes, this
issue is still occurring.
Reboot following updates as of this time stamp on an amd64 nvidia system still
shows broken pipes when shutting down and on the reboot as well as this fixed
aport crasher. Just fyi.
--
plymouth
Still receiving plymouthd crash on reboot with update 17. Here's a partial
syslog snippet
*
Mar 20 22:26:08 lucid-test NetworkManager: info (eth1): supplicant interface
state: starting - ready
Mar 20 22:26:09 lucid-test init: plymouth main process (340) killed by USR2
signal
Mar 20 22:26:09
I know it would be somewhat radical, but perhaps a Launchpad policy
allowing deletion of comments under certain circumstances would be in
order? In this and some other bugs, the large number of me too
comments make it very difficult for someone trying to extract useful
information by reading
Hy!
I made a blueprint for launchpad based on Michael's idea.
https://blueprints.launchpad.net/launchpad/+spec/comment-rating
Sorry for being off-topic!
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - PLEASE NO MORE
CONFIRMATIONS/COMMENTS
man - you have to understand - they report to developers after each
Plymouth upgrade because developers need feedback - also there is an
automated crash report tool.
if developers don't need this information again then they can update
crash reporting tool to be insensitive to this err. message.
[OFFTOPIC]
Martin Pitt:
** Summary changed:
- plymouth pid missing from OMITPIDS and terminated by sendsigs
+ plymouth pid missing from OMITPIDS and terminated by sendsigs - PLEASE NO
MORE CONFIRMATIONS/COMMENTS
What's this? As I can understand, it's meaning THAT NO MORE COMMENTS AT ALL. Am
On Fri, Mar 19, 2010 at 09:56:29AM -, Nemes Ioan Sorin wrote:
man - you have to understand - they report to developers after each
Plymouth upgrade because developers need feedback
No, this is not feedback that we need. That's why the developers have
updated the title of this bug asking
** Changed in: apport (Ubuntu Lucid)
Status: Fix Released = Fix Committed
** Changed in: apport (Ubuntu Lucid)
Status: Fix Committed = Fix Released
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - PLEASE NO MORE
CONFIRMATIONS/COMMENTS
** Changed in: plymouth (Ubuntu Lucid)
Status: Confirmed = Fix Released
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - PLEASE NO MORE
CONFIRMATIONS/COMMENTS
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member of Ubuntu
** Changed in: plymouth (Ubuntu Lucid)
Status: Fix Released = Confirmed
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - PLEASE NO MORE
CONFIRMATIONS/COMMENTS
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member of Ubuntu
the same problem with me
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - PLEASE NO MORE
CONFIRMATIONS/COMMENTS
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs
Today is my notebook installed ubuntu 10:04 Beta 1 with 64 bits, also update
with complete and restarted. Started ubuntu normally.
When I turn on the wireless icon then appears with the star mark (apport) (it
is near the clock).
This is normal?
Thanks
--
plymouth pid missing from OMITPIDS and
** Changed in: plymouth (Ubuntu Lucid)
Assignee: Scott James Remnant (scott) = Zachary Parker (zparker31)
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - PLEASE NO MORE
CONFIRMATIONS/COMMENTS
https://bugs.launchpad.net/bugs/537262
You received this bug notification
** Changed in: plymouth (Ubuntu Lucid)
Assignee: Zachary Parker (zparker31) = Scott James Remnant (scott)
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - PLEASE NO MORE
CONFIRMATIONS/COMMENTS
https://bugs.launchpad.net/bugs/537262
You received this bug notification
I having this on 32bit pae just rebooted fresh, got this while running
the Ubuntu store and installing some software.
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - PLEASE NO MORE
CONFIRMATIONS/COMMENTS
https://bugs.launchpad.net/bugs/537262
You received this bug
I'm still receiving a plymouthd crash report.
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - PLEASE NO MORE
CONFIRMATIONS/COMMENTS
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
I have this plymouthd crash report when on purpose of test i run
Hardware drivers utility
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - PLEASE NO MORE
CONFIRMATIONS/COMMENTS
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member
I' m on a 10.4 LTS AMD64 daily build in VirtualBox i run on purpose
Hardware Drivers utility to test and i get plymouth's crash report
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - PLEASE NO MORE
CONFIRMATIONS/COMMENTS
https://bugs.launchpad.net/bugs/537262
You received
yep, i'm up-to-date as of the 19th of March AEST (18th of March for the rest of
you on the slow end of the world ;) )
and I still get this plymouthd crash report every time I boot to desktop.
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - PLEASE NO MORE
Listen, people. The devs know there is a problem. It is set for High
Priority, and is due to be fixed by Beta2. Please stop yep me tooing
on here please. They'll fix it. Stay calm. Take a deep breath, and just
wait. No more comments.
--
plymouth pid missing from OMITPIDS and terminated by
After the update today 0.8.0~-17 I am still getting the crash report.
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - PLEASE NO MORE
CONFIRMATIONS/COMMENTS
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member of Ubuntu
Bugs, which
just updated march 18th 0100 @ gmt -5, error report still occurs :(
sorry.
I dont seem to be having any actual problems though, certainly not
hangs/crashes.
--
plymouth pid missing from OMITPIDS and terminated by sendsigs
https://bugs.launchpad.net/bugs/537262
You received this bug notification
me2 and im running an Acer Aspire 5720z after start-up this message is
shown through Apport, and I installed 10.04 yesterday, from 9.10, all
went normal, was playing a game, lol, saw the apport...system still
running normal
--
plymouth pid missing from OMITPIDS and terminated by sendsigs
Updated at 2010-03-18 06:20+00:00 on 64-bit workstation Ubuntu and
rebooted and the plymouthd failure still occurs. Desktop comes up fine
but there is an immediate crash report for plymouthd that points to this
bug report.
--
plymouth pid missing from OMITPIDS and terminated by sendsigs
it rebooted once fine here, 64 bits ubuntu too, upgraded from 9.10 .
Succesfull rebooting seems an art(worked fine after first reboot, after
that it was tricky business)
--
plymouth pid missing from OMITPIDS and terminated by sendsigs
https://bugs.launchpad.net/bugs/537262
You received this bug
Updated at 2010-03-18 09:00 (GMT+1), there was some plymouth package
updates
No more plymouth errors at startup.
I guess it is fixed in my case (upgraded 9.10 to 10.04, 64bits version)
--
plymouth pid missing from OMITPIDS and terminated by sendsigs
https://bugs.launchpad.net/bugs/537262
You
** Description changed:
You've been asked to file a bug because Plymouth didn't terminate on
shutdown?
Sorry, but actually this isn't a bug in Plymouth - it's a bug in the
script that's telling you it's a bug ;-)
- I'm leaving this one open because otherwise I'll just get a zillion
The problem is still here on my Amilo Li 3710 laptop (upgraded from
9.10).
--
plymouth pid missing from OMITPIDS and terminated by sendsigs
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
with plymouth update 17 nvidia 8600GT apport reported crash for
plymouthd at startup.
--
plymouth pid missing from OMITPIDS and terminated by sendsigs
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
** Changed in: apport (Ubuntu Lucid)
Status: Fix Released = Fix Committed
--
plymouth pid missing from OMITPIDS and terminated by sendsigs
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
** Changed in: apport (Ubuntu Lucid)
Status: Fix Committed = Fix Released
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - PLEASE NO MORE
CONFIRMATIONS/COMMENTS
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member of Ubuntu
** Summary changed:
- plymouth pid missing from OMITPIDS and terminated by sendsigs
+ plymouth pid missing from OMITPIDS and terminated by sendsigs - PLEASE NO
MORE CONFIRMATIONS/COMMENTS
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - PLEASE NO MORE
CONFIRMATIONS/COMMENTS
No more crash reports after update, but plymouthd still seems to fall
back to text (Ubuntu and four dots) mode on my GeForce 9500 GT. Current
version of NVidia drivers is installed and working.
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - PLEASE NO MORE
same as Shadow Panther - plymounth crash no more - but after Ubuntu
points I got the command line login
after sudo reboot - Ubuntu boot normally
2010/3/18 Shadow Panther panther...@gmail.com:
No more crash reports after update, but plymouthd still seems to fall
back to text (Ubuntu and four
With plymouth update 17 I'm still receiving a plymouthd crash report.
This is on a Lenovo G530 laptop with an Intel graphics card and
components. Has a Pentium dual core processor. Just as a side note, if
you remove plymouth the crash reports no longer occur;). Not to
worry though, I reapplied
This happens to me when my laptop is docked (lid closed). Dell Latitude
D630 64 bit.
--
plymouth pid missing from OMITPIDS and terminated by sendsigs - PLEASE NO MORE
CONFIRMATIONS/COMMENTS
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member of
Apport still reports the bug automatically. This still occurs after the
updates released today, March 17, 2010.
--
plymouth pid missing from OMITPIDS and terminated by sendsigs
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member of Ubuntu
Bugs,
yep, still getting it after todays plymouth update
--
plymouth pid missing from OMITPIDS and terminated by sendsigs
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
** Changed in: plymouth (Ubuntu Lucid)
Milestone: ubuntu-10.04-beta-1 = ubuntu-10.04-beta-2
--
plymouth pid missing from OMITPIDS and terminated by sendsigs
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
I am still getting it after today's plymouth update.
--
plymouth pid missing from OMITPIDS and terminated by sendsigs
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
** Changed in: plymouth (Ubuntu Lucid)
Status: Confirmed = Fix Committed
** Changed in: plymouth (Ubuntu Lucid)
Status: Fix Committed = Confirmed
--
plymouth pid missing from OMITPIDS and terminated by sendsigs
https://bugs.launchpad.net/bugs/537262
You received this bug
I couldn't boot my system normally, so I used a live USB opened a terminal and
typed 'sudo fdisk-l' to make sure which device boot to fix. Then run a file
system check on my hard drive 'sudo fsck /dev/sda1'
Now I'll wait for the bug fix.
--
plymouth pid missing from OMITPIDS and terminated by
get plymouth update 16, randomly my system no boot, or crash.
--
plymouth pid missing from OMITPIDS and terminated by sendsigs
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs
my system boot normally 2 or 3 times and then boot on command line
so 3 to 1
after a command line boot sudo reboot solve the problem next reboot
will boot normally in graphic mode.
2010/3/17 LordStenka lordste...@gmail.com:
get plymouth update 16, randomly my system no boot, or crash.
--
Even after getting plymouth update 16 I'm still receiving a plymouthd
crash report. I had my fingers crossed as it booted up but no such luck
this go around, I suppose. Hopefully, the Devs will get it sorted out by
tomorrow with the release of beta 1. Thanks for your efforts, Devs.
Mucho
This affects me, too.
Since this problem my computer no longer starts correctly when I start
it the first time a day.
The Computer initially starts normal but then it just shows Ubuntu
10.4 for ages.
Only when I unplug it and plug it again it starts correctly.
--
plymouth pid missing from
On Wed, Mar 17, 2010 at 09:37:23PM -, Nichtschlau wrote:
This affects me, too.
Since this problem my computer no longer starts correctly when I start
it the first time a day.
The Computer initially starts normal but then it just shows Ubuntu
10.4 for ages.
Only when I unplug it and
Im in 10.04 Alpha 3, 64-bit.
--
plymouth pid missing from OMITPIDS and terminated by sendsigs
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
bug's still there :(
--
plymouth pid missing from OMITPIDS and terminated by sendsigs
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Yes, we know, that's why the task on the plymouth package is still open.
It's not necessary to comment on the bug just to say this
--
plymouth pid missing from OMITPIDS and terminated by sendsigs
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member
There are they.
** Attachment added: syslog.2.gz, syslog.1 and syslog
http://launchpadlibrarian.net/40993774/syslogs.tar.gz
--
plymouth pid missing from OMITPIDS and terminated by sendsigs
https://bugs.launchpad.net/bugs/537262
You received this bug notification because you are a member of
1 - 100 of 152 matches
Mail list logo
