[Bug 1880029] [NEW] Netplan optional-addresses produces Unknown key name 'OptionalAddresses'
Public bug reported: Running on 20.04 (focal), the following netplan config for a bridge interface, rendering with networkd: network: version: 2 bridges: br0: interfaces: [bond0, guest] dhcp4: on macaddress: aa:bb:cc:dd:db:2f optional-addresses: [ dhcp4 ] Appears to apply cleanly, however under the hood, networkd appears to reject the resulting OptionalAddresses setting: May 21 16:25:50 hyper systemd-networkd[864186]: /run/systemd/network/10 -netplan-br0.network:5: Unknown key name 'OptionalAddresses' in section 'Link', ignoring. ** Affects: netplan.io (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880029 Title: Netplan optional-addresses produces Unknown key name 'OptionalAddresses' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1880029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1687791] Re: Install of kdump-tools fails
Confirmed issue on Bionic. Also confirmed the suggested patch in 1661629 #3 fixed the install for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687791 Title: Install of kdump-tools fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1687791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766308] Re: inexplicably large file reported by zfs filesystem
Yes, please close... thanks again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766308 Title: inexplicably large file reported by zfs filesystem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1766308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766308] Re: inexplicably large file reported by zfs filesystem
Great, thank you. zdb confirms what we already sort of suspected: the file is ~12T with only 5.5G of real content. I was aware that ZFS reported on disk size differently, but the fact that this isn't a feature of compression threw me off in the output. Object lvl iblk dblk dsize dnsize lsize %full type 7516K 128K 5.51G 512 11.1T0.07 ZFS plain file At any rate, it's still not clear to me how we arrived at this giant (but sparse) file, since the VM and image tools (qemu-img) only consider it to be 10G logical. I'm guessing that the implication is that the bug is with qemu rather than ZFS. My initial concern was that it had been a storage layer corruption, but I guess it's equally plausible that somehow the emulation layer ran wild and just started massively growing the file out of bounds on disk. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766308 Title: inexplicably large file reported by zfs filesystem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1766308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766308] Re: inexplicably large file reported by zfs filesystem
1. Yes, compression is on for the parent and inherited. The ratio only shows 1.37x, which seems rather low if a 12T file was all zeros except for >10G? root@fusion:~# zfs get all rpool/DATA/fusion/store/vms/plexee | grep comp rpool/DATA/fusion/store/vms/plexee compressratio 1.37x - rpool/DATA/fusion/store/vms/plexee compression lz4 inherited from rpool rpool/DATA/fusion/store/vms/plexee refcompressratio 1.37x 2. root@fusion:~# du -h /data/store/vms/plexee/plexee-root 5.6G/data/store/vms/plexee/plexee-root This is what I would expect the VM to be using based on how the file was provisioned and its internal disk state. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766308 Title: inexplicably large file reported by zfs filesystem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1766308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766308] Re: inexplicably large file reported by zfs filesystem
A scrub of the pool detected no issues, no errors. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766308 Title: inexplicably large file reported by zfs filesystem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1766308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766308] [NEW] inexplicably large file reported by zfs filesystem
Public bug reported: I have a zfs filesystem containing a single qemu kvm disk image. The vm has been working normally. The image file is only allocated 10G, however today I became aware that the file, when examined from the ZFS host (hypervisor) is reporting an inexplicable, massive file size of around 12T. 12T is larger than the pool itself. Snapshots or other filesystem features should not be involved. I'm suspicious that the file(system?) has been corrupted. root@fusion:~# ls -l /data/store/vms/plexee/ total 6164615 -rw-r--r-- 1 root root 12201321037824 Apr 23 11:49 plexee-root ^^ !! root@fusion:~# qemu-img info /data/store/vms/plexee/plexee-root image: /data/store/vms/plexee//plexee-root file format: qcow2 virtual size: 10G (10737418240 bytes) disk size: 5.9G cluster_size: 65536 Format specific information: compat: 1.1 lazy refcounts: false refcount bits: 16 corrupt: false root@fusion:~# zfs list rpool/DATA/fusion/store/vms/plexee NAME USED AVAIL REFER MOUNTPOINT rpool/DATA/fusion/store/vms/plexee 5.88G 484G 5.88G /data/store/vms/plexee root@fusion:~# zfs get all rpool/DATA/fusion/store/vms/plexee NAMEPROPERTY VALUE SOURCE rpool/DATA/fusion/store/vms/plexee type filesystem - rpool/DATA/fusion/store/vms/plexee creation Mon Mar 26 9:50 2018 - rpool/DATA/fusion/store/vms/plexee used 5.88G - rpool/DATA/fusion/store/vms/plexee available 484G - rpool/DATA/fusion/store/vms/plexee referenced5.88G - rpool/DATA/fusion/store/vms/plexee compressratio 1.37x - rpool/DATA/fusion/store/vms/plexee mounted yes - rpool/DATA/fusion/store/vms/plexee quota none default rpool/DATA/fusion/store/vms/plexee reservation none default rpool/DATA/fusion/store/vms/plexee recordsize128K default rpool/DATA/fusion/store/vms/plexee mountpoint /data/store/vms/plexee inherited from rpool/DATA/fusion rpool/DATA/fusion/store/vms/plexee sharenfs off default rpool/DATA/fusion/store/vms/plexee checksum on default rpool/DATA/fusion/store/vms/plexee compression lz4 inherited from rpool rpool/DATA/fusion/store/vms/plexee atime off inherited from rpool rpool/DATA/fusion/store/vms/plexee devices off inherited from rpool rpool/DATA/fusion/store/vms/plexee exec on default rpool/DATA/fusion/store/vms/plexee setuidon default rpool/DATA/fusion/store/vms/plexee readonly off default rpool/DATA/fusion/store/vms/plexee zoned off default rpool/DATA/fusion/store/vms/plexee snapdir hidden default rpool/DATA/fusion/store/vms/plexee aclinheritrestricted default rpool/DATA/fusion/store/vms/plexee canmount on default rpool/DATA/fusion/store/vms/plexee xattr on default rpool/DATA/fusion/store/vms/plexee copies1 default rpool/DATA/fusion/store/vms/plexee version 5 - rpool/DATA/fusion/store/vms/plexee utf8only off - rpool/DATA/fusion/store/vms/plexee normalization none - rpool/DATA/fusion/store/vms/plexee casesensitivity sensitive - rpool/DATA/fusion/store/vms/plexee vscan off default rpool/DATA/fusion/store/vms/plexee nbmandoff default rpool/DATA/fusion/store/vms/plexee sharesmb off default rpool/DATA/fusion/store/vms/plexee refquota none default rpool/DATA/fusion/store/vms/plexee refreservationnone default rpool/DATA/fusion/store/vms/plexee primarycache all default rpool/DATA/fusion/store/vms/plexee secondarycacheall default rpool/DATA/fusion/store/vms/plexee usedbysnapshots 0 - rpool/DATA/fusion/store/vms/plexee usedbydataset 5.88G - rpool/DATA/fusion/store/vms/plexee usedbychildren0 - rpool/DATA/fusion/store/vms/plexee usedbyrefreservation 0 - rpool/DATA/fusion/store/vms/plexee logbias latency
[Bug 1649729] Re: ntpd startup failures under xenial
Removing ntpdate should remove the if-up script, so I imagine that would "resolve" the bug by way of workaround. The hosts in question were upgraded from prior LTS, so they would have inherited ntpdate from there. I wasn't aware of the changes to sunset it in the current release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1649729 Title: ntpd startup failures under xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1649729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1649729] Re: ntpd startup failures under xenial
I actually think I gave a fairly thorough description of the problem and it has nothing to do with ntpd configuration. I even said specifically that I can manually start/stop ntpd and it works - configuration valid and operational. The problem is /etc/network/if-up.d/ntpdate starting and stopping the daemon in rapid succession when multiple interfaces come up. This causes binding conflicts and often ntpd will wind up down as a result. Reproduction is fairly easy: Just run /etc/network/if-up.d/ntpdate several times in rapid succession and see what happens. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1649729 Title: ntpd startup failures under xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1649729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1649729] [NEW] ntpd startup failures under xenial
Public bug reported: I have a system running 16.04.1 with multiple interfaces configured via /etc/network/interfaces. Following a restart, ntpd will often be found not running, despite being installed and configured. syslog suggests ntpd is being repeatedly stopped and restarted within seconds. Dec 13 20:23:17 mail ntpd[4031]: ntpd 4.2.8p4@1.3265-o Wed Oct 5 12:34:45 UTC 2016 (1): Starting Dec 13 20:23:17 mail ntpd[4031]: ntpd 4.2.8p4@1.3265-o Wed Oct 5 12:34:45 UTC 2016 (1): Starting Dec 13 20:23:17 mail ntpd[4031]: Command line: /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 106:113 Dec 13 20:23:17 mail ntpd[4031]: Command line: /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 106:113 Dec 13 20:23:17 mail ntpd[4034]: proto: precision = 0.105 usec (-23) Dec 13 20:23:17 mail ntpd[4034]: unable to bind to wildcard address :: - another process may be running - EXITING Dec 13 20:23:17 mail ntpd[4034]: proto: precision = 0.105 usec (-23) Dec 13 20:23:17 mail ntpd[4034]: unable to bind to wildcard address :: - another process may be running - EXITING Dec 13 20:23:18 mail ntp[4119]: * Stopping NTP server ntpd Dec 13 20:23:18 mail ntp[4119]: * Stopping NTP server ntpd Dec 13 20:23:18 mail ntp[4183]: * Starting NTP server ntpd Dec 13 20:23:18 mail ntp[4183]: * Starting NTP server ntpd Dec 13 20:23:18 mail ntpd[4193]: ntpd 4.2.8p4@1.3265-o Wed Oct 5 12:34:45 UTC 2016 (1): Starting Dec 13 20:23:18 mail ntpd[4193]: ntpd 4.2.8p4@1.3265-o Wed Oct 5 12:34:45 UTC 2016 (1): Starting Dec 13 20:23:18 mail ntpd[4193]: Command line: /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 106:113 Dec 13 20:23:18 mail ntpd[4193]: Command line: /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 106:113 Dec 13 20:23:18 mail ntpd[4195]: proto: precision = 0.065 usec (-24) Dec 13 20:23:18 mail ntpd[4195]: proto: precision = 0.065 usec (-24) Dec 13 20:23:18 mail ntpd[4195]: unable to bind to wildcard address :: - another process may be running - EXITING Dec 13 20:23:18 mail ntpd[4195]: unable to bind to wildcard address :: - another process may be running - EXITING My current assumption is that this is the work of /etc/network/if- up.d/ntpdate being run on several interfaces nearly simultaneously. The rapid stop/start cycle of the daemon appears to trip up the port binding, and eventually cause ntpd to become unhappy and wind up stopped. Manually restarting ntpd (or even running /etc/network/if-up.d/ntpdate) outside of interface up/down time properly brings up ntpd. It doesn't appear to be a configuration issue as such. Further, running /etc/network/if-up.d/ntpdate from bash several times in rapid succession also produces the 'missing ntpd' behavior, outside of the context of any interface activity. ** Affects: ntp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1649729 Title: ntpd startup failures under xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1649729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1546674] Re: virt-aa-helper Apparmor profile missing rules for name resolution
At least in my instance, and based on at least one other reporter's description, the issue manifests on upgrade of the host to Xenial with existing guests. If you create new guests in Xenial or newer they may very well be configured correctly (I really don't know). My interpretation was that virt-aa-helper added some functionality in Xenial+ which requires this access, but configs from older versions have not granted it. Or at least maybe that would make repro easier? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1546674 Title: virt-aa-helper Apparmor profile missing rules for name resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1546674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1469915] [NEW] Securiteinfo databases changed
Public bug reported: The clamav-unofficial-sigs package is unable to fetch SecuriteInfo databases. Clamscan reports SecuriteInfo honeynet.hdb database integrity tested BAD - SKIPPING rsync: link_stat "/var/cache/clamav-unofficial-sigs/si-dbs/honeynet.hdb" failed: No such file or directory (2) rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1183) [sender=3.1.0] Failed to successfully update SecuriteInfo production database file: honeynet.hdb - SKIPPING Clamscan reports SecuriteInfo securiteinfobat.hdb database integrity tested BAD - SKIPPING rsync: link_stat "/var/cache/clamav-unofficial-sigs/si-dbs/securiteinfobat.hdb" failed: No such file or directory (2) rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1183) [sender=3.1.0] Failed to successfully update SecuriteInfo production database file: securiteinfobat.hdb - SKIPPING ... Further info: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617798 ** Affects: clamav-unofficial-sigs (Ubuntu) Importance: Undecided Status: New ** Affects: clamav-unofficial-sigs (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #617798 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617798 ** Also affects: clamav-unofficial-sigs (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617798 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1469915 Title: Securiteinfo databases changed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav-unofficial-sigs/+bug/1469915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1230917] Re: [SRU] php5-fpm logrotate errors after package switched to upstart
Check that your logrotate config was actually updated? cd /etc/logrotate.d; mv php5-fpm.dpkg-dist php5-fpm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1230917 Title: [SRU] php5-fpm logrotate errors after package switched to upstart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1230917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1372721] [NEW] invalid reopen-logs command in php5-fpm
Public bug reported: The php5-fpm package includes the following logrotate script: /var/log/php5-fpm.log { rotate 12 weekly missingok notifempty compress delaycompress postrotate invoke-rc.d php5-fpm reopen-logs > /dev/null endscript } However running this on 14.04.1 produces an error: initctl: invalid command: reopen-logs Try `initctl --help' for more information. invoke-rc.d: initscript php5-fpm, action "reopen-logs" failed. error: error running non-shared postrotate script for /var/log/php5-fpm.log of '/var/log/php5-fpm.log ' run-parts: /etc/cron.daily/logrotate exited with return code 1 ** Affects: php5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1372721 Title: invalid reopen-logs command in php5-fpm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1372721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1354720] [NEW] duplicate logrotate for ulogd on trusty
Public bug reported: I upgraded a system with ulogd from precise to trusty. On trusty, the system now has ulogd and ulogd2 installed, saying ulogd is a transitional package. Each of these appears to have its own rotation file in logrotate.d: root@trusty:/etc/logrotate.d# dpkg -S /etc/logrotate.d/ulogd ulogd: /etc/logrotate.d/ulogd root@trusty:/etc/logrotate.d# dpkg -S /etc/logrotate.d/ulogd2 ulogd2: /etc/logrotate.d/ulogd2 These both contain wildcard references which then create a conflict over file names: /etc/cron.daily/logrotate: error: ulogd2:1 duplicate log entry for /var/log/ulog/syslogemu.log ** Affects: ulogd2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1354720 Title: duplicate logrotate for ulogd on trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ulogd2/+bug/1354720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 913935] Re: racoon segfaults when flusing SPD
** Bug watch added: Debian Bug tracker #679482 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679482 ** Also affects: ipsec-tools (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679482 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/913935 Title: racoon segfaults when flusing SPD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipsec-tools/+bug/913935/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 674246] [NEW] printers.conf integrity problems
Public bug reported: Binary package hint: cups 1.4.3-1ubuntu1.3 On multiple occasions, I have witnessed a machine under heavy load experience a corrupted printers.conf file. In at least one instance, the file was partially truncated leading to the loss of approximately half of the printers. In another instance, printers.conf went missing entirely, leaving only printers.conf.O behind. An example log from the latter event is as follows... I [09/Nov/2010:10:06:38 +] Saving printers.conf... I [09/Nov/2010:10:06:38 +] Saving job cache file "/var/cache/cups/job.cache"... I [09/Nov/2010:10:06:38 +] Saving subscriptions.conf... I [09/Nov/2010:10:07:08 +] Saving printers.conf... I [09/Nov/2010:10:07:08 +] Saving subscriptions.conf... I [09/Nov/2010:10:07:38 +] Saving printers.conf... I [09/Nov/2010:10:07:38 +] Saving job cache file "/var/cache/cups/job.cache"... I [09/Nov/2010:10:07:38 +] Saving subscriptions.conf... I [09/Nov/2010:10:08:08 +] Saving printers.conf... I [09/Nov/2010:10:08:08 +] Saving job cache file "/var/cache/cups/job.cache"... I [09/Nov/2010:10:08:08 +] Saving subscriptions.conf... W [09/Nov/2010:10:08:20 +] Possible DoS attack - more than 10 clients connecting from ! I [09/Nov/2010:10:08:38 +] Saving printers.conf... I [09/Nov/2010:10:08:38 +] Saving job cache file "/var/cache/cups/job.cache"... I [09/Nov/2010:10:08:38 +] Saving subscriptions.conf... I [09/Nov/2010:10:09:08 +] Saving printers.conf... I [09/Nov/2010:10:09:08 +] Saving job cache file "/var/cache/cups/job.cache"... I [09/Nov/2010:10:09:08 +] Saving subscriptions.conf... W [09/Nov/2010:10:09:24 +] Possible DoS attack - more than 10 clients connecting from ! I [09/Nov/2010:10:09:39 +] Saving printers.conf... I [09/Nov/2010:10:09:39 +] Saving job cache file "/var/cache/cups/job.cache"... I [09/Nov/2010:10:09:39 +] Saving subscriptions.conf... E [09/Nov/2010:10:09:43 +] Unable to encrypt connection from - A TLS packet with unexpected length was received. I [09/Nov/2010:10:10:00 +] Scheduler shutting down normally. I [09/Nov/2010:10:11:09 +] Listening to 0.0.0.0:631 (IPv4) I [09/Nov/2010:10:11:09 +] Listening to /var/run/cups/cups.sock (Domain) I [09/Nov/2010:10:11:09 +] Listening to 0.0.0.0:443 (IPv4) W [09/Nov/2010:10:11:09 +] No limit for CUPS-Get-Document defined in policy default - using Send-Document's policy I [09/Nov/2010:10:11:09 +] Remote access is enabled. I [09/Nov/2010:10:11:09 +] Loaded configuration file "/etc/cups/cupsd.conf" I [09/Nov/2010:10:11:09 +] Using default TempDir of /var/spool/cups/tmp... I [09/Nov/2010:10:11:09 +] MaxClients limited to 1/3 (341) of the file descriptor limit (1024)... I [09/Nov/2010:10:11:09 +] Configured for up to 341 clients. I [09/Nov/2010:10:11:09 +] Allowing up to 10 client connections per host. I [09/Nov/2010:10:11:09 +] Using policy "default" as the default! I [09/Nov/2010:10:11:09 +] Full reload is required. I [09/Nov/2010:10:11:09 +] Loaded MIME database from "/usr/share/cups/mime" and "/etc/cups": 37 types, 73 filters... I [09/Nov/2010:10:11:09 +] Loading job cache file "/var/cache/cups/job.cache"... E [09/Nov/2010:10:11:09 +] [Job 4985] Unable to queue job for destination "leadpipe"! I [09/Nov/2010:10:11:09 +] Full reload complete. I [09/Nov/2010:10:11:09 +] Cleaning out old temporary files in "/var/spool/cups/tmp"... E [09/Nov/2010:10:11:09 +] Unable to remove temporary file "/var/spool/cups/tmp/.fontconfig" - Is a directory I [09/Nov/2010:10:11:09 +] Listening to 0.0.0.0:631 on fd 6... I [09/Nov/2010:10:11:09 +] Listening to /var/run/cups/cups.sock on fd 7... I [09/Nov/2010:10:11:09 +] Listening to 0.0.0.0:443 on fd 8... I [09/Nov/2010:10:11:09 +] Resuming new connection processing... E [09/Nov/2010:10:23:11 +] Unable to encrypt connection from - A TLS packet with unexpected length was received. 10:09:39 is the last time printers.conf is saved 10:10:00 scheduler shuts down (cause never seems to be mentioned for shut downs) 10:11:09 server back up, now missing printers (Unable to queue job for destination "leadpipe"!) Somewhere in this mess the printers.conf was removed or renamed and never replaced. Cups came back up with nil printers (which also leads to samba removing its record of the printers as well). The only possible culprit I can make out from the logs is "Possible DoS attack - more than 10 clients connecting from !" to configure it, as the cupsd.conf makes no apparent mention of it. This all leads me to believe that whatever process is used to continually re-write the printers.conf file is not acting in a suitably atomic fashion. Ideally there should be some mechanism in place to ensure that the integrity of the file will remain intact during updates, even if interrupted. Issue reported to cups: http://cups.org/str.php?L3715 ** Affects: cups (U
[Bug 674240] [NEW] Possible DoS attack from Unknown (cups)
Public bug reported: Binary package hint: cups 1.4.3-1ubuntu1.3 I have witnessed several times in cups logs the following completely unhelpful error: "Possible DoS attack - more than 10 clients connecting from !" First, the most obvious omission is that whatever variable is supposed to be identifying the attacker is not working. This makes finding the trigger user/machine nearly impossible on the face of it. I'm also concerned about what effect this feature may be having on the operation of the server. It does not appear to be an optional feature, and without any means to identify the trigger cause, I would prefer to disable it rather than risk it interfering with the availability of a server under heavy legitimate use. Issue filed with cups: http://cups.org/str.php?L3716 ** Affects: cups (Ubuntu) Importance: Undecided Status: New -- Possible DoS attack from Unknown (cups) https://bugs.launchpad.net/bugs/674240 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 674216] Re: 0x000003e6 Error When Printing from Windows 7 x64
** Description changed: Binary package hint: samba - There exist some driver incompatibilities between Samba and Windows 7 - x64. The driver is able to be installed successfully, but attempting to - then connect to the printer (via Samba) produces Error code 0x03e6 - within Windows. + There exist some driver incompatibilities between Samba (3.4+) and + Windows 7 x64. The driver is able to be installed successfully, but + attempting to then connect to the printer (via Samba) produces Error + code 0x03e6 within Windows. + + There does not appear to be a direct correlation with a specific Make or + Model of printer, as it has been observed across multiple. It may + sometimes be temporarily resolved by re-exporting or re-upload of the + affected driver, but this has not been shown to be a permanent solution. + The only known workaround is to downgrade to Samba 3.3. A bug has been filed against Samba directly here: https://bugzilla.samba.org/show_bug.cgi?id=7567 -- 0x03e6 Error When Printing from Windows 7 x64 https://bugs.launchpad.net/bugs/674216 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 674216] [NEW] 0x000003e6 Error When Printing from Windows 7 x64
Public bug reported: Binary package hint: samba There exist some driver incompatibilities between Samba and Windows 7 x64. The driver is able to be installed successfully, but attempting to then connect to the printer (via Samba) produces Error code 0x03e6 within Windows. A bug has been filed against Samba directly here: https://bugzilla.samba.org/show_bug.cgi?id=7567 ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- 0x03e6 Error When Printing from Windows 7 x64 https://bugs.launchpad.net/bugs/674216 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 183840] Re: please build with SSL/TLS enabled
** Bug watch added: Debian Bug tracker #266229 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=266229 ** Also affects: freeradius (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=266229 Importance: Unknown Status: Unknown -- please build with SSL/TLS enabled https://bugs.launchpad.net/bugs/183840 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 489860] Re: options inet6 breaks fping
** Bug watch added: Debian Bug tracker #558652 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558652 ** Also affects: fping (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558652 Importance: Unknown Status: Unknown -- options inet6 breaks fping https://bugs.launchpad.net/bugs/489860 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 489860] Re: options inet6 breaks fping
** Summary changed: - fping broken in mixed ipv4/ipv6 environment + options inet6 breaks fping ** Description changed: Binary package hint: fping - I'm running a mixed IPv4/IPv6 dual-stack environment. fping seems to - work fine for ipv4 only hosts, and fping6 seems to work fine for ipv6 - only hosts, but when a host can be found via both, it seems that fping - fails for one or the other: - - r...@spooky:~# host firewall - firewall has address 192.168.1.1 - firewall has IPv6 address fe80::2b0:c2af:fa6e:1ee8 - r...@spooky:~# fping firewall - firewall is unreachable - r...@spooky:~# fping 192.168.1.1 - 192.168.1.1 is alive - r...@spooky:~# fping6 fe80::2b0:c2af:fa6e:1ee8 - fe80::2b0:c2af:fa6e:1ee8 is alive - r...@spooky:~# fping6 firewall - firewall is alive - - As you can see, in this example all the fpings worked except for the v4 - fping based on dns lookup. It certainly appears that it's getting - confused by DNS returning a record for the host in question. + fping behaves badly when options inet6 is configured in the resolver. + It appears that the code calls gethostbyname() without checking the + address family of the result. When the resolver returns an AF_INET6 + address, it treats it as IPv4, grabs only part of the address, and + attempts the ping. The ping fails, but without an error indicating why. + Running with -A shows that a nonsensical IPv4 address is being pinged + instead of the expected address. -- options inet6 breaks fping https://bugs.launchpad.net/bugs/489860 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 489860] [NEW] fping broken in mixed ipv4/ipv6 environment
Public bug reported: Binary package hint: fping I'm running a mixed IPv4/IPv6 dual-stack environment. fping seems to work fine for ipv4 only hosts, and fping6 seems to work fine for ipv6 only hosts, but when a host can be found via both, it seems that fping fails for one or the other: r...@spooky:~# host firewall firewall has address 192.168.1.1 firewall has IPv6 address fe80::2b0:c2af:fa6e:1ee8 r...@spooky:~# fping firewall firewall is unreachable r...@spooky:~# fping 192.168.1.1 192.168.1.1 is alive r...@spooky:~# fping6 fe80::2b0:c2af:fa6e:1ee8 fe80::2b0:c2af:fa6e:1ee8 is alive r...@spooky:~# fping6 firewall firewall is alive As you can see, in this example all the fpings worked except for the v4 fping based on dns lookup. It certainly appears that it's getting confused by DNS returning a record for the host in question. ** Affects: fping (Ubuntu) Importance: Undecided Status: New -- fping broken in mixed ipv4/ipv6 environment https://bugs.launchpad.net/bugs/489860 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 441005] Re: upgrade to karmic 9.10: dependency problem of openoffice spoils complete update
I hit this also. Removing the existing openoffice.org-core seems to have worked around it. -- upgrade to karmic 9.10: dependency problem of openoffice spoils complete update https://bugs.launchpad.net/bugs/441005 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 267827] Re: out of date engine causes milter crash
This has not occurred recently, so it does appear that it's been resolved with the new version. ** Changed in: clamav (Ubuntu) Status: Incomplete => Invalid ** Changed in: clamav (Ubuntu) Status: Invalid => Fix Released -- out of date engine causes milter crash https://bugs.launchpad.net/bugs/267827 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 398272] Re: New upstream version
I agree we should push to get this upgraded sooner rather than later. -- New upstream version https://bugs.launchpad.net/bugs/398272 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 324498] Re: update-grub irregularities when using grub-pc
** Changed in: grub2 (Ubuntu) Status: New => Fix Released -- update-grub irregularities when using grub-pc https://bugs.launchpad.net/bugs/324498 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
RE: [Bug 189462] Re: slocate cron job fails if /etc/updatedb.conf notfound
I believe slocate was last shipped in intrepid, so if you define fixed as "it's not there at all", then yes. -- slocate cron job fails if /etc/updatedb.conf not found https://bugs.launchpad.net/bugs/189462 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 376259] Re: BCM4322 doesn't work, FOUND UNSUPPORTED PHY
So for the benefit of those affected... Ubuntu Jaunty is using the b43 driver, which does not support several broadcom N wireless devices, including the BCM4322. Any kernel upgrades in Jaunty are unlikely to change this. You can check the status of your chip here: http://linuxwireless.org/en/users/Drivers/b43 You can try using the STA driver instead, by following the steps here: http://ubuntuforums.org/showthread.php?t=880218 Failing that, you will have to compile your own wl driver using the sources on broadcom's website: http://www.broadcom.com/support/802.11/linux_sta.php ** Summary changed: - BCM4322 doesn't work, FOUND UNSUPPORTED PHY + Some Broadcom chips unsupported by B43 wireless driver [BCM4322] -- Some Broadcom chips unsupported by B43 wireless driver [BCM4322] https://bugs.launchpad.net/bugs/376259 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 289367] Re: camellia cipher does not work in racoon
This issue is still present in Jaunty. -- camellia cipher does not work in racoon https://bugs.launchpad.net/bugs/289367 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 376259] Re: BCM4322 doesn't work, FOUND UNSUPPORTED PHY
** Changed in: linux (Ubuntu) Status: New => Confirmed -- BCM4322 doesn't work, FOUND UNSUPPORTED PHY https://bugs.launchpad.net/bugs/376259 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 369008] [NEW] mdns lookups fail over ipv6
Public bug reported: Binary package hint: libnss-mdns I have avahi running on a couple hosts (Jaunty) in my dual-stack lan. All ipv4 mdns resolution seems to work fine, but ipv6 resolution seems to be failing, even though resolving the same ipv6 hosts works fine using bind. I'm not sure exactly where in the chain the fault lies, but something seems to be amiss. Additionally, a Mac running Bonjour has no problem resolving the same hosts using IPv6. /etc/avahi/avahi-daemon.conf [server] #host-name=foo #domain-name=local #browse-domains=0pointer.de, zeroconf.org use-ipv4=yes use-ipv6=yes #check-response-ttl=no #use-iff-running=no #enable-dbus=yes #disallow-other-stacks=no #allow-point-to-point=no [wide-area] enable-wide-area=yes [publish] #disable-publishing=no #disable-user-service-publishing=no #add-service-cookie=no #publish-addresses=yes #publish-hinfo=yes #publish-workstation=yes #publish-domain=yes #publish-dns-servers=192.168.50.1, 192.168.50.2 #publish-resolv-conf-dns-servers=yes #publish--on-ipv4=yes publish-a-on-ipv6=yes [reflector] #enable-reflector=no #reflect-ipv=no ... r...@host1:/# ping host2 PING host2 (192.168.4.1) 56(84) bytes of data. 64 bytes from host2 (192.168.4.1): icmp_seq=1 ttl=64 time=0.243 ms ^C --- host2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.243/0.243/0.243/0.000 ms r...@host1:/# ping host2.local PING host2.local (192.168.4.1) 56(84) bytes of data. 64 bytes from host2 (192.168.4.1): icmp_seq=1 ttl=64 time=0.212 ms ^C --- host2.local ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.212/0.212/0.212/0.000 ms r...@host1:/# ping6 host2 PING host2(2001:X:X:X::1) 56 data bytes 64 bytes from 2001:X:X:X::1: icmp_seq=1 ttl=64 time=0.189 ms ^C --- host2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.189/0.189/0.189/0.000 ms r...@host1:/# ping6 host2.local unknown host The kicker is, the Mac has no problem with this last lookup, meaning the issue has to be with my linux client implementation: macbookpro:~$ ping6 host2.local PING6(56=40+8+8 bytes) 2001:X:X:X:X:X:X:X --> 2001:X:X:X::1 16 bytes from 2001:X:X:X::1, icmp_seq=0 hlim=64 time=98.522 ms 16 bytes from 2001:X:X:X::1, icmp_seq=1 hlim=64 time=2.524 ms ^C --- host2.local ping6 statistics --- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max = 2.524/50.523/98.522 ms ** Affects: nss-mdns (Ubuntu) Importance: Undecided Status: New -- mdns lookups fail over ipv6 https://bugs.launchpad.net/bugs/369008 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
RE: [Bug 365823] Re: clamav-milter chowns root directory
Looks good to me. -- clamav-milter chowns root directory https://bugs.launchpad.net/bugs/365823 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
RE: [Bug 365823] Re: clamav-milter chowns root directory
Please note by root directory I meant / and not /root. I did have some additional inexplicably clamav owned directories, but the only one that I can reproduce with the latest version is /: r...@prizm:~# apt-get purge clamav-milter Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: clamav clamav-freshclam clamav-base libclamav6 clamav-daemon libtommath0 Use 'apt-get autoremove' to remove them. The following packages will be REMOVED: clamav-milter* 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 528kB disk space will be freed. Do you want to continue [Y/n]? (Reading database ... 166111 files and directories currently installed.) Removing clamav-milter ... * Stopping Sendmail milter plugin for ClamAV clamav-milter [ OK ] Purging configuration files for clamav-milter ... Processing triggers for man-db ... r...@prizm:~# chown root / r...@prizm:~# ls -ld / drwxr-xr-x 21 root root 4096 2009-04-23 20:36 / r...@prizm:~# apt-get -V -t jaunty-proposed install clamav-milter Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: clamav-docs (0.95.1+dfsg-1ubuntu1.1) The following NEW packages will be installed: clamav-milter (0.95.1+dfsg-1ubuntu1.1) 0 upgraded, 1 newly installed, 0 to remove and 45 not upgraded. Need to get 0B/262kB of archives. After this operation, 528kB of additional disk space will be used. Preconfiguring packages ... Selecting previously deselected package clamav-milter. (Reading database ... 166093 files and directories currently installed.) Unpacking clamav-milter (from .../clamav-milter_0.95.1+dfsg-1ubuntu1.1_i386.deb) ... Processing triggers for man-db ... Setting up clamav-milter (0.95.1+dfsg-1ubuntu1.1) ... * Starting Sendmail milter plugin for ClamAV clamav-milter [ OK ] r...@prizm:~# ls -ld / drwxr-xr-x 21 clamav root 4096 2009-04-23 20:36 / r...@prizm:~# ls -l / total 100 drwxr-xr-x 2 root root 4096 2009-04-14 14:32 bin drwxr-xr-x 4 root root 4096 2009-04-17 09:07 boot drwxr-xr-x 13 root root 13860 2009-04-23 20:37 dev drwxr-xr-x 197 root root 16384 2009-04-24 08:57 etc drwxr-xr-x 5 root root 4096 2008-11-13 13:22 home drwxr-xr-x 2 root root 4096 2006-05-07 12:03 initrd drwxrwxr-x 21 root root 12288 2009-04-18 14:46 lib dr-xr-xr-x 143 root root 0 2009-04-23 20:36 proc drwxr-xr-x 52 root root 4096 2009-04-23 17:32 root drwxr-xr-x 2 root root 12288 2009-04-20 20:15 sbin drwxr-xr-x 12 root root 0 2009-04-23 20:36 sys drwxrwxrwt 5 root root 140 2009-04-24 08:59 tmp drwxr-xr-x 14 root root 4096 2008-10-13 10:30 usr drwxr-xr-x 18 root root 4096 2008-12-05 22:43 var -- clamav-milter chowns root directory https://bugs.launchpad.net/bugs/365823 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 365823] [NEW] clamav-milter chowns root directory
Public bug reported: Binary package hint: clamav-milter A clean install of clamav-milter ( 0.95.1+dfsg-1ubuntu1.1) causes the root directory to become owned by the clamav user. This was witnessed breaking ssh chroot environment. ** Affects: clamav (Ubuntu) Importance: Undecided Status: New -- clamav-milter chowns root directory https://bugs.launchpad.net/bugs/365823 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
RE: [Bug 363796] Re: clamav-milter init script fails on pidfile
I have found what I believe is one more bug in this version. For some reason, after doing a clean install I wind up with / owned by the clamav user. I don't know that this is a regression or an existing flaw, but either way it's somewhat bad as it breaks ssh chroots (and maybe other things...). I can open a new bug if necessary, but it would be nice to get the fix into this release if possible. -- clamav-milter init script fails on pidfile https://bugs.launchpad.net/bugs/363796 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
RE: [Bug 363804] Re: clamav-milter logrotate script fails (jaunty)
Looks Good To Me -- clamav-milter logrotate script fails (jaunty) https://bugs.launchpad.net/bugs/363804 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
RE: [Bug 363796] Re: clamav-milter init script fails on pidfile
Looks Good To Me -- clamav-milter init script fails on pidfile https://bugs.launchpad.net/bugs/363796 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
RE: [Bug 363796] Re: clamav-milter init script fails on pidfile
PPA version looks good to me for this bug. -- clamav-milter init script fails on pidfile https://bugs.launchpad.net/bugs/363796 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 363453] Re: clamav-milter requires clamav-daemon in jaunty (?)
This may sound a bit silly, I'm not sure, but why not just prompt the user during upgrade? Several apps are always popping up dialogs for each upgrade cycle (sysstat's log format *always* changes for some reason :). You could just say "The new clamav-milter requires clamav- daemon to be installed. If you're using a remote daemon, make sure to edit /etc/clamav/clamav-milter.conf and add its location. Otherwise, make sure you install clamav-daemon now. [OK]" I'm not sure if apt supports doing more advanced actions like actually asking the user if they want to install clamav-daemon on the spot, but you get the idea. (And yes, I apt-get dist-upgrade.) -- clamav-milter requires clamav-daemon in jaunty (?) https://bugs.launchpad.net/bugs/363453 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 363804] [NEW] clamav-milter logrotate script fails (jaunty)
Public bug reported: Binary package hint: clamav-milter A fresh install of clamav-milter (0.95.1+dfsg-1ubuntu1) creates the following file in logrotate.d: r...@prizm:/tmp# cat /etc/logrotate.d/clamav-milter none { rotate 12 weekly compress delaycompress create 640 clamav adm postrotate /etc/init.d/clamav-milter reload-log > /dev/null endscript } Unfortunately this file is very broken and just errors out whenever logrotate runs it: r...@prizm:/tmp# /etc/cron.daily/logrotate error: clamav-milter:1 unknown option 'none' -- ignoring line error: clamav-milter:1 unexpected text error: clamav-milter:10 unexpected } error: found error in file clamav-milter, skipping r...@prizm:/tmp# /etc/init.d/clamav-milter reload-log * Usage: /etc/init.d/clamav-milter {start|stop|restart|force-reload|status} ** Affects: clamav (Ubuntu) Importance: Undecided Status: New -- clamav-milter logrotate script fails (jaunty) https://bugs.launchpad.net/bugs/363804 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 363796] [NEW] clamav-milter init script fails on pidfile
Public bug reported: Binary package hint: clamav-milter The latest clamav-milter (clamav-milter_0.95.1+dfsg-1ubuntu1) fails to run from a clean install due to "--pidfile" in the init script: r...@prizm:/tmp# apt-get install clamav-milter Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: clamav clamav-base clamav-daemon clamav-freshclam libclamav6 Suggested packages: clamav-docs libclamunrar6 The following NEW packages will be installed: clamav clamav-base clamav-daemon clamav-freshclam clamav-milter libclamav6 0 upgraded, 6 newly installed, 0 to remove and 33 not upgraded. Need to get 0B/23.1MB of archives. After this operation, 25.2MB of additional disk space will be used. Do you want to continue [Y/n]? Preconfiguring packages ... Selecting previously deselected package libclamav6. (Reading database ... 166036 files and directories currently installed.) Unpacking libclamav6 (from .../libclamav6_0.95.1+dfsg-1ubuntu1_i386.deb) ... . Setting up clamav-milter (0.95.1+dfsg-1ubuntu1) ... * Starting Sendmail milter plugin for ClamAV clamav-milter /usr/sbin/clamav-milter: unrecognized option `--pidfile' ERROR: Unknown option passed ERROR: Can't parse command line options [fail] . r...@prizm:/tmp# /etc/init.d/clamav-milter start * Starting Sendmail milter plugin for ClamAV clamav-milter /usr/sbin/clamav-milter: unrecognized option `--pidfile' ERROR: Unknown option passed ERROR: Can't parse command line options [fail] r...@prizm:/tmp# ** Affects: clamav (Ubuntu) Importance: Undecided Status: New -- clamav-milter init script fails on pidfile https://bugs.launchpad.net/bugs/363796 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 363453] Re: clamav-milter requires clamav-daemon in jaunty (?)
I don't use update-manager, but from what I understand it's a graphical applications which may be of little benefit to those of us running servers with no window manager. I can confirm what you said about this only affecting upgrade installs, which is good news at least. The bad news is I also ran into another issue (actually 2) with the latest update this afternoon. First, the upgrade process (and even a --purge) doesn't do anything about old instances of /etc/default/clamav-milter. This is problematic because the init script apparently still reads this file for OPTIONS. Unfortunately, a number of the old options are now invalid, so leaving this file intact breaks the startup if you've declared any commandline options. It also seems the in-box init script is somewhat broken regarding the new milter as well: Setting up clamav-milter (0.95.1+dfsg-1ubuntu1) ... * Starting Sendmail milter plugin for ClamAV clamav-milter /usr/sbin/clamav-milter: unrecognized option `--pidfile' ERROR: Unknown option passed ERROR: Can't parse command line options This I can confirm from a fresh install (no /etc/defaults at all), so it's not an upgrade issue. -- clamav-milter requires clamav-daemon in jaunty (?) https://bugs.launchpad.net/bugs/363453 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 363453] [NEW] clamav-milter requires clamav-daemon in jaunty (?)
Public bug reported: Binary package hint: clamav-milter Up through hardy, clamav-milter didn't require clamav-daemon to be installed and running to work. As of the Jaunty version bump, this no longer appears to be the case. An upgraded canary system produced lots of the following when trying to run milter on a system that doesn't have daemon running: Apr 18 13:03:01 prizm clamav-milter[5091]: No clamd server appears to be available Unfortunately, it doesn't appear that clamav-daemon was ever made a dependency of the clamav-milter package, so any existing installs of milter may break during upgrade, and new installs may fail to run as well. ** Affects: clamav (Ubuntu) Importance: Undecided Status: New -- clamav-milter requires clamav-daemon in jaunty (?) https://bugs.launchpad.net/bugs/363453 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 330735] Re: sed manpage does not document I modifier (case insensitive)
In my opinion, giving partial information in the man page is the worst case scenario. Seeing as it already includes a good number of the available commands, there is significant potential for users to assume that the list is comprehensive. If the owners want to rely explicitly on info pages, they should strip the command list out of the man page entirely and simply leave a note saying "see the info page." Until then, I think leaving holes in the man page is a disservice to users. -- sed manpage does not document I modifier (case insensitive) https://bugs.launchpad.net/bugs/330735 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 330735] [NEW] sed manpage does not document I modifier (case insensitive)
Public bug reported: Binary package hint: sed sed 4.1.5-8 - intrepid The current version of sed appears to support the I modifier: adding /I to a search pattern allows for case insensitive search. Unfortunately, the man page does not document the existence of the flag. ** Affects: sed (Ubuntu) Importance: Undecided Status: New -- sed manpage does not document I modifier (case insensitive) https://bugs.launchpad.net/bugs/330735 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 324498] [NEW] update-grub irregularities when using grub-pc
Public bug reported: Binary package hint: grub-pc After switching to grub-pc in intrepid, I've noticed some irregularities in the behavior of update-grub: 1- It does not seem to respect the default (non-named) images. Event though /boot/vmlinuz exists, update-grub no longer includes it in grub.cfg. update-grub in the old grub package always included these in menu.lst, and it made it much easier to have updates boot themselves by default. 2- It does not order kernels logically. The new grub.cfg tends to order the kernels as follows: vmlinuz-2.6.28-v20 vmlinuz-2.6.28.3-v20 vmlinuz-2.6.28.2-v20 vmlinuz-2.6.27.8-v20 If these were to be put in order of release, we can see that grub is ordering them 2,4,3,1. The oldest image is at the bottom, but the next oldest (the next major version) lands at the top, with the two sub- versions of the latter major version in between. It's clearly not counting the base version without a sub-version in the proper descending order. ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New -- update-grub irregularities when using grub-pc https://bugs.launchpad.net/bugs/324498 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 321049] Re: clock skew causes ntp failure on boot
DISTRIB_ID=Ubuntu DISTRIB_RELEASE=8.10 DISTRIB_CODENAME=intrepid DISTRIB_DESCRIPTION="Ubuntu 8.10" -- clock skew causes ntp failure on boot https://bugs.launchpad.net/bugs/321049 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 321049] [NEW] clock skew causes ntp failure on boot
Public bug reported: Binary package hint: ntp I have a machine which loses time rapidly when shutdown. It has made me very much aware of what seems to be a problem with the ntp setup. ntp always fails on boot. ntpd loads well enough, but the clock skew makes it fail to operate, giving only the following error: time correction of 18001 seconds exceeds sanity limit (1000); set clock manually to the correct UTC time. If I run ntpdate by hand, the clock corrects, and from that point on ntpd runs properly... until the system is taken down again and the process starts over. Looking at the various init and dhcp scripts, ntpdate *should* be running on its own when the system starts, but either it's not running or it's not working. ** Affects: ntp (Ubuntu) Importance: Undecided Status: New -- clock skew causes ntp failure on boot https://bugs.launchpad.net/bugs/321049 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 303737] Re: doesn't accept ipv6 server specificiation
*** This bug is a duplicate of bug 305043 *** https://bugs.launchpad.net/bugs/305043 ** This bug has been marked a duplicate of bug 305043 ntpd does not support ipv6 -- doesn't accept ipv6 server specificiation https://bugs.launchpad.net/bugs/303737 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 189462] Re: slocate cron job fails if /etc/updatedb.conf not found
To summarize the situation: The README.debian in slocate claims that "Secure Locate uses /etc/updatedb.conf which is packaged in 'findutils'. This file is not packaged with Secure Locate." That's all well and good, except evidence indicates that findutils no longer supplies /etc/updatedb.conf. From findutils-4.4.0/debian/changelog: "Drop misnamed /etc/updatedb.conf and include its contents in cron.daily file. (updatedb.conf only configured the cronjob, but not any invocation of updatedb.)" The quick fix would appear to be simply installing the updatedb.conf that ships with slocate. I've created a package below which I believe will accomplish this. slocate_3.1-1.1ubuntu4~4 is available in my PPA: deb http://ppa.launchpad.net/cybrmatt/ubuntu intrepid main deb-src http://ppa.launchpad.net/cybrmatt/ubuntu intrepid main debdiff is attached Please test. ** Attachment added: "slocate_3.1-1.1ubuntu4~4.debdiff" http://launchpadlibrarian.net/21518350/slocate_3.1-1.1ubuntu4%7E4.debdiff -- slocate cron job fails if /etc/updatedb.conf not found https://bugs.launchpad.net/bugs/189462 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 281434] Re: installkernel not creating symlinks in intrepid
This looks like it was fixed at some point. Intrepid no longer creates symlinks as it used to, but it does copy the image files into location with the correct names. I'm not sure why it makes an entire copy of all the files rather than linking, but I'm going to assume it was intentional. ** Changed in: debianutils (Ubuntu) Status: Incomplete => Invalid -- installkernel not creating symlinks in intrepid https://bugs.launchpad.net/bugs/281434 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 295526] Re: Broadcom Corporation BCM43XG will not allow sleep
I can confirm this issue with the latest Intrepid release (12/31/08). Very unfortunate that it prevents any kind of suspend/hibernate on a laptop. -- Broadcom Corporation BCM43XG will not allow sleep https://bugs.launchpad.net/bugs/295526 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 305043] Re: ntpd does not support ipv6
Yes, Looks Good To Me. -- ntpd does not support ipv6 https://bugs.launchpad.net/bugs/305043 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 305043] Re: ntpd does not support ipv6
intrepid-proposed LGTM -- ntpd does not support ipv6 https://bugs.launchpad.net/bugs/305043 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 303737] Re: doesn't accept ipv6 server specificiation
This is a duplicate of Bug #305043. I've posted a test fix there. -- doesn't accept ipv6 server specificiation https://bugs.launchpad.net/bugs/303737 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 305043] Re: ntpd does not support ipv6
Think I've gotten it. Debdiff is attached. New build for testing is in my PPA. deb http://ppa.launchpad.net/cybrmatt/ubuntu intrepid main deb-src http://ppa.launchpad.net/cybrmatt/ubuntu intrepid main ** Attachment added: "ntp_4.2.4p4+dfsg-6ubuntu3~ppa1.debdiff" http://launchpadlibrarian.net/20207237/ntp_4.2.4p4%2Bdfsg-6ubuntu3%7Eppa1.debdiff -- ntpd does not support ipv6 https://bugs.launchpad.net/bugs/305043 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 305043] Re: ntpd does not support ipv6
** Bug watch added: Debian Bug tracker #507806 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507806 ** Also affects: ntp (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507806 Importance: Unknown Status: Unknown -- ntpd does not support ipv6 https://bugs.launchpad.net/bugs/305043 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 305043] Re: ntpd does not support ipv6
This is apparently another instance of glibc 2.8 breakage. See also #249824. Solution is again to define _GNU_SOURCE, though I'm not sure the best place to accomplish that. -- ntpd does not support ipv6 https://bugs.launchpad.net/bugs/305043 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 305043] [NEW] ntpd does not support ipv6
Public bug reported: Binary package hint: ntp The ntp daemon is apparently not being built with IPv6 support, despite the fact that the /etc/ntp.conf it ships with contains IPv6 configurations. The default configuration includes: # By default, exchange time with everybody, but don't allow configuration. ... restrict -6 default kod notrap nomodify nopeer noquery # Local users may interrogate the ntp server more closely. ... restrict ::1 However when starting the daemon, the latter triggers the following error: 3 Dec 23:55:28 ntpd[5215]: getaddrinfo: "::1" invalid host address, ignored ** Affects: ntp (Ubuntu) Importance: Undecided Status: New -- ntpd does not support ipv6 https://bugs.launchpad.net/bugs/305043 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 249824] Re: [intrepid] IPv6 unusable
My package version containing a tilde (1:9.5.0.dfsg.P2-1ubuntu3~ppa3) should work as a half-increment. It's higher than 1:9.5.0.dfsg.P2-1ubuntu2 (current), but should be lower than 1:9.5.0.dfsg.P2-1ubuntu3 (future/final). Assuming this version number or higher will be used by the final push, it will automatically supersede the ppa packages. Of course, you're also free to just remove my ppa from your sources list at any point and install a specific version via apt-get instead. -- [intrepid] IPv6 unusable https://bugs.launchpad.net/bugs/249824 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 249824] Re: [intrepid] IPv6 unusable
I believe parts 1 & 2 have been met sufficiently; if anyone disagrees, please correct me. We've clearly identified the problem, the scope, and the correction. A fix is available in the development release, and a patch is available here for the backport. Subscribers, please test the proposed patch as thoroughly as possible to increase its chances of acceptance. Adding ubuntu-sru, and nominating for Intrepid. -- [intrepid] IPv6 unusable https://bugs.launchpad.net/bugs/249824 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 249824] Re: [intrepid] IPv6 unusable
I've built a patched version for intrepid and uploaded to my PPA: deb http://ppa.launchpad.net/cybrmatt/ubuntu intrepid main deb-src http://ppa.launchpad.net/cybrmatt/ubuntu intrepid main Very preliminary testing looks positive. Will continue running it. Debdiff is attached as well. ** Attachment added: "bind9_9.5.0.dfsg.P2-1ubuntu3~ppa3.diff" http://launchpadlibrarian.net/20172641/bind9_9.5.0.dfsg.P2-1ubuntu3%7Eppa3.diff -- [intrepid] IPv6 unusable https://bugs.launchpad.net/bugs/249824 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 195310] Re: horde3 config diff contains invalid backslashes
** Changed in: horde3 (Ubuntu) Status: Incomplete => Fix Released -- horde3 config diff contains invalid backslashes https://bugs.launchpad.net/bugs/195310 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 274479] Re: ip not being updated and expiring
Doug: Your assertion is not correct. At least for free accounts, they will remove the host if it is neither updated nor acknowledged via the web interface within the required interval. I stopped confirming my host following the resolution of this bug (moving to a different service), and they did in fact remove the host as promised. As Avi pointed out, it is indeed not the fault of the client, but I would argue it most definitely is a limitation (or at very least an annoying requirement) of the service. -- ip not being updated and expiring https://bugs.launchpad.net/bugs/274479 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 177489] Re: loss of masters causing bind to become unresponsive
This was determined to be caused by a new kernel setting (at the time). If net.core.xfrm_larval_drop is not set to 1, bind does not get the blocking behavior it expects on the socket and causes this situation. Setting net.core.xfrm_larval_drop=1 works around it. ** Changed in: bind (Ubuntu) Status: Incomplete => Invalid -- loss of masters causing bind to become unresponsive https://bugs.launchpad.net/bugs/177489 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 296074] Re: dkimproxy tries to install amavisd-new
Thanks Scott. One of these days I'll learn to read the release notes properly. ** Changed in: dkimproxy (Ubuntu) Status: New => Invalid -- dkimproxy tries to install amavisd-new https://bugs.launchpad.net/bugs/296074 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 235800] Re: Can't calibrate elo 3000u touchscreen
** Attachment added: "lspci.gz.gz" http://launchpadlibrarian.net/19599896/lspci.gz.gz ** Changed in: xf86-input-evtouch (Ubuntu) Status: Incomplete => New -- Can't calibrate elo 3000u touchscreen https://bugs.launchpad.net/bugs/235800 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 235800] Re: Can't calibrate elo 3000u touchscreen
** Attachment added: "Xorg.0.log.gz.gz" http://launchpadlibrarian.net/19599893/Xorg.0.log.gz.gz -- Can't calibrate elo 3000u touchscreen https://bugs.launchpad.net/bugs/235800 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 235800] Re: Can't calibrate elo 3000u touchscreen
Still not working I'm afraid. I installed Intrepid and got the monitor on and half working. The display shows up and it does detect touches to the screen, however calibration is still failing. Rather than the old errors, I now at least get a nice failure dialog. It says "No evtouch capable touchscreen found." It requests I mail the lshal output to [EMAIL PROTECTED] which I've now done. I'm also attaching it here. ** Attachment added: "lshal output" http://launchpadlibrarian.net/19599782/evtouch_hal.out.gz.gz -- Can't calibrate elo 3000u touchscreen https://bugs.launchpad.net/bugs/235800 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 296086] Re: clamav-milter warns on inet sockets
Apparmor is not installed on this system. The error message seen part of the init script, indicating it's trying to find a local socket file: if [ $ret = 0 ] && [ "$USE_POSTFIX" = 'yes' ]; then cnt=0 until [ -e "$SOCKET_PATH" ] ; do cnt=`expr "$cnt" + 1` if [ "$cnt" -gt 15 ]; then break fi sleep 2 done if [ -e "$SOCKET_PATH" ]; then chmod g+w $SOCKET_PATH chgrp postfix $SOCKET_PATH else log_warning_msg "Socket not created. Investigate" fi fi -- clamav-milter warns on inet sockets https://bugs.launchpad.net/bugs/296086 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 296086] [NEW] clamav-milter warns on inet sockets
Public bug reported: Binary package hint: clamav-milter It's possible to use an inet socket rather than a local socket with clamav-milter: #SOCKET=local:/var/run/clamav/clamav-milter.ctl SOCKET=inet:8891 If you do this, the init script gets confused, as it's still looking for a physical file. It delays, and then you get "Socket not created. Investigate". The init script should filter out inet: sockets from the portion that does local filesystem socket checks. ** Affects: clamav (Ubuntu) Importance: Undecided Status: New -- clamav-milter warns on inet sockets https://bugs.launchpad.net/bugs/296086 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 296074] [NEW] dkimproxy tries to install amavisd-new
Public bug reported: Binary package hint: dkimproxy The dkimproxy package states amavisd-new is a recommended (but not required) package: [EMAIL PROTECTED]:/tmp# grep amavis dkimproxy-1.0.1/debian/control Recommends: amavisd-new However, attempts to install this package automatically pull in amavisd- new: [EMAIL PROTECTED]:/tmp# apt-get install dkimproxy Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: amavisd-new libarchive-zip-perl libconvert-binhex-perl libconvert-tnef-perl libconvert-uulib-perl libcrypt-openssl-bignum-perl libcrypt-openssl-rsa-perl libio-stringy-perl libmail-dkim-perl libmime-tools-perl libtext-wrapper-perl libunix-syslog-perl Suggested packages: clamav-daemon apt-listchanges libnet-ldap-perl dspam The following NEW packages will be installed: amavisd-new dkimproxy libarchive-zip-perl libconvert-binhex-perl libconvert-tnef-perl libconvert-uulib-perl libcrypt-openssl-bignum-perl libcrypt-openssl-rsa-perl libio-stringy-perl libmail-dkim-perl libmime-tools-perl libtext-wrapper-perl libunix-syslog-perl 0 upgraded, 13 newly installed, 0 to remove and 1 not upgraded. 1 not fully installed or removed. Need to get 1655kB of archives. After this operation, 5337kB of additional disk space will be used. Do you want to continue [Y/n]? n Abort. I see no reason for this; dkimproxy should work fine on its own, and I have no desire to have amavisd on the system. Why is apt trying to force me to install a recommendation? ** Affects: dkimproxy (Ubuntu) Importance: Undecided Status: New -- dkimproxy tries to install amavisd-new https://bugs.launchpad.net/bugs/296074 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 256025] Re: invoke-rc.d procps start loads /etc/syctl.d before /etc/sysctl.conf
I'm partially confused by this bug. I wound up here in the process of filing Bug #292470. It's my observation that in Intrepid final, procps sources /etc/sysctl.conf *first*, which means it is being overridden by /etc/sysctl.d. This is the behavior desired by the requester of this bug, but the bug is not marked Fixed. With that said, I agree with the latter posters here that sysctl.conf should be processed last, giving it the override, and that Ubuntu default configs should be moved to sysctl.d. I disagree with the initial request in this bug to make sysctl.d authoritative (Even though it currently is. Even though this bug is open and the README is wrong). -- invoke-rc.d procps start loads /etc/syctl.d before /etc/sysctl.conf https://bugs.launchpad.net/bugs/256025 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 292470] [NEW] sysctl.conf does not override sysctl.d as claimed
Public bug reported: Binary package hint: procps /etc/sysctl.d/README states that "End-users can use 60-*.conf and above, or use /etc/sysctl.conf directly, which overrides anything in this directory." This is false. /etc/init.d/procps sources /etc/sysctl.conf *first*, which means anything in it is overridden by the contents of /etc/sysctl.d. ... for file in /etc/sysctl.conf /etc/sysctl.d/*.conf ... Bug #256025 appears related to this, but oddly it complains that the README behavior actually occurs, which in the final release of Intrepid it does not. The fix should be one of the following, depending on the outcome of that debate: 1- Fix the init script to source /etc/sysctl.conf last, not first. 2- Fix the README to correctly state that sysctl.d overrides sysctl.conf ** Affects: procps (Ubuntu) Importance: Undecided Status: New -- sysctl.conf does not override sysctl.d as claimed https://bugs.launchpad.net/bugs/292470 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 158582] Re: ifup will fail if IPv6 has been compiled in the kernel
New debdiff with modified ChangeLog. Updated packages for intrepid are now available in my PPA for testing: deb http://ppa.launchpad.net/cybrmatt/ubuntu intrepid main ifupdown_0.6.8ubuntu12~ppa1_i386.deb or https://launchpad.net/%7Ecybrmatt/+archive/+files/ifupdown_0.6.8ubuntu12~ppa1_i386.deb https://launchpad.net/%7Ecybrmatt/+archive/+files/ifupdown_0.6.8ubuntu12~ppa1_amd64.deb ** Attachment added: "ifupdown_0.6.8ubuntu12~ppa1.debdiff" http://launchpadlibrarian.net/19131516/ifupdown_0.6.8ubuntu12%7Eppa1.debdiff -- ifup will fail if IPv6 has been compiled in the kernel https://bugs.launchpad.net/bugs/158582 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 158582] Re: ifup will fail if IPv6 has been compiled in the kernel
** Attachment removed: "ifupdown_0.6.8ubuntu13.debdiff" http://launchpadlibrarian.net/19098773/ifupdown_0.6.8ubuntu13.debdiff -- ifup will fail if IPv6 has been compiled in the kernel https://bugs.launchpad.net/bugs/158582 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 158582] Re: ifup will fail if IPv6 has been compiled in the kernel
@Malte: I'm not really interested in who gets credit for the solution, I was simply trying to add a patch that could hopefully be merged as seamlessly as possible. I had actually intended to upload the fixed package to my ppa for testing, however I'm experiencing technical difficulties preventing me from doing so at the moment. As far as names are concerned, I can't gpg sign a patch/deb as you, so I'm more or less stuck with using my own name there. I believe the change to inet6.defn in your version is technically incorrect. The file appears to be dynamically generated on build, so changes there are not necessary. Linking to the bug is a good idea, however, thanks. -- ifup will fail if IPv6 has been compiled in the kernel https://bugs.launchpad.net/bugs/158582 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 158582] Re: ifup will fail if IPv6 has been compiled in the kernel
debdiff attached ** Attachment added: "ifupdown_0.6.8ubuntu13.debdiff" http://launchpadlibrarian.net/19098773/ifupdown_0.6.8ubuntu13.debdiff -- ifup will fail if IPv6 has been compiled in the kernel https://bugs.launchpad.net/bugs/158582 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 289367] [NEW] camellia cipher does not work in racoon
Public bug reported: Binary package hint: racoon Version 0.7 of ipsec-tools should have added support for the camellia cipher. Indeed, if you man racoon.conf in Intrepid, you'll see that camellia has been added for encryption_algorithm under the proposal and sainfo sections. Unfortunately, trying to enable it is not working as expected. I have the camellia kernel module built and loaded (2.6.26). By changing my encryption_algorithm to "camellia", racoon fails parsing the config file: Oct 25 17:58:20 firewall racoon: DEBUG: reading config file /etc/racoon/racoon.conf Oct 25 17:58:20 firewall racoon: ERROR: /etc/racoon/racoon.conf:21: ";" algorithm mismatched 1 where line 21 is encryption_algorithm camellia; ** Affects: ipsec-tools (Ubuntu) Importance: Undecided Status: New -- camellia cipher does not work in racoon https://bugs.launchpad.net/bugs/289367 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 255776] Re: freeradius lacks eap-tls eap-ttls eap-peap on hardy
*** This bug is a duplicate of bug 183840 *** https://bugs.launchpad.net/bugs/183840 ** This bug has been marked a duplicate of bug 183840 please build with SSL/TLS enabled -- freeradius lacks eap-tls eap-ttls eap-peap on hardy https://bugs.launchpad.net/bugs/255776 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 281434] [NEW] installkernel not creating symlinks in intrepid
Public bug reported: I've been building custom kernels on my Ubuntu installs since Dapper. I recently updated one of my test boxes to the Intrepid beta, and I've noticed that when I install a kernel now, the familiar symlinks (/vmlinuz, System.map, etc), no longer appear in /boot. My kernel- img.conf is identical to a Hardy system which does create the symlinks. ** Affects: debianutils (Ubuntu) Importance: Undecided Status: New -- installkernel not creating symlinks in intrepid https://bugs.launchpad.net/bugs/281434 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 257405] Re: cron.daily job results in "error: GPG validation failed!"
** Changed in: spamassassin (Ubuntu) Status: New => Confirmed -- cron.daily job results in "error: GPG validation failed!" https://bugs.launchpad.net/bugs/257405 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 274479] Re: ip not being updated and expiring
I'm fairly certain other services don't have this limitation. Thanks for your help in clarifying the problem! ** Changed in: no-ip (Ubuntu) Status: New => Invalid -- ip not being updated and expiring https://bugs.launchpad.net/bugs/274479 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 274479] Re: ip not being updated and expiring
Is there a different client that doesn't have this silly limitation? There's nothing in their policy statement that says the client can't update the host within the given interval... only that its current behavior doesn't. -- ip not being updated and expiring https://bugs.launchpad.net/bugs/274479 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 274479] Re: ip not being updated and expiring
No, they've not. It is dynamic, although it goes several months at a time without changing. I would hope this doesn't matter. I've lived in several states, with different providers, and this has always been the case. For the noip2 package to be useful, I would expect it to be able to keep the account alive even when the IP has not changed. -- ip not being updated and expiring https://bugs.launchpad.net/bugs/274479 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 261693] Re: version bump to 0.2.X
I think the intro to the announcement summarizes it best: "Tor 0.2.0.30 switches to a more efficient directory distribution design, adds features to make connections to the Tor network harder to block, allows Tor to act as a DNS proxy, adds separate rate limiting for relayed traffic to make it easier for clients to become relays, fixes a variety of potential anonymity problems, and includes the usual huge pile of other features and bug fixes." The new directory protocol is a big improvement, and the DNS proxy is major new functionality which was lacking in 0.x. I don't think the Tor network will be blocking the previous version in the immediate future, so we should be safe as far as that is concerned. I had hoped to get the request in earlier in the release cycle, but sometimes these things just don't work out. I'll leave it at the discretion of the Ubuntu people to whether this can be included or not. If not, please adjust the bug to apply to the next milestone. -- version bump to 0.2.X https://bugs.launchpad.net/bugs/261693 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 274479] [NEW] ip not being updated and expiring
Public bug reported: Binary package hint: noip2 I've got the noip2 package installed and configured, but for the life of me I can't tell that it's doing anything. Every month I get an email from no-ip saying my hostname is expiring, so the app is clearly not updating my account. I launch it with the -d flag, and all I get is this: Sep 25 12:18:13 host noip2[17762]: v2.1.7 daemon started Sep 25 12:18:13 host noip2[17762]: X.no-ip.com was already set to X. Then, as far as I can tell, nothing. It's running, but the account still gets disabled montly. ** Affects: no-ip (Ubuntu) Importance: Undecided Status: New -- ip not being updated and expiring https://bugs.launchpad.net/bugs/274479 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 267827] [NEW] out of date engine causes milter crash
Public bug reported: I've experienced this with the last couple releases, right up through Hardy. At some point, the clamav engine invariably gets out of date, and clamav in their infinite wisdom starts rejecting freshclam connections: ClamAV update process started at Mon Sep 8 11:25:51 2008 WARNING: Your ClamAV installation is OUTDATED! WARNING: Local version: 0.92.1 Recommended version: 0.94 DON'T PANIC! Read http://www.clamav.net/support/faq main.inc is up to date (version: 48, sigs: 399264, f-level: 35, builder: sven) WARNING: getfile: daily-8185.cdiff not found on remote server (IP: 155.98.64.86) ERROR: getpatch: Can't download daily-8185.cdiff from db.local.clamav.net Downloading daily-8185.cdiff [100%] Downloading daily-8186.cdiff [100%] daily.inc updated (version: 8186, sigs: 16877, f-level: 35, builder: ccordes) WARNING: Your ClamAV installation is OUTDATED! WARNING: Current functionality level = 26, recommended = 35 DON'T PANIC! Read http://www.clamav.net/support/faq Database updated (416141 signatures) from db.local.clamav.net (IP: 65.120.238.5) ... WARNING: Incremental update failed, trying to download daily.cvd Ignoring mirror 168.143.19.95 (has connected too many times with an outdated version) Ignoring mirror 207.57.106.31 (has connected too many times with an outdated version) Trying host database.clamav.net (209.170.150.7)... nonblock_connect: connect timing out (30 secs) Can't connect to port 80 of host database.clamav.net (IP: 209.170.150.7) Ignoring mirror 64.246.134.219 (due to previous errors) ERROR: Can't download daily.cvd from database.clamav.net Giving up on database.clamav.net... Update failed. Your network may be down or none of the mirrors listed in freshclam.conf is working. Check http://www.clamav.net/support/mirror-problem for possible reasons. ... Now this is partially circumstantial evidence, however I never see clamav-milter crash until this freshclam behavior starts in a given release cycle, so I can only assume they're related. At this point, clamav unpredictably but frequently starts crashing with errors similar to the following: Fri Sep 5 07:53:58 2008 -> WARNING: Database has changed, loading updated database LibClamAV Error: cl_load(): Unable to lock database directory: /var/lib/clamav Fri Sep 5 07:56:08 2008 -> ERROR: Unable to lock database directory Fri Sep 5 07:56:08 2008 -> ERROR: Failed to load updated database The only way I've found to work around this is to set up a sitter that restarts clamav-milter when it dies. It would appear that when the out of date engine condition starts to occur, freshclam is locking the database directory longer than it should, and milter in turn is not handling this condition gracefully. ** Affects: clamav (Ubuntu) Importance: Undecided Status: New -- out of date engine causes milter crash https://bugs.launchpad.net/bugs/267827 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 261693] [NEW] version bump to 0.2.X
Public bug reported: The 0.2.X release of Tor has gone stable within the past couple weeks. Debian already has these packages available in testing repositories, as well as in Etch backports. We should strive to include a package in Ubuntu as soon as possible, as the new version provides major feature enhancements as well as many bug fixes over the current 0.1.X releases. ** Affects: tor (Ubuntu) Importance: Undecided Status: New -- version bump to 0.2.X https://bugs.launchpad.net/bugs/261693 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 261326] [NEW] racoon init script fairs poorly when using an unpriv user
Public bug reported: Binary package hint: racoon Racoon offers the option to run as an unprivileged user (See "Privilege separation" in racoon.conf(5)). When attempting to enable these options, the init script has some problems. 1) The unprivileged process attempts to read the .pid file, but fails since it's root owned. 2) Potentially related to #1, the init script fails to stop the racoon daemon using "stop" and "restart." racoon 1:0.6.7-1.1ubuntu1 ** Affects: ipsec-tools (Ubuntu) Importance: Undecided Status: New -- racoon init script fairs poorly when using an unpriv user https://bugs.launchpad.net/bugs/261326 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 244013] [NEW] is_apparmor_present does not check for /sys/module/apparmor
Public bug reported: Binary package hint: apparmor The apparmor init script includes a function called is_apparmor_present. This function attempts to ls /sys/module/apparmor, but doesn't check whether it exists or not first. ls /sys/module/apparmor | grep -qE "^($modules)" ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- is_apparmor_present does not check for /sys/module/apparmor https://bugs.launchpad.net/bugs/244013 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 194623] Re: [hardy] running wondershaper gives 'What is "flowid"? Illegal "police"'
** Changed in: iproute (Ubuntu) Status: New => Confirmed -- [hardy] running wondershaper gives 'What is "flowid"? Illegal "police"' https://bugs.launchpad.net/bugs/194623 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 189462] Re: slocate cron job fails if /etc/updatedb.conf not found
I don't know what thread you were reading, but I didn't see anywhere in the conversation that you linked that slocate would be removed. The conversation focused mainly on the possibility of not shipping it by default in desktop installs. It didn't really even address server installations, nor did it at any point appear to reach a clear conclusion. Regardless, just because something isn't part of the default install doesn't mean that it isn't supported any longer. The vast majority of the apt packages are not installed by default, but they're supported all the same. Any package whose maintainer is the Ubuntu Devs is bound to be kept up to some degree... if they really wanted to cease support for a product it would be removed altogether, which I've seen no evidence of. mlocate has become preferable because the algorithm it uses to update its database is more efficient, resulting in less of a system penalty. It may or may not also be more well supported upstream (but I haven't checked lately). In bash: ~# alias slocate='mlocate' -- slocate cron job fails if /etc/updatedb.conf not found https://bugs.launchpad.net/bugs/189462 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 222804] Re: fail2ban fails to start after reboot
I see no reason this shouldn't meet the SRU requirements. Particularly, this one: - Bugs which represent severe regressions from the previous release of Ubuntu. This includes packages which are totally unusuable, like being uninstallable or crashing on startup. A program which doesn't start at all without manual intervention is a pretty severe regression, IMO. Not to mention that Hardy is an LTS release. -- fail2ban fails to start after reboot https://bugs.launchpad.net/bugs/222804 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 235800] [NEW] Can't calibrate elo 3000u touchscreen
Public bug reported: Binary package hint: xserver-xorg-input-evtouch Device: Elo TouchSystems, Inc. Elo TouchSystems AccuTouch 3000U I've been attempting to get this touchscreen working with Hardy, however I can't get the screen calibrated. Out of the box, the cursor is way off screen somewhere whenever it's touched. I attempted to use the calibrate.sh script, but it's not working properly. The second half of it does seem to work (touching the red X's), but the first half, where one is supposed to find the edges of the screen, does nothing. The window doesn't change at all, and doesn't seem to respond until I press Enter to go onto part 2. The output afterwards gives me the hardcoded max and min of 2 and 0 for both axis. Section "InputDevice" Identifier "TouchScreen" Driver "evtouch" Option "Device" "/dev/input/event2" Option "DeviceName" "TouchScreen" #Option "Calibration" "1" Option "ReportingMode" "Raw" Option "Emulate3Buttons" Option "Emulate3Timeout" "50" Option "SendCoreEvents" "On" EndSection ** Affects: xf86-input-evtouch (Ubuntu) Importance: Undecided Status: New -- Can't calibrate elo 3000u touchscreen https://bugs.launchpad.net/bugs/235800 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 222804] Re: fail2ban fails to start after reboot
Agreed, my systems have not seen this bug fixed yet either. ** Changed in: fail2ban (Ubuntu) Status: Fix Released => Confirmed -- fail2ban fails to start after reboot https://bugs.launchpad.net/bugs/222804 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