https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260381
Bug ID: 260381
Summary: sysmouse or psm delays button release events by about
900ms
Product: Base System
Version: 12.2-STABLE
Hardware: Any
OS: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260381
Bertrand Petit changed:
What|Removed |Added
Attachment #230075|text/x-csrc |text/plain
mime type|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=137228
Bertrand Petit changed:
What|Removed |Added
CC||bs...@phoe.frmug.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260161
--- Comment #6 from commit-h...@freebsd.org ---
A commit in branch stable/13 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=d74c589ead91118a46370edc30f10e7d65ed2636
commit d74c589ead91118a46370edc30f10e7d65ed2636
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260161
Mark Johnston changed:
What|Removed |Added
Status|Open|Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260347
Mark Johnston changed:
What|Removed |Added
Status|New |Open
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260347
Mark Johnston changed:
What|Removed |Added
Assignee|b...@freebsd.org|ma...@freebsd.org
--- Comment #2 f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=137228
--- Comment #3 from Bob Frazier ---
(In reply to Bertrand Petit from comment #2)
I did not see a similarity between the two bugs. Did you post to the correct
bug report with the correct related bug?
This particular report is from 2009 an
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
Bug ID: 260393
Summary: Page Fault tcp_output/tcp_input
Product: Base System
Version: 13.0-STABLE
Hardware: amd64
OS: Any
Status: New
Severity: Affe
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
--- Comment #1 from Dobri Dobrev ---
Created attachment 230083
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=230083&action=edit
core.txt.1
Here's the core.txt.1 from the server that was most-recently updated/rebuilt
kernel/worl
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259555
--- Comment #6 from Martin Filla ---
test scenario
1. Run virtualbox
2. suspend system
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260399
Bug ID: 260399
Summary: freebsd-update is just horrible, it fails and fails
and WHY?
Product: Base System
Version: Unspecified
Hardware: Any
OS: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260343
Rick Macklem changed:
What|Removed |Added
Status|New |Open
Assignee|b...@freebs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260393
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260399
Kubilay Kocak changed:
What|Removed |Added
Keywords||needs-qa
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260399
Kubilay Kocak changed:
What|Removed |Added
CC||somesig...@icloud.com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260399
Kubilay Kocak changed:
What|Removed |Added
Assignee|b...@freebsd.org|ko...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260375
--- Comment #3 from Rick Macklem ---
I think a mailing list (like freebsd-current@) should be asked.
Personally, I do not see why 32bit arches like i386 should not
be fixed, so that they can return 64bit directory offsets if,
as you say, so
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260399
--- Comment #2 from Some Signup ---
It's not related to a version of FreeBSD. It's related solely to freebsd-update
itself (and portsnap).
The simple fact is freebsd-update is not a reliable tool. I am willing to bet
that if I wrote a dead
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260404
Bug ID: 260404
Summary: README(.md): Spell out GPL correctly
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
Severity: Affec
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260404
--- Comment #1 from Fabian Keil ---
Created attachment 230096
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=230096&action=edit
Patch for stable/12 and stable/13 to add the "General"
--
You are receiving this mail because:
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260406
Bug ID: 260406
Summary: pfctl: Cannot allocate memory (after a time)
Product: Base System
Version: CURRENT
Hardware: arm64
URL: https://lists.freebsd.org/archives/freebsd-
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259798
--- Comment #9 from tech-li...@zyxst.net ---
(In reply to jjasen from comment #0)
Hi,
I'm seeing the problem in a different context (arm64 on recent -current) please
see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260406
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260406
--- Comment #1 from tech-li...@zyxst.net ---
also:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259798
some more stats
1. when it gets the error, before reboot
# vmstat -m | grep -E 'pf|Size'
Type InUse MemUse Requests Si
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260399
Graham Perrin changed:
What|Removed |Added
CC||grahamper...@gmail.com
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260406
Kristof Provost changed:
What|Removed |Added
CC||k...@freebsd.org
--- Comment #2
26 matches
Mail list logo
