App lock when /oper cmd issued
Reported by cmturner2 | February 5th, 2008 @ 12:11 PM | in 1.2.2
When I issue an /oper command to gain operator status the Linkinus client experiences a lock of the general UI. The app will not quit, and must be closed using force quit from the Activity Monitor.
Server is hybrid-7.2.2(SVN) running on ubuntu.
Comments and changes to this ticket
-

cmturner2 February 5th, 2008 @ 12:38 PM
I should have also added this is on Leopard 10.5.1.
-

cmturner2 February 24th, 2008 @ 11:34 PM
Issue still present in 10.5.2.
The UI doesn't "hang" until the command goes through server side. UI still allows the affectation of changing channels that have been previously viewed by changing the right pane to previous content, however text input to any does nothing. Channels that had not been visited when selected will have the right pane showing whatever is was previously (no change). Obviously the UI is using cached information and isn't actually active.
Under 10.5.2 you can now quit Linkinus when it is in this state, where previously you had to go to the Activity Monitor and kill the process.
-

Nicolas Lapomarda April 6th, 2008 @ 08:49 AM
- → State changed from new to open
Hi there
/oper works fine on all the networks i'm oper on.
Can you provide me with a way to reproduce the bug?
Thanks.
-

moa April 16th, 2008 @ 10:06 AM
Hi all,
OSX 10.5.2
Linkinus version: 1.2.1/8656, FreeBSD 6.1, i386
Running hybrid-7.2.2, TLSv1 AES256-SHA-256, port 6697
If you can't set any of this up in a test environment. I'd be willing to create another oper block and let you test it on my server.
You can email me: r.low.in.mt at gmail dot com.
-

Nicolas Lapomarda April 17th, 2008 @ 08:37 AM
- → Milestone changed from 1.3 to 1.2.2
Great, I will email you in the next couple of days as I'd like this to be fixed for the next update.
-

cmturner2 April 17th, 2008 @ 02:08 PM
Just did a vanilla 7.10 install w/the 7.2.2 hybrid apt package and no issues.
In my case this narrows it down to specific configuration and/or build parameters used on the server causing the lock (it was build from src not the apt pkg), or something related to the network environment which I could only speculate on at this stage.
-

cmturner2 April 18th, 2008 @ 01:22 AM
Ok, I have a server set up where you can replicate this as often as you desire.
IP: 24.199.212.172
Nickname: Pullo
Username: Pullo
Real Name: Titus Pullo
/oper curtis testing
You'll get the same lock of (what appears to be) the agent as I do.
It's a non-permanent server, I'll take it down once you've resolved this bug.
-

Nicolas Lapomarda April 18th, 2008 @ 01:25 AM
Awesome. I will take care of this this very weekend; so you can remove the server in a day or two.
Thank you.
-

Nicolas Lapomarda April 19th, 2008 @ 05:12 AM
- → State changed from open to resolved
Fixed, thank you
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
