11 Oct
2012
11 Oct
'12
6:30 p.m.
Hello, all. I upgraded on of our Debian Squeeze systems today from TDE
3.5.12 to 3.5.13.1 however I receive a could not start kdeinit error
message. I did search for the error and see a thread which says to
check the libqt3-mt library version but I believe I have the correct
one:
ii libqt3-mt 3:3.3.8d-1ubuntu0+ax1~squeeze
There were no errors I saw on the apt-get install the second time. I
did have a problem the first time. I ran apt-get dist-upgrade from
within TDE. Suddenly, my Windows Manager vanished. I let the upgrade
proceed but then it asked for input and I was unable to provide the
input so I exited the GUI and killed the apt-get process. A dpkg
--configure a seemed to complete the installation correctly.
What do I do next? Thanks - John
11 Oct
11 Oct
6:35 p.m.
New subject: [trinity-users] Could not start kdeinit error
On Thursday 11 of October 2012 20:30:35 John A. Sullivan III wrote:
Hello, all. I upgraded on of our Debian Squeeze
systems today from TDE
3.5.12 to 3.5.13.1 however I receive a could not start kdeinit error
message. I did search for the error and see a thread which says to
check the libqt3-mt library version but I believe I have the correct
one:
ii libqt3-mt 3:3.3.8d-1ubuntu0+ax1~squeeze
There were no errors I saw on the apt-get install the second time. I
did have a problem the first time. I ran apt-get dist-upgrade from
within TDE. Suddenly, my Windows Manager vanished. I let the upgrade
proceed but then it asked for input and I was unable to provide the
input so I exited the GUI and killed the apt-get process. A dpkg
--configure a seemed to complete the installation correctly.
Yes, qt version is correct. Try:
dpkg --configure -a
aptitude dist-upgrade
Slavek
--
7:52 p.m.
New subject: [trinity-users] Could not start kdeinit error
On Thu, 2012-10-11 at 20:35 +0200, Slávek Banko wrote:
On Thursday 11 of October 2012 20:30:35 John A.
Sullivan III wrote:
Thank you both, Slavek and Tim. I had tried re-running apt-get update
and then apt-get dist-upgrade but that did not help. I just followed
Slavek's advice and was surprised to see that packages were removed
rather than upgraded:
root@denise:~# dpkg --configure -a
root@denise:~# aptitude dist-upgrade
The following packages will be REMOVED:
gs{u} kdesdk-scripts-trinity{u} kpilot-trinity{u} libavahi-compat-libdnssd1{u}
libavahi-qt3-dev{u} libdbus-qt-1-1c2{u} libkjsembed1-trinity{u} libogg-dev-la{u}
libpisock9{u} libpoppler-qt2{u} libsensors3{u} libxxf86misc1{u}
However, it has not fixed the problem. The TDE splash screen appears
stuck on starting system services and, behind it, is an error message
about could not start kdeinit :( What next? Thanks - John
Hello, all. I upgraded on of our Debian Squeeze
systems today from TDE
3.5.12 to 3.5.13.1 however I receive a could not start kdeinit error
message. I did search for the error and see a thread which says to
check the libqt3-mt library version but I believe I have the correct
one:
ii libqt3-mt 3:3.3.8d-1ubuntu0+ax1~squeeze
There were no errors I saw on the apt-get install the second time. I
did have a problem the first time. I ran apt-get dist-upgrade from
within TDE. Suddenly, my Windows Manager vanished. I let the upgrade
proceed but then it asked for input and I was unable to provide the
input so I exited the GUI and killed the apt-get process. A dpkg
--configure a seemed to complete the installation correctly.
Yes, qt version is correct. Try:
dpkg --configure -a
aptitude dist-upgrade
Slavek
8:01 p.m.
New subject: [trinity-users] Could not start kdeinit error
On Thursday 11 of October 2012 21:52:48 John A. Sullivan III wrote:
Thank you both, Slavek and Tim. I had tried
re-running apt-get update
and then apt-get dist-upgrade but that did not help. I just followed
Slavek's advice and was surprised to see that packages were removed
rather than upgraded:
root@denise:~# dpkg --configure -a
root@denise:~# aptitude dist-upgrade
The following packages will be REMOVED:
gs{u} kdesdk-scripts-trinity{u} kpilot-trinity{u}
libavahi-compat-libdnssd1{u} libavahi-qt3-dev{u} libdbus-qt-1-1c2{u}
libkjsembed1-trinity{u} libogg-dev-la{u} libpisock9{u} libpoppler-qt2{u}
libsensors3{u} libxxf86misc1{u}
However, it has not fixed the problem. The TDE splash screen appears
stuck on starting system services and, behind it, is an error message
about could not start kdeinit :( What next? Thanks - John
Try to remove from /tmp folders kde-_your_login_ and ksocket-_your_login_.
Slavek
--
8:28 p.m.
New subject: [trinity-users] Could not start kdeinit error
On Thu, 2012-10-11 at 22:01 +0200, Slávek Banko wrote:
On Thursday 11 of October 2012 21:52:48 John A.
Sullivan III wrote:
Alas, that did not work. I should mention that I had previously
rebooted the system (the advantage of it being test). I removed
the /tmp files/directories pertinent to my ID; that did not work. I
deleted all files in /tmp; that did not work. I deleted all files
in /tmp and rebooted again. That did not work :( Next step?
Would it make sense to uninstall and reinstall TDE? What would be the
best way to do that without deleting my configuration? apt-get remove
kdebase-trinity? Thanks - John
Thank you both, Slavek and Tim. I had tried
re-running apt-get update
and then apt-get dist-upgrade but that did not help. I just followed
Slavek's advice and was surprised to see that packages were removed
rather than upgraded:
root@denise:~# dpkg --configure -a
root@denise:~# aptitude dist-upgrade
The following packages will be REMOVED:
gs{u} kdesdk-scripts-trinity{u} kpilot-trinity{u}
libavahi-compat-libdnssd1{u} libavahi-qt3-dev{u} libdbus-qt-1-1c2{u}
libkjsembed1-trinity{u} libogg-dev-la{u} libpisock9{u} libpoppler-qt2{u}
libsensors3{u} libxxf86misc1{u}
However, it has not fixed the problem. The TDE splash screen appears
stuck on starting system services and, behind it, is an error message
about could not start kdeinit :( What next? Thanks - John
Try to remove from /tmp folders kde-_your_login_ and ksocket-_your_login_.
Slavek
9:21 p.m.
New subject: [trinity-users] Could not start kdeinit error
On Thu, 2012-10-11 at 16:28 -0400, John A. Sullivan III wrote:
On Thu, 2012-10-11 at 22:01 +0200, Slávek Banko wrote:
<snip>
Argh!! Uninstalling and reinstalling did not help. Now I am a bit stuck
- although it is test, it is also a development system and we need to
get back on it! What shall I try next?
I did pick up this error in user.log regarding pulseaudio:
Unable to contact D-Bus:
org.freedesktop.DBus.Error.Spawn.ExecFailed: /usr/bin/dbus-launch
terminated abnormally with the following error: Autolaunch error: X11
initialization failed.
Is there a log file where I can see more details about why kdeinit is
failing? Thanks - John
On Thursday 11 of October 2012 21:52:48 John A.
Sullivan III wrote:
Alas, that did not work. I should mention that I had previously
rebooted the system (the advantage of it being test). I removed
the /tmp files/directories pertinent to my ID; that did not work. I
deleted all files in /tmp; that did not work. I deleted all files
in /tmp and rebooted again. That did not work :( Next step?
Would it make sense to uninstall and reinstall TDE? What would be the
best way to do that without deleting my configuration? apt-get remove
kdebase-trinity? Thanks - John Thank you both, Slavek and Tim. I had tried
re-running apt-get update
and then apt-get dist-upgrade but that did not help. I just followed
Slavek's advice and was surprised to see that packages were removed
rather than upgraded:
root@denise:~# dpkg --configure -a
root@denise:~# aptitude dist-upgrade
The following packages will be REMOVED:
gs{u} kdesdk-scripts-trinity{u} kpilot-trinity{u}
libavahi-compat-libdnssd1{u} libavahi-qt3-dev{u} libdbus-qt-1-1c2{u}
libkjsembed1-trinity{u} libogg-dev-la{u} libpisock9{u} libpoppler-qt2{u}
libsensors3{u} libxxf86misc1{u}
However, it has not fixed the problem. The TDE splash screen appears
stuck on starting system services and, behind it, is an error message
about could not start kdeinit :( What next? Thanks - John
Try to remove from /tmp folders kde-_your_login_ and ksocket-_your_login_.
Slavek 
9:28 p.m.
New subject: [trinity-users] Could not start kdeinit error
I'd suggest, you uninstall anything regarding to pulseaudio.
Am Donnerstag, 11. Oktober 2012 schrieb John A. Sullivan III:
On Thu, 2012-10-11 at 16:28 -0400, John A. Sullivan
III wrote:
--
Mag. Dr. Nikolaus Klepp
Einnehmerstraße 14
A-4810 Gmunden
Tel.: +43 650 82 11 724
email: office(a)klepp.biz
On Thu, 2012-10-11 at 22:01 +0200, Slávek Banko
wrote:
<snip>
Argh!! Uninstalling and reinstalling did not help. Now I am a bit stuck
- although it is test, it is also a development system and we need to
get back on it! What shall I try next?
I did pick up this error in user.log regarding pulseaudio:
Unable to contact D-Bus:
org.freedesktop.DBus.Error.Spawn.ExecFailed: /usr/bin/dbus-launch
terminated abnormally with the following error: Autolaunch error: X11
initialization failed.
Is there a log file where I can see more details about why kdeinit is
failing? Thanks - John
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-users-unsubscribe(a)lists.pearsoncomputing.net For additional
commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net Read list
messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting On Thursday 11 of October 2012 21:52:48 John A.
Sullivan III wrote:
Alas, that did not work. I should mention that I had previously
rebooted the system (the advantage of it being test). I removed
the /tmp files/directories pertinent to my ID; that did not work. I
deleted all files in /tmp; that did not work. I deleted all files
in /tmp and rebooted again. That did not work :( Next step?
Would it make sense to uninstall and reinstall TDE? What would be the
best way to do that without deleting my configuration? apt-get remove
kdebase-trinity? Thanks - John Thank you both, Slavek and Tim. I had tried
re-running apt-get
update and then apt-get dist-upgrade but that did not help. I just
followed Slavek's advice and was surprised to see that packages were
removed rather than upgraded:
root@denise:~# dpkg --configure -a
root@denise:~# aptitude dist-upgrade
The following packages will be REMOVED:
gs{u} kdesdk-scripts-trinity{u} kpilot-trinity{u}
libavahi-compat-libdnssd1{u} libavahi-qt3-dev{u} libdbus-qt-1-1c2{u}
libkjsembed1-trinity{u} libogg-dev-la{u} libpisock9{u}
libpoppler-qt2{u} libsensors3{u} libxxf86misc1{u}
However, it has not fixed the problem. The TDE splash screen appears
stuck on starting system services and, behind it, is an error message
about could not start kdeinit :( What next? Thanks - John
Try to remove from /tmp folders kde-_your_login_ and
ksocket-_your_login_.
Slavek
9:33 p.m.
New subject: [trinity-users] Could not start kdeinit error
On Thu, 2012-10-11 at 23:28 +0200, Mag. Dr. Nikolaus Klepp wrote:
I'd suggest, you uninstall anything regarding to
pulseaudio.
<snip>
That's not an option. We've learned to live with it and it is required
for the network sound we use - John
9:42 p.m.
New subject: [trinity-users] Could not start kdeinit error
John A. Sullivan III wrote:
Is there a log file where I can see more details about
why kdeinit is
failing? Thanks - John
You can look at your .xsession-errors file or launch a failsafe session
from your display manager and use the startkde/starttde script to launch
the desktop and look at the errors that appear.
Julius
11:21 p.m.
New subject: [trinity-users] Could not start kdeinit error
On Thursday 11 of October 2012 23:21:14 John A. Sullivan III wrote:
Argh!! Uninstalling and reinstalling did not help.
Now I am a bit stuck
- although it is test, it is also a development system and we need to
get back on it! What shall I try next?
I did pick up this error in user.log regarding pulseaudio:
Unable to contact D-Bus:
org.freedesktop.DBus.Error.Spawn.ExecFailed: /usr/bin/dbus-launch
terminated abnormally with the following error: Autolaunch error: X11
initialization failed.
Is there a log file where I can see more details about why kdeinit is
failing? Thanks - John
I now have only three ideas:
1. Send your .xsession-errors if there's anything we can find.
2. Try to rename your .trinity, if the problem persists with a new profile.
3. You have installed kgtk-qt3-trinity? Try to uninstall it.
Slavek
--
12 Oct
12 Oct
3:03 a.m.
New subject: [trinity-users] Could not start kdeinit error
On Fri, 2012-10-12 at 01:21 +0200, Slávek Banko wrote:
On Thursday 11 of October 2012 23:21:14 John A.
Sullivan III wrote:
I tried removing kgtk-qt3-trinity first and, lo and behold, it solved
the problem. Why would that be? Thanks - John
Argh!! Uninstalling and reinstalling did not
help. Now I am a bit stuck
- although it is test, it is also a development system and we need to
get back on it! What shall I try next?
I did pick up this error in user.log regarding pulseaudio:
Unable to contact D-Bus:
org.freedesktop.DBus.Error.Spawn.ExecFailed: /usr/bin/dbus-launch
terminated abnormally with the following error: Autolaunch error: X11
initialization failed.
Is there a log file where I can see more details about why kdeinit is
failing? Thanks - John
I now have only three ideas:
1. Send your .xsession-errors if there's anything we can find.
2. Try to rename your .trinity, if the problem persists with a new profile.
3. You have installed kgtk-qt3-trinity? Try to uninstall it.
Slavek 
3:12 a.m.
New subject: [trinity-users] Could not start kdeinit error
On Fri, 2012-10-12 at 01:21 +0200, Slávek Banko
wrote:
This is very odd. Slavek, do we need to blacklist that package on
Debian/Ubuntu at this point?
Thanks!
Tim
On Thursday 11 of October 2012 23:21:14 John A.
Sullivan III wrote:
I tried removing kgtk-qt3-trinity first and, lo and behold, it solved
the problem. Why would that be? Thanks - John Argh!! Uninstalling and reinstalling did not
help. Now I am a bit
stuck
- although it is test, it is also a development
system and we need to
get back on it! What shall I try next?
I did pick up this error in user.log regarding pulseaudio:
Unable to contact D-Bus:
org.freedesktop.DBus.Error.Spawn.ExecFailed: /usr/bin/dbus-launch
terminated abnormally with the following error: Autolaunch error: X11
initialization failed.
Is there a log file where I can see more details about why kdeinit is
failing? Thanks - John
I now have only three ideas:
1. Send your .xsession-errors if there's anything we can find.
2. Try to rename your .trinity, if the problem persists with a new
profile.
3. You have installed kgtk-qt3-trinity? Try to uninstall it.
Slavek 
6:53 a.m.
New subject: [trinity-users] Could not start kdeinit error
I tried
removing kgtk-qt3-trinity first and, lo and behold, it solved
the problem. Why would that be? Thanks - John
This is very odd. Slavek, do we need to blacklist that package on
Debian/Ubuntu at this point?
1:06 p.m.
New subject: [trinity-users] Could not start kdeinit error
Dne pá 12. října 2012 Timothy Pearson napsal(a):
With kgtk-qt3 it is strange. With original 3.5.13 for me it was causes
crashes => not possible to login at all. After selecting patches for
3.5.13.1 (including a change from autotools to cmake), kgtk-qt3 for me
suddenly began work.
As seen, we can not clearly say that it would not work. For someone is
working, for someone not. In any case, for some may be a source of
unpleasant problems.
Indeed - I also uninstalled it because it is not compatible with Inkscape
and DVDStyler. And I do not know that it would be easy for users to add
to the list of programs for which no behavior may to be modified.
Slavek
--
On Fri,
2012-10-12 at 01:21 +0200, Slávek Banko wrote:
This is very odd. Slavek, do we need to blacklist that package on
Debian/Ubuntu at this point?
Thanks!
Tim
On Thursday 11 of October 2012 23:21:14 John A.
Sullivan III wrote:
I tried removing kgtk-qt3-trinity first and, lo and behold, it solved
the problem. Why would that be? Thanks - John Argh!! Uninstalling and reinstalling did not
help. Now I am a bit
stuck
- although it is test, it is also a development
system and we need
to get back on it! What shall I try next?
I did pick up this error in user.log regarding pulseaudio:
Unable to contact D-Bus:
org.freedesktop.DBus.Error.Spawn.ExecFailed: /usr/bin/dbus-launch
terminated abnormally with the following error: Autolaunch error:
X11 initialization failed.
Is there a log file where I can see more details about why kdeinit
is failing? Thanks - John
I now have only three ideas:
1. Send your .xsession-errors if there's anything we can find.
2. Try to rename your .trinity, if the problem persists with a new
profile.
3. You have installed kgtk-qt3-trinity? Try to uninstall it.
Slavek
1:31 p.m.
New subject: [trinity-users] Could not start kdeinit error
On Fri, 2012-10-12 at 15:06 +0200, Slávek Banko wrote:
Dne pá 12. října 2012 Timothy Pearson napsal(a):
With kgtk-qt3 it is strange. With original 3.5.13 for me it was causes
crashes => not possible to login at all. After selecting patches for
3.5.13.1 (including a change from autotools to cmake), kgtk-qt3 for me
suddenly began work.
As seen, we can not clearly say that it would not work. For someone is
working, for someone not. In any case, for some may be a source of
unpleasant problems.
Indeed - I also uninstalled it because it is not compatible with Inkscape
and DVDStyler. And I do not know that it would be easy for users to add
to the list of programs for which no behavior may to be modified.
Slavek
Alas, it's a shame to not be able to use it. We find that having more
than one dialog style, especially such drastically different dialog
styles, is confusing to our clients. Thanks - John
> On Fri, 2012-10-12 at 01:21 +0200, Slávek
Banko wrote:
<snip>> >
I tried
removing kgtk-qt3-trinity first and, lo and behold, it solved
the problem. Why would that be? Thanks - John
This is very odd. Slavek, do we need to blacklist that package on
Debian/Ubuntu at this point?
Thanks!
Tim
31 Oct
31 Oct
8:56 p.m.
In article <201210121506.56339.slavek.banko(a)axis.cz>cz>,
Slávek Banko <trinity-users(a)lists.pearsoncomputing.net> wrote:
With kgtk-qt3 it is strange. With original 3.5.13 for me it was causes
crashes => not possible to login at all. After selecting patches for
3.5.13.1 (including a change from autotools to cmake), kgtk-qt3 for me
suddenly began work.
As seen, we can not clearly say that it would not work. For someone is
working, for someone not. In any case, for some may be a source of
unpleasant problems.
I am one of those for whom it works but I have a no doubt unusual
(hand-picked by years of trial and error :-)) combination of old and
new packages. If it were removed or replaced by a dummy package, until
the problem is found, I can't see any real objection given that it's
only for theme niceness.
Nick
--
"The Internet, a sort of ersatz counterfeit of real life"
-- Janet Street-Porter, BBC2, 19th March 1996
9:02 p.m.
New subject: [trinity-users] Re: Could not start kdeinit error
On Wednesday 31 of October 2012 21:56:18 Nick Leverton wrote:
In article
<201210121506.56339.slavek.banko(a)axis.cz>cz>,
Slávek Banko <trinity-users(a)lists.pearsoncomputing.net> wrote:
Probably appropriate will be kgtk-qt3-trinity state not as a 'dependency', but
as 'suggested'. To allow users in case of problems easily remove the package.
Slavek
--
With kgtk-qt3 it is strange. With original 3.5.13
for me it was causes
crashes => not possible to login at all. After selecting patches for
3.5.13.1 (including a change from autotools to cmake), kgtk-qt3 for me
suddenly began work.
As seen, we can not clearly say that it would not work. For someone is
working, for someone not. In any case, for some may be a source of
unpleasant problems.
I am one of those for whom it works but I have a no doubt unusual
(hand-picked by years of trial and error :-)) combination of old and
new packages. If it were removed or replaced by a dummy package, until
the problem is found, I can't see any real objection given that it's
only for theme niceness.
Nick
11 Oct
11 Oct
7:53 p.m.
New subject: [trinity-users] Could not start kdeinit error
Am Donnerstag, 11. Oktober 2012 schrieb Slávek Banko:
On Thursday 11 of October 2012 20:30:35 John A.
Sullivan III wrote:
Maybe you could put a note on the webpage to tell users nit to upgrade from
inside X11?
Nik
Hello, all. I upgraded on of our Debian Squeeze
systems today from TDE
3.5.12 to 3.5.13.1 however I receive a could not start kdeinit error
message. I did search for the error and see a thread which says to
check the libqt3-mt library version but I believe I have the correct
one:
ii libqt3-mt 3:3.3.8d-1ubuntu0+ax1~squeeze
There were no errors I saw on the apt-get install the second time. I
did have a problem the first time. I ran apt-get dist-upgrade from
within TDE. Suddenly, my Windows Manager vanished. I let the upgrade
proceed but then it asked for input and I was unable to provide the
input so I exited the GUI and killed the apt-get process. A dpkg
--configure a seemed to complete the installation correctly.
Yes, qt version is correct. Try:
dpkg --configure -a
aptitude dist-upgrade
Slavek
6:44 p.m.
New subject: [trinity-users] Could not start kdeinit error
Hello, all. I upgraded on of our Debian Squeeze
systems today from TDE
3.5.12 to 3.5.13.1 however I receive a could not start kdeinit error
message. I did search for the error and see a thread which says to
check the libqt3-mt library version but I believe I have the correct
one:
ii libqt3-mt 3:3.3.8d-1ubuntu0+ax1~squeeze
There were no errors I saw on the apt-get install the second time. I
did have a problem the first time. I ran apt-get dist-upgrade from
within TDE. Suddenly, my Windows Manager vanished. I let the upgrade
proceed but then it asked for input and I was unable to provide the
input so I exited the GUI and killed the apt-get process. A dpkg
--configure a seemed to complete the installation correctly.
What do I do next? Thanks - John
As the upgrade was interrupted you may want to see if you have more TDE
packages left to upgrade with 'apt-get dist-upgrade' or similar.
Tim
4434
days inactive
4454
days old
18 comments
7 participants
participants (7)
-
Janek S. -
John A. Sullivan III -
Julius Schwartzenberg -
Mag. Dr. Nikolaus Klepp -
Nick Leverton -
Slávek Banko -
Timothy Pearson