Won't that create a bunch of eth0:0 eth0:1 eth0:2 interfaces? I want a
single interface with multiple addresses (which it partially gives me
now)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1070893
Multiple IPv6 addresses don't work with a single eth0 and I don't want
hundreds of eth0:99. The up' command is at least partially supported by
man interfaces - but it only seems to run the first seven. Bug 508996
seems related.
--
You received this bug notification because you are a member of
Aha! I figured it out.
The address line configured :7, but then an up command later tried to
start 7 again, and it failed with:
SIOCSIFADDR: File exists
Failed to bring up eth0.
Removing the duplicate line fixes the problem.
So this issue is more that ifupdown stops processing when it
Public bug reported:
I have an /etc/network/interfaces that looks like this:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo eth0
iface lo inet loopback
# The
** Package changed: ubuntu = ifupdown (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1070893
Title:
not all ipv6 addresses are brought up on boot
To manage notifications about this bug go
Has anyone been able to get this to work on 10.04-1 x64? I had it
working in 32 mode, but now I can't seem to get it to work on the Sony
VAIO VPCL135FX. My Xorg.log shows:
(II) config/udev: Adding input device Nextwindow Fermi Touchscreen
(/dev/input/event10)
(**) Nextwindow Fermi Touchscreen:
I had this problem, trying to boot Ubuntu 10.04 from a mirrored GPT
system, failed until I moved var back to the / partition. Then it worked
fine.
--
ureadahead requires /var on root filesystem
https://bugs.launchpad.net/bugs/523484
You received this bug notification because you are a member of
Installing python-simplejson fixed this error for me.
--
loggerhead needs a hard dependency on simplejson
https://bugs.launchpad.net/bugs/586611
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I'm now getting this on a non-Nvidia machine:
r...@clientdisplay0018:~# lspci
00:00.0 Host bridge: Intel Corporation 82G35 Express DRAM Controller (rev 03)
00:02.0 VGA compatible controller: Intel Corporation 82G35 Express Integrated
Graphics Controller (rev 03)
00:02.1 Display controller: Intel
Public bug reported:
Binary package hint: xserver-xorg-video-nouveau
My beta 2 install of 10.04 won't do anything but boot into failsafe
mode. However, it appears, based on the logs I see in /var/log/Xorg*,
that it's not even trying anymore to use nouveau. I tried deleting
xorg.conf.failsafe,
** Attachment added: kernel message log
http://launchpadlibrarian.net/44168503/messages
--
xorg starts in failsafe mode repeatedly with nouveau
https://bugs.launchpad.net/bugs/563191
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here is the failsafe log, but it is probably not very helpful; X doesn't
even seem to really try to use nouveau anymore, and there's no Xorg.conf
to edit.
** Attachment added: Failsafe log
http://launchpadlibrarian.net/44168828/Xorg.failsafe.log
--
xorg starts in failsafe mode repeatedly
Removing quiet splash from grub's defaults didn't change this either.
--
xorg starts in failsafe mode repeatedly with nouveau
https://bugs.launchpad.net/bugs/563191
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
apport information
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/44174848/CurrentDmesg.txt
--
xorg starts in failsafe mode repeatedly with nouveau
https://bugs.launchpad.net/bugs/563191
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Tags added: apport-collected
** Description changed:
Binary package hint: xserver-xorg-video-nouveau
My beta 2 install of 10.04 won't do anything but boot into failsafe
mode. However, it appears, based on the logs I see in /var/log/Xorg*,
that it's not even
apport information
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/44174849/Dependencies.txt
--
xorg starts in failsafe mode repeatedly with nouveau
https://bugs.launchpad.net/bugs/563191
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: GdmLog.txt
http://launchpadlibrarian.net/44174850/GdmLog.txt
--
xorg starts in failsafe mode repeatedly with nouveau
https://bugs.launchpad.net/bugs/563191
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
apport information
** Attachment added: GdmLog1.txt
http://launchpadlibrarian.net/44174852/GdmLog1.txt
--
xorg starts in failsafe mode repeatedly with nouveau
https://bugs.launchpad.net/bugs/563191
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: Lspci.txt
http://launchpadlibrarian.net/44174853/Lspci.txt
--
xorg starts in failsafe mode repeatedly with nouveau
https://bugs.launchpad.net/bugs/563191
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
apport information
** Attachment added: Lsusb.txt
http://launchpadlibrarian.net/44174857/Lsusb.txt
--
xorg starts in failsafe mode repeatedly with nouveau
https://bugs.launchpad.net/bugs/563191
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
apport information
** Attachment added: PciDisplay.txt
http://launchpadlibrarian.net/44174861/PciDisplay.txt
--
xorg starts in failsafe mode repeatedly with nouveau
https://bugs.launchpad.net/bugs/563191
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: ProcCpuinfo.txt
http://launchpadlibrarian.net/44174863/ProcCpuinfo.txt
--
xorg starts in failsafe mode repeatedly with nouveau
https://bugs.launchpad.net/bugs/563191
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: ProcInterrupts.txt
http://launchpadlibrarian.net/44174864/ProcInterrupts.txt
--
xorg starts in failsafe mode repeatedly with nouveau
https://bugs.launchpad.net/bugs/563191
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: ProcModules.txt
http://launchpadlibrarian.net/44174867/ProcModules.txt
--
xorg starts in failsafe mode repeatedly with nouveau
https://bugs.launchpad.net/bugs/563191
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: UdevDb.txt
http://launchpadlibrarian.net/44174869/UdevDb.txt
--
xorg starts in failsafe mode repeatedly with nouveau
https://bugs.launchpad.net/bugs/563191
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
apport information
** Attachment added: RelatedPackageVersions.txt
http://launchpadlibrarian.net/44174868/RelatedPackageVersions.txt
--
xorg starts in failsafe mode repeatedly with nouveau
https://bugs.launchpad.net/bugs/563191
You received this bug notification because you are a member of
apport information
** Attachment added: UdevLog.txt
http://launchpadlibrarian.net/44174949/UdevLog.txt
--
xorg starts in failsafe mode repeatedly with nouveau
https://bugs.launchpad.net/bugs/563191
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: Xrandr.txt
http://launchpadlibrarian.net/44174987/Xrandr.txt
--
xorg starts in failsafe mode repeatedly with nouveau
https://bugs.launchpad.net/bugs/563191
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
apport information
** Attachment added: setxkbmap.txt
http://launchpadlibrarian.net/44174992/setxkbmap.txt
--
xorg starts in failsafe mode repeatedly with nouveau
https://bugs.launchpad.net/bugs/563191
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: xdpyinfo.txt
http://launchpadlibrarian.net/44175001/xdpyinfo.txt
--
xorg starts in failsafe mode repeatedly with nouveau
https://bugs.launchpad.net/bugs/563191
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: xkbcomp.txt
http://launchpadlibrarian.net/44175038/xkbcomp.txt
--
xorg starts in failsafe mode repeatedly with nouveau
https://bugs.launchpad.net/bugs/563191
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm seeing this on an Atom 330 processor on an 10.04 upgrade.
It stops at the ureadahead line and doesn't continue any further.
I will boot a rescue CD and look at /etc/fstab for ideas.
--
init: ureadahead-other main process terminated with status 4
https://bugs.launchpad.net/bugs/484677
You
Ah, my actual problem was caused by bad /etc/fstab entries referring to
disks that were not attached; after commenting them out it boots
correctly.
--
init: ureadahead-other main process terminated with status 4
https://bugs.launchpad.net/bugs/484677
You received this bug notification because
This bug is happening to me on Hardy Heron. I'm using OpenVPN and I need
to add a search domain and a dns server line so that the internal VPN
hosts will resolve correcty, but when the VPN disconnects the internal
nameservers are left in /etc/resolv.con and not refreshed.
I'm using wicd instead
Weird. I'm actually getting a different issue now after a reboot cleared
things out - the original DHCP hostname and DNS address are staying in
resolv.conf, and the new server line is being added. After the OpenVPN
tunnel goes down, the VPN server stays in resolv.conf.
--
update-resolv-conf
This bug is happening to me on Hardy Heron. I'm using OpenVPN and I need
to add a search domain and a dns server line so that the internal VPN
hosts will resolve correcty, but when the VPN disconnects the internal
nameservers are left in /etc/resolv.con and not refreshed.
I'm using wicd instead
Weird. I'm actually getting a different issue now after a reboot cleared
things out - the original DHCP hostname and DNS address are staying in
resolv.conf, and the new server line is being added. After the OpenVPN
tunnel goes down, the VPN server stays in resolv.conf.
--
update-resolv-conf
With wicd this is working correctly, as long as I don't tell OpenVPN to
drop privileges to nobody/nogroup (because then running the downscript
will fail!).
I recommend changing update-resolv-conf's header to mention this gotcha,
as such:
# Parses DHCP options from openvpn to update resolv.conf
#
This CD did suspend, but never recovered. I was not able to get back
into the system after suspending without completely powering off.
--
Using suspend key results in suspend loop
https://bugs.launchpad.net/bugs/184960
You received this bug notification because you are a member of Ubuntu
Bugs,
I had a similar issue with 7.10 (installed correctly, wouldn't boot)
until I followed RedHat's recommendation and turned off I2O emulation:
http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/release-
notes/RELEASE-NOTES-x86-en.html
--
Dell PERC 2/SC (AMI Megaraid 466(?)) not working
Look at Jan 15 15:05:11 and environs:
messages.2.gz:Jan 15 15:04:26 tdickson-PC gnome-power-manager: (tdickson)
Suspending computer because the suspend button has been pressed
messages.2.gz:Jan 15 15:05:11 tdickson-PC gnome-power-manager: (tdickson)
Resuming computer
messages.2.gz:Jan 15
Public bug reported:
Binary package hint: gnome-power-manager
If I suspend Ubuntu 7.10 on 2.6.22-14-generic, when it resumes from
suspend, I have about enough time to login before it suspends again. It
continues this loop and I have to power cycle the machine to recover
(losing anything that was
Here is the lspci -v -v -n -n output.
** Attachment added: lspci -v -v -n -n
http://launchpadlibrarian.net/11468417/lspci-vvnn.log
--
Using suspend key results in suspend loop
https://bugs.launchpad.net/bugs/184960
You received this bug notification because you are a member of Ubuntu
Bugs,
Linux tdickson-desktop 2.6.22-14-generic #1 SMP Tue Dec 18 08:02:57 UTC
2007 i686 GNU/Linux
I don't have a current dmesg output (I'd need to reboot).
--
Using suspend key results in suspend loop
https://bugs.launchpad.net/bugs/184960
You received this bug notification because you are a member
This machine is an HP Pavilion Elite
--
Using suspend key results in suspend loop
https://bugs.launchpad.net/bugs/184960
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
45 matches
Mail list logo
