Vladimir Zhbanov schreef op za 22-08-2015 om 16:13 [+0000]:
> On Sat, Aug 22, 2015 at 12:11:18PM -0000, Richard Rasker wrote:
> > Vladimir Zhbanov schreef op za 22-08-2015 om 11:19 [+0000]:
> ...
> > > Could you pull the latest git sources and try once again?
> > > I've just pushed a couple of patches. Perhaps, something will change.
> >
> > Nope, compiling works OK, but the compiled gschem target still crashes
> > with the exact same error message, albeit with a different number
> > (215b400 instead of 1424400) -- but I guess that this is a memory
> > location or some other less relevant identifier.
>
> Try to uninstall the geda packages you have installed. You'll be able
> to install them again any time you want using your package manager after
> doing 'make uninstall' in the source repository. I've just tried to
> install the Debian geda version and got the same result you have after
> doing 'gschem/src/gschem'.
>
> I think the problem could be in the way Debian/Ubuntu places its rc
> files and/or the place where gschem searches for them. Probably some
> setting of the environment variable GEDADATA could help. I didn't try
> setting it though.
>
> In your case, you could also try to configure with another prefix, say
> './configure --prefix=/tmp/gEDA' and run /tmp/gEDA/bin/gschem. This
> should work.
Ah, yes, finally, gschem starts as expected, and yes, now I have the V A
and V S key bindings to toggle visibility of the side bar and the status
bar respectively.
However, nothing has changed yet with respect to the original bug (the
freeze/redraw problem), but now I can at least confirm that hiding
either the side bar or the status bar via the menu or the key bindings
temporarily solves the problem, almost in the same way as dragging it
out of view. The only difference is that with one of the two screen
items disabled, I can keep resizing the main window without problems
(just dragging it out of view isn't as effective, because it becomes
visible again as soon as I enlarge the main window). As soon as both
items are visible, the bug crops up again.
Just to make sure, I also disabled all personal settings by temporarily
renaming de .gEDA directory (which contains gschemrc among other
things), but that also doesn't make any difference.
So in summary: only when BOTH the side bar and the status window are
visible does the bug manifest, and then only when resizing the main
window. When either of the two screen elements is hidden in any way, or
when I do not resize the main window, there is no problem.
Next, I also installed gEDA/gschem on a laptop that I just reinstalled
with Linux Mint 17.1, especially for this purpose. Here too, I can
replicate the bug, so it most definitely has nothing to do with the
machine I'm working on -- the laptop has a different hardware
architecture (32-bit instead of 64-bit) and a different graphics
controller (AMD/ATI instead of nVidia).
Then, as a last try, I changed my system locale from Dutch (NL) to US
English, and rebooted once again for good measure -- but to no avail.
So this is really, really weird. I appear to be the only one who can
very consistently replicate this bug, on either one of two completely
different machines that I tried, one of which with a pristine install,
and even with an English locale setting, at that. The only thing for me
left to try is to reinstall the laptop once again, but this time in
English from the onset, but that shouldn't make a difference, now should
it? As it's a rather old beastie, I wont resort to this last action
unless you guys think it's worth a try.
I'd also almost give you remote access to my laptop, if it weren't for
the fact that the bug explicitly has to do with local mouse and screen
actions, so remote access to an affected machine is probably no use.
Ah well, at least I can still use gschem, and all the time and effort
you put into it is hugely appreciated!
Vladimir Zhbanov schreef op za 22-08-2015 om 16:13 [+0000]: src/gschem' . bin/gschem. This
> On Sat, Aug 22, 2015 at 12:11:18PM -0000, Richard Rasker wrote:
> > Vladimir Zhbanov schreef op za 22-08-2015 om 11:19 [+0000]:
> ...
> > > Could you pull the latest git sources and try once again?
> > > I've just pushed a couple of patches. Perhaps, something will change.
> >
> > Nope, compiling works OK, but the compiled gschem target still crashes
> > with the exact same error message, albeit with a different number
> > (215b400 instead of 1424400) -- but I guess that this is a memory
> > location or some other less relevant identifier.
>
> Try to uninstall the geda packages you have installed. You'll be able
> to install them again any time you want using your package manager after
> doing 'make uninstall' in the source repository. I've just tried to
> install the Debian geda version and got the same result you have after
> doing 'gschem/
>
> I think the problem could be in the way Debian/Ubuntu places its rc
> files and/or the place where gschem searches for them. Probably some
> setting of the environment variable GEDADATA could help. I didn't try
> setting it though.
>
> In your case, you could also try to configure with another prefix, say
> './configure --prefix=/tmp/gEDA' and run /tmp/gEDA/
> should work.
Ah, yes, finally, gschem starts as expected, and yes, now I have the V A
and V S key bindings to toggle visibility of the side bar and the status
bar respectively.
However, nothing has changed yet with respect to the original bug (the
freeze/redraw problem), but now I can at least confirm that hiding
either the side bar or the status bar via the menu or the key bindings
temporarily solves the problem, almost in the same way as dragging it
out of view. The only difference is that with one of the two screen
items disabled, I can keep resizing the main window without problems
(just dragging it out of view isn't as effective, because it becomes
visible again as soon as I enlarge the main window). As soon as both
items are visible, the bug crops up again.
Just to make sure, I also disabled all personal settings by temporarily
renaming de .gEDA directory (which contains gschemrc among other
things), but that also doesn't make any difference.
So in summary: only when BOTH the side bar and the status window are
visible does the bug manifest, and then only when resizing the main
window. When either of the two screen elements is hidden in any way, or
when I do not resize the main window, there is no problem.
Next, I also installed gEDA/gschem on a laptop that I just reinstalled
with Linux Mint 17.1, especially for this purpose. Here too, I can
replicate the bug, so it most definitely has nothing to do with the
machine I'm working on -- the laptop has a different hardware
architecture (32-bit instead of 64-bit) and a different graphics
controller (AMD/ATI instead of nVidia).
Then, as a last try, I changed my system locale from Dutch (NL) to US
English, and rebooted once again for good measure -- but to no avail.
So this is really, really weird. I appear to be the only one who can
very consistently replicate this bug, on either one of two completely
different machines that I tried, one of which with a pristine install,
and even with an English locale setting, at that. The only thing for me
left to try is to reinstall the laptop once again, but this time in
English from the onset, but that shouldn't make a difference, now should
it? As it's a rather old beastie, I wont resort to this last action
unless you guys think it's worth a try.
I'd also almost give you remote access to my laptop, if it weren't for
the fact that the bug explicitly has to do with local mouse and screen
actions, so remote access to an affected machine is probably no use.
Ah well, at least I can still use gschem, and all the time and effort
you put into it is hugely appreciated!
Best regards,
Richard Rasker