View Issue Details

IDProjectCategoryView StatusLast Update
0003737Kali LinuxKali Package Improvementpublic2017-09-18 09:26
ReporterPhexcom Assigned Torhertzog  
PriorityurgentSeveritycrashReproducibilityalways
Status closedResolutionfixed 
Product Version2016.2 
Summary0003737: Kali Auto Logout user during usage
Description

After Upgrade Yesterday, My Kali host acting been functioning abnormally. It auto logout user during usage. Have tried restarting it and even re-updating and upgrading to the latest and greatest but still having the same issue. And I check "dmesg" and Below is what I found..

[51781.183689] hid-generic 0003:0000:0538.0008: input,hidraw0: USB HID v1.11 Mouse [ USB OPTICAL MOUSE] on usb-0000:19:00.0-2/input0

[51784.407052] gnome-shell[26055]: segfault at ffffffffffffffe0 ip 00007fd974f86db9 sp 00007ffd4fbd9d00 error 5 in libwayland-server.so.0.1.0[7fd974f80000+10000]

[51784.439750] traps: gnome-software[26144] trap int3 ip:7f1f20f60261 sp:7ffcf6cc3130 error:0 in libglib-2.0.so.0.5000.2[7f1f20f10000+112000]

[51784.440938] traps: gnome-terminal-[28268] trap int3 ip:7f90be6e8261 sp:7ffc939198d0 error:0 in libglib-2.0.so.0.5000.2[7f90be698000+112000]

[51784.716558] chrome[29039]: segfault at 968 ip 00007f3ecd3e1fe3 sp 00007ffecd4f8a80 error 4 in libX11.so.6.3.0[7f3ecd3b4000+13c000]

Attached Files

Activities

Phexcom

Phexcom

2016-11-23 17:29

reporter   ~0006135

Am I the Only one facing this Problem? Because it's becoming annoying as Kali is my host and I can do any with it now

rhertzog

rhertzog

2016-11-24 09:11

administrator   ~0006136

I think that you are the only one, yes. On the login screen, please double check what session you select, click on the small settings icon (that you get after selecting the user) and make sure to NOT pick a "wayland" session.

Your problems might be related to your usage of wayland instead of X11 (which is the default).

Phexcom

Phexcom

2016-11-24 10:22

reporter   ~0006137

Ok I will check it out. because now i switch to Cinnamon. And I was no more having the issue

sirwibble

sirwibble

2017-01-05 16:59

reporter   ~0006217

You're not the only one. I did a clean install using the x64bit version and it did exactly the same thing. I could logon and as soon as I launch an app or open the terminal window it automatically logs me out and returns to the logon screen.

I did an CTRL-F2 logon to text, did an apt-get update & upgrade which it did and the problem is still there. You cannot use Kali because of the fault.

Others on the web also reporting the issue.

I have downloaded the x32 version to see if that works.

We need a fix!

bitbucket

bitbucket

2017-01-07 18:26

reporter   ~0006224

same problem here.

windows 10 x64
vmware 12.5
Kali vmware image x86 and x64 tested

_cC_

_cC_

2017-01-11 04:06

reporter   ~0006233

what chip sets are these machines?

sirwibble

sirwibble

2017-02-01 14:44

reporter   ~0006296

I found the fix for my problem of auto logout when I launched a terminal etc.

I did a complete re-install, using all default settings and Kali worked fine, no logouts.

I did another re-install but the only thing I changed was my location and the problem came back, I changed the default USA location to my geo location.

I went in to the system settings and change my geo location back to USA and the system works as it should.

If you are having auto logout when launching apps, check which location you have set, if its not set to the USA, change it and try again.

Worked for me.
Good luck

rhertzog

rhertzog

2017-02-01 20:27

administrator   ~0006297

sirwibble, can you let us know what location you used so that we can reproduce the issue and get it fixed?

Does the language matter or only the location?

sirwibble

sirwibble

2017-02-03 14:50

reporter   ~0006308

I had the region and language to UK, now running USA on both - Still working

arun483

arun483

2017-02-05 13:47

reporter   ~0006316

I am having the same issue, I have tried changing location to USA/UK but still no luck. Could it because of USB mouse?

Scrapster

Scrapster

2017-07-19 19:10

reporter   ~0006941

Same thing here, changed locations with no luck.
I'll try a few more things, before I reinstall

rhertzog

rhertzog

2017-09-18 09:26

administrator   ~0007347

We switched back to Xorg by default so this is likely gone. Also a new gnome-shell came in the mean time so the original bug is likely gone too.

Issue History

Date Modified Username Field Change
2016-11-20 10:49 Phexcom New Issue
2016-11-20 10:49 Phexcom File Added: Screenshot from 2016-11-20 14-44-07.png
2016-11-23 17:29 Phexcom Note Added: 0006135
2016-11-24 09:11 rhertzog Note Added: 0006136
2016-11-24 10:22 Phexcom Note Added: 0006137
2017-01-05 16:59 sirwibble Note Added: 0006217
2017-01-07 18:26 bitbucket Note Added: 0006224
2017-01-11 04:06 _cC_ Note Added: 0006233
2017-02-01 14:44 sirwibble Note Added: 0006296
2017-02-01 20:27 rhertzog Note Added: 0006297
2017-02-03 14:50 sirwibble Note Added: 0006308
2017-02-05 13:47 arun483 Note Added: 0006316
2017-07-19 19:10 Scrapster Note Added: 0006941
2017-09-18 09:26 rhertzog Assigned To => rhertzog
2017-09-18 09:26 rhertzog Status new => closed
2017-09-18 09:26 rhertzog Resolution open => fixed
2017-09-18 09:26 rhertzog Note Added: 0007347