August 2015 - openSUSE Bugs - openSUSE Mailing Lists

[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

[Bug 779147] New: KDE:Release:49/branding-openSUSE_12.2: Bug
by bugzilla_noreply＠novell.com 23 Oct '16

23 Oct '16

https://bugzilla.novell.com/show_bug.cgi?id=779147 https://bugzilla.novell.com/show_bug.cgi?id=779147#c0 Summary: KDE:Release:49/branding-openSUSE_12.2: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: openSUSE 12.2 Status: NEW Severity: Minor Priority: P5 - None Component: 3rd party software AssignedTo: toddrme2178(a)gmail.com ReportedBy: lars.altenhain(a)micram.com QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- The post and postun scripts for plymouth-branding-openSUSE set LIBDIR to %{_libdir} before calling plymouth-set-default-theme which then fails on 64bit systems with "/usr/lib/plymouth/script.so does not exist". The "export LIB=%{_libdir}" should be removed from the post and postun scripts as plymouth-set-default-theme contains the following logic to set PLYMOUTH_PLUGIN_PATH variable which uses "plymouth --get-splash-plugin-path" to get the correct path if "LIB" is not set. [ -z "$PLYMOUTH_LIBEXECDIR" ] && PLYMOUTH_LIBEXECDIR="/usr/lib" [ -z "$PLYMOUTH_DATADIR" ] && PLYMOUTH_DATADIR="/usr/share" [ -z "$PLYMOUTH_CONFDIR" ] && PLYMOUTH_CONFDIR="/etc/plymouth/" [ -z "$PLYMOUTH_POLICYDIR" ] && PLYMOUTH_POLICYDIR="/usr/share/plymouth/" if [ -z "$PLYMOUTH_PLUGIN_PATH" ]; then if [ -z "$LIB" ]; then PLYMOUTH_PLUGIN_PATH="$(plymouth --get-splash-plugin-path)" else [ -z "$PLYMOUTH_LIBDIR" ] && PLYMOUTH_LIBDIR="/usr/lib" PLYMOUTH_PLUGIN_PATH=${PLYMOUTH_LIBDIR}/plymouth/ fi fi -- 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 3

[Bug 680148] New: kiwi complains about no clicfs tools if there is no cdrkit compat
by bugzilla_noreply＠novell.com 23 Oct '16

23 Oct '16

https://bugzilla.novell.com/show_bug.cgi?id=680148 https://bugzilla.novell.com/show_bug.cgi?id=680148#c0 Summary: kiwi complains about no clicfs tools if there is no cdrkit compat Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: ms(a)novell.com ReportedBy: coolo(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- I wanted to create a small ISO with clicfs and kiwi complained that there are no tools for clicfs. After digging the code I figured it actually looked for mkisofs first and set the toolerror flag because it's not there. Afaik it's not even using mkisofs but genisoimage -- 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 7

[Bug 907331] New: yast2 partitioner: failure when creating thin lvm volume
by bugzilla_noreply＠novell.com 22 Oct '16

22 Oct '16

http://bugzilla.opensuse.org/show_bug.cgi?id=907331 Bug ID: 907331 Summary: yast2 partitioner: failure when creating thin lvm volume Classification: openSUSE Product: openSUSE Factory Version: 201411* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: mpluskal(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 615112 --> http://bugzilla.opensuse.org/attachment.cgi?id=615112&action=edit y2logs When trying to create thin volume on thin pool (lvm), following error occurs: 2014-11-26 15:57:50 <1> medusa(3470) [Ruby] modules/StorageClients.rb:123 CommitErrorPopup error:-3008 last_action:Formatting logical volume /dev/storage/volume (512.00 GiB) with xfs extended_message:/sbin/mkfs.xfs -q -f -m crc=1 '/dev/storage/volume': /bin/sh: /sbin/mkfs.xfs: No such file or directory # lsblk -f NAME FSTYPE LABEL UUID MOUNTPOINT sda ├─sda1 swap 401da6ed-9159-40a9-a080-31f6638c3a66 [SWAP] └─sda2 btrfs root 3346482b-e201-4f14-bf36-f8fa7f16acbc / sdb └─sdb1 LVM2_member mlavlB-jorg-mbxn-o1p9-ybOf-tKJn-xEHaJh ├─storage-tpool_tmeta │ └─storage-tpool-tpool │ ├─storage-tpool │ └─storage-volume └─storage-tpool_tdata └─storage-tpool-tpool ├─storage-tpool └─storage-volume sr0 # vgdisplay WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it! connect() failed on local socket: No such file or directory Internal cluster locking initialisation failed. WARNING: Falling back to local file-based locking. Volume Groups with the clustered attribute will be inaccessible. --- Volume group --- VG Name storage System ID Format lvm2 Metadata Areas 1 Metadata Sequence No 8 VG Access read/write VG Status resizable MAX LV 0 Cur LV 2 Open LV 0 Max PV 0 Cur PV 1 Act PV 1 VG Size 1.82 TiB PE Size 64.00 MiB Total PE 29808 Alloc PE / Size 16388 / 1.00 TiB Free PE / Size 13420 / 838.75 GiB VG UUID qAn87V-alZH-uhHu-RbGF-g7CM-Fyx2-NUt2sk # lvdisplay WARNING: lvmetad is running but disabled. Restart lvmetad before enabling it! connect() failed on local socket: No such file or directory Internal cluster locking initialisation failed. WARNING: Falling back to local file-based locking. Volume Groups with the clustered attribute will be inaccessible. --- Logical volume --- LV Name tpool VG Name storage LV UUID K7sGmc-qkU2-P9Kq-Tynm-clf1-ecIl-5RZGHE LV Write Access read/write LV Creation host, time medusa, 2014-11-26 15:57:44 +0100 LV Pool metadata tpool_tmeta LV Pool data tpool_tdata LV Status available # open 2 LV Size 1.00 TiB Allocated pool data 0.00% Allocated metadata 0.43% Current LE 16384 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 254:2 --- Logical volume --- LV Path /dev/storage/volume LV Name volume VG Name storage LV UUID 2XA1WV-QzZu-r0dF-EsOm-5wD8-sF1M-sKmo3g LV Write Access read/write LV Creation host, time medusa, 2014-11-26 15:57:49 +0100 LV Pool name tpool LV Status available # open 0 LV Size 512.00 GiB Mapped size 0.00% Current LE 8192 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 254:4 -- You are receiving this mail because: You are on the CC list for the bug.

1 6