Closed Bug 405141 Opened 18 years ago Closed 15 years ago

Logmein plug-in performs an illegal operation [@ npRACtrl!nsQueryInterface::nsQueryInterface+0x518b9]

Categories

(External Software Affecting Firefox :: Other, defect)

Product:
External Software Affecting Firefox
Component:
Other
Platform:
x86
Windows Vista
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: marinebio72, Assigned: marton)

References

(
URL
)

Details

(Keywords: crash, Whiteboard: [logmein])

Crash Data

Attachments

(3 files)

Stack of main thread
6.60 KB, text/plain
Details
screenshot of the current error it throws.
45.13 KB, image/jpeg
Details
installation error screenshot
43.82 KB, image/jpeg
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9b2pre) Gecko/2007112305 Minefield/3.0b2pre Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9b2pre) Gecko/2007112305 Minefield/3.0b2pre The Logmein Plug-in 1.0.0.347 performs an illegal operation when attempting to connect to a computer running Version 4.0.680 of the Free Version of Logmein. (I am not sure if the Pro version causes it as well, but the older versions of Logmein do not cause the problem. I can log in to my computers running previous versions, but not the newest version) I can overcome this problem by using IETab to chrome Internet Explorer into a tab, but I cannot run it directly within firefox. After I try to log on to the specific computer, it will throw an error that says: The plug-in performed an illegal operation you are strongly advised to restart Minefield. Reproducible: Always Steps to Reproduce: 1.log in to logmein.com 2.attempt to log into a computer with newest version (4.0.680) 3.enter user/pass or access code Actual Results: Throws an error : The plug-in performed an illegal operation you are strongly advised to restart Minefield. After clicking Okay, Minefield crashes. Expected Results: Should log on to the computer as normal.
Known Issues Extensions Extensions installed under previous versions of Firefox may be incompatible with Minefield. History and Bookmarks This release is intended to test the backend infrastructure and importing. Most of the user interface changes are in flux and testing is not needed at this point. Note that the new bookmarks and history storage for this release are separate from the previous versions, so if data corruption happens, you can still go back to Firefox 2.0 and have the old data.
it is not an extension, it is a plug-in. And the extension compatibility issues can mostly be overcome by modifying the install.rdf file. I will check to see if it works with 2.0.0.7
i meant 2.0.0.9, and apparently it does work with that version. It is up to the devs to decide whether this needs to be addressed now, but it should stay as a bug.
Works fine for me. Not able to reproduce. Looks more like a Pebcak, or a logmein version issue.
Whoa, you are saying it is my fault? thats highly uncool. I assume you know pebcak means "problem exists between keyboard and chair (or chair and keyboard)". Of course it has something to do with logmein, but since it works on 2.0.0.9 and works on internet explorer 7, it is a minefield compatibility issue that needs to be solved. Try installing the latest version of logmein on someone elses computer in your account, and attempting to connect to that computer through Minefield with the latest plugin. It crashes every time.
Version: unspecified → Trunk
(In reply to comment #5) > ... since it works > on 2.0.0.9 and works on internet explorer 7, it is a minefield compatibility issue perhaps, or perhaps not. did you notify logmein vendor? you don't see a breakpad incident for it, right? http://kb.mozillazine.org/Breakpad
Keywords: crash
Attached file Stack of main thread —
This was very frustrating to try to reproduce. The logmein installer (I used the trial version of Logmein Pro) crashes due to a java bug so I had to install it with IE. The plugin I had to install with Fx2 (after setting extensions.checkCompatibility to false) and then copying LMIProxyHelper.exe, npRACtrl.dll, ractrlkeyhook.dll and unicows.dll to the Minefield plugins directory. Then after taking Remote Control of the computer I'd just set up I get the illegal plugin operation notification but Minefield doesn't crash. I attached WinDBG and tried it again. Console output: SSL_Verify_Callback: preverify 0 SSL_Verify result 1 SSL_Verify_Callback: preverify 0 SSL_Verify result 1 SSL_Verify_Callback: preverify 0 SSL_Verify result 1 (174.c20): C++ EH exception - code e06d7363 (first chance) Then I broke in and grabbed the stack attached here.
Assignee: nobody → marton
Summary: Logmein plug-in performs an illegal operation → Logmein plug-in performs an illegal operation [@ npRACtrl!nsQueryInterface::nsQueryInterface+0x518b9]
Well, I seem to be able to get it to control using the old plugin, and now they seem to have changed something on logmein, because now when I attempt to install the new plugin, I get "Malformed File - Minefield could not install this item because "intall-4ri..rdf" (provided by the item) is not well-formed or does not exist. Please contact the author about this problem." So clearly it seems like something is major wrong on their end. The problem is that I tried calling them to explain it, and they are utterly useless. I will attach a screen shot of the error window.
Thanks for including my account on the discussion. Logmein is aware of the plugin installation issue with FF 3.0 and we're working on a fix. It seems it's more work than we anticipated. Veritas, I appreciate you trying to let us know - but if you call our general number you will get in touch with Sales or Customer Service, and yes, I can see how discussing the details of a Firefox bug can be a frustrating experience with these departments. You need to talk to the LMI devs - and you're doing that right here. Thanks again, and if this bug remains open I'll make sure to circle back when we have a resolution on our end.
A major version change in Firefox usually means some changes on how it behaves and interacts towards plugins. This can cause some accidental compatibility issues, and is not unexpected. Sometimes backwards compatibility is intentionally broken, and what Mozilla expects in this case is that 3rd party plugin developers adapt and migrate to new methods, which replaces the old. In this particular case both happened. There were some small behaviour changes in Firefox which caused some smaller issues and triggered the crash in our plugin. We already fixed these in the LogMeIn plugin. Firefox3 Beta2 introduced an intentional change which breaks backwards compatibility when it comes to the installation of plugins. Beta2 deprecated the used to be standard way of installing plugins (XPI package with install.js)The error message you see when you try to install the plugin tries to tell you this fact, but Firefox never was very user friendly when it comes to communicating problems to the user, that's why the messages doesn't mean anything to most. We are not completely happy with this change as it has a couple of annoying side effects, but as there is no other way, we will change the method our plugin is installed. Veritas, if you wish, you can check out an updated version of the plugin, but it involves some manual installation steps, as the new install package for the LogMeIn plugin is not yet available. Go to our Labs section of the LogMeIn website and download the latest Beta build of LogMeIn (4.0.697 right now). Install this to a computer, then log in to it. Now change the relative part of the URL to /activex/npRACtrl.xpi, and instead of installing, download the XPI file. Extract the contents with WinZip or any similar, and copy the files into your plugin folder. You should have no problem connecting and using our plugin after the plugin is updated.
Status: UNCONFIRMED → NEW
Component: General → Extension Compatibility
Ever confirmed: true
QA Contact: general → extension.compatibility
I have this exact same error using Firefox 3.3 beta (portable edition). Workaround: Cancel the plugininstallation and skip it in the next step. Logmein will use Java instead of the ActiveX plugin.
I'm also having the same issue, but the illegal operation was caught every time right after I log out the remote computer by clicking the "End Remote Session" button.
confirmed, the workaround posted by tibor works. I only add at this point that the install pretends to work (no longer throws an error) with the latest nightly, but it does not succeed in actually installing. Build info:: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9pre) Gecko/2008042006 Minefield/3.0pre
wow, did I ever speak too soon??? Re-update. The manual workaround clearly installed the latest plugin (1.0.0.356), and worked fine throughout remote control, but it hard crashed after ending remote control. It locked me out (had to ctrl-alt-del), freezing on a blue screen with the standard toolbar across the top of the page, then when I crashed it out the rest of the way, DEP (date execution prevention) on vista 64 freaked out and killed the program. its major messed up now.
Component: Extension Compatibility → Plug-ins
Product: Firefox → Core
QA Contact: extension.compatibility → plugins
We've updated logmein.com with the latest version of the plugin that should resolve any and all FF3 compatibility issues. When you go through the "connect to computer" process you will be prompted to install or upgrade the plugin. Our QA dept has cleared the release, but please comment if you see anything out of the ordinary.
the plugin itself works, but it does not install when you go through it the normal way. I had to download the file, and extract the plugins into the plugins folder.
Thanks for the report. The mechanism to update from an older plugin to the latest was not yet enabled on our website, it is now. New users were already getting the latest version, and the update is happening for older versions of the plugin as well now, so you will not need the manual install step anymore.
So is this fixed, as bug 426780 is invalid now due to this I think...
It should be good, yes - to the best of our knowledge the plugin will install and operate perfectly both with the latest FF beta and the 2.x production release. I didn't want to take the liberty to mark this FIXED.
maybe it is something on my end -- but can anyone confirm using the latest nightly that it will actually install without having to manually add it? It is not installing for me.
alright, and something else is wrong now, too. the plugin located at https://secure.logmein.com/activex/interim/npRACtrl.xpi is back to the 356 build. A few days ago when I reformatted my computer i believe it was at 379, which worked. I do not understand what is going on. I am going to go try to access it from a different computer.
yes it was also not installing for me. nothing happens after the downloading part of the process.
fullmetal, thanks for checking on that. alright, so two things are going on here. When I installed a fresh copy of the latest nightly on another computer, it also would not automatically install, and i had to do a manual install, but i noticed that the address that it pointed to when i clicked install was different. on the fresh copy of the install, it points to https://secure.logmein.com/activex/npRACtrl.xpi which seems to be the correct updated version of the plugin. I will try to troubleshoot what is causing my computer to point to the interim one -- marton, is there an operating system check that might be differentiating between vista 64 and winXP? I will do what I can to pin down what is causing it to point differently for my machines.
followup -- I tried deleting out all of my private data, so it doesn't seem to be a history/cache related thing that is pointing me to https://secure.logmein.com/activex/interim/npRACtrl.xpi rather than the correct https://secure.logmein.com/activex/npRACtrl.xpi . I will wait on your, marton, until you let me know if you might have an idea why the installation might be pointing me to different places based on the computer. thanks again for your help on this bug.
There were a couple of situations where the website pushed out the legacy FF2 version of the plugin for FF3 browsers as well. This has been fixed, could you recheck? Thanks.
This problem still occurs. The steps listed in "how to reproduce" is incorrect. I just encountered this problem myself and found that this bug only happens when you install and attempt to use the plug in before restarting Firefox. Even though logmein.com says that you can use the plug in without restarting, if you use it without restarting you may encounter this bug.
(In reply to comment #29) > this bug only happens > when you install and attempt to use the plug in before restarting Firefox. Can you go to about: and copy the entire "Build Identifier" line? Should look like this: Build identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9pre) Gecko/2008060304 Minefield/3.0pre Thanks.
sorry about that: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9) Gecko/2008051206 Firefox/3.0
Component: Plug-ins → Other
Product: Core → Plugins
QA Contact: plugins → other
Version: Trunk → unspecified
Whiteboard: [logmein]
Does this still happen with the latest version of LogMeIn and Firefox 3.6?
haha, no. sorry, i haven't looked at this particular bug in years.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Since this just started working without action from MoCo, then it's not "fixed" but "worksforme" as far as our status logging goes.
Resolution: FIXED → WORKSFORME
Crash Signature: [@ npRACtrl!nsQueryInterface::nsQueryInterface+0x518b9]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: