On Sunday 16 Feb 2014 00:25:55 Alan McKinnon wrote:
On 16/02/2014 02:20, Will Hopper wrote:
This is not at all unlikely - the virtual machine is running in a windows
host that was created by restoring from backups after a drive failed.
Also, the 'new' disk it was restored to is not really a
allright, I will try that, thanks everyone for the advice!
On Sun, Feb 16, 2014 at 3:39 AM, Mick michaelkintz...@gmail.com wrote:
On Sunday 16 Feb 2014 00:25:55 Alan McKinnon wrote:
On 16/02/2014 02:20, Will Hopper wrote:
This is not at all unlikely - the virtual machine is running in a
On Sun, 16 Feb 2014 04:21:29 -0500 Will Hopper wjhopper...@gmail.com said:
allright, I will try that, thanks everyone for the advice!
that should only help if its a REAL drive that has the errors. if its the vm
disk image that already copied errors off the real drive.. it won't help i
think. :)
On Sunday 16 Feb 2014 11:50:16 Carsten Haitzler wrote:
On Sun, 16 Feb 2014 04:21:29 -0500 Will Hopper wjhopper...@gmail.com said:
allright, I will try that, thanks everyone for the advice!
that should only help if its a REAL drive that has the errors. if its the
vm disk image that already
What fs type is /usr/include/ on?
Most times those turn out to be filesystem corruption of one kind
or another. What is really means is that the kernel can't make sense out
of what it finds in the dinode; there can be valid reasons for that but
fs corruption is the common one.
On
On Sat, 15 Feb 2014 22:34:11 +0200
Alan McKinnon alan.mckin...@gmail.com wrote:
What fs type is /usr/include/ on?
Most times those turn out to be filesystem corruption of one kind
or another. What is really means is that the kernel can't make sense
out of what it finds in the dinode; there
This is not at all unlikely - the virtual machine is running in a windows
host that was created by restoring from backups after a drive failed. Also,
the 'new' disk it was restored to is not really a new disk at all.
I am not really knowledgeable about virtual machines at all - would
deleting
On 16/02/2014 02:20, Will Hopper wrote:
This is not at all unlikely - the virtual machine is running in a windows
host that was created by restoring from backups after a drive failed. Also,
the 'new' disk it was restored to is not really a new disk at all.
I am not really knowledgeable
Just ran into this same issue, with a new compile of efl 18.8.5, elementary
1.8.4, and enlightenment 1.8.3 on debian testing virtual machine. Did you
ever find any way to fix this issue?
strangely, xsession-errors has none of this, i could only find the ESTART
messages by running startx and
Have you tried moving your e directory out of the way and then starting
enlightenment. I ran into similar issues with an earlier
version of e18 and this was the only way for me to fix it.
Kevin
On 02/14/2014 10:36 AM, Will Hopper wrote:
Just ran into this same issue, with a new compile of efl
Fri, 14 Feb 2014 11:36:39 -0500 -n
Will Hopper wjhopper...@gmail.com írta:
Just ran into this same issue, with a new compile of efl 18.8.5,
elementary 1.8.4, and enlightenment 1.8.3 on debian testing virtual
machine. Did you ever find any way to fix this issue?
Unfortunately, this issue not
When I log in to e18, I get a blank screen with a simple mouse cursor.
And nothing happens.
In the .xsession-errors file I found this, repeatedly:
ESTART: 0.0 [0.0] - Begin Startup
ESTART: 0.9 [0.9] - Signal Trap
ESTART: 0.00013 [0.4] - Signal Trap Done
ESTART: 0.03026
12 matches
Mail list logo
