Bug 71616 - konsole crash with SIGSEGV on Dell Inspiron 8000 running SuSE 9 Pro 2.4.21-144
Summary: konsole crash with SIGSEGV on Dell Inspiron 8000 running SuSE 9 Pro 2.4.21-144
Status: RESOLVED NOT A BUG
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-01 21:26 UTC by Jimbo
Modified: 2005-02-13 09:15 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 Jimbo 2004-01-01 21:26:21 UTC
Version:            (using KDE KDE 3.1.4)
Installed from:    SuSE RPMs
Compiler:          gcc 3.3.1 
OS:          Linux

Not really sure how this happened.  Konsole was running fine since initial install onto this machine.  To enable my unsupported acx100 chipset based wireless card I open a konsole as root, navigate to the appropriate directory, and use the ./start_net script provided by acx100.sourceforge.net .  The issue first occured after installing kismet 3.0.1c .  I was able to use Kismet without incident in another, non-root konsole window.  Before I switched off my machine I adjusted my system clock.  Konsole hasn't worked properly ever since.  I was able to have it appear briefly, long enough to make it a shaded, transparent window.  

Here is the backtrace:

(no debugging symbols found)...[New Thread 16384 (LWP 3156)]
(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)...0x411e5a86 in waitpid ()
   from /lib/i686/libpthread.so.0
#0  0x411e5a86 in waitpid () from /lib/i686/libpthread.so.0
#1  0x406ca010 in KCrash::defaultCrashHandler(int) ()
   from /opt/kde3/lib/libkdecore.so.4
#2  0x411e496c in __pthread_sighandler () from /lib/i686/libpthread.so.0
#3  <signal handler called>
#4  0x4136a173 in __strtof_internal () from /lib/i686/libc.so.6
#5  0x4138ff09 in _IO_vfscanf_internal () from /lib/i686/libc.so.6
#6  0x4139c6f1 in vsscanf () from /lib/i686/libc.so.6
#7  0x41397bfb in sscanf () from /lib/i686/libc.so.6
#8  0x4159b420 in ColorSchema::rereadSchemaFile() ()
   from /opt/kde3/lib/konsole.so
#9  0x4159c34f in ColorSchemaList::updateAllSchemaTimes(QDateTime const&) ()
   from /opt/kde3/lib/konsole.so
#10 0x4159c686 in ColorSchemaList::checkSchemas() ()
   from /opt/kde3/lib/konsole.so
#11 0x41581dea in Konsole::Konsole(char const*, QString const&, QStrList&, int, bool, bool, bool, bool, QString const&, QString const&, QCString, QString const&, bool, QString const&) () from /opt/kde3/lib/konsole.so
#12 0x4158080e in main () from /opt/kde3/lib/konsole.so
#13 0x0804d8f3 in launch(int, char const*, char const*, char const*, int, char const*, bool, char const*, bool, char const*) ()
#14 0x0804e71f in handle_launcher_request(int) ()
#15 0x0804eca8 in handle_requests(int) ()
#16 0x0804faf8 in main ()

Process 3156 is kdeinit

Anything I can do other that do a complete reinstall of KDE?!?

Thanks in advance, 

Jimbo
Comment 1 Stephan Binner 2004-01-02 09:30:14 UTC
Do you have any own *.schema files in ~/.kde/share/apps/konsole?
Comment 2 Jimbo 2004-01-02 22:49:55 UTC
The only one there under my normal user is Transparent_darkbg.schema . 

Another note, my other terminals are running as they should.

Jimbo
Comment 3 Stephan Binner 2004-01-04 13:57:40 UTC
Try to move it away to see if it causes this crash.
Comment 4 Jimbo 2004-01-04 20:59:50 UTC
The konsole started working again today much to my surprise!  My schema as set still remained and all was well.  So I tried to duplicate what I did in the past.... because my time drifted two minutes behind.  I reset the time as it should have been then ran kismet to ensure the konsole still worked.  It did and I was pretty happy.  Then the litmus test:  reboot machine and check konsole again.  After reboot, konsole debug returned same crash information as before.  I removed my .schema file and konsole still wouldn't work.

Jimbo
Comment 5 Kurt Hindenburg 2005-02-02 18:53:29 UTC
Any update on this?  Have you tried a recent KDE version?
Comment 6 Kurt Hindenburg 2005-02-13 09:15:33 UTC
Reopen with more info if you can reproduce in KDE 3.3.x or 3.4