[02:08] <Chucrute301> hi guys
[02:08] <Chucrute301> this will be maked in ubuntu raring?
[02:08] <Chucrute301> https://bugs.launchpad.net/unity-greeter/+bug/932181
[02:08] <ubot2> Launchpad bug 932181 in unity-greeter (Ubuntu) "Unity Greeter - Update indicator menus so that they match the Unity Greeter style" [Critical,Triaged]
[02:10] <Chucrute301> anyone?
[02:10] <Chucrute301> ?????????
[13:28] <dakira> Live-CD problem: When a USB-Stick with persistent storage is used, /etc/udev/rules.d/70-persistent-net.rules gets a rule added to it on every new device connection. Installing from the stick will result in a copy of the file on the target system. So all network interfaces of all devices the stick was ever connected to, will be in the rules file. You interface names will be something like eth19 and wlan8. On some machines networking wouldn't
[13:28] <dakira> work at all until I deleted the rules. This can't be wanted behavior. Against which package should I file a bug?
[13:44] <xnox> dakira: well, it is the wanted behaviour. if you use two machines regularly with that stick you want it to be eth1 & eth2 for each machine respectuflly.
[13:45] <xnox> dakira: if you want the bug, file it against whichever package provides persistence. casper?!
[13:45] <TheLordOfTime> betcha it'll "Won't Fix" though
[13:51] <dakira> xnox: okay I see
[13:54] <dakira> xnox: I think the persistence is provided by an aufs mounted on the casper fs. filing the bug against aufs would be wrong though, I think
[13:54] <xnox> dakira: the more unplesant side-effect is taking a hard-drive and moving it to a new tower. then you need to remember to clear the persistent rules.
[13:55] <dakira> xnox: yeah.. but that's where I'd expect that. Not with a USB-key I massively use for installing Ubuntu and only use persistence on, so that I don't have to reenter the WiFi credentials.
[13:57] <ogra_> you could create an upstart job that just removes the file before the first network connection comes up and re-creates it
[13:57] <ogra_> or wipe it and force-cr6eate it
[13:58] <xnox> dakira: why do you have persistence on the usb key used for installing ubuntu? surely you know how to save one file on the usb-stick ;-) with the wifi password.
[14:12] <dakira> xnox: I was actually under the impression that the live usb stuff was for installing Ubuntu and that persistence on them, was so that you could save some settings you always need/want. If that isn't the case then the persistence feature doesn't make any sense to me ;)
[14:13] <xnox> dakira: persistance is meant for continued usage: e.g. you want to have usb-stick with ubuntu on it and go between home & work & internet cafe etc. and boot into your OS where ever you go.
[14:13] <TheLordOfTime> yup.
[14:13] <xnox> and use that on daily basis as your "roaming" profile / lightweight dual boot.
[14:13] <TheLordOfTime> as a result of persistence, it has to do what you've described, store each network interface as its own entry.
[14:13] <TheLordOfTime> eth1, eth2, eth3, etc.
[14:14] <xnox> dakira: without persistence, each time you reboot you are back to stock live-cd.
[14:14] <xnox> dakira: which is what you want - when using it as "live-cd for installations off a usb stick"
[14:15] <dakira> Well then my bug report would be, that ubiquity should be removed from the persistent usb-keys because if you install ubuntu from them you get the problems I described above.
[14:16] <xnox> dakira: no, you don't get any problems. ubiquity from usb-stick + persistence, still installs a bare stock system. Or are you saying that ubiquity, from persistence copies all 10 eth devices accross?
[14:16] <dakira> Actually.. I'd say this is a bug with ubiquity because it just should not copy the udev rules from the stick. There we have it ;)
[14:16] <xnox> well it doesn't.
[14:16] <dakira> xnox: it does
[14:16] <TheLordOfTime> it doesn't.
[14:17] <TheLordOfTime> i use a persistent USB for troubleshooting/diagnosis/datarecovery and i use it on at least a thousand systems.
[14:17] <TheLordOfTime> i also use it for installs on my systems.
[14:17] <xnox> dakira: it copies from squashfs. which is the underlying prestine image. Are you saying that on the third install the root device has 3 eth devices?
[14:17] <xnox> dakira: "shadows" of past usb-stick installs?
[14:18] <xnox> the original install images is not modified, and the persistance is stored on the overlay, which is not / should not be copied into the installed system. If something leaks, that means we regressed in ubiquity.
[14:19] <dakira> xnox: I'm saying that I found out about this because one of my installs had its wifi interface named wlan12, so I went out to investigate and saw that the udev rules file of the *installed vanilla Ubuntu* had all the interfaces of all machines in it, that the usb-stick *used to install* was ever connected to.
[14:19] <xnox> dakira: that's a bug in ubiquity then. please do `ubuntu-bug ubiquity` from one of the machines that has wlan12 on it.
[14:20] <xnox> dakira: thank you for taking time to explain this.
[14:20] <xnox> dakira: and please paste the bug # here.
[14:21] <dakira> xnox: I won't be able to do this today. I don't have the respective machines here.. I'll have to install it into a virtual machine to reproduce the problem.
[14:22] <xnox> dakira: if it is possible to boot usb+persistance in vm's multiple times =/
[14:23] <xnox> dakira: can you at least file a bug against ubiquity now, describing this? that previous machine's network devices leak to subsequent installs?
[14:23] <dakira> xnox: I just need to use the stick I have (which has 15+ devices in its stored rules).
[14:24] <dakira> xnox: I'm installing vbox right now.
[14:24] <xnox> ah =) ok.
[14:38] <dakira> I'll be back ;)
[15:17] <dakira> xnox: I'm filing the bug right now. It was a bit harder than I thought to boot a vbox from a USB stick ;)
[15:17] <dakira> xnox: but "good" news. The bug is there in the virtual machine, too.
[15:17] <xnox> yes, it is hard =)
[15:17] <xnox> \0/
[15:18] <xnox> great & I will have logs to see what's going on ;-)
[15:38] <dakira> here you go LP:8dUN13t3AiIP
[15:38] <dakira> arg ;) that was wring ;)
[15:38] <dakira> no c&p from the vm..
[15:39] <TheLordOfTime> is that the bug number...?
[15:39] <dakira> xnox:  LP:1077981
[15:39] <TheLordOfTime> LP Bug 1077981
[15:39] <ubot2> Launchpad bug 1077981 in ubiquity (Ubuntu) "udev rules from persistent usb-stick leak to installs" [Undecided,New] https://launchpad.net/bugs/1077981
[15:40] <xnox> dakira: thanks =)))
[15:41] <dakira> the above was a password that I now changed ;)
[15:44] <xnox> dakira: lol =)
[16:57] <alo21> hi..
[16:57] <alo21> I would like to create a patch
[16:59] <alo21> I run on terminal 'edit-patch fix158' and it gaves me ' No patches in series'. But in debian/patches there is a file called series. Also i think the patch system is quitl (but i am not sure)
[18:06] <TheLordOfTime> alo21, in debian/patches, is ther ea 'fix158' file?
[18:18] <jtaylor> alo21: you looked at picard-tools. maybe you want to comment on bug 1078012
[18:18] <ubot2> Launchpad bug 1078012 in picard-tools (Ubuntu) "Sync picard-tools 1.79-1 (universe) from Debian unstable (main)" [Undecided,Incomplete] https://launchpad.net/bugs/1078012
[18:19]  * TheLordOfTime thinks alo21 should be more responsive to questions...
[21:29] <melkor> I have a problem where ubuntu corrupts my /window 3
[21:30] <melkor> sorry...Ill finish
[21:30] <jtaylor> that would be an awfully specific bug :)
[21:32] <melkor> When I mount an external HDD it gets corrupted. This does not depend on the file system and appears to be specific to the hdd housing I am using.
[21:33] <melkor> I would like to report the bug, but I cannot do it from launchpad and I do not know what package to use ubuntu-bug.
[21:38] <jtaylor> probably linux
[21:40] <melkor> jtaylor: there is a linux package?
[21:40] <jtaylor> of course
[21:43] <melkor> Thanks for the heads up. I gotta move internet access.