[Bug 337377] [NEW] please restore netselect package: it's _not_ debian-specific
Public bug reported: Binary package hint: netselect As described here: https://bugs.launchpad.net/ubuntu/+source/netselect/+bug/275280 the netselect package was removed in intrepid. The justification is mistaken: while the netselect-apt package that depends upon netselect is debian-specific and is better off omitted (if not entirely rewritten), netselect itself is a general tool with nothing debian-specific about it. The problems that omitting it were meant to fix can be fixed entirely by continuing to omit netselect-apt while putting netselect back in. ** Affects: netselect (Ubuntu) Importance: Undecided Status: New -- please restore netselect package: it's _not_ debian-specific https://bugs.launchpad.net/bugs/337377 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/listinfo/ubuntu-bugs
[Bug 241340] [NEW] epdfview package doesn't provide pdf-viewer
Public bug reported: Binary package hint: epdfview The package isn't marked as providing the virtual package pdf-viewer. ** Affects: epdfview (Ubuntu) Importance: Undecided Status: New -- epdfview package doesn't provide pdf-viewer https://bugs.launchpad.net/bugs/241340 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/listinfo/ubuntu-bugs
[Bug 148698] Re: network interface numbers weirdness
*** This bug is a duplicate of bug 145382 *** https://bugs.launchpad.net/bugs/145382 ** This bug has been marked a duplicate of bug 145382 [Gutsy] broken 70-persistent-net.rules -- network interface numbers weirdness https://bugs.launchpad.net/bugs/148698 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 148727] yaird's Templates.cfg refer to /etc/console/boottime.kmap. In ubuntu, it's under /etc/console-setup
Public bug reported: Binary package hint: yaird Yaird's cryptsetup and cryptsetup_luks templates within Templates.cfg expect boottime.kmap.gz or boottime.kmap to be under /etc/console, but it's under /etc/console-setup (this was also true in feisty.) ** Affects: yaird (Ubuntu) Importance: Undecided Status: New -- yaird's Templates.cfg refer to /etc/console/boottime.kmap. In ubuntu, it's under /etc/console-setup https://bugs.launchpad.net/bugs/148727 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 148724] 1017_cryptsetup_blkid_test.patch results in failure with LVM2 within LUKS
Public bug reported: Binary package hint: yaird I created a LUKS partition, /dev/mapper/cryptdisk, used LVM2 to create a physical volume, volume group, and logical volume within it, intending it to be an encrypted root partition. I used yaird to create a boot image, and wrote it to /boot along with an appropriate GRUB entry. (I'm skimming a complex procedure, but it's the same things that worked in feisty.) On booting, the yaird image correctly reports loading my keyboard settings, and prompts for the LUKS passphrase. On entry, it says: Unable to identify the filesystem on volume cryptdisk. Reenter, Ignore, Shell? Looking at the source, I see that 1017_cryptsetup_blkid_test.patch modifies the cryptosetup and cryptosetup_luks templates to run /sbin/blkid on the encrypted device. If blkid's output is the empty string, it concludes the luksOpen (in the LUKS case) failed. I haven't tested yet whether this is an effect of the LVM2 partition inside the LUKS, but on my working setup in feisty, blkid's output for /dev/mapper/cryptdisk _is_ null. There's output for the logical volume device under /dev/mapper, there's output for /dev/mapper/cryptoswap, which has its own entry in /etc/crypttab, but none for cryptdisk. ** Affects: yaird (Ubuntu) Importance: Undecided Status: New -- 1017_cryptsetup_blkid_test.patch results in failure with LVM2 within LUKS https://bugs.launchpad.net/bugs/148724 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 148698] Re: network interface numbers weirdness
I had a similar experience. The installer identified the wireless card as eth0 and the wired network interface on the motherboard as eth1. But on rebooting, I had no net access, as they had become eth2 and eth3. Ifconfig made clear what was happening, so a change to /etc/network/interfaces and an /etc/init.d/networking restart made for a quick fix, but this would have stumped a newbie. It'd be really nice if the installer created /etc/iftab entries for the identified network interfaces' MAC addresses so this didn't come up, though it's probably far too late for Gutsy. -- network interface numbers weirdness https://bugs.launchpad.net/bugs/148698 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 98955] Re: logd not running
My /var/log/boot contains only (Nothing has been logged yet.) and its datestamp is from early last month, when I installed Feisty. So I'm also experiencing logd apparently not running. -- logd not running https://bugs.launchpad.net/bugs/98955 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63429] [Edgy] qemu-make-debian-root hasn't worked since Debian Sarge, and not even then
Public bug reported: Binary package hint: qemu 0.8.2-0ubuntu1 installs /usr/sbin/qemu-make-debian-root, a script to debootstrap a working Debian system into a disk image that can be used in qemu. It fails first because of a reference to libsigc++-1.2-5c102, a package that existed in Debian Sarge, but not Debian Sid or Etch, let alone Ubuntu Edgy. The script includes this line: debootstrap --exclude=syslinux,at,exim,mailx,libstdc++2.10-glibc2.2,mbr,setserial,fdutils,info,ipchains,iptables,lilo,pcmcia-cs,ppp,pppoe,ppp oeconf,pppconfig,wget,telnet,cron,logrotate,exim4,exim4-base,exim4-config,exim4-daemon-light,pciutils,modconf,tasksel --include=aptitude,libsigc++-1.2-5c102 $DISTRO /tmp/mount.$$ $URL That causes this failure when trying to build sid, etch or edgy: E: Couldn't find these debs: libsigc++-1.2-5c102 I tried removing the --exclude and --include parameters from the debootstrap, and also a subsequent dpkg-remove line that also caused dependency problems. Then, with this invocation: sudo qemu-make-debian-root 200 edgy http://us.archive.ubuntu.com/ubuntu edgy the debootstrap looked good, but the script concluded thus: I: Configuring pcmciautils... I: Configuring console-setup... I: Configuring console-tools... I: Configuring ubuntu-minimal... I: Base system installed successfully. /usr/sbin/qemu-make-debian-root: 81: cannot open /tmp/mount.2285/etc/inittab: No such file 409185+0 records in 409185+0 records out 209502720 bytes (210 MB) copied, 2.11577 seconds, 99.0 MB/s Warning: edgy is not a block device Disk edgy: cannot get geometry Disk edgy: 406 cylinders, 16 heads, 63 sectors/track Old situation: Warning: The partition table looks like it was made for C/H/S=*/255/63 (instead of 406/16/63). For this listing I'll assume that geometry. Units = sectors of 512 bytes, counting from 0 Device BootStart End #sectors Id System edgy1 1192779 192779 83 Linux edgy2 0 - 0 0 Empty edgy3 0 - 0 0 Empty edgy4 0 - 0 0 Empty New situation: Units = sectors of 512 bytes, counting from 0 Device BootStart End #sectors Id System edgy163409247 409185 83 Linux edgy2 0 - 0 0 Empty edgy3 0 - 0 0 Empty edgy4 0 - 0 0 Empty Warning: no primary partition is marked bootable (active) This does not matter for LILO, but the DOS MBR will not boot this disk. Successfully wrote the new partition table Re-reading the partition table ... BLKRRPART: Inappropriate ioctl for device If you created or changed a DOS partition, /dev/foo7, say, then use dd(1) to zero the first 512 bytes: dd if=/dev/zero of=/dev/foo7 bs=512 count=1 (See fdisk(8).) Done. -- It did result in a file called edgy, but trying to use that in qemu resulted in qemu hanging after saying Booting from Hard Disk... Making a Debian Sid image (with an unmodified qemu-make-debian-root) resulted in the same messages and result. Finally, the script is written to create only the root user, and assigns the password 'root', i.e., it results in an installation unlike any conventional Ubuntu installation (though one could get the same results with debootstrap.) Perhaps an appropriate Ubuntuization would be to prompt for a login name and password, and to create an ordinary user in sudoers. ** Affects: qemu (Ubuntu) Importance: Undecided Status: Unconfirmed -- [Edgy] qemu-make-debian-root hasn't worked since Debian Sarge, and not even then https://launchpad.net/bugs/63429 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61485] Edgy Knot 3 i386 alternative install CD: did server install, got generic kernel
Public bug reported: After selecting a server install from the alternative installation CD, the generic kernel was installed instead of the server kernel. ** Affects: Ubuntu Importance: Untriaged Status: Unconfirmed -- Edgy Knot 3 i386 alternative install CD: did server install, got generic kernel https://launchpad.net/bugs/61485 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 61487] Edgy Knot 3 i386 alternative install CD: requested Dvorak during server install, got QWERTY
Public bug reported: Did a server install from the Edgy Knot 3 i386 alternative install CD. Requested Dvorak. After installation, the active keymapping in the console was QWERTY. Requesting Dvorak during a text installation of Ubuntu from the Knot 3 i386 alternative CD works -- the keymapping is Dvorak both in Gnome and in the virtual consoles. ** Affects: Ubuntu Importance: Untriaged Status: Unconfirmed -- Edgy Knot 3 i386 alternative install CD: requested Dvorak during server install, got QWERTY https://launchpad.net/bugs/61487 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
