gdebi not working [SOLVED]

[jedi]

Yes I know it is the lazy mans tool.  I am a lazy man!  I can do a 'dpkg --install foo.deb' with the best of them, but gdebi has always been so convenient.  Just double-click on any .deb file, gdebi automatically started, installed the .deb and all was good.  Now however, double-clicking on a .deb file results in gdebi opening for just a brief second then closing with no error, and failing to install the selected .deb file.
Just wondering if it is my machine or if others are seeing this as well...
Thanks...

[PackRat]

Does gdebi write a log file - in /var/log/ maybe? Or can it be configured to do so, then  double-click a deb file.

[VastOne]

I have seen this, but only because a dependency was not met and gdebi was not reporting it correctly

If you try the same install with sudo dpkg -i it should tell you what is happening

I just went through this with a new install of Virtualbox

[hakerdefo]

From your terminal run,

Code Select Expand

sudo gdebi package_to_install.deb
Ofcourse you replace 'package_to_install.deb' with the package you are installing. You'll get some sort of error message(s) in terminal from gdebi that might offer some clues.
By the way if you want to launch graphical gdebi from terminal then the command is,

Code Select Expand

sudo gdebi-gtk package_to_install.deb

Cheers!!!

[VastOne]

This is happening with every deb and the error is

Code Select Expand

AttributeError: 'dict' object has no attribute 'op_progress'

I am working on resolving it

[hakerdefo]

Looks like an upstream gdebi bug,
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742727

Cheers!!!

[VastOne]

gdebi updated today via a dist-upgrade in the SID repos and is now working correctly