Mailinglist Archive: opensuse-bugs (4664 mails)

< Previous Next >
[Bug 577012] New: yast2 crashes on startup with floating point exception when logged in via ssh.
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Thu, 4 Feb 2010 15:14:06 +0000
  • Message-id: <bug-577012-21960@xxxxxxxxxxxxxxxxxxxxxxxx/>

Summary: yast2 crashes on startup with floating point exception
when logged in via ssh.
Classification: openSUSE
Product: openSUSE 11.2
Version: Final
Platform: i586
OS/Version: openSUSE 11.2
Status: NEW
Severity: Major
Priority: P5 - None
Component: YaST2
AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: george@xxxxxxxxxxx
QAContact: jsrain@xxxxxxxxxx
Found By: ---
Blocker: ---

User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US;
rv: Gecko/20091221 Firefox/3.5.7

I am on a remote computer. I connect to the openSUSE machine with ssh, try to
run yast2, and it crashes on startup.

local_machine:~ $ ssh openSUSE_machine -l root
Last login: Tue Feb 2 20:09:29 2010 from local_machine.dom.tld
Have a lot of fun...
openSUSE_machine:~ # yast2
/sbin/yast2: line 454: 12999 Floating point exception$y2ccbin $Y2UI_ARGS "$@"
openSUSE_machine:~ #

I believe the failure is related to the X server on local_machine. In the
example above, local_machine is a macbook running OSX 10.6.2 and XQuartz 2.3.4.
If I connect to the openSUSE machine with ssh from my neighbor's linux box,
then yast does not crash. However, I have no problem running any other X
program using the macbook -- it is ONLY yast that crashes.

So basically, something seems to be wrong with yast that is exposed by the
XQuartz X-server.

Thank you for your attention, and thank you for writing such amazingly cool

Reproducible: Always

Steps to Reproduce:
See details above.
Actual Results:
yast crashes on startup.

Expected Results:
yast should not crash on startup.

Presumably the details above are enough. If not, I will supply any thing
needed, such as logs etc. This is reproducible.

Configure bugmail:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >