*** This bug is a duplicate of bug 1641328 ***
https://bugs.launchpad.net/bugs/1641328
Use the re-ordering of hosts line in nsswitch.conf posted by Mark Tearle in
#1641328:
files mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] dns
This is better than removing "resolve
*** This bug is a duplicate of bug 1641328 ***
https://bugs.launchpad.net/bugs/1641328
** This bug has been marked a duplicate of bug 1641328
Ordering of mdns4_minimal and resolve in /etc/nsswitch.conf causes mDNS
lookups to fail -- breaks network printing
--
You received this bug
This bug still exists in Ubuntu 12.04 LTS and (re)reported in Red Hat
Bugzilla's as bug 749366, so I believe we need a new bug report to get
a fix for this into a 12.04.x point release?
If Andrei's patch to increase bitpool in bluetooth daemon fixes this
problem then the problem _is_ in bluez
To find some way to get MAAS to wait longer, I I initially looked in
/usr/share/pyshared/cobbler/modules/sync_post_restart_services.py and
found code that looks like it uses subprocess_sp() from
/usr/share/pyshared/cobbler/utils.py to run service dnsmasq restart.
Perhaps the code for restarting
To find some way to get MAAS to wait longer, I I initially looked in
/usr/share/pyshared/cobbler/modules/sync_post_restart_services.py and
found code that looks like it uses subprocess_sp() from
/usr/share/pyshared/cobbler/utils.py to run service dnsmasq restart.
Perhaps the code for restarting
Thanks Julian for giving us some insight into the cause of this issue!
If you have some insight into the command sequence MAAS is running then
I hope you can help identify a workaround to enable adding nodes or
create a mini-Howto manually remove a partially added node (from
Cobbler, dnsmasq, etc
Thanks Julian for giving us some insight into the cause of this issue!
If you have some insight into the command sequence MAAS is running then
I hope you can help identify a workaround to enable adding nodes or
create a mini-Howto manually remove a partially added node (from
Cobbler, dnsmasq, etc
Newer versions of xmltv resolve this (and other bugs), as reported by O.
Emmerson on 2009-11-02.
Fixes committed in packages built from xmltv source =0.5.57
eg: The binary packages for Maverick
https://launchpad.net/ubuntu/maverick/+source/xmltv installed (via manual
download) into Lucid today
Fixes committed in packages built from xmltv source =0.5.57
eg: The binary packages for Maverick
https://launchpad.net/ubuntu/maverick/+source/xmltv installed (via manual
download) into Lucid today worked for me to successfully run tv_grab_uk_rt
--configure then (after checking ~/.xmltv/cache/
I found libparse-recdescent-perl is a dependency package of xmltv-util
0.5.57-3, so I needed to install the version from Lucid before I could complete
the manual install of the xmltv packages from Maverick.
Any one else reading this bug report may be looking for a copy-n-paste solution
that
I saw a repeat of this issue after upgrade to lucid and installing
recent kernel update to 2.6.32.22.23
On my system I found that jockey-common (0.5.8-0ubuntu8) recommends
nvidia-common (0.2.23).
Joel Cross's suggestion (#4) to remove nvidia-common worked for me, so I could
then successfully
** Tags added: livecd liveusb unionfs
--
kernel BUG at /build/buildd/linux-2.6.24/fs/attr.c:138!
https://bugs.launchpad.net/bugs/182765
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
*bump*
I confirm that I have exactly the same problem as Adam J Richardson when
attempting to update a LiveUSB 8.04 install using hard-updates source
to try and give me a system that has software versions at least
equivalent to (K)Ubuntu 8.04.1 install.
I too followed the instructions from
13 matches
Mail list logo
