FS#56148 - [freecad] Freecad Crashes on New File

Attached to Project: Community Packages
Opened by John BS (johnabs) - Sunday, 29 October 2017, 07:23 GMT
Last edited by Florian Pritz (bluewind) - Saturday, 02 December 2017, 22:24 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Florian Pritz (bluewind)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: I cannot create new documents in FreeCAD. I found a single post on a forum with a similar bug, and after reproducing the solution, the bug remains.

P.S. Please be gentle senpai, this is my first time...(submitting a bug report).


Additional info:
* version: 0.16 Revision: 6712-3 built 2017-10-18 16:59 UTC (so it's not dead/outdated/unsupported)

* coredump output


Steps to reproduce:
1. pacman -S freecad

2. run freecad (either from terminal or launcher like dmenu or rofi)
Gui appears at this point
3. Open drawing or document of some sort.

4. Try to make a new document. Segmentation fault occurs here.

5. Changing preferences to make a new document on startup also causes a segmentation fault and prevents the gui from opening at all.

Extra note, these are the packages installed by pacman during installation, any other dependencies I must already have installed, but it appears to be an issue primarily with the use of the qt4-4.8.7-22 package I believe Thank you for your help. <script src="https://pastebin.com/embed_js/8figdFcY"></script>
This task depends upon

Closed by  Florian Pritz (bluewind)
Saturday, 02 December 2017, 22:24 GMT
Reason for closing:  Works for me
Comment by John BS (johnabs) - Sunday, 29 October 2017, 07:26 GMT
Whoops, I tried to be fancy and embed the pastebin links. Here they are in the order they were posted in the document: https://pastebin.com/iGxFESA6 and https://pastebin.com/8figdFcY Sorry about that!
Comment by Florian Pritz (bluewind) - Wednesday, 01 November 2017, 15:35 GMT
Do you run nvidia and if so can you try downgrading it? For me this bug appears to be caused by nvidia 387.22-4. 387.12-2 works fine.
Comment by Florian Pritz (bluewind) - Wednesday, 01 November 2017, 16:03 GMT
Works again for me after a reboot. Can you check?
Comment by John BS (johnabs) - Wednesday, 01 November 2017, 18:15 GMT
I've tried the reboot solution a few times and that failed, I'll try again momentarily. I am not running the nvidia package (I checked with pacman -Qe | grep nvidia), but I do have nvidia-340xx package, version 340.104-2, should I also downgrade this one? Thank you for your help thus far!
Comment by John BS (johnabs) - Wednesday, 01 November 2017, 18:26 GMT
I have rebooted after installation again, and still no dice.
Comment by Florian Pritz (bluewind) - Wednesday, 01 November 2017, 18:54 GMT
Yes, check in /var/log/pacman.log which nvidia-340xx package you had before freecad broke and then install it with `pacman -U /var/cache/pacman/pkg/nvidia-340xx-$version.pkg.tar.xz`. Also you may need to reboot after downgrading the package.
Comment by John BS (johnabs) - Thursday, 02 November 2017, 03:04 GMT
I downgraded to nvidia-340xx-340.104-1 and still no dice. I cannot downgrade further as I would also need to downgrade my kernel (old version requires less than 4.13.9). Would I be better off installing a different nvidia package to try this out or should I try installing ? Is there any other diagnostic information I could provide to you? I'm seriously at a loss here, and I'm sorry I'm not sure what else I can do on my end and why it is non-functional.
Comment by John BS (johnabs) - Thursday, 02 November 2017, 03:10 GMT
Also, if this helps, I am running a Thinkpad T420 without an Nvidia card (intel integrated graphics it would seem).
Comment by John BS (johnabs) - Thursday, 02 November 2017, 03:14 GMT
After removing the unnecessary nvidia packages (for some reason I had previously installed bumblebee) still no dice, should I try installing the package you recommended?
Comment by Florian Pritz (bluewind) - Thursday, 02 November 2017, 08:48 GMT
In your case it might be related the to mesa package. Try downgrading that instead.

If you want more responsive help, I suggest you talk to the folks in the #archlinux IRC channel. I believe there should be people active at any time of the day.

Loading...