This also affects me,qapt-deb-installer 3.0.5-1ubuntu1 (Ubuntu Studio
20.10). Reproducible with latest google-earth-pro-
stable_current_amd64.deb
qapt-deb-installer should at a minimum print some useful info on the
terminal. All I see is:
QCommandLineParser: already having an option named "h"
** Changed in: qapt
Status: New => Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205530
Title:
qapt-deb-installer mishandles dependencies on multiarch=foreign
packages
To manage
This bug is still present in qapt-deb-installer 3.0.4-0ubuntu1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205530
Title:
qapt-deb-installer mishandles dependencies on multiarch=foreign
** Changed in: qapt
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205530
Title:
qapt-deb-installer mishandles dependencies on multiarch=foreign
packages
To
** Changed in: qapt
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1205530
Title:
qapt-deb-installer mishandles dependencies on multiarch=foreign
packages
To
** Bug watch added: KDE Bug Tracking System #330446
https://bugs.kde.org/show_bug.cgi?id=330446
** Also affects: qapt via
https://bugs.kde.org/show_bug.cgi?id=330446
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Launchpad has imported 1 comments from the remote bug at
https://bugs.kde.org/show_bug.cgi?id=330446.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
Hi there!
Thanks for reporting this bug! Your bug seems to be a problem with the
KDE program itself, and not with our KDE packages. While we appreciate
your issue, it would be better if it was tracked at
https://bugs.kde.org, so that the KDE developers can deal with this
speedily and have direct
