November 2016 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 907495] New: adding a manual route to a dhcp configured interface results in failed dhcp setup (wicked managed)
by bugzilla_noreply＠novell.com 26 Aug '22

26 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=907495 Bug ID: 907495 Summary: adding a manual route to a dhcp configured interface results in failed dhcp setup (wicked managed) Classification: openSUSE Product: openSUSE 12.3 Version: Final Hardware: Other OS: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: hpj(a)urpla.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When adding a manual route to a dhcp configured eth interface managed by wicked, the dhcp setup fails with a silly message: device enp7s0 failed: "call to org.opensuse.Network.Addrconf.ipv4.static.requestLease failed: General failure" Add a manual route to a dhcp configured interface and restart your system. Be prepared, that this interface will not come up correctly. BTW: the routing editor allows selecting configured interfaces only. The usual order is: setup interface, add route, but you have to confirm the interface setup first, reenter yast network and add the interface based route there after. -- You are receiving this mail because: You are on the CC list for the bug.

2 10

[Bug 992494] New: áÁéÉíÍóÓúÚüÜ cannot be typed in any app using Asturian language and spanish Asturian variant keyboard
by bugzilla_noreply＠novell.com 23 Aug '22

23 Aug '22

http://bugzilla.suse.com/show_bug.cgi?id=992494 Bug ID: 992494 Summary: áÁéÉíÍóÓúÚüÜ cannot be typed in any app using Asturian language and spanish Asturian variant keyboard Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: enolp(a)softastur.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The key combination for typing áÁéÉíÍóÓúÚüÜ does not working, (they appear as aAeEiIoOuUuU), by setting "España - asturianu (ast_ES)" locale and "Asturian (Spain, with bottom-dot H and bottom-dot L)" keyboard layout in any application. However, Ḥḥ, Ḷḷ and Ññ Asturian letters are typed correctly in KDE and GTK applications except Firefox, where all works perfectly. yast2-country package was recently patched because of a similar bug, but updating it, doesn't fix the problem. https://bugzilla.suse.com/show_bug.cgi?id=981008 -- You are receiving this mail because: You are on the CC list for the bug.

2 6

[Bug 938955] New: Desktop selection overridden when installing without recommended packages.
by bugzilla_noreply＠novell.com 23 Aug '22

23 Aug '22

http://bugzilla.suse.com/show_bug.cgi?id=938955 Bug ID: 938955 Summary: Desktop selection overridden when installing without recommended packages. Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: cwh(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Chosing not to install recommnded packages leads to a minimal installation even without xorg and desktop environment although a desktop environment has been selected before. Either the patterns have to be fixed or the no-recommends option should only be allowed for the minimal pattern. -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 948370] New: One-Click-Installer YMP file cannot match group section for Tumbleweed
by bugzilla_noreply＠novell.com 23 Aug '22

23 Aug '22

http://bugzilla.suse.com/show_bug.cgi?id=948370 Bug ID: 948370 Summary: One-Click-Installer YMP file cannot match group section for Tumbleweed Classification: openSUSE Product: openSUSE Factory Version: 2015* Hardware: Other OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: tgoettlicher(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:39.0) Gecko/20100101 Firefox/39.0 Build Identifier: One-Click-Installer YMP files can contain sections for different distribution versions, e.g.: <group distversion="openSUSE 13.2"> You can match against a specific Tumbleweed build: <group distversion="openSUSE 20150924"> But it's not possible to match for Tumbleweed in general because the version of Tumbleweed changes with every build. Can the one-click-installer be extended to not only match against the version but also against the codename? For example: <group distcodename="openSUSE Tumbleweed"> Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

2 2

[Bug 930110] New: yast ncurses menus not properly formatted for tumbleweed ppc64 guest install
by bugzilla_noreply＠novell.com 23 Aug '22

23 Aug '22

http://bugzilla.suse.com/show_bug.cgi?id=930110 Bug ID: 930110 Summary: yast ncurses menus not properly formatted for tumbleweed ppc64 guest install Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: PowerPC-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: normand(a)linux.vnet.ibm.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- yast ncurses menus not properly formatted for tumbleweed ppc64 guest install Detailed flow: * On a Power KVM host I defined a libvirt twppc64.xml using the Tumbleweed-BE-DVD-ppc64-Snapshot20150505-Media.iso retrieved from https://openqa.opensuse.org/tests/60778/asset/3110 * from a ssh session to the PowerKVM I started a screen window from which I started the ppc64 guest. === virsh define twppc64.xml virsh start --console twppc64 === * I captured successively the ncurses menus and did a yast2_ncurse_bad_format.tgz tarball with all those png files. * The first problem is that the text is not properly aligned eg: yast2_img1_installation.png * The 2nd problem is that some characters from previous menu are not cleaned up when new menu is presented. eg: yast2_img4_installation_option.png * The third problem is popup window hardly visible eg: yast2_img9_confirm_password.png -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 980750] New: Plymouth prevents loading DRM/KMS driver for newly installed graphics card
by bugzilla_noreply＠novell.com 22 Aug '22

22 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=980750 Bug ID: 980750 Summary: Plymouth prevents loading DRM/KMS driver for newly installed graphics card Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: All OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: maximilian.staudt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When changing a VGA card in an already installed system, Plymouth will prevent its modern (DRM/KMS) kernel mode driver to be loaded. Example: 1. Install Leap 42.1 in QEMU using the emulated Cirrus card (-vga cirrus). 2. The system boots up with a splash screen. 3. Shut down the system. 4. Start the VM, this time with the Bochs VGA card (-vga std). 5. A splash screen will be shown, but then X falls back to the VESA driver. As a bonus, switching to a text VT (Ctrl-Alt-F1) only gives a blinking cursor. The VT works just fine and is usable, except the user has to operate it blindly as no video is shown. -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1012883] New: System hangs at reboot/shutdown: A stop job is running for User Manager for UID 1000 (1min30)
by bugzilla_noreply＠novell.com 15 Aug '22

15 Aug '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1012883 Bug ID: 1012883 Summary: System hangs at reboot/shutdown: A stop job is running for User Manager for UID 1000 (1min30) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: jeckferson(a)gmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- It's an upstream systemd bug as described in: https://github.com/systemd/systemd/issues/1615 It also manifested in 42.2. -- You are receiving this mail because: You are on the CC list for the bug.

2 28

[Bug 925275] New: NVIDIA Driver not installable
by bugzilla_noreply＠novell.com 15 Jun '22

15 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=925275 Bug ID: 925275 Summary: NVIDIA Driver not installable Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: fbernasek(a)netscape.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 629479 --> http://bugzilla.opensuse.org/attachment.cgi?id=629479&action=edit nvidia driver install log install opensuse tumbleweed 20150329 no problems. after reboot i like to install the NVIDIA-346.47 or 349.12 with booth the same problem can't install the driver. now i update with the kernel from the kernel:stable repositories the same problem. 20150328 the same problem -- You are receiving this mail because: You are on the CC list for the bug.

2 3

[Bug 1004201] New: System hangs during boot due to loop trying to load nvidia modules
by bugzilla_noreply＠novell.com 15 Jun '22

15 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1004201 Bug ID: 1004201 Summary: System hangs during boot due to loop trying to load nvidia modules Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: marcelo.jimenez(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- lspci is: 01:00.0 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 730] (rev a1) Nvidia site explicitly says that the 367.44 driver does support GT 730. In my opinion, there are two problems here: 1 - The system initialization should not loop forever trying to load a module it has already tryed to load and failed 2 - The 367.44 NVIDIA driver should support my hardware. The NVRM messages repeat forever: ... Oct 09 09:17:23 linux-af78 kernel: [drm] Initialized drm 1.1.0 20060810 Oct 09 09:17:23 linux-af78 kernel: nvidia_modeset: module license 'NVIDIA' taints kernel. Oct 09 09:17:23 linux-af78 kernel: Disabling lock debugging due to kernel taint Oct 09 09:17:23 linux-af78 systemd-journal[120]: Journal started Oct 09 09:17:23 linux-af78 kernel: nvidia_modeset: Unknown symbol nvidia_register_module (err 0) Oct 09 09:17:23 linux-af78 kernel: nvidia_modeset: Unknown symbol nvidia_get_rm_ops (err 0) Oct 09 09:17:23 linux-af78 kernel: nvidia_modeset: Unknown symbol nvidia_unregister_module (err 0) Oct 09 09:17:23 linux-af78 systemd[1]: Started Journal Service. ... Oct 09 09:17:31 linux-af78 systemd[1]: Mounting /home... Oct 09 09:17:31 linux-af78 mtp-probe[579]: checking bus 6, device 2: "/sys/devices/pci0000:00/0000:00:1d.2/usb6/6-1" Oct 09 09:17:31 linux-af78 mtp-probe[578]: checking bus 5, device 2: "/sys/devices/pci0000:00/0000:00:1d.1/usb5/5-2" Oct 09 09:17:31 linux-af78 mtp-probe[578]: bus: 5, device: 2 was not an MTP device Oct 09 09:17:31 linux-af78 mtp-probe[579]: bus: 6, device: 2 was not an MTP device Oct 09 09:17:32 linux-af78 kernel: vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem Oct 09 09:17:32 linux-af78 kernel: NVRM: The Unknown NVIDIA G8x Series GPU installed in this NVRM: system is not supported through the 367.44 NVIDIA NVRM: driver. You can try the NVIDIA 340.xx Legacy drivers. NVRM: Please visit http://www.nvidia.com/object/unix.html NVRM: for download information. The 367.44 NVIDIA driver NVRM: will ignore this GPU. Continuing probe... Oct 09 09:17:32 linux-af78 kernel: nvidia: probe of 0000:01:00.0 failed with error -1 Oct 09 09:17:32 linux-af78 kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 246 Oct 09 09:17:32 linux-af78 kernel: NVRM: The NVIDIA probe routine failed for 1 device(s). Oct 09 09:17:32 linux-af78 kernel: NVRM: None of the NVIDIA graphics adapters were initialized! Oct 09 09:17:32 linux-af78 kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 246 Oct 09 09:17:32 linux-af78 kernel: NVRM: NVIDIA init module failed! Oct 09 09:17:32 linux-af78 systemd[1]: Mounted /home. Oct 09 09:17:32 linux-af78 systemd[1]: Starting Local File Systems. Oct 09 09:17:32 linux-af78 systemd[1]: Reached target Local File Systems. Oct 09 09:17:32 linux-af78 systemd[1]: Starting Tell Plymouth To Write Out Runtime Data... Oct 09 09:17:32 linux-af78 systemd[1]: Starting Trigger Flushing of Journal to Persistent Storage... Oct 09 09:17:32 linux-af78 kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) Oct 09 09:17:32 linux-af78 kernel: vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=none,decodes=none:owns=io+mem Oct 09 09:17:32 linux-af78 kernel: NVRM: The Unknown NVIDIA G8x Series GPU installed in this NVRM: system is not supported through the 367.44 NVIDIA NVRM: driver. You can try the NVIDIA 340.xx Legacy drivers. NVRM: Please visit http://www.nvidia.com/object/unix.html NVRM: for download information. The 367.44 NVIDIA driver NVRM: will ignore this GPU. Continuing probe... Oct 09 09:17:32 linux-af78 kernel: nvidia: probe of 0000:01:00.0 failed with error -1 Oct 09 09:17:32 linux-af78 kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 246 Oct 09 09:17:32 linux-af78 kernel: NVRM: The NVIDIA probe routine failed for 1 device(s). Oct 09 09:17:32 linux-af78 kernel: NVRM: None of the NVIDIA graphics adapters were initialized! Oct 09 09:17:32 linux-af78 kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 246 Oct 09 09:17:32 linux-af78 kernel: NVRM: NVIDIA init module failed! Oct 09 09:17:32 linux-af78 kernel: vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=none,decodes=none:owns=io+mem Oct 09 09:17:32 linux-af78 kernel: NVRM: The Unknown NVIDIA G8x Series GPU installed in this NVRM: system is not supported through the 367.44 NVIDIA NVRM: driver. You can try the NVIDIA 340.xx Legacy drivers. NVRM: Please visit http://www.nvidia.com/object/unix.html NVRM: for download information. The 367.44 NVIDIA driver NVRM: will ignore this GPU. Continuing probe... Oct 09 09:17:32 linux-af78 kernel: nvidia: probe of 0000:01:00.0 failed with error -1 Oct 09 09:17:32 linux-af78 kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 246 Oct 09 09:17:32 linux-af78 kernel: NVRM: The NVIDIA probe routine failed for 1 device(s). Oct 09 09:17:32 linux-af78 kernel: NVRM: None of the NVIDIA graphics adapters were initialized! Oct 09 09:17:32 linux-af78 kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 246 Oct 09 09:17:32 linux-af78 kernel: NVRM: NVIDIA init module failed! Oct 09 09:17:32 linux-af78 systemd[1]: Started Tell Plymouth To Write Out Runtime Data. Oct 09 09:17:32 linux-af78 kernel: vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=none,decodes=none:owns=io+mem -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 899330] New: Interfaces does not automatically show up in firewall with NetworkManager
by bugzilla_noreply＠novell.com 05 Jun '22

05 Jun '22

http://bugzilla.opensuse.org/show_bug.cgi?id=899330 Bug ID: 899330 Summary: Interfaces does not automatically show up in firewall with NetworkManager Classification: openSUSE Product: openSUSE Factory Version: 201408* Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: razirazo_90(a)live.com.my QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When using NetworkManager, network interfaces does not listed in firewall. I have to manually configure it using Wicked Service first, to make it registered in firewall. And then use networkManager back. This is troublesome, for example when setting up internet sharing you can't proceed to zone assign and Network masquerade until you do the step above. -- You are receiving this mail because: You are on the CC list for the bug.

2 10