Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No keyboard layout indicator after reboot #195

Closed
cepreu2github opened this issue Sep 28, 2017 · 6 comments
Closed

No keyboard layout indicator after reboot #195

cepreu2github opened this issue Sep 28, 2017 · 6 comments

Comments

@cepreu2github
Copy link

cepreu2github commented Sep 28, 2017

Expected behaviour

After layout setup and reboot layout indicator still must be there in tray.

Actual behaviour

It appears when you add layout but does not appears after reboot.
screenshot 2017-09-28 21-10-31
Image is condition after reboot. There is two layouts, but no indicator.

Steps to reproduce the behaviour

  1. Add additional layout.
  2. Reboot.
  3. Look at panel.

MATE general version

1.18

Package version

1.18.1-2

Linux Distribution

SparkyLinux amd64 (based on Debian testing) updated at 28 sep 2017.

If you need any additional info (like stacktraces, logs, etc), feel free to ask.


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@monsta
Copy link
Contributor

monsta commented Oct 5, 2017

@flexiondotorg: looks like https://bugs.launchpad.net/bugs/1720363, but in Debian.

@cepreu2github
Copy link
Author

Yes. Same symptoms.

@monsta
Copy link
Contributor

monsta commented Oct 5, 2017

I found out that mate-settings-daemon --replace brings it back. Wonder if we have some race condition on session start...

@monsta
Copy link
Contributor

monsta commented Oct 17, 2017

So it turned out to be a packaging issue in Debian and Ubuntu.
The indicator works fine if I build m-s-d from either master or 1.18 branch, but doesn't work in version 1.18.1-2 in Debian Testing (or Unstable) and Ubuntu MATE 17.10.

@flexiondotorg @sunweaver
Please have a look at this. Version 1.18.1-2 contains a patch from cf0b976, but it's not enough. To fix this, you need to do one of the following:

I've uploaded the debdiff with the second solution to https://bugs.launchpad.net/bugs/1720363.
Closing this report, as it's not an upstream issue.

@monsta monsta closed this as completed Oct 17, 2017
@sunweaver
Copy link
Member

sunweaver commented Oct 17, 2017 via email

@monsta
Copy link
Contributor

monsta commented Oct 18, 2017

Thanks 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants