[00:25] <asac> kenvandine_wk: can you please subscribe motu-release, and attach the patches we have now to the two bugs and set bug status to New?
=== bittin___ is now known as bittin`
=== calc_ is now known as calc
=== tkamppeter_ is now known as tkamppeter
[08:12] <pitti> bryce: reverting entire mesa in a SRU sounds very unlikely to me, since it has a high potential for breaking other systems
[08:13] <pitti> bryce: (like systems configured for UXA)
[08:13] <bryce> pitti: we may not need to -- we've had a bit of a brainstorm on #ubuntu-x tonight
[08:13] <pitti> bryce: ah, nice; just reading backscroll from the meeting
[08:14] <bryce> pitti: but I will point out that UXA is definitely not a supported option yet
[08:14] <bryce> or at least, it's not one I am ready to support yet, myself
[08:15] <pitti> bryce: today I thought about converting your troubleshooting guide to a more end user related document "What can you do on intel driver problems", e. g. collect some workarounds
[08:15] <pitti> which we could link from the release notes
[08:15] <bryce> that's a good idea
[08:17] <pitti> bryce: I'll mail you for review when I'm done
[08:18] <bryce> thanks
[08:30] <seb128> mvo: <DBO>	i just came here to say that there are redundant plugins enabled in compiz, and they are causing us to waste CPU resources when we do window fades
[08:30] <seb128> mvo: ^ that's from yesterday
[08:30] <seb128> I think he said he would open a bug
[08:33] <davmor2> mvo: updates seem to be working okay now :)
[08:34] <mvo> thanks seb128 and davmor2
[09:31] <tseliot> seb128: what does Gnome do with DPI (in Jaunty)?
[09:32] <seb128> tseliot: 96 dpi forced
[09:32] <seb128> by default forced, you can change the value in the appearance capplet
[09:32] <tseliot> seb128: with a gconf key in libgnome?
[09:32] <seb128> yes
[09:32] <tseliot> ok, thanks
[09:33] <seb128> you're welcome
[09:33] <seb128> why do you ask? do you have any issue due to that?
[09:38] <asac> hmm ... i experienced issues shutting down my system (using fusa) ... told me that other users are logged in. known bug?
=== dpm_ is now known as dpm
[09:50] <tseliot> seb128: no, I don't but the OEM team needs some customisations
[09:51] <seb128> tseliot: ok, easier way is to unset the key then, but be careful the xrand capplet might still force a 96dpi value when loading configs
[09:51] <seb128> asac: ck-list-sessions?
[09:51] <tseliot> seb128: how come?
[09:51] <seb128> asac: the ck-pam-something might open a ck session for cron job, there is a bug open about that
[09:52] <seb128> tseliot: bug? I know they use to force 96dpi in hardy when the capplet landed rather than reading the key, I didn't try recently though
[09:54] <tseliot> seb128: any hints as to where I should look at to force DPI as they used to do in Hardy? libgnome?
[09:54] <seb128> tseliot: changing the gconf key will change the default value, ie what gnome-settings-daemon apply
[09:57] <chrisccoulson> asac - bug 287715
[09:57] <ubottu> Launchpad bug 287715 in consolekit "Trying to shut down or restart falsely suggests others are logged in" [Medium,Triaged] https://launchpad.net/bugs/287715
[09:59] <asac> chrisccoulson: cool.
[09:59] <seb128> tseliot:
[09:59] <seb128> gnome-rr-config.c:     * dpi 96.
[09:59] <seb128> gnome-rr-config.c:    width_mm = (width / 96.0) * 25.4 + 0.5;
[09:59] <seb128> gnome-rr-config.c:    height_mm = (height / 96.0) * 25.4 + 0.5;
[10:00] <seb128> tseliot: that's the revelant xrandr capplet code I think
[10:00] <tseliot> seb128: great, thanks, this what I was looking for :-)
[10:51] <Keybuk> seb128: didn't the gnome keyring issue get fixed yet?
[10:55] <seb128> Keybuk: which one?
[10:56] <Keybuk> seb128: I have no gnome keyring
[10:56] <Keybuk> System -> Preferences -> Encryption and Keyrings
[10:56] <Keybuk> "A supported PGP passphrase caching agent is not running"
[10:57] <seb128> the gpg agent is seahorse
[10:57] <seb128> do you have seahorse-plugins installed?
[10:57] <Keybuk> yes
[10:57] <Keybuk> seahorse-plugins	2.26.1-0ubuntu1
[10:58] <seb128> Keybuk: let me try something
[10:59] <Keybuk> I have a ~/.gnupg/gpg-agent-info-quest file
[10:59] <seb128> Keybuk: do you have gnupg-agent installed?
[10:59] <Keybuk> that contains GPG_AGENT_INFO=/tmp/gpg-*/S.gpg-agent:*
[10:59] <seb128> if you do uninstall it and restart your session
[11:00] <Keybuk> ah, yes, I do have gpg-agent installed
[11:00] <seb128> it hijacks seahorse
[11:00] <Ampelbein> seb128, Keybuk bug 183514
[11:00] <Keybuk> it's a recommend of gnupg
[11:00] <ubottu> Launchpad bug 183514 in seahorse-plugins "seahorse-agent stops responding when started with gpg-agent" [High,Triaged] https://launchpad.net/bugs/183514
[11:03] <Keybuk> seb128: should that Recommends be demoted to a Suggests?
[11:04] <seb128> Keybuk: I'm not sure, it might be useful in non GNOME cases, maybe ask on #ubuntu-devel for opinions
[11:04] <huats> hello everyone !
[11:04] <huats> hi seb128
[11:04] <seb128> perhaps it could be a gnupg-agent | seahorse or something so it doesn't get installed in default ubuntu
[11:04] <seb128> lut huats
[11:05]  * Tm_T have noticed that seahorse is happily destroying all gpg settings
[11:07] <Tm_T> and that is while I don't use seahorse at all, just have it installed (:
[11:08] <seb128> you should be using it if you have it installed ;-)
[11:09] <Tm_T> seb128: well, that would mean I have to recreate all my gpg settings and keys and...
[11:09] <Tm_T> I don't see any reason why I should use it, though, so I keep holding it away from my systems
[11:09] <seb128> I don't use gpg enough to have an opinion
[11:10] <seb128> I'm just signing emails and packages to upload
[11:10] <seb128> and I didn't have to reconfigure anything
[11:10] <Tm_T> same here, mostly, but also svn
[11:10] <Tm_T> and ssh
[11:10] <seb128> seahorse found my gpp key automagically and acts as a gpg agent correctly
[11:10] <Tm_T> actually ssh (and svn with it)
[11:10] <seb128> dunno why you think you would have to reconfigure your gpg configuration
[11:11] <seb128> ssh is managed by gnome-keyring not seahorse
[11:11] <Tm_T> seb128: seahorse had all empty
[11:11] <seb128> and there again it uses the system config
[11:11] <Tm_T> seb128: I don't use gnome (:)
[11:11] <seb128> you don't have to configure anything, it just lists available keys automatically
[11:11] <Tm_T> seb128: but it didn't do that
[11:12] <seb128> you should have opened a bug then describing the issue
[11:12] <Tm_T> all what it did, was emptied my .gnupg/ dir
[11:12] <seb128> it deleted your private key?!
[11:12] <Tm_T> seb128: yes, all of it
[11:12] <seb128> weird
[11:12] <Tm_T> indeed
[11:12] <seb128> first time I read about a such issue
[11:12] <seb128> and most of the distro team is using it
[11:12] <seb128> there is no reason it would delete any key
[11:13] <seb128> I guess it's something else on your install but your blamed it on seahorse
[11:13] <Tm_T> seb128: also I had many times issues with gnome stuff forcing themselves to be autolaunched in my KDE sessions after install
[11:13] <seb128> autostart is a freedesktop spec
[11:13] <seb128> those are not GNOME specific
[11:13] <Tm_T> seb128: I know, but forcing to autolaunch metacity...
[11:13] <seb128> nothing force anything
[11:14] <seb128> again if you have a specific issue you should open a bug
[11:14] <seb128> some desktops might need an NotShowIn=KDE
[11:14] <seb128> but we don't use KDE so we will not notice
[11:14] <Tm_T> aye, I have to see if it reoccurs
[11:14] <seb128> if you don't open a bug you get what you deserve
[11:14] <Tm_T> as I have broken hardware now so cannot really try to find and report bugs
[11:15] <seb128> ok, so you will keep getting GNOME things started on your KDE session
[11:16] <Tm_T> did yes, until I manually cleaned that stuff from those autorun dirs
[11:16] <Tm_T> these funny and weird issues occured ~6 months ago I think
[11:17] <Tm_T> I assume that I had installed some -default-settings type package that did something unexpected back then
[11:18] <Tm_T> ok, baby woke, will harrass you later (;)
[11:43] <chrisccoulson> downgrading packages is not really supported is it?
[11:44] <jpds> !downgrade
[11:44] <ubottu> Attempting to downgrade to an older Ubuntu version is explicitly not supported, and may break your system.
[11:45] <chrisccoulson> i was referring about downgrading individual packages, but i think that is not really supported by the package manager anyway
[11:45] <chrisccoulson> the only reason i ask is becuase someone opened a bug against brasero because it failed to downgrade from 0.9.1 to 0.8.2. It fails because the package was split between these 2 versions, and there are no conflicts/replaces to handle the downgrade
[11:46] <chrisccoulson> i was just wondering whether to close it
[11:48] <seb128> yes, close it as invalid, downgrade are not supposed to be working
[11:50] <chrisccoulson> thanks seb128 - done
[12:17] <pochu> seb128: thanks for libproxy sponsorship
=== seb128_ is now known as seb128
=== bittin` is now known as bittin^`
[14:24] <Laney> is 2.26.1 finished?
[14:27] <seb128> Laney: sort of, jaunty is frozen so any other update will have to be a sru after jaunty stable next week
[14:27] <Laney> frozen for rc?
[14:28] <seb128> Laney: yes, and between rc and stable we will get only selected bug fixes not new versions
[14:28] <didrocks> seb128: as it's not in the repos yet, I will make people work on gnome-terminal for tomorrow's lesson :)
[14:28] <Laney> got it
[14:29] <Laney> didrocks: And the prize is getting it uploaded? :)
[14:29] <didrocks> Laney: hum, well, I already prepared it, so, no :p
[14:29] <Laney> :(
[14:29] <seb128> didrocks: k
[14:30] <didrocks> Laney: but it's a good candidate: https://bugs.edge.launchpad.net/ubuntu/+source/gnome-terminal/+bug/361053
[14:30] <ubottu> Launchpad bug 361053 in gnome-terminal "Please, sponsor gnome-terminal 2.26.1 to jaunty" [Wishlist,Triaged]
[14:30] <didrocks> you have b-d bumps
[14:30] <didrocks> not applying patches
[14:30] <didrocks> and autotool use :)
[14:31] <didrocks> so, I hope people can learn some stuff from this :-)
[14:31] <Laney> all in 15 mins? :O
=== rickspencer3 is now known as rickspencer3-afk
[14:50] <didrocks> Laney: I think the 15 minutes goal is just a dream :)
=== rickspencer3-afk is now known as rickspencer3
[15:29] <superm1> mvo, ping. i was talking to seb128 about a zenity focus bug yesterday, and he advised I speak with you about it. bug 272083
[15:29] <ubottu> Launchpad bug 272083 in mythbuntu "Zenity windows appear underneath others" [High,Confirmed] https://launchpad.net/bugs/272083
[15:29] <superm1> we (mythbuntu) didn't catch it recently late due to xfwm4 not doing focus right until recently, so we were attributing the "new" focus problem to xfwm4
[15:35] <mvo> superm1: hello. give me a minute, I check it out when I'm finished with my current task
[15:36] <superm1> mvo, hi, sure, please treat the ping as asynchronous, i didn't mean to detract you from something else :)
[15:37] <mvo> superm1: thanks :) np
[18:06]  * kenvandine_wk heads out for lunch... bbiab
[18:37] <rickspencer3> vuntz: hi!
[18:37] <rickspencer3> :)
[18:40] <vuntz> rickspencer3: doh, you spotted me :-)
[18:40] <rickspencer3> lol
[18:55] <l0ser140> somebody knows something about this: i was synchronized evolution using webDAV, I have a login "user@domain.com", but evolution cut off all after @. remains only "user"? need help)
[18:59] <dobey> l0ser140: #ubuntu would be a better place to ask... this isn't a support channel
[19:00] <l0ser140> but what it deals with? xD
[19:01] <dobey> this is a development channel
[19:01] <l0ser140> ok, thx)
=== mpt_ is now known as mpt
=== geser__ is now known as geser
[19:39] <rickspencer3> bryce: so far Option "EXAOptimizeMigration" "off" seems to be working well
[19:50] <kenvandine_wk> rickspencer3: is that the 2d performance tweak?
[19:54] <rickspencer3> kenvandine_wk: it's a suggested option to replace MigrationHeuristic "greedy"
[19:55] <kenvandine_wk> ah
[19:55] <rickspencer3> if you have intel graphics and aren't too happy with the perf, you could test it out
[19:55] <kenvandine_wk> i am very happy with the performance with UXA :)
[19:56] <rickspencer3> UXA is not crashy for you?
[19:56] <kenvandine_wk> rock solid
[19:56] <kenvandine_wk> without it... it sucks..
[19:56] <rickspencer3> In any case, it would probably help out to test EXA
[19:56] <kenvandine_wk> i will
[19:57] <rickspencer3> a comparison would help
[19:57] <kenvandine_wk> after i finish a few install tests... can't kill X with these VMs running
=== rickspencer3 is now known as rickspencer3-afk
[19:57] <rickspencer3-afk> heh
[20:06] <bryce> rickspencer3-afk: \o/
[20:09] <rickspencer3-afk> bryce: in general, it seems that compiz "slows down" as I use the computer
[20:09] <rickspencer3-afk> so I'll let you know in a  few hours
[20:09] <bryce> ok
[20:09] <rickspencer3-afk> cover flow is my "test case" :)
[20:09] <bryce> I've also asked slangasek to re-test, since he's the one that saw the flaw with greedy
[20:10] <bryce> btw, I have a very strong lead on the freeze issue now too (testing it presently...)
[20:10] <rickspencer3-afk> !
[20:11] <bryce> heh, unfortunately, with latest updates now networkmanager is losing its mind
[20:17] <kenvandine_wk> i need to kill pidgin for a bit.. taking up way to much ram :)
[20:49] <kenvandine_wk> rickspencer3-afk: did you test UNR on your netbook?
[20:57] <chrisccoulson> i'm noticing some really odd nautilus behaviour here :/
[21:15] <seb128> chrisccoulson: which one?
[21:16] <chrisccoulson> hi seb128. if i have nautilus in icon view, and then zoom in at greater than 100%, i see a lot of white space in the right hand-side of the window, causing the horizontal scroll bar to appear
[21:17] <seb128> which scrollbar?
[21:17] <seb128> chrisccoulson: similar to http://bugzilla.gnome.org/show_bug.cgi?id=460044
[21:17] <seb128> ?
[21:18] <chrisccoulson> the horizontal one at the bottom of the window. it seems to appear for no reason
[21:18] <ubottu> Gnome bug 460044 in GtkIconView "A way to space out the columns evenly" [Normal,Unconfirmed]
[21:18] <seb128> look at the first screenshot
[21:18] <chrisccoulson> that's quite possibly related, but in this case, nautilus shows the scrollbar
[21:19] <seb128> are you sure there is not a colum on the left which is not on screen?
[21:20] <seb128> I get a scrollbar here but I also get a column not on screen
[21:20] <seb128> but that's buggy indeed, you have lot of spacing on the right which is not useful
[21:21] <chrisccoulson> there doesn't appear to be any other columns. is there anywhere decent i can upload a screenshot too? it might be easier for me to explain that way
[21:21] <chrisccoulson> this seems to have only started in the last day or so
[21:21] <seb128> try downgrading gtk maybe and see if that's still an issue
[21:22] <chrisccoulson> thanks, i'll try that shortly
[21:22] <seb128> or nautilus
[21:22] <seb128> "* Fix icon view RTL layout in compact view" is in the new version
[21:22] <seb128> which means layout changes, could have some side effects
[21:28] <chrisccoulson> seb128 - the behaviour breaks between nautilus 2.26.1 and 2.26.2
[21:28] <chrisccoulson> doesn't seem to be gtk related
[21:28] <chrisccoulson> i'll open a bug report on the bugzilla
[21:29] <seb128> right, what I wrote just before
[21:29] <chrisccoulson> yeah, it seems like that
[21:29] <chrisccoulson> thanks:)
[21:29] <pitti> good night everyone
[21:30] <seb128> 'night pitti
[21:30] <chrisccoulson> good night pitti
[21:30] <kenvandine_wk> night!
[21:32] <seb128> chrisccoulson: you can try undoing the most recent change on http://svn.gnome.org/viewvc/nautilus/trunk/libnautilus-private/nautilus-icon-container.c
[21:32] <seb128> chrisccoulson: when you have a bug open give me the number I will try to ping alex about it tomorrow
[21:33] <chrisccoulson> thanks, i'll do that
[21:33] <seb128> in fact there is several recent commits
[21:33] <chrisccoulson> i'll try and narrow it down this evening if i get the chance
[21:39] <chrisccoulson> seb128 - gnome bug 579086 for the nautilus issue
[21:39] <ubottu> Gnome bug 579086 in Views: Icon View "Excessive white-space on right-hand side in icon view since 2.26.2 upgrade" [Normal,Unconfirmed] http://bugzilla.gnome.org/show_bug.cgi?id=579086
[21:39] <seb128> chrisccoulson: thanks
[21:40] <chrisccoulson> i'll try and spend some time isolating the commit that broke it shortly, but i need to get my stuff ready for work first
[21:45] <seb128> chrisccoulson: no hurry, you might want to wait tomorrow to see if alex see the issue directly or need extra infos
[21:45] <chrisccoulson> yeah, i don't mind doing that
=== rickspencer3-afk is now known as rickspencer3
[22:14] <rickspencer3> kenvandine: I run UNR, but I use desktop mode
[22:17] <james_w> chrisccoulson: "Low" for that policykit-gnome bug seems almost generous :-)
[22:17] <chrisccoulson> heh ;)
[22:17] <chrisccoulson> we need a "very low" ;)
[22:18] <chrisccoulson> i just had a look at some other policykit-gnome bugs
[22:18] <chrisccoulson> one of them is actually a common gnome-panel bug that keeps confusing people
[22:18] <kenvandine> rickspencer3: unr RC won't install on my classmate, but the beta is fine
[22:18]  * kenvandine filed a bug
[22:18] <rickspencer3> hmm
[22:19] <james_w> chrisccoulson: is that the one that I was triaging the other day?
[22:19] <rickspencer3> kenvandine: I haven't installed it since alpha 5
[22:19] <chrisccoulson> about the "Set System Time" button doing nothing?
[22:19] <chrisccoulson> that's a confusing gnome-panel issue
[22:20] <james_w> chrisccoulson: yeah, right at the end I found those bugs and realised it was probably that, but Mike didn't confirm
[22:21] <chrisccoulson> it seems most likely the same bug, so I just marked it as a duplicate
[22:21] <seb128> the "set" button should probably be next to the combo and not close the dialog
[22:21] <seb128> combo -> spin buttons
[22:22] <chrisccoulson> seb128 - that might make more sense
[22:24] <chrisccoulson> seb128 - the current situation is a bit inconsistent. If I open time-admin, I need to be in the admin group to set the time. But any user can do it via the panel. It seems that the policy is different for the 2 separate actions
[22:25] <seb128> would not be a surprise since they are 2 different softwares
[22:26] <james_w> yeah, there's a bug on gnome-panel saying it should be one of "auth_admin*"
[22:27] <seb128> that could make sense
[22:56] <chrisccoulson> is there any easy way of working out what symbols i'm missing in gdb?
[23:03] <seb128> use apport-retrace if that's a crash? ;-)
[23:04] <seb128> or look at the address and the process mapping to see what library matches it
[23:06] <chrisccoulson> apport's not possible here. it's an abort i'm trying to debug. i'll have a look at the addresses and process mapping though
[23:07] <chrisccoulson> i'm actually trying to debug a g_critical message in file-roller. I'm running it with G_DEBUG=fatal_criticals to make it abort so I can see where it comes from. is that the best way of doing that?
[23:08] <seb128> yes
=== asac_ is now known as asac