[tor-bugs] #28332 [Core Tor/Nyx]: Nyx configurashion editor reproducibly crashes if custom ordering is set
Tor Bug Tracker & Wiki
blackhole at torproject.org
Wed Nov 7 14:16:14 UTC 2018
#28332: Nyx configurashion editor reproducibly crashes if custom ordering is set
--------------------------+------------------------------
Reporter: wagon | Owner: atagar
Type: defect | Status: closed
Priority: Medium | Milestone:
Component: Core Tor/Nyx | Version: Tor: 0.3.4.9
Severity: Normal | Resolution: duplicate
Keywords: config | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
--------------------------+------------------------------
Comment (by wagon):
Thank you! Now everything works, but we are probably moving to the stage
"old bugs fixed, new bugs added".
Stable version (2.0.4) didn't have artifacts during startup. Git version
has. I think it is related to your fixes to panels (which were crashing
during scrolling). I'll attach screenshot. Left scrolling panel is
connected to upper symbols, some words are changed (`hidden]n]` instead of
`hidden]`, and `file.e` instead of `file`). I checked few terminals, and
it is everywhere. It is easily fixed if after startup I refresh the
terminal with Ctrl+L, but should it be fixed anyway?
Another thing is more essential: stable version displayed cpu usage by Tor
and its uptime, but git version doesn't do that. cpu is always 0.0, uptime
value is empty. However, if I use root to run git version of Nyx, both cpu
and uptime are shown. It looks like permissions issue, but everything else
works OK, and I failed to find what's wrong with my setup (stable Nyx
worked good also with non-root user).
I think it would be good to have Nyx version also shown at the top. Now it
can be accessed through menu, but since you write 'nyx' at the left top
corner anyway, why not to add its version too? With `tor-prompt` it is
worse: I cannot see any way to learn its version, even as command-line
switch.
Both git and stable `tor-prompt` have one strange behavior:
{{{
$ tor-prompt
Tor isn't running. Starting a temporary Tor instance for our interpreter
to
interact with. This will have a minimal non-relaying configuration, and be
shut down when you're done.
--------------------------------------------------------------------------------
Unable to start tor: Process terminated: Failed to bind one of the
listener ports.
}}}
But:
{{{
$ tor-prompt -i 127.0.0.1:9051
Welcome to Stem's interpreter prompt. This provides you with direct access
to
Tor's control interface.
This acts like a standard python interpreter with a Tor connection
available
via your 'controller' variable...
>>> controller.get_info('version')
'0.2.5.1-alpha-dev (git-245ecfff36c0cecc)'
You can also issue requests directly to Tor...
>>> GETINFO version
250-version=0.2.5.1-alpha-dev (git-245ecfff36c0cecc)
250 OK
For more information run '/help'.
>>>
}}}
Why it doesn't recognize standard port as its default? Is it a bug or
feature? If it is the feature, I would make the default to be the
opposite: if somebody wants to start extra Tor, he should specify some
command-line option.
And the last thing is wrong Nyx log messages (problem exists for both git
and stable):
{{{
[NYX_NOTICE] Unused configuration entry: unicode_support
[NYX_NOTICE] Unused configuration entry: data_directory
[NYX_NOTICE] Unused configuration entry: acs_support
}}}
At first, Nyx always says that these options are "unused" independently on
the value in `nyxrc` config (`true` or `false`). My terminal has unicode
support, everything looks OK with pseudo-graphics, so I cannot understand
why it is "not used". When I disable `acs_support`, pseudo-graphics is
replaced by other symbols, so this option works. But NYX_NOTICE is always
"unused" for both `acs_support false` and `acs_support true`. Maybe you
have added these options, but forgot to update Nyx config validator?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/28332#comment:8>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list