[Bug 1204579] Re: ufw doesn't support concurrent updates

2022-06-03 Thread Raynald de Lahondès
I have declared also the bug in Ansible collection repo, however this is 
clearly a UFW bug:
https://github.com/ansible-collections/community.general/issues/4769

** Bug watch added: github.com/ansible-collections/community.general/issues 
#4769
   https://github.com/ansible-collections/community.general/issues/4769

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1204579

Title:
  ufw doesn't support concurrent updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ufw/+bug/1204579/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1204579] Re: ufw doesn't support concurrent updates

2022-06-03 Thread Raynald de Lahondès
ufw does not support rule removal. For a particular project (a task queue on a 
cloud adhoc HPC cluster), I have had the occasion to test it in a relatively 
massive parallel rate (20 concurrent uses). I have experienced:
- nice behaviour when adding rules,
- bad behaviour when removing rules.

I was triggering ufw with ansible parallel playbooks execution.

When removing rules the defect rate was high (as soon as more than two
playbooks were launched together, some of the rules were not deleted).
In that case, ufw fails silently, which is quite bad.

As a counter measure I used task-spooler (apt install task-spooler) I changed 
my ansible task from:
```yaml
community.general.ufw:
   from_ip: "{{ hostvars[nodename].ipv4 }}"
   rule: allow
   delete: yes
```

to
```yaml
ansible.builtin.script:
   cmd: /usr/bin/tsp /usr/sbin/ufw delete allow from "{{ 
hostvars[nodename].ipv4 }}"
   become: true
```

This solved the issue.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1204579

Title:
  ufw doesn't support concurrent updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ufw/+bug/1204579/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 455786] Re: battery indicator is wrong

2010-05-10 Thread Raynald
I could resolve the bug using combining the trick in bug #270123 and the
trick to update a buggy DSDT table in Karmic/Lucid : go to this bug to
find out because it's really more a matter of ACPI than something to do
with gnome-power-manager.

-- 
battery indicator is wrong
https://bugs.launchpad.net/bugs/455786
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 270123] Re: Wrong battery status

2010-05-10 Thread Raynald
Many thanks to Patrick. This solved the problem for me.


In short combine this to create a new DSDT (ref:
https://wiki.kubuntu.org/LaptopTestingTeam/Old/FujitsuEsprimoU9200)

code
sudo apt-get install iasl
cd
mkdir DSDT
cd DSDT
sudo cat /proc/acpi/dsdt  dsdt.dat
iasl -d dsdt.dat
gedit dsdt.aml
/code

Ok, now you should have your dsdt file open. So let's fix it, look for
the following code in Device (BAT0), under the Method (UPBS, 0,
NotSerialized) subsection:

code
 If (LEqual (Local0, 0x02)) 
 {
 And (Local7, One, Local0) 
 If (LEqual (Local0, One)) 
 {
 And (Local7, 0x80, Local1)
 If (LEqual (Local1, 0x80))
 {
 Or (Local4, 0x02, Local4)
 }
 Else
 {
 Or (Local4, One, Local4) 
 }
 }
  }
/code

Ok, now let's fix it. Else code is misplaced, it has to be moved out of
the If (LEqual (Local0, One)). So, it should be:

code
 If (LEqual (Local0, 0x02)) 
 {
 And (Local7, One, Local0) 
 If (LEqual (Local0, One)) 
 {
 And (Local7, 0x80, Local1)
 If (LEqual (Local1, 0x80))
 {
 Or (Local4, 0x02, Local4)
 }
 //ELSE WAS HERE
 }
 // ELSE CORRECT PLACE
 Else
 {
 Or (Local4, One, Local4) 
 }
  }
/code

Now, simply save and close gedit, and let's continue:

code
cd
cd DSDT
iasl -tc dsdt.dsl
/code

OK now let's insert this in the kernel :

code
mkdir /dsdt
cp dsdt.hex /dest/dsdt_table.h
/code

 - stop following what's written in FujitsuEsprimoU9200, the rest won't
work. -

And follow what's here :

http://newyork.ubuntuforums.org/showthread.php?p=8707937

-- 
Wrong battery status
https://bugs.launchpad.net/bugs/270123
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 455786] Re: battery indicator is wrong

2010-05-07 Thread Raynald
same with Lucid

-- 
battery indicator is wrong
https://bugs.launchpad.net/bugs/455786
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 455786] Re: battery indicator is wrong

2010-05-07 Thread Raynald
this seems a duplicate of #270123

-- 
battery indicator is wrong
https://bugs.launchpad.net/bugs/455786
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 270123] Re: Wrong battery status

2010-01-22 Thread Raynald
Same pb on my Fujitsu it just occured when I switched from 9.06 to 9.10.

-- 
Wrong battery status
https://bugs.launchpad.net/bugs/270123
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs