September 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 800889] New: BIOS says "No OS" on disk after fresh install of 12.3B1 trough USB
by bugzilla_noreply＠novell.com 05 Sep '13

05 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=800889 https://bugzilla.novell.com/show_bug.cgi?id=800889#c0 Summary: BIOS says "No OS" on disk after fresh install of 12.3B1 trough USB Classification: openSUSE Product: openSUSE 12.3 Version: RC 1 Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: j.reitsma(a)hccnet.nl QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 After a failure upgrading my experimental disk from 12.2 to 12.3 (see https://bugzilla.novell.com/show_bug.cgi?id=799296 I downloaded the DVD-iso (openSUSE-DVD-Build0348-x86_64.iso), applied isohybrid to it and installed from the then created USB stick. Installation goes without any warning or error, but after it's finished the system won't boot up from the disk: the bios says "No operating system". I can mount and read the /boot, / and /home partitions on the disk without problems, if I boot up from another disk in the system (in my case, that's an 12.2 system). 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 7

[Bug 370870] alternative mirrors via one-click
by bugzilla_noreply＠novell.com 05 Sep '13

05 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=370870 https://bugzilla.novell.com/show_bug.cgi?id=370870#c13 Ladislav Slezak <lslezak(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |WONTFIX --- Comment #13 from Ladislav Slezak <lslezak(a)suse.com> 2013-09-05 09:18:09 UTC --- I would leave the mirroring at libzypp (using metalink), I don't think there is anything to do in Yast. -- 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 821564] New: yast sw_single crashes on startup
by bugzilla_noreply＠novell.com 05 Sep '13

05 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=821564 https://bugzilla.novell.com/show_bug.cgi?id=821564#c0 Summary: yast sw_single crashes on startup Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 1 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jslaby(a)suse.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- Like this: ... #6 0x00007f96b704b163 in _YUI_THROW<YUINoDialogException> (exception_r=..., where_r=...) at /usr/src/debug/libyui-3.0.4/src/YUIException.h:915 #7 0x00007f96b7049b63 in YDialog::deleteTopmostDialog (doThrow=<optimized out>) at /usr/src/debug/libyui-3.0.4/src/YDialog.cc:510 #8 0x00007f96b72b6d45 in YCP_UI::CloseDialog () at YCP_UI.cc:615 #9 0x00007f96b72a586a in YUINamespace::CloseDialog (this=<optimized out>) at YUINamespace.cc:214 #10 0x00007f96b72a7964 in YUIFunction::evaluateCall_int (this=0x21e1570) at UIBuiltinCalls.h:53 #11 0x00007f96b72bf679 in YCPBuiltinCaller::call (this=0x2690650) at YCPBuiltinCaller.cc:39 #12 0x00007f96b7025f11 in YUI::uiThreadMainLoop (this=0x263b390) at /usr/src/debug/libyui-3.0.4/src/YUI.cc:377 #13 0x00007f96b702606e in start_ui_thread (yui=<optimized out>) at /usr/src/debug/libyui-3.0.4/src/YUI.cc:493 #14 0x00007f96b90cfe0e in start_thread (arg=0x7f96abfbc700) at pthread_create.c:308 #15 0x00007f96b83e5b9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Which is this: 505 YDialog::deleteTopmostDialog( bool doThrow ) 506 { 507 if ( _dialogStack.empty() ) 508 { 509 if ( doThrow ) 510 YUI_THROW( YUINoDialogException() ); ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ It crashes with both ncurses and qt frontend. -- 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 780960] New: Parser error when requesting xml format (API)
by bugzilla_noreply＠novell.com 05 Sep '13

05 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=780960 https://bugzilla.novell.com/show_bug.cgi?id=780960#c0 Summary: Parser error when requesting xml format (API) Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: WebYaST AssignedTo: lslezak(a)suse.com ReportedBy: bgeuken(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- 1. Enable api in /etc/webyast/config.yml 2. Request xml format from webyast, eg. https://localhost:4984/firewall.xml or https://localhost:4984/administrator.xml => XML Parsing Error: not well-formed Location: https://localhost:4984/firewall.xml Line Number 1, Column 1:<?xml version="1.0" encoding="UTF-8"?> Via curl it's: bgeuken@g196:/> curl -u root http://localhost:4984/firewall.xml Enter host password for user 'root': <html> <head><title>302 Found</title></head> <body bgcolor="white"> <center><h1>302 Found</h1></center> <hr><center>nginx/1.0.15</center> </body> </html> -- 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 828254] New: YaST /etc/sysconfig editor returns "Error Configuration script failed ." message each time .
by bugzilla_noreply＠novell.com 05 Sep '13

05 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=828254 https://bugzilla.novell.com/show_bug.cgi?id=828254#c0 Summary: YaST /etc/sysconfig editor returns "Error Configuration script failed ." message each time . 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: bkbin005(a)rinku.zaq.ne.jp QAContact: jsrain(a)suse.com Found By: --- Blocker: --- Created an attachment (id=546909) --> (http://bugzilla.novell.com/attachment.cgi?id=546909) y2log and screenshot User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.116 Safari/537.36 I am using openSUSE 12.3 x86-64 KDE Desktop . And I am testing openSUSE 13.1 Milestone 2 x86-64 GNOME Desktop too . Both 12.3 and 13.1 Milestone 2, YaST /etc/sysconfig editor returns "Error Configuration script failed ." message each time . I attach y2log and a screenshot . Reproducible: Always Steps to Reproduce: 1. Login as root . 2. # /usr/lib/YaST2/y2base sysconfig qt 3. Edit /etc/sysconfig (ex: Change Desktop->Display manager->DISPLAYMANAGER into gdm from kdm4) 4. Select OK . 5. In "Save Modified Variables" window, select Save . Actual Results: YaST2 Dialog box appears, it says "Error Configuration script failed ." Expected Results: The Dialog box should not appear . Please see also: http://forums.opensuse.org/english/get-technical-help-here/applications/486… http://lists.opensuse.org/opensuse-ja/2013-07/msg00022.html -- 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 837257] New: Changing variable SYSTOHC in /etc/sysconfig Editor fails
by bugzilla_noreply＠novell.com 05 Sep '13

05 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=837257 https://bugzilla.novell.com/show_bug.cgi?id=837257#c0 Summary: Changing variable SYSTOHC in /etc/sysconfig Editor fails 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: ulrichvoigt(a)web.de QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:23.0) Gecko/20100101 Firefox/23.0 When using the /etc/sysconfig editor of YaST2 the change of the variable SYSTOHC or FORCE_SYSTOHC fails ("Configuration script failed"). The logfile /var/log/YaST2/y2log shows that /sbin/SuSEconfig is missing: 2013-08-28 11:13:22 <1> swq1-sp.gematronik.com(29564) [YCP] sysconfig/complex.ycp:66 Changes will be written. 2013-08-28 11:13:22 <1> swq1-sp.gematronik.com(29564) [YCP] Progress.ycp:401 Progress::New(Saving sysconfig Configuration, 6, ["Write the new settings", "Activate the changes"]) 2013-08-28 11:13:22 <1> swq1-sp.gematronik.com(29564) [YCP] Progress.ycp:490 No progress icons defined 2013-08-28 11:13:22 <1> swq1-sp.gematronik.com(29564) [qt-styler] QY2Styler.cc(getScaled):221 Loaded pixmap from "work_area" size: 800x600 2013-08-28 11:13:23 <1> swq1-sp.gematronik.com(29564) [YCP] Sysconfig.ycp:988 Starting: /sbin/SuSEconfig 2013-08-28 11:13:23 <1> swq1-sp.gematronik.com(29564) [YCP] Sysconfig.ycp:992 Result: 127 2013-08-28 11:13:23 <3> swq1-sp.gematronik.com(29564) [YCP] Report.ycp:544 Configuration script failed. 2013-08-28 11:13:23 <2> swq1-sp.gematronik.com(29564) [qt-ui] YQUI.cc(qMessageHandler):715 <libqt-warning> QCssParser::parseHexColor: Unknown color name '#b9dc8cf' 2013-08-28 11:13:23 <2> swq1-sp.gematronik.com(29564) [qt-ui] YQUI.cc(qMessageHandler):715 <libqt-warning> QCssParser::parseHexColor: Unknown color name '#ffff' 2013-08-28 11:13:23 <2> swq1-sp.gematronik.com(29564) [qt-ui] YQUI.cc(qMessageHandler):715 <libqt-warning> QCssParser::parseHexColor: Unknown color name '#ffff' 2013-08-28 11:13:23 <1> swq1-sp.gematronik.com(29564) [ui] YPushButton.cc(setFunctionKey):188 Guessing button role YOKButton for YPushButton "OK" at 0x7ff20c3a4c68 from function key F10 2013-08-28 11:13:25 <1> swq1-sp.gematronik.com(29564) [YCP] clients/sysconfig.ycp:109 Sysconfig module finished 2013-08-28 11:13:25 <1> swq1-sp.gematronik.com(29564) [YCP] clients/sysconfig.ycp:110 ---------------------------------------- Reproducible: Always Steps to Reproduce: 1. Start YaST2 2. Open /etc/sysconfig Editor 3. Seach for variable SYSTOHC 4. Change the value of SYSTOHC (to 'yes' or 'no') 5. Press "OK" to save the changes Actual Results: A popup shows the message "ERROR Configuration script failed.". Expected Results: There should be no error. -- 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 782367] New: WebYaST terminal application doesn't work
by bugzilla_noreply＠novell.com 05 Sep '13

05 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=782367 https://bugzilla.novell.com/show_bug.cgi?id=782367#c0 Summary: WebYaST terminal application doesn't work Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: WebYaST AssignedTo: kkaempf(a)suse.com ReportedBy: m407(a)mail.ru QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20100101 Firefox/15.0.1 With a fresh installed server, base repos, updated I got an error. Reproducible: Always Steps to Reproduce: 1. Install openSUSE as server (minimal no X) 2. update 3. install webyast 4. connect to webyast and try to launch terminal Actual Results: Operation is forbidden. If you have to do it, please contact system administrator You are not authorized to access this page. (org.opensuse.yast.modules.yapi.terminal.read) Expected Results: Working terminal -- 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 793123] New: shellinabox, -_ keys do not work in firefox
by bugzilla_noreply＠novell.com 05 Sep '13

05 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=793123 https://bugzilla.novell.com/show_bug.cgi?id=793123#c0 Summary: shellinabox, -_ keys do not work in firefox Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: All OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bernet(a)physik.uzh.ch QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20100101 Firefox/17.0 If you access shellinabox with firefox 2.10 and newer the keys "-" and "_" do not work. This issue is known, it's issue 202 http://code.google.com/p/shellinabox/issues/detail?id=202 There seems to be a patch. Reproducible: Always Steps to Reproduce: 1. Access shellinabox (on a openSUSE installation) with firefox 2. Type - Actual Results: Nothing happens Expected Results: One should see a "-" -- 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 12

[Bug 755725] New: Opensuse VM in cloud fails to boot intermittently with error message "Segmentation Fault"
by bugzilla_noreply＠novell.com 05 Sep '13

05 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=755725 https://bugzilla.novell.com/show_bug.cgi?id=755725#c0 Summary: Opensuse VM in cloud fails to boot intermittently with error message "Segmentation Fault" Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: Other OS/Version: openSUSE 12.1 Status: NEW Severity: Major Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: habdi(a)microsoft.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0) Steps: 1. Upload Opensuse VHd which has olaf latest rpm installed 2. Create hosted service and create a VM using this VHD Intermittently provisioning fails, VM fails to boot with segmanation fault messages. (Attached logs) Settings: 2 vcpus, 3584 MB ram (3.5G) Reproducible: Sometimes Steps to Reproduce: Steps: 1. Upload Opensuse VHd which has olaf latest rpm installed 2. Create hosted service and create a VM using this VHD Intermittently provisioning fails, VM fails to boot with segmanation fault messages. (Attached logs) Settings: 2 vcpus, 3584 MB ram (3.5G) Actual Results: Provisioning fails Expected Results: Provisioning should always succeed -- 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 780333] New: YaST2 Wagon is insufficiently well documented, and appears to be unsupported
by bugzilla_noreply＠novell.com 05 Sep '13

05 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=780333 https://bugzilla.novell.com/show_bug.cgi?id=780333#c0 Summary: YaST2 Wagon is insufficiently well documented, and appears to be unsupported Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: philip(a)pjtait.org QAContact: jsrain(a)suse.com 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 This is intended as a constructive comment on an issue that hinders wider adoption of openSUSE. openSUSE's version upgrade procedure is quite complex and daunting to non-experts, and does not compare well with other Linux distributions. I tried installing "Wagon" but the documentation seems to be for developers, and it is prominently described as unstable. Reproducible: Always Steps to Reproduce: 1. Somehow find out that the version upgrade tool is called "Wagon". 2. Install it. 3. Discover that there seems to be little information or support for it. Actual Results: Not clear on how to use it to update my computer. Expected Results: Easy-to-use tool that checks available upgrades, checks system eligibility, and walks me through the process. -- 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 6