[00:01] <Riddell> promulo: "I work at Embedded Systems and Pervasive Computing Lab" but you're also a student?
[00:02] <Riddell> promulo: and you're doing a masters course over the summer too?
[00:08] <Riddell> promulo: I think "Zeroconf integration" can be done as part of phase 2.1, it's very easy to advertise stuff with avahi, just run the command line if nothing else
[00:08] <Riddell> promulo: looks good otherwise
[00:12] <neversfelde> mhh, we probably patched away amarok's last.fm icons
[00:12] <Riddell> we did?
[00:13] <Riddell> I still see them
[00:13] <Riddell> maybe they won't show on Gnome but I don't think Gnome does menu icons anyway
[00:13] <neversfelde> Riddell: They are away here, after last update. Same problem for kopete
[00:13] <neversfelde> Riddell: this is a fresh lucid installation
[00:14]  * Riddell updates
[00:14] <neversfelde> for kopete this problem exists longer, I did not have the time to check if there is a bug report
[00:15] <Riddell> still there for me
[00:15] <Riddell> in new amarok version
[00:15] <Riddell> also has icon overlay too
[00:15] <Riddell> oh wait, "love" icon gone now
[00:15] <Riddell> spooky
[00:16] <genii> Hm
[00:16] <Riddell> probably agateau is away for easter, could you report a bug and e-mail him?
[00:18] <neversfelde> Riddell: http://imagebin.ca/view/lc6Ng96.html
[00:18] <neversfelde> Riddell: will do
[00:19] <Riddell> /usr/share/kde4/apps/amarok/icons/hicolor/16x16/actions/love-amarok.png  I think it's because it's in there rather than in the global icons directory
[00:19] <Riddell> easily fixed
[00:20] <lex79> Riddell: ehehe that bug took me so long time to figure out and one second to fix
[00:21] <lex79> :)
[00:22] <ryanakca> ScottK: CMakeLists.txt explicitly refers to libinfinity-0.3 . Should I patch to -0.4 or should we drop libqinfinity/kobby from lucid?
[00:24] <genii> I'm reminded of the printing-press repairman. Comes in, looks around for 8-10 hours. Takes a little mallet inside of the printing press, taps 2-3 times and fixes everything. Hearst says "why should I pay you $20,000 ? I could tap something with a hammer"  repairman says: "Yes, but would you know where to tap it?"
[01:01] <neversfelde> is it planned to have a big logo like this in kickoff? If so, it is not a good idea :)
[01:02] <neversfelde> mhh, where is my screenshot
[01:06] <neversfelde> http://imagebin.ca/view/kyg_se.html
[01:07] <lex79> maybe it's too big :)
[01:07] <neversfelde> definitely   :)
[01:12] <lex79> Riddell, apachelogger: I updated kubuntu_12_kubuntu_homepage.diff in bzr, it works
[01:22] <ryanakca> Hmmm... Anybody having a hard time connecting to Jabber servers with Kopete since the latest upgrade?
[01:22] <ryanakca> (which may or may not have anything to do with it)
[01:23] <neversfelde> ryanakca: no, everything is fine here
[01:28] <ryanakca> neversfelde: *nod*
[03:10] <maco> Riddell: there's not a freeze in effect right now is there?
[03:11] <maco> Riddell: nevermind. oops.
[03:11] <maco> Riddell: oh wait thats only for main! yay!
[03:11] <Riddell> maco: are you uploading something?  it'll need an archive admin to accept it
[03:12] <maco> Riddell: to universe, yeah. python-foolscap to fix a really nasty performance bug
[04:32] <ScottK> ryanakca: I'd contact upstream and ask them about 0.4 support
[04:44] <promulo> Riddell: sorry, I'd to go out
[04:44] <promulo> for "work" I mean the masters course itself =)
[04:55] <nixternal> apachelogger: any idea what groo is doing with koffice? why is he uploading to revu when I uploaded 2 days ago 2.1.2?
[04:56] <nixternal> oh well, back to work...later
[04:59] <ScottK> Tm_T: kdeutils is the last 4.4.2 package for powerpc.  It's next up for a powerpc builder.
[05:35] <Tm_T> ScottK: yay, let's see if other fixes are soon available too
[05:57] <Riddell> nixternal: 2.2 beta is different from 2.1.2
[05:57] <Riddell> except quintisan was also packaging it
[06:04] <apachelogger> Riddell: I reopened that bug after the fix, so that it shows up in my assigned bugs list and I make sure to revisit the issue ^^
[06:05] <apachelogger> lex79: cool, thanks
[06:07] <apachelogger> bug 290351 for lucid+1 \o/
[06:09] <apachelogger> mhh, quite some bugfixes too
[06:09]  * apachelogger likies
[06:09] <apachelogger> -i
[06:10] <apachelogger> Riddell: btw, did you update kde-l10n in the backports ppa too?
[06:19] <ScottK> I was telling one of my daughters (the 16 year old) the story of Ubuntu moving the buttons to the left side.
[06:19] <ScottK> She totally freaked out.  It took several repetitions of "You use Kubuntu, it's Ubuntu being changed, don't worry" to calm her down.
[06:20] <ScottK> It's not just geeks that are annoyed.
[06:20] <apachelogger> we should have moved the buttons to the left for april 1 :P
[06:21]  * apachelogger totally didnt know we are that close to april until yesterday morning ^^
[06:23] <ScottK> Would have been a great idea.
[06:23] <ScottK> Off to bed with me.  Good night.
[06:23] <apachelogger> nini ScottK
[06:24] <apachelogger> oh my
[06:24]  * apachelogger thinks dr konqi should also be used to report bugs via help->report bugs
[06:27] <Riddell> apachelogger: oh I quite forgot about backports
[06:27] <apachelogger> Riddell: cool, let me try the script enhancements :)
[06:29] <apachelogger> hm, that might not be as smooth as with source format 3
[06:29] <apachelogger> well, lets see
[06:40] <apachelogger> ^^
[06:40] <apachelogger> Riddell: all I had to do is add a new changelog entry, then
[06:40] <apachelogger> debian/build-l10n.sh ca@valencia en_GB pt_BR zh_CN zh_TW
[06:41] <apachelogger> and debian/upload-l10n.sh
[06:41] <apachelogger> done
[06:41] <apachelogger> :D
[07:20] <apachelogger> or maybe not
[07:20] <apachelogger> with source format 3 it would work ^^
[07:35] <apachelogger> Riddell: can I upload pkg-kde-tools so that it gets left in queue until after freeze?
[08:05]  * apachelogger blinks
[08:05] <apachelogger> oh great, now plasma hates me -.-
[08:05] <apachelogger> ah!
[08:06] <apachelogger> one cant configure which widgets are embedded in the systray if the panel is locked
[08:06]  * apachelogger finds that a bit confusing
[08:09] <nixternal> holy shite, today was nothing but work...all work and no play today
[08:09] <nixternal> just realized it was 02:10...
[08:10]  * nixternal beds
[08:14]  * apachelogger leaves a cookie on nixternal's desk
[08:15]  * apachelogger just found out that when widgets are locked you cant remove them via the scripting api
[08:15] <apachelogger> adding however works
[08:35] <apachelogger> Riddell: new update to kds making updates work when widgets are locked + migrating indicatordisplay to message-indicator
[08:36] <apachelogger> Riddell: also, shouldn't bug 538512 be prevented by freetype?
[08:36] <apachelogger> i.e. the diffrerence between kde and gnome
[08:48] <apparle> I have installed kdenetwork-dbg package, and I want to see the debugging messages of kopete. But when I start the kopete in konsole, I don't get any error, but I cannot login either
[08:50] <apachelogger> you dont neeed kdenetwork-dbg to get debugging messages
[08:50] <apachelogger> -dbg is only good if you have a crash and want to backtrace the crash
[08:51] <apachelogger> to turn on debugging just start kdebugdialog and select everything
[08:51] <apachelogger> then start kopete form a terminal
[08:55] <apparle> apachelogger: alright thanks
[09:00] <apparle> apachelogger: and If I want to see the various internals of a driver (xserver-xorg-video-ati)
[09:00] <apachelogger> the what?
[09:01] <apparle> apachelogger: I mean any debugging messages it may be generating, other than that in Xorg.0.log
[09:01] <apparle> apachelogger: are ther any such messages?
[09:01] <apachelogger> there are no others
[09:01] <apachelogger> though
[09:02] <apachelogger> I wouldnt know
[09:02] <apachelogger> apparle: X is in #ubuntu-x
[09:02] <apparle> apachelogger: so if I would like to debug a driver, you have any suggestion
[09:02] <apachelogger> no, #ubuntu-x might
[09:02] <apachelogger> we do kubuntu in here
[09:03] <apparle> apachelogger: thanks
[09:21] <apachelogger> Riddell, JontheEchidna: bug 553862
[09:23] <apachelogger> sebas: do you happen to know whether the effects settings in the style kcm get detected on-the-fly or are they hardcoded to gpu-- && cpu++?
[09:24]  * apachelogger finds it a bit weird that it claims his atom is a fast cpu ^^
[10:15] <jussi01> http://www.markshuttleworth.com/archives/336
[10:15] <jussi01> Maverick Meerkat
[10:42] <ghostcube_maemo> o/
[11:40] <manchicken> Howdy.
[11:41] <Tm_T> hi manchicken (:
[11:41] <manchicken> Long time no see :)
[11:41] <Tm_T> indeed, been wondering what happened to you
[11:41] <manchicken> These "toddler" things are time-consuming.
[11:42] <Riddell> get them coding, that's the answer
[11:42] <manchicken> Hah!
[11:42] <Tm_T> toddler?
[11:42] <manchicken> He wouldn't mind it, that's for sure :)
[11:42] <manchicken> Yeah, you don't remember?
[11:42] <Tm_T> I don't know what that word means
[11:42] <manchicken> My wife tested positive for children during UDS-Sevilla in May of 2007.
[11:42] <manchicken> Toddler, a rather small child.
[11:42] <Tm_T> I see, congrats
[11:43] <Riddell> baby who's starting to walk/crawl
[11:43] <manchicken> This one's starting to use computers.
[11:43] <Tm_T> manchicken: we have a 1 year 4 months old daughter here (:
[11:43] <manchicken> And pinching iPhones...
[11:43] <manchicken> Very nice :)
[11:43] <Tm_T> and she already learnt to use keyb and mouse
[11:43] <Tm_T> ...unfortunately
[11:43] <manchicken> My boy just grabs anything with buttons and starts pushing.
[11:43] <Tm_T> aye
[11:43] <manchicken> Doesn't matter what it is.
[11:44] <manchicken> I've also been playing with a lot of non-Kubuntu-related techs.
[11:44] <Tm_T> I have noticed the same
[11:44] <manchicken> I've been on the OS X happy path for a little over a year now... which is nice since I haven't had much time, and since my current employer is very Mac-friendly.
[11:45] <manchicken> It's not the same though... I often miss writing software under the direction of Scotsmen and Frenchmen.
[11:46] <manchicken> Though I often wonder if my new-found love for Objective-C would fare well in the Kubuntu world.
[11:47] <manchicken> I'm fetching 10.04 as we speak, to be installed in boot-camp on this spectacular new 500GB hard drive I picked up two weeks ago.
[11:48] <manchicken> I know there's GNUStep... but it's just so ugly.
[11:48] <manchicken> Étoile looks better, but it's still pretty ugly.
[11:55] <manchicken> Riddell: What sort of stuff have you guys been talking about for the next go-round?
[12:03] <manchicken> Sucks... they're going to make me burn the ISO to disc to install it...
[12:07] <Riddell> manchicken: we haven't started looking at Maverick yet
[12:07] <manchicken> Oooh, you all have named this one after Sarah Palin have you?
[12:07] <manchicken> heh
[12:08] <jussi01> manchicken: you cant use the usb creator?
[12:08] <manchicken> Most Americans I believe are weary of that word :)
[12:08] <manchicken> jussi01: I'm trying to install it onto bootcamp. I think the bootcamp assistant wants a disc.
[12:09] <jussi01> manchicken: oh bleh.
[12:09] <debfx> Riddell: the current brightness patch doesn't do anything anymore as the hal property brightness_in_hardware is set to true by default in lucid
[12:10] <Tonio_> I'm giving up on the qt cursor thing.... too hard :'(
[12:10] <debfx> Riddell: the old patch checked that property as a workaround because some laptops (mainly the MSI Wind, which is fixed in Lucid) send brightness key events on every change
[12:16] <Riddell> debfx: I see
[12:17] <Riddell> debfx: I think we should get your patch upstream before patching our packages
[12:17] <Riddell> since it's partly agateau's code I wonder if he'd be able to help with that
[12:21] <manchicken> Dookie... I nabbed the wrong image.
[12:22] <debfx> before the patch can go upstream the osdwidget class needs to be put in a place where both kmix and the battery applet can use it
[12:22] <Tonio_> http://qt.gitorious.org/qt/davidben-qt/commit/7e46ddb8e12a18f5ceb723a4b5d9487ca53a0e45?diffmode=sidebyside
[12:22] <Tonio_> HU ??????????? seems that's the fix
[12:23] <Tonio_> strange it's not in the stable branch yet, but that seems to do exactly what I wanted to.... Testing
[12:28] <manchicken> Sad, nobody's seeding the beta1 torrent right now...
[12:30] <Riddell> beta 1 is old news, everyone is waiting for beta 2
[12:30] <manchicken> I'm just trying to get something I can throw into boot camp that isn't going to take another two hours to update.
[12:30] <manchicken> That said, it's still probably futile.
[12:30] <manchicken> I'll probably do that anyway :)
[12:31]  * Riddell away for weekend
[12:33] <manchicken> http://brainstorm.ubuntu.com/idea/23489/ <-- I wonder if solution #1 on this idea is even possible. I suppose we'd need to first be able to cross-compile to the A4.
[12:35] <manchicken> I guess there'd then have to be some sort of hardware driver for the multi-touch interface. That'd be neat if it could be pulled off though.
[12:40] <apparle> I am trying to solve the problem of kopete and gtalk.  I am gettting this error when running Kopete from konsole "Unknown signature value:  795 "
[12:40] <apparle> It is followed by "kopete(3652)/kopete (jabber - raw protocol) JabberAccount::slotClientDebugMessage: "Client stream error.""
[12:40] <manchicken> Sounds like a TLS issue, no?
[12:41] <manchicken> gtalk does use TLS, no?
[12:41] <apparle> manchicken: I am not sure, but it does use some encryption
[12:41] <manchicken> I'm pretty sure it's using TLS.
[12:41] <agateau> Riddell: not sure I understand what you mean
[12:41] <agateau> Riddell: I didn't work on powermanager
[12:42] <manchicken> apparle: Do you have qca-tls installed?
[12:42] <apparle> manchicken: I'll check
[12:42] <manchicken> I would think it's a default install, but it has been a while.
[12:43] <apparle> manchicken: no
[12:43] <manchicken> I do believe you'll need qca-tls, but then again, as I said before, it has been a while.
[12:45] <manchicken> apparle: What's your kopete version?
[12:45] <apparle> 4.4.2
[12:45] <ryanakca> ScottK: Sent. I'm going skiing with the family, I'll be back Sunday night. Sorry for the delay.
[12:45] <apparle> I am running 10.04 beta1
[12:48] <apparle> manchicken: I installed qca-tls but I am getting the same error
[12:48] <manchicken> Did you restart kopete?
[12:49] <apparle> manchicken: :D yes
[12:49] <manchicken> Just checking :)
[12:49] <manchicken> I'm throwing 10.04 on bootcamp, I'll be in it shortly.
[12:49] <manchicken> I can see if I can replicate. I'll also check LP for a bug.
[12:50] <apparle> manchicken: I am getting this error for specific condidtions
[12:50] <manchicken> Which conditions?
[12:50] <manchicken> It doesn't appear as though this exists in LP.
[12:50] <apparle> manchicken: I am using "talk.google.com" host and "443" port
[12:50] <manchicken> That's what I would expect.
[12:50] <manchicken> 443 is the SSL/TLS port, talk.google.com is the host for gtalk.
[12:50] <apparle> manchicken: normal ports are blocked by college firewall
[12:50] <apparle> manchicken: what's a bootcamp
[12:51] <manchicken> bootcamp is the utility in Mac OS X for booting into multiple operating systems.
[12:51] <apparle> manchicken: normally its gmail.com and 5222/5223 so I told you
[12:51] <manchicken> Interesting.
[12:52] <apparle> manchicken: by default its like that
[12:52] <apparle> and I have to override the default host/port for the one I mentioned above
[12:52] <manchicken> According to google 443 is also an acceptable port for that, so I would doubt there'd be any issue.
[12:52] <manchicken> Yeah, but I doubt the port number would make that difference, I'll have to test that once I'm up and running.
[12:53] <manchicken> Especially since Google says 443 is a supported port number.
[12:53] <manchicken> I'm going to be booting into the installer now... hopefully I didn't screw up and download the wrong image again :)
[12:54] <apparle> manchicken: my friend has a non- firewalled internet and for him the default setup (gmail.com 5222) works fine
[13:22] <Tm_T> hmm, I think I'll upgrade my Intrepid to Lucid ...
[13:22] <Tm_T> and then cry
[13:25] <apparle> Tm_T: why
[13:26] <Tm_T> I'm afraid that current Maemo SDK won't work in Intrepid properly
[13:26] <Tm_T> and I'm also afraid that due to scale of the operation, my hardware fails totally during the upgrade
[13:44] <apparle> Tm_T: if I am making a software in Qt, what care should I take so that the code will be portable to maemo very easily
[13:45] <amichair> is there any supported upgrade path to lucid other than from karmic?
[13:45] <Tm_T> amichair: and Hardy, no
[13:45] <Tm_T> those two only
[13:47] <amichair> I heard rumors Hardy isn't either, because it's not an official LTS or something
[13:47] <amichair> but if it is, that's great
[13:47] <Tm_T> amichair: ah, that might be true, I'm not in top of this matter
[13:47] <Quintasan> hnhg
[13:48] <amichair> but a series of sequential updates (+1 each time) should always work, right?
[13:48] <Tm_T> should
[13:48] <amichair> hehe
[13:48] <amichair> famous last words :-)
[13:54] <ScottK> Hardy -> Lucid is not officially supported for Kubuntu, but because it is for Ubuntu, we care about fixing bugs with it.
[13:55] <manchicken> Stupid broadcom card..
[13:56] <apparle> manchicken: so did you bootcamp?
[13:56] <manchicken> Yeah, trying to get it running without wires.
[13:57] <manchicken> Not playing nice with the broadcom.
[13:57] <amichair> ScottK: what does the difference translate into? "we'll fixe'm as we find'em" vs. "we'll test it before release"?
[13:59] <ScottK> amichair: Yes, plus if we find something late it's not an RC issue.
[14:00] <amichair> ScottK: what's an RC issue? release blocker?
[14:00] <ScottK> Yes.
[14:00] <ScottK> Release Critical
[14:01] <amichair> ScottK: oh, got mixed up with Release Candidate :-)
[14:01] <ScottK> Easy enough
[14:01] <ghostcube_maemo> hi peoples
[14:01] <amichair> so that's good enough for me. I'll just wait a while for such issues to be ironed out and then go for it and hope for the best.
[14:02] <Tm_T> do you like to get logs and reports out of my Intrepid -> Lucid upgrade?
[14:02] <ScottK> If it doesn't work, yes.
[14:03] <Tm_T> roger
[14:03] <manchicken> Doesn't «hardware drivers» support broadcom?
[14:04] <ScottK> It does, at least for some broadcom
[14:05] <amichair> ScottK: you know, there aren't many people who capitalize every chat message. I respect that.
[14:05] <manchicken> I'm running on a unibody mbp, it's not showing any drivers at all...
[14:05] <manchicken> I expected some for the nvidia as well as the broadcom.
[14:05] <Tm_T> amichair: I would, but I find chat messages being something more of a flow of text, not actual "writing"
[14:06] <amichair> Tm_T: true, that's why I sometimes do and sometimes don't too.
[14:06] <ScottK> amichair: With a few exceptions when texting my teenagers, I capitalize text messsages on my phone too.
[14:06] <manchicken> As do I.
[14:07] <amichair> But then, I'm beginning some RSI symptoms, so trying to go easy on the shift key. At least it makes for a good excuse ;-)
[14:07]  * ScottK just uses rsibreak
[14:07] <manchicken> Except that I don't have any teenagers... I only have the two-year-old who sends incoherent gibberish text messages.
[14:07] <amichair> ScottK: is that a take-a-break reminder? or something more clever?
[14:08] <ScottK> The former, although it can get pretty aggressive about enforcement.
[14:08] <amichair> manchicken: at what age do kids get a phone nowadays?
[14:08] <Tm_T> like, throw you out of the office
[14:08] <amichair> ScottK: interesting, like locking u out for a while?
[14:08] <manchicken> amichair: They're born with a two-year contract.
[14:08] <ScottK> amichair: Yes, but you can override it.
[14:09] <amichair> manchicken: lol... sad but true :-)
[14:09] <ScottK> manchicken: Enjoy the kid now.  Teenagers are "fun".
[14:10] <manchicken> ScottK: I sure was. heh
[14:11] <amichair> ScottK: trying out rsibreak, thanks for the tip!
[14:11] <ScottK> "There are two options, you can live at home and follow the house rules or you can move out.  You are trying to create a third option where you stay here, but don't have to follow the rules.  That is not going to happen."
[14:12] <ScottK> manchicken: ^^^ recent actual conversation at our house.
[14:13] <amichair> interestingly, the first RSI symptom I ever got was after fixing a software-properties bug which caused it to crash inconsistently after a bunch of mouse clicks (select/deselect entries). At least the bug got fixed...
[14:13] <manchicken> Ah, I remember those conversations with my parents when I was in highschool.
[14:14] <amichair> ScottK: I can't quite put my finger on it, but sounds like you're teaching them to be good programmers somehow...
[14:14] <ScottK> Maybe.
[14:15] <amichair> good for them :-)
[14:17] <amichair> Wow, helluva welcome screen rsibreak has!
[14:18] <amichair> now that's usability in linux...
[14:19] <manchicken> Okay, I don't have the patience for that.
[14:19] <manchicken> Now I remember why I used to have that System76 box.
[14:20] <ScottK> nixternal: Would you please look at bug 540177?  The upstart job for kdm needs a bit more tweaking.
[14:25] <apparle> What's the meaning of "Unknown signature value:  795 " when I run Kopete in Konsole
[14:36] <Quintasan> hmm
[14:37] <Quintasan> I wonder how did I manage to get a memory exception
[14:50] <Quintasan> apachelogger: ping
[15:19] <larsivi_> bug 553979
[15:54] <larsivi_> bug 553994
[15:54] <larsivi_> Riddell: didn't you see this last one?
[15:58] <Daviey> apachelogger: I hear there are some issues with kubuntu & mysql.. Would you be able to raise a thread on ubuntu-devel-discuss@ ML - as a fix could be related to many different projects.
[16:09] <ScottK> Riddell: Are you around for the release meeting?
[16:16] <apparle> Can some one confirm this for me https://bugs.launchpad.net/ubuntu/+source/kopete/+bug/554010 Just reproduce the settings and see if you get the same error
[16:18] <freinhard> apparle: i'll give it a try
[16:19] <freinhard> apparle: which version are you using atm?
[16:19] <apparle> freinhard: 10.04 will all updates
[16:19] <apparle> freinhard: this bug is there since intrepid
[16:20] <apparle> freinhard: I'll be back in 20-30 minutes.. going for dinner
[16:23] <freinhard> apparle: works for me
[16:24] <freinhard> apparle: all checkboxes checked on the connection tab, host talk.google.com, port 443 => works
[16:27] <apachelogger> Quintasan_: pong
[16:27] <apachelogger> JontheEchidna: btw, that notificationhelper missing from live session because casper clears out the kded modules to a bare minimum
[16:27] <apachelogger> to free up as much mem as possible I presume
[16:27] <JontheEchidna> aah
[16:28] <JontheEchidna> any way to blacklist that one from being cleared?
[16:28] <apachelogger> JontheEchidna: just needs to be removed from casper
[16:28] <apachelogger> not sure if that is worth it though ^^
[16:29] <JontheEchidna> Eww, apport took a huge dump of nepomukservicestub crashes all over kdebase-runtime
[16:29] <apachelogger> Daviey: the only issue was that some files went from mysel-server-5.1 to -server-core-5.1, which is a dependency of server anyway
[16:30] <apachelogger> JontheEchidna: can we sue apport?
[16:30] <Daviey> apachelogger: oh, so there is no issue now?
[16:30] <apachelogger> Daviey: nope, all sorted out in ubuntu11 already
[16:30] <ScottK> apachelogger: Up for doing some upstartification?
[16:30] <JontheEchidna> apachelogger: my theory is that since dr. konqi can't pick up those crashes (the service stubs are not KApplications) upstream doesn't know the extent of crashiness that nepomukservicestub has
[16:30] <apachelogger> well, other than mysql being on gigantic PITA :P
[16:30] <ScottK> KDM upstart script needs a bit more work.
[16:31] <Daviey> apachelogger: i hear ya :)
[16:31] <apachelogger> ScottK: last i worked with upstart was like 2 years ago :P
[16:31] <ScottK> OK.
[16:31]  * apachelogger had an upstarted system way before everyone else :P
[16:31] <apachelogger> JontheEchidna: upstream should make the stubs kapps then?
[16:32] <apachelogger> JontheEchidna: or implement own magic... or QA their software :P
[16:32] <JontheEchidna> apachelogger: KApps would make nepomuk ram usage even more pretendous
[16:32] <apachelogger> how so?
[16:33] <apachelogger> a plain kapp cant require that much
[16:33] <apachelogger> + most of it is shared anyway
[16:33] <JontheEchidna> oh right, I'm thinking python
[16:33] <apachelogger> ewww :P
[16:33] <apachelogger> JontheEchidna: bug 553499 .. .how does the not-workingness exhibit?
[16:33] <apachelogger> any idea how that would work anyway?
[16:33] <apachelogger> ...is it broken upstream?
[16:34] <JontheEchidna> tick the "set date and time automatically" checkbox, hit apply, give your password -> fail dialog
[16:34] <JontheEchidna> broken upstream
[16:34] <apachelogger> oh
[16:34] <apachelogger> sweet
[16:34] <JontheEchidna> http://imagebin.ca/view/3RZlCc.html
[16:34] <JontheEchidna> instafail
[16:34] <apachelogger> better than silentfail I guess
[16:35] <JontheEchidna> funny thing is, I can ping pool.ntp.org
[16:35] <freinhard> wow, there's an error message, outstanding!
[16:35] <apachelogger> yeah probably the probing code is broken
[16:35] <apachelogger> or whatever it uses
[16:36] <apachelogger> also, I'd like to raise serious doubt about our accessibility
[16:36] <freinhard> doesn't work for me either
[16:36] <apachelogger> + the tools are crap and shouldnt be deployed IMHO
[16:36] <apachelogger> kmag for example is an abomination
[16:37] <JontheEchidna> kmag's icon is an abomination
[16:37] <JontheEchidna> + we have the zoom plugin in kwin
[16:37] <apachelogger> worse than python, javascript and plasma-netbook all at once
[16:37] <apachelogger> JontheEchidna: I know some people with visual impairment and they all use desktop zoom
[16:37] <apachelogger> kmag is rather useless anyway since it was super laggy last I checked
[16:40] <apachelogger> JontheEchidna: do we have some new minions around?
[16:40] <JontheEchidna> not really
[16:41] <apachelogger> meh
[16:41] <apachelogger> what component sets the the ~/Desktop icon?
[16:43] <apachelogger> those dbusmenu bugs are creepy!
[16:43] <apachelogger> where did the policykit kcm go?
[16:44] <apachelogger> who is up for a bug hunt?
[16:44] <apachelogger> is there anything planed on coordinated bug hunts together with upstream?
[16:44] <JontheEchidna> apachelogger: never got ported to polkit-1
[16:44] <apachelogger> JontheEchidna: that name is silly anyway ;)
[16:44] <JontheEchidna> there's a port in trunk though
[16:44] <apachelogger> policykit was much superior
[16:46] <apachelogger> I propose that apachelogger writes a billion specs for maverick that someone else must implement :P
[16:52]  * vorian will be helping wrt maverick if that's ok
[16:53] <ScottK> It is.
[16:54] <vorian> excellent
[16:54] <apparle> freinhard: so can you help me out getting it to work
[16:58] <apachelogger> Tm_T: ping ping ping ping ping
[16:58] <apachelogger> Tm_T: ping ping ping ping ping ping ping ping ping
[16:58] <apachelogger> no one around :(
[16:59] <Tm_T> apachelogger: yes?
[16:59] <apachelogger> oh
[16:59]  * apachelogger hugs Tm_T :)
[16:59]  * Tm_T hides
[16:59] <apachelogger> Tm_T: do you happen to know whether there is a particular reason kopete doesnt come with show-user-pics-by-default turned on by default?
[17:00] <Tm_T> apachelogger: there shouldn't be any reason for that
[17:00] <apachelogger> https://bugs.kde.org/show_bug.cgi?id=190086
[17:00] <apachelogger> cause it looks like quite the crap without pics
[17:00] <apachelogger> especially with large lists
[17:00] <Tm_T> indeed
[17:01] <Tm_T> "not every service provider support pics" could be an excuse, but bad one for that
[17:01] <apparle> freinhard: are you there
[17:02] <Tm_T> apachelogger: I'll look that closer after I have gone thru backup&upgrade cycles, mind to make that my bug?
[17:02] <Tm_T> (jussi.kekkonen  gmail
[17:02] <Tm_T> )
[17:02]  * apachelogger assigns
[17:03] <Tm_T> danke
[17:04] <apparle> Kopete supports proxy right?
[17:07] <apachelogger> nixternal: can we haz testing feedback btw?
[17:08] <Tm_T> apparle: yes, kde settings atleast
[17:09] <apparle> Tm_T: Well, then I am totally at a dead end... just can't get kopete to work. freinhard says he set the same settings and it worked for him...
[17:10] <Tm_T> apparle: what doesn't work?
[17:11] <apparle> Tm_T: can't login to gtalk
[17:11] <Tm_T> gives any error?
[17:11] <ScottK> Anyone have anything for another kdebase-workspace upload?
[17:12] <apparle> Tm_T: in the 10.04 beta... no error but it just stays offline
[17:12] <Tm_T> apparle: weird
[17:12] <itguru> Hey devs! How you doing, sorry to invade your room, but you guys kicked butt with KDE 4.4 - I gotta tell you something to make you feel good
[17:13] <itguru> i run fedora, and just for kicks, i decided to check if yum could install all the dependencies of kde without screwing up gnome - spent weeks getting eye candy
[17:13] <itguru> It worked and KDE installed clean, and I thought after a few days to give it a shot -- and it blew my mind
[17:14] <itguru> after 2 minutes, all by devs asked my what i had installed, and where could they get it, now we all run a kde desktop
[17:14] <apparle> Tm_T: When I run it through konsole I see many things out of while these two seem significant "Unknown signature value:  795" and "kopete(8436)/kopete (jabber - raw protocol) JabberAccount::slotClientDebugMessage: "Client stream error.""
[17:14] <Tm_T> apparle: hmh, some error, unfortunately I don't know that
[17:15] <apparle> Tm_T: I can connect if I use PSI or Pidgin
[17:15] <itguru> those plasmoid widgets -- and the level of intergration, is a linux admins dream, thank you all :)
[17:17] <Tm_T> Kdevelop 4.0 rc1 tagged
[17:23] <freinhard> apparle: sry no idea how i can help you there. if it's a laptop, try some other network.
[17:23] <apparle> freinhard: can you try one last thing.... plz onnect through a proxy
[17:24] <apparle> freinhard: because I am behind an http proxy
[17:24] <freinhard> aint got no proxy
[17:24] <apachelogger> apparle: talk to you network administrator, that will be much a faster solution
[17:24] <apachelogger> but from above error message it sounds to me as if the firewall does bad things to the SSL stream
[17:24] <apachelogger> who knows what madness gets applied
[17:25] <apachelogger> itguru: :)
[17:25] <apachelogger> Tm_T: is kdevleop as good das qtcreator these days?
[17:26] <apachelogger> because qtcreator is the love
[17:26] <apparle> apachelogger: Tried that..... they don't even allow a simple IRC... and don't even pay attention to the students
[17:26] <Tm_T> apachelogger: I use neither
[17:27] <apparle> apachelogger: if psi and pidgin can... why can't kopete
[17:27] <apparle> apachelogger: I also love qtcreator
[17:27] <apachelogger> maybe psi and pidgin are unsecure :P
[17:28] <apachelogger> clearly there is something wrong with the xmpp data kopete receives
[17:28] <apachelogger> apparle: does the proxy require authentification?
[17:28]  * apachelogger remembers that the MS firewall thingy is rather annoying in this regard
[17:28] <apparle> apachelogger: no
[17:29] <apachelogger> then I really dont know
[17:29] <apachelogger> defenitely not topicy in here anyway :P
[17:30] <apachelogger> not that we are more on topic otherwise ^^
[17:30] <apparle> apachelogger: I tried ubuntuforums, kubuntu, ubuntu+1, so I though I would ask here
[17:32] <apachelogger> well, if the support people do not know help with that kind of problem, then we dont for sure
[17:32] <apachelogger> apparle: last resort would be trying to get hold of the jabber plugin author
[17:33] <apparle> apachelogger: where would I find him
[17:34] <apachelogger> *shrug*
[17:34]  * apachelogger isnt google :P
[17:35] <apachelogger> so
[17:35] <apachelogger> I need minions
[17:36] <apachelogger> ideally packaging minions
[17:36] <apachelogger> hard working minions, with little self-esteem
[17:37] <apachelogger> oh and they should be good uno players!
[17:37] <apachelogger> someone pretty please get me at least 2 of those :S
[17:37] <apparle> :D
[17:37] <ScottK> Ah, a volunteer.
[17:38] <apachelogger> ah
[17:38] <apachelogger> apparle: welcome to the kubuntu minion program
[17:38] <apachelogger> apparle: bug 553489 eagerly awaits your help
[17:39] <apparle> apachelogger: I would seriously love to help... but I have never done any serious development
[17:39] <apachelogger> stuff that needs doing: contact upstream developer and tell them about this pointlessness + master up a patch that set NoDisplay=true in the destkop file
[17:39] <apachelogger> apparle: about time then ;)
[17:40] <ScottK> apparle: apachelogger will teach you everything you need to know.
[17:40] <apparle> No problem... minion ready to learn as long as the softwares required support proxy and work only on port 80 or 443
[17:41] <apachelogger> apparle: for the first part of the solution (contact upstream developer) you really just need a browser and a mail client I would think
[17:41] <apachelogger> maybe kbluetooth installed ;)
[17:42] <apparle> apachelogger: yes I have it
[17:42] <apachelogger> so first step would be to find out whom to contact
[17:42] <apachelogger> usually you would find that in the about dialog of an application
[17:42] <apachelogger> since kbluetooth should sit in your tray you might just want to check that
[17:43] <apparle><EMAIL_ADDRESS>and<EMAIL_ADDRESS>[17:43] <larsivi_> bug 554080
[17:43] <apachelogger> both then
[17:44] <apachelogger> apparle: please write a mail to those two explaining the situation, referfing to the bug, and asking them to resolve this upstream
[17:44] <apachelogger> i.e. add a NoDisplay=true to the desktop file
[17:44] <apparle> alright
[17:44] <apachelogger> as for that NoDisplay... it's behaviour is defined in the freedesktop.org desktop entry spec
[17:44] <apachelogger> kubotu: google desktop entry spec
[17:44] <kubotu> Results for desktop entry spec: 1. Desktop Entry Specification: http://standards.freedesktop.org/desktop-entry-spec/latest/ | 2. Desktop Entry Specification: http://standards.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html | 3. freedesktop.org - Specifications/desktop-entry-spec: http://www.freedesktop.org/wiki/Specifications/desktop-entry-spec
[17:45] <apachelogger> in that thingy the basic concept of desktop files is defined + a set of standard keys is defined
[17:45] <apachelogger> such as NoDisplay
[17:46] <apachelogger> larsivi_: you know that filing this kind of bug in launchpad will result in JontheEchidna or me closing it?
[17:47] <larsivi_> apachelogger: nope - why?
[17:47] <apachelogger> because it is an issue in upstream source, and we are not fixing upstream bugs due to lack of men power
[17:48] <apachelogger> also see https://wiki.kubuntu.org/Kubuntu/Specs/LucidBugTriagePolicy
[17:49] <larsivi_> apachelogger: I may very well be wrong of course, but it appears to me that this started happening unrelated to a plasma-update
[17:49] <apachelogger> yeah
[17:49] <apachelogger> because the crash is not in plasma at all
[17:49] <apachelogger> but in the kde pixmap caching code
[17:50] <larsivi_> ok
[17:50] <apachelogger> larsivi_: is  your partition maybe full?
[17:50] <larsivi_> far from it
[17:50] <apachelogger> larsivi_: also you could try chown -Rv $USER:$USER ~/.kde
[17:51] <apachelogger> since the most recent call within the KDE stack seems to be in a function named writeData it is more than likely that the data could for whatever reason not be writte
[17:51] <apachelogger> n
[17:52] <larsivi_> I ran the chown - will note if I observe the crash again
[17:52] <apachelogger> of chown doesnt work either you could try mv ~/.kde/cache-logos/kpc/ ~/
[17:52] <apachelogger> that will move your current pixmap cache to your home
[17:53] <apachelogger> so it should be recreated completely
[17:54] <larsivi_> apachelogger: anyway - I'm curious about the policy to close bugs that are reported upstream - I thought the point of the nice linking functionality in launchpad was to have an easy way of seeing which bugs affect ubuntu, which you in no way can have if they're only reported upstream
[17:55] <apachelogger> how is that interesting to us?
[17:55] <ScottK> larsivi_: What we need then is people to do all the work of linking and upstreaming.
[17:55] <apachelogger> for most of the bugs it is nothing but maintenance
[17:55] <apachelogger> looking at it every once in a while, closing it once fixed, getting to know that they were fixed...
[17:55] <larsivi_> ScottK: well, in this case I created the upstream bug, and then linked it
[17:56] <apachelogger> the tracking in launchpad is just of no use
[17:56] <ScottK> Right, but in general.
[17:56] <ScottK> Now if it gets fixed, someone will have to remember to close the LP bug when the fix gets uploaded to Ubuntu
[17:57] <larsivi_> ScottK: hmm, right - I thought it would be like someone being notified through LP when an upstream bug was closed such that the fix could be uploaded
[17:57] <larsivi_> if that isn't the way things happens, then I can see that there is little use
[17:57] <ScottK> Except for important bug fixes we normally wait until KDE releases an update
[17:57] <apparle> apachelogger: so should I send them a new .desktop file or should I ask them to add NoDisplay=true
[17:58] <apachelogger> apparle: a modified desktop file, if at all, or even better a diff to the existing one ;)
[17:58] <apachelogger> apparle: up to you
[17:59] <apachelogger> larsivi_: if we had 100 developers that might be a possible work flow ^^
[17:59] <apachelogger> unfortunately we dont :)
[17:59] <apachelogger> larsivi_: but if you are interested in become one...
[17:59] <apparle> apachelogger: how to generate a diff.. just use the one in my menu, creat a new one and then use diff on them?
[17:59]  * apachelogger is currently looking for people to annoy with all his almighty knowledge ;)
[17:59] <apachelogger> apparle: yes, except you shouldnt use the one in your menu
[18:00] <larsivi_> apachelogger, ScottK: ah well, I won't ever do such a thing again :) However, being a project owner elsewhere in open source land (admittedly a much much smaller project), I  do like such reports (although they're not really upstream bugs but more like compiler bugs affecting the project)
[18:00] <apachelogger> apparle: that just made me think of something...
[18:00] <Tm_T> apachelogger: a banana?
[18:00] <apachelogger> no
[18:00] <apparle> :D
[18:00] <apachelogger> apparle: first lecture of the day ... how do i list package content
[18:01] <apachelogger> answer: dpkg -L
[18:01] <apachelogger> e.g. dpkg -L kbluetooth
[18:01] <larsivi_> apachelogger: I ocassionally opens kde source, but I'm afraid I have to many things on my plate too :)
[18:01] <apachelogger> apparle: that could be extended to dpkg -L kbluetooth | grep .desktop
[18:01] <apachelogger> what do you see when you run that cmd?
[18:01] <apparle> apachelogger: just the files with contain ".desktop" in them
[18:02] <apparle> apachelogger: :D
[18:02] <apachelogger> larsivi_: well, should you know someone who wants to feed of my superior intelligence and all ... ;)
[18:02] <apachelogger> apparle: well, how many? :P
[18:02] <apparle> apachelogger: one I think :P
[18:02] <apachelogger> you think? :P
[18:03] <apachelogger> what does the cmd spit out?
[18:03] <larsivi_> apachelogger: haha, I have enough with my own :D
[18:03] <apparle> apachelogger: two
[18:03] <apachelogger> see :P
[18:03] <apachelogger> and that doesnt make you wonder?
[18:03] <lex79> omg bug 554011
[18:03] <apachelogger> /usr/share/applications/* are desktop files that build your menu and /usr/share/autostart/* those that get autostarted ... obviously
[18:04] <apparle> apachelogger: It made me wonder for a moment
[18:04] <apparle> apachelogger: ya I got that
[18:04] <apparle> apachelogger: so I would be using the one in /usr/share/applications
[18:04] <apachelogger> apparle: to answer your original question as to which one to create a diff with ... yes, the one in usr/share/applications
[18:04] <apachelogger> BUT
[18:05] <apachelogger> apparle: my report says that the problem is that kbluetooth is autostarted and thus the entry in the menu is ugly and stupid
[18:05] <larsivi_> apachelogger: well, since you're a qtcreator fan, maybe you like this one then :P bug 554097
[18:05] <apachelogger> apparle: so why would we want to hide it? there doesnt seem to be any use to the menu entry considering the auto start?
[18:06] <larsivi_> apachelogger: here I asked a person working at qt berlin, and he suggested sending the bug to LP ;)
[18:06] <apachelogger> if only danimo was around :S
[18:07] <apachelogger> larsivi_: that sounds more like a bug in the config
[18:07] <larsivi_> apachelogger: I apt-get install'ed it, then tried to start - I've never actually used it
[18:08] <apachelogger> larsivi_: well, you should try with a new user
[18:08] <apachelogger> because it worked here last I used the old stinky 1.3 build :P
[18:09] <apachelogger> JontheEchidna: I am glad to report that now my buttons from knh are all messed up
[18:09] <apachelogger> always these plasma bugs :/
[18:10] <apachelogger> larsivi_: starts just fine here :S
[18:10] <larsivi_> bleh
[18:11] <apparle> why is the krunner responding very slowly.. it takes 4-5 seconds to execute a command
[18:17] <apparle> apachelogger: any specific parameters I should use for diff
[18:17] <apachelogger> apparle: I like diff -urNad
[18:17] <apachelogger> apparle: also, note my questions :P
[18:18] <apparle> apachelogger: its useless so hide it
[18:18] <apachelogger> apparle: so I suppose instead we should ask upstream to drop it
[18:19] <apachelogger> apparle: or maybe add NotShowIn=kde ... so that it at least doesnt show in KDE's menu
[18:19] <apachelogger> that is also a key defined in the desktop entry spec
[18:20] <apparle> apachelogger: no the application is there, so we should not delete it. if it autostarts in gnome, then showing it in gnome is also not useful
[18:20] <apachelogger> apparle: so one should find out if gnome does autostart it
[18:20] <apachelogger> because I dont think gnome autostarts stuff from /usr/share/autostart/
[18:27] <apparle> apachelogger: where does it autostart then? "/etc/xdg/autostart" google says this.. ? but I am not sure
[18:27] <apachelogger> apparle: gnome autostarts from there, kde does too
[18:28] <apachelogger> question is if gnome also autostarts if the file is in /usr/share/autostart
[18:28] <Tm_T> doesn't IIRC
[18:28] <apachelogger> in that case
[18:28] <apachelogger> apparle: not show in kde
[18:28] <apachelogger> i think it is also undesired to have it autostart in gnome
[18:28] <apparle> apachelogger: then NoDisplay is better
[18:29] <apachelogger> no
[18:29] <apachelogger> then you can boot it altogether
[18:29] <apachelogger> nodisplay is good for nothing but if you want to hide something
[18:30] <apachelogger> and since kbluetooth does not autostart in gnome it makes perfect sense that it shows up in its menu
[18:30] <apparle> apachelogger: then... notshowin=kde in the application .desktop and notshownin=gnome in autostart file
[18:30] <apachelogger> apparle: according to Tm_T gnome does not autostart from /usr/share/autostart anyway
[18:32] <apparle> apachelogger: so a simple notshowin=kde is enough
[18:32] <apachelogger> aye
[18:35] <lex79> what about this? bug 553462
[18:36] <lex79> they want kdenetwork-filesharing package installed by default
[18:37] <lex79> btw it's a duplicate of another bug that I can't find in this moment
[18:37] <ScottK> apachelogger: qbzr is fixed now thanks to Andrew Starr-Bochicchio (just accepted it)
[18:41] <apparle> apachelogger: do the location of the files matter for a diff?
[18:43] <larsivi_> apachelogger: apparently the qtcreator bug was a dup - I just had to wait a very long time before it starts, and then it continues to use a lot of CPU for a while (apparently)
[18:44] <apachelogger> ScottK: cool
[18:44] <apachelogger> apparle: no
[18:44] <apachelogger> larsivi_: I am wondering why that is, it starts pretty quickly here
[18:44] <apachelogger> and I am on a netbook ^^
[18:44] <larsivi_> apachelogger: bug 459752
[18:46] <lex79> larsivi_: fabo was working on that for Debian iirc
[18:46] <larsivi_> lex79: well, I'm happy it started at all - it took so long that I thought it wouldn't
[18:47] <lex79> tw is an upstream bug
[18:47] <lex79> *btw
[18:47] <larsivi_> apachelogger: fwiw, it appears to be a first time thingy (or at least the second startup was fast)
[19:24] <apparle> apachelogger: i sent the mail ... anything else
[22:06] <Tm_T> ok, atleast dependency hell is there from intrepid to lucid
[22:12] <lex79> JontheEchidna: have you seen this bug 553462? Can't we add kdenetwork-filesharing into CD? Or is it useless?
[22:13] <JontheEchidna> lex79: It had quite some quality issues last I checked.
[22:13] <JontheEchidna> apachelogger: ^right?
[22:13] <JontheEchidna> your intolerance for crappy s**t  means you'll probably know :P
[22:14] <lex79> :)
[23:16] <DarkwingDuck> Yay! Moved into my new house!
[23:27] <Tm_T> DarkwingDuck: yay! (:)
[23:28] <DarkwingDuck> It's really nice to have my desktop back too
[23:36] <DarkwingDuck> There we go... Timezones updated


[03:31] <smoser> powersj, :-(. odd that i dont see that. i think because you have (or build systemk has) a eth0
[03:31] <smoser> and i do not.
[03:52] <smoser> powersj, fixing and pushing and walking away. thank youo.
[04:45] <powersj> smoser: thank you
[08:04] <Dominique> Hi, is there a 0.7.8 cloud-init for EL7? The one included with EL7 seems a bit old and has some issues.
[10:08] <Odd_Bloke> smoser: Which tests?
[18:28] <harlowja> Dominique i don't think so, but u can just build your own
[18:28] <harlowja> RH i guess will someday get around to it :-P
[18:28] <harlowja> someone from this community perhaps should take over building of that package for them
[18:28] <harlowja> so that its not always behind
[18:29] <harlowja> 0.7.5 seems to be the latest @ https://apps.fedoraproject.org/packages/cloud-init
[23:45] <kalx2> Hi all. Is there a way to disable ssh key injection in cloud-init? This happens automatically on the Ubuntu 14.04 AMI in AWS. Would like to disable it without disabling SSH entirely