June 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 821366] New: mdmon doesn't start during boot although RAID 1 is present
by bugzilla_noreply＠novell.com 24 Jun '13

24 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=821366 https://bugzilla.novell.com/show_bug.cgi?id=821366#c0 Summary: mdmon doesn't start during boot although RAID 1 is present Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: HP OS/Version: openSUSE 12.3 Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: klaus.braun(a)geographie.uni-freiburg.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 After installation of two new disks in my new installed opensuse 12.3 box and configuration as a raid 1 volume with intel rapid storage controller (Option ROM 10.1.0.1008) the raid is detected after boot and initialized. When I try to build a partition with yast the partitioner hangs during "initialization". Starting /sbin/mdmon md127 solved this problem and I was able to format and mount the raid. After reboot the raid is availabe, but - log in with a user who's homedir is on the raid hangs and - during shutdown the system hangs after a message something like "All DM devices detached" Again I dont't see any mdmon running. If I try /etc/init.d/boot.md stop and /etc/init.d/boot.md start @sbin/mdmon md127 --takeover --offroot is running and I can login and shutdown the machine smoothly. /etc/init.d/boot.md reload however doesn't start mdmon. I think mdmon should start during boot but I don't know how to achive this. Reproducible: Always Steps to Reproduce: 1. create raid 1 with intel faik raid 2. boot computer 3. try to create a partition with yast Actual Results: YAST partitioner hangs because mdmon doesn't start during boot or starts and silently exits Furthermore the raid is not "accessible" for users with their homedirs on thi raid until mdmon is started manually Expected Results: mdmon should start during boot and running Maybe this bug is related to bug 812422 but the solution their doesn't help in my case -- 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 15

[Bug 793954] New: raid1 array sometimes started with one of two disks at boot (again)
by bugzilla_noreply＠novell.com 24 Jun '13

24 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=793954 https://bugzilla.novell.com/show_bug.cgi?id=793954#c0 Summary: raid1 array sometimes started with one of two disks at boot (again) Classification: openSUSE Product: openSUSE Factory Version: 12.3 Milestone 1 Platform: Other OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: nfbrown(a)suse.com ReportedBy: suse-beta(a)cboltz.de QAContact: qa-bugs(a)suse.de Found By: Beta-Customer Blocker: --- Created an attachment (id=516596) --> (http://bugzilla.novell.com/attachment.cgi?id=516596) boot.log (factory from 2012-12-03, mdadm-3.2.6-2.1) It seems the random "start raid array with only one of two disks" problem is back in Factory :-( Details: I have two harddisks in my laptop. Each of them has several partitions, which are paired as RAID 1 (mirroring) arrays. In the last days, my /boot partition (md0) was started with one of two disks (IIRC this happened twice). Today my /testroot partition (md3) started with only one active disk. dmesg does not show any sign of broken disks. At least for /boot, re-adding the second disk with mdadm worked without any complaints (and in the next boots, it came up with both disks), and I expect the same for /testroot. I'll attach boot.log and dmesg output with md3 starting with only one disk. (Sorry, no /v/l/messages because my syslog setup is broken :-( ) -- 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 64

[Bug 761294] New: Fglrx driver for ATI/AMD will not work correctly, claims to be unsupported hardware despite contrary documentation
by bugzilla_noreply＠novell.com 24 Jun '13

24 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=761294 https://bugzilla.novell.com/show_bug.cgi?id=761294#c0 Summary: Fglrx driver for ATI/AMD will not work correctly, claims to be unsupported hardware despite contrary documentation Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: openSUSE 12.1 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: roger.luedecke(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20100101 Firefox/12.0 Though the OSS Radeon driver works surprisingly well, I could really use the extra oomph of fglrx. For that matter, it'd be nice if my laptop didn't feel compelled to double as a hair-dryer. I have installed both from the ATI repo as well as from the source available on AMD website. Both installs claim there is no supported chipset found. However, all available documentation indicates that my chipset is in fact supported. While that driver is installed, the graphics seem to default to a more primitive driver than the Radeon driver as the performance is terrible. Uninstalling fglrx fixes the issue. Reproducible: Always Expected Results: Amazing graphical performance for Second Life. 01:05.0 VGA compatible controller: ATI Technologies Inc RS690M [Radeon X1200 Series] -- 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 10

[Bug 732980] New: Loading module mISDN_dsp makes ksoftirqd use high % of CPU time
by bugzilla_noreply＠novell.com 24 Jun '13

24 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=732980 https://bugzilla.novell.com/show_bug.cgi?id=732980#c0 Summary: Loading module mISDN_dsp makes ksoftirqd use high % of CPU time Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: claude.diderich(a)yahoo.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20100101 Firefox/8.0 When loading the ISDN modules mISDN_core and then mISDN_dsp into the kernel using modprobe, the soft irq handler ksoftirqd usses high % of CPU time on one core of the processor(s) installed in the system. PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 10 root 20 0 0 0 0 S 47 0.0 1:53.77 ksoftirqd/1 Unloading the module mISDN_dsp from the kernel, makes the usage diappear again. Issue has been reproduced on two different machines under openSUSE 12.1 with different hardware (one with ISDN adapter and one without). Kernel is Linux joshua 3.1.0-1.2-default #1 SMP Thu Nov 3 14:45:45 UTC 2011 (187dde0) x86_64 x86_64 x86_64 GNU/Linux dmesg shows Modular ISDN core version 1.1.21 NET: Registered protocol family 34 DSP modul 2.0 mISDN_dsp: DSP clocks every 64 samples. This equals 2 jiffies. Reproducible: Always Steps to Reproduce: 1. modprobe mISDN_core 2. modprobe mISDN_dsp 3. Watch CPU usage, for example through top Actual Results: Machine spends lot of time in ksoftirqd PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 10 root 20 0 0 0 0 S 47 0.0 1:53.77 ksoftirqd/1 Expected Results: Machine spends no time in ksoftirqd (result shown after unloading mISDN_dsp and mISDN_core) PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 10 root 20 0 0 0 0 S 0 0.0 3:03.77 ksoftirqd/1 ISDN functionality is not affected (at least none could be identified). -- 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 826380] New: [openSUSE goes SLE12]: xfig: Change and/or patches may lost
by bugzilla_noreply＠novell.com 24 Jun '13

24 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=826380 https://bugzilla.novell.com/show_bug.cgi?id=826380#c0 Summary: [openSUSE goes SLE12]: xfig: Change and/or patches may lost Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 1 Platform: All OS/Version: SLES 11 Status: NEW Keywords: automation, regression_test_needed Severity: Normal Priority: P5 - None Component: Other AssignedTo: werner(a)suse.com ReportedBy: patch-lost-in-sle(a)suse.de QAContact: qa-bugs(a)suse.de CC: patch-lost-in-sle(a)suse.de Found By: --- Blocker: --- This is a simple test -- 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 826369] New: [openSUSE goes SLE12]: xfig: Change and/or patches may lost
by bugzilla_noreply＠novell.com 24 Jun '13

24 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=826369 https://bugzilla.novell.com/show_bug.cgi?id=826369#c0 Summary: [openSUSE goes SLE12]: xfig: Change and/or patches may lost Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 1 Platform: All OS/Version: SLES 11 Status: NEW Keywords: automation, regression_test_needed Severity: Normal Priority: P5 - None Component: Other AssignedTo: werner(a)suse.com ReportedBy: patch-lost-in-sle(a)suse.de QAContact: qa-bugs(a)suse.de CC: patch-lost-in-sle(a)suse.de Found By: --- Blocker: --- This is a simple test -- 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 826367] New: [openSUSE goes SLE12]: xfig: Change and/or patches may lost
by bugzilla_noreply＠novell.com 24 Jun '13

24 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=826367 https://bugzilla.novell.com/show_bug.cgi?id=826367#c0 Summary: [openSUSE goes SLE12]: xfig: Change and/or patches may lost Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 1 Platform: All OS/Version: SLES 11 Status: NEW Keywords: automation, regression_test_needed Severity: Normal Priority: P5 - None Component: Other AssignedTo: werner(a)suse.com ReportedBy: patch-lost-in-sle(a)suse.de QAContact: qa-bugs(a)suse.de CC: patch-lost-in-sle(a)suse.de Found By: --- Blocker: --- This is a simple test -- 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 823625] New: Xvnc missing GLX support
by bugzilla_noreply＠novell.com 24 Jun '13

24 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=823625 https://bugzilla.novell.com/show_bug.cgi?id=823625#c0 Summary: Xvnc missing GLX support Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: All OS/Version: All Status: NEW Severity: Minor Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: hpj(a)suse.com QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: Development Blocker: --- It looks like Xvnc on openSUSE 12.3 is missing GLX support. This is needed in order to run a proper (non-fallback) GNOME session remotely. With GNOME 3.8, the fallback session has been dropped, making GLX a requirement. It looks like the Fedora project has deployed a small TigerVNC patch to deal with this shortcoming. I've applied their patch with minor changes to our xorg-x11-Xvnc package and confirmed that it fixes the problem. I don't know if the patch is still needed in Factory. We should check, and apply it there if so. See also bug 823410 for a workaround using Xvfb (which has its own problems). -- 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 824025] New: dosfslabel from dosfstools crashes with buffer overflow
by bugzilla_noreply＠novell.com 24 Jun '13

24 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=824025 https://bugzilla.novell.com/show_bug.cgi?id=824025#c0 Summary: dosfslabel from dosfstools crashes with buffer overflow Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: danielstefanmader(a)googlemail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:21.0) Gecko/20100101 Firefox/21.0 Since 2010, the packaged version of dosfstools cannot be used to change the volume label of a VFAT filesystem (without reformatting) because the tool crashes with a buffer overflow. See also here: https://bugs.archlinux.org/task/34193 Please update to the latest version of dosfstools: http://daniel-baumann.ch/software/dosfstools/ Reproducible: Always Steps to Reproduce: 1. dosfslabel /dev/sdb1 ANAME -- 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 11

[Bug 818842] New: Logwatch doesn't report details from /var/log/messages
by bugzilla_noreply＠novell.com 24 Jun '13

24 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=818842 https://bugzilla.novell.com/show_bug.cgi?id=818842#c0 Summary: Logwatch doesn't report details from /var/log/messages Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: gsexton(a)mhsoftware.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/536.29.13 (KHTML, like Gecko) Version/6.0.4 Safari/536.29.13 Logwatch is looking for the lines in /var/log/messages to be in the old format "%b %d ...", not in the new format for RFC-3339 Essentially, all date is filtered out because the date range filter is broken. I looked at logwatch.pl and tried some changes but I can't get it to come out right. Reproducible: Always Steps to Reproduce: 1.Install Logwatch 2.Run It 3.Examine The output Actual Results: Kernel and other messages are not displayed Expected Results: Kernel messages should be displayed. This should be fixed ASAP since the manual explicitly references using logwatch and provides instructions on using 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 6