With a recent update to 7.10 (sorry, I don't know which one) I am now
able to connect via XDMCP. Curiously, netstat shows XDM listening on
udp6:177 like before, but (for whatever reason) it is now working!
--
XDMCP lstening on udp6 instead of udp
https://bugs.launchpad.net/bugs/58071
You receive
More: I upgraded my box to Fiesty and still see the problem. I allowed
the upgrade to overwrite the configuration files and then made the
required changes and kdm is still on udp6:177. I just noticed that sshd
is listening on tcp6:22 as well. I, again, disabled ipv6 per Jesse's
suggestion and s
FWIW: I see the same thing with Edgy. Jesse's changes above disabled
IPV6 and I see kdm listening on udp:177, but I still can't connect via
XDMCP (and yes, I've enabled it in kdmrc, Xaccess, etc).
--
XDMCP lstening on udp6 instead of udp
https://bugs.launchpad.net/bugs/58071
You received this bu
*** This bug is a duplicate of bug 45819 ***
Very quick turn-around - thank you! Since this is a duplicate, could
you post the original bug number so I can follow its progress? Thanks!
--
Typing a path in "Browse icons" closes dialog
https://launchpad.net/bugs/54702
--
ubuntu-bugs mailing lis
Public bug reported:
Attempting to type a path name into the "Browse icons" dialog causes the
dialog to close. I see this behavior in 6.06 (Dapper).
After playing with this for a bit, I believe I see what is happening:
As I type, the current path is being interpreted so that icons in that
path w
