Hello to all.
I'm a long-time TDE user running TDE 14.0.4 amd64 on Debian 9.x Stretch (unstable, actually Siduction, using systemd). It works well, although I occasionally run into minor issues that I eventually solve. It is after all "unstable".
Over the last few weeks a problem remains, binutils_2.27-9_amd64.deb works fine, but several updates of this program which can be loaded by itself, most recently binutils_2.27.90.201612331-1_amd64.deb, all render the system unbootable.
The boot cycle proceeds from sda1 without any errors but the tdm signon comes up with a black background rather the normal blue TDE one. When I logon I get an error message and TDE does not load, showing a problem with my home partition on sda5:
Could not read connection list /home/lsm1/.DCOPserver_LSM1_0 Please check that the "dcopserver" program is running
When I hit Enter I then get:
Could not start tdeinit, Check your installation.
This problem is specific to TDE as I can still load the backup desktop LXQT by the usual logon from the TDE signon box.
When I boot to the console and downgrade to binutils_2.27-9_amd64.deb everything works as usual on the reboot.
If anyone has any possible solutions I'd be happy to try them out and report back.
I thought TDE was up to 14.05 for Stretch and Sid. The binutils update marks TDE for removal, it is why I have not updated binutils on any of my TDE systems (one of which also runs many of DEs). Until Tim, Slavek, or Michele get to fixing it I would not recommend updating or attempting to bypass dpkg's warning.
On 1 January 2017 at 07:50, L.S. McCarty lsmccarty@rogers.com wrote:
Hello to all.
I'm a long-time TDE user running TDE 14.0.4 amd64 on Debian 9.x Stretch (unstable, actually Siduction, using systemd). It works well, although I occasionally run into minor issues that I eventually solve. It is after all "unstable".
Over the last few weeks a problem remains, binutils_2.27-9_amd64.deb works fine, but several updates of this program which can be loaded by itself, most recently binutils_2.27.90.201612331-1_amd64.deb, all render the system unbootable.
The boot cycle proceeds from sda1 without any errors but the tdm signon comes up with a black background rather the normal blue TDE one. When I logon I get an error message and TDE does not load, showing a problem with my home partition on sda5:
Could not read connection list /home/lsm1/.DCOPserver_LSM1_0 Please check that the "dcopserver" program is running
When I hit Enter I then get:
Could not start tdeinit, Check your installation.
This problem is specific to TDE as I can still load the backup desktop LXQT by the usual logon from the TDE signon box.
When I boot to the console and downgrade to binutils_2.27-9_amd64.deb everything works as usual on the reboot.
If anyone has any possible solutions I'd be happy to try them out and report back.
-- SENT BY: Lynn McCarty
To unsubscribe, e-mail: trinity-users-unsubscribe@list s.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pears oncomputing.net Read list messages on the web archive: http://trinity-users.pearsonco mputing.net/ Please remember not to top-post: http://trinity.pearsoncomputin g.net/mailing_lists/#top-posting
On Saturday 31 of December 2016 21:50:44 L.S. McCarty wrote:
Hello to all.
I'm a long-time TDE user running TDE 14.0.4 amd64 on Debian 9.x Stretch (unstable, actually Siduction, using systemd). It works well, although I occasionally run into minor issues that I eventually solve. It is after all "unstable".
Over the last few weeks a problem remains, binutils_2.27-9_amd64.deb works fine, but several updates of this program which can be loaded by itself, most recently binutils_2.27.90.201612331-1_amd64.deb, all render the system unbootable.
The boot cycle proceeds from sda1 without any errors but the tdm signon comes up with a black background rather the normal blue TDE one. When I logon I get an error message and TDE does not load, showing a problem with my home partition on sda5:
Could not read connection list /home/lsm1/.DCOPserver_LSM1_0 Please check that the "dcopserver" program is running
When I hit Enter I then get:
Could not start tdeinit, Check your installation.
This problem is specific to TDE as I can still load the backup desktop LXQT by the usual logon from the TDE signon box.
When I boot to the console and downgrade to binutils_2.27-9_amd64.deb everything works as usual on the reboot.
If anyone has any possible solutions I'd be happy to try them out and report back.
If you want to use TDE on Stretch or Sid it is a good choice to use Preliminary Stable Builds repository:
https://wiki.trinitydesktop.org/Preliminary_Stable_Builds
For Stretch (binutils 2.27.90.20161220) and Sid (binutils 2.27.90.20161231) is updated today.
Cheers
Slavek I'm using Stretch with your PSB repo and keep it up to date each day (today's update was 104 packages from Debian) and binutils will not update without removing many (currently 44) TDE packages. Packages listed here for your perusal. If you have no other DEs updating binutils breaks TDE in Stretch and makes it unusable. kamera-trinity will be removed kappfinder-trinity will be removed kate-trinity will be removed kcontrol-trinity will be removed kcron-trinity will be removed kdat-trinity will be removed kdesktop-trinity will be removed kdpkg-trinity will be removed kfind-trinity will be removed khelpcenter-trinity will be removed kicker-trinity will be removed klipper-trinity will be removed kmenuedit-trinity will be removed knetworkconf-trinity will be removed konqueror-nsplugins-trinity will be removed konqueror-trinity will be removed konsole-trinity will be removed kpackage-trinity will be removed kpager-trinity will be removed kpersonalizer-trinity will be removed kregexpeditor-trinity will be removed ksmserver-trinity will be removed ksplash-trinity will be removed ksysguard-trinity will be removed ksysv-trinity will be removed ktip-trinity will be removed kuser-trinity will be removed libkcddb1-trinity will be removed libkonq4-trinity will be removed libr0 will be removed libtqt3-integration-trinity will be removed tde-core-trinity will be removed tdeadmin-tdefile-plugins-trinity will be removed tdeadmin-trinity will be removed tdebase-tdeio-plugins-trinity will be removed tdebase-trinity will be removed tdebase-trinity-bin will be removed tdeiconedit-trinity will be removed tdelibs-trinity will be removed tdelibs14-trinity will be removed tdemultimedia-tdeio-plugins-trinity will be removed tdepasswd-trinity will be removed tdeprint-trinity will be removed twin-trinity will be removed
On 1 January 2017 at 09:49, Slávek Banko slavek.banko@axis.cz wrote:
On Saturday 31 of December 2016 21:50:44 L.S. McCarty wrote:
Hello to all.
I'm a long-time TDE user running TDE 14.0.4 amd64 on Debian 9.x Stretch (unstable, actually Siduction, using systemd). It works well, although I occasionally run into minor issues that I eventually solve. It is after all "unstable".
Over the last few weeks a problem remains, binutils_2.27-9_amd64.deb works fine, but several updates of this program which can be loaded by itself, most recently binutils_2.27.90.201612331-1_amd64.deb, all render the system unbootable.
The boot cycle proceeds from sda1 without any errors but the tdm signon comes up with a black background rather the normal blue TDE one. When I logon I get an error message and TDE does not load, showing a problem with my home partition on sda5:
Could not read connection list /home/lsm1/.DCOPserver_LSM1_0 Please check that the "dcopserver" program is running
When I hit Enter I then get:
Could not start tdeinit, Check your installation.
This problem is specific to TDE as I can still load the backup desktop LXQT by the usual logon from the TDE signon box.
When I boot to the console and downgrade to binutils_2.27-9_amd64.deb everything works as usual on the reboot.
If anyone has any possible solutions I'd be happy to try them out and report back.
If you want to use TDE on Stretch or Sid it is a good choice to use Preliminary Stable Builds repository:
https://wiki.trinitydesktop.org/Preliminary_Stable_Builds
For Stretch (binutils 2.27.90.20161220) and Sid (binutils 2.27.90.20161231) is updated today.
Cheers
Slávek
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
You're on Stretch or Sid?
For Stretch is in Debian repository binutils = 2.27.51.20161220 and in PSB repository libr0 = 4:0.6.0-3debian9.0.0+4~b6.
For Sid is in Debian repository binutils = 2.27.90.20161231 and in PSB repository libr0 = 4:0.6.0-3debian9.0.0+4~b7.
Please, verify that you install the same versions, as listed above.
As already mentioned I'm using Stretch.
The version of binutils I have is 2.27.51.20161108-1. Updating to 2.27.51.2016220-1 removes the packages listed above. libr0 version is current 4:0.6.0-3debian9.0.0+4~b1.
On 1 January 2017 at 11:44, Slávek Banko slavek.banko@axis.cz wrote:
You're on Stretch or Sid?
For Stretch is in Debian repository binutils = 2.27.51.20161220 and in PSB repository libr0 = 4:0.6.0-3debian9.0.0+4~b6.
For Sid is in Debian repository binutils = 2.27.90.20161231 and in PSB repository libr0 = 4:0.6.0-3debian9.0.0+4~b7.
Please, verify that you install the same versions, as listed above.
-- Slávek
On Sunday 01 of January 2017 01:26:18 Michael . wrote:
Slavek I'm using Stretch with your PSB repo and keep it up to date each day (today's update was 104 packages from Debian) and binutils will not update without removing many (currently 44) TDE packages. Packages listed here for your perusal. If you have no other DEs updating binutils breaks TDE in Stretch and makes it unusable. kamera-trinity will be removed kappfinder-trinity will be removed kate-trinity will be removed kcontrol-trinity will be removed kcron-trinity will be removed kdat-trinity will be removed kdesktop-trinity will be removed kdpkg-trinity will be removed kfind-trinity will be removed khelpcenter-trinity will be removed kicker-trinity will be removed klipper-trinity will be removed kmenuedit-trinity will be removed knetworkconf-trinity will be removed konqueror-nsplugins-trinity will be removed konqueror-trinity will be removed konsole-trinity will be removed kpackage-trinity will be removed kpager-trinity will be removed kpersonalizer-trinity will be removed kregexpeditor-trinity will be removed ksmserver-trinity will be removed ksplash-trinity will be removed ksysguard-trinity will be removed ksysv-trinity will be removed ktip-trinity will be removed kuser-trinity will be removed libkcddb1-trinity will be removed libkonq4-trinity will be removed libr0 will be removed libtqt3-integration-trinity will be removed tde-core-trinity will be removed tdeadmin-tdefile-plugins-trinity will be removed tdeadmin-trinity will be removed tdebase-tdeio-plugins-trinity will be removed tdebase-trinity will be removed tdebase-trinity-bin will be removed tdeiconedit-trinity will be removed tdelibs-trinity will be removed tdelibs14-trinity will be removed tdemultimedia-tdeio-plugins-trinity will be removed tdepasswd-trinity will be removed tdeprint-trinity will be removed twin-trinity will be removed
On 1 January 2017 at 09:49, Slávek Banko slavek.banko@axis.cz wrote:
On Saturday 31 of December 2016 21:50:44 L.S. McCarty wrote:
Hello to all.
I'm a long-time TDE user running TDE 14.0.4 amd64 on Debian 9.x Stretch (unstable, actually Siduction, using systemd). It works well, although I occasionally run into minor issues that I eventually solve. It is after all "unstable".
Over the last few weeks a problem remains, binutils_2.27-9_amd64.deb works fine, but several updates of this program which can be loaded by itself, most recently binutils_2.27.90.201612331-1_amd64.deb, all render the system unbootable.
The boot cycle proceeds from sda1 without any errors but the tdm signon comes up with a black background rather the normal blue TDE one. When I logon I get an error message and TDE does not load, showing a problem with my home partition on sda5:
Could not read connection list /home/lsm1/.DCOPserver_LSM1_0 Please check that the "dcopserver" program is running
When I hit Enter I then get:
Could not start tdeinit, Check your installation.
This problem is specific to TDE as I can still load the backup desktop LXQT by the usual logon from the TDE signon box.
When I boot to the console and downgrade to binutils_2.27-9_amd64.deb everything works as usual on the reboot.
If anyone has any possible solutions I'd be happy to try them out and report back.
If you want to use TDE on Stretch or Sid it is a good choice to use Preliminary Stable Builds repository:
https://wiki.trinitydesktop.org/Preliminary_Stable_Builds
For Stretch (binutils 2.27.90.20161220) and Sid (binutils 2.27.90.20161231) is updated today.
Cheers
Slávek
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
Do you have properly updated lists of PSB repository? As I wrote below, for Stretch is now in PSB repository version libr0 = 4:0.6.0-3debian9.0.0+4~b6.
http://mirror.xcer.cz/trinity-sb/pool/deps-r14/libr/libr/
Cheers
I update my system each day, in theory the lists should all be current. Obviously they aren't though so I need to do some research to find out why. I'll let binutils update today and work out what is going on from there.
On 1 January 2017 at 21:00, Slávek Banko slavek.banko@axis.cz wrote:
Do you have properly updated lists of PSB repository? As I wrote below, for Stretch is now in PSB repository version libr0 = 4:0.6.0-3debian9.0.0+4~b6.
http://mirror.xcer.cz/trinity-sb/pool/deps-r14/libr/libr/
Cheers
Slávek
On Sunday 01 of January 2017 04:21:17 Michael . wrote:
As already mentioned I'm using Stretch.
The version of binutils I have is 2.27.51.20161108-1. Updating to 2.27.51.2016220-1 removes the packages listed above. libr0 version is current 4:0.6.0-3debian9.0.0+4~b1.
On 1 January 2017 at 11:44, Slávek Banko slavek.banko@axis.cz wrote:
You're on Stretch or Sid?
For Stretch is in Debian repository binutils = 2.27.51.20161220 and in PSB repository libr0 = 4:0.6.0-3debian9.0.0+4~b6.
For Sid is in Debian repository binutils = 2.27.90.20161231 and in PSB repository libr0 = 4:0.6.0-3debian9.0.0+4~b7.
Please, verify that you install the same versions, as listed above.
-- Slávek
On Sunday 01 of January 2017 01:26:18 Michael . wrote:
Slavek I'm using Stretch with your PSB repo and keep it up to date each day (today's update was 104 packages from Debian) and binutils will not update without removing many (currently 44) TDE packages. Packages listed here for your perusal. If you have no other DEs updating binutils breaks TDE in Stretch and makes it unusable. kamera-trinity will be removed kappfinder-trinity will be removed kate-trinity will be removed kcontrol-trinity will be removed kcron-trinity will be removed kdat-trinity will be removed kdesktop-trinity will be removed kdpkg-trinity will be removed kfind-trinity will be removed khelpcenter-trinity will be removed kicker-trinity will be removed klipper-trinity will be removed kmenuedit-trinity will be removed knetworkconf-trinity will be removed konqueror-nsplugins-trinity will be removed konqueror-trinity will be removed konsole-trinity will be removed kpackage-trinity will be removed kpager-trinity will be removed kpersonalizer-trinity will be removed kregexpeditor-trinity will be removed ksmserver-trinity will be removed ksplash-trinity will be removed ksysguard-trinity will be removed ksysv-trinity will be removed ktip-trinity will be removed kuser-trinity will be removed libkcddb1-trinity will be removed libkonq4-trinity will be removed libr0 will be removed libtqt3-integration-trinity will be removed tde-core-trinity will be removed tdeadmin-tdefile-plugins-trinity will be removed tdeadmin-trinity will be removed tdebase-tdeio-plugins-trinity will be removed tdebase-trinity will be removed tdebase-trinity-bin will be removed tdeiconedit-trinity will be removed tdelibs-trinity will be removed tdelibs14-trinity will be removed tdemultimedia-tdeio-plugins-trinity will be removed tdepasswd-trinity will be removed tdeprint-trinity will be removed twin-trinity will be removed
On 1 January 2017 at 09:49, Slávek Banko slavek.banko@axis.cz
wrote:
On Saturday 31 of December 2016 21:50:44 L.S. McCarty wrote:
Hello to all.
I'm a long-time TDE user running TDE 14.0.4 amd64 on Debian 9.x Stretch (unstable, actually Siduction, using systemd). It works well, although I occasionally run into minor issues that I eventually solve. It is after all "unstable".
Over the last few weeks a problem remains, binutils_2.27-9_amd64.deb works fine, but several updates of this program which can be loaded by itself, most recently binutils_2.27.90.201612331-1_amd64.deb, all render the system unbootable.
The boot cycle proceeds from sda1 without any errors but the tdm signon comes up with a black background rather the normal blue TDE one. When I logon I get an error message and TDE does not load, showing a problem with my home partition on sda5:
Could not read connection list /home/lsm1/.DCOPserver_LSM1_0 Please check that the "dcopserver" program is running
When I hit Enter I then get:
Could not start tdeinit, Check your installation.
This problem is specific to TDE as I can still load the backup desktop LXQT by the usual logon from the TDE signon box.
When I boot to the console and downgrade to binutils_2.27-9_amd64.deb everything works as usual on the reboot.
If anyone has any possible solutions I'd be happy to try them out and report back.
If you want to use TDE on Stretch or Sid it is a good choice to use Preliminary Stable Builds repository:
https://wiki.trinitydesktop.org/Preliminary_Stable_Builds
For Stretch (binutils 2.27.90.20161220) and Sid (binutils 2.27.90.20161231) is updated today.
Cheers
Slávek
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
On 2017/01/01 05:50 AM, L.S. McCarty wrote:
Hello to all.
I'm a long-time TDE user running TDE 14.0.4 amd64 on Debian 9.x Stretch (unstable, actually Siduction, using systemd). It works well, although I occasionally run into minor issues that I eventually solve. It is after all "unstable".
Over the last few weeks a problem remains, binutils_2.27-9_amd64.deb works fine, but several updates of this program which can be loaded by itself, most recently binutils_2.27.90.201612331-1_amd64.deb, all render the system unbootable.
The boot cycle proceeds from sda1 without any errors but the tdm signon comes up with a black background rather the normal blue TDE one. When I logon I get an error message and TDE does not load, showing a problem with my home partition on sda5:
Could not read connection list /home/lsm1/.DCOPserver_LSM1_0 Please check that the "dcopserver" program is running
When I hit Enter I then get:
Could not start tdeinit, Check your installation.
This problem is specific to TDE as I can still load the backup desktop LXQT by the usual logon from the TDE signon box.
When I boot to the console and downgrade to binutils_2.27-9_amd64.deb everything works as usual on the reboot.
If anyone has any possible solutions I'd be happy to try them out and report back.
Hi there, when binutils is updated, it is necessary to rebuild (or use a rebuilt version of) "dependencies/libr". Without doing so, trying to update binutils will raise a conflict with tdelibs which in turns brings up a long list of packages that needs to be "removed". After rebuilding and installing the new libr, binutils can be updated without problem.
for those using TDE on Sid/stretch you have two choices: 1) if you are building TDE yuorselves, just rebuild and install libr 2) if you are using preliminary stable builds from Slavek's repo, wait until libr is rebuilt and then update binutils at the same time.
After doing all that, I think you will not run into the issue mentioned by McCarty. If you do so, just rebuild and reinstall tdelibs as well from CLI. Just for info, from time to time I run into the same issue (last time was a few weeks ago) and rebuilding as described has always fixed the problem so far (I think libr is enough, but since I do not remember 100% I also recommended tdelibs is the problem persists).
Cheers Michele
On Sunday 01 of January 2017 06:13:30 Michele Calgaro wrote:
On 2017/01/01 05:50 AM, L.S. McCarty wrote:
Hello to all.
I'm a long-time TDE user running TDE 14.0.4 amd64 on Debian 9.x Stretch (unstable, actually Siduction, using systemd). It works well, although I occasionally run into minor issues that I eventually solve. It is after all "unstable".
Over the last few weeks a problem remains, binutils_2.27-9_amd64.deb works fine, but several updates of this program which can be loaded by itself, most recently binutils_2.27.90.201612331-1_amd64.deb, all render the system unbootable.
The boot cycle proceeds from sda1 without any errors but the tdm signon comes up with a black background rather the normal blue TDE one. When I logon I get an error message and TDE does not load, showing a problem with my home partition on sda5:
Could not read connection list /home/lsm1/.DCOPserver_LSM1_0 Please check that the "dcopserver" program is running
When I hit Enter I then get:
Could not start tdeinit, Check your installation.
This problem is specific to TDE as I can still load the backup desktop LXQT by the usual logon from the TDE signon box.
When I boot to the console and downgrade to binutils_2.27-9_amd64.deb everything works as usual on the reboot.
If anyone has any possible solutions I'd be happy to try them out and report back.
Hi there, when binutils is updated, it is necessary to rebuild (or use a rebuilt version of) "dependencies/libr". Without doing so, trying to update binutils will raise a conflict with tdelibs which in turns brings up a long list of packages that needs to be "removed". After rebuilding and installing the new libr, binutils can be updated without problem.
for those using TDE on Sid/stretch you have two choices:
- if you are building TDE yuorselves, just rebuild and install libr
- if you are using preliminary stable builds from Slavek's repo, wait
until libr is rebuilt and then update binutils at the same time.
After doing all that, I think you will not run into the issue mentioned by McCarty. If you do so, just rebuild and reinstall tdelibs as well from CLI. Just for info, from time to time I run into the same issue (last time was a few weeks ago) and rebuilding as described has always fixed the problem so far (I think libr is enough, but since I do not remember 100% I also recommended tdelibs is the problem persists).
Cheers Michele
I can confirm that the rebuild 'libr' is sufficient. Previously it was dependent on binutils also tdebase == was necessary to rebuild tdebase. However, for R14.0.x this is no longer valid.
I try to update 'libr' in preliminary stable builds repository as soon as I notice a change binutils in the Debian repository. However, then it is essential that users have properly updated lists from preliminary stable builds repository. Without that, it just can not work smoothly.
Cheers
On 01/01/17 05:23 AM, Slávek Banko wrote:
On Sunday 01 of January 2017 06:13:30 Michele Calgaro wrote:
On 2017/01/01 05:50 AM, L.S. McCarty wrote:
Hello to all.
I'm a long-time TDE user running TDE 14.0.4 amd64 on Debian 9.x Stretch (unstable, actually Siduction, using systemd). It works well, although I occasionally run into minor issues that I eventually solve. It is after all "unstable".
Over the last few weeks a problem remains, binutils_2.27-9_amd64.deb works fine, but several updates of this program which can be loaded by itself, most recently binutils_2.27.90.201612331-1_amd64.deb, all render the system unbootable.
The boot cycle proceeds from sda1 without any errors but the tdm signon comes up with a black background rather the normal blue TDE one. When I logon I get an error message and TDE does not load, showing a problem with my home partition on sda5:
Could not read connection list /home/lsm1/.DCOPserver_LSM1_0 Please check that the "dcopserver" program is running
When I hit Enter I then get:
Could not start tdeinit, Check your installation.
This problem is specific to TDE as I can still load the backup desktop LXQT by the usual logon from the TDE signon box.
When I boot to the console and downgrade to binutils_2.27-9_amd64.deb everything works as usual on the reboot.
If anyone has any possible solutions I'd be happy to try them out and report back.
Hi there, when binutils is updated, it is necessary to rebuild (or use a rebuilt version of) "dependencies/libr". Without doing so, trying to update binutils will raise a conflict with tdelibs which in turns brings up a long list of packages that needs to be "removed". After rebuilding and installing the new libr, binutils can be updated without problem.
for those using TDE on Sid/stretch you have two choices:
- if you are building TDE yuorselves, just rebuild and install libr
- if you are using preliminary stable builds from Slavek's repo, wait
until libr is rebuilt and then update binutils at the same time.
After doing all that, I think you will not run into the issue mentioned by McCarty. If you do so, just rebuild and reinstall tdelibs as well from CLI. Just for info, from time to time I run into the same issue (last time was a few weeks ago) and rebuilding as described has always fixed the problem so far (I think libr is enough, but since I do not remember 100% I also recommended tdelibs is the problem persists).
Cheers Michele
I can confirm that the rebuild 'libr' is sufficient. Previously it was dependent on binutils also tdebase == was necessary to rebuild tdebase. However, for R14.0.x this is no longer valid.
I try to update 'libr' in preliminary stable builds repository as soon as I notice a change binutils in the Debian repository. However, then it is essential that users have properly updated lists from preliminary stable builds repository. Without that, it just can not work smoothly.
Cheers
Thanks to all for the comprehensive advice. I usually find important things through questions from others so I don't have to ask too many things myself.
I updated to R14.0.5 PSB (I usually track PSB but just hadn't got to it). Then I tried both of the latest binutils versions, debian testing and unstable. The problem remains exactly as before. Is there any further info I can provide?
Cheers!
On Sunday 01 of January 2017 15:51:17 L.S. McCarty wrote:
On 01/01/17 05:23 AM, Slávek Banko wrote:
On Sunday 01 of January 2017 06:13:30 Michele Calgaro wrote:
On 2017/01/01 05:50 AM, L.S. McCarty wrote:
Hello to all.
I'm a long-time TDE user running TDE 14.0.4 amd64 on Debian 9.x Stretch (unstable, actually Siduction, using systemd). It works well, although I occasionally run into minor issues that I eventually solve. It is after all "unstable".
Over the last few weeks a problem remains, binutils_2.27-9_amd64.deb works fine, but several updates of this program which can be loaded by itself, most recently binutils_2.27.90.201612331-1_amd64.deb, all render the system unbootable.
The boot cycle proceeds from sda1 without any errors but the tdm signon comes up with a black background rather the normal blue TDE one. When I logon I get an error message and TDE does not load, showing a problem with my home partition on sda5:
Could not read connection list /home/lsm1/.DCOPserver_LSM1_0 Please check that the "dcopserver" program is running
When I hit Enter I then get:
Could not start tdeinit, Check your installation.
This problem is specific to TDE as I can still load the backup desktop LXQT by the usual logon from the TDE signon box.
When I boot to the console and downgrade to binutils_2.27-9_amd64.deb everything works as usual on the reboot.
If anyone has any possible solutions I'd be happy to try them out and report back.
Hi there, when binutils is updated, it is necessary to rebuild (or use a rebuilt version of) "dependencies/libr". Without doing so, trying to update binutils will raise a conflict with tdelibs which in turns brings up a long list of packages that needs to be "removed". After rebuilding and installing the new libr, binutils can be updated without problem.
for those using TDE on Sid/stretch you have two choices:
- if you are building TDE yuorselves, just rebuild and install libr
- if you are using preliminary stable builds from Slavek's repo, wait
until libr is rebuilt and then update binutils at the same time.
After doing all that, I think you will not run into the issue mentioned by McCarty. If you do so, just rebuild and reinstall tdelibs as well from CLI. Just for info, from time to time I run into the same issue (last time was a few weeks ago) and rebuilding as described has always fixed the problem so far (I think libr is enough, but since I do not remember 100% I also recommended tdelibs is the problem persists).
Cheers Michele
I can confirm that the rebuild 'libr' is sufficient. Previously it was dependent on binutils also tdebase == was necessary to rebuild tdebase. However, for R14.0.x this is no longer valid.
I try to update 'libr' in preliminary stable builds repository as soon as I notice a change binutils in the Debian repository. However, then it is essential that users have properly updated lists from preliminary stable builds repository. Without that, it just can not work smoothly.
Cheers
Thanks to all for the comprehensive advice. I usually find important things through questions from others so I don't have to ask too many things myself.
I updated to R14.0.5 PSB (I usually track PSB but just hadn't got to it). Then I tried both of the latest binutils versions, debian testing and unstable. The problem remains exactly as before. Is there any further info I can provide?
Cheers!
Siduction is based on Debian Sid. Therefore, for Trinity should be apt line as follows:
deb http://mirror.xcer.cz/trinity-sb sid deps-r14 main-r14
Current version of binutils in Sid is 2.27.90.20161231-1. For this binutils version is in deps-r14 corresponding libr0 version 4:0.6.0-3debian9.0.0+4~b7. Please verify (for example, by aptitude), whether you have available just these versions.
On 01/01/17 11:42 AM, Slávek Banko wrote:
On Sunday 01 of January 2017 15:51:17 L.S. McCarty wrote:
On 01/01/17 05:23 AM, Slávek Banko wrote:
On Sunday 01 of January 2017 06:13:30 Michele Calgaro wrote:
On 2017/01/01 05:50 AM, L.S. McCarty wrote:
Hello to all.
I'm a long-time TDE user running TDE 14.0.4 amd64 on Debian 9.x Stretch (unstable, actually Siduction, using systemd). It works well, although I occasionally run into minor issues that I eventually solve. It is after all "unstable".
Over the last few weeks a problem remains, binutils_2.27-9_amd64.deb works fine, but several updates of this program which can be loaded by itself, most recently binutils_2.27.90.201612331-1_amd64.deb, all render the system unbootable.
The boot cycle proceeds from sda1 without any errors but the tdm signon comes up with a black background rather the normal blue TDE one. When I logon I get an error message and TDE does not load, showing a problem with my home partition on sda5:
Could not read connection list /home/lsm1/.DCOPserver_LSM1_0 Please check that the "dcopserver" program is running
When I hit Enter I then get:
Could not start tdeinit, Check your installation.
This problem is specific to TDE as I can still load the backup desktop LXQT by the usual logon from the TDE signon box.
When I boot to the console and downgrade to binutils_2.27-9_amd64.deb everything works as usual on the reboot.
If anyone has any possible solutions I'd be happy to try them out and report back.
Hi there, when binutils is updated, it is necessary to rebuild (or use a rebuilt version of) "dependencies/libr". Without doing so, trying to update binutils will raise a conflict with tdelibs which in turns brings up a long list of packages that needs to be "removed". After rebuilding and installing the new libr, binutils can be updated without problem.
for those using TDE on Sid/stretch you have two choices:
- if you are building TDE yuorselves, just rebuild and install libr
- if you are using preliminary stable builds from Slavek's repo, wait
until libr is rebuilt and then update binutils at the same time.
After doing all that, I think you will not run into the issue mentioned by McCarty. If you do so, just rebuild and reinstall tdelibs as well from CLI. Just for info, from time to time I run into the same issue (last time was a few weeks ago) and rebuilding as described has always fixed the problem so far (I think libr is enough, but since I do not remember 100% I also recommended tdelibs is the problem persists).
Cheers Michele
I can confirm that the rebuild 'libr' is sufficient. Previously it was dependent on binutils also tdebase == was necessary to rebuild tdebase. However, for R14.0.x this is no longer valid.
I try to update 'libr' in preliminary stable builds repository as soon as I notice a change binutils in the Debian repository. However, then it is essential that users have properly updated lists from preliminary stable builds repository. Without that, it just can not work smoothly.
Cheers
Thanks to all for the comprehensive advice. I usually find important things through questions from others so I don't have to ask too many things myself.
I updated to R14.0.5 PSB (I usually track PSB but just hadn't got to it). Then I tried both of the latest binutils versions, debian testing and unstable. The problem remains exactly as before. Is there any further info I can provide?
Cheers!
Siduction is based on Debian Sid. Therefore, for Trinity should be apt line as follows:
deb http://mirror.xcer.cz/trinity-sb sid deps-r14 main-r14
Current version of binutils in Sid is 2.27.90.20161231-1. For this binutils version is in deps-r14 corresponding libr0 version 4:0.6.0-3debian9.0.0+4~b7. Please verify (for example, by aptitude), whether you have available just these versions.
Slaveck,
Thanks for your usual excellent advice. Our messages are crossing out of sync. After receiving a series of helpful messages I noted how I resolved the problem a little while ago, marking the msessage RESOLVED.
I can confirm that the matching pairs of binutils and libr0 in both the testing (stretch) and unstable (Sid) repositories work with Trinity R14.0.5 and Siduction. I'm currently using the Sid versions.
I greatly appreciate you help and continued work on Trinity.
On 01/01/17 05:23 AM, Slávek Banko wrote:
On Sunday 01 of January 2017 06:13:30 Michele Calgaro wrote:
On 2017/01/01 05:50 AM, L.S. McCarty wrote:
Hello to all.
I'm a long-time TDE user running TDE 14.0.4 amd64 on Debian 9.x Stretch (unstable, actually Siduction, using systemd). It works well, although I occasionally run into minor issues that I eventually solve. It is after all "unstable".
Over the last few weeks a problem remains, binutils_2.27-9_amd64.deb works fine, but several updates of this program which can be loaded by itself, most recently binutils_2.27.90.201612331-1_amd64.deb, all render the system unbootable.
The boot cycle proceeds from sda1 without any errors but the tdm signon comes up with a black background rather the normal blue TDE one. When I logon I get an error message and TDE does not load, showing a problem with my home partition on sda5:
Could not read connection list /home/lsm1/.DCOPserver_LSM1_0 Please check that the "dcopserver" program is running
When I hit Enter I then get:
Could not start tdeinit, Check your installation.
This problem is specific to TDE as I can still load the backup desktop LXQT by the usual logon from the TDE signon box.
When I boot to the console and downgrade to binutils_2.27-9_amd64.deb everything works as usual on the reboot.
If anyone has any possible solutions I'd be happy to try them out and report back.
Hi there, when binutils is updated, it is necessary to rebuild (or use a rebuilt version of) "dependencies/libr". Without doing so, trying to update binutils will raise a conflict with tdelibs which in turns brings up a long list of packages that needs to be "removed". After rebuilding and installing the new libr, binutils can be updated without problem.
for those using TDE on Sid/stretch you have two choices:
- if you are building TDE yuorselves, just rebuild and install libr
- if you are using preliminary stable builds from Slavek's repo, wait
until libr is rebuilt and then update binutils at the same time.
After doing all that, I think you will not run into the issue mentioned by McCarty. If you do so, just rebuild and reinstall tdelibs as well from CLI. Just for info, from time to time I run into the same issue (last time was a few weeks ago) and rebuilding as described has always fixed the problem so far (I think libr is enough, but since I do not remember 100% I also recommended tdelibs is the problem persists).
Cheers Michele
I can confirm that the rebuild 'libr' is sufficient. Previously it was dependent on binutils also tdebase == was necessary to rebuild tdebase. However, for R14.0.x this is no longer valid.
I try to update 'libr' in preliminary stable builds repository as soon as I notice a change binutils in the Debian repository. However, then it is essential that users have properly updated lists from preliminary stable builds repository. Without that, it just can not work smoothly.
Cheers
Thanks to all for the comprehensive advice. I usually find important things through questions from others so I don't have to ask too many things myself.
I updated to R14.0.5 PSB (I usually track PSB but just hadn't got to it). Then I tried both of the latest binutils versions, debian testing and unstable. The problem remains exactly as before. Is there any further info I can provide?
SOLVED!
After reading several of the messages in this thread I now understand my problem. I update files manually using synaptic. When I updated to R14.0.5 I just searched for trinity files. Hence Slaveck's updated libr0 file didn't update. When I updated to libr0 4:0.6.0-3debian9.0.0+4~b6 everything worked.
Now that I think of it I remember some previous problems with libr0. I'll now pay more attention to this. Anyway, thanks to all for the help!