| Summary: | Hard system freeze and data loss using updated LibreOffice | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Guillaume Lang <tux> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | dmorganec, ennael1, marja11 |
| Version: | 1 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | libreoffice-3.4.4 | CVE: | |
| Status comment: | |||
| Attachments: | output of "lspcidrake -v" | ||
|
Description
Guillaume Lang
2012-01-16 12:35:28 CET
I have work yesterday 6 hours with LibreOffice without such of issue. (or not the same) So if you can reproduce the backtrace can help (and iirc there is backup in /home/user/.libreoffice/) CC:
(none) =>
dmorganec
Manuel Hiebel
2012-01-18 22:41:18 CET
Keywords:
(none) =>
NEEDINFO (In reply to comment #1) > I have work yesterday 6 hours with LibreOffice without such of issue. (or not > the same) > > So if you can reproduce the backtrace can help @ Guillaume Can you reproduce the crash? If so, could you please read https://wiki.mageia.org/en/Debugging_software_crashes and get a backtrace with gdb? CC:
(none) =>
marja11 and attach it to this bug report, of course :) @ Guillaume Didn't the crashes repeat themselves anymore? @ Guillaume If you can't even switch to tty 2, you won't be able to get a back trace either, sorry we read your report too much in a hurry. So forget about the backtrace we asked for, but tell us whether the problem still occurs. Also, please attach the output of: lspcidrake -v CC'ing someone else who reported a hard system freeze while using LibreOffice, too (bug 4288) CC:
(none) =>
ennael1 Created attachment 1757 [details]
output of "lspcidrake -v"
Apologies for the late answer. I could not get the system to crash again despite similar use patterns, and no extra data loss was observed. I should mention remembering about some older freezes (quite rare) when opening various random LibreOffice documents (unfortunately I did not document this issue). This never resulted in data loss but as this was on opening documents (can't remember if other documents were also active) I can't rule out a common origin. With respect to bug 4288: * Video modules = radeon+i915 (with i915 doing the display and radeon warming the room). * Hardware acceleration is active in LibreOffice. Sorry for being unable to reproduce the bug, I don't get what was then special. @ Guillaume No problem, thx for your reply. Setting severity back to normal. Keywords:
NEEDINFO =>
(none) This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- Mageia Bugsquad Status:
NEW =>
RESOLVED |