That sounds really weird. Having to launch from GUI to start a working image is not very convenient. Let us know if you have any other findings. Cheers, Hernán 2014/1/13 Martin McClure <martin@hand2mouse.com>
On 01/12/2014 05:22 PM, Igor Stasenko wrote:
i remember there was similar problem last year with ubuntu unity desktop: you starting image from command line - nothing respond, but if you start from desktop, everything works well. which then later was cured without any changes from our side, by some ubuntu update
Thanks, Igor!
It would never occur to me to launch from GUI rather than command line.
...OK, this is *completely* weird. Yes, launched from desktop (KDE 4.11 Dolphin) it works. What's more, it *also* works from shells launched from a Konsole instance launched yesterday. But it still fails to work for shells launched from a Konsole instance launched shortly after reboot on Friday night. I haven't yet been able to find any significant difference between those shells. Their environments differ in a few variables, but manually setting those in a shell where Pharo works to the values from a shell where Pharo doesn't work -- Pharo still works. Examining /proc from a working Pharo and a non-working Pharo has not turned up anything.
I'll chase this a bit more later, but at least now I *can* run Pharo. For the moment. Who knows what will happen next time I need to reboot?
Thanks again,
-Martin