Sfdwhf

Building an exterior wall within an exterior wall for insulation

What makes papers publishable in top-tier journals?

Why does photorec keep finding files after I have filled the disk free space as root?

Identify KNO3 and KH2PO4 at home

Does diversity provide anything that meritocracy does not?

GRASS not working with QGIS 3.6

How do you voice extended chords?

Boss asked me to sign a resignation paper without a date on it along with my new contract

Why zero tolerance on nudity in space?

Is a new boolean field better than null reference when a value can be meaningfully absent?

How much mayhem could I cause as a sentient fish?

Why are all my replica super soldiers young adults or old teenagers?

A Missing Symbol for This Logo

What is the difference between rolling more dice versus fewer dice?

How to visualize the Riemann-Roch theorem from complex analysis or geometric topology considerations?

Constexpr if with a non-bool condition

After checking in online, how do I know whether I need to go show my passport at airport check-in?

Why did Luke use his left hand to shoot?

False written accusations not made public - is there law to cover this?

Let's Encrypt and EV certificates for different hosts in the same domain

Salsa20 Implementation: Sum of 2 Words with Carries Suppressed

How do I draw the dotted lines as shown in this figure

A starship is travelling at 0.9c and collides with a small rock. Will it leave a clean hole through, or will more happen?

Why is Agricola named as such?

Automatic logout after every some screen unlock - 18.04 - Wayland

How do I logout in Ubuntu 17.10 with wayland?18.04: How to get Wayland back after upgrade to 18.04?ubuntu 18.04 failed to connect to some HTTPS sitesProblems after upgrade from 17.10 to 18.04Gnome-shell desktop non-responsive after upgrade from 17.10 to 18.04Reinstall wayland - 18.04Running Wayland on 18.04Lock screen is weirdly broken on Ubuntu 18.04 / WaylandWayland option in Ubuntu 18.04Desktop in Ubuntu 18.04 “too big”

0

1

At first I though it's a problem with suspend. I found issues about it, tried some fixes, even upgraded Kernel to the latest version... the problem still persisted.

After that I though it's connected with Spotify as I saw some of its segfaults in dmesg.

I stopped using it, but the problem persisted.

Later I though it may be connected with Electron, but even without any Electron app launched I started to keep locking my screen and unlocking ended up with discovery that every some time I lock my screen and unlock it, the logout follows.

Only other hint I found is the following kind of error in dmesg.

gnome-shell[12710]: segfault at 14af00000014 ip 00007f76be14cf51 sp 00007fff4cd00908 error 4 in libgobject-2.0.so.0.5600.3[7f76be117000+52000]

I'm not sure though if it appears every time or not. I tried to search for it, even found some issues, but they didn't seem connected with this issue.

I also tried removing vino as - as far as I believe - it bases on XServer, but it didn't help.

I have only integrated graphics card and no other video drivers installed than default ones.

I just wonder - what causes such behavior? Is it just a Wayland bug?

18.04 gnome-shell wayland

share|improve this question

edited Jan 25 at 13:52

kcpr

asked Jan 25 at 13:09

kcprkcpr

1,033820

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @user68186, where would You report it then? I'm not really sure what causes that.
  
  – kcpr
  Jan 25 at 13:55
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @user68186, ok, thanks, no worries. I'm just a bit skeptical about it, as it seems very generic to me. And, after all, I think I've found a source of that problem and a solution. Thank You again though.
  
  – kcpr
  Jan 26 at 14:50
  

  
  
  
  

add a comment | 

0

1

At first I though it's a problem with suspend. I found issues about it, tried some fixes, even upgraded Kernel to the latest version... the problem still persisted.

After that I though it's connected with Spotify as I saw some of its segfaults in dmesg.

I stopped using it, but the problem persisted.

Later I though it may be connected with Electron, but even without any Electron app launched I started to keep locking my screen and unlocking ended up with discovery that every some time I lock my screen and unlock it, the logout follows.

Only other hint I found is the following kind of error in dmesg.

gnome-shell[12710]: segfault at 14af00000014 ip 00007f76be14cf51 sp 00007fff4cd00908 error 4 in libgobject-2.0.so.0.5600.3[7f76be117000+52000]

I'm not sure though if it appears every time or not. I tried to search for it, even found some issues, but they didn't seem connected with this issue.

I also tried removing vino as - as far as I believe - it bases on XServer, but it didn't help.

I have only integrated graphics card and no other video drivers installed than default ones.

I just wonder - what causes such behavior? Is it just a Wayland bug?

18.04 gnome-shell wayland

share|improve this question

edited Jan 25 at 13:52

kcpr

asked Jan 25 at 13:09

kcprkcpr

1,033820

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @user68186, where would You report it then? I'm not really sure what causes that.
  
  – kcpr
  Jan 25 at 13:55
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @user68186, ok, thanks, no worries. I'm just a bit skeptical about it, as it seems very generic to me. And, after all, I think I've found a source of that problem and a solution. Thank You again though.
  
  – kcpr
  Jan 26 at 14:50
  

  
  
  
  

add a comment | 

At first I though it's a problem with suspend. I found issues about it, tried some fixes, even upgraded Kernel to the latest version... the problem still persisted.

After that I though it's connected with Spotify as I saw some of its segfaults in dmesg.

I stopped using it, but the problem persisted.

Later I though it may be connected with Electron, but even without any Electron app launched I started to keep locking my screen and unlocking ended up with discovery that every some time I lock my screen and unlock it, the logout follows.

Only other hint I found is the following kind of error in dmesg.

gnome-shell[12710]: segfault at 14af00000014 ip 00007f76be14cf51 sp 00007fff4cd00908 error 4 in libgobject-2.0.so.0.5600.3[7f76be117000+52000]

I'm not sure though if it appears every time or not. I tried to search for it, even found some issues, but they didn't seem connected with this issue.

I also tried removing vino as - as far as I believe - it bases on XServer, but it didn't help.

I have only integrated graphics card and no other video drivers installed than default ones.

I just wonder - what causes such behavior? Is it just a Wayland bug?

18.04 gnome-shell wayland

share|improve this question

edited Jan 25 at 13:52

kcpr

asked Jan 25 at 13:09

kcprkcpr

1,033820

gnome-shell[12710]: segfault at 14af00000014 ip 00007f76be14cf51 sp 00007fff4cd00908 error 4 in libgobject-2.0.so.0.5600.3[7f76be117000+52000]

share|improve this question

edited Jan 25 at 13:52

kcpr

asked Jan 25 at 13:09

kcprkcpr

1,033820

share|improve this question

edited Jan 25 at 13:52

kcpr

asked Jan 25 at 13:09

kcprkcpr

1,033820

asked Jan 25 at 13:09

kcprkcpr

1,033820

asked Jan 25 at 13:09

kcprkcpr

1,033820

1 Answer
1

active

oldest

votes

0

I think I found a source of that behavior. I seems connected to Gnome Extensions and I even managed to narrow it down. I think it's caused by Time++ extension and maybe some other ones I have also disabled. To be honest, at least some of Time++ features seemed to work well even on Wayland, but maybe some others require XServer and change to Wayland started causing problems.

The lesson from that: when You experience any weird behavior of Gnome Shell start from disabling all extensions. Than, if it doesn't help, look for other possible sources of problem.

share|improve this answer

edited 4 mins ago

answered Jan 26 at 14:59

kcprkcpr

1,033820

add a comment | 

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1112774%2fautomatic-logout-after-every-some-screen-unlock-18-04-wayland%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

0

I think I found a source of that behavior. I seems connected to Gnome Extensions and I even managed to narrow it down. I think it's caused by Time++ extension and maybe some other ones I have also disabled. To be honest, at least some of Time++ features seemed to work well even on Wayland, but maybe some others require XServer and change to Wayland started causing problems.

The lesson from that: when You experience any weird behavior of Gnome Shell start from disabling all extensions. Than, if it doesn't help, look for other possible sources of problem.

share|improve this answer

edited 4 mins ago

answered Jan 26 at 14:59

kcprkcpr

1,033820

add a comment | 

0

I think I found a source of that behavior. I seems connected to Gnome Extensions and I even managed to narrow it down. I think it's caused by Time++ extension and maybe some other ones I have also disabled. To be honest, at least some of Time++ features seemed to work well even on Wayland, but maybe some others require XServer and change to Wayland started causing problems.

The lesson from that: when You experience any weird behavior of Gnome Shell start from disabling all extensions. Than, if it doesn't help, look for other possible sources of problem.

share|improve this answer

edited 4 mins ago

answered Jan 26 at 14:59

kcprkcpr

1,033820

add a comment | 

I think I found a source of that behavior. I seems connected to Gnome Extensions and I even managed to narrow it down. I think it's caused by Time++ extension and maybe some other ones I have also disabled. To be honest, at least some of Time++ features seemed to work well even on Wayland, but maybe some others require XServer and change to Wayland started causing problems.

The lesson from that: when You experience any weird behavior of Gnome Shell start from disabling all extensions. Than, if it doesn't help, look for other possible sources of problem.

share|improve this answer

edited 4 mins ago

answered Jan 26 at 14:59

kcprkcpr

1,033820

share|improve this answer

edited 4 mins ago

answered Jan 26 at 14:59

kcprkcpr

1,033820

answered Jan 26 at 14:59

kcprkcpr

1,033820

answered Jan 26 at 14:59

kcprkcpr

1,033820