Jump to content

msfgui java error


Pwnd2Pwnr

Recommended Posts

After Googling the issue, I found that there is no real answer to my issue (from Metasploits end, anyway.). I recently had the msfgui crash on me. Now, when I try to bring it back up, I get this error...

__________________________________________________________________________________________________________________

Dec 15, 2012 8:08:21 AM org.jdesktop.application.Application$1 run

SEVERE: Application class msfgui.MsfguiApp failed to launch

java.lang.NullPointerException

at msfgui.MsfFrame.setLnF(MsfFrame.java:29)

at msfgui.MainFrame.<init>(MainFrame.java:49)

at msfgui.MsfguiApp.startup(MsfguiApp.java:126)

at org.jdesktop.application.Application$1.run(Application.java:171)

at java.awt.event.InvocationEvent.dispatch(Unknown Source)

at java.awt.EventQueue.dispatchEventImpl(Unknown Source)

at java.awt.EventQueue.access$000(Unknown Source)

at java.awt.EventQueue$3.run(Unknown Source)

at java.awt.EventQueue$3.run(Unknown Source)

at java.security.AccessController.doPrivileged(Native Method)

at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source)

at java.awt.EventQueue.dispatchEvent(Unknown Source)

at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)

at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)

at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)

at java.awt.EventDispatchThread.pumpEvents(Unknown Source)

at java.awt.EventDispatchThread.pumpEvents(Unknown Source)

at java.awt.EventDispatchThread.run(Unknown Source)

Exception in thread "AWT-EventQueue-0" java.lang.Error: Application class msfgui.MsfguiApp failed to launch

at org.jdesktop.application.Application$1.run(Application.java:177)

at java.awt.event.InvocationEvent.dispatch(Unknown Source)

at java.awt.EventQueue.dispatchEventImpl(Unknown Source)

at java.awt.EventQueue.access$000(Unknown Source)

at java.awt.EventQueue$3.run(Unknown Source)

at java.awt.EventQueue$3.run(Unknown Source)

at java.security.AccessController.doPrivileged(Native Method)

at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source)

at java.awt.EventQueue.dispatchEvent(Unknown Source)

at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)

at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)

at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)

at java.awt.EventDispatchThread.pumpEvents(Unknown Source)

at java.awt.EventDispatchThread.pumpEvents(Unknown Source)

at java.awt.EventDispatchThread.run(Unknown Source)

Caused by: java.lang.NullPointerException

at msfgui.MsfFrame.setLnF(MsfFrame.java:29)

at msfgui.MainFrame.<init>(MainFrame.java:49)

at msfgui.MsfguiApp.startup(MsfguiApp.java:126)

at org.jdesktop.application.Application$1.run(Application.java:171)

... 14 more

_________________________________________________________________________________________________________________

I do not know what caused the issue (besides a Java event, of course). But, whenever I go to start the msfgui with sudo (~$sudo msfgui ), this error pops up every time. I deleted it and reinstalled it, but no change...

Any help would be appreciated!

Link to comment
Share on other sites

What happens if you try msfconsole? Or install Armitage, if you want a metasploit GUI interface? Possible your metaploit is up to date, but your java is out of date? Just pullign straws, but try apt-get update and apt-get upgrade, see what happens.

Link to comment
Share on other sites

... Armitage works... Which is surprising because my .yml wasn't configured. Must be the 4.5.0 update. I guess I will take Mudges version of the gui :lol: . Msfconsole is working too!

Oddly enough; the gui is still failing... strange brew, ey?

Link to comment
Share on other sites

Possible an update broke something somewhere is my guess, or even the GUI had an update pushed that has a bug or something is even corrupt. personally I hate java, on anything, but In BackTrack, i use it in a VM mostly, so if it gets whacked, I can always revert to a snapshot. Native installs are a bitch to trouble shoot, and linux in general is still greek to me for the most part, so when things bork I either reinstall everything thats failing, or try work arounds, like Armitage.

Link to comment
Share on other sites

My point was, with a VM, I can easily undo or revert back to prior to where things go whacky. With a native install, not so easy to revert or pinpoint where the problem is. If I am in a VM and I update something and then something else breaks, and I can revert, rinse, repeat, I can see where the problem is and what is causing it. With a native install, and no way to easily revert to a working state, good luck figuring it out. ;)

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...