[02:43] <bluefoxicy> mdz:  nah, it doesn't skin and eat kittens, it just cries about missed IRQs
[02:44] <bluefoxicy> mdz:  the related bug on the kernel bug tracker says it sometimes breaks other (perfectly working) hardware; but I haven't personally seen that symptom
[03:19] <kinema> Are there any 2.6.18 kernel packages availiable anywhere?  The module for my NIC wasn't mereged until 2.6.18rcsomething
[03:40] <gnomefreak> kinema: kernels.org
[03:42] <kinema> I would tell you that I was looking for packaged beta Ubuntu kernels but I'm assuming that you already knew that.
[03:44] <zul> no there is no 2.6.18 for ubuntu
[03:47] <Trae> how do you do the apt-get install kenrel-headers`uname-r`  trick.  (or is what I typed it?)
[03:48] <tfheen> Trae: type it just as that, yes.
[03:48] <Trae> tfheen, thank you kindly
[03:49] <infinity> s/kernel/linux/
[03:49] <tfheen> except it's linux-headers- and not kenrel-headers . :-P
[03:49] <tfheen> (not the dah)
[03:49] <tfheen> dash, even
[03:49] <Trae> oh
[03:50] <gnomefreak> tfheen: i subscribed you to a bug report more of a request someone filed to update opera in commercial repos. Its not important but i understadn you were the dev that did that
[03:51] <infinity> Even better would be "apt-get install linux-headers-`uname -r | sed -e 's/[0-9\.-] *//'` ... But I guess that's slightly harder to communicate.
[03:51] <tfheen> gnomefreak: yes, I'll tend to it when edgy is out.  I'm absolutely drowned in the release now.
[03:52] <gnomefreak> i figured that
[03:52] <gnomefreak> just wanted to let you know about it
[03:52] <tfheen> yeah, np
[03:53] <tfheen> it's not fallen off my radar, just not prioritised ATM
[03:53] <Trae> hmm shouldn't apt-get install linux-headers-`uname-r`   automagically install the right one?
[03:54] <Trae> errm... linux-headers`uname -r`  heh
[03:54] <infinity> Trae: It'll install the right one for now, but if you have the "linux-686" and "linux-headers-686" packages installed (for instance, pick your flavour), then the kernel and headers will get updated together with security updates, etc.
[03:54] <infinity> Trae: linux-headers-`uname -r` even.  You missed the dash.
[03:54] <Trae> hmm thought I tried it both ways
[03:55] <infinity> (Note that there's nothing magic about `uname -r`, it's just shell substitution that means "echo the output of the command 'uname -r'")
[03:55] <Trae> there it goes
[03:55] <Trae> I must have typed something wrong
[03:55] <Trae> hehe
[03:55] <Trae> sorry and thanks
[04:08] <gnomefreak> oh cool that never worked for me before :)
[08:06] <scoates> anyone particularly good with kernel modules? http://sourceforge.net/forum/forum.php?thread_id=1595813&forum_id=278158 .. this is on edgy


[04:43] <pitti> Godo morning
[04:43] <pitti> infinity: can do, yes
[04:44] <pitti> bdmurray: I wouldn't have bothered with quantal/raring, for precise it sounds fine to me; but it's already in -proposed now anyway :)
[04:51] <pitti> infinity: btw, I synced postgresql-9.1, that should build on arm64 now
[04:52] <infinity> pitti: \o/
[04:52] <infinity> pitti: Will look shortly.
[05:10] <pitti> infinity: meh, still no export on https://translations.launchpad.net/ubuntu/saucy/+language-packs
[05:10] <pitti> wgrant, StevenK: ^ could you please check whether this is running, or something went wrong?
[05:11] <wgrant> 2013-10-10 11:31:31 ERROR   Uncaught exception while exporting PO file 2444794
[05:11] <pitti> argh
[05:11] <wgrant> DB thing, it seems
[05:11] <pitti> apparently the delta packs run like clockwork, so so PO file 2444794 apparently hasn't been touched for a while
[05:12] <wgrant> Nah, nothing particular to that pofile, I don't think
[05:12] <wgrant> Just a DB glitch
[05:12] <pitti> wgrant: the last export also took about a day longer than expected, but eventually arrived; did that get restarted manually or did it somehow recover from that error?
[05:13] <wgrant> pitti: I haven't manually scheduled one in months. You sure it just wasn't the export that happens a couple of days later?
[05:13] <pitti> wgrant: it could have very well been that
[05:13] <pitti> but time is more critical now with the final release around the cordner
[05:13] <pitti> corner
[05:14] <wgrant> IIRC saucy happens tue/thu
[05:14] <wgrant> Might have to kick a special one off now
[05:14] <pitti> that would be good, so that we can build them Monday morning (or I kick them off on Sunday)
[05:16] <pitti> infinity: ah darn, missed the final freeze for psql? I was waiting for the LP import of the sid upload, but it didn't happen until I had to leave
[05:17] <pitti> infinity: well, I guess it can stay in -proposed and we 0-day update it to -updates if you don't want it in the release any more
[05:17] <infinity> pitti: Nah, it's all good.
[05:18] <infinity> pitti: Bonus points if it actually builds.
[05:18] <pitti> infinity: well, I refreshed config.guess/sub to latest saucy autotools-dev; I'm not sure it'll actually work there, let's see what the tests say
[05:19] <pitti> infinity: in 9.3.1 I saw a log entry "add arm64 s_lock code", we might want to backport that
[05:19] <infinity> Other than random segfaults and, of course, compilers needing to be ported, most stuff has Just Worked, so I have high hopes.
[05:20] <infinity> I don't much care if anything's *optimised* for arm64 right now, so if 9.3.x will make it to 14.04, that's cool.
[05:22] <infinity> sarnold: Have you looked at #1220434?  Looks like the last MIR of the cycle.
[05:23] <pitti> infinity: yes, 9.3 will be in 14.04
[05:24] <infinity> pitti: Kay.  So, if this 9.1 build works at all, we win.
[05:24] <infinity> pitti: More concerned about it because it's part of the base bootstrap loop, not because I think people will want to run psql on their simulators. :)
[05:25] <pitti> infinity: at the worst case I can reupload with a trivial change to add arm64 to the 'test failure is okay' list in debian/rules
[05:25] <pitti> (currently hurd and kfreebsd)
[05:32] <bdmurray> pitti: I meant the verifying the fix for the bug
[05:33] <pitti> bdmurray: it's certainly not verified until it gets tested with the actual binaries from -proposed
[05:33] <pitti> (guard against weird build failures, etc.)
[05:39] <pitti> infinity: OOI, did you find out why gid=tty now magically works?
[05:39] <pitti> (or does it?)
[05:40] <pitti> wgrant: just to avoid misunderstandings, did you kick off a new export now?
[05:40] <wgrant> pitti: I poked ops about it, haven't got a response yet, will repoke once UK appears I guess.
[05:40] <pitti> wgrant: ah, thanks
[05:40] <pitti> hm, why is consolekit still being installed by default
[05:41]  * pitti checks germinate
[05:43] <infinity> pitti: It works fine for me.  I can't figure out what WASN'T working before I rebooted.
[05:45] <infinity> postgres (27651): /proc/27651/oom_adj is deprecated, please use /proc/27651/oom_score_adj instead.
[05:45] <infinity> pitti: Yell at your upstream about that. :P
[05:45] <infinity> pitti: This is 2013, I shouldn't still be seeing those messages.
[05:46] <infinity> pitti: (Build went fine on arm64, though)
[05:47] <pitti> wow, already built?
[05:47] <pitti> it takes some 10 minutes with all the tests even on my machine
[05:47] <pitti> ah, time flies fast this morning
[05:48] <pitti> yay
[05:48] <pitti> infinity: upstream is on BSD :)
[05:48] <pitti> infinity: yeah, I've got a bug for oom_adj
[05:50] <infinity> pitti: My inability to recreate the broken situation I had with the new eglibc leads me to believe I just had something weird going on locally.  But I dunno.
[05:53] <pitti> infinity: (btw, I uploaded umockdev earlier)
[05:53] <infinity> pitti: Thanks.
[05:54] <infinity> pitti: You apparently have fans, because mir build-depends on it.
[05:54] <pitti> heh, yeah
[05:55] <pitti> I could actually also make upower build-dep on it, now that we have it in Debian, too
[06:15] <infinity> pitti: component-mismatches was your code, right?
[06:15] <pitti> infinity: I wrote the SVG/html report on top of it
[06:15] <pitti> http://people.canonical.com/~ubuntu-archive/component-mismatches.svg
[06:15] <pitti> not c-m itself
[06:15] <pitti> I thought that was part of LP?
[06:16] <infinity> Ahh, hrm.  I'm trying to figure out why the c-m python script appears to be crashing on a binary that doesn't exist. :P
[06:16] <pitti> ah no, that was NBS
[06:17] <infinity> Oh.
[06:17] <infinity> I bet it's because germinate's still crashing on pepo.
[06:17] <infinity> wgrant: Did anyone look into that?
[06:18] <wgrant> infinity: Colin said he might, but I suspect he was a bit busy.
[06:32] <Guest3903> i'm seeing quite serious issues while trying to install kubuntu using beta2 or latest ISO  -- looks like it's failing in some partition parsing, so the installer is completely stuck after the "Prepare" step
[06:33] <Guest3903> i have filed a bug here: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1238446
[06:33] <Guest3903> could someone help me debug, or populate the bug report and make it more useful? thanks
[06:59] <dholbach> good morning
[07:02] <Guest3903> hi dholbach: i am facing a serious ubiquity bug on the livecd. could you help me out? or at least help me provide a better bug report?
[07:02] <Guest3903> i have filed a bug here: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1238446
[07:06] <dholbach> Guest3903, I just had a look at /usr/share/apport/package-hooks/source_ubiquity.py - and if you could find an upstart/ubiquity.log and/or casper.log and/or oem-config.log that'd probably help
[07:07] <dholbach> Guest3903, but this is just me doing guesswork - I'm not an expert
[07:07] <Guest3903> dholbach: i am still on the livecd, so if you can tell me where, i can try
[07:08] <dholbach> Guest3903, also in /var/log - like the other log files you added
[07:08] <Guest3903> Attached /var/log/casper.log
[07:08] <Guest3903> i dont' see an upstart/ubiquity.log
[07:15] <dholbach> oSoMoN, happy birthday! :)
[07:16] <Guest3903> i have a feeling i can resolve the problem by clearing out all my partitions, but i thought i'd rather file the bug so that if it's a ubiquity problem, it can be fixed
[07:22] <infinity> Guest3903: What filesystem is/was on that partition?
[07:22] <infinity> Guest3903: Was it XFS?
[07:23] <Guest3903> no
[07:23] <Guest3903> infinity: there are 4 partitions, all of them are either vfat or NTFS
[07:24] <Guest3903> infinity: just added that info to the bug report
[07:25] <infinity> Fun.
[07:26] <Guest3903> yea, the XFS errors confused me too
[07:26] <infinity> Oh, there isn't even an sda4 (well, it probably exists as an extended container)
[07:26] <infinity> The plot thickens.
[07:26] <Guest3903> well, does GPT even have concept of an extended partition?
[07:28] <Guest3903> infinity: also, curiously, parted crashes while trying to print the partition table
[07:28] <infinity> Oh, this is GPT?  I missed that on the first.
[07:28] <infinity> pass...
[07:28] <infinity> Maybe GPT doesn't deal well with having holes in the numbering scheme?
[07:30] <infinity> Guest3903: What does /proc/partitions have to say about it?
[07:31] <Guest3903> infinity: udpated report
[07:33] <Guest3903> infinity: sda4 seems to be partition of unknown type with flag "msft-reserved" -- unlikely to be a hole
[07:34] <infinity> Guest3903: Yeah, I found that in the partman log too.  No idea what that is.    But if you're keen on debugging and fixing that, you might try asking xnox about it when he's around in an hour or two.
[07:35] <xnox> infinity: "in an hour or two" phhhh
[07:35] <infinity> Or right now. :P
[07:35]  * xnox yawns
[07:36] <Guest3903> infinity: yes, i'd rather help fix it if i can :)
[07:36] <xnox> Guest3903: i don't see anything obvious. And indeed it's strange that gpt partition table gives you head-aches.
[07:37] <Guest3903> and interestingly, the 13.04 installer did not have any issues on this exact setup
[07:38]  * xnox ponders why there is Permission Denied.
[07:38] <xnox> Guest3903: all of them are unmounted right?
[07:38] <Guest3903> xnox: yes, "mount" does not show any sdaX partitions mounted
[07:39] <xnox> Guest3903: ok. And what are the labes on /dev/sda2 and /dev/sda1 ?
[07:39] <xnox> *labels
[07:39] <Guest3903> xnox: sda1 is "SONSYS" and sda2 is "Recovery", type vfat and ntfs respectively
[07:40] <oSoMoN> dholbach: thanks :)
[07:40] <Guest3903> i have a feeling that SONSYS is the EFI System partition, Recovery the OEM "windows recovery" partition, no clue about msft-reserver, and the last partition my actual windows install, xnox
[07:42] <jderose> xnox: since you're around... any ideas as to why the OEM user isn't getting removed by oem-config after the user config runs? my highest priority item the next week is getting this fixed (on behalf of System76)... so please task me with whatever will help :)
[07:42] <xnox> Guest3903: infinity: so couple of things are weird. Cause EFI is usually first, not /dev/sda3, and parted thinks they are called "/dev/sda1	žé" and "/dev/sda2	9"
[07:44] <jderose> xnox: and a quick question: is there a way to make ubiquity do more verbose logging during the user config?
[07:44] <Guest3903> xnox: both look like EFI, though it's impossible: https://dpaste.de/ADXx
[07:44] <Guest3903> xnox: i think sda1 is ESP for sda2 "recovery" OS, and sda3 is ESP for sda4/sda5 "windows" OS
[07:44] <xnox> jderose: i wonder if it is a side-effect of ubiquity starting a logind session. Let me get you version numbers such that we can test downgrading oem-config "between the install & prepare for final shipping" stage.
[07:45] <Guest3903> xnox: and if i power my laptop using "assist" button, the recovery ESP kicks in and starts the "recovery" OS (which is windows recovery mode)
[07:45] <Guest3903> if i power on using the power button, windows starts as usual
[07:45] <xnox> jderose: yes, more verbose mode would be, I still think "debug-ubiquity" at kernel cmdline, https://wiki.ubuntu.com/DesktopCDOptions
[07:46] <jderose> xnox: yeah, my hunch is it's related to the new PAM stuffs in ubiquity-cm, but i don't have enough ubiquity knowledge to grok what's really going on :)
[07:46] <xnox> jderose: oh right, yeah.
[07:46] <xnox> jderose: you can't delete a user with active pam session.
[07:47] <xnox> jderose: we usually hang out on #ubuntu-installer, but I guess we can continue here.
[07:47] <jderose> xnox: so bits of the user config are running as the OEM user then?
[07:48] <xnox> cjwatson: infinity: so ubiquity-dm opens a pam/login session for the oem-config user.... thus can't delete it whilst it's well still logged in. Where/how should the user account be deleted? oem-config/post-stop?
[07:49] <Guest3903> xnox: any more useful info i can provide/
[07:50] <xnox> Guest3903: what's the output of "$ sudo parted -l" ?
[07:51] <Guest3903> xnox: https://dpaste.de/7vqi same error pretty much
[07:51] <infinity> xnox: Yeah, if there's a point where we shut down that session, that's when we should delete the user, I guess.
[07:52] <xnox> jderose: so what happens is that machine boots normally -> starting lightdm even is emitted in upstart, oem-config job starts and blocks lightdm. Oem-config job checks for magic file, and start ubiquity-dm as root. At that point ubiquity-dm creates a pam session for the oem-config user ( i think). At the end of the ubiquity-dm run, it deletes the user.
[07:52] <xnox> *not user but session.
[07:52] <xnox> infinity: right, let me look at that code path and check if I can close the pam session earlier, before deleting the user.
[07:53] <xnox> Guest3903: i think your bug is against parted and or windows. So partition/filesystem labels really should not have multiwide characters / unknown encoding.
[07:54] <xnox> Guest3903: if you can boot into windows, open partitioning/admin utilties and try to rename or remove partition labels of whatever is /dev/sda1 and /dev/sda2 in windows.
[07:54] <xnox> Guest3903: then somehow reboot or check that windows still works.
[07:54] <Guest3903> but kde partition manager seems to understand the labels fine, xnox.. so it could be a partition thing?
[07:54] <xnox> Guest3903: then boot up the 13.10 live cd and see what's there.
[07:54] <Guest3903> *parted thing
[07:54] <xnox> Guest3903: hm, we do have old parted.
[07:55] <Guest3903> sounds like a regression still, because 13.04 installer worked on the same setup. i should probably try redoing that to test
[07:55] <xnox> Guest3903: what does kde partitioner manager say? maybe screenshot, or copy strings?
[07:55] <Guest3903> xnox: kde partition manager screenshot is in the report
[07:55] <Guest3903> xnox: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1238446/comments/13
[07:55] <xnox> Guest3903: well, you can fetch /var/log/installer/* from the installed 13.04 and check if the partitions were named the same back when you did 13.04 install. Not much has changed in parted stack in the installed in 13.10.
[07:55] <Guest3903> argh. https://launchpadlibrarian.net/153474755/snapshot1.png
[07:57] <Guest3903> xnox: i don't have the installed system any more, sorry.. i could try running the 13.04 installer again i guess
[07:57] <xnox> Guest3903: strange.
[07:57] <Guest3903> i am sure it worked, though, because i cloned my current disk from the same disk image used when i had installed 13.04
[08:01] <jderose> xnox: so when i use debug-ubiquity, does this additional logging go into syslog, or are there other log files i should be looking at?
[08:01] <xnox> jderose: /var/log/installer/oem-config i think =/ or look at other files under /var/log/installer/*
[08:01] <xnox> jderose: there should also be /var/log/upstart/[oem-config|ubiquity].log
[08:05] <jderose> xnox: upstart/ubiquity.log - http://paste.ubuntu.com/6221392/
[08:05] <jderose> not sure if that ValueError is related or not
[08:06] <xnox> i don't think so.
[08:06] <xnox> it's probably from the "normal/first install"
[08:06] <xnox> not from oem-config run.
[08:08] <Guest3903> whoa, the parted in 13.10 is 3 years old! the lates t release was also in 2012 .. any idea why i
[08:09] <Guest3903> any idea why we have such an old release?
[08:10] <xnox> Guest3903: because FS code was removed in the new major parted series, and debian-installer is not ported yet to the new world order.
[08:10] <Guest3903> xnox: ah i see
[08:11] <Guest3903> xnox: ok, i am going to try booting the kubuntu 13.04 iso to see if it actually works or i'm just misremembering
[08:12] <Guest3903> can't think of anything else useful to do :)
[08:12] <Guest3903> apart from booting to windows and changing the partition labels as you suggested
[08:13] <xnox> Guest3903: or change the labels using KDE partition manager & reboot the installer again.
[08:13] <Guest3903> but parted is not tripping up on the labels, is it? it's tripping up on the device names right
[08:14] <xnox> no, device names are fine.
[08:14] <xnox> i think.
[08:15] <xnox> infinity: it's hallarious but purely from packaging I'm failing to see where "ubiquity" ui is actually started upon oem-config-firstboot. lol.
[08:15] <jderose> xnox: i attached a tarball of all of /var/log after running the user config (and with the debug-ubiquity boot arg) - https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1231166
[08:16] <xnox> jderose: thanks.
[08:16] <jderose> xnox: well, makes me feel a little better about me struggling to find my way around ubiquity :P
[08:16] <xnox> infinity: bug #624888
[08:20] <infinity> xnox: Did the s/deluser/userdel/ thing get reverted, or does userdel now shut you down too?
[08:21] <jderose> infinity: i looked at that earlier today... currently it's using userdel, in oem-config-wrapper i believe is the script
[08:22] <xnox> infinity: does it know about systemd?
[08:22] <xnox> infinity: well logind.
[08:24] <jderose> if the problem is trying to delete the OEM user when that user is logged, can the userdel bit be moved to later stage?
[08:25] <infinity> xnox: Effed if I know.
[08:26] <infinity> xnox: uderdel is pretty dumb, it's not meant to know about much at all.
[08:26] <infinity> xnox: Does userdel perhaps just need a '-f' to fix the bug?
[08:26] <jderose> it's being called with `userdel --force --remove oem`
[08:27] <xnox> jderose: || true
[08:27] <infinity> I guess force needs to be taught to force harder...
[08:27] <jderose> well, yeah, that bit too :P
[08:27] <xnox> so we don't fail, on not removing oem-config user.
[08:28]  * xnox will move it to post-stop exec line in upstart job and check what happens.
[08:28] <jderose> yeah, that seems a bit fragile... better to get a loud error in that case so regressions are noticed sooner
[08:28]  * xnox goes to find coffee
[08:29] <jderose> xnox: infinity: thanks for your help on this! much thanks from System76 :D
[08:31] <Guest42952> xnox: i was wrong, 13.04 ubiquity has the exact same problem. it's stuck after "preparing"
[08:31] <Guest42952> and parted also errors out with the same message
[08:31] <Guest42952>  and yet again kde partition manager works perfectly
[08:33] <infinity> Guest42952: Can you try relabelling to test xnox's theory that the hang is due to multibyte chars?
[08:33] <infinity> Guest42952: We can argue if that's a bug that parted (or something) can't read those labels, and it probably is, but it would be nice to prove it first. :)
[08:34] <Guest42952> well kde partition manager is not allowing me to change labels
[08:35] <Guest42952> but if both blkid and kde partition manager can read the labels fine, it has to be a Parted issue, right?
[08:35] <infinity> I'm not convinced that parted's problem is the labels just yet.
[08:38] <pitti> seb128: bonjour, ça va ?
[08:38] <pitti> seb128: did you already talk to the release team about 3.10.1 bits next Monday?
[08:38] <seb128> pitti, salut, oui, et toi ?
[08:38] <pitti> seb128: je vais très bien, merci
[08:38] <seb128> pitti, no, I planned to just SRU those, we don't have so much 3.10 anyway
[08:39] <pitti> seb128: ok, then I perhaps upload gnome bug 709223 as a patch right now
[08:39] <pitti> seb128: I'll release pygobject 3.10.1 on Monday with that (and a memleak fix)
[08:39] <seb128> pitti, if you want it in the release, today seems a better bet than monday in any case
[08:39] <seb128> who knows we might not get respins after monday
[08:40] <infinity> Monkeys may fly, too.
[08:40] <infinity> (But I appreciate the enthusiasm and confidence)
[08:40] <pitti> oh, I thought it was the pigs who can fly, but perhaps that doesn't work in Canada? :-)
[08:41] <xnox> pitti: britain is a funny place.
[08:41] <xnox> infinity: or not yet?
[08:41] <xnox> =)
[08:41] <pitti> in Canada they say "Adams can sleep"
[08:41] <infinity> pitti: It is, and the monkeys traditionally do something slightly less tasteful.
[08:41] <infinity> xnox: Not in London until Sunday.
[08:41] <xnox> pitti: The Adams family, tudutudutudu.
[08:41] <Guest42952> infinity: anything else i can provide to help?
[08:41] <pitti> oh those mental pictures *off*, *off*!
[08:42] <infinity> Guest42952: Not sure, TBH.  Hence why I pointed you at xnox.  Not my area of expertise. :)
[08:42] <Guest42952> fair enough. xnox, anything else that could help debug/
[08:42] <xnox> not really no.
[08:45] <Guest42952> ok. thanks for all the help, xnox, infinity!
[08:46] <tvoss_> pitti, pin
[08:46] <tvoss_> g even
[08:46] <pitti> hey tvoss_
[08:48] <jderose> er, what did i do... now oem config is launching the ubiquity installer rather than the user config... hmm, time to unbork my VM i guess
[08:51] <tvoss_> pitti, mind having a look here: https://bugs.launchpad.net/mir/+bug/1238417
[08:51] <pitti> tvoss_: queueing
[08:52] <tvoss_> pitti, ack and thx
[08:58] <jderose> xnox: so what were you moving to post-stop?
[08:59] <xnox> jderose: i am investigating at the moment.
[09:00] <jderose> xnox: please let me know if there is anything you want me to try/test
[09:00] <xnox> jderose: there is also kernel cmd line option "debug-oem-config" in addition to "debug-ubiquity"
[09:00] <jderose> ah, okay, i'll try that too. my VM is again submitting to my will, so i'm ready to go
[09:02] <jderose> xnox: is there any use in using debug-oem-config and debug-ubiquity together, or should I just use debug-oem-config?
[09:06] <xnox> i think you just need "debug-oem-config" but debug-ubiquity will not hurt.
[09:08] <jderose> okay, i just tried without the "|| true" bit, hopefully the failure will log something useful...
[09:13] <jderose> xnox: attached another /var/log tarball - https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1231166
[09:14] <xnox> jderose: i think that should work: http://paste.ubuntu.com/6221565/
[09:15] <xnox> jderose: so, "before shipping to use"
[09:15] <xnox> jderose: modify /etc/init/oem-config.conf to include the bits at the end from "post-start script ... end script"
[09:15] <xnox> jderose: then reboot, do end user config, and observe that oem-config user is removed.
[09:15] <jderose> xnox: okay, trying now...
[09:24] <jderose> xnox: yup, that fixes it!
[09:25] <jderose> oem isn't in passwd or group, and /home/oem has been removed
[09:25] <jderose> user login works as expected
[09:26] <xnox> jderose: good.
[09:26] <xnox> jderose: we do keep ubuntuone package for the end user configuration. but it's a separate package from oem-config, FYI.
[09:27] <jderose> yeah, i saw the plugin is in a separate binary package... first thing i tried was removing it, just in case that was the problem :P
[09:28] <jderose> but we'll leave it in place, btw
[09:29] <jderose> xnox: what's the best way for me to help with this? https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1237694 <= my next highest priority
[09:29] <xnox> jderose: i'm working on bug #1226912 at the moment
[09:30] <jderose> (also, BTW, i'm not 100% sure 2.15.21 was what introduced that regression)
[09:30] <xnox> hm.
[09:31] <jderose> xnox: so does this only happen when you "try ubuntu first" rather than directly choose "install ubuntu"? I think i hadn't noticed this because i tend to use the latter
[09:32] <xnox> jderose: no, if you press Esc at boot splash and select "try ubuntu without changing your computer" text menu item.
[09:32] <xnox> jderose: or e.g. if you select that on an UEFI machine.
[09:32] <jderose> gotcha
[09:32] <pitti> bdmurray, stgraber, ScottK: would you mind ack'ing the psql microrelease uploads for all stables? (they have a MRE, and nothing out of the ordinary, so it should be rather straightforward); bug 1237248
[09:45] <jderose> xnox: okay, my brain is mush and i need sleep now, but i'll do what i can to help out on these ubiquity bugs tomorrow, and next week. thanks again!
[09:46] <xnox> jderose: no worries. Thank you.
[10:12] <pitti> infinity: I uploaded apport to disable crash reporting to LP for final release (as per release checklist); it needs to go into the final image, but not necessarily today yet, so please accept whenever it's convenient
[10:13] <infinity> pitti: Yeahp, thanks.
[10:14] <infinity> pitti: To be clear, this is just disabling the "open a web browser and file a bug and make me hate you for it" part, not the reporting to errors.ubuntu.com, right?
[10:14] <pitti> infinity: correct, the whoopsie/daisy parts stay
[10:14] <pitti> infinity: same procedure as last release (and the ones before..)
[10:15] <infinity> pitti: Yeah, it's gotten a bit fuzzy with whoopsie in the mix.  I think we even had one release (or most of one) where we never had the web browser bits.  I liked that cycle. :P
[10:16] <pitti> infinity: before whoopsie we completely disabled apport, to avoid the CPU overhead
[10:16] <infinity> pitti: No, I meant during a dev cycle, we didn't re-enable the browsery bits once.
[10:16] <pitti> then we had that rather long and heated discussion, I admitted defeat, and now it's done like that ever since
[10:16] <pitti> infinity: we usually didn't do before alpha-2
[10:16] <infinity> Anyhow, no big deal.  Current situation works.  Thanks for the upload.
[10:16] <pitti> but it's a matter of some gut feeling "it's time now"
[10:33] <ev> slangasek, pitti, others: I'm finding it hard to find time for bug 1235436. Is anyone available to help out?
[10:40] <xnox> ev: i think it's a funny integration with ro-system images. You cannot rely on file being present or not. Instead you should check if contents of it is zero / non-zero. Or some such. As we can make that file available by default, and allow users over-writting its content, but not completely delete the file.
[10:40] <xnox> ev: this is similar to the timezone changes not persisting across ro-system upgrades bug.
[10:41] <xnox> ev: how is /etc/init/apport-noui.conf created at the moment?
[10:41] <ev> xnox: it's shipped as part of apport
[10:41] <xnox> sorry, i mean the /etc/apport/autoreport.
[10:41] <xnox> that shipped as well?
[10:42] <xnox> ev: i think will be SRUing that bug report.
[10:43] <ev> xnox: oh dear. We need to add that to the writable paths - it's created by system-settings
[10:43] <pitti> it's not in the current images at least
[10:43] <pitti> so, another victim of our hacked-up /etc? :-/
[10:44] <xnox> ev: and you can't test with [ -e ], as system-image updates are ro, and bind-mounted. If user "deletes" the bind-mount, it would be recreated on reboot.
[10:45] <xnox> ev: but you can make it writable, thus one needs to check it's contents, or some such. Which means that maybe you can reuse existing whoopsie config file which is parsable and add "auto=True" key to it.
[10:45] <ev> xnox: can you please add your thoughts to the bug so we're tracking this in a single place?
[10:45] <xnox> ev: ok.
[10:45] <ev> thanks, just trying to manage calls and chatting here at the same time
[10:45] <xnox> ev: and then there is the race to fix of multiple apports tracing the same thing =)))))
[10:45] <ev> I'm going to lose some details :)
[10:46] <pitti> xnox: nah, let's not automatically modify conffiles
[10:46] <xnox> pitti: hm, good point.
[10:46] <pitti> (sorry, just half a brain cell here either, it seems today is the day when I get bombarded with "OMGcanyoulookintobugXXXXX" requests)
[10:46] <xnox> ev: right after I make ubiquity to stop spinning in an infinite loop.
[10:46] <xnox> pitti: ditto =)
[10:47] <pitti> but please let's not do any knee-jerk addition of files o writable-files
[10:47] <pitti> the current implementation for handling files there is quite frankly rather broken and not maintaintable at all
[10:48] <pitti> ev: I'd rather move the file to /lib or something
[10:48] <pitti> ev: or an alternative lookup path to /userdata, or whichever path we actually have left for putting data into
[10:48] <pitti> as we essentially said "/etc/ is not for configuration any more", I guess /userdata is the logical replacement
[10:54] <ev> pitti: I honestly don't mind where we put it
[10:54] <ev> definitely deferring to your better judgement on this :)
[11:14] <infinity> pitti: I'm emptying out the stragglers in the NEW queue, and there's an oddity there from you.
[11:15] <infinity> pitti: You removed flphoto from saucy because it "didn't work with libgphoto 2.5+" and then, on the same day, you uploaded a no-change rebuild, which got cause in NEW because you'd already removed the previous version.
[11:15] <infinity> pitti: So, which is it? :)
[11:15] <infinity> s/cause/caught/
[11:19] <pitti> infinity: I think the reupload was an error, I probably just forgot to rm it from my local "to rebuild"  folder, sorry
[11:42] <tvoss_> pitti, wondering: which value is adjusted by upstart when defining an oom adjustment for a job?
[12:05] <ogra_> tvoss_, how does that matter, since we artificially set it to what we like from lightdm
[12:06] <ogra_> (which is -10 for all apps started by the session currently)
[12:07] <ogra_> tvoss_, http://bazaar.launchpad.net/~mad-wol/upstart/oom-score-stanza/revision/1280
[12:10] <ogra_> tvoss_, "/proc/%d/oom_score_adj", getpid ());
[12:10] <ogra_> it seems to also just use the /proc node
[12:11] <ogra_> (and defaults to 0 as you can see in the code)
[12:11] <ogra_> tvoss_, if you want to allow users to set it you will have to change the kernel i fear
[12:11] <tvoss_> ogra_, not users, u8, but I think I found a way
[12:11] <ogra_> u8 runs as phablet
[12:11] <ogra_> since it gets started by the session upstart process
[12:12] <ogra_> which runs as phablet as well
[12:12] <tvoss_> ogra_, yup, but we can use setcap
[12:12] <ogra_> ah, that could possibly work
[12:27] <mdeslaur> @pilot in
[12:36]  * dholbach hugs mdeslaur
[12:36]  * mdeslaur hugs dholbach
[13:09] <roadmr> hello folks! I was following the procedure to secure-boot over pxe (https://wiki.ubuntu.com/UEFI/SecureBoot-PXE-IPv6) and found what appears to be a typo in shim.efi.signed, it tries to load "grubx64.efi(", I found this by monitoring the tftp log file after it failed to load "grubx64.efi"
[13:48] <GridCube> I wonder why "users" list two times any user name, i understand that users list currently logged users to a system, so it means that my user is logged twice?
[13:54] <xnox> slangasek: ^ see roadmr message.
[13:57] <dobey> GridCube: #ubuntu is for asking for help on ubuntu. the one user listed multiple times is because of virtual terminals and such (if you have terminal windows open, for example)
[13:59] <GridCube> oh correct! dobey :D i opened a bunch of terminals and i got a bunch of my names, thanks a lot. (and sorry for using the wrong channel)
[14:19] <ice9> I want to start with Ubuntu development so where to find simple bugs to start with?
[14:25] <rbasak> ice9: try looking for bugs tagged 'bitesize'. Eg: https://bugs.launchpad.net/ubuntu/+bugs?field.tag=bitesize&orderby=-date_last_updated&start=0
[15:09] <mardy> seb128, Laney: about the EDS integration with UOA, I just forwarded you a patch
[15:09] <seb128> mardy, I was just reading that, what did you ask to mbarnes? if it would be easy to backport the fix?
[15:10] <mardy> seb128, Laney: it's a backport of the OAuth support for calendar, to 3.8
[15:10] <mardy> seb128: yes, and he did this in a very few minutes
[15:10] <seb128> hehe
[15:10] <mardy> seb128: so I guess it's not tested, but that's up to us
[15:10] <seb128> the guy is a rockstar ;-)
[15:10] <seb128> mardy, right
[15:10] <seb128> mardy, it's too much of a diff for saucy anyway
[15:10] <seb128> mardy, but let's land early next cycle (then maybe backport it)
[15:12] <mardy> seb128: maybe we can keep it in -proposed, and give it quite some time for testing before pushing it to everyone?
[15:13] <seb128> mardy, yes, just not for saucy since we are frozen for release since yesterday
[15:13] <mardy> seb128: sure
[15:13] <seb128> mardy, but I'm keeping it on my todo for after next week
[15:13] <mardy> seb128: thanks
[15:18] <roadmr> xnox: perhaps I could file a bug about the shim problem? is lp:ubuntu/shim-signed a good place for that?
[16:06] <mdeslaur> @pilot out
[16:11] <slangasek> ev: I could kick in some time for buG #1235436, but would want pitti's and your guidance on architecture
[16:12] <ev> slangasek: happy to provide guidance, I just don't want to see it fall on the floor as I transition. It's best that more than my eyes are watching its progress.
[16:12] <slangasek> roadmr, xnox: that's no typo in shim.efi.signed; that wiki page was a bit optimistic, and assumed that we would get the fixed shim back signed from MS in a timely fashion
[16:13] <slangasek> roadmr: i.e., this is fixed in shim 0.4-0ubuntu4, but we've been waiting 2 weeks for a signature
[16:15] <slangasek> ev: so if I were to take a stab at this, I would do what I described, having whoopsie scan directly and give whoopsie an 'autoupload' config option.  Where should that option live for whoopsie? Should it reuse /etc/apport/autoreport, or would you like an /etc/whoopsie/autoreport?  Or do you disagree with having whoopsie directly handle this?
[16:15] <ev>  /etc/default/whoopsie?
[16:15] <ev> slangasek: or either of those. I'm not fussy
[16:16] <ev> though pitti and xnox discussed concerns over using /etc on touch
[16:16] <ev> since it's not writable
[16:17] <slangasek> ev: /etc/default/whoopsie has the difficulty that it's owned by the whoopsie package, so how do we configure it differently for phones vs. notphones
[16:18] <slangasek> so, probably needs to be a separate file
[16:18] <infinity> Writing to /etc at runtime is wrong even on classic UNIX systems.
[16:18] <slangasek> (and what was supposed to own that file anyway, since /etc/apport/autoreport still doesn't exist?)
[16:18] <ev> slangasek: *nods*
[16:18] <infinity> At least, I assume we're talking about runtime settings here.
[16:18] <ev> slangasek: it's created by system-settings
[16:18] <ev> but it should be already populated
[16:19] <slangasek> oh?
[16:19] <ev> we got agreement from legal on that, provided we mention it in the first use dialog
[16:19] <ev> and it should be - it's in the spec
[16:19] <infinity> Which belong in user configs or system-wide stuff in /var (or whatever crazy Android equivalent the phone is currently using)
[16:19] <xnox> ev: we don't have first use dialog.
[16:19] <ev> though no one implemented that, did they
[16:19] <xnox> yet.
[16:19] <ev> wooooo
[16:19] <slangasek> heh
[16:19] <ev> priorties
[16:19] <slangasek> so, by default we have no mention of it, which means by default we can't turn it on?
[16:20] <xnox> slangasek: ev: does that file has contents? we can bind mount it and writable, but then it's always present but has content that can be changed.
[16:20] <ev> slangasek: we should check with legal - maybe there's a way out of this
[16:20] <slangasek> xnox: to be determined
[16:20] <ev> it'd be really awful if we had it off by default
[16:20] <ev> as that pretty much guarantees it wont get used
[16:21] <slangasek> ev: I'm not going to try to circumvent the legal guidance here
[16:21] <slangasek> because I agree with it ;)
[16:21] <ev> *nods*
[16:21] <slangasek> for now, I'll focus on sorting out the backend
[16:21] <slangasek> is system-settings supposed to have a toggle for this?
[16:21] <ev> though I am curious as to why you were seeing apport-noui running if nothing was creating that file
[16:21] <ev> yes, and it does
[16:21] <ev> I wrote it
[16:21]  * ev checks on the actual phone
[16:22] <slangasek> ev: because I created the file myself for testing ;)
[16:23] <ev> oh right
[16:23] <ev> and here I was worried it was all going to hell in a handbasket
[16:23] <ev> (not that it isn't :-P)
[16:24] <ev> yup, it's there
[16:24] <ev> security and privacy -> diagnostics
[16:35] <slangasek> ev: ah, so the toggle is there, and it's selected, but it doesn't seem to control /etc/apport/autoreport since I don't have that file
[16:43] <ev> slangasek: on a call, sorry!
[16:43] <roadmr> slangasek: oh I understand, I'll wait for the next version then, rather than filing a bug.
[16:43] <roadmr> slangasek: (re: the "typo" in the shim)
[16:45] <ogra_> slangasek, so since i dont think that we will fix the ureadahead bug before release, would you be very opposed if i shipped an override upstart job for ureadahead (from lxc-android-config or ubuntu-touch-session) that mounts and unmounts debugfs at a place like like /dev/.ureadahead dynamically from pre-start/post-stop scripts ?
[16:46] <slangasek> ogra_: er, what would doing that help?
[16:46] <ogra_> slangasek, it generates proper pack files on the phone here
[16:46] <slangasek> yes, I'm opposed to it because we analyzed the bug and showed that the debugfs mount had nothing to do with the failures
[16:47] <stgraber> right, it'd generate the packs and then never use them and then generate them all over again the next boot since at the time ureadahead starts it won't find them
[16:47] <slangasek> ogra_: did the problem of /var/lib/ureadahead not being mounted before ureadahead starts get solved?
[16:47] <ogra_> stgraber, oh ? why ? they are in a rw dir
[16:48] <ogra_> stgraber, that would surely be mounted already once the upstart job fires
[16:48] <stgraber> ogra_: ureadahead starts before any of the bind-mounts are applied
[16:48] <ogra_> well it definitely works fine on my maguro with such a hacked up upstart job
[16:48] <ogra_> stgraber, ?
[16:48] <ogra_> stgraber, dont you mount them in the initrd ?
[16:48] <stgraber> no
[16:48] <ogra_> oh
[16:48] <stgraber> mountall mounts those
[16:49] <stgraber> (note, we had that very discussion at least once already ;))
[16:49] <ogra_> slangasek, nope, my job would have to start later
[16:49] <ogra_> stgraber, right, i just noticed that i had a modified start on line in my test code
[16:50]  * ogra_ would really like to get these 10sec faster boots :/
[16:50] <slangasek> certainly; but you're not going to get that unless you manage to write pack files that actually get read again
[16:51] <slangasek> and that's not something that lends itself to a quick'n'dirty change
[16:51] <ogra_> so i would need to write them to a temporary space and copy them ...
[16:51] <slangasek> /sys/kernel/debug, btw, should almost always be mounted before the local filesystems
[16:51] <slangasek> no
[16:51] <slangasek> "temporary space and copy" means that they again won't be in the right place on the next boot
[16:52] <stgraber> the real fix there is to get the initrd to mount /var/lib/ureadahead (I believe that was the conclusion of the discussion we had last time)
[16:52] <stgraber> since that's the only way to have that directory readable and writable early enough for ureadahead
[16:52] <ogra_> ok
[16:52] <cjwatson> That's also a workaround, but a better one
[16:53] <ogra_> me grumbles about the metapackage update he just runs ...
[16:53] <ogra_> I: Checking Release signature
[16:53] <ogra_> gpgv: Signature made Fri Oct 11 18:36:48 2013 CEST using DSA key ID 437D05B5
[16:53] <ogra_> gpgv: BAD signature from "Ubuntu Archive Automatic Signing Key<EMAIL_ADDRESS>[16:53] <ogra_> i get that pertty often in recent times
[16:53] <ogra_> (a second fresh run usually works then)
[16:54] <stgraber> cjwatson: it's not pretty I agree but I can't think of a cleaner way of doing it since / is read-only and so can't possibly contain the pack files. ureadahead is meant to start before mountall so can't depend on anything mounted by mountall, therefore we need the kernel, the initrd, upstart of ureadahead itself to mount the pack file location. The least ugly option being the initrd.
[16:55] <stgraber> *or
[16:57] <cjwatson> stgraber: Clint offered the general outline of a solution in https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/523484/comments/34 which I think would be viable
[17:00] <stgraber> cjwatson: that'd mean the very early boot wouldn't benefit from ureadahead but it seems like an acceptable compromise to have a solution which works for everyone
[17:01] <stgraber> though I don't think we should attempt something like that for saucy
[17:01] <cjwatson> stgraber: ureadahead is "start on starting mountall" anyway, and not very much else runs while mountall is running; I don't think it would delay it much unless the fs containing /var/lib/ureadahead is unreasonably slow to mount
[17:02] <cjwatson> stgraber: There are probably some complexities related to ureadahead-other
[17:02] <cjwatson> stgraber: Yeah, I thought about taking a day or two and doing it, but I think it's too risky now
[17:02] <stgraber> sounds like something that should be done in early 14.04
[17:03] <cjwatson> Yep, we definitely should, that bug has dragged on way too long
[17:03] <stgraber> ogra_: http://paste.ubuntu.com/6223336/ should (untested) give you a working ureadahead and also fix the fsck flag you mentioned the other day.
[17:04] <ogra_> stgraber, awesome !
[17:04] <ogra_> i'll test that on the weekend
[17:04] <ogra_> (and take care of landing it on monday)
[17:07] <stgraber> cjwatson: I commented in the bug and milestoned for 13.11 so it hopefully ends up on a list somewhere and we don't forget about it for 14.04
[17:10] <cjwatson> stgraber: thanks
[17:17] <sarnold> infinity: no, I haven't looked at curtin 1220434 yet
[19:49] <slangasek> xnox: why the reopen of the dbus task on bug #1234731?
[20:26] <cjwatson> jdstrand: hmph, I wish I'd noticed earlier that apparmor/saucy has started pulling Python 2 back into standard, when raring had relegated it to desktop
[20:26] <jdstrand> why is it doing that?
[20:26] <cjwatson> For the sake of one script that would probably take five minutes to port
[20:26] <jdstrand> we wrote everything for python3
[20:26] <cjwatson> /usr/sbin/apparmor_status
[20:26] <cjwatson> #!/usr/bin/python
[20:26] <jdstrand> that should be py3
[20:26] <jdstrand> hrm
[20:27] <cjwatson> certainly doesn't seem to require anything 2-specific
[20:27] <jdstrand> yeah, that script is bi-lingual no less
[20:28] <jdstrand> we did it that way intentionally
[20:28] <jdstrand> but obviously got part of it wrong
[20:30] <jdstrand> cjwatson: it is a one character fix that I would be happy to upload
[20:30] <jdstrand> of course, I'd probably need a landing request and everythign else
[20:31] <mdeslaur> lol @ bilingual python
[20:56] <infinity> jdstrand: I'm all for the one-charater fix and no more python2.7 in standard, BTW.
[21:16] <linux> It will be great if ubuntu have on login option to choose effects ccsm like
[21:16] <linux> minimum , medium , maximum with all posibilities like fire , wather , cube ... etc that will be great in unity for new users like girl and boys
[23:39] <Noskcaj> There's spam on http://qa.ubuntuwire.com/bugs/rcbugs/ again
[23:40] <Noskcaj> Also, is there any chance we could sync libtar? it fixes a CVE and nothing else
[23:44] <slangasek> Noskcaj: libtar would be allowed in if someone synced it, yes
[23:55] <Noskcaj> slangasek: Is there any chance you cpuld, or at least file a bug. I'm not able to do anything other than irc curretly


[04:05] <persia> !extras is extras.ubuntu.com is an additional !repo that contains new software made available after the formal release.  This software is unsupported by the Ubuntu team, but the original authors offer some support.
[04:06]  * persia goes off to have a heart-to-heart with ubottu about that response
[04:20] <elky> !extras is extras.ubuntu.com is an additional !repo that contains new software made available after the formal release.  This software is unsupported by the Ubuntu team, but the original authors offer some support.
[04:20] <elky> !no extras is extras.ubuntu.com is an additional !repo that contains new software made available after the formal release.  This software is unsupported by the Ubuntu team, but the original authors offer some support.
[04:20] <elky> !no extras is <reply>extras.ubuntu.com is an additional !repo that contains new software made available after the formal release.  This software is unsupported by the Ubuntu team, but the original authors offer some support.
[04:20] <elky> !extras
[04:20] <elky> persia, ^
[04:21] <persia> !no extras is <reply> extras.ubuntu.com is an external repository for new software made available after the Ubuntu release.  This repository is not part of the Ubuntu distribution and the software is completely unsupported by the Ubuntu team, but the original authors may offer some support.
[04:21] <persia> @login
[04:21]  * persia !#%&
[04:22] <persia> elky, Thanks, although as noted above, part of my delay was sorting the text, rather than just the syntax.  Didn't seem to do any good though :(
[04:25] <persia> Ugh, and the new text misses !repo :(
[04:25] <persia> !no extras is <reply> extras.ubuntu.com is an external !repo for new software made available after the Ubuntu release.  This repository is not part of the Ubuntu distribution and the software is completely unsupported by the Ubuntu team, but the original authors may offer some support.
[04:25]  * persia leaves the factoid alone now
[04:32] <elky> persia, you're satisfied with your latest recommendation?
[04:33] <elky> !no extras is <reply> extras.ubuntu.com is an external !repo for new software made available after the Ubuntu release.  This repository is not part of the Ubuntu distribution and the software is completely unsupported by the Ubuntu team, but the original authors may offer some support.
[04:33]  * elky does it anyway
[04:41] <persia> I'm satisfied.  I don't have approval, but it's lots better than the previous one.
[04:41] <persia> Thanks for the commit.
[04:42] <persia> You don't happen to know what I ought do to fix my @login issue, do you?
[05:03] <Tm_T> persia: I believe tsimpson and jussi are the ones to talk to
[05:03] <persia> Tm_T, Thanks.
[05:09] <persia> Oh, and just for sake of completeness, I did get approval for that final text from a member of the ~a-r-b
[05:16] <Tm_T> ?
[05:17] <persia> Regarding the factoid change above: when it was changed I still didn't have approval from the group responsible for administering extras.ubuntu.com.
[05:17] <persia> Having received approval, I wanted to share, in case any issues were raised in dispute, etc.
[05:17] <Tm_T> aaah
[05:18] <Tm_T> good
[05:18]  * persia likes to be careful, and prefers consensus or at least avoidance of disagreement except when there are substantive issues to discuss
[05:19] <elky> Geekdoms and fiefdoms and all that.
[05:20] <persia> Right.
[06:12] <bazhang> Qwert, how may we help you
[06:35] <Qwert> Hello
[06:36] <bazhang> hi
[06:36] <Qwert> Is it advisable to guide about keylogger installation?
[06:36] <Qwert> http://sourceforge.net/projects/lkl/files/
[06:39] <Qwert> bazhang?
[06:47] <Qwert> Pici?
[06:53] <Tm_T> Qwert: what exactly you're suggesting?
[06:54] <Qwert> Tm_T: Well, its about keylogger.. is it advisable to guide about its installation?
[06:55] <Tm_T> in ubuntu channels? IMHO no
[06:57] <Qwert> Tm_T: Yes.
[06:57] <Qwert> Tm_T: Thanks
[06:57] <Tm_T> Qwert: I think this discussion is more suitable for -irc anyway
[06:58] <Tm_T> ldunn: hi, how can we help you?
[11:57] <jpds> Righto.
[12:52] <bazhang> d3v0, hi
[12:53] <d3v0> hello
[12:54] <d3v0> why did i get taken here =/
[12:54] <d3v0> i'm banned from #ubuntu =/
[12:54] <bazhang> d3v0, ban forwarded from #ubuntu
[12:55] <d3v0> what for exactly?
[12:57] <d3v0> =/
[12:57] <d3v0> someone mind explaining?
[12:59] <bazhang> I'd guess its your quit message
[12:59] <d3v0> hahaha
[12:59] <d3v0> my bad
[12:59] <bazhang> though if I am off jrib can enlighten
[12:59] <ikonia> I don't find that funny
[13:00] <d3v0> i thought it was brb house on fire
[13:01] <d3v0> its changed now though, didnt realise it was an offence
[13:01] <d3v0> well, offensive maybe
[13:01] <d3v0> actually, definitely, i apologise
[13:05] <d3v0> so is this ban permanent or what?
[13:07] <ikonia> no, as long as you can make sure you keep your language, including part message polite and not offensive I'm happy to remove the ban
[13:07] <d3v0> no problemo
[13:07] <ikonia> ok
[13:08] <ikonia> there you go, the ban has been removed, you're welcome to leave this channel and join #ubuntu
[13:08] <d3v0> cheers
[13:10] <bazhang> d3v0, please part here, thanks
[13:10] <d3v0> (Y)
[13:11] <Pici> Anything in the scrollback I should take a look at?
[13:11] <ikonia> !fuck-#ubuntu-offtopic
[13:11] <bazhang> that kuroi fellow seems to be an issue network wide
[13:11] <Pici> ikonia: we don't have any factoids like that.
[13:12] <ikonia> I know
[13:12] <bazhang> thankfully
[13:12] <ikonia> rockhopper is claiming it does in #ubuntu-offtopic
[13:12] <bazhang> kuroi being rockhopper
[13:12] <ikonia> is he known ?
[13:12] <bazhang> ie well known troll
[13:12] <bazhang> yep
[13:13] <ikonia> ahhh right
[13:15] <ikonia> bazhang: rockhopper or kurio don't appear in BT
[13:16] <bazhang> ikonia, first we've seen of him, to my knowledge; I mentioned network wide (ie seen his exploits in other channels)
[13:16] <bazhang> its kuroi btw
[13:22] <ikonia> ah
[19:02] <LjL> why does !br mention "ajuda em brasileiro", which i can only imagine is some new language, instead of "em português" like i'm sure it used to?
[19:02] <LjL> actually, i mean !pt
[19:07] <Pici> LjL: Looks like someone suggested it and we obliged.
[19:08] <LjL> well i don't think it's a good idea :|
[19:09] <Pici> What is 'brasileiro'?
[19:09] <Amaranth> Google thinks it says help in Brazil (or Brazilian) and it appears in search results as an actual phrase
[19:10] <Pici> Do we need separate !br and !pt factoids anyway?
[19:10] <Pici> !br
[19:10] <Pici> !pt
[19:11] <Amaranth> Isn't the !br one for the LoCo?
[19:12] <LjL> i can only imagine "brasileiro" is probably a colloquial term for the form of portuguese spoken in brasil
[19:12] <Amaranth> I think that would make sense with the phrase anyway
[19:12] <Pici> !pt =~ s/brasileiro/português/
[19:12] <LjL> but it's much like saying "In #ubuntu, we only use American"
[19:12] <Amaranth> LjL: Well, if #ubuntu-br is the loco channel it would make sense
[19:12] <Pici> Any objections to aliasing !br to use !pt ?
[19:12] <Amaranth> But I have no idea if that is the case
[19:13] <LjL> no
[19:13] <LjL> last i checked, -br was the general help channel
[19:13] <LjL> while -pt preferred to remain a loco channel only
[19:13] <Amaranth> Although in #ubuntu we do only use American ;)
[19:13] <Amaranth> LjL: That seems... backwards
[19:14] <Pici> oops, wrong channel, but whatever.
[19:14] <Pici> !br
[19:14] <Pici> oh dear
[19:14] <Amaranth> Neat, broken UTF-8
[19:14] <Amaranth> Does sed support utf-8? Or anything outside ascii?
[19:14] <Pici> no br is <reply> Por favor, use #ubuntu-br para ajuda em português. Para entrar no canal por favor faça "/join #ubuntu-br" sem as aspas. Para a comunidade local portuguêsa, use #ubuntu-pt. Obrigado.
[19:14] <Pici> !no br is <reply> Por favor, use #ubuntu-br para ajuda em português. Para entrar no canal por favor faça "/join #ubuntu-br" sem as aspas. Para a comunidade local portuguêsa, use #ubuntu-pt. Obrigado.
[19:14] <Pici> !br
[19:15] <Amaranth> There we go
[19:15] <Pici> argh
[19:15] <Pici> wrong one
[19:15] <Pici> !no pt is <reply> Por favor, use #ubuntu-br para ajuda em português. Para entrar no canal por favor faça "/join #ubuntu-br" sem as aspas. Para a comunidade local portuguêsa, use #ubuntu-pt. Obrigado.
[19:15] <Pici> !no br is <alias> pt
[19:15] <Pici> Thats better.
[20:09] <Flannel> Pici: br is for the LoCo, pt is for the language
[20:11] <IdleOne> I think the people in pt would disagree
[20:11] <Pici> Flannel: Thats not what the factoid has says.
[20:11] <Pici> er, said.
[20:11] <Pici> "Para a comunidade local portuguêsa, use #ubuntu-pt. Obrigado."
[20:11] <Flannel> It might have been changed, I don't know.  But at one point, that's what the division was.
[20:11] <IdleOne> they are having issues in -pt getting channel management access from the br loco leader
[20:11] <Flannel> Would probably be prudent to check with the channels
[20:12] <IdleOne> unless they resolved that this past week or so
[20:12] <Pici> The factoid was changed to say 'brasileiro' is late August.~
[20:22] <LjL> uhmm i guess they've had issues
[20:22] <LjL> because now, the -br topic says "technical support channel in Brazilian Portuguese"
[20:22] <LjL> while -pt doesn't mention technical support, it just tells you to head to -br for the "pt_BR community"
[20:23] <LjL> in other words, there are idiots in charge again
[20:23] <Flannel> sounds like there's some miscommunication or confusion in that relationship
[20:23] <LjL> welcome to -es^2
[20:23] <LjL> i think at least whoever submitted the factoid change should be LARTed.
[20:24] <LjL> "em brasilero", meh
[20:24] <LjL> i'll leave before i say further inappropriate things
[20:25] <IdleOne> who was that masked LjL!
[20:45] <Pici> IdleOne: What was he pm-ing you about?
[20:45] <IdleOne> not sure yet
[20:45] <IdleOne> all he said was hi
[20:46] <IdleOne> probably something about spoofing ops, which I told him never to do again or I would ban until the day I die and then have my kids enforce the ban after that
[20:46] <Pici> He keeps asking for support from me in PM.  The other day he was asking about something that I didn't know anything about and kept rehrasing the question slightly differently.
[20:47] <IdleOne> He hasn't done that with me, yet
[20:47] <IdleOne> heh you jinxed me dude
[20:48] <IdleOne> support question about mirrors in .in
[20:50] <Pici> That guy didn't even say anything.
[20:51] <IdleOne> the guy who /ignored #ubuntu?
[20:51] <Pici> Yeah.
[20:51] <IdleOne> self bans are awesome
[20:51] <IdleOne> be happy he left without being pushed
 Are there problems from users from India on IRC ?
 including me..
 except for your client joining #ubuntu-ops all the time. none that I know of
[20:52] <Pici> heh.
[20:52] <IdleOne> :)
[20:54] <IdleOne> I so want to buy a motorcycle :/
[20:54] <IdleOne> unrelated to anything in this channel but I still want one
[20:58] <guntbert> please have a look at deryl in #ubuntu - talks a lot off topic stuff and when asked to keep to the topic he becomes insulting
[20:59] <IdleOne> will keep an eye open guntbert, thanks
[21:00] <guntbert> thx
[21:00] <Pici> qwert says that he got his client fixed.
[21:00] <Pici> So he shouldn't be accidentally auto-joining here.
[21:01] <Pici> And I'm out for a bit.  Later.
[21:04] <IdleOne> Have a good one
[23:04] <jrib> leaving but windowshasyou in #ubuntu had an interesting first comment


[12:32] <rectec794613> do you guys help out kde users or is there a special channel for that?
[12:33] <Pici> rectec794613: technically the support channels are #ubuntu and #kubuntu, #ubuntuforums is sadly a lot quieter than those channels.
[12:33] <rectec794613> aw
[12:33] <rectec794613> ok thanks i'll be on kubuntu


[00:04] <Seeker`> Doesn't have quite the same ring as "stanley kubrick"
[00:06] <genii> I like how the freenode boxes are all after sci-fi writers actually.
[00:41] <genii> Hockey, dinner, anxious puppy chasing cats, kids. /back later.
[00:47] <LjL> i like how they're after sci-fi writers, i like a little less the fact their MOTD contains a full and detailed biography of the respective sci-fi writers
[00:48] <LjL> *especially* when i'm on pay-by-the-byte GSM connections
[00:49] <Seeker`> LjL: nice
[00:49] <Seeker`> can't you turn MoTD off?
[00:50] <LjL> nope
[00:53] <Seeker`> :(
[01:03] <ThomasHC> Hello
[01:12] <bazhang> ThomasHC, how may we help you
[01:12] <ThomasHC> Yes I was here earlier
[01:12] <ThomasHC> I talked to ikonia I believe
[01:12] <ThomasHC> He told me to come back an hour later to look for Pici
[01:31] <bazhang> ThomasHC, any reason to have 2 nicks joining here?
[01:32] <ThomasHC1> My net conenction died bazhang
[01:32] <ThomasHC1> The other one hasn't pinged out yet
[01:33] <bazhang> ThomasHC1, pici does not seem to be around; I will give you some docs to read first
[01:33] <bazhang> !coc | ThomasHC1
[01:33] <ThomasHC1> Ok, sure
[01:33] <bazhang> !guidelines | ThomasHC1
[01:33] <ThomasHC1> Will do.
[01:45] <Pici> oh well.
[01:45] <bazhang> he's still here.
[01:46] <ThomasHC1> I'm here
[01:46] <Pici> Oh, hello there.
[01:46] <ThomasHC> Hello Pici
[01:46] <ThomasHC> Sorry, net cut out a while ago and it refused to ping out
[01:46] <Pici> Do you undertand why we forwarded you here?
[01:46] <ThomasHC> Yes I do.
[01:47] <ThomasHC> ikonia has explained why and such and bazhang has linked me to the ircguidelines and code of conduct
[01:49] <Pici> ThomasHC: And do you understand them?
[01:49] <ThomasHC> Yes, I do.
[01:50] <Pici> ThomasHC: I'm going to go ahead and remove the ban, please take our guidelines into concideration when you're in our channels.
[01:50] <ThomasHC> Yes, I will thanks, funny when I use Xchat on Windows I get banned :D. back to irssi on linux? ;)
[01:51] <ThomasHC> Thank you, Pici see you later.
[01:51] <bazhang> not auspicious
[03:27] <genii> "I was reading something about CLI how do I install this as my desktop?" ... or so.... bleh
[03:37] <tonyyarusso> haha
[03:51] <Flannel> genii: sudo apt-get install placebo && sudo chvt 1
[03:52]  * Flannel wonders if he can convince people to modify apt-get to give dummy data on any package name ending in -placebo
[03:59] <genii> Flannel: I'll need to remember that one for later
[04:04] <genii> Please someone. lina69 in #u
[04:06] <genii> (my spanish is provided by babelfish....)
[04:26] <tonyyarusso> genii: that's what !es is for ;)
[04:27] <genii> tonyyarusso: They were already bombarded with !es a few times and continued with the "holaaaa!" stuff....
[04:27] <tonyyarusso> genii: that's what banforwards are for ;)
[04:28]  * genii makes a note to ask an #u op for that next time
[04:39] <tritium> genii: you're not one?
[04:40] <genii> tritium: #kubuntu only as far as I know
[04:40]  * tritium is surprised
[04:40] <genii> Although I hang out in #kubuntu #ubuntu #xubuntu etc etc
[04:41] <tritium> Yeah, which is why I thought you were an op in #.
[04:41] <tritium> in #ubuntu, rather
[04:41] <genii> tritium: I'll sometimes give the usual help or so as other ops do in #u but just usually call !ops or so when crap hits the fan, etc
[04:42] <tritium> :)
[04:42] <tritium> genii: mneptok arrived here today
[04:44] <genii> tritium: mneptok is who gives ops their channels?
[04:45] <genii> Or maybe he's just visiting you, I dunno :)
[04:46] <tritium> genii: he's not just visiting.  He moved here.
[04:46] <genii> So you're palling around, etc?
[04:47]  * genii hides the beer
[04:49] <elky> genii, in my experience, if they are doing 'holaaaaaaaaaa' instead of 'hola' then they have no intention of noting !es ;)
[04:49] <genii> elky: Noted :)
[04:51] <elky> it's basically the equivilent of 'wazzuuuuuuuuuuuup'
[04:52] <genii> Hehe
[04:52] <tritium> genii: he just arrived tonight
[04:53] <tritium> elky: who?
[04:54] <elky> tritium, who what? i was discussing troll classification with genii.
[04:54] <elky> tritium, say hi to mneptok and woo for me
[04:55] <genii> tritium: Earlier in #u a spanish speaker ignoring repeated !es   and so on
[04:55] <tritium> elky: oh, I thought you meant mneptok and I (Spanish-speaking is common here ;) )
[04:55] <tritium> elky: I will give them your regards
 i will have her  <-- -ot
[05:47] <tritium> Gah, I can't open files on my ntfs partition.
[05:48] <tritium> MS Office files are gibberish in OpenOffice.  evince complains it can't open octet/streams when I open PDFs.
[05:48]  * jussi01 waves tiredly from the airport....
[05:49] <elky> tritium, eww
[05:49] <tritium> Hi jussi01.
[05:49] <tritium> elky: yes, preventing me from getting work done.
[05:49] <tritium> Time to reboot :(
[05:49] <jussi01> tritium: hei!
[05:53] <jussi01> ok, time to go get on the plane...
[05:54] <tritium> Have a good flight.
[05:55] <jussi01> thanks...
[05:58] <genii> /msg chanserv access #kubuntu-offtopic list
[05:58] <genii> bah
[05:58]  * genii hides in disgrace
[06:02] <tritium> Gah, as much as I hate to reboot, I need 1) working sound, and 2) access to my files on NTFS.
[06:02] <tritium> Good night.
[06:02] <bazhang> night
[06:02] <genii> tritium: Good night
[06:07] <elky> bazhang, you need to stop being so triggerhappy.
[06:07] <bazhang> elky, excuse me?
[06:07] <elky> bazhang, he was letting people know about a job opening.
[06:08] <bazhang> elky, that channel needs to be better monitored. has done so for a long time.
[06:08] <elky> suggesting a job opening is NOT trolling politics.
[06:08] <bazhang> if you are referring to a single instance with lenin_cat, then perhaps, but he has a long history of trolling politics
[06:09] <elky> bazhang, and if he had continued, *then* would have been the time to stop him
[06:09] <elky> bazhang, and i do hang in #wikipedia, i know exactly what he's like.
[06:09] <bazhang> elky, that is a single instance, and as I said, you may be correct. nothing to do with the state that channel has fallen into, and remains however.
[06:10] <elky> bazhang, lauding over every whiff of the o4o areas is not going to help at all.
[06:11] <bazhang> elky, pretending that things are alright in there wont do it either, which has been sop for a long while now.
[06:11] <elky> i am not pretending things are alright.
[06:11] <bazhang> a year or more.
[06:12] <elky> i have never pretended things are alright in that channel. but i am not going to start lynching on sight.
[06:13] <bazhang> not the issue.
[06:14] <bazhang> this has been mentioned many many times in the past, and just glossed over. that channel needs to be better monitored.
[06:14] <elky> bazhang, you are not the answer to that channel.
[06:15] <elky> bazhang, lynching people is not the answer to that channel.
[06:15] <bazhang> elky, no single person is, yourself included.
[06:15] <elky> bazhang, i never said i was. i am saying you're not.
[06:16] <bazhang> and taking a single instance of !politics to a person with a long history of trolling just that very thing is very selective representation of 'lynching'
[06:16] <bazhang> see the long thread with traveler and ubuntu before that.
[06:17] <elky> bazhang, and what would you have done if you were op?
[06:18] <bazhang> elky, it seems odd to me that if loco channels are trolling misogynistic/stalkerish then immediate action is taken, but when under the very auspices of the main channel adjunct, #ubuntu-offtopic, nothing substantive is done for a very long time. and remains unresolved to this date.
[06:19] <elky> bazhang, that is not what i asked.
[06:19] <bazhang> long threads of she is sooo hawt and the like
[06:19] <bazhang> elky, with regards to traveler and ubuntu? nothing differently.
[06:20] <elky> then why the heck bring it up?
[06:25] <bazhang> elky, I will refrain from commenting on that channel in future. thanks for the clarification.
[06:28] <elky> bazhang, dont be a brat. throughout the traveler discussion all i can see is you complaining about lol and enter. there's nothing there that's going to improve their behaviour at all. if you could guide by offering alternatives rather than just pouncing with canned responses, then they might.
[06:31] <elky> responding in a manner that encompasses their whole behaviour is more likely to get response. if you had said to lenin_cat 'i hope this isn't going to be another of your political rants' rather than 'dont troll politics' then you would have got a far better response.
[06:39] <genii> I tend to agree that the approach to someone makes all the difference.
[06:40] <Flannel> This just in!  Geeks discover social skills! Film at 11. :)
[06:42] <elky> fwiw, i contacted traveler in PM to avoid having snuxoll attack me in the channel again.
[06:43]  * genii tivos the 11pm news special to watch later
[06:43] <elky> however this now means one less set of eyes on that channel
[06:57] <elky> is nobody else watching #u :-/
[07:12] <Flannel> I'm around.  Coding.
[07:13] <elky> im around. still in my nightwear. it's 4pm.
[08:10] <genii> Hehe I like that the one fellow in #u thanked the bot
[08:11] <genii> The bot should reply with something like: You're welcome... enjoy Ubuntu!                       or such
[08:11] <genii> Just a thought, anyhow
[08:14] <elky> many problems arise when peeps think the bot is a people.
[08:16] <genii> Ah, hadn't considered. I suppose they may want to converse with it or so, using resources
[08:17] <elky> and spamming here, usually
[09:22] <ikonia> morning
[09:33] <elky> ikonia, you missed fireworks again
[09:33] <ikonia> oh really
[09:34]  * elky points upwards
[09:34] <ikonia> got about 2 minutes logging at the moment as I reset my client,irssi is being a pain
[09:35] <ikonia> elky: una momento
[09:37] <elky> ikonia, http://irclogs.ubuntu.com/2009/05/02/%23ubuntu-ops.html look for 'triggerhappy'
[09:53] <elky> ikonia, did you read the log?
[10:03] <ikonia> reading
[10:05]  * jussi01 prods ikonia
[10:06]  * ikonia prods back
[10:06] <jussi01> genii:
[10:06] <jussi01> ubottu: thanks
[10:06] <jussi01> ikonia: you are not in a phonable time?
[10:07]  * genii jars awake for a second
[10:07] <ikonia> jussi01: yup, just sat at home tidying up/doing odd jobs etc
[10:07] <ikonia> getting read to go up to London
[10:07] <genii> 5AM ... bleh
[10:07] <bazhang> hehe
[10:07] <jussi01> ikonia: can I call?
[10:08] <ikonia> sure
[10:08] <jussi01> ikonia: is your phone on silent...?
[10:09] <ikonia> oh yes, I went to bed late last night so put it on silent
[10:09] <ikonia> hang on
[10:09] <evilGary> ikonia: come to Colchester?  we are having a LUG meet today
[10:10] <ikonia> evilGary: sorry in a studio in London
[10:10] <ikonia> jussi01: phone got
[10:10] <ikonia> is was on silent sorry
[10:29] <jussi01> ikonia: prod.
[10:32] <genii> OK, I'm off and /away for sleep. <brews a fresh pot of coffee and goes>
[10:32] <bazhang> night
[10:32] <elky> goes off for sleep... and brews more coffee on the way?
[10:34] <jussi01> elky: of course - the coffee is for us...
[10:35] <elky> ah
[10:36] <evilGary> ooo, I want coffee
[10:37] <jussi01> evilGary: come meet me in Liverpool and Ill buy you one :D
[10:37]  * elky has an espresso machine
[10:38] <elky> espresso machines are stupidly cheap. only like $100. it's stupid.
[10:40] <jussi01> elky: shush now
[11:02] <bazhang> heh
[11:27] <topyli> @login
[11:27] <topyli> @btlogin
[11:28] <topyli> @mark Jymm_is_a_douche is yaris1234567891
[13:07] <elky> bolt_, you need to stop being a problem, or you will find yourself banned from many more places. do you realise this?
[13:07] <bolt_> yes
[13:08] <elky> then why do you keep on doing it?
[13:08] <bolt_> i don't relise i'm doing it
[13:08] <elky> yes you do.
[13:09] <bolt_> untill now
[13:09] <elky> if you do not, then you should not be using the internet unsupervised.
[13:09] <elky> bolt_, have you been drinking alcohol or taking drugs at all?
[13:10] <bolt_> just melitoium at night nothing else and fish oil
[13:10] <elky> then you should be perfectly capable of controlling your own behaviour.
[13:11] <bolt_> yeah , and i have autisoum
[13:12] <elky> if that is influencing your behaviour on the internet, then you need to have supervision while you're online.
[13:13] <bolt_> i just get impashint
[13:13] <elky> that's not a valid excuse for bad behaviour.
[13:14] <bolt_> oh right
[13:16] <elky> bolt_, also, the reason you were banned from here is that you were threatening people in here.
[13:16] <bolt_> i guessed that
[13:16] <elky> then you are aware of what you do.
[13:17] <elky> you are aware of what is right and what is wrong.
[13:17] <bolt_> somtimes i can control it
[13:18] <bolt_> yeah
[13:18] <elky> i dont think it's a matter of 'can', i think it's a matter of 'find it convenient to'
[13:18] <bolt_> oh ok
[13:20] <bolt_> right
[13:21] <elky> you can go now. you are not unbanned from #ubuntu and you will not be until you can behave appropriately.
[13:21] <elky> you should not use #ubuntu-offtopic for support either.
[13:22] <elky> please investigate ubuntuforums.org instead.
[13:22] <bolt_> but i can behave
[13:22] <elky> not that i've seen.
[13:23] <elky> you are currently talking absolute rubbish in #ubuntu-offtopic.
[13:24] <bolt_> i'm trying to get help
[13:24] <nickspoon> #ubuntu-offtopic is not a support channel, bolt_.
[13:25] <bolt_> but i cant use #ubuntu or #kubuntu thats the ony other one i know
[13:26] <elky> bolt_, you can use ubuntuforums.org.
[13:26] <elky> or the mailing lists at lists.ubuntu.com
[13:26] <bolt_> i don't like it has the wong info that just makes the issue worse
[13:27] <elky> those are your options, since you have deprived yourself of #ubuntu and #kubuntu.
[13:29] <bolt_> non work
[13:29] <elky> !guidelines
[13:30] <bolt_> i know them already
[13:30] <elky> then you really have no excuse.
[13:30] <bolt_> for what
[13:31] <elky> for your behaviour.
[13:31] <bolt_> right
[13:34] <bolt_> but its stopped now (if yu havent notaced)
[13:35] <elky> no, you're still asking for support in the non-support channel.
[13:35] <elky> despite several people asking you to stop.
[13:36] <bolt_> oh i haven relised
[13:36] <bolt_> better now
[13:37] <bolt_> and it stopped by magic
[13:38] <elky> then you dont need to be here anymore. we'll review your bans in a week if we see no more problems from you.
[13:39] <bolt_> great now a week , i cant wait anylonger then 1 day
[13:41] <bolt_> oh great not another issue
[13:59] <elky> ducking out for a few minutes
[14:26] <elky> interesting nick...
[15:52] <elky> topyli, are you around enough to monitor -ot?
[15:56] <topyli> elky: on and off. sauna, grill, other stuff
[15:58]  * elky whimpers. i need to go to bed. got a committee meeting tomorrow. cant sleep all day :(
[15:58] <topyli> go to bed :)
[15:58] <elky> but -ot is full of tards today
[15:59] <bazhang> heh
[16:12] <bazhang> * [chowabunga] (n=chowabun@c-98-192-66-27.hsd1.ga.comcast.net): chowabunga <--wonder if he is archlinux troll
[16:13] <LjL> bazhang: possible, but relatively unlikely
[16:14] <bazhang> LjL, okay, he is giving some bad advice/snark though. may also have me on /ignore
[16:21] <bazhang> seems to have settled down with the random comments now
[16:25] <bazhang> or maybe not :(
[16:58] <LjL> !info conky
[16:58] <ubot4`> LjL: conky (source: conky): highly configurable system monitor for X based on torsmo. In component universe, is optional. Version 1.6.1-0ubuntu4 (jaunty), package size 191 kB, installed size 560 kB
[18:21] <Seeker`> @mark #ubuntu master being abusive
[18:21] <Seeker`> @login
[18:21] <Seeker`> @mark #ubuntu master being abusive
[19:28] <ikonia> can someone copy the ban from #ubuntu/#kubuntu and put it on #ubuntu-offtopic for bolt_ please he's doing that "I speak dog" and "I'm a robot" rubbish again - I've made it %101 clear that is not acceptable
[19:29] <Pici> ikonia: I don't see him in there.
[19:30] <ikonia> he's not any more
[19:30] <Pricey> 3~floodbot not removing bans again? :/
[19:30] <ikonia> I see no reason to allow this to continue in a loop - end it until he learns
[19:30] <ikonia> while there are other channels to do this in, his behaviour loop continues
[19:31] <Pricey> I think we really need to remove some of these bans still.
[19:32] <ikonia> Pricey: which ones ?
[19:32] <ikonia> I did some of floodbots yesterday
[19:32] <Pricey> the exempts look old
[19:32] <Pricey> but there's a huge amount of bans in there too
[19:33] <ikonia> I can go through the floodbots bans if you want and clean up
[19:33] <Pricey> I'm sure we wouldn't miss many of the +d either
[19:33] <Pricey> s/either/too/
[19:34] <LjL> the floodbots never removed actual *bans* they did
[19:35] <Pricey> bah, i meant floodbot exempts sorry
[19:35] <Pricey> and the other bans in general, whether or not they were from the floodbots, didn't look at them too hard
[19:36] <ikonia> I'll do some house keeping,
[19:41] <Pici> LjL: I removed the bans that they set about a week ago, there were quite a lot in there
[20:43] <LjL> Pici: there are quite a few that were set in march too
[21:00] <rdove> can you test me for the DCC bug
[21:01] <LjL> yeah
[21:01] <LjL> vulnerable
[21:02] <LjL> rdove: you are vulnerable
[21:02] <rdove> damn
[21:02] <rdove> lol
[21:02] <rdove> i failed the test?
[21:02] <LjL> rdove: i've marked you as such in #ubuntu-read-topic, so you will be able to ask the bots for other tests
[21:02] <rdove> ok
[21:03] <rdove> brb
[21:08]  * LjL shakes head at IRC wiki page
[21:08] <LjL> people just can't leave it alone
[21:08] <Seeker`> what have they done now?
[21:08] <LjL> Seeker`: nothing too terrible, just +  * '''[[http://www.emacswiki.org/emacs/?action=browse;oldid=EmacsIrcClient;id=ERC|ERC]]''' - an IRC client for the [[http://www.gnu.org/software/emacs/|Emacs]] editor.
[21:09] <LjL> just after i removed the Mac OS client. of course, this is a Unix client for sure, no doubt *roll eyes*


 :-P
[12:51] <daftykins> ah the new TV arrived at last, just put in my new receiver and am enjoying the fun of underspec HDMI cables :)
[12:51] <daftykins> got my desktop PC connected and a game running at 4K on the go
[12:52] <m0nkey_> heh, yeah. probably only get 3 WPM
[12:52] <zmoylan-pi> give me a w! *pew* *pew* *pew*
[12:53] <diddledan> on the plus side, those tai fighters don't stand a chance
[12:53] <zmoylan-pi> pity you work for the empire...
[12:58] <daftykins> OLED vs LCD https://i.imgur.com/1iSqR6X.jpg
[12:58] <diddledan> the one om the left
[12:58] <daftykins> is what :P
[12:58] <diddledan> is better
[12:58] <daftykins> yus!
[12:59] <daftykins> amazing black level + no ugly backlight bleed
[12:59] <diddledan> I'm guessing that's the oled?
[12:59] <daftykins> yip, they're the same size but there's a crazy optical illusion from having the old Samsung closer, on the wooden unit
[13:00] <diddledan> hah
[13:01] <diddledan> I think the optical effect is heightened by the way they're slightly angled in opposing directions, too
[13:03] <daftykins> mmm
[13:03] <daftykins> the OLED is 5mm thick on the panel XD
[13:03] <daftykins> https://i.imgur.com/C3k4ByA.jpg
[13:03] <daftykins> cheese cutting++
[13:04] <diddledan> wow, that's skinny
[13:04] <diddledan> and here I was thinking LED backlighting made for thin panels
[13:08] <foobarryz> trying to install retropie on ubuntu...seems to be compiling from scratch :(
[13:09] <daftykins> o0
[13:09] <foobarryz> probably a bit late to check if there's a package now
[13:09] <daftykins> naaah :P
[13:09] <foobarryz> seems to be a retroarch one
[13:16] <diddledan> bitcoin regulation: http://www.techradar.com/news/uk-government-is-cracking-down-on-criminal-usage-of-bitcoin
[13:24] <zmoylan-pi> it's interfering in trade in diamonds? :-P
[13:25] <diddledan> apple's security patch emails are terrible. EVERYTHING takes the form of: "A <insert feature> issue was addressed with improved <insert feature> handling"
[13:26] <diddledan> e.g. "Description: Multiple memory corruption issues were addressed through improved state management." and "Description: A memory corruption issue was addressed with improved memory handling."
[13:26] <zmoylan-pi> well update notices are awful in general.  there's an update for file manager on my alcatel phone, makes no mention of adding adverts to the app that take up 1/3 of the screen...
[13:27] <diddledan> "Description: A validation issue was addressed with improved input sanitization."
[13:28] <foobarryz> the scrolling on this touchpad stops scrolling as soon as you let go. its a bit odd
[13:28] <foobarryz> shouldn't it carry on when you swipe?
[13:28] <zmoylan-pi> no
[13:28] <foobarryz> on firefox
[13:29] <foobarryz> pretty sure it doesn't feel right
[13:29] <foobarryz> its very abrupt
[13:29] <zmoylan-pi> and in other apps other than firefox?
[13:31] <foobarryz> chromium and terminal too
[13:32] <zmoylan-pi> so, os related more than firefox
[13:32] <foobarryz> same issue. can't think of the words to tell google about it
[13:32] <zmoylan-pi> distro, version?
[13:32] <zmoylan-pi> scroll abruptness lag
[13:34] <foobarryz> mate 17.10
[13:34] <diddledan> "sudden catastrophic loss of linear motion"
[13:35] <diddledan> that'll definitely find relevant pages
[13:35]  * diddledan nods
[13:41] <foobarryz> scrolling inertia libinput
[13:44] <foobarryz> https://bugzilla.redhat.com/show_bug.cgi?id=1225643
[13:46] <foobarryz> well that sucks
[13:46] <foobarryz> its very hard work to get to the bottom of the page
[13:48] <zmoylan-pi> isn't that why the end button was created?
[13:48] <daftykins> got the tickboxes for smooth and autoscrolling on?
[13:52] <diddledan> another "any user can get root" issue in macos: https://m4.rkw.io/blog/macos-high-sierra-10131-insecure-cron-system.html
[13:54] <daftykins> nice
[13:54] <zmoylan-pi> they're just trying to be (ab)user friendly
[13:54] <diddledan> I'm friendly with my abuser, too
[13:54] <diddledan> he's a cool guy except when he's flogging me
[13:54] <daftykins> now get back to work :D
[13:54] <zmoylan-pi> does he charge extra for that
[13:57] <diddledan> he doesn't, no. he just likes to do it for fun
[14:00] <zmoylan-pi> always nice to see people who like their job
[14:07] <diddledan> https://usercontent.irccloud-cdn.com/file/LMlcaeI2/578170_10151910725639262_1611158090_n.jpg
[17:36] <L0ki> Hello All, quick question, was getting taught about the MV command today to rename files...the example given was one file named 'motorhead' which had a sentence specific to itself. Another file named 'ramones', again containing text specific to it. the teacher then used the MV command from motorhead to Ramones, thus changing the name (to only motorhead) but also over writing the text contained in Ramones to that contained in motorhead, I thought in this ca
[17:36] <L0ki> the teacher thought I was wrong and that for renaming you would only use MV?
[17:39] <daftykins> :|
[18:04] <Seeker`> riiiiiiiiiiight
[18:05] <daftykins> gotta love the insta-quitters
[18:12] <diddledan> gotta love IRC clients that don't respect the IRCd's capabilities statement
[18:12] <diddledan> i.e. "I thought in this ca".... huh?
[18:14] <daftykins> mmm
[18:14] <daftykins> think i only upgraded to an irssi that could handle and split that recently
[19:36] <zmoylan-pi> dagnabit, this is irc and we're supposed to have sentences that cut out just when it comes to the interesting pa
[19:42] <daftykins> rtridge in a pear tree
[19:42] <daftykins> sorry, bit of crosstalk


[01:48] <capyre> hi
[01:48] <Guest98123> hi
[01:49] <capyre> alguien que hable espñaol
[01:49] <capyre> =D
[04:16] <mate|68656> Ubuntu Mate 17.10 No Wired internet after Suspend: I recently got a different modem and these past two days my internet's not working after I suspend but it does turn back on after I restart computer.
[04:16] <mate|68656> *-network
[04:16] <mate|68656> description: Ethernet interface
[04:16] <mate|68656> product: 88E8071 PCI-E Gigabit Ethernet Controller
[04:16] <mate|68656> vendor: Marvell Technology Group Ltd.
[04:17] <mate|528> Ubuntu Mate 17.10 No Wired internet after Suspend
[04:17] <mate|528> I recently got a different modem and these past two days my internet's not working after I suspend but it does turn back on after I restart computer.
[04:17] <mate|528> I'm now using an Arris TM822r.  If you need me to do something else for more info please let me know.
[04:22] <kernal> I feel your pain mate|528
[04:22] <kernal> I hate network problems
[04:22] <mate|528> yeah it sucks
[04:22] <mate|528> never had a problem before upgrading modem
[04:23] <mate|528> Also I do have a support ticket open here with more info about the network if anyone could stop by and help it would be greatly appreciated. https://ubuntu-mate.community/t/ubuntu-mate-17-10-no-wired-internet-after-suspend/15959
[04:24] <kernal> modem shouldn't really your computer having a network connection after sleeping?
[04:25] <kernal> really affect*
[04:25] <mate|528> yup after waking up from sleep it kicks me from internet on browser and computer
[04:25] <mate|528> until I restart
[04:25] <mate|528> my modem still shows everything is online though
[04:28] <kernal> does the same thing happen with 16.04?
[04:29] <mate|528> Well I never upgraded the modem with 16.04 so idk
[04:30] <kernal> grab an iso, launch up a live session and see what happens after it goes to sleep?
[04:32] <mate|528> Well I had 16.04 before and everything ran fine when it went to sleep it's just after upgrading modem in 17.10 that it started doing this and really only like a week after running the modem
[04:32] <mate|528> Maybe it needs some different driver now that the modem is different idk
[08:21] <CrazyTux> I want to remove all the traces of KDE Plasma that I have installed on Ubuntu Mate. I am encountering some problems with it.  Je n'ai plus accès à Windows 10...merci de vos conseils;=)
[19:05] <marlin_noir> Bonsoir Darkhero. Disponible?
[19:06] <alkisg> !fr
[19:07] <Darkhero> Sorry, I can only answer in english
[19:09] <vkareh> sounds like he installed Ubuntu and now can't get to Windows 10... what's the shortcut to show the Grub menu during POST?
[19:12] <marlin_noir> Bonsoir...J'ai cliquer un peu vite en installant UBUNTU. Résultat: plus d'accès à win 10 !!!Un coup de main SVP ;=)
[19:13] <diogenes_> !fr | marlin_noir
[19:15] <marlin_noir> OK Merci
[19:16] <vkareh>  marlin_noir: Reboot -> Hold [Shift] -> Select Windows
[19:55] <andrew> I have a brightness control issue on my Lenovo Thinkpad T430i running Ubuntu Mate 16.04.03 LTS. The brightness control is very jumpy, and not accurate whatsoever, sometimes increasing the brightness will make the bar go backwards, and vice versa.
[20:38] <ghost_> how can i clear space in /boot?
[20:40] <diogenes_> ghost_, by removing the old kernels
[20:42] <ghost_> diogenes, could you explain how to do that please?
[20:42] <ghost_> sorry im new to the raspberry pi
[20:45] <diogenes_> ghost_, run in terminal: df -h | nc termbin.com 9999
[20:45] <diogenes_> share the link here
[20:50] <ghost_> diogenes, http://termbin.com/446q
[20:52] <diogenes_> ghost_, 63 MB for /boot?
[20:52] <diogenes_> who taught you to do so?
[20:55] <diogenes_> you can't even fit two kernels in there
[20:55] <ghost_> when i instaled the os thats what it was resized to
[20:55] <diogenes_> by default?
[20:55] <diogenes_> what option did you pick
[20:56] <ghost_> yes by default. and it just asked if i wanted to resize the boot section and i clicked yes
[20:57] <diogenes_> ghost_, do you have any important files on this machine?
[20:57] <ghost_> no, not at the moment.
[20:58] <diogenes_> then I'd recommend you to go ahead reinstall the system, but this time, make only two partitions, two
[20:59] <diogenes_> first partition is / ext4 at least 20 GB
[20:59] <diogenes_> second partition /home ext4 the rest of the space
[20:59] <diogenes_> if you have an EFI system then create a 300 MB /boot/efi partition
[21:00] <diogenes_> and nothing else
[21:00] <diogenes_> no /boot partitions, not even a /swap partition because we can create a swap file afterwards
[21:01] <ghost_> ok, I will go ahead and do that. Thanks
[21:01] <diogenes_> choose "something else" when you reach partitioning
[21:02] <diogenes_> and you're good to go
[21:03] <ghost_> so just those first two partitions and not the /boot or /swap
[21:04] <ghost_> ok, i got it
[21:04] <diogenes_> BUT
[21:04] <diogenes_> if you have a EFI system, then of course you must create a third partition called /boot/efi
[21:04] <diogenes_> otherwise your system won't boot
[21:07] <ghost_> Right, Thanks diogenes
[21:07] <diogenes_> you're welcome
[22:30] <betotho> hi
[22:39] <kaption> back again