Public bug reported:
Create an init file which includes:
### BEGIN INIT INFO
# Default-Start: 3 4 5
# Default-Stop: 0 1 2 6
### END INIT INFO
Then update-rc.d it.
On ubuntu-11.10, I get:
+ update-rc.d za-dc-d defaults
update-rc.d: warning: za-dc-d start runlevel arguments (2 3 4 5)
r...@fuji-land.noir.com ssh chipmunk.palm.com
Welcome to Ubuntu precise (development branch) (GNU/Linux 3.2.0-7-generic
x86_64)
* Documentation: https://help.ubuntu.com/
Last login: Tue Jan 3 14:24:16 2012 from flamingo.palm.com
DISPLAY=localhost:10.0, TERM=xterm, EDITOR=emacsclient,
Two points.
First, ia32-libs is broken. The problem may be inherited. And the
-fix- may but elsewhere, but the presenting issue, the visible symptom,
happens when we attempt to install ia32-libs.
As user/tester, it's my job to report that symptom to the ia32-libs
developer. If the developer
I would argue that it is not appropriate to add random things with
common names like a link to start. I'm sure my personal start program
predates this link.
I -am- using sudo. Roots path is not sanitized. Sudo is the primary
method of achieving root on Ubuntu since root doesnt ordinarily have
If you don't like absolute path version, the switching to initctl
instead of start should also be fine.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dovecot in Ubuntu.
https://bugs.launchpad.net/bugs/900496
Title:
dovecot-core
I would argue that it is not appropriate to add random things with
common names like a link to start. I'm sure my personal start program
predates this link.
I -am- using sudo. Roots path is not sanitized. Sudo is the primary
method of achieving root on Ubuntu since root doesnt ordinarily have
If you don't like absolute path version, the switching to initctl
instead of start should also be fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/900496
Title:
dovecot-core installation fails
If this is a known problem with a known workaround then it needs to get
into user's hands before they start the upgrade. I think that means in
the announcements and such.
In either case, this ticket represents a failure to install and as such,
I think it should stand until the problem is
*** This bug is a security vulnerability ***
Public security bug reported:
precise pangolin alpha 1.
When installing dovecot-core, the installation fails when the service is
started because I already have a program called start in my PATH.
I suspect that /etc/init.d/dovecot should call start
Public bug reported:
Upgrading from 11.10 to precise alpha 1 on amd64.
rich@chipmunk apt-cache policy update-manager
update-manager:
Installed: (none)
Candidate: 1:0.154.6
Version table:
1:0.154.6 0
500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
I
** Attachment added: I'm attaching a tar of the /var/log/dist-upgrade
directory
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/900483/+attachment/2620954/+files/dist-upgrade.tar
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Tags added: distribution-upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/900483
Title:
update fails on libpam-ck-connector:i386
To manage notifications about this bug go to:
*** This bug is a security vulnerability ***
Public security bug reported:
precise pangolin alpha 1.
When installing dovecot-core, the installation fails when the service is
started because I already have a program called start in my PATH.
I suspect that /etc/init.d/dovecot should call start
Public bug reported:
precise pangolin alpha 1 amd64
can't install ia32-libs... missing dependencies. At the very least:
ia32-libs depends on ia32-libs-multiarch
ia32-libs-multiarch depends on bluez-alsa:i386
bluez-alsa:i386 depends on bluez:i386
bluez:i386 depends on lsb-base:i386
This is likely related to #900483
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/900512
Title:
lsb-base:i386 is not available
To manage notifications about this bug go to:
While I can understand a transition in progress, the net result is that
the precise upgrade fails. And even when I can recover the machine, I
can't do any further testing or work.
Wouldn't it have been better to approach this bottom up? With a bottom
up approach, everything would continue to
Public bug reported:
Natty alpha 1 installs on vmware fusion-3.1.2, (on macosx-10.6.5), but
can't boot. Grub is installed correctly and boots into the kernel. The
kernel appears to boot as well. I see booting lines mentioning apparmor
but then it goes to a black screen.
I've tried this twice
Public bug reported:
Ubuntu-10.10 comes with a broken version of tar.
GNU tar-1.23 has a bug and cannot properly remove directories using
--remove-files. GNU tar-1.24 and 1.25 do not have this problem.
** Affects: tar (Ubuntu)
Importance: Undecided
Status: New
--
You received
I'm attaching a short shell script which demonstrates the problem.
** Attachment added: demonstration of the problem.
https://bugs.launchpad.net/ubuntu/+bug/700058/+attachment/1787314/+files/test-tar.sh
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
As an aside, the version of openembedded that I'm using includes the use
of tar and this option. It therefor can't run on ubuntu-10.10 which has
the broken tar.
Building and installing tar-1.25 from debian sid solves the problem.
** Package changed: ubuntu = tar (Ubuntu)
--
You received this
Sorry, this is the i386 server iso.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/700042
Title:
fails to boot on vmware fusion
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
If this is the same bug as https://bugs.launchpad.net/bugs/483890, and
I'm not sure that it is, then it is still in lucid. Lucid is apparently
better, but not fixed.
I ran some tests over the last few days. Using the script I attached to
483890 I can reproduce the problem in seconds on karmic.
beta1 fresh distribution works for both i386 and amd64. However,
updates from 9.10 still do not.
--
lucid installation fails on grub
https://bugs.launchpad.net/bugs/530183
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Apologies for the false alarm. The problem is not in distributed emacs
at all but rather in personal code. (I've been carrying around a copy
of vc-svn.el since before it was included.)
I'd mark this bug as not a bug if I could see how. If you know how,
please feel free to do so.
--
emacs
*** This bug is a duplicate of bug 444563 ***
https://bugs.launchpad.net/bugs/444563
I'm including a copy of the script I'm using to reproduce the problem.
It assume you have a volume group named v4c of at least 8G available.
** Attachment added: script for reproducing a similar problem
*** This bug is a duplicate of bug 444563 ***
https://bugs.launchpad.net/bugs/444563
I'm seeing similar problems in a similar situation. I'm not doing
backups but I am creating and removing a sequence of lv's and snapshots.
Mine are on amd64 karmic. I don't believe I've seen these on lucid
*** This bug is a duplicate of bug 444563 ***
https://bugs.launchpad.net/bugs/444563
I'm not convinced this is the same bug either. Mine is more like yours
than like #444563.
--
Race conditions when creating multiple LVM2 snapshots
https://bugs.launchpad.net/bugs/483890
You received this
I'm seeing similar problems in a similar situation. I'm not doing
backups but I am creating and removing a sequence of lv's and snapshots.
Mine are on amd64 karmic. I don't believe I've seen these on lucid with
the same code, (which only proves I haven't done enough testing :).
If this is a
Public bug reported:
Binary package hint: lvm2
Create 2 logical volumes on the same volume group.
On each of these logical volumes, create one snapshot each.
Now attempt to remove them all using something like lvremove -f vg.
I expect them all to be removed. What I see instead is:
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/40372232/Dependencies.txt
--
lvremove fails
https://bugs.launchpad.net/bugs/533493
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
Binary package hint: debian-installer
When installing a machine fresh using the server images, (x86 or amd64),
I'm presented with a dialog window asking if I want to skip installing
grub. If I answer yes, the installation fails within seconds for lack
of grub installation.
Here it is again: Couldn't parse output from `svn status -v'
Reverified - problem still exists as of Sat Jan 9 09:47:00 PST 2010
** Changed in: emacs23 (Ubuntu)
Status: Incomplete = New
** Description changed:
Binary package hint: emacs23
r...@irish lsb_release -rd
Public bug reported:
Binary package hint: emacs23
r...@irish lsb_release -rd
Description:Ubuntu lucid (development branch)
Release:10.04
To reproduce, load subversion, load emacs, check something out from
subversion, visit one of those files in emacs.
In the same directory, visit a
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/36836278/Dependencies.txt
--
emacs subversion support fails
https://bugs.launchpad.net/bugs/497161
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
34 matches
Mail list logo
