[Bug 1632601] Re: initramfs fails to bring up networking with multiple interfaces, even when an interface is specified
Workaround: In /etc/initramfs-tools/initramfs.conf, I simply set: IP=eth0 DEVICE=eth0 If my analysis is correct, DEVICE is ignored and I can simply use IP. If so, I think there are still at least two bugs here: Autodetection doesn't work with multiple interfaces (and it's clear from the code that it's _trying_ to support that use case), and the sample file has this misleading comment: # # DEVICE: ... # # Specify a specific network interface, like eth0 # Overridden by optional ip= bootarg # This makes it sound like DEVICE is used if ip= isn't set, but that's not true -- if ip= isn't set, and IP isn't set, DEVICE is overridden anyway. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632601 Title: initramfs fails to bring up networking with multiple interfaces, even when an interface is specified To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1632601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632601] [NEW] initramfs fails to bring up networking with multiple interfaces, even when an interface is specified
Public bug reported:
Discovered in Ubuntu 16.04.1 LTS
in initramfs-tools version 0.122ubuntu8.3
I expect that, when I set "DEVICE=eth0" in /etc/initramfs-
tools/initramfs.conf, my system will bring up DHCP on eth0, and ignore
any other interfaces on the system (nothing is plugged into eth1), so
that it can bring up dropbear and wait for me to SSH in and unlock my
root filesystem. This would also affect anything attempting to netboot
with this version of initramfs-tools.
Instead, it ignores my DEVICE line, and instead tries and fails to bring
up DHCP on a fictional interface called "eth0 eth1". This is caused by
_multiple_ bugs in /usr/share/initramfs-tools/scripts/functions.
I'd be sending a patch, but I'm not sure where to send it.
Here's a detailed breakdown:
If the 'ip' bootarg and $IP variable is undefined, then:
* It matches the case on line 285 of 'functions': ""|*|on|any|dhcp)
* It then matches the 'if' condition on line 288: if ! echo "${IP}" | grep -qc
'BOOTIF'; then
* So we execute: DEVICE="${IP#*:*:*:*:*:*}";
It's not at all obvious why that if statement is even there, since if
$IP was BOOTIF, it wouldn't match the given case branch. Continuing:
* Since $IP was empty, $DEVICE is now empty
* Since $DEVICE is empty, on line 295: DEVICE=$(all_netbootable_devices)
$DEVICE is now "eth0 eth1", which might be fine, except:
* On line 299: for dev in "${DEVICE}"; do
This loop would do the right thing -- it would loop through each
interface and try it in turn, and stop once one of them was configured
successfully -- except that, thanks to that quoting, that 'dev' variable
is not set progressively to 'eth0' and then 'eth1'. It is set once, to
the string "eth0 eth1".
That is clearly not what the rest of the script expects. This is
supposed to be the loop where it iterates over 'eth0' and then 'eth1' to
decide which of them to set DEVICE to, so the rest of this script can
understand the DEVICE variable. But instead, it tries to do silly things
like invoke dhclient on a fictional interface called "eth0 eth1",
instead of invoking dhclient once on each interface.
I don't know how to fix the bug where DEVICE is overridden even if the
ip bootarg is absent. Maybe that's the intended behavior? But to at
least fix autodetection, someone could just remove the quotes on $DEVICE
on line 299.
** Affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1632601
Title:
initramfs fails to bring up networking with multiple interfaces, even
when an interface is specified
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1632601/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205452] Re: Eclipse unusable in Kubuntu Saucy (almost immediate JVM segfault)
Problem still exists for me. Changing the GTK theme does not help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205452 Title: Eclipse unusable in Kubuntu Saucy (almost immediate JVM segfault) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1205452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205452] Re: Eclipse unusable in Kubuntu Saucy (almost immediate JVM segfault)
...and for what it's worth, a fresh download of Eclipse Kepler from eclipse.org works fine. Why is Ubuntu's Eclipse held back to 3.8? Maybe an upgrade would solve this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205452 Title: Eclipse unusable in Kubuntu Saucy (almost immediate JVM segfault) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1205452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1196667] Re: Please remove appmenu-gtk from Ubuntu
This has caused https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/126 Is there any way to either roll this back (so as not to break functionality), or anything on the roadmap to fix it properly? I'll take obsolete over gone any day. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1196667 Title: Please remove appmenu-gtk from Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appmenu-gtk/+bug/1196667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 776650] Re: Build qemu-kvm with native VDE support
I'd like to expand on Dwight's comments a bit. Qemu network cards have two sides, the side the VM sees (virtio is probably fastest, if you can get drivers for it), and the backend, which is how that's connected to anything else. Here are the backends it has: -net user. Dirt simple to set up. Pure user-mode networking -- the VM intercepts all requests the guest makes, and just does those again on the host. Doesn't need any special privileges, and for most purposes, it's basically just like having a NAT. It even has a bit of other scattered functionality, like a built in SMB server, so Windows machines can access the host filesystem. Not the fastest, though, and not terribly flexible. -net tap. This would be plenty for Dwight's use case. The host gets a tap interface, which is connected (as if via a crossover cable) to the guest -- with pretty much full networking capabilities. May need to run as root. With iptables, you can certainly set up forwarding, and let guest VMs talk to each other. You can run dnsmasq on the host to provide DHCP and DNS for the VMs. It's just slightly obnoxious, because this is one tap device per client. -net socket -- two modes here: TCP or UDP multicast. TCP lets you wire one NIC on one VM to another NIC on another VM -- basically, a crossover cable. You *could* build a VDE-like switch out of this, by having one VM connect directly to the host with TAP, and have it bridge to other VMs connected with the socket. But this is a pain -- you're basically building a switch out of a VM, which is hugely inefficient compared to VDE. Multicast probably isn't as pleasant -- I don't know enough about multicast to be sure, but it looks like this could end up broadcasting to the entire real network -- better than bridging, but not terribly secure. -net vde -- actual VDE support. VDE lets you do much more than what Dwight is asking for. You can create entire virtual networks, with functioning switches and everything, that aren't connected to the host at all -- and you can connect these to other VMs on other machines. Tonight, I wanted to play with UDP hole punching (http://en.wikipedia.org/wiki/UDP_hole_punching) and other NAT traversal stuff, but I don't have a spare router, and my desktop actually has a real Internet IP address (no NAT). VDE would've let me create as many virtual routers as I wanted, between as many virtual networks as I wanted, all virtualized inside my desktop. It's not just that bridging is a bad idea here, it's that it wouldn't even solve the problem -- the *whole point* is that I want to punch through to an otherwise inaccessible network. I should mention that vdekvm actually does not work for what I want to do, at least as far as I can tell. When I tell it to connect to a switch, it actually tries to create that switch and connect it to the host -- but I want a network that _isn't_ connected to the host! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/776650 Title: Build qemu-kvm with native VDE support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/776650/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 776650] Re: Build qemu-kvm with native VDE support
I'd like to expand on Dwight's comments a bit. Qemu network cards have two sides, the side the VM sees (virtio is probably fastest, if you can get drivers for it), and the backend, which is how that's connected to anything else. Here are the backends it has: -net user. Dirt simple to set up. Pure user-mode networking -- the VM intercepts all requests the guest makes, and just does those again on the host. Doesn't need any special privileges, and for most purposes, it's basically just like having a NAT. It even has a bit of other scattered functionality, like a built in SMB server, so Windows machines can access the host filesystem. Not the fastest, though, and not terribly flexible. -net tap. This would be plenty for Dwight's use case. The host gets a tap interface, which is connected (as if via a crossover cable) to the guest -- with pretty much full networking capabilities. May need to run as root. With iptables, you can certainly set up forwarding, and let guest VMs talk to each other. You can run dnsmasq on the host to provide DHCP and DNS for the VMs. It's just slightly obnoxious, because this is one tap device per client. -net socket -- two modes here: TCP or UDP multicast. TCP lets you wire one NIC on one VM to another NIC on another VM -- basically, a crossover cable. You *could* build a VDE-like switch out of this, by having one VM connect directly to the host with TAP, and have it bridge to other VMs connected with the socket. But this is a pain -- you're basically building a switch out of a VM, which is hugely inefficient compared to VDE. Multicast probably isn't as pleasant -- I don't know enough about multicast to be sure, but it looks like this could end up broadcasting to the entire real network -- better than bridging, but not terribly secure. -net vde -- actual VDE support. VDE lets you do much more than what Dwight is asking for. You can create entire virtual networks, with functioning switches and everything, that aren't connected to the host at all -- and you can connect these to other VMs on other machines. Tonight, I wanted to play with UDP hole punching (http://en.wikipedia.org/wiki/UDP_hole_punching) and other NAT traversal stuff, but I don't have a spare router, and my desktop actually has a real Internet IP address (no NAT). VDE would've let me create as many virtual routers as I wanted, between as many virtual networks as I wanted, all virtualized inside my desktop. It's not just that bridging is a bad idea here, it's that it wouldn't even solve the problem -- the *whole point* is that I want to punch through to an otherwise inaccessible network. I should mention that vdekvm actually does not work for what I want to do, at least as far as I can tell. When I tell it to connect to a switch, it actually tries to create that switch and connect it to the host -- but I want a network that _isn't_ connected to the host! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/776650 Title: Build qemu-kvm with native VDE support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/776650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 580242] Re: Kmail cannot send to groups
Slight problem there: The list has the right number of people, but with that plus sign view, it's also entirely blank addresses. I can't add them (or adding them has no effect), and don't seem to be able to drag them anywhere. -- Kmail cannot send to groups https://bugs.launchpad.net/bugs/580242 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 580242] [NEW] Kmail cannot send to groups
Public bug reported: Binary package hint: kdepim There are several related issues here: When attempting to send to a group, the group is not available for autocompletion. (This worked with the equivalent Distribution List in Kubuntu 9.10.) Selecting it in the Select Recipient dialog adds it as text to the to field -- which is not expanded at ANY point. Pressing send at this point results in a bounced email, as it was attempting to use the name of the list as an email address, without ever expanding to the actual contacts. That alone is a problem, but I dug a little deeper. Expanding the distribution list in Kontact yields what appears to be an empty list -- or rather, a list of seven empty recipients. I've attached a screenshot to illustrate this. Will someone please explain how it is that I have these applications open side-by-side, clearly talking about the same list, yet one can see it, and one can't? This is documented (somewhat) here, I think: http://userbase.kde.org/KAddressBook#Status_of_this_release That means someone at KDE decided that this severe of a regression was acceptable for a release. Really? I'm trying to be polite, but how does THAT make it out the door? ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: kmail 4:4.4.2-0ubuntu5 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Thu May 13 17:11:36 2010 ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: kdepim ** Affects: kdepim (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kmail lucid regression -- Kmail cannot send to groups https://bugs.launchpad.net/bugs/580242 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdepim in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 580242] Re: Kmail cannot send to groups
** Attachment added: screenshot.png http://launchpadlibrarian.net/48415248/screenshot.png ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/48414443/Dependencies.txt -- Kmail cannot send to groups https://bugs.launchpad.net/bugs/580242 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdepim in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 430416] Re: [KARMIC] Dell XPS 1330 does not mount SD card from built in card reader
I see more or less the same errors as fubarbundy: [ 298.600034] mmc0: Timeout waiting for hardware interrupt. [ 298.600044] sdhci: == REGISTER DUMP == [ 298.600053] sdhci: Sys addr: 0xd347e184 | Version: 0x0400 [ 298.600060] sdhci: Blk size: 0x7008 | Blk cnt: 0x0001 [ 298.600067] sdhci: Argument: 0x | Trn mode: 0x0013 [ 298.600074] sdhci: Present: 0x01ff0206 | Host ctl: 0x0001 [ 298.600081] sdhci: Power:0x000f | Blk gap: 0x [ 298.600088] sdhci: Wake-up: 0x | Clock:0x4007 [ 298.600095] sdhci: Timeout: 0x0009 | Int stat: 0x [ 298.600102] sdhci: Int enab: 0x02ff00cb | Sig enab: 0x02ff00cb [ 298.600109] sdhci: AC12 err: 0x | Slot int: 0x [ 298.600116] sdhci: Caps: 0x01e021a1 | Max curr: 0x0040 [ 298.600120] sdhci: === [ 298.603253] mmc0: error -110 whilst initialising SD card I have hibernation enabled, but this is after a fresh boot, no suspending involved. This is an XPS M1530, and it worked fine for the past two or three kernels. -- [KARMIC] Dell XPS 1330 does not mount SD card from built in card reader https://bugs.launchpad.net/bugs/430416 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 430416] Re: [KARMIC] Dell XPS 1330 does not mount SD card from built in card reader
Well, that's amazingly inconsistent. Sometimes, nothing happens until I remove the card (30 seconds or so later), in which case I get an error about the card being removed. Sometimes, I get the above message. I then tried to plug this card into an HP PhotoSmart printer, which gave me an error. I then plugged it back into this laptop -- works fine! What? -- [KARMIC] Dell XPS 1330 does not mount SD card from built in card reader https://bugs.launchpad.net/bugs/430416 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 201887] Re: Slim USB Apple Keyboard not working correctly when pressing the numlock key
Offtopic, but any chance that the mapping of command/option is one of the quirks? Being able to have alt and win be where my muscle memory thinks they are, without having to switch manually when switching keyboards (I've got a PC laptop that I plug this keyboard into), would be awesome. Unfortunately, there's not much to be done about the fn key, without hacking the firmware... -- Slim USB Apple Keyboard not working correctly when pressing the numlock key https://bugs.launchpad.net/bugs/201887 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 236148] Re: Nexuiz 2.4.2
Not even 2.4.1 -- it's 2.4-1, which I take to mean 2.4, Ubuntu patch 1. The problem is, even if the game is playable, there's a nag screen which I haven't found a way to turn off short of modifying the code. By nag screen, I mean something which flies through the screen, blocking your view, while you're playing -- not something you can click through. So the package, as it stands, is plainly broken -- it should either NOT nag the player (at least for singleplayer), or it should be the current version. The common suggestion on the forums is to uninstall the Ubuntu package and download the zipfile. The only other fix that I can see is to upgrade to Intrepid -- the obvious problem being that Nexuiz will itself likely upgrade at some point during the Intrepid cycle. -- Nexuiz 2.4.2 https://bugs.launchpad.net/bugs/236148 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 254544] [NEW] Ruby1.9 is hopelessly out of date
Public bug reported: Binary package hint: ruby1.9 $ grep DESC /etc/lsb-release DISTRIB_DESCRIPTION=Ubuntu 8.04.1 $ ruby1.9 --version ruby 1.9.0 (2007-12-25 revision 14709) [x86_64-linux] $ svn info http://svn.ruby-lang.org/repos/ruby/tags/v1_9_0_0 (snip) Last Changed Rev: 14711 Last Changed Date: 2007-12-25 10:27:31 -0600 (Tue, 25 Dec 2007) That's actually two revisions behind the tag for the initial 1.9.0 release. But 1.9.0 is a moving target: $ svn info http://svn.ruby-lang.org/repos/ruby/tags/v1_9_0_3 Last Changed Rev: 18218 Last Changed Date: 2008-07-25 08:26:23 -0500 (Fri, 25 Jul 2008) For those keeping score, this means the Ubuntu package is exactly seven months behind upstream, on a developer release. I'm really not sure I see the point of keeping a known stable version here -- if that's what you want, there's always Ruby 1.8, which is even more out-of-date, but at least there's a point to keeping it stable. By hopelessly out of date, I mean that I know of at least one third- party library which depends on a bugfix introduced in more recent versions of Ruby1.9. Possible resolutions: - Update Ruby 1.9 (or point me to a repository) - Remove Ruby 1.9 (what's an unstable dev branch doing in an LTS release?!) - Provide a -installer package to ease usage of SVN (I'll write it if needed) ** Affects: ruby1.9 (Ubuntu) Importance: Undecided Status: New -- Ruby1.9 is hopelessly out of date https://bugs.launchpad.net/bugs/254544 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 201887] Re: Slim USB Apple Keyboard not working correctly when pressing the numlock key
I'm not sure what the clear key does, though a quick Google search shows: http://www.google.com/search?q=os+x+clear+keyie=UTF-8oe=UTF-8 The link doesn't work well for me, but the Google summary of the first result includes: The Clear key, of course, acts like the clear key on a calculator... In other words, whatever it is supposed to do, it is NOT supposed to act like a numlock. I would argue that in this case, we should only allow the directional mode for users sophisticated enough to go searching for it -- remember, there is no visual indication that numlock is on or off, and the functions it performs (other than numbers) are not visible anywhere on the keyboard. So any new user who happens to press the clear key will now think something along the lines of My computer is broken! Having the option of directional arrows is nice, but for this keyboard, leave it off by default. -- Slim USB Apple Keyboard not working correctly when pressing the numlock key https://bugs.launchpad.net/bugs/201887 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 62195] Re: edgy update-grub destroys kopt
Thomas, not every instance of UUIDs not being recognized -- at least in the way we're discussing here -- is a bug. Sometimes, it is difficult or impossible to recognize them. Sometimes, it makes no sense to recognize them anyway. Look at the examples which the script already deliberately ignores. Crypto, for example -- you can create a mapping of /dev/mapper/some_name to an underlying UUID device. So, by the time you're trynig to mount that, you actually do want to open it by device name -- because that device name already corresponds to a real UUID device, so you already have all of the benefits of that. RAID is another example, for pretty much the same reasons. /dev/md0, or /dev/md_d0p1, are names that the admin creates, which map (somehow) to underlying block devices. The problem is, a simple regex/glob looking for known patterns is not enough. Some people compile custom kernels. Some people don't use initramfs. Some people might just be using a devicename you hadn't thought of. Either way, by the time someone's digging in menu.lst to disable the UUIDs, it seems reasonable to assume they know what they're doing. So yes, sometimes UUIDs not being recognized are their own bug, but not always. No matter how perfect we get the UUID detection, there should always be a way to disable that. -- edgy update-grub destroys kopt https://bugs.launchpad.net/bugs/62195 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 223245] Re: Konsole line spacing too large
It's not a bug that the spacing is different. It is a bug that there's no way to change it. -- Konsole line spacing too large https://bugs.launchpad.net/bugs/223245 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 62195] Re: edgy update-grub destroys kopt
From what I could tell, the UUID was simply never tracked down. I didn't investigate too much -- net user-visible result is, the machine hangs in the initramfs for several minutes before it finally concludes that it couldn't find anything to mount the root filesystem with. It could be that the UUID code doesn't know to track RAID at all, and only looks at devices that were available at kernel boot time, before the initramfs? What I can tell you is that they're just about completely redundant for RAID configurations, among other things. If I already have an mdadm.conf which I'm using to build the cluster -- or a crypttab which I'm using to build the md-crypt device -- or even some md kernel autodetection, based on UUIDs and metadata stored in the physical volumes... In all of these cases, the actual device I am mounting is going to be the same, every time, as it is hardcoded *somewhere* -- the underlying physical volumes may or may not have been setup by UUID. If they have, then why do UUID stuff twice? If they're setup by /dev/sd*, then there's not much point in using UUIDs higher up the chain. As for assigning someone else to the bug, at the very least, it was an email that I found in the source file in question. Still, if I wasn't supposed to do that, I apologize. -- edgy update-grub destroys kopt https://bugs.launchpad.net/bugs/62195 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 113658] Re: When apt-cacher is used, Update-Manger fails (not #78673 duplicate)
Still not fixed, upgrading from 7.10 to 8.04. What's weird is that using a proxy worked fine with the graphical updater -- this only affects my server. I have bandwidth to spare, but right now, none of the mirrors do. Oh well -- looks like that's 2 gigs more bandwidth wasted because of this bug. (Yes, I could modify my sources.list, and then modify it back later -- and I remember the GUI tool not liking a particularly different sources.list.) -- When apt-cacher is used, Update-Manger fails (not #78673 duplicate) https://bugs.launchpad.net/bugs/113658 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 62195] Re: edgy update-grub destroys kopt
Still exists in Hardy, a year and a half after first reported. Just spent the past hour or two figuring out that this was (yet again!) the issue, and then re-hacking update-grub (as my version had, of course, been nuked by the system update) Is anyone paying attention? Where should I send my patch, if not this bug report? ** Attachment added: patch.hardy http://launchpadlibrarian.net/1303/patch.hardy -- edgy update-grub destroys kopt https://bugs.launchpad.net/bugs/62195 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 62195] Re: edgy update-grub destroys kopt
Does it help to assign to a person? (And am I allowed to do so?) ** Changed in: grub (Ubuntu) Assignee: (unassigned) = Steve Langasek (vorlon) -- edgy update-grub destroys kopt https://bugs.launchpad.net/bugs/62195 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 201887] Re: Slim USB Apple Keyboard not working correctly..
Tommy, probably way too late, but I thought I'd mention, for the record: When you type: sudo echo 2 /wherever Bash sees: (sudo echo 2) /wherever What you probably want is something like sudo su -, then you can just edit it. Or echo 2 | sudo tee /wherever will work, too. I still want to know where the best place to set this is, though -- I suspect it would be somewhere in udev.d, but i really don't know my way around that. For now, I'm sticking it in rc.local, so I don't forget. -- Slim USB Apple Keyboard not working correctly.. https://bugs.launchpad.net/bugs/201887 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 62195] Re: edgy update-grub destroys kopt
Oh, and let's not forget -- menu.lst now lies. It provides a number of options, with instructions on how to use them -- which are then messed with by update-grub. And update-grub, by the way, contains a hardcoded switch statement -- looks like /dev/md[0-9] is now supported. Great. I run a partitioned raid, which means the raid device is /dev/md_d0, and the actual partition is /dev/md_d0p2. I can now look forward to an upgrade, every now and then, requiring manual intervention to keep my system bootable. Attaching a patch for gutsy. Here's the essential problem: Even assuming the uuid stuff works flawlessly, every time (which would be nice), and even assuming nobody ever wants to manually set a device name, there are certain devices which apparently aren't detected by uuid. Rather than having a list of device names known to work by uuid, the update-grub script instead assumes that anything it doesn't recognized as incompatible with uuid is, in fact, compatible. That's just reckless. Unfortunately, I don't know enough about how things are looked up by uuid to know exactly which devices are supported, and which aren't, or how update-grub should know that. And I do think that at the very least, a manual disable should be allowed. ** Attachment added: patch.gutsy http://launchpadlibrarian.net/13411558/patch.gutsy -- edgy update-grub destroys kopt https://bugs.launchpad.net/bugs/62195 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 62195] Re: edgy update-grub destroys kopt
Also: I agree that /dev/foo is error-prone, for auto-generated /dev/sd* corresponding to physical devices. However, my /boot is by UUID just fine, and the RAID device is also assembled by UUID. By the time we get to RAID, LVM, or simple custom device-mapper stuff, it's already pretty much a user-defined device name, hardcoded in a config file. -- edgy update-grub destroys kopt https://bugs.launchpad.net/bugs/62195 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 61463] Re: Script that are using bash could be broken with the new symlink
Steve, short answer, yes, you should tell IBM that their software sucks. Or, specifically, that it's relying on a very dangerous and WRONG assumption, and that it's trivial for them to fix. It should not be the distro's job to fix IBM's bugs. -- Script that are using bash could be broken with the new symlink https://bugs.launchpad.net/bugs/61463 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 145548] Re: [UNMETDEPS] okular has unmet dependencies
*** This bug is a duplicate of bug 131405 *** https://bugs.launchpad.net/bugs/131405 Looks as though there is a version of libpoppler, for qt4, but it's not libpoppler1. Also looks like this needs kde4, so should probably be removed until that's available in Kubuntu (or moved to the kde4 repository). -- [UNMETDEPS] okular has unmet dependencies https://bugs.launchpad.net/bugs/145548 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 154190] We're sorry, the upgrade tool crashed.
Public bug reported: Binary package hint: update-manager Traceback (most recent call last): File /tmp/kde-root/adept_managerB34mqa.tmp-extract/dist-upgrade.py, line 59, in module app.run() File /tmp/kde-root/adept_managerB34mqa.tmp-extract/DistUpgradeControler.py, line 1346, in run self.fullUpgrade() File /tmp/kde-root/adept_managerB34mqa.tmp-extract/DistUpgradeControler.py, line 1312, in fullUpgrade if not self.askDistUpgrade(): File /tmp/kde-root/adept_managerB34mqa.tmp-extract/DistUpgradeControler.py, line 720, in askDistUpgrade if not self._checkFreeSpace(): File /tmp/kde-root/adept_managerB34mqa.tmp-extract/DistUpgradeControler.py, line 634, in _checkFreeSpace st = os.statvfs(d) OSError: [Errno 2] No such file or directory: '/redkey/boot' I can attach more, but I think this answers it: The partition on which my /boot resides (which /boot symlinks to) was not mounted. This is a bug, because it should not be CRASHING, it should be giving me a meaningful error and the opportunity to correct the problem. ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New -- We're sorry, the upgrade tool crashed. https://bugs.launchpad.net/bugs/154190 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 144104] pysol-sound-server should be updated for python2.5
Public bug reported: Binary package hint: pysol-sound-server It installs one file to /usr/lib/python2.4/site- packages/pysolsoundserver.so However, I do not have python2.4 installed; I'm using python2.5, and so is pysol. Thus, pysol cannot enable sound. ** Affects: pysol-sound-server (Ubuntu) Importance: Undecided Status: New -- pysol-sound-server should be updated for python2.5 https://bugs.launchpad.net/bugs/144104 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 92749] Re: bcm43xx_microcode5.fw not available or load failure on starting
Maybe I should open a new bug instead for this... But maybe you should have the bc43xx kernel driver depend on the bc43xx firmware as a Debian package itself? Then modify the bc43xx-fwcutter program to create a simple Debian package and install that by default, rather than just dump the firmware files where the kernel expects them? Better if we can make a good interface for when a broadcom card is detected -- in that case, maybe let bc43xx.ko be included, but as soon as we get a log message about missing firmware (assuming it found a card), we ask the user if they want bc43xx-fwcutter, then immediately download it and run it -- hopefully it can download needed firmware on its own, if the user doesn't have the driver. Even better if we can do this in a generic way, so bc43xx-fwcutter becomes fwcutter, or just binary-grabber or something, to handle similar situations in the future. (I'm assuming that eventually, either Broadcom will cave and release the firmware at least free as in beer, or we'll have free/open firmware instead.) -- bcm43xx_microcode5.fw not available or load failure on starting https://bugs.launchpad.net/bugs/92749 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 61850] 63 megs of source archives...
I'm trying my best to be polite, because this bug has been open for over a year now... Can someone provide a bit of status here? Is this intended to be fixed in Gusty? Is there a reason it can't be fixed in Feisty? Would it be at all helpful for me to post a patch of my changes, when I'm done? -- Kexi cannot access PostgreSQL databases anymore https://bugs.launchpad.net/bugs/61850 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
