| View previous topic :: View next topic |
| Author |
Message |
Demo
Tux's lil' helper
Joined: 25 Nov 2022
Posts: 126
|
 Posted: Sun Mar 31, 2024 5:15 pm Post subject: [Solved]xorg doesn't render text/message flood from pam in |
 |
|
Hello folks ...
Is this normal? | Code: | [/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(253)] CONF: sha512
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(253)] CONF: shadow
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(253)] CONF: debug
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(256)] RETURN success(0) -> -1 ok
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(256)] RETURN open_err(1) -> -3 bad
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(256)] RETURN symbol_err(2) -> -3 bad
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(256)] RETURN service_err(3) -> -3 bad
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(256)] RETURN system_err(4) -> -3 bad
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(256)] RETURN buf_err(5) -> -3 bad
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(256)] RETURN perm_denied(6) -> -3 bad
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(256)] RETURN auth_err(7) -> -3 bad
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(256)] RETURN cred_insufficient(8) -> -3 bad
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(256)] RETURN authinfo_unavail(9) -> -3 bad
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(256)] RETURN user_unknown(10) -> -3 bad
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(256)] RETURN maxtries(11) -> -3 bad
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(256)] RETURN new_authtok_reqd(12) -> -1 ok
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(256)] RETURN acct_expired(13) -> -3 bad
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(256)] RETURN session_err(14) -> -3 bad
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(256)] RETURN cred_unavail(15) -> -3 bad
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(256)] RETURN cred_expired(16) -> -3 bad
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(256)] RETURN cred_err(17) -> -3 bad
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(256)] RETURN no_module_data(18) -> -3 bad
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(256)] RETURN conv_err(19) -> -3 bad
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(256)] RETURN authtok_err(20) -> -3 bad
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(256)] RETURN authtok_recover_err(21) -> -3 bad
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(256)] RETURN authtok_lock_busy(22) -> -3 bad
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(256)] RETURN authtok_disable_aging(23) -> -3 bad
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(256)] RETURN try_again(24) -> -3 bad
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(256)] RETURN ignore(25) -> 0 ignore
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(256)] RETURN abort(26) -> -3 bad
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(256)] RETURN authtok_expired(27) -> -3 bad
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(256)] RETURN module_unknown(28) -> -3 bad
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(256)] RETURN bad_item(29) -> -3 bad
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(256)] RETURN conv_again(30) -> -3 bad
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(256)] RETURN incomplete(31) -> -3 bad
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_add_handler(793)] called.
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_add_handler(796)] _pam_add_handler: adding type 8, handler_type 0, module `pam_unix.so'
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_load_module(680)] _pam_load_module: loading module `/lib64/security/pam_unix.so'
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_add_handler(941)] _pam_add_handler: returning successfully
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_assemble_line(576)] called.
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(79)] _pam_init_handler: LINE: session required pam_limits.so debug
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(101)] _pam_init_handlers: Found PAM config entry for: su-l
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(136)] Using config entry: session
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(139)] Skipping config entry: session (requested=8, found=2)
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_assemble_line(576)] called.
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(79)] _pam_init_handler: LINE: session required pam_env.so debug
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(101)] _pam_init_handlers: Found PAM config entry for: su-l
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(136)] Using config entry: session
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(139)] Skipping config entry: session (requested=8, found=2)
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_assemble_line(576)] called.
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(79)] _pam_init_handler: LINE: session required pam_unix.so debug
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(101)] _pam_init_handlers: Found PAM config entry for: su-l
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(136)] Using config entry: session
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(139)] Skipping config entry: session (requested=8, found=2)
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_assemble_line(576)] called.
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_assemble_line(576)] called.
[/var/tmp/portage/sys-libs/pam-1.5.3-r1/work/Linux-PAM-1.5.3/libpam/pam_handlers.c:_pam_parse_conf_file(79)] _pam_init_handler: LINE: session include system-auth
|
Everytime I think about typing something in a terminal I get 100 pages of what you see. What's amazing is that the pam_handlers.c file is not in /var/temp anymore, and I unmerged and emerged pam. Could be systemd was linked against libraries in build directory?
Gnome on the other hand refuses to show any text in panels/menus/gtk applications if I'm running it on x. Is there any relation? What may cause either or both?
Last edited by Demo on Sat Apr 06, 2024 9:23 pm; edited 1 time in total |
|
| Back to top |
|
 |
Demo
Tux's lil' helper
Joined: 25 Nov 2022
Posts: 126
|
| Posted: Mon Apr 01, 2024 7:36 pm Post subject: |
|
|
bump
| Code: |
COMMON_FLAGS="-O3 -pipe -fuse-ld=gold -march=x86-64-v3 -mtune=skylake"
#COMMON_FLAGS="-O2 -pipe -fuse-ld=gold -march=x86-64-v3 -mtune=skylake"
CFLAGS="${COMMON_FLAGS}"
CXXFLAGS="${COMMON_FLAGS}"
FCFLAGS="${COMMON_FLAGS}"
FFLAGS="${COMMON_FLAGS}"
ARCH="86-64-v3"
MAKEOPTS="-j16"
# EMERGE_DEFAULT_OPTS="--jobs=16"
AUTOCLEAN="yes"
GRUB_PLATFORMS="efi-64"
# NOTE: This stage was built with the bindist Use flag enabled
# This sets the language of build output to English.
# Please keep this setting intact when reporting bugs.
LC_MESSAGES=C
ACCEPT_LICENSE="*"
VIDEO_CARDS="intel"
USE="NOFILTER custom-cflags cxx
debug dga dri3 ffmpeg gold lm-sensors lto man mtp
pgo qsv svg2 threads tidy uefi
upnp upnp-av v4l vaapi vainfo valgrind vc vdo
video-thumbnails vpx webkit wifi hwaccel pipewire -telemetry symlink test ruby_targets_ruby33 python_targets_pypy3 python_targets_python3_12 abi_x86_32 abi_x86_64 abi_x86_x32 zeroconf bluetooth lz4 lzo
cpu_flags_x86_aes cpu_flags_x86_avx cpu_flags_x86_avx2 cpu_flags_x86_f16c cpu_flags_x86_mmx cpu_flags_x86_pclmul cpu_flags_x86_popcnt cpu_flags_x86_rdrand cpu_flags_x86_sse cpu_flags_x86_sse2 cpu_flags_x86_sse3 cpu_flags_x86_sse4_1 cpu_flags_x86_sse4_2 cpu_flags_x86_sse4a cpu_flags_x86_ssse3
#zstd python_targets_python3_13"
ACCEPT_KEYWORDS="~amd64 amd64"
# source /var/lib/layman/make.conf
LANG="en_US.iso88951"
LC_ALL=en_US.iso88591
LANGUAGE=en_US.iso88591
GENTOO_MIRRORS="https://gitweb.gentoo.org/repo/gentoo.git/tree"
# "http://ftp.agdsn.de/gentoo https://ftp.uni-hannover.de/gentoo/ rsync://ftp.linux.org.tr/gentoo-distfiles/ https://www.mirrorservice.org/sites/distfiles.gentoo.org/ http://www.gtlib.gatech.edu/pub/gentoo"
##### testing variables ##########
#LDFLAGS="${LDFLAGS},--defsym=__gentoo_check_ldflags__=0" ## causes error in compilation
#PORTAGE_TMPDIR="/"
PORTAGE_ELOG_CLASSES="log warn error qa"
FEATURES="parallel-fetch parallel-install protect-owned ipc-sandbox network-sandbox sandbox split-log split-elog strict test userfetch userpriv usersandbox -preserve-libs test-fail-continue"
|
| Code: | Portage 3.0.63 (python 3.12.2-final-0, default/linux/amd64/17.1/desktop/gnome/systemd/merged-usr, gcc-13, glibc-2.39-r2, 6.6.13-gentoo-x86_64 x86_64)
=================================================================
System uname: Linux-6.6.13-gentoo-x86_64-x86_64-Intel-R-_Core-TM-_i7-6700_CPU_@_3.40GHz-with-glibc2.39
KiB Mem: 32623448 total, 9803184 free
KiB Swap: 0 total, 0 free
Timestamp of repository gentoo: Mon, 01 Apr 2024 10:00:00 +0000
Head commit of repository gentoo: d8be2f7b0f04c3b71370c60106326db665a686fc
Timestamp of repository dlang: Mon, 01 Apr 2024 09:52:25 +0000
Head commit of repository dlang: 30fdb46625719b8a74153b57a85149c2a8ecf143
Timestamp of repository guru: Mon, 01 Apr 2024 09:52:46 +0000
Head commit of repository guru: 2a9c47d592b1571e7159a328c36e2b55dd5d46b0
sh bash 5.2_p26
ld GNU ld (Gentoo 2.42 p3) 2.42.0
app-misc/pax-utils: 1.3.7::gentoo
app-shells/bash: 5.2_p26::gentoo
dev-build/autoconf: 2.13-r8::gentoo, 2.71-r7::gentoo, 2.72-r1::gentoo
dev-build/automake: 1.16.5-r2::gentoo
dev-build/cmake: 3.29.0::gentoo
dev-build/libtool: 2.4.7-r4::gentoo
dev-build/make: 4.4.1-r1::gentoo
dev-build/meson: 1.4.0-r1::gentoo
dev-java/java-config: 2.3.1-r1::gentoo
dev-lang/perl: 5.38.2-r2::gentoo
dev-lang/python: 3.8.19::gentoo, 3.9.19::gentoo, 3.10.14::gentoo, 3.11.8_p1::gentoo, 3.12.2_p1::gentoo
dev-lang/rust: 1.76.0::gentoo
dev-lang/rust-bin: 1.76.0::gentoo
sys-apps/baselayout: 2.15::gentoo
sys-apps/sandbox: 2.38::gentoo
sys-apps/systemd: 255.3-r1::gentoo
sys-devel/binutils: 2.40-r9::gentoo, 2.41-r5::gentoo, 2.42-r1::gentoo
sys-devel/binutils-config: 5.5::gentoo
sys-devel/clang: 16.0.2::gentoo, 17.0.6::gentoo, 18.1.2::gentoo
sys-devel/gcc: 11.3.1_p20230427::gentoo, 12.2.1_p20230304::gentoo, 13.2.1_p20240210::gentoo
sys-devel/gcc-config: 2.11::gentoo
sys-devel/lld: 16.0.6::gentoo, 17.0.6::gentoo, 18.1.2::gentoo
sys-devel/llvm: 16.0.6::gentoo, 17.0.6::gentoo, 18.1.2::gentoo
sys-kernel/linux-headers: 6.7-r1::gentoo (virtual/os-headers)
sys-libs/glibc: 2.39-r2::gentoo
Repositories:
gentoo
location: /var/db/repos/gentoo
sync-type: rsync
sync-uri: rsync://rsync.gentoo.org/gentoo-portage
priority: -1000
volatile: False
sync-rsync-verify-metamanifest: yes
sync-rsync-verify-max-age: 24
sync-rsync-extra-opts:
sync-rsync-verify-jobs: 1
compiz_reloaded
location: /var/db/repos/compiz_reloaded
masters: gentoo
volatile: False
custom
location: /var/db/repos/custom
masters: gentoo
volatile: False
dlang
location: /var/db/repos/dlang
sync-type: git
sync-uri: https://github.com/gentoo-mirror/dlang.git
masters: gentoo
volatile: False
guru
location: /var/db/repos/guru
sync-type: git
sync-uri: https://github.com/gentoo-mirror/guru.git
masters: gentoo
volatile: False
wayland-desktop
location: /var/lib/layman/wayland-desktop
masters: gentoo
priority: 50
volatile: True
ACCEPT_KEYWORDS="amd64 ~amd64"
ACCEPT_LICENSE="*"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-O3 -pipe -fuse-ld=gold -march=x86-64-v3 -mtune=skylake"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /etc/stunnel/stunnel.conf /usr/share/config /usr/share/gnupg/qualified.txt"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/texmf/language.dat.d /etc/texmf/language.def.d /etc/texmf/updmap.d /etc/texmf/web2c"
CXXFLAGS="-O3 -pipe -fuse-ld=gold -march=x86-64-v3 -mtune=skylake"
DISTDIR="/var/cache/distfiles"
ENV_UNSET="CARGO_HOME DBUS_SESSION_BUS_ADDRESS DISPLAY GDK_PIXBUF_MODULE_FILE GOBIN GOPATH PERL5LIB PERL5OPT PERLPREFIX PERL_CORE PERL_MB_OPT PERL_MM_OPT XAUTHORITY XDG_CACHE_HOME XDG_CONFIG_HOME XDG_DATA_HOME XDG_RUNTIME_DIR XDG_STATE_HOME"
FCFLAGS="-O3 -pipe -fuse-ld=gold -march=x86-64-v3 -mtune=skylake"
FEATURES="assume-digests binpkg-docompress binpkg-dostrip binpkg-logs buildpkg-live config-protect-if-modified distlocks ebuild-locks fixlafiles ipc-sandbox merge-sync merge-wait multilib-strict network-sandbox news parallel-fetch parallel-install pid-sandbox pkgdir-index-trusted protect-owned qa-unresolved-soname-deps sandbox sfperms split-elog split-log strict strict-keepdir test test-fail-continue unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync warn-on-large-env xattr"
FFLAGS="-O3 -pipe -fuse-ld=gold -march=x86-64-v3 -mtune=skylake"
GENTOO_MIRRORS="https://gitweb.gentoo.org/repo/gentoo.git/tree"
LANG="en_US.iso88951"
LC_ALL="en_US.iso88591"
LDFLAGS="-Wl,-O1 -Wl,--as-needed"
LEX="flex"
MAKEOPTS="-j16"
PKGDIR="/var/cache/binpkgs"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --omit-dir-times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --exclude=/.git"
PORTAGE_TMPDIR="/var/tmp"
SHELL="/bin/bash"
USE="#zstd NOFILTER X a52 aac acl acpi alsa amd64 bluetooth branding bzip2 cairo cdda cdr cli colord crypt cups custom-cflags cxx dbus debug dga dri dri3 dts dvd dvdr eds encode evo exif ffmpeg flac fortran gdbm gif gnome gnome-keyring gnome-online-accounts gnome-shell gold gpm gstreamer gtk gui hwaccel iconv icu introspection ipv6 jpeg keyring lcms libnotify libtirpc lm-sensors lto lz4 lzo mad man mng mp3 mp4 mpeg mtp multilib nautilus ncurses networkmanager nls ogg opengl openmp pam pango pcre pdf pgo pipewire png policykit ppds pulseaudio qsv qt5 readline sdl seccomp sound spell ssl startup-notification svg svg2 symlink sysprof systemd test test-rust threads tidy tiff tracker truetype udev udisks uefi unicode upnp upnp-av upower usb v4l vaapi vainfo valgrind vc vdo video-thumbnails vorbis vpx vulkan wayland webkit wifi wxwidgets x264 xattr xcb xft xml xv xvid zeroconf zlib" ABI_X86="64 32" ADA_TARGET="gcc_12" APACHE2_MODULES="authn_core authz_core socache_shmcb unixd actions alias auth_basic authn_anon authn_dbm authn_file authz_dbm authz_groupfile authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs dav_lock deflate dir env expires ext_filter file_cache filter headers include info log_config logio mime mime_magic negotiation rewrite setenvif speling status unique_id userdir usertrack vhost_alias" CALLIGRA_FEATURES="karbon sheets words" COLLECTD_PLUGINS="df interface irq load memory rrdtool swap syslog" CPU_FLAGS_X86="mmx mmxext sse sse2 aes avx avx2 f16c fma3 pclmul popcnt rdrand sse3 sse4_1 sse4_2 sse4a ssse3" ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 garmin garmintxt gpsclock greis isync itrax mtk3301 ntrip navcom oceanserver oncore rtcm104v2 rtcm104v3 sirf skytraq superstar2 tsip tripmate tnt ublox" GRUB_PLATFORMS="efi-64" INPUT_DEVICES="libinput" KERNEL="linux" LCD_DEVICES="bayrad cfontz glk hd44780 lb216 lcdm001 mtxorb text" LUA_SINGLE_TARGET="lua5-1" LUA_TARGETS="lua5-1" OFFICE_IMPLEMENTATION="libreoffice" PHP_TARGETS="php8-1" POSTGRES_TARGETS="postgres15" PYTHON_SINGLE_TARGET="python3_11" PYTHON_TARGETS="python3_11 pypy3 python3_12 python3_13" RUBY_TARGETS="ruby31 ruby33" VIDEO_CARDS="intel" XTABLES_ADDONS="quota2 psd pknock lscan length2 ipv4options ipp2p iface geoip fuzzy condition tarpit sysrq proto logmark ipmark dhcpmac delude chaos account"
Unset: ADDR2LINE, AR, ARFLAGS, AS, ASFLAGS, CC, CCLD, CONFIG_SHELL, CPP, CPPFLAGS, CTARGET, CXX, CXXFILT, ELFEDIT, EMERGE_DEFAULT_OPTS, EXTRA_ECONF, F77FLAGS, FC, GCOV, GPROF, INSTALL_MASK, LD, LFLAGS, LIBTOOL, LINGUAS, MAKE, MAKEFLAGS, NM, OBJCOPY, OBJDUMP, PORTAGE_BINHOST, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PYTHONPATH, RANLIB, READELF, RUSTFLAGS, SIZE, STRINGS, STRIP, YACC, YFLAGS
|
I wanted to add that to work around the issue, I unmerged glibc, then reemerged it - which proved to be much easier than reemerging systemd by the way! -, then I unmerrged systemd, then reemerged the version just before the one I had from a binary package. The original systemd after I updated the whole system was systemd-255.4, which is failing to recompile, along with any version of systemd. |
|
| Back to top |
|
|
flexibeast
Guru
Joined: 04 Apr 2022
Posts: 449
Location: Naarm/Melbourne, Australia
|
| Posted: Tue Apr 02, 2024 12:16 am Post subject: |
|
|
| You have `debug` in your USE flags. i suspect that might be either the cause of the issue, or at least contributing to it. |
|
| Back to top |
|
|
Demo
Tux's lil' helper
Joined: 25 Nov 2022
Posts: 126
|
| Posted: Tue Apr 02, 2024 6:38 am Post subject: |
|
|
Thank you for the reply!
Both the test and debug use flags and test feature were added together 8 months ago along with the valgrind use flag and the several python use flags, and I didn't experience this behavior before ...
To give some more perspective, this installation is almost a year and a half old, it went through change from split-usr to merged-usr, deprication of openssl 1, from non-test, to test and debug, and from solely a 64 bit installation to mixed 64/32 bit installation. So It's not strange that something would break! A lot got broken actually, and I fixed it, however this one is not easy to fix, and I'm not really experienced in tracing code and locating bugs ... |
|
| Back to top |
|
|
flexibeast
Guru
Joined: 04 Apr 2022
Posts: 449
Location: Naarm/Melbourne, Australia
|
| Posted: Tue Apr 02, 2024 7:32 am Post subject: |
|
|
Hmm. Well, there are certainly multiple lines in the output you provided showing a `debug` option being used with multiple modules in the the PAM config files, e.g.
| Code: | | pam_handlers.c:_pam_parse_conf_file(79)] _pam_init_handler: LINE: session required pam_env.so debug |
Looking at the pam ebuild, i don't see it explicitly using the `debug` flag to add such things to the config files, though i don't know if:
| Code: | | $(use_enable debug) |
has that effect in this particular context. (My understanding is that the flag simply enables things in the source, rather than changing config files, but i might be wrong.) Have you added those lines manually yourself?
But perhaps someone with more knowledge than me in this area might be able to offer better help .... |
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 22648
|
| Posted: Tue Apr 02, 2024 2:42 pm Post subject: |
|
|
| That use_enable results in passing --enable-debug to the upstream configure script, which could do anything (or nothing) with it, including enabling source files that are not otherwise used, setting preprocessor macros to change logic in source files that are always used, or generating configuration files differently. |
|
| Back to top |
|
|
Demo
Tux's lil' helper
Joined: 25 Nov 2022
Posts: 126
|
| Posted: Tue Apr 02, 2024 2:56 pm Post subject: |
|
|
These are just status lines from pam, the "pam_unix.so", "pam_limits.so", "pam_env.so" object files are just required libraries for pam to work with the debug configure option. All of these libraries were compiled and available. | Code: | # equery b pam_limits.so
* Searching for pam_limits.so ...
sys-libs/pam-1.5.3-r1 (/lib64/security/pam_limits.so)
sys-libs/pam-1.5.3-r1 (/lib/security/pam_limits.so)
# equery b pam_env.so
* Searching for pam_env.so ...
sys-libs/pam-1.5.3-r1 (/lib64/security/pam_env.so)
sys-libs/pam-1.5.3-r1 (/lib/security/pam_env.so)
# equery b pam_unix.so
* Searching for pam_unix.so ...
sys-libs/pam-1.5.3-r1 (/lib64/security/pam_unix.so)
sys-libs/pam-1.5.3-r1 (/lib/security/pam_unix.so) |
| Quote: | | i don't see it explicitly using the `debug` flag to add such things to the config files |
| Code: | # equery u pam
[ Legend : U - final flag setting for installation]
[ : I - package is installed with flag ]
[ Colors : set, unset ]
* Found these USE flags for sys-libs/pam-1.5.3-r1:
U I
+ + abi_x86_32 : 32-bit (x86) libraries
- - audit : Enable support for Linux audit subsystem using sys-process/audit
- - berkdb : Build the pam_userdb module, that allows to authenticate users against a Berkeley DB file.
Please note that enabling this USE flag will create a PAM module that links to the Berkeley DB
(as provided by sys-libs/db) installed in /usr/lib and will thus not work for boot-critical
services authentication.
+ + debug : Enable extra debug codepaths, like asserts and extra output. If you want to get meaningful
backtraces see https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces
+ + filecaps : Use Linux file capabilities to control privilege rather than set*id (this is orthogonal to
USE=caps which uses capabilities at runtime e.g. libcap)
- - nis : Support for NIS/YP services |
| Quote: | | Have you added those lines manually yourself? |
Nope!
I do confess needing to edit ebuild files from time to time to fix bugs, in addition to having to ebuild packages from the ebuild files with the --skip-manifest option for the same reason, But not with pam! 
| Quote: | | My understanding is that the flag simply enables things in the source, rather than changing config files, but i might be wrong. |
USE flags, and FEATURES enable/disable compiling objects of a package - just like Hu mentioned, they pass options to the ./configure script or meson setup through eclasses - and also build their dependencies, like the tons of packages that become needed when the test flag is enabled.
Thank you for your contribution! |
|
| Back to top |
|
|
flexibeast
Guru
Joined: 04 Apr 2022
Posts: 449
Location: Naarm/Melbourne, Australia
|
| Posted: Wed Apr 03, 2024 1:03 am Post subject: |
|
|
| Hu wrote: | | That use_enable results in passing --enable-debug to the upstream configure script, which could do anything (or nothing) with it, including enabling source files that are not otherwise used, setting preprocessor macros to change logic in source files that are always used, or generating configuration files differently. |
Ah okay, thanks! |
|
| Back to top |
|
|
flexibeast
Guru
Joined: 04 Apr 2022
Posts: 449
Location: Naarm/Melbourne, Australia
|
| Posted: Wed Apr 03, 2024 1:12 am Post subject: |
|
|
| Demo wrote: | | USE flags, and FEATURES enable/disable compiling objects of a package - just like Hu mentioned, they pass options to the ./configure script or meson setup through eclasses - and also build their dependencies, like the tons of packages that become needed when the test flag is enabled. |
Oh i understand how USE flags and FEATURES work in general - i've created / updated / fixed ebuilds myself, and have futzed around with FEATURES for various purposes. It was the effect of the `debug` USE flag in this specific context that i wasn't sure of, which Hu has now addressed.
At any rate, i'm going to keep following this thread, because i seem to remember others encountering this sort issue a few times during the last several years, but i've not been able to find any relevant discussions in my browser history (or indeed via Web searches more generally) .... i initially thought it might have involved Gentoo users, but in the absence of being able to find anything, i also looked for Void-based discussions (as i was previously a Void user prior to moving to Gentoo a couple of years ago). Still nothing. :-/ |
|
| Back to top |
|
|
Demo
Tux's lil' helper
Joined: 25 Nov 2022
Posts: 126
|
| Posted: Fri Apr 05, 2024 5:09 pm Post subject: |
|
|
Well ...
No one seems to be interested anyway! |
|
| Back to top |
|
|
flexibeast
Guru
Joined: 04 Apr 2022
Posts: 449
Location: Naarm/Melbourne, Australia
|
| Posted: Sat Apr 06, 2024 1:14 am Post subject: |
|
|
More likely is, "No-one has any further ideas / suggestions about what the problem might be, or how to investigate further."
Even though the `debug` USE flag might now have effects on your system that it previously didn't, due to various other changes in the system, you don't seem willing to test that. Nor have you indicated that you've tried removing the `debug` argument from the relevant lines in your PAM config (e.g. the one i referenced). Methodically ruling out certain possibilities - "isolation testing" - can help narrow down where the problem might be, particularly in the absence of comments by someone who knows what the problem is likely to be.
In this context, people might be less willing to offer further suggestions, if they feel that you've already decided certain things "couldn't be the problem" (or at least contributing to it), and that it might thus be pointless to make such suggestions. |
|
| Back to top |
|
|
Demo
Tux's lil' helper
Joined: 25 Nov 2022
Posts: 126
|
| Posted: Sat Apr 06, 2024 7:19 am Post subject: |
|
|
It's not that I'm not willing to try, and I have 2 reasons ...
First, in gentoo, if you change a single use flag for a system component you're going to go through lots of compilations, I've done it, tried it, tried again, tried it over. Whenever you change a single use flag, half the system will ask you to recompile. And I know you mean only in a package.use file, not in the make.conf file.
Second, through the compilations you get circular dependencies, which is a stopper.
In addition to that, my intention in having the test, and debug flags is not just for the sake of putting text in the make.conf file. I wanted to try debugging c code as part of self paced learning. But it's not that successful. I wanted to expand the debug and test and add systemtap as well ...
I thought that gentoo would help, because in contrary to LFS, someone worked on a recipe for gentoo. |
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 22648
|
| Posted: Sat Apr 06, 2024 3:33 pm Post subject: |
|
|
| Demo wrote: | | First, in gentoo, if you change a single use flag for a system component you're going to go through lots of compilations |
That can happen sometimes, but not always. Did you at least emerge --pretend --verbose it here? What did that show? | Demo wrote: | | Second, through the compilations you get circular dependencies, which is a stopper. |
This can happen, but not always. Often, it means you need to make another change. However, I would not expect changing USE=debug here to cause a dependency loop. | Demo wrote: | | In addition to that, my intention in having the test, and debug flags is not just for the sake of putting text in the make.conf file. I wanted to try debugging c code as part of self paced learning. But it's not that successful. I wanted to expand the debug and test and add systemtap as well ... |
If that is your motivation, then I think you misunderstand what those flags do. I doubt that they would aid you in learning or debugging any particular language. |
|
| Back to top |
|
|
sam_
Developer
Joined: 14 Aug 2020
Posts: 1961
|
| Posted: Sat Apr 06, 2024 5:16 pm Post subject: |
|
|
Per the global USE flag description for USE=debug, it is not suitable to set globally. So don't do that.
As for USE=test, it doesn't really do anything by itself (it does control test deps, but not running them). You want FEATURES=test to run testsuites. |
|
| Back to top |
|
|
Demo
Tux's lil' helper
Joined: 25 Nov 2022
Posts: 126
|
| Posted: Sat Apr 06, 2024 9:01 pm Post subject: [Solved]xorg doesn't render text/message flood from pam in |
|
|
| Quote: | | Per the global USE flag description for USE=debug, it is not suitable to set globally. So don't do that. |
My understanding of use flags and features both, is that they pass over configuration options so the make script adds or removes a target from the build process. Passing on the --debug option to the ./configure script for example tells make to build the debug symbols that will help gdb know which object files ".so" the executable was linked to at the time of compilation for example, and other information.
The debug flag is just like any other flag, it's local with some packages, and global with others, I honestly don't know much about the difference. To me a use flag is useful only if the package supports it. Much like the cpu_flags_x86_sse2, if a package doesn't support it, then it has no effect, but when it's added to the make.conf file, it will be enabled by default to all packages supporting it.
| Quote: | | As for USE=test, it doesn't really do anything by itself (it does control test deps, but not running them). You want FEATURES=test to run testsuites. |
I do have both, but I think you got it in reverse, the test use flag is the ace, that doesn't work with some packages - I had an example at the top of my mind, then I forgot it -, but the rest are supported by it.
The problem with the testing on gentoo is that it's carried out by python and ruby scripts that are mutually dependent when you set up the flag globally, and setting a use flag per package for many packages is something very daunting, unless you're a scripting wizard, but you wouldn't need to use the test flag then!
| Quote: | | That can happen sometimes, but not always. Did you at least emerge --pretend --verbose it here? What did that show? |
Hu, I must apologize, but I already dumped my old gentoo installation, by that I mean I stored it into a xfs dump file. When there's time, I will restore it on a slower drive to know what happened. I promise you if I did that, I will send to you. I remember you asked me something similar last year and I promised you that if I did it, I'll send to you, but I didn't do the thing I promised to tell you about, whatever that was ...
| Quote: | | This can happen, but not always. Often, it means you need to make another change. However, I would not expect changing USE=debug here to cause a dependency loop. |
It happens so very frequently with the dev-python/* and dev-ruby/* packages, because as I mentioned, many packages from these categories - after the test flag is set globally - wants to be compiled with it unset because in the test section of it's ebuild file, happens to depend on another package that depends on the 1st package too in it's own test section.
It would be nice to create extra sub package sets, like @world and @system, and call them @testing, or @desktop, or @audio, etc. ... Suse and red hat linux have that feature in heir package managers. It's very practical.
| Quote: | | If that is your motivation, then I think you misunderstand what those flags do. I doubt that they would aid you in learning or debugging any particular language. |
I want both the test and debug flags setup for 2 reasons, first as you can see from my cluttered make.conf file, I tend to dabble with software, especially operating system core, so I wanted to measure what I'm doing. Second, in order to be sure about the measurement, I wanted to know if the base system was working as it should or not.
I'm not a sys admin pro, but I'm trying to find an opportunity to join the wagon - which is being taken over by AI as we speak. |
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 22648
|
| Posted: Sat Apr 06, 2024 10:23 pm Post subject: |
|
|
| Demo wrote: | | My understanding of use flags and features both, is that they pass over configuration options so the make script adds or removes a target from the build process. |
USE flags often, but not always, work this way. FEATURES can work this way, but usually are more about Portage logic. | Demo wrote: | | Passing on the --debug option to the ./configure script for example tells make to build the debug symbols that will help gdb know which object files ".so" the executable was linked to at the time of compilation for example, and other information. |
That might be true of some packages, but in general, no, that is not what will happen, nor is it the right way to get the result you describe. | Demo wrote: | | sam_ wrote: | | As for USE=test, it doesn't really do anything by itself (it does control test deps, but not running them). You want FEATURES=test to run testsuites. |
I do have both, but I think you got it in reverse, the test use flag is the ace, that doesn't work with some packages - I had an example at the top of my mind, then I forgot it -, but the rest are supported by it. |
No, sam_ is correct here. | Demo wrote: | | It would be nice to create extra sub package sets, like @world and @system, and call them @testing, or @desktop, or @audio, etc. ... Suse and red hat linux have that feature in heir package managers. It's very practical. |
Portage already supports custom sets, which allow you to define your own package lists. |
|
| Back to top |
|
|
sam_
Developer
Joined: 14 Aug 2020
Posts: 1961
|
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
