June 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 933428] New: btrfs qgroup - allways shows WARNING: Qgroup data inconsistent
by bugzilla_noreply＠novell.com 06 Jan '17

06 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=933428 Bug ID: 933428 Summary: btrfs qgroup - allways shows WARNING: Qgroup data inconsistent Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: mpluskal(a)suse.com QA Contact: qa-bugs(a)suse.de CC: dsterba(a)suse.com Found By: --- Blocker: --- On current factory, it seems that even after qgroup rescan,Qgroup data inconsistent are inconsistent: # btrfs qgroup show /|head WARNING: Rescan is running, qgroup data may be incorrect qgroupid rfer excl -------- ---- ---- 0/5 16.00KiB 16.00KiB ... # btrfs qgroup show /|head WARNING: Qgroup data inconsistent, rescan recommended qgroupid rfer excl I am not sure what more to provide, also boo#933427 - btrfs-image segfault -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 900398] New: XenServer Installation failed
by bugzilla_noreply＠novell.com 05 Jan '17

05 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=900398 Bug ID: 900398 Summary: XenServer Installation failed Classification: openSUSE Product: openSUSE Factory Version: 201410* Hardware: Other OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: olivpass(a)web.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1916.114 Safari/537.36 Build Identifier: openSUSE-13.2-NET-Build0019-x86_64.iso Hi, XenServer installation failed because there is no installation kernel in this iso openSUSE-13.2-NET-Build0019-x86_64.iso! Error Message auf XenServer: Oct 9, 2014 10:05:09 AM Error: Starting VM 'opensuse132_r1_klein' - The bootloader for this VM returned an error -- did the VM installation succeed? INVALID_SOURCE The repository specified did not contain a required file, file:///tmp/cdrom-repo-isbQ8F/boot/x86_64/vmlinuz-xen. The DVD installation with iso openSUSE-13.2-DVD-Build0019-x86_64.iso works well. Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 905832] New: Please backport mmap btrfs fixes/or update to kernel 3.16.7/3.17.3
by bugzilla_noreply＠novell.com 05 Jan '17

05 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=905832 Bug ID: 905832 Summary: Please backport mmap btrfs fixes/or update to kernel 3.16.7/3.17.3 Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: hrvoje.senjan(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- we've got big amount of crashes at KDE bugtracker, with each and one being with openSUSE 13.2, using btrfs as root fs and using 3.16.6 kernel. report can be found here: https://bugs.kde.org/show_bug.cgi?id=340657 KSharedDataCache is used for e.g. Plasma cache and icon cache, and it in turn uses posix_fallocate and mmap, thus apparently a btrfs bug triggers crashing (all reports have plasma receiving a SIGBUS) there is also report with very similar usage @ btrfs ML: http://www.spinics.net/lists/linux-btrfs/msg38740.html users there report the issue is gone with 3.17.2 kernels.. (on KDE tracker we have so far one user validating that there is no crashes with 3.17.2) if you have knowledge which would be commit specifically addressing this issue, please backport it, otherwise, if possible, please update to latest stable kernel (i've read the discussion @ opensuse-kernel, so this doesn't look likely ;-) as this is making a KDE experience on openSUSE 13.2 pretty bad. thanks in advance! -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 906684] New: btrfs bug
by bugzilla_noreply＠novell.com 05 Jan '17

05 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=906684 Bug ID: 906684 Summary: btrfs bug Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: f.st(a)arcor.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Nov 22 11:31:51 peacy kernel: ------------[ cut here ]------------ Nov 22 11:31:51 peacy kernel: kernel BUG at ../fs/btrfs/extent_io.c:2875! Nov 22 11:31:51 peacy kernel: invalid opcode: 0000 [#1] PREEMPT SMP Nov 22 11:31:51 peacy kernel: Modules linked in: joydev hid_sony fuse bnep bluetooth 6lowpan_iphc af_packet sr_mod cdrom xt_pkttype xt_LOG xt_limit cfg80211 ip6t_REJECT xt_tcpudp nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_raw ipt_REJECT iptable_raw xt_CT iptable_filter ip Nov 22 11:31:51 peacy kernel: snd_pcm crc32_pclmul ghash_clmulni_intel cryptd serio_raw pcspkr snd_timer i2c_i801 lpc_ich mfd_core r8169 mii snd wmi mei_me mei fan thermal battery parport_pc parport soundcore processor shpchp dm_mod btrfs xor raid6_pq crc32c_intel i915 Nov 22 11:31:51 peacy kernel: CPU: 1 PID: 1309 Comm: plasma-desktop Not tainted 3.16.6-2-desktop #1 Nov 22 11:31:51 peacy kernel: Hardware name: System manufacturer System Product Name/P8B75-M LX, BIOS 1403 08/06/2014 Nov 22 11:31:51 peacy kernel: task: ffff8800b9964510 ti: ffff8800b9ac4000 task.ti: ffff8800b9ac4000 Nov 22 11:31:51 peacy kernel: RIP: 0010:[<ffffffffa026b068>] [<ffffffffa026b068>] __do_readpage+0x7c8/0x7d0 [btrfs] Nov 22 11:31:51 peacy kernel: RSP: 0018:ffff8800b9ac7988 EFLAGS: 00010206 Nov 22 11:31:51 peacy kernel: RAX: 0000000000326000 RBX: 0000000000001000 RCX: 0000000000000005 Nov 22 11:31:51 peacy kernel: RDX: 0000000000326000 RSI: ffff880102b331d0 RDI: ffff8800b36350b0 Nov 22 11:31:51 peacy kernel: RBP: ffff8800b9ac7b48 R08: ffff8800b36350b0 R09: 000000000050a000 Nov 22 11:31:51 peacy kernel: R10: ffff8800cc3a7000 R11: 0000000000000001 R12: ffff8800b9ac7b48 Nov 22 11:31:51 peacy kernel: R13: ffff8800b9ac7b48 R14: 0000000000000000 R15: 000000000050a000 Nov 22 11:31:51 peacy kernel: FS: 00007ff3b3075780(0000) GS:ffff88011eb00000(0000) knlGS:0000000000000000 Nov 22 11:31:51 peacy kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Nov 22 11:31:51 peacy kernel: CR2: 00007f5f52cf8000 CR3: 00000000b9a0b000 CR4: 00000000000407e0 Nov 22 11:31:51 peacy kernel: Stack: Nov 22 11:31:51 peacy kernel: ffff88011a0ab3c0 ffff8800b9ac7b38 ffffffffa026b760 ffff880000000000 Nov 22 11:31:51 peacy kernel: 0000000000000000 0000000000000000 000000000050afff ffff8801149ad088 Nov 22 11:31:51 peacy kernel: 0000000000000000 ffffea0001f31dd8 0000000000001000 ffff88011a0ab3c0 Nov 22 11:31:51 peacy kernel: Call Trace: Nov 22 11:31:51 peacy kernel: [<ffffffffa026b412>] __extent_readpages.constprop.42+0x2d2/0x2f0 [btrfs] Nov 22 11:31:51 peacy kernel: [<ffffffffa026c6f5>] extent_readpages+0x155/0x1a0 [btrfs] Nov 22 11:31:51 peacy kernel: [<ffffffff8115613b>] __do_page_cache_readahead+0x1ab/0x230 Nov 22 11:31:51 peacy kernel: [<ffffffff8114cab0>] filemap_fault+0x360/0x400 Nov 22 11:31:51 peacy kernel: [<ffffffff81171afa>] __do_fault+0x3a/0xa0 Nov 22 11:31:51 peacy kernel: [<ffffffff8117475d>] do_read_fault.isra.53+0x4d/0x300 Nov 22 11:31:51 peacy kernel: [<ffffffff811761cf>] handle_mm_fault+0x81f/0x1170 Nov 22 11:31:51 peacy kernel: [<ffffffff81048ce8>] __do_page_fault+0x158/0x530 Nov 22 11:31:51 peacy kernel: [<ffffffff816237d8>] page_fault+0x28/0x30 Nov 22 11:31:51 peacy kernel: [<00007ff3b06d6a0c>] 0x7ff3b06d6a0b Nov 22 11:31:51 peacy kernel: Code: e8 ae db ff ff e9 e2 fd ff ff e8 14 1f da e0 e9 08 f9 ff ff bb 00 10 00 00 31 f6 c7 84 24 b4 00 00 00 00 00 00 00 e9 6b fe ff ff <0f> 0b 0f 0b 0f 0b 0f 0b 66 66 66 66 90 41 57 49 89 f7 41 56 41 Nov 22 11:31:51 peacy kernel: RIP [<ffffffffa026b068>] __do_readpage+0x7c8/0x7d0 [btrfs] Nov 22 11:31:51 peacy kernel: RSP <ffff8800b9ac7988> Nov 22 11:31:51 peacy kernel: ---[ end trace 910602ffbf32e856 ]--- Nov 22 11:31:51 peacy kernel: ------------[ cut here ]------------ Nov 22 11:31:51 peacy kernel: WARNING: CPU: 1 PID: 1309 at ../kernel/exit.c:669 do_exit+0x4d/0xa90() Nov 22 11:31:51 peacy kernel: Modules linked in: joydev hid_sony fuse bnep bluetooth 6lowpan_iphc af_packet sr_mod cdrom xt_pkttype xt_LOG xt_limit cfg80211 ip6t_REJECT xt_tcpudp nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_raw ipt_REJECT iptable_raw xt_CT iptable_filter ip Nov 22 11:31:51 peacy kernel: snd_pcm crc32_pclmul ghash_clmulni_intel cryptd serio_raw pcspkr snd_timer i2c_i801 lpc_ich mfd_core r8169 mii snd wmi mei_me mei fan thermal battery parport_pc parport soundcore processor shpchp dm_mod btrfs xor raid6_pq crc32c_intel i915 Nov 22 11:31:51 peacy kernel: CPU: 1 PID: 1309 Comm: plasma-desktop Tainted: G D 3.16.6-2-desktop #1 Nov 22 11:31:51 peacy kernel: Hardware name: System manufacturer System Product Name/P8B75-M LX, BIOS 1403 08/06/2014 Nov 22 11:31:51 peacy kernel: 0000000000000009 ffffffff8161ab03 0000000000000000 ffffffff8105bad7 Nov 22 11:31:51 peacy kernel: 000000000000000b ffff8800b9ac78d8 0000000000000246 ffffffff81a0c6b3 Nov 22 11:31:51 peacy kernel: 0000000000000000 ffffffff8105dd2d 000000000050a000 ffffffff8161559f Nov 22 11:31:51 peacy kernel: Call Trace: Nov 22 11:31:51 peacy kernel: [<ffffffff8100519e>] dump_trace+0x8e/0x350 Nov 22 11:31:51 peacy kernel: [<ffffffff81005506>] show_stack_log_lvl+0xa6/0x190 Nov 22 11:31:51 peacy kernel: [<ffffffff81006c01>] show_stack+0x21/0x50 Nov 22 11:31:51 peacy kernel: [<ffffffff8161ab03>] dump_stack+0x49/0x6a Nov 22 11:31:51 peacy kernel: [<ffffffff8105bad7>] warn_slowpath_common+0x77/0x90 Nov 22 11:31:51 peacy kernel: [<ffffffff8105dd2d>] do_exit+0x4d/0xa90 Nov 22 11:31:51 peacy kernel: [<ffffffff81006537>] oops_end+0x97/0xe0 Nov 22 11:31:51 peacy kernel: [<ffffffff81003770>] do_error_trap+0x70/0xe0 Nov 22 11:31:51 peacy kernel: [<ffffffff8162338e>] invalid_op+0x1e/0x30 Nov 22 11:31:51 peacy kernel: [<ffffffffa026b068>] __do_readpage+0x7c8/0x7d0 [btrfs] Nov 22 11:31:51 peacy kernel: [<ffffffffa026b412>] __extent_readpages.constprop.42+0x2d2/0x2f0 [btrfs] Nov 22 11:31:51 peacy kernel: [<ffffffffa026c6f5>] extent_readpages+0x155/0x1a0 [btrfs] Nov 22 11:31:51 peacy kernel: [<ffffffff8115613b>] __do_page_cache_readahead+0x1ab/0x230 Nov 22 11:31:51 peacy kernel: [<ffffffff8114cab0>] filemap_fault+0x360/0x400 Nov 22 11:31:51 peacy kernel: [<ffffffff81171afa>] __do_fault+0x3a/0xa0 Nov 22 11:31:51 peacy kernel: [<ffffffff8117475d>] do_read_fault.isra.53+0x4d/0x300 Nov 22 11:31:51 peacy kernel: [<ffffffff811761cf>] handle_mm_fault+0x81f/0x1170 Nov 22 11:31:51 peacy kernel: [<ffffffff81048ce8>] __do_page_fault+0x158/0x530 Nov 22 11:31:51 peacy kernel: [<ffffffff816237d8>] page_fault+0x28/0x30 Nov 22 11:31:51 peacy kernel: [<00007ff3b06d6a0c>] 0x7ff3b06d6a0b Nov 22 11:31:51 peacy kernel: ---[ end trace 910602ffbf32e857 ]--- -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 908073] New: Creation of encrypted LVM during installation is impossible when Btrfs is selected
by bugzilla_noreply＠novell.com 05 Jan '17

05 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=908073 Bug ID: 908073 Summary: Creation of encrypted LVM during installation is impossible when Btrfs is selected Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: 64bit OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: Vojtech.Zeisek(a)opensuse.org QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 615682 --> http://bugzilla.opensuse.org/attachment.cgi?id=615682&action=edit Screenshot documenting the bug I use to use disk partitions as follows: 1) boot (+ efi partition if needed) 2) encrypted LVM containing a) root b) swap When installing, I click to expert partitioning and create those partitions manually. No problem. But 13.2 has a small bug. I create boot partition. Then I wish to make encrypted LVM. I add new Raw volume (unformatted). From Formatting Options the second possibility (Do not format...) is checked and LVM selected from drop-down menu. But check-box to encrypt the device is inactive. So the encryption is impossible. I have to click on "Format partition", select Ext4 instead of Btrfs (preselected default) and then again "Do not format...". By this magic operation the encryption check-box is activated, I can check it and continue as I'm used to. Other steps are OK. In all other steps one can choose default value or whatever is wished. The screenshot is from VirtualBox, but it, of course, happens in same way on real HW. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 936573] New: home:darix:neovim/neovim: Bug: Unhandled OSC when using :term
by bugzilla_noreply＠novell.com 04 Jan '17

04 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=936573 Bug ID: 936573 Summary: home:darix:neovim/neovim: Bug: Unhandled OSC when using :term Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: mrueckert(a)suse.com Reporter: damienradtke(a)gmail.com QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- After installing neovim and opening up the built-in terminal emulator (:term), it continuously reports this error: libvterm: Unhandled OSC 7 It looks like this is an error with how the libvterm dependency is built, as documented here: https://github.com/neovim/neovim/issues/2251 Tested with NVIM 0.0.0-alpha (compiled May 22 2015 21:13:03) running in GNOME Terminal 3.14.3-7.1, openSUSE 13.2. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 911618] New: routing wrong when using wicked for networking
by bugzilla_noreply＠novell.com 03 Jan '17

03 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=911618 Bug ID: 911618 Summary: routing wrong when using wicked for networking Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: jnelson-suse(a)jamponi.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have since switched (at not inconsiderable pain, since this is a console-only system) from wicked to network manager due to repeated problems with wicked messing up the routing (and causing other issues). before: turnip:/etc/sysconfig # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 A.B.C.D 0.0.0.0 UG 0 0 0 outside 10.10.0.0 0.0.0.0 255.255.255.0 U 0 0 0 wlp0s18f2u3 A.B.C.0 0.0.0.0 255.255.252.0 U 0 0 0 outside 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 inside 239.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 inside after: turnip:~ # rcnetwork restart turnip:~ # /sbin/route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 A.B.C.D 0.0.0.0 UG 0 0 0 outside A.B.C.0 0.0.0.0 255.255.252.0 U 0 0 0 outside 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 inside turnip:~ # difference: a route for wlp0s18f2u3 a route for 239.0.0.0 ? and then later still: turnip:~ # /sbin/route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 inside turnip:~ # -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 907693] New: Default bootloader GRUB2 is not supported!?
by bugzilla_noreply＠novell.com 03 Jan '17

03 Jan '17

http://bugzilla.opensuse.org/show_bug.cgi?id=907693 Bug ID: 907693 Summary: Default bootloader GRUB2 is not supported!? Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Like it, or not: The default boot loader in openSUSE 13.2 is GRUB2. Unfortunately the program is very complex and documentation is very poor at the same time. And SUSE adds in /usr/share/doc/packages/grub2/README.openSUSE: "There is not yet any support in openSUSE to configure and install grub2." "Currently, perl-Bootloader does not support grub2 as bootloader. Therefore you need to run the following after each kernel change: # grub2-mkconfig -o /boot/grub2/grub.cfg" Why leave the user alone with all that mess? -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 680125] New: dlclose() can not unload all dynamic libraries
by bugzilla_noreply＠novell.com 02 Jan '17

02 Jan '17

https://bugzilla.novell.com/show_bug.cgi?id=680125 https://bugzilla.novell.com/show_bug.cgi?id=680125#c0 Summary: dlclose() can not unload all dynamic libraries Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Development AssignedTo: pth(a)novell.com ReportedBy: gotterdammerung(a)web.de QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=419657) --> (http://bugzilla.novell.com/attachment.cgi?id=419657) test program which opens a dl from cmdline, closes it and checks if it is still open User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-DE; rv:1.9.2.15) Gecko/20110310 Gentoo Firefox/3.6.15 A call to dlclose() does not unload some dynamic libraries, even if the reference count drops to zero and no other loaded libraries use symbols in it. See attached test programm. Some libraries like 'pthread' exhibit this behaviour and it propagates up the dependency chain. This breaks programs which rely on reloading of affected dynamic libraries. Reproducible: Always Steps to Reproduce: 1. compile test program with 'g++ test.cpp -otest -ldl' 2. run 'for file in /usr/lib64/lib*.so; do ./test $file; done | grep failed' Actual Results: see attachment #2 Expected Results: /usr/lib64/librt.so failed. (at least that is what happens on my gentoo machine) AFAIK, x86_64 and x86 are both affected. Related: [[bugzilla:645652]] -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 15

[Bug 622977] New: pstoedit crashes when called from inkscape
by bugzilla_noreply＠novell.com 01 Jan '17

01 Jan '17

http://bugzilla.novell.com/show_bug.cgi?id=622977 http://bugzilla.novell.com/show_bug.cgi?id=622977#c0 Summary: pstoedit crashes when called from inkscape Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: All OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: gerlach(a)mbi-berlin.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.6) Gecko/20100626 SUSE/3.6.6-1.1 Firefox/3.6.6 pstoedit crashes when converting pdf to svg (used by inkscape textext) Reproducible: Always Steps to Reproduce: 1. pstoedit -f plot-svg file.pdf file.svg -dt -ssp -psarg -r9600x9600 (command used by inkscape) Actual Results: pstoedit: version 3.50 / DLL interface 108 (build Jul 5 2010 - release build - g++ 4.5.0 20100604 [gcc-4_5-branch revision 160292]) : Copyright (C) 1993 - 2009 Wolfgang Glunz Inconsistency detected by ld.so: dl-close.c: 731: _dl_close: Assertion `map->l_init_called' failed! -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 22