February 2010 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 539774] New: bootloader module wants to write to floppy disk although there is none
by bugzilla_noreply＠novell.com 09 Feb '10

09 Feb '10

http://bugzilla.novell.com/show_bug.cgi?id=539774 Summary: bootloader module wants to write to floppy disk although there is none Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: sven.burmeister(a)gmx.net QAContact: jsrain(a)novell.com Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.1.3) Gecko/20090909 SUSE/3.5.3-132.1 Firefox/3.5.3 I let the yast bootloader module create a new configuration and enable "boot from mbr". If I click on OK I am prompted to insert a floppy disk although this netbook does not have one. Reproducible: Always -- 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 526918] New: Change default passwd hash algorithm to sha512
by bugzilla_noreply＠novell.com 09 Feb '10

09 Feb '10

http://bugzilla.novell.com/show_bug.cgi?id=526918 Summary: Change default passwd hash algorithm to sha512 Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: bitdealer(a)gmail.com QAContact: qa(a)suse.de Found By: --- Please be so kind to change the default hashing algorithm that gets used by passwd and friends to something more secure than md5 in /etc/default/passwd (preferable sha512). And before you ask, Yes, I have my tin foil hat on ;D -- 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 544809] New: Custom Boot Partition cannot be deleted
by bugzilla_noreply＠novell.com 09 Feb '10

09 Feb '10

http://bugzilla.novell.com/show_bug.cgi?id=544809 Summary: Custom Boot Partition cannot be deleted Classification: openSUSE Product: openSUSE 11.2 Version: Milestone 7 Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: markus.walser(a)gmail.com QAContact: jsrain(a)novell.com Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.1.3) Gecko/20090909 SUSE/3.5.3-1.3 Firefox/3.5.3 During installation I added the entry "/dev/sdb" for "Custom Boot Partition". Afterwords I was unable to delete this entry within the same dialog. Whereas new entries were just appended. It was even possible to add an invalid empty entry by going backward in the installation process. Reproducible: Always Steps to Reproduce: 1.Start installation 2.Create Custom Partition 3.Add a "Custom Boot Partition" entry like "/dev/sdb" 4.Confirm and enter the "Custom Boot Partition" screen again. 5.Delete the existing Custom Boot Partition entry (/dev/sdb). 6.Confirm and check the result in the parent screen. Actual Results: The entry /dev/sdb still exists. Expected Results: The entry should have been removed. -- 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 20

[Bug 569576] New: [Virtualization/xen]
by bugzilla_noreply＠novell.com 09 Feb '10

09 Feb '10

http://bugzilla.novell.com/show_bug.cgi?id=569576 http://bugzilla.novell.com/show_bug.cgi?id=569576#c0 Summary: [Virtualization/xen] Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: carnold(a)novell.com ReportedBy: 0.bugs.only.0(a)gmail.com QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- Request to have OpenSUSE_11.2 repo @, https://build.opensuse.org/package/show?package=xen&project=Virtualization containing e.g., xen-kmp-debug-3.4.1_19718_04_2.6.31.5_0.1-28.1.x86_64.rpm xen-kmp-default-3.4.1_19718_04_2.6.31.5_0.1-28.1.x86_64.rpm xen-kmp-desktop-3.4.1_19718_04_2.6.31.5_0.1-28.1.x86_64.rpm refreshed against latest/released kernel, uname -a Linux server 2.6.31.8-0.1-xen #1 SMP 2009-12-15 23:55:40 +0100 x86_64 x86_64 x86_64 GNU/Linux Thanks. -- 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

[Bug 571846] New: you need to ACK the license again
by bugzilla_noreply＠novell.com 09 Feb '10

09 Feb '10

http://bugzilla.novell.com/show_bug.cgi?id=571846 http://bugzilla.novell.com/show_bug.cgi?id=571846#c0 Summary: you need to ACK the license again Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: locilka(a)novell.com ReportedBy: coolo(a)novell.com QAContact: jsrain(a)novell.com Found By: --- Blocker: --- With 11.3 Milestone 1, build 407 you need to ACK the license in the first screen. This shouldn't be. I didn't change the license tar lately, so I guess it's a regression in yast2-installation -- 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 3

[Bug 578163] New: gnome factory has older version of bug-buddy
by bugzilla_noreply＠novell.com 09 Feb '10

09 Feb '10

http://bugzilla.novell.com/show_bug.cgi?id=578163 http://bugzilla.novell.com/show_bug.cgi?id=578163#c0 Summary: gnome factory has older version of bug-buddy Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Major Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: ruchir.brahmbhatt(a)ecosmob.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/532.5 (KHTML, like Gecko) Chrome/4.0.249.43 Safari/532.5 Gnome factory repository still has bug-buddy 2.28 which makes capturing crashes and backtraces difficult as many times the application crashes in normal run and doesn't crash in gdb. I think having same version as other gnome applications might fix this issue. 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 4

[Bug 518790] New: /usr/bin/build overrides system-wide default setting for ulimit -v
by bugzilla_noreply＠novell.com 09 Feb '10

09 Feb '10

http://bugzilla.novell.com/show_bug.cgi?id=518790 Summary: /usr/bin/build overrides system-wide default setting for ulimit -v Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: All OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Development AssignedTo: pth(a)novell.com ReportedBy: stsp(a)elego.de QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.11) Gecko/2009061212 Iceweasel/3.0.6 (Debian-3.0.6-1) Filing this bug by request of Marcus Rueckert. While compiling Subversion packages with osc, I ran into problems compiling the Java bindings and running the Java binding tests. Java kept having problems allocating memory. After I tried setting the default ulimits to unlimited and adding more RAM to no avail, Peter Poeml pointed out that /usr/bin/build unconditionally sets ulimit -v to 3/4 of the system's total memory. The system I tried to compile with had about 700MB of memory (it's a VM), and this caused the problem (we might as well blame Java for being so memory hungry by default but it's easier to fix /usr/bin/build ;) Commenting out the call to the function setmemorylimit() in /usr/bin/build fixed the problem. On 2009-07-01 21:39:36 +0100, Stefan Sperling wrote: > On Wed, Jul 01, 2009 at 09:05:19PM +0200, Peter Poeml wrote: > > On Wed, Jul 01, 2009 at 07:25:29PM +0100, Stefan Sperling wrote: > > > The above ulimits are also configured for the shell from which > > > I run "osc build". > > > > > > But when I run "osc build", I always get the following error, > > > and the "ulimit -v" value is different (I've added ulimit -a to > > > see the limits used during "osc build"): > > [...] > > > How can I tell osc to use ulimit -v unlimited? > > > > > > I assume none of you are getting this error when building locally? > > > > I'm not sure, but looking at setmemorylimit() in /usr/bin/build, > > the function sets a limit by /proc/meminfo (3/4 of MemTotal; does that > > cause the problem? > > That was it! I commented out the call to that function and got > the packages built for the first time. Reproducible: Always Steps to Reproduce: 1. Install OpenSUSE 11.1 on system with little memory (say, 512MB) 2. osc branch devel:tools:scm:svn subversion 3. osc co ... (follow instructions) 4. osc build Actual Results: 1) testCreate(org.tigris.subversion.javahl.SVNAdminTests)java.lang.UnsatisfiedLinkError: /usr/src/packages/BUILD/subversion-1.6.3/subversion/bindings/javahl/native/.libs/libsvnjavahl-1.so.0.0.0: libneon.so.27: failed to map segment from shared object: Cannot allocate memory at java.lang.ClassLoader$NativeLibrary.load(Native Method) at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1767) at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1692) at java.lang.Runtime.loadLibrary0(Runtime.java:840) at java.lang.System.loadLibrary(System.java:1047) at org.tigris.subversion.javahl.NativeResources.loadNativeLibrary(NativeResources.java:79) Expected Results: ........................................ ........ Time: 142.554 OK (50 tests) -- 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 513004] New: yast2 bootloader doesn't represent the REAL boot conditions
by bugzilla_noreply＠novell.com 09 Feb '10

09 Feb '10

http://bugzilla.novell.com/show_bug.cgi?id=513004 Summary: yast2 bootloader doesn't represent the REAL boot conditions Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: suse(a)tlinx.org QAContact: jsrain(a)novell.com Found By: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.10) Gecko/2009042316 Firefox/3.0.10 (.NET CLR 3.5.30729) I tried to install the xen kernel. It failed due to insufficient room in boot (though it updated the boot config to boot from the new kernel, resulting in a failure each boot, that I had to manually intervene in and boot from an existing kernel until I fixed the problem). The partition was too small for the number and sizes of the new kernels. I repurposed another partition on the same disk. I mount my disks by label. I formatted the new partition as 'Boot'. After copyping the contents of my existing /boot to the new filesystem, I unmounted and relabeled the old partition 'Oboot'. I remounted /boot, and it mounted the new partition by label Boot as expected. I then went into yast2 and told it to finish installing the xen kernel, which it did. When I tried to boot, the system still couldn't find the xen kernel. I edited the /boot/grub/menu and noticed references to the my disk partitions not using LABELS!! :-( (separate issue/bug). I created alternate/duplicate entries for each boot entry so I'd have the originals- but added the suffix 'sda2' after each noting the partition they referenced. The others I changed to reference the new boot partition, sda8 (as I saw no way to specify by label, :-(!). I specified the 'default' entry to boot from a correct entry. Rebooted. Nada. Zilch. Same problemo. No xen.gz. Upon returning to the grub manual intervention screen, I saw the *old* menu.lst. Hrmph! I continued boot and went back into yast2 bootloader. yast2 bootloader showed me my NEW menu -- not the menu I actually saw when I boot! THIS is a the bug. Yast2, as a system config util, should give the user the *real* representation of what is happening at boot-time, not some 'mocked' up simulation based on labeled file system mounts that the *boot loader* doesn't know about. As long as the boot loader doesn't know about labels and doesn't boot from labels, yast2, needs to look at the MBR, and see what physical partition is being booted from and look at the information in that partition. I even noted in yast2 -- that still had the 'menu.lst' file listed as being on "hd(0,1)" -- which it was NOT -- the menu.lst file it was displaying was located on sda8 hd(0,7). I labeled the new disk 'Boot' and renamed the old partition label 'Oboot'. I remount /boot, and it mounted the ne Reproducible: Always Steps to Reproduce: 1. See above in Details 2. 3. Actual Results: Yast2 bootloader doesn't use same info as real boot loader -- it uses correctly labeled partitions while the bootloader still doesn't understand them -- yast2 should check the real MBR data on disk to provide a admin tool that guarantees integrity against the actual system. Severity = major, perhaps even critical since it displays the FALSE information. However the 'priority' as moderated by likelihood of occurrence would be more like a 'Normal' level. -- 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 8

[Bug 568793] New: Updateapplet shows flash-player permanently:
by bugzilla_noreply＠novell.com 09 Feb '10

09 Feb '10

http://bugzilla.novell.com/show_bug.cgi?id=568793 http://bugzilla.novell.com/show_bug.cgi?id=568793#c0 Summary: Updateapplet shows flash-player permanently: Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Update Problems AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: revealed(a)freakmail.de QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.1.7) Gecko/20091222 SUSE/3.5.7-2.4 Firefox/3.5.7 The Updateapplet shows a patch for flash-player, but it is up to date itselves. wild-thing:/etc/zypp # zypper pch | grep flash Updates opensuse.org | flash-player | 1596 | recommended | Benötigt Updates opensuse.org | flash-player | 1707 | security | Installiert Updates opensuse.org | pullin-flash-player | 1595 | recommended | Nicht anwendbar It is the patch 1596, i guess. But flash-player-10.0.42.34-0.1.1.i586 is installed. How do i get rid of this? The updateapplet is permanently getting orange color. Here is what happens when trying to update with zypper in order to get rid of the orange color in updateapplet: wild-thing:/etc/zypp # zypper pchk Daten des Repositorys laden ... Installierte Pakete lesen ... 1 Patch benötigt (0 Sicherheits-Patches) last line says: 1 patch required (0 Security-Patches) wild-thing:/etc/zypp # zypper up Daten des Repositorys laden ... Installierte Pakete lesen ... Keine auszuführenden Aktionen. (last line means like "nothing to do".) Still same result. Reproducible: Always Steps to Reproduce: 1. zypper pch 2. zypper ref 3. zypper up Actual Results: flash-player update repeats to show up in updateapplet. Expected Results: The update should be applied or be obsoleted fully due to the newer installed version and updateapplet should have the up to date state. If you need any further information, please let me know. Please help me to get this fixed. Many thanks and Greetings, R -- 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 15

[Bug 557790] New: Aria2 and zypper behind a proxy does not work
by bugzilla_noreply＠novell.com 09 Feb '10

09 Feb '10

http://bugzilla.novell.com/show_bug.cgi?id=557790 http://bugzilla.novell.com/show_bug.cgi?id=557790#c0 Summary: Aria2 and zypper behind a proxy does not work Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: i686 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: roebenack.b(a)rittal.de QAContact: qa(a)suse.de Found By: --- Blocker: --- Created an attachment (id=329011) --> (http://bugzilla.novell.com/attachment.cgi?id=329011) Log files of zypper and aria and the command line User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.1.4) Gecko/20091016 SUSE/3.5.4-1.1.2 Firefox/3.5.4 I did upgrade from openSuSE 10.3 to 11.0 by zypper (add new repositories, zypper ref, zypper dup). All worked fine. After this I did an update from 11.0 -> 11.1. Zypper worked fine. Then I did an update of zypper with adding the repos of 11.2 and enter "zypper inst zypper". After clening up different dependencies, "zypper dup" does not work anymore. After I had restored my VM-Ware-Snapshot, I did a zypper dup without updating zypper by himself. The Dist-Update worked fine, but after this I get allways the same error while refreshing the repositories: --> Herunterladen fehlgeschlagen: /repodata/repomd.xml konntevon http://ftp5.gwdg.de/pub/linux/packman/suse/11.2/ nicht abgerufen werden Verlauf: -[AbstractCommand.cc:195]URI=http://ftp5.gwdg.de/pub/linux/packman/suse/11.2/repodata/repomd.xml <--- ============================================0 ws002-6859-667:/home/de04566 # zypper ar ftp://ftp5.gwdg.de/pub/linux/suse/opensuse/update/11.2 openSuSE_Update Repository 'openSuSE_Update' wird hinzugefügt [fertig] Repository 'openSuSE_Update' erfolgreich hinzugefügt Aktiviert: Ja Autoaktualisierung: Nein URI: ftp://ftp5.gwdg.de/pub/linux/suse/opensuse/update/11.2 ws002-6859-667:/home/de04566 # zypper ref Metadaten von Repository 'openSuSE_Update' werden abgerufen [\]/repodata/repomd.xml konnte von ftp://ftp5.gwdg.de/pub/linux/suse/opensuse/update/11.2 nicht abgerufen werden Abbrechen, wiederholen, ignorieren? [a/w/i/?] (a): a Metadaten von Repository 'openSuSE_Update' werden abgerufen [Fehler] Repository 'openSuSE_Update' ist ungültig. Can't provide /repodata/repomd.xml : /repodata/repomd.xml konnte von ftp://ftp5.gwdg.de/pub/linux/suse/opensuse/update/11.2 nicht abgerufen werden Bitte überprüfen Sie, ob die für dieses Repository bestimmten URIs zu einem gültigen Repository verweisen. Repository 'openSuSE_Update' wird aufgrund des obigen Fehlers übersprungen. Die Repositories konnten aufgrund von Fehlern nicht aktualisiert werden. =================================== We have a proxy here, so I had to edit the /root/.curlrc at OSS10.3 to work. This is why the 'ar'option of zypper work, but the ref option fails. After some minutes of trying and searching the web, I had found the following hint on: http://linux.derkeiler.com/Mailing-Lists/SuSE/2009-08/msg01072.html --> You can work around it by doing "export ZYPP_ARIA2C=0" and zypper dup after that. <-- Now "zypper ref" work again without any errors (also yast). I have no idea of programming, but this solved my problem! The aria2 version of my system was and still is aria2-1.5.2-2.3.1.i586 I have uploaded the log with and without the "export ZYPP_ARIA2C=0" workaround. It looks like the export workaround made zypper to fall back on curl and ignore aria. Reproducible: Always Steps to Reproduce: 1.Dist-Upgrade 11.1 to 11.2 with out updating zypper first with zypper inst zypper 2.After this you will not be able to update repositories without error messages of aria. => Herunterladen fehlgeschlagen: /repodata/repomd.xml konntevon http://ftp5.gwdg.de/pub/linux/packman/suse/11.2/ nicht abgerufen werden Verlauf: -[AbstractCommand.cc:195]URI=http://ftp5.gwdg.de/pub/linux/packman/suse/11.2/repodata/repomd.xml 4. Do "export ZYPP_ARIA2C=0" and all work fine. -- 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 3