[00:00] <Riddell> ofirk_: bzr branch lp:~ubiquity-slideshow/ubiquity-slideshow-ubuntu/html
[00:00] <Riddell> edit file
[00:01] <Riddell> bzr commit
[00:01] <Riddell> bzr push lp:~<lp-user-id>/ubiquity-slideshow-ubuntu/kubuntu-logo
[00:01] <Riddell> the bzr push needs an ssh key registered in launchpad
[00:07] <lex79> JontheEchidna: advice for bug 554865 ? :)
[00:10] <Riddell> /usr/share/applications/kde4/cantor_part.desktop is the problem
[00:10] <Riddell> I wonder what the solution is
[00:11] <lex79> I knew the problem... :)
[00:11] <Riddell> that file should be in /usr/share/kde4/services/ I think
[00:11] <Riddell> try moving it there and seeing if everything still works
[00:11] <lex79> ok Riddell
[00:12] <lex79> Riddell: do you have time to upload kdemultimedia?
[00:12] <Riddell> can do
[00:12] <lex79> thanks
[00:13] <Riddell> CMakeLists.txt will want    install( FILES cantor_part.desktop  DESTINATION  ${SERVICES_INSTALL_DIR} )
[00:13] <JontheEchidna> lex79: the .desktop file also needs an entry "Type=Service"
[00:14] <lex79> JontheEchidna: there is already
[00:14] <JontheEchidna> Ah, it's near the bottom. Missed it
[00:16] <lex79> strange, cmakelist is ok but the desktop file goes in the wrong place, bah
[00:17] <Riddell> install( FILES cantor_part.desktop  DESTINATION ${XDG_APPS_INSTALL_DIR} )
[00:17] <Riddell> that's wrong
[00:17] <lex79> omg, I saw it now
[00:18] <lex79> patch ! patch ! :)
[00:29] <ofirk_> Riddell: launchpad says: "You cannot upload to this branch. Members of Ubuntu branches can upload to this branch."
[00:31] <Riddell> ofirk_: that's why you need to upload to a branch under your launchpad id
[00:31] <Riddell> bzr push lp:ofirk/ubiquity-slideshow-ubuntu/kubuntu-logo
[00:32] <Riddell> where ofirk is your launchpad login id
[00:43] <Riddell> ofirk_: or you can just send the image to me another way and I'll upload
[00:57] <ofirk_> Riddell: I sent it to your email
[01:38] <freinhard> hi!
[01:39] <freinhard> that's strange: http://packages.ubuntu.com/lucid/opensync-plugin-syncml
[01:39] <freinhard> libsyncml0 not available?
[01:59] <ScottK> freinhard: See the u-d-a mail about unbuildable binaries being removed.  I suspect that's one.
[02:11] <freinhard> ScottK: no, syncml isn't listet in the 3.apr mail.
[02:14] <ScottK> https://launchpad.net/ubuntu/+source/libopensync-plugin-syncml/0.22-2build1
[02:14] <ScottK> Someone should fix that.
[02:15] <ScottK> It's now libsyncml2 due to a soname transition.
[02:15] <ScottK> freinhard: ^^^
[02:16] <freinhard> sry can't, im not here from tomorrow on
[02:19] <ryanakca> nixternal: The kubuntu logo plymouth theme, if you enter the wrong passphrase for an encrypted the disk, the "Invalid passphrase, options or try again" message appears right over the passphrase input box.
[02:34] <JontheEchidna> whee, 2.5 MiB k3b docs all ready for the next CD \o/
[02:35] <lex79> lol
[02:36] <JontheEchidna> silly users, needing documentation
[02:36] <JontheEchidna> ;)
[02:36] <JontheEchidna> "4. The K3b DCOP Interface" <- This.
[02:36] <lex79> they need docs for burning a cd? :)
[02:37] <JontheEchidna> eww, the docs are KDE3 :(
[02:37] <JontheEchidna> " In this dialog is nothing you can do. Just wait for you computer to finish the session."
[02:37]  * JontheEchidna cries
[02:37] <lex79> it's better split the docs and make it suggests
[02:39]  * JontheEchidna screams in horror and throws his coke can at KHC
[02:40] <ScottK> JontheEchidna: Want to revert that one?
[02:40] <JontheEchidna> ...it's tempting
[02:43] <ScottK> The upload was a technical breach of string freeze, so if it's KDE3 docs, might be just as well to get rid of them.
[02:48] <JontheEchidna> ScottK: dputting a docless package now
[02:48] <ScottK> OK.  I'll have a look when it's up.
[02:50] <ScottK> Is it just me or does clicking on "Details" when kpackagekit is upgrading packages not actually provide any additional details, but just a throbber bar?
[02:51] <amichair> ScottK: I noticed that peculiarity.
[02:52] <ScottK> amichair: Please file a bug at b.k.o.
[02:53] <ScottK> JontheEchidna: Accepted.
[02:53] <JontheEchidna> ScottK: the non-python apt backend for packagekit gives the percentage of the current package being downloaded
[02:54] <ScottK> JontheEchidna: Then it shouldn't be offered if the Python one is in use.
[02:54] <amichair> one less bug on the top 9 list. maybe tomorrow I'll have time for some more.
[02:56] <amichair> JontheEchidna: I only see 8 left.
[02:56] <amichair> (one waiting for merge)
[02:56] <JontheEchidna> ah
[02:57] <ScottK> Nice.
[02:57] <JontheEchidna> neat, that's my bug :)
[02:57] <amichair> your bug?
[02:57] <ScottK> Resize and rotate defaults to keeping your changed setting if you don't reject them.
[02:57] <ScottK> Isn't that exactly backwards.
[02:57] <JontheEchidna> amichair: yeah, I reported bug 540278
[02:58] <amichair> JontheEchidna: oh. I thought u introduced it :-P
[02:58] <amichair> actually, none of the links in the slideshow worked.
[02:58] <ScottK> JontheEchidna: Any chance you could fix that for me?
[02:58] <ScottK> That is just totally wrong.
[02:58] <JontheEchidna> where's resize and rotate?
[02:59] <ScottK> JontheEchidna: Systemsettings "Display"
[02:59] <ScottK> krandrtray (I assume)
[02:59] <ScottK> That one should go upstream too.
[03:00] <JontheEchidna> fail, dbusmenu causes the submenu to go offscreen for krandrtray :/
[03:00] <amichair> JontheEchidna: how do I force the notifier to notice and offer the new updates?
[03:01] <JontheEchidna> amichair: packagekit notices when it feels like. I don't really know how that one works. :(
[03:02] <amichair> JontheEchidna: ok
[03:02] <JontheEchidna> dantti might, but he's not here
[03:02] <amichair> no biggie.
[03:04] <amichair> btw, I think ubiquity has some more serious trouble. still crashes a lot, things moving around, getting stuck...
[03:18] <amichair> ScottK: KDE bug #233221, should u ever need it.
[03:18] <ScottK> amichair: Thanks.
[03:19] <amichair> Sorry I didn't file it earlier - I usually do immediately, but I guess I was either really concentrating on something, or really interrupted by something else :-)
[03:20] <ScottK> No problem.  Thanks for doing it.
[03:21] <amichair> humpfff... 5 AM. Time for a long RSI break.
[03:21] <amichair> g'nite!
[03:25] <ScottK> Good night amichair.
[03:26] <DarkwingDuck> Really? Maverick Meerkat?
[03:28] <ScottK> DarkwingDuck: Yes.  Really.  Queue "Danger Zone".
[03:28] <DarkwingDuck> LOL
[03:28] <DarkwingDuck> Well, now we have a name. Time for us Doc guys to start planning again
[03:29] <DarkwingDuck> kubotu: bug 472668
[03:30] <DarkwingDuck> nixternal: ^^
[03:30] <DarkwingDuck> nixternal: bug 554870
[03:31] <DarkwingDuck> nixternal: 554873
[03:31] <DarkwingDuck> nixternal: bug 554873
[03:32] <DarkwingDuck> nixternal: bug 553458
[03:40] <nixternal> yeah, right now I really don't care about bugs to be honest
[03:41] <nixternal> especially the bugs described here
[03:41] <nixternal> the wrong link can be fixed now
[03:42] <nixternal> seeing as these are really small typos, I say we can probably fix them now...I will look at them a bit more on Monday
[03:42] <nixternal> getting things ready for the Blackhawks game tomorrow
[03:43] <DarkwingDuck> ahhh
[03:43] <DarkwingDuck> got ya. I assigned myself. Should I just go ahead and fix the bug and push it?
[03:43] <DarkwingDuck> Well, no you should.
[03:44] <DarkwingDuck> I don't want to get yelled at for committing after the freeze :D
[03:44] <nixternal> not yet...not until i can check it over more
[03:44] <nixternal> not in the mood this week, especially right now
[03:44] <DarkwingDuck> Okay, let me know. I've assigned myself to them.
[03:44] <nixternal> roger that
[03:45] <nixternal> remind me again on monday, because if we do make changes, pot files need to be regenerated and the package needs to be rebuilt and uploaded
[03:45] <DarkwingDuck> kk
[04:07] <ScottK> JontheEchidna: The display resolution default bugs me enough, I even filed a bug: Bug #554948
[06:48] <ScottK> DarkwingDuck: Does kubuntu docs show any screen shots of changing video resolution?
[08:32] <apachelogger> re adblocking... I think it should be working without the evil GUI changes
[08:32] <apachelogger> but for some reason the SSL certificate of esaylist couldnt be checked appropriately and so one gets that kind of message at startup
[08:33] <apachelogger> so I suppose we should use another list ^^
[08:39] <apachelogger> hmmm
[08:39] <apachelogger> what does everyone think about dumping the current adblock list completely? and leaving the adblock setup in 10.10+ to the user?
[08:40] <apachelogger> now that KDE 4.5 contains a fancy easy to use interface for that
[08:40]  * apachelogger never found it a very good thing to block ads by default
[08:57] <apachelogger> lex79: did you upstream the fix for bug 554865 ?
[08:58] <apachelogger> lex79: same for bug 554011 just different upstream ... in case we didnt do the b0rkage ^^
[08:59] <apachelogger> lex79: cantorpart bug nominated and targetted for lucid final
[09:04] <apachelogger> JontheEchidna: we should work the patch policy part of the lucid packaging to its own policy page and stuff ;)
[09:16] <lex79> apachelogger: I don't have the account to access in kde svn
[09:16] <apachelogger> lex79: reviewboard.kde.org
[09:17] <apachelogger> + mail
[09:17] <apachelogger> + irc
[09:17] <apachelogger> + forum
[09:17] <apachelogger> + bko
[09:17] <apachelogger> ...
[09:17] <apachelogger> plenty of choices ;)
[09:17] <lex79> ok
[09:17] <apachelogger> lex79: the patch policy suggest that upstream shall be consulted about the patch, not that one needs to commit it directly :)
[09:18] <apachelogger> in fact it does currently not even imply that one should get it into upstream first and then create a patch of the code included in upstream, which IMHO is a perferred work flow since upstream maintainers usually add some special extra that makes the feature faster or something
[09:19] <lex79> right
[09:19] <apachelogger> bug 553462 is a duplicate of something, i dont know what though ^^
[09:19] <apachelogger> there are like a billion reports regarding filesharing
[09:20] <apachelogger> all saying eventually the same
[09:20] <apachelogger> and all not belonging in the bug tracker to begin with :(
[09:20] <lex79> apachelogger: they want kdenetwork-filesharing into cd I suppose
[09:20] <apachelogger> oh, that bug I can close then
[09:21] <lex79> apachelogger: did you add that package into cd? lol
[09:26]  * lex79 goes out of the home, bbl
[09:34] <apachelogger> lex79: no, adding it is a no-brainer since it is worth nothing without the appropriate server packages, and those shouldnt be on the CD but installed on-demand IMHO
[09:35] <apachelogger> either way the stack is mediocre, so at best it would just put the issues out in the public
[09:39] <amichair> Riddell: How do you recreate bug #540922  ?
[09:39] <apachelogger> ScottK: bug 553541 stable you say? :P
[09:53] <apparle> guys... I thought of taking part in GSoC this year under kubuntu.... but figured out that would be too much for me.... so what all should I learn by next year so as to take part as well as contribute to kubuntu development
[11:21] <Riddell> amichair: I just did an install in oem mode and british english locale
[11:22] <amichair> Riddell: us english probably shouldn't make a difference... couldn't recreate it
[11:23] <amichair> not that I managed to complete an installation... it's full of bugs
[11:23] <amichair> but different ones
[11:23] <Riddell> hopefully it's fixed itself then
[11:23] <Riddell> I saw you reported a crash
[11:23] <amichair> the 4th (different) one I've seen this week
[11:24] <amichair> and I see a few gui ones too...
[11:24] <amichair> bugs tend to cluster
[11:24] <amichair> it would be a good idea to give ubiquity a good triage/test/fix spree before release
[11:35] <apachelogger> hah
[11:35] <apachelogger> openoffice is oracleified
[11:36]  * apachelogger finds that groofy
[11:36] <apachelogger> even though the orangish background and the red logo somehow make an agressive combiniation
[11:56] <jussi01> apachelogger: hrm?
[11:58] <apachelogger> splash screen
[12:01] <jussi01> ooohh
[12:03] <apachelogger> oh man
[12:03] <apachelogger> it is so sad when reviewers dont get their facts straight
[12:03] <apachelogger> apparently Kubuntu 10.04 doesnt use hal
[12:04] <apachelogger> we now have a better hardware abstraction layer with better hardware support and stuff
[12:04] <apachelogger> ...
[12:04] <apachelogger> *sigh*
[12:41] <ejat> apachelogger: :)
[13:45] <markey> there is a lot of interest from KDE users in getting Phonon-VLC. maybe you could consider to offer a package for Lucid?
[13:45] <markey> it would require libVLC 1.1, and Phonon-VLC from Git Master
[13:46] <markey> it's not perfect yet, but already very stable
[13:46] <markey> (has not crashed once for me yet, and xine crashes all the time with HTTP)
[13:48] <JontheEchidna> I doubt that the vlc maintainers would spring for a prerelease version of vlc in an LTS
[13:51] <markey> JontheEchidna: true, but maybe a PPA could be an option?
[13:52] <JontheEchidna> that sounds like the best option
[13:52] <markey> :)
[15:28] <ghostcube_maemo> is there an quassel for maemo?
[15:51] <jussi01> ghostcube_maemo: there was a build around....
[15:51] <ghostcube_maemo> jussi01: thx will have a look
[17:22] <ScottK> "We're pleased to announce the launch of the Groups Advisory Board ..." <--- There should really be a Freenode spam opt out.
[17:23] <nigelb> that seems familiar
[17:31] <apachelogger> and always someone else is spamming
[17:34] <apachelogger> JontheEchidna: how is bug 352687 a bug in workspace?
[17:35] <JontheEchidna> It's talking about the "apply colors to non-KDE apps" checkbox in the colors kcm
[17:35] <JontheEchidna> kcm-gtk doesn't touch colors
[17:35] <apachelogger> I thought it had some color option
[17:35] <apachelogger> but oh well
[17:36] <apachelogger> JontheEchidna: close -> upstream I suggest
[17:40] <apachelogger> also I am not exactly sure how this relates to the kde creaed gtkrc anyway
[17:40] <apachelogger> since clearly the clearlooks stuff is referncing some symbol that does not exist
[17:47]  * JontheEchidna just found a memleak in his code caused by him not deleting his Privat class :x
[17:49] <apachelogger> those things happen
[17:53] <yuriy> wow the OO.o splash screen says oracle now, feels so weird
[18:18] <ScottK> JontheEchidna or apachelogger: I did some detective work on Bug #554948, but now it needs someone who understands the code better than I do.  Would you please take a look?
[18:43] <apachelogger> ScottK, JontheEchidna: from a quick look at the constructor code I would suspect that kdialog's setDefaultButton interface is bugged
[18:48] <apachelogger> ScottK: also, is it just here, or does the krandrtray revert properly while the kcm does not?
[18:54] <lex79> apachelogger: krandrtray works fine here, revert is ok
[18:55] <lex79> kcm doesn't
[18:57] <apachelogger> ewww
[18:57] <apachelogger> tabs
[18:57] <apachelogger> lex79: thanks for testing
[18:57] <lex79> np
[19:00] <ScottK> apachelogger: Would you please mark that in the bug.
[19:04] <apachelogger> I suppose so
[19:04] <apachelogger> also
[19:05] <apachelogger> if dbusmenu is not going to be fixed soonish I will take my laser screwdriver and screw every single patch regarding it towards hell
[19:05]  * apachelogger is getting annoyed majorly by that crap
[19:07] <apachelogger> intersting
[19:07] <ScottK> Since krandrtray works, if we don't get the kcm sorted, maybe we can just patch the kcm away with a release note to use krandrtray.
[19:07] <Nightrose> is anyone else seeing the kopete systray menu flickering since 4.2.4 update?
[19:08] <ScottK> Still on Jaunty?
[19:08] <Nightrose> yes
[19:08] <apachelogger> Nightrose: that is dbusmenu
[19:08] <Nightrose> eh sorry
[19:08] <Nightrose> 4.4.2
[19:08] <ScottK> I just finished upgrading the last Jaunty box to Karmic here about two hours ago, so I can't check.
[19:08] <apachelogger> same goes for amarok
[19:08] <apachelogger> and krandrtray
[19:08] <apachelogger> broken icons in amarok and kopete also come from dbusmeu
[19:08] <Nightrose> ScottK: sorry - getting confused with all the names and numbers ;-)
[19:08] <Nightrose> jaunty with 4.4.2
[19:09] <apachelogger> the fact that kopete never ever loads its menu on first try is also dbusmenu
[19:09] <Nightrose> apachelogger: meh :(
[19:09] <apachelogger> the fact that loading amaroks menu is ...
[19:09] <apachelogger> also dbusmenu \o/
[19:09] <Nightrose> why is that only happening with 4.4.2?
[19:09] <apachelogger> hence my annoyance
[19:09] <Nightrose> didn't happen in 4.4.1
[19:09] <Nightrose> i see
[19:09] <apachelogger> Nightrose: could also be some intermediate change in dbusmenu or some of its stack
[19:09] <ScottK> Probably agateau needs to fix his patch.
[19:10] <Nightrose> k
[19:10]  * Nightrose will wait it out then
[19:10] <Nightrose> it's a bit annoying as one can't click anything for a while in the menu
[20:17] <apachelogger> Computer says ... "NO"
[20:25] <apachelogger> the code style in krandr is rather scary
[20:31]  * apachelogger finds krandr itself rather scary
[20:31] <apachelogger> and confusing
[20:32] <apachelogger> the reason it works via krandrtray is that it uses a completely different approach it seems, krandrtray controls outputs, while the kcm controls screens
[20:32] <apachelogger> which probably makes sense to a certain degree
[20:32] <apachelogger> the the reverting logic in the kcm is apparently broken doesnt make sense though ;)
[20:32] <apachelogger> ScottK: IMHO this should be upstreamed
[20:33] <ScottK> apachelogger: I agree.  I was just hoping one of you code Ninjas could fix it first.
[20:33] <apachelogger> way too complex code base IMHO
[20:33] <apachelogger> + there is more breakage anyway
[20:33] <apachelogger> config restoring doesnt work at all IIRC
[20:34]  * apachelogger doesnt wanna hack with that code style ^^
[20:35] <apachelogger> oh oh oh, maybe i understand...
[20:35] <apachelogger> one screen can have multiple outputs
[20:35] <apachelogger> I am not sure what an output is though
[20:36] <apachelogger> and why krandrtray would set the resolution on a per-output basis
[20:38] <apachelogger> omg there is even a display entity ^^
[20:39] <apachelogger> hm
[20:40] <apachelogger> I actually think i know why the kcm is not working
[20:40] <apachelogger> there is a whole bunch of commented out code that is as far as I understand responsible for altering the output objects
[20:40] <apachelogger> that said, it is also responsible to set the information necessary to reset the outputs
[20:41] <apachelogger> which is exactly the part that is commented out
[20:41] <DarkwingDuck> Happy Easter to all
[20:41]  * apachelogger notes that it is also VERY difficult to read code on a netbook screen -.-
[20:41] <apachelogger> DarkwingDuck: happy easter to you too :)
[20:42] <DarkwingDuck> apachelogger: how are things?
[20:47] <apachelogger> DarkwingDuck: ScottK mad me read ugly code, which makes me think that he supports me in my madness ^^
[20:48] <DarkwingDuck> I think I can dig up some old PERL code for you
[20:49] <apachelogger> PERL!!!
[20:50] <DarkwingDuck> :D
[20:54] <Sput> ♥ Perl ♥
[20:56] <apachelogger> Sput: go make proper kde emoticon support :P
[20:56] <apachelogger> ohhh
[20:56] <apachelogger> kcmshell(14365) RandROutput::tryCrtc: Failed to change output "LVDS1" to CRTC 64
[20:57] <apachelogger> kcmshell(14365) RandROutput::tryCrtc:    Switching back to old CRTC 64
[20:57] <apachelogger> that does look weird, doenst it ^^
[20:59] <apachelogger> ah
[20:59] <apachelogger> I dont get that thing
[20:59]  * apachelogger closes gdb before something bad happens
[20:59] <DarkwingDuck> :D
[20:59] <DarkwingDuck> come one... you broke akonadi for me to fix it :P
[21:00] <apachelogger> hm
[21:00] <apachelogger> kcmshell(14365) RandRCrtc::applyProposed:        Proposed CRTC rect: QRect(0,0 0x0)
[21:00] <apachelogger> I blame the config stuff
[21:00] <apachelogger> ScottK: eventually that is all because the config stuff is busted
[21:00] <DarkwingDuck> aka it's your fault
[21:00] <apachelogger> well, not the button focus
[21:00] <apachelogger> I am not sure where that comes from though
[21:01] <apachelogger> DarkwingDuck: excluded from the rule is code that uses ugly style :P
[21:01] <apachelogger> and that is code with ugly style
[21:01] <DarkwingDuck> ahh, that's your scape-goat?
[21:02] <apachelogger> and patches!
[21:03] <DarkwingDuck> Okay, I really think I need to take some c++ courses.
[21:03] <DarkwingDuck> Or something to learn
[21:14] <Quintasan> apachelogger: I can't get KOffice to build, it fails to find libkexiutils.so.6. I'm sure that it is inside kexi.install file but somehow it fails each time -> http://pastebin.ca/1856852
[21:15] <apachelogger> Quintasan: Note: libraries are not searched in other binary packages that do not have any shlibs or symbols file.
[21:15] <Quintasan> @_@
[21:15] <Quintasan> apachelogger: so kexi libs should actually go to koffice-libs.install>
[21:15] <Quintasan> ?
[21:16] <apachelogger> you should know that :P
[21:16] <apachelogger> it is possible
[21:16] <apachelogger> and would solve the issue
[21:16] <Quintasan> what about those shlibs or symbols file?
[21:16] <apachelogger> but what the note there says is that other packages must be processed before koffice-libs so that it can find the others
[21:17] <ScottK> apachelogger: Would you please some up your krandrtray/kcm findings in the bug so I can upstream it with maximum informaiton.
[21:18] <apachelogger> ScottK: actually I didnt find out anything useful
[21:20] <Quintasan> apachelogger: ^^
[21:20] <apachelogger> ScottK: all I can say that it is one messy code
[21:21] <Quintasan> DarkwingDuck: lern python if you want to troll apachelogger
[21:21] <apachelogger> and that the issue is probably somewhere in the actual restoring portion of thecode
[21:21] <Quintasan> apachelogger luvs python
[21:21] <ScottK> OK.
[21:22] <apachelogger> here it however sent the approiate signals ... so it actually noticed that I cancled/timed out
[21:22] <apachelogger> it just did fail to revert back
[21:22] <apachelogger> and that is IMHO because of the unified approach to doing this
[21:23]  * apachelogger thinks about getting home tomorrow
[21:23] <apachelogger> I am even less useful on a netbook :P
[21:23] <DarkwingDuck> :P
[21:25] <Quintasan> apachelogger: you should feel like you were poked with a stick very moment ago, what about those shlibs files?
[21:38] <apachelogger> Quintasan: post0r your debian dir
[21:39] <AzureDragon> Hello, I'm a student considering applying for the Google Summer of Code. For one of the Kubuntu-related projects I mean. I thought I'd come and say hi. :D
[21:41] <Quintasan> apachelogger: I copy pasted the libs from kexi.install to koffice-libs.install and it worked, but here, anyways -> http://dl.dropbox.com/u/69524/koffice_2.1.81-0ubuntu1.debian.tar.gz
[21:42] <apachelogger> mh mh
[21:43] <apachelogger> Quintasan: must go to koffice-libs because kexi depends koffice-libs, if they are in kexi then ko-libs depends kexi and kexi depends ko-libs
[21:43] <apachelogger> hi AzureDragon
[21:43] <AzureDragon> apachelogger: hi
[21:43] <Quintasan> awesome
[21:44] <Quintasan> AzureDragon: \o
[21:44] <apachelogger> Quintasan: on the other hand...
[21:45] <apachelogger> Quintasan: something might be in ko-libs that does not belong there to begin with :P
[21:45] <apachelogger> and that is the root of all this evil
[21:46] <AzureDragon> Hey I was looking at the KPackageKit project proposal.., Does Kubuntu use the kPackageKit source from the KDE SVN? Or a modified version for Kubuntu?
[21:51] <JontheEchidna> AzureDragon: It's the same as what's in kdesvn, with a few patches to integrate things such as our sources.list editor
[21:52] <JontheEchidna> Though we are using KPK 0.5 rather than 0.6, since 0.6 is an API/ABI unstable version at the moment
[21:52] <Quintasan> AzureDragon: if you have access to lucid machine running lucid I'm sure you can do apt-get source kpackagekit and check things out
[21:52] <Quintasan> lucid machine running lucid :O
[21:52] <Quintasan> awesome error is awesome
[21:53] <AzureDragon> Quintasan: my main desktop is running Lucid. :)
[21:53] <Quintasan> AzureDragon: fabulous, so grab the source already and start hacking :P
[21:55] <AzureDragon> Quintasan: That was something else I was gonna ask. Is knowledge of Qt/C++ a requirement for doing a project like that one in GsoC? I haven't used ether (that being said, I do know how to program, and I am willing to learn as fast as necessary).
[21:56] <Quintasan> AzureDragon: I bet C++ and Qt will be required.
[21:56] <Quintasan> After all KDE is using Qt framework so...
[21:56] <Quintasan> :P
[21:57] <Quintasan> But hey, cpp + qt = magic, you can work on killer apps like Digikam or Choqok
[21:57] <AzureDragon> I might not stand much of a chance of getting in then. =O
[21:58] <Quintasan> I'm just learning on my own pace, I have school, social life (yeah, sometimes it happens  :D) so I'd rather not spent ALL my time on cpp :P
[21:59] <Quintasan> at my own pace*
[21:59] <AzureDragon> =)
[22:02] <AzureDragon> Well, if no-one ends up doing a GsoC project involveing KPackageKit, I may try to controbute over the summer anyhow. =)
[22:40] <amichair> Is there a GUI expert in the house? Or someone familiar with ubiquity?
[22:42] <amichair> or anyone who knows the reason behind the size of the progressbar? http://imagebin.ca/view/GGeqBQ.html
[22:42] <Quintasan> amichair: I think for GUI things you can ask seele
[22:44] <amichair> seele: ^^ any thoughts on this?
[22:47] <DarkwingDuck> woah...
[22:50] <rgreening> nixternal: could yo ulook into this bug report? bug 555349
[22:53] <larsivi> have anyone seen the plymouth theme with a radeon HD card?
[22:53] <larsivi> I've yet to see it at least :P
[23:00] <DarkwingDuck> I can't get it to work on either of my computers... Intel card and Nvidea card
[23:02] <DarkwingDuck> Well, I'm finally setting up filters for my email
[23:33] <seele> amichair: wow.. how did you get the progress bar to do 59% at the first step? did you go backwards after getting so far?
[23:33] <seele> amichair: i think the point is to show you how far you are through the configuration process, although the navigation on the left hand side sortof do that for you already
[23:34] <seele> instead of percentage maybe it should say step 9 of 15 complete or something
[23:34] <amichair> seele: oh not exactly - I just played around with it to get a snapshot
[23:34] <amichair> it's not the overall progress, it's the progress of individual little steps along the way
[23:35] <seele> the combination of all the steps overall, no?
[23:35] <amichair> here's another phase: http://imagebin.ca/view/CQ37320D.html
[23:35] <Riddell> no that's the progress of loading the new step
[23:35] <amichair> e.g., if u click 'update this installer', the progressbar appears and goes from empty to full
[23:35] <Riddell> amichair: what's the problem?
[23:35] <seele> oooooh
[23:36] <seele> is that the downloading updates thing?
[23:36] <amichair> if it updates from the timeserver, it appears and goes again. it disappears in between
[23:36] <Riddell> no, it's a progress bar while each page is loading
[23:36] <Riddell> it's all shtylman's doing
[23:36] <seele> oh, then i have no idea
[23:36] <seele> why would you need to know the status of each page loading?
[23:37] <seele> shouldnt it be rendering in a few miliseconds?
[23:37] <Riddell> just something to look at, else it's unresponsive for several seconds
[23:37] <amichair> Riddell: the problem is both the bug in the last link above
[23:37] <Riddell> can take 10 seconds to load those pages, debconf isn't fast
[23:37] <Riddell> amichair: file a bug, assign to shtylman
[23:37] <seele> then the loading progress should be in the middle of the page that is loading not up in the corner
[23:38] <amichair> which I can fix by making it take up the full width - it's just that it's so unusual, I assume there's some reason behind it...
[23:38] <seele> i hadnt noticed it.. id idnt realise what hta twas for, heh
[23:38] <Riddell> no paticular reason, he just replaced the normal progress bar dialogue with that new progress bar one day, caused a few coding headaches along the way
[23:39] <amichair> seele: It's not exactly the page loading progress. it's more like sub-tasks in between that aren't instantanious provide the progress so the user will know why it's 'stuck'
[23:40]  * daskreech prefers the loading in the corner like as web page
[23:40] <amichair> now that I got the screenshot, I also notice the midget skip button...
[23:41] <DarkwingDuck> hmmm, this is interesting... In Kmail when I move a message to another folder it makes a blank unknown message in the inbox... Anyone know why?
[23:41] <amichair> daskreech: a progressbar is more informative, if percentage info is calculable... and it also says what it's doing (well not in the first screenshot, but in some of them)
[23:41] <daskreech> amichair: That was in response to seele saying the progress should be in the middle of the page
[23:43] <amichair> seele: So, I can't make it full width either (because it bumps into the title text) - so just enlarge it more to the left?
[23:44] <amichair> daskreech: ah, ok. In this case it doesn't replace the page content anyway, so it will stay on top, I guess.
[23:45] <amichair> Riddell: on a related note, there's the other progressbar, of actual installation progress - You and I both opened bugs on the wierd 'skip' button that appears occasionally at the bottom and messes up the layout too
[23:45] <amichair> Riddell: what does that 'skip' do anyway? when I tried clicking it, the whole installer disappeared.
[23:46] <seele> how long does it take to load a page? why not use the little spinner instead of a progress bar
[23:46] <Riddell> yes, could be a papercut that
[23:46] <Riddell> seele: 3 to 10 seconds I'd guess
[23:46] <seele> i dont see what value is provided by showing a straight bar with a percentage.. especailly for every page
[23:46] <seele> geez that is a long freaking time
[23:47] <seele> is that on average/slower systems? i dont remember it taking that long for me
[23:47] <amichair> seele: again, it's not exactly a page load. It's tasks that need to be performed in between. downloading installer updates, getting time from timeserver, and some other stuff. the text on the progress changes accordingly too.
[23:48] <Riddell> well 10 seconds for the partitoner page when you have several disks
[23:48] <seele> why are the installer updates being downloaded between each page?
[23:48] <Riddell> they aren't
[23:48] <amichair> yeah, that too - 'detecting filesystems' or whatever it says... those kinds of tasks
[23:49] <amichair> the updates are if u click 'update this installer' in welcome page. it doesn't actually go to a different page, just does it's thing, and when it's finished, the 'update' link disappears.
[23:49] <seele> whatever piece of information is missing , that ui block should be replaced with the progress indicator with a label that says what it is doing
[23:50] <amichair> I actually opened a bug on that too, I think it should be part of the wizard process - maybe a checkbox for updating, followed by a 'next'.
[23:50] <seele> i still think a spinner is better, the percentage bar isn't telling me anything because the procedures are micro steps
[23:50] <seele> if there is only one step -- e.g. getting the time from the timeserver -- all the steps inbetween dont matter to me so i dont need to know the progress. only that it is doing something
[23:50] <amichair> seele: the first screenshot indeed doesn't say what it's doing - that's a bug. other tasks (like the second image) do
[23:53] <amichair> Here's how it looks when updating installer: http://imagebin.ca/view/mT3BikG.html
[23:53] <seele> yeah, i dunno. how much can we change now anyway? it's my fault for not paying attention to it earlier
[23:55] <ScottK> Since it's post-U/I freeze you'd need to get nixternal to bless any changes and update screenshots.
[23:56] <seele> after convincing shtylman that they should be done
[23:56] <seele> i fail