Hi,
How is it possible to configure TDM / TDE so that it does allow any user
to have more than one session? TDM/Trinity after update to R14, will
actually start a second session but the first goes looked.
Example:
On server logged as supervisor, then on thinstation too, on server goes
the session locked.
on .xsession-errors
[tdecore] Deleting stale lockfile /tmp/tde-supervisor/kdesktop_lock_lockfile
TQThreadInstance::start: Setting thread storage to 0xcff130
[tdecore] Deleting stale lockfile /tmp/tde-supervisor/kdesktop_lock_lockfile
TQThreadInstance::start: Setting thread storage to 0x92ccc0
[tdecore] Deleting stale lockfile /tmp/tde-supervisor/kdesktop_lock_lockfile
TQThreadInstance::start: Setting thread storage to 0x176a220
[tdecore] Deleting stale lockfile /tmp/tde-supervisor/kdesktop_lock_lockfile
TQThreadInstance::start: Setting thread storage to 0x25b0130
[tdecore] Deleting stale lockfile /tmp/tde-supervisor/kdesktop_lock_lockfile
TQThreadInstance::start: Setting thread storage to 0x1317e30
[tdecore] Deleting stale lockfile /tmp/tde-supervisor/kdesktop_lock_lockfile
TQThreadInstance::start: Setting thread storage to 0x22511b0
[tdecore] Deleting stale lockfile /tmp/tde-supervisor/kdesktop_lock_lockfile
TQThreadInstance::start: Setting thread storage to 0x1e2e000
[tdecore] Deleting stale lockfile /tmp/tde-supervisor/kdesktop_lock_lockfile
TQThreadInstance::start: Setting thread storage to 0x155a100
[tdecore] Deleting stale lockfile /tmp/tde-supervisor/kdesktop_lock_lockfile
TQThreadInstance::start: Setting thread storage to 0x806130
[tdecore] Deleting stale lockfile /tmp/tde-supervisor/kdesktop_lock_lockfile
TQThreadInstance::start: Setting thread storage to 0x25d0080
[tdecore] Deleting stale lockfile /tmp/tde-supervisor/kdesktop_lock_lockfile
TQThreadInstance::start: Setting thread storage to 0x1771300
Thanks,
If I try to run konqueror (or kdirstat as another example) I get the window
ok, but it doesn't respond at all.
kmail and konsole work fine, though.
kfmclient openURL file:///etc/hostname
shows the hostname, but then freezes
Hitting the 'x' button I get a dialogue box with
Warning - TWin
Window with title "Konqueror" is not responding......
Using Trinity R14.0.0 with
Linux vega1 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt2-1 (2014-12-08) x86_64
GNU/Linux
Anyone else seen this, or have any ideas on how to diagnose the problem?
cheers
ant
--
Sent from my linux system running Debian 8, desktop Trinity R14
This email is plain text, not HTML. Any attachments are either .jpg or .pdf
this is new. just went to print a DVD label with the lacie lightscribe
software, which has always worked heretofore, though this was the first
time i've used it since upgrading to R14. clicking the buttons is
problematic -- because the buttons can't be seen; the whole thing is black
per the attached window shot.
ideas as to a fix? the application offers no controls for coloration, and
it worked fine on the last release version of TDE.
--
dep
The shortest distance between you and playing great acoustic guitar:
the great new instructional DVDs from Marjorie Thompson,
available at www.MarjorieThompson.com
Hi,
I installed in a qemu-kvm a minimal wheezy:amd64 (whith absolutly no
additional package), dist-upgrade to jessie:amd64 and the following packages
(without any suggests):
xserver-xorg-video-qxl xserver-xorg-video-vmware spice-vdagent dbus psmisc
bzip2 unzip locales file ca-certificates pmount xorg tdebase-trinity
desktop-base-trinity twin-trinity tdm-trinity tde-i18n-de-trinity
knotes-trinity kcalc-trinity xterm
After a reboot everything went fine, but after logout as normal user, qemu-kvm
dies with the message "5416 Speicherzugriffsfehler"
The VM is started with the additional options
-soundhw ac97 -vga qxl -device virtio-serial-pci \
-device virtserialport,chardev=spicechannel0,name=com.redhat.spice.0\
-chardev spicevmc,id=spicechannel0,name=vdagent \
-spice port=${SPICEPORT},addr=${HOST},disable-ticketing
I can not decide, if it is a problem of the qxl-videoserver (optimized for the
spice-protocol) or something inside of Trinity.
Fine regards
Rolf
Alexandre wrote:
>> On Saturday 10 January 2015 14:29:32 Dave wrote:
>> > Does the Raspberry Pi version have TDM, or are we stuck with
>> > lightdm?
> But, try tdm-trinity or tdm as a name, instead of lightdm.
Probably dumb questions, but what is a display manager needed (VS
used) for, and what are the relative merits (lightdm VS tdm)? I don't
seem to have any DM's installed. If lightdm uses less system
resources, does it follow that not using a DM uses even less?
Hi,
I installed trinity r14 on an openSuse 13.2 system using the repositories:
http://tde-mirror.yosemite.net/trinity/trinity/rpm/opensuse13.2/trinity-r14…http://tde-mirror.yosemite.net/trinity/trinity/rpm/opensuse13.2/trinity-r14…
this works very well!
but when I tried to run a python script I got the following:
kof@rzbn0052:~> python
Python 2.7.8 (default, Sep 30 2014, 15:34:38) [GCC] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import Tkinter
>>> master = Tkinter.Tk()
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/lib64/python2.7/lib-tk/Tkinter.py", line 1764, in __init__
self.tk = _tkinter.create(screenName, baseName, className,
interactive, wantobjects, useTk, sync, use)
_tkinter.TclError: unknown color name "BACKGROUND"
>>>
before the trinity installation it worked.
any idea?
sume system information:
kof@rzbn0052:->uname -a
Linux rzbn0052 3.16.7-7-desktop #1 SMP PREEMPT Wed Dec 17 18:00:44 UTC
2014 (762f27a) x86_64 x86_64 x86_64 GNU/Linux
kof@rzbn0052:->cat /etc/os-release
NAME=openSUSE
VERSION="13.2 (Harlequin)"
VERSION_ID="13.2"
PRETTY_NAME="openSUSE 13.2 (Harlequin) (x86_64)"
ID=opensuse
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:opensuse:13.2"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://opensuse.org/"
ID_LIKE="suse"
Regards
Wolfgang
--
Wolfgang Schönfeld
Helmholtz Center Geesthacht
Institute of Coastal Research
Max-Planck-Str. 1
21502 Geesthacht
Germany
Phone: +49 4152 87 1576
Fax: +49 4152 87 1596
Helmholtz-Zentrum Geesthacht
Zentrum für Material- und Küstenforschung GmbH
Max-Planck-Straße 1 I 21502 Geesthacht I Deutschland/Germany
Geschäftsführer/Board of Management: Prof. Dr. Wolfgang Kaysser, Dipl.-Ing. Michael Ganß
Vorsitzender des Aufsichtsrates/Chairman of the Supervisory Board: MinDirig Wilfried Kraus
Amtsgericht Lübeck HRB 285 GE (Register Court)
Internet: http://www.hzg.de
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224
> I'm not sure what that means, but there is is. I'll sign up for an
> account on
> your bug tracker and post more there later, thank you.
Thanks for that! Unfortunately the interesting part of the backtrace is
not shown; you will need to press Return when prompted until you are
dumped back at the (gdb) prompt then post the entire text block that gdb
spat out.
Also, on looking closer it seems that we did not build a debug symbols
package for kpilot-trinity. I am fixing that right now, but testing would
require you to update kpilot-trinity to the latest nightly builds and
install the new kpilot-trinity-dbg package (once it builds that is!). Is
this an option?
> Where can I find the full build log?
Just set Konsole or similar to an unlimited line history, then issue the
dpkg-buildpackage command against a freshly downloaded pacakge and wait
for the error. Copy everything after the dpkg-buildpackage command
(including the command itself) into a new text file and attach that file
to a reply message. :-)
Tim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iFYEARELAAYFAlSvOLwACgkQLaxZSoRZrGGQ0ADgs0eqygTmT6cgzHiJ9Gq9huBg
7gjRf3gXxZHaFwDdHlLr7FuI/xW4QH4bZ08PhotUp2E66WW24DTndw==
=JvIB
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224
All,
As you are probably already aware at around 13:20 GMT 01/07/2015 all TDE
services went offline. This was due to a widespread power outage; to make
matters worse the site's backup generator froze and did not start in time
due to the extreme cold in the area.
All services should now be restored, however as this was a full outage I
expect that there may be some remaining issues that I am not yet aware of.
Please let me know if you see anything still down or malfunctioning at
this point.
As always we need your support to stay online! If you can, please help
the project stay online: https://trinitydesktop.org/donate.php
Thank you for your patience!
Timothy Pearson
Trinity Desktop Project
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iFYEARELAAYFAlSuq1QACgkQLaxZSoRZrGERYQDggPrv0YSyas69nGVzfwAotR7K
WUq7+gMmfrphTgDfSkwKzjfUs/KHEmDElPemYuGb/Jw+FgzDIJgaOg==
=ADoJ
-----END PGP SIGNATURE-----
I use Ubuntu Precise with the R14.0.0 TDE desktop on an amd64 system. I tried to install k3b-trinity with apt-get install and then with apt-get -f install. I have never had problems beforehand installing new packages with apt-get.
The reply I get (in French) translates to something like :
+++++++++
Certain packages cannot be installed...
The following packages have unmet dependancies :
k3b-trinity :
Depend: libk3b3-trinity (= 4:14.0.0-r201-0ubuntu12.04.0+pr34) but 4:14.0.0-s-0ubuntu12.04.0+0 is to be installed
Depend: k3b-data-trinity (= 4:14.0.0-r201-0ubuntu12.04.0+pr34) but 4:14.0.0-s-0ubuntu12.04.0+0 is to be installed
E: Impossible to correct problems, the defective paquages are in « garder en l'état » mode.
++++++++
My understanding (am i correct?) is that k3b-trinity depends on 2 packages older than what I have on my computer (I checked). So what can i do to install k3b so that I can burn a new tde-live-disk for my "new" hand-me-down laptop?
Thanks in advance.
Marc