I've created a bug: https://bugs.launchpad.net/kicad/+bug/1784697

To answer your question, I don't close the blank window.  KiCad crashes with a 
SIGSEGV in gdk_window_set_geometry_hints before I can do anything.  Thus, this 
is a fatal error on my machine.

Guess it's time to look for a new video card.  But as you say, other folks will 
probably run into this problem too, so it would be good to resolve the issue.

        Steve

On 07/31/2018 01:03 PM, Seth Hillbrand wrote:
> I think we should open a bug for this on Launchpad to track the details as 
> this might bite a few other users of legacy NVidia or possibly the fedora 
> package.  Would you be able to transfer the bug report there?
> 
> To track this further, can you say what happens when you close the blank 
> window?  Does KiCad continue to function or does it close?
> 
> -S
> 
> Am Di., 31. Juli 2018 um 09:51 Uhr schrieb Steven A. Falco 
> <[email protected] <mailto:[email protected]>>:
> 
>     A little more info.  My KiCad build works fine on my laptop, which has 
> both an Intel and Nvidia graphics chip on its motherboard.  The Nvidia 
> framebuffer device is using the nouveau driver.
> 
>     In contrast, my desktop machine has to use an official driver supplied by 
> Nvidia, rather than nouveau, because nouveau doesn't work well with the 
> GeForce 210 video card in my desktop machine.
> 
>     It may be that there is an incompatibility between KiCad and the Nvidia 
> driver, at least as it pertains to my hardware.
> 
>     One last thing - KiCad 4.0.7 works fine on my desktop, with the Nvidia 
> driver.
> 
>     I'll keep experimenting, but I'm not sure what to try next.  So far, in 
> all other respects, I don't see a problem with the Nvidia driver.
> 
>             Steve
> 
>     On 07/30/2018 10:08 PM, Steven A. Falco wrote:
>     > Thanks for looking at it.  Regarding your first question, I've placed a 
> copy of my build log in the same dropbox directory, named "build.log".
>     >
>     > Regarding your second question, the gdb crash dump from the Copr 
> nightly build looks about the same as the one from my local build.  Both 
> builds fail with the same error.  I've placed both gdb logs in the dropbox 
> directory, named "err-mine.log" and "err-nightly.log".
>     >
>     > The cmake command used for my build is:
>     >
>     > cmake \
>     >     -DKICAD_SCRIPTING=OFF \
>     >     -DKICAD_SCRIPTING_MODULES=OFF \
>     >     -DKICAD_SCRIPTING_WXPYTHON=OFF \
>     >     -DKICAD_SPICE=OFF \
>     >     -DKICAD_VERSION_EXTRA=%{release} \
>     >     -DwxWidgets_CONFIG_EXECUTABLE=%{_bindir}/%{wx_config} \
>     >     .
>     >
>     > The type of build should default to "Release", according to 
> CMakeLists.txt.  The Fedora build tools add some options to the above 
> command.  From the build log, the command expands to:
>     >
>     > /usr/bin/cmake -DCMAKE_C_FLAGS_RELEASE:STRING=-DNDEBUG 
> -DCMAKE_CXX_FLAGS_RELEASE:STRING=-DNDEBUG 
> -DCMAKE_Fortran_FLAGS_RELEASE:STRING=-DNDEBUG 
> -DCMAKE_VERBOSE_MAKEFILE:BOOL=ON -DCMAKE_INSTALL_PREFIX:PATH=/usr 
> -DINCLUDE_INSTALL_DIR:PATH=/usr/include -DLIB_INSTALL_DIR:PATH=/usr/lib64 
> -DSYSCONF_INSTALL_DIR:PATH=/etc -DSHARE_INSTALL_PREFIX:PATH=/usr/share 
> -DLIB_SUFFIX=64 -DBUILD_SHARED_LIBS:BOOL=ON -DKICAD_SCRIPTING=OFF 
> -DKICAD_SCRIPTING_MODULES=OFF -DKICAD_SCRIPTING_WXPYTHON=OFF 
> -DKICAD_SPICE=OFF -DKICAD_VERSION_EXTRA=2.fc28 
> -DwxWidgets_CONFIG_EXECUTABLE=/usr/bin/wx-config .
>     >
>     > wx-config reports its version as:
>     >
>     > saf$ /usr/bin/wx-config --version-full
>     > 3.0.4.0
>     >
>     > Please let me know any other info you need to help track this down.
>     >
>     >       Steve
>     >
>     > On 07/30/2018 05:08 PM, Seth Hillbrand wrote:
>     >> Hi Steve-
>     >>
>     >> The assert is not triggering for me using Debian.  However, I note 
> that this is a wxWidgets assertion, which should be disabled for release 
> builds.  Since you did the packaging for Fedora, do you have a build log?  
> Alternatively, do you see this assertion when running a local build?
>     >>
>     >> -S
>     >>
>     >> Am Mo., 30. Juli 2018 um 12:37 Uhr schrieb Steven A. Falco 
> <[email protected] <mailto:[email protected]> 
> <mailto:[email protected] <mailto:[email protected]>>>:
>     >>
>     >>     I am using Fedora 28, and have just noticed a strange crash.  This 
> happens with 5.0.0 and also with the latest nightly (r13432-e750382e).
>     >>
>     >>     I've got to assume I'm doing something wrong, but I am baffled, so 
> I want to see what folks think.
>     >>
>     >>     I've attached a backtrace.  The way I cause this crash is to 
> highlight a part in the design here:
>     >>
>     >>     
> https://www.dropbox.com/sh/46lxxedoalq0sdm/AABTNAmVP7wKjbv3_4hBcdcoa?dl=0
>     >>
>     >>     I've attached several screenshots for reference.
>     >>
>     >>     In "highlighted.png" you can see the part I've selected - an Atmel 
> micro.  I type "E" to get the properties, and I wind up with a blank dialog 
> as shown in "blank_alert.png".  It is at that point that I did the backtrace.
>     >>
>     >>     This is with the fallback version of the modern toolset.  If I try 
> to switch to the accelerated toolset, I get an error that I need OpenGL 2.1 
> or higher.  However, I think I have OpenGL 3.3.0:
>     >>
>     >>     saf# glxinfo | grep "OpenGL version"
>     >>     OpenGL version string: 3.3.0 NVIDIA 340.107
>     >>
>     >>     Here is the version info from my build of 5.0.0:
>     >>
>     >>     Application: kicad
>     >>     Version: 5.0.0-2.fc28, release build
>     >>     Libraries:
>     >>         wxWidgets 3.0.4
>     >>         libcurl/7.59.0 OpenSSL/1.1.0h zlib/1.2.11 libidn2/2.0.5 
> libpsl/0.20.2 (+libidn2/2.0.4) libssh/0.7.5/openssl/zlib nghttp2/1.32.0
>     >>     Platform: Linux 4.17.9-200.fc28.x86_64 x86_64, 64 bit, Little 
> endian, wxGTK
>     >>     Build Info:
>     >>         wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) 
> GTK+ 2.24
>     >>         Boost: 1.66.0
>     >>         OpenCASCADE Community Edition: 6.9.1
>     >>         Curl: 7.59.0
>     >>         Compiler: GCC 8.1.1 with C++ ABI 1013
>     >>
>     >>     Build settings:
>     >>         USE_WX_GRAPHICS_CONTEXT=OFF
>     >>         USE_WX_OVERLAY=OFF
>     >>         KICAD_SCRIPTING=OFF
>     >>         KICAD_SCRIPTING_MODULES=OFF
>     >>         KICAD_SCRIPTING_WXPYTHON=OFF
>     >>         KICAD_SCRIPTING_ACTION_MENU=OFF
>     >>         BUILD_GITHUB_PLUGIN=ON
>     >>         KICAD_USE_OCE=ON
>     >>         KICAD_USE_OCC=OFF
>     >>         KICAD_SPICE=OFF
>     >>
>     >>     Please let me know what you think.  I'm mystified.
>     >>
>     >>             Steve
>     >>
>     >>     _______________________________________________
>     >>     Mailing list: https://launchpad.net/~kicad-developers 
> <https://launchpad.net/%7Ekicad-developers> 
> <https://launchpad.net/%7Ekicad-developers>
>     >>     Post to     : [email protected] 
> <mailto:[email protected]> 
> <mailto:[email protected] 
> <mailto:[email protected]>>
>     >>     Unsubscribe : https://launchpad.net/~kicad-developers 
> <https://launchpad.net/%7Ekicad-developers> 
> <https://launchpad.net/%7Ekicad-developers>
>     >>     More help   : https://help.launchpad.net/ListHelp
>     >>
>     >
>     >
> 


_______________________________________________
Mailing list: https://launchpad.net/~kicad-developers
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Reply via email to