abrt 1.1.0 detected a crash.
cmdline: python /usr/share/system-config-kdump/system-config-kdump.py
reason: system-config-kdump.py:1510:cmdline_changed:ValueError: invalid literal for float(): aut
release: Red Hat Enterprise Linux release 6.0 Beta (Santiago)
system-config-kdump.py:1510:cmdline_changed:ValueError: invalid literal for float(): aut
Traceback (most recent call last):
File "/usr/share/system-config-kdump/system-config-kdump.py", line 1523, in reset_cmdline
File "/usr/share/system-config-kdump/system-config-kdump.py", line 1510, in cmdline_changed
ValueError: invalid literal for float(): aut
Local variables in innermost frame:
gtk_entry: <gtk.Entry object at 0x1d454b0 (GtkEntry at 0x1e60510)>
self: <__main__.MainWindow instance at 0x1c4b7a0>
How to reproduce
1.refreshed frub kernel line
3.inserter 3-4 times password
I thought s-c-kdump is closed but this crash appeared after few seconds.
Created attachment 413070 [details]
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
I'm not able to reproduce the bug with step from comment #1. But I reproduced similar issue when I manually changed command line options on Expert settings card. I changed from "crashkernel=192M" to "crashkernel=aa192M" and change focus to another widget, then the error appears in terminal (no crash).
How should s-c-kdump react on that? Error message? Silently change that to some valid value? Something else?
Possible values are
where auto is string
X is numeric value with optional M suffix
Y is optional value with optional M suffix
I will add check for the above possibilities.
Should be fixed in system-config-kdump-188.8.131.52-14.el6
Red Hat Enterprise Linux Beta 2 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.