Well, after checking the syslog entries generated by kdm I realized that the problem was an I/O error on /var/run/xdmctl [...] In fact, I have had to reinstall my X server some time ago, as similar disk I/O related problems did occur.

Has anybody experienced similar problems? What should be done?

Yes. Replace hard disk. Simple ;) Use package smartmontools and run smartctl -s on -a /dev/hda to get information on the disk's internal selftest status. Run disk selftests with smartctl -t short /dev/hda and smartctl -t long /dev/hda. If either stops with a block error the disk is dead. If the number of reallocated sectors is very high, say

100: disk dead. If it keeps increasing: disk dieing fast.

As you had a few of these disk read errors now, chances of the disk not being *&@*#$(ed are very small. Volker -- Volker Kuhlmann is possibly list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me.

I am running ide-smart regularly from a cron job and never had any disk problem reported. Today I have installed smartmontools and run the smartctl tests on the disk, which passed them without any problem.

Hmm. Faultless disks don't have read errors, but you logged some. If the disk is indeed faultless, then there's another hardware error in the system. Bad IDE cable? Bad contact? Unreliable mobo? Overclocked box (always a bad idea)? Volker -- Volker Kuhlmann is possibly list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me.

El Jue 09 Sep 2004 18:54, Patrick Shanahan escribió:

I use ext3 on SuSE 9.0, and have also lost the 'Start new session' menu entry. I have added screens :1, :2 and :3 per your example. What did you do to correct the I/O error and what was the error?

On my /var/log/messages, kdm printed the following: Sep 9 11:41:57 orchid kdm[11410]: Cannot create control FiFo "/var/run/xdmctl/xdmctl" Sep 9 11:41:57 orchid kdm[11410]: mkdir "/var/run/xdmctl/dmctl" failed; no control sockets will be available When trying to create the /var/run/xdmctl/dmctl directory from the shell, it returned with an I/O error. I then simply renamed this dir to xdmctl.old and created a new xdmctl directory and tried to touch files and create dirs in it, just to make sure it would be writable. After 'rckdm restart', all was well. I should remark that neither smart-ide nor smartctl from the package Volker has recommended in another post from this thread have so far reported any disk problems. -- Andreas Philipp Noema Ltda. Bogotá, D.C. - Colombia

Hi All I'm using SuSE 8.1 prof and am now in a pickle. I've just upgraded to the latest version of KDE (3.3) from 3.2 using synaptic and everything went perfectly. However, when I restart from a fresh boot of the system or from "rcxdm start" the login window never comes up and the program returns to the console in both cases. The system log only reports: "Abnormal termination of greeter for display :0, code 127, signal 0" I also received an email to root after running SuSEConfig telling me: "the following variables seem to be doubled in /etc/rc.config and/or the files in /etc/sysconfig: /etc/sysconfig/displaymanager: KDM_GREETING="" /etc/sysconfig/displaymanager: KDM_GREETING="" /etc/sysconfig/displaymanager: KDM_SHUTDOWN="auto" /etc/sysconfig/displaymanager: KDM_SHUTDOWN="auto" /etc/sysconfig/displaymanager: KDM_USERS="" /etc/sysconfig/displaymanager: KDM_USERS="" please specify them correctly" These two error reports seem related but I can't locate how to fix them up and also whether that is the explanation as to why my desktop is not starting. I took the rather studid step (as I later found out) of reinstalling the version of KDE (3.0.3) that came with SuSE 8.1 prof using yast2 and then doing a new install of 3.3. However, the final result was the same, KDE 3.3 doesn't start. I'm desparate to get it up and running as term starts very soon and I still have a lot of preparation to do so has anyone got any ideas as to how to resolve this problem? I've had to resort to Windows in order to post this email message. John Satherley

Hi Fergus/All Thanks for you comments. I've answered below after your points. Cheers John Quoting Fergus Wilde :

On Friday 10 September 2004 09:10, js1@liverpool.ac.uk wrote:

...

Hi All I'm using SuSE 8.1 prof and am now in a pickle.

I've just upgraded to the latest version of KDE (3.3) from 3.2 using synaptic and everything went perfectly. However, when I restart from a fresh boot of the system or from "rcxdm start" the login window never comes up and the program returns to the console in both cases.

One thing you might wan to try is making sure all your access files are cleared out of /tmp. Anything called mcop or dcop or which have your username ought to go, as I remember. Have you verified whether these variables are in fact duplicated in the files concerned? If so, I'd copy the originals to a backup name and deduplicate. 9.1 doesn't have /etc/rc.conf any more, but I don't know when it went.

I had in fact deleted all these files and also the equivalent ones in my home directory. I've also located the offending double entries and commented them out. Unfortunately it make no difference. The offending double entries appear in both the displaymanager and windowmanager files in /etc/sysconfig. However, should I have both these files?

If that doesn't work, I'd try setting up another ordinary user and seeing if you can log in with that identity.

Good idea but the problem is that you need to be in root to issue the command "rcxdm start" and then the opening login window never appears so I can't actually login as another user. Or am I missing something?

Somebody who can remember more details may tell you more, but I'm pretty sure you won't break anything trying those.

...

The system log only reports: "Abnormal termination of greeter for display :0, code 127, signal 0"

I also received an email to root after running SuSEConfig telling me: "the following variables seem to be doubled in /etc/rc.config and/or the files in /etc/sysconfig: /etc/sysconfig/displaymanager: KDM_GREETING="" /etc/sysconfig/displaymanager: KDM_GREETING="" /etc/sysconfig/displaymanager: KDM_SHUTDOWN="auto" /etc/sysconfig/displaymanager: KDM_SHUTDOWN="auto" /etc/sysconfig/displaymanager: KDM_USERS="" /etc/sysconfig/displaymanager: KDM_USERS="" please specify them correctly"

These two error reports seem related but I can't locate how to fix them up and also whether that is the explanation as to why my desktop is not starting.

I took the rather studid step (as I later found out) of reinstalling the version of KDE (3.0.3) that came with SuSE 8.1 prof using yast2 and then doing a new install of 3.3. However, the final result was the same, KDE 3.3 doesn't start.

I'm desparate to get it up and running as term starts very soon and I still have a lot of preparation to do so has anyone got any ideas as to how to resolve this problem? I've had to resort to Windows in order to post this email message. John Satherley

-- Fergus Wilde Chetham's Library Long Millgate Manchester M3 1SB

Tel: 0161 834 7961 Fax: 0161 839 5797

http://www.chethams.org.uk

-- To unsubscribe, email: suse-kde-unsubscribe@suse.com For additional commands, email: suse-kde-help@suse.com Please do not cross-post to suse-linux-e

Hi Fergus/All Thanks for you comments. I've answered below after your points. Cheers John

Quoting Fergus Wilde :

...

On Friday 10 September 2004 09:10, js1@liverpool.ac.uk wrote:

...

Hi All I'm using SuSE 8.1 prof and am now in a pickle.

I've just upgraded to the latest version of KDE (3.3) from 3.2 using synaptic and everything went perfectly. However, when I restart from a fresh boot of the system or from "rcxdm start" the login window never comes up and the program returns to the console in both cases.

One thing you might wan to try is making sure all your access files are cleared out of /tmp. Anything called mcop or dcop or which have your username ought to go, as I remember. Have you verified whether these variables are in fact duplicated in the files concerned? If so, I'd copy the originals to a backup name and deduplicate. 9.1 doesn't have /etc/rc.conf any more, but I don't know when it went.

I had in fact deleted all these files and also the equivalent ones in my home directory. I've also located the offending double entries and commented them out. Unfortunately it make no difference. The offending double entries appear in both the displaymanager and windowmanager files in /etc/sysconfig. However, should I have both these files?

...

If that doesn't work, I'd try setting up another ordinary user and seeing if you can log in with that identity.

Good idea but the problem is that you need to be in root to issue the command "rcxdm start" and then the opening login window never appears so I can't actually login as another user. Or am I missing something?

...

Somebody who can remember more details may tell you more, but I'm pretty sure you won't break anything trying those.

...

The system log only reports: "Abnormal termination of greeter for display

:0, code 127, signal 0"

I also received an email to root after running SuSEConfig telling me: "the following variables seem to be doubled in /etc/rc.config and/or the files in /etc/sysconfig: /etc/sysconfig/displaymanager: KDM_GREETING="" /etc/sysconfig/displaymanager: KDM_GREETING="" /etc/sysconfig/displaymanager: KDM_SHUTDOWN="auto" /etc/sysconfig/displaymanager: KDM_SHUTDOWN="auto" /etc/sysconfig/displaymanager: KDM_USERS="" /etc/sysconfig/displaymanager: KDM_USERS="" please specify them correctly"

These two error reports seem related but I can't locate how to fix

Hi Lennart I've carried out the tests you mention below. There doesn't seem to be anything amiss in /var/log/XFree86.0.log but at the end of /var/log/kdm.log there is the following error message: ** (/opt/kde3/bin/kdm_greet: relocation error: /opt/kde3/lib/libkdecore.so.4: undefined symbol: _ZN6QImage15setMaxImageSizeERK5QSize ** I also got gnome up and running so could access my linux file structure. The fact that it runs would seem also to indicate that the X-server is OK. I next tried to run startx as root and as several ordinary users but the result was always the same it terminated before any login windows appeared and reverted to the console terminal. Here's the end of the output (beginning where errors start to be reported) on the console screen after termination: *** (EE) NV(0): The Riva 128 chipset does not support depth 16. Using depth 15 instead (WW) NV(0): Failed to set up write-combining range (0xf2000000,0x800000) kdeinit: relocation error: /usr/lib/./libqt-mt.so.3: undefined symbol: FT_Seek_Stream startkde: Could not start kdeinit. Check your installation. ksplash: relocation error: /opt/kde3/lib/libkdecore.so.4: undefined symbol: _ZN6QImage15setMaxImageSizeERK5QSize Warning: connect() failed: : No such file or directory kdeinit: kded: relocation error: /opt/kde3/lib/libkdecore.so.4: undefined symbol: _ZN6QImage15setMaxImageSizeERK5QSize DCOP aborting call from 'anonymous-2724' to 'kded' kded: ERROR: Communication problem with kded, it probably crashed. ksmserver: relocation error: /opt/kde3/lib/libkdecore.so.4: undefined symbol: _ZN6QImage15setMaxImageSizeERK5QSize startkde: Shutting down... startkde: Running shutdown scripts... ICE default IO error handler doing an exit(), pid = 2723, errno = 2 startkde: Done. waiting for X server to shut down WARNING: DCOP communication problem! kdeinit: Communication error with launcher. Exiting! ** Hope this info tells you something about what is happening. I look forward to you or anyone else beginning able to resolve this problem and get me back on track. Thanks for help Have a good weekend. John ----- Original Message ----- From: "Lennart Börjeson" To: Sent: Friday, September 10, 2004 1:26 PM Subject: Re: [suse-kde] Upgrade to KDE 3.3 followed by a crash on starting Try to establish whether it is the X-server or kdm which crasches, i.e. log in as root on the console and examine /var/log/XFree86.0.log and /var/log/kdm.log after a crash. If kdm seems to crash, try to get *something* up by logging in on the console and enter startx as any user. If you get a desktop, fine for now, if not try another user, maybe even root. Did X crash? Examine /var/XFree86.0.log. If you get a desktop but still can't start kdm, examine kdm.log *caarefully* and report back here... /Lennart fredagen den 10 september 2004 13.39 skrev js1@liverpool.ac.uk: them

...

...

up and also whether that is the explanation as to why my desktop is not starting.

I took the rather studid step (as I later found out) of reinstalling the version of KDE (3.0.3) that came with SuSE 8.1 prof using yast2 and then doing a new install of 3.3. However, the final result was the same, KDE 3.3 doesn't start.

I'm desparate to get it up and running as term starts very soon and I still have a lot of preparation to do so has anyone got any ideas as to how to resolve this problem? I've had to resort to Windows in order to post this email message. John Satherley

-- Fergus Wilde Chetham's Library Long Millgate Manchester M3 1SB

Tel: 0161 834 7961 Fax: 0161 839 5797

http://www.chethams.org.uk

-- To unsubscribe, email: suse-kde-unsubscribe@suse.com For additional commands, email: suse-kde-help@suse.com Please do not cross-post to suse-linux-e

-- !++ ! Lennart Börjeson ! Partner, Developer ! Cinnober Financial Technology AB ! Industrigatan 2A ! S-112 46 STOCKHOLM ! Sverige/Sweden/Schweden/Suède ! mailto:Lennart.Borjeson@cinnober.com ! phone:+46-8-50304717 ! gsm:+46-70-3394717 ! fax:+46-8-50304701 ! http://www.cinnober.com !-- -- To unsubscribe, email: suse-kde-unsubscribe@suse.com For additional commands, email: suse-kde-help@suse.com Please do not cross-post to suse-linux-e

Over the weekend I checked a number of things including the kde requirements. I noticed that it requires qt3 version >= 3.2. I had version 3.2 installed but noticed that 3.3 was available so I installed that and low and behold kde returned with a login screen and the desktop returned. However, the kicker panel is unfortunately not functioning as normal. Firstly, it didn't reappear as it was for kde3.2 and secondly it does not show any of my 6 desktop windows (I can toggle through them with shift-tab) and a number of programs like kopete, kmix do not show up in the panel either as running programs or as applets but they do appear to be running in the background according to ksysguard. I get the following result on running: rpm -qf /opt/kde3/lib/libkdecore.so.4 /opt/kde3/bin/kdm_greet kdelibs3-3.3.0-7 kdebase3-kdm-3.3.0-8 However, after the new qt3 install the error I noticed relating to the kdm-greet has disappeared from the log files so I presume these two files must be compatible. Any thoughts on what might be wrong with the kicker panel? John On Monday 13 September 2004 11:09, Lennart Börjeson wrote:

OK, so you have an incompatibilty. kdm_greet comes from kdebase3-kdm and libkdecore from kdelibs3. Check that what versions rpm belives you have installed, i.e. do:

rpm -qf /opt/kde3/lib/libkdecore.so.4 /opt/kde3/bin/kdm_greet

On my system this returns

kdelibs3-3.3.0-14 kdebase3-kdm-3.3.0-8

which seems consistent. Check that your packages are of compatible versions. Even if rpm seems to believe they are, reinstall the packages anyway, just in case rpm has screwed up.

/Lennart

fredagen den 10 september 2004 18.11 skrev John Satherley:

...

Hi Lennart I've carried out the tests you mention below. There doesn't seem to be anything amiss in /var/log/XFree86.0.log but at the end of /var/log/kdm.log there is the following error message: ** (/opt/kde3/bin/kdm_greet: relocation error: /opt/kde3/lib/libkdecore.so.4: undefined symbol: _ZN6QImage15setMaxImageSizeERK5QSize ** I also got gnome up and running so could access my linux file structure. The fact that it runs would seem also to indicate that the X-server is OK.

I next tried to run startx as root and as several ordinary users but the result was always the same it terminated before any login windows appeared and reverted to the console terminal. Here's the end of the output (beginning where errors start to be reported) on the console screen after termination: *** (EE) NV(0): The Riva 128 chipset does not support depth 16. Using depth 15 instead (WW) NV(0): Failed to set up write-combining range (0xf2000000,0x800000) kdeinit: relocation error: /usr/lib/./libqt-mt.so.3: undefined symbol: FT_Seek_Stream startkde: Could not start kdeinit. Check your installation. ksplash: relocation error: /opt/kde3/lib/libkdecore.so.4: undefined symbol: _ZN6QImage15setMaxImageSizeERK5QSize Warning: connect() failed: : No such file or directory kdeinit: kded: relocation error: /opt/kde3/lib/libkdecore.so.4: undefined symbol: _ZN6QImage15setMaxImageSizeERK5QSize DCOP aborting call from 'anonymous-2724' to 'kded' kded: ERROR: Communication problem with kded, it probably crashed. ksmserver: relocation error: /opt/kde3/lib/libkdecore.so.4: undefined symbol: _ZN6QImage15setMaxImageSizeERK5QSize startkde: Shutting down... startkde: Running shutdown scripts... ICE default IO error handler doing an exit(), pid = 2723, errno = 2 startkde: Done.

waiting for X server to shut down WARNING: DCOP communication problem! kdeinit: Communication error with launcher. Exiting! ** Hope this info tells you something about what is happening. I look forward to you or anyone else beginning able to resolve this problem and get me back on track. Thanks for help Have a good weekend. John

----- Original Message ----- From: "Lennart Börjeson" To: Sent: Friday, September 10, 2004 1:26 PM Subject: Re: [suse-kde] Upgrade to KDE 3.3 followed by a crash on starting

Try to establish whether it is the X-server or kdm which crasches, i.e. log in as root on the console and examine /var/log/XFree86.0.log and /var/log/kdm.log after a crash.

If kdm seems to crash, try to get *something* up by logging in on the console and enter

startx

as any user.

If you get a desktop, fine for now, if not try another user, maybe even root. Did X crash? Examine /var/XFree86.0.log. If you get a desktop but still can't start kdm, examine kdm.log *caarefully* and report back here...

/Lennart

fredagen den 10 september 2004 13.39 skrev js1@liverpool.ac.uk:

...

Hi Fergus/All Thanks for you comments. I've answered below after your points. Cheers John

Quoting Fergus Wilde :

...

On Friday 10 September 2004 09:10, js1@liverpool.ac.uk wrote:

...

Hi All I'm using SuSE 8.1 prof and am now in a pickle.

I've just upgraded to the latest version of KDE (3.3) from 3.2 using synaptic and everything went perfectly. However, when I restart from a fresh boot of the system or from "rcxdm start" the login window never comes up and the program returns to the console in both cases.

One thing you might wan to try is making sure all your access files are cleared out of /tmp. Anything called mcop or dcop or which have your username ought to go, as I remember. Have you verified whether these variables are in fact duplicated in the files concerned? If so, I'd

copy

...

...

the originals to a backup name and deduplicate. 9.1 doesn't have /etc/rc.conf any more, but I don't know when it went.

I had in fact deleted all these files and also the equivalent ones in my home directory. I've also located the offending double entries and commented them out. Unfortunately it make no difference. The offending double entries appear in both the displaymanager and windowmanager files

in

...

/etc/sysconfig. However, should I have both these files?

...

If that doesn't work, I'd try setting up another ordinary user and

seeing

...

...

if you can log in with that identity.

Good idea but the problem is that you need to be in root to issue the command "rcxdm start" and then the opening login window never appears so I can't actually login as another user. Or am I missing something?

...

Somebody who can remember more details may tell you more, but I'm pretty sure you won't break anything trying those.

...

The system log only reports: "Abnormal termination of greeter for display

:0, code 127, signal 0"

I also received an email to root after running SuSEConfig telling me: "the following variables seem to be doubled in /etc/rc.config and/or the files in /etc/sysconfig: /etc/sysconfig/displaymanager: KDM_GREETING="" /etc/sysconfig/displaymanager: KDM_GREETING="" /etc/sysconfig/displaymanager: KDM_SHUTDOWN="auto" /etc/sysconfig/displaymanager: KDM_SHUTDOWN="auto" /etc/sysconfig/displaymanager: KDM_USERS="" /etc/sysconfig/displaymanager: KDM_USERS="" please specify them correctly"

These two error reports seem related but I can't locate how to fix

them

...

...

...

up and also whether that is the explanation as to why my desktop is

not

...

...

...

starting.

I took the rather studid step (as I later found out) of reinstalling the version of KDE (3.0.3) that came with SuSE 8.1 prof using yast2

and

...

...

...

then doing a new install of 3.3. However, the final result was the same, KDE 3.3 doesn't start.

I'm desparate to get it up and running as term starts very soon and I still have a lot of preparation to do so has anyone got any ideas as

to

...

...

...

how to resolve this problem? I've had to resort to Windows in order to post this email message. John Satherley

-- Fergus Wilde Chetham's Library Long Millgate Manchester M3 1SB

Tel: 0161 834 7961 Fax: 0161 839 5797

http://www.chethams.org.uk

-- To unsubscribe, email: suse-kde-unsubscribe@suse.com For additional commands, email: suse-kde-help@suse.com Please do not cross-post to suse-linux-e

-- !++ ! Lennart Börjeson ! Partner, Developer ! Cinnober Financial Technology AB ! Industrigatan 2A ! S-112 46 STOCKHOLM ! Sverige/Sweden/Schweden/Suède ! mailto:Lennart.Borjeson@cinnober.com ! phone:+46-8-50304717 ! gsm:+46-70-3394717 ! fax:+46-8-50304701 ! http://www.cinnober.com !--

-- Dr J. Satherley Department of Chemistry University of Liverpool Liverpool Merseyside L69 7ZD United Kingdom Phone: +44 (0) 151 794 3530 Fax: +44 (0) 151 794 3588 Email: js1@liverpool.ac.uk

As far as I can tell I've got the latest versions of the kde files available; at least on the synaptic server. I'll wait till there are some updates rather than wasting time tying to solve this kicker problem as I can use my system now. Thanks for your help on this Lennart. John On Monday 13 September 2004 15:21, Lennart Börjeson wrote:

Re. Kicker:

I had that problem, too, after my initial upgrade from KDE 3.2 to 3.3. However, I upgraded once more some days later when there were new 3.3-packages released and the problem disappeared.

When I had the problem, I could make the icons reappear by changing the kicker settings (any setting) for the tray. NB! Their appearance didn't "stuck", i.e. next time I restarted kde (e.g. by logout+login) they were gone once again.

Have you downloaded your packages recently? If not, download again.

/Lennart

måndagen den 13 september 2004 13.37 skrev John Satherley:

...

Over the weekend I checked a number of things including the kde requirements. I noticed that it requires qt3 version >= 3.2. I had version 3.2 installed but noticed that 3.3 was available so I installed that and low and behold kde returned with a login screen and the desktop returned. However, the kicker panel is unfortunately not functioning as normal. Firstly, it didn't reappear as it was for kde3.2 and secondly it does not show any of my 6 desktop windows (I can toggle through them with shift-tab) and a number of programs like kopete, kmix do not show up in the panel either as running programs or as applets but they do appear to be running in the background according to ksysguard.

I get the following result on running: rpm -qf /opt/kde3/lib/libkdecore.so.4 /opt/kde3/bin/kdm_greet kdelibs3-3.3.0-7 kdebase3-kdm-3.3.0-8

However, after the new qt3 install the error I noticed relating to the kdm-greet has disappeared from the log files so I presume these two files must be compatible.

Any thoughts on what might be wrong with the kicker panel? John

On Monday 13 September 2004 11:09, Lennart Börjeson wrote:

...

OK, so you have an incompatibilty. kdm_greet comes from kdebase3-kdm and libkdecore from kdelibs3. Check that what versions rpm belives you have installed, i.e. do:

rpm -qf /opt/kde3/lib/libkdecore.so.4 /opt/kde3/bin/kdm_greet

On my system this returns

kdelibs3-3.3.0-14 kdebase3-kdm-3.3.0-8

which seems consistent. Check that your packages are of compatible versions. Even if rpm seems to believe they are, reinstall the packages anyway, just in case rpm has screwed up.

/Lennart

fredagen den 10 september 2004 18.11 skrev John Satherley:

...

Hi Lennart I've carried out the tests you mention below. There doesn't seem to be anything amiss in /var/log/XFree86.0.log but at the end of /var/log/kdm.log there is the following error message: ** (/opt/kde3/bin/kdm_greet: relocation error: /opt/kde3/lib/libkdecore.so.4: undefined symbol: _ZN6QImage15setMaxImageSizeERK5QSize ** I also got gnome up and running so could access my linux file structure. The fact that it runs would seem also to indicate that the X-server is OK.

I next tried to run startx as root and as several ordinary users but the result was always the same it terminated before any login windows appeared and reverted to the console terminal. Here's the end of the output (beginning where errors start to be reported) on the console screen after termination: *** (EE) NV(0): The Riva 128 chipset does not support depth 16. Using depth 15 instead (WW) NV(0): Failed to set up write-combining range (0xf2000000,0x800000) kdeinit: relocation error: /usr/lib/./libqt-mt.so.3: undefined symbol: FT_Seek_Stream startkde: Could not start kdeinit. Check your installation. ksplash: relocation error: /opt/kde3/lib/libkdecore.so.4: undefined symbol: _ZN6QImage15setMaxImageSizeERK5QSize Warning: connect() failed: : No such file or directory kdeinit: kded: relocation error: /opt/kde3/lib/libkdecore.so.4: undefined symbol: _ZN6QImage15setMaxImageSizeERK5QSize DCOP aborting call from 'anonymous-2724' to 'kded' kded: ERROR: Communication problem with kded, it probably crashed. ksmserver: relocation error: /opt/kde3/lib/libkdecore.so.4: undefined symbol: _ZN6QImage15setMaxImageSizeERK5QSize startkde: Shutting down... startkde: Running shutdown scripts... ICE default IO error handler doing an exit(), pid = 2723, errno = 2 startkde: Done.

waiting for X server to shut down WARNING: DCOP communication problem! kdeinit: Communication error with launcher. Exiting! ** Hope this info tells you something about what is happening. I look forward to you or anyone else beginning able to resolve this problem and get me back on track. Thanks for help Have a good weekend. John

----- Original Message ----- From: "Lennart Börjeson" To: Sent: Friday, September 10, 2004 1:26 PM Subject: Re: [suse-kde] Upgrade to KDE 3.3 followed by a crash on starting

Try to establish whether it is the X-server or kdm which crasches, i.e. log in as root on the console and examine /var/log/XFree86.0.log and /var/log/kdm.log after a crash.

If kdm seems to crash, try to get *something* up by logging in on the console and enter

startx

as any user.

If you get a desktop, fine for now, if not try another user, maybe even root. Did X crash? Examine /var/XFree86.0.log. If you get a desktop but still can't start kdm, examine kdm.log *caarefully* and report back here...

/Lennart

fredagen den 10 september 2004 13.39 skrev js1@liverpool.ac.uk:

...

Hi Fergus/All Thanks for you comments. I've answered below after your points. Cheers John

Quoting Fergus Wilde :

...

On Friday 10 September 2004 09:10, js1@liverpool.ac.uk wrote: > Hi All > I'm using SuSE 8.1 prof and am now in a pickle. > > I've just upgraded to the latest version of KDE (3.3) from 3.2 > using synaptic and everything went perfectly. However, when I > restart from a fresh boot of the system or from "rcxdm start" > the login window never comes up and the program returns to the > console in both cases.

One thing you might wan to try is making sure all your access files are cleared out of /tmp. Anything called mcop or dcop or which have your username ought to go, as I remember. Have you verified whether these variables are in fact duplicated in the files concerned? If so, I'd

copy

...

...

the originals to a backup name and deduplicate. 9.1 doesn't have /etc/rc.conf any more, but I don't know when it went.

I had in fact deleted all these files and also the equivalent ones in my home directory. I've also located the offending double entries and commented them out. Unfortunately it make no difference. The offending double entries appear in both the displaymanager and windowmanager files

in

...

/etc/sysconfig. However, should I have both these files?

...

If that doesn't work, I'd try setting up another ordinary user and

seeing

...

...

if you can log in with that identity.

Good idea but the problem is that you need to be in root to issue the command "rcxdm start" and then the opening login window never appears so I can't actually login as another user. Or am I missing something?

...

Somebody who can remember more details may tell you more, but I'm pretty sure you won't break anything trying those.

> The system log only reports: "Abnormal termination of greeter > for display > > :0, code 127, signal 0" > > I also received an email to root after running SuSEConfig > telling me: "the following variables seem to be doubled in > /etc/rc.config and/or the files in /etc/sysconfig: > /etc/sysconfig/displaymanager: KDM_GREETING="" > /etc/sysconfig/displaymanager: KDM_GREETING="" > /etc/sysconfig/displaymanager: KDM_SHUTDOWN="auto" > /etc/sysconfig/displaymanager: KDM_SHUTDOWN="auto" > /etc/sysconfig/displaymanager: KDM_USERS="" > /etc/sysconfig/displaymanager: KDM_USERS="" > please specify them correctly" > > These two error reports seem related but I can't locate how to > fix

them

...

...

> up and also whether that is the explanation as to why my > desktop is

not

...

...

> starting. > > I took the rather studid step (as I later found out) of > reinstalling the version of KDE (3.0.3) that came with SuSE 8.1 > prof using yast2

and

...

...

> then doing a new install of 3.3. However, the final result was > the same, KDE 3.3 doesn't start. > > I'm desparate to get it up and running as term starts very soon > and I still have a lot of preparation to do so has anyone got > any ideas as

to

...

...

> how to resolve this problem? I've had to resort to Windows in > order to post this email message. John Satherley

-- Fergus Wilde Chetham's Library Long Millgate Manchester M3 1SB

Tel: 0161 834 7961 Fax: 0161 839 5797

http://www.chethams.org.uk

-- To unsubscribe, email: suse-kde-unsubscribe@suse.com For additional commands, email: suse-kde-help@suse.com Please do not cross-post to suse-linux-e

-- !++ ! Lennart Börjeson ! Partner, Developer ! Cinnober Financial Technology AB ! Industrigatan 2A ! S-112 46 STOCKHOLM ! Sverige/Sweden/Schweden/Suède ! mailto:Lennart.Borjeson@cinnober.com ! phone:+46-8-50304717 ! gsm:+46-70-3394717 ! fax:+46-8-50304701 ! http://www.cinnober.com !--

-- Dr J. Satherley Department of Chemistry University of Liverpool Liverpool Merseyside L69 7ZD United Kingdom Phone: +44 (0) 151 794 3530 Fax: +44 (0) 151 794 3588 Email: js1@liverpool.ac.uk