Sequel Pro - doesn't open at all...

[colin]

I've done some searching and haven't found a solution to this.

When i open Sequel Pro, it bounces on the doc for a second, then
closes. It doesn't get to any screen, doesn't "unexpectedly quit",
doesn't do anything, really - it's bizarre.

i tried trashing the application, and installing a new one - no dice.
i tried it using a fresh / new user on my machine, no problems there -
works like a charm.
so, i deleted the pref files in ~/Library/preferences/ but still won't
open.

here's a vid of the behavior:
http://screencast.com/t/ksTtedJbNg0j

If anyone has any clue how to fix this i'd be forever grateful.
Sequel Pro is just so much better than PHP MyAdmin that i may have to
find a new career if i can't get this to work....

i'm on Lion, although my laptop is also on lion and the program works
okay on it.

[Jakob Egger]

A few more details would be helpful:

1) Check Console.app (it's in the utilities folder). Are there any messages from Sequel Pro? Without this information it is almost impossilble to know what's going on.

2) Which version of SP are you using, what Mac do you have, and what version of Lion is installed?

Best regards,
Jakob

> --
> You received this message because you are subscribed to the Google Groups "Sequel Pro" group.
> To post to this group, send email to seque...@googlegroups.com.
> To unsubscribe from this group, send email to sequel-pro+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/sequel-pro?hl=en.
>

[colin]

Thanks Jakob.

here's what console / crash report says:

https://gist.github.com/1528110

honestly, none of that makes sense to me.

I am using Sequel Pro 0.9.9.1, on Mac OS X Lion 10.7.2. I have a
2x2.66GHZ Dual Core Mac Pro.

[Rowan Beentje]

Hi Colin,

Thanks for that report. It looks like Sequel Pro is attempting to open a previous file of some kind automatically on startup, and choking because it's calling a document-based code path that we haven't implemented - because our "document" support is faked just to the bare minimum. So it'd be nice to work out what's triggering this code path to work out what we might actually have to implement :)

Can you remember when the app broke for you? Had you been using connection files, session files, .sql files just beforehand?

So I think the relevant user-specific data that might be breaking it for you is the saved state information. Could you try emptying (but keeping the files within, to send to me perhaps?) the data? It's kept in ~/Library/Saved Application State/com.google.code.sequel-pro.savedState .

Hope that helps,
Rowan

[colin]

Rowan -

Yeah, the fact that it works on another account on the same machine
would indicate that it's user-based.
Honestly, I don't remember the last time it was working - it broke
probably in the summer and i've just been using my work computer or
laptop a lot since then...i'm sure i'd been using .sql or a connection
file though.

when i get back home, i'll try your suggestion and see what happens.

Really appreciate the quick responses -

colin

[colin]

removing the files in com.google.code.sequel-pro.savedState seemed to
do the trick. do you want to check the files out?

[Rowan Beentje]

Hi Colin,

Good to hear that was the root cause. If you could send us the files, that'd be great (my email address above - rowan at beent.je - is as good a place as any); I don't believe they contain any connection details, but it's possible that it would contain the contents of the custom query field; if this is a concern, just sending the .plist file would be useful, as that's an index to the other files (with file names, window positions etc) and may have enough information to provide a pointer to the problem.

Thanks,
Rowan