Bug 266339 - [OpenGL] Crash when launching Kstars
Summary: [OpenGL] Crash when launching Kstars
Status: RESOLVED FIXED
Alias: None
Product: kstars
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Akarsh Simha
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2011-02-14 23:50 UTC by Xavier Besnard
Modified: 2018-09-19 14:38 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
New crash information added by DrKonqi (2.34 KB, text/plain)
2011-02-14 23:53 UTC, Xavier Besnard
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Xavier Besnard 2011-02-14 23:50:03 UTC
Application: kstars (2.0.0)
KDE Platform Version: 4.6.00 (4.6.0)
Qt Version: 4.7.1
Operating System: Linux 2.6.38-3-generic i686
Distribution: Ubuntu natty (development branch)

-- Information about the crash:
- What I was doing when the application crashed: trying to launch Kstars with the K button

Config: ACER 531h with Kubuntu natty updated dayly

-- Backtrace:
Application: KStars (kstars), signal: Segmentation fault
[KCrash Handler]
#7  0x008e39c6 in glGetString () from /usr/lib/mesa/libGL.so.1
#8  0x002ecd10 in QGLExtensions::currentContextExtensions() () from /usr/lib/libQtOpenGL.so.4
#9  0x002ed803 in QGLExtensions::glExtensions() () from /usr/lib/libQtOpenGL.so.4
#10 0x00359285 in QGLContext::chooseVisual() () from /usr/lib/libQtOpenGL.so.4
#11 0x0035c374 in QGLContext::chooseContext(QGLContext const*) () from /usr/lib/libQtOpenGL.so.4
#12 0x002f0f00 in QGLContext::create(QGLContext const*) () from /usr/lib/libQtOpenGL.so.4
#13 0x0035bb9b in QGLWidget::setContext(QGLContext*, QGLContext const*, bool) () from /usr/lib/libQtOpenGL.so.4
#14 0x002f1378 in QGLWidgetPrivate::initContext(QGLContext*, QGLWidget const*) () from /usr/lib/libQtOpenGL.so.4
#15 0x0035a546 in QGLWidgetPrivate::init(QGLContext*, QGLWidget const*) () from /usr/lib/libQtOpenGL.so.4
#16 0x002ebfce in QGLWidget::QGLWidget(QGLContext*, QWidget*, QGLWidget const*, QFlags<Qt::WindowType>) () from /usr/lib/libQtOpenGL.so.4
#17 0x081d2c36 in SkyMapGLDraw::SkyMapGLDraw (this=0xae63908, sm=0xae5ce30) at ../../../kstars/kstars/skymapgldraw.cpp:24
#18 0x081ba31c in SkyMap::SkyMap (this=0xae5ce30) at ../../../kstars/kstars/skymap.cpp:231
#19 0x081ba4fe in SkyMap::Create () at ../../../kstars/kstars/skymap.cpp:140
#20 0x081a96b5 in KStars::buildGUI (this=0x9c93440) at ../../../kstars/kstars/kstarsinit.cpp:666
#21 0x081a9904 in KStars::datainitFinished (this=0x9c93440) at ../../../kstars/kstars/kstarsinit.cpp:524
#22 0x081827f7 in KStars::KStars (this=0x9c93440, doSplash=true, clockrun=true, startdate=..., __in_chrg=<value optimized out>, __vtt_parm=<value optimized out>) at ../../../kstars/kstars/kstars.cpp:109
#23 0x08182a17 in KStars::createInstance (doSplash=true, clockrun=true, startdate=...) at ../../../kstars/kstars/kstars.cpp:124
#24 0x081af8aa in main (argc=0, argv=0x0) at ../../../kstars/kstars/main.cpp:188

Reported using DrKonqi
Comment 1 Xavier Besnard 2011-02-14 23:53:41 UTC
Created attachment 57262 [details]
New crash information added by DrKonqi

kstars (2.0.0) on KDE Platform 4.6.00 (4.6.0) using Qt 4.7.1

- What I was doing when the application crashed:
Launching Kstars

ACER 531h with kubuntu natty updated dayly

-- Backtrace (Reduced):
#7  0x009599c6 in glGetString () from /usr/lib/mesa/libGL.so.1
#8  0x005f1d10 in QGLExtensions::currentContextExtensions() () from /usr/lib/libQtOpenGL.so.4
#9  0x005f2803 in QGLExtensions::glExtensions() () from /usr/lib/libQtOpenGL.so.4
#10 0x0065e285 in QGLContext::chooseVisual() () from /usr/lib/libQtOpenGL.so.4
#11 0x00661374 in QGLContext::chooseContext(QGLContext const*) () from /usr/lib/libQtOpenGL.so.4
Comment 2 Alexey Khudiakov 2011-02-18 20:58:19 UTC
Problem is obviously related to OpenGL. Could your tell which video card and drivers do you use?
Comment 3 Alexey Khudiakov 2011-03-02 22:36:07 UTC
I mark it as NEEDINFO. It's not possible to identify bug without information about hardware and drivers.
Comment 4 Andrew Crouthamel 2018-09-19 14:38:16 UTC
This bug has had its resolution changed, but accidentally has been left in NEEDSINFO status. I am thus closing this bug and setting the status as RESOLVED to reflect the resolution change.