Hello,
Does TDE accepts the Kernel 3.16.0 (Debian Jessie) ?
Because when I try to install "linux-headers-3.16.0-4-686-pae", here below the answer :
Delete the folowing packages : 1) cpp-4.7 2) g++-4.7 3) gcc-4.7 4) gcc-4.7-base 5) kdebase-kio-plugins-trinity 6) kdebase-trinity 7) kdesktop-trinity 8) kmail-trinity 9) konq-plugins-trinity 10) konqueror-nsplugins-trinity 11) konqueror-trinity
Thank.
André
On Sunday 26 of April 2015 22:58:02 andre_debian@numericable.fr wrote:
Hello,
Does TDE accepts the Kernel 3.16.0 (Debian Jessie) ?
Because when I try to install "linux-headers-3.16.0-4-686-pae", here below the answer :
Delete the folowing packages :
cpp-4.7
g++-4.7
gcc-4.7
gcc-4.7-base
kdebase-kio-plugins-trinity
kdebase-trinity
kdesktop-trinity
kmail-trinity
konq-plugins-trinity
konqueror-nsplugins-trinity
konqueror-trinity
Thank.
André
What Trinity version you have installed on? If the final R14.0.0, so that is not suitable for Jessie. R14.0.0 was released long time before the final version of Jessie and therefore now causing conflicts. Instead of final R14.0.0 you can install preliminary packages R14.0.1.
On Sunday 26 April 2015 03:14:48 pm Slávek Banko wrote:
On Sunday 26 of April 2015 22:58:02 andre_debian@numericable.fr wrote:
Hello,
Does TDE accepts the Kernel 3.16.0 (Debian Jessie) ?
Because when I try to install "linux-headers-3.16.0-4-686-pae", here below the answer :
Delete the folowing packages :
cpp-4.7
g++-4.7
gcc-4.7
gcc-4.7-base
kdebase-kio-plugins-trinity
kdebase-trinity
kdesktop-trinity
kmail-trinity
konq-plugins-trinity
konqueror-nsplugins-trinity
konqueror-trinity
Thank.
André
What Trinity version you have installed on? If the final R14.0.0, so that is not suitable for Jessie. R14.0.0 was released long time before the final version of Jessie and therefore now causing conflicts. Instead of final R14.0.0 you can install preliminary packages R14.0.1.
+1,
I am using the R14.0.1 packages with Jessie, ..running great..thanks.
On Monday 27 April 2015 21:02:10 Greg Madden wrote:
On Sunday 26 April 2015 03:14:48 pm Slávek Banko wrote:
On Sunday 26 of April 2015 22:58:02 andre_debian@numericable.fr wrote:
Does TDE accepts the Kernel 3.16.0 (Debian Jessie) ? Because when I try to install "linux-headers-3.16.0-4-686-pae", here below the answer : Delete the folowing packages :
cpp-4.7
g++-4.7
gcc-4.7
gcc-4.7-base
kdebase-kio-plugins-trinity
kdebase-trinity
kdesktop-trinity
kmail-trinity
konq-plugins-trinity
konqueror-nsplugins-trinity
konqueror-trinity
What Trinity version you have installed on? If the final R14.0.0, so that is not suitable for Jessie. R14.0.0 was released long time before the final version of Jessie and therefore now causing conflicts. Instead of final R14.0.0 you can install preliminary packages R14.0.1.
+1, I am using the R14.0.1 packages with Jessie, ..running great..thanks.
Not sure, it's a R14.0.1, but how to be sure ?
thanks.
André
On Monday 27 of April 2015 22:27:39 andre_debian@numericable.fr wrote:
On Monday 27 April 2015 21:02:10 Greg Madden wrote:
On Sunday 26 April 2015 03:14:48 pm Slávek Banko wrote:
On Sunday 26 of April 2015 22:58:02 andre_debian@numericable.fr wrote:
Does TDE accepts the Kernel 3.16.0 (Debian Jessie) ? Because when I try to install "linux-headers-3.16.0-4-686-pae", here below the answer : Delete the folowing packages :
cpp-4.7
g++-4.7
gcc-4.7
gcc-4.7-base
kdebase-kio-plugins-trinity
kdebase-trinity
kdesktop-trinity
kmail-trinity
konq-plugins-trinity
konqueror-nsplugins-trinity
konqueror-trinity
What Trinity version you have installed on? If the final R14.0.0, so that is not suitable for Jessie. R14.0.0 was released long time before the final version of Jessie and therefore now causing conflicts. Instead of final R14.0.0 you can install preliminary packages R14.0.1.
+1, I am using the R14.0.1 packages with Jessie, ..running great..thanks.
Not sure, it's a R14.0.1, but how to be sure ?
thanks.
André
Preliminary packages for R14.0.1 are available on alternative apt source known as 'preliminary-stable-builds':
deb http://mirror.xcer.cz/trinity-sb jessie deps-r14 main-r14
On Monday 27 April 2015 22:37:15 Slávek Banko wrote:
On Sunday 26 of April 2015 22:58:02 andre_debian@numericable.fr wrote:
Does TDE accepts the Kernel 3.16.0 (Debian Jessie) ?
What Trinity version you have installed on? If the final R14.0.0, so that is not suitable for Jessie. R14.0.0 was released long time before the final version of Jessie and therefore now causing conflicts. Instead of final R14.0.0 you can install preliminary packages R14.0.1.
I am using the R14.0.1 packages with Jessie, ..running great..thanks.
Preliminary packages for R14.0.1 are available on alternative apt source known as 'preliminary-stable-builds': deb http://mirror.xcer.cz/trinity-sb jessie deps-r14 main-r14
It's the line I have in /etc/apt/sources.list, so it's a R14.0.1 packages.
How to completely remove TDE-Trinity ?
Since I upgraded Debian to Jessie, I cannot start tde-trinity.
The boot-session "tdm-trinity", appears, I enter my login-user, my password, the desktop starts and at the fifth picture (with a pen) in the blue center area, it stops... impossible to go on !
I tried with others sessions login as gdm3, lightdm => idem.
So, if you have an idea about this break, otherwise I have to re-install all the tde-trinity from new.
Can "systemd" be responsible ?
Thanks.
André
Dne út 28. dubna 2015 andre_debian@numericable.fr napsal(a):
On Monday 27 April 2015 22:37:15 Slávek Banko wrote:
On Sunday 26 of April 2015 22:58:02 andre_debian@numericable.fr
wrote:
Does TDE accepts the Kernel 3.16.0 (Debian Jessie) ?
What Trinity version you have installed on? If the final R14.0.0, so that is not suitable for Jessie. R14.0.0 was released long time before the final version of Jessie and therefore now causing conflicts. Instead of final R14.0.0 you can install preliminary packages R14.0.1.
I am using the R14.0.1 packages with Jessie, ..running great..thanks.
Preliminary packages for R14.0.1 are available on alternative apt source known as 'preliminary-stable-builds': deb http://mirror.xcer.cz/trinity-sb jessie deps-r14 main-r14
It's the line I have in /etc/apt/sources.list, so it's a R14.0.1 packages.
How to completely remove TDE-Trinity ?
Since I upgraded Debian to Jessie, I cannot start tde-trinity.
The boot-session "tdm-trinity", appears, I enter my login-user, my password, the desktop starts and at the fifth picture (with a pen) in the blue center area, it stops... impossible to go on !
I tried with others sessions login as gdm3, lightdm => idem.
So, if you have an idea about this break, otherwise I have to re-install all the tde-trinity from new.
Can "systemd" be responsible ?
Thanks.
André
A few days ago I also noticed a problem with the start kdesktop (on Debian Wheezy) - proved to be similarly - were flashing icon in the splash screen and the desktop was not show. Because my the machine waiting for kernel update, I rebooted and the problem disappeared.
On Tuesday 28 April 2015 18:54:50 Slávek Banko wrote:
Dne út 28. dubna 2015 andre_debian@numericable.fr napsal(a):
How to completely remove TDE-Trinity ? Since I upgraded Debian to Jessie, I cannot start tde-trinity. The boot-session "tdm-trinity", appears, I enter my login-user, my password, the desktop starts and at the fifth picture (with a pen) in the blue center area, it stops... impossible to go on ! I tried with others sessions login as gdm3, lightdm => idem. So, if you have an idea about this break, otherwise I have to re-install all the tde-trinity from new. Can "systemd" be responsible ?
A few days ago I also noticed a problem with the start kdesktop (on Debian Wheezy) - proved to be similarly - were flashing icon in the splash screen and the desktop was not show. Because my the machine waiting for kernel update, I rebooted and the problem disappeared.
With Jessie, the kernel is 3.16 (wheezy was 3.2).
Not solved, reboot does'n change the problem.
Desktop TDE starts and at the fifth icon flashing, the graphic boot stops.
CTRL-ALT-F1 to come back to konsole-mode.
André
On Tue, 28 Apr 2015 20:31:12 +0200 andre_debian@numericable.fr wrote:
On Tuesday 28 April 2015 18:54:50 Slávek Banko wrote:
Dne út 28. dubna 2015 andre_debian@numericable.fr napsal(a):
How to completely remove TDE-Trinity ? Since I upgraded Debian to Jessie, I cannot start tde-trinity. The boot-session "tdm-trinity", appears, I enter my login-user, my password, the desktop starts and at the fifth picture (with a pen) in the blue center area, it stops... impossible to go on ! I tried with others sessions login as gdm3, lightdm => idem. So, if you have an idea about this break, otherwise I have to re-install all the tde-trinity from new. Can "systemd" be responsible ?
A few days ago I also noticed a problem with the start kdesktop (on Debian Wheezy) - proved to be similarly - were flashing icon in the splash screen and the desktop was not show. Because my the machine waiting for kernel update, I rebooted and the problem disappeared.
With Jessie, the kernel is 3.16 (wheezy was 3.2).
Not solved, reboot does'n change the problem.
Desktop TDE starts and at the fifth icon flashing, the graphic boot stops.
CTRL-ALT-F1 to come back to konsole-mode.
Well, "it works for me" :) and a lot of other people so its not that packages are broken. Have you tried adding a new user and login as him? Maybe something broke in your user configuration.
Hi Nick,
On Tuesday 28 April 2015 21:29:48 Nick Koretsky wrote:
On Tue, 28 Apr 2015 20:31:12 +0200
andre_debian@numericable.fr wrote:
On Tuesday 28 April 2015 18:54:50 Slávek Banko wrote:
Dne út 28. dubna 2015 andre_debian@numericable.fr napsal(a):
How to completely remove TDE-Trinity ? Since I upgraded Debian to Jessie, I cannot start tde-trinity. The boot-session "tdm-trinity", appears, I enter my login-user, my password, the desktop starts and at the fifth picture (with a pen) in the blue center area, it stops... impossible to go on ! I tried with others sessions login as gdm3, lightdm => idem. So, if you have an idea about this break, otherwise I have to re-install all the tde-trinity from new. Can "systemd" be responsible ?
A few days ago I also noticed a problem with the start kdesktop (on Debian Wheezy) - proved to be similarly - were flashing icon in the splash screen and the desktop was not show. Because my the machine waiting for kernel update, I rebooted and the problem disappeared.
With Jessie, the kernel is 3.16 (wheezy was 3.2).
Not solved, reboot does'n change the problem.
Desktop TDE starts and at the fifth icon flashing, the graphic boot stops.
CTRL-ALT-F1 to come back to konsole-mode.
Well, "it works for me" :) and a lot of other people so its not that packages are broken. Have you tried adding a new user and login as him? Maybe something broke in your user configuration.
I tried that without any change in behaviour! Though I do agree that something has changed.
On Tue, 28 Apr 2015 23:00:52 +0100 Baron baron@linuxmaniac.net wrote:
Hi Nick,
On Tuesday 28 April 2015 21:29:48 Nick Koretsky wrote:
On Tue, 28 Apr 2015 20:31:12 +0200
andre_debian@numericable.fr wrote:
On Tuesday 28 April 2015 18:54:50 Slávek Banko wrote:
Dne út 28. dubna 2015 andre_debian@numericable.fr napsal(a):
How to completely remove TDE-Trinity ? Since I upgraded Debian to Jessie, I cannot start tde-trinity. The boot-session "tdm-trinity", appears, I enter my login-user, my password, the desktop starts and at the fifth picture (with a pen) in the blue center area, it stops... impossible to go on ! I tried with others sessions login as gdm3, lightdm => idem. So, if you have an idea about this break, otherwise I have to re-install all the tde-trinity from new. Can "systemd" be responsible ?
A few days ago I also noticed a problem with the start kdesktop (on Debian Wheezy) - proved to be similarly - were flashing icon in the splash screen and the desktop was not show. Because my the machine waiting for kernel update, I rebooted and the problem disappeared.
With Jessie, the kernel is 3.16 (wheezy was 3.2).
Not solved, reboot does'n change the problem.
Desktop TDE starts and at the fifth icon flashing, the graphic boot stops.
CTRL-ALT-F1 to come back to konsole-mode.
Well, "it works for me" :) and a lot of other people so its not that packages are broken. Have you tried adding a new user and login as him? Maybe something broke in your user configuration.
I tried that without any change in behaviour! Though I do agree that something has changed.
Ironically right after writing previous message i encountered this behavior on the first boot into jessie on the next machine i updated. But it was fixed by restarting tdm-trinity.
Hi Nick,
On Tuesday 28 April 2015 23:57:36 Nick Koretsky wrote:
On Tue, 28 Apr 2015 23:00:52 +0100
Baron baron@linuxmaniac.net wrote:
Hi Nick,
On Tuesday 28 April 2015 21:29:48 Nick Koretsky wrote:
On Tue, 28 Apr 2015 20:31:12 +0200
andre_debian@numericable.fr wrote:
On Tuesday 28 April 2015 18:54:50 Slávek Banko wrote:
Dne út 28. dubna 2015 andre_debian@numericable.fr napsal(a):
How to completely remove TDE-Trinity ? Since I upgraded Debian to Jessie, I cannot start tde-trinity. The boot-session "tdm-trinity", appears, I enter my login-user, my password, the desktop starts and at the fifth picture (with a pen) in the blue center area, it stops... impossible to go on ! I tried with others sessions login as gdm3, lightdm => idem. So, if you have an idea about this break, otherwise I have to re-install all the tde-trinity from new. Can "systemd" be responsible ?
A few days ago I also noticed a problem with the start kdesktop (on Debian Wheezy) - proved to be similarly - were flashing icon in the splash screen and the desktop was not show. Because my the machine waiting for kernel update, I rebooted and the problem disappeared.
With Jessie, the kernel is 3.16 (wheezy was 3.2).
Not solved, reboot does'n change the problem.
Desktop TDE starts and at the fifth icon flashing, the graphic boot stops.
CTRL-ALT-F1 to come back to konsole-mode.
Well, "it works for me" :) and a lot of other people so its not that packages are broken. Have you tried adding a new user and login as him? Maybe something broke in your user configuration.
I tried that without any change in behaviour! Though I do agree that something has changed.
Ironically right after writing previous message i encountered this behavior on the first boot into jessie on the next machine i updated. But it was fixed by restarting tdm-trinity.
Unfortunately that hasn't worked for me :-)
What I find interesting is having to wait and then reentering my password after which everything works Ok. Even root behaves the same. There is something that has to complete before I / you can login.
On Wed, 29 Apr 2015 16:43:42 +0100 Baron baron@linuxmaniac.net wrote:
Hi Nick,
On Tuesday 28 April 2015 23:57:36 Nick Koretsky wrote:
On Tue, 28 Apr 2015 23:00:52 +0100
Baron baron@linuxmaniac.net wrote:
Hi Nick,
On Tuesday 28 April 2015 21:29:48 Nick Koretsky wrote:
On Tue, 28 Apr 2015 20:31:12 +0200
andre_debian@numericable.fr wrote:
On Tuesday 28 April 2015 18:54:50 Slávek Banko wrote:
Dne út 28. dubna 2015 andre_debian@numericable.fr napsal(a): > How to completely remove TDE-Trinity ? > Since I upgraded Debian to Jessie, I cannot start > tde-trinity. The boot-session "tdm-trinity", appears, I > enter my login-user, my password, the desktop starts and > at the fifth picture (with a pen) in the blue center > area, it stops... impossible to go on ! I tried with > others sessions login as gdm3, lightdm => idem. So, if > you have an idea about this break, > otherwise I have to re-install all the tde-trinity from > new. Can "systemd" be responsible ?
A few days ago I also noticed a problem with the start kdesktop (on Debian Wheezy) - proved to be similarly - were flashing icon in the splash screen and the desktop was not show. Because my the machine waiting for kernel update, I rebooted and the problem disappeared.
With Jessie, the kernel is 3.16 (wheezy was 3.2).
Not solved, reboot does'n change the problem.
Desktop TDE starts and at the fifth icon flashing, the graphic boot stops.
CTRL-ALT-F1 to come back to konsole-mode.
Well, "it works for me" :) and a lot of other people so its not that packages are broken. Have you tried adding a new user and login as him? Maybe something broke in your user configuration.
I tried that without any change in behaviour! Though I do agree that something has changed.
Ironically right after writing previous message i encountered this behavior on the first boot into jessie on the next machine i updated. But it was fixed by restarting tdm-trinity.
Unfortunately that hasn't worked for me :-)
What I find interesting is having to wait and then reentering my password after which everything works Ok. Even root behaves the same. There is something that has to complete before I / you can login.
Yep. This machine got stuck in this state few more times while i was frantically rebooting while making my audio and video work :) And it does seems like this happens if you try to login too fast. I dont think it hanged even once if i waited on login screen for a minute or more, but when i typed password immediately it has a decent chance to stuck.
Still, this only happens on one out of four PCs i updated to jessie since release. And no matter how i look i cant comprehend whats different in this one.
Hi Nick,
On Wednesday 29 April 2015 17:17:58 Nick Koretsky wrote:
On Wed, 29 Apr 2015 16:43:42 +0100
Baron baron@linuxmaniac.net wrote:
Hi Nick,
On Tuesday 28 April 2015 23:57:36 Nick Koretsky wrote:
On Tue, 28 Apr 2015 23:00:52 +0100
Baron baron@linuxmaniac.net wrote:
Hi Nick,
On Tuesday 28 April 2015 21:29:48 Nick Koretsky wrote:
On Tue, 28 Apr 2015 20:31:12 +0200
andre_debian@numericable.fr wrote:
On Tuesday 28 April 2015 18:54:50 Slávek Banko wrote: > Dne út 28. dubna 2015 andre_debian@numericable.fr
napsal(a):
> > How to completely remove TDE-Trinity ? > > Since I upgraded Debian to Jessie, I cannot start > > tde-trinity. The boot-session "tdm-trinity", appears, > > I enter my login-user, my password, the desktop > > starts and at the fifth picture (with a pen) in the > > blue center area, it stops... impossible to go on ! I > > tried with others sessions login as gdm3, lightdm => > > idem. So, if you have an idea about this break, > > otherwise I have to re-install all the tde-trinity > > from new. Can "systemd" be responsible ? > > A few days ago I also noticed a problem with the start > kdesktop (on Debian Wheezy) - proved to be similarly - > were flashing icon in the splash screen and the desktop > was not show. Because my the machine waiting for kernel > update, I rebooted and the problem disappeared.
With Jessie, the kernel is 3.16 (wheezy was 3.2).
Not solved, reboot does'n change the problem.
Desktop TDE starts and at the fifth icon flashing, the graphic boot stops.
CTRL-ALT-F1 to come back to konsole-mode.
Well, "it works for me" :) and a lot of other people so its not that packages are broken. Have you tried adding a new user and login as him? Maybe something broke in your user configuration.
I tried that without any change in behaviour! Though I do agree that something has changed.
Ironically right after writing previous message i encountered this behavior on the first boot into jessie on the next machine i updated. But it was fixed by restarting tdm-trinity.
Unfortunately that hasn't worked for me :-)
What I find interesting is having to wait and then reentering my password after which everything works Ok. Even root behaves the same. There is something that has to complete before I / you can login.
Yep. This machine got stuck in this state few more times while i was frantically rebooting while making my audio and video work :) And it does seems like this happens if you try to login too fast. I dont think it hanged even once if i waited on login screen for a minute or more, but when i typed password immediately it has a decent chance to stuck.
Still, this only happens on one out of four PCs i updated to jessie since release. And no matter how i look i cant comprehend whats different in this one.
I wonder if its hardware related. I upgraded a friends machine and he doesn't have this problem. His machine, mother board wise is AMD based, while mine is intel based. We both have mother boards with built in graphic cards and both have the same Nvidia external AGP graphic cards. But I think that there are to many differences to be able to speculate.
On Wed, 29 Apr 2015 17:36:00 +0100 Baron baron@linuxmaniac.net wrote:
Ironically right after writing previous message i encountered this behavior on the first boot into jessie on the next machine i updated. But it was fixed by restarting tdm-trinity.
Unfortunately that hasn't worked for me :-)
What I find interesting is having to wait and then reentering my password after which everything works Ok. Even root behaves the same. There is something that has to complete before I / you can login.
Yep. This machine got stuck in this state few more times while i was frantically rebooting while making my audio and video work :) And it does seems like this happens if you try to login too fast. I dont think it hanged even once if i waited on login screen for a minute or more, but when i typed password immediately it has a decent chance to stuck.
Still, this only happens on one out of four PCs i updated to jessie since release. And no matter how i look i cant comprehend whats different in this one.
I wonder if its hardware related. I upgraded a friends machine and he doesn't have this problem. His machine, mother board wise is AMD based, while mine is intel based. We both have mother boards with built in graphic cards and both have the same Nvidia external AGP graphic cards. But I think that there are to many differences to be able to speculate.
It doesnt look like its hardware related. All my machines have AMD CPU's. The one which exhibits this have AMD video, but one of others have AMD video too. This behavior happens both with radeon and fglrx drivers. Also this is not systemd related as someone suggested early because i left this one on sysv-init.
Also i tried to monitors what happens when it gets stuck - apparently at one point in tde startup process two kdesktop process started, one finishes almost instantly and other goes to sleep. When it stuck the second process doesnt finish and just sits here. If you kill it (the one which is not in Sl state) tde stratup would proceeds into half-functioning tde session (kicker related stuff works, but desktop is not loaded and background remains from startup. Apparently some other services do not start too because its complains when you try to logout)
On Wednesday 29 April 2015 23:36:19 Nick Koretsky wrote:
On Wed, 29 Apr 2015 17:36:00 +0100
Baron baron@linuxmaniac.net wrote:
Ironically right after writing previous message i encountered this behavior on the first boot into jessie on the next machine i updated. But it was fixed by restarting tdm-trinity.
Unfortunately that hasn't worked for me :-)
What I find interesting is having to wait and then reentering my password after which everything works Ok. Even root behaves the same. There is something that has to complete before I / you can login.
Yep. This machine got stuck in this state few more times while i was frantically rebooting while making my audio and video work :) And it does seems like this happens if you try to login too fast. I dont think it hanged even once if i waited on login screen for a minute or more, but when i typed password immediately it has a decent chance to stuck.
Still, this only happens on one out of four PCs i updated to jessie since release. And no matter how i look i cant comprehend whats different in this one.
I wonder if its hardware related. I upgraded a friends machine and he doesn't have this problem. His machine, mother board wise is AMD based, while mine is intel based. We both have mother boards with built in graphic cards and both have the same Nvidia external AGP graphic cards. But I think that there are to many differences to be able to speculate.
It doesnt look like its hardware related. All my machines have AMD CPU's. The one which exhibits this have AMD video, but one of others have AMD video too. This behavior happens both with radeon and fglrx drivers. Also this is not systemd related as someone suggested early because i left this one on sysv-init.
Also i tried to monitors what happens when it gets stuck - apparently at one point in tde startup process two kdesktop process started, one finishes almost instantly and other goes to sleep. When it stuck the second process doesnt finish and just sits here. If you kill it (the one which is not in Sl state) tde stratup would proceeds into half-functioning tde session (kicker related stuff works, but desktop is not loaded and background remains from startup. Apparently some other services do not start too because its complains when you try to logout)
Apart from not discovering the second desktop process, going through another tty sometimes let me into this half functioning state. It was completly by accident, being called away after putting in my password that I found that the password field was now blank and putting my password in again and pressing enter or the login button that TDE started normally.
On Wednesday 29 April 2015 17:43:42 Baron wrote:
Well, "it works for me" :) and a lot of other people so its not that packages are broken. Have you tried adding a new user and login as him? Maybe something broke in your user configuration.
I delete all TDE and reinstalled it, created a new user, but idem, TDE starts and stop as expalined before...
What I find interesting is having to wait and then reentering my password after which everything works Ok. Even root behaves the same. There is something that has to complete before I / you can login.
Can you explain your method to make TDE starting normally, exactly what you do with tne graphic boot "tdm-trinity".
Thanks.
André
Hi Andre,
On Wednesday 29 April 2015 22:33:22 andre_debian@numericable.fr wrote:
On Wednesday 29 April 2015 17:43:42 Baron wrote:
Well, "it works for me" :) and a lot of other people so its not that packages are broken. Have you tried adding a new user and login as him? Maybe something broke in your user configuration.
I delete all TDE and reinstalled it, created a new user, but idem, TDE starts and stop as expalined before...
What I find interesting is having to wait and then reentering my password after which everything works Ok. Even root behaves the same. There is something that has to complete before I / you can login.
Can you explain your method to make TDE starting normally, exactly what you do with tne graphic boot "tdm-trinity".
Thanks.
André
Simply wait until the password field becomes blank and then put the password back in and press enter.
This works for me every time ! It's just inconvienient.
I've just got the bits for a new machine, so when I get it assembled and Linux loaded I'll be able to see what happens on it. Probably over the bank holiday weekend.
On Thursday 30 April 2015 00:56:31 Baron wrote:
Hi Andre, Simply wait until the password field becomes blank and then put the password back in and press enter. This works for me every time ! It's just inconvienient.
I tried your method, it works, but as you said, it's inconvienient. It's better than nothing :-)
I've just got the bits for a new machine, so when I get it assembled and Linux loaded I'll be able to see what happens on it. Probably over the bank holiday weekend.
It would great if you can find the solution for the TDE stopped boot, and many thanks by advance.
André
Am Donnerstag, 30. April 2015 schrieb andre_debian@numericable.fr:
On Thursday 30 April 2015 00:56:31 Baron wrote:
Hi Andre, Simply wait until the password field becomes blank and then put the password back in and press enter. This works for me every time ! It's just inconvienient.
I tried your method, it works, but as you said, it's inconvienient. It's better than nothing :-)
I've just got the bits for a new machine, so when I get it assembled and Linux loaded I'll be able to see what happens on it. Probably over the bank holiday weekend.
It would great if you can find the solution for the TDE stopped boot, and many thanks by advance.
This problem is not kernel specific. I have made dist-upgrade on my test installation (wheezy) without systemd. Login is automatic. Sometimes (1 of 10) TDE hangs when loading user settings. I have to kill the first instance of X11 with <ctrl>+<alt>+<backspace> and it works.
nik
On Friday 01 May 2015 09:15:53 Dr. Nikolaus Klepp wrote:
Am Donnerstag, 30. April 2015 schrieb andre_debian@numericable.fr:
On Thursday 30 April 2015 00:56:31 Baron wrote:
Simply wait until the password field becomes blank and then put the password back in and press enter. This works for me every time ! It's just inconvienient.
I tried your method, it works, but as you said, it's inconvienient. It's better than nothing :-)
I've just got the bits for a new machine, so when I get it assembled and Linux loaded I'll be able to see what happens on it. Probably over the bank holiday weekend.
It would great if you can find the solution for the TDE stopped boot, and many thanks by advance.
This problem is not kernel specific. I have made dist-upgrade on my test installation (wheezy) without systemd. Login is automatic. Sometimes (1 of 10) TDE hangs when loading user settings. I have to kill the first instance of X11 with <ctrl>+<alt>+<backspace> and it works. nik
Hello,
I'm not on Wheezy, but "Jessie" and with "systemd". Not sure it's possible to deactivate or delete systemd with Jessie...
André
On Fri, 1 May 2015 11:41:02 +0200 andre_debian@numericable.fr wrote:
On Friday 01 May 2015 09:15:53 Dr. Nikolaus Klepp wrote:
Am Donnerstag, 30. April 2015 schrieb andre_debian@numericable.fr:
On Thursday 30 April 2015 00:56:31 Baron wrote:
Simply wait until the password field becomes blank and then put the password back in and press enter. This works for me every time ! It's just inconvienient.
I tried your method, it works, but as you said, it's inconvienient. It's better than nothing :-)
I've just got the bits for a new machine, so when I get it assembled and Linux loaded I'll be able to see what happens on it. Probably over the bank holiday weekend.
It would great if you can find the solution for the TDE stopped boot, and many thanks by advance.
This problem is not kernel specific. I have made dist-upgrade on my test installation (wheezy) without systemd. Login is automatic. Sometimes (1 of 10) TDE hangs when loading user settings. I have to kill the first instance of X11 with <ctrl>+<alt>+<backspace> and it works. nik
Hello,
I'm not on Wheezy, but "Jessie" and with "systemd". Not sure it's possible to deactivate or delete systemd with Jessie...
1. Jessie works perfectly with sysv. all you have to do is install sysvinit-core and deinstall systemd-sysv. 2. Tde stuck on 5th icon on startup doesnt seem to be related to systemd or even jessie, it looks more like a bug in preliminary-stable version of tde. Its just that people are now forced to use this version on jessie and started to step on it.
On Friday 01 of May 2015 12:50:58 Lisi Reisz wrote:
On Friday 01 May 2015 11:05:42 Nick Koretsky wrote:
it looks more like a bug in preliminary-stable version of tde.
Then report it as a bug so that it can get sorted.
Lisi
Yes, this is related to the recent set of patches, which resolved problems with threads and signals between kdesktop and kdesktop_lock. Apparently there is some new race-condition at startup. I'll report this bug soon... Currently, this is the most important bug blocking R14.0.1.
Hi Slavek,
On Friday 01 May 2015 12:07:06 Slávek Banko wrote:
Then report it as a bug so that it can get sorted.
Lisi
Yes, this is related to the recent set of patches, which resolved problems with threads and signals between kdesktop and kdesktop_lock. Apparently there is some new race-condition at startup. I'll report this bug soon... Currently, this is the most important bug blocking R14.0.1.
Thankyou for that confirmation. I'm just about to build a new machine for my self and have two others ariving on Tuesday for clients. These both need to have Jessie + TDE loaded on them.
Thanks for the good work. Unfortunately I'm a hardware engineer and absolutely rubbish with software. I'm more at home with a mill and a lathe nowadays.
On Friday 01 May 2015 09:15:53 Dr. Nikolaus Klepp wrote:
- Jessie works perfectly with sysv. all you have to do is install
sysvinit-core and deinstall systemd-sysv. 2. Tde stuck on 5th icon on startup doesnt seem to be related to systemd or even jessie, it looks more like a bug in preliminary-stable version of tde. Its just that people are now forced to use this version on jessie and started to step on it.
Ok, so, not necessary to migrate from "systemd" to "sysv",
On Friday 01 May 2015 14:02:06 Baron wrote:
Hi Slavek, On Friday 01 May 2015 12:07:06 Slávek Banko wrote:
Then report it as a bug so that it can get sorted. Lisi
Yes, this is related to the recent set of patches, which resolved problems with threads and signals between kdesktop and kdesktop_lock. Apparently there is some new race-condition at startup. I'll report this bug soon... Currently, this is the most important bug blocking R14.0.1.
Thankyou for that confirmation. I'm just about to build a new machine for my self and have two others arriving on Tuesday for clients. These both need to have Jessie + TDE loaded on them.
Thanks for the good work. Unfortunately I'm a hardware engineer and absolutely rubbish with software. I'm more at home with a mill and a lathe nowadays.
When about the patch to resolve the bug blocking login to TDE will available ?
Thanks.
André
On Friday 01 of May 2015 14:02:06 Baron wrote:
Hi Slavek,
On Friday 01 May 2015 12:07:06 Slávek Banko wrote:
Then report it as a bug so that it can get sorted.
Lisi
Yes, this is related to the recent set of patches, which resolved problems with threads and signals between kdesktop and kdesktop_lock. Apparently there is some new race-condition at startup. I'll report this bug soon... Currently, this is the most important bug blocking R14.0.1.
Thankyou for that confirmation. I'm just about to build a new machine for my self and have two others ariving on Tuesday for clients. These both need to have Jessie + TDE loaded on them.
Thanks for the good work. Unfortunately I'm a hardware engineer and absolutely rubbish with software. I'm more at home with a mill and a lathe nowadays.
Bug report filled. See bug 2437:
http://bugs.pearsoncomputing.net/show_bug.cgi?id=2437
On Friday 01 May 2015 18:53:19 Slávek Banko wrote:
On Friday 01 May 2015 12:07:06 Slávek Banko wrote:
Then report it as a bug so that it can get sorted.
Yes, this is related to the recent set of patches, which resolved problems with threads and signals between kdesktop and kdesktop_lock. Apparently there is some new race-condition at startup. I'll report this bug soon... Currently, this is the most important bug blocking R14.0.1.
Thankyou for that confirmation. I'm just about to build a new machine for my self and have two others ariving on Tuesday for clients. These both need to have Jessie + TDE loaded on them. Thanks for the good work. Unfortunately I'm a hardware engineer and absolutely rubbish with software. I'm more at home with a mill and a lathe nowadays.
Bug report filled. See bug 2437: http://bugs.pearsoncomputing.net/show_bug.cgi?id=2437
But actually no patch to correct the bug ?
André
On Friday 01 May 2015 18:45:26 André wrote:
On Friday 01 May 2015 18:53:19 Slávek Banko wrote:
On Friday 01 May 2015 12:07:06 Slávek Banko wrote:
Then report it as a bug so that it can get sorted.
Yes, this is related to the recent set of patches, which resolved problems with threads and signals between kdesktop and kdesktop_lock. Apparently there is some new race-condition at startup. I'll report this bug soon... Currently, this is the most important bug blocking R14.0.1.
Thankyou for that confirmation. I'm just about to build a new machine for my self and have two others ariving on Tuesday for clients. These both need to have Jessie + TDE loaded on them. Thanks for the good work. Unfortunately I'm a hardware engineer and absolutely rubbish with software. I'm more at home with a mill and a lathe nowadays.
Bug report filled. See bug 2437: http://bugs.pearsoncomputing.net/show_bug.cgi?id=2437
But actually no patch to correct the bug ?
Give him (and the others) time! The difficult he can do today. The impossible takes a little longer. Nothing can actually be done yesterday.
The developers are doing this for nothing in their free time. You must be a little patient.
The bug was reported just before 17:53 (my time) and at 18:45 you are complaining that your problem has not yet been solved. What planet do you live on???
Lisi
On 15-05-01 06:29 PM, Lisi Reisz wrote:
On Friday 01 May 2015 18:45:26 André wrote:
On Friday 01 May 2015 18:53:19 Slávek Banko wrote:
On Friday 01 May 2015 12:07:06 Slávek Banko wrote:
Then report it as a bug so that it can get sorted.
Yes, this is related to the recent set of patches, which resolved problems with threads and signals between kdesktop and kdesktop_lock. Apparently there is some new race-condition at startup. I'll report this bug soon... Currently, this is the most important bug blocking R14.0.1.
Thankyou for that confirmation. I'm just about to build a new machine for my self and have two others ariving on Tuesday for clients. These both need to have Jessie + TDE loaded on them. Thanks for the good work. Unfortunately I'm a hardware engineer and absolutely rubbish with software. I'm more at home with a mill and a lathe nowadays.
Bug report filled. See bug 2437: http://bugs.pearsoncomputing.net/show_bug.cgi?id=2437
But actually no patch to correct the bug ?
Give him (and the others) time! The difficult he can do today. The impossible takes a little longer. Nothing can actually be done yesterday.
The developers are doing this for nothing in their free time. You must be a little patient.
The bug was reported just before 17:53 (my time) and at 18:45 you are complaining that your problem has not yet been solved. What planet do you live on???
Lisi
+1 midi-pascal
On 05/01/2015 03:29 PM, Lisi Reisz wrote:
On Friday 01 May 2015 18:45:26 André wrote:
But actually no patch to correct the bug ?
Nothing can actually be done yesterday.
I'm not sure that's correct; nothing is, in fact, pretty much what I got done yesterday. :)
The bug was reported just before 17:53 (my time) and at 18:45 you are complaining that your problem has not yet been solved. What planet do you live on???
Maybe he was complaining, or maybe just asking for clarification. We need to remember that those whose native language is not English often phrase things a little differently than we would, and give them the benefit of the doubt.
On Saturday 02 May 2015 02:01:55 Dan Youngquist wrote:
On 05/01/2015 03:29 PM, Lisi Reisz wrote:
On Friday 01 May 2015 18:45:26 André wrote:
But actually no patch to correct the bug ?
Nothing can actually be done yesterday.
I'm not sure that's correct; nothing is, in fact, pretty much what I got done yesterday. :)
The bug was reported just before 17:53 (my time) and at 18:45 you are complaining that your problem has not yet been solved. What planet do you live on???
Maybe he was complaining, or maybe just asking for clarification. We need to remember that those whose native language is not English often phrase things a little differently than we would, and give them the benefit of the doubt.
Sorry, if I have hurted.
I'm not in a hurry, I'm not complaining about the bug, I can wait... and understand that it's not so easy to repair, as the certificate of TDE site with many complaints :-)
André
Hi All,
Well something has changed ! I did an update last night and this morning found that I could no longer get to my desktop using the technique of waiting for the password to disappear.
Now both my user name and the password are cleared ! However reinstating them both and pressing enter left me with the desktop failing to load and then a dark blue screen.
Eventually I got a working desktop on one of the tty's. But only Kmail and Iceweasel work. The other applications including Synaptic, that I tried don't.
Not good ! For the uninitiated this means that their machine is effectively unuseable.
HTH.
Nothing can actually be done yesterday.
I'm not sure that's correct; nothing is, in fact, pretty much what I got done yesterday. :)
The bug was reported just before 17:53 (my time) and at 18:45 you are complaining that your problem has not yet been solved. What planet do you live on???
Maybe he was complaining, or maybe just asking for clarification. We need to remember that those whose native language is not English often phrase things a little differently than we would, and give them the benefit of the doubt.
It's right, thank you Dan.
You understand the human soul :-)
André
On Tuesday 28 of April 2015 20:31:12 andre_debian@numericable.fr wrote:
On Tuesday 28 April 2015 18:54:50 Slávek Banko wrote:
Dne út 28. dubna 2015 andre_debian@numericable.fr napsal(a):
How to completely remove TDE-Trinity ? Since I upgraded Debian to Jessie, I cannot start tde-trinity. The boot-session "tdm-trinity", appears, I enter my login-user, my password, the desktop starts and at the fifth picture (with a pen) in the blue center area, it stops... impossible to go on ! I tried with others sessions login as gdm3, lightdm => idem. So, if you have an idea about this break, otherwise I have to re-install all the tde-trinity from new. Can "systemd" be responsible ?
A few days ago I also noticed a problem with the start kdesktop (on Debian Wheezy) - proved to be similarly - were flashing icon in the splash screen and the desktop was not show. Because my the machine waiting for kernel update, I rebooted and the problem disappeared.
With Jessie, the kernel is 3.16 (wheezy was 3.2).
Not solved, reboot does'n change the problem.
Desktop TDE starts and at the fifth icon flashing, the graphic boot stops.
CTRL-ALT-F1 to come back to konsole-mode.
André
I have Wheezy with kernel from wheezy-backports == also 3.16.x
As I found out yesterday, immediately after previous restart, I did not show problem, but when I login the next day problem is back! (Machine is running continuously.)
It is positive that with this I have a machine where I can test this problem - reproducibility is pretty much 100% :)
Hello Andre,
On Tuesday 28 April 2015 14:53:36 andre_debian@numericable.fr wrote:
How to completely remove TDE-Trinity ?
Since I upgraded Debian to Jessie, I cannot start tde-trinity.
The boot-session "tdm-trinity", appears, I enter my login-user, my password, the desktop starts and at the fifth picture (with a pen) in the blue center area, it stops... impossible to go on !
I have the same problem ! However through trial n error, I have found that when I get to the login screen, if I put my password in and wait until the password disapears, then put the password back in then press enter, everything works as it should.
I did discover early on that if I switched to tty1 and logged in there it would often boot to the Trinity desktop, but I soon discovered that many things did not work ! It was as though a file that set up my desktop was not being read. I could still surf the net and Email worked but little else.
So, if you have an idea about this break, otherwise I have to re-install all the tde-trinity from new.
Can "systemd" be responsible ?
I don't know anything about that :-( sorry
Hope this helps.
Thanks.
André