[Touch-packages] [Bug 1921781] Re: Build-depends on qt5-default which is obsolete and dropped in hirsute

2021-09-07 Thread Gunnar Hjalmarsson
@Khurshid: indicator-sound was last built several cycles ago. When
trying to build in impish, I met problems which I think go beyond that
qt5-default b-d. (Over my head - gave up.)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to signon-ui in Ubuntu.
https://bugs.launchpad.net/bugs/1921781

Title:
  Build-depends on qt5-default which is obsolete and dropped in hirsute

Status in indicator-sound package in Ubuntu:
  Confirmed
Status in libqofono package in Ubuntu:
  Fix Released
Status in poppler-qml-plugin package in Ubuntu:
  Fix Released
Status in qtpowerd package in Ubuntu:
  Fix Released
Status in qtubuntu-cameraplugin-fake package in Ubuntu:
  Fix Released
Status in signon-keyring-extension package in Ubuntu:
  Fix Released
Status in signon-plugin-sasl package in Ubuntu:
  Fix Released
Status in signon-ui package in Ubuntu:
  Fix Released
Status in unity-api package in Ubuntu:
  Fix Released
Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  These packages build-depend on the qt5-default package, which has been
  dropped upstream in Debian and will not be available in the hirsute
  release.

  These packages should either be updated to not require this build-
  dependency, or be removed from hirsute.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1921781/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1761382] Re: Unable to connect to ibus: Could not connect: Connection refused

2021-09-05 Thread Gunnar Hjalmarsson
I can't reproduce this on the 21.10 development version of Ubuntu. Would
anybody mind if we close this bug report?

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => Incomplete

** Changed in: ibus (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1761382

Title:
  Unable to connect to ibus: Could not connect: Connection refused

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  Get this logged:

  oem@ubuntu:~$ journalctl -b | grep ibus

  dbus-daemon[1074]: [session uid=120 pid=1074] Activating service
  name='org.freedesktop.portal.IBus' requested by ':1.18' (uid=120
  pid=1135 comm="ibus-daemon --xim --panel disable " label="unconfined")

  gnome-shell[1084]: Unable to connect to ibus: Could not connect:
  Connection refused

  /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment:
  setting QT_IM_MODULE=ibus

  /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment:
  setting XMODIFIERS=@im=ibus

  /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment:
  setting GTK_IM_MODULE=ibus

  dbus-daemon[1293]: [session uid=1000 pid=1293] Activating service
  name='org.freedesktop.portal.IBus' requested by ':1.27' (uid=1000
  pid=1458 comm="ibus-daemon --xim --panel disable " label="unconfined")

  gnome-shell[1435]: Unable to connect to ibus: Could not connect:
  Connection refused

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Apr  5 07:43:59 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1761382/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1900640] Re: Ubuntu 20.04 has no capability of surrounding-text feature

2021-09-05 Thread Gunnar Hjalmarsson
According to upstream this is an issue with Google Chrome and gnome-
terminal and not IBus.

A workaround when using ibus-libthai is to choose the "No Check" option
under the "Input sequence check mode" category.

** Changed in: ibus (Ubuntu)
   Importance: Medium => Undecided

** Changed in: ibus (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1900640

Title:
  Ubuntu 20.04 has no capability of surrounding-text feature

Status in ibus:
  Unknown
Status in ibus package in Ubuntu:
  Invalid

Bug description:
  I recently upgrade my Ubuntu LTS from 18.04 to 20.04.
  After the upgrade, I failed to type Thai text with any combining character in 
some apps.
  The log contains this error message:
  `gnome-shell[2076]: (google-chrome-stable:2069): IBUS-WARNING **: 
09:07:10.843: google-chrome-stable has no capability of surrounding-text 
feature`
  `gnome-terminal-[2589]: gnome-terminal-server has no capability of 
surrounding-text feature`

  Expected behavior: Capable of typing any Thai character in any app.
  Actual behavior: Only few apps support typing Thai character, e.g. Firefox, 
Gnome Text Editor.

  Step to reproduce:
  1. Boot up the machine.
  2. Open Google Chrome.
  3. Switch keyboard layout to `Thai (LibThai)`
  4. Type Thai text "กิน" which is equals to following keystroke "dbo" but with 
Thai keyboard layout.

  
  Current workaround:
  Whenever you want to type Thai switch 
  1. Open `Gnome Text Editor`
  2. Switch keyboard layout to `Thai (LibThai)`
  3. Switch to Chrome
  4. Type Thai

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1900640/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1922186] Re: ibus very difficult to restart

2021-09-05 Thread Gunnar Hjalmarsson
The behavior when starting ibus-daemon from IBus Preferences was fixed
in ibus 1.5.25-2.

** Changed in: ibus (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1922186

Title:
  ibus very difficult to restart

Status in ibus:
  New
Status in ibus package in Ubuntu:
  Fix Released

Bug description:
  After closing ibus by task bar -> icon -> rightclick -> `Close` it
  seems to be impossible to restart it.

  Here some ways that should work and how they fail:

  1) Menu -> ibus
  -
  - opens iBus settings 
  - starts ibus service

  Problems:
- No keyboard input is actually processed; I.e. cannot use keyboard then.
- Service is not daemonized; I.e. as soon as the iBus settings window is 
closed, the services quits.

  Suggestion:
- No keyboard input possible seems to be a bug -> should be fixed.
- Service should be daemonized at this point

  2) terminal -> `ibus start`
  ---
  Problems:
- This command does not exist. One has to know, that `ibus-daemon` is the 
one they are searching for.

  Suggestions:
- Implement this command to start the daemon from here

  3) terminal -> `ibus-daemon &` / `ibus-daemon -d`
  -
   - brings up ibus with usable keyboard (good)

  Problems: 
- As soon as terminal gets closed, ibus-daemon quits

  4) terminal -> `nohup ibus-daemon &`
  -
   - brings up ibus with usable keyboard (good)

  Problem: 
- As soon as terminal gets closed, ibus-daemon quits (very strange. 
something I wouldn't expect from a `nohup` call, by the way).

  System
  ===

  - I use ibus in conjunction with ibus-anthy

  
  lsb_release -rd
  --
  Description:  Ubuntu 20.10
  Release:  20.10

  
  apt-cache policy ibus
  --
  ibus:
Installed: 1.5.23-0ubuntu1
Candidate: 1.5.23-0ubuntu1
Version table:
   *** 1.5.23-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status

  
  apt-cache policy ibus-anthy
  --
  ibus-anthy:
Installed: 1.5.11-1build1
Candidate: 1.5.11-1build1
Version table:
   *** 1.5.11-1build1 500
  500 http://archive.ubuntu.com/ubuntu groovy/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ibus 1.5.23-0ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-45.51-generic 5.8.18
  Uname: Linux 5.8.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Thu Apr  1 15:33:00 2021
  RebootRequiredPkgs:
   linux-image-5.8.0-48-generic
   linux-base
   linux-image-5.8.0-49-generic
   linux-base
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1922186/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1939413] Re: /usr/lib/aarch64-linux-gnu/libprotobuf.a’ generated with LTO version 9.2 instead of the expected 11.0

2021-09-04 Thread Gunnar Hjalmarsson
While the rebuild allowed for mozc to build on arm64, as Matthias
pointed out there is a root cause that remains to be dealt with, so re-
opening.

** Changed in: protobuf (Ubuntu)
   Status: Fix Released => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to protobuf in Ubuntu.
https://bugs.launchpad.net/bugs/1939413

Title:
  /usr/lib/aarch64-linux-gnu/libprotobuf.a’ generated with LTO version
  9.2 instead of the expected 11.0

Status in mozc package in Ubuntu:
  Invalid
Status in protobuf package in Ubuntu:
  Triaged

Bug description:
  When trying to build package mozc for arm64 the following error popped
  up:

  lto1: fatal error: bytecode stream in file ‘/usr/lib/aarch64-linux-
  gnu/libprotobuf.a’ generated with LTO version 9.2 instead of the
  expected 11.0

  Why does the library contain LTO information at all?

  Best regards

  Heinrich

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1939413/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1756547] Re: LP refuses to import plural strings where e.g. msgstr[0] entries in PO file miss %d

2021-09-02 Thread Gunnar Hjalmarsson
Go to:

https://translations.launchpad.net/ubuntu/impish/+source/gnome-
shell/+imports

and open the info for e.g. po/kk.po. It tells you that this part from
the PO file was not imported:

#~ msgid "%d new message"
#~ msgid_plural "%d new messages"
#~ msgstr[0] "%d жаңа хабарлама"

#~ msgid "%d new notification"
#~ msgid_plural "%d new notifications"
#~ msgstr[0] "%d жаңа ескерту"

But those entries are marked with '#~', i.e. they are old entries from a
previous version of the template. So what I'm wondering is if it's
sensible that LP validates and tries to import such entries.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gettext in Ubuntu.
https://bugs.launchpad.net/bugs/1756547

Title:
  LP refuses to import plural strings where e.g. msgstr[0] entries in PO
  file miss %d

Status in Launchpad itself:
  Fix Released
Status in Ubuntu Translations:
  Triaged
Status in gettext package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  Some strings of GNOME Shell are untranslated in the Czech translation
  on Ubuntu 18.04 although they are translated upstream and when I try
  to manually translate them on launchpad, I get this error: "number of
  format specifications in 'msgid_plural' and 'msgstr[0]' does not
  match".

  The bad strings are:
  %d minute ago
  %d minutes ago

  %d hour ago
  %d hours ago

  %d week ago
  %d weeks ago

  %d month ago
  %d months ago

  %d year ago
  %d years ago

  They seem to be correct, but they are not accepted for some reason.

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1756547/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1756547] Re: LP refuses to import plural strings where e.g. msgstr[0] entries in PO file miss %d

2021-09-01 Thread Gunnar Hjalmarsson
I uploaded gnome-shell without the workaround.

The original problem, i.e. refusal to import msgstr[0] strings without
%d, is not present any longer.

It complains about the Turkish PO file, but those complaints are
probably motivated due to absent msgstr[1] lines in the upstream PO.

Other complaints, which were there also when the workaround (i.e.
deleted "#, javascript-format" lines in the POT) was in place, are about
strings which are no longer in the POT, and hence don't matter much.
@Colin: Does LP really try to import such strings?

** Changed in: gnome-shell (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gettext in Ubuntu.
https://bugs.launchpad.net/bugs/1756547

Title:
  LP refuses to import plural strings where e.g. msgstr[0] entries in PO
  file miss %d

Status in Launchpad itself:
  Fix Released
Status in Ubuntu Translations:
  Triaged
Status in gettext package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  Some strings of GNOME Shell are untranslated in the Czech translation
  on Ubuntu 18.04 although they are translated upstream and when I try
  to manually translate them on launchpad, I get this error: "number of
  format specifications in 'msgid_plural' and 'msgstr[0]' does not
  match".

  The bad strings are:
  %d minute ago
  %d minutes ago

  %d hour ago
  %d hours ago

  %d week ago
  %d weeks ago

  %d month ago
  %d months ago

  %d year ago
  %d years ago

  They seem to be correct, but they are not accepted for some reason.

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1756547/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1756547] Re: LP refuses to import plural strings where e.g. msgstr[0] entries in PO file miss %d

2021-08-28 Thread Gunnar Hjalmarsson
Re-opening — see bug #1941954

** Changed in: gnome-shell (Ubuntu)
   Status: Fix Released => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gettext in Ubuntu.
https://bugs.launchpad.net/bugs/1756547

Title:
  LP refuses to import plural strings where e.g. msgstr[0] entries in PO
  file miss %d

Status in Launchpad itself:
  Confirmed
Status in Ubuntu Translations:
  Triaged
Status in gettext package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  Some strings of GNOME Shell are untranslated in the Czech translation
  on Ubuntu 18.04 although they are translated upstream and when I try
  to manually translate them on launchpad, I get this error: "number of
  format specifications in 'msgid_plural' and 'msgstr[0]' does not
  match".

  The bad strings are:
  %d minute ago
  %d minutes ago

  %d hour ago
  %d hours ago

  %d week ago
  %d weeks ago

  %d month ago
  %d months ago

  %d year ago
  %d years ago

  They seem to be correct, but they are not accepted for some reason.

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1756547/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1939413] Re: /usr/lib/aarch64-linux-gnu/libprotobuf.a’ generated with LTO version 9.2 instead of the expected 11.0

2021-08-12 Thread Gunnar Hjalmarsson
Thanks for reporting this, Heinrich! It looks like protobuf needs to be
built with gcc-11.

** Changed in: protobuf (Ubuntu)
   Status: New => Fix Committed

** Changed in: protobuf (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Changed in: mozc (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to protobuf in Ubuntu.
https://bugs.launchpad.net/bugs/1939413

Title:
  /usr/lib/aarch64-linux-gnu/libprotobuf.a’ generated with LTO version
  9.2 instead of the expected 11.0

Status in mozc package in Ubuntu:
  Invalid
Status in protobuf package in Ubuntu:
  Fix Committed

Bug description:
  When trying to build package mozc for arm64 the following error popped
  up:

  lto1: fatal error: bytecode stream in file ‘/usr/lib/aarch64-linux-
  gnu/libprotobuf.a’ generated with LTO version 9.2 instead of the
  expected 11.0

  Why does the library contain LTO information at all?

  Best regards

  Heinrich

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1939413/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1939413] Re: /usr/lib/aarch64-linux-gnu/libprotobuf.a’ generated with LTO version 9.2 instead of the expected 11.0

2021-08-11 Thread Gunnar Hjalmarsson
This is an example build log:

https://launchpadlibrarian.net/552672484/buildlog_ubuntu-impish-
arm64.mozc_2.26.4220.100+dfsg-4ubuntu3_BUILDING.txt.gz

from the impish test rebuild:

https://lists.ubuntu.com/archives/ubuntu-devel-
announce/2021-August/001294.html

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to protobuf in Ubuntu.
https://bugs.launchpad.net/bugs/1939413

Title:
  /usr/lib/aarch64-linux-gnu/libprotobuf.a’ generated with LTO version
  9.2 instead of the expected 11.0

Status in mozc package in Ubuntu:
  New
Status in protobuf package in Ubuntu:
  New

Bug description:
  When trying to build package mozc for arm64 the following error popped
  up:

  lto1: fatal error: bytecode stream in file ‘/usr/lib/aarch64-linux-
  gnu/libprotobuf.a’ generated with LTO version 9.2 instead of the
  expected 11.0

  Why does the library contain LTO information at all?

  Best regards

  Heinrich

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1939413/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1939413] Re: /usr/lib/aarch64-linux-gnu/libprotobuf.a’ generated with LTO version 9.2 instead of the expected 11.0

2021-08-11 Thread Gunnar Hjalmarsson
** Also affects: mozc (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: ftbfs impish

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to protobuf in Ubuntu.
https://bugs.launchpad.net/bugs/1939413

Title:
  /usr/lib/aarch64-linux-gnu/libprotobuf.a’ generated with LTO version
  9.2 instead of the expected 11.0

Status in mozc package in Ubuntu:
  New
Status in protobuf package in Ubuntu:
  New

Bug description:
  When trying to build package mozc for arm64 the following error popped
  up:

  lto1: fatal error: bytecode stream in file ‘/usr/lib/aarch64-linux-
  gnu/libprotobuf.a’ generated with LTO version 9.2 instead of the
  expected 11.0

  Why does the library contain LTO information at all?

  Best regards

  Heinrich

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mozc/+bug/1939413/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1931994] Re: [Ubuntu 20.04] OpenSSL bugs in the s390x AES code

2021-08-09 Thread Gunnar Hjalmarsson
I mean (for respective series):

* Accomplish the steps in the Test Plan
* Disclose the result in a comment here
* Change the verification-needed- tag to verification-done-

See comment #22 - #24.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1931994

Title:
  [Ubuntu 20.04] OpenSSL bugs in the s390x AES code

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Bionic:
  Fix Committed
Status in openssl source package in Focal:
  Fix Committed
Status in openssl source package in Hirsute:
  Fix Committed
Status in openssl source package in Impish:
  Fix Released

Bug description:
  Problem description:

  When passing a NULL key to reset AES EVC state, the state wouldn't be 
completely reset on s390x.
  https://github.com/openssl/openssl/pull/14900

  Solution available here:
  
https://github.com/openssl/openssl/commit/dc67210d909b5dd7a50f60a96f36f3f5a891b1c8

  Should be applied to all distros where openssl 1.1.1 is included for 
consistency reason.
  -> 21.10, 20.04, 18.04.
  I think not needed for 16.04 anymore

  [Test plan]

  $ sudo apt install libssl-dev
  $ gcc test.c -o evc-test -lcrypto -lssl # See 
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1931994/comments/2 for 
the test.c program
  $ ./evc-test && echo OK

  [Where problems could occur]

  This patch only touches s390x code paths, so there shouldn't be any 
regression on other architectures. However, on s390x this could reveal
  latent bugs by spreading a NULL key to new code paths.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931994/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1931994] Re: [Ubuntu 20.04] OpenSSL bugs in the s390x AES code

2021-08-08 Thread Gunnar Hjalmarsson
@Simon: You know that the packages in respective -proposed pocket need
to be verified too, right?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1931994

Title:
  [Ubuntu 20.04] OpenSSL bugs in the s390x AES code

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Bionic:
  Fix Committed
Status in openssl source package in Focal:
  Fix Committed
Status in openssl source package in Hirsute:
  Fix Committed
Status in openssl source package in Impish:
  Fix Released

Bug description:
  Problem description:

  When passing a NULL key to reset AES EVC state, the state wouldn't be 
completely reset on s390x.
  https://github.com/openssl/openssl/pull/14900

  Solution available here:
  
https://github.com/openssl/openssl/commit/dc67210d909b5dd7a50f60a96f36f3f5a891b1c8

  Should be applied to all distros where openssl 1.1.1 is included for 
consistency reason.
  -> 21.10, 20.04, 18.04.
  I think not needed for 16.04 anymore

  [Test plan]

  $ sudo apt install libssl-dev
  $ gcc test.c -o evc-test -lcrypto -lssl # See 
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1931994/comments/2 for 
the test.c program
  $ ./evc-test && echo OK

  [Where problems could occur]

  This patch only touches s390x code paths, so there shouldn't be any 
regression on other architectures. However, on s390x this could reveal
  latent bugs by spreading a NULL key to new code paths.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931994/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1931994] Re: [Ubuntu 20.04] OpenSSL bugs im s390x AES code

2021-07-27 Thread Gunnar Hjalmarsson
I re-run the failed tests, and both of them passed on the second
attempt, so it should migrate on impish soon.

The SRUs are now uploaded, following Brian's advice with respect to
hirsute.

@Simon: Good if you can unsubscribe ubuntu-sponsors.

** Changed in: openssl (Ubuntu Hirsute)
   Status: New => In Progress

** Changed in: openssl (Ubuntu Hirsute)
 Assignee: (unassigned) => Canonical Foundations Team 
(canonical-foundations)

** Changed in: openssl (Ubuntu Focal)
   Status: New => In Progress

** Changed in: openssl (Ubuntu Focal)
 Assignee: (unassigned) => Canonical Foundations Team 
(canonical-foundations)

** Changed in: openssl (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: openssl (Ubuntu Bionic)
 Assignee: (unassigned) => Canonical Foundations Team 
(canonical-foundations)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1931994

Title:
  [Ubuntu 20.04] OpenSSL bugs im s390x AES code

Status in Ubuntu on IBM z Systems:
  In Progress
Status in openssl package in Ubuntu:
  Fix Committed
Status in openssl source package in Bionic:
  In Progress
Status in openssl source package in Focal:
  In Progress
Status in openssl source package in Hirsute:
  In Progress
Status in openssl source package in Impish:
  Fix Committed

Bug description:
  Problem description:

  When passing a NULL key to reset AES EVC state, the state wouldn't be 
completely reset on s390x.
  https://github.com/openssl/openssl/pull/14900

  Solution available here:
  
https://github.com/openssl/openssl/commit/dc67210d909b5dd7a50f60a96f36f3f5a891b1c8

  Should be applied to all distros where openssl 1.1.1 is included for 
consistency reason.
  -> 21.10, 20.04, 18.04.
  I think not needed for 16.04 anymore

  [Test plan]

  $ sudo apt install libssl-dev
  $ gcc test.c -o evc-test -lcrypto -lssl # See 
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1931994/comments/2 for 
the test.c program
  $ ./evc-test && echo OK

  [Where problems could occur]

  This patch only touches s390x code paths, so there shouldn't be any 
regression on other architectures. However, on s390x this could reveal
  latent bugs by spreading a NULL key to new code paths.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931994/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1931994] Re: [Ubuntu 20.04] OpenSSL bugs im s390x AES code

2021-07-27 Thread Gunnar Hjalmarsson
@Simon: autopkgtest for mosquitto and puma fails on s390x.

https://people.canonical.com/~ubuntu-archive/proposed-
migration/update_excuses.html#openssl

Please investigate.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1931994

Title:
  [Ubuntu 20.04] OpenSSL bugs im s390x AES code

Status in Ubuntu on IBM z Systems:
  In Progress
Status in openssl package in Ubuntu:
  Fix Committed
Status in openssl source package in Bionic:
  New
Status in openssl source package in Focal:
  New
Status in openssl source package in Hirsute:
  New
Status in openssl source package in Impish:
  Fix Committed

Bug description:
  Problem description:

  When passing a NULL key to reset AES EVC state, the state wouldn't be 
completely reset on s390x.
  https://github.com/openssl/openssl/pull/14900

  Solution available here:
  
https://github.com/openssl/openssl/commit/dc67210d909b5dd7a50f60a96f36f3f5a891b1c8

  Should be applied to all distros where openssl 1.1.1 is included for 
consistency reason.
  -> 21.10, 20.04, 18.04.
  I think not needed for 16.04 anymore

  [Test plan]

  $ sudo apt install libssl-dev
  $ gcc test.c -o evc-test -lcrypto -lssl # See 
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1931994/comments/2 for 
the test.c program
  $ ./evc-test && echo OK

  [Where problems could occur]

  This patch only touches s390x code paths, so there shouldn't be any 
regression on other architectures. However, on s390x this could reveal
  latent bugs by spreading a NULL key to new code paths.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931994/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1937922] Re: gtk4 not built for i386

2021-07-27 Thread Gunnar Hjalmarsson
gtk4 has now been built on i386 - thanks Steve! - and I have uploaded
ibus with gtk4 support (needs to be approved in the NEW queue).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1937922

Title:
  gtk4 not built for i386

Status in gtk4 package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  In Progress

Bug description:
  I'm trying to enable GTK 4 when building ibus:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus2/+packages

  Up to now ibus has been built also on i386, but gtk4 has not been
  built on that arch, so the i386 build fails due to missing build
  dependencies.

  Is it time to stop building ibus on i386? Or can we build gtk4 on i386
  (it was successfully built on Debian's i386)?

  At least some step needs to be taken.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/1937922/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1937922] Re: gtk4 not built for i386

2021-07-27 Thread Gunnar Hjalmarsson
** Also affects: gtk4 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gtk4 (Ubuntu)
   Status: New => Fix Released

** Changed in: ibus (Ubuntu)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1937922

Title:
  gtk4 not built for i386

Status in gtk4 package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  In Progress

Bug description:
  I'm trying to enable GTK 4 when building ibus:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus2/+packages

  Up to now ibus has been built also on i386, but gtk4 has not been
  built on that arch, so the i386 build fails due to missing build
  dependencies.

  Is it time to stop building ibus on i386? Or can we build gtk4 on i386
  (it was successfully built on Debian's i386)?

  At least some step needs to be taken.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/1937922/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1931994] Re: [Ubuntu 20.04] OpenSSL bugs im s390x AES code

2021-07-26 Thread Gunnar Hjalmarsson
Sponsored impish for now.

As regards the SRUs, I suppose that the block-proposed-hirsute tag set
at bug #1927161 needs to be removed. Also, should the test plan be
expanded to include the test script which bugproxy added?

** Changed in: openssl (Ubuntu Impish)
   Status: New => Fix Committed

** No longer affects: openssl (Ubuntu Groovy)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1931994

Title:
  [Ubuntu 20.04] OpenSSL bugs im s390x AES code

Status in Ubuntu on IBM z Systems:
  In Progress
Status in openssl package in Ubuntu:
  Fix Committed
Status in openssl source package in Bionic:
  New
Status in openssl source package in Focal:
  New
Status in openssl source package in Hirsute:
  New
Status in openssl source package in Impish:
  Fix Committed

Bug description:
  Problem description:

  When passing a NULL key to reset AES EVC state, the state wouldn't be 
completely reset on s390x.
  https://github.com/openssl/openssl/pull/14900

  Solution available here:
  
https://github.com/openssl/openssl/commit/dc67210d909b5dd7a50f60a96f36f3f5a891b1c8

  Should be applied to all distros where openssl 1.1.1 is included for 
consistency reason.
  -> 21.10, 20.04, 18.04.
  I think not needed for 16.04 anymore

  [Test plan]

  $ sudo apt install libssl-dev
  $ gcc test.c -o evc-test -lcrypto -lssl # See 
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1931994/comments/2 for 
the test.c program
  $ ./evc-test && echo OK

  [Where problems could occur]

  This patch only touches s390x code paths, so there shouldn't be any 
regression on other architectures. However, on s390x this could reveal
  latent bugs by spreading a NULL key to new code paths.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931994/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1937922] Re: gtk4 not built for i386

2021-07-26 Thread Gunnar Hjalmarsson
@Steve: I suppose this is now a request to add gtk4 to the whitelist, so
I subscribed ubuntu-archive.

I can't tell if any of the current i386 packages will use gtk4. But ibus
needs gtk4 when building to be able to enable gtk4 support, and it would
be convenient to not need to special case i386 and with that create a
permanent Ubuntu/Debian delta. So at least for now it would be great if
gtk4 could be added to the list explicitly.

** Changed in: ibus (Ubuntu)
   Status: Incomplete => New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1937922

Title:
  gtk4 not built for i386

Status in ibus package in Ubuntu:
  New

Bug description:
  I'm trying to enable GTK 4 when building ibus:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus2/+packages

  Up to now ibus has been built also on i386, but gtk4 has not been
  built on that arch, so the i386 build fails due to missing build
  dependencies.

  Is it time to stop building ibus on i386? Or can we build gtk4 on i386
  (it was successfully built on Debian's i386)?

  At least some step needs to be taken.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1937922/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1937922] Re: gtk4 not built for i386

2021-07-26 Thread Gunnar Hjalmarsson
https://irclogs.ubuntu.com/2021/07/26/%23ubuntu-desktop.html#t12:23

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1937922

Title:
  gtk4 not built for i386

Status in ibus package in Ubuntu:
  New

Bug description:
  I'm trying to enable GTK 4 when building ibus:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus2/+packages

  Up to now ibus has been built also on i386, but gtk4 has not been
  built on that arch, so the i386 build fails due to missing build
  dependencies.

  Is it time to stop building ibus on i386? Or can we build gtk4 on i386
  (it was successfully built on Debian's i386)?

  At least some step needs to be taken.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1937922/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1937922] [NEW] gtk4 not built for i386

2021-07-24 Thread Gunnar Hjalmarsson
Public bug reported:

I'm trying to enable GTK 4 when building ibus:

https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus2/+packages

Up to now ibus has been built also on i386, but gtk4 has not been built
on that arch, so the i386 build fails due to missing build dependencies.

Is it time to stop building ibus on i386? Or can we build gtk4 on i386
(it was successfully built on Debian's i386)?

At least some step needs to be taken.

** Affects: ibus (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1937922

Title:
  gtk4 not built for i386

Status in ibus package in Ubuntu:
  New

Bug description:
  I'm trying to enable GTK 4 when building ibus:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus2/+packages

  Up to now ibus has been built also on i386, but gtk4 has not been
  built on that arch, so the i386 build fails due to missing build
  dependencies.

  Is it time to stop building ibus on i386? Or can we build gtk4 on i386
  (it was successfully built on Debian's i386)?

  At least some step needs to be taken.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1937922/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1922186] Re: ibus very difficult to restart

2021-06-09 Thread Gunnar Hjalmarsson
Hey, how about getting a more constructive hobby than killing various
important processes on your system? ;)

More seriously: I'm not sure that "ibus restart" is intended to handle
such situations. But please feel free to comment on the issue I
submitted — the upstream maintainer hasn't attended to it yet. Or,
probably better, submit an own upstream issue since they are separate
things.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1922186

Title:
  ibus very difficult to restart

Status in ibus:
  New
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  After closing ibus by task bar -> icon -> rightclick -> `Close` it
  seems to be impossible to restart it.

  Here some ways that should work and how they fail:

  1) Menu -> ibus
  -
  - opens iBus settings 
  - starts ibus service

  Problems:
- No keyboard input is actually processed; I.e. cannot use keyboard then.
- Service is not daemonized; I.e. as soon as the iBus settings window is 
closed, the services quits.

  Suggestion:
- No keyboard input possible seems to be a bug -> should be fixed.
- Service should be daemonized at this point

  2) terminal -> `ibus start`
  ---
  Problems:
- This command does not exist. One has to know, that `ibus-daemon` is the 
one they are searching for.

  Suggestions:
- Implement this command to start the daemon from here

  3) terminal -> `ibus-daemon &` / `ibus-daemon -d`
  -
   - brings up ibus with usable keyboard (good)

  Problems: 
- As soon as terminal gets closed, ibus-daemon quits

  4) terminal -> `nohup ibus-daemon &`
  -
   - brings up ibus with usable keyboard (good)

  Problem: 
- As soon as terminal gets closed, ibus-daemon quits (very strange. 
something I wouldn't expect from a `nohup` call, by the way).

  System
  ===

  - I use ibus in conjunction with ibus-anthy

  
  lsb_release -rd
  --
  Description:  Ubuntu 20.10
  Release:  20.10

  
  apt-cache policy ibus
  --
  ibus:
Installed: 1.5.23-0ubuntu1
Candidate: 1.5.23-0ubuntu1
Version table:
   *** 1.5.23-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status

  
  apt-cache policy ibus-anthy
  --
  ibus-anthy:
Installed: 1.5.11-1build1
Candidate: 1.5.11-1build1
Version table:
   *** 1.5.11-1build1 500
  500 http://archive.ubuntu.com/ubuntu groovy/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ibus 1.5.23-0ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-45.51-generic 5.8.18
  Uname: Linux 5.8.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Thu Apr  1 15:33:00 2021
  RebootRequiredPkgs:
   linux-image-5.8.0-48-generic
   linux-base
   linux-image-5.8.0-49-generic
   linux-base
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1922186/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1928360] Re: Switch to Fcitx 5 for Chinese

2021-06-04 Thread Gunnar Hjalmarsson
I presented the snap problem for James Henstridge, and he gave me a very
useful hint: The Chromium snap makes use of the bionic library stack
(the gnome-3-28-1804 snap) including the im module installed by fcitx-
frontend-gtk3, i.e. the fcitx 4 gtk im module.

That made me think of . That bug is
still open, and as a result im-config currently sets these variables for
fcitx 5:

GTK_IM_MODULE=fcitx5
XMODIFIERS=@im=fcitx
QT_IM_MODULE=fcitx5

It means that it explicitly looks for the fcitx 5 gtk im module, while
Chromium only has access to the fcitx 4 one.

So as a test I tweaked im-config to set:

GTK_IM_MODULE=fcitx
XMODIFIERS=@im=fcitx
QT_IM_MODULE=fcitx

and that made a difference. With that environment I could successfully
input beautiful Chinese characters in Chromium using fcitx 5. :)

Consequently there seems to be no need to add any extra stuff to
apparmor to handle fcitx 5. Instead I see two options:

1. Change im-config's variable assignment, or

2. somehow add the fcitx 5 im modules for gtk and qt to the snap library
stack.

I'm going to consult with Debian's input method team about which route
is preferable.

@James: Do you see a problem from your POV with adding the fcitx 5 im
modules to the snaps?

** Bug watch added: Debian Bug tracker #977203
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977203

** Also affects: snappy
   Importance: Undecided
   Status: New

** Package changed: apparmor (Ubuntu) => im-config (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1928360

Title:
  Switch to Fcitx 5 for Chinese

Status in Lubuntu default settings:
  New
Status in Snappy:
  New
Status in Ubuntu Kylin:
  In Progress
Status in im-config package in Ubuntu:
  New
Status in language-selector package in Ubuntu:
  Fix Released

Bug description:
  In Debian 11 Fcitx 5 will be the default IM framework for Chinese on
  non-GNOME desktops. I can think it's time to make the equivalent
  changes in Ubuntu 21.10 as well.

  I'd appreciate input on the topic from the Ubuntu Kylin team as well
  as other Chinese speaking users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lubuntu-default-settings/+bug/1928360/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1930145] Re: IBus Panel Show Icon on system tray doesn't persist

2021-06-04 Thread Gunnar Hjalmarsson
I noticed that the issue is present also on Kubuntu 20.04, so it has
been there for a while. It's not present on Ubuntu MATE, though, which
indicates that it's a KDE issue rather than an ibus one.

But @Cory, it would be good if you could clarify why it is a problem. In
short: Why do you want to have ibus-daemon running without seeing which
input source is currently in use? Understanding that would be useful to
determine the importance of the issue.

** Also affects: plasma-desktop (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: plasma-desktop (Ubuntu)
   Status: New => Confirmed

** Tags added: focal hirsute impish

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1930145

Title:
  IBus Panel Show Icon on system tray doesn't persist

Status in ibus package in Ubuntu:
  Incomplete
Status in plasma-desktop package in Ubuntu:
  Confirmed

Bug description:
  After a reboot in Kubuntu 21.04 (and 20.10) the IBus Panel icon
  appears in the system tray despite "Show icon on system tray" NOT
  being checked.  Right clicking on the IBus Panel icon, checking "Show
  icon on system tray" and then unchecking again it causes the icon to
  be correctly hidden.  But the problem reappears after the next reboot.

  Another user reporting what is almost certainly the same behavior:
  https://www.reddit.com/r/kde/comments/j91t8f/ibus_panel_icon_in_system_tray/

  And this is an _identical_ bug report from 2012, so maybe it's a regression 
of some sort?
  https://bugzilla.redhat.com/show_bug.cgi?id=877135

  Based om the trouble shooting requested at that time I get:

  $ gconftool-2 --get /desktop/ibus/panel/show_icon_on_systray
  No value set for `/desktop/ibus/panel/show_icon_on_systray'

  Note that I am running KDE, in case that's the important detail.

  The primary problem is that if you click on it accidentally and close
  the panel, you lose all keyboard input.

  $ lsb_release -rd
  Description:Ubuntu 21.04
  Release:21.04
  $ apt-cache policy ibus
  ibus:
Installed: 1.5.24-1
Candidate: 1.5.24-1
Version table:
   *** 1.5.24-1 500
  500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1930145/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1930145] Re: IBus Panel Show Icon on system tray doesn't persist

2021-05-30 Thread Gunnar Hjalmarsson
Thanks for your report! Yes, it doesn't seem to honor the "Show icon on
system tray" setting at login. Can't tell ATM if ibus or KDE is
responsible for that.

With that said, and considering that you prefer it to not be shown, I
can't help suspecting that ibus is running unnecessarily on your system.

Up to 20.04 ibus was installed for everyone on Kubuntu but only started
by default if the language was Chinese, Japanese, Korean or Vietnamese.
>From 20.10 ibus is not installed for everyone, but if you install it
it's started automatically. The idea is that if ibus is installed it's
assumed that you want to use it. (This can be controlled via the "Input
Method Configuration" GUI.) So unless you use some IBus input method,
the natural solution to fix it for you may be to simply uninstall ibus.

Please clarify your actual use case.

** Changed in: ibus (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1930145

Title:
  IBus Panel Show Icon on system tray doesn't persist

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  After a reboot in Kubuntu 21.04 (and 20.10) the IBus Panel icon
  appears in the system tray despite "Show icon on system tray" NOT
  being checked.  Right clicking on the IBus Panel icon, checking "Show
  icon on system tray" and then unchecking again it causes the icon to
  be correctly hidden.  But the problem reappears after the next reboot.

  Another user reporting what is almost certainly the same behavior:
  https://www.reddit.com/r/kde/comments/j91t8f/ibus_panel_icon_in_system_tray/

  And this is an _identical_ bug report from 2012, so maybe it's a regression 
of some sort?
  https://bugzilla.redhat.com/show_bug.cgi?id=877135

  Based om the trouble shooting requested at that time I get:

  $ gconftool-2 --get /desktop/ibus/panel/show_icon_on_systray
  No value set for `/desktop/ibus/panel/show_icon_on_systray'

  Note that I am running KDE, in case that's the important detail.

  The primary problem is that if you click on it accidentally and close
  the panel, you lose all keyboard input.

  $ lsb_release -rd
  Description:Ubuntu 21.04
  Release:21.04
  $ apt-cache policy ibus
  ibus:
Installed: 1.5.24-1
Candidate: 1.5.24-1
Version table:
   *** 1.5.24-1 500
  500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1930145/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1928360] Re: Switch to Fcitx 5 for Chinese

2021-05-23 Thread Gunnar Hjalmarsson
@Seth: I suppose that the DENIED file I attached in comment #7 does not
help much.

Fcitx 5 is a separate process, i.e. /usr/bin/fcitx5 as opposed to
/usr/bin/fcitx. When in Chromium it behaves as if fcitx5 does not exist,
even if the process runs and I can use fcitx5 in other applications. I
can't even switch to a fcitx5 input method engine when in Chromium, let
alone use such an input engine for typing. Maybe that explains why
nothing fcitx5 related is reflected as DENIED lines.

I'm thinking that maybe there is a need to create the fcitx5 and
fcitx5-strict abstractions using the already existing fcitx and fcitx-
strict abstractions as models.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1928360

Title:
  Switch to Fcitx 5 for Chinese

Status in Lubuntu default settings:
  New
Status in Ubuntu Kylin:
  In Progress
Status in apparmor package in Ubuntu:
  New
Status in language-selector package in Ubuntu:
  Fix Released

Bug description:
  In Debian 11 Fcitx 5 will be the default IM framework for Chinese on
  non-GNOME desktops. I can think it's time to make the equivalent
  changes in Ubuntu 21.10 as well.

  I'd appreciate input on the topic from the Ubuntu Kylin team as well
  as other Chinese speaking users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lubuntu-default-settings/+bug/1928360/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1928360] Re: Switch to Fcitx 5 for Chinese

2021-05-20 Thread Gunnar Hjalmarsson
Thanks handsome_feng!

The Kylin discussion makes me confident that it's fine for Lubuntu as
well. The Lubuntu situation is different, though, since im-config is
disabled by default unless a Chinese locale is in effect. This discourse
topic comes to mind:

https://discourse.ubuntu.com/t/default-im-config-configuration/17136

I'm still interested in talking with some Lubuntu developer on that. But
the outcome of such a discussion would affect other packages but
language-selector, so I just pushed and uploaded the proposed change.

** Changed in: language-selector (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1928360

Title:
  Switch to Fcitx 5 for Chinese

Status in Lubuntu default settings:
  New
Status in Ubuntu Kylin:
  In Progress
Status in apparmor package in Ubuntu:
  New
Status in language-selector package in Ubuntu:
  Fix Committed

Bug description:
  In Debian 11 Fcitx 5 will be the default IM framework for Chinese on
  non-GNOME desktops. I can think it's time to make the equivalent
  changes in Ubuntu 21.10 as well.

  I'd appreciate input on the topic from the Ubuntu Kylin team as well
  as other Chinese speaking users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lubuntu-default-settings/+bug/1928360/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1928360] Re: Switch to Fcitx 5 for Chinese

2021-05-20 Thread Gunnar Hjalmarsson
On 2021-05-20 15:39, handsome_feng wrote:
> With the fcitx items in the current seed, I think pkg_depends don't
> need to pull in the fcitx 4 packages for Ubuntu Kylin 21.10,

Ok, good.

> also it's okay to pull in the fcitx 5 packages, since the im-config
> will set the default input method to fcitx 4 for Ubuntu Kylin 21.10?

Hmm.. Yes, AFAIK that would work. fcitx 4 and fcitx 5 can co-exist, and
if both are installed im-config will pick fcitx 4 by default (can be
changed by the user via Language Support).

Does this mean that the proposed changes to pkg_depends is fine from an
Ubuntu Kylin POV, and that no further changes are needed?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1928360

Title:
  Switch to Fcitx 5 for Chinese

Status in Lubuntu default settings:
  New
Status in Ubuntu Kylin:
  In Progress
Status in apparmor package in Ubuntu:
  New
Status in language-selector package in Ubuntu:
  In Progress

Bug description:
  In Debian 11 Fcitx 5 will be the default IM framework for Chinese on
  non-GNOME desktops. I can think it's time to make the equivalent
  changes in Ubuntu 21.10 as well.

  I'd appreciate input on the topic from the Ubuntu Kylin team as well
  as other Chinese speaking users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lubuntu-default-settings/+bug/1928360/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1928360] Re: Switch to Fcitx 5 for Chinese

2021-05-20 Thread Gunnar Hjalmarsson
@handsome_feng: Great! I have a follow-up question then:

In the desktop seed of Ubuntu Kylin I see these packages:

 * (im-config)
 * (fcitx)
 * (fcitx-frontend-gtk2)
 * (fcitx-frontend-gtk3)
 * (fcitx-frontend-qt5)
 * (fcitx-ui-classic)
 * (fcitx-table)
 * (fcitx-module-cloudpinyin)
 * (fcitx-googlepinyin)

Given that, will it work with the proposed version of pkg_depends, or is
there a reason to keep letting also pkg_depends pull a bunch of fcitx 4
packages for Kylin in 21.10?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1928360

Title:
  Switch to Fcitx 5 for Chinese

Status in Lubuntu default settings:
  New
Status in Ubuntu Kylin:
  In Progress
Status in apparmor package in Ubuntu:
  New
Status in language-selector package in Ubuntu:
  In Progress

Bug description:
  In Debian 11 Fcitx 5 will be the default IM framework for Chinese on
  non-GNOME desktops. I can think it's time to make the equivalent
  changes in Ubuntu 21.10 as well.

  I'd appreciate input on the topic from the Ubuntu Kylin team as well
  as other Chinese speaking users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lubuntu-default-settings/+bug/1928360/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1928360] Re: Switch to Fcitx 5 for Chinese

2021-05-20 Thread Gunnar Hjalmarsson
@handsome_feng: I suppose it is possible. Of course it would have been
desirable to do it in 21.10 to get more time to identify possible issues
before next LTS, but OTOH I know that Sogou is considered important on
Kylin.

Thinking... Maybe we can have it both ways. :) What I mean is that we
could do it now for other flavors, but tell language-selector to not
pull fcitx5 packages on Kylin for now. im-config will keep supporting
both fcitx 4 and 5, and then we would still have reasons to identify and
fix fcitx5 issues with the apparmor profiles in the 21.10 development
cycle.

Would that plan make sense to you?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1928360

Title:
  Switch to Fcitx 5 for Chinese

Status in Lubuntu default settings:
  New
Status in Ubuntu Kylin:
  In Progress
Status in apparmor package in Ubuntu:
  New
Status in language-selector package in Ubuntu:
  In Progress

Bug description:
  In Debian 11 Fcitx 5 will be the default IM framework for Chinese on
  non-GNOME desktops. I can think it's time to make the equivalent
  changes in Ubuntu 21.10 as well.

  I'd appreciate input on the topic from the Ubuntu Kylin team as well
  as other Chinese speaking users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lubuntu-default-settings/+bug/1928360/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1928360] Re: Switch to Fcitx 5 for Chinese

2021-05-18 Thread Gunnar Hjalmarsson
Sure, Seth, attached please find the output from

cat /var/log/audit/audit.log | grep DENIED

** Attachment added: "apparmor_denied-lines_chromium.txt"
   
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1928360/+attachment/5498578/+files/apparmor_denied-lines_chromium.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1928360

Title:
  Switch to Fcitx 5 for Chinese

Status in Lubuntu default settings:
  New
Status in Ubuntu Kylin:
  New
Status in apparmor package in Ubuntu:
  New
Status in language-selector package in Ubuntu:
  In Progress

Bug description:
  In Debian 11 Fcitx 5 will be the default IM framework for Chinese on
  non-GNOME desktops. I can think it's time to make the equivalent
  changes in Ubuntu 21.10 as well.

  I'd appreciate input on the topic from the Ubuntu Kylin team as well
  as other Chinese speaking users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lubuntu-default-settings/+bug/1928360/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1928360] Re: Switch to Fcitx 5 for Chinese

2021-05-18 Thread Gunnar Hjalmarsson
On 2021-05-16 22:23, Gunnar Hjalmarsson wrote:
> As regards apparmor it's possible that no change is needed.

Well, I simply tested with the Chromium snap. fcitx5 does not work in
Chromium, while fcitx4 does. So something needs to be done.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1928360

Title:
  Switch to Fcitx 5 for Chinese

Status in Lubuntu default settings:
  New
Status in Ubuntu Kylin:
  New
Status in apparmor package in Ubuntu:
  New
Status in language-selector package in Ubuntu:
  In Progress

Bug description:
  In Debian 11 Fcitx 5 will be the default IM framework for Chinese on
  non-GNOME desktops. I can think it's time to make the equivalent
  changes in Ubuntu 21.10 as well.

  I'd appreciate input on the topic from the Ubuntu Kylin team as well
  as other Chinese speaking users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lubuntu-default-settings/+bug/1928360/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1856738] Re: access always denied when using @{HOME} tunable in peer_addr for abstract socket

2021-05-17 Thread Gunnar Hjalmarsson
On 2021-05-17 16:06, Rüdiger Kupper wrote:
> Is this issue related to Bug #1890905?

Well, it was me who suggested that. Maybe I should rather have pointed
to the rather old bug #1423890, which includes a link to a mailing list
discussion.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1856738

Title:
  access always denied when using @{HOME} tunable in peer_addr for
  abstract socket

Status in AppArmor:
  Triaged
Status in apparmor package in Ubuntu:
  Triaged

Bug description:
  With this profile:

  #include 

  profile test {
#include 

# Parses but always denied
unix (connect, receive, send)
  type=stream
  peer=(addr="@@{HOME}/.cache/ibus/dbus-*"),

# parses and allows access
  #  unix (connect, receive, send)
  #type=stream
  #peer=(addr="@/home/*/.cache/ibus/dbus-*"),
  }

  In one terminal I start a server:
  $ ./abstract-server stream /home/jamie/.cache/ibus/dbus-foo

  Then in another terminal do:

  $ sudo apparmor_parser -r /tmp/apparmor.profile && aa-exec -p test -- 
./abstract-client stream /home/jamie/.cache/ibus/dbus-foo hi
  connect() failed

  With the following denial (and no output from the server terminal):
  apparmor="DENIED" operation="connect" profile="test" pid=3665 
comm="abstract-client" family="unix" sock_type="stream" protocol=0 
requested_mask="send receive connect" denied_mask="send connect" addr=none 
peer_addr="@/home/jamie/.cache/ibus/dbus-fo" peer="unconfined"

  Commenting out the @{HOME} rule and uncommenting the /home/* rule, it
  works:

  $ sudo apparmor_parser -r /tmp/apparmor.profile && aa-exec -p test -- 
./abstract-client stream /home/jamie/.cache/ibus/dbus-foo hi
  MESSAGE FROM SERVER: received message number 1

  (with the server displaying 'MESSAGE FROM CLIENT: hi')

  Attached is the server and client code.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1856738/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1928360] Re: Switch to Fcitx 5 for Chinese

2021-05-16 Thread Gunnar Hjalmarsson
As regards apparmor it's possible that no change is needed. fcitx5
creates the folder

~/.config/fcitx/dbus

(i.e. not ~/.config/fcitx5/dbus) with a long file name whose contents is
"unix:path=/run/user/1000/bus". Not sure how to safely confirm that,
though.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1928360

Title:
  Switch to Fcitx 5 for Chinese

Status in Lubuntu default settings:
  New
Status in Ubuntu Kylin:
  New
Status in apparmor package in Ubuntu:
  New
Status in language-selector package in Ubuntu:
  In Progress

Bug description:
  In Debian 11 Fcitx 5 will be the default IM framework for Chinese on
  non-GNOME desktops. I can think it's time to make the equivalent
  changes in Ubuntu 21.10 as well.

  I'd appreciate input on the topic from the Ubuntu Kylin team as well
  as other Chinese speaking users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lubuntu-default-settings/+bug/1928360/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1928360] Re: Switch to Fcitx 5 for Chinese

2021-05-16 Thread Gunnar Hjalmarsson
I submitted a merge proposal with suggested changes to language-selector
(pkg_depends). Please review and give feedback.

** Changed in: language-selector (Ubuntu)
   Status: New => In Progress

** Changed in: language-selector (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1928360

Title:
  Switch to Fcitx 5 for Chinese

Status in Lubuntu default settings:
  New
Status in Ubuntu Kylin:
  New
Status in apparmor package in Ubuntu:
  New
Status in language-selector package in Ubuntu:
  In Progress

Bug description:
  In Debian 11 Fcitx 5 will be the default IM framework for Chinese on
  non-GNOME desktops. I can think it's time to make the equivalent
  changes in Ubuntu 21.10 as well.

  I'd appreciate input on the topic from the Ubuntu Kylin team as well
  as other Chinese speaking users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lubuntu-default-settings/+bug/1928360/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1928360] Re: Switch to Fcitx 5 for Chinese

2021-05-16 Thread Gunnar Hjalmarsson
It struck me that Lubuntu, which ships Fcitx by default, has a special
interest in this change, so added a Lubuntu bug task.

** Also affects: lubuntu-default-settings
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1928360

Title:
  Switch to Fcitx 5 for Chinese

Status in Lubuntu default settings:
  New
Status in Ubuntu Kylin:
  New
Status in apparmor package in Ubuntu:
  New
Status in language-selector package in Ubuntu:
  New

Bug description:
  In Debian 11 Fcitx 5 will be the default IM framework for Chinese on
  non-GNOME desktops. I can think it's time to make the equivalent
  changes in Ubuntu 21.10 as well.

  I'd appreciate input on the topic from the Ubuntu Kylin team as well
  as other Chinese speaking users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lubuntu-default-settings/+bug/1928360/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1928360] Re: Switch to Fcitx 5 for Chinese

2021-05-14 Thread Gunnar Hjalmarsson
Assuming that this may require apparmor changes, I added an apparmor
(Ubuntu) bug task.

** Also affects: apparmor (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1928360

Title:
  Switch to Fcitx 5 for Chinese

Status in Ubuntu Kylin:
  New
Status in apparmor package in Ubuntu:
  New
Status in language-selector package in Ubuntu:
  New

Bug description:
  In Debian 11 Fcitx 5 will be the default IM framework for Chinese on
  non-GNOME desktops. I can think it's time to make the equivalent
  changes in Ubuntu 21.10 as well.

  I'd appreciate input on the topic from the Ubuntu Kylin team as well
  as other Chinese speaking users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntukylin/+bug/1928360/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 9364] Re: Dutch "ij" ligature (ij)

2021-05-08 Thread Gunnar Hjalmarsson
Compose followed by i followed by j gives me ij on Ubuntu 21.04. So
somehow (gtk update?) this bug seems to have been fixed. Closing.

** Package changed: xkeyboard-config (Ubuntu) => gtk+3.0 (Ubuntu)

** Changed in: gtk+3.0 (Ubuntu)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xkeyboard-config in
Ubuntu.
https://bugs.launchpad.net/bugs/9364

Title:
  Dutch "ij" ligature (ij)

Status in GTK+:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  The Dutch language has a "ij" ligature (ij), which I can't compose in X using 
the
  "us" keymap and the UTF-8 compose sequences. Most people don't use the 
ligature
  (as "ij" works fine, and has worked fine since the typewriter). As my name
  contains a "ij", and I like to be a nitpick about these things, I'd like to be
  able to type this character easily.

  There are two versions: uppercase (IJ/IJ/unicode 0132) and lowercase
  (ij/ij/unicode 0133)

  More info on the ligature: http://en.wikipedia.org/wiki/Dutch_Y

  I don't think it's really really important, but it'd be nice to be able to do
  this (and it should be easy to add this :))

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/9364/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1926686] Re: lightdm segfaults

2021-05-02 Thread Gunnar Hjalmarsson
Right, bugs are filed against source packages. Changing.

** Package changed: lightdm (Ubuntu) => glibc (Ubuntu)

** Changed in: glibc (Ubuntu)
   Status: Incomplete => New

** Summary changed:

- lightdm segfaults
+ libc-2.31.so segfaults

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1926686

Title:
  libc-2.31.so segfaults

Status in glibc package in Ubuntu:
  New

Bug description:
  [510606.379044] lightdm[4046529]: segfault at 55007d2a3f8b ip
  7f7260003f0b sp 7fffbb5a0600 error 4 in
  libc-2.31.so[7f725ff8e000+178000]

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lightdm 1.30.0-0ubuntu4~20.04.1
  Uname: Linux 5.10.32 x86_64
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Thu Apr 29 20:55:18 2021
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1926686/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1926686] Re: lightdm segfaults

2021-04-30 Thread Gunnar Hjalmarsson
OTOH... If you haven't enabled the guest session feature, the difference
between the lightdm versions in focal-release and focal-proposed can't
possibly cause the segfault.

Did you possibly install everything from focal-proposed? In that case
you may be actually 'testing' this upload:

https://launchpad.net/ubuntu/+source/glibc/2.31-0ubuntu9.3

After all the error message includes "error 4 in libc-2.31.so".

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1926686

Title:
  lightdm segfaults

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  [510606.379044] lightdm[4046529]: segfault at 55007d2a3f8b ip
  7f7260003f0b sp 7fffbb5a0600 error 4 in
  libc-2.31.so[7f725ff8e000+178000]

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lightdm 1.30.0-0ubuntu4~20.04.1
  Uname: Linux 5.10.32 x86_64
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Thu Apr 29 20:55:18 2021
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1926686/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1926686] Re: lightdm segfaults

2021-04-30 Thread Gunnar Hjalmarsson
On 2021-04-30 23:59, Robert Dinse wrote:
> I was under the impression that the purpose of proposed was to test
> and get feedback and fix such things before it entered mainstream.

It is, but such testing happens normally via dedicated bug reports. As
regards the current lightdm version in -proposed that is bug #1921655.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1926686

Title:
  lightdm segfaults

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  [510606.379044] lightdm[4046529]: segfault at 55007d2a3f8b ip
  7f7260003f0b sp 7fffbb5a0600 error 4 in
  libc-2.31.so[7f725ff8e000+178000]

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lightdm 1.30.0-0ubuntu4~20.04.1
  Uname: Linux 5.10.32 x86_64
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Thu Apr 29 20:55:18 2021
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1926686/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1926686] Re: lightdm segfaults

2021-04-30 Thread Gunnar Hjalmarsson
Thanks for your report!

Since you use lightdm 1.30.0-0ubuntu4~20.04.1 from focal-proposed, can
you please downgrade to version 1.30.0-0ubuntu3.1 and let us know if it
makes a difference.

** Changed in: lightdm (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1926686

Title:
  lightdm segfaults

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  [510606.379044] lightdm[4046529]: segfault at 55007d2a3f8b ip
  7f7260003f0b sp 7fffbb5a0600 error 4 in
  libc-2.31.so[7f725ff8e000+178000]

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lightdm 1.30.0-0ubuntu4~20.04.1
  Uname: Linux 5.10.32 x86_64
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Thu Apr 29 20:55:18 2021
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1926686/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1921655] Re: lightdm-guest-session ICEauthority error

2021-04-27 Thread Gunnar Hjalmarsson
I verified the test plan

* on 20.04 using lightdm 1.30.0-0ubuntu4~20.04.1 from focal-proposed

* on 20.10 using lightdm 1.30.0-0ubuntu4~20.10.1 from groovy-proposed

** Tags removed: verification-needed verification-needed-focal 
verification-needed-groovy
** Tags added: verification-done verification-done-focal 
verification-done-groovy

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1921655

Title:
  lightdm-guest-session ICEauthority error

Status in Ubuntu MATE:
  New
Status in lightdm package in Ubuntu:
  Fix Released
Status in lightdm source package in Focal:
  Fix Committed
Status in lightdm source package in Groovy:
  Fix Committed
Status in lightdm source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  If you enable the guest session feature on e.g. Ubuntu MATE, you are
  met by an error message when trying to enter a guest session:

  "Could not update file ICEauthority file /run/user/XXX/ICEauthority"

  Even if it's not always a fatal error (the login may succeed after a
  few minutes), the user experience is really bad, and you are inclined
  to conclude that you are completely blocked from using the feature.

  The proposed fix adds a rule to the lightdm-guest-session AppArmor
  profile and prevents the error from happening.

  [Test Plan]

  On an updated Ubuntu MATE installation:

  * Enable guest session

sudo sh -c 'printf "[Seat:*]\nallow-guest=true\n"
  >/etc/lightdm/lightdm.conf.d/50-enable-guest.conf'

  * Install lightdm from {focal,groovy}-proposed

  * Reboot

  You should now be able to enter a guest session without being stopped
  by the ICEauthority error.

  [Where problems could occur]

  This one-liner is a harmless change.

  The guest session is run in an unconfined mode since Ubuntu 16.10.
  That's why the feature is disabled by default.

  So if the additional rule would be wrong somehow (which I have no
  reason to believe), it wouldn't break the AppArmor security layer for
  the simple reason that it's already broken to begin with.

  [Original description]

  Hello I ran into trouble to start the lightdm-guest-session in linux
  mint (cinnamon).

  ## How to reproduce:
   - boot linux mint (20.02) or ubuntu mate (20.04) I haven't tested other 
distros but I think others are also affected.
   - enable guest user session
   - try to login as guest user
  ## Error logs:
  ### Error Message:
  ` Could not update file ICEauthority file /run/user/XXX/ICEauthority`
  ### aa-notify:
  ```
  Profile: /usr/lib/lightdm/lightdm-guest-session
  Operation: open
  Name: /proc/8125/uid_map
  Denied: w
  Logfile: /var/log/kern.log

  Profile: /usr/lib/lightdm/lightdm-guest-session
  Operation: open
  Name: /proc/8125/setgroups
  Denied: w
  Logfile: /var/log/kern.log

  Profile: /usr/lib/lightdm/lightdm-guest-session
  Operation: open
  Name: /proc/8125/gid_map
  Denied: w
  Logfile: /var/log/kern.log

  Profile: /usr/lib/lightdm/lightdm-guest-session
  Operation: open
  Name: /proc/8624/fd/
  Denied: r
  Logfile: /var/log/kern.log
  ```
  ### dmesg:
  ```
  [  218.831289] audit: type=1400 audit(1616864450.287:76): apparmor="DENIED" 
operation="sendmsg" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/run/systemd/journal/dev-log" pid=3916 comm="cinnamon-sessio" 
requested_mask="w" denied_mask="w" fsuid=999 ouid=0
  [ 1157.263045] audit: type=1400 audit(1616865388.720:1084): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/9899/fd/" pid=9899 comm="gpg-agent" requested_mask="r" 
denied_mask="r" fsuid=999  #ouid=0
  [ 1157.899223] audit: type=1400 audit(1616865389.356:1085): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/1/cgroup" pid=9840 comm="cinnamon-sessio" requested_mask="r" 
denied_mask="r" fsuid=999 ouid=0
  [ 1157.899445] audit: type=1400 audit(1616865389.360:1086): apparmor="DENIED" 
operation="sendmsg" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/run/systemd/journal/dev-log" pid=9840 comm="cinnamon-sessio" 
requested_mask="w" denied_mask="w" fsuid=999 ouid=0
  [ 1157.903410] audit: type=1400 audit(1616865389.364:1087): apparmor="DENIED" 
operation="link" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/run/user/999/ICEauthority-l" pid=9840 comm="cinnamon-sessio" 
requested_mask="l" denied_mask="l" fsuid=999 ouid=999 
target="/run/user/999/ICEauthority-c"
  ```
  ## Solutions:
  ### bad but common work around
  Solutions I found in different forums were to move lightdm-guest-session into 
complain mode like this:
  `aa-complain /usr/lib/lightdm/lightdm-guest-session`
  ### maybe better sollution:
  My fix would be to add this to `/etc/apparmor.d/lightdm-guest-session`:
  ```
  ...
  /usr/lib/lightdm/lightdm-guest-session {
  ...
    owner /run/user/[0-9]*/ICEauthority-? l,`
  ...
  }
  ```
  I honestly have 

[Touch-packages] [Bug 854333] Re: ibus GUI not loading, unable to use input

2021-04-24 Thread Gunnar Hjalmarsson
@aslam: This is a 10 years old bug report, and it was closed long ago.

I'm not sure that you found a bug. I'd recommend you to start with
asking for help at e.g.  in order to find out if
there is something you have misunderstood or if there really is a bug,
and if it is, to which package it belongs.

Then, if you conclude that there is a bug, please file a new bug report.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/854333

Title:
  ibus GUI not loading, unable to use input

Status in ibus package in Ubuntu:
  Fix Released
Status in ibus package in Debian:
  Fix Released

Bug description:
  I'm using oneiric since alpha3, and despite all the updates and
  bugfixes, ibus is just not working under ubuntu, nor kubuntu.

  kernel: 3.0.0-11 (also previous versions)
  ibus: 1.3.99.20110419-1ubuntu3 (also ibus-gtk, ibus-gtk3, ibus-qt4, 
ibus-pinyin packages are installed and up-to-date, with all dependencies)
  kubuntu 11.10 

  The problem is that even though ibus-daemon starts up at login, but it
  doesn't do anything, the icon doesn't appear in the notificaion area,
  and I can't seem to switch to a different method with the hotkey
  either. When I try running ibus-daemon from the command line, i get
  the answer that it's already running for this session. Also there is
  no way under language support to install chinese language pack, only
  the translations, all the other options are greyed out (input methods,
  etc) since oneiric.

  There isn't any error messages whatsoever, it just doesn't work, and
  also the same with scim and uim too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/854333/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1022858] Re: Guest session asks for a password after switching users

2021-04-22 Thread Gunnar Hjalmarsson
On 2020-01-16 13:03, Jarno Suni wrote:
> What is so difficult in not asking password when guest session
> is concerned?

Maybe low priority since guest session is disabled by default.

https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1775088/comments/2

> Does one need to switch from guest session? Maybe it should be
> disabled.

Also such a change would need work.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1022858

Title:
  Guest session asks for a password after switching users

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  When I switch back to an already open guest session from my user
  account, I find that the guest session is locked and it asks for the
  Guest password (which obviously there isn't because it's a guest
  session!).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-session-bin 3.2.1-0ubuntu8
  ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
  Uname: Linux 3.2.0-26-generic x86_64
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Tue Jul 10 09:54:55 2012
  ExecutablePath: /usr/bin/gnome-session
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)
  XsessionErrors: (compiz:1719): GConf-CRITICAL **: gconf_client_add_dir: 
assertion `gconf_valid_key (dirname, NULL)' failed
  --- 
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  DistroRelease: Ubuntu 12.04
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MarkForUpload: True
  Package: lightdm 1.2.1-0ubuntu1.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.2.0-36.57-generic 3.2.35
  Tags:  precise running-unity
  Uname: Linux 3.2.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1022858/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1921655] Re: lightdm-guest-session ICEauthority error

2021-04-12 Thread Gunnar Hjalmarsson
** Description changed:

+ [Impact]
+ 
+ If you enable the guest session feature on e.g. Ubuntu MATE, you are met
+ by an error message when trying to enter a guest session:
+ 
+ "Could not update file ICEauthority file /run/user/XXX/ICEauthority"
+ 
+ Even if it's not always a fatal error (the login may succeed after a few
+ minutes), the user experience is really bad, and you are inclined to
+ conclude that you are completely blocked from using the feature.
+ 
+ The proposed fix adds a rule to the lightdm-guest-session AppArmor
+ profile and prevents the error from happening.
+ 
+ [Test Plan]
+ 
+ On an updated Ubuntu MATE installation:
+ 
+ * Enable guest session
+ 
+   sudo sh -c 'printf "[Seat:*]\nallow-guest=true\n"
+ >/etc/lightdm/lightdm.conf.d/50-enable-guest.conf'
+ 
+ * Install lightdm from {focal,groovy}-proposed
+ 
+ * Reboot
+ 
+ You should now be able to enter a guest session without being stopped by
+ the ICEauthority error.
+ 
+ [Where problems could occur]
+ 
+ This one-liner is a harmless change.
+ 
+ The guest session is run in an unconfined mode since Ubuntu 16.10.
+ That's why the feature is disabled by default.
+ 
+ So if the additional rule would be wrong somehow (which I have no reason
+ to believe), it wouldn't break the AppArmor security layer for the
+ simple reason that it's already broken to begin with.
+ 
+ [Original description]
+ 
  Hello I ran into trouble to start the lightdm-guest-session in linux
  mint (cinnamon).
  
  ## How to reproduce:
-  - boot linux mint (20.02) or ubuntu mate (20.04) I haven't tested other 
distros but I think others are also affected.
-  - enable guest user session
-  - try to login as guest user
+  - boot linux mint (20.02) or ubuntu mate (20.04) I haven't tested other 
distros but I think others are also affected.
+  - enable guest user session
+  - try to login as guest user
  ## Error logs:
  ### Error Message:
  ` Could not update file ICEauthority file /run/user/XXX/ICEauthority`
  ### aa-notify:
- ``` 
+ ```
  Profile: /usr/lib/lightdm/lightdm-guest-session
  Operation: open
  Name: /proc/8125/uid_map
  Denied: w
  Logfile: /var/log/kern.log
-  
+ 
  Profile: /usr/lib/lightdm/lightdm-guest-session
  Operation: open
  Name: /proc/8125/setgroups
  Denied: w
  Logfile: /var/log/kern.log
-  
+ 
  Profile: /usr/lib/lightdm/lightdm-guest-session
  Operation: open
  Name: /proc/8125/gid_map
  Denied: w
  Logfile: /var/log/kern.log
-  
+ 
  Profile: /usr/lib/lightdm/lightdm-guest-session
  Operation: open
  Name: /proc/8624/fd/
  Denied: r
  Logfile: /var/log/kern.log
  ```
  ### dmesg:
  ```
  [  218.831289] audit: type=1400 audit(1616864450.287:76): apparmor="DENIED" 
operation="sendmsg" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/run/systemd/journal/dev-log" pid=3916 comm="cinnamon-sessio" 
requested_mask="w" denied_mask="w" fsuid=999 ouid=0
  [ 1157.263045] audit: type=1400 audit(1616865388.720:1084): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/9899/fd/" pid=9899 comm="gpg-agent" requested_mask="r" 
denied_mask="r" fsuid=999  #ouid=0
  [ 1157.899223] audit: type=1400 audit(1616865389.356:1085): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/1/cgroup" pid=9840 comm="cinnamon-sessio" requested_mask="r" 
denied_mask="r" fsuid=999 ouid=0
  [ 1157.899445] audit: type=1400 audit(1616865389.360:1086): apparmor="DENIED" 
operation="sendmsg" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/run/systemd/journal/dev-log" pid=9840 comm="cinnamon-sessio" 
requested_mask="w" denied_mask="w" fsuid=999 ouid=0
  [ 1157.903410] audit: type=1400 audit(1616865389.364:1087): apparmor="DENIED" 
operation="link" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/run/user/999/ICEauthority-l" pid=9840 comm="cinnamon-sessio" 
requested_mask="l" denied_mask="l" fsuid=999 ouid=999 
target="/run/user/999/ICEauthority-c"
  ```
  ## Solutions:
  ### bad but common work around
- Solutions I found in different forums were to move lightdm-guest-session into 
complain mode like this: 
+ Solutions I found in different forums were to move lightdm-guest-session into 
complain mode like this:
  `aa-complain /usr/lib/lightdm/lightdm-guest-session`
  ### maybe better sollution:
  My fix would be to add this to `/etc/apparmor.d/lightdm-guest-session`:
  ```
  ...
  /usr/lib/lightdm/lightdm-guest-session {
  ...
-   owner /run/user/[0-9]*/ICEauthority-? l,`
+   owner /run/user/[0-9]*/ICEauthority-? l,`
  ...
  }
  ```
  I honestly have no clue about apparmor and I'm unsure where to post this but 
I hope this maybe helps some other people in the future.

** Changed in: lightdm (Ubuntu Groovy)
   Status: Incomplete => In Progress

** Changed in: lightdm (Ubuntu Focal)
   Status: Triaged => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.

[Touch-packages] [Bug 1921655] Re: lightdm-guest-session ICEauthority error

2021-04-10 Thread Gunnar Hjalmarsson
Build failures resolved, and I have uploaded a fix to the hirsute queue
to start with.

** Also affects: lightdm (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: lightdm (Ubuntu Hirsute)
   Importance: Medium
   Status: Triaged

** Also affects: lightdm (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Changed in: lightdm (Ubuntu Hirsute)
   Status: Triaged => Fix Committed

** Changed in: lightdm (Ubuntu Hirsute)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Changed in: lightdm (Ubuntu Groovy)
   Importance: Undecided => Medium

** Changed in: lightdm (Ubuntu Groovy)
   Status: New => Triaged

** Changed in: lightdm (Ubuntu Groovy)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Changed in: lightdm (Ubuntu Focal)
   Importance: Undecided => Medium

** Changed in: lightdm (Ubuntu Focal)
   Status: New => Triaged

** Changed in: lightdm (Ubuntu Focal)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1921655

Title:
  lightdm-guest-session ICEauthority error

Status in Ubuntu MATE:
  New
Status in lightdm package in Ubuntu:
  Fix Committed
Status in lightdm source package in Focal:
  Triaged
Status in lightdm source package in Groovy:
  Triaged
Status in lightdm source package in Hirsute:
  Fix Committed

Bug description:
  Hello I ran into trouble to start the lightdm-guest-session in linux
  mint (cinnamon).

  ## How to reproduce:
   - boot linux mint (20.02) or ubuntu mate (20.04) I haven't tested other 
distros but I think others are also affected.
   - enable guest user session
   - try to login as guest user
  ## Error logs:
  ### Error Message:
  ` Could not update file ICEauthority file /run/user/XXX/ICEauthority`
  ### aa-notify:
  ``` 
  Profile: /usr/lib/lightdm/lightdm-guest-session
  Operation: open
  Name: /proc/8125/uid_map
  Denied: w
  Logfile: /var/log/kern.log
   
  Profile: /usr/lib/lightdm/lightdm-guest-session
  Operation: open
  Name: /proc/8125/setgroups
  Denied: w
  Logfile: /var/log/kern.log
   
  Profile: /usr/lib/lightdm/lightdm-guest-session
  Operation: open
  Name: /proc/8125/gid_map
  Denied: w
  Logfile: /var/log/kern.log
   
  Profile: /usr/lib/lightdm/lightdm-guest-session
  Operation: open
  Name: /proc/8624/fd/
  Denied: r
  Logfile: /var/log/kern.log
  ```
  ### dmesg:
  ```
  [  218.831289] audit: type=1400 audit(1616864450.287:76): apparmor="DENIED" 
operation="sendmsg" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/run/systemd/journal/dev-log" pid=3916 comm="cinnamon-sessio" 
requested_mask="w" denied_mask="w" fsuid=999 ouid=0
  [ 1157.263045] audit: type=1400 audit(1616865388.720:1084): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/9899/fd/" pid=9899 comm="gpg-agent" requested_mask="r" 
denied_mask="r" fsuid=999  #ouid=0
  [ 1157.899223] audit: type=1400 audit(1616865389.356:1085): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/1/cgroup" pid=9840 comm="cinnamon-sessio" requested_mask="r" 
denied_mask="r" fsuid=999 ouid=0
  [ 1157.899445] audit: type=1400 audit(1616865389.360:1086): apparmor="DENIED" 
operation="sendmsg" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/run/systemd/journal/dev-log" pid=9840 comm="cinnamon-sessio" 
requested_mask="w" denied_mask="w" fsuid=999 ouid=0
  [ 1157.903410] audit: type=1400 audit(1616865389.364:1087): apparmor="DENIED" 
operation="link" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/run/user/999/ICEauthority-l" pid=9840 comm="cinnamon-sessio" 
requested_mask="l" denied_mask="l" fsuid=999 ouid=999 
target="/run/user/999/ICEauthority-c"
  ```
  ## Solutions:
  ### bad but common work around
  Solutions I found in different forums were to move lightdm-guest-session into 
complain mode like this: 
  `aa-complain /usr/lib/lightdm/lightdm-guest-session`
  ### maybe better sollution:
  My fix would be to add this to `/etc/apparmor.d/lightdm-guest-session`:
  ```
  ...
  /usr/lib/lightdm/lightdm-guest-session {
  ...
owner /run/user/[0-9]*/ICEauthority-? l,`
  ...
  }
  ```
  I honestly have no clue about apparmor and I'm unsure where to post this but 
I hope this maybe helps some other people in the future.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1921655/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1921655] Re: lightdm-guest-session ICEauthority error

2021-04-08 Thread Gunnar Hjalmarsson
Upstream github issue:

https://github.com/canonical/lightdm/issues/185

** Bug watch added: github.com/canonical/lightdm/issues #185
   https://github.com/canonical/lightdm/issues/185

** Changed in: lightdm (Ubuntu)
   Status: New => Triaged

** Changed in: lightdm (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1921655

Title:
  lightdm-guest-session ICEauthority error

Status in Ubuntu MATE:
  New
Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  Hello I ran into trouble to start the lightdm-guest-session in linux
  mint (cinnamon).

  ## How to reproduce:
   - boot linux mint (20.02) or ubuntu mate (20.04) I haven't tested other 
distros but I think others are also affected.
   - enable guest user session
   - try to login as guest user
  ## Error logs:
  ### Error Message:
  ` Could not update file ICEauthority file /run/user/XXX/ICEauthority`
  ### aa-notify:
  ``` 
  Profile: /usr/lib/lightdm/lightdm-guest-session
  Operation: open
  Name: /proc/8125/uid_map
  Denied: w
  Logfile: /var/log/kern.log
   
  Profile: /usr/lib/lightdm/lightdm-guest-session
  Operation: open
  Name: /proc/8125/setgroups
  Denied: w
  Logfile: /var/log/kern.log
   
  Profile: /usr/lib/lightdm/lightdm-guest-session
  Operation: open
  Name: /proc/8125/gid_map
  Denied: w
  Logfile: /var/log/kern.log
   
  Profile: /usr/lib/lightdm/lightdm-guest-session
  Operation: open
  Name: /proc/8624/fd/
  Denied: r
  Logfile: /var/log/kern.log
  ```
  ### dmesg:
  ```
  [  218.831289] audit: type=1400 audit(1616864450.287:76): apparmor="DENIED" 
operation="sendmsg" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/run/systemd/journal/dev-log" pid=3916 comm="cinnamon-sessio" 
requested_mask="w" denied_mask="w" fsuid=999 ouid=0
  [ 1157.263045] audit: type=1400 audit(1616865388.720:1084): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/9899/fd/" pid=9899 comm="gpg-agent" requested_mask="r" 
denied_mask="r" fsuid=999  #ouid=0
  [ 1157.899223] audit: type=1400 audit(1616865389.356:1085): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/1/cgroup" pid=9840 comm="cinnamon-sessio" requested_mask="r" 
denied_mask="r" fsuid=999 ouid=0
  [ 1157.899445] audit: type=1400 audit(1616865389.360:1086): apparmor="DENIED" 
operation="sendmsg" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/run/systemd/journal/dev-log" pid=9840 comm="cinnamon-sessio" 
requested_mask="w" denied_mask="w" fsuid=999 ouid=0
  [ 1157.903410] audit: type=1400 audit(1616865389.364:1087): apparmor="DENIED" 
operation="link" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/run/user/999/ICEauthority-l" pid=9840 comm="cinnamon-sessio" 
requested_mask="l" denied_mask="l" fsuid=999 ouid=999 
target="/run/user/999/ICEauthority-c"
  ```
  ## Solutions:
  ### bad but common work around
  Solutions I found in different forums were to move lightdm-guest-session into 
complain mode like this: 
  `aa-complain /usr/lib/lightdm/lightdm-guest-session`
  ### maybe better sollution:
  My fix would be to add this to `/etc/apparmor.d/lightdm-guest-session`:
  ```
  ...
  /usr/lib/lightdm/lightdm-guest-session {
  ...
owner /run/user/[0-9]*/ICEauthority-? l,`
  ...
  }
  ```
  I honestly have no clue about apparmor and I'm unsure where to post this but 
I hope this maybe helps some other people in the future.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1921655/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1921655] Re: lightdm-guest-session ICEauthority error

2021-04-08 Thread Gunnar Hjalmarsson
Thanks for your investigation and report!

I'd like to help fixing this, but unfortunately lightdm fails to build
in hirsute at the moment, which blocks me from proceeding.

https://launchpad.net/ubuntu/+archive/test-
rebuild-20210325-hirsute/+build/21263293

Have asked for help with spotting what causes the build failure.

** Tags added: groovy hirsute

** Also affects: lightdm
   Importance: Undecided
   Status: New

** No longer affects: lightdm

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1921655

Title:
  lightdm-guest-session ICEauthority error

Status in Ubuntu MATE:
  New
Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  Hello I ran into trouble to start the lightdm-guest-session in linux
  mint (cinnamon).

  ## How to reproduce:
   - boot linux mint (20.02) or ubuntu mate (20.04) I haven't tested other 
distros but I think others are also affected.
   - enable guest user session
   - try to login as guest user
  ## Error logs:
  ### Error Message:
  ` Could not update file ICEauthority file /run/user/XXX/ICEauthority`
  ### aa-notify:
  ``` 
  Profile: /usr/lib/lightdm/lightdm-guest-session
  Operation: open
  Name: /proc/8125/uid_map
  Denied: w
  Logfile: /var/log/kern.log
   
  Profile: /usr/lib/lightdm/lightdm-guest-session
  Operation: open
  Name: /proc/8125/setgroups
  Denied: w
  Logfile: /var/log/kern.log
   
  Profile: /usr/lib/lightdm/lightdm-guest-session
  Operation: open
  Name: /proc/8125/gid_map
  Denied: w
  Logfile: /var/log/kern.log
   
  Profile: /usr/lib/lightdm/lightdm-guest-session
  Operation: open
  Name: /proc/8624/fd/
  Denied: r
  Logfile: /var/log/kern.log
  ```
  ### dmesg:
  ```
  [  218.831289] audit: type=1400 audit(1616864450.287:76): apparmor="DENIED" 
operation="sendmsg" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/run/systemd/journal/dev-log" pid=3916 comm="cinnamon-sessio" 
requested_mask="w" denied_mask="w" fsuid=999 ouid=0
  [ 1157.263045] audit: type=1400 audit(1616865388.720:1084): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/9899/fd/" pid=9899 comm="gpg-agent" requested_mask="r" 
denied_mask="r" fsuid=999  #ouid=0
  [ 1157.899223] audit: type=1400 audit(1616865389.356:1085): apparmor="DENIED" 
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/proc/1/cgroup" pid=9840 comm="cinnamon-sessio" requested_mask="r" 
denied_mask="r" fsuid=999 ouid=0
  [ 1157.899445] audit: type=1400 audit(1616865389.360:1086): apparmor="DENIED" 
operation="sendmsg" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/run/systemd/journal/dev-log" pid=9840 comm="cinnamon-sessio" 
requested_mask="w" denied_mask="w" fsuid=999 ouid=0
  [ 1157.903410] audit: type=1400 audit(1616865389.364:1087): apparmor="DENIED" 
operation="link" profile="/usr/lib/lightdm/lightdm-guest-session" 
name="/run/user/999/ICEauthority-l" pid=9840 comm="cinnamon-sessio" 
requested_mask="l" denied_mask="l" fsuid=999 ouid=999 
target="/run/user/999/ICEauthority-c"
  ```
  ## Solutions:
  ### bad but common work around
  Solutions I found in different forums were to move lightdm-guest-session into 
complain mode like this: 
  `aa-complain /usr/lib/lightdm/lightdm-guest-session`
  ### maybe better sollution:
  My fix would be to add this to `/etc/apparmor.d/lightdm-guest-session`:
  ```
  ...
  /usr/lib/lightdm/lightdm-guest-session {
  ...
owner /run/user/[0-9]*/ICEauthority-? l,`
  ...
  }
  ```
  I honestly have no clue about apparmor and I'm unsure where to post this but 
I hope this maybe helps some other people in the future.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1921655/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1922186] Re: ibus very difficult to restart

2021-04-03 Thread Gunnar Hjalmarsson
Thanks for clarifying; now I understand better. Yes, there typically is
an ibus icon when you use ibus on a non-GNOME desktop (which I don't
very often). And it indeed includes a "Quit" option.

When the daemon is started from IBus Preferences, I agree it should be
daemonized so it's not killed when you close IBus Preferences. I
reported that upstream, and if you want to test the proposed fix in
hirsute, you can install the ibus packages from this PPA:

https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus

I'm not able to reproduce the other issues you mention, though.

** Changed in: ibus (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ibus (Ubuntu)
   Status: Incomplete => Confirmed

** Bug watch added: github.com/ibus/ibus/issues #2316
   https://github.com/ibus/ibus/issues/2316

** Also affects: ibus via
   https://github.com/ibus/ibus/issues/2316
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1922186

Title:
  ibus very difficult to restart

Status in ibus:
  Unknown
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  After closing ibus by task bar -> icon -> rightclick -> `Close` it
  seems to be impossible to restart it.

  Here some ways that should work and how they fail:

  1) Menu -> ibus
  -
  - opens iBus settings 
  - starts ibus service

  Problems:
- No keyboard input is actually processed; I.e. cannot use keyboard then.
- Service is not daemonized; I.e. as soon as the iBus settings window is 
closed, the services quits.

  Suggestion:
- No keyboard input possible seems to be a bug -> should be fixed.
- Service should be daemonized at this point

  2) terminal -> `ibus start`
  ---
  Problems:
- This command does not exist. One has to know, that `ibus-daemon` is the 
one they are searching for.

  Suggestions:
- Implement this command to start the daemon from here

  3) terminal -> `ibus-daemon &` / `ibus-daemon -d`
  -
   - brings up ibus with usable keyboard (good)

  Problems: 
- As soon as terminal gets closed, ibus-daemon quits

  4) terminal -> `nohup ibus-daemon &`
  -
   - brings up ibus with usable keyboard (good)

  Problem: 
- As soon as terminal gets closed, ibus-daemon quits (very strange. 
something I wouldn't expect from a `nohup` call, by the way).

  System
  ===

  - I use ibus in conjunction with ibus-anthy

  
  lsb_release -rd
  --
  Description:  Ubuntu 20.10
  Release:  20.10

  
  apt-cache policy ibus
  --
  ibus:
Installed: 1.5.23-0ubuntu1
Candidate: 1.5.23-0ubuntu1
Version table:
   *** 1.5.23-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status

  
  apt-cache policy ibus-anthy
  --
  ibus-anthy:
Installed: 1.5.11-1build1
Candidate: 1.5.11-1build1
Version table:
   *** 1.5.11-1build1 500
  500 http://archive.ubuntu.com/ubuntu groovy/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ibus 1.5.23-0ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-45.51-generic 5.8.18
  Uname: Linux 5.8.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Thu Apr  1 15:33:00 2021
  RebootRequiredPkgs:
   linux-image-5.8.0-48-generic
   linux-base
   linux-image-5.8.0-49-generic
   linux-base
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1922186/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1922186] Re: ibus very difficult to restart

2021-04-01 Thread Gunnar Hjalmarsson
On 2021-04-01 16:23, DarkTrick wrote:
> 1) It has a "Quit" option. If you should not quit it, there should be
> no "Quit" option in the menu.

That confuses me. I see that you use an XFCE desktop, and the only icon
you should have AFAIK is "IBus Preferences" which starts a GUI for
certain settings. Quitting that should only quit "IBus Preferences"
while ibus-daemon should keep running.

If you have something else, can you please take a screenshot to show us
what it looks like.

ibus-daemon is not an application. It's a background process, and on
Debian/Ubuntu it's started silently at login while a few related
environment variables are set.

If you want to use some other IM framework, e.g. Fcitx or uim, you can
tell the system so in "Language Support", and after next reboot it will
start Fcitx or uim at login instead and assign other values to the
related variables.

> However, in crashes in 18.xx I remember that `ibus restart` would
> simply tell me "there is no running instance" and do nothing.

Right, if the ibus-daemon process is not running, "ibus restart" won't
help. But there are 'crashes' which don't kill ibus-daemon, and then
"ibus restart" often helps.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1922186

Title:
  ibus very difficult to restart

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  After closing ibus by task bar -> icon -> rightclick -> `Close` it
  seems to be impossible to restart it.

  Here some ways that should work and how they fail:

  1) Menu -> ibus
  -
  - opens iBus settings 
  - starts ibus service

  Problems:
- No keyboard input is actually processed; I.e. cannot use keyboard then.
- Service is not daemonized; I.e. as soon as the iBus settings window is 
closed, the services quits.

  Suggestion:
- No keyboard input possible seems to be a bug -> should be fixed.
- Service should be daemonized at this point

  2) terminal -> `ibus start`
  ---
  Problems:
- This command does not exist. One has to know, that `ibus-daemon` is the 
one they are searching for.

  Suggestions:
- Implement this command to start the daemon from here

  3) terminal -> `ibus-daemon &` / `ibus-daemon -d`
  -
   - brings up ibus with usable keyboard (good)

  Problems: 
- As soon as terminal gets closed, ibus-daemon quits

  4) terminal -> `nohup ibus-daemon &`
  -
   - brings up ibus with usable keyboard (good)

  Problem: 
- As soon as terminal gets closed, ibus-daemon quits (very strange. 
something I wouldn't expect from a `nohup` call, by the way).

  System
  ===

  - I use ibus in conjunction with ibus-anthy

  
  lsb_release -rd
  --
  Description:  Ubuntu 20.10
  Release:  20.10

  
  apt-cache policy ibus
  --
  ibus:
Installed: 1.5.23-0ubuntu1
Candidate: 1.5.23-0ubuntu1
Version table:
   *** 1.5.23-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status

  
  apt-cache policy ibus-anthy
  --
  ibus-anthy:
Installed: 1.5.11-1build1
Candidate: 1.5.11-1build1
Version table:
   *** 1.5.11-1build1 500
  500 http://archive.ubuntu.com/ubuntu groovy/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ibus 1.5.23-0ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-45.51-generic 5.8.18
  Uname: Linux 5.8.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Thu Apr  1 15:33:00 2021
  RebootRequiredPkgs:
   linux-image-5.8.0-48-generic
   linux-base
   linux-image-5.8.0-49-generic
   linux-base
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1922186/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1922186] Re: ibus very difficult to restart

2021-04-01 Thread Gunnar Hjalmarsson
It's not clear to me why you would want to kill the ibus-daemon process
in the first place. It's setup (via im-config) to be started and
configured at login.

As regards commands to start ibus from terminal it differs depending on
the desktop environment.

GNOME:
ibus-daemon --panel disable --xim -d

Other desktop environments:
ibus-daemon --xim -d

In situations where ibus crashes somehow, and IM inputting stops
working, you normally can do:

ibus restart

to fix it.

** Changed in: ibus (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1922186

Title:
  ibus very difficult to restart

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  After closing ibus by task bar -> icon -> rightclick -> `Close` it
  seems to be impossible to restart it.

  Here some ways that should work and how they fail:

  1) Menu -> ibus
  -
  - opens iBus settings 
  - starts ibus service

  Problems:
- No keyboard input is actually processed; I.e. cannot use keyboard then.
- Service is not daemonized; I.e. as soon as the iBus settings window is 
closed, the services quits.

  Suggestion:
- No keyboard input possible seems to be a bug -> should be fixed.
- Service should be daemonized at this point

  2) terminal -> `ibus start`
  ---
  Problems:
- This command does not exist. One has to know, that `ibus-daemon` is the 
one they are searching for.

  Suggestions:
- Implement this command to start the daemon from here

  3) terminal -> `ibus-daemon &` / `ibus-daemon -d`
  -
   - brings up ibus with usable keyboard (good)

  Problems: 
- As soon as terminal gets closed, ibus-daemon quits

  4) terminal -> `nohup ibus-daemon &`
  -
   - brings up ibus with usable keyboard (good)

  Problem: 
- As soon as terminal gets closed, ibus-daemon quits (very strange. 
something I wouldn't expect from a `nohup` call, by the way).

  System
  ===

  - I use ibus in conjunction with ibus-anthy

  
  lsb_release -rd
  --
  Description:  Ubuntu 20.10
  Release:  20.10

  
  apt-cache policy ibus
  --
  ibus:
Installed: 1.5.23-0ubuntu1
Candidate: 1.5.23-0ubuntu1
Version table:
   *** 1.5.23-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status

  
  apt-cache policy ibus-anthy
  --
  ibus-anthy:
Installed: 1.5.11-1build1
Candidate: 1.5.11-1build1
Version table:
   *** 1.5.11-1build1 500
  500 http://archive.ubuntu.com/ubuntu groovy/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ibus 1.5.23-0ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-45.51-generic 5.8.18
  Uname: Linux 5.8.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Thu Apr  1 15:33:00 2021
  RebootRequiredPkgs:
   linux-image-5.8.0-48-generic
   linux-base
   linux-image-5.8.0-49-generic
   linux-base
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1922186/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1481804] Re: LightDM's guest-account script should disable screen lock universally for guest sessions

2021-03-31 Thread Gunnar Hjalmarsson
Thanks Sushenjit. I just added a comment on the other bug.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1481804

Title:
  LightDM's guest-account script should disable screen lock universally
  for guest sessions

Status in lightdm package in Ubuntu:
  Fix Released

Bug description:
  Is it feasible to include in /usr/sbin/guest-account script some
  commands to disable screen lock for guest sessions? It should include
  several commands, depending on Ubuntu flavour. Examples:

  Ubuntu MATE (uses mate-screensaver)
  gsettings set org.mate.screensaver lock-enabled false

  Xubuntu and others (use light-locker)
  gsettings set apps.light-locker light-locker-enabled false
  gsettings set apps.light-locker late-locking false
  gsettings set apps.light-locker lock-on-lid false
  gsettings set apps.light-locker lock-on-suspend false

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1481804/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1775088] Re: Ubuntu Mate guest session locked out when switching from another account

2021-03-31 Thread Gunnar Hjalmarsson
I had a brief look at this using the latest daily build ISO for Ubuntu
MATE 21.04.

lightdm has code for disabling the MATE screensaver. I confirmed that it
works by opening a terminal window within a guest session:

$ gsettings get org.mate.screensaver lock-enabled
false

But I could still reproduce the issue, i.e. I switched to my regular
user and then when trying to switch back to the guest session it
prompted me for the non-existing password.

We should keep in mind that the guest session feature is deprecated and
disabled by default:

https://askubuntu.com/q/915415

AFAIK nobody makes any effort any longer to make sure it keeps working
when software is upgraded.

** Changed in: lightdm (Ubuntu)
   Importance: Undecided => Low

** Changed in: lightdm (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1775088

Title:
  Ubuntu Mate guest session locked out when switching from another
  account

Status in Ubuntu MATE:
  New
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  ATTN: Ubuntu Mate Developers

  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  lightdm:
    Installed: 1.26.0-0ubuntu1
    Candidate: 1.26.0-0ubuntu1
    Version table:
   *** 1.26.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status

  In Ubuntu Mate 18.04 LTS LightDM, I created a file in
  /etc/lightdm/lightdm.conf, with the line:

  allow-guest=true

  This allows me to log into a guest session. The issue is when I try to
  switch between the guest session and a normal session and back.
  Switching from guest session to the normal user session is fine.
  LightDM asks for the normal user password. However, when I try to
  switch from the normal user to back to the guest session I am asked
  for password as well. This is the problem as the guest session has no
  known password. The unlock window has a 'Switch User" button along
  with Cancel, etc. Clicking the "Switch User" button takes me to the
  standard LightDM screen. There I can select from the normal user and
  the guest. However, selecting guest here opens a new guest session,
  and does not take me back to the guest session already open.

  This looks like an old bug https://bugs.launchpad.net/bugs/1481804

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Jun  4 17:46:33 2018
  InstallationDate: Installed on 2018-05-31 (4 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1775088/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1072019] Re: date translated in an English system with Italian localization

2021-03-29 Thread Gunnar Hjalmarsson
The workaround mentioned in comment #3 may be worth repeating, i.e. open
your ~/.profile file for editing and add this line:

export LC_TIME=en_DK.UTF-8

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/1072019

Title:
  date translated in an English system with Italian localization

Status in GLib:
  Won't Fix
Status in GNOME Shell:
  In Progress
Status in Indicator Date and Time:
  In Progress
Status in indicator-datetime package in Ubuntu:
  Triaged

Bug description:
  Release of Ubuntu:12.10
  Package Version: gnome-control-center 3.4.2 and 3.5.x
  Expected Results: system language setting needs to be respected
  Actual Results: date is translated following the reginal format settings

  Hallo
  I want to have my system fully in English, but actually the date  is 
translated in Italian.
  I think that this depend on the fact that I choose Italian in regional format 
(but just to have numbering and currency that I use), I don't want to have the 
date translated into another language.
  See attached screenshot.

  Thanks
  Fabio

  ProblemType: BugDistroRelease: Ubuntu 12.10
  Package: language-selector-gnome 0.90
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Sat Oct 27 10:58:20 2012
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-language-selector
  InstallationDate: Installed on 2012-10-12 (14 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20121011)
  InterpreterPath: /usr/bin/python3.2mu
  MarkForUpload: True
  PackageArchitecture: allSourcePackage: language-selector
  UpgradeStatus: Upgraded to quantal on 2012-10-13 (14 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1072019/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"

2021-03-24 Thread Gunnar Hjalmarsson
On 2021-03-23 17:32, Gunnar Hjalmarsson wrote:
> Then I tried with the groovy ISO, and the issue was present with that
> as well.

That was false alarm at least. Sorry.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1920665

Title:
  Ubiquity KDE crash on try/install and from live session with
  "malloc(): unaligned tcache chunk detected"

Status in mesa package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in mesa source package in Hirsute:
  Confirmed
Status in ubiquity source package in Hirsute:
  Confirmed

Bug description:
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.11
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.460
  CurrentDesktop: KDE
  Date: Sun Mar 21 11:53:44 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

  Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try
  install screen) and from the live session is crashing on launch or
  shortly after.

  Try/Install crash:

   Screen fails to start, or starts then crashes on any user action. The
  user is presented with:

  "Installation failed - The installer encountered an unrecoverable error.
  A desktop session will now be run so that you may investigate the problem or 
try installing again"

  Live session crash:

  The installer does not start from the desktop icon. Starting ubiquity
  from the terminal results in an "Aborted (core dumped)" message and
  nothing else.

  An example /var/log/installer/debug log from a session where both
  crashes were triggered is below.

   /var/log/installer/debug 

  Ubiquity 21.04.11
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  QSocketNotifier: Invalid socket 17 and type 'Read', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Write', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Exception', disabling...
  Your console font configuration will be updated the next time your system
  boots. If you want to update it now, run 'setupcon' from a virtual console.
  update-initramfs is disabled since running on read-only media
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  munmap_chunk(): invalid pointer
  Ubiquity 21.04.11
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  malloc(): unaligned tcache chunk detected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"

2021-03-23 Thread Gunnar Hjalmarsson
I hit this issue a couple of days ago when trying the latest Kubuntu ISO
in a VM.

Then I tried with the groovy ISO, and the issue was present with that as
well.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1920665

Title:
  Ubiquity KDE crash on try/install and from live session with
  "malloc(): unaligned tcache chunk detected"

Status in mesa package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in mesa source package in Hirsute:
  Confirmed
Status in ubiquity source package in Hirsute:
  Confirmed

Bug description:
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.11
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.460
  CurrentDesktop: KDE
  Date: Sun Mar 21 11:53:44 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

  Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try
  install screen) and from the live session is crashing on launch or
  shortly after.

  Try/Install crash:

   Screen fails to start, or starts then crashes on any user action. The
  user is presented with:

  "Installation failed - The installer encountered an unrecoverable error.
  A desktop session will now be run so that you may investigate the problem or 
try installing again"

  Live session crash:

  The installer does not start from the desktop icon. Starting ubiquity
  from the terminal results in an "Aborted (core dumped)" message and
  nothing else.

  An example /var/log/installer/debug log from a session where both
  crashes were triggered is below.

   /var/log/installer/debug 

  Ubiquity 21.04.11
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  QSocketNotifier: Invalid socket 17 and type 'Read', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Write', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Exception', disabling...
  Your console font configuration will be updated the next time your system
  boots. If you want to update it now, run 'setupcon' from a virtual console.
  update-initramfs is disabled since running on read-only media
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  munmap_chunk(): invalid pointer
  Ubiquity 21.04.11
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  malloc(): unaligned tcache chunk detected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1920665/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1916245] Re: No matter how i write the lightdm.conf file, it makes the whole thing crash and i can't login. I'm trying to change the greeter to webkit2

2021-02-19 Thread Gunnar Hjalmarsson
Please show us an example conf file which causes the problem.

** Changed in: lightdm (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1916245

Title:
  No matter how i write the lightdm.conf file, it makes the whole thing
  crash and i can't login. I'm trying to change the greeter to webkit2

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  I installed lightdm and then rebooted. It worked fine but i wanted to
  change how it looks. I tried installing the web-greeter using whither
  as instructed here: https://askubuntu.com/questions/960334/how-can-i
  -install-lightdm-webkit2-greeter

  and the PC wouldn't open. It would be loading forever. So then i
  deleted the conf file and it reverted to the default. I've tried
  placing the same conf file at /etc/lightdm/lightdm.conf with the same
  results

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: lightdm 1.30.0-0ubuntu3.1
  ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Feb 19 14:49:25 2021
  InstallationDate: Installed on 2020-10-14 (127 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to groovy on 2020-11-26 (84 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1916245/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 195982] Re: Shift key (and caps lock) stop working when using VMWare

2021-02-06 Thread Gunnar Hjalmarsson
@Gary: Please submit a new bug report. You won't call anyone's attention
by a comment on this old closed one.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xkeyboard-config in
Ubuntu.
https://bugs.launchpad.net/bugs/195982

Title:
  Shift key (and caps lock) stop working when using VMWare

Status in Linux:
  Invalid
Status in linux package in Ubuntu:
  Won't Fix
Status in xkeyboard-config package in Ubuntu:
  Invalid
Status in Gentoo Linux:
  New

Bug description:
  [Problem]
  VMWare's keyboard mapping is imperfect, sometimes resulting in certain keys 
stopping functionality when running under VMWare, requiring the user to setup 
their configuration settings manually in VMWare.  For a detailed explanation 
see the following article:

  http://www.vmware.com/support/ws55/doc/ws_devices_keymap_linux_longer.html

  [Original Report]
  After a day or so of running the shift key mysteriously stops working as does 
the cap lock. In other words I cannot enter shifted characters of any kind. The 
keyboard is connected to a KVM and all other systems respond to it properly. In 
additional any VMWare sessions I have open respond correctly. So I have the 
condition where all non-vmware applications in Ubuntu Hardy (all updates 
applied as of 2008-02-26 at 12:43 UTC) fail to recognize the shift key BUT 
applications within an active (a paused/restarted session also works) VMWare 
sessions running DO recognize the key.

  When this condition occurs ALL applications (except those within a
  VMWare session) are also unstable and will usually crash within a few
  keystrokes.If I continue to operate in this mode. I cannot pinpoint
  what, if any, application triggers this. It has always happened while
  working within terminal/browser/vmware sessions and NOT when opening a
  new application. It could be related to the KVM switch, but none of my
  other systems (2 Mandriva, 1 Windows) are affected by this.

  This bug has been present on my system for a number of days across
  daily updates and reboots (if the update requested it) and I think
  since I installed Hardy Alpha 1.

  A work around: log off and back on. A reboot/restart does not appear
  to be needed.

  Error logs show some unusual activity.

  --- MARK 
  ...
  ... kernel ... rtc lost 7 interrupts ...
  --- MARK ---
  

  Plus some segfaults indicating which application crashed as I tried to
  type into it (mouse works fine).

  System: HP dv9743cl (which otherwise works lovely)
  Ubuntu: Hardy 8.04 (from lsb-release)

  
  TEST CASE:
  1. Click inside the VM and
 
  2. Hold any of the Ctrl, Alt and/or shift keys while releasing the 
keyboard/mouse to the host OS (which you obviously do when you press Crtl-Alt 
to revert back to windowed mode, as the cursor is then released from the VM). 

  WORKAROUND:
  After this happens to recover your keyboard execute 'setxkbmap' in a terminal

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/195982/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 434601] Re: Package descriptions etc display only in the language of whoever installed the OS

2021-01-31 Thread Gunnar Hjalmarsson
Reversed bogus status changes.

** Changed in: ubuntu-translations
   Status: Fix Released => Confirmed

** Changed in: apt (Ubuntu)
   Status: Fix Released => Confirmed

** Changed in: software-center (Ubuntu)
   Status: Fix Released => Confirmed

** Changed in: ubuntu-translations
 Assignee: Pavel muhlheim (procomp26) => (unassigned)

** Changed in: software-center (Ubuntu)
 Assignee: Pavel muhlheim (procomp26) => (unassigned)

** Changed in: apt (Ubuntu)
 Assignee: mokbel (mrmokbel) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/434601

Title:
  Package descriptions etc display only in the  language of whoever
  installed the OS

Status in Ubuntu Translations:
  Confirmed
Status in apt package in Ubuntu:
  Confirmed
Status in software-center package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: software-store

  if the cache was geneated with a english locale and then is used by a
  user with german locale, the cache will be english only. this needs to
  be fixed by storting a language attribute in the cache and forcing a
  re-generation (or a generation of a new one) if they don't match.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/434601/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1910279] Re: mate-session starts instead when i3 was selected on login screen

2021-01-05 Thread Gunnar Hjalmarsson
Ok, then we seem to have defined the problem: There is a need to make
arctica-greeter play well with accountsservice.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1910279

Title:
  mate-session starts instead when i3 was selected on login screen

Status in Ubuntu MATE:
  New
Status in arctica-greeter package in Ubuntu:
  Confirmed
Status in mate-session-manager package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Have Ubuntu MATE 20.10 installed
  2. Install i3 with `sudo apt-get install i3*`
  3. Reboot machine 
  4. Select i3 (or i3 with debug) on login screen

  Expected results:

  * i3 starts

  Actual results:

  * MATE starts instead of i3

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: mate-session-manager 1.24.1-1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Tue Jan  5 22:27:29 2021
  InstallationDate: Installed on 2020-10-23 (74 days ago)
  InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Release amd64 
(20201022)
  SourcePackage: mate-session-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1910279/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1910279] Re: mate-session starts instead when i3 was selected on login screen

2021-01-05 Thread Gunnar Hjalmarsson
And I think that "XSession" is what counts.

Does it help if you switch to lightdm-gtk-greeter (but keep mate-
session-manager)?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1910279

Title:
  mate-session starts instead when i3 was selected on login screen

Status in Ubuntu MATE:
  New
Status in arctica-greeter package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  New
Status in mate-session-manager package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Have Ubuntu MATE 20.10 installed
  2. Install i3 with `sudo apt-get install i3*`
  3. Reboot machine 
  4. Select i3 (or i3 with debug) on login screen

  Expected results:

  * i3 starts

  Actual results:

  * MATE starts instead of i3

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: mate-session-manager 1.24.1-1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Tue Jan  5 22:27:29 2021
  InstallationDate: Installed on 2020-10-23 (74 days ago)
  InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Release amd64 
(20201022)
  SourcePackage: mate-session-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1910279/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1910279] Re: mate-session starts instead when i3 was selected on login screen

2021-01-05 Thread Gunnar Hjalmarsson
What does this command output:

sudo grep Session /var/lib/AccountsService/users/$USER

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1910279

Title:
  mate-session starts instead when i3 was selected on login screen

Status in arctica-greeter package in Ubuntu:
  New
Status in lightdm package in Ubuntu:
  New
Status in mate-session-manager package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  1. Have Ubuntu MATE 20.10 installed
  2. Install i3 with `sudo apt-get install i3*`
  3. Reboot machine 
  4. Select i3 (or i3 with debug) on login screen

  Expected results:

  * i3 starts

  Actual results:

  * MATE starts instead of i3

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: mate-session-manager 1.24.1-1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Tue Jan  5 22:27:29 2021
  InstallationDate: Installed on 2020-10-23 (74 days ago)
  InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Release amd64 
(20201022)
  SourcePackage: mate-session-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/arctica-greeter/+bug/1910279/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1910135] Re: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 5530 (aptd)

2021-01-04 Thread Gunnar Hjalmarsson
What makes you think that the issue is related to the ibus package?

Usually that happens right after you have logged in to the session, when
some processes are checking for updates behind the scenes. Just wait a
few minutes, and try again.

** Changed in: ibus (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1910135

Title:
  Could not get lock /var/lib/dpkg/lock-frontend. It is held by process
  5530 (aptd)

Status in ibus package in Ubuntu:
  Invalid

Bug description:
  04/0833 Error report when att apply update:

  “E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 
5530 (aptd)
  E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is 
another process using it?
  E: _cache->open() failed, please report.

  W: Be aware that removing the lock file is not a solution and may
  break your system.”04/0833 Error report when att apply update:

  “E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 
5530 (aptd)
  E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is 
another process using it?
  E: _cache->open() failed, please report.

  W: Be aware that removing the lock file is not a solution and may
  break your system.”04/0833 Error report when att apply update:

  “E: Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 
5530 (aptd)
  E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is 
another process using it?
  E: _cache->open() failed, please report.

  W: Be aware that removing the lock file is not a solution and may
  break your system.”

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1910135/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1909347] Re: Keyboard layout used in the second place breaks keymap

2020-12-27 Thread Gunnar Hjalmarsson
I have Ubuntu MATE on a VM and could reproduce your first issue there,
i.e. it's present only when Neo 2 is not first in the list of keyboard
layouts.

Consequently this is probably an xkeyboard-config issue and not specific
to gnome-control-center. And the issue is reasonably upstream in nature.

I found this open upstream issue regarding Neo 2:

https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-
config/-/issues/14

Can't tell if it's related to your observations. If not I would
recommend you to file a new issue upstream. If you do, please post a
link to it here for tracking purposes.

** Bug watch added: 
gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/issues #14
   https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/issues/14

** Package changed: gnome-control-center (Ubuntu) => xkeyboard-config
(Ubuntu)

** Changed in: xkeyboard-config (Ubuntu)
   Importance: Undecided => Low

** Changed in: xkeyboard-config (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xkeyboard-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1909347

Title:
  Keyboard layout used in the second place breaks keymap

Status in xkeyboard-config package in Ubuntu:
  Confirmed

Bug description:
  It's hard to really summarize the issue here. If you use the Neo2
  layout somewhere, the keymap becomes garbled in a very specific way
  (see below). I am not really sure if it affects other keyboard layouts
  or what happens internally. I have selected gnome-control-center as
  the affected package, because this is, where it all starts. There are
  two issues, which are somehow connected.

  
  Reproduction steps (first issue):

  1. Open "Region & Language Settings" in gnome-control-center
  2. In "Input Sources" use "German (no dead keys)" in the FIRST place and 
"German (Neo 2)" in the second place (order matters!)
  3. Open your favorite text editor
  4. Use Super+Alt+Backspace to change to the Neo2 layout
  5. Press and hold the Mod4 key (right of Left Shift) and 3.
  6. You get a 3, expected would be №.

  Reproduction steps (second issue):

  1. Go back to the "Region & Language Settings" and now use "German (Neo 2)" 
in the FIRST place and "German (no dead keys)" in the SECOND place
  2. Open Chromium and open any web page (it does not work with any other 
application)
  3. Use Super+Alt+Backspace to change to "German (no dead keys)" layout
  4. Press Ctrl+F
  5. Instead of the In-Page-Search opening, you go to the search bar, which 
means that the input is interpreted as Ctrl+E instead of Ctrl+F. If you press 
Ctrl+I (which is Ctrl+F on Neo2), the search bar opens, which means that even 
though Neo2 is selected, the old keymap is still somehow active.

  Info:

  1) Release: Ubuntu 20.04.1 LTS
  2) gnome-control-center: Installed: 1:3.36.4-0ubuntu2
  3/4) See reproduction steps above

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1909347/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1829297] Re: ibus-ui-gtk3 crashed with SIGSEGV in tcache_get()

2020-12-14 Thread Gunnar Hjalmarsson
*** This bug is a duplicate of bug 1893551 ***
https://bugs.launchpad.net/bugs/1893551

** This bug has been marked a duplicate of bug 1893551
   Let im-config back off if IBus on GNOME desktops

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1829297

Title:
  ibus-ui-gtk3 crashed with SIGSEGV in tcache_get()

Status in ibus package in Ubuntu:
  New

Bug description:
  browser reading and listening to a yutube-stream, suddeny this bug
  message pops up

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-50.54-lowlatency 4.15.18
  Uname: Linux 4.15.0-50-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  Date: Wed May 15 23:10:18 2019
  ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
  InstallationDate: Installed on 2018-08-08 (280 days ago)
  InstallationMedia: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
  SegvAnalysis:
   Segfault happened at: 0x7f550a55f207 <__GI___libc_malloc+407>:   mov
(%rdx),%rdi
   PC (0x7f550a55f207) ok
   source "(%rdx)" (0x6e6f662f6374652f) not located in a known VMA region 
(needed readable region)!
   destination "%rdi" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   tcache_get (tc_idx=2) at malloc.c:2943
   __GI___libc_malloc (bytes=48) at malloc.c:3050
   ?? () from /usr/lib/x86_64-linux-gnu/libfontconfig.so.1
   FcStrSetAdd () from /usr/lib/x86_64-linux-gnu/libfontconfig.so.1
   FcConfigParseAndLoad () from /usr/lib/x86_64-linux-gnu/libfontconfig.so.1
  Title: ibus-ui-gtk3 crashed with SIGSEGV in tcache_get()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio avahi avahi-autoipd backup bin bluetooth cdrom colord 
crontab daemon dialout dip disk fax floppy games geoclue gnats input irc kmem 
lightdm list lp lpadmin mail man messagebus mlocate netdev news nopasswdlogin 
operator plugdev proxy pulse pulse-access root rtkit sambashare saned sasl 
scanner shadow src ssh ssl-cert staff sudo sys tape video

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1829297/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1843958] Re: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_get_engines_by_names()

2020-12-14 Thread Gunnar Hjalmarsson
*** This bug is a duplicate of bug 1893551 ***
https://bugs.launchpad.net/bugs/1893551

** This bug has been marked a duplicate of bug 1893551
   Let im-config back off if IBus on GNOME desktops

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1843958

Title:
  ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_get_engines_by_names()

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  I was adding a new user in system settings in the liveusb version of
  Ubuntu 19.10 alpha when the error message appeared bellow the other
  windows. I didn't notice anything crashing, AFAICR

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: ibus 1.5.19-4ubuntu2
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CasperVersion: 1.415
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 13 22:16:39 2019
  ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
  LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190909)
  ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fac162ecf3e :movl   
$0xfbad8004,0x20(%rsp)
   PC (0x7fac162ecf3e) ok
   source "$0xfbad8004" ok
   destination "0x20(%rsp)" (0x7ffdf646afd0) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libibus-1.0.so.5
   ibus_bus_get_engines_by_names () from /lib/x86_64-linux-gnu/libibus-1.0.so.5
   ?? ()
   ?? ()
   g_cclosure_marshal_VOID__STRINGv () from 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_get_engines_by_names()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1843958/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1870921] Re: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()

2020-12-14 Thread Gunnar Hjalmarsson
*** This bug is a duplicate of bug 1893551 ***
https://bugs.launchpad.net/bugs/1893551

** This bug is no longer a duplicate of bug 1870747
   ibus-ui-gtk3 crashed with SIGABRT in raise()
** This bug has been marked a duplicate of bug 1893551
   Let im-config back off if IBus on GNOME desktops

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1870921

Title:
  ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()

Status in ibus package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  5 14:44:58 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  InstallationDate: Installed on 2020-04-05 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1870921/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1872071] Re: ibus-x11 crashed with SIGSEGV in __GI___poll()

2020-12-14 Thread Gunnar Hjalmarsson
*** This bug is a duplicate of bug 1893551 ***
https://bugs.launchpad.net/bugs/1893551

** This bug has been marked a duplicate of bug 1893551
   Let im-config back off if IBus on GNOME desktops

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1872071

Title:
  ibus-x11 crashed with SIGSEGV in __GI___poll()

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  This happened at start up after software updater requested a restart.I 
attached 
  unattended-upgrades.log
  unattended-upgrades-dpkg.log
  dpkg.log
  to show what packages were installed before the restart.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 07:16:32 2020
  ExecutablePath: /usr/libexec/ibus-x11
  InstallationDate: Installed on 2020-03-14 (26 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  ProcCmdline: /usr/libexec/ibus-x11 --kill-daemon
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7f6b2b2919f6 <__run_exit_handlers+198>:  mov
0x10(%rax),%rdx
   PC (0x7f6b2b2919f6) ok
   source "0x10(%rax)" (0x1042f359537650) not located in a known VMA region 
(needed readable region)!
   destination "%rdx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   __GI___poll (fds=0x7f6af80067e0, nfds=3, timeout=1766) at 
../sysdeps/unix/sysv/linux/poll.c:29
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ibus_main () from /lib/x86_64-linux-gnu/libibus-1.0.so.5
   ?? ()
  Title: ibus-x11 crashed with SIGSEGV in __GI___poll()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1872071/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1872217] Re: ibus-x11 crashed with SIGSEGV in __GI___poll()

2020-12-14 Thread Gunnar Hjalmarsson
*** This bug is a duplicate of bug 1893551 ***
https://bugs.launchpad.net/bugs/1893551

** This bug is no longer a duplicate of bug 1872071
   ibus-x11 crashed with SIGSEGV in __GI___poll()
** This bug has been marked a duplicate of bug 1893551
   Let im-config back off if IBus on GNOME desktops

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1872217

Title:
  ibus-x11 crashed with SIGSEGV in __GI___poll()

Status in ibus package in Ubuntu:
  New

Bug description:
  Problema constantes de Ibus

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sat Apr 11 14:10:03 2020
  ExecutablePath: /usr/libexec/ibus-x11
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcCmdline: /usr/libexec/ibus-x11 --kill-daemon
  ProcEnviron:
   LANG=es_VE.UTF-8
   LANGUAGE=es_VE:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7fc97abc69f6 <__run_exit_handlers+198>:  mov
0x10(%rax),%rdx
   PC (0x7fc97abc69f6) ok
   source "0x10(%rax)" (0xb143e205ad8c0) not located in a known VMA region 
(needed readable region)!
   destination "%rdx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   __GI___poll (fds=0x55f25e1ac530, nfds=3, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ibus_main () from /lib/x86_64-linux-gnu/libibus-1.0.so.5
   ?? ()
  Title: ibus-x11 crashed with SIGSEGV in __GI___poll()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1872217/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1870747] Re: ibus-ui-gtk3 crashed with SIGABRT in raise()

2020-12-14 Thread Gunnar Hjalmarsson
*** This bug is a duplicate of bug 1893551 ***
https://bugs.launchpad.net/bugs/1893551

** This bug has been marked a duplicate of bug 1893551
   Let im-config back off if IBus on GNOME desktops

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1870747

Title:
  ibus-ui-gtk3 crashed with SIGABRT in raise()

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 13:27:38 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  InstallationDate: Installed on 2020-04-03 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1870747/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1843195] Re: ibus-ui-gtk3 crashed with SIGSEGV in __vfprintf_internal()

2020-12-14 Thread Gunnar Hjalmarsson
*** This bug is a duplicate of bug 1893551 ***
https://bugs.launchpad.net/bugs/1893551

** This bug has been marked a duplicate of bug 1893551
   Let im-config back off if IBus on GNOME desktops

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1843195

Title:
  ibus-ui-gtk3 crashed with SIGSEGV in __vfprintf_internal()

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  switch user not working.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: ibus 1.5.19-4ubuntu2
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep  2 18:03:59 2019
  ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
  InstallationDate: Installed on 2019-08-27 (12 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190819)
  ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   __vfprintf_internal (s=0x7f84e5081f5f, format=0x25 , ap=0x7ffe1ea7fc20, mode_flags=2) at 
vfprintf-internal.c:1289
   __vfprintf_internal (s=0x4, format=0x7ffe1ea7fc20 "\030", ap=0x2, 
mode_flags=) at ../libio/libioP.h:947
  Title: ibus-ui-gtk3 crashed with SIGSEGV in __vfprintf_internal()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1843195/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1869484] Re: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()

2020-12-14 Thread Gunnar Hjalmarsson
*** This bug is a duplicate of bug 1893551 ***
https://bugs.launchpad.net/bugs/1893551

** This bug has been marked a duplicate of bug 1893551
   Let im-config back off if IBus on GNOME desktops

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1869484

Title:
  ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  i don't know what's happened

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 27 23:00:56 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  InstallationDate: Installed on 2018-08-07 (598 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to focal on 2020-03-08 (19 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1869484/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1880371] Re: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()

2020-12-14 Thread Gunnar Hjalmarsson
*** This bug is a duplicate of bug 1893551 ***
https://bugs.launchpad.net/bugs/1893551

** This bug is no longer a duplicate of bug 1869484
   ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()
** This bug has been marked a duplicate of bug 1893551
   Let im-config back off if IBus on GNOME desktops

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1880371

Title:
  ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()

Status in ibus package in Ubuntu:
  New

Bug description:
  Happened after i logged in into the Ubuntu account.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-31.35-lowlatency 5.4.34
  Uname: Linux 5.4.0-31-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 24 02:05:33 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  InstallationDate: Installed on 2020-02-08 (105 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to focal on 2020-04-20 (33 days ago)
  UserGroups: adm boinc cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  mtime.conffile..etc.apport.crashdb.conf: 2020-05-15T09:41:35.683742
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1880371/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1870843] Re: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_call_sync()

2020-12-14 Thread Gunnar Hjalmarsson
This crash type seems to not be present in 20.10, so let's consider it
fixed for now. Closing.

** Changed in: ibus (Ubuntu)
   Status: Incomplete => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1870843

Title:
  ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_call_sync()

Status in ibus package in Ubuntu:
  Fix Released

Bug description:
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 13:03:51 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  ProcEnviron:
   LANGUAGE=es_AR:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fee4f4e8f5b : orq
$0x0,(%rsp)
   PC (0x7fee4f4e8f5b) ok
   source "$0x0" ok
   destination "(%rsp)" (0x7ffe02368d40) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libibus-1.0.so.5
   ibus_bus_get_engines_by_names () from /lib/x86_64-linux-gnu/libibus-1.0.so.5
   ?? ()
   ?? ()
   g_cclosure_marshal_VOID__STRINGv () from 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_get_engines_by_names()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1870843/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1883355] Re: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()

2020-12-14 Thread Gunnar Hjalmarsson
*** This bug is a duplicate of bug 1893551 ***
https://bugs.launchpad.net/bugs/1893551

** This bug is no longer a duplicate of bug 1869484
   ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()
** This bug has been marked a duplicate of bug 1893551
   Let im-config back off if IBus on GNOME desktops

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1883355

Title:
  ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()

Status in ibus package in Ubuntu:
  New

Bug description:
  Happened on startup of pc.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
  Uname: Linux 5.4.0-37-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 13 01:11:52 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  InstallationDate: Installed on 2020-02-08 (125 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to focal on 2020-04-20 (53 days ago)
  UserGroups: adm boinc cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  mtime.conffile..etc.apport.crashdb.conf: 2020-05-15T09:41:35.683742
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1883355/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1871625] Re: ibus-ui-gtk3 crashed with SIGSEGV in __vfprintf_internal()

2020-12-14 Thread Gunnar Hjalmarsson
*** This bug is a duplicate of bug 1893551 ***
https://bugs.launchpad.net/bugs/1893551

** This bug has been marked a duplicate of bug 1893551
   Let im-config back off if IBus on GNOME desktops

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1871625

Title:
  ibus-ui-gtk3 crashed with SIGSEGV in __vfprintf_internal()

Status in ibus package in Ubuntu:
  New

Bug description:
  There is a similar bug but it is on 19.10. I got this on 20.04 after I
  closed and reopened my session.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  8 14:46:26 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  InstallationDate: Installed on 2018-04-07 (732 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403)
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fdcf7d9b9e1 <__vfprintf_internal+1>:nop
%edx
   PC (0x7fdcf7d9b9e1) ok
   source "%edx" ok
   Stack memory exhausted (SP below stack segment)
   SP (0x7fff10ee8da0) not located in a known VMA region (needed readable 
region)!
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop: __vfprintf_internal (s=0x7fff10ee9340, format=0x7fdcf818e0e9 
"%s\n", ap=0x7fff10eeba00, mode_flags=2) at vfprintf-internal.c:1289
  Title: ibus-ui-gtk3 crashed with SIGSEGV in __vfprintf_internal()
  UpgradeStatus: Upgraded to focal on 2020-04-04 (3 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1871625/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1879958] Re: /usr/libexec/ibus-ui-gtk3:11:__vfprintf_internal:buffered_vfprintf:IO_validate_vtable:__vfprintf_internal:___fprintf_chk

2020-12-14 Thread Gunnar Hjalmarsson
*** This bug is a duplicate of bug 1893551 ***
https://bugs.launchpad.net/bugs/1893551

** This bug has been marked a duplicate of bug 1893551
   Let im-config back off if IBus on GNOME desktops

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1879958

Title:
  /usr/libexec/ibus-ui-
  
gtk3:11:__vfprintf_internal:buffered_vfprintf:IO_validate_vtable:__vfprintf_internal:___fprintf_chk

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
ibus.  This problem was most recently seen with package version 
1.5.22-2ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/3a012dedb557f699d32a1f5c166d0c6e0ecd2c70 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1879958/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1878215] Re: ibus crash

2020-12-14 Thread Gunnar Hjalmarsson
*** This bug is a duplicate of bug 1893551 ***
https://bugs.launchpad.net/bugs/1893551

** This bug is no longer a duplicate of bug 1879958
   
/usr/libexec/ibus-ui-gtk3:11:__vfprintf_internal:buffered_vfprintf:IO_validate_vtable:__vfprintf_internal:___fprintf_chk
** This bug has been marked a duplicate of bug 1893551
   Let im-config back off if IBus on GNOME desktops

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1878215

Title:
  ibus crash

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  ibus crash

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Tue May 12 16:59:54 2020
  InstallationDate: Installed on 2017-12-13 (880 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: ibus
  UpgradeStatus: Upgraded to focal on 2020-04-21 (21 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1878215/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1903574] Re: isenkram-lookup crashed with SIGSEGV in g_type_check_instance_cast()

2020-12-05 Thread Gunnar Hjalmarsson
Ok, Matthias, added a gobject-introspection bug task.

** Also affects: gobject-introspection (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gobject-introspection (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gobject-introspection in
Ubuntu.
https://bugs.launchpad.net/bugs/1903574

Title:
  isenkram-lookup crashed with SIGSEGV in g_type_check_instance_cast()

Status in GObject Introspection:
  Unknown
Status in appstream package in Ubuntu:
  Fix Released
Status in gobject-introspection package in Ubuntu:
  Confirmed
Status in isenkram package in Ubuntu:
  Invalid
Status in appstream package in Debian:
  Unknown

Bug description:
  [Impact]

  An attempt to run the isenkram-lookup command from the isenkram-cli
  package results in a segfault/crash. The proposed appstream upload in
   fixes the
  issue.

  [Test case]

  1. Install the isenkram package

  2. Run the isenkram-lookup command

  -> Find that it segfaults

  3. Install the packages built by the appstream source
     package from groovy-proposed

  -> Find that the command succeeds and possibly lists a few
     suggested packages.

  [Where problems could occur]

  TBH this fix is far above my head. Only code comments are changed,
  i.e. some occurrences of "full" are replaced with "container", but it
  still has proved to be it.

  The reasoning in the commit message sounds plausible:

  https://github.com/ximion/appstream/commit/b52858bf

  [Original description]

  I just run the isenkram-lookup command.

  The crash may be related to this autopkgtest failure (which current
  blocks migration of gtk+3.0):

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-
  hirsute/hirsute/amd64/i/isenkram/20201108_141822_ee8c4@/log.gz

  This is the script which fails:

  https://salsa.debian.org/debian/isenkram/-/blob/master/debian/tests
  /test-command-line

  and it includes the isenkram-lookup command.

  ProblemType: Crash
  DistroRelease: Ubuntu 21.04
  Package: isenkram-cli 0.44
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu51
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  9 18:07:47 2020
  ExecutablePath: /usr/bin/isenkram-lookup
  ExecutableTimestamp: 1595665183
  InstallationDate: Installed on 2019-11-10 (365 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  InterpreterPath: /usr/bin/python3.8
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/isenkram-lookup
  ProcCwd: /home/gunnar
  Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: N/A
  SegvAnalysis:
   Segfault happened at: 0x7f27ae221cca :
mov(%rdi),%rax
   PC (0x7f27ae221cca) ok
   source "(%rdi)" (0x64657375) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: isenkram
  StacktraceTop:
   g_type_check_instance_cast () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   as_component_get_provided_for_kind () at 
/lib/x86_64-linux-gnu/libappstream.so.4
   () at /lib/x86_64-linux-gnu/libffi.so.8
   () at /lib/x86_64-linux-gnu/libffi.so.8
   () at /usr/lib/python3/dist-packages/gi/_gi.cpython-38-x86_64-linux-gnu.so
  Title: isenkram-lookup crashed with SIGSEGV in g_type_check_instance_cast()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lp lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gobject-introspection/+bug/1903574/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1906887] Re: 3rd level key options hidden in Tweaks if show-all-sources is true

2020-12-04 Thread Gunnar Hjalmarsson
Originally reported at .

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xkeyboard-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1906887

Title:
  3rd level key options hidden in Tweaks if show-all-sources is true

Status in gnome-tweaks package in Ubuntu:
  New
Status in xkeyboard-config package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  * Enable show-all-sources

gsettings set org.gnome.desktop.input-sources show-all-sources
  'true'

  * Open Tweaks and navigate to Keyboard & Mouse ->
Additional Layout Options -> Key to choose the 3rd level

  * Find that only two odd options are shown

  I would have expected the lv3:* options to be shown, i.e.:

grep lv3 /usr/share/X11/xkb/rules/base.lst

  If I downgrade xkb-data to 2.26-2ubuntu4, the issue is not present. So
  the issue seems to be caused by some kind of incompatibility between
  gnome-tweaks and xkb-data 2.29-2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-tweaks/+bug/1906887/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1906887] [NEW] 3rd level key options hidden in Tweaks if show-all-sources is true

2020-12-04 Thread Gunnar Hjalmarsson
Public bug reported:

Steps to reproduce:

* Enable show-all-sources

  gsettings set org.gnome.desktop.input-sources show-all-sources 'true'

* Open Tweaks and navigate to Keyboard & Mouse ->
  Additional Layout Options -> Key to choose the 3rd level

* Find that only two odd options are shown

I would have expected the lv3:* options to be shown, i.e.:

  grep lv3 /usr/share/X11/xkb/rules/base.lst

If I downgrade xkb-data to 2.26-2ubuntu4, the issue is not present. So
the issue seems to be caused by some kind of incompatibility between
gnome-tweaks and xkb-data 2.29-2.

** Affects: gnome-tweaks (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: xkeyboard-config (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: focal groovy hirsute

** Also affects: xkeyboard-config (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xkeyboard-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1906887

Title:
  3rd level key options hidden in Tweaks if show-all-sources is true

Status in gnome-tweaks package in Ubuntu:
  New
Status in xkeyboard-config package in Ubuntu:
  New

Bug description:
  Steps to reproduce:

  * Enable show-all-sources

gsettings set org.gnome.desktop.input-sources show-all-sources
  'true'

  * Open Tweaks and navigate to Keyboard & Mouse ->
Additional Layout Options -> Key to choose the 3rd level

  * Find that only two odd options are shown

  I would have expected the lv3:* options to be shown, i.e.:

grep lv3 /usr/share/X11/xkb/rules/base.lst

  If I downgrade xkb-data to 2.26-2ubuntu4, the issue is not present. So
  the issue seems to be caused by some kind of incompatibility between
  gnome-tweaks and xkb-data 2.29-2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-tweaks/+bug/1906887/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1901789] Re: Release upgrade 20.04 -> 20.10 removed input method from ibus

2020-11-20 Thread Gunnar Hjalmarsson
A warning dialog added in upstream git:

https://github.com/ibus/ibus/commit/5322c447

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1901789

Title:
  Release upgrade 20.04 -> 20.10 removed input method from ibus

Status in ibus:
  New
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  What happened:
  ===

  I'm using iBus as input "method" with
  - Japanese (Anthy) // primary 
  - German
  set up. 

  I upgraded from ubuntu 20.04 to 20.10.

  EXPECTED: No changes regarding input.
  ACTUAL: German input method was removed

  
  lsb_release -rd
  ===
  Description:  Ubuntu 20.10
  Release:  20.10

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ubuntu-release-upgrader-core 1:20.10.12
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  Date: Wed Oct 28 11:10:04 2020
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to groovy on 2020-10-24 (3 days ago)
  VarLogDistupgradeTermlog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1901789/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1900729] Re: gnome-terminal font settings show only italic version of ubuntu mono

2020-11-16 Thread Gunnar Hjalmarsson
gtk and pango are both blocked by glib before they can migrate. In
addition to that there are a few other autopkgtest regressions blocking
pango.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pango1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1900729

Title:
  gnome-terminal font settings show only italic version of ubuntu mono

Status in gnome-terminal package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in pango1.0 package in Ubuntu:
  Fix Committed
Status in gnome-terminal source package in Groovy:
  Fix Released
Status in gtk+3.0 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

  When you want to select a monospace font in gnome-terminal's profile
  editor, it does not always show the regular font but rather an
  arbitrarily chosen one. The proposed gnome-terminal upload reverts an
  upstream commit, which means that all weights/styles for monospace
  fonts are shown. It takes us back to how it works in focal.

  [Test case]

  * Install the binaries built from gnome-terminal in groovy-proposed

  * Relogin

  * Open gnome-terminal -> Preferences and open the window for selecting
  a custom font for the profile. Find that it shows all available
  monospace fonts. Confirm for a few fonts that they can actually be
  selected without issues.

  [Where problems could occur]

  This is a one liner in gnome-terminal and does not affect other
  applications. So given a successful verification of the test case,
  this ought to be a safe change.

  [Other info]

  Please note that this particular change has not been made in hirsute.
  The reason is that we intend to follow upstream there, which means
  that the issue will be resolved through changes in gtk and pango.

  [Original description]

  trying to change the font in gnome-terminal, only the italics version
  of the ubuntu mono font is shown, as can be seen in the attachment. on
  the other hand, when changing fonts in the appearance settings, i can
  see all variants of the ubuntu fonts...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-terminal 3.38.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Oct 20 16:56:57 2020
  InstallationDate: Installed on 2020-10-20 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1900729/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1903808] Re: GSettings like mouse acceleration are not restored after suspend

2020-11-14 Thread Gunnar Hjalmarsson
*** This bug is a duplicate of bug 1899206 ***
https://bugs.launchpad.net/bugs/1899206

** This bug is no longer a duplicate of bug 1899509
   Mouse/touchpad settings not applied on hotplug/reconnect/resume
** This bug has been marked a duplicate of bug 1899206
   Keyboard and mouse configuration not persisting on USB keyboard 
unplug/reconnect

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1903808

Title:
  GSettings like mouse acceleration are not restored after suspend

Status in xorg package in Ubuntu:
  New

Bug description:
  I have customised some options like mouse acceleration and compose
  keys using gsettings.

  # Disable mouse acceleration
  gsettings set org.gnome.desktop.peripherals.mouse accel-profile flat
  gsettings set org.gnome.desktop.peripherals.mouse speed 0

  # Enable Compose key
  gsettings set org.gnome.desktop.input-sources xkb-options "['compose:caps']"

  
  After around end of August, those settings were not active anymore after 
suspending. A workaround was to open gnome-tweaks and change the settings to 
another value and back to the desired value again.

  If there is something I can do to locate the problem, please let me
  know.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
  Uname: Linux 5.4.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/gpu0'
  .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/capabilities/mig'
  .proc.driver.nvidia.gpus..3c.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:3c:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  450.80.02  Wed Sep 23 
01:13:39 UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.11
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 11 06:38:24 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   evdi, 1.7.0, 5.4.0-51-generic, x86_64: installed
   evdi, 1.7.0, 5.4.0-52-generic, x86_64: installed
   nvidia, 450.80.02, 5.4.0-51-generic, x86_64: installed
   nvidia, 450.80.02, 5.4.0-52-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2278]
 Subsystem: Lenovo GP108M [GeForce MX250] [17aa:2278]
  InstallationDate: Installed on 2020-05-02 (192 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20N3S4AH00
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-52-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2IET87W (1.65 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20N3S4AH00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2IET87W(1.65):bd04/07/2020:svnLENOVO:pn20N3S4AH00:pvrThinkPadT490:rvnLENOVO:rn20N3S4AH00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T490
  dmi.product.name: 20N3S4AH00
  dmi.product.sku: LENOVO_MT_20N3_BU_Think_FM_ThinkPad T490
  dmi.product.version: ThinkPad T490
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1903808/+subscriptions

-- 

[Touch-packages] [Bug 1900729] Re: gnome-terminal font settings show only italic version of ubuntu mono

2020-11-10 Thread Gunnar Hjalmarsson
pango fix uploaded to Debian

** Changed in: pango1.0 (Ubuntu)
   Status: Triaged => Fix Committed

** Changed in: pango1.0 (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pango1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1900729

Title:
  gnome-terminal font settings show only italic version of ubuntu mono

Status in gnome-terminal package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in pango1.0 package in Ubuntu:
  Fix Committed
Status in gnome-terminal source package in Groovy:
  Fix Committed
Status in gtk+3.0 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

  When you want to select a monospace font in gnome-terminal's profile
  editor, it does not always show the regular font but rather an
  arbitrarily chosen one. The proposed gnome-terminal upload reverts an
  upstream commit, which means that all weights/styles for monospace
  fonts are shown. It takes us back to how it works in focal.

  [Test case]

  * Install the binaries built from gnome-terminal in groovy-proposed

  * Relogin

  * Open gnome-terminal -> Preferences and open the window for selecting
  a custom font for the profile. Find that it shows all available
  monospace fonts. Confirm for a few fonts that they can actually be
  selected without issues.

  [Where problems could occur]

  This is a one liner in gnome-terminal and does not affect other
  applications. So given a successful verification of the test case,
  this ought to be a safe change.

  [Other info]

  Please note that this particular change has not been made in hirsute.
  The reason is that we intend to follow upstream there, which means
  that the issue will be resolved through changes in gtk and pango.

  [Original description]

  trying to change the font in gnome-terminal, only the italics version
  of the ubuntu mono font is shown, as can be seen in the attachment. on
  the other hand, when changing fonts in the appearance settings, i can
  see all variants of the ubuntu fonts...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-terminal 3.38.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Oct 20 16:56:57 2020
  InstallationDate: Installed on 2020-10-20 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1900729/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 295990] Re: Keyboard layout reset after attaching USB keyboard

2020-11-10 Thread Gunnar Hjalmarsson
@scheleaap: Please don't talk on a 12 years old and closed bug report.
You are probably experiencing bug #1899206.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xkeyboard-config in
Ubuntu.
https://bugs.launchpad.net/bugs/295990

Title:
  Keyboard layout reset after attaching USB keyboard

Status in xserver-xorg-input-evdev:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in xkeyboard-config package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gnome-control-center

  I use a laptop with Ubuntu 8.10, and has configured two keyboard
  layouts. I use "USA" as the default layout and "Sweden" as an
  alternative layout, and use  for changing layout.

  1)
  Description:  Ubuntu 8.10
  Release:  8.10

  2)
  gnome-control-center:
Installed: 1:2.24.0.1-0ubuntu7.1
Candidate: 1:2.24.0.1-0ubuntu7.1
Version table:
   *** 1:2.24.0.1-0ubuntu7.1 0
  500 http://se.archive.ubuntu.com intrepid-updates/main Packages
  100 /var/lib/dpkg/status
   1:2.24.0.1-0ubuntu7 0
  500 http://se.archive.ubuntu.com intrepid/main Packages

  3)
  When I plug in an USB keyboard it should still be possible to change between 
the default and alternative layout with  or using the applet menu. 
The default and any alternative layout should user configurable, i.e. it should 
not restore system default values when an USB keyboard is attached.

  4)
  When I plug in an USB keyboard after logging in to Ubuntu, it resets the 
keyboard layout (and probably other keyboard settings as well) to the system 
default layout which is stored in /etc/default/console-setup.

To manage notifications about this bug go to:
https://bugs.launchpad.net/evdev/+bug/295990/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1903449] Re: accountsservice displays "Libvirt Qemu"

2020-11-09 Thread Gunnar Hjalmarsson
The issue is not present in Ubuntu 20.04 or later. The question is if
dropping the patch retroactively as a bionic stable release update
should be done. I discussed this with Sebastien Bacher in the ubuntu-
desktop team, and we concluded that we are not able to tell that no
bionic user depends on the patch, so we won't drop it for bionic.

In case of libvirt-qemu you provided a nice workaround, which may be
useful for other users who encounter the issue.

** Changed in: accountsservice (Ubuntu)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1903449

Title:
  accountsservice displays "Libvirt Qemu"

Status in accountsservice package in Ubuntu:
  Fix Released

Bug description:
  Installing libvirt-manager results in account libvirt-qemu being
  created. This user has config in /etc/passwd like follows:

  libvirt-qemu:x:64055:125:Libvirt
  Qemu,,,:/var/lib/libvirt:/usr/sbin/nologin

  The "nologin" should be pretty clear signal that this account is not
  usable for logging in. Despite this, this account is offered in visual
  login (e.g. lightdm). The computation for possible user accounts is
  handled by package accountsservice.

  A workaround is to manually list this user as system user:
  echo -e "[User]\nSystemAccount=true" > 
/var/lib/AccountsService/users/libvirt-qemu

  However, as this user cannot be logged in (/etc/shadow contains "!" as
  the password hash, too) it never makes any sense to show this in login
  screen even without the above manual configuration.

  Related: bug 857651

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: accountsservice 0.6.45-1ubuntu1.3
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-lowlatency 5.4.65
  Uname: Linux 5.4.0-52-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Nov  8 16:54:24 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-01-05 (672 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: accountsservice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1903449/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1900729] Re: gnome-terminal font settings show only italic version of ubuntu mono

2020-11-09 Thread Gunnar Hjalmarsson
Verified the test case using version 3.38.0-1ubuntu1.1 of gnome-
terminal, gnome-terminal-data and nautilus-extension-gnome-terminal from
groovy-proposed.

** Tags removed: verification-needed verification-needed-groovy
** Tags added: verification-done verification-done-groovy

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pango1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1900729

Title:
  gnome-terminal font settings show only italic version of ubuntu mono

Status in gnome-terminal package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in pango1.0 package in Ubuntu:
  Triaged
Status in gnome-terminal source package in Groovy:
  Fix Committed
Status in gtk+3.0 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

  When you want to select a monospace font in gnome-terminal's profile
  editor, it does not always show the regular font but rather an
  arbitrarily chosen one. The proposed gnome-terminal upload reverts an
  upstream commit, which means that all weights/styles for monospace
  fonts are shown. It takes us back to how it works in focal.

  [Test case]

  * Install the binaries built from gnome-terminal in groovy-proposed

  * Relogin

  * Open gnome-terminal -> Preferences and open the window for selecting
  a custom font for the profile. Find that it shows all available
  monospace fonts. Confirm for a few fonts that they can actually be
  selected without issues.

  [Where problems could occur]

  This is a one liner in gnome-terminal and does not affect other
  applications. So given a successful verification of the test case,
  this ought to be a safe change.

  [Other info]

  Please note that this particular change has not been made in hirsute.
  The reason is that we intend to follow upstream there, which means
  that the issue will be resolved through changes in gtk and pango.

  [Original description]

  trying to change the font in gnome-terminal, only the italics version
  of the ubuntu mono font is shown, as can be seen in the attachment. on
  the other hand, when changing fonts in the appearance settings, i can
  see all variants of the ubuntu fonts...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-terminal 3.38.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Oct 20 16:56:57 2020
  InstallationDate: Installed on 2020-10-20 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1900729/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1903449] Re: accountsservice displays "Libvirt Qemu"

2020-11-08 Thread Gunnar Hjalmarsson
Thanks for your report!

This is similar to bug #1841079 which was fixed by dropping 0020
-support-login.defs.patch. That patch should probably be dropped in
bionic too.

Test build without the patch available in this PPA:

https://launchpad.net/~gunnarhj/+archive/ubuntu/accountsservice

** Changed in: accountsservice (Ubuntu)
   Importance: Undecided => Medium

** Changed in: accountsservice (Ubuntu)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1903449

Title:
  accountsservice displays "Libvirt Qemu"

Status in accountsservice package in Ubuntu:
  Triaged

Bug description:
  Installing libvirt-manager results in account libvirt-qemu being
  created. This user has config in /etc/passwd like follows:

  libvirt-qemu:x:64055:125:Libvirt
  Qemu,,,:/var/lib/libvirt:/usr/sbin/nologin

  The "nologin" should be pretty clear signal that this account is not
  usable for logging in. Despite this, this account is offered in visual
  login (e.g. lightdm). The computation for possible user accounts is
  handled by package accountsservice.

  A workaround is to manually list this user as system user:
  echo -e "[User]\nSystemAccount=true" > 
/var/lib/AccountsService/users/libvirt-qemu

  However, as this user cannot be logged in (/etc/shadow contains "!" as
  the password hash, too) it never makes any sense to show this in login
  screen even without the above manual configuration.

  Related: bug 857651

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: accountsservice 0.6.45-1ubuntu1.3
  ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-lowlatency 5.4.65
  Uname: Linux 5.4.0-52-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7.18
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Nov  8 16:54:24 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-01-05 (672 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: accountsservice
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1903449/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1901789] Re: Release upgrade 20.04 -> 20.10 removed input method from ibus

2020-11-08 Thread Gunnar Hjalmarsson
Good.

I understand from some other bug reports that in 20.04 (ibus 1.5.22)
German was denoted as 'xkb:de::ger', and in 20.10 (ibus 1.5.23) that was
changed to 'xkb:de::deu'. You can see what it currently looks like for
you via this command:

gsettings get org.freedesktop.ibus.general preload-engines

So the first time you logged in after the upgrade, your saved value
'xkb:de::ger' was not understood and thus ignored.

The name was changed only for a small number of XKB layouts, of which
German was one. Ideally there should have been some transition code to
deal with the change. Let's await the reaction to the upstream issue.

** Changed in: ibus (Ubuntu)
   Importance: Undecided => Low

** Changed in: ibus (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1901789

Title:
  Release upgrade 20.04 -> 20.10 removed input method from ibus

Status in ibus:
  New
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  What happened:
  ===

  I'm using iBus as input "method" with
  - Japanese (Anthy) // primary 
  - German
  set up. 

  I upgraded from ubuntu 20.04 to 20.10.

  EXPECTED: No changes regarding input.
  ACTUAL: German input method was removed

  
  lsb_release -rd
  ===
  Description:  Ubuntu 20.10
  Release:  20.10

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ubuntu-release-upgrader-core 1:20.10.12
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  Date: Wed Oct 28 11:10:04 2020
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to groovy on 2020-10-24 (3 days ago)
  VarLogDistupgradeTermlog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1901789/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1901789] Re: Release upgrade 20.04 -> 20.10 removed input method from ibus

2020-11-07 Thread Gunnar Hjalmarsson
** Bug watch added: github.com/ibus/ibus/issues #2274
   https://github.com/ibus/ibus/issues/2274

** Also affects: ibus via
   https://github.com/ibus/ibus/issues/2274
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1901789

Title:
  Release upgrade 20.04 -> 20.10 removed input method from ibus

Status in ibus:
  Unknown
Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  What happened:
  ===

  I'm using iBus as input "method" with
  - Japanese (Anthy) // primary 
  - German
  set up. 

  I upgraded from ubuntu 20.04 to 20.10.

  EXPECTED: No changes regarding input.
  ACTUAL: German input method was removed

  
  lsb_release -rd
  ===
  Description:  Ubuntu 20.10
  Release:  20.10

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ubuntu-release-upgrader-core 1:20.10.12
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  Date: Wed Oct 28 11:10:04 2020
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to groovy on 2020-10-24 (3 days ago)
  VarLogDistupgradeTermlog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1901789/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1901789] Re: Release upgrade 20.04 -> 20.10 removed input method from ibus

2020-11-07 Thread Gunnar Hjalmarsson
I would guess that this happened since
/usr/share/ibus/component/simple.xml underwent extensive changes and now
offers a lot more XKB layouts than previously.

Were you able to add back German via ibus-setup, and does it work as
expected after that?

** Package changed: ubuntu-release-upgrader (Ubuntu) => ibus (Ubuntu)

** Changed in: ibus (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1901789

Title:
  Release upgrade 20.04 -> 20.10 removed input method from ibus

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  What happened:
  ===

  I'm using iBus as input "method" with
  - Japanese (Anthy) // primary 
  - German
  set up. 

  I upgraded from ubuntu 20.04 to 20.10.

  EXPECTED: No changes regarding input.
  ACTUAL: German input method was removed

  
  lsb_release -rd
  ===
  Description:  Ubuntu 20.10
  Release:  20.10

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ubuntu-release-upgrader-core 1:20.10.12
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: XFCE
  Date: Wed Oct 28 11:10:04 2020
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to groovy on 2020-10-24 (3 days ago)
  VarLogDistupgradeTermlog:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1901789/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1900729] Re: gnome-terminal font settings show only italic version of ubuntu mono

2020-11-06 Thread Gunnar Hjalmarsson
Current status of this bug:

The gnome-terminal fix for groovy has been pushed to the VCS repo. I'm
waiting for a sponsor to upload it.

As regards hirsute: We have identified three upstream pango commits
which together with the gtk fix in hirsute-proposed fix the issue the
'right' way. The pango PPA now contains all the three commits:

https://launchpad.net/~gunnarhj/+archive/ubuntu/pango1.0

** Changed in: gnome-terminal (Ubuntu Groovy)
   Status: Triaged => In Progress

** Changed in: gnome-terminal (Ubuntu)
   Status: New => Invalid

** Changed in: pango1.0 (Ubuntu)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pango1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1900729

Title:
  gnome-terminal font settings show only italic version of ubuntu mono

Status in gnome-terminal package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in pango1.0 package in Ubuntu:
  Triaged
Status in gnome-terminal source package in Groovy:
  In Progress
Status in gtk+3.0 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

  When you want to select a monospace font in gnome-terminal's profile
  editor, it does not always show the regular font but rather an
  arbitrarily chosen one. The proposed gnome-terminal upload reverts an
  upstream commit, which means that all weights/styles for monospace
  fonts are shown. It takes us back to how it works in focal.

  [Test case]

  * Install the binaries built from gnome-terminal in groovy-proposed

  * Relogin

  * Open gnome-terminal -> Preferences and open the window for selecting
  a custom font for the profile. Find that it shows all available
  monospace fonts. Confirm for a few fonts that they can actually be
  selected without issues.

  [Where problems could occur]

  This is a one liner in gnome-terminal and does not affect other
  applications. So given a successful verification of the test case,
  this ought to be a safe change.

  [Other info]

  Please note that this particular change has not been made in hirsute.
  The reason is that we intend to follow upstream there, which means
  that the issue will be resolved through changes in gtk and pango.

  [Original description]

  trying to change the font in gnome-terminal, only the italics version
  of the ubuntu mono font is shown, as can be seen in the attachment. on
  the other hand, when changing fonts in the appearance settings, i can
  see all variants of the ubuntu fonts...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-terminal 3.38.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Oct 20 16:56:57 2020
  InstallationDate: Installed on 2020-10-20 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1900729/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1900729] Re: gnome-terminal font settings show only italic version of ubuntu mono

2020-11-06 Thread Gunnar Hjalmarsson
** Description changed:

  [Impact]
  
  When you want to select a monospace font in gnome-terminal's profile
  editor, it does not always show the regular font but rather an
- arbitrarily chosen one. The proposed gtk+3.0 upload cherry picks an
- upstream commit which fixes it.
+ arbitrarily chosen one. The proposed gnome-terminal upload reverts an
+ upstream commit, which means that all weights/styles for monospace fonts
+ are shown. It takes us back to how it works in focal.
  
  [Test case]
  
- * Install the binaries built from gtk+3.0 in groovy-proposed
+ * Install the binaries built from gnome-terminal in groovy-proposed
  
  * Relogin
  
  * Open gnome-terminal -> Preferences and open the window for selecting a
- custom font for the profile. Find that it shows regular fonts only.
+ custom font for the profile. Find that it shows all available monospace
+ fonts. Confirm for a few fonts that they can actually be selected
+ without issues.
  
- [ Regression risk ]
+ [Where problems could occur]
  
- The upstream commit was written explicitly to fix this issue, so the
- regression risk should be low. Please note that the only affected file
- is gtk/gtkfontchooserwidget.c, so the scope is very limited which in
- itself ought to limit the regression risk.
+ This is a one liner in gnome-terminal and does not affect other
+ applications. So given a successful verification of the test case, this
+ ought to be a safe change.
+ 
+ [Other info]
+ 
+ Please note that this particular change has not been made in hirsute.
+ The reason is that we intend to follow upstream there, which means that
+ the issue will be resolved through changes in gtk and pango.
  
  [Original description]
  
  trying to change the font in gnome-terminal, only the italics version of
  the ubuntu mono font is shown, as can be seen in the attachment. on the
  other hand, when changing fonts in the appearance settings, i can see
  all variants of the ubuntu fonts...
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-terminal 3.38.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Oct 20 16:56:57 2020
  InstallationDate: Installed on 2020-10-20 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pango1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1900729

Title:
  gnome-terminal font settings show only italic version of ubuntu mono

Status in gnome-terminal package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in pango1.0 package in Ubuntu:
  New
Status in gnome-terminal source package in Groovy:
  Triaged
Status in gtk+3.0 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

  When you want to select a monospace font in gnome-terminal's profile
  editor, it does not always show the regular font but rather an
  arbitrarily chosen one. The proposed gnome-terminal upload reverts an
  upstream commit, which means that all weights/styles for monospace
  fonts are shown. It takes us back to how it works in focal.

  [Test case]

  * Install the binaries built from gnome-terminal in groovy-proposed

  * Relogin

  * Open gnome-terminal -> Preferences and open the window for selecting
  a custom font for the profile. Find that it shows all available
  monospace fonts. Confirm for a few fonts that they can actually be
  selected without issues.

  [Where problems could occur]

  This is a one liner in gnome-terminal and does not affect other
  applications. So given a successful verification of the test case,
  this ought to be a safe change.

  [Other info]

  Please note that this particular change has not been made in hirsute.
  The reason is that we intend to follow upstream there, which means
  that the issue will be resolved through changes in gtk and pango.

  [Original description]

  trying to change the font in gnome-terminal, only the italics version
  of the ubuntu mono font is shown, as can be seen in the attachment. on
  the other hand, when changing fonts in the appearance settings, i can
  see all variants of the ubuntu fonts...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-terminal 3.38.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Oct 20 16:56:57 2020
  InstallationDate: Installed on 2020-10-20 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade 

[Touch-packages] [Bug 1900729] Re: gnome-terminal font settings show only italic version of ubuntu mono

2020-11-05 Thread Gunnar Hjalmarsson
This is getting too complicated to handle as an SRU considering that
it's a not-so-important issue after all. So I think we should simply
revert the problematic gnome-terminal commit in groovy only, and hope
that upstream sorts it out for hirsute. So I would like to upload this
fix to groovy:

https://launchpad.net/~gunnarhj/+archive/ubuntu/gnome-terminal

But I can't do that until the version in hirsute is bumped somehow...

** Also affects: gnome-terminal (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: pango1.0 (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: pango1.0 (Ubuntu Groovy)

** Changed in: gtk+3.0 (Ubuntu Groovy)
   Status: Fix Committed => Won't Fix

** Changed in: gtk+3.0 (Ubuntu Groovy)
 Assignee: Gunnar Hjalmarsson (gunnarhj) => (unassigned)

** Changed in: gnome-terminal (Ubuntu Groovy)
   Importance: Undecided => Low

** Changed in: gnome-terminal (Ubuntu Groovy)
   Status: New => Triaged

** Changed in: gnome-terminal (Ubuntu Groovy)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1900729

Title:
  gnome-terminal font settings show only italic version of ubuntu mono

Status in gnome-terminal package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in pango1.0 package in Ubuntu:
  New
Status in gnome-terminal source package in Groovy:
  Triaged
Status in gtk+3.0 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

  When you want to select a monospace font in gnome-terminal's profile
  editor, it does not always show the regular font but rather an
  arbitrarily chosen one. The proposed gtk+3.0 upload cherry picks an
  upstream commit which fixes it.

  [Test case]

  * Install the binaries built from gtk+3.0 in groovy-proposed

  * Relogin

  * Open gnome-terminal -> Preferences and open the window for selecting
  a custom font for the profile. Find that it shows regular fonts only.

  [ Regression risk ]

  The upstream commit was written explicitly to fix this issue, so the
  regression risk should be low. Please note that the only affected file
  is gtk/gtkfontchooserwidget.c, so the scope is very limited which in
  itself ought to limit the regression risk.

  [Original description]

  trying to change the font in gnome-terminal, only the italics version
  of the ubuntu mono font is shown, as can be seen in the attachment. on
  the other hand, when changing fonts in the appearance settings, i can
  see all variants of the ubuntu fonts...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-terminal 3.38.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Oct 20 16:56:57 2020
  InstallationDate: Installed on 2020-10-20 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1900729/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1900729] Re: gnome-terminal font settings show only italic version of ubuntu mono

2020-11-04 Thread Gunnar Hjalmarsson
Good catch, @Rasmus. I see the same thing, and posted my theory about
what causes it here:

https://gitlab.gnome.org/GNOME/pango/-/issues/483#note_953154

Hmm.. I'm afraid this can be called a regression. Even if the wrong
styles were shown previously, selecting any of those at least didn't
cause gnome-terminal to crash.

@Łukasz: What do you think? Myself can't help thinking (again) about the
alternative solution we discussed shortly, i.e. replacing this gtk
change in groovy with a simple gnome-terminal patch which would give us
the focal behavior back.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1900729

Title:
  gnome-terminal font settings show only italic version of ubuntu mono

Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in gtk+3.0 source package in Groovy:
  Fix Committed

Bug description:
  [Impact]

  When you want to select a monospace font in gnome-terminal's profile
  editor, it does not always show the regular font but rather an
  arbitrarily chosen one. The proposed gtk+3.0 upload cherry picks an
  upstream commit which fixes it.

  [Test case]

  * Install the binaries built from gtk+3.0 in groovy-proposed

  * Relogin

  * Open gnome-terminal -> Preferences and open the window for selecting
  a custom font for the profile. Find that it shows regular fonts only.

  [ Regression risk ]

  The upstream commit was written explicitly to fix this issue, so the
  regression risk should be low. Please note that the only affected file
  is gtk/gtkfontchooserwidget.c, so the scope is very limited which in
  itself ought to limit the regression risk.

  [Original description]

  trying to change the font in gnome-terminal, only the italics version
  of the ubuntu mono font is shown, as can be seen in the attachment. on
  the other hand, when changing fonts in the appearance settings, i can
  see all variants of the ubuntu fonts...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-terminal 3.38.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Oct 20 16:56:57 2020
  InstallationDate: Installed on 2020-10-20 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1900729/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1900729] Re: gnome-terminal font settings show only italic version of ubuntu mono

2020-11-04 Thread Gunnar Hjalmarsson
** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1900729

Title:
  gnome-terminal font settings show only italic version of ubuntu mono

Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in gtk+3.0 source package in Groovy:
  Fix Committed

Bug description:
  [Impact]

  When you want to select a monospace font in gnome-terminal's profile
  editor, it does not always show the regular font but rather an
  arbitrarily chosen one. The proposed gtk+3.0 upload cherry picks an
  upstream commit which fixes it.

  [Test case]

  * Install the binaries built from gtk+3.0 in groovy-proposed

  * Relogin

  * Open gnome-terminal -> Preferences and open the window for selecting
  a custom font for the profile. Find that it shows regular fonts only.

  [ Regression risk ]

  The upstream commit was written explicitly to fix this issue, so the
  regression risk should be low. Please note that the only affected file
  is gtk/gtkfontchooserwidget.c, so the scope is very limited which in
  itself ought to limit the regression risk.

  [Original description]

  trying to change the font in gnome-terminal, only the italics version
  of the ubuntu mono font is shown, as can be seen in the attachment. on
  the other hand, when changing fonts in the appearance settings, i can
  see all variants of the ubuntu fonts...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-terminal 3.38.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Oct 20 16:56:57 2020
  InstallationDate: Installed on 2020-10-20 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1900729/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1900729] Re: gnome-terminal font settings show only italic version of ubuntu mono

2020-11-04 Thread Gunnar Hjalmarsson
@Darko: Yeah, it's indeed different compared to focal. But as was stated
on the upstream issue, it's an intentional design change, and probably
better for most use cases given this gtk fix.

Thanks for verifying!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1900729

Title:
  gnome-terminal font settings show only italic version of ubuntu mono

Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in gtk+3.0 source package in Groovy:
  Fix Committed

Bug description:
  [Impact]

  When you want to select a monospace font in gnome-terminal's profile
  editor, it does not always show the regular font but rather an
  arbitrarily chosen one. The proposed gtk+3.0 upload cherry picks an
  upstream commit which fixes it.

  [Test case]

  * Install the binaries built from gtk+3.0 in groovy-proposed

  * Relogin

  * Open gnome-terminal -> Preferences and open the window for selecting
  a custom font for the profile. Find that it shows regular fonts only.

  [ Regression risk ]

  The upstream commit was written explicitly to fix this issue, so the
  regression risk should be low. Please note that the only affected file
  is gtk/gtkfontchooserwidget.c, so the scope is very limited which in
  itself ought to limit the regression risk.

  [Original description]

  trying to change the font in gnome-terminal, only the italics version
  of the ubuntu mono font is shown, as can be seen in the attachment. on
  the other hand, when changing fonts in the appearance settings, i can
  see all variants of the ubuntu fonts...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-terminal 3.38.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Oct 20 16:56:57 2020
  InstallationDate: Installed on 2020-10-20 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1900729/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1900729] Re: gnome-terminal font settings show only italic version of ubuntu mono

2020-11-02 Thread Gunnar Hjalmarsson
Hi Łukasz,

As regards other concurrent fixes, I first asked Iain Lane if there is
such a plan for groovy, but the most likely SRU in pipeline would be a
focal update to 3.24.23, so he gave me a 'green light' for this groovy
one.

The bug is an annoying one. Maybe the importance was set too low...

The story is summarized on this upstream issue:

https://gitlab.gnome.org/GNOME/pango/-/issues/483

It was closed by Matthias C. since he first thought it was an issue with
the Ubuntu font. When he realized that the incorrect gnome-terminal
behavior was caused by an issue in gtk3's font chooser, he instantly
submitted that commit. Please note that the only affected file is
gtk/gtkfontchooserwidget.c, so the scope is very limited which in itself
ought to limit the regression risk. Also, Matthias is an experienced
GNOME developer, and usually knows what he is doing.

I have confirmed in advance that the change fixes the gnome-terminal
issue.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1900729

Title:
  gnome-terminal font settings show only italic version of ubuntu mono

Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in gtk+3.0 source package in Groovy:
  In Progress

Bug description:
  [Impact]

  When you want to select a monospace font in gnome-terminal's profile
  editor, it does not always show the regular font but rather an
  arbitrarily chosen one. The proposed gtk+3.0 upload cherry picks an
  upstream commit which fixes it.

  [Test case]

  * Install the binaries built from gtk+3.0 in groovy-proposed

  * Relogin

  * Open gnome-terminal -> Preferences and open the window for selecting
  a custom font for the profile. Find that it shows regular fonts only.

  [ Regression risk ]

  The upstream commit was written explicitly to fix this issue, so the
  regression risk should be low.

  [Original description]

  trying to change the font in gnome-terminal, only the italics version
  of the ubuntu mono font is shown, as can be seen in the attachment. on
  the other hand, when changing fonts in the appearance settings, i can
  see all variants of the ubuntu fonts...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-terminal 3.38.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Tue Oct 20 16:56:57 2020
  InstallationDate: Installed on 2020-10-20 (0 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1900729/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


  1   2   3   4   5   6   7   8   9   10   >