[01:27] <bluesabre> micahg, mr_pouit: if you get a chance. https://bugs.launchpad.net/ubuntu/+source/catfish/+bug/1228447
[01:32] <Noskcaj> bluesabre, It might be worth fixing a few of http://lintian.ubuntuwire.org/saucy/full/xubuntu-devel@lists.ubuntu.com.html#catfish_0.8.1-0ubuntu1  if you're uploading
[01:34] <bluesabre> goodness
[01:34] <Noskcaj> yeah
[01:35] <bluesabre> yeah, I mean to fix all the lintian bugs with catfish in the near future
[01:35] <bluesabre> (and mugshot)
[01:35] <bluesabre> but in general, wow, we suck with lintian
[01:35] <bluesabre> or I do
[01:35] <bluesabre> :D
[01:35] <bluesabre> Noskcaj: not sure if you've seen this, http://eriberto.pro.br/blog/?p=1289
[01:36] <Noskcaj> bluesabre, i normally add those tags manually, thanks for the link
[01:37] <Noskcaj> I'll fix all the lintian errors in catfish now. Were you ever going to try and get it in debian again?
[01:37] <Unit193> bluesabre: Yep, something like lintian --pedantic -I -i  would work too, but I don't normally use long description.
[01:37] <bluesabre> Noskcaj: the goal is to get it back into debian
[01:38] <Noskcaj> ok
[01:38] <bluesabre> I guess once we fix it in ubuntu, we should be able to sync it back
[01:38] <bluesabre> I'm still pretty new with working with lintian
[01:38] <Noskcaj> I have cows to feed, i'll be back soon
[01:41] <bluesabre> k
[01:41] <bluesabre> I think I'm heading to bed, be back in ~7-8 hours
[01:45] <bluesabre> actually, how do you get lintian on your system to give all the feedback displayed on that site?
[01:52] <Unit193> bluesabre: lintian -I --pedantic xombrero_1.6.3-1vanir0_i386.changes
[01:52] <Unit193> `debuild` runs it after building.
[01:57] <bluesabre> mine still only displays a minimal amount of data
[01:57] <bluesabre> like for catfish-0.8.2
[01:57] <bluesabre> lintian --pedantic -I -i catfish_0.8.2-0ubuntu1.dsc 
[01:57] <bluesabre> I: catfish source: vcs-field-not-canonical svn://svn.debian.org/python-apps/packages/catfish/trunk/ svn://anonscm.debian.org/python-apps/packages/catfish/trunk/
[01:57] <bluesabre> and then all the help text for that single item
[01:57] <bluesabre> and nothing more
[01:58] <Unit193> Yes, that's the source package, you need to run it on the built binary.  (_amd64.changes)
[01:58] <bluesabre> ah
[01:58] <bluesabre> thanks
[01:58] <Unit193> "
[01:59] <Unit193> "There are three ways to specify binary, udeb or source packages for Lintian to process: by file name (the .deb file for a binary package or the .dsc file for a source package), by naming a .changes file, or by using a lab query (see "LAB QUERY" below)."
[02:00] <Unit193> Running it on the changes file runs it on everything listed in there.
[02:00] <bluesabre> right
[02:00] <bluesabre> that makes more sense
[02:00] <bluesabre> maybe tomorrow I'll get a chance to start cleaning these things up
[02:19] <Noskcaj> bluesabre, Can you have a look at the debian/copyright file for catfish tomorrow? It should be put into the debian format, but i've not been around long enough to fill in the blanks
[02:31] <Noskcaj> Why does catfish use a configure script if it's python?
[02:40] <ali1234> Noskcaj: it looks like it uses a hand coded build.py to actually build it, and then the configure script is just to ease packaging
[03:06] <Noskcaj> bluesabre, I've uploaded a cleaner debdiff to the bug
[03:08] <Noskcaj> bluesabre, You'll need to fix "executable-not-elf-or-script" upstream by adding shebangs. 
[03:08] <Noskcaj> python-script-but-no-python-dep is because you don't use a setup.py
[03:41] <Noskcaj> The installer theme is slightly broken. Note the "format" check-box http://imgur.com/JH0JjdB
[07:34] <elfy> knome: nice wallpaper :)
[07:35] <elfy> ochosi: 3 boots this morning - each time the sound indicator fails - needs the panel restarting - not sure where that would get logged
[07:35] <ochosi> elfy: not sure either
[07:36] <ochosi> but really, sometimes it just works for me
[07:36] <ochosi> you can take a look at ~/.cache/upstart/startxfce4
[07:36] <ochosi> but i don't think you'll find anything useful...
[07:37] <elfy> ok 
[07:37] <elfy> just thought I'd mention that it's more not here than is 
[07:38] <elfy> nothing in that file from today at all :)
[11:46] <bluesabre> Noskcaj, nice work on the catfish debian!
[11:47] <bluesabre> I'll work on the executable-not-elf-or-script
[11:48] <bluesabre> (for next release)
[11:49] <elfy> I'll remove elf from my ping list ... 
[12:03] <bluesabre> haha
[12:03] <bluesabre> then I'll work on executable-not-elfy-or-script
[12:04] <bluesabre> then I'll work on executable-not-elfy-or-script
[12:04] <bluesabre> :D
[12:05] <elfy> :)
[12:05] <elfy> I kept seeing the pings - couldn't work out what was going on lol
[12:09] <brainwash> elfy: can you confirm bug 1227637 ?
[12:10] <elfy> no - I've been installing and updating packages with no problem at all
[12:10] <brainwash> using the command line?
[12:10] <elfy> yep
[12:11] <brainwash> well, it's not a problem, just an annoying warning :)
[12:11] <elfy> and synaptic and update mangler 
[12:11] <elfy> only thing I've not used on this specific install is the USC thing
[12:11] <elfy> brainwash: I understand - if I could confirm it I would :)
[12:13] <brainwash> strange, I would assume that every xubuntu saucy user is affected
[12:16] <elfy> I'll boot an iso see if I can see it there
[12:25] <elfy> nothing there either
[12:27] <brainwash> try glib-compile-schemas /usr/share/glib-2.0/schemas
[12:29] <brainwash> it's this key:
[12:29] <brainwash> [com.ubuntu.update-notifier]
[12:29] <brainwash> auto-launch=false
[12:30] <elfy> I still don't see it 
[12:30] <brainwash> and "gsettings get com.ubuntu.update-notifier auto-launch"?
[12:31] <elfy> No such key 'auto-launch'
[12:32] <brainwash> so why don't you get the warning about the missing key when running apt-get and the schemas get compiled? =S
[12:32] <elfy> no idea :)
[12:34] <brainwash> elfy: once again, thanks for testing :)
[12:34] <elfy> No such key 'auto-launch' in schema 'com.ubuntu.update-notifier' as specified in override file '/usr/share/glib-2.0/schemas/20_xubuntu-default-settings.gschema.override'
[12:34] <brainwash> that's the warning
[12:35] <elfy> that's what is said when doing the glib-compile thing too
[12:35] <brainwash> yes, kinda expected^^
[12:35] <elfy> ok
[12:36] <brainwash> so you are affected too
[12:36] <elfy> well I was when I did glib-compile-schemas /usr/share/glib-2.0/schemas
[12:36] <elfy> http://pastebin.com/T5EJUnEH
[12:37] <brainwash> try "sudo apt-get install --reinstall xubuntu-default-settings"
[12:37] <brainwash> these should trigger the compiling process of the schema files
[12:37] <brainwash> this
[12:38] <elfy> http://pastebin.com/rUsU36SW
[12:38] <brainwash> there we go
[12:39] <elfy> I see no warning when I removed or installed arandr
[12:39] <brainwash> you could add the output to the bug report
[12:40] <brainwash> yes, the schama files don't get compiled every time your run apt-get
[12:40] <brainwash> only, when triggered
[12:40] <elfy> I'm obviously not understanding what you're trying to say here 
[12:41] <brainwash> "Processing triggers for libglib2.0-0"
[12:42] <elfy> ok - we were talking at cross purposes here - I thought you meant when installing anything :)
[12:42] <elfy> I'll add the output to the bug for sudo apt-get install --reinstall xubuntu-default-settings
[12:43] <elfy> it's been a long morning 
[12:44] <brainwash> well, not every time, but I have seen the warning almost every time lately when doing updates :)
[12:44] <elfy> lp is being a pita
[12:45] <brainwash> and it's not about how often you see the warning (or even at all), but about the old key specified in the xubuntu-defaults override file
[12:46] <elfy> yep
[12:46] <brainwash> oh, lp is down
[12:46] <elfy> Launchpad seems to be down
[12:47] <brainwash> #launchpad
[12:47] <elfy> forum seems to be down as well
[12:48] <smartboyhw> They lost a datacentre!
[12:50] <elfy> taken the forum down too
[12:52] <elfy> brainwash: when it's up again I'll add that output 
[13:09] <smartboyhw> elfy, are power failures in the UK often? I heard that it's a power failure/switch failure:)
[13:09] <elfy> not often
[13:11] <smartboyhw> Hmm
[13:13] <elfy> We are not aware of a power cut affecting SE1 0SU.
[13:13] <elfy> assuming data centre is at head office
[13:14] <smartboyhw> I think they have many data centres.
[13:14] <elfy> I'd guess so too - but you mentioned london ;)
[13:14] <elfy> this is offtopic for this channel though
[13:15] <smartboyhw> Yeah \o.
[13:15] <smartboyhw> Sorry people
[15:47] <brainwash> elfy: thanks for adding the terminal output to the bug report
[15:47] <elfy> in the end :p
[15:48] <brainwash> but you did forget to add yourself to the affected user list
[15:48] <brainwash> =S
[15:48] <elfy> no I didn;t
[15:48] <elfy> it crashed on me again 
[15:49] <elfy> I have done it now ;)
[15:49] <brainwash> it's all about the bug report heat :D
[15:49] <elfy> and it's gone again 
[15:51] <brainwash> meanwhile I did a test installation of xubuntu saucy.. is gigolo supposed to have a wifi icon?
[15:52] <brainwash> and abiword has a theme issue, the writing area is surrounded by a big black border, which makes the ruler on top of the document almost invisible
[15:53] <elfy> I'm off for a bit now
[15:53] <brainwash> cya :)
[17:21] <OvenWerks> bluesabre: I think you have been working on display in settings. I don't know if this is that or something else.
[17:21] <OvenWerks> bluesabre: in any case, it seems display 0 draws/redraws first and screen 1 second
[17:23] <OvenWerks> In the case of dual displays that are "the same as" this means that screen 1 settyings override screen 0 setting.
[17:23] <OvenWerks> *settings
[17:45] <OvenWerks> This a problen also if screen 1 is is smaller and displays on top of screen 0 as some of the intel graphics systems in the atom boards seem to require.
[17:46] <OvenWerks> The GPU on the atoms boards is closed :P
[17:48] <OvenWerks> The hacked open one has issues... but drawing screen 1 first and then screen 0 at least hides them. KDE seems to have gotten it to work, so it is not an xorg thing.
[20:05] <Noskcaj> debian's just released a fix for xfhelp4 and bug 1198746
[20:10] <Noskcaj> also, xfwm4 has had a manpage update release and squeeze will now install in saucy
[20:12] <Noskcaj> Do we want any of them?
[20:44] <Noskcaj> micahg, mr_pouit. Should we sync/merge any of the above?
[20:45] <brainwash> ochosi: http://bazaar.launchpad.net/~lightdm-gtk-greeter-team/lightdm-gtk-greeter/trunk/view/head:/src/lightdm-gtk-greeter.c#L1781
[20:46] <brainwash> ochosi: else { gtk_widget_hide (GTK_WIDGET (gtk_builder_get_object (builder, "language_menuitem"))); }
[20:47] <brainwash> ochosi: ^ this does hide the language menu completely, no more white pixel
[20:48] <brainwash> bug 1191509
[20:55] <ochosi> brainwash: great! thanks, will test and commit on monday
[21:02] <brainwash> ochosi: between, the context menu for the password input field can be disabled by the theme? or did you assign the issue to shimmer-themes, because it is visually broken?
[22:11] <Noskcaj> I'll request the two syncs and wait for micah or lionel to look at if we want the merge
[22:12] <Noskcaj> Once the packages leave NEW