[07:50] <didrocks> hi mvo :)
[07:50] <mvo> hi didrocks
[09:03] <crevette> hello
[09:04] <didrocks> lut crevette
[09:05] <crevette> salut didrocks
[10:23] <didrocks> hi seb128 & huats
[10:24] <huats> hey seb128
[10:24] <didrocks> seb128: python-gnome and python-gnome-desktop are ready (bug #327938 and bug #327933)
[10:34] <seb128> lut didrocks huats
[10:34] <seb128> didrocks: ok thanks
[10:35] <didrocks> seb128: you're welcome :)
[11:16] <geser> could someone please look (or even better sponsor) bug 317344 as this blocks the transition of tomboy and f-spot to the new gnome-sharp2 package names?
[11:18] <huats> pochu: do you remember why you enabled the test-suite on gnome-keyring in debian ?
[11:24] <pochu> huats: because test suites are good
[11:24] <huats> pochu: sure but any other reason ?
[11:25] <seb128> you guys are speaking about gnome-keyring?
[11:25] <huats> because in the latest release, it fails to build if you enable them (because it sets -Werrors)
[11:25] <huats> seb128: yep
[11:25] <pochu> huats: in what arches?
[11:25] <seb128> well, that's building the test tools to neither install or run those
[11:25] <huats> seb128: I was asking pochu if there was any reason why he enable the test-suite
[11:26] <pochu> huats: and since what release?
[11:26] <seb128> so what is the interest?
[11:26] <seb128> you don't run those during the build
[11:26] <pochu> seb128: isn't it a test suite?
[11:26] <seb128> and you don't install those
[11:26] <seb128> right, but you need to run make run if you want to run it
[11:26] <seb128> and you don't do it
[11:26] <pochu> oh
[11:26] <seb128> and you don't ship the tools either
[11:26] <seb128> so I fail to see the interest
[11:26] <pochu> you're right then
[11:27] <tjaalton> seb128: I've got a request for gnome-menus; what about moving <DefaultMergeDirs/> to the end of {applications,settings}.menu, so that people can override the values by adding files in *-merged/
[11:27] <pochu> clearly what I wanted to do was to run the test suite... but I failed it seems ;)
[11:27] <huats> pochu: it was added (the set -Werrors) between the  the 2.25.4.1 dans the 2.25.5 I think
[11:27] <seb128> tjaalton: who made that request?
[11:27] <tjaalton> seb128: me :)
[11:27] <pochu> huats: ah ok
[11:27] <seb128> tjaalton: I've an air of dejavu
[11:27] <pochu> huats: so feel free to disable it... it seems my change was pointless :(
[11:28] <huats> pochu: and it fails on the architectures that are not present on ppa :) (otherwise we could test them more easily)
[11:28] <huats> pochu: already did :)
[11:28] <seb128> tjaalton: let me find the bug for you
[11:28] <tjaalton> seb128: ok, so for instance now I can't have a file in merged/ which would remove all KDE entries from the menus (we have to install both desktops)
[11:28] <tjaalton> thanks
[11:28] <seb128> tjaalton: http://bugzilla.gnome.org/show_bug.cgi?id=557443
[11:28] <tjaalton> sigh
[11:29] <pochu> huats: btw, do you have your check-symbols script handy? I'd like to have a look at it :)
[11:29] <huats> sure :)
[11:29] <huats> I will send it to you this afternoon ok ?
[11:29] <seb128> tjaalton: edit the .menu or ship a custom one if you want to do that
[11:29] <tjaalton> seb128: that's exactly what I'm trying to avoid :)
[11:30] <seb128> tjaalton: read the bugs for details and talk to vuntz and try to convince him if you still disagree
[11:30] <tjaalton> seb128: now I just include the file with the excludes, and it works just fine
[11:30] <tjaalton> but I had to add the include to the file
[11:31] <tjaalton> MergeFile that is
[11:31] <tjaalton> anyway, will read
[11:36] <pochu> huats: sure, thanks!
[11:36] <tjaalton> seb128: so the spec sucks :)
[12:08] <andreasn> mpt, ping
[12:15] <asac> seb128: bug 272010 -> please look at totem debdiff and tell me if you want me to push that or do something else on that package for you ;)
[12:21] <asac> anyone here has sun java5/6 plugin installed and can give me a dpkg -L on that?
[12:23] <gnomefreak> asac: http://pastebin.mozilla.org/621196
[12:23] <gnomefreak> its -l not -L
[12:24] <asac> gnomefreak: but i need -L ;)
[12:24] <gnomefreak> but dpkg doesnt like -L
[12:25] <syldeb35> asac: http://pastebin.mozilla.org/621198
[12:26] <asac> syldeb35: hmm ... there is no .so ... where are the alternative links ending?
[12:26] <asac> how is that file called?
[12:28] <didrocks> I have to bind to evince in gnome-python-desktop update: http://paste.ubuntu.com/116783/ but there is no evince-dev or some similar package and it builds successfully without it. Does this mean I have only to add it as a dependency of the binary package?
[12:32] <geser> didrocks: did you checked the build log if it detects evince or not? I guess it checks for evince but as it doesn't find the needed headers it skips it.
[12:33] <didrocks> geser: let me check (and I don't find any package with header for evince, appart from the two libraries that I added libevdocument-dev and libevview-dev)
[12:38] <syldeb35> asac : perhaps this one :dpkg -L sun-java6-bin -->http://pastebin.mozilla.org/621203
[12:38] <syldeb35> the alternative links end to /usr/lib/jvm/java-6-sun/jre/plugin/i386/ns7/libjavaplugin_oji.so
[12:39] <asac> yeah thanks
[12:39] <asac> syldeb35: is that the same filename for sun-java5-bin?
[12:43] <syldeb35> not sur because sun-java5-plugin not installed but I have /usr/lib/jvm/java-1.5.0-sun-1.5.0.17/jre/plugin/i386/ns7/libjavaplugin_oji.so
[12:43] <seb128> didrocks: there is libevdocument and libevview which are evince libraries
[12:43] <syldeb35> and /usr/lib/jvm/java-1.5.0-sun-1.5.0.17/jre/plugin/i386/ns7/libjavaplugin_oji.so
[12:44] <didrocks> seb128: yes, (cf my last sentence :)). I will just try to check the build log first
[12:44] <seb128> asac: the debdiff looks alright please upload
[12:45] <seb128> didrocks: those are the libraries supposed to be used, they did make libraries for a reason
[12:45] <didrocks> seb128: so, gnome-python-desktop will not really depends on evince, but only on those two libraries
[12:45] <seb128> right
[12:45] <asac> seb128: done. thanks
[12:45] <seb128> they made those libs especially for that
[12:45] <seb128> asac: did you push the changes to bzr?
[12:45] <didrocks> seb128: oh right (do you follow a ML to keep up to date with those informations?)
[12:46] <seb128> didrocks: not really, I do read the changes description on the ftp list
[12:46] <asac> seb128: am i part of -desktop?
[12:46] <seb128> ie the NEWS for new tarballs
[12:46] <seb128> asac: dunno, if you are not we can fix that easily ;-)
[12:48] <didrocks> seb128: it's just written "New Evince bindings", not that those 2 lib gives these bindings, but yeah, it's implicite :)
[12:48] <asac> seb128: trying to push ;)
[12:48] <asac> seb128: i think i have no permissions. can you add me?
[12:48] <seb128> asac: sure, one sec
[12:48] <seb128> didrocks: that might have been detailled on a planet.gnome.org blog
[12:49] <seb128> didrocks: and the mention of the split was on the evince side, ie they wrote about new libs allowing embeders
[12:49] <didrocks> seb128: ok. What's strange is that I have no "no evince binding found" in the build log when I don't add them.
[12:50] <didrocks> too late ;)
[12:50] <asac> now seb is gone :)
[12:50] <didrocks> he will be back soon, as usually ^^
[12:51] <asac> yeah. me feels itchy to push the branch and move on ;)
[12:51] <didrocks> asac: :)
[12:51] <didrocks> seb128: ok. What's strange is that I have no "no evince binding found" in the build log when I don't add them.
[12:51] <seb128> asac: added
[12:52]  * asac runs bzr push
[12:52] <seb128> didrocks: maybe the configure is not verbose, are the binding built and in the deb?
[12:52] <asac> ok Pushed up revision 9.
[12:52] <seb128> asac: danke
[12:52] <didrocks> seb128: let me add the b-d first to compare the build log :)
[12:52] <seb128> asac: welcome to ubuntu-desktop too btw ;-)
[12:55] <seb128> doing an another bootchart, brb
[12:55]  * asac feels thrilled
[12:55] <asac> and a warm feeling of new power ;)
[13:04] <didrocks> seb128: yes, it works. It activate a whole bunch of bindings now
[13:04] <seb128> see ;-)
[13:04] <didrocks> seb128: let me push the new branch version
[13:04] <didrocks> (and tag it again)
[13:05] <seb128> you are using tagging now?
[13:05] <didrocks> seb128: yes, since evince update :)
[13:05] <didrocks> I dunno if it's useful, but well
[13:06] <Tm_T> hi asac
[13:14] <didrocks> seb128: it's ok now
[13:24] <seb128> pitti: what command can be called to trigger suspend nowadays?
[13:43] <soren> pm-suspend?
[13:43] <soren> That's what I use.
[14:21] <seb128> mvo_: how busy are you today? ;-)
[14:23] <mvo_> seb128: medium, why? need some sponsoring love?
[14:23] <seb128> mvo_: no, there is a new gnome-control-center version available, I'm looking at it but in case some your patches need to be updated ;-)
[14:24] <mvo_> seb128: hm, I see. if there is trouble please ping me, I will have a look
[14:24] <seb128> mvo_: ok thanks, the proxy thing doesn't apply I'm looking at it
[14:25] <seb128> did I already say how much I dislike glade changes? ;-)
[14:28] <mvo_> you did (and I agree)
[14:28] <geser> mvo_: if you have some time for sponsoring, could you please look and sponsor bug 317344?
[14:29] <mvo_> geser: sure, let me have a look
[14:29] <seb128> mvo_: ok that was an easy one you are off the hook for now ;-)
[14:30] <mvo_> *puffff*
[14:30]  * mvo_ makes a sign of relief :)
[14:30] <seb128> ;-)
[14:30] <seb128> trying gsd update, brb
[14:33] <crevette> wow my karma doubled in the last 2 weeks
[14:33] <crevette> I started low :)
[14:36] <mvo> geser: I have to admit that I don't know that much about c#, is ok that its still "libgnomedesktop2.20-cil" (even though this is now updated to 2.24?
[14:38] <geser> mvo: me neither, I hope that the Debian maintainers know what they do (slomo did the upload to experimental)
[14:38] <mvo> geser: aha, if he did it, then its probably allright :)
[14:39] <crevette> should I ping someone to have universe packaged sponsored? I did 2 bug reports for new versions with universe sponsors subscribed, but I don't news about them
[14:39] <seb128> tseliot: are you there?
[14:39] <mvo> oho, someone else on the hook now ;)
[14:39] <seb128> crevette: no, there is just a lot of items, look on http://daniel.holba.ch/sponsoring/
[14:39] <tseliot> seb128: sure
[14:39] <seb128> mvo: see it's not only you ;-)
[14:40] <seb128> tseliot: you gave me patch updates for some of the g-c-c changes yesterday, did you actually change something to those?
[14:40] <seb128> tseliot: ie 109_screen_resolution_extra.patch applies correctly to 2.25.90
[14:41] <tseliot> seb128: yes, I did changes to them
[14:41] <seb128> same for 110_screen_resolution_package.patch
[14:41] <tseliot> seb128: I think I gave you the right patches, let me check them again
[14:42] <seb128> tseliot: could you summarize the changes so I know why I should use your versions and what to write in the changelog ;-)
[14:42] <seb128> http://albertomilone.com/ubuntu/gnome/jaunty/gcc-patches/110_screen_resolution_package.patch
[14:42] <seb128> http://albertomilone.com/ubuntu/gnome/jaunty/gcc-patches/109_screen_resolution_extra.patch
[14:42] <seb128> http://albertomilone.com/ubuntu/gnome/jaunty/gcc-patches/25_window_manager_settings.patch
[14:43] <seb128> the previous version of those still apply correctly
[14:43] <seb128> I'm not sure what you changed
[14:43] <tseliot> seb128: there were only some small conflicts. The real changes took place in the patches for gnome-desktop
[14:44] <tseliot> seb128: therefore if the old patches compile, simply leave them as they are
[14:44] <seb128> ok
[14:44] <seb128> right the 80_aspect_in_dropdown.patch needed to be updated
[14:44] <seb128> thanks
[14:45] <tseliot> that was relevant to what I do so I thought it would be useful to update it
[14:45] <seb128> indeed that was useful thanks for that one ;-)
[14:45] <tseliot> ;)
[15:24] <lool> seb128: BTW I know now what really made me unhappy about bug-buddy and gnome-dbg
[15:24] <lool> seb128: Something on my system pulled bug-buddy at some point
[15:24] <lool> which pulled gnome-dbg
[15:24] <lool> gnome-dbg and bug-buddy have some circular dependency (one recommends one depends) and wont ever get out of your system
[15:25] <lool> Downgrading the recommends make this loop go away, which is good for my sanity
[15:25] <seb128> ;-)
[15:25] <seb128> I use neither bug-buggy or gnome-dbg so I was not really bothered but I understand your issue ;-)
[15:26] <lool> I guess I could as well drop the bug-buddy depends from gnome-dbg
[15:27] <crevette> what is gnome-dbg ?
[15:27] <lool> a meta package pulling all the *-dbg on Debian
[15:28] <crevette> ah okay, I thought it was kind of debug wrapper scripts that could appears when a crash happens, and offer you to debug it, like in windows :)
[15:28] <seb128> didrocks: is gnome-python-desktop ready to be reviewed?
[15:28] <lool> crevette: Sure, and it would also hand you a patch?   :-)
[15:29] <crevette> lool, we could propose to run nemiver instead of bug-buddy :)
[15:29] <crevette> only for real mens
[15:30] <crevette> lool, I hope you bought the wonderful GNOME tee-shirt at FOSDEM?
[15:31] <maxb> I have Alt+F6 configured to "Run a terminal" as per default, and in compiz it works. In metacity, instead it causes a thick black border to highlight the active window - what is this hilight for, and why is it intercepting the configured keybinding?
[15:32] <lool> crevette: I did
[15:32] <crevette> lool, \./
[15:32] <crevette> are they nice? I choose them, I ordered the print, but I don't know what they look like :)
[15:33] <crevette> s/what/how/
[15:33] <walters> maxb: see /apps/metacity/global_keybindings - by default that's switch_group which switches windows inside a "group" (application, sort of)
[15:34] <maxb> hmm
[15:34] <maxb> I guess I need to file a bug about the UI and actual behaviour disagreeing
[15:34] <asac> seb128: what do you think about bug 217551 ... nm just opens gtk_menu_popup with activate_time
[15:34] <lool> crevette: They are simple and nice
[15:34] <lool> I like the color a lot better than last year's
[15:35] <crevette> don't you like the green ?
[15:35] <crevette> :)
[15:35] <seb128> asac: needs debugging?
[15:35] <crevette> the burgundy looked like cool on the paper
[15:35] <crevette> so I chose that :)
[15:35] <seb128> asac: any reason you don't try to authentificate while the menu is open?
[15:37] <maxb> Where are the keybindings that gnome-keybinding-properties edits stored?
[15:37] <asac> seb128: hmm ... dont think i understand what you mean. from what i understood the keyring dialog is triggered and then all input isnt processed anymore
[15:38] <seb128> asac: to me it seems that the keyring callback get called while the menu is open which creates a keyboard grabbing issue
[15:38] <seb128> asac: usually you open a menu, click on an item, that calls the keyring callback and the menu is closed before you get the dialog
[15:39] <asac> seb128: how does keyring grab keyboard?
[15:40] <asac> gdk_keyboard_grab ;)
[15:41] <seb128> asac: yes
[15:43] <seb128> asac: http://bugzilla.gnome.org/show_bug.cgi?id=554782
[15:43] <seb128> asac: that bug suggests it has been fixed in nm-applet svn some months ago, do you still get the issue on jaunty?
[15:45] <asac> seb128: keyring does no error handling for "grab_keyboard"
[15:46] <seb128> asac: http://svn.gnome.org/viewvc/network-manager-applet?view=revision&revision=1062 ?
[15:47] <asac> seb128: Not fixed in intrepid, not fixed in jaunty. C'mon guys, this is REALLY irritating bug.
[15:47] <asac> seb128: i think it fixed the issue partially
[15:48] <asac> if you reopen the menu before keyring pops up it might reproduce still
[15:48] <seb128> asac: I agree it's an irritating bug
[15:48] <seb128> I'm not sure what the right fix is though
[15:48] <seb128> keyboard grabbing should fail in this case no?
[15:49] <seb128> brb
[15:49] <seb128> trying compiz update
[15:49] <asac> hmm
[15:51]  * seb128 looks to mvo
[15:51] <seb128> mvo: can I get a wm running? danke!
[15:52] <seb128> /usr/bin/compiz.real (core) - Error: Plugin 'core' has ABI version '20090207', expected ABI version '20080828'.
[15:52] <seb128> /usr/bin/compiz.real (ccp) - Error: InitObject failed
[15:52] <seb128> /usr/bin/compiz.real (core) - Error: Couldn't activate plugin 'ccp'
[15:52] <seb128> mvo: you broke my jaunty ;-)
[15:52] <maxb> seb128: Have you got the recent compiz-fusion-plugins-{main,extra} updates? They seemed to take a while to reach the mirrors
[15:53] <maxb> Though clearly there aren't strict enough dependencies
[15:53] <mvo> seb128: did you upgrade everything? hrm hrm
[15:53] <seb128> maxb: that's alright, I know what is broken and why, I'm just teasing mvo because he didn't use breaks correctly ;-)
[15:53] <mvo> but yeah, some dependency strictness is missing
[15:54] <seb128> mvo: no, I did upgrade compiz-gnome
[15:54]  * mvo sighs
[15:54] <mvo> seb128: ha! so you did it on purpose ;) ?
[15:54] <seb128> which triggered compiz-core and compiz-plugins to be upgraded
[15:54] <seb128> mvo: yes, just to show if you did use breaks correctly this time ;-)
[15:54] <seb128> show -> see
[15:55]  * mvo hides under a rock
[15:57] <maxb> The new compiz has also broken a few keyboard shortcuts (bug 328111)
[15:57] <mvo> oh, thanks maxb
[15:57] <mvo> maxb: could you please check if you have the "gnomecompat" plugin enable (it should be default)
[15:57] <maxb> Sure!.. How? :-)
[15:59] <seb128> mvo: bug #327793 has some users which have issues
[15:59] <seb128> mvo: but that seems to be partial upgrades
[15:59] <seb128> restarting session again
[16:00] <mvo> seb128: the broken title bar should be fixed
[16:01] <seb128> mvo: ok, I get 6 workspaces on one line rather than 8 on 2 lines now
[16:01] <seb128> but compiz is running
[16:03] <mvo> seb128: hrm, bad
[16:03] <seb128> let me do an another session restart to make sure that's not transitionnal
[16:05] <seb128> mvo: hum and the gnome-panel taskbar lists all the dialog open, not only the ones on the current workspace as it should
[16:14] <davmor2> bryce: you around yet?
[16:14] <didrocks> seb128: thanks for the sponsoring (when you have some time, there is still gnome-python one)
[16:15] <seb128> didrocks: did you subscribe the sponsor team? it's not listed on
[16:15] <seb128> http://people.ubuntu.com/~dholbach/sponsoring/index.html
[16:16] <didrocks> seb128: yeah, apparently: bug #327933
[16:16] <seb128> it's in the not correctly parsed list, weird
[16:16] <didrocks> I will report a bug to dholbach :)
[16:18] <mvo> seb128: oh, lets talk about it after my meeting
[16:18] <seb128> mvo: it doesn't do it for everything, I'm trying to see what is going on exactly
[16:25] <seb128> mvo: are you running you shiny new compiz version? ;-)
[16:26] <mvo> seb128: no, don't tell me you run this unstable gnome ;) - kidding, yes I do on my workstation
[16:26] <bryce> davmor2: yep
[16:27] <mvo> maxb: please open "ccsm" (from e.g. a terminal) and check it should be in the top row
[16:27] <seb128> mvo: can you try to open evolution on any workspace and see if it's listed on all workspaces?
[16:27] <seb128> mvo: or gnome-screenshot
[16:28] <seb128> mvo: listed in the gnome-panel tasks, not in alt-tab
[16:28] <mvo> seb128: for me it seems to be only in the main one, maybe its viewport<->workspace ocnfusion again :( ?
[16:28] <mvo> and I run a very fresh profile, reseted it the other day
[16:28] <mvo> (the compiz profile)
[16:29] <seb128> I run a recent profile too
[16:29] <seb128> I selected normal in the capplet to restart compiz after the partial broken upgrade
[16:29] <davmor2> bryce: https://bugs.edge.launchpad.net/ubuntu/+source/xserver-xorg-video-nv/+bug/309482 I've added the nv stuff.  Is there an easy way to force vesa use though for the vesa info everytime it reboots it's using nv again
[16:30] <mvo> seb128: lets debug after the meeting/tomorrow, I may need the dump of your profiel settings
[16:32] <seb128> mvo: ok, let me know when you want to debug this
[16:36] <asac> mvo: in the past i saw packages in /var/cache/apt/archives in apt-cache show PACKAGENAME ... thats not the case in jaunty anymore?
[16:36] <asac> s/packages/package-versions/
[16:39] <bryce> heya mvo
[16:40] <bryce> mvo: btw we can drop the blacklisting of Intel Eaglelake from compiz now.
[16:40] <bryce> mvo, (LP: #261080)
[16:41] <bluesmoke> bug 261080
[16:54] <mvo> bryce: done
[16:55] <mvo> asac: hm, what execalty did you see in the past? I have not changed anything here
[16:55] <mvo> asac: I will be away for some minutes, lets talk after
[16:56] <asac> mvo: i think i saw all versions in the cache ... now i see: version in archive + version installed
[16:56] <asac> but no version that is in cache but not installed nor in archive
[16:58] <mvo> asac: I don't think this ever worked, might be conincidence (archive==version-in-cache)
[16:58] <asac> mvo: well. i am quite sure it worked. i used it frequently
[16:59]  * asac confused
[16:59] <asac> of course i believe you ;)
[16:59] <mvo> asac: hm, I can review the bzr logs, but I have currently no idea
[16:59] <asac> you are the man (TM)
[16:59] <mvo> asac: might be really strange side effect or something
[16:59]  * mvo really runs now
[16:59] <mvo> bbl
[17:06] <bryce> mvo: excellent, thanks!
[18:07] <highvoltage> anyone else have a problem in Jaunty where "Launching File Browser" just opens up in a loop in the window list and slows down the machine to a crawl?
[18:24] <dobey> highvoltage: i've seen that happen in intrepid before. could be an extension you have installed, causing problems
[18:25] <highvoltage> dobey: I think it started happening when I installed the netbook-launcher, but it happens even in a safe-mode gnome-session
[18:25] <highvoltage> (when the netbook-launcher isn't started)
[18:25] <dobey> highvoltage: when it happened to me, it was a python-based nautilus extension i was playing with, causing nautilus to "crash" and the session kept restarting it
[18:30] <maxb> mvo: ccsm showed the gnomecompat plugin not selected. ticking it restored Alt+F1 and Alt+F2, but not Alt+F6. However, there's a further problem with handling these as a compiz plugin - it means the settings in gnome-keybinding-properties are not respected
[18:30]  * maxb goes to say the same in the bug
[19:00] <crevette> wow a lot of -dbg pulled in the lastest update
[19:04] <maxb> Yeah, I think that isn't sane
[19:04] <maxb> bug-buddy is the source of the Recommends that pulls it all, AFAIK
[19:05] <pochu> well, you shouldn't need bug-buddy in Ubuntu ;)
[19:06] <maxb> But I didn't install it manually
[19:06] <maxb> It may be that update-manager needs to consider removing bug-buddy rather than pulling in all that lot
[19:34] <benc> do I need to install or configure a firewall on ubuntu desktop?
[19:36] <BugMaN> benc: read this -> https://help.ubuntu.com/8.10/keeping-safe/C/firewall.html
[19:37] <benc> thanks. is it recommended or unnecesary?
[19:38] <BugMaN> benc: not necessary like in a windows environment
[19:39] <benc> BugMaN: I'm developing  web applications so I guess I should setup a firewall. thanks
[19:40] <BugMaN> benc: ok in this case is better to install a firewall
[19:40] <benc> thanks
[20:26] <mvo> maxb: thanks for this update, I check it out (tomorrow)
[20:29] <asac> since today my window decorations are white :/
[20:29] <asac> maybe uxa
[20:29] <asac> let me test
[20:32] <asac> hmm ... that wasnt the problem
[20:47] <bryce> asac: is this with the new 6.10.99 -ati?
[20:48] <asac> bryce: no thats on my thinkpad with i965
[20:48] <asac> i am currently upgrading in the hope that its gone :)
[20:49] <bryce> ok
[20:49] <bryce> duh right, uxa == intel
[20:49] <asac> bryce: http://people.ubuntu.com/~asac/tmp/screen_white.png
[20:50] <asac> but its not accellmethod
[20:50] <bryce> weird.  compiz maybe?
[20:52] <bryce> compiz (1:0.7.9+git20090211-0ubuntu1) was uploaded yesterday, that'd be my first guess
[20:53] <bryce> if you still have earlier compiz debs in your /var/cache/apt/archives/ maybe try reverting?
[20:53] <asac> bryce: ok. it was a temporary issue as it seems
[20:54] <asac> last update made it go away \o/
[20:54] <asac> how colorful a desktop can be ... impressive ;)
[20:54] <asac> for a moment i thought it was an experient from dx team ;)
[20:55] <asac> experiment
[20:58] <bryce> hehe
[22:34] <Amaranth> asac, bryce: Downgrade metacity, not compiz
[22:34] <Amaranth> libmetacity-private changed
[22:34] <Amaranth> The fix should be in compiz git at this point, gotta check on that
[22:35] <Amaranth> Problem was we were creating an RGBA colormap the "old-fashioned" way since when that code was written the way libmetacity wants it done didn't exist
[22:35] <asac> Amaranth: for me its fixed already
[22:35] <Amaranth> ah, mvo is quick :)
[22:38] <Amaranth> yay a git snapshot even
[22:38] <Amaranth> that means wall viewport changing should look a lot cooler
[22:51] <bryce> sweetness.  dual head at 3840 x 1200, and compiz is working (and nice performance).
[22:51] <maxb> asac's grey titlebar issue should be fixed with latest compiz and metacity in the archive
[22:52] <bryce> on RV535/X1650
[22:52] <bryce> I'm stunned, I've not had both dual-head and compiz like this before.  very nice
[22:53]  * bryce wobbles windows across two monitors
[22:53] <dobey> bryce: i wonder how well it works at 4096x1152 :)
[22:55] <bryce> hmm, only issue so far is when I first enabled compiz, it moved all my gnome-terminal windows to 0x0
[23:16] <bryce> Amaranth: hey, have you played with the cube and dual-head displays?
[23:16] <Amaranth> bryce: not in a _long_ time
[23:17] <bryce> basically it seems to give me two cubes, one for each screen
[23:17] <bryce> with each screen being an adjacent face on the cube
[23:17] <bryce> which... works... but doesn't feel right
[23:17]  * bryce shrugs