October 2012 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 783444] New: mkinitrd fails to produce correct mdadm.conf for initrd.
by bugzilla_noreply＠novell.com 17 Oct '12

17 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=783444 https://bugzilla.novell.com/show_bug.cgi?id=783444#c0 Summary: mkinitrd fails to produce correct mdadm.conf for initrd. Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: All OS/Version: openSUSE 12.2 Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: gadm(a)avalon-island.ru QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/21.0.1200.0 Iron/21.0.1200.0 Safari/537.1 Due to bug in /lib/mkinitrd/scripts/setup-md.sh 'mkinitrd' fails to form correct configuration file for initrd, thus leading operating system to be non-bootable. Reproducible: Always Steps to Reproduce: 1. Set up Intel ICH partitionable RAID 2. Set up openSUSE on it 3. Reboot and check that reboot failed. Actual Results: The system should boot normally. Expected Results: System is in non-bootable state: LVM fails to find its physical volumes. By default, 'echo' does NOT recognise escape sequences, as such, line formed by previous script lines ("ARRAY ... \\nUUID= ...) will be put in mdadm.conf LITERALLY, that's obviously wrong. mdadm chokes and bails out. Fix is rather trivial: just add '-e' as first argument to 'echo' in line 95 of script. -- 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 5

[Bug 780935] New: installation produces incorrect mdadm.conf in initrd
by bugzilla_noreply＠novell.com 17 Oct '12

17 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=780935 https://bugzilla.novell.com/show_bug.cgi?id=780935#c0 Summary: installation produces incorrect mdadm.conf in initrd Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ben.ellis(a)familycourt.gov.au QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20100101 Firefox/14.0.1 After installation, the pc reboots and fails to load the OS saying it is waiting for partitions to wake(?). The system is configured with 4x2TB disks in RAID 5. I've booted into rescue mode and opened up the initrd and found the mdadm.conf which contains the following AUTO -all ARRAY /dev/md/imsm0 metadata=imsm UUID=1980e81b:1611decb:a93affc5:d433ba73 ARRAY /dev/md126 container=/dev/md/imsm0 member=0 UUID=dd19099b:51b09297:916172fe:5a1f6582 running "mdadm --examine --scan" provides the following ARRAY metadata=imsm UUID=1980e81b:1611decb:a93affc5:d433ba73 ARRAY /dev/md/SYSTEM container=1980e81b:1611decb:a93affc5:d433ba73 member=0 UUID=dd19099b:51b09297:916172fe:5a1f6582 ARRAY /dev/md/DATA container=1980e81b:1611decb:a93affc5:d433ba73 member=1 UUID=cf946b3b:ea30a129:e8b32923:b4a3ffce after updating the mdadm.conf in the initrd and rebooting the system starts correctly. lspci produces the following 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09) 00:01.1 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5) 00:1c.3 PCI bridge: Intel Corporation 82801 PCI Bridge (rev b5) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation Z68 Express Chipset Family LPC Controller (rev 05) 00:1f.2 RAID bus controller: Intel Corporation 82801 SATA Controller [RAID mode] (rev 05) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05) 01:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GF110 High Definition Audio Controller (rev a1) 02:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560] (rev a1) 02:00.1 Audio device: NVIDIA Corporation GF110 High Definition Audio Controller (rev a1) 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06) 04:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 04) 05:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 04) 06:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge (rev 01) parted -l shows the following Model: ATA ST2000DL003-9VT1 (scsi) Disk /dev/sda: 2000GB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 197kB 1078MB 1077MB primary boot, type=83 2 1078MB 270GB 268GB primary type=07 3 270GB 287GB 17.2GB primary type=82 4 287GB 537GB 250GB primary type=83 Error: /dev/sdb: unrecognised disk label Model: ATA ST2000DL003-9VT1 (scsi) Disk /dev/sdb: 2000GB Sector size (logical/physical): 512B/512B Partition Table: unknown Error: /dev/sdc: unrecognised disk label Model: ATA ST2000DL003-9VT1 (scsi) Disk /dev/sdc: 2000GB Sector size (logical/physical): 512B/512B Partition Table: unknown Model: ATA ST2000DL003-9VT1 (scsi) Disk /dev/sdd: 2000GB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 197kB 1078MB 1077MB primary boot, type=83 2 1078MB 270GB 268GB primary type=07 3 270GB 287GB 17.2GB primary type=82 4 287GB 537GB 250GB primary type=83 Warning: Unable to open /dev/sr0 read-write (Read-only file system). /dev/sr0 has been opened read-only. Error: Can't have a partition outside the disk! Model: HL-DT-ST BDDVDRW CH12LS28 (scsi) Disk /dev/sr0: 4669MB Sector size (logical/physical): 2048B/2048B Partition Table: unknown Model: Linux Software RAID Array (md) Disk /dev/md125: 537GB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 197kB 1078MB 1077MB primary ext4 boot, type=83 2 1078MB 270GB 268GB primary ntfs type=07 3 270GB 287GB 17.2GB primary linux-swap(v1) type=82 4 287GB 537GB 250GB primary ext4 type=83 Model: Linux Software RAID Array (md) Disk /dev/md126: 5464GB Sector size (logical/physical): 512B/512B Partition Table: gpt Number Start End Size File system Name Flags 1 197kB 1100GB 1100GB ext4 primary 2 1100GB 5464GB 4365GB ntfs primary Reproducible: Always Steps to Reproduce: 1. install opensuse 12.2 (or 12.1) 2. use the existing partitions - software choices seem irrelevant 3. use the default boot loader (this works properly) 4. reboot after OS has been installed for part 2 5. failure message appears Actual Results: unable to find the partitions to boot the system Expected Results: a running system Please let me know if you require a screenshot of the actual errors or further information. This has happened in 12.1 as well as 12.2 -- 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 16

[Bug 783766] New: openSUSE:12.2:Update/patchinfo.949: Bug
by bugzilla_noreply＠novell.com 17 Oct '12

17 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=783766 https://bugzilla.novell.com/show_bug.cgi?id=783766#c0 Summary: openSUSE:12.2:Update/patchinfo.949: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Critical Priority: P5 - None Component: 3rd party software AssignedTo: dmueller(a)suse.com ReportedBy: boris.prestel(a)cosbi.de QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- After updating to mdadm 3.2.5-3-13-1-x86_64 from the official update i am no longer able to boot the system. Error message, after grub menu appears, shows: Waiting for device /dev/root ........ My System is a Sony Vaio Z Notebook with an Intel Fake Raid Controller: lspci | grep Intel | grep RAID 00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 05) I have two SSD in RAID 0 The only way, i found to get back to a running system was to downgrade mdadm to version 3.2.5-3.4.1 -- 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 747122] New: starting firefox causes kernel panic with latest update kernel
by bugzilla_noreply＠novell.com 17 Oct '12

17 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=747122 https://bugzilla.novell.com/show_bug.cgi?id=747122#c0 Summary: starting firefox causes kernel panic with latest update kernel Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: Linux Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: ohering(a)suse.com QAContact: qa(a)suse.de Found By: Outsourced Testing Blocker: --- 11.4-x86_64 on HP ProBook 6555b with all updates applied The current kernel-desktop and/or FireFox 10.0.1 update causes a kernel panic when starting FireFox (it opens two windows with a couple of tabs from the previous session). I will try to capture it via serial console. -- 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 47

[Bug 785538] New: home:wrosenauer/sslh: Bug
by bugzilla_noreply＠novell.com 17 Oct '12

17 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=785538 https://bugzilla.novell.com/show_bug.cgi?id=785538#c0 Summary: home:wrosenauer/sslh: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: 3rd party software AssignedTo: wolfgang(a)rosenauer.org ReportedBy: spiollinux(a)alice-dsl.net QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- libconfig.so.9 is missing. Why don't you aggregate it to your repo (see http://en.opensuse.org/openSUSE:Build_Service_Tutorial#Terminology)? Adding a multimedia repo is kind of dumb in a server installation. -- 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 713584] New: bogus logrotate config for syslogd
by bugzilla_noreply＠novell.com 17 Oct '12

17 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=713584 https://bugzilla.novell.com/show_bug.cgi?id=713584#c0 Summary: bogus logrotate config for syslogd Classification: openSUSE Product: openSUSE 12.1 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: ro(a)suse.com QAContact: qa(a)suse.de Found By: Development Blocker: --- see also bug#713581 for apache2 the two upper sections should probably be merged, the whole config is identical and this way we can save at least one "rcsyslog reload" during rotation. I'm not sure how solid all our syslog implementations are for "rcsyslog reload", possibly we also want a sleep after the reload to make sure the reloads do not overlap (in case something backgrounded is done during this graceful restart) -- 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 5

[Bug 783152] New: zfs-fuse wont start at boot time but starts properly if started manually
by bugzilla_noreply＠novell.com 17 Oct '12

17 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=783152 https://bugzilla.novell.com/show_bug.cgi?id=783152#c0 Summary: zfs-fuse wont start at boot time but starts properly if started manually Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: kaspernasebaer(a)gmx.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Opera/9.80 (Windows NT 6.1; WOW64; U; en) Presto/2.10.289 Version/12.02 My system has 3.2GHz and a ssd drive holding all system partitions. There is a zfs pool consisting of four normad HDs. zfs-fuse is set active fpr runlevel 2,3,5 in yast runlevel editor. After booting zfs filesystem is not available because the zfs-fuse daemon is not started. If started manually by "# rczfs-fuse start" no errors occur an the daemon starts up correctly Reproducible: Always Steps to Reproduce: 1. Install zfs-fuse package 2. create a pool on a physical device, e.g. /dev/sdb 3. enable service in runlevel editor 4. reboot twice Actual Results: Service does not start automatically at boot. All zfs-fuse related data is not available. Expected Results: service starts at boot The problem is related to the system init process and the zfs-fuse initscript. The /etc/init.d/zfs-fuse is writing its pidfile into /var/run... before the tmpfs. Later, the pidfile is hidden. The system log shows this messages: WARNING: /var/run/zfs/zfs-fuse.pid already exists; aborting. Changing the pidfile to "/run/zfs-fuse.pid" inside the initscript gets me a bit further, but startup still does not work: Starting zfs-fuse daemonconnect: No such file or directory Please make sure that the zfs-fuse daemon is running. internal error: failed to initialize ZFS library ..done Adding $local_fs and $time to the "# Required-Start:" line is a workarround which works for me but appears not to be the ultimate solution. -- 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 785232] New: NetworkManager drops network connection periodically if IPv6 is set up
by bugzilla_noreply＠novell.com 17 Oct '12

17 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=785232 https://bugzilla.novell.com/show_bug.cgi?id=785232#c0 Summary: NetworkManager drops network connection periodically if IPv6 is set up Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: All OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: wolfgang(a)rosenauer.org QAContact: qa-bugs(a)suse.de Found By: Community User Blocker: --- My network is properly set up for IPv6 internal and global connection (aka having an IPv6 router). Since I've upgraded to 12.2 NetworkManager reconnected every 20 minutes (the 20 minutes are most likely determined from timeout values of the IPv6 router advertisement and might differ for other users). This is actually critical since that means I'm losing my VPN connection every 20 minutes. I only use "Major" because the interval might be longer for other people but basically everyone using IPv6 with autoconfiguration will be affected I guess. My log shows quite some messages like this: ICMPv6 RA: ndisc_router_discovery() failed to add default route. So I found on the net: https://bugzilla.redhat.com/show_bug.cgi?id=785772 http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=77de91… To verify I've updated to NetworkManager 0.9.6 from G:S:36 which shows no unexpected network reconnects for the time being. I strongly recommend to either backport the fix or update to 0.9.6 on 12.2. -- 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 2

[Bug 733868] New: openSUSE 12.1 syslog rotation fails
by bugzilla_noreply＠novell.com 17 Oct '12

17 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=733868 https://bugzilla.novell.com/show_bug.cgi?id=733868#c0 Summary: openSUSE 12.1 syslog rotation fails Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: cbenson(a)fhcrc.org QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0.1) Gecko/20100101 Firefox/8.0.1 Normal log rotation of /var/log/messages fails because this command no longer works in 12.1: "/etc/init.d/syslog reload" /var/log/messages shows: Nov 30 04:00:03 rhino-b logrotate: redirecting to systemctl Nov 30 04:00:03 rhino-b logrotate: Failed to issue method call: Unit syslog.service failed to load: No such file or directory. See system logs and 'systemctl status syslog.service' for details. This can also be reproduced at the command line: /root # systemctl reload syslog.service Failed to issue method call: Unit syslog.service failed to load: No such file or directory. See system logs and 'systemctl status syslog.service' for details. However, this does still work: /root # cd /etc/init.d /etc/init.d # ./syslog reload redirecting to systemctl Reload syslog service The log daemon is rsyslog: /root # ps -ef | grep syslog | grep -v grep root 324 1 0 Nov17 ? 00:00:00 /lib/systemd/systemd-kmsg-syslogd root 418 1 0 Nov17 ? 00:00:00 /lib/systemd/systemd-stdout-syslog-bridge root 12456 1 0 14:01 ? 00:00:00 /sbin/rsyslogd -c 5 -f /etc/rsyslog.conf I have the following conf files for rsyslog: /etc # ls -ld rsyslog* -rw------- 1 root root 4027 Nov 26 06:30 rsyslog.conf drwxr-xr-x 2 root root 4096 Nov 3 07:42 rsyslog.d -rw------- 1 root root 4027 Nov 15 10:07 rsyslog.early.conf Reproducible: Always Steps to Reproduce: 1.systemctl reload syslog.service 2.OR: /etc/init.d/syslog reload 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 9

[Bug 752422] New: bash: path completion converts paths to absolute
by bugzilla_noreply＠novell.com 17 Oct '12

17 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=752422 https://bugzilla.novell.com/show_bug.cgi?id=752422#c0 Summary: bash: path completion converts paths to absolute Classification: openSUSE Product: openSUSE 12.2 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: jslaby(a)suse.com QAContact: qa-bugs(a)suse.de CC: werner(a)suse.com Found By: --- Blocker: --- cd /home ls xsla<TAB> ls xslaby/<TAB> ls /home/xslaby/<TAB> <-- WTF? $ rpm -qf /etc/bash_completion.d/*|sort -u dbus-1-glib-0.98-4.2.x86_64 dconf-0.11.5-1.4.x86_64 git-core-1.7.9.2-1.1.x86_64 glib2-tools-2.31.18-1.1.x86_64 grub2-1.99-16.1.x86_64 PackageKit-0.7.2-2.2.x86_64 scout-0.1.0-48.2.noarch systemd-43-3.1.x86_64 yast2-2.22.4-1.2.x86_64 zypper-1.7.0-4.1.x86_64 -- 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 18