https://bugzilla.suse.com/show_bug.cgi?id=1198309 https://bugzilla.suse.com/show_bug.cgi?id=1198309#c1 Noel Power <nopower@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nopower@suse.com --- Comment #1 from Noel Power <nopower@suse.com> --- (In reply to Igor Kuznetsov from comment #0)

After last updates samba did not work

Whyle starting got the error [2022/04/11 13:00:35.927769, 0] ../../source3/smbd/server.c:1741(main) but status is active

systemctl status smb ��� smb.service - Samba SMB Daemon Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled; vendor preset: disabled) Active: active (running) since Mon 2022-04-11 13:00:36 +04; 9min ago Docs: man:smbd(8) man:samba(7) man:smb.conf(5) Process: 6290 ExecStartPre=/usr/share/samba/update-apparmor-samba-profile (code=exited, status=0/SUCCESS) Main PID: 6294 (smbd) Status: "smbd: ready to serve connections..." Tasks: 4 (limit: 4915) CPU: 158ms CGroup: /system.slice/smb.service ������6294 /usr/sbin/smbd --foreground --no-process-group ������6296 /usr/sbin/smbd --foreground --no-process-group ������6297 /usr/sbin/smbd --foreground --no-process-group ������6738 /usr/sbin/smbd --foreground --no-process-group

������ 11 13:00:35 lnxvrx53 systemd[1]: Starting Samba SMB Daemon... ������ 11 13:00:35 lnxvrx53 smbd[6294]: [2022/04/11 13:00:35.927769, 0] ../../source3/smbd/server.c:1741(main) ������ 11 13:00:35 lnxvrx53 smbd[6294]: smbd version 4.16.0-git.224.70319beb8f8SUSE-oS15.9-x86_64 started. ������ 11 13:00:35 lnxvrx53 smbd[6294]: Copyright Andrew Tridgell and the Samba Team 1992-2022 ������ 11 13:00:36 lnxvrx53 systemd[1]: Started Samba SMB Daemon.

these messages and the status are showing that samba is running normally -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1198309 https://bugzilla.suse.com/show_bug.cgi?id=1198309#c3 Igor Kuznetsov <virex@mail.ru> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID |--- --- Comment #3 from Igor Kuznetsov <virex@mail.ru> --- Sorry, It is running but clients can not connect to samba -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1198309 Marcus Meissner <meissner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1198309 https://bugzilla.suse.com/show_bug.cgi?id=1198309#c23 --- Comment #23 from Igor Kuznetsov <virex@mail.ru> --- After updates at 18.04.2022 samba clients can see the shares, but can not open them. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1198309 https://bugzilla.suse.com/show_bug.cgi?id=1198309#c29 Samuel Cabrero <scabrero@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |scabrero@suse.com Depends on| |1198718 --- Comment #29 from Samuel Cabrero <scabrero@suse.com> --- (In reply to Felix Niederwanger from comment #25)

I think we talk here about two separate issues. Currently on Tumbleweed I cannot mount any samba shares from caja or nautilus. This issue is unrelated to AppArmor because I can reproduce it on a TW VM where I completely disabled apparmor.

Hi Felix, you are right, there are two different problems. I created bsc#1198718 for the gvfs bug. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1198309 Bug 1198309 depends on bug 1198718, which changed state. Bug 1198718 Summary: gvfs: Invalid argument mounting SMB shares https://bugzilla.suse.com/show_bug.cgi?id=1198718 What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1198309 https://bugzilla.suse.com/show_bug.cgi?id=1198309#c33 --- Comment #33 from openQA Review <openqa-review@suse.de> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: extra_tests_filesystem https://openqa.opensuse.org/tests/2335470#step/cifs/1 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" or "EOL" (End-of-Life) 3. The bugref in the openQA scenario is removed or replaced, e.g. `label:wontfix:boo1234` Expect the next reminder at the earliest in 28 days if nothing changes in this ticket. -- You are receiving this mail because: You are on the CC list for the bug.