Just updated to MileStone 4 and get error: unable to start kdeinit4
from /var/log/messages:
Jul 22 19:09:50 wahoo dbus-daemon: Rejected send message, 2 matched rules; type="signal", sender=":1.12" (uid=105 pid=4320 comm="avahi-daemon: starting up) interface="org.freedesktop.Avahi.ServiceTypeBrowser" member="AllForNow" error name="(unset)" requested_reply=0 destination=":1.404" (uid=1000 pid=20248 comm= kdeinit4: kded4 [kdeinit]))
Help :^)
* Patrick Shanahan ptilopteri@gmail.com [07-22-09 22:57]:
Just updated to MileStone 4 and get error: unable to start kdeinit4
from /var/log/messages:
Jul 22 19:09:50 wahoo dbus-daemon: Rejected send message, 2 matched rules; type="signal", sender=":1.12" (uid=105 pid=4320 comm="avahi-daemon: starting up) interface="org.freedesktop.Avahi.ServiceTypeBrowser" member="AllForNow" error name="(unset)" requested_reply=0 destination=":1.404" (uid=1000 pid=20248 comm= kdeinit4: kded4 [kdeinit]))
Today's update and reinstall of openSUSE did not alleviate the problem.
"Could not start kdeinit4. Check your installation"
Suggestion?
On Thursday 23 July 2009 22:51:39 Patrick Shanahan wrote:
- Patrick Shanahan ptilopteri@gmail.com [07-22-09 22:57]:
Just updated to MileStone 4 and get error: unable to start kdeinit4
from /var/log/messages:
Jul 22 19:09:50 wahoo dbus-daemon: Rejected send message, 2 matched rules; type="signal", sender=":1.12" (uid=105 pid=4320 comm="avahi-daemon: starting up) interface="org.freedesktop.Avahi.ServiceTypeBrowser" member="AllForNow" error name="(unset)" requested_reply=0 destination=":1.404" (uid=1000 pid=20248 comm= kdeinit4: kded4 [kdeinit]))
Today's update and reinstall of openSUSE did not alleviate the problem.
"Could not start kdeinit4. Check your installation"
Suggestion?
Please file a bug ;)
Since it mentions avahi, try disabling the two avahi services and login again. Does this help?
Andreas
* Andreas Jaeger aj@novell.com [01-01-70 11:34]:
On Thursday 23 July 2009 22:51:39 Patrick Shanahan wrote:
- Patrick Shanahan ptilopteri@gmail.com [07-22-09 22:57]:
Just updated to MileStone 4 and get error: unable to start kdeinit4
from /var/log/messages:
Jul 22 19:09:50 wahoo dbus-daemon: Rejected send message, 2 matched rules; type="signal", sender=":1.12" (uid=105 pid=4320 comm="avahi-daemon: starting up) interface="org.freedesktop.Avahi.ServiceTypeBrowser" member="AllForNow" error name="(unset)" requested_reply=0 destination=":1.404" (uid=1000 pid=20248 comm= kdeinit4: kded4 [kdeinit]))
Today's update and reinstall of openSUSE did not alleviate the problem.
"Could not start kdeinit4. Check your installation"
Suggestion?
Please file a bug ;)
Since it mentions avahi, try disabling the two avahi services and login again. Does this help?
disabling avahi services does not make a difference.
kdeinit4 in a console: kdeinit4: Aborting. $DISPLAY is not set.
Note: still able to start gnome/icewm/xfce4/twm
will file a bug, tks
On Friday 24 of July 2009, Patrick Shanahan wrote:
kdeinit4 in a console: kdeinit4: Aborting. $DISPLAY is not set.
Of course. How do you expect KDE to work in text mode?
* Lubos Lunak l.lunak@suse.cz [01-01-70 11:34]:
On Friday 24 of July 2009, Patrick Shanahan wrote:
kdeinit4 in a console: kdeinit4: Aborting. $DISPLAY is not set.
Of course. How do you expect KDE to work in text mode?
Runlevel 5, X was running.
Or am I mistaken?
On 2009/07/24 16:21 (GMT-0400) Patrick Shanahan composed:
- Lubos Lunak l.lunak@suse.cz [01-01-70 11:34]:
On Friday 24 of July 2009, Patrick Shanahan wrote:
kdeinit4 in a console: kdeinit4: Aborting. $DISPLAY is not set.
Of course. How do you expect KDE to work in text mode?
Runlevel 5, X was running.
Or am I mistaken?
I think he thought you meant literally a console, as in tty[1-6], rather than Konsole.
* Felix Miata mrmazda@earthlink.net [07-24-09 16:33]:
I think he thought you meant literally a console, as in tty[1-6], rather than Konsole.
and I *did*. :^)
* Lubos Lunak l.lunak@suse.cz [07-24-09 15:40]:
On Friday 24 of July 2009, Patrick Shanahan wrote:
kdeinit4 in a console: kdeinit4: Aborting. $DISPLAY is not set.
Of course. How do you expect KDE to work in text mode?
perhaps incorrect terminology, from tty1 in runlevel 5.
On Friday 24 of July 2009, Patrick Shanahan wrote:
- Lubos Lunak l.lunak@suse.cz [07-24-09 15:40]:
On Friday 24 of July 2009, Patrick Shanahan wrote:
kdeinit4 in a console: kdeinit4: Aborting. $DISPLAY is not set.
Of course. How do you expect KDE to work in text mode?
perhaps incorrect terminology, from tty1 in runlevel 5.
If you want to run KDE manually, for whatever reason, login into the failsafe session type from KDM.
On Thursday 23 July 2009, Patrick Shanahan wrote:
Just updated to MileStone 4 and get error: unable to start kdeinit4
try launching "kdeinit4" manually and see if there is an error message. most likely something with "undefined symbol". please paste that.
Greetings, Dirk
* Dirk Müller dmueller@suse.de [01-01-70 11:34]:
On Thursday 23 July 2009, Patrick Shanahan wrote:
Just updated to MileStone 4 and get error: unable to start kdeinit4
try launching "kdeinit4" manually and see if there is an error message. most likely something with "undefined symbol". please paste that.
kdeinit4: Aborting. $DISPLAY is not set.
tks,
On Friday 24 July 2009, Patrick Shanahan wrote:
try launching "kdeinit4" manually and see if there is an error message. most likely something with "undefined symbol". please paste that.
kdeinit4: Aborting. $DISPLAY is not set.
Okay, please try from a X "failsafe" session.
Thanks, Dirk
* Dirk Müller dmueller@suse.de [07-26-09 18:01]:
On Friday 24 July 2009, Patrick Shanahan wrote:
try launching "kdeinit4" manually and see if there is an error message. most likely something with "undefined symbol". please paste that.
kdeinit4: Aborting. $DISPLAY is not set.
Okay, please try from a X "failsafe" session.
removed the soft link to /opt/kde3/bin/start_kdeinit_wrapper
The kde-failsafe menu offering results in the same "unable to start" notice.
The plain failsafe opens an xterm session and issuing "kdeinit4" provides:
22:43 wahoo:~ > kdeinit4 kdeinit4: preparing to launch /usr/lib64/libkdeinit4_klauncher.so kdeinit4: preparing to launch /usr/lib64/libkdeinit4_kded4.so kdeinit4: preparing to launch /usr/lib64/libkdeinit4_kbuildsycoca4.so kbuildsycoca4 running... kdeinit4: preparing to launch /usr/lib64/libkdeinit4_kbuildsycoca4.so kbuildsycoca4 running... kdeinit4: preparing to launch /usr/lib64/libkdeinit4_kconf_update.so
and no error
more info:
from this failsafe xterm I can issue kdeinit4 rckdm start (as root) plasma-desktop
and I have a running desktop/system lacking some of my extras, kjots, ktea, etc.
Do you need any other info?
On Monday 27 July 2009, Patrick Shanahan wrote:
The kde-failsafe menu offering results in the same "unable to start" notice.
interesting. is there any output in ~/.xsession-errors?
Greetings, Dirk
* Dirk Müller dmueller@suse.de [07-28-09 13:30]:
On Monday 27 July 2009, Patrick Shanahan wrote:
The kde-failsafe menu offering results in the same "unable to start" notice.
interesting. is there any output in ~/.xsession-errors?
/etc/X11/xim: Checking whether an input method should be started. /usr/bin/manpath: can't set the locale; make sure $LC_* and $LANG are correct /home/pat/.profile: line 55: /usr/X11R6/bin/unclutter: No such file or directory /etc/X11/xim: line 72: CONTROL-G: No such file or directory sourcing /etc/sysconfig/language to get the value of INPUT_METHOD INPUT_METHOD is not set or empty (no user selected input method). Trying to start a default input method for the locale --failsafe ... There is no default input method for the current locale. Dummy input method "none" (do not use any fancy input method by default) /usr/bin/manpath: can't set the locale; make sure $LC_* and $LANG are correct
Angels we have heard on High Tell us to go out and Buy. -- Tom Lehrer
If at first you don't succeed, give up, no use being a damn fool.
startkde: Starting up... /usr/bin/startkde: line 380: /usr/lib64/kde4/libexec/start_kdeinit_wrapper: No such file or directory startkde: Could not start kdeinit4. Check your installation.
NOTE: I can start from the twm failsave option and I can start the regular kde4 session with the soft link to /opt/kde3/bin/start_kdeinit_wrapper.
On Tue, Jul 28, 2009 at 21:02, Patrick Shanahanptilopteri@gmail.com wrote:
- Dirk Müller dmueller@suse.de [07-28-09 13:30]:
On Monday 27 July 2009, Patrick Shanahan wrote:
The kde-failsafe menu offering results in the same "unable to start" notice.
interesting. is there any output in ~/.xsession-errors?
[...]
startkde: Starting up... /usr/bin/startkde: line 380: /usr/lib64/kde4/libexec/start_kdeinit_wrapper: No such file or directory startkde: Could not start kdeinit4. Check your installation.
Two lines above is your error. Go find that file. I don't use X86_64 but my investigations led me to kdelib4.
ne...
* ne... guhvies@gmail.com [07-29-09 02:00]:
On Tue, Jul 28, 2009 at 21:02, Patrick Shanahanptilopteri@gmail.com wrote:
- Dirk Müller dmueller@suse.de [07-28-09 13:30]:
On Monday 27 July 2009, Patrick Shanahan wrote:
The kde-failsafe menu offering results in the same "unable to start" notice.
interesting. is there any output in ~/.xsession-errors?
[...]
startkde: Starting up... /usr/bin/startkde: line 380: /usr/lib64/kde4/libexec/start_kdeinit_wrapper: No such file or directory startkde: Could not start kdeinit4. Check your installation.
Two lines above is your error. Go find that file. I don't use X86_64 but my investigations led me to kdelib4.
ne...
note: rpm -ql kdelibs4 |grep wrapper /usr/bin/kdeinit4_wrapper /usr/bin/kwrapper4
there is *no*: start_kdeinit_wrapper
and w/kdelibs4-4.3.61svn998540-3.4 it is not required kdelibs4-4.3.61svn998540-3.4 installed Mon 27 Jul 2009 08:39:34 AM EDT
but it may break again with the next "zypper dup" :^(
On Wed, Jul 29, 2009 at 16:45, Patrick Shanahanptilopteri@gmail.com wrote:
- ne... guhvies@gmail.com [07-29-09 02:00]:
On Tue, Jul 28, 2009 at 21:02, Patrick Shanahanptilopteri@gmail.com wrote:
- Dirk Müller dmueller@suse.de [07-28-09 13:30]:
On Monday 27 July 2009, Patrick Shanahan wrote:
The kde-failsafe menu offering results in the same "unable to start" notice.
interesting. is there any output in ~/.xsession-errors?
[...]
startkde: Starting up... /usr/bin/startkde: line 380: /usr/lib64/kde4/libexec/start_kdeinit_wrapper: No such file or directory startkde: Could not start kdeinit4. Check your installation.
Two lines above is your error. Go find that file. I don't use X86_64 but my investigations led me to kdelib4.
ne...
note: rpm -ql kdelibs4 |grep wrapper /usr/bin/kdeinit4_wrapper /usr/bin/kwrapper4
there is *no*: start_kdeinit_wrapper
and w/kdelibs4-4.3.61svn998540-3.4 it is not required kdelibs4-4.3.61svn998540-3.4 installed Mon 27 Jul 2009 08:39:34 AM EDT
but it may break again with the next "zypper dup" :^( From what I read above, it seems your KDE is 4.4pre. Is this what comes with
MileStone 4? If yes, I may not be able to help you as I'm on KDE4.3RC3. [work]$ rpm -q kdelibs4 kdelibs4-4.2.98-146.1.i586
[work]$ rpm -ql kdelibs4 | /bin/grep wrapper /usr/bin/kdeinit4_wrapper /usr/bin/kwrapper4 /usr/lib/kde4/libexec/start_kdeinit_wrapper
Seems that since it is referenced from statrtkde, it is needed.
HTH ne...
* ne... guhvies@gmail.com [07-29-09 12:10]:
MileStone 4?
:^) Yes
If yes, I may not be able to help you as I'm on KDE4.3RC3. [work]$ rpm -q kdelibs4 kdelibs4-4.2.98-146.1.i586
[work]$ rpm -ql kdelibs4 | /bin/grep wrapper /usr/bin/kdeinit4_wrapper /usr/bin/kwrapper4 /usr/lib/kde4/libexec/start_kdeinit_wrapper
Seems that since it is referenced from statrtkde, it is needed.
??
as presently installed here, start_kdeinit_wrapper is *not* needed ???
I am adding the soft link when I get the error and removing it when there is an update to test necessity. Presently, it is not required.
This may all be due to some funny mix of kde3 requirements pulled in to support basket and quanta and a few other apps not available yet for kde4....
On Wed, Jul 29, 2009 at 17:16, Patrick Shanahanptilopteri@gmail.com wrote:
- ne... guhvies@gmail.com [07-29-09 12:10]:
MileStone 4?
:^) Yes
If yes, I may not be able to help you as I'm on KDE4.3RC3. [work]$ rpm -q kdelibs4 kdelibs4-4.2.98-146.1.i586
[work]$ rpm -ql kdelibs4 | /bin/grep wrapper /usr/bin/kdeinit4_wrapper /usr/bin/kwrapper4 /usr/lib/kde4/libexec/start_kdeinit_wrapper
Seems that since it is referenced from statrtkde, it is needed.
??
as presently installed here, start_kdeinit_wrapper is *not* needed ???
I am adding the soft link when I get the error and removing it when there is an update to test necessity. Presently, it is not required.
This may all be due to some funny mix of kde3 requirements pulled in to support basket and quanta and a few other apps not available yet for kde4....
I have looked into this further and if the error from is startkde is correct then the version you have is not from kdebase4-workspace-4.3.61svn998540. I pulled /spare/RPMS/kdebase4-workspace-4.3.61svn998540-3.1.x86_64.rpm and looked at startkde. It has a reference to kdeinit4 and not /usr/lib/kde4/libexec/start_kdeinit_wrapper as you rightly noted. I would change the following line in startkde from
LD_BIND_NOW=true /usr/lib/kde4/libexec/start_kdeinit_wrapper +kcminit_startup
to
LD_BIND_NOW=true kdeinit4 +kcminit_startup
and see whether this works.
HTH ne... PS: http://download.opensuse.org/repositories/KDE:/KDE4:/UNSTABLE:/Desktop/openS... only had 4.3.61svn998540-3.1and not 4.3.61svn998540-3.4 as you have.
* ne... guhvies@gmail.com [07-29-09 14:45]:
On Wed, Jul 29, 2009 at 17:16, Patrick Shanahanptilopteri@gmail.com wrote:
as presently installed here, start_kdeinit_wrapper is *not* needed ???
I am adding the soft link when I get the error and removing it when there is an update to test necessity. Presently, it is not required.
This may all be due to some funny mix of kde3 requirements pulled in to support basket and quanta and a few other apps not available yet for kde4....
I have looked into this further and if the error from is startkde is correct then the version you have is not from kdebase4-workspace-4.3.61svn998540.
I have: 16:30 wahoo:~ > rpm -q kdebase4-workspace kdebase4-workspace-4.3.61svn998540-3.1
I pulled spare/RPMS/kdebase4-workspace-4.3.61svn998540-3.1.x86_64.rpm /and looked at startkde. It has a reference to kdeinit4 and not /usr/lib/kde4/libexec/start_kdeinit_wrapper as you rightly noted. I /would change the following line in startkde from
LD_BIND_NOW=true /usr/lib/kde4/libexec/start_kdeinit_wrapper +kcminit_startup
to
LD_BIND_NOW=true kdeinit4 +kcminit_startup
the default in kdebase4-workspace-4.3.61svn998540-3.1 is: LD_BIND_NOW=true kdeinit4 +kcminit_startup
and works, see above "wrapper is *not* needed".
and see whether this works.
PS: http://download.opensuse.org/repositories/KDE:/KDE4:/UNSTABLE:/Desktop/openS... only had 4.3.61svn998540-3.1and not 4.3.61svn998540-3.4 as you have.
that was kdelibs4: kdelibs4-4.3.61svn998540-3.4
16:35 wahoo:~ > rpm -q kdelibs4 kdebase4-workspace kdelibs4-4.3.61svn998540-3.4 kdebase4-workspace-4.3.61svn998540-3.1
installed via: zypper dup
Present status *is* working w/o the soft link to start_kdeinit_wrapper (from kdelibs3-3.5.10-29.11)
-
Andreas Jaeger -
Dirk Müller -
Felix Miata -
Lubos Lunak -
ne... -
Patrick Shanahan