Thanks, my first statement was about you using lots of upercase characters where this is not needed. But it seems to be better now.
My last statementy was about putting computer text between CODE tags. You didn’t. As consequence the lay-out is cluttered and the URLs in the listing are resolved to their titles and act as links.
Look at mine (not the repos I have, but how I report it):
henk@boven:~> zypper lr -d
# | Alias | Naam | Ingeschakeld | Vernieuwen | Prioriteit | Type | URI | Service
---+--------------------------------------------------------------------------+--------------------------------------------------------------------------+--------------+------------+------------+--------+------------------------------------------------------------------------------------+--------
1 | KDE_Backports | KDE Backports | Ja | Ja | 99 | rpm-md | http://download.opensuse.org/repositories/KDE:/Backports/openSUSE_11.2 |
2 | KDE_Stable | KDE Stable | Ja | Ja | 99 | rpm-md | http://download.opensuse.org/repositories/KDE:/KDE4:/STABLE:/Desktop/openSUSE_11.2 |
3 | Kernel_ | Kernel | Nee | Ja | 99 | rpm-md | http://download.opensuse.org/repositories/Kernel:/HEAD/openSUSE_11.2/ |
4 | download.nvidia.com-opensuse | NVIDIA Repository | Nee | Ja | 98 | rpm-md | ftp://download.nvidia.com/opensuse/11.2/ |
5 | download.videolan.org-SuSE | VideoLan Repository | Nee | Ja | 99 | rpm-md | http://download.videolan.org/pub/videolan/vlc/SuSE/11.2/ |
6 | http-download.opensuse.org-ee3cb2f9 | Updates for openSUSE 11.2-0 | Ja | Ja | 99 | rpm-md | http://download.opensuse.org/update/11.2/ |
7 | http://download.opensuse.org/repositories/Application:/Geo/openSUSE_11.2 | http://download.opensuse.org/repositories/Application:/Geo/openSUSE_11.2 | Nee | Ja | 99 | rpm-md | http://download.opensuse.org/repositories/Application:/Geo/openSUSE_11.2 |
8 | openSUSE 11.2-0 | openSUSE 11.2-0 | Nee | Nee | 99 | yast2 | cd:/// |
9 | packman.inode.at-suse | Packman Repository | Ja | Ja | 99 | rpm-md | http://packman.inode.at/suse/11.2/ |
10 | repo-debug | openSUSE-11.2-Debug | Nee | Ja | 99 | NONE | http://download.opensuse.org/debug/distribution/11.2/repo/oss/ |
11 | repo-non-oss | openSUSE-11.2-Non-Oss | Ja | Ja | 99 | yast2 | http://download.opensuse.org/distribution/11.2/repo/non-oss/ |
12 | repo-oss | openSUSE-11.2-Oss | Ja | Ja | 99 | yast2 | http://download.opensuse.org/distribution/11.2/repo/oss/ |
13 | repo-source | openSUSE-11.2-Source | Nee | Ja | 99 | NONE | http://download.opensuse.org/source/distribution/11.2/repo/oss/ |
henk@boven:~>
In any case you seem to have Gnome:Stable two times. That is a bit overdone. I do not know if this is why you have the error, but remove one of them.
And then try (as root)
zypper ref
zypper up
to catch the error in text mode. Copy that piece of information and post it here (between CODE tags ), so we can see an unspoiled error message.
, which I followed recently. Would any of the changes made because of this be the reason why I have Gnome: Stable twice?
If it is still possible to delete one of these, could you please walk me through the procedure for doing so? Thanks.
Well, reading it you will see yourself that you had allready the two duplicates there. And Carl tried to remove one with his second zypper command, but the - sign there is a typo, thus it did not work (and you did not repoert the error, I bet it said: Unknown option ‘1’).
You could do better with
zypper rr 2
(I choose 2 because that is the one with the _1 in the name and thus the stranger, but you could so also do a 1 there).
But I suggest you now use the YaST way, only to get a taste of how YaST interfaces to zypper (it is only a GUI to zypper when managing software repos and software installs/removals).
It is not that interesting how you got two of the same. We just want to remove one of them (I would say the second one with the _1 at the end).
Yast > Software > Repository management. Select the one and click the delete/remove button. Finish. That is all. YaST is a miracle.
Henk,
As ever, none of this is quite that simple for poor old me.
I went to Repository management and there are indeed two entries for Gnome:Stable. However the one with the minus isn’t obvious. There is only one difference between the two entries: one has Autorefresh ticked and the other doesn’t. So which should I delete?
According to your own listing, one has an alias (short name) of Gnome:Stable and the thert is Gnome:Stable_1. (_ is called underscore, - is called minus sign).
As said earlier, they are the same, but remove the one without the Autorefresh, else we have to switch the Autorefresh on for the other :). The one that stays should have both Enabled and Autorefresh on (btw that is NOT true for all of the others! Leave them as they are).
Henk,
I did what you said.
I then asked YAST to automatically update and received a message saying that there are some conflicts that need manually resolving.
I can’t copy and paste the text, because of needing to select one of two options: to either install something else or not.
The conflict is as follows:
patch:libfreebl 3-2258.noarch confliects with libfreebl3-32bit.x86_64<3.12.6-3.1.1 provided by libfreebl3-32bit_3.12.6-2.pm6.2.X86_64
I’m sorry but I don’t know what CODE tags are, never having ever used them!
I would be happy to oblige if you explain how.
In the meantime, this is the feedback you asked for first:
| Alias | Name | Enabled | Refresh | Priority | Type | URI | Service
About the CODE tags, I explained that in post #4 above. Complete with example, also all my asking for executing a command are between them.
This is between CODE:
code tags
and this a QUOTE:
Quote
This is bold, italic and underlined.
I all made them by selecting that piece of text (moving the mouse with the left key down from start to finish and then release the key, you will see it highlighted). Then you click the appropriate button in the toolbar above the input field. The # is for CODE (hover over it and it will tell you).
Henk,
Normally a red star appears in the tray at the bottom and prompts me to install patches, so I just click on them and go.
However, I went into YAST and asked it to upgrade security and got the response I mentioned in post 9 above. There appears to be a conflict somewhere. Any thoughts?
My applet is either a green “ball”, or an orange star or a red triangle. Never saw a red star.
And please do use more detail: " I went into YAST and asked it to upgrade security". When I start YaST, there is no item “upgrade security” in the left panel and also not in the right panel when I first choose “Software”.
When the applet is red/orange of whatever scape and you try to use it, do you get the problem there?
You’re right, I think it is an orange rather than a red star; whatever the colour, that is what I usually click on for updates and there has never been a problem before.
In Yast, there is an Online Update option, which I used; this generates the problem message mentioned earlier.
I hardly ever go into Yast, but when I do, this error message is displayed in a separate box:
/usr/share/themes/Synchronicity/gtk-2.0/gtkrc:46: Clearlooks configuration option “menuitemstyle” is not supported and will be ignored.
/usr/share/themes/Synchronicity/gtk-2.0/gtkrc:47: Clearlooks configuration option “listviewitemstyle” is not supported and will be ignored.
/usr/share/themes/Synchronicity/gtk-2.0/gtkrc:48: Clearlooks configuration option “progressbarstyle” is not supported and will be ignored.
/usr/share/themes/Synchronicity/gtk-2.0/gtkrc:46: Clearlooks configuration option “menuitemstyle” is not supported and will be ignored.
/usr/share/themes/Synchronicity/gtk-2.0/gtkrc:47: Clearlooks configuration option “listviewitemstyle” is not supported and will be ignored.
/usr/share/themes/Synchronicity/gtk-2.0/gtkrc:48: Clearlooks configuration option “progressbarstyle” is not supported and will be ignored.
To be honest, I only ever click on the orange star. The only exception to that was when one of the guys on the forum helped me to adapt 32 bit Brother drivers for a 64-bit computer (I think I have that right!), which involved a lot of aggro. Other than that, I change nothing, which is how I like it!
It looks to me that the recent changes to Banshee and the downloading of VLC, which I mention in one of the earlier posts (including link) was the culprit. Previously, everything appeared to work fine and all orange star updates worked perfectly.