November 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 903897] New: Error reported during boot, but no error to be found
by bugzilla_noreply＠novell.com 05 Nov '14

05 Nov '14

http://bugzilla.opensuse.org/show_bug.cgi?id=903897 Bug ID: 903897 Summary: Error reported during boot, but no error to be found Classification: openSUSE Product: openSUSE Factory Version: 201410* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: freek(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When booting Factory snapshot 20141102 one of the first lines on the screen is: [FAILED] Failed to start Load Kernel Modules. See "systemctl status systemd-modules-load.service" for details. FAILED is in RED. Giving this command does not reveal any problem. # systemctl status systemd-modules-load.service systemd-modules-load.service - Load Kernel Modules Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static) Active: active (exited) since di 2014-11-04 12:04:22 CET; 12h ago Docs: man:systemd-modules-load.service(8) man:modules-load.d(5) Process: 388 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=0/SUCCESS) Main PID: 388 (code=exited, status=0/SUCCESS) CGroup: /system.slice/systemd-modules-load.service -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 899674] New: version 20141001: Grub error at second boot (i.e. after installation has been completed)
by bugzilla_noreply＠novell.com 05 Nov '14

05 Nov '14

http://bugzilla.opensuse.org/show_bug.cgi?id=899674 Bug ID: 899674 Summary: version 20141001: Grub error at second boot (i.e. after installation has been completed) Classification: openSUSE Product: openSUSE Factory Version: 201409* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: h.w.schreuder(a)ziggo.nl QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Installation of 13.2-20141001 using ext4 for /, no separate /home. "First boot", near the end of installation, went fine; logging in at KDE also. No actions in the newly installed system, except shutdown and reboot. This results in a black screen with the text "Grub". During installation, boot parameters were specified as follows: MBR not touched, Grub to be installed in /. Reproduction: good: same behaviour on three installs. Remedy: on installation, do NOT install Grub in / (and do nothing in MBR). Since the computer has several bootable linus systems, it is then booted using a pre-existing instance of Grub. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 903520] New: sensors fancontrol service status spam after start: fancontrol: /usr/sbin/fancontrol: line 481: [: too many arguments
by bugzilla_noreply＠novell.com 05 Nov '14

05 Nov '14

http://bugzilla.opensuse.org/show_bug.cgi?id=903520 Bug ID: 903520 Summary: sensors fancontrol service status spam after start: fancontrol: /usr/sbin/fancontrol: line 481: [: too many arguments Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: x86-64 OS: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: zombah(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, I generated fancontrol config for my motherboard (asrock e350m1) with pwmconfig from sensors-3.3.4-3.1.2.x86_64 package on openSUSE 13.1, but after fancontrol service start, systemd status for fancontrol service spam messages like this: Nov 01 06:58:19 hamtaro.site fancontrol[2481]: /usr/sbin/fancontrol: line 481: [: too many arguments Nov 01 06:58:29 hamtaro.site fancontrol[2481]: /usr/sbin/fancontrol: line 481: [: too many arguments Nov 01 06:58:39 hamtaro.site fancontrol[2481]: /usr/sbin/fancontrol: line 481: [: too many arguments Here is content of /etc/fancontrol that pwmconfig created: # Configuration file generated by pwmconfig, changes will be lost INTERVAL=10 DEVPATH=hwmon2=devices/pci0000:00/0000:00:18.3 hwmon3=devices/platform/w83627ehf.656 DEVNAME=hwmon2=k10temp hwmon3=nct6775 FCTEMPS=hwmon3/device/pwm2=hwmon2/device/temp1_input FCFANS= hwmon3/device/pwm2= MINTEMP=hwmon3/device/pwm2=40 MAXTEMP=hwmon3/device/pwm2=65 MINSTART=hwmon3/device/pwm2=128 MINSTOP=hwmon3/device/pwm2=57 -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 903841] SEPOLICY is asking for YUM
by bugzilla_noreply＠novell.com 05 Nov '14

05 Nov '14

http://bugzilla.novell.com/show_bug.cgi?id=903841 Marcus Meissner <meissner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|security-team(a)suse.de |jsegitz(a)novell.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 851229] apache2-itk mpm doesn't exists in build for 13.1
by bugzilla_noreply＠novell.com 05 Nov '14

05 Nov '14

http://bugzilla.suse.com/show_bug.cgi?id=851229 --- Comment #25 from Petr Gajdos <pgajdos(a)suse.com> --- I have notified Apache:Modules maintainer to set build for 13.2. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 851229] apache2-itk mpm doesn't exists in build for 13.1
by bugzilla_noreply＠novell.com 05 Nov '14

05 Nov '14

http://bugzilla.suse.com/show_bug.cgi?id=851229 --- Comment #24 from Vladimir Perepechin <vovochka13(a)gmail.com> --- So, will it be available for 13.2? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 832501] boot on raid device is not started if degraded; fix provided
by bugzilla_noreply＠novell.com 05 Nov '14

05 Nov '14

http://bugzilla.opensuse.org/show_bug.cgi?id=832501 Neil Brown <nfbrown(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(jjletho67-esus@ya | |hoo.it) --- Comment #28 from Neil Brown <nfbrown(a)suse.com> --- Strange... The rdosreport.txt log reports: [ 144.094926] linux-m61d systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-1f3d0926\x2da660\x2d45a6\x2da2b0\x2dbfdf165d64b5.device. But also shows /dev/disk/by-uuid: ... lrwxrwxrwx 1 root 0 10 Oct 15 12:12 1f3d0926-a660-45a6-a2b0-bfdf165d64b5 -> ../../dm-0 So it clearly find the device, but maybe not soon enough for systemd. This dm-0 is an LVM partition in md2, which is a degraded raid1. As it is degraded it isn't started immediately - not until /sbin/mdraid_start is called. That is scheduled to run at a timeout by a udev rules file: etc/udev/rules.d/65-md-incremental-imsm.rules:RUN+="/sbin/initqueue --timeout --name 50-mdraid_start --onetime --unique /sbin/mdraid_start" This will be after the normal lvm scan, but there is a secondary lvm scan similarly scheduled by a timeout. etc/udev/rules.d/64-lvm.rules:RUN+="/sbin/initqueue --timeout --name 51-lvm_scan --onetime --unique /sbin/lvm_scan --partial" So the md device should be assemboed by "50-mdraid_start" and the lvm device by "51-lvm_scan", and as "51" comes after "50", this should happen in the right order. The log confirms this: [ 143.256336] linux-m61d kernel: md/raid1:md2: active with 1 out of 2 mirrors ... [ 144.553192] linux-m61d dracut-initqueue[270]: Scanning devices md2 for LVM logical volumes SystemVG/rootLV The problem is that systemd complains between these two: [ 144.094926] linux-m61d systemd[1]: Timed out waiting for device dev-disk-by\x2duuid-1f3d0926\x2da660\x2d45a6\x2da2b0\x2dbfdf165d64b5.device. I guess the systemd timeout must be only a tiny bit longer than the initqueue timeout. The initqueue timeout is 2*$RDRETRY/3 where RDRETRY is 180 (by default). So 120 seconds. The default timeout for devices seems to be 90 seconds - set by the DefaultTimeoutStartSec value. But that doesn't really seem to line up, so I must be missing something. Can you try booting with rd.timeout=180 added to the command line args? If that works, it will at least hint that I'm on the right track. I might try to set something up myself to test ... if I find time. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 903911] New: DVD install doesn't install GTK YaST interface
by bugzilla_noreply＠novell.com 05 Nov '14

05 Nov '14

http://bugzilla.opensuse.org/show_bug.cgi?id=903911 Bug ID: 903911 Summary: DVD install doesn't install GTK YaST interface Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: roger.luedecke(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Had to install GTK interface manually. WOrked immediately after installing. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 903736] disk device name changed after update 13.1->13.2, grub2 can not load initrd, system does not boot
by bugzilla_noreply＠novell.com 05 Nov '14

05 Nov '14

http://bugzilla.opensuse.org/show_bug.cgi?id=903736 Michael Chang <mchang(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |thomas.blume(a)suse.com Flags| |needinfo?(thomas.blume@suse | |.com) --- Comment #4 from Michael Chang <mchang(a)suse.com> --- Hi Thomas, Do you have any idea as to why udev changes the by-id link name after system upgrade from 13.1 to 13.2? Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 903736] disk device name changed after update 13.1->13.2, grub2 can not load initrd, system does not boot
by bugzilla_noreply＠novell.com 05 Nov '14

05 Nov '14

http://bugzilla.opensuse.org/show_bug.cgi?id=903736 --- Comment #3 from Michael Chang <mchang(a)suse.com> --- The udev unexpectedly changed the disk by-id link name is the root cause. the output flickering or any other trouble in grub is a result of mismatch between embedded images and modules. Due to the name change, grub2-install failed in embedding new core.img to disk so it stayed at grub version in 13.1, while modules in /boot/grub2/i386-pc has been upgraded to 13.2. There's no guarantee for ABI stable for upgrading new version at least. -- You are receiving this mail because: You are on the CC list for the bug.

1 0