Problem description: I have some problem to use LO: if I directly open a file, after the splashscreen the program crashes. If I open Libreoffice and then I'll open the file. It seems to work but if I do something it crashes. Here's report a libreoffice --backtrace file. http://pastebin.com/hS4b8xfy Thank you! Operating System: other Version: 4.2.2.1 release
On which env are you? (Windows, Linux, MacOs, other?) and which version? Did you install any LO specific extensions? Did you install any specific fonts? (i mean which are not out of the box on your env) For the test, could you rename your LO directory profile (see https://wiki.documentfoundation.org/Documentation/UserProfile) and give it a new try?
I'm on Arch Linux and I've not installed any extension. I've removed ~/.config/libreoffice folder and nothing has changed I use tons of fonts, but I've always used them and I'm corrently use them in other system with Ubuntu. Anyway, without fonts all goes ok. How can I know wich font causes instability?
Perhaps there's some quick and easy method but I don't know it. I can only advise you dichotomic method.
Does this persist with LO 4.2.3?
Libreoffice crases on first use of whatever program in Win 7.
Paul: please don't put change "Linux All" to "Windows all". Indeed, either you reproduce the exact same behaviour and it's the same cause (for the moment we don't know) and it's "All" or fill a new bugtracker. For the moment, I would advise you to fill a new bugtracker by using this page: https://www.libreoffice.org/get-help/bug/
Hallo, Julien, Dank u voor uw bezorgdheid ! Mijn probleem zit in de "ouderdom" van mijn Display Adapter, die ActiveX onvoldoende ondersteunt. Ik weet dus dat ik een nieuwe ZOU moeten kopen... Vriendelijke groetjes, paul.langie From: bugzilla-daemon Date: 2014-04-23 11:01 To: paul.langie Subject: [Bug 77320] Other: Libreoffice 4.2.2-5 crashes on startup Julien Nabet changed bug 77320 WhatRemovedAdded OSWindows (All) Linux (All) Comment # 6 on bug 77320 from Julien Nabet Paul: please don't put change "Linux All" to "Windows all". Indeed, either you reproduce the exact same behaviour and it's the same cause (for the moment we don't know) and it's "All" or fill a new bugtracker. For the moment, I would advise you to fill a new bugtracker by using this page: https://www.libreoffice.org/get-help/bug/ You are receiving this mail because: You are on the CC list for the bug.
Paul: Please, speak English in Bugzilla. If I can trust Google translate, I'd say you mix ActiveX and graphic card whereas they're 2 different unrelated things. You can try the raw method: - uninstall LO completely - rename (or remove if you don't need to keep a backup) your LO directory profile (see https://wiki.documentfoundation.org/UserProfile#Windows) - clean your Windows registry with a free tool (like ccleaner) - install last LO version 4.1.5 (stable branch) or 4.2.3 (fresh branch)
Hallo, Julien, Sorry I wasn't aware that I was writing in MY language. (Flamish people are careless about that because they must know several ones). Thank you very much for your careful reaction ! Windows 7 informed me that my problem is inherent to the "age" of my Display Adapter (from beginning of 2k-era). He doesn't support ActiveX far enough. I resolved allready the problem by diminishing the "acceleration" by 2 steps (out of 5 ?). For my old administrative PC this is far good enough. I just recovered this old PC from a severe virusattack and was looking around for another Office-pack. My old PC is my laboratory !! On my other recent PC, I am enjoying full multimedia without fear for viruses (scarce external connections). I no more need help, thank you for your careful reaction ! Friendly greetings, paul.langie paul.langie From: bugzilla-daemon Date: 2014-04-23 11:49 To: paul.langie Subject: [Bug 77320] Other: Libreoffice 4.2.2-5 crashes on startup Comment # 8 on bug 77320 from Julien Nabet Paul: Please, speak English in Bugzilla. If I can trust Google translate, I'd say you mix ActiveX and graphic card whereas they're 2 different unrelated things. You can try the raw method: - uninstall LO completely - rename (or remove if you don't need to keep a backup) your LO directory profile (see https://wiki.documentfoundation.org/UserProfile#Windows) - clean your Windows registry with a free tool (like ccleaner) - install last LO version 4.1.5 (stable branch) or 4.2.3 (fresh branch) You are receiving this mail because: You are on the CC list for the bug.
a.verdoja: any update?
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team Message generated on: 10/01/2015
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of FDO Message generated on: 2015-02-11