@ 7LeagueBoots,
The Nightly LinkGrabber grabs what it thinks is the source HTML for the text you have copied, assuming that your browser copies both the text/plain and text/html versions to the clipboard. If your browser does not follow that convention.
1) What browser are you using. JD may have to exclude that browser from extended clipboard monitoring (only text/plain). Make sure you are not using a clipboard program separate from the normal clipboard program for your OS (these are often used to store your clipboard history, so you can go back and re-use old entries).
2) Please describe how you are copying and give examples of what you are copying. Try this for multiple hosts.
3) Start JD using the Emergency Log procedure (General Discussion -> Self Help Index -> Posting an Emergency Log).
4) Do some copying. Look for circles at the bottom of the window (in the Status Bar). They should fill with green as they process. Exit JDownloader when you are done or 5 minutes after you think it has frozen.
5) Describe your antivirus and firewall setup. What are your settings at the bottom of the page.
6) Include all of the information except for the log in a message (do not send it yet). Check the Hoster Plugins rules for any other recommended information that might apply to this situation.
7) Edit the 2 txt files created by the Emergency Log procedure to make sure the files do not contain your password.
8) Create an archive containing the txt files and any HS_err*.log files that you find in your JDownloader directory. Attach the archive to the message (from 6) - you may have to click on Go Advanced and Manage Attachments.
9) After the attachment is on the message, post the message.
10) PM the URI (web address) of the page and your login information to Jiaz. Your login information will only be used for fixing this bug (Jiaz will preserve the privacy of your information).
I know this seems like a lot, but the previous messages have been missing a lot of information and this is the best way to provide it. Jiaz might have to try to reproduce the problem with a network monitor such as WireShark or a special clipboard monitor.
|