upgrade issues due to remmina packages

[BrandonM7]

Long-time kubuntu user, but wouldn't consider myself a power user by any means. Running 18.04 for about a week, getting this error in terminal which is keeping me from updating or installing anything else. Any ideas on how to fix it? It seems to stem from Remmina but I know diddly nothing about it beyond that. I can't install anything until it's fixed, which is incredibly annoying.

Thanks for any help.

brandon@brandon-XPS-15-9550:~$ sudo apt-get upgrade                
Reading package lists... Done
Building dependency tree       
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
freerdp2-x11 : Depends: libfreerdp-client2 (>= 2.0.0~git201804050820-0+remmina201804082000.ra9ecd6a.d29dd283~ubuntu18.04.1) but it is not installed
              Depends: libfreerdp2 (>= 2.0.0~git201804050820-0+remmina201804082000.ra9ecd6a.d29dd283~ubuntu18.04.1) but it is not installed
              Depends: libwinpr2 (>= 2.0.0~git201804050820-0+remmina201804082000.ra9ecd6a.d29dd283~ubuntu18.04.1) but it is not installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).
brandon@brandon-XPS-15-9550:~$ sudo apt-get --fix-broken install
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Correcting dependencies... Done
The following additional packages will be installed:
libfreerdp-client2 libfreerdp2 libwinpr2
The following NEW packages will be installed:
libfreerdp-client2 libfreerdp2 libwinpr2
0 upgraded, 3 newly installed, 0 to remove and 22 not upgraded.
5 not fully installed or removed.
Need to get 0 B/1,031 kB of archives.
After this operation, 3,528 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
(Reading database ... 199254 files and directories currently installed.)
Preparing to unpack .../libwinpr2_2.0.0~git201804050820-0+remmina201804082000.ra9ecd6a.d29dd283~ubuntu18.04.1_amd64.deb ...
Unpacking libwinpr2:amd64 (2.0.0~git201804050820-0+remmina201804082000.ra9ecd6a.d29dd283~ubuntu18.04.1) ...
dpkg: error processing archive /var/cache/apt/archives/libwinpr2_2.0.0~git201804050820-0+remmina201804082000.ra9ecd6a.d29dd283~ubuntu18.04.1_amd64.deb (--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libwinpr2.so.2.0.0', which is also in package libwinpr2-2:amd64 2.0.0~git20170725.1.1648deb+dfsg1-7
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Preparing to unpack .../libfreerdp2_2.0.0~git201804050820-0+remmina201804082000.ra9ecd6a.d29dd283~ubuntu18.04.1_amd64.deb ...
Unpacking libfreerdp2:amd64 (2.0.0~git201804050820-0+remmina201804082000.ra9ecd6a.d29dd283~ubuntu18.04.1) ...
dpkg: error processing archive /var/cache/apt/archives/libfreerdp2_2.0.0~git201804050820-0+remmina201804082000.ra9ecd6a.d29dd283~ubuntu18.04.1_amd64.deb (--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libfreerdp2.so.2.0.0', which is also in package libfreerdp2-2:amd64 2.0.0~git20170725.1.1648deb+dfsg1-7
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Preparing to unpack .../libfreerdp-client2_2.0.0~git201804050820-0+remmina201804082000.ra9ecd6a.d29dd283~ubuntu18.04.1_amd64.deb ...
Unpacking libfreerdp-client2:amd64 (2.0.0~git201804050820-0+remmina201804082000.ra9ecd6a.d29dd283~ubuntu18.04.1) ...
dpkg: error processing archive /var/cache/apt/archives/libfreerdp-client2_2.0.0~git201804050820-0+remmina201804082000.ra9ecd6a.d29dd283~ubuntu18.04.1_amd64.deb (--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libfreerdp-client2.so.2.0.0', which is also in package libfreerdp-client2-2:amd64 2.0.0~git20170725.1.1648deb+dfsg1-7
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/libwinpr2_2.0.0~git201804050820-0+remmina201804082000.ra9ecd6a.d29dd283~ubuntu18.04.1_amd64.deb
/var/cache/apt/archives/libfreerdp2_2.0.0~git201804050820-0+remmina201804082000.ra9ecd6a.d29dd283~ubuntu18.04.1_amd64.deb
/var/cache/apt/archives/libfreerdp-client2_2.0.0~git201804050820-0+remmina201804082000.ra9ecd6a.d29dd283~ubuntu18.04.1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
brandon@brandon-XPS-15-9550:~$

[acheron]

Those package versions suggest that you are using an unsupported 3rd party PPA

(likely one found at https://launchpad.net/~remmina-ppa-team)

and the packages from there are conflicting with official ones in the Ubuntu archive.

Remove or ppa-purge the packages from the offending ppa would be advisable.

[BrandonM7]

Those package versions suggest that you are using an unsupported 3rd party PPA

(likely one found at https://launchpad.net/~remmina-ppa-team)

and the packages from there are conflicting with official ones in the Ubuntu archive.

Remove or ppa-purge the packages from the offending ppa would be advisable.

That is correct, because the version shipped with 18.04 doesn't play well with new versions of Windows Server - I did that at the suggestion of the Remmina team because I rely heavily on remote desktop for work.

I don't know how to do your suggested fix - could you be more specific with instructions?

Thank you for your help.

[Snowhog]

Those package versions suggest that you are using an unsupported 3rd party PPA

(likely one found at https://launchpad.net/~remmina-ppa-team)

and the packages from there are conflicting with official ones in the Ubuntu archive.

Remove or ppa-purge the packages from the offending ppa would be advisable.

The OP is using apt-get upgrade instead of apt-get dist-upgrade. I would suggest that he attempt the update again, using: sudo apt-get update && sudo apt-get dist-upgrade Things 'might' fare better?

[acheron]

They can try, but the package file conflicts like those occurring are usually a more fundamental packaging problem/conflict than that would solve. Saying that, apt can surprise even me with random weirdness at times. :P

[claydoh]

They can try, but the package file conflicts like those occurring are usually a more fundamental packaging problem/conflict than that would solve. Saying that, apt can surprise even me with random weirdness at times. :P

I agree. The dep errors at the beginning may be from using "apt upgrade" instead of the correct "apt full-upgrade" but the errors at the end after the dependency problem is solved are entirely from the new ppa having the same file in different packages than previous versions they've put out.

I think.

Maybe

I'm not sure

Did you notice the absurdly long versioning in those packages?

Sent from my LG-H931 using Tapatalk

[Snowhog]

And I too, agree, that the packaging within the PPA isn't clean. That said, and because the final errors "at the end after the dependency problem is solved" are solely against the application/packages in the PPA, might the OP try 'forcing' the installation of the affected packages?