Bug 233231 - java swing nullpointerexception sigsegv
Summary: java swing nullpointerexception sigsegv
Status: RESOLVED WORKSFORME
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2010-04-04 11:27 UTC by sreque
Modified: 2018-10-21 04:54 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description sreque 2010-04-04 11:27:03 UTC
Application that crashed: konsole
Version of the application: 2.3.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-20-generic i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
A java swing program I wrote crashed during initialization after being invoked on a konsole bash prompt. Konsole immediately crashed as well.

 -- Backtrace:
Application: Konsole (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#6  0x04621a2a in LinuxProcessInfo::readProcInfo(int) () from /usr/lib/libkonsoleprivate.so
#7  0x0461db65 in Konsole::UnixProcessInfo::readProcessInfo (this=0xa5beca8, pid=12003, enableEnvironmentRead=false) at ../../../../apps/konsole/src/ProcessInfo.cpp:336
#8  0x0461d810 in Konsole::ProcessInfo::update (this=0xa5beca8) at ../../../../apps/konsole/src/ProcessInfo.cpp:68
#9  0x04633176 in Konsole::Session::updateForegroundProcessInfo (this=0xa56fa40) at ../../../../apps/konsole/src/Session.cpp:839
#10 0x046331d2 in Konsole::Session::isForegroundProcessActive (this=0xa56fa40) at ../../../../apps/konsole/src/Session.cpp:1180
#11 0x04633282 in Konsole::Session::getProcessInfo (this=0xa56fa40) at ../../../../apps/konsole/src/Session.cpp:802
#12 0x04634948 in Konsole::Session::updateWorkingDirectory (this=0xa56fa40) at ../../../../apps/konsole/src/Session.cpp:231
#13 0x04635972 in Konsole::Session::getDynamicTitle (this=0xa56fa40) at ../../../../apps/konsole/src/Session.cpp:849
#14 0x0463be09 in Konsole::SessionController::snapshot (this=0xa633ec8) at ../../../../apps/konsole/src/SessionController.cpp:204
#15 0x04644530 in Konsole::SessionController::qt_metacall (this=0xa633ec8, _c=QMetaObject::InvokeMetaMethod, _id=34, _a=0xbfddc41c) at ./SessionController.moc:172
#16 0x0067b263 in QMetaObject::activate (sender=0xa7010f8, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113
#17 0x0067bec2 in QMetaObject::activate (sender=0xa7010f8, m=0x756904, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187
#18 0x006b5667 in QTimer::timeout (this=0xa7010f8) at .moc/release-shared/moc_qtimer.cpp:128
#19 0x006809ae in QTimer::timerEvent (this=0xa7010f8, e=0xbfddc8b0) at kernel/qtimer.cpp:261
#20 0x006753bf in QObject::event (this=0xa7010f8, e=0xbfddc8b0) at kernel/qobject.cpp:1075
#21 0x0482af54 in QApplicationPrivate::notify_helper (this=0x9cb1a00, receiver=0xa7010f8, e=0xbfddc8b0) at kernel/qapplication.cpp:4056
#22 0x0483267c in QApplication::notify (this=0xbfddcc18, receiver=0xa7010f8, e=0xbfddc8b0) at kernel/qapplication.cpp:3603
#23 0x0100ebfa in KApplication::notify (this=0xbfddcc18, receiver=0xa7010f8, event=0xbfddc8b0) at ../../kdeui/kernel/kapplication.cpp:302
#24 0x006656cb in QCoreApplication::notifyInternal (this=0xbfddcc18, receiver=0xa7010f8, event=0xbfddc8b0) at kernel/qcoreapplication.cpp:610
#25 0x006927ce in QCoreApplication::sendEvent (this=0x9cb8384) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#26 QTimerInfoList::activateTimers (this=0x9cb8384) at kernel/qeventdispatcher_unix.cpp:572
#27 0x006900e0 in timerSourceDispatch (source=0x9cb8350) at kernel/qeventdispatcher_glib.cpp:165
#28 0x0025fe88 in g_main_dispatch (context=0x9cb4290) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:1960
#29 IA__g_main_context_dispatch (context=0x9cb4290) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2513
#30 0x00263730 in g_main_context_iterate (context=0x9cb4290, block=<value optimized out>, dispatch=1, self=0x9c08ac0) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2591
#31 0x00263863 in IA__g_main_context_iteration (context=0x9cb4290, may_block=1) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2654
#32 0x0069002c in QEventDispatcherGlib::processEvents (this=0x9cb1b80, flags=...) at kernel/qeventdispatcher_glib.cpp:327
#33 0x048cbbe5 in QGuiEventDispatcherGlib::processEvents (this=0x9cb1b80, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#34 0x00663c79 in QEventLoop::processEvents (this=0xbfddcb74, flags=) at kernel/qeventloop.cpp:149
#35 0x006640ca in QEventLoop::exec (this=0xbfddcb74, flags=...) at kernel/qeventloop.cpp:201
#36 0x0066653f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#37 0x0482add7 in QApplication::exec () at kernel/qapplication.cpp:3525
#38 0x02eab8d0 in kdemain (argc=1, argv=0x9c5a9f0) at ../../../../apps/konsole/src/main.cpp:104
#39 0x0804dde1 in launch (argc=<value optimized out>, _name=<value optimized out>, args=<value optimized out>, cwd=0x0, envc=1, envs=0x9c4f201 "DISPLAY=:0.0", reset_env=false, tty=0x0, 
    avoid_loops=false, startup_id_str=0x9c4f212 "sreque-ubuntu;1270267497;218802;2005_TIME46778") at ../../kinit/kinit.cpp:677
#40 0x0804ea35 in handle_launcher_request (sock=<value optimized out>, who=<value optimized out>) at ../../kinit/kinit.cpp:1169
#41 0x0804eeac in handle_requests (waitForPid=<value optimized out>) at ../../kinit/kinit.cpp:1362
#42 0x0804fbaf in main (argc=2, argv=0xbfddd3e4, envp=0xbfddd3f0) at ../../kinit/kinit.cpp:1793

Reported using DrKonqi
Comment 1 Dario Andres 2010-04-04 17:21:09 UTC
- Is the Konsole crash reproducible for you with your crashing Java app ? (does it crash if you repeat the situation?)
This looks related to bug 201119
Regards
Comment 2 Shlomi Fish 2010-12-03 17:06:21 UTC
(In reply to comment #1)
> - Is the Konsole crash reproducible for you with your crashing Java app ? (does
> it crash if you repeat the situation?)
> This looks related to bug 201119
> Regards

It's been about 8 months since this bug was reported and it's for an old KDE version. I ask the original poster to reply or else I suggest closing this bug.
Comment 3 Dario Andres 2010-12-04 15:36:31 UTC
[Comment from a bug triager]
Marking as NEEDSINFO
Comment 4 Andrew Crouthamel 2018-09-20 22:16:09 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Andrew Crouthamel 2018-10-21 04:54:19 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!