(2013-05-17, 16:32)Memphiz Wrote: Nope this is the xbmc.log ... i am referring to the crashreporter file.
You mean the OS X LOG ? The one
today.
(2013-05-17, 16:36)Memphiz Wrote: Base on that xbmc.log i am still extremly confused:
I don't understand either
(2013-05-17, 16:36)Memphiz Wrote: This looks perfectly fine like someone is pressing a key on your keyboard/remote which is bound to quit xbmc. I guess its as following.
Except that this button used to start XBMC and, most of the time, it does.
(2013-05-17, 16:36)Memphiz Wrote: You start xbmc by pressing the "power on" key on your remote ... XBMC starts up - XBMC receives the very same keypress again and translates it to quit. So basically the one keypress you are doing for starting up XBMC also in the same time results in quitting XBMC.
I understand, my point i only pressing this button once so why, from time to time, it consider two actions ?
(2013-05-17, 16:36)Memphiz Wrote: Does this sound reasonable? If so the whole problem in why this thread is already so long is your wording.
Here is another wording : most of the time when i press this button XBMC starts, from time to time it starts & stop.
(2013-05-17, 16:36)Memphiz Wrote: You always talked about "Crash". Crash is when MacOSX brings up the "This software has crashed" dialog. You need to distinguish a crash from a "XBMC just quits".
I'm talking a crash because :
1. Before my initial post there were no problem
2. don't press twice this button, that was i consider it is not a normal behavior
3. I talk about "crash" because (1) OS X pop up a crash alert and (2) it's not a normal behavior
(2013-05-17, 16:36)Memphiz Wrote: This still doesn't solve your issue nore do i know what really happens/goes wrong here. But at least that theory clears up what happens on your mac.
Sorry, i did not understand what you mean by "But at least that theory clears up what happens on your mac. ".
Nemrod