[Libreoffice-bugs] [Bug 148159] Please check if you get error reports which are assigned to the wrong version of LibreOfficeWriter
https://bugs.documentfoundation.org/show_bug.cgi?id=148159 Dieter changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #8 from Dieter --- (In reply to Adalbert Hanßen from comment #7) > It looks like the bug is fixed in the development version under my operating > conditions. Adalbert, thank you for retesting. => RESOLVED WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148159] Please check if you get error reports which are assigned to the wrong version of LibreOfficeWriter
https://bugs.documentfoundation.org/show_bug.cgi?id=148159 --- Comment #7 from Adalbert Hanßen --- (In reply to Dieter from comment #6) > (In reply to Adalbert Hanßen from comment #4) > > Created attachment 189305 [details] > > the file which crashed LO Writer when double-clicked upon in the file > > browser > > I could open it without any problems > > Version: 7.6.1.2 (X86_64) / LibreOffice Community > Build ID: f5defcebd022c5bc36bbb79be232cb6926d8f674 > CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: > win > Locale: de-DE (de_DE); UI: en-GB > Calc: CL threaded > > Perhaps somebody else can help. Dieter, I just tried to load the file into Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: b3fdd999f87312447d03915585812b3a5cd48141 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: de-DE (de_DE.UTF-8); UI: en-US Calc: threaded and it did not crash. I tried it by going through the normal load file process and I did another trial via Fils>Recent Documents. I did yet another test by double-clicking on the set aside file which I had uploaded when reporting the bug. All three trials did not crash with this version. It looks like the bug is fixed in the development version under my operating conditions. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148159] Please check if you get error reports which are assigned to the wrong version of LibreOfficeWriter
https://bugs.documentfoundation.org/show_bug.cgi?id=148159 --- Comment #6 from Dieter --- (In reply to Adalbert Hanßen from comment #4) > Created attachment 189305 [details] > the file which crashed LO Writer when double-clicked upon in the file browser I could open it without any problems Version: 7.6.1.2 (X86_64) / LibreOffice Community Build ID: f5defcebd022c5bc36bbb79be232cb6926d8f674 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL threaded Perhaps somebody else can help. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148159] Please check if you get error reports which are assigned to the wrong version of LibreOfficeWriter
https://bugs.documentfoundation.org/show_bug.cgi?id=148159 --- Comment #5 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148159] Please check if you get error reports which are assigned to the wrong version of LibreOfficeWriter
https://bugs.documentfoundation.org/show_bug.cgi?id=148159 --- Comment #4 from Adalbert Hanßen --- Created attachment 189305 --> https://bugs.documentfoundation.org/attachment.cgi?id=189305=edit the file which crashed LO Writer when double-clicked upon in the file browser (In reply to Dieter from comment #3) > Hello Adalbert, a new major major release of LibreOffice is available since > this bug was reported. Could you please try to reproduce it with the latest > version of LibreOffice from > https://www.libreoffice.org/download/libreoffice-fresh/ ? > I have set the bug's status to 'NEEDINFO'. Please change it back to > 'UNCONFIRMED' if the bug is still present in the latest version. > > Please test only with older versions, that are still under development I tried it with Version: 7.6.0.3 (X86_64) / LibreOffice Community Build ID: 69edd8b8ebc41d00b4de3915dc82f8f0fc3b6265 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: de-DE (de_DE.UTF-8); UI: de-DE Calc: threaded and I tried to load a file which caused the described error by double-clicking on a file which I had put aside when I reported the bug. The outcome was another crash. During the bug reporting sequence there was a link to https://crashreport.libreoffice.org/stats/crash_details/02b0d723-3657-438b-856b-758278c6cbbc. I followed the link and I observed that it contains information which probably will enable someone to pin this bug. Strangely (after LO Writer was running) I was able to explicitly load the file into it with the open file dialog by explicitly telling the file to open. Strangely I was unable to open it by the open file>Recent dialog: nothing happened. Even more strangely: After trying it several times, now I can open this file by all the described ways. Very strange! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148159] Please check if you get error reports which are assigned to the wrong version of LibreOfficeWriter
https://bugs.documentfoundation.org/show_bug.cgi?id=148159 Dieter changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO CC||dgp-m...@gmx.de --- Comment #3 from Dieter --- Hello Adalbert, a new major major release of LibreOffice is available since this bug was reported. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version. Please test only with older versions, that are still under development -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148159] Please check if you get error reports which are assigned to the wrong version of LibreOfficeWriter
https://bugs.documentfoundation.org/show_bug.cgi?id=148159 Adalbert Hanßen changed: What|Removed |Added Severity|normal |enhancement --- Comment #2 from Adalbert Hanßen --- (In reply to Mike Kaganski from comment #1) > (In reply to Adalbert Hanßen from comment #0) > > If it associates its own version number to the crash report, you'll get one > > under the wrong headline! > > > > Expected Results: > > In case of a crash report, as a user I would expect to see: > > • ... > > You have good point there ... > > Please split it into separate issues. It doesn't matter if the tracker gets > tens more issues; what matters is each one is manageable. This is the split off part about bug reporting. The crash report which triggered it is merely the motivation to show possible causes of trouble by uploaded bug reports and it also suggests an enhancement how to improve this process. I had however forgotten to set the flag "enhancement" which I have set now. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148159] Please check if you get error reports which are assigned to the wrong version of LibreOfficeWriter
https://bugs.documentfoundation.org/show_bug.cgi?id=148159 --- Comment #1 from Mike Kaganski --- (In reply to Adalbert Hanßen from comment #0) > If it associates its own version number to the crash report, you'll get one > under the wrong headline! > > Expected Results: > In case of a crash report, as a user I would expect to see: > • ... You have good point there ... but you put all these *different* issues into a single report, making is completely unmanageable. Every task should have an own issue, to be able to mark it "resolved" independently: e.g., "an indication in which part of the program the error occurred and..." is completely independent from "LibreOfficeWriter keeps track on these issue numbers and dates and ...". Please split it into separate issues. It doesn't matter if the tracker gets tens more issues; what matters is each one is manageable. -- You are receiving this mail because: You are the assignee for the bug.
