Can you still reproduce this? If so, can you please make it hang and than check the process id of the haning gksu? With that, you can run:
$ sudo strace -p $pid 2> /tmp/gksu.strace
(where $pid is the number, eg 1234)
Leave it runing for a bit and then press CTRL-C to stop strace tracing the process.
and
$ sudo gdb -p $pid
(gdb) backtrace
and attach both the file and the backtrace to this report?
Can you still reproduce this? If so, can you please make it hang and than check the process id of the haning gksu? With that, you can run:
$ sudo strace -p $pid 2> /tmp/gksu.strace
(where $pid is the number, eg 1234)
Leave it runing for a bit and then press CTRL-C to stop strace tracing the process.
and
$ sudo gdb -p $pid
(gdb) backtrace
and attach both the file and the backtrace to this report?
Thanks,
Michael