allow root escalation since
all user session jobs run as root.
The following branch includes a fix for this issue:
lp:~jamesodhunt/ubuntu/natty/upstart/fix-chroot-sessions
** Affects: upstart (Ubuntu)
Importance: Critical
Assignee: James Hunt (jamesodhunt)
Status: Fix
We do indeed seem to have an embarrassment of riches here :-)
I for one subscribe to the "dry" principle so would welcome a simpler
method of announcing new Upstart releases as right now it is time
consuming and -- as evinced by this bug -- error prone. A few points:
- upstart.at is owned by Keyb
Note that the fix for this bug in Upstart 1.3 protects against ".conf"
and ".override".
** Changed in: upstart (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
Hi Mike,
Hopefully the newly introduced show-config and check-config commands go
some way towards providing what you are looking for:
https://wiki.ubuntu.com/NattyNarwhal/TechnicalOverviewUpstart#New_Initctl_Commands
http://upstart.ubuntu.com/cookbook/#initctl-show-config
http://upstart.ubuntu.co
Public bug reported:
For the natty cycle, a new mountall event "device-not-ready" was added
to mountall. This event is emitted when the " --dev-wait-time" timeout
(see "mountall --help") is exceeded.
Table 1 of upstart-events(7) therefore needs to be updated to include
"device-not-ready". Details
Public bug reported:
The man page for mountall is too brief. There are currently 9 command-
line options to mountall, but none are specified in mountall(8).
This bug is raised to add all the available options. Run, "mountall
--help" to see them.
** Affects: mountall (Ubuntu)
Importance: Und
Public bug reported:
In a similar vein to bug 791866, /etc/init/rc-sysinit.conf needs to be
updated to add an "emits deconfiguring-networking" line and then
"initctl check-config" run to ensure that the current dbus error
relating to the unknown event "deconfiguring-networking" disappears.
This b
** Changed in: upstart
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/430224
Title:
init: support chroots
To manage notifications about this bug go
** Changed in: upstart
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/94065
Title:
init: add non-destructive means to disable a job
To manage notifications
Chroot support is now available in Upstart 1.3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/430224
Title:
init: support chroots
To manage notifications about this bug go to:
https://bugs.
Public bug reported:
Running dbus-launch from the console results in very poor performance
(keyboard keys need to be held down for multiple seconds for an echo of
that character to appear on the console).
To recreate:
killall dbus-launch &>/dev/null
eval `dbus-launch --auto-syntax --exit-wit
Public bug reported:
The Ubuntu dbus package is not explicitly setting configure options. The
latest version of lp:ubuntu/dbus appears to have introduced a new option
(?) which is defaulting to "enabled". The option is "--
enable-x11-autolaunch":
./configure
grep "^#define DBUS_ENABLE_X11_AUTOLAU
As discussed with Colin, it may be better (and safer) to retain this
change since it is now the default in dbus and as such is the new
expected behaviour.
Users who may be affected by this change in auto-launch behaviour can
either:
1) Arrange for dbus to auto-launch on address they specify using
** Branch linked: lp:~jamesodhunt/ubuntu/oneiric/upstart/fix-for-810956
** Changed in: upstart (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/810956
Ti
Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, this issue is caused by the fact that a default
natty server does not install the "dbus" package and hence non-root
users are unable to communicate with Upstart using initctl (specifically
the "list" and "s
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) => James Hunt (jamesodhunt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/810956
Title:
/dev/.initramfs/ → /run/initramfs transition
Public bug reported:
Oneiric now has a "/run" directory. However, if you run:
pbuilder --execute foo.sh
... once it unpacks the base oneiric image, pbuilder attempts to copy
the specified script (here "foo.sh") to "/run" as a file, not a
directory. This fails since the base oneiric image now inc
** Description changed:
Binary package hint: upstart
The initctl(8) check-config command reads the "emits" stanzas (see
init(5)). However, we have a minor problem in that portmap starts on an
event that is not advertised using "emits":
$ initctl check-config
portmap
- stop on:
Public bug reported:
Binary package hint: dbus
The initctl(8) check-config command reads the "emits" stanzas (see
init(5)). However, we have a minor problem in that dbus starts on an
event that is not advertised using "emits":
$ initctl check-config
dbus
stop on: unknown event deconfiguring-ne
Public bug reported:
Binary package hint: portmap
The new version of upstart in Natty has a visualisation facility. This
requires that all upstart job configuration (".conf") files advertise
the events they emit by specifying the "emits" stanza. However, although
/etc/init/portmap-boot.conf emits
** Changed in: portmap (Ubuntu)
Assignee: (unassigned) => James Hunt (jamesodhunt)
** Changed in: portmap (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Fix now also tested on lucid.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase-workspace in ubuntu.
https://bugs.launchpad.net/bugs/436936
Title:
gdm upstart job checks /proc/cmdline for single user mode, won't start
on post-boot
>From what I can see, the changes that need to be made are:
File /etc/kde4/kdm/Xsession needs to specify the following:
/sbin/initctl -q emit desktop-session-start DISPLAY_MANAGER=kdm
USER=$USER
File /etc/kde4/kdm/Xstartup needs to specify the following:
/sbin/initctl -q emit login-session-
Public bug reported:
Binary package hint: gwibber
Gwibber appears to use an SQLite3 database to store the following
details, each in its own database table:
(1) account details
(2) streams
(3) searches
(4) messages
The problem is that it places this database in
~/.config/gwibber/gwibber.sqlite.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/734917
Title:
gwibber stores data in XDG_CONFIG_HOME directory
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailma
Stage 2 has now been merged.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/723846
Title:
Feature Freeze Exception request for Upstart in Natty
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.
Oops! and we have
File /etc/gdm/PreSession/Default emitting desktop-session-start as the
user that is logging in.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase-workspace in ubuntu.
https://bugs.launchpad.net/bugs/715093
Title:
k
If we have any lightdm gurus reading, it would be good to get the same
functionality with lightdm (see bug 715094).
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase-workspace in ubuntu.
https://bugs.launchpad.net/bugs/715093
Title:
@Felix: thanks for picking this one up. The fact that Xsession doesn't
run as root is fine. With gdm, we have:
File /etc/gdm/Init/Default emitting the login-session-start event (as
root)
File /etc/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Stage 2 now pushed to users. I've updated the doc below to reflect this:
https://wiki.ubuntu.com/NattyNarwhal/TechnicalOverview
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/723846
Title:
Featur
It's looking like the change I made for bug 436936 might be the culprit,
but I am unable to recreate this issue at present.
Please could follow the steps below to run Upstart in debug mode:
1. Hold down SHIFT key before the splash screen appears (this will then display
the grub menu).
2. Type, "
@Fabio - two out of how many systems? Is it consistently reproducible
for those two systems?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/735805
Title:
GDM fails to start
--
ubuntu-bugs mailing l
It's looking like the problem may be with the runlevel test here:
31 if [ "$curr" = S -o "$prev" = unknown ]
32 then
33 # Single-user mode
34 plymouth quit || :
35 exit 0
36 fi
I've attached a version of /et
@Benjamin: thanks for testing! Could you also confirm that if you boot
to recovery mode (single user mode) that once you've at a shell, running
"telinit 2" displays gdm as expected?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
@Benjamin: ok - I think that's why I added the "unknown" check which
clearly caused problems for some systems. The change below *should*
stop gdm from starting in recovery mode:
31 if [ "$curr" = S -o -z "`echo $UPSTART_EVENTS|egrep -o
"\"`" ]
32 then
33
If those who experienced this problem could help with testing a fix for
bug 436936, I have attached a new gdm.conf to bug 436936. Thanks very
much!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/735805
Please could those who experienced the problems on bug 735805 provide
feedback on using the attached gdm.conf. If possible, could you confirm
that:
1) When you boot normally, gdm starts as expected.
2) When you boot to a recovery console that gdm does *NOT* start.
(hold down SHIFT and select
@Jonathan - thanks for testing! Good news. Yes, I think you are right re
friendly-recovery.
@Erick and others - I attach an updated gdm.conf which might help.
Looking at the old gdm.conf, I think it was missing a condition which
this new gdm.conf adds. Please let me know your findings. Thanks for
@Felix - ah! sorry, I see your point, so ignore comment #3. Is there
another script we can use with kdm to emit the desktop-session-start
event?
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase-workspace in ubuntu.
https://bugs.launchp
Branches (1)-(3) inclusive have now been proposed for merging in the
following:
lp:~jamesodhunt/ubuntu/natty/upstart/proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/723846
Title:
Feature F
Branches (1)-(3) inclusive are now in the Natty archive as Upstart
version 0.9.0-1ubuntu3.
I have now documented Scotts socket bridge branch with 2 new man pages
(not yet released) and the requisite .conf file. These can go in the
next update.
I have now completed tests for Branch (4). Plan now i
** Changed in: upstart
Status: Triaged => Fix Released
** Changed in: upstart (Ubuntu)
Status: Invalid => Fix Released
** Changed in: upstart
Assignee: (unassigned) => James Hunt (jamesodhunt)
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) =>
Upstart in Natty now supports Override files and the manual stanza. See:
https://wiki.ubuntu.com/NattyNarwhal/TechnicalOverview#Upstart
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/94065
Title:
Updated https://wiki.ubuntu.com/NattyNarwhal/TechnicalOverview with new
features.
Branch (4) has now been merged into lp:~upstart-devel/upstart/0.9. Now
working on adding doc for socket bridge, sessions and chroots (to be
followed by lp:ubuntu/upstart merge + PPA).
Note that Chroot support seems
Updated lp:~upstart-devel/upstart/0.9 with doc for sessions and chroots
(Branch (2)).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/723846
Title:
Feature Freeze Exception request for Upstart in Natt
It's looking like the failure is multiarch related: /usr/share
/initramfs-tools/scripts/init-top/bootchart is a script run via "/bin/sh
-e". This script attempts to run:
cp /lib/libc.so.* $JAIL/lib
...however, /lib/libc.so.* does not exist, causing the script to exit
and never run the bootchart c
All review comments on merge proposal implemented, bar two:
* debian/manpages/upstart-events.7: This man page isn't available
upstream since it documents the "Ubuntu way", so I think the URL is
correct I think.
* init/main/init.5:
> +Note that a user job configuration file cannot have the s
Re-submitted merge proposal due to a failing "make distcheck" in
upstream branch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/723846
Title:
Feature Freeze Exception request for Upstart in Natty
-
Hi Martin - to re-enable user sessions, users would need to install the
file dbus/Upstart.conf from the upstream version of Upstart as
/etc/dbus-1/system.d/Upstart.conf.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
An updated branch for natty containing the visualisation support (Branch
(4)) is here:
lp:~jamesodhunt/ubuntu/natty/upstart/proposed-stage2
My PPA is currently building packages based on this branch:
ppa:jamesodhunt/upstart-testing
Testers welcome!
--
You received this bug notificatio
@Dave - great! Thanks for trying this out. The vis support doc is below.
This will be added to the Natty Tech Overview when it lands:
Basic Job/Event Visualisation
Upstart provides a new Python script `initctl2dot` which converts the
output of the new `initctl show-config` command to
[[
Minor updates to Branch 4 (man pages and minor script tweaks). Merge
proposal raised for branch:
lp:~jamesodhunt/ubuntu/natty/upstart/proposed-stage2
Latest code published to PPA below:
ppa:jamesodhunt/upstart-testing
--
You received this bug notification because you are a member of Ub
@Dave: The just-updated PPA now contains a man page for the
visualisation command "initctl2dot".
Also, new man pages...
init-checkconf
net-device-added (link to upstart-udev-bridge)
net-device-removed (link to upstart-udev-bridge)
graphics-device-added (link to upstart-udev-bridge)
drm-
Public bug reported:
Binary package hint: rxvt-unicode
I am unable to display the Ubuntu Unicode Symbol (U+E0FF, "") in urxvt
(or in fact xterm).
This symbol displays fine in gnome-terminal and other graphical
applications (such as gedit, libreoffice, gvim).
ProblemType: Bug
DistroRelease: Ubu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/731172
Title:
unable to display Ubuntu Unicode symbol in urxvt
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailma
*** This bug is a duplicate of bug 730860 ***
https://bugs.launchpad.net/bugs/730860
Public bug reported:
Binary package hint: gcc-4.5
I've just received a mail regarding a Natty FTBFS for vim. Details:
* Source Package: vim
* Version: 2:7.3.035+hg~8
Fix tested on natty only at this stage.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase-workspace in ubuntu.
https://bugs.launchpad.net/bugs/436936
Title:
gdm upstart job checks /proc/cmdline for single user mode, won't start
on
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/746289
Title:
bzr keywords plugin crashed with NotImplementedError in inventory()
--
ubuntu-bugs mailing list
ubuntu-
*** This bug is a duplicate of bug 389674 ***
https://bugs.launchpad.net/bugs/389674
I'm not convinced this bug is a duplicate of bug 389674. Yes, I get the
same stacktrace, but that other bug appears unrelated to bzr-keywords
and there is no mention of the work-around I used (which appears to
Public bug reported:
Binary package hint: sysvinit
If an Upstart job has no stop on condition, Upstart won't stop any
instances of it. However, if a job has no stop on, but *does* specify
respawn we have a potential problem at shutdown since:
- /etc/init.d/sendsigs will attempt to kill the Upsta
** Changed in: upstart
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/94065
Title:
init: add non-destructive means to disable a job
--
ubuntu-bugs mailing
Upstart in Ubuntu Natty provides this facility via the "--confdir "
option.
** Also affects: ubuntu
Importance: Undecided
Status: New
** Changed in: ubuntu
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
** Changed in: upstart
Assignee: (unassigned) => James Hunt (jamesodhunt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/328881
Title:
init: support logging of job output
To man
** Tags added: crasher
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/728531
Title:
chroot support is not reliable
To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+b
Could you add "-s 1024" to an strace as the strings are truncated in the
attached log. I think we'll find the log will then show lines like this:
arguments to dbus_message_iter_append_basic() were incorrect, assertion
"%s" failed in file %s line %d.
This is normally a bug in some applicat
Could you install the ddebs for upstart + libnih so we can get a proper
stack trace? dbus_message_iter_append_basic() is called in a lot of
places. I suspect that either upstart-udev-bridge (or more likely
libnih-dbus*) is calling NIH_MUST() or NIH_SHOULD() which will spin
forever until they get th
I don't think it's spamming us. The code that is causing the cpu to max
out I think is in upstart-udev-bridge.c:
276 pending_call = NIH_SHOULD (upstart_emit_event (upstart,
277name, env, FALSE,
278
I wonder if the event name itself is the problem. I've never seen a udev
event which contained underscores:
power_supply-device-added
^
|
is this normal?
If this system is a laptop and you can boot it with the battery removed
on ac power, that would be an int
I love proportional fonts. Don't you? :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/850935
Title:
upstart-udev-bridge at 100% CPU
To manage notifications about this bug go to:
https://bugs.launc
I'm not now convinced the kernel isn't spamming us. Can you do the
following:
1) sudo stop upstart-udev-bridge
2) Plonk the attached bug-850935.conf into /etc/init/.
3) Reboot with the battery attached.
bug-850935.conf will create a file /tmp/bug-850935.log with 1 line for
every "power_supply-dev
*** This bug is a duplicate of bug 829980 ***
https://bugs.launchpad.net/bugs/829980
** This bug has been marked a duplicate of private bug 829980
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/850
Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, this problem seems unrelated to upstart or ufw.
It appears your system has been upgraded to natty from a previous
release and considering some of the files in your root directory, the
problem you have just
Attached is a patch to sysvinit (from which the initscripts binary
package is generated) which appears to fix the problem for maverick. The
patch waits for up to 5 seconds for init to re-exec. If after this time
init has not re-execed, we continue to unmount forcibly. This isn't
ideal, but we canno
** Changed in: sysvinit (Ubuntu Maverick)
Assignee: (unassigned) => James Hunt (jamesodhunt)
** Changed in: sysvinit (Ubuntu Maverick)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Have notified upstreams ("busybox" and "file") that they may wish to
revert this change:
- busybox
http://lists.busybox.net/pipermail/busybox/2011-January/074264.html
- file
(no 2011 archive available yet)
For reference, original upstream patches are here:
- busybox
http://lists.busybox.n
** Patch added: "ubuntu-file-lp683605.patch"
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/683605/+attachment/1783899/+files/ubuntu-file-lp683605.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
** Patch added: "ubuntu-initramfs-tools-lp683605.patch"
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/683605/+attachment/1783900/+files/ubuntu-initramfs-tools-lp683605.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "ubuntu-util-linux-lp683605.patch"
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/683605/+attachment/1783901/+files/ubuntu-util-linux-lp683605.patch
** Changed in: busybox (Ubuntu)
Assignee: (unassigned) => James Hunt (jamesodhunt)
** Changed i
Due to the LINHIB0001 kernel change being reverted, there is no need for
this change. As such, this bug will not be progressed, unless the kernel
change is re-applied.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Public bug reported:
Binary package hint: kdebase-workspace
As an analog to bug #706842, kdm needs to emit two "well-known" upstart
events as gdm does:
1) login-session-start
2) desktop-session-start
Event (1) should be emitted just prior to the display manager starting
whilst event (2) should
@Steve - I've performed a code review of the 2 patches. Aside from a few
minor formatting suggestions for mountall.diff (#2), they look good:
mountall.c:162: indent of 'handler' element should align with 'mnt'.
mountall.c:1559: Suggest comment changed to, "All mounts have been attempted,
so wait
Due to the complexities of parsing the console= kernel param, as Clint
suggested, we could just let the kernel+getty auto-detect speed.
We could therefore create a /etc/init/ttyUSB0.conf (or similar)
containing:
exec /sbin/getty -m -8 115200,57600,38400,19200,9600,4800,2400,1200
ttyUSB0
By spe
Comment #1 was incorrect in that I was actually using ckermit, not
minicom.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/702574
Title:
getty should be started automatically on serial port when seri
This is in the trunk and should be available in upstart-0.6.8 (natty).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/672067
Title:
There is no bash-completion for the commands in upstart
--
ubuntu
Hi Michael,
Thanks for raising this and we shall investigate the possibility of
deferring service startup if possible.
The infrastructure to achieve this is already available in Lucid onwards
in the form of two sneakily "almost undocumented" events (they are
mentioned in changelog entries only fo
Hi Mike,
Thanks for reporting this and be reassured that we are investigating
this suggestion. Natty should ship with a few new man pages for upstart,
including one currently entitled upstart-events. You can see a preview
of it here:
http://people.canonical.com/~jhunt/upstart/man/upstart-events
Hi Oliver,
You are right - my comment #1 does state that we still need to extract
the device name, but we can potentially dispense with the complexities
of handling parity, speed, stop bits, etc.
Just to explain my setup: I have a "USB <-> serial <-> USB" serial
cable, hence I have ttyUSB0 on bot
Public bug reported:
According to http://sphinx.pocoo.org/builders.html#builders, sphinx-build from
the python-sphinx package is able to generate man pages (nroff) as an output
type. However,
___
$ sphinx-build -b man -d _build/doctrees . _build/man
Running Sphinx v0.6.6
Sphin
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/710698
Title:
sphinx-build cannot generate man page output
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/
Oops! Ignore comment #22 as it applies to bug 672177.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/694772
Title:
Sudden reboot during server ISO install
--
ubuntu-bugs mailing list
ubuntu-bugs@li
Thank you for taking the time to report this bug and and helping to make
Ubuntu better.
The problem appears to have been caused by a delay in the required libc6
update moving from maverick-proposed to maverick-updates. This issue has
been resolved, so please retry the upgrade to ensure it works as
ntu17_to_sysvinit_2.87dsf-4ubuntu18.diff"
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/672177/+attachment/1824633/+files/lucid-sysvinit_2.87dsf-4ubuntu17_to_sysvinit_2.87dsf-4ubuntu18.diff
** Changed in: sysvinit (Ubuntu Lucid)
Assignee: (unassigned) => James Hunt (jame
Equivalent sysvinit patch for Maverick.
** Patch added:
"maverick-sysvinit_2.87dsf-4ubuntu18_to_sysvinit_2.87dsf-4ubuntu19.diff"
https://bugs.launchpad.net/ubuntu/natty/+source/sysvinit/+bug/672177/+attachment/1824655/+files/maverick-sysvinit_2.87dsf-4ubuntu18_to_sysvinit_2.87dsf-4ubuntu19.di
Equivalent sysvinit patch for Natty.
** Patch added:
"natty_sysvinit_2.87dsf-4ubuntu19_to_sysvinit_2.87dsf-4ubuntu20.diff"
https://bugs.launchpad.net/ubuntu/natty/+source/sysvinit/+bug/672177/+attachment/1824656/+files/natty_sysvinit_2.87dsf-4ubuntu19_to_sysvinit_2.87dsf-4ubuntu20.diff
--
Y
** Changed in: sphinx (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/710698
Title:
sphinx-build cannot generate man page output
--
ubuntu-bugs mailing list
ub
Hi Jan,
I have written a bash-completion script which I hope to get packaged
soon. The script is attached if you wish to try it.
To use, save the file as $HOME/.bash_completion
** Attachment added: "upstart bash completion script"
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/672067
Comments from Andy on irc:
The issue is if we have natty and hibernate, reboot, hibernate is not detected
and swap is lost. we then fix the tools and reboot and it finds and resume
from the image and the filesystem no longer matches the memory image and BLAMMO
bad corruption of /. So if you i
Updated ppa to (hopefully - anyone is feeling brave...?) avoid data
corruption issues:
https://launchpad.net/~jamesodhunt/+archive/cerulean/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/683605
Tit
Stil require updates to busybox and libmagic1 (in progress...), although
these updates are not required unless you want busybox or /usr/bin/file
to recognize compressed hibernate images.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Binary package hint: autofs5
/etc/init/autofs.conf contains the following stop on condition:
stop on runlevel[!2345]
This will stop the autofs service when the event called
"runlevel[!2345]" is emitted! There is a missing space here. autofs.conf
should specify:
1701 - 1800 of 1868 matches
Mail list logo
