https://bugzilla.novell.com/show_bug.cgi?id=743954 https://bugzilla.novell.com/show_bug.cgi?id=743954#c0 Summary: Cannot create a new feature in Konqueror (WebKit) Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: x86-64 OS/Version: openSUSE 12.1 Status: NEW Severity: Major Priority: P5 - None Component: openFATE AssignedTo: tschmidt@suse.com ReportedBy: giecrilj@stegny.2a.pl QAContact: freitag@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0.1) Gecko/20100101 Firefox/9.0.1 The [Create feature] button does not work in WebKit. Reproducible: Always Steps to Reproduce: 1. Tell Konqueror to create a new feature [1]. 2. Fill the form with the following data: Title:: Better GUI for ENABLE_SYSRQ Product:: openSUSE Distribution Description:: Currently, YaST2 allows to specify a number for sysconfig kernel ENABLE_SYSRQ. It should provide check boxes for individual flags instead. In the mean time, The following script will unscramble the current setting: let R="$(>=1)&1' && echo $K done fi The following code will print the default setting: let L=2 'K=L<<1' 'D=K<<1' 'C=D<<1' 'M=C<<1' 'G=M<<1' 'B=G<<1' 'N=B<<1' 'R=C|M|B' echo $R Use case:: The operator observes that the system becomes unresponsive because a process (such as gdb, which can easily slip out of control) is using too much RAM. The X server is not responding because of that. The operator wants to configure the kernel so that it can use the keyboard shortcut [Alt SysRq F] to kill the memory hog. Why:: Because manual scrambling and unscrambling is inconvenient. Manual killing of excessive processes is easier than restarting the whole system by means of [Ctrl Alt F1] [Ctrl Alt Delete], and may save the operator some data loss. 3. Press [Create feature]. Actual Results: 3. Expected Results: 3. Let a new feature be created. Workaround: Repeat these steps in Firefox. ___ [1] https://features.opensuse.org/feature/new? > -- 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.