Libreoffice&Abstürze Stretch

[Ozelot]

Moin,

Ich verwende Libreoffice Version 5.2.5.1, Build-ID 1:5.2.5-2 unter Stretch/KDE. Gelegentlich bleibt das Programm für 10-20 Sekunden hängen, und danach beendet sich vermutlich X - jedenfalls lande ich nach einem schwarzen Bildschirm wieder bei der (KDM?)-Anmeldung. Wenn ich mich dann sofort wieder einlogge (aber nicht, wenn ich eine Minute warte!), bleibt KDE beim Laden reproduzierbar hängen. Bei einem Reboot von der Konsole, blieb jetzt sogar der mit der Meldung hängen, daß noch ein Job für den entsprechenden User "in Session 8" laufe.

Frage: Wie grenze ich den mutmaßlichen Bug ein (Libreoffice? KDE? KVM? X?) ? Welche logs sollte ich anschauen/posten?

danke!

O

[pferdefreund]

alles unter /var/log und eventuell mal loffice mit den parametern > fehler.txt 2>&1 in einer Konsole starten und dann die Datei fehler mal anschauen. Die Datei fehler.txt sollte dann in deinem $HOME zu finden sein.

[Ozelot]

Libreoffice meldet insgesamt nur ein doppeltes:

Code: Alles auswählen

soffice.bin: Fatal IO error: client killed
soffice.bin: Fatal IO error: client killed

xorg.0.log:
http://nopaste.debianforum.de/39791

user.log:

Code: Alles auswählen

Mar 23 13:54:04 rechnername org.kde.kuiserver[796]: kuiserver: Fatal IO error: client killed
Mar 23 13:54:04 rechnername org.kde.kaccessibleapp[796]: kaccessibleapp: Fatal IO error: client killed
Mar 23 13:54:04 rechnername org.kde.kglobalaccel[796]: The X11 connection broke (error 1). Did the X11 server die?
Mar 23 13:54:04 rechnername org.kde.KScreen[796]: The X11 connection broke (error 1). Did the X11 server die?
Mar 23 13:54:05 rechnername org.kde.kglobalaccel[796]: QXcbConnection: Could not connect to display :0
Mar 23 13:54:17 rechnername org.kde.KScreen[5242]: kscreen.xrandr: Connected output 66 to CRTC 63
Mar 23 13:54:17 rechnername org.kde.KScreen[5242]: kscreen.xcb.helper: Detected XRandR 1.5
Mar 23 13:54:17 rechnername org.kde.KScreen[5242]: kscreen.xcb.helper: Event Base:  89
Mar 23 13:54:17 rechnername org.kde.KScreen[5242]: kscreen.xcb.helper: Event Error:  147
Mar 23 13:54:18 rechnername org.kde.KScreen[5242]: kscreen.xrandr: XRandR::setConfig
Mar 23 13:54:18 rechnername org.kde.KScreen[5242]: kscreen.xrandr: Requested screen size is QSize(2560, 1440)
Mar 23 13:54:18 rechnername org.kde.KScreen[5242]: kscreen.xrandr: Needed CRTCs:  1
Mar 23 13:54:18 rechnername org.kde.KScreen[5242]: kscreen.xrandr: Actions to perform:
Mar 23 13:54:18 rechnername org.kde.KScreen[5242]: kscreen.xrandr: #011Primary Output: false
Mar 23 13:54:18 rechnername org.kde.KScreen[5242]: kscreen.xrandr: #011Change Screen Size: false
Mar 23 13:54:18 rechnername org.kde.KScreen[5242]: kscreen.xrandr: #011Disable outputs: false
Mar 23 13:54:18 rechnername org.kde.KScreen[5242]: kscreen.xrandr: #011Change outputs: false
Mar 23 13:54:18 rechnername org.kde.KScreen[5242]: kscreen.xrandr: #011Enable outputs: false
Mar 23 13:54:18 rechnername org.kde.KScreen[5242]: kscreen.xrandr: XRandR::setConfig done!
Mar 23 13:54:18 rechnername org.a11y.atspi.Registry[5423]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Mar 23 13:54:18 rechnername org.kde.powerdevil.backlighthelper: QDBusArgument: read from a write-only object
Mar 23 13:54:18 rechnername org.kde.powerdevil.backlighthelper: QDBusArgument: read from a write-only object
Mar 23 13:54:18 rechnername org.kde.powerdevil.backlighthelper: QDBusArgument: read from a write-only object
Mar 23 13:54:21 rechnername org.kde.kuiserver[5242]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Mar 23 13:54:21 rechnername org.kde.kuiserver[5242]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Mar 23 13:54:21 rechnername org.kde.kaccessibleapp[5242]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Mar 23 13:54:21 rechnername org.kde.kaccessibleapp[5242]: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Mar 23 13:54:22 rechnername org.kde.kaccessibleapp[5242]: X Error: RenderBadPicture (invalid Picture parameter) 143
Mar 23 13:54:22 rechnername org.kde.kaccessibleapp[5242]:   Extension:    139 (RENDER)
Mar 23 13:54:22 rechnername org.kde.kaccessibleapp[5242]:   Minor opcode: 7 (RenderFreePicture)
Mar 23 13:54:22 rechnername org.kde.kaccessibleapp[5242]:   Resource id:  0x520001c
Mar 23 13:54:22 rechnername org.kde.kaccessibleapp[5242]: X Error: BadWindow (invalid Window parameter) 3
Mar 23 13:54:22 rechnername org.kde.kaccessibleapp[5242]:   Major opcode: 18 (X_ChangeProperty)
Mar 23 13:54:22 rechnername org.kde.kaccessibleapp[5242]:   Resource id:  0x520001b
Mar 23 13:54:22 rechnername org.kde.kaccessibleapp[5242]: X Error: BadWindow (invalid Window parameter) 3
Mar 23 13:54:22 rechnername org.kde.kaccessibleapp[5242]:   Major opcode: 4 (X_DestroyWindow)
Mar 23 13:54:22 rechnername org.kde.kaccessibleapp[5242]:   Resource id:  0x520001b

debug:

Code: Alles auswählen

Mar 23 13:54:05 rechnername sddm-helper[760]: [PAM] Closing session
Mar 23 13:54:05 rechnername sddm-helper[760]: [PAM] Ended.
Mar 23 13:54:05 rechnername sddm[680]: Auth: sddm-helper exited successfully
Mar 23 13:54:05 rechnername sddm[680]: Socket server stopping...
Mar 23 13:54:05 rechnername sddm[680]: Socket server stopped.
Mar 23 13:54:05 rechnername sddm[680]: Display server stopping...
Mar 23 13:54:05 rechnername sddm[680]: Display server stopped.
Mar 23 13:54:05 rechnername sddm[680]: Running display stop script  "/usr/share/sddm/scripts/Xstop"
Mar 23 13:54:05 rechnername sddm[680]: Removing display ":0" ...
Mar 23 13:54:05 rechnername sddm[680]: Adding new display on vt 7 ...
Mar 23 13:54:05 rechnername sddm[680]: Display server starting...
Mar 23 13:54:05 rechnername sddm[680]: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{6be47222-4677-40e7-846e-e8d0e856e869} -background none -noreset -displayfd 19 vt7
Mar 23 13:54:06 rechnername sddm[680]: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
Mar 23 13:54:06 rechnername sddm[680]: Display server started.
Mar 23 13:54:06 rechnername sddm[680]: Socket server starting...
Mar 23 13:54:06 rechnername sddm[680]: Socket server started.
Mar 23 13:54:06 rechnername sddm[680]: Greeter starting...
Mar 23 13:54:06 rechnername sddm[680]: Adding cookie to "/var/run/sddm/{6be47222-4677-40e7-846e-e8d0e856e869}"
Mar 23 13:54:06 rechnername sddm-helper[5178]: [PAM] Starting...
Mar 23 13:54:06 rechnername sddm-helper[5178]: [PAM] Authenticating...
Mar 23 13:54:06 rechnername sddm-helper[5178]: [PAM] returning.
Mar 23 13:54:06 rechnername sddm[680]: Greeter session started successfully
Mar 23 13:54:06 rechnername sddm-greeter[5186]: High-DPI autoscaling Not Enabled
Mar 23 13:54:06 rechnername sddm-greeter[5186]: Reading from "/usr/share/xsessions/plasma.desktop"
Mar 23 13:54:06 rechnername sddm-greeter[5186]: Connected to the daemon.
Mar 23 13:54:06 rechnername sddm[680]: Message received from greeter: Connect
Mar 23 13:54:06 rechnername sddm-greeter[5186]: Adding view for "eDP-1" QRect(0,0 2560x1440)
Mar 23 13:54:06 rechnername sddm-greeter[5186]: Message received from daemon: Capabilities
Mar 23 13:54:06 rechnername sddm-greeter[5186]: Message received from daemon: HostName
Mar 23 13:54:17 rechnername sddm-greeter[5186]: Reading from "/usr/share/xsessions/plasma.desktop"
Mar 23 13:54:17 rechnername sddm[680]: Message received from greeter: Login
Mar 23 13:54:17 rechnername sddm[680]: Reading from "/usr/share/xsessions/plasma.desktop"
Mar 23 13:54:17 rechnername sddm[680]: Reading from "/usr/share/xsessions/plasma.desktop"
Mar 23 13:54:17 rechnername sddm[680]: Session "/usr/share/xsessions/plasma.desktop" selected, command: "/usr/bin/startkde"
Mar 23 13:54:17 rechnername sddm-helper[5207]: [PAM] Starting...
Mar 23 13:54:17 rechnername sddm-helper[5207]: [PAM] Authenticating...
Mar 23 13:54:17 rechnername sddm-helper[5207]: [PAM] Preparing to converse...
Mar 23 13:54:17 rechnername sddm-helper[5207]: [PAM] Conversation with 1 messages
Mar 23 13:54:17 rechnername sddm-helper[5207]: [PAM] returning.
Mar 23 13:54:17 rechnername sddm[680]: Authenticated successfully
Mar 23 13:54:17 rechnername sddm-greeter[5186]: Message received from daemon: LoginSucceeded
Mar 23 13:54:17 rechnername sddm-helper[5178]: [PAM] Closing session
Mar 23 13:54:17 rechnername sddm-helper[5178]: [PAM] Ended.
Mar 23 13:54:17 rechnername sddm[680]: Auth: sddm-helper exited successfully
Mar 23 13:54:17 rechnername sddm[680]: Greeter stopped.
Mar 23 13:54:17 rechnername sddm-helper[5226]: Adding cookie to "/home/xyx/.Xauthority"
Mar 23 13:54:17 rechnername sddm[680]: Session started
Mar 23 13:54:18 rechnername rtkit-daemon[632]: Supervising 1 threads of 1 processes of 1 users.
Mar 23 13:54:18 rechnername rtkit-daemon[632]: Supervising 1 threads of 1 processes of 1 users.
Mar 23 13:54:18 rechnername rtkit-daemon[632]: Supervising 2 threads of 1 processes of 1 users.
Mar 23 13:54:18 rechnername rtkit-daemon[632]: Supervising 2 threads of 1 processes of 1 users.
Mar 23 13:54:18 rechnername rtkit-daemon[632]: Supervising 3 threads of 1 processes of 1 users.

[rendegast]

(Libreoffice? KDE? KVM? X?)

libreoffice mag der Auslöser oder mitbetroffen sein,
der "richtige" Bug würde ich vermuten ist in KDE oder X.
Von einem buggy Anwendungsprogramm sollten Desktop oder X unbeeindruckt bleiben.

Kannst Du das mit einem anderen Desktop / Fenstermanager nachstellen?

bei der (KDM?)-Anmeldung.

sddm

[hikaru]

Dem Xorg-Log zufolge dürfte das ein Laptop mit Intel-Grafik sein, vermutlich nicht älter als Haswell.
Fehlt da vielleicht nur intel-microcode für einen stabilen Betrieb?