Bug 214586

Summary: "Yast2 printer" crashes
Product: [openSUSE] openSUSE 10.2 Reporter: Gerhard Heinzel <gh55>
Component: YaST2Assignee: Michal Zugec <mzugec>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Major    
Priority: P5 - None    
Version: Alpha 5   
Target Milestone: ---   
Hardware: x86-64   
OS: SUSE Other   
Whiteboard:
Found By: Beta-Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Gerhard Heinzel 2006-10-24 07:05:17 UTC
attached is ths output of various attempts.
Other Yast2 modules run ok.


Command: /sbin/yast2 printer &
Segmentation fault at Printerdb.ycp:376
/sbin/yast2: line 233:  5958 Segmentation fault      $ybindir/y2base $module "$@" qt "$Y2_GEOMETRY" $Y2QT_ARGS

# yast2 printer 
terminate called after throwing an instance of 'std::bad_alloc'
  what():  St9bad_alloc
/sbin/yast2: line 233:  5705 Aborted                 $ybindir/y2base $module "$@" qt "$Y2_GEOMETRY" $Y2QT_ARGS

Command: /sbin/yast2 printer &
terminate called after throwing an instance of 'std::bad_alloc'
  what():  St9bad_alloc
/sbin/yast2: line 233:  5238 Aborted                 $ybindir/y2base $module "$@" qt "$Y2_GEOMETRY" $Y2QT_ARGS

Command: /sbin/yast2 printer &
*** glibc detected *** /usr/lib/YaST2/bin/y2base: malloc(): memory corruption: 0x00000000010b2812 ***
======= Backtrace: =========
/lib64/libc.so.6[0x2b61906ec8fe]
/lib64/libc.so.6[0x2b61906ee797]
/lib64/libc.so.6(__libc_malloc+0x86)[0x2b61906f0396]
/usr/lib64/libstdc++.so.6(_Znwm+0x1d)[0x2b618ffd841d]
/usr/lib64/libstdc++.so.6(_ZNSs4_Rep9_S_createEmmRKSaIcE+0x21)[0x2b618ffb6d21]
/usr/lib64/libstdc++.so.6(_ZNSs4_Rep8_M_cloneERKSaIcEm+0x2b)[0x2b618ffb796b]
/usr/lib64/libstdc++.so.6(_ZNSsC1ERKSs+0x4f)[0x2b618ffb810f]
/usr/lib64/YaST2/plugin/libpy2ag_ppd.so.2(_ZN3PPD12cleanupListsEv+0x225)[0x2aaaabb0eb85]
/usr/lib64/YaST2/plugin/libpy2ag_ppd.so.2(_ZN3PPD14createdbThreadEPKc+0xf0f)[0x2aaaabb1d54f]
/lib64/libpthread.so.0[0x2b618eb4c09e]
/lib64/libc.so.6(clone+0x6d)[0x2b619074148d]
Comment 1 Michal Zugec 2006-10-24 13:16:04 UTC

*** This bug has been marked as a duplicate of bug 202903 ***