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:

...

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

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

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:

...

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

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

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:

...

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:

...

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

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

<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@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@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

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

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:

...

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

I tried removing kgtk-qt3-trinity first and, lo and behold, it solved the problem. Why would that be? Thanks - John

...

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?

I only want to remind that I almost exactly the same problem on Squeeze (couldn't start TDE because of gtk integration). The problem: http://trinity-users.pearsoncomputing.net/?0::3668 And the solution: http://trinity-users.pearsoncomputing.net/?0::3670

Janek

On Fri, 2012-10-12 at 15:06 +0200, Slávek Banko wrote:

Dne pá 12. října 2012 Timothy Pearson napsal(a):

...

...

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

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 Wednesday 31 of October 2012 21:56:18 Nick Leverton wrote:

In article 201210121506.56339.slavek.banko@axis.cz,

Slávek Banko trinity-users@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

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 --