View previous topic :: View next topic |
Author |
Message |
cyberoli n00b
Joined: 02 Dec 2004 Posts: 3
|
Posted: Thu Dec 09, 2004 6:16 pm Post subject: Kicker on Ultra 10 SPARC |
|
|
Hi !
I installed KDE 3.3.1 and alway when I want to start the kicker I get the errror message:
X Error: BadValue (integer parameter out of range for operation) 2
Major opcode: 102
Minor opcode: 0
Resource id: 0x0
ERROR:Communication problem with kicker, it probably crashed.
Indeed it did crash:
Can someone please help me ?
Oli |
|
Back to top |
|
|
mriya3 Tux's lil' helper
Joined: 27 Jul 2004 Posts: 124 Location: Switzerland
|
Posted: Fri Dec 24, 2004 11:02 pm Post subject: |
|
|
I have the same problem (tried kde 3.3.1 and 3.3.2 from ~sparc)
Kicker crashes at startup:
Code: | DCOP aborting (delayed) call from 'anonymous-9276' to 'kicker'
ERROR: Communication problem with kicker, it probably crashed. |
The KDE crash handler seems to say something about a settime() function in libpthread.so.0
The machine is a Sunblade 100 w/512MB RAM, kernel 2.6.7
emerge info:
Code: | Portage 2.0.51-r3 (default-linux/sparc/sparc64/2004.3, gcc-3.3.4, glibc-2.3.3.20040420-r2, 2.6.7 sparc64)
=================================================================
System uname: 2.6.7 sparc64 sun4u
Gentoo Base System version 1.4.16
Autoconf: sys-devel/autoconf-2.59-r5
Automake: sys-devel/automake-1.8.5-r1
Binutils: sys-devel/binutils-2.14.90.0.8-r1
Headers: sys-kernel/linux-headers-2.4.23
Libtools: sys-devel/libtool-1.5.2-r7
ACCEPT_KEYWORDS="sparc"
AUTOCLEAN="yes"
CFLAGS="-mcpu=v8 -mtune=v9 -O2 -pipe -fomit-frame-pointer"
CHOST="sparc-unknown-linux-gnu"
COMPILER=""
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-mcpu=v8 -mtune=v9 -O2 -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distlocks sandbox"
GENTOO_MIRRORS="http://gentoo.osuosl.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="sparc X arts avi berkdb bitmap-fonts bonobo cdparanoia crypt cups encode esd f77 fam fbcon flac foomaticdb fortran gcc64 gdbm gif gimpprint gnome gstreamer gtk gtk2 imagemagick imlib java jpeg kde libgda libwww mad mikmod motif mozilla mpeg ncurses nls oggvorbis opengl oss pam pdflib perl png python qt readline sdl spell ssl tcpd tiff truetype xine xml2 xmms xv zlib linguas_it" |
_________________ --
http://www.mriya3.tk | http://www.mriyasoftware.com
--
"Make everything as simple as possible, but not simpler."
-- Albert Einstein |
|
Back to top |
|
|
ashu69 n00b
Joined: 09 Nov 2004 Posts: 45
|
Posted: Tue Dec 28, 2004 3:07 am Post subject: |
|
|
Try this: edit $HOME/.kde/share/config/kickerrc and remove all applets listed therein.
kicker should start fine. Then start adding applets one by one to find the one which
crashes kicker. Then learn to live without that one.
PS: Don't simply remove the Applet stanzas in the begenning of the file. Look for references
to those applets further down in the file (in the [General] section) and remove the
reference as well.
HTH
-a |
|
Back to top |
|
|
mriya3 Tux's lil' helper
Joined: 27 Jul 2004 Posts: 124 Location: Switzerland
|
Posted: Tue Dec 28, 2004 10:50 am Post subject: |
|
|
I've already tried to remove ~/.kde/share/config/kickerrc, and also the whole ~/.kde directory....
I still have the same problem... kicker crashing... _________________ --
http://www.mriya3.tk | http://www.mriyasoftware.com
--
"Make everything as simple as possible, but not simpler."
-- Albert Einstein |
|
Back to top |
|
|
ibtim13 Tux's lil' helper
Joined: 12 Sep 2003 Posts: 84 Location: Troy, NY
|
Posted: Tue Dec 28, 2004 2:43 pm Post subject: |
|
|
It seems, now that I've finished compiling kde, that I also have the
same problem you have, on an Ultra2.
One of these days something is going to work the way it should the first time....One of these days...
I had kde up and running on solaris 9, but I've never gotten it to compile
in gentoo on sparc before, now that I have, it doesn't work..sadness. _________________ Grrr, can't think of anything clever right now, I'll go back and edit this later (9/12/2003) |
|
Back to top |
|
|
robbyjo Guru
Joined: 06 Apr 2003 Posts: 462
|
Posted: Tue Dec 28, 2004 7:39 pm Post subject: |
|
|
For me it seems that the crash was caused by aRts output. I disabled it and it works like a charm. Hope this helps. |
|
Back to top |
|
|
robbyjo Guru
Joined: 06 Apr 2003 Posts: 462
|
Posted: Tue Dec 28, 2004 9:00 pm Post subject: |
|
|
Nah, scratch what I said. Kicker still bombed in my box . |
|
Back to top |
|
|
robbyjo Guru
Joined: 06 Apr 2003 Posts: 462
|
Posted: Wed Dec 29, 2004 1:33 am Post subject: |
|
|
Okay,
After emerging the gdb, this is the debug trace:
Code: | Using host libthread_db library "/lib/libthread_db.so.1".
[KCrash handler]
#3 0x7103b34c in QTime::addMSecs () from /usr/qt/3/lib/libqt-mt.so.3
#4 0x7103b2b0 in QTime::addSecs () from /usr/qt/3/lib/libqt-mt.so.3
#5 0x71c8117c in ClockApplet::clockGetTime ()
from /usr/kde/3.3/lib/kde3/clock_panelapplet.so
#6 0x71c771c0 in DigitalClock::updateClock ()
from /usr/kde/3.3/lib/kde3/clock_panelapplet.so
#7 0x71c7f118 in ClockApplet::slotApplySettings ()
from /usr/kde/3.3/lib/kde3/clock_panelapplet.so
#8 0x71c7e33c in ClockApplet::ClockApplet ()
from /usr/kde/3.3/lib/kde3/clock_panelapplet.so
#9 0x71c75c00 in init () from /usr/kde/3.3/lib/kde3/clock_panelapplet.so
#10 0x71abd688 in PluginLoader::loadApplet ()
from /usr/kde/3.3/lib/libkickermain.so.1
#11 0x71a3febc in InternalAppletContainer::InternalAppletContainer ()
from /usr/kde/3.3/lib/libkdeinit_kicker.so
#12 0x71a4b43c in PluginManager::createAppletContainer ()
from /usr/kde/3.3/lib/libkdeinit_kicker.so
#13 0x71a2ce98 in ContainerArea::defaultContainerConfig ()
from /usr/kde/3.3/lib/libkdeinit_kicker.so
#14 0x71a27c58 in Kicker::Kicker () from /usr/kde/3.3/lib/libkdeinit_kicker.so
#15 0x71a25a7c in kdemain () from /usr/kde/3.3/lib/libkdeinit_kicker.so
#16 0x00014dd4 in ?? () |
Any idea? |
|
Back to top |
|
|
ibtim13 Tux's lil' helper
Joined: 12 Sep 2003 Posts: 84 Location: Troy, NY
|
Posted: Wed Dec 29, 2004 3:47 pm Post subject: |
|
|
Just a guess, but it sure looks like something's wrong with the clock. _________________ Grrr, can't think of anything clever right now, I'll go back and edit this later (9/12/2003) |
|
Back to top |
|
|
ashu69 n00b
Joined: 09 Nov 2004 Posts: 45
|
Posted: Wed Dec 29, 2004 7:42 pm Post subject: |
|
|
Having wasted enoromous amounts of time on this particular
problem (including an unnecessary recompile of kde ), here are two
things i learned the hard way, hope someone would find it
useful.
1. Removing kickerrc does NOT help, it would be re-created when you
start kde, and the problem would remain. [I know, this sucks...]
You really HAVE to edit kickerrc and remove applets.
2. Make sure your glibc is at a stable rev. Anything above
2.3.3.20040420-r2 is evil, as far as kde is concerned.
HTH
-a |
|
Back to top |
|
|
ibtim13 Tux's lil' helper
Joined: 12 Sep 2003 Posts: 84 Location: Troy, NY
|
Posted: Thu Dec 30, 2004 3:03 am Post subject: |
|
|
My glibc is 2.3.3.20040420-r2 not anything higher
and my kickerrc has no application lines in it
and the kicker still crashes. _________________ Grrr, can't think of anything clever right now, I'll go back and edit this later (9/12/2003) |
|
Back to top |
|
|
Weeve Retired Dev
Joined: 30 Oct 2002 Posts: 641
|
Posted: Thu Dec 30, 2004 4:37 am Post subject: |
|
|
This is what worked for me
- Start KDE
- Let kicker crash
- Press Alt+F2 to bring up the Run dialog box
- Type kcontrol into the Run dialog box and press enter
- Select Sound & Multimedia > Sound System from the resulting window
- De-select the "Enable the sound system" option and click apply
- Restart KDE and kicker starts successfully
|
|
Back to top |
|
|
mriya3 Tux's lil' helper
Joined: 27 Jul 2004 Posts: 124 Location: Switzerland
|
Posted: Thu Dec 30, 2004 3:33 pm Post subject: |
|
|
Quote: | This is what worked for me
1. Start KDE
2. Let kicker crash
3. Press Alt+F2 to bring up the Run dialog box
4. Type kcontrol into the Run dialog box and press enter
5. Select Sound & Multimedia > Sound System from the resulting window
6. De-select the "Enable the sound system" option and click apply
7. Restart KDE and kicker starts successfully |
Unfortunately it doesn't work for me... _________________ --
http://www.mriya3.tk | http://www.mriyasoftware.com
--
"Make everything as simple as possible, but not simpler."
-- Albert Einstein |
|
Back to top |
|
|
Weeve Retired Dev
Joined: 30 Oct 2002 Posts: 641
|
Posted: Thu Dec 30, 2004 4:10 pm Post subject: |
|
|
Since you had earlier mentioned that you had adjusted some of your config files, you might try removing any current KDE settings for your user and try that method again. The following command (being run by the same user you run Kshould clean out most of the gotchas;
Code: | rm -rf ${HOME}/.kde* ${HOME}/.mcop* |
|
|
Back to top |
|
|
mriya3 Tux's lil' helper
Joined: 27 Jul 2004 Posts: 124 Location: Switzerland
|
|
Back to top |
|
|
ibtim13 Tux's lil' helper
Joined: 12 Sep 2003 Posts: 84 Location: Troy, NY
|
Posted: Sun Jan 02, 2005 1:10 am Post subject: |
|
|
It also did not work for me. I'm wondering if CFLAGS might have anything to do with this...but I'd like to know before I go recompiling everything.
I've got:
"-mcpu=ultrasparc -O3 -pipe -mvis -fomit-frame-pointer"
any thoughts? _________________ Grrr, can't think of anything clever right now, I'll go back and edit this later (9/12/2003) |
|
Back to top |
|
|
ashu69 n00b
Joined: 09 Nov 2004 Posts: 45
|
Posted: Mon Jan 03, 2005 10:11 pm Post subject: |
|
|
Hmmm.... another long shot: Do you have any conflicts in /usr/kde/ ? Search for
._cfg????_* and make sure you resolve those conflicts (i just copy them over). Also,
as Weeve has already suggested, make sure you have arts disabled via kcontrol.
As for CFLAGS, i have what you have except the -mvis option, i doubt that is the
problem, but then i don't really know.
HTH
-a |
|
Back to top |
|
|
robbyjo Guru
Joined: 06 Apr 2003 Posts: 462
|
Posted: Tue Jan 04, 2005 8:14 pm Post subject: |
|
|
Weeve,
Can you post your kernel configuration? I suspect that this has something to do with nvram or PC RTC or something. Thanks. |
|
Back to top |
|
|
Weeve Retired Dev
Joined: 30 Oct 2002 Posts: 641
|
Posted: Mon Jan 10, 2005 11:48 pm Post subject: |
|
|
I'm using gentoo-dev-sources-2.6.9-r12 on a Blade 1000 with Enhanced Real Time Clock Support and Mostek real time clock support enabled.
However I do have an Ultra 2 running sparc-sources-2.4.28-r3 that does crash. It does have Mostek real time clock support enabled, but there is no option in 2.4.28 for Enhanced Real Time Clock Support |
|
Back to top |
|
|
thesimp2 n00b
Joined: 12 Jan 2005 Posts: 1
|
Posted: Fri Jan 14, 2005 6:46 pm Post subject: |
|
|
Any new clues on this problem? I have the same KDE Panel (kicker) crash on my E250 with KDE3.3.2 and kernel 2.4.24.
I tried al of the above mentioned tricks but it still crashes 100% reproducable when I start KDE. |
|
Back to top |
|
|
Weeve Retired Dev
Joined: 30 Oct 2002 Posts: 641
|
Posted: Sat Jan 15, 2005 5:08 pm Post subject: |
|
|
Unfortunately not.
If everyone could post ideas, suggestions, etc at https://bugs.gentoo.org/show_bug.cgi?id=77623 so we can track it in the bugs system, that would be most excellent.
Thanks |
|
Back to top |
|
|
thesimp n00b
Joined: 05 Jul 2004 Posts: 5
|
Posted: Sun Jan 16, 2005 12:23 am Post subject: |
|
|
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.
The funny thing is that I have a x86 and a sparc with exactly the same packages/setup running side by side. Kicker on the x86 works and on the sparc it crashes. |
|
Back to top |
|
|
gentsquash l33t
Joined: 03 Nov 2004 Posts: 753 Location: Still a Gentoo beginner.
|
Posted: Fri Jan 28, 2005 6:30 pm Post subject: |
|
|
What is the "KDE crash panel", please, and
how does one invoke it? _________________ 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 |
|
|
biggyL Tux's lil' helper
Joined: 31 Jan 2005 Posts: 120 Location: Israel
|
Posted: Mon Jan 31, 2005 7:32 am Post subject: kicker crash |
|
|
Hello,
Does anyone succeeded to solve this crash problem on his system and in what way? |
|
Back to top |
|
|
thesimp n00b
Joined: 05 Jul 2004 Posts: 5
|
Posted: Tue Feb 01, 2005 10:14 pm Post subject: |
|
|
In my reply from jan-16 I was still a bit positive, but now I've given up. I'm not a computer newbie, but I am new to the "Gentoo on sparc + kde" thing. And trying to figure this problem out when you don't know what you are doing is rather difficult
At the moment I run XFCE4.2 as desktop on the sparc. Very different compared to kde, but I like it. |
|
Back to top |
|
|
|