Your message dated Thu, 21 Oct 2021 17:30:57 +0200
with message-id <ae34ff90d650976d2768c3f442d9e5cbfb970fe0.ca...@sviech.de>
and subject line Re: Bug#930563: Can not start freecad
has caused the Debian Bug report #930563,
regarding Can not start freecad
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
930563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930563
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: freecad
Version: 0.18~pre1+dfsg1-5
Severity: grave


I try to start the FreeCAD after I install, but it is not be started, and I get 
the message "freecad: symbol lookup error: 
/lib/x86_64-linux-gnu/libOpenGL.so.0: undefined symbol: _glapi_tls_Current".

My computer is Thinkpad P1.



Best regards,
Gulfstream



-- System Information:
Debian Release: 10.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), 
LANGUAGE=zh_CN.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages freecad depends on:
ii  freecad-python2  0.18~pre1+dfsg1-5

Versions of packages freecad recommends:
ii  calculix-ccx  2.11-1+b3
ii  graphviz      2.40.1-6

Versions of packages freecad suggests:
pn  freecad-doc     <none>
pn  povray          <none>
pn  python-collada  <none>

-- no debconf information

--- End Message ---
--- Begin Message ---
No reply from bug reporter and it seems that the nvidia driver installed from
nvidia directly was causing this [1]. Therefore closing.

[1]https://wiki.debian.org/DontBreakDebian#Don.27t_use_GPU_manufacturer_install_scripts

--- End Message ---
-- 
debian-science-maintainers mailing list
debian-science-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers

Reply via email to