Message: previous - next
Month: September 2012

Re: [trinity-users] Need some help with Trinity under Debian Squeeze

From: Lisi Reisz <lisi.reisz@...>
Date: Sat, 29 Sep 2012 12:21:09 +0100
Hi, Janek,

On 29 September 2012 10:31, Janek S. <fremenzone@...> wrote:
> Hi guys,
> following yesterdays discussion I installed Debian Squeeze with Trinity. I encountered some
> problems I am unable to resolve.
> 1. At first Trinity worked OK. I installed some additional packages I will be needing. Then I
> realized that I didn't format my /home partition used previousle by KDE4. Since I wanted a clean
> install I logged out and removed all files in ~. Now I can't log into Trinity - when I try to do
> that all I get is a blue background and I have to power off my laptop (can't even reset X with
> Ctrl+Alt+Backspace). In ~/.xsession-errors I see something like this:
> [startkde] kdeinit started successfully.
> [trinity kinit] Warrning: connect() failed: Connection refused
> kdeinit: Pipe closed unexpectedly: No such file or directoy
> kdeinit: Launched DCOPServier, pid = 2778 result = 1
> kdeinit: DCOPServer could not be started, aborting.
> QSettings::synx: failed to open '/etc/qt3/qt_plugins_3.3rc.tmp' for writing
> KCrash: crashing.. crashRecursionCounter = 2
> KCrash: Application Name = ksmserver path = <unknown> pid = 2774
> [trinity kinit] Warrning: connect() failed: Połączenie odrzucone
> KCrash cannot reach kdeinit, launching directly.
> ERROR: Couldn't attach to DCOP server!
> [startkde] Shutting down Trinity...
> [trinity kinit] Warrning: connect() failed: Connection refused
> [trinity kinit] Error: Can't contact kdeinit!
> [startkde] Running Trinity shutdown scripts...
> [startkde] Trinity shutdown complete
> I don't think this is caused by cleaning up home directory, I suspect some packages to be causing
> this.

I would have said that it probably _is_ caused by your deletion of
your home directory files.  I had very similar problems yesterday
after making alterations to my home. After every error message, I
tried to put right whatever it was complaining about, but things just
got worse.  I could login to LXDE, but not to Trinity.  So it
obviously _was_ at the level of Trinity, not the system.

Finally I solved Trinity's refusal even to open by creating another
user and starting afresh.  I now have a functioning TDE again, but
have not yet transferred my emails and folders, which is what I was
trying to do when the problem arose.

> 2. Assuming I will be able to run TDE again, I am unable to get NetworkManager to work. I use
> nm-applet. I can add the wireless connection, but I am unable to store password (the field is
> always empty, despite me saving the password). Moreover, nm-applet doesn't list any wirelesss
> networks and when I choose to connect to hidden network and select my connection the "Connect"
> button is grayed out.

I have managed this on my netbook, which is Squeeze + Trinity, by
installing Wicd, which I prefer anyway.