| Summary: | Update request: librecad latest stable version 1.0.0 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Funda Wang <fundawang> |
| Component: | RPM Packages | Assignee: | Funda Wang <fundawang> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | davidwhodgins, qa-bugs |
| Version: | 1 | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | librecad-1.0.0-1.mga1.i586.rpm | CVE: | |
| Status comment: | |||
| Attachments: | Backtrace | ||
|
Description
Funda Wang
2012-01-30 08:24:27 CET
x86_64 I drew two circles and some lines to make it into a cylinder then added some text. When I was trying to rotate the text (without really knowing what I was doing) I caused a segfault. Jan 30 15:07:07 localhost kernel: librecad[21879]: segfault at bc ip 0000000000574820 sp 00007ffffd917298 error 6 in librecad[400000+42b000] I'll haven't been able to reproduce it. Apart from that, it all seems to work including print preview and exporting to png. Created attachment 1463 [details]
Backtrace
Consistently recreated the segfault.
Select Draw/Test, Type in some text. Select Ok.
Left click to insert the text object.
Select Select/Select Entity. Left click on the text.
Right click on the text. Segfault.
Is it the same as this one ? https://github.com/LibreCAD/LibreCAD/issues/235 Never mind, above problem should appear in final 1.0.0. Please test this one: http://sourceforge.net/tracker/?func=detail&aid=3467128&group_id=342582&atid=1433844 (In reply to comment #4) > Never mind, above problem should appear in final 1.0.0. Please test this one: > http://sourceforge.net/tracker/?func=detail&aid=3467128&group_id=342582&atid=1433844 That one produces a segfault in QG_CadToolBarSelect::runNextAction. Comment 2 produces a segfault in RS_ActionSelect::requestFinish, so they're not the same. CC:
(none) =>
davidwhodgins If possible, I would suggest you report this issue upstream at: http://sourceforge.net/tracker/?func=add&group_id=342582&atid=1433844 Then, we will wait 1.0.1 to have this update pushed. Status:
NEW =>
ASSIGNED Reported upstream ... https://sourceforge.net/tracker/?func=detail&aid=3481768&group_id=342582&atid=1433844 From the upstream report. ... Comment By: Dongxu Li (dongxuli) Date: 2012-01-30 21:53 Message: fixed in 1.0.0-SNAPSHOT, commit: 883ec62..9780baf the same bug has been previously fixed in master branch: bug#3437138, commit: 429a1309f I think the one you reported was the same segfault I noticed Dave. I do remember right clicking now you mention it. Well done for finding it again!
claire robinson
2012-02-05 16:58:35 CET
CC:
(none) =>
qa-bugs Here's the link to the original bug report where they say it was fixed ... http://sourceforge.net/tracker/?func=detail&aid=3437138&group_id=342582&atid=1433844 Funda, librecad 1.0.1 is now available, so this update could be continued. 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:
ASSIGNED =>
RESOLVED |