Bug#1004449: rfcomm busyloops taking 35% CPU due to needlessly low busy loop timeout

Package: bluez Version: all tools/rfcomm.c has a ppoll() with 200ns timeout. It just appears to be there to detect when the program should end, and takes about 35% CPU on a raspberry pi 4. If I change it to 10'000'000 (10ms) it seems to not have any functional impact aside from making the CPU

Bug#980595: libcheck made a breaking change

char name[] = { "Thomas Habets" }; char email[] = { "tho...@habets.se " }; char kernel[]= { "Linux" }; char *pgpKey[] = { "http://www.habets.pp.se/pubkey.txt; }; char pgp[] = { "9907 8698 8A24 F52F 1C2E 87F6 3

Bug#955477: NetworkManager removes manually added addresses from interfaces

Package: network-manager Version: 1.14.6-2+deb10u1 NetworkManager removes manually added addresses from interfaces. E.g. if I attach a USB ethernet dongle and run "ip a a 192.0.2.1/24 dev eth0", some time later (it varies. A minute… sometimes an hour) the NetworkManager deletes that address,

Bug#941412: cpio -o -H tar allows anyone who can create files in tree to inject any tar content they want

Package: cpio This command looks safe, and is a reasonable "backup" command: find /home -type f | cpio -H tar -o > /var/backups/backup.tar But if /home/evil/foo.data is maliciously set up (size is >8GiB) then the tar file can be made to have arbitrary content, so a restore could overwrite

Bug#687288: Working as intended

ypedef struct me_s { char name[] = { "Thomas Habets" }; char email[] = { "tho...@habets.se " }; char kernel[]= { "Linux" }; char *pgpKey[] = { "http://www.habets.pp.se/pubkey.txt; }; char pgp[] = { "9907 8698 8A24 F52F 1C2E 87F6 39A4

Bug#863707: Bug fixed in openssl?

https://github.com/openssl/openssl/issues/3615 says this has been fixed in https://github.com/openssl/openssl/commit/7dca72af91936d246700b78e06def16561a36028 and was an OpenSSL bug. So should this issue be closed? -- typedef struct me_s { char name[] = { "Thomas Habets" };

Bug#828579: This patch should fix it

{ char name[] = { "Thomas Habets" }; char email[] = { "tho...@habets.se" }; char kernel[]= { "Linux" }; char *pgpKey[] = { "http://www.habets.pp.se/pubkey.txt; }; char pgp[] = { "9907 8698 8A24 F52F 1C2E 87F6 39A4 9EEA 4

Bug#828544: Fixed in upstream in 0.05

Fixed in upstream in 0.05. -- typedef struct me_s { char name[] = { "Thomas Habets" }; char email[] = { "tho...@habets.se" }; char kernel[]= { "Linux" }; char *pgpKey[] = { "http://www.habets.pp.se/pubkey.txt; }; char pgp[] = { "9907

Bug#833960: Could you provide more details?

Could you provide a config (without secrets) that triggers this? Not being too familiar with setting up IPsec it would save me a lot of time if you could provide the steps needed to reproduce the problem. -- typedef struct me_s { char name[] = { "Thomas Habets" };

Bug#820697: [Pkg-utopia-maintainers] Bug#820697: network-manager should support both 'arping' implementations

On 11 April 2016 at 17:45, Michael Biebl wrote: > > Which is why I'm suggesting that network-manager should be able to aware > > enough to work with either. > I don't think we want that. If arping and iputils-arping want to be > interchangable arping implementations, they

Bug#820697: [Pkg-utopia-maintainers] Bug#820697: network-manager should support both 'arping' implementations

On 11 April 2016 at 17:16, Michael Biebl wrote: > iputils-arping is the version supported by NM upstream. > Portability is no issue, since NM is Linux-only. > To clarify what I meant: network-manager is preventing `arping` from being installed, which means it's preventing

Bug#521011: arping to hostname sometimes fails (fixed in upstream)

Package: arping Version: 2.07~pre1-2 All versions prior to 2.07 (and this includes 2.07pre1) that have a bug with address resolving. This bug causes arpings to a hostname to sometimes fail silently while arpinging the IP address works fine. I am the upstream author and this has been fixed

Bug#387205: xdm password length limit

passwords that long, because that's wrong for several reasons. - typedef struct me_s { char name[] = { Thomas Habets }; char email[] = { [EMAIL PROTECTED] }; char kernel[]= { Linux }; char *pgpKey[] = { http://www.habets.pp.se/pubkey.txt; }; char pgp[] = { A8A3 D1DD

Bug#210992: fixed in 2.05?

? / Thomas Habets - the author of arping pgp8iKSt7V6WN.pgp Description: PGP signature

Bug#330147: RTF FAQ

Q: I can't ping any/some MAC address on my LAN. A: Arping when pinging a MAC relies on the host to answer a broadcast ping (icmp echo request) properly (IIRC: not the windows way). If you want a host to pop up on MAC ping, you have to config it to respond to broadcast pings. (for

Bug#292564: Fixed in arping 2.05

Fixed in the just-released arping 2.05. - typedef struct me_s { char name[] = { Thomas Habets }; char email[] = { [EMAIL PROTECTED] }; char kernel[]= { Linux }; char *pgpKey[] = { http://www.habets.pp.se/pubkey.txt; }; char pgp[] = { A8A3 D1DD 4AE0 8467 7FDE

Bug#291228: Duplicate of bug 241673

Duplicate of bug 241673, and fixed in upstream version of arping some time ago. - typedef struct me_s { char name[] = { Thomas Habets }; char email[] = { [EMAIL PROTECTED] }; char kernel[]= { Linux }; char *pgpKey[] = { http://www.habets.pp.se/pubkey.txt

Bug#241673: Still fixed in upstream

Just generate a new deb from upstream and all will be well. - typedef struct me_s { char name[] = { Thomas Habets }; char email[] = { [EMAIL PROTECTED] }; char kernel[]= { Linux }; char *pgpKey[] = { http://www.habets.pp.se/pubkey.txt; }; char pgp[] = { A8A3 D1DD