March 2010 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 586585] New: Pause and strange output when entering administrator console
by bugzilla_noreply＠novell.com 10 Mar '10

10 Mar '10

http://bugzilla.novell.com/show_bug.cgi?id=586585 http://bugzilla.novell.com/show_bug.cgi?id=586585#c0 Summary: Pause and strange output when entering administrator console Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: neptunia(a)mail.ru QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; ru; rv:1.9.1.8) Gecko/20100204 SUSE/3.5.8-0.1.1 Firefox/3.5.8 When entering su - and then password there is a strange pause and output: anixx@anixx-desktop:~> su - Пароль: -bash: export: `found.': not a valid identifier -bash: export: `found.': not a valid identifier -bash: export: `found.': not a valid identifier -bash: alias: Command: not found -bash: alias: not: not found -bash: alias: found.: not found -bash: export: `found.': not a valid identifier -bash: export: `found.': not a valid identifier -bash: export: `found.': not a valid identifier -bash: alias: Command: not found -bash: alias: not: not found -bash: alias: found.: not found Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 2

[Bug 467437] openssl in openSuSE 11.1 does create wrong PKCS12 files
by bugzilla_noreply＠novell.com 10 Mar '10

10 Mar '10

http://bugzilla.novell.com/show_bug.cgi?id=467437 http://bugzilla.novell.com/show_bug.cgi?id=467437#c30 --- Comment #30 from Guanjun He <gjhe(a)novell.com> 2010-03-10 03:26:14 UTC --- submitted to sle11 and sle11sp1. -- 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 0

[Bug 564093] New: xend doesn't create bridge during boot after update 11.1 to 11.2
by bugzilla_noreply＠novell.com 09 Mar '10

09 Mar '10

http://bugzilla.novell.com/show_bug.cgi?id=564093 http://bugzilla.novell.com/show_bug.cgi?id=564093#c0 Summary: xend doesn't create bridge during boot after update 11.1 to 11.2 Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Xen AssignedTo: jdouglas(a)novell.com ReportedBy: yury.buldakov(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/532.6 (KHTML, like Gecko) Chrome/4.0.267.0 Safari/532.6 After some investigation: On openSUSE 11.1 /dev/shm/sysconfig was created by /etc/sysconfig/network/scripts/functions.common: > > # RUN_FILES_BASE contains the path to the configuration data cache. > > # It __must__ __not__ contain a trailing slash. > > RUN_FILES_BASE=/dev/shm/sysconfig > > test -d $RUN_FILES_BASE || mkdir -p $RUN_FILES_BASE xen bridge creation stores information then (/etc/xen/scripts/network-bridge): > > # Record creation of bridge in /dev/shm/sysconfig/xenbridges so other > > # tools, e.g. yast2 lan, know that Xen bridging is active. > > [ -d /dev/shm/sysconfig/xenbridges ] || mkdir /dev/shm/sysconfig/xenbridges > > touch /dev/shm/sysconfig/xenbridges/${bridge} But in openSUSE 11.2 RUN_FILES_BASE was changed: > > # RUN_FILES_BASE contains the path to the configuration data cache. > > # It __must__ __not__ contain a trailing slash. > > RUN_FILES_BASE=/dev/.sysconfig/network > > test -d $RUN_FILES_BASE || mkdir -p $RUN_FILES_BASE I was unable to find anything that takes care of creation '/dev/shm/sysconfig' directory used in '/etc/xen/scripts/network-bridge' Reproducible: Always Steps to Reproduce: I didn't performed anything special - reproduced every boot -- 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 5

[Bug 574325] New: network freeze at domU reboot/shutdown
by bugzilla_noreply＠novell.com 09 Mar '10

09 Mar '10

http://bugzilla.novell.com/show_bug.cgi?id=574325 http://bugzilla.novell.com/show_bug.cgi?id=574325#c0 Summary: network freeze at domU reboot/shutdown Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Major Priority: P5 - None Component: Xen AssignedTo: jdouglas(a)novell.com ReportedBy: diablo(a)iasi.roedu.net QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=339127) --> (http://bugzilla.novell.com/attachment.cgi?id=339127) domU xen config User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.8pre) Gecko/20100123 Ubuntu/9.10 (karmic) Firefox/3.5.7 I installed OpenSuSE 11.2 in dom0 and one virtual machine (OpenSuSE 11.2) as domU using the configuration attached. When I shutdown (or reboot) the virtual machine, dom0 networking just stops working for around 30 seconds. After that, the dom0 starts to work again, as expected. One very peculiar thing is that that packets are received by dom0 (tested on a blade system, connected remote on management console and using tcpdump) but nothing "leaves" the server. The network stops working in the exact moment that the virtual server stops. Reproducible: Sometimes Steps to Reproduce: 1.install & boot with xen enabled kernel in dom0 2.install OpenSuSE 11.2 in domU 3.on domU, shutdown -r now Actual Results: The network on dom0 stops sending packets on the network Expected Results: send packets on the network. -- 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 4

[Bug 585684] New: YaST is by installation not capable of creating partitioned MD devices
by bugzilla_noreply＠novell.com 09 Mar '10

09 Mar '10

http://bugzilla.novell.com/show_bug.cgi?id=585684 http://bugzilla.novell.com/show_bug.cgi?id=585684#c0 Summary: YaST is by installation not capable of creating partitioned MD devices Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: DOlsson(a)WEB.de QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.17) Gecko/2009122200 SUSE/3.0.17-0.1.1 Firefox/3.0.17 When trying to install openSUSE 11.2 on two new SATA disks (/dev/sda & /dev/sdb), I want to configure a partitioned MD RAID1 device using /dev/sd[ab], but YaST2 refuses to allow me to do this. When trying to using the Create Customer Partition, it is not possible to create an MD disk with /dev/sd[ab] as members of the MD device. After having created a partition on both disks of type 0xFD, it is possible to create a RAID1 MD device, but it is not possible to partition this MD device. Trying a work around, where I create the partitioned MD device by hand with mdadm --create /dev/md/raid1 --name="raid1" --homehost="Loke" --level="raid1" --auto="part3" --metadata="1.0" -v -n 2 /dev/sda /dev/sdb followed by the creation of 3 partitions on "/dev/md/raid1" (/dev/md/raid1p[123]), the MD device is created as I want it. After having booted the installation kernel, I verified that the new MD device is being correctly detected incl. the partitions (which it is), but YaST still refuses to accept that an MD device can be partitioned, thus making it impossible to access the three partitions that I have just created. Reproducible: Always Steps to Reproduce: 1. Boot the openSUSE 11.2 installation DVD 2. Select the Customer Partition Creation menu 3. Under the RAID menu it is not possible to make use of full disks (/dev/sdx) to create an RAID MD device, let alone a partitionable MD device. 3a. Creating a 0xFD partition of both disks, allows for the creation of an MD RAID device, but this device cannot be partitioned either. Actual Results: When trying to create a RAID MD device using full disks (/dev/sdx), the menu refuses with an error messages claiming that there is not any free devices able for the creation of the RAID MD device. Expected Results: When trying to create a RAID MD device using full disks (/dev/sdx), YaST to allow for the selection of disks that does have any partitions created on them to be part of an MD RAID device, just as it should be possible to create partitions on the resulting MD device. -- 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 5

[Bug 377568] Identify repository duplicates
by bugzilla_noreply＠novell.com 09 Mar '10

09 Mar '10

http://bugzilla.novell.com/show_bug.cgi?id=377568 http://bugzilla.novell.com/show_bug.cgi?id=377568#c6 --- Comment #6 from Cristian Rodríguez <crrodriguez(a)novell.com> 2010-03-09 17:37:52 UTC --- sounds fine to me, if duplicate repository is added and baseurl is different it IMHO needs to be added as a mirror except when the server reports itself as mirrorbrain or a redirector. -- 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 0

[Bug 585853] New: socketpair() does not generate socket pair usable as replacement as pipe
by bugzilla_noreply＠novell.com 09 Mar '10

09 Mar '10

http://bugzilla.novell.com/show_bug.cgi?id=585853 http://bugzilla.novell.com/show_bug.cgi?id=585853#c0 Summary: socketpair() does not generate socket pair usable as replacement as pipe Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: All OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: Development AssignedTo: pbaudis(a)novell.com ReportedBy: werner(a)novell.com QAContact: qa(a)suse.de CC: coolo(a)novell.com, ro(a)novell.com Found By: Development Blocker: --- Initial remark: the ksh uses socket pairs as replacement for pipes, also the program man. Now I found that such socket pairs do not generate a SIGPIPE where it should, e.g. from test suite of the ksh: test basic.sh begins at 2010-03-05+16:44:23 basic.sh[436]: early termination not causing broken pipe basic.sh[477]: pipefail causing /bin/true to wait for other end of pipe test basic.sh failed at 2010-03-05+16:44:51 with exit code 2 [ 95 tests 2 errors ] test signal.sh begins at 2010-03-05+16:45:50 signal.sh[55]: pipe with --pipefail PIPE trap hangs signal.sh[296]: kill -PIPE $$ failed, required termination by signal 'KILL' test signal.sh failed at 2010-03-05+16:47:06 with exit code 2 [ 26 tests 2 errors ] .. this works in SLES9, SLES10-SP3, SLES11-SP1, and SLES11, in openSUSE 11.1 and also in openSUSE 11.2. I've tried out the old gcc-4.3 compiler but this does not help therefore I guess that the glibc does generate a socket pair which does *not* rise a SIGPIPE nor a EPIPE if someone writes on a broken socket pair. As this happens within a chroot build environment it seems not to be a kernel runtime problem. -- 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 6

[Bug 377568] Identify repository duplicates
by bugzilla_noreply＠novell.com 09 Mar '10

09 Mar '10

http://bugzilla.novell.com/show_bug.cgi?id=377568 http://bugzilla.novell.com/show_bug.cgi?id=377568#c5 Adrian Schröter <adrian(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adrian(a)novell.com --- Comment #5 from Adrian Schröter <adrian(a)novell.com> 2010-03-09 15:59:21 UTC --- okay, I suggest the following REPOTAGS content: For standard repos created by publisher: obsrepository://$OBS_INSTANCE/$PROJECT/$repository For products build via kiwi: obsproduct:://$OBS_INSTANCE/$PROJECT/$productname Is that okay ? -- 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 0

[Bug 579119] New: yast2 keyboard does not update /etc/hal/fdi/policy/20thirdparty/11-keymap.fdi
by bugzilla_noreply＠novell.com 09 Mar '10

09 Mar '10

http://bugzilla.novell.com/show_bug.cgi?id=579119 http://bugzilla.novell.com/show_bug.cgi?id=579119#c0 Summary: yast2 keyboard does not update /etc/hal/fdi/policy/20thirdparty/11-keymap.fdi Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: i586 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: phdm(a)macqel.be QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.2) Gecko/20090730 SUSE/3.5.2-2.1 Firefox/3.5.2 I use 'yast(2) keyboard' to select my keyboard layout. After that, /etc/sysconfig/keyboard contains my newly selected keyboard layout, but /etc/hal/fdi/policy/20thirdparty/11-keymap.fdi still contains an old (and wrong, of course) keyboard layout. When I then (re)start 'X' to get a pure X server, the keyboard is wrong. Reproducible: Always Steps to Reproduce: 1.type init 3, to stop the xdm system 2.select another keyboard layout using 'yast keyboard' 3.check if /etc/hal/fdi/policy/20thirdparty/11-keymap.fdi is updated. It is not. Also, if I remove /etc/hal/fdi/policy/20thirdparty/11-keymap.fdi before calling 'yast keyboard', /etc/hal/fdi/policy/20thirdparty/11-keymap.fdi is not created. -- 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 17

[Bug 586639] New: lxdm-conf does not use common scripts found at /etc/X11/xdm
by bugzilla_noreply＠novell.com 09 Mar '10

09 Mar '10

http://bugzilla.novell.com/show_bug.cgi?id=586639 http://bugzilla.novell.com/show_bug.cgi?id=586639#c0 Summary: lxdm-conf does not use common scripts found at /etc/X11/xdm Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: All OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: andrea(a)opensuse.org ReportedBy: werner(a)novell.com QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- As the subject says ... IMHO the lxdm should use or map setup for XDM and other DM's found at /etc/X11/xdm -- 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 1