[00:32] Man, writing upstart rules is super-easy. [00:32] Now I just need to figure out the proper dbus-monitor incantation I want. [00:39] RAOF: http://dbus.freedesktop.org/doc/dbus-specification.html#message-bus-routing-match-rules :) [00:52] RAOF and robert_ancell :0 glad to see both of you ! I have a lightdm-that-might-be-an-x question [00:55] RAOF and robert_ancell , so I got my fancy new x220 (intel, of course) and everything is working great now...after some tweaking [00:56] but on the unity-greeter screen, my mouse has HUGE amounts of lag on it...I can't really move it around... [00:56] not sure how to debug it and get you both some useful information [00:58] jasoncwarner_, anything in the -greeter.log file in /var/log/lightdm? [00:58] * jasoncwarner_ looking [00:58] jasoncwarner_, also, once logged in can you run 'dm-tool add-nested-seat' and see if the same problem occurs? [01:00] robert_ancell: what should I be looking for in the greeter log? [01:00] anything looping around? [01:00] i.e. hundreds of lines of something? [01:01] robert_ancell: no, nothing like that... [01:01] dm-tool, should I just run that and then reboot? [01:02] no, it will pop up a nested X window with a login screen [01:02] which is running everything the same as normal, except it uses the Xephyr X server instead of the normal one [01:03] do you know package name ot install for xephyr? [01:03] jasoncwarner_, apt-get install xserver-xephyr [01:03] thanks, installing... [01:04] thanks,,, robert_ancell [01:04] it does not happen in the dm-tool [01:04] mouse moves fine [01:07] robert_ancell: guessing X then... [01:07] that suggests an X problem. It could be gnome-settings-daemon or something like that though [01:08] the next step is to log out, and then go to a text terminal and run top and see if anything is acting up [01:08] (I'm assuming it always occurs?) [01:09] robert_ancell: yeah, it has always happened ... "always" being, 'since I got this computer yesterday...every time on this comp" [01:09] I'll log out now and check top...be back in a few [01:09] at least it's consistent [01:13] hey robert_ancell I just tried to shutdown/restart from the greeter [01:13] #1 - the box wasn't themed with a GTK style...it was base GTK [01:13] #2 - nothing worked? couldn't restart and couldn't power down... [01:13] do you have a /etc/lightdm/unity-greeter.conf? [01:14] robert_ancell: rebooting again...will check in a sec [01:15] robert_ancell: I hate writing this, and I don't know how you'll feel reading it (RAOF either) [01:15] but when I went to a tty and then back to unity-greeter [01:16] the mouse just started working fine [01:16] and then when I rebooted...it seemed to work fine [01:16] that is my def of "magic" :) [01:16] oh yay [01:16] um, so problem solved right? [01:16] :) [01:17] :) that would be an awesome note in the release notes: if laggy mouse, do this ;) [01:17] btw [01:17] i do have a unity-greeter.conf file [01:18] jasoncwarner_, does it sound like bug #828112? [01:18] Launchpad bug 828112 in unity-greeter "Password field feedback slow at times" [Medium,Incomplete] https://launchpad.net/bugs/828112 [01:21] robert_ancell: I think it resembles, that but not exactly. [01:21] though, when I am having the problem, yes, the password field does have lag as well [01:22] could you put your notes on that bug and note the mouse was also a sympton [01:24] robert_ancell: will do [01:29] robert_ancell: lag is back after reboot [01:29] and, yes, it was solved simply by this [01:29] CTRL+ALT F2 [01:29] CTRL+ALT F7 [01:29] no lag after that [01:29] rebooting again... [01:31] robert_ancell: could it be gnome-settings-daemon related? [01:32] I am getting pretty consistent crashes with g-s-s [01:32] and that might be why I don't have a GTK theme on the shutdown dialog? [01:32] I'm just speculating, but both the indicators and g-s-d could run all sorts of things that unity-greeter has no control over [01:33] The sound indicator runs pulse for one... [01:35] I imagine if g-s-s fails to load I would have quite a few problems...and g-s-s crashes each and every boot for me. [01:35] so perhaps... [01:35] https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/838502 [01:35] jasoncwarner_: Error: bug 838502 not found [02:20] robert_ancell: after rebooting quite a few times,I think that bug you linked before and mine are probably the same [02:21] the op prob just didn't move his mouse to see it not moving [02:21] jasoncwarner_, oh good. Is it coming back again? [02:21] yeah [02:21] yeah, that was my guess too [02:23] robert_ancell: did you see my above? I can get it to go away with switching to TTY and back again [02:23] and when I lock my screen and go to switch user (which brings me back to unity-greeter) [02:23] I get it as well [02:23] RAOF, ^ does that sound remotely X related? [02:24] My first guess is video drivers with VT switching, or some sort of power management issue (i.e. idle checking) [02:25] robert_ancell: I'm on intel on this machine... === qwebirc74340 is now known as cyphermox_ [02:35] robert_ancell: That could be X related; VT switching drops drm master, and switching back regains it, which might mean that if it failed the first time then VT switching could re-enable acceleration? [02:36] RAOF, anythink we could check to confirm that? [02:36] robert_ancell: /var/log/Xorg.0.log would contain information to confirm or deny that hypothesis. [02:36] jasoncwarner_, ^^ [02:37] RAOF: what should I be looking for int aht log? [02:38] jasoncwarner_: Well, pastebinning it would be good. The drmOpenDevice lines would be part of the bit. [02:40] RAOF: http://pastebin.com/HwtT0JZn [02:41] Well, that doesn't contain what I'd expect. [02:42] Oh! Compiz is being really slow? Can you check your top output? I've had a problem where something's spamming the dbus, and dbus-daemon has high CPU usage, and because the panel is in the compositor that means that _everything's_ slow. [02:42] (I think in my case it was because indicator-datetime was endlessly trying to enumerate all my calendars) [02:43] VT switching could possibly halt compiz for long enough to unwedge things. [02:44] RAOF: my top didn't show compiz being slow...I'll reboot and look again...but remember, switching to a VT seems to clear it all up...I'm not sure I'll be able to see it... [02:44] oh...I'll log in remotely to see if it is there [02:48] RAOF: ok...I'm actually goign to finish these three emails from my TODO first...been all day and I haven't gotten 'em done...be back in a bit [02:49] jasoncwarner_: No problem :) [02:49] robert_ancell: Have you played around with dbus-monitor? I can't seem to get it to display anything but signals, and I want to trace method calls instead. [02:50] RAOF, no, sorry [02:51] RAOF: system or session bus? and do you need the content of the call of just interface, path and function name? [02:51] RAOF: you can't use dbus-monitor to get method calls by default [02:51] stgraber: System bus, and I really just want to know _when_ it gets called. [02:52] broder: Ah, well now my results make sense :) [02:52] RAOF: sorry can't help much with system bus unless you can tell your client that it's at another location than /run/dbus/system_bus_socket [02:52] (I wrote a dbus proxy as part of my work on arkose which logs everything that goes through it) [02:53] RAOF: if you put http://pastebin.ubuntu.com/679351/ at /etc/dbus-1/system-local.conf and then do pkill -HUP dbus-daemon, you'll be able to see them [02:53] broder: Can I mess with the system bus config to make that work? [02:53] but that completely compromises the integrity of anybody that's depending on dbus for security :) [02:53] e.g. NM [02:54] Well, it's just for local debugging, so that's fine. [02:54] RAOF, does it make sense to disable TCP connections in lightdm by default for security reasons (Bug #838152) [02:54] Launchpad bug 838152 in lightdm "hard-coded "-nolisten tcp"" [Low,Triaged] https://launchpad.net/bugs/838152 [02:55] robert_ancell: Not listening on TCP is certainly the correct default. [02:55] RAOF, ta [02:56] It's something that you might want to offer as an option, though. [03:13] RAOF: fwiw, i think there are less heavyhanded ways of enabling limited eavesdropping, but i've never been able to get them to work [03:14] broder: Nyargh! Is there a *more* heavyhanded way of enabling eavesdropping? I've dumped that in, and can see _other_ method calls, but not the ones that I'm interested in! [03:15] hmm..that's not a problem i've had before [03:15] are you sure the calls are actually getting made? [03:15] Ah, there we go. [03:15] Apparently you need to restart d-feet before that'll work. [03:16] Oh, yeah! The dbus reload probably needs that, doesn't it. [03:16] huh, weird [03:18] I wasn't expecting getting dbus-monitor to work to be the most difficult part of this :) [03:20] Writing upstart rules is plesantly easy. [03:21] https://plus.google.com/115895054477394715961/posts/84KCPX2xgUh [03:22] ping RAOF [03:23] so good news bad news time [03:23] good news: the signal for figuring out when a resume happens works [03:23] bad news: recreating the FBO's doesn't fix the corruption issue [03:44] DBO: Hm. That's non-good. [03:44] so looking at it more carefully [03:44] what I observe is this [03:44] DBO: I thought you'd previously tested and found that to work? [03:45] it did in nux [03:45] I was assuming that would transfer over... [03:45] (we had the inverse problem last cycle, nux was corrupted and compiz wasn't) [03:45] so my observations seem to be as follows: [03:46] 1) the FBO, without being reloaded, actually pants fine (contents are uncorrupted when painted into) [03:46] 2) painting the texture the fbo is bound to onto another fbo works fine [03:46] 3) painting the compiz FBO onto the backbuffer somehow fails terribly [03:47] which really makes me wonder, why do the nux fbo's paint just fine [03:47] Because magic. [03:47] Presumably :) [03:48] I have a screenshot [03:50] RAOF, http://i.imgur.com/TFOXc.png [03:50] see how the corruption is a predictable pattern [03:50] I suspect somehow the driver is blending the FBO onto the backbuffer with an incorrect format [03:50] That looks like it's likely to be tiling-related. [03:51] tiling? [03:51] Given that it occurs on what looks like tiling-sized blocks. [03:52] Textures aren't linear in memory, at least not if you want it to be fast. [03:52] oh [03:52] is that done automatically by the driver? [03:52] They're tiled into crazy patterns so that the multi-bar memory controllers are used maximally. [03:52] Yeah, that's done by the driver. [03:53] maybe an error in the fixed function pipe [03:53] (sam, he's silly like that) [03:54] obviously unity blends fine [03:54] But it's a fertile source of bugs in the kernel/DDX/mesa layers, at least for the free drivers. [03:54] and functionally, it too is painting FBO's [03:55] Yeah, if Unity's doing shadery things and compiz is using fixed-function that could be different, I guess. [03:56] well I mean painting the contents of an FBO shouldn't be functionally different than painting a texture [03:56] which still works fine [03:56] DBO: Will you still be around in ~20 minutes? I'd like to relocate back from this cafe to home. [03:57] yes [03:57] Ta. [03:57] Catch you in 20. [04:23] DBO: Back. [04:23] welcome back RAOF [04:26] RAOF, if you got any ideas that would be great... [04:26] RAOF, is the backbuffer tiled? [04:26] *Everything* is likely to be tiled; back buffer, front buffer, textures, the whole enchilada. [04:26] Because it's like a 300% performance win. [04:27] hmmm [04:27] (Well, not exactly, but it's a huge performance win) [04:27] I hope we dont have to recreate the GL context to get around this [04:27] In fact, from what I gather from nouveau the nv5x+ cards don't actually handle *untiled* surfaces. [04:27] that would kind of suck [04:28] That would rather suck, yes. [04:28] Can you recreate the backbuffer or something? Like, swap out the composite overlay window? [04:34] I dont think so [04:34] maybe? [04:35] That might be something to try, if some tiling bit isn't getting reset properly across suspend. [04:36] wow [04:37] I just realized that the opengl plugin in compiz creates a shader in the most crazy ass fashion [04:37] im betting if we change how we paint this thing [04:37] that will fix it [04:38] Hah! [04:38] Always it is with the craaaazy compiz! [04:47] robert_ancell: good work on unity-greeter today, fixed 2 of my bugs! [04:49] my indicators are in a crash-loop, it's "fun" to see the appmenu appearing and reappearing [04:57] are there any logs I can look at it to see what's breaking with my indicators? [05:23] jbicha, :) [05:23] Good morning [05:25] pitti: good morning [05:25] good morning pitti [05:26] hey guys, how are you? [05:30] Morning pitti. [05:30] Hey pitti [05:31] so, interesting release night.. [05:34] pitti, how is the release looking? [05:34] was respun during the night due to a pretty serious bug with GPT partitions [05:46] good morning [05:47] bonjour didrocks [05:48] Oh, no! It's didrocks! Quick, hide! :) [05:52] guten morgen pitti [05:52] RAOF: not fast enough! :-) [05:57] the more I see bug report, the more I will be in favor to revert Ctrl + Del to simply Del. The trash is there for fat fingers… [05:57] didrocks: I agree with that.. [05:58] and now crtl+del is harder to do than shift-del, which immediately removes it.. [05:59] this was one of these rather pointless changes which destroy the habits learned in years *sigh* [05:59] pitti didrocks change it to just DEL? makes most sense to me. [06:00] can do it if you both agree :) [06:00] and +1 with pitti's remark, it's harder that shift + del, which is some kind of hilarious :) [06:00] than* [06:00] didrocks: we'd need to update the GNOME documentation for that, too, though [06:01] pitti: indeed, so, opening/find a bug and subscribe the doc team to it? (I think there is no patch to the doc for all the indicator/systray removal anyway) [06:01] not sure whether it's in gnome-user-guide or nautilus help or both [06:02] I can have a look, will do that after the cjk landing [06:03] pitti: so, a bunch of package will land with real cjk support (there was a first attempt one ok ago while I was on vacation if i understood correctly), but this time, the correct patches will land [06:03] just saw the confirmation in the bug, nice to hear! [06:03] this touches apt-xapian-index, zg-extension, sotware-center and unity [06:04] jasoncwarner_: FYI ^ [06:04] pitti: ok, will land today if all go well :) [06:04] didrocks: saw that....big change...lots of testing needed [06:04] jasoncwarner_: indeed [06:05] jasoncwarner_: what was missing from the first round was the rebuild of the index once cjk is there [06:05] didrocks: ah...cool...thanks [06:05] once this gets in then, back to oneconf? ;) [06:08] jasoncwarner_: I finished the first round of oneconf in parrallel, it's now working with software-center gtk3 :) [06:09] still missing some speedup improvment (caching and stuff) that I made for the gtk2 version, but it's usable (the whole software-center gtk3 needs some speedups anyways) [06:58] didrocks: I'll take care of making sure the Ubuntu docs say just Delete [06:58] jbicha: I'm writing a script for that, will be way easier :) [06:58] it's not in that many places, is it? [06:59] jbicha: it's in gnome-user-guide FYI, I just run a script to do the sed and such [06:59] jbicha: yeah, but there are the translations ;) [06:59] didrocks: the real docs are in ubuntu-docs, gnome-user-docs is currently just a copy from Debian, it's unclear whether we want to maintain a diff there [07:00] jbicha: if I press F1 on nautilus, it's gnome-user-docs which is used, isn't it? [07:01] didrocks: yes that will need to be patched too, thanks :-) [07:01] jbicha: I'm patching this one (and so, add the tool for regenerating the patch for easier use), can you take care of ubuntu-docs, please? [07:02] didrocks: actually can you correct the nautilus help link to point to ghelp:ubuntu-docs instead of gnome-user-docs? [07:02] gnome-user-docs isn't installed by default [07:03] I thought Nautilus shipped its own help but it just piggybacks on the system help since it's Core [07:06] jbicha: you're right, it's not installed by default [07:06] weird, it's in main, maybe for the dvd? [07:06] didrocks: upgraders will still have it & it's pulled in for users who install gnome shell [07:07] for Natty, we heavily modified gnome-user-docs instead of just using ubuntu-docs so it was installed in Natty [07:09] pitti: You're our resident PolicyKit maestro, right? In bug #837851 it seems that policykit hates colord running as not root; is there a way to tell PolicyKit that it's ok for the colord user to check whether $USER has authorisation on its interfaces? [07:09] Launchpad bug 837851 in colord ""Color" tool in GNOME System Settings only recognizes my webcam as color-manageable device" [High,Confirmed] https://launchpad.net/bugs/837851 [07:09] jbicha: ah, makes sense then, now everything is in ubuntu-docs? I should not touch gnome-user-docs then [07:09] didrocks: yes, it's just easier to keep gnome-user-docs in sync with Debian for now [07:10] jbicha: ok, I remove my script then :) [07:10] jbicha: adding an ubuntu-docs task and assign to you, ok? [07:11] didrocks: that's fine, we were thinking about pushing a new ubuntu-docs update this weekend [07:11] pitti: Specifically, colord asks polkit, as the colord user, whether $USER is authorised to perform the actions, and polkit only allows root to query whether someone else is authorised to perform an action (presumably for security purposes). [07:11] jbicha: but that means that we will have to patch every application to reference ubuntu-docs rather than gnome-user-docs? [07:13] didrocks: there aren't that many apps that use g-u-d, but gnome-control-center probably does [07:13] jbicha: ok, let's try to change it for nautilus first [07:14] good morning everyone [07:15] hey chrisccoulson [07:15] hi pitti, how are you? [07:15] jbicha: so, basically, now it's ghelp:gnome-help#… should it be ghelp:ubuntu-help#… ? [07:15] good morning chrisccoulson [07:15] hi didrocks [07:15] chrisccoulson: pretty well, thanks! [07:15] RAOF: (will get to you, still stuck in release juggling and CD testing in parallel) [07:15] pitti: No problem! [07:18] hmmmm, i just did apport-bug compiz, and apport seems to have frozen :/ [07:18] didrocks: yes, when we push the new ubuntu-docs we'll have to change it again though because the new url will be help: [07:18] instead of ghelp: [07:19] jbicha: ok, let's do that change once you pushed the new ubuntu-docs package, ok? [07:19] jbicha: I'll just push the Ctrl + Del -> Del [07:20] didrocks: yes the other isn't ready yet [07:33] RAOF: so, polkit [07:33] RAOF: right, I'm afraid the 'ownuser || uid==0" check is hardcoded, so that you can't spy on other uers [07:33] users [07:34] That seems like a misfeature. [07:34] so for this we'd need a provision to mark a particular system user as being able to do the same [07:34] Right, that was what I was thinking. [07:34] or a particular program [07:34] like, this privilege could become a polkit privilege [07:35] (recursivity FTW) [07:35] org.freedesktop.polkit.check_authorisation :) [07:35] Hm, no. That wouldn't work; it needs to be a per-action thing. [07:36] You want the colord user to be able to check whether $USER is authorised for org.freedesktop.colord.*, but not anything else. [07:36] So, an extension to the action semantics could do this. [07:36] RAOF: what does colord do if it cannot check this? [07:36] Refuses to add the device, so the cups and g-s-d integration fail. [07:37] asked the other way round, what are the default permissions on org.freedesktop.colord.* ? [07:37] at_console [07:37] I'm not entirely sure why it asks a particular user's permissions to add devices to cups, as cupsd is a system service [07:37] RAOF: eww [07:37] Yeah, I'm not sure if cups is actually going to work *at all* [07:38] colord uses polkit _and_ at_console? [07:38] at_console is an ancient hack for programs which don't use polkit [07:38] Sorry, I couldn't remember the polkit name for at_console. It's default-deny, allow for active user. [07:38] ah, ok [07:38] Ah, allow_active. [07:40] Will allow_active allow cupsd access? [07:40] no [07:40] cupsd is not on any console [07:40] Morning all! [07:40] the consolekit stuff only works for actual sessions, not for system daemons [07:40] hey Sweetshark [07:40] pitti: libreoffice_3.4.2-2ubuntu3 for upload on chinstrap [07:41] RAOF: another option would be to actually stop using polkit, and control this with d-bus policy [07:41] pitti: Yeah, thought so. So, cupsd isn't going to work even once I fix the session stuff. [07:41] RAOF: i. e. allow calling the API from root (that'll cover cupsd) and at_console [07:42] cf. my comment about at_console being deprecated, though [07:42] RAOF: yet another alternative is to let colord run as root, and lock it down with an apparmor profile [07:42] pitti: That would be reasonably easy, and a transitional plan while fixing polkit. [07:43] RAOF: depends on how much patching is involved to remove all the polkit checks from colord [07:43] Although running as root _still_ won't fix cupsd, right? [07:43] pitti: colord has a --no-polkit option. [07:43] RAOF: but I guess it could be factored out, and the functino would only ask polkit if geteuid() == 0 [07:43] and otherwise just allow it [07:43] then we put a d-bus policy in front of it [07:44] that patch should even be upstreamable [07:44] RAOF: ah, that sounds promising, too [07:44] It wouldn't need to be a patch at all; we can just build colord without policykit support. [07:45] you'd need to patch the d-bus policy, but that's relatively simple [07:45] Yeah, I'm pretty sure I know how to do that. [07:45] some of the interfaces might be save for everyone to call [07:46] and the ones that aren't should be removed from context="default" and added to [07:46] and again to [07:46] to cover g-s-d (first) and cupsd (second) [07:47] RAOF: /etc/dbus-1/system.d/NetworkManager.conf does that, for example [07:47] Great. [07:48] And then, a patch to polkit to allow doing this there. [07:52] and a patch to its policy to allow access to root users, not just allow_active [07:52] RAOF: ^ that's easy to do, I can help you with that once it becomes relevant [07:52] (man pklocalauthority) [07:52] something like [07:53] [allow access to cups] [07:53] Identity=unix-user:root [07:53] Action=org.fd.colord.whatever [07:53] ResultAny=yes [07:54] pitti: when you get a second: bug #838623. Do you need a bug/FFe for activating the CJK support? (it was supposed to already be activated, it wasn't the case though) [07:54] Launchpad bug 838623 in software-center "FFe, UIFe: bring back OneConf to Software-Center" [Medium,In progress] https://launchpad.net/bugs/838623 [07:54] didrocks: no, bug fix [07:55] ok, thanks :) [07:55] everything is supposed to work in CJK :) [07:56] Oh, there isn't an yes specifier in the actions. That's kinda strange. [07:56] pitti: indeed :) [07:56] Let's play with dbus policy! [07:57] RAOF: not in the .policy files, no; that needs to go into pklocalauthority [07:59] The strange corners you find in polkit! [08:00] didrocks: don't sweat over dee - we don't need it really, all required things are distropatched by ken, it's just so that other distros can ship gwibber without cherry picking extra api from trunk :-) [08:01] kamstrup: I know, was just kidding :-) [08:01] didrocks: phew, i wouldn't wanna upset you already after my second day back ;-) [08:02] kamstrup: it's never too late to upset me, seems that's dx paradigm ;-) [08:10] morning [08:23] kamstrup, did you get someone to upload jhbuild? [08:24] rodrigo_: I poked lool (as he was the original maintainer afaik), but he was not overly keen on jumping in :-) [08:24] kamstrup, ok, I can do a merge proposal then [08:25] what's the jhbuild version you need? [08:25] hmm, there's only 2.32.4 from last December in download.gnome.org [08:26] rodrigo_: that's also the one :-) [08:26] that's the one you need? [08:50] jasoncwarner_, enjoying your new laptop? ;) [08:51] chrisccoulson: yes, yes I am [08:52] excellent :) [08:52] and, chrisccoulson , glad you are here! :) I had a question for you. I just installed aurora build of FF [08:52] and the menu and ubuntu theme went away [08:52] anyway to get those back? [08:52] i really want to buy a new laptop, but i fear that jo might end my life if i spend money on one, when we're meant to be saving for our own house ;) [08:52] hmmm, the menu disappeared entirely, or appears in it's own window? [08:53] chrisccoulson: it is just not in the global menu position. I would like to renable that because it takes up precious screen realestate on the smaller monitor! :) [08:53] chrisccoulson: just tell her for hte good of your relationship you need a new laptop [08:53] jasoncwarner_, you could try reporting a bug with apport-bug, as the new apport hook i wrote attaches lots of useful information which might save me asking lots of quetions :) [08:53] and then watch how quickly a good relationship can go bad ;) [08:53] heh [08:54] chrisccoulson: I think the menu is the new firefox "we don't enable third party libraries anymore" stuff [08:54] it says it will be renabled when it is "compatible" [08:54] jasoncwarner_, this is a build from the firefox-aurora PPA isn't it? [08:54] whatever that means [08:54] yes [08:54] jasoncwarner_, yeah, apport-bug firefox might help me figure out what's wrong :) [08:55] ok.. [08:55] it should let you report a bug from the PPA [08:55] and it will be useful to find out if the new hook works from there :) [08:55] what about the ubuntu theme? can that be reenabled as well? [08:55] stock firefox isn't exactly pretty :/ [08:56] jasoncwarner_, we only shipped with the stock firefox theme before (it just inherits colours from our theme) [08:56] this "every new release of firefox breaks all the plugins" thing is getting old... [08:56] I highly doubt all those plugins are broken [08:57] would like to be able to override and try it out anyway [09:00] jasoncwarner_, did you manage to report a bug? [09:00] on a call...do it in a bit...I'll let you know... [09:00] thanks [09:01] jasoncwarner_: don't you use https://addons.mozilla.org/addon/add-on-compatibility-reporter/ ? [09:11] jbicha, that won't ever work for the globalmenu-extension [09:11] if it's incompatible, forcing it on will likely just make it crash [09:13] chrisccoulson: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/838671 [09:13] Ubuntu bug 838671 in firefox "Auroa PPA does not work with global menu" [Undecided,New] [09:14] jasoncwarner_, ah, silly me. i need to refresh the aurora branch with the latest version of the extension ;) [09:14] Sweetshark: oh, you apparently built with -sa; I'll edit the sources.changes in-place to drop the tarballs [09:14] i should have checked that already [09:14] https://launchpadlibrarian.net/78687096/Extensions.txt [09:14] nights, how can i report an issue with gnome-settings-daemon from the gnome3-team? [09:15] Sweetshark: oh, or was this done for libreoffice_3.4.2.orig-ext-human-updates.tar.gz? i. e. is that one new? [09:15]