Updated Squeeze/TDE live cd (unofficial) is available:
http://exe-linux.fastfishwebsolutions.com/trinity/
Included are all new Squeeze updates, local script updates with improved
Spanish translations and startkde patch (solves previous kdesu bugs)
Testers appreciated!
Hi,
I wannted fix Bug 690, so I installed daily snapshot from repository,
but I get several bigger problems (konqueror can run in file manager
mode, something like kdesktop fall during login...). Is daily build
supposed to be installable?
Thanks
Jiri Jansky
I have read, here, some users have various issues with 3.5.13. Here is mine.
I use Librreoffice 3.3.4 for my business, all my docs & templates are full page
tables, and multiple pages. One significant issue I have is the cut/copy> paste
function in tables does not work in a timely fashion. I select data in multiple
cells that I want to move or copy elswhere in the table/tables and it takes two
tries to accomplish this. The first try pastes the data into a single cell, I
have to repeat the select/cut/copy>paste process.. time consuming on a feature
that can really save time.
Now how is this a "TDE issue, not sure but two things stand out to me.
1. This is very pronounced since the upgrade from 3.5.12 > 3.5.13.
2. This sequence works fine in a Virtualbox instance of TDE 3.5.12 same LO ver.
I could just re-install 3.5.12 on my workstation, but before I do I wanted to
check other users issues, not 100% confidant the VB is an accurate test
environment, i.e. everything seems to work fine with the virtual hardware VB
uses, and it isn't a 100% identical software stack .
--
Peace,
Greg
Have to load Trinity on a new machine with Debian 6, with internet - no
problems. Also have to update some machines running deb 5 KDE where there is
no internet and have a identical machine with internet access. Update no
problems (reload with wad of DVD's), not sure how to load Trinity
My linux/unix knowledge is not good although have used linux as a prime
desktop for 12 years but with not much debian experience.
Only idea at present is to run
apt-get -d install desktop-base-trinity kde-trinity >tdeload.
followed by
/var/cache/apt/archives to a DVD then -
on another machine to HD at /var/cache/apt/archives
EITHER
put /var/cache/apt/archives in sources.list
apt-get -install desktop-base-trinity kde-trinity
OR
cd /var/cache/apt/archives
dpkg -i desktop-base-trinity
dpkg -i kde-trinity
OR
redo tdeload. as script, in order, for dpkg
There is probably a better/easier method which I haven't thought of and don't
want to find problems which involve satphones
($$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ worse than that seattle mob)
--
regards
John Campbell
One of the problems I experienced when I tried V3.5.13 was that ksysguard was
no longer detecting the lm-sensors output. Has anyone else experienced the
same problem, or conversely, are people that are using 3.5.13 finding that
ksysguard _is_ detecting the hardware sensors on their systems?
Regards,
LeeE
Hi Tim,
I build kopete from git, protocols and plugins are built too, but kopete
cannot see any of them. Any recent changes can be the reason for this?
--
Serghei.
Hi,
I'm frequently experiencing a problem with kdm-trinity (V3.5.12) appearing to
time out on system start-up. The following two lines are put into my syslog
when this happens:
kdm[1966]: X server startup timeout, terminating
kdm[1966]: X server for display :0 can't be started, session disabled
This is an intermittant problem and doesn't happen every time I start my
system (I'd guess it occurs about 50% of the time). When it does I'm left
with just the basic console. However, all I need to do to get X up and
running is to log in on the console and restart kdm-trinity.
The system is running Debian Squeeze on amd64 with an nVidia graphics card
using the proprietary nVidia driver.
Curiously, I don't recall this happening when I first installed TDE V3.5.12,
which was quite some time ago now and it only seems to have started occurring
relatively recently.
Since I first installed Trinity V3.5.12 I have installed a number of Debian
Squeeze updates but in addition to this I also tried upgrading to TDE V3.5.13
but then had to downgrade back to TDE V3.5.12 due to a couple of problems
with V3.5.13.
As I didn't remove TDE V3.5.13 and all of its config files when I downgraded
back to TDE V3.5.12 I imagine that it's possible that kdm-trinity V3.5.13
introduced some different configuration settings. Alternatively, there have
been a couple of kernel updates during this period (I compile my own kernels
from the Debian linux-source package and then need to recompile the nVidia
driver to fit the new kernel. The kernel updates have all been minor point
updates so the kernel configs have been unchanged over the period concerned)
and this may be a factor. Fwiw, the syslog messages from kdm-trinity appear
about 15 seconds after the nVidia module load message.
I've also had a look in the Xorg.log files and while there are no clear errors
or warnings there are differences at the end of the logs between successful
and unsuccessful start ups as shown below...
Unsuccessful startup:
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "pc105"
(**) Option "xkb_layout" "gb"
(II) Power Button: Close
(II) UnloadModule: "evdev"
(II) Power Button: Close
(II) UnloadModule: "evdev"
(II) AT Translated Set 2 keyboard: Close
(II) UnloadModule: "evdev"
(II) ImExPS/2 Generic Explorer Mouse: Close
(II) UnloadModule: "evdev"
(II) ACPI Virtual Keyboard Device: Close
(II) UnloadModule: "evdev"
Successful startup:
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "pc105"
(**) Option "xkb_layout" "gb"
(II) Open ACPI successful (/var/run/acpid.socket)
(II) Feb 15 11:52:58 NVIDIA(0): Setting mode "1920x1200+0+0"
(II) Power Button: Device reopened after 1 attempts.
(II) Power Button: Device reopened after 1 attempts.
(II) AT Translated Set 2 keyboard: Device reopened after 1 attempts.
(II) ImExPS/2 Generic Explorer Mouse: Device reopened after 1 attempts.
(II) ACPI Virtual Keyboard Device: Device reopened after 1 attempts.
The extract from the unsuccessful start up clearly shows that some of the
devices are being closed but I can't see any reasons why and, as I say, there
are no errors or warnings: apart from some different time-stamps earlier on
in the logs they are otherwise identical (according to KDiff3).
Any hints or tips would be appreciated.
Regards,
LeeE
Any way to do it?
Got an Android, would like to sync KOrganzier dates with its internal Calendar
app.
Dex
--
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d--(+)@ s-:+ a C++++ UL++ P+>++ L+++>++++ E-- W++ N o? K-
w--(---) !O M+ V- PS+ PE Y++ PGP t++(---)@ 5 X+(++) R+(++) tv--(+)@
b++(+++) DI+++ D- G++ e* h>++ r* y?
------END GEEK CODE BLOCK------
A hypothetical poll for users here....
If TDE were to close down, which desktop would you use instead? You would
be allowed to abandon Linux entirely in this scenario. ;-)
Please state why you have not already switched; i.e. what item are missing
or suboptimal in the other environment.
I am curious as to why TDE still exists and need some concrete examples to
fall back on to counter detractors.
Thanks!
Tim
