Baho Utot wrote:
Jakub Schmidtke wrote:
How do you know if it locked?
A black screen with an X in the middle and no response from the KBD
until a hard reset. I think the x was looking for the kbd that never
showed up.
was ignored as was Fx
It does sound like you didn't include h
Baho Utot wrote:
> A black screen with an X in the middle and no response from the KBD
> until a hard reset. I think the x was looking for the kbd that never
> showed up.
> was ignored as was Fx
So if X didn't see the keyboard or mouse it would be the same?
As Jan wrote, check if hal is running
On Sun, Mar 15, 2009 at 09:34:21PM +0100, Xavier wrote:
> A quick google gave me this :
> https://bugs.kde.org/show_bug.cgi?id=155904
>
> The cpu usage mentioned are not anywhere near 99 though, but still
> worth a try to add this to $HOME/.kde4/share/config/kdedrc:
> [DirWatch]
> PollInterval=600
> If you have problems again do a strace of the kded4 process, this
> process normaly do a poll() of some sockets and pipes.
>
> Also if appears again ensure that have a clean /tmp and /var/tmp/ ;)
>
> For example, in normal execution, the poll interval is 5 seconds ( see
> http://djgera.pastebin.c
Baho Utot wrote:
>
> Ok i will see if that is what is going on.
>
> Is there a way to kill X if hal is not running other than a hard reset ?
>
> I am running jfs but I rather not test jfs ability to recover after a
> hard reset :)
>
Enable sysrq magic kernel.sysrq = 1 @ /etc/sysctl.conf
Then can
Preston C. wrote:
> Interestingly, I rebooted again, this time not immediately after the
> update/upgrade, but after logging into KDE. Everything seems to be
> fine now, hopefully this problem will not come up again. Thanks for
> the help.
>
>
If you have problems again do a strace of the kded4
Jakub Schmidtke wrote:
Baho Utot wrote:
Tried running X without a config file and it locked as well.
How do you know if it locked?
A black screen with an X in the middle and no response from the KBD
until a hard reset. I think the x was looking for the kbd that never
showed
Baho Utot wrote:
> Tried running X without a config file and it locked as well.
How do you know if it locked?
Jan de Groot wrote:
On Sun, 2009-03-15 at 17:19 -0400, Baho Utot wrote:
I have just installed arch onto a new SATA drive and isused a pacman
-Syu to fetch the latest updates.
I then continued on with alsa-utils then onto xorg
Used pacman -S xorg to install xorg
I then ran Xorg -configure
On Sun, 2009-03-15 at 17:19 -0400, Baho Utot wrote:
> I have just installed arch onto a new SATA drive and isused a pacman
> -Syu to fetch the latest updates.
>
> I then continued on with alsa-utils then onto xorg
>
> Used pacman -S xorg to install xorg
>
> I then ran Xorg -configure which prod
I have just installed arch onto a new SATA drive and isused a pacman
-Syu to fetch the latest updates.
I then continued on with alsa-utils then onto xorg
Used pacman -S xorg to install xorg
I then ran Xorg -configure which produced xorg.conf.new
Started X -config /root/xorg.conf.new
X starte
Interestingly, I rebooted again, this time not immediately after the
update/upgrade, but after logging into KDE. Everything seems to be
fine now, hopefully this problem will not come up again. Thanks for
the help.
I posted on the KDE forum, so I will see if they have any tips, before
I try to do to much.
Hello Preston,
I have had this problem on occassion, but it only appears maybe 3 times. I do a
killall kded4 and then krunner -> kded4. That seems to calm it down. I do not
understand what it does exactly.
http://api.kde.org/4.0-api/kdelibs-apidocs/kded/html/index.html
Shura
___
Thanks for the replies.
Bram, I did install KDE and I did restart after updating, although
this is the first time I have logged into KDE since the update..
Xavier, that is interesting. It seems to be a problem with KDE 4.2,
surely they would have fixed it with KDE 4.2.1? I never have had this
pro
> What got updated?
A lot, :-). I know KDE 4.2 -> 4.2.1. I searched the forum and wiki
but could not figure out what file or command to pull up or use to
show you what got updated?
On Sunday 15 March 2009 21:26:40 Preston C. wrote:
Hi Preston,
> My cpu monitor is almost reading 100%, right after I updated today. It
> was a very large update because I hadn't updated in about a month.
> Here is what "$top" gives me:
>
>
> top - 16:22:55 up 9 min, 2 users, load average: 1.36
On Sun, Mar 15, 2009 at 9:26 PM, Preston C. wrote:
> My cpu monitor is almost reading 100%, right after I updated today. It
> was a very large update because I hadn't updated in about a month.
> Here is what "$top" gives me:
>
>
> top - 16:22:55 up 9 min, 2 users, load average: 1.36, 1.32, 0.68
What got updated?
2009/3/15 Preston C. :
> My cpu monitor is almost reading 100%, right after I updated today. It
> was a very large update because I hadn't updated in about a month.
> Here is what "$top" gives me:
>
>
> top - 16:22:55 up 9 min, 2 users, load average: 1.36, 1.32, 0.68
> Tasks:
My cpu monitor is almost reading 100%, right after I updated today. It
was a very large update because I hadn't updated in about a month.
Here is what "$top" gives me:
top - 16:22:55 up 9 min, 2 users, load average: 1.36, 1.32, 0.68
Tasks: 99 total, 3 running, 96 sleeping, 0 stopped, 0
I am proud to announce the second release of a modified ArchLinux install CD
that includes spoken output for blind users.
It is mostly equivalent to the official "ftp CD", but
the system should start speaking as soon as you boot with it.
Speech is provided via the sound card, using the eSpeak softw
It was working, but not very well... When I gave up and tried to reboot, the
partition was in an inconsistent state. I had to run fsck -f, and then the UUID
was changed.
Anyway, I was wrong. I was trying to change the UUID of a vmware virtual disk,
and this operation made no difference.
Thanks
22 matches
Mail list logo
