6:54 a.m.
My laptop has Intel graphics. I have never been able to use Desktop Effects,
and have worked, since I got it a few months ago, in KDE Failsafe mode. After
updating this morning I decided to give it another try.
In the past I found that I could work for a minute or two, then I would be
dropped to the Login screen, so it must be an X failure, I guess. Today,
though, I went to SystemSettings to enable a few choice effects - none of the
eye-candy stuff, but dimming inactive windows and setting alt-tab to cover
switch. I completely lost keyboard input, although the mouse continued to
work. Gkrellm showed no activity whatsoever, although I suspect that just
means that it had lost connectivity, since mouse movement on the screen must
mean that it's not totally dead.
I know that .xsession-errors is where I should be looking, but I don't really
know where to start, so I've posted it at http://pastebin.ca/1897817. Could
someone please have a look and see if there are any suggestions for solving
the problem. (I have been working for more than 30 minutes now, without a
problem, so I'm hopeful that there is some improvement in the situation since
the update.)
Anne
--
KDE Community Working Group
New to KDE Software? - get help from http://userbase.kde.org
3:09 p.m.
On Saturday 10 July 2010 14:54:56 Anne Wilson wrote:
My laptop has Intel graphics. I have never been able to use Desktop
Effects, and have worked, since I got it a few months ago, in KDE Failsafe
mode. After updating this morning I decided to give it another try.
In the past I found that I could work for a minute or two, then I would be
dropped to the Login screen, so it must be an X failure, I guess. Today,
though, I went to SystemSettings to enable a few choice effects - none of
the eye-candy stuff, but dimming inactive windows and setting alt-tab to
cover switch. I completely lost keyboard input, although the mouse
continued to work. Gkrellm showed no activity whatsoever, although I
suspect that just means that it had lost connectivity, since mouse
movement on the screen must mean that it's not totally dead.
I know that .xsession-errors is where I should be looking, but I don't
really know where to start, so I've posted it at
http://pastebin.ca/1897817. Could someone please have a look and see if
there are any suggestions for solving the problem. (I have been working
for more than 30 minutes now, without a problem, so I'm hopeful that there
is some improvement in the situation since the update.)
Anne
Hi Anne
I will try to help. Dunno if I can be of much help, but maybe if we knock our
heads together we can figure this out.
First thing thing... The log that you've posted doesn't seem to indicate where
the crash is and it doesn't seem to be the Xorg log which can be found at
/etc/log/Xorg.0.log
Next time you get a crash please post what is contained there.
The other thing I gotta ask, is what happens if you start with a completely
clean configuration. I guess you can either do that with a completely new user
for the computer or backup .kde and start again.
Eli
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
1:56 a.m.
On Saturday 10 July 2010 21:09:52 Eli Wapniarski wrote:
Hi Anne
I will try to help. Dunno if I can be of much help, but maybe if we knock
our heads together we can figure this out.
Thanks.
First thing thing... The log that you've posted doesn't seem
to indicate
where the crash is and it doesn't seem to be the Xorg log which can be
found at
/etc/log/Xorg.0.log
It's not, it's .xsession-errors. I did look through Xorg.0.log, but it
seemed to be mostly the happenings at bootup - maybe I missed something so
I'll post that, next time it happens. Interestingly, though, I have been
running for 19 hours now without a crash, so maybe the new driver that came
with the update a couple of days ago has actually cured the problem.
Next time you get a crash please post what is contained there.
The other thing I gotta ask, is what happens if you start with a
completely clean configuration. I guess you can either do that with a
completely new user for the computer or backup .kde and start again.
OK - something to bear in mind if/when it happens again.
Thanks for the offer of help.
Anne
--
KDE Community Working Group
New to KDE Software? - get help from http://userbase.kde.org
12:56 p.m.
On Sunday 11 July 2010 18:25:44 Eli Wapniarski wrote:
On Sunday 11 July 2010 09:56:06 Anne Wilson wrote:
> Thanks for the offer of help.
Your welcome
Eli
Hi, Eli. Here you are: http://pastebin.ca/1899947
I was working on several things, so had both Konqueror and Chromium open with
a number of tabs each. Without warning X crashed. The mouse could move the
cursor - white arrow on black screen, and the keyboard appeared to be read -
Ctrl-alt-F2 was recognised, and so, when I tried it eventually, was Ctrl-alt-
Del. Ctrl-alt-backspace did nothing, though. I tried to use a VT to restart
plasma, but I don't think it's plasma that crashed, I think it was X itself.
Hope you have some ideas :-)
Anne
--
KDE Community Working Group
New to KDE Software? - get help from http://userbase.kde.org
3:18 p.m.
On Tuesday 13 July 2010 20:56:34 Anne Wilson wrote:
On Sunday 11 July 2010 18:25:44 Eli Wapniarski wrote:
> On Sunday 11 July 2010 09:56:06 Anne Wilson wrote:
> > Thanks for the offer of help.
>
> Your welcome
>
> Eli
Hi, Eli. Here you are: http://pastebin.ca/1899947
I was working on several things, so had both Konqueror and Chromium open
with a number of tabs each. Without warning X crashed. The mouse could
move the cursor - white arrow on black screen, and the keyboard appeared
to be read - Ctrl-alt-F2 was recognised, and so, when I tried it
eventually, was Ctrl-alt- Del. Ctrl-alt-backspace did nothing, though. I
tried to use a VT to restart plasma, but I don't think it's plasma that
crashed, I think it was X itself.
Hope you have some ideas :-)
Anne
Hi Anne
What I can see from the logs that you presented was that all the way down
Xwindows seemed to be healthy.
You say that you were able to switch over to a console. The next time it
happens please post the output of
ps aux
One possibility that comes to mind is that it is very possible that the
computer overheated.
Konqueror / Chromium) hmmm.... Questions (probably silly). Are you using
adobe's flash plugin? Is it the 64 bit version or the 32 bit version? If the 32
bit version are you using it in a 64 bit environment? If you are using flash do
you experience the same symptoms if you were to use firefox or google-chrome?
Eli
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
5:01 a.m.
On Tuesday 13 July 2010 21:18:03 Eli Wapniarski wrote:
On Tuesday 13 July 2010 20:56:34 Anne Wilson wrote:
> On Sunday 11 July 2010 18:25:44 Eli Wapniarski wrote:
> > On Sunday 11 July 2010 09:56:06 Anne Wilson wrote:
> > > Thanks for the offer of help.
> >
> > Your welcome
> >
> > Eli
>
> Hi, Eli. Here you are: http://pastebin.ca/1899947
>
> I was working on several things, so had both Konqueror and Chromium open
> with a number of tabs each. Without warning X crashed. The mouse could
> move the cursor - white arrow on black screen, and the keyboard appeared
> to be read - Ctrl-alt-F2 was recognised, and so, when I tried it
> eventually, was Ctrl-alt- Del. Ctrl-alt-backspace did nothing, though.
> I tried to use a VT to restart plasma, but I don't think it's plasma
> that crashed, I think it was X itself.
>
> Hope you have some ideas :-)
>
> Anne
Hi Anne
What I can see from the logs that you presented was that all the way down
Xwindows seemed to be healthy.
Well that rules out one thing. FWIW, Rex also said on IRC that if I could
move the cursor around with the mouse, like that, X hadn't crashed, so we are
looking for something else.
You say that you were able to switch over to a console. The next time
it
happens please post the output of
ps aux
I'll do that.
One possibility that comes to mind is that it is very possible that
the
computer overheated.
I don't think so. I run gkrellm, and this laptop reports about 10' cooler
constantly than my older laptop did when idling. It never seems to raise more
than a few degrees.
Konqueror / Chromium) hmmm....
I have had some problems with Konqueror in the past, which is why I use
Chromium quite a lot. It just seems more stable. I wouldn't be surprised to
find that Konqueror is implicated.
Questions (probably silly). Are you using
adobe's flash plugin? Is it the 64 bit version or the 32 bit version?
I have flash-plugin-10.1.53.64-release.i386
If
the 32 bit version are you using it in a 64 bit environment?
No.
If you are
using flash do you experience the same symptoms if you were to use firefox
or google-chrome?
Flash videos run perfectly in FF and Chromium, but not at all in Konqueror. I
had clicked on a video link, forgetfully, earlier, so Konqueror would have
tried to run it and failed. It's possible that there is a connection there.
At Rex's suggestion, I'm trying xorg-x11-drv-intel-2.12.0 from koji. In this
morning's logwatch I see
WARNING: Kernel Errors Present
ACPI Error (psargs-0359): [ ...: 8 Time(s)
ACPI Error (psparse-0537): ...: 8 Time(s)
[<f81f1041>] ? i915_error_object_create+0x ...: 5 Time(s)
[<f81f1083>] i915_error_object_create+0x ...: 11 Time(s)
[<f81f13f2>] i915_handle_error+0x314/0x813 [i91 ...: 4 Time(s)
[<f81f140e>] i915_handle_error+0x330/0x813 [i91 ...: 7 Time(s)
render error detected, EIR: 0 ...: 157 Time(s)
I don't think the ACPI errors have any connection, but the rest probably do.
I haven't yet trawled through logs to find out exactly when this happened, so
I don't know whether it is building up to the crash, or whether it concerns
the new driver. Later today I'll see if I can put a time on them.
One thing I have found in the logs - prior to installing this experimental
driver, the kdm.log showed
intel_bufmgr_gem.c:1069: Error setting domain 601: Input/output error
intel_bufmgr_gem.c:1069: Error setting domain 828: Input/output error
intel_bufmgr_gem.c:1069: Error setting domain 639: Input/output error
With the new driver that has disappeared, so that has to be a step in the
right direction :-)
'messages' is full of kernel errors, some of which are probably related. It's
probably too big for pastebin, but I could post it somewhere and send the link
to anyone wanting to read it.
Anne
--
KDE Community Working Group
New to KDE Software? - get help from http://userbase.kde.org
12:11 p.m.
On Wednesday 14 July 2010 13:01:19 Anne Wilson wrote:
On Tuesday 13 July 2010 21:18:03 Eli Wapniarski wrote:
> On Tuesday 13 July 2010 20:56:34 Anne Wilson wrote:
> > On Sunday 11 July 2010 18:25:44 Eli Wapniarski wrote:
> > > On Sunday 11 July 2010 09:56:06 Anne Wilson wrote:
> > > > Thanks for the offer of help.
> > >
> > > Your welcome
> > >
> > > Eli
> >
> > Hi, Eli. Here you are: http://pastebin.ca/1899947
> >
> > I was working on several things, so had both Konqueror and Chromium
> > open with a number of tabs each. Without warning X crashed. The
> > mouse could move the cursor - white arrow on black screen, and the
> > keyboard appeared to be read - Ctrl-alt-F2 was recognised, and so,
> > when I tried it eventually, was Ctrl-alt- Del. Ctrl-alt-backspace did
> > nothing, though. I tried to use a VT to restart plasma, but I don't
> > think it's plasma that crashed, I think it was X itself.
> >
> > Hope you have some ideas :-)
> >
> > Anne
>
> Hi Anne
>
> What I can see from the logs that you presented was that all the way down
> Xwindows seemed to be healthy.
Well that rules out one thing. FWIW, Rex also said on IRC that if I could
move the cursor around with the mouse, like that, X hadn't crashed, so we
are looking for something else.
> You say that you were able to switch over to a console. The next time it
> happens please post the output of
>
> ps aux
I'll do that.
> One possibility that comes to mind is that it is very possible that the
> computer overheated.
I don't think so. I run gkrellm, and this laptop reports about 10' cooler
constantly than my older laptop did when idling. It never seems to raise
more than a few degrees.
> Konqueror / Chromium) hmmm....
I have had some problems with Konqueror in the past, which is why I use
Chromium quite a lot. It just seems more stable. I wouldn't be surprised
to find that Konqueror is implicated.
> Questions (probably silly). Are you using
> adobe's flash plugin? Is it the 64 bit version or the 32 bit version?
I have flash-plugin-10.1.53.64-release.i386
> If
> the 32 bit version are you using it in a 64 bit environment?
No.
> If you are
> using flash do you experience the same symptoms if you were to use
> firefox or google-chrome?
Flash videos run perfectly in FF and Chromium, but not at all in Konqueror.
I had clicked on a video link, forgetfully, earlier, so Konqueror would
have tried to run it and failed. It's possible that there is a connection
there.
At Rex's suggestion, I'm trying xorg-x11-drv-intel-2.12.0 from koji. In
this morning's logwatch I see
WARNING: Kernel Errors Present
ACPI Error (psargs-0359): [ ...: 8 Time(s)
ACPI Error (psparse-0537): ...: 8 Time(s)
[<f81f1041>] ? i915_error_object_create+0x ...: 5 Time(s)
[<f81f1083>] i915_error_object_create+0x ...: 11 Time(s)
[<f81f13f2>] i915_handle_error+0x314/0x813 [i91 ...: 4 Time(s)
[<f81f140e>] i915_handle_error+0x330/0x813 [i91 ...: 7 Time(s)
render error detected, EIR: 0 ...: 157 Time(s)
I don't think the ACPI errors have any connection, but the rest probably
do. I haven't yet trawled through logs to find out exactly when this
happened, so I don't know whether it is building up to the crash, or
whether it concerns the new driver. Later today I'll see if I can put a
time on them.
One thing I have found in the logs - prior to installing this experimental
driver, the kdm.log showed
intel_bufmgr_gem.c:1069: Error setting domain 601: Input/output error
intel_bufmgr_gem.c:1069: Error setting domain 828: Input/output error
intel_bufmgr_gem.c:1069: Error setting domain 639: Input/output error
With the new driver that has disappeared, so that has to be a step in the
right direction :-)
'messages' is full of kernel errors, some of which are probably related.
It's probably too big for pastebin, but I could post it somewhere and send
the link to anyone wanting to read it.
Anne
Good luck with the new driver
Eli
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
6:05 a.m.
On Tuesday 13 July 2010 21:18:03 Eli Wapniarski wrote:
You say that you were able to switch over to a console. The next time
it
happens please post the output of
ps aux
Ouput attached.
Anne
--
KDE Community Working Group
New to KDE Software? - get help from http://userbase.kde.org
12:06 p.m.
On Tuesday 20 July 2010 14:05:33 Anne Wilson wrote:
anne 29776 0.1 4.2 179956 164764 ? Sl Jul17 7:06
/usr/bin/virtuoso-t +foreground +configfile /tmp/virtuoso_n29770.ini +wait
Hi Anne
The only thing that I see that maybe (and that's a very iffy maybe) you've got
a buggy plasmoid running. Its maybe, because virtuoso seems to be the only
application utilizing any CPU time at all. But, like I said, its very iffy
because it wasn't very much CPU.
Other than that, I would suggest running with a brand new user or make a
complete backup of your home folder, and start with an absolutely clean
configuration and see if the problem reappears.
I've had some difficulty with plasma during the transisiton from 4.4 to 4.5
probably due to the Beta nature of 4.5 But that was overcome. Part of the
problem was that when I started kde on my dual screen one of my screens was
completely black. However, I could move my mouse and regular applications
would appear on the "black" screen. I did not attribute that to a bug, but
rather corruption due to a unclean shutdown. Now I understand that its not
exactly the same issue as you've been having, but it does sound similar.
Eli
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
12:33 p.m.
On Tuesday 20 July 2010 18:06:05 Eli Wapniarski wrote:
On Tuesday 20 July 2010 14:05:33 Anne Wilson wrote:
> anne 29776 0.1 4.2 179956 164764 ? Sl Jul17 7:06
> /usr/bin/virtuoso-t +foreground +configfile /tmp/virtuoso_n29770.ini
> +wait
Hi Anne
The only thing that I see that maybe (and that's a very iffy maybe) you've
got a buggy plasmoid running. Its maybe, because virtuoso seems to be the
only application utilizing any CPU time at all. But, like I said, its very
iffy because it wasn't very much CPU.
Other than that, I would suggest running with a brand new user or make a
complete backup of your home folder, and start with an absolutely clean
configuration and see if the problem reappears.
I've had some difficulty with plasma during the transisiton from 4.4 to 4.5
probably due to the Beta nature of 4.5 But that was overcome. Part of the
problem was that when I started kde on my dual screen one of my screens was
completely black. However, I could move my mouse and regular applications
would appear on the "black" screen. I did not attribute that to a bug, but
rather corruption due to a unclean shutdown. Now I understand that its not
exactly the same issue as you've been having, but it does sound similar.
Well the circumstances are different, but it does indeed sound very similar.
I have a clear white arrow that moves freely on a black screen. The second
terminal tells me that X is running, which fits with what Rex had said. A
Plasma failure usually leaves applications running and visible, but nothing is
visible. It's a bit of a mystery. Happily it's not too frequent. I'll just
keep experimenting whenever I have some time. Thanks for trying to help.
Anne
--
KDE Community Working Group
New to KDE Software? - get help from http://userbase.kde.org
12:11 a.m.
On Tuesday 20 July 2010 20:33:25 Anne Wilson wrote:
Well the circumstances are different, but it does indeed sound very
similar. I have a clear white arrow that moves freely on a black screen.
Like I said.... The way I fixed it was to start my .kde profile from scratch.
One other thing.... I can't remember what the name of the folder was, but I
had a funny named folder called either .kde(somesuch) or kde(somesuch). I
really can't remember what it was called or where exactly its located.... What
you can do.... temporarily. Is move all the plasma config files out of the way
temproarily and see if that helps. I'm betting that it does.
Eli
The second terminal tells me that X is running, which fits with what
Rex
had said. A Plasma failure usually leaves applications running and
visible, but nothing is visible. It's a bit of a mystery. Happily it's
not too frequent. I'll just keep experimenting whenever I have some time.
Thanks for trying to help.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
3:46 a.m.
On Wednesday 21 July 2010 06:11:39 Eli Wapniarski wrote:
Like I said.... The way I fixed it was to start my .kde profile from
scratch. One other thing.... I can't remember what the name of the folder
was, but I had a funny named folder called either .kde(somesuch) or
kde(somesuch). I really can't remember what it was called or where exactly
its located.... What you can do.... temporarily. Is move all the plasma
config files out of the way temproarily and see if that helps. I'm betting
that it does.
OK - probably worth a try. First, though I've removed the two weather widgets
I had - one of them was installed after I started having the problem, so it's
probably not that, but it was worth a try. I'll leave it alone now and see
whether it happens again. If it does I'll re-set plasma, as you suggest.
Anne
--
KDE Community Working Group
New to KDE Software? - get help from http://userbase.kde.org
5030
days inactive
5041
days old
12 comments
2 participants
participants (2)
-
Anne Wilson -
Eli Wapniarski