[Bug 1918085] Re: Package linux-crashdump in 20.04 configures kernel cmdline crashkernel incorrectly causing lock-up on kernel dump
Also in 22.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918085 Title: Package linux-crashdump in 20.04 configures kernel cmdline crashkernel incorrectly causing lock-up on kernel dump To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1918085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939352] Re: FTBFS 4.13-10ubuntu3 error: ‘numeric_limits’ is not a member of ‘std’
Fix was released in Squid-4.15. Upstream URL for patch is http://www.squid- cache.org/Versions/v4/changesets/squid-4-cbeff29b6088830f14afd587f0fae4f9e0b28369.patch ** Changed in: squid Importance: Unknown => Undecided ** Changed in: squid Status: Unknown => New ** Changed in: squid Remote watch: github.com/onnx/onnx-tensorrt/issues #474 => None ** Changed in: squid Importance: Undecided => Medium ** Changed in: squid Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939352 Title: FTBFS 4.13-10ubuntu3 error: ‘numeric_limits’ is not a member of ‘std’ To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1939352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264313] Re: ls --color hangs for directories linked from network
I do think the fact that a workaround exists is not enough. I really think the default behaviour in Ubuntu of a oft-used command should not create hangs of well over a minute in fairly standard circumstances. It also hangs on links that are not accessible because they have not been Kerberos authenticated or are on unmounted USB devices. So I do think the default should at least be changed here. It is unreasonable default behaviour, not least because it is really unobvious to most users why it happens. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/264313 Title: ls --color hangs for directories linked from network To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/264313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860807] Re: Please support SSL bumping with '--with-openssl' configure option
Please be aware the upstream fix is that Debian Legal and Technical teams finally decided to make it a matter of policy that OpenSSL was to be considered a core part of Debian rather than just a normal third- party library. That opens the GPL exception clause for incompatible core system licenses. I am not sure of the policy position Ubuntu has about OpenSSL. It will need to match that new Debian policy for the package to be imported from Debian with the --with-openssl option intact. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860807 Title: Please support SSL bumping with '--with-openssl' configure option To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1860807/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1684240] Re: Lagging square around mouse pointer
Yes I had this issue described here https://askubuntu.com/questions/1256513/mouse-pointer-on-desktop-is- tailed-by-square-shaped-marks-in-20-04-lts Dell XPS15 9570, Ubuntu 20.04, Linux xps15 5.4.0-48-generic #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux "Fixed" by. Disabling the Settings > Universal Access > Zoom & Pointer Locate. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-workspace in Ubuntu. https://bugs.launchpad.net/bugs/1684240 Title: Lagging square around mouse pointer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-375/+bug/1684240/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1891396] Re: build failure in riscV64
Oops, missed the build version number. >From the build log I see: > checking whether linking without -latomic works... yes A patch adjusting the configure.ac test logic to also check the exchange operator which is missing on riscv64 is the correct way to go. Please submit upstream PR if anyone wants to create and test such a patch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891396 Title: build failure in riscV64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1891396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891396] Re: build failure in riscV64
The upstream patch http://www.squid- cache.org/Versions/v4/changesets/squid-4-f187e5cf415604d4fe839ba57120d846bfa1e672.patch which in includes in Squid-4.12 and later should resolve linking issues with libatomic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891396 Title: build failure in riscV64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1891396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863228] Re: loginctl list-sessions shows ghost sessions that are never completely closed
One last thing if I may: what do you think is better, restart of the service or reboot of the vps? except for the additional logging, is there something I should be aware of when editing the above? Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863228 Title: loginctl list-sessions shows ghost sessions that are never completely closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863228] Re: loginctl list-sessions shows ghost sessions that are never completely closed
Before doing so, is there anything I should be aware of like the consequence of such editing and restarting? You wrote reboot or restart, reboot you mean VPS and restart you mean systemd-logind service? Ofcourse I prefer to restart the service only and not the whole vps, is there a recommended way to do it without breaking anything? I ask because during my searches for the problem, I read that it should be done with cautious. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863228 Title: loginctl list-sessions shows ghost sessions that are never completely closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863228] Re: loginctl list-sessions shows ghost sessions that are never completely closed
I attached the xls because of the indentation problem. Here is the logind output in text (which is ok with indentation). ** Attachment added: "journal-logind.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863228/+attachment/5331729/+files/journal-logind.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863228 Title: loginctl list-sessions shows ghost sessions that are never completely closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863228] Re: loginctl list-sessions shows ghost sessions that are never completely closed
I attached an excel file of the ps -alx command. Regarding the other command, It is long because of the problem :) here is its content Feb 07 10:09:08 vps.server.local systemd[1]: Starting Login Service... Feb 07 10:09:08 vps.server.local systemd-logind[122]: New seat seat0. Feb 07 10:09:08 vps.server.local systemd[1]: Started Login Service. Feb 07 10:09:19 vps.server.local systemd[1]: Stopping Login Service... Feb 07 10:09:19 vps.server.local systemd[1]: Stopped Login Service. Feb 07 10:09:33 vps.server.local systemd[1]: Starting Login Service... Feb 07 10:09:33 vps.server.local systemd-logind[104]: New seat seat0. Feb 07 10:09:33 vps.server.local systemd[1]: Started Login Service. Feb 07 10:10:45 vps.server.local systemd[1]: Stopping Login Service... Feb 07 10:10:45 vps.server.local systemd[1]: Stopped Login Service. Feb 07 10:11:03 vps48064754.local systemd[1]: Starting Login Service... Feb 07 10:11:04 vps48064754.local systemd-logind[163]: New seat seat0. Feb 07 10:11:04 vps48064754.local systemd[1]: Started Login Service. Feb 07 10:13:53 vps48064754.local systemd-logind[163]: New session c1 of user root. Feb 07 10:15:34 vps48064754.local systemd[1]: /lib/systemd/system/systemd-logind.service:32: Unknown lvalue 'RestrictSUIDSGID' in section 'Service' Feb 07 10:17:54 vps48064754.local systemd-logind[163]: New session c2 of user debian-spamd. Feb 07 10:18:23 vps48064754.local systemd-logind[163]: New session c3 of user debian-spamd. Feb 07 10:21:08 vps48064754.local systemd-logind[163]: Removed session c1. Feb 07 10:21:08 vps48064754.local systemd[1]: Stopping Login Service... Feb 07 10:21:08 vps48064754.local systemd[1]: Stopped Login Service. Feb 07 10:21:36 vps48064754.local systemd[1]: Starting Login Service... Feb 07 10:21:36 vps48064754.local systemd-logind[151]: New seat seat0. Feb 07 10:21:36 vps48064754.local systemd[1]: Started Login Service. Then a lot of Feb 07 10:56:52 vps48064754.local systemd-logind[151]: New session cxxx of user domain. Then Feb 07 18:19:18 vps48064754.local systemd[1]: Stopping
[Bug 1863228] Re: loginctl list-sessions shows ghost sessions that are never completely closed
I did loginctl terminate-user domain before so now I have 47 such sessions. domain@domain:~$ ps -alx F UID PID PPID PRI NIVSZ RSS WCHAN STAT TTYTIME COMMAND 4 0 1 0 20 0 232712 10960 ep_pol Ss ?152:21 /lib/systemd/systemd --system --deserialize 12 1 0 2 1 20 0 0 0 kthrea S? 0:00 [kthreadd/79baa9] 1 0 3 2 20 0 0 0 kthrea S? 0:00 [khelper] 4 105 139 1 20 0 189016 988 poll_s Ssl ? 0:03 /usr/sbin/rsyslogd -n 4 0 149 1 20 0 88660 19704 ep_pol Ss ? 1:32 /lib/systemd/systemd-logind 4 0 152 1 20 0 28344 376 hrtime Ss ? 0:02 /usr/sbin/cron -f 4 100 153 1 20 0 48428 1944 ep_pol Ss ? 2:57 /usr/bin/dbus-daemon --system --address=systemd: --4 0 163 1 20 0 196840 18732 poll_s Ssl ? 0:00 /usr/bin/python3 -Es /usr/sbin/firewalld --nofork -1 0 204 1 20 0 10096880 skb_wa Ss ? 0:00 /usr/sbin/saslauthd -a pam -c -m /var/spool/postfix1 0 205 204 20 0 10096892 lock_f S? 0:00 /usr/sbin/saslauthd -a pam -c -m /var/spool/postfix5 118 261 1 20 0 76184 15964 poll_s Ss ? 0:00 postgrey --pidfile=/var/run/postgrey/postgrey.pid -4 106 478 1 20 0 287428 12804 sigsus Ssl ? 0:00 /usr/sbin/named -f -u bind 4 0 489 1 20 0 184288 7800 poll_s Ssl ? 0:00 /usr/bin/python3 /usr/share/unattended-upgrades/una4 0 505 1 20 0 1036648 13412 poll_s Ssl ? 39:19 /usr/bin/python3 /usr/bin/fail2ban-server -xf start4 0 523 1 20 0 72288 916 poll_s Ss ? 0:00 /usr/sbin/sshd -D 0 999 526 1 20 0 4192092 693668 futex_ Sl ? 42:25 /usr/lib/jvm/java-11-openjdk-amd64/bin/java -Djava.1 0 542 1 20 0 24176 256 poll_s Ss ? 0:00 /usr/sbin/xinetd -pidfile /run/xinetd.pid -stayaliv5 0 555 1 20 0 400524 16044 poll_s Ss ? 0:44 /usr/sbin/apache2 -k start 1 0 579 1 20 0 81052 18024 poll_s Ss ? 0:12 /usr/bin/perl /usr/share/usermin/miniserv.pl /etc/u1 0 581 1 20 0 87416 15492 poll_s Ss ? 0:34 /usr/bin/perl /usr/share/webmin/miniserv.pl /etc/we533 3714 555 20 0 400956 9468 ep_pol S? 0:00 /usr/sbin/apache2 -k start 533 3716 555 20 0 400892 9352 SYSC_s S? 0:00 /usr/sbin/apache2 -k start 4 0 5194 1 20 0 76500 1740 ep_pol Ss ? 0:00 /lib/systemd/systemd --user 5 0 5195 5194 20 0 261960 7528 sigtim S? 0:00 (sd-pam) 4 0 5342 1 20 0 289044 2016 poll_s Ssl ? 0:07 /usr/lib/policykit-1/polkitd --no-debug 4 101 5968 1 20 0 71848 156 ep_pol Ss ? 0:00 /lib/systemd/systemd-networkd 4 0 5975 1 20 0 197976 49068 ep_pol Ss ? 0:12 /lib/systemd/systemd-journald 4 0 6087 1 20 0 42092 308 ep_pol Ss ? 0:00 /lib/systemd/systemd-udevd 5 114 6831 1 20 0 120580 2148 poll_s Ss ? 0:02 proftpd: (accepting connections) 4 0 9525 5194 20 0 90368 224 poll_s SLs ? 0:00 /usr/bin/gpg-agent --supervised 1 0 9928 1 20 0 90368 288 poll_s Ss ? 0:00 gpg-agent --homedir /root/.gnupg --use-standard-soc533 10880 555 20 0 400964 9324 SYSC_s S? 0:00 /usr/sbin/apache2 -k start 4 113 11187 1 20 0 302396 6484 pause Ss ? 0:08 /usr/bin/freshclam -d --foreground=true 533 11901 555 20 0 400688 8748 SYSC_s S? 0:00 /usr/sbin/apache2 -k start 4 0 13481 1 20 0 13008 844 poll_s Ss+ ? 0:00 /sbin/agetty -o -p -- \u --noclear tty2 linux 4 0 13482 1 20 0 13008 844 poll_s Ss+ ? 0:00 /sbin/agetty -o -p -- \u --noclear --keep-baud cons4 0 17557 523 20 0 101548 4356 poll_s Ss ? 0:00 sshd: domain [priv] 5 1000 17572 17557 20 0 101548 1960 poll_s R? 0:00 sshd: domain@pts/0 0 1000 17573 17572 20 0 18628 2128 wait Ss pts/0 0:00 -bash 0 1000 17583 17573 20 0 25936 1276 - R+ pts/0 0:00 ps -alx 4 0 18418 1 20 0 317440 1580 ep_pol Ss ? 0:34 php-fpm: master process (/etc/php/7.2/fpm/php-fpm.c533 18419 18418 20 0 317440 1452 skb_wa S? 0:00 php-fpm: pool www 533 18420 18418 20 0 317440 1448 skb_wa S? 0:00 php-fpm: pool www 533 22504 555 20 0 182440 5768 poll_s S? 0:00 /usr/sbin/apache2 -k start 533 23288 555 20 0 400988 9672 SYSC_s S? 0:00 /usr/sbin/apache2 -k start The command journalctl -b -u systemd-logind starts with Feb-07 so there are A LOT of records there. Maybe a grep of something will show only the important stuff? -- You
[Bug 1863228] Re: loginctl list-sessions shows ghost sessions that are never completely closed
Looks "quiet" but I have 1994 sessions in "loginctl list-sessions" domain@domain:~$ ps -elx F UID PID PPID PRI NIVSZ RSS WCHAN STAT TTYTIME COMMAND 5 1000 25901 25885 20 0 101548 1960 ? S? 0:00 sshd: domain@pts/0 0 1000 25902 25901 20 0 18628 2132 wait Ss pts/0 0:00 -bash USER=domain LOGNAME=domain HOME=/home/sto 0 1000 26403 25902 20 0 25936 1276 - R+ pts/0 0:00 ps -elx LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=4 domain@domain:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863228 Title: loginctl list-sessions shows ghost sessions that are never completely closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863228] Re: loginctl list-sessions shows ghost sessions that are never completely closed
I login to domain user using ssh from time to time... as a "bonus", Virtualmin open/close a session for that same user to do its stuff: https://www.cloudmin.com/node/54674 The above is causing the number of ghost sessions to grow even more rapidly Regarding "ps -elx", just to make sure: you want me to run it while I connect (ssh) using domain user? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863228 Title: loginctl list-sessions shows ghost sessions that are never completely closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863228] Re: loginctl list-sessions shows ghost sessions that are never completely closed
I don't mean to sound rude, just want to understand how this is working. I gave it a week and now loginctl list-sessions have 1955 sessions like that and it keeps growing... How the bug reports are handled? Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863228 Title: loginctl list-sessions shows ghost sessions that are never completely closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863228] [NEW] loginctl list-sessions shows ghost sessions that are never completely closed
Public bug reported: I setup a new VPS with ubuntu 18.04.4, including virtualmin/usermin. In auth.log I see a lot of su[12936]: Successful su for domain by root su[12936]: + ??? root:domain systemd-logind[148]: New session c315 of user domain . su[12936]: pam_unix(su:session): session opened for user domain by (uid=0) su[12936]: pam_unix(su:session): session closed for user domain in syslog, I see a lot of systemd[1]: Started Session c314 of user domain. systemd[1]: Started Session c315 of user domain. domain is the user of my virtual server defined in the VPS. c314/c315 increased by 1 each time, every 5 minutes (see explanation below). When running `loginctl list-sessions` those sessions number grow as "active=yes" and "state=closing" and never disappear from the list. a random session as an example: loginctl session-status c315 c315 - domain (1000) Since: Sat 2020-02-08 20:27:08 UTC; 23h ago Leader: 12936 TTY: ??? Remote: user root Service: su; type tty; class user State: closing Unit: session-c315.scope I did a simple test: logged in with ssh, logged out (exit) and re-logged in. I saw 2 sessions in loginctl list-sessions and the previous one, which I obviously closed, never disappeared from the list. as a "bonus": Virtualmin apparently open/close a session for the virtual server user to do its stuff causing the number of ghost sessions to grow forever... I posted this question in server fault, askubuntu, ubuntuforums and virtualmin - no one knew what to tell me. I have no idea what/where to look for... Please advice :) Thanks in advance. FWIW: Someone from virtualmin forum told me that he had a similar problem with debian 9 and it was fixed in debian 10. After a boot I see this, maybe related? Feb 13 06:39:48 domain systemd[1]: Starting User Manager for UID 1000... Feb 13 06:39:48 domain systemd[636]: Failed to create /user.slice/user-1000.slice/user@1000.service/init.scope control group: Permission denied Feb 13 06:39:48 domain systemd[636]: Failed to allocate manager object: Permission denied Feb 13 06:39:48 domain systemd[1]: user@1000.service: Failed with result 'protocol'. Feb 13 06:39:48 domain systemd[1]: Failed to start User Manager for UID 1000 lsb_release -a; uname -a; grep 1000 /etc/passwd No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic Linux domain.com 4.15.0 #1 SMP Mon Dec 9 19:36:21 MSK 2019 x86_64 x86_64 x86_64 GNU/Linux domain:x:1000:1000::/home/domain:/bin/bash ** Affects: 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/1863228 Title: loginctl list-sessions shows ghost sessions that are never completely closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1863228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 640511] Re: squid in lucid adds bogus port number to Host: line if one isn't provided (in original or via vport=)
Squid-2 has long been obsolete upstream. Now that affected Ubuntu are no longer supported we can close. ** Changed in: squid Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/640511 Title: squid in lucid adds bogus port number to Host: line if one isn't provided (in original or via vport=) To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/640511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808861] Re: Problem crashes Unreportable - Invalid core dump: BFD: warning: apport_core is truncated
Something similar here too, with DBUS crashing out, and not generating a complete core dump (though plenty of disk and RAM) un 17 00:10:40 xps15 gjs[2607]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Jun 17 00:10:40 xps15 gjs[2607]: message repeated 8 times: [ g_object_unref: assertion 'G_IS_OBJECT (object)' failed] Jun 17 00:10:40 xps15 systemd[1991]: gnome-terminal-server.service: Main process exited, code=killed, status=15/TERM Jun 17 00:10:40 xps15 systemd[1991]: gnome-terminal-server.service: Succeeded. Jun 17 00:10:45 xps15 gsd-print-notif[2333]: Source ID 3 was not found when attempting to remove it Jun 17 00:10:45 xps15 kernel: [ 8851.668166] rfkill: input handler enabled Jun 17 00:10:45 xps15 systemd[1]: unattended-upgrades.service: Succeeded. Jun 17 00:10:45 xps15 systemd[1991]: Stopping D-Bus User Message Bus... Jun 17 00:10:45 xps15 systemd[1991]: at-spi-dbus-bus.service: Succeeded. Jun 17 00:10:45 xps15 gnome-session[2037]: gnome-session-binary[2037]: WARNING: Lost name on bus: org.gnome.SessionManager Jun 17 00:10:45 xps15 gnome-session[2037]: gnome-session-binary[2037]: CRITICAL: We failed, but the fail whale is dead. Sorry Jun 17 00:10:45 xps15 gnome-session-binary[2037]: WARNING: Lost name on bus: org.gnome.SessionManager Jun 17 00:10:45 xps15 gnome-session-binary[2037]: CRITICAL: We failed, but the fail whale is dead. Sorry Jun 17 00:10:45 xps15 gvfsd[2182]: A connection to the bus can't be made Jun 17 00:10:45 xps15 gnome-shell[2175]: [AppIndicatorSupport-DEBUG] Lost nameorg.kde.StatusNotifierWatcher Jun 17 00:10:45 xps15 gnome-shell[2175]: JS WARNING: [resource:///org/gnome/gjs/modules/signals.js 128]: Too many arguments to method Clutter.Actor.destroy: expected 0, got 1 Jun 17 00:10:45 xps15 systemd[1991]: run-user-1000-gvfs.mount: Succeeded. Jun 17 00:10:45 xps15 systemd[1991]: gvfs-daemon.service: Main process exited, code=killed, status=15/TERM Jun 17 00:10:45 xps15 systemd[1991]: xdg-permission-store.service: Main process exited, code=exited, status=1/FAILURE Jun 17 00:10:45 xps15 tracker-miner-f[2474]: Owner of volume monitor org.gtk.vfs.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts Jun 17 00:10:45 xps15 systemd[1991]: xdg-permission-store.service: Failed with result 'exit-code'. Jun 17 00:10:45 xps15 tracker-miner-f[2474]: Owner of volume monitor org.gtk.vfs.GPhoto2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts Jun 17 00:10:45 xps15 systemd[1991]: gvfs-metadata.service: Succeeded. Jun 17 00:10:45 xps15 kernel: [ 8851.715910] dbus-daemon[2029]: segfault at 0 ip 7fcf20d73e53 sp 7ffefaadc258 error 6 in libdbus-1.so.3.19.9[7fcf20d51000+2d000] Jun 17 00:10:45 xps15 kernel: [ 8851.715930] Code: 89 12 48 89 52 08 48 89 17 c3 0f 1f 44 00 00 48 89 d6 e9 80 fe ff ff 48 8b 46 08 48 39 f0 74 47 48 8b 16 48 89 42 08 48 8b 16 <48> 89 10 48 39 37 74 15 48 c7 46 08 00 00 00 00 48 c7 06 00 00 00 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808861 Title: Problem crashes Unreportable - Invalid core dump: BFD: warning: apport_core is truncated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1808861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816006] Re: /var/run/squid (run_dir) no longer created on start up
Luigi has added a change in Debian 4.5-2 package that should resolve this. ** Also affects: squid (Debian) Importance: Undecided Status: New ** Changed in: squid (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816006 Title: /var/run/squid (run_dir) no longer created on start up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1816006/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1098641] Re: visible_hostname defaults to hostname of first http_port IP, not get_hostname()
** Also affects: squid (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/1098641 Title: visible_hostname defaults to hostname of first http_port IP, not get_hostname() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1098641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794553] Re: squid crashed with SIGABRT in xassert()
IIRC this may be the result of a bug found in the src/ipc/TypedMsgHeader.* GCC-8 patch for 4.1. Debian received the fix for that in the GCC-8 changes formally accepted into 4.2. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794553 Title: squid crashed with SIGABRT in xassert() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1794553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780341] Re: squid should default to more human friendly timestamps
Squid already several contains such other formats. All they take is configuration. The default one is intended for fast machine interpretation, since that is the majority use-case for all Squid installations. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780341 Title: squid should default to more human friendly timestamps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1780341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1022821] Re: squid crashed with SIGSEGV in __find_specmb()
This bug no longer exists in the squid binary packages built from Squid-3 sources in Xenial and later. ** Changed in: squid (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1022821 Title: squid crashed with SIGSEGV in __find_specmb() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1022821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780944] Re: Please provide Squid-4
Ah, okay. So repo related rather than a end-user problem. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780944 Title: Please provide Squid-4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1780944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097032] Re: Please provide GNUTLS support in squid
squid v4 packages are now in Cosmic ** Changed in: squid3 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097032 Title: Please provide GNUTLS support in squid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1097032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793131] Re: FTBFS gcc8
squid 4 packages are now in Cosmic ** Changed in: squid3 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793131 Title: FTBFS gcc8 To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1793131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1416009] Re: Make squid package in 14.04 multithread supported
Squid-4 packages in Cosmic resolve this issue. ** Changed in: squid3 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1416009 Title: Make squid package in 14.04 multithread supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1416009/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780944] Re: Please provide Squid-4
Andreas: I'm working on migrating away from squid-dbg to squid-dbgsym now, so a new upload will happen. FYI: instructions from the the designers of the *-dbgsym system were that the only thing source packages do is drop old *-dbg binary packages from d/control files. debhelper compat level 9+ automation does the upgrade logic. The instructions also stated that maintainers must not attempt any manual dependency or Conflict tricks. Is there something radically different for Ubuntu? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780944 Title: Please provide Squid-4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1780944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780944] Re: Please provide Squid-4
** Description changed: Debian is now providing Squid-4.1. Please update the Ubuntu packages. - This will resolve Ubuntu bug #1097032, bug #16669, and bug #1793131 + This will resolve Ubuntu bug #1097032, bug #16669, bug #1793131, and bug + #1416009. UPDATE:: The v4.2 package now in Debian also contains a fix for bug #1103362. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780944 Title: Please provide Squid-4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1780944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 420729] Re: squid stable permissions problems with log files
This was fixed by the "squid" binary package built from squid3 sources in Ubuntu Xenial and later. ** Changed in: squid (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/420729 Title: squid stable permissions problems with log files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/420729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 223572] Re: ldap_auth library usage
This was fixed by the "squid" binary package built from squid3 sources in Ubuntu Xenial and later. Specifically the ldap_auth helper no longer exists - instead we have a collection of auth helpers using LDAP for different more-specific purposes. ** Changed in: squid (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/223572 Title: ldap_auth library usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/223572/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 594403] Re: cannot be made to cache responses with no LMT/Date/Expires
This was fixed by the "squid" binary package built from squid3 sources in Ubuntu Xenial and later. ** Changed in: squid (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/594403 Title: cannot be made to cache responses with no LMT/Date/Expires To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/594403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 685201] Re: shutdown_lifetime setting behavior does not match doc
Current (upstream) documentation says "until all active sockets are closed" - that means a lot more than just client sockets. ** Changed in: squid (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/685201 Title: shutdown_lifetime setting behavior does not match doc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/685201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 629524] Re: squid not compiled with db_auth
This was fixed by the "squid" binary package built from squid3 sources in Ubuntu Xenial and later. ** Changed in: squid (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/629524 Title: squid not compiled with db_auth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/629524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 695718] Re: squid SIGABRT on bad url_rewriter
This was fixed by the "squid" binary package built from squid3 sources in Ubuntu Xenial and later. ** Changed in: squid (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/695718 Title: squid SIGABRT on bad url_rewriter To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/695718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 958210] Re: squid ABRT due to storeLocateVaryRead()
This was fixed by the "squid" binary package built from squid3 sources in Ubuntu Xenial and later. ** Changed in: squid (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/958210 Title: squid ABRT due to storeLocateVaryRead() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/958210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1416009] Re: Make squid package in 14.04 multithread supported
This is a squid3 (v3.2+) package feature. "squid" package in the affected Ubuntu versions is v2.7. ** Package changed: squid (Ubuntu) => squid3 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1416009 Title: Make squid package in 14.04 multithread supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1416009/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780341] Re: squid should default to more human friendly timestamps
Squid logs are a customized timestamp format based on UNIX times but also including millisecond (and optionally nanosecond) resolution not available in strictly UNIX timestamps. This format and resolution is necessary for accuracy of log information - which is intended more for machine interpretation via log analysis tools, not human. Human timestamps are far to inaccurate and malleable for this type of data recording. They also vary depending on where in the world the reader is located, independent of where the proxy is located. Human calendar systems are a legal fiction, not a technical or scientific measure - the government of any country can redefine them at any time (and some do so even today). So the time of the recording matters as much as the value recorded in human systems. Mapping between the fixed and deterministic Squid log values and a readers local human system is the purpose of log analysis tools and far more easily done from UNIX-like timestamps than other types. For admin who wish to read the logs manually and provide inaccurate data to their analysis tools other formats are configurable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780341 Title: squid should default to more human friendly timestamps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1780341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780944] Re: Please provide Squid-4
** Description changed: Debian is now providing Squid-4.1. Please update the Ubuntu packages. This will resolve Ubuntu bug #1097032 and bug #16669 UPDATE:: The v4.2 package now in Debian also contains a fix for bug - #1103362 + #1103362 and #1793131 ** Description changed: Debian is now providing Squid-4.1. Please update the Ubuntu packages. - This will resolve Ubuntu bug #1097032 and bug #16669 + This will resolve Ubuntu bugs #1097032, #16669, and #1793131 UPDATE:: The v4.2 package now in Debian also contains a fix for bug - #1103362 and #1793131 + #1103362. ** Description changed: Debian is now providing Squid-4.1. Please update the Ubuntu packages. - This will resolve Ubuntu bugs #1097032, #16669, and #1793131 + This will resolve Ubuntu bug #1097032, bug #16669, and bug #1793131 UPDATE:: The v4.2 package now in Debian also contains a fix for bug #1103362. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780944 Title: Please provide Squid-4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1780944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793131] Re: FTBFS gcc8
For the record: All Squid-4+ versions have a hard GCC-5 minimal version requirement. Which should be fine for current Ubuntu. All Squid-3 versions have a GCC-7 or lower build requirement. Optimally GCC-6 or lower, as implemented in the build dependencies for the Debian 3.5.23+ packages. The Squid-4.x packages from Debian all integrate the upstream fix for this, as does the v4.1 package port in cosmic-proposed queue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793131 Title: FTBFS gcc8 To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1793131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787409] Re: apparmor profile incorrect for squidguard usage
Do these settings really need to be in the squid Apparmour profile? Can they be done in a Squidguard profile instead? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787409 Title: apparmor profile incorrect for squidguard usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1787409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780944] Re: Please provide Squid-4
** Description changed: Debian is now providing Squid-4.1. Please update the Ubuntu packages. This will resolve Ubuntu bug #1097032 and bug #16669 + + UPDATE:: The v4.2 package now in Debian also contains a fix for bug + #1103362 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780944 Title: Please provide Squid-4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1780944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780944] Re: Please provide Squid-4
** Summary changed: - Please provide Squid-4.1 + Please provide Squid-4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780944 Title: Please provide Squid-4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1780944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780944] Re: Please provide Squid-4.1
Update FTR: 4.2 is now in the pipeline with the requested merges. Luigi informs me he intends to upload the new version to Debian sometime next week. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780944 Title: Please provide Squid-4.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1780944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780944] Re: Please provide Squid-4.1
Sure. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780944 Title: Please provide Squid-4.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1780944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780944] Re: Please provide Squid-4.1
The biggest thing will be that Ubuntu and Debian used different upgrade paths to move to 'squid' binary names. Most of the rest was pulled upstream for v4. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780944 Title: Please provide Squid-4.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1780944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780944] [NEW] Please provide Squid-4.1
Public bug reported: Debian is now providing Squid-4.1. Please update the Ubuntu packages. This will resolve Ubuntu bug #1097032 and bug #16669 ** Affects: squid3 (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/1780944 Title: Please provide Squid-4.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1780944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 988802] Re: squid3 killed by ABRT signal. assertion failed: disk.cc377: "fd >= 0"
Upstream fixed this bug in release contained in Bionic. ** Changed in: squid3 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/988802 Title: squid3 killed by ABRT signal. assertion failed: disk.cc377: "fd >= 0" To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/988802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759684] Re: squid3 upstream bug 4477 - Linear search through in-memory nodes leads to 100% CPU usage
** Bug watch added: Squid Bugzilla #4477 http://bugs.squid-cache.org/show_bug.cgi?id=4477 ** Also affects: squid via http://bugs.squid-cache.org/show_bug.cgi?id=4477 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/1759684 Title: squid3 upstream bug 4477 - Linear search through in-memory nodes leads to 100% CPU usage To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1759684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711950] Re: New release 3.5.27
Updated packages have been included in Bionic. ** Changed in: squid3 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711950 Title: New release 3.5.27 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1711950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744184] Re: squid 3.3.8 serves duplicate certificates
The official package in Trusty does not contain OpenSSL support. This bug can only happen in unofficial custom builds of Squid. As noted in the ChangeLog upstream have a patch available such builds can use. And Trusty has been superceded by other Ubuntu versions containing that patch. Also please be aware the OpenSSL related code in Squid has been very volatile since 3.2. Best practice for custom builds is to use the latest upstream code instead of rebuilding possibly outdated distro packages. IMO this bug should be closed since it does not actually affect official Ubuntu packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1744184 Title: squid 3.3.8 serves duplicate certificates To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1744184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097032] Re: Please provide GNUTLS support in squid
Update: Squid-4 packages are now available from Debian experimental repository with basic GnuTLS support for reverse- or explicit- proxy use. These currently exclude SSL-Bump, TLS interception and related features. May require the latest Ubuntu or Debian as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097032 Title: Please provide GNUTLS support in squid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1097032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel
** Changed in: linux (Ubuntu) Assignee: (unassigned) => tovagliari amos (tovatamos) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734147 Title: corrupted BIOS due to Intel SPI bug in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1734147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712668] Re: squid3: ftbfs with gcc7: dynamic exception specifications are deprecated
FWIW you managed to submit 6 identical bug reports upstream. The ID of the first was http://bugs.squid-cache.org/show_bug.cgi?id=4759, I've added the explanation there as to why I am not backported the particular patch upstream. There are probably also some other changes in corner features that got bundled in with other large Squid-4+ features or cosmetic patches that disqualify them in their current forms. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712668 Title: squid3: ftbfs with gcc7: dynamic exception specifications are deprecated To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1712668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1572715] Re: Pinger crashed after squid installation
Backtrace information is required to fix this. The logs provided do not contain any mention of squid or pinger process. ** Changed in: squid3 (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1572715 Title: Pinger crashed after squid installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1572715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682736] Re: after 200 GB squid restart http://bugs.squid-cache.org/show_bug.cgi?id=3279
Why delete your data? that upstream bug being logged is just Squid informing you that it cannot perform If-Modified-Since (IMS) revalidation with an object. As it updates that object with a new fetch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682736 Title: after 200 GB squid restart http://bugs.squid- cache.org/show_bug.cgi?id=3279 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1682736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1679403] Re: Missing dep8 tests
The basic test that Squid application will start is already done by the squid package DEP-8 tests. Though that could be repeated as a test for this package with the simpler installation of only squid, squidclient and squid-langpack packages. What seems to be missing is a test that the right Content-Language error response is returned by Squid given an Accept-Language input header. A default installation of squid should reject all traffic, so is easy to test for that. Are there any other specific DEP-8 tests preferred for a package which simply installs translation files for another package? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1679403 Title: Missing dep8 tests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid-langpack/+bug/1679403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1679784] Re: package shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Crashed on
On 6 April 2017 at 01:03, Steve Langasek <steve.langa...@canonical.com> wrote: > Glad to know that you were able to resolve the problem. Can you still > answer the question from my previous mail so that we're able to help > other users avoid this problem? I.e.: > > > Can you please describe exactly how you went about installing the nvidia > > driver, step by step? What did you click on at each step, etc. > Of course, Once the OS was installed. Reboot (at which point I probably should have disabled the Secure Boot in the BIOS). I avoided using the gui to do the updates, because it hung during the update in my previous attempt (rendering the system unbootable -- went to mauve screen with no text [not sure if this would have been resolved by disabling SB in BIOS though as I just went for a re-install]). Looking around it was suggested that I should try using the CLI to do the upgrade. I think the main issue was the option to disable secure boot during the install process did not persist, so when upgrading and installing certain things that needed SB disabled this caused a problem. I'm not sure why this worked with the CLI but didn't than the Software Updater. So I did this (and while it did work): 1. Install OS 2. $ sudo apt-get update 3. $ sudo apt-get dist-upgrade 4. opened the Settings >> Software & Updates >> Additional Drivers [selected the now installed NVIDIA driver in place of the Xorg one] 5. Reboot 6. Disable Secure Boot in BIOS 7. Fin. But probably should have done this: 1. Install OS 2. Reboot 3. Disable Secure Boot in BIOS 4. $ sudo apt-get update 5. $ sudo apt-get dist-upgrade 6. opened the Settings >> Software & Updates >> Additional Drivers [selected the now installed NVIDIA driver in place of the Xorg one] 7. Reboot 8. Fin. Anway hope that helps. -- - Amos Folarin -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1679784 Title: package shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Crashed on changing from Xorg video driver to NVIDIA driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1679784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1679784] Re: package shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Crashed on
On 4 April 2017 at 19:19, Steve Langasek <steve.langa...@canonical.com> wrote: > Processing triggers for shim-signed > (1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1) > ... > Running in non-interactive mode, doing nothing. > dpkg: error processing package shim-signed (--configure): > subprocess installed post-installation script returned error exit status 1 > > This shows that shim needs to interact with you in order to disable > secureboot on your system; this is correct, if you are installing the > nvidia modules you need SB disabled so that kernel module signatures are > not enforced. Thanks -- I was presented with the option to disable the SB during the install. But that didn't persist after reboot, I realised that the once I disabled the UEFI-Windows Secure boot in the BIOS the problems went away. -- - Amos Folarin -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1679784 Title: package shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Crashed on changing from Xorg video driver to NVIDIA driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1679784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1679784] [NEW] package shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Crashed on ch
Public bug reported: I've encountered this repeatedly. In the first installation -- on updating via Software Updater, this crashed on upgrading the shim-signed package. On suggestions from here: I upgrade the system via CLI, i.e. dist-upgrade. This seemed to work, however when I now try to swap the display driver, from xorg --> nvidia. This now triggered the same issue. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Tue Apr 4 18:21:32 2017 DuplicateSignature: package:shim-signed:1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 Processing triggers for shim-signed (1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1) ... Running in non-interactive mode, doing nothing. dpkg: error processing package shim-signed (--configure): subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-04-04 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: shim-signed Title: package shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shim-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial ** Attachment added: "crashed gui image" https://bugs.launchpad.net/bugs/1679784/+attachment/4854665/+files/Screenshot%20from%202017-04-04%2018-37-25.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1679784 Title: package shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Crashed on changing from Xorg video driver to NVIDIA driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1679784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1659567] Re: empty ACL warning during cron.daily/logrotate
There is no way that I'm aware of in any current Squid. The check is a generic validity check used for all ACLs. Whether it is 'harmless' depends on future events at the time of checking. So just silencing or ignoring would leave a lot of nasty misconfigurations quietly accepted. That said; for an automated rotate 2>/dev/null seems reasonable. These types of thing should be caught and fixed on the previous startup or manual rotate attempts. Long-term I think we are going to have to add an explicit flag to indicate whether an ACL is allowed to be empty or not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1659567 Title: empty ACL warning during cron.daily/logrotate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1659567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665292] Re: Squid 3.5.12-1ubuntu7.3 - Xenial - SLOW Upload speed
FYI: If it was upstream then I suspect it is most likely this upstream change, none of the others had much performance gain in upstream tests: http://www.squid-cache.org/Versions/v3/3.5/changesets/squid-3.5-14061.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665292 Title: Squid 3.5.12-1ubuntu7.3 - Xenial - SLOW Upload speed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1665292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1550539] Re: VMWare network interface name change with wily → xenial upgrade
I just encountered this bug today when upgrading from a fully updated 14.04 server to 16.04 using do-release-upgrade. My static IP configured in /etc/network/interfaces was configured to come up on eth0. Logging in on the console and replacing eth0 with ens32 in that interfaces file and rebooting fixed things. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1550539 Title: VMWare network interface name change with wily → xenial upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1550539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1589567] Re: /usr/lib/squid/pinger:*** Error in `(pinger)': free(): invalid pointer: ADDR ***
Fix upstream included in 3.5.23-1ubuntu1. ** Changed in: squid3 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1589567 Title: /usr/lib/squid/pinger:*** Error in `(pinger)': free(): invalid pointer: ADDR *** To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1589567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1585828] Re: /usr/lib/squid/pinger:11:memcpy:Ip::Address::operator:Ip::Address::operator:Icmp6::Recv:main
Upstream fix included in 3.5.23-1ubuntu1. ** Changed in: squid3 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1585828 Title: /usr/lib/squid/pinger:11:memcpy:Ip::Address::operator:Ip::Address::operator:Icmp6::Recv:main To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1585828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644538] Re: Please sync Squid 3.5 latest from Debian
Thanks. Yes, I recall a discussion about that change in the early 'installation script failure' bug reports, the one where others in the Ubuntu team got involved and the squid.maintscript got added. But I too can't find which one right now. - We have not had any repots of similar behaviour from Debian users, but did have several reports about the issue the lack of that init script line caused. So in balance I am procrastinating on taking it until Debian has a documented need/bug. The issue should disappear entirely with the upcoming 4.x package. I'm pulling in the adduser and Vcs-Browser patches. Though please note there was some discussion in debian-devel recently about these URLs that concluded the /cgit/ path segment should be /git/ so as not to depend on the cgit tool specifically. The web server now handles redirection itself from the generic URL syntax. I still dont think the snakeoil patch in its current form is correct for squid/3.x packages. The code to use those certs is not even compiled so at the very least a Depends relationship is bogus. The squidclient/3.x could Recommend since it supports HTTPS, but that is a separate package. And the documentation note I suspect has fooled at least some people into thinking they can use the HTTPS config options already. The rest it will need some testing. I hope to have some time for that this week to try to further minimize the diff, but no guarantees. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644538 Title: Please sync Squid 3.5 latest from Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1644538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644538] Re: Please sync Squid 3.5 latest from Debian
Any progress? I'm getting pings upstream about newer Ubuntu versions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644538 Title: Please sync Squid 3.5 latest from Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1644538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1560429] Re: squid3: segfault when ftp passive mode is not available
Workaround is to configure "ftp_eprt off" for now. A possible fix patch is available at upstream Squid Project in 3.5.23 release. Though we are not sure of completeness yet so the upstream bug report is staying open for now. ** Bug watch added: Debian Bug tracker #793473 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793473 ** Also affects: squid3 (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793473 Importance: Unknown Status: Unknown ** Bug watch added: Squid Bugzilla #4004 http://bugs.squid-cache.org/show_bug.cgi?id=4004 ** Also affects: squid via http://bugs.squid-cache.org/show_bug.cgi?id=4004 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/1560429 Title: squid3: segfault when ftp passive mode is not available To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1560429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613914] Re: squid upgrade fails when user has custom cache_dir
Having a cache_dir at all is non-default. Squid-3 default is to run with a memory-only cache. The /var/spool/squid path is used as default run- time working directory. Which reminds me the proxies low-privilege user account is tied via home directory to the location the original machine install was done with. That probably has not been updated since before Trusty. Symlinks and mount points, either on the cache_dir directory, or below it need to be accounted for. As do SELinux policies, AppArmour policies - both the system ones and custom changes which do not show up in the squid.conf paths. Then there is the issue of other custom tools interacting with the cache_dir data. Not common but when it does happen it's usually custom software outside the package tracking system, which we dont have a clue about whether it can cope with the move. IMHO just leave it, the gain is cosmetic at best and surprisingly hard to do correctly without local knowledge only the admin has. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613914 Title: squid upgrade fails when user has custom cache_dir To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1613914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644538] Re: Please sync Squid 3.5 latest from Debian
Pretty sure it fixes bug #1585828. It should also fix bug #1572715 and bug #1589567 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644538 Title: Please sync Squid 3.5 latest from Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1644538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1585828] Re: /usr/lib/squid/pinger:11:memcpy:Ip::Address::operator:Ip::Address::operator:Icmp6::Recv:main
I believe this was fixed upstream by http://www.squid- cache.org/Versions/v3/3.5/changesets/squid-3.5-14015.patch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1585828 Title: /usr/lib/squid/pinger:11:memcpy:Ip::Address::operator:Ip::Address::operator:Icmp6::Recv:main To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1585828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1390132] Re: Cannot change the maximum number of filedescriptors
This was fixed upstream in 3.3.11. So the Squid v3.5 package in Xenial and later is fixed. ** Changed in: squid3 (Ubuntu) Status: Confirmed => Fix Released ** Bug watch added: Squid Bugzilla #3970 http://bugs.squid-cache.org/show_bug.cgi?id=3970 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1390132 Title: Cannot change the maximum number of filedescriptors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1390132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1390132] Re: Cannot change the maximum number of filedescriptors
For the record upstream patch is at http://bugs.squid- cache.org/show_bug.cgi?id=3970 but requires the build system to be re- bootstrapped so it cannot be easily applied to downstream packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1390132 Title: Cannot change the maximum number of filedescriptors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1390132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1390132] Re: Cannot change the maximum number of filedescriptors
Oops, that was the bug. I mean the patch is http://www.squid- cache.org/Versions/v3/3.3/changesets/squid-3.3-12662.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1390132 Title: Cannot change the maximum number of filedescriptors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1390132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644538] [NEW] Please sync Squid 3.5 latest from Debian
Public bug reported: Debian has a newer squid version (3.5.22) than Ubuntu that fixes several of the open bugs. ** Affects: squid3 (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/1644538 Title: Please sync Squid 3.5 latest from Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1644538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1613914] Re: squid upgrade fails when user has custom cache_dir
All these upgrade failures are because the Unbuntu package touches the cache_dir directory locations on upgrades. The upstream Debian package intentionally does not touch any existing cache_dir locations even if they contain the old 'squid3' folder names in order avoid this type of problem. Can somebody please revert that part of the install/upgrade scripts? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1613914 Title: squid upgrade fails when user has custom cache_dir To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1613914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1578940] Re: package squid3 3.3.8-1ubuntu6.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1568955 *** https://bugs.launchpad.net/bugs/1568955 ** This bug has been marked a duplicate of bug 1568955 package squid (not installed) failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1578940 Title: package squid3 3.3.8-1ubuntu6.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1578940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1617072] Re: package squid 3.5.12-1ubuntu7.2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1
*** This bug is a duplicate of bug 1613914 *** https://bugs.launchpad.net/bugs/1613914 ** This bug is no longer a duplicate of bug 1625569 package squid 3.5.12-1ubuntu7.2 failed to install%Fupgrade: subprocess installed post-installation script returned error exit status 1 ** This bug has been marked a duplicate of bug 1613914 squid upgrade fails when user has custom cache_dir -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1617072 Title: package squid 3.5.12-1ubuntu7.2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1617072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1625569] Re: package squid 3.5.12-1ubuntu7.2 failed to install%Fupgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1613914 *** https://bugs.launchpad.net/bugs/1613914 ** This bug has been marked a duplicate of bug 1613914 squid upgrade fails when user has custom cache_dir -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1625569 Title: package squid 3.5.12-1ubuntu7.2 failed to install%Fupgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1625569/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1528966] Re: error from /etc/resolvconf/update-libc.d/squid3
There should not be any such thing as /etc/resolvconf/update- libc.d/squid3 on a fresh Xenial install. The package and all its paths and scripts are now just 'squid'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1528966 Title: error from /etc/resolvconf/update-libc.d/squid3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1528966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1617072] Re: package squid 3.5.12-1ubuntu7.2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1
*** This bug is a duplicate of bug 1625569 *** https://bugs.launchpad.net/bugs/1625569 ** This bug has been marked a duplicate of bug 1625569 package squid 3.5.12-1ubuntu7.2 failed to install%Fupgrade: subprocess installed post-installation script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1617072 Title: package squid 3.5.12-1ubuntu7.2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1617072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1620120] Re: Segfault in QDevelop -> libc
** Package changed: squid3 (Ubuntu) => qdevelop (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1620120 Title: Segfault in QDevelop -> libc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qdevelop/+bug/1620120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1391159] Re: squid3 is not built with helper /usr/lib/squid3/ext_time_quota_acl
Workaround is to build Squid3 yourself from source package with the helper enabled. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1391159 Title: squid3 is not built with helper /usr/lib/squid3/ext_time_quota_acl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1391159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1618356] [NEW] Calendar misapplying screen orientation information?
Public bug reported: Google calendar app works fine on a normally orientated screen. However for a 90 degree orientated screen it appears to interpret it as a 270 orientated one, and the contents of the window (but not the window itself) flip round so that the calendar etc is upside down. This is a peculiar bug, and manifests itself in my case on a dual screen display with one screen differently orientated. This appeared after LTS upgrade to Ubuntu 16.04.1 unity-webapps-googlecalendar: Version 2.4.16+16.04.20151119-0ubuntu1. ** Affects: unity-webapps-googlecalendar (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/1618356 Title: Calendar misapplying screen orientation information? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-webapps-googlecalendar/+bug/1618356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1611185] Re: Error : Opening the cache
What make you think this is a bug in Squid? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611185 Title: Error : Opening the cache To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1611185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576549] Re: Squid3 : Disable sslv3 if system is built with no sslv3
The Squid packages available in Xenial and later already contain a fix from upstream. ** Changed in: squid3 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576549 Title: Squid3 : Disable sslv3 if system is built with no sslv3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1576549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1571174] Re: package squid3 failed to install/upgrade: dependency problems - leaving triggers unprocessed
** Summary changed: - package squid3 3.3.8-1ubuntu16.2 failed to install/upgrade: dependency problems - leaving triggers unprocessed + package squid3 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1571174 Title: package squid3 failed to install/upgrade: dependency problems - leaving triggers unprocessed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1571174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576531] Re: package squid 3.5.12-1ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1571174 *** https://bugs.launchpad.net/bugs/1571174 ** This bug has been marked a duplicate of bug 1571174 package squid3 3.3.8-1ubuntu16.2 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576531 Title: package squid 3.5.12-1ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1576531/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576938] Re: package squid3 not installed failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1571174 *** https://bugs.launchpad.net/bugs/1571174 ** This bug is no longer a duplicate of bug 1576531 package squid 3.5.12-1ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 ** This bug has been marked a duplicate of bug 1571174 package squid3 3.3.8-1ubuntu16.2 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576938 Title: package squid3 not installed failed to install/upgrade: dependency problems - leaving triggers unprocessed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1576938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576645] Re: package squid3 3.5.12-1ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1571174 *** https://bugs.launchpad.net/bugs/1571174 ** This bug is no longer a duplicate of bug 1576531 package squid 3.5.12-1ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 ** This bug has been marked a duplicate of bug 1571174 package squid3 3.3.8-1ubuntu16.2 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576645 Title: package squid3 3.5.12-1ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1576645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576936] Re: squid3 died during trusty->xenial upgrade
*** This bug is a duplicate of bug 1571174 *** https://bugs.launchpad.net/bugs/1571174 ** This bug has been marked a duplicate of bug 1571174 package squid3 3.3.8-1ubuntu16.2 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576936 Title: squid3 died during trusty->xenial upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1576936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576938] Re: package squid3 not installed failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1576531 *** https://bugs.launchpad.net/bugs/1576531 ** This bug has been marked a duplicate of bug 1576531 package squid 3.5.12-1ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576938 Title: package squid3 not installed failed to install/upgrade: dependency problems - leaving triggers unprocessed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1576938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576645] Re: package squid3 3.5.12-1ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1576531 *** https://bugs.launchpad.net/bugs/1576531 ** This bug has been marked a duplicate of bug 1576531 package squid 3.5.12-1ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576645 Title: package squid3 3.5.12-1ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1576645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1214379] Re: pinger crashed with SIGSEGV in malloc_consolidate()
Can you please provide a backtrace from the new crash? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1214379 Title: pinger crashed with SIGSEGV in malloc_consolidate() To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1214379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1563202] Re: Calamaris 2.99.4.0-19 does not understand 'PINNED' method in squid3 3.3.8-1ubuntu6.6 (trusty)
This was fixed in the package in 15.10 Wily. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1563202 Title: Calamaris 2.99.4.0-19 does not understand 'PINNED' method in squid3 3.3.8-1ubuntu6.6 (trusty) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamaris/+bug/1563202/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1235681] Re: squid3 always run with -N option, incompatible with SMP option (workers)
This is fixed in the squid package now available in Xenial, which removes upstart integration. ** Changed in: squid3 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1235681 Title: squid3 always run with -N option, incompatible with SMP option (workers) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1235681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1547640] Re: proxy tries ipv6 and gets 503 when no ipv6 routes
This is fixed in the squid package now available in Xenial. ** Changed in: squid3 (Ubuntu Xenial) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1547640 Title: proxy tries ipv6 and gets 503 when no ipv6 routes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1547640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1214379] Re: pinger crashed with SIGSEGV in malloc_consolidate()
This is fixed in the squid package now available in Xenial. ** Changed in: squid3 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1214379 Title: pinger crashed with SIGSEGV in malloc_consolidate() To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1214379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532560] Re: pinger crash every night in IcmpPinger::Recv
This is fixed in the squid package now available in Xenial. ** Changed in: squid3 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532560 Title: pinger crash every night in IcmpPinger::Recv To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1532560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1414754] Re: /etc/logrotate.d/squid3 fails to execute sarg-reports
This is fixed in the squid package now available in Xenial. ** Changed in: squid3 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1414754 Title: /etc/logrotate.d/squid3 fails to execute sarg-reports To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1414754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
