Bug 129243 - Bug appears when session is ended with konsole window opened.
Summary: Bug appears when session is ended with konsole window opened.
Status: RESOLVED WORKSFORME
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-06-16 12:28 UTC by John Znuck
Modified: 2006-09-06 13:00 UTC (History)
0 users

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 John Znuck 2006-06-16 12:28:48 UTC
Version:            (using KDE KDE 3.5.0)
Installed from:    Debian testing/unstable Packages

This is a copy of the trace.

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1231866176 (LWP 3150)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#5  0xb65bc687 in Konsole::saveProperties ()
   from /usr/lib/libkdeinit_konsole.so
#6  0xb6d91375 in KMainWindow::savePropertiesInternal ()
   from /usr/lib/libkdeui.so.4
#7  0xb6e73c5a in KMWSessionManaged::saveState () from /usr/lib/libkdeui.so.4
#8  0xb78f411f in KApplication::saveState () from /usr/lib/libkdecore.so.4
#9  0xb71f14d2 in QSessionManager::setRestartCommand ()
   from /usr/lib/libqt-mt.so.3
#10 0xb71f173f in QSessionManager::setRestartCommand ()
   from /usr/lib/libqt-mt.so.3
#11 0xb6985bad in _SmcProcessMessage () from /usr/X11R6/lib/libSM.so.6
#12 0xb696ffbf in IceProcessMessages () from /usr/X11R6/lib/libICE.so.6
#13 0xb71ebbc8 in QSmSocketReceiver::socketActivated ()
   from /usr/lib/libqt-mt.so.3
#14 0xb71ebe67 in QSmSocketReceiver::qt_invoke () from /usr/lib/libqt-mt.so.3
#15 0xb72d454b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#16 0xb72d4e52 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#17 0xb7666f7f in QSocketNotifier::activated () from /usr/lib/libqt-mt.so.3
#18 0xb72f480a in QSocketNotifier::event () from /usr/lib/libqt-mt.so.3
#19 0xb726a87a in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#20 0xb726aa76 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#21 0xb794102e in KApplication::notify () from /usr/lib/libkdecore.so.4
#22 0xb71fc001 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#23 0xb725c435 in QEventLoop::activateSocketNotifiers ()
   from /usr/lib/libqt-mt.so.3
#24 0xb720fd06 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#25 0xb7283255 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#26 0xb728317a in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#27 0xb726938d in QApplication::exec () from /usr/lib/libqt-mt.so.3
#28 0xb65def27 in kdemain () from /usr/lib/libkdeinit_konsole.so
#29 0xb7fd2524 in kdeinitmain () from /usr/lib/kde3/konsole.so
#30 0x0804e1d6 in ?? ()
#31 0x00000001 in ?? ()
#32 0x0808b518 in ?? ()
#33 0x00000001 in ?? ()
#34 0x00000000 in ?? ()
Comment 1 Philip Rodrigues 2006-06-16 17:09:34 UTC
Is the crash reproducible?
Comment 2 John Znuck 2006-06-17 04:29:04 UTC
To answer your question, we would have to know the unique combination of conditions that give rise to this crash. What they are exactly, I wouldn't know. I know my system config which I have stated in the bug report.
Did the backtrace not tell you anything?




Philip Rodrigues <phil@kde.org> wrote: ------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
         
http://bugs.kde.org/show_bug.cgi?id=129243         




------- Additional Comments From phil kde org  2006-06-16 17:09 -------
Is the crash reproducible?


 		
---------------------------------
Ring'em or ping'em. Make  PC-to-phone calls as low as 1
Comment 3 Philip Rodrigues 2006-06-18 16:09:08 UTC
To clarify, I meant reproducible in the sense of "can you reproduce the crash at will?" (or was it just a one-off?). 
Comment 4 John Znuck 2006-06-19 04:24:51 UTC
It is consistent.

Philip Rodrigues <phil@kde.org> wrote: ------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
         
http://bugs.kde.org/show_bug.cgi?id=129243         




------- Additional Comments From phil kde org  2006-06-18 16:09 -------
To clarify, I meant reproducible in the sense of "can you reproduce the crash at will?" (or was it just a one-off?).


 		
---------------------------------
Do you Yahoo!?
 Get on board. You're invited to try the new Yahoo! Mail Beta.It is consistent.<br><br><b><i>Philip Rodrigues &lt;phil@kde.org&gt;</i></b> wrote:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> ------- You are receiving this mail because: -------<br>You reported the bug, or are watching the reporter.<br>         <br>http://bugs.kde.org/show_bug.cgi?id=129243         <br><br><br><br><br>------- Additional Comments From phil kde org  2006-06-18 16:09 -------<br>To clarify, I meant reproducible in the sense of "can you reproduce the crash at will?" (or was it just a one-off?).<br></blockquote><br><p>&#32;
		<hr size=1>Do you Yahoo!?<br> 
Get on board. <a href="http://us.rd.yahoo.com/evt=40791/*http://advision.webevents.yahoo.com/handraisers">You're invited</a> to try the new Yahoo! Mail Beta.
Comment 5 Philip Rodrigues 2006-06-19 18:28:03 UTC
Does the same crash occur with a newly-created user?
Comment 6 John Znuck 2006-06-20 07:34:31 UTC
Hi, this is something I just found out. It does allow a newly created user to login. Does this help to pinpoint the source of the problem?

Philip Rodrigues <phil@kde.org> wrote: ------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
         
http://bugs.kde.org/show_bug.cgi?id=129243         




------- Additional Comments From phil kde org  2006-06-19 18:28 -------
Does the same crash occur with a newly-created user?


 		
---------------------------------
Do you Yahoo!?
 Get on board. You're invited to try the new Yahoo! Mail Beta.Hi, this is something I just found out. It does allow a newly created user to login. Does this help to pinpoint the source of the problem?<br><br><b><i>Philip Rodrigues &lt;phil@kde.org&gt;</i></b> wrote:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> ------- You are receiving this mail because: -------<br>You reported the bug, or are watching the reporter.<br>         <br>http://bugs.kde.org/show_bug.cgi?id=129243         <br><br><br><br><br>------- Additional Comments From phil kde org  2006-06-19 18:28 -------<br>Does the same crash occur with a newly-created user?<br></blockquote><br><p>&#32;
		<hr size=1>Do you Yahoo!?<br> 
Get on board. <a href="http://us.rd.yahoo.com/evt=40791/*http://advision.webevents.yahoo.com/handraisers">You're invited</a> to try the new Yahoo! Mail Beta.
Comment 7 John Znuck 2006-06-20 07:38:25 UTC
The last reply could be confusing. I meant to say that the crash does not occur with a newly-created user.


Philip Rodrigues <phil@kde.org> wrote: ------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
         
http://bugs.kde.org/show_bug.cgi?id=129243         




------- Additional Comments From phil kde org  2006-06-19 18:28 -------
Does the same crash occur with a newly-created user?


 		
---------------------------------
Do you Yahoo!?
 Next-gen email? Have it all with the  all-new Yahoo! Mail Beta.The last reply could be confusing. I meant to say that the crash does not occur with a newly-created user.<br><br><br><b><i>Philip Rodrigues &lt;phil@kde.org&gt;</i></b> wrote:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> ------- You are receiving this mail because: -------<br>You reported the bug, or are watching the reporter.<br>         <br>http://bugs.kde.org/show_bug.cgi?id=129243         <br><br><br><br><br>------- Additional Comments From phil kde org  2006-06-19 18:28 -------<br>Does the same crash occur with a newly-created user?<br></blockquote><br><p>&#32;
		<hr size=1>Do you Yahoo!?<br> Next-gen email? Have it all with the <a href="http://us.rd.yahoo.com/evt=40791/*http://advision.webevents.yahoo.com/handraisers"> all-new Yahoo! Mail Beta.</a>
Comment 8 Philip Rodrigues 2006-06-21 12:12:30 UTC
Try renaming the file ~/.kde/share/config/konsolerc and the directory ~/.kde/share/apps/konsole (with your original user). Restart KDE and try again. Does the problem persist?
Comment 9 John Znuck 2006-06-22 09:38:33 UTC
Renaming the file and the dir seems to have fixed it. Would you want to explain why?


Philip Rodrigues <phil@kde.org> wrote: ------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
         
http://bugs.kde.org/show_bug.cgi?id=129243         




------- Additional Comments From phil kde org  2006-06-21 12:12 -------
Try renaming the file ~/.kde/share/config/konsolerc and the directory ~/.kde/share/apps/konsole (with your original user). Restart KDE and try again. Does the problem persist?


 __________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com Renaming the file and the dir seems to have fixed it. Would you want to explain why?<br><br><br><b><i>Philip Rodrigues &lt;phil@kde.org&gt;</i></b> wrote:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> ------- You are receiving this mail because: -------<br>You reported the bug, or are watching the reporter.<br>         <br>http://bugs.kde.org/show_bug.cgi?id=129243         <br><br><br><br><br>------- Additional Comments From phil kde org  2006-06-21 12:12 -------<br>Try renaming the file ~/.kde/share/config/konsolerc and the directory ~/.kde/share/apps/konsole (with your original user). Restart KDE and try again. Does the problem persist?<br></blockquote><br><p>&#32;__________________________________________________<br>Do You Yahoo!?<br>Tired of spam?  Yahoo! Mail has the best spam protection around <br>http://mail.yahoo.com 
Comment 10 Philip Rodrigues 2006-06-22 14:19:23 UTC
There may be some corrupted entry in one of the files you renamed which was causing the crash. Once you renamed them, konsole no longer tried to read them, and so didn't crash. Could you attach your konsolerc file so we can see if anyone else can reproduce the crash?
Comment 11 Philip Rodrigues 2006-09-06 13:00:17 UTC
Problem gone, and no config files given so closing