Just a few days ago, I posted a problem with Yast in KDE. I got around it with this in a console:
First I su to root
then I did this
yast --gtk
Try it.
On 2014-03-24 15:46, linux trojan wrote:
>
> Just a few days ago, I posted a problem with Yast in KDE. I got around
> it with this in a console:
>
> First I su to root
> then I did this
>
> yast --gtk
>
> Try it.
Yes, of course, As there are three yast flavours, namely qt, gtk, and
ncurses, you can try if another one of them works.
But the OP already tried the ncurses version, and it failed (it is
invoked with plain “yast” in a terminal), so in this case it doesn’t help.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
You are absolutely correct. That is what i was referring to. But I see the more complete picture now. Thanks.
Did not want to quote your entire reply, but thank you for the whole thing. It is likely to become a bible. I still feel a bit like a novice driver given the keys(?) to a formula one car - but now I have a pit crew and medical staff standing by 
I think the most biggest single mistake (amongst many) was the mixing versions in my repos. So I’ll be particularly cautious of that. Plus the home and factory repos are clearly intended for others - they will be off-limits.
Thanks to everyone who contributed - must be exasperating to deal with blundering fools, but you were all very kind.
On 2014-03-24 21:46, smcgrother wrote:
> Did not want to quote your entire reply,
Oh, absolutely, I never do 
> but thank you for the whole thing.
Welcome
> It is likely to become a bible. I still feel a bit like a novice
> driver given the keys(?) to a formula one car
I know that feeling
> I think the most biggest single mistake (amongst many) was the mixing
> versions in my repos.
Correct.
> So I’ll be particularly cautious of that. Plus the
> home and factory repos are clearly intended for others - they will be
> off-limits.
I only use a home repo when told to, ie, when I know that particular
repo is intended by its maintainer for other people to use.
> Thanks to everyone who contributed - must be exasperating to deal with
> blundering fools, but you were all very kind.
No, no, don’t worry about that. Typically many of the people that stay
long in the forum is because they want or like to help other people. We
expect newcomers to make mistakes, so we are not put out because of that
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Gentlemen,
I have the same problem as the origin of this thread. Done everything suggested and still YAST does nothing. It opens without problem and then is a sitting duck. Removed FACTORY repo - no change.
But when I try to open # yast2 from a console it opens and console displays the following message:
“Qt Warning - invalid keysym: dead_actute”
libGL error: dlopen /usr/lib/dri/updates/i915_dri.so failed (/usr/lib/dri/updates/i915_dri.so: cannot open shared object file: No such file or directory)
When I click in YAST on any subprogram the console displays:
Run command: /sbin/yast2 sw_single &
and then it is waiting and waiting until YAST is closed.
I am not an expert on computers so any advise will be greatly appreciated, thanks
Removing the repo alone doesn’t do anything.
Run “sudo zypper dup” to switch your system back to 13.1 (or whatever).
But this could cause problems if you have additional repos, so maybe post your repo list first.
But when I try to open # yast2 from a console it opens and console displays the following message:
“Qt Warning - invalid keysym: dead_actute”
libGL error: dlopen /usr/lib/dri/updates/i915_dri.so failed (/usr/lib/dri/updates/i915_dri.so: cannot open shared object file: No such file or directory)
Those are typical warnings from the current Qt5 packages. So this implies you are indeed starting the YaST from Factory.
I installed (!) 13.1 on the same disc that was 12.1 but used clean install with formatting. This is the only problem I have so far.
The repo list is:
| Alias | Name | Enabled | Refresh | Priority | Type | URI | Service
–±--------------------------±-----------------------------------±--------±--------±---------±-------±--------------------------------------------------------------------------±-------
1 | openSUSE-13.1-1.10 | openSUSE-13.1-1.10 | Yes | No | 99 | yast2 | cd:///?devices=/dev/disk/by-id/ata-PHILIPS_CD-RW_DVD-ROM_SCB5265,/dev/sr0 |
2 | repo-debug | openSUSE-13.1-Debug | No | Yes | 99 | NONE | http://download.opensuse.org/debug/distribution/13.1/repo/oss/ |
3 | repo-debug-update | openSUSE-13.1-Update-Debug | No | Yes | 99 | NONE | http://download.opensuse.org/debug/update/13.1/ |
4 | repo-debug-update-non-oss | openSUSE-13.1-Update-Debug-Non-Oss | No | Yes | 99 | NONE | http://download.opensuse.org/debug/update/13.1-non-oss/ |
5 | repo-non-oss | openSUSE-13.1-Non-Oss | Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/13.1/repo/non-oss/ |
6 | repo-oss | openSUSE-13.1-Oss | Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/13.1/repo/oss/ |
7 | repo-source | openSUSE-13.1-Source | No | Yes | 99 | NONE | http://download.opensuse.org/source/distribution/13.1/repo/oss/ |
8 | repo-update | openSUSE-13.1-Update | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/13.1/ |
9 | repo-update-non-oss | openSUSE-13.1-Update-Non-Oss | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/13.1-non-oss/ |
any suggestion?
Yes. Those are just the default repositories, so run this to bring back your system to 13.1:
sudo zypper dup
You might want to disable the first repo, which is the installation medium. Otherwise you may be asked to insert it.
Everything is available from the online repos anyway.
I did as you suggested and got the following answer for zypper dup:
Computing distribution upgrade…
2 Problems:
Problem: icewm-lite-1.2.38-20.1.3.i586 conflicts with icewm-default provided by icewm-default-1.3.7-26.1.4.i586
Problem: patterns-openSUSE-x11_yast-13.1-13.6.1.i586 conflicts with patterns-openSUSE-kde4 provided by patterns-openSUSE-kde4-13.1-13.6.1.i586
Problem: icewm-lite-1.2.38-20.1.3.i586 conflicts with icewm-default provided by icewm-default-1.3.7-26.1.4.i586
Solution 1: deinstallation of icewm-default-1.3.8-1.2.i586
Solution 2: deinstallation of icewm-lite-1.3.8-1.2.i586
Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c] (c):
I am not sure which of the icewm I should deinstall.
On 2014-03-26 23:56, Rodz47 wrote:
>
> I did as you suggested and got the following answer for zypper dup:
>
> Computing distribution upgrade…
Please post the complete computer text, unmodified, and please do so
inside code tags (the ‘#’ button in the forum editor).
See photo
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Sorry if I did something wrong, doing first time.
linux-u25n:/home/Chris # zypper lr --details
| Alias | Name | Enabled | Refresh | Priority | Type | URI | Service
–±--------------------------±-----------------------------------±--------±--------±---------±-------±--------------------------------------------------------------------------±-------
1 | openSUSE-13.1-1.10 | openSUSE-13.1-1.10 | No | No | 99 | yast2 | cd:///?devices=/dev/disk/by-id/ata-PHILIPS_CD-RW_DVD-ROM_SCB5265,/dev/sr0 |
2 | repo-debug | openSUSE-13.1-Debug | No | Yes | 99 | NONE | http://download.opensuse.org/debug/distribution/13.1/repo/oss/ |
3 | repo-debug-update | openSUSE-13.1-Update-Debug | No | Yes | 99 | NONE | http://download.opensuse.org/debug/update/13.1/ |
4 | repo-debug-update-non-oss | openSUSE-13.1-Update-Debug-Non-Oss | No | Yes | 99 | NONE | http://download.opensuse.org/debug/update/13.1-non-oss/ |
5 | repo-non-oss | openSUSE-13.1-Non-Oss | Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/13.1/repo/non-oss/ |
6 | repo-oss | openSUSE-13.1-Oss | Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/13.1/repo/oss/ |
7 | repo-source | openSUSE-13.1-Source | No | Yes | 99 | NONE | http://download.opensuse.org/source/distribution/13.1/repo/oss/ |
8 | repo-update | openSUSE-13.1-Update | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/13.1/ |
9 | repo-update-non-oss | openSUSE-13.1-Update-Non-Oss | Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/13.1-non-oss/ |
linux-u25n:/home/Chris # zypper dup
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See ‘man zypper’ for more information about this command.
Loading repository data…
Reading installed packages…
Computing distribution upgrade…
2 Problems:
Problem: icewm-lite-1.2.38-20.1.3.i586 conflicts with icewm-default provided by icewm-default-1.3.7-26.1.4.i586
Problem: patterns-openSUSE-x11_yast-13.1-13.6.1.i586 conflicts with patterns-openSUSE-kde4 provided by patterns-openSUSE-kde4-13.1-13.6.1.i586Problem: icewm-lite-1.2.38-20.1.3.i586 conflicts with icewm-default provided by icewm-default-1.3.7-26.1.4.i586
Solution 1: deinstallation of icewm-default-1.3.8-1.2.i586
Solution 2: deinstallation of icewm-lite-1.3.8-1.2.i586Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c] (c): c
linux-u25n:/home/Chris #
and another issue that caused the question
linux-u25n:/home/Chris # yast2
“Qt Warning - invalid keysym: dead_actute”
libGL error: dlopen /usr/lib/dri/updates/i915_dri.so failed (/usr/lib/dri/updates/i915_dri.so: cannot open shared object file: No such file or directory)
Run command: /sbin/yast2 sw_single &
linux-u25n:/home/Chris #
This code opens YAST. The run command appears when I click on the Software Management button within YAST and nothing happens in the windows.
My question remains - what to remove and what to replace with if any.
Thanks for your help
Well, if you are not going to use it (and I guess you don’t) then it doesn’t matter really.
I would deinstall icewm-default, since icewm-lite is the smaller package… 
And you would be asked to deinstall a pattern as well. Just do that, a pattern is just a list of packages that should be installed.
Removing the pattern doesn’t remove any actual packages.
On 2014-03-27 04:06, Rodz47 wrote:
>
> Sorry if I did something wrong, doing first time.
No, you are not doing it right, the format is distorted and difficult to
read.
Simply create a code tag block, and inside paste the entire text from
the terminal, including the command prompt, the answer, and the next
command prompt, all in a single mouse sweep.
Like this:
Telcontar:~ # zypper dummy
Unknown command 'dummy'
Type 'zypper help' to get a list of global options and commands.
Telcontar:~ #
So you get:
> Solution 1: deinstallation of icewm-default-1.3.8-1.2.i586
> Solution 2: deinstallation of icewm-lite-1.3.8-1.2.i586
>
> Choose from above solutions by number or skip, retry or cancel [1/2/s/r/c] (c): c
> linux-u25n:/home/Chris #
It does not matter much which one you choose. try one or the other to
see if they give another conflict. If it gives a lot, abort, and choose
the other.
Unless you really have a preference for one or the other package…
I had the same conflict while recently upgrading a machine. I think I
choose to keep the light version, but I don’t remember.
I suggest you do the “zypper dup” in a text console in text mode. If the
graphical session crashes because of the many upgrades, you will be in
trouble. Or use tmux.
http://en.opensuse.org/SDB:System_upgrade
> and another issue that caused the question
wolfi323 already answered this.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
I did as you suggested and
- after deinstalled the files I was told that they have to be replaced so I run zypper dup
-after zypper dup some of the files were removed and replaced with the older versions. When the process was finished I checked and YAST was working but my gnuCash was not working properly. I reinstalled it and then the whole hell broke loose. The system downloaded the FACTORY again together with some 1800 files. When the process was finished the gnuCash was working but YAST didn’t open at all
I got this message:
linux-u25n:/home/Chris # yast2
/usr/lib/YaST2/bin/y2controlcenter: symbol lookup error: /usr/lib/libQt5Widgets.so.5: undefined symbol: _ZN24QAbstractDeclarativeData14destroyed_qml1E
linux-u25n:/home/Chris #
Pleae note that my first installation was from a DVD i made with ISO downloaded from openSUSE web page. The corrections were downloaded directly for installation. Any further suggestions?
On 2014-03-28 02:16, Rodz47 wrote:
> -after zypper dup some of the files were removed and replaced with the
> older versions. When the process was finished I checked and YAST was
> working but my gnuCash was not working properly. I reinstalled it and
> then the whole hell broke loose. The system downloaded the FACTORY again
Why did you add the factory repo again?
Remove the factory repo, and repeat the “zypper dup” to remove any
factory packages installed.
And then tell us why are you adding that factory repo, as previously.
And how the **** you are installing that gnucash.
> Pleae note that my first installation was from a DVD i made with ISO
> downloaded from openSUSE web page.
Which one exactly? There are several.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)