Barry, your problem looks like bug #571707.
In my opinion this bug (554737) was solved by Steve PPA and the "slow
disk check" is a different problem, so I'm setting this bug state to
"Fix Released".
** Changed in: plymouth
Status: New => Fix Released
--
ply_boot_client_flush() does not r
On Thu, 2010-04-29 at 04:50 +, Steve Langasek wrote:
> That doesn't sound like this bug, and the behavior you describe is not
> reproducible here. It's possible that fsck is running longer than it
> should due to a backed-up queue of messages being sent to plymouth, but
> this would not be a h
Plymouth is *not* ready. My Dell Mini 9 is essentially unusable (takes over 40
mins to fsck) unless I disable the quiet option at boot.
This is a serious unfixed problem to leave in the final release and is likely
to stop unsophisticated new users dead.
--
ply_boot_client_flush() does not read
I just submitted bug #571707.
--
ply_boot_client_flush() does not read replies (plymouth stuck during/after
filesystem check or error)
https://bugs.launchpad.net/bugs/554737
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
I see this bug is becoming quite confusing and convoluted. Sorry to add
to the noise. I am simply wondering if the behavior described in
comments #73,74 has been reported in a separate bug that I could follow.
I am experiencing the same behavior where the filesystem check no longer
hangs, but slows
... my fstab is as fresh as a just-born baby, same one as I installed at
install time.
We'll see again in some time about plymouth.
I surely hope for Ubuntu that you're right and I'm wrong.
Time will tell.
--
ply_boot_client_flush() does not read replies (plymouth stuck during/after
filesystem
letstrynl,
The issues you are describing are *not* this bug. Please file a new bug
report for the problems you're seeing.
> Why use this crap anyway on server dists?
> We had a good and working server dist before it.
> And who needs fancy splash screens on a server anyway?
The graphical splash
I totally agree, Ingo.
As said before I see the need for hiding all kinds of stuff from the average
user, but there are alternatives for that.
And for desktop startup there can a lot be done there, just by using VESA modes.
As for servers: server dists should become less dependant on hardware.
Wh
> Why use this crap anyway on server dists?
It even does not belong into a desktop release, especially one whith
LTS. This widely untested stuff just for eye-catching belongs into a
development version in early alpha stage. Most of the problems which
still persist till today (release date of Lucid
I've had it with plymouth.
Why use this crap anyway on server dists?
We had a good and working server dist before it.
And who needs fancy splash screens on a server anyway?
Come on Canonical, drop the whole stuff for server.
It's not ready for release yet. And you guys know it.
Debian did the ri
Oh, and just to be complete:
THis happens for me only on 10.04 64-bit server, not on 64-bit desktop.
--
ply_boot_client_flush() does not read replies (plymouth stuck during/after
filesystem check or error)
https://bugs.launchpad.net/bugs/554737
You received this bug notification because you are
Ok, I purged cryptsetup to see if it caused the problems. It doesn't.
I find it *very strange* that you cannot reproduce the error, as it
seems quite simple to reproduce on this side.
With 'quiet splash' on the grub kernel commandline, and 1 ext4 partition to
check at startup I get this problem.
Same problem here since the last Plymouth update; fsck gets to the
fateful 70% mark and then slows to a crawl (though not hanging).
The machine is a Dell Mini 9 with a tiny 32G drive so there is no
possibility that fsck is simply taking the "right" time to finish.
--
ply_boot_client_flush() does
I just waited it out -> 5:30 minutes before having a reachable server.
mountall hasnt finished yet:
root 315 1 2 10:30 ?00:00:07 mountall --daemon
Info for you to reproduce:
/etc/default/cryptdisks:
CRYPTDISKS_ENABLE=No
CRYPTDISKS_MOUNT=""
CRYPTDISKS_CHECK=blkid
CRYPTDISKS_PR
How do you explain the following then?
When I remove 'quiet splash' form the grub kernel commandline, the system boots
up quickly.
No hangs on fsck there.
Otherwise behavior as said. I'll investigate.
--
ply_boot_client_flush() does not read replies (plymouth stuck during/after
filesystem che
> I start up without quiet and splash in grub kernel commandline.
> Otherwise system hangs up to 5 minutes on graphical screen.
> Filesystem check goed up to 71%, then counting up very slowly.
That doesn't sound like this bug, and the behavior you describe is not
reproducible here. It's possible
...Booting with quiet and splash removed allows normal start.
Install is current as of now.
--
ply_boot_client_flush() does not read replies (plymouth stuck during/after
filesystem check or error)
https://bugs.launchpad.net/bugs/554737
You received this bug notification because you are a member
I am currently seeing this on a virtualbox instance. After issuing a
forced fsck it stalls at 70%, creeps slowly up to 74% where it seemingly
stops indefinitely.
--
ply_boot_client_flush() does not read replies (plymouth stuck during/after
filesystem check or error)
https://bugs.launchpad.net/bu
Hey Steve,
After applying last updates, mountall hangs again.
When killing it, terminal becomes unstable.
I start up without quiet and splash in grub kernel commandline.
Otherwise system hangs up to 5 minutes on graphical screen.
Filesystem check goed up to 71%, then counting up very slowly.
Cas
On Tue, 2010-04-27 at 05:40 +, Steve Langasek wrote:
> You're seeing bug #570289, a regression that seems to have been
> introduced in the latest upload. Investigation is ongoing.
By way of information. Dell Inspiron Mini 10v. Lucid updates yesterday
and today.
After updating yesterday, se
chef,
You're seeing bug #570289, a regression that seems to have been
introduced in the latest upload. Investigation is ongoing.
--
ply_boot_client_flush() does not read replies (plymouth stuck during/after
filesystem check or error)
https://bugs.launchpad.net/bugs/554737
You received this bug
Hi, I think I have a similar bug to report. Please let me know if this
bug report is supposed to be elsewhere.
I updated lucid with the latest updates today 26/04/10. Before that, I
was running a vanilla kernel of 2.6.34-rc5 without any custom patches.
This worked well until the upgrade. Now I get
FTR, didn't reproduce the high CPU issue in the last couple of days
anymore
--
ply_boot_client_flush() does not read replies (plymouth stuck during/after
filesystem check or error)
https://bugs.launchpad.net/bugs/554737
You received this bug notification because you are a member of Ubuntu
Bugs,
I did some more testing this morning. I think my trial of "noapic
nolapic noacpi" might have been co-incidental with your last fix. I've
taken them out of grub and the problem has not shown. I created
/forcefsck three times and re-booted since with no sign of the earlier
problem. (Dell Inspiron
I attached a pics of my error
** Also affects: plymouth
Importance: Undecided
Status: New
** Attachment added: "P1070306.JPG"
http://launchpadlibrarian.net/44978286/P1070306.JPG
--
ply_boot_client_flush() does not read replies (plymouth stuck during/after
filesystem check or error
On Tue, Apr 20, 2010 at 11:31:21AM -, Barry Drake wrote:
> Steve Langasek wrote:
> > If that grub setting works for you, then you're seeing a kernel bug
> > that's unrelated to this bug.
> Oh any thoughts on whether or not I ought to file a bug report on
> this? I'm happy to put time i
Steve Langasek wrote:
> If that grub setting works for you, then you're seeing a kernel bug
> that's unrelated to this bug.
>
Oh any thoughts on whether or not I ought to file a bug report on
this? I'm happy to put time in doing tests and reporting, but I'm a bit
lost on kernel and othe
Barry,
If that grub setting works for you, then you're seeing a kernel bug
that's unrelated to this bug.
--
ply_boot_client_flush() does not read replies (plymouth stuck during/after
filesystem check or error)
https://bugs.launchpad.net/bugs/554737
You received this bug notification because you
I have the identical problem on a Dell Inspiron Mini 10v running Lucid
with latest updates. Currently I'm getting round the problem using
GRUB_CMDLINE_LINUX="noapic, nolapic, noacpi" in /etc/default/grub
followed by sudo update-grub. I don't really understand why or how this
is working or what co
Mike,
that issue is not related to this bug.
--
ply_boot_client_flush() does not read replies (plymouth stuck during/after
filesystem check or error)
https://bugs.launchpad.net/bugs/554737
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
this fixed is not work for me.
I got the "mountall : plymount command failed " still
and htere is no splash show.
the plymouth version is : 0,8.2-2
and here is the boot.log
** Attachment added: "boot.log"
http://launchpadlibrarian.net/44572522/boot.log
--
ply_boot_client_flush() does not r
I've reported an independent bug here,
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/564434
--
ply_boot_client_flush() does not read replies (plymouth stuck during/after
filesystem check or error)
https://bugs.launchpad.net/bugs/554737
You received this bug notification because you ar
This bug is fixed. Your request to not show the message when no drives
need to be checked is a separate issue that you should file as a report
against the mountall package.
** Changed in: plymouth (Ubuntu Lucid)
Status: Confirmed => Fix Released
--
ply_boot_client_flush() does not read r
if the new package does not fix the problem there is no reason to mark
it as fixed.
and it seems it doesnt fix the issue
On Thu, 2010-04-15 at 18:55 +, Savvas Radevic wrote:
> > Marking it as a confirmed with the assumption that a fix to this bug has
> > caused the new behavior.
>
> The new
> Marking it as a confirmed with the assumption that a fix to this bug has
> caused the new behavior.
The new package is a new upstream release - I think it's better to
leave it as "Fix released" and report a new bug report against the new
package version (include a link to this bug and mention a
Marking it as a confirmed with the assumption that a fix to this bug has
caused the new behavior. If some of the maintainers confirm that it is
a totally independent regression, I'm ready to raise a separate bug.
--
ply_boot_client_flush() does not read replies (plymouth stuck during/after
file
Savvas. I face the same behavior too. If there nothing to check the
message should not be displayed at all. If there is some check
happening and the drives found to be OK, why is the check being
performed for each boot in the first place?
** Changed in: plymouth (Ubuntu Lucid)
Status: Fi
> But no checks seems to be performed: there is no information about the
> progress and the system boots very fast.
I don't think it's a bug -- probably there is nothing to check and the
drives are OK? :)
--
ply_boot_client_flush() does not read replies (plymouth stuck during/after
filesystem c
The root cause of all that trouble is plymouth!
See here: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/556372
how to get rid of it.
--
ply_boot_client_flush() does not read replies (plymouth stuck during/after
filesystem check or error)
https://bugs.launchpad.net/bugs/554737
You rece
With the PPA version I'm always getting the message: Your drives are
beign checked for errors, this may take some time. Press C to cancel all
checks currently in progress.
But no checks seems to be performed: there is no information about the
progress and the system boots very fast. I've restarted
This bug was fixed in the package plymouth - 0.8.2-1
---
plymouth (0.8.2-1) lucid; urgency=low
[ Steve Langasek ]
* New upstream release.
* debian/plymouth.plymouth-stop.upstart: trust the new kdm to stop plymouth
for us, too. LP: #540177.
* plymouth needs to depend on in
Downloaded new plymouth from the vorlon ppa and did the "sudo touch /forcefsck"
test.
Plymouth gets to "1 of 2 partitions, at 72%." then the screen blacks out for 5
seconds. then GDM login appears. I logged in and checked / - the forcefsck
file is gone.
--
ply_boot_client_flush() does not rea
im still getting this bug
--
ply_boot_client_flush() does not read replies (plymouth stuck during/after
filesystem check or error)
https://bugs.launchpad.net/bugs/554737
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
Steve Langasek, you said:
"mountall interprets /forcefsck as "force check of all filesystems", so this is
expected behavior."
In that case there is another bug for mountall to be reported:
/forcefsck shoud respect the figure in column 6 of /etc/fstab and not just
checkk all.
is correct!
--
pl
Steve Langasek, you said:
"mountall interprets /forcefsck as "force check of all filesystems", so this is
expected behavior."
In that case there is another bug for mountall to be reported:
/forcefsck shoud respect the figure in column 6 of /etc/fstab and not just
checkk all.
--
ply_boot_client
If you have fixed that issue, please also correct dependencies of packet
'plymouth'.
Trying to remove it with apt-get will de-install almost the whole system
- which definitely is not required!
--
ply_boot_client_flush() does not read replies (plymouth stuck during/after
filesystem check or err
Mathew Cairns,
mountall running and chewing CPU after plymouth has exited is not the
same bug.
Jorge Suárez,
mountall interprets /forcefsck as "force check of all filesystems", so
this is expected behavior.
** Changed in: plymouth (Ubuntu Lucid)
Status: Triaged => Fix Committed
--
ply
As for why /forcefsck is not removed:
that file is not removed by fsck, instead the mountall init script
contains:
post-stop script
rm -f /forcefsck 2>dev/null || true
end script
which will delete the file after all checks have been done and all
filesystems are mounted. So unless mountall st
Ah, so if you can't login /forcefsck is not removed - that's really odd.
So to get rid of all that trouble, I have renamed '/sbin/plymouthd' and
all is fine here as well. No more hangs with black screen. To see the
boot-messages I already reverted to good old grub-legacy.
Unfortunately there is n
Yes, Directly after login de /forcefsck file is there, and it vanished a
minute later...
--
ply_boot_client_flush() does not read replies (plymouth stuck during/after
filesystem check or error)
https://bugs.launchpad.net/bugs/554737
You received this bug notification because you are a member of
An it is Ubuntu-specific:
Debian Squeeze performs fsck correctly and removes /forcefsck
Also happens on Lucid with grub-legacy instead of grub2, no matter whether ext3
or ext4 filesystem!
--
ply_boot_client_flush() does not read replies (plymouth stuck during/after
filesystem check or error)
h
ingo, I noticed that the file /forcefsck was not deleted too after
starting the session, but it was gone after a while (less than a
minute). Perhaps the file is deleted at some more advanced stage (some
boot process that's still in the background after the session has
already been started?). Chan y
Thanx for the efforts!
did a sudo touch /forcefsck and restarted witout the splash option; everything
seemed to work and the /forcefsck was removed
did a second test with different results
did a sudo touch /forcefsck, and restarted with splash
GDM is shown when Plymouth still says 1 of 2 partitio
It works for me also, but I notice some small problems also.
1. I create /forcefsck file in order to force the disk check during the next
boot.
2. Reboot the laptop.
3. The disk check complete too fast in order to see the proper 100% count. I
see about 90%+ or something like that.
4. The gdm star
Checked again:
fsck is definitely not finished: file /forcefsck is not erased!
So it is not just killing plymouth, start-up procedure is faulty. See also this
bug report:
https://bugs.launchpad.net/bugs/538810
and
https://bugs.launchpad.net/bugs/554079
--
ply_boot_client_flush() does not read
Here still al the same:
with latest Lucid-amd64 updates things did not cange in any way: boot process
hangs at 70%
(initziated by 'touch /forcefsck')
--
ply_boot_client_flush() does not read replies (plymouth stuck during/after
filesystem check or error)
https://bugs.launchpad.net/bugs/554737
It works with two minor problems.
First the %completion goes up to ~80% and then sticks there for ~5-6
second until gdm shows.
Second on vt1 I see a lot (many tens-few hundreds) of "mountall:
Plymouth command failed" messages.
--
ply_boot_client_flush() does not read replies (plymouth stuck dur
The updated plymouth packages solved it for me.
Disk check completes normally in splash screen, after that -> tty.
As expected.
Great work, Steve.
--
ply_boot_client_flush() does not read replies (plymouth stuck during/after
filesystem check or error)
https://bugs.launchpad.net/bugs/554737
You
It worked for me as well, thank you!
At least it boots, but there still some remaining issues:
* I created a file named /forcefsck so only the / should be checked, isn't it?
But Plymouth says 1 of 1 partitions, then 1 of 2, 1 of 3 and 1 of 4. (I suppose
these additional partitions are /var, /tm
The problem still exists for me. However, in my case, no plymouth
processes were present after booting, even though mountall failed to
terminate (see comment 23 above). The only difference I have observed
is that KDM is running on a different console.
Booting the 2.6.32-20 kernel with 'nosplash'
These new versions fix it for me. I don't see any new problems after a
quick restart and hibernate test round.
--
ply_boot_client_flush() does not read replies (plymouth stuck during/after
filesystem check or error)
https://bugs.launchpad.net/bugs/554737
You received this bug notification becaus
Could those experiencing this issue please run 'sudo add-apt-repository
ppa:vorlon/ppa' and install the new version of plymouth from there, and
let us know if this fixes the problem or causes any new ones?
--
ply_boot_client_flush() does not read replies (plymouth stuck during/after
filesystem c
This affected me for the first time today - fsck and plymouth froze at
93% checking disk 1 of 1 - fully updated Lucid Beta 2 - kernel
2.6.32-20.
--
ply_boot_client_flush() does not read replies (plymouth stuck during/after
filesystem check or error)
https://bugs.launchpad.net/bugs/554737
You rec
** Branch linked: lp:ubuntu/plymouth
--
ply_boot_client_flush() does not read replies (plymouth stuck during/after
filesystem check or error)
https://bugs.launchpad.net/bugs/554737
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
There is also a possible additional duplicate of this, as bug #559761.
In that case, the mountall process remains after boot, using 100% CPU
time. However, there are no plymouth processes running at the time. I
have attached a backtrace of the mountall process to comment 8 of that
bug.
--
ply_b
The distinguishing marker for this bug is the backtraces of the
plymouthd and mountall processes. If someone wants to grab that
information from the submitters of bug #554079 and duplicates, that's
fine; otherwise that bug can be revisited and confirmed as a duplicate
after we have this one fixed.
Perhaps 554079 should be moved/merged to this bug? Please see my comment:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/554079/comments/53
I ssh'ed into the machine, killed plymouthd (after all disk activity stopped),
and gdm comes up and I could then continue to login w/o issue.
--
pl
** Changed in: plymouth (Ubuntu Lucid)
Assignee: Scott James Remnant (scott) => Steve Langasek (vorlon)
--
ply_boot_client_flush() does not read replies (plymouth stuck during/after
filesystem check or error)
https://bugs.launchpad.net/bugs/554737
You received this bug notification because
This is probably the same as bug #554079
--
ply_boot_client_flush() does not read replies (plymouth stuck during/after
filesystem check or error)
https://bugs.launchpad.net/bugs/554737
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: plymouth (Ubuntu Lucid)
Milestone: None => ubuntu-10.04
--
ply_boot_client_flush() does not read replies (plymouth stuck during/after
filesystem check or error)
https://bugs.launchpad.net/bugs/554737
You received this bug notification because you are a member of Ubuntu
Bugs, w
70 matches
Mail list logo
