karpathy / ulogme

Automatically collect and visualize usage statistics in Ubuntu/OSX environments.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

__LOCKEDSCREEN didn't catch a thing (Yosemite). 'loginwindow' did

jrub opened this issue · comments

Tried ulogme for two days in MacOsX Yosemite. Most events were into "MISC", and even after customizing my render settings, I observed MISC was still big. Then discovered loginwindow event was captured instead of __LOCKEDSCREEN.

Not sure if it has something to do with any custom Mac config? In fact I usually put my Macbook to sleep while having lunch, and loginwindow was registered on that time... also the Mac was warm when returning from lunch, which makes me think that ulogme prevented it of going to sleep (this is not confirmed, though. I need more testing). Anyway, I got that loginwindow event and none of __LOCKEDSCREEN.

PS: congrats for the tool, I love it 😉

Thanks for the report! I haven't written the OSX parts since I work on a Ubuntu machine, so I'm not very familiar with the code there.

Is this fixable on your end by tuning the config? Or is this something that is breaking your experience? I'm not sure about what the fix would be right now.

Well, adding {pattern : /loginwindow/, mapto : 'Locked Screen'}, to the title_mappings setting did the trick for me.

But if it really prevents going into sleep mode, that would be an issue... Does anybody eperienced the same? Or, can anybody test it too?

I'm using OSX also, and I can confirm that loginwindow maps to Locked Screen correctly.

I'm not sure how to know if it is preventing the computer from sleeping. I think that the program is still running, because it shows up as Locked Screen on the graph -- does that mean it's not sleeping?

By the way, I get __LOCKEDSCREEN when the display is on, and the screen is locked (waiting for password). When the computer is sleeping, it is loginwindow.