[00:25] <Sput> seele: thanks a lot, just have read the summary for now, but it sounds like a very well-made base for us to improve on quassel's usability :)
[00:25] <Sput> will read the full thing tomorrow once I got decent internet access again
[00:48] <JontheEchidna> _Sime: Could I bug you about a crash I've encountered with my python kcm?
[01:00] <ScottK-palm> NCommander:  What's up with my p-a-s changes for kde4bindings?
[01:01] <NCommander> It stopped libqyoto from building on ARM it seems
[01:01] <NCommander> (or being uploaded)
[01:01] <seele> p-a-s?
[01:02] <ScottK-palm> Packages arch specific
[01:03] <ScottK-palm> It's for saying don't build certain packages on specific architectures.
[01:04] <ScottK-palm> NCommander: There's a soyuz bug open right now saying if any binaries a mentioned in p-a-s the entire source package gets skipped.
[01:04] <ScottK-palm> Which is consitent with the hppa build being missing.
[01:04] <NCommander> *winces*
[01:05] <ScottK-palm> consitent/consistent.
[01:05] <ScottK-palm> So I'm skeptical that my p-a-s stuff is affecting only one package.
[01:06] <NCommander> I'll have to look closer at the source of the failure
[01:06] <ScottK-palm> I'll try and have a look though.
[01:07] <ScottK-palm> I need to double check the hppa changes I made in any case.
[01:10] <ScottK-palm> NCommander: If it was a failure to upload error, Soyuz is know to have timing issues and drop binaries every now and then.
[01:11] <NCommander> o_o;
[01:11] <ScottK-palm> I'd ask kiko if he can rescue it.
[01:12] <ScottK-palm> My theory on why Soyuz isn't getting opened has to do with embarassment.
[01:12] <seele> besides kpackagekit and quassel what else was there to review?
[01:12] <ScottK-palm> seele: kvirc? It's the other IRC contender.
[01:16]  * ScottK-palm goes back to pretending to look at the mountains (night time car travel and I'm not driving).
[01:35] <JontheEchidna> _Sime: actually I think I know what's causing the problem. Dunno how to work around/fix it though... Jockey uses a GUI-tookit agnostic backend in another process, relying on the frontend to grab data for populating the UI. Could be funkiness with threads.
[01:35] <JontheEchidna> which cause kcmshell4 to crash
[02:22] <NCommander> Riddell, poke
[05:08] <NCommander> ScottK, ping?
[06:28] <freeflying> NCommander: arounds?
[06:50] <ScottK> NCommander: Pong?
[06:50] <ScottK> Home now.
[07:02] <ScottK> NCommander: Looking here: http://buildd.debian.org/quinn-diff/Packages-arch-specific it looks like my p-a-s changes for kde4bindings/mono on hppa got dropped somewhere.
[09:34] <Arby> JontheEchidna: do you have the code handy that you used to build the kcm module for jockey?
[09:34] <Arby> I need to do system-config-printer-kde at some point
[09:35] <Arby> so I'm looking for examples
[09:35] <Arby> I've got the example code from svn
[09:35] <Arby> but it's not that obvious to me
[10:45] <apachelogger> can anyone reach ftp.kde.org
[11:04] <jussi01> apachelogger: Connection to Server Refused here
[11:14] <apachelogger> jussi01: ok, thx
[11:24] <NCommander> freeflying, for some definitions of around
[12:17] <apachelogger> Riddell: is there a reason kde4.mk enforces the usage of quilt?
[12:19] <NCommander> apachelogger, dislike quilt?
[12:19] <NCommander> apachelogger, and feel like sponsoring more ARM fixes?
[12:32]  * NCommander looks at Riddell or ScottK 
[12:59] <Riddell> apachelogger: not especially, that's just what it's always done
[13:12] <glade88> Does the kdebase-workspace package has the rss dataengine missing?
[13:14] <glade88> plasmoidviewer rssnow -- does not show rss in the list. neither do I have the files /usr/lib/kde4/plasma_engine_rss.so and /usr/share/kde4/services/plasma-dataengine-rss.desktop
[13:14] <apachelogger> NCommander: possibly
[13:14] <NCommander> apachelogger, kdeaccessibity needs sponsoring, and kdeartwork will ...
[13:14] <apachelogger> Riddell: are you fine with making it optional?
[13:15] <apachelogger> Riddell: I think about adding an if condition for the include, that way one just needs to add the build-dep if debian/patches/series is present
[13:16] <apachelogger> NCommander: did you upload accessibility to a ppa and is the patch applied upstream?
[13:17] <NCommander> apachelogger, no, and no. Haven't filed a bug yet
[13:17]  * NCommander isn't having a great amount of luck getting his patches to flow into KDE
[13:17] <apachelogger> you have to poke the people hard enough, bug triage takes way too long
[13:21] <NCommander> apachelogger, care to help?
[13:22] <NCommander> kdeaccessibility is on its way to my PPA
[13:26] <apachelogger> NCommander: will commit the kmag change if it works
[13:26] <NCommander> kmag?
[13:26] <NCommander> oh, the change you had in the repo
[13:33] <apachelogger> hm
[13:34] <apachelogger> NCommander: why does inline qreal clamp not return a qmin anymore?
[13:34] <NCommander> wait what?
[13:34] <apachelogger> -  return qMin(1.0, qMax(0.0, n));
[13:34] <apachelogger> +  return  (1.0, qMax(0.0, double(n)));
[13:34] <apachelogger> patch in accessibility
[13:35] <NCommander> O_o;, crap
[13:35] <NCommander> That's a bug
[13:35] <NCommander> :-)
[13:35]  * NCommander sighs
[13:35] <NCommander> I think I'm slowly loosing my sanity on this porting project
[13:35] <apachelogger> sanity be gone!
[13:36] <NCommander> Uh
[13:36] <NCommander> I'm looking at that patch now
[13:36] <NCommander> It still returns qMin ...
[13:36] <NCommander> -  return qMin(1.0, qMax(0.0, n));
[13:36] <NCommander> +  return qMin(1.0, qMax(0.0, double(n)));
[13:36] <NCommander> That's what I see on accessibility ...
[13:36] <apachelogger> hm
[13:36] <apachelogger> maybe my kate went silly
[13:36]  * NCommander hits apachelogger 
[13:37] <NCommander> don't make me doubt my sanity
[13:37] <apachelogger> hm
[13:37] <apachelogger> funny bug :D
[13:37] <NCommander> Your a KDE developer, fix it :-P
[13:37] <apachelogger> kate rendering is pure magic
[13:37] <NCommander> Qt is pure crap w.r.t. to portability
[13:37] <apachelogger> seriously, I dont think the kate devs even understand it :P
[13:37] <NCommander> Magic crap ;-)
[13:37] <NCommander> write kvim
[13:38]  * apachelogger blames the syntax highlight stuff
[13:38] <apachelogger> NCommander: kate == kvim
[13:38] <NCommander> apachelogger, so it was just a katie bug, and not my sanity?
[13:38] <apachelogger> yes
[13:39] <NCommander> well
[13:39] <NCommander> That's a first.
[14:44] <apachelogger> NCommander: please test the kmag color stuff on arm
[14:44] <NCommander> ??
[14:44] <apachelogger> runtime QA
[14:45] <NCommander> from kdeaccessibility?
[14:45] <apachelogger> yes
[14:45] <NCommander> Your assuming my ARM device has a working X server
[14:45] <apachelogger> oh dear
[14:45] <NCommander> hrm
[14:45] <apachelogger> NCommander: find someone with :P
[14:45]  * NCommander sees if he can just use Xnest
[14:46] <apachelogger> if it works I'll commit the change upstream
[14:46]  * NCommander has no startkde script
[14:46] <apachelogger> -workspace
[14:46] <NCommander> Ok, my ARM box is still doing a build of artwork so when that finishes, I'll test
[14:46] <apachelogger> okies
[15:04] <NCommander> wow
[15:04] <NCommander> Trolltech responded to me on their dbus bug
[15:04] <NCommander> "We're not broken, KDE must change"
[15:04] <NCommander> -_-;
[15:04] <NCommander> *sigh*
[16:37] <DreadKnight> how do i start bluetooth from command line?
[16:39] <ScottK-desktop> Riddell: Have you seen: http://blog.martin-graesslin.com/blog/?p=211 and/or discussed it with bryce?  It'd be really nice to get rid of that problem ...
[16:46] <seele> wow.. MD5 has been broken
[16:46] <seele> http://www.win.tue.nl/hashclash/rogue-ca/
[16:47] <jtechidna> ScottK-desktop: Bryce and Martin have been discussing that directly in an LP bug somewheres
[16:47] <ScottK-desktop> JontheEchidna: Great.  Thanks.
[16:48] <JontheEchidna> last I saw they were asking the patch author his opinion
[16:49] <ScottK-desktop> seele: Interesting.  The theoretical risk has been known for quite some time.  That's the first claim of a practical use I've seen.
[17:41] <vorian> ScottK-desktop: thanks for the sync request
[17:41] <ScottK-desktop> vorian: You're welcome.
[17:42] <vorian> i've been waiting for those folks to fix some licensing issues
[17:42] <Tm_T> hi
[17:42] <vorian> hi
[17:42] <Tm_T> other than me using LPIA arch ?
[17:43] <Tm_T> I noticed that main repos are bit, how would I say, bare here and there
[17:44] <vorian> if memory serves, there was a public domain issue with some of the docs
[17:44] <Tm_T> interesting
[18:53] <Riddell> ScottK-desktop: as far as I caught they want to keep that X patch as it speeds up a lot of things
[18:53] <Riddell> :(
[18:53] <Riddell> and recon that KDE should work around it
[19:10] <apachelogger> Riddell: so we should have kept the old bluez and patched it to work with the intrepid kernel?
[19:11] <apachelogger> somehow I find the attitude flawed TBH
[19:11] <apachelogger> Riddell: what about quilt?
[19:13] <Riddell> apachelogger: alledgedly the old bluez didn't work with current linux
[19:14] <Riddell> that was the rationale for last minute update in intrepid anyway
[19:14] <Riddell> what about quilt?
[19:15] <apachelogger> Riddell: <apachelogger> Riddell: are you fine with making it optional?
 Riddell: I think about adding an if condition for the include, that way one just needs to add the build-dep if debian/patches/series is present
[19:20] <Riddell> apachelogger: if you can get it work then go ahead
[19:20] <apachelogger> aye aye
[19:22] <NCommander> apachelogger or Riddell, feel like sponsoring another ARM portability fix?
[19:22] <NCommander> or ScottK
[19:27] <apachelogger> NCommander: did you test kmag yet?
[19:27] <NCommander> Remember when I said no working X :-P
[19:28]  * apachelogger insists on runtime QA
[19:28] <vorian> :o
[19:28] <NCommander> WHere is the damn startkde script
[19:28] <NCommander> its not in workspace
[19:29] <apachelogger> Riddell, NCommander, vorian: if you got time for a bit of testing http://paste.ubuntu.com:80/96199/
[19:29] <apachelogger> NCommander: kdebase-workspace-bin: /usr/bin/startkde
[19:29] <apachelogger> NCommander: why would you need a complete KDE session anyway?
[19:30] <vorian> apachelogger: sure, as soon as Iget home
[19:30] <apachelogger> vorian: iGet?
[19:30]  * NCommander sees if he can get something to work
[19:31] <vorian> eek, yah, i'm on the phone (i get)
[19:31] <apachelogger> vorian: iPhone?
[19:31] <vorian> of course :p
[19:31] <apachelogger> iGet should be just fine then :P
[19:31] <vorian> hehe
[19:31] <apachelogger> you just had a bit of a case issue
[19:42]  * Arby does the new feature dance
[19:42] <Arby> system-config-printer-kde now does ipp browsing :)
[19:44] <apachelogger> no clue what that might be
[19:44] <apachelogger> *drinking tea*
[19:45] <apachelogger> policykit-kde release coming up \o/
[19:47] <Arby> neither have I really, but it means I can connect to printers on remote machines now :P
[19:48] <Arby> just not using samba
[19:48] <Arby> because setting up shared printers on samba has been a pain
[19:52] <JontheEchidna> <3 print function
[19:55] <ScottK-desktop> Riddell: bluez worked fine for me before it got updated.
[19:58] <ScottK-desktop> NCommander: I see you got a nice mention in Joerg's blog.
[19:58] <NCommander> I did?
[19:58] <NCommander> link?
[20:00] <jpds> NCommander: http://blog.ganneff.de/blog/
[20:00] <NCommander> Well ...
[20:00] <NCommander> Go figure
[20:01] <ScottK-desktop> NCommander: Do you still need some sponsoring?
[20:01] <NCommander> kdeartwork
[20:01] <NCommander> ^ - ScottK-desktop
[20:02] <ScottK-desktop> NCommander: Link?
[20:02] <NCommander> lp:~kubuntu-members/kdeartwork/ubuntu
[20:03]  * ScottK looks
[20:36] <ScottK> NCommander: Kdeartwork uploaded.  Thank you for your contribution to Kubuntu (JontheEchidna too)
[21:13] <ScottK> NCommander: Congratulations.  One more built.  What's next?
[21:14] <NCommander> bluetooth or plasma-addons
[21:14] <ScottK> Well bluetooth is broken anyway.
[21:14] <jussi01> ScottK: any idea of when that might be fixed?
[21:14] <ScottK> Nope.
[21:15] <ScottK> superm1 was helping with it, but I think got distracted.
[21:15]  * jussi01 misses bluetooth
[22:39] <Arby> JontheEchidna: nice work on the jockey kcm module. feel like taking a look at s-c-p-kde :)
[22:39] <Arby> I've made a start but got stuck
[22:39] <Arby> any idea what would cause
[22:39] <Arby> The service 'Printer Configuration' does not provide an interface 'KCModule' with keyword 'system-config-printer-kde/scpk-kcm.py The factory does not support creating components of the specified type
[22:39] <JontheEchidna> Arby: actually I'm stuck with jockey....
[22:39] <Arby> heh :)
[22:39] <Arby> still crashing then?
[22:39] <JontheEchidna> no, I got around that
[22:40] <Arby> cool
[22:40] <JontheEchidna> by crippling the program
[22:40] <Arby> ah
[22:40] <JontheEchidna> but the ui shows up in its own window because I can't set the parent of the ui to the KCModule because it's in another class
[22:41] <Arby> hmm, sounds similar to my problem actually
[22:41] <Arby> if I run scpk-kcm in the source tree the ui loads
[22:41] <Arby> but if I try from system settings I get the above error
[22:41] <JontheEchidna> any console output?
[22:42] <Arby> not from system settings
[22:42] <Arby> kcmshell4 gives
[22:42] <Arby> Loading pykcm.py
[22:42] <Arby> WIdget parent:None
[22:42] <Arby> \o/ Yippie! it kind of works!
[22:42] <Arby> component data: <PyKDE4.kdecore.KComponentData object at 0xb28f5aac>
[22:42] <Arby> Killed
[22:43] <JontheEchidna> and everythings works?
[22:43] <Arby> (I killed it deliberately)
[22:43] <Arby> no, the UI is unresponsive, can't click anything
[22:43] <Arby> window just hangs
[22:43] <JontheEchidna> could you paste your code somewhere nice?
[22:43] <Arby> it loads but nothing more
[22:43] <Arby> yeah
[22:43] <Arby> hang on
[22:44] <JontheEchidna> in my case the misbehavior happens regardless of being in kcmshell or SS
[22:45] <Arby> JontheEchidna: just the PyKcm class http://paste.ubuntu.com/96333/
[22:46] <Arby> the whole program is about 3.5k lines
[22:46] <JontheEchidna> hmm
[22:46] <JontheEchidna> well you won't be needing your own kappliation, systemsettings/kcmshell has that
[22:47] <JontheEchidna> and by the looks of it the actual UI is in the GUI() class?
[22:47] <Arby> yes
[22:47] <JontheEchidna> looks like you're gonna run in to the same problem I am later on then...
[22:48] <Arby> I just copied the main event loop as a starting point
[22:48] <JontheEchidna> it's probably freezing because it's trying to be its own kapplication
[22:48] <JontheEchidna> you can remove lines 27 and 31, that much I know
[22:49] <JontheEchidna> but if its setting up the UI in GUI() I have no clue how you'll be able to set up the UI with the KCModule being the parent
[22:50] <JontheEchidna> and you'll run in to the problem I am running in to. you'll have to tell uic.loadUi to load the .ui file with no parent
[22:50] <JontheEchidna> thus making it a toplevel window
[22:50] <Arby> yeah I see your point
[22:50]  * JontheEchidna is sorta trying to make himself see his point :P
[22:51] <Arby> thanks for the tips
[22:51] <Arby> I think I'll have to poke this some more tomorrow
[22:51] <JontheEchidna> I think I'd try to merge GUI() with PyKcm()
[22:51] <JontheEchidna> since PyKcm is setting up the GUI now
[22:51] <stdin> KMainWindow is very naughty
[22:52] <Arby> that's a huge job, GUI contains a large part of the functionality
[22:52] <Arby> in what way
[22:52] <JontheEchidna> I can't merge the GUI and PyKcm classes because the gui class has jockey's AbstractUI class as a baseclass already
[22:53] <Arby> there's more to this than meets the eye :)
[22:53] <JontheEchidna> and I get a metaclass conflict if I try to make PyKcm a base class of both KCModule and jockey.ui.AbstractUI
[22:53]  * JontheEchidna tears hair out
[22:53]  * Arby gives up for the night
[22:53] <stdin> apparently caused by KMainWindow http://paste.ubuntu.com/96338/
[22:54] <stdin> seeing as using QWidget as the base for my class stops the horrible crash
[22:54] <JontheEchidna> oh yeah, KMainWindow'll do that :P
[22:54] <JontheEchidna> it's especially naughty in pykde
[22:55] <stdin> no, it actually *works* in PyKDE :p
[22:55] <stdin> I can't figure out exactly what's causing the issue there though
[22:56] <stdin> when QObject::event calls qDeleteInEventHandler, it calls it with "this", so where the pointer changed from 0xbf806b98 to 0x06 is a mystery