[opensuse] /sbin/yast2: line 421: 17466 Segmentation fault $ybindir/y2base $module after updates?
Guys, I need your help to identify the possible package that is now causing yast to segfault after yesterday's updates. Generally when yast has gone crazy in the past, it is a Qt version, but looking at the list, I can't find a package that fits the crime. The following are the packages installed yesterday: bespin-icons ctunnel dvgrab ecomorph ecomp edvi elementary-alarm enterminus expedite exquisite freetype2-32bit gftp gftp-common gftp-common-lang gftp-text gpg-pubkey gtk-engines john kde4-style-bespin kdevelop4 kdevelop4-lang kdevelop4-plugins-php kdevelop4-plugins-php-doc kdevplatform kdevplatform-lang libavc1394-0 libdvbpsi5 libiec61883 libkdevplatform0 libquazip1 libupnp3 libvlc5 libvlccore4 libxmmsclient-glib1 libxmmsclient6 lxlauncher mp4v2 pcre-doc pcre-tools showcase vlc vlc-devel vlc-gnome vlc-noX vlc-qt xmms2 xmms2-devel xmms2-docs xmms2-perl xmms2-plugin-base xmms2-ruby The only new packages were the vlc player from videolan. Now I can start yast, but when I tell it to select repositories, or just in resolving dependencies, it segfaults with the following: 15:54 alchemy:/home/david # YaST got signal 11 at YCP file /usr/share/YaST2/clients/inst_packages.ycp:49 /sbin/yast2: line 421: 17466 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS [1]+ Exit 139 yast2 sw_single What looks suspicious? This is on 11.0. Could the vlc package be the culprit? It doesn't sound right, but I'll try removing it. In the mean time, if something else stands out in the list above, please let me know. Thanks! -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 06/06/2010 04:15 PM, David C. Rankin wrote:
Guys,
I need your help to identify the possible package that is now causing yast to segfault after yesterday's updates. Generally when yast has gone crazy in the past, it is a Qt version, but looking at the list, I can't find a package that fits the crime. The following are the packages installed yesterday:
<snip> FYI, I removed the following: 16:17 alchemy:/home/david # rpm -e kdevelop4 kdevelop4-lang kdevelop4-plugins-php kdevelop4-plugins-php-doc kdevplatform kdevplatform-lang vlc vlc-devel vlc-gnome vlc-noX vlc-qt libkdevplatform0 still segfaulting. So those packages were not the issue :-(
What looks suspicious? This is on 11.0. Could the vlc package be the culprit? It doesn't sound right, but I'll try removing it. In the mean time, if something else stands out in the list above, please let me know. Thanks!
-- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2010-06-06 at 16:15 -0500, David C. Rankin wrote:
Guys,
I need your help to identify the possible package that is now causing yast to segfault after yesterday's updates. Generally when yast has gone crazy in the past, it is a Qt version, but looking at the list, I can't find a package that fits the crime. The following are the packages installed yesterday:
Did you reboot? Otherwise, being 11.0, run this in a script: #!/bin/bash set -o nounset # Check there are no processes using software that has been updated by rpm. # Date: Tue, 10 Jan 2006 10:14:59 +0000 (GMT) # From: Bob Vickers <> # Reply-To: suse-security@suse.com # Subject: Re: [suse-security] Patch Noifications # Run lsof and scan the output for libraries that have been updated. Before # SuSE 9.1 these will include the string RPMDELETE, but in 9.1 they include # a semi-colon. # In 9.2 and 9.3 they include the string 'path inode=' #procs=`lsof | grep -E 'RPMDELETE|;|path inode=' | head -$lines` procs=`lsof -n | grep -E 'RPMDELETE|;|path inode=' ` if [ -n "$procs" ] then host=`hostname` cat <<EOF Host $host has obsolete files still in use by running processes. This may constitute a security hazard so you should restart daemons where necessary. COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME EOF echo "$procs" exit 1 else exit 0 fi Running that after an update prints the list of libraries that are still running the old version. You have to restart the appropiate daemons or programs. (when running 11.2 you can use "zypper ps" to get a similar output). Perhaps you have such libraries still loaded if you did not reboot. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkwMJ0QACgkQtTMYHG2NR9Wm+ACfWtkcJZ2HEgTKe6GQsJ9bR9Bl umkAn24uKMSE1LR0ftu2aE0apizCvwrw =6bW7 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 06/06/2010 05:54 PM, Carlos E. R. wrote:
Did you reboot?
Err, um... No? Reboot? Damn -- it worked! Feels familiar for some reason.... Ah, it must just be lack of sleep :p Thanks Carlos. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2010-06-07 at 02:07 -0500, David C. Rankin wrote:
On 06/06/2010 05:54 PM, Carlos E. R. wrote:
Did you reboot?
Err, um... No? Reboot?
Damn -- it worked! Feels familiar for some reason.... Ah, it must just be lack of sleep :p
Thanks Carlos.
Welcome! As to the reason, you/we might have known if you had run that script I posted. The thing is, in Linux, when you erase a file that is in use (opened) the filesystem doesn't actually deletes the file. The directory entry disapears, but not the inode and the data. The program that has that file opened still uses the old (deleted!) version. The moment the deleted file is closed, it does in fact get erased, the inode is cleared. A new run of the prgram gets the new file now. Thus, when you do rpm updates, the daemons that were not restarted, the programs not restarted, keep using the old versions of the libraries - whereas you may have other programs running the new version --> conflicts, bugs, weirdos, etc. So, the script (or the line "lsof -n | grep -E 'RPMDELETE|;|path inode='") detects those files, and you can manually restart those programs. Or, "simply" reboot ;-) The situation is easier on 11.2 and later, because running "zypper ps" does that kind of detection, except that it detects all deleted files, not only those updated by rpm. Unfortunately, the script does no longer work, there is no detectable string I know about. (The script is not mine. I simply modified the one that was posted on the security list time ago). - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkwOodYACgkQtTMYHG2NR9V28QCdG5ijB17KSDf2h9I5kJYcnqWl AWAAn3neABcyzoWnL+fs5NwD9RbHXADR =SCRl -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 06/08/2010 03:02 PM, Carlos E. R. wrote:
So, the script (or the line "lsof -n | grep -E 'RPMDELETE|;|path inode='") detects those files, and you can manually restart those programs. Or, "simply" reboot ;-)
So, if I run the script and get hundreds of lines like this: <snip> kate 11667 david mem REG 8,6 515830 /opt/kde3/lib64/libkresources.so.1.2.0 (path inode=515007) kate 11667 david mem REG 8,6 515852 /opt/kde3/lib64/libvcard.so.0.0.0 (path inode=515030) kate 11667 david mem REG 8,6 515773 /opt/kde3/lib64/libkabc.so.1.2.0 (path inode=514899) kate 11667 david mem REG 8,6 515599 /opt/kde3/lib64/libkutils.so.1.2.0 (path inode=515022) kate 11667 david mem REG 8,6 515842 /opt/kde3/lib64/libktexteditor.so.0.0.0 (path inode=515017) kate 11667 david DEL REG 8,6 515780 /opt/kde3/lib64/libkatepartinterfaces.so.0.0.0;4c10e98c kate 11667 david mem REG 8,6 515876 /opt/kde3/lib64/libkateinterfaces.so.0.0.0 (path inode=515534) kate 11667 david mem REG 8,6 511971 /opt/kde3/lib64/libkdeinit_kate.so (path inode=515538) kate 11667 david mem REG 8,6 514591 /opt/kde3/lib64/kde3/kate.so (path inode=510341) kate 11667 david mem REG 8,6 512839 /opt/kde3/lib64/libkonq.so.4.2.0 (path inode=512838) kate 11667 david mem REG 8,6 515643 /opt/kde3/lib64/libkdefx.so.4.2.0 (path inode=514237) kate 11667 david mem REG 8,6 515846 /opt/kde3/lib64/libkwalletclient.so.1.0.1 (path inode=515026) kate 11667 david mem REG 8,6 515805 /opt/kde3/lib64/libkdesu.so.4.2.0 (path inode=514944) kate 11667 david mem REG 8,6 515435 /opt/kde3/lib64/libDCOP.so.4.2.0 (path inode=514894) kate 11667 david mem REG 8,6 515807 /opt/kde3/lib64/libkdeui.so.4.2.0 (path inode=514947) kate 11667 david mem REG 8,6 515781 /opt/kde3/lib64/libkdecore.so.4.2.0 (path inode=510401) kate 11667 david mem REG 8,6 515816 /opt/kde3/lib64/libkio.so.4.2.0 (path inode=514955) kate 11667 david mem REG 8,6 515583 /opt/kde3/lib64/libkparts.so.2.1.0 (path inode=514977) kio_file 11832 david mem REG 8,6 510325 /opt/kde3/lib64/kde3/kio_file.so (path inode=510324) <big snip> I should probably just go ahead and reboot? :p Thanks Carlos. I can't believe in the thousands of updates I've done, I never really understood this. I had always seen: "This is Linux!, as long as you don't update the kernel, then there is no reason to reboot!" Man, was that information way off the mark. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 10 June 2010 18:44:01 David C. Rankin wrote:
Thanks Carlos. I can't believe in the thousands of updates I've done, I never really understood this. I had always seen: "This is Linux!, as long as you don't update the kernel, then there is no reason to reboot!" Man, was that information way off the mark.
You don't have to reboot. You do have to restart any program you've updated, or any program that uses a library you've updated. In unix since time immemorial, open files are not deleted until they are closed. In this case, it all seems to be kde related, so it should be enough to log out and back in Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2010-06-10 19:50, Anders Johansson wrote:
On Thursday 10 June 2010 18:44:01 David C. Rankin wrote:
Thanks Carlos. I can't believe in the thousands of updates I've done, I never really understood this. I had always seen: "This is Linux!, as long as you don't update the kernel, then there is no reason to reboot!" Man, was that information way off the mark.
There is no need to reboot, but it's easier to tell somebody to reboot instead of telling "run this and that, restart such and such, if you see this do that..." - Hey! After all the explaining I did to you (David), you did not understand, so... yes, please, reboot >:-P
You don't have to reboot. You do have to restart any program you've updated, or any program that uses a library you've updated.
Exactly. It can not be automated.
In unix since time immemorial, open files are not deleted until they are closed.
In this case, it all seems to be kde related, so it should be enough to log out and back in
Yep. - -- Cheers / Saludos, Carlos E. R. (from 11.2 x86_64 "Emerald" GM (Elessar)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAkwRRu8ACgkQU92UU+smfQWFpwCfVhDkg+zqbcFkIyQTayEP13Bi ZUsAmwXithJlTFWKjeBpLg6NogSU4NH5 =DJSg -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, 06 Jun 2010 16:15:02 -0500 "David C. Rankin" <drankinatty@suddenlinkmail.com> wrote:
Guys,
I need your help to identify the possible package that is now causing yast to segfault after yesterday's updates. Generally when yast has gone crazy in the past, it is a Qt version, but looking at the list, I can't find a package that fits the crime. The following are the packages installed yesterday: Hi Have a read of this thread, post #25 and #26 http://forums.opensuse.org/get-help-here/applications/438620-zypper-yast-cor...
-- Cheers Malcolm °¿° (Linux Counter #276890) SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 2.6.32.12-0.7-default up 20:01, 2 users, load average: 0.16, 0.19, 0.19 GPU GeForce 8600 GTS Silent - CUDA Driver Version: 195.36.15 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
Anders Johansson -
Carlos E. R. -
David C. Rankin -
Malcolm