An attempt to start firewall-config ends up with: Illegal instruction (core dumped) As the test machine is EV67 (UP1100) then it is not very likely that this was compiled for a wrong platform. Michal michal
Oops! Forgot to add. Attempts to click on an entry in "System" menu quietly do nothing and this will quite confusing for somebody new
I think this is not a firewall-config problem. In my opinion either glibc, g++ or libqt is the source of the segmentation fault. Could you please make a # gdb /usr/sbin/firewall-config gdb > run gdb > .... gdb > bt
Distributed executables were stripped. But anyway: # gdb /usr/sbin/firewall-config GNU gdb 5.0 Copyright 2000 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "alpha-redhat-linux"... (no debugging symbols found)... (gdb) r Starting program: /usr/sbin/firewall-config [New Thread 1024 (LWP 11035)] Qt: gdb: -nograb added to command-line options. Use the -dograb option to enforce grabbing. firewall-config: Fatal IO error: client killed Program exited with code 01. (gdb) bt No stack. Ok, so lets try with '-dograb', like suggested above: (no debugging symbols found)... (gdb) set args -dograb (gdb) run Starting program: /usr/sbin/firewall-config -dograb [New Thread 1024 (LWP 11040)] firewall-config: Fatal IO error: client killed Program exited with code 01. (gdb) bt No stack. (gdb) quit I did not realized that this program was using Qt. Over years I still have to see a version of Qt and/or KDE which would be not riddled with weird bugs.
*** This bug has been marked as a duplicate of 19182 ***