sorry this is the out come of journalctl /usr/bin/gnome-shell

-- Logs begin at Fri 2018-04-27 22:06:06 EEST, end at Fri 2018-05-18
21:03:51 EE
huhti 27 22:06:13 ThinkPad-X301 org.gnome.Shell.desktop[762]: glamor: EGL
versio
huhti 27 22:06:16 ThinkPad-X301 gnome-shell[762]: JS WARNING:
[resource:///org/g
huhti 27 22:06:16 ThinkPad-X301 gnome-shell[762]: JS WARNING:
[resource:///org/g
huhti 27 22:06:16 ThinkPad-X301 gnome-shell[762]: JS WARNING:
[resource:///org/g
huhti 27 22:06:17 ThinkPad-X301 gnome-shell[762]: JS WARNING:
[resource:///org/g
huhti 27 22:06:19 ThinkPad-X301 gnome-shell[762]: Error looking up
permission: G
huhti 27 22:06:19 ThinkPad-X301 gnome-shell[762]:
nma_mobile_providers_database_
huhti 27 22:06:20 ThinkPad-X301 gnome-shell[762]: JS WARNING:
[resource:///org/g
huhti 27 22:06:44 ThinkPad-X301 gnome-shell[1812]: JS WARNING:
[resource:///org/
huhti 27 22:06:44 ThinkPad-X301 gnome-shell[1812]: JS WARNING:
[resource:///org/
huhti 27 22:06:44 ThinkPad-X301 gnome-shell[1812]: JS WARNING:
[resource:///org/
huhti 27 22:06:46 ThinkPad-X301 gnome-shell[1812]: JS WARNING:
[resource:///org/
huhti 27 22:06:46 ThinkPad-X301 gnome-shell[1812]: Telepathy is not
available, c
huhti 27 22:06:49 ThinkPad-X301 gnome-shell[1812]: JS WARNING:
[/usr/share/gnome
huhti 27 22:06:54 ThinkPad-X301 gnome-shell[1812]:
[AppIndicatorSupport-DEBUG] R
huhti 27 22:06:56 ThinkPad-X301 gnome-shell[1812]: Object St.BoxLayout
(0x561a90
huhti 27 22:06:56 ThinkPad-X301 org.gnome.Shell.desktop[1812]: == Stack
trace fo
huhti 27 22:06:56 ThinkPad-X301 org.gnome.Shell.desktop[1812]: #0
0x7ffff3031450
huhti 27 22:06:56 ThinkPad-X301 org.gnome.Shell.desktop[1812]: #1
0x7ffff30314b0
huhti 27 22:06:56 ThinkPad-X301 org.gnome.Shell.desktop[1812]: #2
0x7ffff3031580
huhti 27 22:06:56 ThinkPad-X301 org.gnome.Shell.desktop[1812]: #3
0x7ffff30315f0
huhti 27 22:06:56 ThinkPad-X301 org.gnome.Shell.desktop[1812]: #4
0x561a8f6df7a0


pe 18. toukok. 2018 klo 21.01 Heikki Moisander (<email address hidden>)
kirjoitti:

> Not sure what came out but this is out come of running journalctl right
> after booting after freeze.
> I need clear guidance to get something else more relevant.
>
> Logs begin at Fri 2018-04-27 22:06:06 EEST, end at Fri 2018-05-18 20:56:33
> EE
> huhti 27 22:06:06 ThinkPad-X301 kernel: Linux version 4.15.0-20-generic
> (buildd@
> huhti 27 22:06:06 ThinkPad-X301 kernel: Command line:
> BOOT_IMAGE=/boot/vmlinuz-4
> huhti 27 22:06:06 ThinkPad-X301 kernel: KERNEL supported cpus:
> huhti 27 22:06:06 ThinkPad-X301 kernel:   Intel GenuineIntel
> huhti 27 22:06:06 ThinkPad-X301 kernel:   AMD AuthenticAMD
> huhti 27 22:06:06 ThinkPad-X301 kernel:   Centaur CentaurHauls
> huhti 27 22:06:06 ThinkPad-X301 kernel: Disabled fast string operations
> huhti 27 22:06:06 ThinkPad-X301 kernel: x86/fpu: x87 FPU will use FXSAVE
> huhti 27 22:06:06 ThinkPad-X301 kernel: e820: BIOS-provided physical RAM
> map:
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x0000000000000000-0x000
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x000000000009ec00-0x000
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x00000000000dc000-0x000
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x0000000000100000-0x000
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x00000000bd6a1000-0x000
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x00000000bd6a7000-0x000
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x00000000bd7b7000-0x000
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x00000000bd80f000-0x000
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x00000000bd8c7000-0x000
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x00000000bd8d2000-0x000
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x00000000bd8d5000-0x000
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x00000000bd8d9000-0x000
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x00000000bd8dd000-0x000
> lines 1-23...skipping...
> -- Logs begin at Fri 2018-04-27 22:06:06 EEST, end at Fri 2018-05-18
> 20:56:33 EEST. --
> huhti 27 22:06:06 ThinkPad-X301 kernel: Linux version 4.15.0-20-generic
> (buildd@lgw01-amd64-039) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3))
> #21-Ubunt
> huhti 27 22:06:06 ThinkPad-X301 kernel: Command line:
> BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic
> root=UUID=bf89dfab-58a9-4161-a23c-18da35c20198 ro quie
> huhti 27 22:06:06 ThinkPad-X301 kernel: KERNEL supported cpus:
> huhti 27 22:06:06 ThinkPad-X301 kernel:   Intel GenuineIntel
> huhti 27 22:06:06 ThinkPad-X301 kernel:   AMD AuthenticAMD
> huhti 27 22:06:06 ThinkPad-X301 kernel:   Centaur CentaurHauls
> huhti 27 22:06:06 ThinkPad-X301 kernel: Disabled fast string operations
> huhti 27 22:06:06 ThinkPad-X301 kernel: x86/fpu: x87 FPU will use FXSAVE
> huhti 27 22:06:06 ThinkPad-X301 kernel: e820: BIOS-provided physical RAM
> map:
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x0000000000000000-0x000000000009ebff] usable
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x000000000009ec00-0x000000000009ffff] reserved
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x00000000000dc000-0x00000000000fffff] reserved
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x0000000000100000-0x00000000bd6a0fff] usable
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x00000000bd6a1000-0x00000000bd6a6fff] reserved
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x00000000bd6a7000-0x00000000bd7b6fff] usable
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x00000000bd7b7000-0x00000000bd80efff] reserved
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x00000000bd80f000-0x00000000bd8c6fff] usable
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x00000000bd8c7000-0x00000000bd8d1fff] ACPI NVS
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x00000000bd8d2000-0x00000000bd8d4fff] ACPI data
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x00000000bd8d5000-0x00000000bd8d8fff] reserved
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x00000000bd8d9000-0x00000000bd8dcfff] ACPI NVS
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x00000000bd8dd000-0x00000000bd8dffff] reserved
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x00000000bd8e0000-0x00000000bd906fff] ACPI NVS
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x00000000bd907000-0x00000000bd907fff] ACPI data
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x00000000bd908000-0x00000000bdb0efff] reserved
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x00000000bdb0f000-0x00000000bdb9efff] ACPI NVS
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x00000000bdb9f000-0x00000000bdbfefff] ACPI data
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x00000000bdbff000-0x00000000bdbfffff] usable
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x00000000bdc00000-0x00000000bfffffff] reserved
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x00000000e0000000-0x00000000efffffff] reserved
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x00000000fec00000-0x00000000fec0ffff] reserved
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x00000000fed00000-0x00000000fed003ff] reserved
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x00000000fed10000-0x00000000fed13fff] reserved
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x00000000fed18000-0x00000000fed19fff] reserved
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x00000000fed1c000-0x00000000fed8ffff] reserved
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x00000000fee00000-0x00000000fee00fff] reserved
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x00000000ff800000-0x00000000ffffffff] reserved
> huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem
> 0x0000000100000000-0x000000013bffffff] usable
> huhti 27 22:06:06 ThinkPad-X301 kernel: NX (Execute Disable) protection:
> active
> huhti 27 22:06:06 ThinkPad-X301 kernel: random: fast init done
> huhti 27 22:06:06 ThinkPad-X301 kernel: SMBIOS 2.4 present.
> huhti 27 22:06:06 ThinkPad-X301 kernel: DMI: LENOVO 4057WFG/4057WFG, BIOS
> 6EET27WW (1.08 ) 03/12/2009
> huhti 27 22:06:06 ThinkPad-X301 kernel: e820: update [mem
> 0x00000000-0x00000fff] usable ==> reserved
> lines 1-44
>
>
> pe 18. toukok. 2018 klo 20.31 Marco Trevisan (Treviño) (mail@3v1n0.net)
> kirjoitti:
>
>> Looks weird, can you attach the output of
>>   journalctl /usr/bin/gnome-shell
>>
>> ?
>>
>> --
>> You received this bug notification because you are subscribed to a
>> duplicate bug report (1768619).
>> https://bugs.launchpad.net/bugs/1766137
>>
>> Title:
>>   [regression] Password accepted but login fails (blank purple screen
>>   and mouse pointer only)
>>
>> Status in gdm:
>>   Fix Released
>> Status in Release Notes for Ubuntu:
>>   Fix Released
>> Status in gdm3 package in Ubuntu:
>>   Fix Released
>> Status in gnome-shell package in Ubuntu:
>>   Invalid
>> Status in gdm3 source package in Bionic:
>>   Fix Committed
>> Status in gnome-shell source package in Bionic:
>>   Invalid
>>
>> Bug description:
>>   [ Description ]
>>
>>   Due to a refcounting bug, a GDBusConnection was getting disposed when
>>   it was still required. The symptom of this was that you couldn't log
>>   in if you'd got your password wrong.
>>
>>   [ Test case ]
>>
>>   1. Boot to GDM
>>   2. Click your username
>>   3. Type the wrong password a couple of times, pressing enter after each
>> time
>>   4. Type the right password
>>
>>   If the bug is happening, after 4. the system hangs at a blank screen
>>   with the mouse cursor. If you then switch to a VT or otherwise connect
>>   to the machine, you can examine the journal and you'll see a
>>   G_IS_DBUS_CONNECTION failure.
>>
>>   [ Fix ]
>>
>>   Marco and I worked upstream on this fix. We found out that there was a
>>   problem like this-
>>
>>   The GdmClient has a shared GDBusConnection for its operations. The
>>   first time  someone calls for it, it is created and stored in the
>>   object's private structure. Subsequent calls return *a new reference*
>>   to this same object. It turned out that the asynchronous method to get
>>   the connection was accidentally unreferencing its object before giving
>>   it to the caller if it was returning an already-existing connection.
>>
>>   For this to work properly, we need to nullify the pointer we stored
>>   when the connection goes away, so we know when to make a new one.
>>   There were some cases where we didn't add the weak references required
>>   to do that. Those are also fixed.
>>
>>   [ Regression potential ]
>>
>>   Now we share connections more than we did before. We also more
>>   carefully track when to clear our object. If we got this wrong, we
>>   might end up leaking the connection or dropping it in even more cases.
>>
>>   [ Original report ]
>>
>>
>>   WORKAROUND: After typing an incorrect password, click Cancel, then
>> click your name, then enter your password again.
>>
>>   ---
>>
>>   Trying to log into my session (Gnome, Xorg), if I enter the wrong
>>   password before entering it correctly, the session doesn't load and I
>>   get a purple screen, a mouse cursor, and an invisible but clickable
>>   menu in the top right. If I enter it correctly the first time, there
>>   is no problem.
>>
>>   I've replicated this from a fresh boot, after logging out and after
>>   'sudo service gdm restart' from the Ctrl-Alt-F4 console.
>>
>>   This is a fresh install, and didn't occur when I was using a previous
>>   install of 18.04 (until Friday).
>>
>>   ProblemType: Bug
>>   DistroRelease: Ubuntu 18.04
>>   Package: gdm3 3.28.0-0ubuntu1
>>   ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
>>   Uname: Linux 4.15.0-15-generic x86_64
>>   ApportVersion: 2.20.9-0ubuntu6
>>   Architecture: amd64
>>   CurrentDesktop: ubuntu:GNOME
>>   Date: Sun Apr 22 20:31:13 2018
>>   InstallationDate: Installed on 2018-04-22 (0 days ago)
>>   InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64
>> (20180421.1)
>>   SourcePackage: gdm3
>>   UpgradeStatus: No upgrade log present (probably fresh install)
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/gdm/+bug/1766137/+subscriptions
>>
>