[01:12] <lamont> hrm... so what's the new soundjuicer, now that it's in universe?
[01:14] <wgrant> lamont: Rhythmbox has done that for years, hasn't it?
[01:15] <lamont> used to be it did it by launching sound-juicer, I thought
[01:15] <lamont> just ran into it when my daughter asked me to put soundjuicer on her laptop, and it fetched from universe
[01:16] <wgrant> It doesn't appear to use Sound Juicer any more.
[01:23] <lamont> it could also be that I'm misremembering ... ta
[14:54] <real_ate> hi guys... i'm wondering if anyone has 5 mins to help me out with a bit of mentoring. I just have 2 things i need explained to me before i can make the app that i want to make but i'm a KDE/Qt programmer and i don't know how the GTK/Ubuntu technologies fit together
[14:55] <Riddell> real_ate: use KDE/Qt then?
[14:56] <real_ate> Riddell: well the app i want to build is for an installation of pure Ubuntu machines
[14:56] <real_ate> not really a production environment but its close ;)
[14:56] <real_ate> and KDE is not an option, so i wanted to learn a bit of the local lingo ;)
[14:57] <real_ate> ... i'll just throw out my first question here and if anyone things i shouldn't be asking like this please just let me know
[14:59] <real_ate> one of the main requirements of the app is that there is a status icon at all times. and based on the work for lucid that is described here: https://wiki.ubuntu.com/DesktopExperienceTeam/ApplicationIndicators There is a good bit of info for me to work with
[15:00] <real_ate> but some code has to run to setup the application indicator but i don't know where that code should be run from
[15:01] <real_ate> should i be looking to create a startup python script or something? or is there a better way to do this?
[15:36] <real_ate> hello again
[15:36] <real_ate> can anyone explain the message ** (test.py:22994): WARNING **: Unable to create Ayatana Watcher proxy!  Could not get owner of name 'org.ayatana.indicator.application': no such name
[15:36] <real_ate>  to me?
[19:17] <jussi01> Hrm, seems to be that the last kernel update broke the anysee driver...
[22:24] <flyback> running hmm
[22:24] <flyback> 8.10 here
[22:24] <flyback> and I don't know if it's changed in 9 or whatever it is
[22:24] <flyback> but seriously consider compiling xchat2 to *NOT* accept dcc by default
[22:25] <flyback> some cornhole last night dcc send spammed me with rather disgusting pornographic titles and I ended up having to just kill X to get rid of all the directory prompts
[22:27] <crimsun> flyback: patches welcome.
[22:27] <flyback> don't think you need a patch it's just a compile time option
[22:28] <crimsun> flyback: i.e., debdiff attached to a bug report
[22:29] <flyback> I run the livecd for now so kinda hard to setup a compile fix etc :P
[22:30] <crimsun> nothing in ./configure --help output.
[22:30] <crimsun> are you referring to something else?
[22:30] <flyback> no the default config is set to auto get dcc
[22:31] <crimsun> be aware of debian/patches/11_fix_dcc_close_message.dpatch
[22:33] <crimsun> hmm, not applied to current builds.
[22:35] <flyback> it's not a bug
[22:35] <flyback> they just setup their default config in a insecure manner
[22:35] <crimsun> flyback: so, provide a patch
[22:36] <crimsun> either I spend a night reading xchat's source instead of fixing alsa bugs, or someone else (you?) more familiar with xchat's source dives in directly
[22:39] <flyback> it was just a suggestion
[22:39] <flyback> sheesh
[22:40] <crimsun> I think you fail to understand me. Suggestions can be converted into patches. #ubuntu-motu can assist.
[22:41] <flyback> unfortunitely I don't have time or the mental health left to work on that right now
[22:43] <flyback> thx for the help thought