We sew this behavior too but at LTP's master branch (ff13d67503a0) and
on top SUSE SLES OS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059103
Title:
ubuntu_ltp: fs testsuite causing tainted
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
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
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
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.
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.
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
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,
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
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
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
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...
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
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
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
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,
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):
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.
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:
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,
** 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,
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.
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
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.
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:
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
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
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
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+
** 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
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.
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:
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.
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
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.
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.
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.
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.
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
** 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
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
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
** 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
** 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
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.
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:
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.
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
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
** 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
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
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
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
** 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 ker
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
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
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
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
; 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.launchpa
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 rec
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
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
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
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
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:***
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:
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
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
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
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
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
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:
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
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
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
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
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
*** 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
*** 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
*** 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
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.
*** 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
** 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:
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
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
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:
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.
** 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
*** 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
*** 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
*** 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
*** 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
*** 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
*** 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
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
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
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.
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
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:
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
1 - 100 of 423 matches
Mail list logo
