[00:04] kenvandine: seahorse 3.4 is working great here now [00:12] /cr/c [01:18] robert_ancell: hey [01:18] got your email, starting to fix this up now [01:33] cyphermox, ta [01:40] robert_ancell: uploaded, building now [01:40] I'll look at gnome-phone-manager tomorrow ;) [01:41] * cyphermox signs off, attempts signing in to D3 :P === jalcine is now known as Jacky [02:18] Grrrr. [02:18] gnome-keyring-daemon changing its interface out from under the libraries is annoying. [02:39] RAOF: YOu mean things like the ssh agent no longer working kinda change? [02:40] oh fun. i bet it breaks ubuntu-sso-client again too [02:42] TheMuso: Correct. [02:43] Yeah, fun times. [02:43] TheMuso: And all my launchpadlib stuff not being able to find my credentials. And evolution not finding my credentials, and seahorse showing a very odd view of my passwords. [02:43] oh ouch. [02:44] RAOF: oh you don't like the new seahorse? [02:44] jbicha: I'd prefer a seahorse that works :) [02:45] seahorse works here... [02:47] Am I the victim of mirror skew? What seahorse version are you talking about? [02:49] seahorse 3.4.1-1; it's a major redesign [02:50] * TheMuso sees a gnome-keyring update after syncing his local mirror. [02:50] * RAOF adds archive.ubuntu.com to sources.list [02:51] ah, yeah, gnome-keyring, seahorse, & gcr needed to be updated at the same time [02:52] Ah yes! New gnome-keyring sees ssh agent working again. [03:03] Oh, wow. They really have changed seahorse, haven't they. [04:02] grrr something mucks up metacity settings at every reboot for my session. I have to delete the metacity gconf settings files to restore proper behavior. [04:05] Would it be too much to ask for GNOME stable releases to really only fix bugs and not change behaviour? [04:06] THis is in quantal... [04:08] * RAOF is processing the SRU queue [04:09] ah ok. [04:09] I knew that, but was not sure if you were talking about my comment. [04:10] But stable GNOME updates changing behaviour has happened before afaik. [04:10] I don't know how it was dealt with though. [04:21] Laney: You're not core-dev?! [08:51] RAOF: Indeed. I got the cli-mono packageset which meant that I could upload everything I needed to touch often in main. [08:51] Fair enough. [08:51] However that is probably changing :P [08:52] RAOF: he knows how the DMB works and avoids to start his core-dev application :) [08:53] actually I did start it the other day [08:53] you might be able to guess the URL [08:53] oh [08:54] I still have a healthy fear of the DMB though … === chaoticuk_ is now known as chaoticuk [13:31] hmmm, now to break firefox in quantal! [13:33] Go ahead...I'm using Chromium ;-) [13:36] i am more than happy to break that too [13:36] well, perhaps if i cared about it ;) [13:43] Ghehe, go ahead ;-) I've got still more back-up browsers =P [13:43] Not the most sophisticated, but "workable" ^_^ [13:46] http://lifehacker.com/5911058/the-avengers-desktop [13:46] Note: UBUNTU desktop [13:47] heh, whenever people do that sort of stuff, it always looks good until they start actually running applications that do more than background status monitoring :) [13:48] well, s/good/cool/ === tkamppeter_ is now known as tkamppeter [15:01] now that folks 0.6.9-1 is in ubuntu quantal, there is a fix in there that should make it into Precise. Do I cheery pick that fix and patch folks in precise and add an -ubuntu1 to it ? [15:01] cherry* [15:02] yeah, that works [15:02] mdeslaur, thanks for the sync btw :) [15:02] as long as precise < precise-proposed <= quantal [15:02] bcurtiswx: -2ubuntu0.1 [15:02] bcurtiswx: np [15:05] geser, the quantal version is 0.6.9-1 i'm not understanding why that goes to -2 [15:05] in precise [15:05] the precise version is -2 [15:05] so -2ubuntusomething [15:05] 0.1 or 1 are both fine [15:06] bcurtiswx: precise has 0.6.8-2 and the usual next version for a SRU would be 0.6.8-2ubuntu0.1 [15:07] or you could use 0.6.9-1~precise1 if you're just backporting from Debian/quantal [15:07] geser, ah yes. I was staring at my rmadison and.. lets just say these pain killers may be working REALLY well :) [15:08] mornin' kenvandine [15:08] good morning [15:10] ok im trying to pull lp:ubuntu/precise/folks but maybe since it was a sync thats not right because I received an error [15:11] well branch would be the right term [15:14] that branch is the right one === marrusl_ is now known as marrusl [15:35] bcurtiswx, i am on it :) [15:35] bcurtiswx, give me 5 minutes [15:48] kenvandine, im in no rush. I'm trying to do some data manupilation on lots of datasets which are each a half GB in size :) [17:17] w00t, closed my first WI :-) [17:18] so,i've nearly closed as many as last cycle already! [17:46] chrisccoulson, adding a WI of "Fix typo in next WI" and subsequently closing it, doesn't count.. :P === charles_ is now known as charles [18:30] kenvandine, in empathy does edit->preferences still have a checkbox that says "automatically connect on startup" in precise? (I'm at work on an older release) [18:35] bcurtiswx, yes [18:35] thx === skaet_ is now known as skaet === kirkland` is now known as kirkland [19:57] gah, ffs [20:02] chrisccoulson: can you disable thumb2 on armel while you're at it? (or I can do it over the weekend otherwise) [20:02] micahg, i disabled it last week [20:02] oh, hrm [20:03] I guess I'll have to dig at some point this cycle (shouldn't matter for older releases, so no rush) [20:03] http://bazaar.launchpad.net/~mozillateam/firefox/firefox-trunk.head/revision/1217 [20:05] chrisccoulson: right, I thought I saw that :), still seems to be unhappy, so probably just needs a patch somewhere, no rush though [22:18] anyone here want to help me triage an apparent gdk problem, so that I may file a more intelligent bug report than "mouse gets stuck"? :) I guess I'll just explain, and then you can tell me to go to #ubuntu if asking here isn't appropriate.. [22:19] so, since my 12.04 upgrade, at least a couple times a day, I'll get into this mode where the window I'm using seems to grab the focus, and won't let go. I.e. I can move around the desktop, but I can't select or type into any other window. [22:20] whenever I click on another window, I get an entry in ~/.xsession-errors saying "Gdk-CRITICAL**: IA__gdk_window_get_events: assertion 'GDK_IS_WINDOW (window)' failed" [22:21] then two following "g_object_ref" and "g_object_unref" G_IS_OBJECT failed assertions, presumably from the same presumed object. [22:22] what component/package do I file this against? [22:23] jbrett, if you run the particular application with G_DEBUG=fatal_criticals, that will make the application abort on those error messages [22:23] then you can get a stacktrace [22:23] (as described https://wiki.ubuntu.com/Backtrace) [22:24] hmm, ok. I never know which application it's going to be, but I guess I can just run the whole desktop with that variable. [22:25] i.e. it's not application specific. This time, it happened to occur while I was in xchat, so I can type this :) [22:25] sometimes it's chrome, sometimes it's gnome-terminal, etc... [22:34] jbrett, sounds more like a compiz or unity bug then tbh ;) [22:34] i thought it was just an issue with a specific application [22:34] but if not, then that's more difficult ;) [22:34] yeah was going to say sounds like a window manager issue [22:34] jbrett, tried it with unity2d or gnome fallback? [22:34] yeah, it's not specific to compiz or unity though. I tried killing unity/compiz and running metacity --replace, and the same thing happens in metacity after a few minutes. [22:35] jbrett, how do you normally recover it? [22:35] so it's some underlying library thing, I guess, I just don't have a clue which library to start with. [22:35] I reboot :) [22:36] I'm tempted to blame the nvidia driver. [22:36] jbrett, have you checked if there are any suspicious errors in dmesg? [22:36] yes, nothing in dmesg or syslog. [22:36] :( [22:36] that sucks [22:36] the only place I can find any errors that make sense is in ~/.xsession-errors. [22:36] i'm not sure what else to suggest. that's not really my area of expertise [22:36] perhaps bryceh has some more ideas :) [22:37] well, xorg would be my next idea ;-) [22:37] so yeah, feel free to `ubuntu-bug xorg`, and if it's not xorg it can be moved from there [22:38] ok, I'll do that and see where it goes :) [22:38] thanks [22:38] jbrett, I hope it's not the nvidia driver though; that's obviously rather hard to fix... [22:38] no kidding. [22:38] if you do suspect -nvidia, try purging it and booting with just -nouveau [22:38] unfortunately, nouveau won't even recognize my card. [22:39] I'm running the identical config on another machine with nouveau, and don't see this problem, that's why I'm suspicious. [22:39] yep, well so much for that idea :-) [22:40] "identical config" means a 12.04 install with rsync'd /home -- obviously not completely identical, and different hardware.. [22:46] well, it's not an issue we've had many reports on (that I know of), and if it was a widespread bug I'm sure people would be reporting it; sounds pretty annoying. So it's likely something peculiar either with your hardware or your install (or just a really obscure bug) [22:51] yeah, I spent quite a while trying to figure out what was messed up with my config -- that's why I duplicated it on another machine. [22:51] but something could obviously be mucked up with the install/upgrade. [22:57] jbrett, yeah took a look thru all the nvidia reports we got for precise; none about mouse focus