[01:15] <ahoneybun> hey Riddell
[06:36] <soee> good morning
[07:42] <shadeslayer_> Riddell: ping
[07:48] <shadeslayer_> Riddell: My ec2 skills are completely gone :S .... can't login to an instance that I provisioned
[08:14] <soee> any idea why i can't install apport-kde upgrade ?
[08:16] <markey> yofel: ok, I think we can greenlight the Qt package. I've been using Amarok constantly yesterday and today, and it hasn't crashed once
[08:16] <markey> very nice
[08:20] <yofel> markey: thanks! I'll try to get the SRU paperwork done this week then
[08:21] <markey> :)
[08:41] <shadeslayer_> yofel: did you upload 4.10.4 for raring?
[08:41] <shadeslayer_> status page is missing half the packages
[08:41] <yofel> shadeslayer_: yeah, can you update the symbols for kdelibs? I think that's all thats left
[08:41] <yofel> shadeslayer_: well, yeah, --sru does that
[08:42] <shadeslayer_> yofel: can di
[08:42] <shadeslayer_> *can do
[08:42] <yofel> IIRC there should be like 55 packages for raring
[08:42] <shadeslayer_> 0.o
[08:43] <yofel> ?
[08:43] <shadeslayer_> 55 packages only?
[08:43] <yofel> that's all that had changes since .3
[08:44] <shadeslayer_> oh? we the script doesn't upload all of it?
[08:44] <shadeslayer_> i.e. if nothing changed in svgpart, it won't upload svgpart?\
[08:45] <yofel> nope, in --sru mode it runs a diff check on every package, if diffstat returns nothing the package is skipped
[08:45] <yofel> what's a bit of work right now is fixing versioned build-deps later, as the script doesn't know how to skip that yet...
[08:46] <yofel> I have an idea for that, but didn't implement it yet
[08:46] <shadeslayer_> ok
[08:52] <shadeslayer_> yofel: btw regarding md5sum checking, should I just make it use rsync instead of scp? we get md5sum checking for free then
[08:53]  * yofel can't think of a reason why not do use rsync right now
[08:54] <yofel> *to use
[08:55] <shadeslayer_> k, I'll try it out
[08:55] <Tm_T> someone please remind me if I haven't mangled channel access list today
[09:03] <shadeslayer_> yofel: not sure if anyone noticed, but http://cdimage.ubuntu.com/kubuntu/releases/raring/release/kubuntu-13.04-desktop-amd64.manifest vs http://cdimage.ubuntu.com/kubuntu/releases/raring/release/kubuntu-13.04-desktop-i386.manifest , the german lang pack is missing on mad64
[09:03] <shadeslayer_> erm
[09:03] <shadeslayer_> amd64
[09:03] <shadeslayer_> or it got accidentally added to i386
[09:04] <shadeslayer_> why would that happen 0.o
[09:06] <yofel> I'm the worst possible person to ask about l10n...
[09:06] <yofel> apachelogger_: ^
[09:07] <yofel> shadeslayer_: on second thought, what to the seeds say?
[09:07] <shadeslayer_> checking
[09:07] <shadeslayer_> usually germinate uses popcon to populate that IIRC
[09:10] <shadeslayer_> hm
[09:10] <shadeslayer_> #by order of popcon (de es fr ru it pt pl ja zh nl cs sv hu el)
[09:10] <shadeslayer_>  * Languages: de es
[09:10] <shadeslayer_> and then it adds it to i386 and amd64
[09:10] <shadeslayer_> this is messed up
[09:11] <shadeslayer_> yofel: http://bazaar.launchpad.net/~kubuntu-dev/ubuntu-seeds/kubuntu.raring/view/head:/ship#L41
[09:11] <shadeslayer_> fr is only added to i386 for some reason? :P
[09:12] <yofel> amd64 was full I guess
[09:12] <shadeslayer_> :S
[09:12] <yofel> yes, we are fat ^^
[09:14] <alvin> I'm sorry for bothering you devs with this, but I'd like some direction. After sending queued mails with Kmail, my plasma-desktop crashed and I can't start it again. I removed plasma-desktoprc and plasma-appletrc, but it still doesn't start. The command 'plasma-desktop' lets the screen flicker and then shows the KDE Crash Handler. I'm now using Krunner to start applications
[09:15] <alvin> I thought it was the Telepathy applet (org.kde.ktp-presence that caused this, because yesterday, adding that crashed plasma-desktop). After todays upgrades, that worked, but now I'm nog so sure.
[09:17] <shadeslayer_> yofel: did someone upload oxygen-icon and kajongg?
[09:17] <shadeslayer_> because those 2 needed to be manually uploaded
[09:18] <yofel> not that I know of
[09:18] <yofel> what's wrong with kajongg?
[09:18] <shadeslayer_> I didn't check
[09:18] <shadeslayer_> but the script skipped those
[09:21] <shadeslayer_> alvin: does this also happen on a guest account?
[09:23] <shadeslayer_> yofel: kde4libs for raring uploaded
[09:23]  * shadeslayer_ looks at oxygen-gtk3
[09:26] <alvin> shadeslayer_: I disabled that. I can try, but I guess not. What I did now was erasing all plasma* and activity* files in ~/.kde/share/config. Then I had to reboot. Just restarting lightdm didn't get me past the KDE Crash Handler. Now, I have the plasma-desktop, but I saw a few crash handlers on logging in. I'll retry logging out now.
[09:26] <shadeslayer_> huh
[09:29] <shadeslayer_> who uses emacs here? :P
[09:30] <alvin> One crash handler remains (also on reboot). A few seconds after logging in: "Nepomuk Service Stub". I'm now installing the debug packages
[09:30] <shadeslayer_> alvin: plz pastebin the backtrace so that we can try and help
[09:31] <alvin> ok, I'll do that first
[09:32] <alvin> shadeslayer_: Is this useful? http://pastebin.kde.org/758852/
[09:33] <shadeslayer_> not really, needs soprano dbg packages
[09:33] <shadeslayer_> vHanda: ^^
[09:33] <alvin> shadeslayer_: So, I have to crash again after installation of those debug packages?
[09:33] <shadeslayer_> alvin: nope, it'll auto refresh IIRC
[09:36] <alvin> Installed libsoprano-dbg and refreshed: http://pastebin.kde.org/758870/
[09:37] <alvin> This is weird. In System Settings, I see that Nepomuk is active (file indexer, semantic desktop and email indexer), but Kmail says it isn't.
[09:42] <alvin> The good news: I think it's a known problem https://bugs.kde.org/show_bug.cgi?id=312760 The bad news: well, when do you guys plan to release KDE 4.11 ;-)
[09:43] <shadeslayer_> whenever upstream releases it :)
[09:43] <alvin> Oh, right. It's not released yet
[09:43] <shadeslayer_> yofel: quick sanity check : subprocess.check_call(["rsync", "--progress", "-z", "-e ssh", remote, "."])
[09:43] <shadeslayer_> -z is for compression
[09:45] <yofel> I'm not sure whether subprocess allows spaces in options (-e ssh), looks right otherwise
[09:45] <shadeslayer_> well ... it works
[09:45] <shadeslayer_> so seems like it does?
[09:45] <yofel> ack then
[09:45]  * shadeslayer_ tries adding --compress-level=9
[09:45]  * yofel -> lunch
[09:45] <shadeslayer_> because, compress all the things!
[10:10] <soee> yofel, this packages were stopped from updating: apport-kde kdelibs5-plugins any idea why ?
[10:14] <apachelogger_> yofel, shadeslayer_: langpacks are not added if they cause oversizing IIRC
[10:15] <shadeslayer_> oh, makes sense
[10:16] <apachelogger_> we must be seriously oversized though :P
[10:17] <apachelogger_> ...there used to be a time when at least de and fr were fitting on the *CD*
[10:19] <shadeslayer_> ScottK: oxygen-gtk3 waiting for you in -proposed
[10:19] <shadeslayer_> in -proposed queue ^_^
[10:21] <vHanda> shadeslayer_: fixed in 4.11
[10:21] <vHanda> we aren't sure why that is happening though
[10:22] <shadeslayer_> vHanda: no chance of backporting?
[10:22] <shadeslayer_> to 4.10.5
[10:24] <vHanda> no
[10:24] <vHanda> but you can apply this fix if you want - https://bugs.kde.org/show_bug.cgi?id=312760#c25
[10:24] <vHanda> this seems to fix it based on reports
[10:24] <vHanda> but we still aren't sure why it happens
[10:24] <vHanda> I've fixed it in 4.11 by not communicating over sockets
[10:27] <shadeslayer_> battery dying
[10:27] <shadeslayer_> cya later
[10:32] <jussi> so, why do sometimes messages have a grey box around them ?
[10:48] <yofel> soee: what are you updating to?
[10:49] <soee> yofel, im on Raring and saw today 4.10.3 updates
[10:50] <yofel> soee: hm, can you please pastebin what an 'aptitude full-upgrade' attempts to do?
[10:51] <soee> yofel, http://pastebin.com/u9ShT5vL
[10:57] <yofel> soee: that's weird and I can't reproduce it here... Maybe your mirror is out of date or broken?
[10:58] <yofel> bbl
[11:22] <shadeslayer_> qemu is so slow
[11:22] <shadeslayer_> so very slow
[11:22] <Darkwing> Morning
[11:22] <shadeslayer_> hi Darkwing :)
[11:32] <shadeslayer_> dafuq
[11:32] <shadeslayer_> http://wstaw.org/m/2013/06/05/plasma-desktoprw4794.png
[11:33] <ahoneybun> Darkwing: 
[11:35] <shadeslayer_> *grumble*
[11:35] <shadeslayer_> kvm is so much faster
[11:35] <shadeslayer_> qemu is complete crap :/
[11:36] <Darkwing> :)
[11:36] <Darkwing> I should use something other than openbox for my testing at some point.
[11:36] <Darkwing> rather virtualbox
[11:37] <ahoneybun> Darkwing: have you seen our progress?
[12:07] <ScottK> shadeslayer: Please reupload without the changes in debian/rules and debian/source/options.
[12:07] <shadeslayer> ack
[12:08] <ScottK> Also, you can compress debian/changelog down to the relevant bits.
[12:09] <shadeslayer> ScottK: though any reasons to do that?
[12:09] <ScottK> It's the changes relevant to the SRU, i.e. more correct.
[12:10] <ScottK> That's what gets shown in various updaters tools and it's a bit confusing as is.
[12:10] <shadeslayer> okay
[12:11] <shadeslayer> I'll just use the old 1.1.1 packaging
[12:14] <shadeslayer> ScottK: I didn't get a rejection email :(
[12:15] <BluesKaj> Hiyas all
[12:15] <ahoneybun> BluesKaj: hey
[12:15] <BluesKaj> hi ahoneybun
[12:28] <shadeslayer> xnox: do you have an idea what could be causing this : https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1187762
[12:29] <shadeslayer> mmm ... description can use better wording
[12:30] <Riddell> shadeslayer: did you work out ec2?
[12:30] <shadeslayer> nope :(
[12:31] <shadeslayer> I've completely forgot how to do it and I tried to follow the docs, but then I couldn't ssh into the machine
[12:31] <shadeslayer> pubkey denied
[12:31] <Riddell> shadeslayer: are you setting it up outside us-east again?
[12:31] <shadeslayer> nope, I was using us-east 
[12:32] <shadeslayer> Riddell: ec2-run-instances ami-5dd0ba34 -t m1.small --region us-east-1 -k key
[12:32] <ScottK> shadeslayer: Odd.  I did reject it.
[12:33] <shadeslayer> ScottK: yeah not sure, I didn't get an email regarding my kdelibs upload as well
[12:34] <Riddell> shadeslayer: then log in with ssh -i key.pem ubuntu@123.aws.com ?
[12:36] <shadeslayer> Riddell: yes
[12:36] <shadeslayer> it said pubkey denied when I tried to do that
[12:38] <shadeslayer> Riddell: maybe the key didn't get copied?
[12:39] <Riddell> shadeslayer: I have four environment variables set, I don't remember what they all do, do you have them set?
[12:39] <shadeslayer> yes, I set them prior to using ec2-run-instances
[12:40] <Riddell> shadeslayer: I'm in
[12:41] <Riddell> shadeslayer: to one I just statred
[12:41] <Riddell> shadeslayer: try ubuntu@ec2-54-224-61-127.compute-1.amazonaws.com
[12:41] <santa_> Riddell (and kubuntu people in general), ximion (since you started tanglu): any toughts on this http://paste.kde.org/759080/ ?
[12:41] <shadeslayer> *blink*
[12:41] <shadeslayer> works
[12:41] <shadeslayer> ah well
[12:41] <Riddell> shadeslayer: it took a while to let me log in
[12:41] <xnox> shadeslayer: live session acting differently from ubiquity-dm session?! subtle things are different between the two. Did you try installer inside the live session?
[12:42] <Riddell> shadeslayer: I got Connection refused for the first couple of minutes after it had started
[12:42] <shadeslayer> xnox: -dm works fine
[12:42] <shadeslayer> Riddell: ec2din said it was runnign
[12:42] <shadeslayer> *running
[12:43] <Riddell> shadeslayer: ec2-describe-instances told me it was up but it still took a bit to be able to do an ssh connection
[12:43] <xnox> shadeslayer: sure, but that's not where the bug is.
[12:44] <shadeslayer> Riddell: hmm
[12:44] <shadeslayer> ah well
[12:44] <xnox> shadeslayer: the user is reporting against live-session running installer, where theme/desktop settings/etc can be interfering.
[12:44] <xnox> shadeslayer: i asked, have you tried inside the live session -> try kubuntu and then start installer.
[12:45] <shadeslayer> xnox: yes, that's exactly where the problem occurs
[12:45] <shadeslayer> it doesn't happen in ubiquity-dm
[12:46] <xnox> so, debug live-session. theme/qt/kde settings and full kubuntu-session is started, which is fully outside of ubiquity control.
[12:46] <Riddell> santa_: gosh yet more kde package forks?
[12:46] <xnox> the bug is somewhere between the two. It might mean that ubiquity needs to adjust settings on startup, which have "compatible" values in ubiquity-dm but not in the live session.
[12:47] <shadeslayer> whaa
[12:47] <shadeslayer> Riddell: did you shut it off :P
[12:47] <ximion> santa_: well, first of all Tanglu is no replacement for anything :P And regarding shared packaging efforts, I would love that! But making it happen would be much work, the Kubuntu/Debian packaging already has some differences, mainly due to Kubuntu shipping newer KDE releases faster
[12:48] <Riddell> shadeslayer: yeah, were you needing it?
[12:48] <shadeslayer> yes :P
[12:48] <shadeslayer> okay wait
[12:48] <Riddell> shadeslayer: oh sorry :(
[12:48] <shadeslayer> Riddell: I wanted to figure out how we can use otto for Kubuntu
[12:48] <Riddell> shadeslayer: what's otto?
[12:48] <shadeslayer> https://launchpad.net/otto
[12:48] <ximion> shared packaging between Tanglu and Kubuntu might be possible, but that is up to the individual teams to decide, because it would require coordination work, and I don't know if the teams want that
[12:49] <ximion> (and I don't want to push anyone)
[12:49] <shadeslayer> Riddell: http://bazaar.launchpad.net/~otto-dev/otto/trunk/view/head:/doc/README
[12:51] <Riddell> ximion: I wouldn't want anything that adds extra hassle to kubuntu packaging but there might be some interesting possibilities to look at
[12:52] <santa_> my idea would cover only kde-related packages
[12:52] <santa_> one possible approach would be:
[12:52] <santa_> we package, let's say kde 4.10.4 for tanglu
[12:52] <santa_> then you adapt that packages for kubuntu
[12:53] <santa_> I do the same for siduction
[12:53] <santa_> and the neptune guy takes siducion packages and backports them to debian testing/stable
[12:53] <santa_> * siduction
[12:53] <Riddell> hmm, the sequential bit is a problem there, I don't want to wait around for tanglu or any other project to do it first
[12:54] <Riddell> plus most of what needs done is compiling it and checking the compilation logs and binaries which are separate for each distro
[12:54] <ximion> Riddell: regarding "sync-with-Tanglu" it pretty much depends on how different the base system of Tanglu will be from the Ubuntu base - would be worth a try. Merging with Debian is much more difficult, and I don't think it would be easily possible (Debian policy is - fortunately - applied strictly there :-) ), but maybe talking to svuorela might be nice.
[12:55] <santa_> about the sequential problem, that would be optional for each kde release
[12:55] <ximion> Riddel: the best approch would be to make the package work on all distros, if it is not too much work
[12:55] <Riddell> that shouldn't be much work no
[12:56] <ximion> Tanglu curently is Debian + systemd + fresh kernel +  a few adjustments on GRUB and the boostrap stuff
[12:56] <santa_> I think it would be nice to make it work for debian sid
[12:56] <santa_> then adapt it to each distro
[12:57] <ximion> I am not *that* familiar with the Ubuntu base anymore, because they diverged quite a lot from what I consider an ideal solution, but I think especially for KDE, using the same packages would work
[12:57] <ximion> (for GNOME not so much, since GNOME is heavily patched :-/)
[12:57] <ximion> santa_: this would slow down Kubuntu development
[12:59] <santa_> ximion: I don't think so as long as forking from customized_uptodate_packages is optional
[12:59] <ximion> Debian has different policies for KDE packaging, to make each package perfect, also in terms of debian/copyright files etc. - this makes sense because Debian releases are less frequent. Kubuntu instead has frequent releases and therefore fixing bugs which actually affect the users makes more sense than the polishing work (which also happens, but not with a *very* high priority)
[12:59] <shadeslayer> Riddell: when passing -k do you pass the path or just the name 'key'
[13:00] <Riddell> shadeslayer: the path
[13:00] <Riddell> full file name
[13:00] <shadeslayer> Riddell: Client.InvalidKeyPair.NotFound: The key pair '/home/shadeslayer/.ec2/key.pem' does not exist
[13:01] <shadeslayer> I ran : ec2-run-instances ami-5dd0ba34 -t m1.small --region us-east-1 -k ~/.ec2/key.pem
[13:01] <shadeslayer> Riddell: and EC2_KEYPAIR is the full path as well?
[13:02] <santa_> ximion: I'm following more or less the kubuntesque approach in siduction (i.e. not caring about copyright files and so on and package fast)
[13:02] <Riddell> shadeslayer: no I have EC2_KEYPAIR=key
[13:02] <santa_> in fact we have kde sc 4.10.4
[13:02] <Riddell> shadeslayer: ec2-run-instances ami-5dd0ba34 -t m1.small --region us-east-1 -k key   <-- no full path
[13:02] <shadeslayer> okay, let me try again
[13:02] <santa_> the thing is: I have some kde 4.10.4 packages compatible with debian sid
[13:02] <Riddell> shadeslayer: ssh -i key.pem ubuntu@ec2-54-224-61-127.compute-1.amazonaws.com  <-- full path
[13:03] <santa_> and they could be developed with other people sharing efforts and in a way which would be reusable by kubuntu and neptune
[13:03] <santa_> imho
[13:04] <shadeslayer> huh
[13:04] <shadeslayer> Riddell: worked now, I suppose it was only a matter of ec2 being a bit slow
[13:04]  * ximion never heard of neptune....
[13:06] <ximion> santa_: well, I am no member of the Kubuntu packagers, but of the Debian/KDE team, so I can only speak for Debian/KDE and say that there might be problems
[13:06] <ximion> for Kubuntu, I don't know
[13:07] <ximion> and Tanglu has a similar policy than Ubuntu for this kind of stuff, so that would work. Also giving Ubuntu devs upload permission to Tanglu can be done quickly (but we still need a good NewMember procedure - Tanglu is very young....)
[13:09] <santa_> http://www.zevenos.de/
[13:11] <santa_> ximion: if I had permissions to upload to tanglu I could, for instance, develop kde sc 4.10.4, copy most of the packages to siduction and customize just a few ones
[13:11] <santa_> and I could help the neptune guy to backport such packages to neptune
[13:12] <santa_> the problem is, as you said the new member procedure of tanglu
[13:12] <santa_> specially, because, you know I'm a DR
[13:12] <santa_> * specially, because, you know, I'm a DR
[13:14] <ScottK> shadeslayer: Can you check spam folders, etc to see if the rejection mail went astray?  People are pretty sure it gets sent.
[13:14] <shadeslayer> ScottK: already checked
[13:14] <shadeslayer> nothing there
[13:17] <ximion> santa_: yes, I know that...
[13:18] <ximion> but as soon as the base system is ready, I don't see an argument why you shouldn't be working on Tanglu - but we need to define some policies and upload permisions first
[13:18] <ximion> also, syncing packaging between distributions seems to be a good idea (at least I think that :P)
[13:19] <yofel> santa_, ximion: I'm all for sharing efforts, esp. as dependency updates, file changes or new packaging will be mostly the same. But working *first* is impossible.
[13:19] <yofel> maybe we could coordinate some changes in debian git, but that would be all
[13:19] <yofel> *first in debian
[13:21] <shadeslayer> can someone send me a test email at : rohangarg AT kubuntu dot org?
[13:21] <shadeslayer> seems like email aliasing is broken
[13:21] <santa_> shadeslayer: you have any idea when lezek is around?
[13:22] <shadeslayer> not really
[13:22] <santa_> ximion: that's nice to know, if I happen to have permissions on tanglu I can assure you the tanglu -> siduction flow will work
[13:22] <shadeslayer> oh drat
[13:23] <yofel> santa_: what was your workflow for the .4 packaging btw.? (As you say you're already done)
[13:23] <shadeslayer> yofel: http://paste.kde.org/759122/
[13:23] <santa_> and then should be easy to add siduction -> tanglu to the chain
[13:23] <santa_> adding kubuntu would be more difficult tough
[13:23] <shadeslayer> no graphics card :(
[13:24] <shadeslayer> can't use ec2 for testing :((
[13:24] <santa_> yofel: I'm not using git for my packages
[13:26] <yofel> santa_: yeah, but do you package all 141 packages by hand? Or do you have something of that automated?
[13:26] <santa_> I just grab debian's git, do my changes and upload to siduction repo
[13:27] <shadeslayer> by hand? :O
[13:28] <yofel> santa_: our workflow is based on bzr for the dev release, classic packaging for the stable release updates and most of the work is done by http://bazaar.launchpad.net/~kubuntu-packagers/+junk/kubuntu-automation/files
[13:29] <santa__> ugh, something wrong happened to my network
[13:29] <yofel> heh
[13:29] <santa__> shadeslayer: I do add the changelog entries by hand, unfortunately
[13:30] <santa__> I do bump the kde-sc-dev-latest version with just one command for a given batch
[13:30] <santa__> I will figure out something for the changelog entries one of these days too
[13:32] <ScottK> I think people that want to derive from Kubuntu packaging are welcome to do so.  People that have changes to improve the packaging are welcome to provide them.  After some sustained, quality contribution, they can become a Kubuntu member and get rights to commit to branches directly.
[13:33] <ScottK> In 6 years of Ubuntu development, I've yet to see a change pushed back to Ubuntu from a derivative, so I'm not holding my breath.
[13:33] <shadeslayer> ScottK: better ? http://paste.ubuntu.com/5735765/
[13:34] <santa__> shadeslayer: yofel: not sure if I answered your questions
[13:35] <ScottK> shadeslayer: I'd keep the debian/copyright updates and in changelog I'd say New upstream release that fixes ....  and describe the reason we're SRUing this.
[13:35] <santa__> shadeslayer, yofel: if I happen to have time one of these days I could explain with more detail how a guy with 8 fingers available packages the whole kde sc in a weekend for both i386 and amd64 :D
[13:36] <shadeslayer> ScottK: ack
[13:36] <yofel> santa__: mostly, we have a bit of a scripted workflow based on http://bazaar.launchpad.net/~kubuntu-packagers/+junk/kubuntu-automation/files
[13:36] <shadeslayer> heh, never noticed ^^
[13:41] <santa__> yofel: good to know, I should take a look when I have time
[13:41] <shadeslayer> ScottK: all fixed : http://paste.ubuntu.com/5735779/
[13:41] <ScottK> shadeslayer: go for it.
[13:42] <shadeslayer> ScottK: uploaded
[13:42] <ScottK> ok
[13:42] <ScottK> Will look in a bit.
[13:43] <shadeslayer> thx
[13:43] <shadeslayer> ScottK: could you move the gtk2 package to -updates as well?
[13:43] <ScottK> shadeslayer: Not yet, it's only 5 days old.
[13:43] <shadeslayer> oh drat, 7 day rule even though we have verification-done
[13:48] <santa__> shadeslayer: do you at least know lezek's nickname? is it the obvious one?
[13:50] <shadeslayer> santa__: it is the obvious one :)
[13:50] <shadeslayer> :(
[13:50] <santa__> ok, thanks
[13:51] <shadeslayer> /sys/class/power_supply/BAT0/energy_full_design = 69000000 , /sys/class/power_supply/BAT0/energy_now = 15160000
[13:51] <shadeslayer> I need a new battery
[13:51] <santa__> I must leave, thanks for your opinions about my ideas
[13:51] <yofel> shadeslayer: at least your battery shows the correct design capacity ^^
[13:51] <shadeslayer> xD
[13:52] <yofel> mine is still at 98% health after 3 years because the design capacity is changing all the time ^^
[13:52] <shadeslayer> hah
[13:52] <yofel> though I have "last full capacity 7700 mAh", so I guess I can't complain
[13:53] <shadeslayer> yofel: /sys/class/power_supply/BAT0/cycle_count is 0 :P
[13:54] <shadeslayer> otto is just weird
[13:54] <shadeslayer> craps out my entire X
[13:54] <yofel> shadeslayer: here it's 0 too, real value is 243 but I need tp_smapi to read that
[13:54] <shadeslayer> what's that?
[13:55] <shadeslayer> thinkpad thingy
[13:55] <yofel> yeah
[13:55] <yofel> ThinkPad SMAPI Support
[13:56] <yofel> pretty fun actually. I can force discharge a batter on AC, tell it to only start charging at 50%, tell it to stop at 80% and stuff like that
[13:57] <yofel> $ cat first_use_date 
[13:57] <yofel> 2010-06-01
[13:57] <yofel> heh, almost exactly 3 years old
[13:57] <yofel> meaning my warranty for the notebook expired a few days ago... never had to use it
[14:01] <Quintasan> 1/4 tests cleared
[14:01] <Quintasan> yofel, shadeslayer: iirc smapi doesn't work or newer thinkpad models
[14:02] <Quintasan> At least it doesnt work on mine
[14:02] <Quintasan> \o
[14:02] <yofel> bummer
[14:03] <Quintasan> tpacpi-bat
[14:03] <Quintasan> saves the day
[14:03] <Quintasan> I can set battery treshholds with that
[14:05] <ScottK> shadeslayer: You can only use a version once.  How about 0.1 for raring.
[14:08] <Quintasan> shadeslayer: You didn't do ktp, right?
[14:09] <Riddelll> Quintasan: he often does
[14:10] <Quintasan> derp
[14:10] <Quintasan> Riddelll: Did you send me the G9 tablet?
[14:10] <Riddelll> Quintasan: um no, sorry I said I would didn't I?
[14:10] <shadeslayer> Quintasan: nope
[14:11] <shadeslayer> ScottK: oh, I didn't use 0.1 in the upload?
[14:11] <ScottK> no
[14:11] <Quintasan> Riddelll: I believe you did at some point. It's not really important now but during holidays I can toy around with it.
[14:11] <Quintasan> shadeslayer: I see. I need to get to it
[14:11] <Darkwing> My quick look at 13.10. :D http://youtu.be/_BOrpTTXTtU
[14:11] <shadeslayer> ScottK: sorry about that
[14:11] <ScottK> no problem
[14:12] <Riddelll> Quintasan: ok will do tomorrow, keep poking me if not, e-mail your address again please
[14:13] <Quintasan> Riddelll: jr@jriddell.org is okay?
[14:13] <shadeslayer> Riddelll: btw they dropped the n7 desktop kernel in saucy
[14:13] <Riddelll> Quintasan: yep
[14:13] <Quintasan> shadeslayer: what?
[14:13] <Quintasan> christ
[14:13] <Quintasan> what the hell?
[14:13] <shadeslayer> yes
[14:13] <shadeslayer> they're using android stuff now
[14:13] <shadeslayer> though it's still available on git
[14:14] <Riddelll> fooey
[14:14] <Quintasan> Riddelll: Sent.
[14:14] <shadeslayer> ScottK: proper version uploaded
[14:14] <Quintasan> shadeslayer: Ridiculous if you ask me :P
[14:15] <shadeslayer> Quintasan: not really, makes sense for them :P
[14:15] <shadeslayer> Quintasan: though the setup they had did fancy things
[14:15] <shadeslayer> like updating the kernel when you first booted the device
[14:15] <shadeslayer> and then updating whenever there were new kernels in /boot
[14:16] <shadeslayer> What I want to do right now is have a rootfs that launches oem-config and is populated with the N7 X11 drivers
[14:17] <shadeslayer> and use the desktop kernel already available
[14:18] <Quintasan> shadeslayer: Do you recall the order of ktp packaing?
[14:19] <shadeslayer> common-internals , then everything else
[14:19] <Riddelll> he's got a magic script to do it no?
[14:19] <Quintasan> Okay
[14:19] <Quintasan> You do?
[14:19] <Quintasan> Gibe pls
[14:19] <shadeslayer> uh
[14:19] <shadeslayer> lemme fish it out
[14:20] <shadeslayer> Quintasan: http://paste.kde.org/759182
[14:20] <shadeslayer> Quintasan: please adjust hardcoded values
[14:20] <Quintasan> wat.
[14:20] <Quintasan> I see
[14:22] <shadeslayer> I suspect you don't need the sed calls now
[14:22] <ScottK> Still waiting for the diff.
[14:22] <shadeslayer> and I'm waiting for some respite from the heat, thing is, you'll probably get the diff faster
[14:23] <shadeslayer> 41 degrees
[14:23] <shadeslayer> I'm melting
[14:23] <shadeslayer> melting I tells ya
[14:23] <Quintasan> I think it doesn't work shadeslayer but whatever
[14:24] <shadeslayer> lies
[14:25] <Quintasan> ktp-common-internals_0.6.1dfsg1-0ubuntu1.debian.tar.gz <--- dfsg
[14:25] <Quintasan> wat
[14:26] <shadeslayer> whut
[14:26] <Quintasan> aaah
[14:26] <Quintasan> Skype icons
[14:26] <Quintasan> This script is uttery broken
[14:26] <shadeslayer> aha
[14:26] <shadeslayer> It needs tweaking ;)
[14:26] <shadeslayer> because, dfsg
[14:26] <Quintasan> It needs rewriting
[14:27] <shadeslayer> tweaking
[14:27] <shadeslayer> anyway
[14:27] <shadeslayer> dinner
[14:50] <shadeslayer> ScottK: diff available :)
[15:01] <Quintasan> ScottK: Is ktp-common-internals_0.6.2+dfsg.orig.tar.bz2 a proper tarball name?
[15:02] <ScottK> Yes
[15:03] <Quintasan> I see.
[15:03] <Riddelll> means it's been changed to remove something non-free
[15:03] <Riddelll> probably skype icons
[15:03] <Quintasan> ScottK, apachelogger_: The http://pkg-perl.alioth.debian.org/howto/repacking.html has a script that is utterly wrong
[15:03] <Quintasan> Riddelll: I know, I'm trying to figure out if there is a proper way of doing tarball repacks
[15:04] <Quintasan> Turns out the script doesn't work
[15:04] <Quintasan> I'll just remove it and pack it back
[15:08] <Quintasan> ScottK: Will that work ^?
[15:08] <Riddelll> Quintasan: sure
[15:25] <Quintasan> ScottK: Would you consider saying something good if I wanted to get DD?
[15:44] <ScottK> I'd want to have sponsored you first in Debian (if I haven't), but yes.
[15:45] <debfx> Quintasan: are you a DM already?
[15:45] <Quintasan> debfx: Not yet.
[15:45] <Quintasan> ScottK: Well, I want to update the whole telepathy-kde stack in Debian
[15:46] <Quintasan> It's a hassle to keep it updated in Ubuntu without doing that
[15:46] <ScottK> DM is probably what you want to start with then.
[15:46] <Riddell> gosh, a littlegirl 
[15:46] <littlegirl> Hey there! (:
[15:47] <littlegirl> How are the docs coming along? I'm finally back at my computer after 10 months away.
[15:47] <Riddell> littlegirl: people can spend 10 months away from their computers?
[15:47] <Riddell> littlegirl: we've a new docs master ahoneybun who is doing interesting things
[15:48] <Riddell> and valorie and Darkwing are doing interesting things with him
[15:48] <littlegirl> You wouldn't think so, but it happened against our will and quite unexpectedly. I've missed it, and I can see from the piles of emails I'm still wading through that a lot has changed. I hope to be able to contribute to the docs again. (:
[15:52] <littlegirl> Server burp.
[15:53] <Quintasan> ScottK: Can you make KTP uploads to Debian happen when I have everything building?
[15:53] <littlegirl> Am I right that the docs are all on a wiki now and no longer done in DocBook?
[15:53] <ScottK> Who's maintainer (and probably not today).
[15:53] <ScottK> littlegirl: Welcome back.
[15:53] <apachelogger_> Quintasan: I think ou are using it wrong
[15:53] <apachelogger_> Quintasan: the script worked 2 months ago just fine
[15:53] <Quintasan> ScottK: gkiagia is but he is no longer taking care of those
[15:53] <Quintasan> apachelogger_: Maybe. I don't really care now, gotta update it in Debian.
[15:53] <littlegirl> Thanks. (:
[15:53] <lordievader> Good afternoon all :)
[15:53] <Riddell> littlegirl: yes I think so
[15:54] <ScottK> Quintasan: Debian KDE Extras Team is maintainer, so anyone in the team can upload it.
[15:54] <ScottK> You can add yourself to uploaders.
[15:54] <ScottK> I doubt I'll have time to sponsor before the weekend though.
[15:55] <littlegirl> Riddell: Thanks. I'll have to learn a bit more about how they're doing things now, and once I install the new version of Kubuntu (still using 10.04, believe it or not), I'll hop back in and help with whatever they need. (:
[15:55] <ScottK> Feel free to find someone else so I don't block (Ask on #debian-qt-kde)
[15:55] <lordievader> littlegirl: Contact either valorie or ahoneybun, they are quite hard at work on the wiki.
[15:57] <littlegirl> lordievader: Will do, thanks!
[16:11]  * Riddell wonders why the bold highlighting doesn't work in rekonq for http://kyofel.dyndns.org/kubuntu/build_status_4.10.4_saucy.html
[16:14] <shadeslayer> Riddell: WFM
[16:15] <shadeslayer> Riddell: http://i.imgur.com/fSfsAjF.png
[16:16] <Riddell> shadeslayer: that rekonq?
[16:16] <shadeslayer> yes
[16:16] <Riddell> mm, something spooky about mine then
[16:17] <shadeslayer> spooky is one way to describe that :P
[16:19] <shadeslayer> I wish LP had an undo feature for when your mouse goes crazy and just clicks on random things
[16:20] <Riddell> does that often affect launchpad?
[16:21] <shadeslayer> no, it often affects my crazy mouse
[16:21] <shadeslayer> I think I need to get it replaced
[17:09] <Quintasan> shadeslayer: get some decent hardware!
[17:09] <Quintasan> says Quintasan whose intel core i5 reports 3 cores
[17:09] <shadeslayer> lol
[17:09] <shadeslayer> Quintasan: I've had this mouse for almost a year
[17:09] <shadeslayer> I've used it *alot*
[17:09] <shadeslayer> so I'm not surprised it's giving out
[17:10] <shadeslayer> (*&(*&^
[17:10] <shadeslayer> 50 KBps
[18:13] <ahoneybun> Riddell: I would hardly call myself a docs master lol
[18:14] <yofel_> !testers | 4.10.4 is ready for testing in ninja PPA for raring
[18:15] <soee> yohoho :)
[18:15] <soee> here i am
[18:16] <soee> yofel_, yor private ppa ?
[18:16] <yofel_> soee: in the private ppa
[18:18] <lordievader> Whoo neat :)
[18:20] <lordievader> Hmm, it seems the Ninja ppa is no longer on my pc. Would someone be so kind to pm it to me? :)
[18:24] <yofel> lordievader: pm
[18:26] <lordievader> :D
[18:29] <BluesKaj> yofel , I don't have the ninjas ppa either 
[18:30] <BluesKaj> ok yofel , got it thanks
[18:39] <genii> I wonder how the ninjas stay stealthy in their Kubuntu Blue outfits
[18:40] <lordievader> yofel: I see no errors/bugs at this time. It even seems faster, but that might be me...
[18:55] <hrw> hello
[18:56] <hrw> can kwin be used without opengl(es) support?
[18:56] <hrw> cause on chromebook/armhf I lack both
[18:56] <jessie> hrw: Yes, but you won't get pretty compositing features.
[18:57] <jessie> Pretty sure it will be just like if you disabled the desktop effects option.
[18:57] <hrw> jessie: I do not have window decoration even
[19:00] <soee> yofel, no errors during upgrade
[19:18] <BluesKaj> yofel . Riddell et al , noglitches with 4.10.4 so far
[19:33] <lordievader> Quintasan: DDOS attacks.
[19:34] <jessie> ^
[19:34] <jessie> Lots of them. And so, Freenode is dying.
[20:03] <ScottK> Same channel on OFTC then if this one goes.
[20:05] <ahoneybun_> valorie_: ping
[20:21] <BluesKaj> ScottK, OFTC?
[20:22] <ScottK> Where the Debian IRC channels are.
[20:22] <ScottK> oftc.net
[20:22] <genii> BluesKaj: Different IRC network
[20:22] <BluesKaj> ok , thanks ScottK , genii
[20:41] <ahoneybun_> Hello
[20:50] <ahoneybun_> valorie_: ping
[21:06] <valorie_> ahoneybun_: pong
[21:07] <ahoneybun_> valorie: only thing left is development
[21:08] <valorie> well, until we come up with more work, lol
[21:08] <valorie> ok, I'll write to the list
[21:08] <valorie> I've been putting that off
[21:10] <ahoneybun_> valorie: yep that's good
[21:10] <ahoneybun_> valorie: Riddell says I'm the doc master lol
[21:11] <valorie> you have been the engine, for sure
[21:11] <ahoneybun_> Yep
[21:11] <valorie> I hope that this is a group effort, and we defer to the experts who've been doing this for years
[21:12] <ahoneybun_> Yea it seems to be so far
[21:13] <valorie> littlegirl PM'd me about this effort, but so far I don't see her here
[21:13] <ahoneybun_> Yea I saw that
[21:13] <valorie> she worked on the docs quite a bit last year
[21:14] <valorie> so it would be nice to see her here again
[21:14] <ahoneybun_> Oh that will be great
[21:16] <ahoneybun_> Also I made a tumblr for the project
[21:17] <valorie> for Kubuntu?
[21:17] <ahoneybun_> The docs
[21:17] <valorie> hmmm
[21:17] <valorie> ok, address?
[21:17] <valorie> dunno how much fossy stuff is on tumblr
[21:18] <valorie> I am, but mostly for graphics, friends, and a bit of politics
[21:18] <valorie> and doctor who, of course
[21:18] <valorie> since it is fan central
[21:20] <ahoneybun_> http://ahoneybun.tumblr.com/
[21:22] <ahoneybun_> valorie: just for fun
[21:25] <ahoneybun__> Still we are making progress
[21:27] <soee> yofel, upgrade and reboot after (4.10.4) all fine (except i had black screen when trying to reboot - had to do hard reset)
[21:31] <yofel> :/
[21:31] <yofel> good that it works at least...
[21:31] <soee> but this might be somehow related to my old laptop
[21:31] <soee> the same i have problem with kded4
[21:31] <valorie> ahoneybun: followed
[21:39] <ahoneybun_> Hello
[21:40] <ahoneybun_> valorie: ping
[22:07] <valorie> dude, you don't have to ping
[22:07] <valorie> just say what you have to say and use my nick
[22:16] <jessie_> vHanda: Any news on my nepomuk?
[22:18] <valorie> ahoneybun: I'm always here, or "here" via my bnc
[22:18] <valorie> so just talk to me
[22:22] <yofel> jessie_: what was your issue again? nepomuk just not starting? or does it crash?
[22:23] <jessie_> yofel: Nepomuk doesn't start.
[22:24] <yofel> jessie_: curious, what does your .kde/share/apps/nepomuk/repository/main/data/virtuosobackend/soprano-virtuoso.log say?
[22:24] <yofel> A few days ago it stopped working on my other notebook too dure to a corrupt soprano-virtuoso.trx
[22:24] <yofel> *due to
[22:25] <jessie_> That appears to be the same issue that I'm having.
[22:26] <jessie_> yofel: http://pastebin.com/rgx6cZAf
[22:26] <yofel> jessie_: can you rename the soprano-virtuoso.trx and restart nepomuk?
[22:28] <jessie_> yofel: And it's working again.
[22:29] <jessie_> Looks like that is my problem.
[22:31] <yofel> hm, so I guess it really is the same thing I had. Except that I have no idea what happened, and I don't even see anything particulary broken in the .trx - except maybe a really long DB.DBA.JSO_PIN_GRAPH line
[22:32] <jessie_> yofel: Well, it's reproducible for me every time I remove all my nepomuk related config files.
[22:33] <jessie_> It's only a matter of time until nepomuk refuses to start again.
[22:33] <jessie> Also on a notebook, with SSD + HDD combo on here, not sure if that matters.
[22:34] <yofel> hm, my notebook with the SSD+HDD combo works prefectly fine, it's my SSD notebook from work that had the issue here.
[22:34] <yofel> Hasn't popped up again so far, so maybe it's the indexer choking on something specific and trying to store something invalid in the DB...
[22:34] <yofel> I'm only guessing though
[22:35] <jessie> An invalid character from a filename, maybe?
[22:35] <Riddell> evening