Bug 182480

Summary: KDE4 Fails to Start
Product: [Unmaintained] kdelibs Reporter: Jared Freeman <jfreemanak>
Component: ksycocaAssignee: David Faure <faure>
Status: RESOLVED WORKSFORME    
Severity: crash CC: andresbajotierra, nospam
Priority: NOR Keywords: investigated, triaged
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Jared Freeman 2009-01-30 20:27:58 UTC 
Version:            (using KDE 4.2.0)
OS:                Linux
Installed from:    Ubuntu Packages

I am a GNOME kind of guy but decided to try out KDE.  I use Ubuntu, so I installed the Kubuntu-desktop.  When I try to start the KDE, I always get this message:


Application: KBuildSycoca (kbuildsycoca4), signal SIGABRT
0x00007fcd3921c5f0 in nanosleep () from /lib/libc.so.6

Thread 1 (Thread 0x7fcd3c9936f0 (LWP 7280)):
[KCrash Handler]
#5  0x00007fcd391a6fd5 in raise () from /lib/libc.so.6
#6  0x00007fcd391a8b43 in abort () from /lib/libc.so.6
#7  0x00007fcd39cf46b5 in qt_message_output () from /usr/lib/libQtCore.so.4
#8  0x00007fcd39cf47fd in qFatal () from /usr/lib/libQtCore.so.4
#9  0x00007fcd3c58d385 in ?? () from /usr/lib/libkdeinit4_kbuildsycoca4.so
#10 0x00007fcd3c58d6b3 in ?? () from /usr/lib/libkdeinit4_kbuildsycoca4.so
#11 0x00007fcd3c57acb2 in ?? () from /usr/lib/libkdeinit4_kbuildsycoca4.so
#12 0x00007fcd3c57db58 in ?? () from /usr/lib/libkdeinit4_kbuildsycoca4.so
#13 0x00007fcd3c57edaa in kdemain () from /usr/lib/libkdeinit4_kbuildsycoca4.so
#14 0x00007fcd39192466 in __libc_start_main () from /lib/libc.so.6
#15 0x0000000000400709 in _start ()

When I try to open a K application from GNOME, I get the same message as well.  I know I am not skilled enough to solve this issue, plus, like I said, I use GNOME primarily.  Thanks.
Comment 1 Juergen Heinemann 2009-01-31 09:45:51 UTC 
I have this Problem to, KDE4 didn't create all needed home directories.
Just test this script and restart kde4.
[CODE]
#!/bin/bash

test -x $(type -p kde4-config) || exit 1

for i in desktop autostart document ; do
  echo "`kde4-config --userpath ${i}`"
  mkdir --mode=0750 -p `kde4-config --userpath ${i}`
done

for i in `kde4-config --types | cut -d' ' -f1` ; do
  dest=`kde4-config --path ${i} | cut -d: -f1`
  test -n "`echo $dest | grep $HOME`" || continue;
  echo "$dest"
  mkdir --mode=0750 -p $dest
done

find `kde4-config --localprefix` -mindepth 1 -type d | xargs chmod 0750

if test -d $HOME/.xdg ; then
  find $HOME/.xdg -mindepth 1 -type d | xargs chmod 0750
fi
[/CODE]
Comment 2 Dario Andres 2009-01-31 13:45:24 UTC 
@Jared: If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here?
You need to install "kdelibs5-dbg"
Thanks :)
Comment 3 David Faure 2009-02-03 01:24:13 UTC 
Please run kbuildsycoca4 in a terminal and tell me what the (end of) the output is. You're hitting an assert, I would like to see which one ;)
Comment 4 Dario Andres 2009-03-25 19:16:24 UTC 
No response. Marking as NEEDSINFO
Comment 5 Andrew Crouthamel 2018-09-19 04:32:12 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Andrew Crouthamel 2018-10-21 05:09:23 UTC 
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!