May 2020 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1171012] New: NIS authentication does not work because ypbind is originating on a non-priviledged port
by bugzilla_noreply＠novell.com 03 May '20

03 May '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1171012 Bug ID: 1171012 Summary: NIS authentication does not work because ypbind is originating on a non-priviledged port Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Critical Priority: P5 - None Component: Network Assignee: screening-team-bugs(a)suse.de Reporter: nanook(a)eskimo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have an OpenSuse Tumbleweed machine as part of an NIS network. Authentication is shared for all users across the network via NIS. A couple of months ago an update to Tumbleweed broke NIS severely. It took me a long time to determine what was wrong but what is happening is that it is originating the connections to the NIS servers using a non-priviledged port, and because of that can not obtain the map passwd.adjunct.byname or byuid, because these maps are available to root users / privileged ports only. I saw another bug that had narrowed this down to a specific library but I can not find it because search here is not working, it hangs indefinitely. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1160706] Display Freeze-Up Problem With nVidia gfxG03 Drivers And OpenSUSE Leap 15.1 KDE Plasma 5.12.8
by bugzilla_noreply＠novell.com 03 May '20

03 May '20

http://bugzilla.suse.com/show_bug.cgi?id=1160706 http://bugzilla.suse.com/show_bug.cgi?id=1160706#c24 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |WONTFIX --- Comment #24 from Stefan Dirsch <sndirsch(a)suse.com> --- Ok. I needed to give up at this point. I suggest to replace your graphics card/machine (nVidia GPU is from 2008!) with a newer one instead. Seriously. Closing... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1169582] New: timezone: Morocco 2020 DST adjustment
by bugzilla_noreply＠novell.com 03 May '20

03 May '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1169582 Bug ID: 1169582 Summary: timezone: Morocco 2020 DST adjustment Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: mcalabkova(a)suse.com Reporter: Andreas.Stieger(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- >From https://www.mmsp.gov.ma/fr/actualites.aspx?id=1940 (translated) The Morocco government decided that "[...] on the holy month of Ramadan, the Kingdom of Morocco will return to legal time of the Kingdom (GMT) by delaying the time by 60 minutes and this on Sunday April 19 at 03:00 in the morning In accordance with article II of the decree n ° 2.18.855 (October 26, 2018) relating to the legal time of the Kingdom, and to the decision of the Head of Government No. 3.25.20 (published on April 13, 2020) concerning the legal time." From https://github.com/eggert/tz/commit/f9aacafa4f15be6e7ff4436164e14d8f08839ac7 > Morocco springs forward on 2020-05-31, not 2020-05-24. > [...] > Morocco's second spring-forward transition in 2020 will be May 31, > not May 24 as predicted earlier. > Adjust future-year predictions to use the first Sunday after the > day after Ramadan, not the first Sunday after Ramadan. https://mm.icann.org/pipermail/tz/2020-April/028939.html This will be reflected in an upcoming version of the time zone database. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1170576] Packagekit extremely slow to search for updates
by bugzilla_noreply＠novell.com 03 May '20

03 May '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1170576 http://bugzilla.opensuse.org/show_bug.cgi?id=1170576#c2 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Andreas.Stieger(a)gmx.de Component|Maintenance |GNOME Assignee|maintenance(a)opensuse.org |gnome-bugs(a)suse.de --- Comment #2 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- Move to gnome Component for Packagekit. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1170811] gpgme: Fails to build with latest gpg-2.2.20
by bugzilla_noreply＠novell.com 03 May '20

03 May '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1170811 http://bugzilla.opensuse.org/show_bug.cgi?id=1170811#c4 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |Andreas.Stieger(a)gmx.de Resolution|--- |FIXED --- Comment #4 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- fixed -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1170972] New: Firefox-Update seems to corrupt Clipboard
by bugzilla_noreply＠novell.com 03 May '20

03 May '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1170972 Bug ID: 1170972 Summary: Firefox-Update seems to corrupt Clipboard Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Windows 10 Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: ik3noob1(a)web.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0 Build Identifier: I'm using Leap 15.1 within VirtualBox. After installing (sorry, patches from November) MozillaFirefox-branding-upstream MozillaFirefox-buildsymbols MozillaFirefox-devel MozillaFirefox-translations-other the clipboard (KDE Plasma 5.12.8) between the Leap-VM and the Host doesn't work anymore (not only using Firefox, always!, e.g. take a snapshot) I only can copy/paste plane text. It does neither depend on VirtualBox Version (5.16 ... current) nor on Host-OS (W7 or W10) Current I locked this patches with zypper Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1171009] New: Some Packages Are Obsolete For Leap 15.2
by bugzilla_noreply＠novell.com 03 May '20

03 May '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1171009 Bug ID: 1171009 Summary: Some Packages Are Obsolete For Leap 15.2 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: 64bit OS: Linux Status: NEW Severity: Enhancement Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: emrecansuster(a)outlook.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi there, I require to the upgrade versions of some packages. First: Some options needs higher version of Glibc. Maybe you would mind upgrade Glibc 2.26 to 2.27 or higher. Secondly: The last version of Bleachbit is 4.0 while Leap 15.2 comes with 2.0. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1170777] New: mycroft plasmoid doesn't work - can't connect or respond to speech
by bugzilla_noreply＠novell.com 03 May '20

03 May '20

http://bugzilla.opensuse.org/show_bug.cgi?id=1170777 Bug ID: 1170777 Summary: mycroft plasmoid doesn't work - can't connect or respond to speech Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: gef_new(a)hotmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Installed package mycroft-plasmoid, expected behavior is to open plasmoid and say "Hey Mycroft, pair my device" and get a 6-digit code to input in my account on website home.mycroft.ai. No response to voice input, for that matter no response to typed input. Investigating, contents of /usr/share/plasma/plasmoids/org.kde.plasma.mycroftplasmoid/contents/code/startservice.sh are as follows: #!/bin/bash cd /home/$USER/mycroft-core/ ./start-mycroft.sh all paplay /usr/share/sounds/freedesktop/stereo/dialog-error.oga However, there's np directory home/gef/mycroft-core, nor any file named start-mycroft.sh anywhere on my system per kfnd. Reviewing the file list for package mycroft-core, I don't see it listed. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1160706] Display Freeze-Up Problem With nVidia gfxG03 Drivers And OpenSUSE Leap 15.1 KDE Plasma 5.12.8
by bugzilla_noreply＠novell.com 03 May '20

03 May '20

http://bugzilla.suse.com/show_bug.cgi?id=1160706 http://bugzilla.suse.com/show_bug.cgi?id=1160706#c23 --- Comment #23 from David Smith <dasmith(a)electronicaidesdesign.com> --- (In reply to Stefan Dirsch from comment #21) > 340.107 driver: > https://www.nvidia.com/de-de/drivers/unix/linux-amd64-display-archive/ > https://www.nvidia.de/Download/driverResults.aspx/135242/de > > Rebuilding RPMs is rather complicated. Please start with manually installing > the driver Well, I ran into a slight problem manually installing the above nvidia-340-107 version driver with openSUSE Leap 15.1 kernel version 4.12.14. 1. I made sure to uninstall the mouveau driver from the system by using the yast software package manager and removing all mouveau software packages that were installed. 2. I even added a "blacklist mouveau" line to the /etc/modprobe.d/50-blacklist.conf file before rebooting the system. 3. At the grub boot loader menu, I highlighted openSUSE Leap 15.1 with kernel 4.12.14 and pressed "E" for edit. Then I moved the cursor down to the line beginning with the word "linux" and pressed the "End" key to move the cursor to the end of the line and entered a space and the number 3 to enter into lever 3 mode. 4. I press function key "F10" to proceed to boot with this kernel 4.12.14 version. 5. I logined as root in text mode and cd /usr/src/nvidia where I had the NVIDIA-Linux-x86_64-340.107.run executable file stored. 6. I typed in sh ./NVIDIA-Linux-x86_64-340-107.run and pressed enter and it showed me the license agreement. After accepting it, then it prompted me to continue, which I did. However, it detected that the nouveau driver was still loaded in the system, which I checked by using lspci | grep VGA and it showed no driver loaded. 7. So I tried typing: nvidia-installer -a --add-this-kernel and pressed the enter key and it started building the kernel and modules until it got to the final process as follows: -> Error. ERROR: Unable to build the NVIDIA kernel module interface. ERROR: Unable to add a precompiled kernel interface for the running kernel. Attached is the nvidia-installer.log file: -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1160706] Display Freeze-Up Problem With nVidia gfxG03 Drivers And OpenSUSE Leap 15.1 KDE Plasma 5.12.8
by bugzilla_noreply＠novell.com 03 May '20

03 May '20

http://bugzilla.suse.com/show_bug.cgi?id=1160706 http://bugzilla.suse.com/show_bug.cgi?id=1160706#c22 --- Comment #22 from David Smith <dasmith(a)electronicaidesdesign.com> --- (In reply to Stefan Dirsch from comment #21) > 340.107 driver: > https://www.nvidia.com/de-de/drivers/unix/linux-amd64-display-archive/ > https://www.nvidia.de/Download/driverResults.aspx/135242/de > > Rebuilding RPMs is rather complicated. Please start with manually installing > the driver Well, I ran into a slight problem manually installing the above nvidia-340-107 version driver with openSUSE Leap 15.1 kernel version 4.12.14. 1. I made sure to uninstall the mouveau driver from the system by using the yast software package manager and removing all mouveau software packages that were installed. 2. I even added a "blacklist mouveau" line to the /etc/modprobe.d/50-blacklist.conf file before rebooting the system. 3. At the grub boot loader menu, I highlighted openSUSE Leap 15.1 with kernel 4.12.14 and pressed "E" for edit. Then I moved the cursor down to the line beginning with the word "linux" and pressed the "End" key to move the cursor to the end of the line and entered a space and the number 3 to enter into lever 3 mode. 4. I press function key "F10" to proceed to boot with this kernel 4.12.14 version. 5. I logined as root in text mode and cd /usr/src/nvidia where I had the NVIDIA-Linux-x86_64-340.107.run executable file stored. 6. I typed in sh ./NVIDIA-Linux-x86_64-340-107.run and pressed enter and it showed me the license agreement. After accepting it, then it prompted me to continue, which I did. However, it detected that the nouveau driver was still loaded in the system, which I checked by using lspci | grep VGA and it showed no driver loaded. 7. So I tried typing: nvidia-installer -a --add-this-kernel and pressed the enter key and it started building the kernel and modules until it got to the final process as follows: -> Error. ERROR: Unable to build the NVIDIA kernel module interface. ERROR: Unable to add a precompiled kernel interface for the running kernel. Attached is the nvidia-installer.log file: -- You are receiving this mail because: You are on the CC list for the bug.

1 0