Hi,
As the title says…
However, I need t run FreeCAD. Can I roll-back a day?
I use this script nightly:
zypper dup --auto-agree-with-licenses
Regards, Martin
The title doesn’t really say much though… 
How exactly is it broken?
However, I need t run FreeCAD. Can I roll-back a day?
Sure, if you use btrfs and didn’t disable snapshots.
“snapper rollback” is your friend then.
https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.reference/cha.snapper.html
[QUOTE=wolfi323;2854220]The title doesn’t really say much though…
How exactly is it broken?
I was not trying to fix the problem - I was hoping that others (more qualified than I) would be on the problem soon?
But as you ask…
Log from 20180203…
.....
Log: /usr/lib64/FreeCAD/Mod/Inspection
Log: /usr/lib64/FreeCAD/Mod/Drawing
Log: /home/mprowe/bin
Log: /usr/local/bin
Log: /usr/bin
Log: /bin
Log: /opt/cross/bin
Log: /usr/lib/mit/sbin
Log: Init: App::FreeCADInit.py done
Log: Init: Creating Gui::Application and QApplication
Log: Local server 'FreeCAD' started
Log: X Error: BadValue (integer parameter out of range for operation) 2
Major opcode: 53 (X_CreatePixmap)
Resource id: 0x1e
Log: X Error: GLXBadPbuffer 177
Extension: 155 (Uknown extension)
Minor opcode: 28 (Unknown request)
Resource id: 0x0
Log: This system does not support pbuffers
And Log from 20180202…
.....
Log: /usr/local/bin
Log: /usr/bin
Log: /bin
Log: /usr/lib/mit/sbin
Log: Init: App::FreeCADInit.py done
Log: Init: Creating Gui::Application and QApplication
Log: Local server 'FreeCAD' started
Log: OpenGL version 3.0 or higher is present
Log: Run Gui init script
Log: Init: Running FreeCADGuiInit.py start script...
Log: Init: Searching modules...
Log: Init: Initializing /usr/lib64/FreeCAD/Mod/Sketcher... done
Log: Init: Initializing /usr/lib64/FreeCAD/Mod/ReverseEngineering... done
Log: Init: Initializing /usr/lib64/FreeCAD/Mod/Image... done
and so on...
Any thoughts?
Regards, Martin
Probably a Mesa problem. Your log shows a “GLXBadPbuffer” error, and Mesa is actually the only update in the latest snapshot that I would see as possibly relevant here. (and that may be very graphics card/driver specific too)
Unfortunately there is no easy way to downgrade to the previous snapshot AFAIK.
Except btrfs’s snapshots, or a backup.
The previous Mesa packages (17.3.3) are still on the servers currently though (just not listed in the repo metadata anymore), so you probably could download and install them manually.
http://download.opensuse.org/tumbleweed/repo/oss/suse/
But, you might just as well break your system completely by doing that…
Okay… I’ll wait.
Martin
Sorry…
One more supplementary question, if I may?
To whom (and how) could I report this problem? Just in case no one else notices!
Is it a Tumbleweed or Mesa or FreeCAD route?
Regards, Martin
I would report it to http://bugzilla.opensuse.org/ (same username/password as here), component XOrg…
(I don’t think it’s a bug in FreeCAD, as that hasn’t changed)
They might refer you to Mesa upstream though.
Btw, there is a known bug in Mesa 18 that causes crashes:
http://bugzilla.opensuse.org/show_bug.cgi?id=1079465
Should be fixed in the next snapshot, or you could try the testing packages mentioned in that bug report. (you’d need to delete ~/.cache/ as well, that by itself may help already for a while at least…)
But if you use KDE/Plasma, you’d likely not even get a desktop in that case.
PS: a Mesa update is available in Tumbleweed’s Update repo meanwhile, so try to update your system (and delete ~/.cache/).
Although, if you do use Plasma without problems, it probably won’t help… (you didn’t tell what desktop you use)
Sorry to keep this thread open. But…
I can confirm that FreeCAD will run on 20180206 - I built a new system and FreeCAD works.
However, on my main workstation where I first ran into problems, although I have upgraded to 20180206 and deleted ~/.cache, FreeCAD will still not run!
Same error log is generated that I submitted earlier.
I have cleared my system of FreeCAD stuff (app & user settings) and reinstalled. No luck. I guess that something is hanging around that is causing me grief?
Any thoughts or suggestions on debugging will be most welcome.
Best regards, Martin
KDE Plasma 5.12
Are the systems using the same graphics card/driver?
If not that might explain the difference. As I wrote, it may be hardware/driver specific.
To rule out any sort of left-over, try a fresh user account.
Thank you for the suggestion. Sorry to take so lone to get back. Trying to recover from the MESA upgrade problem, eventual trashed my system completely!
So, from this mail, it is “all new” at this end and by implication “a fresh user account”.
First, prior to 20180202, FreeCAD ran on my system (TumbleWeed). Now it will not. This is the Console output:
prowe@gzunder:~> FreeCAD
FreeCAD 0.16, Libs: 0.16RUnknown
© Juergen Riegel, Werner Mayer, Yorik van Havre 2001-2015
##### #### ### ####
# # # # # #
# ## #### #### # # # # #
#### # # # # # # # ##### # #
# # #### #### # # # # #
# # # # # # # # # ## ## ##
# # #### #### ### # # #### ## ## ##
failed to create drawable
[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
FreeCAD: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
Aborted (core dumped)
mprowe@gzunder:~>
Now, as I don’t have unlimited resources, I have created a VM (Oracle VirtualBox) with the same OS (Tumbleweed 20180210) and FreeCAD.
And on that VM, it will run! I still get the “failed to create drawable” so I am suspecting that is a “red herring”?
My guess is that in the VM graphic translation between the client machine and the host machine an error is being corrected or at least “worked around”?
Thus, In summery:
FreeCAD on the host hardware/Tumbleweed WILL NOT run.
FreeCAD on a VM in the host hardware WILL run.
Any thought…
Regards, Martin
Well, Tumbleweed emulates a virtual graphics card, so the installation will use a different graphics driver and likely Mesa’s software OpenGL renderer.
IMHO that confirms that it is some problem in Mesa (i.e. the OpenGL driver for your card), or otherwise related to the graphics driver…
You’d probably get it to work on your real hardware by booting with “nomodeset”, but OpenGL would be quite slow then of course.
What graphics card/driver are you using on the affected system btw?
While I look to the “nomodeset” issue, may I try and answer the above?
Not sure how best to do that though? This any good?
gzunder:~ # lspci -vnn | grep VGA -A 12
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Redwood LE [Radeon HD 5550/5570/5630/6390/6490/7570] [1002:68da] (prog-if 00 [VGA controller])
Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e163]
Flags: bus master, fast devsel, latency 0, IRQ 37
Memory at e0000000 (64-bit, prefetchable) [size=256]
Memory at f79c0000 (64-bit, non-prefetchable) [size=128]
I/O ports at a000 [size=256]
Expansion ROM at 000c0000 [disabled] [size=128]
Capabilities: [50] Power Management version 3
Capabilities: [58] Express Legacy Endpoint, MSI 00
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
Capabilities: [150] Advanced Error Reporting
Kernel driver in use: radeon
gzunder:~ #
Regards, Martin[/size][/size][/size][/size]
I probably should have mentioned it, just press ‘e’ at the boot menu and append “nomodeset” to the line starting with “linux” or “linuxefi” (with a leading space).
That won’t change your system, just affect that one boot…
may I try and answer the above?
Ok, so you are using radeon.
Kind of a pity though, because I would have suggested something in case of intel.
Although, maybe “amdgpu.dc=0” would help in your case?
Seems that amdgpu doesn’t even support your card and isn’t used though.
WooHoooo… It looks like you are on to something here!
Yes, “nomodeset” does make a difference! On the positive side, it will allow FreeCAD to run in GUI mode.
But… As you predicted the Desktop experience is pitifully. Only a single VGA display :’(
And yes, you are correct. As far as I can tell the kernel option "amggpu.dc=<0|1> had no effect that I could detect.
So where could this all be pointing? Do you think that this is likely to be a bug (that could/will be fixed) or a feature that I will need to adjust too?
If the latter, do you think a new graphics card is a solution?
Regards, Martin
You could also try Xorg’s modesetting driver, that should more or less support everything.
The easiest way to do this is uninstalling xf86-video-ati, or you could change the Xorg config.
Although, it might already be used anyway (/var/log/Xorg.0.log would tell).
And it probably won’t make a difference if it’s a bug in Mesa…
And yes, you are correct. As far as I can tell the kernel option "amggpu.dc=<0|1> had no effect that I could detect.
Erm, “amdgpu.dc”…
But yes, this will only affect the amdgpu kernel driver, you are using radeon though.
So where could this all be pointing? Do you think that this is likely to be a bug (that could/will be fixed) or a feature that I will need to adjust too?
I would suspect a bug/regression in Mesa’s OpenGL driver as mentioned.
If the latter, do you think a new graphics card is a solution?
Sure, that could help too.
You’d probably use a different driver then, and the problem might be specific to particular card models too.
One thing you could also try is to install the latest unstable FreeCAD version from here:
https://software.opensuse.org//download.html?project=science%3Aunstable&package=FreeCAD
I cannot tell you how well it works though, or if it may help.
No, you have lost me here:\
I’d like to explore, if you have the patience? Is it possible to attach the Xorg.0.log file. It’s a bit long to include in-line.
Erm, “amdgpu.dc”…
Opps… Finger trouble>:(
One thing you could also try is to install the latest unstable FreeCAD version from here:
https://software.opensuse.org//download.html?project=science%3Aunstable&package=FreeCAD
Yep! That worked a treat!!!rotfl! Some python related messages in the log, but on a very quick scan seemed to be working fine. Yippieeeee…
What does this mean?
Regards, Martin
Hello,
I can confirm this issue too:
FreeCAD 0.16, Libs: 0.16RUnknown
© Juergen Riegel, Werner Mayer, Yorik van Havre 2001-2015
##### #### ### ####
# # # # # #
# ## #### #### # # # # #
#### # # # # # # # ##### # #
# # #### #### # # # # #
# # # # # # # # # ## ## ##
# # #### #### ### # # #### ## ## ##
No protocol specified
failed to create drawable
[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
FreeCAD: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
In the FreeCAD.log tail:
Log: Local server 'FreeCAD' failed to start
Log: X Error: BadValue (integer parameter out of range for operation) 2
Major opcode: 53 (X_CreatePixmap)
Resource id: 0x1e
Log: X Error: GLXBadPbuffer 177
Extension: 155 (Uknown extension)
Minor opcode: 28 (Unknown request)
Resource id: 0x0
Log: This system does not support pbuffers
I Try unstable and actual git version compiled from source - no sense - same result. I go through FreeCAD forum about it, but only found this (expect you now it Martin):
https://forum.freecadweb.org/viewtopic.php?f=4&t=26845&p=214870&hilit=tumbleweed#p214870
My video is also a Radeon:
lspci -vnn | grep VGA -A 12
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Caicos PRO [Radeon HD 7450] [1002:677b] (prog-if 00 [VGA controller])
Subsystem: Bitland(ShenZhen) Information Technology Co., Ltd. Device [1642:3a76]
Flags: bus master, fast devsel, latency 0, IRQ 27
Memory at e0000000 (64-bit, prefetchable) [size=256]
Memory at f7e20000 (64-bit, non-prefetchable) [size=128]
I/O ports at e000 [size=256]
Expansion ROM at 000c0000 [disabled] [size=128]
Capabilities: [50] Power Management version 3
Capabilities: [58] Express Legacy Endpoint, MSI 00
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
Capabilities: [150] Advanced Error Reporting
Kernel driver in use: radeon
Any help suggested.[/size][/size][/size][/size]
You can upload it to some sharing/pasting site like paste.opensuse.org and post a link.
Yep! That worked a treat!!!rotfl! Some python related messages in the log, but on a very quick scan seemed to be working fine. Yippieeeee…
What does this mean?
This means that you could use that version instead…
It also should indicate that the next release (0.17) will run on your system.
Thank you. Here it is: http://paste.opensuse.org/43740
Not sure what I’m looking for though, but if (with a little bit of “tweaking”) I can stay away from the “unstable” side of things, I’d feel more comfortable.
Yes! I know I’m running Tumbleweed. That is only because I hate the yearly “big jump” between versions and was hoping the daily incremental route would give me a smoother life.
Maybe not?
Regards, Martin