PDA

View Full Version : Qtcreator crash at startup on xubuntu



gerardpuducul
29th April 2014, 09:13
Hi all,

I had installed QT 5.2.1 on my xubuntu 14.04

I had download qt-opensource-linux-x86-1.5.0-2-online.run

sudo su

chmod +x on this file

then chown root:root on it

and finally run it

THe installation seems OK. Qt has been installed in /opt/Qt/

BUt when I start Qtcreator it crash!!!

ERROR: apport (pid 1782) Tue Apr 29 08:35:54 2014: called for pid 1776, signal 11, core limit 0
ERROR: apport (pid 1782) Tue Apr 29 08:35:54 2014: executable: /opt/Qt/Tools/QtCreator/bin/qtcreator (command line "/opt/Qt/Tools/QtCreator/bin/qtcreator")
ERROR: apport (pid 1782) Tue Apr 29 08:35:54 2014: gdbus call error: Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnkn own: The name org.gnome.SessionManager was not provided by any .service files

ERROR: apport (pid 1782) Tue Apr 29 08:35:54 2014: debug: session gdbus call:
ERROR: apport (pid 1782) Tue Apr 29 08:35:55 2014: wrote report /var/crash/_opt_Qt_Tools_QtCreator_bin_qtcreator.1000.crash

What's wrong?

thanks

gerardpuducul
12th May 2014, 15:51
No One can help me please?

Thanks

anda_skoa
12th May 2014, 16:39
Does the Ubuntu crash tool support any kind of details? A backtrace maybe?
Any other indication what might have done wrong?

Cheers,
_

gerardpuducul
15th May 2014, 13:51
Hi and thanks to take care of me.

I had finally something working.

I control my xubuntu machine through vnc. I use RealVNC and specialy vncserver-x11. In this configuration i had a resolution of 800x600. With this setup, Qcreator don't start.

If I setup a new vnc server with vcnserver-virtaul and with different resolution 1440x900, now I can launch Qtcreator in this vnc session.

DOn't know if the problem come from the vncserver or the resolution...............



Does the Ubuntu crash tool support any kind of details? A backtrace maybe?

How can i retrieve these information?

Thanks

Melebius
7th May 2015, 09:45
Hi, I’m getting a similar problem in Xubuntu. In my case, not only Qt Creator crashes when starting, it breaks down the whole VirtualBox application in which the Xubuntu is running. Qt Creator runs well in GNOME Metacity GUI.

Host specs
Windows 7 Professional, 32bit, SP1
VirtualBox 4.3.24 r98716

Guest specs
Ubuntu 14.04.1 LTS, 32bit (with packages xubuntu-desktop, gnome-session-flashback)
Qt Creator 3.1.1-0ubuntu4

Output of the Qt Creator process
libGL error: pci id for fd 28: 80ee:beef, driver (null)
OpenGL Warning: glFlushVertexArrayRangeNV not found in mesa table
OpenGL Warning: glVertexArrayRangeNV not found in mesa table
OpenGL Warning: glCombinerInputNV not found in mesa table
OpenGL Warning: glCombinerOutputNV not found in mesa table
OpenGL Warning: glCombinerParameterfNV not found in mesa table
OpenGL Warning: glCombinerParameterfvNV not found in mesa table
OpenGL Warning: glCombinerParameteriNV not found in mesa table
OpenGL Warning: glCombinerParameterivNV not found in mesa table
OpenGL Warning: glFinalCombinerInputNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterfvNV not found in mesa table
OpenGL Warning: glGetCombinerOutputParameterivNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterfvNV not found in mesa table
OpenGL Warning: glGetFinalCombinerInputParameterivNV not found in mesa table
OpenGL Warning: glDeleteFencesNV not found in mesa table
OpenGL Warning: glFinishFenceNV not found in mesa table
OpenGL Warning: glGenFencesNV not found in mesa table
OpenGL Warning: glGetFenceivNV not found in mesa table
OpenGL Warning: glIsFenceNV not found in mesa table
OpenGL Warning: glSetFenceNV not found in mesa table
OpenGL Warning: glTestFenceNV not found in mesa table
libGL error: core dri or dri2 extension not found
libGL error: failed to load driver: vboxvideo
OpenGL Warning: glXCreatePbuffer not implemented by Chromium

Windows Error Dialog
VirtualBox.exe - Application Error
The instruction at 0x67c78bb1 referenced memory at 0x00000178. The memory could not be written.
Click on OK to terminate the program.