When reading the thread "Lockups after unlocking screensaver", it
reminds me an unanswered question I had months ago.
I use Trinity 3.13.2 on Ubuntu 12.04 LTS. As far as I can recall
(years), my TDE session started on vt7 (Ctrl-Alt-F7).
After a power outage, I restarted my box and ever since TDE starts on
vt8 (Ctrl-Alt-F8).
Everything works well but I would like to understand the reason of this
vt switch.
I searched the web for an answer with no success.
Does someone on this list has an answer?
Nothing harmful, no bug, but curiosity... is on mars now :-)
midi-pascal
Hi,
I'm running an install from exegnu-jessv-20141125 on a recent
ThinkPad. Amarok when starting complains:
xine was unable to initialize any audio drivers.
Haven't found anything satisfactory in searching, but the problem goes
back at least to KDE3.
BTW, VCL works okay, after I select the mixer. Maybe it uses different drivers.
Robert
TDEPowersave always reports running on AC power, even when running on the
battery, and doesn't give the low battery warnings. This started when I
upgraded to R14; it worked fine in 13.2. It's a big problem because, when
runing on battery, the machine just dies with no warning when the battery is
dead.
This is on an HP laptop running Debian 7 (Wheezy) and R14 from Slavek's
repo, updated this morning.
--
PGP key: http://homestead-products.com/pubkey.htm
Hello
Using Kubuntu 10.04 and trinity 3.5.13.2 I encountered the following
problem.
If I change the language environment from English to Spanish
via kpersonalizer,
- the icons become smaller
- some applications such firefox crash with a signal 11 type error
and a reference to gtk-qt-trinity. However kgtk-qt3-trinity is
not installed.
After removing the .trinity directory and restart trinity, but sticking
to English everything is ok
Has anybody found similar problems?
Thanks
Uwe Brauer
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA224
Cross-post for those not signed up on the trinity-announce mailing list:
http://trinity-announce.pearsoncomputing.net/?0::31
Note that a lot of work has gone into improving the download/mirror system
since RC1; please test and report any issues with installation and/or
download to this list.
Thanks!
Tim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iFYEARELAAYFAlR+Ob8ACgkQLaxZSoRZrGHMCQDbBJc65WxVoV9m5n+tLF+/9dAz
rR+hUObWrXyqPgDgqQaxNVUbpXRrwAD9gVCbOHYYqGO7O+vApn9eAw==
=2sPz
-----END PGP SIGNATURE-----
On Thursday 04 December 2014 14.37:16 Timothy Pearson wrote:
> > On Thursday 04 December 2014 11.37:33 Werner Joss wrote:
> >> ok,
> >> here is a first short report about RC2:
> >> - installation/upgrade from 3.5.13.2 (debian wheezy) did not go through
> >> in
> >> one step, I had to do 'aptitude dist-upgrade' 4 or 5 times, as it
> >> stopped
> >> with dependency errors. finally, competed, though.
> >> - seems to work mostly, so far, but still some glitches:
> >> - konact works, but crashes reproducable upon exit.
> >> - some applications are missing/not available:
> >> kate
> >> kwrite
> >> kradio
> >> should I file bug reports about that ?
> >> Werner
> >
> > I also had to use apt-get dist-update to get R14 running, but only one
> > time.
> >
> > But I have another problem: On R14 I can setup a "link to device" (an
> > nfs
> > share here) but it's not working: once the link is created, I get four
> > tabs
> > (General, permissions, meta-info and preview) where I used to have five
> > ("device" is gone).
> >
> > So the link is not working (mounting per hand does work). I rely heavily
> > on
> > these links so R14 is not usable at this point for me. I don't know if
> > this
> > is one of the "not yet ready" elements or a "bug"?
> >
> > Thierry
>
> This sounds like something that might have slipped through testing as I am
> not familiar with the feature you describe. In general, ever since R14
> RC2 all software should be ready in its final functional form (even in RC1
> this was mostly true but we ran into major problems with the compositor
> for that release); the only changes between RC2 and Final are to resolve
> some remaining crashes, minor defects, updated the documentation, etc.
>
> Can you provide me with detailed reproduction instructions so that I can
> check for a quick fix?
>
> Thanks!
>
> Tim
So, this is what I can provide:
- two screenshots. Both show on the left the "create link" dialog (Create
New -> Link to Device -> nfs). It shows five tabs, the middle one
being "Device".
On the right you see the properties of an existing "Link to Device".
On the desktop of 3.5.13.2 you have the middle tab. On the desktop of
3.5.14.0.0 it does not show. The Link does not get the correct icon and it
does not work either (although mount <mount point> works, so the nfs mount
does work).
I also compared the Desktop Files, they are identical, so the problem is
deeper.
Thierry
Since installing RC2 I have twice experienced "lockups" upon
unlocking the screen. I have never experienced these before.
Once "locked up" the mouse has no effect and there is almost
no keyboard effect. However numlock and capslock keys still
flip their indicator LEDs and ctrl-alt-Fn can be used to
switch to another console.
First time: as root I restarted tdm-trinity. I didn't notice
if there were any error messages. When Trinity restarted it
was on a new console - alt-F8 instead of alt-F7.
The second time: as root I stopped tdm-trinity. I noticed
error messages saying the stop had failed. I killed -9
kdesktop_lock, stopped tdm-trinity again, and started it.
This time Trinity started on the expected console.
I'd appreciate any suggestions of any additional steps I
should take to help diagnose the problem if it happens again.
--Mike
Hello all,
I had installes Wheezy several time and then installes TDE, no problem, choose
TDM and restart...
I've just installed two laptops from the 7.7 CD and both time I had to wipe
out Gnome 3 to get TDE loading. Is this a new rogue Gnome Install way?
Thierry
Debian Wheezy, Amd64, Nvidia quadro card, drivers from vender, dual monitors.
In my .xsession-errors files I can see numerous entries:
"tdecore] Deleting stale lockfile /tmp/tde-pabiVcZK3y/kdesktop_lock_lockfile"
This crashes my X session, ~ 1 minute uptime, dumps me back to the login
screen, totaly unworkable.
I have been working around this issue because it only happens on 2
workstations with the same hardware specs, and drivers from Nvidia.
I remove '/opt/trinity/bin/kdesktop_lock', I do not use screensaver or lock
desktop, this works..until an update replaces the kdesktop_lock binary...this
will stop eventually.
I read bugs 2222 & 2230, re kdesktop_lock, I could run a backtrace if that
would help and if someone could give directions on howto. I will file a bug
with the backtrace.
--
Peace,
Greg
On Friday 28 November 2014, Alexandre wrote:
> Hi,
>
>
> So, I'd like to know if there would be some interest in it, if it worth doing it.
> Also, how many persons here have a Pi?
>
Hi Alexandre,
I have two Raspberry Pis and one Banana Pi. I might be interested in an implementation but my feeling is - the Banana Pi is more worth to work with. It's nearly as cheap as the Raspberry but is a lot better designed and more powerfull:
Raspberry Pi Model B+ Banana Pi
----------------------------------------------------------------------------------------------------------------
SoC Broadcom BCM2835 Allwinner A20
CPU ARM1176JZF-S (700 MHz bis 1000 MHz) ARM Cortex-A7 Dual-Core (1000 MHz)
GPU Broadcom VideoCore IV ARM Mali 400MP2
RAM 512 MByte 1 GByte DDR3 DRAM
LAN 10/100 MBit/s 10/100/1000 MBit/s
GPIO 17 Pins 26 Pins, I2C, SPI, UART, CAN bus
SATA 7-Pin-SATA-Port
USB 4x USB 2.0 Host 2x USB 2.0 Host, 1x USB OTG, 1x CSI Kamera
MISC Onboard Micro und IR-Receiver
SIZE 85,6 mm x 56,0 mm 92,0 mm x 60,0 mm
Price here in Germany: 29 € versus 44 €
Gerhard
PS: hope the crude table formatting goes through