August 2015 - openSUSE Bugs - openSUSE Mailing Lists

[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

[Bug 930340] New: rtl8723be: wifi locks and disconnects on re-keying
by bugzilla_noreply＠novell.com 29 Dec '16

29 Dec '16

http://bugzilla.novell.com/show_bug.cgi?id=930340 Bug ID: 930340 Summary: rtl8723be: wifi locks and disconnects on re-keying 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: psychonaut(a)nothingisreal.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have a Realtek WLAN controller which uses the rtl8723be driver on the 3.16.7-21-desktop kernel. After connecting to a wireless network, the connection works for about 20 or 30 minutes. The connection then drops, and nothing short of rebooting can get it to connect again. Examining /var/log/wpa_supplicant.log shows that the disconnection always happens after a group rekeying: wlp2s0: WPA: Group rekeying completed with 5c:d9:98:e4:d9:d0 [GTK=TKIP] wlp2s0: WPA: Group rekeying completed with 5c:d9:98:e4:d9:d0 [GTK=TKIP] wlp2s0: WPA: Group rekeying completed with 5c:d9:98:e4:d9:d0 [GTK=TKIP] wlp2s0: WPA: Group rekeying completed with 5c:d9:98:e4:d9:d0 [GTK=TKIP] wlp2s0: CTRL-EVENT-DISCONNECTED bssid=5c:d9:98:e4:d9:d0 reason=2 wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=WORLD wlp2s0: CTRL-EVENT-SCAN-STARTED wlp2s0: SME: Trying to authenticate with 5c:d9:98:e4:d9:d0 (SSID='FrettchenNet' freq=2462 MHz) wlp2s0: CTRL-EVENT-SCAN-STARTED wlp2s0: SME: Trying to authenticate with 5c:d9:98:e4:d9:d0 (SSID='FrettchenNet' freq=2462 MHz) wlp2s0: CTRL-EVENT-SCAN-STARTED wlp2s0: SME: Trying to authenticate with 5c:d9:98:e4:d9:d0 (SSID='FrettchenNet' freq=2462 MHz) wlp2s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="FrettchenNet" auth_failures=1 duration=10 reason=CONN_FAILED This looks to be the upstream bug report: https://github.com/lwfinger/rtlwifi_new/issues/22 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 926006] New: KDE does not display Terminus font anymore
by bugzilla_noreply＠novell.com 26 Dec '16

26 Dec '16

http://bugzilla.opensuse.org/show_bug.cgi?id=926006 Bug ID: 926006 Summary: KDE does not display Terminus font anymore Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace Assignee: kde-maintainers(a)suse.de Reporter: suse(a)bugs.jan.ritzerfeld.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 630042 --> http://bugzilla.opensuse.org/attachment.cgi?id=630042&action=edit This is not xos4 Terminus but Arial with misplaced cursor KDE does not display the xos4 Terminus font anymore. It looks like the update of libfreetype6 last month caused this. Konsole and Yakuake use the fixed font metrics for the cursor but actually display Arial. jan@karl:~> fc-match "xos4 Terminus" ter-112n.pcf: "xos4 Terminus" "Regular" xterm does not want to use Terminus: jan@karl:~> xterm -fa "xos4 Terminus" xterm: Selected font has no non-zero height for ISO-8859-1 encoding -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 929688] New: Critical Problem in Qt Network Stack
by bugzilla_noreply＠novell.com 23 Dec '16

23 Dec '16

http://bugzilla.opensuse.org/show_bug.cgi?id=929688 Bug ID: 929688 Summary: Critical Problem in Qt Network Stack Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace Assignee: kde-maintainers(a)suse.de Reporter: freitag(a)owncloud.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- At ownCloud Inc. we have identified and fixed a severe bug in Qt's network stack which leads to data corruption in rare cases. The corruptions are very hard to even identify for users as the file size remains the same. We provided two patches for both the latest Qt4 and Qt5 packages as described in a mail to the Qt devel mailinglist: http://lists.qt-project.org/pipermail/development/2015-May/021295.html We would like to ask kindly to ship these patches on all supported platforms of openSUSE to avoid users data corruption. Thanks! -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 909824] New: Meld background color of the source view is black when using gtk3-oxygen theme in kde4
by bugzilla_noreply＠novell.com 23 Dec '16

23 Dec '16

http://bugzilla.opensuse.org/show_bug.cgi?id=909824 Bug ID: 909824 Summary: Meld background color of the source view is black when using gtk3-oxygen theme in kde4 Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace Assignee: kde-maintainers(a)suse.de Reporter: thomasbilk(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- There is a resolving bug on the GNOME/meld Bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=741287 When you use meld with the gtk3-oxygen theme in kde4 the background of the source view is black and so nothing is readable. It seems like they fixed it. So it would be nice to see the patch in openSuse 13.2. -- You are receiving this mail because: You are on the CC list for the bug.

1 4