Package: nheko
Version: 0.6.1-1
Severity: normal
Dear Maintainer,
* What led up to the situation?
If the device name is empty in the login process (which does not
warn anything when the field is left as is), the nheko session will
not show up in other clients (riot.im in my case). Messages sent to
chat rooms with e2ee enabled either don't get encrypted for existing
rooms, or get encrypted but appear as unknown in other clients for
rooms created by the nheko session.
Since the device name is needed for the session to be recognised by
other clients, I would expect it either -
a. be a required field in the login process.
b. has a default value to be used when not specified.
I believe this will need to be forwarded upstream, but since Debian
discourages directly filing bugs to upstream, here I am...
Cheers.
-- System Information:
Debian Release: buster/sid
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8),
LANGUAGE=zh_CN:zh (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages nheko depends on:
ii libboost-atomic1.67.0 1.67.0-7
ii libboost-chrono1.67.0 1.67.0-7
ii libboost-date-time1.67.0 1.67.0-7
ii libboost-iostreams1.67.0 1.67.0-7
ii libboost-random1.67.0 1.67.0-7
ii libboost-regex1.67.0 1.67.0-7
ii libboost-system1.67.0 1.67.0-7
ii libboost-thread1.67.0 1.67.0-7
ii libc6 2.27-6
ii libcmark0 0.28.3-1
ii libgcc1 1:8.2.0-7
ii liblmdb0 0.9.22-1
ii libolm2 2.2.2+git20170526.0fd768e+dfsg-1
ii libqt5concurrent5 5.11.1+dfsg-9
ii libqt5core5a 5.11.1+dfsg-9
ii libqt5dbus5 5.11.1+dfsg-9
ii libqt5gui5 5.11.1+dfsg-9
ii libqt5multimedia5 5.11.1-2
ii libqt5network5 5.11.1+dfsg-9
ii libqt5svg5 5.11.1-2
ii libqt5widgets5 5.11.1+dfsg-9
ii libsodium23 1.0.16-2
ii libssl1.1 1.1.0h-4
ii libstdc++6 8.2.0-7
ii zlib1g 1:1.2.11.dfsg-1
Versions of packages nheko recommends:
ii ca-certificates 20170717
nheko suggests no packages.
-- no debconf information
