[02:39]  * rbelem hugs afiestas 
[02:39] <rbelem> i will get it running this week :-)
[02:40] <ScottK> maco: pg should work fine with quassel.  I think unsupported means if it breaks you get to keep both halves, not that it doesn't work.  I didn't try it though.
[03:33] <maco> ScottK: it was refusing to do the conversion, just bailing. Riddell got it about the qt driver being missing, but even after that it just acted like i had no pre-existing quassel config and tried to get me to set it up all over again. after exiting that and trying again, it said "well you already set it up, nothing to do" and exited :(  so now i just started over with a blank db
[03:52] <ScottK> OK.
[08:14] <shadeslayer> morning :)
[08:17] <Daskreech> hi
[08:32] <apachelogger> ahoyahoy
[08:44] <valorie> omg I just finished watching A Town Called Mercy
[08:45] <valorie> so cool to be able to watch the doctor soon after the episodes are released
[08:45] <valorie> not so cool to have to wait a week to see the next one!
[08:46] <valorie> actually 2 weeks because I'll be in Randa next weekend
[08:52] <Riddell> valorie: life is cruel, surely you could have a special Randa showing?
[08:56]  * apachelogger wonders how valorie does not expect that :O
[08:59] <tsdgeos> agateau: ping
[08:59] <agateau> tsdgeos: pong
[09:00] <tsdgeos> agateau: you knew something about this https://bugs.launchpad.net/ayatana-scrollbar/+bug/1005677 right
[09:00] <tsdgeos> ?
[09:00] <apachelogger> tsdgeos: are you on 12.04?
[09:01] <tsdgeos> apachelogger: no
[09:01]  * apachelogger waves fist :P
[09:01] <agateau> tsdgeos: heard about it yes
[09:02] <agateau> tsdgeos: haven't investigated much yet
[09:02] <tsdgeos> agateau: ah, i thought you might have some idea to were i should look to try to fix it
[09:02] <tsdgeos> apachelogger: why?
[09:03] <agateau> tsdgeos: when I fixed the bug the first time for 12.04, it was caused by ayatana scrollbars returning a null pointer when Qt widget style tried to allocate a gtk scrollbar iirc
[09:03] <apachelogger> have a bug fix for ktuberling that needs verification, just thought you might want to do it, since you reported :P
[09:03] <tsdgeos> apachelogger: sorry
[09:03] <agateau> tsdgeos: I workarounded it by adding a method to gtk to disable ayatana scrollbars, and patching the qt gtk style to call it
[09:04] <tsdgeos> agateau: i see
[09:04] <tsdgeos> well, i'll have a quick look
[09:04] <agateau> tsdgeos: the qt and gtk patches are still there, so it is weird to see this coming back
[09:05] <agateau> tsdgeos: unless the qt gtk style is using gtk3 now, but I don't think it is the case
[09:05] <agateau> tsdgeos: thanks for looking into that
[09:05] <Riddell> the qt gtk style stuff has changed recently
[09:05] <tsdgeos> agateau: well it's just a random combination fact that it appeared in a list of bugs i'm allowed to work while on work-work
[09:06] <agateau> tsdgeos: ok, nice
[09:06] <agateau> Riddell: do you know what changed?
[09:07] <Riddell> stopped using xsettings-gtk and started setting gtk3 directly
[09:07] <Riddell> using apol's kde-config-gtk
[09:10] <agateau> so the qt style is based on gtk3 these days?
[09:13] <Riddell> no, under kubuntu the gtk3 style is oxygen's gtk 3
[09:14] <Riddell> under unity qt style should pick up the gtk one, that's not changed
[09:21] <agateau> what I am saying is qt gtk style has been based on gtk2 until now, but maybe they ported it to gtk3. haven't checked.
[09:22] <agateau> (i am referring to the style used by qt when running on unity)
[09:22] <Riddell> agateau: right, I don't know anything about that one
[09:22] <Riddell> I don't think that's changed
[09:23] <agateau> i don't think either, given the lack of resources working on it
[09:25] <tsdgeos> well
[09:25] <tsdgeos> it's the stle for sure
[09:25] <tsdgeos> if i use a different style it doesn't crash/act weird
[09:26] <tsdgeos> and the warnings are gone
[09:27] <tsdgeos> anyway let's wait for the qt build to finish
[10:04] <tsdgeos> it's the scrollbars
[10:04] <bambee> afiestas: hi,  your video does not work on your blog post (for webaccounts), at least with chrome it does not work
[10:04] <tsdgeos> building gtk to see why the function to show them is being ignored
[10:04] <tsdgeos> now if gtk was as easy as qt to build...
[10:10] <kubotu> ::workspace-bugs:: [1016681] Could not find debug symbol packages for this application. @ https://bugs.launchpad.net/bugs/1016681 (by ill)
[10:14] <afiestas> bambee: there is a link to the video file
[10:14] <afiestas> btw it works in chrome/ium, rekonq and ff here
[10:18] <Riddell> that video is 130MB maybe your host isn't serving it fast enough
[10:18] <Riddell> I had to download it with wget
[10:19] <afiestas> it should be fast enough
[10:20]  * apachelogger recommends using sane formats for web targettign screencasts :P
[10:20]  * apachelogger wonders why he always ends up with too many ts -.-
[10:27] <afiestas> Riddell: actually going only to 1,5Mb
[10:27] <afiestas> maybe my host penalized me because of yesterday traffic (though  I hva no reached the limit)
[10:27] <afiestas> will host on youtube nexttime
[10:29] <tsdgeos> debian packages are the evil
[10:30] <tsdgeos> silly way to make a configure && make ultra difficult
[10:35] <tsdgeos> what did i say
[10:35] <tsdgeos> you can't even apt-get source && dpkg-buildpackage
[10:35] <tsdgeos> sigh
[10:35] <apachelogger> huh?
[10:36] <apachelogger> apt-get build-dep inbetween the two? :P
[10:36] <shadeslayer> apachelogger: you didn't upload https://launchpad.net/~rohangarg/+archive/experimental/+files/kdevelop-custom-buildsystem_1.2.2-0ubuntu1.dsc
[10:36] <shadeslayer> :|
[10:36] <apachelogger> *shrug*
[10:36] <apachelogger> did you mail cj?
[10:36] <shadeslayer> yes
[10:37] <tsdgeos> apachelogger: sure
[10:37] <tsdgeos> apachelogger: interestingly the second time is working
[10:37] <apachelogger> tsdgeos: so what does it fail with?
[10:37] <shadeslayer> apachelogger: "It's not in core or desktop-core, so there's no reason for me to add a
[10:37] <shadeslayer> manual exception.  You should seed it somewhere"
[10:37] <apachelogger> lol
[10:37] <tsdgeos> apachelogger: some useful "debian/rules error 2"
[10:37] <tsdgeos> :D
[10:37] <shadeslayer> heh
[10:37] <apachelogger> probably a crap package
[10:37] <tsdgeos> but as said on a second run with -nc seems to be getting me further along
[10:38] <apachelogger> packages that require no cleaning are crap packages :P
[10:38] <apachelogger> or your system is outofdate
[10:38] <apachelogger> shadeslayer: one way to look at it
[10:38] <apachelogger> shadeslayer: plz be applying for motu
[10:38] <apachelogger> ->shower();
[10:38] <shadeslayer> ...
[10:38] <shadeslayer> apachelogger: exception caught ENOWATER
[10:38] <shadeslayer> :P
[10:38] <apachelogger> what is this?
[10:38] <apachelogger> java?
[10:39] <shadeslayer> it's whatever-the-hell-you-want-it-to-be
[10:39]  * shadeslayer updates FF KDE 
[10:41] <shadeslayer> actually ... maybe later
[11:31] <tsdgeos> agateau: i know why it's happening, unsure how to fix it :D
[11:32] <agateau> tsdgeos: I am all ears!
[11:32] <tsdgeos> agateau: basically the new "overlay-scrollbar" code renames the class so it's no longer called GtkHScrollbar but OsScrollbar
[11:32] <tsdgeos> thus even if the scrollbar is created
[11:33] <tsdgeos> when the gtkstyle tries to access the GtkHScrollbar it crashes because can't find it
[11:33] <Riddell> how's this for stylish? http://starsky.19inch.net/~jr/tmp/KUBUNTU%20POLO%20PROOF.pdf
[11:33] <tsdgeos> the "overlay-scrollbar" code also has some code to refrain itself from loading, but only works if the main binary is linked against qt, not if qt is loaded by some plugin like in vlc, bzr, etc
[11:34] <tsdgeos> i guess the easiest way is making the gtkstyle query for OsScrollbar if GtkHScrollbar failed
[11:34] <tsdgeos> kludge on top of kludge!
[11:34] <agateau> tsdgeos: hold on, you mean the code renames the "normal" GtkHScrollBar?
[11:35] <agateau> cimitan-crazyness
[11:35] <tsdgeos> well, i guess it hijacks the creation of the class at some stage yes
[11:36] <agateau> gobject is clearly too powerful for its own good
[11:36] <tsdgeos> yep
[11:36] <tsdgeos> i'm not sure my suggested solution works
[11:36] <tsdgeos> let's give it a tr
[11:37] <tsdgeos> maybe i'm talking crap :D
[11:37] <agateau> Riddell: nice!
[11:37] <agateau> tsdgeos: one can never know when it comes to gobject :)
[11:41] <mikhas> oh come on now, you can overload the new operator in C++, too ;-)
[11:41] <tsdgeos> yeah, the patch works, though is a bit crap :D
[11:41] <tsdgeos> wonder if i could coherce gtk not to change the name of the scrollbar if it's not using the overlayed one
[11:41] <tsdgeos> taht seems like a better solution
[11:59] <agateau> tsdgeos: have you talk with cimi about the bug and the patch?
[12:23] <BluesKaj> Hey all
[12:25] <Riddell> dantti: how do I test colord-kde?
[12:48] <shadeslayer> Riddell: are you sure the settings.ini in kubuntu-default-settings is even used?
[12:49] <shadeslayer> because I think it'll need a autostart script to automatically link /usr/share/kubuntu-default-settings/settings.ini to ~/.config/gtk-3.0/settings.ini
[12:50] <Riddell> shadeslayer: in startkde  cp -f /usr/share/kubuntu-default-settings/settings.ini $HOME/.config/gtk-3.0/settings.ini
[12:50] <shadeslayer> uh ... ok
[12:51] <shadeslayer> that seems a bit bad
[12:51] <shadeslayer> and should have been done via autostart no?
[12:51] <Riddell> shadeslayer: how bad?
[12:51] <shadeslayer> bad as in ... cannot be reused by derivatives and what not :P
[12:51] <shadeslayer> hm
[12:52] <Riddell> shadeslayer: maybe, we've always patched startkde for this and my changes removed a load of lines compared to 12.04
[12:52] <Riddell> but feel free to change it if you need to
[12:52] <shadeslayer> I'm a bit unsure of what would happen on the first boot though ;)
[12:52] <Riddell> an autostart script is yet another bash process needing started so that's a downside
[12:53] <shadeslayer> and I might have to force a realod of configs somehow
[12:53] <shadeslayer> ( not sure how that'll happen )
[13:18] <tsdgeos> agateau: ok, basically the "old" scrollbar is no longer used, the code you added to qt and gtk is really a noop
[13:18] <agateau> tsdgeos: oh ok
[13:19] <tsdgeos> since he basically hijacks at the gtk level the scrollbar, the "os_scrollbar_new" function gtk used to use to build the new scrollbar is gone
[13:20] <agateau> so, time to apply your hack?
[13:22] <tsdgeos> don't know
[13:22] <tsdgeos> i'd like to talk to cimi
[13:22] <tsdgeos> he's on holiday though
[13:27] <shadeslayer> do you think we can drop http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging/kde-workspace/view/head:/debian/patches/use_dejavu_as_default_font.diff
[13:27] <shadeslayer> since we now use Ubuntu as the default font?
[13:28] <Riddell> shadeslayer: hmm
[13:29] <Riddell> shadeslayer: we don't use it
[13:29] <Riddell> that's a debian patch we disable
[13:29] <shadeslayer> ah ok
[13:29] <shadeslayer> didn't realize it comes from debian
[13:39] <Daskreech> yofel: ping
[13:40] <yofel> pong?
[13:45] <Daskreech> yofel: Just checking what version of muon are you running?
[13:49] <Daskreech> I have 1.4.0 and it has a total UI freeze anytime you cnofirm packages
[14:10] <yofel> Daskreech: also 1.4.0, but works fine. What freezes? The whole desktop or just muon?
[14:14] <Daskreech> yofel: Just Muon. I can install things and monitor them with the cli but as soon as I hit Apply Changes I get a popup asking for the password but the muon window has been locked by then and never unlocks
[14:14] <Daskreech> had it sit for two days
[14:16] <yofel> never happened to me I fear :/
[14:28] <shadeslayer> yofel: do gtk apps use oxygen gtk for you on quantal?
[14:31] <Daskreech> yofel: Bah. Been happening for 3-4 muon updates now I was hoping it was a bug
[14:59] <BluesKaj> Daskreech, too many probs with muon after update/upgrades , not worth the grief :(
[15:00] <apachelogger> http://wstaw.org/m/2012/09/17/plasma-desktopjk2406.png
[15:00] <apachelogger> dragon3 has now more UIs than I have videos -.-
[15:01] <Daskreech> BluesKaj: such as?
[15:01] <Daskreech> Hmm
[15:01] <BluesKaj> blocking updates in dpkg , Daskreech
[15:01] <Daskreech> I remember that URLS with images in them used to open in gwenview. Now Rekonq does it
[15:01] <Daskreech> wonder what happened with that
[15:02] <BluesKaj> and installs with apt-get
[15:02] <Daskreech> BluesKaj: Mine doesn't block updates but it seems to indicate that it does. Checking on it things actually go through
[15:03] <shadeslayer> Daskreech: check system settings > default application
[15:03] <BluesKaj> I normally don't use package mangers for installations , mostly as a reference guide for package info ..synaptic still works for me Daskreech :)
[15:03] <shadeslayer> and look under "Web Browsers"
[15:04] <shadeslayer> you want the setting to be "in an application based on the contents of the url"
[15:04] <Daskreech> shadeslayer: yeah it's rekonq. But URLS that ended in .jpg/.png/gif etc used to open in gwenview. THough that may have been when konqueror was my default browser :-/
[15:05] <shadeslayer> just set it to what I said and watch the magic :P
[15:05] <Daskreech> BluesKaj: :-) I tend to use Apt-get but i was asked my opinion of muon and the discovery center so I've been trying to use those
[15:05] <Daskreech> shadeslayer: ahhhhhh
[15:05] <agateau> Daskreech: embedding Gwenview in a browse is not that much of a good idea anyway because Gwenview does not support progressive loading
[15:05] <Daskreech> astute
[15:05] <Daskreech> agateau: it wasnt embedded
[15:05] <shadeslayer> :)
[15:06] <agateau> Daskreech: it started the separate application? weird
[15:06] <Daskreech> agateau: bleah. ok now it's embedded 
[15:06] <Daskreech> :-p
[15:06] <shadeslayer> wot
[15:06] <shadeslayer> it always started in a different application for me
[15:07] <shadeslayer> as in, clicking apachelogger's link from Quassel starts a KJob which downloads the url and tells gwenview to openit
[15:07] <Daskreech> Yep
[15:08] <agateau> shadeslayer: ha, that's different, i thought you were talking about clicking on links within a web page
[15:08] <shadeslayer> nah
[15:08] <agateau> shadeslayer: Daskreech: this behavior is configured from a kcm module
[15:08] <shadeslayer> though does gwenview offer a gwenviewpart? :P
[15:08] <Daskreech> agateau: no clicking on an external link
[15:08] <Daskreech> shadeslayer: parrently. 
[15:08] <Daskreech> agateau: which shadeslayer just pointed out
[15:08] <agateau> shadeslayer: it does, but it does not support progressive download
[15:09] <shadeslayer> ah ok
[15:09] <agateau> kcmshell4 componentchooser
[15:09] <agateau> then pick "web browser"
[15:09] <Daskreech> agateau: to be honest I don't know why it would. It's probably expecting files from a hard drive
[15:09] <shadeslayer> I just pointed that out :)
[15:10] <agateau> Daskreech: true, either hard drive or lan network shares, that's why I don't want to work on progressive downloads
[15:10] <agateau> Daskreech: pick "in an application based on the contents of the URL" to get gwenview to open when clicking images from quassel
[15:11] <Daskreech> though gwenview crashes on me anytime i load kipi now
[15:11] <agateau> bad kipi
[15:12] <shadeslayer> who wants to try out the new KDevelop for precise?
[15:13] <shadeslayer> https://launchpad.net/~rohangarg/+archive/experimental?field.series_filter=precise < in case anyone wants to have a go at QA
[15:15] <Daskreech> I would love for kipi to be plugin based 
[15:19] <apachelogger> Daskreech: like kipi you mean? :S
[15:19] <shadeslayer> hehe
[15:19] <Daskreech> apachelogger: yes a plugin with plugins :)
[15:19] <apachelogger> actually I wonder how it loads the plugins
[15:20] <Daskreech> Specifically for the slideshow effect that wuld be be great to democratize 
[15:20] <apachelogger> Daskreech: why be it crashing tho?
[15:20] <Daskreech> Dunno
[15:20] <apachelogger> backtrace!
[15:20] <Daskreech> Didn't care enough to check into it. Someone wanted to know if they could lighten a picture from Gwenview
[15:21] <Daskreech> I looked into it and it crashed twice then the person just opened kolourpaint and fixed it so I stopped looking
[15:23] <agateau> apachelogger: gwenview uses KPluginLoader to load kipi plugins
[15:23] <agateau> but the KIPI API is a bit of a mess
[15:23] <apachelogger> ah yes
[15:23] <apachelogger> how does that go kaboom then?
[15:23] <apachelogger> that's a bit curious
[15:24] <apachelogger> but since Daskreech refuses to feed information we shall all forget about it right now
[15:24] <agateau> BC changes between kipi-plugins and kipi?
[15:24] <agateau> right :)
[15:24] <apachelogger> and best never to talk about it anyway, what with plugins for plugins
[15:24] <agateau> s/BC/BIC/
[15:24] <kubotu> agateau: You did something wrong... Try s/you/me/ or tell me "help sed"
[15:24] <apachelogger> agateau: oh, kipi changes BC without changing soname? :P
[15:25] <Daskreech> give me a moment printing some things off then I'll be back here
[15:25] <apachelogger> actually.... I think our safety net ought to catch upstream being sloppy and not bumping versions on api removal
[15:25] <agateau> apachelogger: it should not, but there has been problem like that in the past
[15:27] <Daskreech> Ah the evil printing is complete
[15:27] <Daskreech> as an aside what's going with CUPS?
[15:29] <apachelogger> why?
[15:29] <apachelogger> it's cupsing I suppose
[15:29] <Daskreech> Wasn't it supposed to be "replaced" or augmented by openprinting.org after Apple said they were planning on screwing it up?
[15:30] <Daskreech> gwenview-dbg installing
[15:31] <agateau> Daskreech: note that I am about to uninstall myself from my laptop :)
[15:32] <Daskreech> agateau: Anything that you would like to know?
[15:32] <Riddell> shadeslayer: kdevelop installs and runs
[15:32] <shadeslayer> w00t
[15:32] <shadeslayer> copying to beta backports then
[15:33] <agateau> Daskreech: backtrace and console output should be good enough
[15:34] <Daskreech> Ok configuring then starting gwenview from the command line to try and run a batch tool on my pr0n
[15:34] <agateau> Daskreech: I don't need those details :)
[15:35] <shadeslayer> "Launchpad encountered an internal error during the following operation: copying a package.  It was logged with id OOPS-2d31429dc528354566e978d2f4e15201.  Sorry for the inconvenience."
[15:35] <shadeslayer> yay
[15:35] <Daskreech> agateau: It shall be allll dark and black
[15:45] <Daskreech> agateau && apachelogger: http://paste.kde.org/550838/
[15:45] <Daskreech> The backtrace is empty?
[15:47] <agateau> Daskreech: weird, should not be empty
[15:47] <agateau> (msg on line 19 can be ignored)
[15:48] <Daskreech> QSocketNotifier: Invalid socket 18 and type 'Read', disabling...
[15:48] <Daskreech> QSocketNotifier: Invalid socket 14 and type 'Read', disabling...
[15:48] <Daskreech> are also on the CLI after that
[15:51] <Daskreech> Yep No backtrace
[16:56] <mparillo> Anybody here running Ubuntu One on a daily build? It has been crashing on startup for me for a couple of days. I send the automatic crash report to Launch Pad, and I learn it is a duplicate, but do you know how I can tell which one? Reason I am asking here is that Kubuntu is unsupported.
[17:47] <kubotu> ::qt-bugs:: [1052076] Widgets stop responding when enabling gestures on (evdev) multitouch device @ https://bugs.launchpad.net/bugs/1052076 (by Cédric Dufour)
[18:12] <yofel> shadeslayer: would need a vm to test, my gtk3 setup here is a mess
[18:21] <shadeslayer> yofel: nvm :)
[20:47] <debfx> qt 4.8.3 is building in the experimental ppa
[20:48] <shadeslayer> quantal?
[20:49] <shadeslayer> yeah
[22:21] <mparillo> Anybody remember how the fonts got ugly in the early betas for 12.04? It had to do with Qt supporting Ubuntu Medium Fonts?  Now I read: Dmitry Shachnev (mitya57) wrote 12 hours ago:	 #39
[22:21] <mparillo> In Quantal, ubuntu-font-family-sources *will* ship the Medium version of the font (see http://pad.lv/1048600). Can anybody please re-open the ubuntu-font-family-sources task and nominate/target all tasks to quantal?