[03:25] so, for discussion on Ubuntu GNOME 13.10, should I just use #ubuntu+1 ? [04:26] no, development is focused on saucy in here, so this channel is fine [04:31] bjsnider, cool [04:32] didn't know about Ubuntu GNOME until 13.04 was released, and man, gotta say, Gnome 3.8 is pretty cool [04:33] strangely enough, I haven't run into a bug yet in 6 hours of using the machine as I usually would. XD well, aside from the issue that fglrx 13.8 needs extra patches to work properly with the 3.11 kernel. [04:33] the fglrx issue is fixed with a set of patched packages from xorg edgers (whose ppa I borked my system with many times in the past. XD) [04:35] doesn't radeon work better than fglrx? [04:36] unfortunately this is not the best hardware to have on linux [04:37] bjsnider, not for my Radeon HD 6670, there's a noticeable performance hit. [04:38] it isn't. but I don't have the money currently to buy a new GPU. [04:39] if your board has an onboard intel chip it might be better [05:18] bjsnider, I wasn't that lucky with this PC, onboard Radeon 3000 [05:18] my laptop, though, has a muxless Intel/Radeon pair, [05:18] decent laptop, might I add. [22:58] jbicha, hi [22:59] can you upload the g-c-c update for seperate backgrounds? [23:06] darkxst: I stumbled across a bug with that feature [23:06] jbicha, what is the bug? [23:06] if you change the lockscreen backend and immediately lock the screen, it's possible for the lockscreen to be white instead of the picture it's supposed to be [23:07] it felt a little harder to trigger that bug with g-s-d 3.8 so I was thinking about holding off on the g-c-c update until we get approval for g-s-d [23:08] if someone hits that bug, things clear up after logging out and logging back in; it's just a temporary glitch [23:11] jbicha, backgrounds are not done by g-s-d anymore, however g-s-d from the archives is still loading the background plugin [23:11] that said it shouldnt know anything about the screenshield backgrounds [23:13] only bug I've found that I haven't reported is one that's been present for some time (currently affects 12.04, 13.04 and 13.10), and the bug is that Empathy doesn't connect to FB, is this a known issue that has a fix? or should I go ahead and report it? [23:14] this bug even affects Arch, so my guess is either that it's a GNOME bug, or FB changed something again. [23:14] ok, maybe g-s-d has nothing to do with it [23:15] c_smith: if you don't know whether a possible bug has been reported or not, you can search for whether it's been reported [23:16] if you don't find anything, go ahead and report it; if it's a duplicate bug triagers will mark the bug and you'll be able to follow the original bug easily [23:16] by default, if a bug is marked duplicate you'll be subscribed to the original bug [23:16] jbicha, main thing I'm not sure of is whether to report it upstream, or locally [23:17] both would be great :) [23:17] cool [23:18] reason I was confused is because this also affects a relatively unpatched distro (Arch) [23:19] well that's a clear sign that it's a gnome bug then but it might only be fixed in the 3.10 series; for saucy and previous we'd probably need to backport the fix so having a launchpad bug would help us see that [23:19] hmmmmm..... on the Launchpad part, I just realized I've no freaking clue where to report it to. XD [23:19] ubuntu-bug gnome-online-accounts [23:19] kk [23:19] keep forgetting about that program. XD [23:20] I get so used to making my bug reports pretty much from scratch. [23:21] c_smith, always use ubuntu-bug, it collects important information from your system! [23:21] will remember to. [23:48] I made a bug on with Ubuntu-bug and put essentially a lightly modified bug on the Gnome bug-tracker. [23:48] now to hope that this isn't something that the devs at FB did. [23:49] I noticed recently Pidgin doesn't connect properly either, so I'm getting the feeling it's something on the FB end.