Mailinglist Archive: opensuse-kde (235 mails)
| < Previous | Next > |
Re: [suse-kde] Upgrade to KDE 3.3 followed by a crash on starting
- From: Lennart Börjeson <lennart.borjeson@xxxxxxxxxxxx>
- Date: Mon, 13 Sep 2004 12:09:05 +0200
- Message-id: <200409131209.05980.lennart.borjeson@xxxxxxxxxxxx>
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" <lennart.borjeson@xxxxxxxxxxxx>
> To: <suse-kde@xxxxxxxx>
> 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@xxxxxxxxxxxxxxx:
> > Hi Fergus/All
> > Thanks for you comments. I've answered below after your points.
> > Cheers
> > John
> >
> > Quoting Fergus Wilde <fwilde@xxxxxxxxxxxxxxx>:
> > > On Friday 10 September 2004 09:10, js1@xxxxxxxxxxxxxxx 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@xxxxxxxx
> > > For additional commands, email: suse-kde-help@xxxxxxxx
> > > 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@xxxxxxxxxxxx
> ! phone:+46-8-50304717
> ! gsm:+46-70-3394717
> ! fax:+46-8-50304701
> ! http://www.cinnober.com
> !--
--
!++
! Lennart Börjeson
! Partner, Developer
! Cinnober Financial Technology AB
! Industrigatan 2A
! S-112 46 STOCKHOLM
! Sverige/Sweden/Schweden/Suède
! mailto:Lennart.Borjeson@xxxxxxxxxxxx
! phone:+46-8-50304717
! gsm:+46-70-3394717
! fax:+46-8-50304701
! http://www.cinnober.com
!--
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" <lennart.borjeson@xxxxxxxxxxxx>
> To: <suse-kde@xxxxxxxx>
> 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@xxxxxxxxxxxxxxx:
> > Hi Fergus/All
> > Thanks for you comments. I've answered below after your points.
> > Cheers
> > John
> >
> > Quoting Fergus Wilde <fwilde@xxxxxxxxxxxxxxx>:
> > > On Friday 10 September 2004 09:10, js1@xxxxxxxxxxxxxxx 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@xxxxxxxx
> > > For additional commands, email: suse-kde-help@xxxxxxxx
> > > 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@xxxxxxxxxxxx
> ! phone:+46-8-50304717
> ! gsm:+46-70-3394717
> ! fax:+46-8-50304701
> ! http://www.cinnober.com
> !--
--
!++
! Lennart Börjeson
! Partner, Developer
! Cinnober Financial Technology AB
! Industrigatan 2A
! S-112 46 STOCKHOLM
! Sverige/Sweden/Schweden/Suède
! mailto:Lennart.Borjeson@xxxxxxxxxxxx
! phone:+46-8-50304717
! gsm:+46-70-3394717
! fax:+46-8-50304701
! http://www.cinnober.com
!--
| < Previous | Next > |