I'm not seeing the same behaviour in Peppermint 10 .. right-clicking the
USB device in Nemo does indeed bring up the context menu, and unplugging
the device whilst the context menu is still visible does leave the
context menu displaying (though it looses the 'Add Bookmark', 'Mount',
and 'Eject'
As far as I was concerned this bug was already fixed in:-
0.52.1-1ubuntu1
in the main repo, so I can't see any need for this in proposed now.
But just to answer your question anyway, YES:-
0.52.2-1ubunti1-18.04.1
also fixes the issue (though now it would likely be more accurate to say
it
Run:
gksudo gedit /usr/share/applications/gdebi.desktop
make it read:-
[Desktop Entry]
Name=GDebi Package Installer
GenericName=Package Installer
Comment=Install and view software packages
Exec=gksudo gdebi-gtk %f
Icon=gnome-mime-application-x-deb
Terminal=false
Type=Application
If you edit the:-
/usr/share/applications/gdebi.desktop
launchers 'Exec' line to:-
Exec=gksudo gdebi-gtk %f
So gdebi-gtk prompts for the password BEFORE loading, it works perfectly
.. maybe a pkexec issue ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
vte2.91 (0.52.0-1ubuntu2) fixes it, thanks everyone.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756238
Title:
gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags
To manage
for what it's worth, 91_keep_fds.patch fixes libvte-2.91-0 for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756238
Title:
gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags
I may have gone overboard with libvte-2.91-0-udeb which isn't a default
package so is unnecessary.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756238
Title:
gdebi-gtk broken in 18.04 error:
Yep, definitely something in vte 0.52 because downgrading to 0.48 by
installing these packages from artful:-
gir1.2-vte-2.91_0.48.4-0ubuntu1_amd64.deb
libvte-2.91-0_0.48.4-0ubuntu1_amd64.deb
libvte-2.91-0-udeb_0.48.4-0ubuntu1_amd64.udeb
libvte-2.91-common_0.48.4-0ubuntu1_all.deb
fixes the issue.
No it's not that clicking the .deb doesn't fire up gdebi-gtk (it does),
it's that gdebi-gtk crashes whilst installing the .deb throwing the
error:-
dpkg: error: unable to read filedescriptor flags for : Bad file descriptor
Changing (or dropping) the %f option makes no difference :(
--
You
Any update on this ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756238
Title:
gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 1756887 ***
https://bugs.launchpad.net/bugs/1756887
Duplicate of
https://bugs.launchpad.net/ubuntu/+source/lxterminal/+bug/1756887
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The issue appears to be the comment:-
# The reason why this isn't 20 is documented at
https://bugs.launchpad.net/ubuntu/+source/lubuntu-
meta/+bug/1752733/comments/3
on line 8 of the lxterminal.postinst script
remove that comment, and
sudo dpkg --configure lxterminal
completes without error.
Public bug reported:
An update to lubuntu-gtk-core and lxterminal failed with the error
message:-
dpkg: dependency problems prevent configuration of lubuntu-gtk-core:
lubuntu-gtk-core depends on lxterminal; however:
Package lxterminal is not configured yet.
dpkg: error processing package
Public bug reported:
When using gdebi-gtk to install a .deb the install fails with the
message:-
dpkg: error: unable to read filedescriptor flags for : Bad file descriptor
This only occurs via the gdebi-gtk GUI front end, packages install perfectly if
done via the CLI with:
sudo gdebi
Sorry (again), I meant correcting it in
/var/lib/dpkg/info/grub-efi-amd64.postinst
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692175
Title:
package grub-efi-amd64 2.02~beta2-36ubuntu3.10 failed
sorry I meant in the grub-efi-amd64 postinst script
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692175
Title:
package grub-efi-amd64 2.02~beta2-36ubuntu3.10 failed to
install/upgrade:
Is there a missing semicolon on line 699 ?
if dpkg --compare-versions "$2" lt-nl 2.02~beta2-36ubuntu3.10
then
should than not be:
if dpkg --compare-versions "$2" lt-nl 2.02~beta2-36ubuntu3.10 ;
then
Correcting that in
/var/lib/dpkg/info/grub-efi-amd64-signed.postinst
and
Still affecting Lubuntu 14.04
** Also affects: lxkeymap
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1009103
Title:
lxkeymap crashes with:
Yeah, definitely ibus related .. terminating, uninstalling, or disabling
ibus from the panel applet fixes the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1307648
Title:
chromium 34 from
Can I add to that, that when I start synaptic with sudo synaptic it doesn't
freeze, or spam the terminal .. for me it only freezes if started with:-
gksudo synaptic
gksu synaptic
synaptic-pkexec
Downgrading Synaptic to synaptic_0.75.12build1 from 12.10 also fixes the
freezes
--
You received
0.80~exp2raring1 didn't fix the random synaptic crashes for me
I've noticed the random crashes don't occur if you start synaptic from the
command line with
sudo synaptic
but the DO occur if it's started with
synaptic-pkexec
or
gksudo synaptic
or
gksu synaptic
--
You received this bug
21 matches
Mail list logo
