[00:45] cyphermox, Did the fix for bug 1035431 ever go upstream? It doesn't seem to be in git and I can't find a bz link [00:45] bug 1035431 in gnome-bluetooth (Ubuntu Trusty) "bluetooth-wizard failed to connect to a keyboard(logitech)" [High,In progress] https://launchpad.net/bugs/1035431 [00:45] I'm happy to do it, just don't want to duplicate work [00:48] timchen119, ^ === darkxst_ is now known as darkxst [01:02] bregma: ping - greyback suggested I talk to you here about narrowing down the component for logging a lockup bug. [01:05] I think it's probably an instance of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1384342, but I'm not sure how to confirm [01:05] Launchpad bug 1384342 in linux (Ubuntu) "kernel messages intel_crtc_wait_for_pending_flips correlate to compiz hang" [High,Triaged] [01:06] Symptoms are that all X applications become unresponsive to mouse, keyboard becomes unresponsive. [01:06] Mouse pointer still works, but is confined to screen 0 (my external monitor doesn't work). [01:06] On trusty, if I just let it sit there, it would come good after about 30-60 seconds. [01:06] On utopic, if I don't manually intervene and switch to a text console and back, it never comes back (at least not in the 12 minutes that I waited last time). [01:06] Switching to a text console and back works extremely slowly, but eventually does the right thing, and everything continues on. [01:06] Other symptoms are: out of order messages in /var/log/syslog (like, 5 minutes out of order), and no kernel oops until I switch VCs. [01:06] Here's the oops that does occur eventually: https://pastebin.canonical.com/121261/ [01:28] After reading that bug more, I think it's the same one affecting me. I've metooed it and added links to another oops & related bug that might be the same one. [02:24] robert_ancell: it's backported from upstream git commits [02:24] that said, I thought it had been uploaded already [02:24] cyphermox, it's not in upstream git [02:25] the SSP code? [02:25] cyphermox, I've opened bugs with patches for our two remaining ubuntu patches === oCrazyLemn is now known as CrazyLemon [02:25] yes [02:25] sure is, though not exactly as-is, since it was bluez5 code [02:25] oh wait [02:25] yeah ok, gnome-bluetooth [02:25] https://bugzilla.gnome.org/show_bug.cgi?id=740829 [02:25] Gnome bug 740829 in general "Wrong signature for org.bluez.Agent1.DisplayPasskey" [Normal,Unconfirmed] [02:25] these parts might not be [02:25] https://bugzilla.gnome.org/show_bug.cgi?id=740830 [02:25] Gnome bug 740830 in general "Add default PIN for Logitech Ultrathin Touch mouse" [Normal,Unconfirmed] [02:28] ok [02:28] well, you're not duplicating work I've been doing [02:29] though AIUI there were commits in upstream git that made the PIN for Ultrathin no longer required [02:30] ah, I see, I'm mixing things up [02:31] there was another thing for Microsoft devices [02:59] robert_ancell: from your bug about updating gnome-bluetooth, have you uploaded the package to ppa:ubuntu-desktop/bluez5 too? [03:00] cyphermox, yes but to the transitions PPA as requested by didrocks [03:00] err [03:00] I thought we were using the one named bluez5 [03:00] So I think he plans to do a binary copy into ppa:ubuntu-desktop/bluez5 [03:00] not that it changes much [03:00] ok [03:01] I think there might be a change of plans based on the email discussion I had with didrocks and seb128 [03:01] I'll test it out in the morning; so I'll put my headset on charge now [03:03] * RAOF should probably fire up his Ziks and see if they work there. [03:03] let's see if everything landed [03:04] The bluez5 PPA is no longer a thing... SO I guess the transitions PPA is what one should use... [03:04] robert_ancell: ah, it was removed and everything is in transitions yes [03:04] cool [03:04] That really should be more widely announced... [03:05] I'm not sure either was really announced [03:05] at least pulse and bluez5 and gnome-bluetooth are there, so things might be in a good enough shape to be usable [03:05] Sure the bluez5 ppa was not announced, but the thread we had going about pulse etc likely has people wondering where things have gone if they update and find a 404. [03:05] yeah [03:05] At least I was wondering about it. [03:06] well, at least all the pieces seem to be in place for testing [03:07] except for my headset batteries being charged, that is [03:14] heh' [03:15] I'm off to bed now, good day! [03:15] cyphermox, bye! [06:45] good morning [07:09] lut didrocks [07:09] salut seb128 [07:09] Laney, bug #1397135 seems a regression from the upower fix from yesterday [07:10] bug 1397135 in unity-settings-daemon (Ubuntu) "Error in `/usr/lib/unity-settings-daemon/unity-settings-daemon': free(): invalid pointer" [High,Confirmed] https://launchpad.net/bugs/1397135 [07:10] bonjour seb128 et didrocks [07:10] rsalveti, you miss debug symbols for u-s-d in your bt [07:10] lut pitti, comment ça va aujourd'hui ? [07:10] seb128: yeah, I get this all the time, I needed to downgrade [07:10] bonjour pitti ! moins fatigué qu'hier ? [07:10] I filed it to errors.u.c., but it didn't turn up there yet [07:10] didrocks: oui, j'ai me levé à 5:30, mais je vais bien :) [07:11] couché tôt hier soir j'imagine :) [07:11] nous allons à Dresden ce week-end, pour visiter nos familles [07:11] didrocks: oui, 22h comme d'habitude :) [07:11] pitti: oh, 2 days is enough or you are taking the train and work from there this afternoon ? [07:12] didrocks: the latter; I leave around 11:15 here and work in the train [07:12] I have some systemd debugging to do :) [07:12] heh :) [07:12] pitti: I thought about another use case where presets can be an issue btw, going to write on the ML [07:13] hopefully relaunching the debate of separating distro preferences from /etc/ [07:13] didrocks: btw, it seems we may want the generator in jessie after all? so it needs porting to 215 [07:13] would be nice to have Lennart's opinion on this [07:13] *nod* [07:13] pitti: want me to do that now? should be easy [07:13] didrocks: if you wish; I just uploaded -7, so we have a clear field for new release team requests :) [07:13] didrocks: so please pull master before you rebase [07:14] * didrocks does [07:14] we also have 2 RC bugs, so -7 won't be the last one anyway [07:14] I think the function that was missing was the only one anyway [07:14] *nod* [07:14] * pitti hugs didrocks, the new systemd master [07:14] * didrocks hugs pitti back, the master of all masters, as usual :) [07:14] pitti, I wonder why e.u.c doesn't pick those u-s-d reports [07:14] pitti, I guess yours is not https://errors.ubuntu.com/problem/fb3c4073786721c0e327ff099ccc1ea7666f6cb7 ? [07:15] seb128: no, that looked different; I have an abort in free() [07:15] what I though [07:16] bug 1397135 is mine [07:16] bug 1397135 in unity-settings-daemon (Ubuntu) "Error in `/usr/lib/unity-settings-daemon/unity-settings-daemon': free(): invalid pointer" [High,Confirmed] https://launchpad.net/bugs/1397135 [07:19] pitti, do you have a bt that includes the u-s-d symbols? [07:20] ah sorry, no [07:20] I can probably re-upgrade, get a fresh crash, and upload that to LP [07:20] I just saw the above bug wasn't a "proper" apport one [08:10] moin [09:03] hiya [09:03] FJKong, Have you played with gqrx at all? [09:03] hey dholbach [09:04] Laney, do you know where http://paste.ubuntu.com/9280386/ could be coming from? [09:04] hey willcooke [09:05] hello [09:05] oh good [09:06] it's exploding (and retheming everything in the process of it, like if g-s-d exploded) every minute [09:08] downgrade it [09:08] let me look [09:11] Laney, hey [09:11] Laney, rsalveti and pitti reported similar issues [09:11] yes great, everybody is [09:11] I wonder if that's doing it for everyone, I didn't try to restart my session (or u-s-d) yet [09:11] no [09:11] because I was running it all day [09:11] k [09:11] but get a better trace if you can [09:12] although I wasn't using the archive binaries to be fair [09:17] https://git.gnome.org/browse/gnome-settings-daemon/commit/plugins/power/gsd-power-manager.c?id=6f1a6debd46cdd279bab8692aa7503e1f7ba954b [09:17] well the trace on the bug is in that code [09:17] sooooooo [09:18] did you test on a laptop? [09:21] no [09:21] anyway I have it now, let's just take this code [09:21] that's why [09:21] 0xb387734f in device_perhaps_recall_delay_cb (user_data=0x972d150) [09:21] at gsd-power-manager.c:960 [09:21] yes [09:21] I know, I just said [09:21] is the invalid free [09:21] k [09:22] where's the upstream import for usd? [09:22] upstream "import"? [09:22] "yes" [09:22] lp:unity-settings-daemon is the source [09:22] the bzr branch [09:22] dunno what you mean "import" [09:23] there's one to cherry pick from [09:23] try lp:gnome-settings-daemon [09:24] that seems outdated though [09:24] I don't think we did use proper vcs cherry pick for other changes [09:24] if you have a branch/patch you want tested locally, let me know [09:24] there was a branch, robert set it up [09:28] I'm not sure... is rolling back to https://launchpad.net/ubuntu/+source/unity-settings-daemon/15.04.0+15.10.20141030-0ubuntu1 going to fix it? [09:28] Laney, ok, I don't know about that [09:28] dholbach, yes [09:28] thanks, because this is a bit annoying :) [09:28] it is [09:29] I might just close IRC for a bit [09:29] this is getting distracting [09:29] Laney, checked my IRC log, I don't find reference to robert_ancell's import [09:29] so sorry, can't help on that [09:29] brb [09:29] morning! [09:29] hey larsu, wie gehts? [09:29] hey larsu [09:29] larsu, hippie! [09:30] Laney, feel free to close/ignore IRC any time during the day when trying to get work done, many do it ;-) [09:30] dholbach: selber hippie! [09:30] dholbach: how was the trip? [09:30] seb128: good thanks! And you? [09:30] ah no, no need to restart - unity-settings-daemon restarted itself ;-) [09:30] larsu, I'm good, thanks [09:31] larsu, quite nice, although I'm not quite as refreshed as having slept 8h in a non-moving bed :) [09:31] how about you? [09:31] seb128: mind if I steal your policykit-1 merge? [09:31] dholbach: haha! I'm good as well, thanks :) [09:32] pitti, please do, I didn't intend to merge it anyway, most of the GNOME merges are a waste of efforts [09:32] like they don't bring anything useful [09:32] so I tend to skip them until there is something worth merging [09:32] seb128: this one drops most of our delta, and I want a rebuild anyway [09:32] k [09:41] seb128: https://code.launchpad.net/~laney/unity-settings-daemon/lp1397135/+merge/243127 review please [09:42] Laney, looking [09:42] Laney, did you find the import vcs? [09:42] no, I passed --author to fake it [09:43] Laney, approved [09:45] Laney, robert_ancell had https://code.launchpad.net/~ubuntu-desktop/gnome-settings-daemon/no-submodules [09:45] just found that in some email [09:46] Laney, he wrote that http://paste.ubuntu.com/9280748/ [09:47] ah [09:47] you can do bzr branch on a git checkout? [09:48] I never tried [09:48] the email is maybe buggy ;-) [09:51] * Laney eyes this job [09:51] https://ci-train.ubuntu.com/job/ubuntu-landing-003-1-build/75/console [09:51] what is "Build source package" doing? [09:52] doing a source build of the deb [09:52] so it can dput that to the ppa [09:52] iirc === vrruiz_ is now known as rvr [09:52] k, log refresh [09:52] it just dputed [09:52] ah there [09:53] just slow [09:54] yeah [09:54] dunno why the log didn't update periodically [10:14] willcooke: gqrx? [10:15] FJKong, it's like a simplified gui to Gnu Radio with a few demods already written for you and you just choose [10:15] quite good [10:15] the version in the archive has issues, but there is a ppa with newer versions in [10:15] willcooke: yes, it seems quite good [10:15] then you just need a cheap DVB-T dongle and you're away [10:18] willcooke: +sa5 seems to be good enough to run a full desktop with Xmir replacing Xorg+mir. But it also shows what mir is still lacking. :P [10:18] 10:51 < duflu> mlankhorst: https://bugs.launchpad.net/xmir/+bug/1216468, https://bugs.launchpad.net/unity-system-compositor/+bug/1204505 [10:18] Launchpad bug 1216468 in XMir "Mouse pointer lags behind slightly (still using software cursor instead of hardware)" [High,Triaged] [10:18] Launchpad bug 1204505 in XMir "[enhancement] unity-system-compositor needs to have hw pointer functionality enabled back" [Medium,Triaged] [10:22] cool! Thanks mlankhorst [10:27] dholbach: want to try ppa:ci-train-ppa-service/landing-003 ? [10:28] Laney: the name of the key if org.gnome.desktop.session idle-delay, but gsm-manager.c binds to idle-timeout... [10:28] Laney: was the name changed? [10:30] larsu: isn't idle-timeout the name of the property on the (G)object? [10:31] (from memory) [10:32] Laney: ah, freaking #defines [10:32] Laney: you're right. False alarm [10:32] (sorry) [10:32] np, it's a bit confusing [10:32] can you reproduce this now? [10:33] no, wfm in a test program [10:35] blerg [10:41] sure, let me try [10:46] Laney, seems to work fine AFAICT [10:47] cool beans [10:52] dholbach: thanks for checking [10:52] going to release this now [10:52] Laney, the u-s-d from the ppa works fine [10:53] rock on [10:53] this train is leaving the station [11:00] Laney: got it. FUCK. [11:00] at least I think I do... [11:00] got is reproduced or got is figured out? [11:00] * larsu shakes fist in desrt's general direction [11:00] but then ... I reviewed that patch :/ [11:00] Laney: both [11:00] neat! [11:01] 1. reproduce [11:01] 2. find the issue [11:01] 3. fix [11:01] status: 2 [11:01] why's the gnome-session case different from your minimal one? [11:01] well, fix then explain if you want ;) [11:02] it subscribes to a detailed signal [11:02] if I subscribe to changed::idle-delay, I don't get events at all [11:02] works if I subscribe to changed [11:02] ah [11:03] but you get the initial value yeah? [11:03] yes, this is already in the "correct" case [11:03] g_settings_bind() uses detailed signals... [11:04] ya, makes sense [11:09] great, now my screen turns off after 100ms [11:09] * larsu should have chosen another key to test :D [11:31] Laney: I have two possible fixes, but need to ask desrt which he prefers [11:32] the problem is that g_signal_has_handler_pending() only returns TRUE when both the signal and the detail match [11:32] it doesn't special case 0 as "any detail", it must be no detail [11:32] actually now that I write this down, this might be the sane behavior... [11:35] https://github.com/jefferyto/gedit-control-your-tabs [11:35] \o/ [11:40] larsu - can you tell me... can I change the colour of the active tab in gedit?> [11:42] willcooke: likely, let me check. Are you running V? [11:43] larsu, nah - too chicken, Trusty [11:44] ah, I think I will edit the Cobalt theme, since that's what I like [11:44] willcooke: you could have tried overriding the css in the inspector then [11:45] ZOMG [11:45] There's a bleedin "Color (spelt wrong) Scheme Editor" [11:45] oh, but I don't think tabs are covered there [11:46] no... [11:46] you have to override the gtk theme [11:46] which is a bit of a pain tbh [11:46] ack [11:46] but doable [11:46] How do we go about getting changes in there by default? [11:46] Do we have to get the OK from design? [11:46] this works: '.notebook tab:active { background-color: red; }' [11:47] Because, IMHO, having the active tab very nearly the same as an inactive tab is wrong [11:47] I agree [11:47] let's do it then :) [11:47] red active tabs \o/ [11:47] I'll clear it with JohnLea [11:47] ;) [11:47] haha [11:53] changing the shade to 0.52 works for me [11:53] thanks larsu [11:53] np [11:53] Laney: this fixes it http://paste.debian.net/plain/133949 [11:53] not sure if we shouldn't change g_signal_has_handler_pending() instead, though [11:54] this is actually a problem in a few other places as well (application, gsimpleaction) [11:54] look at this, all desrt code! :P [11:57] why's it a problem there too? [11:57] or you mean your fix fixes the same issue elsewhere [12:00] because it checks there for subscribed handlers with a 0 detail, too [12:01] if you are subscribed to a detail, the check will fail [12:01] the patch I linked to circumvents this by checking both cases, but this only works because we know which key the user is asking for in g_settings_get [12:02] you can't know that in all cases, and checking _all_ details seems bad [12:02] so, I think passing 0 as detail to has_handler_pending() should mean "no detail or any detail" [12:02] not sure if that's too much of an ABI break though === alan_g is now known as alan_g|lunch === MacSlow is now known as MacSlow|lunch [12:41] seb128: did you get my mail about the 4.2.7+/trusty and 4.3.4/utopic updates? [12:48] is anyone of you running vivid already? do you have some window management / wrong window having focus issues too? [12:49] yes, but this has been a problem for a while, no? [12:50] Trevinho: ^^ ;) === alan_g|lunch is now known as alan_g [13:03] Sweet5hark1, hey, yes, I was on vac yesterday, I've that in my backlog [13:03] dholbach, larsu: unity/compiz didn't change a lot recently afaik, didn't notice any focus issue here [13:04] in what cases does it happen? [13:13] larsu: mh, what specifically? I'm not in vivid, but I didn't see many WM issues before [13:14] willcooke: ok last update for me today, had a stupid bug that broke glxgears when using xmir as replacement for xorg, and i made screen blanking work [13:14] afk a bit [13:14] mlankhorst, coolio! === MacSlow|lunch is now known as MacSlow [13:49] seb128, Trevinho: for example, switching workspace to one with only one window doesn't focus that window [13:50] larsu, wfm, how do you switch workspace? was that one window having focus before you moved out of that workspace? [13:50] mh, there has been a community contribution about that [13:51] seb128: yes, it was. in fact, seems that refocussing the last focussed window on a workspace doesn't work reliably [13:51] seb128: it's one of those things that works 80% of the time [13:51] never saw that issue [13:51] the remaining 20% I type gibberish into a wrong window ;) [13:51] I bet it's more complex than that [13:51] like you might have wins overlapping on 2 workspaces or something [13:52] the tricky part is to determine was in different in the case where it gets it wrong [14:08] seb128, in System Settings -> Security & Privacy -> Diagnostics [14:08] there is an option "Send occasional system information to Canonical" [14:08] "This includes things like how many programs are running, how much disk space the computer has........" [14:08] willcooke, phone or desktop? [14:08] seb128, dednick [14:09] oops sorry dednick ignore [14:09] seb128, desktop [14:09] Do you know what that is? What runs? What info it collects? [14:09] Can't find anything of Google [14:11] *on [14:11] willcooke, it's whoopsie [14:11] seb128, thanks! [14:11] seb128, so what is "Send error reports...." is that apport? [14:11] willcooke, https://wiki.ubuntu.com/ErrorTracker [14:11] willcooke, https://wiki.ubuntu.com/ErrorTracker#Invitation_for_metrics_collection [14:12] is that dialog implemented? [14:12] not that I know [14:12] no, dont think so [14:13] just a tick box [14:13] but under the dialog there is the bit about the control center [14:13] ya [14:13] larsu: hello! [14:13] I don't know what metrics whoopsie gathers either [14:13] desrt: so ... maybe we should make g_signal_has_pending_handlers() do the right thing when passing 0? [14:13] willcooke: ev would be one to ask [14:13] larsu: i was thinking about that [14:13] larsu: or at least document it more explicitly [14:13] as in, return TRUE if detailed signals are connected [14:13] seb128, yeah, that bit of text is pretty vague [14:13] thx seb128, Laney [14:13] willcooke, Laney, I'm not even sure metrics are implemented/what they are, https://launchpad.net/ubuntu/+source/whoopsie-daisy/0.1.10 [14:13] larsu: but truth be told the existing behaviour is logical and consistent [14:13] even if not expected [14:14] desrt: not sure how much of an ABI break that would be... [14:14] willcooke, Laney, that has " * Remove the metrics preferences, since this does not exist." [14:14] willcooke, can you ask on #ubuntu-devel to ev and bdmurray? or want me to do that? [14:14] larsu: it answers the question "if i emitted a signal wuth these ... uh... details.... would it be handled?" [14:14] seb128, s'scool - StephaneVerdy wants to know, so I can put him in touch with ev [14:15] willcooke, well I'm interested by the reply, so asking on #ubuntu-devel would be useful [14:15] desrt: right. The problem is that we might want to check for connected handlers when we don't know the detail [14:15] seb128, kk [14:15] desrt: it works great in the gsettings case, as we do it on a _get( [14:15] larsu: i'd suggest another function for this purpose [14:15] willcooke, it might be that there is no backend behind this control, in which case we should remove it from the UI [14:15] willcooke, and if there is a backend I would still like to know what's the difference between the metrics and the reports [14:15] seb128, +1 [14:15] larsu: i think the behaviour of the existing one does make a good deal of sense -- but we could use a clarifying sentence in the docs [14:15] desrt: ya, proabably better. Then we also don't break anyone [14:16] i'm also not into changing an API in an API-stable library just because the maintainer of that library made a mistake when using it once [14:16] seb128, waiting for stephane to join #u-d [14:16] desrt: right. Want me to add that function or should we wait until we have a use case? [14:16] let's wait [14:16] i'll add a clarification to the docs [14:17] desrt: ok. thanks for the review [14:17] desrt: reverted? [14:17] how did you find the bug, btw? [14:17] larsu: ya... we're going to fix this the 'proper' way, remember? [14:17] desrt: ah, right. [14:17] once someone reviews my signal connection notify patches..... [14:17] desrt: vfuncs on gobjectclass? [14:17] ya [14:17] nice! [14:17] which i already start to think are slightly odd [14:17] desrt: Laney found it [14:18] since you can connect signals on non-gobjects [14:18] but whatever [14:18] anyone else's settings daemon crashing in a loop? [14:18] upgrade [14:18] desrt: like people do that [14:18] Saviq, yes, was fixed this morning [14:18] seb128, ah, was just about to try and upgrade [14:18] :-) [14:18] Laney: do you need this fix pushed on something other than master? [14:19] no [14:19] it's a bit difficult to focus when stuff's jumping around on me ;) [14:19] can't upload again until ppc64el is fixed, though :) [14:19] yeah... [14:19] morning desrt! [14:19] at least, we know who is using vivid and who is not ;) [14:19] Laney: okay, pushed to master. Thanks for pointing it out! [14:20] larsu: just feels a bit inconsistent [14:20] thanks for fixing [14:20] ok let's hope this was the last crash then [14:20] yeah [14:20] * Saviq wonders why `restart unity7` results in all windows killed when unity restarts, as opposed to `pkill compiz` [14:20] the entire way gsignal works is 'bolted on the side' so it sort of feels like this ought to be as well [14:20] desrt: fair enough, but let's be practical about this... [14:20] ie: some sort of g_signal_set_notify_callback() [14:21] hm [14:21]