Nixnote2 will not connect to validate account
..this a issue TEMPLATE.. before posting pls delete the parts, which are not relevant..
Expected vs. actual behavior
Previously Nixnote seamlessly connected with Evernote after installing into a new computer the current version does not accept either the email address or the username.
Steps to reproduce the problem (or log file)
- Install NixNote on Ubuntu.
- Attempt to synch with Evernote.
Specifications
- [Version] Version: 2.1.9+dfsg1-1
system details
System Details Report
Report details
- Date generated: 2024-05-16 18:40:06
Hardware Information:
- Hardware Model: (null)
- Memory: 16.0 GiB
- Processor: 11th Gen Intel® Core™ i7-1185G7 × 8
- Graphics: Intel® Xe Graphics (TGL GT2)
- Disk Capacity: 250.1 GB
Software Information:
- Firmware Version: 03.19
- OS Name: Ubuntu 23.10
- OS Build: (null)
- OS Type: 64-bit
- GNOME Version: 45.2
- Windowing System: Wayland
- Kernel Version: Linux 6.5.0-35-generic
the current version does not accept either the email address or the username.
If the login dialog was shown or not? Any error reported?
When I get time I'll try it again and take better notes.
On Fri, May 17, 2024 at 2:38 AM boo-yee @.***> wrote:
the current version does not accept either the email address or the username.
If the login dialog was shown or not? Any error reported?
— Reply to this email directly, view it on GitHub https://github.com/robert7/nixnote2/issues/224#issuecomment-2116938683, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALQIY3IISXX3J2HZHHKPZKLZCWXWLAVCNFSM6AAAAABH3EFITWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJWHEZTQNRYGM . You are receiving this because you authored the thread.Message ID: @.***>
yeah, same here, can't no sync with evernote.
Try the latest version below please. The previous version uses qtwebkit to open the login page, and it seems not to work today. The latest version uses system browser to login.
https://github.com/robert7/nixnote2/releases/tag/continuous-develop
I had the same issue and, at least with the current continuous-develop release (I mean, the one from Jul 19, 2024), I confirm the issue is solved.