Further to my 2009-04-25 comment, no statistical picture has emerged. It
is difficult to be sure of anything with such an intermittent problem
but I have been getting very good results from cleaning the DVD since
starting to use a micro-fibre cloth (sold for cleaning LCD screens) even
when the DVD
If this is the right report for no boot logging in ubuntu then it is
the right place to comment on Scott James Remnant's explanation of why
bootlogd cannot be used as a workaround for this problem.
In a comment on bug 328881 init: support logging of job output
Hello Scott :-)
Regards If you want it done more urgently, *you're going to do need to
do it yourself*, it's already done.
Sergei Ivanov's workaround described in
https://bugs.launchpad.net/upstart/+bug/98955/ from comment #29 onwards
and in
Hello Scott :-)
I understand you're thinking of a standalone syslogd .deb for ubuntu
only, built either from the ubuntu sysvinit source plus unspecified
fixes or by merging the probably already fixed Debian source into the
ubuntu sysvinit source.
I'm ignorant but willing and have a little
*** This bug is a duplicate of bug 328881 ***
https://bugs.launchpad.net/bugs/328881
AFAIK shutdown messages have never been logged so this bug report is an
enhancement request unlike the others which are about lost
functionality.
--
shutdown console messages are lost
*** This bug is a duplicate of bug 328881 ***
https://bugs.launchpad.net/bugs/328881
Thank you Scott :)
most succinctly makes sense but cannatella's subject is _shutdown_
console messages are lost so I do not understand how this bug can be a
duplicate of any bug report that is about _boot_
*** This bug is a duplicate of bug 328881 ***
https://bugs.launchpad.net/bugs/328881
Thanks Dimitrios Symeonidis
That makes sense. If it were applied in this case then this bug report
(with 74 comments) would be the master rather than
https://bugs.launchpad.net/upstart/+bug/328881 (with
*** This bug is a duplicate of bug 328881 ***
https://bugs.launchpad.net/bugs/328881
This bug report, started on 2007-03-30, has been marked as a duplicate
of https://bugs.launchpad.net/upstart/+bug/328881, started on
2009-02-13.
I understood that later bugs were marked as duplicates of
*** This bug is a duplicate of bug 328881 ***
https://bugs.launchpad.net/bugs/328881
This bug report, started on 2006-11-01, has been marked as a duplicate
of https://bugs.launchpad.net/upstart/+bug/328881, started on
2009-02-13.
I understood that later bugs were marked as duplicates of
*** This bug is a duplicate of bug 328881 ***
https://bugs.launchpad.net/bugs/328881
This bug report, started on 2006-11-01, has been marked as a duplicate
of https://bugs.launchpad.net/upstart/+bug/328881, started on
2009-02-13.
I understood that later bugs were marked as duplicates of
Sorry -- I forgot to point out that
https://bugs.launchpad.net/bugs/328881 has two workarounds, one being an
(unsupported but widely used) bootlogd installation and the other being
a way to stop init script processing and get a login prompt during boot
that allows you to and see (and scroll back
Hello schnauzer :-)
If Intrepid is like Hardy then the issue is that bootlogd itself is not
installed, despite the existence of /etc/default/bootlogd.
Have you got a /sbin/bootlogd executable? If not, see
https://bugs.launchpad.net/bugs/328881 for an (unsupported) workaround
that may also work
Hello Chris :-)
To answer your question I installed OOo_3.1.0_LinuxIntel_install_en-US
(from http://distribution.openoffice.org/p2p/, so the generic .debs, not
ubuntu-specific).
I was still able to run the following from the command line:
soffice
Thanks for your attention Chris :-)
AIUI, URIs are supported by OOo, not by Gnome, so they work
independently of both desktop and OS; the same syntax works on non-Gnome
desktops and on Windows. If my understanding is correct then disabling
OOo's Gnome VFS and GVFS support would not result in
Public bug reported:
Hello :-)
The openoffice man page installed with 1:2.4.1-1ubuntu2.1 describes
filename as filename... Files to operate on.
Please consider adding a description of their format which may, I
believe, be a URL in which case it would begin with file:/// or
macro:///. Maybe
Hello (especially Sergei) :-)
I'm trying to go further, running bootlogd on ubuntu 8.04.02 running in
a VirtualBox virtual machine with / mounted read-only and a writeable
/var/log mounted later. Isn't it always the way -- the code works
perfectly well and then someone shifts the goal posts?!
I
Hello Andrew :-)
Interesting analysis.
You are correct to write The OP's report does not have the 'attempt to
access beyond end of device' error message. That message was not
reported here until
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/228624/comments/14
. I have seen a bewildering
Hello :-)
Subject: bootlogd 2.86.02 boot script link change to capture more boot
messages
Regards the workaround for this bug ('cos it ain't going away any time
soon!).
After installing bootlogd 2.86.02 from the package Sergei attached to
this bug report (thanks Sergei) ...
bootlogd is started
I may have found a workaround. It's difficult to be sure because the
problem is intermittent on my system. The change disables auto-mount for
all removable media. The technique was posted at
http://osdir.com/ml/linux.debian.devel.live/2007-11/msg00070.html. In
the 4 days since making this
Quote: Per a decision made by the Ubuntu Kernel Team, bugs will longer
be assigned to the ubuntu-kernel-team in Launchpad as part of the bug
triage process. The ubuntu-kernel-team is being unassigned from this bug
report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more
information.
This bug is still present in Hardy.
A little more information from
http://bugzilla.gnome.org/show_bug.cgi?id=351086#c2
=== excerpt begins ===
Here's the relevant part in the code:
GnomeUIInfo state_data[] = {
GNOMEUIINFO_ITEM_STOCK(N_(Inactive),
N_(Waiting to start
21 matches
Mail list logo
