|
Bugzilla – Full Text Bug Listing |
|
Description
Rainer Hurtado Navarro
2009-11-25 06:20:48 UTC
Sorry, but it's not reproducible at all. I can paste copied stuff as many times as I want. 1) What application did you use? Writer, Calc, Impress or Draw? 2) Are you in KDE or Gnome? Please note that the priority field is for the developers to adjust, not for users. Adjusting it back to the default value. Created attachment 329886 [details]
Exported YaST XML packages installed on my system list.
So, perhaps you notice some packages incompatibility for the case OOo worked right.
Hello, first, I apologize for changing the priority field, but I didn't know that. Well, I am currently working with OOo WRITER under KDE and I am having the issue right now: I have cut 26 lines of text to paste it in another document and, at the time I make Crtl+V or click the clipboard icon at the bar, OOo Writer paste nothing. So, I had to undone. I tried again, but copying, and opened a Calc Spreadsheet, and selected cells randomly and pasted rightly the copied lines. So, I turned to the target document in which I intended to copy the lines a followsnd I got a paste. But I tried again at my source document, cutting without being success at pasting, even in Calc. I repeated the operation but copying, and in Calc or in Writer I got no paste at all. I work mostly with Writer (95%); secondly, with Calc (5%). The documents I work with today are tiny (3 pages), because I am so troubled with this issue that I am not working with the original document (168 pages), but I am writing in small ones to prevent losing something. Since December 2006 till November 15th, 2009 I booted openSuSE 10.2, but, lately (May, 2009), I was working with OOo 3.1.0 from its web (under openSuSE 10.2's KDE). I had not any trouble with 3.1.0. I just use the following repositories with its priority set as follows: DVD (0), CD Add-on Non OSS (1), CD Add-on Lang (2), net OSS (3), net Non-OSS (4), net Update (5), NVIDIA (6), Packman (7), VideoLan (8), and I don't swith architecture (x86_64 to x86), nor dismissed the official packages in favor of other repositories. I attach my user-packages.xml I don't know whether the following would be as relevant as needed, but I have noticed that the undone memory (the list of actions done displayed from the bar) states instead of "cut", "deleted" ("Eliminado 'whatsoever'"), and, when OOo Writer doesn't paste, the paste icon doesn't work at all (not even displays the options OOo Writer, HTML, RTF and unformatted text).
And, when I chose many cells in OOo Calc, and paste in them something I have copied from OOo Writer, just the first receives the action, although all of them remain selected. Ans the paste icon shows the following options in order: Text document of OOo 3.1, DDD Link, unformatted text, RTF, HTML instead of the usual (GDI metafile, [...], HTML). But, if I copy inside OOo Calc, all the selected cells are pasted. (Currently, at least for now, OOo Calc is pasting with the mentioned behavior. OOo Writer maintains its erratic behavior.)
Rainer: Can you please check if you are able to reproduce the behavior in Gnome, or when you uninstall OpenOffice_org-kde4? Hello, I am sorry for the delay, but I never got no mail from you requesting information, so, as I am very troubled with this, I have reviewed this page for a solution might have come without noticing it, and I have found your request. I have already uninstalled OpenOffice_org-kde4: the behavior does not change, but the open and save dialogs. Concerning Gnome... I'll tell you later. (P. S.: Why your comments are not mailed to me any longer? Mail me that you are requesting information, please, so I could provide it as soon as possible.) Thanks. Hello, I am sorry for the delay. After uninstalling OpenOffice_org-kde4 I installed Gnome as you ask me. Frankly, the behavior of OOo in general improved. And the issue https://bugzilla.novell.com/show_bug.cgi?id=558253 that I reported is not present under Gnome (so, Jan Holesovsky seems to be right). However, it is not solved. In fact, setting up Gnome caused some problems with the multimedia applications, for instance: when I run them, they reset the audio volume to zero. And Gedit has problems with the search engine. But lets return to OOo Writer and Calc because it is the matter for settle here and that I can not handle by my own. The behavior of OOo concerning the copy-cut-paste procedures I previously told, in general, improved. But I have notice that follows: I avoid the use of the copy-cut-paste icons, or its keyboard shortcuts, when the text fragments or cells are near enough to be highlighted with the pointer device (mouse) and moved toward the new location. And, often, OOo crash due to the procedure, and the recovery dialog does not recovers efficiently the document (OOo creates a journal locked document bound to the working document, and I think it is not working efficiently if OOo can not recover successfully the document: I mean for successfully that OOo Writer or Calc revovered the document in a status as near as the time of the crash, not an ideal 100%). In OOo Calc I realized two ways in which they occurs: if one selects multiple cells (A, B, C, D) in a single arrow and moves them so the first one be in B, the second in C, and so on, thus being shifted A, B, C, D to B, C, D, E, or to C, D, E, F, OOo Calc crashes. The same when one selects multiple cells in several arrows and moves them with the mouse although the next position does not overlap the previous ones. I always set in OOo > Tools > Options > Load & Save > Preferences > General > Save information for recovery and left the default time (15 minutes), and also set make always a backup copy option. But I currently set the saving of the recovery information to 7 minutes. However, don't ask me why, today I tested the maneuvers I described supra without crashing the OOo, but the past days that issue drove mad. I wonder if the issue could be related to the working document, because those in where I tried those maneuvers today are different (in fact, are accidental documents) to those in where I am currently working. I do not use macros in them. Thank you all. Created attachment 332734 [details]
Dependency problem when I installed Gnome
Dependency problem when I installed Gnome: I uninstall the kde4 patterns.
Created attachment 332735 [details]
OOo Writer uses to hang when opening under gnome
Created attachment 332736 [details]
OOo Writer uses to hang when opening under gnome
Created attachment 332738 [details]
OOo Writer uses to hang when opening under gnome, another time
OOo Writer uses to hang when opening under gnome, another time. (I repeated the previous image twice mistakenly.)
Created attachment 332739 [details]
OOo Writer uses to hang when opening under gnome, another time.
OOo Writer uses to hang when opening under gnome, another time, the same day. I know that my images are helpless. Sorrily, I cann't snapshot OOo when it crashes. It happens too too too fast, and unwarningly.
Created attachment 332742 [details]
my new user-packages.xml, so the changes in the behavior could be match with the changes in the system.
my new user-packages.xml, so the changes in the behavior could be match with the changes in the system.
please don't think I am trying to discourage you but... o images ( many images ) of a splash screen are not really very useful. o you seem to be reporting multiple problems here, this really is very confusing, please use 1 issue per problem. It seems the original problem here ( to do with copy/paste ) is now not longer reproducible ( under gnome ), is that correct? secondly you mention Writer is hanging but then say it crashes, which do you mean ? ( or do both happen? ) can you isolate a set of steps to reproduce the hang/crash ( or both if both in fact happen ) The images you attached seem to suggest that the application hangs on startup ( if so what way do you start the office process?, does this happen everytime? ) if you can easily get the soffice process to hang or crash you might consider repeating those steps while using gdb to obtain a backtrace, please see http://en.opensuse.org/Bugs:OOo for details on how to obtain a backtrace I am very sorry for the obscurity, because my ignorance, the language and the intention of be very detailed. I'll answer one by one your concerns. >> images ( many images ) of a splash screen are not really very useful. Yes, they are unuseful, but I intended to show you that my OOo is problematic. >> It seems the original problem here ( to do with copy/paste ) is now not longer reproducible ( under gnome ), is that correct? No, it is not correct: it persist, very occasionally, and I noticed that involves highlighting with the mouse and moving the selected text or cells from one place to another. I didn't notice it before because I seldom use this way (I prefer to cut and paste), but as the cutting and pasting wasn't working, I begin using this way. >> secondly you mention Writer is hanging but then say it crashes, which do you mean ? ( or do both happen? ) can you isolate a set of steps to reproduce the hang/crash ( or both if both in fact happen ) Copying-Cutting-Pasting didn't pasted, but the OOo didn't crashed. It was always. Moving selected areas using the mouse did crash OOo without warn (that's why I have no pictures of that) and without efficient recovery of the data. This failure moving data with the mouse was particularly of OOo Calc. When I wrote my request it happened always. The steps follows: "In OOo Calc I realized two ways in which they occurs: if one selects multiple cells (A, B, C, D) in a single arrow and moves them so the first one be in B, the second in C, and so on, thus being shifted A, B, C, D to B, C, D, E, or to C, D, E, F, OOo Calc crashes. The same when one selects multiple cells in several arrows and moves them with the mouse although the next position does not overlap the previous ones." Both things are common, but "However, don't ask me why, today [2009-12-15 17:25:56 UTC] I tested the maneuvers I described supra without crashing the OOo, but the past days that issue drove mad. I wonder if the issue could be related to the working document, because those in where I tried those maneuvers today are different (in fact, are accidental documents) to those in where I am currently working. I do not use macros in them.", or maybe the changes in the behavior could be match with the changes in the packages installed on my system. So, I attached a new user-packages.xml. I mean: today are random or erratic. >> The images you attached seem to suggest that the application hangs on startup ( if so what way do you start the office process?, does this happen everytime? ) Yes, I just have captures of the hanging on startup. It occurs seldom. I start the office process from the SuSE Application Launcher Menu (Favorites). Under KDE I have not that issue, but under Gnome (I have had some troubles with Gnome, or in KDE after installing Gnome with certain applications just in the PC in which I installed Gnome). It is, you are right, not related with the copy-cut(highlighting and moving)-paste issue. I send them just to show you that I am in troubles with the OOo that I can not handle instead or in absence of snapshots from the very moments in which my OOo crash while I work with it and lose my data. In fact, except for the illustrativeness of them, It is not a problem for me to bother you with: I can deal pretty well with this: I kill the process and launch it again. As you have noticed, it is just at start up: there is no data to loss. So, dismiss this point if you have to. >> if you can easily get the soffice process to hang or crash you might consider repeating those steps while using gdb to obtain a backtrace, please see http://en.opensuse.org/Bugs:OOo for details on how to obtain a backtrace If I saw it happens as before, I'll learn about how to obtain a backtrace and I'll follow your suggestion. >> please don't think I am trying to discourage you but... Today I am not working with OOo as intensively as I was when I submitted the bug because (instead of writing, since November 15th) I am dealing with many issues and problems installing openSuSE 11.2 in three PCs I never had before (not with SuSE, not in those PCs, related with wireless networking, Xorg and tablet, fingerprint, audio, Thunderbird - Firefox, devices automounting under KDE, etc.: I reported some; other not; others I simply follow). Some of those problems I can handle myself: I have been using Linux (and SuSE) for a decade now: So, something like that https://bugzilla.novell.com/show_bug.cgi?id=551753 doesn't matter too much for me: I know how to use mount. If I commanded Gnome to Shutdown the system but it lead me to the login screen, I'll command to shutdown from there without headache (however, once the system didn't shutdown but just halted: I had to push the power button). The same if (it is a KDE issue) I umount from the device manager or from the sysinfo:/ KIO slave a SD or a MS or a USB HD and the light remains lighted because the KDE device manager umount but doesn't eject the device: I know I can unplug the device safely because I know it is umounted or I simply order it to eject. Etc. But the other users (I mean that of this three PCs, but I think it is valid for many more users) doesn't know about mount, eject, and so on. Do you think, really think, that I am going to discourage myself? No! Those things happens! And I know you are doing a great job. I am the one who is sorry because I could not provide a better information (yet) so those issues end here for ever ever. I am very thankful to you indeed. For the way you questioned me, it seems that nobody has the same trouble as I have, but I do have it: it is not a hallucination of mine. As I am not able to cut-copy-paste rightly thought the icons or using the keyboard shortcuts, I have to use the mouse to highlight a text (or cells in Calc) and move it to any other part. It is, also a way to cut-paste, although there would be other kind of mechanism involved in this operation. I have already described how Calc crashes, because then I had to switch to Calc from Writer. But it is the same in Writer. Today I am working with a table in Writer, many rows, one column. And I needed to move some part of the content of the last filled row to the last one, but that last one is in the next page. So, when I move the mouse to the inferior edge (drag) to drop in the row I want, which is the first element in the next page, the OOo Writer crashes. It has been invariable and persistent the issue. I have taken with KSnapshot the following pictures: as the mouse cursor isn't pictured, in the first one it lies in the last row of the page, before I pass to the next page, next row. I have remember that there is recordMyDestop utility, so, instead send you pictures, I'll send you a movie. Better, don't you think? Meanwhile, I'll learn how to backtrace OOo... (N. B.: in my previous comment I miss spelled row (columna) as arrow (flecha). Sorry.) Created attachment 333588 [details]
OOoW.ogv: Ogg data, Skeleton v3.0; i. e. a movie of how OOoW crashes as I described in my last comment.
Created attachment 333592 [details] strace to soffice.bin. Installed the corresponded debug packages to that of OpenOffice.org installed: OpenOffice_org-base-debuginfo-3.1.1.4-0.1.4.x86_64.rpm OpenOffice_org-libs-core-debuginfo-3.1.1.4-1.1.4.x86_64.rpm OpenOffice_org-calc-debuginfo-3.1.1.4-1.1.4.x86_64.rpm OpenOffice_org-libs-extern-debuginfo-3.1.1.4-1.1.4.x86_64.rpm OpenOffice_org-components-debuginfo-3.1.1.4-1.1.4.x86_64.rpm OpenOffice_org-libs-gui-debuginfo-3.1.1.4-1.1.4.x86_64.rpm OpenOffice_org-filters-debuginfo-3.1.1.4-1.1.4.x86_64.rpm OpenOffice_org-math-debuginfo-3.1.1.4-1.1.4.x86_64.rpm OpenOffice_org-filters-optional-debuginfo-3.1.1.4-1.1.4.x86_64.rpm OpenOffice_org-pyuno-debuginfo-3.1.1.4-1.1.4.x86_64.rpm OpenOffice_org-gnome-debuginfo-3.1.1.4-1.1.4.x86_64.rpm OpenOffice_org-ure-debuginfo-3.1.1.4-1.1.4.x86_64.rpm OpenOffice_org-impress-debuginfo-3.1.1.4-1.1.4.x86_64.rpm OpenOffice_org-writer-debuginfo-3.1.1.4-1.1.4.x86_64.rpm OpenOffice_org-kde4-debuginfo-3.1.1.4-1.1.4.x86_64.rpm and followed the indications from http://en.opensuse.org/Bugs:OOo. Tell me whether it is needed something more, please. Created attachment 333594 [details]
gdb.log to soffice.bin
Official openSUSE-10.2-x86_64, kernel 2.6.31.5-0.1-desktop and OpenOffice.org 3.1.1: OOO310m21 (Build: 9319) /Build: 3.1.1.4 unupdated. Issues under Official KDE & GNOME.
Rainer, First, I am sorry but the back trace is not really useful. You would need to install the OpenOffice_org-*-debuginfo packages. Then the back trace would include the information about what source line it crashed. Also, please print the full backtrace to the gdb.log after you get the crash (Segmentation fault). You might do it by the following gdb command: thread apply all backtrace Hmm, I am a bit scared by the line: 0x00007fffca393405 in ?? () The '??' means that gdb does not know in what library/module it happened. It might mean that the memory is too broken to read this information. It might mean that the backtrace will not be useful even with the debuginfo packages installed :-( Okay, we will see. In the worst case, we could try to run it with valgrind. Second, I see the following error message in the backtrace: QPixmap: It is not safe to use pixmaps outside the GUI thread It is being solved as the bug #548354. We currently do not have a fix. The only workaround is to remove (rename) the file /usr/lib64/ooo3/basis3.1/program/libvclplug_kde4lx.so I am afraid that it will not solve your problems because it was printed after the crash, ... Third, you wrote in the comment #16 that you were not able to reproduce the crash with some other documents on 2009-12-15 at 17:25:56 UTC. It is quite likely that the problem is related to a particular document. Or it might be related to a particular data structure that you typically use in your documents. Do you know some easy steps how to 100% reproduce a problem with one your document? It would help a lot if you attach the document and describe the steps. Fourth, if you lost too many data during the recovery, you might try to lower to interval in "Tools/Options.../Load-Save/General/Save Autorecovery information every X minutes". Well, it is not too practical with too big documents because the application looks freezed when saving. Fifth, the hanging in the comment #13 need not be a total freeze. It might happen if OOo does a time consuming operation and does not respond quickly. Also it might happen if you do not have enough memory, the system uses swap and every operation takes much longer time. Summary: a) Please, try to remove libvclplug_kde4lx.so b) Please, try to produce backtrace with debuginfo packages installed c) Please, try to attach a problematic documents and steps to reproduce d) if nothing helps, we could try valgrind (In reply to comment #21) a) General comment: This issue has more complexity than it seems to have at first sight. It takes place in OOo: inside a single document, between different instances of the application (Writer, Calc, mixed), and, at last, lesser, between OOo and other applications. When using the toolbar icons or keyboard shortcuts, it often does not paste what was previously copied or cut, but after many attempts (the clipboard seems to be in blank), but there is no a specific number of them, so the issue shows a random component. When moving a highlighted area from a place to another using a pointing device (mouse), that is a sort of cut-paste operation (drag and drop), the application (OOoWriter or OOoCalc) crashes following this two scenarios: 1. Calc document: produces crashing, random occurrence, but when it happens it involves the overlapping of cells in a row or in a column when the intention is displace (or switch) the content in the row or column. 2. Writer document: produces crashing, always, it happens when just dragging a highlighted text selection to the next document page, specially inside a table that continues in the following page (tested in a long table). See video. The issue is not related to a specific document structure, as far as I have noticed. This missfunctioning is new: I use OOo since SuSE 8.1 Professional, either packaged by SuSE or either packaged by openoffice.org. For example, this issue was not present in OOo 3.1.0 from openoffice.org (as openSuSE 10.2 was unsupported by then, I upgraded my OOo directly from openoffice.org, as I use to do, meanwhile I waited the 11.2). And, by the way, I can tell you a bug present since the early stages of the development of OOo, minor, that does not involves data lost, that has not never fixed. It affects the page layout, but I can live with it: when it happens I just correct the page layout and go on. But this issue is of another kind: I am reorganizing the text of an unfinished investigation that I was preparing for 11 years, in which writing I have spend a whole 12th. year and that isn't finished yet. So, guess how awful feelings I have when I cann't work without the thread of losing something. I am writing in Kwrite, and pasting in OOoWriter later! If the content weren't paste (unusual) at least Kwrite doesn't crash, nor OOoWriter. (Other documents are trivial, so I take the risk and work directly on them.) I persist in using the openSuSE boxed OOo (I have thought to download openoffice.org's) to see this bug corrected, so it is time for the b) Replies: > Rainer, First, I am sorry but the back trace is not really useful. You would > need to install the OpenOffice_org-*-debuginfo packages. Then the back trace > would include the information about what source line it crashed. Installed the corresponded debug packages to that of OpenOffice.org installed (https://bugzilla.novell.com/show_bug.cgi?id=558250#c19): OpenOffice_org-base-debuginfo-3.1.1.4-0.1.4.x86_64.rpm OpenOffice_org-libs-core-debuginfo-3.1.1.4-1.1.4.x86_64.rpm OpenOffice_org-calc-debuginfo-3.1.1.4-1.1.4.x86_64.rpm OpenOffice_org-libs-extern-debuginfo-3.1.1.4-1.1.4.x86_64.rpm OpenOffice_org-components-debuginfo-3.1.1.4-1.1.4.x86_64.rpm OpenOffice_org-libs-gui-debuginfo-3.1.1.4-1.1.4.x86_64.rpm OpenOffice_org-filters-debuginfo-3.1.1.4-1.1.4.x86_64.rpm OpenOffice_org-math-debuginfo-3.1.1.4-1.1.4.x86_64.rpm OpenOffice_org-filters-optional-debuginfo-3.1.1.4-1.1.4.x86_64.rpm OpenOffice_org-pyuno-debuginfo-3.1.1.4-1.1.4.x86_64.rpm OpenOffice_org-gnome-debuginfo-3.1.1.4-1.1.4.x86_64.rpm OpenOffice_org-ure-debuginfo-3.1.1.4-1.1.4.x86_64.rpm OpenOffice_org-impress-debuginfo-3.1.1.4-1.1.4.x86_64.rpm OpenOffice_org-writer-debuginfo-3.1.1.4-1.1.4.x86_64.rpm OpenOffice_org-kde4-debuginfo-3.1.1.4-1.1.4.x86_64.rpm What else are needed, because currently I do not know? Also, this backtrace is just for the bug manifestation recorded on video. > > Also, please print the full backtrace to the gdb.log after you get the crash > (Segmentation fault). You might do it by the following gdb command: > > thread apply all backtrace > > Hmm, I am a bit scared by the line: > > 0x00007fffca393405 in ?? () > > The '??' means that gdb does not know in what library/module it happened. It > might mean that the memory is too broken to read this information. It might > mean that the backtrace will not be useful even with the debuginfo packages > installed :-( > > Okay, we will see. In the worst case, we could try to run it with valgrind. > So, if needed, explain me how to use valgrind. I am ready to try. > > Second, I see the following error message in the backtrace: > > QPixmap: It is not safe to use pixmaps outside the GUI thread > > It is being solved as the bug #548354. We currently do not have a fix. The only > workaround is to remove (rename) the file > > /usr/lib64/ooo3/basis3.1/program/libvclplug_kde4lx.so > > I am afraid that it will not solve your problems because it was printed after > the crash, ... > Thank you: I'll see this later. > > Third, you wrote in the comment #16 that you were not able to reproduce the > crash with some other documents on 2009-12-15 at 17:25:56 UTC. It is quite > likely that the problem is related to a particular document. Or it might be > related to a particular data structure that you typically use in your > documents. I thought the same once, so, as I could not send you the text document for which I am worried about, I described it to you (https://bugzilla.novell.com/show_bug.cgi?id=558250#c4) without details. However, you are right when stating that it would probably have a peculiar data structure. But, it happens with more simple documents, as that one I used to record the video of the crashing. And, later, I noticed the problem in Calc (described in https://bugzilla.novell.com/show_bug.cgi?id=558250#c8 https://bugzilla.novell.com/show_bug.cgi?id=558250#c16 https://bugzilla.novell.com/show_bug.cgi?id=558250#c17) working with a very simple spreadsheat. > > Do you know some easy steps how to 100% reproduce a problem with one your > document? It would help a lot if you attach the document and describe the > steps. > I can submit you the Calc spreadheat and one of the Text documents (the recorded one): You would be surprised at the sight of how simple they are. > > Fourth, if you lost too many data during the recovery, you might try to lower > to interval in "Tools/Options.../Load-Save/General/Save Autorecovery > information every X minutes". Well, it is not too practical with too big > documents because the application looks freezed when saving. > I set it to 7 minutes (https://bugzilla.novell.com/show_bug.cgi?id=558250#c8), and yes: the OOo looks freezed when saving, but I am used to. > > Fifth, the hanging in the comment #13 need not be a total freeze. It might > happen if OOo does a time consuming operation and does not respond quickly. > Also it might happen if you do not have enough memory, the system uses swap and > every operation takes much longer time. > Physical RAM: 2.0 Gb Swap: 2.1 Gb Video RAM (NVidia Card) 512 Mb. > > Summary: > > a) Please, try to remove libvclplug_kde4lx.so I'll take care of this later. > b) Please, try to produce backtrace with debuginfo packages installed Suggest me what others debuginfo packages. > c) Please, try to attach a problematic documents and steps to reproduce I can attach you two of them (one for Writer, one for Calc). > d) if nothing helps, we could try valgrind Teach me if so. I know you are working hard, so thank you. Created attachment 336870 [details] gdb.log to soffice.bin, following suggestion of Petr Mladek (http://bugzilla.novell.com/show_bug.cgi?id=558250#c21). [See http://bugzilla.novell.com/show_bug.cgi?id=558250#c21 and http://bugzilla.novell.com/show_bug.cgi?id=558250#c22, and attachment https://bugzilla.novell.com/attachment.cgi?id=333588. The following debug packages were installed since ever: OpenOffice_org-base-debuginfo-3.1.1.4-0.1.4.x86_64.rpm OpenOffice_org-libs-core-debuginfo-3.1.1.4-1.1.4.x86_64.rpm OpenOffice_org-calc-debuginfo-3.1.1.4-1.1.4.x86_64.rpm OpenOffice_org-libs-extern-debuginfo-3.1.1.4-1.1.4.x86_64.rpm OpenOffice_org-components-debuginfo-3.1.1.4-1.1.4.x86_64.rpm OpenOffice_org-libs-gui-debuginfo-3.1.1.4-1.1.4.x86_64.rpm OpenOffice_org-filters-debuginfo-3.1.1.4-1.1.4.x86_64.rpm OpenOffice_org-math-debuginfo-3.1.1.4-1.1.4.x86_64.rpm OpenOffice_org-filters-optional-debuginfo-3.1.1.4-1.1.4.x86_64.rpm OpenOffice_org-pyuno-debuginfo-3.1.1.4-1.1.4.x86_64.rpm OpenOffice_org-gnome-debuginfo-3.1.1.4-1.1.4.x86_64.rpm OpenOffice_org-ure-debuginfo-3.1.1.4-1.1.4.x86_64.rpm OpenOffice_org-impress-debuginfo-3.1.1.4-1.1.4.x86_64.rpm OpenOffice_org-writer-debuginfo-3.1.1.4-1.1.4.x86_64.rpm OpenOffice_org-kde4-debuginfo-3.1.1.4-1.1.4.x86_64.rpm ] cd /usr/lib64/ooo3/program gdb ./soffice.bin 2>&1 | tee /tmp/gdb.log GNU gdb (GDB) SUSE (6.8.91.20090930-2.4) Copyright (C) 2009 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-suse-linux". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/lib64/ooo3/program/soffice.bin...Reading symbols from /usr/lib/debug/usr/lib64/ooo3/program/soffice.bin.debug...done. done. (gdb) run Starting program: /usr/lib64/ooo3/program/soffice.bin Missing separate debuginfo for /lib64/ld-linux-x86-64.so.2 Try: zypper install -C "debuginfo(build-id)=591af1afa33f255704fb6a60859b93d00e205302" Missing separate debuginfo for /usr/lib64/libstdc++.so.6 Try: zypper install -C "debuginfo(build-id)=62220ad5c8941afb5d332c0c47d32f8beec8ac50" Missing separate debuginfo for /lib64/libgcc_s.so.1 Try: zypper install -C "debuginfo(build-id)=0206e11fa8ca0db0633073adcbf1349a7871e1dc" Missing separate debuginfo for /lib64/libc.so.6 Try: zypper install -C "debuginfo(build-id)=c5a3dfd66bf61fcdec9bc22153b2fbd0d6697960" Missing separate debuginfo for /lib64/libcrypt.so.1 Try: zypper install -C "debuginfo(build-id)=b4127c6e9abfb7711018173fc6010b5853a5a781" Missing separate debuginfo for /lib64/libdl.so.2 Try: zypper install -C "debuginfo(build-id)=44e66ebae672563bd496f290e08d316bc3bf0ac7" Missing separate debuginfo for /lib64/libpthread.so.0 Try: zypper install -C "debuginfo(build-id)=7bcbabc9da24424f1f5ef7be77b575fd3d796288" Missing separate debuginfo for /lib64/libm.so.6 Try: zypper install -C "debuginfo(build-id)=57fc1891d8d9f419fb8c7fc06a8285563b53a47e" [Thread debugging using libthread_db enabled] Missing separate debuginfo for /usr/lib64/libjpeg.so.62 Try: zypper install -C "debuginfo(build-id)=ce95cfb1c72cc3f5bf63e48bc4bc6b55fd43ef7a" Missing separate debuginfo for /usr/lib64/libicuuc.so.42 Try: zypper install -C "debuginfo(build-id)=4ae95777e2029933f5f94a56bfd088ee8fa90273" Missing separate debuginfo for /lib64/libz.so.1 Try: zypper install -C "debuginfo(build-id)=763926681ebc75fcd9de7b99f7229ff15c7d1754" Missing separate debuginfo for /usr/lib64/libicule.so.42 Try: zypper install -C "debuginfo(build-id)=72c0cbcd0ccd104e7075c478b9ec576f0b411774" Missing separate debuginfo for /usr/lib64/libfreetype.so.6 Try: zypper install -C "debuginfo(build-id)=548e35b1efff83633f9244c84f02d37571e8ac19" Missing separate debuginfo for /usr/lib64/libX11.so.6 Try: zypper install -C "debuginfo(build-id)=5fa84adc30db95abcbaea20ed7ec1c8dd94dfff2" Missing separate debuginfo for /usr/lib64/libxml2.so.2 Try: zypper install -C "debuginfo(build-id)=195817dfa9ad7b02ae338b694abaff09c2eeca36" Missing separate debuginfo for /usr/lib64/libgdk-x11-2.0.so.0 Try: zypper install -C "debuginfo(build-id)=b790d45d12271f7de80fc24169ecf82071cb832d" Missing separate debuginfo for /usr/lib64/libcairo.so.2 Try: zypper install -C "debuginfo(build-id)=eff393400f13166189b42ccd85c24395cb62901a" Missing separate debuginfo for /usr/lib64/libxcb.so.1 Try: zypper install -C "debuginfo(build-id)=54a77c10d44b40080d6d8e65d277ccb7ab2a5b4a" Missing separate debuginfo for /usr/lib64/libpangocairo-1.0.so.0 Try: zypper install -C "debuginfo(build-id)=92f8e672ab08d6acb437334716aa34af3006624c" Missing separate debuginfo for /usr/lib64/libpango-1.0.so.0 Try: zypper install -C "debuginfo(build-id)=1afe045ecc021366c0515b4dad6e66fe0ebe771e" Missing separate debuginfo for /usr/lib64/libfontconfig.so.1 Try: zypper install -C "debuginfo(build-id)=91c40a3235e928f04acc6b7d9c308f9db5502b20" Missing separate debuginfo for /usr/lib64/libXext.so.6 Try: zypper install -C "debuginfo(build-id)=a14cd41f23af7f31d0ac2bd8eada730888690b27" Missing separate debuginfo for /usr/lib64/libXrender.so.1 Try: zypper install -C "debuginfo(build-id)=55f90cfa8482fae594e59cce00c20937e7257446" Missing separate debuginfo for /usr/lib64/libXinerama.so.1 Try: zypper install -C "debuginfo(build-id)=c7af2457b235b84f26ce24f1c4d260ec7eeb9f88" Missing separate debuginfo for /usr/lib64/libXi.so.6 Try: zypper install -C "debuginfo(build-id)=d278c56b4359f6a219af5e13576873a38581c25c" Missing separate debuginfo for /usr/lib64/libXrandr.so.2 Try: zypper install -C "debuginfo(build-id)=6a1fccee186ebf368f2d6a7d5ccd582943fd1953" Missing separate debuginfo for /usr/lib64/libXcursor.so.1 Try: zypper install -C "debuginfo(build-id)=56d901d8946aefda2e4b5e12dba24c13ac3f61a9" Missing separate debuginfo for /usr/lib64/libXcomposite.so.1 Try: zypper install -C "debuginfo(build-id)=04bac2797b48183b0534d8ab8a481383e12680aa" Missing separate debuginfo for /usr/lib64/libXdamage.so.1 Try: zypper install -C "debuginfo(build-id)=650d88fdf900daadd8ba1c9134c21b4e68b560bc" Missing separate debuginfo for /usr/lib64/libXfixes.so.3 Try: zypper install -C "debuginfo(build-id)=6495446f04c2f9a4fa3021f7322d6f12c4017305" Missing separate debuginfo for /usr/lib64/libgdk_pixbuf-2.0.so.0 Try: zypper install -C "debuginfo(build-id)=20edddb566b82a691512c3bc94f4d6ae4167192c" Missing separate debuginfo for /usr/lib64/libgio-2.0.so.0 Try: zypper install -C "debuginfo(build-id)=08ca9202ff9c75bc7271ef47e5bbad43a2a0c36d" Missing separate debuginfo for /usr/lib64/libgobject-2.0.so.0 Try: zypper install -C "debuginfo(build-id)=f19847d70b70328d99de6303ce77402c1c0ad267" Missing separate debuginfo for /usr/lib64/libglib-2.0.so.0 Try: zypper install -C "debuginfo(build-id)=7e3842ab0a347df5f56a0697077f4eca83bfe5fe" Missing separate debuginfo for /usr/lib64/libpixman-1.so.0 Try: zypper install -C "debuginfo(build-id)=e2796f6ce8e24789f258c0047a7ad1c47eeae67d" Missing separate debuginfo for /usr/lib64/libpng12.so.0 Try: zypper install -C "debuginfo(build-id)=67ebdd04bd0be9a64a35354cb80d8ba2b0221f8f" Missing separate debuginfo for /usr/lib64/libxcb-render-util.so.0 Try: zypper install -C "debuginfo(build-id)=c316459cc02a8eb148173af72236bfa034acd17b" Missing separate debuginfo for /usr/lib64/libxcb-render.so.0 Try: zypper install -C "debuginfo(build-id)=7fdad8a2768f53c44f378b1ce0b4747f045b0ffb" Missing separate debuginfo for /usr/lib64/libXau.so.6 Try: zypper install -C "debuginfo(build-id)=72341bb9d8a1ad2ca2bbced007f3a785121aac28" Missing separate debuginfo for /usr/lib64/libpangoft2-1.0.so.0 Try: zypper install -C "debuginfo(build-id)=ff6ab6a12ac30c66bca001b897d454b901a759cd" Missing separate debuginfo for /usr/lib64/libgmodule-2.0.so.0 Try: zypper install -C "debuginfo(build-id)=8e6cb0d3af9508ac2bfb8db5157694ba8fac5cd9" Missing separate debuginfo for /lib64/libexpat.so.1 Try: zypper install -C "debuginfo(build-id)=73c6b7e33c0787039a38d01b8a08db4f6cac375d" Missing separate debuginfo for /lib64/libresolv.so.2 Try: zypper install -C "debuginfo(build-id)=75e330be16e086696f5aac505e30e9628abc9ca9" Missing separate debuginfo for /lib64/libselinux.so.1 Try: zypper install -C "debuginfo(build-id)=e2a1d921e5eb705fc1e51c5651c04fea1e31bcfd" Missing separate debuginfo for /lib64/libpcre.so.0 Try: zypper install -C "debuginfo(build-id)=faf1aba9b565a29c99ce1d3944978347d6209cc3" Missing separate debuginfo for /usr/lib64/libkdeui.so.5 Try: zypper install -C "debuginfo(build-id)=cbe3c465e0578f3dbd246fec44af62b2170085e5" Missing separate debuginfo for /usr/lib64/libkdecore.so.5 Try: zypper install -C "debuginfo(build-id)=9a289e936c0c7aabfcdb10a0d006b9481be9fdd0" Missing separate debuginfo for /usr/lib64/libQtCore.so.4 Try: zypper install -C "debuginfo(build-id)=5a481b4999bf77ae4e321676edeefebf3ca016d9" Missing separate debuginfo for /usr/lib64/libQtGui.so.4 Try: zypper install -C "debuginfo(build-id)=153db877d0b2be723eb30c307f5be359eecfb047" Missing separate debuginfo for /usr/lib64/libQtSvg.so.4 Try: zypper install -C "debuginfo(build-id)=844b2ce93020733cc3902ef209e6fcd511a59b59" Missing separate debuginfo for /usr/lib64/libSM.so.6 Try: zypper install -C "debuginfo(build-id)=51a2a639c0e174691e5fa6f5d648d835750bc44d" Missing separate debuginfo for /usr/lib64/libICE.so.6 Try: zypper install -C "debuginfo(build-id)=43a0fa4cde51095b57558eb7ed0c90dd90e99fae" Missing separate debuginfo for /usr/lib64/libQtXml.so.4 Try: zypper install -C "debuginfo(build-id)=191780dc8cde58ff79ed64cb6d44a518431b1186" Missing separate debuginfo for /usr/lib64/libXtst.so.6 Try: zypper install -C "debuginfo(build-id)=372dcac1de33eebe36395e8821042e5fd3c021e4" Missing separate debuginfo for /usr/lib64/libQtDBus.so.4 Try: zypper install -C "debuginfo(build-id)=ccb9e3402471c93f49ea0fff6c4d7f75a67f2242" Missing separate debuginfo for /usr/lib64/libQtNetwork.so.4 Try: zypper install -C "debuginfo(build-id)=31e1540f27d5bfbaef3a09231e9132af51097242" Missing separate debuginfo for /lib64/libbz2.so.1 Try: zypper install -C "debuginfo(build-id)=958e1c13f0ca9fdbf19eb82eb3bd37e056d0244d" Missing separate debuginfo for /lib64/liblzma.so.0 Try: zypper install -C "debuginfo(build-id)=8ebcb47bab7c09e368fa3f0a643357c00c16e53a" Missing separate debuginfo for /usr/lib64/libgthread-2.0.so.0 Try: zypper install -C "debuginfo(build-id)=bf745d8917d27e255bf174e08e0e6775de77075b" Missing separate debuginfo for /lib64/librt.so.1 Try: zypper install -C "debuginfo(build-id)=c663e79551b37d4c0c9bc93b252b917bfdedb150" Missing separate debuginfo for /lib64/libuuid.so.1 Try: zypper install -C "debuginfo(build-id)=926afd158a155c4b03dd155013053efcaa53dba0" Missing separate debuginfo for /lib64/libdbus-1.so.3 Try: zypper install -C "debuginfo(build-id)=4ad4dd106eb3658fc1a4e032843edfade99815e7" Missing separate debuginfo for /usr/lib64/gconv/UTF-16.so Try: zypper install -C "debuginfo(build-id)=4dc9c0aff44820b7b04b954c85dc3bd1a9060b2a" Missing separate debuginfo for /usr/lib64/gconv/ISO8859-1.so Try: zypper install -C "debuginfo(build-id)=49ff225f844df9a5eaa3ca88182f63248ab49168" Missing separate debuginfo for /usr/lib64/kde4/plugins/styles/oxygen.so Try: zypper install -C "debuginfo(build-id)=d6cc933ff070152fc7dc05e1296ab0769b5e2773" [New Thread 0x7fffe3515910 (LWP 7582)] [New Thread 0x7fffe2d14910 (LWP 7583)] [New Thread 0x7fffe2015910 (LWP 7584)] [New Thread 0x7fffe072b910 (LWP 7585)] Missing separate debuginfo for /usr/lib64/libicui18n.so.42 Try: zypper install -C "debuginfo(build-id)=a2c65ebbb577a06df0b78aa843ace2c18733c414" Missing separate debuginfo for /usr/lib64/libcups.so.2 Try: zypper install -C "debuginfo(build-id)=680b383e4cbb62248754f056f47273781c3b1d2f" Missing separate debuginfo for /usr/lib64/libgssapi_krb5.so.2 Try: zypper install -C "debuginfo(build-id)=6df5fc58564bab665691e0e8474960c9a19de006" Missing separate debuginfo for /usr/lib64/libssl.so.0.9.8 Try: zypper install -C "debuginfo(build-id)=dfe375bc9207e21034ae1dbc7923007901b64482" Missing separate debuginfo for /usr/lib64/libcrypto.so.0.9.8 Try: zypper install -C "debuginfo(build-id)=a38dcf51609e7f91ad69c7285176e884e7eb8e41" Missing separate debuginfo for /usr/lib64/libkrb5.so.3 Try: zypper install -C "debuginfo(build-id)=28e2e645d50a50b1ec2f5b4c93700538770e2563" Missing separate debuginfo for /usr/lib64/libk5crypto.so.3 Try: zypper install -C "debuginfo(build-id)=63b005e3c750246589ab1a5b3207290e24f7236a" Missing separate debuginfo for /lib64/libcom_err.so.2 Try: zypper install -C "debuginfo(build-id)=4b315beafaf40acf1d3c8a156094a3a49cdb8f2f" Missing separate debuginfo for /usr/lib64/libkrb5support.so.0 Try: zypper install -C "debuginfo(build-id)=12c44ad3cd1a7e48a6d4ffc11b47d692d2a32105" Missing separate debuginfo for /lib64/libkeyutils.so.1 Try: zypper install -C "debuginfo(build-id)=53ad26a72efff14594606a7e0ac497cd7e3f3bac" Detaching after fork from child process 7586. Missing separate debuginfo for /lib64/libnss_files.so.2 Try: zypper install -C "debuginfo(build-id)=fd656fa732f43424cda6b0823514aa1322b68eba" [New Thread 0x7fffdd6d6910 (LWP 7588)] Missing separate debuginfo for /lib64/libnss_compat.so.2 Try: zypper install -C "debuginfo(build-id)=29336a415b26508a447b48beb32a8480a6d83b4e" Missing separate debuginfo for /lib64/libnsl.so.1 Try: zypper install -C "debuginfo(build-id)=47b46e38566ceca1ba0764746a0246eba86db3c3" Missing separate debuginfo for /lib64/libnss_nis.so.2 Try: zypper install -C "debuginfo(build-id)=1c578c95d9518b0b6f112acfc0b742b5281a1da4" [Thread 0x7fffdd6d6910 (LWP 7588) exited] Missing separate debuginfo for /usr/lib64/libdb-4.5.so Try: zypper install -C "debuginfo(build-id)=04e1076a7090062ba79309f37c5c307b34699e57" Missing separate debuginfo for /usr/lib64/libxslt.so.1 Try: zypper install -C "debuginfo(build-id)=611ae06635eea916791b3f84a5d0e88f53f3c1d4" [New Thread 0x7fffdd6d6910 (LWP 7589)] Missing separate debuginfo for /usr/lib64/libldap-2.4.so.2 Try: zypper install -C "debuginfo(build-id)=a6589125e52ab8244be633dd1eaa8311c8f7e42d" Missing separate debuginfo for /usr/lib64/liblber-2.4.so.2 Try: zypper install -C "debuginfo(build-id)=f75d3a47b04b3cf4be017b98ea49931ed0bb80fe" Missing separate debuginfo for /usr/lib64/libsasl2.so.2 Try: zypper install -C "debuginfo(build-id)=55530c7b3537a108922877cabd94865da25308ed" [New Thread 0x7fffd61fd910 (LWP 7591)] [Thread 0x7fffd61fd910 (LWP 7591) exited] [New Thread 0x7fffd61fd910 (LWP 7592)] [New Thread 0x7fffd38b3910 (LWP 7593)] [Thread 0x7fffd38b3910 (LWP 7593) exited] Missing separate debuginfo for /usr/lib64/libhunspell-1.2.so.0 Try: zypper install -C "debuginfo(build-id)=c033685be4451c88d3d5856624d675fab819fffc" Missing separate debuginfo for /usr/lib64/jvm/java-1.6.0-openjdk-1.6.0/jre/lib/amd64/server/libjvm.so Try: zypper install -C "debuginfo(build-id)=29f591fd41033fcf0ba46167fb7b1a4c854244e4" Missing separate debuginfo for /usr/lib64/jvm/java-1.6.0-openjdk-1.6.0/jre/lib/amd64/libverify.so Try: zypper install -C "debuginfo(build-id)=f91547764406253d6caba113cedcb1e98af617f8" Missing separate debuginfo for /usr/lib64/jvm/java-1.6.0-openjdk-1.6.0/jre/lib/amd64/libjava.so Try: zypper install -C "debuginfo(build-id)=6ecd91ce962d7632845b8a0d19a4fa48d51553e2" Missing separate debuginfo for /usr/lib64/jvm/java-1.6.0-openjdk-1.6.0/jre/lib/amd64/native_threads/libhpi.so Try: zypper install -C "debuginfo(build-id)=e43ad24e68d1d8d144fc1917c2eb34fb3efc157c" Missing separate debuginfo for /usr/lib64/jvm/java-1.6.0-openjdk-1.6.0/jre/lib/amd64/libzip.so Try: zypper install -C "debuginfo(build-id)=69f8edec04a9b4495dd0f5b3da23aab2707320e2" [New Thread 0x7fffd1019910 (LWP 7594)] [New Thread 0x7fffd0f18910 (LWP 7595)] [New Thread 0x7fffd0c7b910 (LWP 7596)] [New Thread 0x7fffd0b7a910 (LWP 7597)] [New Thread 0x7fffd0a79910 (LWP 7598)] [New Thread 0x7fffd0978910 (LWP 7599)] [New Thread 0x7fffd0877910 (LWP 7600)] [New Thread 0x7fffd0776910 (LWP 7601)] [New Thread 0x7fffd0675910 (LWP 7602)] [New Thread 0x7fffd0574910 (LWP 7603)] [New Thread 0x7fffd27b5910 (LWP 7604)] Program received signal SIGSEGV, Segmentation fault. 0x00007fffc907c6c3 in ?? () (gdb) cont Continuing. warning: line 6432: incompatible stripping characters and condition warning: line 6444: incompatible stripping characters and condition Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffd61fd910 (LWP 7592)] 0x00007fffc90fb6a5 in ?? () (gdb) cont Continuing. Program received signal SIGSEGV, Segmentation fault. 0x00007fffc9103a67 in ?? () (gdb) cont Continuing. error: empty dic file Hash Manager Error : 2 Program received signal SIGSEGV, Segmentation fault. 0x00007fffc91142e0 in ?? () (gdb) cont Continuing. Program received signal SIGSEGV, Segmentation fault. 0x00007fffc9147d62 in ?? () (gdb) cont Continuing. Program received signal SIGSEGV, Segmentation fault. 0x00007fffc909b210 in ?? () (gdb) cont Continuing. QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPixmap: It is not safe to use pixmaps outside the GUI thread QPainter::begin: Cannot paint on a null pixmap QPainter::save: Painter not active QPainter::translate: Painter not active QPainter::translate: Painter not active QPainter::setPen: Painter not active QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::translate: Painter not active QPainter::setPen: Painter not active QPainter::restore: Unbalanced save/restore QPainter::save: Painter not active QPainter::translate: Painter not active QPainter::translate: Painter not active QPainter::setPen: Painter not active QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::translate: Painter not active QPainter::setPen: Painter not active QPainter::restore: Unbalanced save/restore QPainter::save: Painter not active QPainter::translate: Painter not active QPainter::translate: Painter not active QPainter::setPen: Painter not active QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::translate: Painter not active QPainter::setPen: Painter not active QPainter::restore: Unbalanced save/restore QPainter::save: Painter not active QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setPen: Painter not active QPainter::setBrush: Painter not active QPainter::setPen: Painter not active QPainter::setPen: Painter not active QPainter::setBrush: Painter not active QPainter::setBrush: Painter not active QPainter::setPen: Painter not active QPainter::restore: Unbalanced save/restore X-Error: BadDrawable (invalid Pixmap or Window parameter) Major opcode: 62 (X_CopyArea) Resource ID: 0x0 Serial No: 56655 (56655) These errors are reported asynchronously, set environment variable SAL_SYNCHRONIZE to 1 to help debugging [New Thread 0x7fffd38b3910 (LWP 7605)] [Thread 0x7fffd27b5910 (LWP 7604) exited] [Thread 0x7fffd0978910 (LWP 7599) exited] [Thread 0x7fffd0a79910 (LWP 7598) exited] [Thread 0x7fffd0b7a910 (LWP 7597) exited] [Thread 0x7fffd61fd910 (LWP 7592) exited] [Thread 0x7fffdd6d6910 (LWP 7589) exited] [Thread 0x7fffe072b910 (LWP 7585) exited] [Thread 0x7fffe2015910 (LWP 7584) exited] [Thread 0x7fffe3515910 (LWP 7582) exited] [Thread 0x7fffd1019910 (LWP 7594) exited] [Thread 0x7fffd0f18910 (LWP 7595) exited] [Thread 0x7fffd0c7b910 (LWP 7596) exited] [Thread 0x7fffd0877910 (LWP 7600) exited] [Thread 0x7fffd0776910 (LWP 7601) exited] [Thread 0x7fffd0675910 (LWP 7602) exited] [Thread 0x7fffe2d14910 (LWP 7583) exited] [Thread 0x7fffd0574910 (LWP 7603) exited] [Thread 0x7fffd38b3910 (LWP 7605) exited] Program exited with code 0116. [As suggested me Petr Mladek, http://bugzilla.novell.com/show_bug.cgi?id=558250#c21:] (gdb) thread apply all backtrace [As I didn't see any screen output, I thought it went wrong, so I followed the steps in http://en.opensuse.org/Bugs:OOo before realize that simply perhaps it was all.] (gdb) backtrace No stack. (gdb) thread apply all bt (gdb) quit Thanks for the backtrace. Just one comment. Please, do not paste it to the comment next time. It is long and it is better to attach it as a file. Anyway, as I already mentioned in the comment #21 the message "QPixmap: It is not safe to use pixmaps outside the GUI thread" is related to the bug #548354. A workaround is to remove/rename the file /usr/lib64/ooo3/basis-link/program/libvclplug_kde4lx.so It should be fixed in OOo-3.2-rc2. It should appear the following week in the OpenOffice.org:UNSTABLE reporistory, see http://en.opensuse.org/Additional_YaST_Package_Repositories#OpenOffice.org_UNSTABLE Also, it will will be in the OOO-3.2-final that will appear in the OpenOffice.org:STABLE repository within next few weeks, see http://en.opensuse.org/Additional_YaST_Package_Repositories#OpenOffice.org_STABLE Please, try to remove /usr/lib64/ooo3/basis-link/program/libvclplug_kde4lx.so and tell us if it solved some of your problems. Created attachment 336887 [details] The same as above, but the missing debuginfo packages for requested libraries by OOo were installed: gdb.log to soffice.bin. gdb.log to soffice.bin, following suggestion of Petr Mladek. See https://bugzilla.novell.com/show_bug.cgi?id=558250#c21 and https://bugzilla.novell.com/show_bug.cgi?id=558250#c22, and attachment https://bugzilla.novell.com/attachment.cgi?id=333588. As suggested me Petr Mladek, I did thread apply all backtrace And later followed the steps in http://en.opensuse.org/Bugs:OOo. (In reply to comment #24) > Thanks for the backtrace. Just one comment. Please, do not paste it to the > comment next time. It is long and it is better to attach it as a file. Ups! I am sorry, but I did realize it, so at the same time you replied me I was sending a newer gdb.log https://bugzilla.novell.com/attachment.cgi?id=336887 with some changes. > > Anyway, as I already mentioned in the comment #21 the message > "QPixmap: It is not safe to use pixmaps outside the GUI thread" > is related to the bug #548354. > > A workaround is to remove/rename the file > /usr/lib64/ooo3/basis-link/program/libvclplug_kde4lx.so I am sorry: I thought that to rename this file was better after sending the log thinking that renaming might produce changes in it that could make difficult to compare both outputs... > > It should be fixed in OOo-3.2-rc2. It should appear the following week in the > OpenOffice.org:UNSTABLE reporistory, see > http://en.opensuse.org/Additional_YaST_Package_Repositories#OpenOffice.org_UNSTABLE > > Also, it will will be in the OOO-3.2-final that will appear in the > OpenOffice.org:STABLE repository within next few weeks, see > http://en.opensuse.org/Additional_YaST_Package_Repositories#OpenOffice.org_STABLE > > > Please, try to remove /usr/lib64/ooo3/basis-link/program/libvclplug_kde4lx.so > and tell us if it solved some of your problems. Well, All Right, Sir! I'll inform you whatever happens next. And Thank You. mv /usr/lib64/ooo3/basis-link/program/libvclplug_kde4lx.so /usr/lib64/ooo3/basis-link/program/libvclplug_kde4lx.so.bug548354 done. I don't know yet whether it solves my copy-cut-paste troubles, but it solves indeed my https://bugzilla.novell.com/show_bug.cgi?id=558253, so I am going to report it immediately... Petr Mladek, I do not know whether it is soon to state that the copy-cut-paste & the drag and drop issues have passed away as to remove the NEEDINFO tag, because I need to test more than I have done, specially concerning crazy things. But as far as I worked on some documents ODT and that one ODS, it seems that there are no longer the copy-cut-paste & the drag and drop issues. However, I have noticed that after removing /usr/lib64/ooo3/basis-link/program/libvclplug_kde4lx.so: 1. the bug https://bugzilla.novell.com/show_bug.cgi?id=558253 is solved; 2. a bug involving the OOo search dialog, in which the user couldn't introduce a new work to search o to replace easily because the list of previous searches and replaces were shown, not reported yet, or at least, not for me, is solved also; but, 3. a new bug arose related with the removing /usr/lib64/ooo3/basis-link/program/libvclplug_kde4lx.so: When using "Save as..." functionality, through the icon or through the keyboard shortcut, the OOo crashes stating that an unknown error had occurred and to save the document is needed. When the user open any document, a recovery dialog appears for recovery the-said-so-saved document, so it seems that it wasn't saved. The user may confirm that suggestion by the date and time information of the file, which is unchanged (in a not noatime mounted fs) and if, instead of opening any other document, he opened that file that was crashed: In fact, a recovery dialog appears for recovery the document, and, having finished the recovery, a first copy is load: that that was supposed to be saved, but a second copy (is marked by <2>) is also load with the document as it was before the "Save As..."-crash-save sequence. Restoring /usr/lib64/ooo3/basis-link/program/libvclplug_kde4lx.so solves this issue. If I understand it correctly: + the original bug does not longer appear + bug with the search dialog is being solved as the bug #571373 + the new bug with search dialog is being solved as the bug #571374 => nothing more to solve here => closing this bug as WORKSFORME If you see the original bug again, please open new bug for it and just make a note about this one. The problem is that this bug is a bit messy. We discussed too many things here and it is hard to find the important information. Anyway, thanks a lot for patience and testing. Roman is working hard on fixing all the KDE4-related issues and I am sure that it will be much better in OOo-3.2. After installing the following packages from OBS at December 21th, 2010, this issue reappeared: OpenOffice_org-base-extensions-3.2.1.6-1.2.x86_64.rpm OpenOffice_org-impress-3.2.1.6-1.2.x86_64.rpm OpenOffice_org-calc-3.2.1.6-1.2.x86_64.rpm OpenOffice_org-impress-extensions-3.2.1.6-1.2.x86_64.rpm OpenOffice_org-calc-extensions-3.2.1.6-1.2.x86_64.rpm OpenOffice_org-math-3.2.1.6-1.2.x86_64.rpm OpenOffice_org-draw-3.2.1.6-1.2.x86_64.rpm OpenOffice_org-writer-3.2.1.6-1.2.x86_64.rpm OpenOffice_org-draw-extensions-3.2.1.6-1.2.x86_64.rpm OpenOffice_org-writer-extensions-3.2.1.6-1.2.x86_64.rpm OpenOffice_org-l10n-es-3.2.1.6-1.2.noarch.rpm (the new versions available from OBS are just for them) However I have not serious crashes (seldom) and the recovery seems to work fine at 100%, the cut and paste frequently fails: some times, although I have something in the clipboard, the paste icon is inactive, but Ctrl+V works. some times, nothing is pasted (neither with Ctrl+v, but just under OOo, because most of the times when this happens I am able to paste the content into another application); some times, after a certain amount of time (no more than a minute), even the clipboard itself is cleared (klipper) and some times it pasted unformatted text, so all styles are lost (italics, and so on, but also tables, graphics, &c.). For instance: Número 0 Septiembre de 1984 Junio de 2000 7 de octubre de 2010 26 de octubre de 2010 13 de noviembre de 2010 20 de diciembre de 2010 27 de diciembre de 2010 Índice B/A 0 0.19 0.26 0.1 0.1 0.04 0.16 0.07 it was a 9x2 table. It is not as critical as it was a year ago. Usually it is enough to undo and retry the operation, without restart OOo. Should I to choose between a working document fields updating corrected with those packages and a more or less working cut & paste without crashes and good recovery with the previous released? I think that this last year was not good. Also, 11.3 is buggy. A lot of issues I deal with are not really fixed in 11.3, and there are more which are not present in 11.2. For instance: Dolphin crashes when I drag and drop many files (a 1000, for instance) to move, copy or link; operations that I have to do with bash, and then are well done. Thus I realized that most of SuSE 11.2 faults do persist, but I learned to avoid them, to prevent them... I am just accustomed to the OS: I unconsciously know what button not to press or what function not to ask, or what operation to not perform, and I do not press, ask or perform. So, 11.2 is not so good. To switch to 11.3 is not an option. Also, it is not an option to switch to Gnome. I hate Gnome, and if something goes wrong with KDE is this Gnome-looks now has. I am not lying: I still have an old Compaq Presario 7111LA wit 10.2: although obsolete 10.2 has been the finest version of SuSE I ever had. The problem is that I can not make it work in my newer computers, else will do downgrade SuSE till 10.2! So bad I think the things are, and not only dealing with OOo, but also Dolphin, Xournal, Okular, Firefox (mainly but not all)... Do I dealing with production usable and stable systems or with alpha developments. Please see comment #29, in particular the part about opening a new bugreport, and not polluting the bugreport by including every irrelevant information that comes to your mind. This bugreport has so much noise information that it is next to useless. *** Bug 577579 has been marked as a duplicate of this bug. *** |