|
Bugzilla – Full Text Bug Listing |
| Summary: | YaST2 hangs because of dangling reference in y2base | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Elmar Stellnberger <estellnb> |
| Component: | YaST2 | Assignee: | Ladislav Slezák <lslezak> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | benji |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | 32bit | ||
| OS: | openSUSE 10.3 | ||
| Whiteboard: | |||
| Found By: | Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
output of yast
file with list of packages to be installed valgrind log |
||
Created attachment 178162 [details]
output of yast
The konsole output of 'yast2 -i $(cat susedvd.lis)' has been clipped into backtrace.txt.
Created attachment 178163 [details]
file with list of packages to be installed
The dangling reference & crash appears to be a dupe of https://bugzilla.novell.com/show_bug.cgi?id=332917 The package management lock is separate though. lock has been freed by yast-installer by several closewins of error messages. Created attachment 178176 [details]
valgrind log
For the backtrace has not exactly been the same here you have another valgrind log:
valgrind --leak-check=full --show-reachable=yes yast2 -i $(cat inst/zusedvd-inst.lis)
Unfortunately there seem to be many different memory allocation problems occurring in very different situations: When selecting 'install more packages' after successfull install.: YaST got signal 11 at YCP file /usr/share/YaST2/clients/inst_packages.ycp:39 /sbin/YaST2: line 386: 11961 Speicherzugriffsfehler $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2QT_ARGS Will probably have to run YaST2 with valgrind by default to find out more. Additionally some strange messages can be found in /var/log/y2logRPMc (may not be related to these crashes): Inconsistency detected by ld.so: dl-open.c: 623: _dl_open: Assertion `_dl_debug_initialize (0, args.nsid)->r_state == RT_CONSISTENT' failed! Additional rpm output: /etc/init.d/java.binfmt_misc: line 81: /etc/rc.status: No such file or directory # file rc.status exists! Additional rpm output: /var/tmp/rpm-tmp.99338: line 1: rm: command not found Additional rpm output: /var/tmp/rpm-tmp.71194: line 16: sed: command not found /var/tmp/rpm-tmp.71194: line 137: sed: command not found /var/tmp/rpm-tmp.71194: line 258: sed: command not found 2007-10-09 15:44:23 xntp-4.2.4p3-25.i586.rpm installed ok Additional rpm output: Updating etc/sysconfig/ntp... rm: cannot remove `/etc/sysconfig/network/if-up.d/50-ntp': No such file or directory Additional rpm output: /var/tmp/rpm-tmp.1376: line 1: /usr/lib/ooo-2.0/program/pyunorc-update64: No such file or directory Additional rpm output: Starting SuSEconfig, the SuSE Configuration Tool... Running module permissions only Reading /etc/sysconfig and updating the system... Executing /sbin/conf.d/SuSEconfig.permissions... Finished. WARNING: Failed to parse default value `Munkaasztal h?tter?nek megv?ltoztat?sa;background.desktop,Nyomtat? hozz?ad?sa;gnome-cups-manager.desktop,H?l?zat be?ll?t?sa;YaST2/lan.desktop,Jelsz?csere;gnome-passwd.desktop,Felhaszn?l? hozz?ad?sa;YaST2/users.desktop,Adminisztr?tori be?ll?t?sok;YaST.desktop]' for schema (/schemas/apps/control-center/cc_actions_list) This bug might be a duplicate of bug #332917, could update libzypp and curl packages and try to reproduce it again? No errors have occurred any more in similar settings. curl-7.16.4-16 yast2-2.15.58-12 zypper-0.8.25-0.1 libzypp-3.26.3-1.1 |
> yast2 -i $(cat susedvd.lis) ThereUpon YaST2 has hanged because of dangling reference in y2base. [ctrl]-[C] YaST got signal 2 at YCP file /usr/share/YaST2/clients/sw_single.ycp:187 YaST got signal 3 at YCP file /usr/share/YaST2/clients/sw_single.ycp:187 killall yast2 Beendet Unfortunately even a reboot could not free the lock on the package management system; yast2-message (zypper ditto): Zugriff auf Paketmanagement gescheitert anderer Prozeß blockiert ... In a fact this has revealed two problems: * dangling reference in y2base * missing signal handlers for YaST (quit & free lock); free lock on shutdown