Unlock button freezes Ubuntu tweak

[matbroadbent]

Hi,

Further to historical bugs https://bugs.launchpad.net/ubuntu-tweak/+bug/367028 and https://bugs.launchpad.net/ubuntu-tweak/+bug/446430, I'm unable to use the "Clean Package/Cache/Config/Kernel" features in Ubuntu Tweak 0.5.0. The only error posted to the command line is:

ERROR:dbus.proxies:Introspect error on :1.65:/com/ubuntu_tweak/daemon: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

I've had no previous problems like this with any 0.4x release

[System = Ubuntu Karmic 9.10 32bit 2.6.31-17-generic. All up to date as of 10/01/10 20:00]

[matbroadbent (mail-matthew-broadbent)]

.....as far as "what happens?" goes: the UI greys out for a few seconds and then returns without having unlocked the features. I've tried running application with gksu etc and there's no difference. If it helps I had granted previous versions of Ubuntu Tweak permission remember sudo authentication password (with the "forever" option).

[Ramsey (ramsey-griffieth)]

I'm having the same problem. I didn't set it to remember my password though, so I don't think that's the problem. The closest bug I've seen to this one involved a dependency issue with policykit and I have that installed.

[Ramsey (ramsey-griffieth)]

Okay. I don't know why I didn't do this in the first place but I restarted my computer and there's no error at all. I'm not sure why this is but it's probably worth noting.

[Ding Zhou (tualatrix)]

Hi, Thanks for your report.

Because you upgraded from 0.4 to 0.5, you ran the 0.4 before, the daemon of 0.4 wasn't exit, it acquired the dbus name of com.ubuntu-tweak.daemon, so the 0.5 can't unlock.

I will improve the daemon of 0.5 to avoid it happen again when the future update to 0.6.

[matbroadbent (mail-matthew-broadbent)]

D'oh! The oldest fix in the book and I missed it. :) How embarrassing - I even work in IT support.

Thanks to Ramsey for the fix; and to TualatriX for the explanation.

[johnhamelink (johnhamelink)]

reboot fixed it for me too