es starten Apps nicht wie z.B.:Firefox

Diese Seite verwendet Cookies. Durch die Nutzung unserer Seite erklären Sie sich damit einverstanden, dass wir Cookies setzen. Weitere Informationen

Hinweis: In dem Thema es starten Apps nicht wie z.B.:Firefox gibt es 34 Antworten auf 4 Seiten. Der letzte Beitrag () befindet sich auf der letzten Seite.
  • 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!!!

    Für den Inhalt des Beitrages 134234 haftet ausdrücklich der jeweilige Autor: Alero

  • Sauerland schrieb:

    mach es als root (su -l nicht sudo) per zypper:

    Quellcode

    1. zypper rr 1 2 3
    Danach:

    Quellcode

    1. zypper dup --allow-vendor-change

    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.

    :smilie_pc_012:








    Hat noch jemand eine neue Idee?

    Alero schrieb:

    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!!!


    @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?!! ]
    ⇒ This yellow bird makes yellow snow, deadly yellow snow. ⇐

    wootsdock.blogspot.com/

    Dieser Beitrag wurde bereits 2 mal editiert, zuletzt von Wootsdock ()

    Für den Inhalt des Beitrages 134238 haftet ausdrücklich der jeweilige Autor: Wootsdock

  • 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???

    Für den Inhalt des Beitrages 134241 haftet ausdrücklich der jeweilige Autor: Alero

  • Neu

    @ Sauerland

    zypper lr -d

    Brainfuck-Quellcode

    1. Repository priorities are without effect. All enabled repositories share the same priority.
    2. # | Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service
    3. ---+-------------------------------------+-----------------------------------------+---------+-----------+---------+----------+--------+--------------------------------------------------------------------------+--------
    4. 1 | http-download.opensuse.org-42093fc6 | openSUSE:Factory | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/tumbleweed/repo/oss/ |
    5. 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/ |
    6. 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/ |
    7. 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/ |
    8. 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/ |
    9. 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/ |
    10. 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/ |
    11. 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/ |
    12. 9 | repo-update | openSUSE-Leap-15.0-Update | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/15.0/oss/ |
    13. 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
    ⇒ This yellow bird makes yellow snow, deadly yellow snow. ⇐

    wootsdock.blogspot.com/

    Für den Inhalt des Beitrages 134333 haftet ausdrücklich der jeweilige Autor: Wootsdock

  • Neu

    Quellcode

    1. zypper dup --allow-vendor-change
    2. 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.
    3. Loading repository data...
    4. Reading installed packages...
    5. Computing distribution upgrade...
    6. 2 Problems:
    7. 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
    8. Problem: PackageKit-1.1.10-lp150.8.1.x86_64 requires PackageKit-branding = 1.1.10, but this requirement cannot be provided
    9. 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
    10. deleted providers: ruby2.5-2.5.0-lp150.2.11.x86_64
    11. Solution 1: Following actions will be done:
    12. deinstallation of ruby-2.5-lp150.1.5.x86_64
    13. deinstallation of yast2-services-manager-4.0.10-lp150.7.1.noarch
    14. deinstallation of autoyast2-installation-4.0.69-lp150.2.19.1.noarch
    15. deinstallation of yast2-add-on-4.1.12-1.3.noarch
    16. deinstallation of yast2-apparmor-4.1.7-1.3.noarch
    17. deinstallation of yast2-auth-client-4.1.1-1.3.noarch
    18. deinstallation of yast2-auth-server-4.1.0-1.4.noarch
    19. deinstallation of yast2-firewall-4.0.34-lp150.7.1.noarch
    20. deinstallation of yast2-installation-4.0.74-lp150.2.15.1.noarch
    21. deinstallation of yast2-iscsi-client-4.0.2-lp150.2.3.1.noarch
    22. deinstallation of yast2-journal-4.2.0-1.3.noarch
    23. deinstallation of yast2-mail-4.1.0-1.4.noarch
    24. deinstallation of yast2-metapackage-handler-4.1.0-1.3.noarch
    25. deinstallation of yast2-nfs-client-4.1.5-1.3.noarch
    26. deinstallation of yast2-online-update-4.1.0-1.3.noarch
    27. deinstallation of yast2-pam-4.2.3-1.3.noarch
    28. deinstallation of yast2-proxy-4.1.0-1.3.noarch
    29. deinstallation of yast2-samba-server-4.0.2-lp150.2.3.1.noarch
    30. deinstallation of yast2-security-4.0.1-lp150.2.6.1.noarch
    31. deinstallation of yast2-sudo-4.1.0-1.3.noarch
    32. deinstallation of yast2-support-4.1.1-1.2.noarch
    33. deinstallation of yast2-sysconfig-4.0.1-lp150.2.3.1.noarch
    34. deinstallation of yast2-vpn-4.1.0-1.3.noarch
    35. deinstallation of yast2-online-update-frontend-4.1.0-1.3.noarch
    36. Solution 2: deinstallation of ruby2.5-rubygem-cfa_grub2-1.0.1-lp150.2.3.1.x86_64
    37. Solution 3: keep obsolete ruby-2.5-lp150.1.5.x86_64
    38. Solution 4: break ruby2.5-rubygem-cfa_grub2-1.0.1-lp150.2.3.1.x86_64 by ignoring some of its dependencies
    39. Choose from above solutions by number or skip, retry or cancel [1/2/3/4/s/r/c] (c):
    Alles anzeigen
    ⇒ This yellow bird makes yellow snow, deadly yellow snow. ⇐

    wootsdock.blogspot.com/

    Für den Inhalt des Beitrages 134334 haftet ausdrücklich der jeweilige Autor: Wootsdock

  • Neu

    Quellcode

    1. Choose from above solutions by number or skip, retry or cancel [1/2/3/4/s/r/c] (c): r
    2. Resolving dependencies...
    3. Computing distribution upgrade...
    4. 7 Problems:
    5. Problem: patterns-yast-yast2_basis-20190411-1.3.x86_64 requires yast2-firewall, but this requirement cannot be provided
    6. Problem: yast2-nis-client-4.1.1-1.3.x86_64 requires yast2-pam, but this requirement cannot be provided
    7. Problem: yast2-ruby-bindings-4.2.1-1.3.x86_64 requires ruby, but this requirement cannot be provided
    8. Problem: yast2-update-4.0.18-lp150.2.6.1.x86_64 requires yast2-installation, but this requirement cannot be provided
    9. Problem: yast2-users-4.0.11-lp150.2.10.1.x86_64 requires yast2-security, but this requirement cannot be provided
    10. Problem: yast2-network-4.0.48-lp150.2.16.1.noarch requires yast2-proxy, but this requirement cannot be provided
    11. 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
    12. Problem: patterns-yast-yast2_basis-20190411-1.3.x86_64 requires yast2-firewall, but this requirement cannot be provided
    13. not installable providers: yast2-firewall-4.2.0-1.3.noarch[http-download.opensuse.org-42093fc6]
    14. yast2-firewall-4.0.26-lp150.2.3.1.noarch[repo-update]
    15. Solution 1: Following actions will be done:
    16. keep yast2-firewall-4.0.34-lp150.7.1.noarch
    17. keep yast2-mail-4.1.0-1.4.noarch
    18. keep yast2-online-update-4.1.0-1.3.noarch
    19. keep yast2-online-update-frontend-4.1.0-1.3.noarch
    20. keep yast2-services-manager-4.0.10-lp150.7.1.noarch
    21. keep yast2-sysconfig-4.0.1-lp150.2.3.1.noarch
    22. Solution 2: Following actions will be done:
    23. keep yast2-mail-4.1.0-1.4.noarch
    24. keep yast2-online-update-4.1.0-1.3.noarch
    25. keep yast2-online-update-frontend-4.1.0-1.3.noarch
    26. keep yast2-services-manager-4.0.10-lp150.7.1.noarch
    27. keep yast2-sysconfig-4.0.1-lp150.2.3.1.noarch
    28. Solution 3: deinstallation of patterns-yast-yast2_basis-20180409-lp150.3.1.x86_64
    29. Solution 4: break patterns-yast-yast2_basis-20190411-1.3.x86_64 by ignoring some of its dependencies
    30. Choose from above solutions by number or skip, retry or cancel [1/2/3/4/s/r/c] (c): 2
    31. Problem: yast2-nis-client-4.1.1-1.3.x86_64 requires yast2-pam, but this requirement cannot be provided
    32. Solution 1: deinstallation of yast2-nis-client-4.1.1-1.3.x86_64
    33. Solution 2: keep yast2-pam-4.2.3-1.3.noarch
    34. Solution 3: break yast2-nis-client-4.1.1-1.3.x86_64 by ignoring some of its dependencies
    35. Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c] (c): 1
    36. Problem: yast2-ruby-bindings-4.2.1-1.3.x86_64 requires ruby, but this requirement cannot be provided
    37. deleted providers: ruby-2.5-lp150.1.5.x86_64
    38. not installable providers: ruby-2.6-1.3.i586[http-download.opensuse.org-42093fc6]
    39. ruby-2.6-1.3.x86_64[http-download.opensuse.org-42093fc6]
    40. Solution 1: deinstallation of yast2-ruby-bindings-4.0.6-lp150.1.1.x86_64
    41. Solution 2: keep ruby-2.5-lp150.1.5.x86_64
    42. Solution 3: break yast2-ruby-bindings-4.2.1-1.3.x86_64 by ignoring some of its dependencies
    43. Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c] (c): 1
    44. Problem: yast2-update-4.0.18-lp150.2.6.1.x86_64 requires yast2-installation, but this requirement cannot be provided
    45. not installable providers: yast2-installation-4.2.4-1.3.noarch[http-download.opensuse.org-42093fc6]
    46. yast2-installation-4.0.60-lp150.2.3.1.noarch[repo-update]
    47. yast2-installation-4.0.63-lp150.2.6.1.noarch[repo-update]
    48. yast2-installation-4.0.67-lp150.2.9.1.noarch[repo-update]
    49. yast2-installation-4.0.70-lp150.2.12.1.noarch[repo-update]
    50. Solution 1: deinstallation of yast2-update-4.0.18-lp150.2.6.1.x86_64
    51. Solution 2: keep yast2-installation-4.0.74-lp150.2.15.1.noarch
    52. Solution 3: break yast2-update-4.0.18-lp150.2.6.1.x86_64 by ignoring some of its dependencies
    53. Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c] (c): 1
    54. Problem: yast2-users-4.0.11-lp150.2.10.1.x86_64 requires yast2-security, but this requirement cannot be provided
    55. not installable providers: yast2-security-4.1.2-1.4.noarch[http-download.opensuse.org-42093fc6]
    56. yast2-security-4.0.1-lp150.2.3.1.noarch[repo-update]
    57. Solution 1: deinstallation of yast2-users-4.0.11-lp150.2.10.1.x86_64
    58. Solution 2: keep yast2-security-4.0.1-lp150.2.6.1.noarch
    59. Solution 3: break yast2-users-4.0.11-lp150.2.10.1.x86_64 by ignoring some of its dependencies
    60. Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c] (c): 1
    61. Problem: yast2-network-4.0.48-lp150.2.16.1.noarch requires yast2-proxy, but this requirement cannot be provided
    62. not installable providers: yast2-proxy-4.0.1-lp150.2.3.1.noarch[repo-update]
    63. yast2-proxy-4.0.2-lp150.2.6.1.noarch[repo-update]
    64. Solution 1: deinstallation of yast2-network-4.0.48-lp150.2.16.1.noarch
    65. Solution 2: keep yast2-proxy-4.1.0-1.3.noarch
    66. Solution 3: break yast2-network-4.0.48-lp150.2.16.1.noarch by ignoring some of its dependencies
    67. Choose from above solutions by number or skip, retry or cancel [1/2/3/s/r/c] (c): 1
    68. 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
    69. deleted providers: ruby2.5-2.5.0-lp150.2.11.x86_64
    70. Solution 1: deinstallation of ruby2.5-rubygem-cfa_grub2-1.0.1-lp150.2.3.1.x86_64
    71. Solution 2: deinstallation of yast2-ntp-client-4.0.12-lp150.1.1.noarch
    72. Solution 3: keep obsolete yast2-ntp-client-4.0.12-lp150.1.1.noarch
    73. Solution 4: break ruby2.5-rubygem-cfa_grub2-1.0.1-lp150.2.3.1.x86_64 by ignoring some of its dependencies
    74. Choose from above solutions by number or skip, retry or cancel [1/2/3/4/s/r/c] (c): r
    75. Resolving dependencies...
    76. Computing distribution upgrade...
    77. 8 Problems:
    78. Problem: patterns-yast-yast2_basis-20190411-1.3.x86_64 requires yast2-firewall, but this requirement cannot be provided
    79. Problem: yast2-4.0.103-lp150.2.13.1.x86_64 requires yast2-ruby-bindings >= 3.2.10, but this requirement cannot be provided
    80. Problem: yast2-ldap-4.1.0-1.4.x86_64 requires yast2-network, but this requirement cannot be provided
    81. Problem: yast2-scanner-4.1.0-1.3.x86_64 requires yast2-ruby-bindings >= 1.0.0, but this requirement cannot be provided
    82. Problem: yast2-samba-client-4.2.1-1.3.noarch requires yast2-pam >= 2.14.0, but this requirement cannot be provided
    83. Problem: yast2-ntp-client-4.1.8-1.3.noarch requires yast2-network >= 4.1.17, but this requirement cannot be provided
    84. Problem: yast2-mail-4.1.0-1.4.noarch requires yast2-users, but this requirement cannot be provided
    85. 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
    86. Problem: patterns-yast-yast2_basis-20190411-1.3.x86_64 requires yast2-firewall, but this requirement cannot be provided
    87. not installable providers: yast2-firewall-4.2.0-1.3.noarch[http-download.opensuse.org-42093fc6]
    88. yast2-firewall-4.0.26-lp150.2.3.1.noarch[repo-update]
    89. Solution 1: Following actions will be done:
    90. keep yast2-firewall-4.0.34-lp150.7.1.noarch
    91. keep yast2-installation-4.0.74-lp150.2.15.1.noarch
    92. keep yast2-security-4.0.1-lp150.2.6.1.noarch
    93. keep yast2-update-4.0.18-lp150.2.6.1.x86_64
    94. Solution 2: Following actions will be done:
    95. keep yast2-installation-4.0.74-lp150.2.15.1.noarch
    96. keep yast2-security-4.0.1-lp150.2.6.1.noarch
    97. keep yast2-update-4.0.18-lp150.2.6.1.x86_64
    98. Solution 3: deinstallation of patterns-yast-yast2_basis-20180409-lp150.3.1.x86_64
    99. Solution 4: break patterns-yast-yast2_basis-20190411-1.3.x86_64 by ignoring some of its dependencies
    100. Choose from above solutions by number or skip, retry or cancel [1/2/3/4/s/r/c] (c):
    Alles anzeigen
    ⇒ This yellow bird makes yellow snow, deadly yellow snow. ⇐

    wootsdock.blogspot.com/

    Für den Inhalt des Beitrages 134335 haftet ausdrücklich der jeweilige Autor: Wootsdock

  • Neu

    1 | 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:

    Quellcode

    1. zypper rr http://download.opensuse.org/tumbleweed/repo/oss/

    Dann fehlt das OSS Repo, hinzufügen als root:

    Quellcode

    1. zypper ar -f http://download.opensuse.org/distribution/leap/15.1/repo/oss/ repo-oss
    Danach als root:




    Quellcode

    1. zypper dup --allow-vendor-change
    Links in dieser Signatur bitte zum Lesen anklicken!

    Code-Tags <<<Klick mich
    zypper <<<Klick mich
    Netzwerkprobleme <<<Klick mich

    Für den Inhalt des Beitrages 134337 haftet ausdrücklich der jeweilige Autor: Sauerland

  • Neu

    Brainfuck-Quellcode

    1. zypper rr http://download.opensuse.org/tumbleweed/repo/oss/
    2. Removing repository 'openSUSE:Factory' ...................................................................................................................................................[done]
    3. Repository 'openSUSE:Factory' has been removed.

    Brainfuck-Quellcode

    1. zypper ar -f http://download.opensuse.org/distribution/leap/15.1/repo/oss/ repo-oss
    2. Adding repository 'repo-oss' .............................................................................................................................................................[done]
    3. Repository 'repo-oss' successfully added
    4. URI : http://download.opensuse.org/distribution/leap/15.1/repo/oss/
    5. Enabled : Yes
    6. GPG Check : Yes
    7. Autorefresh : Yes
    8. Priority : 99 (default priority)
    9. Repository priorities are without effect. All enabled repositories share the same priority.
    Alles anzeigen

    Brainfuck-Quellcode

    1. zypper dup --allow-vendor-change
    2. 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.
    3. Retrieving repository 'repo-oss' metadata ................................................................................................................................................[done]
    4. Building repository 'repo-oss' cache .....................................................................................................................................................[done]
    5. Loading repository data...
    6. Reading installed packages...
    7. Computing distribution upgrade...
    8. 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
    9. Solution 1: Following actions will be done:
    10. keep obsolete wayland-devel-1.14.0-lp150.1.4.x86_64
    11. keep obsolete libwayland-server0-1.14.0-lp150.1.4.x86_64
    12. Solution 2: Following actions will be done:
    13. keep obsolete wayland-devel-1.14.0-lp150.1.4.x86_64
    14. keep obsolete libwayland-client0-1.14.0-lp150.1.4.x86_64
    15. keep obsolete libwayland-cursor0-1.14.0-lp150.1.4.x86_64
    16. keep obsolete libwayland-server0-1.14.0-lp150.1.4.x86_64
    17. Solution 3: deinstallation of libwayland-egl-devel-18.0.2-lp150.18.3.1.x86_64
    18. Solution 4: break libwayland-egl-devel-18.0.2-lp150.18.3.1.x86_64 by ignoring some of its dependencies
    19. Choose from above solutions by number or cancel [1/2/3/4/c] (c):
    Alles anzeigen
    ⇒ This yellow bird makes yellow snow, deadly yellow snow. ⇐

    wootsdock.blogspot.com/

    Für den Inhalt des Beitrages 134342 haftet ausdrücklich der jeweilige Autor: Wootsdock