https://bugs.documentfoundation.org/show_bug.cgi?id=160512

Stéphane Guillou (stragu) <stephane.guil...@libreoffice.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |stephane.guillou@libreoffic
                   |                            |e.org

--- Comment #11 from Stéphane Guillou (stragu) 
<stephane.guil...@libreoffice.org> ---
(In reply to Peter Zwitser from comment #10)
> I really don't know what happened, but it looks like it is solved.
> Just for information I'll tell what I did (or actually: not did...)
> 
> 1) removed libreOffice completely.
> 2) removed the PPA with libreOffice.
> 3) installed the default version from Neod. That's version 7 and something.
> 4) The problem still existed.
> 
> So it started to look it had nothing to do with the latest update from
> LibreOffice. I noticed the problem the same day LibreOffice was updated, so
> I thought it had to do with that update.
> Maybe it was something in my system that was recently changed? That would
> also explain why it's hard to reproduce the bug for other people.
> 
> 5) Logged out and logged in again, but this time not with X11 but with
> Wayland.
> 
> Problem was gone. Ah, so it probably has something to do with the
> combination LibreOffice/X11.
> But Wayland has (for the moment) a lot of other problems, so I'd really
> prefer for the moment X11.
> 
> 6) Logged out and logged in again, but now again with X11.
> 
> I was planning to start reading about settings from X11.
> But to my big surprise the problem is gone. I copied all kind of texts about
> a hundred times, because I couldn't believe it, but it's really gone. Even
> restarted the system to be sure.
> 
> I didn't change anything at all, except changing from X11 to Wayland and
> back.
> 
> Sorry for the time you have spent, but since this happened just after the
> update from LibreOffice I really thought it had something to do with that
> update.

Peter, could it be that in the meantime you upgraded to 24.2.3, perhaps? See
bug 160751 and related: several users report 24.2.2 crashing then the issue
resolved in 24.2.3.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to