=== Guest33512 is now known as jalcine
=== jono is now known as Guest27980
soeegood morning06:17
Riddellgood morning Kubuntu!07:54
Riddellcmollekopf: did the packages work?08:12
cmollekopfRiddell: yes, thanks08:12
yofelmorning folks08:19
Riddellhi tariq, how's the support website doing? anything I can do to help?08:21
lordievaderGood morning.08:25
RiddellScottK: did you get a chance to look at the owncloud sru?08:36
shrinigood morning Riddell08:57
Riddellhi shrini09:01
Riddellshrini: did you get your install bug in or do I need to review it?09:01
Riddellagateau: same question ⇈09:05
agateauRiddell: I don't understand the question09:10
Riddellagateau: you had a merge request for ubiquity? is that still needing review?09:10
agateauRiddell: I haven't received any comment, so I guess it does. Note that I pick you out of habit for reviews, but feel free to point me to someone else if you are too busy :)09:12
Riddellthat's all good, I'll get onto them09:12
=== KRF_ is now known as KRF
smartboyhwHello Riddell yofel 11:12
BluesKajHey all11:36
Riddellshadeslayer_: using i-7ae84810 ec2?12:05
smartboyhwRiddell, how about lang packs?:P12:08
Riddellsmartboyhw: onto them now12:31
Riddellsmartboyhw: uploading12:32
smartboyhwRiddell, plz review amarok in my main PPA plz12:37
smartboyhwAnd don't give me packaging jobs for the coming two days plz, I'm soon off to London.12:37
RiddellLondon?  big and smelly place, come up to Edinburgh!12:43
Riddellsmartboyhw: where's amarok?12:43
Riddellah found it thanks https://launchpad.net/~smartboyhw/+archive/ppa12:43
Riddellsmartboyhw: uploaded, thanks for packaging, have fun in England (but if you hear anyone say that tennis chap is English, set them straight)12:52
markeyif anyone complains about Amarok crashing on startup with KDE 4.11, please point them to Amarok 2.8-beta12:53
markeyit's no longer crashing12:53
markeytechnically it's sort of a Plasma regression, but anyway, we are now compatible with that12:53
RiddellI wonder if we need to backport that to any PPA12:54
Riddellmarkey: so amarok 2.7 crashes with plasma 4.11 ?12:54
yofelit doesn't12:54
* apachelogger goes Oo12:54
markeyon a related note, apparently lots of KDE applications, including Amarok, are crashing on Ubuntu/Unity with latest updates. no idea why. with Kubuntu everything is fine12:54
yofelwe have the patch for that for 2 weeks already 12:54
markeyRiddell: yes. if you would like to backport a patch, I can point you to the commit12:55
apacheloggerxnox: pingy12:55
apacheloggeryofel: pingy12:55
apacheloggershadeslayer_: pingy12:55
yofelmarkey: right, what you're seeing is bug 1195007 - I think caused by fixing bug 118006712:55
ubottubug 1195007 in kile (Ubuntu) "kile crashes when click on "file new + save"" [Medium,Confirmed] https://launchpad.net/bugs/119500712:56
ubottubug 1180067 in qt4-x11 (Ubuntu Raring) "No icons on buttons" [High,Fix released] https://launchpad.net/bugs/118006712:56
yofelapachelogger: pong (more or less)12:56
apacheloggeryofel: did you confirm that the qt patch is what causes the crashery?12:56
yofelI confirmed that upgrading *only* qt on raring makes it crash - that's as much as I had time for12:56
xnoxapachelogger: hi.12:57
markeyyofel: that could be it, yes. the backtraces are usually inconclusive. just some X error and then it's crash12:58
apacheloggerScottK, xnox, Riddell: the SRU for bug 1180067 (in theory) makes all KDE software crash, it should get rolled back asap12:58
ubottubug 1180067 in qt4-x11 (Ubuntu Raring) "No icons on buttons" [High,Fix released] https://launchpad.net/bugs/118006712:58
Riddellum, wow12:58
yofelthat patch registers gtk's x error handler for Qt/KDE apps it seems12:58
apacheloggerI am seeing some 20 upstream reports already12:58
ubottucjwatson, jdong, pitti, skaet, ScottK, kees, Daviey, pgraner: reporting regression in a stable release update; investigate severity, start an incident report, perhaps have the package blacklisted from the archive12:58
yofeland gdk_x_error() is FATAL12:58
apacheloggerspread across all of kde12:58
markeyso it seems that Ubuntu devs don't give a shit about Qt apps working right?12:59
xnoxthat list of people needs updating as well.12:59
xnoxmarkey: please, use appropriate language. and Qt is cared about a lot, it's pushed as the default development toolkit for ubuntu.13:00
ScottKxnox: We'll need to revert that unless you have an immediate fix.13:09
ScottKxnox: To be clear though, Canonical is pushing Qt5, not Qt4, so that's not quite true.13:09
ScottKxnox: The regression alert ought to be on #ubuntu-devel since most of those people don't hang out here..13:11
xnoxScottK: sure, but I have no idea how to start and properly record an incident report for SRU regression. And I only sponsored that SRU for mitya. I'm not expecting gdk to error out the way it is reported to be doing.13:11
xnoxScottK: can you coordinate a revert on #ubuntu-devel? or what needs doing here?13:12
ScottKxnox: No.  I have $work to do today.   13:12
ScottKSince you sponsored it, please follow up on #ubuntu-devel.13:12
=== rdieter_ is now known as rdieter
xnoxapachelogger: yofel: it seems like https://developer.gnome.org/gdk/unstable/gdk-General.html#gdk-error-trap-push could be used...13:20
smartboyhwRiddell, I know, it's British rather:P13:21
apacheloggerxnox: I think that has too limited scope... it would need to be ::QApplication -> trap_push; ::~QApplication -> trap_pop13:22
smartboyhw(Well, you can't deny that Andy Murray is British right????)13:22
xnoxapachelogger: if I understand it right, callking gdk_error_trap_push() right after gtk_init, should be sufficient without ever doing a pop.13:24
xnoxapachelogger: that's the solution that libreoffice went for as well.13:25
apacheloggerxnox: I am all for giving it a try, but first I would really push a revert into -updates anthen have a possible fixed fix go through proposed again13:27
xnoxapachelogger: well Riddell wants to revert as well.13:28
xnoxapachelogger: do that.13:28
apacheloggerit has quite the sizable impact, so the longer we don't have a fix the more grumpy upstream KDE gets13:29
apacheloggerRiddell: are you handling the revert?13:29
smartboyhwRiddell, hmm13:31
Riddellapachelogger: yep13:34
smartboyhwRiddell, ftbfs of amarok in armhf13:34
smartboyhwObviously, amd64 successfully built13:36
smartboyhwSo um13:36
apacheloggerbuild log?13:36
smartboyhwapachelogger, not qreaal13:36
smartboyhwBuild dep at cmake13:36
=== BadDesign is now known as Guest85226
Riddellno, cmake13:36
smartboyhwapachelogger, https://launchpad.net/ubuntu/+source/amarok/2:2.7.90-0ubuntu1/+build/4778138/+files/buildlog_ubuntu-saucy-armhf.amarok_2%3A2.7.90-0ubuntu1_FAILEDTOBUILD.txt.gz13:36
RiddellCMake Error at /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:108 (message): Could NOT find Qt4 (missing: QT_QTOPENGL_INCLUDE_DIR QT_QTOPENGL_LIBRARY)13:36
apachelogger  Could NOT find Qt4 (missing: QT_QTOPENGL_INCLUDE_DIR QT_QTOPENGL_LIBRARY)13:37
apacheloggermarkey: ^13:37
smartboyhwWhat the hell13:37
apacheloggeramarok is no longer compatible with ARM13:37
apacheloggeras there is no desktop opengl on ARM13:37
markeywell, who wants to run Amarok on Arm at this point13:37
apacheloggerI do13:38
Riddelldon't think that's amarok fault13:38
Riddelloh it needs opengl?13:38
ScottKTo be fair, not compatible with Ubuntu's Arm.13:38
apacheloggermarkey: easy fix would probably be to simply make the opengl stuff optional13:38
apacheloggerif you care at all13:39
markeyI'm not sure I care that much, for the tiny amount of people trying to run it on ARM13:39
apacheloggerlibqt4-opengl-dev [!armel !armhf]13:39
apacheloggerwhy is that in there at all13:39
markeyif it were a larger audience, then yes13:39
markeyit felt really good to be able to make OpenGL a hard dependency, in 201313:40
Riddellapachelogger: cos it doesn't work on arm and clashes with gles13:40
apacheloggerRiddell: qtopengl doesn't work on arm?13:41
yofelit doesn't from what I've seen in build logs13:42
markeyrelated note: QGLWidget doesn't work right with EGL (it crashes). that's something I'm very interested in13:42
markey(at least on Gentoo it crashes)13:42
xnoxbug 70779413:51
ubottubug 707794 in clementine (Ubuntu) "libqt4-opengl on armel should be compiled with OpenGL ES 2.x support" [Undecided,Triaged] https://launchpad.net/bugs/70779413:51
xnoxnote a few packages are still not fixed / do not support GLES13:51
xnox(or have dependencies which are GL only, without GLES ports)13:52
apacheloggeryofel: kf5 project-neon5-plasma-framework should be building soonishy....... if you want to give it a shot, something with the neon envrionment files is fishy as they alone do not allow me to run plasma-shell, adding the stuff form the wiki additionally makes it work14:03
apacheloggerdidn't work in vbox though, so I suggest native tests14:03
yofelI'll check the list of env vars again, but I thought I added everything...14:05
markeyapachelogger: regarding ARM, I was just reconsidering. I think I can make OpenGL optional for 2.8-final. I'll look into it tonight14:12
markeyok, bbl14:12
apacheloggermarkey: would be very appreciated :)14:12
Riddellagateau: on https://code.launchpad.net/~agateau/ubiquity/kde-rework-try-install-buttons/+merge/172988 ...14:28
Riddellyou add try-install.svg is that used anywhere?14:28
Riddellor is it just the source?14:28
agateauRiddell: it is the source for the new .png files14:29
agateauno need to ship them in the deb14:29
Riddellagateau: how did you test running ubiquity with the buttons?14:30
* xnox started to simply use .svg files directly instead of pngs.14:30
RiddellI tried export UBIQUITY_GREETER=1 but that doesn't help14:30
agateauRiddell: UBIQUITY_GREETER=1 ubiquity -d kde_ui14:30
agateauoh, that works for me14:30
ScottKshadeslayer_ and yofel: What did you tell afiestas_ we thought about KDE switching to a 3 month release cycle?14:31
Riddellagateau: hmm it doesn't work, and it runs in oem mode, wonder why that is14:31
agateauRiddell: haven't tried it with latest saucy, let me try14:31
ScottKafiestas_: Do you have a sample release schedule?  Perhaps you could take the 4.11 schedule and overlay it with what you'd expect if there had been two three month releases instead of one 6 month one?14:32
afiestas_ScottK: wiki page_14:32
yofelScottK: I don't think I explicitely talked to afiestas_, but my position is mostly "I don't care". The schedule I saw didn't really conflict with our 14.04 plans14:32
ScottKafiestas_: Link?14:32
yofeljust different kde version number14:32
afiestas_ScottK: it is in the email14:32
ScottKyofel: No, I think that's wrong.14:32
afiestas_dafuq, nobody has read the wiki or what?14:32
agateauRiddell: indeed, doesn't work14:32
ScottKThanks.  Looking14:32
Riddellit doesn't conflict but I'd like to look at it for cadance, each SC release takes a long time to package14:33
agateauxnox: did anything change wrt the UBIQUITY_GREETER env variable?14:33
yofelif anything the support duration for bugfixes would be an issue14:33
xnoxagateau: not that I know. I usually go to tty1, stop lightdm; stop ubiquity; pkill -9 X; update files in place; start ubiquity: to see the greeter again.14:34
* agateau investigates14:34
xnoxagateau: we now use pkexec, which clears environment better I think, instead of kdesu / gtksu /sudo14:34
yofelafiestas_: any reason why you went with 2 point releases for .13 and 3 for .14? Because we won't care much about .14 from what I see14:35
agateauxnox: ah, could be it14:35
ScottKLooks like 4.13 would release ~a week or two before "T" feature freeze.14:36
ScottKThat's substantially later in the cycle.14:36
agateauxnox: Riddell: there is a "-g" option for the command line, which works for me14:37
afiestas_yofel: that image is a sample14:37
afiestas_it will continue as long as it takes us to release kde514:37
Riddellagateau: oh nice14:37
yofelafiestas_: sure, but as we don't push new features out as updates, if we release with .13 in april, and you then focus all your fixing attention to .14 until frameworks is done that's not really great for us14:39
afiestas_yofel: right, I want us to develop a script or something you guys can use to keep branches alive, and do further releases14:40
afiestas_if we had a site for example, listing bug fixes for example, you could easily backport those and we could do more releases14:41
afiestas_pretty much like we have done with some 0.5 and 0.6 that were not shceduled14:41
ScottKWhich might work, except with more releases, different distros will target different releases and so you end up with double the work.14:42
afiestas_accorcing to the release team (which I plan to join to help them) it won't be that much work14:43
afiestas_since point releases are almost automagical14:43
afiestas_as long as we have people caring about them14:43
afiestas_we have an issue now, that is impacting you (distros) and it is that nobody testes stable branch14:43
afiestas_so we need people that will take "maintainership" of these branches14:44
ScottKWhat's why we put the point releases in a PPA for people to test before we put them into the regular updates cycle.14:44
afiestas_and ofc we need to make life easy to these maintainers14:44
Riddellagateau: getting icons back on the buttons would be a nice addition if you happen to be still in ubiquity mood :)14:54
yofelafiestas_: on the stable branch topic: how can I list all commits done to 4.10 since it was branched? (that means including commits from all repositories that had commits to KDE/4.10 and including the svn branch)14:54
Riddellagateau: 1 merge merged and 1 merge commented although I think a comment from a ubiquity gtk person on the splitting one would be needed before going ahead14:55
agateauRiddell: thanks!14:55
agateauRiddell: will look into the icon issue14:55
agateauRiddell: it's new to saucy, isn't it?14:55
Riddellagateau: I think those went away when I switching it to a QApplication a couple of cycles ago14:55
Riddellhad to get rid of KButton14:56
agateauRiddell: there are icons on button here: http://agateau.com/2013/04/11/hacking-on-ubiquity/ubiquity2.png14:56
Riddellagateau: hmm, but on when I run it on my installed saucy system, I wonder what's going on14:57
afiestas_yofel: yes, even though the idea is to make it even nicer14:58
afiestas_something like 14:58
agateauthat's why I think it's a regression in saucy14:58
afiestas_a website or something14:59
afiestas_or even with email alerts to kde-packagers14:59
afiestas_right now that's done manually I think14:59
afiestas_(with a CCMAIL)14:59
yofelafiestas_: right. I would be even happy with a seperate ML for all stable commits. I gave up on trying to filter kde-commits.15:03
yofelBut yeah, if we could have some kind of notification that somebody fixed something in a stable release (esp. post-last-point-release) that would be incredibly helpful15:03
afiestas_yofel: please, send that kind of feedback to kde-core-devel thread15:04
afiestas_so we can add it to the proposal15:04
yofelright, will do15:06
Riddellagateau: just tried 13.04 on a virtual machine and the icons aren't there http://starsky.19inch.net/~jr/tmp/ubiquity.png15:08
agateauRiddell: I wonder if this could be linked to running ubiquity from the live session versus running it from the dm15:09
agateauRiddell: that is: do you get icons if you select "try kubuntu", then start ubiquity from the desktop icon?15:10
Riddellagateau: let me try15:15
Quintasanany ideas where to debug when pc suddenly shuts down by itself and I get no messages after reboot?15:18
smartboyhwQuintasan, :I15:18
QuintasanI'm praying it's the hdd but who the hell knows15:19
Riddellagateau: yes exactly right15:22
Riddellagateau: icons show when in live session then ubiquity but not standalone ubiquity15:23
agateauRiddell: in raring, I changed code to use QIcon.fromTheme() instead of hardcoded full paths, that must be the reason why15:24
agateauMy guess is the theme is not set when ubiquity is running standalone15:24
Riddellyeah, I wonder how that gets set15:24
Riddellmust be something in QIcon that does it15:24
agateaummm, maybe qapplication does not detect the environment it is running on and cannot pick a theme15:27
agateauwhich would make sense because there is nothing kde running at this point15:27
agateauanyway, I don't get icons at all on saucy :/15:30
tsdgeosScottK: "Either they do have to change and do releases every three months or elements15:32
tsdgeosof the SC get skipped on some releases."15:32
tsdgeoswho is they?15:32
yofelas I understood: e.g. kdepim15:32
ScottKtsdgeos: In this case it's kdepim.15:32
tsdgeoskdepim doesn't do any release 15:32
tsdgeosthe release team does15:32
tsdgeosall they do is increase a version number when we send them an email15:33
ScottKRight, but their repo has to be in a releasable state.15:33
yofelthey release features - aligned to the schedule the release team sets15:33
tsdgeosScottK: repos *always* have to be in a releaseable state15:33
ScottKThere are rules about when features can land, string changes, etc.15:33
ScottKSo I don't think it's right to suggest that changing the release cadence won't affect them.15:34
tsdgeosyou sound like a spanish politician :D15:34
tsdgeosbut it's on the constitution!15:34
tsdgeosScottK: is people suggesting it won't affect them?15:35
ScottKThat's how I read afiestas_' email.15:35
ScottK"You don't have to change the way you work because of this."15:36
tsdgeosand you don't15:36
tsdgeosnoone follows the damn freezes anyway15:36
* ScottK gives up.15:43
tsdgeosScottK: see how laurent says "i just commited a feature for 4.11"15:43
tsdgeoswhat? why? how?15:44
tsdgeosfeature freeze was months ago15:44
ScottKI agree.15:44
tsdgeoshe doesn't understand than a shorter release cycle will be better for him15:44
tsdgeosbecause he won't need to "do it now or wait 6 months to get it released"15:44
tsdgeosit'll be "do it now or wait 3 months to get it released"15:44
tsdgeosso he'll wait and do it proprely15:44
tsdgeosScottK: giving up is what happens when someone proposes change, because people just say "it's not what we do" without even thinking about it15:45
ScottKIts' when someone says two things that can't both possibly be true and people continue to claim it is..15:46
ScottKEither I don't understand or people are just pushing for change no matter the consequence.  I don't know which this is.15:46
tsdgeospeople are pushing?15:47
tsdgeosi only see afiestas_ :D15:47
tsdgeosScottK: you didn't give much info on why kubuntu had problems either15:48
tsdgeos"Let's not do it again"15:48
ScottKLike I said, I don't see how it's possible to both not affect developers and release twice as often, but that may be just me.15:48
tsdgeosseems like a "no because no"15:48
ScottKI think the problems with kdepim were felt by many distros and we discussed it at the time.15:49
yofelkdepim in 4.7 was buggy, really buggy, seriously. And looking back I regret uploading it back then15:49
ScottKIIRC Fedora people like rdieter objected even more than we did.15:49
yofelwe lived through it, but I would very much like to not have something like that happen again15:49
tsdgeosand that has to do what with this?15:49
tsdgeosif 4.7 was buggy 15:49
tsdgeosits code should not had been merged15:50
ScottKyofel: Agreed, but I was talking about 4.5/4.6 where we had no pim.15:50
ScottKIt was always hard to figure out what pimlibs went with what.15:50
yofelright, it was out-of-schedule back then15:50
yofeltsdgeos: ^ and that's the thing we fear. If people start making changes thinking "they have until the next cycle", then things can either be better because they're better tested, but they can also get worse because we get an even larger untested code chunk15:51
yofelno idea what the best way to prevent that is though15:51
tsdgeosyofel: how there can be a larger untested code chunk if there's half the time?15:52
tsdgeospeople is going to chunk code faster magically?15:52
yofeltsdgeos: I meant if they skip a release15:52
yofeli.e. a feature is still developed for half a year, not in 3 months15:52
yofellike kdepim did with their rewrite from 4.4 -> 4.615:53
tsdgeosyofel: you *can't* skip a release15:53
yofelkdepim did15:53
tsdgeosthat's a good keyword15:53
ScottKAll I was saying is we tried skipping and it was painful.15:53
tsdgeosyou said "Let's not do it"15:54
yofelI have a tendency to expect people to do something again if they do it once. If you plan to prevent it: *great*, but understand that I'm skeptical15:54
ScottKOK, I said we tried skipping and it was painful, let's not do it again.15:54
tsdgeosi don't unerstand what you mean by skipping15:55
tsdgeosbut if you mean a module not being released15:55
tsdgeosthat's not going to happen15:55
ScottKThat's what I mean.15:56
tsdgeosif you mean kubuntu not releasing something15:56
tsdgeosthat's your issue15:56
ScottKI mean a module not being released.15:56
afiestas_ScottK: that won't happen15:56
yofelnote that I count "a module not merging any feature branches for a release", skipping a release too in that context15:56
afiestas_it can happen that some developer decides to work on 6 month cycles, mergin features using that timeline, but the module will be released anyway15:57
afiestas_using the example in kde-pim, 4.12 will contain my kde-accounts patches, but won't contain some laurent features because they won't be ready15:57
afiestas_but in anyway 4.12/13/14/15 will be released15:57
tsdgeosyofel: why?15:57
tsdgeosyou are going to force people to develop stuff?15:58
ScottKyofel: I disagree with you there.15:58
yofeltsdgeos: what would have prevented you from calling "kdepim 4.4.11" "kdepim 4.6"?15:58
tsdgeoswhat kind of question is that?15:58
yofelnvm me, maybe my trauma from kdepim 4.6 was just too large so I'm unable to be properly objective here.16:00
yofeltsdgeos: I'm just scared about a "feature" getting too large (e.g. kdepim rewrite) so it's not going to be properly stabilized in *one* kde release timeframe (including point releases).16:02
yofelBut I guess there's nothing one can do about that16:02
QuintasanAre we going to push 4.10.5 to raring?16:02
yofelQuintasan: yes16:03
ScottKQuintasan: Are there positive test results from PPA users?16:03
yofelRiddell: did you apply those kolab patches to the SRU packages too?16:03
QuintasanScottK: From me - it works16:04
smartboyhwScottK, soee did report that 4.10.5 was good here...16:04
QuintasanI can get someone else to test16:04
ScottKAny bugs on ~kubuntu-ppa that need review?16:04
Riddellyofel: i should have done to all the PPA versions yes16:04
ScottKIf not, then I think it's fine to push it to -proposed.16:04
yofelQuintasan: bug 1198754 needs looking at possibly16:05
ubottubug 1198754 in Kubuntu PPA "Please pull rev ec8e405c to fix memory leak in 4.10.x" [Undecided,New] https://launchpad.net/bugs/119875416:05
Riddelle.g. 4.10.5 has them here https://launchpad.net/~kubuntu-ppa/+archive/ppa/+packages?field.name_filter=kdepim&field.status_filter=published&field.series_filter=16:05
yofelRiddell: ok, thanks!16:06
ScottKyofel: We should definitely have that.16:10
yofelQuintasan: mind cherry-picking that? If you have no time I'll do it later16:14
ScottKHow hard would it be to have a PPA that did a recipe build on change for the stable branch?16:42
ScottKPeople interested in the latest stable/testing could run that and it would be reasonably safe.16:42
RiddellScottK: on change of anything in stable branch?16:44
Riddella neon-stable16:44
ScottKExcept I don't think it would need to be separate packages like Neon is.16:44
QuintasanRiddell, ScottK: Any ideas on why we have firefox-locale-en on the CD?16:45
ScottKQuintasan: No.16:45
QuintasanOr it's quite possible the installer pulled it with internet connection16:45
yofelScottK: I think I already explained that to d_ed on kde-quality or so a while ago. Essentially: imports of all stable branches + our SRU packaging in branches + recipes for that16:45
ScottKyofel: Yes.16:46
yofelnot too much work, but still enough that I want to have a confirmed userbase before doing that16:46
ScottKI'm thinking if we did that, maybe we could send a point release straight to proposed since we'd have tested it already.16:46
yofelhm, good point16:46
ScottKSo it would ~replace the updates PPA.16:47
QuintasanHell, I could run taht16:48
* Quintasan was running neon16:48
Quintasanso why not16:48
yofelI have a recipe creation script in the neon tools, that would have to be extended to run on the whole KDE SC16:48
yofelthen we need a name pattern for the SRU branches16:49
yofelimport creation and recipe creation script that is16:49
ScottKapachelogger is our namespace master, right?16:49
yofelright, at least he's better at that than I am ^^16:49
ScottKIn any case, something like this could help with the "no one tests stable" problem, regardless of if the release schedule changes or not.16:52
* Quintasan whines16:57
QuintasanThis !@#!@%! PC16:57
QuintasanWhen I want to debug this bastard - everything works16:57
QuintasanWhen I was to do anything - shit hits the fan16:58
yofelsounds familiar16:58
QuintasanAt least I have an SSD now16:58
QuintasanI can finally kill the only PATA drive now16:59
ScottKCan someone test the qt4-x11 in raring-proposed?17:01
ScottKIs I can get a positive test, I'll release it once it's built on all archs.17:01
Riddellpresumably testing with unity is what's needed17:02
ScottKxnox: ^^^17:02
* ScottK will be away for awhile.17:02
xnoxScottK: Riddell: I don't have access a raring instance. I would have thought the testing that needs to happen is that kile doesn't crash with empty config.17:09
ScottKxnox: But not in Kubuntu.  In Unity.17:09
xnoxoh... wait, yeah under !kde 17:09
ScottKCan you find someone to test?17:09
xnoxScottK: there are many "me too" on bug #119500717:10
ubottubug 1195007 in qt4-x11 (Ubuntu Saucy) "kile crashes when click on "file new + save"" [High,Confirmed] https://launchpad.net/bugs/119500717:10
ScottKxnox: I need to leave and I was hoping someone would get it tested so I can release it when I get back.17:10
xnoxScottK: is there an "SRU accepted template" / call for -proposed testing that you can post there?17:11
apacheloggerScottK, yofel: namespace for what?17:40
ScottKSRU branches for KDE SC packages.17:43
Quintasanyofel: I copied Win7 partition from my HDD to SSD, now I have two grub entries, doesn't matter which I press it still boots from the hdd xD17:45
ScottKxnox: https://bugs.launchpad.net/ubuntu/+source/kile/+bug/1195007/comments/1017:45
ubottuLaunchpad bug 1195007 in qt4-x11 (Ubuntu Saucy) "kile crashes when click on "file new + save"" [High,Confirmed]17:45
apacheloggerScottK, yofel: ~kubuntu-packagers/kubuntu-packaging/phonon-raring in case you mean the packaging17:55
yofelQuintasan: doesn't seem like you migrated the win7 boot manager entries properly17:56
Quintasanyofel: This retarded software overwrote my Kubuntu partition on SSD :D17:56
QuintasanEven though I specifically asked it to restore it to the second paritition17:56
QuintasanThe biggest problem with win7 is that the installer is so retarded it won't install unless your hdd is master on the first channel and you install it on the first partition17:57
* yofel never touches win7 unless he has to17:58
yofelactual my notebook's win7 install is still on it's own HDD, I simply switch the disks out when I need it17:58
Quintasanwell, that's a solution17:58
QuintasanI actually need to do someting about my disks17:58
QuintasanI have overlapping partitions somehow17:59
yofelthere was a grub2 bug where e.g. photoshop overwrote parts of the boot manager data (well, the win7 boot manager doesn't put data there so it's fine right?)17:59
yofelsince then I never dual boot linux and windows from one disk17:59
Quintasanlinks to that17:59
* genii ponders this mid-boggling possibility of photoshop boot loaders18:00
Quintasangenii: wat18:00
geniiQuintasan: I'm not sure why anyone at Adobe thought it might be a good idea. That's why I'm finding it mind-boggling they would store data in the mbr or so18:01
Quintasanyofel: btw, did I tell you about one core missing from my CPU?18:02
yofelQuintasan: bug 441941 - fun read18:03
ubottubug 441941 in grub2 (Ubuntu) "grub fails after running Windows" [High,Triaged] https://launchpad.net/bugs/44194118:03
yofelgenii, Quintasan: obvious reason: Adobe OS18:03
* genii watches http://www.youtube.com/watch?v=QyR1MLI_6Ig for enlightenment18:05
shadeslayer_genii: yofel Quintasan it's akin to shipping a SDK IMHO18:07
shadeslayer_"Here's an env that will work everywhere (TM)"18:07
Quintasanyofel: anyways, I noticed Linux and Win7 stopped showing 4 cores18:08
yofelshadeslayer_: please don't say that, otherwise I'll start looking funny at ubuntu-sdk >.>18:08
QuintasanI was like: well, fcks, okay can live with that but shouldn't the cpu die?18:09
shadeslayer_yofel: hehe18:09
QuintasanImagine my face today when I boot the damn machine and it has 4 cores18:09
yofelQuintasan: wat?18:09
Quintasanquite close, got an image to accomapny that?18:09
Quintasansince I have one18:09
yofelI think we're thinking of the same one ^^18:10
QuintasanI sometimes seriously wonder if it's me having bad luck or emmiting some kind of aura that makes pc parts behave in a completeely retarded manner18:11
geniiyofel: Seems to be some firefox os offshoot18:11
Quintasanyofel: btw, I can't unlock my screen in KDE now18:11
=== cmagina_away is now known as cmagina
shadeslayer_<3 that image18:11
QuintasanIt keeps saying wrong password every damn time :D18:11
yofelQuintasan: official KDE?18:12
shadeslayer_you were hax0red18:12
* yofel remembers that in neon with the old locker18:12
Quintasanyofel: Yeah18:12
yofelbut I think the new one works differently18:12
QuintasanAs in our packages18:12
yofelnot good :S18:12
shadeslayer_Quintasan: coming to Akademy right?18:12
Quintasanshadeslayer_: No.18:13
QuintasanI'm going to be bothering you online18:13
Quintasanyofel: No idea how to debug this, currently I'm logging in via tty and killing it with dbus18:14
yofelme neither, maybe ask in #kde-quality if someone's awake there18:15
Quintasanshit, if my 2x1TB drives die then I'm in a world of suffering18:15
* Quintasan backsup his keys18:15
yofel  xserver-xorg-input-all xserver-xorg-input-synaptics xserver-xorg-video-all xserver-xorg-video-ati xserver-xorg-video-cirrus xserver-xorg-video-intel xserver-xorg-video-mach6418:16
yofel  xserver-xorg-video-r128 xserver-xorg-video-radeon18:16
yofeler, prepend "The following packages will be REMOVED:"18:16
yofelthanks saucy for removing the video driver I'm using18:16
QuintasanDO IT18:17
QuintasanDO IT18:17
yofeldon't wanna ;P18:17
QuintasanYou have to18:17
shadeslayer_yofel: wasn't there a thread about this on ubuntu  devel18:21
yofelshadeslayer_: yeah, but this isn't that but self caused because I had a bit of an unsupported setup on raring here >.>18:22
QuintasanThis is getting worse18:37
QuintasanIt automagically turn off by itself18:37
QuintasanCPU temp is not reaching high levels (30*C)18:37
Quintasan30-40 more likely18:38
QuintasanGPU is not overheating too18:38
yofelresetting or actually powering off?18:38
* Quintasan looks for screwdriver18:39
Quintasanyofel: it powers off then boots after two seconds18:39
shadeslayer_cp: cannot stat 'debian/tmp/usr/bin/akonadi_kolabproxy_resource': No such file or directory18:39
Quintasanyeah, and it won't boot normally since I have to do a little trick to let it boot18:39
Quintasanas in I turn off the switch on the power supply, press the power button so it tries starting with the remainder of electricity in the circuits and then immediately turn on the switch on the power supply18:40
Quintasansounds stupid but it works18:41
Quintasandon't ask me why18:41
yofeland what does it do if you start it in a normal way?18:41
Quintasaneverything gets powered on18:42
Quintasanfans, disks etc18:42
Quintasanbut I get no video output18:42
Quintasanas in,  I can't even see POST screen18:42
QuintasanWhen I do the retarded power supply trick it works18:43
QuintasanI think it's time I just reassemble it18:43
QuintasanThis was the first and the last time I actually let someone else build a PC for me18:45
apacheloggerQuintasan: short circuit? :P18:46
Quintasanapachelogger: How do I go about determining whether that's the cause?18:47
Quintasanwouldn't that actually damage my hardware?18:48
RiddellScottK: xnox: qt update verified on my computer in bug 119500718:49
ubottubug 1195007 in qt4-x11 (Ubuntu Saucy) "kile crashes when click on "file new + save"" [High,Confirmed] https://launchpad.net/bugs/119500718:49
shadeslayer_!find akonadi_googlecalendar_resource saucy18:50
apacheloggerQuintasan:  it would if it didn't shut down ^^18:50
ubottuPackage/file akonadi_googlecalendar_resource does not exist in saucy18:50
apacheloggerQuintasan: disassamble, reassmble18:50
Quintasanapachelogger: Well, I'm going to do that with the exception of CPU18:51
* yofel once had a PSU short circuit on him - but you *smelled* that18:51
shadeslayer_Quintasan: make sure everything is slotted properly18:51
yofeldunno why the hardware survived actually18:51
shadeslayer_my RAM didn't go all the way in and the machine didn't even POST and left me puzzled for quite a while18:51
Quintasanhow the flying fcks do you demonunt this?18:53
Quintasanthings on top are not screws18:54
yofelsee the black parts where it's connected to the mainboard. There's usually some trick to unlock the hooks18:55
QuintasanI'm not sure if I will be able to assemble it again18:56
* Quintasan doesn't touch that for now18:56
ScottKRiddell: was that in KDE or Unity?19:00
yofelScottK: I can verify that ubunt9.2 makes kile work in unity19:01
yofeland someone else confirmed that just now19:02
ScottKI'll release it once it's built. 19:04
Quintasanyofel, shadeslayer_: It still doesn't boot normally19:57
QuintasanI'm probably going to find someone with more powerful PSU to see what happens19:57
QuintasanSince I have to provide additional power to it19:58
Quintasanit just restarted when sitting on login screen19:58
QuintasanI'll try it19:58
yofelin case dmesg ever showed random segfaults19:58
QuintasanIt didn't19:58
QuintasanThat's the problem19:58
QuintasanI can't even get a proper fucking failure message from the system before it goes down19:59
yofelalthough I only recently removed a memory DIMM that was causing system crashes but was error-free in memtest19:59
yofelit also crashed another system so it has to be broken in some way19:59
QuintasanIt's like20:00
Quintasan"Sup bro nothing wro...fuck"20:00
QuintasanPower gets cut for a second or two and then it tries to boot20:01
Quintasanyofel: no errors so far20:11
Quintasanand it didn't reboot20:12
QuintasanWhat the flying fsck20:12
yofelwell, that's how I was feeling too. I left memtest running for a day, 0 errors. Run windows for an hour - BSOD in MEMORY_MANAGEMENT20:12
yofelI'm still not totally sure whether the PC is fine now or not, but without that memory it hasn't crashed yet20:13
Quintasanyofel: Thing is - it doesn't even BSOD or panic20:16
Quintasanthe power gets damn cut for some reason20:17
yofelwell, until I told windows to not damn reboot immediately, my BSOD experience was "oh hi, what can I do for you todaREBOOT"20:18
yofelexcept that I didn't have a moment where it was off completely20:18
yofelScottK: I just remembered why I gave up daily builds of stable kde branches: http://paste.kde.org/79163620:21
yofelI'm just triggering another build of https://code.launchpad.net/~yofel/+recipe/kubuntu-kdelibs-stable. If it breaks again I'll talk to the launchpad people20:21
yofel(or I need hardcoded version strings in the recipe text :/ )20:22
Quintasan5 passes20:56
Quintasanno errors20:56
=== francisco is now known as Guest93946
ScottKyofel: I'm told us recipe format 0.3 instead of format 0.4 may help.23:58

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