During a maintenancerun this morning, a large portion of my servers
promped to install grub to disks, but a few of them still suffered from
the can't answer 'no'-bug, so i was forced to answer 'yes' to the
question and not install / update the MBR.
--
You received this bug notification because
Bug is fixed for me. On upgrade it now prompts me 'GRUB has been
installed to a device that is no longer present', after which i get a
list of devices to install GRUB to. Thanks!
--
Option 'No' at question 'Continue without installing GRUB?' does nothing.
Forced to answer 'Yes'.
Great to see progress on this 'bug'.
For what it's worth, this is how i managed to produce the situation in
the first place; i installed Lucid (server, amd64) in a VM. Installing
Grub bailed out in the installer because of VirtIO weirdness and i had
to select 'do not install any bootloader'. Then
Public bug reported:
Binary package hint: grub2
This bug is in the debconf screens of grub-pc.
During upgrades it asks 'You chose not to install GRUB to any devices. [
... ] Continue without installing GRUB?' and offers two options: Yes or
No. Answering 'No' does nothing and brings you back to
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/48435069/Dependencies.txt
--
Option 'No' at question 'Continue without installing GRUB?' does nothing.
Forced to answer 'Yes'.
https://bugs.launchpad.net/bugs/580408
You received this bug notification because you are a
This bug is hitting me too and it's quite annoying. Any chance on getting the
fix out soon?
Rows are now returned unaffected by any sorting order, in the order i've
inserted them.
--
ORDER BY DESC in InnoDB not working
https://bugs.launchpad.net/bugs/479250
You received this bug notification
This bug is hitting me too and it's quite annoying. Any chance on getting the
fix out soon?
Rows are now returned unaffected by any sorting order, in the order i've
inserted them.
--
ORDER BY DESC in InnoDB not working
https://bugs.launchpad.net/bugs/479250
You received this bug notification
Public bug reported:
Hardy and possibly Intrepid are affected by a bug in rpc.mountd's
--manage-gids option.
This was fixed upstream somewhere between nfs-utils version 1.1.3 and
1.1.4. The problem is that mountd in nfs-utils = 1.1.2 returns a
negative response if there are no GIDs found for
** Attachment added: Patch to mountd/cache.c fixing --manage-gids problem.
http://launchpadlibrarian.net/36194311/mountd_cache.diff
--
An issue with rpc.mountd's --manage-gids option makes NFS operations hang
https://bugs.launchpad.net/bugs/489499
You received this bug notification because
This issue seems related to the device once being used for swap.
I'm experiencing /exactly/ the same problem as you describe above.
I've swapoff'd the md-device, but still i'm unable to stop the array
alltogether or remove a member from it.
Everything results in EBUSY.
Ubuntu 6.06.2 LTS
Linux
JFYI, i installed Jaunty Release Candidate on April 17th, updated to
what's available today (19th). Audio stopped working.
One of the comments state the mixer-element 'Audigy Analog/Digital Output Jack'
needs to be switched -off-.
On my system it's the complete oposite, i have to switch it -on-
Public bug reported:
Binary package hint: apache2.2-common
Hi,
It appears you *need* to source /etc/apache2/envvars before being able to
interact with /usr/sbin/apache2 from the shell.
This is annoying.
| $ /usr/sbin/apache2 -S
| apache2: bad user name ${APACHE_RUN_USER}
| $ .
Public bug reported:
Binary package hint: apache2.2-common
Hi,
It appears you *need* to source /etc/apache2/envvars before being able to
interact with /usr/sbin/apache2 from the shell.
This is annoying.
| $ /usr/sbin/apache2 -S
| apache2: bad user name ${APACHE_RUN_USER}
| $ .
I'm Perl afflicted. That's probably why i tend to type ; after each
line. It doesn't hurt though, in the shellscript.
--
apt cron.daily script doesn't check value-existence
https://bugs.launchpad.net/bugs/223502
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Attached is a patch that fixes a daily cron message on systems that have
gconftool installed but do not have values for /system/http_proxy/* set.
Result is now:
| Subject: Cron [EMAIL PROTECTED] test -x /usr/sbin/anacron || ( cd /
run-parts --report /etc/cron.daily )
|
|
** Attachment added: Patch against cron.daily/apt
http://launchpadlibrarian.net/13979915/cron_daily_apt.diff
--
apt cron.daily script doesn't check value-existence
https://bugs.launchpad.net/bugs/223502
You received this bug notification because you are a member of Ubuntu
Bugs, which is
16 matches
Mail list logo
