Yast error!

English Applications
#1

Hi everyone, long time ubuntu user here, just moved to opensuse 11.1

recently I updated a bunch of packages and now yast is giving me this error when i try and run anything from its “control panel”:

terminate called after throwing an instance of 'YUIPluginException'
  what():  Couldn't load plug-in gtk
YaST got signal 6 at YCP file Wizard.ycp:691
/sbin/yast2: line 437:  4882 Aborted                 $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS

also deluge and gparted are giving strange error messages:

gparted:

(gpartedbin:4207): Gtk-WARNING **: cannot open display:

deluge:

[ERROR   ] 16:49:30 ui:65 Unable to find the requested UI: gtk.  Please select a different UI with the '-u' option or alternatively use the '-s' option to select a different default UI.
Traceback (most recent call last):
  File "/usr/bin/deluge", line 8, in <module>
    load_entry_point('deluge==1.1.0', 'console_scripts', 'deluge')()
  File "/usr/lib64/python2.6/site-packages/deluge/main.py", line 123, in start_ui
    UI(options, args, options.args)
  File "/usr/lib64/python2.6/site-packages/deluge/ui/ui.py", line 66, in __init__
    sys.exit(0)
NameError: global name 'sys' is not defined
#2

you didn’t happen to add a bunch of repos, did you??

see a section in http://tinyurl.com/6jwtg9 on repository management,
also see the howto at http://tinyurl.com/d36dml

welcome to openSUSE, some feel it is advanced from Ubuntu, some
not…it IS different in several ways…you can get a feel here:
http://en.opensuse.org/Concepts

–
goldie

#3

I did, in Ubuntu it seemed I could add repo’s constantly, here’s what I’ve got:

#  | Alias                    | Name                                                | Enabled | Refresh
---+--------------------------+-----------------------------------------------------+---------+--------
1  | GNOME:Factory            | GNOME:Factory                                       | Yes     | Yes    
2  | IPList                   | IPList                                              | No      | No     
3  | KDE:KDE4:Factory:Desktop | KDE:KDE4:Factory:Desktop                            | Yes     | Yes    
4  | Libdvdcss repository     | Libdvdcss repository                                | Yes     | Yes    
5  | Linux-PAM                | Linux-PAM                                           | Yes     | Yes    
6  | X11:XGL                  | X11:XGL                                             | Yes     | No     
7  | devel:tools:building     | devel:tools:building                                | Yes     | Yes    
8  | openSUSE-11.1-Updates    | openSUSE-11.1-Updates                               | Yes     | Yes    
9  | repo                     | NVIDIA Repository                                   | Yes     | Yes    
10 | repo-debug               | openSUSE-11.1-Debug                                 | Yes     | Yes    
11 | repo-non-oss             | openSUSE-11.1-Non-Oss                               | Yes     | No     
12 | repo-oss                 | openSUSE-11.1-Oss                                   | Yes     | No     
13 | repo-source              | openSUSE-11.1-Source                                | Yes     | Yes    
14 | repo-update              | openSUSE-11.1-Update                                | Yes     | No     
15 | repo_1                   | openSUSE BuildService - OpenOffice.org              | Yes     | Yes    
16 | repo_2                   | openSUSE BuildService - Virtualization (QEMU)       | No      | Yes    
17 | repo_3                   | openSUSE BuildService - Virtualization (VirtualBox) | Yes     | Yes    
18 | repo_4                   | openSUSE BuildService - X11:Compiz                  | Yes     | Yes    
19 | repo_5                   | openSUSE BuildService - Drivers for webcams         | Yes     | Yes    
20 | repo_6                   | openSUSE BuildService - Mozilla                     | Yes     | Yes    
21 | repo_7                   | Main Update Repository                              | Yes     | Yes    
22 | repo_8                   | VideoLan Repository                                 | Yes     | Yes    
23 | repo_9                   | Packman Repository                                  | Yes     | Yes

Any advice on these?

#4

Any advice on these?

Yes:

“Way too many”

#5

haha, so which ones should I remove? and how can this fix the yast problem?

#6

> Any advice on these?

yep, i advise you that to correct all the errors and conflicts you
have likely introduced into your new install, i highly suggest you
consider a new install…another way to say that is: i have NO idea
how to even begin to figure out how to undo all that has been done…

if it were my machine (it is, obviously NOT my machine, so you do as
you wish) i would save all the ‘stuff’ on that hard drive that you
created or downloaded and want to keep (documents, emails, music,
photos, video, etc etc etc) to a SAFE location (i’d define safe here
as: somewhere else, on a different machine that can’t be touched by an
openSUSE install on the machine to be reinstalled on) and then do a
NEW install…wiping out ALL previous programs, setting and data…

then my best advice is to USE the system as born for a while without
making ANY changes until AFTER you have done enough reading to know
how to correctly make the changes…

you can start learning with

http://tinyurl.com/6jwtg9

and ALL its embedded links to other important stuff for folks new to
openSUSE…

it is my opinion that this is the BEST method of time management in
the field of computer administration…i mean, how long does it take
to read: “initially set up only 4 repositories (repos). Just 4. No
others.” i guess 5 seconds! now compare that to the time it will take
you to correct all the damage done…

some folk like to learn by doing…personally i think that is second
best way in lots of things we humans do…like: how should learn how
to die?

–
goldie
Give a hacker a fish and you feed him for a day.
Teach reading and you feed him for a lifetime.

#7

Hmm, thanks for the reply, I really didn’t want to reinstall, it took me forever to get everything set up properly, I was hoping for a quick and easy fix :frowning:

#8

Just a point on this- isn’t the package manager supposed to check for conflicts, dependencies etc and resolve them?

#9

All except

8

11

12

and

23

Then a complete “zypper dup” which will result in a lot of traffic and very likely also a lot of downgrades (and praying that you didn’t break too much stuff with your “kamikaze-list” before) which cannot be fixed.

The odd thing about package managers is, they know very well to handle upgrades but not downgrades.

You ask why?

Very simple, if you have an upgrade, you know the version it will be upgraded from before you build the package for the new version and newer packages are built to change configs to the syntax/dependencies of the new version.

This does not necessarily work the other way around, because how should older package versions know how (and from which newer configs which probably didn’t exist, when they were built) they should do any necessary changes?

Less possibilities for you to break things that work until you really know what you are doing when adding new repos.

#10

OK, one more can/should be left:

9  | repo                     | NVIDIA Repository
#11

> Just a point on this- isn’t the package manager supposed to check for
> conflicts, dependencies etc and resolve them?

yep, and it does pretty good job until the user ignores written
advice and official documentation by giving YaST permission to
download the same program (but different versions [one newer than the
other]) from two or more sources, at the same time…

it is just better to following the written word…

–
goldie

#12

Akoellh wrote:

> Yes:
>
> “Way too many”
>
Nonsense, how do you figure that?
Yast breaks after x number of added repo’s?

I don’t see any repository that should break yast, accept the factory repo’s
because they contain newer yast packages.

Only unnessesary repo i see is the libdvdcss or videolan repo, both contain
libdvdcss.

The rest seems fine to me.

Chris Maaskant

#13

> Nonsense, how do you figure that?
> Yast breaks after x number of added repo’s?

breaking YaST is not the issue…

breaking individual applications and/or the entire system is the
issue…(as far as i know YaST will happily continue corrupting your
system for a quite long time if you tell it to, by enabling repos
which should be used carefully and for limited purposes only)…

routinely installing updates from sources in addition to those four
basic ones noted via links in my first post in this thread has often
proven to cause varied problems in stability and/or usability…

these fora are replete with examples…i suggest you read a few and
get back to us…

–
goldie
Give a hacker a fish and you feed him for a day.
Teach reading and you feed him for a lifetime.

#14

goldie wrote:

> breaking individual applications and/or the entire system is the
> issue…(as far as i know YaST will happily continue corrupting your
> system for a quite long time if you tell it to, by enabling repos
> which should be used carefully and for limited purposes only)…

Exactly, it is the user that breaks the system!
The user adds repo’s that are clearly stated as unstable and then
complains that something is broken.
You must indeed be careful in what you add to your system.

Just like Teggun.
He has factory repo’s installed for gnome and kde.
And they have packages for yast,qt and gtk.
All pretty important packages if you ask me.
Installing important packages like that from 2 unstable repo’s is bound to
break something.
>
> these fora are replete with examples…i suggest you read a few and
> get back to us…
>
I read this forum and related newsgroups regularly.
And i often read somebody giving a newbie advice to install a factory repo
to get the latest bling for kde4, and that it is no problem because he or
she doesn’t have a problem with it.

And then there are the one-click installs.
Also a recipe for disaster.
You want package x installed, so you click on the one-click button for that
package, you get the package plus a repository with all kinds of stuff you
don’t need/want which could replace things from the official repo’s at the
next update.
I’m not sure if the repository gets added by default anymore because i don’t
use one-click.

But even if it doesn’t gets added it is still no good.
Because package x might depends on stuff from the other repo’s that does get
updated all the time and package x does not.

I have 18 unofficial repo’s added to the system but i take a good look at
what gets installed and that keeps me out of trouble.

–
Chris Maaskant

#15

By actually looking at them, which you certainly did not!

Otherwise you would have seen what’s wrong with that set.

a) Doubled repos (the Update-repo appears three times) which often cause yast to get into trouble

b) Packman and Videolan which often cause conflicts, libdvdcss is also active, so there is also a double coverage with Videolan, although in that case not very likely to break something).

c) completely unnecessary Repos for normal users like debug ans source, or do you think the TS is a developer?

BTW:

I have nearly 30 Repos active, but none of them are doubled or conflicting with each other.

And the Factory Repos are most certainly the candidates for breaking YaST GUI (mainly qt-interface, Im’pretty sure ncurses will still work, GTK maybe also).

Still thinking it was “Non sense”?

#16

Akoellh wrote:

>
> a) Doubled repos (the Update-repo appears three times) which often
> cause yast to get into trouble

Yes i missed that one, but that shouldn’t break anything.
>
> b) Packman and Videolan which often cause conflicts,

Not if you set the priorities right.

> libdvdcss is also active, so there is also a double coverage with Videolan

I know, that’s what i said.
>
> c) completely unnecessary Repos for normal users like debug ans source,
> or do you think the TS is a developer?

How should i know?
>
> And the Factory Repos are most certainly the candidates for breaking
> YaST GUI

I know, that’s what i said.
>
> Still thinking it was “Non sense”?
>
Yes, because you didn’t make any sense by just saying “Way too many”
As if the number of repositories has anything to do with the error yast
gives.

–
Chris Maaskant

#17

Oh it does, especially if the doubled repos were not fetched from the same server and consequently are not always in sync.

>
> b) Packman and Videolan which often cause conflicts,

Not if you set the priorities right.

Which has to be done by the user explicitely and nearly no new user is doing that.

Also all packages in Videolan except libdvdcss are available with packman and packman contains a lot more packages than Videolan, so there is no reason especially for a new user to add Videolan at all.

> libdvdcss is also active, so there is also a double coverage with Videolan

I know, that’s what i said.
>

The only thing you said in your “non sense” posting, where you also stated verything else “looked fine to you”.

> c) completely unnecessary Repos for normal users like debug ans source,
> or do you think the TS is a developer?

How should i know?

Yeah, of course, the obvious level of excperience the TS shows makes it very likely he is developping/debugging software for openSUSE, no doubt about it …

>
> And the Factory Repos are most certainly the candidates for breaking
> YaST GUI

I know, that’s what i said.

Not in your “Non sense” post.

Yes, because you didn’t make any sense by just saying “Way too many”
As if the number of repositories has anything to do with the error yast
gives.

Yeah, of course it is “non sense” to perhaps giving only a little hint first, so the TS might perhaps (as rarely as it happens though) have a look and think for himself (no, he didn’t, I know) about his own list (for the first time possibly) and noticing at least the tripled update repo.

But I think that’s my problem, still having the idea that even new users can/should be trained to think for them selves.

#18

> I have 18 unofficial repo’s added to the system but i take a good look at
> what gets installed and that keeps me out of trouble.

we agree…

you are obviously not blindly allowing YaST to install whatever pops
up in all your 18 repos…which ought to work ok…but, there are
folks here unlike you that enable whatever they want and then never
look to see see what the openSUSE Updaters is wanting to
update…which is, of course, a recipe for disaster…

–
goldie

#19

Akoellh wrote:

>> Yes i missed that one, but that shouldn’t break anything.
>
> Oh it does, especially if the doubled repos were not fetched from the
> same server and consequently are not always in sync.
>
If some dependency for a package isn’t there, the package will not be
installed, nothing breaks.
>
>> > libdvdcss is also active, so there is also a double coverage with
>> Videolan
>>
>> I know, that’s what i said.
>> >
>
> The only thing you said in your “non sense” posting, where you also
> stated verything else “looked fine to you”.

Well at least i said something that made sense.
>
>
>> How should i know?
>
> Yeah, of course, the obvious level of excperience the TS shows makes it
> very likely he is developping/debugging software for openSUSE, no
> doubt about it …

You asume a lot, i know only what i read.
And what does it matter anyway. debug and source repo’s cause yast to break?

>> > And the Factory Repos are most certainly the candidates for breaking
>> > YaST GUI
>>
>> I know, that’s what i said.[7quote9
>>
>> Not in your “Non sense” post.
>>[/color]
Learn to read.
I said: “I don’t see any repository that should break yast, accept the
factory repo’s
because they contain newer yast packages.”

>> But I think that’s my problem, still having the idea that even new
>> users should be trained to think for them selves.
>
By giving useless answers?
Yast give an error, ah you have too many repo’s, remove some, doesn’t matter
wich one, just remove something, that should fix it!

–
Chris Maaskant

#20

goldie wrote:

> we agree…

We do :slight_smile:

> you are obviously not blindly allowing YaST to install whatever pops
> up in all your 18 repos…which ought to work ok…but, there are
> folks here unlike you that enable whatever they want and then never
> look to see see what the openSUSE Updaters is wanting to
> update…which is, of course, a recipe for disaster…
>
Indeed, that’s why i pointed out to Teggun that the factory repo’s are
probably the cause of the yast error.

–
Chris Maaskant