On 2/21/10, Xavier Chantry wrote:
> On Sun, Feb 21, 2010 at 9:59 PM, Javier Vasquez
> wrote:
>>
>> Bad thing it's still kind of unknown how to solve or to work around
>> it. Well, the work around is not to use xscreensaver, :-(. I don't
>> remember if I can get xlockmore to lock when there's n
On Sun, Feb 21, 2010 at 9:59 PM, Javier Vasquez wrote:
>
> Bad thing it's still kind of unknown how to solve or to work around
> it. Well, the work around is not to use xscreensaver, :-(. I don't
> remember if I can get xlockmore to lock when there's no activity...
> Well, I'll have to look int
On 1/25/10, Damjan Georgievski wrote:
>> Hmm, let me rephrase my initial statement. The only initial symptom
>> was xscreensaver. It was running when all of sudden the FS got
>> corrupted and I couldn't loging, not from xscreensaver, not from
>> console, etc.
>>
>> At this point I have a pretty
> Hmm, let me rephrase my initial statement. The only initial symptom
> was xscreensaver. It was running when all of sudden the FS got
> corrupted and I couldn't loging, not from xscreensaver, not from
> console, etc.
>
> At this point I have a pretty stable system. Nothing fails. Only
> when I
On 1/25/10, Thayer Williams wrote:
> On Sun, Jan 24, 2010 at 7:14 PM, Javier Vasquez
> wrote:
>> Bad thing that xscreensaver corrupted / so that it couldn't be
>> unlocked, and under console there was no way to loging, some misplaced
>> inodes or something...
>>
>> Hard reboot was required, and
On 1/25/10, Xavier Chantry wrote:
> On Mon, Jan 25, 2010 at 4:36 PM, Thayer Williams wrote:
>> On Sun, Jan 24, 2010 at 7:14 PM, Javier Vasquez
>> wrote:
>>> Bad thing that xscreensaver corrupted / so that it couldn't be
>>> unlocked, and under console there was no way to loging, some misplaced
On Mon, Jan 25, 2010 at 4:36 PM, Thayer Williams wrote:
> On Sun, Jan 24, 2010 at 7:14 PM, Javier Vasquez
> wrote:
>> Bad thing that xscreensaver corrupted / so that it couldn't be
>> unlocked, and under console there was no way to loging, some misplaced
>> inodes or something...
>>
>> Hard reb
On Sun, Jan 24, 2010 at 7:14 PM, Javier Vasquez wrote:
> Bad thing that xscreensaver corrupted / so that it couldn't be
> unlocked, and under console there was no way to loging, some misplaced
> inodes or something...
>
> Hard reboot was required, and then at first /tmp was so corrupted that
> it
Hi all,
I have 4 boxes, all with the same partitioning scheme and using ext4
for all of them. This weird thing has only showed up in one of them.
Some time back while playing some video and with xscreensaver active,
the timeout for xscreensaver expired and then password was required...
Bad thin
9 matches
Mail list logo
