On Sun, Oct 30, 2011 at 06:49:14PM -, ingo wrote:
Steve Langasek (vorlon) wrote on 2011-10-25:
And there are a number of other plymouth bugs present that are higher-impact
than this one, so it is unlikely that this bug will receive further
attention for 10.04.
That's true for sure.
On 25/10/2011 21:31, queo wrote:
Please, are there any updates on this issue?
The bug is open since 2010-04-29!
I'm using Linux Mint Isadora 64bit and 32bit, both are having the same bugs.
Please update the Status to Won't fix!!!
But it's fixed in Ubuntu Oneiric.
--
Kind regards,
Loong
25.10.2011 18:38, Chow Loong Jin wrote:
But it's fixed in Ubuntu Oneiric.
And what does it change with regards to Linux Mint 9 Isadora users? Who cares if
this bug was fixed in some fresh-n-shiny Ubuntu and/or Mint release while it is
still not fixed in so-called Long Term Support version of
On 25/10/2011 22:59, queo wrote:
Dear Loong Jin,
thanks for your reply.
I always thought there is a support for 3 years for LTS releases (Ubuntu
10.04 is LTS).
Do I have the wrong information here?
Best regards,
Kurt
Sorry, let me correct myself. It's been fixed from lucid-updates
On Tue, Oct 25, 2011 at 05:42:18PM -, Chow Loong Jin wrote:
The status of the bug is correct -- it's fixed in mountall on Ubuntu, and
mountall in Lucid (via lucid-updates). If it's still broken in Linux Mint,
then
open a task there and set it to the appropriate status. There is no reason
Oddly this was fixed in Ubuntu 10.4.2 and its sub-sequent releases. Mint
maintains that the bug lies upstream. Oh wth I'm using LMDE now
On Wed, Aug 24, 2011 at 3:34 PM, queo 571...@bugs.launchpad.net wrote:
this fix doesn't work
--
You received this bug notification because you are
On 22.08.2011 17:31, queo wrote:
Is there any help available regarding this bug please??
It is open since 2010-04-29 (!)
Here: http://www.debian.org/devel/debian-installer/ - works reliably.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Excerpts from ingo's message of Mon Aug 22 16:07:50 UTC 2011:
On 22.08.2011 17:31, queo wrote:
Is there any help available regarding this bug please??
It is open since 2010-04-29 (!)
Here: http://www.debian.org/devel/debian-installer/ - works reliably.
Bug reports are for helping
Well pardon me. I'm sorry for the wrong info. I just know what took place on
my system. So until you have walked in my shoes, you need to keep your
attitude and that I know all bull crap to yourself. So cancel my account,
who really cares. Its just a linux distro, life still goes on.
On Nov 14,
On Tuesday 16,November,2010 12:17 AM, Richard Postlewait wrote:
Well pardon me. I'm sorry for the wrong info. I just know what took place on
my system. So until you have walked in my shoes, you need to keep your
attitude and that I know all bull crap to yourself. So cancel my account,
who
16.11.2010 00:25, ingo wrote:
The logical way to solve this issues/bugs would
be to purge plymouth and set up a good functional system.
Correct me if I'm wrong but it is perfectly possible to get rid of plymouth in
initramfs and following boot process by simply not installing plymouth themes
It's fixed in Mint 10.
On Sun, Nov 14, 2010 at 8:45 AM, Andreas Jürgens
571...@bugs.launchpad.netwrote:
Hello,
this Bug is nearly 7 month old and I can't understand, why it is not
fixed for LM 9.
Regards
Andreas
--
fsck progress stalls at boot, plymouthd/mountall eats CPU
I can't answer that one; sorry. I just know it's fixed inMint 10, cause it
came up on my system the other day, took like maybe 3 to 5 minutes at the
most. Then it finished booting. I tried Ubuntu 10.10, before Mint 10 RC came
out. If I'm not mistaken Ubuntu still has the same problem.lol Mint's
On Monday 15,November,2010 01:38 AM, Richard Postlewait wrote:
I can't answer that one; sorry. I just know it's fixed inMint 10, cause it
came up on my system the other day, took like maybe 3 to 5 minutes at the
most. Then it finished booting. I tried Ubuntu 10.10, before Mint 10 RC came
out.
14.11.2010 19:59, Richard Postlewait wrote:
It's fixed in Mint 10.
Awesome! Then why the hell is this bug not fixed in latest LTS release? Regular
one-year support releases are just a toys for home linux users while corporate
one tend to use LTS releases for production use. And the fact that
On Monday 15,November,2010 04:42 AM, Alexey Loukianov wrote:
14.11.2010 19:59, Richard Postlewait wrote:
It's fixed in Mint 10.
Awesome! Then why the hell is this bug not fixed in latest LTS release?
Regular
one-year support releases are just a toys for home linux users while
corporate
15.11.2010 00:11, Chow Loong Jin wrote:
Status in “mountall” source package in Lucid: Fix Released
Again, Get The Facts™. I don't care what Mint LTS does, but Ubuntu LTS has it
fixed, so please don't confuse the two again.
Thanks for pointing out on this. So, what is the _real_ current
On Monday 15,November,2010 05:43 AM, ingo wrote:
Status in “mountall” source package in Lucid: Fix Released
But when - too late!
Such things happen when releases are time based instead of when it's
done. What is a LTS-release worth when takes months to become ready for
use.They are almost
On Monday 15,November,2010 08:54 AM, Alexey Loukianov wrote:
15.11.2010 00:11, Chow Loong Jin wrote:
Status in “mountall” source package in Lucid: Fix Released
Again, Get The Facts™. I don't care what Mint LTS does, but Ubuntu LTS has it
fixed, so please don't confuse the two again.
15.11.2010 06:14, Chow Loong Jin wrote:
10 days is too long? Really?
If it was really fixed in that 10 days and all people reporting here blaming
Ubuntu are in reality just hadn't installed fresh updates or are using Mint
instead then it was fast enough to call it good level of support. If not
Have switched to Ubuntu 10.10. No issues at all. Thanks. I wasn't having the
problems your listing anyway.
On Oct 11, 2010 9:22 AM, papukaija 571...@bugs.launchpad.net wrote:
@axel: That issue is not probably related to this bug, and can even be
related to your graphic card driver or plymouth
On Mon, 2010-05-10 at 10:53 +, Michael Hampson wrote:
@ Sitsofe Wheeler, Steve Langasek etc: you are, of course, heroes all.
Can I add my praise?? I've done a bit of development and know how time
consuming and exasperating debugging can be. I've been following the
process and am sooo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10-05-10 06:29 AM, Bernat wrote:
I see a slow down at 95%
I'm pretty sure that's normal
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkvoHEkACgkQst0AR/DaKHveqgCcCXiiBUSI/BIxdhZFzUw7iMKI
Michael,
On Sun, May 09, 2010 at 02:34:30PM -, Michael Hampson wrote:
Further to the immediately preceding post, as an experiment, I forced
fsck on my one-year-old Acer Aspire One Atom-based Netbook with fresh
10.04 install. It has *exactly* the same bug: the check slows to snail's
pace,
On Thu, May 06, 2010 at 10:34:07PM -, Anders Kaseorg wrote:
Sure.
** Patch added: mountall_2.14_lp571707.debdiff
http://launchpadlibrarian.net/47964636/mountall_2.14_lp571707.debdiff
This patch doesn't apply cleanly against the current bzr branch (which
happens to already have a
I've been at a conference and only had time last night to look at the
patched binaries. I installed the patched mountall, but both
libplymouth and plymouth i386 binaries that I got were faulty (looking
inside the packages, the two executables were only 20 bytes). Taking a
fresh download got the
On Fri, 2010-05-07 at 10:28 +, arand wrote:
I do not see that, when downloading the .deb files I get e.g. ~54k for the
plymouthd executable, so that sounds like some kind of corruption in the
download on your side, I think.
Just tried again from:
On Monday 03,May,2010 06:49 PM, D J Eddyshaw wrote:
Interesting thought that this could be related to upgrading from Karmic
rather than a fresh install. Both my machines suffer from the problem
and were upgraded, for what it's worth. How about everyone else?
I think if you read some of the
hwinfo --bios | grep Socket requires root permission to produce the
output.
Fabio Marzocca try using sudo hwinfo --bios | grep Socket
--
fsck progress stalls at boot, plymouthd/mountall eats CPU
https://bugs.launchpad.net/bugs/571707
You received this bug notification because you are a member
On Mon, 2010-05-03 at 13:34 +, letstrynl wrote:
People, can everyone (with or without problems) run the two hwinfo
commands mentioned (with grep please) , so we can see if there's a
connection between hardware and the behavior of plymouth ?
I looked at this, and hwinfo doesn't seem to
30 matches
Mail list logo
