** Tags added: cscc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/554172
Title:
system services using "console output" not starting at boot
To manage notifications about this bug go to:
Thanks for directing me - see:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829644
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/554172
Title:
system services using "console output" not
FrankStefani, given the scope of this closed report was fixed in Ubuntu
10.10 (i.e. pre-dating your usage of 12.04), it had and has nothing to
do with your problem.
However, regarding the problem you are experiencing, it is most helpful if you
use the computer the problem is reproducible with
Your comment describes an issue entirely unrelated to this bug report.
Please file a separate bug report against the cups package using ubuntu-
bug cups.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Unbelievable: After many years with Ubuntu-12.04 to 16.04, followed by
Linux Mint up to 19.3 (Ubuntu 18.04), I switched to a fresh new install
of Lubuntu-19.04 a week ago... and have this strange printer disappear
problem for the first time ever!
Today is May 18th, 2019 - that is over threet
@Christopher: I wasn't suggesting it should stay open. I was just
making a comment on how letting tickets stagnate until everyone gives up
and stops commenting is one sure way to close tickets.
I don't actually use Ubuntu any more because my experience when I last
did (and the reason I switched)
Brian J. Murrell, this report hasn't had a comment from an original
reporter since 2013, and the latest duplicate report filed was back from
Lucid.
Hence, could you please advise precisely on why this report should
remain open?
--
You received this bug notification because you are a member of
That version is now outdated and no more supported
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/554172
Title:
system services
> That version is now outdated and no more supported
Waiting for the Ubuntu versions that bugs are filed against to just
become unsupported is one way to close tickets I suppose. Even tickets
that affect 243 people.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Mike Basinger, this bug was reported a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an
issue? If so, could you please test for this with the latest development
release of Ubuntu? ISO images are available from
** Tags removed: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/554172
Title:
system services using console output not starting at boot
To manage notifications about this bug go to:
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/554172
Title:
system services using console output not starting at boot
--
ubuntu-bugs mailing list
We users are NOT experts in the Launchpad rules and regulations.
We just want our problems addressed.
Please do whatever is necessary to open up a bug that addresses the
long standing and still present condition of init scripts not being executed
reliably.
For Title and Description I propose:
On Mon, 2011-02-14 at 15:13 +, Mike Bianchi wrote:
We users are NOT experts in the Launchpad rules and regulations.
We just want our problems addressed.
Please do whatever is necessary to open up a bug that addresses the
long standing and still present condition of init scripts not being
On Mon, Feb 14, 2011 at 11:56 AM, Clint Byrum cl...@fewbar.com wrote:
Right now the issue that was reported originally is definitely fixed from
the point of view of many of those who reported they were affected
I took Ubuntu 10.04 off my little home network because of this bug after
On Mon, Feb 14, 2011 at 03:13:57PM -, Mike Bianchi wrote:
Please do whatever is necessary to open up a bug that addresses the
long standing and still present condition of init scripts not being executed
reliably.
No, we do not proxy create bug reports. The user /experiencing the problem/
I understand that some people are still finding their boot unreliable. But
there is no evidence that it's related to *this* bug report, and these boot
reliability problems are not reproducible for any of the developers. We
want to help make Ubuntu more reliable for users but the first step in
Any news on this bug? Is anyone trying to fix it?
Considering moving to an other distro without upstart
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/554172
Title:
system services using
Jens Schødt, this bug is in the kernel console device not being
writeable early enough in the boot. I appears to be in upstart because
that is the first thing that tries to write to it. A work around has
been available of the problem for several months, which seems to have
fixed the boot for those
Thanks John,
I see problems in a fresh 10.10 install (both 32 and 64bit). init.d services
are not always started. eg. hostapd and sabnzbdplus.
I dont know about the 'runlevel' reporting 'N' because I am currently trying an
other distro without this problem. I will create a bug if I get back to
On Sat, 2011-02-12 at 21:22 +, Mike Bianchi wrote:
On Sat, Feb 12, 2011 at 02:15:20PM -, Brian J. Murrell wrote:
Any news on this bug? Is anyone trying to fix it?
On Sat, 2011-02-12 at 12:11 +, Jens Schødt wrote:
Yeah, IMHO, upstart was wa rushed into Ubuntu. ...
On Sat, Feb 12, 2011 at 09:22:20PM -, Mike Bianchi wrote:
On Sat, Feb 12, 2011 at 02:15:20PM -, Brian J. Murrell wrote:
Any news on this bug? Is anyone trying to fix it?
On Sat, 2011-02-12 at 12:11 +, Jens Schødt wrote:
Yeah, IMHO, upstart was wa rushed into Ubuntu.
On Sat, 2011-02-12 at 12:11 +, Jens Schødt wrote:
Any news on this bug? Is anyone trying to fix it?
Considering moving to an other distro without upstart
Yeah, IMHO, upstart was wa rushed into Ubuntu. It was clearly
not ready considering how many problems it has caused for
On Sat, Feb 12, 2011 at 02:15:20PM -, Brian J. Murrell wrote:
Any news on this bug? Is anyone trying to fix it?
On Sat, 2011-02-12 at 12:11 +, Jens Schødt wrote:
Yeah, IMHO, upstart was wa rushed into Ubuntu. ...
I agree.
The evidence strongly suggests that Upstart still
Upstart has been working fine for me ever since the patch for this bug.
If you're still experiencing the symptoms in a closed bug report, the
best thing to do is file a new bug. Otherwise fixing the remaining bug
isn't on anyone's to-do list, and it's kind of silly to complain that it
isn't being
I get:
$ runlevel
N 2
whatever that means.
Luckily my remote production unattended 64bit virtual Ubuntu 10.04 LTS server
seems to start Apache, MySQL and SSH when it boots otherwise this would be a
disaster. Why do this kind of thing in a LTS release?? Doesn't anyone
understand the words
@David,
try executing following command (simulates upgrade of libc6):
apt-get install --reinstall libc6
and shutdown you server, then check your root-filesystem,
or reboot and check with cat /var/log/messages | grep orphan
That's Bug #672177
--
You received this bug notification because you
David, if you get runlevel 2 it means that you have a different problem
to this bug (which is about upstart not entering runlevel 2).
If it only effects Apache than I would suggest opening a new bug against
that relevant Apache package (if one does not already exist). If it does
turn out to be an
I cannot see that this has been fixed. I am using 10.04 LTS on my
Toshiba Tecra and do Apache development. Most times but not alawys, on
boot apache2 does not start so I need to do it manually sudo
/etc/init.d/apache2 start
--
You received this bug notification because you are a member of
David Haskins, could you run the 'runlevel' command to check if this is
related to this particular bug, or if it is another problem?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/554172
Title:
On Wed, Jan 12, 2011 at 03:14:41PM -, John Edwards wrote:
David Haskins, could you run the 'runlevel' command to check if this is
related to this particular bug, or if it is another problem?
A better approach might be to put logging into /etc/init.d/apache2
and figure out:
If it is
Probably things will turn better in future, Scott will leave Canonical
and go to Google by next week, leaving behind the half done upstart in
Ubuntu for others to clean up.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/554172
Title:
system services using console output not starting at boot
--
ubuntu-bugs mailing list
For anyone who is still experiencing problems with services not
starting at boot, I suggest you open a new bug (feel free to subscribe
me - robbie.w is my ID). There could be any number of reasons why a
particular service won't start, and we'd rather you open a new bug than
add to this one. If we
I'm running the updated upstart and plymouth-free grub2 config on two newly
installed amd64 boxes (bog-standard Dell 2950s) with today's 2.6.32-24-server
kernel, and I'm still finding a whole bunch of services fail to start (cron,
apache2, mysql, fail2ban, sysstat, postfix, openntpd,
On Tue, Sep 21, 2010 at 04:09:39PM -, Marcus Bointon wrote:
I'm running the updated upstart and plymouth-free grub2 config on two
newly installed amd64 boxes (bog-standard Dell 2950s) with today's
2.6.32-24-server kernel, and I'm still finding a whole bunch of services
fail to start (cron,
The revised version of Upstart fixed it for me. Thanks to Scott James
Remnant and Andy Whitcroft. I have done many cold boots and restarts
since the fix, and the bug is gone.
To avoid problems with Plymouth, get rid of quiet splash in the Grub
kernel command line. Alas, Grub and Grub 2 are
To avoid problems with Plymouth, get rid of quiet splash
Better: get rid of Plymouth
--
system services using console output not starting at boot
https://bugs.launchpad.net/bugs/554172
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Just deinstalling plymouth solves this problem on my system too.
--
system services using console output not starting at boot
https://bugs.launchpad.net/bugs/554172
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Great, thanks for your feedback, Rogi.
Plynouth in my opinion is yust a fancy boot screen which is still in an
alpha stadium. Though Ubuntu team always points out it also does all
logging during boot process - that is the root cause of all that and
other troubles and you again did confirm that.
For anyone who is still experiencing problems with services not starting
at boot, I suggest you open a new bug (feel free to subscribe me -
robbie.w is my ID). There could be any number of reasons why a
particular service won't start, and we'd rather you open a new bug than
add to this one. If we
On my box it helped to just un-install plymouth and all services like cups,
apcupsd ... are starting fine since then.
How to perform this (artificial blocked) un-install, see
https://bugs.launchpad.net/bugs/556372
--
system services using console output not starting at boot
42 matches
Mail list logo
