Bug 153560 - latest kdebase-KDM RPM in supplementary is broken
Summary: latest kdebase-KDM RPM in supplementary is broken
Status: RESOLVED DUPLICATE of bug 153543
: 154283 (view as bug list)
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: KDE (show other bugs)
Version: unspecified
Hardware: 32bit SuSE Linux 10.0
: P5 - None : Major
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-25 21:34 UTC by Forgotten User jq9zgB7cRO
Modified: 2006-03-01 10:30 UTC (History)
2 users (show)

See Also:
Found By: Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
patch for earlykdm script in /etc/init.d (680 bytes, patch)
2006-02-25 23:37 UTC, Ruurd Pels
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Forgotten User jq9zgB7cRO 2006-02-25 21:34:28 UTC
<<snip>>

kdebase3-kdm-3.5.1-27 /etc/init.d/earlykdm hangs
From:
Mark Brand <brandm@xs4all.nl>  (Novell Inc.)
  Date:
Saturday 25 February 2006 12:11:32
  Groups:
opensuse.org.suse-linux.support.updates-patches
Yesterday kdebase3-kdm-3.5.1-27 appeared in the supplementary KDE 3.5.1
repository for Suse 10.0 ix86. On 2 different machines installing this
package prevents KDE from starting. The problem appears to be that
/etc/init.d/earlykdm gets stuck. My first impression is that actually
/sbin/preload gets stuck, but I have not researched this extensively.

Reverting to kdebase3-kdm-3.5.1-18 (from ftp://ftp.kde.org) solves the
problem.

I'm wondering if others have seen this problem and whether Suse is aware
of it.

By the way, some users who find themelves stuck with a system that will
not boot to KDE might appreciate this list of steps to fix the problem:

-Press F2 at the boot menu
-Enter a 3 in the boot options field
-Wait for login prompt
-Log in as root
-Run command:
rpm -Uhv --force
ftp://ftp.kde.org/pub/kde/stable/3.5.1/SuSE/ix86/10.0/kdebase3-kdm-3.5.1-18.i586.rpm
-Run command:
shutdown -r now

<<pins>>

I have followed up with a couple of tips on that post on how to do the
downgrade quicker, pointed out that the rpm command is all one line but
the wrap has split it up, run SuSEconfig and do without a reboot by
just going straight to init 5.

have now had 2 other confirmations of this bug and one saying that his went OK so the score is 3-1 at the moment, I cannot reproduce here as I am using kde-unstable apt repositories for 32+64bit and have no problems
Comment 1 Ruurd Pels 2006-02-25 23:10:37 UTC
Bug shows here too. Experimenting showed me that killing preload will allow the process to continue. So, this is either a bug in preload or a bug in the preloading files.

Experimenting with preload shows me that for some reason it wants to read from the console. Giving it a Ctrl-D finishes it. Examining invocations of preload in other files in /etc/init.d show me that preload seems to be invoked as 

    /sbin/preload < /var/cache/somepreloadcachefile

while in earlykdm it is invoked as 

    /sbin/preload /etc/preload.d/somepreloadfile

Is this correct? FWIW, in the preload cache I find equivalent names for the preload files in /etc/preload.d...
Comment 2 Ruurd Pels 2006-02-25 23:36:49 UTC
OK. Further investigation leads me to believe that this is a bug in the earlykdm script. I verified the working of preload when invoking it as

   /sbin/preload < /var/cache/preload/kdm.XXX.preload

with strace, in which case I see it opening and statting all kinds of files. The funny thing is that in the earlier kdebase3-kdm RPM the earlykdm script is exactly the same. Anyway. It seems to be working if you apply the attached patch to earlykdm, but I'm not 100% sure that it is the correct solution...
Comment 3 Ruurd Pels 2006-02-25 23:37:55 UTC
Created attachment 70315 [details]
patch for earlykdm script in /etc/init.d
Comment 4 Rui Malheiro 2006-02-26 14:16:29 UTC

*** This bug has been marked as a duplicate of 153543 ***
Comment 5 Stephan Kulow 2006-03-01 10:30:37 UTC
*** Bug 154283 has been marked as a duplicate of this bug. ***