Bug 379025

Summary: YaST2 software management in GNOME end with SIGSEGV
Product: [openSUSE] openSUSE 10.3 Reporter: Pavel Nemec <pnemec>
Component: YaST2Assignee: Forgotten User h13THG8RK1 <forgotten_h13THG8RK1>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Critical    
Priority: P5 - None CC: forgotten_h13THG8RK1, mvidner
Version: Final   
Target Milestone: ---   
Hardware: x86-64   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: yast logs

Description Pavel Nemec 2008-04-11 07:52:50 UTC
Created attachment 207392 [details]
yast logs

I am using clean installation of  10.3 GNOME with latest updates. When trying select .software and install it, Window crash and xmessage window popup with error. 

(gtk:16487): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Unknown tag 'P' on line 1 char 12

(gtk:16487): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Unknown tag 'P' on line 1 char 12
Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve property `GtkTreeView::odd-row-color' of type `GdkColor' from rc file value "((GString*) 0x10f4720)" of type `GString'

** (gtk:16487): WARNING **: Markup parse error 'Chyba na Åádku 1 znak 53: Divný znak '@', bylo oÄekáváno '>' nebo '/' pro ukonÄení poÄáteÄního tagu elementu 'cyberorg' nebo pÅípadnÄ atribut; pravdÄpodobnÄ jste použili neplatný znak v názvu atributu'

** (gtk:16487): WARNING **: Markup parse error 'Chyba na Åádku 1 znak 53: Divný znak '@', bylo oÄekáváno '>' nebo '/' pro ukonÄení poÄáteÄního tagu elementu 'cyberorg' nebo pÅípadnÄ atribut; pravdÄpodobnÄ jste použili neplatný znak v názvu atributu'

** (gtk:16487): WARNING **: Markup parse error 'Chyba na Åádku 1 znak 53: Divný znak '@', bylo oÄekáváno '>' nebo '/' pro ukonÄení poÄáteÄního tagu elementu 'cyberorg' nebo pÅípadnÄ atribut; pravdÄpodobnÄ jste použili neplatný z nak v názvu atributu'

** (gtk:16487): WARNING **: Markup parse error 'Chyba na Åádku 1 znak 53: Divný znak '@', bylo oÄekáváno '>' nebo '/' pro ukonÄení poÄáteÄního tagu elementu 'cyberorg' nebo pÅípadnÄ atribut; pravdÄpodobnÄ jste použili neplatný znak v názvu atributu'
YaST got signal 11 at YCP file /usr/share/YaST2/clients/inst_packages.ycp:45
/sbin/yast2: line 386: 16487 NeoprávnÄný pÅístup do pamÄti (SIGSEGV)                     $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2QT_ARGS

(Sorry for czech)

another warning messages are printed in console

(y2controlcenter-gnome:16446): libgnomevfs-CRITICAL **: gnome_vfs_get_uri_from_local_path: assertion `g_path_is_absolute (local_full_path)' failed

(y2controlcenter-gnome:16446): libgnomevfs-CRITICAL **: gnome_vfs_monitor_add: assertion `text_uri != NULL' failed

(y2controlcenter-gnome:16446): libgnomevfs-CRITICAL **: gnome_vfs_get_uri_from_local_path: assertion `g_path_is_absolute (local_full_path)' failed

(y2controlcenter-gnome:16446): libgnomevfs-CRITICAL **: gnome_vfs_monitor_add: assertion `text_uri != NULL' failed


YaST logs will follow
Comment 1 Lukas Ocilka 2008-04-11 12:44:14 UTC
Attach also GDB logs, please

http://en.opensuse.org/Bugs/YaST#How_can_I_start_YaST_in_debugger_.28gdb.29.3F_How_can_I_create_a_backtrace.3F

strace output might help too
thx
Comment 2 Martin Vidner 2008-04-11 16:18:37 UTC
maybe the frontend is getting confused by some unusual repository. please also try whether it crashes with yast2-qt, yast2-ncurses, or zypper.
Comment 5 Pavel Nemec 2008-04-16 11:36:56 UTC
(In reply to comment #2 from Martin Vidner)
> maybe the frontend is getting confused by some unusual repository. please also
> try whether it crashes with yast2-qt, yast2-ncurses, or zypper.
> 
yast2-qt did the job without crash. GTK crash two times. 
Comment 6 Lukas Ocilka 2008-04-16 12:44:55 UTC
So it really seems to be problem in yast2-gtk*
Comment 7 Forgotten User h13THG8RK1 2008-04-16 14:04:59 UTC
There is an issue with the package selector in 10.3 and 64-bit systems. :-/ Sorry about that.

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