By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 2517 - [Regression] Switching to VT terminates TDE session
Summary: [Regression] Switching to VT terminates TDE session
Status: NEEDINFO
Alias: None
Product: TDE
Classification: Unclassified
Component: tdebase (show other bugs)
Version: R14.0.x [Trinity]
Hardware: Other Linux
: P5 normal
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2015-09-03 20:29 CDT by Kristopher
Modified: 2018-08-03 22:26 CDT (History)
4 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
~/.xsession-errors from crash (13.40 KB, text/plain)
2015-09-04 15:25 CDT, Kristopher 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kristopher 2015-09-03 20:29:40 CDT 
I did not notice whether or not this was present in R14.0.0, but it is present in R14.0.1, and was *not* present in 3.5.*.

Switching to a VT (F1-F6) then back to my TDE session will abruptly terminate my TDE session without the normal logout procedure, and will bounce me back to TDM.
Comment 1 Slávek Banko 2015-09-03 20:35:07 CDT 
You can add some additional information - such as distribution, version of distribution and content of .xsession-errors after crash?
Comment 2 Michele Calgaro 2015-09-04 11:04:46 CDT 
Quite strange, never had any problem here.
Please provide us some more info.
Comment 3 Kristopher 2015-09-04 15:25:29 CDT 
Created attachment 2561 [details]
~/.xsession-errors from crash

This is my ~/.xsession-errors file from immediately after a crash, prior to logging back in. I've redacted my user name from this attachment for privacy and replaced it with "{user}" (without quotes).

I am using CentOS 6. I know for fact that 3.5.13.* did not do this on CentOS (or any other distro), so I'm not sure I want to blame CentOS for this.
Comment 4 Michele Calgaro 2015-09-07 10:30:18 CDT 
Uhm... not an easy one. I see a lot of 
<application_name>: Fatal IO error: client killed
in your xsession-error file. I ran into this message when working on another bug not so long ago and that was down to thread handling issues. This may not be the same thing, but it does not bode well anyway :-)

Given you also had other problems after the recent upgrade and to help debugging, would you be able to prepare a fresh CentOS 6 install inside a virtualbox VM, then install R14.0.1 and check whether the problem is repeatable? If so, then it would be very helpful because you could just export the VM and pass it to us for testing/debugging.
Comment 5 Kristopher 2015-09-07 16:40:04 CDT 
(In reply to Michele Calgaro from comment #4)
> Uhm... not an easy one. I see a lot of 
> <application_name>: Fatal IO error: client killed
> in your xsession-error file. I ran into this message when working on another
> bug not so long ago and that was down to thread handling issues. This may
> not be the same thing, but it does not bode well anyway :-)
> 
> Given you also had other problems after the recent upgrade and to help
> debugging, would you be able to prepare a fresh CentOS 6 install inside a
> virtualbox VM, then install R14.0.1 and check whether the problem is
> repeatable? If so, then it would be very helpful because you could just
> export the VM and pass it to us for testing/debugging.

I will see if I can get a VM going on my ancient hardware. If I can, and the problems are there, how would I send you guys the VM? Something tells me it will be too large for email or Dropbox :-)
Comment 6 Michele Calgaro 2015-09-11 08:24:10 CDT 
>I will see if I can get a VM going on my ancient hardware. If I can, and the 
>problems are there, how would I send you guys the VM? Something tells me it 
>will be too large for email or Dropbox :-)
Sorry for the late reply, really busy these days...
If you can prepare a VM, we will find a way for you to pass it to us, for example using google drive or uploading it on the TDE website somewhere.
Alexandre already did it a few times with his TDE/PCLinux remastered version (see bug 2523 for example)
Comment 7 Kristopher 2015-09-12 13:32:19 CDT 
Trying to run VirtualBox on my machine is proving so laggy that I barely got TDE installed -- even opening the TMenu takes close to a minute, and doing anything else in the desktop takes even longer. I do not have the patience to deal with that, and unfortunately I don't have any other machine to run it on.

I can still upload it somewhere if you guys still want to test it, and provide a copy of my current ~/.trinity/ (I'll remove the config files for the PIM apps since those contain private information). I'll still need somewhere to upload, though.
Comment 8 Michele Calgaro 2015-09-13 23:03:08 CDT 
> Trying to run VirtualBox on my machine is proving so laggy 
If it is so much problematic, never mind.
When we will look at this bug, we will try to install CentOS and TDE and see what happen.
Comment 9 Michele Calgaro 2018-08-03 22:26:12 CDT 
I can't reproduce this bug at all. Is it still happening?