RunTime Exception for copyCurrentSelectionToSystemClipboard()



14 years ago
4 years ago


(Reporter: anil, Assigned: jhpedemonte)


({helpwanted, qawanted})

1.7 Branch
Windows NT
helpwanted, qawanted

Firefox Tracking Flags

(Not tracked)




14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.7.5) Gecko/20041217
Build Identifier: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.7.5) Gecko/20041217

For my application we are using Webclient which has mozilla as embedded browser.
I have used, currentPage.copyCurrentSelectionToSystemClipboard(). At runtime it
throws following exception:

     [java] java.lang.UnsatisfiedLinkError: nativeCopyCurrentSelectionToSystemCl
     [java]     at org.mozilla.webclient.impl.wrapper_native.CurrentPageImpl.nat
iveCopyCurrentSelectionToSystemClipboard(Native Method)
     [java]     at org.mozilla.webclient.impl.wrapper_native.CurrentPageImpl$1.r
     [java]     at org.mozilla.webclient.impl.wrapper_native.NativeEventThread.r

I suspect that i have missed a dll file. Please help me out.

Reproducible: Always

Steps to Reproduce:
1.Enable copyButton from the example given in the test folder. the application using ant
3.Click on the Copy Button

Actual Results:  
Should appropriately copy the selected text to the Clipboard

Expected Results:  
UnsatisfiedLinkError thrown.


14 years ago
Assignee: mozilla.webmaster → general
Component: → General
Product: → Mozilla Application Suite
QA Contact: danielwang → general
Version: other → 1.7 Branch

Comment 1

14 years ago
Seems to be a Embedding issue (with a Java twist).
Component: General → Embedding: APIs
Keywords: helpwanted, qawanted
Product: Mozilla Application Suite → Core
Robin, you forgot to actually reassign the bug...
Assignee: general → jhpedemonte
Component: Embedding: APIs → Java to XPCOM Bridge
QA Contact: general → xpcom-bridge
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.