[01:14] Are we leaving LP Bug #1208204 as a known issue at release? [01:14] Launchpad bug 1208204 in indicator-sound (Ubuntu) "indicator-sound no longer functions with xfce4-indicator-plugin" [High,Triaged] https://launchpad.net/bugs/1208204 [01:50] skellat: Well, it's way to late to land GTK3, can't port all the new stuff, so it'd either be a hack or fixed after release. [02:06] Unit193: SRU/Backports it is [02:07] Praise the Lord this thing is only supported for 9 months [02:15] It's the stable release for 9 months. [06:59] btw I tried to repackage indicator-sound as xubuntu-indicator-sound for a gtk2 service patch [06:59] but that didn't work, as Provides idnicator-sound doesn't work since indicator-sound-gtk2 defines an explicit version requirement [06:59] which Provides can't.... erhm... provide :) [06:59] so that was a bust [07:00] https://launchpad.net/~pmjdebruijn/+archive/xubuntu-indicator-sound-testing [07:00] I did modify the original package and put it on a ppa [07:00] but of course that's no feasible solution for upstream [07:07] there is no upstream [07:07] that code is not maintained any more [07:07] I meant upstream (ubuntu) packaging [07:07] sorry for the confusing wording [08:19] @channel - if anyone can run any tests today that will be good - http://iso.qa.ubuntu.com/qatracker/milestones/305/builds [08:19] elfy: Error: 'supybot.-' is not a valid configuration variable. [08:19] stupid thing [08:27] xnox: Hello. It seems ubiquity will not start and will "silently" fail if upower is not installed, might want to depend on it? http://paste.ubuntu.com/6249950 [08:27] (And thus ends my test, oom-killer took it out.) [08:28] ...Or I should stop doing weird things/breaking other peoples toys? :P [08:36] where's the fun in that? [08:40] Unit193: all ubiquity images have upower on them..... what image / cd are you using? [08:41] elfy: Less getting hollered at, here watch. [08:41] xnox: It's not anything relly, just debootstrap base and chroot in and install, then make live. [08:41] (ccan't type now.) [08:41] +well [08:42] Unit193: don't do that. [08:42] Unit193: that's not support, use lp:livecd-rootfs / lp:ubuntu-cdimage to build live images using seeds. [08:42] Unit193: no need to re-invent all of that. [08:44] xnox: Where's the fun in that? :P And that kind of assumes that I'm building a normal flavor? Thanks for the links though, taking a look. (Already re-invented thw wheel though.) Figured you'd might want to know though, as it doesn't start without it... [08:46] morning all === cub_ is now known as cub [08:47] morning slickymaster [08:48] Unit193: it's not the only thing that will not work..... [08:48] Unit193: you do need a normalish desktopish install to make ubiquity actually work. [08:48] xnox: Understandable, I was using openbox. :D [08:49] hi, elfy [08:49] xnox: So guessing considered "NotABug"? :/ [08:49] Unit193: i thought we had an openbox flabour, there was one unofficial one bluebuntu or something. [08:50] Not the slightest clue, was testing something else really. [08:57] xnox: And "regressions" in casper could be asked aoub in #ubuntu-installer perhaps? [08:57] Unit193: casper dicussions are on-topic on #ubuntu-installer. [08:58] Cool, sorry for the bother (and lack of typing ability) [11:07] knome: upgrades are tested - both 64bit and 32bit have at least 1 test I've done for each today and a bunch of tests done over the last few days for superseded ones [11:17] biab [11:21] oki [11:22] brainwash: so i guess i have to check whether we can do in the greeter what feh does (set the root background) [11:26] ochosi: and we need to build xfwm4 with the flag which enables the copy mechanism of the root background [11:28] ..and do some testing, there have to be some drawbacks [11:28] yes? [11:28] like what [11:28] it's not enabled by default [11:30] so what are the drawbacks? [11:31] performance loss? the background gets set and then copied [11:31] maybe visual glitches [11:32] if something goes wrong [11:32] so it needs to be tested, but we got plenty of time until 14.04 :) [11:33] oh, i thought _you_ noticed some drawbacks [11:33] well yes, ofc it has to be tested [11:34] btw, didn't you point out that the calendar-icons were inconsistent in some sizes? (32 and 16px) [11:34] anyhoo, i fixed that yesterday [11:34] i think i did [11:34] wasn't me [11:34] ah, hi knome [11:34] and: you're welcome ;) [11:34] hullo. [11:34] cheers [11:35] but it's usually my job to complain about low res icons :D [11:37] how do you mark bug 1232804 for the next release? or add it to the todo list for 14.04? [11:37] bug 1232804 in xfwm4 (Ubuntu) "[compositing] improve login greeter -> desktop transition" [Undecided,Confirmed] https://launchpad.net/bugs/1232804 [11:41] i think knome started a blueprint for 14.04, you can link it there if you want [11:41] unless we're only using the wiki now to track 14.04, then you can add it there [11:42] (wait for knome's answer on that) [11:43] wha? [11:43] add to the wiki [11:43] easier to follow, supports locks and stuff [11:43] let's move stuff to blueprints when we are done and decided on stuff we want to work on [11:45] link? [11:47] most likely I'm not able to add it myself, so anyone with the required privileges has to it =S [11:47] https://wiki.ubuntu.com/Xubuntu/Roadmap [11:47] you are if you have ubuntu SSO (LP account) [11:51] ok, it won't let me log in currently (stuck at the personal data request) [11:52] that sometimes takes a while [11:53] or a few attempts [12:10] ochosi: sometimes ? is that some European thing for 'always' :p [12:10] And also something about copy it into a text editor before hitting save, or else you might lose it? [12:11] ahah :) [12:11] knome: so - when shall we/I mark these as ready? [12:13] elfy, i'm totally out of the loop. if they look/feel ready to you, please mark them as such [12:13] lol - ok - well I've not seen anything new - some of the odd ubiquity issues are gone it seems [12:13] I'll mark them now then [12:17] are there non-ready images? === cub_ is now known as cub [12:18] knome: yea - lubuntu for one [12:18] heh. i meant for xubuntu [12:19] ochosi, is it know that scrolling doesn't work on gedit (gtk3) on saucy? [12:19] nope - I've marked our finals/dailies/upgrades [12:20] knome: bug 1236271 [12:20] bug 1236271 in xfwm4 (Ubuntu) "GTK3 applications do not react to scroll wheel input when overlay scrollbars are activated" [Undecided,Confirmed] https://launchpad.net/bugs/1236271 [12:20] ah, so it's that. [12:20] xfwm4 not compatible with overlay scrollbars [12:20] how do i disable them? [12:21] normal unity/compiz shouldn't be affected [12:21] xubuntu does not ship with them :) [12:21] well apparently, i have them enabled after upgrade... [12:21] or then it's a non-overlay-scrollbar issue [12:21] the small scrollbars with the popup handle? [12:22] hmm, no [12:22] scrolling doesn't work without that either. [12:22] works in other apps [12:22] yes, only some gtk3 apps are affected [12:23] Setting the environment variable "GDK_CORE_DEVICE_EVENTS=1" does resolve this issue. [12:23] but the issue was gone after disabling overlay scrollbars on my system [12:23] that did it for me too [12:23] woot [12:23] strange [12:24] wait [12:24] no [12:24] huh. [12:25] yeah it did. [12:27] no clue what might be wrong here [13:56] congratulations, my friends :) [13:58] Congrats:) [14:06] hi pleia2 [14:07] hi there elfy [14:07] I shouldn't be awake [14:07] neither should I - got exactly no sleep last night [14:54] afternoon all [16:13] Gratz to Xubuntu 13.10, but this sound menu isn't very good for team :/ [16:15] really [16:15] thanks for reminding us about the sound indicator :) [16:15] we deliberately made sure it wasn't fixed so people could complain [16:17] hahaha [16:24] * slickymaster LOL [16:25] I ought to say that I was in fact joking as someone might read the logs and think I was serious [16:25] for Justin's Case [16:36] ochosi: any news on how lubuntu locks the screen? still only vt switching without actually locking the session? [16:41] hehe :D [16:46] * skellat lifts his trucker's cup full of decaf tea to the notion that Stable Release Updates will be very needed for 13.10 [16:46] decaf tea? [16:46] elfy: I'm not allowed caffeine [16:48] who is in charge of setting up the xfce4-panel gtk3 indicator PPA? [18:32] brainwash: micahg was trying to do it [19:00] Has there name of t-series been announced yet? [19:01] not as far as i know [19:26] skellat: Erm, just looked at the T roadmap, that's not really what I was talking to xn ox about... [19:29] skellat: You are free to use that information for later use with Xubuntu core, but that was only slightly in mind at the time... [20:16] Added the meeting to the Xubuntu team calendar, but didn't see a link to it in the wiki or website. [20:17] ali1234: ok, maybe it will be up and running soon [20:18] cya tomorrow [20:18] ali1234: any more news regarding the users-admin segfault? just leave the report open and forget about it? [20:19] nothing from me [20:22] any drawbacks when the clear operation gets removed? [21:04] knome: Most likely won't make it to the meeting, but I had nothing (of interest) to say anywho. [21:06] I can't make the meeting (timezone issues), can we add python3 and what xfce4.11 stuff we want to the agenda? [21:12] Or is that something for UDS? [21:27] updated http://docs.xubuntu.org/ [21:31] would the change proposed by bug 1241210 affect Xubuntu? [21:31] bug 1241210 in software-properties (Ubuntu) "shouldn't use deprecated gtk-logout-helper" [High,In progress] https://launchpad.net/bugs/1241210 [21:34] pleia2: Great! [21:39] i just realised something about the gtk2 sound indicator - it's actually really easy to bodge it and make it work [21:39] all that is required it to change the dbus service name in both halves and add a new dbus service initializer [21:39] then it will be as if it is a totally different indicator [21:40] this is probably what they should have done when changing to gtk3 in the first place [21:41] Please pardon my lack of knowledge on the subject, but would that mess with applications needing to access the dbus service, like gmusicbrowser or such? [21:41] yes, but volume control should work [21:41] hehe [21:41] Yey, not stupidz. \o/ [21:43] but why would they even care about gtk2 "legacy" stuff? [21:43] it wasn't legacy until after it was replaced [21:43] I mean, it's not like they use it, why would anyone else? [21:44] we can't really complain [21:45] i mean even xubuntu is not going to use that in next release [21:47] if "they" are going to fix something i would rather it was #1203888 [21:47] or #1074314 [21:47] Stinks for LXDE, but not our problem at least. [21:48] bug #1074314 bug #1203888 [21:48] bug 1074314 in indicator-datetime (Ubuntu) "indicator-datetime configuration panel only works in Unity session" [Undecided,Confirmed] https://launchpad.net/bugs/1074314 [21:48] bug 1203888 in libappindicator (Ubuntu) "appindicator ignores menu entries after having sent the menu to the indicator" [High,Triaged] https://launchpad.net/bugs/1203888 [21:48] LXDE is moving to Qt anyway [21:48] Hah, nice. [21:48] ali1234: Not in 14.04, iirc. [21:49] yes, but they do depreciate things [21:49] i bet the released version isn't getting much love right now [21:50] i wonder, is it even possible to use indicators in a Qt desktop? [21:51] it must e if unity switches [21:51] but i don't see how [21:51] unless they also rewrite all indicators as Qt at the same time [22:28] what are we telling folks re: sound indicator? is there a bug report w/ work arounds? [22:30] bug report: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1208204 [22:30] Ubuntu bug 1208204 in indicator-sound (Ubuntu) "indicator-sound no longer functions with xfce4-indicator-plugin" [High,Triaged] [22:30] work around at comment 27 [22:30] pleia2: It is in the release notes as a known issue. I'm not aware of a valid workaround. [22:31] skellat: I know [22:31] I gave someone on facebook a link to the release notes, now he wants a work around ;) [22:31] was just wondering what the party line is, I'll advise waiting for a patch [22:32] do we know if anybody is interested in actually fixing it in the indicator-sound package? [22:32] I hear bluesabre wants to [22:32] I heard that too [22:33] must be a rumor [22:33] :) [22:33] bluesabre: Have we tested that workaround as being arch:any since it refers to amd64 only? My netbook is still only 32-bit, for example... [22:34] Editing the file will get overwritten on package updates, but has the exact same upside, if we update to GTK3 it will too. [22:34] skellat: that work around obiously needs a slight tweak for 32-bit [22:35] the gtk3 update would be a wonderful solution [22:36] What will SRU plus backports landing take in the time we've got before T opens? [22:40] * skellat shuffles off to the kitchen [22:40] BECAUSE THAT'S WHERE THE FOOD IS!! [22:40] /Sorry. [22:41] :) [22:54] like expected, people are complaining about the release :( [22:55] Not where I'm looking, but isn't that to be expected? [22:56] it goes like this "That kind of bugs should really prevent a distribution from being released..." [22:57] Hah, yes. The minor glitches shouldn't be there, hold the release! [22:57] (Don't get me wrong, I do kind of like the Debian style, but also does drive you nuts at times.) [22:59] but I'm curious, does Canonical not allow rescheduling the final release? [23:02] /topic Next focus: Tenacious Tribbles [23:05] and launchpad gets flooded by failed upgrade reports =S [23:06] maybe that's business as usual :D [23:24] good night all