[opensuse-factory] New Tumbleweed snapshot 20170311 released!
Please note that this mail was generated by a script. The described changes are computed based on the x86_64 DVD. The full online repo contains too many changes to be listed here. Please check the known defects of this snapshot before upgrading: https://openqa.opensuse.org/tests/overview?distri=opensuse&groupid=1&version=Tumbleweed&build=20170311 When you reply to report some issues, make sure to change the subject. It is not helpful to keep the release announcement subject in a thread while discussing a specific problem. Packages changed: efibootmgr (0.12 -> 14) gpg2 (2.1.18 -> 2.1.19) grub2 konversation libqb (1.0.1+git20170131.afdff97 -> 1.0.1+git20170306.59eacf0) libvirt (3.0.0 -> 3.1.0) mcelog (1.47 -> 1.48) ntp perl-libwww-perl (6.21 -> 6.22) virglrenderer (0.5.0 -> 0.6.0) virtualbox (5.1.14_k4.10.1_2 -> 5.1.16_k4.10.1_2) vm-install (0.8.60 -> 0.8.61) === Details === ==== efibootmgr ==== Version update (0.12 -> 14) - Update to 14 plus upstream fixes. (fate#322108) (0001-Don-t-use-fshort-wchar-when-building-63.patch, 0002-Remove-extra-const-keywords-gcc-7-gripes-about.patch, 0003-Add-support-for-parsing-optional-data-as-ucs2.patch) - Forward port and refresh SLE patches (efibootmgr-derhat.diff, MARM-sanitize-set_mirror.diff efibootmgr-delete-multiple.diff) - Drop upstreamed patches (efibootmgr-check-boot-order.diff, efibootmgr-fix-efivar-0.24.patch, efibootmgr-fix-usage-of-efi_loadopt_path-again.patch, MARM-add-m-and-M-options.diff, MARM-extend-man-for-M-option.diff, MARM-fix-insufficient-validation-check-of-M-option.diff, MARM-introduce-man-for-m-and-M-option.diff) - Build on all archs. There is no reason not to. (boo#1025520) - Depend on new enough efivar. Build fails otherwise. ==== gpg2 ==== Version update (2.1.18 -> 2.1.19) - GnuPG 2.1.19: * gpg: Print a warning if Tor mode is requested but the Tor daemon is not running. * gpg: New status code DECRYPTION_KEY to print the actual private key used for decryption. * gpgv: New options --log-file and --debug. * gpg-agent: Revamp the prompts to ask for card PINs. * scd: Support for multiple card readers. * scd: Removed option --debug-disable-ticker. Ticker is used only when it is required to watch removal of device/card. * scd: Improved detection of card inserting and removal. * dirmngr: New option --disable-ipv4. * dirmngr: New option --no-use-tor to explicitly disable the use of Tor. * dirmngr: The option --allow-version-check is now required even if the option --use-tor is also used. * dirmngr: Handle a missing nsswitch.conf gracefully. * dirmngr: Avoid PTR lookups for keyserver pools. The are only done for the debug command "keyserver --hosttable". * dirmngr: Rework the internal certificate cache to support classes of certificates. Load system provided certificates on startup. * Add options --tls, --no-crl, and --systrust to the "VALIDATE" command. * dirmngr: Add support for the ntbtls library. * wks: Create mails with a "WKS-Phase" header. Fix detection of Draft-2 mode. * Many other bug fixes and new regression tests. - dirmngr: use system certificate store - Rewrite descriptions ==== grub2 ==== Subpackages: grub2-i386-pc grub2-snapper-plugin grub2-systemd-sleep-plugin grub2-x86_64-efi grub2-x86_64-xen - TPM Support (FATE#315831) * 0001-tpm-Core-TPM-support.patch * 0002-tpm-Measure-kernel-initrd.patch * 0003-tpm-Add-BIOS-boot-measurement.patch * 0004-tpm-Rework-linux-command.patch * 0005-tpm-Rework-linux16-command.patch * 0006-tpm-Measure-kernel-and-initrd-on-BIOS-systems.patch * 0007-tpm-Measure-the-kernel-commandline.patch * 0008-tpm-Measure-commands.patch * 0009-tpm-Measure-multiboot-images-and-modules.patch * 0010-tpm-Fix-boot-when-there-s-no-TPM.patch * 0011-tpm-Fix-build-error.patch * 0012-tpm-Build-tpm-as-module.patch - grub2.spec : Add grub-tpm.efi for Secure Boot - Fix invalid Xen EFI config files if xen_args include GRUB2 quoting (bsc#900418) (bsc#951748) * grub2-efi-xen-cfg-unquote.patch - Fix linuxefi erroneously initialize linux's boot_params with non-zero values. (bsc#1025563) * grub2-linuxefi-fix-boot-params.patch - Removed grub2-fix-multi-device-root-kernel-argument.patch as it has regression on how GRUB_DISABLE_LINUX_UUID=true interpreted (bsc#1015138) ==== konversation ==== Subpackages: konversation-lang - Add upstream patch to fix crash on exit: * fix-crash-on-quit.patch ==== libqb ==== Version update (1.0.1+git20170131.afdff97 -> 1.0.1+git20170306.59eacf0) - loop: Fix splint error - loop: Also set signals changed in qb_loop_signal_mod() back to SIG_DFL (bsc#1026176) - loop: don't override external signal handlers (bsc#1026176) - Upstream version cs: 59eacf07dd92af6917ed351c0c5e51ec5237965c ==== libvirt ==== Version update (3.0.0 -> 3.1.0) Subpackages: libvirt-client libvirt-daemon libvirt-daemon-config-network libvirt-daemon-config-nwfilter libvirt-daemon-driver-interface libvirt-daemon-driver-libxl libvirt-daemon-driver-lxc libvirt-daemon-driver-network libvirt-daemon-driver-nodedev libvirt-daemon-driver-nwfilter libvirt-daemon-driver-qemu libvirt-daemon-driver-secret libvirt-daemon-driver-storage libvirt-daemon-driver-uml libvirt-daemon-driver-vbox libvirt-daemon-lxc libvirt-daemon-qemu libvirt-daemon-xen libvirt-libs - Update to libvirt 3.1.0 - Modularize storage driver by splitting it into backend-specific subpackages - CVE-2017-2635, bsc#1027075 - Many incremental improvements and bug fixes, see http://libvirt.org/news.html - Dropped patches: b018ada3-shunloadtest-build-fix.patch, f86a7a83-libxl-dom0-balloon-fix.patch, 6e4759d0-libxl-timer-fix.patch, 87df87e0-libxl-timer-tsc-emulate.patch, b4386fda-xenconfig-timer-fix.patch, d3970925-timer-tests.patch, 321a28c6-libxl-default-disk-format.patch, bd116810-libxl-fix-disk-detach.patch, ff225538-libxl-autoballoon-setting.patch, c89a6e78-libxl-physinfo-cleanup.patch, d2b77608-libxl-maxmem-fix.patch, 79692c38-libxl-dom0-maxmem.patch, 4ab0c959-libxl-mem-leak.patch, 2dc1cf19-libxl-double-free.patch, apparmor-errormsg-fix.patch, apparmor-alt-seclabel.patch, qemu-disable-namespaces.patch - Drop author list from description. Fix summary to be more accurate as to what the subpackage pertains to. ==== mcelog ==== Version update (1.47 -> 1.48) - Update to version 1.48 * Fix warning with gcc 6.x * Remove obsolete TODO file * Small fixes - Use url for getting sources ==== ntp ==== Subpackages: ntp-doc - Move ntp-kod to /var/lib/ntp/db, because /var/db is not a standard directory and causes problems for transactional updates (ntp-move-kod-file.patch) - Remove 50-ntp.list (bsc#1011919). - Use system-wide libevent instead of local copy. - Simplify ntpd's search for its own executable to prevent AppArmor warnings (bsc#956365, ntp-pathfind.patch). ==== perl-libwww-perl ==== Version update (6.21 -> 6.22) - updated to 6.22 see /usr/share/doc/packages/perl-libwww-perl/Changes 6.22 2017-03-01 - Update Travis-CI to test on minimum versions of prereqs. (GH PR #109) - Fix tests that depended on a newer version of HTTP::Message (GH PR #119) - Update documentation to reflect behavior difference in ->put() depending on the version of HTTP::Message installed. (GH PR #120) ==== virglrenderer ==== Version update (0.5.0 -> 0.6.0) - Fix memory leak in vertex elements state create (CVE-2017-6386 bsc#1027376) 0001-737c3350-renderer-fix-memory-leak-in-vertex-elements-state-cr.patch - Fix RPM groups - Update package to 0.6.0 The following patches will be removed: 0001-48f67f60-renderer-fix-NULL-pointer-deref-in-vrend_clear.patch 0002-40b0e781-renderer-fix-a-leak-in-resource-attach.patch 0003-6eb13f7a-vrend-fix-memory-leak-in-int-blit-context.patch 0004-114688c5-renderer-fix-heap-overflow-in-vertex-elements-state-.patch 0005-926b9b34-vrend-fix-a-stack-overflow-in-set-framebuffer-state.patch All of the removed patches were already included in 0.6.0, So we dont need them any more. ==== virtualbox ==== Version update (5.1.14_k4.10.1_2 -> 5.1.16_k4.10.1_2) Subpackages: virtualbox-guest-kmp-default virtualbox-guest-tools virtualbox-guest-x11 - Removed "vbox_fix_4.10_api_changes.patch" - fixed upstream Removed "vbox_fix_4.11_api_changes.patch" - fixed upstream - Version bump to 5.1.16 (released 2017-03-08 by Oracle) This is a maintenance release. The following items were fixed and/or added: VMM: don't access the MSR_IA32_SMM_MONITOR_CTL MSR if dual-monitor treatment is not available (KVM workaround, bug #14965) VMM: another fix for handling certain MSRs on ancient CPUs without VT-x support for MSR bitmaps VMM: fixed VERR_SSM_LOAD_CPUID_MISMATCH errors when restoring a saved state with SMP guests on hosts without the CPUID/HTT bit set (bug #16428) VMM: fixed a bug in call gate emulation VMM: FWAIT instruction fix VMM: fixed a sporadic guest hang under certain conditions GUI: hide the mini-toolbar from the taskbar and the pager on certain X11 hosts GUI: better error handling on the global settings / network / host-only / DHCP server settings GUI: fixes for full-screen with multiple screens Host-only Network: fixed host-only adapter creation issue preventing VirtualBox installation on Windows 10 hosts (bug #16379) NAT network: fixed two potential crashes in the DHCP server ICH9: fixed incorrect initialization of the primary bus for PCI bridges (5.1.14 regression) Storage: LsiLogic fix for Windows 10 USB: fixed not being able to attach certain USB devices having invalid characters in the device strings (5.0.18 regression; bug #15956) USB: several fixes for the USB/IP support (bug #16462) VBoxSVC: fixed another crash during shutdown under rare circumstances VBoxSVC: fixed a stack overflow on (Windows debug builds only; bug #16409) OVF: when importing an appliance handle more than 10 network adapters if the OVA was created by VirtualBox (bug #16401) OVF: fixes for exporting and importing appliances with many disks (bug #16402) VBoxManage: fixed regression with modifyhd --resize (bug #16311) rdesktop-vrdp: source code tarball fixes Linux Installers: do not rebuild kernel modules unnecessarily (bug #16408) Linux hosts: added an action for opening the VM manager window to the .desktop file Linux hosts / guests: Linux 4.11 compile fixes (bug #16506) Linux Additions: added vboxsf FS modules alias (bug #16404) Linux Additions: fix for the shared folders kernel module to compile on Linux 4.10 Linux Additions: properly install the Linux kernel module override rule on distributions without /etc/depmod.d Windows Additions: fixed a crash with recent Windows 10 builds if 3D is disabled (bug #15973) - Fix API changes for kernel 4.11. This change adds file "vbox_fix_4.11_api_changes.patch". Make some changes to various script files to remove reference to run level 4, which is not used. - Fix for missing global in vboxsf that prevented mounting shared folders for kernel 4.10. This change is the fix for bsc #1027967. ==== vm-install ==== Version update (0.8.60 -> 0.8.61) - bsc#978526 - text mode installation doesn't allow specifying install source (revisited) - Version 0.8.61 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Installed this snapshot and rebooted when it was done. My computer doesn't boot (GRUB works but when kernel 4.10.1-2 is started it immediately reboots, so i.e. a reboot loop). Selecting older kernel 4.10.1-1 does boot, so there's a workaround for now. Asus N53J laptop. On 13-03-17 15:20, Dominique Leuenberger wrote:
Please note that this mail was generated by a script. The described changes are computed based on the x86_64 DVD. The full online repo contains too many changes to be listed here.
Please check the known defects of this snapshot before upgrading: https://openqa.opensuse.org/tests/overview?distri=opensuse&groupid=1&version=Tumbleweed&build=20170311
When you reply to report some issues, make sure to change the subject. It is not helpful to keep the release announcement subject in a thread while discussing a specific problem.
Packages changed: efibootmgr (0.12 -> 14) gpg2 (2.1.18 -> 2.1.19) grub2 konversation libqb (1.0.1+git20170131.afdff97 -> 1.0.1+git20170306.59eacf0) libvirt (3.0.0 -> 3.1.0) mcelog (1.47 -> 1.48) ntp perl-libwww-perl (6.21 -> 6.22) virglrenderer (0.5.0 -> 0.6.0) virtualbox (5.1.14_k4.10.1_2 -> 5.1.16_k4.10.1_2) vm-install (0.8.60 -> 0.8.61)
=== Details ===
==== efibootmgr ==== Version update (0.12 -> 14)
- Update to 14 plus upstream fixes. (fate#322108) (0001-Don-t-use-fshort-wchar-when-building-63.patch, 0002-Remove-extra-const-keywords-gcc-7-gripes-about.patch, 0003-Add-support-for-parsing-optional-data-as-ucs2.patch) - Forward port and refresh SLE patches (efibootmgr-derhat.diff, MARM-sanitize-set_mirror.diff efibootmgr-delete-multiple.diff) - Drop upstreamed patches (efibootmgr-check-boot-order.diff, efibootmgr-fix-efivar-0.24.patch, efibootmgr-fix-usage-of-efi_loadopt_path-again.patch, MARM-add-m-and-M-options.diff, MARM-extend-man-for-M-option.diff, MARM-fix-insufficient-validation-check-of-M-option.diff, MARM-introduce-man-for-m-and-M-option.diff) - Build on all archs. There is no reason not to. (boo#1025520) - Depend on new enough efivar. Build fails otherwise.
==== gpg2 ==== Version update (2.1.18 -> 2.1.19)
- GnuPG 2.1.19: * gpg: Print a warning if Tor mode is requested but the Tor daemon is not running. * gpg: New status code DECRYPTION_KEY to print the actual private key used for decryption. * gpgv: New options --log-file and --debug. * gpg-agent: Revamp the prompts to ask for card PINs. * scd: Support for multiple card readers. * scd: Removed option --debug-disable-ticker. Ticker is used only when it is required to watch removal of device/card. * scd: Improved detection of card inserting and removal. * dirmngr: New option --disable-ipv4. * dirmngr: New option --no-use-tor to explicitly disable the use of Tor. * dirmngr: The option --allow-version-check is now required even if the option --use-tor is also used. * dirmngr: Handle a missing nsswitch.conf gracefully. * dirmngr: Avoid PTR lookups for keyserver pools. The are only done for the debug command "keyserver --hosttable". * dirmngr: Rework the internal certificate cache to support classes of certificates. Load system provided certificates on startup. * Add options --tls, --no-crl, and --systrust to the "VALIDATE" command. * dirmngr: Add support for the ntbtls library. * wks: Create mails with a "WKS-Phase" header. Fix detection of Draft-2 mode. * Many other bug fixes and new regression tests. - dirmngr: use system certificate store - Rewrite descriptions
==== grub2 ==== Subpackages: grub2-i386-pc grub2-snapper-plugin grub2-systemd-sleep-plugin grub2-x86_64-efi grub2-x86_64-xen
- TPM Support (FATE#315831) * 0001-tpm-Core-TPM-support.patch * 0002-tpm-Measure-kernel-initrd.patch * 0003-tpm-Add-BIOS-boot-measurement.patch * 0004-tpm-Rework-linux-command.patch * 0005-tpm-Rework-linux16-command.patch * 0006-tpm-Measure-kernel-and-initrd-on-BIOS-systems.patch * 0007-tpm-Measure-the-kernel-commandline.patch * 0008-tpm-Measure-commands.patch * 0009-tpm-Measure-multiboot-images-and-modules.patch * 0010-tpm-Fix-boot-when-there-s-no-TPM.patch * 0011-tpm-Fix-build-error.patch * 0012-tpm-Build-tpm-as-module.patch - grub2.spec : Add grub-tpm.efi for Secure Boot - Fix invalid Xen EFI config files if xen_args include GRUB2 quoting (bsc#900418) (bsc#951748) * grub2-efi-xen-cfg-unquote.patch - Fix linuxefi erroneously initialize linux's boot_params with non-zero values. (bsc#1025563) * grub2-linuxefi-fix-boot-params.patch - Removed grub2-fix-multi-device-root-kernel-argument.patch as it has regression on how GRUB_DISABLE_LINUX_UUID=true interpreted (bsc#1015138)
==== konversation ==== Subpackages: konversation-lang
- Add upstream patch to fix crash on exit: * fix-crash-on-quit.patch
==== libqb ==== Version update (1.0.1+git20170131.afdff97 -> 1.0.1+git20170306.59eacf0)
- loop: Fix splint error - loop: Also set signals changed in qb_loop_signal_mod() back to SIG_DFL (bsc#1026176) - loop: don't override external signal handlers (bsc#1026176) - Upstream version cs: 59eacf07dd92af6917ed351c0c5e51ec5237965c
==== libvirt ==== Version update (3.0.0 -> 3.1.0) Subpackages: libvirt-client libvirt-daemon libvirt-daemon-config-network libvirt-daemon-config-nwfilter libvirt-daemon-driver-interface libvirt-daemon-driver-libxl libvirt-daemon-driver-lxc libvirt-daemon-driver-network libvirt-daemon-driver-nodedev libvirt-daemon-driver-nwfilter libvirt-daemon-driver-qemu libvirt-daemon-driver-secret libvirt-daemon-driver-storage libvirt-daemon-driver-uml libvirt-daemon-driver-vbox libvirt-daemon-lxc libvirt-daemon-qemu libvirt-daemon-xen libvirt-libs
- Update to libvirt 3.1.0 - Modularize storage driver by splitting it into backend-specific subpackages - CVE-2017-2635, bsc#1027075 - Many incremental improvements and bug fixes, see http://libvirt.org/news.html - Dropped patches: b018ada3-shunloadtest-build-fix.patch, f86a7a83-libxl-dom0-balloon-fix.patch, 6e4759d0-libxl-timer-fix.patch, 87df87e0-libxl-timer-tsc-emulate.patch, b4386fda-xenconfig-timer-fix.patch, d3970925-timer-tests.patch, 321a28c6-libxl-default-disk-format.patch, bd116810-libxl-fix-disk-detach.patch, ff225538-libxl-autoballoon-setting.patch, c89a6e78-libxl-physinfo-cleanup.patch, d2b77608-libxl-maxmem-fix.patch, 79692c38-libxl-dom0-maxmem.patch, 4ab0c959-libxl-mem-leak.patch, 2dc1cf19-libxl-double-free.patch, apparmor-errormsg-fix.patch, apparmor-alt-seclabel.patch, qemu-disable-namespaces.patch - Drop author list from description. Fix summary to be more accurate as to what the subpackage pertains to.
==== mcelog ==== Version update (1.47 -> 1.48)
- Update to version 1.48 * Fix warning with gcc 6.x * Remove obsolete TODO file * Small fixes - Use url for getting sources
==== ntp ==== Subpackages: ntp-doc
- Move ntp-kod to /var/lib/ntp/db, because /var/db is not a standard directory and causes problems for transactional updates (ntp-move-kod-file.patch) - Remove 50-ntp.list (bsc#1011919). - Use system-wide libevent instead of local copy. - Simplify ntpd's search for its own executable to prevent AppArmor warnings (bsc#956365, ntp-pathfind.patch).
==== perl-libwww-perl ==== Version update (6.21 -> 6.22)
- updated to 6.22 see /usr/share/doc/packages/perl-libwww-perl/Changes 6.22 2017-03-01 - Update Travis-CI to test on minimum versions of prereqs. (GH PR #109) - Fix tests that depended on a newer version of HTTP::Message (GH PR #119) - Update documentation to reflect behavior difference in ->put() depending on the version of HTTP::Message installed. (GH PR #120)
==== virglrenderer ==== Version update (0.5.0 -> 0.6.0)
- Fix memory leak in vertex elements state create (CVE-2017-6386 bsc#1027376) 0001-737c3350-renderer-fix-memory-leak-in-vertex-elements-state-cr.patch - Fix RPM groups - Update package to 0.6.0 The following patches will be removed: 0001-48f67f60-renderer-fix-NULL-pointer-deref-in-vrend_clear.patch 0002-40b0e781-renderer-fix-a-leak-in-resource-attach.patch 0003-6eb13f7a-vrend-fix-memory-leak-in-int-blit-context.patch 0004-114688c5-renderer-fix-heap-overflow-in-vertex-elements-state-.patch 0005-926b9b34-vrend-fix-a-stack-overflow-in-set-framebuffer-state.patch All of the removed patches were already included in 0.6.0, So we dont need them any more.
==== virtualbox ==== Version update (5.1.14_k4.10.1_2 -> 5.1.16_k4.10.1_2) Subpackages: virtualbox-guest-kmp-default virtualbox-guest-tools virtualbox-guest-x11
- Removed "vbox_fix_4.10_api_changes.patch" - fixed upstream Removed "vbox_fix_4.11_api_changes.patch" - fixed upstream - Version bump to 5.1.16 (released 2017-03-08 by Oracle) This is a maintenance release. The following items were fixed and/or added: VMM: don't access the MSR_IA32_SMM_MONITOR_CTL MSR if dual-monitor treatment is not available (KVM workaround, bug #14965) VMM: another fix for handling certain MSRs on ancient CPUs without VT-x support for MSR bitmaps VMM: fixed VERR_SSM_LOAD_CPUID_MISMATCH errors when restoring a saved state with SMP guests on hosts without the CPUID/HTT bit set (bug #16428) VMM: fixed a bug in call gate emulation VMM: FWAIT instruction fix VMM: fixed a sporadic guest hang under certain conditions GUI: hide the mini-toolbar from the taskbar and the pager on certain X11 hosts GUI: better error handling on the global settings / network / host-only / DHCP server settings GUI: fixes for full-screen with multiple screens Host-only Network: fixed host-only adapter creation issue preventing VirtualBox installation on Windows 10 hosts (bug #16379) NAT network: fixed two potential crashes in the DHCP server ICH9: fixed incorrect initialization of the primary bus for PCI bridges (5.1.14 regression) Storage: LsiLogic fix for Windows 10 USB: fixed not being able to attach certain USB devices having invalid characters in the device strings (5.0.18 regression; bug #15956) USB: several fixes for the USB/IP support (bug #16462) VBoxSVC: fixed another crash during shutdown under rare circumstances VBoxSVC: fixed a stack overflow on (Windows debug builds only; bug #16409) OVF: when importing an appliance handle more than 10 network adapters if the OVA was created by VirtualBox (bug #16401) OVF: fixes for exporting and importing appliances with many disks (bug #16402) VBoxManage: fixed regression with modifyhd --resize (bug #16311) rdesktop-vrdp: source code tarball fixes Linux Installers: do not rebuild kernel modules unnecessarily (bug #16408) Linux hosts: added an action for opening the VM manager window to the .desktop file Linux hosts / guests: Linux 4.11 compile fixes (bug #16506) Linux Additions: added vboxsf FS modules alias (bug #16404) Linux Additions: fix for the shared folders kernel module to compile on Linux 4.10 Linux Additions: properly install the Linux kernel module override rule on distributions without /etc/depmod.d Windows Additions: fixed a crash with recent Windows 10 builds if 3D is disabled (bug #15973) - Fix API changes for kernel 4.11. This change adds file "vbox_fix_4.11_api_changes.patch". Make some changes to various script files to remove reference to run level 4, which is not used. - Fix for missing global in vboxsf that prevented mounting shared folders for kernel 4.10. This change is the fix for bsc #1027967.
==== vm-install ==== Version update (0.8.60 -> 0.8.61)
- bsc#978526 - text mode installation doesn't allow specifying install source (revisited) - Version 0.8.61
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, 2017-03-13 at 22:35 +0100, opensuse@maridonkers.info wrote:
Installed this snapshot and rebooted when it was done.
My computer doesn't boot (GRUB works but when kernel 4.10.1-2 is started it immediately reboots, so i.e. a reboot loop).
Selecting older kernel 4.10.1-1 does boot, so there's a workaround for now.
Asus N53J laptop.
please file a bug for this! It would be great to get some experts looking at the cause. Strangely enough, the last kernel update was in snapshot 0310 - not 0311; did you happen to skip that one? Cheers, Dominique
Noticed that (kernel not updated in latest snapshot) too when reverting latest update via snapper. BTW: reverting doesn't help (4.10.1-2 remains unbootable). But I did run the revert under kernel 4.10.1-1, which I booted as a workardound. That may have been unwise... My logs appear to show that I didn't skip 310 and even rebooted after it was installed:
zypper history: 2017-03-12 12:35:17|install|openSUSE-release|20170310-1.2|x86_64||download.opensuse.org-oss|d716b90a7d7dec55c1fecf2 69fc3144a33b7139e
last log: reboot system boot 4.10.1-2-default Sun Mar 12 13:07 - 22:26 (1+09:18)
So apparently I've installed 20170310-1.2 snapshot at 2017-03-12 12:35:17 and rebooted when it was done installing at Sun Mar 12 13:07. Hence kernel 4.10.1-2 did boot initially but got corrupted by latest update? I noticed that grub2 and efibootmgr got updated. I'll attempt to file a bug for this. On 13-03-17 22:47, Dimstar / Dominique Leuenberger wrote:
Installed this snapshot and rebooted when it was done.
My computer doesn't boot (GRUB works but when kernel 4.10.1-2 is started it immediately reboots, so i.e. a reboot loop).
Selecting older kernel 4.10.1-1 does boot, so there's a workaround for now.
Asus N53J laptop.
On Mon, 2017-03-13 at 22:35 +0100, opensuse@maridonkers.info wrote: please file a bug for this! It would be great to get some experts looking at the cause.
Strangely enough, the last kernel update was in snapshot 0310 - not 0311; did you happen to skip that one?
Cheers, Dominique
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
opensuse@maridonkers.info composed on 2017-03-13 23:10 (UTC+0100):
Dimstar / Dominique Leuenberger wrote:
On Mon, 2017-03-13 at 22:35 +0100, opensuse@maridonkers.info wrote:
Installed this snapshot and rebooted when it was done.
My computer doesn't boot (GRUB works but when kernel 4.10.1-2 is started it immediately reboots, so i.e. a reboot loop).
Selecting older kernel 4.10.1-1 does boot, so there's a workaround for now.
Asus N53J laptop.
If the online review at http://www.expertreviews.co.uk/laptops/50200/asus-n53j-review is a match, that's GeForce GT425M.
please file a bug for this! It would be great to get some experts looking at the cause.
Strangely enough, the last kernel update was in snapshot 0310 - not 0311; did you happen to skip that one?
Noticed that (kernel not updated in latest snapshot) too when reverting latest update via snapper. BTW: reverting doesn't help (4.10.1-2 remains unbootable). But I did run the revert under kernel 4.10.1-1, which I booted as a workardound. That may have been unwise...
My logs appear to show that I didn't skip 310 and even rebooted after it was installed:
zypper history: 2017-03-12
12:35:17|install|openSUSE-release|20170310-1.2|x86_64||download.opensuse.org-oss|d716b90a7d7dec55c1fecf2
69fc3144a33b7139e
last log: reboot system boot 4.10.1-2-default Sun Mar 12 13:07 - 22:26 (1+09:18)
So apparently I've installed 20170310-1.2 snapshot at 2017-03-12 12:35:17 and rebooted when it was done installing at Sun Mar 12 13:07. Hence kernel 4.10.1-2 did boot initially but got corrupted by latest update? I noticed that grub2 and efibootmgr got updated.
I'll attempt to file a bug for this.
I just did an update to TW 20170311 and 4.10.1-2.1 on host big31 with GT218 GeForce 210 (less than a year older than yours). It's working normally with modeset(0) Xorg driver. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
GeForce GT 335M in mine (think there were several models, mine quite old already). Also it has Intel Video on chip (it can use both cards, NVidia Optimus technology; I primarily use the Intel i915 driver, with bumblebee installed for NVidia but never tried to use it). But most likely not a graphics issue because my system reboots *immediately* after the kernel is selected in GRUB (or the timeout occurs). On 14-03-17 00:56, Felix Miata wrote:
opensuse@maridonkers.info composed on 2017-03-13 23:10 (UTC+0100):
Dimstar / Dominique Leuenberger wrote:
On Mon, 2017-03-13 at 22:35 +0100, opensuse@maridonkers.info wrote:
Installed this snapshot and rebooted when it was done.
My computer doesn't boot (GRUB works but when kernel 4.10.1-2 is started it immediately reboots, so i.e. a reboot loop).
Selecting older kernel 4.10.1-1 does boot, so there's a workaround for now.
Asus N53J laptop.
If the online review at http://www.expertreviews.co.uk/laptops/50200/asus-n53j-review is a match, that's GeForce GT425M.
please file a bug for this! It would be great to get some experts looking at the cause.
Strangely enough, the last kernel update was in snapshot 0310 - not 0311; did you happen to skip that one?
Noticed that (kernel not updated in latest snapshot) too when reverting latest update via snapper. BTW: reverting doesn't help (4.10.1-2 remains unbootable). But I did run the revert under kernel 4.10.1-1, which I booted as a workardound. That may have been unwise...
My logs appear to show that I didn't skip 310 and even rebooted after it was installed:
zypper history: 2017-03-12
12:35:17|install|openSUSE-release|20170310-1.2|x86_64||download.opensuse.org-oss|d716b90a7d7dec55c1fecf2
69fc3144a33b7139e
last log: reboot system boot 4.10.1-2-default Sun Mar 12 13:07 - 22:26 (1+09:18)
So apparently I've installed 20170310-1.2 snapshot at 2017-03-12 12:35:17 and rebooted when it was done installing at Sun Mar 12 13:07. Hence kernel 4.10.1-2 did boot initially but got corrupted by latest update? I noticed that grub2 and efibootmgr got updated.
I'll attempt to file a bug for this.
I just did an update to TW 20170311 and 4.10.1-2.1 on host big31 with GT218 GeForce 210 (less than a year older than yours). It's working normally with modeset(0) Xorg driver.
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Have filed bug 1029267 ( https://bugzilla.opensuse.org/show_bug.cgi?id=1029267 ) Thanks for the pointers. Cheers, Mari On 13-03-17 22:47, Dimstar / Dominique Leuenberger wrote:
Installed this snapshot and rebooted when it was done.
My computer doesn't boot (GRUB works but when kernel 4.10.1-2 is started it immediately reboots, so i.e. a reboot loop).
Selecting older kernel 4.10.1-1 does boot, so there's a workaround for now.
Asus N53J laptop.
On Mon, 2017-03-13 at 22:35 +0100, opensuse@maridonkers.info wrote: please file a bug for this! It would be great to get some experts looking at the cause.
Strangely enough, the last kernel update was in snapshot 0310 - not 0311; did you happen to skip that one?
Cheers, Dominique
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
BTW: tried a recovery mode boot of kernel 4.10.1-2 and it boots normally! It boots and continues until my KDE login screen appears. I can login normally. Now I'm puzzled about the difference between a regular boot and a recovery boot. (Typing this from recovery boot.) On 14-03-17 09:28, opensuse@maridonkers.info wrote:
Have filed bug 1029267 ( https://bugzilla.opensuse.org/show_bug.cgi?id=1029267 )
Thanks for the pointers.
Cheers, Mari
On 13-03-17 22:47, Dimstar / Dominique Leuenberger wrote:
Installed this snapshot and rebooted when it was done.
My computer doesn't boot (GRUB works but when kernel 4.10.1-2 is started it immediately reboots, so i.e. a reboot loop).
Selecting older kernel 4.10.1-1 does boot, so there's a workaround for now.
Asus N53J laptop.
On Mon, 2017-03-13 at 22:35 +0100, opensuse@maridonkers.info wrote: please file a bug for this! It would be great to get some experts looking at the cause.
Strangely enough, the last kernel update was in snapshot 0310 - not 0311; did you happen to skip that one?
Cheers, Dominique
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Have closed bug 1029267 ( https://bugzilla.opensuse.org/show_bug.cgi?id=1029267 ) because the problem no longer occurs (a recovery reboot and subsequent reinstall of the latest update appears to have fixed it). Thanks for the feedback and pointers. On 14-03-17 09:42, opensuse@maridonkers.info wrote:
BTW: tried a recovery mode boot of kernel 4.10.1-2 and it boots normally!
It boots and continues until my KDE login screen appears. I can login normally. Now I'm puzzled about the difference between a regular boot and a recovery boot. (Typing this from recovery boot.)
On 14-03-17 09:28, opensuse@maridonkers.info wrote:
Have filed bug 1029267 ( https://bugzilla.opensuse.org/show_bug.cgi?id=1029267 )
Thanks for the pointers.
Cheers, Mari
On 13-03-17 22:47, Dimstar / Dominique Leuenberger wrote:
Installed this snapshot and rebooted when it was done.
My computer doesn't boot (GRUB works but when kernel 4.10.1-2 is started it immediately reboots, so i.e. a reboot loop).
Selecting older kernel 4.10.1-1 does boot, so there's a workaround for now.
Asus N53J laptop.
On Mon, 2017-03-13 at 22:35 +0100, opensuse@maridonkers.info wrote: please file a bug for this! It would be great to get some experts looking at the cause.
Strangely enough, the last kernel update was in snapshot 0310 - not 0311; did you happen to skip that one?
Cheers, Dominique
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 03/13/2017 05:47 PM, Dimstar / Dominique Leuenberger wrote:
Installed this snapshot and rebooted when it was done.
My computer doesn't boot (GRUB works but when kernel 4.10.1-2 is started it immediately reboots, so i.e. a reboot loop).
Selecting older kernel 4.10.1-1 does boot, so there's a workaround for now.
Asus N53J laptop.
On Mon, 2017-03-13 at 22:35 +0100, opensuse@maridonkers.info wrote: please file a bug for this! It would be great to get some experts looking at the cause.
Strangely enough, the last kernel update was in snapshot 0310 - not 0311; did you happen to skip that one?
My understanding is when using zypper dup it's impossible to skip an update as all new updates include previous updated packages. Am I wrong in this thinking? -- Ken Schneider -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue, 2017-03-14 at 10:00 -0400, Ken Schneider - Factory wrote:
Strangely enough, the last kernel update was in snapshot 0310 - not
0311; did you happen to skip that one?
My understanding is when using zypper dup it's impossible to skip an update as all new updates include previous updated packages. Am I wrong in this thinking?
You can easily skip entire snapshots: simply don't call zypper dup: I'd assume this is nothing unusual (even I do not dup my machine daily) One could also skip single packages (by adding locks). Cheers Dominique -- Dimstar / Dominique Leuenberger <dimstar@opensuse.org>
On 03/14/2017 03:08 PM, Dimstar / Dominique Leuenberger wrote:
On Tue, 2017-03-14 at 10:00 -0400, Ken Schneider - Factory wrote:
Strangely enough, the last kernel update was in snapshot 0310 - not
0311; did you happen to skip that one?
My understanding is when using zypper dup it's impossible to skip an update as all new updates include previous updated packages. Am I wrong in this thinking?
You can easily skip entire snapshots: simply don't call zypper dup: I'd assume this is nothing unusual (even I do not dup my machine daily)
I think Ken wanted to say that "skipping snapshots" just means "not running 'zypper dup'" for some time ... but that you'll still get the accumulated package updates from the "skipped" snapshot(s) the next time you do it again, of course. Have a nice day, Berny -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 03/14/2017 10:36 AM, Bernhard Voelker wrote:
On Tue, 2017-03-14 at 10:00 -0400, Ken Schneider - Factory wrote:
Strangely enough, the last kernel update was in snapshot 0310 - not
0311; did you happen to skip that one? My understanding is when using zypper dup it's impossible to skip an update as all new updates include previous updated packages. Am I wrong in this thinking? You can easily skip entire snapshots: simply don't call zypper dup: I'd assume this is nothing unusual (even I do not dup my machine daily) I think Ken wanted to say that "skipping snapshots" just means "not running 'zypper dup'" for some time ... but that you'll still get the accumulated package updates from the "skipped" snapshot(s)
On 03/14/2017 03:08 PM, Dimstar / Dominique Leuenberger wrote: the next time you do it again, of course.
Have a nice day, Berny
Exactly, much simpler wording then my drawn out reply. Thanks -- Ken Schneider -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 03/14/2017 10:08 AM, Dimstar / Dominique Leuenberger wrote:
On Tue, 2017-03-14 at 10:00 -0400, Ken Schneider - Factory wrote:
Strangely enough, the last kernel update was in snapshot 0310 - not
0311; did you happen to skip that one? My understanding is when using zypper dup it's impossible to skip an update as all new updates include previous updated packages. Am I wrong in this thinking? You can easily skip entire snapshots: simply don't call zypper dup: I'd assume this is nothing unusual (even I do not dup my machine daily)
Yes, I routinely skip some snapshots but once I upgrade to the latest all of the new updates from previous snapshots are included in the latest snapshot. As an hypothetical example: latest installed snapshot 0228 has kernel 4.9 snapshot 0305 has kernel 4.10 and also 50 other updates (I read on the list that are issues with 4.10 for certain CPU's, which I have. I elect to not install 0305). snapshot 0310 has kernel 4.10.1 which fixes issue with my CPU. I elect to upgrade to snapshot 0310 which has the fixed kernel but also has updates for the 50 packages that were introduced in 0305 that were included in 0305. Therefore just because I skipped 0305 and went straight to 0310 from 0228 doesn't mean I also skip the 50 updates introduced in 0305 Is my logic right or wrong?
One could also skip single packages (by adding locks).
Yes I use this method for specific packages, I'm currently using it for the kernel packages. -- Ken Schneider -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tuesday, 14 March 2017 15:37 Ken Schneider - Factory wrote:
Yes, I routinely skip some snapshots but once I upgrade to the latest all of the new updates from previous snapshots are included in the latest snapshot. As an hypothetical example: latest installed snapshot 0228 has kernel 4.9 snapshot 0305 has kernel 4.10 and also 50 other updates (I read on the list that are issues with 4.10 for certain CPU's, which I have. I elect to not install 0305). snapshot 0310 has kernel 4.10.1 which fixes issue with my CPU. I elect to upgrade to snapshot 0310 which has the fixed kernel but also has updates for the 50 packages that were introduced in 0305 that were included in 0305. Therefore just because I skipped 0305 and went straight to 0310 from 0228 doesn't mean I also skip the 50 updates introduced in 0305 Is my logic right or wrong?
You are right. What Dimstar wanted to say was that last time kernel was updated was 0310, not 0311, so that if you only noticed the problem (caused by kernel) after updating to 0311 (as you are responding in thread about 0311 snapshot), it should only be possible if you skipped (at least) 0310. Or put in a different way: if an issue only started to appear after updating from 0310 to 0311, it would have to be caused (or triggered) by something else than kernel update (because there was none between those two). It's a common technique when investigating a regression: you want to minimize the interval between last known good state and first known broken one. Michal Kubeček -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 03/15/2017 02:42 AM, Michal Kubecek wrote:
On Tuesday, 14 March 2017 15:37 Ken Schneider - Factory wrote:
Yes, I routinely skip some snapshots but once I upgrade to the latest all of the new updates from previous snapshots are included in the latest snapshot.
You missed this line:
As an hypothetical example:
As in all made up release numbers not meant to relate to actual release numbers. :-) -- Ken Schneider -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am Montag, 13. März 2017, 22:35:51 CET schrieb opensuse@maridonkers.info:
Installed this snapshot and rebooted when it was done.
My computer doesn't boot (GRUB works but when kernel 4.10.1-2 is started it immediately reboots, so i.e. a reboot loop).
Selecting older kernel 4.10.1-1 does boot, so there's a workaround for now.
Asus N53J laptop.
.... May be, same to me. Quiet old Asus X72V Laptop with two SSDs in it. Running boot massages till ... --- a Startjob ist running diskbyid-*********** -counting sekonds /till no limit. On sda1 round about two minutes. Then the same with the second partition on sda it counts to about 25 minutes till i broke up. No problem to mount this SSD in an other Linux box. SSD back into the lappie, starting the Kernel before this actual one and every thing is OK. Hopefully - some one is unstanding me -english ist not my native language. :( Havea nic evening Gruß Richard -- Signatur ??? Wenn Du hier eine Signatur siehst ... :o ... lies die Packungsbeilage und frage Deinen Arzt oder Apotheker. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (8)
-
Bernhard Voelker
-
Dimstar / Dominique Leuenberger
-
Dominique Leuenberger
-
Felix Miata
-
Ken Schneider - Factory
-
Michal Kubecek
-
opensuse@maridonkers.info
-
Richard Werth