Bsrgvty

Name for geostationary orbit around another planet

How does Remove Curse affect Bestow Curse

How to verify router firmware is legit?

Give a grammar for a language on Σ=a,b,c that accepts all strings containing exactly one a

What are the ways my non-monk character can improve their unarmed damage?

Is it acceptable to have a fraction in an eigenvector?

Decode the Dreaded Alphabet Cypher™️

Frictional force doesn't depend on surface area, but why does this application work?

Selecting Primes from list of list

Signed overflow in C++ and undefined behaviour (UB)

How to (or should one) distinguish between lowercase and uppercase alphabets orally when lecturing?

What did the Oracle take from the Merovingian?

Can Alice win the game?

Will 20 inch BMX wheels fit a folding bike (with 20 inch wheels)?

What is the point of teaching Coding and robotics to kids as young as 6 years old?

Why must a CNN have fixed input size?

Am I being used by my supervisor?

Dice game with rules and three dice

Color coding Alerts

How did the Corona (Key Hole) satellites film canisters deorbit?

Rite of Winter: How to Stop Crescian Couples from Mutual Assassination

Is economics a science?

How to add new line between `ls -l` output

Why does General Grievous say “Ah yes, the negotiator?”

Shortcut function misbehaving?

Notebook display not detected after upgrade to Ubuntu Gnome 16.04No sound from internal speakers after using HDMI outputBoot freeze when using second monitor (Xubuntu 16.04)?External HDMI display on Ubuntu 16.04, NVIDIA GeForce GTX 960MChanging the screen brightness of the external screenUbuntu 16.04 - No default sound device for laptop after unplugging headphones

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;

4

I have a Asus laptop with Ubuntu 16.04, It has a function shortcut (fn+f7) which I used to turn off the display.

I connected it to an external display via HDMI, removed the cable, shut it down. but now after a fresh boot It locks my account instead and not turning the display off!

Any idea or suggestion is appreciated.

16.04 shortcut-keys configuration desktop-environments function-keys

share|improve this question

edited Sep 11 at 15:00

Masked Man

asked Sep 11 at 14:16

Masked ManMasked Man

25522 silver badges1515 bronze badges

add a comment
 | 

4

I have a Asus laptop with Ubuntu 16.04, It has a function shortcut (fn+f7) which I used to turn off the display.

I connected it to an external display via HDMI, removed the cable, shut it down. but now after a fresh boot It locks my account instead and not turning the display off!

Any idea or suggestion is appreciated.

16.04 shortcut-keys configuration desktop-environments function-keys

share|improve this question

edited Sep 11 at 15:00

Masked Man

asked Sep 11 at 14:16

Masked ManMasked Man

25522 silver badges1515 bronze badges

add a comment
 | 

I have a Asus laptop with Ubuntu 16.04, It has a function shortcut (fn+f7) which I used to turn off the display.

I connected it to an external display via HDMI, removed the cable, shut it down. but now after a fresh boot It locks my account instead and not turning the display off!

Any idea or suggestion is appreciated.

16.04 shortcut-keys configuration desktop-environments function-keys

share|improve this question

edited Sep 11 at 15:00

Masked Man

asked Sep 11 at 14:16

Masked ManMasked Man

25522 silver badges1515 bronze badges

share|improve this question

edited Sep 11 at 15:00

Masked Man

asked Sep 11 at 14:16

Masked ManMasked Man

25522 silver badges1515 bronze badges

share|improve this question

edited Sep 11 at 15:00

Masked Man

asked Sep 11 at 14:16

Masked ManMasked Man

25522 silver badges1515 bronze badges

asked Sep 11 at 14:16

Masked ManMasked Man

25522 silver badges1515 bronze badges

asked Sep 11 at 14:16

Masked ManMasked Man

25522 silver badges1515 bronze badges

1 Answer
1

active

oldest

votes

-1

+50

If I understood the problem correct....
You are saying that the behavior of fn+f7 is changed after you attached and detached your device to an external display.

Here are some pointers to find out what fn+f7 is mapped to after this action
https://superuser.com/questions/428945/defining-keyboard-shortcuts-involving-the-fn-key

There are at least two possibilities here
1) When connected to external display, fn+f7 key can't turn that display off (depends upon display type) so it rather changes to display lockout. Maybe you don't remember and you shut it down in that state and so it stays in that stays (some persistent configuration?).
2) fn+f7 is multiplexed at the keyboard hw level and may have a HW bug (passive electronics component used) where attaching to HDMI modified one of it's state holding. This is very less likely and should be cleared after a complete power shutdown and a wait before restart.

share|improve this answer

answered Sep 21 at 0:29

xrplorerxrplorer

7911 bronze badge

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I have a keyboard fn+f8 which is for setting external display states, in windows (which I used a couple years ago) it showed the mode it is in as a notification, e.g. it is mirroring, just external or just internal but in ubuntu it didn't show that so I don't remember in which state I turned it off.
  
  – Masked Man
  Sep 21 at 7:24
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I needed some more clarification and details but have the bounty anyway.
  
  – Masked Man
  Sep 21 at 23:38
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  As for me Fn+f7 stopped working after some Linux kernel update. I did not connect and disconnect any external display to my ASUS UX305L. The HW hotkey simply stopped working. It was working in login screen, in user session etc. Just in case other HW related hotkeys as audio, touchpad, brightness all work OK.
  
  – Sergey Sergeyev
  Sep 28 at 9:01
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @SergeySergeyev, did you find any solution?
  
  – Masked Man
  Sep 28 at 19:47
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  @MaskedMan Can you run xev and check what codes are printed in your system when you press and release fn+f7? Then repeat the experiment while booting off a live disk (I am assuming your Fn+F7 works in that case properly as intended). Compare the two and see if the codes are changed. Then off you go to exploring xkb.
  
  – xrplorer
  Nov 12 at 2:54
  
  

  
  
  
  

 | 
show 2 more comments

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/4.0/"u003ecc by-sa 4.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%2f1173457%2fshortcut-function-misbehaving%23new-answer', 'question_page');

);

Post as a guest

Name

Email

Required, but never shown

-1

+50

If I understood the problem correct....
You are saying that the behavior of fn+f7 is changed after you attached and detached your device to an external display.

Here are some pointers to find out what fn+f7 is mapped to after this action
https://superuser.com/questions/428945/defining-keyboard-shortcuts-involving-the-fn-key

There are at least two possibilities here
1) When connected to external display, fn+f7 key can't turn that display off (depends upon display type) so it rather changes to display lockout. Maybe you don't remember and you shut it down in that state and so it stays in that stays (some persistent configuration?).
2) fn+f7 is multiplexed at the keyboard hw level and may have a HW bug (passive electronics component used) where attaching to HDMI modified one of it's state holding. This is very less likely and should be cleared after a complete power shutdown and a wait before restart.

share|improve this answer

answered Sep 21 at 0:29

xrplorerxrplorer

7911 bronze badge

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I have a keyboard fn+f8 which is for setting external display states, in windows (which I used a couple years ago) it showed the mode it is in as a notification, e.g. it is mirroring, just external or just internal but in ubuntu it didn't show that so I don't remember in which state I turned it off.
  
  – Masked Man
  Sep 21 at 7:24
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I needed some more clarification and details but have the bounty anyway.
  
  – Masked Man
  Sep 21 at 23:38
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  As for me Fn+f7 stopped working after some Linux kernel update. I did not connect and disconnect any external display to my ASUS UX305L. The HW hotkey simply stopped working. It was working in login screen, in user session etc. Just in case other HW related hotkeys as audio, touchpad, brightness all work OK.
  
  – Sergey Sergeyev
  Sep 28 at 9:01
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @SergeySergeyev, did you find any solution?
  
  – Masked Man
  Sep 28 at 19:47
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  @MaskedMan Can you run xev and check what codes are printed in your system when you press and release fn+f7? Then repeat the experiment while booting off a live disk (I am assuming your Fn+F7 works in that case properly as intended). Compare the two and see if the codes are changed. Then off you go to exploring xkb.
  
  – xrplorer
  Nov 12 at 2:54
  
  

  
  
  
  

 | 
show 2 more comments

-1

+50

If I understood the problem correct....
You are saying that the behavior of fn+f7 is changed after you attached and detached your device to an external display.

Here are some pointers to find out what fn+f7 is mapped to after this action
https://superuser.com/questions/428945/defining-keyboard-shortcuts-involving-the-fn-key

There are at least two possibilities here
1) When connected to external display, fn+f7 key can't turn that display off (depends upon display type) so it rather changes to display lockout. Maybe you don't remember and you shut it down in that state and so it stays in that stays (some persistent configuration?).
2) fn+f7 is multiplexed at the keyboard hw level and may have a HW bug (passive electronics component used) where attaching to HDMI modified one of it's state holding. This is very less likely and should be cleared after a complete power shutdown and a wait before restart.

share|improve this answer

answered Sep 21 at 0:29

xrplorerxrplorer

7911 bronze badge

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I have a keyboard fn+f8 which is for setting external display states, in windows (which I used a couple years ago) it showed the mode it is in as a notification, e.g. it is mirroring, just external or just internal but in ubuntu it didn't show that so I don't remember in which state I turned it off.
  
  – Masked Man
  Sep 21 at 7:24
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I needed some more clarification and details but have the bounty anyway.
  
  – Masked Man
  Sep 21 at 23:38
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  As for me Fn+f7 stopped working after some Linux kernel update. I did not connect and disconnect any external display to my ASUS UX305L. The HW hotkey simply stopped working. It was working in login screen, in user session etc. Just in case other HW related hotkeys as audio, touchpad, brightness all work OK.
  
  – Sergey Sergeyev
  Sep 28 at 9:01
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @SergeySergeyev, did you find any solution?
  
  – Masked Man
  Sep 28 at 19:47
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  @MaskedMan Can you run xev and check what codes are printed in your system when you press and release fn+f7? Then repeat the experiment while booting off a live disk (I am assuming your Fn+F7 works in that case properly as intended). Compare the two and see if the codes are changed. Then off you go to exploring xkb.
  
  – xrplorer
  Nov 12 at 2:54
  
  

  
  
  
  

 | 
show 2 more comments

If I understood the problem correct....
You are saying that the behavior of fn+f7 is changed after you attached and detached your device to an external display.

Here are some pointers to find out what fn+f7 is mapped to after this action
https://superuser.com/questions/428945/defining-keyboard-shortcuts-involving-the-fn-key

There are at least two possibilities here
1) When connected to external display, fn+f7 key can't turn that display off (depends upon display type) so it rather changes to display lockout. Maybe you don't remember and you shut it down in that state and so it stays in that stays (some persistent configuration?).
2) fn+f7 is multiplexed at the keyboard hw level and may have a HW bug (passive electronics component used) where attaching to HDMI modified one of it's state holding. This is very less likely and should be cleared after a complete power shutdown and a wait before restart.

share|improve this answer

answered Sep 21 at 0:29

xrplorerxrplorer

7911 bronze badge

share|improve this answer

answered Sep 21 at 0:29

xrplorerxrplorer

7911 bronze badge

answered Sep 21 at 0:29

xrplorerxrplorer

7911 bronze badge

answered Sep 21 at 0:29

xrplorerxrplorer

7911 bronze badge