https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216606
longw...@incore.de changed:
What|Removed |Added
CC||longw...@incore.de
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217231
Bug ID: 217231
Summary: OpenSSL issue for qbittorrent and FreeCAD ports.
Product: Base System
Version: 11.0-STABLE
Hardware: Any
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216606
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-bugs@FreeBSD.org|lini...@freebsd.org
--- Comment #2
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217231
Mark Linimon changed:
What|Removed |Added
Version|11.0-STABLE |Latest
Component|bin
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=165471
--- Comment #5 from commit-h...@freebsd.org ---
A commit references this bug:
Author: emaste
Date: Sun Feb 19 17:23:28 UTC 2017
New revision: 313948
URL: https://svnweb.freebsd.org/changeset/base/313948
Log:
bsdgrep: fix EOF handling wit
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=165471
Ed Maste changed:
What|Removed |Added
Assignee|freebsd-bugs@FreeBSD.org|ema...@freebsd.org
Flags|
To view an individual PR, use:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id).
The following is a listing of current problems submitted by FreeBSD users,
which need special attention. These represent problem reports covering
all versions including experimental development code and ob
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217239
Bug ID: 217239
Summary: head (e.g.:) -r313864 arm64 vs. jemalloc without
MALLOC_PRODUCTION: various examples of tbin->avail
being zero lead to SIGSEGV's
Product: Base
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217138
--- Comment #6 from Mark Millard ---
See also bugzilla 217239 for another type of arm64
specific problem with jemalloc without
MALLOC_PRODUCTION.
--
You are receiving this mail because:
You are the assignee for the bug.
__
Hi,
When I start X with one of the libGL packages installed, I get an error message
in ~/.xsession-errors
libGL error: MESA-LOADER: failed to retrieve device information
libGL error: image driver extension not found
libGL error: failed to load driver: radeon
libGL error: failed to open drm device:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217239
--- Comment #1 from Mark Millard ---
I did not make clear one important point:
These are occasional failures during my experimental
builds. I can not make them fail on demand.
At this point I've no clue what may control the
intermittent n
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217239
--- Comment #1 from Mark Millard ---
I did not make clear one important point:
These are occasional failures during my experimental
builds. I can not make them fail on demand.
At this point I've no clue what may control the
intermittent n
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217239
Shawn Webb changed:
What|Removed |Added
CC||shawn.w...@hardenedbsd.org
--- Commen
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217239
--- Comment #4 from Mark Millard ---
[I have no clue why my prior comment showed up twice.]
I also forgot to list the counts of example core files:
script: 3
powerd: 3
su: 6
Side note. . .
FYI:
I've been deliberately gathering evidence
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217239
--- Comment #5 from Mark Millard ---
Dumb typo fix:
powerd
not powerpd.
(I've typed powerpc a lot and it shows.)
--
You are receiving this mail because:
You are the assignee for the bug.
___
> On Feb 19, 2017, at 14:22, Sid wrote:
>
> Hi,
> When I start X with one of the libGL packages installed, I get an error
> message in ~/.xsession-errors
> libGL error: MESA-LOADER: failed to retrieve device information
> libGL error: image driver extension not found
> libGL error: failed to lo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217243
Bug ID: 217243
Summary: dhclient doesn't consistently update /etc/resolv.conf
with what is defined in /etc/dhclient.conf
Product: Base System
Version: 11.0-RELEASE
Ha
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217243
--- Comment #1 from j...@endries.org ---
Maybe incorrectly, but I was expecting a restart to regenerate resolv.conf with
the domain in it regardless of if the domain string value in dhclient.conf
changed (if the domain wasn't already in reso
18 matches
Mail list logo