June 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 912170] New: Boot fails with BTRFS RAID1 array as /home - open ctree failed
by bugzilla_noreply＠novell.com 09 Nov '16

09 Nov '16

http://bugzilla.opensuse.org/show_bug.cgi?id=912170 Bug ID: 912170 Summary: Boot fails with BTRFS RAID1 array as /home - open ctree failed Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: 64bit OS: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: RyanSKingsbury(a)alumni.utexas.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I recently did a clean install of OpenSUSE 13.2 into a system with three drives - 1 SSD containing the / partition (btrfs format with default subvolumes), and 2 identical HDD's containing /home in an encrypted BTRFS RAID1 array. Initially, I was using only one of the HDD's as /home (still encrypted BTRFS). Once I added the second drive and started the RAID1 mirroring, my system will no longer boot without manual intervention. I get dropped into "emergency mode", but then all I have to do is exit (Ctrl+D) to continue booting and everything works normally. The last entry in the system log before Emergency Mode is invoked is: Code: BTRFS: open_ctree failed It appears that a similar (maybe the same) bug was reported on ArchWiki: https://wiki.archlinux.org/index.php/Btrfs#BTRFS:_open_ctree_failed But the solution refers to mkinitcpio rather than dracut that OpenSUSE uses, so I'm unsure how to apply it to my system. Some relevant system information: excerpt from /etc/fstab: ---- # encrypted RAID1 array containing /home UUID=e91f611f-524a-43f5-bde5-8ebb9672f146 /home btrfs defaults 0 0 ---- /etc/crypttab: ---- encrypted-home-sdb UUID=9c8fb7d0-74e2-4e38-b7c7-6211bbb6d2b1 none luks, retry=1 encrypted-home-sdc UUID=b82e5894-cea2-4fe7-a0a5-80f918e9db61 none luks, retry=1 ---- excerpt from fdisk -l: ---- Device Start End Sectors Size Type /dev/sdb1 2048 1953523711 1953521664 931.5G Microsoft basic data Disk /dev/sdc: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: CAC38602-D5A5-4F28-8344-65B559124514 Device Start End Sectors Size Type /dev/sdc1 2048 1953525134 1953523087 931.5G Linux filesystem Disk /dev/mapper/encrypted-home-sdc: 931.5 GiB, 1000201723392 bytes, 1953518991 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/mapper/encrypted-home-sdb: 931.5 GiB, 1000200994816 bytes, 1953517568 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes ---- Device UUID's: ---- /dev/sda1: UUID="04e20317-f554-43cf-a95d-b0385ebd22bb" UUID_SUB="cb9dc431-1855-466b-ae9a-5c0ddcd7f95a" TYPE="btrfs" PTTYPE="dos" PARTLABEL="primary" PARTUUID="860c637a-83c8-4399-8dc4-5b5ab66c0f06" /dev/sdb1: UUID="9c8fb7d0-74e2-4e38-b7c7-6211bbb6d2b1" TYPE="crypto_LUKS" PARTLABEL="primary" PARTUUID="532a7bd2-6774-422e-90c0-31f19796098d" /dev/sdc1: UUID="1ca9d3ba-c409-4127-91f5-e3d9c21242bd" TYPE="crypto_LUKS" PARTLABEL="Linux filesystem" PARTUUID="5a6830cc-9064-476c-aa79-6189dd0964bd" /dev/mapper/encrypted-home-sdc: UUID="e91f611f-524a-43f5-bde5-8ebb9672f146" UUID_SUB="6007c4c7-5119-4b0f-ab21-134832c4774c" TYPE="btrfs" /dev/mapper/encrypted-home-sdb: UUID="e91f611f-524a-43f5-bde5-8ebb9672f146" UUID_SUB="020bae26-b64f-413e-8263-a6e832ccb224" TYPE="btrfs" ---- -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 915760] New: NetworkManager fails configuring DNS servers when switching network
by bugzilla_noreply＠novell.com 07 Nov '16

07 Nov '16

http://bugzilla.opensuse.org/show_bug.cgi?id=915760 Bug ID: 915760 Summary: NetworkManager fails configuring DNS servers when switching network Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: tsuroerusu(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:35.0) Gecko/20100101 Firefox/35.0 Build Identifier: I run IT at a fairly large school (By Danish standards), and we lend out laptops to students. For this purpose, we have deployed openSUSE 13.2, generally with great success. These are generally ThinkPad R60 and R61 machines, they run openSUSE 13.2 with KDE. However, we are experiencing a problem. When switching between networks, for example from wireless to wireless or wireless to statically configured wired, NetworkManager does not properly alter /etc/resolv.conf with the new DNS servers. Recently, a student took home their borrowed laptop, and connected it to their private wireless network. But when they came back to school, NetworkManager had left their home network's DNS servers in resolv.conf, and then no websites would obviously show up. I have also experienced this problem on my personal laptop, when I try to switch from wireless to wired at home, where I have a statically configured IP in NetworkManager on my wired network. Then more often than not, NetworkManager does not configure ANY DNS servers, despite them being specified in its configuration. In all cases, I am referring to the NetworkManager applet in KDE. This is a huge problem for us. I would really really appreciate, if this issue could be looked into as soon as possible. Reproducible: Always Steps to Reproduce: 1. Configure a wireless connection in the NM applet. 2. Connect to the wireless network, and surf the web. 3. Connect to a different wireless network, and switch between them, at some point the DNS servers will be mis-configured. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 935027] New: Enable CONFIG_EFI_MIXED
by bugzilla_noreply＠novell.com 03 Nov '16

03 Nov '16

http://bugzilla.suse.com/show_bug.cgi?id=935027 Bug ID: 935027 Summary: Enable CONFIG_EFI_MIXED 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: kukuk(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- CONFIG_EFI_MIXED is disabled in SLE and openSUSE. Even if we official don't support systems with a 32bit EFI firmware, there are consumer machines out there which have them. Since we still ship a grub2 capable of booting machines with a pure 32bit EFI firmware, I did run into a lot of problems since CONFIG_EFI_MIXED was disabled: - YaST does not detect that this is a EFI system - efibootmgr cannot access EFI variables - wlan driver did not work - reboot does not work And most likely quite some more. I don't know which disadvantages this option has, but could we please enable it at least for openSUSE? -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 926331] New: / being remounted ro prevents booting
by bugzilla_noreply＠novell.com 02 Nov '16

02 Nov '16

http://bugzilla.suse.com/show_bug.cgi?id=926331 Bug ID: 926331 Summary: / being remounted ro prevents booting Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: oneukum(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- If an error on the root file system causes the fs to be mountable only ro, systemd will refuse to boot the system. Thus fixing the problem requires a rescue disk. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 901278] New: Get 'segmentation fault' during reinstalling hamsta using autoyast on openSUSE 13.2 RC1
by bugzilla_noreply＠novell.com 31 Oct '16

31 Oct '16

http://bugzilla.suse.com/show_bug.cgi?id=901278 Bug ID: 901278 Summary: Get 'segmentation fault' during reinstalling hamsta using autoyast on openSUSE 13.2 RC1 Classification: openSUSE Product: openSUSE Distribution Version: 13.2 RC 1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: tfeng(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 610138 --> http://bugzilla.suse.com/attachment.cgi?id=610138&action=edit auto-install file Description: Install hamsta on openSUSE 13.2 RC1. Then reinstall the machine using autoyast file. It will throw segmentation fault during reboot. And it will hang on reboot, right before set configuration. Autoyast file, y2log, screenshot can be found in attachment. Reproduce Frequency: 100% Step: * Install hamsta on openSUSE 13.2 RC1 * Reinstall hamsta using autoyast -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 927225] New: build logs do not end with newline
by bugzilla_noreply＠novell.com 31 Oct '16

31 Oct '16

http://bugzilla.suse.com/show_bug.cgi?id=927225 Bug ID: 927225 Summary: build logs do not end with newline Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: OBS Request Assignee: mrueckert(a)suse.com Reporter: sweet_f_a(a)gmx.de QA Contact: adrian(a)suse.com Found By: --- Blocker: --- If you have a reproduced build which ends with something like "Retried build at Wed Apr 15 10:09:57 2015 returned same result, skipped" then there is no newline '\n' at the end of log file. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 906248] New: opensuse 13.2 i586 bit not installable as xen pv-guest
by bugzilla_noreply＠novell.com 27 Oct '16

27 Oct '16

http://bugzilla.suse.com/show_bug.cgi?id=906248 Bug ID: 906248 Summary: opensuse 13.2 i586 bit not installable as xen pv-guest Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: i586 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: jgross(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- It is impossible to install openSUSE 13.2 i586 as a Xen pv-guest. There is no xen kernel on the DVD. Host system is SLES 12. x86_64 works as expected, but I need a 32 bit system for some tests. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 904705] New: after update from 13.1 to 13.2 yast2 qt does not start
by bugzilla_noreply＠novell.com 25 Oct '16

25 Oct '16

http://bugzilla.suse.com/show_bug.cgi?id=904705 Bug ID: 904705 Summary: after update from 13.1 to 13.2 yast2 qt does not start Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: aschnell(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- I made an update (using zypper dup) from 13.1 to 13.2 and now yast2 does not start using qt (but does start using ncurses). The program is stuck in a read system call. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 904842] New: bargraph in gtk not working
by bugzilla_noreply＠novell.com 25 Oct '16

25 Oct '16

http://bugzilla.suse.com/show_bug.cgi?id=904842 Bug ID: 904842 Summary: bargraph in gtk not working Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: aschnell(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- The bargraph is not working with the gtk frontend. It just shows a white area. Since the tooltips inside the bargraph are working it looks as if the parameters passed to the bargraph are correct. Due to bug #904705 I cannot test the qt frontend. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 793787] New: Kdenlive crashes, does not start
by bugzilla_noreply＠novell.com 23 Oct '16

23 Oct '16

https://bugzilla.novell.com/show_bug.cgi?id=793787 https://bugzilla.novell.com/show_bug.cgi?id=793787#c0 Summary: Kdenlive crashes, does not start Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: espinosa_cz(a)centrum.cz QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=516460) --> (http://bugzilla.novell.com/attachment.cgi?id=516460) Kdenlive crash file User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Firefox/17.0 I was working with Kdenlive for last for a day or two and was OK. Then I added KDE 49 repo and updated. Kdenlive still worked. Problems started when I hit render button for the first time. Whole application segfaulted. I don't have a crash report for that. Since then Sometimes I managed to run kdenlive as: strace kdenlive Few times kdenlive started, but always crashed when hit render. Lately a message box window appears stating: "No profile was found, using default profile" and then it crash. I upgraded everything possible. All packages where new version is available. Today. Kernel got upgraded on the way too. My openSuse 12.2 was upgraded from openSuse 12.1 recently, few weeks ago and it was not completely smooth transition, but otherwise everything works now, except Kdenlive. I tried both versions from Pacman and KDE 49 repos. Both exhibit same issues. I paid extra attention to have all library versions - mlt, melt, mlt++, libavxxx - from the respective repository and not mix them up. Though the KDE 49 repository contains only libavutil so I guess it will not work anyway, it will not be usable without Pacman libavformat/ffmpeg libs I guess. Still same issue I tried downgrade a notch or two, but no change. Mlt got degraded from mlt5 to mlt4 on the way. No change, same issue. There are 2 types of crash: 1) float point exception in reading some timecode (Mlt?) 2) Mlt crashes when reading some string property (looks like initializing of some effect) I now downgrading back to KDE 4.8, removing KDE 4.9 and all its packages. I will keep you informed. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 12