Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 165429
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Netmon Herd <netmon@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Diego E. 'Flameeyes' Pettenò <flameeyes@gentoo.org>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 165429 depends on: Show dependency tree
Bug 165429 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2007-02-05 11:03 0000
As per summary, the configure-arts patch is pretty much a stupid broken hack;
if you need to remove the forced arts dependency, you should now just add
mirror://gentoo/kde-admindir-3.5.5.tar.bz2 to SRC_URI and make sure that
kde_src_unpack is used, the rest is take care of by kde.eclass.

Thanks,
Diego

------- Comment #1 From Markus Ullmann 2007-02-15 23:01:06 0000 -------
meh, why did I add it? ;)

stable on x86

------- Comment #2 From Simon Stelling (RETIRED) 2007-02-18 15:55:52 0000 -------
not working on amd64. It's crashing once I hit the OK button of the
configuration window which pops up at startup.

CHROOT / # kmyfirewall 
Fontconfig warning: line 32: unknown element "cachedir"
Fontconfig warning: line 33: unknown element "cachedir"
Session management error: Authentication Rejected, reason : None of the
authentication protocols specified are supported and host-based authentication
failed
Fontconfig warning: line 32: unknown element "cachedir"
Fontconfig warning: line 33: unknown element "cachedir"
Session management error: Authentication Rejected, reason : None of the
authentication protocols specified are supported and host-based authentication
failed
kbuildsycoca running...
ScimInputContextPlugin()
QMultiInputContext::changeInputMethod(): index=0, slave=xim
QMultiInputContext::changeInputMethod(): index=0, slave=xim
kio (KMimeType): WARNING: KServiceType::offers : servicetype
KMyFirewall/Installer not found
kio (KMimeType): WARNING: KServiceType::offers : servicetype
KMyFirewall/Compiler not found
kio (KMimeType): WARNING: KServiceType::offers : servicetype
KMyFirewall/RuleOptionEdit not found
kio (KMimeType): WARNING: KServiceType::offers : servicetype
KMyFirewall/RuleTargetOptionEdit not found
QMultiInputContext::changeInputMethod(): index=0, slave=xim
kmyfirewall: WARNING: KXMLGUIClient::setXMLFile: cannot find .rc file
kmfgenericinterfaceparetui.rc
kmyfirewall: WARNING: KXMLGUIClient::setXMLFile: cannot find .rc file
kmfinstallerpluginui.rc
kmyfirewall: WARNING: KXMLGUIClient::setXMLFile: cannot find .rc file
kmfiptablescompiler.rc
QMultiInputContext::changeInputMethod(): index=0, slave=xim
KCrash: Application 'kmyfirewall' crashing...
Could not find 'drkonqi' executable.
KCrash cannot reach kdeinit, launching directly.

------- Comment #3 From Jason Wever (RETIRED) 2007-02-22 01:41:08 0000 -------
Looks OK in SPARC land, so stable it is!

------- Comment #4 From Simon Stelling (RETIRED) 2007-02-27 15:28:16 0000 -------
I just tested the latest stable (0.9.6.2-r1) and it works fine, so taking amd64
off the CC until the problem is fixed.

------- Comment #5 From Toralf Förster 2007-03-15 10:13:57 0000 -------
(In reply to comment #1)
> meh, why did I add it? ;)
> 
> stable on x86
> 
But not bug free :-(
This version lost rules eg it reads in the config file but sometimes not all
rules of them. I run into this trouble now many times.

------- Comment #6 From Markus Ullmann 2007-03-27 21:48:42 0000 -------
You said you "lost" rules.. were they created with <1.0 ? upstream page says
that it is kind of expected then

------- Comment #7 From Markus Ullmann 2007-04-18 10:37:51 0000 -------
Tempted to go back to unstable until upstream becomes active again....

------- Comment #8 From Toralf Förster 2007-04-18 11:26:23 0000 -------
(In reply to comment #6)
> You said you "lost" rules.. were they created with <1.0 ? upstream page says
> that it is kind of expected then
> 
No, if I open a newly created rule set file it might be that not all rules are
loaded - the next cick onto save buttons then overwrites the file and the rules
are lost. I cannot reproduce this behaviour but it happens too often fro me.

------- Comment #9 From Markus Ullmann 2007-04-19 18:38:27 0000 -------
Seems debian has the same issues with it (ML archives rule), herd: do we
consider masking it?

------- Comment #10 From Toralf Förster 2007-04-19 18:50:50 0000 -------
I do currently a backup both of the rule file and of the generated script after
every change. Then I compare the file against backup to see whether I lost
rules or not. This is awfully but I dislike to go back to the old version b/c
of incompatibility of the rule file format.

------- Comment #11 From Markus Ullmann 2007-04-20 17:54:41 0000 -------
Toralf: So you as poweruser, what would you recommend? add a big fat warning
about  this and go along with it?

------- Comment #12 From Toralf Förster 2007-04-20 18:13:29 0000 -------
Yep, a fat warning that version 0.9.x is fine for all who like the iptables
interface of KMyfirewall and that the version 1.0.1 didn't have much more
features for this interface to be worth to be upgraded.

For all others who want to try out the new generic interface they could try it.

------- Comment #13 From Markus Ullmann 2007-05-22 19:24:52 0000 -------
note added

Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug