/srv/irclogs.ubuntu.com/2015/07/21/#kubuntu-devel.txt

=== drawkward_away is now known as drawkward
=== drawkward is now known as drawkward_away
=== drawkward_away is now known as drawkward
lordievaderGood morning.08:14
ricktimmislordievader: Good Morning sir, how are you today ?08:15
lordievaderHey ricktimmis, doing good here. Coffee is brewing. How are you?08:16
ricktimmisGot my Coffee, and starting my day, all looking pretty good so far :-)08:20
lordievader:)08:28
=== drawkward is now known as drawkward_away
=== drawkward_away is now known as drawkward
=== drawkward is now known as drawkward_away
yossarianukupgraded to 15.10 last night - no major issues , the do-release-upgrade process bombed out at one point, but after removing a package (unsure which one as i'm at work now) I could carry on with 'apt-get -f install'12:10
yossarianukfrom my very limited use of it no issues so far.12:10
soee_yossarianuk: good to hear ;)12:32
BluesKajHI folks12:44
soee_hiho BluesKaj12:45
BluesKajhey soee_12:45
yossarianuki notice its using kernel 4.0.x12:56
yossarianukis it going to use 4.1.x when released ?12:56
yossarianukMy benchmarks show 4.1 being a bit faster with IO read speed (ext4) 12:56
yossarianukin case anyone is interested ... http://openbenchmarking.org/result/1507214-BE-1507168BE3512:57
yofel4.1 is in wily-proposed12:57
murthy_yossarianuk: are the phoronix guy?12:58
yossarianukcool (note : kubuntu stacks up well BTW) - compared to opensuse/arch/debian.12:58
yossarianukmurthy_: not with you ? I am a phoronix user - not the developer.12:58
murthy_yossarianuk: ok12:59
murthy_yossarianuk: some of the kde and kubuntu devs dont like the benchmarks done by phoronix12:59
lordievaderIs 4.1 going to be lts?13:15
yossarianukmurthy_: why not ?13:43
yossarianukmurthy_: I do not know of a better app/suite ....13:43
yossarianukmurthy_: I know you have to be careful that sometime games read the wrong screen resolution so run lower (than a compared system) 13:44
yossarianukHowever to fix that I use an xorg.conf (with nvidia), the screen size is always correct for the game when I do.13:45
yossarianukso as long as you are sure all systems are running the game in the same resolution what it the problem?13:46
murthy_yossarianuk: http://blog.martin-graesslin.com/blog/2012/02/about-compositors-and-game-rendering-performance/13:46
murthy_yossarianuk: https://forum.kde.org/viewtopic.php?f=15&t=11055513:48
yossarianukI always enable 2 settings in kde/nvidia or games are 1/3 slower / unplayable13:52
yossarianuk1) I enable the 'suspend desktop effects for full screen apps'13:53
yossarianuk2) I disable Sync to vblank (I have to do this or many games have really laggy controls)13:53
yossarianukAs long as I do these things benchmarks beat windows in many games.13:53
yossarianuk(2) doesn't effect fps but makes games playable.13:54
yossarianukin my experince KDE (with the suspend desktop effects for fullscreen apps enabled) is slightly faster than gnome3/cinnamon/unity13:55
yossarianukKDE is my gaming (and everything) desktop13:55
murthy_yossarianuk: comparing the benchmarks of two different compositors is wrong first. Both offer different level of features and functionality 14:00
yossarianukmurthy_: but surely comparing how a game performs under both compositors is a valid test?14:06
yossarianukI used to not run gnome3 due to the fact you couldn't disable the compositor when it first came out14:07
yossarianuknow I don't run gnome3 as its a unusable mutant tablet interface,14:07
=== murthy_ is now known as murthy
murthyyossarianuk: sorry I was having dinner14:23
yossarianuknp dude - just pointing out that how a game performs under different compostors is something many would be interested it...14:24
yossarianuk*in*14:24
murthyyossarianuk: the kwin developer thinks that the desktop is not designed for gaming 14:24
yossarianukwell once you enable that setting it performs just as well as others (in fact better)14:25
yossarianukwith Nvidia at least14:25
mgraesslinyossarianuk: just do alt+shift+f12 before running games or create a window specific rule to block compositing14:27
murthyyossarianuk: If i am not mistaken thats our kwin developer14:28
yofelit is ^^14:28
=== drawkward_away is now known as drawkward
yossarianukmgraesslin: thanks Martin!14:45
yossarianukmgraesslin: enabling the 'suspend desktop effects for fullscreen apps' seems to work also (at least with plasma5)14:46
yossarianukmy point was that KDE (5) stacks up well against other desktops...14:47
mgraesslinyossarianuk: I cannot recomend the feature, it still has the complete compositor up and running14:47
yossarianukok - well thank you - I shall compare benchamrks after disabling compositing ...14:49
yossarianukim assuming this will not be an issue when we have Wayland ?14:50
yossarianuk(and wayland compatible games ?)14:50
=== mamarley_ is now known as mamarley
=== drawkward is now known as drawkward_away
=== soee_ is now known as soee
=== drawkward_away is now known as drawkward
santa_good evening doko, it seems we will need a fixed scim to build kdeplasma-addons: http://gpul.grupos.udc.es/logs/kdeplasma-addons_5.3.2-0ubuntu1+santa1.1_amd64.build16:42
santa_(I'm rebuilding plasma with gcc 5, status http://gpul.grupos.udc.es/kdenext_buildstatus_ubuntu-exp/ubuntu-exp_status_plasma.html)16:42
santa_the other build failures are just symbols files, I will make patches soon16:43
shadeslayercan we even accept symbols file patches for gcc 5 yet16:49
shadeslayerwhen KCI is still building with 416:49
yofelswitch KCI to 5?16:50
shadeslayerdisparity between vivid,wily archive builds then16:51
shadeslayernot to mention DCI as well16:51
santa_shadeslayer, yofel: my patches for frameworks work with gcc 4 anyway, status http://gpul.grupos.udc.es/kdenext_buildstatus_ubuntu-exp2/ubuntu-exp2_status_kf5.html16:51
yofelwell, we'll have to keep them somewhere, if KCI is a problem we can make another branch maybe16:52
santa_so yes, you can accept my patches, in fact it would be nice to get them in kubuntu_vivid_archive before the gcc switch16:53
yofelalso, you *never* have a guarantee that the same symbol file will work for different releases. Actually, that almost never works as we have pretty much never releases wit the same gcc version16:53
yofelso I'm not sure why you're worrying about vivid when it comes to symbofiles16:53
shadeslayerI'm just saying, it feels switching at the moment is premature16:54
shadeslayershouldn't we wait till August?16:54
yofelso... a week?16:54
shadeslayeryes, no, maybe, idk16:56
* shadeslayer shuts up and goes back into making Qt5 crash16:56
yofelI'll re-read the mail again when my wily upgrade is done..16:56
dokosanta_, scim ftbfs16:59
dokolibtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../../.. -I../../../.. -I../../../.. -I../../../../extras/immodules/common -I../../..16:59
dokousr/include/qt4/QtCore -DQT_IMMODULE -DQT4 -g -O0 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c moc_scim-bridge16:59
doko-client-qt.cpp  -fPIC -DPIC -o .libs/im_scim_la-moc_scim-bridge-client-qt.o16:59
dokomoc_scim-bridge-client-qt.cpp:15:2: error: #error "This file was generated using the moc from 5.4.2. It"16:59
doko #error "This file was generated using the moc from 5.4.2. It"16:59
doko  ^16:59
dokomoc_scim-bridge-client-qt.cpp:16:2: error: #error "cannot be used with the include files from this version of Qt."16:59
mparilloyofel: You wily upgrade is progessing? You cannot reproduce: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/146433016:59
doko #error "cannot be used with the include files from this version of Qt."16:59
doko  ^16:59
dokomoc_scim-bridge-client-qt.cpp:17:2: error: #error "(The moc has changed too much.)"16:59
doko #error "(The moc has changed too much.)"16:59
doko  ^16:59
dokomoc_scim-bridge-client-qt.cpp:22:5: error: 'QByteArrayData' does not name a type16:59
doko     QByteArrayData data[3];16:59
doko     ^16:59
dokomoc_scim-bridge-client-qt.cpp:28:24: error: 'QByteArrayData' was not declared in this scope17:00
shadeslayerok17:00
doko         - idx * sizeof(QByteArrayData)) \17:00
doko                        ^17:00
dokomoc_scim-bridge-client-qt.cpp:32:1: note: in expansion of macro 'QT_MOC_LITERAL'17:00
doko QT_MOC_LITERAL(0, 0, 18), // "ScimBridgeClientQt"17:00
doko ^17:00
dokomoc_scim-bridge-client-qt.cpp:29:5: error: 'Q_STATIC_BYTE_ARRAY_DATA_HEADER_INITIALIZER_WITH_OFFSET' was not declared in this scope17:00
doko     )17:00
doko     ^17:00
dokomoc_scim-bridge-client-qt.cpp:32:1: note: in expansion of macro 'QT_MOC_LITERAL'17:00
doko QT_MOC_LITERAL(0, 0, 18), // "ScimBridgeClientQt"17:00
doko ^17:00
dokomoc_scim-bridge-client-qt.cpp:28:24: error: 'QByteArrayData' was not declared in this scope17:00
doko         - idx * sizeof(QByteArrayData)) \17:00
doko                        ^17:00
dokomoc_scim-bridge-client-qt.cpp:33:1: note: in expansion of macro 'QT_MOC_LITERAL'17:00
doko QT_MOC_LITERAL(1, 19, 14), // "handle_message"17:00
doko ^17:00
dokomoc_scim-bridge-client-qt.cpp:29:5: error: 'Q_STATIC_BYTE_ARRAY_DATA_HEADER_INITIALIZER_W17:00
yofelmparillo: I had one file conflict so far, but I'm not using the release upgrader17:00
mparilloAhh, TY17:00
yofelah, santa fixed that in git already17:01
BluesKajdoko,  have you heard of pastebin?17:01
mitya57doko, sounds like it tries to mix Qt4 and Qt5 code17:02
dokomitya57, yep, trying in a new chroot17:02
=== drawkward is now known as drawkward_away
dokosanta_, now built in the silo16 ppa17:45
=== vHanda_ is now known as vHanda
santa_doko: thanks, right now my buildds are going to be busy rebuilding the rest of the plasma stuff, I will retry the build as soon as I can19:08
fewchaHi everyone :)20:57
fewchaI just built Qt 5.5 from scratch in my Kubuntu 15.0420:57
ari-tczewhi fewcha20:57
Riddellfewcha: elite :)20:57
fewchastill qmake --version is showing me20:58
fewchaQMake version 2.01a20:58
fewchaUsing Qt version 4.8.6 in /usr/lib/x86_64-linux-gnu20:58
fewchaany idea how to turn my system's qt into 5.5 as well?20:58
fewchaari-tczew: Riddell: thanks :D20:59
Riddellclivejo: did you ever get anywhere with calligra?20:59
Riddellfewcha: install qt5-default20:59
clivejoRiddell: only fits of rage20:59
Riddell:(21:00
Riddellclivejo: lots of merges and the stuff sitter posted to the list if you want to try something else21:00
fewchaRiddell: so that will make it 5.4.1, right? How do I make it 5.5? :)21:02
Riddellrun the qmake that was compiled with 5.5 I guess21:02
clivejowhat stuff did sitter post?21:11
fewchaRiddell: Can you please tell me how to do that?21:12
Riddellclivejo: https://lists.ubuntu.com/archives/kubuntu-devel/2015-July/009767.html21:13
Riddellfewcha: um dunno depends where it installed to 21:13
clivejooh Im not on that list21:14
fewchaRiddell: I cloned qt5 in my home, and ran make from there21:15
fewchathere as in ~/qt521:15
Riddellclivejo: ah hah, time to join :)21:15
fewchaI was following https://wiki.qt.io/Building_Qt_5_from_Git21:15
Riddellfewcha: so it'll be somewhere in ~/qt5 I guess, find ~/qt5 -name qmake21:15
fewchaaccording to that, "Installation is only needed if you haven't used the configure options -developer-build or -prefix "%PWD%/qtbase". Otherwise you can just use Qt from the build directory."21:16
fewchaso I didn't do make install21:16
fewchaokay21:16
fewchaRiddell: https://paste.kde.org/psqwfimvg/qop0iu21:17
Riddellfewcha: so /home/sanjiban/qt5/qtbase/bin/qmake21:17
fewchaRiddell: okay so I just need to run that binary21:18
RiddellI guess so, I've done it myself21:18
fewchaRiddell: okay, so https://paste.kde.org/picb6dcpy/bvyo9h21:20
Riddelllooks like it's working21:21
fewchaRiddell: Isn't it showing there that its usage is incorrect?21:21
Riddellit's saying you need to specify I guess, dunno I avoid using qmake as much as possible21:23
fewchaRiddell: okay, but do you remember that when you did it, what did you write there?21:24
Riddellif I run qmake in a directory with a .pro file it'll make a Makefile21:24
Riddellif I run it in a directory with just qt source files it'll write a .pro file21:25
fewchaRiddell: the directory from which I am running qmake, contains only binaries, and one qt.conf21:26
fewchadirectory = ~/qt5/qtbase/bin21:27
fewchaRiddell: Running qmake says that it's usage should be like: /home/sanjiban/qt5/qtbase/bin/qmake [mode] [options] [files]21:28
fewchaRiddell: so do you remember that when you had run that qmake, what had you put in the mode, options, files?21:29
fewcha:)21:29
Riddellfewcha: it depends on what's in the directory you are running it21:29
Riddellwhat do you want it to do?21:29
fewchaI want it to make my system's qt with this qt built from source21:30
fewchasorry21:30
fewchaI want it to replace my system's qt with this qt built from source21:31
fewchaRiddell: so that qmake --version shows me Qt 5.5 rather than Qt 5.421:32
sgclarkhi from Spain..21:42
soeehiho sgclark :)21:42
soeefirst time in Spain ?21:43
sgclarkyes21:47
clivejohot?21:51
sgclarknice breeze, not so bad. but have not been awake much yet haha. long flight(s)21:57
santa_sgclark: which city?22:17
ahoneybunsanta_: should be la coruna22:17
santa_already? welcome then22:18
sgclarkyeah already lol... guess we will explore some22:19
santa_thats good, I think this city is safe in general at night22:21
santa_(probably you should be more careful in other cities of the world XD)22:22
sgclarkwhere I live is not safe in certain places at night heh. I will stick to day exploration till the crowds get here haha.22:28
sgclarkgonna try and sleep some so my schedule is not to bonkers this trip. see you all in a few hours.22:29
santa_good night22:34
shadeslayersgclark: is the weather soupy there too22:39

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!