April 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1184243] [Build 117.13] yast online updates fails at no update repositories being present
by bugzilla_noreply＠suse.com 01 Apr '21

01 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1184243 https://bugzilla.suse.com/show_bug.cgi?id=1184243#c2 --- Comment #2 from Ladislav Slez�k <lslezak(a)suse.com> --- I'm checking the details... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1139939] New: kernel does not contain version information
by bugzilla_noreply＠novell.com 01 Apr '21

01 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1139939 Bug ID: 1139939 Summary: kernel does not contain version information Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: S/390-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: gunreben(a)t-online.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The current kernel rpm (5.1.10-1.2) does not contain a kernel version string. Unfortunately, this makes the install fail, because get_kernel_version does not return the version string. To reproduce, run get_kernel_version on the kernel binary To get the rpm, run: osc getbinaries openSUSE:Factory:zSystems kernel-default standard s390x Another possibility to check is to run the command strings on the kernel which is found on DVD1 below /boot/s390x/linux. -- You are receiving this mail because: You are on the CC list for the bug.

2 9

[Bug 1175633] AUDIT-TRACKER: kdenetwork-filesharing (polkit-unauthorized-privilege, polkit-untracked-privilege, suse-dbus-unauthorized-service)
by bugzilla_noreply＠suse.com 01 Apr '21

01 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1175633 https://bugzilla.suse.com/show_bug.cgi?id=1175633#c11 --- Comment #11 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1175633) was mentioned in https://build.opensuse.org/request/show/882506 Factory / rpmlint -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1184244] New: [Build 117.13] Leap 15.3 ports update repo is expected in test
by bugzilla_noreply＠suse.com 01 Apr '21

01 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1184244 Bug ID: 1184244 Summary: [Build 117.13] Leap 15.3 ports update repo is expected in test Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other URL: https://openqa.opensuse.org/tests/1686050/modules/yast 2_control_center/steps/20 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: lubos.kocman(a)suse.com QA Contact: jsrain(a)suse.com Found By: openQA Blocker: Yes Seems like for whatever reason there is an expectation for an update repository with "ports" in url. This should not be present in 15.3 ## Observation openQA test in scenario opensuse-15.3-DVD-aarch64-yast2_gui@aarch64 fails in [yast2_control_center](https://openqa.opensuse.org/tests/1686050/modules/yas… ## Test suite description Maintainer: qsf-y Test for yast2 UI, GUI only. Running on created gnome images which provides both text console for ncurses UI tests as well as the gnome environment for the GUI tests. Temporarily added YAST2_GUI_TERMINATE_PREVIOUS_INSTANCES to see if helps. This variable triggers code which terminates all yast2 processes before starting new one. (see poo#26104). ## Reproducible Fails since (at least) Build [32.4](https://openqa.opensuse.org/tests/1500129) ## Expected result Last good: (unknown) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=opensu… -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1184257] hardcode knowledge about https://debuginfod.opensuse.org/ in debuginfod client
by bugzilla_noreply＠suse.com 01 Apr '21

01 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1184257 http://bugzilla.opensuse.org/show_bug.cgi?id=1184257#c2 --- Comment #2 from Martin Li��ka <martin.liska(a)suse.com> --- Good point, I can confirm that using [1]: $ ./obs-download-rpms.py https://api.opensuse.org openSUSE:Factory:Staging:A ~/BIG/A $ find . -name '*debugsource*' | wc -l 1834 $ find . -name '*debugsource*' | xargs rpm -qpl | grep -v '/usr/src/debug' (contains no files) $ find . -name '*debugsource*' | xargs rpm -qpl | grep '/usr/src/debug' | wc -l 550850 I'm also thinking about adding a patch to rpm package where we can add assert that all debugsource files live in /usr/src/debug. What do you think? [1] https://github.com/marxin/script-misc/blob/master/obs-download-rpms.py -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1184257] hardcode knowledge about https://debuginfod.opensuse.org/ in debuginfod client
by bugzilla_noreply＠suse.com 01 Apr '21

01 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1184257 http://bugzilla.opensuse.org/show_bug.cgi?id=1184257#c1 --- Comment #1 from Tom de Vries <tdevries(a)suse.com> --- I wrote the following script to verify the assumption: ... #!/bin/sh packages=$(zypper packages | grep debugsource | sed 's/[^|]*|//' | awk '{print $3}') for p in $packages; do sudo zypper install -y --download-only $p 1>&2 rpm=$(find /var/cache/zypp -iname $p*rpm) n=$(echo $rpm | wc -w) if [ $n -ne 1 ]; then echo "Did not find single rpm: \"$rpm\"" > /dev/stderr continue fi rpm -qlp $rpm done ... It generates a list of all the source files in all the source packages. I ran it for quite a bit, and only /usr/src/debug files were found. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1181467] plymouth doesn't restore the console properly when turned off
by bugzilla_noreply＠suse.com 01 Apr '21

01 Apr '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1181467 http://bugzilla.opensuse.org/show_bug.cgi?id=1181467#c3 --- Comment #3 from Cliff Zhao <qzhao(a)suse.com> --- Created attachment 847892 --> http://bugzilla.opensuse.org/attachment.cgi?id=847892&action=edit openQA screen-shot With the recent openSUSE case in openQA, I could not find the test of "step4". I suggest you remove the "/usr/lib/systemd/system/getty(a)tty1.service.d/20-defaults-SUSE.conf", and re-try. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1183821] Bluetooth headphones disconnect periodically
by bugzilla_noreply＠suse.com 01 Apr '21

01 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1183821 https://bugzilla.suse.com/show_bug.cgi?id=1183821#c2 --- Comment #2 from Al Cho <acho(a)suse.com> --- Thanks, backporting and sr 882472 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1182751] Chromium is very slow in snapshot 20210223
by bugzilla_noreply＠suse.com 01 Apr '21

01 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1182751 https://bugzilla.suse.com/show_bug.cgi?id=1182751#c4 --- Comment #4 from Oliver Kurz <okurz(a)suse.com> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: gnome@ https://openqa.opensuse.org/tests/1687167 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" 3. The label in the openQA scenario is removed -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1182125] [Build 20210207] no yast2 online update icon in control center
by bugzilla_noreply＠suse.com 01 Apr '21

01 Apr '21

https://bugzilla.suse.com/show_bug.cgi?id=1182125 https://bugzilla.suse.com/show_bug.cgi?id=1182125#c10 --- Comment #10 from Oliver Kurz <okurz(a)suse.com> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: yast2_gui https://openqa.opensuse.org/tests/1687301 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" 3. The label in the openQA scenario is removed -- You are receiving this mail because: You are on the CC list for the bug.

1 0