November 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1049661] New: Loglevel in OpenStack image is too verbose
by bugzilla_noreply＠novell.com 11 Jul '19

11 Jul '19

http://bugzilla.suse.com/show_bug.cgi?id=1049661 Bug ID: 1049661 Summary: Loglevel in OpenStack image is too verbose Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: gmoro(a)suse.com Reporter: mnowak(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 733135 --> http://bugzilla.suse.com/attachment.cgi?id=733135&action=edit screenshot of logs on console With OpenStack's image loglevel I get too much messages on console. printk is set to: 7 4 1 7 -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1049659] New: Leap JeOS OpenStack should use XFS file system
by bugzilla_noreply＠novell.com 11 Jul '19

11 Jul '19

http://bugzilla.suse.com/show_bug.cgi?id=1049659 Bug ID: 1049659 Summary: Leap JeOS OpenStack should use XFS file system Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: gmoro(a)suse.com Reporter: mnowak(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 733131 --> http://bugzilla.suse.com/attachment.cgi?id=733131&action=edit df -hT JeOS is using btrfs filesystem, but probably should use XFS (as SLES JeOS does). -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1049651] New: Leap JeOS image on Xen PV should display jeos-firstboot on graphical console
by bugzilla_noreply＠novell.com 11 Jul '19

11 Jul '19

http://bugzilla.suse.com/show_bug.cgi?id=1049651 Bug ID: 1049651 Summary: Leap JeOS image on Xen PV should display jeos-firstboot on graphical console Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: gmoro(a)suse.com Reporter: mnowak(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 733126 --> http://bugzilla.suse.com/attachment.cgi?id=733126&action=edit screenshot of serial console Xen PV image from http://download.opensuse.org/repositories/openSUSE:/Leap:/42.3:/Images/imag… displays jeos-firstboot on serial console, but it should display it on "VNC graphical console" instead. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1049644] New: JeOS Hyper-V image does not have graphical GRUB (bw only)
by bugzilla_noreply＠novell.com 11 Jul '19

11 Jul '19

http://bugzilla.suse.com/show_bug.cgi?id=1049644 Bug ID: 1049644 Summary: JeOS Hyper-V image does not have graphical GRUB (bw only) Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: mnowak(a)suse.com QA Contact: jsrain(a)suse.com CC: gmoro(a)suse.com Found By: --- Blocker: --- Created attachment 733121 --> http://bugzilla.suse.com/attachment.cgi?id=733121&action=edit GRUB screenshot Leap 42.3 Hyper-V JeOS image does not have the green graphical interface, it defaults to black & white one. See attachment. Before GRUB menu appears I can see: error: terminal `gfxterm' isn't found. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1049610] New: hyper-v package is missing from Hyper-V JeOS image
by bugzilla_noreply＠novell.com 11 Jul '19

11 Jul '19

http://bugzilla.suse.com/show_bug.cgi?id=1049610 Bug ID: 1049610 Summary: hyper-v package is missing from Hyper-V JeOS image Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Other Assignee: gmoro(a)suse.com Reporter: mnowak(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1048188 +++ 'hyper-v' package contains Hyper-V specific utils & daemons which communicate with Hyper-V hypervisor and thus should be included in JeOS Hyper-V image. Current images are here: http://download.opensuse.org/repositories/openSUSE:/Leap:/42.3:/Images/imag…. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1047256] New: Boot splash not working on boot and shutdown after update
by bugzilla_noreply＠novell.com 11 Jul '19

11 Jul '19

http://bugzilla.suse.com/show_bug.cgi?id=1047256 Bug ID: 1047256 Summary: Boot splash not working on boot and shutdown after update Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: openSUSE 42.2 Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: mhejpetr(a)mhn.cz QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- I have got PC with Nvidia graphics card installed. This machine was not long time used(from April till today), so after boot I did update and reboot... What was surprising - some bug related to Plymouth, frame buffer(??) arrived with updates from approx. last 3 months. - no animated picture in graphics mode visible during boot - only blank screen with 3 small green boxes in the middle - Nvidia proprietary driver installed on this PC, but it seems it does not depend on this - tested also with Nouveau driver with the same result - it was OK before update - it is OK on several PC's/laptops with Intel graphics adapter - so it seems it is NVidia related problem Similiar problem described also in this discussion: https://forums.opensuse.org/showthread.php/504441-3-green-boxes-with-questi… -- You are receiving this mail because: You are on the CC list for the bug.

1 14

[Bug 1044705] New: Failed to mount openSUSE ISO: Unable to verify that the media was mounted
by bugzilla_noreply＠novell.com 11 Jul '19

11 Jul '19

http://bugzilla.suse.com/show_bug.cgi?id=1044705 Bug ID: 1044705 Summary: Failed to mount openSUSE ISO: Unable to verify that the media was mounted Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: opensuse.lietuviu.kalba(a)gmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 729237 --> http://bugzilla.suse.com/attachment.cgi?id=729237&action=edit y2logs For installation of openSUSE Leap 42.3 beta, I try to use LiveUSB, created with live-grub-stick 0.4.1 Boot medium created successfully, I booted from it, selected openSUSE Leap 42.3 installation option. Installer started, I can select language and confirmed licence. But installer failed to add ISO as main repository: Failed to mount /mounts/mp_0003/openSUSE-Leap-42.3-DVD-x86_64-Build0279-Media.iso on /var/adm/mount/AP_0xSNa59m: Unable to verify that the media was mounted If I press "Retry", I can choose to select hard disk partition as repository, but it is a bit irrelevant, because I need ISO, not directory. Becides, I allows to choose between /dev/sda* and /dev/sdc* partiotions, but ISO is in /dev/sdb1 partition. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1044482] New: Doesn't recognize existing btrfs partitions.
by bugzilla_noreply＠novell.com 11 Jul '19

11 Jul '19

http://bugzilla.suse.com/show_bug.cgi?id=1044482 Bug ID: 1044482 Summary: Doesn't recognize existing btrfs partitions. Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: VMWare OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Upgrade Problems Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: jason.evans(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 729077 --> http://bugzilla.suse.com/attachment.cgi?id=729077&action=edit error Upgrade from SLES 42.2 to 42.3 via ISO. Build 0277. See screenshot. Installer sees existing partitions as "Unknown Linux" When I try to choose any partition for installation: Error No installed system that can be upgraded with this product was found on the selected partition. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1044072] New: Ctrl-Alt-F7 in GNOME session locks the screen with "systemd-logind: got pause for 13:65" in log preventing unlock
by bugzilla_noreply＠novell.com 11 Jul '19

11 Jul '19

http://bugzilla.suse.com/show_bug.cgi?id=1044072 Bug ID: 1044072 Summary: Ctrl-Alt-F7 in GNOME session locks the screen with "systemd-logind: got pause for 13:65" in log preventing unlock Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs(a)forge.provo.novell.com Reporter: mnowak(a)suse.com QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- openQA job https://openqa.opensuse.org/tests/420077/ (and others) fail, because while in X we send ctrl-alt-f7 combination 11:47:48.3106 21526 ||| starting reboot_gnome tests/x11/reboot_gnome.pm at 2017-06-13 11:47:48 11:47:48.3110 Debug: /var/lib/openqa/cache/openqa1-opensuse/tests/opensuse/tests/x11/reboot_gnome.pm:21 called utils::power_action 11:47:48.3111 21526 <<< testapi::select_console(testapi_console='x11') `...............................................^^^^^^^^^^^^^^^^^^^^^ GNOME lock itself and is not reacting to 'esc' key sent repeatedly to unlock the session. Xlog: [ 1558.971] (**) Option "fd" "21" [ 1558.972] (II) event3 - (II) Power Button: (II) device removed [ 1558.972] (**) Option "fd" "24" [ 1558.972] (II) event4 - (II) QEMU QEMU USB Tablet: (II) device removed [ 1558.977] (**) Option "fd" "25" [ 1558.977] (II) event0 - (II) AT Translated Set 2 keyboard: (II) device removed [ 1558.978] (**) Option "fd" "26" [ 1558.978] (II) event2 - (II) VirtualPS/2 VMware VMMouse: (II) device removed [ 1558.978] (**) Option "fd" "27" [ 1558.978] (II) event1 - (II) VirtualPS/2 VMware VMMouse: (II) device removed [ 1558.982] (II) systemd-logind: got pause for 13:65 [ 1558.982] (II) systemd-logind: got pause for 13:66 [ 1558.982] (II) systemd-logind: got pause for 13:64 [ 1558.982] (II) systemd-logind: got pause for 13:68 [ 1558.982] (II) systemd-logind: got pause for 13:67 [ 1558.982] (II) systemd-logind: got pause for 226:0 journal: Jun 13 07:49:42 susetest /usr/lib/gdm/gdm-x-session[14571]: (**) Option "fd" "24" Jun 13 07:49:42 susetest /usr/lib/gdm/gdm-x-session[14571]: (II) event3 - (II) Power Button: (II) device removed Jun 13 07:49:42 susetest /usr/lib/gdm/gdm-x-session[14571]: (**) Option "fd" "23" Jun 13 07:49:42 susetest /usr/lib/gdm/gdm-x-session[14571]: (II) event4 - (II) QEMU QEMU USB Tablet: (II) device removed Jun 13 07:49:42 susetest /usr/lib/gdm/gdm-x-session[14571]: (**) Option "fd" "40" Jun 13 07:49:42 susetest /usr/lib/gdm/gdm-x-session[14571]: (II) event0 - (II) AT Translated Set 2 keyboard: (II) device removed Jun 13 07:49:42 susetest /usr/lib/gdm/gdm-x-session[14571]: (**) Option "fd" "26" Jun 13 07:49:42 susetest /usr/lib/gdm/gdm-x-session[14571]: (II) event2 - (II) VirtualPS/2 VMware VMMouse: (II) device removed Jun 13 07:49:42 susetest /usr/lib/gdm/gdm-x-session[14571]: (**) Option "fd" "25" Jun 13 07:49:42 susetest /usr/lib/gdm/gdm-x-session[14571]: (II) event1 - (II) VirtualPS/2 VMware VMMouse: (II) device removed Jun 13 07:49:42 susetest gnome-shell[14601]: clutter_input_device_get_device_id: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed Jun 13 07:49:42 susetest gnome-shell[14601]: clutter_input_device_get_device_id: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed Jun 13 07:49:42 susetest gnome-shell[14601]: clutter_input_device_get_device_id: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed Jun 13 07:49:42 susetest gnome-shell[14601]: clutter_input_device_get_device_id: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed Jun 13 07:49:42 susetest gnome-shell[14601]: clutter_input_device_get_device_id: assertion 'CLUTTER_IS_INPUT_DEVICE (device)' failed Jun 13 07:49:42 susetest /usr/lib/gdm/gdm-x-session[14571]: (II) systemd-logind: got pause for 13:68 Jun 13 07:49:42 susetest /usr/lib/gdm/gdm-x-session[14571]: (II) systemd-logind: got pause for 13:65 Jun 13 07:49:42 susetest /usr/lib/gdm/gdm-x-session[14571]: (II) systemd-logind: got pause for 226:0 Jun 13 07:49:42 susetest /usr/lib/gdm/gdm-x-session[14571]: (II) systemd-logind: got pause for 13:64 Jun 13 07:49:42 susetest /usr/lib/gdm/gdm-x-session[14571]: (II) systemd-logind: got pause for 13:67 Jun 13 07:49:42 susetest /usr/lib/gdm/gdm-x-session[14571]: (II) systemd-logind: got pause for 13:66 Logs in here: https://openqa.opensuse.org/tests/420077/#downloads. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1043466] New: SSSD couldn't load the configuration database during autoinstallation
by bugzilla_noreply＠novell.com 11 Jul '19

11 Jul '19

http://bugzilla.suse.com/show_bug.cgi?id=1043466 Bug ID: 1043466 Summary: SSSD couldn't load the configuration database during autoinstallation Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: x86-64 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: AutoYaST Assignee: autoyast-maintainers(a)suse.de Reporter: jmader2(a)gmu.edu QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- autoinstallation in Leap 42.3-Build0270, <auth-client> <sssd>yes</sssd> <sssd_conf> ... </sssd_conf> </auth-client> -- Unit sssd.service has begun starting up. Jun 08 12:59:28 linux sssd[973]: SSSD couldn't load the configuration database [2]: No such file or directory. Jun 08 12:59:28 linux systemd[1]: sssd.service: Control process exited, code=exited status=4 /var/log/sssd.log: (Thu Jun 8 12:59:28:803060 2017) [sssd] [confdb_get_domains] (0x0010): No domains configured, fatal error! (Thu Jun 8 12:59:28:803117 2017) [sssd] [get_monitor_config] (0x0010): No domains configured. (Thu Jun 8 12:59:28:803159 2017) [sssd] [main] (0x0020): SSSD couldn't load the configuration database. This didn’t happen during autoinstallation in Leap 42.2. SSSD does eventually get configured and started so after the initial boot, authentications configured through SSSD do work. -- Unit sssd.service has begun starting up. Jun 08 13:00:00 linux sssd[3505]: Starting up Jun 08 13:00:02 linux sssd[be[3530]: Starting up Jun 08 13:00:02 linux sssd[3531]: Starting up Jun 08 13:00:02 linux sssd[3532]: Starting up -- Unit sssd.service has finished starting up. Jun 08 13:05:40 Hostname sssd[3532]: Shutting down -- Unit sssd.service has begun shutting down. Jun 08 13:05:40 Hostname sssd[3531]: Shutting down Jun 08 13:05:40 Hostname sssd[be[3530]: Shutting down -- Unit sssd.service has finished shutting down. Jun 08 13:05:41 Hostname sssd[11594]: Starting up Jun 08 13:05:41 Hostname sssd[be[11595]: Starting up Jun 08 13:05:41 Hostname sssd[11597]: Starting up Jun 08 13:05:41 Hostname sssd[11596]: Starting up -- Unit sssd.service has finished starting up. Could be that <auto-client> isn’t performed before sssd service is started the first time. -- You are receiving this mail because: You are on the CC list for the bug.

1 10