Dear Maintainer,

While onionshare had been running with a share for awhile, I went to
stop it from running by
clicking on the button that would normally stop it from running: but
once clicked it said
'starting...  ('which was a little weird).  It seemed to be stuck there.

on the console this is what was displayed

unhandled close event
Error calling Python override of QThread::run(): Traceback (most
recent call last):
  File "/usr/lib/python3/dist-packages/onionshare/threads.py", line 82, in run
    self.mode.app.start_onion_service(
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
        self.mode.get_type(), self.mode.settings, await_publication=True
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/lib/python3/dist-packages/onionshare_cli/onionshare.py",
line 80, in start_onion_service
    self.onion_host = self.onion.start_onion_service(
                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
        mode, mode_settings, self.port, await_publication
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    )
    ^
  File "/usr/lib/python3/dist-packages/onionshare_cli/onion.py", line
746, in start_onion_service
    res = self.c.create_ephemeral_hidden_service(
        {80: port},
    ...<4 lines>...
        client_auth_v3=client_auth_pub_key,
    )
  File "/usr/lib/python3/dist-packages/stem/control.py", line 3057, in
create_ephemeral_hidden_service
    if self.get_version() < stem.version.Requirement.ADD_ONION:
       ~~~~~~~~~~~~~~~~^^
  File "/usr/lib/python3/dist-packages/stem/control.py", line 489, in wrapped
    return func(self, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/stem/control.py", line 1277, in
get_version
    version_str = self.get_info('version')
  File "/usr/lib/python3/dist-packages/stem/control.py", line 489, in wrapped
    return func(self, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/stem/control.py", line 1208, in get_info
    response = self.msg('GETINFO %s' % ' '.join(params))
  File "/usr/lib/python3/dist-packages/stem/control.py", line 662, in msg
    self._socket.send(message)
    ~~~~~~~~~~~~~~~~~^^^^^^^^^
  File "/usr/lib/python3/dist-packages/stem/socket.py", line 460, in send
    self._send(message, lambda s, sf, msg: send_message(sf, msg))
    ~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/stem/socket.py", line 243, in _send
    raise stem.SocketClosed()
stem.SocketClosed

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/onionshare/threads.py", line 111, in run
    message = strings._("error_generic").format(e.args[0])
                                                ~~~~~~^^^
IndexError: tuple index out of range

So what is the bug here that I'm reporting?  That last bit.

If something is going on internal to onionshare, some internal
exception being generated
*at the very least* it should be caught at
/usr/lib/python3/dist-packages/onionshare/threads.py

a test should be made before e.args[0] is invoked to ensure that it
*has* something to index.
it should not be possible for there to be an index error while
handling another error