Re: After upgrade to 4.6.2, kde freezes on login from kdm

2011-05-16 Thread Mordechai Niven
Spot on!

Reverted to the legacy driver as you suggested and all works again.

Thanks 

On Mon, May 16, 2011 at 3:21 AM, Marcos Raúl Carot Collins <
marcos.ca...@gmail.com> wrote:

> I noticed this happening in testing too, and it was due to an upgrade in
> the NVIDIA proprietary driver to version 270. Using the "Legacy GPU version
> (173.14.xx)" works again.
>
> I don't know if the problem is actually in the 270 driver or something
> between it and KDM (as I said it also happens in 4.4.5 from testing).
>
> Cheers,
>
> --
> Marcos R Carot Collins
>
>


After upgrade to 4.6.2, kde freezes on login from kdm

2011-05-15 Thread Marcos Raúl Carot Collins
I noticed this happening in testing too, and it was due to an upgrade in the
NVIDIA proprietary driver to version 270. Using the "Legacy GPU version
(173.14.xx)" works again.

I don't know if the problem is actually in the 270 driver or something
between it and KDM (as I said it also happens in 4.4.5 from testing).

Cheers,

-- 
Marcos R Carot Collins


After upgrade to 4.6.2, kde freezes on login from kdm

2011-05-13 Thread Mordechai Niven
I upgraded from 4.6.1 (which worked fine) to 4.6.2 from experimental. The
upgrade went apparently without problem.

However, when I try to login from kdm, the system hangs as the 5th icon (the
larger kde one) starts to fade in. The disk activity light carries on for a
few more settings and the the system does nothing. I can use ctrl-alt-F1 to
get back to a console and stop kdm. If i use alt-F7 to go back to X without
stopping it, the screen is now black, although the mouse cursor does move.

The same happens even when I tried logging in from a newly created user, so
it isn't related to a specific setting.

The xdm.log has nothing interesting, whilst .xsession.errors is full of
warnings (as noted in previous posts) but no clear indication what has
broken.

I have tried reinstalling most of the kde core packages without any effect.

I can use X with twm, but only by doing startx twm from a console - even if
I choose twm session from the kdm menu it goes into kde and then hangs.

I didn't find anything similar reported, using Google.

Does anyone have an idea of what might be going on or how to get a handle on
it.

Thanks,

Mark


Re: KDE Freezes and exits

2006-01-17 Thread Star King of the Grape Trees

ALWAYS use a subject!

El Virolo wrote:


Hi all,

I recently reinstalled Debian Sid on my Athlon XP machine, with KDE
3.5. The problem is I can't launch KDE : it freezes and gets back to
KDM as soon as it starts displaying "initializing hardware" ... Is
there a log file I can have a look at ? Is it a KDE or udev/hotplug
problem ?

Thanks in advance,

ElVirolo

 




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: KDE freezes on "initializing peripherals"

2002-05-01 Thread David Pashley
On Wednesday 01 May 2002 5:03 am, Phil Dibowitz wrote:
> Greg C. Madden wrote:
> > afaik, xserver-xfree86 is for Xfree86 ver. 4.x & xserver-svga is for
> > Xfree86 ver. 3.x so I don't know if I am much help.
>
> I found that out later tonight - and switched backed to xfree4 and had some
> help making some configuration changes and now all is working perfectly!
> Thanks for everyone's help.
>
>
> Phil

For what it is worth, you will find more information about wht is going on 
after you have logged in in the ~/.xsession-errors file. 

-- 
David Pashley
[EMAIL PROTECTED]
Nihil curo de ista tua stulta superstitione.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: KDE freezes on "initializing peripherals"

2002-04-30 Thread Phil Dibowitz
Greg C. Madden wrote:
afaik, xserver-xfree86 is for Xfree86 ver. 4.x & xserver-svga is for
Xfree86 ver. 3.x so I don't know if I am much help.

I found that out later tonight - and switched backed to xfree4 and had some help 
making some configuration changes and now all is working perfectly! Thanks for 
everyone's help.

Phil
--
Insanity Palace of Metallica
http://www.ipom.com
[EMAIL PROTECTED]
--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: KDE freezes on "initializing peripherals"

2002-04-30 Thread Greg C. Madden
On Tue, 2002-04-30 at 16:28, Phil Dibowitz wrote:
> Greg C. Madden wrote:
> 
> > Last time X-windows/KDE startup froze on me I found my fontpaths in
> > ~/XF86Config-4 were configured wrong. I had just loaded Abiword & was
> > trying to deal with Abiwords fontpath requirements. Fontpath issues can
> > include anti-aliasing in KDE I think.
> > 
> 
> 
> I actually just figured it out - I switched from using xserver-xfree86 to 
> xserver-svga and it works now.
> 
> My only problem now is that I get "interference" sort of. When I scroll in a 
> konsole or other app there's lots of white lines that appear, usually next to 
> or 
> above that application. This also happens when an app opens or closes. Any 
> ideas?

afaik, xserver-xfree86 is for Xfree86 ver. 4.x & xserver-svga is for
Xfree86 ver. 3.x so I don't know if I am much help.
-- 
Greg C. Madden
Debian GNU/Linux 3.0



signature.asc
Description: This is a digitally signed message part


Re: KDE freezes on "initializing peripherals"

2002-04-30 Thread Phil Dibowitz
Greg C. Madden wrote:
Last time X-windows/KDE startup froze on me I found my fontpaths in
~/XF86Config-4 were configured wrong. I had just loaded Abiword & was
trying to deal with Abiwords fontpath requirements. Fontpath issues can
include anti-aliasing in KDE I think.

I actually just figured it out - I switched from using xserver-xfree86 to 
xserver-svga and it works now.

My only problem now is that I get "interference" sort of. When I scroll in a 
konsole or other app there's lots of white lines that appear, usually next to or 
above that application. This also happens when an app opens or closes. Any ideas?

Phil
--
Insanity Palace of Metallica
http://www.ipom.com
[EMAIL PROTECTED]
--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: KDE freezes on "initializing peripherals"

2002-04-30 Thread Greg C. Madden
On Tue, 2002-04-30 at 11:32, Phil Dibowitz wrote:
> Hey all,
> 
> I've installed KDE on my debian box (via apt-get) and when I fire it up it 
> seems 
> to work fine until I it gets to "initializing perihperals" at which point it 
> freezes - and takes console with it. Nothing can be done at console. 
> ctrl-alt-backspace doesn't kill X, virtual consoles can't be used. I CAN ssh 
> in, 
> but killing X doesn't bring back console - the KDE start up screen stays 
> until a 
> reboot is done.
> 
> Interestingly enough prior to getting to "initializing perihperals" I can use 
> my 
> mouse just fine. If I set KDE to startup at boot I can use my mouse and type 
> in 
> my password just fine (implying both mouse and keyboard are configured 
> correctly 
> in XF86Config) - but after logging in, when it gets to "initializing 
> perihperals" it again freezes.
> 
> Another note: I can launch X and twm and it works fine - it's just KDE that 
> has 
> a problem. The logs aren't very helpful here:

Last time X-windows/KDE startup froze on me I found my fontpaths in
~/XF86Config-4 were configured wrong. I had just loaded Abiword & was
trying to deal with Abiwords fontpath requirements. Fontpath issues can
include anti-aliasing in KDE I think.
-- 
Greg C. Madden
Debian GNU/Linux 3.0



signature.asc
Description: This is a digitally signed message part


KDE freezes on "initializing peripherals"

2002-04-30 Thread Phil Dibowitz
Hey all,
I've installed KDE on my debian box (via apt-get) and when I fire it up it seems 
to work fine until I it gets to "initializing perihperals" at which point it 
freezes - and takes console with it. Nothing can be done at console. 
ctrl-alt-backspace doesn't kill X, virtual consoles can't be used. I CAN ssh in, 
but killing X doesn't bring back console - the KDE start up screen stays until a 
reboot is done.

Interestingly enough prior to getting to "initializing perihperals" I can use my 
mouse just fine. If I set KDE to startup at boot I can use my mouse and type in 
my password just fine (implying both mouse and keyboard are configured correctly 
in XF86Config) - but after logging in, when it gets to "initializing 
perihperals" it again freezes.

Another note: I can launch X and twm and it works fine - it's just KDE that has 
a problem. The logs aren't very helpful here:

$ tail -25 XFree86.0.log
(WW) VESA(0): Option "UseFBDev" is not used
(II) Setting vga for screen 0.
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension LBX
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
PEXExtensionInit: Couldn't open default PEX font file  Roman_M
(II) Keyboard "Generic Keyboard" handled by legacy driver
(**) Option "Protocol" "PS/2"
(**) Configured Mouse: Protocol: "PS/2"
(**) Option "CorePointer"
(**) Configured Mouse: Core Pointer
(**) Option "Device" "/dev/psaux"
(==) Configured Mouse: Buttons: 3
(**) Option "Emulate3Buttons" "true"
(**) Configured Mouse: Emulate3Buttons, Emulate3Timeout: 50
(**) Option "ZAxisMapping" "4 5"
(**) Configured Mouse: ZAxisMapping: buttons 4 and 5
(II) XINPUT: Adding extended input device "Configured Mouse" (type: MOUSE)
And I'm using testing, which has KDE 2.2.2:
$ dpkg -l | grep kde
ii  kde2.2.24 The K Desktop Environment
ii  kdebase2.2.2-14   KDE core applications
ii  kdebase-audiol 2.2.2-14   KDE audio libraries amd modules for kdebase
ii  kdebase-doc2.2.2-14   Documentation for Applications in kdebase
ii  kdebase-libs   2.2.2-14   KDE libraries and modules for kdebase
ii  kdelibs3   2.2.2-13   KDE core libraries (runtime files)
ii  kdelibs3-bin   2.2.2-13   KDE core binaries (binary files)
ii  kdepasswd  2.2.2-9A Password changer frontend for KDE
ii  kdewallpapers  2.2.2-14   Some wallpapers for KDE
ii  libkdenetwork1 2.2.2-14   Common libraries needed for KDE network appl
Laslty I asked this question on the KDE list over at kde.org and was told by a 
few who couldn't not figure it out that I might have better luck over here...

Any help would be much appreciated.
Thanks,
Phil
--
"They that can give up essential liberty to obtain a little temporary safety 
deserve neither liberty nor safety."
-Benjamin Franklin, 1759

--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: KDE Freezes

2001-07-17 Thread Alexander Benjik
Am Montag, 16. Juli 2001 16:11 schrieb Rob Weir:
> I've got a pretty standard woody box, and I recently upgraded to
> the KDE2.2beta1 packages from unstable.  I can log on through KDM
> fine, but once I'm in KDE and try to run a KDE program, my machine
> locks hard.  Real hard.  I can sync, unmount and reboot using the
> SysRq key, but ctrl-alt-bkspc out of X doesn't work, and neither does
> ctrl-alt-Fn to get a console.
>
> I'm running kernel 2.4.6, XFree86 4.0.3, with the NVidia GLX (version
> 1.0.1251-2) drivers compiled from woody.  I'm also using the ALSA
> modules, version 0.5.10b-8, again, compiled from the testing sources.

I have a very similar constelation. Try to use the Nvidia Drivers 0.9-769
When i use the 1.0125 my system locks from time to time. 

>
> The odd thing is, KDE starts up fine, but running a KDE program locks
> it up hard.  This also happens when I'm running E and start kmail.  So
> far, the programs that cause the crash are known to be:  NoAtun,
> KMail and Konqy.  As you can imagine, testing this sort of thing is
> not the funnest type of thing in the world, but if anyone has
> something they want me to try, ask away.
>
> Based on the severity of the lock-up, I'm thinking that the NVidia
> drivers are causing it, because it definitely doesn't seem like
> something a user-space app could do.
> Another thought I had is that it could be ALSA.  ALSA refuses to save
> or restore my volume settings on reboot and it seems that every second
> boot requires a '/etc/init.d/alsa force-reload; alsaconf' to get them
> to work at all.


Content-Type: application/pgp-signature; charset="us-ascii"; name="Anhang: 1"
Content-Transfer-Encoding: 7bit
Content-Description: 





Re: KDE Freezes

2001-07-16 Thread Putz Ákos
Just a guess: maybe you should try it without alsa and / or NVidia
kerneldrivers, and with the standard XFree nvidia X driver.
And, isn't it possible, that your linux isn't freezing, maybe it is..ehm.
waiting for something? (device, etc). Try waiting a few minutes, telneting
from other host, running top, etc.

-- 
Putz Ákos   Email : [EMAIL PROTECTED]  




KDE Freezes

2001-07-16 Thread Rob Weir
I've got a pretty standard woody box, and I recently upgraded to
the KDE2.2beta1 packages from unstable.  I can log on through KDM
fine, but once I'm in KDE and try to run a KDE program, my machine
locks hard.  Real hard.  I can sync, unmount and reboot using the
SysRq key, but ctrl-alt-bkspc out of X doesn't work, and neither does
ctrl-alt-Fn to get a console.

I'm running kernel 2.4.6, XFree86 4.0.3, with the NVidia GLX (version
1.0.1251-2) drivers compiled from woody.  I'm also using the ALSA 
modules, version 0.5.10b-8, again, compiled from the testing sources.

The odd thing is, KDE starts up fine, but running a KDE program locks
it up hard.  This also happens when I'm running E and start kmail.  So
far, the programs that cause the crash are known to be:  NoAtun,
KMail and Konqy.  As you can imagine, testing this sort of thing is
not the funnest type of thing in the world, but if anyone has
something they want me to try, ask away.

Based on the severity of the lock-up, I'm thinking that the NVidia
drivers are causing it, because it definitely doesn't seem like
something a user-space app could do.
Another thought I had is that it could be ALSA.  ALSA refuses to save
or restore my volume settings on reboot and it seems that every second
boot requires a '/etc/init.d/alsa force-reload; alsaconf' to get them
to work at all.  

pgp8YRNKpdxzz.pgp
Description: PGP signature