April 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 808994] New: Please add openSUSE:Tools to Community Repositories
by bugzilla_noreply＠novell.com 17 Apr '13

17 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=808994 https://bugzilla.novell.com/show_bug.cgi?id=808994#c0 Summary: Please add openSUSE:Tools to Community Repositories Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jw(a)suse.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- As we define developers to be in our target audience group, we should offer them our tools repo for package building and build service usage. openSUSE:Tools -- 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 808543] New: Default keyboard layout for dutch users now US International instead of US English
by bugzilla_noreply＠novell.com 17 Apr '13

17 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=808543 https://bugzilla.novell.com/show_bug.cgi?id=808543#c0 Summary: Default keyboard layout for dutch users now US International instead of US English Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: All OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: knurpht(a)glosscomputer.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.32 (KHTML, like Gecko) Chrome/27.0.1425.0 Safari/537.32 SUSE/27.0.1425.0 On openSUSE 12.3 GM the default keyboard layout after choosing Dutch as the language is US International. Wrong, we shouldn't have a windows feature, we should have the "linux" way, i.e. use a compose key to create composed characters. After selection compose key doesn't work anymore. Reproducible: Always Steps to Reproduce: 1.Install, select Dutch as the language, US International is auto-selected 2.Fix: Yast - System - System keyboard layout to US English 3.All back to normal Actual Results: No compose key, wrong keyboard layout for a linux user. Expected Results: US English as the default for dutch users. They can set the US International layout in their desktop if they want windows behaviour. I know some people have been putting pressure to change this, one in peticular. We've tried to stop this when discussing it on a dutch launch party. Many of us there agreed it should never be US International. Linux is not windows. -- 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 804238] New: Tumbleweed: Very slow boot with Systemd - normal boot time with sysvinit
by bugzilla_noreply＠novell.com 17 Apr '13

17 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=804238 https://bugzilla.novell.com/show_bug.cgi?id=804238#c0 Summary: Tumbleweed: Very slow boot with Systemd - normal boot time with sysvinit Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: Other OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: kai(a)stella.at QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=525054) --> (http://bugzilla.novell.com/attachment.cgi?id=525054) output from systemd-analyze plot User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 over the last 1-2 months my boot time got progressively slower up to a point where it took over 5 minutes for the kdm loginscreen to appear. systemd-analyze pointed out it was networkmanager.service takeing that long, so i tried it also with network scripts which did not change anything. finally i tried switching back to sysvinit and noticed that with sysvinit boot time is well below 1 minute. i'll attach my latest svg from the systemd-analyze plot (with network scripts active, but as mentioned before network-manager and network scripts did not make any difference) 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 4

[Bug 809114] New: rootflags=data=writeback stripped to rootflags=data: system does not boot like this
by bugzilla_noreply＠novell.com 17 Apr '13

17 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=809114 https://bugzilla.novell.com/show_bug.cgi?id=809114#c0 Summary: rootflags=data=writeback stripped to rootflags=data: system does not boot like this Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: All OS/Version: SUSE Other Status: NEW Severity: Minor Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: estellnb(a)elstel.org QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (OS/2; Warp 4.5; rv:10.0.10) Gecko/20100101 Firefox/10.0.10 In order to install on SSD it is recommendable to set rootflags=data=writeback which does however get stripped to rootflags=data by the installer. As a consequence oS 12.3 does not boot after installation unless you change that back on the grub command line to data=writeback. 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 3

[Bug 808564] New: Installation ruins the MBR if another Grub is installed on it
by bugzilla_noreply＠novell.com 17 Apr '13

17 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=808564 https://bugzilla.novell.com/show_bug.cgi?id=808564#c0 Summary: Installation ruins the MBR if another Grub is installed on it Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mustafaa.alhamdaani(a)gmail.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0 Installation use "Write generic Boot Code to MBR" that ruins other grub instances installed on MBR (I use multiboot and install one grub on MBR and other instances on partitions), There is no need for this option (enlighten me if I am wrong). And is "Set Active Flag in Partition Table for Boot Partition" necessary? 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 3

[Bug 809961] New: yast2-iscsi-server writes its config to /etc/ietd.conf, but /usr/sbin/ietd expects config at /etc/iet/ietd.conf
by bugzilla_noreply＠novell.com 17 Apr '13

17 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=809961 https://bugzilla.novell.com/show_bug.cgi?id=809961#c0 Summary: yast2-iscsi-server writes its config to /etc/ietd.conf, but /usr/sbin/ietd expects config at /etc/iet/ietd.conf Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: i586 OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: belphegor(a)belbel.or.jp QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0 yast2-iscsi-server reads/generates ietd.conf under /etc, but ietd reads its config from /etc/iet/ietd.conf. Reproducible: Always Steps to Reproduce: 1. install packages: yast2-iscsi-server, iscsitarget. 2. add one or more targets with yast -> Network Services -> iSCSI target. 3. prepare iSCSI initiator (in my test, Windows 8). Actual Results: none of targets can be accessed. Expected Results: added targets should be able to be accessed by initiator. openSUSE < 12.2 is not affected. In 12.2, updated version (1.4.20.3-2.8.1) is only affected. In 12.3, default version (1.4.20.3-8.1.2) is affected. -- 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 812368] New: USB device 08E4:0163 DJM-850 recognized by yast, not audacity
by bugzilla_noreply＠novell.com 17 Apr '13

17 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=812368 https://bugzilla.novell.com/show_bug.cgi?id=812368#c0 Summary: USB device 08E4:0163 DJM-850 recognized by yast, not audacity Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: i686 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: roeland(a)linux-it.nl QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0 I have a poineer DJM-850 mixer, that reports itself as device 08E4:0163 with lsusb. ast2 soudn reports the device as a DJM-850; after configuring the device, it's not possible to use it as a device to record from with audacity. It's not 100% clear if the device is supported or not -- yast2 sound recognizes and initilizes the device, so that would give the feeling it would. But then. not seeen in the dropdown menu of audacity. Reproducible: Always Steps to Reproduce: 1. 2. 3. not sure if it's a bug or an enhancement request.. -- 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 815169] New: Online Update during installation stops the installation process. 'openSUSE-2013-253 yast2-install: fix network in 2nd stage' reboot needed
by bugzilla_noreply＠novell.com 17 Apr '13

17 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=815169 https://bugzilla.novell.com/show_bug.cgi?id=815169#c0 Summary: Online Update during installation stops the installation process. 'openSUSE-2013-253 yast2-install: fix network in 2nd stage' reboot needed Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 0 Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bnacht(a)web.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 Installation for openSUSE 12.3 (x86_64): I choose the item 'online update' during the installation process. There was a patch named 'openSUSE-2013-253 yast2-install: fix network in 2nd stage' this kill the installation process. The only way to procced is to switch of the PC hard and restart. If I choose the online update again, same error occurs. I can only success with the installation if i skip the online update. After the installation i can run the Update without error Reproducible: Always Steps to Reproduce: 1. Make a new install of openSUSE12.3 (x86_64) (Deselect automatic configuration) 2. Use default settings. Only configure a separate User and Root account. Software selection default. 3. Coose 'run online update' during the installation process. Actual Results: Installation stops Expected Results: Successful installation I see the behaviour a least on two different PC's of mine -- 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 813187] New: Online update of yast2-installation during 2nd stage install results in yast2 crash
by bugzilla_noreply＠novell.com 17 Apr '13

17 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=813187 https://bugzilla.novell.com/show_bug.cgi?id=813187#c0 Summary: Online update of yast2-installation during 2nd stage install results in yast2 crash Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: llunak(a)suse.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- During 2nd stage installation, running online update performs a (temporary?) removal of package yast2-installation, resulting in yast2 crash (signal 15 at /usr/share/YaST2/clients/online_update_install.ycp:91 , if I remember correctly). The installation was network install of 12.3, KDE desktop, console tools and KDE development patterns added. -- 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 813094] New: YaST does not finish samba boot configuration correctly
by bugzilla_noreply＠novell.com 17 Apr '13

17 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=813094 https://bugzilla.novell.com/show_bug.cgi?id=813094#c0 Summary: YaST does not finish samba boot configuration correctly Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: VMWare OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Wojciech.Szenajch(a)bull.com.pl QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:19.0) Gecko/20100101 Firefox/19.0 OpenSuSE 12.3 x86_64. YaST does not finish samba boot configuration correctly. During boot samba is not started automatically. The following commands must be executed maually after to correct this bug: systemctl enable nmb.service systemctl enable smb.service ifup was used during definition of samba settings. Later change to NetworkManager did not help. Reproducible: Always Steps to Reproduce: 1.define default samba configuration usung YaST 2.test it (nmb and smb are started at this moment) 3.reboot (nmb, smb are not started) Actual Results: Samba is not working after reboot. Expected Results: Samba nmb, smb daemons should be started during boot. -- 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