I just updated to 12.1 and now I can’t get Software Management, Package Search, On-line update, or Software Repositories to open. I click on any of them and just get a watch. Just when I thought I could get back to work!
On 2012-05-03 23:56, stevericketts wrote:
>
> I just updated to 12.1
Which method?
Online upgrade method
Offline upgrade method
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
As the word “updated” is a rather generic English term, like Carlos I urge you to tell what you updated from and how you did that.
Apart from the two “upgrade” (mind another generic English term for the same general idea) methods Carlos points to There are more possibilities. Not all of these are advisable though.
Upgraded from 11.3 to 12.1 using DVD, off-line.
By using the Upgrade button there, or by reinstalling?
On 2012-05-04 15:26, stevericketts wrote:
> Upgraded from DVD, off-line.
You don’t give much info. Well, then you still have to follow the tips on
what to do after the upgrade.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
I don’t give much information because I have no idea where to go next. I upgraded, got no error messages, but things don’t work. I was assuming you would have something for me to look at. As far as the “tips on what to do after the upgrade” is there a specific link to look at?
HCVV: I used the upgrade button.
With no information it’s no easy to say what’s happen…
What’s te message of this command: (as root)
zypper ref
and post here the exit of
zypper lr
linux-cwry:/home/stever/Projects/ComServer/ComServer # zypper ref
** (process:10080): WARNING **: The connection is closed
** (process:10085): WARNING **: The connection is closed
Repository ‘mono’ is up to date.
** (process:10085): WARNING **: The connection is closed
** (process:10085): WARNING **: The connection is closed
Repository ‘openSUSE-12.1-Non-Oss’ is up to date.
** (process:10088): WARNING **: The connection is closed
** (process:10088): WARNING **: The connection is closed
Repository ‘openSUSE-12.1-Oss’ is up to date.
** (process:10085): WARNING **: The connection is closed
** (process:10092): WARNING **: The connection is closed
Retrieving repository ‘openSUSE-12.1-Update’ metadata ]
** (process:10095): WARNING **: The connection is closed
** (process:10095): WARNING **: The connection is closed
Retrieving repository ‘openSUSE-12.1-Update’ metadata ]
** (process:10098): WARNING **: The connection is closed
** (process:10098): WARNING **: The connection is closed
** (process:10154): WARNING **: The connection is closed
Retrieving repository ‘openSUSE-12.1-Update’ metadata |]
** (process:10169): WARNING **: The connection is closed
** (process:10172): WARNING **: The connection is closed
Retrieving repository ‘openSUSE-12.1-Update’ metadata /]
** (process:10184): WARNING **: The connection is closed
** (process:10184): WARNING **: The connection is closed
** (process:10184): WARNING **: The connection is closed
Retrieving repository ‘openSUSE-12.1-Update’ metadata [done]
Building repository ‘openSUSE-12.1-Update’ cache [done]
All repositories have been refreshed.
linux-cwry:/home/stever/Projects/ComServer/ComServer #
linux-cwry:/home/stever/Projects/ComServer/ComServer # zypper lr
| Alias | Name | Enabled | Refresh
–±-----------------------±---------------------------±--------±-------
1 | mono | mono | Yes | No
2 | openSUSE-12.1-12.1-1.4 | openSUSE-12.1-12.1-1.4 | Yes | No
3 | repo-debug | openSUSE-12.1-Debug | No | Yes
4 | repo-debug-update | openSUSE-12.1-Update-Debug | No | Yes
5 | repo-non-oss | openSUSE-12.1-Non-Oss | Yes | Yes
6 | repo-oss | openSUSE-12.1-Oss | Yes | Yes
7 | repo-source | openSUSE-12.1-Source | No | Yes
8 | repo-update | openSUSE-12.1-Update | Yes | Yes
I took some of the “** (process:10184): WARNING **: The connection is closed” statements out because there were quite a few.
Plaese use CODE tags around computer text: http://forums.opensuse.org/english/information-new-users/advanced-how-faq-read-only/451526-posting-code-tags-guide.html
Actually, after looking around a bit, it doesn’t look like I can launch anything from Yast… I tried AppArmor, Firewall, Windows Domain, Samba Server, etc.
On 2012-05-04 18:36, stevericketts wrote:
>
> linux-cwry:/home/stever/Projects/ComServer/ComServer # zypper ref
You did not do “su -”, you did “su”. Means problems.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
On 2012-05-04 17:56, stevericketts wrote:
> As far as the
> “tips on what to do after the upgrade” is there a specific link to look
> at?
I gave it already.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
On Fri, 04 May 2012 20:58:06 +0000, Carlos E. R. wrote:
> On 2012-05-04 18:36, stevericketts wrote:
>>
>> linux-cwry:/home/stever/Projects/ComServer/ComServer # zypper ref
>
> You did not do “su -”, you did “su”. Means problems.
I’m curious - what problems do you think you would see using ‘su’ vs ‘su
-’ for doing a ‘zypper ref’? I ask because before I got in the habit of
doing ‘su -’ myself, I used to just use ‘su’ and do a ‘zypper ref’ and it
never failed for me.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
Did you use the Update Installed option from the DVD? This method is only for subsequent releases, i.e. 11.3 -> 11.4. If this is what you’ve done, do yourself a favor and perform a clean install.
On 2012-05-04 23:04, Jim Henderson wrote:
>> You did not do “su -”, you did “su”. Means problems.
>
> I’m curious - what problems do you think you would see using ‘su’ vs ‘su
> -’ for doing a ‘zypper ref’? I ask because before I got in the habit of
> doing ‘su -’ myself, I used to just use ‘su’ and do a ‘zypper ref’ and it
> never failed for me.
Path is different, for instance. I have seen many “funny” problems clear
out when you use that dash, so I simply refuse to study a problem till it
is retried properly
Maybe it is not a problem this time, but it can not be assured.
And, if he used “su” for zypper, he probably did the same for yast, and
this I know is a problem (the bus messages, for instance, permission denied
on DISPLAY…).
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
On 2012-05-04 23:16, Knurpht wrote:
>
> Did you use the Update Installed option from the DVD? This method is
> only for subsequent releases, i.e. 11.3 -> 11.4. If this is what you’ve
> done, do yourself a favor and perform a clean install.
No, it is not for subsequent releases. It is the zypper dup that is only
for subsequent releases.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
On Fri, 04 May 2012 21:38:07 +0000, Carlos E. R. wrote:
> On 2012-05-04 23:04, Jim Henderson wrote:
>
>>> You did not do “su -”, you did “su”. Means problems.
>>
>> I’m curious - what problems do you think you would see using ‘su’ vs
>> ‘su -’ for doing a ‘zypper ref’? I ask because before I got in the
>> habit of doing ‘su -’ myself, I used to just use ‘su’ and do a ‘zypper
>> ref’ and it never failed for me.
>
> Path is different, for instance. I have seen many “funny” problems clear
> out when you use that dash, so I simply refuse to study a problem till
> it is retried properly
The executable is running, so clearly the path isn’t an issue. AFAIK,
zypper doesn’t depend on environment variables, which is the major
difference between the two.
> Maybe it is not a problem this time, but it can not be assured.
>
> And, if he used “su” for zypper, he probably did the same for yast, and
> this I know is a problem (the bus messages, for instance, permission
> denied on DISPLAY…).
zypper doesn’t care about the setting of DISPLAY, as it’s a CLI tool. It
runs completely without a GUI at all.
The problems appear to be connectivity related.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
Here are the same commands with su -
linux-cwry:~ # zypper ref
Repository 'mono' is up to date.
Repository 'openSUSE-12.1-Non-Oss' is up to date.
Repository 'openSUSE-12.1-Oss' is up to date.
Repository 'openSUSE-12.1-Update' is up to date.
All repositories have been refreshed.
linux-cwry:~ # zypper lr
# | Alias | Name | Enabled | Refresh
--+------------------------+----------------------------+---------+--------
1 | mono | mono | Yes | No
2 | openSUSE-12.1-12.1-1.4 | openSUSE-12.1-12.1-1.4 | Yes | No
3 | repo-debug | openSUSE-12.1-Debug | No | Yes
4 | repo-debug-update | openSUSE-12.1-Update-Debug | No | Yes
5 | repo-non-oss | openSUSE-12.1-Non-Oss | Yes | Yes
6 | repo-oss | openSUSE-12.1-Oss | Yes | Yes
7 | repo-source | openSUSE-12.1-Source | No | Yes
8 | repo-update | openSUSE-12.1-Update | Yes | Yes
I ran yast from the Gnome desktop and provided the root password.