View previous topic :: View next topic |
Author |
Message |
tobiasm n00b
Joined: 13 Jun 2004 Posts: 6
|
Posted: Sun Feb 13, 2005 1:07 pm Post subject: |
|
|
thesimp wrote: | The KDE crash panel complains that it cannot create a valid backtrace, but it managed to come up with this:
Code: | #0 0x715c8b50 in waitpid () from /lib/libpthread.so.0
#1 0x70898218 in KCrash::defaultCrashHandler ()
from /usr/kde/3.3/lib/libkdecore.so.4
#2 0x715c7854 in __pthread_clock_settime () from /lib/libpthread.so.0
#3 0x715c7854 in __pthread_clock_settime () from /lib/libpthread.so.0 |
Let's see if I can find out why the crash panel cannot make a valid backtrace.
|
I have got the same problem on a Ultra-Sparc-60 with 2x450MHz, a gentoo-dev-sources-2.6.10 and a kde 3.3.2
Did somebody try to compile and run KDE with debug-symbols ?
Tobias
PS: I am close to type "emerge gnome xscreensaver" |
|
Back to top |
|
|
ibtim13 Tux's lil' helper
Joined: 12 Sep 2003 Posts: 84 Location: Troy, NY
|
Posted: Wed Feb 16, 2005 5:10 am Post subject: |
|
|
I'm just wondering, are all of you having problems on SMP boxes or
are any of them single processor machines? The problem seems to have
something to do with the clock and threading and I'm wondering if it's because
code that is not really thread safe, but acts like it is on a single cpu system,
is used in the kicker somewhere. _________________ Grrr, can't think of anything clever right now, I'll go back and edit this later (9/12/2003) |
|
Back to top |
|
|
biggyL Tux's lil' helper
Joined: 31 Jan 2005 Posts: 120 Location: Israel
|
Posted: Wed Feb 16, 2005 6:16 am Post subject: |
|
|
I have sparc u30 with uni processor, so I think there is no connection to SMP kernel. |
|
Back to top |
|
|
robbyjo Guru
Joined: 06 Apr 2003 Posts: 462
|
Posted: Wed Feb 16, 2005 11:23 pm Post subject: |
|
|
Uniprocessor Ultra10 here. |
|
Back to top |
|
|
squash Tux's lil' helper
Joined: 22 Jun 2002 Posts: 79
|
Posted: Thu Feb 17, 2005 7:11 pm Post subject: |
|
|
My E250 breaks, but my E450 works fine...strace and gdb don't give any good info... |
|
Back to top |
|
|
squash Tux's lil' helper
Joined: 22 Jun 2002 Posts: 79
|
Posted: Wed Mar 02, 2005 3:56 am Post subject: |
|
|
Well, after the latest qt upgrade (3.3.4 over 3.3.3), kicker now crashes on my e450 as well. I'm trying to back up to 3.3.3 to see if that corrects the situation. If not, maybe the issue lies with gcc? |
|
Back to top |
|
|
squash Tux's lil' helper
Joined: 22 Jun 2002 Posts: 79
|
Posted: Wed Mar 02, 2005 1:59 pm Post subject: |
|
|
Downgrading qt did not help at all... maybe its time to compile qt and kde with all the debugging options enabled/ |
|
Back to top |
|
|
gentsquash l33t
Joined: 03 Nov 2004 Posts: 753 Location: Still a Gentoo beginner.
|
Posted: Thu Mar 03, 2005 4:06 am Post subject: |
|
|
FYI: A different `kicker' problem may have been solved
https://forums.gentoo.org/viewtopic-p-2148221.html#2148221
by emerging. _________________ Your thread resolved? Putting [SOLVED] in its title helps all Gentooers. (Button "edit" , first post)
Prof. Jonathan LF King, Mathematics dept., University of Florida |
|
Back to top |
|
|
squash Tux's lil' helper
Joined: 22 Jun 2002 Posts: 79
|
Posted: Thu Mar 03, 2005 2:43 pm Post subject: |
|
|
I added the USE flags "debug kdeenablefinal" and re-emerged
x11-libs/qt-3.3.4-r2
kde-base/kdelibs-3.3.2-r2
kde-base/kdebase-3.3.2-r1
and now kicker is working again!
If anyone wants a binary package of these 3, I can put it up someplace.
Squash |
|
Back to top |
|
|
ibtim13 Tux's lil' helper
Joined: 12 Sep 2003 Posts: 84 Location: Troy, NY
|
Posted: Sun Mar 06, 2005 5:24 am Post subject: |
|
|
Unfortunately, after following your instructions, kicker still crashes on my Ultra2.
Very Sad. I gave up and deleted all traces of kde from my system. I will try again
in a few months. Hopefully I can get some semblance of sound support working in
the meantime. I'd also like to get openoffice to work one of these days, it always
fails during compiling saying that the java VM detected an error in the external
code. _________________ Grrr, can't think of anything clever right now, I'll go back and edit this later (9/12/2003) |
|
Back to top |
|
|
i-right-i Tux's lil' helper
Joined: 08 Nov 2004 Posts: 118 Location: Chandler, AZ USA
|
Posted: Fri Mar 18, 2005 10:08 pm Post subject: KDE Fubar |
|
|
I had exactly the same issue on my Ultra 10. Bug soup at best. KDE is definetly problematic on Sparc. I messed around with it for over a month before giving up and loading up Black Box as a alternative.
I don't know a ton about desktops, but is there another full featured desktop similar to KDE that actually runs on a sparc?
Thanks,
i-right-i |
|
Back to top |
|
|
Risk n00b
Joined: 05 Mar 2004 Posts: 38 Location: Zoo York City
|
Posted: Sat Mar 19, 2005 1:23 am Post subject: |
|
|
Have just successfully compiled and installed KDE 3.4.0 on a few SPARC64 machines (Ultra 5 / Ultra 10) using gcc-3.3.5 and the kicker crash is now officially a non-issue.
My suggestion is to upgrade to 3.4.0 |
|
Back to top |
|
|
tunkaflux Tux's lil' helper
Joined: 20 Aug 2003 Posts: 76
|
Posted: Sat Mar 19, 2005 11:35 am Post subject: |
|
|
Risk wrote: | Have just successfully compiled and installed KDE 3.4.0 on a few SPARC64 machines (Ultra 5 / Ultra 10) using gcc-3.3.5 and the kicker crash is now officially a non-issue.
My suggestion is to upgrade to 3.4.0 |
Did an "ACCEPT_KEYWORDS=~sparc emerge kde" and I also have the kicker problem, so it's no quite resolved yet
I tried Weeve's suggestion to disable the sound system in KDE: kicker still crashes.
I also tried to disable the applets on the kicker in $HOME/.kde/share/config/kickerrc, but there were no applets listed there.
Should I try to install a kernel from the 2.6.x branch? I heard that Weeve did not have this problem then... |
|
Back to top |
|
|
retroman Apprentice
Joined: 18 Nov 2004 Posts: 207 Location: Stuttgart
|
Posted: Sat Mar 19, 2005 8:07 pm Post subject: kde 3.4 emerge |
|
|
I just did an emerge sync. 3.4 is not there in emerge -pv kde. How do i point it to 3.4??
Jordan |
|
Back to top |
|
|
tunkaflux Tux's lil' helper
Joined: 20 Aug 2003 Posts: 76
|
Posted: Sun Mar 20, 2005 11:04 am Post subject: |
|
|
"ACCEPT_KEYWORDS=~sparc emerge kde" did the trick for me. |
|
Back to top |
|
|
Risk n00b
Joined: 05 Mar 2004 Posts: 38 Location: Zoo York City
|
Posted: Sun Mar 20, 2005 8:11 pm Post subject: |
|
|
Quote: | Should I try to install a kernel from the 2.6.x branch? I heard that Weeve did not have this problem then... |
I ought to have specified that we're using 2.6.10-r6 and 2.6.11-r4 kernels (in instances where the kicker crash problem has been resolved running kde 3.4.0) |
|
Back to top |
|
|
retroman Apprentice
Joined: 18 Nov 2004 Posts: 207 Location: Stuttgart
|
Posted: Mon Mar 21, 2005 7:20 pm Post subject: Problem with kicker |
|
|
Let me start off - DUAL processor Ultra 60
Kernel 2.4.29
Kicker crashes on startup, konqueror crashes when logging in to yahoo mail. Mozilla works fine
got this from kicker from the console, hope this sheads some light
kio (KSycoca): Trying to open ksycoca from
/var/tmp/kdecache-root/ksycoca
X Error: BadValue (integer parameter out of range for
operation) 2
Major opcode: 102
Minor opcode: 0
Resource id: 0x0
X Error: BadValue (integer parameter out of range for
operation) 2
Major opcode: 102
Minor opcode: 0
Resource id: 0x0
kicker: *** Embed 4194315 into 31457453. window=0
kicker: > before reparent: parent=0x2b
kicker: > Loop 0: > reparent of 0x40000b into
0x1e000ad successful
kicker: *** Embed 27262983 into 31457455. window=0
kicker: > before reparent: parent=0x2b
kicker: > Loop 0: > reparent of 0x1a00007 into
0x1e000af successful
kdecore (KConfigSkeleton): Creating KConfigSkeleton
(0x15bee0)
kdecore (KConfigSkeleton):
KConfigSkeleton::readConfig()
ERROR: Communication problem with kicker, it probably
crashed.
bash-2.05b# |
|
Back to top |
|
|
tunkaflux Tux's lil' helper
Joined: 20 Aug 2003 Posts: 76
|
Posted: Wed Mar 23, 2005 5:51 am Post subject: |
|
|
Kicker still crashes on my Sun Netra T1125 when switching from 2.4.x to 2.6.x. This is the same motherboard as the Ultra 60 if I'm correct. |
|
Back to top |
|
|
retroman Apprentice
Joined: 18 Nov 2004 Posts: 207 Location: Stuttgart
|
Posted: Wed Mar 23, 2005 7:07 am Post subject: |
|
|
I spent all this time upgrading kde to 3.4 and the problem is still there. The only new development is you can almost see the panel start to appear before it dies.
The question stands.
Is there anyone out there with an Ultra60 that can run kde 3.3 or kde 3.4? What kernel do you use? If its 2.6, how did you get the mouse to work.
im so annoyed
Jordan |
|
Back to top |
|
|
retroman Apprentice
Joined: 18 Nov 2004 Posts: 207 Location: Stuttgart
|
Posted: Wed Mar 23, 2005 12:07 pm Post subject: |
|
|
Every applet seems to work fine except for the clock applet, it may be causing the problem as i posted in the chatroom and bug #77623.
I have tested every applet individually and they all work except for one..
The clock applet... see snipplet>
bash-2.05b# appletproxy /usr/kde/3.4/share/apps/kicker/applets/clockapplet.desktop
kdecore (KConfigSkeleton): Creating KConfigSkeleton
(0x141cf0)
kdecore (KConfigSkeleton):
KConfigSkeleton::readConfig()
Bus error
bash-2.05b#
I have the strace for the clock applet but it is really big. Where should i post it.
jordan |
|
Back to top |
|
|
chance2105 Tux's lil' helper
Joined: 10 Jun 2004 Posts: 112 Location: Norman, OK USA
|
Posted: Fri Apr 01, 2005 3:29 am Post subject: |
|
|
I get the exact same results as squash: recompiling qt, kdelibs, and kdebase with USE="debug kdeenablefinal" did the trick. I now have a working kicker.
[EDIT:] But, alas, my lowercase B key aint workin .. heh |
|
Back to top |
|
|
chance2105 Tux's lil' helper
Joined: 10 Jun 2004 Posts: 112 Location: Norman, OK USA
|
Posted: Fri Apr 01, 2005 9:32 pm Post subject: |
|
|
For giggles, I figured I'd start recompiling the three of those without USE="debug"
Results:
After compiling qt with debugging off, I now have the return of the kicker crashing scenario.
(hmm)
[EDIT:] had to put 'b'-s in there .. |
|
Back to top |
|
|
chance2105 Tux's lil' helper
Joined: 10 Jun 2004 Posts: 112 Location: Norman, OK USA
|
Posted: Sat Apr 02, 2005 2:33 am Post subject: |
|
|
Okie dokie. I recompiled QT again. This time, I didn't reintroduce the DEBUG flag, I just changed C(XX)FLAGS from:
Code: | -O2 -mcpu=ultrapsarc -pipe |
to
Kicker works. This is making me wonder if we have a GCC issue going on here. |
|
Back to top |
|
|
chance2105 Tux's lil' helper
Joined: 10 Jun 2004 Posts: 112 Location: Norman, OK USA
|
Posted: Sat Apr 02, 2005 4:16 pm Post subject: |
|
|
I've recompiled qt with C(XX)FLAGS"-O2 -pipe" and all three qt, kdeliBs, kdeBase with USE="-deBug -kdeenaBlefinal" .. and .. still have a working kicker.
Seems that the whole issue revolves around compiling QT with the -mcpu=ultrapsarc flag. So for a working kicker, all you have to do is recompile QT without the -mcpu flag, and you're good to go.
I'm not sure yet if lesser values of -mcpu work yet, But it does seem to me that the qt eBuild should Be masking at the very least -mcpu=ultrasparc. |
|
Back to top |
|
|
Weeve Retired Dev
Joined: 30 Oct 2002 Posts: 641
|
Posted: Sat Apr 02, 2005 4:23 pm Post subject: |
|
|
What if you try -mtune=ultrasparc instead of -mcpu=ultrasparc? |
|
Back to top |
|
|
|