[00:07] <Unit193> Anyone else notice that x11vnc no longer works with  -auth guess  ?
[00:47] <Noskcaj_> Did anyone look at bug 1189491 ?
[00:54] <micahg> ali1234: thanks!  I'm on my way
[00:55] <ochosi> Noskcaj: just commented on that bug
[00:55] <micahg> ochosi: andresz branch builds with the new libxfceui?  It's asking for SONAME 1
[00:56] <ochosi> micahg: yeah, you need to --enable-gtk3 though with the andrzejr/wrapper3 branch
[00:56] <micahg> oh, haha, using the wrong flag
[00:57] <ochosi> :>
[00:57] <ochosi> so let's hope it builds now
[00:57] <ochosi> you've seen the build-instructions we've put together on the wiki?
[00:58] <ochosi> micahg: in case not, here they are: https://wiki.ubuntu.com/Xubuntu/Roadmap/Specifications/Saucy/Gtk3Indicators
[00:58] <Unit193> You can run autogen.sh and recreate the orig.tar.gz? 0_o
[01:00] <micahg> ah, you pas it to autogen
[01:00] <ochosi> yes
[01:00] <micahg> ugh, 100th times the charm?
[01:02] <micahg> nope
[01:02] <ochosi> what exactly is failing?
[01:03] <micahg> http://paste.ubuntu.com/6216237/
[01:05] <ochosi> so after skipping the noise, checking for libxfce4ui-1 >= 4.9.0... not found ?
[01:06] <micahg> that's the old version
[01:06] <ochosi> micahg: what about libxfce4ui-1-dev?
[01:06] <ochosi> hm
[01:06] <micahg> it needs both?
[01:06] <ochosi> well the panel is both gtk2 and gtk3
[01:07] <micahg> I can add both
[01:07] <ochosi> i'd assume though that only the new one is needed, but i'm not sure how your whole setup is
[01:08] <micahg> clean chroot with my PPA enabled
[01:09] <ochosi> i think that the panel needs the libxfce4ui-1-dev, at least it should even build without -2 if i'm not mistaken
[01:26] <ochosi> micahg: still no worky?
[01:27] <micahg> nope
[01:27] <Unit193> Stil wonky.
[01:28] <ochosi> :s
[01:28] <ochosi> well, gotta hit the sack
[01:28] <micahg> on the 10th try, I should probably just work on it in a chroot so I don't have to start the build from scratch each time
[01:28] <ochosi> mm
[01:28] <ochosi> good luck with it
[01:29] <ochosi> if you wanna do some easy stuff in between to relax, you could do the gmusicbrowser-upload/s ;) (bluesabre prepared the debdiff and all)
[01:32] <micahg> I'll try to do that tonight, have to run out right now
[04:50] <Noskcaj> micahg, Wouldn't it be easier to work on it just on your system then use a chroot to check dependencies?
[04:50] <Noskcaj> Or are you not on saucy
[05:06] <micahg> not on saucy :)
[05:11] <Pwnna> maybe the devs iwll know
[05:12] <Pwnna> so i have an issue where everytime i press F12, when it is mapped to a keyboard shortcut, it goes and changes some xfconf
[05:12] <Pwnna> specifically, the output-name of /panels/panel-0 and /panels/panel-1
[05:12] <Pwnna> i usually run my laptop with intel graphics card mode
[05:12] <Pwnna> today i turned on nvida mode for a short while to test something
[05:13] <Pwnna> under nvidia, my laptop screen is LVDS-0 while under intel, the screen is LVDS1
[05:13] <Pwnna> i'm back on intel now, but everytime i press F12, which is mapped to my terminal emulator, it changes the output-name of my panels to LVDS-0
[05:13] <Pwnna> wat. this is really annoying as F12 is my terminal key.
[05:15] <Pwnna> i'm like.. grepping through my entire file system for LVDS
[05:15] <Pwnna> and output-name
[05:16] <Pwnna> .any ideas?
[05:23] <Pwnna> .xsession-errors.old:185:warning: output LVDS-0 not found; ignoring
[05:23] <micahg> \o/
[05:24] <Pwnna> but i know that
[05:24] <Pwnna> i know it's trying to change.
[05:24] <Pwnna> wait wat
[05:24] <Pwnna> i got it
[05:25] <Pwnna> it recognized F12 as <Super>F12
[05:25] <Pwnna> it depends on the order
[05:26] <Pwnna> now i redefined <Super>F12, F12 is always detected instead
[05:40] <Unit193> Pwnna: Support in #xubuntu, saucy support in #ubuntu+1
[05:48] <micahg> ok, I finally got it to build, now I need to get the packaging fixed, but not tonight :(
[05:48] <Unit193> Cool, congrats!
[06:46] <Noskcaj> micahg, If there's anything i can do to help, let me know
[07:03] <Unit193> micahg: 10/10/13 which is today (tomorrow?) is the final freeze, just a (hopefully) friendly reminder! :)
[07:05] <Noskcaj> I really hope we don't get this close to the deadline neext cycle
[07:13] <elfy> given the amount of people we have it's more than likely
[08:57] <slickymaster> morning all
[09:09] <knome> hey slickymaster 
[09:12] <slickymaster> hi, knome. Good morning, How are you?
[09:13] <knome> fine!
[09:17] <slickymaster> glad to ear it :)
[09:28] <knome> slickymaster, ready for testing then? :)
[09:30] <slickymaster> knome: yeaps. Waiting for the RC image :) 
[09:30] <slickymaster> knome: in the meanwhile still working on the Xubuntu docs translation, step by step
[09:31] <knome> slickymaster, mhm 
[09:34] <slickymaster> knome: 'mhm' means...?
[09:34] <knome> slickymaster, "ack" ;)
[09:35] <knome> slickymaster, or yup, or okay
[09:35] <slickymaster> knome: :) not I got it
[09:35] <brainwash> ouch, somebody accidentally changed the status of the indicator-sound report to "fix released"
[09:35] <slickymaster> now
[09:35] <Unit193> "I have nothing to say, but would like to confirm I have read it."
[09:36] <brainwash> knome: bug 1208204
[09:36] <brainwash> last comment
[09:36] <knome> done
[09:36] <brainwash> thanks :)
[09:37] <knome> np
[10:07] <brainwash> regarding bug 1229478 - xfpm relies on upower to do suspend/hibernate, but currently upower lies about the availability of logind, thus xfpm falls back to pm-utils.. which is missing
[10:09] <brainwash> ahh, it's a ubuntu/debian specific patch
[10:09] <brainwash> http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/saucy/upower/saucy/view/head:/debian/patches/always_use_pm-utils_backend.patch
[10:42] <brainwash> does a template for the 13.10 release page already exist?
[10:42] <brainwash> with the "known issues" section
[10:51] <brainwash> ochosi: can you still confirm, that "xubuntu" won't react to kb shortcuts for the first 10 sec after login?
[11:08] <ochosi> brainwash: yes
[11:10] <brainwash> do the actions get queued and executed afterwards?
[11:11] <brainwash> I think this is happen on my system
[11:11] <brainwash> happing
[11:12] <brainwash> :/
[11:13] <brainwash> I'll check the log files and enable debug mode if needed
[11:15] <knome> brainwash, no release page, but feel free to list at http://pad.ubuntu.com/Xubuntu1310FinalRelease
[11:16] <ali1234> when the gtk3 indicator 3 ppa is ready, are we gonna basically put it on that bug and say "well, try this"?
[11:16] <ali1234> because i can't see gtk2 sound indicator getting fixed
[11:18] <knome> ali1234, maybe, and get more testing inside the community. not sure if we're getting the gtk3 indicators for the 13.10 release though.
[11:18] <ali1234> indicator3 has been flawless for me so far
[11:19] <ali1234> well, it works exactly as well as it does in unity anyway
[11:19] <knome> yes, but if uploaders have no time, it's not going to get it
[11:19] <Unit193> Final freeze today, so either really sneaky, or packports.
[11:19] <knome> *in
[11:19] <knome> backports too;)
[11:19] <ali1234> yeah i don't expect it to be in 13.10 by default
[11:20] <ali1234> but if gtk2 isn't fixed, people will rage
[11:22] <brainwash> ..and switch to unity :P
[11:23] <knome> ali1234, it's a non-LTS version. i'm starting to be worried if we still have the bug in 14.04
[11:23] <ali1234> yeah. just wondering what we tell people who complain
[11:24] <knome> "it's a non-LTS version"
[11:24] <brainwash> it's non-lts, but the raring users are forced to upgrade soon
[11:24] <knome> sure...but they chose the non-LTS route
[11:24] <Unit193> "Non-LTS" doesn't, or shouldn't mean half-baked.
[11:25] <knome> sure, but there are always bugs and some are more unfortunate than others
[11:25] <knome> we're still looking to get the gtk3 indicator support to backports at least
[11:26] <knome> we can only do what we can do
[11:26] <Unit193> Mhmm.  You just keep on using "Non-LTS" as if it means something. :P
[11:26] <brainwash> the best ofc
[11:26] <knome> Unit193, it does mean something.
[11:26] <knome> Unit193, i don't *want* those to be half-baked, but i'm much less worried about stuff that slips into non-LTS than LTS
[11:27] <brainwash> micahg: any news on bug 1232027 ?
[11:35] <knome> brainwash, i'll get that uploaded.
[11:35] <knome> /seeded
[11:35] <brainwash> thanks
[11:37] <brainwash> knome: do you know why this branch hasn't been reviewed yet? https://code.launchpad.net/~smd-seandavis/xubuntu-default-settings/b2_fixes/+merge/187127
[11:38] <knome> i've just community-approved it.
[11:39] <ali1234> so we don't tell them that gtk3 indicators are available for testing?
[11:39] <ali1234> we just say "it's broken, sorry"
[11:40] <knome> we can't tell them they are available until they are available
[11:43] <ali1234> and when they are?
[11:43] <knome> when somebody has time to set them up
[11:45] <ali1234> micahg is working on it the past two days... looks like it is nearly done
[11:45] <knome> yes. if he gets it done before the freeze, we might get it in.
[11:45] <knome> and the bugfix
[11:45] <knome> *then
[11:45] <brainwash> knome: will seeding the package actually install it (live installer)?
[11:46] <ali1234> ok but that isn't my question
[11:46] <knome> brainwash, yes, seeding means exactly that
[11:46] <brainwash> knome: ok :)
[11:46] <knome> ali1234, the answer to your question is: we will let people know what they should do to get gtk3 indicators when we know how they can and have it set up.
[11:47] <knome> ali1234, and we will make them available in the release if at all possible, and if not, then backports if possible
[12:01] <knome> brainwash, 
[12:01] <knome> 14:58 notice < queuebot:#ubuntu-release: Unapproved: xubuntu-meta  (saucy-proposed/universe) [2.170 => 2.171] (xubuntu)
[12:19] <ochosi> brainwash: yes, here the actions get queued and executed 10 secs after login
[12:27] <elfy> knome: is RC not a milestone release - or is it just that they've not gone out yet?
[12:28] <knome> elfy, i'd say just not out yet
[12:28] <elfy> k - thanks
[12:30] <elfy> knome: just a fyi - I've started looking at the desktop and post install testcases now - talk to you soonish about those
[12:31] <knome> yup, cheers
[12:36] <brainwash> elfy: hey, can you confirm that keyboard shortcut "actions get queued and executed 10 secs after login"? for example launching the terminal via kb shortcut immediately (well, lets say 2-3sec) after logging in
[12:36] <gdos> 2 part question: how do i submit a feature request and search for a possible bug (such as in the custom application launcher panel)?
[12:37] <elfy> brainwash: not now I can't - got a short while at home for a cuppa then back to work
[12:37] <brainwash> elfy: ok
[12:37] <elfy> is there a bug for it?
[12:38] <ochosi> gdos: if it's an xfce component, go to bugs.xfce.org
[12:41] <ochosi> and what "custom application launcher panel" are you referring to?
[12:42] <gdos> the application launcher (the one that you can customize); if i add 2 or more apps to it, the 1st app shown won't launch more than once.
[12:42] <gdos> would that be caleld the xfce4-quicklauncher-plugin?
[12:43] <ochosi> possible, i don't use that
[12:44] <ochosi> what does your panel config call it?
[12:45] <gdos> applauncher
[12:46] <gdos> actually under xubuntu its called launcher under suse its called applauncher
[12:46] <ochosi> right, so that's part of the xfce4-panel's core plugins
[12:46] <gdos> yep. just tested it.
[12:46] <ochosi> what feature would you request exactly?
[12:48] <ochosi> but yeah, feelo free to search bugzilla first
[12:48] <ochosi> bbiab
[12:49] <ali1234> gdos: i can't reproduce launcher bug
[12:56] <gdos> ali1234: under applauncher properties > advanced tick the box that says show last item. (i originally had that ticked and now have it un-ticked either way for me it doesn't work.)
[12:57] <ali1234> gdos: what version are you on?
[12:57] <gdos> xubuntu? 13.04
[12:57] <gdos> xfce4-panel 4.10.0
[12:57] <ali1234> i ticked the box. no change
[12:57] <ali1234> i'm on 13.10/4.10.1
[12:57] <gdos> hmm...
[12:57] <ali1234> what specific apps are you using?
[12:58] <ali1234> on the launcher i mean
[12:58] <gdos> pterm and chromium
[12:58] <ali1234> can you try with, say, xfce-terminal and abiword? (that's what i'm testing with)
[12:58] <gdos> yes.
[12:59] <gdos> i'll create a few more with different apps (some more than others); brb.
[12:59] <ali1234> i wouldn't be surprised if this was fixed - loads of stuff has been
[12:59] <gdos> ok.
[13:00] <gdos> same thing.
[13:01] <gdos> let me go check which version of xfce my suse machine is using...
[13:03] <ali1234> ok i tried in a 13.04 VM and i still can't reproduce
[13:11] <gdos> ok. i tried it on suse 12.3 (xfce 4.10.0) and i was able to reproduce it. when does xubuntu 13.10 come out? 23rd? 
[13:14] <ali1234> yeah
[13:15] <ali1234> actually, the 17th apparently
[13:22] <gdos> ok. ali1234: i will wait and then upgrade and see if it replicates. in the mean time i'll try it on guest login and see if it may simply be a setting issue.
[14:04] <ochosi> brainwash: https://github.com/shimmerproject/elementary-xfce/commit/c4bf794a980766799312f134b04f15810ce8a536
[14:16] <brainwash> ochosi: thanks, this is a big step forward, finally I can enjoy a high res trash bin icon :)
[14:17] <ochosi> brainwash: i know, right? :)
[14:19] <brainwash> ochosi: and I'm wondering again, are there any other people out there affecting by the delayed execution of kb shortcuts after login..
[14:19] <ochosi> well tbh i hope not
[14:20] <ochosi> have you tried to create a new user in saucy and check whether that fixes the issue?
[14:20] <brainwash> oh, not yet, only created a log of the session dbus communication so far (tons of lines)
[14:21] <brainwash> I'll try that
[14:21] <ochosi> well that would seem the most obvious and easy approach to me at least
[14:23] <brainwash> 2nd user is affected too
[14:24] <ochosi> hm, could still be an upgrade-only issue but it's less likely now i'd say
[14:25] <brainwash> I'll investigate some more and report back
[14:28] <ochosi> cool thanks
[14:30] <ochosi> bbl
[16:04] <knome> elfy, i've set up http://pad.ubuntu.com/Xubuntu1310FinalRelease
[16:08] <knome> xubuntu.org says:
[16:08] <knome> Xubuntu is a community‑developed, Ubuntu‑based Linux operating system.
[16:08] <knome> @Xubuntu says:
[16:08] <meetingology> knome: Error: "Xubuntu" is not a valid command.
[16:08] <knome> Xubuntu is a community developed, elegant and easy-to-use operating system based on Ubuntu.
[16:09] <knome> inconsistency, if not else, dash in community(-)developed
[16:09] <knome> and we could probably drop the commas
[16:11] <holstein> xubuntu is an offical community designed operating system based on ubuntu and built to be elegant and easy to use
[16:12] <knome> official is irrelevant
[16:12] <holstein> but, what do i know ;)
[16:12] <holstein> eh.. it comes up a lot
[16:12] <knome> we're only an official flavor, but if we don't mention flavor, it's ambiguous what the "official" means
[16:13] <holstein> otherwise, whats the difference in mint xfce?.. the official "blessing" of ubuntu (an other specifics"
[16:13] <knome> i think the reason why twitter is what it is is a character limitation
[16:13] <holstein> but, at a glance, both are "based on ubuntu"
[16:13] <holstein> i just field that quesiton a lot.. even for seasoned linux users in my LUG..
[16:13] <knome> sure, but what you say doesn't specify "what" official we are...
[16:14] <holstein> right.. "official" by itself doesnt mean anything
[16:14] <knome> and the way the sentence is set up, it sounds like we're an "official operating system"
[16:14] <holstein> i mean, at some point, the user has to look something up and learn.. or just use it
[16:14] <holstein> "officially based on ubuntu"?... 
[16:14] <knome> i don't think we need to emphasize the "official flavorness" in the punchline
[16:14] <knome> well heh, that's not accurate either
[16:15] <knome> if you think about it, isn't mint xfce officially based on ubuntu as well?
[16:15] <holstein> nah.. i dont think you do either.. but i see that often
[16:15] <knome> eg. ubuntu can't deny mint is based on ubuntu
[16:15] <knome> so it's kind of... officially based on ubuntu
[16:15] <holstein> knome: right.. its not something that can be summed up in a sentence, really
[16:15] <knome> yep.
[16:15] <holstein> but, it would be nice..
[16:16] <knome> but it's true we don't say that on our website frontpage.
[16:16] <knome> we could
[16:16] <knome> but probably not the punchline
[16:16] <pleia2> sorry, airplane wifi is being.... airplane wifi-ish :)
[16:17] <holstein> knome: and it could be that im answering the question mint users have about why they cant get support.. rather that "what is xubuntu"
[16:17] <knome> :)
[16:17] <pleia2> I think I might have pulled the twitter one from our strategy doc
[16:18] <knome> i think it's a compromise
[16:18] <knome> we wanted to tell as much as possible
[16:18] <knome> the easy-to-use and elegant stuff is on the next sentence on the website
[16:18] <pleia2> yeah
[16:18] <knome> what about:
[16:19] <knome> TITLE: Xubuntu is a community developed elegant and easy-to-use operating system.
[16:19] <knome> NEXT SENTENCE: Xubuntu is a regocnised flavor of the Ubuntu operating system.
[16:19] <pleia2> it's weird without the commas, hard to parse
[16:20] <knome> ... developed, ...?
[16:20] <pleia2> yeah
[16:20] <knome> note that i dropped ubuntu from the title.
[16:20] <pleia2> I think that's fine
[16:21] <knome> should we drop "Linux" to the next paragraph as well?
[16:23] <pleia2> we should mention linux somewhere on our front page
[16:23] <knome> yeah, but does it have to be on the cat-sized title?
[16:23] <knome> from a pure marketing point of view, it might not be a good selling point, even if we think it's cool.
[16:24] <pleia2> yeah, it doesn't need to be in the header
[16:24] <pleia2> hehe, cat-sized
[16:24] <knome> that's a known finnish phrase
[16:25] <knome> "kissan kokoiset kirjaimet" -> cat-sized letters
[16:25] <pleia2> does it mean medium? :)
[16:25] <pleia2> liken ot a mouse, and not a dog
[16:25] <knome> no, it means BIG
[16:25] <pleia2> elephants are big!
[16:25] <pleia2> also pleia2, but not cats :)
[16:26] <pleia2> I suppose tigers are big
[16:26] <knome> Xubuntu is a Linux operating system and an officially recognised flavor of Ubuntu.
[16:26] <knome> that?
[16:26] <knome> is that a bit clumsy, or is it just me
[16:26] <pleia2> clumbsy
[16:26] <knome> hehe
[16:27] <pleia2> Xubuntu is an officially recognised flavor of the Ubuntu operating system
[16:27] <knome> that's what we have now, but since linux ain't on the title..
[16:27] <GridCube> Xubuntu is an officially recognised flavor of the Ubuntu linux operating system
[16:27] <knome> what about:
[16:28] <pleia2> oh, heh
[16:28] <knome> yeah, that.
[16:28] <knome> but ubuntu doesn't use linux themself
[16:28] <knome> and shouldn't that be Linux, not linux
[16:29] <pleia2> GridCube: +1 Linux
[16:29] <GridCube> uppercase L?
[16:29] <knome> ok, see how it looks now
[16:29] <pleia2> yeah
[16:29] <GridCube> i see
[16:30] <knome> i think that's much better
[16:30] <GridCube> what about, Xubuntu is an officially recognised flavor of the Ubuntu's Linux operating system
[16:30] <knome> no, 
[16:30] <knome> there is no linux system that is "ubuntu's"
[16:30] <pleia2> yeah, first way you had it was good
[16:30] <GridCube> P: ok
[16:30] <knome> if we want to tweak it, we could say
[16:30] <knome> of the Linux-based Ubuntu operating system
[16:31] <GridCube> thats clumbsy again
[16:31] <knome> only a bit, and that would be in line with the fact that canonical doesn't say "Ubuntu Linux" any more
[16:31] <knome> one more thing:
[16:31] <knome> should we swap the two paragraphs?
[16:32] <knome> first telling who xubuntu is perfect for, then telling what it is
[16:32] <knome> and, easy-to-use vs. easy to use
[16:34] <GridCube> what if instead of easy to use we use "accesible" or "user friendly"
[16:34] <knome> we have easy-to-use in our strategy document, and tbh, i'd say changing the wording (at least to "accessible") changes the meaning
[16:35] <GridCube> alright
[16:36] <pleia2> I hate -s
[16:36] <pleia2> easy to use is nice
[16:36] <knome> hehe
[16:36] <knome> what about the paragraph switch?
[16:37] <knome> actually our SD says:
[16:37] <knome> Xubuntu is a community-developed, Ubuntu-based operating system that combines elegance and ease of use.
[16:38] <knome> which is nice wording
[16:38] <knome> except ubuntu-based and the other dash
[16:41] <pleia2> yeah
[16:41] <knome> ok, that's updated
[16:41] <knome> again: what about the paragraph swap?
[16:44] <pleia2> I need to wait for better internet, taking too long to load pages
[16:44] <knome> i can paste
[16:44] <knome> Xubuntu is an officially recognised flavor of the Ubuntu Linux operating system. Xubuntu comes with Xfce, which is a stable, light and configurable desktop environment.
[16:44] <knome> Xubuntu is perfect for those who want the most out of their desktops, laptops and netbooks with a modern look and enough features for efficient, daily usage. It works well on older hardware too.
[16:46] <pleia2> that's what we want, or what we have?
[16:46] <knome> what we have
[16:46] <GridCube> i like it like that
[16:47] <knome> i'm thinking whether we should swap
[16:47] <pleia2> GridCube: +1
[16:47] <knome> i'm thinking if liking it like that is because we appreciate more technical details than most of our users
[16:47] <knome> but sure, let's keep it like that
[16:48] <GridCube> no, i mean, if we say what it is then we can understand what its used for
[16:48] <GridCube> if you know what something is used for, but not what it is...
[16:48] <GridCube> in any case, its far too close for that distinction to matter too much
[16:52] <knome> right, the social media thing was:
[16:52] <knome> "If you're using our logo as your avatar or in your website, please use the latest version. If you need help with converting to a specific size, ask the xubuntu-devel mailing list."
[16:52] <knome> + "Thanks!"
[16:53] <knome> once we get the static. subdomain up, we could dump any images for those requests in a folder there
[16:53] <knome> (for any sensible requests)
[16:59] <GridCube> knome, talking about images
[16:59] <knome> yes?
[16:59] <GridCube> when would you think you can start the desktop showcasing?
[16:59] <knome> i will have to look into that when i seriously have some time
[16:59] <knome> i've been awfully busy lately
[17:00] <GridCube> we have about 6 images that comply to the rules so its like 2 months if we put a new one every like 2 weeks
[17:00] <GridCube> knome, sure
[17:00] <GridCube> :)
[17:00] <knome> bbl->
[17:24] <elfy> brainwash: can't confirm that lag in kbd shortcut immediately after logging in
[17:24] <elfy> in fact the one I tried worked immediately
[17:36] <ochosi> hm, i guess that's good news...
[17:37] <ochosi> cause i'd really prefer if that were our private bug
[17:37] <elfy> :)
[18:01] <knome> probably not though.
[18:01] <knome> we should fix that for 14.04
[18:01] <knome> i'd also say we've hit our deadline for the gtk3 indicators
[18:03] <elfy> possibly - couldn't we call it a Non-release-critical-but-nice-to-have bugfixes :)
[18:04] <elfy> do we have any working indicators? 
[18:04] <knome> some might work...
[18:05] <ochosi> no idea, i haven't used gtk2 indicators in ages
[18:05] <knome> we should just get them in in backports or SRU
[18:06] <elfy> ochosi: only one I had was the sound one till it went
[18:06] <knome> (-updates)
[18:07] <brainwash> and nm applet still works
[18:39] <brainwash> why not replace the sound indicator with the mixer panel plugin? :)
[18:40] <ochosi> cause that doesn't work so well with pulseadio
[18:40] <ochosi> not so well = not at all
[18:40] <brainwash> works for me, but it's a bad solution anyway
[18:40] <ochosi> we could add a launcher for pavucontrol :p
[18:41] <brainwash> the mixer plugin can be configured to open pavucontrol
[18:41] <ochosi> hm, that would be okayish
[18:42] <ochosi> i've never tried it
[18:42] <ochosi> gotta go
[18:42] <ochosi> hf
[18:42] <brainwash> bye
[18:44] <ali1234> mixer doesn't work at all for me
[18:45] <brainwash> =S
[18:46] <knome> ali1234, yes, it doesn't work with pulseaudio
[18:52] <brainwash> volume changing?
[18:53] <knome> xfce4-mixer, or the panel plugin
[18:53] <brainwash> panel plugin
[18:54] <brainwash> as fallback solution for the sound indicator
[18:55] <knome> i mean, neither works with pulseaudio
[19:13] <brainwash> knome: works for me, weird
[19:14] <brainwash> <property name="sound-card" type="string" value="PlaybackBuiltinAudioAnalogStereoPulseAudioMixer"/>
[19:14] <brainwash> or what exactly does not work?
[19:26] <elfy> brainwash: ok - I'll confirm it takes a while for \ kbd shortcut to work when login follows a restart/start
[19:27] <elfy> but then it takes a while for any apps starting to start too
[19:27] <elfy> back tomorrow
[19:32] <Noskcaj> Is there anyone with a xubuntu daily iso who can report a bug for me? My pc is too low on RAM to do it
[19:33] <Noskcaj> Go to the manual partitioning options and notice that the checkbox has a grey square around it
[21:49] <skellat> As seen over in #ubuntu-release moments ago: "(05:46:55 PM) Laney has changed the topic to: Released: 13.10 Beta 1, 13.04, and 12.04.3 | Archive: Frozen, final freeze | Saucy Salamander Release Coordination.  Please don't upload things during freezes where you shouldn't, or be prepared to apologise to the release team | we accept payment in cash, check or beer | melior malum quod cognoscis"
[22:04] <Unit193> [17:46:55] Irssi: Topic: -: Archive: frozen
[22:04] <Unit193> [17:46:55] Irssi: Topic: +: Archive: Frozen, final freeze
[22:38] <Noskcaj_> What packages do we still need to convert to python 3 for 14.04?
[22:42] <knome> brainwash, hey, you around?
[22:43] <brainwash> knome: ye
[22:44] <knome> brainwash, was there a bug for the lag for the shortcuts? can't seem to find it
[22:45] <brainwash> knome: I didn't create one yet
[22:45] <knome> oki, ping me when you do
[22:45] <knome> also, bug 1232027
[22:48] <brainwash> something is definitely wrong, the delayed kb shortcut actions are just a noticeable hint I think, one test account is not able to trigger any of the xfce kb shortcuts.. the session seems somewhat stuck
[22:49] <knome> sure, that's possible
[22:49] <brainwash> yap, pm-utils finally included, 1 bug less
[22:49] <brainwash> :)
[22:50] <brainwash> no clue, why my test system is acting so weird
[22:51] <knome> you should be happy it's your test system, not your production machine
[22:53] <brainwash> usually people would complain instantly about such an issue, but apparently almost nobody seems to be affected
[22:53] <knome> except three people in this channel...
[22:54] <knome> maybe people just think their computers are super slow
[22:54] <knome> i mean, it is an annoying bug
[22:54] <knome> ...otoh, you forget it when it starts working.
[22:54] <brainwash> right, some randomness seems to be involved
[22:56] <brainwash> knome: can you confirm this problem? or not tested yet?
[22:57] <knome> i can confirm that bug on raring at least.
[22:59] <brainwash> mmh, maybe an upstream report does already exist, addressing this kind of problem
[22:59] <brainwash> I'll do some research
[23:00] <knome> thanks
[23:00] <knome> everybody: i just poked around a bit at https://blueprints.launchpad.net/ubuntu/+spec/topic-t-flavor-xubuntu
[23:01] <knome> look at the whiteboard and tell me if you think there's something else we should target
[23:02] <brainwash> unused maximize button :D
[23:02] <knome> that's in the bug list
[23:05] <brainwash> maybe worth fixing this one
[23:05] <brainwash> so only ubiquity is affected?
[23:06] <knome> no, it's actually any 'dialog' window in xfce
[23:06] <brainwash> ah ok, so I didn't notice the non functional maximize button yet
[23:07] <knome> well it's only the 'dialog' type windows :)
[23:08] <brainwash> needs to fixed upstream, so an upstream report is required I think
[23:12] <brainwash> micahg, mr_pouit: can you review https://code.launchpad.net/~smd-seandavis/xubuntu-default-settings/b2_fixes please?
[23:46] <knome> hey jjfrv8 :)
[23:46] <jjfrv8> howdy, knome