[01:43] seems my laptop is broken... [04:49] what's going on with your lappy, ahoneybun? [05:30] Good morning. [06:19] good morning [06:25] * palasso hugs Riddell [07:06] :O [07:08] doko: did kdepim get through proposed on its own now or did someone give it a final poke? [07:12] Riddell: kmix is red btw https://launchpad.net/ubuntu/+source/kmix/4:15.08.0-0ubuntu1 [07:25] sitter, overwrote a hanging autopkg test, but zenshin and akonadi1 were the two last bits [07:25] groovy [07:25] doko: thanks for your help on this [07:27] sitter, next time, please write transition files. the time you spend with that is easily saved later ;) [07:27] * soee reads http://jriddell.org/2015/09/02/jonathan-riddell-ip-policy/ :) [07:30] deadhorsealert.jpeg [07:30] doko: do you have a documentation pointer for writing transition files? [07:35] sitter, https://wiki.debian.org/Teams/ReleaseTeam/TransitionTracker https://code.launchpad.net/ubuntu-transition-tracker/ [07:35] Riddell: LOL [07:35] doko: thanks [07:35] {{{{{{{{{{{{{{{{{hugs}}}}}}}}}}}}}}}} [07:39] Riddell: kubuntu-meta will need update to get rid of now missing kdepim-kresources [07:50] Riddell: http://kci.pangea.pub/job/wily_unstable_rocs/lastFailedBuild/console [07:57] sitter: doing.. [08:13] done! which also added plasma-pa [08:18] * kfunk notes: kontact 5 is a bit broken/crashy [08:38] !info libqextserialport wily [08:38] Package libqextserialport does not exist in wily [08:38] libqextserialport (for marble) - clivejo - Can get it to build locally, but wont upload to LP [08:38] Riddell: can you help clivejo sort the packaging of that? [08:39] I'll e-mail him [08:42] * sitter sent mail about pim stack === sitter changed the topic of #kubuntu-devel to: Plasma 5.4 work in progress. Will be ready soon. | https://trello.com/kubuntu | http://qa.kubuntu.co.uk/ | apps 15.08 https://goo.gl/KFMF4F | 5.4 http://goo.gl/XrOhvc [08:53] sgclark: ping [09:00] sitter: @topic "Plasma 5.4 work in progress. Will be ready soon" isn't it ready and in Wily? [09:02] yes [09:02] someone needs to get on those backports though [09:03] sitter: On the Debian side of kdepim, I'm planning to keep kdepim 4.14.10 in unstable and play with the plasma 5 version in experimental till it can replace the kde4 version. [09:04] ScottK: ^ [09:08] maxyz: that does seem very reasonable [09:09] You are planning to maintain co instabillability till 16.04 ? [09:11] maxyz: we are already not providing co-installability. there is no data migration going on between the two runtimes so any data put into the old kdepim would be lost anyway === Riddell changed the topic of #kubuntu-devel to: Kubuntu: free to share, copy and modify | https://trello.com/kubuntu | http://qa.kubuntu.co.uk/ [09:27] maxyz: can you explain to me the purpose of networkmanager-qt debian/tests/acc ? I don't see an existing acc build to compate anything against so I think it's pointless? [09:27] Riddell: Currently, it tests that the headers compile, that helps finding out missing deps in the -dev package [09:28] Riddell: didn't I already tell you how to fix the acc? [09:28] maxyz: isn't that done at build time? [09:28] maxyz: oh it uses the -dev I see [09:29] sitter: yes and it got further by removing libnm-utils but still seems to fail, I"m investigating [09:29] Can I get the source svg behind http://kubwp.kubuntu.co.uk/wp-content/uploads/2015/03/47Eeknz.png? [09:29] I'm assuming that's based on Vibrant? [09:29] Could someone please tell me the offsets in the original file? [09:29] chalker_: I doubt there's any svg, it's just word kubuntu put on top of the plasma wallpaper [09:30] I used to store the acc dumps in my build machine but it was a bunch of shameful hackery and the checks were mostly useless [09:30] Riddell: what are the offsets there? [09:30] chalker_: no idea [09:30] Riddell: I know about the plasma wallpaper, I have a source svg for that one. [09:30] that acc test should really create an artifact with the actual output, no? [09:30] impossible to debug with the output it generates [09:31] Riddell: My eyes bleedwhen I look at that imageā€¦ [09:31] sitter: It generates a logs dir in the running directory [09:31] It's got both banding and noise, and the lines are aliased. [09:31] maxyz: somehow they don't end up in the artifacts tarball of ubuntu's autopkgtest though, so I suppose they need to be moved somewhere special [09:31] http://autopkgtest.ubuntu.com/packages/n/networkmanager-qt/wily/amd64/ [09:32] Riddell: Ok. Another question: what was the size of the original wallpaper? [09:32] chalker_: I am willing to wager that it wasn't vector drawn but pixel drawn [09:32] If that's based on a png file, I mean. [09:33] sitter: The foreground is fine, the background is bad. [09:33] I have the svg file of the background. [09:33] Just tell me the size that you need. [09:34] chalker_: that wallpaper is ancient history, the new one has some details here https://kver.wordpress.com/2015/07/21/new-artwork-coming-in-5-4-the-tale-of-a-troublesome-wallpaper/ [09:35] sitter: the running directory for the autopkgtest is the uncompressed package directory. I have no idea which dirs you are keeping. It should be trivial to simply cat all the logs on error. [09:35] chalker_: I do not even know who made that banner. ovidiu-florin or ahoneybun might know. and as Riddell indicated, IMO the banner should be redone with new wallpaper anyway s you couldjust go crazy with it ^^ [09:35] Ah, ok. [09:35] I already re-rendered the new wallpapers. [09:35] maxyz: let me ask, but cat-on-errorr seems like a reasonable approach [09:36] I thought that you wanted the old one. [09:36] If you want the Vibrant wallpaper, I could re-render that one. [09:37] maxyz: oh btw, what I wanted to ask a while ago. I recall that the python and ruby teams came up with autopkgtest meta-packages that somehow contain common files to provision testing on any standard python/ruby package. have you looked into that at all? [09:37] the copy-n-paste of debian/tests in all the kf5 packages is really meh considering 99% of the time they require exactly the same stuff anyway [09:38] sitter: Something like: ret=$?; if [ 0 -ne $ret ]; then find logs -type f -print -exec cat '{}' ';'; fi; exit $ret [09:38] chalker_: I don't think anyway would be ungrateful about awesome new artwork instead of awesome old artwork :) [09:40] maxyz: sitter: yes, absolutely; see https://people.debian.org/~mpitt/autopkgtest/README.package-tests.html , your test can put anything into the $ADT_ARTIFACTS dir, and it'll appear in the "artifacts.tar.gz" from autopkgtest.u.c. [09:40] sitter: Could you re-phrase that one, please? =) [09:41] maxyz: depending on how big the logs dir is we could simply log into the artifacts directory [09:42] chalker_: go ahead and make with the new wallpaper [09:42] actually [09:42] Riddell: how about we use the new wallpaper for 15.10? [09:42] sitter: for the website banner? that makes sense [09:43] chalker_: what you could do is re-render the banner with the old wallpaper for Kubuntu 15.04. and do a new banner with the new wallpaper saying Kubuntu 15.10 [09:43] that would be super awesome then :) [09:43] yep [09:43] That wallpaper looks pretty awesome on a 4k monitor. :) [09:44] sitter: I am not good at doing banners, sorry =). I just re-rendered kde wallpapers to remove banding and aliasing. [09:44] But only the two last ones. [09:44] So I was asking you if you need the old one fixed. [09:45] ah yes probably [09:46] chalker_: you'll still need to talk to ovidiu-florin or ahoneybun to find out who has the sources for the banner though [09:46] ovidiu-florin, ahoneybun, ricktimmis: great talk in podcast #4 ! [09:48] sitter: If it's png-based, I will just make you png files. === james is now known as Guest95617 === sitter changed the topic of #kubuntu-devel to: https://trello.com/kubuntu | http://qa.kubuntu.co.uk/ | apps 15.08 https://goo.gl/KFMF4F [09:55] sitter: not like the new topic? [09:56] sitter is a minimalist [09:57] yeah [10:07] sitter, Riddell: It looks like that was 3200x2000 wallpaper. [10:31] chalker_: If we're to replace the old one, I don't see the point in fixing it [10:31] anyhow ahoneybun is the one who made it [10:36] Riddell, sitter: networkmanager-qt's 80d795b1c503fc9bf47539012017bd521116989b, Copy the acc logs to the adt artifacts. [10:40] cool beans thanks [10:40] maxyz: should be copied as acc-logs maybe? [10:40] or do we havemore than acc in there? [10:42] Just the acc output, possibly intermixed with whatever was already in the logs dir. [10:44] hm [10:44] maxyz: so yeah, why not simply log to the artifact directory directly? ^^ [10:45] sitter: how? [10:47] maxyz: I don't see how stuff ends up in logs/ to begin with so I can't really say [10:48] ah well, something to look into eventually [10:48] Riddell: uploading with acc change [10:49] uploaded and pushed [10:49] It's the abi-compliance-checker -q behavior, it can be changed with a entry in the acc file but you'll to mangle it to expand the env var. [10:51] ah [10:53] maxyz: so yeah, I'd `cp logs -r ${ADT_ARTIFACTS}/acc-logs` to have it reflect that this is acc output and probably add an exit handler to rm -rf logs/ [10:54] sitter: The exit is done by adt, afaik [10:54] even better then [10:56] 9350e598e780a2d7c46481f7c56e0b2ad7b0d563 for the directory name. [10:58] cheers [11:14] hummmm apparently make a zip doesnt work in my dolphin either! [11:16] ovidiu-florin: Just in case: http://oserv.org/files/kde/wallpaper-vibrant/desktopWallpaper-vibrant-1.3-kvermette.splitnoise.svg.out.x4.optipng.advdef/images/3200x2000.png [11:26] ahhhhh [11:26] dolphin-plugins was not installed [11:26] I guess I need that for thumbnails and zipping up files [11:27] the zip files aren't managed by ark? (good) [11:28] maxyz: im not sure [11:28] I used to have a Compress item in my menus [11:28] but its gone [11:31] dolphin-plugins has nothing to do with that though [11:35] sitter: yeah, but it solved my thumbnails problem [11:36] literally makes no sense :P [11:36] clivejo: do you have the install list? [11:36] sitter: do you know what I need to install to get back the Compress and Extract menus? [11:36] might be that plugins pulle din something else [11:36] kio-extras probably [11:36] either that or ark [11:36] I am guessing former though [11:37] both are installed [11:37] then I dunno [11:38] clivejo: can you send us your qserialext thing packages? [11:38] I sent it on an email [11:38] clivejo: hmm not got it here [11:38] Riddell: its probably a load of rubbish [11:39] Riddell: did you get my last email? [11:39] maxyz: it uses ark after all btw [11:40] clivejo: I think there is a bug in ark [11:40] ark: /usr/share/kservices5/ServiceMenus/ark_servicemenu.desktop [11:40] that file should provide the service menu itseems [11:41] I assume DCC doesnt work here either :/ [11:43] Riddell: Kmail says the email was sent with an attached file, libqextserialport.tar.gz [11:43] clivejo: file a bug on bugs.kde.org against ark [11:43] to me it looks like the servicemenu desktop file is wrong [11:43] it has ServiceTypes=KonqPopupMenu/Plugin [11:44] but shoudl be ServiceTypes=KFileItemAction/Plugin [11:44] my system is being very unstable and not bing nice to me today [11:51] I think Ive broke my system [11:52] plasma-shell is going crazy and not responding [12:01] my X server keep dying every 2 hours :( [12:04] * Riddell packages plasma 5.4.1 [12:05] Error gettin authority: error initializing authority [12:05] I get this when running a fsck test in recovery mode [12:05] as I can no longer boot [12:09] "no longer boot" ? [12:09] Riddell: nmqt artifacts now have acc logs [12:10] /usr/include/KF5/NetworkManagerQt/networkmanagerqt/ipconfig.h:29:24: fatal error: nm-version.h: No such file or directory [12:10] what the [12:10] libnm-dev:amd64: /usr/include/libnm/nm-version.h [12:10] * sitter wonders if libnm shouldn't be in the -I list [12:11] uh, didn't the rebuild against the new NM fix that o.O? [12:12] well [12:12] well [12:12] right ^^ [12:12] Riddell broke it while fixing it [12:12] lol [12:12] I think I even told him to watch out [12:13] [Dienstag, 01. September 2015] [16:28:47 CEST] and don't forget to update the -dev Depends to libnm-dev [12:13] Riddell: "update" is not the same as "remove" :P [12:14] * sitter diffs against master [12:15] ahoneybun: what is going on with your system that you can't boot ? [12:16] soee: idk I updated during the show yesteryday and then took it out later to a non booting system [12:16] I can get to tty sometimes when I boot from the recovery mode [12:16] I think something to do with UUID [12:16] idk tbh [12:16] anyway g2g to work bbl [12:16] Uploading networkmanager-qt_5.13.0-0ubuntu6.dsc: done. [12:17] Riddell: ^ should fix ACC [12:17] ahoneybun: you have nvidia right? [12:17] I had a X segfault with 355.06 yesterday, had to prime-select intel to get anything working [12:17] ahoneybun: maybe something similar i had [12:17] didn't try 355.11 yet [12:17] mmm [12:17] yofel: don't boot to sddm usualy [12:18] soee: I had a X segmentation fault when it tried to start sddm [12:18] ahoneybun: check .Xauthority user and group [12:18] it had dr something permissons [12:18] but I have to go really [12:18] yofel: yea nvidia [12:19] yofel: yup after this latest nvidia update it seems liek it doesn't work anymore on my laptop when using nvidia profile [12:19] on intel profile all works fine [12:20] right [12:27] but .. i think if i switch profile from nviodia-settings and relogin nvidia is used [12:27] reboot makes it fail [12:29] interesting, I'll try that here later [12:32] actually [12:32] mamarley: did you guys hit something like ^ [12:33] yofel: Huh? [12:33] mamarley: X segfault with nvidia 355.06 on optimus [12:33] intel works [12:33] 355.11 i think [12:34] previous worked fine [12:34] I still had 355.06 when it happened [12:34] so maybe it's not the driver... [12:34] :/ [12:34] sddm ? [12:34] there was some update in last days [12:34] It is likely a problem with the driver itself; I don't see how mis-packaging it could cause a segfault like that. [12:35] probably something in the driver or something related [12:35] was just curious if you had heard about it [12:35] Nope, this is the first time. My recommendation would be to make a post at https://devtalk.nvidia.com/default/board/98/linux/, maybe aaronp will help you out. :) [12:36] thanks [12:37] yofel: ahoneybun said that switching to intel helped him also [12:37] :/ [12:37] so we have the problem with nvidia confirmed in 3 user now [13:13] clivejo: still no e-mail, can you send them by some other means? === Riddell changed the topic of #kubuntu-devel to: https://trello.com/kubuntu | http://qa.kubuntu.co.uk/ | apps 15.08 https://goo.gl/KFMF4F | http://qa.kubuntu.co.uk/ppa-status/plasma/build_status_5.4.1_wily.html [13:17] why 5.4.1 so quickly ? [13:19] just the way the weeks landed [13:20] is there some changlog available ? [13:21] https://www.kde.org/announcements/plasma-5.4.0-5.4.1-changelog.php [13:21] Riddell: Im having big problems at the moment [13:21] plasma-shell is refusing to work for me [13:22] Howdy folks [13:23] it seems to throw a whobbley everytime I click the Kickoff button to open the full page menu [13:24] and I cant fix it now cause Im about to go out the door [13:26] cli the full page menu froze my desktop toyally had to use RESUB to get out of it, then I removed plasma-desktop and kubuntu-desktop and re-installed them because the fancy full screen kicker doesn't work [13:27] phooey [13:29] I'm reluctant to try the full screen launcher agin in case it still isn't fixed even after several large upgrades since [14:15] muon (Plasma/5.4) v5.4.0-5-g11883b9 * Aleix Pol: discover/qml/MuonToolbar.qml [14:15] Use the correct icon for the application menu [14:15] http://commits.kde.org/muon/11883b994d90300be535e8c4d69bee11e66f73ab [15:10] Riddell: I am out. won't be around tomorrow. next week randa so limited availability I suppose. keep an eye on KCI plz. kthxbai [15:11] also if sgclark can make enough time I think I'll try to come up with a jenkins driven release workflow next week [15:11] i.e. eliminate the upload automation and handle all that thru jenkins [15:21] muon (master) v5.4.0-27-g09a944e * Aleix Pol: (3 files in 2 dirs) [15:21] Merge branch 'Plasma/5.4' [15:21] http://commits.kde.org/muon/09a944e34e2f1ad0cf6fe2a9a71b3fc513e2a8e3 [15:21] muon (master) v5.4.0-28-g720c49d * Aleix Pol: notifier (2 files) [15:21] Delay updates notification [15:21] No need to automatically show the notification, we delay it 3' so that we [15:21] can avoid peak moments in the system, such as boot or frequent internet [15:21] connection drops. [15:21] http://commits.kde.org/muon/720c49df7640d701840ba55b46613683f6fc1205 === greyback_ is now known as greyback|eod [17:56] Riddell: safe to remove http://paste.ubuntu.com/12265032/ ? [18:02] Plasma 5.4.1 ready for tests http://qa.kubuntu.co.uk/ppa-status/plasma/build_status_5.4.1_wily.html ? [18:06] Having constant crash issues in a fully-updated Beta install to metal. I've installed every Plasma-related dbg package I could find, to no avail. Anything I can do to help get this properly reported? or should I test 5.4.1 before even trying? [18:07] what crash ? [18:08] Just generic Plasma crashes saying Plasma closed unexpectidly. Can't get a backtrace though all dbg symbols are installed. [18:08] it self-restarts nearly every time, it's jsut annoying, obviously. Happens about every 5-10 mins. [18:10] never seen such problem :/ [18:10] ronnoc: it works fine for me too [18:11] and i have proposed and all staging ppas enables (they should brake something ;) ) [18:12] I just want to help get it reported properly. It's a purely stock, fresh install. And yes, you're living on the edge snele :) [18:14] ronnoc: for me dolphin crashes from time to time [18:15] ronnoc: but never had plasma crash [18:15] Riddell: plasma 5.4.1 tested, smooth upgrade. [18:16] Mine says Plasmashell segfault :/ [18:16] ronnoc: maybe its time for clean (re)install? at one moment my wily installation was so broken that i had to reinstall. now it works great [18:18] snele: maybe, but this install was a few hours ago. Though as you likely know, there were a LOT of updates since the beta was finalized. [18:18] * ronnoc wonders if it's related to the new Intel kernel drivers... [18:18] I have had kdeinit crash a number of times, which dumps me back out to SDDM. It always happens after I unlock the system. [18:21] soee: have you a link to the Plasma 5.4.1 changelog? [18:22] clivejo: chekc history, Riddell posten it ealier today :) [18:22] soee: I cant, I wasnt logged in earlier when this was posted [18:22] and i'm on different machine :D [18:22] Just happened again "Executable: plasmashell PID: 2498 Signal: Segmentation fault (11) Time: 9/3/15 14:22:02" :/ [18:23] and i don't remember the link :( [18:23] had problems with plasma and had to sort out a car [18:23] did Riddell get my email with tar attached [18:25] I'm pretty sure he said something like email was not working [18:25] ronnoc: if that is your test partition/system, enable proposed and maybe stagging ppas to see if that helps [18:26] i don't know if 5.4.1 realise is in proposed or in staging [18:26] but i got it and it works good [18:26] :) [18:26] It's aproduction machine, but tonight I can re-install on a spare drive and enable those for testing. [18:27] snele: That's good to hear :) [18:28] ronnoc: i have boring and rock stable 14.04 as main system and one partition for testing/playing :))) [18:28] but 15.10 work so well for me I'll probably switch to plasma 5 in october [18:29] no crashes at all (exept kwin crash but i fixed it, it was nvidia related) [19:00] clivejo: https://www.kde.org/announcements/plasma-5.4.0-5.4.1-changelog.php [19:02] mmm we need someone handling the Kubuntu user group on Linkenin [19:02] they need some answers [19:02] on our future [19:03] oh interesting, now after updates i have the same situation as ronnoc mentioned [19:03] every ~10 min plasmashell crashes and restarts [19:03] soee: You'll likely find that the longer you're loggin in, the rate will accellerate [19:04] until at some point it's incapable of restarting [19:05] yeah just second tome crash [19:15] soee: on plasma 5.4.1? [19:16] i doubt it's related to plasma 5.4.1 [19:16] more likely to pim [19:26] ronnoc: info form Plasma devels by looking at my stack trace: "that's a crash in the intel i65 mesa driver" [19:29] back, plasma just died :) [19:43] again? [19:46] yes, i tried to disable compositor for sullscreen windows ;) [19:46] but now since the crash all is fine [19:52] yofel: now it is impossible to switch to nvidia provile through nvidia-settings :/ [19:54] meh, command line switch also doesn't work :< [19:54] oh crap, where did all akonadi resources go? [19:55] are you testing anything before upgrade? [19:55] worst distro ever [19:56] what a bug report... [19:57] :D [19:57] worst distro but this one was the best user ever :D [19:59] lol [19:59] I guess I should upgrade the wily box [19:59] on the Worst Distro Ever [19:59] XD === valorie changed the topic of #kubuntu-devel to: Kubuntu: Friendly Computing | https://trello.com/kubuntu | http://qa.kubuntu.co.uk/ | apps 15.08 https://goo.gl/KFMF4F | http://qa.kubuntu.co.uk/ppa-status/plasma/build_status_5.4.1_wily.html [20:01] valorie: some strange crashes today [20:01] well, I don't have proposed and such enabled [20:01] nor do i [20:01] I'm still getting them. Are you soee? [20:02] ronnoc: not since ~40 min but i did relogin 2 or 3 times ahen trying to activate nvidia :) [20:02] hmm [20:03] ronnoc: maybe it is related to some part of plasma we are using and doing something with it [20:06] so how did you induce the crashes? [20:06] all good here so far [20:06] valorie: no idea plasmashell just crashed and restarted itself right away twice for me before [20:06] wow [20:07] 3 time it died when i was playgin with compositor settings [20:07] ok, watching the podcast interviews on it [20:07] podcast interviews ? [20:07] so setting the intel card seems to fix the issue soee [20:08] ahoneybun: can you elaborate? [20:08] ahoneybun: yes, but i can't switch now to nvidia :D [20:08] soee: see the podcast channel [20:09] that little laptop does have intel, but I did nothing special [20:09] ronnoc: something that soee, yofel and I have in common, NVIDIA+Intel cards [20:09] soee: mmm odd [20:09] simplicy rulez [20:09] weee plasma crashed :) [20:09] "We are sorry, plasma closed unexpectedly" [20:09] ok was hoping for something that could lead me to the cause of my chronic crashes :/ [20:10] and I didn't even update yet [20:10] huh [20:10] * ahoneybun needs to reboot in a few [20:10] ;D [20:10] WTF [20:10] #6 0x00007f002696fc3c in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so [20:11] looks liek Plasma 5 has fancy AI and it communicate with all devices and crahes it randomly :) [20:12] * ronnoc is uninstalling Intel firmware to see if that helps [20:12] brb [20:18] hmmm seems that plasma is rock stable for me. but i have proposed and staging enabled, and I am on nvidia [20:20] i need someone on Plasma 5.4.0 to test one thing [20:23] soee: I can try if my machine stays up long enough [20:23] ronnoc: just check in dolphin if it shows icon for .sql files [20:27] excellent here.... [20:29] * ahoneybun reboots and grabs food ;) [20:33] mm rebooted just fine [20:35] wee crash :) [20:36] * ahoneybun wonders when we will not have 2 volume things lol [20:36] remove kmix :) [20:44] ok, so that update is... "fun" [20:44] nvidia is still broken, that's for sure [20:45] also my kwallet is broken, meaning I couldn't connect to the WiFi as plasma-nm couldn't provide a password [20:45] well, I think now that it is raining, I'll go buy a new backup instead of working in the yard [20:45] so I can update this box [20:46] oh, and plasma didn't save my session this time [20:46] so much for that [20:48] hmm, Kontact has this welcom popup "Did you know .. ?" but it is just empty and clicking previous / next changes nothing :) [20:49] wee plasmashell crash .. :) [20:50] do you also have intel in the trace? [20:51] funny enough kmail still works for me [20:52] yofel: i closed this crash window .. my first crash today was http://paste.ubuntu.com/12265705/ [20:52] and info on plasma channel: <_kdepepo> soee, that's a crash in the intel i65 mesa driver [20:52] soee: install xserver-xorg-video-intel-dbg [20:52] that's the same trace I had earlier [20:52] sadly retracing after installing that didn't work [20:53] ok i have it installed [20:53] now this feels like an old-school ubuntu dev release again [20:53] until beta1 everything works fine, then hell breaks loose XD [20:54] :D [20:55] this is what I get with nvidia http://paste.ubuntu.com/12266942/ [20:55] dang, I forgot to run nvidia-bug-report.sh [20:57] :/ [20:59] well, on the positive side, this is perfectly reproducable -.- [20:59] bu this is 100% nvidia driver issue ? [21:00] probably... the only other parts in that trace are libc6 (probably not...), and X (well, this is X, but it works with intel) [21:01] soee: yofel: I have nvidia in desktop pc and it is rock stable. I believe it is optimus issue(you guys have laptops right?) [21:01] yup [21:01] yep [21:02] it's still nvidia_drv.so that crashes though.. [21:03] I guess I could try 352 again.. [21:06] yofel: are problems with optimus+ssdm fixed yet? I am going to buy new laptop soon and I am scared to buy optimus laptop :) [21:06] but like them the best :) [21:08] until yesterday, I didn't really have issues with optimus.. [21:08] soee: also install libgl1-mesa-dri-dbg [21:09] here's my full plasma trace http://paste.ubuntu.com/12267093/ [21:11] yofel: installed [21:11] hihi NVIDIA 355.11 Driver Stabilizes The Series With Full OpenGL For EGL :) [21:11] ... Stabilizes [21:12] riiiiiight [21:16] * yofel filed lp 1492037 [21:16] Launchpad bug 1492037 in mesa (Ubuntu) "Segmentation fault in brw_meta_fast_clear" [Undecided,New] https://launchpad.net/bugs/1492037 [21:18] i confirmed it though have to wait for crash to have some trace [21:19] Riddell et al. : I made a package for the AppStream metadata generated at appstream.kubuntu.co.uk, which installs the data for the "main" and "universe" archive components [21:19] you can get the thing from https://launchpad.net/~ximion/+archive/ubuntu/packagekit/+sourcepub/5368271/+listing-archive-extra and test it [21:20] to reach the archive, it will need a sponsor though ;-) [21:20] oh, and it required the appstream package to be available in at least version 0.8.3, so the data can be read correctly [21:21] we'll need a FFE for that then, we only have 0.5 [21:22] Will you? [21:23] Considering the current version is broken with the upstream data, isn't it just a bug fix? [21:23] hm, good point [21:23] can we still do a sync from unstable? that has 0.8.3-2 [21:25] yofel: appstream-glib is at 0.5 [21:25] will still need a sponsor, I have no upload rights for that [21:26] that version can't read the data as well, but upstream also doesn't have a fix for that yet - and it's not very relevant for KDE :D [21:26] oh, I checked -util [21:26] -index is 0.8.2 [21:26] so the Debian developer dashboard is correct ^^ [21:27] ScottK: the current version is broken with the *downstream* / distro data ;-) - upstream works well [21:27] although I would also consider this to be a bugfix [21:28] especially since the new release doesn't bring many invasive new features [21:28] (not a single change which could break ABI, only the name of a cli tool has changed) [21:29] yofel: I'm getting (what I beleive to be) the same constant Plasmashell segfauts but I do not have anything nvidia on this desktop. [21:30] ronnoc: please pastebin the trace when you get it [21:31] ronnoc: the plasma crash is from the intel mesa dri lib from what I see [21:36] yofel: that would appear to be the case - my graphics is an onboard 82G965 Integrated Graphics Controller [21:36] I should be getting one momentarilly [21:36] ronnoc: make sure you have libgl1-mesa-dri-dbg installed [21:37] ok [23:04] what's the command again to upgrade this box to vivid? [23:04] sudo do-release-devel-upgrade ? [23:05] or is there a kubuntu special version [23:06] got it [23:08] do-release-upgrade -d [23:11] yep, that's what I used [23:11] it's now in the midst of it [23:12] and I'm out ripping out the hated groundcover