Bug 79277 - kdevelop crashes on start on RH7.x based systems
Summary: kdevelop crashes on start on RH7.x based systems
Status: RESOLVED NOT A BUG
Alias: None
Product: kdevelop
Classification: Applications
Component: general (show other bugs)
Version: 3.0.2
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: KDevelop Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-04-08 07:51 UTC by jsu2
Modified: 2004-04-09 02:18 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jsu2 2004-04-08 07:51:36 UTC
Version:           3.0.2 (using KDE KDE 3.2.1)
Installed from:    Compiled From Sources
Compiler:          gcc 3.3.3 Compiled gcc 3.3.3 from source with only C and C++ enabled.
OS:          Linux

When I try to run my newly built kdevelop 3.0.2, I get the following error:

  $ kdevelop
  _kde_IceTransmkdir: Owner of /tmp/.ICE-unix should be set to root
  QPixmap: Cannot create a QPixmap when no GUI is being used
  QPixmap: Cannot create a QPixmap when no GUI is being used
  QPixmap: Cannot create a QPixmap when no GUI is being used
  QPixmap: Cannot create a QPixmap when no GUI is being used
  kbuildsycoca running...
  KCrash: Application 'kbuildsycoca' crashing...
  drkonqi: Unknown option '--startupid'.
  drkonqi: Use --help to get a list of available command line options.
  kdeinit: Shutting down running client.
  Mutex destroy failure: Device or resource busy
  KCrash: Application 'kdevelop' crashing...
  drkonqi: Unknown option '--startupid'.
  drkonqi: Use --help to get a list of available command line options.
  [jsu2@zenodotus jsu2]$ ---------------------------------
  It looks like dcopserver is already running. If you are sure
  that it is not already running, remove
/home/jsu2/.DCOPserver_zenodotus.library.emory.edu_localhost_13
  and start dcopserver again.
  ---------------------------------

  QPixmap: Cannot create a QPixmap when no GUI is being used
  QPixmap: Cannot create a QPixmap when no GUI is being used
  KDE Daemon (kded) already running.

On the alpha architecture, I get the following:

  $ kdevelop
  QPixmap: Cannot create a QPixmap when no GUI is being used
  QPixmap: Cannot create a QPixmap when no GUI is being used
  QPixmap: Cannot create a QPixmap when no GUI is being used
  QPixmap: Cannot create a QPixmap when no GUI is being used
  kbuildsycoca running...
  KCrash: Application 'kdevelop' crashing...
  Unable to start Dr. Konqi
  Mutex destroy failure: Device or resource busy
  ICE default IO error handler doing an exit(), pid = 26877, errno = 0

The above happens on both i386 and alpha running RedHat 7.x.  Here's my system 
info:

  # kde-config --version
  Qt: 3.3.1
  KDE: 3.2.1
  kde-config: 1.0

  # gcc --version
  gcc (GCC) 3.3.3
  
  # perl --version

  This is perl, v5.8.0 built for i386-linux-thread-multi
  (with 1 registered patch, see perl -V for more detail)

  # autoconf --version
  autoconf (GNU Autoconf) 2.57

  # automake --version
  automake (GNU automake) 1.6.3

  # flex --version
  flex version 2.5.4

I have db2, db3, and db4 installed, so between those, configure probably
picked the right one.  Also, kdelibs was built with automake 1.4.  I
installed automake 1.6 to build kdevelop.  I was able to build kdevelop
with automake 1.4 as well.  But, they both crashed.  Here's my how I
configured kdevelop:

  ./configure --prefix=/opt/kde --without-arts --disable-debug

I compiled kdelibs and kdevelop on my debian system as well, and kdevelop runs 
without any problems.  Other than the debian systems having more newer bits
than the RedHat systems, I'm not sure what I did differently.  The RedHat i386 system also has an older KDE installed as well:

kdebase-devel-3.0.5a-0.73.4
kdebase-3.0.5a-0.73.4
kdelibs-devel-3.0.5a-0.73.2
kdelibs-3.0.5a-0.73.2
Comment 1 Jens Dagerbo 2004-04-08 14:27:31 UTC
In the first console trace you have 'kbuildsycoca' crashing before kdevelop does. If not even that can run without crashing something is seriously broken on your system. Does every other KDE app run successfully??

Please rebuild kdevleop with --enable-debug=full. A crashreport without a backtrace or a way to recreate the problem is quite useless.

Comment 2 jsu2 2004-04-08 19:50:44 UTC
I only built kdelibs for kdevelop, so I really don't have any other kde apps.  On the RedHat 7.3 i386 system, there are some older KDE stuff like kdm, but that's about all.  

I've rebuilt kdevelop with "--enable-debug=full", and now I get a dialog window that says:

  There was an error setting up inter-process
  communications for KDE.  The message returned
  by the system was:

  Could not read network connection list.
  /home/jsu2/.DCOPserver_zenodotus.library.emory.edu_localhost_12

  Please check that the "dcopserver" program is running!

The output of the console are as follows:

  _kde_IceTransmkdir: Owner of /tmp/.ICE-unix should be set to root
  ICE Connection rejected!

  DCOPClient::attachInternal. Attach failed Authentication Rejected, reason : Non of the authentication protocols specified are supported and host-based authentication failed
  ICE Connection rejected!

  DCOPClient::attachInternal. Attach failed Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
  DCOPServer self-test failed.
  kdeinit: DCOPServer could not be started, aborting.
  kdevelop (core): SPLASH: message=Starting core application
  kdevelop (core): SPLASH: message=Loading Settings
  KCrash: Application 'kdevelop' crashing...
  drkonqi: Unknown option '--startupid'.
  drkonqi: Use --help to get a list of available command line options.

I'm willing to accept that my kdelibs may not be sane.  But, as I noted initially, I installed kdelibs and kdevelop similarly on a Debian system, and all is well on it.  Is there some way for me to verify my kdelibs installation?
Comment 3 Jens Dagerbo 2004-04-09 02:18:31 UTC
This is turning into a support issue. There is something wrong with your installation and it's not related to KDevelop. Closing bug.