Bug 394977

Summary: yast2 sw_single crashes when wildcards used in search phrase
Product: [openSUSE] openSUSE 11.0 Reporter: Casual J. Programmer <casualprogrammer>
Component: YaST2Assignee: E-mail List <bnc-team-screening>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Major    
Priority: P5 - None CC: locilka
Version: Factory   
Target Milestone: ---   
Hardware: x86   
OS: openSUSE 11.0   
Whiteboard:
Found By: Beta-Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: /var/log/YaST2/*

Description Casual J. Programmer 2008-05-28 08:15:34 UTC 
On a system clean installed & updated from factory, yast2 sw_single aborts when wildcards used in "Search:" input field (i.e. *xen* ). 

# yast2 sw_single
terminate called after throwing an instance of 'zypp::Exception'
  what():  Invalid preceding regular expression
YaST got signal 6 at YCP file /usr/share/YaST2/clients/inst_packages.ycp:49
/sbin/yast2: line 421:  4973 Aborted                 $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS

# yast2 sw_single
terminate called after throwing an instance of 'zypp::Exception'
  what():  Invalid preceding regular expression
YaST got signal 6 at YCP file /usr/share/YaST2/clients/inst_packages.ycp:49
/sbin/yast2: line 421:  5231 Aborted                 $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS

Notebook: Fujitsu Siemens Amilo Si 1520
Graphics: Fujitsu Siemens Mobile 945GM/GMS/GME, 943/940GML Express
Monitor:  QUANTADISPLAY LCD Monitor 1280x800@60Hz
Wireless: Intel PRO/Wireless 3945ABG Network Connection
Sound:    82801G (ICH7 Family) High Definition Audio Controller
Desktop:  gnome-desktop-2.22.1-22
YaST GUI: yast2-qt-2.16.50-2
OS:       openSUSE 11.0 (i586) Beta3plus VERSION = 11.0
Kernel:   2.6.25.4-6-pae

yast2-2.16.71-2
Comment 1 Casual J. Programmer 2008-05-28 08:17:59 UTC 
Created attachment 218526 [details]
/var/log/YaST2/*
Comment 2 Lukas Ocilka 2008-05-28 08:19:26 UTC 

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