I can confirm this. Hit it this weekend trying to install guests on
32-bit karmic host.
Why would you mark this incomplete unless someone can confirm it on
lucid? That's a data point, sure, but it's still badly broken on karmic.
--
KVM guests no longer start after upgrading host system from 9.04
Sebastien, thanks for the clue! There is no dbus session running. This
modification fixes the test case:
$ dbus-launch bash
$ gconftool-2 --ping ; echo $?
2
$ gconftool-2 --spawn
$ gconftool-2 --ping ; echo $?
$ exit
Is this a change between the versions of gconf in karmic and lucid, that
it now
I'm not sure how to reply to comment #2. My sequence of commands showed
that: (1) gconfd was not running at the beginning of the sequence, (2)
gconftool --spawn started it properly, (3) gconftool --ping then could
not find the running daemon. I'm glad that gconftool --ping works right
for you, but
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/39887482/Dependencies.txt
--
gconftool-2 can't find running gconfd-2
https://bugs.launchpad.net/bugs/529577
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
Public bug reported:
Binary package hint: gconf2
$ pgrep -l gconfd-2
$ gconftool-2 --spawn
$ pgrep -l gconfd-2
23220 gconfd-2
Great, so it's running, but...
$ gconftool-2 --ping ; echo $?
2
and since gconftool-2 can't find the running gconfd-2, trying to modify
settings will instead modify the
Okay, by adding this to my /etc/fstab on the nfs root filesystem, then
regenerating the initramfs, it's booting again:
/dev/nfs / nfs nolock,tcp 0 0
So this differs from my jaunty config in two ways:
1. jaunty didn't require nolock. I don't know if it was being
automagically added by mountall or
Btw I'm running mountall-0.2.2
--
nfsroot nolock regression
https://bugs.launchpad.net/bugs/452686
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman
Public bug reported:
Binary package hint: mountall
I just updated a headless thin client from jaunty to karmic. Now it
fails to boot with this:
mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
mountall:
I turn off the desktop because ion3, which doesn't support EWMH, insists
on managing the window. ion3 is a tiled window manager so (if you're
using tiled desktops) there is no desktop for nautilus to draw.
--
gnome-session keeps respawning nautilus when no desktop is drawed
https://bugs.launchpad
Better to use dpkg-divert to protect your modified nautilus.desktop than
trying to use permissions. Here's the formula:
$ sudo dpkg-divert --add --rename --divert \
/usr/share/applications/nautilus.desktop.real \
/usr/share/applications/nautilus.desktop
$ cp /usr/share/applications/nautil
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/33470134/Dependencies.txt
** Attachment added: "XsessionErrors.txt"
http://launchpadlibrarian.net/33470136/XsessionErrors.txt
--
important fix for "timeout" in Debian
https://bugs.launchpad.net/bugs/449194
You received
Public bug reported:
Binary package hint: tct
Due to an incorrect earlier patch, timeout always waits the full time
when used in a pipeline:
$ time -15 4 true
real0m0.013s
$ time -15 4 true | cat
real0m4.012s
This bug was reported and fixed in Debian, see http://bugs.debian.org
/cgi-bi
Public bug reported:
Binary package hint: openct
openct 0.6.14-3ubuntu2 (ubuntu karmic alpha) initscript fails if my usb
actividentity (activkey sim) is inserted. Here is what happens:
# /etc/init.d/openct start
Starting smart card terminal framework: OpenCTusage: ifdhandler [-Hds] [-r
reader]
The better fix would be to update to openct-0.6.16 which already handles
the switch to udevadm
--
Openct needs to be restarted when inserting an eToken
https://bugs.launchpad.net/bugs/368683
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Regarding "exec 2> /tmp/openct-script.log 2>&1" -- this is a mistake. It
redirects stderr first to the file then redirects stderr to stdout.
That's why the logfile was created but blank. You meant "exec 2> /tmp
/openct-script.log 1>&2" to capture both stdout and stderr.
Alternatively "exec 2> /tmp
ause it will fall through if udevinfo produces no output,
since /dev/ satisfies the -n and -e checks.
Here is a patch to fix both problems. I've tested this on karmic
(openct-0.6.14-3ubuntu2)
** Attachment added: "/home/agriffis/openct_usb.patch"
http://launchpadlibrarian.net/2
Edit /etc/network/interfaces, add the following:
auto lo
iface lo inet loopback
--
portmap hangs on shutdown
https://bugs.launchpad.net/bugs/309542
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
Believe the problem here is that the lo interface isn't configured.
pmap_dump attempts to connect to 127.0.0.1 but if lo isn't configured,
it will hang.
--
portmap hangs on shutdown
https://bugs.launchpad.net/bugs/309542
You received this bug notification because you are a member of Ubuntu
Bugs,
You're right, thanks. I'd forgotten about sh -e so if start-stop-daemon
fails then the initscript will stop immediately. I'm still a bit
confused because I've seen this initscript exiting zero when the daemon
didn't start, but on rereading I'm not sure how that could happen. I'll
debug further i
Because of sh -e, the script should abort immediately if start-stop-
daemon returns non-zero status. To avoid that for the sake of error
reporting, the provided patch could be modified as:
start-stop-daemon -p $PIDFILE --stop --retry TERM/3 || status=$?
--
pulseaudio init-script fails to restar
Public bug reported:
Binary package hint: libengine-pkcs11-openssl
See http://www.opensc-project.org/engine_pkcs11/ticket/11
This worked in 0.1.3, broke in 0.1.4.
I reported this bug upstream over a year ago and it was finally
fixed. Can we pull this patch in to Ubuntu ASAP? It's a huge
pain f
This and #244414 are simple bugs with patches, it would be nice to have
them applied in time for intrepid.
--
pulseaudio init-script wrong status
https://bugs.launchpad.net/bugs/244400
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: "pulse-init.patch2"
http://launchpadlibrarian.net/15724245/pulse-init.patch2
--
pulseaudio init-script fails to restart
https://bugs.launchpad.net/bugs/244414
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
u
Public bug reported:
Binary package hint: pulseaudio
package: pulseaudio-0.9.10-2ubuntu1
on Ubuntu intrepid
Sometimes pulseaudio takes a second to stop. This can cause
restart to fail:
$ sudo /etc/init.d/pulseaudio restart
Stopping PulseAudio Daemon.
Starting PulseAudio Daemon/usr/bin/pulseaudi
** Attachment added: "pulse-init.patch1"
http://launchpadlibrarian.net/15722675/pulse-init.patch1
--
pulseaudio init-script wrong status
https://bugs.launchpad.net/bugs/244400
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
Public bug reported:
Binary package hint: pulseaudio
package: pulseaudio-0.9.10-2ubuntu1
on intrepid
The pulseaudio initscript has an error reporting status. We want to know the
status of the start-stop-daemon command, but instead we reference $? after
running a couple conditional blocks. In m
26 matches
Mail list logo
