=== drawkward_away is now known as drawkward | ||
=== drawkward is now known as drawkward_away | ||
=== drawkward_away is now known as drawkward | ||
lordievader | Good morning. | 08:14 |
---|---|---|
ricktimmis | lordievader: Good Morning sir, how are you today ? | 08:15 |
lordievader | Hey ricktimmis, doing good here. Coffee is brewing. How are you? | 08:16 |
ricktimmis | Got 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 | ||
yossarianuk | upgraded 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 |
yossarianuk | from my very limited use of it no issues so far. | 12:10 |
soee_ | yossarianuk: good to hear ;) | 12:32 |
BluesKaj | HI folks | 12:44 |
soee_ | hiho BluesKaj | 12:45 |
BluesKaj | hey soee_ | 12:45 |
yossarianuk | i notice its using kernel 4.0.x | 12:56 |
yossarianuk | is it going to use 4.1.x when released ? | 12:56 |
yossarianuk | My benchmarks show 4.1 being a bit faster with IO read speed (ext4) | 12:56 |
yossarianuk | in case anyone is interested ... http://openbenchmarking.org/result/1507214-BE-1507168BE35 | 12:57 |
yofel | 4.1 is in wily-proposed | 12:57 |
murthy_ | yossarianuk: are the phoronix guy? | 12:58 |
yossarianuk | cool (note : kubuntu stacks up well BTW) - compared to opensuse/arch/debian. | 12:58 |
yossarianuk | murthy_: not with you ? I am a phoronix user - not the developer. | 12:58 |
murthy_ | yossarianuk: ok | 12:59 |
murthy_ | yossarianuk: some of the kde and kubuntu devs dont like the benchmarks done by phoronix | 12:59 |
lordievader | Is 4.1 going to be lts? | 13:15 |
yossarianuk | murthy_: why not ? | 13:43 |
yossarianuk | murthy_: I do not know of a better app/suite .... | 13:43 |
yossarianuk | murthy_: I know you have to be careful that sometime games read the wrong screen resolution so run lower (than a compared system) | 13:44 |
yossarianuk | However to fix that I use an xorg.conf (with nvidia), the screen size is always correct for the game when I do. | 13:45 |
yossarianuk | so 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=110555 | 13:48 |
yossarianuk | I always enable 2 settings in kde/nvidia or games are 1/3 slower / unplayable | 13:52 |
yossarianuk | 1) I enable the 'suspend desktop effects for full screen apps' | 13:53 |
yossarianuk | 2) I disable Sync to vblank (I have to do this or many games have really laggy controls) | 13:53 |
yossarianuk | As 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 |
yossarianuk | in my experince KDE (with the suspend desktop effects for fullscreen apps enabled) is slightly faster than gnome3/cinnamon/unity | 13:55 |
yossarianuk | KDE is my gaming (and everything) desktop | 13:55 |
murthy_ | yossarianuk: comparing the benchmarks of two different compositors is wrong first. Both offer different level of features and functionality | 14:00 |
yossarianuk | murthy_: but surely comparing how a game performs under both compositors is a valid test? | 14:06 |
yossarianuk | I used to not run gnome3 due to the fact you couldn't disable the compositor when it first came out | 14:07 |
yossarianuk | now I don't run gnome3 as its a unusable mutant tablet interface, | 14:07 |
=== murthy_ is now known as murthy | ||
murthy | yossarianuk: sorry I was having dinner | 14:23 |
yossarianuk | np 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 |
murthy | yossarianuk: the kwin developer thinks that the desktop is not designed for gaming | 14:24 |
yossarianuk | well once you enable that setting it performs just as well as others (in fact better) | 14:25 |
yossarianuk | with Nvidia at least | 14:25 |
mgraesslin | yossarianuk: just do alt+shift+f12 before running games or create a window specific rule to block compositing | 14:27 |
murthy | yossarianuk: If i am not mistaken thats our kwin developer | 14:28 |
yofel | it is ^^ | 14:28 |
=== drawkward_away is now known as drawkward | ||
yossarianuk | mgraesslin: thanks Martin! | 14:45 |
yossarianuk | mgraesslin: enabling the 'suspend desktop effects for fullscreen apps' seems to work also (at least with plasma5) | 14:46 |
yossarianuk | my point was that KDE (5) stacks up well against other desktops... | 14:47 |
mgraesslin | yossarianuk: I cannot recomend the feature, it still has the complete compositor up and running | 14:47 |
yossarianuk | ok - well thank you - I shall compare benchamrks after disabling compositing ... | 14:49 |
yossarianuk | im 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.build | 16: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 soon | 16:43 |
shadeslayer | can we even accept symbols file patches for gcc 5 yet | 16:49 |
shadeslayer | when KCI is still building with 4 | 16:49 |
yofel | switch KCI to 5? | 16:50 |
shadeslayer | disparity between vivid,wily archive builds then | 16:51 |
shadeslayer | not to mention DCI as well | 16: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.html | 16:51 |
yofel | well, we'll have to keep them somewhere, if KCI is a problem we can make another branch maybe | 16: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 switch | 16:53 |
yofel | also, 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 version | 16:53 |
yofel | so I'm not sure why you're worrying about vivid when it comes to symbofiles | 16:53 |
shadeslayer | I'm just saying, it feels switching at the moment is premature | 16:54 |
shadeslayer | shouldn't we wait till August? | 16:54 |
yofel | so... a week? | 16:54 |
shadeslayer | yes, no, maybe, idk | 16:56 |
* shadeslayer shuts up and goes back into making Qt5 crash | 16:56 | |
yofel | I'll re-read the mail again when my wily upgrade is done.. | 16:56 |
doko | santa_, scim ftbfs | 16:59 |
doko | libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../../../.. -I../../../.. -I../../../.. -I../../../../extras/immodules/common -I../../.. | 16:59 |
doko | usr/include/qt4/QtCore -DQT_IMMODULE -DQT4 -g -O0 -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c moc_scim-bridge | 16:59 |
doko | -client-qt.cpp -fPIC -DPIC -o .libs/im_scim_la-moc_scim-bridge-client-qt.o | 16:59 |
doko | moc_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 |
doko | moc_scim-bridge-client-qt.cpp:16:2: error: #error "cannot be used with the include files from this version of Qt." | 16:59 |
mparillo | yofel: You wily upgrade is progessing? You cannot reproduce: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1464330 | 16:59 |
doko | #error "cannot be used with the include files from this version of Qt." | 16:59 |
doko | ^ | 16:59 |
doko | moc_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 |
doko | moc_scim-bridge-client-qt.cpp:22:5: error: 'QByteArrayData' does not name a type | 16:59 |
doko | QByteArrayData data[3]; | 16:59 |
doko | ^ | 16:59 |
doko | moc_scim-bridge-client-qt.cpp:28:24: error: 'QByteArrayData' was not declared in this scope | 17:00 |
shadeslayer | ok | 17:00 |
doko | - idx * sizeof(QByteArrayData)) \ | 17:00 |
doko | ^ | 17:00 |
doko | moc_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 |
doko | moc_scim-bridge-client-qt.cpp:29:5: error: 'Q_STATIC_BYTE_ARRAY_DATA_HEADER_INITIALIZER_WITH_OFFSET' was not declared in this scope | 17:00 |
doko | ) | 17:00 |
doko | ^ | 17:00 |
doko | moc_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 |
doko | moc_scim-bridge-client-qt.cpp:28:24: error: 'QByteArrayData' was not declared in this scope | 17:00 |
doko | - idx * sizeof(QByteArrayData)) \ | 17:00 |
doko | ^ | 17:00 |
doko | moc_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 |
doko | moc_scim-bridge-client-qt.cpp:29:5: error: 'Q_STATIC_BYTE_ARRAY_DATA_HEADER_INITIALIZER_W | 17:00 |
yofel | mparillo: I had one file conflict so far, but I'm not using the release upgrader | 17:00 |
mparillo | Ahh, TY | 17:00 |
yofel | ah, santa fixed that in git already | 17:01 |
BluesKaj | doko, have you heard of pastebin? | 17:01 |
mitya57 | doko, sounds like it tries to mix Qt4 and Qt5 code | 17:02 |
doko | mitya57, yep, trying in a new chroot | 17:02 |
=== drawkward is now known as drawkward_away | ||
doko | santa_, now built in the silo16 ppa | 17: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 can | 19:08 |
fewcha | Hi everyone :) | 20:57 |
fewcha | I just built Qt 5.5 from scratch in my Kubuntu 15.04 | 20:57 |
ari-tczew | hi fewcha | 20:57 |
Riddell | fewcha: elite :) | 20:57 |
fewcha | still qmake --version is showing me | 20:58 |
fewcha | QMake version 2.01a | 20:58 |
fewcha | Using Qt version 4.8.6 in /usr/lib/x86_64-linux-gnu | 20:58 |
fewcha | any idea how to turn my system's qt into 5.5 as well? | 20:58 |
fewcha | ari-tczew: Riddell: thanks :D | 20:59 |
Riddell | clivejo: did you ever get anywhere with calligra? | 20:59 |
Riddell | fewcha: install qt5-default | 20:59 |
clivejo | Riddell: only fits of rage | 20:59 |
Riddell | :( | 21:00 |
Riddell | clivejo: lots of merges and the stuff sitter posted to the list if you want to try something else | 21:00 |
fewcha | Riddell: so that will make it 5.4.1, right? How do I make it 5.5? :) | 21:02 |
Riddell | run the qmake that was compiled with 5.5 I guess | 21:02 |
clivejo | what stuff did sitter post? | 21:11 |
fewcha | Riddell: Can you please tell me how to do that? | 21:12 |
Riddell | clivejo: https://lists.ubuntu.com/archives/kubuntu-devel/2015-July/009767.html | 21:13 |
Riddell | fewcha: um dunno depends where it installed to | 21:13 |
clivejo | oh Im not on that list | 21:14 |
fewcha | Riddell: I cloned qt5 in my home, and ran make from there | 21:15 |
fewcha | there as in ~/qt5 | 21:15 |
Riddell | clivejo: ah hah, time to join :) | 21:15 |
fewcha | I was following https://wiki.qt.io/Building_Qt_5_from_Git | 21:15 |
Riddell | fewcha: so it'll be somewhere in ~/qt5 I guess, find ~/qt5 -name qmake | 21:15 |
fewcha | according 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 |
fewcha | so I didn't do make install | 21:16 |
fewcha | okay | 21:16 |
fewcha | Riddell: https://paste.kde.org/psqwfimvg/qop0iu | 21:17 |
Riddell | fewcha: so /home/sanjiban/qt5/qtbase/bin/qmake | 21:17 |
fewcha | Riddell: okay so I just need to run that binary | 21:18 |
Riddell | I guess so, I've done it myself | 21:18 |
fewcha | Riddell: okay, so https://paste.kde.org/picb6dcpy/bvyo9h | 21:20 |
Riddell | looks like it's working | 21:21 |
fewcha | Riddell: Isn't it showing there that its usage is incorrect? | 21:21 |
Riddell | it's saying you need to specify I guess, dunno I avoid using qmake as much as possible | 21:23 |
fewcha | Riddell: okay, but do you remember that when you did it, what did you write there? | 21:24 |
Riddell | if I run qmake in a directory with a .pro file it'll make a Makefile | 21:24 |
Riddell | if I run it in a directory with just qt source files it'll write a .pro file | 21:25 |
fewcha | Riddell: the directory from which I am running qmake, contains only binaries, and one qt.conf | 21:26 |
fewcha | directory = ~/qt5/qtbase/bin | 21:27 |
fewcha | Riddell: Running qmake says that it's usage should be like: /home/sanjiban/qt5/qtbase/bin/qmake [mode] [options] [files] | 21:28 |
fewcha | Riddell: 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 |
Riddell | fewcha: it depends on what's in the directory you are running it | 21:29 |
Riddell | what do you want it to do? | 21:29 |
fewcha | I want it to make my system's qt with this qt built from source | 21:30 |
fewcha | sorry | 21:30 |
fewcha | I want it to replace my system's qt with this qt built from source | 21:31 |
fewcha | Riddell: so that qmake --version shows me Qt 5.5 rather than Qt 5.4 | 21:32 |
sgclark | hi from Spain.. | 21:42 |
soee | hiho sgclark :) | 21:42 |
soee | first time in Spain ? | 21:43 |
sgclark | yes | 21:47 |
clivejo | hot? | 21:51 |
sgclark | nice breeze, not so bad. but have not been awake much yet haha. long flight(s) | 21:57 |
santa_ | sgclark: which city? | 22:17 |
ahoneybun | santa_: should be la coruna | 22:17 |
santa_ | already? welcome then | 22:18 |
sgclark | yeah already lol... guess we will explore some | 22:19 |
santa_ | thats good, I think this city is safe in general at night | 22:21 |
santa_ | (probably you should be more careful in other cities of the world XD) | 22:22 |
sgclark | where 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 |
sgclark | gonna try and sleep some so my schedule is not to bonkers this trip. see you all in a few hours. | 22:29 |
santa_ | good night | 22:34 |
shadeslayer | sgclark: is the weather soupy there too | 22:39 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!