[Bug 279174] POLA violation: Graphical Installer for a natively text UI OS
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279174 Bug ID: 279174 Summary: POLA violation: Graphical Installer for a natively text UI OS Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: misc Assignee: b...@freebsd.org Reporter: concussious.bugzi...@runbox.com "The new installer is expected to increase the attractiveness of the system for users who are accustomed to graphical installers and perceive text interfaces as outdated." FreeBSD has an exceptionally consistent, elegant, and efficient entirely text based interface which comprises the base system. People will be astonished after a graphical bootloader then graphical installer drops them into a text interface after installing the system. To be clear, this is amazing work and I hope all of our graphical downstreams are collaborating and using it. But, there's not a lot of spaces left for people who need a moderm advanced operating system, not a toy, and prefer TUI. This has always been one of those spaces. Thanks everyone, and sorry to speak up in a critical way. -- You are receiving this mail because: You are the assignee for the bug.
Problem reports for b...@freebsd.org that need special attention
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 obsolete releases. Status |Bug Id | Description +---+--- New |252123 | fetch(3): Fix wrong usage of proxy when request i New |262764 | After DVD1 13.0-R install with ports tree, portsn New |262989 | sys/conf/files, sys/conf/options, sys/conf/NOTES: New |269994 | build options have different kernel and userland New |276571 | makefs(8) creates broken UFS images with sectorsi Open| 46441 | sh(1): Does not support PS1, PS2, PS4 parameter e Open|177821 | sysctl: Some security.jail nodes are funky, dupli Open|220246 | syslogd does not send RFC3164-conformant messages Open|250309 | devmatch: panic: general protection fault: sysctl Open|255130 | Issue with rtsx driver Open|256952 | kqueue(2): Improve epoll Linux compatibility (com Open|257149 | CFLAGS not passed to whole build Open|257646 | opensm: rc service is installed by default, but o Open|258665 | lib/libfetch: Add Happy Eyeballs (RFC8305) suppor Open|259292 | vmware/pvscsi: UNMAP fails on VMWare 6.7 thinly p Open|259636 | multiple components: Change "Take Affect" to "Tak Open|259655 | periodic: security/security.functions does not re Open|259703 | In sys/dev/pci/pci.c, error in do_power_nodriver Open|259808 | etc/periodic/daily/100.clean-disks: Fix error (Di Open|260214 | acpi_battery: Should provide current/max battery Open|260245 | swap/vm: Apparent memory leak: 100% swap usage Open|261640 | sysctl: Add -F option to display sysctl format st Open|261641 | drm-kmod: Launch message is written into (possibl Open|261771 | nvme(4): Reports errors every 5 minutes: PRP OFFS Open|261971 | kernel crash launching bhyve guest on ZFS: #15 bu Open|262157 | su+j: Crashes during mmc(4) fsck after timeout: E Open|262192 | Crashes at boot with kern.random.initial_seeding. Open|264028 | loader: Incorrect (32gb) memory reported by BTX l Open|264075 | freebsd-update in 13.1-RELEASE detects an install Open|264188 | kinit(1): Ignores KRB5CCNAME environment variable Open|264226 | setting kern.vty=sc causes hang during UEFI boot Open|264757 | fetch: Show correct port number in -vv output Open|264833 | 12.3-STABLE panic on sync and reboot: panic: slee Open|266419 | mrsas: Corrupts memory (crashes) when reading dat 34 problems total for which you should take action.
[Bug 134767] [sound] [snd_hda] [regression] Sigmatel STAC9205X no sound under RELENG_7_2_0_RELEASE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=134767 Christos Margiolis changed: What|Removed |Added Resolution|--- |Unable to Reproduce Status|Open|Closed -- You are receiving this mail because: You are the assignee for the bug.
[Bug 134767] [sound] [snd_hda] [regression] Sigmatel STAC9205X no sound under RELENG_7_2_0_RELEASE
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=134767 --- Comment #11 from Lars Hecking --- It is definitely no longer relevant to me. I don't have that machine anymore. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 279170] /etc/termcap.db -> /usr/share/misc/termcap.db missing?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279170 Bug ID: 279170 Summary: /etc/termcap.db -> /usr/share/misc/termcap.db missing? Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: misc Assignee: b...@freebsd.org Reporter: ja...@catflap.org I was looking at a ktrace dump file recently (/bin/ls) and noticed that during initialisation, it attempted to read /etc/termcap.db - as that failed, it then read the text version pointed to by /etc/termcap Adding a link: /etc/termcap.db -> /usr/share/misc/termcap.db caused subsequent runs to use the termcap.db version. Is there any reason why /etc/termcap is linked, whilst /etc/termcap.db isn't? And if so, what's the purpose of /usr/share/misc/termcap.db ? Cheers, Jamie -- You are receiving this mail because: You are the assignee for the bug.
[Bug 279154] loader.efi shows wrong kernel name, but boots correct kernel
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279154 Bug ID: 279154 Summary: loader.efi shows wrong kernel name, but boots correct kernel Product: Base System Version: Unspecified Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: free...@kumba.dev NOTE: This is with FreeBSD 14.1-BETA2 I am not 100% on this yet, but I think I am seeing a bit of a visual bug in loader.efi. On an Intel NUC8i5BEH, I build and use a custom kernel that is installed to /boot/kernel.custom. In /boot, I create two symlinks: - "GENERIC" which points at /boot/kernel - "CUSTOM" which points at /boot/kernel.custom In /boot/loader.conf, I set these three variables: > kernels="CUSTOM GENERIC" > kernel="CUSTOM" > bootfile="/boot/kernel.custom/kernel" Under 14.0-RELEASE, the boot menu would show for Item #6, this text: > 6. Kernel: default/CUSTOM (X of Y) But under 14.1-BETA2, I see this: > 6. Kernel: default/GENERIC (X of Y) Which shouldn't happen, because the default kernel is the first element in the 'kernels' variable. However, despite what the menu shows, the correct kernel, pointed at by "CUSTOM", is what is booted (likely because of the setting of the 'kernel' variable or the bootfile variable). So I think this could be just a visual bug, but I am not 100% certain at the moment. I haven't updated a system using the classic BIOS loader yet to see if it's got the same bug. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 279152] panic: VERIFY3(NULL == dmu_buf_set_user(l->l_dbuf, >l_dbu)) failed (0x == 0xfffff808149f9800x)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279152 Mark Linimon changed: What|Removed |Added Keywords||crash -- You are receiving this mail because: You are the assignee for the bug.
[Bug 279152] panic: VERIFY3(NULL == dmu_buf_set_user(l->l_dbuf, >l_dbu)) failed (0x == 0xfffff808149f9800x)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279152 Bug ID: 279152 Summary: panic: VERIFY3(NULL == dmu_buf_set_user(l->l_dbuf, >l_dbu)) failed (0x == 0xf808149f9800x) Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: b...@freebsd.org Reporter: p...@freebsd.org cpuid = 1 time = 1716101420 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe0170b555f0 vpanic() at vpanic+0x13f/frame 0xfe0170b55720 spl_panic() at spl_panic+0x3a/frame 0xfe0170b55780 zap_expand_leaf() at zap_expand_leaf+0x8b7/frame 0xfe0170b55810 fzap_add_cd() at fzap_add_cd+0x1a3/frame 0xfe0170b558b0 fzap_add() at fzap_add+0x88/frame 0xfe0170b558d0 zap_add_impl() at zap_add_impl+0x291/frame 0xfe0170b55950 zap_add() at zap_add+0x70/frame 0xfe0170b559a0 zfs_link_create() at zfs_link_create+0x153/frame 0xfe0170b55af0 zfs_link() at zfs_link+0x37f/frame 0xfe0170b55b60 VOP_LINK_APV() at VOP_LINK_APV+0x86/frame 0xfe0170b55b90 kern_linkat_vp() at kern_linkat_vp+0x33c/frame 0xfe0170b55cc0 kern_linkat() at kern_linkat+0x17b/frame 0xfe0170b55de0 sys_link() at sys_link+0x28/frame 0xfe0170b55e00 amd64_syscall() at amd64_syscall+0x158/frame 0xfe0170b55f30 fast_syscall_common() at fast_syscall_common+0xf8/frame 0xfe0170b55f30 --- syscall (9, FreeBSD ELF64, link), rip = 0x19021dc7251a, rsp = 0x19021ac60538, rbp = 0x19021ac60670 --- How to reproduce: root@mercat1:~ # cd /usr/src/tools/test/stress2/misc root@mercat1:/usr/src/tools/test/stress2/misc # ./all.sh -al5 zfs3.sh Console log: https://people.freebsd.org/~pho/stress/log/log0525.txt -- You are receiving this mail because: You are the assignee for the bug.
