Hello Seth, or anyone else affected,
Accepted glibc into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/glibc/2.31-0ubuntu9.5
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
I tested an upgrade from 0ubuntu9.2 to 0ubuntu9.4 in a vm and could not
reproduce this problem.
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I'm more interested in people updating from the version currently in
updates to the version currently in proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926379
Title:
stack smashing attack
What kinds of tests are we hoping for, here? From people who never
backed out the broken glibc manually? (This might be a difficult group
to reach.)
Or from just anyone, to try to find out if the revert and new fixes were
done correctly?
Thanks
--
You received this bug notification because you
Hello Seth, or anyone else affected,
Accepted glibc into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/glibc/2.31-0ubuntu9.4
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
So I don't know exactly what was going on with sarnold's machine but I
now finally understand why the 0ubuntu9.3 update caused problems:
The tls accounting patch added a glibc tunable
(https://www.gnu.org/software/libc/manual/html_node/Tunables.html). A
tunable is defined internally as a name and
There is a WIP branch to prevent upgrades from 2.31-0ubuntu9.3 and cause
crashes again on that path:
https://code.launchpad.net/~rbalint/ubuntu/+source/glibc/+git/glibc/+ref/ubuntu/focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: glibc (Ubuntu)
Assignee: Balint Reczey (rbalint) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926379
Title:
stack smashing attack detected in bash host tab
We're also seeing this with rsyncd:
| Apr 28 09:35:04 behaim rsync[2152929]: *** stack smashing detected
***: terminated
>From apt history logs:
| Upgrade: libldap-2.4-2:amd64 (2.4.49+dfsg-2ubuntu1.7,
2.4.49+dfsg-2ubuntu1.8), libc6-dev:amd64 (2.31-0ubuntu9.2, 2.31-0ubuntu9.3),
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: glibc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926379
Title:
** Changed in: glibc (Ubuntu)
Assignee: (unassigned) => Balint Reczey (rbalint)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926379
Title:
stack smashing attack detected in bash host tab
Thank you for the bug report.
The update has been reverted, please downgrade glibc binary packges to
2.31-0ubuntu9.2 until the new update becomes available.
The problem seems to be caused by the fix for LP: #1914044.
** Tags added: regression-update
--
You received this bug notification
I couldn't install the debug symbols:
bash-dbgsym : Depends: bash (= 5.0-6ubuntu1) but 5.0-6ubuntu1.1 is to
be installed
And I had to add a Package: bash line to my crash file..
Here's the frames that look most likely related:
#13 0x7f29177a85fa in _dl_find_dso_for_object () from
Possibly a duplicate of bug LP: #1926355
https://bugs.launchpad.net/bugs/1926355
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926379
Title:
stack smashing attack detected in bash host tab
14 matches
Mail list logo
