Sagara Wijetunga wrote:
> James Tyrer wrote:
>> Sagara Wijetunga wrote:
>>
>>> James Tyrer wrote:
>>>
>>>> Sagara Wijetunga wrote:
>>>>
>>>>
>>>>> Hi all
>>>>>
>>>>> I have compiled only following KDE components from sources on
>>>>> Tomahawk Desktop (which is based on FreeBSD 7.2):
>>>>> Oxygen-Icons-4.3.4 kdelibs-4.3.4 KdeLibs-experimental-4.3.4
>>>>> KdePimLibs-4.3.4 kdebase-workspace-4.3.4 KdeBase-4.3.4
>>>>> kdebase-runtime-4.3.4
>>>>>
>>>>>
>>>>>
>>>> Please read the instruction:
>>>>
>>>> http://techbase.kde.org/Getting_Started/Build/KDE4.x
>>>>
>>>> and check the required packages:
>>>>
>>>> http://techbase.kde.org/Getting_Started/Build/KDE4/LFS
>>>>
>>>> Specifically, you need to either install KDESupport or the binaries
>>>> for all of the packages which it contains before you build KDELibs.
>>>>
>>>>
>>>> If this doesn't answer your problem, get back to us.
>>>>
>>>>
>>>>
>>> Hi
>>>
>>> Thanks for the reply.
>>>
>>> Tomahawk Desktop is very similar to LFS, therefore, I followed the
>>> http://techbase.kde.org/Getting_Started/Build/KDE4/LFS and
>>> http://cblfs.cross-lfs.org/index.php/KDE4.
>>>
>>> I did not install KDESupport but installed "KDE4 Support" components
>>> of the http://cblfs.cross-lfs.org/index.php/KDE4 and installed "KDE
>>> Core Packages" and then tried the startkde.
>>>
>>>
>> I wasn't really able to determine from you error logs, exactly why it
>> failed to start up. This isn't that simple since there are errors
>> even if it starts OK.
>>
>> There does appear to be an issue with Python and Glib that you should
>> look into, but I doubt that this is the cause of the KDE problem --
>> configure, build, & install "glib-2" & "pygobject" again and see if
>> that fixes it.
>>
>> However, these instructions are wrong:
>>
>> http://cblfs.cross-lfs.org/index.php/Starting_KDE
>>
>> I suggest that you try this for your ~/.xinitrc file:
>>
>> ------8<------8<------8<------8<------8<------8<------8<------8<------
>>
>> eval `dbus-launch --sh-syntax --exit-with-session`
>>
>> exec startkde
>>
>> ------8<------8<------8<------8<------8<------8<------8<------8<------
>>
>> If you still have problems, try this command:
>>
>> startx > Xuser.log 2>&1
>>
>> and see if it was an X error that caused termination.
>>
>>
> The Python issue was known and seems harmless.
>
> I have found an error, some important variables mentioned in
> http://techbase.kde.org/Getting_Started/Build/KDE4.x were not set
> properly. I have fixed it and then ran startkde, now it complain
> following:
> **
> kstartupconfig4 does not exist or failed. The error code is 3. Check
> your installation.
>
> kstartupconfig4 exists:
> type kstartupconfig4
> kstartupconfig4 is /usr/bin/kstartupconfig4
>
> I have Google searched on kstartupconfig4 issue, but still could not
> find a proper fix, any idea to share?
>
> Regards
> Sagara
>
>
I have another update regarding this.
The .kde contains only .kde/share/config/. No files.
The .kde4 contains only .kde4/share/config/startupconfigkeys.
The /usr/bin/kstartupconfig4 is from kdebase-workspace.
When I run /usr/bin/kstartupconfig4 on a console, the exit code is 3.
According to kdebase-workspace-4.3.4/kstartupconfig/kstartupconfig.cpp:
int main()
{
char kdehome[ 1024 ];
if( getenv( "KDEHOME" ))
strlcpy( kdehome, getenv( "KDEHOME" ), 1024 );
else if( getenv( "HOME" ))
{
strlcpy( kdehome, getenv( "HOME" ), 1024 );
strlcat( kdehome, "/" KDE_DEFAULT_HOME, 1024 );
}
else
return 1;
char filename[ 1024 ];
strlcpy( filename, kdehome, 1024 );
strlcat( filename, "/share/config/startupconfig", 1024 );
if( access( filename, R_OK ) != 0 )
{
int ret = system( "kdostartupconfig4" );
return WEXITSTATUS( ret );
}
}
Since I do not have a /root/.kde4/share/config/startupconfig, it seems
/usr/bin/kstartupconfig4 runs /usr/bin/kdostartupconfig4.
When I run /usr/bin/kdostartupconfig4 on a console, the exit code is 3.
According to the
kdebase-workspace-4.3.4/kstartupconfig/kdostartupconfig.cpp:
int main( int argc, char **argv )
{
#define I18N_NOEXTRACT( x ) ki18n( x )
// Set catalog to "kdelibs4" for KLocale to initialize languages
properly.
KAboutData about( "kdostartupconfig4", "kdelibs4",
I18N_NOEXTRACT( "kdostartupconfig4" ), "1.0" );
KComponentData inst( &about );
kDebug() << "Running kdostartupconfig.";
KCmdLineArgs::init( argc, argv, &about ); // for KLocale not to
complain about encoding
QString keysname = KStandardDirs::locateLocal( "config",
"startupconfigkeys" );
QFile keys( keysname );
if( !keys.open( QIODevice::ReadOnly ))
return 3;
}
It seems the exit code 3 comes from the keys.open( QIODevice::ReadOnly )
failure.
This is what .kde4/share/config/startupconfigkeys contains:
cat .kde4/share/config/startupconfigkeys
kcminputrc Mouse cursorTheme 'Oxygen_Black'
kcminputrc Mouse cursorSize ''
ksplashrc KSplash Theme Default
ksplashrc KSplash Engine KSplashX
kcmrandrrc Display ApplyOnStartup false
kcmrandrrc [Screen0]
kcmrandrrc [Screen1]
kcmrandrrc [Screen2]
kcmrandrrc [Screen3]
kcmfonts General forceFontDPI 0
kdeglobals Locale Language '' # trigger requesting languages from KLocale
Why keys.open( QIODevice::ReadOnly ) fail?
Regards
Sagara
___________________________________________________
This message is from the kde mailing list.
Account management: https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.
