@ Sauerland
Nee hat leider nicht geholfen. Die Progs laufen immer noch nicht.
Gibt es ein befehl der alles aufräumt?
@ Sauerland
Nee hat leider nicht geholfen. Die Progs laufen immer noch nicht.
Gibt es ein befehl der alles aufräumt?
Und nun? Hat leider nicht geholfen. Was hat nicht geholfen? Was hast du eingegeben? Wo? Mit welchem Ergebniss? Welche Meldung hat die Konsole dazu geliefert? Welche Progs? Meinst du, hier hat einer Bock auf Rätselraten? Und die Glaskugeln sind auch alle kaputt.
Mach dir das neu und lass die Finger von Einklickern!!!
Alles anzeigenmach es als root (su -l nicht sudo) per zypper:
Danach:
Und discover ist eh fehleranfällig, würde ich nicht benutzen, lieber zypper oder yast.....
Wobei yast auch noch als ncurses Version funktionieren sollte........
Ich habe alles gemacht was Ihr gesagt, geschrieben, habt. Die Repositories entfernt, und "zypper dup --allow-vendor-change" ausgeführt und "be- abgearbeitet. Dann das OS neu gestartet die updates instaliert und ...
... viel Programme laufen als X immer noch nicht.
Ich habe auch einige Programme erst deinstalliert und dann wieder installiert. ... viel Programme laufen als X immer noch nicht.
Hat noch jemand eine neue Idee?
Alles anzeigenUnd nun? Hat leider nicht geholfen. Was hat nicht geholfen? Was hast du eingegeben? Wo? Mit welchem Ergebniss? Welche Meldung hat die Konsole dazu geliefert? Welche Progs? Meinst du, hier hat einer Bock auf Rätselraten? Und die Glaskugeln sind auch alle kaputt.
Mach dir das neu und lass die Finger von Einklickern!!!
@Alero alles wie etwas weiter oben gemacht. Was gibt es da zu raten? Ihr schreibt mach es so... und ich mache es so. Ist doch einleuchten oder nicht?
[wenn mir jemand sagt deinstalliere app 1 und installiere app2 dann ist doch klar was ich machen?!! ]
Wenn du in der Konsole etwas durchführst, was wir geraten haben, dann erwarten wir, das du die Eingabe in der Konsole sowie die Ausgabe der Konsole hier postest. Geht nicht hilft nicht. Und "die Progs laufen immer noch nicht" ist keine Fehlermeldung des entsprechenden Programmes. Wenn sich ein Programm nicht starten läßt, dann ruft man die Konsole auf, startet das Programm in der Konsole und postet die Eingabe inkl. der Fehlermeldung. Funktioniert das immer noch nicht, startet man das Programm als Root in der Konsole und postet ... weißt schon, siehe oben. Was kapierst du daran nicht???
zypper lr -d
Repository priorities are without effect. All enabled repositories share the same priority.
# | Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service
---+-------------------------------------+-----------------------------------------+---------+-----------+---------+----------+--------+--------------------------------------------------------------------------+--------
1 | http-download.opensuse.org-42093fc6 | openSUSE:Factory | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/tumbleweed/repo/oss/ |
2 | repo-debug | openSUSE-Leap-15.0-Debug | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/debug/distribution/leap/15.0/repo/oss/ |
3 | repo-debug-non-oss | openSUSE-Leap-15.0-Debug-Non-Oss | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/debug/distribution/leap/15.0/repo/non-oss/ |
4 | repo-debug-update | openSUSE-Leap-15.0-Update-Debug | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/debug/update/leap/15.0/oss/ |
5 | repo-debug-update-non-oss | openSUSE-Leap-15.0-Update-Debug-Non-Oss | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/debug/update/leap/15.0/non-oss/ |
6 | repo-non-oss | openSUSE-Leap-15.0-Non-Oss | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/distribution/leap/15.0/repo/non-oss/ |
7 | repo-source | openSUSE-Leap-15.0-Source | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/source/distribution/leap/15.0/repo/oss/ |
8 | repo-source-non-oss | openSUSE-Leap-15.0-Source-Non-Oss | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/source/distribution/leap/15.0/repo/non-oss/ |
9 | repo-update | openSUSE-Leap-15.0-Update | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/15.0/oss/ |
10 | repo-update-non-oss | openSUSE-Leap-15.0-Update-Non-Oss | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/15.0/non-oss/ |
Alles anzeigen
zypper dup --allow-vendor-change
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: ruby2.5-rubygem-cfa_grub2-1.0.1-lp150.2.3.1.x86_64 requires ruby(abi) = 2.5.0, but this requirement cannot be provided
Problem: PackageKit-1.1.10-lp150.8.1.x86_64 requires PackageKit-branding = 1.1.10, but this requirement cannot be provided
Problem: ruby2.5-rubygem-cfa_grub2-1.0.1-lp150.2.3.1.x86_64 requires ruby(abi) = 2.5.0, but this requirement cannot be provided
deleted providers: ruby2.5-2.5.0-lp150.2.11.x86_64
Solution 1: Following actions will be done:
deinstallation of ruby-2.5-lp150.1.5.x86_64
deinstallation of yast2-services-manager-4.0.10-lp150.7.1.noarch
deinstallation of autoyast2-installation-4.0.69-lp150.2.19.1.noarch
deinstallation of yast2-add-on-4.1.12-1.3.noarch
deinstallation of yast2-apparmor-4.1.7-1.3.noarch
deinstallation of yast2-auth-client-4.1.1-1.3.noarch
deinstallation of yast2-auth-server-4.1.0-1.4.noarch
deinstallation of yast2-firewall-4.0.34-lp150.7.1.noarch
deinstallation of yast2-installation-4.0.74-lp150.2.15.1.noarch
deinstallation of yast2-iscsi-client-4.0.2-lp150.2.3.1.noarch
deinstallation of yast2-journal-4.2.0-1.3.noarch
deinstallation of yast2-mail-4.1.0-1.4.noarch
deinstallation of yast2-metapackage-handler-4.1.0-1.3.noarch
deinstallation of yast2-nfs-client-4.1.5-1.3.noarch
deinstallation of yast2-online-update-4.1.0-1.3.noarch
deinstallation of yast2-pam-4.2.3-1.3.noarch
deinstallation of yast2-proxy-4.1.0-1.3.noarch
deinstallation of yast2-samba-server-4.0.2-lp150.2.3.1.noarch
deinstallation of yast2-security-4.0.1-lp150.2.6.1.noarch
deinstallation of yast2-sudo-4.1.0-1.3.noarch
deinstallation of yast2-support-4.1.1-1.2.noarch
deinstallation of yast2-sysconfig-4.0.1-lp150.2.3.1.noarch
deinstallation of yast2-vpn-4.1.0-1.3.noarch
deinstallation of yast2-online-update-frontend-4.1.0-1.3.noarch
Solution 2: deinstallation of ruby2.5-rubygem-cfa_grub2-1.0.1-lp150.2.3.1.x86_64
Solution 3: keep obsolete ruby-2.5-lp150.1.5.x86_64
Solution 4: break ruby2.5-rubygem-cfa_grub2-1.0.1-lp150.2.3.1.x86_64 by ignoring some of its dependencies
Choose from above solutions by number or skip, retry or cancel [1/2/3/4/s/r/c] (c):
Alles anzeigen
Choose from above solutions by number or skip, retry or cancel [1/2/3/4/s/r/c] (c): r
Resolving dependencies...
Computing distribution upgrade...
7 Problems:
Problem: patterns-yast-yast2_basis-20190411-1.3.x86_64 requires yast2-firewall, but this requirement cannot be provided
Problem: yast2-nis-client-4.1.1-1.3.x86_64 requires yast2-pam, but this requirement cannot be provided
Problem: yast2-ruby-bindings-4.2.1-1.3.x86_64 requires ruby, but this requirement cannot be provided
Problem: yast2-update-4.0.18-lp150.2.6.1.x86_64 requires yast2-installation, but this requirement cannot be provided
Problem: yast2-users-4.0.11-lp150.2.10.1.x86_64 requires yast2-security, but this requirement cannot be provided
Problem: yast2-network-4.0.48-lp150.2.16.1.noarch requires yast2-proxy, but this requirement cannot be provided
Problem: ruby2.5-rubygem-cfa_grub2-1.0.1-lp150.2.3.1.x86_64 requires ruby(abi) = 2.5.0, but this requirement cannot be provided
Problem: patterns-yast-yast2_basis-20190411-1.3.x86_64 requires yast2-firewall, but this requirement cannot be provided
not installable providers: yast2-firewall-4.2.0-1.3.noarch[http-download.opensuse.org-42093fc6]
yast2-firewall-4.0.26-lp150.2.3.1.noarch[repo-update]
Solution 1: Following actions will be done:
keep yast2-firewall-4.0.34-lp150.7.1.noarch
keep yast2-mail-4.1.0-1.4.noarch
keep yast2-online-update-4.1.0-1.3.noarch
keep yast2-online-update-frontend-4.1.0-1.3.noarch
keep yast2-services-manager-4.0.10-lp150.7.1.noarch
keep yast2-sysconfig-4.0.1-lp150.2.3.1.noarch
Solution 2: Following actions will be done:
keep yast2-mail-4.1.0-1.4.noarch
keep yast2-online-update-4.1.0-1.3.noarch
keep yast2-online-update-frontend-4.1.0-1.3.noarch
keep yast2-services-manager-4.0.10-lp150.7.1.noarch
keep yast2-sysconfig-4.0.1-lp150.2.3.1.noarch
Solution 3: deinstallation of patterns-yast-yast2_basis-20180409-lp150.3.1.x86_64
Solution 4: break patterns-yast-yast2_basis-20190411-1.3.x86_64 by ignoring some of its dependencies
Choose from above solutions by number or skip, retry or cancel [1/2/3/4/s/r/c] (c): 2
Problem: yast2-nis-client-4.1.1-1.3.x86_64 requires yast2-pam, but this requirement cannot be provided
Solution 1: deinstallation of yast2-nis-client-4.1.1-1.3.x86_64
Solution 2: keep yast2-pam-4.2.3-1.3.noarch
Solution 3: break yast2-nis-client-4.1.1-1.3.x86_64 by ignoring some of its dependencies
Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c] (c): 1
Problem: yast2-ruby-bindings-4.2.1-1.3.x86_64 requires ruby, but this requirement cannot be provided
deleted providers: ruby-2.5-lp150.1.5.x86_64
not installable providers: ruby-2.6-1.3.i586[http-download.opensuse.org-42093fc6]
ruby-2.6-1.3.x86_64[http-download.opensuse.org-42093fc6]
Solution 1: deinstallation of yast2-ruby-bindings-4.0.6-lp150.1.1.x86_64
Solution 2: keep ruby-2.5-lp150.1.5.x86_64
Solution 3: break yast2-ruby-bindings-4.2.1-1.3.x86_64 by ignoring some of its dependencies
Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c] (c): 1
Problem: yast2-update-4.0.18-lp150.2.6.1.x86_64 requires yast2-installation, but this requirement cannot be provided
not installable providers: yast2-installation-4.2.4-1.3.noarch[http-download.opensuse.org-42093fc6]
yast2-installation-4.0.60-lp150.2.3.1.noarch[repo-update]
yast2-installation-4.0.63-lp150.2.6.1.noarch[repo-update]
yast2-installation-4.0.67-lp150.2.9.1.noarch[repo-update]
yast2-installation-4.0.70-lp150.2.12.1.noarch[repo-update]
Solution 1: deinstallation of yast2-update-4.0.18-lp150.2.6.1.x86_64
Solution 2: keep yast2-installation-4.0.74-lp150.2.15.1.noarch
Solution 3: break yast2-update-4.0.18-lp150.2.6.1.x86_64 by ignoring some of its dependencies
Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c] (c): 1
Problem: yast2-users-4.0.11-lp150.2.10.1.x86_64 requires yast2-security, but this requirement cannot be provided
not installable providers: yast2-security-4.1.2-1.4.noarch[http-download.opensuse.org-42093fc6]
yast2-security-4.0.1-lp150.2.3.1.noarch[repo-update]
Solution 1: deinstallation of yast2-users-4.0.11-lp150.2.10.1.x86_64
Solution 2: keep yast2-security-4.0.1-lp150.2.6.1.noarch
Solution 3: break yast2-users-4.0.11-lp150.2.10.1.x86_64 by ignoring some of its dependencies
Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c] (c): 1
Problem: yast2-network-4.0.48-lp150.2.16.1.noarch requires yast2-proxy, but this requirement cannot be provided
not installable providers: yast2-proxy-4.0.1-lp150.2.3.1.noarch[repo-update]
yast2-proxy-4.0.2-lp150.2.6.1.noarch[repo-update]
Solution 1: deinstallation of yast2-network-4.0.48-lp150.2.16.1.noarch
Solution 2: keep yast2-proxy-4.1.0-1.3.noarch
Solution 3: break yast2-network-4.0.48-lp150.2.16.1.noarch by ignoring some of its dependencies
Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c] (c): 1
Problem: ruby2.5-rubygem-cfa_grub2-1.0.1-lp150.2.3.1.x86_64 requires ruby(abi) = 2.5.0, but this requirement cannot be provided
deleted providers: ruby2.5-2.5.0-lp150.2.11.x86_64
Solution 1: deinstallation of ruby2.5-rubygem-cfa_grub2-1.0.1-lp150.2.3.1.x86_64
Solution 2: deinstallation of yast2-ntp-client-4.0.12-lp150.1.1.noarch
Solution 3: keep obsolete yast2-ntp-client-4.0.12-lp150.1.1.noarch
Solution 4: break ruby2.5-rubygem-cfa_grub2-1.0.1-lp150.2.3.1.x86_64 by ignoring some of its dependencies
Choose from above solutions by number or skip, retry or cancel [1/2/3/4/s/r/c] (c): r
Resolving dependencies...
Computing distribution upgrade...
8 Problems:
Problem: patterns-yast-yast2_basis-20190411-1.3.x86_64 requires yast2-firewall, but this requirement cannot be provided
Problem: yast2-4.0.103-lp150.2.13.1.x86_64 requires yast2-ruby-bindings >= 3.2.10, but this requirement cannot be provided
Problem: yast2-ldap-4.1.0-1.4.x86_64 requires yast2-network, but this requirement cannot be provided
Problem: yast2-scanner-4.1.0-1.3.x86_64 requires yast2-ruby-bindings >= 1.0.0, but this requirement cannot be provided
Problem: yast2-samba-client-4.2.1-1.3.noarch requires yast2-pam >= 2.14.0, but this requirement cannot be provided
Problem: yast2-ntp-client-4.1.8-1.3.noarch requires yast2-network >= 4.1.17, but this requirement cannot be provided
Problem: yast2-mail-4.1.0-1.4.noarch requires yast2-users, but this requirement cannot be provided
Problem: ruby2.5-rubygem-cfa_grub2-1.0.1-lp150.2.3.1.x86_64 requires ruby(abi) = 2.5.0, but this requirement cannot be provided
Problem: patterns-yast-yast2_basis-20190411-1.3.x86_64 requires yast2-firewall, but this requirement cannot be provided
not installable providers: yast2-firewall-4.2.0-1.3.noarch[http-download.opensuse.org-42093fc6]
yast2-firewall-4.0.26-lp150.2.3.1.noarch[repo-update]
Solution 1: Following actions will be done:
keep yast2-firewall-4.0.34-lp150.7.1.noarch
keep yast2-installation-4.0.74-lp150.2.15.1.noarch
keep yast2-security-4.0.1-lp150.2.6.1.noarch
keep yast2-update-4.0.18-lp150.2.6.1.x86_64
Solution 2: Following actions will be done:
keep yast2-installation-4.0.74-lp150.2.15.1.noarch
keep yast2-security-4.0.1-lp150.2.6.1.noarch
keep yast2-update-4.0.18-lp150.2.6.1.x86_64
Solution 3: deinstallation of patterns-yast-yast2_basis-20180409-lp150.3.1.x86_64
Solution 4: break patterns-yast-yast2_basis-20190411-1.3.x86_64 by ignoring some of its dependencies
Choose from above solutions by number or skip, retry or cancel [1/2/3/4/s/r/c] (c):
Alles anzeigen
Zitat1 | http-download.opensuse.org-42093fc6 | openSUSE:Factory | Yes | (r ) Yes | Yes | 99 | rpm-md | Index of /tumbleweed/repo/oss
Ist Tumbleweed, also löschen, als root:
Dann fehlt das OSS Repo, hinzufügen als root:
Danach als root:
zypper rr http://download.opensuse.org/tumbleweed/repo/oss/
Removing repository 'openSUSE:Factory' ...................................................................................................................................................[done]
Repository 'openSUSE:Factory' has been removed.
zypper ar -f http://download.opensuse.org/distribution/leap/15.1/repo/oss/ repo-oss
Adding repository 'repo-oss' .............................................................................................................................................................[done]
Repository 'repo-oss' successfully added
URI : http://download.opensuse.org/distribution/leap/15.1/repo/oss/
Enabled : Yes
GPG Check : Yes
Autorefresh : Yes
Priority : 99 (default priority)
Repository priorities are without effect. All enabled repositories share the same priority.
Alles anzeigen
zypper dup --allow-vendor-change
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.
Retrieving repository 'repo-oss' metadata ................................................................................................................................................[done]
Building repository 'repo-oss' cache .....................................................................................................................................................[done]
Loading repository data...
Reading installed packages...
Computing distribution upgrade...
Problem: libwayland-egl-devel-18.0.2-lp150.18.3.1.x86_64 requires libwayland-egl1 = 18.0.2, but this requirement cannot be provided
Solution 1: Following actions will be done:
keep obsolete wayland-devel-1.14.0-lp150.1.4.x86_64
keep obsolete libwayland-server0-1.14.0-lp150.1.4.x86_64
Solution 2: Following actions will be done:
keep obsolete wayland-devel-1.14.0-lp150.1.4.x86_64
keep obsolete libwayland-client0-1.14.0-lp150.1.4.x86_64
keep obsolete libwayland-cursor0-1.14.0-lp150.1.4.x86_64
keep obsolete libwayland-server0-1.14.0-lp150.1.4.x86_64
Solution 3: deinstallation of libwayland-egl-devel-18.0.2-lp150.18.3.1.x86_64
Solution 4: break libwayland-egl-devel-18.0.2-lp150.18.3.1.x86_64 by ignoring some of its dependencies
Choose from above solutions by number or cancel [1/2/3/4/c] (c):
Alles anzeigen