8000 stty standard input inappropriate ioctl for device · Issue #566 · polybar/polybar · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

stty standard input inappropriate ioctl for device #566

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
madnight opened this issue May 5, 2017 · 9 comments
Closed

stty standard input inappropriate ioctl for device #566

madnight opened this issue May 5, 2017 · 9 comments

Comments

@madnight
Copy link
madnight commented May 5, 2017 •
edited
Loading

I simply try this example from the wiki

[module/vpn]
type = custom/script
exec = echo vpn
exec-if = pgrep -x openvpn
interval = 5
format-underline = #268bd2
format-prefix = "🖧 "
format-prefix-foreground = #5b

(openvpn is running) i can also try only echo without exec-if always the same error
but also any other custom script fails with the message:
stty standard input inappropriate ioctl for device
@madnight
Copy link
Author
madnight commented May 5, 2017 •
edited
Loading

it might be the case that polybar does not work with zsh, so if you start polybar from a zsh shell you have to do run it with SHELL=/bin/bash polybar top -r

@jaagr
Copy link
Member
jaagr commented May 12, 2017

I'm using zsh myself and I have no issues with it.

Do you have any stty commands in .zshrc? Anyway, I wouldn't say this is an issue with polybar.

@madnight
Copy link
Author

hmm but non-interactive shells (zsh running a single command) shouldnt load .zshrc as far as i know, otherwise a non-interactive shell would also load left and right prompts, auto completion ... and many more stuff that isnt needed.

Maybe you should check if polybar use a interactive shell for custom command execution.

@jaagr
Copy link
Member
jaagr commented May 12, 2017 •
edited
Loading

Yeah, but child processes inherit the environment. The commands are executed using $SHELL -c <command>. If SHELL is undefined, it will default to /bin/sh.

I don't know enough about zsh to be able to track down the root cause of this. I'd recommend using your workaround for now. Been planning on using a prefixed environment variable (like POLYBAR_SHELL) to determine what shell to use for commands, since others have had issues with it before as well (using zsh/fish).

@madnight
Copy link
Author
madnight commented May 12, 2017 •
edited
Loading

okay thx, maybe you could even force sh, so instead of $SHELL -c using /bin/sh -c. Every sensible environment has /bin/sh (even when its a symlink). I dont think that you have to support every shell on the planet : ) ... maybe also take a look at conky's exec that always worked for me

@jaagr
8000 Copy link
Member
jaagr commented May 12, 2017

SHELL=/bin/sh polybar ... would give you the same behavior. Just use a wrapper to avoid having to type it out.

@madnight
Copy link
Author

Jup, but no wrapper needed with conkys solution: https://github.com/brndnmtthws/conky/blob/master/src/exec.cc#L98

This also avoids other confusing default shell related errors in the future for other users.

@jaagr
Copy link
Member
jaagr commented May 12, 2017 •
edited
Loading

Yeah but as I said earlier, use it for now. A fix won't be available until I get some free time.

@madnight
Copy link
Author

yes sir : ) however polybar is the best bar i used so far!

@jaagr jaagr closed this as completed in 86ff947 May 12, 2017
patrick96 added a commit that referenced this issue Dec 3, 2017
@patrick96
Release 3.1.0 (#863)
bf16a4d 
Breaking Changes:

* Date module no longer supports non-padded specifiers (i.e. `%-d`) and potentially other specifiers, see #792
  - Check http://en.cppreference.com/w/cpp/io/manip/put_time to see supported specifiers
* Setting background color to `background-0` with gradients (refer to https://github.com/jaagr/polybar/wiki/Known-Issues)

Changelog:

Features:
* Feat(mpd): State-specific formats (`format-playing`, `format-paused`, `format-stopped`) (#567), see #524 
* Feat(ipc): Visibility commands (show, hide, toggle, restart, quit) (b6c5563)
* Feat(shell): Bash completion (#588)
* Feat(menu): `expand-right` option (#658), see #655
* Feat(temperature): hwmon sysfs support (#688), see #404 
* Feat(cursor): Change cursors over clickable/scrollable areas (#727), see #721  
* Feat(temperature): Fahrenheit and Celsius tokens (#804)
* Feat(mpd): Use mpd name tag or URI as fallback for title-less tracks (#823), see #815 

Fixes:
* Fix(i3): Clicking workspaces without index (#521), see #520 
* Fix(parser): Prefix options overriding format options (#729), see #544
* Fix(parser): Overline tags (eebf105)
* Fix(process_util): Prefix shell environment variable (`$POLYBAR_SHELL`) (86ff947), see #566 
* Fix(parser): `%{R}` tag (reverse colors) (0bd8f1f), see #585 
* Fix(renderer): Center block position with tray (389bae2 & #673), see #551 & #672 
* Fix(xworkpaces): Active workspace with XMonad (#587), see #411 & #535 
* Fix(config): Expand tilde, environment variable (d3b0670 & #724), see #603 & #719 
* Fix(build): Remove curlbuild.h (#648), see #647 
* Fix(renderer): Off by one error for actions (#663), see #661 
* Fix(gcc): GCC 7.1 ([jaagr/xpp/#6](polybar/xpp#6))
* Fix(fs): Use `bytes_available` for `percentage_used` (138f5fa), see #710
* Fix(fs): Use `f_frsize` for calculations (a682d2a)
* Fix(date): Remove date string length limitation (#745), see #754 
* Fix(renderer): Nested actions (#772), see #760 and #758
* Fix(i3): Check and warn if current workspace not found (#826), see #824 
* Fix(github): Prevent module disappearing with no connection (#811), see #810 
* Fix(renderer): Module gradients (#831), see #759 
* Fix(build): Update deprecated jsoncpp Reader
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jaagr @madnight
0