> But tonight, I get a chance to install yet another machine with Mint 17.
And here are the results: I installed a completely different machine (an
old 64-bit AMD Athlon 3200+) with Mint 17.2 KDE, in the default language
(US English) -- and yes, after adding the mehanik gEDA ppa and
installing geda-gschem I found that gschem exhibited the same bugs once
again.
So it would appear that the problem lies in the combination of Linux
Mint KDE with gschem. From what I experience, anyone should be able to
reproduce the bug by installing Linux Mint KDE + geda-gschem on an
arbitrary machine in an arbitrary language.
Maybe installing Linux Mint with another desktop manager (DM) than KDE
may solve the problem, but installing the KDE version and then switching
to another DM doesn't work.
As soon as I have yet another machine at my disposal and some time to
try out a different DM as a 'pristine install', I will report back.
> But tonight, I get a chance to install yet another machine with Mint 17.
And here are the results: I installed a completely different machine (an
old 64-bit AMD Athlon 3200+) with Mint 17.2 KDE, in the default language
(US English) -- and yes, after adding the mehanik gEDA ppa and
installing geda-gschem I found that gschem exhibited the same bugs once
again.
So it would appear that the problem lies in the combination of Linux
Mint KDE with gschem. From what I experience, anyone should be able to
reproduce the bug by installing Linux Mint KDE + geda-gschem on an
arbitrary machine in an arbitrary language.
Maybe installing Linux Mint with another desktop manager (DM) than KDE
may solve the problem, but installing the KDE version and then switching
to another DM doesn't work.
As soon as I have yet another machine at my disposal and some time to
try out a different DM as a 'pristine install', I will report back.
Best regards,
Richard Rasker