July 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1173704] Installation ISO on Raspberry Pi 3 B+ shows no output when using serial cable only
by bugzilla_noreply＠suse.com 08 Jul '20

08 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1173704 https://bugzilla.suse.com/show_bug.cgi?id=1173704#c9 Steffen Winterfeldt <snwint(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Installation |Kernel Assignee|yast2-maintainers(a)suse.de |kernel-bugs(a)opensuse.org QA Contact|jsrain(a)suse.com |qa-bugs(a)suse.de --- Comment #9 from Steffen Winterfeldt <snwint(a)suse.com> --- Anyway, to sum things up: with console=ttyS0/ttyAMA1 the installer is connecting to these devices but nothing shows up on the line. This doen't look like an installer issue to me. Handing this over to our aarch64 experts. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1173704] Installation ISO on Raspberry Pi 3 B+ shows no output when using serial cable only
by bugzilla_noreply＠suse.com 08 Jul '20

08 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1173704 https://bugzilla.suse.com/show_bug.cgi?id=1173704#c8 Steffen Winterfeldt <snwint(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(moritzrakow(a)web.d | |e) --- Comment #8 from Steffen Winterfeldt <snwint(a)suse.com> --- Hm, you don't have to specify the baud rate, btw? Like console=ttyS0,115200? And the same at the other end? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1173860] kernel-5.3.18-lp152.20.7.1 crash at boot with permissions violation
by bugzilla_noreply＠suse.com 08 Jul '20

08 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1173860 Marcus Meissner <meissner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1173865] New: KXQt Wallpaper configuration "sticky," does not change or set properly
by bugzilla_noreply＠suse.com 08 Jul '20

08 Jul '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1173865 Bug ID: 1173865 Summary: KXQt Wallpaper configuration "sticky," does not change or set properly Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: tonysu(a)su-networking.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is about LXQt, don't know if other various Desktops affected, I suspect something changed how openSUSE interfaces with DE wallpapers, maybe more. LXQt - Incorrectly displays default openSUSE wallpaper on installation. Launch LXQt Configuration Center > Appearance, is set to the default "Frost" but non-functional. Later although I found that clicking almost every other choice did nothing, after clicking "System" suddenly selection was functional and any wallpaper can be selected and applied. Compared to 15.1, noticed the removal of the "Apply" button because selection is dynamically applied which made troubleshooting a bit confusing because was an extra parameter to consider why wasn't working. Speaking of which... I've watched various YouTube about 15.2 now, and one of the first things all comment on is the default wallpaper. IIRC I think this wallpaper was introduced sometime about 13.1? A more interesting wallpaper would have made a world of difference, everyone is changing it out as one of the first recommended configurations. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1173794] New: [Migration]: error happen when do leap15.2 -> sles15.2 zdup upgrade
by bugzilla_noreply＠suse.com 08 Jul '20

08 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1173794 Bug ID: 1173794 Summary: [Migration]: error happen when do leap15.2 -> sles15.2 zdup upgrade Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: wegao(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Fresh install Leap15.2 build (server mode), error happen try register at SCC to get the SUSE Linux Enterprise Server repositories, the command process exit directly and no chance to select option. Refer following link. https://documentation.suse.com/sles/15-SP1/html/SLES-all/cha-upgrade-online… SUSEConnect -r xxxx -p SLES/15.2/x86_64 c76:~ # SUSEConnect -r deedc51104e549deb -p SLES/15.2/x86_64 Registering system to SUSE Customer Center Updating system details on https://scc.suse.com ... Activating SLES 15.2 x86_64 ... -> Adding service to system ... -> Installing release package ... command 'zypper --no-refresh --non-interactive install --no-recommends --auto-agree-with-product-licenses -t product SLES' failed Error: zypper returned (4) with 'Building repository 'SLE-Product-SLES15-SP2-Pool' cache [....done] Building repository 'SLE-Product-SLES15-SP2-Updates' cache [....done] Loading repository data... Reading installed packages... Resolving package dependencies... 2 Problems: Problem: product:openSUSE-15.2-1.x86_64 conflicts with namespace:otherproviders(distribution-release) provided by product:SLES-15.2-0.x86_64 Problem: product:SLES-15.2-0.x86_64 requires product(SLES) = 15.2-0, but this requirement cannot be provided Problem: product:openSUSE-15.2-1.x86_64 conflicts with namespace:otherproviders(distribution-release) provided by product:SLES-15.2-0.x86_64 Solution 1: deinstallation of product:openSUSE-15.2-1.x86_64 Solution 2: do not install product:SLES-15.2-0.x86_64 Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c/d/?] (c): c' <==== exit directly and no chance to input any option c76:~ # c76:~ # -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1171438] keepassxc should no longer have libgcrypt20-hmac in BuildRequires/Requires
by bugzilla_noreply＠suse.com 08 Jul '20

08 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1171438 https://bugzilla.suse.com/show_bug.cgi?id=1171438#c3 --- Comment #3 from OBSbugzilla Bot <bwiedemann+obsbugzillabot(a)suse.com> --- This is an autogenerated message for OBS integration: This bug (1171438) was mentioned in https://build.opensuse.org/request/show/819308 15.1+15.2+Backports:SLE-15-SP1 / keepassxc -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1173862] New: hardware encoding not working with nvidia driver provided by repository
by bugzilla_noreply＠suse.com 07 Jul '20

07 Jul '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1173862 Bug ID: 1173862 Summary: hardware encoding not working with nvidia driver provided by repository Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 3rd Party Driver Assignee: gfx-bugs(a)suse.de Reporter: cornelis(a)solcon.nl QA Contact: sndirsch(a)suse.com Found By: --- Blocker: --- When I install the nvidia driver from https://download.nvidia.com/opensuse/leap/15.2/ ffmpeg with nvenc does not work as normal user. It does work under root. When I install the driver directly (the so-called hard way) ffmpeg with nvenc *does* work under a normal user account. I see this when executing a command like: ffmpeg -i input.mp4 -c:v h264_nvenc out.mp4 I found similar issues on the forum: * https://forums.opensuse.org/showthread.php/540150-NVidia-installer-broke-CU… * https://forums.opensuse.org/showthread.php/538981-Blender-and-Davinci-resol… -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1099766] New: Falkon web browser - No .ymp support configured aka "One Click Install"
by bugzilla_noreply＠novell.com 07 Jul '20

07 Jul '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1099766 Bug ID: 1099766 Summary: Falkon web browser - No .ymp support configured aka "One Click Install" Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: tonysu(a)su-networking.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Am thinking if Falkon is to be officially supported as the main web browser for Desktops like LXQt/LXDE, it should be configured with a .ymp MIME type like FF and Chromium so that it can be used at https://software.opensuse.org/search/ Have not checked where Falkon is commonly installed as part of the default Desktop pattern, believe the OS is not relevant. Although this is on LEAP 15, this is probably true also for Tumbleweed and probably 42.3 -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1173733] Compute capabilities of NVIDIA drivers cannot be initialised by non-root users
by bugzilla_noreply＠suse.com 07 Jul '20

07 Jul '20

https://bugzilla.suse.com/show_bug.cgi?id=1173733 https://bugzilla.suse.com/show_bug.cgi?id=1173733#c19 Matthias Bach <marix(a)marix.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #19 from Matthias Bach <marix(a)marix.org> --- Thanks, sadly it seems the nvidia-uvm-tools.tar tarball makes things worse for me instead of better. With that applied SDDM will only give me a black screen with a mouse pointer. Yet, I still get: > ls /dev/nv* /dev/nvidia0 /dev/nvidiactl /dev/nvidia-modeset /dev/nvram > lsmod | grep nvidia nvidia_drm 53248 2 nvidia_modeset 1118208 3 nvidia_drm nvidia 20721664 66 nvidia_modeset ipmi_msghandler 69632 1 nvidia drm_kms_helper 229376 1 nvidia_drm drm 544768 5 drm_kms_helper,nvidia_drm And to be honest, I find this really confusing, as the scripts obviously shoudl load the modules and create the files… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1173854] New: prime-select-bbswitch has non-absolute path to executable and missing items on the blacklist
by bugzilla_noreply＠suse.com 07 Jul '20

07 Jul '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1173854 Bug ID: 1173854 Summary: prime-select-bbswitch has non-absolute path to executable and missing items on the blacklist Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: X11 3rd Party Driver Assignee: gfx-bugs(a)suse.de Reporter: gafernandesil(a)gmail.com QA Contact: sndirsch(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0 Build Identifier: The package prime-select-bbswitch install a service prime-select.service at /usr/lib/systemd/system/prime-select.service . This service has a wrong path to the executable. The full path to prime-select must be given in order for the service to work: ExecStart=/usr/sbin/prime-select systemd_call This is fixed on the version 0.7.12 of prime-select-bbswitch and prime-select: https://github.com/openSUSE/SUSEPrime Also some kernel modules were missing also fixed in the version 0.7.12. Reproducible: Always Steps to Reproduce: 1.zypper in suse-prime-bbswitch 2.systemctl reboot 3.systemctl status prime-select Actual Results: Exec Error: Executable path is not absolute This error also can be found in the journalctl. It is not possible to choose the driver. Expected Results: prime-select should load correctly and be able to change the graphics driver. If with bbswitch, turn off the Nvidia card when Intel is selected. The version 0.7.12 of suse-prime works correctly. Tested on GTX 960 with G05 Nvidia drivers. -- You are receiving this mail because: You are on the CC list for the bug.

1 2