[04:58] <pitti> Good morning
[05:05] <jibel> good morning
[08:03] <Laney> hello!
[08:04] <seb128> good morning desktopers
[08:04] <seb128> hey Laney
[08:04] <Laney> hey seb128
[08:04] <Laney> did you have a good weekend?
[08:06] <mlankhorst> morning
[08:06] <seb128> Laney, quite good thanks, pretty uneventfull and relaxing ;-) you?
[08:07] <Laney> it was surprisingly hot, so spent some time outside making the most of that
[08:07] <mlankhorst> yeah weekend was nice :P
[08:07] <mlankhorst> 15°c and all
[08:07] <seb128> nice
[08:08] <seb128> it was not cool here, but not hot either
[08:08] <seb128> like 16-18°C
[08:08] <Laney> went climbing and then to the market, then yesterday played carcassonne in the pub
[08:08] <seb128> but they say it might go up to 23°C this week
[08:08] <seb128> let's see
[08:08] <seb128> nice ;-)
[08:08] <Laney> I got the inns and cathedrals addon on Saturday :P
[08:09] <Laney> hello mlankhorst!
[08:09] <Laney> hoe gaat het?
[08:10] <mlankhorst> goed
[08:10] <mlankhorst> I got some biking done :)
[08:10] <Laney> nice
[08:10] <Laney> haven't been out on my road bike in a while
[08:10] <Laney> keep going climbing instead, since i got a season ticket for the centre :S
[08:11] <mlankhorst> and a photo http://imgur.com/9ocLd2h :D
[08:12] <Laney> nice
[08:18] <Mirv> sil2100: telephony-service new dependencies MP on the stack status page
[08:18] <sil2100> Mirv: looking! Thanks
[08:18]  * sil2100 is happy to see we're still using that
[08:19] <Mirv> I'm, at least, not sure if anyone else ;)
[08:22] <Mirv> sil2100: another one https://code.launchpad.net/~timo-jyrinki/cupstream2distro-config/camera_app_depends_on_qtdeclarative5-usermetrics0.1/+merge/188274 - I believe the failing test is still lurking after that (should ping bfiller about it)
[08:24] <Mirv> sil2100: and thanks for the first
[08:30] <didrocks> sil2100: hey! do you mind answering to Thomi about the opened bugs?
[08:30] <sil2100> didrocks: hello! Ok, see the e-mails
[08:30] <didrocks> sil2100: thanks!
[08:32] <mlankhorst> Laney: yep that horse was less nice yesterday though, bucking in all gaits. :P But the most likely explanation was that I messed up somehow, the problem is usually seated on the saddle..
[08:32] <didrocks> sil2100: joining #ubuntu-ci-eng?
[08:32] <didrocks> sil2100: and https://plus.google.com/hangouts/_/b31c28f31fcf9e093dc094c78119b1080db93ff7
[08:51] <Laney> what's the project for the touch greeter?
[08:51] <Laney> Want to check if StatsWelcomeScreen exists in it
[08:55] <Laney> ah
[09:24] <Sweetshark> Moin!
[09:25]  * Sweetshark survive LibreOffice conference in Milan. What a treat!
[09:26] <Laney> hey Sweetshark
[09:26] <Laney> seb128: have you seen this behaviour: http://paste.ubuntu.com/6174839/ ?
[09:26] <Laney> i.e. energy seems to be wrong (disagreeing with percentage)
[09:27]  * Laney switches it to use the indicator's value as that is correct
[09:32] <seb128> Laney, no, seems like an upower bog
[09:33] <seb128> Laney, the issue is that qtsystems doesn't wrap the % property
[09:33] <Laney> I remember you filed some but I didn't know if that was one of them
[09:33] <Laney> I printed out the values used to work out the % and they are energy and energy-full from upower
[09:33] <Laney> seems the bug comes from there
[09:33] <seb128> upower has a bit more smartness for buggy devices to get a correct %
[09:33] <pitti> right, it has a few heuristics
[09:34] <pitti> but if the kernel exports energy or charge, it usually uses that
[09:34] <pitti> Laney: can you check the attributes in /sys/class/power_supply/whatever/ ?
[09:34] <seb128> pitti, hey, wie gehts?
[09:34] <pitti> Laney: grep -r . /sys/class/power_supply/ might be insightful
[09:34] <pitti> seb128: gut, danke! und Dir?
[09:34] <seb128> pitti, zehr gut, danke ;-)
[09:34] <Laney> one second, my desk is falling apart
[09:34] <Laney> but yes
[09:37] <Laney> pitti: http://paste.ubuntu.com/6174879/
[09:39] <pitti> Laney: urgh
[09:39] <pitti> Laney: charge_now/charge_full == 109%
[09:40] <pitti> Laney: I recently fixed upower to prefer reading "capacity" over charge/energy for the percentage value
[09:40] <pitti> so GUIs should generally prefer showing the percentage property
[09:40] <Laney> yeah
[09:40] <Laney> capacity is right, seems that the raw values can be buggy
[09:40] <seb128> pitti, the issue is that qtsystems doesn't wrap that property
[09:40] <Laney> the indicator exposes it
[09:40] <seb128> I've a todo to add it there
[09:41] <Laney> MP to show that one incoming
[09:41] <seb128> Laney, right, I the time I wrote that code we had no indicator :p
[09:41] <seb128> Laney, I wonder if we should make the wifi toggle use the indicator backend as well while we are at it
[09:41] <Laney> it does
[09:42] <Laney> oh no
[09:42] <Laney> that was bt
[09:42] <seb128> right
[09:42] <seb128> the current code doesn't do dynamic updates
[09:42] <Laney> yeah could do that
[09:43] <seb128> thanks
[09:43] <seb128> Laney, btw did you say you could change the checkbox widgets, or should I look at that?
[09:43] <Laney> Can do that next
[09:45] <seb128> ok, I'm going to let it for you
[09:45]  * seb128 goes to try the cmake work
[10:11] <Laney> seb128: Just checked, there doesn't seem to be an action on the indicator for global wifi toggle
[10:11] <Laney> there's only  'wlan0.device-enabled': (true, '', [<true>])
[10:11] <seb128> hum, ok
[10:12] <Laney> maybe they could expose one
[10:15] <seb128> Laney, ideally that's what they would do, I guess the indicator is supposed to turn wifi off as well
[10:16] <Laney> it does
[10:16] <Laney> but it's somehow given the device
[10:17] <seb128> it might be good enough of an approximation for v1.
[10:17] <seb128> ?
[10:18] <Laney> so use NM to get the device name?
[10:18] <Laney> on my laptop the wireless adaptor is called eth1 for some reason
[10:19] <seb128> well, the indicator should probably do what we do
[10:19] <seb128> e.g use the nmclient api to turn wifi on/off
[10:19] <seb128> that has the smartness required iirc
[10:19] <Laney> oh like it already does
[10:52] <didrocks> seb128: mind giving it a look? https://code.launchpad.net/~didrocks/ubuntu-system-settings/move-to-async/+merge/188295
[10:53] <seb128> didrocks, looking
[10:53] <didrocks> thx
[10:57] <seb128> didrocks, does that fix any issue or just cleanups?
[10:57] <didrocks> seb128: I think that way people will stop complaining that the "download" button stay pressed while the daemon is starting
[10:57] <didrocks> (I infer that's the issue)
[10:58] <seb128> oh, right
[10:58] <seb128> didrocks, that makes sense ;-)
[10:58] <seb128> didrocks, thanks
[10:58] <didrocks> seb128: not 100% sure, I don't have any update to process ;)
[10:58] <didrocks> yw!
[10:58] <seb128> I can try in a bit, need to charge my device more before though
[10:58] <didrocks> well, anyway, it can only improve
[10:59] <seb128> we still have suspend issues, it went flat during the w.e
[10:59] <didrocks> yeah, it happens sometimes to me as well
[10:59] <didrocks> or you can see the screen is still on
[11:08] <czajkowski> does anyone use workspaces?  Are they working for you after latest updates?  I've them enabled and can see them on the side bar clicking on the icon on the side bar I cant zoom out to the desktops but it is showing I've 4 enabled
[11:11] <seb128> wfm
[11:16] <czajkowski> bah
[11:16] <czajkowski> seb128: are you sure
[11:17] <seb128> sure yes
[11:18] <czajkowski> time to file a bug :(
[11:19] <czajkowski> what are workspaces filed against?
[11:21] <seb128> compiz I guess
[11:22] <czajkowski> cool
[11:27] <czajkowski> https://wiki.mongodb.com/display/mrkt/Conference+Reviews
[11:27] <czajkowski> bah
[11:27] <czajkowski> god damn right click
[11:27] <czajkowski> https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1233112
[11:58] <mdeslaur> seb128: hi! would you object to something like this: bug 1232589
[11:58]  * mdeslaur looks for bug bot
[11:58] <mdeslaur> LP: #1232589
[11:58] <mdeslaur> meh
[11:59] <seb128> mdeslaur, hey, looking
[11:59] <seb128> no object
[11:59] <seb128> no objection
[12:00] <seb128> check with Laney though
[12:00] <seb128> it's ffish
[12:00] <mdeslaur> yes, definitely needs a ffe
[12:01] <Laney> don't ping me directly, subscribe ubuntu-release please
[12:01] <Laney> personally I'd be happier if it were forwarded
[12:01] <mdeslaur> isn't it a bit ubuntu-specific for upstream to accept?
[12:02] <Laney> don't know, they might
[12:03] <mdeslaur> ok, I'll file an upstream bug and see
[12:04] <Laney> otherwise it's a patch to maintain, so we have to consider whether that is worth it
[12:05] <mdeslaur> I think so :)
[12:48] <desrt> good morning fellow canonical employees!
[12:48] <mlankhorst> heya
[12:49] <seb128> desrt, good morning ... are you part of the group for good?! ;-)
[12:49] <desrt> seb128: still haven't signed the contracts since they had a couple of mistakes when they sent them over, but today is my start day :)
[12:49] <seb128> desrt, welcome on board! ;-)
[12:50]  * desrt spent the weekend telling everyone "i'm between jobs right now..."
[12:50] <desrt> (north american euphemism for 'unemployed')
[12:50] <seb128> lol
[12:50] <pitti> hah
[12:50] <pitti> hey desrt, how are you?
[12:51] <desrt> pitti: good.  probably not as good as you, though :)
[12:51] <desrt> did you have lots of awesome spicy cajun food?
[12:51] <pitti> desrt: I did two weeks ago, yes :)
[12:51] <czajkowski> desrt: greetings from a non canonincal employee :)
[12:51] <desrt> czajkowski: were you former-canonical?
[12:52] <czajkowski> desrt: I was canonical but now I'm not but everyone is here even if you're are or aren't :)
[12:52] <desrt> sometimes you wanna go....
[12:52] <czajkowski> so far seb128 and didrocks havent strangled me for asking bug questions so I'm staying around!
[13:12] <seb128> desrt, btw, about that treeview bug, do you think I should just take your patch or do you want to try to get some upstream review first?
[13:13] <desrt> seb128: i pinged around a bit upstream about it.  nobody wanted to look
[13:13] <desrt> will try to flag down company again today
[13:13] <desrt> if it fixes an issue that we're having right now, though, i say you should take it
[13:13] <seb128> desrt, ok, I'm going to test build/install it, to see if I spot any issue with it
[13:13] <desrt> i'm pretty sure it won't have negative side effects
[13:13] <desrt> let me double-check that, though
[13:13] <seb128> ok
[13:13] <seb128> well, I'm going to test build/install it here anyway
[13:13] <seb128> then ping you again before uploading
[13:14] <desrt> ya.... i'm really sure it won't cause issues
[13:14] <desrt> that variable is used only in a half-dozen places and in all of them, 0 is a better choice for default than -1
[13:24] <desrt> seb128: okay.  the patch is on master and gtk-3-10 now
[13:24] <seb128> desrt, \o/
[13:24] <seb128> desrt, thanks
[13:24] <desrt> np
[13:25]  * desrt enjoys making the minimal amount of effort possible, then magnifying it
[13:25] <desrt> by merging to master _and_ stable, i can consider my 2-character patch as if it were a 4-character patch
[14:41] <seb128> Laney, sorry for the wifi buggy review, pbkac
[14:41] <Laney> heh
[14:41]  * seb128 tried the wifi panel :p
[14:41] <Laney> so it works?
[14:41] <Laney> haha
[14:41] <seb128> yes,in battery
[14:41] <seb128> it's buggy in wifi
[14:41] <seb128> but that's a bug for ted I guess
[14:41] <Laney> didn't look what they do
[14:41] <seb128> (or nick/lars if that's qmenumodel)
[14:42] <Laney> I didn't check my one on device
[14:42] <Laney> not sure what the wifi toggle there does with the NM setting
[14:42] <seb128> Laney, so, doing the Q_EMIT lets the qml side to call the getter for an update?
[14:42] <Laney> yeah
[14:42] <seb128> cool
[14:42] <Laney> it tells QML to go fetch the value again
[14:43] <seb128> ok, on that one done, I'm out for some exercice
[14:44] <seb128> not like friday where I did "just another thing" on 5 things and end-up going after 6pm when it was starting being not sunny anymore, and cold
[14:44] <seb128> be back in ~1h
[15:45] <didrocks> seb128: once you are back: https://code.launchpad.net/~didrocks/ubuntu-system-settings/add-unknown-progress-bar/+merge/188373
[15:45] <didrocks> that is to make some meetings useful ;)
[15:46] <didrocks> jasoncwarner: FYI ^ (just tested it on my phone after downgrading and building)
[15:46] <mterry> attente, does the keyboard indicator in u-g today (saucy) work?  Like, without your new indicator branch, will keyboard layouts in the greeter be busted?
[15:49] <attente> mterry, it will work, it's just the problem with switching to the active user's first layout that's not fixed
[15:52] <mterry> attente, no, right.  I meant before that branch.  Like what we have in saucy (not trunk)
[15:57] <attente> mterry, what we have there in saucy right now works
[15:59] <mterry> attente, OK, cool.  That takes some of the urgency off
[16:00] <seb128> didrocks, thanks
[16:01] <didrocks> yw
[16:04] <seb128> ok, I need to drop offline for 10 minutes or so
[16:04] <seb128> bbiab
[16:06] <sil2100> kenvandine: ping!
[16:06] <sil2100> kenvandine: do you have a moment? https://code.launchpad.net/~sil2100/thumbnailer/packaging_review/+merge/188379
[16:06] <sil2100> kenvandine: didrocks will double-check it later once it's in
[16:06] <sil2100> kenvandine: standard changes ;)
[16:11] <kenvandine> sil2100, sure
[16:11] <sil2100> kenvandine: thanks! :)
[16:12] <sil2100> kenvandine: since if we'll be able to get it merged soon, Didier will preNEW it then ;)
[16:12] <sil2100> Before going EOD
[16:14] <kenvandine> sil2100, done
[16:15] <sil2100> kenvandine: QUICK! Thanks ;)
[16:15] <kenvandine> it was an easy one :)
[16:16] <kenvandine> i didn't review all the packaging... just the changes :)
[16:24] <Laney> dpm: yo
[16:24] <Laney> dpm: have you seen https://bugs.launchpad.net/ubuntu-system-settings/+bug/1215712 before?
[16:26] <dpm> hey Laney, I hadn't, no. but if I understand it correctly, the fix is to set the singular to %1 instead of 1
[16:26] <dpm> so                 value: i18n.tr("%1 minute",
[16:26] <dpm>                                "%1 minutes".arg(5),
[16:26] <dpm>                                5)
[16:26] <Laney> oh I see
[16:27] <Laney> makes sense
[16:28] <dpm> but I think the SDK requires does something not very intuitive with plurals, give me a sec to double-check this is the right format
[16:28] <Laney> it comes up right in the pot
[16:29] <dpm> yeah, but the gettext tools should flag it as incorrect, which is what LP is doing (it uses the standard gettext tools for validation). Not sure why it didn't get flagged as incorrect during build
[16:33] <Laney> ah
[16:36] <dpm> Laney, so the format should be -> i18n.tr("%1 minute", "%1 minutes", val).arg(val)
[16:37] <dpm> there is a bug in the SDK requesting the .arg(val) not to be necessary, but for now it's still needed
[16:38] <Laney> oh I think we have the .arg in the wrong place then
[16:38] <dpm> yeah, just noticed that
[16:39] <Laney> bleh
[16:39] <Laney> let me fix
[16:42] <om26er_> Laney, hey who works on the brightness panel in the system-settings app ?
[16:42] <Laney> om26er_: nobody
[16:42] <Laney> it is deferred
[16:42] <om26er_> :O
[16:42] <om26er_> Laney, rather battery I meant
[16:42] <om26er_> since that panel has a brightness slider
[16:42] <Laney> various people
[16:42] <Laney> what's the problem?
[16:42] <om26er_> bug 1233274
[16:43] <om26er_> https://bugs.launchpad.net/ubuntu-system-settings/+bug/1233274
[16:43] <Laney> yeah that's a known bug in qmenumodle
[16:43] <Laney> s/le/el/
[16:43] <Laney> I think larsu has a fix
[16:43]  * om26er_ assigns larsu 
[16:43] <om26er_> Laney, thansk
[16:43] <om26er_> *thanks
[16:44] <Laney> https://code.launchpad.net/~larsu/qmenumodel/maintain-action-state-type/+merge/187100
[16:44] <larsu> om26er_: already fixed :)
[16:44] <larsu> Laney: ha thanks
[16:44] <Laney> om26er_: feel free to test it
[16:44] <Laney> / review ;-)
[16:45] <larsu> I've linked the bug
[16:45] <om26er_> there are debs attached with the CI message I can test
[16:45] <larsu> seb said he'll do a review to when he has time - but feel free to do one if you get around to it earlier
[16:45] <Laney> be nice to get it merged
[16:46] <larsu> right
[16:56] <seb128> back
[16:57] <seb128> (sorry was offline a bit longer than expected, power was down for some work in the building)
[16:57] <Laney> admit it, you went and had a nap
[16:57] <seb128> lol
[16:57] <seb128> Laney, yeah, I found a bug in your wifi changes during the nap btw :p
[16:57] <Laney> NO YOU DID NOT
[16:57] <seb128> Laney, I can't enable wifi from battery anymore
[16:57] <seb128> the callback is called 4 times when I click on enable
[16:57] <seb128> I guess it does a enable->disable loop
[16:57] <Laney> oh is there a loop
[16:57] <Laney> bah
[16:58] <Laney> qml sucks for that stuff
[16:58] <Laney> did it get merged already?
[16:58] <seb128> yes :/
[16:58] <seb128> Laney, do you want a bug report to track it?
[16:58] <Laney> oh well
[16:58] <Laney> i'll look now
[16:59] <seb128> ok, let me know if need one, or if you get a mr to fix it up
[16:59] <seb128> well, first let me know if you confirm the issue
[16:59] <Laney> I didn't get it in testing
[16:59] <Laney> deliberately tried to make it happen too
[17:00] <seb128> hum
[17:00] <Laney> what's the steps?
[17:01] <didrocks> 17:45:07   didrocks | seb128: once you are back:
[17:01] <didrocks>                     | https://code.launchpad.net/~didrocks/ubuntu-system-settings/add-unknown-progress-bar/+merge/188373
[17:01] <didrocks> 17:45:16   didrocks | that is to make some meetings useful ;)
[17:01] <Laney> https://ubuntuone.com/2O2VxjFNymTlCgxYWRDaN2 hrhr
[17:01] <didrocks> 17:46:01   didrocks | jasoncwarner: FYI ^ (just tested it on my phone after downgrading and building)
[17:01] <didrocks> seb128: now that you are back ^ ;)
[17:02] <seb128> didrocks, yeah, I read the ping before being offline, reviewing that now
[17:02] <didrocks> ah, great! thanks :)
[17:02] <seb128> Laney, steps for me are: run "system-settings battery"; click on the wifi switch -> it turns off, try to click on it again to turn it back on
[17:03] <Laney> hmm, no, can't get it to happen
[17:04] <seb128> :/
[17:05] <seb128> hum, also clicking on bluetooth makes the bluetooth switch vanish from the panel
[17:05] <seb128> but I guess that's an indicator-bluetooth issue for charles
[17:05]  * didrocks waves good evening
[17:05] <Laney> yeah I think that's known
[17:05] <seb128> didrocks, night
[17:05] <Laney> night didrocks
[17:05] <didrocks> seb128: thanks, you too!
[17:05] <didrocks> bye Laney
[17:09] <charles> seb128, the bluetooth indicator is supposed to hide when bluetooth is disabled
[17:09] <seb128> charles, how is one supposed to enable bluetooth back then?
[17:09] <charles> seb128, through settings
[17:10] <seb128> it's pretty un-intuitive ... did you try to discuss that with mpt before?
[17:10] <charles> seb128: you mean, is he aware of it? it was his idea
[17:10] <charles> https://wiki.ubuntu.com/Bluetooth#Indicator_and_menu
[17:10] <Laney> seb128: try lp:~laney/ubuntu-system-settings/battery-dynamic-wireless-fix
[17:10] <seb128> well, did anyone mentioned to him that it's a pretty confusing behaviour?
[17:11] <charles> seb128: no, I don't think that conversation's happened yet. :)
[17:11] <seb128> charles, I'm sort of starting it :p
[17:11] <Laney> seb128: gtg, but feel free to mp/approve that if it works for you or i'll do it tomorrow
[17:12] <seb128> Laney, ok, did you find an issue?
[17:12] <Laney> no
[17:12] <seb128> Laney, looking to that in a minute
[17:12] <Laney> I just changed approach
[17:12] <Laney> copied what I did for the action toggles
[17:12] <Laney> it works there to avoid loops
[17:13]  * Laney waves
[17:14] <seb128> Laney, yep, that works
[17:16] <Laney> seb128:  still here, let me MP it quickly then ;-)
[17:16] <seb128> Laney, thanks ;-)
[17:17] <Laney> done
[17:17] <Laney> bonne nuit
[17:18] <seb128> Laney, night ;-)
[17:43] <seb128> charles, so one issue due to the bluetooth indicator behaviour, is that the system settings control (we reuse the indicator one over qmenumodel) vanish when toggled ... do you think we should create a new profile with that widget only for the settings (and never hide it there)?
[17:46] <charles> seb128, let me take a look at it. My first guess is it might be better to make an item in the same profile that we just never add to the indicator's menu
[17:46] <charles> seb128: I'm not completely sure that would work, but I'd prefer to try it first over creating a new profile just for this
[17:46] <seb128> charles, that makes sense indeed
[17:47] <charles> seb128, I should have time to look at it this afternoon
[17:47] <seb128> charles, excellent
[17:47] <seb128> charles, should I open a bug report to track the issue?
[17:48] <charles> seb128: yes, please
[17:48] <seb128> charles, ok, need to go for dinner but I'm doing that once I'm back
[17:49] <charles> seb128, k
[18:15] <nessita> hello everyone! so, today being Sept 30, I see a bug in the calendar (this is a saucy updated system). Screenshot is: http://ubuntuone.com/1fkmo9FMrWrFNqTt2ksfEv (calendar shows Oct 30 instead)
[18:22] <sarnold> nessita: I don't think the highlighted date is supposed to mean anything, it's never been right for me on 13.04 anyway.
[18:22] <sarnold> (today my September 24 is highlighted. Go figure.)
[18:23] <nessita> sarnold, never ever? is there a bug report I can +1?
[18:23] <sarnold> nessita: hrm, dunno, I haven't gone looking. it -would- be nice if the highlighting meant something though..
[18:25] <nessita> sarnold, it used to highligth the current date :-) (which is what I expected, and what it seems like is trying to do)
[18:25] <nessita> it got the day right but the moth off by one
[18:25] <sarnold> nessita: ha! here's one from two and a half years ago: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/750992
[18:26] <sarnold> nessita: since I always have a terminal handy, I just run 'cal' when I want to see the current date in a calendar. cal always works. :)
[18:30] <sarnold> nessita: interesting, looks like folks were hoping it'd be fixed by oneiric :)  https://bugs.launchpad.net/indicator-datetime/+bug/837440
[18:30] <nessita> sarnold, indeed, reading all the chain duplicates
[18:31] <seb128> nessita, hey
[18:32] <seb128> nessita, I can't confirm that, are you sure you just didn't click on the next month arrow by error?
[18:32] <seb128> nessita, in any case, charles is maintaining that codebase, so maybe check with him what info would be useful in a bug report
[18:33] <mdeslaur> seb128: I see that issue all the time, FWIW
[18:33]  * charles looks at the scrollback
[18:33] <seb128> mdeslaur, the wrong month one?
[18:33] <nessita> seb128, 100% sure I did not click in the date. I just clicked on the indicator to see the whole calendar month, and the Oct 30 was selected
[18:34] <nessita> charles, hello! so, indicator calendar is playing tricks with my head, see http://ubuntuone.com/1fkmo9FMrWrFNqTt2ksfEv
[18:34] <mdeslaur> seb128: the highlight is set to some other date...perhaps the last time I looked, or something
[18:34] <seb128> mdeslaur, does it happen if you stop the service/on login?
[18:34] <sarnold> I've thought before "last time I've looked" but I'm 90% certain I've seen dates in the future seleceted as well.
[18:34] <mdeslaur> I'll check next time
[18:35] <charles> yes, I think that's a 13.10 regression. previously it would always reset to the current date when you popped down the indicator
[18:35] <charles> now it sticks on whatever date you were last looking at
[18:35] <seb128> charles, well, nessita seems to say she never looking at this month/date
[18:35] <seb128> but maybe it's a click error or something
[18:35] <charles> because the indicator never knows anymore when it's been popped down or popped up
[18:36] <charles> seb128, given that it's exactly one month off, my guess is an accidental click on the 'next month' button in the calendar
[18:36] <seb128> yeah, same here
[18:36] <charles> or rather, nessita I'm aware of the not-jumping-back-to-today bug, but I haven't seen a random jump bug before
[18:37] <seb128> nessita, can you kill indicator-datetime-service and see if that's still happening?
[18:37] <nessita> seb128, yes, on it now
[18:37] <charles> the former is already ticketed and on my TODO. if the latter is repeatable, please file a ticket for it
[18:37] <sarnold> charles: I'm pretty sure that indicator has never bee nright for me on 12.04, 12.10, or 13.04 either...
[18:37] <nessita> charles, I never opened calendar today, in this session. I just opened it and got the Oct 30 highligthed
[18:39] <nessita> seb128, when killing the service (I had to "kill" it 3 times to have it really dead), if I click on the datetime indicator, I see a "disabled" calendar (grey out) with the correct date selected
[18:39] <charles> sarnold, is there a bug from the 12.04 timeframe on this?
[18:40] <sarnold> charles: I haven't filed one, since it never worked I assumed it wasn't meant to work. :/ sorry.
[18:40] <charles> heh
[18:40] <mdeslaur> lol
[18:40] <charles> sarnold: are you using unity in 12.04?
[18:40] <sarnold> (like I said, 'cal' is always ready-at-hand and never wrong..)
[18:40] <sarnold> charles: no, 13.04 no
[18:41] <sarnold> s/no /now /  :)
[18:41] <charles> unity triggers the about-to-show event to the indicator which used to make the indicator jump to today
[18:41] <charles> the reason it's regressed in the nightlies now is because the new indicators don't have the same mechanism, we're not using gtk at that level anymore
[18:41] <mdeslaur> 1990's linux user doesn't file bugs for gooey applications
[18:41] <seb128> nessita, hum, weird, it should autorespawn :/
[18:42] <charles> so, if this bug existed before this cycle, maybe it was in the applet-panel which didn't trigger that even for the calendar to see?
[18:42] <sarnold> mdeslaur: and what's with these kids on my lawn? they are magnetically attracted to it, I swear.
[18:42] <nessita> seb128, let me restart the session to try to reproduce from scratch. I also installed a bunch of updates today, so will restart the system
[18:42] <charles> anyway, IMO the repeatable known regression in the nightlies is the first thing to fix
[18:42] <sarnold> agreed
[18:43] <seb128> nessita, ok
[18:43] <sarnold> that way when it works for me in a few weeks it'll be a pleasant surprise :)
[18:43] <charles> sarnold: there's already a ticket for this filed by alesage I believe. I don't have a URL handy and am about to run out to lunch, but you may want to look it up and CC yourself on it
[18:43]  * nessita reboots
[18:44] <charles> sarnold: and if the problem persists after that fix, let me know
[18:52] <nessita> seb128, charles: rebooted and the calendar shows the correct date :-/ will keep an eye on reproducing
[18:53] <seb128> nessita, well, you probably triggered the next month in some way
[18:53] <nessita> seb128, I guess, though I can not think of any action that could have done that
[18:55] <seb128> nessita, keyboard or mouse click
[18:56] <nessita> seb128, right, I'm pretty sure all I did was clicking on the date in the indicator area
[18:56] <nessita> but since I can't reproduce... :-)
[18:57] <nessita> will be alert in case the date is not "today" in any future usage of the indicator
[18:57] <seb128> nessita, well, if you missclick the date and hit one of the next month, it goes there
[18:57] <nessita> right