@Alkis: I added a comment on the new bug. Let's talk there. This one is
closed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1762952
Title:
Alternative shortcut
Hi, this fix caused a regression in ubiquity: LP: #1892014
Ubiquity doesn't put alt_shift_toggle in XKBOPTIONS anymore, so we
cannot switch to e.g. Greek using Alt+Shift, after going through a
normal installation (or even in the live session).
Are users expected to manually run `dpkg-reconfigure
Thank you https://launchpad.net/~gunnarhj for your advice. I report this
on https://gitlab.gnome.org/GNOME/gnome-control-center/issues/290
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
This bug made using emacs and IntelliJ Idea a nuisance. I found a simple
workaround.
0
=1=
You can verify how ALT and SHIFT are not being detected simultaneously by
running
$ xkbwatch
Notice how the blinky lights change for ALT and for SHIFT but not for
both at the same time.
=2=
$ setxkbmap
This bug was fixed in the package console-setup - 1.178ubuntu2.6
---
console-setup (1.178ubuntu2.6) bionic; urgency=medium
* keyboard-configuration.config: Only treat missing XKBOPTIONS as
empty.
console-setup (1.178ubuntu2.5) bionic; urgency=medium
*
Hmm.. Another build attempt succeeded without changes.
I went through step 1 -3 in the test case in the bug description, thus
upgraded to version 1.178ubuntu2.6 of keyboard-configuraion, console-
setup and console-setup-linux from bionic-proposed. The result:
$ cat /etc/default/keyboard
1.178ubuntu2.6 failed to build. My original patch:
https://launchpadlibrarian.net/370321046/console-setup_lp1762952.debdiff
contains proposed changed to d/control and d/rules which would prevent
those build errors.
--
You received this bug notification because you are a member of Ubuntu
Touch
This bug was fixed in the package console-setup - 1.178ubuntu8
---
console-setup (1.178ubuntu8) cosmic; urgency=medium
* keyboard-configuration.config: Only treat missing XKBOPTIONS as
empty.
-- Adam Conrad Wed, 08 Aug 2018 17:32:23 -0600
** Changed in: console-setup (Ubuntu)
Hello Markus, or anyone else affected,
Accepted console-setup into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/console-
setup/1.178ubuntu2.6 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
** Changed in: console-setup (Ubuntu Bionic)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1762952
Title:
Alternative
I went through step 1 -3 in the test case in the bug description, thus
upgraded to version 1.178ubuntu2.4 of keyboard-configuraion, console-
setup and console-setup-linux from bionic-proposed. The result:
$ cat /etc/default/keyboard
XKBLAYOUT="se,us"
BACKSPACE="guess"
XKBVARIANT=","
Hello Adam, or anyone else affected,
Accepted console-setup into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/console-
setup/1.178ubuntu2.4 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
This bug was fixed in the package console-setup - 1.178ubuntu6
---
console-setup (1.178ubuntu6) cosmic; urgency=medium
* keyboard-configuration.{config,templates}: There is no good default for
layout toggling, stop pretending there is. Console users can set one
with
** Changed in: console-setup (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: console-setup (Ubuntu)
Assignee: Gunnar Hjalmarsson (gunnarhj) => Adam Conrad (adconrad)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
@Adam: Sad to hear that the proposed fix caused yet another regression,
and sorry for the inconvenience it caused.
On 2018-07-25 03:31, Adam Conrad wrote:
> That said, I think the "run it sometimes, but not always" fix was
> probably naive at best. The only two options that seem to make
> sense
Re-opening this bug as we had to revert the fix, because it was causing
an installer regression:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1783326
That said, I think the "run it sometimes, but not always" fix was
probably naive at best. The only two options that seem to make sense
This bug was fixed in the package console-setup - 1.178ubuntu2.2
---
console-setup (1.178ubuntu2.2) bionic; urgency=medium
* debian/console-setup-udeb.postinst: Guard the dpkg call in the postinst,
so it isn't attempted in the debian-installer environment (LP: #1782835)
Verified the test case again, this time by upgrading from version
1.178ubuntu2 to 1.178ubuntu2.2, which was uploaded to address the
regression reported in bug #1782835.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
Hello Markus, or anyone else affected,
Accepted console-setup into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/console-
setup/1.178ubuntu2.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Verified the test case by upgrading to version 1.178ubuntu2.1 of
- console-setup
- console-setup-linux
- keyboard-configuration
from bionic-proposed. Result as expected.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
Hey Gunnar! The build just now succeeded after a re-run (?). Probably
some race-condition with the current package dependencies. Anyway, since
the package is built let's not re-upload for no reason. You can proceed
with testing!
--
You received this bug notification because you are a member of
The build failed.
[error] cannot read character map directory `/usr/share/i18n/charmaps':
No such file or directory
Looks like those extra changes, which I proposed in the original patch -
and which proved to not be needed in cosmic - make a difference in
bionic. (Yes, Łukasz, as you suggested
Hello Markus, or anyone else affected,
Accepted console-setup into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/console-
setup/1.178ubuntu2.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
** Changed in: console-setup (Ubuntu Bionic)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1762952
Title:
Alternative
Hi Łukasz, I changed the bug description and added a test case.
Hopefully that is sufficient to proceed with the bionic upload.
** Description changed:
+ [Impact]
+
+ The keyboard-configuration package provides a tool for configuring the
+ keyboard via /etc/default/keyboard. However, there are
@yoosofan: Several options, including CapsLock, are available to switch
layout. If you want to suggest that to be the default option in Ubuntu,
you'd better approach the GNOME developers:
https://gitlab.gnome.org/GNOME/gnome-control-center/issues
(The discussion seems unrelated to this bug.)
--
Is there a reason why we cannot use CapsLock for changing layout?
CapsLock is the most simplest key for changing layout when you want to work
with both hand while writing a mixed text of two language. Actually CapsLock
does not use to its main function because people barely write with a lot of
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: console-setup (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
** Changed in: gnome-control-center (Ubuntu)
Status: Confirmed => Invalid
** Changed in: gnome-control-center (Ubuntu Bionic)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup
This bug was fixed in the package console-setup - 1.178ubuntu3
---
console-setup (1.178ubuntu3) cosmic; urgency=medium
* debian/keyboard-configuration.postinst:
- Don't change /etc/default/keyboard at package upgrades on
desktops, since it may conflict with how desktops
Once this migrates to cosmic release, I'll SRU it to bionic.
** Also affects: console-setup (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: gnome-control-center (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification
I somehow forgot about this bug! Ok, I think I know now what you're
aiming for. Normally just checking for the existence of $2 would be
sufficient but not if we're expecting the config changes to happen on
package reinstall. I guess it's just a matter of design here - I
obviously was thinking of
Yet another example:
https://askubuntu.com/q/1048831
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1762952
Title:
Alternative shortcut for layout switching
To make sure that I'm not wandering, I made an own experiment, where I
put some code in postinst which prints the variables. (I uploaded it to
the same PPA.) Please see the result in the attached file.
So, considering that we must distinguish between upgrades and pure
configuration, only testing
Ok. Please note that I never tested a *first* install of keyboard-
configuration (hard to do due to dependencies). Besides upgrade I tested
reinstall and "dpkg-reconfigure keyboard-configuration". Especially in
the latter case it's obviously important that all the postinst code does
run.
--
You
It shouldn't be like that. I just now did an experiment with a new empty
package and I only saw $2 having the version number for upgrades - on
first install $2 was empty. Anyway, I'll take your changes, tweak them a
little bit and sponsor if they seem to work as expected.
--
You received this
When studying the variables I put a code snippet in postinst and built
the package; something along these lines:
i=1
for p in $@; do
echo "\$$i = $p"
i=$((i+1))
done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Only checking for the existence of $2 was the first thing I tried, after
having read about that method somewhere. What I found when testing was
that $2 always exists when executing postinst in keyboard-configuration.
In case of an upgrade it's the previous package version, and otherwise
it's the
Indeed, this is postinst so the value is "configure" for all successful
upgrades. What could be done is actually only checking if $2 exists or
not, since if I remember correctly we only have postinst configure
called with a version number in the case of upgrades or downgrades -
which I suppose
Thanks for looking, Łukasz.
Right, it didn't build in PPA for me without those. As regards
'locales', according to the build log it looked for and failed to find
/usr/share/i18n/charmaps. As regards the extra install directory in
d/rules, it's obviously needed if the conditions for running the
Thanks for your patch Gunnar! For now I only had a quick look the
changes, was wondering why the debian/control and debian/rules changes
were needed for the PPA upload. It didn't build without those? I would
expect it to not really differ from what would happen in the archive.
Also, from the
On 2018-05-13 04:47, Gunnar Hjalmarsson wrote:
> Those XKB options are probably set by the
> keyboard-configuration.config script in the keyboard-configuration
> package. So maybe we need to figure out a proper way to make that
> script keep its hands off /etc/default/keyboard when a desktop is
>
** Package changed: ubuntu-release-upgrader (Ubuntu) => console-setup
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1762952
Title:
Alternative shortcut
43 matches
Mail list logo