Probleme bei 4.0.23 auf 5.0.12 [gelöst]

GerdNutzinger

@thomas-braun
Skript v.2023-10-10

*** BASE SYSTEM ***
Static hostname: raspberrypi
Icon name: computer
Operating System: Raspbian GNU/Linux 11 (bullseye)
Kernel: Linux 6.1.21-v8+
Architecture: arm64

Model : Raspberry Pi 4 Model B Rev 1.5
Docker : false
Virtualization : none
Kernel : aarch64
Userland : armhf

Systemuptime and Load:
12:00:55 up 1:24, 4 users, load average: 0.74, 0.60, 0.46
CPU threads: 4

*** RASPBERRY THROTTLING ***
Current issues:
No throttling issues detected.

Previously detected issues:
No throttling issues detected.

*** Time and Time Zones ***
Local time: Wed 2023-11-01 12:00:55 CET
Universal time: Wed 2023-11-01 11:00:55 UTC
RTC time: n/a
Time zone: Europe/Berlin (CET, +0100)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no

*** User and Groups ***
pi
/home/pi
pi adm dialout cdrom sudo audio video plugdev games users input render netdev lpadmin gpio i2c spi iobroker

*** X-Server-Setup ***
X-Server: true
Desktop:
Terminal: tty
Boot Target: multi-user.target

*** MEMORY ***
total used free shared buff/cache available
Mem: 3.8G 925M 1.1G 34M 1.7G 2.8G
Swap: 99M 0B 99M
Total: 3.9G 925M 1.2G

     3794 M total memory
      925 M used memory
     1049 M active memory
     1270 M inactive memory
     1119 M free memory
      206 M buffer memory
     1543 M swap cache
       99 M total swap
        0 M used swap
       99 M free swap

Raspberry only:
oom events: 0
lifetime oom required: 0 Mbytes
total time in oom handler: 0 ms
max time spent in oom handler: 0 ms

*** FAILED SERVICES ***

UNIT LOAD ACTIVE SUB DESCRIPTION
0 loaded units listed.

*** FILESYSTEM ***
Filesystem Type Size Used Avail Use% Mounted on
/dev/root ext4 30G 6.9G 21G 25% /
devtmpfs devtmpfs 1.7G 0 1.7G 0% /dev
tmpfs tmpfs 1.9G 0 1.9G 0% /dev/shm
tmpfs tmpfs 759M 920K 758M 1% /run
tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock
/dev/mmcblk0p1 vfat 253M 51M 202M 20% /boot
tmpfs tmpfs 380M 20K 380M 1% /run/user/1000

Messages concerning ext4 filesystem in dmesg:
[Wed Nov 1 10:36:08 2023] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 smsc95xx.macaddr=E4:5F:01:96:8E:89 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty1 root=PARTUUID=42e68ffd-02 rootfstype=ext4 fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles
[Wed Nov 1 10:36:09 2023] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Quota mode: none.
[Wed Nov 1 10:36:09 2023] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[Wed Nov 1 10:36:11 2023] EXT4-fs (mmcblk0p2): re-mounted. Quota mode: none.

Show mounted filesystems (real ones only):
TARGET SOURCE FSTYPE OPTIONS
/ /dev/mmcblk0p2 ext4 rw,noatime
`-/boot /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,flush,errors=remount-ro

Files in neuralgic directories:

/var:
1.6G /var/
908M /var/log
905M /var/log/journal/ce513f1a44ff4c9dbd382eb66e08c51e
905M /var/log/journal
430M /var/cache

Archived and active journals take up 904.1M in the file system.

/opt/iobroker/backups:
31M /opt/iobroker/backups/

/opt/iobroker/iobroker-data:
375M /opt/iobroker/iobroker-data/
181M /opt/iobroker/iobroker-data/files
153M /opt/iobroker/iobroker-data/history
52M /opt/iobroker/iobroker-data/files/javascript.admin
34M /opt/iobroker/iobroker-data/files/javascript.admin/static

The five largest files in iobroker-data are:
21M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.edf7552a.js.map
8.3M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.edf7552a.js
7.1M /opt/iobroker/iobroker-data/files/javascript.admin/static/js/610.f22de4ab.chunk.js.map
6.3M /opt/iobroker/iobroker-data/objects.jsonl
6.3M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_js-node_modules_iobr-99c23e.847b8ad9.chunk.js.map

USB-Devices by-id:
USB-Sticks - Avoid direct links to /dev/* in your adapter setups, please always prefer the links 'by-id':

find: '/dev/serial/by-id/': No such file or directory

*** NodeJS-Installation ***

/usr/bin/nodejs v18.18.2
/usr/bin/node v18.18.2
/usr/bin/npm 9.8.1
/usr/bin/npx 9.8.1
/usr/bin/corepack 0.19.0

nodejs:
Installed: 18.18.2-1nodesource1
Candidate: 18.18.2-1nodesource1
Version table:
*** 18.18.2-1nodesource1 1001
500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
100 /var/lib/dpkg/status
18.18.1-1nodesource1 1001
500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
18.18.0-1nodesource1 1001
500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
18.17.1-1nodesource1 1001
500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
18.17.0-1nodesource1 1001
500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
18.16.1-1nodesource1 1001
500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
18.16.0-1nodesource1 1001
500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
18.15.0-1nodesource1 1001
500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
18.14.2-1nodesource1 1001
500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
18.14.1-1nodesource1 1001
500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
18.14.0-1nodesource1 1001
500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
18.13.0-1nodesource1 1001
500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
18.12.0-1nodesource1 1001
500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
18.11.0-1nodesource1 1001
500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
18.10.0-1nodesource1 1001
500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
18.9.1-1nodesource1 1001
500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
18.9.0-1nodesource1 1001
500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
18.8.0-1nodesource1 1001
500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
18.7.0-1nodesource1 1001
500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
18.6.0-1nodesource1 1001
500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
18.5.0-1nodesource1 1001
500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
18.4.0-1nodesource1 1001
500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
18.3.0-1nodesource1 1001
500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
18.2.0-1nodesource1 1001
500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
18.1.0-1nodesource1 1001
500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
18.0.0-1nodesource1 1001
500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages
12.22.12~dfsg-1~deb11u4 500
500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages

Temp directories causing npm8 problem: 0
No problems detected

Errors in npm tree:

*** ioBroker-Installation ***

ioBroker Status
iobroker is running on this host.

Objects type: jsonl
States type: jsonl

Core adapters versions
js-controller: 5.0.12
admin: 6.12.0
javascript: 7.1.4

Adapters from github: 0

Adapter State

system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0, run as: admin
system.adapter.backitup.0 : backitup : raspberrypi - enabled
system.adapter.discovery.0 : discovery : raspberrypi - enabled
system.adapter.email.0 : email : raspberrypi - enabled
system.adapter.flot.0 : flot : raspberrypi - disabled
system.adapter.fritzdect.0 : fritzdect : raspberrypi - enabled
system.adapter.habpanel.0 : habpanel : raspberrypi - disabled
system.adapter.history.0 : history : raspberrypi - enabled
system.adapter.icons-mfd-svg.0 : icons-mfd-svg : raspberrypi - disabled
system.adapter.jarvis.0 : jarvis : raspberrypi - enabled
system.adapter.javascript.0 : javascript : raspberrypi - enabled
system.adapter.net-tools.0 : net-tools : raspberrypi - enabled
system.adapter.ping.0 : ping : raspberrypi - enabled
system.adapter.sonoff.1 : sonoff : raspberrypi - enabled, port: 1883, bind: 0.0.0.0
system.adapter.sonoff.2 : sonoff : raspberrypi - enabled, port: 1884, bind: 0.0.0.0
system.adapter.terminal.0 : terminal : raspberrypi - enabled, port: 8088, bind: 0.0.0.0, run as: admin
system.adapter.tr-064.0 : tr-064 : raspberrypi - disabled
system.adapter.tr-064.1 : tr-064 : raspberrypi - disabled
system.adapter.tr-064.2 : tr-064 : raspberrypi - disabled
system.adapter.tr-064.3 : tr-064 : raspberrypi - disabled
system.adapter.tuya.0 : tuya : raspberrypi - enabled
system.adapter.vis-bars.0 : vis-bars : raspberrypi - disabled
system.adapter.vis-hqwidgets.0 : vis-hqwidgets : raspberrypi - disabled
system.adapter.vis-inventwo.0 : vis-inventwo : raspberrypi - enabled
system.adapter.vis-material-advanced.0 : vis-material-advanced : raspberrypi - disabled
system.adapter.vis-metro.0 : vis-metro : raspberrypi - disabled
system.adapter.vis.0 : vis : raspberrypi - enabled
system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admin
system.adapter.whatsapp-cmb.0 : whatsapp-cmb : raspberrypi - enabled
system.adapter.yahka.0 : yahka : raspberrypi - enabled
instance is alive

Enabled adapters with bindings

system.adapter.admin.0 : admin : raspberrypi - enabled, port: 8081, bind: 0.0.0.0, run as: admin
system.adapter.sonoff.1 : sonoff : raspberrypi - enabled, port: 1883, bind: 0.0.0.0
system.adapter.sonoff.2 : sonoff : raspberrypi - enabled, port: 1884, bind: 0.0.0.0
system.adapter.terminal.0 : terminal : raspberrypi - enabled, port: 8088, bind: 0.0.0.0, run as: admin
system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admin

ioBroker-Repositories
stable : http://download.iobroker.net/sources-dist.json
beta : http://download.iobroker.net/sources-dist-latest.json

Active repo(s): stable

Installed ioBroker-Instances
Used repository: stable
Adapter "admin" : 6.12.0 , installed 6.12.0
Adapter "backitup" : 2.8.1 , installed 2.8.1
Adapter "discovery" : 3.1.0 , installed 3.1.0
Adapter "email" : 1.2.0 , installed 1.2.0
Adapter "flot" : 1.12.0 , installed 1.12.0
Adapter "fritzdect" : 2.3.1 , installed 2.3.1
Adapter "habpanel" : 0.5.0 , installed 0.5.0
Adapter "history" : 3.0.1 , installed 3.0.1
Adapter "icons-mfd-svg": 1.1.0 , installed 1.1.0
Adapter "jarvis" : 3.1.2 , installed 3.1.2
Adapter "javascript" : 7.1.4 , installed 7.1.4
Controller "js-controller": 5.0.12 , installed 5.0.12
Adapter "net-tools" : 0.2.0 , installed 0.2.0
Adapter "ping" : 1.6.2 , installed 1.6.2
Adapter "simple-api" : 2.7.2 , installed 2.7.2
Adapter "socketio" : 6.5.5 , installed 6.5.5
Adapter "sonoff" : 2.5.3 , installed 2.5.3
Adapter "terminal" : 1.0.0 , installed 1.0.0
Adapter "tr-064" : 4.2.18 , installed 4.2.18
Adapter "tuya" : 3.14.2 , installed 3.14.2
Adapter "vis" : 1.4.16 , installed 1.4.16
Adapter "vis-bars" : 0.1.4 , installed 0.1.4
Adapter "vis-hqwidgets": 1.4.0 , installed 1.4.0
Adapter "vis-inventwo" : 3.3.3 , installed 3.3.3
Adapter "vis-material-advanced": 1.7.4, installed 1.7.4
Adapter "vis-metro" : 1.2.0 , installed 1.2.0
Adapter "web" : 6.1.2 , installed 6.1.2
Adapter "whatsapp-cmb" : 0.2.3 , installed 0.2.3
Adapter "ws" : 2.5.5 , installed 2.5.5
Adapter "yahka" : 1.0.3 , installed 1.0.3

Objects and States
Please stand by - This may take a while
Objects: 1296
States: 1180

*** OS-Repositories and Updates ***
Hit:1 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
Hit:2 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:3 https://deb.nodesource.com/node_18.x nodistro InRelease
Reading package lists...
Pending Updates: 0

*** Listening Ports ***
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name

tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 0 11965 528/cupsd

tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 15508 567/sshd: /usr/sbin
tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 47629 5692/iobroker.js-co
tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 46901 5692/iobroker.js-co
tcp 0 0 0.0.0.0:8400 0.0.0.0:* LISTEN 1001 50312 6025/io.jarvis.0

tcp 0 0 0.0.0.0:1884 0.0.0.0:* LISTEN 1001 48033 5937/io.sonoff.2

tcp 0 0 0.0.0.0:1883 0.0.0.0:* LISTEN 1001 50183 5920/io.sonoff.1

tcp 0 0 0.0.0.0:42173 0.0.0.0:* LISTEN 1001 50085 6077/io.yahka.0

tcp6 0 0 :::22 :::* LISTEN 0 15510 567/sshd: /usr/sbin
tcp6 0 0 :::45069 :::* LISTEN 1001 50083 6077/io.yahka.0

tcp6 0 0 :::8088 :::* LISTEN 1001 51424 6111/io.terminal.0

tcp6 0 0 :::8082 :::* LISTEN 1001 51239 6010/io.web.0

tcp6 0 0 :::8081 :::* LISTEN 1001 46930 5711/io.admin.0

tcp6 0 0 ::1:631 :::* LISTEN 0 11964 528/cupsd

udp 0 0 0.0.0.0:6666 0.0.0.0:* 1001 47871 5822/io.tuya.0

udp 0 0 0.0.0.0:6667 0.0.0.0:* 1001 47872 5822/io.tuya.0

udp 0 0 0.0.0.0:631 0.0.0.0:* 0 15590 580/cups-browsed

udp 0 0 0.0.0.0:5353 0.0.0.0:* 108 11790 384/avahi-daemon: r
udp 0 0 0.0.0.0:58920 0.0.0.0:* 108 11792 384/avahi-daemon: r
udp 0 0 0.0.0.0:68 0.0.0.0:* 0 13283 441/dhcpcd

udp6 0 0 :::546 :::* 0 16455 441/dhcpcd

udp6 0 0 :::44193 :::* 108 11793 384/avahi-daemon: r
udp6 0 0 :::5353 :::* 108 11791 384/avahi-daemon: r

*** Log File - Last 25 Lines ***

2023-11-01 11:32:04.365 - info: host.raspberrypi Do not restart adapter system.adapter.tr-064.3 because disabled or deleted
2023-11-01 11:32:11.459 - error: tr-064.2 (7611) adapter disabled
2023-11-01 11:32:11.512 - warn: tr-064.2 (7611) Terminated (NO_ADAPTER_CONFIG_FOUND): Without reason
2023-11-01 11:32:12.066 - error: host.raspberrypi instance system.adapter.tr-064.2 terminated with code 3 (NO_ADAPTER_CONFIG_FOUND)
2023-11-01 11:32:12.066 - info: host.raspberrypi Do not restart adapter system.adapter.tr-064.2 because disabled or deleted
2023-11-01 11:32:16.631 - error: tr-064.1 (7625) adapter disabled
2023-11-01 11:32:16.687 - warn: tr-064.1 (7625) Terminated (NO_ADAPTER_CONFIG_FOUND): Without reason
2023-11-01 11:32:17.242 - error: host.raspberrypi instance system.adapter.tr-064.1 terminated with code 3 (NO_ADAPTER_CONFIG_FOUND)
2023-11-01 11:32:17.243 - info: host.raspberrypi Do not restart adapter system.adapter.tr-064.1 because disabled or deleted
2023-11-01 11:37:18.989 - info: tuya.0 (5822) bf7485f58956be0656blvs: Connect locally to device
2023-11-01 11:37:18.990 - info: tuya.0 (5822) bf7485f58956be0656blvs Init with IP=192.168.178.51, Key=4870bccd2069e6ff, Version=3.3
2023-11-01 11:42:54.301 - info: tuya.0 (5822) bf7485f58956be0656blvs: Connect locally to device
2023-11-01 11:42:54.302 - info: tuya.0 (5822) bf7485f58956be0656blvs Init with IP=192.168.178.51, Key=4870bccd2069e6ff, Version=3.3
2023-11-01 11:45:29.193 - info: tuya.0 (5822) bf3b14a6e24938dcefsvvj: Connect locally to device
2023-11-01 11:45:29.194 - info: tuya.0 (5822) bf3b14a6e24938dcefsvvj Init with IP=192.168.178.66, Key=rKNJX%q%j/9y<JKX, Version=3.4
2023-11-01 11:46:16.458 - info: tuya.0 (5822) bf3b14a6e24938dcefsvvj: Error on Reconnect (1): connection timed out
2023-11-01 11:46:39.522 - info: tuya.0 (5822) bf3b14a6e24938dcefsvvj: Error on Reconnect (3): connect EHOSTUNREACH 192.168.178.66:6668
2023-11-01 11:47:22.594 - info: tuya.0 (5822) bf3b14a6e24938dcefsvvj: Error on Reconnect (5): connect EHOSTUNREACH 192.168.178.66:6668
2023-11-01 11:48:25.666 - info: tuya.0 (5822) bf3b14a6e24938dcefsvvj: Error on Reconnect (7): connect EHOSTUNREACH 192.168.178.66:6668
2023-11-01 11:48:29.595 - info: tuya.0 (5822) bf7485f58956be0656blvs: Connect locally to device
2023-11-01 11:48:29.596 - info: tuya.0 (5822) bf7485f58956be0656blvs Init with IP=192.168.178.51, Key=4870bccd2069e6ff, Version=3.3
2023-11-01 11:54:04.892 - info: tuya.0 (5822) bf7485f58956be0656blvs: Connect locally to device
2023-11-01 11:54:04.893 - info: tuya.0 (5822) bf7485f58956be0656blvs Init with IP=192.168.178.51, Key=4870bccd2069e6ff, Version=3.3
2023-11-01 11:59:40.185 - info: tuya.0 (5822) bf7485f58956be0656blvs: Connect locally to device
2023-11-01 11:59:40.185 - info: tuya.0 (5822) bf7485f58956be0656blvs Init with IP=192.168.178.51, Key=4870bccd2069e6ff, Version=3.3


============ Mark until here for C&P =============

iob diag has finished.

Thomas Braun · @thomas-braun sagte in Probleme bei 4.0.23 auf 5.0.12:

@gerdnutzinger

Die Zusammenfassung zeigt die wesentlichen Punkte als i.O. an.

Thomas Braun · @thomas-braun Skript v.2023-10-10

@gerdnutzinger

Kannst du mal bitte die Ausgabe von

pgrep -f 'Xorg|ayland|X11'

posten?

GerdNutzinger

@thomas-braun sagte in Probleme bei 4.0.23 auf 5.0.12:

pgrep -f 'Xorg|ayland|X11'

pi@raspberrypi:~ $ pgrep -f 'Xorg|ayland|X11'
575
pi@raspberrypi:~ $

Thomas Braun · @thomas-braun sagte in Probleme bei 4.0.23 auf 5.0.12:

@gerdnutzinger sagte in Probleme bei 4.0.23 auf 5.0.12:

pgrep -f 'Xorg|ayland|X11'

Danke. Bitte noch

ps aux | grep -E 'Xorg|ayland|X11'

GerdNutzinger · @gerdnutzinger sagte in Probleme bei 4.0.23 auf 5.0.12:

@thomas-braun sagte in Probleme bei 4.0.23 auf 5.0.12:

ps aux

Für was sind diese Daten die Du von mir brauchst?

GerdNutzinger · @gerdnutzinger sagte in Probleme bei 4.0.23 auf 5.0.12:

@thomas-braun
pi@raspberrypi:~ $ ps aux | grep -E 'Xorg|ayland|X11'
root 575 0.0 1.3 198080 52660 tty7 Ssl+ 10:36 0:04 /usr/lib/xorg/Xorg :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
pi 20525 0.0 0.0 7464 544 pts/0 S+ 16:13 0:00 grep --color=auto -E Xorg|ayland|X11

Thomas Braun · @thomas-braun sagte in Probleme bei 4.0.23 auf 5.0.12:

@gerdnutzinger sagte in Probleme bei 4.0.23 auf 5.0.12:

Für was sind diese Daten die Du von mir brauchst?

Für das iob diag Kommando. Wollte mal sehen warum da bei dir noch was bezgl. des X-Servers gefunden wird, das dürfte eigentlich nicht mehr der Fall sein.

Kannst du die Kiste mal komplett neustarten und dann nochmal

ps aux | grep -E 'Xorg|ayland|X11'

bitte.

GerdNutzinger · @gerdnutzinger sagte in Probleme bei 4.0.23 auf 5.0.12:

@thomas-braun
Schaut anders aus...

Thomas Braun

@gerdnutzinger sagte in Probleme bei 4.0.23 auf 5.0.12:

Schaut anders aus...

Ja, so soll es auch aussehen. Danke für die Mithilfe!

GerdNutzinger · @gerdnutzinger sagte in Probleme bei 4.0.23 auf 5.0.12:

@thomas-braun
Ich muss DANKE sagen und das sehr gerne.
Was muss ich machen das ich das Problem als gelöst kennzeichne?

Meister Mopper

@gerdnutzinger sagte in Probleme bei 4.0.23 auf 5.0.12:

Was muss ich machen das ich das Problem als gelöst kennzeichne?

Deinen ersten Eintrag mit [gelöst] ergänzen.

Thomas Braun

@gerdnutzinger

Editiere den ersten Beitrag entsprechend.

Community Forum

NEWS

Probleme bei 4.0.23 auf 5.0.12 [gelöst]

Support us

239

32.7k

82.6k

1.3m