[06:13] Riddell: Good Morning jonathan, indeed we finished off the rest of the Haggis. Will try to catch up with you a little later today. [06:14] Riddell: I'm at my desk all day today, give me a nudge when your about. [06:44] Good luck guys, with the KF5 porting and what not. [06:44] Looks like a hurdle. [06:47] not exactly [06:47] there'll be loads of spluts [06:47] *splits [06:47] so that's going to be a PITA to manage [07:17] I read somewhere how the splitting might make it more convinent for devs to come and work on specific modules [07:17] but how the versioning of KDE altogether wouldn't change. [07:17] how is that working out? [07:19] true and true [07:19] well ... the same as it works out right now? [07:20] you release the SC together [07:20] all components follow the release cycle etc [07:24] hm [07:25] so just between you and me (and everyone else here, haha) [07:25] would we ever see a KDE 5.0? [07:29] jackyalcine: heh, there's no KDE 5.0 [07:29] meh versions [07:29] there's KDE Frameworks 5 [07:30] the branding is getting mighty confusing now [07:30] for eg. is there a difference between KDE SC and KDE Frameworks? [07:48] yeah [07:48] that's part of it [07:48] is there any idea on how something like this would be patched up? [07:48] wonder if Blue got something [07:53] patched up? [07:55] whut? [08:08] lol sorry [08:09] Like how would the (potential) branding issue be resolved (if it becomes too much of a problem). [08:09] To be honest, time-related releases would be awesome. but it'd be weird jumping from KDE 4 to KDE 13 lol [08:13] heh [08:13] well ... I don't know myself [08:13] I know that KDE Frameworks is a set of modules [08:13] so you can add a framework module ontop of Qt to get extra functionality [08:13] but I don't know how it relates to KDE SC [08:14] and as for KDE, after the branding change, it will always refer to the community [08:18] that's the upside [08:18] thanks for saturating my brain, shadeslayer [08:18] :) [08:18] glad to :P [08:19] I'm reasonably certain that someone here can explain KDE SC vs FF if you stick around [08:19] everyone is sleeping probably [08:19] shadeslayer: FF? [08:19] sleep? [08:19] oh sorry [08:19] Frameworks Five [08:19] FF [08:19] ah not final fantasy [08:20] not Firefox either [08:20] Firefox is Fx [08:20] oic [08:20] atleast that's how their FAQ said some years ago (: [08:21] anyway, frameworks are technology you build on your user level software, for example KDE sc [08:21] hm, I thought it was the other way around [08:21] KDE SC builds ontop of FF [08:22] oh wait [08:22] that's what you said :P [08:23] lol I was thinking Fantastic Four [08:23] Funky Funk [08:23] KDE should name a release : KDE Funky Funk [08:23] and go all retro [08:23] let's redo KDE 2 ? [08:24] oh wait that's almost what some people are demanding on certain development channels in time to time [08:24] I have a Kubuntu 8.04 CD lying around somewhere [08:24] * shadeslayer rages at ubuntu [08:24] shadeslayer: I should have Ubuntu cds all the way from 5.04 if not 4.10 too [08:25] it cannot run in a VM with 2GB of memory [08:25] huh [08:30] Tm_T: http://i.imgur.com/A5h34hR.jpg [09:21] good morning [09:30] shadeslayer: that looks more like llvmpipe not working right [09:30] last time I tried it in KVM it did work, but was slow as hell [10:15] hi [10:15] does someone here use more then 1 monitor with kde? [10:16] hrw: yes [10:16] Riddell: is there a way to really get kde to remember their setup? [10:17] Riddell: here, never mind what I set in systemsettings, I end with clone [10:17] instead of HDMI0:auto DVI0: right of HDMI0 rotate: left [10:18] hrw: yes, ignore the current tool it's pretty messy and install kscreen from https://launchpad.net/~kubuntu-ppa/+archive/experimental [10:18] thanks [10:18] it needs testers and afiestas is awaiting your feedback (also package reviews to get it into the archive) [10:19] ok [10:19] if this will not work I will revert to good old style: xorg.conf [10:20] hardcore [10:20] but works always [10:22] ok. tested [10:23] looks like xorg.conf needs to go - radeon driver dislike rotating screen in working x11 session [10:23] Riddell: about kscreen: there at least one issue left: what to do about the 'conflikt' with the old screen management module in kded4. [10:24] What has to be done is described in README.debian [10:24] AFAIR fedora splittet the old monitor module into it's own pkg and conflicts with it [10:24] afiestas: please add clear information which way screen is rotated. [10:25] allee: yes that's what I'm thinking [10:25] as "thick line at side of screen" tells me nothing [10:25] allee: mhmm or we divert the old module 'away' [10:25] afiestas: 'identify screens' icon is low res and not intuitive [10:26] afiestas: also there is no info when screens are not snapped. [10:28] afiestas: or if I want to have left in landscape (1920x1080) while right rotated (1080x1920) and snapped in the middle [10:29] afiestas: also buttons to enable/disable screens are non-standard [10:31] afiestas: one thing that happened to be with kscreen: Turn external monitor off, wait 1s, turn it on again while kscreen is still auto-adjusting. What I got was a screen on my external monitor with the size of my notebook screen and the notebook screen was black [10:31] s/to be/to me/ [10:31] yofel__ meant: "afiestas: one thing that happened to me with kscreen: Turn external monitor off, wait 1s, turn it on again while kscreen is still auto-adjusting. What I got was a screen on my external monitor with the size of my notebook screen and the notebook screen was black" [10:32] hrw: report bugs pls [10:32] afiestas: will [10:32] yofel__: report bugs [10:33] will do later [10:33] but firs thave to get xorg.conf written [10:38] ok, restart kdm [10:50] afiestas: it works! [10:52] afiestas: where to report bugs against kscreen? [11:01] hrw: usual place [11:02] afiestas: you mean /dev/null? [11:03] hrw: bugs.kde.org [11:03] so same place [11:05] hrw: saying that bugs.kde.org is dev/null at least in my case is insulting, I spend many hours triaging bugs [11:05] so please, if you want to give feedback do so via bugzilla, if you do not want then do nothing and wait to things to get fixed [11:05] afiestas: sorry for that but most of bugs I reported there stayed there [11:05] so what? that's not excuse [11:05] we mostly develop shit in our free time doing the best you can [11:06] the very least you can do is report bugs and try to do your best as we do [11:06] [11:07] https://bugs.kde.org/buglist.cgi?order=Importance&query_format=advanced&bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=NEEDSINFO&bug_status=VERIFIED&bug_status=CLOSED&component=common&component=kcm&component=kded&component=libkscreen&product=KScreen [11:08] hrw: I challenge you to find there a bug that has not been replied, taken care of, or even fixed [11:21] shadeslayer: are you there? [11:43] phoenix_firebrd: yes [11:43] shadeslayer: it seems the patches in the tomboy-blogposter 0.4.4 is not needed can you confirm that [11:44] I have no idea what that package is [11:44] but have you checked if they were applied upstream? [11:44] shadeslayer: the make files are changes and there is not makefile in the source dir [11:45] shadeslayer: the changelog says the build system is moved to automake, but building fails because of the missing makefile [11:48] shadeslayer: i think the problem is something else [11:48] seems like they were applied upstream [11:48] https://github.com/ozamosi/tomboy-blogposter/commits/master [11:48] last 2 commits [11:49] shadeslayer: I had removed all the patches [11:49] phoenix_firebrd: just from reading the changelog, that sounds right [11:49] shadeslayer: there is something else in the log, i will take a look at it. [11:49] ok [11:50] make[1]: *** No rule to make target `all'. Stop. [12:04] phoenix_firebrd: that's at least missing the error context [12:04] I would guess that automake failed for some other reason [12:04] yofel__: hi [12:04] yofel__: i found it [12:04] yofel__: i am editing the rules now [12:24] yofel__: http://i.imgur.com/ZnzlGUS.png [12:25] all in python [12:25] and that black area actually does show your video [12:25] it's just really dark in my room :P [12:26] is that plain pyqt or qml? [12:27] pyqt [12:27] ah [12:27] still nice [12:30] yofel__: https://gist.github.com/4663893 [12:31] clone to /tmp [12:31] too bad I can't add the videoplayer to the ui file itself [12:32] it conflicts with the one from Qt causing stuff to crash and burn [12:36] phoenix_firebrd: btw. you do know about https://wiki.ubuntu.com/UbuntuDeveloperWeek ? [12:37] shadeslayer: crash and burn o.O? [12:37] ok, crash and burn was a bit too much :P [12:37] basically it does something really stupid [12:37] heh [12:38] oh, there's testing sessions tomorrow on UDW [12:38] might we worth to listen to [12:38] yofel__: this is nice [12:38] phoenix_firebrd: I recommend you listen to dholbach's intro sessions today [12:38] yofel__: the last 4 days where like the same [12:38] yofel__: here or in any other channel? [12:39] #ubuntu-classroom, it's explained on the wiki [12:39] I load the MediaSource into the VideoPlayer and it goes all "You're loading a KDE Phonon MediaSource into the Qt VideoPlayer!!! WTH are you trying to do?!!! " [12:39] but the error message is completely different, it says "You're passing MediaSource to a function that accepts MediaSource" [12:39] shadeslayer: lol, "Building Ubuntu images -- ogra", fun session that'll be :D [12:40] hehe [12:40] I plan to attend that one [12:40] Maybe there'll be some awesome tips in there [12:40] I also have questions [12:41] worth posting that to the mailing list [12:41] yofel__: the class starts approx 2 hrs from now [12:42] ~time utc [12:42] yofel__: you know these are my long requested classes [12:42] unintelligible time [12:42] meh [12:43] ~time [12:43] ~time gmt [12:43] I don't know where you are, use ~time set / to let me know [12:43] unintelligible time [12:43] yofel__: 12:43 [12:43] phoenix_firebrd: yeah, a bit more than 2h till then [12:43] heh [12:43] ~time london [12:43] unintelligible time [12:43] ~time [12:43] I don't know where you are, use ~time set / to let me know [12:43] ~time +0 [12:43] +0 is not a valid country code. [12:43] unintelligible time [12:44] ~time set Asia/Kolkata [12:44] Ok, I'll remember that shadeslayer is on the Asia/Kolkata time zone [12:44] ~time set Europe/Berlin [12:44] ~time uk [12:44] Ok, I'll remember that yofel__ is on the Europe/Berlin time zone [12:44] Europe - London - Tue Jan 29 12:44 GMT [12:44] ~time [12:44] Asia - Kolkata - Tue Jan 29 18:14 IST [12:44] ~time [12:44] there we go :D [12:44] Europe - Berlin - Tue Jan 29 13:44 CET [12:44] kubotu: help time [12:44] usage: time -- timestamp: get info about a specific time, relative to your own time zone | time zone: get local time of a certain location,