[opensuse] Zypper segmentation fault
Greetings to the list This is my first post, so please forgive me for not describing correctly the situation. My home workstation (OpenSuSE 10.3 32bit) has been receiving fairly regularly, albeit manually (every 2-3 days) the official updates, except for the kernel related ones. I admit having several OBS repositories enabled, as well as Packman, Gtk:STABLE and KDE:Backports. I try to be careful about updating major infrastructure, always checking the list of packages to be upgraded or installed, refreshing the repos before any updating takes place, not using any updaterapplet and going mostly through yast2. Yesterday, trying to launch any software management app through yast resulted in the window taken down. Trying the cli greeted me with this: PENTIUM:/var/log # zypper lr Repository 'openSUSE BuildService - Wine CVS Builds' is up to date. Segmentation fault disabling wine repo just confirmed that the next one is ok before spitting out the segfault. Trying through yast again gave this xmessage: YaST got signal 11 at YCP file /usr/share/YaST2/clients/repositories.ycp:761 /sbin/yast2: line 386: 12277 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2QT_ARGS I recall tha a recent wxGTK update wrecked havoc over my gtk2 using apps, but only those alone. Manually donwgrading solved most of the problem, which anyway should be unrelated (?). All this before yesterday. Rebuilding the rpm database did no good. Logfiles do not show anything useful to my (ignorant) eyes. Googling did not help much. I really don't know how to go about troubleshooting zypper, zypplib or whatever is being used. Other components of Yast2 work fine. PENTIUM:/var/log # uname -r 2.6.22.19-0.1-default zypper 0.8.26 RPM version :4.4.2 qt3 version :3.3.8 Any pointers will be welcome. Info upon request. Thanks in advance. -- /"\ \ / ASCII RIBBON CAMPAIGN X AGAINST HTML EMAIL / \ AND POSTINGS -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
??????? ????????? wrote:
Greetings to the list
This is my first post, so please forgive me for not describing correctly the situation. My home workstation (OpenSuSE 10.3 32bit) has been receiving fairly regularly, albeit manually (every 2-3 days) the official updates, except for the kernel related ones. I admit having several OBS repositories enabled, as well as Packman, Gtk:STABLE and KDE:Backports. I try to be careful about updating major infrastructure, always checking the list of packages to be upgraded or installed, refreshing the repos before any updating takes place, not using any updaterapplet and going mostly through yast2. Yesterday, trying to launch any software management app through yast resulted in the window taken down. Trying the cli greeted me with this:
PENTIUM:/var/log # zypper lr Repository 'openSUSE BuildService - Wine CVS Builds' is up to date. Segmentation fault
disabling wine repo just confirmed that the next one is ok before spitting out the segfault. Trying through yast again gave this xmessage:
YaST got signal 11 at YCP file /usr/share/YaST2/clients/repositories.ycp:761 /sbin/yast2: line 386: 12277 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2QT_ARGS
I recall tha a recent wxGTK update wrecked havoc over my gtk2 using apps, but only those alone. Manually donwgrading solved most of the problem, which anyway should be unrelated (?). All this before yesterday. Rebuilding the rpm database did no good. Logfiles do not show anything useful to my (ignorant) eyes. Googling did not help much. I really don't know how to go about troubleshooting zypper, zypplib or whatever is being used. Other components of Yast2 work fine.
PENTIUM:/var/log # uname -r 2.6.22.19-0.1-default
zypper 0.8.26 RPM version :4.4.2 qt3 version :3.3.8
Any pointers will be welcome. Info upon request. Thanks in advance.
I'll bet you have installed a qt or gtk package that is incompatible with Yast. Disable any of the qt and gtk repositories, then you will need to rpm -Uvh --force install the qt and gtk rpms to downgrade to the latest 10.3 versions. Search the mailing list archives for all my posts from Jan. 22 2009 with subject "Yast Seg Faulting on Fresh 11.0 i386 Install" and you will be able to find Anders answer to the problem. -- 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
David C. Rankin pecked at the keyboard and wrote:
Any pointers will be welcome. Info upon request. Thanks in advance.
I'll bet you have installed a qt or gtk package that is incompatible with Yast. Disable any of the qt and gtk repositories, then you will need to rpm -Uvh --force install the qt and gtk rpms to downgrade to the latest 10.3 versions.
Please use --oldpackage instead of --force when downgrading a package. That's what it's there for. You'll have far fewer problems that way. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Ken Schneider - openSUSE wrote:
David C. Rankin pecked at the keyboard and wrote:
Any pointers will be welcome. Info upon request. Thanks in advance.
I'll bet you have installed a qt or gtk package that is incompatible with Yast. Disable any of the qt and gtk repositories, then you will need to rpm -Uvh --force install the qt and gtk rpms to downgrade to the latest 10.3 versions.
Please use --oldpackage instead of --force when downgrading a package. That's what it's there for. You'll have far fewer problems that way.
Oops Sorry, right you are. Old habits...... -- 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 Mon, Mar 23, 2009 at 03:49:40PM -0500, David C. Rankin wrote:
Ken Schneider - openSUSE wrote:
David C. Rankin pecked at the keyboard and wrote:
Disable any of the qt and gtk repositories, then you will need to rpm -Uvh --force install the qt and gtk rpms to downgrade to the latest 10.3 versions.
Thanks for the advice. However, I 'm confused as to how I 'm going to find the gtk related apps to be removed, if my yast interface doesn't come up and zypper segfaults on me. Am I missing something obvious? I know rpm works but don't know which component exactly should be downgraded -- /"\ \ / ASCII RIBBON CAMPAIGN X AGAINST HTML EMAIL / \ AND POSTINGS -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 24 March 2009 03:18:44 am Γαβριήλ Παπαδάκης wrote:
On Mon, Mar 23, 2009 at 03:49:40PM -0500, David C. Rankin wrote:
Ken Schneider - openSUSE wrote:
David C. Rankin pecked at the keyboard and wrote:
Disable any of the qt and gtk repositories, then you will need to rpm -Uvh --force install the qt and gtk rpms to downgrade to the latest 10.3 versions.
Thanks for the advice. However, I 'm confused as to how I 'm going to find the gtk related apps to be removed, if my yast interface doesn't come up and zypper segfaults on me. Am I missing something obvious? I know rpm works but don't know which component exactly should be downgraded
Does console YaST work? -- Regards, Rajko -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2009-03-24 at 10:18 +0200, Γαβριήλ Παπαδάκης wrote:
Ken Schneider - openSUSE wrote:
David C. Rankin pecked at the keyboard and wrote:
Disable any of the qt and gtk repositories, then you will need to rpm -Uvh --force install the qt and gtk rpms to downgrade to the latest 10.3 versions.
Thanks for the advice. However, I 'm confused as to how I 'm going to find the gtk related apps to be removed, if my yast interface doesn't come up and zypper segfaults on me. Am I missing something obvious? I know rpm works but don't know which component exactly should be downgraded
Zypper is not related to gtk nor qt. That will not solve your problem, it is more basic. My guess would be libzypp or something used by it. You will have to use "rpm" to repair your system. My pet command is: rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \ %25{PACKAGER}\n" | sort | cut --fields="2-" | less -S This will show you what you installed recently and change it back (to whatever the oss or update repos have). - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAknI9K8ACgkQtTMYHG2NR9X4mQCfUyIapr4t5VzNmio2lamplG9C 0SYAoInPh5EKZPlc+MMHCJHG6kCwqzTy =vIHP -----END PGP SIGNATURE-----
??????? ????????? wrote:
On Mon, Mar 23, 2009 at 03:49:40PM -0500, David C. Rankin wrote:
Ken Schneider - openSUSE wrote:
David C. Rankin pecked at the keyboard and wrote:
Disable any of the qt and gtk repositories, then you will need to rpm -Uvh --force install the qt and gtk rpms to downgrade to the latest 10.3 versions.
Thanks for the advice. However, I 'm confused as to how I 'm going to find the gtk related apps to be removed, if my yast interface doesn't come up and zypper segfaults on me. Am I missing something obvious? I know rpm works but don't know which component exactly should be downgraded
Identify any qt or gtk repositories you have added, and then just go to http://download.opensuse.org/repositories/(path to your qt or gtk repo) and get the list of files you updated from there. For example, use 'zypper lr -u' to look at the URLs for your repositories, and then go see what files you potentially updated that are causing your problems. For example, go check: http://download.opensuse.org/repositories/KDE:/Qt44/openSUSE_11.0/x86_64 and see what is there. I think I just used: lynx -dump http://download.opensuse.org/repositories/KDE:/Qt44/openSUSE_11.0/x86_64 to get the list of potential files, then I just used a short script to downgrade any files from those repositories. Something like: lynx -dump repourl > filelist while IFS=$'\n' read line; do (parse rpmname from $line) if rpm -q $rpmname; then rpm -Uvh --oldpackage (opensuse oss repo)/$rpmname fi done < filelist I'll see if I kept the file and report back. -- 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
David C. Rankin wrote:
??????? ????????? wrote:
On Mon, Mar 23, 2009 at 03:49:40PM -0500, David C. Rankin wrote:
Ken Schneider - openSUSE wrote:
David C. Rankin pecked at the keyboard and wrote:
Disable any of the qt and gtk repositories, then you will need to rpm -Uvh --force install the qt and gtk rpms to downgrade to the latest 10.3 versions. Thanks for the advice. However, I 'm confused as to how I 'm going to find the gtk related apps to be removed, if my yast interface doesn't come up and zypper segfaults on me. Am I missing something obvious? I know rpm works but don't know which component exactly should be downgraded
Identify any qt or gtk repositories you have added, and then just go to http://download.opensuse.org/repositories/(path to your qt or gtk repo) and get the list of files you updated from there. For example, use 'zypper lr -u' to look at the URLs for your repositories, and then go see what files you potentially updated that are causing your problems. For example, go check:
http://download.opensuse.org/repositories/KDE:/Qt44/openSUSE_11.0/x86_64
and see what is there. I think I just used:
lynx -dump http://download.opensuse.org/repositories/KDE:/Qt44/openSUSE_11.0/x86_64
to get the list of potential files, then I just used a short script to downgrade any files from those repositories. Something like:
lynx -dump repourl > filelist while IFS=$'\n' read line; do (parse rpmname from $line) if rpm -q $rpmname; then rpm -Uvh --oldpackage (opensuse oss repo)/$rpmname fi done < filelist
I'll see if I kept the file and report back.
You are in luck -- I found the scraps. The following will do what you want to downgrade any files from any of the repositories you have disable in attempt to solve your Yast problem: #!/bin/bash showem () { echo -e "\n\tRPMURL = $RPMURL" echo -e "\tRPMFILE = $RPMFILE" echo -e "\tRPMNAME = $RPMNAME" echo -e "\tRPM = $RPM" } # use lynx to get the list, or just save the list to a file and change # the filename at the end of the while loop lynx -dump http://download.opensuse.org/repositories/KDE:/Qt44/openSUSE_11.0/x86_64 > /tmp/qt44list sed -e '/mirrorlist/d' -e '/metalink/d' -e '/\s\[/d' -e 's/^.*http/http/' /tmp/qt44list | grep rpm > /tmp/qt44final while IFS=$'\n' read line; do RPMURL=${line} RPMFILE=${line##*/} RPMNAME=${RPMFILE/%.x86_64.rpm/} RPM=$(echo $RPMNAME | sed -e 's/-[0-9][.][0-9].*$//') # showem # Uncomment to see printout of parameter values if rpm -q $RPMNAME >/dev/null 2>&1; then echo -e "\tDowngrading: $RPMNAME" rpm -Uvh --oldpackage $RPM fi done < /tmp/qt44final exit 0 -- 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 Wednesday, 2009-03-25 at 01:02 -0500, David C. Rankin wrote:
the list of files you updated from there. For example, use 'zypper lr -u' to
Remember that his "zypper" segfaults. He can not use zypper for anything, (nor yast) just raw rpm. ] Subject : Re: [opensuse] Zypper segmentation fault - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAknKKDUACgkQtTMYHG2NR9US0QCdEFiylEvhaqmmudldHXKuZV+t v1wAoIYTpenEJ19AYmnZKNX/cfSIqeGc =eOoQ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
On Wednesday, 2009-03-25 at 01:02 -0500, David C. Rankin wrote:
the list of files you updated from there. For example, use 'zypper lr -u' to
Remember that his "zypper" segfaults. He can not use zypper for anything, (nor yast) just raw rpm.
] Subject : Re: [opensuse] Zypper segmentation fault
-- Cheers, Carlos E. R.
Yes, The script uses rpm. I guess I should have added that if the OP (I'm not going to try to spell the name) can't even use zypper lr to find out what repositories he has, then he will need to just look in /etc/zypp/repos.d to get the URLs for the offending repos, then the script will take care of the rest. Zypper didn't have anything to do with the repair beyond having text config files that will point to the URL of the repository where the conflicting updates came from. Then it just checks whether any of the files in that repo are installed via rpm -q and if so, then downgrades the package to the original ..... crud! I knew I missed something.... This will do it: #!/bin/bash showem () { echo -e "\n\tARCH = $ARCH" echo -e "\tBADREPO = $BADREPO" echo -e "\tOSSREPO = $OSSREPO" echo -e "\tRPMURL = $RPMURL" echo -e "\tRPMFILE = $RPMFILE" echo -e "\tRPMNAME = $RPMNAME" echo -e "\tRPM = $RPM" echo -e "\tOSSURL = $OSSURL\n" } getarch() { case $(arch) in i[3-6]* ) echo i586;; *64 ) echo x86_64;; esac } [[ -z $1 ]] && { echo "\n\tUsage: ${0##*/} URL-2-BadRepository\n"; exit 1; } ARCH=$(getarch) BADREPO=$(echo $1 | sed -e 's/\/$//')/${ARCH} OSSREPO=http://download.opensuse.org/distribution/11.0/repo/oss/suse/${ARCH} # use lynx to get the list, or just save the list to a file and change # the filename at the end of the while loop if [[ ! -r "/tmp/repolist" ]]; then echo -e "Retrieving suspect RPM list from ${BADREPO}\n" if lynx -dump ${BADREPO} > /tmp/repolist; then sed -e '/mirrorlist/d' -e '/metalink/d' -e '/\s\[/d' -e 's/^.*http/http/' /tmp/repolist | grep rpm > /tmp/repofinal else echo -e "\n\tUnable to get RPM list from ${BADREPO}, check your URL\n" exit 1 fi fi if [[ ! -r "/tmp/osslist" ]]; then echo -e "Retrieving OSS RPM list from ${OSSREPO}\n" if lynx -dump ${OSSREPO} > /tmp/osslist; then sed -e '/mirrorlist/d' -e '/metalink/d' -e '/\s\[/d' -e 's/^.*http/http/' /tmp/osslist | grep rpm > /tmp/ossfinal else echo -e "\n\tUnable to get OSS RPM list from ${OSSREPO}\n" exit 1 fi fi while IFS=$'\n' read line; do RPMURL=${line} RPMFILE=${line##*/} RPMNAME=${RPMFILE/%.x86_64.rpm/} RPM=$(echo $RPMNAME | sed -e 's/-[0-9][.][0-9].*$//') showem if rpm -q $RPMNAME >/dev/null 2>&1; then OSSURL=$(grep $RPM /tmp/ossfinal) if [[ -n $OSSURL ]]; then echo -e "\tDowngrading: $RPMNAME to ${OSSURL##*/}" rpm -Uvh --oldpackage ${OSSURL} else echo -e "\tPackage: $RPM, not available in ${OSSREPO}" fi showem fi done < /tmp/repofinal -- 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 Wednesday, 2009-03-25 at 12:11 -0500, David C. Rankin wrote:
Carlos E. R. wrote:
the list of files you updated from there. For example, use 'zypper lr -u' to
Remember that his "zypper" segfaults. He can not use zypper for anything, (nor yast) just raw rpm.
Yes,
The script uses rpm. I guess I should have added that if the OP (I'm not going to try to spell the name) can't even use zypper lr to find out what repositories he has, then he will need to just look in /etc/zypp/repos.d to get the URLs for the offending repos, then the script will take care of the rest.
Zypper didn't have anything to do with the repair beyond having text config files that will point to the URL of the repository where the conflicting updates came from. Then it just checks whether any of the files in that repo are installed via rpm -q and if so, then downgrades the package to the original ..... crud! I knew I missed something.... This will do it:
There is more. Notice that if zypper does not work, the first thing to do is to repair zypper itself, and that is not related to gtk or qt, and the only repos needed are the dvd and the oss repo. I would simply reinstall zypper and its libraries from the dvd. If that does not work, then reinstall everything that was installed recently, which list can be obtained using rpm. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAknKfTgACgkQtTMYHG2NR9U5DgCfUDbKF+N6daZ7av483sqME9j6 nmYAnRruqAVZltlUuAaLVv2ojtb5LcrP =piGE -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
On Wednesday, 2009-03-25 at 12:11 -0500, David C. Rankin wrote:
Carlos E. R. wrote:
the list of files you updated from there. For example, use 'zypper lr -u' to
Remember that his "zypper" segfaults. He can not use zypper for anything, (nor yast) just raw rpm.
Yes,
The script uses rpm. I guess I should have added that if the OP (I'm not going to try to spell the name) can't even use zypper lr to find out what repositories he has, then he will need to just look in /etc/zypp/repos.d to get the URLs for the offending repos, then the script will take care of the rest.
Zypper didn't have anything to do with the repair beyond having text config files that will point to the URL of the repository where the conflicting updates came from. Then it just checks whether any of the files in that repo are installed via rpm -q and if so, then downgrades the package to the original ..... crud! I knew I missed something.... This will do it:
There is more. Notice that if zypper does not work, the first thing to do is to repair zypper itself, and that is not related to gtk or qt, and the only repos needed are the dvd and the oss repo.
I would simply reinstall zypper and its libraries from the dvd.
If that does not work, then reinstall everything that was installed recently, which list can be obtained using rpm.
-- Cheers, Carlos E. R.
What? ... and miss out on a solid hour of scripting?? Never... The approach I took with the script, was designed to target the problem I experienced when I inadvertently installed several qt45 apps that killed Yast deader-than-a-doornail. Not knowing for sure which were the conflicting rpms, disabling the repos that were suspect, identifying the packages that had been installed from the repo, and downgrading to oss solved my problem. I agree that if a reinstall of zypper from the dvd with either --oldpackage or --force, will pull in the and downgrade the required files, then that is certainly the first step, and probably the solution in this case. However, what the script does for the situation that the zypper dvd reinstall doesn't, is to help identify those packages from repo X that had been installed on the system that would provide a good starting point for backing out packages if for some reason the zypper reload didn't work. ...and... having collected the pieces and put them back together, I now have a fairly generic base for repo parsing and comparison against the installed set of packages;-) -- 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 Wednesday, 2009-03-25 at 19:10 -0500, David C. Rankin wrote: ...
What? ... and miss out on a solid hour of scripting?? Never...
X'-)
The approach I took with the script, was designed to target the problem I experienced when I inadvertently installed several qt45 apps that killed Yast deader-than-a-doornail. Not knowing for sure which were the conflicting rpms, disabling the repos that were suspect, identifying the packages that had been installed from the repo, and downgrading to oss solved my problem.
I agree that if a reinstall of zypper from the dvd with either --oldpackage or --force, will pull in the and downgrade the required files, then that is certainly the first step, and probably the solution in this case.
However, what the script does for the situation that the zypper dvd reinstall doesn't, is to help identify those packages from repo X that had been installed on the system that would provide a good starting point for backing out packages if for some reason the zypper reload didn't work.
...and... having collected the pieces and put them back together, I now have a fairly generic base for repo parsing and comparison against the installed set of packages;-)
Interesting... - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAknR/l0ACgkQtTMYHG2NR9V4cwCdHzxeYwl7Vt/MOTHvI06Ez42U 7VAAniWCE+Q12DI8/aU2YlOeXfUhXEex =UT6W -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Γαβριήλ Παπαδάκης wrote:
Greetings to the list
This is my first post, so please forgive me for not describing correctly the situation. My home workstation (OpenSuSE 10.3 32bit) has been receiving fairly regularly, albeit manually (every 2-3 days) the official updates, except for the kernel related ones. I admit having several OBS repositories enabled, as well as Packman, Gtk:STABLE and KDE:Backports. I try to be careful about updating major infrastructure, always checking the list of packages to be upgraded or installed, refreshing the repos before any updating takes place, not using any updaterapplet and going mostly through yast2. Yesterday, trying to launch any software management app through yast resulted in the window taken down. Trying the cli greeted me with this:
PENTIUM:/var/log # zypper lr Repository 'openSUSE BuildService - Wine CVS Builds' is up to date. Segmentation fault
YaST got signal 11 at YCP file /usr/share/YaST2/clients/repositories.ycp:761 /sbin/yast2: line 386: 12277 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2QT_ARGS
Did we release some 10.3 update recently? - -- cheers, jano Ján Kupec YaST team - ---------------------------------------------------------(PGP)--- Key ID: 637EE901 Fingerprint: 93B9 C79B 2D20 51C3 800B E09B 8048 46A6 637E E901 - ---------------------------------------------------------(IRC)--- Server: irc.freenode.net Nick: jniq Channels: #zypp #yast #suse #susecz - ---------------------------------------------------------(EOF)--- -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAknQpukACgkQgEhGpmN+6QHKpQCcDTuaGpk+fr27aM9CbRuF5/+I 6+cAn0l2HWwtPwOuMLfrRiOrwMOmfiha =zy7/ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jan Kupec wrote:
±²Á¹®» ±À±´¬º·Â wrote:
Greetings to the list
This is my first post, so please forgive me for not describing correctly the situation. My home workstation (OpenSuSE 10.3 32bit) has been receiving fairly regularly, albeit manually (every 2-3 days) the official updates, except for the kernel related ones. I admit having several OBS repositories enabled, as well as Packman, Gtk:STABLE and KDE:Backports. I try to be careful about updating major infrastructure, always checking the list of packages to be upgraded or installed, refreshing the repos before any updating takes place, not using any updaterapplet and going mostly through yast2. Yesterday, trying to launch any software management app through yast resulted in the window taken down. Trying the cli greeted me with this:
PENTIUM:/var/log # zypper lr Repository 'openSUSE BuildService - Wine CVS Builds' is up to date. Segmentation fault
YaST got signal 11 at YCP file /usr/share/YaST2/clients/repositories.ycp:761 /sbin/yast2: line 386: 12277 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2QT_ARGS
Did we release some 10.3 update recently?
Sorry, the question should have gone to zypp-devel@opensuse.org. - -- cheers, jano Ján Kupec YaST team - ---------------------------------------------------------(PGP)--- Key ID: 637EE901 Fingerprint: 93B9 C79B 2D20 51C3 800B E09B 8048 46A6 637E E901 - ---------------------------------------------------------(IRC)--- Server: irc.freenode.net Nick: jniq Channels: #zypp #yast #suse #susecz - ---------------------------------------------------------(EOF)--- -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAknQp1sACgkQgEhGpmN+6QER5QCeJ2G+e/fOn8+SjWwjb2IwMDIu zZoAnRIeYg46PptMcXBq5984eqYfSjti =9ets -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (6)
-
Carlos E. R. -
David C. Rankin -
Jan Kupec -
Ken Schneider - openSUSE -
Rajko M. -
Γαβριήλ Παπαδάκης