[Bug 241570] locale - LC_* variables are "C" when I set UTF-8 locale

2019-10-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241570

Bug ID: 241570
   Summary: locale - LC_* variables are "C" when I set UTF-8
locale
   Product: Base System
   Version: 11.3-STABLE
  Hardware: sparc64
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: conf
  Assignee: b...@freebsd.org
  Reporter: mercur...@elming.org

Hello,

I am trying to set UTF-8 locale using 'russian' login class:

russian|Russian Users Accounts:\
:charset=UTF-8:\
:lang=ru_RU.UTF-8:\
:setenv=LC_MESSAGES=en_US.UTF-8,LC_TIME=en_US.UTF-8:\
:tc=default:

My user has 'russian' login class, but localization isn't working properly.

The output of locale command:
[mercurius@tyler ~]$ locale
LANG=ru_RU.UTF-8
LC_CTYPE="C"
LC_COLLATE="C"
LC_TIME="C"
LC_NUMERIC="C"
LC_MONETARY="C"
LC_MESSAGES="C"
LC_ALL=

for example, tmux also shows error:

[mercurius@tyler ~]$ tmux
tmux: invalid LC_ALL, LC_CTYPE or LANG

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 241573] 12.1-RC2 usr.sbin/services_mkdb/services doesn't include SSDP, despite that protocol being used (for UPnP)

2019-10-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241573

Bug ID: 241573
   Summary: 12.1-RC2 usr.sbin/services_mkdb/services doesn't
include SSDP, despite that protocol being used (for
UPnP)
   Product: Base System
   Version: 12.1-RELEASE
  Hardware: Any
   URL: https://www.iana.org/assignments/service-names-port-nu
mbers/service-names-port-numbers.xhtml?&page=34
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: conf
  Assignee: b...@freebsd.org
  Reporter: paua...@gundo.com

[pauamma@gadfly] ~% grep 1900 /etc/services
[pauamma@gadfly] ~% grep -i ssdp /etc/services
[pauamma@gadfly] ~% 

Excerpt from the IANA port numbers list:
ssdp1900tcp SSDP[UPnP_Forum][UPnP_Forum]
ssdp1900udp SSDP[UPnP_Forum][UPnP_Forum]

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 241570] locale - LC_* variables are "C" when I set UTF-8 locale

2019-10-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241570

--- Comment #1 from Conrad Meyer  ---
Have you run cap_mkdb after updating user login class?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 241570] locale - LC_* variables are "C" when I set UTF-8 locale

2019-10-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241570

--- Comment #2 from Eugene Bolshakoff  ---
(In reply to Conrad Meyer from comment #1)
Yes, I have. I also tried other locales (en_US.UTF-8, for example).

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 241577] F_SETLK on NFS

2019-10-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241577

Bug ID: 241577
   Summary: F_SETLK on NFS
   Product: Base System
   Version: 11.3-STABLE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: m...@freebsd.org

I'm forced to use an NFS-share as home directory for a while. The mount is
using default options -- nothing fancy:

 narawntapu:/green/home  /homenfs rw  0 0

However, various things (browsers, Thunderbird) aren't working -- manifesting
all sorts of very strange problems.

Apparently, the underlying reason is the same for all of them -- SQLite3 can
not operate on its database-files, which are used for much of the software's
configuration nowadays.

A very simple test-case is:

% echo .databases | sqlite3 ~/meow.db
Error: disk I/O error

Using /tmp -- or any other local filesystem instead of ~/ -- works as expected.

I used ktrace to see, what exactly is failing in sqlite3, and found this:

 43469 sqlite3  CALL  fcntl(0x3,F_SETLK,0x7fffb920)
 43469 sqlite3  RET   fcntl -1 errno 45 Operation not supported
 43469 sqlite3  CALL  write(0x2,0x7fffc8c0,0x16)
 43469 sqlite3  GIO   fd 2 wrote 22 bytes
   "Error: disk I/O error

The NFS-server (narawntapu) has lock-daemon running:
   PID TT  STATTIME COMMAND
   785  -  Ss   0:02,00 /usr/sbin/rpc.lockd

Neither the client nor the server have any kernel messages in the logs relating
to this problem.

Why is not F_SETLK working? I'm not expecting high performance, but I expect it
to work...

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 241579] FreeBSD i386 sendmail broken for STARTTLS

2019-10-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241579

Bug ID: 241579
   Summary: FreeBSD i386 sendmail broken for STARTTLS
   Product: Base System
   Version: 12.0-RELEASE
  Hardware: Any
OS: Any
Status: New
  Severity: Affects Many People
  Priority: ---
 Component: misc
  Assignee: b...@freebsd.org
  Reporter: t...@mittelstaedt.us

FreeBSD i386 cannot be configured to run TLS on Sendmail.  FreeBSD arm64 works
fine using the identical instructions.  OpenSSL will generate a self signed
certificate if it is defined in /etc/rc.conf for sendmail but sendmail errors
out when attempting to load it.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 224173] serial driver from 10.4 onwards doesn't correctly work in ntpd/DCF77 "parse" clock mode

2019-10-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=224173

pvo...@uos.de changed:

   What|Removed |Added

 CC||pvo...@uos.de

--- Comment #1 from pvo...@uos.de ---
Well, this issue is rather old and still has status "new". I reply because I
have just obviuosly run into the same situation: I have an USB DCF77 receiver
which can never pass a full correct signal to ntpd. It is a GUDE Expert Mouse
Clock 0107 which is correctly recognized by FreeBSD 11.3-RELEASE-p4. I have
built net/ntp from ports with enabled RAWDCF option. However, ntp log is full
of "INCOMPLETE DATA" and "start bit / parity check FAILED" messages. The same
receiver works immediately when connected to a Debian Buster machine.

Is there currently any work in progress on this issue? Is there an issue in
ucom/uftdi kernel modules or in the RAWDCF driver of ntp?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 241577] F_SETLK on NFS is not working

2019-10-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241577

Mark Linimon  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|f...@freebsd.org
Summary|F_SETLK on NFS  |F_SETLK on NFS is not
   ||working

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 241581] PCIe passthrough is broken in QEMU 4 due to PCI Device ID conflict

2019-10-29 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241581

Bug ID: 241581
   Summary: PCIe passthrough is broken in QEMU 4 due to PCI Device
ID conflict
   Product: Base System
   Version: 11.2-STABLE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Some People
  Priority: ---
 Component: kern
  Assignee: b...@freebsd.org
  Reporter: k...@gatorgraphics.com

I run a couple of FreeBSD based VMs in Proxmox. Upgrading to Proxmox 6 which
includes QEMU 4 broke the PCIe passthrough I had setup in both VMs. 

On further investigation someone on the proxmox forums suggested that the
problem is a device ID conflict.

https://forum.proxmox.com/threads/vm-w-pcie-passthrough-not-working-after-upgrading-to-6-0.56021/post-274339

Apparently the QEMU vendor and device ids are being used for the
ptnetmap-memdev device.

https://svnweb.freebsd.org/base/release/12.0.0/sys/net/netmap_virt.h?view=markup#l44

https://devicehunt.com/view/type/pci/vendor/1B36/device/000C

Any chance this can be fixed. I am currently having to run my VMs with an older
version of the Q35 machine in QEMU to make them work and I don't see any way I
can upgrade to later revisions until this is fixed. I suspect there are quite a
few people affected by this.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"