KDE session hanging issues on Fedora 17
Nikhil bhalwankar
nikhilbhalwankar at yahoo.co.in
Wed Jul 25 05:26:44 BST 2012
Hi Duncan,
Thanks a lot for this information. I have switched off the desktop effects during startup. I have not faced the hanging issues in last 3 days.
Many Thanks,
Nikhil Bhalwankar
________________________________
From: "kde-request at mail.kde.org" <kde-request at mail.kde.org>
To: kde at mail.kde.org
Sent: Sunday, 22 July 2012 5:30 PM
Subject: kde Digest, Vol 112, Issue 17
Send kde mailing list submissions to
kde at mail.kde.org
To subscribe or unsubscribe via the World Wide Web, visit
https://mail.kde.org/mailman/listinfo/kde
or, via email, send a message with subject or body 'help' to
kde-request at mail.kde.org
You can reach the person managing the list at
kde-owner at mail.kde.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of kde digest..."
Today's Topics:
1. Re: Plasma "upside down" ... (Hans Muecke)
2. KDE session hanging issues on Fedora 17 (Nikhil bhalwankar)
3. Re: KDE session hanging issues on Fedora 17 (Duncan)
4. KDE lost of settings: "State" field corrupted in all rc files
(Maxime. Haselbauer)
----------------------------------------------------------------------
Message: 1
Date: Sat, 21 Jul 2012 09:48:13 -0500
From: Hans Muecke <kde at filderstadtweather.eu>
To: kde at mail.kde.org
Subject: Re: [kde] Plasma "upside down" ...
Message-ID: <500AC12D.7060608 at filderstadtweather.eu>
Content-Type: text/plain; charset=UTF-8
Am 18.07.2012 17:22, schrieb dE .:
> On 07/13/12 23:14, Hans Muecke wrote:
>> Howdy folks,
>>
>> Ran into a strange problem ...
>>
>> Kubuntu 12.04LTS/KDE4.8.4 ...
>>
>> For whatever reason my plasma desktop crashed yesterday. Couldn't get it
>> to come up again, so I deleted all the plasma files in the home
>> directory to start from scratch.
>> I must have done that in the "protected mode" unknowingly ... since
>> today - when trying to change one of the desktop effects - I was told
>> that I was running protected mode and should switch to the "normal"
>> plasma desktop.
>> Did as requested and ended up with an "upside down" desktop. Visually
>> everything is upside down, but buttons still seem to be where they are
>> supposed to be on the desktop (screenshots: http://goo.gl/N4tVF and
>> http://goo.gl/YjPtc ). Everything looks fine in protected mode ... minus
>> effects that is.
>>
>> Anyone have an idea what went wrong here and how to possibly correct it?
>
> As many people pointed out, this might be an X problem, so I'd suggest
> you post output of --
>
> DISPLAY=":0" xrandr
Here we go ...
Sa Jul 21, 09:46:38 hans at armstrong (~) > DISPLAY=":0" xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 320 x 240, current 1680 x 1050, maximum 1680 x 1050
default connected 1680x1050+0+0 0mm x 0mm
1680x1050 50.0* 90.0
1440x900 51.0 52.0
1400x1050 53.0 54.0
1360x768 55.0 56.0
1280x1024 57.0 58.0
1280x960 59.0
1280x720 60.0
1152x864 61.0 62.0 63.0 64.0
1024x768 65.0 66.0 67.0
960x600 68.0
960x540 69.0
840x525 70.0 71.0 72.0 73.0
832x624 74.0
800x600 75.0 76.0 77.0 78.0
720x450 79.0
700x525 80.0 81.0
680x384 82.0 83.0
640x480 84.0 85.0 86.0 87.0
512x384 88.0 89.0
400x300 91.0
320x240 92.0 93.0
Sa Jul 21, 09:46:43 hans at armstrong (~) >
--
Talk to you later ... Hans (48 to go)
2012/07/21 14:20
EDDS 211420Z 15003KT 9999 SCT020 BKN045CB 15/11 Q1021 RETS NOSIG
------------------------------
Message: 2
Date: Sun, 22 Jul 2012 03:43:11 +0800 (SGT)
From: Nikhil bhalwankar <nikhilbhalwankar at yahoo.co.in>
To: "kde at mail.kde.org" <kde at mail.kde.org>
Subject: [kde] KDE session hanging issues on Fedora 17
Message-ID:
<1342899791.63606.YahooMailNeo at web192505.mail.sg3.yahoo.com>
Content-Type: text/plain; charset="iso-8859-1"
Hi Team,
Greetings for the day !!
I have 64 Bit Fedora Core 17 installed on my DELL Inspiron 15R laptop. I am facing laptop freezing
issues?intermittently?when I login using during KDE session. Can anybody please help me on this?
Many Thanks,
Nikhil Bhalwankar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.kde.org/mailman/private/kde/attachments/20120722/91389183/attachment.html>
------------------------------
Message: 3
Date: Sat, 21 Jul 2012 21:08:48 +0000 (UTC)
From: Duncan <1i5t5.duncan at cox.net>
To: kde at postbox.kde.org
Subject: Re: [kde] KDE session hanging issues on Fedora 17
Message-ID: <pan.2012.07.21.21.08.48 at cox.net>
Content-Type: text/plain; charset=UTF-8
Nikhil bhalwankar posted on Sun, 22 Jul 2012 03:43:11 +0800 as excerpted:
> I have 64 Bit Fedora Core 17 installed on my DELL Inspiron 15R laptop. I
> am facing laptop freezing issues?intermittently?when I login using
> during KDE session. Can anybody please help me on this?
That's not a lot of information to go on... but a few questions:
When posting to a kde list, keep in mind that people run kde on all sorts
of distributions. I use gentoo, here. And just as you likely haven't
the foggiest idea what version of kde (or much else) I'm running when I
say gentoo (which doesn't really have distro releases as it's a rolling
distribution with weekly snapshot install media), I haven't much of an
idea what version of kde (or the kernel, or xorg-server, or...) you're
running when you say fedora core 17.
And on a kde list, the kde version especially useful. So... what kde
version? (If you can't get into the kde GUI to see, from the about
dialog, you can run say, "konsole --version" from a text-based login or
from gnome terminal or whatever. Or query your package manager for it.)
Meanwhile, as I said, that's not a lot to go on, but sometimes I've had
similar issues tied to faulty graphics (OpenGL). So a bit of information
about your graphics stack (hardware, proprietary or freedomware driver
with version, xorg-server version, mesa version, kernel version) might
help.
Do you have a desktop environment / window manager other than kde
installed? Do the freezes happen in it as well as in kde?
Assuming you can get into kde (you say the freezes are intermittent) for
long enough to check, in kde system settings under desktop effects, on
the general tab, are desktop effects enabled (enabled at startup, if your
kde version is new enough)? If you disable them, does the issue go
away? If disabling them entirely helps but you want effects, you can
also try leaving them enabled, but on the advanced tab, try xrender
instead of opengl compositing, or with opengl, uncheck the use opengl 2
shaders (again, I think that's a somewhat newer option) option.
When the freezes happen, is it still possible to switch to a text vt
using for instance ctrl-alt-f1 ? If not, assuming your distro enables
the magic-sysrequest keys, do they still work? (Sysrequest requires
holding the alt key and hitting printscreen/sysrequest, then hit the key
for your desired function.) Alt-srq-k should kill X (if you're not
frozen, be sure everything's saved before you do this). Actually, it
terminates any running program on that virtual terminal and returns you
to the text prompt, or for X, which runs in a VT of its own, to a blank
screen. (You could then use ctrl-alt-f1 to get to a text console and
login or shutdown from there.)
The alt-srq-key sequence, where key is in sequence r,e,i,s,u,b should
force a (partially clean) system reboot. R forces the keyboard out of
Raw "X" mode, E nicely asks running apps to tErminate, I will kIll any
that didn't terminate nicely... which should leave you at a text prompt
if the system's responding normally. S forces an emergency Sync of all
unwritten data back to disk...
You can actually use alt-srq-s to sync disks at any time. I use it
before I do something I know is risky and that might lockup the system,
to be sure everything to that point is saved.
Up to the S, you still have a running system, at a text prompt. Don't do
the last two unless you really do appear to be frozen.
U tells the kernel to remoUnt all mounted filesystems read-only, assuming
it isn't too scrambled to safely do so. If the kernel thinks it's
scrambled, it won't do anything, to avoid writing scrambled data to the
disk. In most cases, if the kernel isn't scrambled, you'll see the disk
activity light blink when you do the S and the U, as it syncs and safely
remounts read-only.
B tells the kernel to reboot, unconditionally, no syncing or saving data
(thus the S and U before it). Even if the kernel doesn't trust itself to
write to disk, if it's not entirely off in never-never-land, it'll
reboot. Thus, if alt-srq-b doesn't force a reboot (and you know magic-srq
is on for your kernel), the kernel is entirely gone.
In addition to forcing a reboot, this sequence also gives you a hint at
how bad the freeze was. If ctrl-alt-f1 lets you switch to VT1 without
issue, then it's likely that switching back to X (ctrl-alt-f7, normally,
since X is traditionally run on vt7) and waiting a bit will solve the
problem. If that does nothing but alt-srq-k kills X, the problem was
worse, but you still might be able to recover from a text console, and if
not, the reisub should at least save some of your data. Similarly if alt-
srq-r then lets you switch to a text VT (ctrl-alt-f1 or whatever).
If those minor things don't work, continue with the eisub sequence. If
the S and U give you disk activity, then userland was mostly/entirely
dead but the kernel was still alive and sane enough to at least save some
data.
If the S and U don't do anything but B does reboot, then the kernel was
alive but damaged enough that it didn't trust itself to write to disk any
longer. That's pretty bad.
If even alt-srq-b doesn't respond, your kernel's entirely dead, the
system fully frozen. If you're getting this sort of thing often, it's a
pretty sure indication of one of two things: Either X and your graphics
stack isn't working well on your hardware and is corrupting the kernel
(X, because of the privs it has to have to efficiently work with
graphics, can more easily than most apps corrupt the kernel), or your
hardware is likely defective. The latter can be due to bad memory, a
faulty CPU, a bad power supply (either from the wall or the computer
power supply unit that converts wall power for use by the computer), or a
bad motherboard chipset, among other things.
Of course if it's the hardware, other desktop environments will likely
show the problem as well, tho perhaps not the the same degree as some
work the hardware harder than others. As for the graphics stack, KDE
with OpenGL effects, especially with OpenGL shaders active, stresses that
more than most desktop environments, tho OpenGL based games use it even
more. That's why the questions about other DEs and whether turning off
effects helpe.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
------------------------------
Message: 4
Date: Sun, 22 Jul 2012 11:16:43 +0100
From: "Maxime. Haselbauer" <maxime.haselbauer at googlemail.com>
To: kde user <kde at mail.kde.org>
Subject: [kde] KDE lost of settings: "State" field corrupted in all rc
files
Message-ID:
<CAG6QrmU6VjofHUbD3jXTFiTje3rrBOS+h98cRW6DWXRkhU9ouA at mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Hi, Kubuntu 12.04 Kde 4.8.4 32 bit
Interesting thing this morning:
I power up my compute and almost every programm open as if KDE would be
freshly installed and it would be the first time I open the programm.
Needless to say, there was no update yesterday and ervything worked fine
when I shut down the computer yesterday evening
Very annoying because it means all your personal settings are lost....
in a short list
Background color of kde
Activities
Amarok collection
The podcast list
All id3 tags you have modified within amarok
Amarok internal database playlist
Amarok .xspf saved playlist
Kdevelop settinggs ....
All Akregator podcasts (although, there IS a feeds.opml file in
~/.kde/share/apps/akregator .... which DOES contain all RSS url I had ...)
Kmail settings (all your accounts)
etc...
So, it looks like it is not reading all rc configuration files (those
stored in ~/.kde/share/config) because all information it lacks are usually
given in those files
Hence I open a couple of rc files and I find an interesting thing:
In each of them, under the [Mainwindow] section there ist something like
State=AAAA/wAAAAD9AAAAAwAAAAAAAAE4AAAB1PwCAAAAAfsAAAAOAE0AbwBkAGUA[...] I
spare you the rest, this continue like that for long
I guess this is not the true state... but a corrupted field. Interesting is
that it looks corrupted for all rc files I have open so far, even those of
programm that I did not open for a while now.
Anyone know something about where it comes from and how to solve it ?
Regards
Maxime Haselbauer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.kde.org/mailman/private/kde/attachments/20120722/1708299d/attachment.html>
------------------------------
___________________________________________________
___________________________________________________
This message digest is from the kde mailing list.
Account management: https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.
End of kde Digest, Vol 112, Issue 17
************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde/attachments/20120725/e387dc7f/attachment.htm>
-------------- next part --------------
___________________________________________________
This message is from the kde mailing list.
Account management: https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.
More information about the kde
mailing list