Comment 37 for bug 1690502

Hello Mr. Zheng.

I have the same issue since I reported this bug.

Now I have these messages:

-- Logs begin at Mon 2017-02-20 21:07:06 -05, end at Sun 2017-06-04 07:06:49 -05. --
Jun 04 06:54:58 soporte.fedora.local kernel: ACPI Error: Needed type [Reference], found [Integer] ffff9c9e20108a68 (20170119/exresop-103)
Jun 04 06:54:58 soporte.fedora.local kernel: ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20170119/dswe
Jun 04 06:54:58 soporte.fedora.local kernel: ACPI Error: Method parse/execution failed [\_PR.CPU0._PDC] (Node ffff9c9e225022d0), AE_AML_OPERAND_TYPE (
Jun 04 06:54:59 soporte.fedora.local kernel: ACPI Exception: AE_AML_PACKAGE_LIMIT, Index (0x000000003) is beyond end of object (length 0x0) (20170119/
Jun 04 06:54:59 soporte.fedora.local kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.GFX0._DSM] (Node ffff9c9e224c5168), AE_AML_PACKAGE_L
Jun 04 06:54:59 soporte.fedora.local kernel: ACPI Exception: AE_AML_PACKAGE_LIMIT, Index (0x000000003) is beyond end of object (length 0x0) (20170119/
Jun 04 06:54:59 soporte.fedora.local kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.GFX0._DSM] (Node ffff9c9e224c5168), AE_AML_PACKAGE_L
Jun 04 06:54:59 soporte.fedora.local kernel: ACPI Error: Method parse/execution failed [\_SB.PCI0.PEG0.PEGP._DSM] (Node ffff9c9e224df9b0), AE_AML_PACK
Jun 04 06:55:01 soporte.fedora.local systemd[1]: systemd-rfkill.socket: Socket service systemd-rfkill.service not loaded, refusing.
Jun 04 06:55:01 soporte.fedora.local systemd[1]: Failed to listen on Load/Save RF Kill Switch Status /dev/rfkill Watch.
Jun 04 06:55:04 soporte.fedora.local systemd[1]: Failed to start SYSV: This service starts and stops VMware services.
Jun 04 06:55:06 soporte.fedora.local gdm-launch-environment][1400]: PAM unable to dlopen(/usr/lib64/security/pam_oddjob_mkhomedir.so): /usr/lib64/secu
Jun 04 06:55:06 soporte.fedora.local gdm-launch-environment][1400]: PAM adding faulty module: /usr/lib64/security/pam_oddjob_mkhomedir.so
Jun 04 06:55:06 soporte.fedora.local systemd[1410]: PAM unable to dlopen(/usr/lib64/security/pam_oddjob_mkhomedir.so): /usr/lib64/security/pam_oddjob_
Jun 04 06:55:06 soporte.fedora.local systemd[1410]: PAM adding faulty module: /usr/lib64/security/pam_oddjob_mkhomedir.so
Jun 04 06:55:08 soporte.fedora.local spice-vdagent[1764]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
Jun 04 06:55:30 soporte.fedora.local gdm-password][1961]: PAM unable to dlopen(/usr/lib64/security/pam_oddjob_mkhomedir.so): /usr/lib64/security/pam_o
Jun 04 06:55:30 soporte.fedora.local gdm-password][1961]: PAM adding faulty module: /usr/lib64/security/pam_oddjob_mkhomedir.so
Jun 04 06:55:32 soporte.fedora.local systemd[1971]: PAM unable to dlopen(/usr/lib64/security/pam_oddjob_mkhomedir.so): /usr/lib64/security/pam_oddjob_
Jun 04 06:55:32 soporte.fedora.local systemd[1971]: PAM adding faulty module: /usr/lib64/security/pam_oddjob_mkhomedir.so
Jun 04 06:55:33 soporte.fedora.local pkexec[2008]: PAM unable to dlopen(/usr/lib64/security/pam_oddjob_mkhomedir.so): /usr/lib64/security/pam_oddjob_m
Jun 04 06:55:33 soporte.fedora.local pkexec[2008]: PAM adding faulty module: /usr/lib64/security/pam_oddjob_mkhomedir.so
Jun 04 06:55:34 soporte.fedora.local pulseaudio[2113]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.systemd1.NoSuchUnit: Un
Jun 04 06:55:35 soporte.fedora.local spice-vdagent[2215]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
Jun 04 06:55:35 soporte.fedora.local vmusr[2232]: [Jun 04 06:55:35.481] [ error] [Gdk] The program 'vmware-user' received an X Window System error.
                                                  This probably reflects a bug in the program.
                                                  The error was 'BadWindow (invalid Window parameter)'.
                                                    (Details: serial 137 error_code 3 request_code 20 minor_code 0)
                                                    (Note to programmers: normally, X errors are reported asynchronously;
                                                     that is, you will receive the error a while after causing it.
                                                     To debug your program, run it with the --sync command line
                                                     option to change this behavior. You can then get a meaningful
                                                     backtrace from your debugger if you break on the gdk_x_error() function.)
Jun 04 06:55:35 soporte.fedora.local abrt-hook-ccpp[2286]: Process 2232 (vmtoolsd) of user 1000 killed by SIGABRT - dumping core
Jun 04 07:01:11 soporte.fedora.local gnome-session-binary[2018]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
lines 1-36

Could anyone help us really?