=== m_conley is now known as m_conley_away [01:15] robert_ancell: Good morning! [02:23] RAOF, yo [02:23] Hey, ho! [02:24] Got the compositor up and running? [02:26] RAOF, not yet, but just updated [02:27] As I said, you'll need to remove vesa and fbdev; they aren't compatible with xwayland, but get autoloaded and then the “this module can't work” code isn't quite right. [02:27] ok [02:28] RAOF, we need a list of blocker bugs that need to be fixed to make it to release, e.g. picking the wrong video card, certain video drivers not working [02:29] Yup. [02:35] robert_ancell: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1022423 filed and linked to the blueprint. [02:35] Ubuntu bug 1022423 in xorg-server "VESA and fbdev drivers get loaded and break the server under XWayland" [High,Triaged] [02:36] RAOF, is there one for picking the wrong video card, or is that a udev issue? [02:39] There's not yet one for picking the wrong card; I'll file that, too. [02:48] robert_ancell: It's now bug #1022424 [02:48] Launchpad bug 1022424 in weston "Can pick wrong DRM device" [Undecided,New] https://launchpad.net/bugs/1022424 [03:17] RAOF, hey, are you able to update the debian colord package easily? http://paste.ubuntu.com/1082169/ [03:18] or even http://paste.ubuntu.com/1082170/ (without an accidental whitespace change) [03:18] robert_ancell: Yup, can do. Although I'll be getting around to colord 0.1.22 shortly. [03:18] cool flick that change in then [03:24] robert_ancell: Hey, you've used google docs recently, right? How do I embed a drawing that I foolishly made separately into a document? [03:25] RAOF, i.e. copy and paste from one document to another? [03:25] Yeah, I guess so. [03:26] I don't know if I managed that, but I do remember finding limitations like that [03:28] Ah. And apparently insert->picture is a filthy lie. === ejat- is now known as ejat [03:38] Good morning [03:42] robert_ancell: hey Robert, how are you? [03:42] pitti, hello, good [03:44] robert_ancell: did you recently use simple-scan to scan more than some 5 pages for a document? it's painfully crashy for me these days [03:44] i. e. I scan 5 or 8 pages, then it crashes, and I have to do it all over again [03:45] pitti, no, but there have been some crashers reported [03:45] I had to resort to my old CLI script [03:45] yes, I reported the ones I got as well [03:45] no> you can't reproduce, or you didn't try to scan several pages? [03:45] bug 1022040 [03:45] Launchpad bug 1022040 in simple-scan "simple-scan crashed with SIGSEGV in pixman_op()" [Medium,New] https://launchpad.net/bugs/1022040 [03:46] might just as well be a GTK bug, I'm not sure [03:46] crash in gtk_widget_set_sensitive(), could be that it crashes when it disables the "Scan" button when I press Ctrl+1 ? [03:46] i. e. not related to the actual SANE part at all? [03:47] I haven't reproduced, but I do know of at least one reproducable crasher [03:48] pitti, can you reproduce by running 'simple-scan test'? [03:48] I'm mashing the ctrl+1 key here and not reproducing [03:48] oh, what does that do? [03:48] a fake scanner? [03:48] pitti, uses the 'test' sane driver [03:48] so yes [03:49] hm, it doesn't actually disable the "scan" button while the scan is in progress [03:49] which widget does it try to make insensitive? [03:49] pitti, no, it should queue a new page [03:49] oh, the stop button perhaps [03:50] if you start a new document with a number of queued pages it crashes when the next page comes [03:50] hm, threading issue perhaps [03:50] likely [03:51] I don't seem to get it with "test", or I'm just being lucky this morning [03:52] robert_ancell: how hard would it be to save the current deck of scanned pages to a temporary file and reload it on next startup? [03:52] pitti, there is a patch for that using sqlite but I haven't got it to work [03:52] uhh, sqlite? [03:53] bug #897469 [03:53] Launchpad bug 897469 in simple-scan "Simple Scan crashes result in preventable data loss" [High,In progress] https://launchpad.net/bugs/897469 [03:53] I had expected just saving the individual PNGs or JPGs [03:53] pitti, you need the metadata too really [03:53] ah, for rotation and clipping? [03:53] yeah, stuff like that [03:54] color profiles etc === test is now known as robert_ancell [05:42] RAOF - http://paste.ubuntu.com/1082274/ still no luck it seems [05:42] hi robert_ancell, RAOF, jasoncwarner_, TheMuso and other .au folks :) [05:43] robert_ancell: ‘wl_display_create failed’ suggests that it's not finding the... oh. [05:43] rickspencer3: Yo! [05:43] hey rickspencer3 [05:44] test: ‘wl_display_create failed’ suggests that it's not finding the wayland socket. [05:44] hey rickspencer3, ca va? [05:44] oops, looks like I interupted some xorg debugging ;) === test is now known as robert_ancell [05:44] bonhour piti, ça va :) [05:44] robert_ancell: Because the segfault is in the failure path. (Yay!) [05:45] RAOF, at least we're getting good test coverage then :) [05:45] robert_ancell: :) [05:45] The rest of the francophone contingent arrives! [05:45] good morning :) [05:45] hey RAOF ;) [05:46] Good morning :) [05:46] how was your week-end? [05:47] Pretty good. Almost cleared enough of my office to move a sofa in there from the bedroom so I can assemble the cot ;) [05:47] My office looks a *lot* bigger without a bunch of boxes in it! [05:47] RAOF, so sudo weston works. Does that suggest I've done something wrong and it's just X failing to tell me nicely? [05:48] robert_ancell: You mean, running X under ‘sudo weston’ works, but running it under weston-as-user dies in this fashion? [05:49] RAOF, oh duh, that doesn't run X at all.. [05:49] X *is* telling you nicely (before it segfaults ☺) - it says [ 418.249] (EE) intel(0): Failed to initialize xwayland. [05:49] is there an easy way to do that? [05:49] robert_ancell: weston --xserver [05:49] Then start an X app, and it'll transparently start an xwayland server for you. [05:50] RAOF, yep, that worked [05:50] OK, so I'll assume it's in my code then [05:51] I'll check again that simple-display-manager actually starts an X server, but it's probably your code, yes.e [05:52] RAOF, gtg, thanks for that. [07:21] Bah. So much for escaping the cold Sam's recovering from... :( [07:37] hey [07:39] morning seb128 :) [07:39] bonjour seb128 [07:39] hey mlankhorst, pitti, how are you? [07:40] seb128: I'm great, thanks! how about you? [07:40] I'm good thanks! [07:40] we had a really nice weekend, spending a lot of time gardening and enjoying the sun [07:40] for a change, no travel and no guests :) [07:40] im good, weekend was terrible and rainy :) [07:41] guten morgen pitti, mlankhorst :) [07:41] bonjour didrocks, ca va? [07:42] pitti, saturday was nice weather here, yesterday a bit rainy but since that was wimbledon finals' day that was ok ;-) [07:42] pitti: ça va bien! good week-end here as well :) [07:42] no rain, quite warm weather :) [07:42] but visited a friends place so I had fun, f-zero and super smash brother doesn't need good weather [07:43] seb128: I have a fix ready for bug 972436; but current apport SRU still has 4/5 unverified, so it's blocked :( [07:43] Launchpad bug 972436 in apport "backend_helper.py crashed with UnicodeEncodeError in apport_excepthook(): 'ascii' codec can't encode character u'\xe8' in position 166: ordinal not in range(128)" [High,Confirmed] https://launchpad.net/bugs/972436 [07:43] mlankhorst: these sound like games? [07:45] pitti: f-zero is a game from the gamecube working on wii, ssb is a series with a wii version [07:45] I'm probably going to buy the wii-u just for that game [07:45] f-zero is a snes game in fact :p [07:46] in its first form [07:46] ah could be [07:46] "could be", it's when didrocks starts to feel old :) [07:46] http://www.youtube.com/watch?v=2T5u9nD_I0I [07:47] impressive speed sensation at the time using the snes mod 7 ;) [07:47] pitti, hum, k, let's try to get that SRU verified this week then [07:47] sigh, the vfs tree I need to avoid deadlocks doesn't boot [07:49] seb128: I'll work on improving the D-BUS exception support in the meantime, perhaps we can fold that into the next SRU as well [07:49] pitti, that would be great! would make didrocks happy as well, his top bug on oneconf is one of those ;-) [07:50] \o/ [07:50] juts for that, I'll fix the latest issue introduced recently by python-distutils-extra :) [07:51] g'morning [07:52] Laney, hey, how are you? [07:52] hey Laney [07:52] hey, yeah good [07:53] nice weekend of cycling and trying to return to climbing after injury :-) [07:53] Laney, injury during climbing? [07:53] or just an injury that made you stop climbing for a while? [07:54] well, both. I injured the "pulleys" on some of my fingers [07:54] still not completely healed but I think I can start gently again to help it recover [07:55] ok === tkamppeter_ is now known as tkamppeter [07:58] pitti, hi [07:59] hello tkamppeter [08:00] pitti, can you have a look at bug 763867, comment #7 and comment #8? [08:00] Launchpad bug 763867 in cups "Canon binary 32-bit drivers can not be installed on Ubuntu 12.04" [Undecided,Confirmed] https://launchpad.net/bugs/763867 [08:05] tkamppeter: replied [08:06] pitti: so the .decode('UTF-8') in http://launchpadlibrarian.net/107350300/python-distutils-extra_2.32-5_2.33-1.diff.gz brought some new warning on precise and quantal with Quickly [08:06] pitti: basically the file contains already the magic "I'm an utf-8 encoded file" [08:06] then .decode tells: [08:06] WARNING: syntax errors in foo/FooWindow.py: encoding declaration in Unicode string (FooWindow.py, line 0) [08:07] le huh? [08:07] seems this should be silent, no? [08:07] I'm afraid I don't understand [08:07] ok, so, the files in Quickly all contains: # -*- Mode: Python; coding: utf-8; indent-tabs-mode: nil; tab-width: 4 -*- [08:07] 2.33-1 changed the open() call to be binary and decodes from UTF-8 itself [08:07] as otherwise it depends on the system locale [08:08] didrocks: sure, and they'll have to if they contain non-ASCII characters with python2 [08:08] indeed [08:08] that patch wouldn't have changed that behaviour at all [08:08] seems that if you call .decode('UTF-8') on such a binary flow, you get the above warning [08:08] pitti: I tried by commenting the .decode() call, and indeed, no more warning [08:09] then you call ast with bytes, not a string [08:09] yeah [08:09] that seems wrong, though [08:09] but even the previous revision didn't get any warning, when you opened the file as string [08:09] (I tried to revert the stenza) [08:09] I would have thought this was equivalent to what you are doing now [08:10] ah, I guess in python2 open(.., 'r') still returned bytes [08:10] oh right, it's python 2 :) [08:10] so ast has no issue to accept bytes [08:10] did you try with py3? [08:10] but I agree it's not the trendline to move everything with string :) [08:11] no, I didn't [08:11] but not sure we want to change to py3 on precise :) [08:11] sure, but I didn't upload that to precise, only to quantal [08:11] pitti: it's in precise-proposed [08:11] so, that seems easy enough to reproduce in a test case [08:12] https://launchpad.net/ubuntu/+source/python-distutils-extra/2.33-0ubuntu0.1 [08:12] oh, someone backported the whole new version [08:13] didrocks: so yeah, can you please report a bug for this? we should add a test case with an utf-8 marker [08:13] then the py2 run should fail [08:13] and we can either toss bytes to ast or do a sys.version_info.major test [08:13] pitti, thanks. [08:13] pitti: I can report a bug, but not sure what's the best strategy to really fix it? [08:14] didrocks: see my previous line :) [08:15] pitti: is it the best fix? seems to be .decode('UTF-8') shouldn't bail if the decoded associated binary is specifying UTF-8 [08:15] didrocks: it's not the .decode() that generates the warning; it's ast [08:15] didrocks: you hand an unicode object to ast in python2, and ast encounters an encoding line in the source; that's what's generating the warning [08:16] all of that madness went away in py3 (source is required to be UTF-8 encoded, and no tag is necessary any more) [08:16] but at least in python2 we need to feed bytes to ast apparently [08:17] pitti: ah, because ast in that case think that if there is an encoding line in the object passed to it, it should be binary? [08:17] apparently [08:17] ok, got it now, will file a bug, test case and a fix :) [08:17] cheers! [08:17] thanks pitti :) [08:17] didrocks: so this p-d-e should be verification-failed then [08:18] * pitti hugs didrocks, merci [08:18] indeed :) [08:18] * didrocks hugs pitti [08:26] confirmed in an ipython [08:26] seb128: did you get anywhere on that gsd patch? [08:26] if not then I'll look at it now [08:27] not yet, feel free to look at it [08:28] k [09:09] pitti: when you get some time: https://code.launchpad.net/~didrocks/python-distutils-extra/fix-warning-using-python2/+merge/113928 [09:12] didrocks: merged, thanks! [09:12] pitti: do you mind if I do a release? I want to backport that to precise-proposed and if the fix is not in quantal, the SRU team doesn't allow it anymore even if it's in trunk [09:13] pitti: thanks for the review :) [09:13] (or if you have time and want to do it…) [09:13] didrocks: I'm currently at it [09:13] excellent! [09:13] to Debian as well [09:13] perfect ;) [09:13] doing the backport to precise-proposed meanwhile [09:14] hi pitti, didrocks [09:14] hello thumper, how are you? [09:14] pitti: mostly good [09:14] frustrated by a gdb bug ☹ [09:14] hey thumper [09:14] but happy I've learned more Alt-Gr codes ☺ [09:15] ♥ [09:15] thumper: want to swap? I'm frustrated by a kernel deadlock :-) [09:15] haven't yet found the cuppa or scissors [09:15] mlankhorst: ah... pass [09:16] thumper: like ✂ ? [09:16] pitti: yeah... [09:16] pitti: how plz? [09:16] thumper: ctrl+u 2707 [09:16] err, 2702 [09:17] pitti: doesn't work in quassel :( [09:17] ah, Ctrl+U is GTK's way of entering an Unicode char; Qt might have a different one [09:17] control-shift-u ? [09:18] mlankhorst: ah, indeed, sorry [09:18] thumper: ^ [09:18] ✇ [09:18] ♪ rocking ♩ ! [09:18] * thumper feels unicode incapable [09:19] I only know some 4 by heart; I use gucharmap or vim digraphs for the others [09:19] I [09:20] didrocks: there, have an upstream/Debian/Quantal 2.34 release [09:20] happy to be able to say 28°C [09:20] but it isn't :( [09:20] 'tis winter [09:20] * didrocks hugs pitti, thanks! [09:20] pitti: I was wanting a short cut to say ✂☹ [09:22] too bad that DEAD and BEEF are not nice unicode chars :) [09:22] :) [09:22] well, 뻯 might very well mean "beef" in whatever script that is [09:23] * didrocks loves when the package is built on soyuz before launchpad computes the diff [09:29] seb128: hm, http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=b6e011ad16311e2985aa523cf9bceef74168f95e makes this quite complicated [09:36] Laney, yeah, I was planning to revert that commit [09:36] Laney, to be able to do at least the current updates [09:36] hm [09:36] that would probably get harder and harder to maintain [09:36] Laney, it's going to be problematic for further updates but that should unblock the first round [09:37] Laney, yeah, well, no regression and having a proper keyboard indicator or a status icon back to patch is going to take a while [09:38] seb128: alright, i'll try it [09:38] Laney, thanks [09:39] Laney, I'm still not convinced of the best way out, we could stay on 3.4 for g-s-d and g-c-c this cycle but I'm not convinced it's a win situation [09:40] indeed. and we'll still have to do the work in some future cycle [09:40] the new version have some nice improvement, tweaks design wanted, support for enterprise logins, etc === dpm is now known as dpm-bbl === rickspencer3 is now known as rickspencer3_ === rickspencer3_ is now known as rickspencer3 [10:04] seb128, didrocks: I wrote some test cases for bug 1020572: http://paste.ubuntu.com/1082499/ [10:04] Launchpad bug 1020572 in apport "Deal better with DbusException errors" [Medium,Triaged] https://launchpad.net/bugs/1020572 [10:05] seb128, didrocks: look at the "DbusErrorAnalysis" checks; does that seem appropriate to you? anything which this should check in addition? [10:05] it's still missing a service which crashes during a method call, which should also cause a NoReply, but with no running service [10:06] that'll be somewhat more tricky to set up, but I'll work on it; but I'm interested in the general feedback [10:08] pitti: looks nice, I didn't know there was two possibility, like process running on different bus and that can be detected :) [10:08] pitti: yeah, the naming seems appropriate to me [10:08] Instead of prose, it could also contain some tag-like fields [10:09] but I'd like to include the detected paths and process names as well [10:09] pitti: test_dbus_service_timeout isn't about a service not responding? [10:09] pitti: which is the same than crash at startup, isn't it? [10:09] didrocks: it is [10:09] didrocks: but it's a hanging process, not a crashed one [10:09] didrocks: i. e. the service is running and you get a NoReply [10:09] didrocks: if the backend is crashing during a call, it will not be running [10:09] (that's the missing case, still above) [10:09] err, "see" above [10:11] pitti: ah ok, in the additional metadata, you are telling that it's still running though [10:11] got it :) [10:11] well, I think you will need a mock service which will crash at startup for your tests [10:12] when called on a particular dbus method [10:15] right, I'll add that === dpm-bbl is now known as dpm [10:57] pitti, looks fine to me! === MacSlow is now known as MacSlow|lunch === gord is now known as gord|lunch === gord|lunch is now known as gord [12:30] * desrt mumbles something about monday and coffee [12:31] hey desrt ;) [12:32] damn you and your timezone [12:33] heh, happy monday morning! [12:34] hey desrt [12:37] good morning to both of you [12:37] * desrt has a bad day ahead [12:37] hey desrt [12:38] i finally did some real runtime testing of my dconf reorganisation last night [12:38] works great [12:38] except for the fact that every time you write a setting it deletes all of the other ones [12:39] desrt, small bug... [12:39] ya [12:39] i was thinking i should release it anyway [12:39] seb128: SRU, perhaps? [12:40] let's see if some user notice [12:40] at least, if they get it we can say "yep, but at least, we knew it before you" :) [12:40] desrt, that would be lot of "fun" ;-) [12:41] "we do not consider the feature of retaining old settings to be important. why do you feel the need to customise more than one option?" [12:41] ^ new GNOME attitude :D [12:41] ;-) [13:16] mvo, hey, how are you? [13:17] hey seb128 - I'm sure you want to nag me about aptdaemon! and you are right for doing it [13:17] mvo, ahah, how did you guess ;-) [13:19] seb128: I was feeling as well that this "how are you" was too nice on a Monday ;) [13:19] didrocks, :-p [13:20] ;) [13:20] seb128: you need to try it my way [13:20] didrocks, don't worry, I'm going to nag you about the unity SRU soon ;-) [13:20] seb128: then nobody suspects a thing [13:20] seb128: well, let's popey's team doing a unity release first :) [13:20] desrt, "can you review this patch: URL"? [13:20] seb128: I did some p-d-e and quickly sru today, did my precise part :p [13:20] didrocks, will that happen before the end of year? ;-) [13:20] seb128: but the sru team is really behind it seems [13:20] :p [13:20] seb128: let's see ;) [13:21] popey, half ":p", we are on a tight schedule for the LTS .1... [13:21] seb128: no. you have to complain about it being monday and mumble something about coffee [13:21] seb128: then, when they're not expecting, you go in for the kill [13:22] desrt, lol [13:22] desrt: you didn't ask anything to us, pitti and I, trapped fish! :) [13:22] didrocks: today was the control [13:22] ahah [13:23] i catch you and release you, so you feel safe [13:23] mvo: hey. any news on the sso gtk+ moving? [13:23] didrocks: but now that you mention it... [13:23] didrocks: just a friendly poke about the status of the dconf profile work :) [13:23] * didrocks is not there [13:23] dobey: its in trunk in s-c now, once I know the parameter I need to pass to the dbus call to call my own custom sso binary I think its done [13:24] desrt: you know it's far from being a priority for me, isn't it? ;) [13:24] didrocks: i expect you will tell me "i was busy on other stuff" and that's fine :) [13:24] just wanted to let you know that i still care :) [13:25] mvo: to the sso regiser and login calls, one of the arguments is a dict; you just add "'ui_executable': 'name-of-the-binary'" to that dict [13:25] didrocks, seb128: I implemented the analysis stuff for ServiceUnknown now, all tests pass now [13:25] desrt: I think it's a good idea, but I will try to do some experiment with it this cycle, but I think if we are going to switch to that, we need a proper blueprint and planning to chance all the override stuff to profiles [13:26] pitti: woooow \o/ [13:26] let's see how far it gets us [13:26] desrt: like the guadec hacking seesions will be a good time IMHO :) [13:26] didrocks: sounds great [13:26] dobey: cool, I add that now, thanks [13:26] didrocks, seb128: NB that NoReply is still blacklisted, as we cannot squeeze anything useful out of it right now [13:26] didrocks: i have a substantially lessened obligation to board duties this year, so i can actually have some hacking time :) [13:27] pitti: testing!! it's fun!! [13:27] desrt: it really is! [13:27] desrt: yeah, you will see the guadec this year and not be locked in a room for a week ;) [13:27] pitti: ok [13:27] pitti: lcov is like ... amazing [13:27] it turns testing into a game [13:27] gotta get a high score! [13:27] (100%, ideally) [13:27] pitti, ok, let's see how that goes, have some of cases handled is a good start ;-) [13:27] desrt: yeah, found the same with python-coverage back then :) [13:28] kenvandine, Sweetshark, kenvandine: hey [13:28] hey seb128 [13:28] kenvandine: are you going to say hi a second time? [13:28] seb128: as soon as we convince the NoReply exception message to reveal which method/dbus name it tried to talk to, we can cover it, too [13:28] kenvandine, Sweetshark, kenvandine: so it seems like the libreoffice 3.5.4 SRU got set verification-failed by micahg due to lo-menubar issues [13:28] ups [13:28] sorry [13:28] kenvandine, Sweetshark, micahg: ^ [13:28] indeed [13:29] i couldn't reproduce it on quantal [13:29] what's the deal there? [13:29] did you try with lo 3.5.4? [13:29] kenvandine: quantal doesn't have 3.5.4 yet [13:29] oh... i assumed it did [13:29] isn't that the rule? gotta upload to devel before SRU? [13:29] that would be interesting to test [13:30] i do have plasma-desktop installed still [13:30] Sweetshark, is LO 3.5.4 in a PPA or somewhere yet? [13:31] kenvandine, it's not an hard rule, we didn't want to block the SRU on sorting quantal toolchain issues [13:32] i see [13:32] kenvandine, and we aim at uploading lo 3.6 beta and not 3.5.n to quantal [13:32] kenvandine, you can probably install the precise-proposed version on quantal [13:32] can someone on precise test lo-menubar 1.1 with the older LO? [13:32] and plasma-desktop [13:34] by Sat night I was thinking that there was indeed no breakage in -updates, and that it was contained in -proposed with the lo3.5.4/lo-menubar 0.1.1 combo [13:34] but I didn't get a chance to confirm it [13:35] micahg, btw I don't care much about the menubars to be broken, the current precise version segfaults libreoffice in some cases and make you loose work wheny ou want to print [13:35] micahg, I like better breaking menubars than having the segfault [13:35] especially that they are from universe [13:35] i.e not supported [13:35] seb128: well, -updates is 0 regressions from what I've been told, you can't trade breakage in an SRU [13:36] the menubars also don't seem like worth failing the libreoffice SRU [13:36] micahg, well, that's a non supported universe package [13:36] seb128: but IANA SRU team member, didn't want it auto-migrated without this issue being looked at [13:37] seb128: I think that's irrelevant as far as breakage goes [13:37] it was migrated [13:37] the bug says it makes plasma-desktop crash [13:37] somebody rolled it back out to proposed [13:37] but it doesn't include a crash report [13:37] seb128: no, I meant libreoffice [13:37] dobey: just to double check, support for the ui_executable is not in quantal yet, correct? i.e. in testing I will see the default -gtk client come up? [13:37] micahg, would you be happy if we make libreoffice Conflicts lo-menubar and just document to not install those? [13:37] * kenvandine would be in favor of that [13:38] seb128: if that's the agreement you come to with the SRU team, that's up to you [13:38] lo-menubar in general has been buggy [13:38] micahg, well, you are the one who failed that SRU [13:38] and it isn't part of the default experience [13:38] micahg, not the SRU team [13:38] mvo: support is there already, yes; it's in precise too [13:38] seb128: only to get review before promotion [13:38] micahg, that's why I'm asking you [13:38] mvo: so once you have it installed, it should work [13:38] micahg, well you also got the menubar update reverted from -updates [13:39] mvo: it will look exactly the same as the current -gtk client, so you'll have to check the process list to see which one it is, really [13:39] seb128: yeah, which I think might have been not necessary, but it's easy enough to push lo-menubar back to updates if the issue is confirmed to be limited to lo 3.5.4 [13:40] EOD Friday is not an opportune time to discover these things [13:40] right [13:40]