October 2012 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 769770] seccheck: invalid detection of multiple occurrence of UID 0
by bugzilla_noreply＠novell.com 19 Oct '12

19 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=769770 https://bugzilla.novell.com/show_bug.cgi?id=769770#c8 --- Comment #8 from Bernhard Wiedemann <bwiedemann(a)suse.com> 2012-10-19 08:00:58 CEST --- This is an autogenerated message for OBS integration: This bug (769770) was mentioned in https://build.opensuse.org/request/show/138780 Evergreen:11.2 / seccheck -- 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

[Bug 652346] New: screensaver and login crash when given wrong password giving entry in SLED sp3
by bugzilla_noreply＠novell.com 18 Oct '12

18 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=652346 https://bugzilla.novell.com/show_bug.cgi?id=652346#c0 Summary: screensaver and login crash when given wrong password giving entry in SLED sp3 Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: Other OS/Version: SLED 10 Status: NEW Severity: Critical Priority: P5 - None Component: KDE3 AssignedTo: kde-maintainers(a)suse.de ReportedBy: brandon(a)krever.ca QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729) screensaver and login crash when given wrong password giving entry to computer in SLED sp3 Reproducible: Always Steps to Reproduce: 1.lock the computer and type something random or type something random at login 2.login/lock will fail giving access to computer 3. Actual Results: screensaver and login crashed when given wrong password giving entry in SLED sp3 Expected Results: it should of said incorrect password. -- 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 785664] New: libxcb bug causes deadlock and freezing applications in wine
by bugzilla_noreply＠novell.com 18 Oct '12

18 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=785664 https://bugzilla.novell.com/show_bug.cgi?id=785664#c0 Summary: libxcb bug causes deadlock and freezing applications in wine Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: All OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: novell(a)mirell.de QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.13 (KHTML, like Gecko) Chrome/24.0.1290.0 Safari/537.13 SUSE/24.0.1290.0 After starting various Windows applications using wine the application will randomly freeze and become unusable due to a deadlock occouring. I am using openSUSE 12.2 Final with wine 1.5.15, libxcb 1.8.1 and NVIDIA 310.14 drivers. Many applications started using wine are affected since this is a generic libxcb bug. Reproducible: Always Steps to Reproduce: 1. Start a GUI windows application using wine 2. Use it for some time 3. Notice it freezes Actual Results: When the deadlock occours, the wine output is: err:ntdll:RtlpWaitForCriticalSection section 0x15d60c "bitblt.c: surface" wait timed out in thread 0009, blocked by 0024, retrying (60 sec) The application window is "frozen". Expected Results: Program does not freeze and continues to work. The bug is also reported upstream at wine: http://bugs.winehq.org/show_bug.cgi?id=31882#c13 It appears to be a libxcb deadlock bug which was known upstream and is fixed in libxcb 1.9. I have already backported the fix/patch on OBS here: https://build.opensuse.org/package/show?package=libxcb&project=home%3AFunky… With this fix for libxcb, wine applications no longer freeze and work fine. However, I have no idea how this would be pushed to the offical update repository as I am unable to submit back my package changes. -- 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 739056] New: mate-conf - polkit and friends, needs review...
by bugzilla_noreply＠novell.com 18 Oct '12

18 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=739056 https://bugzilla.novell.com/show_bug.cgi?id=739056#c0 Summary: mate-conf - polkit and friends, needs review... Classification: openSUSE Product: openSUSE 12.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: nmo.marques(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.2 (KHTML, like Gecko) Chrome/15.0.874.120 Safari/535.2 mateconf is a fork of GNOME2's gconf package and is a part of the GNOME2 fork, MATE Desktop. Following a conversation on #opensuse-gnome, I've given some work to it packaging it and since mate-conf installs some polkit rules it triggers the RPMlint error to contact the SUSE Security Team. I've used 'setBadness' to allow it to build since I need to build other stuff based on it. Though it's not yet a requirement for this package to be reviewed ASAP, I've decided to open already the bug report for it. The plan is as follows: #1 - Build all the stuff (more than half of the packages are building already); #2 - Do deveral runtime tests and check if it can be included in the distro (it can in theory); #3 - Move it to a repository in GNOME name space (probably into GNOME:Ayatana, since MATE can enable most of indicators and friends); #4 - Inclusion on openSUSE (without indicators from Ayatana); I'm not sure of the Security Team process to review this, but I would consider doing this in an earlier stage so everything can be tested properly. The testing packages are on: home:ketheriel:m8/mate-conf. 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 2

[Bug 780132] New: NFS share are not automounting with NIS
by bugzilla_noreply＠novell.com 18 Oct '12

18 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=780132 https://bugzilla.novell.com/show_bug.cgi?id=780132#c0 Summary: NFS share are not automounting with NIS Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: michael(a)karbach.org 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.1180.89 Safari/537.1 Actually I have this problem also with OS-12.1. With a freshly installed OS-12 and a running NIS/NFS my NFS shared filesystem are not automatically mounted. I have marked automount in YaST-NIS module and selected the remote directory, but on boot it will not mount. But a simple mount /home after booting mounts the remote home-directory, without problems. I have this issue on several OS-12-systems. 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 17

[Bug 785307] New: libyui ncurses: nested CheckBoxFrames are falsely activated
by bugzilla_noreply＠novell.com 18 Oct '12

18 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=785307 https://bugzilla.novell.com/show_bug.cgi?id=785307#c0 Summary: libyui ncurses: nested CheckBoxFrames are falsely activated Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 AssignedTo: gs(a)suse.com ReportedBy: jdsn(a)suse.com QAContact: jsrain(a)suse.com CC: tgoettlicher(a)suse.com Found By: Development Blocker: --- Assume we have a ycp dialog with nested CheckBoxFrames (like in the small reproducer below), which are all disabled at the start. When the outer CheckBoxFrame (A) is enabled all inner elements become active. But also the elements inside the inner CheckBoxFrame (B) become active, which is not wanted. Jumping with TAB to the CheckBoxFrame (B) (not clicking on it), disables its inner elements again. Jumping back with TAB reenables its inner elements. This behaviour in ncurses mode is unintuitive, misleading and not consistent with the qt and qtk UIs. With both other UIs the elements of a nested CheckBoxFrame remain disabled. { term nestedCheckboxFrame = `VBox( `CheckBoxFrame( `id(`foo), "Selection A", false, `VBox( `CheckBox("Enable Foo"), `HBox( `HSpacing(2), `Left (`CheckBoxFrame( `id(`bar), "Selection B", false, `VBox(`CheckBox("Enable Bar"), `SelectionBox(`id(`sel), "Select", ["Foo", "Bar", "Baz"]) ) )) ) ) ), `PushButton(`id(`ok), "OK") ); UI::OpenDialog(nestedCheckboxFrame); UI::UserInput(); UI::CloseDialog(); } -- 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 768332] New: quilt doesn't support source package with zip file
by bugzilla_noreply＠novell.com 18 Oct '12

18 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=768332 https://bugzilla.novell.com/show_bug.cgi?id=768332#c0 Summary: quilt doesn't support source package with zip file Classification: openSUSE Product: openSUSE 12.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Other AssignedTo: jdelvare(a)suse.com ReportedBy: fcrozat(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- some rpm source package are using zip file for sources, which is not supported by quilt. example of such package: argyllcms (from multimedia:color_management in obs) -- 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 756201] New: boot fails due to MD devices not starting correctly
by bugzilla_noreply＠novell.com 18 Oct '12

18 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=756201 https://bugzilla.novell.com/show_bug.cgi?id=756201#c0 Summary: boot fails due to MD devices not starting correctly 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: suse(a)randycushman.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20100101 Firefox/11.0 Boot fails due to inaccessible partitions / MD devices not started. Problem started after update from 11.4 to 12.2 using zypper dup. I suspect the new initrd is autodetecting raidsets, finding signatures for raidsets that no longer exist. This seems to vary from one boot attempt to the next. In the most straightforward example, the boot started a nonexistent md8, using a partition that is now part of md5. md5 was left inactive, preventing a successful boot. from initrd: # cat etc/mdadm.conf AUTO -all ARRAY /dev/md0 metadata=0.90 UUID=5aa3525a:7ad6a35f:bc99ad79:a125caa7 ARRAY /dev/md1 metadata=0.90 UUID=828df197:ed191435:9316bb71:60b936be ARRAY /dev/md2 metadata=0.90 UUID=b57f8ec2:a0f97879:098bac5e:769b2d5c ARRAY /dev/md3 metadata=0.90 UUID=c1738aec:4471396a:1620bc28:6a0c8b04 from filesystem: # cat etc/mdadm.conf ARRAY /dev/md0 level=raid1 UUID=5aa3525a:7ad6a35f:bc99ad79:a125caa7 ARRAY /dev/md1 level=raid1 UUID=828df197:ed191435:9316bb71:60b936be ARRAY /dev/md2 level=raid1 UUID=b57f8ec2:a0f97879:098bac5e:769b2d5c ARRAY /dev/md3 level=raid1 UUID=c1738aec:4471396a:1620bc28:6a0c8b04 ARRAY /dev/md4 level=raid1 UUID=efd63b6f:eda21963:ef9ebeac:305c1bed ARRAY /dev/md5 level=raid1 UUID=c0493179:3706fe69:ef9ebeac:305c1bed ARRAY /dev/md6 level=raid1 UUID=61cf3e35:6a4d87df:ef9ebeac:305c1bed ARRAY /dev/md7 level=raid1 UUID=9c4abb01:1a7af84d:ef9ebeac:305c1bed # mdadm -Ds ARRAY /dev/md0 metadata=0.90 UUID=5aa3525a:7ad6a35f:bc99ad79:a125caa7 ARRAY /dev/md1 metadata=0.90 UUID=828df197:ed191435:9316bb71:60b936be ARRAY /dev/md2 metadata=0.90 UUID=b57f8ec2:a0f97879:098bac5e:769b2d5c ARRAY /dev/md3 metadata=0.90 UUID=c1738aec:4471396a:1620bc28:6a0c8b04 ARRAY /dev/md4 metadata=0.90 UUID=efd63b6f:eda21963:ef9ebeac:305c1bed ARRAY /dev/md5 metadata=0.90 UUID=c0493179:3706fe69:ef9ebeac:305c1bed ARRAY /dev/md6 metadata=0.90 UUID=61cf3e35:6a4d87df:ef9ebeac:305c1bed ARRAY /dev/md7 metadata=0.90 UUID=9c4abb01:1a7af84d:ef9ebeac:305c1bed I tried removing "AUTO -all" from the initrd version of mdadm.conf--this made no difference. I tried booting using sysvinit--the boot did not find the lvm root partition. Reproducible: Always Steps to Reproduce: 1. power on PC 2. 3. Actual Results: (from memory) type root password to enter single-user mode Expected Results: normal boot - System is currently dual-boot between openSUSE 11.4 and openSUSE 12.1 using GRUB - Separate root partitions are ext3 on RAID1 - Swap partition is on lvm on RAID1 - All other partitions, including separate root and shared home partitions, are ext4 on lvm on RAID1 -- 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 765344] New: opensuse 12.1 fails to boot from RAID1 root partition
by bugzilla_noreply＠novell.com 18 Oct '12

18 Oct '12

https://bugzilla.novell.com/show_bug.cgi?id=765344 https://bugzilla.novell.com/show_bug.cgi?id=765344#c0 Summary: opensuse 12.1 fails to boot from RAID1 root partition Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: i586 OS/Version: openSUSE 12.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: batpul(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:12.0) Gecko/20100101 Firefox/12.0 I can't find a way to get a working opensuse 12.1 system with a root (or boot) partition on a RAID1 array using mdadm. I have created other md arrays for user and work partitions which are mounted after the kernel has booted with non-raid root and boot partitions. If root is on a md RAID1 partition then the kernel waits for md0 to appear. It first prints a long trail of dots and then asks whether to revert to the underlying partition, but this fails. I've also tried with opensuse 12.2 beta1 to let the installer create a RAID1 root partition, but this fails to boot as well. My conclusion is that opensuse is not currently tested to boot from RAID1 root or boot partitions. This is supported by RH and FC according to various reports and tutorials on the web. Reproducible: Always Steps to Reproduce: 1.install root on RAID1 2.reboot 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 4

[Bug 784171] 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=784171 https://bugzilla.novell.com/show_bug.cgi?id=784171#c0 Summary: openSUSE:12.2:Update/patchinfo.949: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other URL: http://forums.opensuse.org/english/get-technical-help- here/tumbleweed/479250-tumbleweed-mdadm-upgrade-now-wo nt-boot.html OS/Version: openSUSE 12.2 Status: NEW Severity: Critical Priority: P5 - None Component: 3rd party software AssignedTo: dmueller(a)suse.com ReportedBy: valentin(a)isim.ro QAContact: opensuse-communityscreening(a)forge.provo.novell.com CC: nfbrown(a)suse.com Found By: Community User Blocker: --- Seems that the latest mdadm update related to better suspend does make systems with RAID unbootable, see http://forums.opensuse.org/english/get-technical-help-here/tumbleweed/47925… My case: / on RAID10 (fake RAID from intel with IMSM), boot from / After applying the update, the system can not boot, the error messages are related to: mdadm: bad uuid: UUID=<UUID>\nARRAY mdadm: only give one device per ARRAY line /dev/md/imsm0 and /dev/md126 Than the booting hangs while trying to resume from the / partition (in my case md126p2). This is rather a drawback after fixing https://bugzilla.novell.com/show_bug.cgi?id=752107 and the one similar to it. The update: 3.2.5-3.13.1|x86_64||repo-12.2-update|624c659a413a3830b3fd5dad53cd71e5d077e27a979d78fac3799b06139a4067 -- 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