May 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1133423] New: AutoYaST: repository priority not working in add-on section
by bugzilla_noreply＠novell.com 04 Jan '23

04 Jan '23

http://bugzilla.suse.com/show_bug.cgi?id=1133423 Bug ID: 1133423 Summary: AutoYaST: repository priority not working in add-on section Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: apoulat(a)vitechnology.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 803606 --> http://bugzilla.suse.com/attachment.cgi?id=803606&action=edit add-on.xml Hi, I've just seen that, for example with attached add-on.xml given to AutoYaST, with, as you can see one repository with priority 20 and another with priority 10, they both, after install, have a (default) 99 priority (checked with "zypper -lr -p" command). See documentation about that here: https://doc.opensuse.org/projects/autoyast/#idm139966593990112 Note: I'm not sure on how <product> and <product_dir> tags are relevant then I tried without them and there is still the same issue. Thanks -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1029961] New: [META] Finalize /bin -> /usr/bin merge
by bugzilla_noreply＠novell.com 03 Jan '23

03 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1029961 Bug ID: 1029961 Summary: [META] Finalize /bin -> /usr/bin merge 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: daniel.molkentin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Some packages still install files to /bin that are not symlinks. A "find /bin -type f -exec rpm -qf {} \; | sort -u" on a recent TW yields: bash-4.4-95.1.x86_64 dbus-1-1.10.16-1.1.x86_64 keyutils-1.5.9-5.33.x86_64 ksh-93v-6.15.x86_64 net-tools-deprecated-1.60-770.1.x86_64 procps-3.3.12-3.1.x86_64 psmisc-22.21-6.9.x86_64 rpm-4.13.0.1-1.1.x86_64 sash-3.8-2.8.x86_64 sysvinit-tools-2.88+-103.1.x86_64 tar-1.29-3.1.x86_64 tcsh-6.20.00-3.1.x86_64 util-linux-2.29.1-1.1.x86_64 vim-8.0.324-2.1.x86_64 These packages should all install their binaries to %_bindir, i.e. /usr/bin, and have a symlink in /bin. This would finalize the /bin deprecation. I am opening bugs for each of the packages. Once they are all closed, I'll close this one. -- You are receiving this mail because: You are on the CC list for the bug.

2 67

[Bug 1106751] New: iptables does not work with kernel-default-base
by bugzilla_noreply＠novell.com 23 Dec '22

23 Dec '22

http://bugzilla.suse.com/show_bug.cgi?id=1106751 Bug ID: 1106751 Summary: iptables does not work with kernel-default-base Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Initially reported as https://github.com/kubic-project/automation/pull/474#issuecomment-417329301 Docker (and cri-o) do not work in Kubic VM images as iptables does not work: g47:~ # iptables -L iptables: No chain/target/match by that name. -- You are receiving this mail because: You are on the CC list for the bug.

2 49

[Bug 944832] New: installing updates during shutdown causes reboot
by bugzilla_noreply＠novell.com 22 Dec '22

22 Dec '22

http://bugzilla.suse.com/show_bug.cgi?id=944832 Bug ID: 944832 Summary: installing updates during shutdown causes reboot Classification: openSUSE Product: openSUSE Distribution Version: 42.1 Milestone 2 Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: ohering(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- fresh leap milestone 2. I switched from the iso install source to the online oss repo. This repo had a few differend packages compared to the iso. The gnome software installer recognized them as updates. Once I had to shutdown the system it offered a knob to install pending updates, then shutdown. I enabled that box, and hit return. I think nothing was downloaded, but the box did a reboot instead of the expected shutdown. If that feature is not ready yet I suggest to hide it for the time being to really and always do a reliable powerdown if that was requested. -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[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 1136584] New: osc build requires running in a checked out directory even with --alternative-project
by bugzilla_noreply＠novell.com 07 Dec '22

07 Dec '22

http://bugzilla.suse.com/show_bug.cgi?id=1136584 Bug ID: 1136584 Summary: osc build requires running in a checked out directory even with --alternative-project Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: mkubecek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since upgrading my Leap 15.0 system to Leap 15.1, "osc build" requires current directory to be a checked out working copy even when "--alternative-project" argument is used: > mike@unicorn:~/work/git/sle-ksource/kernel-source> osc build --alternative-project openSUSE:Factory kernel-default.spec > Error: "/srv/git/sle-ksource/kernel-source" is not an osc package working copy. Leap 15.0 and 42.3 version did not require this and the example used to work with only package contents in current directory (and no .osc/* metadata). Last known good version: 0.162.1-lp150.1.3 (Leap 15.0) First known bad version: 0.165.0-lp151.1.1 (Leap 15.1) According to Jiří Slabý, 0.164.2 also works. -- You are receiving this mail because: You are on the CC list for the bug.

2 21

[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 1125418] New: GCC 9: xtrabackup build fails
by bugzilla_noreply＠novell.com 20 Nov '22

20 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1125418 Bug ID: 1125418 Summary: GCC 9: xtrabackup build fails 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: martin.liska(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Fails here: https://build.opensuse.org/build/openSUSE:Factory:Staging:Gcc7/standard/x86… with: [ 471s] inlined from 'virtual String* Item_func_format::val_str_ascii(String*)' at /home/abuild/rpmbuild/BUILD/percona-xtrabackup-2.4.12/sql/item_strfunc.cc:3214:13: [ 471s] /usr/include/bits/string_fortified.h:34:33: warning: 'void* __builtin_memcpy(void*, const void*, long unsigned int)' writing 1 or more bytes into a region of size 0 overflows the destination [-Wstringop-overflow=] [ 471s] 34 | return __builtin___memcpy_chk (__dest, __src, __len, __bos0 (__dest)); [ 471s] | ~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [ 471s] [ 80%] Building CXX object sql/CMakeFiles/sql.dir/item_sum.cc.o -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[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

[Bug 1115430] New: [TRACKERBUG-OPENSUSE] FATE#323635: Reduce usage of cron in favour of systemd timers
by bugzilla_noreply＠novell.com 20 Nov '22

20 Nov '22

http://bugzilla.suse.com/show_bug.cgi?id=1115430 Bug ID: 1115430 Summary: [TRACKERBUG-OPENSUSE] FATE#323635: Reduce usage of cron in favour of 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: kstreitova(a)suse.com Reporter: kstreitova(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is a tracker bug for fate#323635 (Reduce usage of cron package in favor of systemd timers). It tracks openSUSE packages only (for SLE packages see bug#1115399). The goal is to minimize the number of openSUSE:Factory packages that use cron in favour of systemd timers. See dependent bugs for more information about particular packages that should be migrated. -- You are receiving this mail because: You are on the CC list for the bug.

2 19

[Bug 1103805] New: No access to mysql/mariadb databases using jdbc driver
by bugzilla_noreply＠novell.com 17 Nov '22

17 Nov '22

http://bugzilla.suse.com/show_bug.cgi?id=1103805 Bug ID: 1103805 Summary: No access to mysql/mariadb databases using jdbc driver Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Linux Status: NEW Severity: Minor Priority: P5 - None Component: LibreOffice Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: r.cabane(a)free.fr QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Please look a this bug I filed : https://bugs.documentfoundation.org/show_bug.cgi?id=119091 The mysql-connector-java (version 5.1.43) as supplied by the OpenSUSE 15.0 distribution is either flawed or incompatible with Libreoffice 6. I solved the case installing the Mariadb connector from the Mariadb website. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 987114] New: Bluetooth headset connected but not showing under 'Sound Settings'
by bugzilla_noreply＠novell.com 16 Nov '22

16 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=987114 Bug ID: 987114 Summary: Bluetooth headset connected but not showing under 'Sound Settings' Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: damien.lloyd21(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:47.0) Gecko/20100101 Firefox/47.0 Build Identifier: On openSUSE Tumbleweed, my bluetooth headset pairs and connects successfully through GNOME's bluetooth interface, but after going to the 'Sound Settings' my bluetooth headset doesn't show up, even though it is paired up. Because I can't see my bluetooth headset under 'Sound Settings' it's not possible to re-route sound through it, which means I can't use my bluetooth headset. Reproducible: Always Steps to Reproduce: 1. Make bluetooth headset discoverable; 2. Open up GNOME's bluetooth interface and select bluetooth headset; 3. Connect to bluetooth headset; 4. Once paired, access 'Sound Settings': bluetooth headset doesn't show up. Actual Results: The bluetooth headset doesn't show up under 'Sound Settings' even though it is connected and paired. Expected Results: The bluetooth headset should appear under 'Sound Settings' so that sound can be re-routed through it. My headset is a UE MEGABOOM and it worked under Ubuntu 14.04/16.04 extremely well. It doesn't work under openSUSE Tumbleweed. -- You are receiving this mail because: You are on the CC list for the bug.

2 13

[Bug 1110245] New: Connection to online repositories should be HTTPS
by bugzilla_noreply＠novell.com 15 Nov '22

15 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1110245 Bug ID: 1110245 Summary: Connection to online repositories should be HTTPS Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: All OS: All Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: digitalmon(a)rambler.ru QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Although the online repository servers support HTTPS connection, downloading of packets still occurs via the HTTP protocol. This compromises the security of users. If their connection to the Internet is intercepted, if they work through any proxy server, the attackers can modify the packages on the fly during the download. To install malware and spyware into target system. At the moment, you can only manually change the URLs of the repositories to https so that the packets are downloaded over a secure channel. I want that by default in the operating system the connection to the online-repositories, the downloading of packets, should be with HTTPS connection. This will make users' safety a step higher. I'm sure there will be less glitches, bugs in user systems. But Https is not a panacea. She is also vulnerable to the attack of MITM. The private surveilance service known to me, generates its own RSA-keys to encrypt the HTTPS, brute-force for them a digital signature so that the browser of user does not suspect forgery. The attacker's computer connects to the remote server by https, downloads packages, replaces executable files, infects them with a virus, and the user gives https traffic with his encryption key and a digital signature. But such an attack is not for everyone. To make it more difficult, you need to use long encryption keys and digital signatures on the repository servers. RSA4096 at least. I know that even LTE-connection to the Internet can be intercepted with using of special technical means and OpenLTE, so I do not trust to LTE. LTE-connection can work without encryption, and 3G connection seems to be always encrypted. A wired connection to the Internet, to intercept - generally easy. As PPPoe, as DHCP (DHCP is without authorization and verification of provider access point). The 3G modem with a good antenna has the same speed as the LTE. -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1129466] New: fwupd cannot update BIOS with UEFI Secure Boot enabled because of missing fwupdx64.efi.signed
by bugzilla_noreply＠novell.com 10 Nov '22

10 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1129466 Bug ID: 1129466 Summary: fwupd cannot update BIOS with UEFI Secure Boot enabled because of missing fwupdx64.efi.signed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: pujos.michael(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- fwdupd 1.2.3-2.1 cannot update the BIOS on my laptop because of this error: $fwupdmgr get-devices ... 20MBCTO1WW System Firmware DeviceId: 65b6a9dc7b7df18bdff003584b51bf21373e3aa6 Guid: 1e1fe415-74e8-49e1-9508-106b3d13d50d Guid: 230c8b18-8d9b-53ec-838b-6cfc0383493a Guid: 171800c9-1a51-5fd9-a32b-7b3999cb1c4e Plugin: uefi Flags: internal|require-ac|supported|registered|needs-reboot Version: 0.1.18 VersionLowest: 0.1.0 Icon: computer Created: 2019-03-15 UpdateError: /usr/lib/fwupd/efi/fwupdx64.efi.signed cannot be found Apparently, if Secure Boot is enabled (my case and I believe TW default on UEFI installs), it looks for /usr/lib/fwupd/efi/fwupdx64.efi.signed. This file is missing but it turns out that /usr/lib/fwupd/efi/fwupdx64.efi is present AND signed: $pesign -S -i /usr/lib/fwupd/efi/fwupdx64.efi --------------------------------------------- certificate address is 0x7f0e55679f78 Content was not encrypted. Content is detached; signature cannot be verified. The signer's common name is openSUSE Secure Boot Signkey The signer's email address is build(a)opensuse.org Signing time: Tue Mar 05, 2019 There were certs or crls included. --------------------------------------------- So the fix is simply so make a symlink and restart fwupd so it sees the change: $ln -s /usr/lib/fwupd/fwupdx64.efi /usr/lib/fwupd/fwupdx64.efi.signed $systemctl restart fwupd Then the error goes away in 'fwupdmgr get-devices' and you can supposedly update with 'fwupdmgr update' (didn't try it at updating the BIOS is rather scary and I do not absolutely need this update currently). So I think the package should be updated to make the symlink (or rename the file if keeping fwupdx64.efi is unecessary). -- You are receiving this mail because: You are on the CC list for the bug.

2 19

[Bug 1098360] New: aide --init gives the error DBG: md_enable: algorithm 7 not available
by bugzilla_noreply＠novell.com 09 Nov '22

09 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1098360 Bug ID: 1098360 Summary: aide --init gives the error DBG: md_enable: algorithm 7 not available Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: 64bit OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: chevy.stroker(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- virt:~ # aide --init DBG: md_enable: algorithm 7 not available gcry_md_enable 7 failedAIDE initialized database at /var/lib/aide/aide.db.new Number of entries: 218651virt:~ # -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1028824] New: aide looking for a removed algorithm
by bugzilla_noreply＠novell.com 09 Nov '22

09 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1028824 Bug ID: 1028824 Summary: aide looking for a removed algorithm Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Upgrade Problems Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: tschaefer(a)t-online.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- After starting: aide -i comes the following notice: DBG: md_enable: algorithm 7 not available -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1094780] New: Laptop with Intel+Nvidia hybrid graphics won't suspend after hibernation
by bugzilla_noreply＠novell.com 09 Nov '22

09 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1094780 Bug ID: 1094780 Summary: Laptop with Intel+Nvidia hybrid graphics won't suspend after hibernation Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: srid(a)rkmail.ru QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 771476 --> http://bugzilla.opensuse.org/attachment.cgi?id=771476&action=edit Log of kernel-vanilla + drm.debug=0x0e A laptop with hybrid graphics won't suspend after it was hibernated and restored. It may not happen on the fist time, but the main idea is that laptop stops suspending to ram at some point if it was hibernated at least one time. Also, it won't shut down gracefully, there are some error messages about nouveau errors and stalled CPU cores. I'm using kernel-vanilla, as kernel-default still has bug 1094751, but if you apply fix proposed in that report, kernel-default behaves identically to kernel-vanilla. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1087375] New: openSUSE:Tools/osc: Bug -- Package internal error
by bugzilla_noreply＠novell.com 05 Nov '22

05 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1087375 Bug ID: 1087375 Summary: openSUSE:Tools/osc: Bug -- Package internal error Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: ro(a)suse.com Reporter: luc14n0(a)linuxmail.org QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- Created attachment 765332 --> http://bugzilla.opensuse.org/attachment.cgi?id=765332&action=edit The working directory compressed in a *.tar.xz file. After running checking in with `osc` I got this error: server does not accept filelist: <directory><entry hash="sha256:db932ad3676e6610047c61561b773da361df1b8e3f412aecc6cc0b7e7aa0428a" md5="5ef267ff27c590ec5d8975a8ee489767" name="baselibs.conf" /><entry hash="sha256:b98a9ea2ed5ea0a62d908182974e8a049fe7a890aad525b44a28bb5e44ca0d4c" md5="6b8f9f2beff3954b29085e7060b2f1e1" name="glibmm-2.57.1.tar.xz" /><entry hash="sha256:d97ebf807e146fcf3a6ae223fb495b0878d7f578a1edde2f3ddb04712993251b" md5="60130102823c2c4007295ce1b9e00fb5" name="glibmm2.changes" /><entry hash="sha256:11665c9da3c95c2ae9b2bb5d804ba9775387ef9d9c48f1a66b8f8b060b05ee07" md5="6a6c21ed626b67736b313ee88d02c455" name="glibmm2.spec" /></directory> missing: <directory error="missing" name="glibmm2"> <entry hash="sha256:d97ebf807e146fcf3a6ae223fb495b0878d7f578a1edde2f3ddb04712993251b" md5="60130102823c2c4007295ce1b9e00fb5" name="glibmm2.changes" /> </directory> Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/osc/babysitter.py", line 61, in run return prg.main(argv) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 344, in main return self.cmd(args) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 367, in cmd retval = self.onecmd(argv) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 501, in onecmd return self._dispatch_cmd(handler, argv) File "/usr/lib/python2.7/site-packages/osc/cmdln.py", line 1232, in _dispatch_cmd return handler(argv[0], opts, *args) File "/usr/lib/python2.7/site-packages/osc/commandline.py", line 4612, in do_commit self._commit(subcmd, opts, args) File "/usr/lib/python2.7/site-packages/osc/commandline.py", line 4715, in _commit prj.commit(packages, msg=msg, files=prj_files, skip_local_service_run=skip_local_service_run, verbose=opts.verbose, can_branch=can_branch, force=opts.force) File "/usr/lib/python2.7/site-packages/osc/core.py", line 989, in commit self.commitExtPackage(pac, msg, todo, verbose=verbose, skip_local_service_run=skip_local_service_run) File "/usr/lib/python2.7/site-packages/osc/core.py", line 1079, in commitExtPackage p.commit(msg=msg, verbose=verbose, skip_local_service_run=skip_local_service_run) File "/usr/lib/python2.7/site-packages/osc/core.py", line 1540, in commit % (ET.tostring(filelist, encoding=ET_ENCODING), ET.tostring(sfilelist, encoding=ET_ENCODING))) PackageInternalError It's the second time I got this error in this last week. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1031134] New: Since upgrade to GNOME 3.24 [TW 20170322] gnome-shell crashes and reloads often
by bugzilla_noreply＠novell.com 05 Nov '22

05 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1031134 Bug ID: 1031134 Summary: Since upgrade to GNOME 3.24 [TW 20170322] gnome-shell crashes and reloads often Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: badshah400(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since the upgrade to TW 201703022 which brought GNOME 3.24 (actually I also saw this while using the beta GNOME 3.23.9x version from GNOME:Next repository), gnome-shell seems to crash and reload every now and then (no specific process to trigger this specifically that I could find). This is nothing more than an annoyance, since the reload works just fine, so the only effect is that the application windows get rordered thereafter. I see messages like these on the journal: Mar 27 16:06:52 tp-yoga260 gnome-shell[17371]: JS WARNING: [resource:///org/gnome/shell/ui/main.js 317]: reference to undefined property global.stage Mar 27 16:06:52 tp-yoga260 gnome-shell[17371]: JS WARNING: [resource:///org/gnome/shell/ui/layout.js 217]: reference to undefined property global.window_group Mar 27 16:06:52 tp-yoga260 gnome-shell[17371]: JS WARNING: [resource:///org/gnome/shell/ui/layout.js 899]: reference to undefined property this.monitors[this.findIndexForAct Mar 27 16:06:52 tp-yoga260 gnome-shell[17371]: JS WARNING: [resource:///org/gnome/shell/ui/osdMonitorLabeler.js 59]: reference to undefined property Meta.MonitorManager Mar 27 16:06:52 tp-yoga260 gnome-shell[17371]: JS WARNING: [resource:///org/gnome/shell/ui/panel.js 1107]: reference to undefined property indicator.menu._openChangedId Mar 27 16:06:52 tp-yoga260 org.gnome.Shell.desktop[17371]: current session already has an ibus-daemon. Mar 27 16:06:52 tp-yoga260 gnome-shell[17371]: JS WARNING: [resource:///org/gnome/shell/ui/slider.js 34]: reference to undefined property St.GenericAccessible Mar 27 16:06:52 tp-yoga260 polkitd[1043]: Registered Authentication Agent for unix-session:2 (system bus name :1.335 [/usr/bin/gnome-shell], object path /org/freedesktop/Pol Mar 27 16:06:52 tp-yoga260 gnome-shell[17371]: JS WARNING: [resource:///org/gnome/gjs/modules/tweener/tweener.js 538]: reference to undefined property properties[istr].array Mar 27 16:06:52 tp-yoga260 gnome-shell[17371]: JS WARNING: [resource:///org/gnome/shell/ui/search.js 432]: reference to undefined property provider.isRemoteProvider Mar 27 16:06:52 tp-yoga260 gnome-shell[17371]: Failed to add search provider /usr/share/gnome-shell/search-providers/org.gnome.bijiben-search-provider.ini: TypeError: appInf Mar 27 16:06:52 tp-yoga260 dbus[988]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' Mar 27 16:06:52 tp-yoga260 systemd[1]: Starting PackageKit Daemon... Mar 27 16:06:52 tp-yoga260 PackageKit[17397]: daemon start Mar 27 16:06:52 tp-yoga260 dbus[988]: [system] Successfully activated service 'org.freedesktop.PackageKit' Mar 27 16:06:52 tp-yoga260 systemd[1]: Started PackageKit Daemon. Mar 27 16:06:53 tp-yoga260 /usr/lib/gdm/gdm-x-session[2581]: (II) modeset(0): EDID vendor "CMN", prod id 4665 Mar 27 16:06:53 tp-yoga260 /usr/lib/gdm/gdm-x-session[2581]: (II) modeset(0): Printing DDC gathered Modelines: Mar 27 16:06:53 tp-yoga260 /usr/lib/gdm/gdm-x-session[2581]: (II) modeset(0): Modeline "1920x1080"x0.0 138.78 1920 1966 1996 2080 1080 1082 1086 1112 +hsync -vsync (66.7 Mar 27 16:06:53 tp-yoga260 gnome-shell[17371]: JS WARNING: [resource:///org/gnome/shell/misc/ibusManager.js 200]: reference to undefined property this._engines[id] Mar 27 16:06:53 tp-yoga260 gnome-shell[17371]: JS WARNING: [resource:///org/gnome/shell/ui/messageList.js 353]: reference to undefined property this._useBodyMarkup Mar 27 16:06:53 tp-yoga260 gnome-shell[17371]: JS WARNING: [resource:///org/gnome/shell/ui/messageList.js 386]: reference to undefined property this._useBodyMarkup Mar 27 16:06:53 tp-yoga260 gnome-shell[17371]: JS WARNING: [resource:///org/gnome/shell/ui/messageList.js 169]: reference to undefined property this._container Mar 27 16:06:53 tp-yoga260 gnome-shell[17371]: nma_mobile_providers_database_lookup_cdma_sid: assertion 'sid > 0' failed Mar 27 16:06:53 tp-yoga260 gnome-shell[17371]: JS WARNING: [resource:///org/gnome/shell/ui/status/network.js 1885]: reference to undefined property this._mainConnectionState Mar 27 16:06:54 tp-yoga260 gnome-shell[17371]: GNOME Shell started at Mon Mar 27 2017 16:06:52 GMT+0200 (CEST) Mar 27 16:07:06 tp-yoga260 gnome-terminal-[17266]: Allocating size to GtkScrollbar 0xb06500 without calling gtk_widget_get_preferred_width/height(). How does the code know t Mar 27 16:07:09 tp-yoga260 kernel: SFW2-INext-DROP-DEFLT IN=wlp4s0 OUT= MAC=33:33:00:00:00:fb:a8:81:95:7d:ba:78:86:dd SRC=fe80:0000:0000:0000:aa81:95ff:fe7d:ba78 DST=ff02:00 Mar 27 16:07:13 tp-yoga260 gnome-shell[17371]: JS WARNING: [resource:///org/gnome/shell/ui/dash.js 760]: reference to undefined property oldApps[oldIndex] Mar 27 16:07:13 tp-yoga260 PackageKit[17397]: daemon quit Mar 27 16:07:13 tp-yoga260 packagekitd[17397]: Source ID 10 was not found when attempting to remove it Mar 27 16:07:13 tp-yoga260 gnome-shell[17371]: JS WARNING: [resource:///org/gnome/shell/ui/appDisplay.js 1298]: reference to undefined property this.name Mar 27 16:07:20 tp-yoga260 sudo[17463]: badshah400 : TTY=pts/1 ; PWD=/home/badshah400 ; USER=root ; COMMAND=/usr/bin/journalctl -b log Mar 27 16:07:20 tp-yoga260 sudo[17463]: pam_unix(sudo:session): session opened for user root by (uid=0) Mar 27 16:07:20 tp-yoga260 sudo[17463]: pam_systemd(sudo:session): Cannot create session: Already occupied by a session Mar 27 16:07:20 tp-yoga260 sudo[17463]: pam_unix(sudo:session): session closed for user root Mar 27 16:07:24 tp-yoga260 sudo[17469]: badshah400 : TTY=pts/1 ; PWD=/home/badshah400 ; USER=root ; COMMAND=/usr/bin/journalctl -b Mar 27 16:07:24 tp-yoga260 sudo[17469]: pam_unix(sudo:session): session opened for user root by (uid=0) Mar 27 16:07:24 tp-yoga260 sudo[17469]: pam_systemd(sudo:session): Cannot create session: Already occupied by a session -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 1051356] New: Epiphany and therefore gnome-shell's portal checking fail with TLS handshake failure
by bugzilla_noreply＠novell.com 05 Nov '22

05 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1051356 Bug ID: 1051356 Summary: Epiphany and therefore gnome-shell's portal checking fail with TLS handshake failure Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: badshah400(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- While connecting to a portal network, epiphany fails with the following error The precise error was: Error performing TLS handshake: Could not negotiate a supported cipher suite. Because epiphany fails, so does gnome-shell's portal checking window, which launches immediately upon detecting a portal network but promptly shows the same message with no way to load the portal login page. Firefox, on the other hand, goes ahead and loads the portal login page on the same network. -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1105268] New: Wayland: Screen rotation to left or right gives blank screen from second attempt onward
by bugzilla_noreply＠novell.com 05 Nov '22

05 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1105268 Bug ID: 1105268 Summary: Wayland: Screen rotation to left or right gives blank screen from second attempt onward Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs(a)forge.provo.novell.com Reporter: badshah400(a)gmail.com QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- GNOME 3.28.2 on Wayland Rotating the screen to the left or right from its default orientation works the first time, but gives a blank screen thereafter, with the following log recorded on the journal: Aug 18 03:08:41 kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=140995 end=140996) time 1818 us, min 1907, max 1919, scanline start 1870, end 89 Aug 18 03:08:42 gsd-color[4609]: failed to set screen _ICC_PROFILE: Failed to open file “/home/badshah/.local/share/icc/edid-400eada130818d341c3ea2fa3de67f03.icc”: Permission denied Aug 18 03:08:42 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space left on device Aug 18 03:08:42 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space left on device Aug 18 03:08:42 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space left on device Aug 18 03:08:42 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space left on device Aug 18 03:08:42 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space left on device Aug 18 03:08:42 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space left on device Aug 18 03:08:42 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space left on device Aug 18 03:08:42 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space left on device Aug 18 03:08:42 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space left on device Aug 18 03:08:42 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space left on device Aug 18 03:08:42 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space left on device Aug 18 03:08:42 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space left on device Aug 18 03:08:43 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space left on device Aug 18 03:08:43 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space left on device Aug 18 03:08:43 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space left on device Aug 18 03:08:43 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space left on device Aug 18 03:08:43 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space left on device Aug 18 03:08:44 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space left on device Aug 18 03:08:44 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space left on device Aug 18 03:08:44 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space left on device Aug 18 03:08:44 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space left on device Aug 18 03:08:44 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space left on device Aug 18 03:08:44 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space left on device Aug 18 03:08:45 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space left on device Aug 18 03:08:45 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space left on device Aug 18 03:08:45 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space left on device Aug 18 03:08:45 gnome-shell[7467]: Failed to set CRTC mode 2880x1920: No space left on device Aug 18 03:08:45 gnome-shell[4401]: Failed to read EDID from 'eDP-1': No such file or directory Aug 18 03:08:45 gnome-shell[4401]: Failed to read EDID from 'eDP-1': No such file or directory Aug 18 03:08:45 gnome-shell[4401]: Failed to read EDID from 'eDP-1': No such file or directory Aug 18 03:08:45 gsd-color[4609]: failed to set screen _ICC_PROFILE: Failed to open file “/home/badshah/.local/share/icc/edid-400eada130818d341c3ea2fa3de67f03.icc”: Permission denied -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1132785] New: Mutt is installed by default for some reason despite evolution also being there
by bugzilla_noreply＠novell.com 05 Nov '22

05 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1132785 Bug ID: 1132785 Summary: Mutt is installed by default for some reason despite evolution also being there Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: badshah400(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Don't need to have two mail clients installed by default, do we? Considering evolution has been GNOME's go-to mail client on openSUSE for ages, please drop mutt from default GNOME packages. It comes from the enhanced base pattern, and makes sense if someone installs a console-only system or desktop system without a default mail client, but we don't need it for GNOME. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1134129] New: [Public Beta program] Broken word wrapping for package description
by bugzilla_noreply＠novell.com 05 Nov '22

05 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1134129 Bug ID: 1134129 Summary: [Public Beta program] Broken word wrapping for package description Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: BuildService Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: badshah400(a)gmail.com QA Contact: adrian(a)suse.com Found By: --- Blocker: --- Created attachment 804184 --> http://bugzilla.opensuse.org/attachment.cgi?id=804184&action=edit obs://science/Herwig package description While using the public beta program interface for OBS, word wrapping is broken when displaying package metainfo, specifically the description: line breaks occur within single words rather than in between two words making the info difficult to read. See, e.g. https://build.opensuse.org/package/show/science/Herwig (screenshot of pkg description metainfo attached) Browser used: Firefox (v 66.0.3) openSUSE Tumbleweed -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1116034] New: Please convert SysV init scripts by safte-monitor into native systemd services
by bugzilla_noreply＠novell.com 03 Nov '22

03 Nov '22

http://bugzilla.suse.com/show_bug.cgi?id=1116034 Bug ID: 1116034 Summary: Please convert SysV init scripts by safte-monitor into native systemd services 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: fbui(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- It would be great if the SysV init scrips shipped by this package could be converted into systemd native services. Indeed most packages shipped by openSUSE Factory switched to native systemd unit files years ago and we plan to drop the obsolete/limited SysV compat support in the future. If this appears to be a big task, one quick way to solve it is to copy and ship (as is) the .service unit wrappers generated automatically by systemd-sysv-generator at boot. Indeed such wrappers are generated by systemd in order to support SysV init scripts similarly to native units. You can see the content of a wrapper unit with: $ systemctl cat <sysvinit-script>.service As you could see the wrapper unit simply calls the SysV script, which should be moved out of /etc/init.d, probably in a directory owned by your package. In all cases we would be glad to provide any help if needed in this task. Thanks in advance. -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1095671] New: sg3_utils: sg_turs command in Leap broken
by bugzilla_noreply＠novell.com 02 Nov '22

02 Nov '22

http://bugzilla.suse.com/show_bug.cgi?id=1095671 Bug ID: 1095671 Summary: sg3_utils: sg_turs command in Leap broken Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dmarkh(a)cfl.rr.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have this little script that shows my problem. #!/bin/bash sg_turs /dev/sr0 > /dev/null RDY=$? echo "RDY = ${RDY}" This script always says the sg_turs commands exit status is 0. Even with the door open and no disk installed. The man page for the sg_turs command says: EXIT STATUS The exit status of sg_turs is 0 when it is successful (e.g. in the case of a mechanical disk, it is spun up and ready to accept commands). For this utility the other exit status of interest is 2 corresponding to the "not ready" sense key. For other exit status values see the sg3_utils(8) man page. -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1056408] New: dm-mpath path remove/add events are received out of order
by bugzilla_noreply＠novell.com 02 Nov '22

02 Nov '22

http://bugzilla.suse.com/show_bug.cgi?id=1056408 Bug ID: 1056408 Summary: dm-mpath path remove/add events are received out of order Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: martin.wilck(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 738867 --> http://bugzilla.suse.com/attachment.cgi?id=738867&action=edit Full journalctl output of the test run I'm not sure if this is really a bug. Currently just documenting it here for further reference. The following is an excerpt of udev monitor output captured while removing and re-adding paths to a multipath map. All paths are removed using the "delete" attribute of the SCSI devices in sysfs until no paths are left, and re-added using "scan" on the scsi host later. It would be expected that NR_VALID_PATHS decreases monotonically to 0 while this happens, and increases again to the full path count (6). The logs show that this is not the case: > [390917.224026] bremer udevadm[27187]: KERNEL - the kernel uevent > [390917.228859] bremer udevadm[27187]: KERNEL[390917.228488] change /devices/virtual/block/dm-1 (block) > [390917.228859] bremer udevadm[27187]: SEQNUM=42117 > [390918.526074] bremer udevadm[27187]: KERNEL[390918.526012] change /devices/virtual/block/dm-1 (block) > [390918.526074] bremer udevadm[27187]: SEQNUM=42118 > [390918.659679] bremer udevadm[27187]: KERNEL[390918.659656] add /devices/virtual/block/dm-20 (block) > [390918.659679] bremer udevadm[27187]: SEQNUM=42120 > [390918.694564] bremer udevadm[27187]: KERNEL[390918.692580] change /devices/virtual/block/dm-20 (block) > [390918.694564] bremer udevadm[27187]: SEQNUM=42121 > [390918.738590] bremer udevadm[27187]: KERNEL[390918.737979] change /devices/virtual/block/dm-1 (block) > [390918.738590] bremer udevadm[27187]: SEQNUM=42122 > [390918.786888] bremer udevadm[27187]: KERNEL[390918.786432] change /devices/virtual/block/dm-20 (block) > [390918.786888] bremer udevadm[27187]: SEQNUM=42123 > [390921.254530] bremer udevadm[27187]: KERNEL[390921.254492] remove /devices/pci0000:00/0000:00:01.0/0000:07:00.4/host7/session1/target7:0:0/7:0:0:1/block/sdd (block) > [390921.254530] bremer udevadm[27187]: SEQNUM=42129 > [390921.283316] bremer udevadm[27187]: KERNEL[390921.279872] change /devices/virtual/block/dm-1 (block) > [390921.283316] bremer udevadm[27187]: SEQNUM=42131 > [390921.418111] bremer udevadm[27187]: KERNEL[390921.417388] remove /devices/pci0000:00/0000:00:01.0/0000:07:00.4/host7/session2/target7:0:1/7:0:1:1/block/sdf (block) > [390921.418111] bremer udevadm[27187]: SEQNUM=42137 > [390921.456920] bremer udevadm[27187]: KERNEL[390921.456897] remove /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-2/target9:0:2/9:0:2:1/block/sdj (block) > [390921.456920] bremer udevadm[27187]: SEQNUM=42144 > [390921.521188] bremer udevadm[27187]: KERNEL[390921.521081] remove /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-5/target9:0:5/9:0:5:1/block/sdn (block) > [390921.521188] bremer udevadm[27187]: SEQNUM=42151 > [390921.563882] bremer udevadm[27187]: KERNEL[390921.563442] remove /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-6/target9:0:6/9:0:6:1/block/sdp (block) > [390921.563882] bremer udevadm[27187]: SEQNUM=42158 > [390921.598413] bremer udevadm[27187]: KERNEL[390921.598384] remove /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-7/target9:0:7/9:0:7:1/block/sdr (block) > [390921.598413] bremer udevadm[27187]: SEQNUM=42165 > [390922.657808] bremer udevadm[27187]: KERNEL[390922.656629] change /devices/virtual/block/dm-1 (block) > [390922.657808] bremer udevadm[27187]: SEQNUM=42167 > [390922.663968] bremer udevadm[27187]: KERNEL[390922.663941] change /devices/virtual/block/dm-1 (block) > [390922.663968] bremer udevadm[27187]: DM_NR_VALID_PATHS=2 > [390922.663968] bremer udevadm[27187]: SEQNUM=42168 > [390922.669569] bremer udevadm[27187]: KERNEL[390922.664428] change /devices/virtual/block/dm-1 (block) > [390922.669569] bremer udevadm[27187]: DM_NR_VALID_PATHS=3 > [390922.669569] bremer udevadm[27187]: SEQNUM=42169 > [390922.681809] bremer udevadm[27187]: KERNEL[390922.681784] change /devices/virtual/block/dm-1 (block) > [390922.681809] bremer udevadm[27187]: DM_NR_VALID_PATHS=0 > [390922.681809] bremer udevadm[27187]: SEQNUM=42170 > [390922.685992] bremer udevadm[27187]: KERNEL[390922.681883] change /devices/virtual/block/dm-1 (block) > [390922.685992] bremer udevadm[27187]: DM_NR_VALID_PATHS=1 > [390922.685992] bremer udevadm[27187]: SEQNUM=42171 > [390923.007623] bremer udevadm[27187]: KERNEL[390923.005324] change /devices/virtual/block/dm-1 (block) > [390923.007623] bremer udevadm[27187]: SEQNUM=42172 > [390923.191107] bremer udevadm[27187]: KERNEL[390923.191008] change /devices/virtual/block/dm-1 (block) > [390923.191107] bremer udevadm[27187]: DM_NR_VALID_PATHS=0 > [390923.191107] bremer udevadm[27187]: SEQNUM=42173 > [390923.191107] bremer udevadm[27187]: KERNEL[390923.191107] change /devices/virtual/block/dm-1 (block) > [390923.191107] bremer udevadm[27187]: DM_NR_VALID_PATHS=1 > [390923.197820] bremer udevadm[27187]: SEQNUM=42174 > [390923.197820] bremer udevadm[27187]: KERNEL[390923.191188] change /devices/virtual/block/dm-1 (block) > [390923.197820] bremer udevadm[27187]: DM_NR_VALID_PATHS=2 > [390923.197820] bremer udevadm[27187]: SEQNUM=42175 > [390923.327083] bremer udevadm[27187]: KERNEL[390923.326048] change /devices/virtual/block/dm-1 (block) > [390923.327083] bremer udevadm[27187]: SEQNUM=42176 > [390923.465309] bremer udevadm[27187]: KERNEL[390923.465183] change /devices/virtual/block/dm-1 (block) > [390923.465309] bremer udevadm[27187]: DM_NR_VALID_PATHS=0 > [390923.465309] bremer udevadm[27187]: SEQNUM=42177 > [390923.465309] bremer udevadm[27187]: KERNEL[390923.465255] change /devices/virtual/block/dm-1 (block) > [390923.465309] bremer udevadm[27187]: DM_NR_VALID_PATHS=1 > [390923.465309] bremer udevadm[27187]: SEQNUM=42178 > [390923.525701] bremer udevadm[27187]: KERNEL[390923.525677] change /devices/virtual/block/dm-1 (block) > [390923.525701] bremer udevadm[27187]: SEQNUM=42179 > [390923.530397] bremer udevadm[27187]: KERNEL[390923.527355] change /devices/virtual/block/dm-1 (block) > [390923.530397] bremer udevadm[27187]: DM_NR_VALID_PATHS=0 > [390923.530397] bremer udevadm[27187]: SEQNUM=42180 > [390923.728997] bremer udevadm[27187]: KERNEL[390923.728977] change /devices/virtual/block/dm-1 (block) > [390923.728997] bremer udevadm[27187]: SEQNUM=42181 > [390924.428687] bremer udevadm[27187]: KERNEL[390924.428662] add /devices/pci0000:00/0000:00:01.0/0000:07:00.4/host7/session1/target7:0:0/7:0:0:1/block/sdd (block) > [390924.428687] bremer udevadm[27187]: SEQNUM=42187 > [390924.432974] bremer udevadm[27187]: KERNEL[390924.428740] add /devices/pci0000:00/0000:00:01.0/0000:07:00.4/host7/session1/target7:0:0/7:0:0:1/block/sdd/sdd1 (block) > [390924.432974] bremer udevadm[27187]: SEQNUM=42188 > [390924.542892] bremer udevadm[27187]: KERNEL[390924.541111] change /devices/virtual/block/dm-1 (block) > [390924.542892] bremer udevadm[27187]: SEQNUM=42189 > [390925.271616] bremer udevadm[27187]: KERNEL[390925.260886] add /devices/pci0000:00/0000:00:01.0/0000:07:00.4/host7/session2/target7:0:1/7:0:1:1/block/sdf (block) > [390925.271616] bremer udevadm[27187]: SEQNUM=42196 > [390925.271616] bremer udevadm[27187]: KERNEL[390925.266471] add /devices/pci0000:00/0000:00:01.0/0000:07:00.4/host7/session2/target7:0:1/7:0:1:1/block/sdf/sdf1 (block) > [390925.271616] bremer udevadm[27187]: SEQNUM=42197 > [390926.801746] bremer udevadm[27187]: KERNEL[390926.793914] change /devices/virtual/block/dm-1 (block) > [390926.801746] bremer udevadm[27187]: SEQNUM=42199 > [390926.986451] bremer udevadm[27187]: KERNEL[390926.985953] change /devices/virtual/block/dm-20 (block) > [390926.986451] bremer udevadm[27187]: SEQNUM=42200 > [390927.120020] bremer udevadm[27187]: KERNEL[390927.119970] add /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-2/target9:0:2/9:0:2:1/block/sdj (block) > [390927.120020] bremer udevadm[27187]: SEQNUM=42208 > [390927.123365] bremer udevadm[27187]: KERNEL[390927.120445] add /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-2/target9:0:2/9:0:2:1/block/sdj/sdj1 (block) > [390927.123365] bremer udevadm[27187]: SEQNUM=42209 > [390927.317358] bremer udevadm[27187]: KERNEL[390927.317323] change /devices/pci0000:00/0000:00:01.0/0000:07:00.4/host7/session1/target7:0:0/7:0:0:1/block/sdd (block) > [390927.317358] bremer udevadm[27187]: SEQNUM=42218 > [390927.326789] bremer udevadm[27187]: KERNEL[390927.326772] add /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-5/target9:0:5/9:0:5:1/block/sdn (block) > [390927.326789] bremer udevadm[27187]: SEQNUM=42219 > [390927.351321] bremer udevadm[27187]: KERNEL[390927.327152] add /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-5/target9:0:5/9:0:5:1/block/sdn/sdn1 (block) > [390927.351321] bremer udevadm[27187]: SEQNUM=42220 > [390927.351321] bremer udevadm[27187]: KERNEL[390927.351084] change /devices/virtual/block/dm-1 (block) > [390927.351321] bremer udevadm[27187]: SEQNUM=42221 > [390927.516235] bremer udevadm[27187]: KERNEL[390927.515269] change /devices/virtual/block/dm-20 (block) > [390927.527714] bremer udevadm[27187]: SEQNUM=42222 > [390928.200506] bremer udevadm[27187]: KERNEL[390927.770567] change /devices/virtual/block/dm-1 (block) > [390928.200506] bremer udevadm[27187]: SEQNUM=42223 > [390928.200506] bremer udevadm[27187]: KERNEL[390927.943102] change /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-2/target9:0:2/9:0:2:1/block/sdj (block) > [390928.200506] bremer udevadm[27187]: SEQNUM=42226 > [390928.315254] bremer udevadm[27187]: KERNEL[390928.211714] change /devices/pci0000:00/0000:00:01.0/0000:07:00.4/host7/session2/target7:0:1/7:0:1:1/block/sdf (block) > [390928.315254] bremer udevadm[27187]: SEQNUM=42235 > [390928.315254] bremer udevadm[27187]: KERNEL[390928.211751] add /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-6/target9:0:6/9:0:6:1/block/sdp (block) > [390928.315254] bremer udevadm[27187]: SEQNUM=42236 > [390928.315254] bremer udevadm[27187]: KERNEL[390928.211783] add /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-6/target9:0:6/9:0:6:1/block/sdp/sdp1 (block) > [390928.315254] bremer udevadm[27187]: SEQNUM=42237 > [390928.315254] bremer udevadm[27187]: KERNEL[390928.251606] change /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-5/target9:0:5/9:0:5:1/block/sdn (block) > [390928.315254] bremer udevadm[27187]: SEQNUM=42238 > [390928.315254] bremer udevadm[27187]: KERNEL[390928.282997] change /devices/virtual/block/dm-1 (block) > [390928.315254] bremer udevadm[27187]: SEQNUM=42239 > [390928.817829] bremer udevadm[27187]: KERNEL[390928.816822] add /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-7/target9:0:7/9:0:7:1/block/sdr (block) > [390928.817829] bremer udevadm[27187]: SEQNUM=42247 > [390928.854385] bremer udevadm[27187]: KERNEL[390928.820989] add /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-7/target9:0:7/9:0:7:1/block/sdr/sdr1 (block) > [390928.854385] bremer udevadm[27187]: SEQNUM=42248 > [390929.247051] bremer udevadm[27187]: KERNEL[390929.246512] change /devices/virtual/block/dm-1 (block) > [390929.247051] bremer udevadm[27187]: SEQNUM=42249 > [390929.394536] bremer udevadm[27187]: KERNEL[390929.394166] change /devices/virtual/block/dm-1 (block) > [390929.394536] bremer udevadm[27187]: SEQNUM=42250 > [390929.611595] bremer udevadm[27187]: KERNEL[390929.611539] change /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-6/target9:0:6/9:0:6:1/block/sdp (block) > [390929.611595] bremer udevadm[27187]: SEQNUM=42252 > [390929.663785] bremer udevadm[27187]: KERNEL[390929.663663] change /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-7/target9:0:7/9:0:7:1/block/sdr (block) > [390929.663785] bremer udevadm[27187]: SEQNUM=42254 > [390929.719168] bremer udevadm[27187]: KERNEL[390929.717500] change /devices/virtual/block/dm-1 (block) > [390929.719168] bremer udevadm[27187]: SEQNUM=42255 > [390929.723174] bremer udevadm[27187]: KERNEL[390929.719502] change /devices/pci0000:00/0000:00:01.0/0000:07:00.4/host7/session1/target7:0:0/7:0:0:1/block/sdd (block) > [390929.723174] bremer udevadm[27187]: SEQNUM=42257 > [390929.735876] bremer udevadm[27187]: KERNEL[390929.735848] change /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-2/target9:0:2/9:0:2:1/block/sdj (block) > [390929.735876] bremer udevadm[27187]: SEQNUM=42259 > [390929.755386] bremer udevadm[27187]: KERNEL[390929.755343] change /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-5/target9:0:5/9:0:5:1/block/sdn (block) > [390929.755386] bremer udevadm[27187]: SEQNUM=42261 > [390929.877702] bremer udevadm[27187]: KERNEL[390929.877683] change /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-6/target9:0:6/9:0:6:1/block/sdp (block) > [390929.877702] bremer udevadm[27187]: SEQNUM=42266 > [390929.924831] bremer udevadm[27187]: KERNEL[390929.878064] change /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-7/target9:0:7/9:0:7:1/block/sdr (block) > [390929.924831] bremer udevadm[27187]: SEQNUM=42267 > [390929.955790] bremer udevadm[27187]: KERNEL[390929.927585] change /devices/pci0000:00/0000:00:01.0/0000:07:00.4/host7/session2/target7:0:1/7:0:1:1/block/sdf (block) > [390929.955790] bremer udevadm[27187]: SEQNUM=42269 > [390930.020907] bremer udevadm[27187]: KERNEL[390930.011276] change /devices/virtual/block/dm-1 (block) > [390930.020907] bremer udevadm[27187]: SEQNUM=42270 > [390930.370889] bremer udevadm[27187]: KERNEL[390930.369901] change /devices/virtual/block/dm-20 (block) > [390930.370889] bremer udevadm[27187]: SEQNUM=42271 > [390930.496407] bremer udevadm[27187]: KERNEL[390930.495825] change /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-2/target9:0:2/9:0:2:1/block/sdj (block) > [390930.496407] bremer udevadm[27187]: SEQNUM=42272 > [390930.572262] bremer udevadm[27187]: KERNEL[390930.503861] change /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-5/target9:0:5/9:0:5:1/block/sdn (block) > [390930.572262] bremer udevadm[27187]: SEQNUM=42273 > [390931.166954] bremer udevadm[27187]: KERNEL[390931.166937] change /devices/virtual/block/dm-20 (block) > [390931.166954] bremer udevadm[27187]: SEQNUM=42274 > [390935.201018] bremer udevadm[27187]: KERNEL[390935.198872] change /devices/virtual/block/dm-1 (block) > [390935.201018] bremer udevadm[27187]: DM_NR_VALID_PATHS=4 > [390935.201018] bremer udevadm[27187]: SEQNUM=42275 > [390935.201018] bremer udevadm[27187]: KERNEL[390935.198928] change /devices/virtual/block/dm-1 (block) > [390935.201018] bremer udevadm[27187]: DM_NR_VALID_PATHS=5 > [390935.201018] bremer udevadm[27187]: SEQNUM=42276 > [390937.211383] bremer udevadm[27187]: KERNEL[390937.210550] change /devices/virtual/block/dm-1 (block) > [390937.211383] bremer udevadm[27187]: SEQNUM=42277 > [390937.381207] bremer udevadm[27187]: KERNEL[390937.381054] change /devices/virtual/block/dm-1 (block) > [390937.381207] bremer udevadm[27187]: DM_NR_VALID_PATHS=4 > [390937.381207] bremer udevadm[27187]: SEQNUM=42278 > [390937.381207] bremer udevadm[27187]: KERNEL[390937.381145] change /devices/virtual/block/dm-1 (block) > [390937.381207] bremer udevadm[27187]: DM_NR_VALID_PATHS=5 > [390937.381207] bremer udevadm[27187]: SEQNUM=42279 > [390937.429646] bremer udevadm[27187]: KERNEL[390937.429621] change /devices/virtual/block/dm-20 (block) > [390937.429646] bremer udevadm[27187]: SEQNUM=42280 > [390937.985145] bremer udevadm[27187]: KERNEL[390937.985121] remove /devices/pci0000:00/0000:00:01.0/0000:07:00.4/host7/session1/target7:0:0/7:0:0:1/block/sdd/sdd1 (block) > [390937.985145] bremer udevadm[27187]: SEQNUM=42285 > [390937.987026] bremer udevadm[27187]: KERNEL[390937.985775] remove /devices/pci0000:00/0000:00:01.0/0000:07:00.4/host7/session1/target7:0:0/7:0:0:1/block/sdd (block) > [390937.987026] bremer udevadm[27187]: SEQNUM=42287 > [390938.015485] bremer udevadm[27187]: KERNEL[390938.015136] remove /devices/pci0000:00/0000:00:01.0/0000:07:00.4/host7/session2/target7:0:1/7:0:1:1/block/sdf/sdf1 (block) > [390938.015485] bremer udevadm[27187]: SEQNUM=42293 > [390938.023810] bremer udevadm[27187]: KERNEL[390938.018748] remove /devices/pci0000:00/0000:00:01.0/0000:07:00.4/host7/session2/target7:0:1/7:0:1:1/block/sdf (block) > [390938.023810] bremer udevadm[27187]: SEQNUM=42295 > [390938.031063] bremer udevadm[27187]: KERNEL[390938.029535] change /devices/virtual/block/dm-1 (block) > [390938.031063] bremer udevadm[27187]: SEQNUM=42297 > [390938.446484] bremer udevadm[27187]: KERNEL[390938.139772] change /devices/virtual/block/dm-1 (block) > [390938.446484] bremer udevadm[27187]: DM_NR_VALID_PATHS=3 > [390938.446484] bremer udevadm[27187]: SEQNUM=42298 > [390938.446484] bremer udevadm[27187]: KERNEL[390938.140898] change /devices/virtual/block/dm-1 (block) > [390938.446484] bremer udevadm[27187]: DM_NR_VALID_PATHS=4 > [390938.446484] bremer udevadm[27187]: SEQNUM=42299 > [390938.446484] bremer udevadm[27187]: KERNEL[390938.149693] remove /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-2/target9:0:2/9:0:2:1/block/sdj/sdj1 (block) > [390938.446484] bremer udevadm[27187]: SEQNUM=42304 > [390938.446484] bremer udevadm[27187]: KERNEL[390938.237922] change /devices/virtual/block/dm-1 (block) > [390938.446484] bremer udevadm[27187]: DM_NR_VALID_PATHS=2 > [390938.446484] bremer udevadm[27187]: SEQNUM=42305 > [390938.446484] bremer udevadm[27187]: KERNEL[390938.239503] remove /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-2/target9:0:2/9:0:2:1/block/sdj (block) > [390938.446484] bremer udevadm[27187]: SEQNUM=42307 > [390938.446484] bremer udevadm[27187]: KERNEL[390938.327236] remove /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-5/target9:0:5/9:0:5:1/block/sdn/sdn1 (block) > [390938.506363] bremer udevadm[27187]: SEQNUM=42313 > [390938.506363] bremer udevadm[27187]: KERNEL[390938.334884] remove /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-5/target9:0:5/9:0:5:1/block/sdn (block) > [390938.506363] bremer udevadm[27187]: SEQNUM=42315 > [390938.506363] bremer udevadm[27187]: KERNEL[390938.365174] remove /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-6/target9:0:6/9:0:6:1/block/sdp/sdp1 (block) > [390938.506363] bremer udevadm[27187]: SEQNUM=42321 > [390938.506363] bremer udevadm[27187]: KERNEL[390938.365980] remove /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-6/target9:0:6/9:0:6:1/block/sdp (block) > [390938.506363] bremer udevadm[27187]: SEQNUM=42323 > [390938.506363] bremer udevadm[27187]: KERNEL[390938.409840] remove /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-7/target9:0:7/9:0:7:1/block/sdr/sdr1 (block) > [390938.506363] bremer udevadm[27187]: SEQNUM=42329 > [390938.506363] bremer udevadm[27187]: KERNEL[390938.455190] change /devices/virtual/block/dm-1 (block) > [390938.506363] bremer udevadm[27187]: SEQNUM=42331 > [390938.506363] bremer udevadm[27187]: KERNEL[390938.457370] remove /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-7/target9:0:7/9:0:7:1/block/sdr (block) > [390938.525323] bremer udevadm[27187]: SEQNUM=42332 > [390938.583254] bremer udevadm[27187]: KERNEL[390938.579475] change /devices/virtual/block/dm-1 (block) > [390938.583254] bremer udevadm[27187]: DM_NR_VALID_PATHS=2 > [390938.583254] bremer udevadm[27187]: SEQNUM=42334 > [390938.583254] bremer udevadm[27187]: KERNEL[390938.579549] change /devices/virtual/block/dm-1 (block) > [390938.583254] bremer udevadm[27187]: DM_NR_VALID_PATHS=3 > [390938.583254] bremer udevadm[27187]: SEQNUM=42335 > [390938.674003] bremer udevadm[27187]: KERNEL[390938.673980] change /devices/virtual/block/dm-1 (block) > [390938.674003] bremer udevadm[27187]: DM_NR_VALID_PATHS=1 > [390938.674003] bremer udevadm[27187]: SEQNUM=42336 > [390938.726836] bremer udevadm[27187]: KERNEL[390938.726746] change /devices/virtual/block/dm-1 (block) > [390938.726836] bremer udevadm[27187]: DM_NR_VALID_PATHS=0 > [390938.726836] bremer udevadm[27187]: SEQNUM=42337 > [390938.812787] bremer udevadm[27187]: KERNEL[390938.812765] change /devices/virtual/block/dm-1 (block) > [390938.812787] bremer udevadm[27187]: SEQNUM=42338 > [390939.005794] bremer udevadm[27187]: KERNEL[390939.003576] change /devices/virtual/block/dm-1 (block) > [390939.005794] bremer udevadm[27187]: DM_NR_VALID_PATHS=0 > [390939.005794] bremer udevadm[27187]: SEQNUM=42339 > [390939.005794] bremer udevadm[27187]: KERNEL[390939.003669] change /devices/virtual/block/dm-1 (block) > [390939.005794] bremer udevadm[27187]: DM_NR_VALID_PATHS=1 > [390939.005794] bremer udevadm[27187]: SEQNUM=42340 > [390939.005794] bremer udevadm[27187]: KERNEL[390939.005303] change /devices/virtual/block/dm-1 (block) > [390939.005794] bremer udevadm[27187]: DM_NR_VALID_PATHS=2 > [390939.005794] bremer udevadm[27187]: SEQNUM=42341 > [390939.111993] bremer udevadm[27187]: KERNEL[390939.111147] change /devices/virtual/block/dm-1 (block) > [390939.111993] bremer udevadm[27187]: SEQNUM=42342 > [390939.118368] bremer udevadm[27187]: KERNEL[390939.115373] change /devices/virtual/block/dm-1 (block) > [390939.118368] bremer udevadm[27187]: DM_NR_VALID_PATHS=0 > [390939.118368] bremer udevadm[27187]: SEQNUM=42343 > [390939.118368] bremer udevadm[27187]: KERNEL[390939.115492] change /devices/virtual/block/dm-1 (block) > [390939.118368] bremer udevadm[27187]: DM_NR_VALID_PATHS=1 > [390939.118368] bremer udevadm[27187]: SEQNUM=42344 > [390939.528492] bremer udevadm[27187]: KERNEL[390939.525550] change /devices/virtual/block/dm-1 (block) > [390939.528492] bremer udevadm[27187]: SEQNUM=42345 > [390939.614831] bremer udevadm[27187]: KERNEL[390939.614803] change /devices/virtual/block/dm-1 (block) > [390939.614831] bremer udevadm[27187]: DM_NR_VALID_PATHS=0 > [390939.614831] bremer udevadm[27187]: SEQNUM=42346 > [390939.698977] bremer udevadm[27187]: KERNEL[390939.697700] change /devices/virtual/block/dm-1 (block) > [390939.698977] bremer udevadm[27187]: SEQNUM=42347 > [390941.621201] bremer udevadm[27187]: KERNEL[390941.619527] add /devices/pci0000:00/0000:00:01.0/0000:07:00.4/host7/session1/target7:0:0/7:0:0:1/block/sdd (block) > [390941.621201] bremer udevadm[27187]: SEQNUM=42355 > [390941.621201] bremer udevadm[27187]: KERNEL[390941.620032] add /devices/pci0000:00/0000:00:01.0/0000:07:00.4/host7/session1/target7:0:0/7:0:0:1/block/sdd/sdd1 (block) > [390941.621201] bremer udevadm[27187]: SEQNUM=42356 > [390941.719531] bremer udevadm[27187]: KERNEL[390941.717815] change /devices/virtual/block/dm-1 (block) > [390941.719531] bremer udevadm[27187]: SEQNUM=42357 > [390942.438547] bremer udevadm[27187]: KERNEL[390942.438514] add /devices/pci0000:00/0000:00:01.0/0000:07:00.4/host7/session2/target7:0:1/7:0:1:1/block/sdf (block) > [390942.438547] bremer udevadm[27187]: SEQNUM=42365 > [390942.446220] bremer udevadm[27187]: KERNEL[390942.438581] add /devices/pci0000:00/0000:00:01.0/0000:07:00.4/host7/session2/target7:0:1/7:0:1:1/block/sdf/sdf1 (block) > [390942.446220] bremer udevadm[27187]: SEQNUM=42366 > [390942.501852] bremer udevadm[27187]: KERNEL[390942.501830] change /devices/virtual/block/dm-20 (block) > [390942.501852] bremer udevadm[27187]: SEQNUM=42367 > [390942.558110] bremer udevadm[27187]: KERNEL[390942.555625] add /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-2/target9:0:2/9:0:2:1/block/sdj (block) > [390942.558110] bremer udevadm[27187]: SEQNUM=42375 > [390942.558110] bremer udevadm[27187]: KERNEL[390942.555999] add /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-2/target9:0:2/9:0:2:1/block/sdj/sdj1 (block) > [390942.558110] bremer udevadm[27187]: SEQNUM=42376 > [390942.605523] bremer udevadm[27187]: KERNEL[390942.565430] change /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-2/target9:0:2/9:0:2:1/block/sdj (block) > [390942.605523] bremer udevadm[27187]: SEQNUM=42377 > [390943.122495] bremer udevadm[27187]: KERNEL[390943.122455] add /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-5/target9:0:5/9:0:5:1/block/sdn (block) > [390943.122495] bremer udevadm[27187]: SEQNUM=42385 > [390943.122495] bremer udevadm[27187]: KERNEL[390943.122507] add /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-5/target9:0:5/9:0:5:1/block/sdn/sdn1 (block) > [390943.122495] bremer udevadm[27187]: SEQNUM=42386 > [390943.415924] bremer udevadm[27187]: KERNEL[390943.415181] change /devices/virtual/block/dm-1 (block) > [390943.415924] bremer udevadm[27187]: SEQNUM=42387 > [390943.591209] bremer udevadm[27187]: KERNEL[390943.591188] change /devices/virtual/block/dm-20 (block) > [390943.591209] bremer udevadm[27187]: SEQNUM=42388 > [390943.952947] bremer udevadm[27187]: KERNEL[390943.951985] add /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-6/target9:0:6/9:0:6:1/block/sdp (block) > [390943.952947] bremer udevadm[27187]: SEQNUM=42396 > [390943.952947] bremer udevadm[27187]: KERNEL[390943.952643] add /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-6/target9:0:6/9:0:6:1/block/sdp/sdp1 (block) > [390943.952947] bremer udevadm[27187]: SEQNUM=42397 > [390944.162459] bremer udevadm[27187]: KERNEL[390944.161005] change /devices/virtual/block/dm-1 (block) > [390944.162459] bremer udevadm[27187]: SEQNUM=42398 > [390944.327919] bremer udevadm[27187]: KERNEL[390944.327896] change /devices/virtual/block/dm-1 (block) > [390944.327919] bremer udevadm[27187]: SEQNUM=42399 > [390944.462480] bremer udevadm[27187]: KERNEL[390944.450906] change /devices/virtual/block/dm-1 (block) > [390944.462480] bremer udevadm[27187]: SEQNUM=42400 > [390944.617185] bremer udevadm[27187]: KERNEL[390944.617111] add /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-7/target9:0:7/9:0:7:1/block/sdr (block) > [390944.617185] bremer udevadm[27187]: SEQNUM=42408 > [390944.617185] bremer udevadm[27187]: KERNEL[390944.617177] add /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-7/target9:0:7/9:0:7:1/block/sdr/sdr1 (block) > [390944.617185] bremer udevadm[27187]: SEQNUM=42409 > [390944.671978] bremer udevadm[27187]: KERNEL[390944.659043] change /devices/virtual/block/dm-1 (block) > [390944.671978] bremer udevadm[27187]: SEQNUM=42410 > [390946.022466] bremer udevadm[27187]: KERNEL[390946.020770] change /devices/virtual/block/dm-1 (block) > [390946.022466] bremer udevadm[27187]: SEQNUM=42411 > [390952.494777] bremer udevadm[27187]: KERNEL[390952.494627] remove /devices/virtual/block/dm-20 (block) > [390952.494777] bremer udevadm[27187]: SEQNUM=42412 > [390952.506439] bremer udevadm[27187]: KERNEL[390952.501083] remove /devices/virtual/block/dm-20 (block) > [390952.506439] bremer udevadm[27187]: SEQNUM=42414 > [390952.583668] bremer udevadm[27187]: KERNEL[390952.583616] change /devices/virtual/block/dm-1 (block) > [390952.583668] bremer udevadm[27187]: SEQNUM=42415 > [390954.455934] bremer udevadm[27187]: KERNEL[390954.455883] change /devices/virtual/block/dm-1 (block) > [390954.455934] bremer udevadm[27187]: SEQNUM=42416 > [390954.531979] bremer udevadm[27187]: KERNEL[390954.531953] remove /devices/pci0000:00/0000:00:01.0/0000:07:00.4/host7/session1/target7:0:0/7:0:0:1/block/sdd/sdd1 (block) > [390954.531979] bremer udevadm[27187]: SEQNUM=42417 > [390954.550602] bremer udevadm[27187]: KERNEL[390954.550566] change /devices/pci0000:00/0000:00:01.0/0000:07:00.4/host7/session1/target7:0:0/7:0:0:1/block/sdd (block) > [390954.550602] bremer udevadm[27187]: SEQNUM=42418 > [390954.581518] bremer udevadm[27187]: KERNEL[390954.581464] remove /devices/pci0000:00/0000:00:01.0/0000:07:00.4/host7/session2/target7:0:1/7:0:1:1/block/sdf/sdf1 (block) > [390954.581518] bremer udevadm[27187]: SEQNUM=42419 > [390954.590478] bremer udevadm[27187]: KERNEL[390954.589744] change /devices/pci0000:00/0000:00:01.0/0000:07:00.4/host7/session2/target7:0:1/7:0:1:1/block/sdf (block) > [390954.590478] bremer udevadm[27187]: SEQNUM=42420 > [390954.627454] bremer udevadm[27187]: KERNEL[390954.627047] remove /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-2/target9:0:2/9:0:2:1/block/sdj/sdj1 (block) > [390954.627454] bremer udevadm[27187]: SEQNUM=42421 > [390954.638348] bremer udevadm[27187]: KERNEL[390954.637967] change /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-2/target9:0:2/9:0:2:1/block/sdj (block) > [390954.638348] bremer udevadm[27187]: SEQNUM=42422 > [390954.674020] bremer udevadm[27187]: KERNEL[390954.673998] remove /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-5/target9:0:5/9:0:5:1/block/sdn/sdn1 (block) > [390954.674699] bremer udevadm[27187]: SEQNUM=42423 > [390954.711117] bremer udevadm[27187]: KERNEL[390954.710629] change /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-5/target9:0:5/9:0:5:1/block/sdn (block) > [390954.711117] bremer udevadm[27187]: SEQNUM=42424 > [390954.726214] bremer udevadm[27187]: KERNEL[390954.726194] remove /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-6/target9:0:6/9:0:6:1/block/sdp/sdp1 (block) > [390954.726214] bremer udevadm[27187]: SEQNUM=42425 > [390954.735782] bremer udevadm[27187]: KERNEL[390954.735747] change /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-6/target9:0:6/9:0:6:1/block/sdp (block) > [390954.735782] bremer udevadm[27187]: SEQNUM=42426 > [390954.778212] bremer udevadm[27187]: KERNEL[390954.778190] remove /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-7/target9:0:7/9:0:7:1/block/sdr/sdr1 (block) > [390954.778212] bremer udevadm[27187]: SEQNUM=42427 > [390954.783988] bremer udevadm[27187]: KERNEL[390954.783952] change /devices/pci0000:00/0000:00:01.0/0000:07:00.6/host9/rport-9:0-7/target9:0:7/9:0:7:1/block/sdr (block) > [390954.783988] bremer udevadm[27187]: SEQNUM=42428 -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1118099] New: aws-cli-1.16.48-1.1.noarch requires python3-colorama <= 0.3.9, but this requirement cannot be provided
by bugzilla_noreply＠novell.com 01 Nov '22

01 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1118099 Bug ID: 1118099 Summary: aws-cli-1.16.48-1.1.noarch requires python3-colorama <= 0.3.9, but this requirement cannot be provided Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Cloud:Tools Assignee: public-cloud-maintainers(a)suse.de Reporter: rombert(a)apache.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- It seems that the aws-cli / python3-colorama dance is up again :-) Problem: aws-cli-1.16.48-1.1.noarch requires python3-colorama <= 0.3.9, but this requirement cannot be provided deleted providers: python3-colorama-0.3.9-1.3.noarch Solution 1: deinstallation of aws-cli-1.16.48-1.1.noarch Solution 2: keep obsolete python3-colorama-0.3.9-1.3.noarch Solution 3: break aws-cli-1.16.48-1.1.noarch by ignoring some of its dependencies -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1101785] New: rubygem-mysql2 update to 0.5 broke velum
by bugzilla_noreply＠novell.com 26 Oct '22

26 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1101785 Bug ID: 1101785 Summary: rubygem-mysql2 update to 0.5 broke velum Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Ruby Assignee: ruby-devel(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The package rubygem-mysql2 has been updated to version 0.5; this in turned made velum unresolvable (and uninstallable) Velum seems, as far as I saw on quick glance, to be the only consumer of rubygem-mysql2 -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1076835] New: [Build 20180117] Enlightenmnet: newly asks for language
by bugzilla_noreply＠novell.com 26 Oct '22

26 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1076835 Bug ID: 1076835 Summary: [Build 20180117] Enlightenmnet: newly asks for language Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/586280/modules/enlig htenment_first_start/steps/1 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ## Observation openQA test in scenario opensuse-Tumbleweed-NET-x86_64-otherDE_enlightenment@64bit fails in [enlightenment_first_start](https://openqa.opensuse.org/tests/586280/modules… ## Reproducible Fails since (at least) Build [20180117](https://openqa.opensuse.org/tests/586213) ## Expected result Last good: [20180116](https://openqa.opensuse.org/tests/584144) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?version=Tumbleweed&machine… The recent changes were a switch away from /etc/sysconfig/language:RC_LANG to fully localectl managed -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1006958] New: gdb build often stalls on OBS
by bugzilla_noreply＠novell.com 26 Oct '22

26 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1006958 Bug ID: 1006958 Summary: gdb build often stalls on OBS Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- gdb is among the list of packages that often cause a stall in OBS - OBS detects this after a while and cancels the build. The issue though is that unreliable builds are a pain and must not happen (especially when being a ring package; it is built very often in the stagings and every fail requires the staging managers to interact) The current fail I have here stops with: <[ 6299s] Running target unix/-m32/-fPIC/-pie >[ 6299s] Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target. >[ 6299s] Using /usr/share/dejagnu/config/unix.exp as generic interface file for target. >[ 6299s] Using /home/abuild/rpmbuild/BUILD/gdb-7.11.1/gdb/testsuite/config/unix.exp as tool-and-target-specific interface file. >[ 6299s] Running /home/abuild/rpmbuild/BUILD/gdb-7.11.1/gdb/testsuite/gdb.xml/tdesc-arch.exp ... >[ 6299s] /home/abuild/rpmbuild/BUILD/gdb-7.11.1/build-x86_64-suse-linux/gdb/gdb version 7.11.1 -nw -nx -data-directory /home/abuild/rpmbuild/BUILD/gdb-7.11.1/build-x86_64-suse-linux/gdb/testsuite.unix.-m32.-fPIC.-pie/../data-directory >[ 6299s] >[ 6299s] >[ 6299s] === gdb Summary === >[ 6299s] >[ 6299s] # of expected passes 8 >[ 6300s] /home/abuild/rpmbuild/BUILD/gdb-7.11.1/build-x86_64-suse-linux/gdb/gdb version 7.11.1 -nw -nx -data-directory /home/abuild/rpmbuild/BUILD/gdb-7.11.1/build-x86_64-suse-linux/gdb/testsuite.unix.-m32.-fPIC.-pie/../data-directory >[ 6300s] >[35104s] ### WATCHDOG MARKER END ### >[35104s] No buildstatus set, either the base system is broken (kernel/initrd/udev/glibc/bash/perl) >[35104s] or the build host has a kernel or hardware problem... > > >Job seems to be stuck here, killed. (after 28800 seconds of inactivity) -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 993011] New: [openQA] CTRL-ALT-DEL does not show the logout dialog
by bugzilla_noreply＠novell.com 26 Oct '22

26 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=993011 Bug ID: 993011 Summary: [openQA] CTRL-ALT-DEL does not show the logout dialog Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Seen by openQA tests, e.g. https://openqa.opensuse.org/tests/239654 After the system was upgraded from openSUSE 13.2 to Tumbleweed (20160808, first to have plasma 5.7.2), the logout dialog no longer shows when pressing ctrl-alt-del This appears on updates performed using the DVD and boot from the Network CD, but seems not to happen in the case when the system was updated using zdup. The tests had been re-run a couple times. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 941884] New: libcamgm fails test suite due to expired certificates
by bugzilla_noreply＠novell.com 26 Oct '22

26 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=941884 Bug ID: 941884 Summary: libcamgm fails test suite due to expired certificates Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: dimstar(a)opensuse.org QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- since recently, libcamgm no longer passes the test suite... the build lo ends with: [...] [ 358s] Running ListTest... [ 358s] Output doesn't match expected data: [ 358s] --- ./single.out/ListTest.out 2014-04-12 17:19:43.000000000 +0000 [ 358s] +++ ./single.out/out/ListTest.out 2015-08-16 18:11:50.226671071 +0000 [ 358s] @@ -125,7 +125,7 @@ [ 358s] country = DE [ 358s] emailAddress = suse(a)suse.de [ 358s] serial = 07 [ 358s] -status = Valid [ 358s] +status = Expired [ 358s] New Entry [ 358s] certificate = 08:40717a16174dc4d516f6fa7ee8eeb18c-1124792802 [ 358s] commonName = Full Test Certificate [ 358s] @@ -153,7 +153,7 @@ [ 358s] country = DE [ 358s] emailAddress = suse(a)suse.de [ 358s] serial = 0B [ 358s] -status = Valid [ 358s] +status = Expired [ 358s] getCertificateList successfully executed [ 358s] =================== end List tests ======================== [ 358s] DONE [ 358s] FAIL: ListTest [...] [ 364s] Running VerifyTest... [ 365s] Output doesn't match expected data: [ 365s] --- ./single.out/VerifyTest.out 2014-04-12 17:19:43.000000000 +0000 [ 365s] +++ ./single.out/out/VerifyTest.out 2015-08-16 18:11:57.086773026 +0000 [ 365s] @@ -6,10 +6,10 @@ [ 365s] 04: Verify failed: Found revoked certificate [ 365s] 05: Verify failed: Found revoked certificate [ 365s] 06: Verify failed: Found revoked certificate [ 365s] -07: Verify success [ 365s] +07: Verify failed: Found expired certificate [ 365s] 08: Verify failed: Found expired certificate [ 365s] 09: Verify failed: Found revoked certificate [ 365s] 0A: Verify failed: Found expired certificate [ 365s] -0B: Verify success [ 365s] +0B: Verify failed: Found expired certificate [ 365s] =================== end List tests ======================== [ 365s] DONE [ 365s] FAIL: VerifyTest [...] libcamgm is a dependency to yast2-ca-management, which in turn is required by yast2-auth-server (which is why a delete request for libcamgm back in May could not be fullfilled) This whole thing is a ring, packae, causing all stagings to fail, hence I mark it major -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 1002565] New: can't install ruby2.2-rubygem-rhc-testsuite-1.35.3-1.5.x86_64
by bugzilla_noreply＠novell.com 26 Oct '22

26 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1002565 Bug ID: 1002565 Summary: can't install ruby2.2-rubygem-rhc-testsuite-1.35.3-1.5.x86_64 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- can't install ruby2.2-rubygem-rhc-testsuite-1.35.3-1.5.x86_64 zypper in ruby2.2-rubygem-rhc-testsuite-1.35.3-1.5.x86_64 Loading repository data... Reading installed packages... Resolving package dependencies... >Problem: nothing provides rubygem(ruby:2.2.0:commander) < 4.3.0 needed by ruby2.2-rubygem-rhc-1.35.3-1.5.x86_64 > Solution 1: do not install ruby2.2-rubygem-rhc-testsuite-1.35.3-1.5.x86_64 > Solution 2: break ruby2.2-rubygem-rhc-1.35.3-1.5.x86_64 by ignoring some of its dependencies -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1066408] New: Deadbeef contains an invalid appdata.xml file
by bugzilla_noreply＠novell.com 26 Oct '22

26 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1066408 Bug ID: 1066408 Summary: Deadbeef contains an invalid appdata.xml file Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The package deadbeef ships with an appdata.xml file (to show in socftware centers), but the file is invalid. (appstream-builder:17416): As-WARNING **: ignoring description '<description><_p>DeaDBeeF (as in 0xDEADBEEF)…' from ./tmp/deadbeef-0.7.2-4.2/usr/share/appdata/deadbeef.appdata.xml: Unknown tag '_p' Seems upstream prepared the file for translation, but then did not pass it through the translation process -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 1023737] New: openSUSE:Factory/golang-google-golangorg-appengine fails to build
by bugzilla_noreply＠novell.com 26 Oct '22

26 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1023737 Bug ID: 1023737 Summary: openSUSE:Factory/golang-google-golangorg-appengine fails to build Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The package golang-google-golangorg-appengine fails to build in openSUSE:Factory. Earlier notifications by email to the bugowner and Maintainer have remained without reaction / fix. If the package is not being fixed within 2 weeks, it will be scheduled for removal from Tumbleweed -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1023734] New: openSUSE:Factory/golang-org-x-oauth2 fails to build
by bugzilla_noreply＠novell.com 26 Oct '22

26 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1023734 Bug ID: 1023734 Summary: openSUSE:Factory/golang-org-x-oauth2 fails to build Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The package golang-org-x-oauth2 fails to build in openSUSE:Factory. Earlier notifications by email to the bugowner and Maintainer have remained without reaction / fix. If the package is not being fixed within 2 weeks, it will be scheduled for removal from Tumbleweed -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 971006] New: rpmlint: no-dependency-on perl-base 5.22.1
by bugzilla_noreply＠novell.com 26 Oct '22

26 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=971006 Bug ID: 971006 Summary: rpmlint: no-dependency-on perl-base 5.22.1 Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- rpmlint does not understand how openSUSE specifies perl dependencies and falsly reports: no-dependency-on perl-base 5.22.1 in openSUSE, we use the macro %perl_requires which translates to: Requires: perl(:MODULE_COMPAT_5.22.1) It would be great to get this recognized as dependency being satisfied -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1132118] New: Xindy does not run due to incompatible CLISP runtime
by bugzilla_noreply＠novell.com 25 Oct '22

25 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1132118 Bug ID: 1132118 Summary: Xindy does not run due to incompatible CLISP runtime Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: christian-david(a)web.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- xindy does not run what can be tested with $ xindy --version xindy release: 2.5.1 xindy script version: 1.18 /usr/lib64/clisp-2.49.92/base/lisp.run: initialization file `/usr/lib64/xindy/xindy.mem' was not created by this version of CLISP runtime Same error happens if xindy is used for a “real” task. -- You are receiving this mail because: You are on the CC list for the bug.

2 13

[Bug 1041742] New: Filetriggers do not fire (reliably)
by bugzilla_noreply＠novell.com 25 Oct '22

25 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1041742 Bug ID: 1041742 Summary: Filetriggers do not fire (reliably) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)forge.provo.novell.com Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In GNOME:Next, we started experimenting with file triggers (with the goal to lower the number of bugs based on missing post scripts) As a sample, I implemented this trigger (on glib2-tools): %transfiletriggerin -n glib2-tools -- %{_datadir}/glib-2.0/schemas %{_bindir}/glib-compile-schemas %{_datadir}/glib-2.0/schemas %transfiletriggerpostun -n glib2-tools -- %{_datadir}/glib-2.0/schemas %{_bindir}/glib-compile-schemas %{_datadir}/glib-2.0/schemas The trigger is confirmed to work, but in some cases, it seems not to fire, eg on the package 'gdm' (which is currently the reason why http://download.opensuse.org/repositories/GNOME:/Medias/images/iso/?P=GNOME… fails to boot to desktop) zypper in --no-recommends gdm => the file trigger is not executed rpm -i gdm-3.24.1.rpm => the trigger actually seems to work (which is why I file it against libzypp) This currently stops us from moving forward and proposing file triggers to be more widely used (even though I think they can solve quite some packaging bugs) The packages in question for testing are all in the GNOME:Next repository (glib2 which has the trigger, it has the %glib2_gsettings_schema_post set to %nil, so packages that use it in their post script only get a dummy - once the implementation is complete, we will of course go and clean those out completely) -- You are receiving this mail because: You are on the CC list for the bug.

2 28

[Bug 1093168] New: pacemaker: using service template in preun/postun
by bugzilla_noreply＠novell.com 24 Oct '22

24 Oct '22

http://bugzilla.suse.com/show_bug.cgi?id=1093168 Bug ID: 1093168 Summary: pacemaker: using service template in preun/postun Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: High Availability Assignee: ha-bugs(a)suse.de Reporter: ro(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- you can not used a service template (foo@.service) without parameter in a specfile with the %service_add/del macros: %preun cts %service_del_preun pacemaker-cts-dummyd@.service %postun cts %service_del_postun pacemaker-cts-dummyd@.service this will just result in errors during uninstall of the package: (1/1) Removing pacemaker-cts-1.1.18+20180430.b12c320f5-1.4.noarch ........[done] Additional rpm output: Failed to stop pacemaker-cts-dummyd@.service: Unit name pacemaker-cts-dummyd@.service is missing the instance name. See system logs and 'systemctl status pacemaker-cts-dummyd@.service' for details. Failed to get load state of pacemaker-cts-dummyd@.service: Unit name pacemaker-cts-dummyd@.service is neither a valid invocation ID nor unit name. -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1115512] New: pam-config does not find (nor load) pam_yubico.so
by bugzilla_noreply＠novell.com 24 Oct '22

24 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1115512 Bug ID: 1115512 Summary: pam-config does not find (nor load) pam_yubico.so 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: fred.blaise(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0 Build Identifier: After installed pam_yubico, and adding the following line in /etc/pam.d/common-auth, running `sudo pam-config --update` fails with `/etc/pam.d/common-auth-pc: Unknown module pam_yubico.so, ignored!` The module never appears in the --list-modules either. Reproducible: Always Steps to Reproduce: 1. sudo zypper in pam_yubico 2. sudo ldconfig (or reboot) 3. Amend /etc/pam.d/common-auth-pc to add pam_yubico as requirement 4. Run pam-config --update and get ignore message. Actual Results: /etc/pam.d/common-auth-pc: Unknown module pam_yubico.so, ignored! Expected Results: Module loads and I can use my yubikey with pam. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1088177] New: Default Active Titlebar color on openSUSEdark and openSUSEdarkalternate colorchemes
by bugzilla_noreply＠novell.com 23 Oct '22

23 Oct '22

http://bugzilla.suse.com/show_bug.cgi?id=1088177 Bug ID: 1088177 Summary: Default Active Titlebar color on openSUSEdark and openSUSEdarkalternate colorchemes Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: andretiago(a)outlook.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 766009 --> http://bugzilla.suse.com/attachment.cgi?id=766009&action=edit Titlebar active color Default Active Titlebar color of openSUSEdark and openSUSEdarkalternate color schemes looks out of place and it's hard to read. https://i.imgur.com/vshYSxz.png I think the default color should be replaced -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1008674] New: Login difficulties with LightDM 1.20
by bugzilla_noreply＠novell.com 22 Oct '22

22 Oct '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1008674 Bug ID: 1008674 Summary: Login difficulties with LightDM 1.20 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: Markus.Elfring(a)web.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Today I dared to update the display manager to the version “LightDM 1.20.0-1.1”. Unfortunately, I observed that the corresponding graphical login did not work as expected. The information “exist status: 1” was recorded in the systemd journal. -- You are receiving this mail because: You are on the CC list for the bug.

2 10