http://bugzilla.opensuse.org/show_bug.cgi?id=1194322
Bug ID: 1194322
Summary: eth0 report update as boot completes causes screen to
clear, in spite of --noclean agetty option
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86-64
OS: Other
Status: NEW
Severity: Minor
Priority: P5 - None
Component: Basesystem
Assignee: screening-team-bugs(a)suse.de
Reporter: mrmazda(a)earthlink.net
QA Contact: qa-bugs(a)suse.de
CC: sbrabec(a)suse.com
Blocks: 1168405
Found By: ---
Blocker: ---
Created attachment 854979
--> http://bugzilla.opensuse.org/attachment.cgi?id=854979&action=edit
/etc/systemd/system/getty.target.wants/getty(a)tty1.service
Original Summary:
eth0 report update as boot completes causes screen to clear, in spite of
--noclean agetty option
This began with TW very long ago and applies to 15.4 and 15.3 as well. 15.2 was
OK.
To reproduce:
1-uninstall or disable Plymouth
2-Include
ExecStart=-/sbin/agetty -o '-p -- \\u' --noclear %I $TERM
in
/etc/systemd/system/getty.target.wants/getty(a)tty1.service
3-boot without quiet or splash=silent, and with noresume added to, linu line in
grub.cfg
Actual behavior:
1-post KMS-engagement text messages appear onscreen ending with:
a: Welcome to openSUSE...(tty1).
b: eth0:
c: <hostname> login:
2-screen clears to only:
a: Welcome to openSUSE...(tty1).
b: eth0: xxx.xxx.xxx.xxx
c: <hostname> login:
3-EOF
Expected behavior:
1-post KMS-engagement text messages appear onscreen ending with:
a: Welcome to openSUSE...(tty1).
b: eth0:
c: <hostname> login:
2-EOF
Other data:
# systemd-analyze critical-chain
...
������multi-user.target @2.465s
������kbdsettings.service @400ms +2.064s
������basic.target @396ms
������sockets.target @396ms
������telnet.socket @396ms
������sysinit.target @394ms
������systemd-timesyncd.service @366ms +27ms
������systemd-tmpfiles-setup.service @356ms +8ms
������local-fs.target @355ms
������usr-local.mount @351ms +3ms
������systemd-fsck(a)dev-disk-by\x2dlabel-tm8p04usrlcl.service
@330ms +19ms
������local-fs-pre.target @327ms
������lvm2-monitor.service @246ms +80ms
������dm-event.socket @239ms
������system.slice
������-.slice
# systemctl status systemd-networkd
��� systemd-networkd.service - Network Configuration
Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; enabled;
vendor preset: disabled)
Active: active (running) since Tue 2022-01-04 20:35:46 EST; 9min ago
TriggeredBy: ��� systemd-networkd.socket
Docs: man:systemd-networkd.service(8)
Main PID: 572 (systemd-network)
Status: "Processing requests..."
Tasks: 1 (limit: 4915)
CPU: 47ms
CGroup: /system.slice/systemd-networkd.service
������572 /usr/lib/systemd/systemd-networkd
Jan 04 20:35:46 ab560 systemd[1]: Starting Network Configuration...
Jan 04 20:35:46 ab560 systemd-networkd[572]: lo: Link UP
Jan 04 20:35:46 ab560 systemd-networkd[572]: lo: Gained carrier
Jan 04 20:35:46 ab560 systemd-networkd[572]: Enumeration completed
Jan 04 20:35:46 ab560 systemd[1]: Started Network Configuration.
Jan 04 20:35:48 ab560 systemd-networkd[572]: eth0: Link UP
Jan 04 20:35:51 ab560 systemd-networkd[572]: eth0: Gained carrier
# rpm -qa | egrep -i 'NetworkManager|Wicked'
#
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1182554
Bug ID: 1182554
Summary: cannot start greetd.service .... missing PAM module
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86-64
OS: openSUSE Tumbleweed
Status: NEW
Severity: Enhancement
Priority: P5 - None
Component: Other
Assignee: screening-team-bugs(a)suse.de
Reporter: mcepl(a)suse.com
QA Contact: qa-bugs(a)suse.de
CC: denis.kondratenko(a)suse.com, mcepl(a)suse.com,
opensuse(a)trummer.xyz, stdden(a)opensuse.org
Found By: ---
Blocker: ---
Created attachment 846366
--> https://bugzilla.suse.com/attachment.cgi?id=846366&action=edit
journalctl -xb output
When trying to replace gdm with greetd following the steps on
https://en.opensuse.org/Portal:OpenSUSEway, greetd fails to start and journal
shows:
�no 22 09:38:10 stitny greetd[2347]: error: PAM 'greetd' service missing
When looking around, there is the file /usr/etc/pam.d/greetd with this content:
~@stitny$ cat /usr/etc/pam.d/greetd
#%PAM-1.0
auth requisite pam_nologin.so
auth include common-auth
account include common-account
password include common-password
session required pam_loginuid.so
session optional pam_keyinit.so force revoke
session include common-session
~@stitny$
but I have still /etc/pam.d/ as well and there is no greetd file. Which one is
used?
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1177260
Bug ID: 1177260
Summary: Switching python-numpy to plain BLAS causes
significant performance regression
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Basesystem
Assignee: screening-team-bugs(a)suse.de
Reporter: stefan.bruens(a)rwth-aachen.de
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
https://build.opensuse.org/request/show/835366 switched numpy to plain
BLAS/LAPACK, which causes a significant performance regression:
---
import numpy as np
import time
n = 4000
start_time = time.time()
A = np.random.randn(n,n).astype('float64')
B = np.random.randn(n,n).astype('float64')
print(" init took {} seconds ".format(time.time() - start_time))
start_time = time.time()
m = A@B
print(" mmult took {} seconds ".format(time.time() - start_time))
print(np.__config__.show())
---
python3-numpy-1.19.1 with openblas: mmult took 2.4579274654388428 seconds
python3-numpy-1.19.2 with blas/lapack: mmult took 877.8246397972107 seconds
python3-numpy-1.19.2 with openblas: mmult took 2.6917877197265625 seconds
MMult 4000x4000 is 64e9 multiplications and additions, thats ~150kOps/s for
BLAS/LAPACK.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1165273
Bug ID: 1165273
Summary: zathura-plugin-pdf-mupdf not loaded due to error.
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86-64
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Other
Assignee: screening-team-bugs(a)suse.de
Reporter: dracaphallus(a)gmail.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML,
like Gecko) Chrome/80.0.3987.100 Safari/537.36
Build Identifier:
Running zathura after the installation of zathura-plugin-pdf-mupdf the
following error output is produced:
```
error: Could not load plugin '/usr/lib64/zathura/libpdf-mupdf.so'
(/usr/lib64/zathura/libpdf-mupdf.so: undefined symbol: jpeg_resync_to_restart).
```
>From the error output I'd deduced that the package was packaged wrong and
therefore produced the error mentioned above. It has the plugin from working as
intended by making zathura incapable of opening the supported document formats
(PDF, ePub, and OpenXPS).
This issue was reported 14 days ago using the comment section of
openSUSE:Factory, while it was reported 8 days ago in the comment section of
`X11:Utilities` with no response. This has lead me to file a bug report in
OpenSUSE Bugzilla with the hope of getting this issue resolved.
Reproducible: Always
Steps to Reproduce:
1. Installing zathura-plugin-pdf-mupdf using zypper.
2. Running zathura through terminal.
Actual Results:
The following error was produced:
```
error: Could not load plugin '/usr/lib64/zathura/libpdf-mupdf.so'
(/usr/lib64/zathura/libpdf-mupdf.so: undefined symbol: jpeg_resync_to_restart).
```
Expected Results:
Zathura being able to open the supported document formats (PDF, ePub, and
OpenXPS).
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1200564
Bug ID: 1200564
Summary: io_uring instability on ppc64
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: PowerPC-64
OS: Other
Status: NEW
Severity: Major
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs(a)opensuse.org
Reporter: dmueller(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
when using aio=io_uring in qemu for KVM virtual machine guests on a SLE15SP4 or
a opensuse tumbleweed host kernel on power8 or power9 machine, we have very
rapid I/O corruption (within milliseconds-seconds) in the guest. on all other
architectures things work perfectly fine.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1195094
Bug ID: 1195094
Summary: nVidia: Remove generic (fb) driver first ...
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86-64
OS: openSUSE Tumbleweed
Status: NEW
Severity: Enhancement
Priority: P5 - None
Component: X11 3rd Party Driver
Assignee: gfx-bugs(a)suse.de
Reporter: sndirsch(a)suse.com
QA Contact: sndirsch(a)suse.com
Found By: ---
Blocker: ---
Users of nVidia's proprietary driver are running into issues with the
introduction of 'simpledrm'.
https://forums.developer.nvidia.com/t/510-39-01-on-5-16-0-kernel-green-scre…
There are workarounds available like
a) patching the nvidia kernel module and no longer calling
pci_request_regions(...) function
b) Kernel option 'initcall_blacklist=simpledrm_platform_driver_init'
c) Kerneloption ' fbcon=map:1'.
But the culprit is that nVidia doesn't remove the generic driver (e.g.
efifb/vesafb) first. This should be changed to address the real issue here.
API under MIT license
https://elixir.bootlin.com/linux/latest/source/include/drm/drm_aperture.h
Example for nouveau driver.
https://elixir.bootlin.com/linux/latest/source/drivers/gpu/drm/nouveau/nouv…
Thomas is the author of 'simpledrm'. Please correct me, if I misunderstood
anything and feel free to add more details here.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1200983
Bug ID: 1200983
Summary: mouse & keyboard not available in X/plasma
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86-64
OS: openSUSE Tumbleweed
Status: NEW
Severity: Normal
Priority: P5 - None
Component: X.Org
Assignee: gfx-bugs(a)suse.de
Reporter: opensuse(a)mike.franken.de
QA Contact: gfx-bugs(a)suse.de
Found By: ---
Blocker: ---
Starting with a few Tumbleweed snapshots ago I always have the problem, that
mouse and keyboard are not working in my X/plasma desktop.
I always have to unplug und plug them in again. After that they work as
expected.
There are no obvious error messages, that could help me to solve this problem.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1196048
Bug ID: 1196048
Summary: audit file watches do not really work?
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs(a)opensuse.org
Reporter: meissner(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
auditctl -e 1
auditctl -w /etc/issue
if i do
echo hallo >> /etc/issue
-> not audited
if i do
vim /etc/issue
... remove hallo line and save ...
-> audited
cat /etc/issue
-> not audited
Not sure if I am doing it right.
--
You are receiving this mail because:
You are on the CC list for the bug.