=== turgay_ is now known as turgay [07:55] good morning [08:18] Good morning. [09:06] Good morning folks [09:11] o/ [09:27] anyone who knows how to check for installed Qt5 plugins using cmake with Ubuntu 14.04? according to cmake no plugins are available at all although the installed libqt5gui5 package contains them [09:30] frechdachs69: no idea I'm afraid, try in #kde-devel [09:44] which package do I have to install with ubuntu 14.04 to get 'Qt5Gui_QGifPlugin.cmake' ? [09:47] frechdachs69: http://packages.ubuntu.com/search?searchon=contents&keywords=libqgif.so&mode=exactfilename&suite=trusty&arch=any [09:50] Riddell, mamarley: I pushed my current stuff to the kubuntu_unstable branch, will definitely need some peer review [09:51] sitter: for what? [09:51] qca that is [09:51] ah hah [09:51] sitter: did you add a suffix? [09:51] Riddell: yeah library currently is libqca-qt5 [09:59] Riddell: thx but I'm not looking for the shared lib but for the cmake file [10:01] frechdachs69: using that site you can see there's no such file [10:29] frechdachs69: "plugin" indicates it's a plugin => there are no cmake files for plugins (because you cannot link against them anyway) [11:05] sitter: Cool, thanks! I will try to build Quassel against it and see what happens. [11:06] mamarley: I'm compiling now if you want the amd64 vivid packages shortly [11:07] I'm not on Vivid quite yet. [11:07] it needs some changes to compile, wait until I put it in git [11:07] OK [11:11] Riddell: if in unstable new package version is built, it means that some changes has been added right ? [11:12] so the build is not triggered if package does not change ? [11:12] soee: you mean in kubuntu-ci? [11:12] Riddell: yes [11:12] yeah I guess so, could be upstream or packaging change [11:13] Riddell: for example, kactivities-kf5 last build was from 18 and there is from today, can i check what exactly has changed there ? [11:16] Riddell: Which git repository are you talking about? [11:16] mamarley: packaging in http://anonscm.debian.org/cgit/pkg-kde/kde-req/qca2.git/ [11:16] kubuntu_unstable branch [11:16] Ah, OK. Silly me, I was looking on Lauchpad. [11:18] mamarley: old school, we're moving to debian git now [11:18] but there's a million missing symbols :( [11:18] Those annoying symbols :( [11:19] Also, if you want old-school, where I work, we are just finally migrating the project on which I work from CVS to git. O.o [11:20] wow :) [11:21] As someone who learned VCSs on git, CVS is like "argh!" [11:45] hmm, this qca packaging needs some love [11:51] Riddell: Yeah... For me, it fails to even apply the disable_randomunittest.diff patch. [11:53] mamarley: and the qt5 package has the slight failing of compiling against qt4 :) [11:53] Oops [11:55] fixing it.. [11:55] Thank you :) [12:28] morning === rdieter_work is now known as rdieter [12:29] sgclark: HI [12:29] oops [12:29] sgclark: Hi! [12:30] * mamarley can't type today. [12:33] mamarley: ok qca2 updated in git kubuntu_unstable branch [12:34] mamarley: I also uploaded to ppa:kubuntu-ppa/staging for kubuntu_vivid [12:34] Riddell: Oh, even better, thanks! [12:36] mamarley: also uploaded to ppa:kubuntu-ppa/staging for utopic [12:37] mamarley: are you able to test it and check it works with quassel fo qt5? then I can upload it to the archive [12:38] Sometime today. Before too much longer, someone is coming to fix the windshield on my car so I will be busy. [12:39] yeah anytime is good, you're the only person who requested it so far so it's your own time you're wasteing as my teacher used to say :) [12:39] * Riddell wonders why he uploaded to staging and not experimental === frechdachs69_ is now known as frechdachs69 [12:56] Riddell: It is FTBFS for i386 on Vivid and both arches on Utopic :( [12:57] Test failures, ugh. [12:58] woho chromium 39 [12:59] soee: I don't know about you, but for me, Chromium turns into a jerky CPU-hog on any page that has any sort of fixed background or overlay. [13:00] i had small problems with 38 - was just hangind after several minutes of usage (i couldnf do any action except minimize/maximize) [13:00] than when minimized it stared to respond again [13:00] mamarley: mm, adding a workaround [13:01] Strange that it succeeded on Vivid x86_64 but failed everywhere else... [13:02] now with one tab opened all chromium processes use ~300mb [13:03] mamarley: ok reuploaded to kubuntu-ppa/experimental [13:03] Thanks! [13:10] Riddell: https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/experimental/+build/6597264 :( [13:11] Riddell: http://blog.martin-graesslin.com/blog/2014/06/where-are-my-systray-icons/ <- did you plan to integrate this Qt patch? I'm running 14.10 + kubuntu-next-ppa, and I still don't get the icon for pidgin, for instance. [13:11] (still have to run wmsystemtray to make it show up) [13:12] kfunk: same with skype [13:13] yeah, it's one of the biggest remaining annoyances in Plasma 5 these days ;) [13:13] rest works like a charm [13:14] Hiyas all [13:21] kfunk: well this isnt any problem to me tbh :) im missing my shortcut to switch to 'next activity' :) thats teh biggest issue for me [13:21] to me, activities are quite useless altogether tbh ;) [13:21] I'm happy when they don't get in my way [13:21] (like accidentally switching activities, which happened in the past) [13:22] The Quassel compilation with QCA on Qt5 almost works, but I get a "make[2]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libqca.so', needed by 'src/../quasselcore'. Stop." right at the end. :( [13:23] I don't know much about cmake, or about how Qt5 support is implemented in QCA2, but maybe I need to use "QCA2-QT5" instead of just "QCA2" as the package name [13:24] Nope. [13:28] It's not just about the package name, it's also about the library file names. [13:29] See what I had to do for qscintilla2 as a rough example. [13:41] ScottK: This version: https://launchpad.net/ubuntu/+source/qscintilla2/2.8.3+dfsg-3 ? [13:42] mamarley: Yes, although if you look at later versions, I didn't get it quite right on the first try. [13:42] OK, thanks! [13:46] ScottK: Would this need to be changes to the QCA package or the Quassel package? I looked at the diff for the qscintilla2 package, but it doesn't appear to be using cmake and I am not sure what the changes mean. [13:46] qscintilla2 is using qmake, so it's not exactly the same. [13:46] It'd be QCA. [13:47] The point was both the package name and the name if the files in the library need changing to not conflixt. [13:47] conflict [13:47] mamarley: ah yes simple mistake I made, fixing [13:47] kfunk: hmm we should do already no? [13:48] ScottK: Riddell: By hacking the build.make file after configuring, I actually got it to build. [13:48] Now to see if it runs... [13:49] mamarley: huh? what did you need to do? [13:49] Riddell: I changed "libqca.so" to "libqca-qt5.so". A dirty workaround, I know, but I am just trying to see if it will run at all. [13:50] Riddell: doesn't appear to be working. does it for you? [13:50] Riddell: try running pidgin, for instance [13:50] mamarley: new upload to kubuntu-ppa/experimental [13:50] or do I just need to tweak some settings? [13:51] no tweaks needed [13:51] installing skype.. [13:52] kfunk: hwo can you accidentyl switch activity ? D: [13:52] soee: with shortcuts, I think [13:52] at least in KDE4 times [13:52] by now I removed any activities but one, so it can't happen anymore [13:52] :) this shortcut was teh best think in kde :) [13:53] Riddell: Thanks! [13:53] kfunk: skype is i386 so you need to install sni-qt:i386 [13:53] And by the way, with the hack to get it compiled, Quassel with QCA on Qt5 seems to be working! [13:53] mamarley: oh you had to edit the file in quassel I see [13:53] I don't actually know of any encrypted channels in which to try it, but it starts and doesn't crash, so... [13:53] Riddell: Yep. [13:54] Riddell: skype is not my issue [13:54] mamarley: fancy adding that as a comment to https://git.reviewboard.kde.org/r/121168 ? "you are making distros change the library name which means anything using the library also needs to be changed, please update the soversion as this patch does" [13:55] Ah, you want me to get involved in that flamewar :) [13:55] lol [13:55] Sure, I can do that. [13:55] Riddell: pidgin is 64bit, and I have sni-qt installed [13:55] * mamarley puts on the flamesuit and refills his flamer's propane tank. [13:57] kfunk: yes I gree that does not work [13:59] ScottK: bug 1378789 still needing some love [14:00] bug 1378789 in kubuntu-settings (Ubuntu Trusty) "[SRU] Set the default IO scheduler to CFQ in Kubuntu Trusty" [Undecided,Confirmed] https://launchpad.net/bugs/1378789 [14:00] Riddell: It might take me a minute, sorry. I created a KDE Identity, but the confirmation email was greylisted :/ [14:00] * ScottK has a list. That's on it. [14:01] hmmm. I have a Qt5 application using QSystemTrayIcon where it doesn't work either [14:01] I'm confused [14:04] oh well, wmsystemtray is my friend for now ;) [14:11] mamarley: if you have a package of quassel do let me know and I can upload to experimental for testing [14:15] Riddell: I do, in my quassel-exp PPA. The core works fine, but the client crashes on startup. The error information prints something about a Qt4 lib, so I am not sure what is going on with that. [14:17] mamarley: maybe something is linking against qt4 [14:17] is there any other source available for plasma 5 application colour schemes? the downloader still has no other choices and most of the colours mamarley: pastebin ldd /usr/bin/quassel [14:26] mamarley: u mean the client package build qt5 in your experimental ppa? === toscalix_ is now known as toscalix [15:11] Riddell: Just a sec, I need to compile it again. I don't have the packages installed because that would screw up my real client. [15:19] Riddell: http://paste.kde.org/pfcutmyp8 [15:20] yep that's qt5 alright [15:20] Riddell: http://paste.kde.org/po34oe3ur [15:21] hmm libQtGui.so.4 [15:21] Yep [15:21] so what's loading that? [15:22] * mamarley has been unable to figure that out as of yet. [15:23] mamarley: try pmap? [15:24] Riddell: It crashes immediately upon executing it, so I don't think that would work. [15:25] ooh 5.4 [15:25] ooh 5.4 [15:26] New software is fun :) [15:26] * ScottK thought we were staying with 5.3.whatever. [15:26] Maybe it is the Qt5-edgers PPA? [15:26] If so, it shouldn't be in our branches. [15:26] * mamarley has no idea what he is talking about; please ignore him. [15:27] is qt 5.4.0 even out? [15:27] Pretty sure it's not. [15:28] mamarley: I wonder if it's your install of phonon vlc [15:28] Mirv: ^^^ what's that commit message about Qt 5.4.0? [15:28] mamarley: try rm /usr/lib/x86_64-linux-gnu/qt4/plugins/phonon_backend/phonon_vlc.so for good luck [15:28] Riddell: Oh, yes. I am using the VLC phonon backend, and VLC uses Qt4. Darn. [15:28] Let me switch to the null backend. [15:30] IT WORKS! [15:30] It is ugly, but it works! [15:31] mamarley: what did you do? [15:31] Riddell: I uninstalled phonon4qt5-backend-vlc. [15:32] hum, that really shouldn't be loading qt4 [15:32] It shouldn't, but at least it tells me it isn't a problem with my Quassel build. [15:32] As far as the Qt5.4 thing, the package named above is building in https://launchpad.net/~canonical-qt5-edgers/+archive/ubuntu/qt5-beta2. [15:33] That PPA has Qt 5.4beta in it. [15:46] google code in starts in 5 days, what kubuntu tasks can we create for it? [15:46] tasks for school age people should take a few days [15:48] dunno, did that sddm hard coding paths geet fixed? the libreoffice them thing? [15:48] * sgclark shrugs [15:49] libreoffice I've added [15:50] sddm might be too hard [15:50] last year I had a guy writing blog posts [15:50] and packaging some bits [15:51] we hae been doing pretty good on blogging, though I guess more depth might be good. Always stuff to package [15:52] Riddell: What else needs porting to Qt5/Kf5 that wouldn't be too hard? [15:52] I am trying to at least finish the kde4 applications today, tomorrow is a big holiday here and I have to cook for an army [15:53] * ScottK hopes you're doing the cooking because you enjoy it. [15:54] sgclark: oh yes it's the big US holiday, I forbid you from doing kubuntu stuff tomorrow [15:54] ScottK: print-manager, dunno if that is hard tho [15:54] ScottK: I love cooking :) [15:54] Riddell: thanks :) [15:54] Also print-manager's upstream KDE, not Kubuntu specific. [15:54] Still worth having someone do it. [15:54] ahh [15:55] no biggie, 4 version works, just not user friendly to access it [15:55] What about he restricted driver thingy. Did someone do that already? [15:55] it is in kcm5 [15:55] Great. [15:55] sgclark: print-manager is being done by someone at red hat, needs testing [15:56] hmm, testing, there's an idea [15:56] oh cool [15:56] yes testing, we have piles of applications in ninjhas that need more testing, I am just starting them and not really trying to crash them [15:58] Riddell: For some reason, I can't get Quassel to detect QCA at all anymore. It just says "-- Could NOT find QCA2 (missing: QCA2_LIBRARIES)" during the configure. [15:58] I definitely have the -dev package installed though. [15:59] mamarley: during compile? [16:00] After I execute the cmake command. [16:00] Not while it is actually compiling. [16:00] right [16:00] well needs something else changed for the qca rename? [16:01] It has "find_package(QCA2)" in CMakeLists.txt. That might need to change, but I am not sure. [16:04] FindQCA2.cmake will need to change [16:04] you may want to grump about this to the qca maintainer [16:06] Put on your flame retardant pants first. [16:06] ScottK: Still got those on from earlier :) [16:07] Actually it looks like Quassel has its own FindQCA2.cmake file. [16:07] :-) [16:07] patch that then I guess [16:07] Then whine at Sput. [16:07] Yep, looking at that now. [16:08] Actually, I don't even need to whine at Sput. I can just make a PR myself. :) [16:08] well it's not something that can be fixed upstream alas except through qca [16:09] * mamarley fires the QCA maintainer. [16:19] This file doesn't make any sense. It has a bunch of variables like QCA2_INCLUDE_DIR and QCA2_LIBRARIES that don't seem to be defined anywhere. [16:19] It is almost like it is pulling data out of mid air. [16:20] cmake files sometimes do [16:20] it'll magically make them based on something else if you do mylib(QCA2) [16:20] or something [16:22] It appears to be using pkg-config... [16:24] that'll be your magic then [16:25] "pkg-config --modversion qca2-qt5" prints something other than blank or an error message, so that seems to be a good thing. [16:25] sitter: new git repo up on debian for kscreen with kubuntu_unstable branch [16:26] It looks like having separate FindQCA2.cmake and FindQCA2-QT5.cmake files might be a good idea. [16:32] yes it would [16:32] * Riddell out [16:40] Um, I actually got it to work. That is surprising... [16:41] It finds QCA2, anyway. Let's see if it builds... [16:48] Nope, it about 200 errors while linking. Typical. [16:53] (This is probably why I am a Java developer and not a C(++) developer. :) === tazz_ is now known as tazz === rdieter is now known as rdieter_work [18:02] <_Groo_> prolly you guys already know, but today kubuntu-ci is failing in plasmashell with plasmashell: symbol lookup error: plasmashell: undefined symbol: _ZN7KScreen6Config11outputAddedEPNS_6OutputE [18:02] <_Groo_> but the login freeze bug is apparently gone [18:03] <_Groo_> for utopic btw [18:16] <_Groo_> plasma-workspace now needs kf5screen 5.0.93, and the repo kscreen is 5.0.91 ence it breaks [18:16] <_Groo_> https://www.irccloud.com/pastebin/4LEFWzJ7 [18:19] <_Groo_> and kscreen doesnt compile because its missing qt4 oO Found unsuitable Qt version "" from NOTFOUND, this code requires Qt 4.x [18:21] _Groo_: try the frameworks branch in kscreen [18:21] <_Groo_> yofel: link? [18:23] uh, 'git clone git://anongit.kde.org/kscreen; cd kscreen; git checkout frameworks' ? [18:25] <_Groo_> ahhh sorry, i thought it was a ppa, lol [18:27] <_Groo_> yofel: i dont have resources to compile kscreen + kf5 this week, im using a borrowed laptop, i can only report bugs :( === alket_ is now known as alket [19:10] lordievader: ping [19:11] Riddell: I got it working! The Quassel packaging is a bit crude, but you are definitely welcome to look at it. [19:11] who's going to FOSDEM? [19:32] sitter: how does one trigger a no-change rebuild in CI? Or do I need a jenkins account for that? === rdieter_laptop is now known as rdieter [20:06] yofel: I think we need an account, hense why I have not done anything [20:07] sitter is out today too [20:09] yeah, probably. I fixed libkscreen at least [20:10] I know Riddell put kscreen in unstable, dunno what needs to be done to get ci to build it [20:11] the weekly ci really needs to be completed for people to use. daily really should not be used by everyone, unless someone is fixing stuff 24/7 [20:25] wow, that many of oyu are going to FOSDEM? [20:25] overwhelming, isn't it? ^^ [20:26] I was thinking about it, but without taking Friday and Monday off it would be too hectic === alket_ is now known as alket [21:18] this has been one annoying bug [21:18] https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1306991 [21:18] Launchpad bug 1306991 in python-pip (Debian) "pip stops with ImportError for request-Modul" [Unknown,New] [21:18] rbelem: ping [21:18] has anyone else ran into this? [21:19] if you're on ubuntu 14.10 and you install the python3-pip package, by default it's broken since it's reliant on requests [21:19] and by ubuntu i mean the greater ecosystem :P [21:19] if you're in 14.04, and you use pip3 to install requests, you're screwed [21:20] the most annoying thing (no a bug) i have when starting kubuntu is some message with text Broken Pipe :) [21:20] er, i need better word to use than "screwed" [21:21] yottabit: You'll probably have more luck on a non-Kubuntu channel. [22:43] yofel: yeah needs user [22:43] not sure how to handle this tho because jenkins apparently has no concept of groups, so I guess there'll just be a shared account