August 2022 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1201822] New: VUL-0: CVE-2022-34037: caddy: oob read allows for DoS
by bugzilla_noreply＠suse.com 06 Aug '22

06 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1201822 Bug ID: 1201822 Summary: VUL-0: CVE-2022-34037: caddy: oob read allows for DoS Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other URL: https://smash.suse.de/issue/338088/ OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Security Assignee: alexandre.vicenzi(a)suse.com Reporter: cathy.hu(a)suse.com QA Contact: security-team(a)suse.de Found By: Security Response Team Blocker: --- rh#2110269 An out-of-bounds read in the rewrite function at /modules/caddyhttp/rewrite/rewrite.go in Caddy v2.5.1 allows attackers to cause a Denial of Service (DoS) via a crafted URI. https://github.com/caddyserver/caddy/issues/4775 References: https://bugzilla.redhat.com/show_bug.cgi?id=2110269 http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-34037 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-34037 https://github.com/caddyserver/caddy/issues/4775 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1194854] New: eclipse install from java packages sle_15_sp4 crashes on start up
by bugzilla_noreply＠suse.com 06 Aug '22

06 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1194854 Bug ID: 1194854 Summary: eclipse install from java packages sle_15_sp4 crashes on start up Classification: openSUSE Product: openSUSE Backports Version: SLE-15-SP4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Critical Priority: P5 - None Component: Packages Assignee: packagehub-bugs(a)suse.com Reporter: zacharykraus(a)yahoo.com QA Contact: packagehub-bugs(a)suse.com Found By: --- Blocker: --- Created attachment 855379 --> http://bugzilla.opensuse.org/attachment.cgi?id=855379&action=edit Java error I think this is in the right location. I installed eclipse from https://download.opensuse.org/repositories/Java:/packages/SLE_15_SP4/. When you start up from gnome bar the eclipse logo pops up and than disappears. if you try running from the terminal, you get this print out: "CompileCommand: exclude org/eclipse/core/internal/dtree/DataTreeNode.forwardDeltaWith CompileCommand: exclude org/eclipse/jdt/internal/compiler/lookup/ParameterizedMethodBinding.<init> CompileCommand: exclude org/eclipse/cdt/internal/core/dom/parser/cpp/semantics/CPPTemplates.instantiateTemplate CompileCommand: exclude org/eclipse/cdt/internal/core/pdom/dom/cpp/PDOMCPPLinkage.addBinding CompileCommand: exclude org/python/pydev/editor/codecompletion/revisited/PythonPathHelper.isValidSourceFile CompileCommand: exclude org/eclipse/tycho/core/osgitools/EquinoxResolver.newState free(): invalid pointer" The error file produced in my home directory has been attached.it reports the java vm crashing. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1202190] New: Eclipse IDE fails to start after update
by bugzilla_noreply＠suse.com 06 Aug '22

06 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202190 Bug ID: 1202190 Summary: Eclipse IDE fails to start after update Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Java Assignee: java-maintainers(a)suse.de Reporter: opensuseforum(a)thefifthcontinent.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After updating on 2022-08-05 (openSUSE Tumbleweed 20220729-0 -> 20220804-0) the Eclipse IDE silently closes itself on startup. Rolling back fixes the issue. Link to original eclipse bug report: https://github.com/eclipse-platform/.github/issues/47 -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1202189] New: Polkit pkexec split breaks desktop applications
by bugzilla_noreply＠suse.com 06 Aug '22

06 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202189 Bug ID: 1202189 Summary: Polkit pkexec split breaks desktop applications Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: georg.pfuetzenreuter(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, a user in #opensuse reported `gparted` to no longer launch if started without root privileges since the last update of Tumbleweed. Investigation revealed that this is caused by https://build.opensuse.org/request/show/989831 no longer providing `pkexec` by default. I submitted a patch for `gparted` (https://build.opensuse.org/request/show/993466) however I still like to address this bug in a broader scheme. It seems other applications faced the same issue, and got a "Recommends: pkexec" added as a solution, for example Nautilus (https://bugzilla.opensuse.org/show_bug.cgi?id=1202070) But it seems clear that this won't be the only applications facing the issue - other desktop programs utilizing `pkexec` are likely to be affected as well. - Can we trace all affected applications and add the necessary "Recommends: pkexec" to them? - Alternatively, as suggested by the reporter in IRC, would it be feasible to add `pkexec` to one of the desktop patterns? Best, Georg -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1202036] New: Screen share in Plasma Wayland does not work
by bugzilla_noreply＠suse.com 06 Aug '22

06 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1202036 Bug ID: 1202036 Summary: Screen share in Plasma Wayland does not work Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: noga.dany(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Screen share in Plasma Wayland does not work. Leap 15.4, KDE Plasma wayland, Intel integrated GPU from i5-11400H, no NVidia on this computer. Tested in Flatpak OBS Studio, Flatpak Chrome with enabled WebRTC PipeWire support, rpm Firefox. Dialog for screen share correctly opens, but then only empty mononitor is shared. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1201107] New: windows:mingw:win32/mingw32-
by bugzilla_noreply＠suse.com 06 Aug '22

06 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201107 Bug ID: 1201107 Summary: windows:mingw:win32/mingw32- Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: fstrba(a)suse.com Reporter: ralf.habacker(a)freenet.de QA Contact: screening-team-bugs(a)suse.de CC: fridrich.strba(a)bluewin.ch, hib(a)hiberis.nl, mkbosmans(a)gmail.com Found By: --- Blocker: --- Several packages like mingw32-liborcus fails to extract symbols caused by a crash of i686-w64-mingw32-dump_syms: [ 118s] extracting debug info from /home/abuild/rpmbuild/BUILDROOT/mingw32-liborcus-0.11.2-lp153.6.1.x86_64/usr/i686-w64-mingw32/sys-root/mingw/bin/orcus-ods.exe [ 118s] /usr/bin/i686-w64-mingw32-gen_sym_files: line 30: 17860 Segmentation fault i686-w64-mingw32-dump_syms $1 $PATH_MAP > $SYMFILE and later [ 129s] mingw32-liborcus-debug.noarch: W: zero-length /usr/i686-w64-mingw32/sys-root/mingw/symbols/liborcus-0.11-0.dll/liborcus-0.11-0.dll.sym [ 129s] mingw32-liborcus-debug.noarch: W: zero-length /usr/i686-w64-mingw32/sys-root/mingw/symbols/liborcus-mso-0.11-0.dll/liborcus-mso-0.11-0.dll.sym [ 129s] mingw32-liborcus-debug.noarch: W: zero-length /usr/i686-w64-mingw32/sys-root/mingw/symbols/liborcus-parser-0.11-0.dll/liborcus-parser-0.11-0.dll.sym [ 129s] mingw32-liborcus-debug.noarch: W: zero-length /usr/i686-w64-mingw32/sys-root/mingw/symbols/liborcus-spreadsheet-model-0.11-0.dll/liborcus-spreadsheet-model-0.11-0.dll.sym [ 129s] mingw32-liborcus-debug.noarch: W: zero-length /usr/i686-w64-mingw32/sys-root/mingw/symbols/orcus-css-dump.exe/orcus-css-dump.exe.sym [ 129s] mingw32-liborcus-debug.noarch: W: zero-length /usr/i686-w64-mingw32/sys-root/mingw/symbols/orcus-csv.exe/orcus-csv.exe.sym [ 129s] mingw32-liborcus-debug.noarch: W: zero-length /usr/i686-w64-mingw32/sys-root/mingw/symbols/orcus-detect.exe/orcus-detect.exe.sym [ 129s] mingw32-liborcus-debug.noarch: W: zero-length /usr/i686-w64-mingw32/sys-root/mingw/symbols/orcus-json.exe/orcus-json.exe.sym [ 129s] mingw32-liborcus-debug.noarch: W: zero-length /usr/i686-w64-mingw32/sys-root/mingw/symbols/orcus-mso-encryption.exe/orcus-mso-encryption.exe.sym [ 129s] mingw32-liborcus-debug.noarch: W: zero-length /usr/i686-w64-mingw32/sys-root/mingw/symbols/orcus-ods.exe/orcus-ods.exe.sym [ 129s] mingw32-liborcus-debug.noarch: W: zero-length /usr/i686-w64-mingw32/sys-root/mingw/symbols/orcus-xls-xml.exe/orcus-xls-xml.exe.sym [ 129s] mingw32-liborcus-debug.noarch: W: zero-length /usr/i686-w64-mingw32/sys-root/mingw/symbols/orcus-xlsx.exe/orcus-xlsx.exe.sym [ 129s] mingw32-liborcus-debug.noarch: W: zero-length /usr/i686-w64-mingw32/sys-root/mingw/symbols/orcus-xml-dump.exe/orcus-xml-dump.exe.sym [ 129s] mingw32-liborcus-debug.noarch: W: zero-length /usr/i686-w64-mingw32/sys-root/mingw/symbols/orcus-xml.exe/orcus-xml.exe.sym [ 129s] mingw32-liborcus-debug.noarch: W: zero-length /usr/i686-w64-mingw32/sys-root/mingw/symbols/orcus-yaml.exe/orcus-yaml.exe.sym [ 129s] mingw32-liborcus-debug.noarch: W: zero-length /usr/i686-w64-mingw32/sys-root/mingw/symbols/orcus-zip-dump.exe/orcus-zip-dump.exe.sym [ 129s] 8 packages and 0 specfiles checked; 0 errors, 29 warnings. see https://build.opensuse.org/package/live_build_log/windows:mingw:win32/mingw… for the related build log The crashing tool i686-w64-mingw32-dump_syms is located in rpm -q -f `which i686-w64-mingw32-dump_syms` mingw32-cross-breakpad-tools-20140827-lp153.13.1.x86_64 -- You are receiving this mail because: You are on the CC list for the bug.

1 25

[Bug 1201772] New: LXQt Configuration Center-> keyboard and mouse module not function
by bugzilla_noreply＠suse.com 06 Aug '22

06 Aug '22

https://bugzilla.suse.com/show_bug.cgi?id=1201772 Bug ID: 1201772 Summary: LXQt Configuration Center-> keyboard and mouse module not function Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: LXQt Assignee: mvetter(a)suse.com Reporter: viking018-mailbox(a)yahoo.co.uk QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Upon click on above mention option from menu "Preferences->LXQt Settings->Keyboard and Mouse" there is not widow pop-up or error message. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1201660] New: iio-sensor-proxy-3.3-1.5.x86_64 contains an invalid systemd service file
by bugzilla_noreply＠suse.com 06 Aug '22

06 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1201660 Bug ID: 1201660 Summary: iio-sensor-proxy-3.3-1.5.x86_64 contains an invalid systemd service file Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: monkeyboyted(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi, I notice iio-sensor-proxy packages does not seem to work on default in opensuse tumbleweed. I believe this package is needed to enable autorotate in gnome-shell. $sudo systemctl enable iio-sensor-proxy.service The unit files have no installation config (WantedBy=, RequiredBy=, Also=, Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled using systemctl. Possible reasons for having this kind of units are: �� A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory. �� A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. �� A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). �� In case of template units, the unit is meant to be enabled with some instance name specified. $rpm -qa iio-sensor-proxy iio-sensor-proxy-3.3-1.5.x86_64 $rpm -ql iio-sensor-proxy /etc/dbus-1 /etc/dbus-1/system.d /etc/dbus-1/system.d/net.hadess.SensorProxy.conf /usr/bin/monitor-sensor /usr/lib/systemd/system/iio-sensor-proxy.service /usr/lib/udev/rules.d/80-iio-sensor-proxy.rules /usr/libexec/iio-sensor-proxy $lsb_release -a LSB Version: n/a Distributor ID: openSUSE Description: openSUSE Tumbleweed Release: 20220714 Codename: n/a $sudo systemctl cat iio-sensor-proxy.service # /usr/lib/systemd/system/iio-sensor-proxy.service [Unit] Description=IIO Sensor Proxy service [Service] Type=dbus BusName=net.hadess.SensorProxy ExecStart=/usr/libexec/iio-sensor-proxy #Uncomment this to enable debug #Environment="G_MESSAGES_DEBUG=all" # Lockdown ProtectSystem=strict ProtectControlGroups=true ProtectHome=true ProtectKernelModules=true PrivateTmp=true RestrictAddressFamilies=AF_UNIX AF_LOCAL AF_NETLINK MemoryDenyWriteExecute=true RestrictRealtime=true -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1142574] New: cryfs ppc64 build failure: __builtin_crypto_vpmsumd requires the -mpower8-vector
by bugzilla_noreply＠novell.com 05 Aug '22

05 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1142574 Bug ID: 1142574 Summary: cryfs ppc64 build failure: __builtin_crypto_vpmsumd requires the -mpower8-vector Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: normand(a)linux.vnet.ibm.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 811389 --> http://bugzilla.opensuse.org/attachment.cgi?id=811389&action=edit cryfs_standard__ppc64_201907240835.log cryfs ppc64 build failure: __builtin_crypto_vpmsumd requires the -mpower8-vector as reported in openSUSE:Factory:PowerPC (1) log saved as attachment. (1) https://build.opensuse.org/package/live_build_log/openSUSE:Factory:PowerPC/… === [ 1024s] lto1: error: builtin function '__builtin_crypto_vpmsumd' requires the '-mpower8-vector' option [ 1024s] lto1: fatal error: target specific builtin not available [ 1024s] lto-wrapper: fatal error: /usr/bin/c++ returned 1 exit status [ 1024s] /usr/lib64/gcc/powerpc64-suse-linux/9/../../../../powerpc64-suse-linux/bin/ld: error: lto-wrapper failed [ 1024s] collect2: error: ld returned 1 exit status [ 1042s] error: Bad exit status from /var/tmp/rpm-tmp.caXmGn (%build) === -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1140585] New: cryfs - 0.10.0-1.3 - Illegal instruction on AMD Phenom II X4 965 Processor
by bugzilla_noreply＠novell.com 05 Aug '22

05 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1140585 Bug ID: 1140585 Summary: cryfs - 0.10.0-1.3 - Illegal instruction on AMD Phenom II X4 965 Processor Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: palica(a)liguros.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Trying to use cryfs on an AMD PC: palica@sucellus:~> cryfs .Private/ 9_Private Illegal instruction (core dumped) palica@sucellus:~> sudo cryfs .Private/ 9_Private -o allow_other Illegal instruction palica@sucellus:~> zypper info cryfs Loading repository data... Reading installed packages... Information for package cryfs: ------------------------------ Repository : Main Repository (OSS) (20190704) Name : cryfs Version : 0.10.0-1.3 Arch : x86_64 Vendor : openSUSE Installed Size : 5.5 MiB Installed : Yes Status : up-to-date Source package : cryfs-0.10.0-1.3.src Summary : CryFS encryption Description : CryFS provides a FUSE-based mount that encrypts file contents, file sizes, metadata and directory structure. It uses encrypted same-size blocks to store both the files themselves and the blocks' relations to one another. These blocks are stored as individual files in the base directory, which can then be synchronized to remote storage (using an external tool). palica@sucellus:~> dmesg|tail [ 667.314215] BTRFS info (device dm-0): qgroup scan completed (inconsistency flag cleared) [ 891.504820] traps: cryfs[17825] trap invalid opcode ip:5596343a66df sp:7ffff48b2638 error:0 in cryfs[559634356000+20f000] [ 911.655522] traps: cryfs[18281] trap invalid opcode ip:5568d347c6df sp:7ffec8878018 error:0 in cryfs[5568d342c000+20f000] palica@sucellus:~> lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 48 bits physical, 48 bits virtual CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 1 Core(s) per socket: 4 Socket(s): 1 NUMA node(s): 1 Vendor ID: AuthenticAMD CPU family: 16 Model: 4 Model name: AMD Phenom(tm) II X4 965 Processor Stepping: 3 CPU MHz: 800.000 CPU max MHz: 3400.0000 CPU min MHz: 800.0000 BogoMIPS: 6830.70 Virtualization: AMD-V L1d cache: 64K L1i cache: 64K L2 cache: 512K L3 cache: 6144K NUMA node0 CPU(s): 0-3 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt hw_pstate vmmcall npt lbrv svm_lock nrip_save I am happy to provide any other info needed. Thanks for help. PS: was already not working with 20190606, I thought that upgrading to latest would solve the issue. IMHO missing some cpu instruction set maybe? -- You are receiving this mail because: You are on the CC list for the bug.

2 3