November 2018 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1093592] New: redshift doesn't work after geoclue2 update
by bugzilla_noreply＠novell.com 16 Dec '22

16 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1093592 Bug ID: 1093592 Summary: redshift doesn't work after geoclue2 update Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dmarcoux(a)posteo.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 770512 --> http://bugzilla.opensuse.org/attachment.cgi?id=770512&action=edit redshift error Hello, I updated to the latest snapshot (2018 05 15) and since then, redshift with geoclue2 doesn't work. After launching, it displays an error (see attachment). This wasn't happening with the previous snapshot I had, but I'm not sure which one. The issue seems to arise due to changes within the recent revisions of the geoclue2 package, so as far as 2 months ago. So by looking at the snapshots, I suspect it is in one of those: - 2018 03 04 - 2018 04 24 - 2018 05 11 - 2018 05 13 The workaround is to provide the latitude and longitude manually with the option -l. -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 1111657] New: python-cffi build fail with glibc maintenance update
by bugzilla_noreply＠novell.com 14 Dec '22

14 Dec '22

http://bugzilla.suse.com/show_bug.cgi?id=1111657 Bug ID: 1111657 Summary: python-cffi build fail with glibc maintenance update Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: mlin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- With glibc maintenance update https://build.opensuse.org/request/show/639803 , python-cffi build failed due to it can not pass unittest[1]. Both package are from SLE. [1] https://build.opensuse.org/package/live_build_log/openSUSE:Leap:15.1:Stagin… -- You are receiving this mail because: You are on the CC list for the bug.

2 31

[Bug 1089025] New: [diff] osc diff -r rev1:rev2 is not always working as expected
by bugzilla_noreply＠novell.com 07 Dec '22

07 Dec '22

http://bugzilla.suse.com/show_bug.cgi?id=1089025 Bug ID: 1089025 Summary: [diff] osc diff -r rev1:rev2 is not always working as expected Classification: Internal Novell Products Product: openSUSE Build Service Version: 2.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: osc Assignee: adrian(a)suse.com Reporter: eich(a)suse.com QA Contact: adrian(a)suse.com Found By: Development Blocker: --- 'osc diff' is not always producing output reliably: Using it on a devel project, it looks like it produces no output when the submission to factory has been 'folded back' - which is quite annoying. In science/netcdf-cxx4 on OBS a 'osc diff -r 22:20' (or osc 'diff -r 20:22') produces no output nor does it for any earlier commits. -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1024727] New: Cannot login to Bugzilla using Bugzilla "login" button
by bugzilla_noreply＠novell.com 04 Dec '22

04 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1024727 Bug ID: 1024727 Summary: Cannot login to Bugzilla using Bugzilla "login" button Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bugzilla Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: qantas94heavy(a)gmail.com QA Contact: novbugzilla-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- Created attachment 713674 --> http://bugzilla.opensuse.org/attachment.cgi?id=713674&action=edit Unprocessed PHP file I attempted to login to Bugzilla by clicking the "Login" button on the Bugzilla home page, which took me to the following URL: https://login.microfocus.com/nidp/idff/sso?id=132&sid=5&option=credential&s… Instead of receiving the page as usual, it appears to load some scripts from the following URL: https://www.suse.com/common/inc/include.php?file=headers/hdr_head.html The PHP file there appears to be unprocessed, which is most likely causing the issue here. I was only able to login by going through the openSUSE wiki then going back to Bugzilla. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1047225] New: LUKS password doesn't show up when booting with nomodeset
by bugzilla_noreply＠novell.com 30 Nov '22

30 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1047225 Bug ID: 1047225 Summary: LUKS password doesn't show up when booting with nomodeset Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: tiwai(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Install a TW system with the standard procedure for LVM+encrpption as suggested by installer on KVM. It works fine with the graphical LUKS password. But when you boot with nomodeset boot option, the boot process hangs without asking the LUKS password. This didn't happen on openSUSE Leap 42.2 / 42.3. And when I upgrade only plymouth packages on the Leap system, it starts showing the same problem. So, it's a regression in the recent plymouth package. -- You are receiving this mail because: You are on the CC list for the bug.

2 13

[Bug 1096833] New: VUL-0: matrix-synapse: event visibility rules not applied correctly
by bugzilla_noreply＠novell.com 24 Nov '22

24 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1096833 Bug ID: 1096833 Summary: VUL-0: matrix-synapse: event visibility rules not applied correctly Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: okurz(a)suse.com Reporter: astieger(a)suse.com QA Contact: security-team(a)suse.de Found By: --- Blocker: --- from https://github.com/matrix-org/synapse/releases/tag/v0.31.1 Changes in synapse v0.31.1 (2018-06-08) v0.31.1 fixes a security bug in the get_missing_events federation API where event visibility rules were not applied correctly. We are not aware of it being actively exploited but please upgrade asap. Bug Fixes: Fix event filtering in get_missing_events handler (PR #3371) https://github.com/matrix-org/synapse/commit/ad9edd1d968f19dd4d7c65102fe552… -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1029190] New: Support for package variants according to the evaluation of bigger regular expressions
by bugzilla_noreply＠novell.com 24 Nov '22

24 Nov '22

http://bugzilla.suse.com/show_bug.cgi?id=1029190 Bug ID: 1029190 Summary: Support for package variants according to the evaluation of bigger regular expressions Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: All Status: NEW Severity: Enhancement Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: Markus.Elfring(a)web.de QA Contact: qa-bugs(a)suse.de CC: astieger(a)suse.com Found By: --- Blocker: --- I noticed that the parameter “--with-link-size=2” is used so far in a package specification. https://build.opensuse.org/package/view_file/openSUSE:Factory/pcre2/pcre2.s… This setting limits the size of regular expressions. I would like to work with bigger search patterns occasionally. So I suggest to generate also variants for this software with an internal link size of 3 (and 4) for the data processing with 8 and 16 bit characters. See also: Selection of system properties for the regular expressions engine at run time https://bugs.exim.org/show_bug.cgi?id=1922 By the way: How do you think about to use the specifications “LDFLAGS“ und “%{?_smp_mflags}“ as parameters for the script “%configure“ there? -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1052740] New: convert X keyboards into kbd and set unicode console font for languages with non-Latin alphabets
by bugzilla_noreply＠novell.com 22 Nov '22

22 Nov '22

http://bugzilla.suse.com/show_bug.cgi?id=1052740 Bug ID: 1052740 Summary: convert X keyboards into kbd and set unicode console font for languages with non-Latin alphabets Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: opensuse.lietuviu.kalba(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Now openSUSE for languages with Latin alphabets use converted keyboard layouts from X into kbd, also use unicode console font (as converted layouts supports it). Remaining task is to do same transition for non-Latin console keyboard layouts and set appropriate console font. Perhaps we should preconfigure option to switch between native and US QWERTY in console for these non-Latin languages and keyboard layouts. As noted in https://bugzilla.suse.com/show_bug.cgi?id=942896#c70 , As noted in https://bugzilla.suse.com/show_bug.cgi?id=942896#c69 Greek seems not have converted console keyboard layout from X into kbd. For Greek perhaps we can use eurlatgr console font (like for Latin alphabets) All Cyrillic layouts now use UniCyr_8x16.psf font, but this font seems to be compatible with cp866, cp1251, iso8859-5 and koi8-r (according http://www.tldp.org/HOWTO/Belarusian-HOWTO/x28.html) and not compatible with unicode per se. But openSUSE seems don't provide converted layouts for Russian, Ukrainian, Serbian, Bulgarian, Tajik. For Cyrillic alphabets we should use LatArCyrHeb-14, LatArCyrHeb-16+ or LatArCyrHeb-16 console font, that support unicode. -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1082318] New: Packages must not mark license files as %doc
by bugzilla_noreply＠novell.com 21 Nov '22

21 Nov '22

http://bugzilla.suse.com/show_bug.cgi?id=1082318 Bug ID: 1082318 Summary: Packages must not mark license files as %doc Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Certain licenses require that license files must be shipped together with the binaries in all cases. By using the %doc marker, this is no longer guaranteed (e.g. by enabling excludedocs). Thus it is important that for such cases, %license is used instead of %doc. The effect is that the file is always installed, stored in a different directory (/usr/share/licenses/<pkg>/) and can be queried using rpm (e.g. "rpm -qL kernel-firmware"). -- You are receiving this mail because: You are on the CC list for the bug.

2 249

[Bug 1115455] New: rkhunter: migrate from cron to systemd timers
by bugzilla_noreply＠novell.com 20 Nov '22

20 Nov '22

http://bugzilla.suse.com/show_bug.cgi?id=1115455 Bug ID: 1115455 Summary: rkhunter: migrate from cron to systemd timers Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: kstreitova(a)suse.com QA Contact: qa-bugs(a)suse.de CC: kstreitova(a)suse.com Found By: --- Blocker: --- This bug is part of TRACKERBUG bug#1115430. Based on fate#323635 (Reduce usage of cron package in favor of systemd timers) we would like to minimize the number of packages that use cron in favour of systemd timers. It seems that your package uses cron. Please take a look at it and evaluate if it's possible to migrate your package to use systemd timers without impacting behaviour. If it's not possible, please write down the reason. Please note that by default, services are not enabled when the package is installed. You probably want your service to be enabled by default so you should create a submit request on systemd-presets-branding-openSUSE package, modifying default-openSUSE.preset file by adding "enable your_service_name.service". -- You are receiving this mail because: You are on the CC list for the bug.

2 6