[Bug 746595] New: KBD_NUMLOCK="yes" in /etc/sysconfig/keyboard does not work under systemd init
https://bugzilla.novell.com/show_bug.cgi?id=746595 https://bugzilla.novell.com/show_bug.cgi?id=746595#c0 Summary: KBD_NUMLOCK="yes" in /etc/sysconfig/keyboard does not work under systemd init Classification: openSUSE Product: openSUSE 12.2 Version: Factory Platform: PC OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: mrmazda@earthlink.net QAContact: qa@suse.de Found By: --- Blocker: --- y2logs (bug 746594): http://bugzilla.novell.com/attachment.cgi?id=475750 This started in 12.1. see: https://bugzilla.novell.com/show_bug.cgi?id=720486#c11 To reproduce: 1-install 12.2M1/KDE with default init packages 2-set KBD_NUMLOCK="yes" in /etc/sysconfig/keyboard 3-reboot Actual results: 1-NUM state is off on tty[1-6] Expected results: 1-NUM state is on on tty[1-6] -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c
zj jia
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c1
--- Comment #1 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c2
--- Comment #2 from Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c3
Wolfgang Rosenauer
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c4
Wolfgang Rosenauer
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c5
--- Comment #5 from Stanislav Brabec
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c6
--- Comment #6 from Stanislav Brabec
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c7
Jeff Mahoney
Confirming "rm /lib/systemd/system/kbd.service" as a quick work-around. I do not see any apparent regressions.
I believe this means it runs the old kdb script, right? Fine, kill the kdb.service file from the systemd package. This habit of ignoring regressions because they don't fit the systemd model needs to stop. This is a feature openSUSE has had since before there was an openSUSE and the fact that systemd doesn't honor it is a regression. I'd imagine the numlock enable-disable feature works on non-x86 systems as well as x86 systems that don't have a BIOS in which to make that determination. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c8
--- Comment #8 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c9
--- Comment #9 from Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c10
--- Comment #10 from Jeff Mahoney
I don't agree with you, Jeff : kernel should keep the numlock state when it starts and we shouldn't have to read BIOS state with hwinfo to workaround it.
This is probably true, but is a separate issue. My point is that there are systems that don't have a numlock boot option and that had the ability to set the default are not longer having it honored. Also, it's a pretty unreasonable expectation to require users that want a different default to change their BIOSes. We should honor if it's set and override it if it's set in software. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c11
--- Comment #11 from Stanislav Brabec
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c12
--- Comment #12 from Stanislav Brabec
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c13
--- Comment #13 from Stanislav Brabec
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c14
Stanislav Brabec
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c15
--- Comment #15 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c16
Stanislav Brabec
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c17
Jeff Mahoney
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c18
--- Comment #18 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c19
Stanislav Brabec
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c20
--- Comment #20 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c21
--- Comment #21 from Wolfgang Rosenauer
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c22
--- Comment #22 from Stanislav Brabec
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c23
--- Comment #23 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c24
--- Comment #24 from Stanislav Brabec
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c25
--- Comment #25 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c26
--- Comment #26 from Stanislav Brabec
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c27
--- Comment #27 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c28
Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c29
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c30
--- Comment #30 from Stanislav Brabec
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c31
--- Comment #31 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c32
--- Comment #32 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c33
--- Comment #33 from Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c34
--- Comment #34 from Stanislav Brabec
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c35
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c36
--- Comment #36 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c37
--- Comment #37 from Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c38
Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c39
Frederic Crozat
and the reason why 8 of my 10 12.2 installations and all except 1 of my dozen or so 12.1 installations default to sysvinit-init boot. Systemd would get a whole lot more testing here, and a whole lot less attention paid to sysvinit bugs, if this actually got fixed.
please refrain from such comments in bugzilla in the future. I make your message more difficult to understand and doesn't give incentive to anybody on fixing bugs. Stay focused on the bug itself and nothing else. If you don't say which package of systemd is installed on your system, it is impossible to guess if you have a version which is supposed to contain the fix or not and how you are testing exactly and what is exactly broken. So far, I've tested on Factory, with systemd-44-5.1 (and on 12.1 maintenance update, they are similar) and numlock is correctly set for X session. For tty, numlock is enabled correctly but the leds itself doesn't seem to be set properly, as stanislav noted in comment34. When starting in runlevel 3 directly, it looks like the numlock is kind of set (login complains about "numlock is off") but neither keyboard nor leds are set properly. Starting X ensures leds is set properly. Stanislav, it looks like something is missing, compared to sysvinit, in the runlevel 3 setup. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c40
--- Comment #40 from Felix Miata
If you don't say which package of systemd is installed on your system, it is impossible to guess if you have a version which is supposed to contain the fix or not and how you are testing exactly and what is exactly broken.
# rpm --changelog -q systemd | head ... * Fri Apr 20 2012 sbrabec@suse.cz - Implemented SUSE specific sysconfig numlock logic (bnc#746595). ... Don't you think it safe to assume when someone complains of "10 ... systems updated from Factory repo as late as" 6 weeks after a supposed fix is reported that some version containing that "fix" had been installed?
From the host that's booted ATM: # rpm -qa | grep systemd systemd-44-8.1.i586
For the record, these are the 12.2M1 hosts this bug affects (100% of my Factory installations), with their latest (all June) 'zypper dup' dates: gx28b 02 m7ncd 03 big31 06 gx280 07 gx27b 08 kt880 08 s2846 09 gx110 09 t2240 10 gx62b 11 kt400 11 gx260 11 I'm going to pass on booting the other 11 right now just to gather their systemd versions to report here. I test by booting, 39 times out of 40, directly into runlevel 3, where everything is virtually guaranteed to be big enough to be legible, unlike typical X defaults. I try to login, and get login failure because I start using numpad keystrokes for password entry before looking at the screen after the switch from tty1 to tty2 or tty3. Sorry I forgot to include the 3 tidbit in comment 0. I wouldn't know if this had any effect on runlevel 5, as I always set numlock=On in kdmrc before first instance of runlevel 5 is initiated after an installation. What exactly is broken remains as exactly stated in comment 0, as login confirms with "Hint: Num Lock is off". -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c41
Stanislav Brabec
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c42
--- Comment #42 from Stanislav Brabec
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c43
--- Comment #43 from Stanislav Brabec
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c44
--- Comment #44 from Stanislav Brabec
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c45
Felix Miata
http://download.opensuse.org/repositories/home:/sbrabec:/branches:/Base:/Sys...
I installed these on 5 systemd-sysvinit-equipped systems zypper dup'd from Factory repos on or after 28 June. Success rate: 60%: one failure (=NUM off on all ttys from the time kernel turns off BIOS=ON setting) on a 1133MHz PIII (Dell BIOS), the other a 2.8GHz P4 (AMI BIOS). Successes were on 2 P4s and one Athlon. All use the very same IBM brand PS/2-connected keyboard. What info do I need to collect on the "failure" systems? FWIW, one it succeeded on also has KDE3 installed, and in its Konsole, keyboard repeat rate went to virtual infinity, making it nearly impossible to type only one of any character, including BS. In the other two "successes", keyboard rate in Konsole 4 is normal. On the failure, I exited KDE, deleted the home directories containing KDE settings, restarted KDE, reset my preferences, and keyboard was restored to normal behavior, even after KDE session shutdown and restart. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c46
--- Comment #46 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c47
Stanislav Brabec
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c48
--- Comment #48 from Stanislav Brabec
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c49
--- Comment #49 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c50
--- Comment #50 from Felix Miata
1. See "systemd-analyze plot >boot-numlock-failed.svg" output.
???: Traceback (most recent call last): File "/usr/bin/systemd-analyze", line 113, in <module> import cairo, os ImportError: No module named cairo -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c51
--- Comment #51 from Felix Miata
I have a (probably ugly) quick hack: Edit /lib/systemd/system/udev-trigger.service and add systemd-vconsole-setup.service to the After= list.
Success on PIII host gx150. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c52
--- Comment #52 from Frederic Crozat
(In reply to comment #47)
1. See "systemd-analyze plot >boot-numlock-failed.svg" output.
???: Traceback (most recent call last): File "/usr/bin/systemd-analyze", line 113, in <module> import cairo, os ImportError: No module named cairo
install python-cairo -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c53
--- Comment #53 from Felix Miata
you can try by adding something like: After=dev-tty1.device dev-tty2.service
to systemd-vconsole-setup.service
the following does not succeed on 2.8GHz P4 host hs80e: # systemd-vconsole-setup.service [Unit] Description=Setup Virtual Console DefaultDependencies=no Conflicts=shutdown.target After=systemd-readahead-collect.service systemd-readahead-replay.service dev-tty1.device dev-tty2.service Before=sysinit.target shutdown.target [Service] Type=oneshot RemainAfterExit=yes ExecStart=/lib/systemd/systemd-vconsole-setup <EOF> But, comment 51 does also apply to host hs80e. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c54
--- Comment #54 from Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c55
--- Comment #55 from Stanislav Brabec
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c56
--- Comment #56 from Stanislav Brabec
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c57
Stanislav Brabec
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c58
Stanislav Brabec
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c59
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c60
Stanislav Brabec
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c61
Stanislav Brabec
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c62
--- Comment #62 from Frederic Crozat
By the way, one of my colleagues accepted a HackWeek project that would make possible to replace slow and complex hwinfo --bios | grep "Num Lock:" by a simple utility that only checks NumLock. I guess that with that tool it would be possible to implement the feature in the way acceptable for upstream.
Well, if he can get this code to be in the kernel directly, it could be a nice project too ;) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c63
--- Comment #63 from Felix Miata
Well, if he can get this code to be in the kernel directly, it could be a nice project too ;)
Don't the kernel devs have an unofficial "thou shalt pay no mind to the BIOS NUM setting" policy? Why else hasn't the the kernel been handling this since the beginning of time? What are Mandriva & Mageia doing differently from openSUSE WRT NUM state on ttys? On those, NUM seems handled automatically, with no string "NUM" anywhere in their /etc/sysconfig/keyboards, and nothing that comes to my attention in their kernel configs. Once I've turned it on in any tty in either of those, that's where it stays across boots for that tty. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c64
--- Comment #64 from Stanislav Brabec
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c65
--- Comment #65 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c66
--- Comment #66 from Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c67
Stanislav Brabec
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c68
Felix Miata
Could you check systemd-analyze plot graph.
Host gx62b: ???: Traceback (most recent call last): File "/usr/bin/systemd-analyze", line 3, in <module> import dbus, sys ImportError: No module named dbus Host gx150: Does by a very small amount, less than the width of red for udev-trigger.service.
Does your systemd changelog include: * Fri Jul 20 2012 sbrabec@suse.cz - Fix NumLock detection/set race condition (bnc#746595#c47).
Host gx62b: It didn't. After installing the comment 44 package I locked it pending BS backlog reduction and hadn't unset the lock. Now with systemd-44-10.1.1 NUM is working. Host gx150: NUM is working now. Is http://lists.opensuse.org/opensuse-factory/2012-09/msg00108.html related to this racing? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=746595 https://bugzilla.novell.com/show_bug.cgi?id=746595#c Bug 746595 depends on bug 769423, which changed state. Bug 769423 Summary: setleds +num call in the systemd only sets leds, not NumLock http://bugzilla.novell.com/show_bug.cgi?id=769423 What |Old Value |New Value ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c69
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c70
Stanislav Brabec
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c71
--- Comment #71 from Stanislav Brabec
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c72
--- Comment #72 from Stanislav Brabec
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c73
--- Comment #73 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c74
Stanislav Brabec
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c75
--- Comment #75 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c76
--- Comment #76 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c77
--- Comment #77 from Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c78
--- Comment #78 from Stanislav Brabec
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c79
--- Comment #79 from Stanislav Brabec
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c80
Stanislav Brabec
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c81
--- Comment #81 from Stanislav Brabec
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c82
--- Comment #82 from Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=746595
https://bugzilla.novell.com/show_bug.cgi?id=746595#c83
--- Comment #83 from Stanislav Brabec
participants (1)
-
bugzilla_noreply@novell.com