http://bugzilla.opensuse.org/show_bug.cgi?id=1183642http://bugzilla.opensuse.org/show_bug.cgi?id=1183642#c4
Tristan Miller <psychonaut(a)nothingisreal.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |psychonaut(a)nothingisreal.co
| |m
Flags|needinfo?(virex(a)mail.ru) |
--- Comment #4 from Tristan Miller <psychonaut(a)nothingisreal.com> ---
Same problem for me. X2Go was working fine with openSUSE-release-20220426 but
upon upgrading to openSUSE-release-20220515, x2goserver immediately disconnects
after accepting a connection. Reverting to the 20220426 system snapshot (via
snapper) works around the problem, but of course isn't a real solution.
At the time I was running a development version of x2goserver from September
2021. The problem persists when running the latest development versions of
x2goserver (and x2goclient, nx-libs, etc.) from today:
<https://download.opensuse.org/repositories/home:/psych0naut:/x2go/openSUSE_…>.
The operation of x2goclient is unaffected; it's still possible to connect to
X2Go servers running on earlier versions of Tumbleweed, or on Leap 15.3.
Running applications remotely directly with ssh -X sill works.
There is nothing obvious (to me, anyway) in the x2goclient, x2goserver, and
sshd logs that points to a cause, but I can provide these on request. An X2Go
developer is aware of the issue (see thread at
<https://lists.x2go.org/pipermail/x2go-user/2022-May/006813.html>) but also
doesn't seem to know what the problem might be. Our best guess is that some
update to the security or networking packages in Tumbleweed is the culprit.
I've already tried downgrading openssh (to the packages from 3 months ago), and
also temporarily disabling AppArmor, but that didn't help.
I'm clearing the needinfo flag as I believe Igor has already provided the
requested logs.
Let me know what other things I could try to downgrade. (I suppose I could
restore my snapshot from 20220426 and then start upgrading suspicious packages
one at a time until I find the ones that break X2Go, though that might take a
very long time.)
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1200003https://bugzilla.suse.com/show_bug.cgi?id=1200003#c1
Tom���� Ba��ant <tbazant(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |CONFIRMED
CC| |tbazant(a)suse.com
Assignee|fs(a)suse.com |tbazant(a)suse.com
Whiteboard| |https://jira.suse.com/brows
| |e/DOCTEAM-652
--- Comment #1 from Tom���� Ba��ant <tbazant(a)suse.com> ---
Thank you for reporting this bug!
It is being tracked and processed as part of our queue.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1200111
Bug ID: 1200111
Summary: Patch to fix samba-tool dbcheck functionality.
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.3
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Samba
Assignee: samba-maintainers(a)SuSE.de
Reporter: zombie.ryushu(a)zoho.com
QA Contact: samba-maintainers(a)SuSE.de
Found By: ---
Blocker: ---
This Patch was offered up by Andrew Bartlett to fix the samba-tool dbcheck
functionality in OpenSuse Leap 15.3
Patch may require a rediff.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1200091
Stefan Hundhammer <shundhammer(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |shundhammer(a)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=1200091https://bugzilla.suse.com/show_bug.cgi?id=1200091#c4
--- Comment #4 from Stefan Hundhammer <shundhammer(a)suse.com> ---
Summary:
There is an option to do that for experts, but with a zypper command line.
It is potentially dangerous to make this too easy to do casually for average
users; they might not realize the dangers that are involved. We don't mark
patches as "recommended" without a good reason.
I vote against changing that; IMHO it would be a change for the worse.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1199925https://bugzilla.suse.com/show_bug.cgi?id=1199925#c3
--- Comment #3 from Petr Vorel <petr.vorel(a)suse.com> ---
FYI even the latest test
nsuse-Tumbleweed-JeOS-for-kvm-and-xen-x86_64-Build20220531-jeos-ltp-syscalls@uefi_virtio-2G
[1] (which is using package from factory [2]) is still using old unfixed
version bf9678782 ("tst_test: Remove timeout stubs") due kvm_pagefault01 error
[3]:
[ 1058s] ltp.x86_64: E: executable-stack (Badness: 10000)
/opt/ltp/testcases/bin/kvm_pagefault01
[ 1058s] The binary declares the stack as executable. Executable stack is
usually an
[ 1058s] error as it is only needed if the code contains GCC trampolines or
similar
[ 1058s] constructs which uses code on the stack. One common source for
needlessly
[ 1058s] executable stack cases are object files built from assembler files
which don't
[ 1058s] define a proper .note.GNU-stack section.
...
[ 1058s] ---------------- Badness 10214 exceeds threshold 999, aborting.
----------------
(there are many errors, but this one is considered that serious that it breaks
build).
Can anybody advice me how to allow LTP being build with kvm_pagefault01 being
included in the package?
[1] https://openqa.opensuse.org/tests/2397961#next_previous
[2]
https://download.opensuse.org/repositories/benchmark:/ltp:/devel/openSUSE_F…
[3]
https://build.opensuse.org/package/live_build_log/benchmark:ltp:devel/ltp/o…
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1200091https://bugzilla.suse.com/show_bug.cgi?id=1200091#c2
--- Comment #2 from Stefan Hundhammer <shundhammer(a)suse.com> ---
To cover your use case, however, there is a simple alternative with zypper
commands:
sudo zypper list-patches -g security
and
sudo zypper patch -g security
In the YaST online update GUI, there is no counterpart; but IIRC security and
recommended patches are preselected by default (optional patches are not) which
is appropriate for most users.
--
You are receiving this mail because:
You are on the CC list for the bug.