Ticket #62 (closed Defect: fixed)

Opened 4 years ago

Last modified 22 months ago

inputbox don't send the text

Reported by: knuterik@… Owned by: timothy
Priority: Normal Milestone:
Component: Colloquy (Mac) Version: Built Source
Severity: Normal Keywords:
Cc:

Description

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.

Attachments

Sample of Colloquy.txt (3.6 kB) - added by bogo_lode 3 years ago.
sample of colloquy during bug

Change History

Changed 4 years ago by novaa

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.

Changed 4 years ago by nightstalker

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...

Changed 4 years ago by timothy

  • status changed from new to closed
  • resolution set to fixed

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

Changed 3 years ago by autoxr

  • status changed from closed to reopened
  • version changed from 2.0 (2D9) to Built Source
  • resolution deleted

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.

Changed 3 years ago by rinoa

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

Changed 3 years ago by akempgen

making #366 a duplicate of this one

Changed 3 years ago by akempgen

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

Changed 3 years ago by bogo_lode

sample of colloquy during bug

Changed 22 months ago by Rinoa

Also see #1105

Changed 22 months ago by timothy

  • status changed from reopened to closed
  • resolution set to fixed

Fixed in [3740].

Note: See TracTickets for help on using tickets.