Genymotion pára de funcionar no Ubuntu 16.04

0

Depois de alocar meu sistema (Ubuntu 16.04) no data center, de repente meu Genymotion parou de funcionar seguindo o seguinte erro:

Logging activities to file: /home/*/.Genymobile/genymotion.log (noting logged here)
Segmentation fault (core dumped)

Então eu re-instalo, mas ainda tenho o mesmo problema .... Então eu verifiquei o Virtualbox seguindo:

$ sudo /etc/init.d/vboxdrv status
sudo: /etc/init.d/vboxdrv: command not found

Por isso, resolvi desinstalar os dois e instalá-los novamente. mas o problema ainda existe

Aqui está o que eu fiz:

instalando o Virtualbox e o pacote relacionado:

$ sudo dpkg -i virtualbox-5.1_5.1.16-1138411~Ubuntu~xenial_amd64.deb (downloaded from virtualbox.org)

Selecting previously unselected package virtualbox-5.1.
(Reading database ... 246386 files and directories currently installed.)
Preparing to unpack virtualbox-5.1_5.1.16-113841~Ubuntu~xenial_amd64.deb ...
Unpacking virtualbox-5.1 (5.1.16-113841~Ubuntu~xenial) ...
Setting up virtualbox-5.1 (5.1.16-113841~Ubuntu~xenial) ...
addgroup: The group 'vboxusers' already exists as a system group. Exiting.
Processing triggers for systemd (229-4ubuntu17) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
Processing triggers for shared-mime-info (1.5-2ubuntu0.1) ...
Processing triggers for desktop-file-utils (0.22-1ubuntu5.1) ...
Processing triggers for gnome-menus (3.13.3-6ubuntu3.1) ...
Processing triggers for bamfdaemon (0.5.3~bzr0+16.04.20160824-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for mime-support (3.59ubuntu1) ...

$ sudo apt-get install -f

Reading package lists... Done
Building dependency tree       
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 162 not upgraded.

$ sudo apt-get install dkms

Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following NEW packages will be installed:
  dkms
0 upgraded, 1 newly installed, 0 to remove and 162 not upgraded.
Need to get 0 B/66.1 kB of archives.
After this operation, 265 kB of additional disk space will be used.
Selecting previously unselected package dkms.
(Reading database ... 247164 files and directories currently installed.)
Preparing to unpack .../dkms_2.2.0.3-2ubuntu11.3_all.deb ...
Unpacking dkms (2.2.0.3-2ubuntu11.3) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up dkms (2.2.0.3-2ubuntu11.3) ...

$ sudo /usr/src/linux-headers-$(uname -r)/s
scripts/sign-file sha256 ./MOK.priv ./MOK.der $(modinfo -n vboxdrv)

$ sudo /etc/init.d/vboxdrv status
sudo: /etc/init.d/vboxdrv: command not found

$ sudo apt-get install linux-headers-'uname -r'

Reading package lists... Done
Building dependency tree       
Reading state information... Done
linux-headers-4.10.0-30-generic is already the newest version (4.10.0-30.34~16.04.1).
0 upgraded, 0 newly installed, 0 to remove and 162 not upgraded.

Instale e execute o Genymotion:

$ ./genymotion-2.8.1_x64.bin -d /opt/

    Installing for all users.        
    Installing to folder [/opt/genymotion]. Are you sure [y/n] ? y      
    - Trying to find VirtualBox toolset .................... OK (Valid version of VirtualBox found: 5.1.16r113841)
    - Extracting files ..................................... OK (Extract into: [/opt/genymotion])
    - Installing launcher icon ............................. OK
    Installation done successfully.        
    You can now use these tools from [/opt/genymotion]:
     - genymotion
     - genymotion-shell
     - gmtool

$ /opt/genymotion/genymotion
Logging activities to file: /home/*/.Genymobile/genymotion.log
Segmentation fault (core dumped)

Eu tentei seguir, mas o erro ainda está disponível:

$ sudo apt-get install build-essential module-assistant     
Reading package lists... Done
Building dependency tree
Reading state information... Done
build-essential is already the newest version (12.1ubuntu2).
module-assistant is already the newest version (0.11.8).
0 upgraded, 0 newly installed, 0 to remove and 162 not upgraded.

$ sudo m-a prepare
Getting source for kernel version: 4.10.0-30-generic
Kernel headers available in /usr/src/linux-headers-4.10.0-30-generic
Creating symlink...
apt-get install build-essential 
Reading package lists... Done
Building dependency tree
Reading state information... Done
build-essential is already the newest version (12.1ubuntu2).
0 upgraded, 0 newly installed, 0 to remove and 162 not upgraded.
Done!

$ sudo /etc/init.d/vboxdrv setup
sudo: /etc/init.d/vboxdrv: command not found

aqui é o resultado de /etc/init.d/virtualbox status :

virtualbox.service - LSB: VirtualBox Linux kernel module
   Loaded: loaded (/etc/init.d/virtualbox; bad; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2017-08-09 23:51:09 IRDT; 12h ago
     Docs: man:systemd-sysv-generator(8)

Aug 09 23:51:09 *-G31M-ES2C virtualbox[31835]:  * Loading VirtualBox kern...
Aug 09 23:51:09 *-G31M-ES2C virtualbox[31835]:  * No suitable module for ...
Aug 09 23:51:09 *-G31M-ES2C virtualbox[31835]:    ...fail!
Aug 09 23:51:09 *-G31M-ES2C systemd[1]: virtualbox.service: Control proc...1
Aug 09 23:51:09 *-G31M-ES2C systemd[1]: Failed to start LSB: VirtualBox ....
Aug 09 23:51:09 *-G31M-ES2C systemd[1]: virtualbox.service: Unit entered....
Aug 09 23:51:09 *-G31M-ES2C systemd[1]: virtualbox.service: Failed with ....
Aug 10 00:04:22 *-G31M-ES2C systemd[1]: Stopped LSB: VirtualBox Linux ke....
Aug 10 00:08:51 *-G31M-ES2C systemd[1]: Stopped LSB: VirtualBox Linux ke....
Aug 10 00:23:30 *-G31M-ES2C systemd[1]: Stopped LSB: VirtualBox Linux ke....
Hint: Some lines were ellipsized, use -l to show in full.

Eu apenas reinicio o sistema e aqui está o resultado novamente:

$ sudo /etc/init.d/virtualbox status
● virtualbox.service - LSB: VirtualBox Linux kernel module
   Loaded: loaded (/etc/init.d/virtualbox; bad; vendor preset: enabled)
   Active: active (exited) since Thu 2017-08-10 12:15:37 IRDT; 4min 14s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 1107 ExecStart=/etc/init.d/virtualbox start (code=exited, status=0/SUCCESS)

Aug 10 12:15:37 *-G31M-ES2C systemd[1]: Starting LSB: VirtualBox Linux k....
Aug 10 12:15:37 *-G31M-ES2C systemd[1]: Started LSB: VirtualBox Linux ke....
Hint: Some lines were ellipsized, use -l to show in full.

$ opt/genymotion/genymotion
Logging activities to file: /home/*/.Genymobile/genymotion.log (still empty)
Segmentation fault (core dumped)

Descobri que o seguinte comando é o mesmo que /etc/init.d/vboxdrv setup|status ( referência )

 /sbin/rcvboxdrv setup|status

aqui está o resultado:

VirtualBox kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) are loaded

Eu também tento solução em Problema com a execução do genymotion na área de trabalho do KDE mas recebo o seguinte erro:

Logging activities to file: /home/*/.Genymobile/genymotion.log (noting logged here)
    Aborted (core dumped)

e aqui está o arquivo * .log:

Aug 11 01:40:08 [genymotion] [fatal] This application failed to start because it could not find or load the Qt platform plugin "xcb".

Reinstalling the application may fix this problem.

Também verifico a biblioteca necessária para o Qt, conforme declarado em aqui , mas anotando o resultado, então todo o lib necessário está disponível.

Editar 1

Eu encontre aquele sistema com systemd despejado do núcleo para /var/lib/systemd/coredump/ , então primeiro eu instalo coredumpctl e então executo Genymotion para criar o dump principal. Siga as instruções aqui para criar dump.core , aqui está o resultado:

$ coredumpctl dump 9808 --output /home/*/genymotion.core     

    PID: 9808(genymotion)
           UID: 1000 (*)
           GID: 1000 (*)
        Signal: 6 (ABRT)
     Timestamp: Fri 2017-08-11 12:37:29 IRDT (4min 58s ago)
  Command Line: /opt/genymotion/genymotion
    Executable: /opt/genymotion/genymotion
 Control Group: /user.slice/user-1000.slice/session-c2.scope
          Unit: session-c2.scope
         Slice: user-1000.slice
       Session: c2
     Owner UID: 1000 (*)
       Boot ID: f572250f03be48d9aa9facf22d0ffd0a
    Machine ID: *******
      Hostname: *-G31M-ES2C
      Coredump: /var/lib/systemd/coredump/core.genymotion.1000.f572250f03be48d9aa9facf22d0ffd0a.9808.1502438849000000000000.xz
       Message: Process 9808 (genymotion) of user 1000 dumped core.

                Stack trace of thread 9808:
                #0  0x00007f86f96c2428 __GI_raise (libc.so.6)
                #1  0x00007f86f96c402a __GI_abort (libc.so.6)
                #2  0x00000000004b6fb7 n/a (genymotion)
                #3  0x00007f86fa74f468 n/a (libQt5Core.so.5)
                #4  0x00007f86fa750f69 _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5)
                #5  0x00007f86fac80e99 _ZN22QGuiApplicationPrivate25createPlatformIntegrationEv (libQt5Gui.so.5)
                #6  0x00007f86fac80ecd _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt5Gui.so.5)
                #7  0x00007f86fa9487e6 _ZN16QCoreApplication4initEv (libQt5Core.so.5)
                #8  0x00007f86fa948856 _ZN16QCoreApplicationC1ER23QCoreApplicationPrivate (libQt5Core.so.5)
                #9  0x00007f86fac82cc9 _ZN15QGuiApplicationC1ER22QGuiApplicationPrivate (libQt5Gui.so.5)
                #10 0x00007f86fa18ebcd _ZN12QApplicationC2ERiPPci (libQt5Widgets.so.5)
                #11 0x0000000000438c53 n/a (genymotion)
                #12 0x000000000042373e n/a (genymotion)
                #13 0x00007f86f96ad830 __libc_start_main (libc.so.6)
                #14 0x0000000000429739 n/a (genymotion)
More than one entry matches, ignoring rest.

e, em seguida, execute o seguinte: @kenorb disse:

$ gdb -c genymotion.core

GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".
[New LWP 9808]
Core was generated by '/opt/genymotion/genymotion'.
Program terminated with signal SIGABRT, Aborted.
#0  0x00007f86f96c2428 in ?? ()
(gdb) bt
#0  0x00007f86f96c2428 in ?? ()
#1  0x00007f86f96c402a in ?? ()
#2  0x0000000000000020 in ?? ()
#3  0x0000000000000000 in ?? ()
(gdb) bt full
#0  0x00007f86f96c2428 in ?? ()
No symbol table info available.
#1  0x00007f86f96c402a in ?? ()
No symbol table info available.
#2  0x0000000000000020 in ?? ()
No symbol table info available.
#3  0x0000000000000000 in ?? ()
No symbol table info available.

Editar 2

Eu removi o builtin qt no Genymotion e verifiquei o qt disponível no meu sistema:

$ qtchooser -list-versions
4
5
default
qt4-x86_64-linux-gnu
qt4
qt5-x86_64-linux-gnu
qt5

mas ainda não conseguiu iniciar o Genymotion.

Eu também instalo o qt-5.9.1 baixando qt-unified-linux-x64-3.0.0-online do aqui mas isso não acontece listar quando eu executar qtchooser -list-versions . (nenhuma versão mais nova estava disponível), como devo forçar o trabalho do Genymotion com isso?

Editar 3

A solução não funcionou para mim. Eu resolvi reinstalar o sistema operacional. Agora tudo está bem. mas depois de reiniciar o sistema Genymotion falhou novamente.

    
por user3933607 10.08.2017 / 08:30

1 resposta

0

O seu acidente parece estar relacionado com o quadro do Qt ( libQt5Gui.so.5 ). Estas são as linhas reveladoras:

   Stack trace of thread 9808:
    #0  0x00007f86f96c2428 __GI_raise (libc.so.6)
    #1  0x00007f86f96c402a __GI_abort (libc.so.6)
    #2  0x00000000004b6fb7 n/a (genymotion)
    #3  0x00007f86fa74f468 n/a (libQt5Core.so.5)
    #4  0x00007f86fa750f69 _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5)
    #5  0x00007f86fac80e99 _ZN22QGuiApplicationPrivate25createPlatformIntegrationEv (libQt5Gui.so.5)
    #6  0x00007f86fac80ecd _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt5Gui.so.5)
    #7  0x00007f86fa9487e6 _ZN16QCoreApplication4initEv (libQt5Core.so.5)
    #8  0x00007f86fa948856 _ZN16QCoreApplicationC1ER23QCoreApplicationPrivate (libQt5Core.so.5)
    #9  0x00007f86fac82cc9 _ZN15QGuiApplicationC1ER22QGuiApplicationPrivate (libQt5Gui.so.5)
    #10 0x00007f86fa18ebcd _ZN12QApplicationC2ERiPPci (libQt5Widgets.so.5)

A pesquisa por _ZNK14QMessageLogger5fatalEPKcz fornece alguns problemas semelhantes a essa biblioteca.

Por favor, veja o seguinte bug:

que sugerem que este problema acontece no Qt 5.5.1-9, porém não no 5.5.1-7 (ou -8). Então você pode tentar atualizar ou fazer o downgrade do seu Qt.

Outra solução para tentar é remover o arquivo /var/lib/sddm/.cache , de acordo com este comentário .

Idealmente, se você pudesse atualizar seu Qt para a última versão disponível , caso contrário, tente instalá-lo manualmente ( 5.9.2 ou superior) para substituir sua biblioteca de arquivos libQt5Gui.so.5 defeituosa, ou construir a partir do código fonte .

    
por kenorb 16.08.2017 / 23:20