April 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1031334] openhpi fails to build with GCC 7
by bugzilla_noreply＠novell.com 01 Apr '17

01 Apr '17

http://bugzilla.suse.com/show_bug.cgi?id=1031334 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dmacvicar(a)suse.com Assignee|bnc-team-screening(a)forge.pr |kkaempf(a)suse.com |ovo.novell.com | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1031400] Networkmanger does not manage all devices
by bugzilla_noreply＠novell.com 01 Apr '17

01 Apr '17

http://bugzilla.suse.com/show_bug.cgi?id=1031400 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bnc-team-screening(a)forge.pr |os.gnome.maintainers@gmail. |ovo.novell.com |com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1031434] libinput source package not available
by bugzilla_noreply＠novell.com 01 Apr '17

01 Apr '17

http://bugzilla.suse.com/show_bug.cgi?id=1031434 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bnc-team-screening(a)forge.pr |jengelh(a)inai.de |ovo.novell.com | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1031476] lsblk command showing incorrect mount point for btrfs
by bugzilla_noreply＠novell.com 01 Apr '17

01 Apr '17

http://bugzilla.suse.com/show_bug.cgi?id=1031476 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bnc-team-screening(a)forge.pr |sbrabec(a)suse.com |ovo.novell.com | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1031892] New: snapperd in connection with other process consumes 100% CPU
by bugzilla_noreply＠novell.com 01 Apr '17

01 Apr '17

http://bugzilla.suse.com/show_bug.cgi?id=1031892 Bug ID: 1031892 Summary: snapperd in connection with other process consumes 100% CPU Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: hehe_br-opensuse(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 719527 --> http://bugzilla.suse.com/attachment.cgi?id=719527&action=edit hwinfo Hi, I have installed Tumbleweed for a month now, and almost twice a day these process consumes 100% CPU, only the mouse responds for about 10 minutes or more: snapperd brtfs_cleaner brtfs_transacti kworker/u8:x file_baloo It sometimes happens during the login, other times randomly. Even to connect to the tty (CTRL SHIFT f1) to run the command "top" takes about three minutes. Before I was using openSUSE Leap and I had never had a problem with snapper. openSUSE Tumbleweed 20170328 -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1026212] New: Apache doesn't start correctly on boot (very often)
by bugzilla_noreply＠novell.com 01 Apr '17

01 Apr '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1026212 Bug ID: 1026212 Summary: Apache doesn't start correctly on boot (very often) Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Major Priority: P5 - None Component: Apache Assignee: bnc-team-apache(a)forge.provo.novell.com Reporter: studio(a)anchev.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have been experiencing this so many times and I can't find a pattern. The system boots normally but the few sites which I have on the local machine don't load (404). Running 'rcapache2 restart' makes everything work but I can't find why it sometimes happens and based on what factors. Looking at /var/log/apache2/error_log: ------------------------------------- [Sun Feb 19 16:28:30.000427 2017] [:notice] [pid 1767] ModSecurity for Apache/2.9.0 (http://www.modsecurity.org/) configured. [Sun Feb 19 16:28:30.469773 2017] [:notice] [pid 1767] ModSecurity: APR compiled version="1.5.1"; loaded version="1.5.1" [Sun Feb 19 16:28:30.469792 2017] [:notice] [pid 1767] ModSecurity: PCRE compiled version="8.33 "; loaded version="8.39 2016-06-14" [Sun Feb 19 16:28:30.469798 2017] [:warn] [pid 1767] ModSecurity: Loaded PCRE do not match with compiled! [Sun Feb 19 16:28:30.469802 2017] [:notice] [pid 1767] ModSecurity: LUA compiled version="Lua 5.2" [Sun Feb 19 16:28:30.469807 2017] [:notice] [pid 1767] ModSecurity: LIBXML compiled version="2.9.1" [Sun Feb 19 16:28:30.469811 2017] [:notice] [pid 1767] ModSecurity: Status engine is currently disabled, enable it by set SecStatusEngine to On. [Sun Feb 19 16:28:30.495914 2017] [core:error] [pid 1767] (EAI 2)Name or service not known: AH00547: Could not resolve host name site1.local -- ignoring! [Sun Feb 19 16:28:30.495979 2017] [core:error] [pid 1767] (EAI 2)Name or service not known: AH00547: Could not resolve host name site2.local -- ignoring! [Sun Feb 19 16:28:30.496037 2017] [core:error] [pid 1767] (EAI 2)Name or service not known: AH00547: Could not resolve host name site3.local -- ignoring! [Sun Feb 19 16:28:31.018255 2017] [mpm_prefork:notice] [pid 1767] AH00163: Apache/2.4.16 (Linux/SUSE) OpenSSL/1.0.1i-fips configured -- resuming normal operations [Sun Feb 19 16:28:31.018285 2017] [core:notice] [pid 1767] AH00094: Command line: '/usr/sbin/httpd-prefork -f /etc/apache2/httpd.conf -D SYSCONFIG -D SSL -C PidFile /var/run/httpd.pid -C Include /etc/apache2/sysconfig.d/ -D SYSTEMD -D FOREGROUND' ------------------------------------- I ran 'rcapache2 restart' and in the same log I see: ------------------------------------- [Sun Feb 19 16:33:38.465418 2017] [mpm_prefork:notice] [pid 1767] AH00170: caught SIGWINCH, shutting down gracefully [Sun Feb 19 16:33:39.000468 2017] [:notice] [pid 3473] ModSecurity for Apache/2.9.0 (http://www.modsecurity.org/) configured. [Sun Feb 19 16:33:39.000561 2017] [:notice] [pid 3473] ModSecurity: APR compiled version="1.5.1"; loaded version="1.5.1" [Sun Feb 19 16:33:39.000568 2017] [:notice] [pid 3473] ModSecurity: PCRE compiled version="8.33 "; loaded version="8.39 2016-06-14" [Sun Feb 19 16:33:39.000572 2017] [:warn] [pid 3473] ModSecurity: Loaded PCRE do not match with compiled! [Sun Feb 19 16:33:39.000575 2017] [:notice] [pid 3473] ModSecurity: LUA compiled version="Lua 5.2" [Sun Feb 19 16:33:39.000579 2017] [:notice] [pid 3473] ModSecurity: LIBXML compiled version="2.9.1" [Sun Feb 19 16:33:39.000582 2017] [:notice] [pid 3473] ModSecurity: Status engine is currently disabled, enable it by set SecStatusEngine to On. [Sun Feb 19 16:33:40.013885 2017] [mpm_prefork:notice] [pid 3473] AH00163: Apache/2.4.16 (Linux/SUSE) OpenSSL/1.0.1i-fips configured -- resuming normal operations [Sun Feb 19 16:33:40.013934 2017] [core:notice] [pid 3473] AH00094: Command line: '/usr/sbin/httpd-prefork -f /etc/apache2/httpd.conf -D SYSCONFIG -D SSL -C PidFile /var/run/httpd.pid -C Include /etc/apache2/sysconfig.d/ -D SYSTEMD -D FOREGROUND' [Sun Feb 19 16:33:45.022714 2017] [core:notice] [pid 3473] AH00052: child pid 3485 exit signal Segmentation fault (11) [Sun Feb 19 16:33:47.024813 2017] [core:notice] [pid 3473] AH00052: child pid 3486 exit signal Segmentation fault (11) [Sun Feb 19 16:33:52.029721 2017] [core:notice] [pid 3473] AH00052: child pid 3481 exit signal Segmentation fault (11) [Sun Feb 19 16:34:16.054527 2017] [core:notice] [pid 3473] AH00052: child pid 3505 exit signal Segmentation fault (11) [Sun Feb 19 16:34:17.056118 2017] [core:notice] [pid 3473] AH00052: child pid 3501 exit signal Segmentation fault (11) [Sun Feb 19 16:34:17.056145 2017] [core:notice] [pid 3473] AH00052: child pid 3502 exit signal Segmentation fault (11) [Sun Feb 19 16:36:13.176170 2017] [core:notice] [pid 3473] AH00052: child pid 3508 exit signal Segmentation fault (11) [Sun Feb 19 16:36:28.191208 2017] [core:notice] [pid 3473] AH00052: child pid 3506 exit signal Segmentation fault (11) [Sun Feb 19 16:36:28.191241 2017] [core:notice] [pid 3473] AH00052: child pid 3507 exit signal Segmentation fault (11) [Sun Feb 19 16:36:38.201731 2017] [core:notice] [pid 3473] AH00052: child pid 3617 exit signal Segmentation fault (11) [Sun Feb 19 16:36:40.204770 2017] [core:notice] [pid 3473] AH00052: child pid 3620 exit signal Segmentation fault (11) [Sun Feb 19 16:36:41.207193 2017] [core:notice] [pid 3473] AH00052: child pid 3621 exit signal Segmentation fault (11) [Sun Feb 19 16:36:51.219528 2017] [core:notice] [pid 3473] AH00052: child pid 3555 exit signal Segmentation fault (11) [Sun Feb 19 16:36:54.222686 2017] [core:notice] [pid 3473] AH00052: child pid 3480 exit signal Segmentation fault (11) [Sun Feb 19 16:36:54.222723 2017] [core:notice] [pid 3473] AH00052: child pid 3489 exit signal Segmentation fault (11) [Sun Feb 19 16:37:13.241850 2017] [core:notice] [pid 3473] AH00052: child pid 3642 exit signal Segmentation fault (11) ------------------------------------- and after that everything works as expected. All the HDD and SSD drives on the system are healthy. site1.local, site2.local and site3.local are properly configured in /etc/hosts and point to 127.0.0.1 When this happens I notice that Apache starts before wicked: ------------------------------------- [~]: systemd-analyze blame 6.767s nut-driver.service 2.222s apache2.service 2.124s mysql.service 2.027s wicked.service 1.353s ModemManager.service 1.292s SuSEfirewall2_init.service 302ms php-fpm.service 275ms avahi-daemon.service 266ms libvirtd.service 242ms SuSEfirewall2.service ... ------------------------------------- But this is strange considering that the service says the unit should start after network.target: ------------------------------------- cat /usr/lib/systemd/system/apache2* [Unit] Description=The Apache Webserver After=network.target nss-lookup.target time-sync.target remote-fs.target Before=getty(a)tty1.service plymouth-quit.service xdm.service [Service] Type=notify PrivateTmp=true ExecStart=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k start ExecReload=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k graceful ExecStop=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k graceful-stop KillMode=mixed [Install] WantedBy=multi-user.target Alias=httpd.service apache.service [Unit] Description=The Apache Webserver %I After=network.target nss-lookup.target time-sync.target Before=getty(a)tty1.service plymouth-quit.service xdm.service [Service] Type=notify PrivateTmp=true Environment="HTTPD_INSTANCE=%i" ExecStart=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k start ExecReload=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k graceful ExecStop=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k graceful-stop KillMode=mixed [Install] WantedBy=multi-user.target Alias=httpd@.service apache@.service ------------------------------------- BTW in /usr/lib/systemd/system I have 2 services: apache2.service and apache2@.service - is that normal and why are they 2? -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1032006] New: VUL-0: CVE-2017-7374: kernel-source: denial of service (NULL pointer dereference) or possibly gain privileges by revoking keyring keys being used for ext4, f2fs, or ubifs encryption
by bugzilla_noreply＠novell.com 01 Apr '17

01 Apr '17

http://bugzilla.suse.com/show_bug.cgi?id=1032006 Bug ID: 1032006 Summary: VUL-0: CVE-2017-7374: kernel-source: denial of service (NULL pointer dereference) or possibly gain privileges by revoking keyring keys being used for ext4, f2fs, or ubifs encryption Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: security-team(a)suse.de Reporter: mikhail.kasimov(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Ref: https://nvd.nist.gov/vuln/detail/CVE-2017-7374 ==================================================== Description Use-after-free vulnerability in fs/crypto/ in the Linux kernel before 4.10.7 allows local users to cause a denial of service (NULL pointer dereference) or possibly gain privileges by revoking keyring keys being used for ext4, f2fs, or ubifs encryption, causing cryptographic transform objects to be freed prematurely. Source: MITRE Last Modified: 03/31/2017 ==================================================== Hyperlink: [1] http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=1… [2] https://github.com/torvalds/linux/commit/1b53cf9815bb4744958d41f3795d5d5a1d… [3] https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.10.7 -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 999818] Enabling secure boot causes shim-install to fail
by bugzilla_noreply＠novell.com 01 Apr '17

01 Apr '17

http://bugzilla.suse.com/show_bug.cgi?id=999818 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|ibs:running:4392:low |ibs:running:4392:low |maint:planned:update | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1004933] New: BUG: unable to handle kernel NULL pointer dereference at 0000000000000008
by bugzilla_noreply＠novell.com 01 Apr '17

01 Apr '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1004933 Bug ID: 1004933 Summary: BUG: unable to handle kernel NULL pointer dereference at 0000000000000008 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: sebastian.kratz(a)piraten-ahoi.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 697537 --> http://bugzilla.opensuse.org/attachment.cgi?id=697537&action=edit complete dmesg this prevents me from booting. i've had the apparently terrible idea of putting attached edid in /lib/firmware a couple of weeks ago. if i unplug the monitor i can boot normally and X will detect the monitor on it's own when i replug it. this issue was apparently raised by udev, because i could boot the kernel 4.7.6-1-default before without problem, now i can't. uname -a Linux fxe 4.7.6-1-default #1 SMP PREEMPT Fri Sep 30 12:22:14 UTC 2016 (fb37fcc) x86_64 x86_64 x86_64 GNU/Linux [ 56.392430] BUG: unable to handle kernel NULL pointer dereference at 0000000000000008 [ 56.392474] IP: [<ffffffff812195f4>] set_root+0x24/0xb0 [ 56.392503] PGD 0 [ 56.392520] Oops: 0000 [#1] PREEMPT SMP [ 56.392539] Modules linked in: nf_log_ipv6 xt_pkttype nf_log_ipv4 nf_log_common xt_LOG xt_limit af_packet iscsi_ibft iscsi_boot_sysfs msr dm_crypt algif_skcipher af_alg snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep joydev uas usb_storage snd_pcm coretemp r8169 kvm_intel snd_timer iTCO_wdt iTCO_vendor_support kvm gpio_ich mii acpi_cpufreq tpm_tis fjes snd lpc_ich mfd_core soundcore ppdev tpm ip6t_REJECT nf_reject_ipv6 parport_pc parport shpchp i2c_i801 irqbypass button xt_tcpudp nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_raw ipt_REJECT nf_reject_ipv4 iptable_raw xt_CT iptable_filter ip6table_mangle nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_ipv4 nf_defrag_ipv4 ip_tables xt_conntrack nf_conntrack ip6table_filter ip6_tables [ 56.393141] x_tables btrfs xor hid_generic raid6_pq usbhid ata_generic ata_piix serio_raw ehci_pci amdkfd amd_iommu_v2 radeon i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops uhci_hcd ehci_hcd usbcore ttm usb_common drm sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua [ 56.393381] CPU: 0 PID: 224 Comm: plymouthd Not tainted 4.7.5-1-default #1 [ 56.393410] Hardware name: FUJITSU ESPRIMO P2560 /D3041-A1, BIOS 6.00 R1.02.3041.A1 11/09/2010 [ 56.393451] task: ffff880036d5c100 ti: ffff880036d10000 task.ti: ffff880036d10000 [ 56.393477] RIP: 0010:[<ffffffff812195f4>] [<ffffffff812195f4>] set_root+0x24/0xb0 [ 56.393507] RSP: 0018:ffff880036d13928 EFLAGS: 00010202 [ 56.393533] RAX: ffff880036d5c100 RBX: ffff880036d13a60 RCX: 0000000000000000 [ 56.393557] RDX: ffffffff82220e88 RSI: 0000000000000000 RDI: ffff880036d13a60 [ 56.393580] RBP: ffff880036d13940 R08: 0000000000000048 R09: ffff8800d2495ba0 [ 56.393602] R10: ffff880196bdd000 R11: 0000000000000000 R12: 0000000000000000 [ 56.393626] R13: ffff88019fb0f01c R14: ffff880196bd9780 R15: ffff880198623f00 [ 56.393650] FS: 00007f2c8a81a800(0000) GS:ffff88019fc00000(0000) knlGS:0000000000000000 [ 56.393687] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 56.393706] CR2: 0000000000000008 CR3: 00000000d2984000 CR4: 00000000000406f0 [ 56.393728] Stack: [ 56.393740] ffff880036d13a60 0000000000000040 ffff88019fb0f01c ffff880036d13978 [ 56.393785] ffffffff8121a3b3 ffff88019fb0f000 ffff880036d13b74 ffff880036d13a60 [ 56.393829] ffff880196bd9780 ffff880198623f00 ffff880036d13b74 ffffffff8121dae5 [ 56.393875] Call Trace: [ 56.393895] [<ffffffff8121a3b3>] path_init+0x1e3/0x350 [ 56.393919] [<ffffffff8121dae5>] path_openat+0x65/0x13b0 [ 56.393939] [<ffffffff8121ff5e>] do_filp_open+0x7e/0xe0 [ 56.393960] [<ffffffff8120eb20>] file_open_name+0xf0/0x120 [ 56.393980] [<ffffffff8120eb7c>] filp_open+0x2c/0x50 [ 56.393998] [<ffffffff81215dd4>] kernel_read_file_from_path+0x34/0x70 [ 56.394024] [<ffffffff814ee2fa>] _request_firmware+0x40a/0xad0 [ 56.394046] [<ffffffff814ee9ec>] request_firmware+0x2c/0x40 [ 56.394085] [<ffffffffc01b81fb>] drm_load_edid_firmware+0x28b/0x430 [drm_kms_helper] [ 56.394121] [<ffffffffc01adcd3>] drm_helper_probe_single_connector_modes+0x1e3/0x4d0 [drm_kms_helper] [ 56.394159] [<ffffffffc01bacb5>] drm_fb_helper_hotplug_event+0x95/0x120 [drm_kms_helper] [ 56.394190] [<ffffffffc01bad90>] drm_fb_helper_restore_fbdev_mode_unlocked+0x50/0x70 [drm_kms_helper] [ 56.394268] [<ffffffffc021c426>] radeon_fbdev_restore_mode+0x16/0x40 [radeon] [ 56.394307] [<ffffffffc01f057e>] radeon_driver_lastclose_kms+0xe/0x20 [radeon] [ 56.394360] [<ffffffffc0059cf9>] drm_lastclose+0x29/0x120 [drm] [ 56.394390] [<ffffffffc005a0da>] drm_release+0x2ea/0x4c0 [drm] [ 56.394412] [<ffffffff81211d28>] __fput+0xb8/0x1c0 [ 56.394431] [<ffffffff810996bc>] task_work_run+0x7c/0xa0 [ 56.394452] [<ffffffff81080613>] do_exit+0x2c3/0xb90 [ 56.394471] [<ffffffff81080f5a>] do_group_exit+0x3a/0xa0 [ 56.394490] [<ffffffff81080fd0>] SyS_exit_group+0x10/0x10 [ 56.394512] [<ffffffff816bc276>] entry_SYSCALL_64_fastpath+0x1e/0xa8 [ 56.396002] DWARF2 unwinder stuck at entry_SYSCALL_64_fastpath+0x1e/0xa8 [ 56.396002] Leftover inexact backtrace: [ 56.396002] Code: 1f 84 00 00 00 00 00 66 66 66 66 90 55 65 48 8b 04 25 00 d4 00 00 48 89 e5 41 55 41 54 53 f6 47 38 40 4c 8b a0 d0 06 00 00 74 3b <41> 8b 4c 24 08 f6 c1 01 75 75 49 8b 54 24 20 49 8b 44 24 18 48 [ 56.396002] RIP [<ffffffff812195f4>] set_root+0x24/0xb0 [ 56.396002] RSP <ffff880036d13928> [ 56.396002] CR2: 0000000000000008 [ 56.396002] ---[ end trace b72a0561f3c99686 ]--- -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 1031025] New: brtfs + grub2, save default produces error: sparse file not allowed at boot
by bugzilla_noreply＠novell.com 01 Apr '17

01 Apr '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1031025 Bug ID: 1031025 Summary: brtfs + grub2, save default produces error: sparse file not allowed at boot 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: harald.achitz(a)gmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 Build Identifier: default openSUSE installation with a brtfs root partition setup grub2 to save and boot the last used entry GRUB_DEFAULT=saved GRUB_SAVEDEFAULT="true" reboot save default does not work, it will always boot the first in the list, and an error messages is displayed sparse file not allowed at boot Reproducible: Always Steps to Reproduce: 1. install btrfs root partition and dual boot, for example with windows 2. setup grub2 to save default and boot saved 3. reboot Actual Results: instead of booting the last selected boot menu, always the default is used and an error error: sparse file not allowed at boot is displayed Expected Results: to boot the last selected boot entry without any problems -- You are receiving this mail because: You are on the CC list for the bug.

1 10