Bug 52355 - network socket or fontconfig crash
Summary: network socket or fontconfig crash
Status: RESOLVED FIXED
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 1.1.3
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-12-27 22:32 UTC by Shawn Wilson
Modified: 2003-03-04 16:35 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 Shawn Wilson 2002-12-27 22:32:24 UTC
Version:           1.1.3 (using KDE KDE 3.0.4)
Installed from:    Debian testing/unstable Packages
Compiler:          gcc 2.95.4 
OS:          Linux

when konsole is run it crashes with a "The application Konsole (konsole) crashed and caused the signal 11 (SIGSEGV)" 
This happens every time that I have tried to open konsole for the past week or so, before the network socket errors started (about 3 days ago) i got errors with the fontconfig1 libs (which indeed weren't even there and didn't seem to be included in it's package at the time). i am getting these errors as root to insure that all permissions are correct.

running debian (sid)
kde 3.0.4 debian packages
Qt 3.1.1
fontconfig1 2.1


the command line spits all of this out:

_IceTransOpen: Unable to Parse address none
Session management error: Could not open network socket
DCOPServer up and running.
_IceTransOpen: Unable to Parse address none
Session management error: Could not open network socket
KCrash: crashing.... crashRecursionCounter = 2
KCrash: Application Name = konsole path = <unknown> pid = 13512
_IceTransOpen: Unable to Parse address none
Session management error: Could not open network socket
Mutex destroy failure: Device or resource busy
kdeinit: Fatal ID error: client killed
kdeinit: sending SIGHUP to children.
kdeinit: sending SIGTERM to children.
kdeinit: Exit.

GDB:

(no debugging symbols found)...(no debugging symbols found)...[New Thread 16384 (LWP 13512)]

(no debugging symbols found)...(no debugging symbols found)...

0x40dfda39 in wait4 () from /lib/libc.so.6
#0  0x40dfda39 in wait4 () from /lib/libc.so.6
#1  0x40e70ba0 in sys_sigabbrev () from /lib/libc.so.6
#2  0x40caf061 in waitpid () from /lib/libpthread.so.0
#3  0x404cda20 in KCrash::defaultCrashHandler () from /usr/lib/libkdecore.so.4
#4  0x40d8a898 in sigaction () from /lib/libc.so.6
#5  0x0805eddc in QWidget::paintEvent ()
#6  0x08065f40 in QWidget::paintEvent ()
#7  0x08065c24 in QWidget::paintEvent ()
#8  0x080656ae in QWidget::paintEvent ()
#9  0x0806705e in QWidget::paintEvent ()
#10 0x0805e7ac in QWidget::paintEvent ()
#11 0x0805dd1c in QWidget::paintEvent ()
#12 0x40d799f1 in __libc_start_main () from /lib/libc.so.6
Comment 1 Stephan Binner 2002-12-30 11:09:01 UTC
KDE 3.0.4 doesn't work well with Qt 3.1.x 
Comment 2 Stephan Binner 2003-03-04 15:53:14 UTC
Does this still happen with the KDE 3.1 Debian packages? 
Comment 3 Chris Maxwell 2003-03-04 16:31:16 UTC
no... upgrading to 3.1 fixed the problems on my box;
thanks

KDE 3.1.0
Konsole 1.2
gcc: 3.2.3 2003 0228 (debian prerelease)
debian sid/unstable
linux kernel 2.4.20
Comment 4 Stephan Binner 2003-03-04 16:35:17 UTC
*** Bug has been marked as fixed ***.