hotkeys/key combinations stop working after a while

[Enjam]

Distro: ubuntu budgie 18.04.1 LTS (up to date as of 04 sept 2018)

Issue Summary:
After a fresh install of ubuntu budgie everything works, then suddenly volume up down, volume mute, CTRL+ALT+T, super+A not working anymore. I did reinstall the OS again, it worked, then i realized that the issue occurs when i connect an external HDMI Monitor to the computer.

After doing research i found a solution here: https://discourse.ubuntubudgie.org/t/volume-up-down-calculator-ctr-altl-t-windows-key-a-and-more-not-working-anymore/140

The command: "nohup budgie-wm --replace" solves this issue

However a freshly installed ubuntu budgie is still having this problem.
Please kindly check, let me know if any additional information needed

[fossfreedom (fossfreedom)]

The other workaround in that thread is the ibus tweak. Did that work for you?

[Enjam (benpiller)]

I will do a fresh install and i will post an update once i finished. :)
Thanks for the quick reply.

On Tue, Sep 4, 2018 at 10:10 AM fossfreedom <email address hidden>
wrote:

> The other workaround in that thread is the ibus tweak. Did that work for
> you?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1790582
>
> Title:
> hotkeys/key combinations stop working after a while
>
> Status in Ubuntu Budgie:
> New
>
> Bug description:
> Distro: ubuntu budgie 18.04.1 LTS (up to date as of 04 sept 2018)
>
> Issue Summary:
> After a fresh install of ubuntu budgie everything works, then suddenly
> volume up down, volume mute, CTRL+ALT+T, super+A not working anymore. I did
> reinstall the OS again, it worked, then i realized that the issue occurs
> when i connect an external HDMI Monitor to the computer.
>
> After doing research i found a solution here:
> https://discourse.ubuntubudgie.org/t/volume-up-down-calculator-ctr-
> altl-t-windows-key-a-and-more-not-working-anymore/140
>
> The command: "nohup budgie-wm --replace" solves this issue
>
> However a freshly installed ubuntu budgie is still having this problem.
> Please kindly check, let me know if any additional information needed
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntubudgie/+bug/1790582/+subscriptions
>

--
Benjamin Piller

[Enjam (benpiller)]

Changed settings to "none" instead of "ibus". Now i'll wait to see if it is
working for a longer time or forever.. :)
I don't understand though why it's not an issue on standard ubuntu but on
budgie...

On Tue, Sep 4, 2018 at 12:43 PM Benjamin Piller <email address hidden> wrote:

> I will do a fresh install and i will post an update once i finished. :)
> Thanks for the quick reply.
>
> On Tue, Sep 4, 2018 at 10:10 AM fossfreedom <email address hidden>
> wrote:
>
>> The other workaround in that thread is the ibus tweak. Did that work for
>> you?
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1790582
>>
>> Title:
>> hotkeys/key combinations stop working after a while
>>
>> Status in Ubuntu Budgie:
>> New
>>
>> Bug description:
>> Distro: ubuntu budgie 18.04.1 LTS (up to date as of 04 sept 2018)
>>
>> Issue Summary:
>> After a fresh install of ubuntu budgie everything works, then suddenly
>> volume up down, volume mute, CTRL+ALT+T, super+A not working anymore. I did
>> reinstall the OS again, it worked, then i realized that the issue occurs
>> when i connect an external HDMI Monitor to the computer.
>>
>> After doing research i found a solution here:
>> https://discourse.ubuntubudgie.org/t/volume-up-down-calculator-ctr-
>> altl-t-windows-key-a-and-more-not-working-anymore/140
>>
>> The command: "nohup budgie-wm --replace" solves this issue
>>
>> However a freshly installed ubuntu budgie is still having this problem.
>> Please kindly check, let me know if any additional information needed
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/ubuntubudgie/+bug/1790582/+subscriptions
>>
>
>
> --
> Benjamin Piller
>

--
Benjamin Piller

[Enjam (benpiller)]

Since i use the "none" settings in the input method, i couldn't reproduce the issue.
If this is the solution, this should be set to "none" by default on the OS image, right?