You are not logged in.

Pages: 1

#1 2018-07-20 11:58:42

friendofarch
Member
Registered: 2013-12-30
Posts: 59

Can't relogin with mainuser after other users logged in (GDM)

I have a strange problem:

If a second user logs in with gdm I can't relogin with my mainuser afterwards?!?

When I enter the credentials on gdm for about ~1-2 minutes nothing happens, then loginscreen just reloads without any feedback.

I tried to get some useful information with dmesg, but there is no output?!?

Any ideas?

The problem is rather new, started ~2 weeks ago...

Offline

#2 2018-07-20 12:38:22

WorMzy
Administrator
From: Scotland
Registered: 2010-06-16
Posts: 13,718
Website

Re: Can't relogin with mainuser after other users logged in (GDM)

Why are you looking in dmesg? What makes you think this is related to the kernel?

Post the full journal from an affected session.

Mod note: Moving to NC.

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#3 2018-07-22 17:16:56

friendofarch
Member
Registered: 2013-12-30
Posts: 59

Re: Can't relogin with mainuser after other users logged in (GDM)

For some reason the problem didn't reappear until now...

WorMzy wrote:

Why are you looking in dmesg? What makes you think this is related to the kernel?

Good question! Just a habit... If I have problems I check dmesg and usually I get the information to fix it wink

WorMzy wrote:

Post the full journal from an affected session.

Jul 22 18:42:15 Computer tracker-extract[3058]: Could not insert metadata for item "file:///home/user/Videos/this%20is%20england.avi": Unable to insert multiple values for subject `urn:uuid:99999999-0b41-5437-80e7-914d7eaecd71' and single valued property `nie:contentCreated' (old_value: '<untransformable>', new value: '<untransformable>')
Jul 22 18:42:15 Computer tracker-extract[3058]: If the error above is recurrent for the same item/ID, consider running "tracker-extract" in the terminal with the TRACKER_VERBOSITY=3 environment variable, and filing a bug with the additional information
Jul 22 18:42:15 Computer tracker-miner-fs.desktop[1586]: Received signal:15->'Beendet'
Jul 22 18:42:15 Computer tracker-miner-fs.desktop[1586]: OK
Jul 22 18:42:26 Computer tracker-store[3085]: Received signal:15->'Beendet'
Jul 22 18:42:26 Computer tracker-store[3085]: OK
Jul 22 18:42:35 Computer tracker-miner-apps.desktop[1633]: Received signal:15->'Beendet'
Jul 22 18:42:35 Computer tracker-miner-apps.desktop[1633]: OK
Jul 22 18:42:50 Computer nemo-autostart.desktop[1587]: Socket File: /run/user/1000/ownCloud/socket
Jul 22 18:42:50 Computer nemo-autostart.desktop[1587]: Could not connect to unix socket. [Errno 2] File or folder not found
Jul 22 18:42:50 Computer nemo-autostart.desktop[1587]: Socket File: /run/user/1000/ownCloud/socket
Jul 22 18:42:50 Computer nemo-autostart.desktop[1587]: Could not connect to unix socket. [Errno 2] File or folder not found
Jul 22 18:42:50 Computer nemo-autostart.desktop[1587]: Socket File: /run/user/1000/ownCloud/socket
Jul 22 18:42:50 Computer nemo-autostart.desktop[1587]: Could not connect to unix socket. [Errno 2] File or folder not found
Jul 22 18:42:50 Computer nemo-autostart.desktop[1587]: Socket File: /run/user/1000/ownCloud/socket
Jul 22 18:42:50 Computer nemo-autostart.desktop[1587]: Could not connect to unix socket. [Errno 2] File or folder not found
Jul 22 18:42:50 Computer nemo-autostart.desktop[1587]: Socket File: /run/user/1000/ownCloud/socket
Jul 22 18:42:50 Computer nemo-autostart.desktop[1587]: Could not connect to unix socket. [Errno 2] File or folder not found
Jul 22 18:42:50 Computer nemo-autostart.desktop[1587]: Socket File: /run/user/1000/ownCloud/socket
Jul 22 18:42:50 Computer nemo-autostart.desktop[1587]: Could not connect to unix socket. [Errno 2] File or folder not found
Jul 22 18:42:50 Computer nemo-autostart.desktop[1587]: Socket File: /run/user/1000/ownCloud/socket
Jul 22 18:42:50 Computer nemo-autostart.desktop[1587]: Could not connect to unix socket. [Errno 2] File or folder not found
Jul 22 18:42:50 Computer nemo-autostart.desktop[1587]: Socket File: /run/user/1000/ownCloud/socket
Jul 22 18:42:50 Computer nemo-autostart.desktop[1587]: Could not connect to unix socket. [Errno 2] File or folder not found
Jul 22 18:42:51 Computer org.gnome.Shell.desktop[1110]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Jul 22 18:42:51 Computer org.gnome.Shell.desktop[1110]: > Warning:          Unsupported maximum keycode 374, clipping.
Jul 22 18:42:51 Computer org.gnome.Shell.desktop[1110]: >                   X11 cannot support keycodes above 255.
Jul 22 18:42:51 Computer org.gnome.Shell.desktop[1110]: > Warning:          Unsupported high keycode 372 for name <I372> ignored
Jul 22 18:42:51 Computer org.gnome.Shell.desktop[1110]: >                   X11 cannot support keycodes above 255.
Jul 22 18:42:51 Computer org.gnome.Shell.desktop[1110]: >                   This warning only shows for the first high keycode.
Jul 22 18:42:51 Computer org.gnome.Shell.desktop[1110]: > Internal error:   Could not resolve keysym XF86WWAN
Jul 22 18:42:51 Computer org.gnome.Shell.desktop[1110]: > Internal error:   Could not resolve keysym XF86RFKill
Jul 22 18:42:51 Computer org.gnome.Shell.desktop[1110]: > Internal error:   Could not resolve keysym XF86Keyboard
Jul 22 18:42:51 Computer org.gnome.Shell.desktop[1110]: Errors from xkbcomp are not fatal to the X server
Jul 22 18:42:52 Computer gnome-shell[1110]: JS ERROR: TypeError: this._currentWindow is null
                                            _setCurrentRect@resource:///org/gnome/shell/ui/keyboard.js:536:13
                                            wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
                                            _init/<@resource:///org/gnome/shell/ui/keyboard.js:503:13
Jul 22 18:42:52 Computer gnome-shell[1110]: JS ERROR: TypeError: this._currentWindow is null
                                            _setCurrentRect@resource:///org/gnome/shell/ui/keyboard.js:536:13
                                            wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
                                            _init/<@resource:///org/gnome/shell/ui/keyboard.js:503:13
Jul 22 18:42:52 Computer gnome-shell[1110]: Object Clutter.Clone (0x56392ce450d0), has been already finalized. Impossible to get any property from it.
Jul 22 18:42:52 Computer gnome-shell[1110]: Object Clutter.Clone (0x56392ce450d0), has been already finalized. Impossible to set any property to it.
Jul 22 18:42:52 Computer org.gnome.Shell.desktop[1110]: == Stack trace for context 0x56392b7d2180 ==
Jul 22 18:42:52 Computer org.gnome.Shell.desktop[1110]: #0 0x7ffeb5bb6c00 b   resource:///org/gnome/shell/ui/tweener.js:73 (0x7f8c3c4c8cd0 @ 9)
Jul 22 18:42:52 Computer org.gnome.Shell.desktop[1110]: #1 0x7ffeb5bb6ca0 b   resource:///org/gnome/shell/ui/tweener.js:105 (0x7f8c3c4c8f78 @ 36)
Jul 22 18:42:52 Computer org.gnome.Shell.desktop[1110]: #2 0x7ffeb5bb6d40 b   resource:///org/gnome/shell/ui/tweener.js:92 (0x7f8c3c4c8de0 @ 52)
Jul 22 18:42:52 Computer org.gnome.Shell.desktop[1110]: #3 0x7ffeb5bb7bd0 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7f8c3c4d2918 @ 54)
Jul 22 18:42:52 Computer org.gnome.Shell.desktop[1110]: #4 0x7ffeb5bb7d20 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7f8c3c4d29a0 @ 1626)
Jul 22 18:42:52 Computer org.gnome.Shell.desktop[1110]: #5 0x7ffeb5bb7dd0 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7f8c3c4d2a28 @ 100)
Jul 22 18:42:52 Computer org.gnome.Shell.desktop[1110]: #6 0x7ffeb5bb7e60 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7f8c3c4d2ab0 @ 10)
Jul 22 18:42:52 Computer org.gnome.Shell.desktop[1110]: #7 0x7ffeb5bb7ee0 I   resource:///org/gnome/gjs/modules/signals.js:128 (0x7f8c3c4cff78 @ 386)
Jul 22 18:42:52 Computer org.gnome.Shell.desktop[1110]: #8 0x7ffeb5bb7f90 b   resource:///org/gnome/shell/ui/tweener.js:207 (0x7f8c3c4cf5e8 @ 159)
Jul 22 18:42:52 Computer org.gnome.Shell.desktop[1110]: #9 0x7ffeb5bb8000 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f8c3c4b5de0 @ 71)
Jul 22 18:42:52 Computer org.gnome.Shell.desktop[1110]: #10 0x7ffeb5bb8000 I   resource:///org/gnome/shell/ui/tweener.js:182 (0x7f8c3c4cf560 @ 15)
Jul 22 18:42:52 Computer org.gnome.Shell.desktop[1110]: == Stack trace for context 0x56392b7d2180 ==
Jul 22 18:42:52 Computer org.gnome.Shell.desktop[1110]: #0 0x7ffeb5bb6c00 b   resource:///org/gnome/shell/ui/tweener.js:80 (0x7f8c3c4c8cd0 @ 82)
Jul 22 18:42:52 Computer org.gnome.Shell.desktop[1110]: #1 0x7ffeb5bb6ca0 b   resource:///org/gnome/shell/ui/tweener.js:105 (0x7f8c3c4c8f78 @ 36)
Jul 22 18:42:52 Computer org.gnome.Shell.desktop[1110]: #2 0x7ffeb5bb6d40 b   resource:///org/gnome/shell/ui/tweener.js:92 (0x7f8c3c4c8de0 @ 52)
Jul 22 18:42:52 Computer org.gnome.Shell.desktop[1110]: #3 0x7ffeb5bb7bd0 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7f8c3c4d2918 @ 54)
Jul 22 18:42:52 Computer org.gnome.Shell.desktop[1110]: #4 0x7ffeb5bb7d20 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7f8c3c4d29a0 @ 1626)
Jul 22 18:42:52 Computer org.gnome.Shell.desktop[1110]: #5 0x7ffeb5bb7dd0 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7f8c3c4d2a28 @ 100)
Jul 22 18:42:52 Computer org.gnome.Shell.desktop[1110]: #6 0x7ffeb5bb7e60 b   resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7f8c3c4d2ab0 @ 10)
Jul 22 18:42:52 Computer org.gnome.Shell.desktop[1110]: #7 0x7ffeb5bb7ee0 I   resource:///org/gnome/gjs/modules/signals.js:128 (0x7f8c3c4cff78 @ 386)
Jul 22 18:42:52 Computer org.gnome.Shell.desktop[1110]: #8 0x7ffeb5bb7f90 b   resource:///org/gnome/shell/ui/tweener.js:207 (0x7f8c3c4cf5e8 @ 159)
Jul 22 18:42:52 Computer org.gnome.Shell.desktop[1110]: #9 0x7ffeb5bb8000 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f8c3c4b5de0 @ 71)
Jul 22 18:42:52 Computer org.gnome.Shell.desktop[1110]: #10 0x7ffeb5bb8000 I   resource:///org/gnome/shell/ui/tweener.js:182 (0x7f8c3c4cf560 @ 15)
Jul 22 18:42:53 Computer gnome-shell[1110]: JS ERROR: TypeError: this._currentWindow is null
                                            _setCurrentRect@resource:///org/gnome/shell/ui/keyboard.js:536:13
                                            wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
                                            _init/<@resource:///org/gnome/shell/ui/keyboard.js:503:13
Jul 22 18:42:53 Computer gnome-shell[1110]: JS ERROR: TypeError: this._currentWindow is null
                                            _setCurrentRect@resource:///org/gnome/shell/ui/keyboard.js:536:13
                                            wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
                                            _init/<@resource:///org/gnome/shell/ui/keyboard.js:503:13
Jul 22 18:42:53 Computer gnome-shell[1110]: JS ERROR: TypeError: this._currentWindow is null
                                            _setCurrentRect@resource:///org/gnome/shell/ui/keyboard.js:536:13
                                            wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
                                            _init/<@resource:///org/gnome/shell/ui/keyboard.js:503:13
Jul 22 18:42:53 Computer gnome-shell[1110]: JS ERROR: TypeError: this._currentWindow is null
                                            _setCurrentRect@resource:///org/gnome/shell/ui/keyboard.js:536:13
                                            wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
                                            _init/<@resource:///org/gnome/shell/ui/keyboard.js:503:13
Jul 22 18:42:53 Computer gnome-shell[1110]: JS ERROR: TypeError: this._currentWindow is null
                                            _setCurrentRect@resource:///org/gnome/shell/ui/keyboard.js:536:13
                                            wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
                                            _init/<@resource:///org/gnome/shell/ui/keyboard.js:503:13
Jul 22 18:42:53 Computer gdm-password][3175]: gkr-pam: unlocked login keyring
Jul 22 18:42:53 Computer /usr/lib/gdm-x-session[1313]: (II) systemd-logind: got resume for 13:70
Jul 22 18:42:53 Computer /usr/lib/gdm-x-session[1313]: (II) systemd-logind: got resume for 13:65
Jul 22 18:42:53 Computer /usr/lib/gdm-x-session[1313]: (II) systemd-logind: got resume for 13:72
Jul 22 18:42:53 Computer /usr/lib/gdm-x-session[1313]: (II) systemd-logind: got resume for 13:82
Jul 22 18:42:53 Computer /usr/lib/gdm-x-session[1313]: (II) systemd-logind: got resume for 13:68
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: (II) systemd-logind: got resume for 13:69
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: (II) systemd-logind: got resume for 13:81
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: (II) systemd-logind: got resume for 226:0
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: (II) AIGLX: Resuming AIGLX clients after VT switch
Jul 22 18:42:54 Computer kernel: rfkill: input handler disabled
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: (II) modeset(0): EDID vendor "AUO", prod id 4204
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: (II) modeset(0): Printing DDC gathered Modelines:
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: (II) modeset(0): Modeline "1366x768"x0.0   69.30  1366 1414 1446 1454  768 771 777 793 -hsync -vsync (47.7 kHz eP)
Jul 22 18:42:54 Computer gsd-color[1532]: failed to set screen _ICC_PROFILE: Datei »/var/lib/gdm/.local/share/icc/edid-7c4f47b635a0342d129ec38f20009786.icc« konnte nicht geöffnet werden: Keine Berechtigung
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: (II) event1  - Sleep Button: is tagged by udev as: Keyboard
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: (II) event1  - Sleep Button: device is a keyboard
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: (II) event4  - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: (II) event4  - AT Translated Set 2 keyboard: device is a keyboard
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: (II) event17 - SynPS/2 Synaptics TouchPad: is tagged by udev as: Touchpad
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: (II) event17 - SynPS/2 Synaptics TouchPad: device is a touchpad
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: (II) event8  - ThinkPad Extra Buttons: is tagged by udev as: Keyboard Switch
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: (II) event8  - ThinkPad Extra Buttons: device is a keyboard
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: (II) event18 - TPPS/2 IBM TrackPoint: is tagged by udev as: Mouse Pointingstick
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: (II) event18 - TPPS/2 IBM TrackPoint: trackpoint does not have a specified range, guessing... see https://wayland.freedesktop.org/libinput/doc/1.11.2/trackpoints.html
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: (II) event18 - TPPS/2 IBM TrackPoint: trackpoint device set to range 31
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: (II) event18 - TPPS/2 IBM TrackPoint: device is a pointer
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: (II) event6  - Full-Speed Mouse Full-Speed Mouse: is tagged by udev as: Keyboard
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: (II) event6  - Full-Speed Mouse Full-Speed Mouse: device is a keyboard
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: (II) event5  - Full-Speed Mouse Full-Speed Mouse: is tagged by udev as: Mouse
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: (II) event5  - Full-Speed Mouse Full-Speed Mouse: device is a pointer
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: (II) systemd-logind: got resume for 13:67
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: (II) event3  - Video Bus: is tagged by udev as: Keyboard
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: (II) event3  - Video Bus: device is a keyboard
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: (II) systemd-logind: got resume for 13:66
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: (II) event2  - Power Button: is tagged by udev as: Keyboard
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: (II) event2  - Power Button: device is a keyboard
Jul 22 18:42:54 Computer gnome-shell[1385]: g_array_unref: assertion 'array' failed
Jul 22 18:42:54 Computer gnome-shell[1385]: g_array_unref: assertion 'array' failed
Jul 22 18:42:54 Computer gnome-shell[1385]: g_array_unref: assertion 'array' failed
Jul 22 18:42:54 Computer gnome-shell[1385]: g_array_unref: assertion 'array' failed
Jul 22 18:42:54 Computer gnome-shell[1385]: g_array_unref: assertion 'array' failed
Jul 22 18:42:54 Computer gnome-shell[1385]: g_array_unref: assertion 'array' failed
Jul 22 18:42:54 Computer gnome-shell[1385]: g_array_unref: assertion 'array' failed
Jul 22 18:42:54 Computer gnome-shell[1385]: g_array_unref: assertion 'array' failed
Jul 22 18:42:54 Computer gnome-shell[1385]: g_array_unref: assertion 'array' failed
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: > Warning:          Unsupported high keycode 372 for name <I372> ignored
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: >                   X11 cannot support keycodes above 255.
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: >                   This warning only shows for the first high keycode.
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: > Internal error:   Could not resolve keysym XF86WWAN
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: > Internal error:   Could not resolve keysym XF86RFKill
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: > Internal error:   Could not resolve keysym XF86Keyboard
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: Errors from xkbcomp are not fatal to the X server
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: > Warning:          Unsupported high keycode 372 for name <I372> ignored
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: >                   X11 cannot support keycodes above 255.
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: >                   This warning only shows for the first high keycode.
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: > Internal error:   Could not resolve keysym XF86WWAN
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: > Internal error:   Could not resolve keysym XF86RFKill
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: > Internal error:   Could not resolve keysym XF86Keyboard
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: Errors from xkbcomp are not fatal to the X server
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: > Warning:          Unsupported high keycode 372 for name <I372> ignored
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: >                   X11 cannot support keycodes above 255.
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: >                   This warning only shows for the first high keycode.
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: > Internal error:   Could not resolve keysym XF86WWAN
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: > Internal error:   Could not resolve keysym XF86RFKill
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: > Internal error:   Could not resolve keysym XF86Keyboard
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: Errors from xkbcomp are not fatal to the X server
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: > Warning:          Unsupported high keycode 372 for name <I372> ignored
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: >                   X11 cannot support keycodes above 255.
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: >                   This warning only shows for the first high keycode.
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: > Internal error:   Could not resolve keysym XF86WWAN
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: > Internal error:   Could not resolve keysym XF86RFKill
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: > Internal error:   Could not resolve keysym XF86Keyboard
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: Errors from xkbcomp are not fatal to the X server
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: > Warning:          Unsupported high keycode 372 for name <I372> ignored
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: >                   X11 cannot support keycodes above 255.
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: >                   This warning only shows for the first high keycode.
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: > Internal error:   Could not resolve keysym XF86WWAN
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: > Internal error:   Could not resolve keysym XF86RFKill
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: > Internal error:   Could not resolve keysym XF86Keyboard
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: Errors from xkbcomp are not fatal to the X server
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: The XKEYBOARD keymap compiler (xkbcomp) reports:
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: > Warning:          Unsupported high keycode 372 for name <I372> ignored
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: >                   X11 cannot support keycodes above 255.
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: >                   This warning only shows for the first high keycode.
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: > Internal error:   Could not resolve keysym XF86WWAN
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: > Internal error:   Could not resolve keysym XF86RFKill
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: > Internal error:   Could not resolve keysym XF86Keyboard
Jul 22 18:42:54 Computer /usr/lib/gdm-x-session[1313]: Errors from xkbcomp are not fatal to the X server
Jul 22 18:42:55 Computer /usr/lib/gdm-x-session[1313]: (EE) client bug: timer event17 trackpoint: offset negative (-204ms)

The journal is pretty long (~33.000 lines!), but they are mostly repeating. So I just posted the last few lines...

What I found out by now, ist that the problem seems to be connected to "tracker". There are 6 processes running, 3 for each user. If I kill mine I can login again, but that's more of a workaround than a fix... Searching for this error-message I only find an empty bug report.

It seems I have another problem with owncloud, but I think I have to keep it for another thread wink

Offline

Pages: 1

Board footer

Powered by FluxBB