http://bugzilla.opensuse.org/show_bug.cgi?id=1089941 http://bugzilla.opensuse.org/show_bug.cgi?id=1089941#c3 --- Comment #3 from Frank Voorburg --- (In reply to Tomáš Chvátal from comment #1)

Does it happen also if you just open ie oowriter binary? Or empty documents load up fast?

The same problem occurs when using the oowriter binary directly. I ran the following from the terminal to produce the problem: oowriter /home//Desktop/test.odt The document is just an empty document with one line of text. I attached it for reference purposes. Starting LibreOffice writer on its own it not delayed. The problem only occurs when loading a document, if no other document as open yet. I also found out that saving a document for the first time seems to cause a similar delay. So I start LibreOffice writer and then save the file after adding a little bit of text. If then takes about the same delay to actually save the file. If I then modify the text and save again, it goes fast as expected. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1089941 http://bugzilla.opensuse.org/show_bug.cgi?id=1089941#c5 --- Comment #5 from Tomáš Chvátal --- (In reply to Frank Voorburg from comment #3)

(In reply to Tomáš Chvátal from comment #1)

...

Does it happen also if you just open ie oowriter binary? Or empty documents load up fast?

The same problem occurs when using the oowriter binary directly. I ran the following from the terminal to produce the problem: oowriter /home//Desktop/test.odt

The document is just an empty document with one line of text. I attached it for reference purposes.

Starting LibreOffice writer on its own it not delayed. The problem only occurs when loading a document, if no other document as open yet.

I also found out that saving a document for the first time seems to cause a similar delay. So I start LibreOffice writer and then save the file after adding a little bit of text. If then takes about the same delay to actually save the file. If I then modify the text and save again, it goes fast as expected.

You can try to run the package using strace to see if it is looking up something or waiting or something... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1089941 http://bugzilla.opensuse.org/show_bug.cgi?id=1089941#c7 --- Comment #7 from Frank Voorburg --- Based on your request, I ran strace with the command: strace -o oowriter_strace.log oowriter ~/Downloads/test.odt. See the attached oowriter_strace.log file. It freezes on the following line: rt_sigaction(SIGINT, {sa_handler=0x5616df255a10, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7fb22cd84a70}, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7fb22cd84a70}, 8) = 0 wait4(-1, Then after about 10 seconds oowriter window shows up with the loaded test.odt file and nothing else is outputted by strace. When I close oowriter, the strace output continues on the line that started with "wait4(-1,": wait4(-1, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 3141 rt_sigaction(SIGINT, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7fb22cd84a70}, {sa_handler=0x5616df255a10, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7fb22cd84a70}, 8) = 0 ioctl(2, TIOCGWINSZ, {ws_row=66, ws_col=272, ws_xpixel=0, ws_ypixel=0}) = 0 ioctl(1, TCGETS, {B38400 opost isig icanon echo ...}) = 0 getuid() = 1000 geteuid() = 1000 etc. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1089941 http://bugzilla.opensuse.org/show_bug.cgi?id=1089941#c9 --- Comment #9 from Frank Voorburg --- I did a debug session with gdb, which reports a segmentation fault. I attached a log of my debug session (gdb_session.log). Perhaps someone can inspect it and find the cause of the problem. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1089941 http://bugzilla.opensuse.org/show_bug.cgi?id=1089941#c11 --- Comment #11 from Tomáš Chvátal --- (In reply to Frank Voorburg from comment #10)

Created attachment 767591 [details] GDB session log

You need to install debuginfo packages for this to be useful, it will replace all those ?? with code pointers, see the gdb recommending those zypper in commands -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1089941 http://bugzilla.opensuse.org/show_bug.cgi?id=1089941#c13 --- Comment #13 from Tomáš Chvátal --- (In reply to Frank Voorburg from comment #12)

I had all available debug packages installed. The once that are reported missing cannot be found, unfortunately.

That is weird, it should work even if you copied out the lines verbatim to those in the gdb? Try at least by hand "zypper in glibc-debuginfo libreoffice-debuginfo" -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1089941 http://bugzilla.opensuse.org/show_bug.cgi?id=1089941#c15 Frank Voorburg changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #15 from Frank Voorburg --- After some more testing, I found the cause of the problem and the solution. As you might have seen in the files I attached previously, I have the hostname of my system set to "tumbleweed". It turns out that this is the cause of the problem. The moment I change the hostname to anything else, the reported problem disappears. For verification purposes, I created a new Tumbleweed install in VMware Workstation. By default the hostname was "linux-khi1". At this point the problem was not present. Then after changing the hostname to "tumbleweed" using section Network Settings in Yast, the problem appeared. Changing the hostname to something else, made the problem disappear again. I'll go ahead and update the bug status to resolved. Tomáš, thanks for your assistance and feedback. It is much appreciated. -- You are receiving this mail because: You are on the CC list for the bug.