openSUSE Bugs September 2021

bugs@lists.opensuse.org

1 participants
2886 discussions

[Bug 1187477] New: Selecting LXQt thems works badly or not at all

by bugzilla_noreply＠suse.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1187477 Bug ID: 1187477 Summary: Selecting LXQt thems works badly or not at all 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: LXQt Assignee: mvetter(a)suse.com Reporter: tonysu(a)su-networking.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In the LXQt Configuration > Appearance > LXQt themes, switching between theeme does not work for most, and works badly even for those that preview only after clicking around. This reminds me of a problem that has happened often in the past when the path to the directory holding the themes is incorrect but back then there was a way to define a path to the directory holding the themes. I don't see that now so there is no way to manually correct the problem. It should also be noted that if LXQt is chosen as the only Desktop installed during installation (by first selecting Generic Desktop, then in the Installation summary click on "Software" and then adding the LXQt pattern), the generic openSUSE wallpaper displays instead of any of the LXQt themes, further suggesting a bad path. -- You are receiving this mail because: You are on the CC list for the bug.

40 minutes

[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

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.

6 hours, 36 minutes

[Bug 1111871] New: lxqt-powermanagement: battery not found, it requires upower (perhaps as libkf5solid dependency)

by bugzilla_noreply＠novell.com

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.

15 hours, 43 minutes

[Bug 1176743] New: Add lxmenu-data as dependency for pcmanfm-qt

by bugzilla_noreply＠suse.com

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.

15 hours, 45 minutes

[Bug 1083699] New: [Build 148.1] openQA test fails in reboot_icewm

by bugzilla_noreply＠novell.com

http://bugzilla.opensuse.org/show_bug.cgi?id=1083699 Bug ID: 1083699 Summary: [Build 148.1] openQA test fails in reboot_icewm Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other URL: https://openqa.opensuse.org/tests/623420/modules/reboo t_icewm/steps/7 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: LXDE Assignee: andrea(a)opensuse.org Reporter: okurz(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 762487 --> http://bugzilla.opensuse.org/attachment.cgi?id=762487&action=edit no clock widget shown in lxqt ## Observation openQA test in scenario opensuse-15.0-NET-x86_64-otherDE_lxqt@64bit in https://openqa.opensuse.org/tests/623420/modules/reboot_icewm/steps/7 shows no clock widget. The attached screenshot shows that the widget is activated and shows up as "Unknown". ~/.xsession-errors does not show any relevant information. ## Reproducible Fails reproducibly every build. ## Expected result Last good: [openSUSE Leap 42.3 GM](https://openqa.opensuse.org/tests/451668#step/reboot_icewm/7) showing the clock widget in the bottom right corner. ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?flavor=NET&distri=opensuse… -- You are receiving this mail because: You are on the CC list for the bug.

15 hours, 49 minutes

[Bug 1180591] New: Display backlight stuck at 100%

by bugzilla_noreply＠suse.com

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 day, 1 hour

[Bug 1184141] New: coturn.service: syscall restrictions are too strict

by bugzilla_noreply＠suse.com

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 day, 5 hours

[Bug 1154126] New: hplip-systray does not work correctly with KDE Plasma 5.17

by bugzilla_noreply＠novell.com

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.

1 day, 17 hours

[Bug 1190191] New: mariadb 10.5.12 updated 4 September 2021 blocked akonadi from starting

by bugzilla_noreply＠suse.com

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.

2 days, 6 hours

[Bug 1142574] New: cryfs ppc64 build failure: __builtin_crypto_vpmsumd requires the -mpower8-vector

by bugzilla_noreply＠novell.com

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.

3 days, 15 hours

Jump to page:

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Bugs September 2021