Void's Forums

by **sh00der** » Wed Jul 02, 2003 12:12 pm

Hey there, last night I installed Muse (which I can't get any sound out of incidentally) using apt in RedHat 8.0. Now konsole crashes when I try to start it. When I try to run it I get the KDE Crash Handler window saying

"Short Description
The application Konsole (konsole) crashed and caused the signal 11 (SIGSEGV).

What is this?
An application mostly receives the SIGSEGV signal due to a bug in the application. The application was asked to save its documents......."

Backtrace gives ....
(no debugging symbols found)...0x40e54587 in waitpid ()
from /lib/libpthread.so.0
#0 0x40e54587 in waitpid () from /lib/libpthread.so.0
#1 0x4062b1e5 in KCrash::defaultCrashHandler(int) ()
from /usr/lib/libkdecore.so.4
#2 0x40e531cd in __pthread_clock_settime () from /lib/libpthread.so.0
#3 0x40fc3568 in killpg () from /lib/libc.so.6
#4 0x4129f85b in Konsole::makeGUI() () from /usr/lib/konsole.so
#5 0x412a4668 in Konsole::activateSession(TESession*) ()
from /usr/lib/konsole.so
#6 0x412a439e in Konsole::activateSession() () from /usr/lib/konsole.so
#7 0x412a3c7d in Konsole::runSession(TESession*) () from /usr/lib/konsole.so
#8 0x412a5b23 in Konsole::newSession(KSimpleConfig*, QString, QStrList const&, QString const&, QString const&, QString const&) () from /usr/lib/konsole.so
#9 0x4129a970 in Konsole::Konsole(char const*, QString const&, QStrList&, int, bool, bool, bool, bool, QString const&, QString const&, QCString, QString const&, bool) () from /usr/lib/konsole.so
#10 0x41298edf in main () from /usr/lib/konsole.so
#11 0x0804cb9f in strcpy ()
#12 0x0804d8bb in strcpy ()
#13 0x0804dd7c in strcpy ()
#14 0x0804eb40 in strcpy ()
#15 0x40fb0907 in __libc_start_main () from /lib/libc.so.6

What's happened?

by **Void Main** » Wed Jul 02, 2003 6:31 pm

Which repository did you install it from? Did it install/upgrade other dependent packages? I have had problems in the past mixing repositories and now only trust using FreshRPM.net which seems to be the most reliable/stable (nearly rock solid in fact).

by **sh00der** » Thu Jul 03, 2003 10:49 am

Void, that's probably where I went wrong I think I used

http://freesoftware.ircam.fr/mirrors/planetccrma/apt/

But how do I fix it? Do I have to uninstall KDE and then re-install it again?

by **Void Main** » Thu Jul 03, 2003 10:27 pm

I suppose I could point my apt to that repository and then install the program and see what it tries to install. I could make a list and pass it on to you and have you remove those RPMS (or downrev to the Red Hat defaults). I have had a similar problem in the past when using planetccrma apps. I installed something from there and it installed a different version of Python which broke all the redhat-config-xxxxx commands. Actually it broke everything that depended on Python. I was able to remove the bad packages and reinstall the good ones and get back to where I was.

Here's what it wants to install when I do an "apt-get install muse":

Code: Select all: # apt-get install muse Reading Package Lists... Done Building Dependency Tree... Done The following extra packages will be installed: jack-audio-connection-kit ladcca libfluidsynth The following packages will be upgraded jack-audio-connection-kit The following NEW packages will be installed: ladcca libfluidsynth muse 1 packages upgraded, 3 newly installed, 0 removed and 37 not upgraded. Need to get 2292kB of archives. After unpacking 5479kB of additional disk space will be used. Do you want to continue? [Y/n]

So maybe you might just try removing the above packages and see if it fixes anything.

by **sh00der** » Fri Jul 04, 2003 2:51 pm

Void, thanks for taking the time to list those rpms for me, I tried removing them but sadly konsole is still not having it.

Isn't there a way to just replace konsole rather than the whole kdebase thing? If it means re-installing kde I will probably lose all my settings and stuff won't I? If it comes to that I'll have to stick with xterm for a while.

by **Tux** » Fri Jul 04, 2003 3:19 pm

I think you should install KDE redhat from http://kde-redhat.sourceforge.net/ they have an apt repository.
There are several advantages to this:
A) It will fix your problem and retain your settings.
B) You will have the newest KDE.
C) You will rid yourself of RedHat's 'broken' KDE.

I did this a few month and have been very happy with KDE 3.0.5a, it kept all my settings, bookmarks etc and it removes certain brokenness from KDE so that you can install mosfet's liquid

I also later successfully updated that to the latest version of 3.1x whatever that may be, can't remember the version number, lol.

by **Void Main** » Sun Jul 06, 2003 2:50 pm

Or upgrade to Red Hat 9 which comes with KDE 3.1-11 and isn't "broken".

by **Calum** » Mon Jul 07, 2003 6:32 am

Tux wrote:C) You will rid yourself of RedHat's 'broken' KDE.

i hear people talk about red hat's broken kde frequently, and usually it comes down to red hat working more closely with the GNOME team than the KDE team when putting together their distro, but i have never noticed a problem with red hat's kde in versions 7.0, 8.0 or 9.0. While using 7.0 i was a total newbie, so might not have noticed stuff, in 8.0 i didn't use kde much, and again in 9.0 am not using kde much (although nautilus is still buggy and will hang at no notice so i am forced to use kde now Windowmaker is not in RH (which is ridiculous, i mean slack only has one CD and it comes with something like 8 desktop environments, and mandrake has 6 or so on its 2 disk effort)) but still, you'd think if there was some problem with KDE in red hat, that i might have noticed it by now? i have also used KDE in slack 9.0 and mandrake 8.2 (oh yes and mdk 9.0 also) and couldn't notice any obvious cripplage in the RH version.

So what's all this fuss about godsdamnit?

by **Tux** » Mon Jul 07, 2003 10:34 am

My main gripe is that they moved files areount and chaged the K menu somehow in a way which stopped mosfet's liquid from working.
This is actually of little significance to me anymore as I don't use mosfet's liquid anymore I believe there was some other compatibility broken from their KDE hacks but I have never experienced them myself.
There is definately 'some' degree of breakage although they could just be called changes.

by **Void Main** » Mon Jul 07, 2003 7:39 pm

I'm not sure. It's not the same as a default KDE installation but there is nothing broken that I am aware of. I am very happy with Red Hat's customizations personally and don't really understand the gripes. The only gripe that I agreed with was when in one of the betas they removed the KDE credit from the "About" boxes but I believe that was quickly returned. I would actually have been disappointed if Red Hat had not customized KDE and not tailored it to be Red Hat specific. To me, that's what Open Source is all about. Personally I am still using Gnome on Red Hat at home but am using KDE at work on Sun/Solaris.

by **Calum** » Thu Jul 10, 2003 12:47 pm

well i just did a whole system upgrade using apt (which takes two days on dialup) and i found that the new kde which it upgrades to from the freshrpms site, appears to be identical to the one in slack 9 (to my eyes), so perhaps the freshrpms one is the default, meaning if you used their apt repository to update rh9, then you no longer have red hat's customised version?

oh yes and to answer sh00der's question: no all the settings are exactly the same as they were before. i upgraded the glibc package and kdebase and friends came with it, well recommended. I had to remember to run twm instead of kde to do it in though, last time i tried to update kdebase while running kde would you believe...

by **Void Main** » Thu Jul 10, 2003 7:34 pm

FreshRPMS doesn't have a customized version of KDE that I am aware of. If you did an upgrade from RH8 to RH9 via apt and the stock FreshRPMS sources.list then you should have the KDE that ships with RH9.

Void's Forums

konsole crashing

konsole crashing

konsole krashing

Who is online