[Bug 1920794] [NEW] tc tool does not accept ipset match
Public bug reported: Steps to reproduce: tc qdisc add dev eth0 root handle 1: htb tc class add dev eth0 parent 1: classid 1:1 htb rate 1024Kbit ipset create mytest hash:net tc filter add dev eth0 protocol ip parent 1:0 prio 1 basic match 'ipset(mytest src)' classid 1:1 Last command fails with the message: Unknown ematch "ipset" Illegal "ematch" It works well with 18.04. On 20.04 machine it also works fine inside Ubuntu 18.04 LXD container. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: iproute2 5.5.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Mar 22 16:18:17 2021 SourcePackage: iproute2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: iproute2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920794 Title: tc tool does not accept ipset match To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1920794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1616771] [NEW] kernel BUG in ppp_generic.c, high load average after that
Public bug reported: On a server machine that runs a pppoe server I have noticed a high load average on a idle machine (CPU is 90% idle). Looking at kernel logs I have found following: [ cut here ] kernel BUG at /build/linux-lts-wily-Ejb_ce/linux-lts-wily-4.2.0/drivers/net/ppp/ppp_generic.c:291! invalid opcode: [#1] SMP Modules linked in: btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c act_mirred sch_ingress cls_fw cls_u32 sch iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat xt_CT nf_conntrack iptable_raw ipt_REJECT nf_reject_ipv4 xt_tcpudp iptab p llc ebtable_filter ebtables x_tables ppdev kvm_intel kvm crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper pvpanic lp 8250_fintek parport_pc parport cirrus ttm drm_kms_helper mac_hid drm syscopyarea sysfillrect sysimgblt i2c_piix4 psmouse flop CPU: 0 PID: 1667 Comm: pppd Not tainted 4.2.0-42-generic #49~14.04.1-Ubuntu Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 task: 8800660a3700 ti: 88002f36c000 task.ti: 88002f36c000 RIP: 0010:[] [] ppp_pernet.part.16+0x4/0x6 RSP: 0018:88002f36fdf8 EFLAGS: 00010246 RAX: RBX: 4004743a RCX: 0065b528 RDX: 01c3 RSI: 4004743a RDI: 81cdd580 RBP: 88002f36fdf8 R08: R09: 020c84e0 R10: 7ffcefbbf610 R11: 0246 R12: 880021176900 R13: 880021176500 R14: 0065b528 R15: 0065b528 FS: 7fb63fc07740() GS:88007fc0() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f5bbfeb5000 CR3: 69b49000 CR4: 001406f0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 Stack: 88002f36fe78 8159e7fa 81cede80 01c3 880036567ca8 01c3 8080808080808080 fe00 8120b324 0001 880021176500 Call Trace: [] ppp_ioctl+0xdca/0xde0 [] ? __fd_install+0x24/0xc0 [] do_vfs_ioctl+0x2cd/0x4b0 [] ? putname+0x5f/0x70 [] ? __raw_callee_save___pv_queued_spin_unlock+0x11/0x20 [] SyS_ioctl+0x79/0x90 [] entry_SYSCALL_64_fastpath+0x16/0x75 Code: 00 00 00 48 c7 c7 58 9a a9 81 48 89 e5 e8 b0 be 8b ff 5d c6 05 97 97 54 00 01 c3 55 48 89 e5 0f 0b 55 48 89 e5 0f 0b 55 48 89 e5 <0f> 0b 55 48 89 e5 0f 0b 0f 1f 44 00 00 55 48 c7 c7 20 d7 cd 81 RIP [] ppp_pernet.part.16+0x4/0x6 RSP ---[ end trace e5e2f1c7519e1d6c ]--- Except from unusually high load average I have noticed no other problems. But some services on a machine do monitor load average and shut down if it goes too high, so I had to reboot a machine to fix the issue. I'll be happy to give any additional information required to fix this bug. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-headers-4.2.0-42 4.2.0-42.49~14.04.1 ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12 Uname: Linux 4.2.0-42-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Thu Aug 25 12:19:02 2016 InstallationDate: Installed on 2012-07-25 (1491 days ago) InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 (20120424.1) PackageArchitecture: all SourcePackage: linux-lts-wily UpgradeStatus: Upgraded to trusty on 2013-04-10 (1233 days ago) ** Affects: linux-lts-wily (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1616771 Title: kernel BUG in ppp_generic.c, high load average after that To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-wily/+bug/1616771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1585614] Re: libc on 2016-05-25 causes Apache not to restart, libm.so.6: symbol __strtold_nan, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
It definitely affects 14.04. I had to restart apache2 on several 14.04 installations today. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1585614 Title: libc on 2016-05-25 causes Apache not to restart, libm.so.6: symbol __strtold_nan, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1585614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 986159] Re: squid3 open file descriptors limit is set incorrectly
I can confirm that squid3 installed from precise-proposed (3.1.19-1ubuntu3) has open files limit correctly set to 65535. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/986159 Title: squid3 open file descriptors limit is set incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/986159/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 986159] Re: squid3 open file descriptors limit is set incorrectly
I can confirm that squid3 installed from precise-proposed (3.1.19-1ubuntu3) has open files limit correctly set to 65535. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/986159 Title: squid3 open file descriptors limit is set incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/986159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 986159] Re: squid3 open file descriptors limit is set incorrectly
We will receive a new hardware for our proxy server in the coming days. Then we'll test new package and report back. As we are here, may be it is better to use upstart's directives (umask and limit) for these things? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/986159 Title: squid3 open file descriptors limit is set incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/986159/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 986159] Re: squid3 open file descriptors limit is set incorrectly
We will receive a new hardware for our proxy server in the coming days. Then we'll test new package and report back. As we are here, may be it is better to use upstart's directives (umask and limit) for these things? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/986159 Title: squid3 open file descriptors limit is set incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/986159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 986159] Re: squid3 open file descriptors limit is set incorrectly
On Fri, Apr 20, 2012 at 9:29 PM, Robie Basak 986...@bugs.launchpad.net wrote: I wonder if you can give us any information on the impact of this bug? If we release without this fix, how many people are likely to be affected? Do you think this bug is severe enough to warrant a freeze exception? I think that this bug won't affect most users, and of course there's an easy workaround by fixing the config file by hand, so it probably doesn't justify a freeze exception. Or is this inaccurate? I agree. Squid is a server side application and most system administrators running heavy proxy are aware of file descriptor issues and easily can make necessary changes themselves. The alternatives are to either issue a Stable Release Update after release (https://wiki.ubuntu.com/StableReleaseUpdates), or to defer the fix until the next release. That would be great. -- Timur Irmatov, xmpp:irma...@jabber.ru -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/986159 Title: squid3 open file descriptors limit is set incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/986159/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 986159] Re: squid3 open file descriptors limit is set incorrectly
On Fri, Apr 20, 2012 at 9:29 PM, Robie Basak 986...@bugs.launchpad.net wrote: I wonder if you can give us any information on the impact of this bug? If we release without this fix, how many people are likely to be affected? Do you think this bug is severe enough to warrant a freeze exception? I think that this bug won't affect most users, and of course there's an easy workaround by fixing the config file by hand, so it probably doesn't justify a freeze exception. Or is this inaccurate? I agree. Squid is a server side application and most system administrators running heavy proxy are aware of file descriptor issues and easily can make necessary changes themselves. The alternatives are to either issue a Stable Release Update after release (https://wiki.ubuntu.com/StableReleaseUpdates), or to defer the fix until the next release. That would be great. -- Timur Irmatov, xmpp:irma...@jabber.ru -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/986159 Title: squid3 open file descriptors limit is set incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/986159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 986159] [NEW] squid3 open file descriptors limit is set incorrectly
Public bug reported: As far as I can see, upstart configuration file for squid3 tries to raise limit of open file descriptors to 65535 in pre-start script. Apparently, this is not working as expected, because squid3 starts and reports 'With 1024 file descriptors available' in cache.log Moving ulimit -n 65535 to script section that starts squid itself solves this. Patch to /etc/init/squid3.conf: --- squid3.conf 2012-04-20 17:37:12.636701094 +0500 +++ squid3.conf.new 2012-04-20 17:37:04.624866173 +0500 @@ -47,9 +47,6 @@ then /usr/sbin/squid3 $SQUID_ARGS -z -f $CONFIG fi - - umask 027 - ulimit -n 65535 end script script @@ -57,5 +54,7 @@ . /etc/default/squid3 fi + umask 027 + ulimit -n 65535 exec /usr/sbin/squid3 -N $SQUID_ARGS -f $CONFIG end script P.S. System is Ubuntu 12.04 fully updated as of 2012-04-20. ** Affects: squid3 (Ubuntu) Importance: Undecided Status: New ** Tags: squid3 ulimit ** Description changed: As far as I can see, upstart configuration file for squid3 tries to raise limit of open file descriptors to 65535 in pre-start script. Apparently, this is not working as expected, because squid3 starts and reports 'With 1024 file descriptors available' in cache.log Moving ulimit -n 65535 to script section that starts squid itself solves this. Patch to /etc/init/squid3.conf: --- squid3.conf 2012-04-20 17:37:12.636701094 +0500 +++ squid3.conf.new 2012-04-20 17:37:04.624866173 +0500 @@ -47,9 +47,6 @@ - then - /usr/sbin/squid3 $SQUID_ARGS -z -f $CONFIG - fi + then + /usr/sbin/squid3 $SQUID_ARGS -z -f $CONFIG + fi - - umask 027 - ulimit -n 65535 - end script - - script + end script + + script @@ -57,5 +54,7 @@ - . /etc/default/squid3 - fi - + . /etc/default/squid3 + fi + + umask 027 + ulimit -n 65535 - exec /usr/sbin/squid3 -N $SQUID_ARGS -f $CONFIG - end script + exec /usr/sbin/squid3 -N $SQUID_ARGS -f $CONFIG + end script + + P.S. System is Ubuntu 12.04 fully updated as of 2012-04-20. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/986159 Title: squid3 open file descriptors limit is set incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/986159/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 986159] [NEW] squid3 open file descriptors limit is set incorrectly
Public bug reported: As far as I can see, upstart configuration file for squid3 tries to raise limit of open file descriptors to 65535 in pre-start script. Apparently, this is not working as expected, because squid3 starts and reports 'With 1024 file descriptors available' in cache.log Moving ulimit -n 65535 to script section that starts squid itself solves this. Patch to /etc/init/squid3.conf: --- squid3.conf 2012-04-20 17:37:12.636701094 +0500 +++ squid3.conf.new 2012-04-20 17:37:04.624866173 +0500 @@ -47,9 +47,6 @@ then /usr/sbin/squid3 $SQUID_ARGS -z -f $CONFIG fi - - umask 027 - ulimit -n 65535 end script script @@ -57,5 +54,7 @@ . /etc/default/squid3 fi + umask 027 + ulimit -n 65535 exec /usr/sbin/squid3 -N $SQUID_ARGS -f $CONFIG end script P.S. System is Ubuntu 12.04 fully updated as of 2012-04-20. ** Affects: squid3 (Ubuntu) Importance: Undecided Status: New ** Tags: squid3 ulimit ** Description changed: As far as I can see, upstart configuration file for squid3 tries to raise limit of open file descriptors to 65535 in pre-start script. Apparently, this is not working as expected, because squid3 starts and reports 'With 1024 file descriptors available' in cache.log Moving ulimit -n 65535 to script section that starts squid itself solves this. Patch to /etc/init/squid3.conf: --- squid3.conf 2012-04-20 17:37:12.636701094 +0500 +++ squid3.conf.new 2012-04-20 17:37:04.624866173 +0500 @@ -47,9 +47,6 @@ - then - /usr/sbin/squid3 $SQUID_ARGS -z -f $CONFIG - fi + then + /usr/sbin/squid3 $SQUID_ARGS -z -f $CONFIG + fi - - umask 027 - ulimit -n 65535 - end script - - script + end script + + script @@ -57,5 +54,7 @@ - . /etc/default/squid3 - fi - + . /etc/default/squid3 + fi + + umask 027 + ulimit -n 65535 - exec /usr/sbin/squid3 -N $SQUID_ARGS -f $CONFIG - end script + exec /usr/sbin/squid3 -N $SQUID_ARGS -f $CONFIG + end script + + P.S. System is Ubuntu 12.04 fully updated as of 2012-04-20. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/986159 Title: squid3 open file descriptors limit is set incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/986159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 868894] Re: compiz assert failure: *** glibc detected *** compiz: double free or corruption (!prev): 0x00007fa90829aec0 ***
*** This bug is a duplicate of bug 857738 *** https://bugs.launchpad.net/bugs/857738 ** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/868894 Title: compiz assert failure: *** glibc detected *** compiz: double free or corruption (!prev): 0x7fa90829aec0 *** To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/868894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 865905] [NEW] aptitude won't forget a list of 'new packages'
Public bug reported: When I launch aptitude in terminal, it always shows a large number of new packages: --- New Packages (19858) After pressing 'f' it clears that list, but on next start or next update of package lists with 'u' it still shows that same amount of new packages. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: aptitude 0.6.4-1ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu2 Architecture: amd64 Date: Tue Oct 4 10:33:34 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110920.5) SourcePackage: aptitude UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: aptitude (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/865905 Title: aptitude won't forget a list of 'new packages' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptitude/+bug/865905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 865905] Re: aptitude won't forget a list of 'new packages'
** Description changed: - When a launch aptitude in terminal, it always shows a large number of + When I launch aptitude in terminal, it always shows a large number of new packages: --- New Packages (19858) After pressing 'f' it clears that list, but on next start or next update of package lists with 'u' it still shows that same amount of new packages. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: aptitude 0.6.4-1ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu2 Architecture: amd64 Date: Tue Oct 4 10:33:34 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110920.5) SourcePackage: aptitude UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/865905 Title: aptitude won't forget a list of 'new packages' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptitude/+bug/865905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 664165] Re: arping fails to set correct broadcast address (it's not working at all)
Yes, I also confirm that arping from iputils-s20101006.tar.bz2 works while included with maverick doesn't. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/664165 Title: arping fails to set correct broadcast address (it's not working at all) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 681254] [NEW] arping fails to ping local machines
*** This bug is a duplicate of bug 664165 *** https://bugs.launchpad.net/bugs/664165 Public bug reported: My interface eth0 is configured like this: 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 00:1a:80:24:28:b8 brd ff:ff:ff:ff:ff:ff inet 192.168.1.34/24 brd 192.168.1.255 scope global eth0 inet6 fe80::21a:80ff:fe24:28b8/64 scope link valid_lft forever preferred_lft forever There's a local host 192.168.1.22 which is reachable: $ ping -c1 -q 192.168.1.22 PING 192.168.1.22 (192.168.1.22) 56(84) bytes of data. --- 192.168.1.22 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 5.476/5.476/5.476/0.000 ms I can't ping this host with arping: sudo arping -I eth0 192.168.1.22 ARPING 192.168.1.22 from 192.168.1.34 eth0 ^CSent 8 probes (8 broadcast(s)) Received 0 response(s) Running tpcdump shows that arping sends ARP discovery packets to wrong MAC address (ff:1a:ff:24:00:b8) instead of broadcast (ff:ff:ff:ff:ff:ff): 13:22:05.515156 ARP, Request who-has 192.168.1.22 (ff:1a:ff:24:00:b8) tell 192.168.1.34, length 28 13:22:06.515976 ARP, Request who-has 192.168.1.22 (ff:1a:ff:24:00:b8) tell 192.168.1.34, length 28 13:22:07.516058 ARP, Request who-has 192.168.1.22 (ff:1a:ff:24:00:b8) tell 192.168.1.34, length 28 Address ff:1a:ff:24:00:b8 looks familiar to my machines MAC (00:1a:80:24:28:b8) - three octets match at correct positions. It seems that arping somehow does incorrect discovery of broadcast address. arping from lenny does not have this problem. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: iputils-arping 3:20100418-2ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic i686 Architecture: i386 Date: Thu Nov 25 13:18:35 2010 ProcEnviron: LANGUAGE=ru_RU:ru:en_GB:en PATH=(custom, user) LANG=ru_RU.utf8 SHELL=/bin/bash SourcePackage: iputils ** Affects: iputils (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 maverick -- arping fails to ping local machines https://bugs.launchpad.net/bugs/681254 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 681254] Re: arping fails to ping local machines
*** This bug is a duplicate of bug 664165 *** https://bugs.launchpad.net/bugs/664165 -- arping fails to ping local machines https://bugs.launchpad.net/bugs/681254 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 681254] Re: arping fails to ping local machines
*** This bug is a duplicate of bug 664165 *** https://bugs.launchpad.net/bugs/664165 ** This bug has been marked a duplicate of bug 664165 arping fails to set correct broadcast address (it's not working at all) * You can subscribe to bug 664165 by following this link: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/664165/+subscribe -- arping fails to ping local machines https://bugs.launchpad.net/bugs/681254 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 554005] Re: Using some glib functions within multiprocessing from a threaded app sometimes causes 100% CPU utilization
I am also having a problem with gwibber-service consuming 100% of CPU. Also, I see two instances of this process in 'top' listing. gwibber and gwibber service packages' versions are 2.30.1-0ubuntu1 ** Changed in: gwibber (Ubuntu Lucid) Status: Fix Released = New -- Using some glib functions within multiprocessing from a threaded app sometimes causes 100% CPU utilization https://bugs.launchpad.net/bugs/554005 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 159208] releases mirror strongly prefers apache
Public bug reported: I'm trying to create a mirror of ubuntu archive and releases. Catalog 'releases' contains iso images of ubuntu releases. Also, it contains HEADER.html, FOOTER.html and .htaccess files, which are used by Apache web server to build pretty indexes of catalogs. But, we'd like to setup our mirror using lighttpd because we think it better suits a task of serving static content. We could create such prettry indexes ourselves using provided HEADER.html, but the tree is rsynced regularly so it will be removed on every update. May be static index.html in releases folder would be a better way, allowing different mirrors use different web-servers? ** Affects: ubuntu Importance: Undecided Status: New -- releases mirror strongly prefers apache https://bugs.launchpad.net/bugs/159208 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
