From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021126 Description of problem: When i click on the up2date icon it does not execute or if i type in the cmd it does not work...when i do a backtrace gdb up2date i get this message: [root@localhost root]# gdb up2date GNU gdb Red Hat Linux (5.2.1-4) Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux"..."/usr/sbin/up2date": not in executable format: File format not recognized Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.click up2date icon/or type cmd up2date 2. 3. Additional info: this is the second time this has happened. i would have to reinstall up2date.
The error you are receiving is because gdb attempts to grab information from the object code of a binary file. "up2date" is not a binary application - it is actually a Python script: $ file /usr/sbin/up2date /usr/sbin/up2date: a /usr/bin/python -u script text executable Instead you could provide the strace output of the execution: # strace /usr/sbin/up2date 2> output_up2date.stderr Attach output_up2date.stderr to this bug.
How does up2date fail if ran from the command line? Do you get error messages? if so, what are they?
Created attachment 89945 [details] up2date stderr
apparently all you need to do is rm -f /var/lib/rpm__db*...conflict w/ the rpm bug...closed
check that....its rm -f /var/lib/rpm/__db*