On Sunday 21 February 2016 01.41:18 Glen Cunningham wrote:
> Reply to my own post for the archives.
>
> On Sunday 21 February 2016 09:38:25 Glen Cunningham wrote:
> > Thanks for the try, Nik,
> >
> > On Sunday 21 February 2016 03:39:15 Dr. Nikolaus Klepp wrote:
> > > Hi!
> > >
> > > It's that simple :-)
> >
> > NO! It is not that simple.
> >
(...)
>
> Laboriously copied the above 6 files/directories from .kde3 on the old
> box to .trinity on the new one.
> That did not work! Kmail failed to start.
> Deleted the 5 config files, restarted kmail, at least kmail started
> this time and my old mailboxes seem to have survived.
>
> There has gotta be a better way!
> Cheers,
> Glen
It should - almost - work the way Nik indicated.
There are possibly a few things to edit when you move to .trinity (but that
will be only once). Mainly, did you edit /.trinity/share/config/kmailrc ? In
the last part of the file (after the mailboxes), you have the path to your
mail directory.
In (very) old time this would have been ~/mail , but somwhere in KDE history
it was relocated to a ./kde3 subdirectory, usually
$HOME/.kde3/share/apps/kmail/mail. You must change that to
$HOME/.trinity/share/apps/kmail/mail
As far as I remember that's all I had to do (apart from copyinf the
directory).
Thierry
G'day Trinity Users,
At last I've found a tuit ( a round one) :-) Upgrading from
TDE 3.5.11 to Trinity R14.0.2. So far, I've got Ubuntu 14.04.4 with
Trinity R14.0.2 on another computer. My yellow-streak compells me to
leave the working TDE 3.5.11 system alone until the new box is properly
configured.
My main problem is transferring KMail settings and mailboxes to the
new system, so my questions are ....
1. Is it just a simple copy of the files from the old to the new
systems?
2. If this is possible, which files need to be copied? From where to
where? (Seems that paths and directories are very different on the two
systems).
FWIW. I tried searching the list archives but my search-foo is rather
low just now, but I found some references that suggest that what I want
to do is actually doable.
Thanks in antic,
Glen
PS. If anyone is interested, the "new" system is an Aldi Akoya E4214
which is not as yet well supported by Linux distros but eventually got
WiFi working with a custom compiled driver. G.
Anyone know how to get them to show in main menu sections they belong in
automatically instead of Lost & Found? (TDERandRTray and
Konsole-superusermode are there too.)
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
I have a CM devastator keyboard with back lighting. This keyboard uses the
scroll lock key to turn the light on and off. On my system running Ubuntu
under other desktop environments like Mate or KDE I can turn the back light
on using xset led 3 and I usually have it scripted to turn on after I log
in. Under Trinity doing xset led 3 causes the keyboard to flash really
quickly once and then the light goes off. Is there something holding the
keyboard under Trinity? Is there a way to use the back light?
--
John P
I went to check on the latest version of Alexandre's remaster for PCLinuxOS,
having the PCLinuxOS_no_TDE_remaster_5sept2015.iso already downloaded; but
the most recent on the TDE site is this one:
PCLinuxOS_no_remaster_2octobre2014.iso
Is there a problem with the newer one?
Lisi
Greetings everybody;
Everytime I have to reboot, but often, or more recently because of tdm
updates, restart tdm, I have had to find a shell and execute "alsactl
restore" before I have sound.
Is there a file that runs after my login, far enough after it, that I
could add that command to instead of figureing out "hey its awful quiet
in here" some time after the restart and reminds me to go and execute
it?
If I could figure out where in the restart the sound gets muted, I'd fix
it there. This has been a nearly 2 year long problem for me.
Thanks everybody.
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
This started after an update Friday. Get the login screen, system
accepts password, progress bar shows for about 1/3 of the way, then
get the dialog box about ksmserver crashing. I've done both "report
crash" and "create backtrace" both of which cycle me back to the login
screen.
I pull packages from here:
deb http://mirror.xcer.cz/trinity-sb trusty deps-r14 main-r14
Stuff I don't understand from the logs:
Feb 9 11:01:47 toto3 kernel: [ 0.008000] tsc: Marking TSC unstable
due to check_tsc_sync_source failed
Feb 9 11:01:47 toto3 kernel: [ 0.920132] ioapic: probe of
0000:00:05.4 failed with error -22
Feb 9 11:01:47 toto3 kernel: [ 4.348917] fglrx: module
verification failed: signature and/or required key missing - tainting
kernel
Feb 9 11:01:48 toto3 failsafe: Failsafe of 120 seconds reached.
Feb 9 11:02:01 toto3 kernel: [ 18.578714] init: failsafe main
process (1243) killed by TERM signal
[ 232.363] (EE) AIGLX error: failed to open
/usr/X11R6/lib64/modules/dri/fglrx_dri.so,
error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared
object file: No such file or directory]
[ 232.363] (EE) AIGLX error: failed to open
/usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot
open shared object file: No such file or directory]
[ 232.363] (EE) AIGLX error: failed to open
/usr/X11R6/lib/modules/dri/fglrx_dri.so,
error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared
object file: No such file or directory]
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu 14.04.3 LTS"
Welcome to Ubuntu 14.04.3 LTS (GNU/Linux 3.13.0-77-generic x86_64)
--
Peter Laws / N5UWY
National Weather Center / Network Operations Center
University of Oklahoma Information Technology
plaws(a)ou.edu
College of Architecture, Regional and City Planning, MRCP '16
Ign http://buildbot.linuxcnc.org wheezy/2.7-rtpreempt Translation-en_US
Ign http://buildbot.linuxcnc.org wheezy/2.7-rtpreempt Translation-en
Ign http://www.deb-multimedia.org wheezy/main Translation-en_US
Ign http://mozilla.debian.net wheezy-backports/iceweasel-release
Translation-en_US
Ign http://www.deb-multimedia.org wheezy/main Translation-en
Ign http://mozilla.debian.net wheezy-backports/iceweasel-release
Translation-en
Ign http://mirror.xcer.cz wheezy/deps-r14 Translation-en_US
Ign http://linuxcnc.org wheezy/2.6 Translation-en_US
Ign http://mirror.xcer.cz wheezy/deps-r14 Translation-en
Ign http://linuxcnc.org wheezy/2.6 Translation-en
Ign http://linuxcnc.org wheezy/2.7-uspace Translation-en_US
Ign http://mirror.xcer.cz wheezy/main-r14 Translation-en_US
Ign http://linuxcnc.org wheezy/2.7-uspace Translation-en
Ign http://mirror.xcer.cz wheezy/main-r14 Translation-en
Ign http://linuxcnc.org wheezy/base Translation-en_US
Ign http://linuxcnc.org wheezy/base Translation-en
So obviously I do not have the correct entry in the line for
mirror.xcer.cz wheezy in my sources.list or perhaps something in
preferences suffering from bitrot?
What is the correct sources.list line for staying current with all tde
r14 updates?
I did just now get 11 updates for the box on the mill, but none for this
box, which should have similar TDE installs. But I've been looking at a
red star for the update-manager status just to the left of the time-date
display for weeks, just on this machine, but if I "sudo apt-get update",
no errors are reported. But I just checked in /etc/apt/sources.list.d
and found several enpty or all commented out files and nuked them and
the red star is gone. Puzzling at best, like waiting for the other shoe
to drop.
Plausible explanation for a buglet? DIIK.
Thanks folks.
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
Hi all!
I just wanted to ask: is any news on porting TDE to *BSD?
Nik
--
Please do not email me anything that you are not comfortable also sharing with the NSA.
Greetings guru's;
This did work before the 51 tde updates yesterday:
gene@GO704:~/linuxcnc$ python python_opencv_camera_example_with_gui.py
Traceback (most recent call last):
File "python_opencv_camera_example_with_gui.py", line 278, in <module>
main()
File "python_opencv_camera_example_with_gui.py", line 222, in main
root = Tk()
File "/usr/lib/python2.7/lib-tk/Tkinter.py", line 1712, in __init__
self.tk = _tkinter.create(screenName, baseName, className,
interactive, wantobjects, useTk, sync, use)
_tkinter.TclError: unknown color name "BACKGROUND"
This has been a dog & pony show I have been to before, several times,
and each time IIRC the fix was different. Historically, if by playing
the 10,000 monkeys with typewriters scene long enough that I manage to
fix 'BACKGROUND' the FOREGROUND will be the next excuse used to exit a
formerly working script.
Does anyone have a clue what to fix this time?
Thanks everybody.
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>