https://bugzilla.suse.com/show_bug.cgi?id=1197178
Bug ID: 1197178
Summary: agetty should give a sensible name when "-" is passed
as tty port
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: fbui(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
agetty allows to pass "-" as tty port argument and in this case it assumes that
its stdin is already connected to a tty.
However instead of figuring out the real name of "-", it keeps "-" as tty name
internally which leads to uses of '\l' specifier in /etc/issue being
substituted with '-', which is not meaningful.
Can this be fixed so when "-" is passed as argument to agetty, '\l' in
/etc/issue is substituted with the actual name of the tty device being
connected ?
Thanks.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1194945
Bug ID: 1194945
Summary: Cifs `umount` returns 32 and `df` fails with no
permission
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.2
Hardware: Other
OS: openSUSE Leap 15.2
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Kernel
Assignee: kernel-bugs(a)opensuse.org
Reporter: mantel(a)pre-sense.de
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Created attachment 855424
--> https://bugzilla.suse.com/attachment.cgi?id=855424&action=edit
cifs kernel debug output
Hello!
We have encountered two CIFS-issues which appear reproducible. But the
conditions
to reproduce are unknown to us. The setup is the following:
- An linux client which mounts a cifs share.
- Windows Server which offers the cifs share. Sadly, we could not determine
which windows server versions are related in the bugs.
- The cifs share contains subfolders for various users, which are readable
for the users.
- The parent folder is readable, but not writable for the users.
- Example: //domain_name/company_users/username
- company_users is a directory. the user has readonly permissions on that
directory.
- username is a subdirectory of company_users. the user has write
permissions on that directory.
We encounter two CIFS-issues. They might be considered as two seperate bugs,
but since
they occur in the same setup I just list them here:
- `df` fails with permission denied when using it on the share.
- `umount` of a cifs share fails with status code 32. Before the update to
openSUSE Leap 15.2 the umount operation worked. It seems to be a regression.
We could determine the kernel version which introduced the `umount` regression:
ok 5.3.18-lp152.63.1
ok 5.3.18-lp152.66.2
ok 5.3.18-lp152.69.1 --> last kernel which can umount
FAIL 5.3.18-lp152.72.1
FAIL 5.14.15-lp153.2.1.g3416a5a
In an upstream forum was a description for enhanced debug informations of the
kernel. You
can find enhanced debug output in an attached file, at the end of the file
(lines 721 - 739).
You can also find the `df` permission denied at line 422. We dont know this is
an actual regression. Every kernel we tried from openSUSE Leap 15.2 didn't
work.
We would like to debug this more but we have no clue how to continue at this
point.
Any help is welcome.
Thanks, Alex
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1186365
Bug ID: 1186365
Summary: Empty screen on Live XFCE in QEMU with virgl
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.3
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Xfce
Assignee: bnc-team-xfce(a)forge.provo.novell.com
Reporter: arvidjaar(a)gmail.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
I observed this both with Leap 15.3 current image and with Tumbleweed.
I boot manually using
"${QEMU_BIN}" \
-nodefaults \
-machine q35,accel=kvm \
-cpu kvm64 \
-m 2G \
-device virtio-scsi-pci \
-drive
file=$HOME/tmp/openSUSE-Leap-15.3-XFCE-Live-x86_64-Build9.78-Media.iso,if=none,id=cd0,format=raw
-device scsi-cd,drive=cd0,id=cd0 \
-netdev user,id=uplink -device virtio-net-pci,netdev=uplink \
-name "Leap 15.3 Live XFCE" \
-monitor unix:path="$QEMU_MONITOR_SOCKET",server=on,wait=off \
-vga virtio -display gtk,gl=on,zoom-to-fit=off,show-cursor=on \
&
It boots and leaves me with empty screen. Switching to tty1 and logging in I
see full graphical session correctly started, all processes present, just no
output on tty7. This works if I disable OpenGL (-display gtk,gl=off).
The KDE Live image boots normally using the same command line. TW XFCE Live
image has the same issue. Regular TW GNOME and KDE both work with virgl.
Host - Ubuntu 20.04 with GNOME Wayland session.
QEMU emulator version 6.0.0 (v6.0.0-1-gd11fb9fde1)
virglrenderer-0.7.0-1138-g3639155
Both compiled from source. QEMU has single patch to fix mouse positioning in
gtk under Wayland.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1193984
Bug ID: 1193984
Summary: SELinux: targeted: rpcinfo violation
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.3
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Other
Assignee: screening-team-bugs(a)suse.de
Reporter: okir(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
This is with Leap 15.3 and the targeted SELinux policy from MicroOS 5.1
This is a two-node configuration. Running rpcinfo on the client, trying to
perform a NULL call to the server's rpcbind:
/sbin/rpcinfo -T udp $server_ip portmapper
The test user is tied to SELinux user staff_u.
This results in the following audit message:
audit: type=1400 audit(1640160326.582:12): avc: denied { name_bind } for
pid=4754 comm="rpcinfo" src=690 scontext=staff_u:staff_r:staff_t:s0-s0:c0.c1023
tcontext=system_u:object_r:hi_reserved_port_t:s0 tclass=udp_socket permissive=1
It's possible that this is harmless (rpcinfo may just try to do a
bindresvport() call in case it's running with privileges). However, in order to
avoid noise, we may want to patch this out for euid != 0.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1199548
Bug ID: 1199548
Summary: GQRX 2.15.9-1.7-x86-64 segfaults on starting
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86-64
OS: openSUSE Tumbleweed
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Other
Assignee: screening-team-bugs(a)suse.de
Reporter: rskunath(a)gmail.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
GQRX 2.15.9-1.7-x86-64 segfaults on starting.
This is new behavior and was true on version 2.15.8 (mnhauke repo)and also on
2.15.9 (Software Defined Radio repo) after the roll-out of the large Tumbleweed
updateyesterday.
I get no additional information on the segfault when running GQRX in gdb, and I
do have the 2 debug packages for GQRX installed.
I'd be happy to provide anything additional that would help determine what the
cause of the segfault is.
Thanks in advance.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1195904
Bug ID: 1195904
Summary: SELinux: targeted: ssh violation
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.3
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Basesystem
Assignee: screening-team-bugs(a)suse.de
Reporter: okir(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
The following happens with the SELinux packages from MicroOS 5.1 on SLES15SP3.
User "testuser" has been assigned SELinux user user_u and attempts to log in
via ssh, using key authentication
TEST: verify that the SSH key we generated can be used for authentication
== Authorizing ssh key id_rsa ==
client: echo $HOME; user=testuser
client: downloading /home/testuser/.ssh/id_rsa.pub
server: mkdir -m 0755 -p ~/.ssh; user=testuser
server: uploading data to /home/testuser/.ssh/authorized_keys
client: ssh -oStrictHostKeyChecking=no server true; user=testuser
Warning: Permanently added 'server,192.168.121.205' (ECDSA) to the list of
known hosts.
Failing: server: SELinux policy violation
server: by systemd (pid=4281; context=user_u:user_r:user_t:s0; permissive=1)
server: create access to dir inaccessible (dev=None; ino=None;
context=system_u:object_r:user_tmp_t:s0)
server: create access to file reg (dev=None; ino=None;
context=system_u:object_r:user_tmp_t:s0)
server: create access to fifo_file fifo (dev=None; ino=None;
context=system_u:object_r:user_tmp_t:s0)
server: create access to sock_file sock (dev=None; ino=None;
context=system_u:object_r:user_tmp_t:s0)
server: create access to lnk_file .#invocation:dbus.socketbf6abda56b666fe5
(dev=None; ino=None; context=system_u:object_r:user_tmp_t:s0)
OK, RSA key authentication seems to work
FAIL: server: SELinux policy violation
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1189907
Bug ID: 1189907
Summary: gnome-software: packages from the main distro
repository should not be marked as potentially
dangerous
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: GNOME
Assignee: gnome-bugs(a)suse.de
Reporter: mrueckert(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
it should work more like software.o.o categorizes packages.
i think the main culprit might be that it doesnt have any permissions
information like it has for flatpak based apps.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1172650
Bug ID: 1172650
Summary: MicroOS: License not displayed in german
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: axel.braun(a)gmx.de
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Created attachment 838577
--> http://bugzilla.opensuse.org/attachment.cgi?id=838577&action=edit
empty license screen
When installing MicroOS (snapshot:20200604) in german, the installation page
'Language, Keyboard and license contains am empty license
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1199964
Bug ID: 1199964
Summary: Bogus "Limited Connectivity" on ethernet
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Minor
Priority: P5 - None
Component: Network
Assignee: screening-team-bugs(a)suse.de
Reporter: pedrohqb(a)gmail.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Not affecting actual connectivity. It claims there's no connection to internet.
The bogus message started after an update last week. Affects all my TW system
on KDE and Gnome as well.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1194705
Bug ID: 1194705
Summary: [SELinux] Problems with colord
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Security
Assignee: security-team(a)suse.de
Reporter: mcepl(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
See what I���ve found in the journal:
Jan 14 17:11:08 stitny colord[19334]: CdMain: failed to load mapping database:
Can't open database: unable to open database file
Jan 14 17:11:08 stitny systemd[1]: colord.service: Main process exited,
code=exited, status=1/FAILURE
Jan 14 17:11:08 stitny systemd[1]: colord.service: Failed with result
'exit-code'.
Jan 14 17:11:08 stitny systemd[1]: Failed to start Manage, Install and Generate
Color Profiles.
Jan 14 17:11:08 stitny kernel: audit: type=1400 audit(1642176668.663:44015):
avc: denied { read write } for pid=19334 comm="colord" name="mapping.db"
dev="nvme0n1p2" ino=14847 scontext=system_u:system_r:init_t:s0
tcontext=system_u:object_r:colord_var_lib_t:s0 tclass=file permissive=0
Jan 14 17:11:08 stitny kernel: audit: type=1400 audit(1642176668.663:44016):
avc: denied { read } for pid=19334 comm="colord" name="mapping.db"
dev="nvme0n1p2" ino=14847 scontext=system_u:system_r:init_t:s0
tcontext=system_u:object_r:colord_var_lib_t:s0 tclass=file permissive=0
Using colord-1.4.5-4.2.x86_64 and selinux-policy-20211111-1.2.noarch
--
You are receiving this mail because:
You are on the CC list for the bug.