September 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1175037] New: Sporadic endless loop in claws-mail/RSSyl - pango or harfbuzz related?
by bugzilla_noreply＠suse.com 09 Aug '22

09 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1175037 Bug ID: 1175037 Summary: Sporadic endless loop in claws-mail/RSSyl - pango or harfbuzz related? 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: d_werner(a)gmx.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 840462 --> http://bugzilla.opensuse.org/attachment.cgi?id=840462&action=edit gdb backtrace of claws-mail In claws-mails (3.17.6 from Tumbleweed) RSS reader RSSyl some messages cause "endless loops". The problem happens in Tumbleweed and Leap 15.2 (in Leap 15.2 observed with claws-mail 3.17.5 from GA and also with 3.17.6 from the update - repo). But it is not identical, a message which triggers the endless loop in Tumbleweed can be viewed without problem in Leap 15.2. Luckily it is only a small percentage of messages which cause this, but if it happens claws-mail needs to be killed. Viewing the same message after the restart will trigger the problem again. In backtraces taken while in this endless loop state I always observed harfbuzz or pango related entries last on the stack. So maybe the actual problem is in this area. Attached several stack traces from claws-mail looping over the same message. 38 is the related message which caused this in Tumbleweed snapshot 20200807 which can be opened in Leap 15.2 with up to date fixes. I did not observe something similar with Leap 15.1. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 1172059] New: windows:mingw:win{32,64}: packages including native and cross packages does not build with enabled debug info
by bugzilla_noreply＠suse.com 09 Aug '22

09 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1172059 Bug ID: 1172059 Summary: windows:mingw:win{32,64}: packages including native and cross packages does not build with enabled debug info Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: ralf.habacker(a)freenet.de QA Contact: bnc-team-screening(a)forge.provo.novell.com Found By: --- Blocker: --- If debug information support is enabled in the mentioned project, some packages will not be built due to a conflict when collecting debug information for native and cross-compiled packages. How to reproduce: 1. branch one of the following package into a local project mingw32-libqt4 mingw32-libqt4-static mingw32-libqt5-qtbase mingw32-libqt5-qtdeclarative mingw32-libqt5-qttools 2. enable debug info support at the created project What happens: The build fails with "error: Installed (but unpackaged) file(s) found:" /usr/lib/debug/... What is expected: The build should not fail with debug info support enabled at project or package level Adding debug information at the project level was originally proposed as a workaround for a non-stripping problem with the cross-gcc package reported at https://bugzilla.opensuse.org/show_bug.cgi?id=1116889. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1111871] New: lxqt-powermanagement: battery not found, it requires upower (perhaps as libkf5solid dependency)
by bugzilla_noreply＠novell.com 08 Aug '22

08 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1111871 Bug ID: 1111871 Summary: lxqt-powermanagement: battery not found, it requires upower (perhaps as libkf5solid dependency) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Patterns Assignee: dimstar(a)opensuse.org Reporter: danielmirkin(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Tumbleweed with LXQt installed on Sony Vaio PCG-71913L. Started LXQt, lxqt-powermanagement complains "Battery not found - LXQt could not find data about any battery - monitoring disabled". Following https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828697 , I've installed upower on Tumbleweed, and now lxqt-powermanagement is able to find battery data and to show Battery icon [SOLVED]. I suggest upower must be stated as Required to libkf5solid package (or perhaps to lxqt-powermanagement package itself). -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1176743] New: Add lxmenu-data as dependency for pcmanfm-qt
by bugzilla_noreply＠suse.com 08 Aug '22

08 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1176743 Bug ID: 1176743 Summary: Add lxmenu-data as dependency for pcmanfm-qt Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: screening-team-bugs(a)suse.de Reporter: ignacio_taranto(a)protonmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- lxmenu-data is required for displaying the "Applications" menu under the "Places" section and probably other functionality. According to the official README (https://github.com/lxqt/pcmanfm-qt#compiling-source-code) the runtime dependencies are: qtx11extras, lxmenu-data, liblxqt and libfm-qt. libfm-qt is already a dependency and I think lxmenu-data should be at least a recommended package. I don't know about liblxqt though. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1180591] New: Display backlight stuck at 100%
by bugzilla_noreply＠suse.com 08 Aug '22

08 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1180591 Bug ID: 1180591 Summary: Display backlight stuck at 100% Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: maurizio.galli(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 844855 --> http://bugzilla.opensuse.org/attachment.cgi?id=844855&action=edit system information I have just upgraded my device to Tumbleweed and now backlight brightness is stuck at 100% with no way to change it. I have tried several methods, including xbacklight and Xfce settings. Backlight control used to work fine with Kernel 5.3 shipped by Leap. I found a recent report using similar hardware that could suggest a regression in the kernel: https://discuss.getsol.us/d/6039-brightness-control-not-working-on-apple-di… I attached information about my system but please let me know what else I can provide. -- You are receiving this mail because: You are on the CC list for the bug.

1 24

[Bug 1184141] New: coturn.service: syscall restrictions are too strict
by bugzilla_noreply＠suse.com 08 Aug '22

08 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1184141 Bug ID: 1184141 Summary: coturn.service: syscall restrictions are too strict Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: xm.koutny+suse.com(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I'm running coturn-4.5.2-lp152.20.1.x86_64 from network:telephony (on Leap 15.2). I updated from 4.5.1 (Leap) which worked fine but now I'm running into troubles: 1) Started process will terminate soon with SIGSYS 2) After resolving this, it'll fail with > 0: : ERROR: main: Cannot configure any meaningful IP listener address I strace'd both issues: 1) (very early at the start of binary, fails even with other executables, most likely anything linked with pthread) > 1974 set_tid_address(0x7fefc2c04290) = 1974 > 1974 set_robust_list(0x7fefc2c042a0, 24) = 0 > 1974 rt_sigaction(SIGRTMIN, {sa_handler=0x7fefc1fc5bf0, sa_mask=[], sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7fefc1fd22d0}, NULL, 8) = 0 > 1974 rt_sigaction(SIGRT_1, {sa_handler=0x7fefc1fc5c90, sa_mask=[], sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7fefc1fd22d0}, NULL, 8) = 0 > 1974 rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0 > 1974 prlimit64(0, RLIMIT_STACK, NULL, <unfinished ...>) = ? > 1 <... epoll_pwait resumed>[{EPOLLHUP, {u32=2326093456, u64=94697765035664}}], 50, -1, NULL, 8) = 1 > 1974 +++ killed by SIGSYS +++ 2) > 2168 write(3, "0: : WARNING: cannot find privat"..., 69) = 69 > 2168 write(3, "0: : WARNING: cannot start TLS a"..., 95) = 95 > 2168 write(3, "0: : NO EXPLICIT LISTENER ADDRES"..., 53) = 53 > 2168 write(3, "0: : ===========Discovering list"..., 58) = 58 > 2168 socket(AF_NETLINK, SOCK_RAW|SOCK_CLOEXEC, NETLINK_ROUTE) = -1 EAFNOSUPPORT (Address family not supported by protocol) > 2168 write(3, "0: : ERROR: main: Cannot configu"..., 70) = 70 The following .service file modification fixes the issue for me: -SystemCallFilter=~@clock @debug @module @mount @raw-io @reboot @swap @privileged @resources @cpu-emulation @obsolete -RestrictAddressFamilies=AF_INET AF_INET6 AF_UNIX +SystemCallFilter=~@clock @debug @module @mount @raw-io @reboot @swap @privileged @cpu-emulation @obsolete +RestrictAddressFamilies=AF_INET AF_INET6 AF_UNIX AF_NETLINK Note that the first change may not be needed with systemd newer than v235 [1] (I guess I shouldn't be running coturn from network:telephony on Leap). [1] 4c3a917617 ("seccomp: include prlimit64 and ugetrlimit in @default") v235~15^2~3 -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1154126] New: hplip-systray does not work correctly with KDE Plasma 5.17
by bugzilla_noreply＠novell.com 07 Aug '22

07 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1154126 Bug ID: 1154126 Summary: hplip-systray does not work correctly with KDE Plasma 5.17 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: fkrueger(a)mailbox.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Given TW20191012 with KDE Plasma 5.17 (via KDE/Frameworks5 repo) hplip-systray (hplip-3.19.6-2.1.x86_64) is always shown, although it is configured as "Hide when inactive". As a matter of fact, changing the behaviour of the system tray icon via the HP Device Manager does not have any effect at all. On top of that, the icon is frozen. Any idea? -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 1190191] New: mariadb 10.5.12 updated 4 September 2021 blocked akonadi from starting
by bugzilla_noreply＠suse.com 07 Aug '22

07 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1190191 Bug ID: 1190191 Summary: mariadb 10.5.12 updated 4 September 2021 blocked akonadi from starting Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: openSUSE Leap 15.3 Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance Assignee: maintenance(a)opensuse.org Reporter: richard.bos(a)xs4all.nl QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- just updated mariadb from 10.5.11 to 10.5.12 this broke akonadi and so no email?? Downgrading back to mariadb-10.5.11 made it all work again. It's the mariadb from the repo-sle-update repository. mariadb 10.5.12 updated 4 September 2021. I don't have more information, as I'm back at 10.5.11. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[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