Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

inputbox don't send the text #62

Closed
zadr opened this issue Mar 14, 2005 · 15 comments
Closed

inputbox don't send the text #62

zadr opened this issue Mar 14, 2005 · 15 comments

Comments

@zadr
Copy link
Contributor

zadr commented Mar 14, 2005

Issue migrated from trac ticket # 62

component: Colloquy (Mac) | priority: Normal | resolution: Fixed

2005-03-14 10:40:48: knuterik@tenthumbs.net created the issue


had a problem with the text on the input box not getting sent when i hit return, but only on the connection to freenode, where i could not send to any channel or to console. the inputboxes for my simultanious connection to quakenet worked just fine. i have had this error happening several. Disconnecting freenode and reconnecting using the "connections" window, seemed to fix it after a couple of attemts, while quitting colloquy and restarting it gave me the same error on the same connection (freenode). I'm have set colloquy to connect automatically to quakenet and the freenode at startup.

@zadr
Copy link
Contributor Author

zadr commented Mar 17, 2005

2005-03-17 14:39:36: novaa commented


I also see this sometimes (also with a simultaneous connection to Quakenet where everything works), mostly a restart of colloquy helps. I can say that its not Terminal.app with its secure input (which bugged me with bf-1942) If I find a way to reproduce this i will post it here.

@zadr
Copy link
Contributor Author

zadr commented Apr 4, 2005

2005-04-04 09:25:04: nightstalker commented


i also have this problem from time to time. iirc it happens only after waking from sleep here, a manual reconnect or autoconnect on startup dont seem to cause it...

@zadr
Copy link
Contributor Author

zadr commented May 12, 2005

2005-05-12 18:23:03: timothy changed status from new to closed

@zadr
Copy link
Contributor Author

zadr commented May 12, 2005

2005-05-12 18:23:03: timothy changed resolution from ** to fixed

@zadr
Copy link
Contributor Author

zadr commented May 12, 2005

2005-05-12 18:23:03: timothy commented


I think this has been fixed for a while. Reopen it is happens again.

@zadr
Copy link
Contributor Author

zadr commented Mar 8, 2006

2006-03-08 09:44:57: autoxr commented


Happens to me with latest nightly and experimental. Doesn't happen often, but it'll randomly happen when I connect to my proxy. Maybe 1 in 10 or 20 times. Sometimes disconnecting/reconnecting works, sometimes it doesn't and then I have to quit relaunch. That usually clears it up.

@zadr
Copy link
Contributor Author

zadr commented Mar 8, 2006

2006-03-08 09:44:57: autoxr changed status from closed to reopened

@zadr
Copy link
Contributor Author

zadr commented Mar 8, 2006

2006-03-08 09:44:57: autoxr changed resolution from fixed to **

@zadr
Copy link
Contributor Author

zadr commented Jun 13, 2006

2006-06-13 20:17:52: rinoa commented


Are there any exceptions in the system console when this problem occurs?

@zadr
Copy link
Contributor Author

zadr commented Jul 10, 2006

2006-07-10 09:07:15: @akempgen commented


making #366 a duplicate of this one

@zadr
Copy link
Contributor Author

zadr commented Jul 14, 2006

2006-07-14 17:55:40: @akempgen commented


jruderman had

2006-07-14 13:40:56.949 Colloquy[10205] setGroupIdentifier:: _NSUndoStack 0x4f1260 is in invalid state, calling setGroupIdentifier with no begin group mark

in his console during this bug

@zadr
Copy link
Contributor Author

zadr commented Sep 24, 2007

2007-09-24 20:04:58: Rinoa commented


Also see #1105

@zadr
Copy link
Contributor Author

zadr commented Sep 24, 2007

2007-09-24 23:36:00: timothy changed status from reopened to closed

@zadr
Copy link
Contributor Author

zadr commented Sep 24, 2007

2007-09-24 23:36:00: timothy changed resolution from ** to fixed

@zadr
Copy link
Contributor Author

zadr commented Sep 24, 2007

2007-09-24 23:36:00: timothy commented


Fixed in [3740].

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant