July 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 884901] New: Update OpenLP from 2.0.4 to 2.0.5
by bugzilla_noreply＠novell.com 10 Jul '14

10 Jul '14

https://bugzilla.novell.com/show_bug.cgi?id=884901 https://bugzilla.novell.com/show_bug.cgi?id=884901#c0 Summary: Update OpenLP from 2.0.4 to 2.0.5 Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: All OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: joseph(a)mulloy.me QAContact: qa-bugs(a)suse.de 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 Final Release in 2.0 branch. Upstream Minor Bugfix Release Changelog: * Change to BibleGateway URL to use legacy web interface * Issues with Themes when comparing theme files (lp#719514) * Improved error messages with Easy Worship Song Imports (lp#1326664) * Allow more than 26 equal verses within a Song. (lp#1310523) * Handle songs where two optional breaks follow each other. (lp#1296104) * Improve Database update error handling. (lp#1136278) Reproducible: Always -- 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 886484] New: e1000e needs update
by bugzilla_noreply＠novell.com 10 Jul '14

10 Jul '14

https://bugzilla.novell.com/show_bug.cgi?id=886484 https://bugzilla.novell.com/show_bug.cgi?id=886484#c0 Summary: e1000e needs update Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Enhancement Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: armin.herbert(a)atrics.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:30.0) Gecko/20100101 Firefox/30.0 Many recent desktop mainboards have Intel NICs onboard like Intel® Ethernet Connection I218-V (pci id 8086:15a1). This chip is supported by e1000e driver versions higher than 2.4.14. The most recent kernel from openSUSE 13.1, 3.11.10-17, supplies only driver version 2.3.2 The current version of the e1000e driver is 3.0.4 Reproducible: Always Steps to Reproduce: 1. Get mainboard with 8086:15a1 chip 2. install openSUSE 13.1; update ; start yast 3. yast says unsupported chip, lacking firmware Actual Results: modprobe e1000e doesn't detect the chip Expected Results: modprobe e1000e ; ip link list shows interface network driver updates bring other improvements as well, they're usually worth it. -- 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 1

[Bug 878479] New: initrd fails to assemble degraded MD raid1 mirror, root fs not found
by bugzilla_noreply＠novell.com 10 Jul '14

10 Jul '14

https://bugzilla.novell.com/show_bug.cgi?id=878479 https://bugzilla.novell.com/show_bug.cgi?id=878479#c0 Summary: initrd fails to assemble degraded MD raid1 mirror, root fs not found Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: walter.haidinger(a)gmx.at QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0 initrd images created by mkinitrd-2.8.1-2.1.x86_64 fail to assemble a _degraded_ array during boot. I guess this is because md arrays get assembled by udev now. If the md raid1 mirror is synced, there is no problem. Because the raid1 mirror contains the root fs, boot fails due to the root filesystem not being found. As a workaround, I've created the script /lib/mkinitrd/boot/03-md_assemble.sh which just contains: #!/bin/bash /sbin/mdadm --assemble --scan 03-md_assemble.sh is picked up my mkinitrd and run right after 03-md.sh. The array gets assembled although mdadm complains as expected, e.g.: mdadm: /dev/md1 has been started with 1 drive (out of 2). Reproducible: Always Steps to Reproduce: 1. have a degraded raid1 mirror 2. reboot 3. Actual Results: mirror is not assembled, root filesystem is not found Expected Results: start the degraded array, continue to boot -- 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 8

[Bug 879514] New: Waiting for device /dev/1 to appear
by bugzilla_noreply＠novell.com 10 Jul '14

10 Jul '14

https://bugzilla.novell.com/show_bug.cgi?id=879514 https://bugzilla.novell.com/show_bug.cgi?id=879514#c0 Summary: Waiting for device /dev/1 to appear Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: dihewo(a)gmx.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Firefox/24.0 My setup: - /boot on mdadm mirror (two partition) - / on mirrored logical volume (2 mirrored mdadm partitions, volume group on mirror, / and other partitions as valume group) I can start the boot process and after a few messages of failed ata soft resets I get the message: Waiting for device /dev/1 to appear,..... in the ememergency shell I have to assemble the mirror, activate the volume group and create a link from /dev/dm-10 to /dev/1 Then the boot process continues, In that emergency shell (way before systemd emergency mode) I did not see /etc/mdadm.conf though it is in initrd (checked by unpacking it). So the questions: - Where does /dev/1 come from? - Why is the main mirror not created? - Where did /etc/mdadm.conf go on boot? Reproducible: Always Steps to Reproduce: 1. Boot my system :-( (Since I don't know what is going on, I cannot give any clues how to reproduce this error in that rearly state of the boot process) 2. 3. Expected Results: Boot process completion -- 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 4

[Bug 880096] New: NFS having issues
by bugzilla_noreply＠novell.com 10 Jul '14

10 Jul '14

https://bugzilla.novell.com/show_bug.cgi?id=880096 https://bugzilla.novell.com/show_bug.cgi?id=880096#c0 Summary: NFS having issues Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: nfbrown(a)suse.com ReportedBy: msvec(a)suse.com QAContact: qa-bugs(a)suse.de CC: mcaj(a)suse.com Found By: --- Blocker: --- This is a combination of SLES 11 SP3 server and 13.1 client. Server log is full of errors like this: RPC: AUTH_GSS upcall timed out. Please check user daemon is running. And client shows these in random order and quantity: NFS: nfs4_reclaim_open_state: unhandled error -13. Zeroing state NFS: nfs4_reclaim_open_state: Lock reclaim failed! The process on the client hang (basically forever). On the client systemctl status nfs.service also shows this: rpc.idmapd[2767]: nfsdreopen: Opening '/proc/net/rpc/nfs4.nametoid/channel' failed: errno 2 (No such file or directory) rpc.idmapd[2767]: nfsdreopen: Opening '/proc/net/rpc/nfs4.idtoname/channel' failed: errno 2 (No such file or directory) -- 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 6

[Bug 851993] New: boot failure after 12.3 -> 13.1 upgrade if /boot is on RAID
by bugzilla_noreply＠novell.com 10 Jul '14

10 Jul '14

https://bugzilla.novell.com/show_bug.cgi?id=851993 https://bugzilla.novell.com/show_bug.cgi?id=851993#c0 Summary: boot failure after 12.3 -> 13.1 upgrade if /boot is on RAID Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ar16(a)imapmail.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 Starting with a working 12.3 server with boot-on-RAID & lvm-on-RAID for other partitions, I in-place-upgraded to 13.1. There were no errors on upgrade; and a mkinitrd is successful. @reboot, it no longer boots. Appears to hang at an LVM2/Dbus timeout waiting for the /boot device that's on RAID; here's a log snippet: http://pastebin.com/KcNPriuV The upgrade from 12.3 -> 13.3 moves LVM2 from sysvinit to systemd init; the unit files are new. There's at least 1 issue with LVM2 systemd unit (https://forums.opensuse.org/newthread.php?do=newthread&f=668) mdadm 3.3 has issues too (http://www.spinics.net/lists/raid/msg44943.html) There's obviously a dependency problem. Finding/fixing it has been elusive so far. Any suggestions how to specifically identify which dependency is broken? Fyi, all machines I've upgraded 12.3 -> 13.1 with boot&lvm-on-RAID fail in this manner. All machines I've upgraded 12.3 -> 13.1 with boot&LVM, but *NO* RAID, boot without fail. @ forums, a comment: > There was a problem with offline upgrade and raid: the DVD used a > different device name for the raid than the running system, so that the > raid is not found at some point. I don't know if it has been solved points to a possible related comment: ---------------------------------------- Date: Thu, 21 Mar 2013 15:43:37 +0100 From: Claudio ML <> To: opensuse at opensuse.org Subject: [opensuse] Usual problem with upgrade from DVD to 12.3 with system using mdadm Hello all, I have seen there is the same problem of the previous versions of OpenSuSE also into 12.3. The problem is: If you try to upgrade from a DVD an OpenSuSE with software raid (mdadm), the installer don't see the previous version of openSuSE on the hard disk. This is caused because the kernel don't recognize correctly the md arrays. In example, if i have md0 (/ root file system), md1 (/var), md2 (/srv), the installer see this as md125, md126 and md127. So, no DVD upgrade possible for this machines. I have tryied to edit manually the fstab on the machine, adapting to what the installer see, but after the upgrade the system becomes un-bootable. Anyone have a good workaround for this problem? Cordially, Claudio. ---------------------------------------- this, too, may be of interest: Bug 849752 - 13.1RC2 Cannot boot from RAID1 volume(s) https://bugzilla.novell.com/show_bug.cgi?id=849752#c9 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 41

[Bug 885806] New: package mdadm tries to access deprecated (missing) /etc/init.d/mdadm
by bugzilla_noreply＠novell.com 10 Jul '14

10 Jul '14

https://bugzilla.novell.com/show_bug.cgi?id=885806 https://bugzilla.novell.com/show_bug.cgi?id=885806#c0 Summary: package mdadm tries to access deprecated (missing) /etc/init.d/mdadm Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: wagner-thomas(a)gmx.at QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Opera/9.80 (Windows NT 6.1; WOW64; Edition Campaign 21) Presto/2.12.388 Version/12.17 Just did a "zypper dup" and during the mdadm update deprecated/missing /etc/init.d/mdadmd is accessed. (28/30) Installing: mdadm-3.3.1-134.1 ..................................[done] Additional rpm output: Updating /etc/sysconfig/mdadm... /var/tmp/rpm-tmp.FwV8BT: line 8: /etc/init.d/mdadmd: No such file or directory Reproducible: Always # zypper info mdadm Loading repository data... Reading installed packages... Information for package mdadm: ------------------------------ Repository: Base:System Name: mdadm Version: 3.3.1-134.1 Arch: x86_64 Vendor: obs://build.opensuse.org/Base:System Installed: Yes Status: up-to-date Installed Size: 1.1 MiB Summary: Utility for Configuring MD Setup Description: Mdadm is a program that can be used to control Linux md devices. It is intended to provide all the functionality of the mdtools and raidtools programs but with a very different interface. -- 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 1

[Bug 719686] New: Service does not start without portmapper
by bugzilla_noreply＠novell.com 09 Jul '14

09 Jul '14

https://bugzilla.novell.com/show_bug.cgi?id=719686 https://bugzilla.novell.com/show_bug.cgi?id=719686#c0 Summary: Service does not start without portmapper Classification: openSUSE Product: openSUSE 12.1 Version: Milestone 5 Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: f.de.kruijf(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:6.0.2) Gecko/20100101 Firefox/6.0.2 After installation of the packages fam and fam-server one could activate the fam service simply by giving, as root, the command "rcfam start". This is no longer the case. There is an error message in /var/log/messages telling: Sep 22 10:26:55 eik121m5 famd[2572]: can't register with portmapper. So apparently portmapper is now necessary. In openSUSE 11.4 this was not necessary. Reproducible: Always Steps to Reproduce: 1. 2. 3. Actual Results: fam daemon does not start Expected Results: fam daemon does start without portmapper. -- 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 27

[Bug 789894] New: String in module Email server
by bugzilla_noreply＠novell.com 09 Jul '14

09 Jul '14

https://bugzilla.novell.com/show_bug.cgi?id=789894 https://bugzilla.novell.com/show_bug.cgi?id=789894#c0 Summary: String in module Email server Classification: openSUSE Product: openSUSE Factory Version: 12.3 Milestone 1 Platform: Other OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: f.de.kruijf(a)gmail.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20100101 Firefox/16.0 When using the module Email Server, on the page Outgoing Mail, there is a message "The server uses &TLS" one can choose between 3 radio buttons (No, Use, Enforce). This message must be "The server uses TLS", because this message does not have a an associated shortcut. It is more logical to replace Use with Maybe. It is message #322 in mail.pot 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 7

[Bug 430849] The YaST2 DRBD module has an inconsistent way of using case for DRBD/drbd
by bugzilla_noreply＠novell.com 09 Jul '14

09 Jul '14

https://bugzilla.novell.com/show_bug.cgi?id=430849 https://bugzilla.novell.com/show_bug.cgi?id=430849#c4 Freek de Kruijf <freek(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |CLOSED Resolution| |FIXED --- Comment #4 from Freek de Kruijf <freek(a)opensuse.org> 2014-07-09 20:14:51 UTC --- Is OK now. -- 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 0