When running gksudo python hardy, I get the same behavior I would have
gotten had I done it the traditional, GUI way.  On the other hand,
running just gksudo hardy exits almost immediately.  On the gripping
hand, when done the traditional way, it appears to be executed (by root)
simply as hardy.  This means the environment (files etc.) needs to be in
a special state for hardy to function.

-- 
Upgrade from gutsy to hardy-beta hangs
https://bugs.launchpad.net/bugs/205225
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to