Issue 355 in xmonad: XMonad.Actions.WindowGo (runOrRaise) fails on the specific command "chromium"
Status: New Owner: ---- New issue 355 by vox.cogitatio: XMonad.Actions.WindowGo (runOrRaise) fails on the specific command "chromium" http://code.google.com/p/xmonad/issues/detail?id=355 What steps will reproduce the problem? 1.Use keybinding to spawn chromium. 2.Use keybinding to runOrRaise chromium. What is the expected output? What do you see instead? When chromium is not running, these keybindings should do the same thing (i.e launch chromium). Instead, the spawn keybinding works as intended while the runOrRaise binding does nothing. When chromium is already running, the runOrRaise binding will raise the window as intended. Oddly enough i have only seen this error with chromium specifically, not any other commands. What version of the product are you using? On what operating system? Xmonad 0.9-2, on Arch Linux. Attachments: xmonad.hs 1.6 KB -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings
Comment #1 on issue 355 by gwern0: XMonad.Actions.WindowGo (runOrRaise) fails on the specific command "chromium" http://code.google.com/p/xmonad/issues/detail?id=355 This is probably due to runOrRaise's use of safeSpawn. Is chromium installed installed somewhere not in the default $PATH that X (and XMonad) would see? spawn goes through the shell usually and may see a different $PATH. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings
Comment #2 on issue 355 by vox.cogitatio: XMonad.Actions.WindowGo (runOrRaise) fails on the specific command "chromium" http://code.google.com/p/xmonad/issues/detail?id=355 Arch's chromium build has a startscript in /usr/bin so that shouldn't be an issue. Timely response by the way. :-) -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings
Comment #3 on issue 355 by gwern0: XMonad.Actions.WindowGo (runOrRaise) fails on the specific command "chromium" http://code.google.com/p/xmonad/issues/detail?id=355 I was on gmail when you reported it. If I'm right, then explicitly binding safeSpawn "chromium" to a key should fail. Could you try that? -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings
Comment #4 on issue 355 by vox.cogitatio: XMonad.Actions.WindowGo (runOrRaise) fails on the specific command "chromium" http://code.google.com/p/xmonad/issues/detail?id=355 I tried that, and it did indeed fail. Why do you think safeSpawn has trouble with this command specifically? I know that I have used RoR successfully on other programs in /usr/bin, so i don't think it's a $PATH problem. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings
Comment #5 on issue 355 by gwern0: XMonad.Actions.WindowGo (runOrRaise) fails on the specific command "chromium" http://code.google.com/p/xmonad/issues/detail?id=355 With more sleep, I see I should've suggested you fire up GHCi and do a safeSpawn in there instead, in hopes that you would see an error message or informative output of some other kind. Is http://aur.archlinux.org/packages/chromium-browser-bin/chromium-browser-bin/... the script concerned? What happens with safeSpawn "full-path-to-actual-binary-and-not-the-script"? Or with just the actual-binary? -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings
Comment #6 on issue 355 by vox.cogitatio: XMonad.Actions.WindowGo (runOrRaise) fails on the specific command "chromium" http://code.google.com/p/xmonad/issues/detail?id=355 That script you linked to is not the one in /usr/bin. I'm attaching that one. Also, I've tried safeSpawn of "chromium", "/usr/bin/chromium", and "/usr/lib/chromium/chromium" (which is the actual binary) in both XMonad as a keybinding and in ghci by importing safeSpawn. In all cases running it manually in ghci suceeded while the keybinding failed silently. Attachments: chromium 133 bytes -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings
Comment #7 on issue 355 by allbery.b: XMonad.Actions.WindowGo (runOrRaise) fails on the specific command "chromium" http://code.google.com/p/xmonad/issues/detail?id=355 That sounds to me like your normal PATH is okay but it's wrong when xmonad starts. I have attached a small wrapper script which captures a log of messages from chromium. Please put it somewhere like your home directory or your private bin directory (don't replace /usr/bin/chromium!) and safeSpawn it from xmonad, then check ~/chromium.log for errors. Attachments: chromium-w.sh 63 bytes -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings
Comment #8 on issue 355 by vox.cogitatio: XMonad.Actions.WindowGo (runOrRaise) fails on the specific command "chromium" http://code.google.com/p/xmonad/issues/detail?id=355 You'll fins the logfile attached. FYI i think the "zygote" is referring to chromiums's tabs, which run in separate processes. It looks like it's doing some sort of fork but then cant find the child process and terminates immediately. EDIT: I googled this particular error message and it might be a known issue w. chromium. Does safeSpawn manage signals, or SIG_CHLD in particular? http://code.google.com/p/chromium/issues/detail?id=29279 Attachments: chromium.log 122 bytes -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings
Comment #9 on issue 355 by allbery.b: XMonad.Actions.WindowGo (runOrRaise) fails on the specific command "chromium" http://code.google.com/p/xmonad/issues/detail?id=355 That would probably be it; last I checked, xmonad ignored SIGCHLD. I am surprised it doesn't undo that in the child when spawning subprocesses, though. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings
Updates: Status: Fixed Comment #10 on issue 355 by SpencerJanssen: XMonad.Actions.WindowGo (runOrRaise) fails on the specific command "chromium" http://code.google.com/p/xmonad/issues/detail?id=355 In core xmonad, we set SIGCHLD to default in forked processes, safeSpawn didn't do that. Fixed in darcs. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings
participants (1)
-
codesite-noreply＠google.com