Am Mittwoch, 17. Februar 2016 schrieb Gene Heskett:
On Tuesday 16 February 2016 16:53:24 Gene Heskett
wrote:
On Tuesday 16 February 2016 10:10:54 Dr. Nikolaus
Klepp wrote:
Am Mittwoch, 10. Februar 2016 schrieb Lisi
Reisz:
> Why not just _try_, just for - I don't know - for heck's sake
> - doing *exactly* what Nik suggested? You never know, it
> might work.
>
> <quote>
> I had to use "start with empty session" temporarily (for one
> or two reboots) to get rid of some hikups.
> </quote>
>
> Lisi
I'm couriouse: Gene, could you solve the problem?
Nik
Sorry Nik, I haven't tried, been up to my tail in other projects.
But I will at some point do exactly that. And let everyone know.
Cheers, Gene Heskett
Dr Nik;
I had a huge update tonight, 165 packages. So I set it to start
with an empty config, and alternately rebooted and edited grub.cfg
to get it to use the latest kernel automatically since it has been
built with enough stuff I can run the uspace sim version of lcnc
with it. That took 4 reboots to get it right, each one a blank
screen except for the icons & tde menu's.
Getting that right, I reset it to use a saved config, and sure as
God made little green apples, on the next reboot nothing had
changed, it was all back, and all piled up on workspace 2, with the
4 tab terminal that lives on workspace 2 in my usual workflow,
sitting on top of everything else.
So it appears that accomplished zero effect other than kmail wasn't
restarted, everything else was after 4 reboots to an empty config,
including kcalc on its correct workspace 3..
Is the a subdir in ~/.trinity or ~/.kde ( those file dates were all
old) that I can nuke, to make it resave the config as it exists at
logout/reboot?
IOW, What did I do wrong? Should I have been just logging out as
opposed to a hot reboot?
And how does one go about "saving" the manually saved session that
this menu gives you the option of using. I haven't run across a menu
entry to do that. That seems like it should be the real answer,
saving the currently running stuff, including the workspace # its
running on.
But what do I know?
In the FWIW category, big story about a Glibc vulnerability,
released by both Red Hat and Google, a dns exploit that gives the
attacker root with one query. Supposedly a year old, but I don't
recall seeing anything but an update to the docs for glibc in recent
history.
Does anyone know if the wheezy glibc has actually been quietly
patched for that exploit or not in the last year?
Thanks.
Cheers, Gene Heskett
Hi Gene!
Ok, then there is something wrong in your ~/.trinity - and I expect
it's not that easy to correct by hand.
The easiest fix is probably this:
- log out of TDE
- go to a console <ctrl>+<alt>+<f1>
- log in as "gene" or what ever user you use
- $ mv .trinity .trinity-old
- back to X11
- log in
- wizard comes up, just walk through it
- test session, which I expect to work.
- no copy the configs you need from the .trinity-old to .trinity, at
least mails.
I know, that's anoying, but it sometimes happens. Maybe silent
bitrotting, who knows?
Nik