wie sieht es mit der Eindeutschung aus? Dolphin ist immer noch komplett in auswärts
Also, hier mit KDE ist Dolphin komplett in Deutsch! Ich habe halt wie immer KDE gewählt, auch wenn da etwas von Alpha-Status stand. Bis jetzt läuft das relativ rund.
Bei Reddit ist mir aufgefallen, dass manche Leute MicroOS bereits seit längerer Zeit nutzen...
Nach einem Neustart sah es dann so aus:
localhost:~ # transactional-update dup
Checking for newer version.
transactional-update 4.1.3 started
Options: dup
Separate /var detected.
2023-02-28 12:15:56 tukit 4.1.3 started
2023-02-28 12:15:56 Options: -c2 open
2023-02-28 12:15:56 Using snapshot 2 as base for new snapshot 3.
2023-02-28 12:15:56 Syncing /etc of previous snapshot 1 as base into new snapshot "/.snapshots/3/snapshot"
2023-02-28 12:15:56 SELinux is enabled.
ID: 3
2023-02-28 12:15:57 Transaction completed.
Calling zypper --no-cd dup
2023-02-28 12:15:58 tukit 4.1.3 started
2023-02-28 12:15:58 Options: call 3 zypper --no-cd dup -y --auto-agree-with-product-licenses
2023-02-28 12:15:59 Executing `zypper --no-cd dup -y --auto-agree-with-product-licenses`:
Ignoring repository 'openSUSE-MicroOS-20230226-0' because of 'no-cd' option.
Loading repository data...
Reading installed packages...
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.
Computing distribution upgrade...
The following 3 packages are going to be upgraded:
MicroOS-release MicroOS-release-appliance libKF5IdleTime5
The following product is going to be upgraded:
openSUSE MicroOS
20230226-0 -> 20230227-0
3 packages to upgrade.
Overall download size: 0 B. Already cached: 1.4 MiB. After the operation, additional 42.3 KiB will be used.
Continue? [y/n/v/...? shows all options] (y): y
In cache MicroOS-release-appliance-20230227-2134.1.x86_64.rpm (1/3), 8.3 KiB
In cache libKF5IdleTime5-5.103.0-2.1.x86_64.rpm (2/3), 73.2 KiB
In cache MicroOS-release-20230227-2134.1.x86_64.rpm (3/3), 1.3 MiB
Checking for file conflicts: [..done]
(1/3) Installing: MicroOS-release-appliance-20230227-2134.1.x86_64 [..done]
(2/3) Installing: libKF5IdleTime5-5.103.0-2.1.x86_64 [...done]
(3/3) Installing: MicroOS-release-20230227-2134.1.x86_64 [...done]
2023-02-28 12:16:01 Application returned with exit status 0.
2023-02-28 12:16:01 Transaction completed.
Trying to rebuild kdump initrd
Creating a new grub2 config
2023-02-28 12:16:02 tukit 4.1.3 started
2023-02-28 12:16:02 Options: call 3 bash -c /usr/sbin/grub2-mkconfig > /boot/grub2/grub.cfg
2023-02-28 12:16:02 Executing `bash -c /usr/sbin/grub2-mkconfig > /boot/grub2/grub.cfg`:
Generating grub configuration file ...
Found theme: /boot/grub2/themes/openSUSE/theme.txt
Found linux image: /boot/vmlinuz-6.1.12-1-default
Found initrd image: /boot/initrd-6.1.12-1-default
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
done
2023-02-28 12:16:03 Application returned with exit status 0.
2023-02-28 12:16:03 Transaction completed.
2023-02-28 12:16:03 tukit 4.1.3 started
2023-02-28 12:16:03 Options: close 3
2023-02-28 12:16:03 New default snapshot is #3 (/.snapshots/3/snapshot).
2023-02-28 12:16:03 Transaction completed.
Please reboot your machine to activate the changes and avoid data loss.
New default snapshot is #3 (/.snapshots/3/snapshot).
transactional-update finishedHier ist jetzt keine Rede mehr davon, dass das Packman-Repo nicht gültig sei. 
localhost:~ # transactional-update shell
Checking for newer version.
Repository 'Packman' is invalid.
[Packman|http://ftp.halifax.rwth-aachen.de/packman/suse/openSUSE_Tumbleweed/] Valid metadata not found at specified URL
History:
- Signature verification failed for repomd.xml
- Can't provide /repodata/repomd.xml
Please check if the URIs defined for this repository are pointing to a valid repository.
Some of the repositories have not been refreshed because of an error.
transactional-update 4.1.3 started
Options: shell
Separate /var detected.
2023-02-28 12:12:04 tukit 4.1.3 started
2023-02-28 12:12:04 Options: -c1 open
2023-02-28 12:12:04 Using snapshot 1 as base for new snapshot 2.
2023-02-28 12:12:04 No previous snapshot to sync with - skipping
Relabeled /var from system_u:object_r:unlabeled_t:s0 to system_u:object_r:var_t:s0
Relabeled /var/lib from unconfined_u:object_r:unlabeled_t:s0 to unconfined_u:object_r:var_lib_t:s0
ID: 2
2023-02-28 12:12:04 Transaction completed.
Opening chroot in snapshot 2, continue with 'exit'
2023-02-28 12:12:04 tukit 4.1.3 started
2023-02-28 12:12:04 Options: call 2 bash
Relabeled /var/lib/ca-certificates from unconfined_u:object_r:var_lib_t:s0 to unconfined_u:object_r:cert_t:s0
Relabeled /var/lib/alternatives from unconfined_u:object_r:var_lib_t:s0 to unconfined_u:object_r:rpm_var_lib_t:s0
Relabeled /var/log from unconfined_u:object_r:var_t:s0 to unconfined_u:object_r:var_log_t:s0
2023-02-28 12:12:04 Executing `bash`:
transactional update # zypper in mc
New repository or package signing key received:
Repository: Packman
Key Fingerprint: F887 5B88 0D51 8B6B 8C53 0D13 45A1 D067 1ABD 1AFB
Key Name: PackMan Project (signing key) <packman@links2linux.de>
Key Algorithm: RSA 4096
Key Created: Tue Sep 16 00:18:00 2014
Key Expires: Fri Sep 13 00:17:21 2024
Rpm Name: gpg-pubkey-1abd1afb-54176598
Note: Signing data enables the recipient to verify that no modifications occurred after the data
were signed. Accepting data with no, wrong or unknown signature can lead to a corrupted system
and in extreme cases even to a system compromise.
Note: A GPG pubkey is clearly identified by its fingerprint. Do not rely on the key's name. If
you are not sure whether the presented key is authentic, ask the repository provider or check
their web site. Many providers maintain a web page showing the fingerprints of the GPG keys they
are using.
Do you want to reject the key, trust temporarily, or trust always? [r/t/a/?] (r): t
Retrieving repository 'Packman' metadata ...............................................................................................................................................................................................................................[done]
Building repository 'Packman' cache ....................................................................................................................................................................................................................................[done]
Loading repository data...
Reading installed packages...
Resolving package dependencies...
The following 5 NEW packages are going to be installed:
libgpm2 libslang2 libssh2-1 mc mc-lang
5 new packages to install.
Overall download size: 2.2 MiB. Already cached: 0 B. After the operation, additional 8.5 MiB will be used.
Continue? [y/n/v/...? shows all options] (y):
Retrieving: libgpm2-1.20.7-19.11.x86_64 (openSUSE-Tumbleweed-Oss) (1/5), 19.1 KiB
Retrieving: libgpm2-1.20.7-19.11.x86_64.rpm ..............................................................................................................................................................................................................[done (149.4 KiB/s)]
Retrieving: libslang2-2.3.3-1.1.x86_64 (openSUSE-Tumbleweed-Oss) (2/5), 385.5 KiB
Retrieving: libslang2-2.3.3-1.1.x86_64.rpm ................................................................................................................................................................................................................[done (61.6 KiB/s)]
Retrieving: libssh2-1-1.10.0-1.7.x86_64 (openSUSE-Tumbleweed-Oss) (3/5), 114.3 KiB
Retrieving: libssh2-1-1.10.0-1.7.x86_64.rpm ................................................................................................................................................................................................................[done (2.6 KiB/s)]
Retrieving: mc-4.8.28-2.3.x86_64 (openSUSE-Tumbleweed-Oss) (4/5), 779.1 KiB
Retrieving: mc-4.8.28-2.3.x86_64.rpm .......................................................................................................................................................................................................................[done (6.2 MiB/s)]
Retrieving: mc-lang-4.8.28-2.3.noarch (openSUSE-Tumbleweed-Oss) (5/5), 983.0 KiB
Retrieving: mc-lang-4.8.28-2.3.noarch.rpm ..................................................................................................................................................................................................................[done (5.7 MiB/s)]
Checking for file conflicts: ...........................................................................................................................................................................................................................................[done]
(1/5) Installing: libgpm2-1.20.7-19.11.x86_64 ..........................................................................................................................................................................................................................[done]
(2/5) Installing: libslang2-2.3.3-1.1.x86_64 ...........................................................................................................................................................................................................................[done]
(3/5) Installing: libssh2-1-1.10.0-1.7.x86_64 ..........................................................................................................................................................................................................................[done]
/usr/libexec/mc/cons.saver: setting to root:root 4755 (wrong permissions 0755)
(4/5) Installing: mc-4.8.28-2.3.x86_64 .................................................................................................................................................................................................................................[done]
(5/5) Installing: mc-lang-4.8.28-2.3.noarch ............................................................................................................................................................................................................................[done]
transactional update #In der Shell wurden dann auch die Signaturen für Packman verarbeitet und ich konnte ein Prpgramm via zypper in installieren.
Habe jetzt mal versucht, das Packman-Repo einzubinden.
localhost:~ # zypper ar -p 20 -f -t:rpm-md http://ftp.halifax.rwth-aachen.de/packman/suse/openSUSE_Tumbleweed/ Packman
Warning: Legacy commandline option --type detected. This option is ignored.
Adding repository 'Packman' ............................................................................................................................................................................................................................................[done]
Repository 'Packman' successfully added
URI : http://ftp.halifax.rwth-aachen.de/packman/suse/openSUSE_Tumbleweed/
Enabled : Yes
GPG Check : Yes
Autorefresh : Yes
Priority : 20 (raised priority)
Repository priorities in effect: (See 'zypper lr -P' for details)
20 (raised priority) : 1 repository
99 (default priority) : 3 repositoriesrpm-md lässt sich schon mal nicht ändern...
localhost:~ # transactional-update dup --from Packman
Syntax: transactional-update [option...] [general-command...] [package-command]
transactional-update [option...] standalone-command
[...]Ergibt einen Syntax-Error und gibt die Hilfeseite aus
was der Konsolenbefehl transactional-update nun genau im System veranstaltet, ist mir auch noch schleierhaft
Ohne Option entspricht das zypper up. Man kann aber dup als Option anhängen.
transactional-update -helpListet immerhin die grundlegenden Kommandos auf. Leider gibt es dazu keine man-page, oder ich hab mich beim Suchen zu dusslig angestellt. 
meinen Drucker hat das System zwar erkannt, es druckt aber nicht
Same here! Mein alter Samsung Laser wurde nach Installation der Treibersoftware ebenfalls erkannt, bleibt jedoch in der Warteschlange hängen; offenbar irgendein Rechteproblem, denn ich konnte immerzu etwas von 'verboten' lesen.
Wir lassen uns weiter überraschen. 
Interessant finde ich ja die Softwareumgebung, die offensichtlich ja aus den Tumbleweed-Repos kommt.
Mich würde es nicht wundern, wenn eines Tages Tumbleweed automatisch zu microOS wird...
Werde morgen mal testen, wie sich hier die TW-Version des Packman-Repos verhält.
localhost:~ # zypper lr -d
# | Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service
--+-----------------------------+-----------------------------+---------+-----------+---------+----------+--------+----------------------------------------------------------+--------
1 | openSUSE-MicroOS-20230226-0 | openSUSE-MicroOS-20230226-0 | No | ---- | ---- | 99 | rpm-md | cd:/?devices=/dev/disk/by-id/ata-QEMU_DVD-ROM_QM00001 |
2 | repo-debug | openSUSE-Tumbleweed-Debug | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/tumbleweed/repo/oss/ |
3 | repo-non-oss | openSUSE-Tumbleweed-Non-Oss | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/tumbleweed/repo/non-oss/ |
4 | repo-oss | openSUSE-Tumbleweed-Oss | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/tumbleweed/repo/oss/ |
5 | repo-source | openSUSE-Tumbleweed-Source | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/source/tumbleweed/repo/oss/ |
6 | repo-update | openSUSE-Tumbleweed-Update | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/tumbleweed/ |
localhost:~ #Hallo Vetinari77,
deine Leap15.4-Installation ist das letzte Glied einer langen Hard- / Softwarekette. Am sinnvollsten ist es meist, ein Problem von der Basis her zu finden und zu lösen.
Möglicherweise ist deine Frage in einem Forum für VirtualBox besser aufgehoben.
Probiere einmal, die äußerst rechte Spalte frei zu lassen. Seitdem ich dort keine Icons mehr habe, werden meine Symbole nicht mehr durcheinander gewürfelt, was durchaus auch mal nach einem Neustart vorkommen konnte.
Man sagte mir damals, das würde am NVIDIA-Treiber liegen.
Ich kann mit diesem Workaround gut leben.
das Vergessen ist bei mir das Problem, ich lese hier quasi täglich mit und versuche mir das auch zu merken.
Genau das ist der Punkt, warum ich bereits vor vielen Jahren begonnen habe, mir derartige Dinge zu notieren. Meine 'Roadmap' für die Installation ist bereits über 300 Zeilen lang und liegt auf einem Laufwerk, das nach der Installation von TW sowieso immer eingebunden wird.
