Bug#948626: kicad: Closing pcbnew hangs main kicad process

2020-06-04 Thread Paul "LeoNerd" Evans
On Thu, 4 Jun 2020 16:45:45 +0100 "Paul \"LeoNerd\" Evans" wrote: > At this point now I'm a little stuck, because being unable to > associate footprints with components, I can't actually make any new > boards. With pcbnew crashing only on exit, at least I could edit and > save just fine within on

Bug#948626: kicad: Closing pcbnew hangs main kicad process

2020-06-04 Thread Paul "LeoNerd" Evans
On Sun, 26 Jan 2020 17:51:55 +0100 Carsten Schoenert wrote: > > Seems to be stored there: > >$ grep canvas_type .config/kicad/pcbnew > >canvas_type=1 > > > > (When switched on seems to be "=1", switched off to be "=2", > > but not completely sure about it.) > > And maybe which graphics

Bug#948626: kicad: Closing pcbnew hangs main kicad process

2020-01-26 Thread Carsten Schoenert
Hi, Am 25.01.20 um 17:25 schrieb Bernhard Übelacker: > I guess then I could not help any more. > Maybe the Maintainer have some other hints. currently I've no idea what's the culprint. I can't reproduce this behavior on none of my machines and these are 5-6 various types of hardware. > One thing

Bug#948626: kicad: Closing pcbnew hangs main kicad process

2020-01-25 Thread Bernhard Übelacker
Hello Paul, > That was my first thought; as explained in my initial bug report: >>> If run from the terminal there is no printed output of any kind. Sorry I missed that one. >> Otherwise maybe it is related to the used desktop environment, >> if xorg or wayland is in use > > I'm using xorg and

Bug#948626: kicad: Closing pcbnew hangs main kicad process

2020-01-20 Thread Paul "LeoNerd" Evans
On Mon, 13 Jan 2020 22:43:52 +0100 Bernhard Übelacker wrote: > Hello Paul, > in that case I guess kicad is really trying to leave > the process for some reason. > > That reason is maybe written to stdout. Therefore maybe you > can run kicad from a terminal and attach its output. > Probably that

Bug#948626: kicad: Closing pcbnew hangs main kicad process

2020-01-13 Thread Bernhard Übelacker
Hello Paul, in that case I guess kicad is really trying to leave the process for some reason. That reason is maybe written to stdout. Therefore maybe you can run kicad from a terminal and attach its output. Probably that could give any hints. Otherwise maybe it is related to the used desktop envi

Bug#948626: kicad: Closing pcbnew hangs main kicad process

2020-01-12 Thread Paul "LeoNerd" Evans
On Sat, 11 Jan 2020 14:26:12 +0100 Bernhard Übelacker wrote: > Could you recheck - could it be that this pid 309563 > was still running from a previous kicad session and > your hanging kicad was another, newer process? Definitely a new one. To retest: $ pgrep kicad [nothing] [run kicad,

Bug#948626: kicad: Closing pcbnew hangs main kicad process

2020-01-11 Thread Bernhard Übelacker
Hello Paul, I am not involved in packaging kicad or wxwidgets, just trying to collect some more information. Could you recheck - could it be that this pid 309563 was still running from a previous kicad session and your hanging kicad was another, newer process? Because, I guess, the __run_exit_han

Bug#948626: kicad: Closing pcbnew hangs main kicad process

2020-01-10 Thread Paul "LeoNerd" Evans
Package: kicad Version: 5.1.5+dfsg1-2 Severity: normal I can open, use and close eeschema just fine. I can open and use pcbnew just fine, but when I attempt to close it and return back to the main toplevel kicad window, the entire process hangs at 100% CPU usage, not drawing any windows (existing