March 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 760859] New: raid1 with pata and sata disk started as 2 arrays
by bugzilla_noreply＠novell.com 14 Mar '13

14 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=760859 https://bugzilla.novell.com/show_bug.cgi?id=760859#c0 Summary: raid1 with pata and sata disk started as 2 arrays Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: volker3204(a)paradise.net.nz QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.34 (KHTML, like Gecko) konqueror/4.7.2 Safari/534.34 There seems to be a race condition between PATA disk, SATA disk, and a USB flash card reader for which device gets allocated device names in /dev first. If it ends up like # lsscsi [0:0:0:0] disk ATA SAMSUNG HD103UJ 1AA0 /dev/sda [4:0:0:0] disk Generic IC1210 CF 1.9C /dev/sdb [4:0:0:1] disk Generic IC1210 MS 1.9C /dev/sdc [4:0:0:2] disk Generic IC1210 MMC/SD 1.9C /dev/sdd [4:0:0:3] disk Generic IC1210 SM 1.9C /dev/sde [5:0:0:0] disk ATA ST3120026A 3.06 /dev/sdf after the raid1 was created with the two disks as /dev/sd[ab] then two separate arrays are started, both degraded. It used to work fine before systemd, or up to 11.1 (didn't try with 11.[234]), but 12.1 is broken. # cat /etc/mdadm.conf DEVICE containers partitions ARRAY /dev/md/linux1:system UUID=2276a9a1:da6d0888:554fa14a:f4f32b37 ARRAY /dev/md/linux1:home UUID=ae0f83e0:3304dfea:feed7f14:ef394574 # mdadm -Ds ARRAY /dev/md126 metadata=1.0 name=linux1:system UUID=2276a9a1:da6d0888:554fa14a:f4f32b37 ARRAY /dev/md/linux1:home metadata=1.2 name=linux1:home UUID=ae0f83e0:3304dfea:feed7f14:ef394574 ARRAY /dev/md/linux1:home metadata=1.2 name=linux1:home UUID=ae0f83e0:3304dfea:feed7f14:ef394574 Initrd contains # t etc/mdadm.conf AUTO -all ARRAY /dev/md126 metadata=1.0 name=linux1:system UUID=2276a9a1:da6d0888:554fa14a:f4f32b37 The problem occurs only with the second array for /home, not the first array for / . Reproducible: Always Steps to Reproduce: 1. Set up system as described. 2. Reboot several times, examining raid status each time. 3. Actual Results: 1 raid1 array started with 2 active disks for rootfs. 2 raid1 arrays started with 1 active disk each, both degraded. Both arrays have the same array UUID. Expected Results: 2 raid1 arrays started, both with 2 active disks. -- 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 34

[Bug 808295] New: "jsmeix" can no longer review pending changes for openSUSE Wiki articles
by bugzilla_noreply＠novell.com 14 Mar '13

14 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=808295 https://bugzilla.novell.com/show_bug.cgi?id=808295#c0 Summary: "jsmeix" can no longer review pending changes for openSUSE Wiki articles Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: All OS/Version: All Status: NEW Severity: Normal Priority: P5 - None Component: Wiki AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jsmeix(a)suse.com QAContact: adrian(a)suse.com Found By: Community User Blocker: No My openSUSE user is "jsmeix". I can no longer review pending changes for openSUSE Wiki articles. When I try it I get only "Action failed" shown as title of the tab in my browser (Firefox) where I tried to review the Wiki article. There is no (error)-message or anything which indicates why the "Action failed". For example currently https://en.opensuse.org/SDB:How_to_set-up_a_HP_printer has pending changes where it fails as described above. Review pending changes has worked well in the past for me but since a longer time it failed as described above from time to time but sometimes it still worked. Since some time it now fails in any case. I tried with different Firefox versions under different openSUSE versions at work and even with an up to date Firefox under Windows 7 at home but it fails everywhere in the same way. Therefore I assume it is not my fault. -- 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 614646] New: zypper useColor = autodetect crash
by bugzilla_noreply＠novell.com 14 Mar '13

14 Mar '13

http://bugzilla.novell.com/show_bug.cgi?id=614646 http://bugzilla.novell.com/show_bug.cgi?id=614646#c0 Summary: zypper useColor = autodetect crash Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: lnussel(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.1.9) Gecko/20100317 SUSE/3.5.9-0.1.1 Firefox/3.5.9 when I enable useColor in zypper.conf ('autodetect' or 'always') zypper aborts: # zypper ref terminate called after throwing an instance of 'std::logic_error' what(): basic_string::_S_construct NULL not valid Aborted # echo $TERM linux Happens with any command. # rpm -q zypper libzypp zypper-1.4.4-1.1.i586 libzypp-7.6.0-1.2.i586 Reproducible: Always -- 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 16

[Bug 687530] New: in proper parsing of the /etc/zypp/zypper.conf
by bugzilla_noreply＠novell.com 14 Mar '13

14 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=687530 https://bugzilla.novell.com/show_bug.cgi?id=687530#c0 Summary: in proper parsing of the /etc/zypp/zypper.conf Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: mrueckert(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- "installRecommends = no " with that trailing space the option will not be parsed properly and it will still pull in recommended packages. additional the output in the zypper.log is kind of confusing. dontinstallrecommended=1 <- it will install recommends dontinstallrecommended=0 <- it wont install recommends last but not least Michael Andres was wondering why zypper has its own config anyway. it shouldnt have options that are already handled in /etc/zypp/zypp.conf. -- 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 9

[Bug 765164] New: creating of initrd fails
by bugzilla_noreply＠novell.com 14 Mar '13

14 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=765164 https://bugzilla.novell.com/show_bug.cgi?id=765164#c0 Summary: creating of initrd fails Classification: openSUSE Product: openSUSE 12.2 Version: Beta 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: foren(a)nuxli.ch QAContact: jsrain(a)suse.com Found By: Beta-Customer Blocker: --- With a clean install of openSUSE 12.2 Beta 1, the installation of the bootloader (grub2) fails when creating initrd with the following message: ---- Kernel image: /boot/vmlinuz-3.4.0-2-desktop Initrd image: /boot/initrd-3.4.0-2-desktop KMS drivers: i915 Root device: /dev/sda2 (mounted on / as ext4) Kernel modules: thermal_sys thermal processor fan scsi_dh scsi_dh_auls scsi_dh_emc scsi_sh_hp_sw scsi_dh_rdac video button ic2-algo-bit drm drm_helper i915 hid_logitec-dj Features: acpi kms block usb resume.userspace resume.kernel Perl-Bootloader: 2012-06-01 22:23:53 ERROR: Core::ReadFiles: Failed to open /boot/grub2/device.map Can't use an undefined calue as a HASH reference at /usr/lib/perl5/vendor_perl5/5.14.2/bootloader/Core/GRUB2.pm line 1023. There was an error generating the initrd (2) ---- Additional information: Lenovo x220, selected language: German, configured grub not to set boot flag and not to write to MBR but to boot from boot partition. New to beta testing, I hope I gave all informations needed. :-) -- 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 28

[Bug 761985] New: Errors in comments of zypp.conf
by bugzilla_noreply＠novell.com 14 Mar '13

14 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=761985 https://bugzilla.novell.com/show_bug.cgi?id=761985#c0 Summary: Errors in comments of zypp.conf Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: All OS/Version: All Status: NEW Severity: Minor Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: avm-xandry(a)yandex.ru QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=490601) --> (http://bugzilla.novell.com/attachment.cgi?id=490601) Patch for zypp.conf User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.19 (KHTML, like Gecko) Chrome/18.0.1025.168 Safari/535.19 In /etc/zypp/zypp.conf i found a two errors in comment. First: "This optin returns the number of testcases to keep on the system." - "optin"? I think should be "option". Two: "Whetever to apply locks in locks file after zypp start." - here a word "Whetever". Should be "Whatever". I attached patch file. $ diff Software/zypp.conf Software/zypp.conf.new 320c320 < ## This optin returns the number of testcases to keep on the system. Old --- > ## This option returns the number of testcases to keep on the system. Old 406c406 < ## Whetever to apply locks in locks file after zypp start. --- > ## Whatever to apply locks in locks file after zypp start. Reproducible: Always Steps to Reproduce: 1. Install libzypp 2. grep optin /etc/zypp/zypp.conf 3. grep Whetever /etc/zypp/zypp.conf Expected Results: Returns ## This optin returns the number of testcases to keep on the system. Old and ## Whetever to apply locks in locks file after zypp start. -- 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 722551] New: zypper verify says it supports --recommends, but it doesn't
by bugzilla_noreply＠novell.com 14 Mar '13

14 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=722551 https://bugzilla.novell.com/show_bug.cgi?id=722551#c0 Summary: zypper verify says it supports --recommends, but it doesn't Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: jnelson-suse(a)jamponi.net QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0) Gecko/20100101 Firefox/7.0 See the following transcript: localhost:~ # zypper verify -h verify (ve) [options] Check whether dependencies of installed packages are satisfied and repair eventual dependency problems. Command options: -r, --repo <alias|#|URI> Load only the specified repository. --no-recommends Do not install recommended packages, only required. --recommends Install also recommended packages in addition to the required. -D, --dry-run Test the repair, do not actually do anything to the system. --download Set the download-install mode. Available modes: only, in-advance, in-heaps, as-needed -d, --download-only Only download the packages, do not install. localhost:~ # zypper verify --recommends Unknown option '--recommends' localhost:~ # 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 13

[Bug 801423] New: systemd crashed while starting dhcpd with Assertion 's->state == SERVICE_START || s->state == SERVICE_START_POST' failed
by bugzilla_noreply＠novell.com 13 Mar '13

13 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=801423 https://bugzilla.novell.com/show_bug.cgi?id=801423#c0 Summary: systemd crashed while starting dhcpd with Assertion 's->state == SERVICE_START || s->state == SERVICE_START_POST' failed Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: openSUSE 12.1 Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: stefan.muenkner(a)mx.uni-saarland.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=522782) --> (http://bugzilla.novell.com/attachment.cgi?id=522782) backtrace via dumped core User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 On my server systemd crashed yesterday in the middle of the night, while (most probably) trying do a scheduled restart of the dhcp-daemon via crontab. dhcpd was not restarted. The system was still working (seemingly) without any problems, but any usage of systemctl failed with: "Failed to get D-Bus connection: Failed to connect to socket /org/freedesktop/systemd1/private: Connection refused" (see the logs for more detailed infos) Consequently, since I was not able to restore the connection to the D-Bus service, the server could not be shutdown normally, the only way apart from a hard reset was using Alt+SysReq. This has the potential to cause data loss!!!! As a consequence I switched back to the standard SysV init. Reproducible: Didn't try The crontab entry leading to it: 26 3 * * * /usr/sbin/rcdhcpd restart from the logs : Jan 30 03:26:03 myserver systemd[1]: Assertion 's->state == SERVICE_START || s->state == SERVICE_START_POST' failed at src/service.c:2715, function service_fd_event(). Aborting. Jan 30 03:26:03 myserver systemd[1]: Caught <ABRT>, dumped core as pid 28315. Jan 30 03:26:03 myserver systemd[1]: Freezing execution. Jan 30 04:13:25 myserver systemd-logind[9265]: Removed session c24. lines Jan 30 03:26:03 myserver systemd[1]: Freezing execution. <-- snip - snip --> an 30 10:08:36 myserver systemd-cgroups-agent[2915]: Failed to get D-Bus connection: Failed to connect to socket /org/freedesktop/systemd1/private: Connection refused Jan 30 10:08:43 myserver systemd-cgroups-agent[2919]: Failed to get D-Bus connection: Failed to connect to socket /org/freedesktop/systemd1/private: Connection refused Jan 30 10:08:44 myserver systemd-cgroups-agent[2921]: Failed to get D-Bus connection: Failed to connect to socket /org/freedesktop/systemd1/private: Connection refused Jan 30 10:08:45 myserver systemd-cgroups-agent[2923]: Failed to get D-Bus connection: Failed to connect to socket /org/freedesktop/systemd1/private: Connection refused Jan 30 10:08:46 myserver systemd-cgroups-agent[2925]: Failed to get D-Bus connection: Failed to connect to socket /org/freedesktop/systemd1/private: Connection refused Jan 30 10:08:52 myserver systemd-cgroups-agent[2927]: Failed to get D-Bus connection: Failed to connect to socket /org/freedesktop/systemd1/private: Connection refused -- 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 808614] New: RN: openSUSE 12.3 update wanted
by bugzilla_noreply＠novell.com 13 Mar '13

13 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=808614 https://bugzilla.novell.com/show_bug.cgi?id=808614#c0 Summary: RN: openSUSE 12.3 update wanted Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: Other Status: ASSIGNED Severity: Enhancement Priority: P5 - None Component: Release Notes AssignedTo: ke(a)suse.com ReportedBy: ke(a)suse.com QAContact: coolo(a)suse.com Depends on: 804773,808104,808108,808111,808116,808595 Found By: Documentation Blocker: --- Collection bugs here... -- 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 808595] New: release notes: bug in double signing shim
by bugzilla_noreply＠novell.com 13 Mar '13

13 Mar '13

https://bugzilla.novell.com/show_bug.cgi?id=808595 https://bugzilla.novell.com/show_bug.cgi?id=808595#c0 Summary: release notes: bug in double signing shim Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Release Notes AssignedTo: ke(a)suse.com ReportedBy: lnussel(a)suse.com QAContact: coolo(a)suse.com CC: glin(a)suse.com, mlin(a)suse.com Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #808594 +++ See bug 808594 for description. If the openSUSE 12.3 medium does not boot on future secure boot enabled hardware the user has to temporarily disable secure boot, install openSUSE and apply all online updates to get an updated shim. After that secure boot can be turned on again. -- 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