I didn't have such problems in 2007.1.
The other thing is that once I exported my setting with File -> Export.. -> Export as IPTables (Linux) Script and now just don't know how to import them.
What am I doing wrong?
Full Version: Problem with KMyFirewall configuration
I compiled KMyFirewall 1.0.1 from sources without probs. Now I have them with configuring it. The problem is all options are inactive (I run it as root)
I didn't have such problems in 2007.1.
The other thing is that once I exported my setting with File -> Export.. -> Export as IPTables (Linux) Script and now just don't know how to import them.
What am I doing wrong?
I didn't have such problems in 2007.1.
The other thing is that once I exported my setting with File -> Export.. -> Export as IPTables (Linux) Script and now just don't know how to import them.
What am I doing wrong?
Hi zibi,
did you pass on your kde install path when compiling?
(http://magrathea.dnsalias.net/~hubinger/kmf/kmf_doc/compilation.html)
Besides from that, I would check which config files the app is using and where they reside. This can be checked by "urpmq -vil kmyfirewall". Defaults seem to lie in /usr/share.
So if you're finding the corresponding filenames within your user dir from a previous installation, you should be able to go ahead.
HTH,
scoonma
did you pass on your kde install path when compiling?
(http://magrathea.dnsalias.net/~hubinger/kmf/kmf_doc/compilation.html)
Besides from that, I would check which config files the app is using and where they reside. This can be checked by "urpmq -vil kmyfirewall". Defaults seem to lie in /usr/share.
So if you're finding the corresponding filenames within your user dir from a previous installation, you should be able to go ahead.
HTH,
scoonma
Hi there scoonma 
1. No, I did not pass those paths while compiling, but I think that configuration script guessed them correctly as there were no errors during compilation.
2. What should I do with this?
1. No, I did not pass those paths while compiling, but I think that configuration script guessed them correctly as there were no errors during compilation.
2. What should I do with this?
CODE
[root@localhost zibi1981]# urpmq -vil kmyfirewall
getting lock on urpmi
sprawdzanie pliku syntezy [/var/lib/urpmi/synthesis.hdlist.plf-free.cz]
sprawdzanie pliku syntezy [/var/lib/urpmi/synthesis.hdlist.plf-nonfree.cz]
sprawdzanie pliku syntezy [/var/lib/urpmi/synthesis.hdlist.main.cz]
sprawdzanie pliku syntezy [/var/lib/urpmi/synthesis.hdlist.contrib.cz]
sprawdzanie pliku syntezy [/var/lib/urpmi/synthesis.hdlist.non-free.cz]
sprawdzanie pliku syntezy [/var/lib/urpmi/synthesis.hdlist.main_updates.cz]
sprawdzanie pliku syntezy [/var/lib/urpmi/synthesis.hdlist.contrib_updates.cz]
sprawdzanie pliku syntezy [/var/lib/urpmi/synthesis.hdlist.non-free_updates.cz]
brak pliku hdlist dla no?nika contrib, uzyskano cz??ciowe wyniki dla pakietu kmyfirewall
Name : kmyfirewall
Version : 1.0.1
Release : 1mdv2007.1
Group : System/Configuration/Networking
Size : 587210 Architecture: i586
Summary : IPTables-based firewall configuration tool for the KDE
unlocking urpmi database
getting lock on urpmi
sprawdzanie pliku syntezy [/var/lib/urpmi/synthesis.hdlist.plf-free.cz]
sprawdzanie pliku syntezy [/var/lib/urpmi/synthesis.hdlist.plf-nonfree.cz]
sprawdzanie pliku syntezy [/var/lib/urpmi/synthesis.hdlist.main.cz]
sprawdzanie pliku syntezy [/var/lib/urpmi/synthesis.hdlist.contrib.cz]
sprawdzanie pliku syntezy [/var/lib/urpmi/synthesis.hdlist.non-free.cz]
sprawdzanie pliku syntezy [/var/lib/urpmi/synthesis.hdlist.main_updates.cz]
sprawdzanie pliku syntezy [/var/lib/urpmi/synthesis.hdlist.contrib_updates.cz]
sprawdzanie pliku syntezy [/var/lib/urpmi/synthesis.hdlist.non-free_updates.cz]
brak pliku hdlist dla no?nika contrib, uzyskano cz??ciowe wyniki dla pakietu kmyfirewall
Name : kmyfirewall
Version : 1.0.1
Release : 1mdv2007.1
Group : System/Configuration/Networking
Size : 587210 Architecture: i586
Summary : IPTables-based firewall configuration tool for the KDE
unlocking urpmi database
QUOTE
1. No, I did not pass those paths while compiling, but I think that configuration script guessed them correctly as there were no errors during compilation.
Hm. Then at least I'd check if the config script set the path correctly from it's logfile. Qt-path may not be a problem, but I kde could be different (default values vs. user values for apps). Besides that, it's from the docs page of KMyFirewall!
QUOTE
2. What should I do with this?
CODE
[root@localhost zibi1981]# urpmq -vil kmyfirewall
getting lock on urpmi
[...]
getting lock on urpmi
[...]
Ah! You'll only see the full list of files (due to the -l option) if you installed not the synthesis, but the full hdlist.cz from repositories.
HTH,
scoonma
QUOTE (scoonma @ Oct 16 2007, 11:21 AM) 
Hm. Then at least I'd check if the config script set the path correctly from it's logfile. Qt-path may not be a problem, but I kde could be different (default values vs. user values for apps). Besides that, it's from the docs page of KMyFirewall!
Where can I find this logfile? I've searched whole KMyFirewall directory (the one in which I compiled it), but just couldn't find it.
QUOTE (zibi1981 @ Oct 19 2007, 06:32 AM)
Where can I find this logfile?
If you ran ./configure, there should be a 'config.log' in the same directory that you ran it in.
You can get the whole config.log file below. Here is what I found in it about paths.
CODE
PATH: /usr/bin
PATH: /bin
PATH: /usr/local/bin
PATH: /usr/X11R6/bin/
PATH: /usr/games
PATH: /usr/lib/qt3//bin
PATH: /home/zibi1981/bin
PATH: /usr/lib/qt3//bin
PATH: /bin
PATH: /usr/local/bin
PATH: /usr/X11R6/bin/
PATH: /usr/games
PATH: /usr/lib/qt3//bin
PATH: /home/zibi1981/bin
PATH: /usr/lib/qt3//bin
Did you install the automake package?
EDIT: Please also do a "urpmi libjpeg62" if needed.
EDIT: Please also do a "urpmi libjpeg62" if needed.
Already have them both as You can see below.
CODE
[zibi1981@localhost ~]$ rpm -qa | grep automake
automake-1.10-2mdv2008.0
[zibi1981@localhost ~]$ rpm -qa | grep libjpeg62
libjpeg62-6b-41mdv2008.0
libjpeg62-devel-6b-41mdv2008.0
automake-1.10-2mdv2008.0
[zibi1981@localhost ~]$ rpm -qa | grep libjpeg62
libjpeg62-6b-41mdv2008.0
libjpeg62-devel-6b-41mdv2008.0
QUOTE (zibi1981 @ Oct 23 2007, 12:13 AM)
Already have them both as You can see below.
Good. Please inspect the contents of this file:
/etc/ld.so.conf
and the contents of the directory
/etc/ld.so.conf.d/
If there's no KDE library path reference in one of these, you may have to provide that information at compile time using the option mentioned above explicitly (try /usr/lib/kde3 first). Also check wether you've installed all -devel type packages possibly needed for your KDE version. Another potential source of problems I could think of is a possible version conflict or mismatch due to KDE 3.x / 4.x. Mandriva 2008 offers both of them.
Content of /etc/ld.so.conf:
/etc/ld.so.conf.d/ is a folder in which I found
Should I add /usr/lib/kde3 to /etc/ld.so.conf?
I passed on the path to KDE and got this
CODE
include ld.so.conf.d/*.conf
/usr/X11R6/lib
/usr/lib/qt3/lib
/usr/X11R6/lib
/usr/lib/qt3/lib
/etc/ld.so.conf.d/ is a folder in which I found
CODE
[zibi1981@localhost ld.so.conf.d]$ ls -al
razem 24
drwxr-xr-x 3 root root 4096 2007-10-13 22:15 ./
drwxr-xr-x 86 root root 8192 2007-10-25 09:21 ../
drwxr-xr-x 2 root root 4096 2007-10-13 12:12 GL/
lrwxrwxrwx 1 root root 25 2007-10-13 12:12 GL.conf -> /etc/alternatives/gl_conf
-rw-r--r-- 1 root root 18 2007-09-07 23:59 graphviz.conf
-rw-r--r-- 1 root root 17 2007-09-16 07:50 qt4.conf
razem 24
drwxr-xr-x 3 root root 4096 2007-10-13 22:15 ./
drwxr-xr-x 86 root root 8192 2007-10-25 09:21 ../
drwxr-xr-x 2 root root 4096 2007-10-13 12:12 GL/
lrwxrwxrwx 1 root root 25 2007-10-13 12:12 GL.conf -> /etc/alternatives/gl_conf
-rw-r--r-- 1 root root 18 2007-09-07 23:59 graphviz.conf
-rw-r--r-- 1 root root 17 2007-09-16 07:50 qt4.conf
Should I add /usr/lib/kde3 to /etc/ld.so.conf?
I passed on the path to KDE and got this
CODE
[root@localhost kmyfirewall-1.0.1]# ./configure --prefix=/usr/lib/kde3
(...)
Warning: you chose to install this package in /usr/lib/kde3,
but KDE was found in /usr.
For this to work, you will need to tell KDE about the new prefix, by ensuring
that KDEDIRS contains it, e.g. export KDEDIRS=/usr/lib/kde3:/usr
Then restart KDE.
Good - your configure finished. Start make now
(...)
Warning: you chose to install this package in /usr/lib/kde3,
but KDE was found in /usr.
For this to work, you will need to tell KDE about the new prefix, by ensuring
that KDEDIRS contains it, e.g. export KDEDIRS=/usr/lib/kde3:/usr
Then restart KDE.
Good - your configure finished. Start make now
QUOTE (zibi1981 @ Oct 25 2007, 10:17 AM)
Should I add /usr/lib/kde3 to /etc/ld.so.conf?
That does make sense to me. Afterwards, invoke "ldconfig" (no parameters) as root and try compiling (without --prefix...) --> KMyFirewall should install to /usr/local, which is better in case something fails.
I did that and KMyFirewall installed to
Unfortunately still nothing. The options are inactive as they were before
CODE
[zibi1981@localhost kmyfirewall-1.0.1]$ whereis kmyfirewall
kmyfirewall: /usr/bin/kmyfirewall /usr/include/kmyfirewall
kmyfirewall: /usr/bin/kmyfirewall /usr/include/kmyfirewall
Unfortunately still nothing. The options are inactive as they were before
QUOTE (zibi1981 @ Oct 25 2007, 11:17 PM)
Unfortunately still nothing. The options are inactive as they were before
Okay, last chance? The configure program said kde is installed to /usr, most normal user generated installations (i.e. without giving params to ./configure) go into /usr/local. So you could (as normal user!) do a
CODE
./configure --prefix=/usr
to insure KMyFirewall will go into the normal KDE tree, afterwards "make" (as normal user again!) and finally "make install" as root.
Good luck!
O.K., did as you suggested, but nothing has changed. KMyFirewall is still in the same place, so what was the point here?
CODE
[zibi1981@localhost kmyfirewall-1.0.1]$ whereis kmyfirewall
kmyfirewall: /usr/bin/kmyfirewall /usr/include/kmyfirewall
kmyfirewall: /usr/bin/kmyfirewall /usr/include/kmyfirewall
The --prefix option is used to determine an install path for compiled binaries after building them. So it's done correctly. BTW, I saw version 1.0.1 is recent for 2007.1 and also for 2008, ready to install with urpmi. Why not use that one?
I did that before, and I couldn't even start this program, but here you go...
And now what happens when I run newly installed KMyFirewall...
CODE
[root@localhost kmyfirewall-1.0.1]# urpmq -i kmyfirewall
Name : kmyfirewall
Version : 1.0.1
Release : 1mdv2007.1
Group : System/Configuration/Networking
Size : 587210 Architecture: i586
Summary : IPTables-based firewall configuration tool for the KDE
[root@localhost kmyfirewall-1.0.1]# urpmi kmyfirewall
W celu spe?nienia zale?no?ci zostan? zainstalowane nast?puj?ce pakiety:
Package Version Release Arch
(medium "contrib")
kmyfirewall 1.0.1 1mdv2007.1 i586
libkmyfirewall0 1.0.1 1mdv2007.1 i586
Zostanie wykorzystany dodatkowy obszar na dysku: 1.5MB
Rozpocz?? instalacj? 2 pakietów? (T/n) t
ftp://ftp.ps.pl/mirrors/Mandrakelinux/official/2008.0/i586/media/contrib/release/libkmyfirewall0-1.0.1-1mdv2007.1.i586.rpm
ftp://ftp.ps.pl/mirrors/Mandrakelinux/official/2008.0/i586/media/contrib/release/kmyfirewall-1.0.1-1mdv2007.1.i586.rpm
instalowanie libkmyfirewall0-1.0.1-1mdv2007.1.i586.rpm kmyfirewall-1.0.1-1mdv2007.1.i586.rpm z /var/cache/urpmi/rpms
Przygotowywanie... #############################################
1/2: libkmyfirewall0 #############################################
2/2: kmyfirewall ##########################
Name : kmyfirewall
Version : 1.0.1
Release : 1mdv2007.1
Group : System/Configuration/Networking
Size : 587210 Architecture: i586
Summary : IPTables-based firewall configuration tool for the KDE
[root@localhost kmyfirewall-1.0.1]# urpmi kmyfirewall
W celu spe?nienia zale?no?ci zostan? zainstalowane nast?puj?ce pakiety:
Package Version Release Arch
(medium "contrib")
kmyfirewall 1.0.1 1mdv2007.1 i586
libkmyfirewall0 1.0.1 1mdv2007.1 i586
Zostanie wykorzystany dodatkowy obszar na dysku: 1.5MB
Rozpocz?? instalacj? 2 pakietów? (T/n) t
ftp://ftp.ps.pl/mirrors/Mandrakelinux/official/2008.0/i586/media/contrib/release/libkmyfirewall0-1.0.1-1mdv2007.1.i586.rpm
ftp://ftp.ps.pl/mirrors/Mandrakelinux/official/2008.0/i586/media/contrib/release/kmyfirewall-1.0.1-1mdv2007.1.i586.rpm
instalowanie libkmyfirewall0-1.0.1-1mdv2007.1.i586.rpm kmyfirewall-1.0.1-1mdv2007.1.i586.rpm z /var/cache/urpmi/rpms
Przygotowywanie... #############################################
1/2: libkmyfirewall0 #############################################
2/2: kmyfirewall ##########################
And now what happens when I run newly installed KMyFirewall...
CODE
[root@localhost kmyfirewall-1.0.1]# kmyfirewall
shell-init: error retrieving current directory: getcwd: cannot access parent directories: Nie ma takiego pliku ani katalogu
kbuildsycoca running...
Reusing existing ksycoca
kio (KService*): WARNING: The desktop entry file .hidden/dirfilterplugin.desktop has Type=Service but is located under "apps" instead of "services"
kio (KService*): WARNING: Invalid Service : .hidden/dirfilterplugin.desktop
kbuildsycoca: WARNING: KLocale: trying to look up "" in catalog. Fix the program
kio (KService*): WARNING: Invalid Service : /usr/share/applications/kde/kmyfirewall.desktop
kbuildsycoca: WARNING: '/usr/share/applications/openoffice.org2.3-base.desktop' specifies undefined mimetype/servicetype 'application/vnd.oasis.opendocument.database'
kbuildsycoca: WARNING: '/usr/share/applications/yelp.desktop' specifies undefined mimetype/servicetype 'application/docbook+xml'
kbuildsycoca: WARNING: 'knotify.desktop' specifies undefined mimetype/servicetype 'KNotify'
kbuildsycoca: WARNING: 'xine_part.desktop' specifies undefined mimetype/servicetype 'KaffeinePart'
kbuildsycoca: WARNING: '/usr/share/applications/kde/konversation.desktop' specifies undefined mimetype/servicetype 'DCOP/InstantMessenger;DCOP/Unique'
kbuildsycoca: WARNING: '/usr/share/applications/kover.desktop' specifies undefined mimetype/servicetype 'application/x-kover'
kbuildsycoca: WARNING: '/usr/share/applications/kde/kpovmodeler.desktop' specifies undefined mimetype/servicetype 'KPovModeler/Document'
kmyfirewall:
Found Splashscreen at: /usr/share/apps/kmyfirewall/pics/splash.png
kmyfirewall: KMFSelectInterface::accept()
kmyfirewall: Found item: 0
kmyfirewall:
Found Splashscreen at: /usr/share/apps/kmyfirewall/pics/splash.png
kmyfirewall:
void KMFConfigDialog::setupPlugins()
kmyfirewall: void KMFConfigDialog::checkPlugins()
kmyfirewall:
Start query
kmyfirewall: Query performed for KMyFirewall/Installer
kmyfirewall: Found Plugin: KMyFirewall Installer for Linux
Library: libkmfinstaller_linux
kmyfirewall: Query performed for KMyFirewall/Compiler
kmyfirewall: Found Plugin: KMyFirewall IPTables Compiler
Library: libkmfcompiler_ipt
kmyfirewall: Library files for "libkmfcompiler_ipt.la" not found in paths.
>> running as realtime process now (priority 50)
Launched ok, pid = 8419
kmyfirewall: Couldn't load plugin: KMyFirewall IPTables Compiler
KCrash: Application 'kmyfirewall' crashing...
shell-init: error retrieving current directory: getcwd: cannot access parent directories: Nie ma takiego pliku ani katalogu
kbuildsycoca running...
Reusing existing ksycoca
kio (KService*): WARNING: The desktop entry file .hidden/dirfilterplugin.desktop has Type=Service but is located under "apps" instead of "services"
kio (KService*): WARNING: Invalid Service : .hidden/dirfilterplugin.desktop
kbuildsycoca: WARNING: KLocale: trying to look up "" in catalog. Fix the program
kio (KService*): WARNING: Invalid Service : /usr/share/applications/kde/kmyfirewall.desktop
kbuildsycoca: WARNING: '/usr/share/applications/openoffice.org2.3-base.desktop' specifies undefined mimetype/servicetype 'application/vnd.oasis.opendocument.database'
kbuildsycoca: WARNING: '/usr/share/applications/yelp.desktop' specifies undefined mimetype/servicetype 'application/docbook+xml'
kbuildsycoca: WARNING: 'knotify.desktop' specifies undefined mimetype/servicetype 'KNotify'
kbuildsycoca: WARNING: 'xine_part.desktop' specifies undefined mimetype/servicetype 'KaffeinePart'
kbuildsycoca: WARNING: '/usr/share/applications/kde/konversation.desktop' specifies undefined mimetype/servicetype 'DCOP/InstantMessenger;DCOP/Unique'
kbuildsycoca: WARNING: '/usr/share/applications/kover.desktop' specifies undefined mimetype/servicetype 'application/x-kover'
kbuildsycoca: WARNING: '/usr/share/applications/kde/kpovmodeler.desktop' specifies undefined mimetype/servicetype 'KPovModeler/Document'
kmyfirewall:
Found Splashscreen at: /usr/share/apps/kmyfirewall/pics/splash.png
kmyfirewall: KMFSelectInterface::accept()
kmyfirewall: Found item: 0
kmyfirewall:
Found Splashscreen at: /usr/share/apps/kmyfirewall/pics/splash.png
kmyfirewall:
void KMFConfigDialog::setupPlugins()
kmyfirewall: void KMFConfigDialog::checkPlugins()
kmyfirewall:
Start query
kmyfirewall: Query performed for KMyFirewall/Installer
kmyfirewall: Found Plugin: KMyFirewall Installer for Linux
Library: libkmfinstaller_linux
kmyfirewall: Query performed for KMyFirewall/Compiler
kmyfirewall: Found Plugin: KMyFirewall IPTables Compiler
Library: libkmfcompiler_ipt
kmyfirewall: Library files for "libkmfcompiler_ipt.la" not found in paths.
>> running as realtime process now (priority 50)
Launched ok, pid = 8419
kmyfirewall: Couldn't load plugin: KMyFirewall IPTables Compiler
KCrash: Application 'kmyfirewall' crashing...
Hm, this looks really bad. Sorry, I've no more ideas than to file a bug report to qa.mandriva.com and wait for a fix.
Anyone else has an idea what to try next?
No one replied, so far... Does anyone use KMyFirewall on Mandriva 2008.0? If so, then how to configure it properly? Does anyone have similar problem with it?
sorry that I can't help you, but I haven't used kmyfirewall on Mandriva, i just use the built-in mandriva firewall, which worked very well for me so far. Maybe kmyfirewall conflicts with it ? Don't know how much (if at all) mandriva tweaked iptables/shorewall.
So for now I got back to Firestarter, although I prefer KMyFirewall...
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.