December 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1156895] New: autofs.conf disallow browsing of automounted directories per default
by bugzilla_noreply＠novell.com 04 Dec '19

04 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=1156895 Bug ID: 1156895 Summary: autofs.conf disallow browsing of automounted directories per default Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: ralf.bueker(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- running autofs on a openSuse 15.1 System leads to frustration, cause the directories are mounted unbrowsable. To verify: rpm2cpio autofs-5.1.3-lp151.7.2.x86_64.rpm | cpio -iv --to-stdout ./etc/autofs.conf > ./autofs.conf # less autofs.conf | grep browse_mode # browse_mode - maps are browsable by default. browse_mode = no the default value has been changed in the autofs.conf, which we provide with openSUSE. That leads to a lot of irritation and shoud be changed. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1131960] pptp Error: either "to" is duplicate, or "uid" is a garbage.
by bugzilla_noreply＠novell.com 04 Dec '19

04 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=1131960 http://bugzilla.suse.com/show_bug.cgi?id=1131960#c2 --- Comment #2 from Swamp Workflow Management <swamp(a)suse.de> --- This is an autogenerated message for OBS integration: This bug (1131960) was mentioned in https://build.opensuse.org/request/show/754108 Factory / pptp -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1155836] sporadic workqueue lockups in sound_hda_core
by bugzilla_noreply＠novell.com 04 Dec '19

04 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=1155836 http://bugzilla.suse.com/show_bug.cgi?id=1155836#c23 --- Comment #23 from Markus Koßmann <markus.kossmann(a)gmx.de> --- (In reply to Takashi Iwai from comment #22) > Well, the question is how often (and reliably) you can reproduce this issue. > Unfortunately I can't reproduce it reliably. And currently it is rare. Last time on Nov.21. But generally maybe one time a week ( would be about 15 boots). Maybe lots of reboots shows the problem reliably. But I haven't tried that yet. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1131960] pptp Error: either "to" is duplicate, or "uid" is a garbage.
by bugzilla_noreply＠novell.com 04 Dec '19

04 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=1131960 http://bugzilla.suse.com/show_bug.cgi?id=1131960#c1 Reinhard Max <max(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Reinhard Max <max(a)suse.com> --- Package update submitted to Factory. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1158288] New: virtualbox fails to build with Python 3.8
by bugzilla_noreply＠novell.com 04 Dec '19

04 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=1158288 Bug ID: 1158288 Summary: virtualbox fails to build with Python 3.8 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: virt-bugs(a)suse.de Reporter: mcepl(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- https://build.opensuse.org/package/show/openSUSE:Factory:Staging:A/virtualb… Fails immediately in ./configure run: [ 128s] Checking for Python support: [ 128s] ** Python not found! [ 128s] Check /home/abuild/rpmbuild/BUILD/VirtualBox-6.0.14/configure.log for details -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1137688] yast2 tune: store sysrq setting in /etc/sysctl.d/
by bugzilla_noreply＠novell.com 04 Dec '19

04 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=1137688 Imobach Gonzalez Sosa <igonzalezsosa(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(sb56637(a)gmail.com | |) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1137688] yast2 tune: store sysrq setting in /etc/sysctl.d/
by bugzilla_noreply＠novell.com 04 Dec '19

04 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=1137688 http://bugzilla.suse.com/show_bug.cgi?id=1137688#c11 Imobach Gonzalez Sosa <igonzalezsosa(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |igonzalezsosa(a)suse.com --- Comment #11 from Imobach Gonzalez Sosa <igonzalezsosa(a)suse.com> --- Could you set the parameter (using the YaST2 system settings again) and tell us the content of `/etc/sysctl.d/30-yast.conf`? It should contain "kernel.sysrq = 1". If it is still set to 184 after reboot, it might happen that the YaST value is being overridden. Please, check sysctl.d(5) and systctl.conf(5) for more information about which files are read (and in which order). PS: the 30-yast.conf will be (automatically) moved to 70-yast.conf in the future. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1143959] Reduce kernel firmware file installations
by bugzilla_noreply＠novell.com 04 Dec '19

04 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=1143959 http://bugzilla.suse.com/show_bug.cgi?id=1143959#c10 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|tiwai(a)suse.com |shundhammer(a)suse.com --- Comment #10 from Takashi Iwai <tiwai(a)suse.com> --- As the fix for kernel-default-base is done, the rest is about the handling of Recommends:kernel-firmware in kernel-default.rpm. And from now on, I'd toss this to YaST guys, who have a better idea about installation. Reassigned to Stefan for now, but feel free to push back if inappropriate. As discussed earlier, we may move the recommends into patterns, or implement something in YaST, so that user can choose the optimized for the current hardware or comprehensive / safe with all files. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1155836] sporadic workqueue lockups in sound_hda_core
by bugzilla_noreply＠novell.com 04 Dec '19

04 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=1155836 http://bugzilla.suse.com/show_bug.cgi?id=1155836#c22 --- Comment #22 from Takashi Iwai <tiwai(a)suse.com> --- Well, the question is how often (and reliably) you can reproduce this issue. If this is really a bug remaining in CA0132 HD-audio driver, I have some experimental patch to play with and can build a test kernel package on top of the latest 5.4.y stable branch. But it's hard to reproduce, it won't help much. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1155545] [LiveInst] Upgrade from Leap 15.0 using the live upgrade fails
by bugzilla_noreply＠novell.com 04 Dec '19

04 Dec '19

http://bugzilla.suse.com/show_bug.cgi?id=1155545 http://bugzilla.suse.com/show_bug.cgi?id=1155545#c19 --- Comment #19 from Fabian Vogt <fvogt(a)suse.com> --- The way I see it, the live net installer has multiple advantages: * Using this, several bugs in YaST code were found and subsequently fixed * Substantial gain for not much effort * Other distros have installable live CDs, it's what users expect I regularly use it myself for debugging, as having a more complete environment available on the same system is quite valuable. (In reply to Ancor Gonzalez Sosa from comment #18) > 3) Then turns out that, although the YaST team has been trying to help when > possible and reasonable, the whole thing actually does not work as smooth as > expected. > > 4) But instead of fixing the buggy environment (that was the premise, > "difference in environments should be neglegible, anything else is a bug in > the environment") we end up with a bunch of bug reports about thing we have > to adapt in the YaST side for it to work in this new environment. That was > not the deal. Please tell me which bugs in the environment you're talking about here, to my knowledge there aren't any open ones. The only adaption that had to happen AFAIK (but only because of another bug, YaST touching the outside /run), was to ignore wicked setup if NM is running. -- You are receiving this mail because: You are on the CC list for the bug.

1 0