Skip to content
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.

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

cannot open file /proc/fb on Ubuntu on Windows 10 #449

Closed
Log1x opened this issue Mar 16, 2017 · 11 comments
Closed

cannot open file /proc/fb on Ubuntu on Windows 10 #449

Log1x opened this issue Mar 16, 2017 · 11 comments

Comments

@Log1x
Copy link

Log1x commented Mar 16, 2017

Hey there.

Just installed the latest Windows 10 after being hesitant to switch to Windows 10 for quite awhile now.

Bash for Windows is a breath of fresh air compared to using alternatives like Cygwin (Babun).

I grabbed screenfetch off the Ubuntu repository and all works well except I'm getting a fatal error for /proc/fb.

awk: fatal: cannot open file `/proc/fb' for reading (No such file or directory)
/usr/bin/screenfetch: line 1341: [: =: unary operator expected

screenshot

I'm guessing this is due to Bash not being able to detect a GPU? Is there a way to fix this?

Thanks in advance.

EDIT: Sorry for the initial title. Was typing clear in my terminal and it happen to go into GitHub's issue title and submit. 😿

@Log1x Log1x changed the title clear cannot open file /proc/fb on Ubuntu on Windows 10 Mar 16, 2017
@Log1x
Copy link
Author

Log1x commented Mar 16, 2017

Appears this was fixed in the latest commit -- anyway we can get this pushed to Launchpad?

Thanks!

@darealshinji
Copy link
Collaborator

PPA was updated.

@Zachswan1
Copy link

Issue still persists for me. Using latest release available on LaunchPad.

@darealshinji
Copy link
Collaborator

@Zachswan1 New update on PPA should fix that

@hubdows
Copy link

hubdows commented Jul 21, 2017

Issue still persists with version 3.8.0-2~trusty.

awk: fatal: cannot open file `/proc/fb' for reading (No such file or directory)

@darealshinji darealshinji reopened this Jul 21, 2017
@Pablo1107
Copy link

I have ArchWSL and this happens to me too. Any fix?

@ghost
Copy link

ghost commented Apr 2, 2018

@Pablo1107, dc72b59 this commit fixed it for me

@darealshinji
Copy link
Collaborator

Good point, that commit should have fixed it.

@Xmetalfanx
Copy link

Xmetalfanx commented Apr 3, 2018

I can't comment on this exact issue, but I think it was on 16.04 (Ubuntu ..) based releases the default version of Screenfetch in the repos is not the newest version ... I wonder in some cases some of these issues ... heck i see "trusty" aka 14.04 in that screenshot ... are being caused by people running an older version of screenfetch before commits that fixed different issues were included.

I commented on another issue that has been closed now where i did see the same problem the user described ... then I added the ppa with the newest version, upgraded and it was fixed ... .this is what I am getting at

@Pablo1107
Copy link

@dahsameer the latest version on the arch repo is screenfetch 3.8.0-2, when that commit was released?

@darealshinji
Copy link
Collaborator

Maybe adding a template that tells the user he/she should check the latest version from git before making a bug report would help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants