https://bugzilla.novell.com/show_bug.cgi?id=335267
Summary: /etc/init.d/kbd: setfont: putfont: 256,8x16: failed: -1 Product: openSUSE 10.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: ensonic@sonicpulse.de QAContact: qa@suse.de Found By: ---
OpenSuse 10.3 upgraded from 10.2, 10.1 ... etc
Loading console font lat9w-16.psfu -m trivial G0:loadable setfont: putfont: 256,8x16: failed: -1 putfont: KDFONTOP: Invalid Argument
this causes /etc/init.d/kbd to fail to load Simillar report here too: http://forums.suselinuxsupport.de/index.php?s=388da10dedb07ea5d7ec84f2649b41...
https://bugzilla.novell.com/show_bug.cgi?id=335267
Cyril Hrubis chrubis@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |jw@novell.com
https://bugzilla.novell.com/show_bug.cgi?id=335267#c1
Juergen Weigert jw@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED
--- Comment #1 from Juergen Weigert jw@novell.com 2007-10-19 12:26:31 MST --- This does not happen with a new installation of 10.3 I'll test the update from 10.2 case.
What is the impact of this? Does it hinder KDM?
https://bugzilla.novell.com/show_bug.cgi?id=335267#c2
Juergen Weigert jw@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |ensonic@sonicpulse.de
--- Comment #2 from Juergen Weigert jw@novell.com 2007-10-19 13:09:59 MST --- It does not happen to me. setfont is happy after 10.2 -> 10.3 update.
The code changed betwen 10.2 and 10.3, we removed some compatibility cruft with old kernels during bug #302010.
Could you please try if the old kbd package from 10.2 behaves the same on the updated 10.3 box? http://download.opensuse.org/distribution/10.2/repo/oss/suse/i586/kbd-1.12-8... http://download.opensuse.org/distribution/10.2/repo/oss/suse/x86_64/kbd-1.12...
https://bugzilla.novell.com/show_bug.cgi?id=335267#c3
--- Comment #3 from Stefan Kost ensonic@sonicpulse.de 2007-10-19 13:38:44 MST --- Sometimes the keyboard is dead in GDM. Restarting GDM or /etc/init.d/kbd does not help. Unfortunately the error message is not really helpful to me. I'll llok at the init scipt tomorrow to see what it does and check running the stuff step by step.
Regarding comment #2 - do you want me to temporary downgrade the kdb package?
https://bugzilla.novell.com/show_bug.cgi?id=335267#c4
--- Comment #4 from Stefan Kost ensonic@sonicpulse.de 2007-10-20 03:59:38 MST --- I've found the cause - I added an echo of the executed commands and a -v to the actual command: echo /bin/setfont -C $tty $CONSOLE_FONT $UMAP $SMAP /bin/setfont -v -C $tty $CONSOLE_FONT $UMAP $SMAP
There is a race of starting /etc/init.d/xdm. It fails for "tty7". The xdm script should probably list kbd under "Required-Start" instead of "Should-Start" or alternatively the kdb script should not fail when it fails for one of the ttys.
https://bugzilla.novell.com/show_bug.cgi?id=335267#c5
--- Comment #5 from Stefan Kost ensonic@sonicpulse.de 2007-10-20 04:05:43 MST --- Oh, another workaround is to edit /etc/sysconfig/keyboard KBD_TTY="tty1 tty2 tty3 tty4 tty5 tty6 tty10" on my system it was set to: KBD_TTY="tty1 tty2 tty3 tty4 tty5 tty6 tty7 tty8 tty9 tty10 tty12 tty13 tty14 tty15 tty16 tty17 tty18 tty19 tty20"
no idea where this setting comes from. I haven't touched this for sure.
https://bugzilla.novell.com/show_bug.cgi?id=335267#c6
Stefan Kost ensonic@sonicpulse.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|ensonic@sonicpulse.de |
--- Comment #6 from Stefan Kost ensonic@sonicpulse.de 2007-10-20 12:56:26 MST --- Above info is enough for a fix. (Remove needinfo flag).
https://bugzilla.novell.com/show_bug.cgi?id=335267#c7
--- Comment #7 from Juergen Weigert jw@novell.com 2007-10-22 04:24:09 MST --- Thanks Stefan! /etc/sysconfig/keyboard contains KBD_TTY="tty1 tty2 tty3 tty4 tty5 tty6" on my test machine. This is why I did not see the error. I am surprised you have a much longer list (including tty7) there.
We'd prefer to have xdm and kbd run in parallel, for fastest start-up. I will investigate, where the KBD_TTY setting comes from.
https://bugzilla.novell.com/show_bug.cgi?id=335267#c8
--- Comment #8 from Stefan Kost ensonic@sonicpulse.de 2007-10-22 04:54:55 MST --- I have to say that I am upgrading my system since 6.4. So it might be hard to tell where it came from. Two things: * shouldn't tty10 be on the list? * wouldn't it be better to continue if one on the setfont calls fail (or continue if atleast on of them succeeded).
https://bugzilla.novell.com/show_bug.cgi?id=335267#c9
Juergen Weigert jw@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |kq8z67r6309fo9001@sneakemail.com
--- Comment #9 from Juergen Weigert jw@novell.com 2007-10-22 12:20:53 MST --- *** Bug 331529 has been marked as a duplicate of this bug. ***
https://bugzilla.novell.com/show_bug.cgi?id=331529
https://bugzilla.novell.com/show_bug.cgi?id=335267#c10
Ulrich Windl Ulrich.Windl@rz.uni-regensburg.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |Ulrich.Windl@rz.uni-regensburg.de
--- Comment #10 from Ulrich Windl Ulrich.Windl@rz.uni-regensburg.de 2007-11-12 01:38:40 MST --- FYI: The problem appeared first here after having installed the most recent online updates (later than Friday 11:00 UTC). Before that that problem was not there (in 10.3). The machine had also been upgraded from 10.2... On the race of gdb: I noticed that gdm is started even before the network or clock is set up. Maybe a bit too early...
https://bugzilla.novell.com/show_bug.cgi?id=335267
User dieter.jurzitza@t-online.de added comment https://bugzilla.novell.com/show_bug.cgi?id=335267#c11
Dieter Jurzitza dieter.jurzitza@t-online.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dieter.jurzitza@t-online.de
--- Comment #11 from Dieter Jurzitza dieter.jurzitza@t-online.de 2008-04-16 02:36:09 MST --- I see a similar issue here. Asus board, NVIDIA graphics card. I did not upgrade my system but did a fresh install of opensuse 10.3, 64 Bit system. The entries regarding the tty's are correct - tty1 to tty6.
I have tried to find a correlation between this problem and the starting of xdm, but in vain. So I patched the file /etc/init.d/kbd: ******************************************************************** --- kbd.original 2007-09-21 21:29:32.000000000 +0200 +++ kbd 2008-04-16 06:53:48.000000000 +0200 @@ -31,6 +31,10 @@ # Description: Keyboard settings (don't disable!) ### END INIT INFO
+DONE=10 +WAIT=30 +LOGFILE="/tmp/setfontlog_KBD" + . /etc/rc.status . /etc/sysconfig/console . /etc/sysconfig/keyboard @@ -42,6 +46,7 @@ LOCALE_CHARMAP=`locale charmap` LC_ALL=POSIX
+ MACHINE=`/bin/uname -m 2> /dev/null` if [ "$MACHINE" = "sparc" -o "$MACHINE" = "sparc64" ]; then # Test if we have a serial console. @@ -240,10 +245,10 @@ # this means that initialization was already done. # don't do it twice unless forced, it may annoy xdm and # produce lots of error messages. - test -s /var/run/keymap && exit 0 + test -s /var/run/keymap && exit 0 ;; esac - + echo "NEUANFANG-KBD" >> ${LOGFILE}
if test -z "$KEYTABLE"; then echo "No keyboard map to load" @@ -409,9 +414,24 @@ # The chvt is not needed for SuSE kernels test "$NON_SUSE_KERNEL" != "yes" || chvt ${tty#*tty}
- /bin/setfont -C $tty $CONSOLE_FONT $UMAP $SMAP - rc_status - + i=0 + while [ "${i}" != "${DONE}" ]; do + i=`expr ${i} + 1` + echo "/bin/setfont -v -C $tty $CONSOLE_FONT $UMAP $SMAP" >> ${LOGFILE} 2>&1 + /bin/setfont -v -C $tty $CONSOLE_FONT $UMAP $SMAP >> ${LOGFILE} 2>&1 + if [ "$?" != "0" ]; then + sleep ${WAIT} + echo "KBD - Schleife ${i} mit Fehler!" >> ${LOGFILE} + echo "KBD-secondloop waiting ${i}*${WAIT} seconds"
${LOGFILE}
+ else + break + fi + done + if [ ${i} == "${DONE}" ]; then + echo $rc_failed + else + echo "KBD - nach ${i} Schleifen ohne Fehler durchgelaufen!" >> ${LOGFILE} + fi echo -en "$CONSOLE_MAGIC" > $tty done test "$NON_SUSE_KERNEL" != "yes" || chvt $FGCONS
******************************************************************** What I observe from this: things work now. Typically the wait loop is entered due to an error occuring, but after a certain delaytime, the commands are processed and everything completes without error. Please see the example of a logfile setfontlog_KBD attached.
So, IMHO there is something happening that makes /bin/setfont inoperable that can be circumvented by simply waiting sufficiently long.
So, probably this helps getting a better understanding of what is going on here.
Furthermore I add dmesg-output and lspci-output for your information.
Take care
Dieter Jurzitza
https://bugzilla.novell.com/show_bug.cgi?id=335267
User dieter.jurzitza@t-online.de added comment https://bugzilla.novell.com/show_bug.cgi?id=335267#c12
--- Comment #12 from Dieter Jurzitza dieter.jurzitza@t-online.de 2008-04-16 02:37:18 MST --- Created an attachment (id=208224) --> (https://bugzilla.novell.com/attachment.cgi?id=208224) dmesg-output - FYI only
https://bugzilla.novell.com/show_bug.cgi?id=335267
User dieter.jurzitza@t-online.de added comment https://bugzilla.novell.com/show_bug.cgi?id=335267#c13
--- Comment #13 from Dieter Jurzitza dieter.jurzitza@t-online.de 2008-04-16 02:39:11 MST --- Created an attachment (id=208227) --> (https://bugzilla.novell.com/attachment.cgi?id=208227) Output of the /etc/init.d/kbd - file using my patch when the issue occurs
You have to compare this with the patch to kbd I applied - nothing magic here. After waiting long enough, things seem to work flawlessly. Probably some relation with the nvidia graphics driver?
https://bugzilla.novell.com/show_bug.cgi?id=335267
User dieter.jurzitza@t-online.de added comment https://bugzilla.novell.com/show_bug.cgi?id=335267#c14
--- Comment #14 from Dieter Jurzitza dieter.jurzitza@t-online.de 2008-04-16 02:39:55 MST --- Created an attachment (id=208229) --> (https://bugzilla.novell.com/attachment.cgi?id=208229) lspci - output - FYI only
https://bugzilla.novell.com/show_bug.cgi?id=335267
User dieter.jurzitza@t-online.de added comment https://bugzilla.novell.com/show_bug.cgi?id=335267#c15
--- Comment #15 from Dieter Jurzitza dieter.jurzitza@t-online.de 2008-04-16 02:43:47 MST --- Created an attachment (id=208232) --> (https://bugzilla.novell.com/attachment.cgi?id=208232) This is the patch if someone does not like to type things manually ...
https://bugzilla.novell.com/show_bug.cgi?id=335267
User Ulrich.Windl@rz.uni-regensburg.de added comment https://bugzilla.novell.com/show_bug.cgi?id=335267#c16
--- Comment #16 from Ulrich Windl Ulrich.Windl@rz.uni-regensburg.de 2008-04-16 03:47:29 MST --- What surprised me in 10.3 is that gdm is started even before the network is up. Also NTP is run before the network is up (It's run again when the network is up). I wonder whether process dependencies are correctly configured AND considered. Maybe instead of a sleep and retry for the kbd problem, proper ordering of the start scripts would fix the problem (A guess, just a guess).
https://bugzilla.novell.com/show_bug.cgi?id=335267
User dieter.jurzitza@t-online.de added comment https://bugzilla.novell.com/show_bug.cgi?id=335267#c17
--- Comment #17 from Dieter Jurzitza dieter.jurzitza@t-online.de 2008-04-16 06:59:10 MST --- Hi Ulrich, I totally agree with your arguments. My point is to find out _what_ is causing /bin/setfont to fail. Knowing this I guess it would be much easier to find a fix. This is why I posted "my" solution, so someone with more insight could probably have a look and find out what causes setfont to fail - what really makes me wonder is that it takes more than a minute to get this into proper operation (2 times 30s sleep after starting /etc/init.d/kbd is quite something ...) Take care
Dieter
https://bugzilla.novell.com/show_bug.cgi?id=335267
User dieter.jurzitza@t-online.de added comment https://bugzilla.novell.com/show_bug.cgi?id=335267#c18
--- Comment #18 from Dieter Jurzitza dieter.jurzitza@t-online.de 2008-04-17 07:10:50 MST --- And another one: today I found a situation where even "waiting forever" does not help, the waitloop is terminated after 10x30sx6tty's without success. So, a big help would be if someone with deeper insight could support me in testing what is actually failing - the font files are there, they are readable, so, this cannot cause this problem. Thank you for looking into this, take care
Dieter
https://bugzilla.novell.com/show_bug.cgi?id=335267
User dieter.jurzitza@t-online.de added comment https://bugzilla.novell.com/show_bug.cgi?id=335267#c19
--- Comment #19 from Dieter Jurzitza dieter.jurzitza@t-online.de 2008-04-23 04:55:06 MST --- Last week I disabled earlyxdm from starting. _That_ really seems to fix things. In contrast to before I did not see one single failure or even wait in the delayloop I introduced in /etc/init.d/kbd (see above).
So, starting xdm too early seems to introduce problems on my computer - the question arises how many seconds can be saved by starting earlyxdm and why the issues pop up.. The problem is not solved IMHO, but as a workaround I can recommend uninstalling the package "preload". Take care
Dieter Jurzitza
https://bugzilla.novell.com/show_bug.cgi?id=335267
User coolo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=335267#c20
Stephan Kulow coolo@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |marvin24@gmx.de
--- Comment #20 from Stephan Kulow coolo@novell.com 2008-05-21 06:17:12 MST --- *** Bug 392669 has been marked as a duplicate of this bug. ***
https://bugzilla.novell.com/show_bug.cgi?id=392669
https://bugzilla.novell.com/show_bug.cgi?id=335267
User coolo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=335267#c21
Stephan Kulow coolo@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |abittner@stud.fh-heilbronn.de
--- Comment #21 from Stephan Kulow coolo@novell.com 2008-06-24 03:19:12 MDT --- *** Bug 401673 has been marked as a duplicate of this bug. ***
https://bugzilla.novell.com/show_bug.cgi?id=401673
https://bugzilla.novell.com/show_bug.cgi?id=335267
User mmarek@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=335267#c22
Michal Marek mmarek@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jw@novell.com AssignedTo|jw@novell.com |mmarek@novell.com Status|ASSIGNED |NEW
--- Comment #22 from Michal Marek mmarek@novell.com 2008-09-03 09:46:18 MDT --- -> new maintainer
https://bugzilla.novell.com/show_bug.cgi?id=335267
Michal Marek mmarek@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium
https://bugzilla.novell.com/show_bug.cgi?id=335267
User mmarek@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=335267#c23
Michal Marek mmarek@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |dieter.jurzitza@t-online.de
--- Comment #23 from Michal Marek mmarek@novell.com 2008-09-26 09:15:34 MDT --- (In reply to comment #13 from Dieter Jurzitza)
Created an attachment (id=208227)
--> (https://bugzilla.novell.com/attachment.cgi?id=208227) [details]
Output of the /etc/init.d/kbd - file using my patch when the issue occurs
Interesting - do you only see setfont errors on the first console (/bin/setfont -v -C /dev/tty1) or is it random?
All: 1) Does the problem occur on 11.0 or Factory? 2) Does it persist if you disable the earlyxdm init script (insserv -r earlyxdm)?
https://bugzilla.novell.com/show_bug.cgi?id=335267
User dieter.jurzitza@t-online.de added comment https://bugzilla.novell.com/show_bug.cgi?id=335267#c24
--- Comment #24 from Dieter Jurzitza dieter.jurzitza@t-online.de 2008-09-28 09:02:25 MDT --- Hi Michal, I did not install 11.0 because this is a machine I use for daily work - and new installations usually come with other issues, so I am staying with 10.3 for now. What ought to be clear from my previous comments is the fact that disabling earlyxdm fixes everything. I haven't had a single issue with setfont since I disabled earlyxdm. I can try to reenable earlyxdm and try to use the /bin/setfont command as described by you in case the error occurs from different tty's - would that be a help for you? Didn't test that so far. Give me your opinion on this, take care
Dieter Jurzitza
https://bugzilla.novell.com/show_bug.cgi?id=335267
User marvin24@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=335267#c25
Marvin FourtyTwo marvin24@gmx.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|dieter.jurzitza@t-online.de |
--- Comment #25 from Marvin FourtyTwo marvin24@gmx.de 2008-10-07 06:11:18 MDT --- Problem also exists in 11.0. Message is printed for all initialized tty's (1-6) on the first console. Removing earlyxdm solves the problem here. Will try factory later.
https://bugzilla.novell.com/show_bug.cgi?id=335267
User dieter.jurzitza@t-online.de added comment https://bugzilla.novell.com/show_bug.cgi?id=335267#c26
--- Comment #26 from Dieter Jurzitza dieter.jurzitza@t-online.de 2008-10-08 12:39:38 MDT --- Ok. This tells me two things:
1.) I need not verify that in 10.3 because it persists in 11.0, 2.) earlyxdm is a showstopper in this regard for some reason.
So, as I suggested above (#18): someone with a deeper insight what earlyxdm can do that disturbes setfont is mandatory. I am willing to test things but I need guidance.
If you do not have time left for that: what time benefit arises from starting earlyxdm? Maybe it would be a good idea to stop starting earlyxdm if it is not save and no one at Novell has the time to fix the issues caused by that?
Take care
Dieter Jurzitza
https://bugzilla.novell.com/show_bug.cgi?id=335267
User dieter.jurzitza@t-online.de added comment https://bugzilla.novell.com/show_bug.cgi?id=335267#c27
Dieter Jurzitza dieter.jurzitza@t-online.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|Basesystem |X.Org Product|openSUSE 10.3 |openSUSE 11.1 Target Milestone|--- |Final
--- Comment #27 from Dieter Jurzitza dieter.jurzitza@t-online.de 2008-12-27 08:50:33 MST --- Just to let you know: this problem still exists in openSUSE 11.1, and the solution is the very same: kick out earlyxdm and things will work flawlessly.
And the conclusion in #26 remains valid: someone with a deeper insight should look into the bug as my possibilities are restricted to testing and further debugging.
I know now two different computers I can access that exhibit the very same problem, so it is nothing exotic IMHO.
Thank you, take care
Dieter Jurzitza
https://bugzilla.novell.com/show_bug.cgi?id=335267
User jasondamfus@gmx.net added comment https://bugzilla.novell.com/show_bug.cgi?id=335267#c28
Jason Damfus jasondamfus@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jasondamfus@gmx.net
--- Comment #28 from Jason Damfus jasondamfus@gmx.net 2009-02-13 05:32:12 MST --- The mentioned solution does not work for me. I also upgraded a fresh system from 10.3 to 11.1. Stopping/Deactivating earlyxdm does not show any change. A workaround for me is booting inti runlevel 3, then manualy change into runlevel 5. So the problem eventually seems to be an issue of something starting to early and interfering with the x-server/kde-interface.
(I can't tell if the problem would exist if I had installed 11.1 in the first place because for some reason the 11.x install-kernels won't load on my machine)
I really hope someone finds a solution and creates a bugfix!
https://bugzilla.novell.com/show_bug.cgi?id=335267
User dieter.jurzitza@t-online.de added comment https://bugzilla.novell.com/show_bug.cgi?id=335267#c29
--- Comment #29 from Dieter Jurzitza dieter.jurzitza@t-online.de 2009-02-14 02:28:34 MST --- Hi Jason, would you try to uninstall package preload? rpm -e preload - does not generate issues but stops all "early load" stuff - just for testing? Thank you, take care
Dieter Jurzitza
https://bugzilla.novell.com/show_bug.cgi?id=335267
User jasondamfus@gmx.net added comment https://bugzilla.novell.com/show_bug.cgi?id=335267#c30
--- Comment #30 from Jason Damfus jasondamfus@gmx.net 2009-02-15 15:03:02 MST --- Hello Dieter, i tried booting directly into runlevel 5 after uninstalling 'preload'; it did not solve the problem, although the x-server now crashes a few seconds later. (The screen changes from console to x-server twice before finally ending at the console-screen; interestingly without any error message) Also I found out today that i can be 'too fast' entering runlevel 5 manually.
Thank you for the fast answer!
JD
https://bugzilla.novell.com/show_bug.cgi?id=335267
User dieter.jurzitza@t-online.de added comment https://bugzilla.novell.com/show_bug.cgi?id=335267#c31
--- Comment #31 from Dieter Jurzitza dieter.jurzitza@t-online.de 2009-02-15 22:55:54 MST --- Hi Jason, so far so bad. Have you tried to stop your system from booting the init-scripts in parallel? Try (I have already done so) to set RUN_PARALLEL in the sysconfig-editor to "no".
If you want to set it manually you can directly edit /etc/sysconfig/boot.
After that, restart and look what happens. This is not to say that this solves the issue, but this is an attempt to reduce the amount of possibilities that could cause problems.
Hope this helps, take care
Dieter Jurzitza
https://bugzilla.novell.com/show_bug.cgi?id=335267
User jasondamfus@gmx.net added comment https://bugzilla.novell.com/show_bug.cgi?id=335267#c32
--- Comment #32 from Jason Damfus jasondamfus@gmx.net 2009-03-02 02:12:27 MST --- Just to let you know: To me the Problem seems to be related to some 'special' Hardware/Bios-setups. I finally found a way to install opensuse 11.1 directly - but the problem still exists: there is no failure-message, but still the x-server won't start automatically. My guess is that old hardware and a slow CPU may be the cause.
JD
https://bugzilla.novell.com/show_bug.cgi?id=335267
User Ulrich.Windl@rz.uni-regensburg.de added comment https://bugzilla.novell.com/show_bug.cgi?id=335267#c33
--- Comment #33 from Ulrich Windl Ulrich.Windl@rz.uni-regensburg.de 2009-03-02 03:12:11 MST --- In reply to comment #32: [...]
automatically. My guess is that old hardware and a slow CPU may be the cause.
Having started a program that runs over 7000 threads on an older laptop, causing a load of > 200 while keeping the system responsive, I'd say there are no slow CPUs, but only race conditions. And "sleep" is no mechanism for process synchronization.
-
bugzilla_noreply＠novell.com