February 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1123316] YaST2 iSCSI LIO Target does not accept lvm volumes as /dev/vg/lvol for LUN
by bugzilla_noreply＠novell.com 05 Feb '19

05 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1123316 http://bugzilla.suse.com/show_bug.cgi?id=1123316#c3 Stefan Schubert <schubi(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ancor(a)suse.com Flags|needinfo?(iliady(a)yahoo.com) |needinfo?(ancor(a)suse.com) --- Comment #3 from Stefan Schubert <schubi(a)suse.com> --- Ancor I am not a storage expert, but as far I am remembering we have already had some issues/discussion about "naming". Could you please check this ? Thanks ! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1122410] lxqt-sudo does not pass $XAUTHLOCALHOSTNAME
by bugzilla_noreply＠novell.com 05 Feb '19

05 Feb '19

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

1 0

[Bug 423007] zypper: wrapping usage texts
by bugzilla_noreply＠novell.com 05 Feb '19

05 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=423007 http://bugzilla.suse.com/show_bug.cgi?id=423007#c9 --- Comment #9 from Karl Eichwalder <ke(a)suse.com> --- (In reply to Benjamin Zeller from comment #8) > Maybe Michael can say something about that. > We discussed that last week and the outcome was to stick with 100 columns > because terminals are wide enough today. People are different :) And people said the same 10 years ago and even 15 years ago co#132 were quite common. A default xterm still starts with COLUMNS=80. This mean: either stick with the 79/80 characters line length or use long lines (= no line breaks at all, and hope terminals will handle it properly). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1124082] Please add CPU governor setting to YaST Kernel Settings module
by bugzilla_noreply＠novell.com 05 Feb '19

05 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1124082 http://bugzilla.suse.com/show_bug.cgi?id=1124082#c5 Ladislav Slezák <lslezak(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low --- Comment #5 from Ladislav Slezák <lslezak(a)suse.com> --- My comment: I'm not sure if we want to add this feature to YaST. I mean this requirement is really specific and implementing such feature just for few users does not make much sense IMHO. BTW YaST would need to define a systemd service as well, there is no support for something like that in the system. (The IO scheduler is initialized via adding a boot parameter to grub). There is even a document how to write and use that systemd service, see https://www.suse.com/support/kb/doc/?id=7021316. I think that should be enough for most users who need this feature. What we could do is to package that service file directly into the "cpupower" package and allow configuration via some /etc/sysconfig file. (For configuring in YaST you could use the YaST Sysconfig Editor.) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1121067] perl crashes with buffer overflow when running git send-email
by bugzilla_noreply＠novell.com 05 Feb '19

05 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1121067 http://bugzilla.suse.com/show_bug.cgi?id=1121067#c3 Martin Wilck <martin.wilck(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |martin.wilck(a)suse.com --- Comment #3 from Martin Wilck <martin.wilck(a)suse.com> --- FTR, in case others end up here searching for the solution: the package has been renamed. Install perl-Term-ReadLine-Gnu 1.36-1.1 to get the fix. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1120759] perl SIGSEGV with Term::ReadLine call readline()
by bugzilla_noreply＠novell.com 05 Feb '19

05 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1120759 http://bugzilla.suse.com/show_bug.cgi?id=1120759#c12 Martin Wilck <martin.wilck(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |martin.wilck(a)suse.com --- Comment #12 from Martin Wilck <martin.wilck(a)suse.com> --- FTR, in case others end up here searching for the solution: the package has been renamed. Install perl-Term-ReadLine-Gnu 1.36-1.1 to get the fix. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1120747] Unknown symbols listed when loading snd_hda_core
by bugzilla_noreply＠novell.com 05 Feb '19

05 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1120747 http://bugzilla.suse.com/show_bug.cgi?id=1120747#c22 --- Comment #22 from Daniel Molkentin <daniel.molkentin(a)suse.com> --- Ok, feel free to proceed with this bug as you like, but if you want to keep it open, please reassign. If I can lend a hand: any time. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1120747] Unknown symbols listed when loading snd_hda_core
by bugzilla_noreply＠novell.com 05 Feb '19

05 Feb '19

http://bugzilla.suse.com/show_bug.cgi?id=1120747 http://bugzilla.suse.com/show_bug.cgi?id=1120747#c21 --- Comment #21 from Takashi Iwai <tiwai(a)suse.com> --- For this particular bug, maybe not much. I'm going to rethink and cleanup the current sound module loading mechanism, in anyway, but the primary culprit was the superfluous /etc/module-load.d/yast.conf, and this shouldn't happen in normal situations any longer. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1040022] New: CPU fan speed not being reported
by bugzilla_noreply＠novell.com 05 Feb '19

05 Feb '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1040022 Bug ID: 1040022 Summary: CPU fan speed not being reported Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: reg(a)seowebsales.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- As you can see from below the fan speed is always reported as zero. The chip is NCT6791D and the motherboard is Asus X99-E WS. I don't know if this is a related problem or not but the only fan that shows is the CPU fan. There are 4 chassis fans that are not shown. All the speeds show just fine in the BIOS. Fan speed regulation is fine but that's because the BIOS is doing the controlling, as far as I know. > sensors coretemp-isa-0000 Adapter: ISA adapter Package id 0: +54.0°C (high = +87.0°C, crit = +105.0°C) Core 0: +49.0°C (high = +87.0°C, crit = +105.0°C) Core 1: +46.0°C (high = +87.0°C, crit = +105.0°C) Core 2: +50.0°C (high = +87.0°C, crit = +105.0°C) Core 3: +43.0°C (high = +87.0°C, crit = +105.0°C) Core 4: +43.0°C (high = +87.0°C, crit = +105.0°C) Core 5: +46.0°C (high = +87.0°C, crit = +105.0°C) Core 6: +44.0°C (high = +87.0°C, crit = +105.0°C) Core 7: +43.0°C (high = +87.0°C, crit = +105.0°C) radeon-pci-0700 Adapter: PCI adapter temp1: +63.0°C (crit = +120.0°C, hyst = +90.0°C) asus-isa-0000 Adapter: ISA adapter cpu_fan: 0 RPM -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1124088] /bin/dracut-emergency refers to /dev/consoles (with an s)
by bugzilla_noreply＠novell.com 05 Feb '19

05 Feb '19

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

1 0