Created attachment 42467 [details] Popup window showing the Fatal Error THE ERROR: Message modal popup shows the following: ------------------------------------------------------------------ The program cannot be started. A general error occured while accesing your central configuration. ------------------------------------------------------------------ HARDWARE: ------------------------------------------------------------------ Intel(R) Core(TM)2 Duo - E4700 @2.60GHz RAM physical: 4 GB ------------------------------------------------------------------ SOFTWARE: ------------------------------------------------------------------ Physical Addres Extension - was set Windows XP Professional (all current updates in place) - administrative account Added msvcp90.dll in c:\windows\system32\ folder LibreOffice it is installed for all users. All necessary firewall and antivirus configurations are done. Firewall - Comodo v3.14.147648.588 (all current updates in place) Antivirus - Avira Product version 10.0.0.609 (all current updates in place) Installed twice and has resulted the same error. Oracle OpenOffice works fine. ------------------------------------------------------------------
strange windows install bug -> Tor
(In reply to comment #1) > strange windows install bug -> Tor What can I say. I agree. And it is very frustrating because I was very excited about this app. For the moment I use Oppen Office. So if you have any idea where to look at, on my install and system please do not hesitate and email me. I will try to install LibreOffice to a windows 7 virtualbox image later at the end of this week to see what will happen then. Its a hacked barebone distribution Only about 2 GB it's the footprint on the HDD. In my opinion and from my experience as programmer these types of errors probably happens when the distribution is assuming that on the SO some libraries are preexistent or sometimes them could be missing or there can exist older versions or maybe corrupted ones and the software try to use them. So that I can verify if you give me a list of these libraries to check if are prezent and have the same name and size or maybe it could be useful to aply a MD5 hashing on each of them to compare with those you have and that are functioning whith the LibreOffice. Also if LibreOffice try to install his libraries over some ones that are locked because they are in use by some other app or service, mislead install can happen. Without a validating install: ownfiles and disponible memory RAM and virtual at the moment of the install and at the each ordinary run, these errors can appear.
As other people install and run LibreOffice on XP just fine, it most likely is caused by something specific to your installation. After all, your say yourself it is a "hacked barebone distribution". Impossible to reproduce without having access to that "hacked" installation, and why should we bother? Resolving as NOTOURBUG.
(In reply to comment #3) > As other people install and run LibreOffice on XP just fine, it most likely is > caused by something specific to your installation. After all, your say yourself > it is a "hacked barebone distribution". Impossible to reproduce without having > access to that "hacked" installation, and why should we bother? Resolving as > NOTOURBUG. I am sorry Tor, but you did not read carefully the comments from the beginning. In the first post(the description of the bug) I have described in detail the configuration of my sytem: hard and soft where I have encontered the error. That "hacked barebone distribution" refers to a future intention of mine to test Libre office on a virtualbox win7 - for wich, sadly, I did not had the available time to do it yet. So I am sorry but the bug can not be set yet to NOTOURBUG whitout a proper investigation. Please reread my posts. I reopened the issue. Thank you and best regards, Florin J.
(In reply to comment #4) > (In reply to comment #3) > > As other people install and run LibreOffice on XP just fine, it most likely is > > caused by something specific to your installation. After all, your say yourself > > it is a "hacked barebone distribution". Impossible to reproduce without having > > access to that "hacked" installation, and why should we bother? Resolving as > > NOTOURBUG. > > I am sorry Tor, but you did not read carefully the comments from the beginning. > In the first post(the description of the bug) I have described in detail the > configuration of my sytem: hard and soft where I have encontered the error. > That "hacked barebone distribution" refers to a future intention of mine to > test Libre office on a virtualbox win7 - for wich, sadly, I did not had the > available time to do it yet. > So I am sorry but the bug can not be set yet to NOTOURBUG whitout a proper > investigation. > > Please reread my posts. > > I reopened the issue. > > Thank you and best regards, > Florin J. Well I forgot to emphasize, that I have a legal aquired XP licence on this PC, where I've encountered the error. So, no barebone and no hacked install is on my PC. It's all legal an paid.
Getting the same error using LibO_3.3.0_Linux_x86 on Mandriva 2010.2; have removed .libreoffice and similar files from OpenOffice.org (a suggested fix on some other list), but that did not work.
J David, please file a separate bug report. *This* bug report is about something that happens (for the bug reporter) on Windows *only*.
Florin, do you still see the problem with 3.3.2? What about 3.4 beta2?
Nobody else is able to reproduce this => it can't be blocker. Florin, please try the last (beta4) build and report if you still see the problem.
This is definitely NOT just a Windows problem. I am seeing the same behavior on BOTH OpenOffice3.3 on Fedora 14 x86_64, as well as on LibreOffice3.4 (stable), which was just freshly installed. 1. Removing, respectively, ~/.openoffice.org or ~/.libreoffice does no good. New directories of the same names get created, and the same error message pops up. 2. This bug happens on an account by account basis. That is, it happens to each user on the system, independently, after one or more uses of OO or LO. An important point here is that once either program is broken, both are broken. If I create a new user account, the first time I try to use OO or LO, the program works. After that, both no longer work at all. 3. This is an old and widespread bug. If you google the error message, you see numerous people complaining about this problem for at least a year, with both OpenOffice and LibreOffice. 4. I have not installed any extensions. 5. I see the bug running on GNOME, KDE, and LXDE desktops, same machine, same accounts. 6. I have checked /var/log/secure, /var/log/messages, with no messages recorded at the time OO or LO was launched. So the status is, on my system, I can run neither OO nor LO work at all. Zilch! Perhaps a good approach would be for someone with access to the source code to grep the error message and see which part of the code generates this message.
Brian, thanks a lot for now making this bug report completely useless. Why did you changhe the platform from Windows (only) to Linux (only)? The initial bug report was for Windows, so *if* you are sure that it is the same bug (not just the same symptom), what you could have done would have been to change the platform to All. Anyway, tempted to resolve this as invalid, but I am sure somebody will just reopen it anyway.
(In reply to comment #11) > Brian, thanks a lot for now making this bug report completely useless. Why did > you changhe the platform from Windows (only) to Linux (only)? The initial bug > report was for Windows, so *if* you are sure that it is the same bug (not just > the same symptom), what you could have done would have been to change the > platform to All. Jeez, what a snarky answer. Nonetheless, you are correct that the platform should be ALL, and it was my stupid mistake to put in "linux" for the platform. I have changed it to ALL. Unless there is some specific reason for thinking otherwise, if the symptoms are the same, the least hypothesis is that it is a platform independent bug, until proven otherwise. Without a clue as to the underlying problem, it would be counter productive and probably misleading to spawn two independent bug reports. >Anyway, tempted to resolve this as invalid, but I am sure > somebody will just reopen it anyway. What kind of attitude is that? Go Google the error message, both for OpenOffice and for LibreOffice. See for yourself how many people have reported this bug on both Windows and Linux. This is real, it is a big show stopper for people who encounter it. Even if you create a new userid, very quickly, both OO and LO become unusable. Even if you stipulate that several independent problems generate the same behavior and error message on different systems, it is still a bug, in the sense that the error message is too vague. What central configuration is it talking about? Why not give the actual filename that it can't read?
> Why not give the actual filename that it can't read? Indeed. Do you think it is we who wrote this code, and came up with the often so utterly useless error messages?
Created attachment 48614 [details] The same popup
(In reply to comment #8) > Florin, do you still see the problem with 3.3.2? What about 3.4 beta2? Hi Tor, Sorry for the delayed response but sometimes one mail can escape from my attention but many are much harder. Since you asked if I have installed v3.4.beta2 a stable version released. So I have installed v3.4 stable. The result is the same. Same popup shows up with the same message.
(In reply to comment #15) > (In reply to comment #8) > > Florin, do you still see the problem with 3.3.2? What about 3.4 beta2? > > Hi Tor, > > Sorry for the delayed response but sometimes one mail can escape from my > attention but many are much harder. > > Since you asked if I have installed v3.4.beta2 a stable version released. > So I have installed v3.4 stable. > > The result is the same. Same popup shows up with the same message. Also a strange thing happen on uninstall. I am not sure if this thing have anything to do with this bug but for the moment I will describe it here. The uninstall, somewhere in the process, asked me to close firefoox for some reason. I have not remember what was the message because I didn't pay attention then, because sometimes I expect to happen that for the common files beeing in use. Removing or modifying that sort of files is forbidden because they are in use by another application. Later after I have remembered the circumstances I have concluded that there happened an odd thing. The same confirmation message should be poped up on install! Why that didn't happened? No confirmation was asked from me and firefox was all the time open (no closing, no opening). When I have some time, but only if you consider that it have some significance, I will do the same test under the same conditions: Firefox opened, install LibreOffice, try to open LibreOffice, close LibreOffice. Best Regards, F.J.
I'm having this exact issue on a Win7 64 system very recently fresh installed. 3.3 Beta was installed and working then just stopped with this error - I have been rebuilding the system so I can't trace it to what I installed that may have led to the issue but it's not working now anyway. I've tried _a lot_ of things including re-installing, removing all files re-installing, replacing Java, etc etc nothing seems to work. I will gladly provide any information I can to help trace this - as I really need to access all my LibreOffice documents and currently can't find any way to do it.
Update: I got it working again - here's how: After a LOT of reading online someone mentioned Windows Firewall as being a possible issue causing this (mine is usually disabled) I completed the following actions: Re-activated Windows Firewall Uninstalled LibreOffice 3.4 Deleted ALL files from the Roaming/LibreOffice folder Deleted ALL files from Program Files (x86)/Libre Office 3.4 Cleared ALL temp files Rebooted Fresh Installed Libre Office 3.4 with nothing else running - application starts Disabled Windows Firewall again - application starts Looks like there is something going on there - could be the Firefox Issue or the Firewall - hope that helps.
NEW, unassigned bug: replace "infoprovider" with move to state "NEEDINFO".
needinfo keyword redundant by needinfo status.
Dear bug submitter! Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs. To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem. Yours! Florian