[01:00] be back tomorrow; have fun [01:35] well, that's not pretty [01:35] http://imagebin.org/305129 [01:35] indicator-datetime, indicator-keyboard without an icon, ibus [01:36] maybe tomorrow's iso will look a bit better [01:40] bluesabre: /var/crash/ [03:11] Unit193: remove the files inside or the whole directory? [04:43] Hello, has anyone considered changing the default colors of the xcfe4-terminal? Some colors are too dark to be readable... :/ [04:47] OvenWerk1: That was to remove bothering of crashes, the files there. [05:11] Unit193: Thankyou. Yes that helps. [05:11] Heh, sure. [05:12] (switching the nvidia driver to the open one seems to help more) [05:13] apport-cli can show you them. [05:38] good morning [05:54] morning elfy [05:55] hi jhenke [06:02] i guess most of the people here are still away/sleeping? [06:03] that and saturday :) [06:03] well I had a nice little nephew waking me at 6:30 am ^^ [06:04] just being courious whether todays image will be clean of those extra indicators [06:05] I'd not count on it [06:06] I have a netbook here, where I would want to install xubuntu (was my sisters running WinXP), but as it does not accept booting from USB sticks, I want a "clean" image to install it [06:07] I understand - all you can do is zsync ~11:00UTC and see [06:08] the image is 'usually' new at ~10ish [06:08] yep, just still hoping it would work today ;) [06:08] :) [06:12] elfy: Could check manifests. [06:13] oh yea - those things [06:13] not sure when that would be changed though [06:14] current doesn't have blueman [09:11] aiui, there is NO NEW IMAGES unless we request a respin [09:48] slickymaster, have you had bug 1196625 in a long time? [09:48] bug 1196625 in software-center (Ubuntu) "software-center crashed with signal 5 in _XReadEvents()" [Medium,Confirmed] https://launchpad.net/bugs/1196625 [09:51] I have still this bug from time to time :] [09:53] wondering if the assignee is really working on it, has 2 karma on launchpad and no memberships [09:53] sorry, 5 lp karma... [09:59] why installer is still in english and my own lang when I choose my lang? there should be only my own lang cause translation was done on launchpad before the beta 2 :/ [10:05] how much before? [10:06] a month? [10:07] i'm trying to localize Xubuntu as much as possible but it is sometime very hard to do this :/ [10:08] polish is your language? i see 28 untranslated strings [10:11] wtf? there were translations and it's gone :/ [10:12] what is going on with this launchpad :/ [10:13] did you do the translations before we did the call for translations? it's likely that you have translated old strings. [10:13] knome I thought there are new images generated once a day? hence daily image? [10:13] jhenke, not during RC [10:13] :( [10:13] https://wiki.ubuntu.com/ReleaseCandidate [10:14] "During the week leading up to the final release, the images produced are all considered release candidates" ? [10:14] sounds like daily images to me, or is something tricking my mind right now? [10:14] is [10:14] " In an ideal world, the first one would end up being the final release..." [10:15] the idea of a release candidate is "do not change it if it works" [10:15] well I do not want to argue about it [10:15] well ours did not work as expected yesterday... [10:15] no problem really [10:15] yes, and still wouldn't, so we haven't yet rebuild [10:15] we can do that when we need to, though [10:16] okay then I guess it makes no sense to test the new one (which according to the website was build just some minutes ago) [10:16] 12-Apr-2014 10:05 [10:17] well it "always" makes sense... [10:17] there might be other things landed that might have regressions [10:17] just not realistic to expect unfixed things to be fixed in that ISO :) [10:18] my hope was that the dependecy chane would be solved by the time the ISO was generated [10:18] you know, optimism ;) [10:18] i doubt so... [10:20] well I'll test it any way then, the most useful thing I can do right now :( [10:20] so, do you we already need to write a SRU report for merge requests? non-critical issues ofc [10:21] anything that will be a SRU will need a SRU report at some point [10:21] mmh, some point [10:21] so we've already passed that point, right? [10:21] well, before it's landing as a SRU :P [10:21] that question both makes and doesn't make sense [10:22] I think so, the release candidate mail sounded like everything is a SRU now, except release blocking bugs [10:22] yep. [10:22] we don't have any blockers :) [10:22] so things that won't go into the release, are SRU material [10:23] for those, you will need SRU reports [10:23] ok [10:30] upgrading to trusty [10:30] mrh [10:38] good morning everyone [10:51] bug 1306917 [10:51] bug 1306917 in light-locker-settings (Ubuntu) "light-locker: screen always locked" [Undecided,New] https://launchpad.net/bugs/1306917 [10:51] can anyone confirm this? [10:54] knome: can we move bug 1270894 to 14.04.1? [10:54] bug 1270894 in ristretto (Ubuntu) "Sorting by date or name not working properly in thumbnail bar" [Medium,Confirmed] https://launchpad.net/bugs/1270894 [10:59] patched abiword available from https://launchpad.net/~thad-fisch/+archive/abiword [11:00] brainwash, can and should. [11:00] do I need to create an extra bug report to request an update of abiword via debdiff? [11:01] or can I simply attach it to one of the existing reports (3)? [11:01] i... don't know the answer to that question :P [11:01] i guess you'd need a sponsorshhip bug [11:01] I think so too [11:01] which could be one of the existing bugs, but would be cleaner if it wasn't, since it fixes multiple issues [11:01] well, first it needs to be tested [11:02] I don't want to attach a bad debdiff :) [11:02] elfy: please test https://launchpad.net/~thad-fisch/+archive/abiword [11:03] you can find the bug numbers in the PPA description [11:03] i'm not sure if those bugs would be critical enough to warrant a final freeze exception... [11:04] the crash on exporting PDF is semi-nasty [11:04] sru then [11:04] quick sru [11:04] there is no quick SRU... it's .1 in 6 months [11:04] we can push them to updates though [11:04] yes, update [11:05] yes, sure [11:05] but it's that a sru? [11:05] not necessarily [11:05] a SRU means the change will be on the next ISO [11:06] withtout a need to upgrade your system [11:06] ah, that's fine [11:06] and it will also be landing for *everybody* [11:06] so it will stay broken on the live cd [11:06] not just those who opted in for extra updates [11:06] for 14.04, yes... [11:06] (unless we want to argue it getting a final freeze exception) [11:07] which triggers a respin, correct? [11:08] it doesn't trigger one, but obviously we'd like one [11:08] but we will need one for the bluetooth stuff. [11:08] a respin for abiword alone is overkill [11:08] sure. [11:08] but that might be an indicator it's overkill to break the final freeze with it [11:10] brainwash, for future convenience, can you drop in the bug titles to the PPA description along with their numbers [11:11] brainwash, i'm thinking the PDF export bug might warrant the exception. [11:11] and while we do that, we could land the other two [11:12] but i'd poke around in -release and ask what people think [11:13] also, i should be able to test the PPA soonish [11:19] 14:15 knome: what's the general thought about fixing a low, but annoying bug along with a high/critical bug during the final freeze? [11:20] 14:15 knome: (in the same package) [11:20] 14:19 cjwatson: I'd probably be OK with it as long as the diff was clear and we could make a good estimate from it that the risk is low [11:23] brainwash, bug 1292290 ? [11:23] bug 1292290 in xfce4-settings (Ubuntu) "Window manager keybindings don't work after reboot" [Undecided,Confirmed] https://launchpad.net/bugs/1292290 [11:51] knome: well, it's a bug I can confirm [11:51] but not triage? :| [11:52] no, but maybe fix if I take a look at the source :D [11:52] i could approve that as late fix... [11:53] if it really is as the bug says, and is impacting many users (which i'm not sure of) [11:56] there is also bug 1303404 [11:56] bug 1303404 in libxfce4ui "Hotkeys overriding each other" [Medium,Confirmed] https://launchpad.net/bugs/1303404 [11:56] and maybe https://code.launchpad.net/~thad-fisch/xubuntu-default-settings/migrate-kb-shortcuts [11:57] mhm.. [11:57] they have changed to in 4.11 [11:58] the merge would make sense, but again, final freeze... [11:58] should work fine, but once you hit the "reset keybinds" button, it will also add the version of the keybind [11:59] hmh [11:59] that's a low-priority issue then [11:59] this needs some time to fix [11:59] it's... a bit annoying, but not a huge issue imo [11:59] all 3 issues I mean [11:59] talking about the last one [11:59] yes [11:59] sicne it only happens when you are at that dialog, it's barely a problem :) [12:00] and in a way, it doesn't make as much sense to land the fix for .1... :| [12:03] ahh, yes now that you mention that explains some behaviour when changing keybindings [12:03] we need to forward it upstream at least [12:04] sure [12:08] so there won't be any fix before release [12:08] if there is a fix for the two bugs, i'm ok to approve those, but the migration stuff, nah [12:09] brb, booting to trusty side of things! [12:10] hey guys [12:11] has anybody looked at why indicator-keyboard and indicator-datetime seem to be in the latest nightlies? [12:12] or do I have a project now? [12:13] it was assumed they came via the dependecy chain, as gnome-bluetooth was pulled in and with it gnome-control-center and unity-control-center [12:19] hmm... not able to login graphically [12:20] ah [12:23] fun [12:23] remove indicator-datetime indicator-keyboard [12:23] installs gnome-control-center [12:23] :\ [12:24] so the dependencies need to be tweaked [12:24] anybody looking into this currently? [12:24] is this something cyphermox was looking at? [12:24] bluesabre I think we need to look into that once gnome-bluetooth is gone [12:24] I think so [12:25] ok, so we are removing gnome-bluetooth then? [12:26] afaik the agreed solution is to demote it from recommend to suggest on network-manager-gnome [12:27] that should stop pulling it into the default install [12:47] brainwash: confirm that fixes those 3 abiword bugs [12:50] apparently does so for bug 1054315 [12:50] bug 1054315 in AbiWord "abiword crashed with SIGABRT" [Critical,Invalid] https://launchpad.net/bugs/1054315 [12:58] elfy: thanks [12:58] the linked report is marked as invalid [13:01] no idea why - but that doesn't mean it doesn't happen - just that it got marked invalid ;) [13:01] it might have been that guy wandering around making vague pronouncements on our bugs :p [13:06] hmm, i'm having problems getting lightdm to run on upgrade from 13.10 [13:06] that's unusual [13:06] o'rly? :P [13:06] anything in the logs? [13:07] it's probably related to xrandr not being able to open any display.. [13:07] O.o [13:07] can see plymouth when i don't use the nvidia driver [13:07] seems like you should have answered elfy's calls for testing ;) [13:07] but it just loads infinitely [13:07] hey, production machines! [13:08] :D [13:09] maybe install the nvidia proprietary drivers, and run nvidia-xconfig? [13:09] i *just* did that [13:09] but i'm pretty sure that won't fix it [13:09] i've tried with a veeeery similar xorg file and the proprietary drivers installed [13:09] jockey-text is a joke [13:10] it never does anything [13:10] i'm just it is just sleep(random) [13:10] pebkac [13:11] elfy: bug 1306905 [13:11] bug 1306905 in xfce4-panel (Ubuntu) "action buttons always ask for confirmation" [Undecided,New] https://launchpad.net/bugs/1306905 [13:11] "Since today's daily update,..." [13:11] elfy, feel free to prove me wrong and point where the problem is... [13:12] between the keyboard and the chair - that's the bkac bit :p [13:13] yes, and what is that problem? [13:13] :p [13:14] try esc and see if it's hanging at nvidia-prime [13:15] that says ok.. persistenced daemon says fail [13:15] not seen that in my travels [13:15] "starting ligthdm display manager" -> fail [13:16] "starting send an event to indicate plymouth is up" -> fail [13:24] brainwash: I have no idea what that bug report even means [13:25] the confirmation dialog (ok or cancel + 30sec timeout) [13:25] and that means just as much [13:26] what confirmation button in panel configuration says that? [13:26] action button [13:27] ? [13:27] top right corner (old panel layout) [13:27] the thingy with your name [13:27] oh [13:28] action plugin [13:28] O.O [13:28] :D [13:28] well, this particular user has reported some "bugs" which I cannot confirm at all [13:28] right [13:29] I might understand why - hang on I'll comment [13:30] I thought your volman thing was up the kibosh this morning - following updates - EVERYTHING including reboot wanted a password - once I rebooted all was ok again [13:31] suspend from there works [13:32] fine - and now that I've gotten used to it in whiskermenuI see that I could have had buttons on the panel [13:32] knome: I can't find anything re that lightdm issue of yours [13:34] knome: what happens if you delete your existing Xorg.conf? [13:36] * bluesabre works on getting rid of gnome-bluetooth [13:39] bluesabre, nothing. [13:40] :\ [13:40] bluesabre, well, when i deleted that and the nvidia driver, i got to plymoith [13:40] *plymouth [13:40] which kept on loading infinitely [13:40] whats the graphics card? [13:41] nvidia geforce gtx 560 ti [13:43] yup, no idea [13:43] yup [13:43] since you did an upgrade, do you still have the old kernels installed? [13:43] not, removed them [13:43] but i could reinstall them [13:44] * knome facepalm [13:44] I'd try that, otherwise... [13:44] #xubuntu is the support channel [13:44] ;) [13:44] /etc/lightdm/lightdm.conf didn't specify user session or greeter [13:44] ah [13:44] that's lame [13:44] i read that elfy had that problem before [13:44] that's gone [13:45] elfy, really? how did it occur to me today then... :) [13:45] that fixes it... [13:46] look in /usr/share/lightdm/lightdm.conf.d/ [13:46] 60-light ... blah I think is where greeter is specified now [13:47] yeah.. but to be exact [13:47] lightdm.conf had them set to null [13:47] eg user_session= [13:47] would the .d files still overwrite? [13:48] knome: here I have no /etc/lightdm/lightdm.conf at all - try # them or renaming them [13:48] well i just specified them [13:48] and that fixes the issue as i said [13:48] i'll go and enable nvidia now [13:48] i can look at the lightdm conf after that [13:48] didn't see you say it was fixed [13:48] 16:45 knome: that fixes it... [13:49] i wouldn't have any clue to look there unless i found your forum thread [13:49] oh - I thought that was a sarky comment to my 'that's gone' lol [13:49] so indirect thanks ;) [13:49] forum's are rubbish apparently :D [13:49] no, i'm hardly snarky/joking when i'm debugging [13:49] :) [13:50] forum usability is still rubbish ;) [13:50] not for me :) [13:51] yeah, i can understand and respect different people liking different methods [13:51] I can too - and do use different methods [13:51] yep [13:51] i just can't deal with the slow pace of forums [13:51] well, it's probably not slow paced all the time [13:51] but it's somehow.. so scattered :| [13:52] I really need to try and get my head around what's gone on with lightdm [13:52] maybe you should ask bluesabre [13:52] I try hard to catch xubuntu stuff on my forum and make sure it is prefixed with xubuntu [13:52] yeah, but even that isn't the problem :) [13:52] nope - it can be slow [13:53] by scattered i mean that even if the forum was perfectly organized (which it never is), and all posts were tagged, you would still have to dig for stuff consistently [13:54] ok, confess, WHO SWITCHED MY MONITOR ORDER [13:54] left is virtually right and right is virtually left [13:55] one more reboot... [13:56] bert was in charge of switching monitors [13:57] i've been speedy [13:57] it never occurred to me that nvidia-settings would be in the... settings manager [13:57] knome: yep - I use a search engine for buntu generally - usually works [13:57] * knome facepalms with a splat [13:57] knome: all sorts of things get left in there ... [13:58] i even made the right hand side monitor the primary one [13:58] which has been bugging me since we moved here in mid-december [13:58] I don't know what happens with lightdm [13:58] we bug robert if there's an issue [13:58] s/we/ochosi [13:58] my favorite CLI command [13:59] sudo apt-get purge apport [13:59] :) [14:00] back later [14:01] bluesabre: it's not so much issue - just wth has been moved about :) [14:01] also, I don't get that either ;) [14:01] knome: is cyphermox leading the charge on bluetooth? [14:05] bluesabre: I'm glad it's not just me then :p [14:08] bluesabre, yes, but please make sure removing it helps with removing stuff you want out [14:09] elfy, what was the bug for the lightdm issue? [14:12] knome: my one? [14:12] i found it, bug 1267442 [14:12] bug 1267442 in nvidia-prime (Ubuntu) "Install nvidia-331 on X/K/Lubuntu results in unbootable machine" [High,Fix released] https://launchpad.net/bugs/1267442 [14:12] yea that's it - back later [14:13] I love the fact that nvidia-prime actually works in trusty [14:14] bluesabre, i like the prime messages: [14:14] ** Message: PRIME: No offloading required. Abort [14:14] ** Message: PRIME: is it supported? no [14:14] ah [14:15] well, it works for my new laptop with the haswell/nvidia combo [14:15] :) [14:15] mh [14:18] ok, tested a package with gnome-bluetooth moved to suggests, it seems to work [14:19] reinstalling the existing package adds these things: [14:19] http://imagebin.org/305191 [14:20] installing the new package: [14:21] too lazy to copypaste? [14:21] vm doesnt have extensions installed [14:21] http://imagebin.org/305192 [14:22] copypaste to a file in vm, cat file | pastebinit [14:22] mmh, I guess that we know that already [14:23] anyway, if cyphermox is handling it, cool, otherwise, let me know if I need to bug the sponsors [14:23] he said so [14:23] but it takes soooo long :) [14:24] where can we even track the status? [14:24] bluesabre, he is, but stay on your toes just in case [14:24] brainwash, please stop whining [14:24] lol [14:24] I'll push a merge request tomorrow morning if I don't hear anything [14:25] bluesabre, it involves studio and mythbuntu seed, so careful! :) [14:25] ah [14:28] but ibus is not involved? [14:28] one sec [14:29] or did you forget to remove it manually [14:29] forgot to remove it [14:29] 1. new package does not pull ibus [14:30] 2. old (current) package does [14:30] so yes, fixes ibus as well [14:30] ok [14:36] so, installation diff http://paste.ubuntu.com/7239825/ [14:37] which is silly [14:37] :D [14:46] bluesabre, pretty much... [14:55] besides that issue, and abiword's zaniness, the release looks awesome [14:56] I am so ready to move on to libreoffice [14:56] going to really push for that next release [14:56] hmm... [14:56] since abiword and gnumeric are some of the worst-designed gtk apps there are [14:56] that would make the ISO over a gig though [14:56] what about just dropping them altogether? [14:57] I wouldn't mind that personally [14:57] well the next big target is 16.04 [14:58] right [14:58] do (most) people really do their office stuff locally and not in the cloud in 2016? [14:58] well i don't know, probably nobody knows [14:58] plenty of opinions on that ofc [14:58] but i would say dropping abiword and gnumeric will make *more* sense *after* 14.04 [14:58] right-o [14:58] regardless if it's (still) the optimal choice or not [14:58] but i don't know [14:59] i'm not the one who decides... [14:59] 5 days and i'm free! [14:59] :'( [14:59] we need to keep rolling forward [15:00] let's have some fun and put Unit193 in charge through the next LTS [15:04] bug 1306952 [15:04] bug 1306952 in abiword (Ubuntu) "Abiword bug fix update for trusty" [Undecided,New] https://launchpad.net/bugs/1306952 [15:06] I'll take that for a spin [15:09] bluesabre, please also ask for an ACK from the release team [15:09] of course [15:09] i've asked about that yesterday and cjwatson said he'd probably ACK it if the diff was clean [15:09] brainwash: works well [15:10] knome: abiword or bluetooth? [15:10] abiword [15:10] i've no reason to think the bluetooth issue wouldn't be approved either [15:11] only one of the abiword bugs were *actually* critical enough to be worth acking a final freeze exception [15:11] the thing i asked from -release was if we could slip in a few low-prio bugs as well [15:12] what about https://code.launchpad.net/~thad-fisch/ubuntu/trusty/thunar-volman/fix-automount ? [15:12] or https://code.launchpad.net/~thad-fisch/ubuntu/trusty/xfwm4/fix-untiling [15:12] is it worth to release an update after release? [15:13] if volman actually fixes stuff (as it seems to), we could try to push it in [15:13] and fast... to be done with one respin. [15:13]