![]() Registered Member ![]()
|
I have today done a new instal of kde neon from the last snapshot (17/09/2020) and there were about 100 updates as you would expect.
My problem is that discover no longer installs a deb from an unsigned repo. How can I remove this newly introduced feature - as I have 10 or so debs on my local drive which I wish to install? |
![]() Registered Member ![]()
|
Was fine and then the update all broke it. I'm on the same boat.
|
![]() Registered Member ![]()
|
pleased (sorry) that it is not just me!
have some deb files to get my scanner working downloaded from the epson webite that I can't install now |
![]() Registered Member ![]()
|
Plus one
same problem over here. Philippe. |
![]() Registered Member ![]()
|
Same here.
The only way I'm managed to install some deb is with "sudo apt install deb_package_name.deb" or if the author of the deb (for ex: vivaldi.com) has some documentation on adding manually their signed keys, repositories and other steps. Steps that frankly cannot be expected of the user to do unless there's a bug or testing. Please fix. |
![]() Registered Member ![]()
|
Manually downloaded debs are not part of a repo, so cannot be giving the error - but an incorrectly added repo, unrelated to these debs, can give this, especially if the deb has dependencies that need to be installed, or the debs perhaps are for an older Ubuntu version?
Also, if the downloded deb itself is faulty, like Vivaldi's may be, then that is not Neon, or even Ubuntu's problem. So I suspect multiple issues, possibly. To see what is really going on is to try the command line
If it does not, use
For some debs that add repos on their own, try using dpkjg
This is somewhat basic Debian/Ubuntu package troubleshooting
claydoh, proud to be a member of KDE forums since 2008-Oct, and KDE user since 2001
|
![]() Registered Member ![]()
|
I had the same issue but then noticed a prior transient Discover error message and had just posted a request for help in the forum for System and Utilities under the title: Discover DEB install error ... odrs.gnome.org/1.0 ?
Perhaps the same earlier error msg pops up for you? Here is a copy of the post: I get an error message that is a transient notification that pops up after bringing up Discover even before clicking Install for a DEB using Discover. How can the underlying issue be fixed or worked around? I recently nuked and paved to bring up KDE Neon User built on Ubuntu 20.04 after the upgrade failed. I was trying to install slack-desktop-4.9.1-amd64.deb and got this popup notification when Discover came up: "Error while fetching reviews: error transferring https://odrs.gnome.org/1.0/reviews/api/fetch - server replied: BAD REQUEST" Earlier I missed that notification and clicked Install in Discover and entered my password and got the message: "Cannot install from an unsigned repo" The same problem has come up with another DEB.
Neon Plasma 5.20 User on 1 desktop and on Asus Transformer 3 Pro laptop. Win10 in VirtualBox for JMP stat package. Still 5.19 on older desktop.
|
![]() Registered Member ![]()
|
gdebi proved to be a great workaround. So for me problem is solved.
![]()
Neon Plasma 5.20 User on 1 desktop and on Asus Transformer 3 Pro laptop. Win10 in VirtualBox for JMP stat package. Still 5.19 on older desktop.
|
![]() Registered Member ![]()
|
Download the .deb > Open a terminal window and enter:
Works perfectly. |
![]() Registered Member ![]()
|
I have had another go with this. Installing a deb using the command:
sudo dpkg -i name.of.somepackage.deb works fine if it is a single deb that does not need any other packages. If it does need say another package from a standard repo then it doesn't. I tried again and did a fresh install using the snapshot of the 17092020. If I install the required deb files (for example for my epson scanner) using discover, before applying the required system updates, these install fine with no 'cannot instal from an unsigned repo' error. As a test I then uninstalled the scanner debs and tried to reinstall them using discover only to receive the 'cannot instal from an unsigned repo' error. Which seems to imply that a system setting was changed when installing the system updates after the fresh install. There does not appear to be a setting in discover for unsigned debs. |
![]() Registered Member ![]()
|
Yes. it's happening to me too, so I'm using the terminal
Command: sudo apt install ./name_software.deb |
![]() Registered Member ![]()
|
Hello, it didn't work for me too with Discover...
I use qApt
Right clic on your file, open with, write qapt-deb-installer then OK It works easily with gdebi too. Do the same method. |
![]() Registered Member ![]()
|
|
![]() Registered Member ![]()
|
Same here can't install .deb packages with Discover.
While KDE is pretty awesome (just switched from Mate this week), it seems KDE is having some serious issues. Some on purpose, some not... On line accounts... Broken Discover install .deb... Broken Dolphin or Kate as root... Broken (don't lecture me about dangerous please. dangerous is driving a motorcycle 200MPH on a public highway. modifying system files on my computer... not dangerous) Kio Gdrive... Broken Kio Skype, Telegram, Lync... Broken other then these critical services KDE is awesome!! |
![]() Registered Member ![]()
|
qapt doesn't list dependencies like gdebi. |
Registered users: bartoloni, Bing [Bot], Google [Bot], q.ignora, watchstar