[RELEASE] Chrome Launcher

  Thread Rating:
  • 4 Votes - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Post Reply
nickr Online
Donor
Posts: 9,913
Joined: May 2009
Reputation: 179
Location: Christchurch NZ
Post: #241
(2014-11-26 08:48)KratsYnot Wrote:  A few days ago I set up RaspBMC on the Raspberry Pi, and after installing the Chrome Launcher, whenever I try to open launcher, I just get the message 'Chrome not found." I tried uninstalling it and installing from a flash drive instead, and that did not help either. I couldn't find anywhere else this question had been asked, so would anybody here have any solutions?

Thanks,
Krats

Pretty sure chrome doesn't run on rpi

If I have helped you or increased your knowledge, click the plus button and increase my reputation :)
find quote
joeyjoejoe Offline
Junior Member
Posts: 6
Joined: Feb 2012
Reputation: 0
Post: #242
(2014-12-01 10:34)joeyjoejoe Wrote:  HI

I have a problem when i try to use Chrome Launcher, The symptoms are as follows.

When launching a page, even the stock vimeo page, Chrome launches, then quickly goes to background. It continues to run and in the case of vimeo, video playback starts, but I cannot access it. When I exit xbmc, Vimeo is still full screen playing in Kiosk mode.

This also happens when I use SkyGO, I dont know if this is related.

I would post some log file, but I dont see any mention of the app in there?

Thanks

Joe

Just to update, I have solved this problem now. What was happening was to do with 'focus' restrictions imposed by using xbmclauncher. The launche automatically sets the focus of xbmc to be forced to the foreground, even if another program is launched. I have resolved this in the settings now.

My next problem though, is that when Chrome does launch in kiosk mode, I can still see the taskbar, it is not full screen as if I had hit F11, why is this the case. Am i understanding this wrong, I thought it should work completely full screen?

Thanks

Joe
find quote
JasonPell Offline
Senior Member
Posts: 192
Joined: Mar 2012
Reputation: 1
Location: Geelong, Australia
Post: #243
What OS are you on
find quote
caffeinepills Offline
Junior Member
Posts: 10
Joined: Nov 2014
Reputation: 0
Post: #244
Running Windows 8 , XBMC Helix, NetfliXBMC, and Chrome Launcher and having an issue.

If I am running true full screen Chrome Launcher will minimize XBMC and then launch Chrome. THis causes problems when XBMC doesn't regain focus and is stuck in the taskbar.

However, if I use the option in XBMC for "USe a fullscreen window rather than true fullscreen". The window will launch ok, Any solutions?

EDIT: Solved. Seems NetlfiXBMC or Chrome Launcher must look for XBMC.exe to restore focus. Since XBMC is renamed to Kodi.exe in the newest versions, seems it doesn't work yet.
(This post was last modified: 2014-12-07 12:49 by caffeinepills.)
find quote
sector72 Offline
Junior Member
Posts: 11
Joined: Apr 2012
Reputation: 0
Post: #245
Hi. I run Ubuntu 14.04 LTS on my HTPC. Until a few days ago, this Ubuntu release continued to use XBMC 13.2. A couple days ago, the upstream repositories finally switched to Kodi 14.0. The switchover was mostly seamless but I've noticed that Chrome launcher now longer works.

I have the machine configured to run XBMC/Kodi in standalone mode so my script starts a desktop environment prior to firing up Chrome:

Code:
#!/bin/bash
/usr/bin/unity &
/usr/bin/google-chrome --no-proxy-server "$@"
killall unity

This worked fine before the upgrade. What happens now is:
1) I see the unity desktop environment start. I do not see the Chrome window open.
2) After maybe one second, the screen changes back to Kodi. However Kodi no longer has mouse or keyboard focus and seems dead in the water.

If I ssh into the HTPC at this point, I can see that both Unity and Chrome are in fact running. They're just not visible.

Has Kodi changed its behavior so that it forces itself into the foreground?
find quote
sector72 Offline
Junior Member
Posts: 11
Joined: Apr 2012
Reputation: 0
Post: #246
Going to follow up to my own post...

I downgraded to 13.2 and verified that Chrome launcher indeed worked. So something changed in 14.0.

With that in mind, I tried something that I was pretty sure wouldn't work: I edited script.sh and commented out the two lines that start and stop the secondary desktop environment. So the new script looks like this:

#!/bin/bash
/usr/bin/google-chrome --no-proxy-server "$@"

It works! Looks like starting the desktop manager isn't necessary on 14.0.
find quote
Post Reply