Propane stalls on the "Connecting" message

Katherine Mereand's Avatar

Katherine Mereand

29 Sep, 2009 07:56 PM

Hi there,

The situation is rather odd; about half the time my laptop has to log into a VPN, but one that still allows connections to the outside world (Tweetie, Safari, etc all work fine). When I launch Propane (or especially, when I wake up the laptop in the VPN network) it will browse the chatrooms of my campfire site, and will log into Campfire, but will stall with "Connecting". After it does this, it won't work anywhere, even in a non-VPN network. I essentially have to remove it and all the preference files, and reinstall it.

Please help!

  1. Support Staff 1 Posted by trevor on 29 Sep, 2009 08:35 PM

    trevor's Avatar

    Hi Katherine,

    that is odd.

    The first question I have to ask is: once Propane has stopped working in the VPN, are you able to access your campfire chats with Safari (not Firefox, Safari specifically)?

    An even more relevant test might be... what happens if you join a chat in Safari, go to sleep, and then wake up in the VPN. Does Safari get confused too? The reason I ask is because, for the most part, Propane is just a wrapper around the Safari WebKit engine.

    When you say "remove it and all the preference files" - do you mean you're just removing the app bundle and ~/Library/Preferences/com.protocool.Propane.plist or are you also having to remove the contents of ~/Library/Application\ Support/Propane/ as well?

    Are you absolutely sure it's the removal of the app and those files that fixes it? I'm a bit incredulous because those steps just don't make sense. Is it just removing the config files or just removing the app bundle that achieves the same result?

    Also, you say it stalls with "Connecting" - the window that displays that message is translucent so if anything had partially loaded you would be able to see a ghostly image of the chat behind the "connecting" message. Is anything displayed there or is it just white?

    Another thing I'm interested in: Propane caches the rooms to display in the lobby (command-o to show it). If the items in the lobby listing just have the room title and topic (as in they don't say "unoccupied" or they don't list the current users) then you haven't actually connected. Do the items in the lobby listing show current chat participants (or "unoccupied")?

    If the lobby shows participants, what happens if you click the menu item of Lobby -> Open Files & Transcripts? Is it just a blank page that never finishes loading?

    If the Files & Transcripts page doesn't load after a minute or so, open Console.app (in your utilities folder) and look for entries that say "Propane". If there are any, please cut and paste them in your reply here.

    Sorry for asking so many questions - it's such a strange behaviour that I'm unsure where the root of the problem may be. It may take us a bit of to-ing and fro-ing to track it down.

    Regards, Trev

  2. Support Staff 2 Posted by trevor on 29 Sep, 2009 10:33 PM

    trevor's Avatar

    Hi again Katherine,

    I've been doing some digging and found some old (2006) complaints about Safari (i.e. WebKit, the same rendering engine used by Propane) failing to load https pages with a cisco VPN. It was related to SSL certificates failing to validate properly.

    I'm not sure if that issue was ever addressed, so if it's still a problem then Safari would suffer the same way that Propane is. So testing against Safari is definitely a good starting point.

    Another thought occurred to me: I wonder if the DNS cache is messed-up somehow, especially when you wake from sleep into the VPN.

    As such, another test might be to quit Propane, Safari, and any other WebKit-based apps such as MailPlane that you might be running when you enter the VPN. Once they've all exited, type the following command in Terminal.app:

    dscacheutil -flushcache

    After that, restart Propane and see if it manages to reconnect properly.

    Regards, Trev

  3. 3 Posted by Barb Dybwad on 12 Nov, 2009 03:47 AM

    Barb Dybwad's Avatar

    I'm having the same issue with the stall on "connecting." In answers to your questions:

    *) yes I can see a "ghost" of the chat behind the connecting message although it's paged back a bit and not the most current stuff (attaching image)

    *) I can view transcripts from the lobby just fine, which seems to correctly update with room participants and room topic. also, other users in the chat report seeing that i've entered the room.

    *) i found these two error lines in Console.app relating to Propane:

    11/11/09 7:28:49 PM Propane[20280] CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.

    11/11/09 7:28:54 PM Propane[20280] *** WebKit discarded an uncaught exception in the webView:didFinishLoadForFrame: delegate: [ valueForUndefinedKey:]: this class is not key value coding-compliant for the key userID.

    *) flushing the cache didn't solve the problem... but then i don't usually use a VPN so this issue may be unrelated

    Any help appreciated... thanks!

  4. Support Staff 4 Posted by trevor on 12 Nov, 2009 05:20 AM

    trevor's Avatar

    Hi Barb,

    sorry about the problems you're having here.

    First of all, the screenshot looks like you've spoken some messages in the room - was that from in Propane or did you have to use another browser?

    Next, I need to understand a bit more about the "valueForUndefinedKey" exception, and for that it would be great if you could complete these steps.

    1 - make sure you're not running Propane
    2 - open Console.app and take a note of the last timestamp of any Propane log messages. We just want to make sure we know which are the old messages so we can ignore them.
    3 - keeping Console.app open, start Propane.
    4 - assuming it's still hanging on the "connecting" screen, wait at least 60 seconds
    5 - press the reload button in Console.app
    6 - copy all of the Propane messages that have appeared since step 2 and paste them back here.

    Also, could you tell me what version of OS X, Propane, and Safari you're running.

    Oh and finally, does Campfire work in Safari for you? If so, what value do you get back if you 'speak' the following message:

    /eval window.chat.userID
    

    (by the way, that won't get sent to everyone in the room, it's just in your browser).

    Sorry for all the demands from you, but it will really help to confirm some suspicions.

    Regards, Trev

  5. 5 Posted by Barbara Dybwad on 19 Nov, 2009 01:45 AM

    Barbara Dybwad's Avatar

    Hey there -- apologies for the delay, it's been a crazy week. Replies below:

    On Wed, Nov 11, 2009 at 9:20 PM, trevor <
    [email blocked]<tender%[email blocked]>
    > wrote:

  6. Support Staff 6 Posted by trevor on 19 Nov, 2009 04:15 AM

    trevor's Avatar

    Sorry Barb,

    most of your message didn't make it through.

    When replying by email you have to keep all of your text above the "Add your reply above here" line because everything below that is stripped by Tender.

    Regards, Trev

  7. 7 Posted by Barbara Dybwad on 19 Nov, 2009 05:35 PM

    Barbara Dybwad's Avatar

    oh wow, totally missed that. ok, take 2:

    From: trevor
    > Subject: Propane stalls on the "Connecting" message
    >
    > Hi Barb,
    >
    > sorry about the problems you're having here.
    >
    > First of all, the screenshot looks like you've spoken some messages in the
    > room - was that from in Propane or did you have to use another browser?
    >

    Yes, those message were from another instance -- I had started using
    Campfire in Fluid when Propane went wonky... but it won't send audio
    notifications for some reason, and for many other reasons I'd prefer Propane
    back! ;)

    >
    > Next, I need to understand a bit more about the "valueForUndefinedKey"
    > exception, and for that it would be great if you could complete these steps.
    >
    > 1 - make sure you're not running Propane
    > 2 - open Console.app and take a note of the last timestamp of any Propane
    > log messages. We just want to make sure we know which are the old messages
    > so we can ignore them.
    > 3 - keeping Console.app open, start Propane.
    > 4 - assuming it's still hanging on the "connecting" screen, wait at least
    > 60 seconds
    > 5 - press the reload button in Console.app
    > 6 - copy all of the Propane messages that have appeared since step 2 and
    > paste them back here.
    >

    Since I haven't tried to troubleshoot in the past week there are 0 instances
    of Propane in the log over the recorded interval (since 11/12).

    Followed the above and immediately got a string of Safari errors followed by
    those same Propane errors from before:

    11/18/09 5:35:37 PM Safari[3910] -[WebIconMenuItem
    accessibilityAttributeNames]: unrecognized selector sent to instance
    0x11592db40
    11/18/09 5:35:37 PM Safari[3910] -[WebIconMenuItem
    accessibilityAttributeNames]: unrecognized selector sent to instance
    0x132c03690
    11/18/09 5:35:37 PM Safari[3910] -[WebIconMenuItem
    accessibilityAttributeNames]: unrecognized selector sent to instance
    0x132c82fb0
    11/18/09 5:35:37 PM Safari[3910] -[WebIconMenuItem
    accessibilityAttributeNames]: unrecognized selector sent to instance
    0x12f228100
    11/18/09 5:35:37 PM Safari[3910] -[NSMenuItem accessibilityAttributeNames]:
    unrecognized selector sent to instance 0x12f161cf0
    11/18/09 5:35:37 PM Safari[3910] -[WebIconMenuItem
    accessibilityAttributeNames]: unrecognized selector sent to instance
    0x132cdca30
    11/18/09 5:35:37 PM Safari[3910] -[WebIconMenuItem
    accessibilityAttributeNames]: unrecognized selector sent to instance
    0x12f2a7ed0
    11/18/09 5:35:37 PM Safari[3910] -[WebIconMenuItem
    accessibilityAttributeNames]: unrecognized selector sent to instance
    0x1263e6b40
    11/18/09 5:35:37 PM Safari[3910] -[WebIconMenuItem
    accessibilityAttributeNames]: unrecognized selector sent to instance
    0x12afbe170
    11/18/09 5:35:37 PM Safari[3910] -[WebIconMenuItem
    accessibilityAttributeNames]: unrecognized selector sent to instance
    0x12c7bcaf0
    11/18/09 5:35:37 PM Safari[3910] -[WebIconMenuItem
    accessibilityAttributeNames]: unrecognized selector sent to instance
    0x132ce2df0
    11/18/09 5:35:37 PM Safari[3910] -[WebIconMenuItem
    accessibilityAttributeNames]: unrecognized selector sent to instance
    0x12c7e54c0
    11/18/09 5:35:37 PM Safari[3910] -[WebIconMenuItem
    accessibilityAttributeNames]: unrecognized selector sent to instance
    0x1159e8fb0
    11/18/09 5:35:37 PM Safari[3910] -[WebIconMenuItem
    accessibilityAttributeNames]: unrecognized selector sent to instance
    0x13696d3e0
    11/18/09 5:35:37 PM Safari[3910] -[WebIconMenuItem
    accessibilityAttributeNames]: unrecognized selector sent to instance
    0x128779510
    11/18/09 5:35:37 PM Safari[3910] -[WebIconMenuItem
    accessibilityAttributeNames]: unrecognized selector sent to instance
    0x12af23ea0
    11/18/09 5:35:37 PM Safari[3910] -[NSMenuItem accessibilityAttributeNames]:
    unrecognized selector sent to instance 0x11b8f2de0
    11/18/09 5:35:37 PM Safari[3910] -[WebIconMenuItem
    accessibilityAttributeNames]: unrecognized selector sent to instance
    0x12f2f5fb0
    11/18/09 5:35:37 PM Safari[3910] -[NSMenuItem accessibilityAttributeNames]:
    unrecognized selector sent to instance 0x12af17c80
    11/18/09 5:35:37 PM Safari[3910] -[WebIconMenuItem
    accessibilityAttributeNames]: unrecognized selector sent to instance
    0x11b90b270
    11/18/09 5:35:37 PM Safari[3910] -[WebIconMenuItem
    accessibilityAttributeNames]: unrecognized selector sent to instance
    0x136926630
    11/18/09 5:35:37 PM Safari[3910] -[WebIconMenuItem
    accessibilityAttributeNames]: unrecognized selector sent to instance
    0x12af224f0
    11/18/09 5:35:37 PM Safari[3910] -[WebIconMenuItem
    accessibilityAttributeNames]: unrecognized selector sent to instance
    0x12f16a3c0
    11/18/09 5:35:37 PM Safari[3910] -[NSMenuItem accessibilityAttributeNames]:
    unrecognized selector sent to instance 0x13690d820
    11/18/09 5:35:37 PM Safari[3910] -[WebIconMenuItem
    accessibilityAttributeNames]: unrecognized selector sent to instance
    0x12f18d5e0
    11/18/09 5:35:37 PM Safari[3910] -[WebIconMenuItem
    accessibilityAttributeNames]: unrecognized selector sent to instance
    0x132c278f0
    11/18/09 5:35:37 PM Safari[3910] -[WebIconMenuItem
    accessibilityAttributeNames]: unrecognized selector sent to instance
    0x12c7103f0
    11/18/09 5:35:37 PM Safari[3910] -[WebIconMenuItem
    accessibilityAttributeNames]: unrecognized selector sent to instance
    0x12f19ba40
    11/18/09 5:35:37 PM Safari[3910] -[WebIconMenuItem
    accessibilityAttributeNames]: unrecognized selector sent to instance
    0x12c729fb0
    11/18/09 5:35:37 PM Safari[3910] -[WebIconMenuItem
    accessibilityAttributeNames]: unrecognized selector sent to instance
    0x1369ede00
    11/18/09 5:35:37 PM Safari[3910] -[WebIconMenuItem
    accessibilityAttributeNames]: unrecognized selector sent to instance
    0x12c7365e0
    11/18/09 5:35:37 PM Safari[3910] -[WebIconMenuItem
    accessibilityAttributeNames]: unrecognized selector sent to instance
    0x1369774d0
    11/18/09 5:35:37 PM Safari[3910] -[WebIconMenuItem
    accessibilityAttributeNames]: unrecognized selector sent to instance
    0x12afd7370
    11/18/09 5:35:37 PM Safari[3910] -[WebIconMenuItem
    accessibilityAttributeNames]: unrecognized selector sent to instance
    0x12c7f1d80
    11/18/09 5:35:37 PM Safari[3910] -[WebIconMenuItem
    accessibilityAttributeNames]: unrecognized selector sent to instance
    0x12873eec0
    11/18/09 5:35:37 PM Safari[3910] -[NSMenuItem accessibilityAttributeNames]:
    unrecognized selector sent to instance 0x127a79610
    11/18/09 5:35:37 PM Safari[3910] -[WebIconMenuItem
    accessibilityAttributeNames]: unrecognized selector sent to instance
    0x12af71540
    11/18/09 5:35:37 PM Safari[3910] -[NSMenuItem accessibilityAttributeNames]:
    unrecognized selector sent to instance 0x12c7dee30
    11/18/09 5:36:10 PM Propane[5121] CFPropertyListCreateFromXMLData():
    Old-style plist parser: missing semicolon in dictionary.
    11/18/09 5:36:27 PM Propane[5121] *** WebKit discarded an uncaught exception
    in the webView:didFinishLoadForFrame: delegate: <NSUnknownKeyException>
    [<DOMHTMLTableSectionElement 0x15064a80> valueForUndefinedKey:]: this class
    is not key value coding-compliant for the key userID

    >
    > Also, could you tell me what version of OS X, Propane, and Safari you're
    > running.
    >

    Versioning: OS X 10.6.1, Propane Version 1.0.2 (1.0.2.00cd7a7), Safari
    Version 4.0.3 (6531.9)

    >
    > Oh and finally, does Campfire work in Safari for you? If so, what value do
    > you get back if you 'speak' the following message:
    >
    > /eval window.chat.userID
    >

    Yes, it does work ok in Safari. Here's what I got from the above:

    >>> window.chat.userID
    476611

    >
    > (by the way, that won't get sent to everyone in the room, it's just in your
    > browser).
    >
    > Sorry for all the demands from you, but it will really help to confirm some
    > suspicions.
    >

    No worries, thanks for the investigation! Let me know if anything turns
    up...

    cheers,
    Barb

    >
    > Regards, Trev
    >
    > View this Discussion online:
    > http://help.propaneapp.com/discussions/propane-bugreports/68-propane-stalls-on-the-connecting-message
    > --
    > Reply with #ignore to stop receiving notifications for this discussion.
    >

  8. Support Staff 8 Posted by trevor on 19 Nov, 2009 06:08 PM

    trevor's Avatar

    Hi again Barb,

    thanks for that - it's valuable information.

    This latest debug from Console.app shows DOMHTMLTableSectionElement barfing over userID, which is different from your initial report.

    The difference is troubling but the good news is that I know exactly what's happening (at least during your latest attempt). Now to figure out why...

    I'll keep you posted.

    Trev

  9. Support Staff 9 Posted by trevor on 24 Nov, 2009 02:00 AM

    trevor's Avatar

    Hi Barb,

    sorry for the delays in getting this resolved.

    Basically, I'm getting callbacks telling me the page has loaded, which should also mean that the chat is also running. That appears to not be the case for you and I haven't been able to recreate the exact same situation you're seeing.

    I've altered the room loading mechanism so that the exception you're seeing won't be triggered and so that it complains about any files that failed to load (I suspect the campfire javascript may not be loading properly).

    I can't say for sure that it will solve the symptom - that it never finishes loading the room - but it is more forgiving of the situation where the chat javascript object has not been created.

    I'm hoping that the worst-case scenario is that it takes a few seconds longer to detect that campfire is running properly (after it starts to poll for messages).

    Sorry for the long update - I just want to set your expectations a bit.

    Here's the build, let me know if it works out for you so that I can roll the changes into the release branch:

    http://propaneapp.com/appcast/PropaneNewLoading.zip

    Regards, Trev

  10. 10 Posted by Barbara Dybwad on 24 Nov, 2009 05:20 PM

    Barbara Dybwad's Avatar

    Hey Trevor,

    Success!! The build you sent worked; the room finally finished fully
    loading. Thanks huge for tracking this down -- I really appreciate it!! Let
    me know if you need any other post-diagnosis from me :)

    Again, thanks!
    -Barb

  11. Support Staff 11 Posted by trevor on 24 Nov, 2009 05:31 PM

    trevor's Avatar

    Great, thanks for your help diagnosing this.

    Regards, Trev

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:

»

Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac