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

Silent failure with nxt-filer when brick is not plugged in #51

Open
GoogleCodeExporter opened this issue Oct 10, 2015 · 2 comments
Open

Comments

@GoogleCodeExporter
Copy link

When starting nxt_filer from a graphical desktop environment when no
Lego Mindstorm NXT is plugged in, for example using Alt-F2 in KDE,
nothing happen.   The program just silently fail to start, and do not
report any errors using the GUI.

Trying to run it from a shell show these messages:

% nxt_filer
Traceback (most recent call last):
  File "/usr/bin/nxt_filer", line 144, in <module>
    brick = nxt.locator.find_one_brick(keyword_arguments.get('host',None))
  File "/usr/lib/python2.6/dist-packages/nxt/locator.py", line 137, in find_one_brick
    raise BrickNotFoundError
nxt.locator.BrickNotFoundError
%

Please change the program to report this problem with a GUI popup or
something similar, to avoid confusing users trying to start the program
for the first time.



What version of nxt-python are you using? On what operating system? 2.2.2 on 
Debian GNU/Linux


Please provide any additional information below.

See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697224 for the original 
Debian bug report.

Original issue reported on code.google.com by [email protected] on 9 Apr 2013 at 1:11

@GoogleCodeExporter
Copy link
Author

Original comment by [email protected] on 9 Apr 2013 at 3:10

  • Changed state: Accepted
  • Added labels: Component-Scripts, Component-UI, OpSys-All, Series-2.x, Type-Enhancement, Usability
  • Removed labels: Type-Defect

@tcwan
Copy link
Contributor

tcwan commented Mar 9, 2018

nxt-filer is obsolete.
There is a replacement, nxtfilemgr, which can be found in the master branch.
Nonetheless, I didn't implement any error pop-ups, so the status message is displayed only in the terminal.

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

No branches or pull requests

3 participants