2014-07-19, 15:17
When I close XBMC I do not have any access to the Notebook about half an hour or so, the display is black. After that I can use the Notebook the usual way.
What might that be caused by?
What might that be caused by?
Quote: Virus?Actually I would not think so.
Quote: What operating system?Win 7.
Quote: In Windows or Linux you could try ending the process, and on OSX you can try force quitting the application.Yes, I would do it, if I had access to it.
Quote:Does the problem occur if you start xbmc and then quit xbmc without watching a movie?The problem does not occur always when closing XBMC as I see now. If I remember it right, the problem occurs after watching a movie and start watching a movie, so after watching a movie for may be 5 minutes and closing then.
Quote:Does the problem occur if you start xbmc then start to watch a movie but quite the movie after one minute then directly quit xbmc after that?Ah, there is the question to my answer before. I assume, when it happened once, I started the movie, watching it, skipping some times within the movie and then quitting during the movie was running.
Quote:Are you using local files from your notebook or are you fetching them from your movie server or streaming them from the internet?Local files on Notebook and on external Hard Disks. No server and streaming.
Quote: Have you produced a debug log and looked within the log for hints to the cause?No, I didn't, it do not know how to cause the issue.
Quote: If you can get access to another pc and connecting both to a router, can you ping your notebook after quiting xbmc and while the screen black?I assume, that would not be possible to do here, unfortunately.
Quote:Dirki, i think that nickr may agree that if you define the xbmc version in your signature and at some time in the future update to xbmc 27.3 (for example) then this (old) thread will have your updated signature. As such anyone else who finds the thread using google or search may indeed be misslead into thinking this old issue is with xbmc 27.3Yes, thank you, skylarking, that is fairly true, unless one would - in this case (and to make it a bit more inconvenient) - regard the posting date in combination with the XBMC (and / or other) version(s). The problem of a signature generally, obviously.
Quote:I'd say it's best practice to explicitly type the OS and XBMC version you are using in the thread body itself rather than rely on a changing signature to provide such info...Yes, indeed, that's true, I would say.