[Bug 232313] GCE image size is now > 30 GB, above free quota

2019-01-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232313 --- Comment #25 from Kirk McKusick --- (In reply to Conrad Meyer from comment #24) Thanks, doing the 'truncate -s 30g myvm.img' did the trick and I was able to then successfully growfs the filesystem. I did cause a panic because of having a

[Bug 233735] Possible build race: genoffset.o /usr/src/sys/sys/types.h: error: machine/endian.h: No such file or directory

2019-01-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233735 --- Comment #4 from Li-Wen Hsu --- https://ci.freebsd.org/job/FreeBSD-head-amd64-build/11587/console -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@fr

[Bug 233735] Possible build race: genoffset.o /usr/src/sys/sys/types.h: error: machine/endian.h: No such file or directory

2019-01-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233735 --- Comment #3 from Li-Wen Hsu --- https://ci.freebsd.org/job/FreeBSD-head-sparc64-build/11283/console -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@

[Bug 234691] 'make buildworld' of 12.0-RELEASE sources fails, com_err.h not found

2019-01-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234691 --- Comment #1 from commit-h...@freebsd.org --- A commit references this bug: Author: nyan Date: Mon Jan 14 06:34:58 UTC 2019 New revision: 343011 URL: https://svnweb.freebsd.org/changeset/base/343011 Log: Use ${SRCTOP}/contrib/com_err/c

[Bug 234885] cmp(1) Capsicum error if stdin closed

2019-01-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234885 Mark Johnston changed: What|Removed |Added Attachment #201110|0 |1 is obsolete|

[Bug 234885] cmp(1) Capsicum error if stdin closed

2019-01-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234885 Mark Johnston changed: What|Removed |Added CC||ma...@freebsd.org --- Comment #1 f

[Bug 230725] [patch] kerberos5 files missing in tools/build/mk/OptionalObsoleteFiles.inc

2019-01-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230725 Oleksandr Tymoshenko changed: What|Removed |Added CC||go...@freebsd.org

[Bug 230725] [patch] kerberos5 files missing in tools/build/mk/OptionalObsoleteFiles.inc

2019-01-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230725 --- Comment #3 from commit-h...@freebsd.org --- A commit references this bug: Author: gonzo Date: Mon Jan 14 03:13:31 UTC 2019 New revision: 343009 URL: https://svnweb.freebsd.org/changeset/base/343009 Log: Add four kerberos CLI utilitie

[Bug 204916] Add Quirks for Dell ChromeBook: Allows boot/run

2019-01-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204916 Oleksandr Tymoshenko changed: What|Removed |Added CC||go...@freebsd.org

[Bug 204916] Add Quirks for Dell ChromeBook: Allows boot/run

2019-01-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204916 --- Comment #1 from commit-h...@freebsd.org --- A commit references this bug: Author: gonzo Date: Mon Jan 14 01:30:48 UTC 2019 New revision: 343008 URL: https://svnweb.freebsd.org/changeset/base/343008 Log: Add Dell Chromebook to the lis

[Bug 232313] GCE image size is now > 30 GB, above free quota

2019-01-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232313 --- Comment #24 from Conrad Meyer --- (In reply to Kirk McKusick from comment #23) For vmrun.sh, you can probably just use 'truncate -s 30g myvm.img' to grow the size of the image used by Bhyve. -- You are receiving this mail because: You

[Bug 232313] GCE image size is now > 30 GB, above free quota

2019-01-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232313 --- Comment #23 from Kirk McKusick --- (In reply to Mateusz Kwiatkowski from comment #22) Trying to reproduce your test. The problem that I have is that I cannot increase the size of the virtual disk in my virtual machine. What is the pro

[Bug 234671] clang faults while compiling new GlusterFS source code

2019-01-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234671 Dimitry Andric changed: What|Removed |Added Status|New |Open Assignee|b...@free

[Bug 234622] [libc] getgrent() issue with large NIS groups

2019-01-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234622 Jilles Tjoelker changed: What|Removed |Added CC||jil...@freebsd.org S

[Bug 234042] panics on 12.0-RELEASE: swi4: clock(0), instruction pointer 0x0

2019-01-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234042 --- Comment #13 from Mike Andrews --- https://www.bit0.com/download/vmcores.schnapps.tar.gz.gpg https://www.bit0.com/download/vmcores.whiskey.tar.gz.gpg https://www.bit0.com/download/vmcores.wine.tar.gz.gpg emailed passphrase -- You are

[Bug 204545] Adding quirk entry for some (Acer C720P Chromebook) firmware in keyboard module

2019-01-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204545 Oleksandr Tymoshenko changed: What|Removed |Added Resolution|--- |Overcome By Events

Problem reports for b...@freebsd.org that need special attention

2019-01-13 Thread bugzilla-noreply
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

[Bug 200757] A typo in /usr/src/UPDATING

2019-01-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200757 Andriy Voskoboinyk changed: What|Removed |Added Status|New |Closed Resolution|---

[Bug 234042] panics on 12.0-RELEASE: swi4: clock(0), instruction pointer 0x0

2019-01-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234042 --- Comment #12 from Mike Andrews --- https://www.bit0.com/download/vmcores.champagne.tar.gz.gpg -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebs

[Bug 228875] Synaptics gestures like two finger scroll and trackpoint do not work.

2019-01-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228875 Oleksandr Tymoshenko changed: What|Removed |Added Status|New |Closed CC|

[Bug 234042] panics on 12.0-RELEASE: swi4: clock(0), instruction pointer 0x0

2019-01-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234042 --- Comment #11 from Mike Andrews --- https://www.bit0.com/download/vmcore.0.whitedog.2018-12-30 and https://www.bit0.com/download/kernel.whitedog.2018-12-30 should cover that -- I don't have anything in /usr/lib/debug at all but the kernel

[Bug 234793] Failed unknown for $USER in sshd logs even if I got authenticated

2019-01-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234793 --- Comment #3 from Egbert Pot --- Created attachment 201095 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=201095&action=edit server--sshd_config -- You are receiving this mail because: You are the assignee for the bug. __

[Bug 234793] Failed unknown for $USER in sshd logs even if I got authenticated

2019-01-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234793 --- Comment #2 from Egbert Pot --- Created attachment 201094 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=201094&action=edit server--auth.log -- You are receiving this mail because: You are the assignee for the bug. _

[Bug 234793] Failed unknown for $USER in sshd logs even if I got authenticated

2019-01-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234793 Egbert Pot changed: What|Removed |Added CC||egbert@gmail.com Attachment #2010

[Bug 234793] Failed unknown for $USER in sshd logs even if I got authenticated

2019-01-13 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234793 --- Comment #4 from Egbert Pot --- I I have the same issue as @Sverre. Due to this issue I cannot use Fail2Ban, since it also bans successful logins. To help debugging this issue, I've added: * SSH server configuration from /etc/ssh/sshd_c