Problem description: Starting with Libreoffice 3.4 and in 3.5, when clicking the Borders tab in Format Cells the program crashes. Steps to reproduce: 1. Right click in a cell in Calc. 2. Select Format Cells 3. Click the Borders tab. Current behavior: Calc crashes Expected behavior: open the Border tab for accessing cell border settings. Platform (if different from the browser): Browser: Mozilla/5.0 (X11; Linux i686; rv:10.0.1) Gecko/20100101 Firefox/10.0.1
On pc Debian x86-64 with 3.5 branch updated today, I don't reproduce this bug. Several questions : - have you got this problem with brand new documents or just with specific ones ? - have you got error messages in console ? - did you install 3.5.0 on a clean env (remove or move profile if you need to backup it, uninstall previous version, install 3.5.0) ?
(In reply to comment #1) > On pc Debian x86-64 with 3.5 branch updated today, I don't reproduce this bug. > > Several questions : > - have you got this problem with brand new documents or just with specific ones ? > - have you got error messages in console ? > - did you install 3.5.0 on a clean env (remove or move profile if you need to backup it, uninstall previous version, install 3.5.0) ? The answers to your questions: - any document, either existing or new - yes: The error was 'BadMatch (invalid parameter attributes)'. (Details: serial 13631 error_code 8 request_code 59 minor_code 0) - I removed the profile and the problem persists. I should probably mentioned that Libreoffice is compiled from source in Gentoo. It happens for at least a few months, starting with version 3.4, it did not happen in 3.3.
for devs/QA guys : a link with https://bugs.freedesktop.org/show_bug.cgi?id=47015 ?
Not reproducible on 3.5.1 RC2. Platform: Linux x86
have never seen such a crash, and i tend to open "border" dialogs a lot :) > The error was 'BadMatch (invalid parameter attributes)'. > (Details: serial 13631 error_code 8 request_code 59 minor_code 0) perhaps something related to missing XSync or some such voodoo?
please do a stacktrace breaking on gdk_x_error with: export SAL_SYNCHRONIZE=1 export GDK_SYNCHRONIZE=1 failing that, please try if the error persists with: export SAL_USE_VCLPLUGIN=gen please also state the WM you are using. likely related to: https://bugs.freedesktop.org/show_bug.cgi?id=50173 https://bugs.freedesktop.org/show_bug.cgi?id=46687
What window manager are you using out of interest ? is it Unity ? ;-)
@mmeeks: The chances of unity being used on gentoo are rather slim. No need for badmouthing here.
Something weird going on with the recent rash of "BadMatches", none of which I've seen. Something changed somewhere to trigger these. Throwing XSyncs about the place just seems wrong.
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
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