=== Punna is now known as Pwnna === doko_ is now known as doko [09:11] morning all [09:25] brainwash: it was confirmed that the xfwm4 settings bug is a packaging thing, so no need to worry about that one [09:38] hey folks, on my xubuntu saucy install, I still have a broken volume indicator, I assume that's a known issue? [09:38] pmjdebruijn: yep it is known :) [09:39] k fair enough [09:39] elfy: s/:)/:'(/ [09:39] ochosi: indeed - but what can I do ;) [09:39] elfy: cry baby cry, make your mother sigh! [09:40] pmjdebruijn: there is a 'fix' but if it upgrades it needs redoing atm [09:40] but I don't think anything will get done with it this side of release [09:40] ochosi: my mother would just slap me ;) [09:41] "this side of release"? [09:41] elfy: i assume it would be well-deserved (your mother will know why she slaps you i assume) [09:41] before Thursday pmjdebruijn - not sure what we'll be able to do post release either - but I think we're looking at doing something [09:42] ochosi: couldn't possibly say :) [09:43] is there a launchpad bug related to this? possibly with a track record of what's known about this issue? [09:43] https://bugs.launchpad.net/bugs/1208204 [09:44] Ubuntu bug 1208204 in indicator-sound (Ubuntu) "indicator-sound no longer functions with xfce4-indicator-plugin" [High,Triaged] [09:46] thanks [09:47] I'll have a read tonight :) [09:47] :) [09:49] oh btw, I assume revert to the Raring version isn't on option, since the changes which broke it, were purposefully for mainline ubuntu? [09:50] wouldn't it in that case make sense to fork it? [09:50] xfce-indicator-sound ? [09:50] or xubuntu-indicator-sound [09:51] no, that wouldn't help [09:51] I can't answer that I'm afraid [09:51] ochosi can though :) [09:52] you'd still have to backport the whole beast to gtk2 [09:52] and it makes much more sense to use the xfce4-indicator-plugin that support gtk3 [09:52] (especially since it already exists and works) [09:55] I mean fork the raring version [09:55] not the saucy one [09:56] that won't work either [09:56] because there were protocol changes [09:58] oh I though someone reported downgrading the package to the raring version worked [09:59] anyhow, I'll read the full thread tonight then [10:00] sure [10:01] (fwiw, i've never tried downgrading) [12:57] pmjdebruijn: yeah what you said pretty much sums it up [12:58] pmjdebruijn: the indicators has two parts: the part which the users sees and the dbus backend [12:59] so the gtk2 and gtk3 versions both have a backend in the package, but when you install the gtk2 indicator it uses the gtk3 backend anyway. this is pretty much required due to how dbus services are initialized [12:59] in raring it didn't matter because the two backends were compatible but in saucy they are not [13:00] so forking isn't required - what you need to do is make the gtk2 indicator compatible with the gtk3 backend again [13:01] that would be a lot of work, and we have gtk3 indicators working now [13:01] btw the workaround is to edit the dbus service so it runs the gtk2 backend - this patch can never go in ubuntu as it will break the gtk3 indicator [13:09] right. but in that case just forking the package would at least allow for a temporary fix [13:10] I'll give that a go on my ppa tonight then [13:38] ali1234: do you intend to comment on the users-admin lp report? [14:07] the test cases are (disabled) [14:08] will try with "daily" [14:12] the daily zsync has absolute no difference from the final ISO [14:14] Respin happening..... [14:14] ok [14:14] so it useless for me to test now [14:14] GridCube, technically, you report results to the "final" milestone, but the ISO is called "daily" until the release actually happens... [14:15] yes, but the final report site says "disabled" so i assume that if i do the test it wont be useful [14:15] Nah, wait for the respin [17:19] * ochosi senses general pre-release fatigue [17:20] (usually followed by post-release depressions) [17:24] ochosi: xfwm4 is able to copy the root background, but not the "background" set by lightdm [17:24] in lightdm that's done via accountsservice [17:24] but that's an ubuntu-only accountsservice patch [17:25] right, but it's not able to copy the pixels [17:25] :D [17:25] maybe it would pre-load xfdesktop's wallpaper? [17:25] well we can modify the greeter if that helps [17:26] xfdesktop does not set the root background, just drawing a window right? [17:26] (but iirc we set the root background to the wallpaper in the greeter already, not sure what else we could do there) [17:26] possible, i don't know [17:29] mmh, maybe it will work to start xfdesktop first and delay xfwm4 (and therefore the panel) [17:31] gotta go [17:31] bye [17:48] hi huys [17:48] guys* [17:49] tomorrow stable release :) [17:49] :/ i still could not test the image [17:51] hehe :D [17:52] I'm testing this on Sapphire Edge-HD4 and it works now :) [17:55] now we need to focus on fixing the remaining known bugs [18:01] And from what I've seen today #ubuntu-release looks like a bit of a horror show when it comes to ubiquity [18:10] so 13.10 feels more like a snapshot on the way to 14.04 [18:22] anyone got any idea why our Final tests are disabled? [18:46] beats me [18:46] :/ i wanted to test today but i dont know if its worth [18:46] brainwash: Sticking my .02 € in...I seem to remember this very thing was discussed several Team Meetings ago (right after Canonical announced that the non-LTS releases were going to be supported for only 9 months). To be honest, I don't remember exactly what was decided: a) all releases were equal (but LTS release were more equal than others), or b) non-LTS releases were to be considered as snapshots. Maybe some of the less-memory-challenged here ca [18:46] n pipe in on that. [19:12] ochosi: I tried to start xfdesktop first and delay xfwm4 just a bit, but it does not work that well and even might cause some glitches.. so I simply used feh to set the root background according to the user's stored details (accountsservice) and xfwm4 picks up the background without any visible drawbacks [19:13] ochosi: I'm using the gtk2 indicators from precise and raring, so yes that works. :P [19:14] Unit193: even the messages and sync one? [19:15] drc: Heh, well put. Sounds like the old Russian way, "Yes, comrade captain!" [19:15] thad_: I don't use sync, but messages yes. [19:16] well, nice to know :) [19:26] (Mixed raring and precise when I used raring too.) [19:33] a solution for everyone would be great :P [19:33] "soon" I guess [19:36] Hah, yeah. That's just for crazies like me. The GTK3 stack will hopefully make it into -backports. :) [19:39] What part of october 17th are we releasing on? I want to be the very first person running t-series [19:40] 25 minutes after you've gone to bed [19:40] sounds about right [19:41] Since it is the 17th already [19:42] there you go - we'll be releasing on the 18th as far as you're concerned :p [19:44] Do they still have a #release-party (or what ever it was called) ? [19:44] apparently [19:45] bit like driving for a while with kids in the back I'd imagine ;) [19:46] ah...#ubuntu-release-party Already 22 in the channel :) [19:46] are we there yet ... [19:47] * drc waits to the time-adding bot to kick in.... [20:49] oh great, just before final release I broke the brtfs filesystem of my test installation :/ [20:49] anyone familiar with brtfs? balancing the filesystem caused a kernel panic :( [20:54] (btrfs) [20:55] bug 1235798 [20:55] bug 1235798 in linux (Ubuntu) "Kernel stops during btrfs-balance" [Medium,Confirmed] https://launchpad.net/bugs/1235798 [21:05] good night all [21:06] Howdy. [21:06] Unit193, hi