July 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 630434] New: Server refuses to boot, while used iSCSI based non "/" file system is not available.
by bugzilla_noreply＠novell.com 27 Apr '16

27 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=630434 http://bugzilla.novell.com/show_bug.cgi?id=630434#c0 Summary: Server refuses to boot, while used iSCSI based non "/" file system is not available. Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: SLES 11 Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: DOlsson(a)WEB.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.6) Gecko/20100626 SUSE/3.6.6-1.1 Firefox/3.6.6 On our SLES 11 GM based "mirror" server (running as a virtual XEN guest), we are using iSCSI to attach to our NAS holding the "/data" file system, whereas all other file systems (/, /boot, /var, /home) are placed on local disk. When rebooting the server, it refuses to boot correctly, while it is not able to "fsck" the "/data" file system -- The system stops in "(repair filesystem) #" mode (after having entered the "root" password). Using the "nofail" option for the "/data" file system helps to get the system to reboot correctly, but in this case the "/data" file system is neither being checked nor mounted during the system startup, which therefore -- once again -- makes the system unusable! Using the "nofail" option is part of the "solution" listed in the SLES 11 SP1 documentation, but since the system is unusable, this is *not* the solution to the problem. The problem is that the "mkinitrd" is and the boot scripts are not capable of handling iSCSI attached file systems correctly. The correct way of handling iSCSI attached devices are: - All iSCSI devices having the "onboot" set as node startup setting must be attached during the "initrd" boot sequence (i.e. by "boot.open-iscsi") -- and this *independent* of whether the "/" (root) file system is attached via iSCSI or not, - All iSCSI devices having the "automatic" set as node startup setting need to be attached during the normal booting sequence (i.e. by "open-iscsi"), - All iSCSI devices having the "manual" set as node startup setting should be left alone. Using such a attaching schema will ensure that a server is capable of being booted with all its iSCSI file systems being attached, checked and mounted. Reproducible: Always Steps to Reproduce: 1a. Setup an iSCSI device and mount it e.g. as "/home" (no changes to "/etc/fstab"). 2a. Reboot the system 3a. System fails to boot, while "/home" is not available. 1b. Setup an iSCSI device and mount it e.g. as "/home", and add the "nofail" option in "/etc/fstab" to the "/home" mount point. 2b. Reboot system. 3b. System boots, but "/home" is neither checked nor mounted! Actual Results: When using iSCSI devices for non root file systems - the system is not able to boot, when the file system on the iSCSI device is listed in "/etc/fstab" as a file system that should be mounted or - the system boots boots, when the file system on the iSCSI device has been marked with "nofail" in "/etc/fstab", but the file is neither being checked nor it is being mounted. Expected Results: System boots with all file systems listed in "/etc/fstab" being checked and mounted independently of whether they are on local or iSCSI attached disks. -- 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 91

[Bug 832519] New: zypper --sort-by-priority does not sort numerically
by bugzilla_noreply＠novell.com 27 Apr '16

27 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=832519 https://bugzilla.novell.com/show_bug.cgi?id=832519#c0 Summary: zypper --sort-by-priority does not sort numerically Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: alanprescott(a)yahoo.co.uk QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:22.0) Gecko/20100101 Firefox/22.0 In list repos option with zypper, using the -P|--sort-by-priority does an alpha sort rather than a numeric sort - i.e. priority 21 is sorted before 3,4,5 etc. Reproducible: Always Steps to Reproduce: 1. run zypper lr -Pe file.repo ; less file.repo 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 10

[Bug 710541] New: Zypper gives no information about where source-install downloads files
by bugzilla_noreply＠novell.com 27 Apr '16

27 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=710541 https://bugzilla.novell.com/show_bug.cgi?id=710541#c0 Summary: Zypper gives no information about where source-install downloads files Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: All OS/Version: openSUSE 11.4 Status: NEW Severity: Enhancement Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: admin(a)damienradtke.org QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.107 Safari/535.1 When installing a package's source using "zypper source-install", no information can be found about where the source is actually downloaded to. "zypper help source-install" doesn't help, nor does "man zypper". The target location is /usr/src/packages/SOURCES, but those unfamiliar with RPM practices won't know that. Please provide a message, such as in the help text for source-install, that points the user to the directory the source was downloaded to. 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 10

[Bug 637791] New: libzypp log: wrong error message if gpg not installed
by bugzilla_noreply＠novell.com 27 Apr '16

27 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=637791 https://bugzilla.novell.com/show_bug.cgi?id=637791#c0 Summary: libzypp log: wrong error message if gpg not installed Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: dheidler(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- the error message tells you, that the files in the repository are not existing, but the real issue is, that gpg is not installed we should check for gpg installed and greate a more expressive message -- 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 755383] New: VUL-0: python: hash collision DoS
by bugzilla_noreply＠novell.com 27 Apr '16

27 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=755383 https://bugzilla.novell.com/show_bug.cgi?id=755383#c0 Summary: VUL-0: python: hash collision DoS Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: Other Status: ASSIGNED Severity: Normal Priority: P5 - None Component: Other AssignedTo: jmatejek(a)suse.com ReportedBy: mvyskocil(a)suse.com QAContact: security-team(a)suse.de CC: lnussel(a)suse.com, security-team(a)suse.de Depends on: 751718 Found By: Other Blocker: --- +++ This bug was initially created as a clone of Bug #751718 +++ Your friendly security team received the following report via oss-security. Please respond ASAP. The issue is public. CVE-2012-1150 python dictionaries are prone to hash table collision attacks. Web services for example might store parameters of a GET or POST request in a dictionary. An attacker may use this to cause high CPU load http://bugs.python.org/issue13703 http://seclists.org/fulldisclosure/2011/Dec/477 http://www.ocert.org/advisories/ocert-2011-003.html https://bugzilla.redhat.com/show_bug.cgi?id=750555 --------------------------- This one is for python3 for openSUSE 12.1 only. -- 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 702825] New: IcedTeaPlugin.so gives undefined symbol, plugin_debug, when icedtea-web is installed
by bugzilla_noreply＠novell.com 27 Apr '16

27 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=702825 https://bugzilla.novell.com/show_bug.cgi?id=702825#c0 Summary: IcedTeaPlugin.so gives undefined symbol, plugin_debug, when icedtea-web is installed Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: Java AssignedTo: bnc-team-java(a)forge.provo.novell.com ReportedBy: falolaf(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:5.0) Gecko/20100101 Firefox/5.0 After the security update of java-1_6_0-openjdk the icedtea plugin in firefox isn't working. The following is outputed when trying to load an applet: LoadPlugin: failed to initialize shared library /usr/lib64/IcedTeaPlugin.so [/usr/lib64/IcedTeaPlugin.so: undefined symbol: plugin_debug] Installed packages: icedtea-web-1.1-0.2.1 java-1_6_0-openjdk-1.6.0.0_b22.1.10.2-4.3.1 java-1_6_0-openjdk-devel-1.6.0.0_b22.1.10.2-4.3.1 Downgrading to previous version and installation of java-1_6_0-openjdk-plugin and it's working again. Reproducible: Always Steps to Reproduce: See details. Actual Results: See details. Expected Results: See details. -- 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 22

[Bug 804502] New: when using the default "use the user password for root", no user is created
by bugzilla_noreply＠novell.com 21 Apr '16

21 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=804502 https://bugzilla.novell.com/show_bug.cgi?id=804502#c0 Summary: when using the default "use the user password for root", no user is created Classification: openSUSE Product: openSUSE Factory Version: 12.3 Beta 1 Platform: i586 OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jdd(a)dodin.org QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/17.0 Firefox/17.0 Hello, Just got a pretty weird bug. As a workflow to test an other bug I tryed to install very last 12.3 iso (rc1 probably, build 024) I let the tick for "use same passwd for root" what I never do usually. I used "culte" for user, "culte123" as passwd (dummy, so I can share :-). I was asked "do you really want that" and said yes. When te (xfce, no boot manager) install was over I could boot (with other party grub legacy). The boot was incredibly long - but the computer is old. and on the xfce login, I couldn't log. No user. But I could perfectly log as root with culte123!!! and veryfy, nothing in /home. loging xfce as root I could add the culte user with yast and log normally jdd Reproducible: Didn't try Steps to Reproduce: very long to reproduce :-( Actual Results: I don't see hox this can happen. I was never asked for the root pass, of course -- 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 13

[Bug 831791] New: YaST bootloader (grub2) failed to add a parameter with a space in it.
by bugzilla_noreply＠novell.com 20 Apr '16

20 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=831791 https://bugzilla.novell.com/show_bug.cgi?id=831791#c0 Summary: YaST bootloader (grub2) failed to add a parameter with a space in it. Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: adrien.clerc(a)gls-france.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:22.0) Gecko/20100101 Firefox/22.0 I want to add acpi_osi="!Windows 2012" on the kernel command line (see #831790), and it fails with the following error: "Command 2012 not found" It seems that the space doesn't make him happy. Adding it manually to grub.cfg works like a charm. 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 5

[Bug 549849] New: Eclipse doesn't accept mouse clicks on buttons
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=549849 Summary: Eclipse doesn't accept mouse clicks on buttons Classification: openSUSE Product: openSUSE 11.2 Version: RC 1 Platform: x86 OS/Version: openSUSE 11.2 Status: NEW Severity: Major Priority: P5 - None Component: Development AssignedTo: pth(a)novell.com ReportedBy: davor.cengija(a)gmail.com QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.3) Gecko/20090909 SUSE/3.5.3-3.2 Firefox/3.5.3 As described on Beta and Pre-release forum, http://forums.opensuse.org/pre-release-beta/424021-eclipse-doesnt-accept-mo… I just downloaded the newest Eclipse, just to be sure, but I had the same problem with some older version. Start Eclipse, and for example try to create a new project. Enter the project's name and click Next. The button recognizes that it's being clicked (e.g. gets focus, changes color etc) but nothing happens. Pressing enter works (as the button has focus now). The same thing happens on the next screen with the Finish button. Reproducible: Always Steps to Reproduce: 1. Start Eclipse 2. Click File>New>Java Project 3. Enter project's name, click Next - nothing happens 4. Press Enter button - wizard advances to next step, as expected It seems that this problems is easiliy reproducible, and is related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=288909 However, it is quite serios, almost a showstopper for a number of users. If you need additional details, don't hesitate to ask, I'm more than willing to assist here. -- 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 9

[Bug 637382] New: (r)quotad init missing /etc/sysconfig/quotad for setting of "-p (port)", etc.
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

https://bugzilla.novell.com/show_bug.cgi?id=637382 https://bugzilla.novell.com/show_bug.cgi?id=637382#c0 Summary: (r)quotad init missing /etc/sysconfig/quotad for setting of "-p (port)", etc. Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: All OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: pgngw+dev001+novell.com(a)f-m.fm QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.8) Gecko/20100723 SUSE/3.6.8-1.3 Firefox/3.6.8 goal is to set *static* ports for nfs services. refs: http://www.lowth.com/LinWiz/nfs_help.html http://www.novell.com/support/viewContent.do?externalId=7000524&sliceId=1 http://wiki.debian.org/SecuringNFS whereas MOUNTD & STATSD opts can be set/overridden in /etc/sysconfig/nfs, QUOTAD is missing the same option. cat /etc/init.d/quotad ... # /etc/init.d/quotad # # and its symbolic link # # /sbin/rcquotad ... rpm -q --whatprovides /etc/init.d/quotad quota-nfs-3.17-7.2.x86_64 ls -al /etc/sysconfig/*quota* /bin/ls: No match. @ http://www.novell.com/support/viewContent.do?externalId=7000524&sliceId=1 "... /etc/services .. * rquota, : add the port assignment to the file. For example: rquotad 4003/tcp rquotad 4003/udp .. Please note that custom edits of the /etc/init.d/nfsserver are not recommend, nor is it supported. Further, changed /etc/init.d scripts may be replaced during online updates or when updating to a new service pack. " iiuc, /etc/services is NOT guaranteed safe from upgrades/overwrites. I tried to raise the issue in #opensuse-factory, as it's likely an issue in/for 11.4 as well. Told 'not interested' ... Checked @ #opensuse, told that the port mods should be made in /etc/sysconfig/foo, ----------------------------- [12:21] <dev001> since there are some 'packagers' around -- where can I find Packaging Guidelines for if/when to use /etc/sysconfig/blah + /etc/init.d/blah pairs? reading here, http://en.opensuse.org/openSUSE:Packaging_Conventions_RPM_Macros, I see mention -- but not guideline statement/policy. [12:21] <yaloki> dev001: there is no need for a guideline [12:22] <yaloki> dev001: you need /etc/init.d/foo to have a script to start a daemon [12:22] <yaloki> dev001: if you can make it configurable (e.g. port number or such), then you store that configuration in /etc/sysconfig/foo and use those parameters in the init script [12:23] <dev001> yaloki: sure, that makes sense. and that's what I thought. but, it's not what novell does/recommends -- in at least the one case i'm looking at. [12:24] <yaloki> dev001: I'm packaging for SUSE/openSUSE since 10 years, so take my word for it [12:24] <yaloki> dev001: and that's also the convention [12:24] <dev001> yaloki: I'm not disagreeing with you. i'm telling you , however, what Novell does in the case of quotad. they recommend making static port assignments by mod'ing /etc/services. [12:25] <yaloki> dev001: well maybe that's because quotad is not configurable in a different way [12:25] <yaloki> dev001: many daemons look up which port they should listen on in /etc/services [12:25] <yaloki> dev001: (actually it's even a system call in glibc) [12:26] <dev001> yaloki: it most certainly is. adding a "-p port" spec is straightforward, and frequently/widely used. [12:26] <yaloki> dev001: well then the packager simply forgot to do that [12:26] <yaloki> dev001: file a bug ----------------------------- checking man page, man rquotad ------------------------- RQUOTAD(8) NAME rquotad, rpc.rquotad - remote quota server SYNOPSIS rpc.rquotad [ -sSFI ] [ -p port ] .. OPTIONS .. -p port, --port port Listen on alternate port port. .. ------------------------- 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 42