Public bug reported:

libgksu2-0 has changed from the 2.0.12 to 2.0.13 release, specifically,
in it's handling of forkpty for interacting with sudo: it's now an
option which ISN'T enabled by default.

In order to restore the previous behavior:

change the rules file in debian/ to read:

DEB_CONFIGURE_EXTRA_FLAGS := --disable-gtk-doc --enable-gnome-keyring
--enable-sudo-forkpty

This will restore the previous behavior.

Simplest test to verify broken vs. fixed behavior:

gksu gksu ls  ---> will give the assert error

after enabling sudo-forkpty

gksu gksu ls ---> returns directory listing, as it does on Karmic.

Please fix, blocker for sabayon in lucid

** Affects: libgksu (Ubuntu)
     Importance: High
         Status: Confirmed

** Changed in: libgksu (Ubuntu)
   Importance: Undecided => High

** Changed in: libgksu (Ubuntu)
       Status: New => Confirmed

** Changed in: libgksu (Ubuntu)
    Milestone: None => lucid-alpha-2

-- 
libgksu fails to start many programs, fails with: assert g_str_has_prefix str 
!= NULL
https://bugs.launchpad.net/bugs/501559
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to