fc12 yumex crashes

[petarp]

Need help - yumex crashes after checking repositories:

    running
Current Settings
    autorefresh: True
    branding_title: 'Yum Extender NextGen'
    color_install: 'darkgreen'
    color_normal: 'black'
    color_obsolete: 'blue'
    color_update: 'red'
    debug: False
    disable_repo_page: False
    plugins: True
    proxy: ''
    recentdays: 14
    repo_exclude: ['debug', 'source']
    win_height: 600
    win_sep: 300
    win_width: 1000
    yumdebuglevel: 2
/usr/lib/python2.6/site-packages/guihelpers/__init__.py:199: GtkWarning: gtk_scrolled_window_add(): cannot add non scrollable widget use gtk_scrolled_window_add_with_viewport() instead
  self.add_from_file(filename)
eth0 (e1000e) is connected
/usr/lib/python2.6/site-packages/yumexgui/gui.py:179: DeprecationWarning: Use the new widget gtk.Tooltip
  self.tooltip = gtk.Tooltips()
/usr/lib/python2.6/site-packages/yumexgui/gui.py:206: DeprecationWarning: Use the new widget gtk.Tooltip
  self.tooltip.set_tip(button, tooltip)
eth0 (e1000e) is connected
Connected to an network
eth0 (e1000e) is connected
Starting yum child process
YUM: Loaded plugins: presto
Downloaded : rpmfusion-free/group_gz ( 1.5 k )
Downloaded : rpmfusion-free-updates/group_gz ( 1.5 k )
Downloaded : rpmfusion-nonfree/group_gz ( 1.0 k )
Downloaded : rpmfusion-nonfree-updates/group_gz ( 1.0 k )
History Enabled
/usr/bin/yumex: line 5:  2680 Segmentation fault      (core dumped) /usr/bin/python /usr/share/yumex/yumex.pyc $*

yum clean all

did not help.
Could not find the same bug anywhere.

[jtripcevic]

I just found that I have the same problem. I looked at a stack trace-back in gdb. Seems that the latest gtk2 update added a new function called "temporary_disable_extension_events" in gdkwindow.c. This function gets into a loop by recursively calling itself so you end up with a stack overflow hence a SEGFAULT 11. Package
gtk2-2.18.5-3.fc12 added this new function. You can try replacing the package with the version that was replaced gtk2-2-18.4-3. I'm still debugging and post more when I'm finished.

Joko

---------- Post added at 09:29 PM CST ---------- Previous post was at 08:25 PM CST ----------

I replaced my latest libgdk (libgdk-x11-2.0.so.0.1800.5) with the libgdk (libgdklibgdk-x11-2.0.so.0.1800.4) from the previous version of gtk2 package. This fixes the yumex crash but I can't say what it might effect. I'll submit
a bug to bugzilla. If you want to try the fix download the older version of gtk2 package (gtk2-2.18.4-3.fc12)
and extract the libgdk-x11-2.0.so.0.1800.4 file. Change the ending .4 to .5 then go to /usr/lib and rename the
current libgdk (libgdk-x11-2.0.so.0.1800.5) to something else. Then put your older version in it's place (you'll
need to be root to make these changes). This should fix your yumex crash but beware it could effect another
application that uses this library. By the way I'm not running an x86_64. I'm running 32-bit. Your libraries I suppose are in /usr/lib64 but they have the same file names.

Good luck

[cafetono]

I'm having the same problem: /usr/bin/yumex: line 5: 2201 Segmentation fault (core dumped) /usr/bin/python /usr/share/yumex/yumex.pyc $*

[bobwoodbury]

I have the same problem. Yumex crashes after "getting group information". This problem began today when I installed updates using yumex.

I tried the gtk2-2-18.4-3 fix, and that worked, temporarily. Then I installed "VirtualBox". Subsequently, yumex crashed again, same as before. I don't know if the VirtualBox install had anything to do with the recurrence of the problem. Here is the output:

> yumex
running
Current Settings
autorefresh: True
branding_title: 'Yum Extender NextGen'
color_install: 'darkgreen'
color_normal: 'black'
color_obsolete: 'blue'
color_update: 'red'
debug: False
disable_repo_page: False
plugins: True
proxy: ''
recentdays: 14
repo_exclude: ['debug', 'source']
win_height: 966
win_sep: 637
win_width: 1280
yumdebuglevel: 2
/usr/lib/python2.6/site-packages/guihelpers/__init__.py:199: GtkWarning: gtk_scrolled_window_add(): cannot add non scrollable widget use gtk_scrolled_window_add_with_viewport() instead
self.add_from_file(filename)
/usr/lib/python2.6/site-packages/yumexgui/gui.py:179: DeprecationWarning: Use the new widget gtk.Tooltip
self.tooltip = gtk.Tooltips()
/usr/lib/python2.6/site-packages/yumexgui/gui.py:206: DeprecationWarning: Use the new widget gtk.Tooltip
self.tooltip.set_tip(button, tooltip)
Can't detect the network connection state
Starting yum child process
YUM: Loaded plugins: presto
History Enabled
/usr/bin/yumex: line 5: 2111 Segmentation fault (core dumped) /usr/bin/python /usr/share/yumex/yumex.pyc $*


Bob Woodbury

[jtripcevic]

Bob, I installed VirtualBox on my machine and yumex still works without a SEGFAULT. Could you do a stack back trace using GDB? You'll need to install the debug files for the libraries being debugged ( see the man page for debug-install) Onec you've
done that launch the following command: "gdb /usr/bin/python" this will put you in to the debugger. Once you have the (gdb)
prompt enter "run /usr/share/yumex/yumex.pyc". This will start up yumex in the debugger. Once you get the SEGFAULT enter
"bt" in the debugger to get a stack trace (you need to make sure that you have ample scrollback in your terminal window, say
at least 30000 lines). Select all the text and put it in a file and attach it to your post. I'll have a look at it.

[bobwoodbury]

Unfortunately, I've fixed the problem so I don't get the segfault now. I don't know for sure what fixed the problem, but I have a pretty good idea. Here's the sequence of events:

After doing updates (using yumex) and rebooting, yumex crashed with the segfault.

I followed the suggestion in a previous post:
I did a "mv /usr/lib/libgdk-x11-2.0.so.0.1800.5 /usr/lib/libgdk-x11-2.0.so.0.1800.5.sav
I copied libgdk-x11-2.0.so.0.1800.4 from a previous release to /usr/lib/libgdk-x11-2.0.so.0.1800.5

This worked (temporarily) but was a bad act because there are links in /usr/lib to libgdk-x11-2.0.so.0.1800.5 which stayed with the file when I moved it to /usr/lib/libgdk-x11-2.0.so.0.1800.5.sav

So there was an inconsistency in /usr/lib.

When I looked carefully and realized what had happened, I made it consistent again. That is, I got rid of the file from the previous release and restored the one I had saved. Also, I reestablished the link to the file. So now my /usr/lib directory looks like this:

lrwxrwxrwx 1 root root 26 2009-12-18 15:22 libgdk-x11-2.0.so -> libgdk-x11-2.0.so.0.1800.5
-rwxr-xr-x 2 root root 740572 2009-12-19 01:36 libgdk-x11-2.0.so.0
-rwxr-xr-x 2 root root 740572 2009-12-19 01:36 libgdk-x11-2.0.so.0.1800.5

Note that libgdk-x11-2.0.so.0 and libgdk-x11-2.0.so.0.1800.5 are linked.

With this configuration, yumex works fine, though I can't say for sure this is the way it should be.

I suspect that the update that started the problem left some inconsistency in the /usr/lib directory in regards to libgdk-x11-2.0.so, libgdk-x11-2.0.so.0, and libgdk-x11-2.0.so.0.1800.5, and that I just stumbled around until I got it right.

From the posts that are appearing in regards to this problem, I expect there will be someone who can give you a listing of their /usr/lib directory so you can verify if this is the problem.

BTW: My system is 32-bit. I responded to this thread because this is where I saw the problem reported, and it seems people are seeing the problem without regard to 32 vs 64 bit.

Let me know if I can be of help.

Thanks,
Bob Woodbury

[David Batson]

chepioq found the problem and solution. It is the latest gtk2 updates.

See post #11 below.
http://forums.fedoraforum.org/showthread.php?t=236523

[jtripcevic]

I'm quite sure that the update causes the problem as I put a fix in the new code, recompiled a new rpm and installed it. The SEGFAULT did not reappear. Concerning your links, they should have followed the new file as mine did. When you renamed
the old file the two links should have showed up as broken. Then when you put in the new file they should link up to it
automatically. I can't say why yours didn't. In any case if you're happy that it's working now that's the important part. I'm still
going to file a bug report on the update.