Went for it, upgrades main workstation,,whew... a couple of issues.
Wheezy amd64, TDE 3.5.13.2 > http://mirror.xcer.cz/trinity-sb/dists/wheezy/deps-r14
I used 'apt-get dist-upgrade', went without a hitch.
Issue: when I log in, a dialog box pops up for a locked session, need password. I get from 3-6 of these dialogs on each login, I usually do not shut my box down..minor anoyance , definately not locked sessions, or screensavers... would like to know how to get rid of these.
I use the 'adept-notifier' icon in the system tray. The icon no longer, it used to, changes to green after a update. A restart of the session will remedy this, do not want shut everything down to fix issues with desktops.
Love kdepim..it is the app that keeps me hooked on Trinity, not feeling the love for kpdf & gwenview.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
Went for it, upgrades main workstation,,whew... a couple of issues.
Wheezy amd64, TDE 3.5.13.2 > http://mirror.xcer.cz/trinity-sb/dists/wheezy/deps-r14
I used 'apt-get dist-upgrade', went without a hitch.
Issue: when I log in, a dialog box pops up for a locked session, need password. I get from 3-6 of these dialogs on each login, I usually do not shut my box down..minor anoyance , definately not locked sessions, or screensavers... would like to know how to get rid of these.
I use the 'adept-notifier' icon in the system tray. The icon no longer, it used to, changes to green after a update. A restart of the session will remedy this, do not want shut everything down to fix issues with desktops.
Love kdepim..it is the app that keeps me hooked on Trinity, not feeling the love for kpdf & gwenview.
-- Peace,
Greg
Out of curiosity, what don't you like about kpdf and gwenview? My biggest beefs with kpdf are the lack of proper bookmarks and lack of fillable forms support.
Tim
On Thursday 07 August 2014 10:28:37 you wrote:
Went for it, upgrades main workstation,,whew... a couple of issues.
Wheezy amd64, TDE 3.5.13.2 > http://mirror.xcer.cz/trinity-sb/dists/wheezy/deps-r14
I used 'apt-get dist-upgrade', went without a hitch.
Issue: when I log in, a dialog box pops up for a locked session, need password. I get from 3-6 of these dialogs on each login, I usually do not shut my box down..minor anoyance , definately not locked sessions, or screensavers... would like to know how to get rid of these.
I use the 'adept-notifier' icon in the system tray. The icon no longer, it used to, changes to green after a update. A restart of the session will remedy this, do not want shut everything down to fix issues with desktops.
Love kdepim..it is the app that keeps me hooked on Trinity, not feeling the love for kpdf & gwenview.
-- Peace,
Greg
Out of curiosity, what don't you like about kpdf and gwenview? My biggest beefs with kpdf are the lack of proper bookmarks and lack of fillable forms support.
Tim
I have filed or commented bugs on both.
KPDF does not print 11x17 (ledger or tabloid), from a 22x34 original.
Gwenview uses all memory (8GB) viewing a folder of .tiff files, sizes from 200K to 950K.
tiff & pdf are the most common way (here) to distribute construction drawings, 22x34, electronically.
Problematic here, I like the apps, but other apps work fine...just means having more software & libraries installled.. not a functional issue just not the as clean as I 'used' to like.
Dne čt 7. srpna 2014 Greg Madden napsal(a):
I use the 'adept-notifier' icon in the system tray. The icon no longer, it used to, changes to green after a update. A restart of the session will remedy this, do not want shut everything down to fix issues with desktops.
True, that I also noticed this on my test machine. I think that this is related to commit d69942a0 (adept).
Dne čt 7. srpna 2014 Greg Madden napsal(a):
Issue: when I log in, a dialog box pops up for a locked session, need password. I get from 3-6 of these dialogs on each login, I usually do not shut my box down..minor anoyance , definately not locked sessions, or screensavers... would like to know how to get rid of these.
That is strange. Something like this I never noticed. Is there anything interesting in .xsession-errors?
On Tuesday 12 August 2014 06:51:20 you wrote:
Dne čt 7. srpna 2014 Greg Madden napsal(a):
Issue: when I log in, a dialog box pops up for a locked session, need password. I get from 3-6 of these dialogs on each login, I usually do not shut my box down..minor anoyance , definately not locked sessions, or screensavers... would like to know how to get rid of these.
That is strange. Something like this I never noticed. Is there anything interesting in .xsession-errors?
My home directory is a separte hard drive, it is been reused on updates or from backus sinceat least 2004. It has quite abit of old config info, some xsession-errors are related to this. My testing of TDE in vm's do not have any issues
I will try cleaning up my home dir first, thanks for your reponse.
My home directory is a separte hard drive, it is been reused on updates or from backus sinceat least 2004. It has quite abit of old config info, some xsession-errors are related to this. My testing of TDE in vm's do not have any issues I will try cleaning up my home dir first, thanks for your reponse.
As a quick test, you can try creating a new account and make sure that you have no issue with it. If that is the case, the problem is almost surely related to some old stuff/config still present in your home folder.
Cheers Michele
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
My home directory is a separte hard drive, it is been reused on updates or from backus sinceat least 2004. It has quite abit of old config info, some xsession-errors are related to this. My testing of TDE in vm's do not have any issues I will try cleaning up my home dir first, thanks for your reponse.
As a quick test, you can try creating a new account and make sure that you have no issue with it. If that is the case, the problem is almost surely related to some old stuff/config still present in your home folder.
Cheers Michele
And if you do manage to find the offending file I'd like to figure out what happened so that we can prevent it occurring for anyone else!
Tim
On Tuesday 12 August 2014 20:25:44 you wrote:
My home directory is a separte hard drive, it is been reused on updates or from backus sinceat least 2004. It has quite abit of old config info, some xsession-errors are related to this. My testing of TDE in vm's do not have any issues I will try cleaning up my home dir first, thanks for your reponse.
As a quick test, you can try creating a new account and make sure that you have no issue with it. If that is the case, the problem is almost surely related to some old stuff/config still present in your home folder.
Cheers Michele
And if you do manage to find the offending file I'd like to figure out what happened so that we can prevent it occurring for anyone else!
Tim
I created a new user, I have enclosed a pristine (new user) .xsession-errors file. snipped for all the lockfile entries.
I still get the locked session dialog, lots for the new user...on one login attempt I never got an unlocked session to use.
New issues 1. the new user does not have 'opt/trinity/bin' or other TDE specific entries in PATH ? I use 'adduser' (cli) to create users on my system. 2. Dual monitor, no panel on one of the monitors
Xsession: X session started for debian at Wed Aug 13 15:26:23 AKDT 2014 localuser:debian being added to access control list [starttde] Starting starttde. [starttde] This script is /usr/bin/x-session-manager [starttde] TDE version is R14.0.0 [DEVELOPMENT] [starttde] TDE base directory is /opt/trinity [starttde] TDEHOME is not set. [starttde] Set TDEHOME to /home/debian/.trinity. [starttde] Setting TDEROOTHOME to /root/.trinity. [starttde] XDG_DATA_DIRS: /opt/trinity/share:/usr/local/share:/usr/share [starttde] TDEDIR: /opt/trinity [starttde] TDEDIRS: [starttde] Starting Trinity... [tdebuildsycoca] tdebuildsycoca running... [dcopserver] DCOP Cleaning up dead connections. [starttde] TDE_FULL_SESSION: true [starttde] TDE_SESSION_UID: 1003 [tdeinit] Shutting down running client. --------------------------------- [dcopserver] It looks like dcopserver is already running. If you are sure that it is not already running, remove /home/debian/.DCOPserver_tdewheezy__0 and start dcopserver again. --------------------------------- [kded] Daemon (kded) is already running. [tdebuildsycoca] tdebuildsycoca running... [tdebuildsycoca] Reusing existing tdesycoca. tdeio (KService*): WARNING: The desktop entry file /usr/share/applications/usbview.desktop has Type=Applications/System/Hardware instead of "Application" or "Service" tdeio (KService*): WARNING: Invalid Service : /usr/share/applications/usbview.desktop [dcopserver] DCOP Cleaning up dead connections. [starttde] tdeinit started successfully. [tdecore] Deleting stale lockfile /tmp/tde-debian/kdesktop_lock_lockfile [tdecore] Deleting stale lockfile /tmp/tde-debian/kdesktop_lock_lockfile [tdecore] Deleting stale lockfile /tmp/tde-debian/kdesktop_lock_lockfile [kdesktop] SAK driven secure dialog is not available for use (retcode 6). Check tdmtsak for proper functionality. [kdesktop] SAK driven secure dialog is not available for use (retcode 6). Check tdmtsak for proper functionality. [tdecore] Deleting stale lockfile /tmp/tde-debian/kdesktop_lock_lockfile [tdecore] Deleting stale lockfile /tmp/tde-debian/kdesktop_lock_lockfile [tdecore] Deleting stale lockfile /tmp/tde-debian/kdesktop_lock_lockfile [tdecore] Deleting stale lockfile /tmp/tde-debian/kdesktop_lock_lockfile tdeio (TDEIOConnection): ERROR: Could not write data (pid 5154 process "nit] media /tmp/tdesocket-debian/tdelauncher9oiZU") [tdecore] Deleting stale lockfile /tmp/tde-debian/kdesktop_lock_lockfile
<snipped ~ 200 deleting lockfile lines>
SAK is not enabled in Contro Center
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
On Tuesday 12 August 2014 20:25:44 you wrote:
My home directory is a separte hard drive, it is been reused on updates or from backus sinceat least 2004. It has quite abit of old config info, some xsession-errors are related to this. My testing of TDE in vm's do not have any issues I will try cleaning up my home dir first, thanks for your reponse.
As a quick test, you can try creating a new account and make sure that you have no issue with it. If that is the case, the problem is almost surely related to some old stuff/config still present in your home folder.
Cheers Michele
And if you do manage to find the offending file I'd like to figure out what happened so that we can prevent it occurring for anyone else!
Tim
I created a new user, I have enclosed a pristine (new user) .xsession-errors file. snipped for all the lockfile entries.
I still get the locked session dialog, lots for the new user...on one login attempt I never got an unlocked session to use.
New issues
- the new user does not have 'opt/trinity/bin' or other TDE
specific entries in PATH ? I use 'adduser' (cli) to create users on my system. 2. Dual monitor, no panel on one of the monitors
Xsession: X session started for debian at Wed Aug 13 15:26:23 AKDT 2014 localuser:debian being added to access control list [starttde] Starting starttde. [starttde] This script is /usr/bin/x-session-manager [starttde] TDE version is R14.0.0 [DEVELOPMENT] [starttde] TDE base directory is /opt/trinity [starttde] TDEHOME is not set. [starttde] Set TDEHOME to /home/debian/.trinity. [starttde] Setting TDEROOTHOME to /root/.trinity. [starttde] XDG_DATA_DIRS: /opt/trinity/share:/usr/local/share:/usr/share [starttde] TDEDIR: /opt/trinity [starttde] TDEDIRS: [starttde] Starting Trinity... [tdebuildsycoca] tdebuildsycoca running... [dcopserver] DCOP Cleaning up dead connections. [starttde] TDE_FULL_SESSION: true [starttde] TDE_SESSION_UID: 1003 [tdeinit] Shutting down running client.
[dcopserver] It looks like dcopserver is already running. If you are sure that it is not already running, remove /home/debian/.DCOPserver_tdewheezy__0 and start dcopserver again.
[kded] Daemon (kded) is already running. [tdebuildsycoca] tdebuildsycoca running... [tdebuildsycoca] Reusing existing tdesycoca. tdeio (KService*): WARNING: The desktop entry file /usr/share/applications/usbview.desktop has Type=Applications/System/Hardware instead of "Application" or "Service" tdeio (KService*): WARNING: Invalid Service : /usr/share/applications/usbview.desktop [dcopserver] DCOP Cleaning up dead connections. [starttde] tdeinit started successfully. [tdecore] Deleting stale lockfile /tmp/tde-debian/kdesktop_lock_lockfile [tdecore] Deleting stale lockfile /tmp/tde-debian/kdesktop_lock_lockfile [tdecore] Deleting stale lockfile /tmp/tde-debian/kdesktop_lock_lockfile [kdesktop] SAK driven secure dialog is not available for use (retcode 6). Check tdmtsak for proper functionality. [kdesktop] SAK driven secure dialog is not available for use (retcode 6). Check tdmtsak for proper functionality. [tdecore] Deleting stale lockfile /tmp/tde-debian/kdesktop_lock_lockfile [tdecore] Deleting stale lockfile /tmp/tde-debian/kdesktop_lock_lockfile [tdecore] Deleting stale lockfile /tmp/tde-debian/kdesktop_lock_lockfile [tdecore] Deleting stale lockfile /tmp/tde-debian/kdesktop_lock_lockfile tdeio (TDEIOConnection): ERROR: Could not write data (pid 5154 process "nit] media /tmp/tdesocket-debian/tdelauncher9oiZU") [tdecore] Deleting stale lockfile /tmp/tde-debian/kdesktop_lock_lockfile
<snipped ~ 200 deleting lockfile lines>
SAK is not enabled in Contro Center
-- Peace,
Greg
Very strange; it looks like the kdesktop_lock process is continuously restarting. I have never encountered anything remotely like this.
Are you certain kdesktop and kdesktop_lock are the latest R14 versions? If there is an old 3.5.13.2 or lower kdesktop_lock executable in your path it might theoretically be able to do something like this.
Tim
On Thursday 14 of August 2014 20:11:17 Timothy Pearson wrote:
On Tuesday 12 August 2014 20:25:44 you wrote:
My home directory is a separte hard drive, it is been reused on updates or from backus sinceat least 2004. It has quite abit of old config info, some xsession-errors are related to this. My testing of TDE in vm's do not have any issues I will try cleaning up my home dir first, thanks for your reponse.
As a quick test, you can try creating a new account and make sure that you have no issue with it. If that is the case, the problem is almost surely related to some old stuff/config still present in your home folder.
Cheers Michele
And if you do manage to find the offending file I'd like to figure out what happened so that we can prevent it occurring for anyone else!
Tim
I created a new user, I have enclosed a pristine (new user) .xsession-errors file. snipped for all the lockfile entries.
I still get the locked session dialog, lots for the new user...on one login attempt I never got an unlocked session to use.
New issues
- the new user does not have 'opt/trinity/bin' or other TDE
specific entries in PATH ? I use 'adduser' (cli) to create users on my system. 2. Dual monitor, no panel on one of the monitors
Xsession: X session started for debian at Wed Aug 13 15:26:23 AKDT 2014 localuser:debian being added to access control list [starttde] Starting starttde. [starttde] This script is /usr/bin/x-session-manager [starttde] TDE version is R14.0.0 [DEVELOPMENT] [starttde] TDE base directory is /opt/trinity [starttde] TDEHOME is not set. [starttde] Set TDEHOME to /home/debian/.trinity. [starttde] Setting TDEROOTHOME to /root/.trinity. [starttde] XDG_DATA_DIRS: /opt/trinity/share:/usr/local/share:/usr/share [starttde] TDEDIR: /opt/trinity [starttde] TDEDIRS: [starttde] Starting Trinity... [tdebuildsycoca] tdebuildsycoca running... [dcopserver] DCOP Cleaning up dead connections. [starttde] TDE_FULL_SESSION: true [starttde] TDE_SESSION_UID: 1003 [tdeinit] Shutting down running client.
[dcopserver] It looks like dcopserver is already running. If you are sure that it is not already running, remove /home/debian/.DCOPserver_tdewheezy__0 and start dcopserver again.
[kded] Daemon (kded) is already running. [tdebuildsycoca] tdebuildsycoca running... [tdebuildsycoca] Reusing existing tdesycoca. tdeio (KService*): WARNING: The desktop entry file /usr/share/applications/usbview.desktop has Type=Applications/System/Hardware instead of "Application" or "Service" tdeio (KService*): WARNING: Invalid Service : /usr/share/applications/usbview.desktop [dcopserver] DCOP Cleaning up dead connections. [starttde] tdeinit started successfully. [tdecore] Deleting stale lockfile /tmp/tde-debian/kdesktop_lock_lockfile [tdecore] Deleting stale lockfile /tmp/tde-debian/kdesktop_lock_lockfile [tdecore] Deleting stale lockfile /tmp/tde-debian/kdesktop_lock_lockfile [kdesktop] SAK driven secure dialog is not available for use (retcode 6). Check tdmtsak for proper functionality. [kdesktop] SAK driven secure dialog is not available for use (retcode 6). Check tdmtsak for proper functionality. [tdecore] Deleting stale lockfile /tmp/tde-debian/kdesktop_lock_lockfile [tdecore] Deleting stale lockfile /tmp/tde-debian/kdesktop_lock_lockfile [tdecore] Deleting stale lockfile /tmp/tde-debian/kdesktop_lock_lockfile [tdecore] Deleting stale lockfile /tmp/tde-debian/kdesktop_lock_lockfile tdeio (TDEIOConnection): ERROR: Could not write data (pid 5154 process "nit] media /tmp/tdesocket-debian/tdelauncher9oiZU") [tdecore] Deleting stale lockfile /tmp/tde-debian/kdesktop_lock_lockfile
<snipped ~ 200 deleting lockfile lines>
SAK is not enabled in Contro Center
-- Peace,
Greg
Very strange; it looks like the kdesktop_lock process is continuously restarting. I have never encountered anything remotely like this.
Are you certain kdesktop and kdesktop_lock are the latest R14 versions? If there is an old 3.5.13.2 or lower kdesktop_lock executable in your path it might theoretically be able to do something like this.
Tim
Greg, can you post your apt sources.list?
On Thursday 14 August 2014 10:23:30 am you wrote:
On Thursday 14 of August 2014 20:11:17 Timothy Pearson wrote:
On Tuesday 12 August 2014 20:25:44 you wrote:
My home directory is a separte hard drive, it is been reused on updates or from backus sinceat least 2004. It has quite abit of old config info, some xsession-errors are related to this. My testing of TDE in vm's do not have any issues I will try cleaning up my home dir first, thanks for your reponse.
As a quick test, you can try creating a new account and make sure that you have no issue with it. If that is the case, the problem is almost surely related to some old stuff/config still present in your home folder.
Cheers Michele
And if you do manage to find the offending file I'd like to figure out what happened so that we can prevent it occurring for anyone else!
Tim
I created a new user, I have enclosed a pristine (new user) .xsession-errors file. snipped for all the lockfile entries.
I still get the locked session dialog, lots for the new user...on one login attempt I never got an unlocked session to use.
New issues
- the new user does not have 'opt/trinity/bin' or other TDE
specific entries in PATH ? I use 'adduser' (cli) to create users on my system. 2. Dual monitor, no panel on one of the monitors
Xsession: X session started for debian at Wed Aug 13 15:26:23 AKDT 2014 localuser:debian being added to access control list [starttde] Starting starttde. [starttde] This script is /usr/bin/x-session-manager [starttde] TDE version is R14.0.0 [DEVELOPMENT] [starttde] TDE base directory is /opt/trinity [starttde] TDEHOME is not set. [starttde] Set TDEHOME to /home/debian/.trinity. [starttde] Setting TDEROOTHOME to /root/.trinity. [starttde] XDG_DATA_DIRS: /opt/trinity/share:/usr/local/share:/usr/share [starttde] TDEDIR: /opt/trinity [starttde] TDEDIRS: [starttde] Starting Trinity... [tdebuildsycoca] tdebuildsycoca running... [dcopserver] DCOP Cleaning up dead connections. [starttde] TDE_FULL_SESSION: true [starttde] TDE_SESSION_UID: 1003 [tdeinit] Shutting down running client.
[dcopserver] It looks like dcopserver is already running. If you are sure that it is not already running, remove /home/debian/.DCOPserver_tdewheezy__0 and start dcopserver again.
[kded] Daemon (kded) is already running. [tdebuildsycoca] tdebuildsycoca running... [tdebuildsycoca] Reusing existing tdesycoca. tdeio (KService*): WARNING: The desktop entry file /usr/share/applications/usbview.desktop has Type=Applications/System/Hardware instead of "Application" or "Service" tdeio (KService*): WARNING: Invalid Service : /usr/share/applications/usbview.desktop [dcopserver] DCOP Cleaning up dead connections. [starttde] tdeinit started successfully. [tdecore] Deleting stale lockfile /tmp/tde-debian/kdesktop_lock_lockfile [tdecore] Deleting stale lockfile /tmp/tde-debian/kdesktop_lock_lockfile [tdecore] Deleting stale lockfile /tmp/tde-debian/kdesktop_lock_lockfile [kdesktop] SAK driven secure dialog is not available for use (retcode 6). Check tdmtsak for proper functionality. [kdesktop] SAK driven secure dialog is not available for use (retcode 6). Check tdmtsak for proper functionality. [tdecore] Deleting stale lockfile /tmp/tde-debian/kdesktop_lock_lockfile [tdecore] Deleting stale lockfile /tmp/tde-debian/kdesktop_lock_lockfile [tdecore] Deleting stale lockfile /tmp/tde-debian/kdesktop_lock_lockfile [tdecore] Deleting stale lockfile /tmp/tde-debian/kdesktop_lock_lockfile tdeio (TDEIOConnection): ERROR: Could not write data (pid 5154 process "nit] media /tmp/tdesocket-debian/tdelauncher9oiZU") [tdecore] Deleting stale lockfile /tmp/tde-debian/kdesktop_lock_lockfile
<snipped ~ 200 deleting lockfile lines>
SAK is not enabled in Contro Center
-- Peace,
Greg
Very strange; it looks like the kdesktop_lock process is continuously restarting. I have never encountered anything remotely like this.
Are you certain kdesktop and kdesktop_lock are the latest R14 versions? If there is an old 3.5.13.2 or lower kdesktop_lock executable in your path it might theoretically be able to do something like this.
Tim
Greg, can you post your apt sources.list?
sources.lis, I have a partial, amd64, i386, Debian mirror..updated daily.
I have checked all the TDE installed packages, they are the appropriate versions.
It seems the saved session feature may be part of the problem. I have dual monitors and 6 desktops per monitor, Session saved does not work, bring up saved app on appropriate desktop, 100%...varies. The locked session dialog appears when I try to use a desktop..start an app, click to focus.
deb http://192.168.0.4/debian/ wheezy main contrib non-free #deb http://192.168.0.4/debian/ jessie main contrib non-free #deb http://debian.osuosl.org/debian/ wheezy main contrib non-free #deb http://http.debian.net/debian stable main contrib non-free deb http://http.debian.net/debian/ wheezy-backports main contrib non-free deb http://security.debian.org/ wheezy/updates main contrib non-free deb http://mirror.xcer.cz/trinity-sb wheezy deps-r14 main-r14
On Thursday 14 August 2014 10:11:17 am you wrote:
And if you do manage to find the offending file I'd like to figure out what happened so that we can prevent it occurring for anyone else!
Tim
snip
Very strange; it looks like the kdesktop_lock process is continuously restarting. I have never encountered anything remotely like this.
Are you certain kdesktop and kdesktop_lock are the latest R14 versions? If there is an old 3.5.13.2 or lower kdesktop_lock executable in your path it might theoretically be able to do something like this.
Tim
Never found an answer, the kdesktop_lock was so annoying, even dropping back to the login screen again.
I removed all *-trinity packages, + 'rm -R /opt/trinity' ..whatever was left there, removed anything remotly associated wit TDE, tqt3*? stuff.
Re-installed and it works ! I enclosed my current .xsession-errors file, much cleaner..a few comments I don't see when running Wmaker, which I had to use to sort this thing out..yea for WM.
It sems it was a failed upgrade, all the packages were R14 versions but something in /opt/trinity or /etc ?
Thanks for all the comments.
[dcopserver] It looks like dcopserver is already running. If you are sure that it is not already running, remove /home/pabi/.DCOPserver_tdewheezy__0 and start dcopserver again. --------------------------------- [kded] Daemon (kded) is already running. [tdebuildsycoca] tdebuildsycoca running... [tdebuildsycoca] Reusing existing tdesycoca. [dcopserver] DCOP Cleaning up dead connections. [starttde] tdeinit started successfully. [kdesktop] SAK driven secure dialog is not available for use (retcode 6). Check tdmtsak for proper functionality. [tdecore] Deleting stale lockfile /tmp/tde-pabi/kdesktop_lock_lockfile [tdecore] Deleting stale lockfile /tmp/tde-pabi/kdesktop_lock_lockfile [tdecore] Deleting stale lockfile /tmp/tde-pabi/kdesktop_lock_lockfile [tdecore] Deleting stale lockfile /tmp/tde-pabi/kdesktop_lock_lockfile [kdesktop] SAK driven secure dialog is not available for use (retcode 6). Check tdmtsak for proper functionality. tdeio (TDEIOConnection): ERROR: Could not write data (pid 15589 process "nit] media /tmp/tdesocket-pabi/tdelauncherSfEROM.") [tdeinit] Could not find 'tdewalletmanager' executable.
On Wednesday 10 September 2014 08:03:05 pm you wrote:
On Thursday 14 August 2014 10:11:17 am you wrote:
And if you do manage to find the offending file I'd like to figure out what happened so that we can prevent it occurring for anyone else!
Tim
snip
Very strange; it looks like the kdesktop_lock process is continuously restarting. I have never encountered anything remotely like this.
Are you certain kdesktop and kdesktop_lock are the latest R14 versions? If there is an old 3.5.13.2 or lower kdesktop_lock executable in your path it might theoretically be able to do something like this.
Tim
Never found an answer, the kdesktop_lock was so annoying, even dropping back to the login screen again.
I removed all *-trinity packages, + 'rm -R /opt/trinity' ..whatever was left there, removed anything remotly associated wit TDE, tqt3*? stuff.
Re-installed and it works ! I enclosed my current .xsession-errors file, much cleaner..a few comments I don't see when running Wmaker, which I had to use to sort this thing out..yea for WM.
It sems it was a failed upgrade, all the packages were R14 versions but something in /opt/trinity or /etc ?
Thanks for all the comments.
[dcopserver] It looks like dcopserver is already running. If you are sure that it is not already running, remove /home/pabi/.DCOPserver_tdewheezy__0 and start dcopserver again.
[kded] Daemon (kded) is already running. [tdebuildsycoca] tdebuildsycoca running... [tdebuildsycoca] Reusing existing tdesycoca. [dcopserver] DCOP Cleaning up dead connections. [starttde] tdeinit started successfully. [kdesktop] SAK driven secure dialog is not available for use (retcode 6). Check tdmtsak for proper functionality. [tdecore] Deleting stale lockfile /tmp/tde-pabi/kdesktop_lock_lockfile [tdecore] Deleting stale lockfile /tmp/tde-pabi/kdesktop_lock_lockfile [tdecore] Deleting stale lockfile /tmp/tde-pabi/kdesktop_lock_lockfile [tdecore] Deleting stale lockfile /tmp/tde-pabi/kdesktop_lock_lockfile [kdesktop] SAK driven secure dialog is not available for use (retcode 6). Check tdmtsak for proper functionality. tdeio (TDEIOConnection): ERROR: Could not write data (pid 15589 process "nit] media /tmp/tdesocket-pabi/tdelauncherSfEROM.") [tdeinit] Could not find 'tdewalletmanager' executable.
A followup re failed upgrade.After I 'purged' all trinity packages I had an /opt/trinity dir left, I failed to look inside for content but I removed it maually.
On another test rmoving/purge of trinity I noticed the '/opt/trinity' dir gets removed...removal is what I would expect..not sure why it was not on my workstation. On my latest test '/etc/trinity/tdm/backgroundrc' was the only thing left in /etc/trinity..which I would expect /etc/trinity to be removed also in a purge..Debians package management.
Only thing I learned from this is testing in virtualization is not an absolute indicator of what will happen on my workstatio..just more fiddling.