Bug 432942

Summary:	yast2 hangs in chroot environment, y2log reports "... Memory leak? ..."
Product:	[openSUSE] openSUSE 11.0	Reporter:	Norbert Klein <ch.kamal>
Component:	YaST2	Assignee:	E-mail List <yast2-maintainers>
Status:	RESOLVED FIXED	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P5 - None	CC:	mantel
Version:	Final
Target Milestone:	---
Hardware:	x86-64
OS:	openSUSE 11.0
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Norbert Klein 2008-10-07 09:14:26 UTC

I enter a functional system from a pxe booted rescue system with chroot. 

If I run yast (ncurses mode) from there the start screen of yast appears. I can select a  module but then nothing happens. I immediatley return to the start screen of yast.
When I exit yast and restart it it hangs completely, the start screen does not appear and I have to kill it with [ctrl-z] kill %1.

The following processes are still running:
/usr/lib/YaST2/bin/y2base menu -S ncurses
\_ sh -c /sbin/yast online_update  >&2
\_ /bin/bash /sbin/yast online_update
\_ /usr/lib/YaST2/bin/y2base online_update -S ncurses

If I boot the system directly yast works fine. So I compared the output of y2log. The difference is that in the chroot environment y2log reports additionally these lines:
rescue(2535) [ui-events] YEvent.cc(YEvent):43 Memory leak? 5 active events!
rescue(2535) [ui-events] YEvent.cc(YEvent):43 Memory leak? 6 active events!
rescue(2535) [ui-events] YEvent.cc(YEvent):43 Memory leak? 7 active events!
...
rescue(2535) [ui-events] YEvent.cc(YEvent):43 Memory leak? 30 active events!

Comment 1 Hubert Mantel 2008-10-09 14:37:47 UTC

Fixed in svn.

Comment 2 Norbert Klein 2008-10-09 18:23:59 UTC

I am not yet familiar with the build process, when will it be available as a normal yast update? I just want to avoid a self compiled yast on a production system.
Thanks anyway for the fix.