search

linuxmint / warpinator

Share files across the LAN
GNU General Public License v3.0
1.21k stars 81 forks source link

Warpinator doesn't start emitting "can only concatenate str (not int) to str" #107

Closed yesint closed 2 years ago

yesint commented 2 years ago

On my Linux mint 20.2 laptop warpinator stopped working. If started from command line the following is printed:

$ warpinator
can only concatenate str (not "int") to str

Reinstalling the package doesn't help. I can't google anything similar to this problem. Any suggestions?

mtwebster commented 2 years ago

Have you installed any python3 modules from other than the system package manager? Or a newer python3 version than what's included with Mint?

mtwebster commented 2 years ago

Try the following commands:

gsettings reset org.x.warpinator.preferences reg-port
gsettings reset org.x.warpinator.preferences port

You'll need to re-set them possibly in preferences. I discovered a typo that could cause the error you're getting if both ports have the same value. The gui prevents this, but possibly you changed them in some other way.

yesint commented 2 years ago

Try the following commands:

gsettings reset org.x.warpinator.preferences reg-port
gsettings reset org.x.warpinator.preferences port

You'll need to re-set them possibly in preferences. I discovered a typo that could cause the error you're getting if both ports have the same value. The gui prevents this, but possibly you changed them in some other way.

I confirm that changing these settings solve the problem! However, I'm sure that never changed anything through gsettings or fiddled with warpinator settings in any other way. It seems that this happened after some of recent updates, but I can't track it better because I only use warpinator once per month or so. Thank you very much for your help!

mtwebster commented 2 years ago

Did you upgrade from 20.1 to 20.2? That's another scenario I can think of that would cause this - there was only a single port in the previous version. When the additional port was added during the upgrade, it may have ended up the same as the existing one. Regardless, this shouldn't have caused a crash - I'll leave this open until I get a chance to fix it.

Thanks

yesint commented 2 years ago

Did you upgrade from 20.1 to 20.2? That's another scenario I can think of that would cause this - there was only a single port in the previous version. When the additional port was added during the upgrade, it may have ended up the same as the existing one. Regardless, this shouldn't have caused a crash - I'll leave this open until I get a chance to fix it.

Thanks

The problem appeared in 20.1 before the upgrade to 20.2. The upgrade itself doesn't fix it. However, I noticed that in 20.1 warpinator was pulled from backports repository (not sure if it explains anything).

mtwebster commented 2 years ago

Ah you're right, we backported the new version to 20.1, 20, this is possibly what happened, then.

janos-r commented 2 years ago

I just used these 2 commands to fix this on my mom's pc. I was suddenly wondering why her warpinator was not starting while visiting over the holidays. Btw I upgraded her system from 20.1 to 20.2 when it came out, and warpinator was working fine somewhere in the past. Thank you very much for this thread! <3