[00:37] <bob3> tHE TRANSFER IS BLOCKED AT 25%
[00:37] <bob3> still plenty room in the usb
[00:40] <bob3> arraybolt3 what's the method to verify and copy anything missing?
[00:41] <arraybolt3> Agh, sounds like a bad USB drive. Or there's a LOT of data missing.
[00:41] <bob3> no error message, just no progress for 30min
[00:41] <arraybolt3> Er, a lot of data still being copied.
[00:41] <arraybolt3> Crud. The USB drive is probably bad. Do you have any other pendrives?
[00:42] <bob3> I do but even worse reputation ones
[00:43] <arraybolt3> It's not the reputation of the drives that matters necessarily, it's how much they've been used. If you've been using this one drive a lot because its the "good drive", you may have burnt it out. That's just what flash drives do after long enough.
[00:43] <bob3> wow it's frozen I cant even create a folder
[00:43] <bob3> this one was brand new
[00:43] <arraybolt3> Yeah, that's a bad drive.
[00:43] <arraybolt3> What brand was it? Sometimes brand new drives are bad.
[00:44] <bob3> I killed the process as it said not responding
[00:44] <bob3> kingston
[00:44] <arraybolt3> What a drag. What brands are the other drives?
[00:44] <bob3> Adata
[00:44] <bob3> is kingston bad?
[00:45] <bob3> damn when I open the backup folder it takes forever to load
[00:45] <arraybolt3> Kingston is among the lowest-quality of the reputable drives. I'm not sure how adata compares, but I think they're good. I've have an Adata SSD that works great.
[00:46] <bob3> yeah I ahve an adata ssd too and the usb drives have 50%+ failure rates
[00:46] <bob3> error mounting usb can't read superblock
[00:46] <arraybolt3> Ah, crud.
[00:47] <arraybolt3> Personally, if the backup is really important, I would back up to an external HDD or SSD.
[00:47] <arraybolt3> I'll find a link to a good one.
[00:47] <arraybolt3> They're pretty cheap.
[00:48] <bob3> man these things are scams
[00:49] <arraybolt3> This is the cheapest one I could find, and it's a brand I know is good: https://www.bestbuy.com/site/wd-easystore-1tb-external-usb-3-0-portable-hard-drive-black/6406515.p?skuId=6406515
[00:50] <arraybolt3> Yeah, flash drives have surprisingly high failure rates, even from the best brands.
[00:50] <bob3> I'll just transplant an SSD
[00:50] <arraybolt3> Sometimes even when they don't fail, they can corrupt your data.
[00:50] <arraybolt3> That'll work well, also.
[00:50] <arraybolt3> Hey, wait, you have a spare SSD? That might make this whole process easier.
[00:52] <arraybolt3> I'll be right back, I've got something I have to do, shouldn't take longer than five minutes, ten at the outside.
[00:53] <bob3> well it's not spare but it can be borrowed
[00:59] <bob3> I'm going to burn through usbs
[01:07] <arraybolt3> OK. Well, your "burn through usbs" idea is good, and the borrowable ssd idea is good. Just make sure to get the hidden files and folders in your backup, and do the backup in a root instance of the file explorer.
[01:07] <bob3> Hey what do I run after lsblk and before sudo umount?
[01:07] <arraybolt3> sudo mount <path to USB partition here> /mnt
[01:07] <arraybolt3> sudo chmod 0777 /mnt
[01:07] <arraybolt3> Obviously, the USB needs formatted to EXT4 first.
[01:09] <bob3> says mnnt special device does not exist
[01:10] <arraybolt3> Probably forgot the /dev in front of the partition name. If the partition is "sdb1", then replace <path to USB partition here> with "/dev/sdb1"
[01:11] <bob3> wow mnt: wrong fs type, bad option, bad superblock or other error
[01:12] <arraybolt3> Probably forgot the number at the end. Not "/dev/sdb", but "/dev/sdb1". (Again, this assumes your USB partition is sdb1.)
[01:13] <bob3> it's clearly listed with the label I gave it and it's sdd/sdd1
[01:14] <bob3> tried both and it does not exit now
[01:14] <arraybolt3> Reformat the drive and try again. If that doesn't work, try a new drive.
[01:14] <bob3> tried unplugging and replugging and it detects it
[01:14] <bob3> Maybe I can just use it as fat32 and backup the partition to it?
[01:15] <arraybolt3> No, that won't work. fat32 doesn't support files bigger than 4GB.
[01:15] <arraybolt3> And it may also mess with file permissions if you do a file copy backup.
[01:16] <arraybolt3> Hey, try "sudo umount /dev/sdd1", then do the "sudo mount /dev/sdd1 /mnt" and all that stuff.
[01:17] <bob3> worked except at last step it said /mnt not mounted
[01:17] <arraybolt3> Ok, do these commands in order:
[01:18] <arraybolt3> sudo umount /dev/sdd1
[01:18] <arraybolt3> sudo mount /dev/sdd1 /mnt
[01:18] <arraybolt3> sudo chmod 0777 /mnt
[01:18] <arraybolt3> sudo umount /dev/sdd1
[01:18] <genii> I'm getting deja vu all over again
[01:18] <arraybolt3> Then unplug the drive and plug it back in.
[01:19] <arraybolt3> @genii Right? His system might be acting weird.
[01:19] <genii> If you don't want the write to remain caches, you may want to issue sudo sync to make sure it gets written before you remove it
[01:19] <bob3> works
[01:21] <arraybolt3> OK, good.
[01:21] <arraybolt3> @genii I think umount does that automatically.
[01:21] <arraybolt3> Now do the file copy backup.
[01:21] <arraybolt3> @bob3
[01:23] <bob3> Let's see how it goes 7.6GB/26GB
[01:23] <arraybolt3> 👍
[01:27] <bob3> 9% going to leave timestamps here for the weirdness
[01:28] <arraybolt3> Probably 9% number of files, 7.6GB size of files. That would be my guess, though I'm not totally sure.
[01:28] <bob3> yes that's what I meant
[01:29] <bob3> It's going along at a steady rate 12%
[01:30] <arraybolt3> Good.
[01:30] <bob3> time remaining is going down instead of up compeltely unlike the kingston which had some good flash followed by trash
[01:30] <arraybolt3> Don't be alarmed if you see the time suddenly shoot up, then start going down again - that is likely a result of Linux's disk cache, and I've seen it many times.
[01:34] <bob3> 25%
[01:34] <bob3> atleast 4 times faster
[01:36] <pirota> Hi guys
[01:36] <pirota> I am using lubuntu, I am trying to create a bootable usb. Which program can be used
[01:38] <arraybolt3> @pirota https://www.balena.io/etcher/
[01:40] <bob3> 35%
[01:40] <bob3> watch it die all of a sudden
[01:40] <arraybolt3> @bob3 I hope not!
[01:41] <pirota> I get this error when I try and install it
[01:41] <pirota> .7.9-linux-x64.zip
[01:41] <pirota> Reading package lists... Done
[01:41] <pirota> Building dependency tree... Done
[01:41] <pirota> Reading state information... Done
[01:41] <pirota> E: Unable to locate package balena-etcher-electron-1.7.9-linux-x64.zip
[01:41] <pirota> E: Couldn't find any package by glob 'balena-etcher-electron-1.7.9-linux-x64.zip'
[01:41] <bob3> is there a good reason formatted ext4 thumbdrives aren't writeable to start? really annoying
[01:42] <bob3> I used rufus to create bootable USB. good in my experience
[01:42] <bob3> so you can try rufus too
[01:43] <pirota> will apt-get install etcher work?
[01:43] <arraybolt3> @pirota No, Etcher is an appimage. You download it from the website, set it as executable, and run it. But if you're already using Lubunt, you don't need it. I thought you were making a Lubuntu USB.
[01:43] <arraybolt3> If you're using Lubuntu, do this:
[01:43] <arraybolt3> Open a terminal with Ctrl+Alt+T.
[01:44] <arraybolt3> Make sure your target USB drive is **not** inserted, and type "lsblk" in the terminal. Then press Enter.
[01:44] <arraybolt3> Now insert your USB, and run "lsblk" again. You will see a new entry in the list - this new entry is your target USB drive.
[01:44] <arraybolt3> Now, go to wherever your ISO image is using file manager.
[01:44] <arraybolt3> Click "Tools", and click "Open Terminal".
[01:45] <arraybolt3> Finally, run "sudo dd if=./<insert ISO image name here> of=/dev/<insert USB drive here> bs=4M status=progress".
 Startup-disk-creator is installed already. (re @lubuntu_bot: (irc) <pirota> I am using lubuntu, I am trying to create a bootable usb. Which program can be used)
[01:46] <arraybolt3> @kc2bez I've had startup-disk-creator fail on me in interesting ways in the past, whereas dd never did me wrong.
[01:47] <arraybolt3> @pirota Actually, according to kc2bez, there's a program in Lubuntu called "startup-disk-creator" that should do the trick. Try that first, it's way easier. It should already be installed.
 dd works great too if you are comfortable on the command line.
[01:49] <arraybolt3> @kc2bez Thanks for popping in with that, it's way easier. They've probably fixed whatever problem I was running into back when I tried to use it.
 There have been a bunch of fixes to it. I think it should be pretty solid.
[01:51] <arraybolt3> @kc2bez That makes sense. Last I tried to use it was on Kubuntu 14.04... yikes
 One of our developers did an SRU not too long ago that went that far back.
[01:55] <arraybolt3> Wow. I was using back when I had no internet connection, so it was just whatever was on the ISO.
[01:56] <arraybolt3> s/using/using it
[01:57] <bob3> 68%
[02:11] <bob3> 92%
[02:15] <bob3> weird it's at 7.3/7.6 GB but 100% and time remianing 0
[02:15] <arraybolt3> Probably got one big file left, or cached data.
[02:15] <bob3> ok it ended on its own!
[02:15] <arraybolt3> Yay!
[02:15] <arraybolt3> OK, so you'll want to make sure that none of the files got corrupted during copy. Let me get you the command to do that...
[02:16] <arraybolt3> OK, so, pop open a terminal with Ctrl+Alt+T.
[02:17] <arraybolt3> Now, type "sudo su -", then "cd /media/lubuntu".
[02:18] <arraybolt3> Let me know whenever you've done that.
[02:30] <bob3> what's the procedure after lsblk?
[02:30] <arraybolt3> USB drive is still /dev/sdd?
[02:30] <arraybolt3> If so:
[02:30] <arraybolt3> sudo umount /dev/sdd1
[02:31] <arraybolt3> sudo mount /dev/sdd1 /mnt
[02:31] <arraybolt3> sudo chmor 0777 /mnt
[02:31] <arraybolt3> ACK! No...
[02:31] <arraybolt3> sudo chmod 0777 /mnt
[02:31] <arraybolt3> sudo umount /dev/sdd1
[02:31] <arraybolt3> (Don't do the "chmor" one - that was a typo)
[02:32] <bob3> doe sunmounting it from file explorer do the same as umount?
[02:33] <arraybolt3> I don't think so - I think unmounting from file explorer may fully eject the drive, making it so that it won't be available for the rest of the commands. I could be wrong on that one, but for best results, use the umount commands.
[02:36] <bob3> yeah it ejected it and commands wouldnt work l,ol
[02:36] <arraybolt3> That's how we learn Linux. :)
[02:45] <bob3> says it doesn't exist but it's there!
[02:46] <bob3> I'm lost
[02:46] <arraybolt3> What doesn't exist? The drive? The backup folder?
[02:46] <bob3> the drive with the old backup
[02:46] <bob3> I formatted to ext4. can write to it
[02:47] <bob3> well can't write to it*
[02:47] <arraybolt3> And what command is failing?
[02:47] <bob3> the 2nd one
[02:47] <bob3> nvm
[02:47] <bob3> I added a '/' at the end of sdb1
[02:47] <bob3> which bogged it
[02:47] <arraybolt3> Oh, that would do it.
[02:48] <bob3> could I mess the hdd up if I made one of these commands to it?
[02:49] <arraybolt3> Only the chmod one. The others aren't dangerous.
[02:49] <arraybolt3> Even if you chmod 0777 the hard drive, your data will be intact, but the permissions will be mangled to all get out.
[02:49] <bob3> copying backup
[02:50] <arraybolt3> Nice, and good luck with the flash drive!
[02:50] <bob3> So the plan is to then backup the partition to the first drive or even a new drive.
[02:50] <bob3> I'll try a new drive to test it too
[02:51] <bob3> and then we try to recover ability to boot?
[02:51] <arraybolt3> OK. And the target drive is way smaller than the source drive, right?
[02:51] <bob3> or if that fails reinstall by wiping whole disk
[02:51] <arraybolt3> (BTW, this is a very good strategy. Making a disk image and then messing with the original disk until you get it to boot is pretty much how its done AFAIK.)
[02:52] <bob3> So I won't be abcking up the whole disk, just the portion of the partition used
[02:53] <arraybolt3> Yes.  Then we'll delete the giant file.
[02:53] <arraybolt3> This will clear any data hanging around in the free space of your drive so that you can copy it onto a smaller drive.
[02:55] <arraybolt3> Then we're going to use a trick called a sparse copy that allows you to copy a giant file to a small drive. Because we've zeroed all the free space on the drive first, this will allow a ~130 GB file to fit on a ~20 GB drive, because most of the disk image will be all zeros, which the sparse copy can basically compress away.
[02:55] <arraybolt3> Since we're using EXT4 on the backup drive, this will work almost certainly work (so long as the flash drive doesn't fail).
[02:56] <arraybolt3> This approach is way, way, way safer than trying to resize a partition.
[03:02] <arraybolt3> Let me know whenever you're back so I can help guide you through that.
[03:02] <arraybolt3> @bob3
[03:05] <bob3> 24% 45min left
[03:06] <arraybolt3> Nice!
[03:12] <bob3> 33% 45 min left. 0.0
[03:13] <arraybolt3> Probably just the disk cache doing its thing.
[03:14] <arraybolt3> I've made live ISO USB drives where the file clone command looked like it was sailing along smoothly, then hit 100%... and stopped for ten or fifteen minutes before the clone finished.
[03:14] <arraybolt3> \0/
[03:14] <bob3> well disk cache theory sounds like ti would be unstable but the tiem remaining is very stable
[03:14] <bob3> only moves slowly
[03:14] <arraybolt3> As in still stuck at 45 min?
[03:15] <bob3> well no it goes up or down <10 seconds
[03:15] <bob3> updates 1/s
[03:15] <arraybolt3> Hmm, odd. Might be a UI bug, I should look into it.
[03:15] <bob3> ur a dev?
[03:16] <bob3> I don't think it's a UI bug. most of the time it changes by 1-2s
[03:16] <arraybolt3> ...Ish... I haven't done any coding for the OS, but I know enough to look at something, know if it's wonky, and tell the real devs what's gone wrong.
[03:16] <bob3> 40% 40min
[03:16] <arraybolt3> kc2bez is a real dev, you might have seen him pop in a bit ago.
[03:17] <bob3> I wish there was a partition manager or apt that can create format ext4 drives and make them writeable without the hassle
[03:17] <bob3> I don't get it it was a terrible experience a few months ago when I didn't know. I jsut gave up on ext4 and used fat32
[03:18] <arraybolt3> Right? I think the problem there is that fat32 drives don't have any such things as file permissions, so when the OS mounts it, it just works (depending on the mount command you use - that's a whole different bag of beans)
[03:18] <bob3> if the file permission can be changed, what's the point of it? to prevent non user access?
[03:19] <arraybolt3> But ext4 supports UNIX file permissions, and by default, the root of an ext4 drive is owned by root and isn't writable by everyone, so you end up with a drive that only root can write to until you chmod 0777 it.
[03:19] <arraybolt3> File permissions exist to keep unauthorized users from messing with stuff. You'll notice the "chmod 0777" command has "sudo" in front of it. Sudo basically means "run as root".
[03:20] <arraybolt3> When you do "sudo chmod 0777 /dev/<whatever>", you're executing the "chmod 0777 /dev/<whatever>" command as root.
[03:20] <arraybolt3> The reason it just works is because you're on a live ISO. On an installed system, the "sudo" command would ask you for your password before doing anything.
[03:21] <arraybolt3> This way, you can't mess with core system files unless you really want to, and some random guy who walks by can't mess with core system files at all (unless he boots your system with a live ISO - that's another whole bag of beans)
[03:21] <bob3> does chmod 0777 just remove permissions or ?
[03:22] <arraybolt3> chmod 0777 allows any user in the world to read, write, and execute files, as well as delete files, list the contents of folders, and add new files.
[03:22] <arraybolt3> It's basically a "let anyone do anything" command.
[03:23] <bob3> if a os partition was chmod 0777'd and booted into, would it be easy to hack?
[03:23] <bob3> by outsiders
[03:23] <arraybolt3> Pretty darn easy.
[03:24] <arraybolt3> With normal file permissions, if you accidentally run malware, you might be able to get away with making a new user account, and be good, since the malware should be confined to the user you ran it as.
[03:24] <arraybolt3> With a drive that was chmod 0777'd, it would be able to do anything it wanted.
[03:25] <arraybolt3> (As an aside, don't rely on user accounts to protect you from malware - it's a good line of defense, and in other uses of Linux, file permissions are essential to security, but as a rule of thumb, don't ever execute malware on your system, and be careful of viruses.)
[03:28] <bob3> are u sure we can't safely shrink a partition or check if it was ok? I have enough space to make 3 more copies of it on the disk
[03:28] <arraybolt3> I am very sure that it's not safe. I have destroyed all the data in a partition doing that.
[03:29] <arraybolt3> And everything looked perfectly safe when I did it. The command failed for no particular reason that I could see, and my data was dead.
[03:30] <bob3> I did move the partition once but it would say "move and shrink" even though the final size was the same down to 0.1GB (would not show in more detail)
[03:30] <arraybolt3> Partitions are fickle things - one misstep when messing with them, and poof, there went your data. That's why the solution I'm suggesting doesn't edit the partitions, it just copies them.
[03:30] <arraybolt3> Did the system stop booting immediately after you did the move?
[03:30] <bob3> No
[03:30] <bob3> The move was after trying to fix it
[03:31] <arraybolt3> Oh. Well, glad it worked that time, don't do that anymore!
[03:31] <bob3> Well how do you know it didn't break something? isn't it all or nothing?
[03:31] <arraybolt3> Because you can still copy files. If you can copy files, your data is intact (unless something went severely wrong that I don't know about).
[03:32] <arraybolt3> As long as the files and their permissions are intact, you can finagle the thing into booting, but it's always a good idea to have backups like you're doing.
[03:33] <arraybolt3> (For the record, I have shrank and moved partitions successfully in the past - it's just that I've also had it go horribly wrong in the past.)
[03:34] <bob3> is it easy to encrypt ext4 thumbdrive with a pass?
[03:34] <arraybolt3> I think so. Depends on the tool you use. I'll see if Lubuntu's partition manager can do that.
[03:34] <bob3> when it went wrong was it user error, poweroutage or just random bug?
[03:36] <arraybolt3> Dunno. I think it was random bug, but it might have been user error. All I know is that everything looked perfectly fine, I told it do go ahead and shrink the partition, and it errored out and killed the partition.
[03:36] <arraybolt3> I'm testing out the encryption thing.
[03:39] <arraybolt3> It looks like it's very easy to encrypt a thumb drive.
[03:39] <arraybolt3> Or at least make a thumb drive that encrypts everything you put on it.
[03:43] <arraybolt3> Alright! I now know how to make an encrypted thumb drive. You do have to reformat the drive in order to make it encrypted, but once that's done, anything you save to the drive will be encrypted when you save it, and you'll need a password to access it.
[03:43] <arraybolt3> I can show you how whenever you'd like.
[03:45] <bob3> is there also a way to use compression on ext4 to speed it up (ofload to cpu)?
[03:46] <arraybolt3> I don't know, I'd imagine so.
[03:55] <bob3> Why is there multiple releases per month. is the dev really changing source code this often?
[03:55] <bob3> is it automated?
[03:56] <bob3> https://appimage.bitmessage.org/releases/
[03:56] <bob3> I could try a more up to date version
[03:56] <bob3> 88% 8min
[03:57] <arraybolt3> It might be that he's doing that much work on it. Some programmers really get into their stuff - that's why Linux exists.
[03:57] <arraybolt3> It might be possible that your problem is that you're missing other needed config files. Have you checked home/user/.cache on your main drive?
[03:58] <arraybolt3> Also check home/user/.local/share
[03:58] <arraybolt3> On the main drive
[04:01] <arraybolt3> If bitmessage was working before, once we get your drive to boot again, it should work again.
[04:01] <arraybolt3> And since we're doing all these backups, we should be able to recover from most any mess-up.
[04:06] <bob3> Normally I'd go to sleep now. How long would this take?
[04:07] <arraybolt3> Pretty long. If you need to stop for tonight and pick up in the morning, that's fine. I'm usually on IRC after 1 P.M.
[04:07] <bob3> 1pm EST?
[04:07] <arraybolt3> 1pm CDT.
[04:08] <arraybolt3> (Plus, there's a bunch of other people here who are also very helpful)
[04:08] <arraybolt3> (so even if I'm not on, someone should hopefully be there.)
[04:08] <bob3> There's files missing from the backup idk why
[04:08] <arraybolt3> That's fixable. You did the backup in a root instance of the file explorer, right?
[04:09] <bob3> Yes
[04:09] <arraybolt3> OK, so you have a terminal open still, right?
[04:10] <arraybolt3> Type "sudo su -", press Enter, then type "cd /media/lubuntu" and press Enter again.
[04:10] <bob3> wait a sec the file size is good when I open properties from rooted file explorer
[04:10] <bob3> but not from normal file explorer
[04:10] <arraybolt3> Hmm. Turn off all the file explorers, then open a normal file explorer, set it to show hidden files, and look again.
[04:13] <arraybolt3> Worst case scenario, even if the backup is messed up, it's easy to fix. (And I don't think it's messed up - I think the non-root file explorer probably just isn't quite up to speed.)
[04:14] <bob3> ok it matches but only when in root
[04:14] <bob3> I think it's fine
[04:15] <arraybolt3> You know what, I bet I know why. Probably some of the files or folders aren't read-accessible by a normal user, so it can't see their sizes and just ignores them.
[04:15] <arraybolt3> I think it's fine too.
[04:16] <bob3> Well I'm glad I copied everything as my old backup had neither hidden files, didn't use admin and also was fat32 so lots of html files lost
[04:16] <bob3> Do you want me to do a copy of the partition? It will finish overnight
[04:16] <arraybolt3> Oy. That would be very hard to use to recover...
[04:17] <arraybolt3> Well, sorta. We can prep to do the partition copy, but it will take a bit, and so the prep step might have to take overnight, and then we can do the partition copy tomorrow (unless it finishes quick).
[04:18] <arraybolt3> To do the partition prep, do this command sequence:
[04:18] <arraybolt3> sudo su -
[04:18] <arraybolt3> cd /media/lubuntu
[04:18] <arraybolt3> ls
[04:18] <arraybolt3> cd <put the big long number here>
[04:19] <arraybolt3> dd if=/dev/zero of=./blank.img bs=4M status=progress
[04:19] <arraybolt3> That will get everything ready so you can safely copy the partition.
[04:20] <bob3> How is it not safe with KDE part manager?
[04:20] <bob3> or will it cause it to shrink it by the empty space?
[04:21] <arraybolt3> Making the big zero file makes it so that you can copy the partition WITHOUT shrinking, even though the drive you're copying onto is smaller than the partition.
[04:21] <arraybolt3> Shrinking the partition messes with file system stuff, and if it fails partway through (like it has on me), it's quite possible that all of your data will basically vanish.
[04:21] <bob3> no I'm not ready to backup to thumbdrive
[04:22] <bob3> just meant copying the partition on the hdd
[04:22] <bob3> the hdd has plenty of unallocated space
[04:22] <bob3> I deleted the windows partition and mint partition plus it still had lots of space
[04:22] <bob3> They were obsolete
[04:23] <arraybolt3> Eh, I'd recommend doing the thumb drive backup first just for good measure.
[04:23] <bob3> sure cya tomorrow
[04:23] <arraybolt3> OK. Glad to be of service, and I'll see you tomorrow!
[10:23] <alif> hi
 hi
[17:23] <bob90> is it safe to extent a os ext4 partition?
[17:23] <bob90> extend*
[17:31] <tomreyn> ext4 is a file system. it's usually safe to extend an unmounted, clean, ext4 file system. but you should always ensure you have proper backups before applying such changes.
[17:32] <bob90> If something bad happens will I get an error? I'm actually looking to shrink a partition
[17:32] <tomreyn> partitions you don't extend, but you rewrite them (or a software does it for you, pretending that you can resize them).
[17:33] <bob90> I think if I can make a copy of it first and then shrink it and if there's no error and I can open the files just as before, I assume it's fine
[17:33] <bob90> then it will be small enough to fit as a partition backup on a USB
[17:33] <bob90> then I can tinker and try to make my OS bootable again
[17:34] <bob90> or rewrite it and use my user file backup to restore most things. but I'm afraid to lose something
[17:34] <bob90> I'd rather just make it bootable again.
[17:34] <tomreyn> you should expect to see an error message and / or a non-zero exit code when a command fails to do the requested operation.
[17:34] <bob90> Is the change that KDE partition manager gives no message indicating an error but an error occured nevertheless? I presume the chance is virtually zero
[17:35] <bob90> It shows what % of the partition is being used so it should be designed to shrink it by the unused part right?
[17:35] <tomreyn> resize2fs -M    is probably what you're looking for. the above note on backups still applies.
[17:36] <tomreyn> i'm not familiar with kde partition manager, can't comment
 at lxqt 1.1 where can i increase number of virtual desktops ?
 i should make an obvious statement - LXQt 1.1 is not yet in LUbuntu and if you install it yourself it's for 'testing purposes' - the goal is to get it in this cycle but there will be testing, etc. that has to be done
 just an obvious FYI to everyone
 This is usually a function of the window manager configuration. (re @tbs61: at lxqt 1.1 where can i increase number of virtual desktops ?)
 i see, thanks.
 when i increase number of virtual desktops to 4, at panel's "desktop swicher" widget it doesnt show 4 box for each virtual desktop. but it changes desktops with moving up and down mouse whell. is that a bug or normal ? (re @kc2bez: This is usually a function of the window manager configuration.)
 or is it also about window manager ?
 As @teward001 pointed out we do not have LXQt 1.1 in Lubuntu so I have no idea what window manager or distribution you are using. This is an offtopic discussion. (re @tbs61: or is it also about window manager ?)
 okay, thanks ^^ (re @kc2bez: As @teward001 pointed out we do not have LXQt 1.1 in Lubuntu so I have no idea what window manager or distribution you are using. This is an offtopic discussion.)
[20:57] <bob22> I wonder if my resize will take longer than copy
[20:57] <bob22> There's no progress bar
[20:58] <bob22> arraybolt3 was it you that helped me yesterday?
[22:24] <micha_> !de
[23:35] <bob5> I'm back
[23:35] <bob5> backed up the partition
[23:37] <arraybolt3> @bob5 Hey, sorry I wasn't there at first!
[23:38] <arraybolt3> Alright! So your next goal is to get the existing partition to boot, right?
[23:45] <bob5> Yes
[23:45] <bob5> Glad to see you
[23:45] <bob5> I'm currently restoring the backup partition into unallocated space to test it.
[23:46] <arraybolt3> OK. So, quick question, can you pop open a terminal (Ctrl+Alt+T), and tell me what this command does: "ls /sys/firmware/efi"
[23:49] <arraybolt3> This will tell me part of how your system works internally so that I can get a better idea of how to get it to boot.
[23:53] <arraybolt3> It would also help to know the results of "sudo parted -l" (the last two characters are a dash followed by a lowercase L). Just glance through the output and tell me if your main drive says "Partition Table: gpt" or "Partition Table: mbr" in it.


[01:30] <waltman> Angry Anaconda
[01:30] <waltman> My hobby is coming up with Ubuntu release names :)
[01:32] <waltman> Bashful Boa Constrictor
[01:32] <waltman> Cheeful Cheetah
[01:33] <waltman> Deranged Direwolf
[01:33] <waltman> I'm just an idea guy. Mark's going to have to run with these.
[01:33] <pleia2> haha <3
[02:27] <JonathanD> Terrifying Trump
[10:58] <teddy-dbear> Morning peoples, critters and everything else
[13:27] <icey> ahoy
[13:27] <icey> JonathanD: that's slightly terrifying...
[14:27] <JonathanD> icey: heh :)
[23:30] <ChinnoDog> What ever happened to sadin? He used to be in this channel once upon a time.


[01:06] <ax562> knome would this be all the reported bugs for xubuntu 16.10? https://blueprints.launchpad.net/ubuntu/+spec/xubuntu-y-bugs
[01:06] <knome> nope.
[01:06] <knome> that's just the bugs we are committing to fix
[01:07] <knome> or at least committed to try to fix
[01:07] <ax562> haha
[01:07] <ax562> what if someone doesn't get the error reported on a bug?
[01:07] <knome> then we don't know about their bug?
[18:47] <Unit193> Hah, Debian #828175.
[20:03] <flocculant> is that a dupe ...


[14:47] <mterry> tsdgeos: the clickscope-no-longer-special branch -- how well does the dash deal with no scopes at all?
[14:47] <mterry> As long as you can access the bottom bar to add scopes back, I guess no problem
[14:54] <tsdgeos> mterry: it's "ok"
[14:54] <tsdgeos> "ok" meaning
[14:54] <tsdgeos> you get an empty window
[14:54] <tsdgeos> you can access the scopes scope to add stuff
[14:54] <tsdgeos> and the scopes scope looks a bit broken with an empty space on top
[14:54] <tsdgeos> but nothing too terrible imho
[14:55] <mterry> tsdgeos: sure, good enough
[14:56] <tsdgeos> mterry: what i want to try after the silo works is that it doesn't explode because defaults ask for clickscope and you don't have it installed
[14:56] <tsdgeos> pstolowski says that it shoudl be fine
[14:56] <tsdgeos> but i'll give it a try once the silo builds
[14:57] <mterry> tsdgeos: mmm
[15:17] <tsdgeos> mterry: tested
[15:17] <tsdgeos> it's good
[15:17] <tsdgeos> mterry: so will you take care of landing https://bileto.ubuntu.com/#/ticket/2404 ?
[15:24] <mterry> tsdgeos: yeah -- silo works?
[15:24] <mterry> I'll mark it as such and babysit it through QA
[15:25] <tsdgeos> mterry: i haven't tested the silo becvause it's still building, but i tested the CI build packages of the two branches that are in the silo
[15:25] <tsdgeos> so it "should be the same"? (TM)
[15:25] <mterry> tsdgeos: ok
[15:25] <mterry> thx


[02:57] <henrique> Olá amigos!
 i live booted lubuntu because it will be light but now its taking about 3.8 gb of my ram
 i cannot even open more than 3 chrome tabs
 is there any way to use lubuntu without consuming more ram … i am using usb2.0 … and 4 chrome tabs
[07:15] <guiverc> @anonid, running a live environment is less efficient on RAM than an installed environment, the / fs is created in RAM (which normally would be on disk), files need unsquashing before use (more ram used) etc...  you also haven't said which release/system
 @guiverc [<guiverc> @anonid, running a live environment is less efficient on RAM than an i …], lubuntu
 A live system is not the same as an installed system. … And a live system is not intended for daily use.
 20.04 lts
 will it be faster on usb 3.0
[07:23] <guiverc> @anonid, yes, but it's still stuck working in a *live* environment so you've not removed the greatest bottleneck (which is via install)
 @guiverc [<guiverc> @anonid, yes, but it's still stuck working in a *live* environment so …], so can i install lubuntu on usb 2.0 with another usb how will it perform
[07:27] <guiverc> Yes you can, but it's more difficult with `calamares` (20.04) than it used to be with `ubiquity` (18.04; ubiquity allowed you to select thumb-drives to install to)...
[07:28] <guiverc> It may still not be possible, I've not really tried to install to thumb-drive (have no reason to), but I'm aware calamares differs to ubiquity adding a hurdle (but I don't know how high)
 is there any way to free up the ram so that i can run smoothly
 @guiverc [<guiverc> It may still not be possible, I've not really tried to install to thum …], i tried it it showed me rsync error code 11
[07:31] <guiverc> did the media check complete successfully?  (on booting)
 @guiverc [<guiverc> did the media check complete successfully?  (on booting)], yes it successfully completed
 i tried the image on virtual machine also
 ok i dont want to get another headache  … can you please tell me how to reduce the storage … i used rufus persistant storage feature to live boot
[07:34] <guiverc> trying on a virtual machine doesn't really prove anything; it won't be identical to real hardware; you'd need to test it on an 100% identical box to validate media or the ISO validation & media check (built into 20.04)
 @guiverc [<guiverc> trying on a virtual machine doesn't really prove anything; it won't be …], i was able to get into the live environment
 @anonid [ok i dont want to get another headache  … can you please tell me how to reduce th …], can you please help me with this 👆
[07:36] <guiverc> getting into the live environment is no test, to test you'd have to use every function & search logs for squashfs errors...
[07:36] <guiverc> reducing memory; don't change anything (COW means every change will use RAM), reboot will clean memory too
[07:37] <guiverc> avoid adding packages, or where you need to add packages, use existing libraries (not additional libs due hit in memory involved..)
 @guiverc [<guiverc> avoid adding packages, or where you need to add packages, use existing …], i only installed brave
 i dont want some apps if i delete them will memory be freed
[07:38] <guiverc> COW=copy on write; a change on a real system is written to disk, changes are COPIED (copy on write) to ram instead of being changes
[07:38] <guiverc> no deletions won't free all the ram like an installed system (it can free some yes), reboot will clear all
 @guiverc [<guiverc> no deletions won't free all the ram like an installed system (it can f …], but i am not live usb so if i reboot will windows os be swiched considering the fact that my disk is at top of boot order
[07:40] <guiverc> a LIVE system is intended for repair, quick test & temporary use, not to be used as real system... design choices
 ok thankyou
[07:42] <guiverc> recall COW; part of why deletions won't free up space.. as system progresses ram will decrease as there is no disk to save those changes; RAM is constantly being used as a stack
 the reason why i didnt install was that i had issues with bluetooth audio headphones
 if i use live i can reinstall it anytime
 moreover i want windows
 @anonid [moreover i want windows], as some softwares run only on windows
 will decreasing the size of persistant storage help
 is there any way to duel boot
 lubuntu
[08:25] <guiverc> @anonid, you can dual boot Lubuntu; but as I don't use windows (10) I'm not good for giving advice in that regards, likewise I rarely use persistent-live sorry
 @guiverc [<guiverc> @anonid, you can dual boot Lubuntu; but as I don't use windows (10) I' …], thanks a lot for the help 👍
[09:47] <guiverc> you're most welcome
[21:09] <Tony48> Hi - How can we configure wifi on a hidden (SSID) network? We are using 20.04.1 LTS (Focal Fossa). nm-tray does not provide the option.
[21:15] <krytarik> Tony48: https://stackoverflow.com/questions/35476428/how-to-connect-to-hidden-wifi-network-using-nmcli - I'd try something along these lines.
 @Tony48 [<Tony48> Hi - How can we configure wifi on a hidden (SSID) network? We are using …], with "Advanced Network Configuration"


[12:04] <jbailey> zyga_laptop: Right.  That's a kernel packaging problem.  Add -t to the command line in the meantime to fix that.
[12:06] <zyga_laptop> jbailey: no no
[12:06] <zyga_laptop> jbailey: I'm talking about bad grammar
[12:06] <zyga_laptop> 'was been'? is that wabbit talk?
[12:16] <kmr> comparing trac and eventum, it seems like trac will be more helpful as a bts for our interal development. The integration with subversion is a win for us.
[12:25] <netdur> hey, is Matthew Paul Thomas here?
[12:26] <crimsun> mpt is not online presently.
[12:26] <netdur> how do I contact him?
[12:27] <netdur> ubuntu-devel?
[12:27] <netdur> I mean maillist
[02:00] <neuralis> Treenaks, ping
[02:31] <Simira> ahrgle...
[04:53] <Aegir> I gotta get me one of them sexeh Ubuntu stickers for my laptop... If the damn thing ever comes back from the repair shop...
[06:16] <moquist> I'm new to packaging, and I've used dh_make and dpkg-buildpackage -rfakeroot on the game 'apricots'.  dpkg-buildpackage seems to build [almost?]  everything, and then it errs out.  http://paste.ubuntulinux.nl/d4452 shows the error I'm getting; I don't understand why fakeroot isn't taking care of the "Permission denied" problem.
[06:17] <Amaranth> moquist: #ubuntu-motu is probably better for packaging help
[06:17] <moquist> Amaranth: right.  thx.
[06:17] <Amaranth> that's where the excellent masters of the universe hang out
[06:18] <crimsun> the error's pretty simple; you used an absolute path
[06:18] <crimsun> -ECHANNEL
[06:37] <feugan3333> Hi all. Is there documentation on how apt works? I want to know exactly what happens when I specify the "-b" option to apt-get source package1.
[06:38] <Amaranth> man apt-get
[06:38] <Amaranth> -b just builds it the same way you could with dpkg-buildpackage
[06:39] <feugan3333> Thanks Amaranth, so I need to look at dpkg's documentation?
[06:40] <Amaranth> i guess
[06:40] <Amaranth> if you're looking for some kind of architectural overview I don't think one exists.
[06:45] <feugan3333> Amaranth: What I really want to do is build a package with debug information included. I don't think there is any way to do this with apt,dpkg,etc. I would just download the source from the packages site and then build it that way. But I'm having trouble getting this to work. So I'd like to see what was done to get the package to build on ubuntu.
[06:46] <Amaranth> ah, well, that's easier
[06:46] <crimsun> remove the call to dh_strip
[06:46] <Amaranth> it's just an environment variable you set before you run apt-get -b source package
[06:46] <Amaranth> i can't remember the variable though
[06:46] <crimsun> should be NOSTRIP
[06:47] <crimsun> DEB_BUILD_OPTIONS=nostrip,noopt,debug
[06:47] <feugan3333> Thanks crimsun, Amaranth
[07:10] <Treenaks> `/lastlog treenaks
[07:10] <Treenaks> hm
[07:11] <Treenaks> neuralis: pong
[07:11] <Amaranth> sounds good
[07:12] <Amaranth> err -ECHANNEL
[07:12] <Treenaks> yay 7:12 on a Sunday morning ;)
[07:12] <Amaranth> yay 12:14 on a sunday morning
[07:13] <Treenaks> Amaranth: 12:14?! what kind of place are you in then?
[07:14] <Amaranth> middle of the us
[07:14] <Treenaks> oh wait, 0:14
[07:14] <Treenaks> not 12:14 ;)
[10:32] <feugan3333> Does here use anyone use dh_make?
[10:33] <feugan3333> Err, Does anyone here use dh_make?
[10:42] <zyga> feugan3333: probably
[10:43] <pef> hello
[10:48] <feugan3333> zyga: I think there is a bug in the script at line 405. Mine says "if ( -x '/usr/bin/bzip2' && -x '/usr/bin/gizp' )"
[10:48] <zyga> feugan3333: looking
[11:00] <zyga> feugan3333: re
[11:01] <zyga> feugan3333: so what is the bug?
[11:03] <feugan3333> zyga: what the hell is gizp? I think they mean gzip. And it is not located in /usr/bin. It's located in /bin
[11:03] <zyga> feugan3333: ahh!
[11:03] <zyga> I didn't notice the typo
[11:04] <zyga> good catch!
[11:04] <zyga> will you mail the maintainer?
[11:04] <feugan3333> Neither did I, untill struggling for a few minutes
[11:04] <zyga> and file a bug about it
[11:04] <feugan3333> sure, do I need to create a patch?
[11:04] <zyga> mark it as trivial
[11:04] <zyga> feugan3333: you could, it's a one liner :)
[11:05] <feugan3333> zyga: where do I post the bug report? :-)
[11:05] <zyga> feugan3333: bugzilla.ubuntu.com or .debian.org
[11:05] <feugan3333> thanks
[11:06] <zyga> feugan3333: thanks for taking a look at it :)
[11:07] <feugan3333> sure, it's nice to actually contribute :-)
[11:09] <feugan3333> Seems like someone found it first: http://bugzilla.ubuntu.com/show_bug.cgi?id=17846
[11:10] <feugan3333> but they don't seem to notice that gzip is not located in /usr/bin
[11:11] <zyga> add a comment
[11:11] <feugan3333> ok
[11:11] <zyga> and attach a patch too
[11:15] <feugan3333> zyga: How do I create a patch. Is a unified patch good enough? "diff -u oldfile newfile > mypatch"
[11:15] <zyga> feugan3333: perfect
[11:15] <zyga> diff -u is great
[01:10] <smurf> elmo: Please get gnutls12 from Debian
[01:19] <pef> elmo: please add my gpg key to keyring so I can upload to archive (gpgid: 601FA31D, launchpad id: loic)
[01:35] <zyga> has anyone seen pitti/
[01:39] <mdke> zyga, it is sunday
[01:43] <highvoltage> sunday bloody sunday
[01:47] <zyga> sunday is the day I get worried about monday's project
[01:52] <zyga> anyone with little kernel knowledge around
[01:52] <zyga> I've recompiled the standard ubuntu i386 kernel
[01:52] <tseng> its much easier to ask your question and hope for an answer than keep asking about presence
[01:52] <zyga> but after booting it panics with
[01:53] <zyga> 'unable to mount root fs on unknown-block(0,0)
[01:53] <zyga> and before that: cannot open root device hda1 or unknown block(0,0)
[01:53] <zyga> what did I do wrong?
[01:54] <mdke> they can probably help you in #ubuntu
[01:54] <zyga> will try but I don't have high hopes
[01:54] <mdke> well your hopes are higher there than off-topic in here tbh
[01:54] <Seveas> #ubuntu-devel is not for support
[01:55] <mdke> zyga, alternatively, try the support mailing lists or the forums
[01:55] <HiddenWolf> zyga, either you don't have ide-support enabled, or it's something with lvm, would be my guess.
[01:55] <tseng> HiddenWolf: more like he didnt build and load an initrd
[01:55] <zyga> mdke: I'll check the forums
[01:56] <zyga> I used make-kpgk
[01:56] <zyga> okay, in #ubuntu
[04:08] <\sh> grmpf...wtf is this?
[04:08] <Treenaks> this is IRC
[04:08] <Treenaks> Welcome.
[04:08] <\sh> infinity: ping
[04:21] <mdke> does anyone around know much about keybuk's bootchart package?
[04:21] <mdke> i get an error when installing, and I wondered if it is problematic
[04:29] <mdke> http://pastebin.com/427780
[04:32] <\sh> damnit
[04:32] <\sh> gajim orig.tar.gz in ubuntu is smaller then debians version...which means katie is bitching around...
[04:54] <slomo_> \sh: not the first package this merge-round with this problem :/
[04:55] <\sh> slomo_: sadly...it means I can forget about the merge and merge upstream changes and debian changes by hand..or I bring in gajim 0.9.0+cvs
[04:55] <highvoltage> should i have gotten any kind of notification for the lpbugs i sent yesterday? i still can't see anythin on launchpad about it.
[04:56] <slomo_> \sh: make a -Xubuntu1 with the merged changes... where's the problem?
[04:56] <slomo_> \sh: it only means that we have to care for it for the remaining time of 0.8.2
[04:57] <\sh> slomo_: our package is 0.8.2-0ubuntu1 debian is 0.8.2-1 and we will have 0.8.2-1ubuntu1
[04:59] <slomo_> \sh: yes
[05:30] <\sh> slomo_: and this is now the problem..because 0.8.2-1 orig.tar.gz is some bytes bigger then 0.8.2-0ubuntu1
[05:31] <slomo_> \sh: upload a 0.8.2-1ubuntu1 which uses our different tarball
[05:32] <\sh> slomo_: for that I have to find out what is different between our tarball and the debian one...because we used the normal upstream tarball
[05:33] <slomo_> \sh: yes... diff it ;) i guess debian took a tar.bz2 and repackaged it...
[05:34] <slomo_> pitti: hi, do you have the time to look at a MainInclusionReport atm?
[05:34] <\sh> slomo_: argl
[06:47] <\sh> infinity: can u please have a look at http://people.ubuntu.com/~lamont/buildLogs/a/ardour/0.99-3ubuntu1/ardour_0.99-3ubuntu1_20051110-0202-i386-failed.gz because it has this little nasty scons bug again....thx :)
[07:01] <Manny> hi
[07:03] <Manny> I'm not sure whether to ask here or in #ubuntu-motu...I'm supposed to get Ubuntu play nicely with ThinkPads. It looks like most of the software is available already (kernel, xorg drivers for the special mouse device etc.). Whom do I have to contact to get the packages into ubuntu, and which packages are suitable? Is there an additional laptop-related driver package, or should this go into stock xorg/stock kernels?
[07:03] <Manny> by stock I mean the stock ubuntu packages, not the stock tarball
[07:04] <Manny> for instance, http://web.telia.com/~u89404340/patches/touchpad/2.6.11/ has a kernel patchset. Am I supposed to just file a bug report an lean back?
[07:06] <lifeless> Manny: I suggest you file bugs for all of them
[07:07] <lifeless> Manny: and then depending on the reaction you may need to do new packages, put patches in existing packages etc
[07:07] <Manny> lifeless, thanks
[07:07] <lifeless> Manny: also, if you think a patch to an existing package is appropriate, do that when you file the bug
[07:07] <Manny> lifeless, new bugs through launchpad, right?
[07:07] <lifeless> Manny: that way the person getting it can decide to just apply the patch :)
[07:07] <Manny> lifeless, so I should try them out and compile them by hand first?
[07:08] <lifeless> Manny: re launchpad for new bugs, I don't know if the transition happened yet.
[07:08] <Manny> the problem with hardware-related patches is always that WFM doesn't mean works for all
[07:08] <lifeless> Manny: I would file the bugs first. That way discussion starts now,.
[07:18] <Manny> http://bugzilla.ubuntu.com/show_bug.cgi?id=19566 if any kernel bug triager is interested
[07:20] <siretart> Manny: which packages are missing?
[07:22] <Manny> siretart, I think none, xorg-driver-synaptics seems to be available :)
[07:22] <siretart> Manny: it is.
[07:22] <siretart> Manny: did you check which of these patches are actually missing in the ubuntu kernel?
[07:24] <Manny> siretart, I grepped the debian changelog, and neither found synaptic nor [Tt] hink[Pp] ad nor TAP
[07:25] <Manny> let me check...
[07:26] <siretart> I remember there has been quite some work on getting alps support right
[07:28] <Manny> hrm you seem to use a driver called cPad. http://web.telia.com/~u89404340/patches/touchpad/2.6.11/ has patches for alps stuff, though. The alps.c file is almost not touched with the current kernel diffs.
[07:28] <Manny> (at least with patch-2.6.12-9.23)
[07:29] <mdke> Manny, our head laptop guy is mjg59, you can try getting in touch with him too if you like.
[07:29] <Manny> mjg59, ping
[07:30] <mdke> Manny, you can also try the laptop testing mailing list, see http://lists.ubuntu.com/mailman/listinfo/laptop-testing-team
[07:30] <mdke> he reads that, in case you don't catch him here
[07:30] <Manny> mdke, thanks
[07:30] <mdke> np
[07:30] <mdke> i have a thinkpad myself
[07:31] <Manny> mdke, he's also available on the GIMPnet, so I can bug him whenever I want :)
[07:31] <mdke> sure
[07:32] <neuralis> Treenaks, ping
[07:33] <mdke> Manny, oh, one last place is #ubuntu-laptop
[07:36] <siretart> lol: http://www.flickr.com/photos/mbp_/61725150/
[10:29] <thierry_> how could I take a list of files and open all of them with gedit at once in a bash script?
[10:29] <crimsun> -ECHANNEL
[10:30] <crimsun> but you'd just pass them to gedit, like: gedit a b c d e f [...]
[10:31] <thierry_> ok and to count how many files I have in the list?
[10:44] <mdke> i wonder if there is something wrong with the mailing list
[10:44] <mdke> every SINGLE time I post to it and someone replies, I get two copies, one from the list and one from the sender
[10:45] <daniels> err
[10:45] <daniels> look at the To field
[10:45] <daniels> it
[10:45] <daniels> 'll have you and the list both there
[10:45] <mdke> it has me in the to field, and the list in Cc
[10:45] <mdke> it only happens on -devel
[10:45] <bob2> someone should invent a header that specifies if you should get a CC or not on list-replies
[10:46] <mdke> the mailing list shouldn't be sending me mail where I am in the to field, iirc
[10:46] <mdke> for example, on the -doc list, people reply-to-all constantly, and I never get two copies
[10:46] <mdke> only on -devel
[10:46] <neuralis> mdke, that's a configurable mailman setting which most list admins do not turn on.
[10:46] <mdke> yeah
[10:46] <daniels> reply-to-list is crack
[10:47] <mdke> daniels, it's not reply-to munging, it is just the list doesn't send the person mail if they are in the to field
[10:47] <mdke> it's a pain getting two copies of everything
[10:48] <daniels> there's a very common procmail recipe you can find that caches message-ids and throws away duplicates
[10:49] <mdke> i don't use procmail
[10:54] <mdke> neuralis, ah could it be first_strip_reply_to that you were referring to?
[10:55] <neuralis> mdke, no, actually it looks i was misremembering. mailman has a "do not send members a copy of their own post" switch, and i thought i saw a "do not send members a copy of replies for which they're in the To/CC field", but i was wrong.
[10:56] <mdke> well something must do it, because -devel is the only list I get two copies of peoples' mails
[10:56] <neuralis> mdke: do the other lists have explicit reply-to headers set?
[10:58] <mdke> neuralis, i'm not sure, i can post two headers, one from -doc and one from -devel
[10:59] <mdke> http://pastebin.com/428302 and http://pastebin.com/428303
[11:00] <neuralis> 428303 is not a list mail, it's a reply that was sent to you personally.
[11:00] <mdke> ah
[11:01] <neuralis> look at the headers for any *list* mail on -doc, and see if the Reply-To: <-doc list address> header is there.
[11:01] <mdke> i guess because the list didn't send me a copy of that one, because I was in To:
[11:01] <mdke> try 428308
[11:02] <mdke> no hang on
[11:02] <neuralis> yes, that's devel, and incidentally that's the mail i just sent you ;)
[11:02] <mdke> 428310
[11:03] <mdke> heh, coincidence
[11:05] <neuralis> well, you have evolution sending a Reply-To: <you> header anyway, so if you didn't get a duplicate of the 428303 paste, it's a mailman setting i'm not familiar with.
[11:05] <mdke> i'm poking around in mailman to see if I can find it
[11:10] <kapputu> Hello everyone, I would like to spend my spare time on Ubuntu, I have no specific interests but initially I'd like to be told to do till I find my grounding
[11:10] <kapputu> *told what to do
[11:10] <kapputu> how should I go about it?
[11:11] <neuralis> kapputu, you can help with documentation or bug triaging on the less technical side, and packaging on the more technical side.
[11:11] <mdke> kapputu, if you are interested in development, #ubuntu-motu. if documentation http://doc.ubuntu.com, if art http://art.ubuntu.com, etc
[11:11] <neuralis> kapputu, #ubuntu-motu for packaging, #ubuntu-doc for documentation.
[11:11] <kapputu> what's motu?
[11:12] <mdke> actually, http://www.ubuntu.com/community/participate has a rather good list of stuff
[11:12] <neuralis> kapputu, https://wiki.ubuntu.com/MOTU
[11:12] <kapputu> I think I'd like to get started with documentation since that'd give me a better understanding of things
[11:12] <mdke> kapputu, definitely check out doc.ubuntu.com then
[11:13] <kapputu> thanks folks
[11:13] <kapputu> I'll do as you guys suggested
[11:14] <mdke> welcome to the community
[11:14] <kapputu> thanks mdke
[11:15] <kapputu> I have been making use of open-source a lot and I think it's time I gave something back
[11:17] <mdke> :)
[11:57] <Burgundavia> neuralis, you still up?
[11:58] <neuralis> Burgundavia, yeah, give me three minutes, busy atm
[11:58] <Burgundavia> neuralis, np
[11:59] <Burgundavia> neuralis, when you get a chance, can you take a look at https://wiki.ubuntu.com/BetterLaptopTesting


[15:08] <Brainstorm> Updates for Bangladesh: +9369 cases (now 1.2 million), +218 deaths (now 20685) since a day ago


[04:52] <pitti> Good morning
[06:26] <seb128> good morning desktopers
[06:26] <pitti> bonjour seb128, ça va ?
[06:26] <seb128> pitti, salut, ça va bien ! et toi ?
[06:27] <pitti> seb128: je vais bien aussi, merci ! le premier session de Taekwondo hier, je peux le sentir :)
[06:27] <pitti> (après 4 semaines)
[06:27] <seb128> oh, c'était la rentrée ?
[06:28] <pitti> seb128: illes remettent la salle durant les vacandes d'école
[06:28] <larsu> http://ralphlosey.files.wordpress.com/2010/01/french1.jpg?w=450
[06:29] <seb128> larsu, lol
[06:29] <pitti> seb128: alors j'ai allé courier ;)
[06:29] <seb128> pitti, ah, ok
[06:29] <pitti> larsu: santé !
[06:29] <seb128> en France toutes les activités arrêtent pendant les vacances
[06:29] <larsu> pitti: :)
[06:29] <pitti> seb128: oui, "les grandes vacances", non ? :-)
[06:29] <seb128> oui ;-)
[06:30] <seb128> larsu, there is no way around, you need to learn french, just admit it :p
[06:30] <larsu> I guess so....
[06:30] <pitti> seb128: en aôut 2007, nous avons dans Paris -- seulment peu de gens ici :)
[06:30] <larsu> I hear it's important for my job
[06:30] <larsu> can't understand the small talk my colleagues are making in the morning
[06:30]  * seb128 hugs larsu and pitti
[06:31] <pitti> larsu: c'est l'équipe du bureau .. on parle français ici ☺
[06:31]  * pitti donne une accolade retour à seb128 et larsu
[06:32] <larsu> pitti: quelle tristesse!
[06:32] <pitti> alors, je doit utiliser dict.leo.org souvent ..
[06:32]  * larsu hugs as well
[06:34] <pitti> seb128: tu semble me comprendre, c'est bon :) (alors c'est sans doute c'est très faux..)
[06:34] <seb128> pitti, btw, tz changing works against after updating from 201 to 207 for me, go figure...
[06:34] <seb128> pitti, oui :-)
[06:34] <pitti> seb128: yeah, so I read; no idea what changed
[06:34] <seb128> je te comprends
[06:34] <pitti> seb128: the thing that did change recently was the partitioning layout
[06:34] <seb128> yeah, me neither
[06:34] <pitti> seb128: perhaps there was some problem with the /etc/ writable bits?
[06:34] <seb128> could be indeed
[06:34] <seb128> that's on krillin as well
[06:34] <seb128> not sure how different things are from malo
[06:34] <seb128> l->k
[06:35] <pitti> no idea, but I'm on image 208, and it just works
[06:36] <seb128> pitti, do you know how upower gets the charge info?
[06:37] <pitti> seb128: yes, it just reads it from sysfs
[06:37] <seb128> it doesn't update as it should, I guess that's a lower-in-the-stack issue, but unsure where
[06:37] <pitti> seb128: and the remaining time for (dis)charging is computed based on the (dis)charge profile in /var/lib/upower, learned from the past
[06:37] <seb128> well, here it's the % which is wrong
[06:38] <pitti> seb128: wrong how? magnitude or doesn't update?
[06:38] <seb128> it's on a flat 73% since yesterday 20h
[06:38] <seb128> which I don't believe
[06:38] <pitti> upower has quite an impressive set of heuristics to detect various driver bugs and fix the units/scaling
[06:38] <seb128> ubuntu touch is not that power efficient
[06:38] <pitti> heh, you bet
[06:39] <seb128> especially that it's connected to wifi
[06:39] <pitti> ok, so the number is plausible (not scaled by 10 or 1000 or so), but just doesn't update?
[06:39] <seb128> yes
[06:39] <seb128> I think it was correct at the time
[06:39] <seb128> it just sometime seems to not pick updates
[06:39] <pitti> You can try "udevadm monitor -e --udev"
[06:39] <pitti> you ought to get some change events for teh battery every now and then
[06:40] <seb128> k, just got one
[06:40] <seb128> not sure what info is useful there though?
[06:41] <seb128> POWER_SUPPLY_CAPACITY=70
[06:41] <seb128> is that the charge %.
[06:41] <seb128> ?
[06:41] <pitti> apparently; but it's a nonstandard property that upower doesn't listen to
[06:41] <seb128> well, it has the same value than upower is giving
[06:42] <pitti> seb128: what do you have in /sys/class/power_supply/battery/capacity ?
[06:42] <pitti> seb128: yeah, it better does :)
[06:42] <pitti> seb128: oh, you mean upower --dump is right, but the indicator doesn't update? or upower --dump is behind, too?
[06:42] <seb128> they all display 70%
[06:42] <seb128> which I don't believe in
[06:42] <pitti> well, 70 != 73
[06:43] <seb128> # cat /sys/class/power_supply/battery/capacity
[06:43] <seb128> 70
[06:43] <pitti> but if sysfs says 70, then userspace can't know any better
[06:43] <seb128> yeah
[06:43] <seb128> well, it was 73%
[06:43] <pitti> if "capacity" exists, upower uses that
[06:43] <seb128> and I plugged it in usb to adb shell
[06:43] <pitti> otherwise it computes it from charge_now and charge_full, or other attributes
[06:43] <seb128> and now it's 70%
[06:45] <pitti> seb128: iahmad just mentioned something similar:
[06:45] <pitti> "started de-charging when put on power"
[06:45] <pitti> is that what you see, too?
[06:45] <seb128> yes
[06:45] <seb128> it was 73% since yesterday evening
[06:45] <seb128> and move to 70% in the few minutes I have it on usb
[06:46] <pitti> hm, did we recently get a new kernel on this device?
[06:46] <seb128> not sure, I think ogra said no
[06:51] <seb128> pitti, k, after a power down/up cycle, charge is at 26%
[06:51] <seb128> so the 70% land was staled
[06:52] <seb128> well, what is weird is that a reboot is not enough to fix it
[06:52] <larsu> I get a battery warning every time I unsuspend my laptop
[06:52] <seb128> I went to the factory mode to see if I could get the charge from there, didn't find it, booted back to Ubuntu
[06:52] <pitti> uh, not? so it's even lower than the kernel, it's in the battery itself?
[06:52] <seb128> larsu, the g-s-d one saying the battery is low?
[06:52] <larsu> "8% remaining" - when in fact it's full
[06:52] <larsu> seb128: I don't know :(
[06:52] <larsu> might be i-power as well
[06:52] <seb128> larsu, can you look at the charge history if there are spikes on resume?
[06:53] <larsu> seb128: no spikes
[06:53] <seb128> k, dunno then
[06:53] <larsu> "time to empty" in the statistics tabs is wrong
[06:54] <seb128> your laptop doesn't suspend after resume due to it?
[06:54] <larsu> ah wait no, it just has a weird y axis
[06:54] <larsu> seb128: no, everything is fine except for the notification bubble
[06:55] <larsu> AH! There is a spike indeed
[06:55] <larsu> I only see it when I enable "show data points"
[06:55] <larsu> so the notification is correctr
[06:55] <larsu> but the data is wrong :)
[06:58] <seb128> right
[06:58] <seb128> that's annoying
[06:59] <seb128> larsu, at least yours say 8%
[06:59] <seb128> on my laptop it sometimes does it but with a lower value
[06:59] <seb128> which triggers a "battery is low, suspending"
[06:59] <larsu> crazy!
[06:59] <seb128> indeed
[06:59] <larsu> so this is a known issue?
[07:00] <seb128> I know about it at least :p
[07:00] <seb128> I never took the time to properly report it/check if it was reported
[07:01] <seb128> I guess you have a current spike on resume and that might lead to buggy computations or something, with upower not smart enough to filter those buggy data points out
[07:01] <seb128> maybe pitti knows about it better?
[07:02] <pitti> it does have some heuristics, but I don't know them by heart
[07:43] <willcooke> Good morning desktoppers
[07:43]  * willcooke is back from the dead
[07:43] <willcooke> http://www.bbc.co.uk/news/technology-21895723
[07:43] <willcooke> sorry, wrong link
[07:44] <willcooke> http://www.bbc.co.uk/news/technology-28928369
[07:44] <seb128> hey willcooke
[07:44] <willcooke> morning seb128
[07:45] <seb128> willcooke, I've read different variants of that story, some mentioning that html5 based distro
[07:45] <seb128> or desktop
[07:47] <willcooke> hmm.  That article is a bit light on detail, my reading is that JackYu and team have announced 14.10 but the BBC have misinterpreted it as a whole new OS (whereas we know Ubuntu Kylin has been around for a while)
[07:47] <JackYu> willcooke, :)
[07:48] <JackYu> morning, all.
[07:48] <willcooke> Hey JackYu!  You're nearly famous in the UK, but they didn't mention your name ;)
[07:50] <JackYu> willcooke, I will ask they write my name next time, if they do mention Ubuntu Kylin, lol:).
[07:50] <willcooke> :D
[07:51] <willcooke> JackYu, I'm just catching up on my email backlog from last week, are you free in an hour or so for a sync up?
[07:53] <seb128> willcooke, do you know when didrocks is supposed to come back? the calendar suggested yesterday, but I guess that's not accurate?
[07:53] <willcooke> Tomorrow
[07:53] <willcooke> (My) Calendar has him off  today and yesterday
[07:54] <seb128> k
[07:54] <JackYu> willcooke, well, it's fine. I think it's better 6-7 hours later. I'm also just coming back from a bushiness travel and should sync up the development work first:).
[07:54] <seb128> thanks
[07:54] <larsu> I'm glad we have a lot of calendars :)
[07:54] <seb128> larsu, :-p
[07:54] <JackYu> larsu, lol...
[07:55] <larsu> this Icon component is awesome. Let's reload the the icon data when the size changes...
[07:55] <larsu> to bad qml doesn't do this if the icon name is the same
[07:55]  * larsu should probably rant in #ubuntu-unity
[07:55] <willcooke> JackYu, Ahh, kk - ping me when you're free
[07:56] <JackYu> willcooke, sure:)
[07:56] <willcooke> @ calendars (larsu, seb128) - that's part of my plan for doing the holiday bookings myself, I will make sure that everything is added to the UE holiday calendar, which does actually show didrocks as off today.
[07:56] <meetingology> willcooke: Error: "calendars" is not a valid command.
[07:57] <willcooke> and I'm also tracking conference attendance in there too
[07:57] <larsu> willcooke: nice!
[07:57]  * larsu vaguely remembers willcooke's email about htis
[07:57] <larsu> *this
[07:57] <willcooke> :D
[07:59] <willcooke> seb128, have you found a way to adjust screen brightness on the Inspiron yet?
[07:59] <willcooke> incidentally - I let my 6 year old have a go on the U8 desktop over the weekend, he fired up YouTube and was watching lego videos in no time, no help from me.
[08:01] <seb128> willcooke, no, but I didn't look for one
[08:02] <seb128> nice for the lego videos ;-)
[08:02] <darkxst> hey seb128, any update on the gnome-desktop update?
[08:03] <seb128> darkxst, hey, not that I know, Laney and robert_ancell and you seemed to be on it so I didn't really get involved in that one
[08:03] <seb128> I pinged robert_ancell about it on friday though, and he said that was on top of his todolist for this week
[08:03] <seb128> Laney is travelling/at debconf this week, so he might not have lot of cycles for that
[08:06] <darkxst> seb128, ok, I did chat with robert last week, but he ddnt really have an answer
[08:07] <seb128> to what question?
[08:07] <darkxst> looking at the gnome-desktop merge
[08:07] <darkxst> or the failures rather from the cut+paste rather
[08:07] <seb128> he's the one who did the work no?
[08:07] <seb128> right
[08:08] <seb128> well he said he would have a look/debug this week
[08:08] <seb128> you might be a better tz to catch him though
[08:08] <darkxst> seb128, ok cool
[08:08] <seb128> I've virtually no overlap with him
[08:08] <darkxst> seb128, I haven't been around much during B/H this week, but will be the next few days
[08:10] <darkxst> our labs dont have access to IRC ;(
[08:11] <seb128> ssh to a server and irssi from it ;-)
[08:23] <darkxst> seb128, can only ssh through port 443 but it drops out after exactly 30secs
[08:24] <darkxst> silly proxies
[08:24] <seb128> not really handy indeed
[08:26] <darkxst> and to add to the fun all webmail accounts are blocked apart from gmail
[08:29] <darkxst> and they run custom filters on top of gmail, that junk's most non uni email
[08:50] <seb128> pitti, is that desktop/translation applying to ubuntu-system-settings since that's not a click?
[08:50] <pitti> seb128: well, it only/mainly seems to affect debs (dialer, messaging, system-settings)
[08:51] <seb128> pitti, k, the description is confusing then, I though it would use the gettext translations for those
[08:51] <seb128> the bug states the issue is the location of the .mo for clicks
[08:51] <seb128> but that's not an issue for debs
[08:52] <pitti> seb128: it's a bit saddening that people fix this by adding translations to the .desktop file, instead of teaching unity to read the domain from the .desktop (X-Ubuntu-Gettext-Domain), but either way
[08:52] <pitti> seb128: hm, the bug description says that .desktop files need to include translations?
[08:53] <seb128> pitti, well, "other apps cannot know where .mo files might be located for click packages" is the rational
[08:53] <pitti> right
[08:53] <pitti> click's .desktop files should of course include everything
[08:54] <seb128> that's what this bug is about afaik
[08:54] <pitti> "Core apps .desktop files do not include translated strings" is correct
[08:55] <pitti> the "click" in the description is confusing indeed, and not relevant
[08:55]  * pitti clarified the description
[08:56] <seb128> well, core apps are click, and as I understand it the issue is that unity8 can't dgettext on a domain because the .mo are not in one location
[08:56] <seb128> pitti, ^
[08:56] <seb128> but yeah, if unity8 doesn't dgettext, it might fail to load translations for debs which have a .mo on a known location
[08:56] <pitti> well, apparetnly people used that very bug for dialer/messaging/etc.
[08:56] <seb128> Saviq, ^?
[08:56] <seb128> pitti, those are clicks, so yeah
[08:57] <pitti> seb128: no, they aren't
[08:57] <pitti> well, their .dekstop files don't have x-ubuntu-gettext-domain either
[08:57] <seb128> pitti, oh, ok, I though all core apps were clicks nowadays, included dialer
[08:57] <seb128> but seems you are right
[08:57] <seb128> that bug is still confusing to me ;-)
[08:58] <seb128> what should we do from the settings side?
[08:58] <pitti> dialer, address-book, media-player, messaging, and webbrowser are debs
[08:58] <Saviq> we were looking into supporting in-.desktop translation, falling back to dgettext in case when X- is there is not going to be much more difficult
[08:58] <pitti> seb128: intltool-merge the .desktop.in to include translations, or better yet, add x-ubuntu-gettext-domain: (if unity8 can handle that)
[08:58] <Saviq> seb128, pitti ↑
[08:58] <seb128> Saviq, that's good news
[08:59] <Saviq> it can't *just yet*, but it's minimal work
[08:59] <seb128> great
[08:59] <seb128> is there a bug tracking that work?
[08:59] <pitti> some apps do have translations in their .desktop (e. g. address-book-app or clock)
[08:59] <Saviq> bug #1350360
[08:59] <ubot2> Launchpad bug 1350360 in qtmir "App name in the splash screen needs to be localized" [Critical,In progress] https://launchpad.net/bugs/1350360
[08:59] <seb128> thanks
[08:59] <pitti> splash screen != dash, though
[08:59] <Saviq> pitti, ah dash
[08:59] <pitti> but if it applies there as well, so much the better
[09:00] <Saviq> pitti, nope, that needs to happen in unity-scope-click then
[09:00] <Saviq> pitti, but they already do the .ini style translation
[09:00] <pitti> x-u-gettext-domain is certainly preferrable to inline translations
[09:00] <Saviq> pitti, doing dgettext should be just one call
[09:00] <Saviq> pitti, sure, where it's possible
[09:00] <pitti> right
[09:00] <Saviq> but IIUC we decided against that for .clicks?
[09:00] <pitti> Saviq: right, that'd just apply to debs
[09:00] <pitti> well, applying it to clicks would be nice, but that's more complicated
[09:01] <Saviq> pitti, seb128, so yeah, I don't think there's a bug on that for the scope
[09:01] <seb128> k
[09:07] <willcooke> seb128, Do you know if the fixes for the desktop session from the PPA made it in to the archive yet?  i.e. If people download the Desktop Next ISO today will the session unlock work?
[09:08] <willcooke> seb128, low priority ^^^^^
[09:08] <seb128> willcooke, it's in the archive since friday, I verified it and it works
[09:08] <seb128> so daily iso should work
[09:08] <willcooke> niiiiiiiiiiiiice!  Thanks seb128
[09:08] <seb128> even if I didn't try to confirm it
[09:08] <seb128> but the update fixed my installed system
[09:08] <willcooke> seb128, I'll reinstall from ISO today and check it...
[09:08] <willcooke> popey, FYI ^^^^
[09:08] <seb128> thanks
[09:09] <willcooke> anyone know what happened to the torrents for ISO downloads?  (popey perhaps)
[09:10] <willcooke> my crazy home brew load balancer likes torrents
[09:10] <willcooke> tkamppeter, thanks for email.  I will stand in for you at the meeting today
[09:10]  * willcooke remembers to send the reminder email
[09:12] <seb128> willcooke, you ask for desktop-next? not sure, but my understanding is that torrent mostly work if you have enough people sharing
[09:12] <seb128> which is good for published ubuntu images
[09:12] <seb128> not so much for dailies of beta isos
[09:13] <popey> yeah, needs a "swarm" of people to seed
[09:13] <willcooke> seb128, yeah, there isnt a .torrent for the desktop next version.  Perhaps I should seed it/
[09:13] <seb128> I've no opinion on that, but I'm not much of a torrent user ;-)
[09:14] <willcooke> I've got two un-bonded ADSL lines so torrents are perfect for it, otherwise I'm tied to a single line for standard downloads
[09:15] <seb128> k
[09:16] <popey> dunno how many downloads unity-next is getting.. interestingly the Ubuntu MATE Remix (alpha) is getting ~200 downloads a day of the ISO.
[09:17] <willcooke> I would expect unity-next to be more like 10s a day
[09:18] <seb128> yeah, that's more likely
[09:19]  * willcooke be pimping it
[09:19] <willcooke> I'm writing a blog post
[09:20] <willcooke> so, ya know, that'll make all the difference ;)
[10:32] <pitti> seb128: do you know whether you or ken or someone else plans to land system-settings soon?
[10:32] <pitti> bug 1361588, same old, same old..
[10:32] <ubot2> Launchpad bug 1361588 in ubuntu-system-settings "Needs POT update" [Critical,New] https://launchpad.net/bugs/1361588
[11:33] <seb128> shrug
[11:34] <seb128> pitti, that constant filing of "pot needs updating" bugs doesn't make sense
[11:34] <pitti> well sure, it should just happen automatically
[11:34] <seb128> we do update the pot regularly, no need to go through bug filing every time
[11:35] <seb128> pitti, I submitted https://code.launchpad.net/~seb128/ubuntu-system-settings/translate-missing-sources/+merge/232184 earlier, that needs to go in, then we can do a pot update
[11:35] <seb128> pitti, btw, feel free to just commit pot updates directly to trunk when needed (at least for settings)
[11:35] <pitti> seb128: uh, can we do that?
[11:36] <seb128> pitti, sure, why not? that's how we handle it for u-s-s
[11:36] <pitti> when I asked for those x-ubuntu-use-langpack: thing, I got told to not commit stuff directly
[11:36] <seb128> the CI machinery handle it just fine
[11:36] <pitti> seb128: background is, I was asked to do a full testing with German and track everything which I can't fix in LP translations as bug; and that one breaks a lot
[11:37] <pitti> apparently "regularly" is not often enough
[11:37] <seb128> it adds a "  * Resync trunk" to the changelog
[11:37] <pitti> happy to just commit it, if that works
[11:37] <seb128> that's how we get translations updates
[11:37] <seb128> they are autocommited to trunk by launchpad
[11:37] <pitti> right
[11:37] <pitti> so how do I update the pot?
[11:38] <seb128> "make pot" in a builddir
[11:38] <pitti> ah, ok
[11:38] <seb128> like bzr bd and ctrl-C after the cmakery and run it in the builddir
[11:38] <seb128> or do the mkdir build; cmake; etc by hand
[11:38] <pitti> is there any reason why people don't just include that in MPs which change strinsg?
[11:38] <pitti> like in your's above?
[11:39] <seb128> yes
[11:39] <seb128> because 5 people submit a small change which impacts a string
[11:39] <seb128> and we get 4 mps that need to be rebase
[11:39] <seb128> in order
[11:39] <seb128> we used to do that and had mps conflicting all the time
[11:39] <seb128> because they all updated the pot
[11:39] <seb128> it's easier to just commit directly to trunk
[11:40] <pitti> so devs can't do it because of conflicts, the CI train can't do it because it requires a package build, and most devs don't do it because they just forget
[11:40] <seb128> or to do an "update the template" attached to a landing
[11:40] <seb128> but one for the whole landing
[11:40] <seb128> yeah, I start wondering if we should go back to the distro schemas
[11:41] <seb128> not sure why dpm&co decided it was better to have translations done on the upstream project
[11:41] <pitti> we need to for clicks
[11:41] <seb128> I think it was because things were in universe/not always packages in Ubuntu
[11:41] <pitti> for the .debs there's no reason
[11:41] <seb128> right
[11:41] <pitti> seb128: btw, I'm currently approving all the auto-imports after my X-Use-Langpack: orgy
[11:42] <pitti> so that ubuntu and trunk should sync trasnlations nicely
[11:42] <seb128> great
[11:47] <pitti> seb128: bah "You cannot upload to this branch. Members of Ubuntu Touch System Settings can upload to this branch. "
[11:47] <willcooke> seb128, just reinstalled from the new daily image for Next.  Works good!
[11:47] <seb128> willcooke, great
[11:47] <pitti> seb128: I put it on http://people.canonical.com/~pitti/tmp/pot-bundle, perhaps you can download and pull from that, then push?
[11:47] <seb128> pitti, try again?
[11:48] <pitti> ah, thanks
[11:48]  * willcooke -> lunch
[11:48] <pitti> seb128: so, let's see how fast that imports into LP :)
[11:48] <seb128> willcooke, enjoy
[11:49] <pitti> seb128: oh, screw -- it recorded the fact that I locally merged your branch, even though I reverted it afterwards
[11:49] <seb128> pitti, seems like you commited my mp as well
[11:49] <pitti> seb128: guess I'll uncommit and hit bzr over the head..
[11:49] <seb128> pitti, yeah, you need a "bzr revert"
[11:49] <seb128> not "bzr revert somefile"
[11:50] <pitti> seb128: well, that woudl have reverted my .pot update
[11:50] <pitti> I'll diff/revert/patch
[11:50] <seb128> yeah, I usually do
[11:50] <seb128> bzr revert
[11:50] <seb128> mv po/uss.pot~ po/uss.pot
[11:50] <seb128> or whatever backup file you have from bzr on reverts
[11:51] <pitti> hm, I pushed again (overwrite)
[11:52] <pitti> WTF
[11:53] <pitti> even full revert doesn't seem to work
[11:53] <pitti> ah, now https://code.launchpad.net/~system-settings-touch/ubuntu-system-settings/trunk updated, all good
[11:53] <seb128> pitti, launchpad imported it
[11:53] <seb128> 47 strings to translate in french
[11:54] <seb128> it was 0 earlier
[11:54] <seb128> https://translations.launchpad.net/ubuntu-system-settings
[11:54] <pitti> yay
[11:54] <pitti> so, off to getting some overdue lunch, and translation orgy after that ;)
[11:54] <seb128> pitti, enjoy!
[11:55] <pitti> seb128: thansk for your help!
[11:55] <seb128> yw ;-)
[11:57] <pitti> rvr: ^ so, feel free to translate system-settings to Spanish :)
[11:57] <rvr> pitti: Aha
[13:07] <Sweetshark> seb128, pitti: you need git, its much more intuitive than bzr.
[13:07] <Sweetshark> <flame on>
[13:07] <seb128> Sweetshark, not friday yet
[13:08] <Sweetshark> seb128: awww, somewhere on this world its got to be friday. everything else would be too depressing.
[13:09] <willcooke> :D
[13:23] <willcooke> sheesh.  Rookie mistake on my part... did some washing this morning, now I have no trousers to wear.
[13:24] <willcooke> emergency decorating jeans to the rescue
[13:36] <seb128> willcooke, you should ignore reddit btw :p
[13:36] <seb128> (just replied to your / mhall119 email)
[13:36] <willcooke> thanks seb128
[14:08] <willcooke> tkamppeter, ping
[14:10] <willcooke> tkamppeter, I'm planning to set up a couple of Hangouts for printer vendors to drop in to over the next couple of weeks so we can give a quick intro in to the cool things which are coming in the next 12 months.  Could you be available to answer technical questions during those sessions?  Probably only 45 mins x 2
[14:50] <seb128> qengho, hey, could you have a look to bug #1361372 (or talk to the security team/jdstrand about it, if it's rather for apparmor than chrome)
[14:50] <ubot2> Launchpad bug 1361372 in lightdm "Apparmor stopping Google Chrome from launching in guest session" [Undecided,New] https://launchpad.net/bugs/1361372
[14:50] <qengho> seb128: sure.
[14:50] <seb128> thanks
[14:52] <jdstrand> seb128, qengho: I plan to fix that in the coming days
[14:53] <seb128> jdstrand, hey, great, thanks
[14:53] <qengho> jdstrand: apparmor is really coming along. I want to thank whoever is responsible.
[14:54] <jdstrand> qengho: cool, I'll pass that along :)
[15:27] <willcooke_> sorry folks, running a bit behind.  Will start the weekly meeting in a few mins
[15:28] <seb128> willcooke_, still a few minutes before it starts anyway ;-)
[15:30] <willcooke_> Ok, trying to work out who is here:
[15:31]  * Sweetshark sneaks in
[15:33] <willcooke_> attente_, FJKong , happyaron, larsu, qengho, seb128, Sweetshark
[15:33] <willcooke_> anyone missing who is here and not at DebConf/asleep/holiday/etc?
[15:33] <seb128> Laney, debconf is not an excuse to sneak off the meeting :p
[15:34] <seb128> willcooke_, the list seems good to me
[15:34] <willcooke_> Ok cool
[15:34] <willcooke_> I also have updates from tkamppeter, TheMuso and robert_ansell - so I will do those at the end
[15:34] <willcooke_> attente_, you want to kick off?
[15:35] <attente_> sure
[15:35] <attente_> customize fcitx-qimpanel so that we can disable indicator-keyboard, in transition PPA and proposed upstream
[15:36] <attente_> talked to happyaron and csslayer about input context problem, he fixed it upstream, thanks happyaron for uploading
[15:36] <attente_> still blocked by fcitx MIR
[15:36] <attente_> to do: file FFe
[15:36] <attente_> to do: add fcitx signal for monitoring changes to current IM engine
[15:37] <attente_> to do: figure out how to disable per-window behaviour in fcitx (indicator-keyboard will do it)
[15:37] <attente_> (eof)
[15:37] <seb128> attente_, I didn't update/restart since yesterday, but I had issues with the ppa starting on friday(?)
[15:37] <seb128> like indicator-keyboard would say I'm using a "fr" keyboard
[15:38] <seb128> but fcitx would force it into qwerty
[15:38] <seb128> like I was changing it with the indicator and the change stays for a second
[15:38] <seb128> exiting fcitx makes the changes stop, so I guess it's it doing it
[15:38] <seb128> (I should probably follow up out of the meeting on that/test the current ppa version)
[15:39] <attente_> seb128, i guess if you had that problem on friday, it still exists now
[15:39] <seb128> k, I'm going to test again later/tomorrow morning and ping you for debugging I guess
[15:39] <seb128> attente_, didrocks should be back tomorrow, hopefully we can resume the MIR then
[15:39] <attente_> ok, i'll see if i can replicate it
[15:40] <willcooke_> Great, sounds like we have a plan to move that all forward then.
[15:41] <seb128> yes
[15:41] <willcooke_> Shall we move on to FJKong (if you're still awake :) )
[15:42] <attente_> seb128, you have what input sources/fcitx engines (listed in u-c-c region?)
[15:42] <willcooke_> Let's assume that FJKong and happyaron are afk and skip to larsu.  If you guys are online we can fit you in at the end.
[15:43] <larsu> a bit of a slow week due to a cold and lots of disussions
[15:43] <larsu> I'm talking with Mirco, Saviq, and design about notifications again
[15:43] <larsu> since I'll probably be the one taking care of it on unity7 in the future, I want to be prepared
[15:44] <larsu> seb128 made me aware of some problems in unitythemeiconprovider, which is contains the icon loading code for all of our qml things
[15:45] <larsu> I fixed that and another long-standing bug (people wanted different fallbacks) by implementing the fdo spec in there instead of using qt's implementations
[15:45] <larsu> also gives us rectangular icons and lets us drop a lot of hacks all over the place (which is what I'm currently doing)
[15:45] <larsu> I'm having some problems with UITK's test system, but I hope the guys in #sdk can help me with that
[15:46] <larsu> I've also looked more into some theming issues on 12.04 (for yorba apps), but didn't get around to finish that properly yet
[15:46] <seb128> larsu, you should probably ask again on #sdk, channel seems active now
[15:46] <larsu> I think that's it from me this week
[15:46] <larsu> seb128: ya, thanks
[15:46] <seb128> yw :-)
[15:47] <willcooke_> thanks larsu
[15:47] <willcooke_> qengho, over to you
[15:48] <qengho> Hello my lovelies!
[15:48] <qengho> * to-do: tracking SSE / SSE2 support upstream bug. May require new Cr release.
[15:48] <qengho> * in-progress: more work on mir support in chromium.
[15:48] <qengho> * in-progress: flash plugin Legal chatter.
[15:48] <qengho> * done-ish: flash plugin packaged for Partner repo. I'd like testing and feedback. See Chromium stage PPA.
[15:48] <qengho> EOF
[15:49] <willcooke_> Cool, thanks qengho.
[15:49] <willcooke_> So anyone listening who can help with testing, please get involved.
[15:49] <willcooke_> Oh, that reminds me, attente_ I said I would test your stuff, totally forgot.  Will do that.
[15:49] <willcooke_> same for qengho - I will get a VM set up this week and test
[15:50] <attente_> willcooke_, cool, thanks
[15:50] <willcooke_> seb128, over to you
[15:50] <seb128> k
[15:50] <seb128> • (had half a day off work)
[15:50] <seb128> • worked on some translations issue for ubuntu-touch/rtm
[15:50] <seb128> • debugging/bug reports for ubuntu touch current images
[15:50] <seb128> • tested desktop-next fixes for login, works \o/
[15:50] <seb128> • ubuntu-system-settings for touch
[15:50] <seb128> ∘ continued work on redoing the update panels layout using a colum, got that landed!
[15:50] <seb128> ∘ review for others (wizard language change, lockscreen, rotation, bluetooth fixes, icons)
[15:50] <seb128> ∘ tried to help Diego with cross-compilation issues, but it turned out it was already known problems with on-their-way solutions so let that for others
[15:50] <seb128> ∘ looked at the background panel "default wallpaper not selected"
[15:50] <seb128> • sponsored chromium-browser/utopic update, verified it fixes i386 issues
[15:50] <seb128> • usual share of bugs triaging and desktop discussions
[15:50] <seb128>
[15:50] <seb128> that's it for the week ;-)
[15:52] <willcooke_> Great stuff, thanks seb128
[15:52] <willcooke_> Sweetshark, you're up....
[15:52] <Sweetshark> - preparing some urgent updates for utopic/trusty/precise
[15:52] <Sweetshark> - happy on the updates on the Linux Munich story: http://www.omgubuntu.co.uk/2014/08/munich-council-say-talk-limux-demise-greatly-exaggerated
[15:52] <Sweetshark> - some initial upstream code review of mail merge improvements send by Munich for LibreOffice
[15:52] <Sweetshark> - conference preparations
[15:52] <Sweetshark> - prepared upstream tinderboxing in docker/saltstack (WIP)
[15:52] <Sweetshark> - some cleanup on the PPAs and bugtriage
[15:52] <Sweetshark> - no more fancy seb128-style ASCII bullets this week, dont wanna be a copycat
[15:53] <Sweetshark> EOF
[15:53] <willcooke_> :D
[15:54] <willcooke_> Thanks for posting that link,  glad to see the FUD isnt pervasive
[15:54] <willcooke_> Here comes a cut and paste for the guys I'm standing in for....
[15:55] <willcooke_> = tkamppeter =
[15:55] <willcooke_> - cups-filters: Released 1.0.58 with complete color management support,
[15:55] <willcooke_> contributed by Joseph Simon as GSoC 2014 project.
[15:55] <willcooke_> - system-config-printer: Added patch from Daniel Dressler's ippusbxd
[15:55] <willcooke_> GSoC 2014 project to start ippusbxd if needed and to set up printers
[15:55] <willcooke_> using it.
[15:55] <seb128> do them one by one or IRC might not like the spam copy ;-)
[15:55] <willcooke_> - Synced/merged all printing-related packages with Debian to be
[15:55] <willcooke_> up-to-date on Feature Freeze.
[15:55] <willcooke_> - OpenPrinting web site: Worked with Lexmark on addition of some new
[15:55] <willcooke_> printer entries/PPDs.
[15:55] <willcooke_> - Google Summer of Code 2014: Final evaluations
[15:55] <willcooke_> - Bugs
[15:55] <willcooke_> ack
[15:55]  * willcooke_ waits for the spam counter to tick down
[15:55] <willcooke_> = robert_ancell =
[15:55] <willcooke_> Worked on:
[15:55] <willcooke_> - Updated libgtop and rebuilt all dependencies for new soname
[15:55] <willcooke_> - Modify LightDM to support containerized Unity 8 session
[15:55] <willcooke_> - Reviewing multi-seat patches for LightDM
[15:55] <willcooke_> Currently working on:
[15:55] <willcooke_> - Fixing issues in unity-settings-daemon patches to work with new gnome-desktop
[15:55] <willcooke_> - Improving GTK+ Mir patch
[15:55] <willcooke_> Not blocked on anything.
[15:55] <willcooke_> = TheMusco =
[15:55] <willcooke_> * At the request of Will, started work on revamping the screen reader related documentation on https://help.ubuntu.com/community/Accessibility. Got some ideas on how to improve the docs written down.
[15:55] <willcooke_> * As a result, started going over relevant accessibility interface and activation methods, particularly keyboard shortcuts. Submitted a patch to change the keyboard shortcut for activating and deactivating the screen reader in unity-greeter to be the same as the shortcut used for the screen reader in the Unity and GNOME desktop sessions.
[15:55] <willcooke_> * Started performing accessibility install tests to see if any bugs had cropped up since trusty, and found that accessibility settings were not getting applied post install in some situations. A fix for some of this was made in the most recent upload of casper, however things still don't appear to be behaving as they shoudl with latest utopic daily. Investigation is ongoing.
[15:56] <willcooke_> * Started a discussion upstream about getting rid of the /usr/share/applications/orca.desktop file, which would allow the user to launch Orca from the dash. A couple of bugs have been filed about issues with running Orca in this way, and there not being an obvious way to disable it. Orca is a service after all, so this file shouldn't be needed any longer, given the shortcut toggle and the switch in the universal access preferences.
[15:56] <willcooke_> And for me...
[15:56] <willcooke_> * I'm setting up some hangouts for printer vendors to let them know what we're working on
[15:57] <willcooke_> * Writing a blog post with Jorge about U8 and what to expect in the coming months/years
[15:57] <willcooke_> * Preparing for Octobers sprints (I'll be asking for some session ideas this week, already got a few: printer dialogues, file manager)
[15:58] <larsu> willcooke_: you forgot to paste a period in tkamppeter's post. It's supposed to be "- Bugs." :P
[15:58] <seb128> willcooke_, sprints, plural?
[15:58] <willcooke_> larsu, :D
[15:58] <willcooke_> seb128, singular - typo
[15:58]  * willcooke_ is trying a standing up meeting
[15:58] <seb128> ;-)
[15:59] <willcooke_> doesnt seem to help my typing
[15:59] <willcooke_> :)
[15:59] <willcooke_> oh, and generic manager stuff.
[15:59] <willcooke_> walking around with a clipboard, asking stupid questions, the normal stuff
[15:59] <willcooke_> Ok, moving on to Any Other Business
[16:00] <willcooke_> Anyone got some?
[16:01] <willcooke_> sounds like not.
[16:01] <willcooke_> In which case, meeting ends.
[16:01] <seb128> seems not
[16:01] <seb128> thanks!
[16:01] <willcooke_> thanks guys, keep rocking!
[16:01] <larsu> thanks!
[16:01] <FJKong> willcooke_: ping
[16:01]  * Sweetshark goes back to torture builder :>
[16:02] <Sweetshark> s/builder/builders/
[16:03] <willcooke_> hey FJKong
[16:03] <FJKong> sorry, I am just driving back from my friends party to home. Last week I was focusing on a input method bug. It has been fixed. besides we have meeting with NUDT discussing about nautilus and nemo.
[16:03] <willcooke_> no worries man
[16:03] <willcooke_> great, I wanted to speak to you a bit about Nemo, probably in our 1:1 tomorrow
[16:04] <FJKong> willcooke_: ok, let's talk it tomorrow then
[16:05] <willcooke_> cool, thanks FJKong
[16:05] <FJKong> willcooke_: thanks
[16:16] <attente_> FJKong, hey, do you think it's possible for us to get https://github.com/lenky0401/fcitx-qimpanel/pull/27 merged upstream
[17:01] <qengho> Cr 37 arrives and upstream can't make release tarballs. Awesome.
[17:07] <seb128> mterry, hey
[17:07] <mterry> seb128, hello
[17:07] <seb128> mterry, is the lock screen launcher/indicator config supposed to work, or is unity8 support missing still?
[17:07] <seb128> mterry, doesn't seem to work here
[17:07] <mterry> seb128, unity8 support is in https://code.launchpad.net/~mterry/unity8/interactive-while-locked/+merge/231253
[17:08] <seb128> mterry, oh ok, that explains why it doesn't work :p
[17:08] <mterry> seb128, certainly the most likely  ;)
[17:08] <seb128> mterry, thanks ;-)
[17:10] <seb128> mterry, ok, I comment approved, needs to be test with unity8 before landing thoguh
[17:10] <mterry> seb128, awesome.  Sorry about that, I thought I linked to the unity8 MP in the descriptions but looks like I just did the gsettings one
[17:10] <seb128> no worry