Once a week for the past few months, I’ve been doing an online update to my OpenSuse 12.1. Until now everything has worked flawlessly. Last night’s update was large, including thunderbird and my default kernel.
Today the third party TB external editor extension apparently failed silently. Following previous TB online updates, thunderbird runs a self test to decide if the addons work. Not so with TB Vs 11.0.1. I think my previous TB was at Vs 10.
What I want to try is to roll back the TB online update to where it was prior to the update. There must be a record somewhere what happened with that last online update.
A snapshot of my updated status is: OpenSuse 12.1 kernel 3.1.10-1.9-default #1 SMP Thu Apr 5 on a Pentium 4. I’m running lxde, but I also have Kde 4.7.2 release 5 installed. Thunderbird is now at revision 11.0.1 and the globs EE extension is Vs 1.0. The external editor I use is oowriter from Libre Office 3.4.5 built 1505.
So my question is how would I go back to the previous thunderbird version, not knowing what that version was? heboland
If you don’t know what the previous version was, it’s hard. But you could revert to the version that came with the distro. Search for the TB package, click versions, click the version you want, the package will be marked for install. Afterwards lock the package to stop it from updating.
> So my question is how would I go back to the previous thunderbird
> version, not knowing what that version was? heboland
Fire up yast package manager. I’ll assume you use the qk aka kde version.
Search for the thunderbird package. There is a tab named “versions”, select
it. You will see a list of thunderbird version, one marked, which is the
current one. You can mark any other and install it.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
Robin, how slick your advice worked! It took me a while to find the Revision Tab after searching for TB, but there was the entire update TB history.
Knurpht, your solution would have worked also, but Robin’s revision history started with TB 7, then 9, 10, and 11. If I would have gone back to TB 7, I don’t know if I could have updated to TB 10 without jumping straight to TB 11.
In the end this whole “problem” turned out to be an operator error on my part! When I rolled back to TB10, the globs EE 1.0 didn’t display. Poking around, I discovered that the Composition Toolbar wasn’t displayed. Apparently in the online update to TB 11, that option got changed. Selecting that toolbar revealed the EE button.
From there I updated TB back to 11.0.1. TB did the self test and the toolbar and EE button was there and working.
For the record, I have the globs EE 1.0 working this TB 11.0.1 using oowriter from Libre Office 3.4.5.
Robin, Knurpht, thanks for you excellent help. I tried to mark this thread solved. If it needs more marking, feel free! heboland
On 2012-04-23 03:16, heboland wrote:
>
> Hi Robin, Knurpht!
>
> Robin, how slick your advice worked! It took me a while to find the
> Revision Tab after searching for TB, but there was the entire update TB
> history.
Welcome
It should be easy to see - unless you use the GTK / Gnome version of Yast,
there I’m not sure how to do it.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
heboland, congratulations on sorting your difficulty.
wrt one of your questions in the thread:
… one way to get a list as to what was updated, is to use a basic rpm command in a terminal. By doing this in a terminal means one can do this with or without an X GUI.
Send the command:
rpm -qa --last | less
and scroll up/down with the up/down arrow keys and PgUp/PgDn keys.
or send the contents to another file (in my example arbitrarily called “myupdatedrpms.txt” ):
rpm -qa --last > myupdatedrpms.txt
and then use a text editor like ‘mc’ (or if one has a GUI a text editor like leafpad or kwrite or gedit) to look at myupdatedrpms.txt. Or after having created myupdatedrpms.txt, look at myupdatedrpms.txt with a command like ‘cat’.
> … one way to get a list as to what was updated, is to use a basic rpm
> command in a terminal. By doing this in a terminal means one can do this
> with or without an X GUI.
>
> Send the command:
>
> Code:
> --------------------
>
> rpm -qa --last | less
>
> --------------------
I find that this has little information, so I use this other set of
commands instead:
