Won't let me enter a room.

Asa Wilson's Avatar

Asa Wilson

02 Mar, 2009 02:46 PM

I just updated to the latest propane this weekend. Now, whenever I try to join one of our rooms the app hangs and the room just says 'Connecting...'. It does allow entry to other rooms, however. I can join the inaccessible room with no problem through campfire on the web.

  1. Support Staff 1 Posted by trevor on 02 Mar, 2009 03:44 PM

    trevor's Avatar

    Hi Asa,

    this is certainly odd, esp the fact that it's just one of your rooms.

    If you open Console.app are there any messages from Propane in the Sender column?

    Regards, Trevor

  2. 2 Posted by Asa Wilson on 03 Mar, 2009 01:51 PM

    Asa Wilson's Avatar

    Well yes.. But the successful and unsuccessful rooms look the same. From app start-up to room joining.

    It's the only room that is recently active, but not the only one with Room participants. It has a title with a "%" in it... (Grasping at straws!)

  3. Support Staff 3 Posted by trevor on 03 Mar, 2009 11:20 PM

    trevor's Avatar

    Hi Asa,

    the % character might (in some strange way) be an issue but I would have expected console.app to log an exception. Even so, can you tell me the exact text of the topic containing the '%' character so that I can replicate it here.

    You mention that it's only one room (and always the same room). Are you the only Propane user unable to access that room?


  4. 4 Posted by Asa Wilson on 03 Mar, 2009 11:27 PM

    Asa Wilson's Avatar

    Sure the room topic changes fairly regularly. Right now its: '60.4% Code Coverage' The number changes often (going up of course!).

    There is one other propane user (also on the latest version), but he has no trouble getting in the room.

    If you can't replicate the problem perhaps I can just get an old version of the app and wait a version to upgrade. Maybe the magical mystery will have absolved itself by then?

  5. Support Staff 5 Posted by trevor on 04 Mar, 2009 06:49 AM

    trevor's Avatar

    Hi Asa,

    I'm not able to reproduce it here but I also don't like the idea of downgrading you just hoping that somehow it'll fix itself. There must be a legitimate reason it's happening to you and not to your colleague.

    There is one thing we can try. The current version of Propane stores all of the campfire settings into plist files under Library/Application Support/Propane/hosts. So if the campfire host is called 'barnacle' then I'd expect a barnacle.plist file to appear in the hosts directory.

    Completely quit from Propane and then move the probematic host's plist file to another directory. When you restart Propane the host won't be in your list so go ahead and add it.

    First of all, take note of whether or not you're prompted to give your login details. If you're not asked for login details this is significant.

    Next, take note of the lobby listing for the host - does the offending room say anything about being 'locked'?

    And finally, by some (infuriating) magic, are you now able to access the offending room?

    Depending on the answers to this test I may prepare a special build of Propane that does super-verbose logging so that we can track down exactly where it's failing for you.

    Really sorry about this. Trev

  6. 6 Posted by Asa Wilson on 04 Mar, 2009 11:48 AM

    Asa Wilson's Avatar

    I renamed the plist to plist.bak When I started propane it asked for the host and for login information. And no magic here, still did not let me enter that room and still does let me enter the other rooms. The room did not say anything about being locked.

  7. Support Staff 7 Posted by trevor on 05 Mar, 2009 04:43 AM

    trevor's Avatar

    Hi Asa,

    I'm so sorry this is taking so long for me to track down - I'm suffering from a really nasty cold/flu - I'm really not myself right now...

    Anyhow, I've prepared a special debug build of Propane for you to try (I hope that's okay, I feel kind-of bad asking you to jump through these hoops):

    You can find the build at http://propaneapp.com/appcast/asa.zip - inside the zip file is your version of Propane but don't overwrite your currently installed version (at least not at first). Just unpack it to the desktop or something benign like that.

    You'll need to quit Propane if it's running and then from a command-shell (i.e. Terminal.app) you'll need to enable the extended logging:

    defaults write com.protocool.Propane verboseRoomDelegate -bool YES

    Once that's done, open Console.app and clear the display. Then start the 'asa' version of Propane and try to open the offending room. Try to let it load for at least a minute or two to give any network-timeout issues a chance to resolve.

    Once you're satisfied that the offending room has completely stalled (or successfully loaded!), select all of the lines in Console.app and command-c to copy them to the clipboard. You can then paste the lines into any text editor and attach that file to a message in here.

    (There should be a lot of debug lines so a screen capture is not going to be the best way to show it to me).

    Finally - and this is super important. If for some reason this build loads that room (can't see it happening but you never know...) you must disable the extended logging and quit/restart Propane. Otherwise it will rapidly fill up your logfiles as it spits out debug every 3 seconds.

    You disable the logging as such:

    defaults write com.protocool.Propane verboseRoomDelegate -bool NO

    Let me know how this works out for you and again, I'm really sorry I haven't been able to quickly address this problem.


  8. 8 Posted by Sean Abrahams on 22 Mar, 2009 07:46 PM

    Sean Abrahams's Avatar

    I started having this exact problem today, except that I can't access any of my rooms. I'm running Mac OS X 10.5.6 and Safari 4 beta. I haven't changed my setup in any way for the past few weeks.

    I deleted Library/Application Support/Propane and re-installed with no luck.

    I downloaded the special build above and followed the steps. Attached is my output from the console.

  9. Support Staff 9 Posted by trevor on 23 Mar, 2009 06:30 AM

    trevor's Avatar

    Hi Sean,

    thanks for sending me the log through.

    There's one very critical event missing from the log file - namely that WebKit is never reporting that the room's html dataSource (the html file for the room) has finished loading, nor is it reporting that the entire page (including all assets) has finished loading either.

    There are two events that Propane watches out for during load - the first is a didFinishLoadForFrame, which is WebKit saying the page has fully loaded. The second is a request to the Campfire polling URL.

    Once either of those events occurs then Propane will install its callbacks into the running campfire and it will remove the translucent 'shield' (who's job is to block access to a partially-initialized chat room).

    Prior to this point, everything is in the hands of WebKit and if neither of those events fires then the chat is most certainly not 'running' and there's not much I can do to overcome that situation...

    So... with that background out of the way, I have to wonder if this is related to the strange "safari swallows my cookies" issues that (I've heard) still occasionally happen even under Safari 4 beta. In addition to login details being lost, some people have complained that all they periodically just get blank pages.

    I've personally never been able to reproduce it but I have seen reports of people correcting the problem by quitting all webkit-based applications (fluid, Propane etc), clearing cookies in Safari, and then quitting Safari. Apparently webkit-based applications will start correctly after that.

    I'm afraid I don't know if it requires removing all cookies (which would be annoying) or if you can just remove all cookies for *.campfirenow.com domains.

    Would you be willing to try this out?

    Oh, and Asa (the original reporter of the problem), if you're paying attention here, do you still suffer from this problem?

    Regards, Trev

  10. 10 Posted by Sean Abrahams on 23 Mar, 2009 06:39 AM

    Sean Abrahams's Avatar

    Thanks for the excellent response Trev. Clearing the cookies for *.campfirenow.com worked. I did not need to restart Safari or Webkit (I use both).

    I hope this helps others in the future. Propane is an excellent app. Time for me to buy it :-)

  11. 11 Posted by Asa Wilson on 01 Apr, 2009 09:22 PM

    Asa Wilson's Avatar

    Hey there,

    Just checking to see if you had any further ideas about this bug. I
    sent back the output of my log files did you get them? Clearing
    cookies and all that did not help at all.


    -- Asa Wilson [email blocked]

  12. Support Staff 12 Posted by trevor on 01 Apr, 2009 09:30 PM

    trevor's Avatar

    Hi Asa,

    sorry but no, I didn't get your log files - are you able to re-send them?

    Regards, Trev

  13. trevor closed this discussion on 16 Jan, 2010 10:05 AM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? 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