| Summary: | crash when a new folder is created in KDE file integration | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | Mark <m.wege> |
| Component: | LibreOffice | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | l.lunak, momonasmon, serval2412 |
| Priority: | medium | ||
| Version: | 4.1.0.4 release | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
| Attachments: | backtrace | ||
|
Description
Mark
2013-08-19 22:10:55 UTC
Hi, I can't reproduce the crash under Ubuntu 13.10 (64-bit) with LO 4.1.0.4 & KDE 4.11. I'm able to create a new folder (either from Dolphin or by right-clicking) and save a document to it. Please inform your distro & KDE version. I am using Kubuntu 13.04 (64) with Lo 4.1.04 and KDE 4.11 (In reply to comment #2) > I am using Kubuntu 13.04 (64) with Lo 4.1.04 and KDE 4.11 Still can't reproduce. Kubuntu 13.04 64-bit fully updated, KDE 4.11 (from kubuntu-backports PPA), LO 4.1.0.4 (from libreoffice-4-1 PPA). Mark: could you try to retrieve a backtrace (see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace)? It may help to pinpoint the problem. I gave this a try, but it appears thought that this does not work with the KDE filemenu active. When started with the backtrace option Libreoffice just crashes for me when wanting to open the file menu, by clicking on "Save". I have attached that backtrace, but I guess it wont help, but may be you can tell me how to create usable backtrace anyway. Created attachment 84498 [details]
backtrace
Thank you Mark for your feedback. Here's an interesting part of bt: Thread 1 (Thread 0x7ffff7f8da00 (LWP 24781)): #0 strcmp () at ../sysdeps/x86_64/multiarch/../strcmp.S:134 #1 0x00007ffff7de35c6 in check_match (sym=0x7ffff473d798) at dl-lookup.c:150 #2 0x00007ffff7de3ea0 in do_lookup_x (new_hash=new_hash@entry=317935421, old_hash=old_hash@entry=0x7fffffffa260, result=result@entry=0x7fffffffa270, scope=<optimised out>, i=<optimised out>, i@entry=0, flags=flags@entry=5, skip=skip@entry=0x0, undef_map=undef_map@entry=0x1cd3570) at dl-lookup.c:250 #3 0x00007ffff7de41c9 in _dl_lookup_symbol_x (undef_name=0x7fffb8ad5820 "_ZNK3svt19StatusbarController14getControlRectEv", undef_map=0x1cd3570, ref=ref@entry=0x7fffffffa338, symbol_scope=0x1cd38c8, version=0x0, type_class=type_class@entry=1, flags=5, skip_map=skip_map@entry=0x0) at dl-lookup.c:739 #4 0x00007ffff7de8c95 in _dl_fixup (l=<optimised out>, reloc_arg=<optimised out>) at ../elf/dl-runtime.c:113 #5 0x00007ffff7def725 in _dl_runtime_resolve () at ../sysdeps/x86_64/dl-trampoline.S:45 #6 0x00007fffb9470f31 in SwViewLayoutControl::Paint (this=0x238dc80, rUsrEvt=...) at /build/buildd/libreoffice-4.1.0/sw/source/ui/utlui/viewlayoutctrl.cxx:99 #7 0x00007ffff5c2fb1e in SfxStatusBarControl::paint (this=0x238dc80, xGraphics=..., rOutputRectangle=..., nStyle=0) at /build/buildd/libreoffice-4.1.0/sfx2/source/statbar/stbitem.cxx:400 #8 0x00007ffff56e0757 in framework::StatusBarManager::UserDraw (this=<optimised out>, rUDEvt=...) at /build/buildd/libreoffice-4.1.0/framework/source/uielement/statusbarmanager.cxx:667 #9 0x00007ffff6b8582b in StatusBar::ImplDrawItem (this=this@entry=0x2376290, bOffScreen=bOffScreen@entry=0 '\000', nPos=nPos@entry=9, bDrawText=bDrawText@entry=1 '\001', bDrawFrame=bDrawFrame@entry=1 '\001') at /build/buildd/libreoffice-4.1.0/vcl/source/window/status.cxx:442 #10 0x00007ffff6b8875a in StatusBar::Paint (this=0x2376290) at /build/buildd/libreoffice-4.1.0/vcl/source/window/status.cxx:750 #11 0x00007ffff6bbc42c in Window::ImplCallPaint (this=this@entry=0x2376290, pRegion=pRegion@entry=0x366cb00, nPaintFlags=26, nPaintFlags@entry=28) at /build/buildd/libreoffice-4.1.0/vcl/source/window/window.cxx:2470 #12 0x00007ffff6bbc1b6 in Window::ImplCallPaint (this=this@entry=0x1f2b780, pRegion=pRegion@entry=0x0, nPaintFlags=<optimised out>) at /build/buildd/libreoffice-4.1.0/vcl/source/window/window.cxx:2494 Lubos: one for you? (put it at NEW since bt provided) I cannot reproduce (possibly fixed by my recent fix for bug#69002), and the backtrace is useless. Can you please provide a Valgrind log (as in comment #4, just see the Valgrind section)? Is your fix already part of a release. I am running Version: 4.2.3.3 and still have crash. No, it may take a while. Let me know, when it is released, then I will test it. 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 |