[Bug 947287] Re: Unable to change status in pidgin

2012-04-10 Thread Sarrvesh
Moving it to confirmed once again since the problem persists even in 12.04 beta 1. ** Changed in: pidgin (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 947287] Re: Unable to change status in pidgin

2012-03-27 Thread Sarrvesh
Yup, the problem is still there even after executing the command sudo dpkg-reconfigure pidgin. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/947287 Title: Unable to change status in pidgin To

[Bug 947287] Re: Unable to change status in pidgin

2012-03-26 Thread Ronny Cardona
I've a fresh install, not and upgraded one and I think that's why can't reproduce it here. What if you do: sudo dpkg-reconfigure pidgin Same result? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 947287] Re: Unable to change status in pidgin

2012-03-20 Thread Sarrvesh
Hi Roney, I think the problem is still there. This is what I did: 1. Open the pidgin window. 2. Click on the drop-down box at the bottom of the window to change the status. What happens here is that the drop-down box expands but closes immediately. If I change the status using the chat

[Bug 947287] Re: Unable to change status in pidgin

2012-03-19 Thread Ronny Cardona
Hi Sarrvesh, I can't reproduce this bug. Would you please try to reproduce it after installing the updates if available? Thanks for reporting this bug. ** Changed in: pidgin (Ubuntu) Status: New = Confirmed ** Changed in: pidgin (Ubuntu) Status: Confirmed = Incomplete -- You

[Bug 947287] Re: Unable to change status in pidgin

2012-03-05 Thread Sarrvesh
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/947287 Title: Unable to change status in pidgin To manage notifications about this bug go to: