search

bordaigorl / rmview

A live viewer for reMarkable written in PyQt5
GNU General Public License v3.0
742 stars 61 forks source link

configparser.DuplicateOptionError after Update 2.14 #140

Open exodd opened 2 years ago

exodd commented 2 years ago

Hello,

as the title says, the last update broke it down. After resetting the ssh keys, I've been trying to use the screenshare (I've tried activating it before and after I launch rmview with the same effect), but it won't connect to the pc. The program doesn't stop and tries to connect to the tablet, but it falls endlessly into the same error: image

bordaigorl commented 2 years ago

Oh boy, it looks like your xochitl.conf contains two UserToken keys, which is surprising. If you are comfortable with accessing the tablet via SSH you can locate /home/root/.config/remarkable/xochitl.conf on your tablet and find the offending duplicate UserToken. Make a backup of the file before you attempt any modification. If one of the UserToken entries is empty (i.e. UserToken=@ByteArray()) then remove that one. If the duplicates are all non-trivial, then you need to figure out which one is the one that gets picked up by xochitl and remove the others (my guess would be it's the last one in textual order but who knows). If it gets to that I can help you figuring it out.

More long term: if I get more reports like this I'll consider adding some support for duplicates but this feels like a bug of the tablet's software...

exodd commented 2 years ago

Thanks for the replay.

There ARE 2 different usertokens, and I may know what caused the error:

one is "UserToken" and the other is "usertoken", so there's an ambiguity in lower/uppercases somehow it seems that the software writing the tokens makes a distinction between the two, and the one reading them doesn't

They are both non-empty and also not the same, so I'll try to delete one at random. Wish me luck

exodd commented 2 years ago

Ok, I deleted the last one, and now rmview works again! Thanks a lot!

bordaigorl commented 2 years ago

@exodd thanks for reporting back, this can be useful for other users. Could be worth filing a bug report through the official support, this definitely sounds like a bug in their software.