Log file created on Mon May 14 15:00:18 MDT 2007 IMPORTANT: Because updating this file after every log message would kill performance, it will be *incomplete* unless you invoke the Utilities->Troubleshooting->Update Activity Log on Disk command! [message] Log: When reporting bugs, please include the following information: [message] Log: java.version=1.6.0 [message] Log: java.vm.version=1.6.0-b105 [message] Log: java.runtime.version=1.6.0-b105 [message] Log: java.vendor=Sun Microsystems Inc. [message] Log: java.compiler=null [message] Log: os.name=Windows XP [message] Log: os.version=5.1 [message] Log: os.arch=x86 [message] Log: user.home=C:\Documents and Settings\cboal [message] Log: java.home=C:\Program Files\Java\jdk1.6.0\jre [message] Log: java.class.path=C:\Program Files\jEdit\jedit.jar [notice] jEdit: An error occurred while connecting to the jEdit server instance. [notice] jEdit: This probably means that jEdit crashed and/or exited abnormally [notice] jEdit: the last time it was run. [notice] jEdit: If you don't know what this means, don't worry. [notice] jEdit: java.net.ConnectException: Connection refused: connect [notice] jEdit: at java.net.PlainSocketImpl.socketConnect(Native Method) [notice] jEdit: at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) [notice] jEdit: at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) [notice] jEdit: at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) [notice] jEdit: at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) [notice] jEdit: at java.net.Socket.connect(Socket.java:519) [notice] jEdit: at java.net.Socket.connect(Socket.java:469) [notice] jEdit: at java.net.Socket.(Socket.java:366) [notice] jEdit: at java.net.Socket.(Socket.java:208) [notice] jEdit: at org.gjt.sp.jedit.jEdit.main(jEdit.java:249)

What happens if you start jedit with the -noserver option instead?

When you installed jEdit, did you use the Windows installer? If so, did you select to not have the server start up? If that's the case, try re-installing jEdit with the Windows installer and leave that option checked.

Again, I'm not on windows, so I'm sorry I'm not much help.

You could also post your issue to the user's mailing list.

Learn from the past. Live in the present. Plan for the future.

Yes I am positive I removed my .jedit file. In fact I accidentally lost my macros as I failed to properly back it up.

I also uninstalled it and and re-installed it with the start server automatically option checked. I rebooted my machine and now it will not open up at all.

I then tried to run it with the -noserver option and it at least opens up but when I try and resize it I get the same connection error in the activity log and it closes. Here is the command I used:

"C:\Program Files\Java\jdk1.6.0\bin\javaw.exe" -Xms64M -Xmx192M -jar "C:\Program Files\jEdit\jedit.jar" -noserver

Here is the default command associated with the shortcut:

"C:\Program Files\Java\jdk1.6.0\bin\javaw.exe" -Xms64M -Xmx192M -jar "C:\Program Files\jEdit\jedit.jar" -reuseview

I have also tried uninstalling and reinstalling java.

Very strange.

Someone please correct me if I'm wrong here, it's been years since I've done any development on Windows.

Try executing the command using java instead of javaw. If I remember correctly, the javaw basically disconnects the process from the console. Maybe you're getting some error that's not in the Activity.log.

I don't know if you're using another IDE for java development, but I have gotten jEdit to run in Eclipse under debug mode. It's extreme, but if it's definitely not working for you, and you want to try it....


Learn from the past. Live in the present. Plan for the future.

The lines from ActivityLog that You've copied for us do only log the beginning of jEdit's startup. They show absolutely no error - like the Log says itself "Don't worry" .

If You had hope that the crash is logged, You have to open the activity.log with another editor before jEdit is restarted and look for the last lines in the file.

But now regarding the real problem - it's weird:
Look at "Global Options -> Appearence" and deactivate the last 3 options.
Propably You could find suspicious options for the system's graphic adapter - try change them.