Hi. I would update my SuSE 10.0 yesterday with Yast. It seemed to work ok. I have modified Yast per the instruction "Update all package versions on your suse linux 10.0 machine" found on the Novell site. It has worked fine, and for instance it has updated my KDE excellent. After the updae yesterday I was told to reboot, due to get the new kernel effective. I did it, and then the problem occurred. I cannot remember quite ok, what happened, but I decided to boot with my DVD, to be able to repair the installation. Now it can boot ok again. But it starts up as its in runlevel runlevel 3 -not the X-. Running Yast I can see, that the runlevel is set to 5. I'm sure the problem is to be found in the X. Then I tried a startx from both root and user. Here's the report from the usertry: xauth: error while loading shared libraries: libXext.so.6: cannot open shared object file: No such file or directory xauth: error while loading shared libraries: libXext.so.6: cannot open shared object file: No such file or directory xauth: error while loading shared libraries: libXext.so.6: cannot open shared object file: No such file or directory xauth: error while loading shared libraries: libXext.so.6: cannot open shared object file: No such file or directory xauth: error while loading shared libraries: libXext.so.6: cannot open shared object file: No such file or directory X Window System Version 6.8.2 Release Date: 9 February 2005 X Protocol Version 11, Revision 0, Release 6.8.2 Build Operating System: SuSE Linux [ELF] SuSE Current Operating System: Linux lajka3 2.6.13-15-default #1 Tue Sep 13 14:56:15 UTC 2005 i686 Build Date: 12 September 2005 Before reporting problems, check http://wiki.X.Org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Sun Feb 5 06:55:33 2006 (==) Using config file: "/etc/X11/xorg.conf" (EE) R128(0): No DFP detected /usr/X11R6/lib/X11/xkb/xkbcomp: error while loading shared libraries: libxkbfile.so.1: cannot open shared object file: No such file or directory (EE) Couldn't load XKB keymap, falling back to pre-XKB keymap Could not init font path element /usr/X11R6/lib/X11/fonts/local, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/CID, removing from list! /etc/X11/xim: Checking wether an input method should be started. INPUT_METHOD is not set or empty (no user selected input method). Trying to start a default input method for the locale en_US.UTF-8 ... There is no default input method for the current locale. /usr/X11R6/bin/numlock: error while loading shared libraries: libXext.so.6: cannot open shared object file: No such file or directory kdostartupconfig: error while loading shared libraries: libXi.so.6: cannot open shared object file: No such file or directory xmessage: error while loading shared libraries: libXmu.so.6: cannot open shared object file: No such file or directory /opt/kde3/bin/ksplashx: error while loading shared libraries: libXext.so.6: cannot open shared object file: No such file or directory kde-config: error while loading shared libraries: libXi.so.6: cannot open shared object file: No such file or directory xset: error while loading shared libraries: libXxf86misc.so.1: cannot open shared object file: No such file or directory xset: error while loading shared libraries: libXxf86misc.so.1: cannot open shared object file: No such file or directory startkde: Starting up... kdeinit: error while loading shared libraries: libXi.so.6: cannot open shared object file: No such file or directory startkde: Could not start kdeinit. Check your installation. xmessage: error while loading shared libraries: libXmu.so.6: cannot open shared object file: No such file or directory Warning: connect() failed: : No such file or directory ksmserver: error while loading shared libraries: libXi.so.6: cannot open shared object file: No such file or directory dcop: error while loading shared libraries: libXi.so.6: cannot open shared object file: No such file or directory startkde: Shutting down... Warning: connect() failed: : No such file or directory Error: Can't contact kdeinit! unix_connect: can't connect to server (unix:/tmp/ksocket-erikja/lajka.urbakken.dk-18c2-43c530c4) startkde: Running shutdown scripts... startkde: Done. waiting for X server to shut down xauth: error while loading shared libraries: libXext.so.6: cannot open shared object file: No such file or directory Can I reinstall X, or are there other things that's better ?. Erik Jakobsen
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2006-02-05 at 07:15 +0100, Erik Jakobsen wrote:
xauth: error while loading shared libraries: libXext.so.6: cannot open shared object file: No such file or directory
That library should come from "xorg-x11-libs...rpm". You could reinstall that. Remember you can use Yast in text mode.
(EE) R128(0): No DFP detected /usr/X11R6/lib/X11/xkb/xkbcomp: error while loading shared libraries: libxkbfile.so.1: cannot open shared object file: No such file or directory
same rpm as above. If you see more errors due to missing libraries of files, you can find them out with "pin". - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFD5epltTMYHG2NR9URAovTAJ427dbGlI99ZwXK+4dAjh2hVilR1QCeKKyH Uskai9VVBbHxHc1o7zjADac= =/CYC -----END PGP SIGNATURE-----
Carlos E. R. wrote: Hello Carlos, and thanks for the reply.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Sunday 2006-02-05 at 07:15 +0100, Erik Jakobsen wrote:
xauth: error while loading shared libraries: libXext.so.6: cannot open shared object file: No such file or directory
That library should come from "xorg-x11-libs...rpm". You could reinstall that. Remember you can use Yast in text mode.
Ok about the library and the Yast. I have just ran the Yast again, but of course it was the same, as I haven't changed anything. It was running with Yast in textmode. Can you please tell me what to do ?.
(EE) R128(0): No DFP detected /usr/X11R6/lib/X11/xkb/xkbcomp: error while loading shared libraries: libxkbfile.so.1: cannot open shared object file: No such file or directory
same rpm as above.
Ok fine.
If you see more errors due to missing libraries of files, you can find them out with "pin".
That indeed was a fine tool you told me about there, thanks!.
- -- Cheers, Carlos Robinson
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76
iD8DBQFD5epltTMYHG2NR9URAovTAJ427dbGlI99ZwXK+4dAjh2hVilR1QCeKKyH Uskai9VVBbHxHc1o7zjADac= =/CYC -----END PGP SIGNATURE-----
Erik
xauth: error while loading shared libraries: libXext.so.6: cannot open shared object file: No such file or directory
That library should come from "xorg-x11-libs...rpm". You could reinstall that. Remember you can use Yast in text mode.
Ok about the library and the Yast. I have just ran the Yast again, but of course it was the same, as I haven't changed anything.
It was running with Yast in textmode.
Can you please tell me what to do ?.
Hi Carlos. I can see, that I have installed xorg-x11-libs-6.8.2-100.i586.rpm Maybe its a too new or too old version ?. /Erik
On Sunday 05 February 2006 09:48, Erik Jakobsen wrote:
Can you please tell me what to do ?. ... Maybe its a too new or too old version ?.
YOU will not be covered here. I would like to outline how to make sure,
Hi Erik, I found the post you were referring to here: http://www.novell.com/coolsolutions/feature/16592.html Excerpt: through YAST, that you have all packages on your system updated to the latest possible version. It's actually quite simple.
It's worth a note, however, to mention that because a lot of these packages
are bleeding edge, slight system instability may occur from performing the updates listed here. It isn't the process, itself, that is risky, Eric... it is all those "bleeding edge" sources the article provided. It would have been much better had Novell/SUSE insisted on a much larger and direct *warning.* The following feedback posted on that page says it all:
This is very interesting, but hardly something that should go into "newbies," unless one enjoys the thought of newbies trashing their systems. Just to see what would happen, I tried this in the lab. The desktop became unuseable, forcing a reimage on the test machine.
As far as repairs go, it isn't like you have a bunch of dependency problems to solve... at least that rpm knows about... you have problematic software installed. I wouldn't know where to start telling you how to reverse all the changes. It's possible, but a chore. You might want to think about wiping the drive, reinstalling and chalking it up to experience... it could be faster. Maybe someone else will have a more optimistic opinion? Good luck & regards, - Carl
On Sunday 05 February 2006 10:17, Carl Hartung wrote:
... Maybe someone else will have a more optimistic opinion?
Addendum: Erik, It just occurred to me that you might be able to restore your system by using the "Repair Installed System" option after booting the installer from your CD/DVD. Or, another alternative: - Boot to run level 3, log in as root, run "yast" in ncurses (text) mode. - Remove the installation sources that you added following the article. - Refresh the installation sources again. - Open the 'Software Management' module. This is where it becomes a chore, since you're in text mode: - Explore the menus using Tab and Shift+Tab (forward and back) - Highlight "Filters", use your down arrow to highlight "Installed Packages" - PgDn and PgUp scrolls you through the list of installed packages. - Find each package where the installed version is *newer* than the one that is available from your original sources, highlight "Actions", arrow down to "Update" and hit "Enter" to select the package for "updating." (In this case, it really means "reinstall the previous version") - Once you are satisfied that all the "bleeding edge" packages have been selected for replacement with earlier versions, Tab to "Accept" and hit Enter. I can't guarantee this will fix every problem, but there's a good chance it will get the system back to a more usable condition so you can iron out the remaining problems from your desktop. Good luck! - Carl
Carl Hartung wrote:
On Sunday 05 February 2006 10:17, Carl Hartung wrote:
... Maybe someone else will have a more optimistic opinion?
Addendum:
Erik,
It just occurred to me that you might be able to restore your system by using the "Repair Installed System" option after booting the installer from your CD/DVD. Or, another alternative:
This is what I did today, but I maybe have overseen something.
- Boot to run level 3, log in as root, run "yast" in ncurses (text) mode. - Remove the installation sources that you added following the article.
Where in the article is that described ?.
- Refresh the installation sources again. - Open the 'Software Management' module.
Ok.
This is where it becomes a chore, since you're in text mode:
Defenitely you are right.
- Explore the menus using Tab and Shift+Tab (forward and back)
- Highlight "Filters", use your down arrow to highlight "Installed Packages"
- PgDn and PgUp scrolls you through the list of installed packages.
- Find each package where the installed version is *newer* than the one that is available from your original sources, highlight "Actions", arrow down to "Update" and hit "Enter" to select the package for "updating." (In this case, it really means "reinstall the previous version")
- Once you are satisfied that all the "bleeding edge" packages have been selected for replacement with earlier versions, Tab to "Accept" and hit Enter.
I can't guarantee this will fix every problem, but there's a good chance it will get the system back to a more usable condition so you can iron out the remaining problems from your desktop.
This indeed is a job to do, but I can follow your advice clearly. Thank you.
Good luck!
- Carl
Erik
On Sunday 05 February 2006 14:28, Erik Jakobsen wrote:
On Sunday 05 February 2006 10:17, Carl Hartung wrote: - Remove the installation sources that you added following the article.
Where in the article is that described ?.
What I've said is to remove the extra installation sources that you added when you followed the article. Revert back to the installation sources you had *before* you read the article. - Carl
Carl Hartung wrote:
On Sunday 05 February 2006 14:28, Erik Jakobsen wrote:
On Sunday 05 February 2006 10:17, Carl Hartung wrote: - Remove the installation sources that you added following the article.
Where in the article is that described ?.
What I've said is to remove the extra installation sources that you added when you followed the article. Revert back to the installation sources you had *before* you read the article.
- Carl
Ok Carl, but how can I determine what is new, and what is old ? Erik
Carl, On Sunday 05 February 2006 07:17, Carl Hartung wrote:
...
Hi Erik,
I found the post you were referring to here:
That's a good page. I haven't seen it before, but I follow that basic procedure regularly (I like to live dangerously). One thing I'd add to it is that after the "Update if newer version available" step, click on the header for the package status column (the left-most one that displays the icon showing the packages' status: padlock, blue or black check-box, white-on-green lightening bolt, trashcan, etc.). This will sort the package listing according to status and then you can see all the packages that will be updated or installed together. Locked packages will be at the top. Just scroll down until you see the first lightening bolt or blue check-box to see the packages that will be updated or installed. Randall Schulz
Randall R Schulz wrote:
Carl,
On Sunday 05 February 2006 07:17, Carl Hartung wrote:
...
Hi Erik,
I found the post you were referring to here:
That's a good page. I haven't seen it before, but I follow that basic procedure regularly (I like to live dangerously).
Hi Randall. Please tell me what is dangerous, and then I maybe can get rid of this sort of problems in the future.
One thing I'd add to it is that after the "Update if newer version available" step, click on the header for the package status column (the left-most one that displays the icon showing the packages' status: padlock, blue or black check-box, white-on-green lightening bolt, trashcan, etc.). This will sort the package listing according to status and then you can see all the packages that will be updated or installed together. Locked packages will be at the top. Just scroll down until you see the first lightening bolt or blue check-box to see the packages that will be updated or installed.
I maybe have overseen some important thing here. I only clicked on the zzz All, and followed the Package Summary on the right side and down, until I have marked all the red and blue ones for updating. Is that wrong. I have done it in this way, that I have clicked on either the red or blue ones until the white-on-green lightening bolt was visible. In what you have written above, do you mean the following from top to bottom ?: Install Do Not Install Keep Delete Update if newer version available Update unconditional Taboo-Never Install Protected - Do Not Modify That means, that you have opened "All in This List" at first ?. I can see, that there is 2 white-on-green's, and that could have been my problem, if I have choosen the "Unconditional" ?
Randall Schulz
/Erik Jakobsen.
Carl Hartung wrote:
On Sunday 05 February 2006 09:48, Erik Jakobsen wrote:
Can you please tell me what to do ?.
...
Maybe its a too new or too old version ?.
Hi Erik,
I found the post you were referring to here:
Good Carl
Excerpt:
YOU will not be covered here. I would like to outline how to make sure,
possible version. It's actually quite simple.
.
It's worth a note, however, to mention that because a lot of these packages
are bleeding edge, slight system instability may occur from performing the updates listed here.
It isn't the process, itself, that is risky, Eric... it is all those "bleeding edge" sources the article provided. It would have been much better had Novell/SUSE insisted on a much larger and direct *warning.*
Carl! Could you please tell me that in details, what you really mean here ?.
The following feedback posted on that page says it all:
This is very interesting, but hardly something that should go into
"newbies," unless one enjoys the thought of newbies trashing their systems. Just to see what would happen, I tried this in the lab. The desktop became unuseable, forcing a reimage on the test machine.
As far as repairs go, it isn't like you have a bunch of dependency problems to solve... at least that rpm knows about... you have problematic software installed. I wouldn't know where to start telling you how to reverse all the changes. It's possible, but a chore. You might want to think about wiping the drive, reinstalling and chalking it up to experience... it could be faster. Maybe someone else will have a more optimistic opinion?
Well I am bored with this article. It twice has given me the same problems. But I thought I have seen the light with this article, as its first main reason for me was to could be able to update KDE, and it was well done in the first over, but the benefit dissappeared in the second try, as then there were no X . Then I have to try to find a new way to be able to update KDE, and also all the other packages.
Good luck & regards,
- Carl
Thanks for the message Carl and for the good wishes. Erik
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2006-02-05 at 15:10 +0100, Erik Jakobsen wrote:
That library should come from "xorg-x11-libs...rpm". You could reinstall that. Remember you can use Yast in text mode.
Ok about the library and the Yast. I have just ran the Yast again, but of course it was the same, as I haven't changed anything.
I'm assuming that you are only using official packages from the dvd and official SuSE updates with YOU (Yast Online Update). If you are using packages from some repository, specially bleeding edge ones, I can not help. Please specify what exactly and from where you have installed, and somebody else might help. Even SuSE provided kde upgrades (not YOU updates), are somewhat experimental and supportless. Thus, provided you are using the official, original, rpms, just tell Yast to reinstall that "xorg-x11-libs...rpm", again, regardless of it being already installed. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD4DBQFD5iI/tTMYHG2NR9URAotOAJ0WSJ3HM6x9OaAFuQUxRXb+wOtaXQCUDVYH JE1CK5MVtXpFWSkdV7shyA== =kaR1 -----END PGP SIGNATURE-----
Carlos E. R. wrote:
I'm assuming that you are only using official packages from the dvd and official SuSE updates with YOU (Yast Online Update). If you are using packages from some repository, specially bleeding edge ones, I can not help. Please specify what exactly and from where you have installed, and somebody else might help.
Well to that I'll say, that I use the information mentioned on this URL: http://www.novell.com/coolsolutions/feature/16592.html What say to that with reference to what you have written above ?.
Even SuSE provided kde upgrades (not YOU updates), are somewhat experimental and supportless.
That's a pity.
Thus, provided you are using the official, original, rpms, just tell Yast to reinstall that "xorg-x11-libs...rpm", again, regardless of it being already installed.
Would be nice if you would give me advice on how to do it. I have thought in the same direction, but doesn't know exactly how, and another case is that it will be a huge job, as I have updated all possible packages marked red or blue as shown in the article above. I will say, that this is the second time I encounter this behaviour. First time I gave up repair the installed 10.0. At first it worked splendid, but when I look through the Yast->Software management->Package Group->zzz-All the second time, and mark the red and blue packages it runs wrong, due to a reason I don't know. Thought it was nice having found the pahe mentioned above, but it may be wrong, and there may be something, that I don't understand ?. /Erik
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2006-02-05 at 19:54 +0100, Erik Jakobsen wrote:
Well to that I'll say, that I use the information mentioned on this URL:
http://www.novell.com/coolsolutions/feature/16592.html
What say to that with reference to what you have written above ?.
I don't know, because I haven't looked at it; and I'm not going to, because in order to do so I'd have to connect and pay the phone call. Not everybody has broadband nor cheap phone. But from the comments of other people here, I can guess what it says.
Even SuSE provided kde upgrades (not YOU updates), are somewhat experimental and supportless.
That's a pity.
It is their stated policy.
Thus, provided you are using the official, original, rpms, just tell Yast to reinstall that "xorg-x11-libs...rpm", again, regardless of it being already installed.
Would be nice if you would give me advice on how to do it. I have thought in the same direction, but doesn't know exactly how, and another case is that it will be a huge job, as I have updated all possible packages marked red or blue as shown in the article above.
Then, you need the advice of somebody that has gone the same route as you. For myself, first I would go to the same repository to check if they have a matching "xorg-x11-libs...rpm", or a list of known problems. That failing, I would undo the upgrade; I would get a list of every modified rpm and reinstall them from the dvd. For example, I'd use: rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} %{BUILDTIME:day} %-30{NAME}\t%{VERSION} %{RELEASE} %35{PACKAGER}\n" | sort | less -S which produces an rpm list ordered by install date with some data fields; the last one identifies the packager, which could help you identify them. (use "rpm --querytags | less" to get the list of available fields) Or you could use: rpm -q -a --last |less which produces roughly the same list, ordered last installed first. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFD5l4ptTMYHG2NR9URAuyXAJ4k7+etjCMlka7y/PXR46X/KRRrxACfUUgu d3672QtJxKv1evEIgQwqBO8= =gLxM -----END PGP SIGNATURE-----
On Sunday 05 February 2006 15:20, Carlos E. R. wrote:
Then, you need the advice of somebody that has gone the same route as you.
I've done what I advised Erik to do (YaST ncurses in run level 3) to downgrade from a system-wide update that broke my desktop... it's a chore but it has a good chance of getting him back to his desktop.
For example, I'd use:
rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} %{BUILDTIME:day} %-30{NAME}\t%{VERSION} %{RELEASE} %35{PACKAGER}\n" | sort | less -S
which produces an rpm list ordered by install date with some data fields; the last one identifies the packager, which could help you identify them.
The next thing needed, of course is a script :-) to pump that data into rpm to effect the necessary changes. It would sure beat "hunting and pecking" through ncurses YaST and marking each individual package. You could write something like that, couldn't you Carlos? (nudge nudge) :-) Carl
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2006-02-05 at 15:59 -0500, Carl Hartung wrote:
I've done what I advised Erik to do (YaST ncurses in run level 3) to downgrade from a system-wide update that broke my desktop... it's a chore but it has a good chance of getting him back to his desktop.
Yes, that would work. A real chore, with so many packages... {shudder}
For example, I'd use:
rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} %{BUILDTIME:day} %-30{NAME}\t%{VERSION} %{RELEASE} %35{PACKAGER}\n" | sort | less -S
which produces an rpm list ordered by install date with some data fields; the last one identifies the packager, which could help you identify them.
The next thing needed, of course is a script :-) to pump that data into rpm to effect the necessary changes. It would sure beat "hunting and pecking" through ncurses YaST and marking each individual package.
¡Armor on!
You could write something like that, couldn't you Carlos? (nudge nudge)
Too late, I didn't feel the nudge :-P It is not so complicated to do by hand. Any of the two commands above would produce the list; it is just a question of using an editor and leaving only the needed packages, and then feeding that list to rpm: cd /media/dvd/...... rpm --test --install ---force rpm1 rpm2 rpm3 rpm4..... if it works, then repeat without "test". Notice that you can copy and paste in text mode, provided you first do "rcgpm start" to load the text mode mouse driver. Otherwise, it is simple enough to convert the edited list into a one line script. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFD5o6stTMYHG2NR9URAtIPAKCWNKaOzU3HvZUgAJe9JcKzHqetyACfWxDz 8gZ7R1iBfrrxX5bqZd08NkQ= =7HJ6 -----END PGP SIGNATURE-----
On Sunday 05 February 2006 18:47, Carlos E. R. wrote:
¡Armor on!
lol!
It is not so complicated to do by hand. Any of the two commands above would produce the list; it is just a question of using an editor and leaving only the needed packages, and then feeding that list to rpm:
Easily done by the vi-impaired with mc. Cool! (I *can* use vi in a pinch, but... well... why? Especially when there's an alternative? {rhetorical; not flame bait!})
cd /media/dvd/...... rpm --test --install ---force rpm1 rpm2 rpm3 rpm4.....
if it works, then repeat without "test".
This is a new invocation of CLI rpm for me. Thanks!
Notice that you can copy and paste in text mode, provided you first do "rcgpm start" to load the text mode mouse driver.
*This* little tidbit is also new to me. *Two* gold stars! Thanks again! (I wonder how Erik is progressing?) Carl
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2006-02-05 at 20:14 -0500, Carl Hartung wrote:
It is not so complicated to do by hand. Any of the two commands above would produce the list; it is just a question of using an editor and leaving only the needed packages, and then feeding that list to rpm:
Easily done by the vi-impaired with mc. Cool! (I *can* use vi in a pinch, but... well... why? Especially when there's an alternative? {rhetorical; not flame bait!})
Me too X'-) Just as a reminder: the editor "joe" is now present in the SuSE rescue system. And vi too, of course ;-)
Notice that you can copy and paste in text mode, provided you first do "rcgpm start" to load the text mode mouse driver.
*This* little tidbit is also new to me. *Two* gold stars! Thanks again!
Welcome! I used text mode for a month or two before I got X mode to work properly, back in SuSE 5.2 or something. Sax wasn't available or wasn't much good, and I hadn't discovered this list (did not even have internet, probably). So, I used those tricks - and many people from that time, I guess.
(I wonder how Erik is progressing?)
Not too well, I'm afraid. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFD53FhtTMYHG2NR9URAjKCAJ0Zbqv+bqwl0K4ogqaDrsvpFrXk5ACcCL35 442xMT8TRDCAkZkjNCLu1mw= =Ivr4 -----END PGP SIGNATURE-----
On Monday 06 February 2006 10:55, Carlos E. R. wrote:
Just as a reminder: the editor "joe" is now present in the SuSE rescue system. And vi too, of course ;-)
Thanks. Rescue mode is when I use vi, so I'll test drive joe sometime this week.
I used text mode for a month or two before I got X mode to work properly, back in SuSE 5.2 or something. Sax wasn't available or wasn't much good, and I hadn't discovered this list (did not even have internet, probably).
So, I used those tricks - and many people from that time, I guess.
Adversity is the mother of invention, right? I *like* command line mode for lots of reasons. It "feels" more direct and less cumbersome, particularly for system administrative tasks. Of course, there were few alternatives* to CLI when I started learning computers, so I'm biased. (*at the OS, not application level) Of course, a properly configured contemporary desktop running on top of today's SUSE Linux on top of powerful hardware is a beautiful thing, too!
(I wonder how Erik is progressing?)
Not too well, I'm afraid.
What do you think of my misinterpreted 'red' vs. 'blue' diagnosis? (I'm holding off discussing 'automatic dependency checking,', which I suspect has already been turned off, inadvertently or otherwise.) :-) Carl
* Carl Hartung
Thanks. Rescue mode is when I use vi, so I'll test drive joe sometime this week.
Joe can use the old cp/m familiar wordstar command set. It's like rediscovering an old friend. <grin>. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2
On Monday 06 February 2006 12:19, Patrick Shanahan wrote:
Joe can use the old cp/m familiar wordstar command set. It's like rediscovering an old friend. <grin>.
Wow! I wonder if those neurons still exist in my brain? I'm going to fire it up and try it today. Thanks, Patrick! - Carl
Carl, On Monday 06 February 2006 09:30, Carl Hartung wrote:
On Monday 06 February 2006 12:19, Patrick Shanahan wrote:
Joe can use the old cp/m familiar wordstar command set. It's like rediscovering an old friend. <grin>.
Wow! I wonder if those neurons still exist in my brain? I'm going to fire it up and try it today. Thanks, Patrick! - Carl
A brief anecdote: I was a dyed-in-the-wool Vi programmer working exclusively on Unix systems for many years when the Mac burst on the personal computer scene. As so many did, I became enamored of it and diverted my career for about 10 years to do Mac programming. During this time, I had no access to Vi and used only MPW, BBEdit and Mac-specific text editors and word processors. When in 1997 I got a job back in the Unix (and Windows) world, I went back to Vi (or Vim as the case now often was). I had some trepidation about this, fearing I'd forgotten all my Vi skills. But much to my surprise, they had not dulled at all! I could just sit down and blast away as skillfully as I had for many years back when Vi was the only editor I knew. Basal ganglia are a wonderful thing! But with the experience fresh in my mind of using MPW (a programmable programmers' editor and IDE of sorts), I thought I should try to learn Emacs, it being a highly customizable and programmable editor (and an IDE of sorts). Well, I just couldn't do it. When I tried to use a text-mode, non mouse-and-menus editor, all my Vi knowledge barred the door--I just could not make the switch to the Emacs commands. Not, at least, without taking a lot of time to do nothing but learn a new editor. So I gave up on that. Basal ganglia are a cursed thing! Oddly enough, I don't have any problems taking up new mouse-and-menus editors. So my guess is that you'll probably be able to resurrect your Wordstar editing skills quite quickly. Randall Schulz
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2006-02-06 at 12:19 -0500, Patrick Shanahan wrote:
Joe can use the old cp/m familiar wordstar command set. It's like rediscovering an old friend. <grin>.
I know, I use jstar all the time. It even has syntax highlighting! But I wonder how can I fire up wordstar mode when using joe, instead of jstar. jstar is just a symlink to joe, but the rescue cd doen't have the symlinks, so a way to use joe in ws mode would be interesting - but I failed to find the way in the man page. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFD59gktTMYHG2NR9URAqwFAJ90TaDT+LU1WbIfFFNtzGQTif0HeACgkTTT KKrtnVnMIWdOCiBXnwpHvOU= =pedI -----END PGP SIGNATURE-----
* Carlos E. R.
I know, I use jstar all the time. It even has syntax highlighting!
But I wonder how can I fire up wordstar mode when using joe, instead of jstar. jstar is just a symlink to joe, but the rescue cd doen't have the symlinks, so a way to use joe in ws mode would be interesting - but I failed to find the way in the man page.
I don't know. jstar is just a simlink to joe: pat@wahoo:~> l `which jstar` lrwxrwxrwx 1 root root 3 2004-06-21 08:13 /usr/local/bin/jstar -> joe* I find that 'joe' is close enough to ws/qedit/... and several small cp/m editors I grew accustomed years ago.... -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2
Carl Hartung wrote:
On Monday 06 February 2006 10:55, Carlos E. R. wrote:
Just as a reminder: the editor "joe" is now present in the SuSE rescue system. And vi too, of course ;-)
Thanks. Rescue mode is when I use vi, so I'll test drive joe sometime this week.
I used text mode for a month or two before I got X mode to work properly, back in SuSE 5.2 or something. Sax wasn't available or wasn't much good, and I hadn't discovered this list (did not even have internet, probably).
So, I used those tricks - and many people from that time, I guess.
Adversity is the mother of invention, right? I *like* command line mode for lots of reasons. It "feels" more direct and less cumbersome, particularly for system administrative tasks. Of course, there were few alternatives* to CLI when I started learning computers, so I'm biased. (*at the OS, not application level)
Of course, a properly configured contemporary desktop running on top of today's SUSE Linux on top of powerful hardware is a beautiful thing, too!
(I wonder how Erik is progressing?)
Not too well, I'm afraid.
What do you think of my misinterpreted 'red' vs. 'blue' diagnosis? (I'm holding off discussing 'automatic dependency checking,', which I suspect has already been turned off, inadvertently or otherwise.) :-)
Carl
To you all. I'm not usre if I'll try further on with this challenge. Just now, I'm very tired, but time will show what I'll do. Maybe another time I'll try to fix the problem, and by your help. Thanks for the expression for your help, wich I do appreciate very much. And then thanks to all, that has helped me. /Erik
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2006-02-06 at 11:48 -0500, Carl Hartung wrote:
So, I used those tricks - and many people from that time, I guess.
Adversity is the mother of invention, right? I *like* command line mode for lots of reasons. It "feels" more direct and less cumbersome, particularly for system administrative tasks. Of course, there were few alternatives* to CLI when I started learning computers, so I'm biased. (*at the OS, not application level)
One of the reasons I liked Linux is that it had a CLI with the features MsDos could have had, but never had. And one thing I disliked was the sometimes cumbersome interfaces - like for example, keys like ctrl-right not working in editors, or mouse doing nothing in text mode. Thus, gpm was nice... the only program I know that uses the mouse in text mode is mc (midnight commander). I guess that user friendly programs came to Linux when graphic desktops were already in boom.
Of course, a properly configured contemporary desktop running on top of today's SUSE Linux on top of powerful hardware is a beautiful thing, too!
Yea! You can have dozens of xterms laying around ;-)
(I wonder how Erik is progressing?)
Not too well, I'm afraid.
What do you think of my misinterpreted 'red' vs. 'blue' diagnosis?
I always forget and have to look at the help guide. O:-) But then, I know better that trying to install the newest and shiniest ;-)
(I'm holding off discussing 'automatic dependency checking,', which I suspect has already been turned off, inadvertently or otherwise.) :-)
Ough. Yes, that could explain why the "xorg-x11-libs...rpm" is missing. Or the main package has wrong dependency table. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFD5967tTMYHG2NR9URAhZQAJ0W3O0ghG0+u0pwUeQypKnxpvzxVgCdEhor xtO2KVODpUAazHagpHEAJcc= =qZZA -----END PGP SIGNATURE-----
* Carlos E. R.
One of the reasons I liked Linux is that it had a CLI with the features MsDos could have had, but never had. And one thing I disliked was the sometimes cumbersome interfaces - like for example, keys like ctrl-right not working in editors, or mouse doing nothing in text mode. Thus, gpm was nice... the only program I know that uses the mouse in text mode is mc (midnight commander). I guess that user friendly programs came to Linux when graphic desktops were already in boom.
I use jed in mail.mode/mutt.mode as my editor in mutt. Removes sig's and correctly reformates quotes, removes quote layers, etc. AND recognizes the mouse in xterm or a regular term session with gpm active. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery2
Carlos E. R. wrote:
It is not so complicated to do by hand. Any of the two commands above would produce the list; it is just a question of using an editor and leaving only the needed packages, and then feeding that list to rpm:
cd /media/dvd/...... rpm --test --install ---force rpm1 rpm2 rpm3 rpm4.....
if it works, then repeat without "test".
Notice that you can copy and paste in text mode, provided you first do "rcgpm start" to load the text mode mouse driver. Otherwise, it is simple enough to convert the edited list into a one line script.
Hi Carlos. I have ran the 3 suggestions you wrote for me: carlos1: 1136964478 Wed Jan 11 2006Tue Sep 13 2005 xorg-x11-fonts-100dpi 6.8.2 100 http://www.suse.de/feedback 1136964485 Wed Jan 11 2006Tue Sep 13 2005 xorg-x11-fonts-cyrillic 6.8.2 100 http://www.suse.de/feedback 1136964488 Wed Jan 11 2006Tue Sep 13 2005 xorg-x11-fonts-syriac 6.8.2 100 http://www.suse.de/feedback 1136964490 Wed Jan 11 2006Tue Sep 13 2005 xorg-x11-man 6.8.2 100 http://www.suse.de/feedback carlos2: TRIGGERVERSION TRIGGERFLAGS TRIGGERINDEX VERIFYSCRIPT CHANGELOGTIME CHANGELOGNAME CHANGELOGTEXT PREINPROG POSTINPROG PREUNPROG POSTUNPROG BUILDARCHS carlos3: xscreensaver-4.22-5 Sat Feb 4 20:22:30 2006 xorg-x11-server-6.8.2-100 Sat Feb 4 20:22:24 2006 xntp-4.2.0a-46 Sat Feb 4 20:22:19 2006 vorbis-tools-1.0.1-93 Sat Feb 4 20:22:12 2006 tightvnc-1.2.9-186 Sat Feb 4 20:22:11 2006 smpppd-1.59-4 Sat Feb 4 20:22:10 2006 rcgpm: Neither the variables MOUSEDEVICE and MOUSETYPE nor the variable GPM_PARAM is set in /etc/sysconfig/mouse What to insert here ?. I use an optical HP Mouse. Being in Yast it tells to ignore mouse --regardles of if one exists. Now to the work back again, but I'm not quite sure on how to do, as I don't seem to be able to see what packageversions that was active before the destroying tools had been initialized . Think what you wrote: "cd /media/dvd/...... rpm --test --install ---force rpm1 rpm2 rpm3 rpm4....." Should be used, but when ?. /Erik
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2006-02-06 at 05:28 +0100, Erik Jakobsen wrote:
I have ran the 3 suggestions you wrote for me:
carlos1:
1136964478 Wed Jan 11 2006Tue Sep 13 2005 xorg-x11-fonts-100dpi 6.8.2 100 http://www.suse.de/feedback 1136964485 Wed Jan 11 2006Tue Sep 13 2005 xorg-x11-fonts-cyrillic 6.8.2 100 http://www.suse.de/feedback 1136964488 Wed Jan 11 2006Tue Sep 13 2005 xorg-x11-fonts-syriac 6.8.2 100 http://www.suse.de/feedback 1136964490 Wed Jan 11 2006Tue Sep 13 2005 xorg-x11-man 6.8.2 100 http://www.suse.de/feedback
This list has the most recently installed at the bottom.
carlos3:
xscreensaver-4.22-5 Sat Feb 4 20:22:30 2006 xorg-x11-server-6.8.2-100 Sat Feb 4 20:22:24 2006 xntp-4.2.0a-46 Sat Feb 4 20:22:19 2006 vorbis-tools-1.0.1-93 Sat Feb 4 20:22:12 2006 tightvnc-1.2.9-186 Sat Feb 4 20:22:11 2006 smpppd-1.59-4 Sat Feb 4 20:22:10 2006
This other list has the most recently installed at the top.
rcgpm:
Neither the variables MOUSEDEVICE and MOUSETYPE nor the variable GPM_PARAM is set in /etc/sysconfig/mouse
What to insert here ?. I use an optical HP Mouse. Being in Yast it tells to ignore mouse --regardles of if one exists.
It should have been set up by Yast, if I remember correctly. Anyway: MOUSEDEVICE="/dev/mouse" GPM_PARAM="" MOUSETYPE=??? look it up in "/etc/X11/xorg.conf". For example, if you see: Section "InputDevice" Driver "mouse" Identifier "Mouse[1]" ... Option "Protocol" "imps/2" Then you enter MOUSETYPE=imps2 or exps2 - it works for me. I just tried several till it worked.
Now to the work back again, but I'm not quite sure on how to do, as I don't seem to be able to see what packageversions that was active before the destroying tools had been initialized .
But as the list is ordered by install date (not rpm creation date), and you know when you did what you did, you simply have to replace any thing installed that day and later.
Think what you wrote:
"cd /media/dvd/...... rpm --test --install ---force rpm1 rpm2 rpm3 rpm4....."
Should be used, but when ?.
When you know what you have to reinstall. Change to the directory in the dvd containing the rpm, and enter the appropriate command line containing the name of every rpm you want to reinstall... - From your list above, I see you installed "xorg-x11-server-6.8.2-100" on "Sat Feb 4 20:22:24 2006" - the day before you posted your question. Obviously, that's one rpm to reinstall: that and everything installed Feb 4 and later. If you reinstall more than you need, it doesn't matter. Not much, anyway. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFD53AFtTMYHG2NR9URAmHwAJwO/LEZ4WaZDB7gbtqj1q5cLQ7jwwCcCIi4 OPdayNmosUY3DR9rc2xk0kc= =Dr2y -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2006-02-06 at 16:49 +0100, I wrote:
It should have been set up by Yast, if I remember correctly. Anyway:
MOUSEDEVICE="/dev/mouse" GPM_PARAM="" MOUSETYPE=???
look it up in "/etc/X11/xorg.conf". For example, if you see:
Section "InputDevice" Driver "mouse" Identifier "Mouse[1]" ... Option "Protocol" "imps/2"
Then you enter
MOUSETYPE=imps2
or exps2 - it works for me. I just tried several till it worked.
Correction: I have in "xorg.conf": Option "Protocol" "explorerps/2" Thus in "/etc/sysconfig/mouse" I have: MOUSETYPE="exps2" I forgot I was testing something and had to retrieve files from the backup. Yours will be diferent, but you should see the idea. You do not really need to set up rcgpm if you don't want to: just make dump the rpm list to a file (rpm whatever > file.txt), and edit the file. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFD53TCtTMYHG2NR9URAou4AJ0bOvs2vlV8UhakJ5e0diEKFWEepgCeOHSy /WJmnwk/cTBMzgqBr9BZots= =wYiP -----END PGP SIGNATURE-----
Carlos E. R. wrote:
The Sunday 2006-02-05 at 19:54 +0100, Erik Jakobsen wrote:
Well to that I'll say, that I use the information mentioned on this URL:
...
For example, I'd use:
rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} %{BUILDTIME:day} %-30{NAME}\t%{VERSION} %{RELEASE} %35{PACKAGER}\n" | sort | less -S
which produces an rpm list ordered by install date with some data fields; the last one identifies the packager, which could help you identify them.
... Hi Carlos Not sure if this warrants another thread - apologies if you think it should ... I've been watching this thread with great interest following my earlier "[SLE] Session management error" thread to which you contributed. My system has returned to a "flaky" state (YaST2 hangs when refreshing any mirror site other than Packman ...) and I'm genuinely not sure of the cause. I've tried Carl's '... run "yast" in ncurses (text) mode.' without any resolution, so ran your command (rpm ... ) above. Checking the results of the query I note that an application (specifically: BitTorrent) that I installed using YaST2 some three+ days ago, from a SuSE mirror site, shows as being installed yesterday (build date unchanged: 13/09/05). Any comments on this ... Cheers Brian
On Mon, 2006-02-06 at 11:16 +0000, Brian Green wrote:
Carlos E. R. wrote:
The Sunday 2006-02-05 at 19:54 +0100, Erik Jakobsen wrote:
Well to that I'll say, that I use the information mentioned on this URL:
...
For example, I'd use:
rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} %{BUILDTIME:day} %-30{NAME}\t%{VERSION} %{RELEASE} %35{PACKAGER}\n" | sort | less -S
which produces an rpm list ordered by install date with some data fields; the last one identifies the packager, which could help you identify them.
...
Hi Carlos
Not sure if this warrants another thread - apologies if you think it should ...
I've been watching this thread with great interest following my earlier "[SLE] Session management error" thread to which you contributed. My system has returned to a "flaky" state (YaST2 hangs when refreshing any mirror site other than Packman ...)
It may appear to hang when it actually just takes a very long time to refresh. On my laptop I start up Software Management and walk away for about 10 minutes because it takes so long. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
Ken Schneider wrote:
On Mon, 2006-02-06 at 11:16 +0000, Brian Green wrote:
Carlos E. R. wrote:
The Sunday 2006-02-05 at 19:54 +0100, Erik Jakobsen wrote:
Well to that I'll say, that I use the information mentioned on this URL:
... For example, I'd use:
rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} %{BUILDTIME:day} %-30{NAME}\t%{VERSION} %{RELEASE} %35{PACKAGER}\n" | sort | less -S
which produces an rpm list ordered by install date with some data fields; the last one identifies the packager, which could help you identify them.
...
Hi Carlos
Not sure if this warrants another thread - apologies if you think it should ...
I've been watching this thread with great interest following my earlier "[SLE] Session management error" thread to which you contributed. My system has returned to a "flaky" state (YaST2 hangs when refreshing any mirror site other than Packman ...)
It may appear to hang when it actually just takes a very long time to refresh. On my laptop I start up Software Management and walk away for about 10 minutes because it takes so long.
Ken, valid point, and I did consider that I was expecting too much! But, until the w/e, refresh from all of the mirror sites I was accessing was 'almost' instant. In this case Software Management required a 'Forced Quit' as Abort was inactive. Similarly, I could directly access the mirror sites by http/ftp without any pause. Hence, I rationalised that the problem was internal (conflict with some 'reference' table ???) rather than external (i.e. everybody access the same mirror sites as me a the same time ...). Cheers Brian
On Tue, 2006-02-07 at 08:41 +0000, Brian Green wrote:
Ken Schneider wrote:
On Mon, 2006-02-06 at 11:16 +0000, Brian Green wrote: <snip>
It may appear to hang when it actually just takes a very long time to refresh. On my laptop I start up Software Management and walk away for about 10 minutes because it takes so long.
Ken, valid point, and I did consider that I was expecting too much! But, until the w/e, refresh from all of the mirror sites I was accessing was 'almost' instant. In this case Software Management required a 'Forced Quit' as Abort was inactive. Similarly, I could directly access the mirror sites by http/ftp without any pause. Hence, I rationalised that the problem was internal (conflict with some 'reference' table ???) rather than external (i.e. everybody access the same mirror sites as me a the same time ...).
You must remember that a lot more takes place then just accessing a web/ftp site. There is a lot of internal processing going on comparing existing file versions with the lists obtained from the web sites. With the same repos on my desktop and laptop, it takes almost twice as long on the laptop to refresh then the desktop. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
Ken Schneider wrote:
On Tue, 2006-02-07 at 08:41 +0000, Brian Green wrote:
Ken Schneider wrote:
On Mon, 2006-02-06 at 11:16 +0000, Brian Green wrote: <snip> It may appear to hang when it actually just takes a very long time to refresh. <snip>
Ken, valid point, and I did consider that I was expecting too much! <snip>
You must remember that a lot more takes place then just accessing a web/ftp site. There is a lot of internal processing going on comparing existing file versions with the lists obtained from the web sites. With the same repos on my desktop and laptop, it takes almost twice as long on the laptop to refresh then the desktop.
Ken, not meaning to be pedantic, nor do I feel the need to have the last word, but ... Today (just!) click "Software Management" to "Search:", refreshing the database to SIX mirror sites, plus "cd:///", took less than 40 seconds. This is, and has consistently been, a typical time until this w/e ... where it appeared to "hang". Similarly, adding a new ftp source (in "Installation Sources"), or executing a Refresh (via, Edit/Refresh) currently, and typically, takes less than 4 seconds ... Mustn't quibble, all appears well (on my desktop) at the moment ... Cheers Brian
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2006-02-06 at 11:16 -0000, Brian Green wrote:
Checking the results of the query I note that an application (specifically: BitTorrent) that I installed using YaST2 some three+ days ago, from a SuSE mirror site, shows as being installed yesterday (build date unchanged: 13/09/05).
Any comments on this ...
Dunno... but you could check to see if the rpm database is corrupt. I don't remember how and have no time left, so you look up the man page ;-) Otherwise, something made an automatic update, perhaps. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFD53IgtTMYHG2NR9URAqGKAJ9XgYszUmkXEuuR9WjwjbShA38taQCeMoVA jBWf/QrBgJMJnZXy0/Dwe0w= =cjyA -----END PGP SIGNATURE-----
Carlos E. R. wrote:
The Monday 2006-02-06 at 11:16 -0000, Brian Green wrote:
...
Checking the results of the query I note that an application (specifically: BitTorrent) that I installed using YaST2 some three+ days ago, from a SuSE mirror site, shows as being installed yesterday (build date unchanged: 13/09/05).
Any comments on this ...
Dunno... but you could check to see if the rpm database is corrupt. I don't remember how and have no time left, so you look up the man page ;-)
Otherwise, something made an automatic update, perhaps.
Carlos, Ouch! But, thanks for the starter ... Checked the 'rpm database' using 'rpm -V -a' and got 14,409 potentially compromised packages! Of these 14,338 where, allegedly, 'missing' packages/dependencies, 19 were configuration files (so they can be ignored ...?), but only (!) 493 had some problem with the Modification Time (but not, apparently, BitTorrent, or it's dependencies, as it didn't appear in the list). None of the packages listed were obvious candidates for possible installation problems even if I discounted as relevant a large number of the entries as they appear to relate to cups and hplip - whilst printing and scanning (on my all-in-one) are working fine. So, back to Google, ... Cheers Brian Brian
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2006-02-07 at 13:09 -0000, Brian Green wrote:
Dunno... but you could check to see if the rpm database is corrupt. I don't remember how and have no time left, so you look up the man page ;-)
Otherwise, something made an automatic update, perhaps.
Carlos, Ouch! But, thanks for the starter ...
Checked the 'rpm database' using 'rpm -V -a' and got 14,409 potentially compromised packages!
Ah, no! It is not that. The option -V verifies the list of installed files from rpms and compares them with the original installed versions: size, date, permissions... even an MD5 sum, and displays discrepancies. It can be used, for example, to do "incremental" backups - in fact, this is what Yast backup does. +++ digression Try this for "fun": rpm --all --verify --nomd5 \ | tee $LISTOFNOTVERIFIEDFILESINRPMS \ | sed -n 's/^S.* \///p;s/^\.......T.* \///p' \ | sort > $LISTOFMODIFIEDILESINRPMS Replace the variables with new filenames; the second one is the list of files to make an incremental rpm_backup - ie, backup every file that was installed from the dvd, but modified. New files are not included. If you want to list new files, I use (watch line wrap) in a script: EXTRAPATHSTOBACKUP="/etc /usr /var /bin /sbin /boot /lib /opt /root /home /www" rpm --all --query --list | sort > $LISTOFALLFILESINRPMS & # List files included in a rpm pckg find $EXTRAPATHSTOBACKUP | sort > $LISTOFFOUNDFILES & # List all files in main directories wait # List files not belonging to an rpm, but existing in one of those directories comm -2 -3 $LISTOFFOUNDFILES $LISTOFALLFILESINRPMS > $LISTOFUNIQUEFILES # All files except those in a rpm ++- end digression. However, if a "--verify" run fails, the database is damaged.
Of these 14,338 where, allegedly, 'missing' packages/dependencies, 19 were configuration files (so they can be ignored ...?), but only (!) 493 had some problem with the Modification Time (but not, apparently, BitTorrent, or it's dependencies, as it didn't appear in the list). None of the packages listed were obvious candidates for possible installation problems even if I discounted as relevant a large number of the entries as they appear to relate to cups and hplip - whilst printing and scanning (on my all-in-one) are working fine.
Dependencies problems? If that's correct, that could break yast. Just one idea... Did you "upgrade" kde? That could be it... The thread is to long to verify if you said you did, but from your first email I think you might. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFD6QOZtTMYHG2NR9URAt1zAKCNs6yS/BsGskeG/66VlizwdTUPwQCeMz7c fAu3EkMPG2fohpX1IbEZL5s= =omu2 -----END PGP SIGNATURE-----
Carlos E. R. wrote:
The Tuesday 2006-02-07 at 13:09 -0000, Brian Green wrote:
Dunno... but you could check to see if the rpm database is corrupt. I don't remember how and have no time left, so you look up the man page ;-)
...
Carlos, Ouch! But, thanks for the starter ...
Checked the 'rpm database' using 'rpm -V -a' and got 14,409 potentially compromised packages!
Ah, no! It is not that. The option -V verifies the list of installed files from rpms ... ...
Just one idea... Did you "upgrade" kde? That could be it...
... Carlos, Thanks for the heads-up concerning kde. Tut! I'm guilty of not picking that up from the other thread ... So, just done the updates. It would appear then that my rpm database is not corrupted. However, as this is the year of the sleepy dog, and as my system is currently behaving, I going to let it lie ... Much appreciate your help, cheers Brian
On Sunday 05 February 2006 13:54, Erik Jakobsen wrote:
Well to that I'll say, that I use the information mentioned on this URL: http://www.novell.com/coolsolutions/feature/16592.html
Hi Erik, You didn't include a link to the article in your original post, but I was able to locate it with Google. I've already quoted this excerpt once, but it is important and apparently needs repeating: "It's worth a note, however, to mention that because a lot of these packages are bleeding edge, slight system instability may occur from performing the updates listed here." and the feedback comment, too: "This is very interesting, but hardly something that should go into "newbies," unless one enjoys the thought of newbies trashing their systems. Just to see what would happen, I tried this in the lab. The desktop became unuseable, forcing a reimage on the test machine." My point here is this: There were clear warnings provided that your system and desktop could become unstable by following the procedure described in the article.
Even SuSE provided kde upgrades (not YOU updates), are somewhat experimental and supportless.
That's a pity.
The unofficial SUSE supplementary packages come with a README.txt file in the base directory. It includes the following disclaimer and warnings: "We publish these packages as a service to the community... there is no warranty... If you wish to use a newer version of a package and if you insist on having properly working updates at hand if there is a security update, then please use a newer SuSE Linux version. If you feel a little bit adventurous, then these packages will suit your needs." Again, you have been warned about breakage resulting from introducing "bleeding edge," "unofficial" and "unsupported" packages into your system. Now it starts to get really interesting (not for you, but from a troubleshooting perspective):
Thus, provided you are using the official, original, rpms, just tell Yast to reinstall that "xorg-x11-libs...rpm", again, regardless of it being already installed.
Would be nice if you would give me advice on how to do it. I have thought in the same direction, but doesn't know exactly how, and another case is that it will be a huge job,
????????????????????????????????????????????????????????????
as I have updated all possible packages marked red or blue ????????????????????????????????????????????????????????????
as shown in the article above.
If you don't understand what the red and blue are telling you, this could explain a *lot* of your problems. That article will cause you to break your system even if you know what you are doing. Not understanding what the red and blue is telling you makes the problem worse... it's like mistaking your gas pedal for the brake pedal in your car. :-/ Red = you already have the "latest" available version installed. It means *do not update" (I think if you select it, YaST will interpret your instructions as a request to *downgrade* the package... the opposite of what you want.) Blue = an updated version is available, meaning you can update it if you want.
I will say, that this is the second time I encounter this behaviour. First time I gave up repair the installed 10.0.
We have an old saying: "Third time is a charm" :-)
At first it worked splendid, but when I look through the Yast->Software management->Package Group->zzz-All the second time, ??????????????????????????????????????????????????? and mark the red and blue packages it runs wrong, ??????????????????????????????????????????????????? due to a reason I don't know.
:-) I do :-)
Thought it was nice having found the pahe mentioned above, but it may be wrong, and there may be something, that I don't understand ?.
Yes. You need to study the rpm package database management system. When you understand how rpm works, the tools in YaST are very, very helpful. When you *don't* understand them, upgrades like the one you are attempting are difficult to manage without breaking your system. regards, - Carl
Carl Hartung wrote:
On Sunday 05 February 2006 13:54, Erik Jakobsen wrote:
Well to that I'll say, that I use the information mentioned on this URL: http://www.novell.com/coolsolutions/feature/16592.html
Hi Erik,
Hi Carl.
You didn't include a link to the article in your original post, but I was able to locate it with Google. I've already quoted this excerpt once, but it is important and apparently needs repeating:
Oh sorry, but good you found it yourself.
"It's worth a note, however, to mention that because a lot of these packages are bleeding edge, slight system instability may occur from performing the updates listed here."
I have felt that on my old body :-).
and the feedback comment, too:
"This is very interesting, but hardly something that should go into "newbies," unless one enjoys the thought of newbies trashing their systems. Just to see what would happen, I tried this in the lab. The desktop became unuseable, forcing a reimage on the test machine."
That I have read, but too late :-(
My point here is this: There were clear warnings provided that your system and desktop could become unstable by following the procedure described in the article.
Yes you of course are right.
Even SuSE provided kde upgrades (not YOU updates), are somewhat experimental and supportless.
That's a pity.
The unofficial SUSE supplementary packages come with a README.txt file in the base directory. It includes the following disclaimer and warnings:
Do you mean that txt, that is visible if marking a package ?.
"We publish these packages as a service to the community... there is no warranty... If you wish to use a newer version of a package and if you insist on having properly working updates at hand if there is a security update, then please use a newer SuSE Linux version. If you feel a little bit adventurous, then these packages will suit your needs."
Oh yes !
Again, you have been warned about breakage resulting from introducing "bleeding edge," "unofficial" and "unsupported" packages into your system.
That's right, and I'm not telling the opposite :-)
Now it starts to get really interesting (not for you, but from a troubleshooting perspective):
If it starts. At the present I don't feel for it.
Thus, provided you are using the official, original, rpms, just tell Yast to reinstall that "xorg-x11-libs...rpm", again, regardless of it being already installed.
Would be nice if you would give me advice on how to do it. I have thought in the same direction, but doesn't know exactly how, and another case is that it will be a huge job,
????????????????????????????????????????????????????????????
as I have updated all possible packages marked red or blue
????????????????????????????????????????????????????????????
as shown in the article above.
If you don't understand what the red and blue are telling you, this could explain a *lot* of your problems. That article will cause you to break your system even if you know what you are doing.
I hasve been told, that both the red and blue are for update, but have now learned it that its not true the hard way .. Pyhh.
Not understanding what the red and blue is telling you makes the problem worse... it's like mistaking your gas pedal for the brake pedal in your car. :-/
That's why I cannot drive in my car :-)
Red = you already have the "latest" available version installed. It means *do not update" (I think if you select it, YaST will interpret your instructions as a request to *downgrade* the package... the opposite of what you want.)
Blue = an updated version is available, meaning you can update it if you want.
Thanks for this explanation Carl.
I will say, that this is the second time I encounter this behaviour. First time I gave up repair the installed 10.0.
We have an old saying: "Third time is a charm" :-)
Charm ???. I really need my spectacles, and even that I'm not sure it will be a charm :-)
At first it worked splendid, but when I look through the Yast->Software management->Package Group->zzz-All the second time,
???????????????????????????????????????????????????
and mark the red and blue packages it runs wrong,
???????????????????????????????????????????????????
due to a reason I don't know.
:-) I do :-)
Now I do too I do :-)
Thought it was nice having found the pahe mentioned above, but it may be wrong, and there may be something, that I don't understand ?.
Yes. You need to study the rpm package database management system.
Ok.
When you understand how rpm works, the tools in YaST are very, very helpful. When you *don't* understand them, upgrades like the one you are attempting are difficult to manage without breaking your system.
But how to do when I'm colour blind :-), Was a joke.
regards,
- Carl
Regards, Erik P.S. I'm not sure I'll do the job.
On Monday 06 February 2006 11:55, Erik Jakobsen wrote:
P.S. I'm not sure I'll do the job.
The important thing is you have persisted until the solution was found. If you save your data, clean out the partition and install again, please leave it 'stock' so you can have a stable desktop and study ahead of time what you want to do. It's OK to ask questions here *before* you get into trouble. ;-) regards, Carl
Addendum. I missed this question. Sorry! - Carl On Monday 06 February 2006 11:55, Erik Jakobsen wrote:
Do you mean that txt, that is visible if marking a package ?.
Look in this directory: ftp://mirror.mcs.anl.gov/pub/suse/i386/supplementary - Carl
On Monday 6 February 2006 17:55, Erik Jakobsen wrote:
Carl Hartung wrote:
On Sunday 05 February 2006 13:54, Erik Jakobsen wrote:
Well to that I'll say, that I use the information mentioned on this URL: http://www.novell.com/coolsolutions/feature/16592.html
Hi Erik,
Hi Carl.
---------------------[ 8< ]--------------------------------------------------- Dear List, It is good to see how many people are willing to help each other on a list like this. SuSE is always sold (!) as an easy to use, perfect for beginners and non-technical people distribution. When Novell took over SuSE they claimed they should maintain the high standard SuSE users were used to. The opposite seems to be true. You buy a "distro" and from there, you are on your own. They release "fixes" that could make your system unusable in the worst case. The main question that rises my mind is "How the H&ll do they test their software, if it is tested at all". And how do they expect to sell distributions, if their fixes can ruin a *customers* machine, even if they say so in a (lousy IMO) disclaimer. If you let people pay for your product, make it work or don't sell it in the first place. The fact that official updates crash the machine, is one of the main reasons why people switch to Linux from "the other operating system". By releasing bad binaries or update scripts, you damage the entire Linux community because most people don't see the difference between a distribution and Linux in General. One of the most common errors I saw in the updates, were the missing sym-links. Did anyone tried to compile a QMake project under KDevelop (SuSE 10.0 boxed set) without creating a /usr/lib/qt3 link to the real directory? ( /usr/lib/qt3 is defined in the -spec files of Qt but the link is not created during installation, so qmake, designer, assistant, uic and moc can not be found as the PATH is set to the formentioned link) Every update of KDE or X, seem to break the Screensaver links. Again: This seems like untested to me. My advice to beginners today would be: don't use SuSE for your every day work. Nice to look at if you are curious, but for the serious user, please take Fedora if you can. If it has some problems, you didn't pay EUR 68,= for it and the amount of binaries are plenty on the Internet. I know there is an OpenSuSE version now, but if people have a choice, they choose applications. And the boxed set is more packed with that. Quite simple. I sincerely hope that Novell is reading this list, because since my previous mail, I'm quite disappointed. I used SuSE Linux from version 5 but left this distro since 9.0 because of the slow responses on the desktop. I bought the boxed 10.0 set, but saw no improvements and reinstalled Fedora again. Kind Regards, -- Peter M. Groen Open Systems Development Klipperwerf 12 2317 DZ Leiden T : +31-(0)71-5216317 M : +31-(0)6-29563390 E : pgroen@osdev.xs4all.nl Skype : peter_m_groen
On Mon, 2006-02-06 at 18:32 +0100, Peter M. Groen wrote:
On Monday 6 February 2006 17:55, Erik Jakobsen wrote: ---------------------[ 8< ]---------------------------------------------------
Dear List,
It is good to see how many people are willing to help each other on a list like this.
SuSE is always sold (!) as an easy to use, perfect for beginners and non-technical people distribution. When Novell took over SuSE they claimed they should maintain the high standard SuSE users were used to. The opposite seems to be true.
You buy a "distro" and from there, you are on your own. They release "fixes" that could make your system unusable in the worst case.
You will very, very rarely find YOU fixes that make a system unusable. If -you- stray away from SUSE blessed packages it is -your- responsibility to make sure they will not make -your- system unstable not SuSE. ANY third party software downloaded from other the ftp.suse.com or an authorized mirror site IS third party and it is not the responsibility of Novell/SuSE to test those packages. If -you- have a problem with an installed third party package complain to the author of that site!
The main question that rises my mind is "How the H&ll do they test their software, if it is tested at all". And how do they expect to sell distributions, if their fixes
What fixes are you talking about and be very specific as to where you downloaded the "fixes" from and how you installed them. Do you honestly think that if the problems were in the distribution purchased from Novell that -you- would be the only one having the problems? Get real and get a life. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
Hi Peter, On Monday 06 February 2006 12:32, Peter M. Groen wrote:
It is good to see how many people are willing to help each other on a list like this.
Yes it is. So what is your contribution today? The core problem which instigated this thread was the OP misinterpreting the meaning of 'red' and 'blue' package listings in YaST's Software Management module. You're not trying to blame Novell/SUSE for that, are you? I agree the article *should* have carried a larger and more stern warning, but this is just a single editorial oversight. It certainly isn't fair to cast it as an accurate indicator of the distribution quality or of Novell/SUSE's competence. That's just irrational. You must be mad (as in "angry.") With change comes adaptation and, yes, adjustments can be painful. The distribution is growing and maturing in an organic fashion, making it sometimes difficult to stay on top. And there will always be a learning curve, no matter the platform. So, the traffic on these lists is, by and large, dealing with problems along that curve and finding solutions to them. I think you will have a hard time finding a list where everybody is posting frequent "Just letting everybody know my system is still running great! I'll post to the problem list if one crops up!" Do you know of such a list? Of course not! With these factors in mind, I think your "don't use SuSE for your every day work" proposition is pure rubbish! I use SUSE for everything, including my every day work, excepting of course a couple of applications where no comparable Linux/OSS packages are available. The rest of the time, I honestly feel very sorry for people stuck running other systems, even other Linux distributions. I think to myself "They don't know what they're missing! What a beautiful piece of engineering... a work of art... and love!" So please keep this kind of whining to the OT list, if you must vent. bye, Carl
participants (9)
-
Brian Green -
Carl Hartung -
Carlos E. R. -
Erik Jakobsen -
James Knott -
Ken Schneider -
Patrick Shanahan -
Peter M. Groen -
Randall R Schulz